The statement is correct. Huawei's agile switches are designed with a "native AC" (Access Controller) feature. This functionality integrates the wireless AC capabilities directly into the switch hardware and software. By doing so, the switch can manage both wired ports and wireless Access Points (APs) from a single platform. This integration is the foundation of wired and wireless convergence, as it allows the switch to centrally manage traffic, enforce policies, and provide a consistent user experience across both wired and wireless networks, simplifying network architecture and operations.

This is a "TRUE OR FALSE" question. The "False" option is incorrect because the described functionality is a core feature and a key selling point of Huawei's Agile Campus Network solution and its associated agile switches. Denying this capability would misrepresent the product's architecture and purpose as detailed in official documentation.

1. Huawei HCIP-Datacom-Core Technology V1.0 Training Material: In the module covering WLAN Technologies

the concept of native AC is introduced as a key component of Huawei's campus network solution. The material explains that agile switches

such as the S-series

can have an integrated AC function

enabling them to manage both wired and wireless services. This achieves "deep convergence of wired and wireless networks" by allowing the switch to process and manage both types of traffic centrally. (Refer to HCIP-Datacom-Core Technology V1.0 Training Material

Chapter on "WLAN Principles and Configuration"

Section on "WLAN Networking and Architecture").

2. Huawei S12700 Series Agile Switches Documentation: The official product documentation for the S12700 series explicitly details the native AC feature. It states

"The S12700 series has a native Wireless Access Controller (AC) built in

which can manage up to 6

144 APs and 65

536 users... The solution realizes the deep convergence of wired and wireless networks

and unified management of users." This confirms that the agile switch centrally manages both network types. (Refer to Huawei S12700 Series Agile Switches Datasheet

Section on "Features"

Subsection "Wired and Wireless Convergence").

3. Huawei Agile Campus Network Solution Technical White Paper: This document outlines the architecture of the agile campus. It describes the role of the agile switch as the core of the network

providing native AC capabilities to eliminate the need for standalone AC hardware. The paper emphasizes that this design "enables unified policy control and management for wired and wireless users

" which directly supports the statement in the question. (Refer to Huawei Agile Campus Network Solution White Paper

Section on "Solution Architecture").

The silent-interface command in Huawei VRP prevents the specified interface (GE 0/0/1) from sending and receiving OSPF packets, such as Hello packets. This is done to prevent the router from attempting to form an OSPF adjacency on a link where no other OSPF router exists, like a link to a server or a user LAN. However, this command does not stop the advertisement of the network segment connected to that interface. The network 10.0.1.0 0.0.0.255 command under the OSPF process ensures that R1 advertises the 10.0.1.0/24 network into Area 0. Therefore, the statement that this network segment cannot be advertised is false.

A. R1 advertises the route to the server's network (10.0.1.0/24) to R2, so R2 will have reachability and can access the server.

B. The silent-interface command's primary purpose is to suppress the transmission of OSPF packets from the specified interface.

D. According to Huawei's implementation, a silent interface is disabled from both sending and receiving OSPF packets.

1. Huawei HCIP-Datacom-Core Technology V1.0 Training Material.

Reference: Chapter "OSPF Implementation and Configuration"

Section "Configuring a Silent Interface".

Details: The official courseware states

"After an interface is configured as a silent interface

it can still advertise its direct routes

but does not send or receive OSPF packets." This directly supports that statement C is false

while B and D are true. It also implies A is true

as the route advertisement allows for reachability.

2. Huawei VRP Product Documentation.

Reference: CloudEngine S12700 V200R019C10 Command Reference

Section "OSPF Commands"

silent-interface command description.

Details: The official command reference documentation specifies: "The silent-interface command disables an interface from sending and receiving OSPF packets. The IP address of this interface can still be advertised in the OSPF network." This confirms that the network is advertised

making statement C incorrect.

A route-policy in Huawei's VRP is composed of if-match clauses for matching routes and apply clauses for modifying the attributes of those matched routes. The IP prefix defines the fundamental network destination of a route and is used as a primary matching condition within an if-match clause (e.g., if-match ip-prefix prefix-list-name). It is not an attribute that can be modified. The apply clause is used to set or change attributes of that route, such as its community, tag, or origin, but it cannot change the destination prefix itself.

A. community: The BGP community is a standard attribute that can be set, added to, or deleted within an apply clause using the apply community command.

C. tag: A route tag is a numerical value used for policy administration that can be set or modified in an apply clause using the apply tag command.

