3Com MSR 50 Series Configuration Manual page 2228

2228 C 128: IPX C
HAPTER ONFIGURATION
If IPX packet debugging information displays a packet is discarded, and the
■
prompt is "Packet size is greater than interface MTU!", it indicates the output
packet size is greater than the maximum packet size that the interface can
transmit. Use the display interface command to check the interface MTU and
use the display ipx interface command to check the RIP and SAP packet size.
If RIP or SAP packet size is greater than interface MTU, RIP or SAP packet can
not be sent out this interface.
Symptom 4: SAP packets can not be received.
Solution:
Use the display ipx interface command to check the receiving interface
■
configuration. If SAP is disabled on this interface, SAP packets from this
interface will be discarded.
Symptom 5: IPX type 20 packets can not be transmitted to any network segment.
Solution:
Use the display ipx interface command to check whether the forwarding for
■
IPX type 20 packets is enabled on the receive/send interfaces. If it is not
enabled, IPX type 20 packets can not be forwarded.
Enable IPX packet debugging using the debugging ipx packet command. If
■
the debugging information displays that the type 20 packet is discarded and
the prompt is "Transport Control field of IPX type-20 packet >= 8!", it indicates
the IPX type 20 packet can only be forwarded 8 times. If the upper limit is
reached, the IPX type 20 packet will not be forwarded further.
Troubleshooting IPX RIP
Symptom 1: No routes can be learnt from a peer.
Solution:
Enable IPX RIP debugging using the debugging ipx rip packet verbose
■
command. Check whether there are RIP packets from the peer. If not, problems
on the lower layer connection of the two devices may exist.
If a RIP packet with routing information is received from the peer, use the
■
debugging ipx rip event command to see whether the received route is
added into the routing table. If not, faults occurred when adding the route into
the routing table. Possible faults include: the packet encapsulation formats of
the end interfaces do not match, or a bad RIP packet is received and discarded.
Symptom 2: A static route is redistributed to IPX RIP, but no static route is
advertised.
Solution:
Use the display ipx routing-table command to check whether the static
■
route exists.
If the static route is not available, use the display ipx routing-table verbose
■
command to check whether it is inactive. If so, check further why it is inactive.
Possible reasons could be: the next hop network ID is unreachable, or the