Redback Networks

Customer Engineering

IS-IS Troubleshooting Guide

Issue Date: 2009-Feb-04 8:09 PM

Version: 16

Document ID: CE-TG-0007

Created by: Jerry Yu on: 05/02/2009

Updated by: Jerry Yujerryyu on: 2/4/2009 08:09:00 PM

Proprietary and Confidential

 Copyright 2009 Redback Networks Inc.

All rights reserved. No part of this publication may be used or
reproduced in any form by any means without prior written
permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Document Information

Document Name IS-IS Trouble-shooting Guide

Redback Document ID CE-TG-0007

Version 1.0

Issue Date 2009-Feb-04 8:09 PM

Document Acceptance
I have reviewed this document and it is approved for use effective from the signing date below.

Name Position Signature Date

Revision History

Issue Author(s) Date Description

1.0 Jerry Yu 05/02/2009 Initial Draft

Created by: Jerry Yu on: 05/02/2009 Page 2 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

Table of Contents

1 Introduction...............................................................................................................2

2 Topology....................................................................................................................2

3 Troubleshooting IS-IS Routing Problems....................................................2

3.1 IS-IS Adjacency Formation Problems.................................................................................. 4

3.1.1 Mismatched Level 1 and Level 2 Interfaces.................................................................................................. 4
3.1.2 Misconfigured NSAPs (NETs)............................................................................................................................. 7
3.1.3 Duplicate System IDs in an Area..................................................................................................................... 12
3.1.4 Misconfigured IP Addresses and Subnets.................................................................................................. 14
3.1.5 Authentication Problems...................................................................................................................................... 16
3.1.6 Commonly used CLI for debugging IS-IS adjacency............................................................................18

3.2 IS-IS Route Maintenance Problems....................................................................................18

3.2.1 Advertising IP Subnets by Activating IS-IS on Interfaces....................................................................19
3.2.2 IS-IS Route Installation Problems................................................................................................................... 22
3.2.3 Route Flaps/Unstable IS-IS Routes............................................................................................................... 24
3.2.4 Discontinuous Level 2 Subdomains............................................................................................................... 25
3.2.5 IS-IS summarization and redistribution problems....................................................................................26
3.2.6 Commonly used CLI for debugging IS-IS Route Problems...............................................................30

4 Summary..................................................................................................................30

Created by: Jerry Yu on: 05/02/2009 Page 3 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

1 Introduction

This document is intended to provide for troubleshooting steps to be taken for debugging IS-IS related
issues. This document is supposed to be generic troubleshooting guide, for specific feature related
information other resources should be considered.

2 Topology

3 Troubleshooting IS-IS Routing Problems

Common IS-IS routing problems fall under the following two broad categories:

 Adjacency formation problems

 Route maintenance problems

Created by: Jerry Yu on: 05/02/2009 Page 4 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

In Intermediate System-to-Intermediate System (IS-IS) Protocol, there are two types of networks: point-to-
point and broadcast. Unlike Open Shortest Path First (OSPF) Protocol, IS-IS does not have other network
types like non-broadcast and point-to-multipoint. For each type of network, a different type of IS-IS Hello
(IIH) packet is exchanged to establish adjacency. On point-to-point networks, point-to-point IIHs are
exchanged; and on broadcast networks (such as LAN), Level 1 or Level 2 LAN IIHs are exchanged.

During normal operation, IS-IS routers form and maintain adjacencies with each other by using hello
packets. Routing information is then exchanged by flooding LSPs, which are stored in appropriate Link-
State databases (Level 1 or Level 2). Sequence number packets (CSNPs and PSNPs) provide control for
the flooding process and ensure database synchronization. All these processes need to occur
successfully to ensure accurate dissemination of routing information in the IS-IS domain. Any failures

Created by: Jerry Yu on: 05/02/2009 Page 5 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
result in inconsistencies that ultimately result in routing problems. The following sections identify problems
and list the corresponding ways to isolate those problems

3.1 IS-IS Adjacency Formation Problems

Adjacency formation problems are common IS-IS failures. They mainly occur as a result of router
misconfiguration, hardware and software failures, and interoperability problems between routers from
different vendors. Adjacency problems are easier to isolate than routing problems. The following list of
adjacency problems are discussed in this section:

 Mismatched Level 1 and Level 2 interfaces

 Misconfigured NSAPs

 Duplicate system IDs

 Misconfigured IP addresses and Subnets

 Mismatch Authentication

3.1.1 Mismatched Level 1 and Level 2 Interfaces

The default mode of operation for SmartEdge routers running IS-IS is Level 1-2. In this mode, a router
can form both Level 1 and Level 2 adjacencies with neighbors in the same area and form only Level 2
adjacencies with neighbors in different areas. Below topology diagrams such a configuration. R2 forms
only a L2 adjacency with R3, which is in area 49.0002. The default Level 1-2 mode can be modified for all
interfaces on the router by using the router isis configuration-level command IS-type or for a specific
interface with the interface-level configuration command circuit-type level [level-1 | level-2]. If R2 is
misconfigured as a Level 1 only on 9/2 using any of the previously mentioned commands, it loses the
adjacency with R3. Consequently, the domain will be partitioned and there will be no communication
between area 49.0001 and area 49.0002.

The output shows as below in details:

Created by: Jerry Yu on: 05/02/2009 Page 6 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
[local]R2.17.145#sh config isis
Building configuration...

Current configuration:
context local
!
router isis csc
net 49.0001.0000.0000.0001.00 >>>>>>>>>>>>>> by default, SE use L1-L2
address-family ipv4 unicast
!
interface 9/2
! bind to ethernet 9/2
circuit type level-1
address-family ipv4 unicast
!

[local]R3.16.121#sh config isis

Building configuration...

Current configuration:
context local
!
router isis csc
net 49.0002.0000.0000.0002.00 >>>>>>>>>>>>>> by default, SE use L1-L2
address-family ipv4 unicast
!
interface 10/10
! bind to ethernet 10/10 >>>>>>>>>>>>>>>> by default, SE use L1-L2
address-family ipv4 unicast
!
interface loBB
address-family ipv4 unicast
!
end
[local]R3.16.121#

[local]R2.17.145#sh isis adjacency