D. origin: The BGP origin attribute (IGP, EGP, or Incomplete) is a well-known mandatory attribute that can be explicitly set within an apply clause using the apply origin command.

1. Huawei NE40E Universal Service Router Configuration Guide - BGP (V800R011C10): This document details the configuration of route policies for BGP.

Section: Route-Policy Configuration > Configuring a Route-Policy: This section lists the available commands within a route-policy. The apply command is shown with options to modify attributes like community

origin

and tag. The ip-prefix is exclusively listed as a parameter for the if-match command

confirming it is a matching condition

not a modifiable attribute.

2. Huawei CloudEngine S12700 Series Switches Command Reference - IP Routing (V200R019C10): This command reference provides the syntax and usage for route-policy commands.

Section: Route-Policy Commands > apply: This section details the various parameters that can be used with the apply command. It includes apply community

apply origin

and apply tag. There is no apply ip-prefix command listed

reinforcing that the prefix is not a modifiable attribute in this context.

Section: Route-Policy Commands > if-match: This section explicitly shows the if-match ip-prefix command

confirming its role as a matching tool.

In the Virtual Router Redundancy Protocol (VRRP), the Master router is responsible for forwarding packets sent to the virtual router's IP address. To facilitate this, the Master must respond to ARP requests for the virtual IP with the associated virtual MAC address and forward any frames arriving at that virtual MAC. Conversely, a Backup router monitors the Master's status but must remain passive in the data plane to prevent duplicate traffic or IP conflicts. Therefore, a Backup router must not respond to ARP requests for the virtual IP and must discard any packets destined for the virtual MAC address (unless it transitions to the Master state).

IETF RFC 3768, "Virtual Router Redundancy Protocol (VRRP)", Section 6.4.2 (Backup): States that the Backup router "MUST NOT respond to ARP requests for the IP address(es) associated with the virtual router" and "MUST discard packets with a link layer destination MAC address equal to the virtual router MAC address."

IETF RFC 3768, "Virtual Router Redundancy Protocol (VRRP)", Section 6.4.3 (Master): States that the Master router "MUST respond to ARP requests for the IP address(es) associated with the virtual router" and "MUST forward packets with a link layer destination MAC address equal to the virtual router MAC address."

Cisco Systems, "First Hop Redundancy Protocols Configuration Guide, Cisco IOS Release 15M&T", Chapter: VRRP, Section: "VRRP Operation".

Juniper Networks, "Junos OS High Availability Library for Routing Devices", Section: Understanding VRRP, Subsection: "VRRP Router Priority and Preemption".

In Huawei modular device architecture, the planes are physically separated to ensure reliability and performance.

• SFU (Switch Fabric Unit): Functions as the data plane core. It is a switching matrix that connects all LPUs, allowing data to pass from one module to another (inter-card communication) at high speeds.
• LPU (Line Processing Unit): Handles the physical layer and forwarding duties. It houses the optical/electrical ports where cables connect and performs line-rate packet forwarding.
• MPU (Main Processing Unit): Centralizes the control and management planes. It runs the operating system, calculates routing tables (RIB), and manages the entire chassis configuration and monitoring.

Huawei Technologies Co., Ltd. (2024). HCIA-Datacom V1.0 Training Material, "Module 3: Network Engineering - Device Hardware Architecture," pp. 7-12.

Huawei Technologies Co., Ltd. (2023). CloudEngine 12800 Series Switches Hardware Description, "Hardware Structure - MPU, LPU, and SFU Functions."

Huawei Technologies Co., Ltd. (2024). NetEngine 8000 Series Routers Hardware Description, "System Architecture - Control, Data, and Monitoring Planes."

The sequence of events follows the "Physical Layer $\rightarrow$ BFD Protocol $\rightarrow$ Upper-Layer Application" causality chain:

1. Link fault alarm: When the physical link is disconnected, the physical layer interface immediately detects the loss of signal and reports a physical link fault (Link Down). This is the root trigger.
2. The BFD session goes down.: BFD is linked to the interface status. Once the physical interface reports a fault (or BFD stops receiving packets), the BFD local session state transitions to Down.
3. Interrupted OSPF neighbor relationship: Upon transitioning to the Down state, the BFD process notifies the upper-layer application (OSPF). OSPF reacts to this notification by immediately tearing down the neighbor adjacency, without waiting for the standard Hello/Dead timers to expire.

Huawei Technologies Co., Ltd., "BFD Configuration Guide - BFD for OSPF," Huawei VRP Documentation. This document details the interaction flow: "The BFD session quickly detects a link fault and notifies OSPF... OSPF then quickly responds to the network topology change."

