PowerChute on Windows PC failing to action Maintenance Mode on ESXi Hosts.

[CBT]

Greetings,

I have several issues with PowerChute configuration/setup.

My environment is configured as follows:

1 x Windows PC with PowerChute Network Shutdown installed & configured to LAN.

2 x Dell Poweredge R430 (installed withe ESXi 7 Hosts & vCenter Server Appliance VM + Multiple Guest VMs).

1 x APC Smart UPS with Network Management Card.

1 x Synology RS815RP+ NAS

1. Shutdown sequence of Group 1 & Group 2 are inverted (Group 1 - 192.168.1.247 shutdown command initiated first instead of Group 2 192.168.1.249 first).

2. All VMs shutdown including vCenter Server Appliance VM but fails to initiate 'Maintenance Mode' on the ESXi Hosts.

I see from the event log 'Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.' this would be due to the VM shutdown commands have already been initiated, the commands i want to issue are for the final shutdown of the ESXi Hosts and assume a scripted file command should be sent direct to via their I.P Address's and NOT via the vCenter Server Appliance which has already been initiated shutdown?

3. Cannot find any instructions on the internet for issuing either a .cmd file or 'SSH' command to shutdown the ESXi Hosts.

Here is the Event Log...

03/19/2022 10:10:20 UPS Outlet Group has turned on.
03/19/2022 10:06:06 ERROR: The ini file is missing shutdownCommandFile key from section Shutdown.
03/19/2022 10:06:06 ERROR: The ini file is missing shutdownCommandFile key from section Shutdown.
03/19/2022 10:05:17 Available runtime has been exceeded.
03/19/2022 10:05:17 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
03/19/2022 10:05:10 Outlet Group Outlet Group 1 is turned off for NMC 192.168.1.239.
03/19/2022 10:05:09 PowerChute successfully accessed TCP port 6547.
03/19/2022 10:05:09 PowerChute is attempting to access TCP port 6547.
03/19/2022 10:05:09 PowerChute Network Shutdown version 4.4.1 monitoring started.
03/19/2022 10:05:07 UPS Outlet Group has turned off.
03/19/2022 10:05:07 Communication has been established.
03/19/2022 10:05:07 PowerChute successfully accessed UDP port 3052.
03/19/2022 10:05:07 PowerChute is attempting to access UDP port 3052.
03/19/2022 09:41:35 Shutting down physical machine that PowerChute is running on.
03/19/2022 09:41:13 Shutdown Host unsuccessful for Host 192.168.1.249.
03/19/2022 09:40:43 Shutdown Host unsuccessful for Host 192.168.1.247.
03/19/2022 09:38:27 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
03/19/2022 09:38:07 Shutting down vCenter Server VM vCenterServer.
03/19/2022 09:36:03 Shutting down VMs on Host 192.168.1.249.
03/19/2022 09:35:51 UPS critical event: Outlet Group Turn off initiated.
03/19/2022 09:35:51 UPS Outlet Group: Outlet Group 1 turn off has been initiated.
03/19/2022 09:35:47 No vApp to shutdown on Host 192.168.1.247.
03/19/2022 09:35:47 Starting vApp shutdown process.
03/19/2022 09:35:47 Shutting down VMs on Host 192.168.1.247.
03/19/2022 09:35:46 PowerChute is turning off UPS 192.168.1.239
03/19/2022 09:35:46 Shutdown sequence started on Hosts 192.168.1.247, 192.168.1.249 in response to UPS critical event: On Battery.
03/19/2022 09:35:46 UPS critical event: On Battery.
03/19/2022 09:35:26 UPS has switched to battery power.

[BillP]

@CBT 

Do you have vCLS enable? If so see Schneider Electric FAQ https://www.apc.com/us/en/faqs/FA416409/

[CBT]

Thanks for the response.

I tried that method a couple of days back, followed all the instructions and it still failed to shutdown the hosts,

I found a method of disabling both the vCLS VMs though the VCSA config file which completely removes them. The shutdown still fails, i'm just analyzing the pcnsconfig.ini and log files to see whats going wrong.