Question 550
An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. Which change best corrects the failure without losing the intended design?
Explanation
Correct Answer
This is the model-intended best choice because structured protocol-layer evidence separates link health from routing convergence issues. The targeted correction is to collect protocol adjacency, LSP and routing-table outputs for the affected route. Validate it by observing that the report explains the fault from interface through neighbor to selected route.
Incorrect Answers
Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead collect protocol adjacency, LSP and routing-table outputs for the affected route; verify: The report explains the fault from interface through neighbor to selected route.
The alternative addresses a router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view, not the present root cause. Here the selected correction must reflect structured protocol-layer evidence separates link health from routing convergence issues. Test for: The report explains the fault from interface through neighbor to selected route.
This answer would be more suitable when a route reflector receives a new branch prefix but one iBGP client never learns it, where the corrective action is to check client definitions, route-reflector session state and export policy. The failure here is different: Structured protocol-layer evidence separates link health from routing convergence issues. Required validation: The report explains the fault from interface through neighbor to selected route.