Configuring RIPv1 and RIPv2
There are two versions of RIP known as v1 and v2. The differences are major changes in how RIP advertises and populates the routing table. This lab will discuss and demonstrate the configuration and verification of RIPv1 and RIPv2.
Real World Application & Core Knowledge
After reading completing Lab 7-1 you should have an excellent foundation for understanding RIP. Now its time to build even further on that foundation. Technically Lab 7-1 was a RIPv1 lab. When you enable RIP, by default it uses version 1 unless you specify it to use Version 2. RIPv1 however has limitations that are just not feasible in today’s modern networks.
Such limitation of classful routing protocols were seen early in the evolutionary development of the internet as more and more networks became discontigious, such information about subnets needed to be advertised along with the networks to other routers to ensure IP connectivity.
There are a several new features that RIPv2 has that RIPv1 does not, first off being the ability to send subnet information in updates; VLSM. RIPv2 is a Classless routing protocol. RIPv2 also sends its updates to the Multicast address of 224.0.0.9 whereas v1 sent the updates to the broadcast address. RIPv2 also supports authentication now to prevent unwanted rouge network routers from being placed into the network causing chaos in the routing table. Route tagging is now a supported feature in RIP as of version two which will help in managing redistributed routes which will be discussed in Section 10.
If you’ve completed the previous lab then you’ll notice that with RIPv1, subnets are not advertised and this causes a problem. /24 subnets cannot be advertised out /30 subnetted links. So in this lab you’re going to use Version 2 to fix this issue. You’ll continue to build onto the previous labs logical topology which is shown below;
Familiarize yourself with the following new command(s);
| Command | Description |
|---|---|
| version 2 | This command is executed in rip router configuration mode to specify that the RIP process should operate at version 2. |
Lab Prerequisites
- If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start devices; R1, R2 and R3.
- Establish a console session with devices R1, R2 and R3 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.
Lab Objectives
- Configure R1, R2 and R3 to run RIP Version 2.
- Verify that all routes are propagating properly in the network from R1 to R2 and from R3 to R2 using show ip route. Verify IP connectivity using ping sourced from the 10.70.20.0/24 network to the 10.70.10.0/24 and 10.70.30.0/24 networks
Lab Instruction
Objective 1. – Configure R1, R2 and R3 to run RIP Version 2.
R1>enable R1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R1(config)#router rip R1(config-router)#version 2 R1(config-router)#end R1#
R2>enable R2#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R2(config)#router rip R2(config-router)#version 2 R2(config-router)#end R2#
R3>enable R3#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R3(config)#router rip R3(config-router)#version 2 R3(config-router)#end R3#
Objective 2. – Verify that all routes are propagating properly in the network from R1 to R2 and from R3 to R2 using show ip route. Verify IP connectivity using ping sourced from the 10.70.20.0/24 network to the 10.70.10.0/24 and 10.70.30.0/24 networks
R2#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 10.0.0.0/8 is variably subnetted, 7 subnets, 2 masks C 10.70.12.0/30 is directly connected, Serial0/0.221 C 10.70.23.0/30 is directly connected, Serial0/0.223 C 10.70.21.0/30 is directly connected, Serial0/1 R 10.70.30.0/24 [120/1] via 10.70.23.2, 00:00:04, Serial0/0.223 C 10.70.20.0/24 is directly connected, Loopback0 R 10.70.10.0/24 [120/1] via 10.70.21.1, 00:00:27, Serial0/1 [120/1] via 10.70.12.1, 00:00:21, Serial0/0.221 R 10.56.10.0/30 [120/1] via 10.70.21.1, 00:00:27, Serial0/1 [120/1] via 10.70.12.1, 00:00:21, Serial0/0.221 R2#ping 10.70.10.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.70.10.1, timeout is 2 seconds: Packet sent with a source address of 10.70.20.1 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 12/54/144 ms R2#ping 10.70.30.1 source lo0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.70.30.1, timeout is 2 seconds: Packet sent with a source address of 10.70.20.1 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 20/60/128 ms R2#
After viewing the routing table; you’ll notice that after Version 2 has been configured all the subnets are propagated properly and you can reach the subnets correctly from the given networks.
