LAB MANUAL

Name: Saboor Ur Rahman

Reg ID: 54840
Course: Routing & Switching (Lab)
Faculty: Sir Mohsin Mubeen Abbasi
Class Timings: Tuesday (2:30 – 5:30)
Table of Contents

Lab 1 Basic Switch Configuration

Lab 2 VLAN
Lab 3 Trunk
Lab 4 EtherChannel
Lab 5 VTP Modes
Lab 6 InterVLAN Routing
Lab 7 Configuring Static Route
Lab 8 Configuring Default Route
Lab 9 Routing Information Protocol (RIP)
Lab 10 VLSM Network - RIP vs RIPv2
Lab 11 Discontiguous Network – EIGRP
Lab 12 OSPF
 Lab 1
Basic Switch Configuration
Learning Objectives:
• Configure a switch with a name
• Configure passwords to ensure that access to the CLI is secured.
• Connect PC0 and PC1 to the switch as shown in the diagram
• Assign Static IP address to both PC’s
• Verify the connectivity by sending PING message from PC0 to PC1
• Save the active configuration

Physical Topology:

Switch name: IU
First Computer: PC0, 192.168.1.1
Second Computer: PC1, 192.168.1.2
Line Console password: cisco
Enable Secret password: cisco

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.
Step 1 Enter privileged mode

a. Privileged mode gives access to all the switch commands. Many of the privileged commands configure
operating parameters. Therefore, privileged access should be password-protected to prevent
unauthorized use. The privileged command set includes those commands contained in user EXEC mode,
as well as the configure command through which access to the remaining command modes is gained.

Switch>enable
Switch#

b. Notice the prompt changed in the configuration to reflect privileged EXEC mode.

Step 2 Examine the current switch configuration

a. Examine the following current running configuration file:

Switch#show running-config

b. How many Ethernet or Fast Ethernet interfaces does the switch have?

24 Fast Ethernet interfaces and 2 Gigabit Ethernet interfaces.

c. What is the range of values shown for the VTY lines?

0 to 15.

d. Examine the current contents of NVRAM as follows:

Switch#show startup-config
%% Non-volatile configuration memory is not present

e. Why does the switch give this response?

The startup configuration has not been saved to NVRAM yet. This is why the configuration file does not
exist in NVRAM.

Step 3 Assign a name to the switch

a. Enter enable and then the configuration mode. The configuration mode allows the management of
the switch. Enter IU, the name this switch will be referred to in the following:

Switch#configure terminal

Enter the configuration commands, one for each line. End by pressing Ctrl-Z.
Switch(config)#hostname IU
IU(config)#exit

b. Notice the prompt changed in the configuration to reflect its new name. Type exit or press
Ctrl-Z to go back into privileged mode.

Step 4 Examine the current running configuration

a. Exam the current configuration that follows to verify that there is no configuration except for the
hostname:

IU#show running-config

b. Are there any passwords set on the lines?

No, there are no passwords configured yet.

c. What does the configuration show as the hostname of this switch?

IU.

Step 5 Set the access passwords (1900: Skip to Step 6)

Enter config-line mode for the console. Set the password on this line as cisco for login. Configure the vty
lines 0 to 15 with the password cisco as follows:

IU#configure terminal

Enter the configuration commands, one for each line. End by pressing Ctrl-Z.

IU (config)#line con 0
IU (config-line)#password cisco

IU (config-line)#line vty 0 15
IU (config-line)#password cisco

IU (config-line)#exit

Step 6 Set the command mode passwords

a. Set the enable password to cisco and the enable secret password to class as follows:

IU (config)#enable password cisco

IU (config)#exit

IU (config)#enable secret password cisco

IU (config)#exit
b. Which password takes precedence, the enable password or enable secret password?

The enable secret password takes precedence.

Step 7 Assign IP addresses to both Computers

a. Click on PC0, Go to Config and assign IP address 192.168.1.1 to Fast Ethernet

Click on PC1, Go to Config and assign IP address 192.168.1.2 to Fast Ethernet

b. Open Command Prompt on PC0

Ping PC1 by using the command below

PC>Ping 192.168.1.2

c. Note down the PING result

Step 8 Save the configuration

a. The basic configuration of the switch has just been completed. Back up the running configuration file
to NVRAM as follows:

Note: This will ensure that the changes made will not be lost if the system is rebooted or loses power.
IU#copy running-config startup-config
Destination filename [startup-config]?[Enter]
Building configuration...

[OK]
IU#

b. Configuration upload is successfully completed.

Step 9 Examine the startup configuration file

a. To see the configuration that is stored in NVRAM, type show startup-config from the privileged EXEC
(enable mode).

IU#show startup-config

b. What is displayed?

