3.13 Configure, verify, and troubleshoot RIPv2 for IPv4 (excluding authentication, filtering, manual summarization, redistribution)

Configuring RIP is very simple. The following commands configure RIP v2 and RIP for each network:

Router(config)#router rip
Router(config-router)#version 2
Router(config-router)#no auto-summary

There is only two “show” commands for RIP:

Router#show ip rip database auto-summary directly connected, FastEthernet0/0 auto-summary
 [1] via, 00:00:09, FastEthernet0/0 auto-summary directly connected, GigabitEthernet4/0 auto-summary
 [1] via, 00:00:19, GigabitEthernet4/0
Routing Protocol is "rip"
 Outgoing update filter list for all interfaces is not set
 Incoming update filter list for all interfaces is not set
 Sending updates every 30 seconds, next due in 29 seconds
 Invalid after 180 seconds, hold down 180, flushed after 240
 Redistributing: rip
 Default version control: send version 2, receive version 2
 Interface Send Recv Triggered RIP Key-chain
 FastEthernet0/0 2 2
 GigabitEthernet4/0 2 2
 Automatic network summarization is not in effect
 Maximum path: 4
 Routing for Networks:
 Routing Information Sources:
 Gateway Distance Last Update 120 00:00:38 120 00:00:31
 Distance: (default is 120)

To verify RIP check the routing table:

Router#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
 D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
 E1 - OSPF external type 1, E2 - OSPF external type 2
 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
 ia - IS-IS inter area, * - candidate default, U - per-user static route
 o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
C is directly connected, FastEthernet0/0
R [120/1] via, 00:00:24, FastEthernet0/0
C is directly connected, GigabitEthernet4/0
R [120/1] via, 00:00:05, GigabitEthernet4/0

If routes are missing this could mean:

  1. missing network command(s)
  2. interface or neighbor down
  3. mismatched RIP version
  4. ACLs blocking updates
    1. RIP v2 uses the multicast address

To troubleshoot RIPv2 use the debug commands:

Router#debug ip rip events
RIP event debugging is on
Router#debug ip rip database
RIP database events debugging is on
*Apr 21 16:02:04.807: RIP: sending v2 update to via GigabitEthernet4/0 (
*Apr 21 16:02:04.807: RIP: Update contains 2 routes
*Apr 21 16:02:04.807: RIP: Update queued
*Apr 21 16:02:04.811: RIP: Update sent via GigabitEthernet4/0
*Apr 21 16:02:13.907: RIP: received v2 update from on GigabitEthernet4/0
*Apr 21 16:02:13.907: RIP-DB: network_update with succeeds
*Apr 21 16:02:13.911: RIP-DB: adding (metric 1) via on GigabitEthernet4/0 to RIP database
*Apr 21 16:02:13.911: RIP: Update contains 1 routes
*Apr 21 16:02:15.775: RIP: sending v2 update to via FastEthernet0/0 (
*Apr 21 16:02:15.775: RIP: Update contains 2 routes
*Apr 21 16:02:15.775: RIP: Update queued
*Apr 21 16:02:15.779: RIP: Update sent via FastEthernet0/0
*Apr 21 16:02:17.587: RIP: received v2 update from on FastEthernet0/0
*Apr 21 16:02:17.587: RIP-DB: network_update with succeeds
*Apr 21 16:02:17.591: RIP-DB: adding (metric 1) via on FastEthernet0/0 to RIP database

Leave a comment

Your email address will not be published. Required fields are marked *