I know how to use it.
IÂ´ve tested that in a few test environment.
My question was, if this it supported by vmware in any support case!
APC have now released a version of PowerChute specifically designed to be installed on ESX.
So there is no need to go through the process of that document any longer.
Can you send me a link to that software?
How is it called?
Seeing as the documentation on this isn't all that extensive (especially for a non-linux user) I'm providing the steps to make it all work ... well it does for me and that's all that matters ;o)
All these commands are performed at the command line on the console or by using a SSH client (using SSH client allows some nice copy and paste action).
Firstly open the firewall ports
esxcfg-firewall -o 3052,tcp,out,"APC PowerChute Port 3052"
esxcfg-firewall -o 3052,tcp,in,"APC PowerChute Port 3052"
esxcfg-firewall -o 3052,udp,out,"APC PowerChute Port 3052"
esxcfg-firewall -o 3052,udp,in,"APC PowerChute Port 3052"[/b]
Then install the APC Network Shutdown Software
Then configure the software
Type 3 and press enter
Type in the IP address of the Management Card and press enter
Enter the Username, Password and Authentication Phrase
Repeat for the second management card
Answer No to registering another management card
Answer Yes to starting the service[/b]
Now you can configure the event actions etc by pointing your web browser to http://[i]servername[/i]:3052/[/b]
To uninstall, type rpm -e pcns[/b]
Once logged on to the web interface
Specify the Configure Shutdown settings
Anways let me know if I've missed something or if I've opened too many ports etc. Always willing to help out.
Very good summary of the steps needed. Did this recently for 2 customers and yes indeed non of the available documentation is complete.
I do have one remark. The line esxcfg-firewall -o 3052,tcp,out,"APC PowerChute Port 3052" is not necessary.
Port 3052 tcp in is necessary for configuration of PCNS through a web browser.
Port 3052 udp in is necessary for communication from the Network Management Card to PCNS, e.g. in the case of a power failure.
Port 3052 udp out is necessary for communication from PCNS to the Network Management Card and for broadcasting a shutdown to other PCNS clients on the same subnet. Remember that you can have only 50 PCNS clients registered on one Network Management Card. To address more clients the broadcast feature is used.
Port 80 is where the Network Management Card listens for communication.
Thanks for the feedback, I'll make sure I update our documentation and change it on the servers.
attempting to install the vmware version of PCNS software on an ESX3.01 host (connected to a single APC UPS) , everything goes fine until it attempts to register the agent with the management card, at which point it times out, and im back to square one
port 3052 is opened, in and out, port 80 is open outbound....
got the same problem .
tried to open all the ports but the agent couldn't register
Here's some general tips for troubleshooting, it's always good to go back to basics.
Can you ping the UPS management cards from the ESX hosts?
If not are they in the same subnet?
If different subnet do they have a default gateway defined?
Have you installed the windows version on a windows machine to ensure that the same settings you are using actually work?
Perhaps a reboot of the ESX host may be required after you make the firewall changes.
Is there a firewall between the UPS management cards and the ESX servers?
Hopefully one of these points you in the right direction.
Did you use the right passphrase ?
I think the default Authentication Phrase is: "admin user phrase"
what error message do you get when it fails?
The Network Management Card has room for only 50 clients. Look in the configuration of the NMC to see if your client table is full.