Lab 11

Title: RIP Configuration

Topology Diagram

Learning Objective

Upon completion of this lab, you will be able to:

 Cable a network according to the Topology Diagram.

 Erase the startup configuration and reload a router to the default state.
 Perform basic configuration tasks on a router.
 Configure and activate interfaces.
 Configure RIP routing on all routers.
 Verify RIP routing using show and debug commands.
 Reconfigure the network to make it contiguous.
 Observe automatic summarization at boundary router.
 Gather information about RIP processing using the debug ip rip command.
 Configure a static default route.
 Propagate default routes to RIP neighbors.
 Document the RIP configuration.

14-EE-10:Ahmed Hameed
 Scenario A: Running RIPv1 on Class full Networks

Topology Diagram

Step 1

Cable a network that is similar to the one in the Topology Diagram.

Use any current router in this lab as long as it has the required interfaces shown in the topology.

14-EE-10:Ahmed Hameed
Step 2

Clear any existing configurations on the routers

Task 2

Perform Basic Router Configurations.

Perform basic configuration of the R1, R2, and R3 routers according to the following guidelines:

 Configure the router hostname.

 Disable DNS lookup.
 Configure an EXEC mode password.
 Configure a message-of-the-day banner.
 Configure a password for console connections.
 Configure a password for VTY connections.

For R1

14-EE-10:Ahmed Hameed
Similarly with R2 and R3

Task 3

Configure and Activate Serial and Ethernet Addresses.

Step 1

Configure interfaces on R1, R2, and R3.

Configure the interfaces on the R1, R2, and R3 routers with the IP addresses from the table under the
Topology Diagram.

For R1

At fa0/0 ip address 192.168.1.1 255.255.255.0

At serial 0/0 ip address 192.168.2.1 255.255.255.0

14-EE-10:Ahmed Hameed
Similarly configurations with R2,R3

For R2

At Fa0/0 ip address 192.168.3.1 255.255.255.0

At S0/0/0 192.168.2.2 255.255.255.0

At S0/0/1 192.168.4.2 255.255.255.0

For R3

At Fa0/0 192.168.5.1 255.255.255.0

At S0/0/1 192.168.4.1 255.255.255.0

Step 2

Verify IP addressing and interfaces.

Use the show ip interface brief command to verify that the IP addressing is correct and that the interfaces
are active.

For R1

For R2

14-EE-10:Ahmed Hameed
For R3

Step 3

Configure Ethernet interfaces of PC1, PC2, and PC3.

14-EE-10:Ahmed Hameed
Step 4

Test the PC configuration by pinging the default gateway from the PC.

Task 4

Configure RIP.

Step 1

Enable dynamic routing.

To enable a dynamic routing protocol, enter global configuration mode and use the router command.

To enable RIP, enter the command router rip in global configuration mode.

Step 2

Enter classful network addresses.

14-EE-10:Ahmed Hameed
Enter the classful network address for each directly connected network, using the network command

The network command:

 Enables RIP on all interfaces that belong to this network. These interfaces will now both send
and receive RIP updates.
 Advertises this network in RIP routing updates sent to other routers every 30 seconds.

When you are finished with the RIP configuration, return to privileged EXEC mode and save the current
configuration to NVRAM.

Step 3

Configure RIP on the R2 router using the router rip and network commands.

When you are finished with the RIP configuration, return to privileged EXEC mode and save the current
configuration to NVRAM.

Step 4

Configure RIP on the R3 router using the router rip and network commands.

14-EE-10:Ahmed Hameed
When you are finished with the RIP configuration, return to privileged EXEC mode and save the current
configuration to NVRAM.

Task 5

Verify RIP Routing

Step 1

Use the show ip route command to verify that each router has all of the networks in the topology entered
in the routing table. Routes learned through RIP are coded with an R in the routing table

For R1

For R2

For R3

14-EE-10:Ahmed Hameed
Step 2