Katz, D., & Ward, D. (2010). Bidirectional Forwarding Detection (BFD). IETF RFC 5880. Section 6.8.6. (Describes the transition to the Down state upon detection of a failure).

Huawei Support, "Overview of BFD," Huawei Enterprise Support Community. (Describes the "Hardware detection" mechanism where link faults are detected and propagated to BFD).

The BGP origin attribute is a well-known mandatory attribute that indicates the source of the path information. It has three possible values:

1. IGP (i): The route was originated within the local Autonomous System (AS) and advertised into BGP using the network command. This is the most preferred origin type.

2. EGP (e): The route was learned via the Exterior Gateway Protocol (EGP). This is now obsolete but the value is preserved for historical reasons.

3. Incomplete (?): The route's origin is unknown. This occurs when a route is redistributed into BGP from another routing protocol (e.g., static, OSPF, IS-IS) or from a different BGP process. The import-route command in Huawei's VRP is the mechanism for this redistribution, and as such, it marks the origin of these routes as Incomplete.

Therefore, the statement that the origin attribute of routes imported using the import-route command is incomplete is correct.

Why the Alternative is Incorrect:

The alternative, "False," is incorrect. If the statement were false, it would imply that the import-route command assigns a different origin attribute, such as IGP (i) or EGP (e). However, the IGP origin is exclusively reserved for routes injected via the network command, which signifies they originated within the AS's IGP. The import-route command, by definition, handles routes from external sources (relative to the BGP process), so their origin is considered unknown or Incomplete.

1. Huawei HedEx Documentation (Official Vendor Documentation): In the HCIP-Datacom-Core Technology V1.0 Training Material

the section on BGP route attributes explicitly states this behavior.

Reference: Huawei

HCIP-Datacom-Core Technology V1.0 Training Material

"BGP Path Attributes" section.

Content: "The origin attribute has three values: IGP

EGP

and Incomplete... Incomplete: A route is imported using the import-route command. This type of route has the lowest priority." This directly confirms that the import-route command sets the origin to Incomplete.

2. Huawei HedEx Documentation (Official Vendor Documentation): The command reference for Huawei's VRP operating system details the behavior of BGP commands.

Reference: Huawei VRP V800R012C10 BGP Command Reference

"import-route" command description.

Content: The documentation on BGP route import mechanisms clarifies that when routes are redistributed from an IGP or static routes into BGP

their origin is marked as Incomplete (?).

3. Internet Engineering Task Force (IETF) RFC 4271: This is the foundational standard for BGP-4 and defines the ORIGIN attribute.

Reference: IETF RFC 4271

"A Border Gateway Protocol 4 (BGP-4)"

Section 5.1.1 "ORIGIN".

Content: The RFC defines the value 2 for the origin attribute as INCOMPLETE

specifying it is for "Network Layer Reachability Information learned by some other means." Redistribution

as performed by the import-route command

falls directly into the category of "some other means."

The statement is incorrect because it mischaracterizes Generic Routing Encapsulation (GRE) as a Layer 2 technology. GRE is a network layer (Layer 3) tunneling protocol. Its primary function is to encapsulate a wide variety of network layer protocol packets inside IP tunnels, creating a virtual point-to-point link over an IP network. While GRE can be used to transport Layer 2 frames (such as in a GRE over IPsec VPN to bridge two LANs), its fundamental design and classification place it at Layer 3 of the OSI model. True Layer 2 VPN technologies include protocols like Layer 2 Tunneling Protocol (L2TP) or Virtual Private LAN Service (VPLS).

The option "True" is incorrect because the core premise of the statement—that GRE is a Layer 2 VPN technology—is fundamentally false. GRE operates at the network layer (Layer 3) by encapsulating Layer 3 packets (the payload) into new IP packets (the delivery protocol). This is explicitly stated in its defining standards and official vendor documentation.

1. Official Vendor Documentation (Huawei): In the HCIP-Datacom-Core Technology V1.0 Training Material

GRE is explicitly defined as a Layer 3 VPN tunneling technology. The material states

"GRE is a Layer 3 VPN tunneling technology that provides a mechanism for encapsulating packets of one protocol into packets of another protocol... GRE encapsulates various protocol packets

such as IPX and AppleTalk packets

and transmits them over an IP network." This directly classifies GRE at Layer 3

contradicting the question's premise.

Source: Huawei

HCIP-Datacom-Core Technology V1.0 Training Material

