Collect, visualize, report on energy and thermal metrics for IT, facilities, property, enterprise assets
This chapter describes a scenario where various Tivoli products are used to collect and report on energy and thermal metrics for IT, facilities/property and enterprise assets.
This chapter contains the following topics:
3.1 Terminology
Before introducing the first Green IT scenario we first introduce important terminology that will be frequently used throughout the Green IT scenarios. Table 3-1 introduces the most important power, thermic and industry terms.
Table 3-1 Green IT terminology
Term
Description
PDU
Power distribution unit: A device that distributes power to a data center.
IPDU
Intelligent PDU: PDU that is capable of energy metering at the outlet ports
UPS
Uninterruptible power supply: A device that provides immediate emergency power, usually by means of batteries, if power fails.
CRAC
Computer room air conditioner: Monitors and controls a computer room’s temperature, humidity, and air flow.
Chiller
Provides chilled water used to cool and dehumidify air.
Power saver mode
Provides a way to save power by dropping the voltage and frequency a fixed percentage. This percentage is predetermined to be within a safe operating limit and is not user configurable. Under current implementation this percentage is a 14% frequency drop. Power saver mode is available on POWER6® Blades and 9406/9117-MMA rack systems.
Power capping
Enforces a user-specified limit on power usage. Setting a power capping value ensures that system power consumption stays at or below the value that is defined by the setting. Power capping is available only on supported IBM Servers and IBM Blade Servers.
Carbon footprint
The footprint is the total set of greenhouse gases (GHG) emissions caused by an organization, event or product. For simplicity of reporting, it is often expressed in terms of the amount of carbon dioxide (CO2). For our scenarios, carbon footprint is used in the context of the data center: the total emission of CO2 of the data center is expressed in kg CO2.
DCiE
Data Center infrastructure Efficiency: is a performance metric for calculating the energy efficiency of a data center. DCIE is the percentage value derived, by dividing information technology equipment power by total facility power. For example, if a data center has a total power consumption of 8000kW, and 6000kW is being used for all IT equipment, the DCIE equals 75%.
PUE
Power Usage Effectiveness: Inverse of DCIE. PUE is the percentage value derived by dividing total facility power by IT facility power.
kWh
kilo watt hour: The amount of energy delivered in one hour at a power level of 1000W (measurement unit for selling electricity).
3.2 Scenario overview
This first Green IT scenario focusses on collecting data that is relevant for optimizing the energy usage of a data center. To take appropriate actions for optimizing the energy consumption of a data center, we must first accurately collect thermal and energy metrics. The scenario also focusses on the ways to look at both the real-time and historical data.
The power and thermal data for the IT and facility/property assets is collected and analyzed using the various components of the IBM Tivoli Monitoring for Energy Management bundle. Tivoli Monitoring for Energy Management collects its data from several sources:
IT components (Blade Centers, Rack Servers)
Facilities/property and enterprise assets (PDU)
Uninterruptible power supplies (UPS)
Computer room air conditioners (CRAC)
The collected data is visualized and reported on in various ways. The Tivoli Enterprise Portal is used to visualize the collected thermal and energy data. By using workspaces that are provided in IBM Tivoli Monitoring for Energy Management, data can be combined with existing performance monitoring data that is provided by the Tivoli Enterprise Portal. This way offers administrators an integrated view of real-time power, temperature and application and system performance data in their data centers.
The second usage of the thermal and energy data involves the Reporting and Optimization feature of the Tivoli Monitoring for Energy Management product. The Reporting and Optimization feature reports on the usage and estimated cost of energy that is used in the data center. This scenario shows examples of reports for energy management costs in a data center, itemized by resource, such as servers, network devices, cooling equipment and other facilities in the data center. The scenario also demonstrates the modeling and recommendation engine of the Reporting and Optimization feature, which allows for the optimization of data centers based on power usage and associated costs.
Finally, thermal and energy data can be used by Tivoli Usage and Accounting to generate more complex reports for allocate costs to clients, departments, accounts, servers, and more.
3.3 Products involved
The products and product components involved in this scenario are as follows:
IBM Tivoli Monitoring V6.2.2
IBM Systems Director V6.2
IBM Systems Director Active Energy Manager™ V4.3
IBM Tivoli Monitoring for Energy Management V6.2.1
IBM Tivoli Common Reporting V1.2
IBM Tivoli Integrated Portal V1.1.1
IBM Tivoli Usage and Accounting Manager V7.1.2
3.3.1 IBM Systems Director Active Energy Manager
IBM Systems Director Active Energy Manager provides you with resources to monitor and manage power consumption in a data center, toward a green infrastructure. You use it to control energy efficiency on both IBM hardware products and third-party products. By implementing Active Energy Manager with properly configured compatible products, you are also able to determine suitable power allocation, predict energy consumption, and establish limits for power usage.
3.3.2 IBM Tivoli Monitoring for Energy Management
IBM Tivoli Monitoring for Energy Management provides management, monitoring, reporting, and recommendations to help optimize energy resources for efficient data center operation.
The Tivoli Monitoring for Energy Management software is consists of several separate component products. Tivoli Monitoring for Energy Management bundle includes the following existing software products:
IBM Tivoli Monitoring
IBM Systems Director
IBM Systems Director Active Energy Manager
In addition to these existing products that are part of the bundle, the Tivoli Monitoring for Energy Management offering also includes a number of specific “energy” monitoring agents:
Active Energy Manager agent
Eaton Power Xpert agent
Johnson Controls Metasys agent
Siemens APOGEE agent
APC InfraStruXure agent
Also included in addition to these monitoring agents is the Tivoli Monitoring for Energy Management Reporting and Optimization feature. This feature reports on the usage and estimated cost of energy used in the data center.
The next sections briefly describe the Tivoli Monitoring for Energy Management agents and the Reporting and Optimization feature.
Active Energy Manager Agent
The Active Energy Manager Agent (AEM Agent) is an IBM Tivoli Monitoring Agent that provides the integration between Tivoli Monitoring and IBM Systems Director Active Energy Manager. It is installed on the IBM Systems Director server where it collects the data from the IBM Systems Director Active Energy Manager. This way the AEM agent, indirectly, collects data from the following devices:
IBM BladeCenter®
Racks
Rack Servers
System z10s
PDUs
UPS units
Sensors
CRACs
Eaton Power Xpert agent
The IBM Tivoli Monitoring for Energy Management: Eaton Power Xpert Agent is used to monitor Eaton Power Xpert Devices. The agent uses the Simple Network Management Protocol (SNMP) to remotely collect metrics from the following devices:
PDUs through the PXGX 1000 gateway card
UPS units through the PXGX 2000 interface
4000, 6000 and 8000 Meters
Johnson Controls Metasys agent
The Johnson Controls Metasys agent uses web services to remotely collect metrics from the Johnson Controls Metasys Building Automation and Control system. This way the agent can collect data from the following devices:
CRACs
Chillers
PDUs
UPS units
Generators
Sensor devices
Siemens APOGEE agent
The Siemens APOGEE agent uses SOAP to remotely collect data from the Siemens APOGEE Building Automation and Control System. The APOGEE agent collects data for the following APOGEE devices:
Air Handle Units
Chiller Plants
Chillers
CRACs
Meters
Generators
PDUs
Sensors
UPS units
APC InfraStruXure agent
The APC InfraStruXure agent uses SNMP to remotely collect metrics from the following APC devices:
UPS units
PDUs
Cooling devices
Environmental monitoring devices
Rack Air Removal Units
 
