PowerChute Network Shutdown shuts down an ESXi host in vSAN cluster before it has been moved to maintenance mode.

Search FAQs

You are currently viewing the content available in Vietnam. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.

Issue:
PowerChute Network Shutdown shuts down an ESXi host in vSAN cluster before it has been moved to maintenance mode.

Product Line:
PowerChute Network Shutdown (PCNS) version 4.2

Environment:

vSAN cluster containing 3 x VMware ESXi 6.5 Hosts (H1, H2, H3)
All servers are protected by 1 UPS
PowerChute and vCenter Server are installed on a physical server outside the HA cluster
Data is located on ESXi Hosts H1 & H2, H3 is a witness server, VM setting is "FTT = 1"

Symptoms:

PowerChute starts a shutdown sequence and the hosts set to move to maintenance mode
ESXi hosts H1 and H3 move to maintenance mode as expected
ESXi host H2 does not move to maintenance mode

Note: The following message appears in the Event Log indicating that a host has failed to enter maintenance mode:

Failed to enter maintenance mode on Host <H2>

ESXi hosts H1, H2 & H3 are shut down.

Cause:
There is a known VMware issue whereby the last host is unable to move to maintenance mode.

Resolution:
Upgrade to PowerChute Network Shutdown 4.3