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
Using OpenManage Power Center through
Command Line Interface
All commands supported by the command line interface (CLI) have the following format:
ompc_cli [COMMAND] [GENERIC_OPTIONS] [COMMAND_OPTIONS] [COMMAND_TARGET]
The operation must start with a valid [COMMAND]. Options can be entered anywhere after [COMMAND]. For each option that has a value,
the value must be supplied immediately after the option.
NOTE: If a duplicate or incorrect option value is supplied with a command, the CLI window is closed with an error. For example,
when both the –prole and –protocol options are supplied at the same time in a command, the CLI window is closed with an
error.
GENERIC_OPTIONS is used to run a generic job for this command line.
On Microsoft Windows operating system, user authentication credentials are specied as follows:
• user_auth <POWER_CENTER|WINDOWS_LOCAL|WINDOWS_DOMAIN>
• user_name <user_name>: If user_type is WINDOWS_DOMAIN, then the user_name must be in domain\user format.
• user_password <password>
On Linux operating systems, user authentication credentials are specied as follows:
• user_auth <power_center|linux_local|ldap>
• user_name <user_name>
• user_password <password>
The COMMAND_TARGET species the targets on which the command operates. For example, the COMMAND_TARGET for add_prole is a
prole name to be added. For a specic command, the
COMMAND_TARGET cannot have the same value with the name of a generic option
or an option supported by this command. For example, the COMMAND_TARGET cannot be –protocol or –user_name for the command
add_prole.
For COMMAND_TARGET, the order of its content must be kept as dened in the specic command denition section. Any valid option can
be mixed with the content of COMMAND_TARGET. For example, the order of COMMAND_TARGET of the move_device command must be
supplied
FROM_GROUP_PATH rst, then TO_GROUP_PATH.
Topics:
• Command Line Interface error handling
• Command Line Interface commands
• Command line interface error codes
4
Using OpenManage Power Center through Command Line Interface 31