Configure access points

In this overview, all the existing access points should be marked as Found . If this is not the case, we recommend that you take another look at the DHCP server settings on the branch office router. You should check, particularly, whether the CAPWAP option has been set up correctly. The VPN network connection from head office to the branch office may also be the cause of the fault. If these can be ruled out as the cause of the fault, an accidentally activated DHCP server on a device in the branch office may be causing the problem. This server must be deactivated and all the access points in the branch office disconnected from the mains in order to get a fresh network configuration from the DHCP server. Another alternative is to wait for the so-called DHCP Lease Time to expire.

Now the wireless and VSS profiles that were set up previously can be set up on the access points that have been found. We shall now describe how to modify an access point for the location »Nbg - Shop«.

Go to Wireless LAN Controller -> Slave AP Configuration-> Slave Access Points .

A name that is as unambiguous as possible should be given as the Location, e. g. Nbg - Shop .
It is essential that the wireless module's Operation Mode is left as On . This means that the wireless module profile being used determines the operating mode.
Next the 2.4 GHz Radio Profile that was configured previously is selected to be the Active Radio Profile.
The Channel is left as Auto so that it is determined dynamically using the wireless profile's channel plan and the WLAN environment.
Lastly, under Assigned Wireless Networks (VSS) and using the Add button, the wireless network Staff that has been configured is assigned to the wireless module.
The other settings are applied as they are. Confirm with OK.

	Note
	If an access point has two wireless modules, two configuration masks appear for Wireless Module 1 and Wireless Module 2. They are set in the same way as in the previous example.

The other access points in the overview list are configured in exactly the same way as the first one was. Just one unique location name must be given to each access point, otherwise there is no longer any way to distinguish between the access points, e. g. when doing the WLAN network monitoring (in the menu Wireless LAN Controller ->Monitoring).

Once the access points have all been set up, they are given the status Managed in the overview under Wireless LAN Controller ->Slave AP configuration-> Slave Access Points, so they are now live. The WLAN controller is also blocking them against any sort of external configuration access.

Choose whether the selected Access Pont is to be managed by the WLAN Controller by clicking the

button or the

button in the Action column.

You can disconnect the Access Point from the WLAN Controller and therefore remove it from your WLAN infrastructure by click on the

button. The Access Point then receives the Discovered status, but is no longer Managed .

However, the WLAN channels shown in the menu (Wireless LAN Controller ->Slave AP configuration -> Slave Access Points) may not be ideal, e. g. in terms of one channel being assigned more than once. While being taken up and running, the access points were only able to tune into the general WLAN environment, not to each other. There are two ways of correcting this retrospectively: Either by using the START button to triggeri the New channel setting action for all the managed access points at every location, or by triggering the channel search specifically for one affected access point by clicking the Refresh symbol in the Channel search column.

When the channel setting is complete, adjacent access points at any location ought to transmit on different channels.