debug ip rip event

Use the debug ip rip command to display information on Routing Information Protocol (RIP) routing transactions. The no form of this command disables debugging output.

[no] debug ip rip event

The debug ip rip command will start debugging RIP advertisements. Updates that are sent and received through interfaces of the router are displayed on the terminal if this command is configured. If the network does not change and nothing happens to the link status, the debug information will repeat every time the update timer expires.

RouterA#debug ip rip

RIP: sending v1 update to 255.255.255.255 via Ethernet0    (205.187.18.1)
     network 205.187.22.0, metric 2
     network 205.187.23.0, metric 2
     network 205.187.20.0, metric 1
     network 205.187.21.0, metric 2
     network 205.187.19.0, metric 1
RIP: sending v1 update to 255.255.255.255 via Serial0 (205.187.20.1)
     network 205.187.23.0, metric 2
     network 205.187.18.0, metric 1
     network 205.187.19.0, metric 1
RIP: sending v1 update to 255.255.255.255 via Serial1 (205.187.19.1)
     network 205.187.20.0, metric 1
     network 205.187.21.0, metric 2
     network 205.187.18.0, metric 1
RIP: received v1 update from 205.187.19.6 on Serial1
     205.187.22.0 in 1 hops
     205.187.23.0 in 1 hops
     205.187.21.0 in 2 hops
RIP: received v1 update from 205.187.20.5 on Serial0
     205.187.22.0 in 1 hops
     205.187.23.0 in 2 hops
     205.187.21.0 in 1 hops
  

Consider a portion of the above output:

RIP: received v1 update from 205.187.20.5 on Serial0
     205.187.22.0 in 1 hops
     205.187.23.0 in 2 hops
     205.187.21.0 in 1 hops
  

The Serial0 interface of the router is receiving RIP Version1, denoted by v1, from 205.187.20.5. The next lines are the routes the sending router knows or can get to. The hop count associated with each route entry is included in its advertisement.

Note: When a router is calculating hop count, it will count hops from the perspective of the neighboring router. The general rule is to add one to the hop count of the current routing information before advertising the routes.

RIP: sending v1 update to 255.255.255.255 via Ethernet0    (205.187.18.1)
     network 205.187.22.0, metric 2
     network 205.187.23.0, metric 2
     network 205.187.20.0, metric 1
     network 205.187.21.0, metric 2
     network 205.187.19.0, metric 1
  

Here the router is sending Version1 updates, denoted by v1, on the Ethernet0 interface. RIP updates are sent as either broadcasts or multicasts to the broadcast address, so the router is advertising to the broadcast address 255.255.255.255. In the above output, the router is claiming that it can reach five networks. The updates will contain directly connected networks and also routes learned via RIP.

Entries such as the following appear at startup or when an event occurs such as an interface transitioning or a user manually clearing the routing table:

RIP: broadcasting general request on Ethernet0
RIP: broadcasting general request on Ethernet1
  

An entry such as the following is most likely caused by a malformed packet from the transmitter:

RIP: bad version 128 from 160.89.80.43

Note: although in a real network if the network setup does not change or the link status does not alter, the output of debug ip rip will repeat itself every time the update timer expires, in the Cisco Interactive Mentor (CIM) environment output will not be continous. One complete ouput will be displayed.