Use the show ip protocols command to view information about the routing processes.

The show ip protocols command can be used to view information about the routing processes that are
occurring on the router. This output can be used to verify most RIP parameters to confirm that:

 RIP routing is configured

 The correct interfaces send and receive RIP updates
 The router advertises the correct networks
 RIP neighbors are sending updates

For R1

R1 is indeed configured with RIP. R1 is sending and receiving RIP updates on FastEthernet0/0 and
Serial0/0/0. R1 is advertising networks 192.168.1.0 and 192.168.2.0. R1 has one routing information
source. R2 is sending R1 updates

Step 3

Use the debug IP rip command to view the RIP messages being sent and received.

14-EE-10:Ahmed Hameed
Rip updates are sent every 30 seconds so you may have to wait for debug information to be displayed.

The debug output shows that R1 receives an update from R2. Notice how this update includes all the
networks that R1 does not already have in its routing table. Because the FastEthernet0/0 interface belongs
to the 192.168.1.0 network configured under RIP, R1 builds an update to send out that interface. The
update includes all networks known to R1 except the network of the interface. Finally, R1 builds an
update to send to R2. Because of split horizon, R1 only includes the 192.168.1.0 network in the update.

Step 4

Discontinue the debug output with the undebug all command.

Outputs Of Running Configuration

Scenario B:

14-EE-10:Ahmed Hameed
 Running RIPv1 with Subnets and Between Classful Networks

Topology Diagram

Addressing Table:

Task 01 : Configure and Activate Serial and Ethernet Addresses.

Step 1 Configure interfaces on R1, R2, and R3.

Step 2

14-EE-10:Ahmed Hameed
 Configure Ethernet interfaces of PC1, PC2, and PC3.

Task 2

Configure RIP

Step 1

Configure RIP routing on R1 as shown below.

Only a single network statement is needed for R1. This statement includes both interfaces on different
subnets of the 172.30.0.0 major network

Step 2

Configure R1 to stop sending updates out the FastEthernet0/0 interface.

The passive-interface fast Ethernet 0/0 command is used to disable sending RIPv1 updates out that
interface. When you are finished with the RIP configuration, return to privileged EXEC mode and
save the current configuration to NVRAM.

Step 3

Configure RIP routing on R2 as shown below

14-EE-10:Ahmed Hameed
 Again notice that only a single network statement is needed for the two subnets of 172.30.0.0. This
statement includes both interfaces, on different subnets, of the 172.30.0.0 major network. The
network for the WAN link between R2 and R3 is also configured. When you are finished with the
RIP configuration, return to privileged EXEC mode and save the current configuration to NVRAM.

Step 4

Configure RIP routing on R3 as shown below.

When you are finished with the RIP configuration, return to privileged EXEC mode and save the
current configuration to NVRAM.

Task 3

Verify RIP Routing

For R1

For R2

14-EE-10:Ahmed Hameed
For R3

Step 2

Verify that all necessary interfaces are active.

First make sure that all necessary interfaces are active with show IP interface brief. Then use show IP
protocols to verify the RIP configuration

14-EE-10:Ahmed Hameed
Step 3

View the RIP messages being sent and received. To view the RIP messages being sent and received
use the debug ip rip command. Notice that RIP updates are not sent out of the fa0/0 interface because
of the passive-interface fast Ethernet0/0 command.

Step 4

Discontinue the debug output with the undebug all command.

Outputs of Running Configuration:

14-EE-10:Ahmed Hameed
Scenario C

Running RIPv1 on a Stub Network

Topology Diagram

14-EE-10:Ahmed Hameed
 Background

