module 2 5 dmp ipmi

7/28/2019 Module 2 5 Dmp Ipmi

1/20

DPM - IPMI

Product Support Engineering

VM ware Co n f i d en t i a l


2/20

VI4 - Mod 2-5 - Slide 2

Module 2 LessonsLesson 1 vCenter Server High Availability

Lesson 2 vCenter Server Distributed Resource Scheduler Lesson 3 Fault Tolerance Virtual Machines

Lesson 4 Enhanced vMotion Compatibility

Lesson 5 DPM - IPMI

Lesson 6 vAppsLesson 7 Host Profiles

Lesson 8 Reliability, Availability, Serviceability ( RAS )

Lesson 9 Web Access

Lesson 10 vCenter Server Update Manager Lesson 11 Guided Consolidation

Lesson 12 Health Status


3/20


Module 2-5 Lessons

Lesson 1 Overview of DPM and IPMILesson 2 Configuring IPMI settings

Lesson 3 Testing IPMI

Lesson 4 Enabling Power Management

Lesson 5 Troubleshooting IPMI


4/20


Managing Power ResourcesThe VMware Distributed Power Management (DPM) feature allows a

DRS cluster to reduce its power consumption by comparing per-hostcapacity versus demand and then taking (or recommending) theappropriate actions.

If sufficient excess capacity is found, DRS places one or more hosts instandby mode, migrating any virtual machines running on them to other

hosts and then powering them off.When capacity is deemed to be inadequate, DRS brings hosts out of standby mode (powers them on) and migrates virtual machines, usingVMotion, to them.


5/20


Managing Power Resources

ESX/ESXi hosts cannot automatically be brought out of standbymode unless there is a running vCenter Server in the cluster.

VMware DPM can use Intelligent Platform Management Interface(IPMI) , Integrated Lights-out (iLO) and Wake-On-LAN (WOL) asthe wake protocols that bring hosts out of standby mode.

Any host that supports both IPMI and WOL, defaults to using IPMI.


6/20


Configure IPMI Settings for VMware DPMIntelligent Platform Management Interface (IPMI) is a

hardware level specification that describes an interface for monitoring and controlling computers.

A Baseboard Management Controller (BMC) implements theinterface, providing a gateway for accessing hardware controlfunctions, and allowing the interface to be accessed from a remote

system using serial or LAN connections.This remote management can occur when there is no operatingsystem running on the host and when the system is powered off.

You must configure the BMC and IPMI settings of each host.Ensure that the BMC LAN channel is configured to be alwaysavailable and to allow operator privileged commands.

BMC configuration steps vary according to manufacturer and model.


7/20


Configure IPMI Settings for VMware DPM

To configure IPMI settings1 Select the host in the VI Client inventory.

2 Click the Configuration tab to display it.

3 Click IPMI Settings.


8/20


Configure IPMI Settings for VMware DPM

4 Click Properties.

5 Provide the following information:User name and password for a BMC account. (This user name must have theability to remotely power the host on.)

IP address of the NIC associated with the BMC. (This IP address should bestatic or a DHCP address with infinite lease.)

MAC address of the NIC associated with the BMC.6 Click OK.


9/20


Test Wake-on-LAN for VMware DPMThe use of Wake-on-LAN (WOL) for the VMware DPM feature is fullysupported

Before testing WOL, ensure that your cluster meets the following prerequisites:Your cluster must contain at least two ESX 3.5 (or ESXi 3.5) or later hosts.Each hosts VMotion networking link must be working correctly. The VMotionnetwork should also be a single IP subnet, not multiple subnets separated byrouters.The VMotion NIC on each host must support WOL. To display the

WOLcompatibility status for each NIC on a host, select the host in the inventorypanel of the VI Client, choose the Configuration tab, and click Network Adapters.

The NIC must have Yes displayed in the Wake On LAN Supported column. The switch port that each WOL supporting VMotion NIC is plugged into should beset to auto negotiate the link speed, and not set to a fixed speed (for example,1000 Mb/s). Many NICs support WOL only if they can switch to 100 Mb/s or lesswhen the host is powered off.

After you verify these prerequisites, test each ESX/ESXi host that is going to useWOL to support VMware DPM. When you test these hosts, ensure that theVMware DPM feature is disabled for the cluster.


10/20


ESX/ESXi host for Wake-on-LAN operability

To test an ESX/ESXi host for Wake-on-LAN operability1 Place the host in standby mode by clicking the Enter Standby Modecommand on the hosts Summary tab in the VI Client. This completely powersdown the host.

2 Attempt to bring the host out of standby mode by clicking the Power Oncommand on the hosts Summary tab.

