Technical FAQs

Ask a Question

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

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

  • 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"
  • 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.
There is a known VMware issue whereby the last host is unable to move to maintenance mode.

For Windows:
  • Follow the Steps below to run the patch,
1. Stop PCNS Service - net stop pcns1
2. Edit pcnsconfig.ini and add "Skip_Maintenance_Mode = true" to [HostDetails] section of ini file.
3. Replace pcns.jar (C:\Program Files\APC\PowerChute\group1\comp folder) with patched version of the jar.
4. Re-start PCNS Service - net start pcns1
  • Install teraterm macro function
Place both files attached to this FAQ in the directory that PCNS is installed in (e.g. C:\Program Files\APC\PowerChute\group1 on Windows).
  • vSAN_shutdown.bat
  • vSAN_shutdown_macro.ttl
  • Confirm or modify the file-path in "vSAN_shutdown.bat"
  • Modify the configurations in vSAN_shutdown_macro.ttl to match your system configuration
  1. Num=3 (Number of ESXi hosts)
  2. ESXi_HOST_IP[1] = '' (Input all ESXi hosts from [1])
  3. UserName = 'root' (Input username to log into all ESXi Hosts)
  4. Password = 'root' (Input password to log into all ESXi Hosts)
  • Set "vSAN_Shutdown.bat" as the Shutdown command file in PCNS.
  • It is preferred to add each host as known host manually through tera terminal tool.
  • Script outputs the simplified logs(vSAN_shutdown_log.txt) in the location "C:\Program Files\APC\PowerChute\group1" can be used for troubleshooting.
  • It is preferred to estimate and provide enough time for each host to run the commands.
  • There may be an inconsistency in the sequence of events in the Task Console of the vCenter Web Client. It can appear that the host has entered maintenance mode after the host shutdown has been initiated.
Was this helpful?
What can we do to improve the information ?