In this scenario we will modify Scenario B to only run RIP between R1 and R2. Scenario C is a
typical configuration for most companies connecting a stub network to a central headquarters router
or an ISP. Typically, a company runs a dynamic routing protocol (RIPv1 in our case) within the local
network but finds it unnecessary to run a dynamic routing protocol between the company’s gateway
router and the ISP. For example, colleges with multiple campuses often run a dynamic routing
protocol between campuses but use default routing to the ISP for access to the Internet. In some
cases, remote campuses may even use default routing to the main campus, choosing to use dynamic
routing only locally. To keep our example simple, for Scenario C, we left the addressing intact from
Scenario B. Let’s assume that R3 is the ISP for our Company XYZ, which consists of the R1 and R2
routers using the 172.30.0.0/16 major network, sub netted with a /24 mask. Company XYZ is a stub
network, meaning that there is only one way in and one way out of the 172.30.0.0/16 network—in via
R2 (the gateway router) and out via R3 (the ISP). It doesn’t make sense for R2 to send R3 RIP
updates for the 172.30.0.0 network every 30 seconds, because R3 has no other way to get to
172.30.0.0 except through R2. It makes more sense for R3 to have a static route configured for the
172.30.0.0/16 network pointing to R2. How about traffic from Company XYZ toward the Internet? It
makes no sense for R3 to send over 120,000 summarized Internet routes to R2. All R2 needs to know
is that if a packet is not destined for a host on the 172.30.0.0 network, then it should send the packet
to the ISP, R3. This is the same for all other Company XYZ routers (only R1 in our case). They
should send all traffic not destined for the 172.30.0.0 network to R2. R2 would then forward the
traffic to R3

Task 1

Make Changes between Scenario B and Scenario C.

Step 1

Remove network 192.168.4.0 from the RIP configuration for R2.

Remove network 192.168.4.0 from the RIP configuration for R2, because no updates will be sent
between R2 and R3 and we don’t want to advertise the 192.168.4.0 network to R1.

Step 2

Completely remove RIP routing from R3.

14-EE-10:Ahmed Hameed
 Task 2

Configure the Static Route on R3 for the 172.30.0.0/16 network.

Because R3 and R2 are not exchanging RIP updates, we need to configure a static route on R3 for the
172.30.0.0/16 network. This will send all 172.30.0.0/16 traffic to R2

Task 3

Configure a Default Static Route on R2.

Step 1

Configure R2 to send default traffic to R3.

Configure a default static route on R2 that will send all default traffic packets with destination IP
addresses that do not match a specific route in the routing table to R3.

Step 2

Configure R2 to send default static route information to R1.

The default-information originate command is used to configure R2 to include the default static route
with its RIP updates. Configure this command on R2 so that the default static route information is
sent to R1.

Task 4

Verify RIP Routing.

Step 1

Use the show ip route command to view the routing table on R2 and R1

14-EE-10:Ahmed Hameed
 Step 2

View the RIP updates that are sent and received on R1 with the debug ip rip command

Step 3

Discontinue the debug output with the undebug all command

Step 4

Use the show ip route command to view the routing table on R3

Task 5

Document the Router Configurations

On each router, capture the following command output to a text file and save for future reference:

 Running configuration
 Routing table
 Interface summarization
 Output from show ip protocols

14-EE-10:Ahmed Hameed
Output

Routing table

R1

R2

14-EE-10:Ahmed Hameed
R3

Interface Summarization

For R1

14-EE-10:Ahmed Hameed
For R2 For R3

Output From Show IP Protocols

For R1

For R2

14-EE-10:Ahmed Hameed
Task 06

Erase the configurations and reload the routers. Disconnect and store the cabling. For PC hosts that
are normally connected to other networks (such as the school LAN or to the Internet), reconnect the
appropriate cabling and restore the TCP/IP settings

Similarly with R2

Scenario D

Learning Objectives

Upon completion of this lab, you will be able to

 Cable a network according to the Topology Diagra

 Configure RIPv2 on all routers.
 Examine the automatic summarization of routes. Examine routing updates with debug ip rip.
 Disable automatic summarization.
 Document the RIPv2 configuration.
 Examine the automatic summarization of routes.

Topology Diagram:

14-EE-10:Ahmed Hameed
Addressing table

