REDES DE DATOS II

Clase 4. IS-IS

Alberto Arellano A. Ing. Msc.

[email protected]
CCNA – CCNP – CCSP – LPI - JNCIA
 What is IS-IS?
• Intermediate System to Intermediate System
• An “IS” is ISO terminology for a ROUTER
• IS-IS was originally designed for use as a dynamic routing
protocol for ISO CLNP(Connectionless-mode Network
Protocol), defined in the ISO 10589 standard.
• Later adapted to carry IP prefixes in addition to CLNP (known as
Integrated or Dual IS-IS) as described in RFC 1195 (12/1990)
• Easily extensible with Type/Length/Value (TLV) extensions;
• IPv6 Address Family support (RFC 5308) (10/2008)
• Multi-Topology support (RFC 5120) (02/2008)
• MPLS Traffic Engineering (RFC 5316) (12/2008)
• Predominantly used in ISP environment or Large Enterprise
Networks
 What is IS-IS?
• IS-IS is a Layer 2 protocol and is not encapsulated in IP
• IS-IS Protocol Data Unit (PDU) uses Ethertype 0x8872
• IS-IS Fixed header (8 bytes)
• IS-IS Data encoded as Type-Length-Value (TLV)
Packets IS-IS
LSA / LSP
 IS-IS Operation
Routers with IS-IS enabled on them look for neighbouring
routers also running IS-IS.
• Hello Protocol Data Units (PDUs) are exchanged
• The “Hello” packet includes the list of known neighbours,
and details such as “hello interval” and “router dead
interval”
• Hello interval – how often the router will send Hellos
• Router dead interval – how long to wait before deciding router has
disappeared
• The values of “hello interval” and “router dead interval” must match on
both neighbours.
• When a neighbouring router responds with matching
details, a neighbour relationship is formed
IS-IS Operation
IS-IS & OSPF Packets
 IS-IS Adjacencies
 A relationship is formed between neighbouring routers for the
purpose of exchanging routing information
• This is called an ADJACENCY
 Once an adjacency is formed, neighbours share their link state
information
• Information goes in a Link State PDU (LSP)
• LSPs are flooded to all neighbours
 New information received from neighbours is used to compute a new
view of the network
 On a link failure
• New LSPs are flooded
• The routers recompute the routing table
IS-IS Adjacencies
 IS-IS Areas
For Link State routing
protocols, the area groups
several routers within the same
flooding domain.
• Sub domain (area)
• Level-2 Sub domain (backbone)
• Level-1 area
• Level-1-2 router (L1-L2)
• IS-IS does not have back- bone
“area”
• A backbone is a contiguous
collection of Level-2 routers
 IS-IS Hierarchy Levels
• IS-IS presently has a two-layer
hierarchy
• The backbone (level 2)
• Non-backbone areas (level 1)
• An IS (router) can be either:
• Level 1 router (used for intra-
area routing)
• Level 2 router (used for inter-
area routing)
• Level 1–2 router (intra and inter-
area routing)
 Level 1 Router
 Level 1-only routers
– Can only form adjacencies with Level 1 routers with-in the
same area
– Link State Data Base (LSDB) only carries intra-area
information
Level 1-2 Routers
 These level 1-2 routers will establish two neighbor
adjacencies:
– Level 1 neighbor adjacency with the router in the same
area.
– Level 2 neighbor adjacency with the router in the other
area.
 Level 2 Router
 Level-2-only
routers
– Exchange
information
about the L2
area
The level two routers form
a continuous string of
backbone routers
 LSPs (Link State Packets)
 IS-IS uses LSPs (Link State Packet) which is similar to OSPF’s LSAs.
In the LSP you will find:
• One or more prefixes
• Adjacent neighbors
• Metric
Links in IS-IS
 Two types of links in IS-IS:
– Point-to-point link: Only one other router on the link, forming a
point-to-point adjacency
– Multi-access network (e.g. ethernet): Potential for many other
routers on the network, with several other adjacencies.
 IS-IS in multi-access networks has optimizations to aid
scaling
– One router is elected to originate the LSPs for the whole multi-
access network
– Called “Designated Intermediate System”
– Other routers on the multi-access network form adjacencies with
the DIS
 NET (Network Entity Title)
