Is Is

Advanced Network Design
ICT347 / ICT647
Integrated IS-IS
Week 4
CCNP: Building Scalable Internetworks
Module 4
Sources
Sources used in creating this IS-IS presentation:

Cisco Online curriculum
Not much as I figured you can read this yourself
IS-IS Network Design Solutions, Cisco Press
Very Good Reference
CCNP Self-Study (BSCI), Cisco Press
Routing TCP/IP Volume I, by Jeff Doyle, Cisco Press
Agenda
IS-IS vs. OSPF
History of IS-IS
Introduction to IS-IS
Addressing
Hellos, Neighbours and Adjacencies
IS-IS Processes
Certification Exam Notes
IS-IS versus OSPF
IS-IS is exactly the same as OSPF

only completely different
IS-IS versus OSPF

Terminology
IS-IS
OSPF
ES (End System)
Host
Comments
IS
Router
(Intermediate System)
Circuit
Link
SNPA (Subnetwork
Point of Attachment)
Datalink Address
PDU
(Protocol Data Unit)
Packet
DIS (Designated
Intermediate System)
DR (Designated
Router)
N/A
BDR
IIH
Hello packet
(IS-to-IS Hello Packet)
IS-IS versus OSPF

Terminology
IS-IS
OSPF
Comments
LSP
(Link-State Packet)
LSA (Link-State
Advertisement)
LSAs are actually comparable to

TLVs used in LSPs.
CNSP (Complete
Sequence Number
PDU or Packet)
DBD (Data Base

Description Packet)
PSNP (Partial
Sequence Number
PDU or Packet)
LSAck or LSR
(Link State Request)
Routing Domain
AS
Level 1 Area
Area (non-backbone)
Level 2 Area
Backbone area
(Area 0)
The term routing domain is also

used with OSPF.
IS-IS uses a backbone path

connected by contiguous L2
routers. There is no backbone
area in IS-IS
IS-IS versus OSPF

Intermediate Systems (Routers)
IS-IS
OSPF
Comments
Level 1 IS (router)
Internal
Non-backbone Router
Internal, non-backbone router in

a Totally Stubby Area
Level 2 IS (router)
Internal Backbone
Router or ASBR
Any Level 2 router can distribute

externals into the domain. No
special name. (Cisco IOS allows
Level 1 routers to distribute
externals.)
Level 1-2 IS (router)
ABR
System ID
Router ID
The System ID is the key for SPF

calculations. Sometimes the
NET address is thought of as the
Router ID.
AFI = 49
RFC 1918 Addresses
AFI is part of the NSAP.
IS-IS versus OSPF

Timers
Interface timers
IS-IS
OSPF
Point-to-Point
Hello 10 sec
Holdtime 30 sec
Hello 10 sec
Dead 40 sec
Broadcast
Hello 10 sec
Holdtime 30 sec
Hello 10 sec
Dead 40 sec
NBMA
N/A
Hello 30 sec
Dead 120 sec
IS-IS versus OSPF

Timers
Other timers
IS-IS
OSPF
LS Aging
1,200 sec or 20
min
(counts down)
3,600 sec or 60
min
(counts up)
LS Refresh
Every 15 min
Every 30 min
NBMA
N/A
Hello 30 sec
Dead 120 sec
SPF Delay/Holdtime 5.5 sec / 10 sec
5 sec / 10 sec
Agenda
IS-IS vs. OSPF
History of IS-IS
Addressing
IS-IS Processes
History of IS-IS and OSPF

http://www.nanog.org
1985
Originally called DECnet Phase V
1987
IS-IS (from DEC) selected by ANSI as OSI
intradomain protocol (CLNP only)
1988
NSFnet deployed, IGP based on early IS-IS draft
OSPF work begins, loosely based on IS-IS
mechanisms
IP extensions to IS-IS defined
Dual-mode IS-IS RFC published

1989
OSPF v.1 RFC published
IS-IS becomes ISO proposed standard
Public bickering ensues--OSPF and IS-IS are
blessed as equals by IETF, with OSPF somewhat
more equal
Private cooperation improves both protocols
1990
Dual-mode IS-IS RFC published
1991
OSPF v.2 RFC published
Cisco ships OSI-only IS-IS

1992
Cisco ships dual IS-IS
Lots of OSPF deployed, but very little IS-IS
1993
Novell publishes NLSP (IPX IS-IS knockoff)
1994
Large ISPs need an IGP; IS-IS is recommended due to
recent rewrite and OSPF field experience (and to lesser
extent, NSF CLNP mandate)
1995
ISPs begin deployment of IS-IS, Cisco implementation
firms up, protocol starts to become popular in niche