Created by: Jerry Yu on: 05/02/2009 Page 7 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
[local]R2.17.145#terminal monitor
[local]R2.17.145#debug isis adjacency interface 9/2
[local]R2.17.145#Jan 29 16:28:25: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from
0030.88 02.1f44 seq 201 on intf 9/2
Jan 29 16:28:25: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030. 8802.1f44 on intf 9/2
Jan 29 16:28:27: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
38 on intf 9/2
Jan 29 16:28:29: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2
Jan 29 16:28:34: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
202 on intf 9/2
Jan 29 16:28:34: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8802.1f44 on intf 9/2
Jan 29 16:28:37: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
39 on intf 9/2
Jan 29 16:28:40: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2
Jan 29 16:28:44: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
203 on intf 9/2
Jan 29 16:28:44: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8802.1f44 on intf 9/2
Jan 29 16:28:47: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
40 on intf 9/2
Jan 29 16:28:50: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2
Jan 29 16:28:52: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
204 on intf 9/2
Jan 29 16:28:52: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8802.1f44 on intf 9/2
Jan 29 16:28:55: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
41 on intf 9/2
Jan 29 16:28:59: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2
Jan 29 16:29:00: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
205 on intf 9/2
Jan 29 16:29:00: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8802.1f44 on intf 9/2
Jan 29 16:29:07: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
42 on intf 9/2
Jan 29 16:29:09: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
206 on intf 9/2
Jan 29 16:29:09: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8802.1f44 on intf 9/2
Jan 29 16:29:11: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2

Created by: Jerry Yu on: 05/02/2009 Page 8 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
After change R2 interface 9/2 circuit type as Level 2, the IS-IS L2 adjacency shows up.

[local]R2.17.145(config)#context local
[local]R2.17.145(config-ctx)#router isis csc
[local]R2.17.145(config-isis)#interface 9/2
[local]R2.17.145(config-isis-if)#circuit type level-2-only
[local]R2.17.145(config-isis-if)#end
[local]R2.17.145#sh isis adjacency

IS-IS Adjacenc(ies) for tag csc:

SystemId Interface L MT Stat Hold SNPA Uptime
R3.16.121 9/2 2 U Init 20 0030.8802.1f44
00:00:00

Total IS-IS Adjacenc(ies): 1

[local]R2.17.145#sh isis adjacency

IS-IS Adjacenc(ies) for tag csc:

SystemId Interface L MT Stat Hold SNPA Uptime
R3.16.121 9/2 2 U Up 26 0030.8802.1f44
00:00:03

Total IS-IS Adjacenc(ies): 1

[local]R2.17.145#sh isis adjacency det

IS-IS Adjacenc(ies) for tag csc:

SystemId Interface L MT Stat Hold SNPA Uptime
R3.16.121 9/2 2 U Up 20 0030.8802.1f44
00:00:09
Area Address(es): 49.0002
IP Address(es): 200.1.1.2
BFD state N/A
neighbor IIH current seq 69, total iih pkt miss 0
adj nh-id 9, neighbor sent re-start tlv

Total IS-IS Adjacenc(ies): 1

[local]R2.17.145#

Created by: Jerry Yu on: 05/02/2009 Page 9 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Conclusion:
When the two routers are within different areas, they have to establish L2 adjacency. Therefore, the two
connected interfaces need to be configured as match circuit type- Either both use L2 or one use L2 with
another use L1-L2.
When the two routers are within same area, the routers can establish L1, L2 or L1|L2 adjacency
depending on configured circuit type of two connected interfaces. They could be L1 to L1, L2 to L2, L1 to
L1|L2 , L2 to L1|L2 or L1|L2 to L1|L2.

3.1.2 Misconfigured NSAPs (NETs)

Each IS-IS node must have at least one NSAP address (NET) to identify it as a network node. This NET
consists of the area ID of the node, the System ID, and a 0-value NSEL. The system ID is required to be
unique within the area; the NSEL value is fixed at 0x00. The area ID (also referred to as the area prefix)
must be the same for all nodes in the same area. For nodes with multiple NETs, the system ID must be
the same in all of them, and at least one of the area prefixes must be shared with another node in the
same area. The effect of misconfiguring a NET is illustrated in below. In this example, R2, R3, and R4 are
meant to be together in area 49.0001. They are also meant to form both Level 1 and Level 2
adjacencies.

The outputs of the show isis adjacency command from R2, R3, and R4 indicate R4 formed only Level 2
adjacencies with R2 and R3. However, R2 and R3 formed Level 1-2 adjacencies with each other as
expected. This creates a suspicion about the configuration and operation of R4.

Created by: Jerry Yu on: 05/02/2009 Page 10 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
[local2]R2.17.145#sh isis adjacency

IS-IS Adjacenc(ies) for tag csc2:

SystemId Interface L MT Stat Hold SNPA Uptime
R3.16.121 12/5 2 U Up 18 0030.8800.2b40
00:24:54
R3.16.121 12/5 1 U Up 28 0030.8800.2b40
00:24:54
R4 12/5 2 U Up 24 0030.8800.3345
00:10:08

Total IS-IS Adjacenc(ies): 3

[local2]R2.17.145#

[local2]R3.16.121#sh isis adjacency

IS-IS Adjacenc(ies) for tag csc2:

SystemId Interface L MT Stat Hold SNPA Uptime
R2.17.145 2/5 2 U Up 25 0030.8810.49a0
00:25:09
R2.17.145 2/5 1 U Up 21 0030.8810.49a0
00:25:09
R4 2/5 2 U Up 25 0030.8800.3345
00:10:19

Total IS-IS Adjacenc(ies): 3

[local2]R3.16.121#
[local2]R4#sh isis adjacency

IS-IS Adjacenc(ies) for tag csc2:

SystemId Interface L MT Stat Hold SNPA Uptime
R2.17.145 14/5 2 U Up 25 0030.8810.49a0
00:10:33
R3.16.121 14/5 2 U Up 28 0030.8800.2b40
00:10:30

Total IS-IS Adjacenc(ies): 2

[local2]R4#

Created by: Jerry Yu on: 05/02/2009 Page 11 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
A glance at the MAC addresses under the show port x/y detail shows that R2 has a higher MAC address
than R3 and R4, so with each node retaining the default interface priority value, R2 should be both the
Level 1 and Level 2 DIS. This is confirmed by the show isis interface output of R2, R3 and R4. R4 points
correctly to R2 as the Level 2 DIS but incorrectly to itself as the Level 1 DIS. This implies that there is a
problem with Level 1 communication. Because this is a new setup and all the defaults have not been
tampered with, the only factor that might dictate the type of adjacency formed is the area prefix.

Further inspection of the NET configured on R4 shows that it was misconfigured with
47.1000.0000.0000.0003.00 00 rather than 49.1000.0000.0000.0003.00. This area ID mismatch resulted
in R2 and R3 forming only Level 2 adjacencies with R4.

[local2]R2.17.145#sh port 12/5 det

ethernet 12/5 state is Up
Description :
Line state : Up
Admin state : Up
Link Dampening : disabled
Undampened line state : Up
Dampening Count : 0
Encapsulation : ethernet
MTU size : 1500 Bytes
NAS Port Type :
MAC address : 00:30:88:10:49:a0
Media type : 100Base-TX
Speed : 100 Mbps
Duplex mode : full
Loopback : off
Active Alarms : NONE

