ESXi Network shutdown on VM Guest

[BillP]

Hi,

we have two ESXi hosts in the branch offices around the globe named "CityVM01a" and "CityVM01b".
The ESXi hosts "CityVM01a" and "CityVM01b" and the ESXi hosts from other branch offices are configured over a VCenter Appliance that are running in a big VMCluster in the CityHQ.
On ESXi host "CityVM01a" we have 2 productive VMs with Windows Server 2012 and one VM with Windows10 online.
On ESXi host "CityCM01b" we have a replica from Veeam of the two 2012 Servers (a offlinecopy) from ESXi host "CityVM01a" and two running Windows10 VMs online.
On one of the Windows10 Vms on ESXi host "CityCM01b" we installed the network shutdown software with the connectivity over the management card to the UPS in the branche office.

Config of Power Chute
Configure Events: UPS on Battery / Enabled shutdown / Delay 180 sec.
Virtualization Settings: VM Shutdown enabled / Duration 300 sec. / VM Startup disabled

If the Power is gone the UPS bring afther 300 sec. the ESXi "CityVM01a" in maintenance and shuting down all VMs. The "CityVM01b" are unable to go to maintenance but the VMs are shutting down also.
The ESXi Host "CityVM01a" are shutting down afther the next 300 sec. but the ESXi Host "CityVM01b" have no VMs online are still running and crashing if the battery is empty.

Whats wrong? Is the "CityVM01b" not in maintenance because the powerchute agent is running on a VM on this host?
Is there a other solution to handle this scenario with no additional VM/Appliance?

Thanks for any help and comments

Best regards Stefan

[BillP]

Hi,

On 9/1/2016 10:22 AM, Stefan said:

On one of the Windows10 Vms on ESXi host "CityCM01b" we installed the network shutdown software with the connectivity over the management card to the UPS in the branche office.

This is not a supported configuration. Please review Application Note 180 for supported configurations. We support running PCNS on a standalone Windows system not a VM when vCenter is running at a remove location. 

[BillP]

Hi Bill,

can you explain where the problem is?

In App Not 180 on picture "B) Both vCenter Server and PowerChute are running on Virtual Machines" in the same cluster.

Ok but we have the same config but with the vCenter in a other location. But the vCenter have the full time access to the ESXi hosts so that cannot be the problem. And if the vCenter are not accessible we have local users on the ESXi hosts like in your documentation.

Can you pls clear the situation, thanks.

regards stefan

[BillP · Accepted solution]

Hi,

In Application Note 180 on page 11 and 13 we provided diagrams the show PCNS running at 2 locations and vCenter running at only 1 of them. This is similar to your configuration with the exception that you have vCenter running at a third location. In neither diagram is PCNS running on as a VM. What image are you referring to?  If you are referring to the diagram on page 4 that is not applicable to your configuration. That diagram is for PCNS and vCenter to be install at a single location and controlling a single location.