Users Guide

ManualsBrandsDell ManualsActive System ManagerEMC OpenManage Power Center 4.0

Table Of Contents

Dell EMC OpenManage Power Center 4.0 User’s Guide
Overview
- Key features
- New in this release
- Topology
- System requirements
  - Hardware and software requirements for the server system
  - Hardware and software requirements for devices
Getting started
- Management console introduction
- Home page
- Common use cases
- Supported and unsupported devices
Using OpenManage Power Center
- Preinstallation requirement for OpenManage Power Center
- Using Power Center on Microsoft Windows operating systems
- Using OpenManage Power Center on Linux operating systems
Using OpenManage Power Center through Command Line Interface
- Command Line Interface error handling
- Command Line Interface commands
- Command line interface error codes
Access control
- About authentication
- Logging in
- Logging out
- Managing user roles and privileges
- Managing user accounts
- Viewing current user information
Task management
- Discovery tasks
  - Creating discovery tasks
  - Re-running recent discovery tasks
- Power control tasks
  - Creating power tasks
- Protocol profile
Device Management
- Adding a new device
- Adding an existing group
- Adding a device from the network
- Viewing resource utilization history
- Filtering devices
- Editing a device
- Deleting devices using a filter
- Sorting devices
- Updating Device location
- Chained PDU Support
  - Viewing chained PDUs
- Managing groups
Virtual machines
- Filtering virtual machines
- Creating a new virtual machine group
- Adding a virtual machine to an existing group
- Moving a virtual machine group
- Viewing a virtual machine power history graph
- Viewing a virtual machine power distribution graph
- Deleting a VM group
Power Monitoring
- Power monitoring levels
- Power thresholds
- Viewing power details
- Viewing Energy Consumption
- Viewing a power history graph
- Viewing system airflow graph
- Monitoring PDU
- Monitoring UPS Power
Temperature Monitoring
- Temperature Monitoring Level
- Viewing Temperature Details
- Viewing a temperature history graph
- Monitoring the Temperature of the Chassis/Blade Server
- Applying circuit breaker limits to chassis
- Monitoring the Temperature of Devices/Groups
Policies
- Dynamic power caps
- Power Policy Capabilities
  - Scenario 1 — The license expires or is not imported
  - Scenario 2 — You try to import a license on a device without a license imported
- Upgrading Device Power Policy Capability
- Creating a policy
- Policy Priority Levels
- Policy Modes
- Enabling or disabling a policy
- Viewing policies in the power details graph
- Editing a policy
- Deleting a policy
- Filtering policies
Analysis
- Server characteristics
- Underutilized servers
  - Configuring underutilized servers settings
- Power Analysis
- Cooling Analysis
Managing reports
- Viewing Report Details
- Creating reports
- Editing reports
- Deleting reports
- Adding report groups
- Editing report groups
- Deleting report groups
Event Management
- Pre-defined events
- Custom events
- Application log events
- Supported PDU and UPS events
- Event severity levels
- Viewing events
- Sorting events
- Adding comments to events
- Deleting events
- Filtering events
- Sending test events from an IPMI device
Security
- Starting Services with a Windows operating system standard user account
- Operating system hardening
- Audit log
- Managing certificates
Configuring settings
- General settings
  - Configuring console session timeout
  - Setting protocol timeout periods
- Monitoring settings
- Database policy settings
  - Setting or editing the database policy
  - Configuring database backup
- Directory
  - Editing directory settings
  - Viewing directory settings
- Alerts
- Editing SMTP settings
- Licensing
  - Importing a License
- Inventory
  - Configuring inventory settings
