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

Let’s analyze the scenario and each statement carefully based on OSPF path selection and BGP behavior in Huawei routers.

✅ Option A: The preferred path is R1–R3–R4.

According to the OSPF cost values:

R1–R3–R4: Cost = 1 + 1 = 2

R1–R2–R4: Cost = 2 + 2 = 4

OSPF chooses the lowest-cost path to reach a destination. Therefore, R1 will prefer the R1–R3–R4 path to reach 172.20.1.4/32.

Huawei Datacom Reference:

" OSPF selects routes based on the shortest path calculated using link costs. The router always selects the path with the lowest cost. "

(Source: HCIE-Datacom Study Guide v3.0 – OSPF Path Selection, Chapter 5)

✅ Option B: If the stub router on-startup command is run on R3, packet loss occurs during the power-off process of R3 but no packet loss occurs during the startup process of R3.

When R3 is powered off, OSPF needs to reconverge, which causes temporary packet loss.

When R3 starts up, it will advertise itself as a stub router using the stub-router on-startup command. This tells OSPF not to use R3 as a transit path during the startup period, thus preventing traffic blackholing.

Huawei Datacom Reference:

" stub-router on-startup command prevents a newly started router from being used as a transit node by OSPF, allowing routing to remain stable during convergence. "

(Source: HCIE-Datacom Study Guide v3.0 – OSPF Stub Router Functionality, Chapter 6.2)

❌ Option C: The preferred path is R1–R2–R4.

This is incorrect because the OSPF path cost via R2 is higher (4) than the cost via R3 (2).

❌ Option D: Packet loss occurs during both the power-off and startup processes of R3.

Incorrect. As explained above, when the stub-router on-startup command is used, packet loss is avoided during startup, but still occurs during power-off since the alternate path requires convergence.

In MPLS LDP, there are two types of sessions:

Direct LDP sessions: Established between directly connected LSRs using LDP Hellos over a link.

Remote LDP sessions (also called targeted LDP sessions): Established between non-directly connected LSRs. These require manual configuration of the remote peer.

In this scenario, SWA and SWC are not directly connected, so a remote (targeted) LDP session must be set up.

For a remote LDP session:

You must configure the remote peer using the command:

[SWA-MPLS-LDP] targeted-peer x.x.x.x

Where x.x.x.x is the LSR ID of SWC (33.3.3.3 in this case).

The current configuration does not include this required step.

Thus, the correct statement is:

D. You need to create a remote peer and specify an LSR ID for the remote peer.

The command output shows:

* > i before both networks, which means these routes are the preferred routes (*) and are learned via internal BGP (i).

Two networks are listed: 3002::3 and 3002::4, which means R1 does have these two routes in its BGP IPv6 routing table.

For 3002::4, the path origin shows 65001 i, which means this route originated from AS 65001 and was learned through IBGP.

The AS Path attribute is only shown for 3002::4, but both routes are clearly present.

Therefore, the correct conclusion is:

D. R1 has routes 3002::3/128 and 3002::4/128.