Note: The Tivoli Monitoring for Energy Management provides monitoring of a wide range of IT and facilities devices. If your data center hosts devices that are not supported by any of these agents, you can use the IBM Tivoli Agent Builder to design and package a custom agent to track and monitor power and thermal data. Creating a custom agent and integrating it with Tivoli Monitoring for Energy Management is described in IBM Tivoli Monitoring for Energy Management Reporting and Optimization User’s Guide, SC27-2418.
Reporting and Optimization feature
The Tivoli Monitoring for Energy Management Reporting and Optimization feature is installed on Tivoli Common Reporting and Tivoli Integrated Portal. It is used to create reports for energy management costs. The Reporting and Optimization component uses the historical data from the Tivoli Data Warehouse, collected by the different Tivoli Monitoring for Energy Management agents.
Reporting and Optimization uses the Tivoli Integrated Portal for consolidation of its user interface components. The Reporting and Optimization user interface consists of three major components:
Reports concerning energy, CPU utilization and recommendations
Energy usage metrics charting portlets
Report parameter configuration portlets
The Reporting and Optimization reports can be itemized by resource, such as servers, storage, network devices, cooling equipment, and other facilities in the data center. You can analyze power usage and DCiE metrics trends for the data center using Reporting and Optimization charts.
Reporting and Optimization also has a modeling and recommendation engine to help optimize data centers, based on power usage and associated costs. Using these results, you can perform “what if” calculations to determine power savings and cost savings alternatives.
3.4 Benefits
A first and important step towards a Green IT data center is the accurate collection of power and thermal data for all devices in the data center. Visualizing the collected data provides an insight in the power consumption, energy cost and carbon emission of the components in the data center. It enables us to assess the efficiency of energy consumption in the data center. Even more important is that correctly interpreting the collected data (both real-time and historical) enables us to identify opportunities for saving energy and associated costs.
In this scenario, we first demonstrate the IBM Tivoli Monitoring for Energy Management capabilities to collect, visualize, and report on power, thermal, systems and application data from a wide variety of IT and facilities equipment. We show how Tivoli Monitoring for Energy Management data provides administrators with an unprecedented integrated view of power, temperature, and application performance. With this information, the administrator can react appropriately if problems occur that are related to power or thermal issues.
Next, we demonstrate the capabilities of the Reporting and Optimization feature of IBM Tivoli Monitoring for Energy Management. The feature uses the historical power and CPU data to identify opportunities for saving energy and associated costs by determining which servers or server pools can be put on power savings mode, standby mode, or completely powered off during certain time intervals.
3.5 Architectural diagram of integration
Figure 3-1 on page 25 shows the architectural diagram of this integration scenario. The power and thermal data is collected by the separate Tivoli Monitoring for Energy Management agents from the various IT and infrastructure components. The agents report the data to Tivoli Monitoring where it is stored and summarized in the Tivoli Data Warehouse. The data can be examined using the Tivoli Enterprise Portal client, by looking at the workspaces provided by Tivoli Monitoring for Energy Management or by creating custom workspaces and views.
Figure 3-1 Architectural overview scenario 1
The Reporting and Optimization (R&O) feature adds various energy management reports to the Tivoli Integrated Portal (TIP). For example reports that provide insight into the total energy consumption, carbon footprint and energy efficiency of a data center. Also reports are available to identify opportunities for saving energy and associated costs by determining which servers or server pools can be put on power savings mode, standby mode, or completely powered off during certain time intervals.
3.6 Implementation steps
This section describes how to integrate the Tivoli products that are used in this scenario. It does not cover the complete installation of the products, only the installation steps that are relevant for the integration of the products are shown.
First, we show how to configure the Tivoli Monitoring for Energy Management Active Energy Manager (AEM) agent. The AEM agent provides the integration between IBM Tivoli Monitoring and IBM Systems Director Active Energy Manager. Then, we show how to install and configure the Tivoli Monitoring for Energy Management Reporting and Optimization feature, which provides the integration between Tivoli Monitoring for Energy Management and the Tivoli Integrated Portal.
3.6.1 Installing and configuring the Tivoli Monitoring for Energy Management Active Energy Manager (AEM) agent
The AEM agent actually consists of two parts: an Tivoli Monitoring AEM agent and an IBM Systems Director plug-in. Both components must be installed on the IBM Systems Director server.
 
