Dell OpenManage Power Center v1.2 Owner's Manual

Dell OpenManage Power Center 1.2 User Guide

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.

Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc. Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware trademarks of VMware, Inc. in the United States or other countries. Corporation.

2012 - 12

Virtual SMP

vMotion

is a registered trademark of International Business Machines

IBM

vCenter

and

vSphere

are registered trademarks or

Rev. A01

Contents

Notes, Cautions, and Warnings...................................................................................................2

1 Overview.......................................................................................................................................9

Key Features.............................................................................................................................................................9

Topology...................................................................................................................................................................9

System Requirements.............................................................................................................................................10

Hardware and Software Requirements for the Server System.......................................................................10

Hardware and Software Requirements for Devices........................................................................................11

2 Getting Started...........................................................................................................................13

Management Console Introduction........................................................................................................................13

Common Use Cases................................................................................................................................................14

3 Installing, Uninstalling, and Launching Power Center........................................................15

Installing, Uninstalling, and Launching Power Center In Windows.......................................................................15

Installing Power Center On A Windows Server...............................................................................................15

Installed Directories In Windows.....................................................................................................................16

Power Center Services in Windows................................................................................................................17

Upgrading.........................................................................................................................................................17

Uninstalling Power Center In Windows...........................................................................................................17

Launching Power Center In Windows.............................................................................................................18

Configuring ESC for Internet Explorer..............................................................................................................18

Installing, Uninstalling, and Launching Power Center In Linux..............................................................................19

Installing Power Center On A Linux Server......................................................................................................19

Installed Directories In Linux...........................................................................................................................20

Power Center Services In Linux.......................................................................................................................20

Uninstalling Power Center In Linux..................................................................................................................21

Launching Power Center In Linux....................................................................................................................21

4 Command Line Interface..........................................................................................................23

Command Line Interface Error Handling................................................................................................................23

Command Line Interface Commands......................................................................................................................24

help...................................................................................................................................................................24

add_profile.......................................................................................................................................................24

update_profile..................................................................................................................................................25

add_device.......................................................................................................................................................25

update_device..................................................................................................................................................25

rediscover_device............................................................................................................................................25

remove_profile.................................................................................................................................................26

delete_device...................................................................................................................................................26

add_group........................................................................................................................................................26

delete_group....................................................................................................................................................26

update_group...................................................................................................................................................27

add_device_to_group......................................................................................................................................27

remove_device_from_group............................................................................................................................28

move_device....................................................................................................................................................28

move_group......................................................................................................................................................29

add_group_to_group........................................................................................................................................29

List commands.................................................................................................................................................29

list_device_props.............................................................................................................................................30

list_devices......................................................................................................................................................30

list_group_props..............................................................................................................................................30

list_groups........................................................................................................................................................30

find_device.......................................................................................................................................................31

Command Line Interface Error Codes.....................................................................................................................31

5 Access Control..........................................................................................................................33

About Authentication..............................................................................................................................................33

Logging In...............................................................................................................................................................33

Logging in with User Name and Password......................................................................................................34

Log in with Single Sign-on (SSO)......................................................................................................................35

Multiple User Login..........................................................................................................................................38

Logging out.............................................................................................................................................................38

Managing User Roles.............................................................................................................................................38

Adding a Custom Role......................................................................................................................................38

Editing A Role...................................................................................................................................................38

Deleting A Role.................................................................................................................................................39

Managing User Accounts.......................................................................................................................................39

Adding A User Account....................................................................................................................................39

Adding A Group Account.................................................................................................................................40

Editing A User Or Group Account.....................................................................................................................40

Deleting a User or Group Account...................................................................................................................40

Changing A User Account Password...............................................................................................................40

Roles and Privileges...............................................................................................................................................41

Global Configuration.........................................................................................................................................41

Manage Role/User...........................................................................................................................................41

View Device/Group..........................................................................................................................................42

Manage Device/Group.....................................................................................................................................42

Manage Policy.................................................................................................................................................42

Manage Event..................................................................................................................................................42

Viewing Current User Information..........................................................................................................................43

Licensing.................................................................................................................................................................43

Importing a License..........................................................................................................................................43

6 Device Discovery......................................................................................................................45

New Device Discovery...........................................................................................................................................45

Supported and Unsupported Devices..............................................................................................................45

Adding a Device from the Network..................................................................................................................47

Adding a Device Manually...............................................................................................................................48

Rediscovering Devices in a Chassis................................................................................................................49

Protocol Profile.................................................................................................................................................49

7 Device Management................................................................................................................51

Discovering Devices...............................................................................................................................................51

Viewing Devices.....................................................................................................................................................51

Editing a Single Device...........................................................................................................................................52

Editing Multiple Devices.........................................................................................................................................52

Editing a Protocol....................................................................................................................................................53

Removing Devices..................................................................................................................................................53

Device List: Filter.....................................................................................................................................................53

Sorting Devices.......................................................................................................................................................54

8 Group Management..................................................................................................................55

Mapping Group Structure Information...................................................................................................................55

Finding a Group or Device......................................................................................................................................55

9 Groups.........................................................................................................................................57

Adding a New Group..............................................................................................................................................57

Adding a Custom Group..........................................................................................................................................58

Adding Existing Group(s) as the Child of a Parent Group.......................................................................................58

Adding Existing Device(s) as the Child of a Parent Group......................................................................................58

Moving Groups or Devices.....................................................................................................................................59

Deleting a Group or Deleting a Device from a Group.............................................................................................59

Editing a Group.......................................................................................................................................................59

Managing a Group..................................................................................................................................................59

Viewing Group or Device Details............................................................................................................................59

Creating a New Power Policy..........................................................................................................................60

Enabling or Disabling a Power Policy..............................................................................................................61

Deleting a Power Policy...................................................................................................................................61

Applying an Emergency Power Reduction.......................................................................................................61

Stopping an Emergency Power Reduction......................................................................................................62

10 Power Monitoring...................................................................................................................63

Power Monitoring Levels........................................................................................................................................63

Power Monitoring Configuration............................................................................................................................63

Power Thresholds............................................................................................................................................63

Viewing Power Details............................................................................................................................................64

Power Details for the Current Time Window...................................................................................................64

Power Details for a Different Time Window....................................................................................................65

Power Details for Racks...................................................................................................................................65

Viewing Energy Consumption.................................................................................................................................65

Monitoring PDU Power...........................................................................................................................................66

Monitoring UPS Power...........................................................................................................................................66

Power Dashboard...................................................................................................................................................66

Printing the Power Monitoring/Dashboard Graph..................................................................................................67

11 Temperature Monitoring........................................................................................................69

Temperature Monitoring Level...............................................................................................................................69

Temperature Monitoring Configuration..................................................................................................................69

Temperature Thresholds..................................................................................................................................69

Viewing Temperature Details.................................................................................................................................70

Temperature Details for the Current Time Window.........................................................................................70

Temperature Details for a Different Time Window..........................................................................................70

Chassis Details.................................................................................................................................................71

Monitoring the Temperature of the Chassis/Blade Server.....................................................................................71

Monitoring the Temperature of Devices/Groups....................................................................................................71

Temperature Dashboard.........................................................................................................................................71

Printing the Power Monitoring/Dashboard Graph..................................................................................................72

12 Policies......................................................................................................................................73

Dynamic Power Caps..............................................................................................................................................74

Power Policy Capabilities.......................................................................................................................................74

Scenario 1 — The license expires or is not imported......................................................................................74

Scenario 2 — You try to import a license on a device without a license imported.........................................75

Upgrading Device Power Policy Capability............................................................................................................75

Creating a New Power Policy.................................................................................................................................75

Viewing Policy Details............................................................................................................................................76

Policy Priority Levels..............................................................................................................................................76

Policy Modes..........................................................................................................................................................77

Enabling or Disabling a Power Policy.....................................................................................................................77

Displaying Policies in the Power Details Graph.....................................................................................................77

Editing A Power Policy............................................................................................................................................78

Deleting a Power Policy..........................................................................................................................................78

Filtering Power Policies..........................................................................................................................................78

Emergency Power Reduction.................................................................................................................................78

Canceling EPR..................................................................................................................................................79

Policy-Related Events.............................................................................................................................................79

13 Comparing................................................................................................................................81

Changing the Time Period.......................................................................................................................................81

Adding a Device or Group for Comparison.............................................................................................................81

Removing/Changing a Device or Group..................................................................................................................81

Printing the Comparison Result..............................................................................................................................82

14 Event Management.................................................................................................................83

Predefined Events...................................................................................................................................................83

Custom Events........................................................................................................................................................85

Supported PDU and UPS Events.............................................................................................................................86

Event Severity Levels..............................................................................................................................................86

Viewing Events.......................................................................................................................................................87

Sorting Events.........................................................................................................................................................87

Editing Events..........................................................................................................................................................87

Deleting Events.......................................................................................................................................................87

Deleting an Event.............................................................................................................................................88

Deleting all Events............................................................................................................................................88

Filtering Devices.....................................................................................................................................................88

Filtering Events by Group/Device.....................................................................................................................88

Sending Test Events from an IPMI Device.............................................................................................................89

15 Security.....................................................................................................................................91

Starting Services with a Windows Operating System Standard User Account.....................................................91

Operating System Hardening..................................................................................................................................92

Audit Log.................................................................................................................................................................93

Managing Certificates............................................................................................................................................93

16 Configuring Power Center Settings......................................................................................95

Monitoring Settings................................................................................................................................................95

Recommended Sampling Intervals for Performance Tuning and Scaling.......................................................95

When are the settings effective?.....................................................................................................................95

Default Units Settings.............................................................................................................................................95

Protocol Type Device Timeout Settings.................................................................................................................96

Energy Consumption Settings.................................................................................................................................96

Database Policy Settings........................................................................................................................................96

Installation Settings................................................................................................................................................97

Database Settings............................................................................................................................................97

LDAP Settings...................................................................................................................................................98

17 Backup and Recovery..........................................................................................................101

Power Center Data Files for Backup and Recovery.............................................................................................101

Backing up Power Center Data............................................................................................................................102

Recovering Power Center Data............................................................................................................................102

18 Troubleshooting.....................................................................................................................105

Why can’t I access the Power Center management console from a Web browser, even though the Power

Center server is running normally?.......................................................................................................................105

Why can’t I play videos by clicking links on the Getting Started or Compare pages?.........................................105

Why was I automatically logged out of Power Center?.......................................................................................105

Why did my connection to Dell iDRAC6 devices (Dell PowerEdge Servers) fail, when the network

connection status is Connected?.........................................................................................................................105

Why can’t Power Center receive events sent from devices?..............................................................................105

Why does the error "Server side error has occurred, please contact support" display when I launch the

Power Center management console?..................................................................................................................106

Why does the Firefox Web browser crash after running for an extended period of time?..................................106

Why can’t I see Power/Temperature data in the Dashboard tab?.......................................................................106

Why are previously-existing power policies (including EPR) still effective on devices when Power Center

is corrupted or has been uninstalled?..................................................................................................................106

Why do I see the PostgreSQL error log "FATAL: terminating connection due to administrator command" in

the Windows event log?.......................................................................................................................................107

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. OMPC Features

Feature Description

Power Monitoring Monitors power-related metrics on the following levels:

• Individual device

• Data center/Room/Aisle/Rack/Chassis

• User-defined group

Temperature Monitoring Monitors data center temperature data.

Power Control Creates policies that control data center power

consumption at the device and group levels.

Device Discovery Supports Dell enterprise systems including PowerEdge

blade and tower/rack servers, chassis, and many different PDU and UPS devices.

Role-based Access Control Supports user authentication and multiple role-based

privilege levels.

Event Management Allows you to monitor and manage device and group

events.

Topology

The following figure shows how to use a Web browser to access the Power Center server and manage the data center.

Figure 1. OMPC Topology Diagram

System Requirements

Hardware and Software Requirements for the Server System

NOTE: For the most current list of hardware and software requirements, refer to the readmefirst file and the Release Notes which may be found at www.dell.com/support/manuals.

Software Requirements

Power Center supports the following operating systems:

• Microsoft Windows SBS 2011

• Microsoft Windows Server 2008 Standard/Enterprise/Datacenter (x86, x64)

• Microsoft Windows Server 2008 R2

• Microsoft Windows Server 2012

• Microsoft Windows 7

• Microsoft Windows 8

• Red Hat Linux 5.8 x86_64

• Red Hat Linux 5.9 x86_64

• Red Hat Linux 6.2 x86_64

• Red Hat Linux 6.3 x86_64

• SUSE Linux Enterprise Server 10 SP4 x86_64

• SUSE Linux Enterprise Server 11 SP2 x86_64

Power Center supports the following Web browsers:

• Mozilla Firefox 10, 11, 12, 13, 14, and 15

• Microsoft Internet Explorer 8.0, 9.0 and 10

Power Center is validated to work with the following virtualization environment:

• VMware ESX (3.5/4.0)

• Microsoft Server 2008 Hyper-V

The Power Center installation includes the following major software tools:

• Sun Microsystems Java Runtime Environment (JRE) 6

• Apache Tomcat application server

NOTE: Power Center 1.2 does not support PostregSQL 9.0. Only PostgreSQL 8.3.5 is supported as a remote database server.

• PostgreSQL 8.3.5

Hardware Requirements

You must install Power Center on a system with at least:

• A dual-core processor of 2.6Ghz or higher

• 4GB RAM

• 60GB free space of hard drive

• Gigabit bandwidth of network infrastructure

Hardware and Software Requirements for Devices

• Managed servers must have an Integrated Dell Remote Access Controller (iDRAC) 6 or 7. For iDRAC 6, the latest version is recommended. For iDRAC 7, the recommended version is 1.23.23.

• Power Distribution Unit (PDU) and Uninterruptable Power Supply (UPS) devices must comply with the Management Information Base (MIB) provided by the vendor through SNMP interface.

• Devices must provide exclusive access for Power Center. This is because the policies set on the devices from other management software will impact the Power Center power control function.

• The Baseboard Management Controller (BMC) user, through which Power Center communicates with devices, must be a local user with the Administrator role. The device must be configured to allow the Administrator to use at least one of the cipher suite levels 0-3, and enable the IPMI over LAN setting.

• The WS-MAN user, through which Power Center communicates with the chassis, must be a local user with the Administrator role. The chassis must be configured to enable the Web Server service.

• Chassis Management Controller (CMC) that supports all devices installed in your managed network

NOTE: For a list of OMPC-supported devices, see Supported Devices and Unsupported Devices.

Getting Started

This chapter introduces the OpenManage Power Center management console and presents several use cases that describe standard usages of Power Center.

Management Console Introduction

To use Power Center, you must open a Web browser and log in. The management console opens with a list of the available pages in the left navigation pane, and the currently-open page in the right pane.

Table 2. Main OMPC Pages

Main Page Available Actions on This Page

Getting Started This page introduces Dell OpenManage Power Center

features, and lists initial setup steps and additional tasks you can complete after setup. You can select a video from the video library to help you get started, or click help links to get additional information.

Groups This page enables you to set up and organize your devices

into groups. You can view or edit data center power information for a

group and view information for the devices in a rack or chassis.

This page includes these tabs: Events, Dashboards, Power Details, Temperature Details, Policies, Thresholds.

Discovery This page discovers supported devices in the data center

network. After a device is discovered, it is automatically added to the Devices page and can be managed by Power Center. From this page, you can:

• View the active searches

• View the recent discovery jobs

• Rerun a search using the discovery search criteria

Devices This page lists network-discovered devices and devices

added manually. From this page, you can:

• Add supported or unsupported devices to the Devices page

• Remove devices from the Devices page

• Edit device information for a single device or multiple devices

• Edit protocol information for a single device

• Filter and sort devices to meet current needs

Policies This page enables you to manage the power policies.

Main Page Available Actions on This Page

Compare This page enables you to compare power and temperature

status and energy consumption between the selected groups and/or devices. You can also print comparison results.

Settings This page enables you to view or configure all settings.

Settings — User Accounts This page enables you to set up and manage user

accounts.

Settings — Licensing This page enables you to view or import a license.

Event Logs This page lists all events at all severity levels.

From this page, you can:

• View all events

• Add comments to events

• Delete the events

• Filter and sort the events

Common Use Cases

This section provides a standard scenario to help users in an Administrator role get started with Power Center.

If you are a first-time user, you can follow the sequence of steps 1-5 to install Power Center and set up the group structure for monitoring your data center. Then, see steps 6, 7, and/or 8 to use Power Center for monitoring, comparing power and temperature data between devices and/or time slots, and creating policies:

1. Install OpenManage Power Center.

2. Launch Power Center.

3. Discover devices and add one or more devices manually or from the network.

4. Manage your devices. You can delete, edit, and filter devices. You can also click Add in the Devices page to add a device manually, then manage it.

5. Create one or more data center group structures.

6. Create one or more power policies, and apply to devices.

7. Monitor Power and Temperature events on devices.

8. Compare power/temperature status and the energy cost for two or three devices/groups.

Installing, Uninstalling, and Launching Power Center

This chapter explains how to install, uninstall, and launch Power Center on both Windows and Linux platforms.

You can use a Web browser to launch Power Center.

Installing, Uninstalling, and Launching Power Center In Windows

