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

When adding a chassis to a rack, the CLI chooses an available slot (if there is one available). If you want to specify a slot for the chassis in
the rack, you must use the add_device_to_group command.
List commands
The following are generic rules for list commands:
• The output of list commands is a simple table-like structure, where a comma-delimited list of column names will be output rst,
followed by the data, in comma-delimited format. There is one line per record. If a piece of data is not applicable or available, that data is
represented by two commas next to each other (NULL eld).
• Line breaks (CRLF) in the output elds must be replaced with spaces.
• Fields containing double quotes and commas must be enclosed in double quotes.
• If a double quote appears inside a eld, it must be escaped by preceding it with another double quote. For example: “aaa”, “b””bb”,
“ccc”.
list_device_props
Usage:
ompc_cli list_device_props [-service_tag <servtag>] [<device_name>]
The list_device_props command lists all properties for the device identied by servtag or device_name. Properties include
service_tag, protocol, protocol properties, device name, address (IP or host name), model, and device type (device name is the rst
column).
Secret data (password/key) is not listed as a protocol property.
list_devices
Usage:
ompc_cli list_devices [GROUP_PATH]
The list_devices command lists all devices immediately under the GROUP_PATH. If no GROUP_PATH is supplied, then the CLI lists all
devices, connected or not, that are managed by OMPC. Properties include all properties of the list_device_props command, except for
protocol information (the rst column has the device name).
If “/” is provided as GROUP_PATH, the CLI lists the devices at the root level.
list_group_props
Usage:
ompc_cli list_group_props GROUP_PATH
The list_group_props command lists all properties for a group identied by GROUP_PATH. Properties include group_type (DC, room, rack,
aisle, etc.), description, and additional properties unique to that group type. For example, for rack, the additional properties include capacity
and total power capacity.
This command does not apply to “/”.
Using OpenManage Power Center through Command Line Interface
39