I use PCNS 3.0.1 on Vsphere ESXi 5.0.1 and VMA to shutdown the VM's and the host in case of a power outage. Last week I upgraded VMA 5.0.0 to the latest version 184.108.40.206 (not really an upgrade, but a fresh install). Unfortunately the automatic shutdown doesn't work anymore.
When I run the shutdown script, it seems the relevant ESXi host can't be find or it isn't being managed by the VMA. Then I tried a complete fresh install of all components, but the problem stays.
Anybody who recognizes this problem? Solution for now is to stick with VMA 5.0.0
For PCNS the target ESXi hosts should be added to VIFP(VI Fast Pass)
I have also just verified that the issue is with the vMA 220.127.116.11 installing vMA 5.0 and pcns 3.0.1 has fixed my problem. Thanks for this information and hopefully someone else will find it helpful.
I'm experiencing the same issue.
Here's the error I receive:
[11.05.2012, 17:45:12]debug: Login by vi-fastpass to: <ESXi Host>
[11.05.2012, 17:45:12]debug: Error: Unable to login to host: "<ESXi Host>"! Host may not be accessible over the network or is not managed by VMA
Some additional useful information that I had to track down was that, for FastPass, you can simply add your vCenter Server (: sudo vifp addserver <vCenter Server IP>) as the only server used to control your ESXi hosts; or better yet: Add its IP during the PCNS installation. Also, when configuring events in the PCNS web interface, use "Run Command File" and enter the full path of the shutdown script (/opt/APC/PowerChute/group1/bin/shutdown) in the "Full path of the command file:" text box.
These steps are for the paid version of ESXi 5.
Same problem here. PCNS 3.0.1 and vMA 18.104.22.168 (5.0 patch 2) . The UPS switch off, but ESX host doesn t shutdown
vi-admin@localhost:/[192.168.76.22]> sudo /opt/APC/PowerChute/group1/bin/shutdown
Use of uninitialized value $loglevel in string eq at /opt/APC/PowerChute/group1/bin/shutdownhost.pl line 59.
Connecting to server localhost ...
[11.06.2011, 20:46:54]debug: Connecting to server localhost
Version on 192.168.76.22:
[11.06.2011, 20:46:54]debug: Login by vi-fastpass to: 192.168.76.22
[11.06.2011, 20:46:54]debug: Error: Unable to login to host: "192.168.76.22"! Host may not be accessible over the network or is not managed by VMA
So the patch 2 does not solve this bug.
I'll try to go back to 5.0,0.0
> vMA 22.214.171.124 same issue
Thanks for this advice. I'm new to VMware and setting up an ESXi 5.0 Update 1 Server with APC SmartUPS with NMC.
So I don't have to try vMA 126.96.36.199 first and continue my setup with vMA 5.0
Are there any restrictions I have to consider using a free licence key?
IIRC I've read in some HowTos that the vMA works in paid licences environment only?
With 188.8.131.52 it works. The host shutodown while with 184.108.40.206 don't . Now i try to upgrade vma to 220.127.116.11 via web interface and i'll tell you if it works with 18.104.22.168
The PCNS is always 3.0.1.