Wireless Controller
Dedicated Wi-Fi control and management for high density and mobility
sachitdas_FTNT
Article Id 197196
Description
This article describes how to setup N+1 configuration.

Scope
For version 8.x and above.

Solution
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 fail over more than one master controller.

Configuration steps.

1) Starting N+1 on Master Controllers.

N+1 must first be started on the master controllers.

To configure a master controller.

-
On each master controller, enter configuration mode and start the N+1 software:
# configure terminal
(config)# nplus1 start master
- Exit configuration mode and check that the N+1 software has been started on that controller:
(config) exit
sh nplus1
-----------------------------------------------------
Master controller
nplus1 Software Version : 1.0-40
Master IP : 10.1.1.10
Master Hostname : 3000-1
-----------------------------------------------------
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.

- Enter configuration mode and start the N+1 software:
# configure terminal
(config)# nplus1 start slave
Setting up this controller as a Passive Slave controller.
(config)#
- Check that the software has started on the slave with the show nplus1 command.

Note:
No masters display in the master controllers list):
(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#

- Supply the hos tname (for example, 3000-1) and IP address of each master controller in the cluster.
# configure terminal
3000-slave(config)# nplus1 add 3000-1 10.1.1.10
admin@10.1.1.10 Password: xxx
- Exit configuration mode and check that the master controller has been enabled (the Admin status is now Enable).
(config) exit
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 has to be the last controller in the cluster to start N+1. 
Licensing not required up to 5 controllers in total (4 master controllers + 1 slave controllers).



Contributors