Intermediate System to Intermediate System (IS-IS, also written ISIS) is a link-state interior gateway protocol (IGP), typically deployed within a single autonomous system, and is used in large enterprise and service provider networks to exchange routing information. The IS-IS protocol is defined in ISO/IEC 10589:2002 as an international standard within the Open Systems Interconnection (OSI) reference model. IS-IS operates by flooding link state information throughout a network of routers. Each IS-IS router builds its own link-state database (LSDB) by collecting the flooded link-state information from other routers. Like OSPF, IS-IS uses Dijkstra's algorithm for computing the shortest paths through the network. Packets (datagrams) are then forwarded along the computed shortest paths to their destinations.
History IS-IS was developed by Digital Equipment Corporation as part of DECnet Phase V. The Internet Engineering Task Force (IETF) published an IS-IS specification in 1990, but that RFC was later retracted and marked as historic because it republished a draft rather than a final version of the International Organization for Standardization (ISO) standard, causing confusion. The protocol was standardised by ISO in 1992 as ISO 10589 for use between Intermediate Systems rather than end systems or hosts. The purpose of IS-IS was to make the routing of datagrams possible using the ISO-developed OSI protocol stack called Connectionless-mode Network Service (CLNS). IS-IS was developed at roughly the same time that the Internet Engineering Task Force IETF was developing a similar protocol called OSPF. IS-IS was later extended to support routing of datagrams in the Internet Protocol (IP), the network-layer protocol of the global Internet. This extension is known as Integrated IS-IS. By 2005, IS-IS had become the de facto standard for large service provider network backbones.
IS-IS terminology The ISO IS-IS standard defines its own terminology for network components, some of which differs from the terms usually found in the industry.
Intermediate System: A router Designated Intermediate System: An IS selected to represent other ISs on a shared circuit. End System (ES): A host or device that does not participate in routing. Circuit: A Layer 2 broadcast domain. Such as a point-to-point link, or a LAN. Adjacency: A neighboring IS that an IS exchanges routing information with. Type-length-value (TLV): The link state information is encoded into TLVs and then packed into one or multiple LSPs. Link State PDU(LSP): IS-IS packets used for sharing link state information.
Packet types IS-IS operates over both broadcast (LAN) and point-to-point network links. Adjacencies are formed between neighboring routers to exchange routing information.
IS-IS Hello PDU (IIH) IS-IS Hello PDUs are exchanged periodically to establish and maintain adjacencies. On broadcast networks, a Designated Intermediate System (DIS) is elected based on interface priority and system ID. This hello packet will be sent separately for Level 1 or Level 2. There are three IS-IS hello packets depending on the circuit type. LAN L1 (PDU type 15) LAN L2 (PDU type 16) P2P (PDU type 17). On point-to-point links, there are no separate hello packets per level like there are on broadcast links. Unlike OSPF, IS-IS does not require matching hello intervals, although significant mismatches may affect adjacency stability. Link State PDU (LSP) This contains the actual routing information. The LSP contains a number of fields called type–length–values (TLVs), which contain the routing data. Each LSP is identified by an LSP ID and consists of a System ID, Pseudonode ID and Fragment ID. In this example LSP with ID 1921.6820.0002.02-01, 1921.6820.0002 is the System ID (that generated this LSP), 02 is the Pseudonode ID, 01 is the Fragment ID. If the Pseudonode ID is equal to zero, then it represents a real intermediate system. Any non-zero value means that the LSP is generated by a DIS (Pseudonode). If an LSP exceeds the maximum transmission unit (MTU), it is fragmented into multiple LSPs distinguished by a Fragment ID. Fragment numbering begins at zero; an unfragmented LSP consists of a single fragment (ID 0), while additional fragments are assigned incrementing identifiers. Complete Sequence Number PDU (CSNP) The Complete Sequence Number PDU (CSNP) is sent by the Designated Intermediate System (DIS) at regular intervals, typically every 10 seconds. It contains a summary of Link State PDUs (LSPs), including sequence numbers and checksums. Partial Sequence Number PDU (PSNP) If a router detects discrepancies between its link-state database and a received CSNP, it sends a PSNP requesting the missing or updated LSPs.
IS-IS addressing and NET Unlike most IP routing protocols, IS-IS operates directly over Layer 2 rather than relying on Layer 3 for transport, and does not use IP addresses to identify interfaces. Instead, IS-IS identifies interfaces using Layer 2 addresses (SNPA, e.g. MAC addresses on Ethernet), and identifies routing nodes using ISO network addresses. Each Intermediate System is assigned a Network Entity Title (NET), which is an NSAP address used to identify the router within the IS-IS routing domain. A NET is an NSAP used as a Network Entity Title where the NSEL field is set to zero. While not required by the protocol, a common operational practice is to set the System ID field to a unique IPv4 address from one of the router’s loopback interfaces. On a single intermediate system there can be up to 3 NET addresses. This may be useful during migration of an IS from one area to another. The NET consists of an Area, System ID and NSEL field. Area itself consists of an AFI (Address Family Identifier) and an Area ID. Area can have a variable length of 1–13 bytes. The System ID is six bytes long and the NSEL is one byte. As an example, the fields of the ISO Network Address "49.0100.1921.6821.1138.00" are as follows:
49 is the AFI. 49 specifically represents the "private address space", similar to RFC1918 for IPv4., 0100 is the Area ID, 49.0100 is the Area, 1921.6821.1138 is the System ID, 00 is the NSEL, which must be zero. Routers will not form adjacencies with routers with a non-zero NSEL in their NET, as that field is only used by the NSAP.
… excerpt ends here. Continue reading the full article.
