H12-891_V1.0 Exam Dumps - HCIE-Datacom V1.0

Link-LSA (Type 8) in OSPFv3 performs the following:

Advertises the router’s link-local address to neighbors.

Advertises the router’s interface ID on the link.

Carries IPv6 prefixes associated with the interface (since Router LSA no longer does this in OSPFv3).

The Options field in Link-LSA contains capabilities of the originating router, not the options from Network-LSA.

So, Option D is incorrect — the Link-LSA does not advertise options from the Network-LSA.

Correct answer: D

In Huawei’s VXLAN implementation, the typical mapping between VNIs (VXLAN Network Identifiers) and BDs (Bridge Domains) is:

1:1 mapping — each VNI is uniquely associated with a single bridge domain.

This allows proper MAC learning and forwarding in the data plane for isolated tenant traffic.

Other mappings (N:1, 1:N, N:M) may be technically possible but not recommended or supported in most enterprise deployments.

Correct answer: B. 1:1

PQ (Priority Queuing) ensures low-latency services like voice and video are prioritized.

WFQ (Weighted Fair Queuing) fairly allocates remaining bandwidth to services like FTP.

Option B provides a balanced approach: guarantees for voice/video via PQ, and fairness for FTP via WFQ.

Exact Extract - Huawei HCIE-Datacom QoS Module:

“Voice and video traffic should be handled by PQ to minimize delay and jitter. Non-critical services such as FTP should be placed in WFQ queues to ensure bandwidth fairness.”

EVPN Route Types:

Type 1 (MAC/IP Advertisement Route): Advertises host MAC and IP information — used.

Type 2 (MAC/IP Advertisement Route): Advertises MAC + IP binding for end hosts — used.

Type 3 (Inclusive Multicast Ethernet Tag Route): Used to advertise VXLAN multicast group info — used.

Type 4 (Ethernet Segment Route): Used in multi-homing scenarios, especially in DC (data center) environments, to coordinate DF election — typically not used in campus VXLAN.

So in campus virtualized networks, which are often single-homed, Type 4 is not required.

Correct answer: C. Type 4

Let’s break this down step-by-step based on Huawei IS-IS VPN and multi-process behavior.

🔹 Configuration Summary:

Process 1: IS-IS for the global routing table

Process 2: IS-IS for VPN instance tt

Process 3: IS-IS for VPN instance rr

✅ Option C: Correct

Process 1 contains only global routing information.

The configuration of isis 1 does not include any vpn-instance keyword, meaning it is bound to the global routing table.

It does not interact with VPN routing tables unless explicitly configured with import/export mechanisms or route leaking (which is not shown here).

Huawei Datacom Reference:

“When an IS-IS process is not associated with a VPN instance, it belongs to the global routing table and only maintains global routes.”

(Source: HCIE-Datacom Study Guide v3.0 – Chapter: IS-IS for IPv4 and IPv6, Section: Multi-Instance Routing)

✅ Option D: Correct

Routing information of process 2 is isolated from that of process 3.

isis 2 is bound to VPN instance tt

isis 3 is bound to VPN instance rr

Each IS-IS process in Huawei VRF context maintains independent LSDBs and routing tables, and by default, they do not share routing information unless route leaking or redistribution is configured (which is not shown in the config).

Huawei Datacom Reference:

“IS-IS processes bound to different VPN instances operate independently and do not share routing information.”

(Source: HCIE-Datacom Study Guide v3.0 – Chapter: MPLS L3VPN with IS-IS)

Comprehensive and Detailed Explanation:

✔ gRPC supports four types of RPCs:

Unary RPC → Client sends one request, server responds once.

Server streaming RPC → Server sends multiple responses.

Client streaming RPC → Client sends multiple requests.

Bidirectional streaming RPC → Both sides exchange multiple messages.

✔ Why B and C Are Incorrect:

❌ (B) Incorrect → The method rpc dataPublish(stream serviceArgs) returns(stream serviceArgs) {} violates gRPC syntax.

❌ (C) Incorrect → rpc stream LotsOfGreetings(HelloRequest) returns (HelloResponse) {} contains incorrect stream positioning.

📖 Reference: Huawei HCIE Datacom – gRPC API and Streaming Mechanisms

Comprehensive and Detailed In-Depth Explanation:

BGP4+ (BGP for IPv6) uses the MP_REACH_NLRI (Multiprotocol Reachable Network Layer Reachability Information) attribute to advertise IPv6 routes. This attribute is part of BGP ' s multiprotocol extensions (RFC 2858), allowing BGP to support multiple address families, including IPv6.

MP_REACH_NLRI: Advertises reachable IPv6 prefixes along with next-hop information.

MP_UNREACH_NLRI: Used to withdraw previously advertised IPv6 routes.

Since IPv6 addresses are significantly different from IPv4 addresses in structure and length (128 bits), the traditional BGP update message format (which supports only IPv4) is insufficient. The MP_REACH_NLRI attribute solves this by carrying IPv6-specific information.

Understanding OSPF Neighbor States

OSPF (Open Shortest Path First) establishes neighbor relationships through several states:

1️⃣ Down: No Hello packets received.

2️⃣ Init: Router receives Hello packets but its own Router ID is missing in the received packets.

3️⃣ 2-Way: Routers see each other in Hello packets. (Stable state for non-DR/non-BDR routers).

4️⃣ ExStart: Routers start exchanging LSAs but may face MTU mismatches.

5️⃣ Exchange: Routers send Database Description (DBD) packets to synchronize link-state databases.

6️⃣ Loading: Routers exchange Link-State Requests (LSRs) & Updates (LSUs) to fully sync.

7️⃣ Full: Routers are fully synchronized.

Analysis of the Answer Choices

✅ A. For non-DR and non-BDR routers on an Ethernet link, the 2-Way state is acceptable.

Correct: Non-DR/Non-BDR routers remain in 2-Way state since they don’t need to form full adjacency.

✅ B. The Init state indicates that the router has received Hello packets from its neighbors, but the received Hello packets do not contain the OSPF RID of the receiving router.

Correct: If an OSPF router receives a Hello but does not see its own Router ID, it stays in the Init state.

✅ C. The ExStart state indicates that two neighbor routers have inconsistent MTUs or the same OSPF Router ID (RID).

Correct: If MTUs mismatch or RIDs conflict, the DBD exchange fails, causing routers to remain in ExStart state.

❌ D. The Attempt state indicates that the router does not send unicast Hello packets to configured neighbors.

Incorrect:

In Attempt state, routers send unicast Hello packets to manually configured neighbors (common in NBMA networks).

If no Hello responses are received, they remain in Attempt state, but they DO send Hellos.

Real-World Application

OSPF Troubleshooting: Identifying routers stuck in Init or ExStart states can point to MTU mismatches or neighbor misconfigurations.

NBMA Networks (Frame Relay, DMVPN): Manually configured neighbors may stay in Attempt state if Hello packets are lost.

✅ Reference: Huawei HCIE-Datacom Study Guide – OSPF Neighbor States & Troubleshooting