IS-IS Protocol

IS-IS Introduction
Session Number
Presentation_ID
2003 Cisco Systems, Inc. All rights reserved.
Agenda
IS-IS Overview
Flooding
CLNS Addressing
Configuration
IS-IS Levels
New Features
IS-IS PDUs
Deployment Scenarios
LSP Header
RST-208
3010_05_2001_c1
Presentation_ID
2001, Cisco Systems,

2003Inc.
Cisco
AllSystems,
rights reserved.
Inc. All rights reserved.
IS-IS Overview
Session Number
Presentation_ID
Terminology
AFI: Authority and Format Identifier (the first octet of all OSI NSAP
addressesidentifies format of the rest of the address)
CLNP: Connection-Less Network Protocol (ISO 8473the OSI
connectionless network layer protocolvery similar to IP)
ES: End System (the OSI term for a host)
IS: Intermediate System (the OSI term for a router)
ES-IS: End System to Intermediate System routing exchange
protocol
(ISO 9542OSI protocol between routers and end systems)
IS-IS: Intermediate System to Intermediate System routing
exchange protocol (the ISO protocol for routing within a single
routing domain)
IS-IS Hello: A Hello packet (defined by the IS-IS protocol)
LSP: Link State Packet (a type of packet used by the IS-IS protocol)
TLV: Type Length Value
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
IS-IS Overview
IS-IS was originally designed for use as a dynamic
routing protocol for the ISO Connectionless
Network Protocol (CLNP); (ISO10589 or RFC 1142)
Adapted for routing IP in addition to CLNP
(RFC1195) as integrated or dual IS-IS
IS-IS is a Link State Protocol similar to the Open
Shortest Path First (OSPF)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
IS-IS Overview (Cont.)

IS-IS is an Interior Gateway Protocol (IGP) used for
routing within an Autonomous System (AS) also
referred to as a routing domain
BGP is normally used dynamic routing between IP
domains
ISO-IGRP is a Cisco proprietary routing protocol
that can be used between CLNP domains
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.

3 network protocols play together to deliver the ISO
defined Connectionless Network Service
CLNP
IS-IS
ES-ISEnd System to Intermediate System
Protocol
All 3 protocols independently ride over layer 2
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.

CLNP is the ISO equivalent of IP for datagram
delivery services (ISO 8473, RFC 994)
IS-IS carries routing information; integrated IS-IS
works within the ISO CNLS framework if even used
for routing IP (ISO 8473, RFC 1142)
ES-IS is a dynamic protocol for discovering layer 2
adjacencies (ISO9542, RFC 995); hosts and routers
discover each other via ES-IS
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
CLNS Addressing
Session Number
Presentation_ID
CLNS Addressing
Area
ID
SEL
CLNS addressing consists of 3 parts:

Areavariable
ID
SEL(ector)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
10
NSAPs and Addressing

ISO/IEC 10589 distinguishes only 3 fields in the NSAP
address format
DSP
IDP
AFI
IDI
High Order DSP
System ID
NSEL
6 Bytes
1 Byte
Variable Length Area Address
Area address: Variable length field composed of high order octets

of the NSAP excluding the SystemID and SEL fields
SystemID: Defines an ES or IS in an area; Cisco implements
a fixed length of 6 octets for the SystemID
NSEL: Selector, also designated as N-selector; it is the last
byte of the NSAP and identifies a network service user (transport
entity or the IS network entity itself)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
11
NSAPs and Addressing (Cont.)

NSAP: Network Service Access Point
An NSAP has an address that consists of 3 parts
Variable length area-address
6 Byte system ID
Byte n-selector (indicating transport layer)
Total length between 8 and 20 bytes
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
12
NETs versus NSAPs

NET: Network Entity Title
Is the address of the network entity itself
A NET is an NSAP where n-selector is 0 (common
practice)
A NET implies the routing layer of the IS itself
(no transport layer)
ISs (routers) do not have any transport layer
(selector=0)
Multiple NETs are like secondary IP addresses; only
use them when merging or splitting areas
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
13
OSI AddressingNET and System Identifier

Rules
NET must begin with an octet
47.xxxx....;
0111.xxxx... Not 111.xxxx...
NET must end with a single octet set to 00, identifying network
entity (for example, router) itself
...xxxx.00
System ID normally six octets (on Cisco six!) and has to be the
same length everywhere
Examples:
RST-208
3010_05_2001_c1
Presentation_ID
47.0001.0000.0c12.3456.00
01.1921.6811.1003.00
1047.0001.1234.5678.9101.00

2003Inc.
Cisco
AllSystems,
rights reserved.
14
CLNS Addressing: NSAP Examples

