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

The slot option is applicable only when moving a device (including a chassis) to a rack. It species which slot the device should be moved
into. If it is not provided when moving a device to a rack, the CLI identies a slot.
When moving a UPS/PDU from one rack to another rack and the slot is not provided:
• If the UPS/PDU is in a slot of a previous rack, the CLI selects one slot in the new rack.
• If the UPS/PDU is attached in a previous rack, the CLI attaches it in the new rack.
When moving a UPS/PDU from one rack to another rack and you have specied the slot:
• If the UPS/PDU is in a slot of a previous rack, the CLI uses the specied slot in the new rack.
• If the UPS/PDU is attached in a previous rack, the CLI reports an error.
You cannot change the UPS/PDUS properties between “slotted” and “attached” in Power Center. You can change between “slotted” and
“attached” by removing the UPS/PDU from the rack, and re-adding it to the rack.
If the device to be moved is a chassis, the behavior is the same as moving it through the move_group command.
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 identied by FROM_GROUP_PATH no longer belongs to the original parent in
FROM_GROUP_PATH. It belongs 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.
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 identied 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).
38
Using OpenManage Power Center through Command Line Interface