IS-IS · Topic 1 of 4
IS-IS Link State Database, PDUs and TLVs
Learn the IS-IS NET address, per level link state database, hello, LSP, CSNP and PSNP PDU types and the TLVs that carry IS-IS information for JN0-352.
- 6 min
- A NET has area, 6 byte system ID and an NSEL of 00.
family isois required onlo0and on each IS IS interface.- There is a separate LSDB for Level 1 and Level 2.
What it is
IS IS is a link state protocol. Each router, called an intermediate system (IS), describes its links and prefixes in a link state PDU (LSP) and floods it to the other routers. Each router keeps the LSPs in a link state database (LSDB) and runs the shortest path first algorithm on it.
IS IS PDUs are not IP packets. They are carried directly in layer 2 frames, as part of the OSI protocol suite. The data inside is built from type, length, value (TLV) fields.
How it works
The NET
Every IS IS router has a network entity title (NET), which gives its area and its system ID. It is configured as an address on the loopback interface in the ISO family.
user@R1# set interfaces lo0 unit 0 family iso address 49.0001.0102.5500.0001.00
| Part | Example | Meaning |
|---|---|---|
| Area ID | 49.0001 | AFI 49 (private addressing) and the area number; 1 to 13 bytes |
| System ID | 0102.5500.0001 | 6 bytes, unique in the domain, often a padded loopback address |
| NSEL | 00 | The selector; always 00 for a router |
The system ID must be unique for every router. Routers in the same area share the area ID.
Each interface that runs IS IS also needs family iso:
user@R1# set interfaces ge-0/0/1 unit 0 family inet address 10.1.1.1/30
user@R1# set interfaces ge-0/0/1 unit 0 family iso
A missing family iso on the interface or on lo0 is the most common reason IS IS does nothing on Junos OS. There is no error; the interface simply does not take part.
The link state database
IS IS keeps one LSDB for Level 1 (inside the area) and a separate one for Level 2 (between areas). A router in both levels holds two databases.
An LSP is identified by an LSP ID with three parts: the system ID, a pseudonode ID and a fragment number, such as R1.00-00. The .00 pseudonode ID means a real router. A non-zero value, such as R1.02-00, is a pseudonode LSP created by the DIS for a LAN (see the next page).
Each LSP also carries a sequence number (higher is newer) and a remaining lifetime. The Junos default lifetime is 1200 seconds, and the originator refreshes the LSP before it expires.
user@R1> show isis database
IS-IS level 1 link-state database:
LSP ID Sequence Checksum Lifetime Attributes
R1.00-00 0x8 0x2b1c 1112 L1 L2
R2.00-00 0x6 0x8f40 1098 L1 L2
R2.02-00 0x2 0x5a77 1098 L1 L2
Use show isis database extensive to see the TLVs inside each LSP. The Attributes column shows the levels.
The PDU types
| PDU | Level 1 type | Level 2 type | Purpose |
|---|---|---|---|
| IS to IS hello (IIH) | 15 (LAN) | 16 (LAN) | Discover neighbors on a broadcast link |
| Point to point hello | 17 | 17 | Discover the neighbor on a point to point link |
| Link state PDU (LSP) | 18 | 20 | Carry the topology and prefix information |
| Complete sequence number PDU (CSNP) | 24 | 25 | List every LSP in the database |
| Partial sequence number PDU (PSNP) | 26 | 27 | Acknowledge LSPs or request missing ones |
How the database is kept in step differs by link type.
- Broadcast link: the DIS sends a CSNP every 10 seconds. A router that sees an LSP missing or old from the CSNP answers with a PSNP request.
- Point to point link: a CSNP is sent once, when the adjacency comes up. After that each LSP is acknowledged with a PSNP.
IS IS hellos are padded with extra bytes up to the interface MTU by default, at least while the adjacency forms. A neighbor whose MTU is smaller cannot receive them, which makes an MTU mismatch show up as a failed adjacency. Junos controls this with the interface statement hello-padding (loose, strict, adaptive or disable).
The TLVs
An LSP is a header followed by a series of TLVs. Each TLV has a type number, a length and a value. A router that does not know a TLV type ignores it.
| TLV | Name | Carries |
|---|---|---|
| 1 | Area addresses | The areas of the router |
| 2 | IS neighbors (narrow) | Adjacent routers with a 6 bit metric |
| 22 | Extended IS reachability | Adjacent routers with a 24 bit metric (wide) |
| 128 | IP internal reachability | IPv4 prefixes, 6 bit metric |
| 130 | IP external reachability | IPv4 prefixes from other protocols, 6 bit metric |
| 135 | Extended IP reachability | IPv4 prefixes with a 32 bit metric (wide) |
| 129 | Protocols supported | Which network protocols (IPv4, IPv6) the router can route |
| 137 | Dynamic hostname | The router name shown instead of the system ID |
| 232 | IPv6 interface address | Interface IPv6 addresses |
| 236 | IPv6 reachability | IPv6 prefixes |
The TLVs 2, 128 and 130 are the narrow metric set, and 22 and 135 are the wide metric set. Both are in the exam, because the choice affects what metrics you can configure (see the metrics page).
One IS IS process carries IPv4 and IPv6 routes. There is no separate IS IS for IPv6, because TLVs 232 and 236 add IPv6 to the same LSPs.
Common mistakes
Forgetting family iso. IS IS needs it on lo0 for the NET and on every IS IS interface.
Giving two routers the same system ID. The LSPs overwrite each other. Area IDs may repeat, system IDs may not.
What to remember for the exam
- A NET has area, 6 byte system ID and an NSEL of 00.
family isois required onlo0and on each IS IS interface.- There is a separate LSDB for Level 1 and Level 2.
- LSP ID format is system ID, pseudonode ID, fragment number; pseudonode ID 00 is a router.
- PDUs: IIH (15, 16, 17), LSP (18, 20), CSNP (24, 25), PSNP (26, 27).
- DIS sends CSNPs every 10 seconds on a LAN; on point to point a CSNP is sent once.
show isis database extensiveshows the LSPs and TLVs.
Check yourself
In the NET
49.0002.0102.5500.0003.00, what is the system ID?0102.5500.0003, the 6 bytes before the final 00 selector.What is the difference between a CSNP and a PSNP?
A CSNP lists all LSPs in the database for synchronization, while a PSNP lists some LSPs to acknowledge or request them.
Why does an IPv4 firewall filter that drops OSPF not affect IS IS?
IS IS PDUs are carried directly over layer 2 and are not IP packets, so an inet filter does not match them.
Topic 1 of 4 in IS-IS
Test yourself on IS-IS
The full Juniper JNCIS-ENT JN0-352 question bank has 846 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.