-
Cisco IOS XR Routing Command Reference, Release 3.4
-
Preface
-
BGP Commands on Cisco IOS XR Software
-
EIGRP Commands on Cisco IOS XR Software
-
IS-IS Commands on Cisco IOS XR Software
-
OSPF Commands on Cisco IOS XR Software
-
OSPFv3 Commands on Cisco IOS XR Software
-
RIB Commands on Cisco IOS XR Software
-
RIP Commands on Cisco IOS XR Software
-
Routing Policy Language Commands on Cisco IOS XR Software
-
Static Routing Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
IS-IS Commands on Cisco IOS XR Software
default-information originate (IS-IS)
maximum-redistributed-prefixes (IS-IS)
mpls traffic-eng multicast-intact (IS-IS)
mpls traffic-eng router-id (IS-IS)
show isis checkpoint adjacency
show isis checkpoint interface
show isis mpls traffic-eng adjacency-log
show isis mpls traffic-eng advertisements
show isis mpls traffic-eng tunnel
IS-IS Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor the Intermediate System-to-Intermediate System (IS-IS) protocol.
For detailed information about IS-IS concepts, configuration tasks, and examples, see Implementing IS-IS on Cisco IOS XR Software configuration guide.
address-family (IS-IS)
To enter address family configuration mode for configuring Intermediate System-to-Intermediate System (IS-IS) routing that use standard IP Version 4 (IPv4) and IP Version 6 (IPv6) address prefixes, use the address-family command in router configuration or interface configuration mode. To disable support for an address family, use the no form of this command.
address-family {ipv4 | ipv6} {unicast | mulitcast}
no address-family {ipv4 | ipv6} {unicast | multicast}
Syntax Description
ipv4
Specifies IPv4 address prefixes.
ipv6
Specifies IPv6 address prefixes.
unicast
Specifies unicast address prefixes.
multicast
Specifies multicast address prefixes.
Defaults
An address family is not specified. The default subaddress family (SAFI) is unicast.
Command Modes
Router configuration
Interface configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the address family command to place the router or interface in address family configuration mode. In router address family configuration mode, you can configure routing that uses standard IPv4 or IPv6 address prefixes. An address family must be specified in interface configuration mode. In interface address family configuration mode, you can alter interface parameters for IPv4 or IPv6.
An address family must be specified to configure parameters that pertain to a single address family.
Task ID
Examples
The following example shows how to configure the IS-IS router process with IPv6 unicast address prefixes:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface gigabitEthernet 0/1/0/0RP/0/RP0/CPU0:router(config-isis-if)# address-family ipv6 unicastRP/0/RP0/CPU0:router(config-isis-if-af)#adjacency-check disable
To suppress Intermediate System-to-Intermediate System (IS-IS) IP Version 4 (IPv4) or IP Version 6 (IPv6) protocol-support consistency checks performed on hello packets, use the adjacency-check disable command in address family configuration mode. To remove this function, use the no form of this command.
adjacency-check disable
no adjacency-check disable
Syntax Description
This command has no arguments or keywords.
Defaults
Adjacency check is enabled in both address families.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
IS-IS performs consistency checks on hello packets and forms an adjacency only with a neighboring router that supports the same set of protocols. A router running IS-IS for both IPv4 and IPv6 does not form an adjacency with a router running IS-IS for IPv4 only.
Use the adjacency-check disable command to suppress the consistency checks for IPv6 IS-IS and allow an IPv4 IS-IS router to form an adjacency with a router running IPv4 IS-IS and IPv6. IS-IS never forms an adjacency between a router running IPv4 IS-IS only and a router running IPv6 only.
In addition, the adjacency-check disable command suppresses the IPv4 or IPv6 subnet consistency check and allows IS-IS to form an adjacency with other routers regardless of whether they have an IPv4 or IPv6 subnet in common.
Task ID
Examples
The following example shows how the network administrator introduces IPv6 into an existing IPv4 IS-IS network and ensures that the checking of hello packet checks from adjacent neighbors is disabled until all neighbor routers are configured to use IPv6:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv6RP/0/RP0/CPU0:router(config-isis-af)# adjacency-check disablecircuit-type
To configure the type of adjacency used for the Intermediate System-to-Intermediate System (IS-IS) protocol, use the circuit-type command in interface configuration mode. To reset the circuit type to Level l and Level 2, use the no form of this command.
circuit-type {level-1 | level-1-2 | level-2-only}
no circuit-type
Syntax Description
Defaults
Default adjacency types are both Level 1 and Level 2 adjacencies.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Adjacencies may not be established even if allowed by the circuit-type command. The proper way to establish adjacencies is to configure a router as a Level 1, Level 1 and Level 2, or Level 2-only system using the is-type command. Only on networking devices that are between areas (Level 1 and Level 2 networking devices) should you configure some interfaces to be Level 2-only to prevent wasting bandwidth by sending out unused Level 1 hello packets. Remember that on point-to-point interfaces, the Level 1 and Level 2 hello packets are in the same packet.
Task ID
Examples
The following example shows how to configure a Level 1 adjacency with its neighbor on Packet-over-SONET/SDH (POS) interface 0/2/0/0 and Level 2 adjacencies with all Level 2-capable routers on POS interface 0/5/0/2:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# is-type level-1-2RP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/0RP/0/RP0/CPU0:router(config-isis-if)# circuit-type level-1RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/5/0/2RP/0/RP0/CPU0:router(config-isis-if)# circuit-type level-2-onlyIn this example, only Level 2 adjacencies are established because the is-type command is configured:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# is-type level-2-onlyRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/0RP/0/RP0/CPU0:router(config-isis-if)# circuit-type level-1-2Related Commands
Configures the routing level for an instance of the IS-IS routing process.
Configures an IS-IS NET for the routing process.
clear isis process
To clear the link-state packet (LSP) database and adjacency database sessions for an Intermediate System-to-Intermediate System (IS-IS) instance or all IS-IS instances, use the clear isis process command in EXEC mode.
clear isis [instance instance-id] process
Syntax Description
instance instance-id
(Optional) Specifies IS-IS sessions for the specified IS-IS instance only.
•
The instance-id argument is the instance identifier (alphanumeric) defined by the router isis command.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear isis process command without any keyword to clear all the IS-IS instances. Add the instance instance-id keyword and argument to clear the specified IS-IS instance.
Task ID
Examples
The following example shows the IS-IS LSP database and adjacency sessions being cleared for instance 1:
RP/0/RP0/CPU0:router# clear isis instance 1 processRelated Commands
Displays the IS-IS link-state database.
Displays information about IS-IS neighbors.
clear isis route
To clear the Intermediate System-to-Intermediate System (IS-IS) routes in a topology, use the clear isis route command in EXEC mode.
clear isis [instance instance-id] {afi-all | ipv4 | ipv6} {unicast | multicast | safi-all} route
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear isis route command to clear the routes from the specified topology or all routes in all topologies if no topology is specified.
Task ID
Examples
The following example shows how to clear the routes with IPv4 unicast address prefixes:
RP/0/RP0/CPU0:router# clear isis ipv4 unicast routeRelated Commands
Displays the IS-IS link-state database.
Displays information about IS-IS neighbors.
clear isis statistics
To clear the Intermediate System-to-Intermediate System (IS-IS) statistics, use the clear isis statistics command in EXEC mode.
clear isis [instance instance-id] statistics [interface-type interface-instance]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear isis statistics command to clear the information displayed by the show isis statistics command.
Task ID
Examples
The following example shows the IS-IS statistics for a specified interface being cleared:
RP/0/RP0/CPU0:router# clear isis instance 23 statisticsRelated Commands
csnp-interval
To configure the interval at which periodic complete sequence number PDUs (CSNPs) packets are sent on broadcast interfaces, use the csnp-interval command in interface configuration mode. To restore the default value, use the no form of this command.
csnp-interval seconds [level {1 | 2}]
no csnp-interval [seconds] [level {1 |2}
Syntax Description
Defaults
seconds: 10 seconds
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The csnp-interval command applies only to the designated router (DR) for a specified interface. Only DRs send CSNP packets to maintain database synchronization. The CSNP interval can be configured independently for Level 1 and Level 2.
Use of the csnp-interval command on point-to-point subinterfaces makes sense only in combination with the IS-IS mesh-group feature.
Note
Task ID
Examples
The following example shows how to set the CSNP interval for Level 1 to 30 seconds:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/0/2/0RP/0/RP0/CPU0:router(config-isis-if)# csnp-interval 30 level 1default-information originate (IS-IS)
To generate a default route into an Intermediate System-to-Intermediate System (IS-IS) routing domain, use the default-information originate command in address family configuration mode. To remove the default-information originate command from the configuration file and restore the system to its default condition, use the no form of this command.
default-information originate [route-policy route-policy-name]
no default-information originate [route-policy route-policy-name]
Syntax Description
route-policy
(Optional) Defines the conditions for the default route.
route-policy-name
(Optional) Meaningful name for the route map.
Defaults
A default route is not generated into an IS-IS routing domain.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If a router configured with the default-information originate command has a route to 0.0.0.0 in the routing table, IS-IS originates an advertisement for 0.0.0.0 in its link-state packets (LSPs).
Without a route policy, the default is advertised only in Level 2 LSPs. For Level 1 routing, there is another process to find the default route, which is to look for the closest Level 1 and Level 2 router. The closest Level 1 and Level 2 router can be found by looking at the attached-bit (ATT) in Level 1 LSPs.
A route policy can be used for two purposes:
•
•
Task ID
Examples
The following example shows how to generate a default external route into an IS-IS domain:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# default-information originateRelated Commands
Redistributes routes from one IS-IS instance into another instance.
Displays the IS-IS link-state database.
disable (IS-IS)
To disable the Intermediate System-to-Intermediate System (IS-IS) protocol on a specified interface, use the disable command in interface address family configuration mode. To remove this function, use the no form of this command.
disable
no disable
Syntax Description
This command has no arguments or keywords.
Defaults
IS-IS protocol is enabled.
Command Modes
Interface address family configuration
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to disable the IS-IS protocol for IPv4 unicast on Packet-over-SONET/SDH (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/1/0/1RP/0/RP0/CPU0:router(config-isis-if)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-if-af)# disabledistance (IS-IS)
To define the administrative distance assigned to routes discovered by the Intermediate System-to-Intermediate System (IS-IS) protocol, use the distance command in address family configuration mode. To remove the distance command from the configuration file and restore the system to its default condition in which the software removes a distance definition, use the no form of this command.
distance weight [address/prefix-length [prefix-list-name]]
no distance [weight] [address/prefix-length [route-list-name]]
Syntax Description
Defaults
weight: 115
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
An administrative distance is an integer from 1 to 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means that the routing information source cannot be trusted at all and should be ignored. Weight values are subjective; no quantitative method exists for choosing weight values.
Use the distance command to configure the administrative distances applied to IS-IS routes when they are inserted into the Routing Information Base (RIB), and influence the likelihood of these routes being preferred over routes to the same destination addresses discovered by other protocols.
The address/prefix-length argument defines to which source router the distance applies. In other words, each IS-IS route is advertised by another router, and that router advertises an address that identifies it. This source address is displayed in the output of the show isis route detail command.
The distance command applies to the routes advertised by routers whose address matches the specified prefix. The prefix-list-name argument can then be used to refine this further so that the distance command affects only specific routes.
Task ID
Examples
The following example gives a distance of 10 to all routes to 2.0.0.0/8 and 3.0.0.0/8 (or more specific prefixes) that are advertised by routers whose ID is contained in 1.0.0.0/8. It gives a distance of 80 to all other routes.
RP/0/RP0/CPU0:router(config)# ipv4 prefix-list target_routesRP/0/RP0/CPU0:router(config-ipv4_pfx)# permit 2.0.0.0/8RP/0/RP0/CPU0:router(config-ipv4_pfx)# permit 3.0.0.0/8RP/0/RP0/CPU0:router(config-ipv4_pfx)# deny 0.0.0.0/0RP/0/RP0/CPU0:router(config-ipv4_pfx)# exitRP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# distance 10 1.0.0.0/8 target_routesRP/0/RP0/CPU0:router(config-isis-af)# distance 80Related Commands
Configures the IS-IS routing protocol and specifies an IS-IS instance.
Displays summary information about the IS-IS instance.
show isis route detail
Displays link-state packet (LSP) details.
hello-interval (IS-IS)
To specify the length of time between hello packets sent by the Intermediate System-to-Intermediate System (IS-IS) protocol software, use the hello-interval command in interface configuration mode. To restore the default value, use the no form of this command.
hello-interval seconds [level {1 | 2}]
no hello-interval [seconds] [level {1 | 2}]
Syntax Description
Defaults
seconds: 10 seconds
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The hello interval can be configured independently for Level 1 and Level 2, except on serial point-to-point interfaces. (Because only a single type of hello packet is sent on serial links, it is independent of Level 1 or Level 2.) Configuring Level 1 and Level 2 independently is used on Switched Multimegabit Data Service (SMDS) multiaccess networks or LAN interfaces.
Note
A slower hello interval saves bandwidth and CPU. Especially when used in combination with a higher hello multiplier, this strategy may increase overall network stability.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level keyword.
Task ID
Examples
The following example shows how to configure TenGigE interface 0/6/0/0 to advertise hello packets every 5 seconds for Level 1 topology routes. This situation causes more traffic than configuring a longer interval, but topological changes are detected more quickly.
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface TenGigE 0/6/0/0RP/0/RP0/CPU0:router(config-isis-if)# hello-interval 5 level 1Related Commands
Specifies the number of IS-IS hello packets a neighbor must miss before the router should declare the adjacency as down.
hello-multiplier
To specify the number of Intermediate System-to-Intermediate System (IS-IS) hello packets a neighbor must miss before the router should declare the adjacency as down, use the hello-multiplier command in interface configuration mode. To restore the default value, use the no form of this command.
hello-multiplier multiplier [level {1 | 2}]
no hello-multiplier [multiplier] [level {1 | 2}]
Syntax Description
Defaults
multiplier: 3
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The "holding time" carried in an IS-IS hello packet determines how long a neighbor waits for another hello packet before declaring the neighbor to be down. This time determines how quickly a failed link or neighbor is detected so that routes can be recalculated.
Use the hello-multiplier command in circumstances where hello packets are lost frequently and IS-IS adjacencies are failing unnecessarily. You can raise the hello multiplier and lower the hello interval (hello-interval (IS-IS) command) correspondingly to make the hello protocol more reliable without increasing the time required to detect a link failure.
On point-to-point links, there is only one hello for both Level 1 and Level 2. Separate Level 1 and Level 2 hello packets are also sent over nonbroadcast multiaccess (NBMA) networks in multipoint mode, such as X.25, Frame Relay, and ATM.
Task ID
Examples
The following example shows how the network administrator wants to increase network stability by making sure an adjacency goes down only when many (ten) hello packets are missed. The total time to detect link failure is 60 seconds. This strategy ensures that the network remains stable, even when the link is fully congested.
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# hello-interval 6RP/0/RP0/CPU0:router(config-isis-if)# hello-multiplier 10Related Commands
hello-padding
To configure padding on Intermediate System-to-Intermediate System (IS-IS) hello protocol data units (IIH PDUs) for all IS-IS interfaces on the router, use the hello-padding command in interface configuration mode. To suppress padding, use the no form of this command.
hello-padding {disable | sometimes} [level {1 | 2}]
no hello-padding [disable | sometimes] [level {1 | 2}
Syntax Description
disable
Suppresses hello padding.
sometimes
Enables hello padding during adjacency formation only.
level {1 | 2}
(Optional) Specifies hello padding for Level 1 or Level 2 independently.
Defaults
Hello padding is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You might want to suppress hello padding to conserve network resources. The lower the circuit speed, the higher the percentage of padding overhead. Before suppressing the hello padding, you should know your physical and data link layer configurations and have control over them, and also know your router configuration at the network layer.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level keyword.
Task ID
Examples
The following example shows how to suppress IS-IS hello padding over local area network (LAN) circuits for interface POS 0/2/0/1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# hello-padding disableRelated Commands
hello-password
To configure the authentication password for an Intermediate System-to-Intermediate System (IS-IS) interface, use the hello-password command in interface configuration mode. To disable authentication, use the no form of this command.
hello-password [hmac-md5 | text] [clear | encrypted] password [level {1 | 2}] [send-only]
no hello-password [hmac-md5 | text] [clear | encrypted] password [level {1 | 2}] [send-only]
Syntax Description
Defaults
Both Level 1 and Level 2 are configured if no level is specified.
password: encrypted textCommand Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When a text password is configured, it is exchanged as clear text. Therefore, the hello-password command provides limited security.
When an hmac-md5 password is configured, the password is never sent over the network and is instead used to calculate a cryptographic checksum to ensure the integrity of the exchanged data.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level keyword.
Task ID
Examples
The following example shows how to configure a password with HMAC-MD5 authentication for hello packets running on Packet-over-SONET/SDH (POS) 0/2/0/3 interface:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/3RP/0/RP0/CPU0:router(config-isis-if)# hello-password hmac-md5 clear mypasswordRelated Commands
hello-password accept
To configure an additional authentication password for an Intermediate System-to-Intermediate System (IS-IS) interface, use the hello-password accept command in interface configuration mode. To disable authentication, use the no form of this command.
hello-password accept {clear | encrypted} password [level {1 | 2}]
no hello-password accept {clear | encrypted} password [level {1 | 2}]
Syntax Description
Defaults
Both Level 1 and Level 2 are configured if no level is specified.
Command Modes
Interface configuration
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the hello-password accept command to add an additional password for an IS-IS interface. An authentication password must be configured using the hello-password command before an accept password can be configured for the corresponding level.
Task ID
Examples
The following example shows how to configure a password:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/3RP/0/RP0/CPU0:router(config-isis)# hello-password accept encrypted 111D1C1603Related Commands
hostname dynamic disable
To disable Intermediate System-to-Intermediate System (IS-IS) routing protocol dynamic hostname mapping, use the hostname dynamic command in router configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.
hostname dynamic disable
no hostname dynamic disable
Syntax Description
Defaults
Router names are dynamically mapped to system IDs.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
In an IS-IS routing domain, each router is represented by a 6-byte hexadecimal system ID. When network administrators maintain and troubleshoot networking devices, they must know the router name and corresponding system ID.
Link-state packets (LSPs) include the dynamic hostname the type, length, and value (TLV) which carry the mapping information across the entire domain. Every router in the network, upon receiving the TLV from an LSP, tries to install it in a mapping table. The router then uses the mapping table when it wants to convert a system ID to a router name.
To display the entries in the mapping tables, use the show isis hostname command.
Task ID
Examples
The following example shows how to disable dynamic mapping of hostnames to system IDs:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# hostname dynamic disableRelated Commands
hostname
Specifies the name of the local router.
Displays the router name-to-system ID mapping table.
ignore-lsp-errors
To override the default setting of a router to ignore Intermediate System-to-Intermediate System (IS-IS) link-state packets (LSPs) that are received with internal checksum errors, use the ignore-lsp-errors disable command in router configuration mode. To enable ignoring IS-IS LSP errors, use the no form of this command.
ignore-lsp-errors disable
no ignore-lsp-errors disable
Syntax Description
Defaults
The system purges corrupt LSPs that cause the initiator to regenerate LSPs.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The IS-IS protocol definition requires that a received LSP with an incorrect data-link checksum be purged by the receiver, which causes the initiator of the packet to regenerate it. However, if a network has a link that causes data corruption while still delivering LSPs with correct data-link checksums, a continuous cycle of purging and regenerating large numbers of packets can occur. Because this situation could render the network nonfunctional, use this command to ignore these LSPs rather than purge the packets.
The receiving network devices use link-state packets to maintain their routing tables.
Task ID
Examples
The following example shows how to instruct the router to ignore LSPs that have internal checksum errors:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# ignore-lsp-errors disableinterface (IS-IS)
To configure the Intermediate System-to-Intermediate System (IS-IS) protocol on an interface, use the interface command in router configuration mode. To disable IS-IS routing for interfaces, use the no form of this command.
interface type instance
no interface type instance
Syntax Description
Defaults
No interfaces are specified.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
An address family must be established on the IS-IS interface before the interface is enabled for IS-IS protocol operation.
Task ID
Examples
The following example shows how to enable an IS-IS multitopology configuration for IPv6 on Packet-over-SONET/SDH (POS) interface 0/3/0/0:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# net 49.0000.0000.0001.00RP/0/RP0/CPU0:router(config-isis)# interface POS0/3/0/0RP/0/RP0/CPU0:router(config-isis-if)# address-family ipv6 unicastRP/0/RP0/CPU0:router(config-isis-if-af)# metric-style wide level 1!RP/0/RP0/CPU0:router(config)# interface POS0/3/0/0RP/0/RP0/CPU0:router(config-if)# ipv6 address 2001::1/64Related Commands
ispf
To configure the incremental shortest path first (iSPF) algorithm to calculate network topology, use the ispf command in address family configuration mode. To disable this algorithm function, use the no form of this command.
ispf [level {1 | 2}]
no ispf [level {1 | 2}]
Syntax Description
Defaults
The iSPF algorithm is not configured.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The iSPF algorithm may be used to reduce the processor load when IS-IS needs to recalculate its topology after minor changes.
Task ID
Examples
The following example shows how to configure iSPF for the IPv4 unicast topology at Level 1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# ispf level 1is-type
To configure the routing level for an Intermediate System-to-Intermediate System (IS-IS) area, use the is-type command in router configuration mode. To set the routing level to the default level, use the no form of this command.
is-type {level-1 | level-1-2 | level-2-only}
no is-type [level-1 | level-1-2 | level-2-only]
Syntax Description
Defaults
Both Level 1 and Level 2 are configured if no level is specified.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When the router is configured with Level 1 routing only, this router learns about destinations only inside its area. Level 2 (interarea) routing is performed by the closest Level 1-2 router.
When the router is configured with Level 2 routing only, this router is part of the backbone, and does not communicate with Level 1 routers in its own area.
The router has one link-state packet database (LSDB) for destinations inside the area (Level 1 routing) and runs a shortest path first (SPF) calculation to discover the area topology. It also has another LSDB with link-state packets (LSPs) of all other backbone (Level 2) routers, and runs another SPF calculation to discover the topology of the backbone and the existence of all other areas.
We highly recommend that you configure the type of an IS-IS routing process to establish the proper level of adjacencies. If there is only one area in the network, there is no need to run both Level 1 and Level 2 routing algorithms.
Task ID
Examples
The following example shows how to specify that the router is part of the backbone and that it does not communicate with Level 1-only routers:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# is-type level-2-onlyRelated Commands
log adjacency changes (IS-IS)
To cause an IS-IS instance to generate a log message when an Intermediate System-to-Intermediate System (IS-IS) adjacency changes state (up or down), use the log adjacency changes command in router configuration mode. To restore the default value, use the no form of this command.
log adjacency changes
no log adjacency changes
Syntax Description
This command has no arguments or keywords.
Defaults
No log messages are generated.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the log adjacency changes command to monitor IS-IS adjacency state changes; it may be very useful when monitoring large networks. Messages are logged using the system error message facility. Messages are of the forms:
%ISIS-4-ADJCHANGE: Adjacency to 0001.0000.0008 (POS0/2/1/0) (L2) Up, new adjacency%ISIS-4-ADJCHANGE: Adjacency to router-gsr8 (POS0/2/1/0) (L1) Down, Holdtime expiredUsing the no form of the command removes the specified command from the configuration file and restores the system to its default condition with respect to the command.
Task ID
Examples
The following example shows how to configure the router to log adjacency changes:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# log adjacency changesRelated Commands
log pdu drops
To log Intermediate System-to-Intermediate System (IS-IS) protocol data units (PDUs) that are dropped, use the log pdu drops command in router configuration mode. To disable this function, use the no form of this command.
log pdu drops
no log pdu drops
Syntax Description
This command has no arguments or keywords.
Defaults
PDU logging is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the log pdu drops command to monitor a network when IS-IS PDUs are suspected of being dropped. The reason for the PDU being dropped and current PDU drop statistics are recorded.
The following are examples of PDU messages:
%ISIS-4-ERR_IIH_INPUT_Q_OVERFLOW: IIH input queue overflow: 86 total drops; 19 IIH drops, 44 LSP drops, 23 SNP drops%ISIS-4-ERR_LSP_INPUT_Q_OVERFLOW: LSP input queue overflow: 17 total drops; 9 IIH drops, 3 LSP drops, 5 SNP dropsTask ID
Examples
The following example shows how to enable PDU logging:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# log pdu dropslsp fast-flood threshold
To configure the link-state packet (LSP) threshold, use the lsp fast-flood threshold command in interface configuration mode. To restore the default value, use the no form of this command.
lsp fast-flood threshold lsp-number [level {1 | 2}]
no lsp fast-flood threshold [lsp-number] [level {1 | 2}]
Syntax Description
lsp-number
Number of LSPs to send back to back. Range is 1 to 4294967295.
level {1 | 2}
(Optional) Specifies the LSP threshold for Level 1 or Level 2 independently.
Defaults
10 LSPs are allowed in a back-to-back window
Command Modes
Interface configuration
Command History
Release 3.4.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the lsp fast-flood threshold command to accelerate convergence of LSP database. LSPs are sent back-to-back over an interface up to the specified limit. Past the limit, LSPs are sent out in the next batch window as determined by LSP pacing interval.
Duration of back-to-back window = LSP interval * LSP fast-flood threshold limit
Task ID
Examples
The following example shows how to configure the LSP threshold:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS 0/3/0/0RP/0/RP0/CPU0:router(config-isis-if)# lsp fast-flood threshold 234 level 1Related Commands
lsp-gen-interval
To customize IS-IS throttling of link-state packet (LSP) generation, use the lsp-gen-interval command in router configuration mode. To restore the default value, use the no form of this command.
lsp-gen-interval {[initial-wait initial] [secondary-wait secondary] [maximum-wait maximum]} [level {1 | 2}]
no lsp-gen-interval [[initial-wait initial] [secondary-wait secondary] [maximum-wait maximum]] [level {1 | 2}]
Syntax Description
Defaults
initial-wait initial: 50 milliseconds
secondary-wait secondary: 200 milliseconds
maximum-wait maximum: 5000 millisecondsCommand Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
During prolonged periods of network instability, repeated recalculation of LSPs can cause increased CPU load on the local router. Further, the flooding of these recalculated LSPs to the other Intermediate Systems in the network causes increased traffic and can result in other routers having to spend more time running route calculations.
Use the lsp-gen-interval command to reduce the rate of LSP generation during periods of instability in the network. This command can help to reduce CPU load on the router and to reduce the number of LSP transmissions to its IS-IS neighbors.
Task ID
Examples
The following example shows how to set the maximum interval between two consecutive occurrences of an LSP to 15 milliseconds and the initial LSP generation delta to 5 milliseconds:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# lsp-gen-interval maximum-wait 15 initial-wait 5Related Commands
Configures the amount of time between retransmission of each IS-IS LSP on a point-to-point link.
lsp-interval
To configure the amount of time between each link-state packet (LSP) sent on an Intermediate System-to-Intermediate System (IS-IS) interface, use the lsp-interval command in interface configuration mode. To restore the default value, use the no form of this command.
lsp-interval milliseconds [level {1 | 2}]
no lsp-interval [milliseconds] [level {1 | 2}]
Syntax Description
milliseconds
Time delay (in milliseconds) between successive LSPs. Range is 1 to 4294967295.
level {1 | 2}
(Optional) Configures the LSP time delay for Level 1 or Level 2 independently.
Defaults
milliseconds: 33 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to cause the system to send LSPs every 100 milliseconds (10 packets per second) on Level 1 and Level 2:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# lsp-interval 100Related Commands
Configures the amount of time between retransmission of each IS-IS LSP on a point-to-point link.
lsp-mtu
To set the maximum transmission unit (MTU) size of Intermediate System-to-Intermediate System (IS-IS) link-state packets (LSPs), use the lsp-mtu command in router configuration mode. To restore the default, use the no form of this command.
lsp-mtu bytes [level {1 | 2}]
no lsp-mtu [bytes] [level {1 | 2}]
Syntax Description
RP/0/0/CPU0:P1#show isis interface briefIS-IS lab InterfacesInterface All Adjs Adj Topos Adv Topos CLNS MTU PrioOK L1 L2 Run/Cfg Run/Cfg L1 L2----------------- --- --------- --------- --------- ---- ---- --------PO0/3/0/1 Yes 1 0 1/1 1/1 Up 4469 - -PO0/3/0/3 Yes 1 0 1/1 1/1 Up 4469 - -PO0/3/0/4 Yes 1 0 1/1 1/1 Up 4469 - -PO0/3/0/5 Yes 1 0 1/1 1/1 Up 4469 - -PO0/3/0/6 Yes 1 0 1/1 1/1 Up 4469 - -PO0/3/0/7 Yes 1 0 1/1 1/1 Up 4469 - -Defaults
bytes: 1492 bytes
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Under normal conditions, the default MTU size should be sufficient. However, if the MTU size of a link is less than 1500 bytes, the LSP MTU size must be lowered accordingly on each router in the network. If this action is not taken, routing becomes unpredictable.
This guideline applies to all Cisco networking devices in a network. If any link in the network has a reduced MTU size, all devices must be changed, not just the devices directly connected to the link.
Note
To be certain about a link MTU size, use the show isis interface command to display the value.
Task ID
Examples
The following example shows how to set the MTU size to 1300 bytes:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# lsp-mtu 1300Related Commands
mtu
Adjusts the maximum packet size or MTU size.
Displays information about the IS-IS interface.
lsp-password
To configure the link-state packet (LSP) authentication password, use the lsp-password command in router configuration mode. To remove the lsp-password command from the configuration file and disable link-state packet authentication, use the no form of this command.
lsp-password {hmac-md5 | text} {clear | encrypted} password [level {1 | 2}] [send-only] [snp send-only]
no lsp-password [{hmac-md5 | text} {clear | encrypted} password [level {1 | 2}] [send-only] [snp send-only]]
Syntax Description
Defaults
Both Level 1 and Level 2 are configured if no level is specified.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When a text password is configured, it is exchanged as clear text. Therefore, the lsp-password command provides limited security.
When an HMAC-MD5 password is configured, the password is never sent over the network and is instead used to calculate a cryptographic checksum to ensure the integrity of the exchanged data.
The recommended password configuration is that both incoming and outgoing SNPs be authenticated.
Note
To configure an additional password, use the lsp-password accept command.
Task ID
Examples
The following example shows how to configure separate Level 1 and Level 2 LSP and SNP passwords, one with HMAC-MD5 authentication and encryption and one with clear text password authentication and no encryption:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# lsp-password hmac-md5 clear password1 level 1RP/0/RP0/CPU0:router(config-isis)# lsp-password text clear password2 level 2Related Commands
Configures an additional LSP password when one LSP password is already configured for a level.
lsp-password accept
To configure an additional link-state packet (LSP) authentication password, use the lsp-password accept command in router configuration mode. To remove the lsp-password accept command from the configuration file and restore the system to its default condition, use the no form of this command.
lsp-password accept {clear | encrypted} password [level {1 | 2}]
no lsp-password accept [{clear | encrypted} password [level {1 | 2}]]
Syntax Description
Defaults
Both Level 1 and Level 2 are configured if no level is specified.
Command Modes
Router configuration
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The lsp-password accept command adds an additional password for use when validating incoming LSPs and sequence number PDUs (SNPs). An LSP password must be configured using the lsp-password command before an accept password can be configured for the corresponding level.
Task ID
Examples
The following example shows how to configure an accept Level 1 LSP and SNP password:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# lsp-password accept encrypted password1 level 1Related Commands
lsp-refresh-interval
To set the time between regeneration of link-state packets (LSPs) that contain different sequence numbers, use the lsp-refresh-interval command in router configuration mode. To restore the default refresh interval, use the no form of this command.
lsp-refresh-interval seconds [level {1 | 2}]
no lsp-refresh-interval [seconds [level {1 | 2}]]
Syntax Description
seconds
Refresh interval (in seconds). Range is 1 to 65535 seconds.
level {1 | 2}
(Optional) Specifies routing Level 1 or Level 2 independently.
Defaults
seconds: 900 seconds (15 minutes)
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The refresh interval determines the rate at which the software periodically sends the route topology information that it originates. This behavior is done to keep the information from becoming too old. By default, the refresh interval is 7200 seconds (2 hours).
LSPs must be refreshed periodically before their lifetimes expire. The refresh interval must be less than the LSP lifetime specified with this router command. Reducing the refresh interval reduces the amount of time that undetected link-state database corruption can persist at the cost of increased link utilization. (This event is extremely unlikely, however, because there are other safeguards against corruption.) Increasing the interval reduces the link utilization caused by the flooding of refreshed packets (although this utilization is very small).
Task ID
Examples
The following example shows how to change the LSP refresh interval to 10,800 seconds (3 hours):
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# lsp-refresh-interval 10800Related Commands
maximum-paths (IS-IS)
To configure the maximum number of parallel routes that an IP routing protocol will install into the routing table, use the maximum-paths command in address family configuration mode. To remove the maximum-paths command from the configuration file and restore the system to its default condition with respect to the routing protocol, use the no form of this command.
maximum-paths maximum
no maximum-paths
Syntax Description
maximum
Maximum number of parallel routes that IS-IS can install in a routing table. Range is 1 to 32 for Cisco CRS-1s and 1 to 16 for Cisco XR 12000 Series Routers.
Defaults
maximum (Cisco CRS-1): 8 routes
maximum (Cisco XR 12000 Series Router): 8 routesCommand Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to allow a maximum of 16 paths to a destination:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# maximum-paths 16maximum-redistributed-prefixes (IS-IS)
To specify an upper limit on the number of external prefixes (subject to summarization) that the Intermediate System-to-Intermediate System (IS-IS) protocol advertises, use the maximum-redistributed-prefixes command in address family mode. To disable this feature, use the no form of this command.
maximum-redistributed-prefixes maximum [level {1 | 2}]
no maximum-redistributed-prefixes [maximum [level {1 | 2}]]
Syntax Description
maximum
Maximum number of redistributed prefixes advertised. Range is 1 to 28000.
level {1 | 2}
(Optional) Specifies maximum prefixes for Level 1 or Level 2.
Defaults
maximum: 10000
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the maximum-redistributed-prefixes command to prevent a misconfiguration from resulting in redistribution of the Internet. If IS-IS encounters more than the maximum number of prefixes, it sets a bi-state alarm. If the number of to-be-redistributed prefixes drops back to the maximum or lower—either through reconfiguration or a change in the redistribution source—IS-IS clears the alarm.
Task ID
Examples
The following example shows how to specify the number of redistributed prefixes at 5000 for Level 2:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# maximum-redistributed-prefixes 5000 level 2max-lsp-lifetime
To set the maximum time that link-state packets (LSPs) persist without being refreshed, use the max-lsp-lifetime command in router configuration mode. To restore the default time, use the no form of this command.
max-lsp-lifetime seconds [level {1 | 2}]
no max-lsp-lifetime [seconds [level {1 | 2}]]
Syntax Description
seconds
Lifetime (in seconds) of the LSP. Range from 1 to 65535 seconds.
level {1 | 2}
(Optional) Specifies routing Level 1 or Level 2 independently.
Defaults
seconds: 1200 seconds (20 minutes)
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval command. The maximum LSP lifetime must be greater than the LSP refresh interval.
Task ID
Examples
The following example shows how to set the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# max-lsp-lifetime 11000Related Commands
mesh-group (IS-IS)
To optimize link-state packet (LSP) flooding in nonbroadcast multiaccess (NBMA) networks with highly meshed, point-to-point topologies, use the mesh-group command in interface configuration mode. To remove a subinterface from a mesh group, use the no form of this command.
mesh-group {number | blocked}
no mesh-group
Syntax Description
number
Number identifying the mesh group of which this interface is a member. Range is 1 to 4294967295.
blocked
Specifies that no LSP flooding takes place on this interface.
Defaults
There is no mesh group configuration (normal LSP flooding).
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
LSPs first received on subinterfaces that are not part of a mesh group are flooded to all other subinterfaces in the usual way.
LSPs first received on subinterfaces that are part of a mesh group are flooded to all interfaces except those in the same mesh group. If the blocked keyword is configured on a subinterface, then a newly received LSP is not flooded out over that interface.
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 is logically disconnected from the rest of the network. In other words, blocking flooding on all links permits the best scaling performance, but there is no flooding. Permitting flooding on all links results in very poor scaling performance.
Note
Task ID
Examples
In the following example, six interfaces are configured in three mesh groups. LSPs received are handled as follows:
•
•
•
•
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/1/0/0RP/0/RP0/CPU0:router(config-isis-if)# mesh-group 10RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/1/0/1RP/0/RP0/CPU0:router(config-isis-if)# mesh-group 10RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/0RP/0/RP0/CPU0:router(config-isis-if)# mesh-group 11RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# mesh-group 11RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/3/0/1RP/0/RP0/CPU0:router(config-isis-if)# mesh-group 12RP/0/RP0/CPU0:router(config-isis-if)# exitRP/0/RP0/CPU0:router(config-isis)# interface POS0/3/0/0RP/0/RP0/CPU0:router(config-isis-if)# mesh-group blockedmetric
To configure the metric for an Intermediate System-to-Intermediate System (IS-IS) interface, use the metric command in interface address family configuration mode. To restore the default metric value, use the no form of this command.
metric {default-metric | maximum} [level {1 | 2}]
no metric [{default-metric | maximum} [level {1 | 2}]]
Syntax Description
Defaults
default-metric: Default is 10.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Interface address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Specifying the level keyword resets the metric only for Level 1 or Level 2 routing, respectively.
We highly recommend that you configure metrics on all interfaces.
Metrics of more than 63 cannot be used with narrow metric style.
Task ID
Examples
The following example shows how to configure Packet-over-SONET/SDH 0/1/0/1 interface with a default link-state metric cost of 15 for Level 1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/1/0/1RP/0/RP0/CPU0:router(config-isis-if)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-if-af)# metric 15 level 1Related Commands
metric-style narrow
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept old-style type, length, and value (TLV) objects, use the metric-style narrow command in address family configuration mode. To remove the metric-style narrow command from the configuration file and restore the system to its default condition, use the no form of this command.
metric-style narrow [transition] [level {1 | 2}]
no metric-style narrow [transition] [level {1 | 2}]
Syntax Description
Defaults
Old-style TLVs are generated.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
IS-IS traffic engineering extensions include new-style TLV objects with wider metric fields than old-style TLV objects. By default, the router generates old-style TLV objects only. To perform Multiprotocol Label Switching traffic engineering (MPLS TE), a router must generate new-style TLV objects.
Task ID
Examples
The following example shows how to configure the router to generate and accept only old-style TLV objects on router Level 1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# metric-style narrow level 1Related Commands
Configures a router to generate and accept both old-style and new-style TLV objects.
Configures a router to generate and accept only new-style TLV objects.
metric-style transition
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept both old-style and new-style type, length, and value (TLV) objects, use the metric-style transition command in address family configuration mode. To remove the metric-style transition command from the configuration file and restore the system to its default condition, use the no form of this command.
metric-style transition [level {1 | 2}]
no metric-style transition [level {1 | 2}]
Syntax Description
transition
Instructs the router to generate and accept both old-style and new-style TLV objects.
level {1 | 2}
(Optional) Specifies routing Level 1 or Level 2 independently.
Defaults
New-style TLVs are not generated.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
IS-IS traffic engineering extensions include new-style TLV objects with wider metric fields than old-style TLV objects. By default, the router generates old-style TLV objects only. To perform Multiprotocol Label Switching traffic engineering (MPLS TE), a router needs to generate new-style TLV objects.
Task ID
Examples
The following example shows how to configure the router to generate and accept both old-style and new-style TLV objects on Level 2:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# metric-style transition level 2Related Commands
Configures a router to generate and accept only old-style TLV objects.
Configures a router to generate and accept only new-style TLV objects.
metric-style wide
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept only new-style type, length, and value (TLV) objects, use the metric-style wide command in address family configuration mode. To remove the metric-style wide command from the configuration file and restore the system to its default condition, use the no form of this command.
metric-style wide [transition] [level {1 | 2}]
no metric-style wide [transition] [level {1 | 2}]
Syntax Description
Defaults
Old-style TLV lengths are generated, if this command is not configured.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
IS-IS traffic engineering extensions include new-style TLV objects with wider metric fields than old-style TLV objects. If you enter the metric-style wide command, a router generates and accepts only new-style TLV objects. Therefore, the router uses less memory and fewer other resources rather than generating both old-style and new-style TLV objects.
To perform MPLS traffic engineering, a router needs to generate new-style TLV objects.
Note
Task ID
Examples
The following example shows how to configure a router to generate and accept only new-style TLV objects on Level 1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# metric-style wide level 1Related Commands
mpls ldp sync
To configure Label Distribution Protocol (LDP) IS-IS synchronization, use the mpls ldp sync command in interface address family configuration mode. To disable LDP synchronization, use the no form of this command.
mpls ldp sync [level {1 | 2}]
no mpls ldp sync [level {1 | 2}]
Syntax Description
Defaults
If a level is not specified, LDP synchronization is set for both levels.
Command Modes
Interface address family configuration
Command History
Release 3.3.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
MPLS VPN traffic forwarded using LDP labels may be dropped in the following instances:
•
•
In both instances, outbound LDP labels are not available for forwarding MPLS traffic. LDP IS-IS synchronization addresses the traffic drop. When the mpls ldp sync command is configured, IS-IS advertises the maximum possible link metric until LDP has converged over the link. The link is less preferred and least used in forwarding MPLS traffic. When LDP establishes the session and exchanges labels, IS-IS advertises the regular metric over the link.
Note
Task ID
Examples
The following example shows how to enable LDP IS-IS synchronization:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS 0/3/0/0RP/0/RP0/CPU0:router(config-isis-if)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-if-af)# mpls ldp syncRelated Commands
mpls traffic-eng
To configure a router running the Intermediate System-to-Intermediate System (IS-IS) protocol to flood Multiprotocol Label Switching traffic engineering (MPLS TE) link information into the indicated IS-IS level, use the mpls traffic-eng command in address family configuration mode. To disable this feature, use the no form of this command.
mpls traffic-eng {level-1 | level-1-2 | level-2-only}
no mpls traffic-eng [level-1 | level-1-2 | level-2-only]
Syntax Description
level-1
Specifies routing level 1.
level-1-2
Specifies routing levels 1 and 2.
level-2-only
Specifies routing level 2.
Defaults
Flooding is disabled.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the mpls traffic-eng command, which is part of the routing protocol tree, to flood link resource information (such as available bandwidth) for appropriately configured links in the link-state packet (LSP) of the router.
Task ID
Examples
The following example shows how to turn on MPLS traffic engineering for IS-IS level 1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng level-1Related Commands
Specifies that the traffic engineering router identifier for the node is the IP address associated with a given interface.
mpls traffic-eng multicast-intact (IS-IS)
To enable a router that is running the Intermediate System-to-Intermediate System (IS-IS) protocol so that Protocol-Independent Multicast (PIM) and Multiprotocol Label Switching (MPLS) traffic engineering operate, use the mpls traffic-eng multicast-intact command in address family configuration mode. To disable this feature, use the no form of this command.
mpls traffic-eng multicast-intact
no mpls traffic-eng [multicast-intact]
Syntax Description
This command has no arguments or keywords.
Defaults
Multicast-intact is disabled.
Command Modes
Address family configuration
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If Multiprotocol Label Switching Traffic Engineering (MPLS-TE) is configured through the IS-IS routing domain and multicast protocols (like Protocol Independent Multicast [PIM]) are also enabled, then use the mpls traffic-end multicast-intact command to install nontraffic engineering next hops in the Routing Information Base (RIB) for use by multicast. The installation of IP-only next hops is in addition to the installation of the standard set of paths for a prefix, which might be over traffic engineered tunnels.
The mpls traffic-eng multicast-intact command allows PIM to use the native hop-by-hop neighbors even though the unicast routing is using MPLS TE tunnels.
Examples
The following example shows how to enable the multicast-intact feature:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng multicast-intactRelated Commands
mpls traffic-eng router-id (IS-IS)
To specify the Multiprotocol Label Switching traffic engineering (MPLS TE) router identifier for the node, use the mpls traffic-eng router-id command in address family configuration mode. To disable this feature, use the no form of this command.
mpls traffic-eng router-id {ip-address | interface-type interface-instance}
no mpls traffic-eng [router-id]
Syntax Description
Defaults
Global router identifier is used.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The identifier of the router acts as a stable IP address for the traffic engineering configuration. This IP address is flooded to all nodes. For all traffic engineering tunnels originating at other nodes and ending at this node, you must set the tunnel destination to the traffic engineering router ID of the destination node, because that is the address used by the traffic engineering topology database at the tunnel head for its path calculation.
Note
Task ID
Examples
The following example shows how to specify the traffic engineering router identifier as the IP address associated with loopback interface 0:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng router-id Loopback0Related Commands
Turns on flooding of MPLS traffic engineering link information in the indicated IGP level or area.
net
To configure an Intermediate System-to-Intermediate System (IS-IS) network entity title (NET) for the routing process, use the net command in router configuration mode. To remove the net command from the configuration file and restore the system to its default condition, use the no form of this command.
net network-entity-title
no net network-entity-title
Syntax Description
network-entity-title
NET that specifies the area address and the system ID for an IS-IS routing process.
Defaults
No NET is configured. The IS-IS instance is not operational, because a NET is mandatory.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Under most circumstances, one and only one NET should be configured.
A NET is a network service access point (NSAP) where the last byte is always zero. On a Cisco router running IS-IS, a NET can be 8 to 20 bytes in length. The last byte is always the n-selector and must be zero. The n-selector indicates to which transport entity the packet is sent. An n-selector of zero indicates no transport entity and means that the packet is for the routing software of the system.
The six bytes directly preceding the n-selector are the system ID. The system ID length is a fixed size and cannot be changed. The system ID must be unique throughout each area (Level 1) and throughout the backbone (Level 2).
All bytes preceding the system ID are the area ID.
A maximum of three NETs for each router is allowed. In rare circumstances, it is possible to configure two or three NETs. In such a case, the area this router is in has three area addresses. Only one area still exists, but it has more area addresses.
Configuring multiple NETs can be temporarily useful in network reconfiguration in which multiple areas are merged, or in which one area is split into more areas. Multiple area addresses enable you to renumber an area individually as needed.
Task ID
Examples
The following example shows how to configure a router with NET area ID 47.0004.004d.0001 and system ID 0001.0c11.1110:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# net 47.0004.004d.0001.0001.0c11.1110.00Related Commands
Configures the routing level for an instance of the IS-IS routing process.
Enables the IS-IS routing protocol and specifies an IS-IS instance.
nsf (IS-IS)
To enable nonstop forwarding (NSF) on the next restart, use the nsf command in router configuration mode. To restore the default setting, use the no form of this command.
nsf {cisco | ietf}
no nsf {cisco | ietf}
Syntax Description
cisco
Specifies Cisco proprietary NSF restart.
ietf
Specifies Internet Engineering Task Force (IETF) NSF restart.
Defaults
NSF is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
NSF allows an Intermediate System-to-Intermediate System (IS-IS) instance to restart using checkpointed adjacency and link-state packet (LSP) information, and to perform restart with no impact on its neighbor routers. In other words, there is no impact on other routers in the network due to the destruction and recreation of adjacencies and the system LSP.
Task ID
Examples
The following example shows how to enable Cisco proprietary NSF:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# nsf ciscoRelated Commands
nsf interface-expires
To configure the number of resends of an acknowledged nonstop forwarding (NSF)-restart acknowledgment, use the nsf interface-expires command in router configuration mode. To restore the default value, use the no form of this command.
nsf interface-expires number
no nsf interface-expires
Syntax Description
Defaults
number: 3 resends
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When a hello packet sent with the NSF restart flag set is not acknowledged, it is re-sent. Use the nsf interface-expires command to control the number of times the NSF hello is re-sent. When this limit is reached on an interface, any neighbor previously known on that interface is assumed to be down and the initial shortest path first (SPF) calculation is permitted, provided that all other necessary conditions are met.
The total time period available for adjacency reestablishment (interface-timer * interface-expires) should be greater than the expected total NSF restart time.
The nsf interface-expires command applies only to Internet Engineering Task Force (IETF)-style NSF. It has no effect if Cisco proprietary NSF is configured.
Task ID
Examples
The following example shows how to allow only one retry attempt on each interface if an IETF NSF restart signal is not acknowledged:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# nsf ietfRP/0/RP0/CPU0:router(config-isis)# nsf interface-expires 1Related Commands
nsf interface-timer
To configure the time interval after which an unacknowledged Internet Engineering Task Force (IETF) nonstop forwarding (NSF) restart attempt is repeated, use the nsf interface-timer command in router configuration mode. To restore the default value, use the no form of this command.
nsf interface-timer seconds
no nsf interface-timer
Syntax Description
Defaults
seconds: 10 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When the IETF NSF restart process begins, hello packets send an NSF restart flag that must be acknowledged by the neighbors of the router. Use the nsf interface-timer command to control the restart time interval after the hello packet is re-sent. The restart time interval need not match the hello interval.
The nsf interface-timer command applies only to IETF-style NSF. It has no effect if Cisco proprietary NSF is configured.
Task ID
Examples
The following example shows how to ensure that a hello packet with the NSF restart flag set is sent again every 5 seconds until the flag is acknowledged:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# nsf ietfRP/0/RP0/CPU0:router(config-isis)# nsf interface-timer 5Related Commands
Configures the number of resends of an acknowledged NSF-restart acknowledgment.
Specifies the length of time between hello packets that the software sends.
nsf lifetime (IS-IS)
To configure the maximum route lifetime following a nonstop forwarding (NSF) restart, use the nsf lifetime command in router configuration mode. To restore the default value, use the no form of this command.
nsf lifetime seconds
no nsf lifetime
Syntax Description
Defaults
seconds: 60 seconds (1 minute)
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the nsf lifetime command to set the maximum available time for the reacquisition of checkpointed adjacencies and link-state packets (LSPs) during a Cisco proprietary NSF restart. LSPs and adjacencies not recovered during this time period are abandoned, thus causing changes to the network topology.
Task ID
Examples
The following example shows how to configure the router to allow only 20 seconds for the entire NSF process:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# nsf ciscoRP/0/RP0/CPU0:router(config-isis)# nsf lifetime 20passive (IS-IS)
To suppress Intermediate System-to-Intermediate System (IS-IS) packets from being transmitted to the interface and received packets from being processed on the interface, use the passive command in interface configuration mode. To restore IS-IS packets coming to an interface, use the no form of this command.
passive
no passive
Syntax Description
This command has no arguments or keywords.
Defaults
Interface is active.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure the router to suppress IS-IS packets on Packet-over-SONET/SDH (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/1/0/1RP/0/RP0/CPU0:router(config-isis-if)# passiveRelated Commands
Allows the IS-IS interface to participate in forming adjacencies without advertising connected prefixes in the LSPs.
point-to-point
To configure a network of only two networking devices that use broadcast media and the integrated Intermediate System-to-Intermediate System (IS-IS) routing protocol to function as a point-to-point link instead of a broadcast link, use the point-to-point command in interface configuration mode. To disable the point-to-point usage, use the no form of this command.
point-to-point
no point-to-point
Syntax Description
This command has no arguments or keywords.
Defaults
Interface is treated as broadcast if connected to broadcast media.
Command Modes
Interface configuration
Command History
Release 3.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.3.0
No modification.
Release 3.4.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the point-to-point command only on broadcast media in a network with two networking devices. The command causes the system to issue packets point-to-point rather than as broadcasts. Configure the command on both networking devices in the network.
Task ID
Examples
The following example shows how to configure a 10-Gb Ethernet interface to act as a point-to-point interface:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface TenGigE 0/6/0/0RP/0/RP0/CPU0:router(config-isis-if)# point-to-pointpriority (IS-IS)
To configure the priority of designated routers, use the priority command in interface configuration mode. To reset the default priority, use the no form of this command.
priority value [level {1 | 2}]
no priority [value] [level {1 | 2}]
Syntax Description
value
Priority of a router. Range is 0 to 127.
level {1 | 2}
(Optional) Specifies routing Level 1 or Level 2 independently.
Defaults
value: 64
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Priorities can be configured for Level 1 and Level 2 independently. Specifying Level 1 or Level 2 resets priority only for Level 1 or Level 2 routing, respectively. Specifying no level allows you to configure all levels.
The priority is used to determine which router on a LAN is the designated router or Designated Intermediate System (DIS). The priorities are advertised in the hello packets. The router with the highest priority becomes the DIS.
In the Intermediate System-to-Intermediate System (IS-IS) protocol, there is no backup designated router. Setting the priority to 0 lowers the chance of this system becoming the DIS, but does not prevent it. If a router with a higher priority comes online, it takes over the role from the current DIS. For equal priorities, the higher MAC address breaks the tie.
Task ID
Examples
The following example shows how to give Level 1 routing priority by setting the priority level to 80. This router is now more likely to become the DIS.
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface TenGigE0/6/0/0RP/0/RP0/CPU0:router(config-isis-if)# priority 80 level 1propagate level
To propagate routes from one Intermediate System-to-Intermediate System (IS-IS) level into another level, use the propagate level command in address family configuration mode. To disable propagation, use the no form of this command.
propagate level {1 | 2} into level {1 | 2} distribute-list access-list-name
no propagate level {1 | 2} into level {1 | 2}
Syntax Description
Defaults
Route leaking (Level 2 to Level 1) is disabled.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
In general, route propagation from Level 1 to Level 2 is automatic. You might want to use this command to better control which Level 1 routes can be propagated into Level 2.
Propagating Level 2 routes into Level 1 is called route leaking. Route leaking is disabled by default. That is, Level 2 routes are not automatically included in Level 1 link-state packets (LSPs). If you want to leak Level 2 routes into Level 1, you must enable that behavior by using this command.
Propagation from Level 1 into Level 1 and from Level 2 into Level 2 is not allowed.
Task ID
Examples
The following example shows how to redistribute Level 2 routes to Level 1:
RP/0/RP0/CPU0:router(config)# ipv4 access-list 101 permit ip 10.0.0.0 255.0.0.0 10.1.0.1 0.255.255.255RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# net 49.1234.2222.2222.2222.00RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# propagate level 2 into level 1 distribute-list 101Related Commands
redistribute (IS-IS)
To redistribute routes from one routing protocol into Intermediate System-to-Intermediate System (IS-IS), use the redistribute command in address family configuration mode. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
Border Gateway Protocol (BGP)
redistribute bgp process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
no redistribute bgp process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
Connected Routes
redistribute connected [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
no redistribute connected [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
Intermediate System-to-Intermediate System (IS-IS)
redistribute isis process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
no redistribute isis process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
Open Shortest Path First (OSPF)
redistribute ospf process-id [level-1 | level-2 | level-1-2] [match {external [1 | 2] | internal | nssa-external [1 | 2]}] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
no redistribute ospf process-id [level-1 | level-2 | level-1-2] [match {external [1 | 2] | internal | nssa-external [1 | 2]}][metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
Open Shortest Path First Version 3 (OSPFv3)
redistribute ospfv3 process-id [level-1 | level-2 | level-1-2] [match {external [1 | 2] | internal | nssa-external [1 | 2]}] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
no redistribute ospfv3 process-id [level-1 | level-2 | level-1-2] [match {external [1 | 2] | internal | nssa-external [1 | 2]}] [metric metric-value] [metric-type {internal | external}] [route-policy route-policy-name]
Static
redistribute static [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {1 | 2}] [route-policy route-policy-name]
no redistribute static [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {1 | 2}] [route-policy route-policy-name]
Syntax Description
Defaults
Level 2 is configured if no level is specified.
metric-type: internal
match: If no match keyword is specified, all OPSF routes are redistributed.Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the redistribute command to control the redistribution of routes between separate IS-IS instances. To control the propagation of routes between the levels of a single IS-IS instance, use the propagate level command.
Task ID
Examples
In this example, IS-IS instance isp_A readvertises all of the routes of IS-IS instance isp_B in Level 2 LSP. Note that the level-2 keyword affects which levels instance isp_A advertises the routes in and has no impact on which routes from instance isp_B are advertised (any Level 1 routes from IS-IS instance isp_B are included in the redistribution.
RP/0/RP0/CPU0:router(config)# router isis isp_ARP/0/RP0/CPU0:router(config-isis)# net 49.1234.2222.2222.2222.00RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# redistribute isis isp_B level-2!RP/0/RP0/CPU0:router(config)# router isis isp_BRP/0/RP0/CPU0:router(config-isis)# is-type level 1RP/0/RP0/CPU0:router(config-isis)# net 49.4567.2222.2222.2222.00RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# set-attached-bitRelated Commands
retransmit-interval (IS-IS)
To configure the amount of time between retransmission of each Intermediate System-to-Intermediate System (IS-IS) link-state packet (LSP) on a point-to-point link, use the retransmit-interval command in interface configuration mode. To restore the default value, use the no form of this command.
retransmit-interval seconds [level {1 | 2}]
no retransmit-interval [seconds [level {1 | 2}]]
Syntax Description
Defaults
seconds: 5 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
To prevent needless transmission results, the seconds argument should be conservative.
The retransmit-interval command has no effect on LAN (multipoint) interfaces. On point-to-point links, the value can be increased to enhance network stability.
Because retransmissions occur only when LSPs are dropped, setting this command to a higher value has little effect on reconvergence. The more neighbors networking devices have, and the more paths over which LSPs can be flooded, the higher this value can be made.
Task ID
Examples
The following example shows how to configure Packet-over-SONET/SDH (POS) interface 0/2/0/1 for retransmission of IS-IS LSPs every 60 seconds for a large serial line:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# retransmit-interval 60Related Commands
Configures the amount of time between retransmissions of any IS-IS LSPs on a point-to-point interface.
retransmit-throttle-interval
To configure minimum interval between retransmissions of different Intermediate System-to-Intermediate System (IS-IS) link-state packets (LSPs) on a point-to-point interface, use the retransmit-throttle-interval command in interface configuration mode. To remove the command from the configuration file and restore the system to its default condition, use the no form of this command.
retransmit-throttle-interval milliseconds [level {1 | 2}]
no retransmit-throttle-interval [milliseconds [level {1 | 2}]]
Syntax Description
milliseconds
Minimum delay (in milliseconds) between LSP retransmissions on the interface. Range is 0 to 65535.
level {1 | 2}
(Optional) Specifies routing Level 1 or Level 2 independently.
Defaults
Default is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the retransmit-throttle-interval command to define the minimum period of time that must elapse between retransmitting any two LSPs on an interface. The retransmit-throttle-interval command may be useful in very large networks with many LSPs and many interfaces as a way of controlling LSP retransmission traffic. This command controls the rate at which LSPs can be re-sent on the interface.
Task ID
Examples
The following example shows how to configure Packet-over-SONET/SDH (POS) interface 0/2/0/1 to limit the rate of LSP retransmissions to one every 300 milliseconds:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# interface POS0/2/0/1RP/0/RP0/CPU0:router(config-isis-if)# retransmit-throttle-interval 300Related Commands
Configures the minimum interval time between regenerating the same LSP.
Configures the amount of time between retransmission of each IS-IS LSP over a point-to-point link.
router isis
To enable the Intermediate System-to-Intermediate System (IS-IS) routing protocol and to specify an IS-IS instance, use the router isis command in global configuration mode. To disable IS-IS routing, use the no form of this command.
router isis instance-id
no router isis instance-id
Syntax Description
Defaults
An IS-IS routing protocol is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the router isis command to create an IS-IS routing process. An appropriate network entity title (NET) must be configured to specify the address of the area (Level 1) and system ID of the router. Routing must be enabled on one or more interfaces before adjacencies may be established and dynamic routing is possible.
Task ID
Examples
The following example shows how to configure IS-IS for IP routing:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# net 49.0001.0000.0001.00Related Commands
set-attached-bit
To configure an Intermediate System-to-Intermediate System (IS-IS) instance with an attached bit in the Level 1 link-state packet (LSP), use the set-attached-bit command in address family configuration mode. To remove the set-attached-bit command from the configuration file and restore the system to its default condition, use the no form of this command.
set-attached-bit
no set-attached-bit
Syntax Description
This command has no arguments or keywords.
Defaults
Attached bit is not set in the LSP.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set-attached bit command to set an IS-IS instance with an attached bit in the Level 1 LSP that allows another IS-IS instance to redistribute Level 2 topology. The attached bit is used when the Level 2 connectivity from another IS-IS instance is advertised by the Level 1 attached bit.
Cisco IOS XR software does not support multiple Level 1 areas in a single IS-IS routing instance. But the equivalent functionality is achieved by redistribution of routes between two IS-IS instances by using the redistribute (IS-IS) command.
The attached bit is configured for a specific address family only if the single-topology command is not configured.
Note
Task ID
Examples
The following example shows how to set the attached bit for a Level 1 instance that allows the Level 2 instance to redistribute routes from the Level 1 instance:
RP/0/RP0/CPU0:router(config)# router isis 1RP/0/RP0/CPU0:router(config-isis)# net 49.0001.0001.0001.0001.00RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# redistribute isis 2 level 2!RP/0/RP0/CPU0:router(config-isis-af)# interface POS0/3/0/0RP/0/RP0/CPU0:router(config-isis-af-if)# address-family ipv4 unicast!!RP/0/RP0/CPU0:router(config)# router isis 2RP/0/RP0/CPU0:router(config-isis)# is-type level-1RP/0/RP0/CPU0:router(config-isis)# net 49.0002.0001.0001.0002.00RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# set-attached-bit!RP/0/RP0/CPU0:router(config-isis-af)# interface POS0/1/0/0RP/0/RP0/CPU0:router(config-isis-af-if)# address-family ipv4 unicastRelated Commands
Redistributes routes from one IS-IS instance into another instance.
Configures the link topology for IPv4 when IPv6 is configured.
set-overload-bit
To configure the router to signal other routers not to use it as an intermediate hop in their shortest path first (SPF) calculations, use the set-overload-bit command in router configuration mode. To remove the designation, use the no form of this command.
set-overload-bit [on-startup {delay | wait-for-bgp}] [level {1 | 2}]
no set-overload-bit [[on-startup {delay | wait-for-bgp}] [level {1 | 2}]]
Syntax Description
Defaults
The overload bit is not set.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set-overload-bit command to force the router to set the overload bit in its nonpseudonode link-state packets (LSPs). Normally the setting of the overload bit is allowed only when a router experiences problems. For example, when a router is experiencing a memory shortage, the reason might be that the link-state database is not complete, resulting in an incomplete or inaccurate routing table. If the overload bit is set in the LSPs of the unreliable router, other routers can ignore the router in their SPF calculations until it has recovered from its problems. The result is that no paths through the unreliable router are seen by other routers in the Intermediate System-to-Intermediate System (IS-IS) area. However, IP prefixes directly connected to this router are still reachable.
The set-overload-bit 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.
Routers with overload bit set are:
•
A router configured as an LSP flooding server, for example, on a nonbroadcast multiaccess (NBMA) network, in combination with the mesh group feature.
Task ID
Examples
The following example shows how to configure the overload bit:
RP/0/RP0/CPU0:router(config)# router isis ispRP/0/RP0/CPU0:router(config-isis)# set-overload-bitshow isis adjacency
To display Intermediate System-to-Intermediate System (IS-IS) adjacencies, use the show isis adjacency command in EXEC mode.
show isis [instance instance-id] adjacency [level {1 | 2}] [interface-type interface-instance] [detail] [systemid system-id]
Syntax Description
Defaults
No instance ID specified displays IS-IS adjacencies for all the IS-IS instances.
Both Level 1 and Level 2 are configured if no level is specified.Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show isis adjacency command:
RP/0/RP0/CPU0:router# show isis adjacencyIS-IS p Level-1 adjacencies:System Id Interface SNPA State Hold Changed NSF BFD12a4 PO0/1/0/1 *PtoP* Up 23 00:00:06 Capable Init12a4 Gi0/6/0/2 0004.2893.f2f6 Up 56 00:04:01 Capable UpTotal adjacency count: 2IS-IS p Level-2 adjacencies:System Id Interface SNPA State Hold Changed NSF BFD12a4 PO0/1/0/1 *PtoP* Up 23 00:00:06 Capable None12a4 Gi0/6/0/2 0004.2893.f2f6 Up 26 00:00:13 Capable InitTotal adjacency count: 2Table 48 describes the significant fields shown in the display.
Related Commands
show isis adjacency-log
To display the Intermediate System-to-Intermediate System (IS-IS) adjacency log, use the show isis adjacency-log command in EXEC mode.
show isis adjacency-log [level {1 | 2}] [last number | first number]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show isis adjacency-log command:
RP/0/RP0/CPU0:router# show isis adjacency-logIS-IS 10 Level 1 Adjacency logWhen System Interface State Details4d00h 12a1 PO0/5/0/0 d -> i4d00h 12a1 PO0/5/0/0 i -> u New adjacencyIPv4 Unicast Up4d00h 12a1 Gi0/6/0/0 d -> u New adjacency4d00h 12a1 Gi0/6/0/0 u -> d Interface statedown3d17h 12a1 Gi0/6/0/0 d -> u New adjacency3d17h 12a1 Gi0/6/0/0 u -> d Interface statedown01:44:07 12a1 Gi0/6/0/0 d -> u New adjacencyIS-IS 10 Level 2 Adjacency logWhen System Interface State Details4d00h 12a1 PO0/5/0/0 d -> i4d00h 12a1 PO0/5/0/0 i -> u New adjacencyIPv4 Unicast Up4d00h 12a1 Gi0/6/0/0 d -> u New adjacency4d00h 12a1 Gi0/6/0/0 u -> d Interface statedown3d17h 12a1 Gi0/6/0/0 d -> u New adjacency3d17h 12a1 Gi0/6/0/0 u -> d Interface statedown01:44:07 12a1 Gi0/6/0/0 d -> u New adjacencyTable 49 describes the significant fields shown in the display.
show isis checkpoint adjacency
To display the Intermediate System-to-Intermediate System (IS-IS) checkpoint adjacency database, use the show isis checkpoint adjacency command in EXEC mode.
show isis [instance instance-id] checkpoint adjacency
Syntax Description
Defaults
No instance ID specified displays IS-IS checkpoint adjacencies for all the IS-IS instances.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show isis checkpoint adjacency command to display the checkpointed adjacencies. With this information you can restore the adjacency database during a Cisco proprietary nonstop forwarding (NSF) restart. This command, with the show isis adjacency command, may be used to verify the consistency of the two databases.
Task ID
Examples
The following is sample output from the show isis checkpoint adjacency command:
RP/0/RP0/CPU0:router# show isis checkpoint adjacencyInterface Level System ID State Circuit ID Chkpt IDPOS3/0/0/1 1 router-gsr8 Up 0001.0000.0008.04 80011fecPOS0/4/0/1 1 router-gsr9 Up 0001.0000.0006.01 80011fd8POS3/0/0/1 2 router-gsr8 Up 0001.0000.0008.04 80011fc4Table 50 describes the significant fields shown in the display.
Related Commands
show isis checkpoint interface
To display the Intermediate System-to-Intermediate System (IS-IS) checkpoint interfaces, use the show isis checkpoint interface command in EXEC mode.
show isis checkpoint interface
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show isis checkpoint interface command:
RP/0/RP0/CPU0:router# show isis checkpoint interfaceIS-IS 10 checkpoint interfaceInterface Index CircNum DIS Areas Chkpt IDPO0/5/0/0 0 0 NONE 80002fe8Gi0/6/0/0 1 3 L1L2 80002fd0Table 51 describes the significant fields shown in the display.
show isis checkpoint lsp
To display the Intermediate System-to-Intermediate System (IS-IS) checkpoint link-state packet (LSP) protocol data unit (PDU) identifier database, use the show isis checkpoint lsp command in EXEC mode.
show isis [instance instance-id] checkpoint lsp
Syntax Description
Defaults
No instance ID specified displays IS-IS checkpoint LSPs for all the IS-IS instances.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The checkpointed LSPs displayed by this command are used to restore the LSP database during a Cisco proprietary nonstop forwarding (NSF) restart. The show isis checkpoint lsp command, with the show isis database command, may be used to verify the consistency of the two databases.
Task ID
Examples
The following is sample output from the show isis checkpoint lsp command:
RP/0/RP0/CPU0:router# show isis checkpoint lspLevel LSPID Chkpt ID1 router-gsr6.00-00 80011f9c1 router-gsr6.01-00 80011f881 router-gsr8.00-00 80011f741 router-gsr9.00-00 80011f602 router-gsr6.00-00 80011f4c2 router-gsr6.01-00 80011f382 router-gsr8.00-00 80011f242 router-gsr9.00-00 80011f10Total LSP count: 8 (L1: 4, L2 4, local L1: 2, local L2 2)Table 52 describes the significant fields shown in the display.
Related Commands
