DATA NETWORKS LAYER

LABORATORY SESSION 5
EC4060

JENARTHTHAN A.
2021/E/006
GROUP CG1
SEMESTER 4
22 DEC 2023
OBJECTIVES

Part 1: Build the Network and Configure Basic Device Settings

Part 2: Configure Switches with VLANs and Trunking
Part 3: Verify Trunking, VLANs, Routing, and Connectivity

APPARATUS

1. 1 Router (Cisco 4200 series)

2. 2 Switches (Cisco 2960)
3. 2 PCs (Windows 10 with terminal emulation program)
4. Console cables to configure the Cisco IOS devices via the console ports
5. Ethernet cables as shown in the topology

PROCEDURE:

Erasing and Reloading the Switch

1. Opening Putty and Accessing Privileged EXEC Mode:

o The Putty application was launched.
o enable command was entered to access privileged EXEC mode.
2. Removing VLAN Database Information:
o The VLAN database information file was deleted.
3. Clearing Switch Startup Configuration from NVRAM:
o The switch startup configuration file stored in NVRAM was erased.
4. Verifying Deletion of VLAN Information:
o Checked whether VLAN information, excluding the default management VLAN, was
successfully deleted.
5. Restarting the Switch Software:
o The switch software was restarted using the reload command.

Steps:

1. Access Privileged EXEC Mode:

Switch>enable

2. Delete VLAN Database Information:

Switch#delete flash:vlan.dat
Delete filename [vlan.dat]? [Enter]
Delete flash:vlan.dat? [confirm] [Enter]
%Error deleting flash:vlan.dat (No such file or directory)

3. Erase Startup Configuration from NVRAM:

Switch#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm]
Erase of nvram: complete
 4. Reload Switch Software:

Switch(config)#reload
System configuration has been modified. Save? [yes/no]:
Proceed with reload? [confirm] [Enter]
Reload requested by console.
Would you like to enter the initial configuration dialog? [yes/no]:
Press RETURN to get started! [Enter]

OBSERVATION:

Figure 1: Putty Software Interface

Erasing and Reloading the Switch
Figure 2: Command Line Interface - Erasing and Reloading Switch
Erasing and Reloading the Router
1. Access Privileged EXEC Mode:

Router>enable

2. Delete Startup Configuration:

Router#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm]
Erase of nvram: complete

3. Reload Router Software:

Router(config)#reload
System configuration has been modified. Save? [yes/no]:
Proceed with reload? [confirm]
Reload requested by console.
Would you like to enter the initial configuration dialog? [yes/no]:
Press RETURN to get started!
 Figure 3: Command Line Interface - Erasing and Reloading the Router

DISCUSSION

The process of erasing and reloading a switch or router serves as a critical preparatory step in networking
labs. By starting with a clean slate, devoid of any prior configurations, this practice ensures a predictable and
stable environment for subsequent exercises. Removing VLAN databases and startup configurations not only
prevents potential conflicts but also establishes a reliable baseline, crucial for consistent lab outcomes.
Verification steps, such as checking for successful configuration deletion, enhance understanding and
proficiency in command-line operations. The act of restarting the device through the reload command
reinforces the importance of software readiness. In conclusion, the significance of this process lies in its role
as a foundational practice, fostering a conducive learning environment and providing essential skills for
effective network administration and configuration.

CONCLUSION

The importance of erasing and reloading lies in the establishment of a pristine, interference-free environment
for subsequent lab activities. This process ensures a predictable, reliable starting point, prevents
configuration conflicts, and sets the stage for effective learning and experimentation in network
configuration labs. The objectives include achieving a clean slate, verifying the removal of configurations,
and preparing the device for successful lab execution. This foundational knowledge is critical for anyone
pursuing hands-on experience in network administration and configuration.
Lab – Configuring Per-Interface Inter-VLAN Routing

Topology

The network topology consists of a router (R1) connected to two switches (S1 and S2) as per the provided
addressing table. Two PCs (PC-A and PC-B) are connected to S1 and S2, respectively.

Addressing Table

Background and Scenario:

• The lab aims to configure per-interface inter-VLAN routing, a legacy approach that facilitates
understanding before moving to more advanced methods.

Preparation:

• Verified that routers and switches have no startup configurations to ensure a clean setup.
• Used Cisco 1941 Integrated Services Routers for routers and Cisco Catalyst 2960s for switches,
referring to the Router Interface Summary Table for correct interface identifiers.
PROCEDURE:

Part 1: Build the Network and Configure Basic Device Settings:

Step 1: Cabled the network following the provided topology.

Step 2: Initialized and reloaded both the router and switches to clear any existing configurations.

Step 3: Configured basic settings for R1:

o Entered global configuration mode on R1 using Router>enable and Router#configure

terminal.
o Copied and pasted the provided basic configuration settings.
o Configured addressing on G0/0 and G0/1, and enabled both interfaces.
o Saved the configuration using R1#copy running-config startup-config.
R1 Configuration:

• Device: R1
• Interface: G0/0
• IP Address: 192.168.20.1
• Subnet Mask: 255.255.255.0
• Default Gateway: N/A
• Interface: G0/1
• IP Address: 192.168.10.1
• Subnet Mask: 255.255.255.0
• Default Gateway: N/A

Router successfully configured with the provided IP addresses on interfaces G0/0 and G0/1.

Step 4: Configured basic settings on both switches:

o Entered global configuration mode on each switch using Switch>enable and

Switch#configure terminal.
o Copied and pasted the provided basic configuration settings for each switch.
o Configured the hostname and saved the configuration.

For switch 1:
For switch 2:

Step 5: Configured basic settings on PC-A and PC-B:

PC-A Configuration:

• IP Address: 192.168.10.3
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.10.1

PC-A Configuration
PC-B Configuration:

• IP Address: 192.168.20.3
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.20.1

PC-A and PC-B successfully configured with the specified IP addresses and default gateways.

o Assigned IP addresses and default gateway addresses to PC-A and PC-B according to the
Addressing Table.

Part 2: Configure Switches with VLANs and Trunking

Step 1: Configured VLANs on S1

a. Accessed the command-line interface of S1.

Switch>enable
Switch#configure terminal
Switch(config)#

b. Created VLAN 10 and assigned the name 'Student'

Switch(config)#vlan 10
Switch(config-vlan)#name Student
c. Created VLAN 20 and assigned the name 'Faculty-Admin'.

Switch(config)#vlan 20
Switch(config-vlan)#name Faculty-Admin

d. Configured F0/1 as a trunk port.

Switch(config)#interface FastEthernet0/1
Switch(config-if)#switchport mode trunk

e. Assigned ports F0/5 and F0/6 to VLAN 10 and configured them as access ports.

Switch(config)#interface range FastEthernet0/5 - 6

Switch(config-if-range)#switchport mode access
Switch(config-if-range)#switchport access vlan 10

f. Assigned an IP address to VLAN 10 and enabled it. (Referred to the Addressing Table)

Switch(config)#interface vlan 10
Switch(config-if)#ip address 192.168.10.11 255.255.255.0
Switch(config-if)#no shutdown
Step 2: Configured VLANs on S2
a. Accessed the command-line interface of S2.
Switch>enable
Switch#configure terminal
Switch(config)#

b. Created VLAN 10 and assigned the name 'Student'.

Switch(config)#vlan 10
Switch(config-vlan)#name Student

c. Created VLAN 20 and assigned the name 'Faculty-Admin'.

Switch(config)#vlan 20
Switch(config-vlan)#name Faculty-Admin

d. Configured F0/1 as a trunk port.

Switch(config)#interface FastEthernet0/1
Switch(config-if)#switchport mode trunk

e. Assigned ports F0/11 and F0/18 to VLAN 20 and configured them as access ports.
Switch(config)#interface range FastEthernet0/11 - 18
Switch(config-if-range)#switchport mode access
Switch(config-if-range)#switchport access vlan 20

f. Assigned an IP address to VLAN 10 and enabled it. (Referred to the Addressing Table)
Switch(config)#interface vlan 10
Switch(config-if)#ip address 192.168.10.12 255.255.255.0
Switch(config-if)#no shutdown

g. Configured the default gateway according to the Addressing Table.

Switch(config)#ip default-gateway 192.168.10.1
S1 Configuration:

• VLAN: 10
• IP Address: 192.168.10.11
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.10.1

S2 Configuration:

• VLAN: 10
• IP Address: 192.168.10.12
• Subnet Mask: 255.255.255.0
• Default Gateway: 192.168.10.1

Switches S1 and S2 successfully configured with VLAN 10 and assigned IP addresses according to the
Addressing Table.
Part 3: Verified Trunking, VLANs, Routing, and Connectivity