Example 1:
47.0001.aaaa.bbbb.cccc.00
Area = 47.0001, SysID = aaaa.bbbb.cccc, NSel = 00
Example 2:
39.0f01.0002.0000.0c00.1111.00
Area = 39.0f01.0002, SysID = 0000.0c00.1111, NSel = 00
Example 3:
49.0002.0000.0000.0007.00
Area = 49.0002, SysID = 0000.0000.0007, Nsel = 00
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
15
Identifying Systems in IS-IS

The area address uniquely identifies the routing
area and the System ID identifies each node
All routers within an area must use the same area
address
An ES may be adjacent to a level-1 router only if they
both share a common area address
Area address is used in level-2 routing
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
16
Identifying Systems in IS-ISSystem ID

System ID may be the MAC address (CLNS) or IP
address of an interface (IP world)
System ID used in level-1 routing and has to be unique
within an area (and of same length)
System ID has to be unique within level-2 routers that
form routing domain
General recommendation: domain-wide unique System ID
RST-208
3010_05_2001_c1
Presentation_ID
17

2003Inc.
Cisco
AllSystems,
rights reserved.
CLNS Addressing: NSAP Examples (Cont.)

39.0f01.0003.6666.6666.6666.00
39.0f01.0002.4444.4444.4444.00
39.0f01.0002.3333.3333.3333.00
39.0f01.0004.7777.7777.7777.00
39.0f01.0001.2222.2222.2222.00
39.0f01.0001.1111.1111.1111.00
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
18
CLNS Addressing: How Do Most ISP Define

System IDs?
The LOOPBACK IP Address: 192.168.3.25
The AREA the Router Under Is: 49.0001
IP Address Conversion Process to System ID:
192.168.3.25
192.168.003.025
1921.6800.3025
49.0001.1921.6800.3025
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
19
IS-IS Levels
Session Number
Presentation_ID
20
Areas and Backbone Routers

IS-IS has a 2 layer hierarchy
The backbone (Level 2)
The areas (Level 1)
An IS can be
Level 1 router (intra-area routing)
Level 2 router (inter-area routing)
Level 1-2 router (intra and inter-area routing)
For each level (1 and 2) a DIS will be elected on

LANs
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
21
Areas and Backbone Routers (Cont.)

Level 1 router
Has neighbors only on the same area
Has the Level 1 LSDB with all routing information for the
area
Use the closest Level 2 router to exit the area
This may result in sub-optimal routing
Level 2 router
May have neighbors in other areas
Has a Level 2 LSDB with all information about inter-area
routing
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
22

Level 12 router
May have neighbors on any area
Has two LSDBs:
Level 1 for the intra-area routing
Level 2 for the inter-area routing
If the router has adjacencies to other areas,
it will inform the Level 1 routers (intra-area)
it is a potential exit point for the area
RST-208
3010_05_2001_c1
Presentation_ID
23

2003Inc.
Cisco
AllSystems,
rights reserved.

Area 49.001
L1
L1L2
Area 49.003
Area 49.0002
L1
RST-208
3010_05_2001_c1
Presentation_ID
L1L2

2003Inc.
Cisco
AllSystems,
rights reserved.
L1L2
L1
24

Backbone must be L2 contiguous
Area 3
L1 Only
L1L2
Area 2
L2 Only
L1L2
L1 Only
L1L2
Area 4
L1L2
L1 Only
Area 1
L1L2
L1 Only
RST-208
3010_05_2001_c1
Presentation_ID
25

2003Inc.
Cisco
AllSystems,
rights reserved.

Area 1
Router A
Im in area 2 and ALL

my neighbors are in the
same area. I must be a
L1-only router ?
Area 2
Router B
Area 2
Router C
!! NO !!
Router C must have a full L2 LSDB
to route between areas 1, 3, and 4.
Remember, the backbone must be
contiguous.
Area 3
Router F
Area 2
Router D
Area 2
Router E
Area 4
Router G
Remember, the Backbone Must Be Contiguous:

IS-IS Router Cannot Determine If They Need to Be L1 or L1L2,
So All Routers Try to Be a L1L2 IS by Default
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
26
Example #1: Area ConfigurationPhysical

View
R2 and R3 belong to their respective level-1 areas
and provide a physical connection between them
L1L2 routers
R2
R3
Area-1
Area-2
R4
R1
L1 routers
RST-208
3010_05_2001_c1
Presentation_ID
27

2003Inc.
Cisco
AllSystems,
rights reserved.
Example #1: Area ConfigurationLogical

View
R2 and R3 are still L1 routers, but, in addition, they provide an
entry point to the level-2 backbone interconnecting both level-1
areas
R2
L2
R3
L2
L1
L1
L1
R1
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
R4
28
Example #2: L2 and L1/L2 Routers Forming L2