1996
1996--1998
IS-IS niche popularity continues to grow (some ISPs
switch to it from OSPF)
IS-IS becomes barrier to entry for router vendors
targeting large ISPs
Juniper and other vendors ship IS-IS capable routers
1999
1999--2000
Extensions continue for both protocols
Who uses IS-IS?
IS-IS is popular amongst telcos and large ISPs

A Tier-1 carrier is a telco or ISP that is at the top of the
telecommunications peering and settlements food chain
Tier-1 operators typically have operations in more than one country
Tier-1 operators own and operate their own physical networks, and
either own or part-own their international submarine cable links
Example of Tier-1 carriers (not necessarily IS-IS users)

AT&T
BBN/Genuity
British Telecom (BT)
Cable & Wireless
Connect Internet Solutions
German Telekom
Global Crossing
Level 3
NTT/Verio
Optus
Qwest
Sprint
Telstra
UUNET (owned by Worldcom,
doing business as MCI)
Williams Communications
Agenda
IS-IS vs. OSPF
History of IS-IS
Addressing
IS-IS Processes
Protocols
Routers
Areas
OSI: Two Network Services,

Two Network Protocols
CONP/CMNS

Connection-Oriented Network Protocol: OSI network layer protocol that carries

upper layer data over connection-oriented links.
Connection Mode Network Service: Requires establishment of a path between
transport layer entites
CLNP/CLNS

Connectionless Network Protocol: OSI network layer protocol that carries upper
layer data over connectionless links, Similar to IP
Connectionless Network Service: Performs datagram support, does not require
circuit to be established
IS-IS Protocol Options

IS-IS (ISO 10589)
Dynamic link state routing protocol used in an ISO CLNS
environment
ISO-IGRP
Cisco IOS offers proprietary routing protocol for CLNS
Based on IGRP, distance vector technology
Can be used for Level 3 Routing, between IS-IS domains
Integrated IS-IS (RFC 1195)

IS-IS for mixed ISO CLNS and IP environments.
Either
Purely ISO
Purely IP (CCNP 1)
Both
OSI Routing Protocols:

ES-IS and IS-IS
ES-IS
Analogous to ARP in IP
Not technically a routing
protocol
Sometimes referred to as
Level 0 routing
ESs (hosts) discover
nearest IS (router) by
listening to IS Hello (ISH)
packets
ISs (routers) know which
hosts are on their
subnetwork by listening to
ES Hello (ESH) packets.
ISH
ESH
Not applicable to IP
10
OSI Routing Protocols: ES-IS

and IS-IS
IS-IS
OSI distinguishes between Level
1, Level 2, and Level 3 routing.
Level 1 Routing
If DA is an ES on another
subnetwork in the same area,
the IS knows the correct
route and forwards packet
appropriately
Level 2 Routing
If DA is an ES on another
area, the Level 1 IS sends
the packet to the nearest
Level 2 IS
Level 3 Routing is between
separate domains
Pure CLNS environment IDRP
or ISO-IGRP can be used, in
IP, BGP is used
Not applicable to CCNP
Boundary areas in IS-IS exists

on a link between routers and
not on a router itself as in
OSPF
These routers should be

entirely in Area 1 and Area 2
IS-IS Areas
Level 1 IS (L1 IS, router)

Analogous to OSPF Internal
non-backbone router
Responsible for routing to
ESs inside an area

Backbone router
Responsible for routing
between areas
Level 1 and Level 2 IS

(L1L2 IS, router)
Analogous to OSPF ABR
Participates in both
L1 intra-area routing and
L2 inter-area routing
11
Level 1 Router

non-backbone router
(Totally Stubby)
Responsible for routing to
ESs inside an area.
An area is a contiguous
group of Level 1 routers
Level 1 routers maintain

the Level 1 database for
the area and exit points to
beighbouring areas
Level 2 Router

Analogous to OSPF
Backbone Internal Router
Responsible for routing
between areas
Also referred to as
area routers
Interconnect Level 1 areas
Stores separate database

of inter-area topology
12
Level 1 Level 2
Router
Level 1 and Level 2 IS

(L1-L2 IS, router)
Analogous to OSPF ABR router
Participates in both L1 intra-area
routing and L2 inter-area routing
Maintain both Level 1 and

