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
Resolution: Wait one minute or more for iDRAC6 devices to release the connection sessions, then try again.
Why can’t Power Center receive events sent from
devices?
Possible Cause: Power Center is not the destination host of the events sent from devices.
Resolution: Make sure the Power Center server’s IP address is registered on the device as the destination for events.
Possible Cause: There is a network connection problem.
Resolution: Make sure the device network and the Power Center server are connected and packets can be routed.
Possible Cause: Essential services are not started.
Resolution: Make sure that if the Windows SNMP trap service is installed on the Power Center server, this service and the OpenManage
Power Center SNMP Dispatcher are started on the Power Center server.
Why are previously-existing power policies (including
EPR) still eective on devices when Power Center is
corrupted or has been uninstalled?
Possible Cause: Even if Power Center is corrupted or uninstalled, the Power Cap Values of existing power policies (including EPR) on the
devices still remain eective.
Resolution:
NOTE
: Check your data center power capacity to avoid tripping the breaker before performing the following steps.
• If you intend to uninstall Power Center, make sure to remove all devices rst.
• If Power Center is corrupted, do one of the following to remove the power policies:
• If the device number is small, access the iDRAC management console, and manually remove the power policies.
• If the device number is large, perform the following steps. Power Center removes the policies rst, and then remove the devices.
1 Install Power Center.
2 Add all the devices to the Power Center management console.
3 Create a logical group that contains all of the devices, and then create a power policy for this group.
4 Remove all of these devices from the Power Center management console.
Why do I see the PostgreSQL error log "FATAL:
terminating connection due to administrator
command" in the Windows event log?
Possible Cause: This error is caused by Power Center server shutdown. Normally, the Power Center database service (Dell OpenManage
Power Center Database Server service) stops after other Power Center services; however, if the Power Center server has been shut down
quickly, the Power Center database service is forced to stop when other Power Center services are not yet stopped. In this case, the
database connection sessions that cannot be closed by other Power Center services is closed by the Power Center database service, and
126
Troubleshooting