Users Guide
Table Of Contents
- Dell EMC OpenManage Power Center 4.0 User’s Guide
- Overview
- Getting started
- Using OpenManage Power Center
- Preinstallation requirement for OpenManage Power Center
- Using Power Center on Microsoft Windows operating systems
- Installing OpenManage Power Center on Microsoft Windows Server
- Installed directories in Windows
- OpenManage Power Center services on Microsoft Windows operating systems
- Upgrading Power Center on Microsoft Windows operating systems
- Uninstalling OpenManage Power Center on Microsoft Windows operating system
- Launching OpenManage Power Center on Microsoft Windows operating systems
- Configuring Enhanced Security Configuration for Internet Explorer
- 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
- help
- add_profile
- update_profile
- add_device
- update_device
- rediscover_device
- find_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
- list_report_groups
- list_reports
- run_report
- discover_device
- backup_database
- restore_database
- add_ssh_server_key
- remove_ssh_server_key
- list_ssh_server_key
- Command line interface error codes
- Access control
- Task management
- Device Management
- Virtual machines
- Power Monitoring
- Temperature Monitoring
- Policies
- Analysis
- Managing reports
- Event Management
- Security
- Configuring settings
- Logs
- 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
- Upgrade failure recovery on Linux operating system
• Click Run Once option to schedule one time database backup. Specify the date and time of the schedule.
• Select Periodic option and specify if the database backup has to happen daily, weekly, or on a specic day.
NOTE: Under the Range of recurrence option, select the start and end date for the task, or select the No End
Date option to run the task for an unlimited period.
7 Click Apply to save the changes or click Cancel to revert to the previously saved settings.
NOTE: After the database backup is complete, you can view the application log details about the completion of the
database backup by clicking Click here link.
Directory
NOTE: The Directory settings screen is available only in the Linux environment.
On the Directory settings screen, you can congure LDAP settings to manage user authentication and certicate validation on systems
running Linux, where OpenManage Power Center is installed. The following table lists the options available on this screen.
Table 14. Directory settings options
Option Description
Enable LDAP User Authentication Select the check box to enable the LDAP user authentication. The following elds are
enabled only when you select this check box.
• LDAP Server Address
• Bind Distinguished Name
• Bind Password
• Base Distinguished Name to Search
• Attribute of User Login
LDAP Server Address (Enter single DNS names
or IP addresses, or multiple ones separated by a
comma)
Enter the IP address or the DNS name of the LDAP server. You can enter multiple IP
addresses or names, separating them using a comma. For example:
192.125.46.89, 192.25.47.68
Bind Distinguished Name Enter a user name for the Bind search. If a name is not entered, OpenManage Power
Center uses an anonymous Bind to search for the user’s login Distinguished name.
For example: uid=mark, ou=manager, dc=dell, dc=com
Bind Password Enter a password for the Bind Distinguished name you provided.
Base Distinguished Name to Search The Distinguished name of the directory branch from where search begins. For
example: ou=ccr, dc=dell, dc=com
Attribute of User Login Specify a user login attribute for the search. If an attribute is not provided, the
default search string, ‘uid’, is used. The attribute must be unique.
Advanced Settings Select this check box to enable advanced LDAP settings. The following elds are
enabled only when you select this check box.
• LDAP Server Port
• Search Filter
• Network Timeout
• Search Timeout
• Enable Certicate Validation
LDAP Server Port Enter a port number for the LDAP server over SSL. The default port number is 636.
Search Filter Specify a valid LDAP search lter if you cannot uniquely identify the login user with
the specied Base Distinguished Name. If a search lter is not provided, the default
lter (objectClass=*) is used and all objects in the tree are searched. The
maximum length of this lter is 1024 characters.
118 Conguring settings