Question 300
A Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. Which protocol behavior most directly determines the correct diagnosis?
Explanation
Correct Answer
Correct diagnosis: An operational interface is not evidence of matching IS-IS protocol configuration. The appropriate action is: Inspect IS-IS interface enablement, levels, area identifiers and link type. The follow-up evidence required is: The corrected circuit shows the expected neighbor and link-state entries.
Incorrect Answers
That result would be useful for a different failure, namely: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. The current case specifically calls for: Inspect IS-IS interface enablement, levels, area identifiers and link type. The required observed result is: The corrected circuit shows the expected neighbor and link-state entries.
This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: The corrected circuit shows the expected neighbor and link-state entries. The relevant action is: Inspect IS-IS interface enablement, levels, area identifiers and link type.
Compare area, interface mode, timers, authentication and physical status on both endpoints is a relevant step for the separate scenario in which a new OSPF uplink remains down at the adjacency stage after a router replacement. It does not directly fix this case. Instead inspect IS-IS interface enablement, levels, area identifiers and link type; verify: The corrected circuit shows the expected neighbor and link-state entries.