ISIS Coneptual Part
ISIS Coneptual Part
Whole Story
Link-state Review
IS-IS Levels
Operation of IS-IS
Attached Bit
NSAP Addressing
IS-IS Adjacency States
Protocol Data Unit Types
DIS
TLV
Link-state Database
Database Integrity
SPF and path selection criteria
Whole Story
The International Standards Organization (ISO) calls a router an intermediate system. A host is referred
to as an end system by the ISO. Since routers connect hosts in the IP world, intermediate systems
connect end systems in an ISO network. IS-IS was originally designed to support the Connectionless
Network Protocol (CLNP) and was later adapted to support IP reachability. Both the IP and CLNP
information is carried within the payload of the IS-IS routing updates. The Juniper Networks
implementation of IS-IS supports only IP routing
1. Level – 1
2. Level – 2
Level 2
Two IS-IS routers form an adjacency and share database information when both ends of their common
link are configured for Level 2 irrespective of area value. Let’s take a look at Figure 7.2. All of the
interfaces on Riesling are within the defined Level 2 area. In addition, both Cabernet and Merlot have an
interface within that same Level 2 area. The dotted line represents the shared topology knowledge
within the Level 2 link-state databases on the routers. The area values are different on the routers
(49.0001 and 47.0005.80.8300), but the only requirement for a Level 2 adjacency is that each end of the
link reside within Level 2.
Level 1
The requirements for a Level 1 adjacency are a bit different. Two IS-IS routers form an adjacency when
each end of the common network link is configured for Level 1 and the IS-IS area value of each router is
identical. Figure 7.3 displays a Level 1 area. All interfaces on Shiraz and a single interface on Cabernet
and Merlot reside within Level 1. Cabernet, Merlot, and Shiraz all share an IS-IS area value of
47.0005.80.8300. This common area value allows adjacencies to form and updates to be exchanged. As
before, all interfaces bounded by the dotted line exchange link-state updates. When the common link
between Cabernet and Riesling is configured for Level 1, no IS-IS adjacency forms since the area values
of the two routers are different. Only a Level 2 adjacency can form between these two routers.
Tip
L1 / L2 router has separate database for each level like ABR in OSPF. Both Cabernet and Merlot have two
link-state databases. One database contains the Level 1 data while the other contains the Level 2
information. The Dijkstra Algorithm is calculated within each level database.
Operation of ISIS
1. An individual ISIS router can be one of the following.
a. Level-1 router --- L1
b. Level-2 router --- L2
c. Level-1 and Level-2 router L1/L2 Junos Default router
2. L1 routers contain IP routes for their specific level and maintain default route 0.0.0.0/0 toward
backbone network.
3. L2 routers are considered as backbone routes and have full knowledge of the network. It means
that routes in Level 1 are also present in Level 2.
4. In hierarchical network design, at least one router should be L1/L2 router.
Attached Bit (if data wants to send then use default gateway of l1/l2)
An L1/L2 router connected to another L2 router in a different area sets the attached bit in its L1 updates.
An L1 router that receives an update with the attached bit set assumes that the L1/L2 router has
reachability to the remainder of the network. The L1 router installs a 0.0.0.0 /0 default route locally that
points to the L1/L2 router as a next hop. Since all Level 1 routers have explicit knowledge of routes
within their area, the default route is used only to reach routes outside the Level 1 area.
NSAP Addressing
Network Entity Title is divided into three major parts. Remem imp
1. Area
a. AFI (Authority and Format Identifier)
b. IDI (Initial Domain Identifier)
c. DSP (Domain Specific Part)
2. System ID (network sap address)
3. N-SELECTOR
IS-IS uses the standard Network Service Access Point (NSAP) addressing as defined in ITU X.213. The
size of the NSAP address varies from 8 to 20 bytes in length. There are three major parts to the address
structure: area, system ID, and N-selector. The first part of the address indicates the IS-IS area value.
This field begins with the Authority and Format Indicator (AFI), is followed by the Initial Domain
Identifier, and finishes with the Domain-Specific Part (DSP). The AFI byte indicates the governing body
that administers the address space and assigns addresses. Networks often use 0x49 as their AFI, which
represents the private NSAP address space. The NSAP private addresses are analogous to the private IP
address space defined in RFC 1918. Your network requires a registered address only when
Connectionless Network Protocol (CLNP) routing(direction) is desired with another network. The JUNOS
software default does not route CLNP packets, so using private NSAP area addresses is perfectly fine.
New
This state is seen when the IS-IS adjacency process is just beginning. Start events could include router
boot-up or initial configuration.
One-Way
Your IS-IS router transitions to this state after sending an IS-IS Hello PDU. In addition, any received hellos
do not contain the local router’s address as a neighbor.
Initializing
When a local router sees itself in a neighbor’s hello, it transitions to this state. This state shows that
bidirectional communications are established.
Up
This is a fully functioning state for IS-IS. An adjacency relationship is formed and the databases have
been exchanged.
Down
This represents a nonfunctioning adjacency. An IS-IS router moves to this state for one of several
reasons, including area mismatches, expiration of the hold time, and authentication failures.
Reject
Upon an authentication failure, an IS-IS router will transition between this state and the Down state.
FIGURE 7. 6
IS-IS startup sequence and Information Exchange
Router A and Router B are forming an adjacency and exchanging the information in their databases. The
specific steps of this process are:
2. Each router sends a Complete Sequence Number PDU (CSNP) to its peer. These contain a complete
summary listing of the link-state database, including sequence numbers and the age of each data
segment.
3. Router B determines that it is missing information from its database and sends a Partial Sequence
Number PDU (PSNP) to Router A.
4. Router A responds to this request with a link-state PDU (LSP) containing the requested information.
5. Router B issues either a PSNP (on a point-to-point link) or a CSNP (on a broadcast link) to inform
Router A that the advertised link-state PDU was received. This acknowledgement is a critical step
because it guarantees the reliable flooding of database information to all routers in the network.
TIP
Router issues a CSNP on a broadcast link for acknowledgement only when it’s the Designated
Intermediate System for that link.
Detail of PDU
We will discuss each PDU in detail. Each PDU sent has common header, let discuss it first.
Each PDU shares a common header, illustrated in Figure 7.7. The header consists of the following fields:
Protocol ID (1 octet): This field is set to a constant value of 0x83 and designates that the higher-level
data belongs to IS-IS.
Header Length (1 octet): This field indicates the total length, in octets, of the IS-IS headers. It includes
both the common IS-IS header and any PDU-specific headers that follow.
Version/Protocol ID Extension (1 octet): This field is set to a constant value of 0x01. The IS-IS
specification defines this field as an extension area for the Protocol ID data. The JUNOS software does
not implement this function.
ID Length (1 octet): This field is used to inform other systems of the system ID length. For backward
compatibility, the default length of 6 bytes is represented with the constant value of 0x00. The JUNOS
software does not use a larger ID size, so this field is set to a constant value of 0x00.
PDU Type (1 octet): This field designates the PDU carried after the common header. The first 3 bits are
set to 0. The remaining bit combinations include:
Version (1 octet): This field is set to a constant value of 0x01, the current IS-IS version.
Maximum Area Addresses (1 octet): This field is set to a constant value of 0x00. It informs other
systems how many area addresses are supported by the local router. A value of 0 means that no more
than three area addresses are assigned to this router.
Details of each PDU type follow the common header. The information within the PDUs is encoded in a
format called a triple (Type, Length, Value). IS-IS makes extensive uses of this format (often abbreviated
as TLV) to convey information within its messages
L1 LAN Hello PDUs are multicast to the “All L1 ISs” address of 01:80:c2:00:00:14. L2 routers share a
separate multicast address “All L2 ISs” of 01:80:c2:00:00:15. Both LAN Hello PDUs share a common
packet format, as shown in Figure 7.8. The IS-IS LAN Hello PDU consists of the following fields:
Circuit Type (1 octet): The first 6 bits are set to 0. The remaining bits designate the level at which the
interface is operating: L1 (0x01), L2 (0x02), or L1/L2 (0x03). PDUs with a value of 0x00 in this field are
ignored.
L1 bit 7 6 5 4 3 2 1 0
0x01 0 0 0 0 0 0 0 1
L2 bit 7 6 5 4 3 2 1 0
0x02 0 0 0 0 0 0 1 0
L1/L2
bit 7 6 5 4 3 2 1 0
0x03 0 0 0 0 0 0 1 1
Source ID (6 octets): This field designates the sender of the IIH. The field is set to the 6-byte system ID of
the sending router.
Holding Time (2 octets): The value in this field represents the amount of time each neighboring router
should wait before terminating the adjacency after the last received IS-IS Hello PDU from this neighbor.
PDU Length (2 octets): The value in this field represents the total length of the IS-IS Hello PDU. The field
is set to a constant value of 1492 bytes (0x05D4).
Priority (1 octet): The first bit is set to 0. The remainder of the byte designates the value used for the
election of the DIS. The default value for the JUNOS software is 64.
LAN ID (7 octets): This field designates the ID of the current DIS on the broadcast circuit. The field is set
to the 6-byte system ID and 1-byte circuit ID of the DIS.
TLVs (Variable): This field contains information about the sending router, including the area address,
neighbor ID, authentication, and interface addressing.
Relevant portions of the output have been highlighted. You see the Circuit Type, Circuit ID, Hold Time,
and Priority fields. Shiraz is advertising a hold time of 27 seconds. This is the default value for the JUNOS
software on LAN interfaces unless the local router is the DIS. Hello PDUs are advertised every (hold
time / 3) seconds, so the default Hello timer is 9 seconds. Shiraz is also advertising a local DIS priority of
64, the JUNOS software default. This is the first tiebreaker for the election of the DIS.
DIS (Designated Intermediate System) like OSPF DR for broadcast use only
DIS helps to reduce the amount of data in the link-state database and aid in the processing of the
shortest path first (SPF) calculation.
DIS is elected only on a broadcast-capable link.
Reduce LSP Flooding, Facilitate Database Synchronization
DIS election steps are as follows.
Length (2 octets) The total length of the CSNP, in octets, is encoded in this field.
Source ID (7 octets) This field designates the sender of the CSNP. It is set to the 6-byte system ID and 1-
byte circuit ID (0x00) of the sending router.
Start LSP ID (8 octets) This field is set to a constant value of 0x0000.0000.0000.00-00. It designates the
smallest possible LSP ID value.
End LSP ID (8 octets) This field is set to a constant value of 0xFFFF.FFFF.FFFF.FF-FF. It designates the
largest possible LSP ID value.
TLVs (Variable) This field contains the summary database information from the local router.
Each segment of Riesling’s database contains the LSP ID, a sequence number, a lifetime value, and a
checksum. The combination of these data segments uniquely identifies each LSP in the network. As
Cabernet receives the CSNP, it checks the database entries against its own local link state database. If
some advertised information is missing, Cabernet requests the specific LSP details using a Partial
Sequence Number PDU. At this point, Cabernet’s local database matches the advertised LSP
information. The JUNOS software designates a match with the Matched database, matching sequence
numbers message.
Link-State PDU
Thus far, we’ve been talking about the link-state database from numerous perspectives. IS-IS routers
have formed adjacencies and compared their databases. Complete and Partial Sequence Number PDUs
have been sent between routers to synchronize the databases. We’ve failed to discuss the actual
database information to this point. Let’s now tackle this subject. A link-state PDU (LSP) contains
information about each router in the network and its connected interfaces. Metric and IS-IS neighbor
information is also included.
Database Integrity
Each router in the IS-IS network maintains a complete link-state database for each of its configured
levels. We can view all database entries in the network by using the show isis database command.
The advertised LSPs in each level must be identical on each router. Each LSP in the database is uniquely
identified by its 8-byte LSP ID, which contains the system ID, circuit ID, and LSP number fields. New
versions of each LSP begin with a sequence number of 0x00000001 and count up to a maximum value of
0xffffffff. If an IS-IS router receives an LSP with a known LSP ID and an updated sequence number, it
assumes that the received LSP is more up-to-date than the current LSP and installs it in the database.
To maintain an accurate link-state database, LSPs have a defined lifetime, during which they are
considered active and usable. The LSP header contains a configurable remaining lifetime field, which
counts down to a value of 0. By default, the JUNOS software sets the beginning lifetime of all LSPs to
1200 seconds (20 minutes). The originating router is responsible for re-flooding its own LSP before the
remaining lifetime reaches 0 seconds. The JUNOS software accomplishes this task when the lifetime
reaches approximately 317 seconds.
Technical difference between ISIS and OSPF L2= BACKBONE AREA L1= none back area L1, info in tlv
in isis and info in lsa in ospf, packet in ospf, pdu in isis
The issue arises with SPF scalability. In OSPF, node reachability information and NLRI are advertise in
same LSA. When there is a change in NLRI (change of routes) happen in OSPF, SPF is run on whole node
which takes time. But in ISIS, node reachability is advertised in different TLV and NLRI is advertised in
different TLV. So when there is a change in NLRI, SPF is run only on that specific TLV not on the whole
node. It takes less time. Main purpose is looping avoidance that is why structure.