Home > > > CCNA 200-301 Course Labs: Practical Exercises for Routing, Switching, and VLANs

CCNA 200-301 Course Labs: Practical Exercises for Routing, Switching, and VLANs

Author : mahesh 2003 | Published On : 05 Nov 2026

 

The practical lab component is where theoretical knowledge transforms into actual engineering competence for the Cisco CCNA Certification exam. While multiple-choice questions test your conceptual memory, hands-on labs train your reflexes for configuration syntax, troubleshooting error states, and verifying connectivity across complex topologies.

Router-on-a-stick and VLAN trunking architecture for CCNA practical labs. Source: Made with Google AI

Essential Lab Environments for CCNA 200-301

Before diving into specific exercises, you will need a reliable lab environment to execute Cisco IOS commands:

  • Cisco Packet Tracer: The premier free simulation tool provided by Cisco, ideal for building switches, routers, end-hosts, and basic wireless components without requiring physical hardware.

  • GNS3 / EVE-NG: Advanced network emulation platforms that run real Cisco IOS software images (like IOSv and IOSvL2), offering a closer replication of enterprise production environments.

Core Lab Exercises to Master

1. VLANs and Trunking Configuration

Virtual Local Area Networks (VLANs) segment broadcast domains within a Layer 2 switch environment. A foundational lab should simulate a multi-department office layout.

  • Key Tasks:

    • Create and name VLANs across multiple switches (vlan 10, name Engineering).

    • Assign access ports to specific VLANs (switchport mode access, switchport access vlan 10).

    • Configure IEEE 802.1Q trunk links between switches to carry multi-VLAN traffic (switchport mode trunk, switchport trunk allowed vlan).

  • Verification Commands: show vlan brief, show interfaces trunk.

2. Inter-VLAN Routing (Router-on-a-Stick)

By default, devices in different VLANs cannot communicate without a Layer 3 device. A "Router-on-a-Stick" lab connects a switch trunk port to a single physical router interface divided into virtual sub-interfaces.

  • Key Tasks:

    • Configure the switch port facing the router as an 802.1Q trunk.

    • On the router, configure sub-interfaces corresponding to each VLAN (interface GigabitEthernet0/0.10).

    • Enable encapsulation with the target VLAN ID (encapsulation dot1q 10).

    • Assign the default gateway IP address for that subnet and enable proxy ARP if required (ip address 192.168.10.1 255.255.255.0).

  • Verification Commands: show ip route, show ip interface brief, ping across subnets.

3. Layer 2 Security: Spanning Tree Protocol (STP) & Port Security

Preventing switching loops and mitigating unauthorized physical access are critical operational skills.

  • Key Tasks:

    • STP Optimization: Manually configure the primary and secondary root bridges for your VLANs (spanning-tree vlan 1 root primary) to ensure deterministic path selection rather than relying on default bridge IDs.

    • Port Security: Restrict physical switch ports to specific MAC addresses, configure violation modes (protect, restrict, shutdown), and enable PortFast / BPDU Guard on edge ports connected to end-user workstations.

  • VerificationCommands: show spanning-tree, show port-security interface.

4. Static Routing and Basic OSPF Lab

Transitioning from local switching to internetwork routing requires setting up clear routing paths between multiple routers.

  • Key Tasks:

    • Configure static and default routes between branch routers and a central headquarters router.

    • Initialize single-area OSPFv2 across a multi-router topology, ensuring router IDs are set, wildcard masks are accurately calculated, and interfaces are properly assigned to Area 0.

    • Configure passive interfaces on router ports facing end-user LANs to suppress unnecessary OSPF hello packets.

  • Verification Commands: show ip route, show ip ospf neighbor, show ip ospf interface brief.

Best Practices for CCNA Lab Setup Success

  • Always Save Configurations: Make it a habit to type write memory or copy running-config startup-config after every successful module configuration to avoid losing work during emulated crashes.

  • Isolate Troubleshooting Steps: If pings fail, break the path down systematically: Check physical link lights, verify interface states (no shutdown), confirm VLAN assignments, check trunk encapsulation, and finally inspect routing tables.