Table Of Contents
ignore-lsp-errors
interface ctunnel
ip domain-lookup nsap
isis adjacency-filter
iso-igrp adjacency-filter
log-adjacency-changes (ISO CLNS)
lsp-mtu (ISO CLNS)
match clns address
match clns next-hop
match clns route-source
match interface (ISO CLNS)
match metric (ISO CLNS)
match route-type (ISO CLNS)
metric weights (ISO CLNS)
redistribute (ISO CLNS)
route-map (ISO CLNS)
router iso-igrp
set level (ISO CLNS)
set metric (ISO CLNS)
set metric-type (ISO CLNS)
set tag (ISO CLNS)
show clns
show clns cache
show clns es-neighbors
show clns filter-expr
show clns filter-set
show clns interface
show clns is-neighbors
show clns neighbor areas
show clns neighbors
show clns protocol
show clns route
show clns traffic
show isis routes
show route-map
show tarp
show tarp blacklisted-adjacencies
ignore-lsp-errors
To allow the router to ignore Intermediate System-to-Intermediate System (IS-IS) link-state packets that are received with internal checksum errors rather than purging the link-state packets, use the ignore-lsp-errors command in router configuration mode. To disable this function, use the no form of this command.
ignore-lsp-errors
no ignore-lsp-errors
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default; that is, corrupted LSPs are dropped instead of purged for network stability.
Command Modes
Router configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.0
|
This command is now enabled by default.
|
Usage Guidelines
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 command 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.
If you want to explicitly purge the corrupted LSPs, issue the no ignore-lsp-errors command.
Examples
The following example instructs the router to ignore link-state packets that have internal checksum errors:
interface ctunnel
To create a virtual interface to transport IP over a CLNS tunnel (CTunnel), use the interface ctunnel command in global configuration mode. To remove the virtual interface, use the no form of this command.
interface ctunnel interface-number
no interface ctunnel interface-number
Syntax Description
interface-number
|
CTunnel interface number (a number from 0 through 2,147,483,647).
|
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
When configuring an IP over CLNS tunnel, you must first create a virtual interface. In the following example, the interface ctunnel command is used to create the virtual interface.
Examples
The following example configures a CTunnel from one router to another and shows the CTunnel destination set to 49.0001.1111.1111.1111.00:
ip address 10.0.0.3 255.255.255.0
ctunnel destination 49.0001.1111.1111.1111.00
Related Commands
Command
|
Description
|
clns routing
|
Enables routing of CLNS packets.
|
ctunnel destination
|
Configures the destination parameter for a CLNS tunnel.
|
debug ctunnel
|
Displays debug messages for the IP over a CLNS Tunnel feature.
|
ip address
|
Sets a primary or secondary IP address for an interface.
|
ip routing
|
Enables IP routing.
|
ip domain-lookup nsap
To allow Domain Name System (DNS) queries for CLNS addresses, use the ip domain-lookup nsap command in global configuration mode. To disable this function, use the no form of this command.
ip domain-lookup nsap
no ip domain-lookup nsap
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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 given a host name. This feature is useful for the ISO CLNS ping EXEC command and when making CLNS Telnet connections.
Examples
The following example disables DNS queries of CLNS addresses:
Related Commands
Command
|
Description
|
ip domain-lookup
|
Enables the IP DNS-based host name-to-address translation.
|
ping (privileged)
|
Diagnoses basic network connectivity on Apollo, AppleTalk, CLNS, DECnet, IP, Novell IPX, VINES, or XNS networks.
|
redistribute (ISO CLNS)
|
Redistributes routing information from one domain into another routing domain.
|
isis adjacency-filter
To filter the establishment of Intermediate System-to-Intermediate System (IS-IS) adjacencies, use the isis adjacency-filter command in interface configuration mode. To disable filtering of the establishment of IS-IS adjacencies, use the no form of this command.
isis adjacency-filter name [match-all]
no isis adjacency-filter name [match-all]
Syntax Description
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.
|
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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 the match-all keyword 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.
Examples
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.**
isis adjacency-filter ourfriends
Related Commands
Command
|
Description
|
clns adjacency-filter
|
Filters the establishment of CLNS ES and IS adjacencies.
|
clns filter-expr
|
Combines CLNS filter sets and CLNS address templates to create complex logical NSAP pattern-matching expressions.
|
clns filter-set
|
Builds a list of CLNS address templates with associated permit and deny conditions for use in CLNS filter expressions.
|
clns template-alias
|
Builds a list of alphanumeric aliases of CLNS address templates for use in the definition of CLNS filter sets.
|
iso-igrp adjacency-filter
|
Filters the establishment of ISO IGRP adjacencies.
|
iso-igrp adjacency-filter
To filter the establishment of ISO IGRP adjacencies, use the iso-igrp adjacency-filter command in interface configuration mode. To disable filtering of the establishment of ISO IGRP adjacencies, use the no form of this command.
iso-igrp adjacency-filter name
no iso-igrp adjacency-filter name
Syntax Description
name
|
Name of the filter set or expression to apply.
|
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Examples
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.**
iso-igrp adjacency-filter ourfriends
Related Commands
Command
|
Description
|
clns adjacency-filter
|
Filters the establishment of CLNS ES and IS adjacencies.
|
clns filter-expr
|
Combines CLNS filter sets and CLNS address templates to create complex logical NSAP pattern-matching expressions.
|
clns filter-set
|
Builds a list of CLNS address templates with associated permit and deny conditions for use in CLNS filter expressions.
|
clns template-alias
|
Builds a list of alphanumeric aliases of CLNS address templates for use in the definition of CLNS filter sets.
|
isis adjacency-filter
|
Filters the establishment of IS-IS adjacencies.
|
log-adjacency-changes (ISO CLNS)
To cause Intermediate System-to-Intermediate System (IS-IS) to generate a log message when an Netware Link Services Protocol (NLSP) IS-IS adjacency changes state (up or down), use the log-adjacency-changes command in router configuration mode. To disable this function, use the no form of this command.
log-adjacency-changes
no log-adjacency-changes
Syntax Description
This command has no arguments or keywords.
Defaults
Does not log adjacency changes
Command Modes
Router configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
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
Examples
The following example instructs the router to log adjacency changes:
Related Commands
Command
|
Description
|
logging
|
Logs messages to a syslog server host.
|
lsp-mtu (ISO CLNS)
To set the maximum transmission unit (MTU) size of Intermediate System-to-Intermediate System (IS-IS) link-state packets (LSPs), use the lsp-mtu command in router configuration mode. To disable this function, use the no form of this command.
lsp-mtu size
no lsp-mtu
Syntax Description
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.
|
Defaults
1497 bytes
Command Modes
Router configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
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.
Note
This rule applies for all routers in a network. If any link in the network has a reduced MTU, all routers must be changed, not just the routers directly connected to the link.
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.
Examples
The following example sets the MTU size to 1300 bytes:
Related Commands
Command
|
Description
|
clns mtu
|
Sets the MTU packet size for the interface.
|
mtu
|
Adjusts the maximum packet size or MTU size.
|
match clns address
To define the match criterion, use the match clns address command in route-map configuration mode. Routes that have a network address matching one or more of the names—and that satisfy all other defined match criteria—will be redistributed. To remove the match criterion, use the no form of this command.
match clns address name [name...name]
no match clns address name [name...name]
Syntax Description
name
|
Name of a standard access list, filter set, or expression.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the CLNS address matching criterion:
redistribute iso-igrp remote route-map ourmap
match clns address ourprefix
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
match clns next-hop
To define the next-hop match criterion, use the match clns next-hop command in route-map configuration mode. Routes that have a next-hop router address matching one of the names—and that satisfy all other defined match criteria—will be redistributed. To remove the match criterion, use the no form of this command.
match clns next-hop name [name...name]
no match clns next-hop name [name...name]
Syntax Description
name
|
Name of an access list, filter set, or expression.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the CLNS next-hop matching criterion:
redistribute iso-igrp remote route-map ourmap
match clns next-hop ourprefix
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
match clns route-source
To define the route-source match criterion, use the match clns route-source command in route-map configuration mode. 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. To remove the specified match criterion, use the no form of this command.
match clns route-source name [name...name]
no match clns route-source name [name...name]
Syntax Description
name
|
Name of access list, filter set, or expression.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the CLNS route-source matching criterion:
redistribute iso-igrp remote route-map ourmap
match clns route-source ourprefix
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
match interface (ISO CLNS)
To define the interface match criterion, use the match interface command in route-map configuration mode. Routes that have the next hop out one of the interfaces specified—and that satisfy all other defined match criteria—will be redistributed. To remove the specified match criterion, use the no form of this command.
match interface type number [type number...type number]
no match interface type number [type number...type number]
Syntax Description
type
|
Interface type.
|
number
|
Interface number.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the interface (ISO CLNS) matching criterion:
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
match interface ethernet2
Related Commands
match metric (ISO CLNS)
To define the metric match criterion, use the match metric command in route-map configuration mode. Routes that have the specified metric—and satisfy all other defined match criteria—will be redistributed. To remove the specified match criterion, use the no form of this command.
match metric metric-value
no match metric metric-value
Syntax Description
metric-value
|
Route metric. This can be an Interior Gateway Routing Protocol (IGRP) five-part metric.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the metric (ISO CLNS) matching criterion:
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
match route-type (ISO CLNS)
To define the route-type match criterion, use the match route-type command in route-map configuration mode. Routes that have the specified route type—and satisfy all other defined match criteria—will be redistributed. To remove the specified match criterion, use the no form of this command.
match route-type {level-1 | level-2}
no match route-type {level-1 | level-2}
Syntax Description
level-1
|
IS-IS Level 1 routes.
|
level-2
|
IS-IS Level 2 routes.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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. The no route-map command deletes the route map.
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 argument given with the set commands. The no forms of the match commands remove the specified match criteria.
Examples
In the following configuration, an ISO IGRP-learned route with a prefix 49.0001.0002 will be redistributed if it satisfies the route-type (ISO CLNS) matching criterion:
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
metric weights (ISO CLNS)
To specify different metrics for the ISO IGRP routing protocol on CLNS, use the metric weights command in router configuration mode. This command allows you to configure the metric constants used in the ISO IGRP composite metric calculation of reliability and load. To return the five k arguments to their default values, use the no form of this command.
metric weights qos k1 k2 k3 k4 k5
no metric weights
Syntax Description
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.
|
Defaults
qos: 0
k1: 1
k2: 0
k3: 1
k4: 0
k5: 0
Command Modes
Router configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Two additional ISO IGRP metrics can be configured. These are the bandwidth and delay associated with an interface.
Note
Using the bandwidth and delay interface configuration commands to change the values of the ISO IGRP metrics also changes the values of IP IGRP metrics.
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 9600 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 30 lists the default values used for several common media.
Table 30 Bandwidth Values by Media Type
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.
Examples
The following example sets all five metric constants:
metric weights 0 2 0 1 0 0
Related Commands
Command
|
Description
|
bandwidth (interface)
|
Sets a bandwidth value for an interface.
|
delay
|
Sets a delay value for an interface.
|
redistribute (ISO CLNS)
To redistribute routes from one routing domain into another routing domain, use the redistribute command in router configuration mode. To disable redistribution, or to disable any of the specified keywords, use the no form of this command.
redistribute protocol [tag] [route-map map-tag]
no redistribute protocol [tag] [route-map map-tag] static [clns | ip]
Syntax Description
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, Cisco IOS software injects 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.
|
Defaults
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.
Command Modes
Router configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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 command is performed. Redistribution only occurs for Level 2 routing.
You can specify more than one IS-IS process per router. Cisco IOS Release 12.1 provides multi-area support where each IS-IS process can handle a separate level-1 area. To create more than one level-1 IS-IS routing process, use the clns router isis command in interface configuration mode. You must use the area tag argument for multiarea IS-IS configuration, in order to define a meaningful name for each routing process. See the clns router isis command earlier in this chapter for more information.
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.
Examples
The following example illustrates redistribution of ISO IGRP routes of Michigan and ISO IGRP routes of Ohio into the IS-IS area tagged 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:
redistribute iso-igrp Germany
In the following example, the router advertises any static routes it knows about in the Chicago domain:
Related Commands
Command
|
Description
|
route-map (ISO CLNS)
|
Defines the conditions for redistributing routes from one routing protocol into another.
|
route-map (ISO CLNS)
To define the conditions for redistributing routes from one routing protocol into another, use the route-map command in global configuration mode. To delete the route map, use the no form of this command.
route-map map-tag {permit | deny} sequence-number
no route-map map-tag {permit | deny} sequence-number
Syntax Description
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.
|
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Related Commands
router iso-igrp
To identify the area that the router will work in and let it know that it will be routing dynamically using the ISO IGRP protocol, use the router iso-igrp command in global configuration mode. To disable ISO IGRP routing for the system, use the no form of this command with the appropriate tag.
router iso-igrp [tag]
no router iso-igrp [tag]
Syntax Description
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.
|
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Creating a name for a routing process means that you use names when configuring routing. You can specify up to ten ISO IGRP processes.
Examples
The following example specifies a router in Manufacturing. The command must be typed on one line.
router iso-igrp Manufacturing
Related Commands
Command
|
Description
|
clns router iso-igrp
|
Specifies ISO IGRP routing on a specified interface.
|
redistribute (ISO CLNS)
|
Redistributes routing information from one domain into another routing domain.
|
set level (ISO CLNS)
To specify the routing level of routes to be advertised into a specified area of the routing domain, use the set level command in route-map configuration mode. To disable advertising the specified routing level into a specified area, use the no form of this command.
set level {level-1 | level-2 | level-1-2}
no set level {level-1 | level-2 | level-1-2}
Syntax Description
level-1
|
Inserted in IS-IS Level 1 link-state PDUs.
|
level-2
|
Inserted in IS-IS Level 2 link-state PDUs. For IS-IS destinations, level-2 is the default.
|
level-1-2
|
Inserted into both Level 1 and Level 2 IS-IS link-state PDUs.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Examples
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:
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
match clns address ourprefix
access-list 1 permit 160.89.0.0 0.0.255.255
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
set metric (ISO CLNS)
To change the metric value used to redistribute routes, use the set metric command in route-map configuration mode. To reinstate the original metric values, use the no form of this command.
set metric metric-value
no set metric metric-value
Syntax Description
metric-value
|
Route metric. This can be an IGRP five-part metric.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Examples
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:
redistribute rip route-map ourmap
redistribute iso-igrp remote route-map ourmap
match clns address ourprefix
access-list 1 permit 160.89.0.0 0.0.255.255
clns filter-set ourprefix permit 49.0001.0002...
Related Commands
set metric-type (ISO CLNS)
To set the metric type for redistributed routes, use the set metric-type command in route-map configuration mode. To reinstate the original metric type, use the no form of this command.
set metric-type {internal | external}
no set metric-type {internal | external}
Syntax Description
internal
|
IS-IS internal metric.
|
external
|
IS-IS external metric.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Examples
The following example sets the metric type of the destination protocol to IS-IS internal metric:
Related Commands
set tag (ISO CLNS)
To set a tag value to associate with the redistributed routes, use the set tag command in route-map configuration mode. To revert to redistributing routes without associating a specific tag with them, use the no form of this command.
set tag tag-value
no set tag tag-value
Syntax Description
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.
|
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
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.
Examples
The following example sets the tag value of the destination routing protocol to 5:
Related Commands
show clns
To display information about the CLNS network, use the show clns command in EXEC mode.
show clns
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show clns command:
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
Routing for Area: 39.0004.0030
Table 31 describes significant fields shown in the display.
Table 31 show clns Field Descriptions
Field
|
Description
|
2 Interfaces Enabled for CLNS
|
Indicates how many interfaces have the CLNS 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.
|
show clns cache
To display the CLNS route cache, use the show clns cache command in EXEC mode. The cache contains an entry for each destination that recently has been fast-switched. 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 | invalidations]
Syntax Description
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.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show clns cache command:
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 @ Ethernet0/1: 0000.0c00.6fa5
Table 32 describes significant fields shown in the display.
Table 32 show clns cache Field Descriptions
Field
|
Description
|
CLNS routing cache version 433
|
Number identifying this particular CLNS routing cache.
|
Destination ->
Next hop
@ Interface:
SNPA Address
Rewrite / Length
|
Destination NSAP for the packet.
Next hop system ID used to reach the destination.
Interface through which the router transmitted the packet.
Address of the subnetwork point of attachment (SNPA) of the next hop for this destination NSAP.
Interface encapsulation data and length of the cache entry that the cache must overwrite onto the outgoing frame prior to sending it. If the rewrite length of the cache entry is zero, this field will not be displayed.
|
[42]
|
Cache location for this entry.
|
*39.0004.0040.0000.0C00.2D55.001
|
Destination NSAP address.
|
ISOLATOR
|
Destination host name.
|
0000.0C00.2D55
|
System ID of the next-hop router.
|
Ethernet0/1
|
Interface through which the router transmitted the packet.
|
000.0c00.6fa5
|
SNPA for the next-hop router through the output interface.
|
The following is sample output from the show clns cache delay-parameters command:
Minimum invalidation interval 2 seconds,
Maximum invalidation interval 5 seconds,
Quiet interval 3 seconds,
Invalidation rate 3 in last second, 3 in last 3 seconds
Table 33 describes significant fields shown in the display.
Table 33 show clns cache delay-parameters Field Descriptions
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
Table 34 describes significant fields shown in the display.
Table 34 show clns cache invalidations Field Descriptions
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.
|
Related Commands
Command
|
Description
|
clear clns cache
|
Clears and reinitializes the CLNS routing cache.
|
show clns es-neighbors
To list the ES neighbors that this router knows about, use the show clns es-neighbors command in EXEC mode.
show clns area-tag es-neighbors [type number] [detail]
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or Connectionless Network Service (CLNS) router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
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.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(5)T
|
The area-tag argument was added.
|
Examples
The following is sample output from the show clns es-neighbors command when Ethernet interface 0 is specified:
Router# show clns es-neighbors ethernet0
System Id Interface State Type Format
0800.2B14.060E Ethernet0 Up ES Phase V
0800.2B14.0528 Ethernet0 Up ES Phase V
Table 35 describes the significant fields shown in the display.
Table 35 show clns es-neighbors Field Descriptions
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.
Related Commands
Command
|
Description
|
clear clns es-neighbors
|
Removes ES neighbor information from the adjacency database.
|
clns es-neighbor
|
Defines all end systems that will be used when you manually specify the NSAP-to-SNPA mapping.
|
show clns filter-expr
To display one or all currently defined CLNS filter expressions, use the show clns filter-expr command in EXEC mode.
show clns filter-expr [name] [detail]
Syntax Description
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.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
The show clns filter-expr detail command would yield the following output:
Router# show clns filter-expr detail
ADULTS = (FRED or BARNEY) or (WILMA or BETTY)
Related Commands
Command
|
Description
|
clns filter-expr
|
Combines CLNS filter sets and CLNS address templates to create complex logical NSAP pattern-matching expressions.
|
show clns filter-set
To display one or all currently defined CLNS filter sets, use the show clns filter-set command in EXEC mode.
show clns filter-set [name]
Syntax Description
name
|
(Optional) Name of the filter set to display. If none is specified, all are displayed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
Related Commands
Command
|
Description
|
clns filter-set
|
Builds a list of CLNS address templates with associated permit and deny conditions for use in CLNS filter expressions.
|
show clns interface
To list the CLNS-specific information about each interface, use the show clns interface command in EXEC mode.
show clns interface [type number]
Syntax Description
type
|
(Optional) Interface type.
|
number
|
(Optional) Interface number.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
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 36 describes significant fields shown in the display.
Table 36 show clns interface Field Descriptions
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
|
(Second interface). Shown to be up, and the line protocol is up.
|
Serial 2 is up, line protocol is up
|
(Third interface). Shown to be up, and the line protocol 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.
|
show clns is-neighbors
To display Intermediate System-to-Intermediate System (IS-IS) related information for IS-IS router adjacencies, use the show clns is-neighbors command in EXEC mode. Neighbor entries are sorted according to the area in which they are located.
show clns area-tag is-neighbors [type number] [detail]
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or CLNS router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
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.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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 37 describes significant fields shown in the display.
Table 37 show clns is-neighbors Field Descriptions
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
0800.2B16.24EA Ethernet0 Up L1L2 64/64 0800.2B16.24EA.01 Phase V
Area Address(es): 47.0004.004D.0001
0000.0C00.3E51 Serial1 Up L2 0 04 Phase V
Area Address(es): 39.0004
000.0C00.62E6 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V
Area Address(es): 47.0004.004D.0001
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.
Related Commands
Command
|
Description
|
clear clns is-neighbors
|
Removes IS neighbor information from the adjacency database.
|
clns is-neighbor
|
Defines all intermediate systems that will be used when you manually specify the NSAP-to-SNPA mapping.
|
show clns neighbor areas
To display information about Intermediate System-to-Intermediate System (IS-IS) neighbors and the areas to which they belong, use the show clns neighbor areas command in EXEC mode.
show clns area-tag neighbor areas
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or CLNS router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Use the show clns neighbor areas command to verify that all expected adjacencies are up with all neighbors. If they are not, recheck the area addresses specified in both routers. If the router is running in dual CLNS-IP mode in an area, verify that a valid IP address is configured on each interface in the area. Consider using the debug isis adjacency command to gather additional information.
Examples
The following example shows output when two Level 1 and one Level 2 IS-IS areas are configured.
Router# show clns neighbor areas
System Id Interface Area Name State Holdtime Type Protocol
0000.0000.0009 Tu529 L2BB Up 26 L1L2 IS-IS
0000.0000.0053 Et1 A3253-01 Up 21 L1 IS-IS
0000.0000.0003 Et1 A3253-01 Up 28 L1 IS-IS
0000.0000.0002 Et2 A3253-02 Up 22 L1 IS-IS
0000.0000.0053 Et2 A3253-02 Up 23 L1 IS-IS
Table 38 describes the significant fields shown in the display.
Table 38 show clns neighbor areas Field Descriptions
Field
|
Descriptions
|
System Id
|
Identification value of the system.
|
Interface
|
Interface on which the router was discovered.
|
Area Name
|
Name of the area in which the system is configured.
|
State
|
Adjacency state. Up and Init are the states. See the show clns neighbors description.
|
Init
|
System is waiting for an IS-IS hello message.
|
Up
|
Believes the system is reachable.
|
Holdtime
|
Number of seconds before this adjacency entry times out.
|
Type
|
L1, L2, and L1L2 type adjacencies.
|
ES
|
End-system adjacency either discovered by the ES-IS protocol or statically configured.
|
IS
|
Router adjacency either discovered by 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, International Standards Organization Interior Gateway Routing Protocol (ISO IGRP), static, and DECnet.
|
Related Commands
show clns neighbors
To display both ES and IS neighbors, use the show clns neighbors command in EXEC mode.
show clns area-tag neighbors [type number] [area] [detail]
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or CLNS router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
type
|
(Optional) Interface type.
|
number
|
(Optional) Interface number.
|
area
|
(Optional) When specified, the CLNS multiarea adjacencies are displayed.
|
detail
|
(Optional) When specified, the area addresses advertised by the neighbor in the hello messages is displayed. Otherwise, a summary display is provided.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(5)T
|
The area and detail keywords were added.
|
Examples
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 SNPA Interface State Holdtime Type Protocol
0000.0000.0007 aa00.0400.6408 Ethernet0 Init 277 IS ES-IS
0000.0C00.0C35 0000.0c00.0c36 Ethernet1 Up 91 L1 IS-IS
0800.2B16.24EA aa00.0400.2d05 Ethernet0 Up 29 L1L2 IS-IS
0800.2B14.060E aa00.0400.9205 Ethernet0 Up 1698 ES ES-IS
0000.0C00.3E51 *HDLC* Serial1 Up 28 L2 IS-IS
0000.0C00.62E6 0000.0c00.62e7 Ethernet1 Up 22 L1 IS-IS
0A00.0400.2D05 aa00.0400.2d05 Ethernet0 Init 24 IS ES-IS
Table 39 describes the fields shown in the display.
Table 39 show clns neighbors Field Descriptions
Field
|
Description
|
System Id
|
Six-byte value that identifies a system in an area.
|
SNPA
|
Subnetwork Point of Attachment. This is the data link address.
|
Interface
|
Interface in which the system was learned from.
|
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
0102.5555.0036 Et1/1 0030.80aa.9b81 Up 23 L1 IS-IS
IP Address(es): 175.1.19.36*
0000.0000.0001 Et1/1 0030.9655.201d Up 23 L1L2 IS-IS
Area Address(es): 49.0002
IP Address(es): 172.16.19.22* 10.12.33.54 10.120.33.253
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 IS neighbor and its uptime. 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.
Related Commands
Command
|
Description
|
clear clns neighbors
|
Removes CLNS neighbor information from the adjacency database.
|
show clns protocol
To list the protocol-specific information for each ISO IGRP or Intermediate System-to-Intermediate System (IS-IS) routing process in the router, use the show clns protocol command in EXEC mode. There will always be at least two routing processes, a Level 1 and a Level 2, and there can be more.
show clns [domain | area-tag] protocol
Syntax Description
domain
|
(Optional) Particular ISO IGRP routing domain.
|
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or Connectionless Network Service (CLNS) router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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:
ISO IGRP Level 2 Router: DOMAIN_remote
Routing for domain: 39.0003
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:
System Id: 0000.0C00.224D.00 IS-Type: level-1-2
Routing for area address(es):
Interfaces supported by IS-IS:
Next global update in 530 seconds
Table 40 describes significant fields shown in the display.
Table 40 show clns protocol Field Descriptions
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 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 41 describes significant fields shown in the IS-IS portion of the display.
Table 41 show clns protocol with IS-IS Field Descriptions
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.
|
show clns route
To display one or all of the destinations to which this router knows how to route CLNS packets, use the show clns route command in EXEC mode.
show clns route nsap
Syntax Description
nsap
|
CLNS network service access point (NSAP) address.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(5)T
|
Fields for displaying information about prefix routes were added or changed.
|
Usage Guidelines
The show clns route command shows the Intermediate System-to-Intermediate System (IS-IS) Level 2 routing table and static and Intermediate System-to-Intermediate System Interior Gateway Routing Protocol (ISO-IGRP) learned prefix routes. This table stores IS-IS area addresses and prefix routes.
Examples
The following is sample output from the show clns route command when the nsap argument is not used:
ISO-IGRP Routing Table for Domain 49.0002, Area 0007
System Id Next-Hop SNPA Interface Metric State
milles milles *HDLC* Se1 8476 Up
0000.0000.0007 milles *HDLC* Se1 10476 Up
rips 0000.0000.0000 -- -- 0 Up
ISO-IGRP Routing Table for Domain 49.0002
Area Id Next-Hop SNPA Interface Metric State
0002 0000.0000.0000 -- -- 0 Up
Codes: C - connected, S - static, d - DecnetIV
I - ISO-IGRP, i - IS-IS, e - ES-IS
C 49.0002 [2/0], Local ISO-IGRP Domain
C 49.0001.0000.0000.0005.00 [1/0], Local IS-IS NET
C 49.0002.0007.0000.0000.0005.00 [1/0], Local ISO-IGRP NET
C 49.0001 [2/0], Local IS-IS Area
S 50.1234 [10/0], Discard Entry
I 55.5555.5555 [100/8476]
S 77.7777.7777.7777 [10/0]
d 88.8888.8888.0007 [120/0], DecnetIV Entry
Table 42 describes the significant fields shown in the display.
Table 42 show clns route Field Descriptions
Field
|
Description
|
Domain 49.0002
|
The ISO-IGRP routing domain for which we are displaying the routes.
|
Area 0007
|
The ISO-IGRP area in which the displayed the Level 1 host routes are.
|
System Id
|
Identification value of the system listed in the Level 1 forwarding table.
|
Area Id
|
The identification value of the area listed in the area forwarding table.
|
Next-Hop
|
System ID of the best cost next-hop to listed address.
|
SNPA
|
MAC address of the next-hop system.
|
Interface
|
Interface through which next-hop system is known.
|
Metric
|
ISO-IGRP cost to reach the destination.
|
State
|
Up (active) or Down (nonoperational).
|
Table 43 describes the codes as they appear in the previous display.
Table 43 prefix routes Field Descriptions
Field
|
Description
|
C (connected)
|
The domain, area, or NET was learned via local configuration.
|
S (static)
|
The destination was learned via a locally configured static route.
|
d (DECnet IV)
|
The destination is a converted DECnet phase IV area address.
|
I (ISO-IGRP)
|
The destination is a prefix learned via Level 2 ISO-IGRP.
|
i (IS-IS)
|
The destination is a prefix learned via Level 2 IS-IS.
|
e (ES-IS)
|
The destination is learned via end system-intermediate system (ES-IS) redirects.
|
33.3333.3333
|
Destination prefix.
|
[110/10]
|
Administrative distance/metric.
|
via bakel
|
Next-hop system via which this destination is reachable. Shown as a 6-byte system ID, or as symbolic name (if available).
|
Ethernet0
|
Outgoing interface via which this destination is reachable.
|
Local IS-IS NET
|
Prefix is the full NET configured under an IS-IS process.
|
Field
|
Description
|
Local ISO-IGRP NET
|
Prefix is the full NET configured under an ISO-IGRP process.
|
Local ISO-IGRP Domain
|
Prefix is the domain part of a locally configured ISO-IGRP NET. This prefix is installed for redistribution purposes.
|
Local IS-IS Area
|
Prefix is the area address of a locally configured IS-IS NET. This prefix is installed for redistribution purposes.
|
Discard Entry
|
Prefix is learned via a locally configured static discard entry.
|
DecnetIV Entry
|
Prefix is a combination of the locally configured DECnet conversion prefix and a dynamically learned DECnet IV route. This prefix is installed for redistribution purposes.
|
The following is sample output showing a single CLNS route using the show clns route command with the nsap argument:
Router# show clns route 33.3333.3333
Routing entry for 33.3333.3333
Known via "isis", distance 110, metric 10, Dynamic Entry
Routing Descriptor Blocks:
isis, route metric is 10, route version is 4
Table 44 describes the significant fields shown in the display.
Table 44 show clns route Field Descriptions
Field
|
Description
|
Routing entry for 33.3333.3333
|
The prefix route being examined.
|
Known via "isis", distance 110, metric 10, Dynamic Entry
|
This route was learned from an IS-IS routing process. The administrative distance is 110. The cost to reach the destination is 10.
|
Routing Descriptor Blocks
|
Each destination in the CLNS routing table can be reached by one or more paths. Each path is stored in a Routing Descriptor Block. The maximum number of paths in CLNS is 6.
|
via bakel, Ethernet0
|
Next-hop is neighbor "bakel." Outgoing interface is Ethernet0.
|
Redistributing via
|
Protocols other than originating protocol that advertise this prefix.
|
isis, route metric is 10, route version is 4
|
Originating protocol, cost for this path, route version in case this is an IS-IS route.
|
Related Commands
show clns traffic
To list the CLNS packets that this router has seen, use the show clns traffic command in EXEC mode.
show clns area-tag traffic
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or CLNS router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
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 45 describes significant fields shown in the display.
Table 45 show clns traffic Field Descriptions
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.
|
show isis routes
To display the Intermediate System-to-Intermediate System (IS-IS) Level 1 forwarding table for IS-IS learned routes, use the show isis routes command in EXEC mode.
show isis area-tag routes
Syntax Description
area-tag
|
Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or Connectionless Network Service (CLNS) router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show isis routes command:
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 46 describes significant fields shown in the display.
Table 46 show isis routes Field Descriptions
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).
|
show route-map
To display all route maps configured or only the one specified, use the show route-map command in EXEC mode.
show route-map [map-name]
Syntax Description
map-name
|
(Optional) Name of a specific route map.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show route-map command:
route-map sid, permit, sequence 10
route-map sid, permit, sequence 20
Table 47 describes the fields shown in the display:
Table 47 show route-map Field Descriptions
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: tag
|
Match criteria—conditions under which redistribution is allowed for the current route map.
|
Set clauses: metric
|
Set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met.
|
Related Commands
Command
|
Description
|
redistribute (ISO CLNS)
|
Redistributes routing information from one domain into another routing domain.
|
route-map (ISO CLNS)
|
Defines the conditions for redistributing routes from one routing protocol into another.
|
show tarp
To display all global TID Address Resolution Protocol (TARP) parameters, use the show tarp command in EXEC mode.
show tarp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is sample output from the show tarp command:
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 48 describes the fields shown in the display.
Table 48 show tarp Field Descriptions
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.
|
show tarp blacklisted-adjacencies
To list all adjacencies that have been blacklisted (that is, adjacencies that this router will not propagate TARP PDUs to) by the tarp blacklist-adjacency command, use the show tarp blacklisted-adjacencies command in EXEC mode.
show tarp blacklisted-adjacencies
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
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 49 describes the field shown in the display.
Table 49 show tarp blacklisted adjacencies Field Descriptions
Field
|
Description
|
49.0001.5555.5555.5555.00
|
NSAP address of the blacklisted router.
|
Related Commands
Command
|
Description
|
tarp blacklist-adjacency
|
Blacklists the specified router so that the router does not receive TARP PDUs propagated by this router.
|