This chapter explains how to install, uninstall, and launch Power Center on Windows platforms.

Installing Power Center On A Windows Server

To install Dell OpenManage Power Center on a Windows Server, you must have Administrator privileges. Otherwise, the installation may fail.

Before installing Power Center, verify that your system meets the minimum system requirements.

NOTE: During the installation, Power Center uses the Windows Network Service account to start the Power Center service. For better security, you can turn off the Power Center services and change to an account other than the Windows Network Service account to start the Power Center services.

1. Download Power Center at http://www.dell.com/powercenter.

2. Double-click OpenManagePowerCenter.exe.

3. On the Installation Wizard home page, click Next.

4. On the License Agreement page, read the license agreement, select I accept ..., and then click Next.

5. On the License page, read the license message, and then click Next.

6. On the Destination Folder screen, either leave the default installation path or browse to your desired installation path. Click Next.

NOTE: The installation path only supports ANSI characters (English characters, numbers, and simple symbols). Do not use an installation path with non-ANSI characters.

7. On the OpenManage Power Center Setting screen, configure the following HTTPS settings, and then click Next.

– HTTPS Port — By default, Power Center uses port 8643 for HTTPS communication. To select a different

port, enter a new port number between 1000 and 9999.

– Keystore Password — Enter a password that will be used to access the keystore file. In the Verify

