Controller Based WLANs

Usage of AP-Move command in 8.x code
Requirement:

•In some application scenarios, customer wants to move some specific APs to other another controller.

•Currently the function can only be done by configuring LMS or AP failover.

•In case customers are reluctant to make any configuration changes, they can make use of AP-move feature.



Solution:

AP-move command can be used in moving an AP from one controller to another without making any configuration changes.

When AP-move is executed on the cluster leader, sapm will send a message to CM to reassign new S-AAC.

Case 1: For redundancy, CM leader will assign new S-AAC with flag S-AAC-assign-by-apmove.

Case 2: For non-redundancy case, CM leader will temporarily enable AP redundancy and assign a new S-AAC to AP with flag S-AAC-assign-by-apmove

 



Configuration:

We can use the following syntax to execute AP move command:

 

•apmove <ap-mac>  <target-ip>

•apmove <ap-group> <source-ip> <target-ip>

•apmove all <source-ip> <target-ip>



Verification

 

•APMOVE can only be executed on cluster LC leader.

 

•AP-Move command will not de-authenticate the clients.

•AP will rebootstrap with APMOVE to non S-AAC.

Version history
Revision #:
1 of 1
Last update:
‎02-21-2017 05:32 AM
Updated by:
 
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.