The startup configuration file will display the saved configuration, including the hostname, passwords,
and any additional settings configured.

c. Are all the changes that were entered recorded in the file?

Yes, all changes saved with the copy running-config startup-config command will be recorded in the file.

Step 10 Exit the switch

Leave the switch welcome screen by typing exit as follows:

IU#exit

Once these steps are completed, logoff by typing exit, and turn all the devices off. Then remove and
store the cables and adapter.

Conclusion:

The switch was successfully configured with a hostname and passwords for console and VTY lines.
The enable secret password was set to enhance security.
IP addresses were assigned to PCs, and successful connectivity was verified using the ping command.
The configuration was saved to NVRAM to prevent data loss on reboot.

Learning Outcomes:
Learned how to configure and secure a switch using privileged and configuration modes.
Gained practical knowledge of assigning IP addresses and verifying connectivity.
Understood the importance of saving the configuration to NVRAM for persistent settings.
 Lab 2
Configuring VLAN’s
Learning Objectives:
In this Lab we exercised the features of VLAN and how the VLAN’s are created in a switched
environment.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.

Creating and configuring VLAN on a single Switch

Step 1: Check Switch configuration

S1#show running-config

a. How many VLAN’s are showing in the configuration

5 VLANs (Default VLANs: VLAN 1, 1002, 1003, 1004, 1005).

b. Is there any IP address configured on VLAN

No, by default, VLAN 1 does not have an IP address configured.
Step 2: Configuring IP address on Switch

a. a. Set the IP address of the switch to 192.168.1.10 with a subnet mask of 255.255.255.0 as follows:

Note: This is done on the internal virtual interface VLAN 1.

S1(config)#interface VLAN 1
S1(config-if)#ip address 192.168.1.10 255.255.255.0
S1(config-if)#exit

Step 3: Assigning IP addresses to computers as follows

PC1: 192.168.1.1
PC2: 192.168.1.2
PC3: 192.168.1.3
PC4: 192.168.1.4

a. Are you able to PING switch IP address from any of the machines

Yes, if the IP addresses and subnet mask are configured correctly on both the switch and PCs.

b. Note down the switch port numbers where the computers are connected
PC1 connects to port __1___
PC2 connects to port __2___
PC3 connects to port __3___
PC4 connects to port __4___

c. PING PC1 PC2, PC1 PC3, PC3 PC4 and note down the results

d. Use the following command to display basic information about switch VLAN interfaces

Switch1#show vlan brief

e. Port numbers 1, 2, 3 and 4 are associated with which Vlan?

VLAN 1 (default VLAN).

Step 4: Creating a new VLAN on the switch

a. Create a new VLAN 2 as follows

Switch1#config t
Switch1(config)#vlan 2
Switch1(config)#exit

b. Check vlan information again.

Switch1#show vlan brief
 c. Has Vlan 2 been created on the switch?

Yes, VLAN 2 will be displayed in the output of the show vlan brief command.

Step 5: Assigning ports to Vlan 2

a. Assign Ports 3 and 4 to Vlan 2 as follows

Switch1(config)#interface fastethernet 0/3
Switch1(config-if)#switchport access vlan 2
Switch1(config-if)#exit

Switch1(config)#interface fastethernet 0/4

Switch1(config-if)#switchport access vlan 2
Switch1(config-if)#exit

b. PING PC1 PC3, PC1 PC4, PC3 PC4

c. Are you able to PING PC3 from PC1? Not successful (different VLANs).
d. Are you able to PING PC4 from PC3? Successful (both in VLAN 2).

Conclusion:
VLANs were successfully created and configured to segment the network.

PCs in different VLANs cannot communicate unless routing is configured between VLANs.

Ports were assigned to VLAN 2, demonstrating traffic isolation between VLANs.

Learning Outcomes:
Gained practical knowledge of creating VLANs and assigning switch ports to VLANs.

Understood the role of VLANs in traffic isolation within a switched network.

Learned to configure IP addresses on VLAN interfaces and PCs to verify connectivity.

 Lab 3
VLAN Trunk
Learning Objectives:
In this lab students will exercise the features of VLANs on multiple switches. Create VLAN Trunk to pass
the tagged traffic from one switch to another.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.

Part 1: Creating and configuring VLAN on a multiple Switches

Step 1:

a. Connect PC 1 and PC 2 to port 1 and port 2 on Switch 1 respectively

b. Connect PC 3 and PC 4 to port 1 and port 2 on Switch 2 respectively

c. Which cable configuration is used to connect a computer to a switch?

Straight-through cable.
 d. Which cable configuration is used to connect both switches?
Crossover cable.

Step 2 : Assign IP addresses to all the computers as follows

PC1: 192.168.1.1 PC2: 192.168.1.2