Password field, enter the password again to confirm. The password must be more than 5 characters, and cannot contain non-ANSI characters and double quotes (").

8. On the OpenManage Power Center Setting screen, enter the following information for the PostgreSQL database server account.

– Use another database server — This option enables you to install the Power Center database on a remote

server. To use this option, the remote system must meet the following requirements:

* The remote server must have a running PostgreSQL database service with at least v8.3.5. You can

download it from http://www.postgresql.org.

* There is no Power Center database on the remote server.

* The database service on the remote server is able to accept remote database connections.

* The correct connection information (Server Name, Database Port, Database User Name, Database

User Password) is provided.

If you enabled the option to use another database server, enter the following information about the database service on the remote server:

– User Name — Enter your PostgreSQL database server user name.

– User Password — Enter your PostgreSQL database server user password.

NOTE: The password must be a minimum of 8 characters in length with characters from at least three of the following categories: uppercase, lowercase, numeric, non-alphanumeric. It cannot include spaces.

– Verify password — Enter the password again to confirm.

– PostgreSQL Port — Default value is 6443. If another database is already using the default port, enter a new

port number between 6000 to 9999.

– PostgreSQL Data Directory — The location of PostgreSQL data. If you enabled the option Use another

database server, you do not need to enter information for this field.

9. In the OpenManage Power Center Settings screen, continue to configure the Power Center super user account (also called installation account in the User Accounts page) settings. This account is used for logging into the Power Center management console:

– User Name — Enter a name for the super user, or leave the default name (admin). The user name must be:

* Unique for each Power Center user

* Up to 20 uppercase or lowercase printable characters, except “/\[]:;|=,+*?<>.@

* Not case sensitive

– User Password — Create the user password for the super user account.

NOTE: The password must be a minimum of 8 characters, with characters from at least three of the following categories: uppercase, lowercase, numeric, and non-alphanumeric. The password can include spaces.

– Verify password — Enter the password again to confirm.

10. Click Next.

11. On the Ready to Install the Program screen, click Install.

12. After installation completes, click Finish to exit the installation wizard.

Installed Directories In Windows

By default, the Power Center package installs to C:\Program Files\Dell\OpenManagePowerCenter.

NOTE: You cannot install Power Center in the root folders of the Windows volume. You must select a non-root folder or another volume.

The Power Center package includes the following folders:

• bin — Power Center binaries

• conf — Power Center configuration files

• external — Other applications installed by Power Center

• Logs — Power Center event logs

• Pgdata (default) — Database files

To protect data, the following files are accessible only to Network Service or Administrator users:

• OpenManagePowerCenter\conf\app.config.xml

• OpenManagePowerCenter\external\apache-tomcat\conf\server.xml

Power Center Services in Windows

Power Center includes the following services:

• Dell OpenManage Power Center – The Apache Tomcat server that hosts the Power Center web application which passes action requests to the Power Center server.

• Dell OpenManage Power Center Database Server – The PostgreSQL internal database for Power Center.

• Dell OpenManage Power Center SNMP Dispatcher – If the Windows SNMP trap service is installed, then it reroutes SNMP traps to the Dell OpenManage Power Center Server service. If the Windows SNMP trap service is not installed, this service will automatically stop.

NOTE: If the Windows SNMP trap service is installed, make sure it is not disabled. Otherwise, Power Center cannot function properly.

• Dell OpenManage Power Center Server – The Power Center server core service. It carries out all actions including communication with devices.

To stop or start a service, select the appropriate service from the Windows Services list, and select the action to perform.

Power Center uses the Network Service account to start all services. You can change to a normal Windows operating system user account for security purposes. For more information on how to change the account, see Starting Services

with a Normal Windows OS User Account.

Upgrading

To upgrade Power Center from a previous version, the system must meet the following minimum requirements:

• At least 363 MB of free space on the C: drive

• Running Windows Server 2008 or later

1. Install OpenManage Power Center. For more information, see Installing Power Center.

A dialog box displays, informing you that an older version of OMPC is installed.

2. If you want to migrate the previous Power Center database, ensure that Migrate previous data check box is selected. This will migrate most of the Power Center data, such as hierarchy information, monitoring history, policy settings, events, and credential data.

3. To upgrade, click Upgrade now. If you do not want to upgrade, click Cancel.

Uninstalling Power Center In Windows

NOTE: Make sure to remove all devices from the Power Center management console before uninstalling Power Center. Otherwise, the existing power cap value set in the policies (including EPR) will remain effective on the devices. Make sure to check your data center power capacity before removing the devices to avoid tripping the breaker, because the policies will be removed at the same time.

1. Go to Add/Remove Programs.

2. Select Dell Power Measurement, Mitigation, and Management, and click Remove.

3. Click Yes to confirm. Follow the on-screen instructions.

If you did not check the Use another database server option during installation, the uninstall program removes the Power Center database and configurations.

If you checked the Use another database server option and used another database during the installation, the uninstall program does not uninstall the database.

Launching Power Center In Windows

Open a Web browser. You may need to configure your Web browser to launch Power Center.

To launch Power Center, enter the following address in lower case in your Web browser: https://

<Server_Name>:<HTTPS_Port>/powercenter/

For example: https://localhost:8643/powercenter/

NOTE: For Windows Server 2003, if you reinstall Power Center on the same server using a different HTTPS port, you must log out of Windows, then log in to make sure the new HTTPS port takes effect.

NOTE: Power Center only supports screen resolutions of 1024*768 pixels or higher. Make sure to correctly set the screen resolution on your system before launching the Power Center management console.

Select a user account and enter your name and password. The Power Center console appears. You can start to use the Power Center functions.

Configuring ESC for Internet Explorer

If the Power Center server uses Windows Server 2008 or Windows Server 2012 and the Web browser is Internet Explorer 8 or above, then the Internet Explorer Enhanced Security Configuration (ESC) feature is enabled by default. To make sure Power Center functions properly in Internet Explorer, you must either disable this feature or configure Internet Explorer to trust the Power Center site and links.

Disabling ESC in Windows Server 2012

1. Close any open Internet Explorer windows.

2. Open Server Manager.

3. On the left navigation bar, click Local Server.

4. Under Properties, locate IE Enhanced Security Configuration; click the On or Off radio buttons for both Administrators and Users as desired to enable or disable the feature for those groups.

5. Click OK to save your selections.

Disabling ESC in Windows Server 2008

1. Go to Control Panel → System and Security → Administrative Tools → Server Manager.

2. In the Server Summary Security Information section, click Configure IE ESC.

The Internet Explorer Enhanced Security Configuration window opens.

3. Set enhanced security configuration Off for both administrators and users.

Configuring ESC to Trust the Power Center Site and Links

1. Go to Internet Explorer → Tools → Internet Options → Security.

2. Click Trusted Sites, and add

NOTE: You may need to restart Internet Explorer for the configuration to take effect.

about: Blank

as a trusted site.

Installing, Uninstalling, and Launching Power Center In Linux

This section explains how to install, uninstall, and launch Power Center on Linux platforms.

Installing Power Center On A Linux Server

To install Dell OpenManage Power Center, you must have Administrator privileges.

Before installing Power Center, verify that your system meets the minimum system requirements.

NOTE: Use –prefix=<dir> to save the installation binary file to a location other than the default path.

1. Download the Power Center compressed (*.zip or *.tar.gz) installation file at http://www.dell.com/powercenter.

NOTE: You must use the root user account to execute the following steps.

2. Decompress the installation file to produce rpm and install.sh files

NOTE: While the default installation directory is /opt/dell/ompc, Dell recommends that you direct the installation to INSTALLDIR as described in the following step.

3. Run the following command to install the binary and automatically launch the initialization tool:

#./install.sh <INSTALLDIR>

4. Type rpm –i on the Linux command line interface to extract the binary files.

5. In the Linux terminal, use the initialization tool to install and configure Power Center.

The Welcome screen of the Dell OpenManage Power Center Installation Wizard appears.

6. Press <Enter> to continue.

The End User License Agreement appears.

7. Read the EULA agreement, then type accept to continue.

The Power Center License screen appears.

8. Review the license message, then press <Enter> to continue.

The HTTPS Setting screen appears.

9. Configure the HTTPS settings by entering a number from the list, then providing the information requested.

– HTTPS Port—Enter a port number between 1000 and 9999. OMPC uses a default port number 8643

– Keystore Password—Enter a password that will be used to access the keystore file. The password must be

more than 5 characters, and cannot contain non-ANSI characters and double quotes (").

Press <Enter> when you have made all your changes. The Database Server screen appears.

10. The Database Server option allows you to install the Power Center database on a remote server. To use this option,

the system must meet the following requirements:

– The remote server must be running a v8.3.5 PostgreSQL database service. You can download this service

from http://www.postgresql.org.

– There is no Power Center database on the remote server.

– The database service on the remote server is able to accept remote database connections.

Select one of the database server options listed. The Database Setting screen appears.

11. Configure the PostgreSQL service by providing the following information:

– User Name—Enter your PostgreSQL database server user name.

– User Password—Enter your PostgreSQL database server user password.

– PostgreSQL Port—The default value is 6443. If another database is already using the default port, enter a

different port.

– PostgreSQL Data Directory—The location of PostgreSQL data.

Press <Enter> to continue.

NOTE: You must create a super user account in order to log into OpenManage Power Center following installation.

12. 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.

NOTE: The password must be a minimum of 8 characters in length, with characters from at least three of the following categories: uppercase, lowercase, numeric, and non-alphanumeric. The password can include spaces

13. Press <Enter> to initiate the installation.

14. Once the installation has completed, type q to quit the installation wizard.

Installed Directories In Linux

By default, the Power Center package installs to /opt/dell/ompc.

The Power Center package includes the following folders:

• bin — Power Center binaries

• conf — Power Center configuration files

• external — Other applications installed by Power Center

• logs — Power Center event logs

• pgdata (default) — Database files

Power Center Services In Linux

Power Center includes the following services on Linux platform installations:

• Dell OpenManage Power Center Database Services – The PostgreSQL internal database for Power Center.

• Dell OpenManage Power Center DataCenter Manager Service – The Power Center server core service. It carries out all actions including communication with devices.

• Dell OpenManage Power Center Authentication Service – Authenticates the local Linux user and group through a standard PAM interface.

• Dell OpenManage Power Center WebServer Service – The Apache Tomcat server that hosts the Power Center web application which passes action requests to the Power Center server.

Use the following command at the command line interface to check Power Center service status:

#service ompcdaemons status Control power center service

To start, stop, or restart Power Center service, use the following command:

#service ompcdaemons start|stop|restart|status

Uninstalling Power Center In Linux

To uninstall Power Center on a Linux server, type the following at the command line interface:

rpm –e OpenManage_PowerCenter

If you did not check the Use another database server option during installation, the uninstall program removes the Power Center database and configurations.

If you checked the Use another database server option and used another database during the installation, the uninstall program does not uninstall the database.

Launching Power Center In Linux

Open a Web browser. You may need to configure your Web browser to launch Power Center.

To launch Power Center, enter the following address in lower case in your Web browser: https://

<Server_Name>:<HTTPS_Port>/powercenter/

For example: https://localhost:8643/powercenter/

NOTE: Power Center only supports screen resolutions of 1024*768 pixels or higher. Make sure to correctly set the screen resolution on your system before launching the Power Center management console.

Select a user account and enter your name and password. The Power Center console appears. You can start to use the Power Center functions.

Command Line Interface

All of the 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.

NOTE: If a duplicate or incorrect option value is supplied with a command, the CLI will exit with an error. For example, when both the –profile and –protocol options are supplied at the same time in a command, the CLI will exit with an error.

GENERIC_OPTIONS is used to run a generic job for this command line.

In Windows

In Linux

, user authentication credentials are specified as follows:

• user_auth <POWER_CENTER|WINDOWS_LOCAL|WINDOWS_DOMAIN>

• user_name <user_name>: If user_type is WINDOWS_DOMAIN, then the user_name must be in domain \user format.

• user_password <password>

, user authentication credentials are specified as follows:

• user_auth <power_center|linux_local|ldap>

• user_name <user_name>

• user_password <password>

The COMMAND_TARGET specifies the targets on which the command will operate. For example, the COMMAND_TARGET for add_profile is a profile name to be added. For a specific command, the COMMAND_TARGET cannot have the same value with the name of a generic option or an option supported by this command. For example, the COMMAND_TARGET cannot be –protocol or –user_name for the command add_profile.

For COMMAND_TARGET, the order of its content must be kept as defined in the specific command definition section. Any valid option can be mixed with the content of COMMAND_TARGET. For example, the order of COMMAND_TARGET of the move_device command must be supplied FROM_GROUP_PATH first, then TO_GROUP_PATH.

Command Line Interface Error Handling

In Windows

displays. For more information, refer to Command Line Interface Error Codes.

In Linux

displays. Use stderr to get a more specific error code, and to find more information on that code, see Command Line

Interface Error Codes.

, when the command is successful, the CLI exit code is 0. If the command is not successful, an error code

, when a command is successful, the CLI exit code is 0. If a command is not successful, a generic error code, 1,

Command Line Interface Commands

NOTE: In the following commands, [ ] represents optional attributes and < > represents variables. All command line text is case insensitive.

help

Usage:

ompc_cli help [<COMMAND>] [<COMMAND_OPTION >]

The help command prints the help content for a command or a command option (including the generic option). Authentication is not required for the help command.

If no help command is specified (the ompc_cli command was issued with no parameters), generic help information about the ompc_cli tool displays. ompc_cli help also displays the generic help.

ompc_cli help help displays the help for the help command.

When only <COMMAND> is provided, the CLI prints the help for the specified command, including the command options that are available for the command. If you enter an invalid command, the CLI displays an error message.

When both <COMMAND> and <COMMAND_OPTION> are provided, the CLI prints the help for the command option specified for the given command. If the command option is not a valid option for given command, the CLI displays an error message.

If more than one command or command option is provided, the CLI displays an error message.

add_profile

Usage:

ompc_cli add_profile -protocol <protocol_name> [-description <description>] [<pair of protocol property and value options>] <profile_name>

The add_profile command adds a new discovery profile to OMPC. The profile_name argument is used to identify the profile, and must be a unique name. The protocol property and value depend on the protocol used to perform discovery.

The protocol_name should be <IPMI | SNMPv1v2c | SNMPv3 | WS-Man>

For IPMI, the properties are:

• bmc_user

• bmc_password

• bmc_key

For SNMPv1v2c, the property is snmp_community_string. (Required).

For SNMPv3, the properties are:

•

snmp_user (Required)

snmp_authentication_password

•

snmp_encryption_password

•

For WS-Man, the properties are:

wsman_port

•

wsman_user

•

• wsman_password

• wsman_validate_cert (its value must be true or false)

update_profile

Usage:

ompc_cli update_profile [-description <description>] [<pair of protocol property and value options>] <profile_name> [<new_profile_name>]

The update_profile command updates an existing discovery profile identified by profile_name in OMPC. The semantics of the command options are the same as those in add_profile. The protocol property set that can be updated depends on the protocol supported by this profile. If new_profile_name is provided, the profile_name is updated to the new_profile_name.

add_device

Usage:

ompc_cli add_device [-device_name <device_name>] [-description <description>] [size <size>] [-nameplate_power <nameplate_power>] [-derated_power <derated_power>] –device_type <SERVER | PDU | UPS | UNSUPPORTED|CHASSIS> [model <model>] [–profile <profile-name>] [-protocol <protocol_name>] [<pair of protocol property and value options>] [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 command option. You cannot enter –profile and –protocol at the same time.

The device_name is optional, and if not provided, OMPC will generate a device_name (following the same rule as in network discovery). For unsupported devices, the default auto-generated device_name is unique identifiers, OMPC appends numbers to the device name.

The [host_name or ip] option is required, except when the device_type is

The -model option is valid only when the type is

Unsupported

. To ensure

update_device

Usage:

ompc_cli update_device [-description <description>] [-size <size>] [nameplate_power <nameplate_power>] [-derated_power <derated_power>] [-host_name <host_name>] [-ip <ip>] [<pair of protocol property and value options>] <device_name > [<new_device_name>]

The update_device command updates device information identified by its device_name. If new_device_name is provided, the device_name will also be updated to the new_device_name. [<pair of protocol property and value options>] depends on the protocol supported by this device.

rediscover_device

Usage:

ompc_cli rediscover_device [-service_tag <stag>] [<device_name>]

The rediscover_device command lets OMPC connect with the device and refresh properties that might be changed on the device side (for example, power capability and device model).

After rediscovery, the Time of Discovery is updated to the time of rediscovery.

For the Chassis Management Controller (CMC), if you are rediscovering it before adding it to the rack (in other words, the blades inside it are not enumerated), it will not trigger enumerating blades inside it. If rediscovering a CMC after it is added to rack (the blades inside it are enumerated), OMPC will enumerate blade changes inside it to reflect any changes.

You cannot use -service_tag and device_name at the same time.

If the device is an unsupported device (device_type is rediscover for unsupported devices.”

Unsupported

), the CLI displays the error, “CLI does not allow

remove_profile

Usage:

ompc_cli remove_profile <profile-name>

The remove_profile command removes a discovery profile.

delete_device

Usage:

ompc_cli delete_device [-service_tag <stag>] [<device_name>]

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.

add_group

Usage:

ompc_cli add_group [-description <description>] -group_type <DC|ROOM|AISLE| RACK|CUSTOM > [-capacity <capacity>] [-total_power_capacity <power_capacity>] GROUP_PATH

The add_group command adds a new group identified by GROUP_PATH. If the type is RACK, you must supply the <capacity> option.

Forward slash (/) cannot be used as GROUP_PATH in the add_group command.

The chassis can be added to any group at any time. You can only add Chassis Management Console (CMC) to one rack; not multiple racks.

When you add CMC to any group, the blades inside it can be enumerated.

delete_group

Usage:

ompc_cli delete_group [-preview] GROUP_PATH

The delete_group command deletes a group identified by GROUP_PATH. All devices in this group will be removed from this group. The devices will still exist on the Devices page and in other groups that contain the devices.

All subgroups will be removed from this group. If a subgroup belongs to multiple parent groups, this subgroup will still exist in the other parent groups. If the subgroup no longer belongs to any parent group (after being removed from the current parent), this subgroup will be deleted from OMPC. This also applies to the group itself.

If the [-preview] option is given, a summary of the groups, devices, and policies impacted will display. No deletion occurs.

• 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 whether they will be deleted from OMPC or not. (It is possible that a subgroup could be removed from the specified group path, but not be deleted from OMPC due to a reference from another parent group.)

• All devices and subgroups are counted in the summary (not only the direct children of a specified group).

• Any policies that you added to the impacted devices are not counted in the summary, because the device will not be deleted from OMPC, and these policies will remain on these devices.

Example Summary:

– Number of impacted devices: 5

– Number of impacted subgroups: 10

– Number of impacted policies: 3

You can delete a chassis as a group with the delete_group command. In this case, after successful removal, the chassis will be kept on the containing this chassis (if there is no connection between the chassis and the blades inside it).

Devices page as a device, but will no longer appear as a group if there is no other group

update_group

Usage:

ompc_cli update_group [-description <description>] [-group_type <DC|ROOM|AISLE| CUSTOM >] [-capacity <capacity>] [-total_power_capacity <power_capacity>] GROUP_PATH [new_group_name]

The update_group command updates the properties of an existing group identified by GROUP_PATH. The –capacity and –total_power_capacity options are valid only when the group to be updated is a rack. The –group_type of a rack cannot be updated, and no other type of group can be updated to be a rack.

If new_group_name is provided, the CLI updates the name of the group to the new name. The group can belong to another group. If this is the case, the rename operation may fail because of the name confliction.

The chassis can be regarded as group, so the CLI allows updates to the properties of the chassis through the update_group command. You can only update the chassis’ description and name through the update_group command. You cannot update other types of groups to be a chassis.

The name must be unique across devices and groups under the same parent group.

You cannot use “/” as GROUP_PATH in the update_group command.

add_device_to_group

Usage:

ompc_cli add_device_to_group [-slot <slot_num>] [-service_tag <stag>] [<device_name >] GROUP_PATH

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 will be added. If the value of the slot is -1, the system will choose a slot automatically. When adding PDU/UPS, if you do not provide a slot option, the PDU/UPS will be attached to the rack. For

adding a server or chassis to rack, -slot is allowed (when not provided, the system will choose a slot automatically). If adding a server or chassis to other groups, -slot is not allowed (an error will display).

Slots start from 1 (0 is an invalid slot number).

PDU and UPS can only be added to a rack. For PDU and UPS in other types of groups in a previous OMPC release, if the you upgrade the data, you must remove PDU and UPS from those groups after upgrading.

The add_device_to_group command does not move a device from one group to another group. This is done by move_device.

If a device already belongs to a group, you can use the add_device_to_group command to add the device to another group. After successfully adding the device, this device belongs to both the old group and the new parent group. The exception is that devices can only belong to one rack (not multiple racks), and blades can only belong to one chassis (not multiple chassis). You cannot add blades to a chassis with the add_device_to_group command.

When a chassis is added to any group, the blades inside the chassis will be enumerated and the chassis becomes a group that contains all of the blades inside it.

remove_device_from_group

Usage:

ompc_cli remove_device_from_group [-service_tag <stag>] [<device_name >] GROUP_PATH

The remove_device_from_group command removes a device from a group identified by GROUP_PATH.

You can remove a chassis (as a device) from a group.

If a device belongs to multiple groups, after you remove it from one group, it will still belong to other groups.

A chassis can be removed through this command. In this case, the behavior is the same as removing a chassis by using the delete_group command.

move_device

Usage:

ompc_cli move_device [-service_tag <stag>] [<device_name >] [-slot <slot_num>] FROM_GROUP_PATH TO_GROUP_PATH

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

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.

When moving a PDU/UPS from one rack to another rack and the slot is not provided:

• If the PDU/UPS is in a slot of a previous rack, the CLI selects one slot in the new rack.

• If the PDU/UPS is attached in a previous rack, the CLI attaches it in the new rack.

When moving a PDU/UPS from one rack to another rack and you have specified the slot:

• If the PDU/UPS is in a slot of a previous rack, the CLI uses the specified slot in the new rack.

• If the PDU/UPS is attached in a previous rack, the CLI reports an error.

You cannot change the PDU/UPS properties between “slotted” and “attached” in Power Center. You can change between “slotted” and “attached” by removing the PDU/UPS from the rack, and re-adding it to the rack.

If the device to be moved is a chassis, the behavior will be the same as moving it through the move_group command.

FROM_GROUP_PATH; it belongs to TO_GROUP_PATH.

You cannot use the attributes -service_tag and device_name at the same time.

If the move operation fails, the device stays in the original group. There are exceptions for critical situations such as power failures, crashes, network failures for the remote database, and local network failures.

move_group

Usage:

ompc_cli move_group FROM_GROUP_PATH TO_GROUP_PATH

The move_group command moves a group from FROM_GROUP_PATH to TO_GROUP_PATH.

You cannot use the same group path as FROM_GROUP_PATH to TO_GROUP_PATH. Also, you cannot use “/” as FROM_GROUP_PATH.

After successfully moving a group, the group identified by FROM_GROUP_PATH will no longer belong to its original parent in FROM_GROUP_PATH. It will belong to TO_GROUP_PATH.

When moving a chassis to a rack, the CLI chooses one available slot (if a slot is available). If you want to specify a slot for the chassis in the new rack, you must use the move_device command.

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).

You cannot add groups to a rack (except for the chassis, which is a device before it is added to a rack, then a group after it is added to a rack).

When adding a chassis to a rack, the CLI will choose one available slot (if there is one available). If you want to specify a slot for the chassis in the rack, you must use the add_device_to_group command.

List commands

The following are generic rules for list commands:

• The output of list commands is a simple table-like structure, where a comma-delimited list of column names will be output first, followed by the data, in comma-delimited format. There is one line per record. If a piece of data is not applicable or available, that data is represented by two commas next to each other (NULL field).

• Line breaks (CRLF) in the output fields must be replaced with spaces.

• Fields containing double quotes and commas must be enclosed in double quotes.

• If a double quote appears inside a field, it must be escaped by preceding it with another double quote. For example: “aaa”, “b””bb”, “ccc”.

list_device_props

Usage:

ompc_cli list_device_props [-service_tag <servtag>] [<device_name>]

The list_device_props command lists all properties for the device identified by servtag or device_name. Properties include service_tag, protocol, protocol properties, device name, address (IP or host name), model, and device type (device name is the first column).

Secret data (password/key) is not listed as a protocol property.

list_devices

Usage:

ompc_cli list_devices [GROUP_PATH]

The list_devices command lists all devices immediately under the GROUP_PATH. If no GROUP_PATH is supplied, then the CLI will list all devices, connected or not, that are managed by OMPC. Properties include all properties of the list_device_props command, except for protocol information (device name will be the first column).

If “/” is provided as GROUP_PATH, the CLI will list 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 “/”.

list_groups

Usage:

ompc_cli list_groups [-unique] [GROUP_PATH]

The list_groups command lists all child groups for the GROUP_PATH (immediate only). If no GROUP_PATH is supplied, the CLI lists all group paths or all unique groups in OMPC. Properties include the fully-qualified group name, group type, and member_count. The member_count property is the number of devices and groups immediately under the child group.

[-unique] has no impact if GROUP_PATH is provided.

If “/” is provided as GROUP_PATH, then the CLI lists the groups at root level.

A group might have multiple fully-qualified group names. When [-unique] is provided, the CLI lists all unique groups; otherwise, the CLI will list all group paths.

Example output for list_groups:

group_name, group_type, member_count

myservers/mygroup, Room, 20

find_device

Usage:

ompc_cli find_device [-service_tag <stag>] <device_name>

The find_device command is used to list all of the fully-qualified group names of the groups to which the device that is identified by servtag or device_name belongs.

You cannot use service_tag and device_name at the same time.

Command Line Interface Error Codes

An error code appears when one of the following two conditions occurs:

• The CLI identified an error, such as a command or command option validation error. The error code is generated by the CLI. The module number for the CLI is 0xEE. An error number for each command and option will display.

• An OMPC back-end error occurs. In this situation, the error code from the server will be returned by the CLI.

The error codes use the following format:

8E|Module|Related Module (Optional)|Detail (Optional)

OMPC modules and error codes:

• OMPC Database — 0x01

• DCM SDK — 0x02

• OMPC UI asset — 0x03

• DC Modeling — 0x04

• Overview — 0x05

• Monitoring — 0x06

• User Accounts — 0x07

• 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

Access Control

This chapter provides information about access control in Power Center, including:

• Log in/Log out — You can log into Power Center by entering a user account, or by Kerberos Single Sign-On (SSO).

• User/Role/Privilege Management — After logging in, you can manage user accounts in the management console. Power Center provides role-based access control. You must set up roles first, and then define the privileges for each role. Then, you can set up Power Center accounts and assign them to different roles.

• Licensing — Power Center requires a valid license. You must import a license before the trial license expires.

About Authentication

Power Center supports both Power Center users and Windows users.

For cross-domain authentication, domains must be two-way transitively trusted by the domain in which the Power Center server is installed. For domains that are one-way trusted or not trusted by the domain in which the Power Center server is installed, authentication of user accounts in these domains is not supported and may fail.

Logging In

Power Center supports both Power Center-managed users and authenticated Windows and Linux users.

NOTE: When logging into Power Center for the first time, you must use the Power Center user account created during installation

For both Windows and Linux installations

• Power Center Account — For the first-time login, you must use the Power Center user account created during the installation

For Windows installations only

• Local Windows Account — Windows local account on the Power Center server

• Domain Account — Windows domain account

NOTE: You cannot log into Power Center using SSO on the Power Center server. You only can log into Power Center using SSO remotely.

NOTE: You must add the SSO user account to Power Center before you can log in using SSO. You will skip the login page and enter the Getting Started page directly using SSO.

• Kerberos Single Sign-On (SSO) — This feature enables you to log in without entering a user name and password, if you have already logged into the Windows domain. The only SSO method Power Center supports is Kerberos SSO. For more information on SSO, see Log in with Single Sign-on (SSO).

. Power Center tries Kerberos SSO first. If it fails, the Power Center login form appears, and you can use the user account information to log into Power Center.

For Linux installations only

NOTE: Power Center requires that SSL is enabled at the LDAP server, otherwise authentication attempts will fail.

• Local Linux Account — Linux local account on the Power Center server

NOTE: The LDAP Account type is only available when LDAP authentication has been enabled in

LDAPSettings.

• LDAP Account

Logging in with User Name and Password

To log into Power Center with a user name and password, use one of the following accounts:

• Power Center Account — You can create this account in Power Center. For the first-time login, you must use the Power Center user account created during the installation.

NOTE: Before logging into Power Center using either the Windows domain or the Windows local account, you must add the account into Power Center by accessing the User Accounts page. For further information, see Adding A User Account.

• Domain Account — Windows domain account.

• Windows Local Account — Windows local account on the Power Center server.

• Linux Local Account — Linux local account on the Power Center server.

NOTE: LDAP authentication must be enabled in LDAP Settings.

• LDAP Account

For more information on how to open the Power Center management console, see Launching Power Center.

Logging In With An OpenManage Power Center Account

1. Enter the User Name and Password of the OpenManage Power Control account.

2. Select OMPC Account (default) from the Login using drop-down list.

3. Click Login.

Logging In With A Windows Domain Account

1. Enter the User Name and Password of the Windows domain account.

2. Select Windows Domain Account from the Login using drop-down list.

3. Enter the Domain name for the Windows domain account.

4. Click Login.

Logging In With A Windows Local Account

1. Enter the User Name and Password of the Windows local account.

2. Select Windows Local Account from the Login using drop-down list.

3. Click Login.

Logging In With A Linux Local Account

1. Enter the User Name and Password of the Linux local account.

2. Select Linux Local Account from the Login using drop-down list.

3. Click Login.

Logging In With An LDAP Account

NOTE: The LDAP Account type is only available when LDAP authentication has been enabled in LDAPSettings.

1. Enter the User Name and Password of the LDAP account.

2. Select LDAP Account from the Login using drop-down list.

3. Click Login.

Log in with Single Sign-on (SSO)

SSO uses centralized authentication servers that other applications and systems utilize for authentication purposes, and combines this with techniques to ensure that users do not actively have to enter their credentials more than once. Kerberos SSO requires specific setting for Web browser. You must configure your Web browser to support SSO. For more information on how to configure this, see your Web browser Help. For a list of supported Web browsers, see

System Requirements.

The following is an example of configuration steps in Microsoft Internet Explorer 8:

1. Go to Internet Exploer 8 → Internet Options → Security → Local Intranet, then click Sites. The Local Intranet

window opens.

2. Click Advanced, add your Power Center site (for example, server1.dcm.dell.com) to the Local Intranet.

NOTE: Kerberos SSO may not work if Power Center services are launched by an account other than Network Service.

Single Domain Environment

You can set up a single domain environment with the following components:

• Domain Controller – AD server that supports the domain (parent and child)

• Power Center Server – Server with Power Center installed

• Power Center Client — Client server that connects to the Power Center server

Figure 2. Single Domain Environment Diagram

To set up the Kerberos SSO single domain environment, install Power Center and configure the Web browser.

Installing Power Center for Logging on with SSO

When installing Power Center:

1. Set up a Realm Name. You must enter a Fully Qualified Domain Name (FQDN) of the Realm—for example, dcm.dell.com.

2. Set up Microsoft Active Directory (AD) domain controller addresses—for example, 192.168.0.250. Separate multiple addresses with a comma.

3. Specify a domain user for dcm.dell.com as Power Center server’s domain account for Kerberos SSO—for example, "Tom" and Tom’s password. The user account you specify must be an existing and valid domain user account.

Configuring Web Browsers for Single Sign-On

To enable Kerberos Single Sign-on (SSO), you must configure your Web browser to support the feature. For more information, see your Web browser Help. For a list of supported Web browsers, see System Requirements.

NOTE: To correctly set up Kerberos SSO, the date and time on all involved computers must be consistent and DNS configuration must be correct.

To support SSO in Internet Explorer, you must add the Power Center server as a local Intranet site.

The following is an example of the configuration steps in Microsoft Internet Explorer 8:

1. Go to Internet Explorer 8 → Internet Options → Security → Local Intranet, and click Sites.

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

You 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 the child domains.

• Power Center Server — This is the server with Power Center installed. It is an AD domain controller.

• Power Center Client — The client server connects to the network of the Power Center server.

Figure 3. Multiple Domain Environment Diagram

To set up the Kerberos SSO multiple domain environment, install Power Center, set up SPN for Power Center service, and configure the Web browser.

Windows NT LAN Manager (NTLM) Authentication Limitation

Power Center supports Kerberos SSO for Windows domain user authentication. To enable this feature, Power Center is configured to support the Windows integrated authentication option which includes two authentication mechanisms: Kerberos and NTLM .

NTLM is not supported in Power Center. If the client’s Web browser uses NTLM to authenticate domain users for Power Center, there are some limitations.

What is the limitation?

The Web browser displays a message box requiring a Windows user name and password.

• If you click OK after entering a user name and password, whether the information is correct or not, the Power Center login page displays and requires you to authenticate through the login page.

• If you click Cancel, an HTTP Status 401 failure displays, and you cannot log into Power Center.

When does this occur?

This occurs when one of the following elements of Kerberos SSO is not correctly configured: Power Center server, Web browser. or the AD domain controller configuration.

How do you resolve this issue?

Correctly configure your Power Center server, AD controller, and Web Browser for Kerberos SSO. For more information, see your Web browser’s Help.

Multiple User Login

Power Center supports up to ten concurrent user login instances. When multiple users log into Power Center, if one user implements a change in Power Center (for example, deleting a device or moving a device), this may cause unexpected behavior for other logged in users. For example:

• If another user is viewing the management console, that user may see inconsistent data.

• If another user is performing operations on the same device, that user may receive an error message.

Logging out

To log out of Power Center with not logged in through Kerberos SSO, click Logout at the upper right corner of the management console.

When logged in through Kerberos SSO, you must close the Web browser or the Power Center management console to log out. Clicking Logout will not work.

Managing User Roles

Power Center supports three types of predefined roles. Each role has different privileges:

• Administrator – All privileges

• Power User – All privileges except

• Guest –

Only a user with the

View Device/Group

Manage Role/User

privileges only

privilege can add, edit, or delete a role in Power Center.

and

Manage License

Adding a Custom Role

1. Click Settings → User and Group Accounts in the left pane.

2. In the Account Roles section, click Add Role.

3. Enter a unique Role Name that is less than 50 characters.

4. Optionally, enter a Description that is less than 1024 characters.

5. Select the privileges to assign to the role.

6. Click Apply.

Editing A Role

1. Click Settings → User and Group Accounts in the left pane.

2. In the Account Roles section, click Edit.

3. Edit the role name, description, or privileges.

4. Click Apply to save your changes, or click Cancel to discard them.

privileges

NOTE: You cannot edit a pre-defined role.

Deleting A Role

1. Click Settings → User and Group Accounts in the left pane.

2. In the Account Roles section, click Delete.

3. Select the roles to delete.

4. Click Apply to save your changes, or click Cancel to discard them.

Managing User Accounts

You can create users and assign them to different roles.

If you have the

Adding A User Account

1. Click Settings → User and Group Accounts in the left pane.

2. In the User and Group Accounts section, click Add and select User.

The Add User window opens.

3. Select a User Type and enter the required credentials:

For a Windows installation:

Manage Role/User

NOTE: If OpenManage Power Center is installed on a Windows Active Domain Controller server, every user account added on this server should be a Windows Domain Account.

privilege, you can add/edit/delete a user in Power Center.

– OMPC Account—Create a unique User Name, then enter a password that is at least 8 characters long and

includes characters from at least three of the following categories: uppercase, lowercase, numeric, nonalphanumeric.

– Windows Local Account—Enter a valid User Name for the Windows account.

NOTE: If Power Center is installed on a Windows 2012 Essential server and the server is configured as a Domain controller, all user accounts on the server should be Windows Domain Accounts, not Windows Local Accounts.

– Windows Domain Account—Enter a valid User Name for the Windows domain account, then enter a valid

Windows Domain Name.

For a Linux installation:

– OMPC Account—Create a unique User Name, then enter a password that is at least 8 characters long and

includes characters from at least three of the following categories: uppercase, lowercase, numeric, nonalphanumeric.

– Linux Local Account—Enter a valid User Name for the Linux account.

NOTE: While Linux Local Accounts can be changed from the Linux server, these changes will not be mirrored in the same local account that was added to Power Center, and Power Center authentication attempts on this account will fail. To keep the Linux Local Account in sync between Power Center and the Linux server when the local account is changed from Linux, the original account must be deleted from Power Center and the changed account must be created in Power Center as a new Linux Local Account.

– LDAP Account—Enter a valid User Name for the LDAP account.

4. Select between one and four User and Group Roles.

NOTE: A user description is useful when there are two users with the same user name. Two user accounts with the same user name are only possible where the user types differ.

5. Optionally, enter a user Description.

6. Click Apply to add the user account, or click Cancel to discard your changes.

Adding A Group Account

1. Click Settings → User and Group Accounts in the left pane.

2. In the User and Group Accounts section, click Add and select Group.

The Add Group window opens.

3. Select a Group Type and enter the required credentials:

For a Windows installation:

– Windows Local Group—Enter a valid Group Name for the Windows account.

– Windows Domain Group—Enter a valid Group Name for the Windows domain account, then enter a valid

Windows Domain Name.

For a Linux installation:

– Enter a Group Name.

4. Select between one and four User and Group Roles.

5. Optionally, enter a group description.

6. Click Apply to add the new group, or click cancel to discard your changes.

Editing A User Or Group Account

1. Click Settings → User and Group Accounts in the left pane.

2. In the User and Group Accounts section, click Edit and then make the desired changes. Use the sliding scroll bar to scroll across and view all fields.

3. Click Apply to save your changes, or click Cancel to discard them.

Deleting a User or Group Account

NOTE: You cannot delete the Power Center managed user (super user) that was created during installation.

1. Click Settings → User and Group Accounts in the left pane.

2. In the User and Group Accounts section, click Delete.

3. Select the user or group account to delete.

4. Click Apply to delete the selected accounts, or click Cancel to discard your changes.

Changing A User Account Password

1. Click Settings.

2. Do one of the following:

– Click User and Group Accounts → Edit, then click Update Password beside the User Account you want to

update.

– Click Current User → Update Password.

The Update Password window opens.

3. Enter a Password that is at least 8 characters long and includes characters from at least three of the following

categories: uppercase, lowercase, numeric, non-alphanumeric. Confirm the password.

4. Click Apply to save your new password, or click Cancel to discard your changes.

Roles and Privileges

Power Center supports three pre-defined roles:

• Administrator: All privileges

• Power User: All privileges except

• Guest:

Additionally, you can create custom roles with one or more of the following privileges:

• Global configuration

• Device discovery

• Manage role/user

• View device/group

• Manage device/group

• Manage policy

• Manage event

• Manage license

View device/group

Manage role/user

privileges only

and

Manage license

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

sampling interval and database settings. Users without this privilege can only view part of the Settings page, and cannot make any changes (the Edit option is not available).

privilege enables a user to change the Power Center global configuration—for example, the

Manage Role/User

Users with the

• Create roles

• Delete roles

• Update roles

• Create users

• Delete users

• Update users

Manage Role/User

privilege can:

Users without this privilege can only view their own user account information and update the password; the User Roles and User Accounts sections do not display on the User Accounts page.

View Device/Group

The

View Device/Group

cannot view device or group information; they can only view the Settings page.

Users with only the

• The Discovery page is not available.

• The pages under Devices and Groups do not enable Add/Delete/Edit functionality.

privilege enables a user to view all device and group information. Users without this privilege

View Device/Group

privilege have the following restrictions:

Manage Device/Group

The

Manage Device/Group

• Create groups

• Create a Data Center/Room/Aisle/Rack/Device

• Associate Data Center/Room/Aisle/Rack/Device/Group

• Manage a device

• Remove a device/group from the Device List

privilege enables a user to:

NOTE: When you assign the

View Device/Group

Users without this privilege can view all devices and group information, but cannot add/delete/edit/manage the devices and groups.

privilege to this user as well.

Manage Device/Group

privilege to a user, Power Center automatically assigns the

Manage Policy

The

Manage Policy

• Add/remove a policy

• Update a policy

• Start/stop Emergency Power Reduction on a device or group

NOTE: To manage a policy, you must also have the

Users without this privilege cannot see the Policies tab on the Groups page.

privilege enables a user to:

View Device/Group

privilege.

Manage Event

The

Manage Event

• Add/Remove an event condition (threshold)

• Update an event condition (threshold)

• Remove an event

privilege enables a user to:

NOTE: To manage an event, you must also have the

Users without this privilege can view event information and add comments to events, but cannot delete events or see the Thresholds tab in the Groups page.

View Device/Group

privilege.

Viewing Current User Information

You can view current user information and update the current user’s password.

To view current user information, click the login user name in the upper-right corner of any page, or go to Settings → User Accounts → Current User .

To update the user password:

1. Click Update Password.

2. Enter the current password and new password. Enter the new password again to confirm.

3. Click Apply.

Licensing

Power Center requires a valid license. Power Center automatically installs a 60-day trial license during the installation. You must import a perpetual license before the trial license expires. Only users with the Manage License privilege can import the license.

You can view license information in the Licensing page. Power Center license information includes:

• Product Name — Product name

• Version — Product version

• License Type — Trial (60 days) or Perpetual

• Expiration — For Trial license only. Displays the license expiration date in the format: YYYY-MM-DD, Days Left: xx.

• Status — Valid or Expired

From the Licensing page you can:

• Import a license

NOTE: The Getting Started page displays a warning message when the license expires in less than 30 days.

You can get the Power Center license at: http://www.dell.com/powercenter.

Importing a License

You must purchase, download, and import a license to continue using the product after the 60 day trial period.

1. Click Settings → Licensing in the left pane.

2. Click Import License.

3. In the Import License window, click Continue.

a) If you have not downloaded your license, click Click here to download your license file.

Your web browser opens the Dell OpenManage Power Center website. b) Click Click here to download. c) Download and unzip the OpenManage Power Center License.zip file onto your network.

