How to install PowerChute Network Shutdown on VMware ESXi 3.5, 4.0 and 4.1

Transcription

1 How to install PowerChute Network Shutdown on VMware ESXi 3.5, 4.0 and 4.1

2 Basic knowledge of Linux commands and Linux administration is needed before user should attempt the installation of the software. PowerChute network Shutdown (PCNS) or is required. PowerChute Network Shutdown requires VMware Infrastructure Management Assistant (VIMA) 1.0 or vsphere Management Assistant (vma) install on the VMware ESXi host. If you need help installing VIMA or vma please contact VMware support or go to this site When installing on VMware ESXi with vma 4.1 please see KBase # for installation patch. The VIMA or vma client requires AMD Opteron, Rev E or later CPU or Intel processors with EM64T and VT support You will need VMware Infrastructure Client installed on your desktop / laptop to log into the ESXi host system. You can load the client by logging into the ESXi host via a web browser. Communications ports 3052, 80 need to be open and 6547, 6548, 6549 depending on the number of instances being installed.

3 To load VMware desktop Infrastructure client log into the ESXi host using a web browser and the systems IPaddress and download the client. Enter IPaddress Download the desktop client

4 Once the client has been instlled a short cut to the client will be placed on the desktop

5 Double click on the client and the login screen will launch. Log into the host server

6 View of Infrastructure Client

7 If the VIMA or vma has not been loaded go to File Virtual Appliances - Import.

8 Import from the VMware Market place: download from and navigate / browse to where you downloaded the file to and import from there. Import from URL To download any files from VMware you are required to create a user account.

9 Once the VIMA or vma client has been added select it from the list of available virtual systems to load PCNS on.

10 If loading from CD verify that the CD drive is connected on the client and the CD is loaded into the host system CD drive.

11

12 From the console tab log into the client.

13 If one has not been created, create a mount point for the CD. sudo mkdir /mnt/cdrom

14 Change the permissions on the new mount point sudo chmod 666 /mnt/cdrom

15 Mount the APC CD and change directory to view the files in the ESXi directory. sudo mount t iso9660 /dev/cdrom /mnt/cdrom cd /mnt/cdrom/esxi Line Commands Line 1 sudo mount t iso9660 /dev/cdrom /mnt/cdrom Line 2 cd /mnt/cdrom/esxi

16 From within the ESXi directory on the APC CD run the installation script. sudo./install.sh NOTE: If the install files were downloaded from APC web site you will need to copy the files to a temporary directory to be uncompressed before the program can be installed. Assuming you are copying to /tmp the commands are sudo cp pcns224esxi.tar.gz /tmp cd /tmp sudo gunzip pcns224esxi.tar.gz sudo tar xvf pcns224esxi.tar

17 When running the install file answer the installation questions as they appear on the console.

18 When installing PCNS be sure when asked to enter the host server ipaddress, user name, and password. This enables communication between the vma / VIMA client and the host server. When installing PCNS or if you choose not to enter the host info during the installation you will need to establish communications between the vma / VIMA client and the host server manually. Please see pages 29 and 30 for instructions.

19 Once the installation is complete verify that the needed communications ports are open and then run the configuration script found in /opt/apc/powerchute/group1

20 To verify the needed communications ports are open run this sudo /sbin/iptables L To open all ports stop the firewall temporally run the command sudo service iptables stop To restart the firewall run the command sudo service iptables start NOTE: When Installing PCNS the iptable is edited automatically by the installer. For PCNS the iptable has to be edited by the user. PCNS users can skip to page 27. If the iptable has been edited have the administrator add ports TCP 80, TCP & UDP 3052 and TCP 6547, 6548, 6549 as needed for the instances installed. In this example port 80, 3052 are open along with 6547 since this is a single instance installation. Also open is port 22 to allow for SSH connections (port 22 is optional). All of these ports have a restrictions that only allows for connections from IPaddress range X.X with a subnet mask of

21 In the example above we edited the iptables. Since this is a new install we first opening all of the ports, flushing any default setting, and deleting any default chains. Flushing the filters and deleting the chains is important since rules are checked in sequential order and we don t want any old filter to deny packets to the ports we are about to open.

22 Above we have created 2 new chains. 1 named apc and 1 named system. The system chain was created to allow the system to communicate with itself, and the apc chain was created to allow communications the PCNS.

23 Above we have opened ports 3052, 80, 22 and 6547, assigned them to the apc chain, and restricted communications for ipaddresses X.X

24 Above we have opened the iptables to allow icmp echo request and replies (Pings) for troubleshooting

25 Above we have allowed output from all and blocked input and forwarding from all except from the ports specified in the apc and system chains created earlier.

26 The final step in editing the iptables is to save the file. If this step is skipped the next time the VIMA / vma client is rebooted the changes will be lost.

27 Once the ports have been opened run the configuration script in /opt/apc/powerchute/group1 Answer the configuration questions as they appear in the console and the installation is complete.

28 Be sure to select yes to start the PCNS services.

29 To manually add the host server to the server list first check to be sure the server is not already in the list by running the command vifp listservers If the server is not in the list add the server to the list by running the command sudo vifp addserver Verify the server has been added vifp listservers

30 Next you need to add the server to the fasspass list the command is vifpinit <server name or ipaddress> NOTE: for vma 4.1 the vifpinit command has been replace with vifptarget the command for 4.1 is vifptarget s <server name or ipaddress> To verify there is communications between the cleint and the host run the command Vicfg-nics l (lower case letter l) should display a lst of the host NICs.

31 Once PCNS has been started you can now log into the PCNS client via your web browser. Using the ipaddress of the VIMA / vma for a typical / single instance installation.