Powerchute 3.01 with two ESXi 4.1 hosts not shutting VMs in power failure

[Anonymous user]

I am running Powerchute pcns 3.01 on Vma connecting to two ESXi 4.1 hosts and connecting to a APC 750XL UPS with a network card. There seems to be a disconnect between the power loss failure and the shutdown command. Is there any way to test this process without actually shutting down all my servers?

The last power failure gave me this log file info:

750XL log:
09/08/2012 14:07:36 UPS: A discharged battery condition no longer exists.
09/08/2012 13:49:03 UPS: The battery power is too low to support the load; if power fails, the UPS will be shut down immediately.
09/08/2012 13:48:50 System: Network service started. System IP is 10.1.1.204 from manually configured settings.
09/08/2012 13:49:02 UPS: Restored the local network management interface-to-UPS communication.
09/08/2012 13:48:49 System: Coldstart.
09/08/2012 12:44:55 UPS: A low battery condition no longer exists.
09/08/2012 12:44:55 UPS: The output power is turned off due to a low battery.
09/08/2012 12:42:21 UPS: The battery power is too low to continue to support the load; the UPS will shut down if input power does not return to normal soon.
09/08/2012 12:12:55 UPS: On battery power in response to an input power problem.

vMA log:
09/08/2012 15:08:33 Available runtime is sufficient.
09/08/2012 15:07:55 Battery has recharged
09/08/2012 14:57:32 Available runtime has been exceeded.
09/08/2012 14:57:14 PowerChute successfully opened TCP port 6547.
09/08/2012 14:57:11 PowerChute successfully opened TCP port 3052.
09/08/2012 14:57:07 PowerChute Network Shutdown version 3.0.1 started
09/08/2012 14:57:06 PowerChute successfully opened UDP port 3052.
09/08/2012 14:57:02 Battery is discharged
09/08/2012 14:57:02 Communication has been established
09/08/2012 13:13:01 UPS has switched to battery power
09/08/2012 12:28:21 Input power has been restored: UPS has switched to On Line operation
09/08/2012 12:28:19 UPS has switched to battery power

Thanks in advance,
Chris

Message was edited by: HorizonsAdmin

[BillP]

hi Chris,

can you give me the data log from this time too from the network management card in the UPS?

have you done any specific configuration on the PCNS installed on the vMA? or did you just install it and thats it?

are these times lined up or are they really skewed and thats part of the problem?

[Anonymous user]

Here are the complete logs from the 750XL log:
09/08/2012 14:07:36 UPS: A discharged battery condition no longer exists.
09/08/2012 13:49:03 UPS: The battery power is too low to support the load; if power fails, the UPS will be shut down immediately.
09/08/2012 13:48:50 System: Network service started. System IP is 10.1.1.204 from manually configured settings.
09/08/2012 13:49:02 UPS: Restored the local network management interface-to-UPS communication.
09/08/2012 13:48:49 System: Coldstart.
09/08/2012 12:44:55 UPS: A low battery condition no longer exists.
09/08/2012 12:44:55 UPS: The output power is turned off due to a low battery.
09/08/2012 12:42:21 UPS: The battery power is too low to continue to support the load; the UPS will shut down if input power does not return to normal soon.
09/08/2012 12:12:55 UPS: On battery power in response to an input power problem.
09/08/2012 11:43:41 System: Web user 'apc' logged out from 192.168.10.1.
09/08/2012 11:40:40 System: Web user 'apc' logged in from 192.168.10.1.
09/08/2012 11:28:15 UPS: No longer on battery power.
09/08/2012 11:28:12 UPS: On battery power in response to an input power problem.

Yes, the difference in the times seems to be the problem. It looks to me like there was a half hour between the power down event and the response from the hosts to shut down. I followed the "How to install PowerChute Network Shutdown 3.0 on VMware ESXi – vMA 4.0, 4.1, 5.0". The only configuration that I did after installation was to add an additional server to the list via "sudo vifp addserver"

Thanks,
Chris

Message was edited by: HorizonsAdmin

[BillP · Accepted solution]

can you provide the data log too please? under logs->data->log?