Configuration Example: RIPv2 on Pod#4

Tom4498 · Joined: 05 Oct 2004 Posts: 276 Location: America/New_York

I setup basic isdn, frame-relay and vlans on pod 4.

R1 vlan10 10.1.1.1 <- network command
R2 vlan20 10.2.1.2 <- network command
R3 vlan30 10.3.1.3 <- network command
R4 vlan30 10.3.1.4 <- network command
R7 vlan30 10.3.1.7 <- network command
frame-relay 10.4.1.0 <- hub and spoke with R1 as the hub
isdn 10.5.1.0 <-- static route from R5 and passive interfaces with neighbor commands and all ip traffic allowed with dialer-idle timeout 60

I turned on RIP v2 on all routers. Here is a sample Config from R2:
router rip
version 2
no auto-summary
network 10.2.1.0
network 10.4.1.0

Here is the routing table on R4:
R4#show ip route
Codes: C - connected, S - static, I - IGRP, 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, E - EGP
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

10.0.0.0/24 is subnetted, 5 subnets
C 10.3.1.0 is directly connected, Ethernet0
R 10.2.1.0 [120/2] via 10.4.1.2, 00:00:17, Serial0
R 10.1.1.0 [120/1] via 10.4.1.1, 00:00:17, Serial0
R 10.5.1.0 [120/1] via 10.3.1.7, 00:00:20, Ethernet0
C 10.4.1.0 is directly connected, Serial0

Here is a ping from R4 over isdn to R5 and through R7
R4#ping 10.5.1.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.5.1.5, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 32/35/36 ms

