Configuring HA for Redundancy

The High Availability (HA) configuration maintains system reliability and minimizes downtime by enabling automatic failover to the secondary node when the primary node becomes unavailable, ensuring uninterrupted service.

You will need the static IP addresses for the controller nodes that you intend to designate as Primary and Secondary. This task is performed on the GUI for the controller to be designated as the Primary node.

Complete the following steps to configure HA.

  1. From the main menu, select Admin > HA.

    Enabling HA

    Enabling HA
  2. In the HA Configuration section, configure the following.
    1. Primary Node IP: Enter the static IP address of the primary node.
      Note: During normal conditions, the primary node is responsible for handling operations.
    2. Secondary Node IP: Enter the static IP address of the secondary node.
      Note: The secondary node takes over when the primary node fails.
    3. Virtual IP: Enter the static virtual IP address.
      Note: A Virtual IP (VIP) is an IP address that the clients use to connect to the system, regardless of which node (primary or secondary) is active.
  3. Click Enable to activate HA.
    A pop-up appears, enter the admin pasword, and click Submit to enable HA.

    Entering the Authentication Password

    You can monitor the status and health of the HA system using the following visual and text indicators:

    HA Status and HA Health

    HA Status Enabled HA is enabled.
    Disabled HA is disabled.
    HA Health Healthy The Primary and Secondary nodes are synchronized.
    Critical If HA is enabled, then either the primary or the secondary node is unrecoverable. If HA is disabled, then HA Health defaults to Critical.
Parent topic: High Availability RUCKUS IoT Controller