IS-IS · Topic 4 of 4

Configure, Monitor and Troubleshoot IS-IS

Configure IS-IS in Junos with family iso and a NET, export and leak routes between levels with policy, and troubleshoot with show isis and traceoptions.

  • 6 min
In a nutshell
  • IS-IS needs a NET on lo0, family iso on each interface and protocols isis interface entries.
  • level 1 disable makes a Level 2 only router; point-to-point removes the DIS.
  • Export policy injects other routes; use to level to pick the level.

What it is

A working IS-IS setup in Junos needs three things: a NET on lo0, family iso on every IS-IS interface, and the interfaces listed under [edit protocols isis]. Missing any one of them is the most common reason IS-IS does not start.

Routing policy injects other routes into IS-IS (export) and leaks Level 2 routes into Level 1. Troubleshooting tools are the show isis commands, clear isis, and traceoptions.

NET on lo0plusfamily iso on interfacesplusprotocols isis interfacehellosAdjacency Up

How it works

Complete basic configuration

user@router# set interfaces lo0 unit 0 family inet address 192.168.0.1/32
user@router# set interfaces lo0 unit 0 family iso address 49.0001.1921.6800.0001.00
user@router# set interfaces ge-0/0/0 unit 0 family inet address 10.0.12.1/30
user@router# set interfaces ge-0/0/0 unit 0 family iso
user@router# set protocols isis interface ge-0/0/0.0 point-to-point
user@router# set protocols isis interface lo0.0 passive
user@router# set protocols isis level 1 disable

This router runs Level 2 only. It advertises its loopback and the link subnet, and forms one point-to-point adjacency.

Common interface options

OptionEffect
passiveAdvertise the interface prefixes, send no hellos
point-to-pointNo DIS election on Ethernet
level <n> metric <m>Interface metric for that level; default 10
level <n> priority <p>DIS priority; default 64
level <n> disableStop that level on this interface
level <n> hello-interval, hold-timeHello timers; default 9 and 27 seconds

Authentication is set per level for the whole router, or per interface:

user@router# set protocols isis level 2 authentication-key "Jn0364key" authentication-type md5

Export policy

IS-IS advertises the prefixes of its own interfaces automatically. Static, BGP and other routes need an export policy. Use to level to choose the level that receives them.

user@router# set policy-options policy-statement STATIC-TO-ISIS term 1 from protocol static
user@router# set policy-options policy-statement STATIC-TO-ISIS term 1 to level 2
user@router# set policy-options policy-statement STATIC-TO-ISIS term 1 then accept
user@router# set protocols isis export STATIC-TO-ISIS

Exported routes appear in other routers as IS-IS external routes, with preference 160 at Level 1 or 165 at Level 2.

Leaking Level 2 routes into Level 1

Level 2 routes do not enter Level 1 by default. On the L1/L2 router, an export policy with from level 2 and to level 1 leaks them:

user@router# set policy-options policy-statement L2-TO-L1 term 1 from protocol isis
user@router# set policy-options policy-statement L2-TO-L1 term 1 from level 2
user@router# set policy-options policy-statement L2-TO-L1 term 1 from route-filter 10.200.0.0/16 orlonger
user@router# set policy-options policy-statement L2-TO-L1 term 1 to level 1
user@router# set policy-options policy-statement L2-TO-L1 term 1 then accept
user@router# set protocols isis export L2-TO-L1
Level 2 routeexport policy from level 2 to level 1Level 1 LSPleaked prefixSPFL1 routerspecific route

Level 1 routers then reach 10.200.0.0/16 through the best L1/L2 router for that prefix, not just the nearest attached one.

Import policy

An IS-IS import policy controls which IS-IS routes are installed in the local routing table. Like OSPF, it does not remove LSPs from the database or stop them from being flooded. Apply it with set protocols isis import <policy>.

ExportImport
DirectionRouting table into IS-IS, or Level 2 into Level 1IS-IS into the routing table
DefaultOnly IS-IS interface prefixes are advertisedAccept all
Effect on LSDBAdds prefixes to LSPsNone

Monitoring commands

CommandShows
show isis adjacencyNeighbors, level, state, hold time, SNPA
show isis adjacency detailArea addresses, IP addresses and why an adjacency is up or down
show isis interfaceIS-IS interfaces, DIS per level, metric per level
show isis databaseLSPs per level
show isis routeRoutes calculated by IS-IS
show route protocol isisIS-IS routes active in inet.0
show isis spf logWhen SPF ran and what triggered it
show isis statisticsPDU counters, including errors

Clearing and tracing

clear isis adjacency resets adjacencies; name a neighbor to reset only one.

user@router# set protocols isis traceoptions file isis-trace size 1m files 3
user@router# set protocols isis traceoptions flag hello detail
user@router# set protocols isis traceoptions flag error detail
user@router# commit

user@router> show log isis-trace
user@router> monitor start isis-trace

The lsp and spf flags trace flooding and SPF runs.

A troubleshooting order

No adjacencycheckfamily iso on both endscheckNET on lo0checkInterface listed in isisnot passiveInterface listed in isischeckLevel and areacheckAuthentication and MTUtrace hello and errorAdjacency Up but route missingcheckshow isis database extensivecheckExport or leak policy
SymptomLikely cause
No adjacency, no hellos sentNo family iso on the interface, or no NET on lo0
Level 2 up, Level 1 missingDifferent area IDs, or Level 1 disabled
Adjacency stuck InitializingHellos one way only, authentication mismatch, or MTU problem
Static route not seen elsewhereNo export policy, or wrong to level
Exam tip

show isis adjacency detail shows the neighbor's area addresses. Comparing them with your own NET quickly explains a missing Level 1 adjacency.

Common mistakes

Configuring family iso on lo0 only. Every IS-IS interface needs family iso, or it sends no hellos.

Expecting Level 2 routes in Level 1 without policy. Leaking needs from level 2 and to level 1 in an export policy on the L1/L2 router.

Watch out

An export policy with a bare then accept and no from sends every active route, including full BGP tables, into IS-IS. Always match a protocol or prefix list.

What to remember for the exam

  • IS-IS needs a NET on lo0, family iso on each interface and protocols isis interface entries.
  • level 1 disable makes a Level 2 only router; point-to-point removes the DIS.
  • Export policy injects other routes; use to level to pick the level.
  • Leak Level 2 into Level 1 with from level 2 and to level 1 on the L1/L2 router.
  • Import policy changes only the routing table, not the LSDB.
  • Tools: show isis adjacency, interface, database, route, spf log, statistics; clear isis adjacency; traceoptions with hello and error flags.

Check yourself

  • An interface is listed under protocols isis and has an IPv4 address, but no adjacency forms and no hellos are sent. What is the likely cause?

    The interface has no family iso, which IS-IS needs to send its PDUs.

  • Which policy terms leak Level 2 routes into Level 1?

    An export policy on the L1/L2 router with from protocol isis, from level 2, to level 1 and then accept.

  • Which command shows when SPF ran and what triggered it?

    show isis spf log.

Topic 4 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.