Table of Contents
Advertisement
Chapter 5: Troubleshooting software issues
This section contains information and procedures for troubleshooting software issues.
Related links
Troubleshooting Avaya Aura Communication Manager in an Avaya Aura Virtualized Environment
page 34
ESXi host alarm after VMware 6.0 Update 3A upgrade
vCenter Server inaccessible after server failure or unexpected server reboot
Reconfiguring a cluster
Timeout error configuring High Availability in vCenter
Backing up and restoring vCenter configuration
Recovering from a failed VCSA 5.5 upgrade
Avaya Aura VMs do not recover
Troubleshooting Avaya Aura
an Avaya Aura
The issues in the following section are encountered when running Avaya Aura
Manager in an Avaya Aura
Servers are temporarily in an active / active state
Condition
®
Avaya Aura
Communication Manager servers temporarily run in an active / active state in a
duplicated server configuration. The active server becomes unresponsive, Avaya Aura
Communication Manager interchanges to the standby server, and the unresponsive server returns
to an active state. Avaya Aura
the arbiter resolves the dual state and returns one server to standby status.
Cause
®
Avaya Aura
Communication Manager is working as designed. There is an underlying cause in the
overall solution configuration that needs to be addressed.
Solution
October 2017
on page 37
on page 43
®
Virtualized Environment
®
Virtualized Environment such as the Avaya Pod Fx.
®
Communication Manager then runs in an active / active state until
Troubleshooting the Avaya Pod Fx
Comments on this document? infodev@avaya.com
on page 36
on page 39
on page 41
on page 42
®
Communication Manager in
on page 37
®
Communication
®
™
on
34
Advertisement
Table of Contents
Troubleshooting
