Before defining a profile cluster configuration, refer to the following deployment
guidelines to ensure the configuration is optimally effective:
- A cluster member cannot adopt more APs than its hardware capacity and
license provisions allow. This is important when the number of pooled AP and
AAP licenses exceeds the aggregated AP and AAP capacity available after a
cluster member has failed. A cluster supported profile should be designed to
ensure adequate AP and AAP capacity exists to address failure scenarios
involving both APs and AAPs.
- When cluster is enabled for a profile and a failure occurs amongst one of
the cluster members, AP and AAP licenses are persistent in the cluster even
during reboots or power outages. If a cluster member failure were to occur,
cluster settings must remain enabled on all remaining cluster members or the
pooled member licenses will be deprecated.