[local2]R2.17.145#

[local2]R2.17.145#sh isis interfaces

IS-IS interface(s) for tag csc2:
Interface L MT Stat Level-1-DR Level-2-DR Metric
12/5 3 U Up R2.17.145.01 R2.17.145.01 10

Total IS-IS Interface(s): 1

[local2]R2.17.145#

Created by: Jerry Yu on: 05/02/2009 Page 12 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

[local2]R3.16.121#sh port 2/5 det

ethernet 2/5 state is Up
Description :
Line state : Up
Admin state : Up
Link Dampening : disabled
Undampened line state : Up
Dampening Count : 0
Encapsulation : ethernet
MTU size : 1500 Bytes
NAS Port Type :
MAC address : 00:30:88:00:2b:40
Media type : 100Base-TX
Speed : 100 Mbps
Duplex mode : full
Loopback : off
Active Alarms : NONE

[local2]R3.16.121#sh isis interfaces

IS-IS interface(s) for tag csc2:
Interface L MT Stat Level-1-DR Level-2-DR Metric
2/5 3 U Up R2.17.145.01 R2.17.145.01 10

Total IS-IS Interface(s): 1

[local2]R3.16.121#

[local2]R4#sh port 14/5 det

ethernet 14/5 state is Up
Description :
Line state : Up
Admin state : Up
Link Dampening : disabled
Undampened line state : Up
Dampening Count : 0
Encapsulation : ethernet
Created by: Jerry Yu on: 05/02/2009 Page 13 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
MTU size : 1500 Bytes
NAS Port Type :
MAC address : 00:30:88:00:33:45
Media type : 100Base-TX
Speed : 100 Mbps
Duplex mode : full
Loopback : off
Active Alarms : NONE

[local2]R3#sh isis interfaces

IS-IS interface(s) for tag csc2:
Interface L MT Stat Level-1-DR Level-2-DR Metric
14/5 3 U Up ser-1.01 R2.17.145.01 10

Total IS-IS Interface(s): 1 R3 choose itself as L1 DIS, which is

[local2]ser-1# incorrect since R2 has higher MAC!

[local2]R2.17.145#terminal monitor
[local2]R2.17.145#debug isis adjacency interface 12/5
[local2]R2.17.145#Feb 3 16:03:22: [0004]: %ISIS-7-ADJ: send L2 LAN IIH on intf
12/5
Feb 3 16:03:26: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.2b40 seq
321 on intf 12/5
Feb 3 16:03:27: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.2b40 seq
316 on intf 12/5
Feb 3 16:03:27: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.3345 seq
213 on intf 12/5
Feb 3 16:03:30: [0004]: %ISIS-7-ADJ: send L1 LAN IIH on intf 12/5
Feb 3 16:03:31: [0004]: %ISIS-7-ADJ: send L2 LAN IIH on intf 12/5
Feb 3 16:03:31: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.3345 seq
211 on intf 12/5
Feb 3 16:03:31: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8800.3345 on intf 12/5
Feb 3 16:03:35: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.2b40 seq
322 on intf 12/5
Feb 3 16:03:35: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.3345 seq
214 on intf 12/5

Created by: Jerry Yu on: 05/02/2009 Page 14 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Feb 3 16:03:37: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.2b40 seq
317 on intf 12/5
Feb 3 16:03:39: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.3345 seq
212 on intf 12/5
Feb 3 16:03:39: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH with area mismatch from
0030.8800.3345 on intf 12/5
Feb 3 16:03:41: [0004]: %ISIS-7-ADJ: send L2 LAN IIH on intf 12/5
Feb 3 16:03:42: [0004]: %ISIS-7-ADJ: send L1 LAN IIH on intf 12/5

3.1.3 Duplicate System IDs in an Area

All IS-IS nodes in an area must have the same area prefix and a unique system ID. If a node has multiple
NETs configured, each address must retain the same system ID. This is a critical protocol requirement,
especially because the system ID forms part of the LSPID, and uniqueness is required to identify the
owners of LSPs flooded within the area. When different nodes in the area are erroneously configured with
the same system ID, the problem is detected and each node logs appropriate error messages to that
effect. If the nodes are directly connected, each router immediately detects the problem as it exchanges
hellos to establish adjacency. Consequently, the adjacency fails. If they are not directly connected,
however, they overwrite each other's LSP for some time until the IS-IS process determines, based on the
frequency of occurrence, that the problem is because of duplicate system IDs and logs appropriate error
messages. Below shows the output of the debug isis adjacency command for a duplicate system ID
situation between directly connected neighbors within same broadcast domain that was mis-configured as
duplicate System IDs in same area.

[local2]R2.17.145#Feb 3 16:10:06: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from

0030.8800.3345 seq 23 on intf 12/5
Feb 3 16:10:06: [0004]: %ISIS-7-ADJ: rcvd LAN L2 IIH duplicate system ID from
0030.8800.3345 on intf 12/5
Feb 3 16:10:07: [0004]: %ISIS-7-ADJ: send L1 LAN IIH on intf 12/5
Feb 3 16:10:07: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.2b40 seq
355 on intf 12/5
Feb 3 16:10:07: [0004]: %ISIS-7-ADJ: send L2 LAN IIH on intf 12/5
Feb 3 16:10:09: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.3345 seq
23 on intf 12/5
Feb 3 16:10:09: [0004]: %ISIS-7-ADJ: rcvd LAN L1 IIH duplicate system ID from
0030.8800.3345 on intf 12/5
Feb 3 16:10:11: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.2b40 seq
362 on intf 12/5
Feb 3 16:10:15: [0004]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.3345 seq
24 on intf 12/5
Feb 3 16:10:15: [0004]: %ISIS-7-ADJ: rcvd LAN L2 IIH duplicate system ID from
0030.8800.3345 on intf 12/5
Feb 3 16:10:17: [0004]: %ISIS-7-ADJ: send L2 LAN IIH on intf 12/5
Feb 3 16:10:17: [0004]: %ISIS-7-ADJ: send L1 LAN IIH on intf 12/5

Created by: Jerry Yu on: 05/02/2009 Page 15 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Feb 3 16:10:17: [0004]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.3345 seq
24 on intf 12/5
Feb 3 16:10:17: [0004]: %ISIS-7-ADJ: rcvd LAN L1 IIH duplicate system ID from
0030.8800.3345 on intf 12/5

[local2]R4#Feb 3 16:01:53: [0008]: %ISIS-7-ADJ: rcvd L1 LAN IIH from

0030.8810.49a0 seq 356 on intf 14/5

Feb 3 16:01:53: [0008]: %ISIS-7-ADJ: rcvd LAN L1 IIH duplicate system ID from
0030.8810.49a0 on intf 14/5

Feb 3 16:01:55: [0008]: %ISIS-7-ADJ: send L2 LAN IIH on intf 14/5