d) Return to the Import License window.

4. Click Upload File.

5. Browse to a license file, and click Open.

Power Center imports the license and displays a message upon successful import. You can view the license information in the Licensing page.

Device Discovery

The

Device Discovery

Settings page, but cannot make any changes.

New Device Discovery

To manage devices in Power Center, you must first add the devices to the Power Center management console. You must have

Manage Device/Group

Power Center device discovery includes both the automatic detection of all devices on your data center and the collection of basic information about each device, such as:

• Device name

• Connection status

• Device type

• Device model

• IP address

• Hostname

• Communication protocol

privilege enables a user to discover network devices. Users without this privilege can view the

and

Discover Device

privileges to add a device to Power Center.

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:

• Discover a device from the network — Discovered devices will be automatically added to the Device List.

• Manually add a device — Use the Power Center management console to specify device properties and add a device to the Device List.

NOTE: If you use a network security policy, the discovery function may not work properly.

Supported and Unsupported Devices

You can add or discover supported devices, and create a group structure to build out the data center. Power Center cannot discover or manage all device types, and unsupported devices must be manually added to make the data center group structure complete.

For supported devices:

• Device types include chassis, server, UPS, and PDU.

• Set the connection protocol and credential information so that the device can communicate with Power Center.

• Add or discover a supported device to the device list in the Devices page. Perform management functions including discovery, adding to the group structure, monitoring power and temperature, applying power management policies, and sending events.

Power Center supports up to 4000 managed devices in one data center.

Table 3. Supported Devices

Category Supported Platform Validated Model

Server Dell

• Dell PowerEdge R610 Rack Server

• Dell PowerEdge R620 Rack Server

• Dell PowerEdge R710 Rack Server

• Dell PowerEdge R720 Rack Server

• Dell PowerEdge R820 Rack Server

• Dell PowerEdge M610 Blade Server

• Dell PowerEdge M620 Blade Server

• Dell PowerEdge T620 Tower Server

Chassis Dell

PDU Dell

APC

Eaton

Emerson

ServerTech

• Dell PowerEdge M1000e Blade Enclosure

• Dell 6804 Metered PDU

• Dell 6607 Metered PDU

• Dell XX5T6 Metered PDU

• Dell 6803 Metered PDU

• Dell 6605 PDU

• APC Metered Rack PDU AP78001

• APC Switched Rack PDU AP7900

• APC Switched Rack PDU AP7920

• Eaton Monitored PDU PW312MI0UC07

• Eaton Switched PDU PW105SW0U154

• Emerson Liebert MPH MPHNCR09NXXE30

• ServerTech Switched PDU CW-24V4J411

• ServerTech Smart CDU, 0U CS-24V1-C20M

Category Supported Platform Validated Model

UPS Dell

• Dell N313P Line interactive UPS w/ web card H910P

• Dell Online Rack UPS 3750R OL K804N

• Dell UPS, 2700/2300VA, 120V, 3U K802N

APC

Eaton

Emerson

For unsupported devices:

• Power Center does not communicate with unsupported devices; therefore, connection protocol and credential information is not necessary.

• Unsupported devices cannot be discovered, only added manually to the device list on the Devices page.

• Power Center adds the unsupported device to the group structure, but cannot manage it using the available management functions.

You may need to enter the following power values when adding supported or unsupported devices:

• Faceplate Power: The maximum amount of power that a group/device can draw; this value should be listed on the power supply specifications. The faceplate power rating is typically much higher than the actual power used by the device.

• De-rated Power: The default maximum power value; if a power measurement cannot be completed, this value is used.

• APC Online UPS w/ Web card SURTD3000XLI

• APC Smart-UPS 3000VA RM SUA3000RM2U

• Smart-UPS 5000VA RM DL5000RMT5U

• Eaton Line interactive UPS w/ Web card PW5130I1750-XL2U

• Emerson Online UPS w/ Web card GXT2-2700RT208

NOTE: Faceplate power value is always greater than the de-rated power value.

Adding a Device from the Network

You can use the Power Center management console to discover a device from the network.

Before adding a device from the network, make sure the DNS server is set up correctly. Specifically, make sure that:

• There is a DNS server running on the Power Center network.

• The specified DNS server has a reverse DNS zone for the network on which you are trying to discover the devices.

NOTE: Power Center server tries to get device names from the DNS server specified in the network configuration of the operating system. This may cause the device name to be different from the actual one if the DNS server resolves the device IP address to a different device name.

To discover devices from the network, Enter IP Range, Select the protocol, view the summary, and search devices.

Enter IP Range

1. Go to the Discovery page.

2. Enter an IP address range, or select one from the list. If the correct range is not displayed, add it.

3. Click Apply.

The new IP range is added to the list of IP ranges that displays at the top of the page.

4. Select at least one IP range and click Next.

NOTE: The IP Ranges section lists not only the IP ranges that you have added, but also the IP ranges of the three most recent discovery tasks.

Adding an IP Range

1. Click Discovery in the left pane.

2. Click Add IP Range.

3. Enter a Beginning IP address, an End IP address, and a Network Mask.

4. Click Apply.

Select a Protocol, View Summary, and Search Devices

You can either create a new protocol profile or use an existing one.

To create a new protocol profile:

1. Click Add Protocol.

2. Enter the following information:

– Profile Name – Enter a unique name that will be used to identify the profile. Must be less than 16

characters.

– Description – Enter a description for the profile.

– Protocol – Select the protocol used for communicating with devices through the network. You must enter

credential information for the selected protocol. For more information, see Protocol Profile.

3. Click Apply.

The new protocol profile is added and displayed at the top of the page. You can click + next to a profile to see its details.

4. Select the connection protocol(s).

5. Click Next.

The Summary information displays.

6. Review the information and click Search.

7. After the search progress completes, go to the Devices page to validate that the correct devices are listed on the page.

Adding a Device Manually

To add a device manually in the Power Center management console:

1. Go to the Device List page, and click Add.

2. Enter the device and protocol information (Required Device Information, Protocol Information, Optional Device Information) for the device you want to add.

– Required Device Information:

* Device Name: Enter the name of the device.

* Device Type: Select a device type of Server, UPS, PDU, Chassis, or Unsupported.

* IP Address or Hostname: Enter either a valid IP address or a hostname. Power Center will validate

the field. This is optional for Unsupported devices.

– Protocol Information: This is not required for Unsupported devices. For more information on credential

information for the protocols, see Protocol Profile.

* Protocol: The corresponding protocol type displays after you select the device type. If you selected

a UPS or a PDU in the previous step, you must select a protocol.

* Credential Information: Enter the protocol credential information.

– Optional Device Information:

* Device Model: Enter the device model. This field is available when you add an unsupported device.

* Size of Device: Select the device height (1-10 rack unit).

* Description: Enter a description for the device.

* Faceplate Power: Enter the faceplate power value.

* De-rated Power: Enter the de-rated power value.

3. Click Apply.

Rediscovering Devices in a Chassis

If you have physically added, removed, or changed the devices in a chassis, you can update the device information in Power Center.

1. Click Groups in the left pane.

2. Select the enclosure, and then click the Chassis tab in the bottom pane.

3. Click Rediscover Chassis Devices.

Protocol Profile

Power Center server uses a protocol profile to communicate with devices. The protocol profile specifies a device’s connection protocol and credential information. You will select a protocol profile when you discover a new device.

You can set up multiple protocol profiles for each protocol. Additionally, you can add a new profile, edit an existing profile, or delete a profile.

Power Center supports the following connection protocol types, and includes several optional settings:

NOTE: Get the correct protocol type and credential information from your system administrator. The user name and password for the IPMI/WS-MAN protocol must be the same as those used for the iDRAC/CMC Web console.

• IPMI: Select IPMI protocol for the server.

– IPMI User Name – Maximum length is 16 characters.

– IPMI Password – Maximum length is 255 characters.

– IPMI Key – A string of 40 hex digits.

