configuration guide for ipm&vmware 0.6

www.eaton.com/virtualization

Management Integration – VMWare & IPM

Configuration Guide

for

Intelligent Power Plug-In vCenter

Revision History

Revision Description By

2nd

April 2010 Create the Document Bégou

19th April 2010 Updated Vageesh/Prashant

21 April 2010 Updated Bégou


Management Integration – VMWare & IPM /14

Contents

1 Configuration ...........................................................................................................................................3

1.1 Intelligent Power Plug-in vCenter Installation ...................................................................................3 1.1.1 Introduction.................................................................................................................................3 1.1.2 Prerequisite ................................................................................................................................3 1.1.3 Installation ..................................................................................................................................3 1.1.4 Using Intelligent Power Plug-in vCenter.....................................................................................3 1.1.5 Checking Registered Plug-in......................................................................................................4 1.1.6 Using IPM with vCenter..............................................................................................................5

1.2 How to Forward Power Event in vCenter..........................................................................................6 1.2.1 Introduction.................................................................................................................................6 1.2.2 Prerequisites...............................................................................................................................6 1.2.3 Download the Script ...................................................................................................................6 1.2.4 Configure the Web Interface ......................................................................................................6 1.2.5 Test the configuration.................................................................................................................8

1.3 Enter or Exit host from Maintenance Mode on Power Event (only work with ESX Server).............9 1.3.1 Introduction.................................................................................................................................9 1.3.2 Concept of Maintenance Mode ..................................................................................................9 1.3.3 Eaton Network management System only supports ESX and not ESXi..................................10

1.4 Configure Maintenance mode and vMotion ....................................................................................11 1.4.1 Prerequisites.............................................................................................................................11 1.4.2 Configuring vCenter and IPM...................................................................................................11 1.4.3 Configuration of the Scripts ......................................................................................................12 1.4.4 Test of the configuration...........................................................................................................13

2 Appendix ................................................................................................................................................14 2.1 References......................................................................................................................................14

2.1.1 Eaton and Virtualization ...........................................................................................................14 2.1.2 VMware ESX configuration ......................................................................................................14 2.1.3 vCenter Server (VMware Supervisor) ......................................................................................14 2.1.4 Intelligent Power Manager (Eaton Power Supervisor) .............................................................14 2.1.5 Eaton Software & Scripts Package ..........................................................................................14 2.1.6 Maintenance Mode...................................................................................................................14 2.1.7 vSphere SDK for Perl ...............................................................................................................14



1 Configuration

1.1 Intelligent Power Plug-in vCenter Installation

1.1.1 Introduction

VMware’s vCenter Server platform forms the foundation for virtualization management. It provides management of hosts and Virtual machines from a single console. To further unlock the power of VMware’s management system, VMware has provided a facility to extend the functionality of VMware vCenter. Various useful applications can be attached to vCenter to make it more useful. Eaton vCenter Plug-in called “Intelligent Power Plug-in vCenter” is a very easy to use and deploy Plug-in to manage IPM from vCenter. This plug-in provides the facility to integrate Intelligent Power Manager (IPM) with vCenter environment. Once the plug-in is deployed, a tab in vCenter will open IPM and allow users to configure and manage IPM from vCenter environment.

1.1.2 Prerequisite

Following are the prerequisites for Intelligent Power Plug-in vCenter: 1. VMware vCenter installed on physical Windows server 2. IPM installed on one of the machines in that Network subnet 3. Eaton Software & Scripts Package obtained

a. by downloading from the link “http://powerquality.eaton.com/Products-services/Power-Management/Software-Drivers/Intelligent-PM.asp ”

b. from IPP\Softwares directory in the CD shipped with UPS 4. VSphere Client installed on a managing server or PC

You must also have a knowledge / experience with IPM software and VMware Infrastructure

1.1.3 Installation

1. Double Click on Intelligent Power Plug-in vCenter setup,exe. 2. Follow the steps as mentioned in installer 3. Click on finish button to complete the installation. 4. vCenter Plugin Configurator is now installed on the machine.

1.1.4 Using Intelligent Power Plug-in vCenter

1. Click on Start -> Eaton -> Intelligent Power Plug-in vCenter -> Intelligent Power Plug-in vCenter 2. The following window will be displayed:



Field Information IPP/IPM Address – Host name or IP address of the machine where IPM is installed. vCenter Server Hostname/IP- Host name or IP address of vCenter Server. If you have configured vCenter server port number other than 443 provide that it next filed. vCenter Admin Username – Administator user name of the vCenter server. vCenter Admin Password – Administrator password of the vCenter server. Fill all the information above and click on one of the following button. 1. Register Plug-in - Registers Plug-in in vCenter server. IPM tab will be added when you next

connect to vCenter server with vShpere Client. 2. Un-Register Plug-in - Unregisters Plug-in in vCenter server. It will be visible until vCenter with

vShpere Client is active. Close and again connect to vCenter with vSphere Client. 3. Update Plug-in - Re-registers Plug-in in vCenter server. This feature can be used to change the

