6 Energy_management_support_for_blade

ligc edited this page 2015-07-30 04:22:49 -04:00

Table of Contents

• 1. Overview
• 2. The attributes that the renergy command will support
• 3. Implementation details

Table of Contents

• 1. Overview
• 2. The attributes that the renergy command will support
• 3. Implementation details

{{:Design Warning}}

1. Overview

Blade Center has the architecture that all the blade servers are put in one chassis, and all the power of blade servers is supplied by the power modules which installed in the chassis. In the blade center architecture, the blade servers are managed by the Management Module which also is a module installed in the chassis. The Management Module supplies the SNMP interface to manage other modules that installed in the chassis. (includes the blade server modules)

The Management Module supplies the energy management information of all the modules which installed in the chassis, and supplies the information for each blade server. The renergy command can use the Management module as the target node to get the power information for the whole chassis and use the blade as the node to get the information for the specific blade server.

2. The attributes that the renergy command will support

2.1 The power attributes supported by chassis

In the blade center, the power management is divided into two domains. Each domain has two power modules and several blade slots. The power domain information is useful for user to know the power domain status.

2.1.1 Get the energy information for power domain 1:

For this domain, the following information will be displayed:

1. Status of power domain
SNMP node: fuelGaugeStatus - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.3.x] (x is the domain number)


2. Power Management Policy
Description: It has several values:                    
  redundantWithoutPerformanceImpact(0),
  redundantWithPerformanceImpact(1),
  nonRedundant(2),
  redundantACPowerSource(3),
  acPowerSourceWithBladeThrottlingAllowed(4),
  notApplicable(255)
SNMP node: fuelGaugePowerManagementPolicySetting - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.6.x]


3. The first power module capability in this domain
Description: Unit is Watt.
SNMP node: fuelGaugeFirstPowerModule - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.4.x]


4. The second power module capability in this domain
Description: Unit is Watt.
SNMP node: fuelGaugeSecondPowerModule - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.5.x]


5. Total available power in this domain
Description: This value comes from the installed power modules and the current Power Management Policy Setting
SNMP node: fuelGaugeTotalPower - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.7.x]


6. Power that has been reserved in this domain
Description: It includes the power reservation for management modules, IO modules and blade servers.
SNMP node: fuelGaugeAllocatedPower - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.8.x]


7. Remaining power available in this domain
Description: Remaining Power = Total Power - Power In Use
SNMP node: fuelGaugeRemainingPower - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.9.x]


8. Total power being used in this domain 
SNMP node: fuelGaugePowerInUsed - [.1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.10.x]

2.1.2 Get the energy information for power domain 2:

The attributes are same with ones in the domain 1.

2.1.3 Get the total available DC

chassisTotalDCPowerAvailable - [.1.3.6.1.4.1.2.3.51.2.2.10.5.1.1.0]

2.1.4 Get the total AC in use

Description: All the power in use + power consumed by the cooling device

chassisTotalACPowerInUsed - [.1.3.6.1.4.1.2.3.51.2.2.10.5.1.2.0]

2.1.5 Output Thermal of the chassis

chassisTotalThermalOutput - [.1.3.6.1.4.1.2.3.51.2.2.10.5.1.3.0]

2.1.6 The temperature of environment

frontPanelTemp - [.1.3.6.1.4.1.2.3.51.2.2.1.5.1.0]

2.1.7 The temperature of management module

mmTemp - [.1.3.6.1.4.1.2.3.51.2.2.1.1.2.0]

2.2 The power attributes supported by blade server

2.2.1 Get the current power allocation for the blade (current power in used)

SNMP node: pd2ModuleAllocatedPowerCurrent - [.1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.7]

2.2.2 Get the the maximum power allocation for the blade

SNMP node: pd2ModuleAllocatedPowerMax - [.1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.8]

2.2.3 Get the minimum power allocation for the blade

SNMP node: pd2ModuleAllocatedPowerMin - [.1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.9]

2.2.4 Get the power capability of the blade

SNMP node: pd1ModulePowerCapabilities - [.1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.12]

Values:
noAbility(0),
staticPowerManagement(1),
fixedPowerManagement(2),
dynamicPowerManagement(3),
dynamicPowerMeasurement1(4),
dynamicPowerMeasurement2(5),
dynamicPowerMeasurementWithPowerCapping(6),
notApplicable(255)

2.2.5 Get/Set the maximum power that can be used by the blade (power capping)

