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 update_prole command updates an existing discovery prole identied by profile_name in OMPC. The semantics of the
command options are the same as those in add_prole. The protocol property set that can be updated depends on the protocol supported
by this prole. If new_profile_name is provided, the prole_name is updated to the new_prole_name.
add_device
Usage:
ompc_cli add_device [-device_name <device_name>] [-description <description>] [-size <size>] [-
estimated_max_power <estimated_max_power>] –device_type <SERVER | PDU | UPS | UNSUPPORTED |
CHASSIS | HYPERVISOR> [-model <model>] [–profile <profile-name>] [-protocol <protocol_name>]
[<pair of protocol property and value options>] [host_name or ip]
The add_device command adds a device to OMPC by using the prole name-identied prole or by using related protocol information
directly supplied through the command option. You cannot enter –profile and –protocol at the same time.
The device_name is optional, and if not provided, OMPC generates a device_name (following the same rule as in network discovery).
For unsupported devices, the default auto-generated device_name is Unsupported. To ensure unique identiers, OMPC appends numbers
to the device name.
The [host_name or ip] option is required, except when the device_type is Unsupported.
The -model option is valid only when the type is Unsupported.
update_device
Usage:
ompc_cli update_device [-description <description>] [-size <size>] [-estimated_max_power
<estimated_max_power>] [-host_name <host_name>] [-ip <ip>] [<pair of protocol property and
value options>] <device_name > [<new_device_name>]
The update_device command updates device information identied by its device_name. If new_device_name is provided, the
device_name is also updated to the new_device_name. [<pair of protocol property and value options>] depends
on the protocol supported by this device.
rediscover_device
Usage:
ompc_cli rediscover_device [-service_tag <stag>] [<device_name>]
The rediscover_device command lets OMPC connect with the device and refresh properties that might be changed on the device side (for
example, power capability and device model).
After rediscovery, the Time of Discovery is updated to the time of rediscovery.
For the Chassis Management Controller (CMC), if you try to rediscover the CMC before adding it to the rack, the blades inside it are not
enumerated. If you are rediscovering a CMC after it is added to rack, the blades are enumerated.
You cannot use -service_tag and device_name at the same time.
If the device is an unsupported device (device_type is Unsupported), the CLI displays the error, “CLI does not allow rediscover for
unsupported devices.”
34
Using OpenManage Power Center through Command Line Interface