Question 320
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS PE advertises VPN routes while its core LDP neighbors have not formed, so VPN packets are dropped inside the provider backbone. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: An MPLS PE advertises VPN routes while its core LDP neighbors have not formed, so VPN packets are dropped inside the provider backbone. The most directly supported response is: Restore supported LDP neighbor discovery and label exchange across the transport path before enabling service traffic. Technical basis: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. Evidence of success: Hop-by-hop LFIB entries exist along the route and test VPN packets reach the remote PE. Ongoing protection: Check LDP session state and outgoing-label resolution during PE activation.
Incorrect Answers
That recurring practice manages a separate exposure: SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. The present case instead depends on: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The suitable ongoing safeguard is: Check LDP session state and outgoing-label resolution during PE activation.
That recurring practice manages a separate exposure: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The present case instead depends on: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The suitable ongoing safeguard is: Check LDP session state and outgoing-label resolution during PE activation.
SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. Maintaining that control would not track the failure described here. The relevant risk is: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. Review this instead: Check LDP session state and outgoing-label resolution during PE activation.