Feb 3 16:01:55: [0008]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8810.49a0 seq
351 on intf 14/5

Feb 3 16:01:55: [0008]: %ISIS-7-ADJ: rcvd LAN L2 IIH duplicate system ID from
0030.8810.49a0 on intf 14/5

Feb 3 16:02:00: [0008]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8800.2b40 seq
354 on intf 14/5

Feb 3 16:02:01: [0008]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8800.2b40 seq
348 on intf 14/5

Feb 3 16:02:01: [0008]: %ISIS-7-ADJ: send L1 LAN IIH on intf 14/5

Feb 3 16:02:03: [0008]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8810.49a0 seq
352 on intf 14/5

Feb 3 16:02:03: [0008]: %ISIS-7-ADJ: rcvd LAN L2 IIH duplicate system ID from
0030.8810.49a0 on intf 14/5

Feb 3 16:02:03: [0008]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8810.49a0 seq
357 on intf 14/5

Feb 3 16:02:03: [0008]: %ISIS-7-ADJ: rcvd LAN L1 IIH duplicate system ID from
0030.8810.49a0 on intf 14/5

Feb 3 16:02:05: [0008]: %ISIS-7-ADJ: send L2 LAN IIH on intf 14/5

3.1.4 Misconfigured IP Addresses and Subnets

Originally, the IS-IS protocol relied on only IS-IS hellos to form and maintain adjacencies, using a three-
way handshake on broadcast links and a two-way handshake on point-to-point links, all independent of
the IP configuration. The increasing popularity of IS-IS for routing IP has promoted various enhancements
both within the IETF and in vendor-specific implementations through feature introductions.

The effect of IP address misconfiguration is illustrated in the following debugging and show command
output. In Example below the IP address of R3’s interface 10/10is changed to 201.1.1.2/24. This
erroneous entry causes adjacency to be invalidated at R3 and logging of an adjacency change message.
The debugging output shown in below includes an error, “rcvd L2 LAN IIH with no common IP subnets fro
m 0030.8810.10fd on intf 10/10”

Created by: Jerry Yu on: 05/02/2009 Page 16 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

[local]R3.16.121#config
Enter configuration commands, one per line, 'end' to exit
[local]R3.16.121(config)#context local
[local]R3.16.121(config-ctx)#int 10/10
[local]R3.16.121(config-if)#no ip address
[local]R3.16.121(config-if)# ip address 201.1.1.2/24
[local]R3.16.121(config-if)#commit
Transaction committed.

[local]R3.16.121(config-if)#end

[local]R3.16.121#terminal monitor

[local]R3.16.121#debug isis adjacency interface 10/10

[local]R3.16.121#Jan 30 11:53:39.062: [0001]: %ISIS-7-ADJ: send L2 LAN IIH on
intf 10/1 0
Jan 30 11:53:41.069: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8810.10fd
seq 21 on intf 10/10
Jan 30 11:53:41.071: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH with no common IP
subnets for m 0030.8810.10fd on intf 10/10
Jan 30 11:53:45.389: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8810.10fd
seq 22 on intf 10/10
Jan 30 11:53:45.390: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with no common IP
subnets from 0030.8810.10fd on intf 10/10

Created by: Jerry Yu on: 05/02/2009 Page 17 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Jan 30 11:53:45.472: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 10/10
Jan 30 11:53:49.962: [0001]: %ISIS-7-ADJ: send L2 LAN IIH on intf 10/10
Jan 30 11:53:50.679: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8810.10fd
seq 22 on intf 10/10
Jan 30 11:53:50.680: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH with no common IP
subnets from 0030.8810.10fd on intf 10/10
Jan 30 11:53:53.169: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8810.10fd
seq 23 on intf 10/10
Jan 30 11:53:53.171: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with no common IP
subnets from 0030.8810.10fd on intf 10/10
Jan 30 11:53:53.872: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 10/10
Jan 30 11:54:00.980: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8810.10fd
seq 24 on intf 10/10
Jan 30 11:54:00.981: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH with no common IP
subnets from 0030.8810.10fd on intf 10/10
Jan 30 11:54:01.182: [0001]: %ISIS-7-ADJ: send L2 LAN IIH on intf 10/10
Jan 30 11:54:02.194: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8810.10fd
seq 23 on intf 10/10
Jan 30 11:54:02.195: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH with no common IP
subnets from 0030.8810.10fd on intf 10/10
Jan 30 11:54:04.463: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 10/10

3.1.5 Authentication Problems

IS-IS specifications (ISO 10589 [1] and RFC 1195 [2]) provide a simple password scheme for
authentication.

When authentication is configured, a clear-text password is inserted into IS-IS packets, such as LSPs,
CSNPs, and PSNPs, as are also hellos (link authentication only). The password is verified before a
packet is accepted for processing. Clearly, a password mismatch between the source of the packet and
the recipient could create both adjacency and routing maintenance problems, depending on the type of
authentication enabled. Output below shows a debug isis adj output for a link authentication failure.

Configures Intermediate System-to-Intermediate System (IS-IS) routing packet authentication using the
simple or Hash-Based Message Authentication Code-Message Digest 5 (HMAC-MD5) authentication
scheme for the IS-IS interface or IS-IS instance.

Use the authentication command in IS-IS interface configuration mode to configure IS-IS routing packet
authentication using the simple or HMAC-MD5 authentication scheme for an IS-IS interface.

Use the authentication command in IS-IS router configuration mode to configure IS-IS routing packet
authentication using the simple or HMAC-MD5 authentication scheme for an IS-IS instance. To use a
different key for a specific interface, use the authentication command in IS-IS interface configuration
mode.

Created by: Jerry Yu on: 05/02/2009 Page 18 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
IS-IS authentication increases the network routing security. This command authenticates all IS-IS packets
on the IS-IS interface or IS-IS instance.

The following example demonstrates adjacency cannot be established between R2 and R3. R2
configured with IS-IS authentication and R3 without authentication.

[local]R2.17.145#sh config isis

Building configuration...

Current configuration:
context local
!
router isis csc
net 49.0001.0000.0000.0001.00
authentication key-chain jyu type simple
address-family ipv4 unicast
!
interface 9/2
! bind to ethernet 9/2
hello padding never
address-family ipv4 unicast
!
interface loBB
passive-interface
address-family ipv4 unicast
!
End