Backbone
This
This router
router must
must behave
behave as
as level
level 22 as
as well
well in
in order
order
to
to guarantee
guarantee backbone
backbone continuity.
continuity.
Area-3
L2-only
L1L2
L1-only
L1L2
L1L2
Area-2
L1-only
Area-4
L1L2
L1-only
L1L2
Backbone
links
RST-208
3010_05_2001_c1
Presentation_ID
Area-1
L1-only
IS-IS domain

2003Inc.
Cisco
AllSystems,
rights reserved.
29
SPF (Dijkstra) and Partial Route Calculation

SPF (Dijkstra) is run when topology has to be
calculated (SPF tree)
PRC (Partial Route Calculation) is executed when IP
routing information has to be calculated
If an IS receives an LSP where only IP information
has changed, it will run PRC only (less CPU)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
30
IS-IS PDUs
Session Number
Presentation_ID
31
IS-IS PDUs
IS-IS packets are encapsulated directly in a datalink frame
There is no CLNS or IP header
Hello PDUs (IIH, ISH, ESH)
LSP
Non-pseudonode LSP
Pseudonode LSPs
CSNP
PSNP
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
32
Encapsulation
IS-IS
Datalink Header
(OSI Family
0xFEFE)
IS-IS Fixed Header

(First Byte Is 0x83)
IS-IS TLVs
ESIS
Datalink Header
(OSI Family 0xFEFE)
ESIS Fixed Header

(First Byte is 0x81)
ESIS TLVs
CLNS
Datalink Header
(OSI Family 0xFEFE)
CLNS Header (with NSAPs)

(First Byte Is 0x80)
RST-208
3010_05_2001_c1
Presentation_ID
User Data
33

2003Inc.
Cisco
AllSystems,
rights reserved.
Mac Layer Addresses

On LANs IS-IS PDUs are forwarded to the following
well known MAC layer broadcast addresses
RST-208
3010_05_2001_c1
Presentation_ID
AllL1ISs
01-80-C2-00-00-14
AllL2ISs
01-80-C2-00-00-15
AllIntermediateSystems
09-00-2B-00-00-05
AllEndSystems
09-00-2B-00-00-04

2003Inc.
Cisco
AllSystems,
rights reserved.
34
Hello PDUs
IIHs are between routers (IS-IS)
Exchanged by ISs to form adjacencies
Point-to-point IIH
Level 1 LAN IIH
Level 2 LAN IIH
Multipoint and P2P IIHs are padded to full MTU Size

Useful to detect MTU inconsistencies
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
35
Hello PDUs (Cont.)

Point-to-Point IS-IS Hello
Circuit-type:
1Level 1 only
2Level 2 only (no IS-ES hello)
3Level 12
Source ID: Transmitting routers network layer address

Holding time: Time at which neighbors can legally declare this
route dead if they havent gotten a hello from it
Packet length: The length of the entire IS-IS hello message
Local circuit ID: Identifier to the interface and unique relative
to the transmitting routers other interfaces
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
36
Hello PDUs (Cont.)

LAN IS-IS Hello
Priority: The transmitting routers priority for
becoming designated router on the LAN, with
higher #s having a higher priority
LAN ID: The name of the LAN as assigned by the
DIS; it consists of DIS-ID + extra octet to
differentiate this LAN from others with the same
DIS
RST-208
3010_05_2001_c1
Presentation_ID
37

2003Inc.
Cisco
AllSystems,
rights reserved.
Hello PDUs (Cont.)
ES Sends ESH
IS Send ISH for ES
IS-IS Adjacency through IIH
ISs send IIH to establish IS-IS adjacencies
ISs listen to ESH to discover ESs
ISs send ISH for ESs
Es sends ESH and listen to ISH
ESs select IS as default router by listening to ISH
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
38
Node and Pseudonode LSP

2 kinds of Link State PDUs
Non-Pseudonodes represent routers
Pseudonodes represents LANs
(created by the DIS)
A Level 1 router will create a Level 1 LSP

A Level 2 router will create a Level 2 LSP
A Level 12 router will create
A Level 1 LSP and a Level 2 LSP
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
39
Non-Pseudonode LSP Generation

Each IS will create and flood a new NonPseudonode LSP
When a new neighbor comes up or goes away
When new IP prefixes are inserted or removed
When the metric of a link did change
When refresh interval timer expires
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
40
Pseudonode LSP Generation

The DIS will create and flood a new Pseudonode
LSP
When a new neighbor comes up or goes away
When refresh interval timer expires
Pseudonode LSP is created by the DIS

One for each level (Level 1 and/or Level 2)
One for each LAN
Reduces adjacencies and flooding over LAN