• WS-MAN: Select WS-MAN protocol for the chassis.

– WS-MAN User Name – HTTP basic user name; maximum length is 255 characters.

– WS-MAN Password – HTTP basic password; maximum length is 255 characters.

– WS-MAN Port – Default value is 443, or enter a port number from 1 to 65535.

– WS-MAN Validate Certificate – (Optional) Enables device certificate validation.

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)

located at http://www.delltechcenter.com/page/dcim.modular.cmc.winrm. For more information on how to import the certificate to Power Center, see Managing Certificates.

• SNMP v1v2c: Select an SNMP protocol version from SMMPv1 or SNMP v2/v2c for the PDU or UPS.

– SNMP Community string – (Required) Maximum length is 255 characters.

• SNMP v3: Select SNMP v3 for the PDU or UPS.

– SNMP User Name – (Required) Maximum length is 255 characters.

– SNMP Authentication Password – (Required) Maximum length is 16 characters.

– SNMP Encryption Password – Maximum length is 255 characters. When the SNMP Authentication

Password is empty, the SNMP Encryption Password is also empty.

Device Management

The Devices page lists network-discovered devices and devices that were added manually. From this page, you can:

• Add supported or unsupported devices to the Devices page

• Remove devices from the Devices page

• Edit device information for a single device or multiple devices

• Edit protocol information for a single device

• Filter and sort devices to meet current needs

Discovering Devices

You can discover devices from your data center’s network.

1. Click Discovery in the left pane.

2. Configure the search criteria for the devices you want to discover.

3. The discovered devices appear in the Devices page.

Viewing Devices

The Devices page lists the following device information:

Table 4. Fields on the Devices Page

Field Description

Name Device Name — Power Center resolves this name during

network discovery

Status Device status, including:

• Connected

• Lost connection

• Unknown

IP Address Device IP address

Hostname Device hostname

Serial Number or Service Tag Device serial number or service tag

• Service Tag: The service tags for Dell chassis and servers

• Serial Number: The serial numbers for Dell PDU and UPS devices

• NA: For all other devices, NA is displayed

Device Type Device type, including:

Field Description

• Server

• PDU

• UPS

• Chassis

• Unsupported

Device Model Device model—for example, PowerEdge M610

Protocol Protocol used for communication, including:

• IPMI

• SNMPv1v2c or SNMPv3

• WS-MAN

Power Capability Power monitoring and capping capability, or whether the

device can be upgraded, including:

• Unknown

• None

• Monitor

• Monitor & Capping

• Monitor and Upgradable

Group Device’s physical group.

Time of Discovery Time when the device was discovered

Description Device description

Size of Device Physical size of device in rack units (U)

Faceplate Power Device faceplate power

De-rated Power Device de-rated power

NOTE: If a device is already discovered and listed in the Devices page, when Power Center runs a discovery task and this device is discovered again, all the device information for this device is updated in the Devices page. For more information on device discovery, see Adding a Device from the Network.

Editing a Single Device

1. Click Devices in the left pane.

2. Click Edit → Edit.

NOTE: You must scroll to the right to see all of the fields.

3. Edit the desired fields. You can edit the Name, IP Address , Hostname, Description, Size of Device, Faceplate Power and Derated Power of the device.

NOTE: You cannot edit the Faceplate Power and Derated Power for a chassis.

Editing Multiple Devices

1. Click Devices in the left pane.

2. Click Edit → Batch Edit.

3. Select the checkboxes of the devices that you want to edit, and click Next.

The editable fields depend on the type of devices you select.

4. Enter the required information. You can edit the Faceplate Power, De-rated Power, Description, Size of Device, or

Protocol Information for the devices.

NOTE:

– If you selected devices with different protocol types, then you cannot edit the protocol information.

– If you edit the protocol information and leave the User Name field empty, the user name remains

unchanged.

– The Clear checkbox only appears next to applicable fields. If you select the Clear checkbox next to a

field, the current value of this field is cleared. If you do not select the Clear checkbox and leave this field empty, the value remains unchanged.

5. Click Apply.

Editing a Protocol

You can edit the protocol information for a single device.

1. Click Devices in the left pane.

2. Scroll to the right to view the Protocol column.

3. In the Protocol column, click the link of the device protocol that you want to edit.

4. The Edit Protocol Information window opens. Enter the required information and click Apply.

Review the following for additional information on using the User Name field and Clear checkbox:

– If the User Name field is left empty, the user name will be cleared.

– If you select the Clear checkbox next to a field, the current value of this field is cleared. If you do not select

the Clear checkbox and leave the field empty, the value remains unchanged.

5. Click Apply.

Removing Devices

You can delete a single device, or you can delete multiple devices at once.

1. Click Devices in the left pane.

2. Do one of the following:

To delete a single device, click Delete → Delete. Select the checkbox for the device you want to delete, and click Apply.

To delete all devices, click Delete → Delete All. Read the verification pop-up message, and click Yes to continue. Devices in the device list are deleted. If the current device list is a filtered device list, only the filtered devices are deleted.

Device List: Filter

This Filter window filters devices. This is useful when you want to view specific devices, for example, you can view devices of a certain device type.

1. Click Devices in the left pane.

2. Click Filter.

The Filter window opens.

3. Do one of the following:

– Click IP Range, and enter the start and end IP address of devices.

– Click Date Range, and enter the start and end date of device discovery. Enter the dates manually following

the format YYYY-MM-DD, or select the dates from the calendar. Devices discovered from 00:00:00 of start date to 00:00:00 of the next day after the end date are displayed. For example, if you enter the filtering option 2011-01-01 as both start date and end date, all devices discovered between 00:00:00 of 2011-01-01 and 00:00:00 of 2011-01-02 are displayed.

– Click Protocol, and select the protocols used for communication. You can select multiple protocols.

– Click Status, and select device statuses. You can select multiple statuses.

– Click Device Type/Model, and select the device type or device model. the device model is the specific

model information of a device type, for example, PowerEdge M610. All the models that currently exist in the Devices page are shown. If you selected both Device Type and Device Model, make sure the device type matches the device model, otherwise no result is shown.

– Click Physical Group, and select a physical group where the device is located. You can select any level of

the physical group, including data center, room, aisle, rack and chassis.

– Click Faceplate/Derated Power, and enter a faceplate or de-rated power range of devices.

– Click Power Capability, and select the power capability of the device. You can select multiple power

capabilities.

4. Click Apply.

The Devices page displays the filtered devices.

Sorting Devices

By default, on the Devices page, the devices are listed by Name in alphabetical order (A-Z). To sort the list, click the Up or Down symbol next to the field to list the devices in ascending or descending order. The symbol of the current sorting field is displayed in orange.

Group Management

Power Center enables you to create groups for organizing devices, so that you can manage them more efficiently.

Mapping Group Structure Information

Power Center supports group structure mapping for Dell PowerEdge rack servers and tower servers. For more information on the specific models, see Supported Devices.

After you create or update the group structure, Power Center automatically updates the location information in the firmware of supported devices using the following mapping structure:

• Data Center — Data center and room information in Power Center; format: <Data Center - Room>

• Aisle — Aisle information in Power Center

• Rack — Rack information in Power Center

• Rack Slot — Rack slot information in Power Center

• Chassis — Chassis information in Power Center (if applicable)

NOTE: To view updated location information on supported device, you must make sure the device status has a

Connected

Finding a Group or Device

status in Power Center. It may take a few minutes for location information to update in device firmware.

After the data center group structure is set up, you can find a group or device on the Groups page.

On the Groups page, you can:

• Find a group or device (excludes Unsupported devices).

• View event status. If there are critical or warning events on a group or device, an event icon displays next to the group/device icon. If critical and warning events both exist, only the critical event icon displays.

• View the power details of the group/device.

• Click the Manage Group link to manage the selected group/device.

Groups

On the Groups screen, you can organize devices into groups.

From this screen, you can:

• Add a new group

• Add a new custom group

• Add an existing group as the child of a parent group

• Add an existing device as the child of a parent group

• Edit a group

• Delete a group

• Move a group or device

• Manage the group membership

• View power, temperature, and events, and manage thresholds and power policies for devices and groups

Adding a New Group

For information about adding an existing group, refer to Adding an Existing Group. For information about adding an existing device, refer to Adding an Existing Device.

A group can represent the actual structure of a data center, room, aisle, or rack. You can nest groups in parent-child relationships to represent how the devices in your data center are physically configured.

You can add a new group to an existing group.

1. Click Groups in the left pane.

2. To select where in the parent-child hierarchy to add the group, do one of the following:

– To add the group at the root level, make sure no groups are selected.

– To add a group as a child, click the parent group under which the new group should be nested.

3. Click Add.

4. Select Add a New Group.

5. Select a Group Type of

NOTE: Select

6. Enter the Number to Add; for example, you might want to create one data center or five racks.

7. Enter a Name that you will use to identify the group for future use.

NOTE: The name must be unique across groups and devices under the parent group.

8. Enter a Description of what the group contains.

9. For racks only: a) Select the rack Capacity (number of rack units).

b) Enter the Total Power Capacity that is determined by the power distribution to the rack.

Data Center, Room, Aisle

Custom

only to create a logical group. Refer to Adding a Custom group.

, or

Rack

10. Click Apply.

Adding a Custom Group

A custom group represents an association of similar devices. For example, you might create a custom group of email or print/file servers.

1. Click Groups in the left pane.

2. To select where in the parent-child hierarchy to add the group, do one of the following:

– To add the group at the highest parent level, make sure no groups are selected.

– To add a group as a child, click the parent group under which the new group should be nested.

3. Click Add.

4. Select Add a New Group.

5. Select a Group Type of

6. Enter the Number to Add; for example, you might want to create one data center or five racks.

7. Enter a Name the you will use to identify the group for future use.

8. Enter a Description of what the group contains.

9. Click Apply.

Custom

Adding Existing Group(s) as the Child of a Parent Group

1. Click Groups in the left pane.

2. In the column structure, click the parent group to which the child group will be added.

3. Click Add.

4. Select Add an Existing Group.

5. Select the child group(s) to add beneath the parent group.

6. Click Apply.

Adding Existing Device(s) as the Child of a Parent Group

After a device is discovered or manually added to Power Center, you can add it to a group.

NOTE: Racks are special groups. To add a device to a rack, select the rack, click Manage, and select the slot to which you want to add the device. Click Add to Rack Slot, then click Apply.

To add multiple devices to the selected rack, click Batch Add, then click Apply.

To add devices to a parent group, perform the following steps:

1. Click Groups in the left pane.

2. Click the parent group to which you want to add the device.

3. Click Add.

4. Select Add an Existing Device.

5. Select one or more devices to add to the group.

6. Click Apply.

Moving Groups or Devices

You can move groups of devices from one rack to another. You can also move a group of devices from one slot to another slot in a rack.

1. Click Groups in the left pane.

2. Click on the device or group that you want to move.

3. Click Move.

4. Select the destination group in the Move Device window.

5. Click Move.

NOTE: Any power policies in effect will be recalculated after moving the group.

Deleting a Group or Deleting a Device from a Group

1. Click Groups in the left pane.

2. Click the group (or device) that you want to delete from the hierarchy.

3. Click Delete.

4. Click Delete again to confirm the deletion.

Editing a Group

1. Click Groups in the left pane.

2. Select the group you want to edit.

3. Click Edit.

4. Edit the Group Type, Name, and/or Description.

5. Click Apply.

Managing a Group

1. Click Groups in the left pane.

2. Click the group that you want to manage. If you want to manage a specific group, select the group. If you want to manage a subgroup (or a child of a group) then select the parent group, and navigate to the subgroup or child group.

3. Click Manage.

NOTE: To manage the devices associated with a data center, click the Associated Devices tab. You can add, edit, remove, or move groups. Click X to close the window.

4. Click Add, Edit, Delete, or Move.

5. Enter the requested information and click Apply.

Viewing Group or Device Details

On the Groups screen, you can view the overview, event, power, temperature, threshold, and policy details associated with a group or device.

• Overview

– Current power being used. You can set the unit (Watts or BTU/hr) in Settings.

– Current temperature. You can set the unit (Celsius or Fahrenheit) in Settings.

– PDU Dashboard that displays the name, time, power, current, and voltage associated with all PDUs in

the selected group

– Top 10 critical events including severity, entity, event type, description, time stamp, and comments

• Events—Critical and warning events currently associated with the group or device

• Power

– Graph of temperature for the past 15 minutes (15 Mn), hour (1 H), day (1 D), week (1 W), month (1 M), 3

months (3 M), or one year (1 Y)

– Energy consumption for the selected time period for IT equipment and cooling

• Temperature

– Graph of power usage in BTU/hr for the past 15 minutes (15 Mn), hour (1 H), day (1 D), week (1 W), month

(1 M), 3 months (3 M), or one year (1 Y)

• Thresholds

– Click Edit to enter Power Thresholds or Temperature Thresholds

• Policies

– Create a new power policy

– Enable or disable a power policy

– Delete a power policy

– Apply an emergency power reduction

Creating a New Power Policy

You can create static power policies for a rack, chassis or device, and create dynamic power policies for any group/ device. Power policies only apply to the groups/devices that have Monitor & Capping power capability.

1. Click Groups in the left pane.

2. Click the entity (data center, room, aisle, rack, or chassis) to which the policy will apply.

3. Click the POLICIES tab near the bottom of the screen.

4. Click Create New Policy.

5. In the Create New Policy window: a) Enter a policy name that is less than 25 characters.

b) For racks and chassis only, select a Policy Type of c) Select a fixed time period to display Average Power and Maximum Power values that can be used to estimate a

Power Cap Value. The Average Power, Maximum Power, Lower Bound and Upper Bound values only refer to the devices that have monitoring and capping power capability.

d) Enter either a Power Cap Value or Percentage of Capability to set the total power consumption budget for

devices with monitoring and capping power capabilities:

* Power Cap Value—Enter a value between the Lower Bound and Upper Bound. The

lowest minimum power consumption since the device/group was discovered or added to Power Center. The

Upper Bound

workload state.

* Percentage of Capability— Enter a percentage between 1-100%. The following formula will calculate

the total power consumption budget:

is the maximum power consumption when the device/group is in a maximum

Static

Upper Bound

Dynamic

Percentage of Capability

Lower Bound

Power Cap Value

is the

e) Click Next. f) Allocate power for the group/device:

* Dynamic policy—Set the priority (High, Medium, and Low) for individual devices in the group. Power

Center reserves more of the budgeted power for the devices/groups with a higher priority when the power budget is not completely utilized.

* Static policy—Enter values for the Power Cap or Percentage of Capability, if desired. By default, Power

Center uses the same percentage of the Upper Bound value as the power cap for every device. If the sum of the values is higher than the power cap value set in the previous step, Power Center will change

the Power Cap Value and display a message. g) Click Next. h) Select a policy schedule when the group/devices will be monitored:

* Time Span—Always or a range (start and end times in the format HH:MM using 24-hour time)

* Recurrence Pattern—Always or specific days of the week

* Recurrence Range—Always or a range (start and end dates)

i) Review the policy summary information, and click Apply.

The new policy takes effect immediately.

Enabling or Disabling a Power Policy

1. Do one of the following:

– Click Policies in the left pane.

– Click Groups in the left pane, and then click the POWER POLICIES tab.

2. Click Enable/Disable.

3. Select a policy to enable, or deselect to disable.

4. Click Apply.

Deleting a Power Policy

1. Do one of the following:

– Click Policies in the left pane.

– Click Groups in the left pane, and then click the POWER POLICIES tab.

2. Click Delete.

3. Select one or more policies to delete.

4. Click Apply.

Applying an Emergency Power Reduction

Applying an Emergency Power Reduction reduces device power to an extremely low level to lower power consumption and reduce heat output. This feature has a negative impact on device performance, and should be used only when needed—for example, when a data center faces a brownout (a temporary reduction of electric service in which power is reduced but not shut off).

1. Click Groups in the left pane.

2. Click the entity (data center, room, aisle, rack, or chassis) to which the Emergency Power Reduction will apply.

3. Click the Policies tab near the bottom of the screen.

4. Click Emergency Power Reduction.

5. Click Continue.

Stopping an Emergency Power Reduction

1. At the top of the screen, click the red EMERGENCY POWER REDUCTION icon.

2. Select the groups and/or devices on which the power reduction should stop.

3. Click Apply.

Power Monitoring

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.

Power Monitoring Levels

Power Center provides power monitoring at the following levels for groups:

• Individual device

• Rack

• Aisle

• Room

• Data center

Power Monitoring Configuration

You can configure power monitoring settings in Power Center, including

• Thresholds (average and maximum power for events)

• Device and group range (monitor all or none)

• Default units (watts or BTU per hour)

• Energy consumptions (power consumption and cost)

Power Thresholds

It is useful to monitor thresholds when you want to be notified when the power of a group and/or device exceeds the set limits.

1. Click Groups in the left pane.

2. Select the group or device for which you want to set the threshold.

3. Click the Thresholds tab.

4. Click Edit.

5. Enter the values for the following:

– Critical Threshold (BTU/hr) for Custom Max Power Group

When the maximum power exceeds this setting, the critical-level event “Max Power” is sent.

– Critical Threshold (BTU/hr) for Custom Average Power Group

