Avaya Oceana® provides the Campus High Availability (HA) functionality. Using this functionality, Avaya Oceana® can automatically recover from a single point of failure.
Note:
In this chapter, the terms virtual machine and node refer to a virtual server that hosts the Avaya Breeze® platform.
This functionality provides mitigation for the following failure scenarios:
A single Avaya Oceana® process outage at a time.
A single virtual machine outage at a time.
A single physical server outage at a time.
A single network link outage at a time.
The following are the advantages and limitations of Avaya Oceana® HA:
Avaya Oceana® successfully processes new contacts after the outage.
Agents and supervisors successfully operate after the outage.
Loss of active and queued contacts and sessions can occur during the outage.
Avaya Analytics™ reports can contain incorrect or missing metrics after the outage.
The outage period counts the time taken to detect the failure and the time taken to fail over to backup processes.
The following table lists the concepts used in Avaya Oceana® HA:
Concept |
Description |
Failure Event |
Specifies one of the following single failure scenarios:
Failure of a single process. Failure of a single virtual machine. Failure of a single physical server. Failure of both network links to a virtual machine. Failure of all network links to a single physical server. |
Network Failure |
Specifies one of the following network failures:
Failure of all network links to a virtual machine. For example, the failure of a virtual network adaptor on a virtual machine isolates the virtual machine from the network. Failure of all network links to a single physical server. For example, the failure of all network adaptors on a physical server isolates the physical server from the network. Avaya Oceana® does not detect the network latency directly. The Avaya Breeze® platform detects all severe network issues and triggers a failover of the virtual machine or process. When a network failure isolates a virtual machine or a physical server from the network, manual intervention is required before the virtual machine or physical server can reconnect to the network. When a network failure isolates a virtual machine or a physical server from the network, Avaya Oceana® identifies and shuts down WAS and GigaSpaces on the isolated virtual machine or physical server. |
Process Failure |
Specifies the failure of a single process in Avaya Oceana®. For example, the failure of the WebSphere Application Server process or a GigaSpaces PU instance. |
Server Failure |
Specifies the failure of a single virtual machine or a single physical server. This failure implies that all process instances within the virtual machine or the physical server are lost. |
Avaya Oceana® only supports a single failure event. Therefore, if two simultaneous failure events occur, Avaya Oceana® components cannot operate in HA mode.
Avaya Oceana® supports HA in the following failure scenarios:
Network failure on the physical server hosting the Avaya Oceana® Cluster 3 - Avaya Breeze® platform node (Active Load Balancer) and Active Omnichannel Database.
Power failure on the physical server hosting the Avaya Oceana® Cluster 3 - Avaya Breeze® platform node (Active Load Balancer) and Active Omnichannel Database.
Network failure on the physical server hosting the Avaya Oceana® Cluster 2 - Avaya Breeze® platform node (Active Load Balancer).
Power failure on the physical server hosting the Avaya Oceana® Cluster 2 - Avaya Breeze® platform node (Active Load Balancer).
Network failure on the physical server hosting the Avaya Oceana® Cluster 1 - Avaya Breeze® platform node (Active Load Balancer and Database), Active Application Enablement Services, and Active Communication Manager.
Power failure on the physical server hosting the Avaya Oceana® Cluster 1 - Avaya Breeze® platform node (Active Load Balancer and Database), Active Application Enablement Services, and Active Communication Manager.