[local]R2.17.145#terminal monitor
[local]R2.17.145#debug isis adjacency
[local]R2.17.145#Feb 2 12:23:10: [0001]: %ISIS-7-ADJ: send L2 LAN IIH on intf
9/2
Feb 2 12:23:11: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
25878 on intf 9/2
Feb 2 12:23:11: [0001]: %ISIS-7-ADJ: authentication failed on rcvd L2 LAN IIH
from 0030.8802.1f44 on interface 9/2
Feb 2 12:23:15: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
25877 on intf 9/2
Feb 2 12:23:15: [0001]: %ISIS-7-ADJ: authentication failed on rcvd L1 LAN IIH
from 0030.8802.1f44 on interface 9/2
Created by: Jerry Yu on: 05/02/2009 Page 19 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Feb 2 12:23:16: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2
Feb 2 12:23:19: [0001]: %ISIS-7-ADJ: send L2 LAN IIH on intf 9/2
Feb 2 12:23:22: [0001]: %ISIS-7-ADJ: rcvd L2 LAN IIH from 0030.8802.1f44 seq
25879 on intf 9/2
Feb 2 12:23:22: [0001]: %ISIS-7-ADJ: authentication failed on rcvd L2 LAN IIH
from 0030.8802.1f44 on interface 9/2
Feb 2 12:23:23: [0001]: %ISIS-7-ADJ: rcvd L1 LAN IIH from 0030.8802.1f44 seq
25878 on intf 9/2
Feb 2 12:23:23: [0001]: %ISIS-7-ADJ: authentication failed on rcvd L1 LAN IIH
from 0030.8802.1f44 on interface 9/2
Feb 2 12:23:24: [0001]: %ISIS-7-ADJ: send L1 LAN IIH on intf 9/2

[local]R3.16.121#sh isis adjacency

R3 IS-IS state keeps as “Init” state
forever due to R2 fail authentication.
IS-IS Adjacenc(ies) for tag csc:
SystemId Interface L MT Stat Hold SNPA Uptime
R2.17.145 10/10 2 U Init 23 0030.8810.10fd
00:00:00
ser-1 2/11 2 U Up 28 0030.8800.334b
02d19h05

[local]R3.16.121#sh config isis

Building configuration...

Current configuration:
context local
!

router isis csc

net 49.0002.0000.0000.0002.00
address-family ipv4 unicast
redistribute connected
!
interface 10/10
! bind to ethernet 10/10
hello padding never
address-family ipv4 unicast
!
interface loBB
Created by: Jerry Yu on: 05/02/2009 Page 20 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
address-family ipv4 unicast
!
interface 2/11
! bind to ethernet 2/11
circuit mtu 500
address-family ipv4 unicast
!
end
[local]R3.16.121#

3.1.6 Commonly used CLI for debugging IS-IS adjacency

Reset IS-IS adjacencies with neighbors. clear isis adjacency

Enable the generation of IS-IS adjacency debug messages. debug isis adjacency
Enables the generation of all IS-IS debug messages debug isis all
Enable the generation of IS-IS Hello packet debug messages debug isis hello-packets
Display continuously updated information about IS-IS neighbors. monitor isis adjacency
Display continuously updated information about IS-IS interfaces. monitor isis interfaces
Display continuously updated information about IS-IS traffic statistics. monitor isis statistics
Display information about IS-IS neighbors. show isis adjacency
Display the current IS-IS configuration for the current context. show configuration isis
Display adjacency logs show isis adj-log

3.2 IS-IS Route Maintenance Problems

This section focuses on route maintenance problems. The adjacency formation problems discussed in the
preceding section are much easier to troubleshoot and resolve than router maintenance problems, which
are normally not obvious in very large networks until a specific address or subnet becomes unreachable.
Obviously, most IS-IS problems relate to adjacency problems. When no adjacency issues exist, it
becomes challenging to isolate routing problems; however, the routing table might be fed with routing
information from multiple sources. Most routers connected to the Internet are configured with two IP
routing protocols, typically BGP for inter-domain routing and IS-IS or OSPF for intra-domain routing.

Frequently in these situations, little overlap occurs in prefixes advertised by each protocol, so there is
practically no contention in populating the routing table.
Even though very rare, route maintenance problems might relate to problems in the lookup mechanism
rather than the actual source of the route. This section focuses on only IS-IS-related causes. The
Created by: Jerry Yu on: 05/02/2009 Page 21 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
following are the most common causes of routing inconsistencies in IS-IS and are discussed in detail in
the following sections:

 IS-IS route advertisement problems

 IS-IS route installation problem

 Route flaps

 Discontinuous Level 2 subdomain

 IS-IS summarization and redistribution problems

If a route is not being heard in the rest of the area or domain, the first step in troubleshooting the problem
is to make sure the procedure for introducing the route into the IS-IS process has been properly
configured.

3.2.1 Advertising IP Subnets by Activating IS-IS on Interfaces

If the first method is used, the ip router isis command must be applied to the appropriate interface. Note
that IS-IS does not use a network statement for advertising an IP route as is commonly done for other
protocols. Instead, enabling IS-IS on an interface triggers the formation of adjacencies on that interface
and also advertises the attached IP subnet in an LSP to all neighbors. The show ip interface brief
command confirms the interface on which the route is connected, followed by a show isis interface
command. The actual configuration of the interface can also be verified with the command show
running-config | begin interface <type and number>, as shown in Example 10-38.

[local]R2.17.145#sh isis interfaces det

IS-IS interface(s) for tag csc:
9/2
Up, level: 3, Ckt Id: 1, lan, Ucast IP address: 200.1.1.1/24
mtu: 9000, speed 1000000, Grid: 0x10000000, nh-id: 2, ckt 9/2
metrics[L1/L2]: v4 ucast[10/10]
Level Adjs Priority Hello Hold Auth Blocked Metric
1 1 64 0 30 10
2 1 64 5 30 10
loBB
Up, level: 3, Ckt Id: 2, p2p, Ucast IP address: 110.1.1.1/32
mtu: 1500, speed 0, Grid: 0x10000001, nh-id: 3, ckt Loopback
metrics[L1/L2]: v4 ucast[10/10]
Level Adjs Priority Hello Hold Auth Blocked Metric
3 0 64 7 30 10

Total IS-IS Interface(s): 2

Created by: Jerry Yu on: 05/02/2009 Page 22 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
[local]R2.17.145#

If the interface is properly configured, the next step might be to take a look at the IP reachability
information fields of the router's LSP with the command show isis database level detail LSPID. This
command provides insight into the information in the LSP that is advertised to other neighbors. It is
assumed that there are no adjacency problems with any of the neighbors in the direction of the network
where the route is missing. The level-1 keyword is used if the route is missing in only the local area, and
the level-2 keyword is used if the route is not present in other areas within the same domain. If no
adjacency problems exist, IS-IS routing is enabled correctly on the interface where the route should be
taken from, and the prefix is seen in the LSP of the local router; then the problem is complex and requires
more insight. The show isis database level detail LSPID command should be used on the remote
routers to check the presence and currency of the LSP in question. The debug isis update-packet
command assists with debugging any issues with periodic database synchronization on LANs. Note that
synchronization issues are absent on point-to-point links because of the reliable flooding process used on
such links.