When the average power exceeds this setting, the critical-level event “Average Power” is sent.

– Warning Threshold (BTU/hr) for Custom Max Power Group

When the maximum power exceeds this setting, the warning-level event “Max Power” is sent.

– Warning Threshold (BTU/hr) for Custom Average Power Group

When the average power exceeds this setting, the warning-level event “Average Power” is sent.

6. Click Apply.

After you configure the thresholds, you can view a graphical representation of the power details in the Power tab.

For more information on configuring the device/group range and sampling interval, see Monitoring Settings.

For more information on configuring default units and energy consumption, see Energy Consumption Settings.

Viewing Power Details

Click Groups in the left pane. Click the icon for the group or device, then open the Power tab.

The Power Details page displays information for PDU and other devices and groups. Power Center does not provide power details for UPS.

For devices and groups (excluding PDU and UPS), by default, the Power Details graph displays the power details for the previous hour.

You can also view the following details:

Power Details for the Current Time Window

You can view power details for the current time window by clicking a time window tab. The following table describes the time windows and their associated intervals:

Table 5. Time Windows and Intervals

Time Window Description Interval

15Min 15 minutes 1 minute

1H 1 hour 3 minutes

1D 1 day 1 hour

1W 1 week 6 hours

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. If you change the sampling interval to 6 minutes, the interval of the 15Min time window is 3 minutes and the interval of the 1H time window is 6 minutes.

Power Details for a Different Time Window

Click the arrows < > to view the details for the previous/next sampling time, or click the double arrows << >> to view the details for the previous/next page of results for the current time window. You can click Average, Maximum, or Minimum to display the selected value.

• Average: The average value from the previous time point to the current time point.

• Maximum: The maximum value from the previous time point to the current time point.

• Minimum: The minimum value from the previous time point to the current time point.

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. You only need to pay attention when the Average power value exceeds the Power Cap value.

NOTE: You can set the time interval (the period from a time point to the next time point) in the Settings page. For information on configuring the interval, see Monitoring Settings.

Power Details for Racks

For racks, you can click Power Consumption to display PDU power consumption for all rack PDUs.

You can also click Power Policies to change a power policy.

NOTE: The Power Policies button is only enabled if you have configured a power policy in the Policies page.

You can view the following power details of PDU devices. For more information on supported PDU devices, see System

Requirements.

• PDU device information, including PDU name, model, and IP address.

• PDU outlet information, including outlet number, power (W), voltage (V), amps (A), and the time of the information recorded, following the format <YYYY-MM-DD HH:MM:SS>. The table lists the information for each outlet and the total power consumption for all outlets.

NOTE: For PDU outlet information, Power Center only supports the Dell Managed Rack PDU 6605.

Viewing Energy Consumption

The Power Details page provides the following energy consumption information:

• IT Equipment Energy — The total energy consumption and cost for all managed devices in the selected device/ group.

NOTE: Power Center can read the power consumption of a device when it as at S0 (On) state. For devices in S4/S5 state, Power Center uses a fixed value (30W) to calculate the power consumption.

• Cooling Energy — The estimated energy consumption and cost needed to cool the selected device/group.

Cooling Energy = IT Equipment Energy * Cooling Multiplier

You can configure the cooling multiplier on the Settings page, in the Energy Consumption section.

• Energy Consumed (Total) — The combined energy consumption and costs for the IT equipment and cooling energy. The formula is:

Cost = (IT Equipment Energy T1*Cooling Multiplier) *Flat Rate T1+(IT Equipment Energy T2*Cooling Multiplier) *Flat Rate T2+°¦+(IT Equipment Energy Tn*Cooling Multiplier) *Flat Rate Tn

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 → Energy Consumption page.

NOTE: The Energy Consumption section displays information based on the values configured in the Settings page. This information should be used as an estimate only.

NOTE: When a device or group is newly-added or created in Power Center, the power and energy consumption data displayed in the "1W" and "1M" time windows are different if the monitored time is less than 1 week, and the data displayed in the "1H" and "1D" time windows are different if the monitored time is less than 1 day. This occurs because Power Center uses different sampling intervals for different time windows. For example, a device is added into Power Center at 2011-10-15 09:00, and the current time is 2011-10-17 11:10. For the 1M time window (sampling interval is 1 day), the power and energy consumption is calculated from 2011-09-17 00:00 to 2011-10-17 00:00. For the 1W time window (sampling time is 1 hour), the power and energy consumption is calculated from 2011-10-10 11:00 to 2011-10-17 11:00. There is an 11 hour gap; therefore, the data displayed in the two time windows are not the same.

Monitoring PDU Power

To monitor PDU power, click Groups in the left pane, navigate to the PDU, and click the Overview tab. The PDU Dashboard displays all PDU information.

The boxes in the PDU Dashboard show the instantaneous power value of the PDU. The Dashboard page also lists the PDU details read from the device. It displays NA when the data is not provided on the PDU device.

Monitoring UPS Power

To monitor UPS power, click Groups in the left pane, navigate to the UPS, and click the Overview tab. The UPS Dashboard displays all UPS information.

The boxes in the UPS Dashboard show the instantaneous power value of the UPS. The Dashboard page also lists the UPS details read from the device. It displays NA when the data is not provided on the UPS.

Power Dashboard

You can monitor the Power Center overall status from the Dashboard.

1. Click Groups in the left pane.

2. Click the group/device icon.

3. Click Overview.

4. The Dashboard displays.

For devices (Excludes PDU and UPS):

– The left box displays the average power consumption of the latest sampling interval.

– The right box displays the level of the average power consumption by comparing it with the power

thresholds you set in the Thresholds tab.

For groups:

– The left box shows the aggregated power value of the latest sampling interval for the devices with Monitor

power capability in the group.

– The right box displays the level of the aggregated power value compared with the power thresholds you set

in the Thresholds tab.

NOTE: Aggregated power value is the power value calculated by the power data aggregation. The calculation formula is case-by-case, and depends on whether the data aggregation is based on time periods or groups.

The right box displays different colors indicating different severity levels:

– Red shows the power range that triggers a critical event.

– Orange shows the power range that triggers a warning event.

– Green shows the power range that does not trigger any event.

For more information on how to configure the sampling interval, see Monitoring Settings.

For more information on how to configure the thresholds, see Power Monitoring Configuration.

Printing the Power Monitoring/Dashboard Graph

Click Print to print the power monitoring, power dashboard graph to a PDF file or printer.

You must set the Web browser to enable the "Print Background" option and other printing settings, otherwise the results are printed either without a background or with incorrect page alignment.

NOTE: For information on enabling “Print Background,” see your Web browser’s help.

NOTE: When printing graphs in Microsoft Internet Explorer 8, verify that:

• The Web browser mode is not set as Internet Explorer 7 mode.

• The following options are all selected in File → Page Setup :

– Portrait

– Print Background Colors and Images

– Enable Shrink-to-Fit

Temperature Monitoring

Power Center enables monitoring of the current or historical 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.

Temperature Monitoring Level

Power Center provides temperature monitoring at the following levels:

• Device level — You can monitor temperature-related metrics for devices.

• Physical group level — You can monitor temperature-related metrics at the physical group level (data center, room, aisle, chassis modular).

• Logical group level — You can monitor temperature-related metrics at the logical group level.

Temperature Monitoring Configuration

You can configure temperature monitoring settings in Power Center, including:

• Thresholds (Inlet temperature range for events)

• Device and group range (Monitor all or not)

• Sampling interval (1, 3, or 6 minutes)

• Default units (Celsius or Fahrenheit)

Temperature Thresholds

It is useful to monitor thresholds when you want to be notified when the temperature of the group/device exceeds the thresholds. Once the temperature value exceeds a critical or warning threshold, the related event is sent.

To configure thresholds:

1. Click Groups in the left pane.

2. Click the group/device icon.

3. Click the Thresholds tab.

4. Go to Temperature Thresholds and click Edit.

5. Enter values for the following:

– Critical thresholds for average inlet temperature - Greater — When the temperature is greater than the

setting, the critical-level event "Average Inlet Temperature" is sent.

– Critical thresholds for average inlet temperature - Less — When the temperature is less than the setting,

the critical-level event "Average Inlet Temperature" is sent.

– Warning thresholds for average inlet temperature - Greater — When the temperature is greater than the

setting, the warning-level event "Average Inlet Temperature" is sent.

– Warning thresholds for average inlet temperature - Less — When the temperature is less than the setting,

the warning-level event "Average Inlet Temperature" is sent.

6. Click Apply.

After you have configured the thresholds, you will see four lines with different colors indicating the thresholds in the Temperature Details tab.

For more information on how to configure the device/group range and sampling interval, see Monitoring Settings.

For more information on how to configure the default units and energy consumption, see Energy Consumption Settings.

Viewing Temperature Details

Click Groups in the left pane. Click the icon for the group or device, then open the Temperature tab.

By default, the Temperature Details graph displays the temperature details for the previous hour.

You can also view the following details:

Temperature Details for the Current Time Window

You can view temperature details for the current time window by clicking a time window tab. The following table describes the time windows and their associated intervals:

Table 6. Time Windows and Intervals

Time Window Description Interval

15Min 15 minutes 1 minute

1H 1 hour 3 minutes

1D 1 day 1 hour

1W 1 week 6 hours

1M 1 month 1 day

3M 3 months 1 week

1Y 1 year 2 weeks

Temperature Details for a Different Time Window

• Average: The average value from the previous time point to the current time point.

• Maximum: The maximum value from the previous time point to the current time point.

• Minimum: The minimum value from the previous time point to the current time point.

For example, you view temperature details in the 1H (1 hour) window and the maximum value at 15:00 shows 40°C and the time interval is 6 minutes. This value would represent that the maximum temperature from 14:54 to 15:00 is 40°C.

Chassis Details

The Chassis Details table appears when you access the Temperature Details page on a chassis. Chassis Details lists all blade servers within the chassis and their temperature details in a table, including:

• Device: Device name.

• Average: The average value of the latest sampling interval.

• Maximum: The maximum value of the latest sampling interval.

• Minimum: The minimum value of the latest sampling interval.

NOTE: You can set the time interval (the period from a time point to the next time point) in the Settings page. For information on configuring the interval, see Monitoring Settings.

NOTE: The Average, Maximum, or Minimum field displays NA if no data is available—for example, when the blade server is an Unsupported device.

Monitoring the Temperature of the Chassis/Blade Server

You can monitor the inlet temperature at the blade server level.

You can also monitor the inlet temperature at the chassis level, including average, maximum, and minimum details.

Monitoring the Temperature of Devices/Groups

Power Center supports temperature monitoring of the inlet temperature span for devices and groups. The inlet temperature span is the average inlet temperature differential between the maximum and 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.

Temperature Dashboard

1. Click Groups in the left pane.

2. Click the group/device icon.

3. Click Overview.

4. The Dashboard displays.

For devices (Excludes PDU and UPS):

– The left box displays the average temperature status of the latest sampling interval.

– The right box displays the level of the temperature status by comparing it with the temperature thresholds

you set in the Thresholds tab.

For groups:

– The left box shows the aggregated temperature value of the latest sampling interval for the devices with

Monitor temperature capability in the group.

– The right box displays the level of the aggregated temperature value compared with the temperature

thresholds you set in the Thresholds tab.

NOTE: Aggregated temperature value is the temperature value calculated by the temperature data aggregation. The calculation formula is case-by-case, and depends on whether the data aggregation is based on time periods or groups.

The right box displays different colors indicating different severity levels:

– Red shows the temperature range that triggers a critical event.

– Orange shows the temperature range that triggers a warning event.

– Green shows the temperature range that does not trigger any event.

For more information on how to configure the sampling interval, see Monitoring Settings.

For more information on how to configure the thresholds, see Temperature Monitoring Configuration.

Printing the Power Monitoring/Dashboard Graph

Click Print to print the power monitoring, power dashboard graph to a PDF file or printer.

You must set the Web browser to enable the "Print Background" option and other printing settings, otherwise the results are printed either without a background or with incorrect page alignment.

NOTE: For information on enabling “Print Background,” see your Web browser’s help.

NOTE: When printing graphs in Microsoft Internet Explorer 8, verify that:

• The Web browser mode is not set as Internet Explorer 7 mode.

• The following options are all selected in File → Page Setup :

– Portrait

– Print Background Colors and Images

– Enable Shrink-to-Fit

Policies

A power policy is a set of configurations used to manage the power cap for a device or group. A policy is useful for power management in different situations. For example, you can set up a policy to:

• Make sure power consumption does not exceed the capacity of the circuit.

• Schedule power usage according to the workload of the device/group. For example, you can set an aggressive cap when the workload is low, enabling a reduction of power use for your data center.

• Increase rack density. For example, you could monitor current power consumption on a rack with ten device to estimate how many additional devices you can add to the rack. Then, you can establish a power policy to cap the total power consumption of the rack after the devices are added.

Power Center supports two policy types:

• Static—Manually set the power cap for each device in a rack or chassis.

• Dynamic—Power Center dynamically allocates the power cap for each device in a data center, room, aisle, rack, or chassis.

From this screen, you can:

• Enable or disable a power policy

• Delete a power policy

• Create a new power policy

• Filter power policies so only certain policies display

• Edit a power policy

• View policy details including:

– Enabled: Whether the policy is enabled or disabled

– Active: Whether the policy is currently in use or not

– Entity Name: Name of the group to which the policy applies

– Policy Name: Name assigned to the policy

– Type: Static policy or dynamic policy

– Power Cap: Power cap for the group

– Date Range: Start and end dates defining when the policy is active

– Time Range: Time of day when the policy is active

– Days: Day(s) of the week when the policy is active

NOTE: If an emergency occurs—for example, power fails and devices are running on the UPS—you can initiate an

Emergency Power Reduction to minimize power consumption.

Dynamic Power Caps

The following terms are helpful for understanding how a dynamic power cap works:

• Consumption: The amount of power a device is using.

• Power Cap: The maximum amount of power that a device is allowed to consume (may not be equal to its demand).

• Headroom: The difference between power cap and power consumption of a device or a group of devices under a power policy.

• Demand: Amount of power a device requests to accommodate its workload.

The top priority of a dynamic power cap is to enable all devices to execute workloads without requiring more power than the overall power cap assigned to the group. When choosing a dynamic power cap, remember:

• If lower-priority devices require additional power to maintain their cap, they may receive more power than higher-priority devices.

• If the power cap is too restrictive and the group power consumption exceeds the power cap, an event is sent for the power policy. If this occurs frequently, you should reconsider the power allocation or adjust workloads accordingly.

• If fluctuations in device power requirements occur after the power cap is successfully established, then a device that requires additional power may not receive it if the power cap of another device in the policy would be violated. To force one or more devices in a policy to a lower cap, create a static power policy for the device at a lower level (rack or chassis). The most restrictive power cap of the overlapping policies will be applied to the device.

• If there is excess available power (known as headroom) after all power capping requirements are met, it is dynamically allocated according to the priority and demand of each device in the power policy.

Power Policy Capabilities

Power Center defines the following statuses of power policy capabilities for the devices:

• Unknown — Shown for unsupported devices or devices that were never connected to Power Center.

• None — No power policy capability. You cannot set any policy on the device.

• Monitor — With power monitoring capability only.

• Monitor & Capping — With power monitoring and capping capabilities.

• Monitor and Upgradable — With power monitoring capability, and can be upgraded to have power capping capability.

You can find this power policy capability status in the Power Capability column of the Devices page.

For servers that comply with Dell iDRAC7, when there is a power policy capability change due to a license change, Power Center will change its information in the management console within 24 hours. There are two scenarios:

Scenario 1 — The license expires or is not imported

In this case, the following happens:

• If a policy exists on the devices, you will receive a "Server Capabilities Changed" event.

• The Policies tab of the devices is set to disabled in the Groups page.

• The power capability status of the devices is set to "None" in the Devices page.

• 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, you will receive a "Server Capabilities Changed" event.

• 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. You can access it from the Policies page.

Upgrading Device Power Policy Capability

The power policy capability of some devices can be upgraded to include capping of power consumption—for example, Dell PowerEdge M620. These devices show Monitor and Upgradable. To upgrade the device so that its power consumption can be capped, go to the Devices page and click Upgrade next to the device, then follow the instructions on the pop-up help page to upgrade the device power capability. Once the upgrade is completed, the power capability status changes to

Monitor & Capping within 24 hours.

Creating a New Power Policy

1. Click Groups in the left pane.

2. Click the entity (data center, room, aisle, rack, or chassis) to which the policy will apply.

3. Click the POLICIES tab near the bottom of the screen.

4. Click Create New Policy.

5. In the Create New Policy window:

a) Enter a policy name that is less than 25 characters. b) For racks and chassis only, select a Policy Type of c) Select a fixed time period to display Average Power and Maximum Power values that can be used to estimate a

Power Cap Value. The Average Power, Maximum Power, Lower Bound and Upper Bound values only refer to the devices that have monitoring and capping power capability.

d) Enter either a Power Cap Value or Percentage of Capability to set the total power consumption budget for

devices with monitoring and capping power capabilities:

* Power Cap Value—Enter a value between the Lower Bound and Upper Bound. The

lowest minimum power consumption since the device/group was discovered or added to Power Center. The

Upper Bound

workload state.

