Prerequisites for Geographic Redundancy setup

Last Updated : Oct 12, 2023 |
Prolog information
In a Geographic Redundancy setup, the two standalone System Manager servers that you designate as primary and secondary, must meet the following requirements:
  • Contain the same version of the software that includes software packs.
  • Contain the same profile for primary and secondary System Manager Geographic Redundancy virtual machines.
    For example, if the primary System Manager contains Profile 2, the secondary System Manager must also contain Profile 2.
  • Contain the same version of the System Manager software that includes service pack and software patches.
  • Contain the same parent domain names for two System Manager systems.
    For example, http://smgr.abc.com and http://smgr.xyz.com are invalid domain names because the parent domain names abc and xyz are different.
  • Communicate with each other over the network by using the IP address and fully qualified domain name (FQDN).
  • Synchronized network time.
  • Use DNS to ensure the name resolution is automatic. Otherwise, you must resolve the IP address and host name in the /etc/hosts file on the primary and secondary System Manager servers.
  • The required ports must be open to support the Geographic Redundancy feature. For port usage information, see Avaya Aura® System Manager on the Avaya™ support website at http://support.avaya.com/.
  • Must have T1 as the minimum data transfer speed between primary and secondary System Manager servers. T1 provides a speed of 1.544 Mbps.
  • Network latency less than 500 ms.