Technical data

N+1 Redundancy
© 2012 Meru Networks, Inc. Implementing Redundancy 103
3000-1# configure terminal
3000-1(config)# nplus1 stop
3000-1(config)# exit
Replacing a Master Controller
Should a Master Controller in the cluster need to be replaced, the following summa-
rizes the steps needed to replace a Master Controller.
1. On the Slave Controller, disable the failed Master Controller:
3000-slave# configure terminal
3000-slave(config)# nplus1 disable <master IP-addr>
3000-slave(config)# exit
2. Stop the failed Master Controller N+1 services (skip if Master Controller is not
functioning):
3000-master# configure terminal
3000-master(config)# nplus1 stop
3000-master(config)# exit
3. Power down the failed Master Controller (skip if Master Controller is not
functioning):
3000-master(config)# poweroff
4. Physically remove the failed controller and replace it with the new controller.
(New controller must be running the same version of System Director as the Slave
Controller and have the same static IP address that the replaced controller had.)
5. On the Slave Controller, execute the nplus1 access command to allow access to
the newly added Master Controller:
3000-slave# configure terminal
3000-slave(config)# nplus1 access master_IP_addr
6. On the Slave Controller, enable the new Master Controller:
3000-slave(config)# nplus1 enable master_IP_addr
3000-slave(config)# exit
On the Slave Controller, give access permission for the new Master Controller:
3000-slave(config)# nplus1 access master_IP_addr
Working with N+1 Syslog
Checking the Syslog Debug Level
The show nplus1 debugloglevel command shows the level of verboseness set for the
N+1 log messages.
3000-slave# sh nplus1 debugloglevel
nplus1 Debug Logging Level: 0
3000-slave#