Scenario:

The network shown in the Topology Diagram contains a discontiguous network, 172.30.0.0. This
network has been subnetted using VLSM. The 172.30.0.0 subnets are physically and logically divided
by at least one other classful or major network, in this case the two serial networks
209.165.200.228/30 and 209.165.200.232/30. This can be an issue when the routing protocol used
does not include enough information to distinguish the individual subnets. RIPv2 is a classless
routing protocol that can be used to provide subnet mask information in the routing updates. This will
allow VLSM subnet information to be propagated throughout the network.

Task 1

14-EE-10:Ahmed Hameed
 Cable, Erase, and Reload the Routers

Step 1

Cable a network.

Cable a network that is similar to the one in the Topology Diagram.

Step 2

Clear the configuration on each router.

Clear the configuration on each of routers using the erase startup-config command and then reload the
routers. Answer no if asked to save changes.

Task 2

Load Routers with the Supplied Scripts.

14-EE-10:Ahmed Hameed
Step 1

Load the given script onto R1.

Similar with R2 and R3 following changings will take place

For R2

At Fa0 ip address 10.1.0.1 255.255.0.0

At Serial 0/0/0 ip address 209.165.200.229 255.255.255.252

At serial 0/0/1 ip address 209.165.200.233 255.255.255.252

At router rip: passive-interface fa0/0 #network 10.0.0.0 #network 209.165.200.0

14-EE-10:Ahmed Hameed
 For R3

At Fa0/0 ip address 172.30.100.1 255.255.255.0

At Serial 0/0/1 IP address 209.165.200.234 255.255.255.252

AT #interface Loopback 0: IP address 172.30.110.1 255.255.0

At #interface Loopback1: IP address 172.30.200.17 255.255.255.240

At #interface Loopback2: IP address 172.30.200.33 255.255.255.240

At router rip: passive-interface fa0/0 #network 172.30.0.0 #network 209.165.200.0

Task 3

Examine the Current Status of the Network.

Step 1

Verify that both serial links are up.

The two serial links can quickly be verified using the show ip interface brief command on R2.

Step 2

Check the connectivity from R2 to the hosts on the R1 and R3 LANs.

For the 1841 router, you will need to disable IP CEF to obtain the correct output from the ping
command.

From the R2 router, how many ICMP messages are successful when pinging PC1?

From the R2 router, how many ICMP messages are successful when pinging PC4?

14-EE-10:Ahmed Hameed
Step 3

Check the connectivity between the PCs.

From the PC1, is it possible to ping PC2?

 What is the success rate?

 From the PC1, is it possible to ping PC3?

 What is the success rate?

 From the PC1, is it possible to ping PC4?

 What is the success rate?

 From the PC4, is it possible to ping PC2?

 What is the success rate?

 From the PC4, is it possible to ping PC3

 What is the success rate?

14-EE-10:Ahmed Hameed
Step 4

View the routing table on R2.

Both the R1 and R3 are advertising routes to the 172.30.0.0/16 network; therefore, there are two entries
for this network in the R2 routing table. The R2 routing table only shows the major classful network
address of 172.30.0.0—it does not show any of the subnets for this network that are used on the LANs
attached to R1 and R3. Because the routing metric is the same for both entries, the router alternates the
routes that are used when forwarding packets that are destined for the 172.30.0.0/16 network.

Step 5

Examine the routing table on the R1 router.

Both R1 and R3 are configured with interfaces on a discontinuous network, 172.30.0.0. The 172.30.0.0
subnets are physically and logically divided by at least one other classful or major network—in this case,
the two serial networks 209.165.200.228/30 and 209.165.200.232/30. Classful routing protocols like
RIPv1 summarize networks at major network boundaries. Both R1 and R3 will be summarizing
172.30.0.0/24 subnets to 172.30.0.0/16. Because the route to 172.30.0.0/16 is directly connected, and
because R1 does not have any specific routes for the 172.30.0.0 subnets on R3, packets destined for the
R3 LANs will not be forwarded properly.