SNMP node: bladeDetailsMaxPowerConfig - [.1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.3]

2.2.6 Get the Effective CPU Clock Rate

SNMP node: bladeDetailsEffectiveClockRate - [.1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.4]

2.2.7 Get the Maximum CPU Clock Rate

SNMP node: bladeDetailsMaximumClockRate - [.1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.5]

2.2.8 Get/Set the static/dynamic power save (looks like the snmp does not support it now)

SNMP node: bladeDetailsPowerSaverMode - [.1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.6]

3. Implementation details

Blade center has two power domains, part of the blade modules accommodated by power domain 1 and others accommodated by power domain 2. Following is the bay map between the server blade bay and domain bay.

powerDomain1 - contains the serverBladeBay 1-7

BladeCenter: (serverBladeBay 1-6) (BayNumber 11-16)
BladeCenter H: (serverBladeBay 1-7) (BayNumber 17-23)
BladeCenter T: (serverBladeBay 1-4) (BayNumber 13-16)
BladeCenter HT:(serverBladeBay 1-6) (BayNumber 23-28)
BladeCenter S:(serverBladeBay 1-6) (BayNumber 18-23)

powerDomain2 - contains the serverBladeBay 8-14 (BayNumber 17-23)

BladeCenter: (serverBladeBay 7-14) (BayNumber 1-8)
BladeCenter H: (serverBladeBay 1-7) (BayNumber 17-23)   "It should be the serverBladeBay 8-14. It's a bug and has been fixed."
BladeCenter T: (serverBladeBay 5-8) (BayNumber 3-6)
BladeCenter HT:(serverBladeBay 7-12) (BayNumber 3-8)

News

• Apr 22, 2016: xCAT 2.11.1 released.
• Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
• Dec 11, 2015: xCAT 2.11 released.
• Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
• Jul 30, 2015: xCAT 2.10 released.
• Jul 30, 2015: xCAT migrates from sourceforge to github
• Jun 26, 2015: xCAT 2.7.9 released.
• Mar 20, 2015: xCAT 2.9.1 released.
• Dec 12, 2014: xCAT 2.9 released.
• Sep 5, 2014: xCAT 2.8.5 released.
• May 23, 2014: xCAT 2.8.4 released.
• Jan 24, 2014: xCAT 2.7.8 released.
• Nov 15, 2013: xCAT 2.8.3 released.
• Jun 26, 2013: xCAT 2.8.2 released.
• May 17, 2013: xCAT 2.7.7 released.
• May 10, 2013: xCAT 2.8.1 released.
• Feb 28, 2013: xCAT 2.8 released.
• Nov 30, 2012: xCAT 2.7.6 released.
• Oct 29, 2012: xCAT 2.7.5 released.
• Aug 27, 2012: xCAT 2.7.4 released.
• Jun 22, 2012: xCAT 2.7.3 released.
• May 25, 2012: xCAT 2.7.2 released.
• Apr 20, 2012: xCAT 2.7.1 released.
• Mar 19, 2012: xCAT 2.7 released.
• Mar 15, 2012: xCAT 2.6.11 released.
• Jan 23, 2012: xCAT 2.6.10 released.
• Nov 15, 2011: xCAT 2.6.9 released.
• Sep 30, 2011: xCAT 2.6.8 released.
• Aug 26, 2011: xCAT 2.6.6 released.
• May 20, 2011: xCAT 2.6 released.
• Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
• xCAT Release Notes Summary
• xCAT OS And Hw Support Matrix
• xCAT Test Environment Summary

History

• Oct 22, 2010: xCAT 2.5 released.
• Apr 30, 2010: xCAT 2.4 is released.
• Oct 31, 2009: xCAT 2.3 released.
  xCAT's 10 year anniversary!
• Apr 16, 2009: xCAT 2.2 released.
• Oct 31, 2008: xCAT 2.1 released.
• Sep 12, 2008: Support for xCAT 2
  can now be purchased!
• June 9, 2008: xCAT breaths life into
  (at the time) the fastest
  supercomputer on the planet
• May 30, 2008: xCAT 2.0 for Linux
  officially released!
• Oct 31, 2007: IBM open sources
  xCAT 2.0 to allow collaboration
  among all of the xCAT users.
• Oct 31, 1999: xCAT 1.0 is born!
  xCAT started out as a project in
  IBM developed by Egan Ford. It
  was quickly adopted by customers
  and IBM manufacturing sites to
  rapidly deploy clusters.