Today, ISIS conveys IP routing information, nevertheless each IS (router)
is still identified via an OSI address: used to originate the LSP. ISIS
requests only one OSI address or NET (Network Entity Title) per router.
The NET address is a variable data, but it usually has a size of 10
bytes. The NET is made of 3 parts:
• The Area ID
• The System ID
• The NSEL (NET Selector)
NET (Network Entity Title)
 Area ID:
– Variable part of the NET address: usually equal to 1, 3 or 5 bytes.
– The first byte (AFI – Address Family Identifier): (like IP : Public, private
address). Just remember that usually SP has not a public range of ISO
addresses and uses the AFI = 49 (private-addressing)
– The following bytes of the AREA ID can be arbitrary filled to represent the
Area number: useful for Level 1 adjacency.
 System ID:
– Like the OSPF router-id this identifies uniquely the router.
 System ID :
– Usually System ID is derived from the IP loopback address, 3 known methods
are used:
 NSEL:
– The NSEL is like the Protocol field of the IP header. It must be set to 0x00 in
order to an adjacency comes up.
SYSTEM ID
NET Configuration
On CISCO IOS, the NET address is configured at the loopback
level:

On Juniper JUNOS, the NET address is configured at the

loopback level:
 Hello Messages IS L1/L2

 IS-IS uses Hello PDUs to IIH

establish adjacencies with
other routers. IS IS
L1 L1
 IS-IS has three types of
Hello PDUs: ISH ESH
– ESH, sent by ES to an IS
– ISH, sent by IS to an ES ES ES
– IIH, used between two
ISs
 IS-IS Timers
 IS-IS discover neighbors and forms adjacencies using IS-IS
Hello PDUs.
• Transmitted every 10 seconds
• Can be changed using the interface command, is
hello-interval
 Hold time defaults to 3 times the Hello time (30 seconds),
before declaring a neighbor dead.
• Changed using the interface command is hello-
multiplier
• Default is 3
Metric and Calculate the Shortest Path
IS-IS has four metric values that it can work with:
– Default Metric: every interface has a default metric of 10, no matter
the bandwidth. A gigabit interface gets the same metric as a serial
link. We can manually configure a different metric for each interface.
– Delay: similar to how EIGRP uses delay.
– Expense: the actual monetary cost of a link.
– Error: similar to how EIGRP uses reliability.
 Cisco and Juniper routers, however, only support the default metric.
 By default, supports narrow metrics, which means you can define cost
values between 1-63. To solve this problem, enable wide metrics, which
allows you to define cost values between 1-16777214. (metric-style
wide)
Total cost of any route = sum of metrics of the outgoing interfaces.
 Configure IS-IS – CISCO IOS
e0/0 e0/0 Lo0=192.168.0.1/32
Lo0=192.168.0.1/32
R1L1/L2 R2
10.10.10.0/24

R1 R2
int lo0 int lo0
ip add 192.168.0.1 255.255.255.255 ip add 192.168.0.2 255.255.255.255
ip router Isis ip router Isis
exit exit
int e0/0 int e0/0
ip add 10.10.10.1 255.255.255.0 ip add 10.10.10.2 255.255.255.0
ip router ip router Isis
exit exit
router Isis router Isis
net 49.0001.1921.6800.0001.00 net 49.0001.1921.6800.0002.00
Configure IS-IS – CISCO IOS XR
 Configure IS-IS - JUNIPER
em0 em0 Lo0=192.168.0.1/32
Lo0=192.168.0.1/32
R1L1/L2 R2
10.10.10.0/24

set interface em0 unit 0 family inet address 10.10.10.1/24

set interface em0 unit 0 family iso
set interface lo0 unit 0 family inet address 192.168.0.1/32
set interface lo0 unit 0 family iso address 49.0001.1921.6800.0001.00
set protocols isis interface em0
set protocols isis interface lo0
commit
 Configure IS-IS - HPE
Gi0/0/1 Gi0/0/1 Lo0=192.168.0.1/32
Lo0=192.168.0.1/32
R1L1/L2 R2
10.10.10.0/24

