Controller Based WLANs

'Disaster-Recovery' feature on AOS 8.x
Q:

How can we rollback a bad configuration on a MD in AOS 8.x?



A:

AOS 8.x brings in a new feature - 'Disaster Recovery'. While configuring MD's there are chances that we end up saving wrong configuration.

 

For eg; while doing initial configuration of MD and we save the wrong mac-address MM. Once the MD boots up we cannot edit any changes as all the configuration is pushed from MM. In these kind of scenarios we can use the 'Disaster-Recovery' option instead of doing a 'write erase'.

 

Consider that during initial setup, a wrong IPSEC key was saved and MD was rebooted. Post reboot MD will fail to contact MM and no configuration sync will happen.

(A7030) *#show running-config | include master
Building Configuration...
masterip 10.17.164.237 ipsec aruba123456 interface vlan 1

(A7030) *#show switches
All Switches
------------
IP Address    IPv6 Address  Name   Location          Type  Model      Version       
----------    ------------  ----   --------          ----  -----      -------       
10.17.169.71  2001::1       A7030  Building1.floor1  MD    Aruba7030  8.0.1.0_57204  


(A7030) *#configure terminal
This controller is managed by a Mobility Master.
Configuration changes can only be performed on the Mobility Master.

 

'write erase' is an option that can be tried. To avoid un-necessary re-configuration of the controller post 'write erase', we can use the 'disaster-recovery' feature as shown below:

 

(A7030) *#disaster-recovery on

*******************************
Entering disaster recovery mode
*******************************


(DR-Mode) *[mm] (config) #show switches

All Switches
------------
IP Address    IPv6 Address  Name   Location          Type  Model      Version        Status  Configuration State       
----------    ------------  ----   --------          ----  -----      -------        ------  -------------------       
10.17.169.71  2001::1       A7030  Building1.floor1  MD    Aruba7030  8.0.1.0_57204  up      CONFIG DISASTER RECOVERY  


(DR-Mode) *[mm] #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z

(DR-Mode) *[mm] (config) #masterip 10.17.164.237 ipsec aruba123 interface vlan 1
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) #write memory
Saving Configuration...


(DR-Mode) *[mm] #show running-config | include master
Building Configuration...
masterip 10.17.164.237 ipsec aruba123 interface vlan 1


(DR-Mode) *[mm] #disaster-recovery off

(A7030) *#show switches

All Switches
------------
IP Address    IPv6 Address  Name   Location          Type  Model      Version        Status  Configuration State  
----------    ------------  ----   --------          ----  -----      -------        ------  -------------------  
10.17.169.71  2001::1       A7030  Building1.floor1  MD    Aruba7030  8.0.1.0_57204  up      CONFIG PROPAGATION  

Total Switches:1

 

Once 'disaster-recovery' is turned 'off', MD performs a full-sync with MM and resumes configuration sync.

Version History
Revision #:
1 of 1
Last update:
‎03-17-2017 03:27 PM
Updated by:
 
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.