Browse FAQs

Why do ESXi hosts show as disconnected after being shut down by PowerChute Network Shutdown when the vCenter Server is also shut down?

Published date: 10 July 2019

Issue:
ESXi hosts are disconnected in vCenter Server after being powered on following a UPS critical event where PowerChute Network Shutdown has also shut down the vCenter Server physical machine.

Product Line:
PowerChute Network Shutdown version 3.1

Environment:
VMware vCenter Server

Cause:
This issue occurs when using an administrator account in PowerChute Network Shutdown that only exists in vCenter instead of an Active Directory or Local User account that exists on both the ESXi hosts and vCenter Server. When the ESXi hosts come back online before the vCenter Server has fully started they incorrectly return their PowerState as PoweredOff to the VMware Java APIs. This prevents PowerChute from starting VMs and performing other tasks correctly. To avoid this issue PowerChute will disconnect and re-connect the host. When the local administrator is configured in PowerChute vCenter Server Settings, PowerChute was incorrectly using these credentials to try to re-connect the ESXi hosts and this failed since the local administrator account does not have access to the ESXi hosts.

Resolution:
1. The recommended solution is to Install PowerChute Network Shutdown version 4.x and configure VMware SSO and use an Active Directory or Local User account in PowerChute that has permissions on both vCenter Server and the ESXi hosts.

Please review Application Note 180 and PowerChute VMware Users Guide

 


Was this helpful?

What can we do to improve the information ?

Can't find what you are looking for?

Reach out to our customer care team to receive information on technical support, assistance for complaints and more.