Level 2 LSDB
Supports Level 1 function,

communicating with other
Level 1 routers in the area
Inform Level 1 routers that the

L1L2 router is the exit point
(default route) from the area
Supports Level 2 function,

communicating with the rest of
the backbone path
IS-IS Backbone
IS-IS does not share the

concept of a backbone area
with OSPF
An IS-IS backbone can

appear as a set of distinct
areas interconnected by a
chain of L2 routers,
weaving through and
between the L1 areas
The IS-IS backbone (path)

consists of a contiguous set
of L1L2 and L2 routers
Where is the backbone?
13
Agenda
IS-IS vs. OSPF
History of IS-IS
Addressing
IS-IS Processes
OSI Addressing
NSAP
(Network Service Access Point)
Area - System ID - NSEL
SNPA
(Subnetwork Point of Attachment)
14
OSI Addressing
OSI network layer

addressing uses the NSAP
(Network Service Access
Point), consisting of:
OSI Address of the device
Link to higher layer protocol
We will not cover the variety

of NSAP formats which exist
Represented in hexadecimal
(up to 40 hex digits)
Cisco format:
Area System ID NSEL
49.0001.2222.2222.2222.00
Network Service Access Points
Format of the Cisco NSAP address consists of three parts:

1. Area address
2. System ID
3. NSAP Selector byte (NSEL)
15
Network Service Access Points
Area address is a variable length field
System ID is the ES or IS identifier within an area, similar

to the OSPF router ID
System ID has a fixed length of six bytes, built into IOS
The NSAP Selector byte is a service identifier

Analogous to that of a port or socket in TCP/IP
Do I have to know this?

I am only routing IP?
Yes!
NSAP prefixes are required for CLNS routing,
including IP only networks
In IP-only networks, IS-IS uses OSI addresses
Identify the router (IS)
Build the topology table
Build the SPF tree
LSPs
Hello and other PDUs
NSAP addresses are required for CLNS routing
16
Cisco Format NSAPs

Area
Area System ID NSEL

49.0001.2222.2222.2222.00
Addresses starting with 49 (AFI=49) are considered private IP

address, analogous to RFC 1918
Routed by IS-IS
Should not be advertised to other CLNS networks
(outside this IS-IS domain)
Additional 2 bytes (HODSP) added for the area ID
All routers in the same area must have the same area address
Cisco Format NSAPs

System ID
Area System ID NSEL

49.0001.2222.2222.2222.00
OSI requires System ID must be the same number of bytes
throughout the domain
Cisco fixes the System ID at 6 bytes
Customary to use one of the following:

MAC address from the router
IP address of loopback interface
o 192.168.111.3 -> 192.168.111.003 -> 1921.6811.1003
Each IS and ES must have a unique System ID within the area
(recommend to be unqiue within the domain)
17
Cisco Format NSAPs

NSAP Selector (NSEL)
Area System ID NSEL

49.0001.2222.2222.2222.00
NSEL is a service identifier, loosely equivalent to a port in TCP/IP

Must be specified by a single byte preceded by a period (.)
Not used in routing decisions
When NSEL = 00, it identifies the device itself, the network level address
The NSAP with a NSEL = 00 is known as a Network Entity Title (NET
NET)
A NET is an NSAP with the NSEL set to (00)
NSAP
Example Addresses
Example 1: NSAP
47.0001.aaaa.bbbb.cccc.00
Area ID is 47.0001
System ID is aaaa.bbbb.cccc
NSAP selector byte is 00
Example 2: NSAP
39.0f01.0002.0000.0c00.1111.00
Area ID is 39.0f01.0002
System ID is 0000.0c00.1111
NSAP selector byte is 00
18
Configuring IS-IS (so far)

SanJose1
interface FastEthernet0/0
ip address 172.16.0.1 255.255.255.0
ip router isis
isis priority 100
router isis
net 49.0001.1111.1111.1111.00
SanJose2
ip address 172.16.0.2 255.255.255.0
ip router isis
router isis
net 49.0001.2222.2222.2222.00
Area
49.0001
SanJose3
ip address 172.16.0.3 255.255.255.0
ip router isis
router isis
net 49.0001.3333.3333.3333.00
Circuit ID
IP address
NSAP
MAC (SNPA) address
IP address
NSAP
SNPA address
The router assigns a Circuit ID of one octet to each interface
For point-to-point interfaces, this is the sole circuit identifier