subnets
RST-208
3010_05_2001_c1
Presentation_ID
41

2003Inc.
Cisco
AllSystems,
rights reserved.
Pseudonode LSP Generation (Cont.)

DIS
DIS
PSN
Broadcast link represented as virtual node, referred to as Pseudonode (PSN)

PSN role played by the Designated Router (DIS)
DIS election is preemptive, based on interface priority with highest MAC
address being tie breaker
IS-IS has only one DIS; DIS helps routers on broadcast link
to synchronize their IS-IS databases
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
42
LSPDB without Pseudonode

LSP for Router B
IS: 10 A
10 C
10 D
ES: 10 E
LSP for Router A

IS: 10 B
10 C
10 D
ES: 10 E
LSP for Router D

IS: 10 A
10 B
10 C
ES: 10 E
LSP for Router C

IS: 10 A
10 B
10 D
ES: 10 E
EndSystem E
RST-208
3010_05_2001_c1
Presentation_ID
43

2003Inc.
Cisco
AllSystems,
rights reserved.
Pseudonode in the LSPDB
LSP for Router A

IS: 10 P
LSP for Router A

IS: 10 P
LSP for the
Pseudonode P
IS: 0 A
0B
0C
0D
ES: 0 E
LSP for Router A

IS: 10 P
LSP for Router A

IS: 10 P
EndSystem E
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
44
Neighbors and Adjacencies

IIH (IS-IS Hello) between routers
Two types of HELLOS on LANL1 and L2
Only one on p2p (with the type of desired adjacency
describedL1, L2 or both)
HELLOS sent every 10 seconds, holdtime 30 seconds
(default)
Separate adjacencies are built for L1 and L2 routers

L1/L2 routers keep two tables
Routers form adjacencies with all other routers

and send LSPs to all routers on the LAN (unlike
OSPF routers)
RST-208
3010_05_2001_c1
Presentation_ID
45

2003Inc.
Cisco
AllSystems,
rights reserved.
LAN Adjacencies
Adjacencies are established based on the area address announced in
the incoming IIHs and the type of the router
Area-1
Area-1
Area-1
RST-208
3010_05_2001_c1
Presentation_ID
L1
L1

2003Inc.
Cisco
AllSystems,
rights reserved.
Area-1
L1/L2
L1/L2
L1/L2
Area-2
L1/L2
L1 adjacency
L2 adjanceny
46
WAN Adjacencies
Area-1
Area-1
Area-1
L1
L1
L1
Area-1
L2
Area-2
Area-2
Area-1
L2
#
L1/L2
L1/L2
L1/L2
L1/L2
L2
L1L2
Area-1
RST-208
3010_05_2001_c1
Presentation_ID
L1/L2
L1/L2
L2
L1/L2
L1/L2
L1
Area-1
L2
L1
Area-1
Area-1
L2
Area-1
Area-1
L1
L2
Area-1
L1/L2

2003Inc.
Cisco
AllSystems,
rights reserved.
47
CSNP/PSNP
For both Level 1 and Level 2 databases, we have
CSNPs and PSNPs
Level 1 CSNP
Level 2 CSNP
Level 1 PSNP
Level 2 PSNP
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
48
Complete Sequence Number PDU

Describes all LSPs in your LSDB (in range)
Contains an address range
LSPid, seqnr, checksum, remaining lifetime
Used at 2 occasions
Periodic multicast by DIS (every 10 seconds)
On p2p links when link comes up
Created and flooded by the DIS

Every 10 seconds
On each LAN the IS is the DIS
If LSDB is large, multiple CSNPs are sent

RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
49
Partial Sequence Number PDU

PSNPs have 2 functions
Exchanged by ISs on p2p links (ACKs)
Acknowledge receipt of an LSP
Request transmission of latest LSP
PSNPs describe LSPs by its header

LSP identifier
Sequence number
Remaining lifetime
LSP checksum
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
50
LSP Header
Session Number
Presentation_ID
51
LSP Header
The LSP header contains
LSP-id
Sequence number
Remaining lifetime
Checksum
Type of LSP (Level 1, Level 2)
Attached bit
Overload bit
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
52
LSP Header (Cont.)

LSP identifier consists of 3 parts
Source ID
System-ID of router (non-PN) or DIS (Pseudonode)
Pseudonode ID
Zero for router LSP, non-zero for
Pseudonode LSP
LSP number
Fragmentation number
00c0.0040.1234.01-00
Frag-Nr
System ID
PN-ID
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
53
LSP Header (Cont.)

LSP sequence number
Used to determine the newest LSP version
LSP remaining lifetime

Used to purge old LSPs
LSP checksum
LSP type
Level 1 or Level 2
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
54
LSP Header (Cont.)

