Wireless Access

 View Only
last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Strange Configuration 7030

This thread has been viewed 4 times

  • 1.  Strange Configuration 7030

    Posted Dec 20, 2019 02:16 AM

    We currently have two controllers which are configured as standalone / standby. When the main controller is no longer alive the standby controller is running.

     

    AS i can see there are three configurations:

    1. The mobility master configuration (mm) (192.168.200.140)
    2. The node configuration (standalone) (192.168.200.141)
    3. The other node configuration (standby) (192.168.200.142)

    I noticed that when i switch off the standalone, the master configuration on the standby is not identical to the standalone controller.

     

    I checked the nodes configuration and they are perfectly the same (Except for IP / hostname). How come the mobility master configuration is not identical on both controllers? 

     

    Furthermore, i have posted the database sync below. 

    <----Display of show database sync from standalone----------------->
Last L2 synchronization time: Fri Dec 20 07:44:59 2019
Last L3 synchronization time: Secondary not synchronized since last reboot
To Master Switch at 10.100.200.142:  succeeded
WMS Database backup file size: 96909 bytes
Local User Database backup file size: 49536 bytes
Global AP Database backup file size: 14964 bytes
IAP Database backup file size: 3751 bytes
Airgroup Database backup file size: 3055 bytes
License Database backup file size: 4943 bytes
CPSec Database backup file size: 3248 bytes
Bocmgr Database backup file size: 6017 bytes
L2 Synchronization took 8 second
L3 Synchronization took less than one second

87 L2 synchronization attempted
4 L2 synchronization have failed

0 L3 synchronization attempted
0 L3 synchronization have failed

L2 Periodic synchronization is enabled and runs every 30 minutes

L3 Periodic synchronization is disabled

Synchronization doesn't include Captive Portal Custom data
    <----Display of show database sync from standby----------------->
Last L2 synchronization time: Fri Dec 20 07:44:59 2019
From Master Switch at 10.100.200.141:  succeeded
WMS Database backup file size: 96909 bytes
Local User Database backup file size: 49536 bytes
Global AP Database backup file size: 14964 bytes
IAP Database backup file size: 3751 bytes
Airgroup Database backup file size: 3055 bytes
License Database backup file size: 4943 bytes
CPSec Database backup file size: 3248 bytes
Bocmgr Database backup file size: 6017 bytes
L2 Synchronization took 8 second

90 L2 synchronization attempted
3 L2 synchronization have failed

L2 Periodic synchronization is enabled and runs every 30 minutes

Synchronization doesn't include Captive Portal Custom data
    <----Display of show database sync from master mobility----------------->
Last L2 synchronization time: Fri Dec 20 08:15:01 2019
Last L3 synchronization time: Secondary not synchronized since last reboot
To Master Switch at 10.100.200.142:  succeeded
WMS Database backup file size: 97851 bytes
Local User Database backup file size: 49550 bytes
Global AP Database backup file size: 14964 bytes
IAP Database backup file size: 3751 bytes
Airgroup Database backup file size: 3055 bytes
License Database backup file size: 4943 bytes
CPSec Database backup file size: 3248 bytes
Bocmgr Database backup file size: 6017 bytes
L2 Synchronization took 8 second
L3 Synchronization took less than one second

88 L2 synchronization attempted
4 L2 synchronization have failed

0 L3 synchronization attempted
0 L3 synchronization have failed

L2 Periodic synchronization is enabled and runs every 30 minutes

L3 Periodic synchronization is disabled

Synchronization doesn't include Captive Portal Custom data

     



  • 2.  RE: Strange Configuration 7030
    Best Answer

    Posted Dec 20, 2019 02:50 AM

    After comparing the two configuration  line by line the only difference was an extra aaa profile which was empty on the standby which was deleted.

     

    After the deletion a reboot was done and the configuration sync worked.