zNetLaB › Guided labs › Enterprise
Wireless — a WLAN, an AP that joins, and a client in its VLAN
Enterprise Intermediate 7 devices 5 checked tasks 100 points Plan lab
A controller, two access points and two clients. Build a WLAN with a client VLAN and a pre-shared key, join the clients to it, and prove the wireless host is simply a host in that VLAN — same trunk, same SVI, same everything. 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
A controller, two access points and two clients. Build a WLAN with a client VLAN and a pre-shared key, join the clients to it, and prove the wireless host is simply a host in that VLAN — same trunk, same SVI, same everything.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (100 points).
Network status
Devices: 1 switch, 4 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. SW1 starts with addresses (V20 10.20.0.1/24) and VLAN 20 already configured. Wired-PC is a host with 10.20.0.10/24, gateway 10.20.0.1. WLC1, AP1, AP2, Tablet-1 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
Both access points have joined the controller (15 pts) An enabled WLAN broadcasts CORP-WIFI in client VLAN 20 (25 pts) …and it is protected with a pre-shared key (15 pts) Both clients are associated to it (25 pts) A client landed in VLAN 20, not VLAN 1 (20 pts) The activity, in order
Both access points have joined the controller Why: Each goal is a state the lab can check on the running device. Verify with: show running-config An enabled WLAN broadcasts CORP-WIFI in client VLAN 20 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config …and it is protected with a pre-shared key Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Both clients are associated to it Why: Each goal is a state the lab can check on the running device. Verify with: show running-config A client landed in VLAN 20, not VLAN 1 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config 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
A controller, two access points and two clients. Build a WLAN with a client VLAN and a pre-shared key, join the clients to it, and prove the wireless host is simply a host in that VLAN — same trunk, same SVI, same everything.
What you will be able to do
Both access points have joined the controller
An enabled WLAN broadcasts CORP-WIFI in client VLAN 20
…and it is protected with a pre-shared key
Both clients are associated to it
The network
Catalyst 9300-24, Catalyst 9800-L, Catalyst CW9176I, Catalyst 9166I, Laptop, Tablet, PC — 7 devices in all, already cabled.
Gi1/0/1 Gi0/0/0 Gi1/0/2 Gi0 Gi1/0/3 Gi0 Gi1/0/10 Fa0 Wireless0 Wireless0 Wireless0 Wireless0 SW1 WLC1 AP1 AP2 Laptop-1 Tablet-1 Wired-PC 10.20.0.10/24 · gw 10.20.0.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
SW1 Catalyst 9300-24 configure it WLC1 Catalyst 9800-L configure it AP1 Catalyst CW9176I configure it AP2 Catalyst 9166I configure it Laptop-1 Laptop configure it Tablet-1 Tablet configure it Wired-PC PC 10.20.0.10 / 255.255.255.0 gw 10.20.0.1
Cabling
SW1 Gi1/0/1 ↔ WLC1 Gi0/0/0 SW1 Gi1/0/2 ↔ AP1 Gi0 SW1 Gi1/0/3 ↔ AP2 Gi0 SW1 Gi1/0/10 ↔ Wired-PC Fa0 AP1 Wireless0 ↔ Laptop-1 Wireless0 AP2 Wireless0 ↔ Tablet-1 Wireless0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
SW1 vlan 20
name WIFI
exit
interface range GigabitEthernet1/0/2 - 3
switchport trunk encapsulation dot1q
switchport mode trunk
exit
interface GigabitEthernet1/0/10
switchport mode access
switchport access vlan 20
exit
ip routing
interface Vlan20
ip address 10.20.0.1 255.255.255.0
no shutdown
exit 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 Both access points have joined the controller 15 Checked automatically against the device’s live state (apJoined). and Checked automatically against the device’s live state (apJoined). 2 An enabled WLAN broadcasts CORP-WIFI in client VLAN 20 25 Checked automatically against the device’s live state (wlanUp). 3 …and it is protected with a pre-shared key 15 Checked automatically against the device’s live state (wlanSecured). 4 Both clients are associated to it 25 Checked automatically against the device’s live state (wifiAssoc). and Checked automatically against the device’s live state (wifiAssoc). 5 A client landed in VLAN 20, not VLAN 1 20 Checked automatically against the device’s live state (wifiVlan).
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:
WLC1 wireless mobility group name CAMPUS
wlan CORP 1 CORP-WIFI
client vlan 20
security wpa wpa2
security wpa akm psk
security wpa psk set-key ascii 0 znetlab2026
no shutdown
exit Laptop-1 netsh wlan connect ssid=CORP-WIFI key=znetlab2026 Tablet-1 netsh wlan connect ssid=CORP-WIFI key=znetlab2026 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.