Controller Based WLANs

What are the caveats of enabling database sync on Aruba controllers?

by ‎05-18-2016 01:15 PM - edited ‎05-18-2016 01:15 PM
Q:

Aruba controller allows database sync between the master and standby controller so that the localuserdb is preserved on standby controller in case the master controller goes down.

What are the various points that need to be kept in mind regarding database sync on Aruba controllers?

 

 



A:

1. Database sync is of two types, manual and automatic.

2. Manual database sync can only be configured on a Master controller. Automatic sync can be configured on all controllers but functions only on a master.

3. On standby, it gives following error:

(standby) #database synchronize
Cannot start database synchronization: switch is not an active Master.

 

4. On Local controller it gives following error:

(local-5) #database synchronize
Cannot start database synchronization: peer is not configured.

 

5. Both Manual and automatic, database sync types will copy the contents of local-user-db from master to standby. There is no change on local controllers.

6. Database sync will erase the contents of the localuser-db on standby and copy Master controller's local-user-db.

7. We must not configure small time value for database sync especially if database is huge. This might result in error following error message:

show run
Building Configuration...
Module Configuration Manager is busy. Please try later


8. To avoid this, we can increase the time value of database sync. The time configured depends upon the local-user-db size, controller capacity, network latency etc. Below we configure it to be 600 minutes or 10 hours :

(master) #configure t
(master) (config) #database synchronize period 600

 

9. If the last sync was automatic, it will show up as below on the master controller:

(master) #show database synchronize

Last synchronization time: Wed May  4 06:26:20 2016
To Master Switch at 10.150.2.3:  succeeded
WMS Database backup file size: 160918 bytes
Local User Database backup file size: 60808 bytes
CPSec Database backup file size: 3252 bytes
Synchronization took 3 second

1 synchronization attempted
0 synchronization have failed

Periodic synchronization is enabled and runs every 600 minutes
Synchronization doesn't include Captive Portal Custom data

 

10 When we manually sync the database, it shows up as below:

(master) #database synchronize
(master) #show database synchronize

Last manual synchronization time: Wed May  4 12:07:45 2016
To Master Switch at 10.150.2.3:  succeeded
WMS Database backup file size: 155050 bytes
Local User Database backup file size: 60808 bytes
CPSec Database backup file size: 3252 bytes
Synchronization took 2 second

2 synchronization attempted
0 synchronization have failed

Periodic synchronization is enabled and runs every 360 minutes
Synchronization doesn't include Captive Portal Custom data
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.