Narration transcript
The English narration in this video. Select a time to watch that moment.
Start with a prepared controller, a directly connected access point, and a client network.
Select the controller and open its Web UI from the device toolbar.
Check the dashboard counts before making a configuration change.
Use Monitoring to inspect the joined access point and the client list.
Choose a WLAN identifier, profile name, and the network name that clients will use.
This controller uses an existing enabled policy profile to select the client VLAN.
Correct the validation error before creating the network with a valid pre-shared key.
Check the saved network row for its security, policy profile, and enabled status.
Reopen the editor to verify that the saved key is not displayed.
For a basic edit, leaving an existing saved key blank keeps that key.
Apply the matching network name and key on the wireless client, then verify its connection in Monitoring.
The optional radio model is off, so unavailable signal values are not measurements.
Change to the second policy profile, then renew the client's address and test its new gateway.
Rotating the wireless key disconnects the old client settings until the client is updated.
Disable the WLAN to stop its client connections while keeping the profile.
Enable it again and check that the client reconnects.
An Open WLAN uses no pre-shared key in this supported lab workflow.
Remove only the training network, then reload and verify that the other profiles remain.
The second controller family uses a client VLAN field instead of a policy profile.
Create its training network with the matching VLAN and security settings.
Its editor provides separate quality-of-service and advanced forms.
Save each form, reopen it, and verify the stored values.
A saved quality-of-service choice alone does not demonstrate packet prioritization.
After a controller change, confirm both the saved profile and an actual client connection.