* Percentage of Capability— Enter a percentage between 1-100%. The following formula will calculate

the total power consumption budget: e) Click Next. f) Allocate power for the group/device:

is the maximum power consumption when the device/group is in a maximum

Static

Upper Bound

Dynamic

Percentage of Capability

Lower Bound

Power Cap Value

is the

* Dynamic policy—Set the priority (High, Medium, and Low) for individual devices in the group. Power

Center reserves more of the budgeted power for the devices/groups with a higher priority when the power budget is not completely utilized.

* Static policy—Enter values for the Power Cap or Percentage of Capability, if desired. By default, Power

the Power Cap Value and display a message. g) Click Next. h) Select a policy schedule when the group/devices will be monitored:

* Time Span—Always or a range (start and end times in the format HH:MM using 24-hour time)

* Recurrence Pattern—Always or specific days of the week

* Recurrence Range—Always or a range (start and end dates)

i) Review the policy summary information, and click Apply.

The new policy takes effect immediately.

Viewing Policy Details

You can view policies from the following pages:

• Policy page — This page lists all policies. You cannot create a policy on this page. You can edit, delete, sort, filter or enable/disable the policies.

• Groups → Policy page — This page lists policies for a specific entity. To view the policies, go to the Groups page, select a physical group or logical group, select an entity and click its Policies tab. You can create, edit, delete, sort, or enable/disable the policies on this page.

These two pages display policy details:

• Enabled — The policy is enabled or disabled.

• Active — The policy is in use or not in use.

• Entity Name — Name of the entity.

• Policy Name — Name of the policy.

• Type — Static power policy or dynamic power policy.

• Power Cap — Power cap for the entity.

• Date Range — Start date and end date for the policy to take effect.

• Time Range — Time of the day for the policy to take effect.

• Days — Day of the week for the policy to take effect.

Policy Priority Levels

When you create or update a policy, you can select different priority levels for each device/group. For example, you can set priority levels based on the service level agreements associated with workloads running on a device/group.

Power Center tends to reserve more power to the devices/groups with higher priority when the power cap for devices/ groups is not fully utilized.

For each device/group, you can set one of the three priority levels:

• Low

• Medium (Default)

• High

Priority lists are policy-specific; however, a device/group may have different priority levels in different policies. A higherpriority value of a device/group in a policy overrides the lower-priority value of the same node in another policy.

For example, you created Policy1 for device <A, B, C> and Policy2 for device <B, C, D>, 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.

Policy Modes

The policy mode is shown in the Enabled and Active columns in the Policies page. A green symbol indicates Enabled or Active. Power Center supports three policy modes:

Table 7. Policy Modes

Enabled Column Active Column Mode Description

Green Green Enabled and active The policy is in use now.

Green NA Enabled but not active The policy is available but

not in use now.

NA NA Disabled The policy is created but not

available for use.

Enabling or Disabling a Power Policy

1. Do one of the following:

– Click Policies in the left pane.

– Click Groups in the left pane, and then click the POWER POLICIES tab.

2. Click Enable/Disable.

3. Select a policy to enable, or deselect to disable.

4. Click Apply.

Displaying Policies in the Power Details Graph

1. Click Groups in the left pane.

2. Click the icon of the device/group, and go to the Power Details tab.

3. Click Power Policy under the graph.

4. Click Select Power Policy, and select a policy.

The policy implementation status is displayed in the Power Details graph.

NOTE: To hide a policy, click Power Policy again.

Editing A Power Policy

You can edit one power management policy at a time.

1. Do one of the following:

– Click Policies in the left pane.

– Click Groups in the left pane, select a group, and then click the Policies tab.

2. Click Edit next to the policy you want to change.

3. In the Edit Policy wizard, make changes to the Set Power Cap and/or Choose Schedule pages.

4. Click Apply to immediately apply changes.

Deleting a Power Policy

1. Do one of the following:

– Click Policies in the left pane.

– Click Groups in the left pane, and then click the POWER POLICIES tab.

2. Click Delete.

3. Select one or more policies to delete.

4. Click Apply.

Filtering Power Policies

You can filter power policies so they display according to type, power cap, and/or status.

1. Click Policies in the left pane.

2. Do one or more of the following:

– Click Policy Type and select

– Click Power Cap and enter a Minimum and/or Maximum BTU/hr limit

– Click Policy Status and select options for Policy Enabled and Policy Activated

3. Click Apply.

Static

Dynamic

Emergency Power Reduction

When there is an emergency situation—for example, if there is a power failure and the devices are running on the UPS, you can initiate Emergency Power Reduction to set the power consumption to minimal.

CAUTION:

Applying emergency power reduction will throttle power on the devices down to an extremely low level, which will impact performance. All devices with Monitor & Capping power capability are impacted. Use this only in an emergency situation.

To initiate an emergency power reduction:

1. In the left pane, click Groups.

2. Click the icon of the device/group, and go to the Policies tab

3. Click Emergency Power Reduction in the upper-right corner.

4. In the Emergency Power Reduction window, read the message, and click Continue.

All of the devices with the Monitor & Capping power capability within this group are set to the minimal power consumption state. The Emergency Power Reduction button appears in the upper-right corner of all pages. The devices impacted by emergency power reduction are marked with In EPR in the Groups pages.

Canceling EPR

1. In the upper-right corner of any page, click Emergency Power Reduction.

The Emergency Power Reductions window opens.

2. In the Remove column, select the devices/groups from which you want to cancel emergency power reduction. You can select multiple devices/groups.

3. Click Apply.

The In EPR text of the device/group disappears from the Groups page. The Emergency Power Reduction button disappears when you have removed all devices/groups from the Emergency Power Reductions window.

Policy-Related Events

When a device/group that is configured with a policy has a group structure change—for example, a device or group is deleted, moved, or added, a Warning event is sent. For more information on policy-related events, see Pre-defined

Events.

Comparing

NOTE: If you are using Internet Explorer 8, you must install Adobe Flash Player in order for the compare function to work properly.

Power Center enables you to add a device or a group to compare the device’s or group’s power and temperature status and energy consumption in the selected time period. For example, you can select the devices within two rooms and compare their temperatures, or select two groups with similar devices to compare their power consumption, or you can compare the data from one group in two different time periods. You can also print the comparison results.

The power and temperature information that you can compare includes:

• Power consumption — Average, maximum, minimum, and peak time power consumption.

• Temperature — Average, maximum, and minimum temperature.

• Energy — Total energy consumption and cost, including IT energy and cooling energy.

To compare the groups/devices, click Compare in the left pane, change the time period, and add a device or group.

Changing the Time Period

You can select a date and time range to compare the monitored power and temperature status of the devices within the selected period. To select a date and time period:

1. Click Change Time Period

2. Select start date and end dates from Date From and Date To.

You can either select from the calendar, or manually enter the dates in the format <YYYY-MM-DD>.

3. Select start and end times from Time From and Time To.

You can select from the drop-down list. If you need to compare the data for one day (24 hours), select 00:00 of this date and 00:00 of the next day to compare.

4. Click Apply.

Adding a Device or Group for Comparison

You can add one to three devices or groups to compare the power and temperature status. Only one device or group can be added at a time.

1. Click Add Device or Group.

2. Click a category in the left pane — Groups or All Devices.

A specific group/device selection window displays.

3. In the selection window, click Select next to the group or device.

The group or device group is added to, and displayed in, the Compare page.

Removing/Changing a Device or Group

To remove a group or device from comparison, click the X button of the selected device/group.

To change a device/group for comparison, remove the device/group first, then add a different device/group.

Printing the Comparison Result

To print the comparison result, click Print on the Compare page.

You must set the Web browser to enable the "Print Background" option and other printing settings, otherwise the results are printed either without a background or with incorrect page alignment.

For more information on enabling the "Print Background" option and other print settings, see Printing the Power

Monitoring/Dashboard Graph.

Event Management

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.

Power Center uses port 162 to listen for events from external devices. If the SNMP Trap service exists and uses port 162, Power Center automatically uses port 1162 to receive external events forwarded by the SNMP trap service.

Predefined Events

A predefined event is an event that Power Center defines based on system conditions. Device support for events includes:

• PDU/UPS devices – To receive events, you must subscribe to the event from the console of that PDU or UPS.

• Dell PowerEdge tower and rack servers – Support all IPMI events (IPMI Power Unit, IPMI Power Supply, IPMI Processor Temperature Trip, IPMI Fan).

• Dell PowerEdge blade servers – Only support IPMI Processor Temperature Trip events.

• Integrated Dell Remote Access Controller (iDRAC) – Only supports the IPMI trap format. To receive events from an iDRAC device, make sure the alert function is enabled and the IPMI trap format is selected for all Power Center-supported events in the iDRAC management console (IPMI Power Unit, IPMI Power Supply, IPMI Processor Temperature Trip, IPMI Fan). For example, in the iDRAC7 management console, you must select IPMI trap for all PWR/PSU/CPU/Fan-related alerts.

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

Cannot Register Event on Device The device cannot register device

events to the Power Center server automatically.

Communication with Chassis Failed Power Center lost communication

with the chassis.

Informative

Warning

Type Description Severity Level

Communication with Chassis Restored Power Center restored

communication with the chassis.

Communication With Node Failed Power Center lost communication

with the device.

Communication With Node Restored Power Center restored

communication with the device.

Database Maintenance Success Database maintenance completed

successfully.

Hierarchy Change Policy A group structure has affected a

policy.

Internal Error Power Center internal error. Warning

IPMI Power Unit Events related to the server power

unit.

IPMI Power Supply Events related to the server power

supply.

IPMI Processor Temperature Trip Events related to the server processor

temperature trip.

IPMI Fan Events related to the server fan. Critical

IPMI Test An IPMI test event was received. Informative

Kerberos SSO Initialization Failed SSO initialization failed because

Kerberos SSO configuration is incorrect.

UPS Bad Battery Events related to battery failure in the

UPS.

UPS Low Battery Events related to low battery limits

and exceeded thresholds in the UPS.

UPS Bad Temperature Events related to temperature limits

and exceeded thresholds in the UPS.

UPS Bad Input Events related to power input failure

in the UPS.

UPS Bad Output Events related to power output failure

in the UPS.

UPS Overload Events related to output power load

limits and exceeded thresholds in the UPS.

UPS On Bypass Events related to on bypass in the

UPS.

UPS Bad Bypass Events related to bypass failure in the

UPS.

UPS Shutdown Events related to UPS shutdown. Informative

UPS Charge Failure Events related to charge failure in the

UPS.

UPS Fan Failure Events related to power fan failure in

the UPS.

Informative

Warning

Informative

Warning

Critical

Warning

Critical

Informative

Critical

Type Description Severity Level

UPS Communication Lost Events related to communication lost

in the UPS.

Protocol Timeout Change Failed Protocol timeout change has failed. Warning

PDU High Load The PDU power is greater than the

high load threshold.

PDU Low Load The PDU power is lower than the low

load threshold.

PDU Overload The PDU is overloaded. Critical

PDU Outlet High Load The PDU outlet power is greater than

the high load threshold.

PDU Outlet Low Load The PDU outlet power is lower than

the low load threshold.

PDU Outlet Overload The PDU outlet is overloaded. Critical

PDU Outlet Off The PDU outlet is Off. Informative

PDU Outlet On The PDU outlet is On. Informative

Server Capabilities Changed The server capabilities have changed,

for example, a license change. This event is only applicable to a device that has a policy applied. When you see such an event, check the policy on the device.

Warning

Custom Events

Custom events that you have set up are automatically triggered when the custom condition threshold is reached.

Table 9. Power Center Custom Events

Type Description Severity Level

Average Power Average power consumption is

greater than the average value you set in the Thresholds

Average Inlet Temperature Average temperature is greater or

less than the average value you set in the Thresholds

Max Power Power consumption is greater than

the maximum value you set in the Thresholds

Policy Cannot Be Maintained Policy cannot be maintained because

average power consumption of devices with power capping capability that 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

Critical or Warning; depends on the threshold type

Critical

Informative

Type Description Severity Level

Power Return To Normal Power consumption returned to the

normal range you set in the Thresholds

Temperature Return To Normal Temperature returned to the normal

range you set in the Thresholds

Informative

When the following changes occur, then corresponding

• Device/group is removed from Power Center.

• Event condition is removed from Power Center; for example, the Threshold settings.

• Event condition is updated in Power Center; for example, the Threshold settings.

• Power policy is removed or disabled.

•

Policy Return To Normal

For example, when the event becomes an threshold and 40 °C as the reaches 60 °C. When the average temperature returns to 45 °C, the When the average temperature returns to 35 °C, the

Power/Temperature Return to Normal

Informative

event is triggered.

event. Using the Average Inlet Temperature as an example: If you set 50 °C as the

Warning

threshold, then

Critical

Warning

events become

event is triggered, the corresponding

and

Warning

Critical

event automatically becomes

Informative

events are sent when the average temperature

event automatically becomes

events:

Informative

Critical

Informative

Warning

Critical

Supported PDU and UPS Events

Power Center supports events for different PDU and UPS devices. The following table lists the events that are validated by Power Center for specific devices. There may be other events not mentioned in this table.

Table 10. PDU and UPS Events

PDU/UPS Model Supported Events

Dell UPS UPS Low Battery, UPS Bad Input

APC UPS UPS Low Battery, UPS Shutdown, UPS On Bypass

Eaton UPS UPS Low Battery, UPS Bad Input, UPS Bad Battery

Emerson UPS UPS Low Battery

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.

APC PDU PDU Low Load, PDU High Load, PDU Overload

ServerTech PDU PDU High Load, PDU Outlet On, PDU_Outlet Off

Emerson PDU PDU Low Load, PDU High Load, PDU Overload

Event Severity Levels

NOTE: Severity levels defined in Power Center may be inconsistent with the levels defined on monitored devices. For example, an event defined as severe on a device might be considered a warning event in Power Center.

Table 11. Power Center Event Severity Levels

Severity Level Icon Description

Critical Errors that cause managed devices or

Power Center to stop working properly. You must take action to resolve the issue.

Warning Errors requiring attention. You should

look into the root cause to determine whether to take action.

Informative Event that is not an error or warning.

This is an informational event; you do not need to take action.

Viewing Events

You can see the critical events notification from the Current Status section in the left pane of the Power Center management console, with the total critical events number shown.

You can view events from the following pages:

• Groups – Lists events at Critical and Warning severity levels only, from most recent to earlier. Displays events at different device/group levels. The events you see at a device/group level include all events that occurred on within this device/group.

• Event Logs – Lists all events at all severity levels.

Sorting Events

On the Event Logs page, by default, the events are listed by Timestamp in descending order (from most recent to older). To sort by a field, click the Up or Down symbol next to the field to list events in ascending or descending order. The symbol of the current sorted field is displayed in orange.

Editing Events

You can add comments to events to help track occurrences in your network environment— for example, you might add a comment describing why an event was triggered or the action that was taken.

1. Go to the Event Logs page.

2. Click the icon in the Comments column.

The Event Comment window opens.

3. Click Add Comment that is 512 characters or less.

4. Enter your comment in the Descriptions field, and then click Apply.

NOTE: You cannot edit a comment after clicking Apply. You can only add more comments. Power Center automatically adds User Name and Time Stamp information to each comment.

Deleting Events

Power Center automatically deletes old events according to your database purge settings. For more information on database purge settings, see Database Policy Settings.

You can also manually delete events in Power Center.

Deleting an Event

1. Click Event Logs in the left pane.

2. Click Delete → Delete.

3. Select the events to delete, and click Apply.

Deleting all Events

1. Click Event Logs in the left pane.

2. Click Delete → Delete All.

A message window appears.

3. Click Yes.

All the events currently listed on the page are deleted.

Filtering Devices

You can apply a filter to show only specific devices.

1. Click Devices in the left pane.

2. Click Filter.

The Filter window opens.

3. Click a filtering option in the left pane (IP Range, Date Range, Protocol, Status, Device Type/Model, Physical Group, Faceplate/De-rated Power, or Power Capability) to display a specific filtering option window.

4. In the filtering option window, use the displayed information to select one or more filtering options.

– IP Range — Enter the start and end IP address of devices.

– Date Range — Enter the start and end date of device discovery. Enter the dates manually in the format

<YYYY-MM-DD>, or select dates from the calendar. Devices discovered from 00:00:00 of start date to 00:00:00 of the next day after the end date are displayed. For example, if you enter the filtering option 2011-01-01 as both start date and end date, all devices discovered between 00:00:00 of 2011-01-01 and 00:00:00 of 2011-01-02 are displayed.

– Protocol — Select one or more protocols used for communication.

– Status — Select one or more device statuses.

– Device Type/Model — Select the device type or device model. Device Model is the specific model

information of a device type—for example, PowerEdge M610. All the models that currently exist in the Device List page are shown. If you selected both Device Type and Device Model, make sure the device type matches the device model. Otherwise, no result is shown.

– Physical Group — Select a physical group where the device is located. You can select any level of the

physical group, including data center, room, aisle, rack, chassis.

– Faceplate/De-rated Power — Enter a faceplate or de-rated power range of devices.

– Power Capability — Select one or more device power capabilities.

5. Click Apply.

The Device List page displays the filtered devices.

Filtering Events by Group/Device