Note: We assume that you have installed the Active Energy Manager on the IBM Systems Director server. This needs to be installed before the AEM agent plug-in can be installed.
Tivoli Monitoring AEM agent is installed in the same way as any other Tivoli Monitoring agent. Detailed installation instructions can be found in the IBM Tivoli Monitoring: Installation and Setup Guide, GC32-9407. During the installation of the Tivoli Monitoring AEM agent you are presented with a configuration window as shown in Figure 3-2.
Figure 3-2 AEM Agent Configuration
The Active Energy Manager Agent configuration consists of the following settings:
Cache Update Interval: The interval in minutes at which the AEM agent retrieves the data from the IBM Systems Director AEM plug-in. The minimum value is 1 minute, the default value is 5 minutes.
Active Energy Manager Data Provider Port: The TCP/IP port to which the AEM agent connects to retrieve data from the IBM Systems Director AEM-plug-in. The default value is 4322.
Active Energy Manager Remote Power Control Port: The TCP/IP port to which the AEM agent connects for power control operations to the IBM Systems Director AEM-plug-in. The default value is 4321.
Active Energy Manager Data Collection Mode: The mode in which data is collected from IBM Systems Director AEM. Possible values are full or limited. If full is selected, all AEM data is collected. If limited is selected, only CPU, power, and temperature data are collected.
Active Energy Manager Power Management Mode: The mode in which power management is handled. Possible values are enabled or disabled. When enabled, a power cap or power saver mode can be set on supported systems using the Tivoli Monitoring Tivoli Enterprise Portal client. If disabled is selected, the power management modes are not available from the Tivoli Monitoring Tivoli Enterprise Portal client.
After installing and configuring the Tivoli Monitoring AEM agent, the AEM plug-in must be installed on the IBM Systems Director server. This plug-in is used to provide the data from IBM Systems Director Active Energy Manager to the Tivoli Monitoring AEM agent.
The installation executable for the plug-in is located on the Tivoli Monitoring for Energy Management installation media as shown on Figure 3-3
Figure 3-3 AEM plug-in installer location
The installation is started by launching the executable for the corresponding platform. The installation wizard takes you through a number of installation steps, which require no specific configuration. The installation wizard is shown in Figure 3-4.
Figure 3-4 AEM plug-in installer wizard
After successful installation of the AEM-plug-in the AEM agent should correctly appear in the Tivoli Enterprise Portal client. The Agent Status workspace should correctly display the various AEM managed objects as shown in Figure 3-5 on page 28. The active objects that are shown in this workspace will depend on the devices available on the IBM Systems Director server.
Figure 3-5 AEM Agent in Tivoli Enterprise Portal client
 
