Refer to the exhibit. MPLS traffic from the packet core that is connected to router RX (10.10.10.1) to the radio network that is connected to router RB (10.10.10.6) uses the longer route RB R2 RY RX…

Question

Exhibit

Options

• ARX(config)#mpls ldp holdtime 30
• BRZ(config)#interface FastEthernet0/0 RZ(config)#mpls ldp discovery transport-address 10.10.10.6
• CRZ(config)#interface FastEthernet0/0 RZ(config)#mpls ldp discovery transport-address 10.10.10.1
• DRX(config)#mpls ldp neighbor 10.10.10.6 targeted ldp

• A
  7% (3)
• B
  78% (32)
• C
  12% (5)
• D
  2% (1)

Explanation

LDP establishes a TCP session between peers using their configured transport addresses (typically loopback addresses). When two LDP routers are directly connected, LDP first discovers neighbors via UDP hellos on the link-local subnet, then initiates a TCP session using the transport addresses advertised in those hellos. If the transport address on a directly connected interface of RZ does not match what is expected by the neighbor on the shortest path, LDP may fail to establish a session over that link and instead use an alternative (longer) path. By configuring mpls ldp discovery transport-address 10.10.10.6 on RZ's FastEthernet0/0, RZ advertises 10.10.10.6 (RB's loopback) as the transport address on that segment, allowing LDP to properly establish a session over the direct link, enabling MPLS label switching along the shortest path. Option A (changing holdtime on RX) does not address a transport address mismatch. Option C uses the wrong address (10.10.10.1 belongs to RX, not the intended next-hop). Option D (targeted LDP) is for non-directly-connected peers and would not resolve a direct-link discovery issue.

No community discussion yet for this question.