zNetLaB › Guided labs › Enterprise
Enterprise campus — VLANs, trunking, router-on-a-stick
Enterprise Intermediate 6 devices 5 checked tasks 80 points Plan lab
Two VLANs across a trunk, inter-VLAN routing on dot1Q sub-interfaces, and a DHCP pool per VLAN. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Two VLANs across a trunk, inter-VLAN routing on dot1Q sub-interfaces, and a DHCP pool per VLAN.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (80 points).
Network status
Devices: 2 PCs, 2 switchs, 1 router, 1 server, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. PC-Sales is a host with 10.10.10.10/24, gateway 10.10.10.1. PC-Eng is a host with 10.10.20.10/24, gateway 10.10.20.1. Gateway starts with addresses (G0/1 10.10.99.1/24). Server is a host with 10.10.99.100/24, gateway 10.10.99.1. Access-SW, Dist-SW start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
VLAN 10 and VLAN 20 exist on Access-SW (10 pts) PC-Sales port in VLAN 10, PC-Eng port in VLAN 20 (10 pts) Both switch uplinks are 802.1Q trunks (15 pts) Router sub-interfaces g0/0.10 and g0/0.20 addressed (20 pts) PC-Sales reaches the Server across VLANs (25 pts) The activity, in order
VLAN 10 and VLAN 20 exist on Access-SW Why: A port assigned to a VLAN that does not exist carries nothing. Verify with: show vlan brief PC-Sales port in VLAN 10, PC-Eng port in VLAN 20 Why: A VLAN is a separate broadcast domain; the port’s VLAN decides which devices can talk without a router. Verify with: show vlan brief Both switch uplinks are 802.1Q trunks Why: A trunk carries many VLANs over one cable, tagged with 802.1Q. Both ends must agree. Verify with: show interfaces trunk Router sub-interfaces g0/0.10 and g0/0.20 addressed Why: Each goal is a state the lab can check on the running device. Verify with: show running-config PC-Sales reaches the Server across VLANs Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.10.99.100 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Two VLANs across a trunk, inter-VLAN routing on dot1Q sub-interfaces, and a DHCP pool per VLAN.
What you will be able to do
VLAN 10 and VLAN 20 exist on Access-SW
PC-Sales port in VLAN 10, PC-Eng port in VLAN 20
Both switch uplinks are 802.1Q trunks
Router sub-interfaces g0/0.10 and g0/0.20 addressed
The network
PC, Catalyst 2960-24TT, ISR 2911, Server — 6 devices in all, already cabled.
Fa0 Fa0/1 Fa0 Fa0/2 Gi0/1 Gi0/1 Gi0/2 Gi0/0 Gi0/1 10.10.99.1/24 Fa0 PC-Sales 10.10.10.10/24 · gw 10.10.10.1 PC-Eng 10.10.20.10/24 · gw 10.10.20.1 Access-SW Dist-SW Gateway Server 10.10.99.100/24 · gw 10.10.99.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
PC-Sales PC 10.10.10.10 / 255.255.255.0 gw 10.10.10.1 PC-Eng PC 10.10.20.10 / 255.255.255.0 gw 10.10.20.1 Access-SW Catalyst 2960-24TT configure it Dist-SW Catalyst 2960-24TT configure it Gateway ISR 2911 configure it Server Server 10.10.99.100 / 255.255.255.0 gw 10.10.99.1
Cabling
PC-Sales Fa0 ↔ Access-SW Fa0/1 PC-Eng Fa0 ↔ Access-SW Fa0/2 Access-SW Gi0/1 ↔ Dist-SW Gi0/1 Dist-SW Gi0/2 ↔ Gateway Gi0/0 Gateway Gi0/1 ↔ Server Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
Gateway interface g0/1
ip address 10.10.99.1 255.255.255.0
no shutdown Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 VLAN 10 and VLAN 20 exist on Access-SW 10 On Access-SW: show vlan brief lists VLAN 10. and On Access-SW: show vlan brief lists VLAN 20. 2 PC-Sales port in VLAN 10, PC-Eng port in VLAN 20 10 On Access-SW: show vlan brief — Fa0/1 is an access port in VLAN 10. and On Access-SW: show vlan brief — Fa0/2 is an access port in VLAN 20. 3 Both switch uplinks are 802.1Q trunks 15 On Access-SW: show interfaces trunk lists Gi0/1. and On Dist-SW: show interfaces trunk lists Gi0/1. and On Dist-SW: show interfaces trunk lists Gi0/2. 4 Router sub-interfaces g0/0.10 and g0/0.20 addressed 20 Checked automatically against the device’s live state (dot1q). and Checked automatically against the device’s live state (dot1q). 5 PC-Sales reaches the Server across VLANs 25 On PC-Sales: ping 10.10.99.100 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
Access-SW vlan 10
name Sales
exit
vlan 20
name Engineering
exit
interface f0/1
switchport mode access
switchport access vlan 10
exit
interface f0/2
switchport mode access
switchport access vlan 20
exit
interface g0/1
switchport mode trunk Dist-SW vlan 10
exit
vlan 20
exit
interface g0/1
switchport mode trunk
exit
interface g0/2
switchport mode trunk Gateway interface g0/0
no shutdown
exit
interface g0/0.10
encapsulation dot1Q 10
ip address 10.10.10.1 255.255.255.0
exit
interface g0/0.20
encapsulation dot1Q 20
ip address 10.10.20.1 255.255.255.0 Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.