The following actions should be taken to address the underlying cause of the dual active state:
• Datastore architecture should be designed to tolerate drive failures, controller failures, and
connectivity issues without disruption. The active and standby servers should be located on
separate datastores.
• Avaya Aura
®
Communication Manager CPU reservations should be used if ESXi hosts are
oversubscribed. See
Deploying Avaya Aura
®
Communication Manager on VMware
®
in
Virtualized Environment (6.x VE only)
and
Deploying Avaya Aura
®
Communication Manager in
Virtualized Environment (7.x VE and AVP)
for reservation guidelines.
• VMware recommends only allocating to a virtual machine as many virtual resources as it
requires. Allocating more resources than necessary can, in some cases, reduce VM
performance as well as the performance of other VMs on the same host. See the section
ESXi
CPU Considerations
in
Performance Best Practices for VMware vSphere 6.0
in the VMware
6.0 documentation for more information.
Link bandwidth or connectivity issues cause non-deterministic behavior
Condition
Active / active states, filesync failures, server interchanges, server resets, or other non-deterministic
behavior.
Cause
Duplication link bandwidth or connectivity issues might cause active / active states, filesync failures,
server interchanges, server resets, or other non-deterministic behavior.
Solution
The duplication link must have a total capacity of 1Gbps that is dedicated to CM duplication. The
duplication link interface should be a separate and dedicated interface. See
PSN003556u
on the
Avaya Support website for additional information. See
Duplicated Avaya Aura
®
Communication
Manager on VMware
for best practices on deploying duplicated CM servers in a VE configuration. It
should be referenced for any duplicated CM VE deployment.
Snapshots can adversely impact service
Condition
Use of snapshots on Avaya Aura
®
Communication Manager can cause interchanges or adversely
impact service in other ways. Extreme caution must be exercised when using virtual machine
snapshots with Avaya Aura
®
Communication Manager deployed on VMware.
Solution
The following must be understood if you are considering the use of snapshots:
• Snapshot operations should never be performed on the active VM. The application must be
stopped and placed out of service before performing snapshot operations.
• The application should be started and brought back into service after the snapshot operation is
complete.
• If the duplex Open Virtual Application (OVA) is in use, snapshot operations should be
performed on the standby CM VM after ensuring the standby is refreshed. If a snapshot is
taken on the active VM a service impacting interchange is likely to occur.
Troubleshooting Avaya Aura
®
Communication Manager in an Avaya Aura
®
Virtualized Environment
October 2017
Troubleshooting the Avaya Pod Fx
™
35