Important: When installing the Tivoli Monitoring for Energy Management AEM plug-in version 6.2.1 with IBM Systems Directory 6.2, the plug-in does not work correctly. Although the installation of the plug-in is successful, the agent status workspace in the Tivoli Enterprise Portal shows an error for the object status. The MANIFEST.MF file included with the AEM plug-in is not compatible with IBM Systems Director 6.2. For more information see the Technote:
3.6.2 Installing and configuring Tivoli Monitoring for Energy Management Reporting and Optimization
Tivoli Monitoring for Energy Management Reporting and Optimization needs to be installed on top of Tivoli Common Reporting and Tivoli Integrated Portal. As a pre-requisite the Tivoli Integrated Portal must be configured to enable base charting. If base charting support is not enabled, Tivoli Integrated Portal must be reinstalled.
The installation images for Reporting and Optimization consist of an executable that needs to be launched on the Tivoli Integrated Portal server. For example, on a Windows Tivoli Integrated Portal server the ITMFEMRO_Windows.exe is launched to install the Reporting and Optimization feature. The executable launches an installation wizard that guides the user through the installation and configuration.
The wizard prompts for the Tivoli Common Reporting (TCR) and Tivoli Integrated Portal (TIP) configuration settings as shown in Figure 3-6 on page 29.
Figure 3-6 Reporting and Optimization TCR and TIP configuration settings
The following configuration settings must be provided:
Provide TCR Installed path: This is the installation directory for the Tivoli Integrated Portal or Tivoli Common Reporting Server.
Port: The port number for the Tivoli Integrated Portal Server has a default value of 16316 (secure access). The value for unsecure access is 16315.
Profile Name: The Tivoli Integrated Portal profile name has a default value of TIPProfile in an embedded WebSphere Application Server.
Cell Name: The Tivoli Integrated Portal cell name has a default value of TIPCell in an embedded WebSphere Application Server.
Server Name: The name of the Tivoli Integrated Portal Server has a default value of server1 in an embedded WebSphere Application Server.
User Name: The Tivoli Integrated Portal administrator user ID has a default value of tipadmin.
Password: The password for the Tivoli Integrated Portal administrator user ID has no default value.
After providing the Tivoli Common Reporting and Tivoli Integrated Portal configuration settings, the wizard prompts for the Tivoli Data Warehouse configuration settings, as shown in Figure 3-7 on page 30.
Figure 3-7 Reporting and Optimization Tivoli Data Warehouse configuration settings
The Tivoli Data Warehouse consists of the following configuration settings:
Database Product type: The database server, such as DB2®, Oracle, or MS SQL Server
Hostname/IP: The fully qualified host machine name or IP address for the database server
Port: The number of the port for the database server that has a default value of 50000
DB Name: The name of the Tivoli Data Warehouse database that has a default value of WAREHOUS
TDW Schema Name: The database schema name
User Name: The administrator user ID for the Tivoli Data Warehouse database
Password: The password for the administrative user
JDBC Driver Path: If DB product type is Oracle or MS SQL Server, provide the path to the respective JDBC or ODBC driver library.
When the wizard finishes, you can verify the correct installation of Reporting and Optimization by opening the Tivoli Integrated Portal Console. After logging on, you see a new “Energy” item in the explorer on the left side. Additionally when you expand the “Reporting” item there will be a new item in the common reporting section named Tivoli Monitoring for Energy Management. This section contains the various Tivoli Monitoring for Energy Management Reporting and Optimization reports as shown in Figure 3-8 on page 31.
Figure 3-8 Verifying the installation of Reporting and Optimization
The data that is used for these Reporting and Optimization reports is extracted from the Tivoli Data Warehouse. Each report requires specific historical data. To make this historical data available the historical data collection of Tivoli Monitoring must be correctly configured.
Enabling the historical data for a specific attribute group is a two-step procedure. The historical data configuration is done using the Tivoli Enterprise Portal client’s History Configuration option. First, specify the summarization and pruning options for the attribute group. Figure 3-9 on page 32 shows the summarization and pruning settings for the attribute group KE9_ALL_BLADECENTERS_POWER_DATA.
 
Note: E9 is the product code for the IBM Tivoli Monitoring for Active Energy Management Agent.
Figure 3-9 Summarization and pruning settings for AEM attribute group
It is important to turn on summarization for all data intervals: yearly, quarterly, monthly, weekly, daily, hourly. Also if you plan to use pruning to save disk space in the database, the minimum periods of time are: 3 years, 8 quarters, 8 months, 14 weeks, 14 days, 72 hours. More aggressive pruning can cause reports to not display data for earlier periods. There is no need to keep “Detailed data” after summarization.
Next, create a collection setting for the attribute group. The collection setting is shown in Figure 3-10 on page 33. The collection settings are as follows:
Collection Interval: Interval at which the agent collects the attribute group data
Collection location: Location where the short term historical data is stored, either at the TEMA or the Tivoli Enterprise Monitoring Server.
Warehouse Interval: Interval at which the data is sent to the warehouse (1 hour, 12 hours or 1 day).
 