3 Observe whether or not the host successfully powers back on.For any host that fails to exit standby mode successfully, select the host inthe cluster Settings dialog boxs Host Options page and change its Power Management setting to Disabled. After you do this, VMware DPM does notconsider that host a candidate for being powered off.

CAUTION Ensure that any host being added to a VMware DPM cluster that uses WOL as a wake protocol is tested and disabled from usingpower management if it fails the testing. If this is not done, VMware DPMmight power down hosts that it subsequently can not power back up.


11/20


Enabling VMware DPM for a DRS Cluster

Configure the power management automation level, threshold, andhost level overrides.

These settings are configured under Power Management in the clustersSettings dialog box.


12/20


Enabling VMware DPM for a DRS Cluster

Automation Level

Whether the host power state andmigration recommendationsgenerated by VMware DPM areexecuted automatically or notdepends upon the power

management automation levelselected for the feature.

The options available are:Off

Manual

Automatic


13/20


Enabling VMware DPM for a DRS Cluster DPM Threshold

The power state (host power on or off)recommendations generated by theVMware DPM feature are assignedpriorities

ranging from priority-one to priority-fiverecommendations.

These priority ratings are based on theamount of over or under utilizationfound in the DRS cluster and theimprovement that is expected from theintended host power state change

A priority one recommendation ismandatory, while a priority fiverecommendation brings only slightimprovement

NOTE The DRS threshold and the VMwareDPM threshold are essentially independent.You can differentiate the aggressiveness of themigration and host power staterecommendations they respectively provide.


14/20


Enabling VMware DPM for a DRS Cluster Host Options -Host-Level Overrides

When you enable a host in the DRScluster to use VMware DPM, it inheritsthe clusters power managementautomation level.

Create an override by selecting thehost in the cluster Settings dialogboxs Host Options page and clickingits Power Management setting.

You can change this setting to thefollowing options:

Disabled

Always Manual

Always Automatic

NOTE Times for the Last Time Exited Standbyfield are derived from the vCenter Server eventlog. If this log is cleared, the times are reset toNever.


15/20


Troubleshooting IPMI

Check the VC logs for [updateIpmi] or IPMIlib: or IPMI lib:

[2008-11-12 16:27:41.232 01444 verbose 'App'] [VpxVmomi] Invoking [updateIpmi] on[vim.HostSystem:host-10] session [D004135C-7928-4A51-BA2F-D26B3ED59C1B]

[2008-11-12 16:27:41.232 01444 verbose 'App'] Arg ipmiInfo:

(vim.host.IpmiInfo) {

dynamicType = ,

bmcIpAddress = "10.21.73.113",

bmcMacAddress = "00:19:99:17:11:D6",

login = "admin",

password = (not shown),

}


16/20



Invalid MAC Address[2008-11-12 16:27:27.701 00592 verbose 'App'] [VpxVmomi] Invoking [updateIpmi] on[vim.HostSystem:host-10] session [D004135C-7928-4A51-BA2F-D26B3ED59C1B]



dynamicType = ,


bmcMacAddress = "00:19:99:17:11:D",

login = "admin",


}

***

***

[2008-11-12 16:27:27.779 00796 warning 'App'] [VpxdMoHost] IPMIlib: reference MACaddress did not match one read from BMC of target host cs-tse-f113


17/20



Invalid Username[2008-11-12 17:06:45.154 03204 verbose 'App'] [VpxVmomi] Invoking [updateIpmi] on[vim.HostSystem:host-37] session [D004135C-7928-4A51-BA2F-D26B3ED59C1B]



dynamicType = ,


bmcMacAddress = "00:19:99:17:11:D6",

login = " administrator ",


}

***

***

[2008-11-12 17:06:46.217 03260 error 'App'] [VpxdMoHost] IPMI lib: GetMacAddr callfailed. API error 13 (hex).


18/20



Invalid IP Address[2008-11-12 17:29:29.967 02228 verbose 'App'] [VpxVmomi] Invoking [updateIpmi] on[vim.HostSystem:host-37] session [D004135C-7928-4A51-BA2F-D26B3ED59C1B]



dynamicType = ,

bmcIpAddress = " 10.21.35.113 ",

bmcMacAddress = "00:19:99:17:11:D6",

login = "admin",


}

***[2008-11-12 17:29:50.982 00796 error 'App'] [VpxdMoHost] IPMI lib: GetMacAddr callfailed. API error 13 (hex).


19/20


Lesson 2-5 Summary

Learn how to enable IPMI on a Cluster Learn how to test IPMI settings

Learn how to troubleshoot IPMI


20/20


Lesson 2-5 - Lab 5

Module 2-5 Lab 5 VMware vCenter DPM/IPMI

Enable IPMI on a Cluster

Test IPMI settings


module 2 5 dmp ipmi

Documents