For example, 03
For LAN interfaces, the Circuit ID is tagged to the end of the

System ID of the designated IS to form a 7-byte LAN ID
For example, 1921.6811.1001.
1921.6811.1001.03
03
19
Subnetwork
Point of Attachment
IP address
NSAP
MAC (SNPA) address
IP address
NSAP
SNPA address
The SNPA is taken from the following:

MAC address on a LAN interface
Virtual Circuit ID for X.25 or ATM
Data link connection identifier (DLCI) for Frame Relay
High-Level Data Link Control (HDLC) for interfaces
Display both ES and IS

neighbours
SNPA is the MAC address of
the remote router.
Area
49.0001
Serial would show

encapsulation (e.g. HDLC)
Cisco routers default to L1L2

operation
20
Agenda
IS-IS vs. OSPF
History of IS-IS
Addressing
IS-IS Processes
Network Representation
OSI has only two main types

of physical links:
Broadcast:
Broadcast Multiaccess media
types, usually LANs
Nonbroadcast
Nonbroadcast: Point-to-Point,
Multipoint, and dynamically
established links (WAN links)
IS-IS supports only two

media representations:
Broadcast for LANs
Point
Point--to
to--Point for all other
media
IS-IS has no concept of an

NBMA network
Recommended that point-topoint links be used for native
ATM, Frame Relay, or X.25
21
Hello Messages
IS-IS uses Hello PDUs to

establish adjacencies with
other ISs and ESs
IS-IS has three types of

Hello PDUs
ESH, sent by ES to an IS
ISH, sent by IS to an ES
IIH, used between ISs
o Hello L1 LAN
o Hello L2 LAN
o Hello PointPoint-to
to--Point
Neighbours and Adjacencies
IS-IS discover beighbours

and forms adjacencies
using IS-IS Hello PDUs
Transmitted every 10sec
Can be changed using the

interface command
is hello-interval
Hold time defaults to

3 times the Hello time
(30 seconds), before
declaring a beighbour dead
Changed using the interface
command
is hello-multiplier
Default is 3
22
Designated IS
Similar to the DR in OSPF

DIS (Designated IS) is
elected to generate the LSP
(Link State Packet, ie. LSA)
representing the virtual
router connecting all
attached routers to a star
topology
For SPF, the whole network
must look like a collection of
nodes and point-to-point
links
Multi-access networks use a
virtual node called the
pseudonode
Each router on the LAN
simulates an interface on the
pseudonode
Designated IS Election
Router with highest priority

(Cisco default is 64)
Router with highest MAC
address
Differences from OSPF
No BDR concept
No way to make a router
ineligible from being DIS (no
OSPF priority 0)
New IS can cause a new
election
Used as circuit ID for all

routers on LAN
Periodically broadcasts
CSNPs (OSPF DBD) every 10
seconds
23
Adjacencies
L1 routers form L1
adjacencies with L1 and
L1-L2 routers in their area
L2 routers form L2
adjacencies with L2 and
L1-L2 routers in their area
or another area
L1L2 routers form L1 and

L2 adjacencies with each
other in their area or
another area
L1 router does not form an

adjacency with an L2
router
WAN Adjacencies
On point-to-point links the

IIH PDUs are common to
both Level 1 and Level 2
ISs Announce both their

Level type and Area ID
Remember, separate
LSDBs for different Levels
What are the

adjacencies?
L1?
L2?
L1L2?
None?
24
WAN Adjacencies
Adjacencies also determine

what type of routes the IS
will have in its route table
L1: Intra-area routes
o Routes only within that area
L2: Inter-area routes

o Routes from other areas
Both
Adjacency requires
L1 ISs in the same area
System ID must be unique
Hello timers do not have to

match

SanJose1
ip address 172.16.0.1 255.255.255.0
ip router isis
isis priority 100
router isis
net 49.0001.1111.1111.1111.00
SanJose2
ip address 172.16.0.2 255.255.255.0
ip router isis
router isis
net 49.0001.2222.2222.2222.00
DIS
Area
49.0001
SanJose3
ip address 172.16.0.3 255.255.255.0
ip router isis
router isis
net 49.0001.3333.3333.3333.00
25
Agenda
IS-IS vs. OSPF
History of IS-IS
Addressing
IS-IS Processes
LSDB Synchronization and

Update Process
LSP (LSA)
LSP (LSA)
LSP (LSA)
PSNP
(LSAck)
PSNP (LSAck)
PSNP (LSAck)
IS-IS LSDB uses special PDUs called Sequence Number PDUs:

PDUs
Complete Sequence Number PDU (CSNP) [OSPF: DBD Packet]
o List of LSPs held by the router
Partial Sequence Number PDU (PSNP) [OSPF: LSAck/LSR]

o Acknowledge the receipt of a LSP
o Request a complete LSP for a missing entry
26
Update Process
Point-to-Point networks:
Once an LSP is sent, router sets a timer
(minimumLSPTransmissionInterval) of 5 seconds
If PSNP not received, resends LSP
Update Process
1.
DIS mutlicasts CSNP
2.
R1 sends a PSNP [LSR] to DIS
3.
DIS sends LSP [LSA] to R1
4.
R1 sends PSNP to acknowledge
LSP 77
CSNP
(DBD)
(LSA)
PSNP
(LSAk)
PSNP
(LSR)
On Broadcast networks:
LSPs are not acknowledged by each receiving router.
DIS periodically multicasts a CSNP [OSPF DBD] that describes every
LSP in LSDB
o Default is every10 seconds
L1 CNSPs are multicast to AllL1ISs

L2 CNSPs are multicast to AllL2ISs
27
Decision Process
Once the update process has built the LSDB, the Decision
Process uses the LSDB to calculate the SPF
Separate SPF for L1 routes and L2 routes
Four types of metrics:

Default: Supported by all routers (only one supported by Cisco)

Delay: Measures Transit Delay
Expense: Measures the monetary cost of link utilisation
Error: Measures error probability
Metric expressed as an integer between 0 and 63

Separate metric is calculated for each route
SPF must be run for each metric, for both L1 and L2 routes
Cisco only supports the Default metric
Metrics
Cisco assigns a default metric of 10 to every
interface regardless of interface type
Left to the default, IS-IS metric becomes a
simple measure of hop count
Interface command isis metric changes
default value
Total cost of any route is a sum of individual
metrics of the outgoing interfaces
The maximum metric value is 1023
Extended Metric
Cisco IOS supports a 24-bit wide metric field
Allows a maximum metric of 16777215 (224 - 1) with a
total path metric of 4261412864 (232 - 225)
28
Metrics
Ciscos IS-IS implementation will perform equal cost load

balancing up to six paths
Supports VLSM
L1 routers calculate path to the nearest L2 router for interinterarea routing [Totally Stubby Area]
When an L2 or L1L2 router is attached to another area, the router
will advertise this fact
The Decision Process in L1 routers will choose the metrically closest
L1L2 router as the default router
An L1 0.0.0.0/0 route will be installed into the routing table
IS-IS command summary-address network mask is used

to configure summarisation (L1, L2 or both)
L2 routers are expected to know about all routes
ISIS command default-information originate advertises a
default route into the backbone path
Odds and Ends
L1L2 routers run two IS-IS processes, one for its L1 LSDB
and another for its L2 LSDB
Once a packet is accepted by a router the System ID and

NSEL are stripped
29
Sub-optimal Routing
Sub-optimal routing is not necessarily a disadvantage
Multi-Area IS-IS Example
30
Note: ip router isis command must be added not only to transit interfaces but
also to interfaces connected to stub networks whose IP addresses should be
advertised by IS-IS.
Levels
L1L2
SanJose1
ip address 172.16.0.1 255.255.255.0
ip router isis
interface Serial0/0
ip address 10.0.0.2 255.255.255.252
ip router isis
router isis
net 49.0001.1111.1111.1111.00
is-type level-1-2
SanJose2
ip address 172.16.0.2 255.255.255.0
ip router isis
ip address 172.16.0.20 255.255.255.0
ip router isis
router isis
net 49.0001.2222.2222.2222.00
is-type level-1
L1
L2
Phoenix
ip address 192.168.30.1 255.255.255.0
ip router isis
interface Serial0/0
ip address 10.0.0.1 255.255.255.252
ip router isis
router isis
net 49.0002.3333.3333.3333.00
is-type level-2-only
is-type {level-1 | level-1-2 |

level-2-only}
show clns
neigh
System ID Cisco IOS uses
L1L2
the hostname.
SNPA is the MAC of the
remote router or HDLC on the

serial link.
The Type is the is-type of the
remote router.
L1
L2
SanJose1#show clns beighbours

