Troubleshooting Ipx Rip; Troubleshooting Ipx Sap - H3C MSR3600-51F Configuration Manual

•
Enable IPX packet debugging using the debugging ipx packet command. According to the
detailed information displayed about IPX packets received, transmitted, forwarded, and
discarded, you can locate the error.
Packets are discarded
If IPX packet debugging information displays that a packet is discarded, and the information
displayed is Packet size is greater than interface MTU!, it indicates that 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
cannot be sent out this interface.
SAP packets cannot be received
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.
IPX type 20 packets cannot be transmitted to any other network segment
•
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
cannot 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

No routes can be learned from a peer
•
Enable IPX RIP debugging using the debugging ipx rip packet verbose command. Check
whether RIP packets can be received from the peer. If not, problems on the lower layer
connection of the two devices might 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 to the routing table. If not, faults
occurred when the route was added to the routing table. Possible faults could be that the packet
encapsulation formats of the end interfaces do not match, or a bad RIP packet is received and
discarded.
A static route is redistributed to IPX RIP but no static route is advertised
•
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 outgoing interface is down. When the route becomes
active, it can be advertised as a RIP route.
•
If the static route exists in the outing table, check its hops. If hops are more than or equal to 15,
the static route cannot be advertised.

Troubleshooting IPX SAP

Unable to add a static service information item to SIT
•
Use the display ipx service-table inactive command to see whether the item is inactive. If so,
it indicates that no active route to the destination server exists.
11