AE Services Server supports a virtual IP address for each of the eth0, eth1 and eth2 interfaces. To be able to administer a virtual IP address, these interfaces must have a valid IP address. AE Services continues to support HA configuration without any virtual IP addresses configured. In such a configuration, the AE Services Server client applications connect one of the two IP addresses associated with each of AE Services Servers’ client connectivity interfaces. This is dependent on the AE Services Server that is active.

GRHA is enhanced with the following changes:

1. Registration states are replicated, as they happen over a newly created socket (TLS) connection between active and standby AE Services server.

2. Registration states are kept in memory in the /dev/shm/resq directory.

   Note:

   /dev/shm is a memory file system.

3. Virtual IP addresses can be configured for public, private and OOBM interfaces.

Since GRHA performs a synchronous update for session states, it can be used in place of FRHA.

Using virtual IP addresses have significant advantages:

• The client application can use the same IP address to connect to the active AE Services GRHA server. The client application does not have to maintain two different AE Services Server IP addresses

• If a virtual IP address is also used for Switch and Media Connectivity, any DMCC associations that are currently in place at the time of a GRHA fail-over will be automatically recovered by the new active AE Services server. The associations include the following:

  • DMCC client sessions

  • DMCC devices and device monitors

  • DMCC station registrations

  • DMCC call associations

  • DMCC system registrations.