Troubleshooting Ipx Rip - HP A-MSR Series Configuration Manual

Symptom 5
IPX type 20 packets cannot be transmitted to any other network segment.
Solution
 Use display ipx interface 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 debugging ipx packet. 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 is not forwarded further.

Troubleshooting IPX RIP

Symptom 1
No routes can be learned from a peer.
Solution
Enable IPX RIP debugging using debugging ipx rip packet verbose. Check whether RIP packets can be

received 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 debugging ipx rip event 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.
Symptom 2
A static route is redistributed to IPX RIP but no static route is advertised.
Solution
Use display ipx routing-table to check whether the static route exists.

If the static route is not available, use display ipx routing-table verbose 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.
13