PC3: 192.168.1.3 PC4: 192.168.1.4

a. Check Vlan status on both switches using the following command

Switch#sh vlan brief

b. At this point all computers should be able to access each other. Verify it by using PING command

At this stage, all computers should communicate successfully since they are in the default VLAN
1.

Step3: Creating VLAN

a. Create Vlan 2 on Switch 1 and Switch 2 by using the command below

Switch#config t
Switch(config)#vlan 2
Switch(config)#exit

b. Add port 1 of switch 1 and port 2 of switch 2 to Vlan 2. Follow the command below
Switch1(config)#interface fastethernet 0/1
Switch1(config-if)#switchport access vlan 2
Switch1(config-if)#exit

Switch2(config)#interface fastethernet 0/2

Switch2(config-if)#switchport access vlan 2
Switch1(config-if)#exit

c. Are you able to PING from PC 1 to PC 2, if No then Why ?

No.
Reason: PC1 and PC2 are now in different VLANs, and inter-VLAN routing is not configured.

d. Are you able to PING from PC 1 to PC 4, if No then Why?

No.
Reason: PC1 and PC4 are in same VLANs, But there is no trunk route setup.

e. PING PC 2 > PC 3, Can you PING? If Yes then how?

Yes.
Reason: PC2 and PC3 are in VLAN 1 and can communicate.
Step 4: Adding a trunk port

a. Make Port 3 on Switch 1 and Switch 2 a Trunk port. Follow the command
Switch1#conf t
Switch1(config)#switchport mode trunk
Switch1(config)#exit

b. Are you able to PING from PC 1 to PC 4?

Yes.
Reason: The trunk allows VLAN 2 traffic to pass between switches.
c. Are you able to PING from PC 2 to PC 3?
Yes.
Reason: PC2 and PC3 are in VLAN 1, and the trunk carries VLAN 1 traffic.
d. Are you able to PING from PC 2 to PC 4?
No.
Reason: PC2 is in VLAN 1, while PC4 is in VLAN 2, and inter-VLAN routing is not configured.

Conclusion:

VLANs effectively isolate traffic between devices in different VLANs.

Trunking enables VLAN traffic to pass between switches.

Inter-VLAN communication requires routing, which is not configured in this lab.

Learning Outcomes:

Understood VLAN creation and configuration on multiple switches.

Learned to configure trunk ports to enable VLAN traffic across switches.

Verified network connectivity and traffic isolation between VLANs.

 Lab 4

Configuring EtherChannel
Learning Objectives:
In this Lab students will exercise the features of EtherChannel.

EtherChannel is a port link aggregation technology or port-channel architecture used primarily on Cisco
switches. It allows grouping of several physical Ethernet links to create one logical Ethernet link for the
purpose of providing fault-tolerance and high-speed links between switches, routers and servers.

Physical Topology:

Background/Preparation:

Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.

Step 1:

a. Follow the steps from Lab 3 to create VLANs on both switches

b. Configure Trunk on Port GigaEthernet 1/1 and 1/2 on both switches
c. At this point PC1 should PING PC4 and PC2 will PING PC3. Verify the results.
Step 2:

a. Check running configuration as follow

Switch#show running-config

Note: At this point a trunk will be shown on Gigabitethernet ports but no etherchannel is configured

b. Check trunk status by using the command

Switch#show interfaces trunk
c. What ports are configured for Trunk
Ports GigabitEthernet 1/1 and 1/2 on both switches are configured for Trunk.

d. What’s the status of the trunk and the encapsulation used

The trunk status is "up", and the encapsulation used is 802.1Q.

e. Check Etherchannel Status as follow

Switch#Show etherchannel summary

f. Is any Etherchannel showing in the configuration

No, EtherChannel is not yet configured.

Step 3:

a. Configure etherchannel on port Ge1/1 and 1/2 on both switches. Follow the command below
Switch#conf t

Switch(config)#interface range gigabitEthernet 1/1 – 2

Switch(config-if-range)#channel-group 1 mode desirable

Switch(config-if-range)#exit

b. Check Etherchannel Status as follow

Switch#Show etherchannel summary

c. How many channel groups are showing

One channel group is showing.

d. What ports are bundled up in etherchannel.

Ports GigabitEthernet 1/1 and 1/2 are bundled up in EtherChannel.

e. What is the protocol used in etherchannel

The protocol used in EtherChannel is PAgP (Port Aggregation Protocol).
Step 4:

a. Ping PC1 > PC4 and PC2 > PC3 and verify the connectivity

Both pings should be successful, the EtherChannel configuration is working, and the devices are
connected as expected.

Conclusion:
In this lab, we configured and tested EtherChannel between two switches to combine multiple physical

