Information Technology Reference
In-Depth Information
Table12-9 ISO CLNS: Poor Performance (continued)
Possible Problem
Solution
Bridge or repeater
in parallel with
router
A bridge or repeater in parallel with a router can cause updates
and traffic to be seen from both sides of an interface.
1.
Use the
show clns is-neighbors detail
and the
show clns
neighbors detail
exec commands to see through which
routers and protocols the router's adjacencies were learned.
The following is sample output from the
show clns neighbors
detail
command:
router#
show clns neighbors detail
System Id SNPA Interface State
Holdtime Type Protocol
000.0000.0007 aa00.0400.6408 Ethernet0 Init 291
IS ES-IS
Area Address(es): 47.0005.80FF.F500.0000.0003.0020
0000.0C00.0C35 0000.0c00.0c36 Ethernet1 Up
94
L1 IS-IS
Area Address(es): 47.0004.004D.0001 39.0001
0800.2B16.24EA aa00.0400.2d05 Ethernet0 Up
9
L1L2 IS-IS
Area Address(es): 47.0004.004D.0001
0800.2B14.060E aa00.0400.9205 Ethernet0 Up
1651
ES ES-IS
Area Address(es): 49.0040
0000.0C00.3E51 *HDLC*
Serial1
Up
27
L2 IS-IS
Area Address(es): 39.0004
0000.0C00.62E6 0000.0c00.62e7 Ethernet1 Up
26
L1 IS-IS
Area Address(es): 47.0004.004D.0001
oA00.0400.2D05 aa00.0400.2d05 Ethernet0 Init 29
IS ES-IS
Area Address(es): 47.0004.004D.0001
Look for routers that are known to be on a remote network. A
router listed in the adjacency table but that is not on a directly
connected network indicates a problem.
You can also look for paths to networks (or areas) on multiple
interfaces.
If you determine that there is a parallel bridge or repeater,
remove the device or configure filters that block routing
updates from being learned from the device.
2.
Route
redistribution
problem
Misconfigured route redistribution can cause performance
problems. For specific troubleshooting information, see the
section “ISO CLNS: Redistribution Causes Routing Problems”
earlier in this chapter.
