Study guide
10.4 IS-IS Database Synchronization and DIS
JNCIS-ENT Enterprise Routing and Switching Study Guide 2026 Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Junos Enterprise Fundamentals
1.1 JNCIS-ENT Exam Logistics & Blueprint Breakdown 1.2 Junos CLI, Enterprise Platforms & Interface Families 1.3 Layer 2 Bridging Mechanics & Packet Forwarding
2 Chapter 2: VLANs & Inter-VLAN Routing
2.1 VLAN Segmentation and 802.1Q Tags 2.2 Access, Trunk, Native and Voice VLANs 2.3 IRB Architecture and Interface Families 2.4 IRB Configuration and Packet Walk 2.5 VLAN Configuration, Verification & Troubleshooting
3 Chapter 3: Spanning Tree Protocols
3.1 Layer 2 Loops and Root Bridge Election 3.2 STP Costs, Port Roles, States and BPDUs 3.3 RSTP Rapid Convergence & Link Types 3.4 MSTP Architecture & Spanning Tree Operations
4 Chapter 4: Layer 2 Security & Feature Protection
4.1 Edge BPDU and Root Protection 4.2 Loop Protection and Diagnostic States 4.3 Port Security, MAC Limiting & Persistent MAC Learning 4.4 DHCP Snooping, Dynamic ARP Inspection (DAI) & IP Source Guard 4.5 Layer 2 Firewall Filters: Types, Order and Actions
5 Chapter 5: Advanced Layer 2 Features & Storm Control
5.1 Storm Control & Broadcast/Multicast Suppression 5.2 MACsec Link Security and Key Agreement 5.3 LLDP and LLDP-MED Operations & Verification
6 Chapter 6: Protocol-Independent Routing & Load Balancing
6.1 Static, Aggregate, and Generated Routes 6.2 Routing Instances and RIB Groups 6.3 Junos Load Balancing & Filter-Based Forwarding (FBF) 6.4 Martian Routes and Route Acceptance
7 Chapter 7: Junos Routing Policy & Firewall Filters
7.1 Routing Policy Framework & Term Evaluation 7.2 Prefix Lists & Route Filters 7.3 Firewall Filters & Policers
8 Chapter 8: Open Shortest Path First (OSPF) Operation
8.1 OSPF Architecture & Neighbor Adjacency Formation 8.2 OSPF Areas & LSA Types 8.3 OSPFv2 & OSPFv3 Configuration and Verification
9 Chapter 9: Advanced OSPF Features & Routing Policies
9.1 OSPF Special Area Types 9.2 Route Summarization & OSPF Authentication 9.3 OSPF Diagnostics & Common Failure Scenarios
10 Chapter 10: Intermediate System to Intermediate System (IS-IS)
10.1 IS-IS Encapsulation and NET Identity 10.2 IS-IS Levels, Areas and Default Routing 10.3 IS-IS PDU Families and Neighbor Exchange 10.4 IS-IS Database Synchronization and DIS 10.5 IS-IS Configuration, Metrics & Troubleshooting
11 Chapter 11: Border Gateway Protocol (BGP)
11.1 BGP Roles, AS Numbers and TCP Transport 11.2 EBGP/IBGP Sessions, State Machine and Messages 11.3 BGP Attributes & Junos Path Selection Algorithm 11.4 BGP Configuration & Policy Implementation 11.5 BGP Scaling with Route Reflection & Diagnostics
12 Chapter 12: IP Tunneling & High Availability
12.1 GRE & IP-IP Tunneling Architecture 12.2 Link Aggregation (LAG/LACP) & Redundant Trunk Groups (RTG) 12.3 Virtual Chassis Roles and Elections 12.4 Virtual Chassis Links, Splits and Provisioning 12.5 Routing Engine Redundancy: GRES, NSR, NSB and GR 12.6 BFD Detection and VRRP Gateway Redundancy 12.7 Unified ISSU: Requirements and Verification
10.4 IS-IS Database Synchronization and DIS
Key Takeaways Explain This Topic AI
DIS election uses higher priority then higher interface MAC/SNPA and is preemptive.
IS-IS has no backup DIS; LAN routers retain pairwise adjacencies across DIS changes.
The pseudonode reduces link-state topology representation rather than eliminating pairwise neighbor relationships.
Last updated: October 2026
2. Link-State Synchronization Workflow
Database synchronization follows distinct operational patterns depending on whether the physical medium is a point-to-point circuit or a multi-access broadcast LAN: +---------------------------------------------------------------------------------------------------+
- | POINT-TO-POINT LINK DATABASE SYNCHRONIZATION |
- | |
- | Router A Router B |
- | | | |
- | |-------- 1. Point-to-Point IIH (Initializing) -------->| |
- | |<------- 2. Point-to-Point IIH (Up) -------------------| |
- | |-------- 3. Point-to-Point IIH (Up) ------------------>| [Adjacency Established] |
- | | | |
- | |-------- 4. CSNP (Full LSDB Summary) ----------------->| |
- | |<------- 5. CSNP (Full LSDB Summary) ------------------| |
- | | | |
- | |-------- 6. PSNP (Requests missing LSP B1) ----------->| |
- | |<------- 7. Full LSP B1 -------------------------------| |
- | |-------- 8. PSNP (Explicit Acknowledgment of B1) ----->| |
- +---------------------------------------------------------------------------------------------------+
On broadcast LANs, synchronization is driven asynchronously by the periodic CSNP transmissions of the DIS:
The DIS periodically broadcasts a CSNP every 10 seconds to 01:80:C2:00:00:14 (L1) or 01:80:C2:00:00:15 (L2).
A newly joined router receives the CSNP and audits its local LSDB.
For any missing or newer LSPs advertised in the CSNP, the new router multicasts a PSNP soliciting the full LSP.
The DIS (or any other router on the segment that has the requested LSP) responds with the full LSP .
If the new router possesses an LSP that is newer than what the DIS advertised in the CSNP, the new router immediately floods its newer LSP onto the LAN, forcing the DIS and all peers to update their databases.
3. Designated Intermediate System (DIS) Mechanics
On a multi-access broadcast segment (such as an Ethernet switch interconnecting multiple routers), requiring every router to establish separate link-state adjacencies and originate individual link connections creates an N ( N − 1 ) / 2 N(N-1)/2 N ( N − 1 ) /2 scaling problem. To solve this, IS-IS elects a Designated Intermediate System (DIS) for Level 1 and a separate DIS for Level 2. +---------------------------------------------------------------------------------------------------+
- | THE PSEUDONODE CONCEPT ON BROADCAST NETWORKS |
- | |
- | Physical LAN Topology: Logical Pseudonode Topology: |
- | |
- | [Router A] [Router B] [Router A] |
- | \ / \ |
- | ============= (LAN) [Pseudonode] |
- | / \ (1921.6800.0001.01) |
- | [Router C] [Router D (DIS)] / \ |
- | [Router B] [Router C, D] |
- +---------------------------------------------------------------------------------------------------+
- The Pseudonode Concept
The DIS creates and advertises a virtual router called a Pseudonode . Instead of every router advertising connections to every other router on the segment, each router advertises a single connection to the Pseudonode with its configured link cost. The DIS then generates a Pseudonode LSP (with a non-zero Pseudonode ID, e.g., 1921.6800.0001.01-00 ) listing all routers attached to that LAN segment. This reduces the number of link advertisements in the LSDB from O ( N 2 ) O(N^2) O ( N 2 ) to O ( N ) O(N) O ( N ) .
DIS Election Criteria
Interface Priority : Values range from 0 to 127 . In Junos OS, the default priority is 64 .
Important Trap : Unlike OSPF where a priority of 0 makes a router ineligible to become DR, in IS-IS a priority of 0 is completely valid and can still become DIS if no other router has a higher priority or MAC address.
Tiebreaker : If priority values tie, the router with the highest Subnetwork Point of Attachment (SNPA) —which is the Layer 2 MAC address of the interface—wins the election.
Critical Differences: IS-IS DIS vs. OSPF DR
- Operational Feature IS-IS Designated IS (DIS) OSPF Designated Router (DR)
- Backup Role NO Backup DIS (BDIS) exists Elects a Backup Designated Router (BDR)
Preemption Strictly Preemptive : A router with higher priority immediately usurps the DIS role Non-preemptive : An active DR remains until it reboots or fails
Adjacency Structure Full mesh : All routers form full adjacencies with ALL other routers on the LAN DROthers form full adjacencies only with DR and BDR; 2-Way with each other
- Priority Range 0 to 127 (Junos default: 64) 0 to 255 (Junos default: 128)
- Priority 0 Meaning Valid priority; still eligible to become DIS Ineligible to become DR or BDR
Hello Timer on LAN DIS transmits Hellos every 3 seconds (holdtime 9s); non-DIS every 9s (holdtime 27s) DR and all routers use identical Hello timers (default 10s / Dead 40s)
Database Maintenance Periodic CSNP multicasts every 10 seconds by DIS LSU retransmissions with unicast/multicast LSAck confirmations
Why IS-IS Does Not Need a Backup DIS
In OSPF, DROthers form adjacencies only with the DR and BDR. If the DR fails and there were no BDR, all routers would have to start database synchronization from scratch, causing significant network drops. In IS-IS, all routers on the LAN form full adjacencies with one another . Every router already possesses an identical, fully synchronized LSDB. If the active DIS fails:
Non-DIS routers miss the DIS holdtime (9 seconds with default Junos timers).
The remaining routers immediately elect the new DIS based on highest priority and MAC address.
The new DIS originates a new Pseudonode LSP and multicasts a CSNP.
Existing adjacencies and databases remain, but pseudonode replacement can still trigger SPF and forwarding convergence.