If you run into issues where one of the controllers gets rolled-back to original config, but Mobility Master/Conductor still has the new config, you can fix it on the controller, from CLI with the following:
!!!!!DON'T DO ANYTHING ELSE IN DISASTER-RECOVERY MODE. THIS IS A GOOD WAY TO BREAK MOBILITY MASTER/CONDUCTOR!!!!!!
(MC2) #disaster-recovery on
Entering disaster recovery mode
(DR-Mode) [mm] #configure t
Enter Configuration commands, one per line. End with CNTL/Z
(DR-Mode) [mm] (config) #controller-ip vlan 2
Error: interface VLAN 2 has static ip address configured at group level /mm
(DR-Mode) [mm] (config) #cd /mm/mynode
(DR-Mode) [mynode] (config) #controller-ip vlan 2
This configuration change requires a reboot. Do you want to continue[y/n]:y
Mobility Master will be rebooted on write memory.
(DR-Mode) ^[mynode] (config) #cd /mm
(DR-Mode) ^[mm] (config) #masterip 192.168.2.5 ipsec Aruba123 interface vlan 2
Change in the masterip configuration requires device to reload. Make sure the modified configuration ensures connectivity to the Master. Do you want to continue [y/n]: y
(DR-Mode) ^[mm] (config) #no ip default-gateway 192.168.100.1
(DR-Mode) ^[mm] (config) #ip default-gateway 192.168.2.1
(DR-Mode) ^[mm] (config) #exit
(DR-Mode) ^[mm] #write mem
(DR-Mode) ^[mm] #
(continued on next page)
[22:16:20]:Shutdown processing started
Because we rebooted, we didn't need to turn disaster-recovery off. If we hadn't rebooted, you can turn DR off with the command "disaster-recovery off"
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.