Data Center 1 complete failure with geo-redundancy or disaster recovery
Impact
All agents assigned to the Avaya Hybrid Cloud Gateway cluster 1 lose the SIP signaling connections to Avaya Aura®. The existing calls are in the media preservation mode if the call media does not go through the AAMS or GXXX media gateways in Data Center(DC) 1. Otherwise, the call media becomes non-functional. Media-preserved calls have no access to mid-call features. No new calls can be made or received. Avaya Workspaces displays the error message to the impacted users.
HCG Signaling Connector recovery
A total DC 1 failure triggers a failover to DC 2. To recover the Avaya Experience Platform™ (On-Prem + Connect) functionality, the administrator must manually perform the following steps:
Configure the Communication Manager-1 element in Application Center Administration and map it to Avaya Hybrid Cloud Gateway cluster 2. When Communication Manager-1 and Session Managers of DC 1 are non-functional, the agent login and call routing work automatically with the active Session Manager of DC 2 with survivable server core-1.
The configuration change triggers the Avaya Experience Platform On-Prem ADF connector to auto re-register the affected Avaya Workspaces endpoint to UC3.
For all the agents logged in to Communication Manager-1 before the failure, the agent login and call routing works automatically with the active Session Manager of DC 2 with survivable server core-1 after the SIP station is re-registered from Avaya Hybrid Cloud Gateway cluster 2.
HCG Admin Services recovery
During an outage, Cloud Ops cannot access the Avaya Hybrid Cloud Gateway cluster in DC 1. However, Cloud Ops can access the Avaya Hybrid Cloud Gateway cluster in DC 2.
HCG Signaling Connector return to normal
The failback to a recovered Communication Manager is a manual process performed during a maintenance window.
In this scenario, Communication Manager is recovering from a complete DC failure, which is also a manually controlled failback process.
Configure the Communication Manager-1 and remap it from Avaya Hybrid Cloud Gateway cluster 2 to Avaya Hybrid Cloud Gateway cluster 1 in Application Center Administration.
The agents logged in to Survivable Server Core-1 before the DC 1 was restored. After the SIP station is re-registered from Avaya Hybrid Cloud Gateway cluster 1, the login and call routing agent works automatically with the active Session Manager of DC 1 with Communication Manager-1 .
HCG Admin Services return to normal
After the DC 1 is functional, the admin services in the new primary node on the Avaya Hybrid Cloud Gateway cluster 1 can support the Cloud Ops remote access.
