Scribd
Upload
35 views9 pages

Ccna2 RIPv2Lab

The document outlines the configuration and operation of RIPv2 on three routers: SantaCruz1, SantaCruz2, and ISP, detailing their IP address assignments and RIPv2 settings. It explains the transition from RIPv1 to RIPv2, highlighting the benefits of classless routing protocols, and provides steps for testing connectivity and examining routing tables. Additionally, it introduces CIDR (Classless Inter-Domain Routing) and route aggregation, demonstrating how to summarize routes to optimize routing tables.

Uploaded by

hasan23105101093
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
35 views9 pages

Ccna2 RIPv2Lab

The document outlines the configuration and operation of RIPv2 on three routers: SantaCruz1, SantaCruz2, and ISP, detailing their IP address assignments and RIPv2 settings. It explains the transition from RIPv1 to RIPv2, highlighting the benefits of classless routing protocols, and provides steps for testing connectivity and examining routing tables. Additionally, it introduces CIDR (Classless Inter-Domain Routing) and route aggregation, demonstrating how to summarize routes to optimize routing tables.

Uploaded by

hasan23105101093
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Part 1: Running RIPv2

Basic Configuration

SantaCruz1
hostname SantaCruz1
interface ethernet 0
ip add 172.30.1.1 255.255.255.0
interface loopback 0
ip add 172.30.2.1 255.255.255.0
interface serial 0
ip add 192.168.4.26 255.255.255.252

SantaCruz2
hostname SantaCruz2
interface ethernet 0
ip add 172.30.100.1 255.255.255.0
interface loopback 0
ip add 172.30.110.1 255.255.255.0
interface serial 0
ip add 192.168.4.22 255.255.255.252

ISP
hostname ISP
interface ethernet 0
ip add 10.0.0.1 255.0.0.0
interface serial 0
ip add 192.168.4.25 255.255.255.252
interface serial 1
ip add 192.168.4.21 255.255.255.252
Step 1 –Configure RIPv2 with no auto-summary
On all three routers configure RIPv1 for all networks.

SantaCruz1
router rip
network 172.30.0.0
2.168.4.0
network 19 version 2
no auto-summary

SantaCruz2
router rip
network 172.30.0.0
2.168.4.0
network 19 version 2
no auto-summary

ISP
router rip
network 10.0.0.0
2.168.4.0
network 19 version 2
no auto-summary

version 2 – Change from RIPv1 to RIPv2, a classless routing protocol. Classless routing protocols
pass the subnet mask with the routing update and also allow use of VLSM and CIDR.

no auto-summary – Do not summarize at classful or major network boundaries.

RIPv2 message format

