|
|
The International Organization for Standardization (ISO) Connectionless Network Service (CLNS) protocol is a standard for the network layer of the OSI model.
Use the commands in this chapter to configure and monitor ISO CLNS networks. For ISO CLNS protocol configuration information and examples, refer to the "Configuring ISO CLNS" chapter of the Network Protocols Configuration Guide, Part 3.
password | Password you assign. |
No area authentication password is defined.
Router configuration
This command first appeared in Cisco IOS Release 10.0.
This password is inserted in Level 1 (station router level) link-state PDUs, complete sequence number PDUs (CSNPs), and partial sequence number PDUs (PSNPs).
The following example assigns an area authentication password:
router isis
area-password angel
You can use the master indexes or search online for documentation of related commands.
Use the clear clns cache EXEC command to clear and reinitialize the CLNS routing cache.
clear clns cacheThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example clears the CLNS routing cache:
clear clns cache
Use the clear clns es-neighbors EXEC command to remove end system (ES) neighbor information from the adjacency database.
clear clns es-neighborsThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example removes the ES neighbor information from the adjacency database:
clear clns es-neighbors
You can use the master indexes or search online for documentation of related commands.
clear clns neighbors
show clns es-neighbors
Use the clear clns is-neighbors EXEC command to remove intermediate system (IS) neighbor information from the adjacency database.
clear clns is-neighborsThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example removes the IS neighbor information from the adjacency database:
clear clns is-neighbors
You can use the master indexes or search online for documentation of related commands.
clear clns neighbors
show clns is-neighbors
Use the clear clns neighbors EXEC command to remove CLNS neighbor information from the adjacency database.
clear clns neighborsThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example removes the CLNS neighbor information from the adjacency database:
clear clns neighbors
You can use the master indexes or search online for documentation of related commands.
clear clns es-neighbors
clear clns is-neighbors
show clns neighbors
Use the clear clns route EXEC command to remove all of the dynamically derived CLNS routing information.
clear clns routeThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example removes all of the dynamically derived CLNS routing information:
clear clns route
You can use the master indexes or search online for documentation of related commands.
Use the clear clns route EXEC command to remove all of the dynamically derived CLNS routing information.
clear clns routeThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following example removes all of the dynamically derived CLNS routing information:
clear clns route
You can use the master indexes or search online for documentation of related commands.
Use the clear tarp counters EXEC command to clear all Target Identifier Address Resolution Protocol (TARP) counters that are shown with the show tarp traffic command.
clear tarp countersThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
Clearing the counters can assist you with troubleshooting. For example, you may want to clear the counter and then check to see how many PDUs the router is originating.
The following example clears the TARP counters:
clear tarp counters
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The loop-detection buffer table prevents TARP packets from looping.
Clearing the counters assists you with troubleshooting. For example, clear the loop-detection buffer table and assign a new sequence number (using the tarp sequence-number command) to ensure that other hosts update their entries.
The following example clears the TARP loop-detection buffer table:
clear tarp ldb-table
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
Clearing the TID cache is one method to remove old entries. Another method is to set the length of time a dynamically created TARP entry remains in the TID cache using the tarp-cache-timer command.
The clear tarp tid-table command does not delete the cache entry for its own TID or the cache entries explicitly configured with the tarp map command.
The following example clears the TARP TID table:
clear tarp tid-table
You can use the master indexes or search online for documentation of related commands.
show tarp map
show tarp tid-cache
tarp allow-caching
tarp cache-timer
tarp map
Use the clns access-group interface configuration command to filter transit CLNS traffic going either into or out of the router or both on a per-interface basis. Use the no form of this command to disable filtering of transit CLNS packets.
clns access-group name [in | out]
name | Name of the filter set or expression to apply. |
in | (Optional) Filter should be applied to CLNS packets entering the router. |
out | (Optional) Filter should be applied to CLNS packets leaving the router. If you do not specify an in or out keyword, out is assumed. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command has no effect on any CLNS packets sourced by the Cisco IOS software. It applies only to packets forwarded by the software. Fast switching is still supported with access groups in place, but its performance will be impacted based on the complexity of the filters.
For descriptions of filter sets and expressions, refer to the clns filter-expr, clns filter-set, and clns template-alias global configuration commands in this chapter.
The following example shows how to enable forwarding of frames received on Ethernet 0 that had a source address of anything other than 38.840F, and a destination address that started with 47.0005 or 47.0023, but nothing else:
clns filter-set US-OR-NORDUNET permit 47.0005...
clns filter-set US-OR-NORDUNET permit 47.0023...
clns filter-set NO-ANSI deny 38.840F...
clns filter-set NO-ANSI permit default
clns filter-expr STRANGE source NO-ANSI and destination US-OR-NORDUNET
interface ethernet 0
clns access-group STRANGE in
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns filter-set
clns template-alias
Use the clns adjacency-filter interface configuration command to filter the establishment of CLNS ES and IS adjacencies. Use the no form of this command to disable this filtering.
clns adjacency-filter {es | is} name
es | ES adjacencies are to be filtered. |
is | IS adjacencies are to be filtered. |
name | Name of the filter set or expression to apply. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Filtering is performed on full NSAP addresses. If filtering should only be performed on system IDs or any other substring of the full NSAP address, the wildcard-matching capabilities of filter sets should be used to ignore the insignificant portions of the NSAP addresses.
For descriptions of filter sets and expressions, refer to the clns filter-expr, clns filter-set, and clns template-alias global configuration commands in this chapter.
The following example builds a filter that accepts end system adjacencies with only two systems, based only on their system IDs:
clns filter-set ourfriends...0000.0c00.1234.**
clns filter-set ourfriends...0000.0c00.125a.**
interface ethernet 0
clns adjacency-filter es ourfriends
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns filter-set
clns template-alias
To control the invalidation rate of the CLNS route cache, use the clns cache-invalidate-delay global configuration command. To allow the CLNS route cache to be immediately invalided, use the no form of this command.
clns cache-invalidate-delay [minimum maximum quiet threshold]
minimum | (Optional) Minimum time (in seconds) between invalidation request and actual invalidation. The default is 2 seconds. |
maximum | (Optional) Maximum time (in seconds) between invalidation request and actual invalidation. The default is 5 seconds. |
quiet | (Optional) Length of time (in seconds) before invalidation. |
threshold | (Optional) Maximum number of invalidations considered to be quiet. |
minimum = 2 seconds
maximum = 5 seconds
quiet = 3 seconds
threshold = 0 invalidations
Global configuration
This command first appeared in Cisco IOS Release 10.3.
All cache invalidation requests are honored immediately.
This command should typically not be used except under the guidance of technical support personnel. Incorrect settings can seriously degrade network performance.
In an environment with heavy traffic, the CLNS cache can get invalidated (purged) too frequently. Frequent cache invalidations will cause the CPU to spend too much time purging and repopulating the cache.
The clns cache-invalidate-delay command controls how the CLNS route cache is purged. The intent is to delay invalidation of the cache until after routing has settled down. Because the routing table changes tend to be clustered in a short period of time, and the cache may be purged repeatedly, a high CPU load might be placed on the router.
When this feature is enabled, and the system requests that the route cache be purged, the request is held for at least the minimum seconds. Then the system determines whether the cache has been "quiet" (that is, less than threshold invalidation requests in the last quiet seconds). If the cache has been quiet, the cache is then purged. If the cache does not become quiet within maximum seconds after the first request, it is purged unconditionally.
Manipulation of these parameters trades off CPU utilization versus route convergence time. The timing of routing protocols is not affected, but the removal of stale cache entries is affected.
The following example sets a minimum delay of 5 seconds, a maximum delay of 30 seconds, and quiet threshold of no more than 5 invalidation requests in the previous 10 seconds:
clns cache-invalidate-delay 5 30 10 5
You can use the master indexes or search online for documentation of related commands.
clns route-cache
show clns cache
Use the clns checksum interface configuration command to enable checksum generation when ISO CLNS routing software sources a CLNS packet. Use the no form of this command to disable checksum generation.
clns checksumThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command has no effect on routing packets, such as ES-IS, ISO-Interior Gateway Routing Protocol (IGRP) and IS-IS, sourced by the system. It applies to pings and trace route packets.
The following example shows how to enable checksum generation:
interface ethernet 0
clns checksum
Use the clns cluster-alias interface configuration command to allow multiple systems to advertise the same system ID as other systems in ES hello messages. Use the no form of this command to disable cluster aliasing.
clns cluster-aliasThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This feature caches multiple ES adjacencies with the same NSAP, but with different SNPA addresses. When a packet is destined to the common NSAP address, the Cisco IOS software load-splits the packets among the different SNPA addresses. A router that supports this capability forwards traffic to each system.
If DECnet Phase V cluster aliases are disabled on an interface, ES hello packet information is used to replace any existing adjacency information for the NSAP. Otherwise, an additional adjacency (with a different SNPA) is created for the same NSAP.
The following example shows how cluster aliasing is enabled on specified interfaces:
clns nsap 47.0004.004d.0001.0000.0c00.1111.00
clns routing
interface ethernet 0
clns cluster-alias
interface ethernet 1
clns cluster-alias
Use the clns configuration-time global configuration command to specify the rate at which ES hellos and IS hellos are sent. Use the no form of this command to restore the default value.
clns configuration-time seconds
seconds | Rate in seconds at which ES and IS hello packets are sent. |
60 seconds
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example specifies that ES hellos and IS hellos are to be sent every 100 seconds:
clns configuration-time 100
You can use the master indexes or search online for documentation of related commands.
clns esct-time
clns holding-time
Use the clns congestion-threshold interface configuration command to set the congestion experienced bit if the output queue has more than the specified number of packets in it. A number value of zero or the no form of this command prevents this bit from being set. Use the no form of this command to remove the parameter setting and set it to 0.
clns congestion-threshold number
number | Number of packets that are allowed in the output queue before the system sets the congestion-experienced bit. The value zero (0) prevents this bit from being set. |
4 packets
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
If a router configured for CLNS experiences congestion, it sets the congestion experienced bit. The congestion threshold is a per-interface parameter set by this interface configuration command. An error PDU (ERPDU) is sent to the sending router and the packet is dropped if the number of packets exceeds the threshold.
The following example sets the congestion threshold to 10:
interface ethernet 0
clns congestion-threshold 10
Use the clns dec-compatible interface configuration command to allow IS hellos sent and received to ignore the N-selector byte. Use the no form of this command to disable this feature.
clns dec-compatibleThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example enables DEC-compatible mode:
interface ethernet 0
clns dec-compatible
Use the clns enable interface configuration command if you do not intend to perform any static or dynamic routing on an interface, but intend to pass ISO CLNS packet traffic to end systems. Use the no form of this command to disable ISO CLNS on a particular interface.
clns enableThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example enables ISO CLNS on Ethernet interface 0:
interface ethernet 0
clns enable
Use the clns erpdu-interval interface configuration command to determine the minimum interval time, in milliseconds, between error ERPDUs. A milliseconds value of zero or the no form of this command turns off the interval and effectively sets no limit between ERPDUs.
clns erpdu-interval milliseconds
milliseconds | Minimum interval time (in milliseconds) between ERPDUs. |
10 ms
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command does not send ERPDUs more frequently than 1 per interface per 10 ms. It is wise not to send an ERPDU frequently if bandwidth is precious (such as over slow serial lines).
The following example sets the ERPDU interval to 30 ms:
interface ethernet 0
clns erpdu-interval 30
You can use the master indexes or search online for documentation of related commands.
Use the clns esct-time interface configuration command to supply an ES configuration timer option in a transmitted IS hello packet that tells the ES how often it should transmit ES hello packet PDUs. Use the no form of this command to restore the default value and disable this feature.
clns esct-time seconds
seconds | Time, in seconds, between ES hello PDUs. Range is 0 to 65535. |
0 seconds (disabled)
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example sets the ES configuration time to 10 seconds:
interface ethernet 0
clns esct-time 10
You can use the master indexes or search online for documentation of related commands.
clns configuration-time
clns holding-time
Use the clns es-neighbor interface configuration command to list all systems that will be used when you manually specify the NSAP-to-SNPA mapping. The SNPAs are the MAC addresses. Use the no form of this command to delete the ES neighbor.
clns es-neighbor nsap snpa
nsap | Specific NSAP to map to a specific MAC address. |
snpa | Data link (MAC) address. |
No end systems are listed.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
If you have configured either the clns router iso-igrp or clns router isis interface configuration commands for a particular interface, the ES-IS routing software automatically turns ES-IS on for that interface.
It is only necessary to use static mapping for those end systems that do not support ES-IS. The Cisco IOS software will continue to discover dynamically those end systems that do support ES-IS.
The following example defines an ES neighbor on Ethernet interface 0:
interface ethernet 0
clns es-neighbor 47.0004.004D.0055.0000.0C00.A45B.00 0000.0C00.A45B
In this case, the end systems with the following NSAP, or network entity title (NET), are configured with an Ethernet MAC address of 0000.0C00.A45B:
47.0004.004D.0055.0000.0C00.A45B.00
You can use the master indexes or search online for documentation of related commands.
Use one or more clns filter-expr global configuration commands to combine CLNS filter sets and CLNS address templates to create complex logical NSAP pattern-matching expressions. Use the no form of this command to delete the expression.
clns filter-expr ename term
ename | Alphanumeric name to apply to this filter expression. |
term | Filter expression term. A term can be any of the following: ename—Another, previously defined, filter expression. sname (or destination sname)—A previously defined filter set name, with the filter set applied to the destination NSAP address. source sname—A previously defined filter set name, with the filter set applied to the source NSAP address. |
No filter expression is defined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Filter expressions can reference previously defined filter expressions, so you can build arbitrarily complex expressions.
The first form listed defines a simple filter expression that is pattern matched only if the pattern given by term is matched.
The second form defines a filter expression that is pattern matched only if the pattern given by term is not matched.
The third form defines a filter expression that is pattern matched if either of the patterns given by the two terms are matched.
The fourth form defines a filter expression that is pattern matched only if both of the patterns given by the two terms are matched.
The fifth form defines a filter expression that is pattern matched only if one of the patterns, but not both, given by the two terms are matched.
The sixth and final form of the command deletes the definition of an existing filter expression.
Use this command to define complex filter expressions. See the description of the clns filter-set global configuration command to learn how to define filter sets.
The following example shows how to define a filter expression that matches addresses with a source address of anything besides 39.840F, and a destination address that started with 47.0005 or 47.0023, but nothing else:
clns filter-set US-OR-NORDUNET permit 47.0005...
clns filter-set US-OR-NORDUNET permit 47.0023
clns filter-set NO-ANSI deny 38.840F...
clns filter-set NO-ANSI permit default
!
clns filter-expr STRANGE source NO-ANSI and destination US-OR-NORDUNET
You can use the master indexes or search online for documentation of related commands.
clns filter-set
clns template-alias
show clns filter-expr
Use one or more clns filter-set global configuration commands to build a list of CLNS address templates with associated permit and deny conditions for use in CLNS filter expressions. CLNS filter expressions are used in the creation and use of CLNS access lists. Use the no form of this command to delete the entire filter set.
clns filter-set name [permit | deny] template
name | Alphanumeric name to apply to this filter set. |
permit | deny | (Optional) Addresses matching the pattern specified by template are to be permitted or denied. If neither permit nor deny is specified, permit is assumed. |
template | Address template, template alias name, or the keyword default. Address templates and alias names are described under the description of the clns template-alias global configuration command. The default keyword denotes a zero-length prefix and matches any address. |
No address templates are defined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Use this command to define a list of pattern matches and permit/deny conditions for use in CLNS filter expressions. Filter expressions are used in the creation and use of CLNS access lists. See the description of the clns filter-expr global configuration command to learn how to define filter expressions and the clns template-alias global configuration command to learn how to define address templates and address template aliases.
Each address that must be matched against a filter set is first compared against all the entries in the filter set, in order, for an exact match with the address. If the exact match search fails to find a match, then the entries in the filter set containing wildcard matches are scanned for a match, again, in order. The first template that matches is used. If an address does not match any of the filter set entries, an implicit "deny" is returned as the permit/deny action of the filter set.
The following example returns a permit action if an address starts with either 47.0005 or 47.0023. It returns an implicit deny action on any other address.
clns filter-set US-OR-NORDUNET permit 47.0005...
clns filter-set US-OR-NORDUNET permit 47.0023...
The following example returns a deny action if an address starts with 39.840F, but returns a permit action for any other address:
clns filter-set NO-ANSI deny 38.840F...
clns filter-set NO-ANSI permit default
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns template-alias
show clns filter-set
Use the clns holding-time global configuration command to allow the sender of an ES hello or IS hello to specify the length of time you consider the information in the hello packets to be valid. Use the no form of this command to restore the default value (300 seconds, or 5 minutes).
clns holding-time seconds
seconds | Length of time in seconds during which the information in the hello packets is considered valid. |
300 seconds (5 minutes)
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Setting this value too high puts extra traffic on a line and adds time to process hellos. However, you want to avoid setting it too low if your topology changes more often than the Cisco IOS software sends updates.
The following example sets the holding time at 150 seconds:
clns holding-time 150
You can use the master indexes or search online for documentation of related commands.
clns configuration-time
clns esct-time
Use the clns host global configuration command to define a name-to-NSAP mapping that can then be used with commands requiring NSAPs.
clns host name nsap
name | Desired name for the NSAP. The first character can be either a letter or a number, but if you use a number, the operations you can perform are limited. |
nsap | NSAP to which that the name maps. |
No mapping is defined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The assigned NSAP name is displayed, where applicable, in show and debug EXEC commands. There are some effects and requirements associated with using names to represent network entity titles (NETs) and NSAPs, however. Although using names as proxies for addresses is allowed with CLNS commands, they are never written out to nonvolatile random-access memory (NVRAM).
The first character can be either a letter or a number, but if you use a number, the operations you can perform (such as ping) are limited.
The clns host command is generated after all other CLNS commands when the configuration file is parsed. As a result, the NVRAM version of the configuration cannot be edited to specifically change the address defined in the original clns host command. You must specifically change any commands that refer to the original address. This affects all commands that accept names.
The commands that are affected by these requirements include the following:
The following example defines names to NSAPs:
clns host cisco1 39.0001.0000.0c00.1111.00
clns host cisco2 39.0002.0000.0c00.1111.00
router iso-igrp
net cisco1
!
interface ethernet 0
clns net cisco2
You can use the master indexes or search online for documentation of related commands.
clns es-neighbor
clns is-neighbor
Use the clns is-neighbor interface configuration command to list all intermediate systems that will be used when you manually specify the NSAP-to-SNPA mapping. The SNPAs are the MAC addresses. Use the no form of this command to delete the specified IS neighbor.
clns is-neighbor nsap snpa
nsap | NSAP of a specific intermediate system to enter as neighbor to a specific MAC address. |
snpa | Data link (MAC) address. |
No intermediate systems are listed.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
It is sometimes preferable for a router to have a neighbor entry statically configured rather than learned through ES-IS, ISO IGRP, or IS-IS. This interface configuration command enters an IS neighbor.
The following example defines an IS neighbor on Ethernet interface 0:
interface ethernet 0
clns is-neighbor 47.0004.004D.0055.0000.0C00.A45B.00 0000.0C00.A45B
You can use the master indexes or search online for documentation of related commands.
Use the clns mtu interface configuration command to set the maximum transmission unit (MTU) packet size for the interface. Use the no form of this command to restore the default and maximum packet size.
clns mtu bytes
bytes | Maximum packet size in bytes. The minimum value is 512; the default and maximum packet size depend on the interface type. |
Depends on interface type
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
All interfaces have a default maximum packet size. You can set the MTU size of the packets sent on the interface with the mut interface configuration command.
All routers on a physical medium must have the same protocol MTU in order to operate.
The CTR card does not support the switching of frames larger than 4472 bytes. Interoperability problems can occur if CTR cards are intermixed with other Token Ring cards on the same network. These problems can be minimized by lowering the CLNS MTUs to be the same on all routers on the network with the clns mtu command.
The following example sets the MTU packet size to 1000 bytes:
interface ethernet 0
clns mtu 1000
You can use the master indexes or search online for documentation of related commands.
mtu
Use the clns net global configuration command to assign a static address for a router. If the Cisco IOS software is configured to support ISO CLNS, but is not configured to dynamically route CLNS packets using ISO IGRP or IS-IS, use this command to assign an address to the router. Use the no form of this command to remove any previously configured NET or NSAP address.
clns net {net-address | name}
net-address | NET address. Refer to the "Usage Guidelines" section. |
name | CLNS host name to be associated with this interface. |
No static address is assigned.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
A CLNS packet sent to any of the defined NSAPs or NETs will be received by the router. The Cisco IOS software chooses the NET to use when it sends a packet with the following algorithm:
The following example assigns a static address:
clns net 49.0001.aa00.0400.9105.00
Use the clns net interface configuration command to assign an NSAP address or name to a router interface. If the Cisco IOS software is configured to support ISO CLNS, but is not configured to dynamically route CLNS packets using an ISO IGRP or IS-IS, use this command to assign an address to the router. Use the no form of this command to remove any previously configured NSAP address.
clns net {nsap-address | name}
nsap-address | Specific NSAP address. |
name | Name to be associated with this interface. |
No address or name is assigned.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command is useful if you are doing static routing and need to control the source NET used by the router on each interface.
The following example assigns an NSAP address to a router interface:
interface ethernet 0
clns net 49.0001.0000.0c00.1111.00
The following example assigns a name to a router interface:
interface ethernet 0
clns net cisco
Use the clns packet-lifetime global configuration command to specify the initial lifetime for locally generated packets. Use the no form of this command to remove the parameter's settings.
clns packet-lifetime seconds
Packet lifetime in seconds. |
32 seconds
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example sets a packet lifetime of 120 seconds:
clns packet-lifetime 120
You can use the master indexes or search online for documentation of related commands.
Use the clns rdpdu-interval interface configuration command to determine the minimum interval time (in milliseconds) between redirect PDUs (RDPDUs). A milliseconds value of zero or the no form of this command turns off the interval rate and effectively sets no limit between RDPDUs.
clns rdpdu-interval milliseconds
milliseconds | Minimum interval time (in milliseconds) between RDPDUs. |
100 ms
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
An RDPDU is rate-limited and is not sent more frequently than one per interface per 100 ms. There is no need to change the default. This setting will work fine for most networks.
The following example sets an interval of 50 ms:
interface ethernet 0
clns rdpdu-interval 50
You can use the master indexes or search online for documentation of related commands.
Use this form of the clns route global configuration command to create an interface static route. Use the no form of this command to remove this route.
clns route nsap-prefix type number [snpa-address]
nsap-prefix | Network service access point prefix. This value is entered into a static routing table and used to match the beginning of a destination NSAP. The longest NSAP-prefix entry that matches is used. |
type | Interface type. |
number | Interface number. |
snpa-address | (Optional) Specific SNPA address. Optional for serial links; required for multiaccess networks. |
No interface static routes are created.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
If you do not specify an SNPA address when you have a multiaccess network, you will receive an error message indicating a bad SNPA.
The following example shows how to create a static route for an Ethernet interface:
clns route 39.0002 ethernet 3 aa00.0400.1111
The following example shows how to create a static route for a serial interface:
clns route 39.0002 serial 0
You can use the master indexes or search online for documentation of related commands.
clns route (to enter a static route)
clns route default
clns route discard
Use this form of the clns route global configuration command to enter a specific static route. NSAPs that start with nsap-prefix are forwarded to next-hop-net or the name of the next hop. Use the no form of this command to remove this route.
clns route nsap-prefix {next-hop-net | name}
nsap-prefix | Network service access point prefix. This value is entered into a static routing table and used to match the beginning of a destination NSAP. The longest NSAP-prefix entry that matches is used. |
next-hop-net | Next-hop NET. This value is used to establish the next hop of the route for forwarding packets. |
name | Name of the next hop node. This value can be used instead of the next-hop NET to establish the next hop of the route for forwarding packets. |
No static route is entered.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example forwards all packets toward the specified route:
clns route 39.840F 47.0005.80FF.FF00.0123.4567.89AB.00
You can use the master indexes or search online for documentation of related commands.
clns route (to enter a static route)
clns route default
clns route discard
Use the clns route-cache interface configuration command to allow fast switching through the cache. Use the no form of this command to disable fast switching.
clns route-cacheThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The cache still exists and is used after the no clns route-cache command is used; the software just does not do fast switching through the cache.
The following example shows how to allow fast switching through the cache:
interface ethernet 0
clns route-cache
Use the clns route global configuration command to configure a default zero-length prefix rather than type an NSAP prefix. Use the no form of this command to remove this route.
clns route default nsap-prefix type number
nsap-prefix | Network service access point prefix that is a default zero-length prefix. |
type | Interface type. Specify the interface type immediately followed by the interface number; there is no space between the two. |
number | Interface number. |
No default prefix is configured.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example configures a default zero-length prefix:
clns route default 39.840F ethernet0
You can use the master indexes or search online for documentation of related commands.
clns route (interface static route)
clns route (to enter a static route)
clns route discard
To assign a default discard route and automatically discard packets with NSAP addresses that do not match any existing routes, use the clns route default discard global configuration command. To remove the default discard route, use the no form of this command.
clns route default discardThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
The only time you would use this command is if you are using static routing and ES-IS and you wish disable ES-IS and therefore reduce the router to using purely static routing. Using this command will reduce the functionality of the router by forcing ISO CLNS to ignore all nodes that were learned through ES-IS.
The following example assigns a default discard route:
clns route default discard
When you enter the enter the show clns route command, you will see the following default discard route information:
#show clns route
Codes: C - connected, S - static, d - DecnetIV
I - ISO-IGRP, i - IS-IS, e - ES-IS
S Default Prefix [10/0], Discard Entry
You can use the master indexes or search online for documentation of related commands.
show clns route
Use the clns route discard global configuration command to explicitly tell a router to discard packets with NSAP addresses that match the specified nsap-prefix. Use the no form of this command to remove this route.
clns route nsap-prefix discard
nsap-prefix | Network service access point prefix. This value is entered into a static routing table and used to match the beginning of a destination NSAP. The longest NSAP-prefix entry that matches is used. |
discard | Explicitly tells a router to discard packets with NSAPs that match the specified nsap-prefix. |
No NSAP addresses are identified.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The decnet advertise command and the clns route discard command work together when DECnet Phase IV/V conversion is enabled. Any packet with the specified CLNS NSAP prefix causes CLNS to behave as if no route were found. Because DECnet Phase IV/V conversion is enabled, the route is then looked up in the Phase IV routing table. The router that is advertising the DECnet Phase IV route converts the packet to OSI and sends it to the router that is advertising the CLNS discard static route. Once it gets there, the packet is converted back to Phase IV.
CLNS discard routes cannot be used to discard packets that are addressed to a destination for which there is a dynamic route, if that destination is within the domain (ISO-IGRP) or area (IS-IS) of the router.
The following example discards packets with a destination NSAP address that matches the prefix 47.0005:
clns route 47.0005 discard
You can use the master indexes or search online for documentation of related commands.
clns route (interface static route)
clns route (to enter a static route)
clns route default
Use the clns router isis interface configuration command to enable IS-IS routing for OSI on a specified interface. Use the no form of this command with the appropriate area tag to disable IS-IS routing for the system.
clns router isis [tag]
tag | (Optional) Meaningful name for a routing process. If not specified, a null tag is assumed. It must be unique among all CLNS router processes for a given router. Use the same text for the argument tag as specified in the router isis global configuration command. |
IS-IS routing is not specified for any interface.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Creating a name for a routing process means that you use names when configuring routing. You can specify only one IS-IS process per router.
The following example enables IS-IS routing for OSI on Ethernet interface 0:
router isis cisco
net 39.0001.0000.0c00.1111.00
interface ethernet 0
clns router isis cisco
You can use the master indexes or search online for documentation of related commands.
Use the clns router iso-igrp interface configuration command to specify ISO IGRP routing on a specified interface. Use the no form of the global configuration command with the appropriate tag to disable ISO IGRP routing for the system.
clns router iso-igrp tag [level 2]
tag | Meaningful name for routing process. It must be unique among all CLNS router processes for a given router. This tag should be the same as defined for the routing process in the router iso-igrp global configuration command. |
level 2 | (Optional) Allows the interface to advertise Level 2 information. |
ISO IGRP routing is not specified on any interface.
Interface configuration
Global configuration
This command first appeared in Cisco IOS Release 10.0.
If you want this interface to advertise Level 2 information only, use the level 2 keyword. This option reduces the amount of router-to-router traffic by telling the Cisco IOS software to send out only Level 2 routing updates on certain interfaces. Level 1 information is not passed on the interfaces for which the Level 2 option is set.
In the following example, the interface advertises Level 2 information only on serial interface 0:
router iso-igrp marketing
net 49.0001.0000.0c00.1111.00
interface serial 0
clns router iso-igrp marketing level 2
You can use the master indexes or search online for documentation of related commands.
Use the clns routing global configuration command to enable routing of CLNS packets. Use the no form of this command to disable CLNS routing.
clns routingThis command has no arguments or keywords.
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example enables routing of CLNS packets:
clns routing
You can use the master indexes or search online for documentation of related commands.
Use the clns security pass-through global configuration command to allow the Cisco IOS software to pass packets that have security options set. Use the no form of this command to disable this function.
clns security pass-throughThis command has no arguments or keywords.
The software discards any packets it sees as set with security options.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
The following example allows the Cisco IOS software to pass packets that have security options set:
clns routing
router iso-igrp
net 47.0004.004d.0001.0000.0c11.1111.00
clns security pass-through
You can use the master indexes or search online for documentation of related commands.
Use the clns send-erpdu interface configuration command to allow CLNS to send an error PDU when the routing software detects an error in a data PU. Use the no form of this command o disable this function.
clns send-erpduThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
When a CLNS packet comes in, the routing software looks in the routing table for the next hop. If it does not find the next hop, the packet is discarded and an ERPDU can be sent.
The following example shows how to allow CLNS to send an error PDU when it detects an error in a data PDU:
interface ethernet 0
clns send-erpdu
You can use the master indexes or search online for documentation of related commands.
Use the clns send-rdpdu interface configuration command to allow CLNS to send redirect PDUs (RPDUs) when a better route for a given host is known. Use the no form of this command to disable this function.
clns send-rdpduThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
If a packet is sent out the same interface it came in on, an RDPDU can also be sent to the sender of the packet.
The following example shows how to allow CLNS to send RPDUs:
interface ethernet 0
clns send-rdpdu
You can use the master indexes or search online for documentation of related commands.
Use the clns split-horizon interface configuration command to implement split horizon for ISO-IGRP updates. Use the no form of this command to disable this feature.
clns split-horizonThis command has no arguments or keywords.
For all LAN interfaces—enabled
For WAN interfaces on X.25, Frame Relay, or SMDS networks—disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Normally, routers that are connected to broadcast-type OSI networks and that use distance vector routing protocols employ the split-horizon mechanism to prevent routing loops. Split-horizon blocks information about routes from being advertised by a router out any interface from which that information originated. This behavior usually optimizes communications among multiple routers, particularly when links are broken. However, with nonbroadcast networks, such as Frame Relay and SMDS, situations can arise for which this behavior is less than ideal. For all interfaces except those for which either Frame Relay or SMDS encapsulation is enabled, the default condition for this command is for split horizon to be enabled.
If your configuration includes either the encapsulation frame-relay or encapsulation smds interface configuration commands, the default is for split horizon to be disabled. Split horizon is not disabled by default for interfaces using any of the X.25 encapsulations.
For networks that include links over X.25 PSNs, the neighbor interface configuration command can be used to defeat the split horizon feature. You can as an alternative explicitly specify the no clns split-horizon command in your configuration. However, if you do so, you must similarly disable split horizon for all routers in any relevant multicast groups on that network.
Split horizon for ISO IGRP defaults to off for X.25, SMDS, and Frame Relay. Thereby, destinations are advertised out the interface for which the router has a destination.
In general, changing the state of the default for this interface configuration command is not recommended, unless you are certain that your application requires making a change in order to properly advertise routes. Remember that if split horizon is disabled on a serial interface (and that interface is attached to a packet-switched network), you must disable split horizon for all routers in any relevant multicast groups on that network.
In the following example, split horizon is disabled on a serial link connected to an X.25 network:
interface serial 0
encapsulation x25
no clns split-horizon
Use one or more clns template-alias global configuration commands to build a list of alphanumeric aliases of CLNS address templates for use in the definition of CLNS filter sets. Use the no form of this command to delete the alias.
clns template-alias name template
name | Alphanumeric name to apply as an alias for the template. |
template | Address template, as defined in the "Usage Guidelines" section. |
No alias list is defined.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Address templates are "pattern forms" that match one or more CLNS addresses. They can be simple single CLNS addresses, which match just themselves, or contain wildcards, prefixes, and suffixes, allowing a single template to match many addresses.
The simplest address template matches just a single address, as shown in this example:
47.0005.1234.5678.9abc.def0.00
Wildcard digits, which can match any value, are indicated with asterisks (*). The following template matches the above address and any other 12-byte long address that starts with 47.0005.1234.5678:
47.0005.1234.5678.****.****.**
Because OSI addresses are variable in length, it is often useful to build templates that match addresses that share a common prefix. The following template matches any address of any length that begins with the prefix 47.0005.1234.5678:
47.0005.1234.5678...
In other instances, matching a suffix of the address is also important, such as when matching system IDs. The following template matches any address that ends with the suffix 0000.0c01.2345.00:
...0000.0c01.2345.00
In other cases, you might want to match addresses on a single-bit granularity, rather than half-byte (four-bit, or nibble) granularity. This pattern matching is supported by allowing the hex digits that represent four bits to be replaced by groups of four binary bits, represented by 0s and 1s. These four binary digits are enclosed within parentheses. The following template matches any address that starts with 47.0005 followed by the binary bits 10. The final two binary bits in the nibble can be either 0 or 1, and are represented with asterisks.
47.0005.(10**)...
Use this command to define aliases for commonly referenced address templates. The use of these aliases reduces the chances for typographical error in the creation of CLNS filter sets.
The following command defines a filter set called COMPLEX-PREFIX for the last example given in the "Usage Guidelines" section:
clns template-alias COMPLEX-PREFIX 47.0005.(10**)...
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns filter-set
Use the clns want-erpdu global configuration command to specify whether to request ERPDUs on packets sourced by the router. Use the no form of this command to remove the parameter's settings.
clns want-erpduThis command has no arguments or keywords.
To request ERPDUs
Global configuration
This command first appeared in Cisco IOS Release 10.0.
This command has no effect on routing packets (ES-IS, ISO IGRP, and IS-IS) sourced by the system. It applies to pings and trace route packets.
The following example requests EPDUs on packets sourced by the router:
clns want-erpdu
You can use the master indexes or search online for documentation of related commands.
Use the distance router configuration command to configure the administrative distance for CLNS routes learned. Use the no form of this command to restore the administrative distance to the default.
distance value [clns]
value | Administrative distance, indicating the trustworthiness of a routing information source. This argument has a numerical value between 0 and 255. A higher relative value indicates a lower trustworthiness rating. Preference is given to routes with smaller values. The default, if unspecified, is 110. |
clns | (Optional) CLNS-derived routes for IS-IS. |
Static routes—10
ISO IGRP routes—100
IS-IS routes—110
Router configuration
This command first appeared in Cisco IOS Release 10.0.
When multiple routing processes are running in the same router for CLNS, it is possible for the same route to be advertised by more than one routing process. The Cisco IOS software always picks the route whose routing protocol has the lowest administrative distance.
The show clns protocol EXEC command displays the default administrative distance for a specified routing process.
In the following example, the distance value for CLNS routes learned is 90. Preference is given to these CLNS routes rather than routes with the default administrative distance value of 110.
router isis
distance 90 clns
Use the domain-password router configuration command to configure the routing domain authentication password. Use the no form of this command to disable the password.
domain-password password
password | Password you assign. |
No routing domain authentication password is set.
Router configuration
This command first appeared in Cisco IOS Release 10.0.
This password is inserted in Level 2 (area router level) link-state PDUs, CSNPs, and PSNPs.
The following example assigns an authentication password to the routing domain:
router isis
domain-password flower
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
Purge corrupt link-state packets causing initiator to regenerate link-state packet.
Router configuration
This command first appeared in Cisco IOS Release 11.1.
The IS-IS protocol definition requires that a received link-state packet 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 link-state packets with correct data link checksums, a continuous cycle of purging and regenerating large numbers of packets can occur. Because this could render the network nonfunctional, use the ignore-lsp-errors to ignore these link-state packets rather than purge the packets.
Link-state packets are used by the receiving routers to maintain their routing tables.
The following example instructs the router to ignore link-state packets that have internal checksum errors:
router isis
ignore-lsp-errors
Use the ip domain-lookup nsap global configuration command to allow Domain Naming System (DNS) queries for CLNS addresses. Use the no form of this command to disable this feature.
ip domain-lookup nsapThis command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
With both IP and ISO CLNS enabled on a router, this feature allows you to discover a CLNS address without having to specify a full CLNS address. This feature is useful for the ISO CLNS ping EXEC command and when making Telnet connections.
The following example disables DNS queries of CLNS addresses:
no ip domain-lookup nsap
You can use the master indexes or search online for documentation of related commands.
ip domain-lookup
ping (privileged)
ping (user)
Use the isis adjacency-filter interface configuration command to filter the establishment of IS-IS adjacencies. Use the no form of this command to disable filtering of the establishment of IS-IS adjacencies.
isis adjacency-filter name [match-all]
name | Name of the filter set or expression to apply. |
match-all | (Optional) All NSAP addresses must match the filter in order to accept the adjacency. If not specified (the default), only one address need match the filter in order for the adjacency to be accepted. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Filtering is performed by building NSAP addresses out of incoming IS-IS hello packets by combining each area address in the hello with the system ID. Each of these NSAP addresses is then passed through the filter. If any one NSAP matches, the filter is considered "passed," unless match-all was specified, in which case all addresses must pass. The functionality of the match-all keyword is useful in performing "negative tests," such as accepting an adjacency only if a particular address is not present.
Filtering is performed on full NSAP addresses. If filtering should only be performed on system IDs, or any other substring of the full NSAP address, the wildcard matching capabilities of filter sets should be used to ignore the insignificant portions of the NSAP addresses.
Filter sets and expressions are described in this manual in the descriptions for the clns filter-expr, clns filter-set, and clns template-alias global configuration commands.
The following example builds a filter which accepts adjacencies with only two systems, based only on their system IDs:
clns filter-set ourfriends...0000.0c00.1234.**
clns filter-set ourfriends...0000.0c00.125a.**
!
interface ethernet 0
isis adjacency-filter ourfriends
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns filter-set
clns template-alias
Use the isis circuit-type interface configuration command to configure the type of adjacency desired for the specified interface. Use the no form of this command to reset the circuit type to Level l and Level 2.
isis circuit-type {level-1 | level-1-2 | level-2-only}
level-1 | Level 1 adjacency is established if there is at least one area address in common between this system and its neighbors. |
level-1-2 | Level 1 and 2 adjacency is established if the neighbor is also configured as level-1-2 and there is at least one area in common. If there is no area in common, a Level 2 adjacency is established. This is the default. |
level-2-only | Level 2 adjacency is established on the circuit. If the neighboring router is a Level 1 only router, no adjacency is established. |
Level 1 and 2 adjacency is established.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
It is normally not necessary to configure this feature because the IS-IS protocol automatically determines area boundaries and keeps Level 1 and Level 2 routing separate. Indiscriminate use of this feature may cause incorrect operation, such as routing loops brought on by an accidental partitioning of a Level 1 area.
In the following example, a router is configured to allow only a Level 1 adjacency. If there are no area addresses in common between this system and its neighbors, no adjacency will be formed.
clns router isis
interface serial 0
isis circuit-type level-1
Use the isis csnp-interval interface configuration command to configure the IS-IS CSNP interval for the specified interface. Use the no form of this command to restore the default value.
isis csnp-interval seconds {level-1 | level-2}
seconds | Interval of time in seconds between transmission of CSNPs on multiaccess networks. (Only applies for the designated router.) The default is 10 seconds. |
level-1 | Interval of time between transmission of CSNPs for Level 1 independently. |
level-2 | Interval of time between transmission of CSNPs for Level 2 independently. |
10 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command only applies to the designated router for a specified interface. Only designated routers send CSNP packets in order to maintain database synchronization. The CSNP interval can be configured independently for Level 1 and Level 2. This feature does not apply to serial point-to-point interfaces. It does apply to WAN connections if the WAN is viewed as a multiaccess meshed network.
In the following example, serial interface 0 is configured for transmitting CSNPs every 5 seconds. The router is configured to act as a station router.
interface serial 0
isis csnp-interval 5 level-1
Use the isis hello-interval interface configuration command to specify the length of time in seconds between hello packets that the Cisco IOS software sends on the specified interface. Use the no form of this command to restore the default value.
isis hello-interval seconds {level-1 | level-2}
seconds | Unsigned integer value. A value three times the hello interval seconds is advertised as the holdtime in the hello packets transmitted. It must be the same for all routers attached to a common network. With smaller hello intervals, topological changes are detected faster, but there is more routing traffic. The default is 10 seconds. |
level-1 | Configure the hello interval for Level 1 independently. Use this on X.25, SMDS, and Frame Relay multiaccess networks. |
level-2 | Configure the hello interval for Level 2 independently. Use with X.25, SMDS, and Frame Relay multiaccess networks. |
10 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The hello interval can be configured independently for Level 1 and Level 2, except on serial point-to-point interfaces. (Because there is only a single type of hello packet sent on serial links, it is independent of Level 1 or Level 2.) The level-1 and level-2 keywords are used on X.25, SMDS, and Frame Relay multiaccess networks.
In the following example, serial interface 0 is configured to advertise hello packets every 5 seconds. The router is configured to act as a station router. This causes more traffic than configuring a longer interval, but topological changes will be detected faster.
interface serial 0
isis Hello-interval 5 level-1
You can use the master indexes or search online for documentation of related commands.
multiplier | Number from 3 to 1000. The seconds specified by the isis hello-interval command are multiplied by the number specified for the isis hello-multiplier command to determine the holding time transmitted in the IS-IS hello packet. If this command is not used, the default multiplier is 3. |
level-1 | (Optional) Configure the multiplier for Level 1 independently. The default is Level 1. |
level-2 | (Optional) Configure the multiplier for Level 2 independently. |
The default hello multiplier is 3 for Level 1 and Level 2.
Interface configuration
This command first appeared in Cisco IOS Release 11.1
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 isis 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 (isis hello-interval command) correspondingly to make the hello protocol more reliable without increasing the time required to detect a link failure.
In the following example, serial interface 0 is configured to advertise hello packets every 15 seconds and the multiplier is 5. This causes the hello packet holding time to be 75 seconds.
interface serial 0
isis hello-interval 15 level-2
isis hello-multiplier 5 level-2
Use the isis metric interface configuration command to configure the metric (or cost) for the specified interface. Use the no form of this command to restore the default metric value.
isis metric default-metric {level-1 | level-2}
default-metric | Metric used for the redistributed route. The range is 0 to 63. The default value is 10. |
level-1 | The router acts as a station router (Level 1) only. |
level-2 | The router acts as an area router (Level 2) only. |
Default metric = 10
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The default-metric is used as a value for the IS-IS metric. This is the value assigned when there is no quality-of-service (QOS) routing performed. Only this metric is supported by Cisco routers. You can configure this metric for Level 1 or Level 2 routing.
Specifying the level-1 or level-2 keywords resets the metric only for Level 1 or Level 2 routing, respectively.
In the following example, serial interface 0 is configured for a default link-state metric cost of 15 for Level 1:
interface serial 0
isis metric 15 level-1
Use the isis password interface configuration command to configure the authentication password for a specified interface. Use the no form of this command to disable authentication for IS-IS.
isis password password {level-1 | level-2}
password | Authentication password you assign for an interface. |
level-1 | Configure the authentication password for Level 1 independently. For Level 1 routing, the router acts as a station router only. |
level-2 | Configure the authentication password for Level 2 independently. For Level 2 routing, the router acts as an area router only. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Different passwords can be assigned for different routing levels using the level-1 and level-2 keywords.
Specifying the level-1 or level-2 keywords disables the password only for Level 1 or Level 2 routing, respectively. If no keyword is specified, the default is level-1.
The following example configures a password for serial interface 0 at Level 1:
interface serial 0
isis password frank level-1
Use the isis priority interface configuration command to configure the priority of this system for designated router election. Use the no form of this command to reset priority to 64.
isis priority value {level-1 | level-2}
value | Priority of a router; a number from 0 to 127. The default is 64. |
level-1 | Set priority for Level 1 independently. |
level-2 | Set priority for Level 2 independently. |
Priority of 64
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Priorities can be configured for Level 1 and Level 2 independently. Specifying the level-1 or
level-2 keywords resets priority only for Level 1 or Level 2 routing, respectively.
The following example sets the Level 1 priority level to 50:
interface serial 0
isis priority 50 level-1
Use the isis retransmit-interval interface configuration command to configure the number of seconds between retransmission of IS-IS link-state PDU retransmission for point-to-point links. Use the no form of this command to restore the default value.
isis retransmit-interval seconds
seconds | Integer that should be greater than the expected round-trip delay between any two routers on the attached network. The setting of this parameter should be conservative, or needless retransmission will result. The value should be larger for serial lines and virtual links. The default value is 5 seconds. |
5 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example configures serial interface 0 for retransmission of IS-IS link-state PDU every 10 seconds for a large serial line:
interface serial 0
isis retransmit-interval 10
Use the iso-igrp adjacency-filter interface configuration command to filter the establishment of ISO IGRP adjacencies. Use the no form of this command to disable filtering of the establishment of ISO IGRP adjacencies.
iso-igrp adjacency-filter name
name | Name of the filter set or expression to apply. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Filtering is performed on full NSAP addresses. If filtering should only be performed on system IDs, or any other substring of the full NSAP address, the wildcard matching capabilities of filter sets should be used to ignore the insignificant portions of the NSAP addresses.
For descriptions of filter sets and expressions, refer to the clns filter-expr, clns filter-set, and clns template-alias global configuration commands in this chapter.
The following example builds a filter that accepts adjacencies with only two systems, based only on their system IDs:
clns filter-set ourfriends...0000.0c00.1234.**
clns filter-set ourfriends...0000.0c00.125a.**
!
interface ethernet 0
iso-igrp adjacency-filter ourfriends
You can use the master indexes or search online for documentation of related commands.
clns filter-expr
clns filter-set
clns template-alias
Use the is-type router configuration command to configure the IS-IS level at which the Cisco IOS software is to operate. Use the no form of this command to reset the parameter to the default.
is-type {level-1 | level-1-2 | level-2-only}
level-1 | Causes the router to act as a station router. |
level-1-2 | Causes the router to act as both a station router and an area router. |
level-2-only | Causes the router to act as an area router only. |
The router acts as both a station router and an area router.
Router configuration
This command first appeared in Cisco IOS Release 10.3.
It is normally not necessary to configure this feature because the IS-IS protocol automatically determines area boundaries and keeps Level 1 and Level 2 routing separate. Indiscriminate use of this feature may cause incorrect operation, such as routing loops brought on by an accidental partitioning of a Level 1 area.
The following example specifies a router as capable of being used as an area router only:
clns routing
router isis area1
net 47.0004.004d.0001.0000.0c11.1111.00
is-type level-2-only
This command has no arguments or keywords.
Does not log adjacency changes.
Router configuration
This command first appeared in Cisco IOS Release 11.1.
This command allows the monitoring of IS-IS adjacency state changes. This may be very useful when monitoring large networks. Messages are logged using the system error message facility. Messages are of the form:
%CLNS-5-ADJCHANGE: ISIS: Adjacency to 0000.0000.0034 (Serial0) Up, new adjacency
%CLNS-5-ADJCHANGE: ISIS: Adjacency to 0000.0000.0034 (Serial0) Down, hold time expired
The following example instructs the router to log adjacency changes:
router isis
log-adjacency-changes
You can use the master indexes or search online for documentation of related commands.
logging
size | Maximum packet size in bytes. The size must be less than or equal to the smallest MTU of any link in the network. The default size is 1497 bytes. |
1497 bytes
Router configuration
This command first appeared in Cisco IOS Release 10.3.
Under normal conditions, the default MTU size should be sufficient. However, if the MTU of a link is below 1500 bytes, the link-state packet MTU must be lowered accordingly on each router in the network. If this is not done, routing becomes unpredictable.
 | Caution The CLNS MTU of a link (which is the applicable value for IS-IS, even if it is being used to route IP) may differ from the IP MTU. To be certain about a link MTU as it pertains to IS-IS, use the show clns interface command to display the value. |