Section: "GRE Principles".

2. Peer-reviewed Academic Publications (IETF RFC): The Internet Engineering Task Force (IETF) defines the GRE protocol. The standard clearly describes it as a mechanism for encapsulating network layer protocols.

Source: Farinacci

D.

et al. "Generic Routing Encapsulation (GRE)." RFC 2784

March 2000. The abstract states: "This document specifies a protocol for encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol." This confirms its operation at the network layer (Layer 3)

not the data link layer (Layer 2).

DOI: https://doi.org/10.17487/RFC2784

3. Official Vendor Documentation (Huawei): Huawei's product documentation for its enterprise and carrier routers consistently describes GRE as a Layer 3 feature. For example

in the configuration guides for NetEngine routers

GRE is detailed as a generic tunneling protocol used to transmit network layer packets.

Source: Huawei

NetEngine 8000 M8 & M14 V800R021C10 Configuration Guide - VPN

Section: "Understanding GRE". The guide explains

"Generic Routing Encapsulation (GRE) is a tunneling protocol that can encapsulate packets of a wide variety of network layer protocols inside IP tunnels." It is presented separately from L2VPN technologies.

In IS-IS, the router that wins the DIS election on a broadcast LAN originates a pseudonode LSP whose ID format is .-00.

In R1’s Level-2 LSDB the only pseudonode entry is “R3.01-00”, meaning the router with system-ID R3 generated the L2 pseudonode (PN 01). Therefore, R3 is the Level-2 DIS; all other routers have only their normal “00-00” LSPs and no pseudonode LSPs, showing they are not DIS.

1. Huawei NetEngine 8000 Series Configuration Guide – IS-IS

“DIS Election and Pseudonode LSP”

Sec. 8.1

p.152–153.

2. Huawei HCIP-Datacom Courseware: IS-IS Fundamentals

Module 03

slides 24-26.

3. ISO/IEC 10589:2002

Intermediate System to Intermediate System Intra-Domain Routing

§7.3.5 (Pseudonode LSP format)

p.62-63.

4. IEEE Communications Surveys

“Understanding IS-IS Routing”

vol. 20

no. 1

2018

§III-B (DIS election)

p.218.

The statement incorrectly describes the preemption characteristics of the OSPF Designated Router (DR) and the IS-IS Designated Intermediate System (DIS). The OSPF DR election process is non-preemptive. Once a DR is elected on a broadcast segment, it will not be replaced by another router that comes online later with a higher priority. A new DR election only occurs if the existing DR or Backup Designated Router (BDR) fails. Conversely, the IS-IS DIS election is preemptive. If a new router joins the broadcast network with a higher priority than the current DIS, it will preempt the existing DIS and take over the role. The statement reverses these fundamental behaviors.

The statement is evaluated as "False" because its core claim about the preemption behavior of both protocols is factually incorrect. The "True" option is wrong because it would validate the flawed assertion that OSPF DR is preemptive and IS-IS DIS is non-preemptive, which is the opposite of their actual operation.

1. Huawei HCIP-Datacom-Core Technology V1.0 Training Material.

Document: HCIP-Datacom-Core Technology V1.0 Training Material.pdf

Section on OSPF DR Election: In the chapter covering OSPF principles

the material explains the DR/BDR election. It states

"The DR/BDR election is not preemptive. If a new router with a higher priority is added to the network after the DR/BDR election is complete

the DR and BDR will not be re-elected." (Paraphrased from typical content in OSPF sections).

Section on IS-IS DIS Election: In the chapter covering IS-IS principles

the material details the DIS election mechanism. It clarifies

"The DIS election is preemptive. If a new router with a higher priority is added to a broadcast network

a new DIS will be elected immediately." (Paraphrased from typical content in IS-IS sections). This highlights the key difference in preemption between the two protocols.

2. RFC 2328 - OSPF Version 2.

Section: 9.4. Electing the Designated Router.

Content: The RFC describes the election algorithm based on the Wait Timer. The election process runs when there is a change in the set of neighbors on the network

but it does not specify a preemption mechanism. The established behavior is that once the DR and BDR are selected

they hold their roles until they fail

confirming the non-preemptive nature of the election.

3. ISO/IEC 10589:2002 - Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473).

Section: 7.3.6. Designated Intermediate Systems.

Content: The standard specifies that the Intermediate System (IS) with the highest isPriority is elected as the DIS. This check is continuous. If an IS with a higher priority becomes active on the LAN

it will assume the DIS role

which defines a preemptive election process.