Dell OpenManage Power Center 3.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview...............................................................................................................10 Key features......................................................................................................................................... 10 New in this release............................................................................................................................... 11 Topology....................................................................
Using OpenManage Power Center through Command Line Interface 31 Command Line Interface error handling........................................................................................... 32 Command Line Interface commands................................................................................................ 32 help................................................................................................................................................ 32 add_profile....................
Editing a role..................................................................................................................................49 Deleting a role............................................................................................................................... 49 Privileges........................................................................................................................................49 Managing user accounts................................................
Power monitoring levels..................................................................................................................... 73 Power thresholds.................................................................................................................................73 Viewing power details......................................................................................................................... 74 Power details for the current time window.................................
Viewing active idle power distribution graph...............................................................................89 Exporting server power report .....................................................................................................89 Underutilized servers.......................................................................................................................... 89 Configuring underutilized servers settings...............................................................
15 Configuring settings.......................................................................................114 General settings................................................................................................................................. 114 Configuring console session timeout.........................................................................................114 Setting protocol timeout periods........................................................................................
Why do I see the PostgreSQL error log "FATAL: terminating connection due to administrator command" in the Windows event log?............................................................................................ 128 Why I can’t open power center login page when I access it through Firefox 31?......................... 128 Why I encounter an error, “An internal error occurred.
1 Overview Dell OpenManage Power Center is a power management solution for the data center. It enables you to monitor and manage power consumption and temperature in your data center through the management console. Key features Table 1. Dell OpenManage Power Center features Feature Description Easy Installation The Dell OpenManage Power Center installation wizard has easy-to-use steps that allow you to install the application easily and in a few minutes.
Feature Description Event Management Allows you to monitor and manage device and group events. Report Management Allows you to generate reports for inventory and monitoring. Stranded Power Information Stranded power, also known as headroom, is the excess power available for a device group. Dell OpenManage Power Center helps you to calculate the stranded power for devices and device groups.
• View real-time system airflow history of the Dell’s 13th generation of PowerEdge servers. See Viewing system airflow history. • Replicate the data center hierarchy on the iDRAC location based on OMPC physical location modelling. See Creating discovery tasks and Updating iDRAC location. • 21 pre-defined templates to create, customize, run and export reports. See Managing reports • Modified filters to customize the results based on distinctive needs and environment.
System requirements This section describes the general requirements of OMPC and provides information on supported operating systems and the basic system requirements for server system and devices that use OMPC. Hardware and software requirements for the server system Hardware requirements You must install Power Center on a system with at least: • A dual-core processor of 2.
The Dell OpenManage Power Center installation includes the following major software tools: • Sun Microsystems Java Runtime Environment (JRE) 7 Update 25 • Apache Tomcat application server 7.0.52 • PostgreSQL 9.3.5 Hardware and software requirements for devices • Managed servers must have an Integrated Dell Remote Access Controller (iDRAC) 6, 7, or 8. For iDRAC6, the latest version is recommended. For iDRAC7, the recommended version is 1.66.65 or later. For iDRAC8, the recommended version is 2.10.10.
Getting started 2 This chapter introduces the Dell OpenManage Power Center management console, and presents several use cases that describe standard uses of Dell OpenManage Power Center. Management console introduction To use Open Manage Power Center, you must open a Web browser and log in. The management console opens with a list of the available screens in the left navigation pane, and the currently-open screen in the right pane. Table 2.
Main Screen Available actions on the screen • • • • • • • • • Set the estimated maximum power for devices Edit devices or managed groups Delete devices or managed groups Refresh the list of devices or managed groups Filter and search the list of devices Sort the list of devices Move devices from one group to another Enable or disable Emergency Power Reduction (EPR) View details of the devices or managed groups All devices, whether grouped or unassigned are listed in the All Devices tab.
Main Screen Available actions on the screen • Info On this screen you can: • • • • • • Acknowledge Events Add a note to an event Delete Events Sort events Filter events Export Events Logs The Logs screen displays information about unexpected or informational events or internal errors that occur in Dell OpenManage Power Center.
Events On the Home page, you can view a pie graph representation of events occurring in Dell OpenManage Power Center. Move the pointer over the graph to view the number of each event type. Events (Top 5 Groups) On the Home page, you can view a bar graph representation of the top five device groups, that have the highest number of events with severity as Critical, followed by the events that has the events with severity as Warning and Information.
Top 10 (Most Recent) Critical and Warning Events This option enables you to view the recent top ten critical and warning events. Common use cases This section provides a standard scenario to help Administrators to get started with Dell OpenManage Power Center. If you are a first-time user, you can follow the sequence of steps 1-5 to install Dell OpenManage Power Center and set up the group structure for monitoring your data center.
Category Supported Platform Validated Model • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 20 Dell PowerEdge R610 Server Dell PowerEdge R710 Server Dell PowerEdge R715 Server Dell PowerEdge R810 Server Dell PowerEdge R815 Server Dell PowerEdge R910 Server Dell PowerEdge M610 Server Dell PowerEdge M610x Server Dell PowerEdge M710 Server Dell PowerEdge M710HD Server Dell PowerEdge M910 Server Dell PowerEdge T610 Server Dell PowerEdge T710 Server Dell PowerEdge R2
Category Supported Platform Validated Model • • • • Dell PowerEdge FD332 Server Dell PowerEdge C4130 Server Dell PowerEdge C6220 Server Dell PowerEdge C6220 II Server HP • • • • • • • HP ProLiant DL360 G5 HP ProLiant DL380 G7 HP ProLiant DL360p G8 HP ProLiant DL360p G9 HP ProLiant BL460c G6 HP ProLiant BL460c G7 HP ProLiant BL460c G9 IBM • • • IBM System x3550 M4 IBM System x3550 M5 IBM Blade HS12 (Type 8028)/ 8028IC2 IBM Blade HS23 (Type 7875)/ 7875OI5 • Chassis Cisco Cisco UCSB-B200-M3 Intel
Category Supported Platform Eaton Validated Model • APC AP8653 PDU • Eaton Monitored PDU PW312MI0UC07 Eaton Switched PDU PW105SW0U154 • Emerson • Emerson Liebert MPH MPHNCR09NXXE30 ServerTech • ServerTech Switched PDU CW-24V4J411 ServerTech Smart CDU, 0U CS-24V1-C20M • UPS Raritan • • • Raritan DPXS20A-16 PDU Raritan PX3-4731I2V PDU Raritan PX3-4732V-F5 PDU Dell • Dell N313P Line interactive UPS w/ web card H910P Dell Online Rack UPS 3750R OL K804N Dell UPS, 2700/2300VA, 120V, 3U K802N
Using OpenManage Power Center 3 This chapter explains how to install, uninstall, and launch Dell OpenManage Power Center on Microsoft Windows and Linux platforms. Preinstallation requirement for Dell OpenManage Power Center Ensure that you assess the following before installing OMPC. • Administrator privileges. • Read/write access to the destination folder. • Ensure that the system meets or exceeds the minimum requirement. For more information, see System Requirements.
6. • Unique for each OpenManage Power Center user • Up to 20 uppercase or lowercase printable characters, except “/\[]:;|=,+*?<>.@ • Not case-sensitive Enter the password in the Password text box and then, in the Verify Password text box to confirm it. NOTE: The password must be a minimum of eight characters, with characters from at least three of the following categories: uppercase, lowercase, numeric, and non-alphanumeric.
Installed directories in Windows By default, the OpenManage Power Center package installs to C:\Program Files\Dell \OpenManagePowerCenter. NOTE: You cannot install OpenManage Power Center in the root folders of the Windows volume. You must select a non-root folder or another volume.
A dialog box is displayed, informing you that an older version of OpenManage Power Center is installed. 2. If you want to migrate the previous Power Center database, ensure that Migrate data check box is selected. This migrates most of the Power Center data, such as hierarchy information, monitoring history, policy settings, events, and credential data. Uncheck Keep Power/Thermal Data checkbox if you do not need to migrate the existing power or thermal data. NOTE: The special characters, such as \ or a spa
Alternately, you can also launch OpenManage Power Center by opening a web browser. You may need to configure your web browser to launch OpenManage Power Center. To launch OpenManage Power Center, enter the following address in lower case in your Web browser: https://:/powercenter/ For example: https://localhost:8643/powercenter/ NOTE: It is recommended to use screen resolutions of 1280*800 pixels or higher for using the OpenManage Power Center management console.
Using Dell OpenManage Power Center on Linux operating systems This section explains how to install, uninstall, launch, and upgrade Power Center on Linux platforms. Installing Power Center on a Linux server 1. Download the Power Center compressed (*.zip or *.tar.gz) installation file at dell.com/powercenter. NOTE: You must use the root user account to execute the following steps. NOTE: Use –prefix=
to save the installation binary file to a location other than the default path. 2.NOTE: You must create a super user account to log into OpenManage Power Center following installation. 11. Create a super user account. a. Type 1, then enter a super user account name. The account name must be: • Unique for each Power Center user • Up to 20 uppercase or lowercase printable characters, except “/\[]:;|=,+'*?<>.@ • Not case sensitive b. Type 2, then enter a password for the super user account.
Uninstalling Power Center in Linux NOTE: Ensure to remove all devices from the OpenManage Power Center console before uninstalling Power Center. Otherwise, the existing power cap value set in the policies (including EPR) will remain effective on the devices. Ensure to check your data center power capacity before removing the devices to avoid tripping the breaker, because the policies are also removed at the same time.
Using OpenManage Power Center through Command Line Interface 4 All commands supported by the command line interface (CLI) have the following format: ompc_cli [COMMAND] [GENERIC_OPTIONS] [COMMAND_OPTIONS] [COMMAND_TARGET] The operation must start with a valid [COMMAND]. Options can be entered anywhere after [COMMAND]. For each option that has a value, the value must be supplied immediately after the option.
Command Line Interface error handling On Microsoft Windows and Linux operating systems, an exit code is displayed indicating the successful execution of a command. An error code is displayed, if a command is not executed successfully. On Microsoft Windows operating system, when the command is successful, the CLI exit code is 0. Refer Command Line Interface Error Codes to know about specific error codes. On Linux operating system, when a command is successful, the CLI exit code is 0.
The protocol_name should be For IPMI, the properties are: • ipmi_user • ipmi_password • ipmi_key For SNMPv1v2c, the property is snmp_community_string. (Required).
add_device Usage: ompc_cli add_device [-device_name ] [-description ] [size ] [-estimated_max_power ] –device_type [-model ] [–profile ] [protocol ] [] [host_name or ip] The add_device command adds a device to OMPC by using the profile name-identified profile or by using related protocol information directly supplied through the comm
remove_profile Usage: ompc_cli remove_profile The remove_profile command removes a discovery profile. delete_device Usage: ompc_cli delete_device [-service_tag ] [] The delete_device command deletes a device. You cannot use –service_tag and device_name at the same time. If the device is a chassis, it is deleted like a group (if the blades in it are already enumerated). The chassis itself is also deleted from OMPC, and is no longer visible on the Devices page.
• The summary includes the number of impacted devices, number of impacted groups, and number of impacted policies. • All subgroups under the specified group path are counted in the summary irrespective of whether they are deleted from OMPC or not deleted. It is possible that a subgroup could be removed from the specified group path, but can not be deleted from OMPC due to a reference from another parent group.
add_device_to_group Usage: ompc_cli add_device_to_group [] GROUP_PATH [-slot ] [-service_tag ] The add_device_to_group command adds a device to a group. If a device is added to a rack, the slot_num option is used to specify into which slot the device is added. If the value of the slot is -1, the system chooses a slot automatically. When adding PDU/UPS, if you do not provide a slot option, the PDU/UPS is attached to the rack.
The move_device command moves a device from FROM_GROUP_PATH to TO_GROUP_PATH. After successfully moving the device, the device no longer belongs to FROM_GROUP_PATH; it belongs to TO_GROUP_PATH. The slot option is applicable only when moving a device (including a chassis) to a rack. It specifies which slot the device should be moved into. If it is not provided when moving a device to a rack, the CLI identifies a slot.
add_group_to_group Usage: ompc_cli add_group_to_group GROUP_PATH TO_ _GROUP_PATH The add_group_to_group command adds a group identified by GROUP_PATH to TO_GROUP_PATH. If the source group path also belongs to another parent group, after successfully adding the group, the source group belongs to both the old group and the new parent group. The exception is that a chassis can only belong to one rack (not multiple racks).
If “/” is provided as GROUP_PATH, the CLI lists the devices at the root level. list_group_props Usage: ompc_cli list_group_props GROUP_PATH The list_group_props command lists all properties for a group identified by GROUP_PATH. Properties include group_type (DC, room, rack, aisle, etc.), description, and additional properties unique to that group type. For example, for rack, the additional properties include capacity and total power capacity. This command does not apply to “/”.
The list_reports command is used to list user defined reports. REPORT_GROUP is the name of a report group. If no REPORT_GROUP is supplied, all reports are listed. Else, only those belonging to the specified REPORT_GROUP are listed. Each report is output in one row containing these fields: report_name, description, format, report_group_name, created_by and status (running or not).
After a discovery is complete, the discovered devices are added to OpenManage Power Center automatically and the count is displayed in the console. If the device discovery fails, an error message is displayed. backup_database Usage: ompc_cli backup_database -path -encrypt_password [quiet] The backup_database command is used to initiate the OMPC database backup. The -path and -encrypt_password options must be supplied.
• Setting — 0x08 • Event — 0x09 • Discovery — 0x0A • License — 0x0B • Policy — 0x0C • Connection Pool — 0x0D • Role/ Privilege — 0x0E • Login/ Logout — 0x0F • Profile — 0x10 • Available List — 0x11 • Security — 0x12 • Paging/Sorting/Filtering — 0x13 • Configuration — 0x14 • Unit Handler — 0x15 • Infrastructure — 0x16 • Unknown — 0xFF 43
Access control 5 This chapter provides information about access control in Dell OpenManage Power Center, including: • Log in/Log out — Log into OpenManage Power Center by entering user account credentials. • User/Role/Privilege Management — After logging in, you can manage user accounts from the Settings → Users screen of the management console. OpenManage Power Center provides role-based access control; to use these controls, set up roles first, and then define the privileges for each role.
• • • NOTE: You must add the SSO user account to OpenManage Power Center before you can log in using SSO. You skip the login page and enter the Home page directly using SSO. Windows Domain Account — Windows domain account. Windows Local Account — Windows local account on the OpenManage Power Center server. Linux Local Account — Linux local account on the OpenManage Power Center server. NOTE: OpenManage Power Center requires that SSL is enabled at the LDAP server, if not, the authentication fails.
SSO support. For more information, see configuration steps for Internet Explorer 10 in Configuring Web Browsers For Single Sign-on, or for instructions on SSO configuration in other web browsers, consult the appropriate browser help documentation. Additionally, for a list of OpenManage Power Centersupported web browsers, see System Requirements.
The Local Intranet window opens. 2. Click Advanced. 3. Add your Power Center site into Local Intranet—for example, server1.dcm.dell.com. Multiple domain environment Set up a multiple domain environment with the following components: • Domain Controller — There can be several Windows Active Directory (AD) domain controllers; for example, a parent domain and many child domains. • Power Center Server — This is the server with Power Center installed. It is an AD domain controller.
Windows NT LAN Manager (NTLM) authentication limitation Dell OpenManage Power Center supports Kerberos SSO for Windows domain user authentication. To enable this feature, OpenManage Power Center is configured to support the Windows integrated authentication option which includes two authentication mechanisms: Kerberos and NTLM . NTLM is not supported in OpenManage Power Center. If the client’s web browser uses NTLM to authenticate domain users for OpenManage Power Center, there are some limitations.
6. • Global Configuration • Manage Role/User • View Device/Group • Manage Device/Group • Manage Policy • Manage Event/Log • Manage License • Manage Report • Execute Power Task • Manage Power Task • Database Backup Click Save to add the custom role, or click Cancel to discard your changes and return to the Roles tab. Editing a role NOTE: You cannot edit a predefined role. 1. In the left pane, click Settings → Roles. 2.
• Execute Power Task • Manage Power Task • Database Backup Every Power Center screen functions differently depending on the privilege level assigned to a user account: • Fully functional—User can view and edit all. • Partially functional—User can partially view or edit. • Not functional—User sees a blank page. Global Configuration The Global Configuration privilege enables a user to change the Power Center global configuration—for example, the sampling interval and database settings.
NOTE: When you assign the Manage Device/Group privilege to a user, Power Center automatically assigns the View Device/Group privilege to this user as well. Users without this privilege can view all devices and group information, but cannot add/delete/edit/ manage the devices and groups.
Execute power task The Execute Power Task privilege enables a user to: • Create power control tasks • Perform power control task Manage power task The Manage Power Task privilege enables a user to: • Manage power control tasks • View power control task • Edit power control task • Re-run power control task • Stop power control task • Delete power control task Backup Database The Backup Database privilege enables a user to: • Manage database policies • Schedule database purge • Configure
– Enter a unique User Name for the account. – Enter a Password that is at least eight characters long and includes characters from at least three of the following categories: uppercase, lowercase, numeric, and nonalphanumeric. – Re-enter the password in the Verify Password text box to confirm. For a Windows installation: • Windows Local Account — Enter a unique User Name for the account.
8. Select between one and four user roles and privileges. If the role you want is not available in the drop-down list, click Create New to open the Add Role wizard. For more information, see Dell OpenManage Power Center User’s Guide. 9. Click Save to add the new group, or click Cancel to discard your changes. Editing a user or group account 1. In the left pane, click Settings → Users. 2. Select the check box next to the user or group account that you want to edit, then click Edit.
To change the current user password, see Changing A User Or Group Account Password.
Task management 6 The Tasks feature enables you to perform device discovery and power control tasks such as power-on and power-off, on a specific device or group of devices. In the left pane, click Tasks. The Tasks screen comprises the following tabs: • Discovery Tasks • Power Control Tasks By default, the Discovery Tasks tab is displayed.
This information enables you to track device status and data center information. You can also manage these discovered devices in Power Center. If there is a new or changed device in your data center, you can use the device discovery function to rediscover the devices. There are two ways to add a device in Power Center: • Using a single IP address or IP ranges or host names to discover devices on the network, at the scheduled time.
NOTE: You can edit the task to clear or select the Activate check box and view the status of the task in the Discovery Tasks tab. b. Under the Range of recurrence option, select the start and end date for the task, or select the No End Date option to run the task for an unlimited period. c. Click Next to view the summary of the discovery task in the Summary tab. The summary comprises the name of the task, protocol used, IP ranges, and schedule.
Restarting a system forcefully is called ‘warm boot’ while closing all the programs and shutting down a system is called ‘cold boot’. 3. Select the Perform random power on commands check box, specify the interval (in minutes) and the number of devices to which you want to apply the power task, and click Next. 4. In the Associated Devices/Groups tab, select the devices in the All Devices tab or in the Grouped Devices tab, select the device groups that you want to manage and click Next. 5.
NOTE: A trusted certificate must be imported into the system before the WS-MAN Validate Certificate option is enabled, or communication may fail. For more information on how to install the certificate using the Dell Chassis Management Controller, see the white paper Using Windows Remote Management (WinRM) to Remotely Manage Dell PowerEdge M1000e Using the Chassis Management Controller (CMC) available at delltechcenter.com/page/ dcim.modular.cmc.winrm.
• SSH Editing a protocol You can edit the protocol information of a device. 1. In the left pane, expand Tasks and click Protocols. The Select Connection Protocol screen is displayed. 2. Select the check box next to the protocol you want to edit. 3. In the task menu, click Edit. The Edit Protocol window is displayed. 4. Make the required changes. 5. Click Finish to save your changes, or click Cancel to discard them. Deleting a protocol 1. In the left pane, expand Tasks, and click Protocols.
Device Management 7 The Devices feature enables you to view and manage the network-discovered devices and devices added manually. You can also categorize the devices into groups. In the left pane, click Devices. The Devices screen is displayed and comprises the following tabs: • • All Devices Managed Groups By default, the All Devices tab is displayed. You can also view the details of a specific device or device group at the bottom section of the Devices screen.
4. Specify the model of the device in the Model text box. 5. From Additional Information → Size of Device (U) drop-down list, select the size of the device you want to add, in rack units (U). 6. Enter a description for the device in the Device Description text box. 7. Enter the maximum power estimate, in watts, for the device in the Estimated Max Power (W) text box. 8. Click Finish to add the device, or click Cancel to discard your changes. The device is displayed in the All Devices tab.
3. Click Details → Resource Utilization History. The Resource Utilization History- window is displayed, where an is the selected device. 4. Click X in the upper-right corner to return to the Managed Groups tab. Filtering devices The filter feature in the All Devices tab helps you to view devices that share a certain attribute. For example, you can view devices of a certain device type or devices that share an IP range. 1. In the left pane, click Devices.
You can select multiple power capabilities. • Select the Protocol check box and select the protocols used for communication. The available options are: – IPMI (Server) – WS-MAN (Chassis) – SNMPv1v2c (UPS/PDU) – SNMPv3 (UPS/PDU) – HTTPS – SSH You can select multiple protocols. • Select the Status check box and select device status from the drop-down list. The available options are: – Connected – Lost Connection – Unknown You can select multiple status.
5. Click Finish to save your changes, or click Cancel to return to the Devices screen without saving your changes. Deleting devices using a filter You can also delete devices using the Filter feature. 1. In the left pane, click Devices. 2. In the task menu, click Filter. The Device Filter window is displayed. 3. Select the filter by which you want to sort the devices list. 4. Select the check boxes next to the devices that you want to delete. 5. In the task menu, click Delete.
The iDRAC Location Update window is displayed. 4. Click Update to update the device location with the iDRAC location. NOTE: The location can be updated only for rack and tower servers. NOTE: If the iDRAC path and the device path are not synchronized, a warning message is displayed in Details → Device Details section. You may have to update the device path to ensure that it is synchronized with the iDRAC path. A table is displayed providing information about the successful location update.
NOTE: To view updated location information on supported device, you must make sure the device status has a Connected status in Power Center. It may take a few minutes for location information to update in device firmware. Creating a new group A group can represent the actual structure of a data center, room, aisle, rack, or custom. You can nest groups in parent-child relationships to represent how the devices in your data center are physically configured. 1.
5. Click Finish to return to the Devices screen, or click Cancel to discard your changes. 6. Confirm the move: a. Click the Devices → Managed Groups. b. Using the device tree, select the group to which you added the group or device, and check to make sure that the device is listed as expected. Managing Racks Dell OpenManage Power Center allows you to manage racks and the slotted and associated devices that have been added to the Power Center system.
5. Click Finish to return to the Manage Rack screen and review your changes, or click Cancel to return to the previous screen. Editing a rack-associated device 1. In the left pane, click Devices → Managed Groups. 2. From the list of devices select a rack device. 3. In the task menu, click Manage Rack → Associated Devices → Add To Rack. 4. From the list of devices, select the device you want to edit, and click Edit. 5. Make the desired changes. 6.
Viewing a rack utilization graph Dell OpenManage Power Center allows you to view a graphical representation of different aspects of rack utilization for custom and physical entitles within the Power Center system. This information can help you determine the availability of space and power within specific racks to add new devices. 1. In the left pane, click Devices → Managed Group. 2. From the list of device groups, select a group that contains a rack device.
Enabling Emergency Power Reduction 1. In the left pane, click Devices → All Devices or Devices → Managed Groups. 2. From the list of devices, select the device (data center, room, aisle, rack, or chassis) to which you need to apply the Emergency Power Reduction. 3. In the task menu, click Enable EPR. The following message is displayed. Applying Emergency Power Reduction will throttle power down to an extremely low level, and impact performance. Do you want to continue? 4. Click Yes to proceed.
Power Monitoring 8 Power Center enables the monitoring of current or historical power-related metrics (for example, power consumption or cost). This can help you understand the power status in the data center and plan for additional power infrastructure, cooling, and facility needs. You can monitor power at different device and/or group levels. You can configure power monitoring settings to meet your monitoring needs, and you can print the power status graph.
Viewing power details In the left pane, click Devices → All Devices or Devices → Managed Groups. Click the icon for a device or group, then refer to the lower detail portion of the screen. While Dell OpenManage Power Center does provide power information for PDU and other devices and groups, Power Center does not provide power details for UPS devices. For devices and groups (excluding PDU and UPS), by default, the Power graph displays the power details for the previous hour.
For example, you view power details in the 1H (1 hour) window and the maximum value at 15:00 shows 500W and the time interval is 6 minutes. This value would represent that the maximum power consumption from 14:54 to 15:00 is 500W. NOTE: It is common to see some instantaneous values exceed the Power Cap value in the Maximum line. Power Center monitors this value and controls it to the normal power range with this happens.
NOTE: T1/T2/.../Tn is the time period (in hours) at a certain flat rate. NOTE: By default, the Cost column displays 0. You must configure the cost rate to see the cost. The rate is a global setting, and can be set on the Settings → Monitoring page. NOTE: The Energy Consumption Cost section displays information based on the values configured in the Settings screen. This information should be used as an estimate only.
Scheduling (PTAS) and helps in balancing the data center workload, efficient server utilization, and thermal management from a rack level. CFM or the system airflow graph is useful from a group level (data center, room, aisle, rack, or custom groups). The values are collected only from the devices that support this feature. 1. In the left pane, click Devices → Managed Group 2. Select a data center, room, aisle, or any rack in the data center.
9 Temperature Monitoring Dell OpenManage Power Center enables monitoring of the current and historical server inlet temperature of the data centers in Power Center. This can help you understand the temperature status and identify hot spots in the data center. You can monitor the temperature status at different device/group levels. You can configure the temperature monitoring settings to meet your monitoring needs, and you can print the temperature status graph.
Time Window Description Interval 1M 1 month 1 day 3M 3 months 1 week 1Y 1 year 2 weeks NOTE: This table lists the interval when the sampling interval is at the default value (1 minute). Changing the sample interval results in interval changes for the 15Min and 1H time windows. If you change the sampling interval to 3 minutes, the interval of the 15Min time window is 3 minutes.
3. In the Details section, click the Thresholds tab. 4. Click View History next to Average Inlet Temperature Alert Thresholds. Alternately, you can also click Thermal History in the Summary tab. The temperature history graph is displayed in a new window. 5. Select the time period and attributes displayed: a. To select the time period represented in the graph, click the buttons along the top of the graph. b.
minimum temperature reading for a device in a group (Celsius or Fahrenheit). You can calculate this value according to the maximum and minimum temperature from the Temperature Details graph.
Policies 10 A power policy is a set of configurations to manage the power cap for a device or group. A policy is useful for power management in different situations. For example, you can create a policy to: • Power Cap — Make sure that power consumption does not exceed the capacity of the circuit. • Control Power Usage — Schedule power usage according to the workload of the device or group.
• Demand — Amount of power a device requests to accommodate its workload. • Estimated maximum power (Estimated max power) — The maximum power consumption allocation estimated for a device. The estimated max power is considered the peak power consumption by a device. Dynamic power caps enable all devices to execute workloads without requiring more power than the overall power cap assigned to the group.
• You cannot edit the policy of this device from the Policies page; you can only delete it. Scenario 2 — You try to import a license on a device without a license imported In this case, the following happens: • If a policy exists on the devices, a "Server Capabilities Changed" event is generated. • The Policies tab of the devices is set to Enabled in the Groups page. The power capability status of the devices is changed in the Devices page. The policy of the devices is editable.
8. 9. • Previous hour • Previous day • Previous week • Previous month • Previous quarter Enter a value in the Power Cap Value text box. Click Next to continue, click Back to return to the previous screen, or click Cancel to discontinue the task. 10. In the Power Cap Priorities window, select an option from the Priority drop-down list to set the capping priority for each device in the group.
For example, you created Policy1 for device and Policy2 for device , and you configured different priorities or power caps for the policy with the same time slot. In this case, Power Center follows these rules: • If there are overlapping policies on an entity, the policy with the lowest power cap is applied. • If there are overlapping dynamic policies on an entity and both are currently active, the highest priority (High > Medium > Low) of this entity is applied.
4. Make the required changes. NOTE: You cannot change the selected device or group while editing a policy. 5. In the Summary screen, review the changes and click Finish to save the changes, click Back to return to the previous screen, or click Cancel to discard the changes. Deleting a power policy 1. In the left pane, click Policies. The Policies screen is displayed. 2. In the list of policies, select the check box next to the policy that you want to delete.
Analysis 11 This chapter provides information about various graphs and helps in analyzing the artifacts derived from the observation. The Analysis feature enables you to view a graphical representation of the server characteristics, power or thermal characteristics, and also the underutilized servers. You can export the report in XML or CSV format. The graphs are useful in analyzing the power and thermal issues, to measure the server characteristics and utilize them efficiently.
Viewing peak power distribution graph OMPC allows you to view the details about the distribution of peak power for the servers. 1. In the left pane, click Analysis → Server Characteristics. 2. In the task menu, click Peak Power. The Peak Power Distribution — graph is displayed. 3. Set the power range distribution value by typing the value in Set Y-axis Power Range Granularity text box and click Apply.
The following formulae is used used in calculating the underutilization value of a server, Servers with an average utilization of less than or equal to , where represents a utilization percentage. The range is between 0% to 20%, by default the value is set to 15. Servers with percentile utilization being less than or equal to . , where is the percentile. The range is between 0% to 20%, by default the value is set to 95.
Viewing placement suggestions 1. In the left pane, click Analysis and then click Power Analysis. The Power & Space Analysis page is displayed. 2. In the Placement Suggestions Based on Available Power and Space section, click Launch. Placement Suggestion window is displayed. 3. From the Group Selection tab, select the data centers by clicking + to analyze the availability of power and space. Click Next. 4. In the Placement Type tab, select the type of placement required from the drop-down list.
NOTE: The estimated data should be used as a reference for planning as the final value may change during plan execution. Cooling Analysis OMPC helps you in monitoring the temperature sensors of the supported devices in a data center. The observed data is helpful in identifying the potential cooling issues of all the rooms in a data center. In the left pane, click Analysis → Cooling Analysis. The Cooling Analysis screen is displayed.
Viewing devices under large temperature span room 1. In the left pane, click Analysis and then click Cooling Analysis. The Data center Cooling Analysis page is displayed. 2. In the Large Temperature Span Rooms section, you can view the rooms with a large temperature difference between the inlet temperature and over cooling threshold value. Click on any room that is listed. Room : Devices Under Large Temperature Span Room window is displayed.
Managing reports 12 This chapter provides information on periodically generating reports for inventory and monitoring and managing the reports. Pre-defined templates are provided to help you generate the reports. By default, the reports are generated in HTML format. You can download the reports in XML or CSV format. In the left pane, click Reports. The Reports screen is displayed.
• Thermal Data — The Thermal data report displays the observed temperature values for the selected devices or device groups. • Power Utilization — The Power utilization report displays the power utilization for the selected devices or device groups. • Power Threshold Violations — The Power threshold violation reports displays the information about the power threshold violations for the selected devices or device groups.
• Power Hoarders Rack • Power Frugal Rack • Raw Monitoring Data • Comparison Report • Thermal Data • Power Utilization • Power Threshold Violations • Power Cap Violations • Power Cap Settings • Threshold Settings • Rack Fragmentation Hoarders • Rack Space Hoarders • Rack Space Frugal • Highest Temperature • Lowest Temperature • Events Report The New Report wizard is displayed. 3. Enter a name for the report in the Name text box. 4.
8. In the Associated Devices/Groups tab, select the devices or groups for which you want to generate the report. a. Click the ‘plus’ icon to add them to the Selected Devices/Groups list and click Next. NOTE: This option is displayed only for Power Headroom, General Inventory, Raw monitoring data, and Comparison report types. 9. In the Report Attributes tab, select one or more attributes that you want to include in the report. The attributes displayed are based on the report type you select. a.
Adding report groups The Report Groups feature allows you to classify the reports into different groups. For example, you can create two reports based on the available power data and add them to different groups. This helps you filter and find specific reports. 1. Click Reports → Report Group. The Add/Edit/Delete Report Groups window is displayed. 2. To create a report group, select New from the Group drop-down list. 3. Enter a name for the report group in the Name text box. 4.
Event Management 13 This chapter provides information on event types, severity levels, supported PDU/UPS events, and how to manage Power Center events. You can receive events indicating an abnormal power/temperature situation in the data center. Power Center detects: • Pre-defined events • Custom events Power Center uses port 6553 to listen for internal events. If another application is configured to use port 6553, you must change it to reserve port 6533 for Power Center.
NOTE: For more information on using the iDRAC management console, see iDRAC documentation. Table 8. Power Center events and severity levels Type Description Severity Level Blades Change In Chassis Some blades in a chassis have changed; you must manually rediscover the chassis. Power Center detects chassis changes once every 15 minutes Informative Cannot Register for Events The device cannot register device Warning events to the Power Center server automatically.
Type Description Severity Level IPMI Processor Temperature Trip Events related to the server processor temperature trip. Critical IPMI Test An IPMI test event was received. Informative MPCM Configure Failed Failed to set MPCM on the chassis. Warning MPCM Not Supported The Dell chassis does not support Warning MPCM. Upgrading firmware on the chassis might be required. PDU High Load The PDU power is greater than the high load threshold.
Type Description Severity Level UPS Battery Low Events related to low battery Critical limits and exceeded thresholds in the UPS. UPS Bypass Failure Events related to bypass failure in Critical the UPS. UPS Charge Failure Events related to charge failure in Critical the UPS. UPS Communication Lost Events related to communication Warning lost in the UPS. UPS Fan Failure Events related to power fan failure in the UPS. Critical UPS Input Power Events related to power input failure in the UPS.
Type Description Severity Level relate to this policy exceed the power cap value of this policy Policy Return To Normal Policy can now be maintained, because power consumption is less than the power cap value Informative Power Average power consumption is greater than the average value you set in the Thresholds.
Type Severity Functional area Description Protocol Timeout Change Failed Warning Monitor The protocol timeout change failed. Duplicate Device Deleted Informative Discovery The duplicated device has been deleted. Email Failure Warning Event The email alert for the event has failed. SMTP or Alert Settings might be incorrect. Internal Database Operation Error Warning Service Internal database operation failed.
PDU/UPS Model Supported Events Dell PDU PDU Low Load, PDU High Load, PDU Overload, PDU Outlet Low Load*, PDU Outlet High Load*, PDU Outlet Overload*, PDU Outlet On*, PDU Outlet Off* NOTE: Events marked with * are only supported on Dell Managed Rack PDU 6605.
b. Click View Events. The Events screen with the list of events is displayed. • From the Home screen: a. In the left pane, click Home. b. Click View Events. The Events (Overall) and Events (Top 5 Groups) graphs are displayed. The Events screen with the list of events is displayed. NOTE: By default, the protocol error events are hidden. To view these events, click Settings → Database. In the Events Logs Settings section, uncheck the Ignore Protocol Operation Events(s) option. Sorting events 1.
Deleting events 1. In the left pane, click Events. The Events screen is displayed. 2. Select the check box next to the event or events that you want to delete. If you want to delete all the events in the list, select the check box next to Severity. 3. In the task menu, click Delete. The following message is displayed. Are you sure you want to delete the selected item(s)? 4. Click Yes to proceed with the deletion. NOTE: You also have the option to delete all the events by clicking Delete All.
– UPS Charge Failure – UPS Fan Failure – UPS Communication Lost – PDU Low Load – PDU High Load – PDU Overload – PDU Outlet Low Load – PDU Outlet High Load – PDU Outlet Overload – PDU Outlet On – PDU Outlet Off – CMC SNMP Event – iDRAC SNMP Event – Protocol Operation Failed – Entity Capabilities Changed – Power Return To Normal – Temperature Return To Normal – Maximum Power – Power – Average Inlet Temperature – Policy Cannot be Maintained – Policy Return To Normal – Blades Changed In Chassis – Server Capabil
OR • Enter a name for the filter in the Filter Name (Optional) text box and click Save and Run to save the filter and sort the events based on the filter criteria. OR • Click Cancel to discard your selections and return to the Events screen. You can use the saved filters later. Sending test events from an IPMI device Power Center enables you to view test events sent from an IPMI device, therefore, you can verify the event channel between the IPMI device and Power Center server.
Security 14 Power Center is designed to ensure data confidentiality, data integrity, and the security of user authentication. Power Center not only provides authentication and access control to user accounts (see Access Control), but also protects all of the communication channels to the Power Center server and the stored sensitive data (for example, passwords) on the Power Center server.
• Dell\OpenManagePowerCenter\external\apache-tomcat\conf\context.xml • Dell\OpenManagePowerCenter\external\apache-tomcat\conf\server.xml • Dell\OpenManagePowerCenter\external\apache-tomcat\conf\tomcat-users.xml • Dell\OpenManagePowerCenter\external\apache-tomcat\conf\web.xml • Dell\OpenManagePowerCenter\keystore.ssl • Dell\OpenManagePowerCenter\pgdata\pg_hba.conf • Dell\OpenManagePowerCenter\pgdata\postgresql.conf 4. Delete all content under Dell\OpenManagePowerCenter\external\apache-tomcat\w
Action Tracked Information Start/stop network discovery Network discovery information; includes protocol profile, IP range Change session timeout Old/new value of timeout Change password for Power Center managed user User name Update role privilege Role name, old/new value of privileges Add/remove user to role User name, old/new value of role name Add/remove user User name The event logs are kept in the log file. You can find the log file(s) in: \OpenManagePowerCenter\logs\Audit.
– Import a certificate for your CA. – Import the Certificate Reply from the CA. • Scenario 3 – Import a new Trust Certificate. Some devices (for example, chassis and the exposed management interface through WS-MAN) or web service providers may provide a certificate for Power Center validation when establishing communication. If you validate the certificate and Power Center fails to verify it by building a trust path from the trust certificate in the keystore file, then communication fails.
Configuring settings 15 You configure the OpenManage Power Center settings in the Settings screen. The Settings screen comprises the following tabs: • General — Configure the timeout for console and device communication. • Monitoring — Configure the power/thermal units and energy consumption parameters. • Alerts — Configure alerts for SNMP traps, enable or disable sending alerts through emails, configure email recipients, and event severity-level.
By default, the General settings screen is displayed. 2. In the Protocols Timeout section, enter the time in seconds for the specified communication protocol (IPMI, SNMP, WS-MAN, HTTPS, or SSH). OpenManage Power Center considers the device not reachable if it cannot get any response from the device within the timeout period. 3. Click Save to apply your settings, Reset to revert to the previously saved settings. The new settings take effect the next time when Power Center communicates with the device.
• Power/Temperature sampling interval — Every 30 minutes, for example, 08:00, 08:30, 09:00, and so on. Configuring the power and temperature sampling intervals 1. On the Settings screen, click the Monitoring tab. Select the Monitoring all devices and groups check box to enable the power and thermal monitoring of all devices and groups. 2. Enter values in the Power Sampling Interval and Temperature Sampling Interval text boxes. The default power and temperature sampling interval is one minute. 3.
By default, OpenManage Power Center keeps compressed power/temperature data and event data up to 365 days and non-compressed power/temperature data up to 14 days. You can configure the duration for which OpenMange Power Center retains compressed and non-compressed data using the Data compression and Purge data (older than) fields. Data that exceeds its duration or is older than the purge date is deleted. This improves the efficiency of the data query.
NOTE: Data in the backup folder may be overwritten any existing files as part of a subsequent backup. It is recommended to generate a status file in the backup location before scheduling a database backup. 4. In the Backup Path text box, enter the location of the OMPC server to save the backup files. NOTE: If the backup location does not exist, you must have the appropriate network permissions to create a backup location and copy the files to and from the location. 5.
Option Description Bind Distinguished Name Enter a user name for the Bind search. If a name is not entered, OpenManage Power Center uses an anonymous Bind to search for the user’s login Distinguished name. For example: uid=mark, ou=manager, dc=dell, dc=com Bind Password Enter a password for the Bind Distinguished name you provided. Base Distinguished Name to Search The Distinguished name of the directory branch from where search begins.
Option Description Directory Service DA Certificate Information Displays information about the CA certificate that is in effect. From this screen you can: • View directory settings • Edit directory settings Editing directory settings NOTE: Directory settings are only applicable to Dell OpenManage Power Center installations in a Linux environment. 1. In the left pane, click Settings → Directory. 2.
– Upload Directory Service CA Certificate (optional unless Certificate Validation is enabled) — Click Browse and navigate to the CA certificate you want to upload, then click Open to upload the new certificate. – Directory Service CA Certificate Information — Displays information about the CA certificate that is in effect. 4. Click Save to save your settings, or click Reset to revert to the previously saved settings. Viewing directory settings In the left pane, click Settings → Directory.
• Power Return To Normal • Temperature Return To Normal The SNMP traps enable you to identify OpenManage Power Center-specific alerts on the third-party consoles. 1. In the left pane, click Settings → Alerts. 2. Select the Enable SNMP Traps check box. 3. Enter the following information: 4. • The IP address or hostname (Destination IP/Host) of the destination device to which events are sent. The maximum length is 255 characters. • The port number (Port) of the destination device.
4. Select the Use Credentials check box to use the user credentials for accessing the SMTP server. Licensing Dell OpenManage Power Center requires a valid license for capping the Dell’s 13th generation of PowerEdge systems (advanced power capping) and monitoring non-Dell systems (third-party power monitoring) such as Intel, HP, IBM, and Cisco. The licenses are of three types: • Evaluation — These licenses are valid for a limited duration only.
Configuring inventory settings 1. In the left pane, click Settings → Inventory. 2. In the Schedule chassis inventory search on every text box, enter the interval, in minutes, at which you want to run the chassis inventory check. The default interval is 30 minutes. 3. Click Run Now to run the inventory check immediately. The Last search for chassis inventory run at displays the timestamp at which the inventory check was last run. 4.
16 Logs The Logs feature displays information about unexpected or informational events, or internal errors that occur in OpenManage Power Center. The latest application log is displayed on the top of the list. A log can have a maximum of 1,00,000 entries. In the left pane, click Logs. The Application Logs screen is displayed.
Troubleshooting 17 This chapter lists some of the known issues you may encounter when working with Power Center. Why am I being required to log in more than once by Power Center? Possible Cause: This occurs when one of the following elements of Kerberos SSO is not correctly configured: the Power Center server, the web browser, or the AD domain controller configuration. Resolution: Correctly configure your Power Center server and web browser for Kerberos SSO.
Why did my connection to Dell iDRAC6 devices (Dell PowerEdge Servers) fail, when the network connection status is Connected? Possible Cause: Dell iDRAC6 devices are limited to three concurrent connection sessions, and you have reached the limit. There are various reasons that may cause the session to be occupied for a while until it is relinquished—for example, you used incorrect credential information to connect with Dell iDRAC6 devices for three times or more within a short period.
– If the device number is large, perform the following steps. Power Center removes the policies first, and then remove the devices. 1. Install Power Center. 2. Add all the devices to the Power Center management console. 3. Create a logical group that contains all of the devices, and then create a power policy for this group. 4. Remove all of these devices from the Power Center management console.
Why I encounter an error, “An internal error occurred. Contact Dell support for help: subordinate error code: 0x8f0c1301”, the Home page when OpenManage Power Center server is installed on SUSE Linux Enterprise Server 11 SP2? Possible Cause: SUSE Linux Enterprise Server 11 SP2 has a known time zone issue which cause power center fail to get the right time zone of server. For more information, visit www.suse.com/support/ update/announcement/2012/suse-ru-20121258-1.html.
Why is the “policy return to normal” event not displayed when the only device in the Chassis Management Controller (CMC) is deleted? Possible Cause: When the last blade in the chassis is deleted, the power value returns to “–1” as there is no device in the chassis. The comparison between the power value and the policy capping fails and the “policy return to normal” event is not triggered. Resolution: You can add a blade to the chassis if the power value does not exceed the power capping value.
A Upgrade failure recovery on Microsoft Windows operating system Check OMPC status If the installer process is stopped or server is switched off during upgrade, the upgrade fails. Follow the steps to troubleshoot the upgrade failure scenario: 1. Run wmic product where name='Dell OpenManage Power Center' get version command on the windows command line interface to get the current version OMPC. 2. If the OMPC old version is displayed, for example 3.0.1.
NOTE: In some case (Power off or killed OMPC installer program), there is still a corrupt OMPC in the Windows OS. It may not be able to uninstall by the above command and will block any new OMPC installed. In this case, you need to remove OMPC manually. 2. a. Open register table using the regedit command and search all key or value include {79427712-CD0A-4114-A571-6BCA07F2EE0A}. Remove all key or value found. b. Stop all OMPC services if they exist. c.
2. Execute below SQL to clean old database: DROP DATABASE IF EXISTS dcm_tmp and DROP DATABASE IF EXISTS dcmapp_tmp. 3. Recover other disk files. Follow the process specified in Rollback to previous OMPC version.
B Upgrade failure recovery on Linux operating system Use install.sh command in the new OMPC version package to do upgrade or install OMPC. The install.sh command detects the version of OMPC. if there is an old version installed, upgrade process is initialized. If not, then a new version is installed. Check OMPC status If the installer process is stopped or server is switched off during upgrade, the upgrade fails. Follow the steps to troubleshoot the upgrade failure scenario: 1.
2. Check the database version: a. [PGSQLDRV]= postgresql-9.3-1102.jdbc4.jar if target version is above or equals to 3.1; b. [PGSQLDRV]= postgresql-8.3-603.jdbc4.jar if target version below 3.1; You can get the current database version by the DB_VERSION item in [InstDir]/dbinfor.tmp. Check the availability of /etc/ompc/upgradeok: If it exists, it means upgrade completed. If not, new OMPC installed but upgrading yet to be completed. Rollback to previous OMPC version 1.
