| You need to purchase a license of the PCNS Agent for each Host, it is provided from APC |
| If you use ESXi then you will also need VIMA installed and the process is more complex |
| You MUST have the VMware Tools running in each Guest, as you risk data loss otherwise! |
- Upload the file to your ESX Server via SCP or place it on an accesible VMFS/NFS share
- Unpack the file at a location (i.e. home/temp folder), it contains the installer:
gunzip pcns224_esx.tar.gz tar -xf pcns224_esx.tar
- Run the installer as root:
[root@vmware3 tempapc]# ./install.sh ------------------------------------------------------------------ PowerChute Network Shutdown v.2.2.4 for VMware Copyright (c) 2009 Schneider Electric, All Rights Reserved. ------------------------------------------------------------------ OS=Linux Initializing ... Press any key to display End User License Agreement- confirm the License Agreement with "yes"
- The default PCNS instance Number is 1 and should be taken as long as you do not really have multiple UPSs attached to your host
- The default install directory /opt/APC/PowerChute should be fine and you will need to confirm it
- The default java directory is also fine and can be confirmed
- Now the system is installing and also configuring the VMware Firewall
Copying jre to /opt/APC/PowerChute/jre ... Extracting jre to /opt/APC/PowerChute/jre ... java version "1.5.0_18" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_18-b02) Java HotSpot(TM) Client VM (build 1.5.0_18-b02, mixed mode, sharing) JAVA_DIR=/opt/APC/PowerChute/jre/jre1.5.0_18 Configuring startup files ... Startup script=/etc/rc.d/init.d/PowerChute Updating Linux symbolic link ... 2010-05-25 11:22:35 (21437) WARN : OpenPort: Opening a previously opened port: 3052. 2010-05-25 11:22:37 (21868) WARN : OpenPort: Opening a previously opened port: 3052. 2010-05-25 11:22:39 (22300) WARN : OpenPort: Opening a previously opened port: 3052. Configuring uninstall script ... Completed. Please run the PCNSConfig.sh script located within the PCNS installation directory to complete the installation.
- Now cd into the install dir:
cd /opt/APC/PowerChute/group1
- And run the Config Tool:
./PCNSConfig.sh -------------------------------------------------- PowerChute Network Shutdown Configuration Utility -------------------------------------------------- Press Ctrl + C at anytime to abort. Configuring PowerChute Network Shutdown ... [1]: Configure for a single UPS device [2]: Configure for a parallel Silcon UPS / Smart-UPS VT / Galaxy system [3]: Configure for multiple Smart-UPS or Galaxy devices [4]: Configure for multiple Symmetra devices Please select the appropriate configuration type (1) [ 1 - 4 ]:
As you normally have only one single UPS you choose option 1
- Next you need to enter the Management Card IP (i.e. 10.123.45.67), the Port (80 is default), an administrator user (we default to apc) and a password for the admin.
- Now it comes to the authentication phrase which is global for all devices attached to your APC UPS, it needs to be between 15 and 32 characters
- You should now see a confirmation of your settings:
Setting Summary: Management Card IP: 10.123.45.67 Management Card Port #: 80 Administrator User Name: apc Administrator Password: [ MASKED ] Authentication Phrase (default): [ MASKED ] - AFter it successfully sets up the conmmunication you need to confirm that the service should be started.
- You are done with the VMware console/ssh part
- Open your favorite web browser and connect to https://servername:6547

You might see the usual error of an untrusted certificate which you should confirm - Once logged in you can configure the settings, one is very important if you have multiple servers connected: Disable the "Turn off the UPS after the shutdown finishes" as it might turn off power even before all hosts are shutdown.
- Next you need to get back to your VMware VCP Client, as the above only configures the shutdown of the host itself.
- Under each host you have configured look at the configuration screen for "Virtual Machine Startup/Shutdown"
- Check that the "Allow virtual machines to start and stop automatically with the system" is enabled

if necessary change the order of the systems and decide which ones should be started manual
- Check that the "Allow virtual machines to start and stop automatically with the system" is enabled
- Under each host you have configured look at the configuration screen for "Virtual Machine Startup/Shutdown"
Add Comment