IS-IS · Topic 1 of 4
IS-IS PDUs, TLVs and the Link-State Database
Learn IS-IS hello, LSP, CSNP and PSNP PDUs, the key TLVs, LSP IDs, sequence numbers and the 1200 second lifetime, and show isis database for the JN0-364.
- 5 min
- PDUs: hello (IIH), LSP, CSNP, PSNP; carried directly in Layer 2 frames.
- CSNP lists every LSP; PSNP requests or acknowledges specific LSPs.
- The DIS sends CSNPs on a LAN, every 10 seconds by default.
What it is
IS-IS routers exchange protocol data units (PDUs). Hellos build adjacencies, link-state PDUs (LSPs) describe each router and its links, and sequence number PDUs (SNPs) keep databases in sync. IS-IS PDUs are carried directly in Layer 2 frames, not inside IP packets.
The contents of each PDU are built from TLVs (type, length, value). New features are added as new TLVs, so IS-IS carries IPv4, IPv6 and traffic engineering information without changing the protocol itself. All LSPs together form the link-state database, one per level.
How it works
PDU types
| PDU | Type numbers | Purpose |
|---|---|---|
| IS-IS hello (IIH) | 15 LAN Level 1, 16 LAN Level 2, 17 point-to-point | Discover neighbors and keep adjacencies alive |
| Link-state PDU (LSP) | 18 Level 1, 20 Level 2 | Describe a router's adjacencies and prefixes |
| Complete SNP (CSNP) | 24 Level 1, 25 Level 2 | List the headers of every LSP in the database |
| Partial SNP (PSNP) | 26 Level 1, 27 Level 2 | Request missing LSPs or acknowledge received ones |
On a point-to-point link there is a single hello type for both levels. On a LAN, Level 1 and Level 2 hellos are separate.
How SNPs keep the database in sync
On a LAN, the DIS sends a CSNP periodically, every 10 seconds by default. Each router compares the list with its own database. If it is missing an LSP or holds an older copy, it sends a PSNP asking for it. If it holds a newer copy, it floods that LSP.
On a point-to-point link, CSNPs are exchanged when the adjacency comes up and Junos repeats them every 5 seconds by default. Each LSP is acknowledged with a PSNP.
| LAN | Point-to-point | |
|---|---|---|
| CSNP | Sent periodically by the DIS | Sent at adjacency up, then every 5 seconds in Junos |
| PSNP | Requests missing LSPs | Acknowledges each LSP, and requests missing ones |
| LSP acknowledgment | Implicit, through the next CSNP | Explicit, with a PSNP |
LSP identifiers
Every LSP has an ID made of three parts: the 6-byte system ID, a pseudonode ID and a fragment number. Junos shows the system ID as the hostname when dynamic hostname TLV 137 is received.
| LSP ID | Meaning |
|---|---|
R1.00-00 | Router R1, its own LSP, first fragment |
R1.00-01 | Router R1, second fragment |
R2.02-00 | A pseudonode LSP for a LAN where R2 is DIS |
A nonzero pseudonode ID always means a LAN pseudonode created by the DIS.
Sequence numbers and lifetime
Each LSP carries a sequence number and a remaining lifetime. A higher sequence number is newer. The lifetime counts down, unlike the OSPF age, which counts up.
The Junos default LSP lifetime is 1200 seconds. The originating router refreshes its LSPs before they expire. An LSP whose lifetime reaches zero is purged from the database.
Common TLVs
| TLV | Name | Carries |
|---|---|---|
| 1 | Area addresses | The area IDs of the router |
| 2 | IS reachability | Neighbors with narrow metrics |
| 6 | IS neighbors | MAC addresses of neighbors seen on a LAN, in hellos |
| 8 | Padding | Fills hellos to the full MTU |
| 10 | Authentication | Authentication data |
| 22 | Extended IS reachability | Neighbors with wide metrics, plus traffic engineering sub-TLVs |
| 128 | IP internal reachability | IPv4 prefixes with narrow metrics |
| 129 | Protocols supported | IPv4, IPv6 or both |
| 130 | IP external reachability | External IPv4 prefixes with narrow metrics |
| 132 | IP interface address | The router's IPv4 interface addresses |
| 135 | Extended IP reachability | IPv4 prefixes with wide metrics |
| 137 | Dynamic hostname | The router's host name |
| 232 | IPv6 interface address | The router's IPv6 interface addresses |
| 236 | IPv6 reachability | IPv6 prefixes |
TLV 22 and TLV 135 are the "wide metric" TLVs. They are needed for traffic engineering, because TE information rides in sub-TLVs of TLV 22.
Viewing the database
This router runs Level 2 only, so its Level 1 database is empty (output trimmed).
user@router> show isis database
IS-IS level 1 link-state database:
0 LSPs
IS-IS level 2 link-state database:
LSP ID Sequence Checksum Lifetime
R1.00-00 0x1c 0x5e3b 1043
R2.00-00 0x21 0x3a17 988
R2.02-00 0x9 0x8c41 988
3 LSPs
| Command | Use |
|---|---|
show isis database | LSP IDs, sequence numbers and remaining lifetime per level |
show isis database extensive | Every TLV inside each LSP |
show isis database R2.00-00 detail | One router's LSP, with its neighbors and prefixes |
show isis hostname | The system ID to hostname mapping |
show isis statistics | Counters for each PDU type |
show isis database extensive is the place to confirm what a router really advertises, such as wide metrics, an overload bit or a leaked prefix. Read the TLVs, not just the route table.
Common mistakes
Assuming IS-IS runs over IP. It runs directly over Layer 2 with ISO addressing. A firewall filter on family inet does not see IS-IS PDUs.
Reading lifetime as age. IS-IS lifetime counts down to zero; OSPF LSA age counts up to MaxAge.
Thinking a pseudonode is a real router. An LSP ID with a nonzero pseudonode number is generated by the DIS to represent the LAN.
IS-IS keeps a separate database for each level. A Level 1 only router has no Level 2 database entries, and a Level 2 only router has no Level 1 entries.
What to remember for the exam
- PDUs: hello (IIH), LSP, CSNP, PSNP; carried directly in Layer 2 frames.
- CSNP lists every LSP; PSNP requests or acknowledges specific LSPs.
- The DIS sends CSNPs on a LAN, every 10 seconds by default.
- LSP ID: system ID, pseudonode ID, fragment number; nonzero pseudonode ID means a LAN pseudonode.
- Higher sequence number is newer; lifetime counts down; Junos default lifetime 1200 seconds.
- Key TLVs: 1 area, 22 extended IS reachability, 128 and 135 IP reachability, 137 hostname, 236 IPv6.
- One link-state database per level;
show isis database extensiveshows the TLVs.
Check yourself
Which PDU does the DIS send periodically on a LAN to keep databases in sync?
The CSNP, which lists the headers of every LSP in the database.
What does the LSP ID
R2.02-00represent?The pseudonode LSP for a LAN where R2 is the DIS, first fragment.
Which TLV carries IPv4 prefixes with wide metrics?
TLV 135, extended IP reachability.
Topic 1 of 4 in IS-IS
Test yourself on IS-IS
The full Juniper JNCIS-SP JN0-364 question bank has 860 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.