Ethernet links into a single logical link for improved fault tolerance and bandwidth. After verifying the

trunk configuration and ensuring proper connectivity between PCs, we proceeded to configure the

EtherChannel, checking the show etherchannel summary command to confirm its status. Successful

pings confirmed the EtherChannel setup was effective for improving network reliability and

performance.

Learning Outcomes:
Learned how to configure EtherChannel to aggregate multiple links into a single logical connection.

Gained an understanding of the trunking and EtherChannel configurations using commands like show

running-config, show interfaces trunk, and show EtherChannel summary.

Confirmed the effectiveness of EtherChannel for enhancing fault tolerance and network speed.

Verified the connection status and the correct operation of the EtherChannel with pings and network

tests.
 Lab 5

Virtual LAN Trunking Protocol (VTP) Modes

Learning Objectives:
In this Lab students will exercise the features of VLAN and also VTP role in sharing information of VLAN
database between connected Switches. Students will learn and implement VTP modes i.e. Server, Client
and Transparent.

Physical Topology:

Background/Preparation

Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.

Step 1: Configuring Trunk between switches

a. Configure Trunk ports between all switches. Use the following common
Switch(config)#switchport mode trunk
 b. Check Trunk status on all switches using the command
Switch#show interfaces trunk

c. Write down the port numbers on each switch that are configured for trunk

Step 2: Assigning IP addresses to the computers

PC 1: 192.168.1.1 PC 2: 192.168.1.2 PC 3: 192.168.1.3

Note: At this point all computers should be able to PING each other.

Step 3: Configuring VTP domain name

a. Check VTP status on all switches using the command below

Switch#show vtp status

Note: All switches are in Server Mode and VTP domain name shows empty

b. Login to Switch0, use the command below to configure VTP domain name
Switch0(config)#vtp domain IU

c. Check vtp status again. Domain name should be set to IU now.

d. Check vtp status on all remaining switches. The change will reflect on other switches after short
interval.

Step 4: Configuring VTP Modes

a. Switch0 is already on Server mode. Configure Switch1, Switch2 and Switch3 as Clients using the
command below
Switch(config)#vtp mode client

b. Configure Transparent mode on Switch4 and Switch5 using the command below
Switch(config)#vtp mode transparent

Step 5: Creating VLANs and verify VTP advertisement

a. Create VLAN2 and VLAN3 on switch0.

b. Check Vlan status on Switch1, 2 and 3. Has VLAN2 and VLAN3 been created automatically on
these switches

Yes, VLANs 2 and 3 will be automatically created on these switches since they are in Client mode
and receive the VTP advertisement.

c. Check VLAN status on Switch4 and 5. Have new vlans been created on these switches

No new VLANs will be created on Switches 4 and 5 because they are in Transparent mode and
do not participate in VTP.
 d. Delete VLAN 3 on Switch0. Check the status on Client switches.

VLAN 3 will be deleted on Switch0, and the change will propagate to the client switches.

Conclusion:
In this lab, we successfully configured VTP to share VLAN information across multiple switches. We

verified the operation of VTP in different modes—Server, Client, and Transparent—and confirmed that

VLANs created on the VTP Server were automatically propagated to the Client switches, but not to the

Transparent mode switches.

Learning Outcomes:
Configured VLANs and used VTP for automatic VLAN distribution across switches.

Configured and understood the behaviour of VTP Server, Client, and Transparent modes.

Verified how VLAN changes are reflected across switches in different VTP modes.
 Lab 6
Basic Inter-VLAN Routing
Learning Objectives:
In this lab, students will learn how to configure a router to pass traffic from one VLAN to another VLAN.
Students will learn Inter-VLAN routing.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch. Any other switch used may produce different output. Select the “Command
Line” option from the menu to perform the steps for this lab.

Step 1: Configuring VLAN

a. Create VLAN 2 on Switch0

b. Add PC2 to VLAN2

c. Check Vlan status by using the command below

 Switch(config)#shvlan brief

Note: PC1 will remain in VLAN1

Step 2: Assigning IP addresses to the computers

PC1: IP address 192.168.1.1

Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.5

PC2: IP address: 192.168.2.1

Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.5

a. PING PC1 > PC2

b. Were you able to PING

At this stage, you will not be able to PING PC2 from PC1 because they are in separate VLANs, and
inter-VLAN routing is not yet configured.

Step 3: Create a trunk between Switch and a Router

Switch(config)#interface fastethernet 0/3

Switch(config-if)#switchport mode trunk

Step 4: Configuring Router

Router(config-if)#interface fastethernet 0/0.1

