222 Configuring and managing Mobility Domain roaming
NN47250-500 (Version 03.01)
If primary seed of the Mobility Domain or the secondary seed is configured and the primary seed is unavailable
then the configuration changes for WSSs can only be performed on the primary seed of the Mobility Domain or the
secondary seed.

Autodistribution of APs on the Virtual Controller Cluster

The following are the Autodistribution of APs on the Virtual Controller Cluster:
Load balancing of APs are supported across the cluster without any explicit configuration.
The maximum number of configured APs on the primary or secondary seed restrict the maximum number of
configured APs on the cluster. Use larger capacity WSSs for larger deployment of APs.
Client session states are shared among WSSs in the cluster configuration.

“Hitless” failover with Virtual Controller Cluster configuration

The following are the “Hitless” failover with Virtual Controller Cluster configuration:
Failure of an WSS has no adverse impact on the current installation. Existing clients and APs remain active on the
network and there is no impact on the ability to make cluster configuration changes while the WSS is in a “Failure”
state.
APs connected to a WSS failover to another WSS in the cluster without resetting on the network.
Existing client sessions on an AP are not disconnected if the WSS is in the process of failing.
Client session states are shared between WSSs with a configuration profile for an AP. This ensures proper network
resiliency capability.
Keepalive packets are sent between the primary seed and the cluster members to ensure that all members are available.

Configuring Smart Mobile Cluster on a Mobility Domain

On the primary seed for the Mobility Domain, enter the following commands:
WSS_PS# set cluster mode enable
success:change accepted
On the secondary seed for the Mobility Domain, enter the following command to provide cluster redundancy on the
network:
WSS_SS# set cluster mode preempt enable
On each Mobility Domain member, enter the following command:
WSS# set cluster mode enable
success:change accepted
WSS# set cluster mode enable
success:change accepted
WSS# set cluster mode enablesyn
success:change accepted