Skip to main content

SMGR - Geographic Redundancy

To configure geographic redundancy for Avaya System Manager 8.0, you will need to perform the following steps:

  1. Determine the roles of the System Manager instances: The primary instance will be the active instance, and the secondary instance will be the standby instance.

  2. Ensure that both instances are running the same software version and have the same licenses and certificates installed.

  3. Configure network connectivity between the two instances, including IP addressing, routing, and firewalls.

  4. Configure the primary instance to replicate data to the secondary instance. This can be done using the System Manager web interface:

    a. Log in to the System Manager web interface for the primary instance.

    b. Navigate to the System Manager Settings page.

    c. Select Geographic Redundancy from the left-hand menu.

    d. Enter the IP address of the secondary instance in the Remote System Manager IP field.

    e. Select the types of data to replicate to the secondary instance, such as configuration data, system logs, and alarms.

    f. Click the Save button to save the configuration.

  5. Configure the secondary instance to receive replicated data from the primary instance. This can also be done using the System Manager web interface:

    a. Log in to the System Manager web interface for the secondary instance.

    b. Navigate to the System Manager Settings page.

    c. Select Geographic Redundancy from the left-hand menu.

    d. Enter the IP address of the primary instance in the Primary System Manager IP field.

    e. Click the Save button to save the configuration.

  6. Verify that the replication is working correctly by checking the replication status on both instances. This can be done using the System Manager web interface:

    a. Log in to the System Manager web interface for either instance.

    b. Navigate to the System Manager Dashboard page.

    c. Check the Replication Status section to ensure that replication is occurring successfully.

  7. Test the failover process by simulating a failure of the primary instance. This can be done by shutting down the primary instance or disconnecting it from the network.

    a. After the primary instance has failed, the secondary instance should automatically assume the active role.

    b. Verify that users are able to access the System Manager web interface and that all data is available.

    c. Once the primary instance is back online, it will automatically assume the standby role and begin replicating data from the secondary instance.

Note that geographic redundancy requires careful planning and testing to ensure that it is configured correctly and working properly. It is also important to regularly test the failover process to ensure that it will work correctly in the event of a failure.

If host is not set on secondary SMGR it wont work we need to run changeVFQDN and match the virtual FQDN from Primary server

Back to top