In a Geographic Redundancy setup, the two standalone System Manager servers that you designate as primary and secondary servers 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, smgr.abc.com and 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 FQDN.
In the Geographic Redundancy setup, the primary and secondary System Manager must use the same VFQDN.
Have a synchronized network time.
Use DNS to ensure that the name resolution is automatic. Otherwise, you must resolve the IP address and the host name in the /etc/hosts file on the primary and secondary System Manager servers.
Have open required ports to support the Geographic Redundancy feature. For port usage information, see Avaya Port Matrix: Avaya Aura® System Manager on the Avaya Support website at http://support.avaya.com/.
Have T1 as the minimum data pipe between the primary and the secondary System Manager server. T1 provides 1.544 Mbps.
Have network latency that is less than 500 ms.
In the Geographic Redundancy setup, if you need to configure the outbound firewall rules, then you need to add the peer IP addresses on the primary and secondary System Manager servers.
