Novell NETWARE 6-DOCUMENTATION Manual page 1857

Heavy Network-Layer Traffic Occurs on a Point-to-Point Link
146 Internetwork Packet Exchange
In NLSP, this determination is easy to make. Simply look at an affected
system's neighbors to see whether they have the problem, too. Examine
each system as you move outward. If just a single NLSP system is
experiencing the problem, then the cause is probably a local connectivity
problem. Check the system for neighbor state changes and disappearing
services.
Try to determine whether the problem has a boundary. If you see a system
in which one set of routers or services is disappearing and see an adjacent
system in which a different set of routers or services is disappearing, you
probably have found the boundary. Check to determine whether any of
these systems has problems with its neighbors, has fluctuating links, or
has a duplicate system ID.
If you find that the problem is isolated to a LAN, then follow the
procedures described under
Unreachable Intermittently" on page
that is supplying routing information to the network is losing its
neighbors, particularly the Designated Router. This system is probably
the source of the problem.
If you find that the problem is caused by some interaction with RIP and
SAP, check all systems for consistency on the LAN regarding the
following configurable RIP and SAP parameters in NIASCFG: Packet
Size Override, Periodic Update Interval, and Aging Interval Multiplier
(parameter path: Select Bindings > a specific interface > Expert Bind
Options > RIP (or SAP) Bind Options).
You should never let a periodic multiplier be less than 4. Because of timer
skew, this means that after three packets containing the same route are
dropped, the system loses this route. If any of the previously listed RIP
and SAP parameters are different, you must reconfigure the values. Better
still, use the default values, especially on LANs. Using different values
for the timers is too risky to justify the savings on a LAN.
There is heavy Network-layer traffic on a point-to-point link and you are
using RIP and SAP.
Migrate to NLSP.
There is heavy Network-layer traffic on a point-to-point link and you are
using NLSP.
"Multiple Systems on a LAN Become
138. You might find that one system