westcott... I was able to advance. Unfortunately another problem shows up.
The correct way to configure is:
First configure the VRRP as the configuration guide says.
between the VMC and the physical controller there is no problem with changing master(standalone) and standby(standalone) role with each other. Although I did not test the preempt function.
(Aruba-MC-VA) [mynode] #show vrrp
Virtual Router 180:
Description MASTER_VRRP
Admin State UP, VR State MASTER
IP Address 172.16.1.150, MAC Address 00:00:5e:00:01:b4, vlan 172
Priority 201, Advertisement 1 sec, Preemption Disable Delay 0
Auth type PASSWORD, Auth data: ********
tracking is not enabled
(WLC-7005) [mynode] #show vrrp
Virtual Router 180:
Description BKP_VRRP
Admin State UP, VR State BACKUP
IP Address 172.16.1.150, MAC Address 00:00:5e:00:01:b4, vlan 172
Priority 101, Advertisement 1 sec, Preemption Disable Delay 0
Auth type PASSWORD, Auth data: ********
tracking is not enabled
Both rolesinfo in this configuration still says switchrole:standalone
So, the second step is to configure the database synchronization as you told.
To do that, is necessary to level up in the hierarchy and in the level Mobility Controller activate the database synchronization toggle and set a sync period and then in the local node level, the toggle and the sync period will be the same as the one settled in the mobility controller level. So this time in the local level, It will be need to fill in Master VRRP, the peer ip and the IPsec peer passphrase. So the section about Master Redudancy of the chapter is partly correct to my scenario.
Now, with this setup complete, in show roleinfo, the backup VRRP controller will be called standbye and with show swiches both controller are showing up their respective information.
(Aruba-MC-VA) [mynode] #show switches
All Switches
------------
IP Address IPv6 Address Name Location Type Model Version Status Configuration State Config Sync Time (sec) Config ID
---------- ------------ ---- -------- ---- ----- ------- ------ ------------------- ---------------------- ---------
172.16.1.131 None Aruba-MC-VA Building1.floor1 standalone ArubaMC-VA 8.2.2.4_68953 up UPDATE SUCCESSFUL 0 14
172.16.1.132 None WLC-7005 Building1.floor1 standby Aruba7005 8.2.2.4_68953 up CONFIG FAILURE(14) 0 14
Total Switches:2
But, with this setting, the database synchronization will not work.
(Aruba-MC-VA) [mynode] #show database synchronize
Last L2 synchronization time: Fri Jan 31 14:33:44 2020
Last L3 synchronization time: Secondary not synchronized since last reboot
To Master Switch at 172.16.1.139: *** FAILED ***
WMS Database backup file size: 40266 bytes
Local User Database backup file size: 41647 bytes
Global AP Database backup file size: 23061 bytes
IAP Database backup file size: 3760 bytes
Airgroup Database backup file size: 3062 bytes
License Database backup file size: 5323 bytes
CPSec Database backup file size: 3224 bytes
L2 Synchronization took 10 second
L3 Synchronization took less than one second
Last failure cause: Standby switch did not acknowledge the CPSec database transfer
(Aruba-MC-VA) [mynode] # show log errorlog all
(…)
Jan 31 14:27:34 <dbsync 307273> <5520> <ERRS> |dbsync| dbsync: failed to start db sync on standby (handle_start_sync_reply_receive)
WLC-7005) [mynode] # show log errorlog all
(…)
Jan 31 14:27:34 dbsync[3834]: <307319> <3834> <ERRS> |dbsync| dbsync: Can not start db sync on backup Master Switch: (SYNC_WAIT_WMS_DB)
So, I discover that to resolve this error, it was necessary to configure the Cluster WhiteList propagation settings, so I set the master as the root and the standbye as the member.
Unfortunately the problem with synchronization will continue, and new error shows up….
(WLC-7005) [mynode] # show log errorlog all
(...)
Jan 31 14:48:29 <dbsync 307335> <3834> <ERRS> |dbsync| dbsync: Can not receive file on backup Master Switch: (SYNC_WAIT_BOCMGR_DB)
(Aruba-MC-VA) [mynode] # show log errorlog all
(…)
Jan 31 14:48:29 <dbsync 307398> <5520> <ERRS> |dbsync| dbsync: failed to receive CPSEC db sync on standby (handle_send_cpsec_db_ack)
(Aruba-MC-VA) [mynode] #show database synchronize
Last L2 synchronization time: Fri Jan 31 14:48:29 2020
Last L3 synchronization time: Secondary not synchronized since last reboot
To Master Switch at 172.16.1.139: *** FAILED ***
WMS Database backup file size: 40266 bytes
Local User Database backup file size: 41649 bytes
Global AP Database backup file size: 23061 bytes
IAP Database backup file size: 3760 bytes
Airgroup Database backup file size: 3062 bytes
License Database backup file size: 5323 bytes
CPSec Database backup file size: 3224 bytes
L2 Synchronization took 11 second
L3 Synchronization took less than one second
Last failure cause: Standby switch did not acknowledge the CPSec database transfer
57 L2 synchronization attempted
57 L2 synchronization have failed
0 L3 synchronization attempted
0 L3 synchronization have failed
L2 Periodic synchronization is enabled and runs every 1 minute
L3 Periodic synchronization is disabled
Synchronization doesn't include Captive Portal Custom data
(Aruba-MC-VA) [mynode] #
(WLC-7005) [mynode] #show database synchronize
Last L2 synchronization time: Fri Jan 31 14:48:29 2020
From Master Switch at 172.16.1.131: *** FAILED ***
WMS Database backup file size: 40266 bytes
Local User Database backup file size: 41649 bytes
Global AP Database backup file size: 23061 bytes
IAP Database backup file size: 3760 bytes
Airgroup Database backup file size: 3062 bytes
License Database backup file size: 5323 bytes
CPSec Database backup file size: 0 bytes
Bocmgr Database backup file size: 0 bytes
L2 Synchronization took 11 second
Last failure cause: Unknown error
57 L2 synchronization attempted
57 L2 synchronization have failed
L2 Periodic synchronization is enabled and runs every 1 minute
Synchronization doesn't include Captive Portal Custom data
(WLC-7005) [mynode] #
So.... Any help ? Is this a bug ?
Just to put more information. In my lab I have the VMC and two physical controllers. So as the VMC is showing this error I decide to try the same configuration using the two physical controllers, so without the Clustering whitelist (because it not asked) and the two physical controller It is partially working, as there is no error message showing up, but the configuration are is not been replicated to the standby controller… I check it by removing the master and AP did go the standby but there is no config in the standby, so even with the database synchronization not showing error with two physical controller there is no replication of the configuration….