System information
Troubleshooting Novell IPX
Book Title
8-162
IPX Enhanced IGRP: Router Stuck in Active Mode
Symptom: An IPX Enhanced IGRP router is stuck in Active mode. The router repeatedly sends
error messages similar to the following:
%DUAL-3-SIA: Route 3c.0800.0c00.4321 Stuck-in-Active
SAP updates are being sent
incrementally rather than
periodically
Connectivity problems can occur when LAN interfaces are configured to send
incremental (not periodic) SAP updates on segments that have attached Novell
clients or servers. Incremental SAP updates are sent only when there is a change in
the SAP table.
Step 1 Use the show running-config privileged exec command to view the
router configuration. Look for ipx sap-incremental eigrp interface
configuration command entries on interfaces with attached Novell clients
or servers.
Step 2 If the command is present and the interface in question has attached
Novell clients or servers, you must disable the ipx sap-incremental eigrp
command. This command should be configured on an interface only if all
the nodes attached to that interface are Enhanced IGRP peers.
Link problem
Step 1 Use the show interfaces privileged exec command and look for drops and
interface resets.
The following is sample output from the show interfaces command:
Router#show interfaces fastethernet 1/0
FastEthernet1/0 is up, line protocol is up
Hardware is cyBus FastEthernet Interface, address is
0010.5498.d020 (bia 0010. 5498.d020)
Internet address is 208.84.3.33/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely
255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set
(10 sec), hdx, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:07, output 00:00:07, output hang
never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Link problem Step 2 If you see many drops or interface resets, use the debug ipx sap activity
privileged exec command and then the clear ipx eigrp neighbor
privileged exec command.
Caution: Because debugging output is assigned high priority in the CPU
process, it can render the system unusable. For this reason, use debug
commands only to troubleshoot specific problems or during
troubleshooting sessions with Cisco technical support staff. Moreover, it
is best to use debug commands during periods of lower network traffic
and fewer users. Debugging during these periods decreases the likelihood
that increased debug command processing overhead will affect system
use.
If there is a link problem, the debug ipx sap activity command will not
produce any output.
Step 3 Refer to the appropriate chapter elsewhere in this book for information on
troubleshooting the particular link type. For example, for serial links,
refer to Chapter 15, “Troubleshooting Serial Line Problems.”
Possible Problem Solution