Wireless Controller
Dedicated Wi-Fi control and management for high density and mobility
shruthinr
Staff
Staff
Article Id 191736
Description
This article outlines the steps to be followed in case of replacing a master controller.

Scope
Controller 7.x and above.

Solution
Step 1: Power the original master controller off, the slave controller will then take the active role.  If the master controller is already down/RMA’d, the slave controller would have taken the role and show up as Active Slave.

Step 2:  Get Console access to the new controller.  Replace to a new controller, which contains same configuration of bonding, interface mode. Assign an unused IP address to the new controller (not the master IP).  Copy the configuration and make sure everything is same as active slave controller.  Do copy running to startup.
# copy running-config startup-config

Step 3:  Assign IP address(es) as the original master controller to the new controller.

Step 4: Run "nplus1 start master" command on the new controller in order to make master controller.
# configure terminal
# nplus1 start master

Step 5: Run "nplus1 slave" command on the new master controller in order to detect the slave controller, and then, the new master controller takes passive role. (Please wait until master comes up as passive master)
# configure terminal
# nplus1 slave

Step 6: Run "nplus1 access" command on active slave controller in order to generate authorized key on the new passive master controller.
# configure terminal
# nplus1 access

For example:
MC3200(15)(config)# nplus1 access 10.33.186.126
admin@10.33.186.126 Password:

When you run the above command you will be prompted to enter password.  Please enter the new controller password.

Step 7:  Do “nplus1 revert” on active slave to get the master state as active and slave state to Passive.
# configure terminal
# nplus1 revert

Step 8:  Check the nplus1 status on both the controllers using the following command.
#show nplus1

Contributors