You can filter the events by a group or device.

1. In the left pane, click Events Logs.

2. Click Group/Device Filter.

3. Click a filtering option in the left panel (Groups or All Devices) to display a specific filtering option window.

4. In the filtering option window, use the displayed information to select the filtering options. You can select one group

or device.

– For groups, the filtering option window lists the groups as active links. Click a link.

– For devices, the filtering option window displays the devices. Click Select next to a device.

5. The Event Logs page displays the filtered events.

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.

Before sending a test event, make sure:

• The IPMI device is added on the Devices page.

• The network connection status of the IPMI device is

• The Power Center server address is added in the event destination list of the IPMI device.

To send a test event from an IPMI device, see the following example for a Dell PowerEdge M610 server:

1. Open the iDRAC management console of the M610, and go to the page related to SNMP trap settings.

2. Click Send next to the Power Center server address to send a test event.

3. Open the Power Center management console, and click Event Logs in the left pane.

The informative event

IPMI Test

appears on the Event Logs page.

Connected

NOTE: For more information on steps 1 and 2, see the IPMI device documentation.

Security

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.

To enhance security for your Power Center system:

• Start services with a normal Windows operating system (OS) user account: After installation, Power Center services are logged on with the Network Service account by default. You can use a normal Windows OS user account instead of the Network Service account to provide better security.

• OS hardening: You can apply OS hardening on the system where Power Center is installed. By doing so, the minimum security foundation is set up for Power Center security-related configurations.

• Audit log: Power Center tracks the action log for critical user operations, including user login/logout, emergency power reduction, start/stop network discovery, security configuration, and policy change.

• Certificate management: To enforce communication confidentiality and data integrity, Power Center enables SSL/TLS communication between the Power Center management console and the Power Center server and between the Power Center server and managed chassis. The SSL/TLS authentication is certificate-based. Power Center uses a Keystore file to manage certificates.

Starting Services with a Windows Operating System Standard User Account

To configure a standard Windows user account, follow these steps:

1. Stop all Power Center services.

2. Go to Control Panel → User Accounts → Manage User Accounts , and add a new standard user (either local or domain), or select an existing standard user.

3. Grant Full Control permission of the following directories or files to the user account.

Directory:

– Dell\OpenManagePowerCenter\bin

– Dell\OpenManagePowerCenter\external\apache-tomcat

– Dell\OpenManagePowerCenter\external\pgsql\bin

– Dell\OpenManagePowerCenter\logs

– Dell\OpenManagePowerCenter\pgdata

File:

– Dell\OpenManagePowerCenter\conf\user.config.xml

– Dell\OpenManagePowerCenter\conf\app.config.xml

– 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\external\jre\lib\security\krb5.conf

– Dell\OpenManagePowerCenter\external\jre\lib\security\login.conf

– 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\work.

5. Update the Properties of the Power Center services to use the normal user account to log into the service. When the system notifies that "The account .\A has been granted the Log On As A Service right," click

6. Start all Power Center services for these changes to take effect.

OK to confirm.

Operating System Hardening

Before deploying Power Center on a virtual appliance, you must configure the operating system (OS) as follows to prevent data conflicts and errors:

• Installation Settings

– Do not install Power Center and its database in the system volume or domain controller.

• Service Pack and Hotfix Settings

– Install all critical or important service packs and hot fixes.

– For Windows Server 2003, use version SP2 or above.

• Account Policy Settings for Windows Server 2003, Windows Server 2008 and Windows 7/Vista:

– Use the minimum password length.

– Use the maximum password age.

For Windows Server 2008 and Windows 7/Vista:

– Apply all of the account policies in the Center for Internet Security (CIS) 2008 and Windows 7/Vista

hardening benchmark.

• User Rights Settings

– Apply all user rights hardening requirements for Windows Server 2003, Windows Server 2008, and

Windows 7/Vista of the CIS benchmark.

• Security Options Settings

– Apply all security option hardening requirements for Windows Server 2003, Windows Server 2008, and

Windows 7/Vista of the CIS benchmark, including the requirements for the domain controller.

• File and Registry Permission Settings

– Apply the hardening requirements for Windows Server 2003 of the CIS benchmark.

For more information on CIS benchmark, see http://cisecurity.org.

For more information on Power Center-supported operating systems, see System Requirements.

Audit Log

Power Center tracks critical operations and stores related information in a log file for auditing purposes. Each log includes the following basic information:

• User name

• Time

• Action

• Details (Depends on the action; see the following table for audit log details).

Table 12. Audit Log Details

Action Tracked Information

Successful/failed user login/logout Source IP

Add/remove emergency power reduction Impacted single device/group

Set/update/remove power policy Impacted single device/group

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: <InstallDir>\OpenManagePowerCenter\logs \Audit.log.x. Where x is the incremental number, if applicable (shown below.)

The total size of all audit log files is limited to 20 MB. Power Center keeps up to three audit log files of approximately 6.67 MB each. If a new log causes the file size to exceed the limitation for a single log file, Power Center renames the log file to a new name and stores the new log in a new log file with the original file name.

When generating an audit log file, the naming rules are as follows:

• audit.log — The first audit log file name. This file always logs the latest actions.

• audit.log.1 — The second audit log file name. This is copied from audit.log when it exceeds the file size limitation.

• audit.log.2 — The third audit log file name. This is copied from audit.log.1 when audit.log exceeds the file size limitation.

Managing Certificates

Power Center uses Keytool— a key and certificate management utility from the Java Runtime Environment (JRE)—to generate a key pair (a public key and an associated private key) that is used to create a self-signed certificate during installation.

Keytool is installed at <InstallDir>\external\jre\bin\keytool.exe. The private key and the self-signed certificate are stored in the keystore file at <InstallDir>\keystore.ssl. The self-signed certificate expires three months after installation.

NOTE: It is strongly recommended to update the private key and self-signed certificate within three months.

You can manage Power Center certificates in Keytool. Common scenarios include:

• Scenario 1 — Generate a key pair and self-signed certificate. During Power Center installation, a key pair and self-signed certificate are generated for the Power Center server.

NOTE: When you delete an entry from the keystore file, make sure you leave at least one key pair entry in the keystore file; otherwise, Power Center will not work.

• Scenario 2 – Replace the self-signed certificate with a signed certificate issued by a Certification Authority (CA). A certificate signed by a CA is more likely to be trusted by the Web browsers. To sign your certificate by a CA, do the following:

– Generate a Certificate Signing Request (CSR) and submit to the CA.

– 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 will fail. In this scenario, you may need to import a new trust certificate to make sure a trust path can be built to verify the certificate.

For more information on how to manage certificates, see Keytool documentation.

Configuring Power Center Settings

You configure all the Power Center settings in the Settings page.

1. In the left pane, click Settings.

2. Click Edit on the selected settings.

3. Enter or select a new value.

4. Click Apply.

Some settings will take effect immediately; some will not. See the following sections for more specific information.

Monitoring Settings

These settings are used to enable/disable monitoring and set the sampling interval:

• Monitor all devices and groups – Enables or disables monitoring of all devices and groups. The default is Yes. If you select No, you cannot view the device/group power and temperature details.

• Power sampling interval – Power Center gets power data according to the sampling interval you set (1, 3, or 6 minutes). You can view power data on the Power Details page. The default is 1 minute.

• Temperature sampling interval – Power Center gets temperature data according to the sampling interval you set (1, 3, or 6 minutes). You can view temperature data on the Temperature Details page. The default is 1 minute.

Recommended Sampling Intervals for Performance Tuning and Scaling

It is important to configure appropriate Power and Temperature Sampling Intervals in Power Center, because sampling intervals impact the system performance and footprint significantly, including network bandwidth consumption, database size, and trend graph display latency.

The default power and temperature intervals in Power Center are 1 minute. This value is appropriate for small- or medium-sized environments where the device number is less than 1000; however, when the environment has more managed devices, it is recommended to adjust the values to 3 or 6 minutes.

NOTE: The device number includes only supported devices. Unsupported devices are not counted.

When are the settings effective?

• Monitor all devices and groups — Immediately

• Power/Temperature sampling interval — Every 30 minutes, for example, 08:00, 08:30, 09:00, and so on

Default Units Settings

These settings convert the power/temperature value into your selected units of measurement, and display the energy consumption cost in your selected currency.

• Power Units – Select the power unit used to display power details. Power Center automatically converts the power values according to the selected unit.

• Temperature Units – Select the temperature unit used to display temperature details. Power Center automatically converts the temperature values according to the selected unit.

• Currency – Select the currency used to display energy consumption cost. After you change the unit, Power Center does not convert the cost value according to the exchange rate—Power Center only changes the display of the currency symbol.

These are effective immediately.

Protocol Type Device Timeout Settings

These settings are used to configure the timeout between devices and the Power Center server.

• IPMI – Communication timeout between Power Center and an IPMI-enabled device (1-20 seconds). The default is 3 seconds.

• SNMP – Communication timeout between Power Center and a SNMP-enabled device (1-20 seconds). The default is 3 seconds.

• WS-MAN – Communication timeout between Power Center and a WS-MAN device (5-180 seconds). The default is 60 seconds.

The settings are effective from the next time Power Center tries to communicate with the affected device.

Energy Consumption Settings

These settings are used to calculate the energy consumption cost.

• Flat Rate — The rate of the power per kilowatt-hour (kWh); it uses the currency you set in Default Units. The default is 0.

• Cooling Multiplier — The multiplier enables estimating the energy needed to cool the device/group. The default is 1.5.

When are the settings effective?

• Flat Rate — From beginning of the next hour. For example, if you changed the setting on 8:15, the new setting will be effective from 9:00.

• Cooling Multiplier — Immediately.

Database Policy Settings

Database policy settings are used to configure the database maintenance policy.

Power Center stores monitoring data for your data center in a database file, using compressed power/temperature data to optimize for higher query performance and smallest database size. It stores both power/temperature compressed data and non-compressed data in the database. Data compression helps improve data query efficiency by aggregating and saving monitoring data using a bigger granularity (hourly or daily), but not the original granularity decided by the Sampling Interval.

By default, Power Center keeps compressed power/temperature data and event data up to 365 days and noncompressed power/temperature data up to 14 days. You can configure the length of time that Power Center will keep compressed and non-compressed data using the Purge Data Older Than and Data Compression fields. Data that exceeds its length of time or is older than the purge date is deleted. This improves the efficiency of the data query. You can automatically purge data by using the Schedule Database Purging Daily at field, or you can trigger it manually to start purging data immediately (see “Purge Database Now,” below).

You can set the following for database maintenance:

• Data Compression — Set the number of the days (1-14) to keep the non-compressed data. The default is 7 days.

• Purge Data Older Than — Set the number of the days (1-365) to keep the compressed data and the event logs. The default is 365 days.

• Schedule Database Purging Daily at — Set the time of day to start database purging (00:00:00 - 23:00:00). The default is 23:00:00.

• Export Database — Export the data in a selected date range to a .csv file. Click Export Database, and define a start and end date to export all the data between 00:00:00 of the start date to 00:00:00 of the next day after the end date to a .csv file. By default, the .csv file is saved in the Downloads folder of your Web browser. The following data is exported:

– Measurement data of supported devices (excludes groups) — There is no measurement data for

unsupported devices.

– Hourly data — Hourly data is the data collected during the hour before (timestamp - 1). For example, if

the timestamp of the data is 14:00:00, the PowerAvg field displays the average power from 13:00:00 to 14:00:00.

NOTE: If there is no data available at the defined timestamp, this field displays -1.

The .csv file includes the following fields:

– DeviceId — Power Center internal device unique ID

– DeviceType — Device type; for example, Server, PDU, UPS or CMC

– DeviceName — Device name

– DeviceIP — Device IP address

– Timestamp — Data timestamp

– PowerAvg — Average power value

– PowerMin — Minimum power value

– PowerMax — Maximum power value

– InletTemperatureAvg — Average inlet temperature value

– InletTemperatureMin — Minimum inlet temperature value

– InletTemperatureMax — Maximum inlet temperature value

• Purge Database Now — You can manually purge the database at anytime. Once you click Purge Database Now, Power Center immediately purges the database according to your setting in Purge Data Older Than. Once completed, you will see the informative event

Database Maintenance Success

in the Event Logs page.

Installation Settings

During Power Center installation, you set the communication settings between the Power Center server and the database. After installation, you can change these settings in the Settings page.

Database Settings

To change database connection information, you can configure the database settings on the Settings page. Power Center supports database settings changes for local and remote systems on both Windows and Linux servers.

NOTE: When changing database settings on a Windows server, you must stop Power Center services, make all changes, then restart Power Center services. For information on stopping and starting services, see your Windows operating system Help.

For Windows installations:

• Change local database settings: If you install Power Center using local database settings, you can change the settings (except PostgreSQL Host) on the Settings screen after installation. Power Center does not support switching from the local database to the remote database.

• Change remote database settings: If you install Power Center using remote database settings, you can change all the settings in the Settings screen after installation.

Before changing the database settings, the system must meet the following requirements:

• The correct connection information (Server Name, Database Port, Database User Name, Database User Password) are provided.

• The new database must be an existing Power Center database, and the version of PostgreSQL is at least 8.3.5.

• If the new database is located on a remote server, the database service on the remote server must be able to accept the remote database connection.

You can configure the following database settings on the Settings screen:

• PostgreSql Host

• PostgreSql Port

• User Name

• Password

For Linux installations:

1. Log into the OMPC server using the root user account.

2. Type /opt/dell/ompc/config.sh to access the command line interface.

3. Modify database settings.

4. Close command line interface.

LDAP Settings

Configure LDAP settings to manage user authentication and certificate validation.

1. Click Settings in the left pane.

2. Under LDAP Settings, click Edit.

3. To enable LDAP authentication, place a checkmark in the Enable LDAP User Authentication checkbox, then provide the following information:

– LDAP Server Address (required). Enter single DNS names or IP addresses, or multiple names or addresses

separated by a comma. For example:

192.25.46.89,192.25.47.68

– LDAP Server Port (required). Enter the port number for the LDAP server over SSL. The default port number

is 636.

– Bind Distinguished Name (optional). Where a Bind Distinguished Name is not provided, Power Center will

use an anonymous bind to search for the user's login Distinguished Name. For example:

uid=mark,ou=manager,dc=dell,dc=com

If a Bind Distinguished Name is provided, Power Center will not attempt an anonymous bind search.

– Bind Password (optional unless a Bind Distinguished Name is provided).

– Base Distinguished Name to Search (required). The Distinguished Name of the branch of the directory from

which searches start. For example:

ou=ccr,dc=dell,dc=com

– Attribute of User Login (optional). Use this field to specify an attribute for which to search. If this field is not

configured, the default search string used is “uid”. The User Login attribute must be unique.

– Search Filter (optional). Specify a valid LDAP search filter if you cannot uniquely identify the login user

within the chosen Base Distinguished Name. If a search filter is not provided, the filter defaults to (objectClass=*) and searches all objects in the tree. The maximum length of this property is 1024 characters.

– Certificate Validation Enabled (optional). If this option is selected, Power Center uses the CA certificate to

validate the LDAP server certificate during the SSL handshake.

– 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. Information describing the CA certificate currently in effect

displays.

– Network Timeout (seconds). Controls how long OpenManage Power Center LDAP will wait for an LDAP

server to set up a connection. The default is 30 seconds.

– Search Timeout (seconds).Controls how long an individual request can take before OpenManage Power

Center LDAP stops awaiting a response to the search request. The default is 120 seconds.

4. Click Apply to save these settings, or click Cancel to discard your changes.

100

Dell OpenManage Power Center v1.2 Owner's Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Overview

Key Features

Topology

System Requirements

Hardware and Software Requirements for the Server System

Hardware and Software Requirements for Devices

Getting Started

Management Console Introduction

Common Use Cases

Installing, Uninstalling, and Launching Power Center

Installing, Uninstalling, and Launching Power Center In Windows

Installing Power Center On A Windows Server

Installed Directories In Windows

Power Center Services in Windows

Upgrading

Uninstalling Power Center In Windows

Launching Power Center In Windows

Configuring ESC for Internet Explorer

Installing, Uninstalling, and Launching Power Center In Linux

Installing Power Center On A Linux Server

Installed Directories In Linux

Power Center Services In Linux

Uninstalling Power Center In Linux

Launching Power Center In Linux

Command Line Interface

Command Line Interface Error Handling

Command Line Interface Commands

help

add_profile

update_profile

add_device

update_device

rediscover_device

remove_profile

delete_device

add_group

delete_group

update_group

add_device_to_group

remove_device_from_group

move_device

move_group

add_group_to_group

List commands

list_device_props

list_devices

list_group_props

list_groups

find_device

Command Line Interface Error Codes

Access Control

About Authentication

Logging In

Logging in with User Name and Password

Log in with Single Sign-on (SSO)

Multiple User Login

Logging out

Managing User Roles

Adding a Custom Role

Editing A Role

Deleting A Role

Managing User Accounts

Adding A User Account

Adding A Group Account

Editing A User Or Group Account

Deleting a User or Group Account

Changing A User Account Password

Roles and Privileges

Manage role/user

Global Configuration

View Device/Group

Manage Device/Group

Manage Policy

Manage Event

Viewing Current User Information

Licensing