System information

Troubleshooting Novell IPX 8-151
IPX RIP: No Connectivity over IPX RIP Router
Missing ipx network
commands on interface
To enable IPX protocol processing on an interface, enter the ipx network
number interface configuration command:
ipx network network [encapsulation encapsulation-type [secondary]]
Syntax Description:
• network—Network number. This is an eight-digit hexadecimal number
that uniquely identifies a network cable segment. It can be a number in
the range 1 to FFFFFFFE. You do not need to specify leading zeros in
the network number. For example, for the network number 000000AA
you can enter just AA.
• encapsulation encapsulation-type—(Optional) Type of encapsulation.
It can be one of the following values:
❍ arpa (for Ethernet interfaces only)—Use Novell’s Ethernet II
encapsulation. This encapsulation is recommended for networks that
handle both TCP/IP and IPX traffic.
❍ hdlc (for serial interfaces only)—Use HDLC encapsulation.
❍ novell-ether (for Ethernet interfaces only)—Use Novell’s Ethernet
802.3 encapsulation. This encapsulation consists of a standard 802.3
MAC header followed directly by the IPX header with a checksum of
FFFF. It is the default encapsulation used by NetWare Version 3.11.
❍ sap (for Ethernet interfaces)—Use Novell’s Ethernet 802.2
encapsulation. This encapsulation consists of a standard 802.3 MAC
header followed by an 802.2 LLC header. This is the default
encapsulation used by NetWare Version 4.0. (for Token Ring
interfaces)—This encapsulation consists of a standard 802.5 MAC
header followed by an 802.2 LLC header. (for FDDI interfaces)—This
encapsulation consists of a standard FDDI MAC header followed by an
802.2 LLC header.
Missing ipx network
commands on interface
❍ snap (for Ethernet interfaces)—Use Novell Ethernet Snap
encapsulation. This encapsulation consists of a standard 802.3 MAC
header followed by an 802.2 SNAP LLC header. (for Token Ring and
FDDI interfaces)—This encapsulation consists of a standard 802.5 or
FDDI MAC header followed by an 802.2 SNAP LLC header.
• secondary—(Optional) Indicates an additional network configured
after the first (primary) network.
RIP timer mismatch You can change RIP timer values changed on servers running NetWare 4.x or later.
Mismatches between routers and servers can cause connectivity problems.
Step 1 Use the show ipx interfaces privileged exec command on the router to
view the state of IPX interfaces. Look for output similar to the following:
C4500#show ipx interface
[...]
Updates each 60 seconds, aging multiples RIP: 3 SAP: 3
[...]
Compare the timer value configured on the router with that configured on
Novell servers.
Step 2 The timer values configured on servers and routers should be the same
across the whole IPX network.
Reconfigure the router or the servers to bring the timer values into
conformance. On the router, use the ipx update-time interface
configuration command to change the RIP timer interval.
For information on changing the timer value configured on Novell
servers, consult your server documentation.
Possible Problem Solution