Router(config-subif)#encapsulation dot1q 1
Router(config-subif)#ip address 192.168.1.5 255.255.255.0
Router(config-if)#interface fastethernet 0/0.2
Router(config-subif)#encapsulation dot1q 2
Router(config-subif)#ip address 192.168.2.5 255.255.255.0

Step 5: Displaying Routing Table

a. Type show ip route at the privileged EXEC mode prompt.

b. Are there entries in the routing table?
Yes, there should be two directly connected networks (192.168.1.0/24 and 192.168.2.0/24).
c. What interface are they all pointing to?
FastEthernet 0/0.1 and FastEthernet 0/0.2.
Step 6: Verifying the result

a. PING PC1 > PC2

b. Were you able to PING? Yes.

Conclusion:

VLANs successfully isolate traffic within their broadcast domains.

Configuring a trunk port allows tagged VLAN traffic to pass between a switch and a router.

Sub interfaces on the router enable inter-VLAN communication.

Routing table entries confirm connectivity between VLANs, ensuring proper network

segmentation and traffic flow.

Learning Outcomes:

Developed practical skills in VLAN and inter-VLAN routing configurations.

Learned how to configure subinterfaces on a router for inter-VLAN communication.

Verified network functionality and understood the role of a routing table in VLAN routing.
 Lab 7
Configuring Static Route
Learning Objectives:
In this Lab students will learn to configure static route on Cisco routers to ensure end-to-end
connectivity between PC0 and PC1

Physical Topology

Background/Preparation

Cable a network similar to the one in the diagram. The configuration output used in this lab is produced
from a 2960 series switch and 2811 router. Any other switch used may produce different output. Select
the “Command Line” option from the menu to perform the steps for this lab.

Step 1: Configuring Routers

a) Configure Router 1, Router 2 and Router 3 as follows

Router 1:
Fe0/0: 10.1.1.1 255.255.255.0
S1/0: 10.1.3.1 255.255.255.0

Router 2:
Fe0/0: 10.1.2.1 255.255.255.0
S1/0: 10.1.3.2 255.255.255.0

b) Configure DCE clock rate 64000 on serial interface of Router 1 using the following command
 Router 1#conf t
Router 1(config)#clock rate 64000
Router 1(config)#exit

c) How many subnets are there in the network and what are they
There are two subnets:
Subnet 1: 10.1.1.0/24 (Router1 and PC0)
Subnet 2: 10.1.2.0/24 (Router2 and PC1)
Inter-router link: 10.1.3.0/24

Step 2: Configure IP address and default Gateway on both computers

PC 0:
IP Address 10.1.1.2
Gateway: 10.1.1.1

PC 2:
IP Address: 10.1.2.2
Gateway: 10.1.2.1

a) Ping PC0 > PC1

b) Are you able to PING? What’s the ping result
At this stage, the ping will fail because static routes are not yet configured on the routers.

Step 3: Configuring IP Routes on both Routers

Router 1:
Router(config)#ip route 10.1.2.0 255.255.255.0 10.1.3.2

Router 2:
Router(config)#ip route 10.1.1.0 255.255.255.0 10.1.3.1

a) Ping PC0 > PC1

b) Is the ping successful? If yes then why.

Ping from PC0 (10.1.1.2) to PC1 (10.1.2.2).

The ping is successful because static routes allow the routers to forward packets between the
subnets.
Conclusion:

Static routes were successfully configured to enable communication between different subnets.

Routers can manually direct traffic to networks that are not directly connected.

End-to-end connectivity was verified by a successful ping between PC0 and PC1.

Learning Outcomes:

Gained hands-on experience configuring IP addresses, gateways, and static routes.

Understood the importance of static routing in network communication.

Learned how to troubleshoot connectivity issues in multi-router setups

 Lab 8
Configuring Default Static Route
Learning Objectives:
In this Lab students will learn to configure default static route on Cisco routers to ensure end-
to-end connectivity between PC0 and PC1

Physical Topology:

Background:

Router0 does not have a route to a remote unknown network 172.16.5.0 which is a Router 2
LAN. Router 2 also have no routes back to Router 0 LAN which is 172.16.6.0 Default route will
be configured on Router 0 and Router 2 to access the unknown networks

Step 1: Configuring Router Interfaces

d) Configure Router 0, Router 1 and Router23 as follows

Router 0:
Fe0/0: 172.16.6.1 255.255.255.0
S1/0: 10.1.1.1 255.255.255.0

Router 1:
S1/0: 10.1.1.2 255.255.255.0
S1/1: 192.168.1.1 255.255.255.0
Router 2:
Fe0/0: 172.16.5.1 255.255.255.0
S1/0: 192.168.1.2 255.255.255.0

e) Configure DCE clock rate 64000 on serial interface of Router 0 and Router 2 using the following
command