Logs
- Sorting the logs display
- Setting the application log size
Troubleshooting
- Why am I being required to log in more than once by Power Center?
- Why can’t I access the Power Center management console from a Web browser, even though the Power Center server is running normally?
- Why was I automatically logged out of Power Center?
- Why did my connection to iDRAC6 devices (PowerEdge Servers) fail, when the network connection status is Connected?
- Why can’t Power Center receive events sent from devices?
- Why are previously-existing power policies (including EPR) still effective on devices when Power Center is corrupted or has been uninstalled?
- Why do I see the PostgreSQL error log "FATAL: terminating connection due to administrator command" in the Windows event log?
- Why I can’t open power center login page when I access it through Firefox 31?
- Why I encounter an error, “An internal error occurred. Contact the technical support for help: subordinate error code: 0x8f0c1301”, the Home page when OpenManage Power Center server is installed on SUSE Linux Enterprise Server 11 SP2?
- Why do I encounter a network exception while adding a LDAP user?
- Why do I encounter a network exception while adding a chassis to a group?
- In the compare report, why is the average power value of a device different when the service is stopped for a few hours?
- Why is the “policy return to normal” event not displayed when the only device in the Chassis Management Controller (CMC) is deleted?
- After discovering the devices, incorrect device information is displayed? Why is this happening?
- I am not able to view the power headroom graph on the home screen. How do I troubleshoot?
- I am not able to manage the servers discovered by OMPC through the Redfish protocol. Events are also not logged. How do I troubleshoot and resolve the issue?
- I discovered a server through the Redfish protocol. When I tried to manage the server, the events are not logged in the event list. What do I do now?
Upgrade failure recovery on Microsoft Windows operating system
- Check OMPC statusRecover OMPCCheck OMPC database service statusRollback to previous OMPC versionCheck OMPC database upgrade statusUpdate OMPC to next versionRecover OMPC to old version
Upgrade failure recovery on Linux operating system
- Check OMPC statusRecover OMPCCheck OMPC database daemon statusRollback to previous OMPC versionCompleting OMPC upgrade

• SSH User Name — The user name for WMI-based device communication for managing third-party enclosures. Maximum length is

255 characters.

• SSH Password — The password for SSH-based device communication. Maximum length is 255 characters.

• WMI Port — The port for WMI-based device communication. The default port is 443.

• Validate Certicate — (Optional) Enables device certicate validation.

NOTE: You can change the protocol timeout settings in the Settings > General tab.

Redsh protocol support

Starting OMPC 4.0, you can discover devices by using the Redsh protocol. The tasks that you can perform by using the Redsh protocol

depends on the roles dened by the Distributed Management Task Force (DMTF) standard, namely Administrator, Operator, and ReadOnly.

For example, with the administrator role, you have access to all the iDRAC privileges, with the ReadOnly role, you have access only to the

iDRAC login privilege. For more information on the roles and iDRAC privileges, see the iDRAC Redsh reference guide.

In OMPC, you can discover and manage devices by using multiple protocols. For example, to manage servers-you can use the IPMI or the

Redsh protocol. OMPC does not change the protocol in use for devices discovered earlier. If you want to change the protocol to manage

a device, you have to delete the device discovered using a protocol and rediscover with the other protocol.

NOTE: You cannot discover the Non-Dell servers through the Redsh protocol.

Limitations in using OMPC with Redsh protocols and devices

• You cannot discover Non-Dell servers through the Redsh protocol.

• Power capping and iDRAC location update functionality is supported only on Dell’s 14th generation of PowerEdge servers.

• CUPS metrics, CFM metrics, and subsystem power metrics information are not available on devices discovered through the Redsh

protocol.

• The following features are not supported by the Redsh protocol:

• iDRAC location update

• Calculating average power

• Power Capping

• CUPS

• Airow

• Outlet Thermal

• PEC Chassis Information—only for C6320

• Graceful shutdown and graceful restart

• The following features are not supported on iDRAC9 by the Redsh protocol:

• CUPS

• Airow

• Outlet Thermal

• Slot number in chassis—only for C6420

• Graceful shutdown and graceful restart

NOTE

: In OMPC 4.0, there are restrictions in using Redsh protocol with the lockdown feature of iDRAC enabled. For more

information, see Troubleshooting chapter.

NOTE: By default, the Redsh events are not logged into the event list. For more information, see Troubleshooting

chapter.

Task management 59