Enterprise VLAN and Inter-VLAN Routing Lab

Department VLANs on access switches, 802.1Q trunks between them, and inter-VLAN routing — built and verified in a simulated environment, with the command output published as evidence.

Project
PROJECT-02
Type
Networking lab — simulated environment
Status
In progress

Objectives

  • Segment the environment into department VLANs on access switches.
  • Carry every VLAN between switches over 802.1Q trunks and confirm the allowed list.
  • Route between VLANs so each department can reach what it is entitled to reach.
  • Keep spanning tree predictable: root bridge placement, port roles and states.
  • Prove each step with command output rather than assumption.

Technologies

  • VLAN configuration
  • Access ports
  • 802.1Q trunking
  • Inter-VLAN routing
  • STP / RSTP
  • EtherChannel / LACP
  • DHCP
  • Route verification

What the lab output must show

  • VLAN to port mapping for each department, per switch.
  • Trunk status, native VLAN and allowed VLAN list on every uplink.
  • MAC address table showing expected learning per VLAN.
  • Spanning tree topology: root bridge, port roles, port states.
  • Gateway reachability for each VLAN, with the routing table that makes it work.
  • DHCP leases obtained by a client in each VLAN.
  • A deliberately broken trunk and a wrongly placed gateway, used for the troubleshooting write-ups.

Status

The lab is being built in a simulated environment. VLANs, access ports, trunks, spanning tree and the routing table are all supported there; settings-specific behaviour is confirmed per run rather than assumed. In progress

Content pending — shared topology link, configurations and command output

Added here once the run is complete and the output has been read back. No console output is written from memory or from an example found elsewhere.

Related: three-site enterprise network and the full project record.