Question 360
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An LDP session remains established but its transport prefix FEC changes next hop after an IGP metric update. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: An LDP session remains established but its transport prefix FEC changes next hop after an IGP metric update. The most directly supported response is: Check that newly selected routes still resolve through the correct downstream label bindings. Technical basis: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Evidence of success: The LFIB switches labels consistently with the updated IGP shortest path. Ongoing protection: Correlate IGP changes with LFIB programming and packet-loss metrics.
Incorrect Answers
Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. Maintaining that control would not track the failure described here. The relevant risk is: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.
An SRTE policy is usable only when its segment instructions resolve through supported topology. Maintaining that control would not track the failure described here. The relevant risk is: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.
An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. Maintaining that control would not track the failure described here. The relevant risk is: LDP label mappings are tied to FECs while forwarding next hops follow routed reachability. Review this instead: Correlate IGP changes with LFIB programming and packet-loss metrics.