Question 650
After fixing the following network problem, what should the team verify: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive.
Explanation
Correct Answer
LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs. This confirms the approved response: Align authorized LDP session authentication and transport addresses on the intended peers. It is relevant because: LDP discovery and its subsequent transport session are separate stages with independent failure conditions.
Incorrect Answers
The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This would validate ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.
The test isolates a healthy transport LSP from a missing inner VPN route or label binding. This would validate ANOTHER scenario: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. The specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.
A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table. This would validate ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. The specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.