Question 340
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS data path shows a valid local label while the downstream label lookup points to a missing outgoing interface. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: An MPLS data path shows a valid local label while the downstream label lookup points to a missing outgoing interface. The most directly supported response is: Trace the LFIB and IGP next-hop mapping to repair the underlying transport path. Technical basis: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. Evidence of success: Each hop has an eligible outgoing label operation and egress reachability. Ongoing protection: Verify LFIB consistency after routing reconvergence and line-card restart.
Incorrect Answers
The alternative guards against: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. The root condition for this case is: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The focused prevention check is: Verify LFIB consistency after routing reconvergence and line-card restart.
The alternative guards against: Path computation depends on the attributes advertised or otherwise provided to its topology database. The root condition for this case is: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The focused prevention check is: Verify LFIB consistency after routing reconvergence and line-card restart.
That recurring practice manages a separate exposure: TE affinity constraints select links according to defined administrative groups. The present case instead depends on: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The suitable ongoing safeguard is: Verify LFIB consistency after routing reconvergence and line-card restart.