Huawei's IS-IS implementation distinguishes the CSNP behavior on broadcast and point-to-point links. A DIS periodically sends CSNP summaries on broadcast networks, but P2P adjacencies still exchange CSNPs during initial database synchronization. After comparing the received complete list of LSP headers with its own LSDB, a router can use PSNPs to request missing information or acknowledge LSPs. The absence of periodic DIS-based CSNP flooding on P2P links does not mean that CSNPs are never exchanged. Hence the assertion that P2P synchronization does not need CSNPs is false.
Technical Deep Dive:
B is FALSE. IS-IS uses Hellos to establish adjacency, LSPs to disseminate link-state information, and SNPs to compare or request database information. A CSNP provides a complete summary of known LSPs; PSNPs carry partial summaries, requests or acknowledgments depending on link context. On a P2P link, the two routers exchange CSNPs when the adjacency is initially established so they can identify differing LSP content. Missing or stale LSPs are requested or refreshed through the appropriate PSNP and LSP exchange. P2P links do not elect a DIS and thus lack the periodic DIS behavior seen on multiaccess LANs. But the absence of a DIS is not proof that CSNP is unnecessary at adjacency setup. This is an important exam-key correction: the intended statement is false under Huawei's documented P2P LSDB synchronization procedure.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit