• Pairing and Configuring the Clusters

    You must add two HPE Aruba Networking Central On-Premises clusters, where one is primary and the other is secondary, and pair them for configuring the redundancy.

    Before pairing the HPE Aruba Networking Central On-Premises clusters for the Datacenter Redundancy configuration, ensure to schedule backup on both the clusters. For information on how to schedule a backup operation, see Back up and Restore System Data.

    • Redundancy configuration must not be done between two primary clusters. If one cluster has the Initial Role as Primary, then the other cluster must have the Initial Role as Secondary.

    • Schedule the same type of Backup Mode on both clusters, either Full Backup or Incremental Backup. Select a backup time that occurs after the completion of redundancy operation. This is necessary because both redundancy and backup are system operations and only one operation can execute at a time.

    • If backup was scheduled only on the primary cluster and not done on secondary cluster before configuring the DR. Then, after a failover, when the secondary cluster attains primary role, schedule the backup.

    To configure redundancy between two HPE Aruba Networking Central On-Premises clusters, complete the following steps on both clusters:

    1. In the HPE Aruba Networking Central On-Premises app Short form for application. It generally refers to the application that is downloaded and used on mobile devices. , set the filter to Global.

    2. Under Global Settings, select System Management > Datacenter Redundancy.

      The Datacenter Redundancy tab is displayed.

    3. Click the + icon on the Redundancy Status table.

      The Add Redundant Cluster window is displayed.

    4. On the Add Redundant Cluster window, specify the following details:

      1. Assign an Initial Role to the Current Cluster—Assign the initial role to the HPE Aruba Networking Central On-Premises cluster that you are currently accessing. The available options are Primary or Secondary. If primary is already configured, then secondary must be assigned.

        Initial role configuration is used for the following:

        • When enabling the redundancy, the initial role is used for assigning the roles.

        • If a role mismatch is encountered in the redundancy, the initial role may be used for determining the new primary.

      2. Specify DR Pairing Key of Peer Cluster—This is the key of the peer cluster, it is required for the pairing. Copy the key by clicking Copy DR Pairing Key To Clipboard on the Redundancy Status table from the WebUI of the other HPE Aruba Networking Central On-Premises cluster.

    5. Click Add.

      One HPE Aruba Networking Central On-Premises cluster is successfully added.

    6. Click the Enable Redundancy toggle switch.

      The redundancy is successfully configured for one cluster. For information about how to enable autofailover, see Enabling Autofailover.

    7. Similarly, add the second cluster. Follow the same procedure as mentioned from step numbers 3 to 6.

      After enabling datacenter redundancy on secondary cluster, it goes into the maintenance mode. The backup data from the primary cluster is restored in the secondary cluster.

      Both the clusters are displayed in the Redundancy Status table. The following details are displayed:

      • Appliance—Name of the HPE Aruba Networking Central On-Premises application.

      • Current Role—The role of the appliance.

      • Status—The health status of the appliance. After clicking the Enable Redundancy toggle switch, it takes approximately 10 minutes to process. The Status column displays Good for both the clusters indicating that configuration is successful.

      • Last Heartbeat Received from Peer—Time stamp indicating when the latest health status was checked.

      • Time to Failover (in minutes)—The time specified for the failover. This is applicable only for the automatic failover method.

    Figure 1  Configuring Redundancy