WEBVTT

1
00:00:00.100 --> 00:00:08.100
Start with a prepared controller, a directly connected access point, and a client network.

2
00:00:12.450 --> 00:00:19.450
Select the controller and open its Web UI from the device toolbar.

3
00:00:21.100 --> 00:00:26.600
Check the dashboard counts before making a configuration change.

4
00:00:27.650 --> 00:00:34.650
Use Monitoring to inspect the joined access point and the client list.

5
00:00:47.350 --> 00:00:55.350
Choose a WLAN identifier, profile name, and the network name that clients will use.

6
00:00:55.400 --> 00:01:02.900
This controller uses an existing enabled policy profile to select the client VLAN.

7
00:01:04.700 --> 00:01:12.200
Correct the validation error before creating the network with a valid pre-shared key.

8
00:01:17.250 --> 00:01:24.750
Check the saved network row for its security, policy profile, and enabled status.

9
00:01:27.750 --> 00:01:34.750
Reopen the editor to verify that the saved key is not displayed.

10
00:01:37.700 --> 00:01:45.200
For a basic edit, leaving an existing saved key blank keeps that key.

11
00:02:08.550 --> 00:02:18.050
Apply the matching network name and key on the wireless client, then verify its connection in Monitoring.

12
00:02:18.150 --> 00:02:25.650
The optional radio model is off, so unavailable signal values are not measurements.

13
00:02:39.000 --> 00:02:48.000
Change to the second policy profile, then renew the client's address and test its new gateway.

14
00:03:17.000 --> 00:03:25.000
Rotating the wireless key disconnects the old client settings until the client is updated.

15
00:03:28.650 --> 00:03:35.650
Disable the WLAN to stop its client connections while keeping the profile.

16
00:03:36.650 --> 00:03:42.150
Enable it again and check that the client reconnects.

17
00:04:11.300 --> 00:04:18.300
An Open WLAN uses no pre-shared key in this supported lab workflow.

18
00:04:42.350 --> 00:04:50.350
Remove only the training network, then reload and verify that the other profiles remain.

19
00:04:56.700 --> 00:05:04.700
The second controller family uses a client VLAN field instead of a policy profile.

20
00:05:16.600 --> 00:05:23.100
Create its training network with the matching VLAN and security settings.

21
00:05:25.800 --> 00:05:31.400
Its editor provides separate quality-of-service and advanced forms.

22
00:05:47.050 --> 00:05:53.050
Save each form, reopen it, and verify the stored values.

23
00:05:53.100 --> 00:05:59.700
A saved quality-of-service choice alone does not demonstrate packet prioritization.

24
00:06:22.250 --> 00:06:30.250
After a controller change, confirm both the saved profile and an actual client connection.