Question 600
For a carrier automation platform team, the change record describes: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. What preventive validation should be standard?
Explanation
Correct Answer
Verify data-plane steering separately from RSVP session state. This helps prevent recurrence of the issue: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. Acceptance evidence should be: FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.
Incorrect Answers
Inspect protection flags and test actual repair behavior instead of assuming FRR is armed. That is a sensible control for ANOTHER scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.
Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.
Include crossregion label-stack tracing in service acceptance. That is a sensible control for ANOTHER scenario: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.