0 1 2 33
01234567890123456789012345678901
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| command (1) | version (1) | must be zero (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family Identifier (2) | Route Tag (2) |
+-------------------------------+-------------------------------+
| IP Address (4) |
+---------------------------------------------------------------+
| Subnet Mask (4) |
+---------------------------------------------------------------+
| Next Hop (4) |
+---------------------------------------------------------------+
| Metric (4) |
+---------------------------------------------------------------+

Step 2 –Testing connectivity again


SantaCruz1
SantaCruz1# ping 10.0.0.1
!!!!! - Successful
SantaCruz1# ping 172.30.100.1
!!!!! - Successful
SantaCruz1# ping 172.30.110.1
!!!!! - Successful

SantaCruz2
SantaCruz2# ping 10.0.0.1
!!!!! - Successful
SantaCruz2# ping 172.30.1.1
!!!!! - Successful
SantaCruz2# ping 172.30.2.1
!!!!! - Successful

ISP
ISP# ping 172.30.1.1
!!!!! - Successful
ISP# ping 172.30.2.1
!!!!! - Successful
ISP# ping 172.30.100.1
!!!!! - Successful
ISP# ping 172.30.110.1
!!!!! - Successful
Step 3 – Examine the new routing tables
Notice the subnets!

SantaCruz1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<text omitted>

Gateway of last resort is not set

172.30.0.0/24 is subnetted, 4 subnets


C 172.30.2.0 is directly connected, Loopback0
C 172.30.1.0 is directly connected, Ethernet0
R 172.30.100.0 [120/2] via 192.168.4.25, 00:00:16, Serial0
R 172.30.110.0 [120/2] via 192.168.4.25, 00:00:16, Serial0
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
R 192.168.4.20 [120/1] via 192.168.4.25, 00:00:17, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.25, 00:00:17, Serial0
SantaCruz1#

SantaCruz2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<text omitted>

Gateway of last resort is not set

172.30.0.0/24 is subnetted, 4 subnets


R 172.30.2.0 [120/2] via 192.168.4.21, 00:00:16, Serial0
R 172.30.1.0 [120/2] via 192.168.4.21, 00:00:16, Serial0
C 172.30.100.0 is directly connected, Ethernet0
C 172.30.110.0 is directly connected, Loopback0
192.168.4.0/30 is subnetted, 2 subnets
R 192.168.4.24 [120/1] via 192.168.4.21, 00:00:16, Serial0
C 192.168.4.20 is directly connected, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:16, Serial0
SantaCruz2#
ISP#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<text omitted>

Gateway of last resort is not set

172.30.0.0/24 is subnetted, 4 subnets


R 172.30.2.0 [120/1] via 192.168.4.26, 00:00:28, Serial0
R 172.30.1.0 [120/1] via 192.168.4.26, 00:00:28, Serial0
R 172.30.100.0 [120/1] via 192.168.4.22, 00:00:02, Serial1
R 172.30.110.0 [120/1] via 192.168.4.22, 00:00:02, Serial1
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
C 192.168.4.20 is directly connected, Serial1
C 10.0.0.0/8 is directly connected, Ethernet0
ISP#

Step 4 – View the RIPv2 routing updates


Notice the subnet mask sent and received in the RIPv2 multicast updates!

ISP#debug ip rip
RIP protocol debugging is on

ISP#01:23:34: RIP: received v2 update from 192.168.4.22 on Serial1


01:23:34: 172.30.100.0/24 -> 0.0.0.0 in 1 hops
01:23:34: 172.30.110.0/24 -> 0.0.0.0 in 1 hops
ISP#
01:23:38: RIP: received v2 update from 192.168.4.26 on Serial0
01:23:38: 172.30.2.0/24 -> 0.0.0.0 in 1 hops
01:23:38: 172.30.1.0/24 -> 0.0.0.0 in 1 hops
ISP#

01:24:31: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.0.1)


01:24:31: 172.30.2.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 172.30.1.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 172.30.100.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 172.30.110.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 192.168.4.24/30 -> 0.0.0.0, metric 1, tag 0
01:24:31: 192.168.4.20/30 -> 0.0.0.0, metric 1, tag 0
01:24:31: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.4.25)
01:24:31: 192.168.4.20/30 -> 0.0.0.0, metric 1, tag 0
01:24:31: 172.30.100.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 172.30.110.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 10.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
01:24:31: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.4.21)
01:24:31: 192.168.4.24/30 -> 0.0.0.0, metric 1, tag 0
01:24:31: 172.30.2.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 172.30.1.0/24 -> 0.0.0.0, metric 2, tag 0
01:24:31: 10.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
ISP#un all
All possible debugging has been turned off
ISP#
Part 2: RIPv2 with VLSM and CIDR

Step 5 – A quick introduction to CIDR (Classless Interdomain Routing)


From Pacific Bell’s site: http://public.pacbell.net/dedicated/cidr.html

“CIDR is a new addressing scheme for the Internet which allows for more efficient allocation of IP
addresses than the old Class A, B, and C address scheme.”

“Why Do We Need CIDR? With a new networks being connected to the Internet every 30 minutes
the Internet was faced with two critical problems:

1. Running out of IP addresses


2. Running out of capacity in the global routing tables

“Classless Inter-Domain Routing (CIDR) is a replacement for the old process of assigning Class A,
B and C addresses with a generalized network "prefix". Instead of being limited to network
identifiers (or "prefixes") of 8, 16 or 24 bits, CIDR currently uses prefixes anywhere from 13 to 27
bits. Thus, blocks of addresses can be assigned to networks as small as 32 hosts or to those with
over 500,000 hosts. This allows for address assignments that much more closely fit an
organization's specific needs.”

“A CIDR address includes the standard 32-bit IP address and also information on how many bits
are used for the network prefix. For example, in the CIDR address 206.13.01.48/25, the "/25"
indicates the first 25 bits are used to identify the unique network leaving the remaining bits to
identify the specific host.”
Route Aggregation (Summarization)

CIDR will be discussed more in later CCNA and CCNP semesters, but let’s see a simple example of
how CIDR can be used.

The CIDR addressing scheme also enables "route aggregation" in which a single high-level route
entry can represent many lower-level routes in the global routing tables. This allow routing tables
have fewer entries in them, as a single entry may represent (summarize) many networks, just like a
classful address can represent many subnets.

