PCNS fails to shutdown vmware host which is running vCenter Server VM

[Anonymous user]

Hello all,

I'm experience problems using PCNS 3.1 to gracefully bring down my vSphere environment in the event of a power failure.  Below are the details of my environment, and the problem I'm encountering..

VMware vSphere 5.5, with 2 Host HA cluster

each host has redundant power supplies, each of which is plugged into a dedicated UPS for that host

HOST1-PS1 -> UPS1

HOST1-PS2 -> UPS1

HOST2-PS1 -> UPS2

HOST2-PS2 -> UPS2

Both UPSes have APC Network Management Cards

PowerChute Network Shutdown for Windows 3.1.0 Build 4512 is installed on a physical Windows 7 machine

vCentre Server is installed and running on a Windows Server 2012 VM on HOST1

PCNS is configured using Advanced UPS Configuration as per PCNS User Guide

pcnsadmin users accounts and permissions have been created and assigned as per PCNS for VMware guide

Shutdown sequence has been configured using the PCNS PowerChute Setup wizard

When power is cut to a single UPS (tested on both), the shutdown sequence for the attached Host is initiated, running VM's migrate to the other host, and the affected host shuts down successfully. 

When the power is pulled to both UPSes (power failure simulation), commands are successfully sent to both hosts and all VM's shutdown accordingly.  Host2 also shutdowns properly, however, after the vCentre Server shutdowns on host1, host1 fails to power down.

Question is, does the vCentre Server VM need to be running in order to shutdown the host it is running on or should the PCNS Agent running on the physical machine outside the virtual environment be able to shutdown HOST1 after vCentre powered down? 

Reference Documents

PowerChute Network Shutdown v3.1 User Guide

PowerChute Network Shutdown for VMware

Looks forward to your replies

Thanks,

Derek

[BillP]

Hello Derek,

Is is possible to provide the event log, debug log and pcnsconfig.ini please? To enable debug logging please refer to KBase FA230514. Link to the KBase is below::

http://www.apc.com/site/support/index.cfm/faq/

What could be happening here is that the vCenter VM is being shutdown along with the rest of the VM's. PowerChute is unable to locate the vCenter VM and therefore shutting it down too early with the rest of the VM's. It is very important that VMware tools is installed on the vCenter VM.

Can you tell me if you see the vCenter icon(green icon) beside Host1 on the VMware Protection page? See screenshot:

Are the hosts added to the vCenter server using the IP address or FQDN?

Please make sure that there are no old copies of VM's in the inventory that are using the same IP address/FQDN/hostname as the vCenter VM. PCNS can detect this and miss the live vCenter VM and this can happen if the old VM's are even powered off.

Is the DNS on a VM or a physical machine? If its on a VM, and being shutdown with the rest of the VM or otherwise offline. You may want to refer to KBase FA166844.

Is your physical machine powering the PowerChute agent being powered by either of these UPS's or a separate UPS? If so, you may want to refer to KBase FA235983.

Regards,

B

[Anonymous user · Accepted solution]

Thanks B,

To answer your questions...

I've attached the event log, debug log and pcnsconfig.ini files for your review.

I've also attached a screen capture of the vCenter VM status, confirming that VMware Tools is installed and running on the vCenter VM.

I've also attached a screen capture confirming that the vCenter icon is displayed in the VMware Protection page, under the appropriate host (HOST1).

The hosts would have been added to vCenter by IP address.

I don't see any old copies of VMs in the inventory that are using the same IP/FQDN/hostname as the vCenter VM.

DNS is running on one of the VM's on HOST2, and this VM is one of the ones being shutdown automatically by PCNS when HOST2 shutdown is initiated (before the vCenter VM & HOST1 shutdown).

The physical machine running the PowerChute agent is not attached to either of the UPSes that either host is connected to.  It's connected via USB to it's own UPS (without a network management card).