Online resources for University of Greenwich, School of Engineering


Introduction to Computer Networking 

 Labwork - Routing Protocol Basics
Download the PT file for this part of the lab and run it in Packet Tracer.

You may need to save it to the desktop before running Packet Tracer from the NAL window.


Use your log books to make notes for this lab.
Answer all questions.



Changing Hostnames

Note that for this lab, all commands are in courier font.

Click on Router 0 and the Control Panel will appear. Click the CLI tab.

Login to Router0 and gain access to User Exec mode.

Use the enable command to achieve this.

1. What is the router prompt?

Type the command show running-config

2. What addressing information is already entered for the Ethernet and Serial interfaces?

Type the command configure terminal

3. What has the command prompt changed to?

Type hostname London

4. What has the command prompt changed to?

Type the exit command , press ENTER then issue the write command.

If you do not issue the write command, your changes will be lost if the router loses power as they are only held in RAM until you issue the write command.

5. What is the name of the file that holds the router's configuration once you have saved it?

Now rename Router1 using the same commands as above, except its name will be Paris.

Rename Router2 to Berlin.

Rename Router3 to Rome.

Save all configurations on each router using the write command.

6. Which Priv Exec command will perform the same function as the write command?


Changing the Display Name

The display names should now be changed to match the names you have already given these routers.

In the Control Panel, Config tab, for each router, enter the appropriate name as described above in the field called, 'Display Name'

When you have finished this, all routers should be correctly named in both the IOS and on the screen.

Save all configurations on each router using the write command.

Remember to save your work regularly.
If Packet Tracer or your PC crashes, you will lose all unsaved work!


Setting IP addresses on interfaces

The IP addressing scheme is given in the diagram above.

Hover over each of the Ethernet and Serial links in the Packet Tracer application to discover which router port it is connected to as shown below.
The clock icon can be seen on the left next to the interface description, Se0/0.


Make a table similar to the one below showing interface connections for each router in the network.

Add the IP address and subnet mask for each of the router's connected interfaces similar to that below for all FOUR routers.
You can find these details on the network diagram at the top of this page.

Note that each serial link has a small icon representing a clock at ONE end only.
This end of the serial link, known as DCE, supplies the timing to the other end of the link.
Make a note which interfaces are responsible for supplying the clocking in your tables in the DCE/DTE column.
In this lab we will use 56000 bps for the Clock Rate.

London
Interface
IP Address
Subnet Mask
Clock Rate
DCE/ DTE
FastEthernet0/0  
200.22.0.1           
255.255.255.0     
N/A               
N/A                                                      
Serial0/0
192.168.100.1
255.255.255.0 56000 bps
DCE                      
Serial0/1 Not connected
Not connected
Not connected
Not connected   


Paris
Interface
IP Address
Subnet Mask
Clock Rate
DCE/ DTE
                              
                                  
                                 
                           
                                











Berlin
Interface
IP Address
Subnet Mask
Clock Rate
DCE/ DTE
                              
                                  
                                 
                           
                                











Rome
Interface
IP Address
Subnet Mask
Clock Rate
DCE/ DTE
                              
                                  
                                 
                           
                                











Once you have completed all FOUR tables, you can begin entering the interface addresses using the highlighted commands from the CLI tab as shown below.

7. Make a copy of these tables available in your log books.

Do not forget to issue the no shutdown command to turn the interface on. Routers by default have their interfaces turned off.
As you enter commands, the router will issue status messages to show that it has accepted the commands.


London#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
London(config)#interface FastEthernet0/0
London(config-if)#ip address 200.22.0.1 255.255.255.0
London(config-if)#no shutdown

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
London(config-if)#interface Serial0/0
London(config-if)#ip address 192.168.100.1 255.255.255.0
London(config-if)#clock rate 56000
London(config-if)#no shutdown

%LINK-5-CHANGED: Interface Serial0/0, changed state to down
London(config-if)#end
%SYS-5-CONFIG_I: Configured from console by console
London#write

Now do the same for the other THREE routers BUT use their IP addressing information from the tables you have created.

Remember to put a clock rate of 56000 bps on all serial links that are the DCE end of the link.

There is no need for a clock rate to be entered on the DTE end of a serial link.

When you have completed this, all links should have a green dot in the Packet Tracer application to show that the interfaces are 'up'.

If any of the links remain red, you should check you have entered the interface data correctly.

At the Priv Exec prompt enter the command show ip interface brief for each router.

London#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
 
FastEthernet0/0        200.22.0.1      YES manual up                    up
 
FastEthernet0/1        unassigned      YES manual administratively down down
 
Serial0/0              192.168.100.1   YES manual down                  down
 

The Status and Protocol should both appear 'up' not 'down as highlighted above. 'down' indicates a problem with the configuration.

8. Take a screenshot of the output of the command show ip interface brief for each router.


Setting up Routing

For each router, make a note of the NETWORKS it has attached to it. You will need these when you enter the routing information.

Make a table to hold this information. Look at the Packet Tracer screen and check the interface connections and their IP addresses. 

Enter these addresses and the subnet mask as shown below.

Router
London
Paris
Berlin
Rome
192.168.100.0 /24
a.b.c.d /?
a.b.c.d /?
a.b.c.d /?
200.22.0.0 /24
a.b.c.d /? a.b.c.d /? a.b.c.d /?

c.d.e.f /? g.h.i.j /? l.m.n.o /?

Now enter Global Configuration mode for the London router.

Type the commands as shown below:

London#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
London(config)#router rip
London(config-router)#network 192.168.100.0
London(config-router)#network 200.22.0.0
London(config-router)#end
%SYS-5-CONFIG_I: Configured from console by console
London#write

Repeat this using your network information for all the other routers in your network.

Remember that you only need to include those networks that are actually connected to each particular router.

When you have done this, type the command

Router#show ip route

This will show the networks that your router knows about.

London#show ip route
Codes: C - connected, S - static, I - IGRP, 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, E - EGP
       i - IS-IS, 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

C    192.168.100.0/24 is directly connected, Serial0/0
C    200.22.0.0/24 is directly connected, FastEthernet0/0
R    200.22.1.0/24 [120/1] via 192.168.100.2, 00:00:27, Serial0/0

London#

9. Refer to each of your routers and make a table that shows each of the networks it knows about and how it knows about them. This is shown in the Codes part of the routing table, e.g. the 200.22.1.0/24 network was discovered using RIP.


PC Addressing

Visit each PC in turn and click on the Desktop tab and enter the IP Configuration dialogue.



Add the IP addressing information as given in the diagram.

The default gateway will be the IP address of the router's FastEthernet interface to which the LAN is attached.

Try to ping one PC from another from the PC's command prompt.

10. Take a screenshot of a successful ping from PC to PC.

If this is successful, try using the tracert command to show all hops en route to the destination.

If this is not successful, you need to troubleshoot.

Troubleshooting
Check first that you can ping your local router.
Gradually move further away from the PC that issued the ping command until you cannot ping.
This will help you to isolate the problem.
Check the output from show ip interface brief to see if there are interface problems on your routers.


Save your results in your logbook.

If you wish, you may download Packet Tracer 5 from the Useful Applications link on the home page.



Back to Index page

Written by M Clements                        
Last updated :
27/01/2009 13:13