Controller Based WLANs

Requirement:

Even though APs are seen up and active on Local Controller(s), at times Master Controller database might be showing it down. On such cases, we can manually synchronize AP database on the Master Controller for the AP(s) in question terminated on respective Local Controller.

Staring 6.4.3.X AOS version, a new command has been added to manually synchronize the AP database in case of any miss-match between the Master and Local Controller.

Below command needs to be executed on Master Controller for. Can be executed for specific AP or based on LMS address.

(Aruba Controller)# ap gap-db resync lms lms-ip 140.104.9.23 ap-name <name of the AP>

(Aruba Controller)# ap gap-db resync lms lms-ip <lms-ip>

As shown below, AP named after Test01 is seen up on the Local Controller. However Master Controller AP database shows it to be down. Post "ap gap-db resync" execution, AP database on Master was forcefully synchronized followed by which the AP is shown up.

On Master:

(Aruba-Master-7210) #show ap database | include "Test01"
Test01     Default  105      10.10.23.73   Down                      10.10.9.21  0.0.0.0

On Local:

(Aruba-Local-7240) #show ap database | include "Test01"
Test01     Default  105      10.10.23.73   Up 3d:0h:35m:51s          10.10.9.23  140.104.9.22

After execution of "ap gap-db resync" on Master, the AP is shown up.

(Aruba-Master-7210) #show ap database | include "Test01"
Test01     Default  105      10.10.23.73   Down                      10.10.9.21  0.0.0.0

(Aruba-Master-7210) # ap gap-db resync lms lms-ip 10.10.9.23 ap-name Test01

(Aruba-Master-7210) #show ap database | include "Test01"
Test01     Default  105      10.10.23.73   Up 3d:0h:35m:51s          10.10.9.21  0.0.0.0