IPM address. Changes made will be visible when you next time connect to vCenter with vShpere Client.

1.1.5 Checking Registered Plug-in

In the vSphere Client, click on Plug-ins -> Manage Plug-in

Intelligent Power Plug-in vCenter can be seen in Plug-in Manager



1.1.6 Using IPM with vCenter

The “Eaton Power Manager” tab will now be visible in the vCenter Server Console (and in the root

folder ). IPM is now available and is fully functional with the vSphere Client. To learn more about the features and usage of IPM, please consult the IPM User Manual. The IPM screen is shown below, note the “Eaton Power Manager” tab on the top is selected.



1.2 How to Forward Power Event in vCenter

1.2.1 Introduction

The goal of this part is to integrate the generation of power event in vCenter Server.

1.2.2 Prerequisites

The following are prerequisites: 1. VMware vSphere vCenter, vSphere SDK for Perl and Intelligent Power Plug-in vCenter are

installed. 2. IPM is installed on one of the machines in the subnet 3. Eaton Software & Scripts Package 4. VSphere Client installed on a managing server or PC

It is better to have minimum of knowledge of VMware environment.

1.2.3 Download the Script

Extract the Eaton package (obtained in step 3 of section 1.1.2) on the IPM server and copy the file “CreateEvent.pl” in the root folder of IPM. Example: “C:\Program Files\EATON\IntelligentPowerManager”

1.2.4 Configure the Web Interface

Connect to the Web Interface of IPM https://127.0.0.1:4680/ (or through Eaton's Plug-in) and go to the view “Action” on your left

Click on “Create new action” on your right

Configure the new action with the good parameters



Event criticalities:

Event categories:

Action Type:

Configure the command line: perl CreateEvent.pl --server @IPorNAME --username $Username --password $Password --msg "{object} {nodeName} {message}"

Parameters: @IPorNAME: IP Address or Name of the vCenter Server (Its is not required to enter if IPM is installed on the same server as vCenter server) $Username: Username of an Administrator of vCenter server $Password : Password of an Administrator of vCenter server “Message”: Must be between double quotes; a few parameters like {object} {nodeName} can be used after msg. See screen shot below:



1.2.5 Test the configuration

Select the new action that you have created and click on “Test selected action”

Click on the Task & Events tab from the root folder as shown below. Data on alarms and alerts from Intelligent Power manager is added to other alarms and alerts for other vCenter components as shown in the screen shot below.

In real situation you should have a log like:



1.3 Enter or Exit host from Maintenance Mode on Power Event (only work with ESX Server)

1.3.1 Introduction

The Dynamic Resource Scheduler (DRS) application from VMware is used to provide load balancing within the IT network. In particular, DRS is used to ensure the right resource capacity is available for the data center load. A second application called vMotion in conjunction with DRS will enact movement of Virtual machines from physical server to physical server in order to provide the best load balance. The DPM application (Distributed Power Manager) will help maximize data center electrical power efficiency by checking DRS for physical server utilization then using vMotion, will move Virtual machines to servers in order to fully unload servers than idle them or power them down for maximum power savings. Eaton uses the same vMotion capability when a UPS is in a critical power situation to move virtual machines off of a server that has a critical power situation. Intelligent Power Manager will now write alarms/alerts into vCenter, which, in turn, will trigger vMotion. VMware uses the term ‘setting a server into Maintenance mode’ to trigger the vMotion. It is called this because before performing maintenance on server, the data center manager needs to clear the Virtual Machines from the server.

1.3.2 Concept of Maintenance Mode

Both standalone hosts, and hosts within a cluster, support the maintenance mode. Only ESX Server 3.0 and later supports maintenance mode for standalone hosts. A host enters or leaves maintenance mode only as the result of a user request. If the host is in a cluster when it enters maintenance mode, the user is given the option to evacuate powered-off virtual machines. If this option is selected, each powered-off virtual machine is migrated to another host, unless there is no compatible host available for the virtual machine in the cluster. While in maintenance mode, the host does not allow deployment or ‘power-on’ of a virtual machine. Virtual machines that are running on a host entering maintenance mode need to be either migrated to another host or shut down (either manually or automatically by DRS). When no more running virtual machines are on the host, the host’s icon changes to include ‘under maintenance’ designation and the host’s Summary panel indicates the new state. The default automation mode of a virtual machine determines its behavior when the host (in a DRS cluster) it is running on enters maintenance mode:

• Any fully automated virtual machine is migrated automatically.

• For a partially automated or manual virtual machine, a recommendation for further user action is generated and displayed.



1.3.3 Eaton Network management System only supports ESX and not ESXi

Eaton suggests users to install the Eaton Network Shutdown Module or Netwatch for protection of the ESXi server on a vMA installed on the ESXi local disc (should be as close to the server)

1. We can't finish the maintenance mode task because the vMA can't move.

2. We can't shutdown the vMA because we must keep the vMA working to shutdown the server if necessary



1.4 Configure Maintenance mode and vMotion