14-EE-10:Ahmed Hameed
Step 6 Examine the routing table on the R3 router.

R3 only shows its own subnets for 172.30.0.0 network: 172.30.100/24, 172.30.110/24, 172.30.200.16/28,
and 172.30.200.32/28. R3 does not have any routes for the 172.30.0.0 subnets on R1

Step 7

Examine the RIPv1 packets that are being received by R2.

Use the debug ip rip command to display RIP routing updates. R2 is receiving the route 172.30.0.0, with
1 hop, from both R1 and R3. Because these are equal cost metrics, both routes are added to the R2 routing
table. Because RIPv1 is a classful routing protocol, no subnet mask information is sent in the update

14-EE-10:Ahmed Hameed
R2 is sending only the routes for the 10.0.0.0 LAN and the two serial connections to R1 and R3. R1 and
R3 are not receiving any information about the 172.30.0.0 subnet routes.

Task 4

Config the RIP version 2

Step 1

Use the version 2 command to enable RIP version 2 on each of the routers.

RIPv2 messages include the subnet mask in a field in the routing updates. This allows subnets and their
masks to be included in the routing updates. However, by default RIPv2 summarizes networks at major
network boundaries, just like RIPv1, except that the subnet mask is included in the update

Step 2

Verify that RIPv2 is running on the routers.

The debug ip rip, show ip protocols, and show run commands can all be used to confirm that RIPv2 is
running.

14-EE-10:Ahmed Hameed
Task 5

Examine the Automatic Summarization of Routes.

The LANs connected to R1 and R3 are still composed of discontinuous networks. R2 still shows two
equal cost paths to the 172.30.0.0/16 network in the routing table. R2 still shows only the major
classful network address of 172.30.0.0 and does not show any of the subnets for this network.

For R1

For R2

For R3

14-EE-10:Ahmed Hameed
Use the output of the debug ip rip command to answer the following questions:

 What entries are included in the RIP updates sent out from R3?

 On R2, what routes are in the RIP updates that are received from R3?

R3 is not sending any of the 172.30.0.0 subnets—only the summarized route of 172.30.0.0/16,
including the subnet mask. This is why R2 and R1 are not seeing the 172.30.0.0 subnets on R3.

14-EE-10:Ahmed Hameed
Task 6

Disable Automatic Summarization.

The no auto-summary command is used to turn off automatic summarization in RIPv2. Disable auto
summarization on all routers. The routers will no longer summarize routes at major network boundaries.

For R1

Similarly with R2 and R3

Task 7

Examine the Routing Tables.

The LANs connected to R1 and R3 should now be included in all three routing tables.

For R1:

14-EE-10:Ahmed Hameed
For R2

For R3

Use the output of the debug IP rip command to answer the following questions

14-EE-10:Ahmed Hameed
Task 8

Verify Network Connectivity.

Step 1

Check connectivity between R2 router and PCs

14-EE-10:Ahmed Hameed
Step 2

Check the connectivity between the PCs

Task 9

Documentation

On each router, capture the following command output to a text (.txt) file and save for future reference.

Show running-config

14-EE-10:Ahmed Hameed
For R1:

For R2

14-EE-10:Ahmed Hameed
For R3

14-EE-10:Ahmed Hameed
Show IP route

R1

For R2

14-EE-10:Ahmed Hameed
For R3

show ip interface brief

For R2:

14-EE-10:Ahmed Hameed
Foe R3

show ip protocols: For R1

For R2

14-EE-10:Ahmed Hameed
For R3

Task 10

Clean Up

Erase the configurations and reload the routers. Disconnect and store the cabling. For PC hosts that are
normally connected to other network (such as the school LAN or to the Internet), reconnect the
appropriate cabling and restore the TCP/IP settings.

14-EE-10:Ahmed Hameed
14-EE-10:Ahmed Hameed