Question 220
An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. What assessment accurately links the fault to its correction?
Explanation
Correct Answer
Because rSVP-TE path choice can account for configured topology constraints and resources, the best response is to review explicit-path or constraint-based RSVP traffic-engineering intent. A reviewer can close the technical case only after confirming that the installed LSP avoids the prohibited link in a failure-free test.
Incorrect Answers
That result would be useful for a different failure, namely: An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. The current case specifically calls for: Review explicit-path or constraint-based RSVP traffic-engineering intent. The required observed result is: The installed LSP avoids the prohibited link in a failure-free test.
Inspect local preference, export/import inheritance and selected BGP path attributes is a relevant step for the separate scenario in which a policy change unexpectedly makes a backup transit provider carry most outbound traffic. It does not directly fix this case. Instead review explicit-path or constraint-based RSVP traffic-engineering intent; verify: The installed LSP avoids the prohibited link in a failure-free test.
The alternative addresses an MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition, not the present root cause. Here the selected correction must reflect rSVP-TE path choice can account for configured topology constraints and resources. Test for: The installed LSP avoids the prohibited link in a failure-free test.