Pure CLNS Routing Network

Below verifies the CLNS configuration on RT3. RT3 (49.0001.3333.3333.3333.00) is able to reach RT4 (49.0002.4444.4444.4444.00):

RT3#sh clns
Global CLNS Information:
  1 Interfaces Enabled for CLNS
  NET: 49.0001.3333.3333.3333.00
  Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64
  ERPDU's requested on locally generated packets
  End system operation only (CLNS forwarding not allowed)
RT3#
RT3#sh clns interface
FastEthernet0/0 is up, line protocol is up
  Checksums enabled, MTU 1497, Encapsulation SAP
  ERPDUs enabled, min. interval 10 msec.
  CLNS fast switching enabled
  CLNS SSE switching disabled
  DEC compatibility mode OFF for this interface
  Next ESH/ISH in 42 seconds
RT3#
RT3#sh clns neighbors

System Id      Interface   SNPA                State  Holdtime  Type Protocol
1111.1111.1111 Fa0/0       cc00.0f38.0000      Up     279       IS   ES-IS
RT3#
RT3#sh clns route
Codes: C - connected, S - static, d - DecnetIV
       I - ISO-IGRP,  i - IS-IS,  e - ES-IS
       B - BGP,       b - eBGP-neighbor

C  49.0001.3333.3333.3333.00 [1/0], Local NET

S  Default Prefix [10/0]
      via 49.0001.1111.1111.1111.00
RT3#
RT3#debug clns packets
CLNS packets debugging is on
RT3#
RT3#ping 49.0002.4444.4444.4444.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 = 92/130/160 ms
RT3#
00:01:36: CLNS: Originating packet, size 100
00:01:36:       from 49.0001.3333.3333.3333.00
      to 49.0002.4444.4444.4444.00
      via 1111.1111.1111 (FastEthernet0/0 cc00.0f38.0000)
00:01:36: CLNS: Echo Reply PDU received on FastEthernet0/0!
00:01:36: CLNS: Originating packet, size 100
00:01:36:       from 49.0001.3333.3333.3333.00
      to 49.0002.4444.4444.4444.00
      via 1111.1111.1111 (FastEthernet0/0 cc00.0f38.0000)
00:01:36: CLNS: Echo Reply PDU received on FastEthernet0/0!
--- output omitted ---

The which-route {nsap-addr | clns-name} privileged command displays the OSI routing table in which the specified CLNS destination is found. This command determines the next-hop router and is important when troubleshooting configuration with multiple processes running.

RT1#which-route 49.0001.1111.1111.1111.00
Route look-up for destination 49.0001.1111.1111.1111.00
  Found route in IS-IS level-1 routing table - destination is local
RT1#
RT1#which-route 49.0001.2222.2222.2222.00
Route look-up for destination 49.0001.2222.2222.2222.00
  Route not found
RT1#
RT1#which-route 49.0001.3333.3333.3333.00
Route look-up for destination 49.0001.3333.3333.3333.00
  Found route in IS-IS level-1 routing table

Adjacency entry used:
System Id      Interface   SNPA                State  Holdtime  Type Protocol
3333.3333.3333 Fa0/0       cc02.03fc.0000      Up     277       IS   ES-IS
  Area Address(es): 49.0001
  Uptime: 00:01:59
RT1#
RT1#which-route 49.0002.4444.4444.4444.00
Route look-up for destination 49.0002.4444.4444.4444.00
  Found route in CLNS L2 prefix routing table

Route entry used:
i  49.0002 [110/10]
      via RT2, FastEthernet1/0

Adjacency entry used:
System Id      Interface   SNPA                State  Holdtime  Type Protocol
RT2            Fa1/0       cc01.03fc.0010      Up     8         L2   IS-IS
  Area Address(es): 49.0002
  Uptime: 00:02:16
  NSF capable
RT1#which-route 49.0002
Route look-up for destination 49.0002
  Found route in CLNS L2 prefix routing table

Route entry used:
i  49.0002 [110/10]
      via RT2, FastEthernet1/0

Adjacency entry used:
System Id      Interface   SNPA                State  Holdtime  Type Protocol
RT2            Fa1/0       cc01.03fc.0010      Up     9         L2   IS-IS
  Area Address(es): 49.0002
  Uptime: 00:02:27
  NSF capable
RT1#

Route information can reside in the following table:
= IS-IS Level 1 routing table
= ISO IGRP System ID or area routing table
= Prefix routing table (IS-IS Level 2 routes, ISO IGRP domain routes, and static routes)
= Adjacency table