IS-IS · Topic 3 of 4
IS-IS Metrics and Basic Configuration
Learn IS-IS metrics (default 10, narrow and wide) and configure IS-IS on Junos: NET, family iso, levels, interfaces, authentication, overload.
- 6 min
- Default metric is 10 on every interface; the sum along the path is the cost.
- Narrow metrics: 63 per interface, 1023 per path. Junos sends narrow and wide TLVs by default;
wide-metrics-onlydrops the narrow ones and needs every router in the level to support wide metrics. - Preference: L1 internal 15, L2 internal 18, L1 external 160, L2 external 165.
What it is
IS IS chooses the path with the lowest total metric. In Junos OS the metric is a simple configured cost per interface, with a default of 10 on every interface. The speed of the link is not used unless you set a reference bandwidth.
This page also covers the working configuration: the NET on the loopback, family iso on interfaces, the protocols isis hierarchy, and the options the exam expects, such as passive interfaces, authentication and the overload bit.
How it works
Metrics
The default metric is 10 for every interface, no matter the speed. A path of three links costs 30. To prefer a link, give it a lower metric, per level:
user@R1# set protocols isis interface ge-0/0/1.0 level 1 metric 5
user@R1# set protocols isis interface ge-0/0/1.0 level 2 metric 5
The metric of a path is the sum of the interface metrics along it.
IS IS has two metric formats.
| Narrow metrics | Wide metrics | |
|---|---|---|
| Interface metric | 6 bits, maximum 63 | 24 bits |
| Total path metric | 10 bits, maximum 1023 | 32 bits |
| TLVs | 2, 128, 130 | 22, 135 |
Junos sends both narrow and wide TLVs by default, and a metric above 63 is carried in full only in the wide ones. wide-metrics-only stops the narrow TLVs. Use it only when every router in the level understands wide metrics, or the topology breaks.
user@R1# set protocols isis level 1 wide-metrics-only
user@R1# set protocols isis level 2 wide-metrics-only
Setting reference-bandwidth under protocols isis makes Junos calculate the interface metric from the link speed instead of using 10. As with OSPF, set it the same on every router.
Preference
IS IS routes enter the routing table with these default preferences: Level 1 internal 15, Level 2 internal 18. The external route preferences are higher: Level 1 external 160 and Level 2 external 165. A Level 1 route therefore beats a Level 2 route to the same prefix, no matter the metric, and both beat OSPF external (150) but lose to OSPF internal (10).
Basic configuration
user@R1# set interfaces lo0 unit 0 family inet address 10.255.0.1/32
user@R1# set interfaces lo0 unit 0 family iso address 49.0001.0102.5500.0001.00
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
user@R1# set protocols isis interface ge-0/0/1.0 point-to-point
user@R1# set protocols isis interface lo0.0 passive
user@R1# commit
What each line does:
- The NET goes on
lo0infamily iso. One NET is enough. family isoon the interface lets it carry IS IS PDUs.interface ge-0/0/1.0turns IS IS on for that link. With no level configured, it runs Level 1 and Level 2.point-to-pointavoids the DIS election on a two router link.lo0.0is advertised, but it sends no hellos because it is passive. In IS IS the loopback address is advertised through its interface; there is no separate network statement.
To make a router Level 2 only:
user@R1# set protocols isis level 1 disable
Additional basic options
| Option | Purpose |
|---|---|
level 1 disable, level 2 disable | Restrict the router or an interface to one level |
passive | Advertise an interface but form no adjacency on it |
point-to-point | Treat a LAN interface as a point to point link |
level <n> priority | DIS priority on an interface; default 64 |
level <n> metric | Interface metric for a level; default 10 |
hello-padding | Control padding of hellos to the MTU (disable turns it off) |
authentication-type and authentication-key | Authenticate the LSPs and sequence number PDUs for a level (simple or MD5) |
overload | Advertise the router as overloaded so others avoid it for transit |
bfd-liveness-detection | Detect link failure faster than the 27 second hold time |
ignore-attached-bit | Do not install a default route from the attached bit |
lsp-lifetime | Lifetime of the LSPs this router originates; default 1200 seconds |
Authentication on a level:
user@R1# set protocols isis level 2 authentication-key "S3cret"
user@R1# set protocols isis level 2 authentication-type md5
All routers in a level must use the same key and type. A mismatch drops the LSPs and sequence number PDUs, so the databases never agree. Hello authentication is configured per interface.
The overload bit tells other routers not to use this one as a transit path, while its own connected routes stay reachable. It is useful before maintenance:
user@R1# set protocols isis overload
Monitoring
user@R1> show isis adjacency
user@R1> show isis interface
user@R1> show isis database
user@R1> show isis route
user@R1> show route protocol isis
show isis adjacency is the first check. show isis interface shows the levels, metrics and DIS. show isis route shows the SPF results.
When you configure IS IS, check four things before anything else: the NET on lo0, family iso on every IS IS interface, the same levels on both ends and the same area for Level 1.
Common mistakes
Missing family iso. The interface is silent. This is the first thing to check.
Mixing narrow and wide metrics. If only some routers use wide-metrics-only, they stop agreeing on the topology.
Forming adjacencies on the loopback. Mark lo0.0 as passive, so it is advertised and sends no hellos.
Narrow metrics stop at 63 per interface. If a larger metric does not give the result you expect, check that every router in the level reads the wide TLVs.
What to remember for the exam
- Default metric is 10 on every interface; the sum along the path is the cost.
- Narrow metrics: 63 per interface, 1023 per path. Junos sends narrow and wide TLVs by default;
wide-metrics-onlydrops the narrow ones and needs every router in the level to support wide metrics. - Preference: L1 internal 15, L2 internal 18, L1 external 160, L2 external 165.
- Configuration needs the NET on
lo0andfamily isoon every IS IS interface. passivefor the loopback,point-to-pointfor two router links.overloadstops transit use; authentication must match per level.
Check yourself
A path crosses three IS IS links with default settings. What is the metric?
30, because the default metric is 10 on every interface and the path metric is the sum.
Which preference does a Level 1 IS IS route have, and does it beat a Level 2 route to the same prefix?
15, and yes, because Level 1 (15) is more preferred than Level 2 (18).
An interface is configured under
protocols isisbut no adjacency forms and there is no error. What do you check first?Whether
family isois configured on that interface.
Topic 3 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.