Usage of AP-Move command in 8.x code

By esupport posted Feb 21, 2017 08:32 AM

  
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.

1 comment
23 views

Comments

Apr 28, 2020 05:26 AM

Do we have a similar command to move clients?

Situation: we have an issue that sometimes after upgrades of controllers, the nginx service did not start and we can't get it started without a reboot of the controller.

Now my end-customer was moving his AP to another controller since he thought that his client would also move, but since he is in clustering, his client was still falling on the controller with the issue and due to this he thought all controllers had the issue. If he can move his client to another controller he could test with his own client the behavior on other controllers...