Geographic Redundancy overview

Last Updated : Dec 05, 2021 |
Prolog information
Metadata
Keywords:
Avaya Aura® provides System Manager Geographic Redundancy, a resiliency feature that handles scenarios where the primary System Manager server fails or the data network partially loses connectivity. In such scenarios, the system manages and administers products such as Avaya Aura® Session Manager and Avaya Aura® Communication Manager across the customer enterprise using the secondary System Manager server.
For customers who need highly fault-tolerant deployments, System Manager supports System Manager Geographic Redundancy deployments that can provide the Active-Standby mode of resiliency.
From Release 8.0.1, System Manager also supports Geographic Redundancy in a mixed deployment environment.
From Release 7.0.1, System Manager supports deployment on different server types and different deployment modes in Geographic Redundancy. System Manager supports mixed:
  • Servers from any combination of Avaya Supplied Avaya Solutions Platform 130 severs supported for System Manager.
  • The primary System Manager server running as the only Avaya application on the server, while the secondary System Manager running along with other Avaya applications on another server and vice-versa.
  • Servers from both customer-provided virtualized environment and Avaya Solutions Platform 130.
    For example, the primary System Manager server can be on Avaya Solutions Platform 130 and the secondary System Manager server can be on a customer-provided virtualized environment.
The following are some key differences between Geographic Redundancy and High Availability (HA) solutions:
Geographic Redundancy
HA
Addresses sudden, site-wide disasters.
Addresses server outages due to network card, hard disk, electrical, or application failure.
Distributed across WAN.
Deployed within a LAN.
Manual
Automated
You must deploy System Manager on both the standalone servers with separate IP addresses and configure Geographic Redundancy. If a managed product that supports the Geographic Redundancy feature loses connectivity to the primary System Manager server, the secondary System Manager server provides the complete System Manager functionality. However, you must manually activate the secondary System Manager server.
Note:
Only the system administrator can perform Geographic Redundancy-related operations.
You must reconfigure the elements that do not support Geographic Redundancy so that the elements can interact with the secondary System Manager server to receive configuration information. For more information about configuring elements that do not support Geographic Redundancy, see Geographic Redundancy-unaware elements overview.
During the installation of GR-unaware elements such as Presence Server, you must specify whether you want to enable the Geographic Redundancy feature on the element.

Out of Band Management in a Geographic Redundancy setup

When you configure Geographic Redundancy, provide Management network details only. Validation fails if you configure Geographic Redundancy with Public network details. In Geographic Redundancy setup, you do not disable or enable Out of Band Management on both primary and secondary System Manager virtual machine. You can enable Out of Band Management on the primary System Manager virtual machine and disable Out of Band Management on the secondary System Manager virtual machine, and vice versa.