Standard operation: Basic CMS HA setup

In the following example, the primary and secondary CMS servers are in different data centers. Both CMS servers connect to the same Communication Manager. The secondary CMS server sends a Heartbeat signal to the primary server every 20 seconds to verify connectivity.

Standard operation: Dual-IP setup

The following example illustrates a dual-IP setup featuring a main Communication Manager and an ESS. The links to the main Communication Manager remain connected and active in this scenario. Links to the ESS are not connected. With the dual-IP feature, the main Communication Manager and ESS cannot both be active and connected to the same CMS ACD simultaneously.

In this scenario, Admin-Sync pushes administrative data from the primary CMS to the secondary CMS in real time.

Failure scenario: Primary CMS server is down

In this basic HA setup example, the primary CMS server is down due to a network or hardware failure. The Heartbeat signal indicates a primary CMS server failure. Therefore, the secondary CMS automatically becomes the active server.

Failure scenario: Communication Manager link is not working

An outage can also occur due to a failure of the Communication Manager link. The Heartbeat signal from the secondary CMS to the primary CMS continues to work as expected. In this situation, the secondary CMS server does not detect that the link to the primary CMS failed. Therefore, set the secondary CMS as the active server.