Nlsp Decision Process Is Running Frequently (Duplicate System Id); Other Router Names Are Not Displayed; System Frequently Appears And Disappears On The Lan - Novell NETWARE 6-DOCUMENTATION Manual

NLSP Decision Process Is Running Frequently (Duplicate System ID)

Other Router Names Are Not Displayed

System Frequently Appears and Disappears on the LAN

Cause 2 —NLSP has a software error that is either corrupting the graph
or causing the graph to be represented incorrectly.
Contact technical support.
The NLSP decision process is running frequently.
To observe this symptom, obtain access to a NetWare server or router running
NLSP in the network and enter SET ISUL DEBUG=256 at the system
console prompt. Every time the decision process runs, an entry is displayed at
the system console. If the decision process runs at least every 30 seconds,
there might be a duplicate system ID.
Change the internal network number of one of the conflicting systems, or
remove one of the systems from the network immediately. For information
about how to find the malfunctioning node, refer to
Problems (Duplicate ID or Network Number)" on page
If other router names do not display when the DISPLAY SERVERS command
is used, the NLSP Local Area Addresses might be different. Load NIASCFG
and select Configure NIAS > Protocols and Routing > Network Interfaces >
IPX > IPX Expert Configuration option to set the IPX network number and
area mask to zeros.
A system frequently appears and disappears on the LAN.
Cause 1 .—System is not transmitting its packets to the Designated Router
properly.
At the Designated Router, check the Neighbor State Changes option in
IPXCON (parameter path: Select Circuits > a specific circuit > Detailed
Circuit Information) and monitor it for the circuit (LAN).
If the number is increasing but there are no new systems on the network
and systems are not being bound and unbound or restarted, then a local
connectivity problem probably exists.
"IPX Connectivity
129.
Troubleshooting 135