PowerChute 4.3.0 + VMware vCenter and ESXi host shutdown flow

[BillP]

Hi team

In PC 4.3 I like to have PC to shutdown the VM's and afterwards vCenter and then the both ESXi hosts. But it went a bit strange:

1. simulate the shutdown seq by removing the NMC communications
2. almost directly the VM's are shutdown, except from vCenter and PCNS.
3. Took a while then ESX2 got a shutdown, PCNS was running on that host
4. PCNS got booted at ESX1, and start vCenter
5. PCNS scans for triggers and sees that the comm with NMC still is disconnected
6. vCenter shutdown
7. PCNS and ESX1 will never shutdown.

How can i overcome the last steps to shutdown everything?

06/12/2019 18:53:24 PowerChute cannot communicate with the Network Management Card.
06/12/2019 18:53:24 UPS critical event: PowerChute cannot communicate with the NMC.
06/12/2019 18:53:24 Shutdown sequence started on Hosts esx2.domain.x, esx1.domain.x in response to UPS critical event: PowerChute cannot communicate with the NMC.
06/12/2019 18:53:25 Shutting down VMs on Host esx1.domain.x.
06/12/2019 18:53:25 Starting vApp shutdown process.
06/12/2019 18:53:25 No vApp to shutdown on Host esx1.domain.x.
06/12/2019 18:53:27 Shutting down VMs on Host esx2.domain.x.
06/12/2019 18:53:42 Cannot connect to https://192.168.1.16:443
06/12/2019 18:55:37 Shutting down vCenter Server VM vCenter.
06/12/2019 18:57:46 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.

06/12/2019 19:01:15 PowerChute is attempting to open UDP port 3052.
06/12/2019 19:01:15 PowerChute successfully opened UDP port 3052.
06/12/2019 19:01:18 Cannot connect to https://192.168.1.16:443
06/12/2019 19:01:19 PowerChute Network Shutdown version 4.3.0 monitoring started.
06/12/2019 19:01:19 PowerChute is attempting to open TCP port 6547.
06/12/2019 19:01:19 PowerChute is attempting to open TCP port 3052.
06/12/2019 19:01:19 PowerChute successfully opened TCP port 3052.
06/12/2019 19:01:19 PowerChute successfully opened TCP port 6547.
06/12/2019 19:02:39 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.

06/12/2019 19:02:39 Attempting to start vCenter Server VM vCenter.
06/12/2019 19:03:15 PowerChute cannot communicate with the Network Management Card.
06/12/2019 19:03:15 UPS critical event: PowerChute cannot communicate with the NMC.
06/12/2019 19:03:15 Shutdown sequence started on Hosts esx2.domain.x, esx1.domain.x in response to UPS critical event: PowerChute cannot communicate with the NMC.
06/12/2019 19:03:15 PowerChute cannot locate the vCenter Server VM in the Inventory. See the troubleshooting section in the Online Help.
06/12/2019 19:03:18 Cannot connect to https://192.168.1.16:443
06/12/2019 19:03:33 Shutting down VMs on Host esx1.domain.x.
06/12/2019 19:03:33 Cannot connect to vCenter Server. PowerChute will not be able to perform vApp Shutdown.
06/12/2019 19:05:34 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
06/12/2019 19:05:49 Could not enter maintenance mode on Host esx2.domain.x.
06/12/2019 19:05:52 Shutdown Host failed for Host esx2.domain.x.

[BillP]

Hi,

The PCNS VM should not be migrated to another host. Do you have HA enabled? If so what are the settings and is migration enabled in PCNS?

On 6/12/2019 2:05 PM, Rob said:

06/12/2019 19:05:49 Could not enter maintenance mode on Host esx2.domain.x.
06/12/2019 19:05:52 Shutdown Host failed for Host esx2.domain.x.

This looks to be a permissions issue. Please see setting up users starting on page 58 of the User's Guide. 

[BillP · Accepted solution]

Hi Bill

I think you're right, there was an issue with a none conclusive DNS record which prevents the host from reaching the AD.

tnx Rob