Huawei H12-891_V1.0 - HCIE-Datacom V1.0

In Huawei iMaster NCE-WAN controller active/standby deployment, to ensure seamless switchover and uninterrupted management and control channel communication, the following IPs must be configured consistently:

A. Southbound public IP addresses — Required for southbound communication from remote WAN devices via public networks.

C. Southbound private IP addresses — Used for devices accessing controllers over private links. Must remain unchanged between controllers.

D. Northbound IP addresses — For API and external system integration, ensuring upper-layer platforms don ' t need reconfiguration during switchover.

Internal interconnection addresses (B) are used for internal HA communication between controllers and do not need to be identical, hence not selected.

Exact Extract - Huawei HCIE-Datacom iMaster NCE-WAN Deployment Guide:

“To maintain service continuity, configure consistent southbound and northbound IP addresses across active and standby controllers. Internal interconnection addresses differ between nodes.”

Comprehensive and Detailed In-Depth Explanation:

In large- and medium-sized campus networks, Multi-mode authentication is commonly used for PCs connected to IP phones. This is because multi-mode authentication allows:

Multiple authentication methods on the same interface, such as MAC address authentication for the IP phone and 802.1X authentication for the PC.

This setup is ideal for scenarios where both devices share a single network port but require different authentication mechanisms.

MAC address authentication (A) and 802.1X authentication (B) individually cannot accommodate both devices efficiently.

Portal authentication (D) is mainly used for guest access and is not practical for IP phone and PC connections.

🔸 R1 – Headend

It receives a normal IPv6 packet from CE1.

It inserts the SRH (Segment Routing Header) with segment list.

Therefore, R1 is the Headend.

Huawei Reference:

“The SRv6 headend node receives a normal IPv6 packet and inserts an SRH, becoming the source of the SR path.”

(Source: HCIE-Datacom V1.0 – SRv6 Fundamentals)

🔸 R2 – Transit Node

R2 simply forwards the SRv6-encapsulated packet.

It does not process any segment SID.

Hence, R2 is a Transit node.

“Transit nodes in SRv6 just forward packets based on the active segment in the IPv6 destination address without processing SRH.”

(Source: HCIE-Datacom Study Guide – SRv6 Node Roles)

🔸 R3 – Endpoint

The first SID in SRH is FC03::3, which belongs to R3.

R3 processes the SID, pops it, and forwards the packet to the next segment FC04::4.

Thus, R3 is an Endpoint for one segment.

🔸 R4 – Endpoint

The final destination SID in the SRH is FC04::4, which belongs to R4.

R4 performs the final End behavior, handling the payload.

So, R4 is also an Endpoint.

Comprehensive and Detailed Explanation:

✔ SR-MPLS Policy candidate paths are used for flexible path selection and load balancing in Segment Routing (SR-MPLS) networks.

✔ Correct Statements:

✅ (A) Each candidate path can have multiple segment lists, each with its own weight for load balancing.

✅ (B) Load balancing is supported both between candidate paths and within segment lists.

✅ (C) An SR-MPLS Policy can contain multiple candidate paths, each with a preference value.

✅ (D) The candidate path with the highest preference is selected as the primary path.

📖 Reference: Huawei HCIE Datacom – SR-MPLS Policy Path Selection

Comprehensive and Detailed In-Depth Explanation:

Telemetry in a narrow sense refers specifically to the device-side telemetry process, which includes the following key modules:

Data generation (A): The device collects and generates telemetry data, such as performance metrics or operational statistics.

Data push (B): The device actively pushes the collected data to the configured destination (such as a collector or management system) using a data streaming protocol.

Data source (C): The entity on the device that generates or provides the monitored data.

Data subscription (D) is not part of the device-side telemetry; it is related to the management system side, where users subscribe to specific telemetry data streams.

Therefore, the correct answers are A, B, C.

Comprehensive and Detailed In-Depth Explanation:

In the inter-AS MPLS VPN Option B solution:

Option B establishes a multi-hop eBGP connection between the ASBRs (ASBR-PE1 and ASBR-PE2) to exchange VPNv4 routes.

In this setup, the ASBRs exchange labeled VPNv4 routes via MP-BGP (Multiprotocol BGP).

The command:

[ASBR-PE1-bgp-af-vpnv4] undo peer 10.0.34.4 enable

is used to disable VPNv4 route exchange between the ASBR-PE1 and ASBR-PE2.

If this command is executed, ASBR-PE1 will not transmit VPNv4 routes to ASBR-PE2, breaking the inter-AS VPN connectivity.

Therefore, the statement is FALSE because ASBR-PE1 and ASBR-PE2 must exchange VPNv4 routes to maintain connectivity between the VPN sites across different ASes.