vCenter Server inaccessible after server failure or
unexpected server reboot
The VMware vCenter Server status shows Stopped and fails to Start. In normal operation, status
shows Running.
Occurrence of issue: very rare
Overall completion: approximately 1 hour
Cause
A host server failure or unexpected reboot of the host server with the vCenter Appliance and the
vCenter database virtual machines, which causes the vCenter appliance and the vCenter database
server to be migrated to a new host. This results in a temporary interruption in access to vCenter. If
vCenter cannot be reached or accessed after 15 minutes, the vCenter appliance can have issues
with the services starting up. The message states
vpxd failed to start
.
Contact Avaya Support for advanced troubleshooting and repair.
Solution
1. Log in to the vCenter web interface located at:
https://<vCenter_ip_address:5480>
.
2. Click
Summary
.
3. In the vCenter Server section, click
Start
to restart the Server process.
4. Verify that the status changes to
Running
.
vCenter is back online. Proceed to
on page 37 for the procedure to
configure the cluster.
Related links
Troubleshooting software issues
on page 34
Reconfiguring a cluster
About this task
This procedure is used to reconfigure a cluster after an unexpected shutdown of the Avaya Pod Fx.
Procedure
1. On the Management Server Console, launch the vCenter vSphere Client, and log in.
Important:
Administrator must have advanced knowledge of VMware and vCenter.
The vCenter screens do not show any administration.
2. Use the wizard to create a Data Center and Cluster.
3. Add the hosts to the Cluster.
vCenter Server inaccessible after server failure or unexpected server reboot
October 2017
Troubleshooting the Avaya Pod Fx
™
37