Hands-On Lab 2-2: Multi-Floor Enterprise LAN Design and Implementation

Lab Overview

• Lab Number: 2-2
• Lab Name: Multi-Floor Enterprise LAN with Distribution and Access Switches
• Lab Difficulty: Rated 4/10
• Approximate Time: 45-60 minutes
• Preferred Image: iol-l2, iol-l3
• Lab on: Chapter 2: Fundamentals of Ethernet LANs
• Figure: 2-3 (Single-Building Enterprise Wired and Wireless LAN)

Objective

Design and implement a multi-floor enterprise LAN using access and distribution switches. Configure inter-switch trunking, verify connectivity and understand the role of trunk ports in supporting multiple VLANs.

Scenario Description

This scenario simulates a multi-floor enterprise network. Each floor has its own access switch connecting PCs and printers. The floors are interconnected via a distribution switch. The goal is to set up the network, assign IP addresses, enable trunk ports, and verify connectivity across floors.

Network Structure

• Subnet 1 (Floor 1): 192.168.1.0/24
  • Access Switch: Floor 1 Access Switch
  • PCs:
    • PC1: 192.168.1.10
    • PC2: 192.168.1.20
  • • Printer:
    • IP: 192.168.1.30
• Subnet 2 (Floor 2): 192.168.2.0/24
  • Access Switch: Floor 2 Access Switch
  • PCs:
    • PC3: 192.168.2.10
    • PC4: 192.168.2.20
  • • Printer:
    • IP: 192.168.2.30
• Distribution Layer: Distribution Router (Connecting Access Switches)

Topology Diagram

Below is the topology diagram for this lab setup:

Prerequisites

1. EVE-NG installed and operational.
2. Images for vios-l2 and vPCS are available.
3. Basic understanding of CLI commands for switches and routers.

Implementation Steps

Step 1: Set up the topology

1. Add the following devices in EVE-NG:
   • Two Access Switches (iol-l2) for Floor 1 and Floor 2.
   • One Distribution Router (iol-l3).
   • Four vPCS for PCs.
   • Two Printers (vPCS or equivalent).
2. Connect:
   • PCs and Printer1 to Floor 1 Access Switch.
   • PCs and Printer2 to Floor 2 Access Switch.
   • Interconnect the Access Switches to the Distribution Switch using trunk links.

Why this step?

This step ensures that the physical and logical connections mimic a real-world multi-floor enterprise network. Establishing the topology is critical to testing communication paths and configurations.

Step 2: Configure IP Addresses on PCs and Printers

1. Floor 1 Devices:

• PC1:

ip 192.168.1.10 255.255.255.0

• PC2:

ip 192.168.1.20 255.255.255.0

• Printer1:

ip 192.168.1.30 255.255.255.0

2. Floor 2 Devices:

• PC3:

ip 192.168.2.10 255.255.255.0

• PC4:

ip 192.168.2.20 255.255.255.0

• Printer2:

ip 192.168.2.30 255.255.255.0

Why this step?

Assigning unique IP addresses to each device ensures they can communicate within their subnets and across floors. Proper IP addressing is the foundation of network communication.

Step 3: Configure the Switches

1. Access Switches:

• Assign a hostname for each switch:

enable
configure terminal
hostname Floor1_Access

enable
configure terminal
hostname Floor2_Access

Tip

“Uplink port” refers to the port on a switch that connects to another switch, router, or higher-tier network device.

Why this step?

Assigning hostnames makes it easier to identify switches during configuration and troubleshooting.

2. Distribution Router:

• Router configuration:

Router>enable
Router#configure terminal
Router(config)#hostname Distribution-R
Distribution-R(config)#int ethernet0/0
Distribution-R(config-if)#ip address 192.168.1.1 255.255.255.0
Distribution-R(config-if)#description uplink-port-floor1
Distribution-R(config-if)#no shutdown
Distribution-R(config-if)#exit
Distribution-R(config)#
Distribution-R(config)#interface e0/1
Distribution-R(config-if)#ip address 192.168.2.1 255.255.255.0
Distribution-R(config-if)#description uplink-port-floor2
Distribution-R(config-if)#no shutdown
Distribution-R(config-if)#exit
Distribution-R(config)#

Tip

Assign a routers ports ip will enable routing between other segmants.

Why this step?

This step allows routing between the subnets on each floor by enabling IP addresses on the router’s interfaces and activating them. The router acts as the default gateway for each floor.

Step 4: Verify Connectivity

1. Ping between devices on the same floor:

• From PC1 to PC2:

ping 192.168.1.20

• From PC3 to PC4:

ping 192.168.2.20

Why this step?

This step verifies that devices within the same subnet can communicate, ensuring the Access Switch configurations are correct.

2. Ping between devices on different floors:

• From PC1 to PC3:

ping 192.168.2.10

Why this step?

Testing inter-floor communication ensures that routing between subnets is configured properly on the Distribution Router and that trunking links are functional.

Verification & Testing

1. Check Router Ports IPs:

show ip interface brief

Tip

If devices across floors cannot communicate, verify that the ip ports are operational. Misconfigured router ports are a common cause of inter-switch communication failure.

2. Ping Devices:

• Verify that devices can communicate within their respective subnets and across floors.

Key Commands

• Assign hostname:
  • hostname <name>
• Enable IP routing on router ports:
  • interface <interface>
  • ip address <ip, subnet mask>
  • no shutdown
• Test connectivity:
  • ping <Destination IP>

Troubleshooting Tips

• If devices cannot communicate across floors:
  • Check if trunking is enabled on uplink ports.
  • Use show interfaces trunk to verify trunk status.

Tip

Ensure each device has the correct IP configuration and belongs to the correct subnets are introduced.

Key Takeaways

• Understand the importance of trunking in inter-switch communication.
• Learn how the switchport mode trunk command enables the port to carry traffic for multiple VLANs.
• Use verification commands like show interfaces trunk to troubleshoot trunk-related issues.

Common Pitfalls

• Forgetting to enable trunk mode on uplink ports.
• Misconfiguring IP addresses or subnets.
• Not activating ports with no shutdown.

Validation Checklist

1. Trunk ports are operational between switches.
2. Devices within the same floor can communicate.
3. Devices across floors can communicate.

Lab Notes

• Extra Tip: Always verify trunk configuration using show interfaces trunk before testing inter-switch connectivity.
• This lab can be extended by introducing VLANs for better segmentation and security.