The following example sets the MTU size to 1300 bytes:
router isis
lsp-mtu 1300
You can use the master indexes or search online for documentation of related commands.
mtu
clns mtu
name | Name of a standard access list, filter set, or expression. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
name | Name of an access list, filter set, or expression. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
Use the match clns route-source route-map configuration command to define the route-source match criterion; routes that have been advertised by routers at the address specified by the name—and that satisfy all other defined match criteria—will be redistributed. Use the no form of this command to remove the specified match criterion.
match clns route-source name [name...name]
name | Name of access list, filter set, or expression. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
type | Interface type. |
number | Interface number. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
Use the match metric route-map configuration command to define the metric match criterion; routes that have the specified metric—and satisfy all other defined match criteria—will be redistributed. Use the no form of this command to remove the specified match criterion.
match metric metric-value
metric-value | Route metric. This can be an Interior Gateway Routing Protocol (IGRP) five-part metric. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
Use the match route-type route-map configuration command to define the route-type match criterion; routes that have the specified route type—and satisfy all other defined match criteria—will be redistributed. Use the no form of this command to remove the specified match criterion.
match route-type {level-1 | level-2}
level-1 | IS-IS Level 1 routes. |
level-2 | IS-IS Level 2 routes. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all defined match criteria must be satisfied to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You can use the master indexes or search online for documentation of related commands.
redistribute
route-map
set level
Use the metric weights router configuration command to specify different metrics for the ISO IGRP routing protocol on CLNS. This command allows you to configure the metric constants used in the ISO IGRP composite metric calculation of reliability and load. Use the no form of this command to return the five k constants to their default values.
metric weights qos k1 k2 k3 k4 k5
qos | QOS defines transmission quality and availability of service. The argument must be 0, the default metric. |
k1, k2, k3, k4, k5 | Values that apply to ISO IGRP for the default metric QOS. The k values are metric constants used in the ISO IGRP equation that converts an IGRP metric vector into a scalar quantity. They are numbers from 0 to 127; higher numbers mean a greater multiplier effect. |
qos = 0
k1 = 1
k2 = 0
k3 = 1
k4 = 0
k5 = 0
Router configuration
This command first appeared in Cisco IOS Release 10.0.
Two additional ISO IGRP metrics can be configured. These are the bandwidth and delay associated with an interface.
By default, the IGRP composite metric is a 24-bit quantity that is a sum of the segment delays and the lowest segment bandwidth (scaled and inverted) for a given route. For a network of homogeneous media, this metric reduces to a hop count. For a network of mixed media (FDDI, Ethernet, and serial lines running from 9,600 bps to T1 rates), the route with the lowest metric reflects the most desirable path to a destination.
Use this command to alter the default behavior of IGRP routing and metric computation and allow the tuning of the IGRP metric calculation for QOS.
If k5 equals 0, the composite IGRP metric is computed according to the following formula:
metric = [K1 * bandwidth + (K2 * bandwidth) / (256 - load) + K3 * delay]
If k5 does not equal zero, the following additional operation is done:
metric = metric * [K5 / (reliability + K4)]
The default version of IGRP has both k1 and k3 equal to 1, and k2, k4, and k5 equal to 0.
Delay is in units of 10 microseconds. This gives a range of 10 microseconds to 168 seconds. A delay of all ones indicates that the network is unreachable.
Bandwidth is inverse minimum bandwidth of the path in bits per second scaled by a factor of 10e10. The range is 1200 bps to 10 Gbps.
Table 32 lists the default values used for several common media.
| Media Type | Delay | Bandwidth |
|---|---|---|
Satellite | 200,000 (2 sec) | 20 (500 Mbit) |
Ethernet | 100 (1 ms) | 1,000 |
1.544 Mbps | 2000 (20 ms) | 6,476 |
64 kbps | 2000 | 156,250 |
56 kbps | 2000 | 178,571 |
10 kbps | 2000 | 1,000,000 |
1 kbps | 2000 | 10,000,000 |
Reliability is given as a fraction of 255. That is, 255 is 100 percent reliability or a perfectly stable link. Load is given as a fraction of 255. A load of 255 indicates a completely saturated link.
In the following example, all five metric constants are set:
router iso-igrp
metric weights 0 2 0 1 0 0
You can use the master indexes or search online for documentation of related commands.
bandwidth
delay
Use the net router configuration command to configure an NET for the specified routing process. The no form of this command removes the specified NET.
net network-entity-title
network-entity-title | Area addresses for the ISO IGRP or IS-IS area. |
No NET is specified for any specific routing process.
Router configuration
This command first appeared in Cisco IOS Release 10.0.
For IS-IS, multiple NETs per router are allowed, with a maximum of three. There is no default value for this command.
Although IS-IS allows you to configure multiple NETs, ISO IGRP allows only one NET per routing process.
The net router configuration command allows you to specify a name for an NET, as well as an address.
The following example specifies an NET for ISO IGRP:
router iso-igrp Finance
net 47.0004.004d.0001.0000.0c11.1111.00
The following example specifies a single NET for IS-IS:
router isis Pieinthesky
net 47.0004.004d.0001.0000.0c11.1111.00
Use the ISO CLNS ping privileged EXEC command to send ISO CLNS echo packets to test the reachability of a remote router over a connectionless OSI network. The ping command sends an echo request packet to an address, then awaits a reply. Ping output can help you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is functioning.
ping clns {host | address}
clns | CLNS protocol. |
host | Host name of system to ping. |
address | Address of system to ping. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The OSI Connectionless Network Protocol (ISO 8473) does not specify a network-level echo protocol. The Internet Engineering Task Force (IETF) has specified and proposed such a protocol in RFC 1139. Cisco has implemented this specification using the proposed new PDU types Echo Request (1E) and Echo Reply (1F). Non-Cisco routers may or may not forward these packets, depending on whether they are specific about the packet types they will forward. End systems may not recognize these packets, but will typically generate an error packet (ERPDU) as a response. This ERPDU is useful, as it confirms the reachability of the end system.
To abort a ping session, type the escape sequence (by default, Ctrl-^ X, which is done by simultaneously pressing the Ctrl, Shift, and 6 keys, letting go, then pressing the X key).
Table 33 describes the test characters that the ping facility sends.
| Character | Description |
|---|---|
! | Each exclamation point indicates receipt of a reply. |
. | Each period indicates the network server timed out while waiting for a reply. |
U | A destination unreachable error PDU was received. |
C | A congestion experienced packet was received. |
I | User interrupted test. |
? | Unknown packet type. |
& | Packet lifetime exceeded. |
The following display shows a sample ISO CLNS ping session that uses a name to specify the source:
router# ping
Protocol [ip]: clns
Target CLNS address: thoth
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Source CLNS address [39.000f.aa00.0400.013c.00]:
Type escape sequence to abort.
Sending 5, 100-byte CLNS Echos to
55.0006.0100.0000.0000.0001.8888.1112.1314.151
6.00, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 112/113/116 ms
The following display shows a sample ISO CLNS ping session that uses a NET address to specify the source:
router# ping
Protocol [ip]: clns
Target CLNS address: 47.0004.0050.0002.0000.0c00.243b.00
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Source CLNS address [39.000f.aa00.0400.013c.00]:
Type escape sequence to abort.
Sending 5, 100-byte CLNS Echos to 47.0004.0050.0002.0000.0C00.243B.00,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/4/8 ms
Table 34 describes the fields shown in the display.
| Field | Description |
|---|---|
Protocol [ip]: | Default is IP. Enter clns. |
Target CLNS address: | Prompts for the CLNS address or host name of the destination node you plan to ping. |
Repeat count [5]: | Number of ping packets that will be sent to the destination address. Default: 5. |
Datagram size [100]: | Size of the ping packet (in bytes). Default: 100 bytes. |
Timeout in seconds [2]: | Timeout interval. Default: 2 (seconds). |
Source address: | Address that appears in the ping packet as the source address. |
If you have both ISO CLNS and IP enabled, you can use the DNS to query ISO CLNS addresses through use of the "NSAP" type.
For example, suppose your DNS entries look something like the following:
finance.cisco.comIN A 1.2.3.4
marketing.cisco.comIN NSAP
47.0005.80.FEFF00.0000.0001.0001.1b2a.0000.0c1a.1bff.00
baz.cisco.comIN A 1.2.3.5
IN NSAP
47.0005.80.FEFF00.0000.0001.0001.1b2a.0000.0c1a.1b2c.00
Based on the these entries, the following examples will produce the results as indicated:
router# ping finance.cisco.com
! this will do an IP style ping
router# ping marketing.cisco.com
! this will do a CLNS style ping (since only a NSAP entry appears)
Router# ping baz.cisco.com
! this will do an IP style ping (prefers IP if it can get it)
Router# ping
Protocol [ip]: clns
Target CLNS address: baz.cisco.com
! this will do a CLNS ping the NSAP for baz.cisco.com
You can use the master indexes or search online for documentation of related commands.
clns | CLNS protocol. |
host | Host name of system to ping. |
address | Address of system to ping. |
User EXEC
This command first appeared in Cisco IOS Release 10.0.
The OSI Connectionless Network Protocol (ISO 8473) does not specify a network-level echo protocol. The Internet Engineering Task Force (IETF) has specified and proposed such a protocol in RFC 1139. Cisco has implemented this specification using the proposed new PDU types Echo Request (1E) and Echo Reply (1F). Non-Cisco routers may or may not forward these packets, depending on whether they are specific about the packet types they will forward. End systems may not recognize these packets, but will typically generate an error packet (ERPDU) as a response. This ERPDU is useful, as it confirms the reachability of the end system.
The user ping feature provides a basic ping facility for CLNS users who do not have system privileges. This feature allows the Cisco IOS software to perform the simple default ping functionality for the CLNS protocol. Only the nonverbose form of the ping command is supported for user pings.
If the system cannot map an address for a host name, it returns an "%Unrecognized host or address" error message. To abort a ping session, type the escape sequence (by default, Ctrl-^ X, which is done by simultaneously pressing the Ctrl, Shift, and 6 keys, letting go, then pressing the X key).
Table 35 describes the test characters that the ping facility sends.
| Character | Description |
|---|---|
! | Each exclamation point indicates receipt of a reply. |
. | Each period indicates the network server timed out while waiting for a reply. |
U | A destination unreachable error PDU was received. |
C | A congestion experienced packet was received. |
I | User interrupted test. |
? | Unknown packet type. |
& | Packet lifetime exceeded. |
The following display shows sample ping output when you ping the CLNS address 47.0004.0050.0002.0000.0c00.243b.00:
router> ping clns 47.0004.0050.0002.0000.0c00.243b.00
Sending 5, 100-byte CLNS Echos to 47.0004.0050.0002.0000.0C00.243B.00,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/4/8 ms
You can use the master indexes or search online for documentation of related commands.
Use the redistribute router configuration command to redistribute routing information from one domain into another routing domain. Use the no form of this command to disable redistribution, or to disable any of the specified keywords.
redistribute protocol [tag] [route-map map-tag]
protocol | Type of other routing protocol that is to be redistributed as a source of routes into the current routing protocol being configured. The keywords supported are iso-igrp, isis, and static. |
tag | (Optional) Meaningful name for a routing process. |
route-map map-tag | (Optional) Route map should be interrogated to filter the importation of routes from this source routing protocol to the current routing protocol. If not specified, all routes are redistributed. If this keyword is specified, but no route map tags are listed, no routes will be imported. The argument map-tag is the identifier of a configured route map. |
static | Keyword static is used to redistribute static routes. When used without the optional keywords, this causes the Cisco IOS software to inject any OSI static routes into an OSI domain. |
clns | (Optional) Keyword clns is used when redistributing OSI static routes into an IS-IS domain. |
ip | (Optional) Keyword ip is used when redistributing IP into an IS-IS domain. |
Disabled, except for static routes, which by default are redistributed into IS-IS routing domains but are not redistributed into ISO IGRP domains. The keyword clns is the default with the keyword static.
Router configuration
This command first appeared in Cisco IOS Release 10.0.
When used with IS-IS, the redistribute command causes the routes learned by the routing process tag to be advertised in the IS-IS routing process. Static routes are always redistributed into IS-IS unless a no redistribute static is performed. Redistribution only occurs for Level 2 routing.
You can specify only one IS-IS process per router. Creating a name for a routing process means that you use names when configuring routing. If the tag argument is not specified, a null tag is assumed. It must be unique among all CLNS router processes for a given router.
When used with ISO IGRP, if you have a router that is in two routing domains, you might want to redistribute routing information between the two domains. The redistribute router configuration command configures which routes are redistributed into the ISO IGRP domain. It is not necessary to use redistribution between areas.
The tag argument must be unique among all CLNS router processes for a given router. This tag should be the same as defined for the routing process in the router iso-igrp global configuration command.
Static routes are only redistributed into ISO IGRP when a redistribute static command is entered. The default is to not redistribute static routes into ISO IGRP. Only the router that injects the static route needs to have a redistribute static command defined. This command is needed only when you run ISO IGRP.
The following example illustrates redistribution of ISO IGRP routes of Michigan and ISO IGRP routes of Ohio into the IS-IS area tagged USA:
router isis USA
redistribute iso-igrp Michigan
redistribute iso-igrp Ohio
The following example illustrates redistribution of IS-IS routes of France and ISO IGRP routes of Germany into the ISO IGRP area tagged Backbone:
router iso-igrp Backbone
redistribute isis France
redistribute iso-igrp Germany
In the following example, the router advertises any static routes it knows about in the Chicago domain:
router iso-igrp Chicago
redistribute static
You can use the master indexes or search online for documentation of related commands.
Use the route-map global configuration command to define the conditions for redistributing routes from one routing protocol into another. Use the no form of this command to delete the route map.
route-map map-tag {permit | deny} sequence-number
map-tag | Meaningful name for the route map. The redistribute command uses this name to reference this route map. Multiple route-maps can share the same map tag name. Can either be an expression or a filter set. |
permit | If the match criteria are met for this route map, and permit is specified, the route is redistributed as controlled by the set actions. If the match criteria are not met, and permit is specified, the next route map with the same map-tag is tested. If a route passes none of the match criteria for the set of route maps sharing the same name, it is not redistributed by that set. |
deny | If the match criteria are met for the route map, and deny is specified, the route is not redistributed, and no further route maps sharing the same map tag name will be examined. |
sequence-number | Number that indicates the position a new route map is to have in the list of route maps already configured with the same name. If given with the no form of this command, it specifies the position of the route map that should be deleted. |
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met.
You can use the master indexes or search online for documentation of related commands.
match clns address
redistribute
set level
Use the router isis global configuration command to enable the IS-IS routing protocol on your router and to configure the IS-IS routing process. This command identifies the area the router will work in and lets the router know that it will be routing dynamically rather than statically. Use the no form of this command with the appropriate tag to disable IS-IS routing for the system.
router isis [tag]
tag | (Optional) Meaningful name for a routing process. If it is not specified, a null tag is assumed. The argument tag must be unique among all CLNS router processes for a given router. The tag argument is used later as a reference to this process. |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Creating a name for a routing process means that you use names when configuring routing. You can specify only one IS-IS process per router. Only one IS-IS process is allowed, whether you run it in integrated mode, ISO CLNS, or IP only.
The following example starts IS-IS routing with the optional tag argument:
router isis Pieinthesky
You can use the master indexes or search online for documentation of related commands.
Use the router iso-igrp global configuration command to identify the area the router will work in and let it know that it will be routing dynamically using the ISO IGRP protocol. Use the no form of this command with the appropriate tag to disable ISO IGRP routing for the system.
router iso-igrp [tag]
tag | (Optional) Meaningful name for a routing process. For example, you could define a routing process named Finance for the Finance department, and another routing process named Marketing for the Marketing department. If not specified, a null tag is assumed. The tag argument must be unique among all CLNS router processes for a given router. |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 10.0.
Creating a name for a routing process means that you use names when configuring routing. You can specify up to ten ISO IGRP processes.
In the following example, a router is specified in Manufacturing. The command must be typed on one line.
router iso-igrp Manufacturing
You can use the master indexes or search online for documentation of related commands.
Use the set level route-map configuration command to specify the routing level of routes to be advertised into a specified area of the routing domain. Use the no form of this command to disable advertising the specified routing level into a specified area.
set level {level-1 | level-2 | level-1-2}
level | Redistributed routes are advertised into this specified area of the routing domain. For IS-IS destinations, the default value is level-2. |
level-1 | Inserted in IS-IS Level 1 link-state PDUs. |
level-2 | Inserted in IS-IS Level 2 link-state PDUs. |
level-1-2 | Inserted into both Level 1 and Level 2 IS-IS link-state PDUs. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the redistribution set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. When all match criteria are met, all set actions are performed. The no route-map command deletes the route map.
Given the following configuration, a RIP-learned route for network 160.89.0.0 and an ISO IGRP-learned route with prefix 49.0001.0002 will be redistributed into an IS-IS Level 2 link-state PDU with metric 5:
router isis
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
route-map ourmap permit
match ip address 1
match clns address ourprefix
set metric 5
set level level-2
access-list 1 permit 160.89.0.0 0.0.255.255
clns filter-set ourprefix permit 49.0001.0002...
You can use the master indexes or search online for documentation of related commands.
match clns address
redistribute
route-map
Use the set metric route-map configuration command to set the metric value to give the redistributed routes. Use the no form of this command to disable redistributing routes of a specific metric.
set metric metric-value
metric-value | Route metric. This can be an IGRP five-part metric. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the redistribution set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. When all match criteria are met, all set actions are performed. The no route-map command deletes the route map.
Given the following configuration, a RIP-learned route for network 160.89.0.0 and an ISO IGRP-learned route with prefix 49.0001.0002 will be redistributed into an IS-IS Level 2 link-state PDU with metric 5:
router isis
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
!
route-map ourmap permit
match ip address 1
match clns address ourprefix
set metric 5
set level level-2
!
access-list 1 permit 160.89.0.0 0.0.255.255
clns filter-set ourprefix permit 49.0001.0002...
You can use the master indexes or search online for documentation of related commands.
match clns address
redistribute
route-map
Use the set metric-type route-map configuration command to set the metric type to give redistributed routes. Use the no form of this command to disable redistributing routes of a specific metric type.
set metric-type {internal | external}
internal | IS-IS internal metric. |
external | IS-IS external metric. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the redistribution set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. When all match criteria are met, all set actions are performed. The no route-map command deletes the route map.
You can use the master indexes or search online for documentation of related commands.
match clns address
redistribute
route-map
Use the set tag route-map configuration command to set a tag value to associate with the redistributed routes. Use the no form of this command to disable redistributing routes with the specific tag.
set tag tag-value
tag-value | Name for the tag. The tag value to associate with the redistributed route. If not specified, the default action is to forward the tag in the source routing protocol onto the new destination protocol. |
Disabled
Route-map configuration
This command first appeared in Cisco IOS Release 10.0.
You can use the master indexes or search online for documentation of related commands.
match clns address
redistribute
route-map
Use the show clns EXEC command to display information about the CLNS network.
show clnsThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns command:
router# show clns
Global CLNS Information:
2 Interfaces Enabled for CLNS
NET: 39.0004.0030.0000.0C00.224D.00
NET: 39.0003.0020.0000.0C00.224D.00
Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64
ERPDU's requested on locally generated packets
Intermediate system operation enabled (forwarding allowed)
ISO IGRP level-1 Router: remote
Routing for Domain: 39.0003, Area: 0020
ISO IGRP level-2 Router: DOMAIN_remote
Routing for Domain: 39.0003
IS-IS level-1-2 Router:
Routing for Area: 39.0004.0030
Table 36 describes significant fields shown in the display.
| Field | Description |
|---|---|
2 Interfaces Enabled for CLNS | Indicates how many interfaces have the CLNS routing protocol enabled. |
NET: 39.0004.0030.0000.0C00.224D.00 | First of two NETs for this router. |
Configuration Timer: 60 | Displays the interval (in seconds) after which the router sends out IS hello packets. |
Default Holding Timer: 300 | Length of time (in seconds) hello packets are remembered. |
Packet Lifetime 64 | Default value used in packets sourced by this router. |
ERPDUs requested on locally generated packets | Indicates whether ERPDUs are requested for packets sourced by the router. |
Intermediate system operation enabled (forwarding allowed) | Indicates whether this router is configured to be an ES or an IS. |
ISO IGRP level-1 Router: remote | Specifies what CLNS routing type (ISO IGRP or IS-IS) and what routing level (Level 1, Level 2, or both) is enabled on the router. |
Routing for Domain: 39.0003, Area: 0020 | Specifies the domain (39.0003) and area (0020) for which this CLNS routing type and routing level is enabled. |
IS-IS level-1-2 Router: | Specifies that IS-IS is running in this router. Its tag is null. It is running Level 1 and Level 2. |
Routing for Area: 39.0004.0030 | Specifies the IS-IS area this router is in. |
Use the show clns cache EXEC command to display the CLNS routing cache. The cache contains an entry for each destination that has packet switching enabled. The output of this command includes entries showing each destination for which the router has switched a packet in the recent past. This includes the router itself.
show clns cache
delay-parameters | (Optional) Current settings for delays when entries are invalidated in the CLNS route cache. |
invalidations | (Optional) When specified, shows the last time each function purged the CLNS route cache. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns cache command:
Router# show clns cache
CLNS routing cache version 433
Destination -> Next hop @ Interface: SNPA Address => Rewrite / Length
[42] *39.0004.0040.0000.0C00.2D55.00 ISOLATOR
-> 0000.0C00.2D55 @ Serial2: 0000.0c00.6fa5
Table 37 describes significant fields shown in the display.
| Field | Description |
|---|---|
CLNS routing cache version 433 | Number identifying this particular CLNS routing cache. |
Destination -> | Destination NSAP for the packet. |
Next hop | Next hop system ID used to reach the destination. |
@ Interface: | Interface through which the router transmitted the packet. |
[42] | Cache location for this entry. |
*39.0004.0040.0000.0C00.2D55.001 | NSAP address. |
ISOLATOR | NSAP host name. |
Table 38 describes significant fields shown in the display.
| Field | Description |
|---|---|
Minimum invalidation interval | Minimum time (in seconds) between invalidation request and actual invalidation. |
Maximum Invalidation interval | Maximum time (in seconds) between invalidation request and actual invalidation. |
Quiet interval | Length of time (in seconds) before invalidation. |
Threshold | Maximum number of invalidations considered to be quiet. |
Invalidation rate | Number of invalidations (route cache purges) per second. |
The following is sample output from the show clns cache invalidations command:
Caller Count Last Invalidation
clns_fastsetup 3 20:55:56
clns_route_update 23 20:56:44
clns_route_adjust 2 20:55:52
isis_compute_spt 2017 00:10:13
delete_adjacency 9 1d19h
clns_ager 11 1d19h
Table 39 describes significant fields shown in the display.
| Field | Description |
|---|---|
Caller | Lists the names of the functions that have purged the CLNS route cache. |
Count | Number of times the function has invalidated the CLNS route cache. |
Last invalidation | The last time the function invalidated the CLNS route cache. |
You can use the master indexes or search online for documentation of related commands.
Use the show clns es-neighbors EXEC command to list the ES neighbors that this router knows about.
show clns es-neighbors [type number] [detail]
type | (Optional) Interface type. |
number | (Optional) Interface number. |
detail | (Optional) When specified, the areas associated with the end systems are displayed. Otherwise, a summary display is provided. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns es-neighbors command when Ethernet interface 0 is specified:
router# show clns es-neighbors
System Id Interface State Type Format
0800.2B14.060E Ethernet0 Up ES Phase V
0800.2B14.0528 Ethernet0 Up ES Phase V
Table 40 describes the significant fields shown in the display.
| Field | Descriptions |
|---|---|
System Id | Identification value of the system. |
Interface | Interface on which the router was discovered. |
State | Adjacency state. Up and Init are the states. See the show clns neighbors description. |
Type | Type of neighbor. Only valid value for the show clns es-neighbors EXEC command is ES. |
Format | Indicates if the neighbor is either a Phase V (OSI) adjacency or Phase IV (DECnet) adjacency. |
The following is sample output from the show clns es-neighbors detail command:
router# show clns es-neighbors detail
System Id Interface State Type Format
0800.2B14.060E Ethernet0 Up ES Phase V
Area Address(es): 49.0040
0800.2B14.0528 Ethernet0 Up ES Phase V
Area Address(es): 49.0040
Notice that the information displayed in show clns es-neighbors detail output includes everything shown in show clns es-neighbors output, but it also includes the area addresses associated with the ES neighbors.
You can use the master indexes or search online for documentation of related commands.
Use the show clns filter-expr EXEC command to display one or all currently defined CLNS filter expressions.
show clns filter-expr [name] [detail]
name | (Optional) Name of the filter expression to display. If none is specified, all are displayed. |
detail | (Optional) When specified, expressions are evaluated down to their most primitive filter set terms before being displayed. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following displays assume filter expressions have been defined with the following commands. FRED, BARNEY, WILMA, and BETTY are all filter sets.
clns filter-expr MEN FRED or BARNEY
clns filter-expr WOMEN WILMA or BETTY
clns filter-expr ADULTS MEN or WOMEN
The show clns filter-expr command would yield the following output:
router# show clns filter-expr
MEN = FRED or BARNEY
WOMEN = WILMA or BETTY
ADULTS = MEN or WOMEN
The show clns filter-expr detail command would yield the following output:
router# show clns filter-expr detail
MEN = FRED or BARNEY
WOMEN = WILMA or BETTY
ADULTS = (FRED or BARNEY) or (WILMA or BETTY)
You can use the master indexes or search online for documentation of related commands.
Use the show clns filter-set EXEC command to display one or all currently defined CLNS filter sets.
show clns filter-set [name]
name | (Optional) Name of the filter set to display. If none is specified, all are displayed. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following display assumes filter sets have been defined with the following commands:
clns filter-set US-OR-NORDUNET 47.0005...
clns filter-set US-OR-NORDUNET 47.0023...
clns filter-set LOCAL 49.0003...
The following is a sample output from the show clns filter-set command:
router# show clns filter-set
CLNS filter set US-OR-NORDUNET
permit 47.0005...
permit 47.0023...
CLNS filter set LOCAL
permit 49.0003...
You can use the master indexes or search online for documentation of related commands.
Use the show clns interface EXEC command to list the CLNS-specific information about each interface.
show clns interface [type number]
type | (Optional) Interface type. |
number | (Optional) Interface number. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns interface command that includes information for Token Ring and serial interfaces:
router# show clns interface
TokenRing 0 is administratively down, line protocol is down
CLNS protocol processing disabled
TokenRing 1 is up, line protocol is up
Checksums enabled, MTU 4461, Encapsulation SNAP
ERPDUs enabled, min. interval 10 msec.
RDPDUs enabled, min. interval 100 msec., Addr Mask enabled
Congestion Experienced bit set at 4 packets
CLNS fast switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 18 seconds
Routing Protocol: ISO IGRP
Routing Domain/Area: <39.0003> <0020>
Serial 2 is up, line protocol is up
Checksums enabled, MTU 1497, Encapsulation HDLC
ERPDUs enabled, min. interval 10 msec.
RDPDUs enabled, min. interval 100 msec., Addr Mask enabled
Congestion Experienced bit set at 4 packets
CLNS fast switching enabled
DEC compatibility mode OFF for this interface
CLNS cluster alias enabled on this interface
Next ESH/ISH in 48 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Level-1 Metric: 10, Priority: 64, Circuit ID: 0000.0C00.2D55.0A
Number of active level-1 adjacencies: 0
Level-2 Metric: 10, Priority: 64, Circuit ID: 0000.0000.0000.00
Number of active level-2 adjacencies: 0
Next IS-IS LAN Level-1 hello in 3 seconds
Next IS-IS LAN Level-2 hello in 3 seconds
Table 41 describes significant fields shown in the display.
| Field | Description |
|---|---|
TokenRing 0 is administratively down, line protocol is down | (First interface). Shown to be administratively down with CLNS disabled. |
TokenRing 1 is up, line protocol is up/ Serial 2 is up, line protocol is up | (Second, third interfaces). Shown to be up, and CLNS is up. |
Checksums enabled | Can be enabled or disabled. |
MTU | The number following MTU is the maximum transmission size for a packet on this interface. |
Encapsulation | Describes the encapsulation used by CLNP packets on this interface. |
ERPDUs | Displays information about the generation of ERPDUs. They can be either enabled or disabled. If they are enabled, they are sent out no more frequently than the specified interval. |
RDPDUs | Provides information about the generation of RDPDUs. They can be either enabled or disabled. If they are enabled, they are sent out no more frequently than the specified interval. If the address mask is enabled, redirects are sent out with an address mask. |
Congestion Experienced | Tells when CLNS will turn on the congestion experienced bit. The default is to turn this bit on when there are more than four packets in a queue. |
CLNS fast switching | Displays whether fast switching is supported for CLNS on this interface. |
DEC compatibility mode | Indicates whether DEC compatibility has been enabled. |
CLNS cluster alias enabled on this interface | Indicates that CLNS cluster aliasing has been enabled on this interface. |
Next ESH/ISH | Displays when the next ES hello or IS hello is sent on this interface. |
Routing Protocol | Lists the areas that this interface is in. In most cases, an interface will be in only one area. |
Circuit type | Indicates whether the interface has been configured for local routing (Level 1), area routing (Level 2), or local and area routing (Level 1-2). |
Remaining fields | Last series of fields displays information pertaining to the ISO CLNS routing protocols enabled on the interface. For ISO IGRP, the routing domain and area addresses are specified. For IS-IS, the Level 1 and Level 2 metrics, priorities, Circuit IDs, and number of active Level 1 and Level 2 adjacencies are specified. |
Use the show clns is-neighbors EXEC command to display IS-IS related information for IS-IS router adjacencies. Neighbor entries are sorted according to the area in which they are located.
show clns is-neighbors [type number] [detail]
type | (Optional) Interface type. |
number | (Optional) Interface number. |
detail | (Optional) When specified, the areas associated with the intermediate systems are displayed. Otherwise, a summary display is provided. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns is-neighbors command:
router# show clns is-neighbors
System Id Interface State Type Priority Circuit Id Format
0000.0C00.0C35 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V
0800.2B16.24EA Ethernet0 Up L1L2 64/64 0800.2B16.24EA.01 Phase V
0000.0C00.3E51 Serial1 Up L2 0 04 Phase V
0000.0C00.62E6 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V
Table 42 describes significant fields shown in the display.
| Field | Descriptions |
|---|---|
System Id | Identification value of the system. |
Interface | Interface on which the router was discovered. |
State | Adjacency state. Up and Init are the states. See the show clns neighbors description. |
Type | L1, L2, and L1L2 type adjacencies. See the show clns neighbors description. |
Priority | IS-IS priority that the respective neighbor is advertising. The highest priority neighbor is elected the designated IS-IS router for the interface. |
Circuit Id | Neighbor's idea of what the designated IS-IS router is for the interface. |
Format | Indicates if the neighbor is either a Phase V (OSI) adjacency or Phase IV (DECnet) adjacency. |
The following is sample output from the show clns is-neighbors detail command:
router# show clns is-neighbors detail
System Id Interface State Type Priority Circuit Id Format
0000.0C00.0C35 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V
Area Address(es): 47.0004.004D.0001 39.0001
Uptime: 0:03:35
0800.2B16.24EA Ethernet0 Up L1L2 64/64 0800.2B16.24EA.01 Phase V
Area Address(es): 47.0004.004D.0001
Uptime: 0:03:35
0000.0C00.3E51 Serial1 Up L2 0 04 Phase V
Area Address(es): 39.0004
Uptime: 0:03:35
000.0C00.62E6 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V
Area Address(es): 47.0004.004D.0001
Uptime: 0:03:35
Notice that the information displayed in show clns is-neighbors detail output includes everything shown in show clns is-neighbors output, but it also includes the area addresses associated with the IS neighbors (intermediate-system adjacencies) and how long (uptime) the adjacency has existed.
You can use the master indexes or search online for documentation of related commands.
Use the show clns neighbors EXEC command to display both ES and IS neighbors.
show clns neighbors [type number] [detail]
area | (Optional) When specified, the CLNS multiarea adjacencies are displayed. |
type | (Optional) Interface type. |
number | (Optional) Interface number. |
detail | (Optional) When specified, the area addresses advertised by the neighbor in the hello messages is displayed. Otherwise, a summary display is provided. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns neighbors command. This display is a composite of the show clns es-neighbor and show clns is-neighbor commands.
router# show clns neighbors
System Id Interface SNPA State Holdtime Type Protocol
0000.0000.0007 Ethernet0 aa00.0400.6408 Init 277 IS ES-IS
0000.0C00.0C35 Ethernet1 0000.0c00.0c36 Up 91 L1 IS-IS
0800.2B16.24EA Ethernet0 aa00.0400.2d05 Up 29 L1L2 IS-IS
0800.2B14.060E Ethernet0 aa00.0400.9205 Up 1698 ES ES-IS
0000.0C00.3E51 Serial1 *HDLC* Up 28 L2 IS-IS
0000.0C00.62E6 Ethernet1 0000.0c00.62e7 Up 22 L1 IS-IS
0A00.0400.2D05 Ethernet0 aa00.0400.2d05 Init 24 IS ES-IS
Table 43 describes the fields shown in the display.
| Field | Description |
|---|---|
System Id | Six-byte value that identifies a system in an area. |
Interface | Interface in which the system was learned from. |
SNPA | Subnetwork Point of Attachment. This is the data link address. |
State | State of the ES or IS. |
Init | System is an IS and is waiting for an IS-IS hello message. IS-IS regards the neighbor as not adjacent. |
Up | Believes the ES or IS is reachable. |
Holdtime | Number of seconds before this adjacency entry times out. |
Type | The adjacency type. Possible values are as follows: |
ES | End-system adjacency either discovered via the ES-IS protocol or statically configured. |
IS | Router adjacency either discovered via the ES-IS protocol or statically configured. |
L1 | Router adjacency for Level 1 routing only. |
L1L2 | Router adjacency for Level 1 and Level 2 routing. |
L2 | Router adjacency for Level 2 only. |
Protocol | Protocol through which the adjacency was learned. Valid protocol sources are ES-IS, IS-IS, ISO IGRP, Static, and DECnet. |
The following is sample output from the show clns neighbors detail command:
router# show clns neighbors detail
System Id Interface SNPA State Holdtime Type Protocol
000.0000.0007 Ethernet0 aa00.0400.6408 Init 291 IS ES-IS
Area Address(es): 47.0005.80FF.F500.0000.0003.0020
IP Address(es):175.1.19.22* 123.120.33.54 30.12.33.253
Uptime: 02:21:00
0000.0C00.0C35 Ethernet1 0000.0c00.0c36 Up 94 L1 IS-IS
Area Address(es): 47.0004.004D.0001 39.0001
IP Address(es):175.1.19.23
Uptime: 01:53:58
0800.2B16.24EA Ethernet0 aa00.0400.2d05 Up 9 L1L2 IS-IS
Area Address(es): 47.0004.004D.0001
IP Address(es):120.154.227.253*
Uptime: 03:09:59
0800.2B14.060E Ethernet0 aa00.0400.9205 Up 1651 ES ES-IS
Area Address(es): 49.0040
IP Address(es):120.154.227.252*
Uptime: 02:01:28
0000.0C00.3E51 Serial1 *HDLC* Up 27 L2 IS-IS
Area Address(es): 39.0004
IP Address(es):175.1.19.20*
Uptime: 02:58:58
0000.0C00.62E6 Ethernet1 0000.0c00.62e7 Up 26 L1 IS-IS
Area Address(es): 47.0004.004D.0001
IP Address(es):175.1.19.19*
Uptime: 03:10:00
oA00.0400.2D05 Ethernet0 aa00.0400.2d05 Init 29 IS ES-IS
Area Address(es): 47.0004.004D.0001
IP Address(es):120.154.226.253*
Uptime: 03:09:30
Notice that the information displayed in show clns neighbors detail output includes everything shown in show clns neighbors output in addition to the area address associated with the ES and IS neighbors and their uptimes. When IP routing is enabled, Integrated-ISIS adds information to the output of the show clns commands. The show clns neighbors detail command output shows the IP addresses that are defined for the directly connected interface and an asterik (*) to indicate which IP address is the next-hop.
You can use the master indexes or search online for documentation of related commands.
Use the show clns protocol EXEC command to list the protocol-specific information for each
ISO IGRP routing process in the router. There will always be at least two routing processes, a Level 1 and a Level 2, and there can be more.
domain | (Optional) Particular ISO IGRP routing domain. |
area-tag | (Optional) Particular IS-IS area. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns protocol command:
router# show clns protocol
ISO IGRP Level 1 Router: remote
Routing for domain: 39.0003 area: 0020
Sending Updates every 45 seconds. Next due in 11 seconds
Invalid after 135 seconds,
Hold down for 145 seconds
Sending Router Hellos every 17 seconds. Next due in 9 seconds
Invalid after 51 seconds,
IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
Interfaces in domain/area:
TokenRing1
ISO IGRP Level 2 Router: DOMAIN_remote
Routing for domain: 39.0003
Redistribute:
isis (Null Tag)
Sending Updates every 45 seconds. Next due in 2 seconds
Invalid after 135 seconds,
Hold down for 145 seconds
Sending Router Hellos every 17 seconds. Next due in 0 seconds
Invalid after 51 seconds,
ISO IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
Interfaces in domain/area:
TokenRing1
IS-IS Router: <Null Tag>
System Id: 0000.0C00.224D.00 IS-Type: level-1-2
Manual area address(es):
39.0004.0030
Routing for area address(es):
39.0004.0030
Interfaces supported by IS-IS:
Serial2
Next global update in 530 seconds
Redistributing:
static
iso-igrp (remote)
Distance: 110
Table 44 describes significant fields shown in the display.
| Field | Description |
|---|---|
ISO IGRP Level 1 Router: | Indicates what CLNS routing type is enabled on the router. (Always ISO IGRP when the fields in this section are displayed.) Also indicates what routing level (Level 1, Level 2, or both) is enabled on the router. |
remote | Process tag that has been configured using the router iso-igrp global configuration command. |
Routing for domain: 39.0003 area: 0020 | Domain address and area number for Level 1 routing processes. For Level 2 routing processes, this command lists the domain address. |
Sending Updates every 45 seconds. | Displays when the next routing updates are sent. |
Next due in 11 seconds | Indicates when the next update is sent. |
Invalid after 135 seconds | Indicates how long routing updates are to be believed. |
Hold down for 145 seconds | Indicates how long a route is held down before new information is to be believed. |
Sending Router hellos every 17 seconds. Next due in 9 seconds | Indicates how often the Cisco IOS software sends hello packets to each other and when the next is due. |
Invalid after 51 seconds | Indicates how long a neighbor entry is remembered. |
IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0 | Displays lists the weights applied to the various components of the metric. These fields are followed by the list of interfaces in this area. |
Interfaces in domain/area: | List of interface names for which the router process is configured. |
Table 45 describes significant fields shown in the IS-IS portion of the display.
| Field | Description |
|---|---|
IS_IS Router: <Null Tag> | Indicates what CLNS routing type is enabled on the router. (Always IS-IS when the fields in this section are displayed.) |
System Id: 0000.0C00.224D.00 | Identification value of the system. |
IS-Type: level-1-2 | Indicates what routing level (Level 1, Level 2 or both) is enabled on the router. |
Manual area address(es): 39.0004.0030 | Area addresses that have been configured. |
Routing for area address(es): 39.0004.0030 | List of manually configured and learned area addresses. |
Interfaces supported by IS-IS: | List of interfaces on the router supporting IS-IS. |
Next global update in 530 seconds | Next expected IS-IS update (in seconds). |
Redistributing: | Configuration of route redistribution. |
Distance: | Configured distance. |
Use the show clns route EXEC command to display all of the destinations to which this router knows how to route packets. The show clns route command shows the IS-IS Level 2 routing table as well as static and ISO IGRP learned prefix routes. This table stores IS-IS area addresses and prefix routes. Destinations are sorted by category.
show clns route [nsap]
nsap | (Optional) CLNS NSAP address. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns route command:
router# show clns route
ISO IGRP Routing Table for Domain 39.0003, Area 0020
System Id Next-Hop SNPA Interface Metric State
0000.0C00.224D 0000.0000.0000 -- -- 0 Up
ISO IGRP Routing Table for Domain 39.0003
Area Id Next-Hop SNPA Interface Metric State
0020 0000.0000.0000 -- -- 0 Up
CLNS Prefix Routing Table
39.0003 [100/0]
via 39.0004.0030.0000.0C00.224D.00, ISO IGRP, Up
39.0004.0040 [110/10]
via 0000.0C00.2D55, IS-IS, Up, Serial2
39.0004.0030 [110/0]
via 0000.0C00.224D, IS-IS, Up
39.0004.0030.0000.0C00.224D.00, Local NET Entry
39.0003.0020.0000.0C00.224D.00, Local NET Entry
39.0001, DECnet discard Entry, Up
As the display shows, neighbors are not included in the show clns route output.
Table 46 describes significant fields shown in the display.
| Field | Descriptions |
|---|---|
| The following are for dynamically learned routes: | |
Domain 39.0003 | The routing domain for which we are displaying the routes. |
Area 0020 | The area this portion of the routing table describes. |
System Id | Identification value of the system listed in Level 1 forwarding table. |
Area Id | The identification value of the area listed in the area forwarding table. |
Next-Hop | System ID of best cost next-hop to listed address. |
SNPA | SNPA of next-hop system. |
Interface | Interface through which next-hop system is known. |
Metric | ISO IGRP metric for the route. |
State | Up (active) or Down (nonoperational). |
| The following are for prefix routes: |
|
39.0003 | Destination prefix. |
[100/0] | Administrative distance/metric. |
Next-hop address | Either an NET (if a static route) or System ID, if route obtained via IS-IS or ISO-IGRP. |
ISO IGRP | Indicates whether the route was learned using ISO IGRP or IS-IS. |
Up | Link status—Up (active) or Down (nonoperational). |
Serial 2 | Interface type—Only appears if the specific interface through which the destination is reachable is unambiguously known; Local NET Entry indicates destination is on a directly connected network. |
DECnet Discard Entry | Static route entry for DECnet. |
Output for the show clns route nsap command is the same as that for show clns route, but only lists a single entry.
You can use the master indexes or search online for documentation of related commands.
Use the show clns traffic EXEC command to list the CLNS packets this router has seen.
show clns trafficThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show clns traffic command:
router# show clns traffic
CLNS & ESIS Output: 139885, Input: 90406
CLNS Local: 0, Forward: 0
CLNS Discards:
Hdr Syntax: 150, Checksum: 0, Lifetime: 0, Output cngstn: 0
No Route: 0, Dst Unreachable 0, Encaps. Failed: 0
NLP Unknown: 0, Not an IS: 0
CLNS Options: Packets 19, total 19, bad 0, GQOS 0, cngstn exprncd 0
CLNS Segments: Segmented: 0, Failed: 0
CLNS Broadcasts: sent: 0, rcvd: 0
Echos: Rcvd 0 requests, 69679 replies
Sent 69701 requests, 0 replies
ESIS(sent/rcvd): ESHs: 0/34, ISHs: 483/1839, RDs: 0/0, QCF: 0/0
ISO IGRP: Querys (sent/rcvd): 0/0 Updates (sent/rcvd): 1279/1402
ISO IGRP: Router Hellos: (sent/rcvd): 1673/1848
ISO IGRP Syntax Errors: 0
IS-IS: Level-1 Hellos (sent/rcvd): 0/0
IS-IS: Level-2 Hellos (sent/rcvd): 0/0
IS-IS: PTP Hellos (sent/rcvd): 0/0
IS-IS: Level-1 LSPs (sent/rcvd): 0/0
IS-IS: Level-2 LSPs (sent/rcvd): 0/0
IS-IS: Level-1 CSNPs (sent/rcvd): 0/0
IS-IS: Level-2 CSNPs (sent/rcvd): 0/0
IS-IS: Level-1 PSNPs (sent/rcvd): 0/0
IS-IS: Level-2 PSNPs (sent/rcvd): 0/0
IS-IS: Level-1 DR Elections: 0
IS-IS: Level-2 DR Elections: 0
IS-IS: Level-1 SPF Calculations: 0
IS-IS: Level-2 SPF Calculations: 0
Table 47 describes significant fields shown in the display.
| Field | Description |
|---|---|
CLNS & ESIS Output | Total number of packets that this router has sent. |
Input | Total number of packets that this router has received. |
CLNS Local | Lists the number of packets that were generated by this router. |
Forward | Lists the number of packets that this router has forwarded. |
CLNS Discards | Lists the packets that CLNS has discarded, along with the reason for the discard. |
CLNS Options | Lists the options that have been seen in CLNS packets. |
CLNS Segments | Lists the number of packets that have been segmented and the number of failures that occurred because a packet could not be segmented. |
CLNS Broadcasts | Lists the number of CLNS broadcasts that have been sent and received. |
Echos | Lists the number of echo request packets and echo reply packets that have been received. The line following this field lists the number of echo request packets and echo reply packets that have been sent. |
ESIS (sent/rcvd) | Lists the number of ESH, ISH, and Redirects sent and received. |
ISO IGRP | Lists the number of IGRP queries and updates sent and received. |
Router Hellos | Lists the number of IGRP router hello packets that have been sent and received. |
IS-IS: Level-1 hellos (sent/rcvd) | Lists the number of Level 1 IS-IS hello packets sent and received. |
IS-IS: Level-2 hellos (sent/rcvd) | Lists the number of Level 2 IS-IS hello packets sent and received. |
IS-IS: PTP hellos (sent/rcvd) | Lists the number of point-to-point IS-IS hello packets sent and received over serial links. |
IS-IS: Level-1 LSPs (sent/rcvd) | Lists the number of Level 1 link-state PDUs sent and received. |
IS-IS: Level-2 LSPs (sent/rcvd) | Lists the number of Level 2 link-state PDUs sent and received. |
IS-IS: Level-1 CSNPs (sent/rcvd) | Lists the number of Level 1 CSNPs sent and received. |
IS-IS: Level-2 CSNPs (sent/rcvd) | Lists the number of Level 2 CSNPs sent and received. |
IS-IS: Level-1 PSNPs (sent/rcvd) | Lists the number of Level 1 PSNPs sent and received. |
IS-IS: Level-2 PSNPs (sent/rcvd) | Lists the number of Level 2 PSNPs sent and received. |
IS-IS: Level-1 DR Elections | Lists the number of times Level 1 designated router election occurred. |
IS-IS: Level-2 DR Elections | Lists the number of times Level 2 designated router election occurred. |
IS-IS: Level-1 SPF Calculations | Lists the number of times Level 1 shortest-path-first (SPF) tree was computed. |
IS-IS: Level-2 SPF Calculations | Lists the number of times Level 2 SPF tree was computed. |
Use the show isis database EXEC command to display the IS-IS link state database. A summary display is provided if no options are specified.
show isis database [level-1] [level-2] [detail] [lspid]
level-1 | (Optional) Displays the IS-IS link state database for Level 1. You can use the abbreviation l1. |
level-2 | (Optional) Displays the IS-IS link state database for Level 2. You can use the abbreviation l2. |
detail | (Optional) When specified, the content of each link-state PDU is displayed. Otherwise, a summary display is provided. |
lspid | (Optional) Link-state protocol ID. Displays the contents of the specified link-state packet. The Link-state protocol ID must be in the form of xxxx.xxxx.xxxx.yy-zz or name.yy-zz. For a description of these values, see Table 48 in the "Usage Guidelines" section. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
Each of the options shown in brackets for this command can be entered in an arbitrary string within the same command entry. For example, the following are both valid command specifications and provided the same display: show isis database detail l2 and show isis database l2 detail.
The values for the argument lspid are described in Table 48:
| Value | Description |
|---|---|
xxxx.xxxx.xxxx.yy-zz | xxxx.xxxx.xxxx—System ID. |
name.yy-zz | name—CLNS host name. |
The following is sample output from the show isis database command when specified with no options or as show isis data l1 l2:
router# show isis database
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.00-00 0x0000000C 0x5696 792 0/0/0
0000.0C00.40AF.00-00* 0x00000009 0x8452 1077 1/0/0
0000.0C00.62E6.00-00 0x0000000A 0x38E7 383 0/0/0
0000.0C00.62E6.03-00 0x00000006 0x82BC 384 0/0/0
0800.2B16.24EA.00-00 0x00001D9F 0x8864 1188 1/0/0
0800.2B16.24EA.01-00 0x00001E36 0x0935 1198 1/0/0
IS-IS Level-2 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.03-00 0x00000005 0x04C8 792 0/0/0
0000.0C00.3E51.00-00 0x00000007 0xAF96 758 0/0/0
0000.0C00.40AF.00-00* 0x0000000A 0x3AA9 1077 0/0/0
Table 49 describes significant fields shown in the display.
| Field | Description |
|---|---|
LSPID | The link-state PDU ID. The first six octets form the system ID. The next octet is the pseudo ID. When this value is zero, the link-state PDU ID describes links from the system. When it is not zero, the link-state PDU is a pseudo-node link-state PDU. The designated router for an interface is the only system that originates pseudonode link-state PDUs. The last octet is the link-state PDU number. If there is more data than can fit in a single link-state PDU, additional link-state PDUs are sent with increasing link-state PDU numbers. An asterisk (*) indicates that the link-state PDU was originated by the local system. |
LSP Seq Num | Sequence number for the link-state PDU that allows other systems to determine if they have received the latest information from the source. |
LSP Checksum | Checksum of the entire link-state PDU packet. |
LSP Holdtime | Amount of time the link-state PDU remains valid, in seconds. |
ATT | The attach bit. This indicates that the router is also a Level 2 router, and it can reach other areas. |
P | The P bit. Detects if the IS is area partition repair capable. |
OL | The overload bit. Determines if the IS is congested. |
The following is sample output from the show isis database detail command:
router# show isis database detail
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.00-00 0x0000000C 0x5696 325 0/0/0
Area Address: 47.0004.004D.0001
Area Address: 39.0001
Metric: 10 IS 0000.0C00.62E6.03
Metric: 0 ES 0000.0C00.0C35
0000.0C00.40AF.00-00* 0x00000009 0x8452 608 1/0/0
Area Address: 47.0004.004D.0001
Metric: 10 IS 0800.2B16.24EA.01
Metric: 10 IS 0000.0C00.62E6.03
Metric: 0 ES 0000.0C00.40AF
IS-IS Level-2 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.03-00 0x00000005 0x04C8 317 0/0/0
Metric: 0 IS 0000.0C00.0C35.00
0000.0C00.3E51.00-00 0x00000009 0xAB98 1182 0/0/0
Area Address: 39.0004
Metric: 10 IS 0000.0C00.40AF.00
Metric: 10 IS 0000.0C00.3E51.05
As the display shows, in addition to the information displayed in show isis database, the show isis database detail command displays the contents of each link-state PDU.
Table 50 describes significant fields shown in the display.
| Field | Description |
|---|---|
LSPID | The link-state PDU ID. The first six octets form the System ID. The next octet is the pseudo ID. When this value is zero, the link-state PDU describes links from the system. When it is not zero, the link-state PDU is a pseudo-node link-state PDU. The designated router for an interface is the only system that originates pseudonode link-state PDUs. The last octet is the link-state PDU number. If there is more data than can fit in a single link-state PDU, additional link-state PDUs are sent with increasing link-state PDU numbers. An asterisk (*) indicates that the link-state PDU was originated by the local system. |
LSP Seq Num | Sequence number for the link-state PDU that allows other systems to determine if they have received the latest information from the source. |
LSP Checksum | Checksum of the entire link-state PDU packet. |
LSP Holdtime | Amount of time the link-state PDU remains valid, in seconds. |
ATT | The attach bit. This indicates that the router is also a Level 2 router, and it can reach other areas. |
P | The P bit. Detects if the IS is area partition repair-capable. |
OL | The overload bit. Determines if the IS is congested. |
Area Address: | Reachable area addresses from the router. |
Metric: | IS-IS metric for the route. |
Use the show isis routes EXEC command to display the IS-IS Level 1 forwarding table for IS-IS learned routes.
show isis routesThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show isis routes command:
router# show isis routes
IS-IS Level-1 Routing Table - Version 34
System Id Next-Hop SNPA Interface Metric State
0000.0C00.0C35 0000.0C00.0C35 0000.0c00.0c36 Ethernet1 20 Up
0800.2B16.24EA 0800.2B16.24EA aa00.0400.2d05 Ethernet0 10 Up
0800.2B14.060E 0800.2B14.060E aa00.0400.9205 Ethernet0 10 Up
0800.2B14.0528 0800.2B14.0528 aa00.0400.9105 Ethernet0 10 Up
0000.0C00.40AF 0000.0000.0000 -- -- 0 Up
0000.0C00.62E6 0000.0C00.62E6 0000.0c00.62e7 Ethernet1 10 Up
AA00.0400.2D05 0800.2B16.24EA aa00.0400.2d05 Ethernet0 10 Up
Table 51 describes significant fields shown in the display.
| Field | Description |
|---|---|
Version 34 | Indicates version number of the Level 1 routing table. All Level 1 routes with a version number that does not match this number are flushed from the routing table. The router's version number increments when the configuration changes from Level 1 or Level 1-2 to Level 2 only. |
System Id | Identification value of the system listed in Level 1 forwarding table. |
Next-Hop | System ID of best-cost next-hop to listed address. |
SNPA | SNPA of next-hop system. |
Interface | Interface through which next-hop system is known. |
Metric | IS-IS metric for the route. |
State | Up (active) or Down (nonoperational). |
Use the show isis spf-log EXEC command to display a history of the SPF calculations for IS-IS.
show isis spf-logThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show isis spf-log command:
router> show isis spf-log
Level 1 SPF log
When Duration Nodes Count Last trigger LSP Triggers
0:30:59 1028 84 1 PADTHAI.00-00 TLVCONTENT
0:27:09 1016 84 1 PADTHAI.00-00 TLVCONTENT
0:26:30 1136 84 1 PADTHAI.04-00 TLVCONTENT
0:23:11 1244 84 1 PADTHAI.00-00 TLVCONTENT
0:22:39 924 84 2 PADTHAI.00-00 TLVCONTENT
0:22:08 1036 84 1 PADTHAI.04-00 TLVCONTENT
0:20:02 1096 84 1 PADTHAI.00-00 TLVCONTENT
0:19:31 1140 84 1 PADTHAI.04-00 TLVCONTENT
0:17:25 964 84 2 PERIODIC
0:16:54 996 84 1 PADTHAI.00-00 TLVCONTENT
0:16:23 984 84 1 TOMYUM.03-00 TLVCONTENT
0:15:52 1052 84 1 TOMYUM.03-00 TLVCONTENT
0:14:34 1112 84 1 TOMYUM.00-00 TLVCONTENT
0:13:37 992 84 1 TOMYUM.03-00 TLVCONTENT
0:13:06 1036 84 1 TOMYUM.00-00 TLVCONTENT
0:12:35 1008 84 1 PADTHAI.00-00 TLVCONTENT
0:02:52 1032 84 1 PADTHAI.00-00 TLVCONTENT
0:02:16 1032 84 1 IPBACKUP IPQUERY
0:01:44 1000 84 3 PADTHAI.00-00 TLVCONTENT
Level 2 SPF log
When Duration Nodes Count Last trigger LSP Triggers
3:18:31 712 84 1 PERIODIC
3:03:24 708 84 1 PERIODIC
2:48:17 660 84 1 PERIODIC
2:33:12 784 84 1 PERIODIC
2:32:00 644 84 1 PADTHAI.00-00 TLVCONTENT
2:31:29 544 84 63 PADTHAI.03-00 TLVCONTENT
2:30:58 544 84 36 PADTHAI.00-00 TLVCONTENT
2:30:27 528 84 39 TOMYUM.00-00 NEWADJ NEWLSP
2:29:57 628 84 57 TOMYUM.00-00 TLVCONTENT
2:18:07 652 84 1 PERIODIC
2:02:59 772 84 1 PERIODIC
1:47:55 740 84 1 PERIODIC
1:32:47 816 84 1 PERIODIC
1:17:43 744 84 1 PERIODIC
1:02:37 712 84 1 PERIODIC
0:47:29 664 84 1 PERIODIC
0:32:27 732 84 1 PERIODIC
0:17:22 788 84 1 PERIODIC
0:02:16 660 84 1 RTCLEARED
Table 52 describes the fields shown in the display.
| Field | Description |
|---|---|
When | Amount of time since the SPF calculation took place. |
Duration | Amount of time (in milliseconds) that the calculation required. |
Nodes | Number of link-state packets (LSPs) encountered during the calculation. |
Count | Number of times that the SPF calculation was triggered before it actually took place. An SPF calculation is normally delayed for a short time after the event that triggers it. |
Last trigger LSP | LSP id of the last LSP that caused a full SPF calculation. This is done for the triggers NEWLSP, LSPEXPIRED, LSPHEADER, TLVCODE and TLVCONTENT. When multiple LSPs change, only the last one to arrive at the router appears in the log. |
Triggers | List of the types of triggers that were recorded before the SPF calculation occurred (more than one type may be displayed): PERIODIC—Periodic SPF calculation (every 15 minutes). NEWSYSID—New system ID was assigned. NEWAREA—New area address was configured. NEWLEVEL—Level of the IS-IS process was changed. RTCLEARED—CLNS routing table was manually cleared. NEWMETRIC—Link metric of an interface was reconfigured. IPBACKUP—IP backup route is needed (because a route from a protocol with a worse administrative distance has been lost). IPQUERY—IP routing table was manually cleared. ATTACHFLAG—Level 2 router has become attached or unattached from the rest of the Level 2 topology. LSPEXPIRED—LSP has expired. NEWLSP—New LSP has been received. LSPHEADER—LSP with changed header fields was received. TLVCODE—LSP with a changed TLV code field was received. TLVCONTENT—LSP with changed TLV contents was received. ADMINDIST—Administrative distance of the IS-IS process was reconfigured. AREASET—Calculated area address set has changed. BACKUPOVFL—All known IP backup routes have been lost. NEWADJ—New neighbor adjacency came up. DBCHANGED—IS-IS link-state database was manually cleared. |
Use the show route-map EXEC command to display all route-maps configured or only the one specified.
show route-map [map-name]
map-name | (Optional) Name of a specific route map. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show route-map command:
router# show route-map
route-map sid, permit, sequence 10
Match clauses:
tag 1 2
Set clauses:
metric 5
route-map sid, permit, sequence 20
Match clauses:
tag 3 4
Set clauses:
metric 6
Table 53 describes the fields shown in the display:
| Field | Description |
|---|---|
route-map | Name of the route map. |
permit | Indicates that the route is redistributed as controlled by the set actions. |
sequence | Number that indicates the position a new route map is to have in the list of route maps already configured with the same name. |
Match clauses: | Match criteria—conditions under which redistribution is allowed for the current route map. |
Set clauses: | Set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. |
You can use the master indexes or search online for documentation of related commands.
Use the show tarp EXEC command to display all global TARP parameters.
show tarpThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp command:
router# show tarp
Global TARP information:
TID of this station is "cerd"
Timer T1 (timer for response to TARP Type 1 PDU) is 15 seconds
Timer T2 (timer for response to TARP Type 2 PDU) is 25 seconds
Timer T3 (timer for response to ARP request) is 40 seconds
Timer T4 (timer that starts when T2 expires) is 15 seconds
Loop Detection Buffer entry timeout: 300 seconds
TID cache entry timeout: 300 seconds
This station will propagate TARP PDUs
This station will originate TARP PDUs
TID<->NET cache is enabled
Sequence number that next packet originated by this station will have: 9
Update remote cache (URC) bit is 0
Packet lifetime: 100 hops
Protocol type used in outgoing packets: "FE"
N-Selector used in TARP PDU's: "AF"
Table 54 describes the fields shown in the display.
| Field | Description |
|---|---|
TID | Target identifier assigned to this router by the tarp tid command. |
Timer T1 | Number of seconds that the router will wait to receive a response from a Type 1 PDU. The T1 timer is set by the tarp t1-response-timer command. |
Timer T2 | Number of seconds that the router will wait to receive a response from a Type 2 PDU. The T2 timer is set by the tarp t2-response-timer command. |
Timer T3 | Number of seconds that the router will wait for a response from a Type 5 PDU. The T3 timer is set by the tarp arp-request-timer command. |
Timer T4 | Number of seconds that the router will wait for a response from a Type 2 PDU after the T2 timer has expired. The T4 timer is set by the tarp post-t2-response-timer command. |
Loop Detection Buffer entry timeout | Number of seconds that a System ID-to-sequence number mapping entry remains in the loop-detection buffer table. The loop-detection buffer timeout is set by the tarp ldb-timer command. |
TID cache entry timeout | Number of seconds that a dynamically created TARP entry remains in the TID cache. The cache timeout is set by the tarp cache-timer command. |
Propagate TARP PDUs | Indicates whether the router can propagate TARP PDUs to its TARP neighbors. This field is set by the tarp global-propagate command. |
Originate TARP PDUs | Indicates whether the router can originate TARP PDUs. This field is set by the tarp originate command. |
TID<->NET cache | Indicates whether the router will store TID-to-network (NSAP) address mapping in cache. This field is set by the tarp allow-caching command. |
Sequence number | Number used by the next packet to indicate if the packet is newer than the last information received. This number can be changed by the tarp sequence-number command. |
Update remote cache | Indicates the setting of the URC bit in outgoing PDUs. When the bit is zero, the receiver of the PDU will update its cache entry. When the bit is one, the receiver of the PDU will not update its cache entry. This URC bit is set by the tarp urc command. |
Packet lifetime | Number of hosts that a PDU can traverse before the PDU is discarded. The packet lifetime is set by the tarp lifetime command. |
Protocol type | Hexadecimal representation of the protocol used in outgoing PDUs. The protocol type is set by the tarp protocol-type command. Only CLNP (indicated by FE) is supported. |
N-selector | Hexadecimal representation of the N-selector used to indicate that the packet is a TARP PDU. The N-selector is set by the tarp nselector-type command. The default is "AF." |
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp blacklisted-adjacencies command:
router# show tarp blacklisted-adjacencies
Adjacencies that we won't propagate TARP PDU's to:
49.0001.5555.5555.5555.00
Table 55 describes the field shown in the display.
| Field | Description |
|---|---|
49.0001.5555.5555.5555.00 | NSAP address of the blacklisted router. |
You can use the master indexes or search online for documentation of related commands.
tid | Target identifier of the router from which you want information. Alphanumeric string up to 255 characters. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp host command:
router# show tarp host artemis
TID of entry: artemis
NET of entry: 49.0001.1111.1111.1111.00
Entry type: DYNAMIC
Expiration time: 280 seconds
Table 56 describes the fields shown in the display.
| Field | Description |
|---|---|
TID | Target identifier of the router. |
NET | NSAP address of the router. |
Entry type | Type of entry in the TID cache. Values are local, dynamic, or static. A static entry is created with the tarp map command. |
Expiration time | Amount of time that a dynamically created entry will remain in the TID cache. The cache timer is set by the tarp cache-timer command. |
You can use the master indexes or search online for documentation of related commands.
Use the show tarp interface EXEC command to list all interfaces that have TARP enabled.
show tarp interface [type number]
type | (Optional) Interface type. |
number | (Optional) Interface number. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp interface command:
router# show tarp interface
Ethernet0 is up, line protocol is up, encapsulation is ARPA
TARP propagation is enabled on this interface
Table 57 describes the fields shown in the display.
| Field | Description |
|---|---|
Ethernet...is {up | down} ...is administratively down | Indicates whether the interface hardware is currently active (whether carrier detect is present) or if it has been taken down by an administrator. |
line protocol is {up | down | administratively down} | Indicates whether the software processes that handle the line protocol think the line is usable (that is, whether keepalives are successful). |
Encapsulation | Indicates the encapsulation method assigned to the interface. |
TARP propagation | Indicates whether this interface can propagate TARP PDUs. The propagation is set by the tarp propagate command. |
You can use the master indexes or search online for documentation of related commands.
Use the show tarp ldb EXEC command to display the contents of the loop-detection buffer table.
show tarp ldbThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp ldb command:
router# show tarp ldb
System ID Sequence Number Expiration (sec)
1111.1111.1111 4 240
Table 58 describes the fields shown in the display.
| Field | Description |
|---|---|
System ID | System ID of the router. |
Sequence Number | Sequence number of the last packet sent by the router specified by the system ID. |
Expiration (sec) | Time, in seconds, left before this entry in the loop-detection buffer table is cleared. The time is set by the tarp ldb-timer command. |
You can use the master indexes or search online for documentation of related commands.
clear tarp ldb-table
tarp sequence-number
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp map command:
router# show tarp map
Static MAP entries:
shashi 49.0001.6666.6666.6666.00
sonali 49.0001.7777.7777.7777.00
Table 59 describes the fields shown in the display.
| Field | Description |
|---|---|
shashi | TID of the static entry. |
49.0001.6666.6666.6666.00 | NSAP address of the static entry. |
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp static-adjacencies command:
router# show tarp static-adjacencies
Manual (static) TARP adjacencies:
55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00
Table 60 describes the field shown in the display.
| Field | Description |
|---|---|
55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00 | NSAP address of the TARP adjacency. |
You can use the master indexes or search online for documentation of related commands.
detail | (Optional) List additional information in the TID/NET cache (such as the expiration time for dynamic entries). |
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp tid-cache command:
router# show tarp tid-cache
TID ('*' : static; & : local) NSAP
* shashi 49.0001.6666.6666.6666.00
& router 49.0001.3333.3333.3333.00
* sonali 49.0001.7777.7777.7777.00
artemis 49.0001.1111.1111.1111.00
The following is sample output from the show tarp tid-cache detail command:
router# show tarp tid-cache detail
TID ('*': static; &: local) NSAP
& router 49.0001.3333.3333.3333.00
Expiration time: NONE
Table 61 describes the fields shown in the displays.
| Field | Description |
|---|---|
TID | Target identifier assigned to the TID cache entry. Static entries are flagged with an asterisk (*). The local entry is flagged with an ampersand (&). |
NSAP | NSAP address of the TID cache entry. |
* | An asterisk (*) indicates that the entry in the TID cache is static (that is, you have created an entry in the TID cache with the tarp map command. |
& | An ampersand (&) indicates that the entry in the TID cache is the local entry (that is, the router to which you are connected). |
Expiration time | Amount of time the entry remains in the TID cache. When this time expires, the entry is removed from the TID cache. Only dynamic entries have an expiration time. The local entry indicated by an ampersand (&) and static entries indicated by an asterisk (*) are not removed from the TID cache. |
You can use the master indexes or search online for documentation of related commands.
clear tarp tid-table
tarp cache-timer
tarp map
tarp tid
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show tarp traffic command:
router# show tarp traffic
TARP counters:
Packets output: 11, Input: 5
Hdr syntax: 0
No memory: 0, Invalid packet: 0
Lifetime exceeded: 0
Table 62 describes the fields shown in the display.
| Field | Description |
|---|---|
Packets output | Indicates the number of PDUs that this router has originated. |
Input | Indicates the number of PDUs that this router has received. |
Hdr syntax | Number of PDUs with bad header information. |
No memory | Number of times a request for memory failed (because of insufficient memory). |
Invalid packets | Number of received PDUs that contained invalid information. |
Lifetime exceeded | Number of received PDUs with zero lifetime. |
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
By default, storing TID-to-network (NSAP) address mapping in cache is enabled unless you specifically disable the capability with the no tarp allow-caching command. If you disable this capability, you must use the tarp allow-caching command to re-enable storage of TID-to-network address mapping in cache. After re-enabling this capability, any previously cleared local entry and all static entries are restored.
The following example disables storage of TID-to-NSAP address mapping in cache on the router:
no tarp allow-caching
You can use the master indexes or search online for documentation of related commands.
clear tarp tid-table
show tarp tid-cache
show tarp map
tarp cache-timer
tarp map
seconds | Number of seconds that the router will wait for a response from a TARP type 5 PDU. The range is 0 to 3600 seconds. The default is 40 seconds. |
40 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
You may want to increase the time if your network has a slow link or there are long delay times on the link.
TARP Type 5 PDUs are sent by the tarp query command to determine a TID that corresponds to a particular NSAP.
The following example sets the timeout for TARP type 5 PDUs to 60 seconds (one minute):
tarp arp-request-timer 60
You can use the master indexes or search online for documentation of related commands.
nsap | NSAP address that cannot receive TARP PDUs. Use the full NSAP address. |
All hosts receive propagated TARP PDUs.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
A TARP router propagates PDUs to all its TARP adjacencies (both dynamic and static). Use the tarp blacklist-adjacency command to bypass hosts that may not have TARP running or to bypass hosts to which you do not want to propagate TARP PDUs.
The following example specifies that the router 49.0001.0000.0c00.1111.1234.00 will not receive propagated TARP PDUs:
tarp blacklist-adjacency 49.0001.0000.0c00.1111.1234.00
You can use the master indexes or search online for documentation of related commands.
show tarp blacklisted-adjacencies
seconds | Number of seconds an entry remains in the TID cache. The range is 30 to 86,400 seconds. The default is 3,600 seconds (one hour). |
3,600 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Static entries (those created with the tarp map command) remain in the TID cache unless cleared by the no tarp map command.
If entries frequently change, you may want to use a shorter time period. If entries are stable, you may want to use a longer time period.
The following example limits the time an entry remains in the TID cache to 1,800 seconds (30 minutes):
tarp cache-timer 1800
You can use the master indexes or search online for documentation of related commands.
clear tarp tid-table
show tarp tid-cache
This command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
Enabling TARP allows the interface to request and respond to TARP PDUs. TARP PDUs are identified by a unique N-selector in the NSAP address. You must also have the TARP process running on the router by using the tarp run command.
The following example enables TARP on Ethernet interface 0:
interface ethernet 0
tarp enable
You can use the master indexes or search online for documentation of related commands.
show tarp interface
tarp nselector-type
tarp propagate
tarp run
This command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
TARP PDUs are globally propagated to all TARP neighbors by default unless you specifically disable the capability with the no tarp global-propagate command. If you disable this capability, you must use the tarp global-propagate command to re-enable global purgation of TARP PDUs.
TARP PDUs are propagated on all interfaces by default unless you specifically disable the capability on a specific interface with the no tarp propagate command.
The following example disables global propagation of TARP PDUs on this router:
no tarp global-propagate
You can use the master indexes or search online for documentation of related commands.
seconds | Number of seconds that a system ID-to-sequence number mapping entry remains in the loop-detection buffer table. The range is 0 to 86,400 seconds. The default is 300 seconds. |
300 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
The loop-detection buffer table prevents TARP PDUs from looping.
The following example limits the time an entry remains in the loop-detection buffer table to 600 seconds (10 minutes):
tarp ldb-timer 600
You can use the master indexes or search online for documentation of related commands.
clear tarp ldb-table
show tarp ldb
tarp lifetime
hops | Number of hosts that a PDU can traverse before it is discarded. Each router represents one hop. The range is 0 to 65535 hops. The default is 100 hops. |
100 hops
Global configuration
This command first appeared in Cisco IOS Release 11.1.
The number of hops specified is decremented after every hop. A PDU with a lifetime of zero is discarded.
The following example specifies that the TARP PDU can traverse 150 hosts before it is discarded:
tarp lifetime 150
You can use the master indexes or search online for documentation of related commands.
tarp arp-request-timer
tarp ldb-timer
tid | Target identifier to be mapped to the specified NSAP. Alphanumeric string up to 255 characters. |
nsap | NSAP address to map to the specified TID. Use the full NSAP address. |
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Use the tarp map command to map multiple NSAP addresses on a router. For example, using the tarp resolve to get the NSAP for a known TID will always return the first NSAP address. If the router has multiple NSAP addresses, you can use the tarp map command to map the TID to multiple NSAP addresses. If a router has NSAP addresses 1, 2, 3, the tarp resolve command will always return NSAP address 1. Use the tarp map command to map the router to NSAP addresses 2 and 3 so the tarp query command will return the TID corresponding to the other NSAP addresses.
The following example maps the NSAP address 49.0001.000.1111.1111.1234.00 to TID SJ1:
tarp map sj1 49.0001.0000.1111.1111.1234.00
You can use the master indexes or search online for documentation of related commands.
clear tarp tid-table
show tarp map
tarp query
tarp resolve
hex-digit | Digit in hexadecimal format to be used to identify TARP PDUs. The default is AF. |
AF
Global configuration
This command first appeared in Cisco IOS Release 11.1. This feature provide flexibility in using the N-selector field to indicate TARP PDUs. The N-selector must be the same on all hosts running the TARP process.
The following example changes the N-selector used in CLNP PDUs to BC:
tarp nselector-type BC
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Origination of TARP PDUs is enabled by default unless you specifically disable the capability with the no tarp originate command. If you disable this capability, you must use the tarp originate command to re-enable origination of TARP PDUs.
The following example disables the origination of TARP PDUs on this router:
no tarp originate
You can use the master indexes or search online for documentation of related commands.
seconds | Number of seconds that the router will wait for a response for a Type 2 PDU after the default timer has expired. The range is 0 to 3,600 seconds. The default is 15 seconds. |
15 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
A Type 1 PDU is sent to all Level 1 (IS-IS and ES-IS) neighbors when a router has a TID for which it has no matching NSAP information. If no response is received within the specified timeout period, a Type 2 PDU is sent to all Level 1 and Level 2 neighbors. If no response is received within the specified timeout period, additional time is allocated based on the number specified in the tarp post-t2-response-timer command.
The following example sets the additional time to wait for a response from a Type 2 PDU to 60 seconds:
tarp post-t2-response-timer 60
You can use the master indexes or search online for documentation of related commands.
This command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
TARP PDUs are propagated on all interfaces by default unless you specifically disable the capability on a specific interface with the no tarp propagate command. If you disable this capability, you must use the tarp propagate command to re-enable purgation of TARP PDUs. Enabling propagation of TARP PDUs allows the interface to propagate PDUs to all neighbors on this interface. TARP PDUs are identified by a unique N-selector in the NSAP.
The following example starts the TARP process on the router and enables TARP propagation on Ethernet interface 0:
interface ethernet 0
tarp propagate
You can use the master indexes or search online for documentation of related commands.
show tarp interface
tarp enable
tarp global-propagate
tarp nselector-type
tarp run
hex-digit | Digit in hexadecimal format to be used to identify the protocol used in outgoing TARP PDUs. The default is FE (for CLNP). |
FE
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Only FE is supported.
You can use the master indexes or search online for documentation of related commands.
Use the tarp query EXEC command to determine a TID corresponding to a specific NSAP address.
tarp query nsap
nsap | NSAP address that you want the TID for. Use the full NSAP address. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
If there is a TID entry in the local TID cache, the requested information is displayed.
If there is no TID entry in the local TID cache, a TARP Type 5 PDU is sent to the specified NSAP address. Because the NSAP address is specified, the PDU is unicast to the particular NSAP address. If a response is received (in the form of a Type 3 PDU), the local TID cache is updated and the requested information is displayed.
The length of time that the router will wait for a response to a Type 5 PDU is controlled by the tarp arp-request-timer command.
The following is sample output from the tarp query command:
router# tarp query 49.0001.3333.3333.3333.00
Type escape sequence to abort.
Sending TARP type 5 PDU, timeout 40 seconds...
TID corresponding to NET 49.0001.3333.3333.3333.00 is cerd
Table 63 describes the fields shown in the display.
| Field | Description |
|---|---|
Sending TARP type 5 PDU | PDU requesting the TID of the specified NSAP. |
Timeout... | Number of seconds the router will wait for a response from the Type 5 PDU. The timeout is set by the tarp arp-request-timer command. |
TID corresponding to... is... | Indicates the TID for the specified NSAP address. |
show tarp
tarp arp-request-timer
Use the tarp resolve EXEC command to determine an NSAP address corresponding to a specified TID.
tarp resolve tid [1 | 2]
tid | Target identifier to be mapped to the specified NSAP. Alphanumeric string up to 255 characters. |
1 | (Optional) Send a Type 1 PDU. The default is a Type 1 PDU. If a response is not received before the timeout period, a Type 2 PDU is sent. |
2 | (Optional) Send only Type 2 PDU. |
EXEC
This command first appeared in Cisco IOS Release 11.1.
If there is an NSAP entry in the local TID cache, the requested information is displayed.
If there is no NSAP entry in the local TID cache, a TARP Type 1 or Type 2 PDU is sent out. By default a Type 1 PUD is sent. A Type 1 PDU is sent to all Level 1 (IS-IS and ES-IS) neighbors. If a response is received (in the form of a Type 3 PDU), the local TID cache is updated and the requested information is displayed.
If a response from the Type 1 PDU is not received within the timeout period, a Type 2 PDU is sent to all Level 1 and Level 2 neighbors. If a response is received (in the form of a Type 3 PDU), the local TID cache is updated and the requested information is displayed.
The length of time that the router will wait for a response to a Type 1 PDU is controlled by the tarp t1-response-timer command. The length of time that the router waits for a response to a Type 2 PDU is controlled by the tarp t2-response-timer command and the tarp-post-t2-response-timer command.
The following is sample output from the tarp resolve command:
router# tarp resolve artemis
Type escape sequence to abort.
Sending TARP type 1 PDU, timeout 15 seconds...
NET corresponding to TID artemis is 49.0001.1111.1111.1111.00
Table 64 describes the fields shown in the display.
| Field | Description |
|---|---|
Sending TARP type 1 PDU | PDU requesting the NSAP of the specified TID. |
timeout... | Number of seconds the router will wait for a response from the Type 1 PDU. The timeout is set by the tarp t1-response-timer command. |
NET corresponding to... is... | Indicates the NSAP address (in this case, 49.0001.1111.1111.1111.00) for the specified TID. |
You can use the master indexes or search online for documentation of related commands.
tarp map
tarp post-t2-response-timer
tarp t1-response-timer
tarp t2-response-timer
nsap | NSAP address to create a static TARP adjacency. Use the full NSAP address. |
Global configuration
This command first appeared in Cisco IOS Release 11.1.
A TARP router propagates PDUs to all its adjacencies and static TARP adjacencies.
If a router is not running TARP, the router discards TARP PDUs rather than propagating the PDUs to all its adjacencies. To allow propagation of the PDU to hosts that are "beyond" a non-TARP router, you must use the tarp route-static command to ensure that the hosts receive PDUs. The tarp route-static command allows TARP PDUs to "tunnel" through hosts that are not running TARP.
The specified router, as identified by the NSAP address, is stored in a TARP static adjacencies queue.
Use the tarp blacklist-adjacency command to bypass hosts that may not have TARP running.
The following example adds 49.0001.0000.0c00.1111.1234.00 as a static TARP adjacency to the TARP queue:
tarp route-static 49.0001.0000.0c00.1111.1234.00
You can use the master indexes or search online for documentation of related commands.
show tarp static-adjacencies
tarp blacklist-adjacency
This command has no arguments or keywords.
No TARP process (unless configured to start in NVRAM).
Global configuration
This command first appeared in Cisco IOS Release 11.1.
You must also enable TARP on the individual interfaces by using the tarp enable command.
The following example starts the TARP process on the router:
tarp run
You can use the master indexes or search online for documentation of related commands.
number | Number from 0 to 65535 that will be used as the sequence number in the next outgoing PDU. The default is zero. |
Zero
Global configuration
This command first appeared in Cisco IOS Release 11.1.
The sequence number lets the router determine if information received in the PDU is newer than the last information received. You may want to increase the sequence number to ensure that other hosts update their entries in TID cache.
The following example causes a sequence number of 10 to be assigned to the next TARP PDU:
tarp sequence-number 10
You can use the master indexes or search online for documentation of related commands.
seconds | Number of seconds that the router will wait to receive a response from a Type 1 PDU. The range is 0 to 3600 seconds. The default is 15 seconds. |
15 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
A Type 1 PDU is sent to all Level 1 (IS-IS and ES-IS) neighbors when a router has a TID for which it has no matching NSAP information. If no response is received within the timeout period (specified by the tarp t1-response-timer command), a Type 2 PDU is sent to all Level 2 neighbors.
The following example sets the timeout period for a Type 1 PDU to 60 seconds:
tarp t1-response-timer 60
You can use the master indexes or search online for documentation of related commands.
seconds | Number of seconds that the router will wait to receive a response from a Type 2 PDU. The range is 0 to 3600 seconds. The default is 25 seconds. |
25 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.1.
A Type 1 PDU is sent to all Level 1 (IS-IS and ES-IS) neighbors when a router has a TID for which it has no matching NSAP information. If no response is received within the timeout period (specified by the tarp t1-response-timer command), a Type 2 PDU is sent to all Level 2 neighbors. If no response is received within the timeout period (specified by the tarp t2-response-timer command), additional time can be allocated by using the tarp post-t2-response-timer command.
The following example sets the timeout period for a Type 2 PDU to 60 seconds:
tarp t2-response-timer 60
You can use the master indexes or search online for documentation of related commands.
tarp post-t2-response-timer
tarp t1-response-timer
tid | Target identifier to be used by this router. Alphanumeric string up to 255 characters. |
Global configuration
This command first appeared in Cisco IOS Release 11.1.
All hosts using TARP must have a unique TID assigned.
The following example assigns the TID SJ3 to the router:
tarp tid sj3
You can use the master indexes or search online for documentation of related commands.
show tarp
show tarp host
show tarp tid-cache
0 | Set the update remote cache bit to 0, which is the default value. When the bit is zero, the receiver's PDU will update its TID cache entry. |
1 | Set the update remote cache bit to 1. When the bit is 1, the receiver's TID cache is not updated. |
Global configuration
This command first appeared in Cisco IOS Release 11.1.
The following example sets the update remote cache bit in the outgoing PDU to 1, so the cache at the receiver's end is not updated:
tarp urc 1
You can use the master indexes or search online for documentation of related commands.
Use the timers basic router configuration command to configure ISO IGRP timers. Use the no form of this command to restore the default values.
timers basic update-interval holddown-interval invalid-interval
update-interval | Time, in seconds, between the sending of routing updates. The default value is 90 seconds. |
holddown-interval | Time, in seconds, a system or area router is kept in holddown state, during which routing information regarding better paths is suppressed. (A router enters into a holddown state when an update packet is received that indicates the route is unreachable. The route is marked inaccessible and advertised as unreachable. However, the route is still used for forwarding packets.) When the holddown interval expires, routes advertised by other sources are accepted and the route is no longer inaccessible. The default value is 145 seconds. |
invalid-interval | Time, in seconds, that a route remains in the routing table after it has been determined that it is not reachable. After that length of time, the route is removed from the routing table. The default value is 135 seconds. |
update-interval = 90 seconds
holddown-interval = 145 seconds
invalid-interval = 135 seconds
Router configuration
This command first appeared in Cisco IOS Release 10.0.
Because the ISO IGRP routing protocol executes a distributed, asynchronous routing algorithm, it is important that these timers be the same for all routers in the network.
In the following example, updates are broadcast every 60 seconds. When an update packet is received that indicates the router is unreachable, the router will be in holddown state for 100 seconds before once more becoming accessible. If a router is not heard from in 130 seconds, the route is removed from the routing table.
router iso-igrp
timers basic 60 100 130
Use the trace privileged EXEC command to trace routes on a router configured with the ISO CLNS protocol.
traceThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The trace command terminates when the destination responds, when the maximum time to live (TTL) is exceeded, or when the user interrupts the trace with the escape sequence. The information is encoded as follows:
hop-count name(nsap) result-of-probe
The following display shows an example of ISO CLNS trace output:
router# trace
Protocol [ip]: clns
Target CLNS address: thoth
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Type escape sequence to abort.
Tracing the route to THOTH (55.0006.0100.0000.0000.0001.8888.1112.1314.1516)
HORUS(55.0006.0100.0000.0000.0001.6666.3132.3334.3536) 32 msec ! 28 msec
28 msec !
2 ISIS(55.0006.0100.0000.0000.0001.7777.2122.2324.2526) 56 msec ! 80 msec
56 msec !
3 THOTH(55.0006.0100.0000.0000.0001.8888.1112.1314.1516) 80 msec ! 80 msec ! 8
Table 65 describes the parameters that can be specified when using the trace dialog for CLNS.
| Field | Description |
|---|---|
Protocol [ip] | The default protocol for trace is IP. You must specify CLNS to begin tracing a router on a CLNS router. |
Target CLNS address | You can specify either an NSAP or host name. |
Timeout in seconds | You can specify the length of time to wait after sending each probe before giving up on getting a response. |
Probe count | You can specify the number of probes to be sent at each TTL level. The default is 3. |
Minimum Time to Live [1] | You can set the TTL value for the first probes. The default is 1. Set to a higher value to suppress the display of known hops. |
Maximum Time to Live [30] | You can set the largest TTL value that can be used. The default is 30. The trace command terminates when the destination is reached or when this value is reached. |
Table 66 describes characters that can appear in ISO CLNS output.
| Character | Description |
|---|---|
& | A time-to-live-exceeded error PDU was received. |
U | A destination unreachable error PDU was received. |
I | The user interrupted the test. |
* | The probe timed out. |
C | A congestion experienced packet was received. |
You can use the master indexes or search online for documentation of related commands.
Use the trace user EXEC command to discover the CLNS routes that packets will actually take when traveling to their destination.
trace clns destination
destination | Destination address or host name on the command line. The default parameters for the appropriate protocol are assumed and the tracing action begins. |
clns | CLNS keyword. |
User EXEC
This command first appeared in Cisco IOS Release 10.0.
The trace command works by taking advantage of the error messages generated by the Cisco IOS software and when a datagram exceeds its Time-to-Live (TTL) value.
The trace command starts by sending probe datagrams with a TTL value of 1. This causes the first software to discard the probe datagram and send back an error message. The trace command sends several probes at each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet can result in one or two error messages. A time exceeded error message indicates that an intermediate router has seen and discarded the probe. A destination unreachable error message indicates that the destination node has received the probe and discarded it because it could not deliver the packet. If the timer goes off before a response comes in, trace prints an asterisk (*).
The following display shows sample CLNS trace output when a destination host name has been specified:
router# trace clns ABA.NYC.mil
Type escape sequence to abort.
Tracing the route to ABA.NYC.mil (26.0.0.73)
1 DEBRIS.CISCO.COM (131.108.1.6) 1000 msec 8 msec 4 msec
2 BARRNET-GW.CISCO.COM (131.108.16.2) 8 msec 8 msec 8 msec
3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec
4 BB2.SU.BARRNET.NET (131.119.254.6) 8 msec 8 msec 8 msec
5 SU.ARC.BARRNET.NET (131.119.3.8) 12 msec 12 msec 8 msec
6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec
7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
Table 67 describes the fields shown in the display.
| Field | Description |
|---|---|
1 | Indicates the sequence number of the router in the path to the router. |
DEBRIS.CISCO.COM | Host name of this router. |
131.108.1.6 | Internetwork address of this router. |
1000 msec 8 msec 4 msec | Round-trip time for each of the three probes that are sent. |
Table 68 describes the characters that can appear in trace output.
| Character | Description |
|---|---|
nn msec | For each node, the round-trip time in milliseconds for the specified number of probes. |
* | The probe timed out. |
? | Unknown packet type. |
Q | Source quench. |
P | Protocol unreachable. |
N | Network unreachable. |
U | Port unreachable. |
H | Host unreachable. |
You can use the master indexes or search online for documentation of related commands.
Use the which-route EXEC command if you want to know which next-hop router will be used or if you have multiple processes running and want to troubleshoot your configuration. This command displays the routing table in which the specified CLNS destination is found.
which-route {nsap-address | clns-name}
nsap-address | CLNS destination network address. |
clns-name | Destination host name. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
Route information can reside in the following tables:
The following example shows that destination information for router gray is found in the IS-IS Level 1 routing table. The destination is on the local system.
gray# which-route gray
Route look-up for destination 39.0001.0000.0c00.bda8.00, GRAY
Found route in IS-IS level-1 routing table - destination is local
The following example shows that destination information for NSAP address 49.0001.0000.0c00.bda8.00 is found in the ISO IGRP Level 1 routing table. The destination is on the local system.
gray# which-route 49.0001.0000.0c00.bda8.00
Route look-up for destination 49.0001.0000.0c00.bda8.00
Found route in ISO IGRP routing table - destination is local
The following example shows that destination information for router green is found in the IS-IS Level 1 routing table. The destination is not on the local system. Table 69 describes the display fields in the adjacency entry used to reach system green.
gray# which-route green
Route look-up for destination 39.0001.0000.0c00.7f06.00, GREEN
Found route in IS-IS level-1 routing table
Adjacency entry used:
System Id SNPA Interface State Holdtime Type Protocol
GREEN 0000.0c00.2d55 Ethernet0 Up 91 L1L2 IS-IS
Area Address(es): 39.0001
| Field | Description |
|---|---|
System ID | Six-byte value that identifies a system in an area. A name is displayed in this field if one has been assigned with the clns host global configuration command. |
SNPA | SNPA data link address. |
Interface | Interface from which system information was learned. |
State | State of the ES or IS. Possible values are as follows: Init—The system is an IS and is waiting for an IS-IS hello message. The neighbor to the IS-IS is not adjacent. Up—The ES or IS is reachable. |
Holdtime | Number of seconds for which the information is valid. |
Type | Adjacency type. Possible values are as follows: ES—An end-system adjacency that is either discovered by the ES-IS protocol or statically configured. IS—A router adjacency that is either discovered by the IS-IS protocol or is statically configured. L1—A router adjacency for Level 1 routing only. L1L2—A router adjacency for Level 1 and Level 2 routing. L2—A router adjacency for Level 2 only. |
Protocol | Protocol through which the adjacency was learned. Valid protocol sources are ES-IS, IS-IS, ISO IGRP, and Static. |
The following example shows that destination information for NSAP address 49.0001.1111.1111.1111.00 is found in the ISO IGRP routing table. Table 69 describes the display fields in the adjacency entry used to reach NSAP address 49.0001.1111.1111.1111.00.
gray# which-route 49.0001.1111.1111.1111.00
Route look-up for destination 49.0001.1111.1111.1111.00
Found route in ISO IGRP routing table
Adjacency entry used:
System Id SNPA Interface State Holdtime Type Protocol
1111.1111.1111 0000.0c01.151d Ethernet1 Up 38 L1L2 ISO IGRP
Area Address(es): 49.0001
The following example indicates that the specified address is not found in a routing table:
gray# which-route 47.0003.0000.0000.0000.00
Route look-up for destination 47.0003.0000.0000.0000.00
Route not found
The following example indicates that the specified NSAP address was found in the CLNS prefix routing table. This information is followed by the route entry used to reach NSAP address 49.0003.0000.0000.0000.00.
gray# which-route 49.0003.0000.0000.0000.00
Route look-up for destination 49.0003.0000.0000.0000.00
Found route in CLNS prefix routing table
Route entry used:
49 [10/0]
via 1111.1111.1111, Ethernet1, Static
You can use the master indexes or search online for documentation of related commands.
Posted: Tue Nov 28 11:29:04 PST 2000
Copyright 1989-2000©Cisco Systems Inc.