LSP Attached Bit
Set in the Level 1 LSP by a L1-L2 router if
it has connectivity to another area
Indicate to the area routers (Level 1) that it is a
potential exit point of the area
Level 1 routers select the closest (best metric)
Level 2 router with the ATT-bit set
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
55
LSP Header (Cont.)

LSP overload bit
Set by the IS when it has an overload problem
on its LSDB
Indicates that the router has an incomplete LS database,
and hence cannot be trusted to compute any correct routes
Is used in the LSDB, but topology behind it is not
calculated
Therefore other routers do not compute routes which
would require the PDU to pass through the overloaded
router
ExceptionES neighborssince these paths are
guaranteed to be non-looping
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
56
Flooding
Session Number
Presentation_ID
57
Reasons for Flooding

All routers generate an LSP
All LSPs need to be duplicated and sent to all
routers in the network
If LSPDB is not synchronized, routing loops might occur
IS-IS two components are the SPF computation and

reliable flooding
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
58
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 config changes
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
59
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
Neighbors flood the LSP further
Only flood new LSPs, ack old ones
Because we have state in our LSPDB, we can prevent
infinite looping of LSPs
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
60
Flooding on a P2P Link

Once the adjacency is established both IS send
CSNP packet
Missing LSPs are sent by both ISs if not present in
the received CSNP
Missing LSPs may be requested through PSNP
RST-208
3010_05_2001_c1
Presentation_ID
61

2003Inc.
Cisco
AllSystems,
rights reserved.
Flooding on a P2P Link (Cont.)
RTA
RTB
RTC
Interface 4
Interface 1
Interface 2
LSP
RTA.00-00
SEQ#100
PSNP
RTA.00-00
SEQ#100
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
Interface 3
LSP
RTA.00-00
SEQ#100
PSNP
RTA.00-00
SEQ#100
62
Link-State Database SynchronizationP2P
R1
III.
III. ACK:
ACK:
Thank
Thank you
you for
for
LSP
33
LSP 33
R3
LSP 33
s0
PSNP
R2
I.
I. Link
Link
went
went down
down
II.
II. New
New LSP
LSP
describing
describing the
the
current
current situation
situation
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
63
Flooding on a LAN (Broadcast Links)

On LANs only, theres a designated router (DIS)
DIS has two tasks
Creating and updating the Pseudonode LSP
Conducting the flooding over the LAN
A DIS is elected for each LAN

DIS election is based on priority
Breaking-tie is the highest SNPA (MAC address)
DIS election is deterministic
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
64
Flooding on a LAN
(Broadcast Links) (Cont.)
Interface 2
RTA (DIS)
RTB
Interface 1
Interface 3
RTB
CSNP
RTA
LSP
RTA.00-00
SEQ#100
RST-208
3010_05_2001_c1
Presentation_ID
RTC
LSP
RTC.00-00
SEQ#1
PSNP
RTB.00-00
SEQ#200
RTA
RTB
65

2003Inc.
Cisco
AllSystems,
rights reserved.
Link-State Database SynchronizationLAN

CSNP sent periodically
(every 10 s) by DIS
R2/DIS
I.
I. CSNP:
CSNP:
LSP76
LSP76
LSP77
LSP77
LSP88
LSP88
PSNP
R1
RST-208
3010_05_2001_c1
Presentation_ID
II.
II. Request:
Request:
Sorry.
Sorry. II
missed
missed LSP
LSP 77
77

2003Inc.
Cisco
AllSystems,
rights reserved.
CSNP
PSNP
66
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
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
67
Remaining Lifetime
Used to age out old LSPs
When the originator is not anymore
We need periodic refresh (with higher seqnr) to

keep stable LSPs valid
IS-IS counts down from 1200 sec to 0
We allow to start at 65535 sec (18.7h)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
68
How Is Remaining Lifetime Used?

If the remaining lifetime expires, the first router that
notices, purges the LSP:
Remove LSP body, only keep header; set age to zero;
flood via normal way in the network; zero lifetime LSP are
newer than non-zero lifetime LSPs
After a while all routers remove the purged LSP from their
LSPDB
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
69
LSP Checksum
Used to detect LSP corruption during flooding
Depending on Layer 2 CRC is not enough, corruption
happens in routers and switches
Compute checksum of received LSP, check against
checksum inside LSP
If corrupt, drop LSP; sender retransmits
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
70
Compare LSP on Checksum