Router 1#conf t
Router 1(config)#clock rate 64000
Router 1(config)#exit

f) Check the routing table on all routers using “show ip route” command. What routes are
showing up in each router
Router 0: Should only display directly connected routes for 172.16.6.0 and 10.1.1.0.
Router 1: Should display directly connected routes for 10.1.1.0 and 192.168.1.0.
Router 2: Should display directly connected routes for 172.16.5.0 and 192.168.1.0.

Step 2: Configure IP address and default Gateway on both computers

PC 0:
IP Address 172.16.6.2
Gateway: 172.16.6.1

PC 1:
IP Address: 172.16.5.2
Gateway: 172.16.5.1

c) Ping PC0 > PC1

d) Are you able to PING? What’s the ping result
The ping will fail because static/default routes are not yet configured.

Step 3: Configuring Static IP Route on Router 1 to both LAN’s

Router(config)#ip route 172.16.6.0 255.255.255.0 Serial 1/0

Router(config)#ip route 172.16.5.0 255.255.255.0 Serial 1/1

c) Ping PC0 > PC1. Are you able to PING?

The ping may still fail since routers 0 and 2 don't have a route to each other's LANs.

Step 4: Configuring Default Static Route on Router 0 and Router 2

Router0(config)# ip route 0.0.0.0 0.0.0.0 Serial1/0

Router2(config)# ip route 0.0.0.0 0.0.0.0 Serial1/0

a) PING PC0 > PC1. Are you able to ping?

The ping should now be successful because the default routes allow Router 0 and Router 2 to
forward packets for unknown networks to Router 1.

b) Check the routing table and write down the entries for each router
Router 0: Should display directly connected routes and the default route via serial 1/0.
Router 1: Should display static routes to both LANs and directly connected routes.
Router 2: Should display directly connected routes and the default route via serial 1/0.

Conclusion:
Default static routes were successfully configured on Router 0 and Router 2 to enable communication

between unknown networks.

The static routes on Router 1 facilitated the interconnection between LANs.

End-to-end connectivity between PC0 and PC1 was verified using successful ping tests.

Learning Outcomes:
Understood the configuration of default static routes and their role in forwarding packets to unknown

networks.

Learned to verify connectivity and troubleshoot routing issues using the ping command.

Gained hands-on experience with routing table analysis using the show ip route command.
 Lab 9
Configuring RIP
Learning Objectives:
In this Lab students will learn about Routing Information Protocol (RIP) and how to configure
RIP on Cisco routers.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is
produced from a 2960 series switch and 2811 router. Any other switch used may produce
different output. Select the “Command Line” option from the menu to perform the steps for
this lab.
Step 1: Configuring Routers

g) Configure Router 0, Router 1 and Router 2 as follows

Router 0:
Fe0/0: 192.168.1.1 255.255.255.0
S1/0: 192.168.2.1 255.255.255.0

Router 1:
Fe0/0: 192.168.3.1 255.255.255.0
S1/0: 192.168.2.2 255.255.255.0
S1/1: 192.168.4.1 255.255.255.0

Router 2:
Fe0/0: 192.168.5.1 255.255.255.0
S1/0: 192.168.4.2 255.255.255.0

h) Configure DCE clock rate 64000 on serial interface of Router 0 and Router 1 using the
following command

Router #conf t
Router(config)#clock rate 64000
Router(config)#exit

i) How many subnets are there in the network and what are they?

1. 192.168.1.0/24
2. 192.168.2.0/24
3. 192.168.3.0/24
4. 192.168.4.0/24
5. 192.168.5.0/24

Step 2: Configure IP address and default Gateway on all computers

PC 0:
IP Address 192.168.1.2
Gateway: 192.168.1.1

PC 1:
IP Address: 192.168.3.2
Gateway: 192.168.3.1

PC 2:
IP Address: 192.168.5.2
Gateway: 192.168.5.1

e) Ping PC0 > PC1 , PC0 > PC2

Ping will fail because dynamic routing (RIP) is not configured.
 f) Are you able to PING? What’s the ping result
Ping will fail because dynamic routing (RIP) is not configured.

Conclusion:

RIP was successfully configured on all routers to dynamically exchange routing information.

End-to-end connectivity between all PCs was achieved through dynamic routing.

The configuration was verified using show ip route, show ip protocols, and successful ping tests.

Learning Outcomes:
Understood the basic configuration and operation of RIP.

Learned to dynamically exchange routing information between routers using RIP.

Gained practical experience in verifying RIP using routing tables and protocol commands.
 Lab 10
VLSM Network
RIP vs RIPv2

