IS IS Cisco

Note: This PowerPoint presentation is taken largely
from a presentation given by Gerry Redwine of Cisco

Systems.
Topics
• Link-state protocol fundamentals

• Overview of IS-IS
• Areas and levels
• NSAPs and LSP identifiers
• CLNS routing principles
• LSP Flooding
• IP routing specifics
• Configuration Commands
• Show Commands
• Debug Commands
Rick Graziani graziani@cabrillo.edu

Link State Routing Protocol
Fundamentals
About linkstate protocols
LSP for router-A
to B
to C to E
• In a link-state protocol, the network can be viewed as a jigsaw puzzle

• Each jigsaw piece holds one router
• Each router creates a packet which represents its own jigsaw piece
– This packet is called a Link State PDU (LSP)
About linkstate protocols
• These packets are flooded everywhere

• Therefore each router receives all pieces of the jigsaw
puzzle
• Each routers compute SPF algorithm to put the pieces
together
– Input: all jigsaw puzzle pieces (LSPs)
– Output: Area or network topology tree
Shortest Path Tree

The jigsaw puzzle
LSP for router-B

LSP for router-A
to A
to B
to E
to D
to C to E
to A to B
to A LSP for routerE to B
to D to C
LSP for router-D

LSP for router-C
All routers have same view
• All routers exchange all LSPs

• via a reliable flooding mechanism
• All routers store all LSPs in a so-called link-state database
(LSPDB)
• separate from the routing table (RIB)
• all routers should have exactly the same LSPDB, but
different RIBs

What to do with LSPs ?
• Each router ‘composes the jigsaw puzzle’ by executing

Dijkstra’s Shortest Path First algorithm (SPF)
– the topology is calculated as a Shortest Path Tree
(SPT), with itself as root
– each router computes a different SPT
• From the SPT the routing table is calculated

All routers have same LSPDB
RouterA’s LSPDB
lspB
lspA RouterB’s LSPDB
lspA lspB
lspE RouterE’s LSPDB
lspD lspB
lspC lspA lspE
lspD
lspC
lspE
lspD
lspC
lspA lspB lspB
lspA
lspE lspE
lspD lspD
lspC lspC
RouterC’s LSPDB RouterD’s LSPDB
Brief Overview of IS-IS
What is IS-IS ?
• IS stands for Intermediate System

• IS is “OSI speak” for router
• IS-IS is the Intermediate System to Intermediate System
intra-domain routing protocol
• IS-IS was defined in 1992 in the ISO/IEC
recommendation 10589
Rick Graziani graziani@cabrillo.edu 11

IS-IS for IP routing
• IS-IS was designed for OSI routing

• IS-IS is easily extendable
• Extensions for IP routing in rfc1195
– Also called “Integrated IS-IS”or “Dual IS-IS”
• Easy to extend for other protocols mainly IPv6

Only 4 types of IS-IS packets
• IS-IS Hello packet (IIH)

• Link State Packet (LSP)
• Partial Sequence Number Packet (PSNP)
• Complete Sequence Number Packet (CSNP)
• Packets are sometimes called Protocol Data Units (PDU in
OSI)

IS-IS Hello PDUs
• Also called IIHs

• Used for maintaining adjacencies
• Different on p2p links and LANs
• Different from ISHs and ESHs (ESIS)
• IIHs are padded to full MTU size

Link State PDUs
• Called LSPs
• Contains all info about one router
– adjacencies, connected IP prefixes, OSI endsystems,
area addresses, etc.
• One LSP per router (plus fragments)
• One LSP per LAN network

Sequence Number PDUs
• Partial (PSNP) and Complete (CSNP)

• Used when flooding the LSPDB
• PSNPs are like ACKs on p2p links
• CSNPs are used for LSPDB synchronization over LANs
• CSNP are also used to sync LSPDB over new p2p
adjacencies

Pseudonodes and network LSAs
• For SPF, the whole network must look like a collection of

nodes and point-to-point links
– Multi-access networks are different
• Assume a virtual node for the LAN
– this virtual node is called pseudonode. It is not a real
router, but just an extra LSP in the LSPDB

A pseudonode on a LAN
Physical view Logical view
DIS
DIS
LAN
Pseudonode

Who creates the pseudonode
• Created by Designated Router (DIS)

• No Backup Designated Router in IS-IS
• The DIS reports all LAN neighbors in the pseudonode
LSP; with metric 0
• All LAN routers report connectivity to the pseudonode in
their LSPs

Identifying nodes
• In IS-IS SystemIDs are 6 bytes. Nodes are identified by

7 bytes.
– A normal node (non-pseudonode) is identified by 6
bytes systemID plus a zero (e.g. 00c0.0040.1234.00-
00 )
– A pseudonode is identified by the systemID of the
DIS, plus 1 byte from the circuitID of the interface of
the DIS
– (e.g. 00c0.0040.1234.01-00 )

