Case 6: The primary System Manager cannot communicate with the system elements, but the elements can communicate with the secondary System Manager

Last Updated : Oct 09, 2020 |

Procedure

  1. 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.

  2. Verify that the secondary System Manager is managing all the geographical redundancy-aware Session Manager instances.

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

  3. Reconfigure the 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 the FQDN, see Maintaining Avaya Aura® Session Manager.

  4. Deactivate the secondary System Manager using the Geographic Redundancy webpage of the secondary System Manager.

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

    Note:

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

  5. 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 standby mode.
  6. From the primary System Manager, run the database recovery procedure from the Geographic Redundancy webpage. Using this step, you can keep the current primary System Manager database or replace with the database from the secondary System Manager.

    For more information about restoring the primary System Manager server, see Administering Avaya Aura® System Manager.

  7. 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 geographical redundancy-aware element, see Administering Avaya Aura® System Manager.

  8. 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.