[local]R2.17.145#sh isis database l1

IS-IS level 1 link-state database for tag csc:

LSPID Sequence Checksum Holdtime AT/OL Len
R2.17.145.00-00* 0x3db 0x511a 521 0/0 97
R2.17.145.01-00* 0x6e 0x95b1 521 0/0 53
R3.16.121.00-00 0x1dc 0x7539 1126 0/0 124
ser-1.00-00 0xf 0xee4f 599 0/0 82
ser-1.01-00 0x4 0x6c41 599 0/0 53

Total IS-IS LSP(s) for tag csc in Level-1: 5

[local]R2.17.145#sh isis database l2

IS-IS level 2 link-state database for tag csc:

LSPID Sequence Checksum Holdtime AT/OL Len
R2.17.145.00-00* 0x3e4 0xfdf0 453 0/0 133
R2.17.145.01-00* 0x397 0x3ae0 377 0/0 53
R3.16.121.00-00 0x3df 0xd56a 1181 0/0 160
ser-1.00-00 0x10 0xf5bf 612 0/0 118
ser-1.01-00 0x4 0x6c41 612 0/0 53

Total IS-IS LSP(s) for tag csc in Level-2: 5

[local]R2.17.145#

Created by: Jerry Yu on: 05/02/2009 Page 23 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Advertising a Subnet with passive-interface

The passive-interface command is normally used when the subnet on an interface needs to be
advertised without forming adjacency or sending redundant hello messages over that interface. For
example, a loopback interface is normally defined as a passive interface so that its address will be
advertised without wasting CPU cycles to generate unnecessary hellos to nonexistent neighbors. If a
loopback address is not advertised, the configuration should be checked to make sure it is specified as a
passive interface.

[local]R2.17.145#sh config isis

Building configuration...

Current configuration:
context local
!
router isis csc
net 49.0001.0000.0000.0001.00
address-family ipv4 unicast
!
interface 9/2
! bind to ethernet 9/2
hello padding never
address-family ipv4 unicast
!
interface loBB
passive-interface
address-family ipv4 unicast
!
end
[local]R2.17.145#sh isis in
[local]R2.17.145#sh isis interfaces
IS-IS interface(s) for tag csc:
Interface L MT Stat Level-1-DR Level-2-DR Metric
9/2 3 U Up R2.17.145.01 R2.17.145.01 10
loBB 3 U Up 1

Total IS-IS Interface(s): 2

[local]R2.17.145#sh isis interfaces det
IS-IS interface(s) for tag csc:
9/2
Created by: Jerry Yu on: 05/02/2009 Page 24 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Up, level: 3, Ckt Id: 1, lan, Ucast IP address: 200.1.1.1/24
mtu: 9000, speed 1000000, Grid: 0x10000000, nh-id: 2, ckt 9/2
metrics[L1/L2]: v4 ucast[10/10]
Level Adjs Priority Hello Hold Auth Blocked Metric
1 1 64 4 30 10
2 1 64 3 30 10
loBB
Up, level: 3, Ckt Id: 2, p2p(Passive), Ucast IP address: 110.1.1.1/32
mtu: 1500, speed 0, Grid: 0x10000001, nh-id: 3, ckt Loopback
metrics[L1/L2]: v4 ucast[1/1]
Level Adjs Priority Hello Hold Auth Blocked Metric
3 0 64 7 30 1

Total IS-IS Interface(s): 2

[local]R2.17.145#

3.2.2 IS-IS Route Installation Problems

Route installation problems involve situations where an LSP from a remote router is properly received, but
a route in the LSP is not installed in the routing table as expected. IS-IS does not have any complicated
schemes for installing routes that are determined by the SPF process to be the best path. For example,
OSPF external link-state advertisements have a forwarding address when non-zero has to be learned
through OSPF for a routing bit that controls insertion into the routing table to be set appropriately. IS-IS
has no concept of a routing bit. The most plausible reason why an IS-IS route should not make it into the
routing table is because there is a similar route from another routing source with a better administrative
distance than IS-IS. Route installation problems are rare in IS-IS, and when they do occur, the reason is
most certainly a software failure or an interoperability issue.

You can use the following commands to isolate route installation problems:

 show ip route [isis]

 show isis database level detail LSPID

[local]R2.17.145#sh isis database level-2

IS-IS level 2 link-state database for tag csc:

LSPID Sequence Checksum Holdtime AT/OL Len
R2.17.145.00-00* 0x4fd 0xb97f 953 0/0 116
R2.17.145.01-00* 0x4ab 0xff6 953 0/0 53
Created by: Jerry Yu on: 05/02/2009 Page 25 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
R3.16.121.00-00 0x4fb 0xf1fb 1119 0/0 197
ser-1.00-00 0x129 0x34c4 447 0/0 92
ser-1.01-00 0x118 0x4157 447 0/0 53

Total IS-IS LSP(s) for tag csc in Level-2: 5

[local]R2.17.145#
[local]R2.17.145#sh isis database level-2 det

IS-IS level 2 link-state database for tag csc:

LSPID Sequence Checksum Holdtime AT/OL Len
R2.17.145.00-00* 0x4fc 0xbb7e 421 0/0 116
Area Address: 49.0001
NLPID: IP
Hostname: R2.17.145
IP Address: 110.1.1.1
M-Topology:
Metric: 10 IS-Extended R2.17.145.01
Metric: 10 IP 200.1.1.0/24
Metric: 1 IP 110.1.1.1/32
Metric: 10 IP 200.1.1.0/24
Metric: 1 IP 110.1.1.1/32
R2.17.145.01-00* 0x4aa 0x11f5 421 0/0 53
Metric: 0 IS-Extended R2.17.145.00
Metric: 0 IS-Extended R3.16.121.00
R3.16.121.00-00 0x4fa 0xf3fa 566 0/0 197
Area Address: 49.0002
NLPID: IP
Hostname: R3.16.121
IP Address: 100.1.1.2
M-Topology:
Metric: 10 IS-Extended R2.17.145.01
Metric: 10 IS-Extended ser-1.01
Metric: 10 IP 200.1.1.0/24
Metric: 10 IP 100.1.1.2/32
Metric: 10 IP 118.1.1.0/24
Metric: 0 IP 10.16.50.4/32
Metric: 0 IP 10.16.50.20/30
Created by: Jerry Yu on: 05/02/2009 Page 26 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Metric: 0 IP 10.16.50.52/30
Metric: 0 IP 10.16.83.34/32
Metric: 0 IP 10.192.16.0/23
Metric: 10 IP 100.1.1.2/32
Metric: 10 IP 200.1.1.0/24
Metric: 10 IP 118.1.1.0/24
ser-1.00-00 0x129 0x34c4 788 0/0 92
Area Address: 49.0001
NLPID: IP
Hostname: ser-1
IP Address: 118.1.1.1
M-Topology:
Metric: 10 IS-Extended ser-1.01
Metric: 10 IP 118.1.1.0/24
Metric: 10 IP 118.1.1.0/24
ser-1.01-00 0x118 0x4157 788 0/0 53
Metric: 0 IS-Extended ser-1.00
Metric: 0 IS-Extended R3.16.121.00