In ISP’s network there are several 207.0.0.0/16 networks. (Remember, the network address has
nothing to do with the network prefix or mask. We need both the address and the mask to
determine the network address and host addresses of the network.)

Let’s add the following (bolded) commands to the ISP router:

router rip
version 2 redistribute static
network 10.0.0.0
network 192.168.4.0
no auto-summary

ip route 207.0.0.0 255.0.0.0 null0

We have created a static route to a summary using a /8 mask to summarize all of the 207.0.0.0/16
networks. Notice that we will be advertising a /8 mask with a network address beginning with
“207,” which is normally a /24 mask in the classful world.

The redistribute static command, redistributes or propagates this static route using RIP updates to
other RIP routers.

Let’s look at some routing tables!

ISP#show ip route

172.30.0.0/24 is subnetted, 4 subnets


R 172.30.2.0 [120/1] via 192.168.4.26, 00:00:23, Serial0
R 172.30.1.0 [120/1] via 192.168.4.26, 00:00:23, Serial0
R 172.30.100.0 [120/1] via 192.168.4.22, 00:00:26, Serial1
R 172.30.110.0 [120/1] via 192.168.4.22, 00:00:26, Serial1
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
C 192.168.4.20 is directly connected, Serial1
C 10.0.0.0/8 is directly connected, Ethernet0
S 207.0.0.0/8 is directly connected, Null0
ISP#

SantaCruz1#show ip route

172.30.0.0/24 is subnetted, 4 subnets


C 172.30.2.0 is directly connected, Loopback0
C 172.30.1.0 is directly connected, Ethernet0
R 172.30.100.0 [120/2] via 192.168.4.25, 00:00:24, Serial0
R 172.30.110.0 [120/2] via 192.168.4.25, 00:00:24, Serial0
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
R 192.168.4.20 [120/1] via 192.168.4.25, 00:00:24, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.25, 00:00:24, Serial0
R 207.0.0.0/8 [120/1] via 192.168.4.25, 00:00:24, Serial0
SantaCruz1#

SantaCruz2#show ip route

172.30.0.0/24 is subnetted, 4 subnets


R 172.30.2.0 [120/2] via 192.168.4.21, 00:00:19, Serial0
R 172.30.1.0 [120/2] via 192.168.4.21, 00:00:19, Serial0
C 172.30.100.0 is directly connected, Ethernet0
C 172.30.110.0 is directly connected, Loopback0
192.168.4.0/30 is subnetted, 2 subnets
R 192.168.4.24 [120/1] via 192.168.4.21, 00:00:19, Serial0
C 192.168.4.20 is directly connected, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:19, Serial0
R 207.0.0.0/8 [120/1] via 192.168.4.21, 00:00:19, Serial0
SantaCruz2#

NOTE: Propagating a “supernet”

If we were running the classful routing protocol RIPv1, RIP would not propagate a 207.0.0.0/8
network because the /8 is fewer bits than the classful mask of /24 for a “207” network. It is only
because we are running the classless routing protocol, RIPv2 that this route is propagated
(redistributed via RIP).

207.0.0.0/8 is also known as a supernet. A supernet is the aggregation (summarization) of IP


network addresses advertised as a single classless network address. The 207.0.0.0/8 network
address is the supernet or summarization of 207.0.0.0/16, 207.1.0.0/16, 207.2.0.0/16, etc.

Step 6 – A quick introduction to VLSM (Variable Length Subnet Masking)

Notice that Santa Cruz2 now has two additional subnets, but they have a /28 mask that is different
the other /24 subnets.

VLSM allows us to have different size subnets in our network to accommodate subnets that need
more or less hosts. VLSM is nothing more than taking a subnet and subnetting it again!

For example, let’s use the 172.30.200.0/24 subnet where the last 8 bits are usually for the hosts.
Now take those last eight bits and use the first four for subnet and the last four for hosts. This
gives us a 255.255.255.240 mask or /28.

172.30.200.0 255.255.255.240

Network First Host Last Host Broadcast


