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
System Requirements.............................................................................................................................................10
Hardware and Software Requirements for the Server System.......................................................................10
Hardware and Software Requirements for Devices........................................................................................11
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
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
List commands.................................................................................................................................................29
Command Line Interface Error Codes.....................................................................................................................31
About Authentication..............................................................................................................................................33
Logging in with User Name and Password......................................................................................................34
Log in with Single Sign-on (SSO)......................................................................................................................35
Multiple User Login..........................................................................................................................................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
Viewing Current User Information..........................................................................................................................43
Importing a License..........................................................................................................................................43
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
Editing a Single Device...........................................................................................................................................52
Editing a Protocol....................................................................................................................................................53
8 Group Management..................................................................................................................55
Mapping Group Structure Information...................................................................................................................55
Finding a Group or Device......................................................................................................................................55
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
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
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
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
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
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
Supported PDU and UPS Events.............................................................................................................................86
Deleting an Event.............................................................................................................................................88
Deleting all Events............................................................................................................................................88
Filtering Events by Group/Device.....................................................................................................................88
Sending Test Events from an IPMI Device.............................................................................................................89
Starting Services with a Windows Operating System Standard User Account.....................................................91
Operating System Hardening..................................................................................................................................92
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
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
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
FeatureDescription
Power MonitoringMonitors power-related metrics on the following levels:
•Individual device
•Data center/Room/Aisle/Rack/Chassis
•User-defined group
Temperature MonitoringMonitors data center temperature data.
Power ControlCreates policies that control data center power
consumption at the device and group levels.
Device DiscoverySupports Dell enterprise systems including PowerEdge
blade and tower/rack servers, chassis, and many different
PDU and UPS devices.
Role-based Access ControlSupports user authentication and multiple role-based
privilege levels.
Event ManagementAllows you to monitor and manage device and group
events.
1
Topology
The following figure shows how to use a Web browser to access the Power Center server and manage the data center.
9
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
10
•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:
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.
11
12
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 PageAvailable Actions on This Page
Getting StartedThis 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.
GroupsThis 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.
DiscoveryThis 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:
2
•View the active searches
•View the recent discovery jobs
•Rerun a search using the discovery search
criteria
DevicesThis 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
PoliciesThis page enables you to manage the power policies.
13
Main PageAvailable Actions on This Page
CompareThis 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.
SettingsThis page enables you to view or configure all settings.
Settings — User AccountsThis page enables you to set up and manage user
accounts.
Settings — LicensingThis page enables you to view or import a license.
Event LogsThis 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.
14
3
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.
15
* 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
16
To protect data, the following files are accessible only to Network Service or Administrator users:
•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.
17
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.
18
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.
19
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. The password can
include spaces.
– 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
20
To start, stop, or restart Power Center service, use the following command:
#service ompcdaemons start|stop|restart|status
Uninstalling Power Center In Linux
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.
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.
21
22
Command Line Interface
All of the commands supported by the command line interface (CLI) have the following format:
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_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>
4
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,
23
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
•
24
•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
.
Unsupported
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.
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).
25
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.
The delete_device command deletes a device. You cannot use –service_tag and device_name at the same time.
If the device is a chassis, it is deleted like a group (if the blades in it are already enumerated). The chassis itself is also
deleted from OMPC, and is no longer visible on the Devices page.
The 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.
26
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
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.
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
27
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.
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.
28
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.
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.
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”.
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
30
Loading...
+ 77 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.