Product specifications

Efficient Networks
®
Router family
Technical Reference Guide
Chapter 7: Monitoring System Performance
Efficient Networks
®
Page 7-13
IPX Routing
• Check that IPX routing has been enabled and that the remote end is enabled
for IPX routing.
• Validate that the IPX WAN network number matches the remote router’s
WAN network number.
• Check that IPX SAPs correctly identify the servers and applications on the
remote network and have valid network numbers, node numbers, etc.
• Check that every SAP has a router to its internal network.
• Check that the IPX routes (network numbers, hops, and ticks) seeded into
the routing table for network segments and servers beyond the remote router
are correct.
• Validate that the IPX WAN network number matches the remote router’s
WAN network number.
• Check that the IPX routes (network numbers, hops, and ticks) seeded into
the routing table for network segments and servers beyond the remote router
are correct.
• Check that IPX SAPs correctly identify the servers and applications on the
remote network and have valid network numbers, node numbers, etc.
• Be sure to reboot if IPX addresses, routes, SAPs or control has been
changed.
• If the router fails to negotiate IPX:
– Make sure that at least one WAN number is not equal to zero at one end
of the link.
– The server must have an IPX route to the remote LAN.
– The Novell server needs to have burst mode turned on.
– Large Internet packets have to be turned on.
• For Novell 3.12 and later:
– Client needs VLM.EXE, net.cfg: large Internet packets=ON, Pburst=5
• If you can’t see the server SAPs:
– Check the frame types using the eth list command and ensure that they
are the same on both routers.
– Check that the Ethernet cable is correctly plugged in.
– Make sure that the Novell server is up.
Incorrect VPI/VCI (ATM Routers)
If you are given an incorrect VCI/VPI number or none at all to use for the remote, and
you need to determine what the possible value might be, use the atom findpvc
command.