Question 420
An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. What observable result most directly verifies the intended configuration?
Explanation
Correct Answer
Because label-switching errors can occur even when control-plane endpoint reachability is good, the best response is to inspect the incoming label, outgoing label and interface on each affected LSR. A reviewer can close the technical case only after confirming that the repaired hop has the expected swap operation and carries a test packet.
Incorrect Answers
That result would be useful for a different failure, namely: A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. The current case specifically calls for: Inspect the incoming label, outgoing label and interface on each affected LSR. The required observed result is: The repaired hop has the expected swap operation and carries a test packet.
Distinguish the MPLS shim label stack from the encapsulated payload is a relevant step for the separate scenario in which an operator expects an MPLS label to represent an entire customer IP packet header. It does not directly fix this case. Instead inspect the incoming label, outgoing label and interface on each affected LSR; verify: The repaired hop has the expected swap operation and carries a test packet.
The alternative addresses two BGP paths have different local preferences and a technician expects the shorter AS path always to win, not the present root cause. Here the selected correction must reflect label-switching errors can occur even when control-plane endpoint reachability is good. Test for: The repaired hop has the expected swap operation and carries a test packet.