Single Point Setup Overview
Single Point Setup provides a centralized method to administer and control wireless services across multiple devices. You use Single Point Setup to create a single group, or cluster, of wireless devices. After the WAP devices are clustered, you can view, deploy, configure, and secure the wireless network as a single entity. After a wireless cluster is created, Single Point Setup also facilitates channel planning across your wireless services to reduce radio interference and maximize bandwidth on the wireless network.
When you first set up your WAP device, you can use the Setup Wizard to configure Single Point Setup or join an existing Single Point Setup. If you prefer not to use the Setup Wizard, you can use the web-based configuration utility.
Managing Single Point Setup Across Access Points
Single Point Setup creates a dynamic, configuration-aware cluster, or group, of WAP devices in the same subnet of a network. A cluster supports a group of up to 16 configured WAP581 devices, but no other non-WAP581 models in the same cluster.
![]() Note |
Ensure that the PID is exactly the same in order for the device to cluster. For example: The WAP581-C-K9 will not cluster with the WAP581-E-K9 or any other WAP. |
Single Point Setup allows the management of more than one cluster in the same subnet or network; however, they are managed as single independent entities. The following table shows the wireless service limits of a Single Point Setup:
Group/Cluster Type |
WAP Devices per Single Point Setup |
Number of Active Clients per Single Point Setup |
Maximum Number of Clients (Active and Idle) |
---|---|---|---|
Cisco WAP581 |
16 |
960 for the WAP581 with a dual radio |
2048 for the WAP581 with a dual radio |
A cluster can propagate configuration information, such as VAP settings, the QoS queue parameters, and the radio parameters. When you configure Single Point Setup on a device, settings from that device (whether they are manually set or set by default) are propagated to other devices as they join the cluster.
To form a cluster, make sure the following prerequisites or conditions are met:
Procedure
Step 1 |
Plan your Single Point Setup cluster. Be sure that two or more WAP devices that you want to cluster are the same model. For example, Cisco WAP581 devices can only cluster with other Cisco WAP581 devices.
|
||
Step 2 |
Set up the WAP devices that will be clustered on the same IP subnet and verify that they are interconnected and accessible across the switched LAN network. |
||
Step 3 |
Enable Single Point Setup on all WAP devices. See Access Points for more information. |
||
Step 4 |
Verify that all WAP devices reference the same Single Point Setup name. See Access Points for more information. |
Single Point Setup Negotiation
When a AP is enabled and configured for Single Point Setup, it begins sending periodic advertisements every 10 seconds to announce its presence. If there are other WAP devices that match the criteria for the cluster, arbitration begins to determine which WAP device will distribute the master configuration to the rest of the members of the cluster.
The following rules apply to Single Point Setup cluster formation and arbitration:
-
For existing Single Point Setup clusters, whenever the administrator updates the configuration of any member of the cluster, the configuration change is propagated to all members of the cluster, and the configured WAP device assumes control of the cluster.
-
When two separate Single Point Setup clusters join into a single cluster, then the latest modified cluster wins arbitration of the configuration and overwrites and updates the configuration of all clustered WAP devices.
-
If a WAP device in a cluster does not receive advertisements from a WAP device for more than 60 seconds (for example, if the device loses connectivity to other devices in the cluster), the device is removed from the cluster.
-
If a WAP device in Single Point Setup mode loses connectivity, it is not immediately dropped from the cluster. If it regains connectivity and rejoins the cluster without having been dropped, and configuration changes were made to that device during the lost connectivity period, the changes are propagated to the other cluster members when connectivity resumes.
-
If a WAP device in a cluster loses connectivity, is dropped, later rejoins the cluster, and configuration changes were made in the during the lost connectivity period, the changes are propagated to the device when it rejoins. If there are configuration changes in both the disconnected device and the cluster, then the device with the greatest number of changes and, secondarily, the most recent change, will be selected to propagate its configuration to the cluster. (That is, if WAP1 has more changes, but WAP2 has the most recent change, WAP1 is selected. If they have an equal number of changes, but WAP2 has the most recent change, then WAP2 is selected.)
Operation of a Device Dropped From a Single Point Setup
When a WAP device that was previously a member of a cluster becomes disconnected from the cluster, the following guidelines apply:
-
The loss of contact with the cluster prevents the WAP device from receiving the latest operational configuration settings. The disconnection results in a halt to proper seamless wireless service across the production network.
-
The WAP device continues to function with the wireless parameters that it last received from the cluster.
-
The wireless clients associated with the non-clustered WAP device continue to associate with the device with no interruption of the wireless connection. In other words, the loss of contact with the cluster does not necessarily prevent the wireless clients associated with that WAP device from continued access to network resources.
-
If the loss of contact with the cluster is due to a physical or logical disconnection with the LAN infrastructure, the network services out to the wireless clients may be impacted depending on the nature of the failure.
Configuration Parameters Propagated and Not Propagated to Single Point Setup Access Points
The following table summarizes the configurations that are shared and propagated among all clustered WAP devices:
Common Configuration Settings and Parameters that are Propagated in Single Point Setup |
|
---|---|
Access Control |
Password Complexity |
Client QoS |
User Accounts |
Email Alert |
QoS |
HTTP/HTTPs Service (Except SSL Certificate Configuration) |
Radio Settings Including TSPEC Settings (Some exceptions) |
Log Settings |
Rogue AP Detection |
Client Filter |
Scheduler |
Management Access Control |
SNMP and SNMPv3 |
Networks |
WPA-PSK Complexity |
Time Settings |
Cisco Umbrella (Except Device Tag) |
LLDP (Except POE Priority Configuration) |
PnP (Plug and Play) |
Radio Configuration Settings and Parameters that are Propagated in Single Point Setup |
|
Wireless Network Mode |
|
Fragmentation Threshold |
|
RTS Threshold |
|
Rate Sets |
|
Channel |
|
Protection |
|
Fixed Multicast Rate |
|
Broadcast or Multicast Rate Limiting |
|
Wireless Band Selection |
|
Short Guard Interval Supported |
|
Radio Configuration Settings and Parameters that are Not Propagated in Single Point Setup |
|
Channel |
|
Beacon Interval |
|
DTIM Period |
|
Maximum Stations |
|
Transmit Power |
|
Other Configuration Settings and Parameters that are Not Propagated in Single Point Setup |
|
Utilization Threshold |
Port Settings |
Bonjour |
VLAN and IPv4 |
IPv6 Address |
Bridge |
IPv6 Tunnel |
Packet Capture |