Learning Objectives:
In this Lab students will learn to configure RIPv2 in a VLSM network. Students will learn the
difference between both RIP and RIPv2. RIP does not support VLSM Networks.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is
produced from a 2811 router. Any other Router used may produce different output. Select the
“Command Line” option from the menu to perform the steps for this lab.
Step 1: Configuring Routers

j) Configure Router 0, Router 1, Router 2 and Router 3 as follows

Router 0:
interface Serial1/0
ip address 10.1.2.1 255.255.255.0
clock rate 64000

Router 1:
interface Serial1/0
ip address 10.1.2.2 255.255.255.0
!
interface Serial1/1
ip address 10.1.3.1 255.255.255.252
clock rate 64000

Router 2
interface Serial1/0
ip address 10.1.3.2 255.255.255.252
!
interface Serial1/1
ip address 10.1.4.1 255.255.255.0
clock rate 64000

Router 3
interface Serial1/0
ip address 10.1.4.2 255.255.255.0

Step 2: Configuring RIP on all Routers

d) Referring to Lab 9 of RIP. Use the same commands to configure RIP on the routers.
e.g. Router(config)#router rip
Router(config)#network IP Address

e) PING PC0 > PC1

f) Are you able to ping? If Not then why?
Ping will fail because RIP does not support VLSM.

Step 3: Configuring RIPv2 on all Routers

Router 0
router rip
version 2
network 10.1.2.0

Router 1
router rip
version 2
network 10.1.2.0
network 10.1.3.0

Router 2
router rip
version 2
network 10.1.3.0
network 10.1.4.0
Router 3
router rip
version 2
network 10.1.4.0

a) Run “show ip route” on all routers. What networks are showing on Router 1 and 2

 Router 1: Networks 10.1.2.0 and 10.1.3.0.

 Router 2: Networks 10.1.3.0 and 10.1.4.0.

b) Are you able to ping from Router 1 to Router 3?

Yes, because RIPv2 supports VLSM, and routes are correctly advertised with subnet mask
information.

Conclusion:
RIP does not support VLSM because it does not advertise subnet mask information in routing updates.

RIPv2 supports VLSM, allowing networks with different subnet masks to be routed effectively.

By using RIPv2, dynamic routing in a VLSM network is achieved successfully.

Learning Outcomes:
Gained practical knowledge of configuring RIPv2 in a network.

Understood the limitations of RIP and the advantages of RIPv2 in handling VLSM networks.

Developed troubleshooting skills by analysing and resolving routing issues in RIP configurations.
 Lab 11
Discontiguous Network
EIGRP vs RIP
Learning Objectives:
In this Lab students will learn to configure EIGRP in a Discontiguous Network. Students will
learn the difference between both EIGRP and RIP. RIP does not support Discontiguous
Networks.

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is
produced from a 2960 series switch and 2811 router. Any other switch used may produce
different output. Select the “Command Line” option from the menu to perform the steps for
this lab.
Step 1: Configuring Routers

k) Configure Router 0, Router 1, Router 2 and Router 3 as follows

Router 0:
interface FastEthernet0/0
ip address 10.1.1.1 255.255.255.0S1/0: 10.1.3.1 255.255.255.0
!
interface Serial1/0
ip address 10.1.2.1 255.255.255.0
clock rate 64000

Router 1:
interface Serial1/0
ip address 10.1.2.2 255.255.255.0
!
interface Serial1/1
ip address 192.168.1.1 255.255.255.0
clock rate 64000

Router 2
interface Serial1/0
ip address 192.168.1.2 255.255.255.0
!
interface Serial1/1
ip address 10.1.4.1 255.255.255.0
clock rate 64000

Router 3
interface FastEthernet0/0
ip address 10.1.5.1 255.255.255.0
duplex auto
speed auto
!
interface Serial1/0
ip address 10.1.4.2 255.255.255.0

Step 2: Configure IP address and default Gateway on both computers

PC 0:
IP Address 10.1.1.2
Gateway: 10.1.1.1
PC 2:
IP Address: 10.1.5.2
Gateway: 10.1.5.1

g) Ping PC0 > PC1

h) Are you able to PING? What’s the ping result?

The ping will fail because the routers are not configured with any routing protocols yet, meaning
the routers do not know how to forward the traffic to the destination.

Step 3: Configuring RIP on all Routers

g) Referring to Lab 9 of RIP. Use the same commands to configure RIP on the routers.
e.g. Router(config)#router rip
Router(config)#network IP Address

h) PING PC0 > PC1

i) Are you able to ping? If Not then why?
Ping will fail because RIP does not support discontiguous networks.

Step 4: Configuring EIGRP on all Routers

Router 0
router eigrp 100
network 10.1.1.0
network 10.1.2.0
no auto-summary

Router 1
router eigrp 100
network 10.1.2.0
network 192.168.1.0
no auto-summary

