Live Virtual Machine Lab 7.2 Module 07: Configuring Switching Features
Introduction
The Live Virtual Machine Lab 7.Day to day, in this lab, learners work inside a virtual machine environment that replicates real-world enterprise network infrastructure, allowing them to practice essential switching concepts without requiring physical hardware. Practically speaking, this module is a critical component of many IT and networking curricula, particularly those aligned with Cisco Networking Academy or similar structured learning paths. In practice, the module focuses on key switching technologies such as VLANs (Virtual Local Area Networks), trunking, Spanning Tree Protocol (STP), port security, and VTP (VLAN Trunking Protocol). 2 Module 07 is a hands-on networking exercise designed to give students practical experience in configuring and managing switching features within a simulated network environment. Plus, understanding these features is fundamental for anyone pursuing a career in network administration, cybersecurity, or systems engineering. By the end of this module, students should be able to configure, verify, and troubleshoot switching operations in a controlled lab setting, building the skills needed to manage production networks confidently.
Understanding the Virtual Machine Lab Environment
Before diving into the switching features themselves, it actually matters more than it seems. The Live Virtual Machine Lab 7.2 provides a pre-configured virtualized network topology that typically includes multiple virtual switches, routers, and end-user devices. That's why these components are simulated using software such as Cisco Packet Tracer, GNS3, or a dedicated virtual lab platform provided by your educational institution. The virtual machines emulate real networking hardware, meaning that all commands, configurations, and troubleshooting procedures you perform in the lab are directly transferable to physical equipment in a real data center or enterprise office.
The virtual lab environment is designed to be safe and forgiving. In practice, you can make mistakes, break configurations, and start over without any risk of disrupting a live production network. In practice, this is one of the greatest advantages of using a live virtual machine lab — it bridges the gap between theoretical knowledge and practical application. In Module 07, the topology usually includes at least two or three managed switches connected together, several PCs or end devices assigned to different VLANs, and trunk links connecting the switches. The goal is to simulate a realistic small-to-medium business network where switching features must be properly configured for traffic to flow correctly and securely.
Quick note before moving on.
Core Switching Features Covered in Module 07
Module 07 of the Live Virtual Machine Lab 7.2 covers several essential switching features that form the backbone of modern LAN (Local Area Network) design. Each of these features plays a specific role in how traffic is managed, segmented, and secured within a switched network Surprisingly effective..
VLAN Configuration
Virtual Local Area Networks (VLANs) are one of the most important concepts in modern switching. A VLAN allows you to logically segment a single physical switch into multiple separate broadcast domains. Without VLANs, every device connected to a switch would be in the same broadcast domain, meaning that broadcast traffic from one device would reach every other device on the network. This creates unnecessary congestion and security risks. In this module, you will learn how to create VLANs on a switch, assign ports to specific VLANs, and verify that traffic is properly isolated between VLANs. Take this: you might configure VLAN 10 for the Accounting department, VLAN 20 for Engineering, and VLAN 30 for Guest access. Devices in VLAN 10 cannot directly communicate with devices in VLAN 20 unless a Layer 3 device (such as a router or Layer 3 switch) is used to route traffic between them.
Trunking
Trunking is the mechanism by which VLAN information is carried across links between switches. A trunk port is configured to carry traffic for multiple VLANs simultaneously over a single physical link. This is essential in networks where switches are interconnected and devices in the same VLAN may be connected to different switches. In the lab, you will configure trunk ports using the IEEE 802.1Q standard, which adds a VLAN tag to each Ethernet frame to identify which VLAN the frame belongs to. You will also learn how to verify trunk status, check which VLANs are allowed on a trunk, and troubleshoot common trunking issues such as mismatched native VLAN configurations or disabled trunking on one end of the link Worth keeping that in mind..
Spanning Tree Protocol (STP)
Spanning Tree Protocol is a Layer 2 protocol that prevents network loops in switched environments. When multiple switches are interconnected, there is a risk of creating redundant paths that can cause broadcast storms, MAC address table instability, and network outages. STP solves this problem by logically blocking redundant paths and maintaining only one active path between any two network devices. In Module 07, you will configure and observe STP operations, including understanding root bridge election, port roles (root, designated, blocking), and port states (blocking, listening, learning, forwarding). You may also explore Rapid Spanning Tree Protocol (RSTP), which provides faster convergence times compared to the original STP standard Simple, but easy to overlook..
Port Security
Port security is a switching feature that restricts the MAC addresses allowed on a specific switch port. This is a critical security measure that helps prevent unauthorized devices from connecting to the network. In the lab, you will configure port security to limit the number of MAC addresses that can be learned on a given port, set the violation mode (shutdown, restrict, or protect), and observe what happens when a violation occurs. Here's one way to look at it: if a port is configured to allow only one MAC address and a second device is connected, the switch can either shut down the port entirely or log the violation while still allowing traffic from the original device Practical, not theoretical..
VLAN Trunking Protocol (VTP)
VTP is a Cisco proprietary protocol that simplifies VLAN management across multiple switches in a network. Instead of manually creating and deleting VLANs on every switch, VTP allows you to manage VLANs from a single switch (the VTP server) and have those changes propagated to all other switches in the same VTP domain. In this module, you will configure VTP server, client, and transparent modes, set the VTP domain name and password, and verify that VLAN information is being synchronized correctly across the network.
Step-by-Step Guide to Configuring Switching Features in the Lab
Configuring switching features in the Live Virtual Machine Lab follows a systematic process. Below is a general step-by-step breakdown of the workflow you will encounter in Module 07 It's one of those things that adds up. But it adds up..
Step 1: Access the Virtual Switch. Open your virtual lab environment and launch a terminal or console session on the first switch in the topology. Use the appropriate console cable simulation or SSH/Telnet connection provided by the lab platform.
Step 2: Enter Global Configuration Mode. From the privileged EXEC mode, enter global configuration mode by typing configure terminal. This is where you will begin entering all switching commands.
Step 3: Create VLANs. Use the vlan <number> command followed by name <vlan-name> to create each required VLAN. Here's one way to look at it: vlan 10 followed by name Accounting creates VLAN 10 with the name Accounting.
Step 4: Assign Access Ports to VLANs. manage to each interface that connects to an end device and assign it to the appropriate VLAN using the switchport mode access and `
Step 4 – Assign Access Ports to VLANs
Enter interface configuration mode for the port that connects to an end‑device and issue the following commands:
interface GigabitEthernet0/2
switchport mode access ! ensures the port operates as an access link
switchport access vlan 10 ! places the port in VLAN 10 (Accounting)
switchport nonegotiate ! disables DTP on a pure access port
Repeat the process for each host‑connected interface, using the VLAN number that corresponds to the user’s department or function. If a port must remain free for future use, you can add the switchport protected command; this prevents the port from learning any MAC addresses while still allowing traffic to pass That's the part that actually makes a difference..
Step 5 – Configure Trunk Links
Links that carry multiple VLANs between switches must be set to trunk mode. On each participating interface run:
interface GigabitEthernet0/1
switchport mode trunk ! enables trunking
switchport trunk allowed vlan 10,20,30 ! list only the VLANs you intend to transport
switchport nonegotiate ! suppresses DTP on a dedicated trunk
If you need to permit all VLANs, use switchport trunk allowed vlan all. Verify the trunk’s status with show interfaces trunk; the output will list the native VLAN (default 1) and the allowed VLAN set.
Step 6 – Verify VLAN Configuration
Use the following privileged‑EXEC commands to confirm that the VLANs exist and that ports are correctly associated:
show vlan brief ! displays VLAN IDs, names, and member ports
show interfaces status ! shows which ports are in access or trunk mode
show running-config interface Gi0/2 ! checks the exact configuration applied to a specific port
If any port shows an unexpected VLAN or mode, adjust the configuration and re‑verify until the output matches the design And that's really what it comes down to..
Step 7 – Enable Rapid Spanning Tree Protocol (RSTP)
To achieve faster reconvergence after a topology change, issue:
spanning-tree mode rapid-pvst ! activates RSTP (Rapid PVST+) on the switch
Optionally, you can set the priority of the switch to influence the root bridge election:
spanning-tree vlan 10 priority 4096 ! lower value makes the switch more likely to become root for VLAN 10
Verify the RSTP state with:
show spanning-tree summary
show spanning-tree
These commands display the current root bridge, port roles, and timers, confirming that the network is operating under RSTP rather than the legacy STP And that's really what it comes down to. But it adds up..
Step 8 – Test Redundancy and Convergence
Introduce a temporary change—such as disabling a redundant uplink or unplugging a connected host—and observe the switching behavior. Use show spanning-tree repeatedly to watch the port transition from blocking to forwarding and note the convergence time. In a properly tuned RSTP environment, the transition should occur in seconds rather than the dozens of seconds typical of classic STP.
Step 9 – Implement Port Security
Secure each access port by limiting the number of MAC addresses it can learn:
interface GigabitEthernet0/2
switchport port-security ! enable the feature
switchport port-security maximum 1 ! allow only one MAC address
switchport port-security violation shutdown ! shut down the port on a violation
switchport port-security mac-address sticky ! dynamically learn the first MAC and store it in the config
After configuring, verify the binding with:
show port-security interface Gi0/2
Attempting to connect a second device should trigger the defined violation mode, protecting the network from rogue devices.
Step 10 – Configure VTP
First, decide which switch will act as the VTP server. On that device:
vtp domain lab1
vtp password Cisco123! ! set a password for authentication
vtp version 2 ! use VTP 2 for enhanced functionality
Assign the server role (if not already) and then configure the remaining switches as clients:
interface GigabitEthernet0/5
switchport mode access
switchport access vlan 1 ! place the interface in the default VLAN temporarily
switchport nonegotiate
On each client, set the VTP mode:
switchport mode vtp client ! tells the switch to listen to VTP updates
Verify the domain and mode status with:
show vtp status
show vtp interface Gi0/5
Create a new VLAN on the server (e.g., VLAN 40 – Guest) and confirm that the change propagates to all clients automatically. Use show vlan brief on each switch to verify synchronization Small thing, real impact..
Step 11 – Troubleshoot Common Issues
- VLAN mismatch: If a trunk shows “trunking allowed VLANs” that do not include a particular VLAN, the VLAN will be absent on the remote side. Ensure the allowed‑VLAN list matches the intended set on both ends.
- RSTP convergence delays: Verify that all switches run the same RSTP mode (rapid‑pvst) and that no legacy STP instances are active.
- Port‑security violations: Check the error counters with
show port-security statistics; a high count may indicate a mis‑configured device or a cable issue.
Step 12 – Document the Configuration
Finally, export the running configuration to a text file and store it in a version‑controlled repository. Use commands such as:
copy running-config startup-config ! ensure the config persists after reload
A well‑documented configuration simplifies future troubleshooting and provides a baseline for network audits.
Conclusion
The lab exercise demonstrates how a series of interrelated switching features—VLAN segmentation, trunking, Rapid Spanning Tree, port security, and VTP—work together to create a secure, resilient, and easily manageable LAN. Mastery of these tasks not only prepares technicians for real‑world deployments but also establishes a solid foundation for more advanced topics such as EtherChannel, QoS, and network automation. Also, by systematically assigning access ports, establishing trunk links, enabling rapid convergence, enforcing MAC‑address limits, and centralizing VLAN administration, network engineers can prevent unauthorized devices, minimize downtime, and streamline configuration across distributed switches. Continued practice, documentation, and testing are essential to maintain a reliable switching environment as the network evolves And that's really what it comes down to..