Note: Figure 3-10 on page 33 shows warehouse interval of one day. Set it to 1 hour if you want hourly Reporting and Optimization reports.
Figure 3-10 Historical collection settings for AEM attribute group
The IBM Tivoli Monitoring for Energy Management Reporting and Optimization User’s Guide, SC27-2418, contains a complete description of which attribute groups are required for which Reporting and Optimization reports. The reports work only if the correct attribute groups have been configured for historical data collection.
Configuring Tivoli Monitoring for Energy Management Reporting and Optimization Preferences settings
After configuring the Tivoli Monitoring Data Warehousing settings, the Tivoli Monitoring agents start collecting the data for the attribute groups and forward it to the Tivoli Data Warehouse.
Before you can use the reports of Tivoli Monitoring for Energy Management Reporting and Optimization, you must configure the preferences. This step is done from the Tivoli Integrated Portal console by selecting Energy  Optimization for Energy Management  Preferences from the left Explorer window.
Next, perform the following steps:
1. Configure the “Server Settings” by clicking the Data Refresh Settings as shown in Figure 3-11.
Figure 3-11 Reporting and Optimization Preferences
2. Select the Refresh option as shown in Figure 3-12.
Figure 3-12 Refreshing the Reporting and Optimization data
This step starts the process of loading the most current data from the Tivoli Data Warehouse. If everything is configured correctly, you see the result shown in Figure 3-13.
Figure 3-13 Data refresh successful
The tabs are as follows:
The Server tab shows the Tivoli Monitoring for Energy Management devices for which you are storing data in the Tivoli Data Warehouse. These devices include servers, rack servers and blade servers depending on the configuration of your environment.
The Storage tab is where you add storage devices such as tape and disk devices.
In the Network tab, you add network devices such as routers, switches and repeaters.
Note that the storage and network devices you add here are not added to the Tivoli Data Warehouse database; they are saved in the Reporting and Optimization configuration database.
The Power Devices and Cooling tabs list the respective devices from the Tivoli Data Warehouse. In the Power Devices tab, you may link devices (such as servers, storage devices) with a power device.
The Groups tab is where you define a logical collection of servers and devices in the data center and that share common characteristics, for example a group of servers and devices with the same physical location. These groups can be used to filter the results of an Reporting and Optimization report. For example, when running a report to display the power usage of the data center we can provide a group as a parameter to the report so that only the power usage of the devices within that group are shown.
The Server Pools tab is where you define server pools, which are a collection of servers that are designated to run the same workload or application. Server pools are not stored in the Tivoli Data Warehouse, they are stored in the Reporting and Optimization configuration database. Figure 3-14 on page 36 shows an example of server pools.
Server pools are used in the “Standby and Power-Down Recommendations Server Pool” report which is used to provide power-down and standby recommendations. In this report, Reporting and Optimization analyses the historical CPU data of the servers in a server pool to determine whether there are periods in which a server or servers within the pool can be placed in power save mode or can be powered down.
Figure 3-14 Configuring Server Pools
The Energy Rate Plan settings (Figure 3-15) is where you define several energy rate plans that are used for energy cost calculation.
Figure 3-15 Energy Rate Plans
By default, “Energy Rate Plan #1” is defined during installation of the Reporting and Optimization product. You may define additional plans as shown in Figure 3-16 on page 37.
Figure 3-16 Adding an energy rate plan
The Data Analyzer Settings define the scheduling and running time of the Reporting and Optimization data analysis. The data analysis generates the data required by the Power Savings Recommendation report set (Standby mode recommendation, Power-down mode recommendation, and Dynamic power saving mode recommendation). The scheduling options are shown in Figure 3-17.
Figure 3-17 Data Analyzer Settings
The Data Center Settings is where you define data center parameters that are not collected by the Tivoli Monitoring for Energy Management monitoring infrastructure. Here you can define the maximum power that is available to the data center and the maximum cooling capacity (Figure 3-18 on page 38). These parameters are used in the Data Center Power Capacity chart and the Data Center Cooling Capacity chart.
Figure 3-18 Data Center Settings
3.6.3 Configuring Tivoli Usage and Accounting Manager for collecting Active Energy Manager information
Tivoli Usage and Accounting Manager has several embedded data collectors on the product, called core collectors. One collector enables Tivoli Usage and Accounting Manager to collect, from IBM Tivoli Monitoring, data that is stored on Tivoli Data Warehouse and treat it to more complex costs analysis.
The following tables in Tivoli Data Warehouse that are created by Tivoli Monitoring for Energy Management are read by the Tivoli Usage and Accounting Manager collector:
KE9_ALL_RACK_SERVERS_POWER_DATA
KE9_ALL_BLADECENTERS_POWER_DATA
KE9_ALL_SYSTEM_Z10_ECS_POWER_DATA
KE9_ALL_PDUS_POWER_DATA
Configuring the collection of energy metrics and its use on Tivoli Usage and Accounting Manager reports requires the following steps:
1. Access to Tivoli Usage and Accounting Manager engine server as chargeback administrator using a URL similar to the following format:
http://IP:11052/ibm/console
2. Select Usage and Accounting Manager  System Maintenance  Data Sources, as shown in the Figure 3-19 on page 39.
Figure 3-19 Tivoli Usage and Accounting Manager tasks list
3. Create a new collector data source by clicking Collector-Database  New, as shown in Figure 3-20 on page 40.
Figure 3-20 Tivoli Usage and Accounting Manager Data Source creation
4. Introduce the correct parameters for the Tivoli Data Warehouse connection, as in Figure 3-21.
Figure 3-21 Tivoli Data Warehouse general properties
5. Click Test Connection and if it works, click OK.
6. Access to Tivoli Usage and Accounting Manager (TUAM) Engine Server as root user.
7. Change to directory:
/opt/ibm/tuam/samples/jobfiles
8. Make a copy of the sample file for the jobrunner to the correct directory and rename it:
cp SampleTDW_AEM.xml /opt/ibm/tuam/jobfiles/TDW_AEM.xml
9. Edit the file TDW_AEM.xml and look for the following lines:
<Connection dataSourceName="tf620b"/>
10. Replace these lines with the following line and save the file:
<Connection dataSourceName="TDW"/>
Where dataSourceName must be the same one that is used in Figure 3-21 on page 40.
11. Include a new line in the cron table (crontab) to create a jobrunner task by using the following command:
crontab -e
12. Add a line similar to the following one:
15 * * * * (/opt/ibm/tuam/bin/startJobRunner.sh TDW_AEM.xml >> /opt/ibm/tuam/logs/jobrunner/TDW_AEM.log 2>&1)
13. Access Tivoli Usage and Accounting Manager process engine console and go to Job Runner  Log Files. See the results for the logs (Figure 3-22).
Figure 3-22 JobRunner log files
 