Areas and levels
21
Hierarchy
• IS-IS has 2 layers of hierarchy

– the backbone is called level-2
– areas are called level-1
• Same algorithms apply for L1 and L2
• A router can take part in L1 and L2
– inter-area routing (or inter-level routing)

Level-1 Routers
• Neighbors only in the same area

• L1 has information about own area
• L1-only routers look at the attach-bit (ATT) in L1 LSPs to
find the closest L1L2 router
• L1-only routers install a default route to the closest L1L2
router in the area

Level-2 routers
• May have neighbors in other areas

• L2 has information about L2 topology
• L2 has information what L1 destinations are reachable and
how to reach them via the L2 topology
• L2 routers often do also L1 routing
– so called L1L2 routers

Adjacency levels
L1-Adjacency L2-Adjacency
Router with adjacencies within
the same area.
However, needs to have a L2
database as well since it is a transit
node
Therefore L1L2 adjacency is required
L2-Adjacency
L2-Adjacency
L1L2 L1L2
Adjacency Adjacency

Level-1, Level-2 & Level-1-2 Routers
• Backbone MUST BE L2 contiguous
L1-only
L2-only
L1-L2
L1-only
L1-only
L1-L2
L1-L2
L1-only
This router has to behave as level2
as well in order to guarantee backbone
L1-L2 continuity
L1-only

Level-1, Level-2 & Level-1-2 Routers
• Backbone MUST BE L2 contiguous
L1-only
L2-only
L1-L2
L1-only
L1-L2
L1-L2
L1-L2
L1-only
This router has to behave as level2
as well in order to guarantee backbone
L1-L2 continuity
L1-only

NSAPs and LSPids
28
NSAPs and Addressing
• Network Service Access Point

• The NSAP is the network layer address for CLNS
packets
• One NSAP per box, not per interface (similar to DECnet)
• SNPA means SubNetwork Point of Attachment, which is
the layer2 or MAC address

How do I read an NSAP ?
• An NSAP consists of 3 parts

• area-address, systemID and n-selector
• Total length between 8 and 20 bytes
• example: 49.0001.0000.0000.0007.00

NETs versus NSAPs
• A NET is an NSAP with n-selector 0

• A NET implies the routing layer of the IS itself (no
transport layer)
• On routers we always deal with NETs
– We haven’t implemented TP4 (or another transport
layer)

Do I need an NSAP if I want to use IS-IS for
IP routing ?
• Yes, still needed for IP routing only

• Area address is like OSPF area nr
• SystemID is like an OSPF routerID
– LSP identifier is derived from systemID

Creating unique systemIDs
• SystemID is 6 bytes
• Start numbering 1, 2, 3, 4 …. etc
• Convert your loopback IP address
– 192.31.231.16 -> 192.031.231.016 -> systemID
1920.3123.1016

Creating area addresses
• If you do CLNS routing, request an official NSAP prefix

• If you do just IP routing, use AFI 49
• AFI 49 denotes private address space
– like network 10.0.0.0 in IP
• Just number your areas 49.0001… 49.0002….,
49.0003,… etc

LSP Identifier
• LSP identifier consists of 3 parts

• Source ID
• SystemID of router or DIS (if pseudonode)
• Pseudonode ID
• Router LSP = zero, Pseudonode LSP = non-
zero
• LSP number
• Fragmentation number
• Example: 00c0.0040.1234.02-00
SystemID PN-ID Frag-Nr

CLNS routing principles
36
OSI protocol family
• CLNS is datagram delivery protocol

– like bare IP service
– actually called CLNP
• ESIS is like ARP, ICMP, HSRP, IRDP
– between routers and hosts
• IS-IS and ISO-IGRP are the IGPs

OSI protocol family
• IS-IS is not encapsulated in CLNS

– and not encapsulated in IP (yet)
• Encapsulated directly in layer2
• Protocol family is OSI
– usually values like 0xFE or 0xFEFE
– (ppp uses 0x0023 and 0x8023)

Encapsulation of IS-IS
Datalink header ISIS fixed header

ISIS: (OSI family 0xFEFE) (first byte is 0x82)
ISIS TLVs
Datalink header ESIS fixed header

ESIS: (OSI family 0xFEFE) (first byte is 0x81)
ESIS TLVs
Datalink header CLNS header (with NSAPs)

CLNS: (OSI family 0xFEFE) (first byte is 0x80)
User data

Level-1 routing
• L1-only routers know only topology of their own area

(including all ISs and ESs in the area)
• Traffic to other areas is sent via the closest L2 IS
• L1L2 ISs set the “attached-bit” in their L1 LSP

Area addresses
• An area address is like a summary

• All L1 ISs and ESs in an area must have NSAPs that
start with the same area-address
• L1L2 routers advertise their area-addresses to L2
routers in other areas
• Multiple area-adresses possible

