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 delete_group command deletes a group identied by GROUP_PATH. All devices in this group are removed. The devices still exists on
the Devices page and in other groups that contain them.
All subgroups are removed from this group. If a subgroup belongs to multiple parent groups, this subgroup still exists in the other parent
groups. If the subgroup no longer belongs to any parent group (after being removed from the current parent), this subgroup is deleted from
OMPC. This also applies to the group itself.
If the [-preview] option is given, a summary of the groups, devices, and policies impacted is 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 specied group path are counted in the summary irrespective of whether they are deleted from OMPC or not
deleted. It is possible that a subgroup could be removed from the specied group path, but can not be deleted from OMPC due to a
reference from another parent group.
• All devices and subgroups are counted in the summary and not only the direct children of a specied group.
• Any policies that you added to the impacted devices are not counted in the summary, because the devices are not deleted from OMPC,
and these policies 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 is kept on the
Devices page as a device, but it no longer appears as a group if there is no other group containing this chassis (if there is no connection
between the chassis and the blades inside it).
update_group
Usage:
ompc_cli update_group [-description <description>] [-group_type <DC|ROOM|AISLE|CUSTOM|RACK >] [-
capacity <capacity>] [-total_power_capacity <power_capacity>] GROUP_PATH [new_group_name]
The update_group command updates the properties of an existing group identied 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 coniction.
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.
36
Using OpenManage Power Center through Command Line Interface