Monitoring RIP Traffic
Monitoring RIP Routing Information
Purpose
This topic applies only to the J-Web Application package.
Use the monitoring functionality to monitor RIP routing on routing devices.
Action
To view RIP routing information in the J-Web interface, select Monitor > Routing > RIP Information.
To view RIP routing information in the CLI, enter the following CLI commands:
show rip statisticsshow rip neighbor
Meaning
Table 1 summarizes key output fields in the RIP routing display in the J-Web interface.
Field |
Values |
Additional Information |
|---|---|---|
| RIP Statistics | ||
Protocol Name |
The RIP protocol name. |
|
Port number |
The port on which RIP is enabled. |
|
Hold down time |
The interval during which routes are neither advertised nor updated. |
|
Global routes learned |
Number of RIP routes learned on the logical interface. |
|
Global routes held down |
Number of RIP routes that are not advertised or updated during the hold-down interval. |
|
Global request dropped |
Number of requests dropped. |
|
Global responses dropped |
Number of responses dropped. |
|
| RIP Neighbors | ||
Neighbor |
Name of the RIP neighbor. |
This value is the name of the interface on which RIP is enabled. Click the name to see the details for this neighbor. |
State |
State of the RIP connection: Up or Dn (Down). |
|
Source Address |
Local source address. |
This value is the configured address of the interface on which RIP is enabled. |
Destination Address |
Destination address. |
This value is the configured address of the immediate RIP adjacency. |
Send Mode |
The mode of sending RIP messages. |
|
Receive Mode |
The mode in which messages are received. |
|
In Metric |
Value of the incoming metric configured for the RIP neighbor. |
|
Verifying a RIP Configuration
To verify a RIP configuration, perform the following tasks:
Verifying the RIP-Enabled Interfaces
Purpose
Verify that all the RIP-enabled interfaces are available and active.
Action
From the CLI, enter the show rip neighbor command.
Sample Output
command-name
user@host> show rip neighbor Source Destination Send Receive In Neighbor State Address Address Mode Mode Met -------- ----- ------- ----------- ---- ------- --- ge-0/0/0.0 Dn (null) (null) mcast both 1 ge-0/0/1.0 Up 192.168.220.5 224.0.0.9 mcast both 1
Meaning
The output shows a list of the RIP neighbors that are configured on the device. Verify the following information:
Each configured interface is present. Interfaces are listed in alphabetical order.
Each configured interface is up. The state of the interface is listed in the Destination State column. A state of Up indicates that the link is passing RIP traffic. A state of Dn indicates that the link is not passing RIP traffic. In a point-to-point link, this state generally means that either the end point is not configured for RIP or the link is unavailable.
Verifying Reachability of All Hosts in the RIP Network
Purpose
By using the traceroute tool on each loopback address in the network, verify that all hosts in the RIP network are reachable from each Juniper Networks device.
Action
For each device in the RIP network:
In the J-Web interface, select Troubleshoot>Traceroute.
In the Remote Host box, type the name of a host for which you want to verify reachability from the device.
Click Start. Output appears on a separate page.
Sample Output
command-name
1 172.17.40.254 (172.17.40.254) 0.362 ms 0.284 ms 0.251 ms 2 routera-fxp0.englab.mycompany.net (192.168.71.246) 0.251 ms 0.235 ms 0.200 ms
Meaning
Each numbered row in the output indicates a routing hop in the path to the host. The three-time increments indicate the round-trip time (RTT) between the device and the hop for each traceroute packet.
To ensure that the RIP network is healthy, verify the following information:
The final hop in the list is the host you want to reach.
The number of expected hops to the host matches the number of hops in the traceroute output. The appearance of more hops than expected in the output indicates that a network segment is probably unreachable. It might also indicate that the incoming or outgoing metric on one or more hosts has been set unexpectedly.
Verifying the Exchange of RIP Messages
Purpose
Verify that RIP messages are being sent and received on all RIP-enabled interfaces.
Action
From the CLI, enter the show rip statistics command.
Sample Output
command-name
user@host> show rip statistics
RIPv2 info: port 520; holddown 120s.
rts learned rts held down rqsts dropped resps dropped
10 0 0 0
t1-0/0/2.0: 0 routes learned; 13 routes advertised; timeout 120s; update interval 45s
Counter Total Last 5 min Last minute
------- ----------- ----------- -----------
Updates Sent 2855 11 2
Triggered Updates Sent 5 0 0
Responses Sent 0 0 0
Bad Messages 0 0 0
RIPv1 Updates Received 0 0 0
RIPv1 Bad Route Entries 0 0 0
RIPv1 Updates Ignored 0 0 0
RIPv2 Updates Received 41 0 0
RIPv2 Bad Route Entries 0 0 0
RIPv2 Updates Ignored 0 0 0
Authentication Failures 0 0 0
RIP Requests Received 0 0 0
RIP Requests Ignored 0 0 0
ge-0/0/1.0: 10 routes learned; 3 routes advertised; timeout 180s; update interval 30s
Counter Total Last 5 min Last minute
------- ----------- ----------- -----------
Updates Sent 2855 11 2
Triggered Updates Sent 3 0 0
Responses Sent 0 0 0
Bad Messages 1 0 0
RIPv1 Updates Received 0 0 0
RIPv1 Bad Route Entries 0 0 0
RIPv1 Updates Ignored 0 0 0
RIPv2 Updates Received 2864 11 2
RIPv2 Bad Route Entries 14 0 0
RIPv2 Updates Ignored 0 0 0
Authentication Failures 0 0 0
RIP Requests Received 0 0 0
RIP Requests Ignored 0 0 0
Meaning
The output shows the number of RIP routes learned. It also shows the number of RIP updates sent and received on the RIP-enabled interfaces. Verify the following information:
The number of RIP routes learned matches the number of expected routes learned. Subnets learned by direct connectivity through an outgoing interface are not listed as RIP routes.
RIP updates are being sent on each RIP-enabled interface. If no updates are being sent, the routing policy might not be configured to export routes.
RIP updates are being received on each RIP-enabled interface. If no updates are being received, the routing policy might not be configured to export routes on the host connected to that subnet. The lack of updates might also indicate an authentication error.