Level-2 Routing
• L2 routers know about other areas

– L2 area addresses and L2 routers
• When doing OSI routing, the L2 ISs must know their own
area. Therefore never use L2-only on OSI routers
– L2-only is possible when doing just IP

Level-2 Routing
• Transit traffic requires routers inside the area to know

about other areas
– routers in transit paths must be L1L2 routers to have
the full L2 LSDB
– similar to pervasive BGP requirement
• L2 routers must be contiguous

The Backbone
• A router can’t tell whether it is a transit node

– Therefore the cisco default is to be L1L2
– This will make the backbone larger then necessary
– So always configure L1-only or L2-only when possible
• L1L2 in one area is less scalable
– Especially with ISIS for IP

Can an IS determine its level ?
“I’m in area 2 and ALL
Area 1 my neighbors are in the
same area. I must be a Area 3
L1-only router ?”
Area 2 Area 4
!! NO !!
Rtr C must have a full L2 LSDB
to route between areas 1, 3 and
4. Remember, the backbone
must be contiguous.
ISIS router cannot determine if they need to be L1 or L1L2

Therefore By default all cisco routers will behave as L1L2
The Attached bit
L1-LSDB L1-LSDB
rtrA.00-00 ATT-bit rtrD.00-00 ATT-bit
L2-LSDB
rtrB.00-00 rtrE.00-00
rtr A rtrA.00-00
rtrC.00-00 rtrF.00-00
rtrD.00-00
rtr D
Area 2
Area 1
• L1L2 routers set the ATT bit in their L1 LSP

• L1 routers use ATT bit found in L1-LSDB as possible area exit point
– ISIS for IP: level-1 router will install a 0.0.0.0/0 route towards the
L1L2 with ATT-bit set
• Shortest metric to the L1L2 who sets the ATT bit wins

LSP flooding
47
Why do we need flooding
• All routers generate an LSP

• All LSPs need to be flooded to all routers in the network
– if LSPDB is not synchronised, routing loops or
blackholes might occur
• IS-IS’ two components are the SPF computation and
reliable flooding

What triggers a new LSP ?
• When something changes …

– Adjacency came up or went down
– Interface up/down (connected IP prefix !)
– Redistributed IP routes change
– Inter-area IP routes change
– An interface is assigned a new metric
– Most other configuration changes
– Periodic refresh

What to do with a new LSP ?
• Create new LSP, install in your own LSPDB and mark it for
flooding
• Send the new LSP to all neighbors
• Neigbors flood the LSP further

Basic flooding rules
• When receiving an LSP, compare with old version of

LSP in LSPDB
• If newer:
– install it in the LSPDB
– Acknowledge the LSP with a PSNP
– Flood to all other neighbors
– Check if need to run SPF

Basic flooding rules
• If same age:
• If older:
– Send our version of the same LSP
– Wait for PSNP

Sequence number
• Each LSP (and LSP fragment) has its own sequence

number
• When router boots, set seqnr to one
• When there is a change, the seqnr is incremented, a
new version of the LSP is generated with the new seqnr
• Higher seqnr means newer LSP

Remaining lifetime
• Used to age out old LSPs
• Periodic refresh needed to keep stable LSPs valid
• IS-IS counts down from 1200 sec to 0
– we allow start at 65535 sec (18.7h)
• When lifetime expires, the LSP is purged from the
network
– Header with lifetime = 0 is flooded

Flooding on a P2P Link
LSP
id=x seqnr=22
RouterA
Receives LSP
id=x seqNr=22 RouterB
It’s new. Put it in
the LSPDB
LSP
Now flood it: id=x seqnr=22
Set SRM bit. Received it. Local
Send over p2p. copy has seqNr = 21.
So the received one is
newer. Install it in LSDB.
Received ack PSNP Acknowledge it. Maybe
Clear SRMbit id=x seqnr=22 flood further.
The Designated Router
• DIS is like the DR in OSPF

• DIS is only on LANs, not on p2p
• DIS has two tasks
– create/update pseudonode LSP
– conduct flooding over the LAN
• DIS sends persiodic CSNPs
– LSPid, SeqNr, Checksum, Lifetime of all LSPs
present in the LSPDB

The Designated IS
• No Backup DIS in ISIS

– not necessary, no LSPDB resync
• DIS is elected by priority and MAC
– actually is “self-elected”
• LAN circuitID shows who is DIS
– use show clns interface

Flooding on a LAN
Rtr-A DIS
Received new LSP
id=x seqNr=22
LAN
Install in LSPDB.
LSP Flood the LSP.
!!! Problem !!! LSP
Dropped LSP id=x seqNr=22
Local copies of LSP-y and CSNP

