Summit WM3000 Series SW v5.1 – Clustering
5
© 2012 Extreme Networks, Inc. All rights reserved.
Introduction
Two Wireless LAN (WLAN) controllers are clustered together for redundancy and resiliency. As such, the cluster can only
be formed between WLAN controllers of like model. For example, a WM3600 can only be clustered with another WM3600,
not a WM3700 or WM3400.
Clustering enables redundancy for features such as AP Adoption, License Aggregation, AP failover, DHCP and AP load
balancing. Unlike previous versions of WM3000 Series software (four and below), clustering now truly uses a single
configuration across cluster members (not including device specific items). The configuration of the cluster or adopted AP
can be modified through the GUI of either cluster member. AP and AAP licenses are shared across the cluster. However
the advanced Security and Advanced WIPS licenses will need to be installed per WLAN controller.
Three scenarios will be explored in this document to build a cluster.
•
The first will put two WLAN controllers in the same Layer-2 network. The cluster is built with a mix of CLI
(command line interface) commands and GUI modifications.
•
The second scenario captures how to configure the cluster strictly through the CLI on both WLAN controllers,
but still in a Layer-2 network.
•
The third configuration leverages the CLI again, but the controllers will reside in unique VLANS (L3 topology).