If two LSPs have same LSPid, same seqnr, and
remaining lifetime, keep the LSP with highest
checksum
Guarantees consistent LSPDBs all across the network
Can happen after a router reboots, or is reconnected to
the network
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
71
Configuration
Session Number
Presentation_ID
72
How to Configure?
R1 Configuration
R1
!
interface Loopback0
ip address 172.16.1.1 255.255.255.255
!
interface Ethernet0
ip address 172.16.12.1 255.255.255.0
ip router isis
!
router isis
passive-interface Loopback0
net 49.0001.1720.1600.1001.00
!
R2
e0
e0
s0
s0
R3
RST-208
3010_05_2001_c1
Presentation_ID
73

2003Inc.
Cisco
AllSystems,
rights reserved.
How to Configure? (Cont.)

R2 Configuration
!
interface Loopback0
ip address 172.16.2.2 255.255.255.255
!
interface Ethernet0
ip address 172.16.12.2 255.255.255.0
ip router isis
!
interface Serial0
ip address 172.16.23.1 255.255.255.252
ip router isis
!
router isis
passive-interface Loopback0
net 49.0001.1720.1600.2002.00
!
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
R1
R2
e0
e0
s0
s0
R3
74
Looking at the Show Commands

R1#show clns neighbor
System Id Interface SNPA
State Holdtime Type Protocol
R2
Et0
0000.0c47.b947 Up 24
L1L2 IS-IS
R1#show clns interface ethernet 0

Ethernet0 is up, line protocol is up
Checksums enabled, MTU 1497, Encapsulation SAP
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x0, local circuit ID 0x1
Level-1 Metric: 10, Priority: 64, Circuit ID: R2.01
Number of active level-1 adjacencies: 1
Level-2 Metric: 10, Priority: 64, Circuit ID: R2.01
Number of active level-2 adjacencies: 1
Next IS-IS LAN Level-1 Hello in 5 seconds
Next IS-IS LAN Level-2 Hello in 1 seconds
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
75
Looking into the Database

R2#show clns neighbor
System Id Interface SNPA
State Holdtime Type Protocol
R1
Et0
0000.0c09.9fea Up 24
L1L2 IS-IS
R3
Se0
*HDLC*
Up 28
L1L2 IS-IS
R2#show isis database
IS-IS Level-1 Link State Database:
LSPID
LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
R1.00-00 0x0000008B 0x6843
55
0/0/0
R2.00-00 * 0x00000083 0x276E
77
0/0/0
R2.01-00 * 0x00000004 0x34E1
57
0/0/0
R3.00-00 0x00000086 0xF30E
84
0/0/0
IS-IS Level-2 Link State Database:
LSPID
R1.00-00 0x00000092 0x34B2
41
0/0/0
R2.00-00 * 0x0000008A 0x7A59
115
0/0/0
R2.01-00 * 0x00000004 0xC3DA
50
0/0/0
R3.00-00 0x0000008F 0x0766
112
0/0/0
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
76
Looking into the Database Detail

R2#show isis database R2.00-00 detail
IS-IS Level-1 LSP R2.00-00
LSPID
R2.00-00 * 0x00000093 0x077E
71
0/0/0
Area Address: 49.0001
NLPID:
0xCC
Hostname: R2
IP Address: 172.16.2.2
Metric: 10
IP 172.16.12.0 255.255.255.0
Metric: 0
IP 172.16.2.2 255.255.255.255
Metric: 10
IP 172.16.23.0 255.255.255.252
Metric: 10
IS R2.01
Metric: 10
IS R3.00
IS-IS Level-2 LSP R2.00-00
LSPID
R2.00-00 * 0x0000009A 0x5A69
103
0/0/0
Area Address: 49.0001
NLPID:
0xCC
Hostname: R2
IP Address: 172.16.2.2
Metric: 10
IS R2.01
Metric: 10
IS R3.00
Metric: 10
IP 172.16.23.0 255.255.255.252
Metric: 10
IP 172.16.1.1 255.255.255.255
Metric: 10
IP 172.16.3.3 255.255.255.255
Metric: 0
IP 172.16.2.2 255.255.255.255
Metric: 10
IP 172.16.12.0 255.255.255.0
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
77
Looking into the Routing-Table

R1#show ip route isis
i L1 172.16.2.2/32 [115/10] via 172.16.12.2, Ethernet0
i L1 172.16.3.3/32 [115/20] via 172.16.12.2, Ethernet0
R2#show ip route isis

i L1 172.16.1.1/32 [115/10] via 172.16.12.1, Ethernet0
i L1 172.16.3.3/32 [115/10] via 172.16.23.2, Serial0
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
78
Show IS-IS SPF-Log
R1#show isis spf-log

Level 1 SPF log
When Duration Nodes Count First trigger LSP Triggers
04:07:42
12
PERIODIC
03:52:41
12
PERIODIC
03:37:40
12
PERIODIC
00:37:31
12
PERIODIC
00:22:31
21
PERIODIC
00:07:30
19
PERIODIC
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
79
Show IS-IS LSP Log
R1#show isis lsp-log