Router 2
router eigrp 100
network 192.168.1.0
network 10.1.4.0
no auto-summary
Router 3
router eigrp 100
network 10.1.4.0
network 10.1.5.0
no auto-summary

c) Run “show ip route” on all routers. What networks are showing on Router 1 and 2
d) Are you able to ping from PC0 to PC1?
Yes, the ping works after EIGRP is configured.

e) Why use “no auto-summary” command?

To prevent EIGRP from summarizing routes at classful boundaries, which causes issues
in discontiguous networks.

Conclusion:

In this lab, we learned to configure EIGRP to support discontiguous networks. RIP was not suitable for

this topology because it could not handle discontiguous networks, and thus routing between them

failed. By configuring EIGRP with the "no auto-summary" command, we enabled the routers to handle

the discontiguous networks properly and established connectivity between PC0 and PC1

Learning Outcomes:
Understanding the limitations of RIP in discontiguous networks.

Configuring EIGRP to support discontiguous networks.

The significance of the "no auto-summary" command in EIGRP for correct routing.

Troubleshooting routing issues in discontiguous networks and resolving them with EIGRP.
 Lab 12
OSFP
Learning Objectives:
In this Lab students will learn about OSPF routing protocol. How OSPF is configured. Students
will learn different commands to verify OSPF configuration

Physical Topology:

Background/Preparation
Cable a network similar to the one in the diagram. The configuration output used in this lab is
produced from a 2960 series switch and 2811 router. Any other switch used may produce
different output. Select the “Command Line” option from the menu to perform the steps for
this lab.
Step 1: Configuring Routers

l) Configure Router 0, Router 1, Router 2 as follows

Router 0:
interface Serial1/0
ip address 192.168.10.1 255.255.255.252
clock rate 64000
!
interface Serial1/1
ip address 192.168.10.5 255.255.255.252
clock rate 64000

Router 1:
interface Serial1/0
ip address 192.168.10.2 255.255.255.252
!
interface Serial1/1
ip address 192.168.10.9 255.255.255.252

Router 2
interface FastEthernet0/0
ip address 10.1.1.1 255.255.255.0
!
interface Serial1/0
ip address 192.168.10.6 255.255.255.252
!
interface Serial1/1
ip address 192.168.10.10 255.255.255.252
clock rate 64000

Step 2: Configure IP address and default Gateway on PC0

PC 0:
IP Address 10.1.1.2
Gateway: 10.1.1.1

i) Ping PC0 > PC1

j) Are you able to PING? What’s the ping result?
The ping will fail because OSPF is not yet configured.

Step 3: Configuring OSPF on all Routers

Router 0
router ospf 1
network 192.168.10.4 0.0.0.3 area 0
network 192.168.10.0 0.0.0.3 area 0
Router 1
router ospf 1
network 192.168.10.8 0.0.0.3 area 0
network 192.168.10.0 0.0.0.3 area 0

Router 2
router ospf 1
network 192.168.10.4 0.0.0.3 area 0
network 192.168.10.8 0.0.0.3 area 0
network 10.1.1.0 0.0.0.255 area 0

f) Run “show ip route” on all routers. Note down the routing table of each router
Router 0: Will display networks 192.168.10.0/30 and 192.168.10.4/30.
Router 1: Will display networks 192.168.10.8/30 and 192.168.10.0/30.
Router 2: Will display networks 192.168.10.4/30, 192.168.10.8/30, and 10.1.1.0/24.

g) Are you able to ping from PC0 to Router 0? Yes

h) Run “Show ip ospf neighbors” command and note down the results.
Displays the OSPF neighbors (Router 1, Router 2) with their router IDs and state.
Both state is Full meaning OSPF is fully established

i) Run “show ip protocol” and note down the result.

Displays OSPF as the active routing protocol on all routers with network 0.0.0.0.
For OSPF it shows Routing protocol, Network statements, Routing protocol timer
settings

Conclusion:
In this lab, we configured and verified OSPF routing protocol on multiple routers. The network was

divided into different areas, and OSPF was enabled on the specified interfaces. The show ip route and

show ip ospf neighbors commands helped confirm the OSPF configuration and the establishment of

OSPF neighbors. The lab demonstrated how to set up OSPF, troubleshoot connectivity, and verify the

routing information exchanged between routers. Successful ping tests confirmed proper communication

between devices.
Learning Outcomes:
Learned how to configure OSPF on Cisco routers.

Gained an understanding of how OSPF exchanges routing information and establishes neighbor

relationships.

Became familiar with using commands like show ip route, show ip ospf neighbors, and show ip protocol

to verify and troubleshoot OSPF configurations.

Understood the role of areas in OSPF and how to configure networks within specific areas.