Total IS-IS LSP(s) for tag csc in Level-2: 5

[local]R2.17.145#
The show ip route prefix command determines the absolute absence of the prefix from the routing table.
If the route is present but from another source, the administrative distance should be lower; otherwise,
there's an issue. The isis keyword lists only all IS-IS routes in the IP routing table. This might prove useful
to confirm whether only a specific route from IS-IS is affected.

If a route is not in the routing table as expected, the show isis database command specifying the routing
level, the LSPID of the source LSP, and the detail keyword should be used to probe further into the
contents of the LSP.

3.2.3 Route Flaps/Unstable IS-IS Routes

Route instability means that the route is available only intermittently. This is usually described as a route
flap. Route flap might result just from an unstable link or possibly because of a more complex underlying
condition, such as an intermittent routing loop.

Typically, at the point where the flap is seen, the LSP that contains the route is periodically advertised and
withdrawn, or newer versions are continuously being received. Route flaps can also have a devastating
effect on the routing environment if a large number of LSPs and routers are affected. This might cause
the SPF process to run for prolonged periods, resulting in potentially dangerous levels of CPU utilization
on the affected routers.

If the network changes affect only IP prefixes, only partial route calculation (PRC) might be performed by
the IS-IS SPF process. Other situations might require scheduling of a "full" SPF. The latter is more CPU-
intensive.
Created by: Jerry Yu on: 05/02/2009 Page 27 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
By far, the most common causes of route flaps are unstable links. In a large network, the display-route-
detail command discussed in the preceding section can determine the LSP associated with the unstable
route . The focus of problem isolation can then be placed on the source of the LSP.

In most cases, a route flap problem can be quickly confirmed by looking at the sequence numbers of
LSPs in the same link state database. The show isis database output features a far higher sequence
number for the LSP with ID R2 than for the other known LSPs. The huge discrepancy signals either
problems at the source or somewhere in between the source and the point of observation. If the source
and the router at which the problem is being observed are directly connected, you can use standard
procedures to troubleshoot the physical and data link layers. The show interface or show isis interface
command can provide link status information and some leads might be available in the logs. Because the
problem might be adjacency related, the debug isis adj-packet debugging option can be enabled to
observe the problem further. At the source of the LSP, the debug isis spf-log command provides
information regarding events affecting the locally sourced LSP and, therefore, some clues to the problem.

[local]R2.17.145#sh isis database level-2

IS-IS level 2 link-state database for tag csc:

LSPID Sequence Checksum Holdtime AT/OL Len
R2.17.145.00-00* 0x4fd 0xb97f 953 0/0 116
R2.17.145.01-00* 0x4ab 0xff6 953 0/0 53
R3.16.121.00-00 0x4fb 0xf1fb 1119 0/0 197
R4.00-00 0x129 0x34c4 447 0/0 92
R4.01-00 0x118 0x4157 447 0/0 53

Total IS-IS LSP(s) for tag csc in Level-2: 5

[local]R2.17.145#

3.2.4 Discontinuous Level 2 Subdomains

IS-IS requires the Level 2 backbone that interconnects the various areas to be contiguous. This condition
can easily be violated by bad network design or router misconfiguration, as shown in below. SmartEdge
routers function as Level 1-2 by default and caution should be exercised in turning off Level 2 routing until
the impact is well understood. The Level 1-only router in area 49.0002 disrupts the continuity of the Level
2 path, preventing areas 49.0001 and 49.0003 from reaching each other.

Created by: Jerry Yu on: 05/02/2009 Page 28 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

3.2.5 IS-IS summarization and redistribution problems

The most complicated routing maintenance problems involve redistribution. Redistribution of static routes
is manageable and related problems are easy to troubleshoot.

Problems that relate to redistribution of a dynamically learned route are far more complicated. This is
primarily because no inherent loop-prevention mechanisms are associated with route redistribution. The
safest way to redistribute routes without establishing loops and route feedback is to limit the points where
redistribution occurs. When problems occur in such situations, it is best to troubleshoot at the points of
redistribution (border routers). Redistributed IP routes are entered as externals into the LSP. The show
isis database level detail LSPID command can be used to inspect the LSPs of the border routers to
ensure the external reachability information reaches the LSPs correctly. When the IS-IS domain has
multiple points of redistribution, more than one LSP can introduce the external routes into the IS-IS
domain, requiring care to be taken so that the border routers do not point to each other as the best exit
from the domain to the external destinations.

The router-level display-route-detail command provides knowledge about which LSPs are responsible for
specific routes in the routing table. This is a useful tool for troubleshooting routing problems and tracking
where the entries in the routing table originate from. Figure 10-8 demonstrates the operation of this
command, and the command output is shown in Example 10-39. A partial configuration of RT1 and the
output of the show ip route isis command executed on RT1 are included in Example 10-39. Also shown is
a show isis database command from the same router. Each IS-IS entry in the routing table of RT1
indicates the number of the LSP from which it came. The LSP numbers are shown in brackets in the show
isis database output. For example, 10.1.2.0/24 is learned from LSP number 4, which is RT2.00-00. The
display-route-detail command also displays backup paths for routes, which are alternative, less-
preferred paths. The following backup entry is provided for this route:
Created by: Jerry Yu on: 05/02/2009 Page 29 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

[local]R3.16.121#sh ip int brief

Fri Jan 30 16:23:41 2009
Name Address MTU State Bindings
10/10 200.1.1.2/24 1400 Up ethernet 10/10
2/11 118.1.1.2/24 500 Up ethernet 2/11
GE10/2 10.16.50.22/30 1500 Up ethernet 10/2
GE10/4 10.16.50.53/30 1500 Up ethernet 10/4
Lo0.1 10.16.83.34/32 1500 Up (Loopback)
lo1 10.16.50.4/32 1500 Up (Loopback)
loBB 100.1.1.2/32 1500 Up (Loopback)
mgmt 10.192.16.121/23 1500 Up ethernet 7/1

[local]R3.16.121(config)#context local
[local]R3.16.121(config-ctx)#router isis csc
[local]R3.16.121(config-isis)#address-family ipv4 unicast
[local]R3.16.121(config-isis-af)#redistribute connected
Created by: Jerry Yu on: 05/02/2009 Page 30 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
[local]R3.16.121(config-isis-af)#end
[local]R3.16.121#

[local]R3.16.121#sh ip route isis

