Novell NETWARE 6-DOCUMENTATION Manual page 1860

CALLMGR Shows an IPX Circuit but IPXCON Does Not
Single System Is Entering an Overloaded State
Many Systems Are Entering an Overloaded State
Cause 6 —Load sharing is enabled between dissimilar paths.
Verify that the two paths have comparable media and data rates.
CALLMGR shows an IPX circuit but IPXCON does not.
IPXCON does not show a circuit until after IPXWAN has completed
negotiation.
Check the link for errors, and make sure that both sides of the IPX link are
implementing IPXWAN properly.
A single system is in an overloaded state.
Cause 1 —System is running out of memory.
Cause 2 —Another system is experiencing database overload. It is possible
that another system in an overloaded state is causing your system to go into an
overloaded state.
On each suspect system, use MONITOR to check whether the Alloc Memory
Pool is set too low. If the value is too low, increase the value set for the Alloc
Memory Pool or remove some applications.
Cause 3 —Transient condition on that router.
If the problem persists, the system is running out of memory. If the value is
too low, increase the value set for the Alloc Memory Pool or remove some
applications.
Many systems are entering an overloaded state.
Cause 1 —Systems are being overrun with routing information. Possibly the
number of systems in the NLSP area has exceeded the number you originally
intended.
Using IPXCON, look at the number of routers in the area (parameter path:
Select NLSP Information > Routers). Add this number to the number of LANs
in the area. This sum is a good indicator of the amount of memory that is
Troubleshooting 149