ArubaOS 8.6.0.0 Help Center

Configuring High Availability

The high availability feature supports redundancy models with an active controller pair, or an active/standby deployment model with one backup controller supporting one or more active controllers. Each of these clusters of active and backup controllers comprises a high-availability group. All active and standby controllers within a single high-availability group must be deployed in independent masters topology. An independent masters topology requires all independent master controllers to have the same WLANWireless Local Area Network. WLAN is a 802.11 standards-based LAN that the users access through a wireless connection. configuration.

The High Availability feature is not supported on Standalone Master-Standby deployments.

The following procedure configures High Availability using the WebUI:

  1. For a Stand alone controller, under Mobility Controller, select your device and then navigate to the Configuration > Redundancy> High availability tab.
  2. For a managed device, navigate to the Configuration > Redundancy> High availability tab.
  3. Expand the HA Groups accordion and click +. A pop-up window appears.
  4. In the Name field, enter a name for the new HA group.
  5. Configure an IPv4 or IPv6 address for the controller.
    1. Click + in the HA Controller IPv4 or HA Controller IPv6 fields. The Add HA Controller IP window opens. Enter an IP address.

    IPv4 and IPv6 controllers can be part of the same HA group profile. However, HA works only between controllers of same IP format.

    1. Click the Role drop-down list to assign a role to the controller. The IP address of each controller must be reachable by APs and must be the IP address that appears in the Configuration > Controller > System settings tab of the controller WebUI, or in the output of the show controller-ip CLICommand-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command. The role can be one of the following options:
    • active: Controller is active and serving APs.
    • dual: Controller serves some APs and acts as a standby controller for other APs.
    • standby: Controller does not serve APs and only acts as a standby in case of failover.
    1. Click OK to add the controller to the group.
  6. (Optional) Select the Pre-emption check box to enable the failed over APs to attempt to connect back to its original active controller once the controller is reachable again. When you enable this setting, the AP waits for the time specified by the lms-hold-down-period parameter defined in the ap system profile before the AP attempts to switch back from the standby controller to the original controller.
  7. (Optional) The standby controller over-subscriptionA business model where a customer pays a certain amount as subscription price to obtain access to a product or service. feature allows a standby controller to support connections to standby APs beyond the controller's original rated AP capacity. To enable this feature, select the Over subscription check box.
  8. (Optional) Select the State synchronization check box to enable the feature. State synchronization improves failover performance by synchronizing client authentication state information from the active controller to the standby controller. (For more information about state synchronization, see  Client State Synchronization).

    State synchronization is not applicable for IPv6 controllers.

  9. (Optional) Select the Heartbeat check box to enable the high availability inter-controller heartbeat features, which enable faster AP failover from an active controller to a standby controller, especially in situations where the active controller reboots or loses connectivity to the network. To edit the default heartbeat threshold and interval values:
    • Enter a heartbeat threshold in the Heartbeat threshold field to define the number of heartbeats that must be missed before the APs are forced to failover to the standby controller. This value must be between 3 and 10, inclusive.
    • Enter a heartbeat interval in the Heartbeat interval (ms) field to define how often inter-controller heartbeats are sent. This value must be between 100 and 1000 ms, inclusive.
  10. (Optional) If you enabled the state synchronization feature in Step , enter a pre-shared key into the Pre-shared key and Retype pre-shared key fields.
  11. Click Submit.
  12. Click Pending Changes.
  13. In the Pending Changes window, select the check box and click Deploy changes.

The following procedure associates a controller with a High Availability group:

  1. For a standalone controller, under Mobility Controller, select your device and then navigate to the Configuration > Redundancy > High availability tab.
  2. For a managed device, navigate to Configuration > Redundancy > High availability tab.
  3. Expand the HA Member accordion.
  4. Select a HA group from Member of HA group drop-down list.
  5. Click Submit.
  6. Click Pending Changes.
  7. In the Pending Changes window, select the check box and click Deploy changes.

To configure a High Availability group using the command-line interface, access the CLICommand-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. in config mode and issue the following commands. The high availability group profile should be configured with a pair of IPv4 controller addresses and pair of IPv6 controller addresses to allow an IPv4 or IPv6 access point to establish a connection to a standby controller.

(host) [mynode] (config) #ha group-profile <profile>

(host) [mynode] (HA group information "default") #controller <ip> role [active/dual/standby]

A controller using the high availability features must be defined as a member of a high availability group. To add a controller to the new high availability group, issue following CLICommand-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command:

(host)[mynode] (config)#ha group-membership <ha-group>

/*]]>*/