Employees associate to a campus WLAN and never get an address. The SSID is on the policy tag, and the client VLAN that the policy profile names is shut down on the controller's switch. What is broken?
Select an answer to reveal the explanation.
Short Explanation
Your SSID is present, but the network underneath it is switched off. Bring up the client VLAN so your associated clients have somewhere to request an address.
Full Explanation
Association gets a client onto the WLAN, but the address comes from the VLAN named in the policy profile. That client VLAN is shut down on the controller’s switch, so an associated client has nowhere to request an address. The SSID is on the policy tag, which is why clients can associate; a shut VLAN does not remove the SSID name from beacons. The claim that the country code is unset because the controller stores it through a shut VLAN confuses unrelated settings: country code is a regulatory setting, not something a VLAN stores. The claim that band select causes the failure also confuses unrelated behavior: band select steers capable clients between bands; it does not shut a VLAN or steer clients to a band without DHCP. The client VLAN being shut is the fault, so bring it up. Exam caveat: an up VLAN with no DHCP helper can produce the same symptom, so confirm a scope or helper answers after bringing the VLAN up. Practical check: no-shut the client VLAN, renew a test client, and verify that its address lands in that VLAN; check one live client before changing anything else on the floor.