Here is some debug output I got from R4.
R4#debug ip rip
RIP protocol debugging is on
13:35:19: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:35:19: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:35:19: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:35:19: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:35:19: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:35:19: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:35:19: 10.5.1.5/32 via 0.0.0.0 in 1 hops
13:35:19: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:35:19: RIP: build update entries
13:35:19: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:35:19: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:35:19: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:19: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:35:19: RIP: build update entries
13:35:19: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:35:19: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:35:19: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:19: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:19: 10.5.1.0/24 via 0.0.0.00.5., metric 2, tag 0
13:35:19: 10.5.1.5/32 via 0.0.0.0, metric 2, tag 0
13:35:22: RIP: received v2 update from 10.4.1.1 on Serial0
13:35:22: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:35:22: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:35:22: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:35:22: 10.5.1.5/32 via 10.4.1.3 in 3 hops
13:35:45: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:35:45: RIP: build update entries
13:35:45: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:35:45: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:35:46: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:46: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:35:46: RIP: build update entries
13:35:46: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:35:46: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:35:46: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:46: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:35:46: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:35:46: 10.5.1.5/32 via 0.0.0.0, metric 2, tag 0
13:35:47: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:35:47: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:35:47: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:35:47: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:35:48: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:35:48: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:35:48: 10.5.1.5/32 via 0.0.0.0 in 1 hops
13:35:52: RIP: received v2 update from 10.4.1.1 on Serial0
13:35:52: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:35:52: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:35:52: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:35:52: 10.5.1.5/32 via 10.4.1.3 in 3 hops
13:36:05: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:36:05: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:07: RIP: sending v2 flash update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:36:07: RIP: build flash update entries
13:36:07: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:07: RIP: sending v2 flash update to 224.0.0.9 via Serial0 (10.4.1.4)
13:36:07: RIP: build flash update entries
13:36:07: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:07: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:36:07: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:09: RIP: received v2 update from 10.4.1.1 on Serial0
13:36:09: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:14: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:36:14: RIP: build update entries
13:36:14: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:36:14: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:36:14: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:14: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:14: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:36:14: RIP: build update entries
13:36:14: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:36:14: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:36:14: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:14: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:14: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:36:14: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:14: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:36:14: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:36:14: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:36:14: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:36:14: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:17: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:36:17: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:36:17: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:21: RIP: received v2 update from 10.4.1.1 on Serial0
13:36:21: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:36:21: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:36:21: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:36:21: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:40: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:36:40: RIP: build update entries
13:36:40: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:36:40: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:36:40: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:40: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:40: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:36:40: RIP: build update entries
13:36:40: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:36:40: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:36:40: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:40: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:36:40: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:36:40: 10.5.1.5/32 via 0.0.0.0, metric 16, tag 0
13:36:42: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:36:42: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:36:42: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:36:42: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:36:42: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:44: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:36:44: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:36:44: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:36:48: RIP: received v2 update from 10.4.1.1 on Serial0
13:36:48: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:36:48: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:36:48: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:36:48: 10.5.1.5/32 via 0.0.0.0 in 16 hops (inaccessible)
13:37:09: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:37:09: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:37:10: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:37:10: RIP: build update entries
13:37:10: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:37:10: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:37:10: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:10: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:37:10: RIP: build update entries
13:37:10: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:37:10: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:37:10: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:10: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:10: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:37:11: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:37:11: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:37:11: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:37:11: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:37:17: RIP: received v2 update from 10.4.1.1 on Serial0
13:37:17: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:37:17: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:37:17: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:37:36: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:37:36: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:37:37: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:37:37: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:37:37: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:37:37: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:37:37: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:37:37: RIP: build update entries
13:37:37: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:37:37: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:37:37: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:37: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:37:37: RIP: build update entries
13:37:37: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:37:37: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:37:37: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:37: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:37:37: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:37:45: RIP: received v2 update from 10.4.1.1 on Serial0
13:37:45: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:37:45: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:37:45: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:38:04: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:38:04: RIP: build update entries
13:38:04: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:38:04: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:38:04: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:04: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:38:04: RIP: build update entries
13:38:04: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:38:04: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:38:04: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:04: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:04: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:38:04: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:38:04: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:38:04: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:38:04: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:38:05: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:38:05: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:38:12: RIP: received v2 update from 10.4.1.1 on Serial0
13:38:12: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:38:12: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:38:12: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:38:32: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:38:32: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:38:33: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:38:33: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:38:33: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:38:33: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:38:34: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:38:34: RIP: build update entries
13:38:34: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:38:34: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:38:34: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:34: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:38:34: RIP: build update entries
13:38:34: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:38:34: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:38:34: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:34: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:38:34: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:38:41: RIP: received v2 update from 10.4.1.1 on Serial0
13:38:41: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:38:41: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:38:41: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:38:58: RIP: received v2 update from 10.3.1.7 on Ethernet0
13:38:58: 10.5.1.0/24 via 0.0.0.0 in 1 hops
13:39:01: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.3.1.4)
13:39:01: RIP: build update entries
13:39:01: 10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
13:39:01: 10.2.1.0/24 via 0.0.0.0, metric 3, tag 0
13:39:01: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:39:01: RIP: sending v2 update to 224.0.0.9 via Serial0 (10.4.1.4)
13:39:01: RIP: build update entries
13:39:01: 10.1.1.0/24 via 10.4.1.1, metric 2, tag 0
13:39:01: 10.2.1.0/24 via 10.4.1.2, metric 3, tag 0
13:39:01: 10.3.1.0/24 via 0.0.0.0, metric 1, tag 0
13:39:01: 10.4.1.0/24 via 0.0.0.0, metric 1, tag 0
13:39:01: 10.5.1.0/24 via 0.0.0.0, metric 2, tag 0
13:39:03: RIP: received v2 update from 10.3.1.3 on Ethernet0
13:39:03: 10.1.1.0/24 via 0.0.0.0 in 2 hops
13:39:03: 10.2.1.0/24 via 0.0.0.0 in 3 hops
13:39:03: 10.4.1.0/24 via 0.0.0.0 in 1 hops
13:39:09: RIP: received v2 update from 10.4.1.1 on Serial0
13:39:09: 10.1.1.0/24 via 0.0.0.0 in 1 hops
13:39:09: 10.2.1.0/24 via 10.4.1.2 in 2 hops
13:39:09: 10.4.1.0/24 via 0.0.0.0 in 1 hops

Tom4498 · Joined: 05 Oct 2004 Posts: 276 Location: America/New_York

I added the following in config mode....
key chain ripkey
key 1
key-string cisco

I added to each interface....
ip rip authentication key-chain ripkey
ip rip authentication mode md5

I only turned rip authentication on R1 and wanted to see what the rejection would look like with debugging.

R1#debug ip rip
RIP protocol debugging is on
13:47:49: RIP: ignored v2 packet from 10.4.1.3 (invalid authentication)
13:47:52: RIP: ignored v2 packet from 10.4.1.4 (invalid authentication)
13:47:52: RIP: ignored v2 packet from 10.4.1.2 (invalid authentication)
13:48:04: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.1.1.1)

When I added authentication to all routers I was able to restore my routing table.