Configuring N+1

Ruckus IoT Controller N+1 high availability (HA) feature ensures high system availability, reliability and scalability of the controller, and also enables load balancing, backup, and failover. To configure an HA cluster, all the hosts in the cluster must have access to the same shared storage, which allows virtual machines (VMs) on a given host to fail over to another host without any downtime in the event of a failure.

Before beginning to use N+1, pay attention to the following prerequisites for configuring the primary and secondary controller:
  • The primary and secondary controller must be in the same subnet and reachable.
  • The primary and secondary controller must be configured with static IP addresses.
  • The primary and secondary controller must be running the same version.
  • The primary and secondary controller must have a synchronized date and time.
  • The primary and secondary controller must have different host names.
  • The secondary controller services must be started for N+1 to work.

Configuring Static Addresses for Primary and Secondary Controller

The static IP addresses of the primary and secondary controller can be configured in two ways:
  • From the Ruckus IoT Controller main menu, select Admin > VM Configurations.
  • Set the static address of the primary and secondary controller on the Initialization page. Refer to Logging In to Ruckus IoT Controller.

Configuring the N+1 Feature

After configuring the static IP addresses for primary and secondary controller, N+1 can be enabled by performing the following steps.
  1. Log in to the console of the Ruckus IoT Controller.
  2. Enter 5 in the Enter Choice field.
    Figure 1. Ruckus IoT Controller Main Menu
  3. Enter 1 to continue the configuration.
    Figure 2. Continuing the Configuration
  4. To configure the primary controller, enter 1 and type the IP address of the secondary controller in the Enter Secondary Controller IP field.
    Figure 3. Configuring the Primary Controller
  5. Type the preferred IP address in the Enter preferred Virtual IP field.
    Note: The Preferred Virtual IP should not be same as primary or secondary controller IP.
    Figure 4. Entering the Preferred Virtual IP Address
  6. Enter Y to continue with the N+1 configuration.
    Figure 5. Completing the Primary Controller Configuration
    After configuring the primary controller, the configuration of secondary controller begins.
    Figure 6. Continuing with the Secondary Controller Configuration
    Figure 7. N+1 Configuration Completed
    You have configured N+1 successfully.
  7. To verify the IP addresses of the primary or active primary, and the secondary or active secondary, enter 5 in the Enter Choice field.
    Figure 8. Verifying the IP Address of the Active Primary
  8. To replace the secondary controller , enter 3.
    Figure 9. Replacing the IP Address of Secondary Controller
    Figure 10. Successful Completion of Replacing the Node
  9. To enable Forced Fallback, enter 3 and y to continue the configuration.
    Figure 11. Configuring Forced Fallback
  10. To replace the primary controller, enter3.
    Figure 12. Replacing the Primary Controller
  11. Enter the IP address of the primary controller.
    Figure 13. Continuing with Replacing the Primary Controller
    Replacing the primary controller has been successfully completed.
    Figure 14. Completion of Replacing the Primary Controller