Controller Based WLANs

What are the possible reasons that the AP didnt fail-over to the backup controller?
Q:

What are the possible reasons that the AP didnt fail-over to the backup controller?



A:

One of the possible reason is that, If the config sync is not successful between the controllers, the profiles will not be pushed to the backup controllers and Aps will stuck in ID flag as shown below.

 

 

Executing #write memory on the master controller didn't help and throws the below error message.

 

Sep 23 09:54:46 <stm 305027>  <ERRS> |stm|  AP test-AP1: No valid instances of required profile "ap system-profile"
Sep 23 09:54:46 <stm 305027>  <ERRS> |stm|  AP test-AP2: No valid instances of required profile "ap system-profile"
Sep 23 09:54:46 <stm 305027>  <ERRS> |stm|  AP test-Ap3: No valid instances of required profile "ap system-profile"

 

Below are the profile errors seen on the controller.

 

 

By doing cfgm sync, all the profiles are pushed to the standby controller.

 

On Master:

(Aruba) (config) #cfgm set sync-type complete 
(Aruba) (config) #write memory

 

So if the config are not pushed to the standby controller  even after doing doing #write memory, we can do cfgm sync which will helpful to sync the config with the standby controller.

 

Version History
Revision #:
2 of 2
Last update:
‎10-18-2016 03:16 PM
Updated by:
 
Labels (1)
Contributors
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.