
Configuring the Wireless AP
Configuring an AP Cluster
SCALANCE WLC711
User Guide, V8.11, 07/2012, C79000-G8976-C260-03 3-75
If you have not configured synchronization, you must configure the foreign controller to ensure
that all AP radios in the load balance group have the same WLAN services assigned before the AP
fails over, as originally configured for the load group. If the WLAN services assigned do not
match when an AP fails over, the affected AP radios will be removed from the load group. If you
change the WLAN services to match after the AP fails over, the AP radios still will not be allowed
to be in the load group. You must reconnect the AP to the home controller to have the radios
become part of the load group again.
Load Balance Group Statistics
You can view load balance group statistics through the Active Wireless Load Groups report. For
more information, see “Viewing Load Balance Group Statistics” on page 16-6.
Configuring an AP Cluster
APs operating in both fit mode and standalone mode operate in a cluster setup. A cluster is a
group of Wireless APs configured to communicate with each other. Mobile users (MU) can
seamlessly roam between the APs participating in the cluster. The Siemens Wireless AP extends
basic cluster functionality with the following enhancements:
• Support for fast roaming
• Automatic Channel Selection (ACS) for all APs in the cluster
• Cluster member information is available to the user
• MU statistic history
• Pre-authentication
A cluster forms when APs operating are within the same subnet and multicast and IGMP
snooping are enabled. The APs in the cluster use a default cluster ID (shared secret) or a cluster ID
that you assign.
An AP cluster can exist at any point in your network. Each cluster member periodically (30
seconds) sends a secure SIAPP (Siemens Inter-AP Protocol) multicast message to update other
cluster members. The SIAPP message includes:
• The AP name
• The AP Ethernet MAC address
• The AP IP address
• The client count
• The base BSSIDs for both radios
Each AP caches locally stored information about other cluster members and maintains its own
view of the cluster.
Kommentare zu diesen Handbüchern