System Id
Interface
SNPA
SanJose2
Fa0/0
0003.6be9.d480
Phoenix
Se0/0
*HDLC*
State
Up
Up
Holdtime
26
28
Type Protocol
L1
IS-IS
L2
IS-IS
SanJose2#show clns beighbours

System Id
Interface
SNPA
SanJose1
Fa0/0
0002.b9ee.5ee0
State
Up
Holdtime
4
Type Protocol
L1
IS-IS
Phoenix#show clns beighbours

System Id
Interface
SNPA
SanJose1
Se0/0
*HDLC*
State
Up
Holdtime
27
Type Protocol
L2
IS-IS
31
show isis data

SanJose1 has a L1 LSDB and
a L2 LSDB.
Email me if you want the
detail of this output or I can
add it to the presentation.
Use detail option for
complete LSDB.
L1L2
L1
L2
SanJose1#show isis database

IS-IS Level-1 Link State Database:
LSPID
LSP Seq Num LSP Checksum
SanJose1.00-00
* 0x00000005
0xDE15
SanJose1.01-00
* 0x00000003
0xBBFE
SanJose2.00-00
0x00000006
0xBDFB
LSPID
LSP Seq Num LSP Checksum
SanJose1.00-00
* 0x0000001B
0xAB48
SanJose1.01-00
* 0x0000001B
0x5526
Phoenix.00-00
0x0000001E
0xA3D3
Phoenix.01-00
0x00000002
0x54A6
LSP Holdtime
916
1165
470
ATT/P/OL
1/0/0
0/0/0
0/0/0
LSP Holdtime
914
480
912
826
ATT/P/OL
0/0/0
0/0/0
0/0/0
0/0/0
show isis data

L1L2
SanJose2 only has a L1

LSDB.
Phoenix only has a L2 LSDB.

L1
L2
SanJose2#show isis database

LSPID
LSP Seq Num
SanJose1.00-00
0x00000005
SanJose1.01-00
0x00000003
SanJose2.00-00
* 0x00000006
LSP Checksum
0xDE15
0xBBFE
0xBDFB
LSP Holdtime
907
1155
464
ATT/P/OL
1/0/0
0/0/0
0/0/0
Phoenix#show isis database

LSPID
LSP Seq Num
SanJose1.00-00
0x0000001B
SanJose1.01-00
0x0000001B
SanJose2.00-00
0x00000024
Phoenix.00-00
* 0x0000001E
Phoenix.01-00
* 0x00000002
LSP Checksum
0xAB48
0x5526
0x2FD3
0xA3D3
0x54A6
LSP Holdtime
893
459
0 (932)
895
808
ATT/P/OL
0/0/0
0/0/0
0/0/0
0/0/0
0/0/0
32
show ip route
Because SanJose1 is an L1L2
L1L2
router, it contains both:

L1 routes for Area 49.0001
and
L2 routes for the other
area 49.0002.
L1
L2
SanJose1#show ip route
Gateway of last resort is not set
i L2 192.168.30.0/24 [115/20] via 10.0.0.1, Serial0/0

C
192.168.10.0/24 is directly connected, FastEthernet0/1

172.16.0.0/24 is subnetted, 1 subnets
172.16.0.0 is directly connected, FastEthernet0/0
i L1 192.168.20.0/24 [115/20] via 172.16.0.2, FastEthernet0/0

C
10.0.0.0 is directly connected, Serial0/0
show ip route
Because SanJose2 is only an
L1 router, it only contains:
L1 routes for Area 49.0001
and
The 0.0.0.0/0 default route
sent by SanJose1.
L1L2
L1
L2
SanJose2#show ip route
Gateway of last resort is 172.16.0.1 to network 0.0.0.0
i L1 192.168.10.0/24 [115/20] via 172.16.0.1, FastEthernet0/0
C
172.16.0.0 is directly connected, FastEthernet0/0

i L1
10.0.0.0 [115/20] via 172.16.0.1, FastEthernet0/0
i*L1 0.0.0.0/0 [115/10] via 172.16.0.1, FastEthernet0/0
33
show ip route
Because Phoenix is an L2
L1L2
router, it contains:
L2 routes which are L1
routes from Area 49.0001.
No L1 routes from Area
49.0002.
L1
L2
Phoenix#show ip route
Gateway of last resort is not set
C
i L2 192.168.10.0/24 [115/20] via 10.0.0.2, Serial0/0

i L2
172.16.0.0 [115/20] via 10.0.0.2, Serial0/0
i L2 192.168.20.0/24 [115/30] via 10.0.0.2, Serial0/0

