Troubleshooting Rip; Router Not Receiving Routes - HP 7102dl - ProCurve Secure Router Configuration Manual

C a u t i o n

Troubleshooting RIP

You can scan RIP events to determine the problem by entering the debug
commands shown in Table 15-21 on page 15-150. For example, enter:
ProCurve# debug ip rip
Examine Table 15-22 to learn about the messages associated with particular
problems. The following sections will give general tips on how to troubleshoot
these problems.
Table 15-22. RIP Debug Messages
Message
discard packet from
<A.B.C.D> (source
Address not in RIP
network)
ignored [v1 | v2] packet
from <A.B.C.D> (illegal
version)
you do NOT see:
[v1 | v2] sent <number>
route
RIP debug messages can be processor-intensive.

Router Not Receiving Routes

A router may not receive routes because:
an interface has not been enabled to participate in RIP
an interface is listening for the incorrect RIP version
remote sites are separated by a non-multicast network
IP Routing—Configuring RIP, OSPF, BGP, and PBR
Possible Problem
A RIP interface directly
connects to an interface with
an address on a different
network.
RIP versions are incompatible. • Determine whether the local
• LANs are not participating in
RIP.
• RIP interfaces are passive.
Troubleshooting Routing
Next Best Step
The peer should not be on a
different network.
However, you can add the
peer's network from the RIP
configuration mode context:
network <peer A.B.C.D>
<subnet mask>
or remote peer is configured
for the wrong version.
• If the local router, determine
whether the global version
or a particular interface is
misconfigured.
• Add the LAN to RIP.
• If the LAN should not be
running RIP, redistribute
connected routes.
• Remove the passive-
interface configuration.
15-153