- Table of Contents
-
- 06-Network
- 01-Scanner
- 02-VRF
- 03-Interface
- 04-Interface pairs
- 05-Interface collaboration
- 06-Security zones
- 07-VLAN
- 08-MAC
- 09-DNS
- 10-ARP
- 11-ND
- 12-Forwarding advanced settings
- 13-ALG
- 14-GRE
- 15-IPsec
- 16-ADVPN
- 17-L2TP
- 18-SSL VPN
- 19-Routing table
- 20-Static routing
- 21-Policy-based routing
- 22-OSPF
- 23-BGP
- 24-IS-IS
- 25-RIP
- 26-IPv4 multicast routing
- 27-IPv6 multicast routing
- 28-PIM
- 29-IGMP
- 30-MLD
- 31-DHCP
- 32-HTTP
- 33-SSH
- 34-NTP
- 35-FTP
- 36-Telnet
- 37-MAC authentication
- 38-MAC address whitelist
- 39-MAC access silent MAC info
- 40-MAC access advanced settings
- 41-IP authentication
- 42-IPv4 whitelist
- 43-IPv6 whitelist
- Related Documents
-
Title | Size | Download |
---|---|---|
24-IS-IS | 37.40 KB |
IS-IS
This help contains the following topics:
¡ Configure an IS-IS interface
Introduction
IS-IS is a link-state interior gateway protocol (IGP) used within an AS. It uses the SPF algorithm for route calculation.
Network entities
A network entity title (NET) identifies the network layer information of an IS. It does not include transport layer information. A NET is a special NSAP address with the SEL being 0. The length of a NET is in the range of 8 to 20 bytes, same as a NSAP address.
A NET includes the following parts:
· Area ID—The length of an area ID is 1 to 13 bytes.
· System ID—A system ID uniquely identifies a host or router in the area and it length is fixed at 6 bytes.
· SEL—The SEL value is 0 and the length is fixed at one byte.
For example, for a NET ab.cdef.1234.5678.9abc.00, the area ID is ab.cdef, the system ID is 1234.5678.9abc, and the SEL is 00.
Typically, a router only needs one NET, but it can have a maximum of three NETs for smooth area merging and partitioning. When you configure multiple NETs, make sure they have the same system ID.
IS-IS areas
IS-IS has a 2-level hierarchy to support large-scale networks. A large-scale routing domain is divided into multiple areas. Typically, a Level-1 router is deployed within an area. A Level-2 router is deployed between areas. A Level-1-2 router is deployed between Level-1 and Level-2 routers.
· Level-1 router
A Level-1 router establishes neighbor relationships with Level-1 and Level-1-2 routers in the same area. It maintains an LSDB comprising intra-area routing information. A Level-1 router forwards packets destined for external areas to the nearest Level-1-2 router.
Level-1 routers in different areas cannot establish neighbor relationships.
· Level-2 router
A Level-2 router establishes neighbor relationships with Level-2 and Level-1-2 routers in the same area or in different areas. It maintains a Level-2 LSDB containing inter-area routing information. All the Level-2 and Level-1-2 routers must be contiguous to form the backbone of the IS-IS routing domain.
Level-2 routers can establish neighbor relationships even if they are in different areas.
· Level-1-2 router
A router with both Level-1 and Level-2 router functions is a Level-1-2 router. It can establish Level-1 neighbor relationships with Level-1 and Level-1-2 routers in the same area. It can establish Level-2 neighbor relationships with Level-2 and Level-1-2 routers in different areas. A Level-1 router can reach other areas only through a Level-1-2 router. The Level-1-2 router maintains two LSDBs, a Level-1 LSDB for intra-area routing and a Level-2 LSDB for inter-area routing.
Configure IS-IS
Configure an IS-IS instance
1. Click the Network tab.
2. In the navigation pane, select Routing > IS-IS.
3. Click Create.
4. Configure the IS-IS instance parameters.
Table 1 IS-IS instance parameters
Item |
Description |
Specify an instance ID. |
|
Level |
Specify an IS level. Options include Level-1, Level-2, and Level-1-2: · Level-1—A Level-1 router maintains a Level-1 LSDB comprising intra-area routing information. · Level-2—A Level-2 router maintains a Level-2 LSDB containing inter-area routing information. · Level-1-2—A Level-1-2 router has both Level-1 and Level-2 router functions. It maintains two LSDBs, a Level-1 LSDB for intra-area routing and a Level-2 LSDB for inter-area routing. |
Network entity title |
Specify a network entity title for the IS-IS process. A network entity title is a dotted hexadecimal string in X…X.XXXX....XXXX.00 format. The X…X segment represents the area address, the XXXX....XXXX segment represents the system ID, and the 00 segment is the SEL. |
5. Click OK.
The IS-IS instance will be displayed on the IS-IS instance page.
Configure an IS-IS interface
1. Click the Network tab.
2. In the navigation pane, select Routing > IS-IS.
3. Click the Interface List tab.
4. Configure the following interface parameters as needed.
Table 2 IS-IS interface parameters
Item |
Description |
Interface |
Interface that runs IS-IS. |
Select whether to enable IS-IS on the interface and specify a circuit level. Level options include Level-1, Level-2, and Level-1-2. For an interface of a Level-1 router, the circuit level can only be Level-1. For an interface of a Level-2 router, the circuit level can only be Level-2. For an interface of a Level-1-2 router, you must specify a circuit level to form only the specified level neighbor relationship. |
|
Level-1 link cost |
Specify the link cost used for Level-1 route calculation. |
Level-2 link cost |
Specify the link cost used for Level-2 route calculation. |
5. Click Apply.