Information Technology Reference
In-Depth Information
Table8-11
IPX Enhanced IGRP: Router Stuck in Active Mode (continued)
Possible Problem
Solution
Interface or other
hardware problem
has occurred.
Use the
show ipx eigrp neighbors
exec command, and
examine the Uptime and Q Cnt (queue count) fields in the
output. The following is sample output from the
show ipx
eigrp neighbors
command:
1.
Router#
show ipx eigrp neighbors
IPX EIGRP Neighbors for process 200
H Address
Interface
Hold Uptime Q
Seq SRTT RTO
(secs) (h:m:s)
Cnt Num (ms) (ms)
6 90.0000.0c02.096e Tunnel44444 13 0:30:57
0 21 9 20
5 80.0000.0c02.34f2 Fddi0 12 0:31:17
0 62 14 28
4 83.5500.2000.a83c TokenRing2 13 0:32:36
0 626 16 32
3 98.0000.3040.a6b0 TokenRing1 12 0:32:37
0 43 9 20
2 80.0000.0c08.cbf9 Fddi0 12 0:32:37
0 624 19 38
1 85.aa00.0400.153c Ethernet2 12 0:32:37
0 627 15 30
0 82.0000.0c03.4d4b Hssi0 12 0:32:38
0 629 12 24
If the uptime counter is continually resetting, or if the queue
count is consistently high, there might be a hardware problem.
Check the output of the “Stuck-in-Active” error message.
The output indicates the general direction of the problem
node, but if there are multiple nodes in that direction, the
problem could be in any one of them.
2.
Make sure that the suspect router still works. Check the
interfaces on the suspect router. Make sure that the interface
and line protocol are up, and determine whether the interface
is dropping packets. For more information on
troubleshooting hardware, see Chapter 3.
3.
