Avaya Pod Fx, Руководство по устранению неисправностей, Страница: 34 / 66

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 on
page 34
ESXi host alarm after VMware 6.0 Update 3A upgrade on page 36
vCenter Server inaccessible after server failure or unexpected server reboot on page 37
Reconfiguring a cluster on page 37
Timeout error configuring High Availability in vCenter on page 39
Backing up and restoring vCenter configuration on page 41
Recovering from a failed VCSA 5.5 upgrade on page 42
Avaya Aura VMs do not recover on page 43
Troubleshooting Avaya Aura
®
Communication Manager in
an Avaya Aura
®
Virtualized Environment
The issues in the following section are encountered when running Avaya Aura
®
Communication
Manager in an Avaya Aura
®
Virtualized Environment such as the Avaya Pod Fx.
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
®
Communication Manager then runs in an active / active state until
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 Troubleshooting the Avaya Pod Fx
™
34
Comments on this document? infodev@avaya.com