CLNS ping and traceroute

Cisco IOS Software provides ping and traceroute tools for ISO CLNP, which are analogous to the all-too-familiar IP version. ping clns and traceroute clns apparently were designed for use in ISO CLNP environments, yet they can be useful for troubleshooting IS-IS operation problems in IP environments. Contrary to popular belief, the clns router isis command is not required to enable the ping clns and traceroute clns commands to work. You might recall that, in addition to the IS-IS process, only the ip router isis command is required to activate IS-IS routing for IP only on a router's interface. Examples 11-34 through 11-38 demonstrate the operation of the CLNS-based ping clns and traceroute clns commands. These examples are based on Figure 11-11. There is an extended option for each of these commands, just as in the case of the corresponding IP versions.

Figure 11-11. Basic Network for Testing Operation of the ping clns and traceroute clns Commands

Example 11-34 Operation of the ping clns Command

 RT5#  ping clns 49.0002.0000.0000.0006.00  Type escape sequence to abort.  Sending 5, 100-byte CLNS Echos with timeout 2 seconds  !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms 

Example 11-35 Operation of the ping clns Command in Extended Mode

 RT5#  ping  Protocol [ip]:  clns   Target CLNS address: 49.0002.0000.0000.0006.00  Repeat count [5]:  2  Datagram size [100]: Timeout in seconds [2]: Extended commands [n]:  y   Source CLNS address [49.0001.0000.0000.0005.00]:  Include global QOS option? [yes]: Pad packet? [no]: Validate reply data? [no]: Data pattern [0xABCD]: Sweep range of sizes [n]: Verbose reply? [no]: Type escape sequence to abort. Sending 2, 100-byte CLNS Echos with timeout 2 seconds !! Success rate is 100 percent (2/2), round-trip min/avg/max = 4/4/4 ms 

Example 11-36 shows the packet debugs during operation of the ping clns command (see Examples 11-34 and 11-35). The debugs show the source and destination NSAPs, as well as the outgoing interface for each outgoing packet.

Example 11-36 CLNS Packet Debugs During CLNS ping s

 RT5#  debug clns packets  Mar 10 07:50:43:  CLNS: Originating packet, size 100  Mar 10 07:50:43:  from 49.0001.0000.0000.0005.00   to 49.0002.0000.0000.0006.00  via 0000.0000.0001 (Ethernet0/0 00d0.58f7.8941) Mar 10 07:50:43: CLNS:  Echo Reply PDU received on Ethernet0/0!  Mar 10 07:50:43: CLNS: Originating packet, size 100 Mar 10 07:50:43:       from 49.0001.0000.0000.0005.00       to 49.0002.0000.0000.0006.00       via 0000.0000.0001 (Ethernet0/0 00d0.58f7.8941) Mar 10 07:50:43: CLNS: Echo Reply PDU received on Ethernet0/0! 

Examples 11-37 and 11-38 illustrate the operation of the traceroute clns command in standard and extended modes from RT5 to RT6. As in the case of the ping clns command, operation in extended mode allows customization of the command, including explicit specification of the source NSAP address of the traceroute packets.

Example 11-37 Operation of traceroute clns Command

 RT5#  traceroute clns 49.0002.0000.0000.0006.00  Type escape sequence to abort.  Tracing the route to  49.0002.0000.0000.0006.00   1 49.0001.0000.0000.0001.00 0 msec ! 0 msec ! 0 msec !   2 49.0002.0000.0000.0002.00 0 msec ! 0 msec ! 0 msec !   3 49.0002.0000.0000.0006.00 0 msec ! 0 msec ! 0 msec ! 

Example 11-38 Operation of traceroute clns Command in Extended Mode

 RT5#  traceroute  Protocol [ip]:  clns    Target CLNS address: 49.0002.0000.0000.0006.00   Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Extended commands [n]:  y    Source CLNS address [49.0001.0000.0000.0005.00]:   Include global QOS option? [yes]: Pad packet? [no]: Validate reply data? [no]: Data pattern [0x60CD]: Sweep range of sizes [n]: Verbose reply? [no]: Type escape sequence to abort. Tracing the route to  49.0002.0000.0000.0006.00  1 49.0001.0000.0000.0001.00 4 msec ! 0 msec ! 0 msec !   2 49.0002.0000.0000.0002.00 0 msec ! 0 msec ! 0 msec !  3 49.0002.0000.0000.0006.00 0 msec ! 0 msec ! 0 msec !