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
add_device_to_group
Usage:
ompc_cli add_device_to_group [-slot <slot_num>] [-service_tag <stag>] [<device_name >]
GROUP_PATH
The add_device_to_group command adds a device to a group. If a device is added to a rack, the slot_num option is used to specify into
which slot the device is added. If the value of the slot is -1, the system chooses a slot automatically. When adding UPS/PDU, if you do not
provide a slot option, the UPS/PDU is attached to the rack. For adding a server or chassis to rack, -slot is allowed (when not provided,
the system chooses a slot automatically). If adding a server or chassis to other groups, -slot is not allowed (an error is displayed).
Slots start from 1 (0 is an invalid slot number).
PDU and UPS can only be added to a rack. For PDU and UPS in other types of groups in a previous OMPC release, if the you upgrade the
data, you must remove PDU and UPS from those groups after upgrading.
The add_device_to_group command does not move a device from one group to another group. This is done by move_device.
If a device already belongs to a group, you can use the add_device_to_group command to add the device to another group. After
successfully adding the device, this device belongs to both the old group and the new parent group. The exception is that devices can only
belong to one rack (not multiple racks), and blades can only belong to one chassis (not multiple chassis). You cannot add blades to a
chassis with the add_device_to_group command.
When a chassis is added to any group, the blades inside the chassis is enumerated and the chassis becomes a group that contains all of the
blades inside it.
remove_device_from_group
Usage:
ompc_cli remove_device_from_group [-service_tag <stag>] [<device_name >] GROUP_PATH
The remove_device_from_group command removes a device from a group identied by GROUP_PATH.
You can remove a chassis (as a device) from a group.
If a device belongs to multiple groups, after you remove it from one group, it still belongs to other groups.
A chassis can be removed through this command. In this case, the behavior is the same as removing a chassis by using the delete_group
command.
move_device
Usage:
ompc_cli move_device [-service_tag <stag>] [<device_name >] [-slot <slot_num>] FROM_GROUP_PATH
TO_GROUP_PATH
The move_device command moves a device from FROM_GROUP_PATH to TO_GROUP_PATH. After successfully moving the device, the
device no longer belongs to
FROM_GROUP_PATH; it belongs to TO_GROUP_PATH.
Using OpenManage Power Center through Command Line Interface
37