|
|
This chapter describes how to configure Integrated Intermediate System-to-Intermediate System (IS-IS). For a complete description of the integrated IS-IS commands listed in this chapter, refer to the "Integrated IS-IS Commands" chapter of the Cisco IOS IP and IP Routing Command Reference publication. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
IS-IS is an International Organization for Standardization (ISO) dynamic routing specification. IS-IS is described in ISO 10589. The Cisco implementation of IS-IS allows you to configure IS-IS as an IP routing protocol.
To configure IS-IS, perform the tasks in the following sections. Enabling IS-IS is required; the remainder of the tasks are optional, although you might need to perform them, depending upon your specific application.
In addition, you can filter routing information and specify route redistribution. For more information about these features, see the "Filter Routing Information" and "Redistribute Routing Information" sections, respectively, in the "Configuring IP Routing Protocol-Independent Features" chapter of this document.
Unlike other routing protocols, enabling IS-IS requires that you create an IS-IS routing process and assign it to a specific interface, rather than to a network. You can specify more than one IS-IS routing process per Cisco router, using the multiarea IS-IS configuration syntax. You then configure the parameters for each instance of the IS-IS routing process.
Small IS-IS networks are built as a single area that includes all the routers in the network. As the network grows larger, it is usually reorganized into a backbone area made up of the connected set of all Level 2 routers from all areas, which is in turn connected to local areas. Within a local area, routers know how to reach all system IDs. Between areas, routers know how to reach the backbone, and the backbone routers know how to reach other areas.
Routers establish Level 1 adjacencies to perform routing within a local area (intra-area routing). Routers establish Level 2 adjacencies to perform routing between Level 1 areas (interarea routing).
Some networks use legacy equipment that supports only Level 1 routing. These devices are typically organized into many small areas that cannot be aggregated due to performance limitations. Cisco routers are used to interconnect each area to the Level 2 backbone.
A single Cisco router can participate in routing in up to 29 areas, as well as perform Level 2 routing in the backbone. In general, each routing process corresponds to an area. By default, the first instance of the routing process configured performs both Level 1 and Level 2 routing. You can configure additional router instances, which are automatically treated as Level 1 areas. You must configure the parameters for each instance of the IS-IS routing process individually.
For IS-IS multiarea routing, you can configure only one process to perform Level 2 routing, although you can define up to 29 Level 1 areas for each Cisco router. If Level 2 routing is configured on any process, all additional processes are automatically configured as Level 1. You can configure this process to perform Level 1 routing at the same time. If Level 2 routing is not desired for a router instance, remove the Level 2 capability using the is-type command. Use the is-type command also to configure a different router instance as a Level 2 router.
Network entity titles (NETs) define the area addresses for the IS-IS area and the system ID of the router. Refer to the "Configuring ISO CLNS" chapter in the Cisco IOS Apollo Domain, Banyan VINES, ISO CLNS, and XNS Configuration Guide for a more detailed discussion of NETs.
To enable IS-IS and specify the area for each instance of the IS-IS routing process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router#router isis [area tag] | Enables IS-IS routing for the specified routing process, and places you in router configuration mode. Use the area tag argument to identify the area to which this IS-IS router instance is assigned. A value for tag is required if you are configuring multiple IS-IS areas. The first IS-IS instance configured is Level1-2 by default. Later instances are automatically Level1. You can change the level of routing to be performed by a particular routing process using the is-type command. |
Step2 | Router(config)#net network-entity-title | Configures NETs for the routing process. Specify a NET for each routing process if you are configuring multiarea IS-IS. You can specify a name for a NET and for an address. |
See the "IS-IS Configuration Examples" section at the end of this chapter for examples of configuring IS-IS as an IP routing protocol.
To enable IP routing and specify the area for each instance of the IS-IS routing process, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router#interface type number | Enters interface configuration mode. |
Step2 | Router(config-if)#ip router isis [area tag] | Configures an IS-IS routing process for ISO Connectionless Network Service (CLNS) on an interface and attaches an area designator to the routing process. |
Step3 | Router(config-if)#ipaddress ip-address-mask | Defines the IP address for the interface. An IP address is required on all interfaces in an area enabled for IS-IS if any one interface is configured for IS-IS routing. |
See the "IS-IS Configuration Examples" section at the end of this chapter for examples of configuring IS-IS as an IP routing protocol.
The Cisco IS-IS implementation allows you to alter certain interface-specific IS-IS parameters. Most interface configuration commands can be configured independently from other attached routers. The isis password command should configure the same password on all routers on a network. The settings of other commands (isis hello-interval, isis hello-multiplier, isis retransmit-interval, isis retransmit-throttle-interval, isis csnp-interval, and so on) can be different on different routers or interfaces. However, if you decide to change certain values from the defaults, it makes sense to configure them on multiple routers and interfaces.
You can perform these tasks, described in the following sections:
You can configure a cost for a specified interface. You can configure the default-metric for Level 1 or Level 2 routing. To configure the metric for the specified interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis metric default-metric {level-1 |
level-2}
| Configure the metric (or cost) for the specified interface. |
You can specify the length of time (in seconds) between hello packets that the Cisco IOS software sends on the interface.
To specify the length of time between hello packets for the specified interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis hello-interval seconds {level-1 |
level-2}
| Specify the length of time, in seconds, between hello packets the Cisco IOS software sends on the specified interface. |
The hello interval can be configured independently for Level 1 and Level 2, except on serial
point-to-point interfaces. (Because there is only a single type of hello packet sent on serial links, it is independent of Level 1 or Level 2.) Specify an optional level for X.25, Switched Multimegabit Data Service (SMDS), and Frame Relay multiaccess networks. X25, SMDS, ATM, and Frame Relay networks should be configured with point-to-point subinterfaces.
Complete sequence number PDUs (CSNPs) are sent by the designated router to maintain database synchronization. You can configure the IS-IS CSNP interval for the interface.
To configure the CSNP interval for the specified interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis csnp-interval seconds {level-1 |
level-2}
| Configure the IS-IS CSNP interval for the specified interface. |
This feature does not apply to serial point-to-point interfaces. It applies to WAN connections if the WAN is viewed as a multiaccess meshed network.
You can configure the number of seconds between retransmission of IS-IS link-state packets (LSPs) for point-to-point links. To set the retransmission level, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis retransmit-interval seconds | Configure the number of seconds between retransmission of IS-IS LSPs for point-to-point links. |
The value you specify should be an integer greater than the expected round-trip delay between any two routers on the attached network. The setting of this parameter should be conservative, or needless retransmission will result. The value should be larger for serial lines.
To configure the delay between successive IS-IS LSP transmissions, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis lsp-interval milliseconds | Configure the delay between successive IS-IS LSP transmissions. |
You can configure the maximum rate at which IS-IS LSPs will be re-sent on point-to-point links, in terms of the number of milliseconds between packets. This configuration is different from the retransmission interval, which is the amount of time between successive retransmissions of the same LSP.
The retransmission throttle interval is typically not necessary, except in cases of very large networks with high point-to-point neighbor counts. To set the retransmission throttle interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis retransmit-throttle-interval milliseconds | Configure the IS-IS LSP retransmission throttle interval. |
To specify the number of IS-IS hello packets a neighbor must miss before the router should declare the adjacency as down, use the following command in interface configuration command. The default value is 3.
| Command | Purpose |
|---|---|
isis hello-multiplier multiplier {level-1 | level-2} | Set the hello multiplier. |
You can configure the priority to use for designated router election. Priorities can be configured for Level1 and Level 2 individually.
To specify the designated router election, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis priority value {level-1 |
level-2}
| Configure the priority to use for designated router election. |
You can specify adjacency levels on a specified interface. This parameter is also referred to as the interface circuit type.
To specify the interface circuit type, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis circuit-type {level-1 | level-1-2 |
level-2-only}
| Configure the type of adjacency desired for neighbors on the specified interface (the interface circuit type). |
You can assign different passwords for different routing levels. Specifying Level 1 or Level 2 configures the password for only Level 1 or Level 2 routing, respectively. If you do not specify a level, the default is Level 1. By default, authentication is disabled.
To configure a password for the specified level, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
isis password password {level-1 |
level-2}
| Configure the authentication password for a specified interface. |
Limiting LSP flooding is important to IS-IS networks in general, and is not limited to configuring multiarea IS-IS networks. In a network with a high degree of redundancy, such as a fully meshed set of point-to-point links over a nonbroadcast multiaccess (NBMA) transport, flooding of LSPs can limit network scalability. You can reduce LSP flooding in two ways:
You can completely block flooding (full blocking) on specific interfaces, so that new LSPs will not be flooded out over those interfaces. However, if flooding is blocked on a large number of links, and all remaining links go down, routers cannot synchronize their link-state databases even though there is connectivity to the rest of the network. When the link-state database is no longer updated, routing loops usually result.
To use CSNPs on selected point-to-point links to synchronize the link-state database, configure a CSNP interval using the isis csnp-interval command on selected point-to-point links over which normal flooding is blocked. You should use CSNPs for this purpose only as a last resort.
Configuring mesh groups (a set of interfaces on a router) can help to limit redundant flooding. All routers reachable over the interfaces in a particular mesh group are assumed to be densely connected (each router has many links to other routers), where many links can fail without isolating one or more routers from the network.
Normally, when a new LSP is received on an interface, it is flooded out over all other interfaces on the router. When the new LSP is received over an interface that is part of a mesh group, the new LSP will not be flooded out over the other interfaces that are part of that same mesh group.
Mesh groups rely on a full mesh of links between a group of routers. If one or more links in the full mesh goes down, the full mesh is broken, and some routers might miss new LSPs, even though there is connectivity to the rest of the network. When you configure mesh groups to optimize or limit LSP flooding, be sure to select alternative paths over which to flood in case interfaces in the mesh group go down.
To minimize the possibility of incomplete flooding, you should allow unrestricted flooding over at least a minimal set of links in the mesh. Selecting the smallest set of logical links that covers all physical paths results in very low flooding, but less robustness. Ideally you should select only enough links to ensure that LSP flooding is not detrimental to scaling performance, but enough links to ensure that under most failure scenarios no router will be logically disconnected from the rest of the network.
The following tasks differ from the preceding interface-specific IS-IS tasks because they configure IS-IS itself, rather than the interface.
You can configure optional IS-IS parameters as described in the following sections:
You can force a default route into an IS-IS routing domain. Whenever you specifically configure redistribution of routes into an IS-IS routing domain, the Cisco IOS software does not, by default, redistribute the default route into the IS-IS routing domain. You can use a route map to conditionally advertise the default route, depending on the existence of another route in the routing table of the router.
To generate a default route, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
default-information originate [route-map map-name] | Force a default route into the IS-IS routing domain. |
See also the discussion of redistribution of routes in the "Configuring IP Routing Protocol-Independent Features" chapter of this document.
You can configure the router to act as a Level 1 (intra-area) router, as both a Level1 router and a Level 2 (interarea) router, or as an interarea router only.
To specify router level support, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
is-type {level-1 | level-1-2 |
level-2-only}
| Configure the system type (area or backbone router). |
You can assign passwords to areas and domains.
The area authentication password is inserted in Level 1 (station router level) LSPs, CSNPs, and partial sequence number PDUs (PSNPs). The routing domain authentication password is inserted in Level2 (the area router level) LSPs, CSNPs, and PSNPs.
To configure either area or domain authentication passwords, use the following commands in router configuration mode:
| Command | Purpose |
|---|---|
area-password password | Configure the area authentication password. |
domain-password password | Configure the routing domain authentication password. |
You can create aggregate addresses that are represented in the routing table by a summary address. This process is called route summarization. One summary address can include multiple groups of addresses for a given level. Routes learned from other routing protocols also can be summarized. The metric used to advertise the summary is the smallest metric of all the more-specific routes.
To create a summary of addresses for a given level, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
summary-address address mask {level-1 | level-1-2 | level-2} | Create a summary of addresses for a given level. |
You can configure the router to set the overload bit (also known as the hippity bit) in its nonpseudonode LSPs. Normally the setting of the overload bit is allowed only when a router runs into problems. For example, when a router is experiencing a memory shortage, it might be that the link-state database is not complete, resulting in an incomplete or inaccurate routing table. By setting the overload bit in its LSPs, other routers can ignore the unreliable router in their shortest path first (SPF) calculations until the router has recovered from its problems.
The result will be that no paths through this router are seen by other routers in the IS-IS area. However, IP and CLNS prefixes directly connected to this router will be still be reachable.
This command can be useful when you want to connect a router to an IS-IS network, but do not want real traffic flowing through it under any circumstances. Examples are:
To set the overload bit, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
set-overload-bit | Set the overload bit. |
You can change the routing level configured for an area using the is-type command. If the router instance has been configured for Level1-2 area (the default for the first instance of the IS-IS routing process in a Cisco router), you can remove Level2 (interarea) routing for the area using the is-type command and change the routing level to Level1 (intra-area). You can also configure Level2 routing for an area using the is-type command, but the instance of the IS-IS router configured for Level2 on the Cisco router must be the only instance configured for Level2.
To change the routing level for an IS-IS routing process in a given area, use the following command in router configuration mode:
| Command | Purpose |
|---|---|
Router (config)#is-type {level-1 | level-1-2 |
level-2-only}
| Configures the routing level for an instance of the IS-IS routing process. |
To customize display output when the IS-IS multiarea feature is used, making the display easier to read, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
Router#isis display delimiter [return cnt | char cnt] | Specifies the delimiter to be used to separate displays of information about individual IS-IS areas. |
For example, the following command causes information about individual areas to be separated by 14dashes (-) in the display:
isis display delimiter - 14
The output for a configuration with two Level1 areas and one Level2 area configured is as follows:
dtp-5#show clns neighbors -------------- Area L2BB: System Id Interface SNPA State Holdtime Type Protocol 0000.0000.0009 Tu529 172.21.39.9 Up 25 L1L2 IS-IS -------------- Area A3253-01: System Id Interface SNPA State Holdtime Type Protocol 0000.0000.0053 Et1 0060.3e58.ccdb Up 22 L1 IS-IS 0000.0000.0003 Et1 0000.0c03.6944 Up 20 L1 IS-IS -------------- Area A3253-02: System Id Interface SNPA State Holdtime Type Protocol 0000.0000.0002 Et2 0000.0c03.6bc5 Up 27 L1 IS-IS 0000.0000.0053 Et2 0060.3e58.ccde Up 24 L1 IS-IS
To monitor the IS-IS tables and databases, use the following commands in EXEC mode:
| Command | Purpose |
|---|---|
show isis database [level-1] [level-2] [l1] [l2] [detail] [lspid] | Display the IS-IS link-state database. |
show isis area-tag routes | Display the IS-IS Level 1 routing table. |
show isis spf-log | Display how often and why the router has run a full SPF calculation. |
show isis area-tag topology | Display a list of all connected routers in all areas. |
The following example shows how to configure three routers to run IS-IS as an IP routing protocol. Figure 30 illustrates the example configuration.
Router A
router isis net 49.0001.0000.0000.000a.00 interface ethernet 0 ip router isis interface serial 0 ip router isis
Router B
router isis net 49.0001.0000.0000.000b.00 interface ethernet 0 ip router isis interface ethernet 1 ip router isis interface serial 0 ip router isis
Router C
router isis net 49.0001.0000.0000.000c.00 interface ethernet 1 ip router isis interface ethernet 2 ip router isis
The following example shows a mulitarea IS-IS configuration with two Level1 areas and one Level1-2 area. Figure 31 illustrates this configuration.
clns routing ... interface Tunnel529 ip address 10.0.0.5 255.255.255.0 ip router isis BB clns router isis BB interface Ethernet1 ip address 10.1.1.5 255.255.255.0 ip router isis A3253-01 clns router isis A3253-01 ! interface Ethernet2 ip address 10.2.2.5 255.255.255.0 ip router isis A3253-02 clns router isis A3253-02 ... router isis BB ! Defaults to "is-type level-1-2" net 49.2222.0000.0000.0005.00 ! router isis A3253-01 net 49.0553.0001.0000.0000.0005.00 is-type level-1 ! router isis A3253-02 net 49.0553.0002.0000.0000.0005.00 is-type level-1
Posted: Wed Jul 26 18:35:36 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.