Auto reboot feature in 8.x when controller IP/VLAN is changed

MVP
MVP
Q:

Why Aruba Controller automatically reboots in 8.X version after executing 'write-memory', when Controller's IP/VLAN is changed?



A:

As recommended by Aruba, any change to Controller's IP/VLAN to take affect, a reboot is must and required. In 6.x codes, post making the VLAN/IP change, you will be prompted with the below message to save the configuration and reboot. 

 

Present Warning Message in 6.x

(TAC-LAB-7210-1) (config) #controller-ip vlan 111
Since controller IP address will change, connectivity to this controller might be affected. Do you want to proceed with this action [y/n]: y

This configuration change requires a reboot.
 PLEASE SAVE THE CONFIGURATION AND REBOOT.

(TAC-LAB-7210-1) (config) #

 

However from 8.x onwards, any change in Controller IP/VLAN, will automatically force the controller to reboot, the moment, the configuration is pushed using 'write memory'. A manual reload is not required to reboot the Controller for the changes to take effect. 

 

Present Warning Message in 8.x:

(LAB-mm01) [mynode] (config) #controller-ip vlan 1

This configuration change requires a reboot. Do you want to continue[y/n]:y
PLEASE SAVE THE CONFIGURATION AND REBOOT.

(LAB-mm01) ^[mynode] (config) #write memory

Saving Configuration...
Partial configuration for /mm/mynode
------------------------------------
Contents of : /flash/ccm/partial/725/p=sc=mynode.cfg
controller-ip vlan 1
Configuration Saved.

 

Starting from 8.3.0.5 onwards, the above syntax will be changed with the below message:

 

New Warning message:

(MM1) ^[mynode] (config) #controller-ipv6 vlan 1 address 2001::1
This configuration change requires a reboot. Do you want to continue[y/n]:y
Mobility Master will be rebooted on write memory.
Version history
Revision #:
2 of 2
Last update:
‎01-30-2019 03:55 PM
Updated by:
 
Labels (1)
Contributors