-
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}