Note: You might receive error messages indicating that you are not monitoring certain resources, for example PDUs. In that case, the table does not exist Tivoli Data Warehouse, and a red indicator is shown. The remaining collections work.
3.7 Scenario walk-through
This scenario describes how IBM Tivoli Monitoring for Energy Management can be used to monitor and visualize thermal and power data combined with application and system data from a real-life data center.
3.7.1 Data Center environment
The data center used in this scenario consists of the following IT infrastructure:
Rack Servers: IBM x3850 and x3950
BladeCenter Chassis: IBM HS21, LS41
Power Systems: IBM 550, 575
System Z10
The data center also contains the following facilities equipment:
Intelligent Power Distribution Unit (iPDU): APC, Eaton
Uninterrupted Power Supply (UPS): APC, Eaton
Computer Room Air Conditioner (CRAC): Liebert
Chillers: JCI Metasys
Figure 3-23 shows the setup of the monitoring infrastructure for this data center. The various IT and facilities components of the data center are monitored using IBM Systems Director for Active Energy Manager. The AEM agent forwards the data to Tivoli Monitoring, where the monitoring data is stored in the Tivoli Data Warehouse.
Figure 3-23 Data Center setup: Green IT scenario 1
The data can be viewed using various Tivoli Enterprise Portal workspaces and using the Reporting and Optimization (R&O) feature of Tivoli Monitoring for Energy Management we can analyze the data and display reports showing data center efficiency, energy cost, carbon footprint and many more. The Reporting and Optimization feature also provides features for making recommendations for power savings, standby and power down recommendations for server pools, allowing you to reduce data center power consumption and associated cost.
3.7.2 Visualizing and reporting energy and thermal metrics
The data provided by the Tivoli Monitoring for Energy Management agents can be consulted using the ready-to-use Tivoli Monitoring for Energy Management Tivoli Enterprise Portal workspaces. In our example data center we are using the AEM agent. The workspaces for the AEM agent will be displayed on the navigator item of the system where the agent is installed (which is also the IBM Systems Director machine). Figure 3-24 shows an example of the Active Energy Manager workspaces. The figure shows the data for a specific BladeCenter (BC5MM). The views in this workspace show the average power consumption (AC and DC) and the thermal data (exhaust and ambient temperature) for this BladeCenter.
Figure 3-24 Default Active Energy Manager workspace
The AEM workspaces that are provided with Tivoli Monitoring for Energy Management are all described in IBM Tivoli Monitoring for Energy Management: Active Energy Manager User’s Guide, SC23-9741.
The IBM Tivoli Monitoring administrator can create custom workspaces displaying the thermal and power data in various views. Before showing examples of custom workspaces, we briefly explain how to create custom workspaces in Tivoli Enterprise Portal.
Creating custom workspaces
This section uses a simple example to describe how to create a custom workspace. The basic basic steps are as follows:
Create a new “navigator” named “IBM Green IT Data Center”
In the new navigator create a new “navigator item” named “Real-Time Power/Thermal/CPU data”
For the new navigator item create a new workspace. The new workspace contains 3 new views showing a plot diagram of CPU, power and thermal data
Perform the following steps to create a custom workspace:
1. Create a new navigator. By default, Tivoli Enterprise Portal includes two ready-to-use navigators: Physical navigator and Logical navigator. Enterprise is a node in the Physical navigator tree. Creating a new navigator is done by clicking the Edit Navigator View from the top menu bar, as shown in Figure 3-25.
Figure 3-25 Create new navigator
2. In the Edit Navigator View window, click the Create New Navigator icon.
3. Specify the name and description of the new navigator (Figure 3-26 on page 45).
Figure 3-26 Create new navigator view
4. Click OK. The new navigator is now created and is initially empty.
5. Add navigator items to the navigator by clicking New navigator item, as shown in Figure 3-27.
Figure 3-27 Creating a new navigator item
6. The definition of the new navigator item is shown in Figure 3-28 on page 46. Specify a name, a description and a list of “Assigned” systems. The assigned system list is important because it determines for which systems we can display data in the workspaces that we will define for this navigator item.
Figure 3-28 Creating a new navigator item
In the example, we have selected two Managed System Groups: IBM AEM and NT_SYSTEM. These are dynamic groups that contain all Active Energy Manager systems and Windows systems respectively.
7. Access the new navigator from the Tivoli Enterprise Portal by using the View drop-down list of the Tivoli Enterprise Portal client (Figure 3-29).
Figure 3-29 Opening the new navigator view
After clicking the navigator item you see a workspace as shown in Figure 3-30 on page 47.
Figure 3-30 Opening the new navigator item
The workspace has not been defined yet. By default it contains two views: a web browser view and a Notepad view. In our example we want to create a workspace that contains three plot chart views, showing CPU, power and thermal data.
8. To create these three views, first split the default Notepad view (at the bottom of the workspace) in two separate view by selecting the Split View icon as highlighted in Figure 3-31.
Figure 3-31 Splitting a view
9. Replace the web browser view at the top of the workspace with a plot chart view by selecting the Plot Chart view icon from the Tivoli Enterprise Portal menu bar (highlighted in Figure 3-32 on page 48) and drag it onto the web browser view. The web browser view is now replaced by a plot chart view.
Figure 3-32 Adding a plot chart view
10. Define the properties for the plot chart view: When prompted to assign a query for the new view (Figure 3-33), click Yes. The query that is assigned to a view determines which data will be available for displaying in the particular view.
Figure 3-33 Assign query dialog
A window opens as shown in Figure 3-34.
11. Select Click here to assign a query.
Figure 3-34 View properties
12. In our example, we want to display CPU data for our Windows servers in the plot chart view. We select the Processor Overview query in the Windows OS Processor object, as shown in Figure 3-35 on page 49.
Figure 3-35 Query specification
The Processor Overview query returns a number of attributes such as %Processor Time, %Privileged Time, and more. In our plot chart view, we want to display only %Processor Time. To achieve this, we must define filters that are applied to the selected query.
13. Access the filters by clicking the Filters tab as shown in Figure 3-36 on page 50.
Figure 3-36 Defining query filters
14. For our example, we select the %Processor Time only for the _Total Processor (in a machine with multiple CPUs, the _Total is the average for all the CPUs). These filters are shown in Figure 3-37.
Figure 3-37 Filter specification
15. Besides specifying the query and the query filters, we must also define the Style of our view. Click the Style tab, shown in Figure 3-38 on page 51. This tab is where to define the plot-chart refresh interval (30 seconds in our example), the plot duration, and other settings (color, labels for x-y axis).
Figure 3-38 View style properties
After defining all the settings for our plot chart view, it will show data as shown in Figure 3-39 on page 52.
Figure 3-39 CPU Plot chart completed
16. Similarly you can define the other two views showing thermal and power data. The process of defining these views is similar to the example of the CPU plot chart view, we have just described. The main difference is the selection of the query for these views. The power and thermal data will be collected using a query of the Active Energy Manager agent. Figure 3-40 shows the query items that are available for the Active Energy Manager agent.
Figure 3-40 Selecting an Active Energy Manager query
Real-life examples of custom workspaces
The previous section, describes how to create a simple custom workspace. Figure 3-41 shows a real-life example of a custom workspace. This custom workspace contains three views. The upper view is a plot chart displaying the history of the total power consumption of the data center. The lower left view has a circular gauge showing the current power usage of the data center. The lower right view has a circular gauge showing the data center temperature.
Figure 3-41 Total power and thermal data of the data center
Another example of a custom workspace is shown in Figure 3-42. In this example, two bar chart views are used to display CPU, memory usage, and number of guest machines (left view) and temperature and power usage (right view).
Figure 3-42 Blade Centers power and thermal data
 