C
10.0.0.0 is directly connected, Serial0/0
Agenda
IS-IS vs. OSPF

History of IS-IS
Addressing
IS-IS Processes
34

Additional information helpful to
understand and some of those little items
they like to ask us about on certification
exams
Terminology
CLV (Code/Length/Value) and TLV
(Type/Length/Value)
Same thing, CLV is more of the OSI term
There are variable length fields in a PDU
Code or Type specifies the type of information
Length specifies the size of the Value field
Value is the information itself
o Example CLV or TLV 128 defines the capability to
carry IP routes in IS-IS packets, in essence TLV 128
is Integrated IS-IS
35
IS-IS Routing Process

IS-IS Routing Process had four stages:
1. Update
2. Decision
3. Forwarding
4. Receive

Update
Routers can only forward data packets if
they have an understanding of the
network topology
LSPs are generated and flooded
throughout the network whenever:
An adjacency comes up or down
(example: a new router comes online)
An interface on a router changes state or is
assigned a new metric
An IP route changes
(example: because of redistribution)
36

Update
Sending and Receiving an LSP
Receiving an LSP
If the LSP is already present in the database
(LSDB), the router (IS) acknowledges (PSNP)
and ignores it
The router sends the duplicated LSP it its
neighbours
L1 LSPs are flooded throughout the area
L2 LSPs are sent across all L2 adjacencies

Update
Sending LSPs on a Point-to-Point Interface

When an adjacency is established, both routers send a CSNP
[OSPF DBD] summary of their LSDB
If the receiving router has any LSPs that were not present in the
CSNP it received, it sends a copy of the missing LSP to the other
router
CSNP
You are
missing
LSP 3
CSNP
LSP 3
PSNP (Ack)
37

Update
Sending LSPs on a Point-to-Point Interface

If the receiving router is missing any LSPs received in the CSNP, the
receiving router sends a PSNP [OSPF LSR] requesting the full LSP to be sent
LSPs are acknowledges with a PSNP [OSPF LSAck]
When the LSP is sent, the router sets a timer (Cisco default = 5 seconds)
o LSP is resent if the acknowledgement (PSNP) is not received within 5 seconds
CSNP
CSNP
PSNP 3
LSP 3
PSNP (Ack)
I am
missing
LSP 3

Update
Sending LSPs on a Broadcast Interface
The DIS [OSPF DR] takes on much of the
responsibility for synchronising databases on
behalf of the pseudonode
DIS has three tasks:
1. Creating and maintaining adjacencies
2. Creating and updating the pseudonode LSP
3. Flooding the LSPs over the LAN
38

Update
Sending LSPs on a Broadcast Interface

On receiving a CSNP the router compares it with its LSDB

If the receiving router has a newer version of the LSP then what was sent in the
CSNP, or if the CSNP did not contain one of its LSPs, the router multicasts the LSP
CSNP
(DBD)
LSP 88
I have a
newer version
of LSP 88
Receipt of LSP 88 is acknowledged by all routers with a PSNP.

Update
Sending LSPs on a
Broadcast Interface
On receiving a CSNP the
router compares it with its
LSDB
LSP 77
CSNP
(DBD)
(LSA)
PSNP
(LSAk)
PSNP
(LSR)
If the database is missing

an LSP that was in the
CSNP, it sends a PSNP
requesting the full LSP
The DIS sends the LSP
The receiving router
acknowledges with a PSNP
39

Update
Determining if an LSP is valid:
Receiving router uses three fields determine if the
received LSP is more recent than the LSDB entry
1. Remaining Lifetime
Used to age-out or delete LSPs
Lifetime is set to 0 and flooded
Receiving routers recognize this means the route
is bad and deletes the LSP from their LSDB,
rerunning SPF algorithm, new SPT, new routing
table.
Note: LSPs have a maxium age of 20 minutes in
an IS-IS LSDB, and are re-flooded (refreshed)
every 15 minutes.

Update
2. Sequence Number
First LSP starts with a sequence number of 1,
with following LSPs incremented by 1.
3. Checksum
If received LSPs checksum does not
computer correctly, the LSP is flushed and the
lifetime set to 0.
The receiving router floods the LSP with the
lifetime set to 0.
When the originating router gets this LSP
(lifetime = 0) it retransmits a new LSP.
40

