Novell NETWARE 6-DOCUMENTATION Manual page 1856

Services or Routes are Fluctuating Excessively
set to Off. If this is the case, and if you want to run RIP between the
servers, then set RIP State to On.
Cause 2 —Two NLSP systems are configured with different area addresses.
In this case, the Initialization Failures counter in IPXCON should be
increasing (parameter path: Select Circuits > Detailed Circuit Information).
If you are on an area boundary and you are using RIP as the interarea protocol,
configure RIP on both systems on the interface through which they are
communicating.
Cause 3 —One of the routers has the RIP State option set to Auto. If you
intended to use RIP for interarea routing on the network, this condition is
potentially serious. If the two NLSP routers are in communication with each
other, they continue to run RIP. However, if they are connected together with
a bridge or hub and that hardware fails and is brought up again sometime later,
NLSP does not detect the condition and RIP does not turn on again.
If you are running RIP and SAP on the network and the routes and services
fluctuate, refer to "Services or Routes are Fluctuating Excessively."
The number of routes and services are fluctuating excessively. Some
fluctuation is normal in a large network. Change is occurring constantly as
systems are brought down for maintenance and other reasons. However,
hundreds of routes and services appearing and disappearing indicates a
network error. All the following problems are solved with the same procedure:
Cause 1 —Misconfiguration with RIP and SAP.
Cause 2 —Problem with a link.
Cause 3 —Error in NLSP.
Cause 4 —Two systems are competing for a system ID.
Cause 5 —LAN is generating errors.
First try to determine which systems are affected. It might be helpful to
determine which services are appearing and disappearing and to trace the
paths backward to their location. If many services are appearing and
disappearing, it might work better to find the set of affected systems. In
either case, you should be able to determine the boundary routers.
Troubleshooting 145