CSC 335 Data Communications and Networking
Understanding Routing Information Protocol
Name: _________________________________________________________
Date: __________________________________________________________
1. Goal
This lab helps you gain a better understanding of how to configure and troubleshoot RIP version 2. In this lab, we will configure a basic lab topology, enable RIPv2 on the routers and configure them to advertise their networks. We will also learn to use Cisco IOS show and debug commands to verify and troubleshoot our lab.
Please answer all questions in red and attach required screenshots to this lab report and then submit it to D2L.
2. Routing Information Protocol (RIP)
RIP is one of the oldest distance-vector routing protocols, which uses the hop count as a routing metric. RIP avoids routing loops by employing a limit on the number of hops permitted in a path from the source to a destination. The maximum number of hops permitted for RIP is 15. A hop count of 16 is considered an infinite distance, in other words, the route is considered unreachable. Despite this limitation, RIP works great for basic route communications between devices.
How RIP works? With RIP, a router sends its full routing table to all other connected routers every 30 seconds. Triggered updates can also occur if a router goes down before the 30-second timer has expired.
What is different in RIP version 2? RIPv2 boasts the following enhancements:
· Support for variable length subnet masks (VLSM) (Because of this, RIP doesn't assume that all networks are classful.)
· Multicast routing updates
· Authentication with an encrypted password for routing updates.
3. Lab Procedures
3.1 Topology
Step 1: Create three routers, three switches, and two PCs.
Step 2: Change the display and host name according to the following figure.
3.2 making the connection
Step 3: Use copper straight-Through to connect:
· PC-1 FastEthernet0 to SW1 GigabitEthernet 0/2
· SW1 GigabitEthernet 0/1 to R1 GigabitEthernet 0/0
· PC-2 FastEthernet0 to SW3 GigabitEthernet 0/2
· SW3 GigabitEtherent 0/1 to R3 GigabitEthernet 0/1
· R3 GigabitEthernet 0/0 to SW2 GigabitEthernet 0/2
· SW2 GigabitEthernet 0/1 to R2 GigabitEthernet 0/0
Why using Straight-Through cable?
Using Straight through cable because it connect computers and other end-user devices so here it connects computer with the switches.it can also be used to directly connect like devices two hubs or two switches. It is most often used to connect two devices of the same type too.
Step 4: Use Serial DCE to connect serial ports
Step 4.1: Create Serial ports
Click the router, for example R2. Click Physical tab. You will see the following figure
Then, turn off the switch. If you cannot see the switch, zoom in to find it. After you turn off the switch, we can add the serial port to the router. Click HWIC-2T (The HWIC-2T is a Cisco 2-port Serial High-Speed WAN Interface Card, providing 2 serial ports), and drag it to any slot. After that, turn on the switch. Then, the back of the router looks like the following figure.
Repeat the same process for R1 and R3.
Step 4.2: Connect Serial ports by Serial DCE
· R1 S0/1/0 to R2 S0/1/0 (note: click R2 first to make the interface as DCE)
· R2 S0/1/1 to R3 S0/1/0 (note: click R2 first to make the interface as DCE)
Your topology should be the same as the following figure.
Step 5: Configure no-domain lookup on all routers and switches
Click R1, then choose the CLI tab. First, you need to enter the configure terminal mode. Then, use the command “no ip domain-lookup” to disable the DNS lookup.
Repeat the same process for all routers (R2 and R3) and switches (SW1, SW2, and SW3).
3.3 LAN Configuration
Step 6: Assign IP address and subnet to GigabitEthernet interfaces of R1, R2 and R3. Here is the command for R1. You need to repeat the same process for R2 and R3.
· R1: GigabitEthernet 0/0: 172.16.10.1/24
· R2: GigabitEthernet 0/0: 192.168.2.2/27
· R3:
o GigabitEthernet 0/0: 192.168.2.3/27
o GigabitEthernet 0/1: 172.16.30.1/24
Step 7: Assign IP address, subnet, and default gateway to hosts.
Click the PC icon, then choose desktop tab. Enter the IP address and subnet mask under IP Configuration.
· PC-1:
o ip address and mask: 172.16.10.10/24
o Default gateway: 172.16.10.1
· PC-2:
o ip address and mask: 172.16.30.10/24
o Default gateway: 172.16.30.1
Step 8: Insure GigabitEthernet interfaces are not administratively down by access each interface and issue a “no shutdown” command. Here is the example for R1. Please repeat the same process for R2 and R3.
Step 8.1: Change the status from administratively down to administratively up
Step 8.2: Check the status by “show interface” command for all routers. Here is the example for R1. Please repeat the process for R2 and R3.
3.4 WAN Configuration
Step 9: Assign IP address and subnet to serial interfaces of R1, R2 and R3. Here is the example for R3. Please repeat the process for R1 and R2.
· R1
o S0/1/0: 192.168.0.1/30
· R2
o S0/1/0: 192.168.0.2/30
o S0/1/1: 192.168.1.1/29
· R3
o S0/1/0: 192.168.1.2/29
What is serial interface?
Serial interface is communication interface between two digital systems that transmit data as a series of volatage pulses down a wire.the serial interface encodes the bits of a binary number by their temporal location on a wire rather than their spatial location within a set of a wire.
Step 10: Assign IP address and subnet to loopback of R1 and R3
Here is the example for R1 Loopback interface 100. Repeat the same process for R1 Loopback interface 101, and R3 Loopback interface 100 and 101.
· R1
o Loopback 100: 10.10.100.1/27
o Loopback 101: 10.10.101.1/26
· R3
o Loopback 100: 10.30.100.1/29
o Loopback 101: 10.30.101.1/25
What is loopback address?
An address that sends outgoing signals back to the same computer for testing. The looback address allows for a reliable method of testing the functionality of an Ethernet card and its drivers and software without a physical network.it also allows information technology professionals to test IP coftware without worrying about broken or crupted driver or hardware
Step 11: Configure R2 interface Serial0/1/0 and Serial0/1/1 as DCE to provide clocking to R1 and R3 at a clock speed of 2 Mbps. Here is the example for interface S0/1/0. Repeat the same process for S0/1/1.
Tips: use “show controller S0/1/0” and “show controller S0/1/1” on R1, R2, and R3 to check which interface is DCE and which one is DTC.
What is DCE and what is DTE?
DCE stands for Data communications Equipment and DTE is Data terminal Equipment. At physical layer, a DCE takes data generated by a DTE, converts them to an appropriate signal, and then introduces signal onto telecommunication.
Step 12: Insure all interfaces are not administratively down.
Apply “no shutdown” for each interface and then use “show interface” to check the status.
Step 13: Using ping insure connectivity to the connected ports.
For example:
Can you successfully ping from PC-1 to PC-2? Show screenshot and explain why or why not.
Yes, I can ping PC-1 to PC-2 successfully
3.5 RIP Configuration
Step 14: Enable RIPv2 on R1, R2 and R3
Step 15: Configure RIPv2 routing for the GigabitEthernet and the Serial interfaces of R1, R2 and R3.
Here is the example for R1 for both Step 14 and 15. Repeat the same process for R2 and R3.
Step 16: Verify that RIPv2 has been enabled on R1, R2, and R3 using the appropriate commands.
Issue “show ip protocols” and “show ip route” on R1, R2 and R3. For example:
Can you successfully ping from PC-1 to PC-2? Show screenshot and explain why or why not.
3.6 Automatic Summarization
In your studies, you learned that RIPv2 performs automatic summarization at Classful boundaries.
Step 17: Disable automatic summarization on R1, R2, and R3.
Here is the example to disable automatic summarization on R1. Repeat the same process for R2 and R3.
Display the routing tables of R2 and R3 and verify that the 10.10.100.0/27 and 10.10.101.0/26 routes from R1 are now present.
Can you successfully ping from PC-1 to PC-2? Show screenshot and explain why or why not.
3.7 Verifying RIPv2 Updates Using Debug
RIPv2 update debugging is used by network engineers to troubleshoot network and routing problems. Like RIPv1, RIPv2 is a distance vector protocol that uses hop count with a maximum of 15 hops, but unlike RIPv1, RIPv2 sends updates using Multicast.
Enable debugging on R1 and R2 and verify that RIPv2 updates are being sent out of all RIPv2-enabled networks. Keep in mind that by default RIP sends updates every 30 seconds, so you will typically see updates within that time frame. Familiarize yourself with the output of the debugs.
Real World Tip: you may wish to start a capture on your terminal session to capture the debug output to a file so you can review it later.
Step 18: Issue “debug ip rip events” on R1 and R2
Here is the example for R1. Repeat the same process for R2.
Show the result you got by screenshot. Explain why or why not RIP works.
Step 19: Disable debugging on all interfaces.
Here is the example for R1. Repeat the same process for R2.
3.7 Passive Interfaces for RIPv2 Updates (Bonus 2 points)
In this part of the lab, you will show how to prevent RIPv2 from sending unnecessary updates by using passive interfaces.
By default, RIPv2 sends updates via Multicast on all interfaces for which RIPv2 has been enabled. For example, it is not possible to ever have another device connected to a Loopback interface, so it is a waste of router processing power to have RIPv2 continuously send updates to a Loopback interface.
Step 20: using the “show ip protocols” command verify which interfaces RIPv2 is sending updates on.
Show your screenshot and summarize interfaces that are enabled for RIPv2 updates.
Step 21: Enable debugging on R1 and show that RIPv2 updates are being sent on all RIPv2-enabled interfaces. Disable debugging when done.
Show screenshot and highlight important parts.
Step 22: Prevent RIPv2 from sending updates on the Loopback interfaces of R1 and R3.
Show your commands by using screenshot
Step 23: Verify your configuration by using the “show IP protocols” command and enabling debugging. Disable debugging when done.
Show screenshot and highlight important parts.