LSP-z are up-to-date but id=y seqnr=... Periodic CSNP
local copy of LSP-x is older. id=x seqNr=22 every 10 secs
Request latest LSP-x via id=z ...
PSNP
PSNP
id=x seqNr=21 Neighbor has an
old LSP, better
resend him latest
Got it. Install and LSP
run SPF id=x seqNr=22
IP routing specifics
59
L1 advertised into L2
• All L1L2 routers advertise all the IP prefixes they learn

via L1 into L2
• Only advertise routes you use
– (inter-level routing goes via the RIB)
• Summarization possible
– - At L1->L2
– - when redistributing

L1 advertised into L2
• Level-1 preferred over Level-2

– In case of SAME routes (same prefix and same mask)
• Internal equal to external route type
– (TLV 128 versus TVL 130)
• Internal over external metric-type

ISIS routing Levels
L1 L1L2
2. Level-1 LSP with 3. Level-2 LSP with
IP prefix: 10.1.0.0/16 IP prefix: 10.1.0.0/16
IP prefix:
10.10.0.0/16
L1
2. Level-1 LSP with
IP prefix: 1. Level-1 LSP with
10.10.0.0/16 Attached-bit (used as
L1L2 a default route by all
level-1routers
L1
Routers within an area do not
have any routing information L1
about prefixes originated outside
the area. Default routing (ATTbit
or explicit 0.0.0.0/0) is used to reach
destinations outside the area.

ISIS routing Levels
3. Level-2 LSP with
IP prefix: 10.1.0.0/16
L2 0. Level-1 LSP with

3. Level-2 LSP with L2
ATT bit set
IP prefix: 10.1.0.0/16
L1
L1L2
2. Level-2 LSP with

IP prefix: 10.1.0.0/16 2. Level-2 LSP with
IP prefix: 10.1.0.0/16
L1L2
0. Level-1 LSP with 0. Level-1 LSP with L1L2
ATT bit set ATT bit set
4. At this point the prefix
L1 10.1.0.0/16 will NOT be inserted
1. Level-1 LSP with L1 in the L1 LSP (no route leaking
IP prefix: 10.1.0.0/16 by default)
2. At this point prefix
10.1.0.0/16 will be
10.1.0.0/16 is
inserted in L2 LSP

Configuration, Show,
& Debug Commands
64
Command Agenda
• Basic Configuration Commands

• Important Show Commands
• Useful Debug Commands

Basic Configuration
Commands
• Router sub-commands
–router isis <tag name>
–net <net>
–is-type <L1 L2 L1L2>
–default-information originate <route-map> (only for
L2)
–Hostname-dynamic

Basic Configuration
Commands
• Interface sub-commands
–ip router isis <tag name>
–clns router isis <tag name>
–isis metric <value>
–isis priority <value>
–isis circuit-type <L1 L2 L1L2>
–isis hello-interval <seconds>
–isis hello-multiplier <value>

Basic Configuration
L1router
Router-A
-------------- Router-B
-------------- S0 Rtr-A
interface Loopback0
interface Loopback0
ip address 192.168.1.5 255.255.255.255
ip address 192.168.1.1 255.255.255.255
!
interface Serial0
! Area 49.0001
Interface Serial0
ip address 192.168.120.5 255.255.255.0
ip address 192.168.120.10 255.255.255.0
ip router isis
ip router isis S1
!
router isis
! Rtr-B
interface Serial1
is-type level-1
ip address 192.168.222.1 255.255.255.0
passive-interface Loopback0
net 49.0001.1921.6800.1005.00
ip router isis S0
!
router isis
L1L2 routers
net 49.0001.1921.6800.1001.00
S1
S0 Rtr-C
Area 49.0002
S1
Rtr-D
L1router
Basic Configuration
L1router
Router-C Router-D
-------------- --------------
S0 Rtr-A
interface Loopback0 interface Loopback0
ip address 192.168.2.2 255.255.255.255 ip address 192.168.2.4 255.255.255.255
! !
interface Serial0 interface Serial1 Area 49.0001
ip address 192.168.111.2 255.255.255.0 ip address 192.168.111.4 255.255.255.0
ip router isis ip router isis S1
isis circuit-type level-1 !
! router isis Rtr-B
interface Serial1 is-type level-1
ip address 192.168.222.2 255.255.255.0
ip router isis
net 49.0002.1921.6800.2004.00
S0
isis circuit-type level-2
! L1L2 routers
router isis
passive-interface Loopback0 S1
net 49.0002.1921.6800.2002.00
S0 Rtr-C
Area 49.0002
S1
Rtr-D
L1router
Show clns
L1L2 routers
S0 S1
S1 Rtr-B S0 Rtr-C
Area 49.0001 Area 49.0002

S0 S1
Rtr-A
Rtr-D
L1routers
Rtr-B#show clns
Global CLNS Information:
2 Interfaces Enabled for CLNS
NET: 49.0001.1921.6800.1001.00
Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64
ERPDU's requested on locally generated packets
Running IS-IS in IP-only mode (CLNS forwarding not allowed)

Show clns protocol
L1router
S0 Rtr-A
Rtr-B# show clns protocol Area 49.0001
S1
IS-IS Router: <Null Tag> Rtr-B
System Id: 1921.6800.1001.00 IS-Type: level-1-2
S0
Manual area address(es):
49.0001 L1L2 routers
Routing for area address(es): S1
49.0001
Interfaces supported by IS-IS: S0 Rtr-C
Serial1 - IP
Serial0 - IP Area 49.0002
Redistribute:
static (on by default) S1
Distance for L2 CLNS routes: 110 Rtr-D
L1router
show clns neighbors
L1L2 routers
S0 S1
S1 Rtr-B S0 Rtr-C
Area 49.0001 Area 49.0002

S0 S1
Rtr-A
Rtr-D
L1routers
Rtr-B# show clns neighbors
System Id Interface SNPA State Holdtime Type Protocol

Rtr-C Se0 *HDLC* Up 23 L2 IS-IS
1921.6800.1005 Se1 *HDLC* Up 21 L1 IS-IS

Show clns interface
L1router
Rtr-B# show clns int serial1
Serial1 is up, line protocol is up S0 Rtr-A
Checksums enabled, MTU 1500, Encapsulation HDLC
ERPDUs enabled, min. interval 10 msec. Area 49.0001
CLNS fast switching enabled S1
CLNS SSE switching disabled Rtr-B
DEC compatibility mode OFF for this interface
S0
Next ESH/ISH in 47 seconds
Routing Protocol: IS-IS L1L2 routers
Circuit Type: level-1-2 S1
Interface number 0x2, local circuit ID 0x101
Level-1 Metric: 10, Priority: 64, Circuit ID: 1921.6800.1005.00 S0 Rtr-C
Number of active level-1 adjacencies: 1
Level-2 Metric: 10, Priority: 64, Circuit ID: Rtr-B.01 Area 49.0002
Next IS-IS Hello in 6 seconds S1
Rtr-D
L1router
Show clns interface
L1router
Rtr-B# show clns int serial0 S0 Rtr-A
Serial0 is up, line protocol is up

Area 49.0001
Checksums enabled, MTU 1500, Encapsulation HDLC
ERPDUs enabled, min. interval 10 msec. S1
Rtr-B
CLNS fast switching enabled
CLNS SSE switching disabled S0
DEC compatibility mode OFF for this interface L1L2 routers
Next ESH/ISH in 30 seconds S1
Routing Protocol: IS-IS
Circuit Type: level-1-2 Rtr-C
S0
Interface number 0x1, local circuit ID 0x100
Level-1 Metric: 10, Priority: 64, Circuit ID: Rtr-C.01 Area 49.0002
Level-2 Metric: 10, Priority: 64, Circuit ID: Rtr-B.00 S1
Number of active level-2 adjacencies: 1 Rtr-D
Next IS-IS Hello in 6 seconds
L1router
Show isis database
L1L2 routers
S0 S1
S1 Rtr-B S0 Rtr-C
Area 49.0001 Area 49.0002

S0 S1
Rtr-A
Rtr-D
L1routers
Rtr-B# show isis database
IS-IS Level-1 Link State Database:

LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
Rtr-B.00-00 * 0x00000020 0x0C24 674 1/0/0
1921.6800.1005.00-00 0x00000023 0x909E 830 0/0/0
1921.6800.1005.01-00 0x00000017 0xC896 841 0/0/0
IS-IS Level-2 Link State Database:

Rtr-B.00-00 * 0x00000024 0x7D98 748 0/0/0
Rtr-C.00-00 0x00000028 0x1E01 1128 0/0/0

Show isis database detail
Rtr-B# show isis database 1921.6800.1001.00-00 detail

IS-IS Level-1 LSP Rtr-B.00-00
Rtr-B.00-00 * 0x00000020 0x0C24 424 1/0/0
Area Address: 49.0001
NLPID: 0xCC
Hostname: Rtr-B
IP Address: 192.168.1.1
Metric: 0 IP 192.168.1.1 255.255.255.255
Metric: 10 IP 192.168.222.0 255.255.255.0
Metric: 10 IP 192.168.120.0 255.255.255.0
Metric: 10 IS 1921.6800.1005.00
IS-IS Level-2 LSP Rtr-B.00-00

Rtr-B.00-00 * 0x00000025 0x7B99 1186 0/0/0
Area Address: 49.0001
NLPID: 0xCC
Hostname: Rtr-B
IP Address: 192.168.1.1
Metric: 10 IS Rtr-C.00
Metric: 10 IP 192.168.120.0 255.255.255.0
Metric: 0 IP 192.168.1.1 255.255.255.255
Metric: 20 IP 192.168.1.5 255.255.255.255
Metric: 10 IP 192.168.222.0 255.255.255.0
Show isis lsp-log
L1router
Rtr-B# show isis lsp-log
S0 Rtr-A
Level 1 LSP log
When Count Interface Triggers Area 49.0001
01:50:44 1 CONFIG
01:50:35 1 Loopback0 IPUP S1
01:50:28 1 Serial0 IPUP Rtr-B
01:50:20 1 Serial1 IPUP
01:50:20 1 Serial1 NEWADJ S0
01:50:18 1 ATTACHFLAG L1L2 routers
01:36:49 1 Loopback0 CONFIG
S1
Level 2 LSP log
When Count Interface Triggers S0 Rtr-C
01:50:46 1 CONFIG
01:50:36 1 Loopback0 IPUP
01:50:30 2 Serial0 NEWADJ IPUP Area 49.0002
01:50:22 1 Serial1 IPUP
01:50:10 1 IPIA S1
01:48:21 1 Serial0 DELADJ Rtr-D
01:48:16 1 Serial0 NEWADJ
01:36:51 1 Loopback0 CONFIG
L1router
Show isis spf-log
L1router
Rtr-B# show isis spf-log S0 Rtr-A
Level 1 SPF log

Area 49.0001
When Duration Nodes Count First trigger LSP Triggers
02:16:52 0 1 1 Rtr-B.00-00 NEWLSP S1
02:16:42 0 1 1 Rtr-B.00-00 TLVCODE Rtr-B
02:16:32 0 1 2 Rtr-B.00-00 NEWADJ TLVCONTENT
02:16:22 8 3 4 Rtr-B.00-00 ATTACHFLAG LSPHEADER S0
TLVCON TENT
02:02:57 4 3 1 Rtr-B.00-00 TLVCONTENT L1L2 routers
02:01:52 8 3 1 PERIODIC S1
01:46:52 8 3 1 PERIODIC
01:31:53 8 3 1 PERIODIC
01:16:52 8 3 1 PERIODIC S0 Rtr-C
01:01:52 8 3 1 PERIODIC
00:46:52 8 3 1 PERIODIC
00:31:51 8 3 1 PERIODIC Area 49.0002
00:16:51 8 3 1 PERIODIC
00:01:50 64 3 1 PERIODIC S1
Rtr-D
L1router
Show isis spf-log
L1router
S0 Rtr-A
Area 49.0001
Level 2 SPF log S1

When Duration Nodes Count First trigger LSP Triggers Rtr-B
02:16:54 0 1 1 Rtr-B.00-00 NEWLSP
S0
02:16:44 0 1 1 Rtr-B.00-00 TLVCODE
02:16:34 8 2 3 Rtr-B.00-00 NEWADJ NEWLSP TLVCONTENT L1L2 routers
02:14:29 8 2 3 Rtr-B.00-00 NEWADJ TLVCONTENT
02:14:23 4 2 1 Rtr-C.00-00 TLVCODE S1
02:13:56 8 2 1 Rtr-C.00-00 TLVCONTENT
02:02:59 4 2 1 Rtr-B.00-00 TLVCONTENT Rtr-C
S0
02:01:54 4 2 1 PERIODIC
01:46:54 4 2 1 PERIODIC
01:31:54 4 2 1 PERIODIC Area 49.0002
01:16:54 4 2 1 PERIODIC
01:01:54 4 2 1 PERIODIC S1
00:46:53 4 2 1 PERIODIC
00:31:53 4 2 1 PERIODIC Rtr-D
00:16:53 4 2 1 PERIODIC
00:01:53 60 2 1 PERIODIC
L1router
Show clns traffic
• LSPs sourced indicates stability of IS

• LSP retransmissions should stay low
• PRCs can not be checked elsewhere
• LSP checksum errors are a bad sign
• Update queue should not stay full
• Update queue should not drop much

Show clns traffic
L1router
S0 Rtr-A
Rtr-B# show clns traffic
CLNS: Time since last clear: never
CLNS & ESIS Output: 669, Input: 4773 Area 49.0001
CLNS Local: 0, Forward: 0 S1
CLNS Discards: Rtr-B
Hdr Syntax: 0, Checksum: 0, Lifetime: 0, Output cngstn: 0
No Route: 0, Discard Route: 0, Dst Unreachable 0, Encaps. Failed: 0 S0
NLP Unknown: 0, Not an IS: 0
CLNS Options: Packets 0, total 0 , bad 0, GQOS 0, cngstn exprncd 0 L1L2 routers
CLNS Segments: Segmented: 0, Failed: 0 S1
CLNS Broadcasts: sent: 0, rcvd: 0
Echos: Rcvd 0 requests, 0 replies Rtr-C
Sent 0 requests, 0 replies S0
ESIS(sent/rcvd): ESHs: 0/0, ISHs: 669/660, RDs: 0/0, QCF: 0/0
ISO-IGRP: Querys (sent/rcvd): 0/0 Updates (sent/rcvd): 0/0 Area 49.0002
ISO-IGRP: Router Hellos: (sent/rcvd): 0/0
ISO-IGRP Syntax Errors: 0 S1
Rtr-D
IS-IS: Time since last clear: never
IS-IS: Level-1 Hellos (sent/rcvd): 282/0
L1router
Show clns traffic
L1router
IS-IS: Level-2 Hellos (sent/rcvd): 285/0 S0 Rtr-A

IS-IS: PTP Hellos (sent/rcvd): 420/415
IS-IS: Level-1 LSPs sourced (new/refresh): 8/2 Area 49.0001
IS-IS: Level-2 LSPs sourced (new/refresh): 9/1
IS-IS: Level-1 LSPs flooded (sent/rcvd): 5/8 S1
IS-IS: Level-2 LSPs flooded (sent/rcvd): 7/8 Rtr-B
IS-IS: LSP Retransmissions: 0
S0
IS-IS: Level-1 CSNPs (sent/rcvd): 1/1
IS-IS: Level-2 CSNPs (sent/rcvd): 2/2 L1L2 routers
IS-IS: Level-1 PSNPs (sent/rcvd): 7/4
S1
IS-IS: Level-2 PSNPs (sent/rcvd): 7/5
IS-IS: Level-1 DR Elections: 1
IS-IS: Level-2 DR Elections: 1 S0 Rtr-C
IS-IS: Level-1 SPF Calculations: 7
IS-IS: Level-2 SPF Calculations: 9
Area 49.0002
IS-IS: Level-1 Partial Route Calculations: 1
IS-IS: Level-2 Partial Route Calculations: 5
S1
IS-IS: LSP checksum errors received: 0
IS-IS: Update process queue depth: 0/200 Rtr-D
IS-IS: Update process packets dropped: 0
L1router
Debug isis adj-packets
L1L2 routers
S0 S1
S1 Rtr-B S0 Rtr-C
Area 49.0001 Area 49.0002

S0 S1
Rtr-A
Rtr-D
L1routers
Rtr-B# debug isis adj-packets
IS-IS Adjacency related packets debugging is on
Rtr-B#
05:45:21: ISIS-Adj: rcvd state UP, old state UP, new state UP
05:45:21: ISIS-Adj: Action = ACCEPT
05:45:24: ISIS-Adj: Sending serial IIH on Serial0, length 1499
05:45:26: ISIS-Adj: Rec serial IIH from *HDLC* (Serial1), cir type L1, cir id 00
, length 1499
05:45:26: ISIS-Adj: rcvd state UP, old state UP, new state UP
05:45:26: ISIS-Adj: Action = ACCEPT
05:45:26: ISIS-Adj: Sending serial IIH on Serial1, length 1499
05:45:31: ISIS-Adj: Rec serial IIH from *HDLC* (Serial0), cir type L1L2, cir id
01, length 1499
Debug isis snp-packets
L1L2 routers
S0 S1
S1 Rtr-B S0 Rtr-C
Area 49.0001 Area 49.0002

S0 S1
Rtr-A
Rtr-D
Rtr-B# debug isis snp-packets L1routers
IS-IS CSNP/PSNP packets debugging is on
07:51:59: ISIS-Snp: Build L2 PSNP entry for 1921.6800.2002.00-00, seq 35

07:51:59: ISIS-Snp: Sending L2 PSNP on Serial0
07:53:50: ISIS-Snp: Rec L1 PSNP from 1921.6800.1005 (Serial1)
07:53:50: ISIS-Snp: PSNP entry 1921.6800.1001.00-00, seq 31, ht 1197
07:53:50: ISIS-Snp: Same entry 1921.6800.1001.00-00, seq 31
07:54:26: ISIS-Snp: Build L1 PSNP entry for 1921.6800.1005.00-00, seq 2F
07:54:26: ISIS-Snp: Sending L1 PSNP on Serial1
07:55:18: ISIS-Snp: Rec L2 PSNP from 1921.6800.2002 (Serial0)
07:55:18: ISIS-Snp: PSNP entry 1921.6800.1001.00-00, seq 32, ht 1197
07:55:18: ISIS-Snp: Same entry 1921.6800.1001.00-00, seq 32

Debug isis spf-triggers
L1router
Rtr-B# debug isis spf-triggers
IS-IS SPF triggering events debugging is on S0 Rtr-A
Rtr-B#
07:32:10: ISIS-Spf: L1 SPF needed, periodic SPF, from 0x356C8DC Area 49.0001
07:32:10: ISIS-Spf: L2 SPF needed, periodic SPF, from 0x356C8DC
Rtr-B#conf t S1
Rtr-B(config)#int serial0 Rtr-B
Rtr-B(config-if)#isis metric 15
Rtr-B(config-if)# ^Z S0
07:38:27: ISIS-Spf: L1 SPF needed, new metric, from 0x3560762
Rtr-B(config)#int serial0 L1L2 routers
Rtr-B(config-if)#shut S1
Rtr-B(config-if)# ^Z
07:39:23: ISIS-Spf: L2, 1921.6800.1001.00-00 TLV contents changed, code 0x2
S0 Rtr-C
07:39:28: ISIS-Spf: L1 SPF needed, L2 attach changed, from 0x357CF36
07:39:28: ISIS-Spf: L1, LSP fields changed 1921.6800.1001.00-00
Area 49.0002
S1
Rtr-D
L1router
Lab Topology
L1L2 L1L2
R2 R3
1
.0 00
L1 L1
49
R4
49.0002 R5
L1
R1

Lab Instructions
1. Configure R1 and R2 to belong to the same area. Configure each to route

CLNS and IP data. Configure the serial link to only form L1 adjacencies.
2. Configure R2 and R3 to form an L2 adjacency; IP only.
3. Configure R3, R4 and R5 to belong to the same area; IP only.
4. Configure R5 so its systemID will be used to build the Psuedonode for the
ethernet segment.

Lab Exercise
1. What command can be used to confirm the R1 and R2 are enabled

to route IP and CLNS packets?
2. What command did you issue to verify that only an L2 adjacency was
formed between R2 and R3?
3. Is the ATT bit set in area 49.0002? If so, what command should you
use to confirm it has been set?
4. What command do you use to display the Pseudonode LSP of the
ethernet segment? What is the metric to each of the nodes listed?
5. Determine if R1 displays the IP subnet of the ethernet segment in
area 49.0002. If it does not display the route, why not?

Course Number
Presentation_ID © 2000, Cisco Systems, Inc. 89

IS IS Cisco

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IS IS Cisco

Caricato da

Copyright:

Formati disponibili

Note: This PowerPoint presentation is taken largely

from a presentation given by Gerry Redwine of Cisco

• Link-state protocol fundamentals

Rick Graziani graziani@cabrillo.edu

LSP for router-A

• In a link-state protocol, the network can be viewed as a jigsaw puzzle

• These packets are flooded everywhere

Rick Graziani graziani@cabrillo.edu

LSP for router-B

LSP for router-D

• All routers exchange all LSPs

Rick Graziani graziani@cabrillo.edu

• Each router ‘composes the jigsaw puzzle’ by executing

Rick Graziani graziani@cabrillo.edu

• IS stands for Intermediate System

Rick Graziani graziani@cabrillo.edu 11

• IS-IS was designed for OSI routing

Rick Graziani graziani@cabrillo.edu 12

• IS-IS Hello packet (IIH)

Rick Graziani graziani@cabrillo.edu 13

• Also called IIHs

Rick Graziani graziani@cabrillo.edu 14

Rick Graziani graziani@cabrillo.edu 15

• Partial (PSNP) and Complete (CSNP)

Rick Graziani graziani@cabrillo.edu 16

• For SPF, the whole network must look like a collection of

Rick Graziani graziani@cabrillo.edu

Physical view Logical view

Rick Graziani graziani@cabrillo.edu

• Created by Designated Router (DIS)

Rick Graziani graziani@cabrillo.edu 19

• In IS-IS SystemIDs are 6 bytes. Nodes are identified by

Rick Graziani graziani@cabrillo.edu 20

• IS-IS has 2 layers of hierarchy

Rick Graziani graziani@cabrillo.edu

• Neighbors only in the same area

Rick Graziani graziani@cabrillo.edu

• May have neighbors in other areas

Rick Graziani graziani@cabrillo.edu

Rick Graziani graziani@cabrillo.edu

Rick Graziani graziani@cabrillo.edu

Rick Graziani graziani@cabrillo.edu

• Network Service Access Point

Rick Graziani graziani@cabrillo.edu

• An NSAP consists of 3 parts

Rick Graziani graziani@cabrillo.edu 30

• A NET is an NSAP with n-selector 0

Rick Graziani graziani@cabrillo.edu

• Yes, still needed for IP routing only

Rick Graziani graziani@cabrillo.edu

Rick Graziani graziani@cabrillo.edu 33

• If you do CLNS routing, request an official NSAP prefix

Rick Graziani graziani@cabrillo.edu 34

• LSP identifier consists of 3 parts

Rick Graziani graziani@cabrillo.edu

• CLNS is datagram delivery protocol

Rick Graziani graziani@cabrillo.edu 37

• IS-IS is not encapsulated in CLNS

Rick Graziani graziani@cabrillo.edu 38

Datalink header ISIS fixed header

Datalink header ESIS fixed header

Datalink header CLNS header (with NSAPs)