Meru Technical Note - How do I setup N plus 1 (N+1) Configuration?
How do I setup N plus 1 (N+1) Configuration?
Scope
KB ARTICLE TYPE: Configuration
RELATED PRODUCTS: All controller/AP platforms
RELATED SOFTWARE VERSIONS: 3.4.2-140 or later
KEYWORDS : N+1, redundancy, clusterSolution
The optional N+1 redundancy software feature replaces and extends the standard Meru Wireless LAN System High Availability redundancy service by allowing a standby N+1 slave controller to monitor and failover more than one master controller.
The detailed configuration steps are as below,
Configuration Steps:
STEP 1: Starting N+1 on Master Controllers: N+1 must first be started on the Master Controllers.
To configure a master controller:
1. On each master controller, enter configuration mode and start the N+1 software:
3000-1# configure terminal
3000-1(config)# nplus1 start master
2. Exit configuration mode and check that the N+1 software has been started on that controller:
3000-1(config)# exit
3000-1# sh nplus1
-----------------------------------------------------
Master controller
nplus1 Software Version : 1.0-40
Master IP : 10.1.1.10
Master Hostname : 3000-1
-----------------------------------------------------
STEP 2: Configuring N+1 on the Slave Controller
After starting N+1 on each of the Master Controllers, start N+1 on the Slave Controller, and then add each Master Controller to the Slave Controller.
To configure N+1 on the slave controller, follow these steps:
1. Enter configuration mode and start the N+1 software:
3000-slave# configure terminal
3000-slave(config)# nplus1 start slave
Setting up this controller as a Passive Slave controller
3000-slave(config)#
2. Check that the software has started on the slave with the show nplus1 command
(note that no masters display in the Master Controllers list):
3000-slave (config)# do show nplus1
-----------------------------------------------------------------
Current State: Passive
Wait to restore: 8 minutes
Nplus1 Software Version: 1.0-40
Slave IP: 10.1.1.21
Slave Hostname: 3000-slave
-----------------------------------------------------------------
Master Controllers
Hostname IP Address Admin Switch Reason Adverts SW Version
-----------------------------------------------------------------
3000-slave#
3. Supply the hostname (for example, 3000-1) and IP address of each master
controller in the cluster. You will be prompted for the controller’s password to complete the addition:
3000-slave# configure terminal
3000-slave(config)# nplus1 add 3000-1 10.1.1.10
admin@10.1.1.10 Password: xxx
4. Exit configuration mode and check that the master controller has been enabled
(the Admin status is now Enable):
3000-slave(config)# exit
3000-slave# show nplus1
-----------------------------------------------------------------
Current State : Passive
Wait to Restore : 8 minutes
nplus1 Software Version : 1.0-40
Slave IP : 10.1.1.21
Slave Hostname : 3000-slave
-----------------------------------------------------------------
Master Controllers
Hostname IP Address Admin Switch Reason Adverts SW Version
--------------------------------------------------------------------
3000-1 10.1.1.10 Enable Yes - 1 3.4.2-140
LIMITATIONS IF ANY: The Slave Controller must be the last controller in the cluster to start N+1. Licensing required if there is more than one Master.