Download Lab 8: Configuring Network with RIP in ECE 4110 - Prof. Henry Owen and more Lab Reports Electrical and Electronics Engineering in PDF only on Docsity!
ECE 4110 Internetwork Programming
Lab 8: Configuring a Network Using RIP Routing Protocol
Group Number: _________________________
Member Names: _________________________ _________________________
Date Issued: November 10, 2005
Date Due: November 22, 2005
Last Edited: November 9, 2005
This lab requires that you use one of three setups. You must sign up in advance on
the lab door. You may reserve one setup for no more than 1.5 hours at a time. You must
use the same setup each time you work on this lab. You NEED your group hard drive
for this lab.
This is a very open ended lab, and you should start early to guarantee you
have enough time to finish.
Goal
In this lab you will become familiar with the Cisco routers and switches in our
lab. You will learn to program these routers to create a network, then you will experiment
with the routing protocol RIP to observe how routers communicate to make the network
functional.
Prelab Questions
QP.1: What are the differences between a distance vector and a link-state routing
protocol? What kind of routing protocol is RIP?
QP.2: What IP protocol and port number does RIP use?
QP.3: How do RIP routers to exchange routing information?
QP.4: What is the maximum number of routes that can be sent in a RIP update?
QP.5: What is VLSM? Does RIP support it? Justify your answer.
QP.6: What metric does RIP use?
Lab Scenario
In this lab we will construct the network pictured below.
( c is either 1, 2, or 3 and is the playstation number your using.)
RIP1 Digi#__
RIP4 Digi#___
RIP3 Digi# __ RIP2 Digi#__
Ethernet
FastEthernet
Ethernet0/
10.c.3.
10.c.6.
10.c.6.1 10.c.7.
10.c.8.
10.c.2.
10.c.2.
10.c.3.
10.c.7.
Network 10.c.8.
Ethernet
Ethernet1/
Ethernet
Ethernet
Ethernet
Ethernet
Linux
Computer
10.c.3.
Network 10.c.1.
Network
10.c.5.
Network
10.c.4.
FastEthernet
FastEthernet0 FastEthernet0/
10.c.1.
10.c.4.
10.c.5.
VLAN
VLAN
VLAN
VLAN
VLAN
VLAN
VLAN
VLAN
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch 0/__
Switch Digi#_____
Reference the following table to see which devices you will be programming:
Playstation1 Playstation2 Playstation
Switch 5 14 23
RIP1 Router 7 16 25
RIP2 Router 8 17 26
RIP3 Router 9 18 27
RIP4 Router 10 19 28
By typing the appropriate number, you gain access the router. To log out, type an
invalid option, such as q. Go to the router rack at the back of the classroom. The numbers
on the console manager and the above table correspond to the numbers posted to the left
of the physical routers in this rack. These are the devices you will be configuring.
Now by referring to the image on page 2 and the directions you followed in Lab6,
you need to setup the Cisco Router and Switches. You need to create the VLANS, define
the Switch interfaces, and configure each router interface. NOTE: DO NOT add static
routing like you did in Section 5 of lab 6. This document does not have explicit
instructions on how to set this topology up as you learned everything you need to know in
Lab 6.
The following table should be filled out with information about your setup.
Playstation Number: _________
Router Interface VLAN Switch Interface
Number
IP Address
RIP1 Ethernet
RIP1 Ethernet
RIP1 FastEthernet
RIP2 Ethernet
RIP2 Ethernet
RIP2 FastEthernet
RIP3 Ethernet
RIP3 Ethernet
RIP3 FastEthernet
RIP4 Ethernet
RIP4 Ethernet
RIP4 FastEthernet
Table 2.1: Router Interface Table
After you are done configuring the switch and routers through the DigiConsole, you will
also need to manually configure the networking cables so each router interface plugs into
the proper switch ports you have defined.
Section 2: Configuring RIP on Routers
At this point in time, all of our interfaces should be established and running. From
RIP4, attempt to ping 10.c.7.1. If you can do this, you can access your own interface.
Now attempt to ping 10.c.7.2. This should also be successful; you can now access RIP
across our functional VLAN!
Now try to ping 10.c.3.1. Although a functional link exists between RIP4 and
RIP3 and another exists between RIP3 and RIP1, this ping should fail. Routing has not
yet been setup on any of our routers, so no router can reach any interface that isn’t
directly connected! Type show ip route to see what networks your router can currently
access.
Q2.1: What is the output of this command? What information does this provide?
Reenter configuration mode. To enable RIPv4 routing, type:
# router rip
# version 2
RIP now requires that we tell it to which network it is routing, and to what other
routers we are directly connected.
Type:
# network 10.c.0.
to advise RIP to route to our entire network.
Next configure the neighboring routers by typing:
# neighbor 10.c.7.
# neighbor 10.c.6.
These are the IP addresses of the directly connected network interfaces of our
neighboring routers (see the network diagram).
Type exit to leave RIP configuration. Repeat these steps using the appropriate
neighbor IPs to configure all four of your RIP routers.
Finally our network is configured. After a few minutes the RIP messages will
propagate to create all network routes, our network should be fully functional. You may
wish to log onto each RIP machine and ping each of the nine router interfaces in order to
guarantee that your network is configured properly. If you cannot ping, you may have
configured one or more routers incorrectly, and you should fix this problem before
moving on to the next section. When troubleshooting, you may want to make use of the
show ip route command in order to see which interfaces are not functioning correctly.
Log back onto RIP4 and type show ip route again.
Q2.2: How has the output changed since you set up RIP? What do these changes
mean?
Q3.2.c: What value is the administrative distance for RIP? Why do you think this is
important?
Type traceroute 10.c.8.
When there are multiple routes with the same cost to a destination, routers often
use a technique called "equal cost load-balancing". The Cisco routers are configured to
alternate which equal cost route is used to send packets. For example, if you send 3
packets and there are 2 equal cost routes, the first packet would go out the first interface,
the second packet would go out the second interface, and then the third packet would go
out the first interface.
Q3.3: Copy your traceroute output below. What path(s) are taken? Include both IPs
and the names of the routers. Explain why the output appears as it does.
Connect to RIP3, then shutdown the interface Ethernet0/0:
#interface Ethernet 0/
#shutdown
Keep track of when you typed shutdown (start a stopwatch if you have one).
Because you have changed the network topology, the RIP process on RIP3 will send out
an immediate flash update. Note that you have simulated a network failure: interface
10.c.3.2 on RIP3 no longer works.
Connect to RIP1, and look at the routing table by typing show ip route. Now type
ping 10.c.7.1. You are trying to contact 10.c.7.1 (RIP4) which is on the other side of the
shutdown interface of RIP3.
Q3.4: Do you get a response? Why/Why not? How long should it take RIP1 to flush
its routing tables?
Type show ip route on RIP1 again.
Q3.5: What routes do you see? Is the routing table different from before? If so,
how?
If your routing table is unchanged, keep trying until it does change. If you surpass
7 minutes, ask a TA for help.
Q3.6: How long did it take the routing table of RIP 1 to change? Why?
Type ping 10.c.7..
Q3.7: Do you now see a response? Why or why not?
Now try to ping RIP1 from RIP3. On router RIP3 type ping 10.c.3.1.
Q3.8: Do you see a response? Why or why not? If it does not work repeat until it does
or ask a TA for help. If you did not see a response immediately, how long after
you shutdown RIP3 did it take before you could? Why?
Re-enable Ethernet0/0 with the no shutdown command.
Section 4: Observing RIP Traffic
In this section of the lab, you will use Ethereal to examine the updates that are
sent between routers. Looking at the network diagram, notice that there is a Linux
machine on the subnet between RIP1 and RIP3 labeled Linux Computer. This is one of
the setups entitled ECE 4110 Lab 8 Playstation #C in lab. From this machine open
Ethereal.
Under Display Options enable “Automatic scrolling in live capture” and disable
all three “Enable name resolutions”. Start capturing packets in promiscuous mode. Let
ethereal run for about 2 minutes and then stop capturing packets. Ignore the ARP and
TFTP traffic.
To save the data captured by Ethereal, you may need to use the procedure as the
following:
Click File -> Print
Choose "Format" as Plain Text ( PostScript is OK too, if you want to view it with
GSview...). Choose "Print to" as File.
Type a file name. Choose the style as you need to print.
You can save the file in your floppy disk, then open it later with any text editor on
another computer.
If you have Ethereal in your own PC, simply save the data in a file, then open it
with Ethereal.
You should see packets originating from two sources, 10.c.3.1 (RIP1) and
10.c.3.2 (RIP3). These are the router updates that are sent from one router to all
neighbors. Click on one of the packets originating from 10.c.3.1 and look at the contents
of the packet. Answer the following:
Q4.1: What is the destination address of IP multicast? What’s the significance of
this address?
Q4.2: What protocol (of transport layer) is used to send RIP updates?
Q4.3: What is the source port number?
