IS-IS · Topic 4 of 4

IS-IS Routing Policy and Troubleshooting Tools

Learn IS-IS import and export policy and route leaking between levels on Junos, and troubleshoot with ping, traceroute, traceoptions and logs for JN0-352.

  • 6 min
In a nutshell
  • Export policy puts external routes into IS IS and leaks routes between levels.
  • Leaking Level 2 into Level 1 needs from level 2 and to level 1 in an export policy.
  • Import policy changes only the local routing table, not the LSDB.

What it is

Routing policy in IS IS decides which routes enter IS IS from other sources, which IS IS routes move between levels, and which IS IS routes enter the routing table. The two policy points are export and import, both set under protocols isis.

Troubleshooting tools are the commands and logs for finding out why an adjacency is down, why a route is missing or why traffic takes the wrong path.

Static or direct routeexport policy acceptsIS ISexternal route in LSPflooded toOther routersLevel 2 routesexport policy from level 2 to level 1Level 1 area

How it works

Export policy

IS IS advertises the interfaces that run IS IS. Routes from another source, such as static, direct or OSPF, are not advertised unless an export policy accepts them.

user@R1# set policy-options policy-statement STATIC-TO-ISIS term 1 from protocol static
user@R1# set policy-options policy-statement STATIC-TO-ISIS term 1 from route-filter 192.168.0.0/16 orlonger
user@R1# set policy-options policy-statement STATIC-TO-ISIS term 1 then accept
user@R1# set protocols isis export STATIC-TO-ISIS

The accepted routes appear in the router's LSP as external reachability, and other routers install them as IS IS external routes with preference 160 (Level 1) or 165 (Level 2). The final then accept is needed, because a route that the policy does not accept is rejected.

Route leaking between levels

By default, a Level 1 and 2 router advertises Level 1 routes into Level 2, and it does not advertise Level 2 routes into Level 1. To give the Level 1 area specific routes from the backbone, you use an export policy that matches the source level and the destination level:

user@R1# set policy-options policy-statement L2-TO-L1 term 1 from level 2
user@R1# set policy-options policy-statement L2-TO-L1 term 1 from route-filter 10.50.0.0/16 orlonger
user@R1# set policy-options policy-statement L2-TO-L1 term 1 to level 1
user@R1# set policy-options policy-statement L2-TO-L1 term 1 then accept
user@R1# set protocols isis export L2-TO-L1

The from level 2 and to level 1 conditions make this a leak. Without the route-filter, all Level 2 routes would leak. Apply the policy on the Level 1 and 2 router at the area border.

Level 2 routefrom level 2 and to level 1Policy acceptsleaked intoLevel 1 LSPspecific route in the area

Import policy

An import policy applies to the IS IS routes before they enter the routing table. Use it to refuse routes you do not want installed. It does not change the link state database, so the other routers still see the LSP.

user@R1# set policy-options policy-statement NO-TEST term 1 from route-filter 172.31.0.0/16 orlonger
user@R1# set policy-options policy-statement NO-TEST term 1 then reject
user@R1# set protocols isis import NO-TEST
ExportImport
DirectionFrom the routing table into IS IS, or between levelsFrom IS IS into the routing table
EffectChanges what the router advertises in LSPsChanges what the router installs
Typical useRedistribute static routes, leak routes between levelsRefuse specific prefixes

Troubleshooting sequence

Go from the bottom up. Each step tests a layer the next one depends on.

Interface upshow interfaces tersecheckfamily iso and NETcheckAdjacencyshow isis adjacencycheckDatabaseshow isis databasecheckRoutesshow route protocol isis

Ping and traceroute

user@R1> ping 10.1.1.2 rapid count 5
user@R1> ping 10.255.0.2 source 10.255.0.1 rapid
user@R1> traceroute 10.255.0.2 no-resolve

ping and traceroute use IP. They prove the IPv4 path, but not the IS IS adjacency, which runs below IP. A working ping with no adjacency usually means a missing family iso, a level mismatch or an authentication mismatch.

Show commands

CommandShows
show isis adjacencyNeighbors, level, state and hold time
show isis interfaceLevels, metrics, DIS per level and passive interfaces
show isis databaseThe LSPs per level; extensive shows the TLVs
show isis routeThe routes SPF calculated
show isis statisticsCounters of PDUs sent, received and dropped
show route protocol isisIS IS routes in the routing table with preference 15 or 18
Symptom in show isis adjacencyLikely cause
No entry at allfamily iso missing, interface not in protocols isis, or a level mismatch
Initializing or One-wayHellos in one direction only; authentication, MTU or a filter
No Level 1 entry, Level 2 entry presentArea mismatch for Level 1, or Level 1 disabled on one side
Level 2 only, where Level 1 expectedDifferent areas
Adjacency flapsLink errors, MTU, or hold time expiring

Traceoptions

user@R1# set protocols isis traceoptions file isis-trace size 1m files 5
user@R1# set protocols isis traceoptions flag hello detail
user@R1# set protocols isis traceoptions flag error
user@R1# set protocols isis traceoptions flag lsp
user@R1# commit

user@R1> show log isis-trace
user@R1> monitor start isis-trace
user@R1> monitor stop

Useful flags are hello, lsp, csn, spf, packets and error. The file is written in /var/log. Use monitor start to watch it live, and delete the configuration afterward, as tracing with detail costs CPU and disk.

Logging

The routing process records adjacency changes in the system log:

user@R1> show log messages | match ISIS
user@R1> show log messages | last 50

The time stamps show whether an adjacency flaps at regular intervals.

Watch out

Do not rely on a successful ping as proof that IS IS is working. ping tests IP, and IS IS needs the ISO family, matching levels and areas, and matching authentication.

Common mistakes

Expecting a static route to be advertised without an export policy. It needs one.

Leaving traceoptions in the configuration. It uses disk and CPU.

What to remember for the exam

  • Export policy puts external routes into IS IS and leaks routes between levels.
  • Leaking Level 2 into Level 1 needs from level 2 and to level 1 in an export policy.
  • Import policy changes only the local routing table, not the LSDB.
  • Check show isis adjacency, show isis interface and show isis database.
  • traceoptions writes to a file in /var/log; read it with show log or monitor start.

Check yourself

  • How do you give a Level 1 area specific routes from Level 2?

    Use an export policy with from level 2 and to level 1 on a Level 1 and 2 router, and apply it with protocols isis export.

  • Neighbors can ping each other but there is no IS IS adjacency. Name two causes.

    A missing family iso on the interface, and a level or Level 1 area mismatch (authentication or MTU problems are also possible).

  • Does an IS IS import policy hide a route from other routers?

    No, it only controls what the local router installs in its routing table; the LSP is unchanged.

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