system-view
isis 1
is-level level-1
network-entity 49.0001.1921.6800.0001.00
quit
interface gigabitethernet 1/0/1
isis enable 1
quit
Lab. IS-IS IPv4 Multivendor
Configure IS-IS Core Network – R2
Configure IS-IS Core Network – JUN-1
configure
set interfaces em0 unit 0 family inet address 10.10.2.2/24
set interfaces em0 unit 0 family iso
set interfaces em1 unit 0 family inet address 200.10.10.253/30
set interfaces em2 unit 0 family inet address 10.10.5.1/24
set interfaces em2 unit 0 family iso
set interfaces em3 unit 0 family inet address 10.10.3.1/24
set interfaces em3 unit 0 family iso
set interfaces lo0 unit 0 family inet address 192.168.0.2/32
set interfaces lo0 unit 0 family iso address 49.0006.1921.6800.0002.00
set protocols isis interface em0
set protocols isis interface em2
set protocols isis interface em3
set protocols isis interface lo0
commit
Configure IS-IS Core Network – JUN-2
configure
set interfaces em0 unit 0 family inet address 10.10.5.2/24
set interfaces em0 unit 0 family iso
set interfaces em1 unit 0 family inet address 10.10.6.1/24
set interfaces em1 unit 0 family iso
set interfaces lo0 unit 0 family inet address 192.168.0.3/32
set interfaces lo0 unit 0 family iso address 49.0006.1921.6800.0003.00
set protocols isis interface em0
set protocols isis interface em1
set protocols isis interface lo0
commit
Configure IS-IS Core Network – R4
Configure IS-IS Core Network – JUN-3
configure
set interfaces em0 unit 0 family inet address 10.10.4.2/24
set interfaces em0 unit 0 family iso
set interfaces em1 unit 0 family inet address 10.10.7.2/24
set interfaces em1 unit 0 family iso
set interfaces em2 unit 0 family inet address 10.10.3.2/24
set interfaces em2 unit 0 family iso
set interfaces lo0 unit 0 family inet address 192.168.0.5/32
set interfaces lo0 unit 0 family iso address 49.0006.1921.6800.0005.00
set protocols isis interface em0
set protocols isis interface em1
set protocols isis interface em2
set protocols isis interface lo0
commit
Verify IS-IS Neighbors
Verify IS-IS Routing Table
Verify IS-IS Routing Table
Redistribute Default Route&Static Route
Redistribute Default Route&Static Route-Cisco
Redistribute Static Route - Juniper
1.- Create Static Route
2.- Create Policy Routing
3.- Export Policy Routing into Protocol ISIS

set routing-options static route 172.20.20.0/24 next-hop 200.10.10.254

edit policy-options
set policy-statement exportarRutaEstatica term 1 from protocol static
set policy-statement exportarRutaEstatica term 1 then accept
exit
set protocols isis export exportarRutaEstatica
commit
Redistribute
Static Route -
Juniper
IS-IS only IPv6
IS-IS with dual stack

Dual IPv4/IPv6 configuration.

Redistributing both IPv6 static
routes and IPv4 static routes.
IS-IS IPv6 Single Topology

In Single topology IS-IS for IPv6 uses the same SPF

for both IPv4 and IPv6.
• IPv4 and IPv6 topologies MUST match exactly
• Cannot run IS-IS IPv6 on some interfaces, IS-IS
IPv4 on others.
• An IS-IS IPv6-only router will not form an
adjacency with an IS-IS IPv4/IPv6 router.
 IS-IS IPv6 Single Topology

interface FastEthernet0/0.23
encapsulation dot1Q 23
ip address 20.2.3.2 255.255.255.0
ip router isis
ipv6 address 2001:20:2:3::2/64
ipv6 router isis
isis ipv6 metric 20
end

interface FastEthernet0/0.24
encapsulation dot1Q 24
ip address 20.2.4.2 255.255.255.0
ip router isis
ipv6 address 2001:20:4:2::2/64
ipv6 router isis
isis metric 20
end
IS-IS IPv6 Multi-Topology (RFC 5120)
• Multitopology IS-IS enables IS-IS to run independent IP
topologies in a single routing domain.
• This can be separate IPv4 topologies, separate IPv6
topologies, or a combination of both sets.
• When multitopology IS-IS is used, separate databases
are maintained for each topology and SPF runs are
performed separately for each database.
IS-IS IPv6 Multi-Topology (RFC 5120)