Question 170
A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which root-cause explanation and corrective action fit the case?
Explanation
Correct Answer
This option addresses the stated case rather than another networking issue. Principle: IS-IS packet exchange and transport differ from OSPF over IP. Remedy: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Proof: A link-level packet trace observes the relevant IS-IS PDUs.
Incorrect Answers
IPv4 BGP session liveness does not prove IPv6 family route exchange describes a neighboring protocol concern. In this case the controlling fact is iS-IS packet exchange and transport differ from OSPF over IP. A correct remediation would recognize IS-IS as a link-layer routing protocol with its own PDUs and demonstrate: A link-level packet trace observes the relevant IS-IS PDUs.
The proposed principle concerns another network fault: IS-IS advertises extensible routing attributes using TLV-encoded fields. Here, iS-IS packet exchange and transport differ from OSPF over IP. The most direct correction is to recognize IS-IS as a link-layer routing protocol with its own PDUs, confirmed by a link-level packet trace observes the relevant IS-IS PDUs.
That result would be useful for a different failure, namely: An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. The current case specifically calls for: Recognize IS-IS as a link-layer routing protocol with its own PDUs. The required observed result is: A link-level packet trace observes the relevant IS-IS PDUs.