1.4.1 Prerequisites

All machines are configured to be on file server

1.4.2 Configuring vCenter and IPM

1. Enable the DRS in “Fully Automated” automation level with following steps:

1. Open the vCenter server in a vSphere client. 2. Right click on your Cluster > Edit Setting > Turn on VMWare DRS. Click on next with all

default values and finish. 2. Install the IPM on one of the machines in the subnet 3. Install vSphere SDK for Perl on the machine where IPM server is installed. 4. Extract the Eaton package on the machine where IPM is installed. 5. Copy the file “CreateEvent.pl” and “MaintenanceMode.pl” into the root folder of IPM. For example:

“C:\Program Files\EATON\IntelligentPowerManager” 6. Copy the java script file “MaintenanceMode.js” into the folder

IntelligentPowerManager\configs\scripts\ 7. Edit the javascript file, and change all the variables corresponding to the environment as

described in section 1.4.3 below. 8. Restart the IPM service



1.4.3 Configuration of the Scripts

//--------------------START SETUP 1 ------------------------------

//--------------------ESX 1/UPS 1 ------------------------------

//Information about ESX host and its corresponding UPS (ESX Host and Server 1)

var host1="IP or Hostname of ESX host";

// the name of the host in vCenter Server (IP or Name)

var statusUPS1 = UserFunctions.getNodeData("IP or hostname of UPS or Node Name in IPM");

//Name of the Node in IPM (IP,DNSName or other)

//The UPS1 link to the Host1

//if the status of the UPS1 is on Battery, the Host1 enters in maintenance mode

if(statusUPS1 && statusUPS1["UPS.PowerSummary.PresentStatus.ACPresent"] != 1 )

{

UserFunctions.exec("perl MaintenanceMode.pl --server "+vCenter+" --username "+username+" -

-password "+password+" --host "+host1+" --value 1");

}

//if the status of the UPS1 is on the sector, the Host1 exit the maintenance mode

else if(statusUPS1["UPS.PowerSummary.PresentStatus.ACPresent"] == 1)

{

UserFunctions.exec("perl MaintenanceMode.pl --server "+vCenter+" --username "+username+"

--password "+password+" --host "+host1+" --value 0");

}

//--------------------END SETUP1 ------------------------------

//--------------------START SETUP 2 ------------------------------

//--------------------ESX 2/UPS 2 ------------------------------

var host2="IP or Hostname of 2nd ESX host";

var statusUPS2 = UserFunctions.getNodeData("IP or hostname of UPS or Node Name in IPM that

is powering ESX 2");

//The UPS2 link to the Host2

if(statusUPS2 && statusUPS2["UPS.PowerSummary.PresentStatus.ACPresent"] != 1 )

{


-password "+password+" --host "+host2+" --value 1");

}

else if(statusUPS2["UPS.PowerSummary.PresentStatus.ACPresent"] == 1)

{


--password "+password+" --host "+host2+" --value 0");

}

//--------------------END SETUP2 ------------------------------

//--------------------START SETUP N ------------------------------

//--------------------ESX N/UPS N ------------------------------

var hostx="IP or Hostname of n-th ESX host";

var statusUPSx = UserFunctions.getNodeData("IP or hostname of UPS or Node Name in IPM that

is powering ESX n");

//The UPSx link to the Hostx

if(statusUPSx && statusUPSx["UPS.PowerSummary.PresentStatus.ACPresent"] != 1 )

{


-password "+password+" --host "+hostx+" --value 1");

}

else if(statusUPSx["UPS.PowerSummary.PresentStatus.ACPresent"] == 1)

{


--password "+password+" --host "+hostx+" --value 0");

}

//--------------------END SETUPN ------------------------------



1.4.4 Test of the configuration

To test the installation, perform a power failure on the UPS and see if the corresponding ESX host went in Maintenance mode. Besides, removing from the UPS, the user can initiate a utility failure test from the website of the network management card. To get to the Network management card website, type in the IP address of the network management card.



2 Appendix

2.1 References

2.1.1 Eaton and Virtualization

Please visit http://www.eaton.com/virtualization

2.1.2 VMware ESX configuration

Please visit http://www.vmware.com/support/

2.1.3 vCenter Server (VMware Supervisor)

Please visit http://www.vmware.com/products/vcenter/ for more information about download and installation of vCenter Server Please visit also http://www.vmware.com/products/drs/ for more information about Distributed Resource Scheduler

2.1.4 Intelligent Power Manager (Eaton Power Supervisor)

Please visit http://download.mgeops.com/ for more information about download and installation of IPM

2.1.5 Eaton Software & Scripts Package

Please visit http://download.mgeops.com/

2.1.6 Maintenance Mode

Please visit http://pubs.vmware.com/vi35/resmgmt/vc_cluster_concepts.6.11.html

2.1.7 vSphere SDK for Perl

Please visit http://www.vmware.com/support/developer/viperltoolkit/ for more information about download and installation of vSphere SDK for Perl.

configuration guide for ipm&vmware 0.6

Documents