Level 1 LSP log
When
Count
Interface Triggers
5d05h
5d05h
5d04h
Ethernet0 NEWADJ DIS
5d04h
Ethernet0 CONFIG DELADJ DELADJ
5d04h
Serial1 NEWADJ
00:23:10
Loopback0 CONFIG
RST-208
3010_05_2001_c1
Presentation_ID
Serial1 DELADJ
ATTACHFLAG

2003Inc.
Cisco
AllSystems,
rights reserved.
80
New Features
Session Number
Presentation_ID
81
L2->L1 Route Leaking

RFC1195 defines all routers as STUB routers
No information is leaked from routers in L2 into
routers in L1
Hence all L1-routers are forced to route to the
closest L2-router
This may result in sub-optimal routing
This is IP only feature (CLNS still uses STUB)
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
82

This new feature allows redistribution of L2-IP
routes into L1 areas
Enables Level 1-only routers to pick the best path
to exit the area
Enables MPLS-VPN (PE reachability) between areas
Redistribution is controlled via distribute-lists
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
83

Prefixes MUST be present in the routing table as
ISIS level-2 routes
Otherwise no leaking occurs
Same criteria than L1 to L2
Inter-area routing is done through the routing table
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
84
When leaking routes from L2 backbone into L1 areas

a loop protection mechanism need to be used in
order to prevent leaked routes to be re-injected into
the backbone
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
85

Recommendation:
use wide Metric TLV (TLV 135)
Configure with:
router isis
metric-style wide
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
86
L2->L1 Route Leaking (Cont.)

Route leaking is implemented in both 12.0S and 12.1
Cisco IOS 12.0S command
advertise ip L2-into-L1 <100-199>
Cisco IOS 12.1 command
redistribute isis ip level-2 into level-1 distribute-list <100-199>
Both commands are supported

12.0S command will be converted into 12.1 syntax
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
87
Fast Hellos
Hold-time can be set to 1 second
interface POS0/0
isis hello-interval minimal
By default hello-multiplier is 3
Hello packets sent every 333 msecs
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
88
Fast Hellos (Cont.)

Advantages
Reduced link failure detection time
Disadvantages
Increased BW/buffer/CPU usage can cause missed
hellos; potential increased adjacency flapping can cause
instability
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
89
Fast Hellos (Cont.)

Configuration:
Interface configuration mode:
Rtr-A(config)#int POS0/0
Rtr-A(config-if)#isis hello-interval minimal
Rtr-A(config-if)#isis hello-multiplier 4
Advertised hold time will now be 1 second, hello-interval

will be 250 ms
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
90
Multi-Area Support
Allows multiple IS-IS processes to be configured on
a single router
Each process serves a different area
One of the processes will be L1L2 to advertise all
area addresses from all processes into L2
Maximum number of configurable IS-IS processes
on a single router is 29
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
91
Why use Multi-Area ?

ADMs used in Telco SDH/Sonet networks use CLNS
for network management
IS-IS implementation used on ADMs may have
scaling limitations
Thus, may only build small L1 areas
Each ISIS router belongs to one area
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
92
Deployment Scenarios
Session Number
Presentation_ID
93
L1-Only POPs
POP 1
L1-Only
POP 2
L1-Only
CORE
L1-Only
POP 3
L1-Only
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
POP 4
L1-Only
94
L1-Only POPs (Cont.)

IS-IS is a newer protocol at that time at least
operationally with the ISPs
In this designall the routers will be running in one
area and are all doing L1-only routing
This design is flat with a single L1-only database
running on all the routers
If you have a change in the topology, the SPF
computation will be done in all the routers as they
are in the L1-only sub-domain
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
95

Also the Tier 1 ISPs picked up L1-only to avoid suboptimal routing problems
The other factor is when the router runs
as L1L2then the router(s) will have 2 instances of
SPFs
Since most of the routers were AGS+/7XXX
at that time, the ISPs had chosen L1-only singlearea IS-IS with in their network
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
96
L2-Only POPs
POP 1
Area 49.0001
POP 2
Area 49.0001
CORE
L2-Only
POP 3
Area 49.0001
RST-208
3010_05_2001_c1
Presentation_ID
POP 4
Area 49.0001

2003Inc.
Cisco
AllSystems,
rights reserved.
97

