Managing data center failures Case 1: The primary data center fails

Last Updated : Jun 26, 2020 |

Procedure

  1. Determine whether the System Manager failure is severe.

    • If you can gain access to the primary System Manager in a short duration, restart the primary System Manager and keep the secondary System Manager in the standby mode. In this case, do not follow the procedure in this section.

    • If you cannot gain access to the primary System Manager in a short duration, activate the secondary System Manager and continue to follow the procedures in this section.

  2. Manually activate the secondary System Manager using the Geographic Redundancy webpage of the secondary System Manager.

    For more information about activating the secondary System Manager server, see Administering Avaya Aura® System Manager. Manual activation of the secondary System Manager takes between 10 to 20 minutes. Wait until the secondary System Manager is accessible.

    Avoid making any changes to the call routing configuration, the user configuration, or the network configuration administration on the secondary System Manager. Retaining the same configuration as on the primary System Manager simplifies the process of restoring the system back into the sunny day configuration.

  3. Verify that the secondary System Manager is active. Confirm this fact by viewing the Geographic Redundancy webpage of the secondary System Manager.
  4. Verify that the secondary System Manager is managing all the Session Manager instances that are Geographic Redundancy-aware.

    For more information about determining the System Manager that manages a Geographic Redundancy-aware, see Administering Avaya Aura® System Manager.

  5. Reconfigure Geographic Redundancy-unaware elements to use the secondary System Manager. Run the changeMgmtIP command from the Session Manager command line to reconfigure the Session Manager to use the secondary System Manager.

    For more information about changing the IP address or FQDN in System Manager, see Maintaining Avaya Aura® Session Manager.

  6. Verify that the data replication from the secondary System Manager to the Session Manager elements is working.

    To verify the data replication, view the Replication page of the secondary System Manager.

    For more information, see the Managing system data section.

  7. In the Session Manager > System Status > User Registrations webpage of the secondary System Manager, verify that the endpoints can complete the registrations.

    For more information, see the User Registration section.

  8. On the secondary System Manager web console, using the Session Manager > System Tools > Maintenance Tests webpage, perform the maintenance tests on the Session Manager instances that are managed by the secondary System Manager.

    For more information, see the Maintenance tests section.

  9. After the primary System Manager comes back to service, recover the server and configure the secondary System Manager to the standby mode similar to the sunny day scenario. Follow the steps as mentioned below:
    1. Deactivate the secondary System Manager by using the Geographic Redundancy webpage from the secondary System Manager.
      Note:

      For more information about deactivating the secondary System Manager server, see Administering Avaya Aura® System Manager.

      Manual deactivation of the secondary System Manager takes between 10 to 20 minutes.

    2. Verify that the secondary System Manager is in the standby mode by checking the Geographic Redundancy webpage of the primary System Manager.

      Logging in to the secondary System Manager web console must indicate that the System Manager is in the standby mode.

    3. From the primary System Manager, run the database recovery procedure in the Geographic Redundancy webpage.

      Using this step, you can keep the current primary System Manager database or replace with the secondary System Manager database. For more information about restoring the primary System Manager server, see Administering Avaya Aura® System Manager.

    4. Verify that the primary System Manager is managing all the Geographic Redundancy-aware elements.

      For more information about determining the System Manager that manages a Geographic Redundancy-aware, see Administering Avaya Aura® System Manager.

    5. Reconfigure the Geographic Redundancy-unaware elements to use the primary System Manager. To reconfigure a Session Manager to use the primary System Manager, run the changeMgmtIP command from the command line.

      For more information about changing the IP address or the FQDN, see Maintaining Avaya Aura® Session Manager.