Tip: Another typical scenario in Tivoli Monitoring for Energy Management environment is the ability to set a threshold and be alerted of it being exceeded.
3.7.3 Visualizing and reporting energy and thermal metrics using Tivoli Monitoring for Energy Management Reporting and Optimization
The reports provided with Reporting and Optimization are divided into a number of report sets. Figure 3-43 shows the report sets that are available with Tivoli Monitoring for Energy Management Reporting and Optimization.
Figure 3-43 Reporting and Optimization Report sets
The reports and purpose of the reports are as follows:
Active Energy Manager: Contains exception reports (showing devices that are being excluded from normal reports because of problem data), top energy-use reports and top heat-gain reports.
Baseline Power Metrics: Contains the Data Center Power Usage report, displaying power usage details of the data center. See Figure 3-44 on page 55.
CPU utilization: Contains the CPU Utilization of Servers report, which shows the CPU utilization of selected servers.
Data Center Efficiency: Contains the DCIE report, which shows the Data Center Infrastructure Efficiency and PUE of the data center.
Eaton Reports: Contains Eaton breaker reports.
Historical Power Trends: Contains various reports displaying history data of power usage for various types of devices.
Power Savings Recommendations: Contains reports that use calculated data to make recommendations for power-down, standby, and dynamic power-savings settings. These recommendations are based on the historical CPU data of servers within a server pool. These reports can also be used to forecast power consumption in a future date and time window.
Power Usage Comparison: Contains the Data Center Power Usage Comparison report, which you use to compare two date periods for power usage, estimated cost, and carbon emission.
Figure 3-44 shows the Data Center Power Usage report. This report provides data concerning the total power usage, estimated cost and carbon emission of the data. It also shows how servers, facility devices, storage and network contribute to these totals.
Figure 3-44 Reporting and Optimization Data Center Power Usage report
When executing the Reporting and Optimization reports, you must specify a number of parameters such as date and time ranges. In most reports, you may also allow specify a group of devices, as shown in Figure 3-45 on page 56. Creating server groups was described in “Configuring Tivoli Monitoring for Energy Management Reporting and Optimization Preferences settings” on page 33.
This feature is particularly useful because you may use it to filter the report data for a specific group of devices. For example, the report shown in Figure 3-44 can be filtered to show only data for the devices in the “North” group.
Figure 3-45 Reporting and Optimization Report Parameters
Figure 3-46 shows the Data Center Infrastructure Efficiency report.
Figure 3-46 Reporting and Optimization Data Center Infrastructure Efficiency report
This report contains two important indicators of the “greenness” of a data center:
DCIE: The data center infrastructure efficiency
PUE: The power usage effectiveness
PUE is the original metric; DCiE was created to more easily understand the efficiency of the data center. The indicators are calculated using the following formulas:
DCiE = (IT equipment power / total facility power) x 100%
PUE = Total facility power / IT equipment power
IT equipment power includes the load that is associated with all of your IT equipment (such as servers, storage, and network equipment).
Total facility power includes IT equipment and everything that supports the IT equipment load such as PDU, CRAC, and UPS units.
A DCiE value of 33% (equivalent to a PUE of 3.0) suggests that the IT equipment consumes 33% of the power in the data center. Thus, for 100 dollars spent in energy, only 33 dollars are really used by IT equipment. Improvements in energy efficiency result in movement towards 100% DCiE, the ideal number.
A recent study initiated by IBM showed that the average DCiE is 44%. An excellent DCiE is more than 60%, thus many data centers can be optimized.
Figure 3-47 shows a scale to illustrate relative measurements of the DCiE and the PUE.
Figure 3-47 DCIE and PUE relative scale
An important feature of the Tivoli Monitoring for Energy Management Reporting and Optimization product is the recommendations reports. For example, the “Stand-by and Power-Down Recommendations for Server Pool” report displays recommendations for putting servers on standby or powering off.
When this report is generated, Reporting and Optimization evaluates the servers in a server pool during a time period and searches for servers with no or unvarying CPU load. Based on this date, it makes recommendations for placing certain servers in the pool in standby or power-off mode. Figure 3-48 on page 58 shows an example of this report. The report contains several recommendations for powering down certain servers during certain time windows.
Figure 3-48 Reporting and Optimization Standby and Power-Down Recommendations for Server Pool report
A last example of a Reporting and Optimization report is shown in Figure 3-49 on page 59. It shows the “Data Center Power Usage Comparison” report, which you may use to compare two time periods. In the example, we compared the first half of October with the second half of October. As the report shows, during the second half of October the data center consumed far more energy compared to the first half of October.
Figure 3-49 Reporting and Optimization Data Center Power Usage Comparison
3.7.4 Visualizing Tivoli Usage and Accounting Manager reports based on IBM Tivoli Monitoring for Energy Management
The reports provided by the Tivoli Data Warehouse collector for the Tivoli Monitoring for Energy Management use the following Tivoli Usage and Accounting Manager resource types:
PWRAC
PWRDC
PWRAMTMP
PWREXTMP
PWRIN
PWROUT
For accessing the ready-reports, access Tivoli Usage and Accounting Manager reporting server by using a URL similar to the following format, and click Login, as in Figure 3-50 on page 60:
http://IP/tuam/
Figure 3-50 Login to Tivoli Usage and Accounting Manager Reporting Server
For access to the reports, click Reports → Run Reports. The available report types are listed (Figure 3-51). Use them to review invoices, trends and usage per account, and type of resource, for example.
Figure 3-51 Tivoli Usage and Accounting Manager Report types
The sample report in Figure 3-52 on page 61 shows the energy consumed, and the temperature of each Account Code in a BladeCenter.
Figure 3-52 Tivoli Usage and Accounting Manager report
3.8 Summary
Figure 3-53 shows the quick summary for this integration.
Figure 3-53 Quick summary
This scenario demonstrated how the various components of IBM Tivoli Monitoring for Energy Management can be used to accurately collect power and thermal data from a wide range of IT devices and facilities and property resources. We have shown how this data can be combined with system and application performance data to provide the administrators with an unprecedented integrated view of power, temperature and application performance data.
We have also demonstrated the capabilities of the Reporting and Optimization feature of Tivoli Monitoring for Energy Management. Reporting and Optimization reports are available to calculate indicators for greenness of a data center (PUE and DCIE), it can provide us with detailed information about the power consumption, estimated cost and carbon emission of our data center.
The Reporting and Optimization feature can also help us identify opportunities for saving energy and associated costs by determining which servers or server pools can be put on power savings mode, standby mode or completely powered off during certain time intervals.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.142.195.204