Most of the Tier 1 ISPs are running Level 2-only on
all the routers
The rough approximation of routers L2-only are
about 8001000
The SPF-computation may take up to 23 sec.
Most of the uplinks into the core are OC-12 to OC48 POS links
As the network grows, easy to bring the L1-only
POPs
All the routers in L2 will share all the LSPs
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
98
L1 in the POP and L2 in the Core
POP 2
L1-Only
L1L2 Area 49.0002
L1L2
POP 1
L1-Only
Area 49.0001 L1L2
L1L2
CORE
L2-Only
L1L2
L1L2
L1L2
POP 3
L1-Only
Area 49.0003
RST-208
3010_05_2001_c1
Presentation_ID
L1L2
POP 4
L1-Only
Area 49.0004

2003Inc.
Cisco
AllSystems,
rights reserved.
99
L1 in the POP and L2 in the Core (Cont.)

Within a given local popall the routers will be in a separate
area
The L1L2 routers at the edge of the POPs will be running
L1-adj going into the POP
L2-adj into the core with the rest of the L1L2 routers
The SPF computations will be limited to the respective L1areas only

All the L1-routers in a given pop will receive the ATT bit set by
the L1L2 router at the edge of this pop
This will cause the sub-optimal routing in reaching out the
prefixes outside the POP by the local routers
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
100
L1 in the POP and L2 in the Core (Cont.)

Route-Leaking
It is recommended to configure the L1L2 routers at

the edge of the pop with route-leaking capabilities
This way we leak the longer prefixes of the remote

pop into the pop
Hence the L1 routers will be able to take the
right exist router based on the metric of the leaked
IP-prefix
Whenever you configure for route-leakingmake
sure you configure the routers with metric-style
wide
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
101
Suggested Reading
ISO 10589 (IS-IS Intra-Domain Routing Exchange Protocol)
RFC 1195 (OSI IS-IS for Routing in TCP/IP and Dual Environments)
draft-ietf-isis-traffic-02.txt (TE Extensions for IS-IS)
draft-ietf-isis-3way-04.txt (3-Way Handshake)
RFC 2966 (Route-leaking)
RFC 2763 (Dynamic Hostname Exchange)
draft-hsmit-mpls-igp-spf-00.txt
RST-208
3010_05_2001_c1
Presentation_ID

2003Inc.
Cisco
AllSystems,
rights reserved.
102
RST-208
3010_05_2001_c1
2001, Cisco Systems, Inc. All rights reserved.
103

IS-IS Protocol

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

IS-IS Protocol

Diunggah oleh

Hak Cipta:

Format Tersedia

IS-IS Introduction

2003 Cisco Systems, Inc. All rights reserved.

2001, Cisco Systems,

2003 Cisco Systems, Inc. All rights reserved.

2001, Cisco Systems,

2001, Cisco Systems,

IS-IS Overview (Cont.)

2001, Cisco Systems,

IS-IS Overview (Cont.)

All 3 protocols independently ride over layer 2

2001, Cisco Systems,

IS-IS Overview (Cont.)

2001, Cisco Systems,

2003 Cisco Systems, Inc. All rights reserved.

CLNS addressing consists of 3 parts:

2001, Cisco Systems,

NSAPs and Addressing

High Order DSP

Variable Length Area Address

Area address: Variable length field composed of high order octets

2001, Cisco Systems,

NSAPs and Addressing (Cont.)

2001, Cisco Systems,

NETs versus NSAPs

2001, Cisco Systems,

OSI AddressingNET and System Identifier

2001, Cisco Systems,

CLNS Addressing: NSAP Examples

2001, Cisco Systems,

Identifying Systems in IS-IS

2001, Cisco Systems,

Identifying Systems in IS-ISSystem ID

2001, Cisco Systems,

CLNS Addressing: NSAP Examples (Cont.)

2001, Cisco Systems,

CLNS Addressing: How Do Most ISP Define

2001, Cisco Systems,

2003 Cisco Systems, Inc. All rights reserved.

Areas and Backbone Routers

For each level (1 and 2) a DIS will be elected on

2001, Cisco Systems,

Areas and Backbone Routers (Cont.)

2001, Cisco Systems,

Areas and Backbone Routers (Cont.)

2001, Cisco Systems,

Areas and Backbone Routers (Cont.)

2001, Cisco Systems,

Areas and Backbone Routers (Cont.)

2001, Cisco Systems,

Areas and Backbone Routers (Cont.)

Im in area 2 and ALL

Remember, the Backbone Must Be Contiguous:

2001, Cisco Systems,

Example #1: Area ConfigurationPhysical

2001, Cisco Systems,

Example #1: Area ConfigurationLogical

2001, Cisco Systems,

Example #2: L2 and L1/L2 Routers Forming L2

2001, Cisco Systems,

SPF (Dijkstra) and Partial Route Calculation

2001, Cisco Systems,

2003 Cisco Systems, Inc. All rights reserved.

2001, Cisco Systems,