172.30.200.0/28 172.30.200.1 172.30.200.14 172.30.200.15
172.30.200.16/28 172.30.200.17 172.30.200.30 172.30.200.31
172.30.200.32/28 172.30.200.33 172.30.200.46 172.30.200.47
172.30.200.48/28 172.30.200.49 172.30.200.62 172.30.200.63
172.30.200.64/28 172.30.200.65 172.30.200.78 172.30.200.79
172.30.200.80/28 172.30.200.81 172.30.200.94 172.30.200.95
172.30.200.96/28 172.30.200.97 172.30.200.110 172.30.200.111
172.30.200.112/28 172.30.200.113 172.30.200.126 172.30.200.127
172.30.200.128/28 172.30.200.129 172.30.200.142 172.30.200.143
172.30.200.144/28 172.30.200.145 172.30.200.158 172.30.200.159
172.30.200.160/28 172.30.200.161 172.30.200.174 172.30.200.175
172.30.200.176/28 172.30.200.177 172.30.200.190 172.30.200.191
172.30.200.192/28 172.30.200.193 172.30.200.206 172.30.200.207
172.30.200.208/28 172.30.200.209 172.30.200.222 172.30.200.223
172.30.200.224/28 172.30.200.225 172.30.200.238 172.30.200.239
172.30.200.240/28 172.30.200.241 172.30.200.254 172.30.200.255

This means we no longer can use 172.30.200.0/24 host addresses, but we can summarize all of
these subnets as 172.30.300.0/24.

Add the loopback interface addresses (in bold) on SantaCruz2 router:


interface Loopback0
ip address 172.30.110.1 255.255.255.0
!
interface Loopback1
ip address 172.30.200.17 255.255.255.240
!
interface Loopback2
ip address 172.30.200.33 255.255.255.240
!
interface Ethernet0
ip address 172.30.100.1 255.255.255.0
!
interface Serial0
ip address 192.168.4.22 255.255.255.252

Now let’s look at the routing tables:


SantaCruz2#show ip route

172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks


C 172.30.200.32/28 is directly connected, Loopback2
C 172.30.200.16/28 is directly connected, Loopback1
R 172.30.2.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0
R 172.30.1.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0
C 172.30.100.0/24 is directly connected, Ethernet0
C 172.30.110.0/24 is directly connected, Loopback0
192.168.4.0/30 is subnetted, 2 subnets
R 192.168.4.24 [120/1] via 192.168.4.21, 00:00:21, Serial0
C 192.168.4.20 is directly connected, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0
R 207.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0

ISP#show ip route

172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks


R 172.30.200.32/28 [120/1] via 192.168.4.22, 00:00:21, Serial1
R 172.30.200.16/28 [120/1] via 192.168.4.22, 00:00:21, Serial1
R 172.30.2.0/24 [120/1] via 192.168.4.26, 00:00:07, Serial0
R 172.30.1.0/24 [120/1] via 192.168.4.26, 00:00:07, Serial0
R 172.30.100.0/24 [120/1] via 192.168.4.22, 00:00:21, Serial1
R 172.30.110.0/24 [120/1] via 192.168.4.22, 00:00:21, Serial1
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
C 192.168.4.20 is directly connected, Serial1
C 10.0.0.0/8 is directly connected, Ethernet0
S 207.0.0.0/8 is directly connected, Null0

SantaCruz1#show ip route

172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks


R 172.30.200.32/28 [120/2] via 192.168.4.25, 00:00:17, Serial0
R 172.30.200.16/28 [120/2] via 192.168.4.25, 00:00:17, Serial0
C 172.30.2.0/24 is directly connected, Loopback0
C 172.30.1.0/24 is directly connected, Ethernet0
R 172.30.100.0/24 [120/2] via 192.168.4.25, 00:00:17, Serial0
R 172.30.110.0/24 [120/2] via 192.168.4.25, 00:00:17, Serial0
192.168.4.0/30 is subnetted, 2 subnets
C 192.168.4.24 is directly connected, Serial0
R 192.168.4.20 [120/1] via 192.168.4.25, 00:00:17, Serial0
R 10.0.0.0/8 [120/1] via 192.168.4.25, 00:00:17, Serial0
R 207.0.0.0/8 [120/1] via 192.168.4.25, 00:00:18, Serial0

Routing Table Notes:


• Notice that the 172.30.0.0/16 network shows that the route “is variably subnetted, with 6
subnets, 2 masks.”
• Notice that the parent network, 172.30.0.0 includes the classful mask of “/16,” instead of the
subnetted mask (which would be the case of this network was not variably subnetted).
• Jog the memory: Remember that this mask is used to determine whether or not to look at the
child routes. If the destination ip address matches the parent network and mask, it will
then look at the children routes for a longest-bit-match. Also remember that depending on
whether you are using classful routing behavior (no ip classless) or classless routing
behavior (ip classless), this will determine if a supernet or default route is used if there is
match with the parent but none of the child routes.
• Notice that the subnet mask is included with the “child route” when the network is variably
subnetted, “172.30.200.16/28,” “172.30.100.0/24,” etc.

You might also like