Decision
The Decision Process
Uses Dijkstras algorithm to build a SPT (Shortest
Path Tree)
The SPT is used to create the forwarding table, also
known as the routing table
Several tables are used during this process:
PATH table
o PATH table is the SPT during the construction of the
LSDB
o Each candidate route is placed in the PATH table while
the metric is examined to determine if it is the shortest
path to the destination.
TENT is the tentative database (a scratchpad)

during this process

Decision
Determining the best route
Criteria by which the lowest cost paths are selected and
placed in the forwarding database are:
Cisco allows up to six equal-cost paths, four by default
Cisco only supports the default metric
Internal paths are chosen before external paths outside the routing
domain, to prevent sub-optimal routes and routing loops
L1 paths within the area are more attractive than L2 paths
outside the area, to prevent sub-optimal routes and routing loops
Longest match or most specific address in IP ensures that the
closest router is chosen
ToS (Type of Service) in IP header is used, if configured
If there is no path, the forwarding database sends the packet to
the nearest Level 2 router, which is the default router
41

Forwarding and Receiving
Forwarding process
After the SPT has been built the forwarding database can
be created
The forwarding table is the lookup table for the longest
match
The forwarding table for IS-IS is more relevant to CLNS
than to IP because the IP routing information is entered
directly into the IP routing table
Receive process
If the frame is valid, the receive process passes user data
and error reports to the forwarding process
Whereas routing information (Hellos, LSPs, and SNPs)
are sent to the update process
Receive process is primarily concerned with CLNS routing
and not IP
Route Summarisation
Rules for IS-IS route summarisation
similar to that of OSPF
Level 1-2 routers (L1L2)
Similar to OSPF ABR
Configured at the L1L2 router at the edge of an
area
L1L2 routers can summarise the routes within
their area to L1L2 or L2 routers in another area
This is an efficient method of establishing prefix
(network addresses) routing into other areas
42
Route Summarisation
If one edge L1L2 router in an area is
summarising routes for that area, another
edge L1L2 router in that area must also be
summarising routes
If other L1L2 routers are summarising and one edge
L1L2 router is not summarising, all traffic destined
for that area will be sent to the non-summarising
router because of longest match routing
L1 routes cannot be summarised within the

area because it is not permitted by IS-IS
(L1 routers cannot summary routes)
L2 ISs can summarise at the area boundary
Questions?
43

Is Is

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Is Is

Hochgeladen von

Copyright:

Verfügbare Formate

Advanced Network Design

Sources used in creating this IS-IS presentation:

IS-IS versus OSPF

IS-IS is exactly the same as OSPF

IS-IS versus OSPF

IS-IS versus OSPF

LSAs are actually comparable to

DBD (Data Base

The term routing domain is also

IS-IS uses a backbone path

IS-IS versus OSPF

Internal, non-backbone router in

Any Level 2 router can distribute

Level 1-2 IS (router)

The System ID is the key for SPF

RFC 1918 Addresses

AFI is part of the NSAP.

IS-IS versus OSPF

IS-IS versus OSPF

SPF Delay/Holdtime 5.5 sec / 10 sec

History of IS-IS and OSPF

History of IS-IS and OSPF

History of IS-IS and OSPF

History of IS-IS and OSPF

Who uses IS-IS?

IS-IS is popular amongst telcos and large ISPs

Example of Tier-1 carriers (not necessarily IS-IS users)

OSI: Two Network Services,

Connection-Oriented Network Protocol: OSI network layer protocol that carries

IS-IS Protocol Options

Integrated IS-IS (RFC 1195)

OSI Routing Protocols:

OSI Routing Protocols: ES-IS

Boundary areas in IS-IS exists

These routers should be

Level 1 IS (L1 IS, router)

Level 2 IS (L2 IS, router)

Level 1 and Level 2 IS

Level 1 IS (L1 IS, router)

Level 1 routers maintain

Level 2 IS (L2 IS, router)

Interconnect Level 1 areas

Stores separate database

Level 1 and Level 2 IS

Maintain both Level 1 and

Supports Level 1 function,

Inform Level 1 routers that the

Supports Level 2 function,

IS-IS does not share the

An IS-IS backbone can

The IS-IS backbone (path)

Where is the backbone?

OSI network layer

We will not cover the variety

Network Service Access Points

Format of the Cisco NSAP address consists of three parts:

Network Service Access Points

Area address is a variable length field

System ID is the ES or IS identifier within an area, similar

The NSAP Selector byte is a service identifier

Do I have to know this?

NSAP addresses are required for CLNS routing

Cisco Format NSAPs