Codes: C - connected, S - static, S dv - dvsr, R - RIP, e B - EBGP, i B - IBGP
A,H - derived hidden
O - OSPF, O3 - OSPFv3, IA - OSPF(v3) inter-area,
N1 - OSPF(v3) NSSA external type 1, N2 - OSPF(v3) NSSA external type
2
E1 - OSPF(v3) external type 1, E2 - OSPF(v3) external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, N - NAT
IPH - IP Host, SUB A - Subscriber address, SUB S - Subscriber static
MIP F - Mobile-IP Foreign Agent, MIP H - Mobile-IP Home Agent
A - Derived Default, MH - Media Nexthop
> - Active Route, * - LSP

Type Network Next Hop Dist Metric UpTime Interface

> i L2 10.16.50.2/32 10.16.50.21 115 101 4d01h GE10/2
> i L2 10.16.50.8/32 10.16.50.54 115 101 4d01h GE10/4
> i L2 10.16.50.36/30 10.16.50.21 115 200 4d01h GE10/2
> 10.16.50.54 GE10/4
> i L2 110.1.1.1/32 200.1.1.1 115 11 00:10:57 10/10
[local]R3.16.121#

[local]R2.17.145#sh ip route isis

Codes: C - connected, S - static, S dv - dvsr, R - RIP, e B - EBGP, i B - IBGP
A,H - derived hidden
O - OSPF, O3 - OSPFv3, IA - OSPF(v3) inter-area,
N1 - OSPF(v3) NSSA external type 1, N2 - OSPF(v3) NSSA external type
2
E1 - OSPF(v3) external type 1, E2 - OSPF(v3) external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, N - NAT
IPH - IP Host, SUB A - Subscriber address, SUB S - Subscriber static
MIP F - Mobile-IP Foreign Agent, MIP H - Mobile-IP Home Agent
A - Derived Default, MH - Media Nexthop
> - Active Route, * - LSP

Created by: Jerry Yu on: 05/02/2009 Page 31 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1

Type Network Next Hop Dist Metric UpTime Interface

> i L2 10.16.50.4/32 200.1.1.2 115 10 00:00:00 9/2
> i L2 10.16.50.20/30 200.1.1.2 115 10 00:00:00 9/2
> i L2 10.16.50.52/30 200.1.1.2 115 10 00:00:00 9/2
> i L2 10.16.83.34/32 200.1.1.2 115 10 00:00:00 9/2
i L2 10.192.16.0/23 200.1.1.2 115 10 9/2
> i L2 100.1.1.2/32 200.1.1.2 115 20 00:05:16 9/2
> i L2 118.1.1.0/24 200.1.1.2 115 20 00:05:16 9/2
[local]R2.17.145#

[local]R4#sh ip route isis

Codes: C - connected, S - static, S dv - dvsr, R - RIP, e B - EBGP, i B - IBGP
A,H - derived hidden
O - OSPF, O3 - OSPFv3, IA - OSPF(v3) inter-area,
N1 - OSPF(v3) NSSA external type 1, N2 - OSPF(v3) NSSA external type
2
E1 - OSPF(v3) external type 1, E2 - OSPF(v3) external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, N - NAT
IPH - IP Host, SUB A - Subscriber address, SUB S - Subscriber static
M F - Mobile Sub Foreign Agent, M H - Mobile Sub Home Agent
A - Derived Default, MeH - Media Nexthop
> - Active Route, * - LSP

Type Network Next Hop Dist Metric UpTime Interface

> i L2 10.16.50.4/32 118.1.1.2 115 10 00:00:12 14/11

> i L2 10.16.50.20/30 118.1.1.2 115 10 00:00:12 14/11
> i L2 10.16.50.52/30 118.1.1.2 115 10 00:00:12 14/11
> i L2 10.16.83.34/32 118.1.1.2 115 10 00:00:12 14/11
i L2 10.192.16.0/23 118.1.1.2 115 10 14/11
> i L2 100.1.1.2/32 118.1.1.2 115 20 00:04:46 14/11
> i L2 110.1.1.1/32 118.1.1.2 115 21 00:04:46 14/11
> i L2 200.1.1.0/24 118.1.1.2 115 20 00:04:46 14/11
[local]R4#

Created by: Jerry Yu on: 05/02/2009 Page 32 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
Advertising Summary Routes

Frequently, network operators attempt to summarize routing information by representing a set of routes
with one or a fewer number of prefixes than in the original set. This is good practice and helps save on
system resources, such as memory and network bandwidth. If many smaller prefixes are summarized into
one prefix, less space is required in the LSP to advertise those prefixes, and, therefore, less bandwidth is
needed to flood the smaller LSP throughout the area. When routes are summarized, they might become
part of an aggregate. Therefore, troubleshooting missing routes in such environments should involve
checking whether they are represented accurately by the summaries as intended.

3.2.6 Commonly used CLI for debugging IS-IS Route Problems

Enable the generation of IS-IS LSP debug messages. debug isis lsp-packets
Enable the generation of debug messages for events relating to interaction debug isis routes
between the
Routing Information Base (RIB) and IS-IS.
Enable the generation of debug messages related to IS-IS complete debug isis snp-packets
sequence number
protocol data units (CSNPs) and partial sequence number protocol data units
(PSNPs).
Enable the generation of debug messages for events related to SPF debug isis spf-events
computation within IS-IS.
Enable the generation of debug messages for events related to the causes debug isis spf-triggers
of triggered SPF
runs within IS-IS.
Display information about the IS-IS link-state database. show isis database
Display IS-IS protocol summary information. show isis protocol-
summary
Display IS-IS routes. show isis routes
Display a history of the IS-IS SPF calculation results. show isis spf-log
Display information about IS-IS IP summary addresses show isis summary-
address
Display IS-IS topology information. show isis topology

4 Summary
The network engineer should have a good understanding of the concepts behind a network protocol and
be able to apply that knowledge in troubleshooting scenarios, logical and practical, in the real world. This
guideline document focuses on troubleshooting IS-IS routing problems. The material presented
categorizes IS-IS failures into two main groups: adjacency problems and route maintenance problems.

The discussion about troubleshooting tools, such as show commands and debug commands, show you
how to review specific problems and examples. The various command and debug output examples
Created by: Jerry Yu on: 05/02/2009 Page 33 of 34
Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.
 IS-IS Troubleshooting Guide
CE-TG-0007 1.1
enable you to build up expertise in troubleshooting IS-IS routing problems and also serve as an excellent
reference source.

Created by: Jerry Yu on: 05/02/2009 Page 34 of 34

Updated by: jerryyu on: 2/4/2009 08:09:00 PM /conversion/tmp/activity_task_scratch/647234987.doc
Copyright 2009 Redback Networks Inc. All rights reserved.
Proprietary and Confidential.
No part of this publication may be used or reproduced in any form by any means without prior written permission from Redback Networks Inc.