System information

Troubleshooting Novell IPX
Book Title
8-164
Table 8-11 IPX Enhanced IGRP: Router Stuck in Active Mode
Possible Problem Solution
Active timer value is
misconfigured
Step 1 The active timer specifies the maximum period of time that an Enhanced
IGRP router will wait for replies to its queries. If the active timer value is
set too low, there might not be enough time for all the neighboring routers
to send their replies to the active router. A value of 3 (3 minutes, which is
the default value) is strongly recommended to allow all Enhanced IGRP
neighbors to reply to queries.
Step 2 Check the configuration of each Enhanced IGRP router using the show
running-config privileged exec command. Look for a timers active-time
router configuration command entry.
Step 3 The value set by the timers active-time command should be consistent
among routers in the same autonomous system. A value of 3 (3 minutes,
which is the default value) is strongly recommended to allow all
Enhanced IGRP neighbors to reply to queries.
Interface or other hardware
problem
Step 1 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:
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.
Step 2 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.
Step 3 Make sure the suspect router still works. Check the interfaces on the
suspect router. Make sure the interface and line protocol are up and
determine whether the interface is dropping packets. For more
information on troubleshooting hardware, see Chapter 3,
“Troubleshooting Hardware and Booting Problems.”