Step 1: Verified the R1 routing table.

a) On R1, issued the show ip route command to check the listed routes.

Router#show ip route

Analyzed the displayed routes on R1.

b) On both S1 and S2, issued the show interface trunk command to verify the trunk status of F0/1.

Switch#show interface trunk

Verified that the F0/1 port on both switches was set to trunk.
 c) Issued a show vlan brief command on both S1 and S2 to check the active VLANs and port
assignments.

Switch#show vlan brief

Verified the activity of VLANs 10 and 20 and checked the correct port assignments.

Question: Why is F0/1 not listed in any of the active VLANs?

The reason F0/1 is not listed in any of the active VLANs is because it has been configured as a trunk port.
Trunk ports are used to carry traffic for multiple VLANs, and they do not belong to a specific VLAN like
access ports do. In the context of the lab instructions, F0/1 is configured as a trunk port to allow traffic for
multiple VLANs, and therefore, it is not associated with a specific VLAN in the "show vlan brief" output.

d) Performed a ping from PC-A in VLAN 10 to PC-B in VLAN 20.

C:\>ping 192.168.20.3

Checked the success of Inter-VLAN routing by ensuring successful pings between the 192.168.10.0
network and the 192.168.20.0 network.
e) Verified connectivity between devices by attempting to ping between all devices.

Checked the success of Inter-VLAN routing by ensuring successful pings between PC-A to PC-B

Checked the success of Inter-VLAN routing by ensuring successful pings between PC-B to PC-A
Ensured successful pings between all devices.

Troubleshooted in case of unsuccessful pings.

DISCUSSION

What is an advantage of using legacy inter-VLAN routing?

Legacy inter-VLAN routing offers a straightforward and cost-effective solution for network configurations.
By connecting different physical router interfaces to distinct switch interfaces, the setup is simplified,
making it ideal for smaller networks. The approach, exemplified by Router-on-a-Stick, proves compatible
with older equipment and provides fine-grained control over traffic flow through the application of access
control lists. Additionally, it enhances security by restricting communication between VLANs and offers an
efficient option for small to medium-sized networks, striking a balance between simplicity and effectiveness.

The advantages of using legacy inter-VLAN routing include:

1. Simplicity in Configuration: Legacy inter-VLAN routing involves connecting different physical

router interfaces to different physical switch interfaces, leading to a straightforward and simple
configuration process.
2. Cost-Effectiveness: Legacy inter-VLAN routing is often more cost-effective compared to newer
solutions like Layer 3 switches. It utilizes a single router interface to route traffic between VLANs,
reducing the need for expensive Layer 3 switches.
3. Compatibility with Older Equipment: Legacy inter-VLAN routing, such as Router-on-a-Stick, can
work with older network equipment that may not support newer routing protocols or Layer 3
switching.
4. Fine-Grained Control: It allows for fine-grained control over traffic flow and routing policies.
Administrators can apply access control lists (ACLs) and security policies at the router interface
level.
5. Security: VLAN routing enhances security by restricting communication between VLANs. Devices
within the same VLAN can communicate, but communication with devices in other VLANs requires
routing through a router or Layer 3 switch.
6. Ease of Configuration for Small to Medium-Sized Networks: Legacy inter-VLAN routing,
particularly Router-on-a-Stick, is simple and easy to set up, making it suitable for smaller networks.
While it may not be as scalable as modern solutions, it efficiently serves the needs of small to
medium-sized networks.

In summary, legacy inter-VLAN routing provides a balance between simplicity, cost-effectiveness, and
security, making it a viable option for certain network configurations, especially in scenarios with budget
constraints or compatibility requirements with older equipment.

CONCLUSION

In conclusion, this lab on configuring per-interface inter-VLAN routing provided valuable hands-on
experience in setting up a network infrastructure with legacy routing methods. The process involved erasing
and reloading configurations on both switches and routers, ensuring a clean slate for effective configuration.
The steps covered configuring basic device settings, creating VLANs, trunking, and verifying routing and
connectivity. Legacy inter-VLAN routing, exemplified by Router-on-a-Stick, emerged as a simple and cost-
effective solution, particularly suitable for smaller networks. Through this practical exercise, a deeper
understanding of VLANs, routing, and switch configuration was gained, reinforcing fundamental concepts in
network administration.