Question 200
For a regional peering-exchange operator, the change record describes: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. What preventive validation should be standard?
Explanation
Correct Answer
Validate explicit-route hops against TE capability data before committing. This helps prevent recurrence of the issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Acceptance evidence should be: RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.
Incorrect Answers
Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.
Include TE database completeness checks during IGP maintenance. That is a sensible control for ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.
Check IGP and LDP FEC consistency at every interregion boundary. That is a sensible control for ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.