Question 90
A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. Which technical explanation and controlled action address the symptom?
Explanation
Correct Answer
This is the model-intended best choice because end-to-end signaling state alone cannot pinpoint a data-plane label failure. The targeted correction is to collect hop-local LFIB, label forwarding and interface counters along the LSP. Validate it by observing that the corrected transit hop forwards the expected incoming label to its planned outgoing label.
Incorrect Answers
Labels are generally meaningful within the forwarding context where they are allocated describes a neighboring protocol concern. In this case the controlling fact is end-to-end signaling state alone cannot pinpoint a data-plane label failure. A correct remediation would collect hop-local LFIB, label forwarding and interface counters along the LSP and demonstrate: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
That result would be useful for a different failure, namely: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. The current case specifically calls for: Collect hop-local LFIB, label forwarding and interface counters along the LSP. The required observed result is: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
This response would target a different source scenario: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. It cannot establish the current acceptance requirement, which is: The corrected transit hop forwards the expected incoming label to its planned outgoing label. The relevant action is: Collect hop-local LFIB, label forwarding and interface counters along the LSP.