Feedback
Table Of Contents
show tarp blacklisted-adjacencies
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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch clns address ourprefixclns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch clns next-hop ourprefixclns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch clns route-source ourprefixclns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute rip route-map ourmapredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch interface ethernet2Related 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
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:
router isisredistribute rip route-map ourmapredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch metric 26795clns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute rip route-map ourmapredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch route-type level-2clns 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
Defaults
qos: 0
k1: 1
k2: 0
k3: 1
k4: 0
k5: 0Command Modes
Router configuration
Command History
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 8 lists the default values used for several common media.
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:
router iso-igrpmetric weights 0 2 0 1 0 0Related Commands
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
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
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 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:
router isis USAredistribute iso-igrp Michiganredistribute iso-igrp OhioThe 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 Backboneredistribute isis Franceredistribute iso-igrp GermanyIn the following example, the router advertises any static routes it knows about in the Chicago domain:
router iso-igrp Chicagoredistribute staticRelated Commands
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
Defaults
The permit keyword is the default.
Command Modes
Global configuration
Command History
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 can be given in any order, and all match commands must "pass" 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.
Use route maps when you want detailed control over how routes are redistributed between routing processes. The destination routing protocol is the one you specify with the router global configuration command. The source routing protocol is the one you specify with the redistribute router configuration command. See the "Examples" section for an illustration of how route maps are configured.
When you are passing routes through a route map, a route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route map section with an explicit match specified.
Examples
The following example redistributes Routing Information Protocol (RIP) routes with a hop count equal to 1 into Open Shortest Path First (OSPF). These routes will be redistributed into OSPF as external link-state advertisements (LSAs) with a metric of 5, metric type of Type 1, and a tag equal to 1.
router ospf 109redistribute rip route-map rip-to-ospfroute-map rip-to-ospf permitmatch metric 1set metric 5set metric-type type1set tag 1Related 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
Defaults
Disabled
Command Modes
Global configuration
Command History
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 ManufacturingRelated Commands
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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
router isisredistribute rip route-map ourmapredistribute iso-igrp remote route-map ourmaproute-map ourmap permitmatch ip address 1match clns address ourprefixset metric 5set level level-2access-list 1 permit 160.89.0.0 0.0.255.255clns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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 172.16.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 isisredistribute rip route-map ourmapredistribute iso-igrp remote route-map ourmap!route-map ourmap permitmatch ip address 1match clns address ourprefixset metric 5set level level-2!access-list 1 permit 172.16.0.0 0.0.255.255clns 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
route-map map-typeset metric-type internalRelated 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
Defaults
Disabled
Command Modes
Route-map configuration
Command History
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:
route-map tagset tag 5Related Commands
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
Command Modes
EXEC
Command History
Examples
The following is sample output from the show clns cache command:
Router# show clns cacheCLNS routing cache version 433Destination -> Next hop @ Interface: SNPA Address => Rewrite / Length[42] *39.0004.0040.0000.0C00.2D55.00 ISOLATOR-> 0000.0C00.2D55 @ Ethernet0/1: 0000.0c00.6fa5Table 9 describes significant fields shown in the display.
Table 9 show clns cache Field Descriptions
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.
1 A leading asterisk (*) indicates that the entry is an allowable value.
The following is sample output from the show clns cache delay-parameters command:
Router# show clns cache delay-parametersMinimum invalidation interval 2 seconds,Maximum invalidation interval 5 seconds,Quiet interval 3 seconds,Threshold 0 requestsInvalidation rate 3 in last second, 3 in last 3 secondsTable 10 describes significant fields shown in the display.
The following is sample output from the show clns cache invalidations command:
Router# show clns cache invalidationsCaller Count Last Invalidationclns_fastsetup 3 20:55:56clns_route_update 23 20:56:44clns_route_adjust 2 20:55:52isis_compute_spt 2017 00:10:13delete_adjacency 9 1d19hclns_ager 11 1d19hTable 11 describes significant fields shown in the display.
Related Commands
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
Command Modes
EXEC
Command History
Examples
The following is sample output from the show clns es-neighbors command when Ethernet interface 0 is specified:
Router# show clns es-neighbors ethernet0System Id Interface State Type Format0800.2B14.060E Ethernet0 Up ES Phase V0800.2B14.0528 Ethernet0 Up ES Phase VTable 12 describes the significant fields shown in the display.
The following is sample output from the show clns es-neighbors detail command:
Router# show clns es-neighbors detailSystem Id Interface State Type Format0800.2B14.060E Ethernet0 Up ES Phase VArea Address(es): 49.00400800.2B14.0528 Ethernet0 Up ES Phase VArea Address(es): 49.0040Notice 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
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
Command Modes
EXEC
Command History
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 BARNEYclns filter-expr WOMEN WILMA or BETTYclns filter-expr ADULTS MEN or WOMENThe show clns filter-expr command would yield the following output:
Router# show clns filter-exprMEN = FRED or BARNEYWOMEN = WILMA or BETTYADULTS = MEN or WOMENThe show clns filter-expr detail command would yield the following output:
Router# show clns filter-expr detailMEN = FRED or BARNEYWOMEN = WILMA or BETTYADULTS = (FRED or BARNEY) or (WILMA or BETTY)Related Commands
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
Command Modes
EXEC
Command History
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-setCLNS filter set US-OR-NORDUNETpermit 47.0005...permit 47.0023...CLNS filter set LOCALpermit 49.0003...Related Commands
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 privileged EXEC mode.
show clns interface [type number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show clns interface command that includes information for Token Ring and serial interfaces:
Router# show clns interfaceTokenRing 0 is administratively down, line protocol is downCLNS protocol processing disabledTokenRing 1 is up, line protocol is upChecksums enabled, MTU 4461, Encapsulation SNAPERPDUs enabled, min. interval 10 msec.RDPDUs enabled, min. interval 100 msec., Addr Mask enabledCongestion Experienced bit set at 4 packetsCLNS fast switching disabledDEC compatibility mode OFF for this interfaceNext ESH/ISH in 18 secondsRouting Protocol: ISO IGRPRouting Domain/Area: <39.0003> <0020>Serial 2 is up, line protocol is upChecksums enabled, MTU 1497, Encapsulation HDLCERPDUs enabled, min. interval 10 msec.RDPDUs enabled, min. interval 100 msec., Addr Mask enabledCongestion Experienced bit set at 4 packetsCLNS fast switching enabledDEC compatibility mode OFF for this interfaceCLNS cluster alias enabled on this interfaceNext ESH/ISH in 48 secondsRouting Protocol: IS-ISCircuit Type: level-1-2Level-1 Metric: 10, Priority: 64, Circuit ID: 0000.0C00.2D55.0ANumber of active level-1 adjacencies: 0Level-2 Metric: 10, Priority: 64, Circuit ID: 0000.0000.0000.00Number of active level-2 adjacencies: 0Next IS-IS LAN Level-1 hello in 3 secondsNext IS-IS LAN Level-2 hello in 3 secondsCisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T
The following is sample output from the show clns interface command that verifies that the BFD feature has been enabled on Ethernet interface 3/0. The relevant command output is shown in bold in the output.
Router# show clns interface ethernet 3/0Ethernet3/0 is up, line protocol is upChecksums enabled, MTU 1497, Encapsulation SAPERPDUs enabled, min. interval 10 msec.CLNS fast switching enabledCLNS SSE switching disabledDEC compatibility mode OFF for this interfaceNext ESH/ISH in 42 secondsRouting Protocol: IS-ISCircuit Type: level-1-2Interface number 0x1, local circuit ID 0x2Level-1 Metric: 10, Priority: 64, Circuit ID: RouterA.02DR ID: 0000.0000.0000.00Level-1 IPv6 Metric: 10Number of active level-1 adjacencies: 0Level-2 Metric: 10, Priority: 64, Circuit ID: RouterA.02DR ID: 0000.0000.0000.00Level-2 IPv6 Metric: 10Number of active level-2 adjacencies: 0Next IS-IS LAN Level-1 Hello in 3 secondsNext IS-IS LAN Level-2 Hello in 5 secondsBFD enabledTable 13 describes the significant fields shown in the display.
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
Command Modes
EXEC
Command History
Examples
The following is sample output from the show clns is-neighbors command:
Router# show clns is-neighborsSystem Id Interface State Type Priority Circuit Id Format0000.0C00.0C35 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase V0800.2B16.24EA Ethernet0 Up L1L2 64/64 0800.2B16.24EA.01 Phase V0000.0C00.3E51 Serial1 Up L2 0 04 Phase V0000.0C00.62E6 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase VTable 14 describes significant fields shown in the display.
The following is sample output from the show clns is-neighbors detail command:
Router# show clns is-neighbors detailSystem Id Interface State Type Priority Circuit Id Format0000.0C00.0C35 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase VArea Address(es): 47.0004.004D.0001 39.0001Uptime: 0:03:350800.2B16.24EA Ethernet0 Up L1L2 64/64 0800.2B16.24EA.01 Phase VArea Address(es): 47.0004.004D.0001Uptime: 0:03:350000.0C00.3E51 Serial1 Up L2 0 04 Phase VArea Address(es): 39.0004Uptime: 0:03:35000.0C00.62E6 Ethernet1 Up L1 64 0000.0C00.62E6.03 Phase VArea Address(es): 47.0004.004D.0001Uptime: 0:03:35Notice 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
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
Command Modes
EXEC
Command History
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 areasSystem Id Interface Area Name State Holdtime Type Protocol0000.0000.0009 Tu529 L2BB Up 26 L1L2 IS-IS0000.0000.0053 Et1 A3253-01 Up 21 L1 IS-IS0000.0000.0003 Et1 A3253-01 Up 28 L1 IS-IS0000.0000.0002 Et2 A3253-02 Up 22 L1 IS-IS0000.0000.0053 Et2 A3253-02 Up 23 L1 IS-ISTable 15 describes the significant fields shown in the display.
Related Commands
show clns neighbors
To display end system (ES), intermediate system (IS), and multitopology Integrated Intermediate System-to-Intermediate System (M-ISIS) neighbors, use the show clns neighbors command in user EXEC or privileged EXEC mode.
show clns neighbors [process-tag] [interface-type interface-number] [area] [detail]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show clns neighbors command displays the adjacency that is learned through multitopology IS-IS for IPv6.
Examples
The following is sample output from the show clns neighbors command:
Router# show clns neighborsSystem Id Interface SNPA State Holdtime Type Protocol0000.0000.0007 Et3/3 aa00.0400.6408 UP 26 L1 IS-IS0000.0C00.0C35 Et3/2 0000.0c00.0c36 Up 91 L1 IS-IS0800.2B16.24EA Et3/3 aa00.0400.2d05 Up 27 L1 M-ISIS0800.2B14.060E Et3/2 aa00.0400.9205 Up 8 L1 IS-ISThe following is sample output from the show clns neighbors command using the process-tag argument to display information about the VRF-aware IS-IS instance tagRED:
Router# show clns tagRED neighborsTag tagRED:System Id Interface SNPA State Holdtime Type Protocoligp-03 Fa0/ 200d0.2b7f.9502 Up 9 L2 IS-ISigp-03 PO2/2.1 DLCI 211 Up 27 L2 IS-ISigp-02 PO2/0.1 DLCI 131 Up 29 L2 IS-ISigp-11 Fa0/4 000e.d79d.7920 Up 7 L2 IS-ISigp-11 Fa0/5 000e.d79d.7921 Up 8 L2 IS-ISigp-11 PO3/2.1 DLCI 451 Up 24 L2 IS-ISThe following is sample output from the show clns neighbors command using the detail keyword:
Router# show clns neighbors detailSystem Id Interface SNPA State Holdtime Type Protocol0000.0000.0007 Et3/3 aa00.0400.6408 UP 26 L1 IS-ISArea Address(es): 20IP Address(es): 172.16.0.42*Uptime: 00:21:490000.0C00.0C35 Et3/2 0000.0c00.0c36 Up 91 L1 IS-ISArea Address(es): 20IP Address(es): 192.168.0.42*Uptime: 00:21:520800.2B16.24EA Et3/3 aa00.0400.2d05 Up 27 L1 M-ISISArea Address(es): 20IP Address(es): 192.168.0.42*IPv6 Address(es): FE80::2B0:8EFF:FE31:EC57Uptime: 00:00:27Topology: IPv60800.2B14.060E Et3/2 aa00.0400.9205 Up 8 L1 IS-ISArea Address(es): 20IP Address(es): 192.168.0.30*Uptime: 00:21:52The following is sample output from the show clns neighbors command using the process-tag argument to display information about the VRF-aware IS-IS instance tagSecond:
Router# show clns tagSecond neighborsTag tagSecond:System Id Interface SNPA State Holdtime Type Protocoligp-03 Fa0/2 00d0.2b7f.9502 Up 9 L2 IS-ISigp-03 PO2/2.1 DLCI 211 Up 27 L2 IS-ISigp-02 PO2/0.1 DLCI 131 Up 29 L2 IS-ISigp-11 Fa0/4 000e.d79d.7920 Up 7 L2 IS-ISigp-11 Fa0/5 000e.d79d.7921 Up 8 L2 IS-ISigp-11 PO3/2.1 DLCI 451 Up 24 L2 IS-ISTable 16 describes the significant fields shown in the display.
Notice that the information displayed in the show clns neighbors detail command output includes everything shown in show clns neighbors command 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 asterisk (*) to indicate which IP address is the next hop.
show clns protocol
To list the protocol-specific information for each ISO Interior Gateway Routing Protocol (IGRP) or Intermediate System-to-Intermediate System (IS-IS) routing process in the router, use the show clns protocol command in privileged EXEC mode.
show clns [domain | process-tag] protocol
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
There will always be at least two routing processes, a Level 1 and a Level 2, and there can be more.
Examples
The following is sample output from the show clns protocol command:
Router# show clns protocolISO IGRP Level 1 Router: remoteRouting for domain: 39.0003 area: 0020Sending Updates every 45 seconds. Next due in 11 secondsInvalid after 135 seconds,Hold down for 145 secondsSending Router Hellos every 17 seconds. Next due in 9 secondsInvalid after 51 seconds,IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0Interfaces in domain/area:TokenRing1ISO IGRP Level 2 Router: DOMAIN_remoteRouting for domain: 39.0003Redistribute:isis (Null Tag)Sending Updates every 45 seconds. Next due in 2 secondsInvalid after 135 seconds,Hold down for 145 secondsSending Router Hellos every 17 seconds. Next due in 0 secondsInvalid after 51 seconds,ISO IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0Interfaces in domain/area:TokenRing1IS-IS Router: <Null Tag>System Id: 0000.0C00.224D.00 IS-Type: level-1-2Manual area address(es):39.0004.0030Routing for area address(es):39.0004.0030Interfaces supported by IS-IS:Serial2Next global update in 530 secondsRedistributing:staticiso-igrp (remote)Distance: 110The following is sample output from the show clns protocol command using the process-tag argument to display information about the VPN routing/forwarding instance (VRF)-aware IS-IS instance tagFirst:
Router# show clns tagFirst protocolIS-IS Router: tagFirstSystem Id: 0000.0001.0002.00 IS-Type: level-2-onlyManual area address(es):49.000bRouting for area address(es):49.000bInterfaces supported by IS-IS:FastEthernet4/1 - IPFastEthernet4/0 - IPEthernet0/2 - IPFastEthernet4/3 - IPRedistributing:staticDistance: 110RRR level: noneGenerate narrow metrics: level-1-2Accept narrow metrics: level-1-2Generate wide metrics: noneAccept wide metrics: noneTable 17 describes the significant fields shown in the display.
Table 18 describes significant fields shown in the IS-IS portion of the display.
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
Command Modes
EXEC
Command History
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:
Router# show clns routeISO-IGRP Routing Table for Domain 49.0002, Area 0007System Id Next-Hop SNPA Interface Metric Statemilles milles *HDLC* Se1 8476 Up0000.0000.0007 milles *HDLC* Se1 10476 Uprips 0000.0000.0000 -- -- 0 UpISO-IGRP Routing Table for Domain 49.0002Area Id Next-Hop SNPA Interface Metric State0002 0000.0000.0000 -- -- 0 UpCodes: C - connected, S - static, d - DecnetIVI - ISO-IGRP, i - IS-IS, e - ES-ISC 49.0002 [2/0], Local ISO-IGRP DomainC 49.0001.0000.0000.0005.00 [1/0], Local IS-IS NETC 49.0002.0007.0000.0000.0005.00 [1/0], Local ISO-IGRP NETC 49.0001 [2/0], Local IS-IS Areai 33.3333.3333 [110/10]via bakel, Ethernet0S 50.1234 [10/0], Discard EntryI 55.5555.5555 [100/8476]via milles, Serial1S 77.7777.7777.7777 [10/0]via Serial0d 88.8888.8888.0007 [120/0], DecnetIV Entryi 33.4567.8901 [110/10]via bakel, Ethernet0Table 19 describes the significant fields shown in the display.
Table 20 describes the codes as they appear in the previous display.
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.3333Routing entry for 33.3333.3333Known via "isis", distance 110, metric 10, Dynamic EntryRouting Descriptor Blocks:via bakel, Ethernet0isis, route metric is 10, route version is 4Table 21 describes the significant fields shown in the display.
Related Commands
show clns traffic
To list the Connectionless Network Service (CLNS) packets that this router has seen, use the show clns traffic command in privileged EXEC mode.
show clns area-tag traffic [since {bootup | show}]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
10.0
This command was introduced.
12.2(9)T
The since, bootup, and show keywords were introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following sample output from the show clns traffic command lists all the CLNS packets it has seen:
Router# show clns trafficCLNS & ESIS Output: 139885, Input: 90406CLNS Local: 0, Forward: 0CLNS Discards:Hdr Syntax: 150, Checksum: 0, Lifetime: 0, Output cngstn: 0No Route: 0, Dst Unreachable 0, Encaps. Failed: 0NLP Unknown: 0, Not an IS: 0CLNS Options: Packets 19, total 19, bad 0, GQOS 0, cngstn exprncd 0CLNS Segments: Segmented: 0, Failed: 0CLNS Broadcasts: sent: 0, rcvd: 0Echos: Rcvd 0 requests, 69679 repliesSent 69701 requests, 0 repliesESIS(sent/rcvd): ESHs: 0/34, ISHs: 483/1839, RDs: 0/0, QCF: 0/0ISO IGRP: Querys (sent/rcvd): 0/0 Updates (sent/rcvd): 1279/1402ISO IGRP: Router Hellos: (sent/rcvd): 1673/1848ISO IGRP Syntax Errors: 0IS-IS: Level-1 Hellos (sent/rcvd): 0/0IS-IS: Level-2 Hellos (sent/rcvd): 0/0IS-IS: PTP Hellos (sent/rcvd): 0/0IS-IS: Level-1 LSPs (sent/rcvd): 0/0IS-IS: Level-2 LSPs (sent/rcvd): 0/0IS-IS: Level-1 CSNPs (sent/rcvd): 0/0IS-IS: Level-2 CSNPs (sent/rcvd): 0/0IS-IS: Level-1 PSNPs (sent/rcvd): 0/0IS-IS: Level-2 PSNPs (sent/rcvd): 0/0IS-IS: Level-1 DR Elections: 0IS-IS: Level-2 DR Elections: 0IS-IS: Level-1 SPF Calculations: 0IS-IS: Level-2 SPF Calculations: 0Table 22 describes the significant fields shown in the display.
Related Commands
clear clns traffic
Clears all ISO CLNS statistics that are displayed when you use the show clns traffic command.
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
Examples
The following is sample output from the show clns command:
Router# show clnsGlobal CLNS Information:2 Interfaces Enabled for CLNSNET: 39.0004.0030.0000.0C00.224D.00NET: 39.0003.0020.0000.0C00.224D.00Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64ERPDU's requested on locally generated packetsIntermediate system operation enabled (forwarding allowed)ISO IGRP level-1 Router: remoteRouting for Domain: 39.0003, Area: 0020ISO IGRP level-2 Router: DOMAIN_remoteRouting for Domain: 39.0003IS-IS level-1-2 Router:Routing for Area: 39.0004.0030Table 23 describes significant fields shown in the display.
show isis route
To display the Intermediate System-to-Intermediate System (IS-IS) Level 1 forwarding table for IS-IS learned routes, use the show isis route command in user EXEC or privileged EXEC mode.
show isis [area-tag] route [hostname]
Syntax Description
area-tag
(Optional) Name for a routing process.
hostname
(Optional) Hostname or Network Service Access Point (NSAP) address of a router.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The area-tag argument 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. This argument is required for multiarea IS-IS configuration.
Examples
The following is sample output of the IS-IS Level-1Routing Table from the show isis route command:
Router# show isis routeIS-IS Level-1 Routing Table - Version 34System Id Next-Hop SNPA Interface Metric State0000.0C00.0C35 0000.0C00.0C35 0000.0c00.0c36 Ethernet1 20 Up0800.2B16.24EA 0800.2B16.24EA aa00.0400.2d05 Ethernet0 10 Up0800.2B14.060E 0800.2B14.060E aa00.0400.9205 Ethernet0 10 Up0800.2B14.0528 0800.2B14.0528 aa00.0400.9105 Ethernet0 10 Up0000.0C00.40AF 0000.0000.0000 -- -- 0 Up0000.0C00.62E6 0000.0C00.62E6 0000.0c00.62e7 Ethernet1 10 UpAA00.0400.2D05 0800.2B16.24EA aa00.0400.2d05 Ethernet0 10 UpTable 24 describes the significant fields shown in the display.
Related Commands
clns router isis
Configures an IS-IS routing process for CLNS on a specified interface and attaches an area designator to the routing process.
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
Examples
The following is sample output from the show tarp blacklisted-adjacencies command:
Router# show tarp blacklisted-adjacenciesAdjacencies that we won't propagate TARP PDU's to:49.0001.5555.5555.5555.00Table 25 describes the field shown in the display.
Table 25 show tarp blacklisted adjacencies Field Descriptions
49.0001.5555.5555.5555.00
NSAP address of the blacklisted router.
Related Commands
tarp blacklist-adjacency
Blacklists the specified router so that the router does not receive TARP PDUs propagated by this router.
show tarp host
To display information about a specific TID Address Resolution Protocol (TARP) router stored in the local TID cache, use the show tarp host command in EXEC mode.
show tarp host tid
Syntax Description
tid
Target identifier of the router from which you want information. Alphanumeric string up to 255 characters.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp host command:
router# show tarp host artemisTID of entry: artemisNET of entry: 49.0001.1111.1111.1111.00Entry type: DYNAMICExpiration time: 280 secondsTable 26 describes the fields shown in the display.
Related Commands
show tarp interface
To list all interfaces that have TID Address Resolution Protocol (TARP) enabled, use the show tarp interface command in EXEC mode.
show tarp interface [type number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp interface command:
Router# show tarp interfaceEthernet0 is up, line protocol is up, encapsulation is ARPATARP propagation is enabled on this interfaceTable 27 describes the fields shown in the display.
Related Commands
tarp enable
Enables the TARP on an interface.
tarp propagate
Reenables propagation of TARP PDUs on an interface.
show tarp ldb
To display the contents of the loop-detection buffer table, use the show tarp ldb command in EXEC mode.
show tarp ldb
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp ldb command:
Router# show tarp ldbSystem ID Sequence Number Expiration (sec)1111.1111.1111 4 240Table 28 describes the fields shown in the display.
Related Commands
show tarp map
To list all static entries in the TID cache that were configured with the tarp map command, use the show tarp map command in EXEC mode.
show tarp map
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp map command:
Router# show tarp mapStatic MAP entries:shashi 49.0001.6666.6666.6666.00sonali 49.0001.7777.7777.7777.00Table 29 describes the fields shown in the display.
Table 29 show tarp map Field Descriptions
shashi
TID of the static entry.
49.0001.6666.6666.6666.00
NSAP address of the static entry.
Related Commands
clear tarp tid-table
Clears the dynamically created TARP TID-to-NSAP address mapping entries stored in TID cache.
tarp map
Enters a TID-to-NSAP static map entry in the TID cache.
show tarp static-adjacencies
To list all static TID Address Resolution Protocol (TARP) adjacencies that are configured with the tarp route-static command, use the show tarp static-adjacencies command in EXEC mode.
show tarp static-adjacencies
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp static-adjacencies command:
Router# show tarp static-adjacenciesManual (static) TARP adjacencies:55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00Table 30 describes the field shown in the display.
Table 30 show tarp static-adjacencies Field Descriptions
55.0001.0001.1111.1111.1111.1111.1111.1111.1111.0
NSAP address of the TARP adjacency.
Related Commands
show tarp tid-cache
To display information about the entries in the TID cache, use the show tarp tid-cache command in EXEC mode. Entries are created dynamically, statically, or as a result of assigning a TID to the device by using the tarp tid command.
show tarp tid-cache [detail]
Syntax Description
detail
(Optional) List additional information in the TID/NET cache (such as the expiration time for dynamic entries).
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp tid-cache command:
Router# show tarp tid-cacheTID ('*' : static; & : local) NSAP* shashi 49.0001.6666.6666.6666.00& router 49.0001.3333.3333.3333.00* sonali 49.0001.7777.7777.7777.00artemis 49.0001.1111.1111.1111.00The following is sample output from the show tarp tid-cache detail command:
Router# show tarp tid-cache detailTID ('*': static; &: local) NSAP& router 49.0001.3333.3333.3333.00Expiration time: NONETable 31 describes the fields shown in the displays.
Related Commands
show tarp traffic
To display statistics about TID Address Resolution Protocol (TARP) PDUs since the last time the counters were cleared, use the show tarp traffic command in EXEC mode.
show tarp traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tarp traffic command:
Router# show tarp trafficTARP counters:Packets output: 11, Input: 5Hdr syntax: 0No memory: 0, Invalid packet: 0Lifetime exceeded: 0Table 32 describes the fields shown in the display.
Related Commands
clear tarp counters
Clears all TARP counters that are displayed with the show tarp traffic command.
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
Examples
The following is sample output from the show tarp command:
Router# show tarpGlobal TARP information:TID of this station is "cerd"Timer T1 (timer for response to TARP Type 1 PDU) is 15 secondsTimer T2 (timer for response to TARP Type 2 PDU) is 25 secondsTimer T3 (timer for response to ARP request) is 40 secondsTimer T4 (timer that starts when T2 expires) is 15 secondsLoop Detection Buffer entry timeout: 300 secondsTID cache entry timeout: 300 secondsThis station will propagate TARP PDUsThis station will originate TARP PDUsTID<->NET cache is enabledSequence number that next packet originated by this station will have: 9Update remote cache (URC) bit is 0Packet lifetime: 100 hopsProtocol type used in outgoing packets: "FE"N-Selector used in TARP PDU's: "AF"Table 33 describes the fields shown in the display.
tarp allow-caching
To reenable the storage of TID-to-NSAP address mapping in the TID cache, use the tarp allow-caching command in global configuration mode. To disable this function and clear the TID cache, use the no form of this command.
tarp allow-caching
no tarp allow-caching
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
By default, storing TID-to-network (NSAP) address mapping in the 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 reenable 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.
Examples
The following example disables storage of TID-to-NSAP address mapping in cache on the router:
no tarp allow-cachingRelated Commands
tarp arp-request-timer
To set the timeout for TID Address Resolution Protocol (TARP) Type 5 PDUs, use the tarp arp-request-timer command in global configuration mode. To set the timeout to the default value, use the no form of this command.
tarp arp-request-timer seconds
no tarp arp-request-timer
Syntax Description
seconds
Number of seconds for which the router will wait for a response from a TARP Type 5 PDU. The range is from 0 to 3600 seconds.
Defaults
40 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
The following example sets the timeout for TARP Type 5 PDUs to 60 seconds (one minute):
tarp arp-request-timer 60Related Commands
tarp lifetime
Specifies the lifetime for locally generated TARP PDUs based on the number of hops.
tarp query
Determines a TID corresponding to a specific NSAP address.
tarp blacklist-adjacency
To blacklist the specified router so that the router does not receive TID Address Resolution Protocol (TARP) PDUs propagated by this router, use the tarp blacklist-adjacency command in global configuration mode. To remove the specified router from the blacklist so that the router can once again receive propagated TARP PDUs, use the no form of this command.
tarp blacklist-adjacency nsap
no tarp blacklist-adjacency nsap
Syntax Description
Defaults
All hosts receive propagated TARP PDUs.
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
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.00Related Commands
show tarp blacklisted-adjacencies
Lists all blacklisted adjacencies (to which this router will not propagate TARP PDUs) by the tarp blacklist-adjacency command.
tarp cache-timer
To specify the length of time for which a dynamically created TID Address Resolution Protocol (TARP) entry remains in the TID cache, use the tarp cache-timer command in global configuration mode. To set the timer to the default value, use the no form of this command.
tarp cache-timer seconds
no tarp cache-timer
Syntax Description
seconds
Number of seconds for which an entry remains in the TID cache. The range is 30 to 86,400 seconds.
Defaults
3,600 seconds (one hour)
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
The following example limits the time for which an entry remains in the TID cache to 1,800 seconds (30 minutes):
tarp cache-timer 1800Related Commands
tarp enable
To enable TID Address Resolution Protocol (TARP) on an interface, use the tarp enable command in interface configuration mode. To disable TARP on a particular interface, use the no form of this command.
tarp enable
no tarp enable
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
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.
Examples
The following example enables TARP on Ethernet interface 0:
interface ethernet 0 tarp enableRelated Commands
tarp global-propagate
To reenable the capability to propagate TID Address Resolution Protocol (TARP) PDUs globally, use the tarp global-propagate command in global configuration mode. To disable global propagation of TARP PDUs, use the no form of this command.
tarp global-propagate
no tarp global-propagate
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
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 reenable 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.
Note
Examples
The following example disables global propagation of TARP PDUs on this router:
no tarp global-propagateRelated Commands
tarp ldb-timer
To specify the length of time for which a system ID-to-sequence number mapping entry remains in the loop-detection buffer table, use the tarp ldb-timer command in global configuration mode. To set the timer to the default value, use the no form of this command.
tarp ldb-timer seconds
no tarp ldb-timer
Syntax Description
seconds
Number of seconds for which 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.
Defaults
300 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
The loop-detection buffer table prevents TARP PDUs from looping.
Examples
The following example limits the time for which an entry remains in the loop-detection buffer table to 600 seconds (10 minutes):
tarp ldb-timer 600Related Commands
tarp lifetime
To specify the lifetime for locally generated TID Address Resolution Protocol (TARP) PDUs based on the number of hops, use the tarp lifetime command in global configuration mode. To set the PDU lifetime to the default value, use the no form of this command.
tarp lifetime hops
no tarp lifetime
Syntax Description
hops
Number of hosts that a PDU can traverse before it is discarded. Each router represents one hop. The range is 0 to 65,535 hops. The default is 100 hops.
Defaults
100 hops
Command Modes
Global configuration
Command History
Usage Guidelines
The number of hops specified is decremented after every hop. A PDU with a lifetime of zero is discarded.
Examples
The following example specifies that the TARP PDU can traverse 150 hosts before it is discarded:
tarp lifetime 150Related Commands
tarp map
To enter a TID-to-NSAP static map entry in the TID cache, use the tarp map command in global configuration mode. To remove a static map entry from the TID cache, use the no form of this command.
tarp map tid nsap
no tarp map tid nsap
Syntax Description
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.
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
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.00Related Commands
tarp nselector-type
To specify the N-selector to be used in Connectionless Network Protocol (CLNP) PDUs to indicate that the packet is a TID Address Resolution Protocol (TARP) PDU, use the tarp nselector-type command in global configuration mode. To set the N-selector to the default value, use the no form of this command.
tarp nselector-type hex-digit
no tarp nselector-type
Syntax Description
Defaults
AF
Command Modes
Global configuration
Command History
Usage Guidelines
This feature provides 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.
Examples
The following example changes the N-selector used in CLNP PDUs to BC:
tarp nselector-type BCRelated Commands
tarp originate
To reenable the router to originate TID Address Resolution Protocol (TARP) PDUs, use the tarp originate command in global configuration mode. To disable the capability to originate TARP PDUs, use the no form of this command.
tarp originate
no tarp originate
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
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 reenable origination of TARP PDUs.
Examples
The following example disables the origination of TARP PDUs on this router:
no tarp originateRelated Commands
tarp post-t2-response-timer
To specify the length of time for which a router waits for a response to a Type 2 PDU after the default timer expires, use the tarp post-t2-response-timer command in global configuration mode. To set the timer to the default value, use the no form of this command.
tarp post-t2-response-timer seconds
no tarp post-t2-response-timer
Syntax Description
seconds
Number of seconds for which the router will wait for a response for a Type 2 PDU after the default timer has expired. The range is 0 to 3600 seconds.
Defaults
15 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
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 60Related Commands
tarp t2-response-timer
Specifies the length of time for which the router will wait for a response from a Type 2 PDU.
tarp propagate
To reenable propagation of TID Address Resolution Protocol (TARP) PDUs on an interface, use the tarp propagate command in interface configuration mode. To disable propagation of TARP PDUs on one or more interfaces, use the no form of this command.
tarp propagate [all | message-type type-number [type-number] [type-number]]
no tarp propagate [all | message-type type-number [type-number] [type-number]]
Syntax Description
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Pressing Return or Enter after tarp propagate is the same as typing the keyword all.
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 reenable propagation 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.
Note
Examples
The following example starts the TARP process on the router and enables TARP propagation on Ethernet interface 0:
interface ethernet 0 tarp propagateRelated Commands
tarp protocol-type
To specify the network protocol type to be used in outgoing TID Address Resolution Protocol (TARP) PDUs, use the tarp protocol-type command in global configuration mode. To set the protocol type to the default value, use the no form of this command.
tarp protocol-type hex-digit
no tarp protocol-type
Syntax Description
hex-digit
Two digits in hexadecimal format to be used to identify the protocol used in outgoing TARP PDUs. The default is FE (for CLNP).
Defaults
FE
Command Modes
Global configuration
Command History
Usage Guidelines
Only FE is supported.
Examples
The following example shows the TARP network protocol type changed from the default of FE to AO:
tarp protocol-type aoRelated Commands
tarp query
To determine a corresponding TID entry for a specific NSAP address, use the tarp query command in EXEC mode.
tarp query nsap
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
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.
Examples
The following is sample output from the tarp query command:
Router# tarp query 49.0001.3333.3333.3333.00Type escape sequence to abort.Sending TARP type 5 PDU, timeout 40 seconds...TID corresponding to NET 49.0001.3333.3333.3333.00 is cerdTable 34 describes the fields shown in the display.
Related Commands
show tarp
Displays all global TARP parameters.
tarp arp-request-timer
Sets the timeout for TARP Type 5 PDUs.
tarp resolve
To determine an NSAP address corresponding to a specified TID, use the tarp resolve command in EXEC mode.
tarp resolve tid [1 | 2]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
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 PDU 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.
Examples
The following is sample output from the tarp resolve command:
Router# tarp resolve artemisType escape sequence to abort.Sending TARP type 1 PDU, timeout 15 seconds...NET corresponding to TID artemis is 49.0001.1111.1111.1111.00Table 35 describes the fields shown in the display.
Related Commands
tarp route-static
To configure a static TID Address Resolution Protocol (TARP) adjacency, use the tarp route-static command in global configuration mode. To remove a static TARP adjacency from the TARP queue, use the no form of this command.
tarp route-static nsap [all | message-type type-number [type-number] [type-number]]
no tarp route-static nsap [all | message-type type-number [type-number] [type-number]]
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Pressing Return or Enter after tarp route-static is the same as typing the keyword all.
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 prevent sending TARP PDUs directly to hosts that are not running TARP.
Examples
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.00Related Commands
tarp run
To start the TID Address Resolution Protocol (TARP) process on the router, use the tarp run command in global configuration mode. To stop the TARP process, use the no form of this command.
tarp run
no tarp run
Syntax Description
This command has no arguments or keywords.
Defaults
No TARP process (unless configured to start in NVRAM).
Command Modes
Global configuration
Command History
Usage Guidelines
You must also enable TARP on the individual interfaces by using the tarp enable command.
Examples
The following example starts the TARP process on the router:
tarp runRelated Commands
tarp enable
Enables the TARP on an interface.
tarp propagate
Reenables propagation of TARP PDUs on an interface.
tarp sequence-number
To specify the sequence number to be used in the next originated TID Address Resolution Protocol (TARP) PDU, use the tarp sequence-number command in global configuration mode. To return to the default value, use the no form of this command.
tarp sequence-number number
no tarp sequence-number number
Syntax Description
Defaults
Zero
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
The following example causes a sequence number of 10 to be assigned to the next TARP PDU:
tarp sequence-number 10Related Commands
show tarp
Displays all global TARP parameters.
show tarp ldb
Displays the contents of the loop-detection buffer table.
tarp t1-response-timer
To specify the length of time for which the router will wait for a response from a Type 1 PDU, use the tarp t1-response-timer command in global configuration mode. To set the timer to the default value, use the no form of this command.
tarp t1-response-timer seconds
no tarp t1-response-timer
Syntax Description
seconds
Number of seconds for which the router will wait to receive a response from a Type 1 PDU. The range is 0 to 3600 seconds.
Defaults
15 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
The following example sets the timeout period for a Type 1 PDU to 60 seconds:
tarp t1-response-timer 60Related Commands
tarp t2-response-timer
Specifies the length of time for which the router will wait for a response from a Type 2 PDU.
tarp t2-response-timer
To specify the length of time for which the router will wait for a response from a Type 2 PDU, use the tarp t2-response-timer command in global configuration mode. To set the timer to the default value, use the no form of this command.
tarp t2-response-timer seconds
no tarp t2-response-timer
Syntax Description
seconds
Number of seconds for which the router will wait to receive a response from a Type 2 PDU. The range is 0 to 3600 seconds.
Defaults
25 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
The following example sets the timeout period for a Type 2 PDU to 60 seconds:
tarp t2-response-timer 60Related Commands
tarp tid
To assign a TID to the router, use the tarp tid command in global configuration mode. To remove the TID from the router, use the no form of this command.
tarp tid tid
no tarp tid tid
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
All hosts using TID Address Resolution Protocol (TARP) must have a unique TID assigned.
Examples
The following example assigns the TID SJ3 to the router:
tarp tid sj3Related Commands
tarp urc
To set the update remote cache bit in all subsequent outgoing PDUs, use the tarp urc command in global configuration mode. To set the update remote cache bit to the default value, use the no form of this command.
tarp urc {0 | 1}
no tarp urc
Syntax Description
Defaults
The default value is 0.
Command Modes
Global configuration
Command History
Usage Guidelines
If you do not specify either 0 or 1, the default value 0 is used.
Examples
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 1Related Commands
timers basic (ISO CLNS)
To configure ISO IGRP timers, use the timers basic command in router configuration mode. To restore the default values, use the no form of this command.
timers basic update-interval holddown-interval invalid-interval
no timers basic update-interval holddown-interval invalid-interval
Syntax Description
Defaults
update-interval: 90 seconds
holddown-interval: 145 seconds
invalid-interval: 135 secondsCommand Modes
Router configuration
Command History
Usage Guidelines
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.
Examples
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-igrptimers basic 60 100 130which-route
To determine which next-hop router will be used or to troubleshoot your configuration if you have multiple processes running, use the which-route command in EXEC mode. This command displays the routing table in which the specified CLNS destination is found.
which-route {nsap-address | clns-name}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Route information can reside in the following tables:
•
•
•
•
Examples
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.
Router# which-route grayRoute look-up for destination 39.0001.0000.0c00.bda8.00, GRAYFound route in IS-IS level-1 routing table - destination is localThe 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.
Router# which-route 49.0001.0000.0c00.bda8.00Route look-up for destination 49.0001.0000.0c00.bda8.00Found route in ISO IGRP routing table - destination is localThe 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.
Router# which-route greenRoute look-up for destination 39.0001.0000.0c00.7f06.00, GREENFound route in IS-IS level-1 routing tableAdjacency entry used:System Id SNPA Interface State Holdtime Type ProtocolGREEN 0000.0c00.2d55 Ethernet0 Up 91 L1L2 IS-ISArea Address(es): 39.0001Table 36 describes the display fields in the adjacency entry used to reach system green.
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 36 describes the display fields in the adjacency entry used to reach NSAP address 49.0001.1111.1111.1111.00.
Router# which-route 49.0001.1111.1111.1111.00Route look-up for destination 49.0001.1111.1111.1111.00Found route in ISO IGRP routing tableAdjacency entry used:System Id SNPA Interface State Holdtime Type Protocol1111.1111.1111 0000.0c01.151d Ethernet1 Up 38 L1L2 ISO IGRPArea Address(es): 49.0001The following example indicates that the specified address is not found in a routing table:
Router# which-route 47.0003.0000.0000.0000.00Route look-up for destination 47.0003.0000.0000.0000.00Route not foundThe 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.
Router# which-route 49.0003.0000.0000.0000.00Route look-up for destination 49.0003.0000.0000.0000.00Found route in CLNS prefix routing tableRoute entry used:49 [10/0]via 1111.1111.1111, Ethernet1, StaticRelated Commands
clns host
Defines a name-to-NSAP mapping that can then be used with commands requiring NSAPs.
