Release Notes

Resolution or workaround: Log in or ask person with admin right account to log into OpenManage Power Center and create the
account if in fact you made a mistake of deleting the account.
Issue 6: Server cannot edit the power policy on the enclosure M1000e/VRTX from static to dynamic.
Description: OMPC supports static power policy for M1000e/VRTX at the chassis level. Due to this, the option for selecting
dynamic or static power policy is unavailable.
Resolution or workaround: Select Static power policy for M1000e/VRTX.
Issue 7: Device selection is lost when navigating to another page.
Description: This is a known limitation of the OMPC UI. The UI only focusses on the current page. Any actions such as edit or delete
need to be taken on the current page for the selected devices. Otherwise, the selection will be lost when you navigate to the next
page.
Resolution or workaround: Perform the recommended tasks on devices displayed one page at a time.
Issue 8: I get a network exception error when I am trying to log in with an LDAP user account.
Description: LDAP server conguration (see Settings > Directory) is required to log in with an LDAP user account. This issue could
be caused by the network communication between LDAP and OMPC server during the authentication process.
Resolution or workaround: Check the LDAP conguration in OpenManage Power Center setting to make sure the IP address of
LDAP server is correct.
Issue 9: The memory power is incorrect for some devices in power history window.
Description: The power history chart in device page shows abnormal reading/spikes in memory power.
Resolution or workaround: Update the iDRAC rmware to latest to solve this issue.
Issue 10: Power capability changed from Monitor and capping to None for T420 Server when we apply the the iDRAC rmware
2.10.10.10.
Description: Eventhough T420 server have the capping capability, it will change to None if we apply iDRAC rmware 2.10.10.10.
Resolution or workaround: Update the iDRAC rmware to latest to solve this issue.
Issue 11: Slot info of C6420 is not available if the device is discovered through Redsh protocol.
Description: If a C6420 server is added through Redsh protocol, there is no Redsh command to get its slot number in chassis.
Resolution or workaround: If you need to view the slot information, you can remove the device and re-discover the server through
IPMI protocol.
Issue 12: Turning on “Lockdown mode” on 14G servers will impact OMPC functions of power capping and device location editing, if
the server is discovered by Redsh protocol.
Description: 14th generation of PowerEdge servers provided a new switch “Lockdown mode” in iDRAC console. The “Lockdown
mode” will lock down all write operation on the servers. Turning on “Lockdown mode” on 14G servers will impact OMPC functions of
power capping and device location editing. These operations in OMPC will fail when the “Lockdown mode” is enabled.
Resolution or workaround: Turn-o the “Lockdown mode” in iDRAC console if you are discovering the server through Redsh
protocol or remove the device and re-discover the server through IPMI protocol.
Installation Prerequisites
Dependencies
• Managed servers must have an Integrated Dell Remote Access Controller (iDRAC) 6, 7, or 8. It is recommended to use the latest
version rmware.
• Power Distribution Unit (PDU) and Uninterruptible Power Supply (UPS) devices must comply with the Management Information
Base (MIB) the vendor provides through SNMP interface.
• Devices must provide exclusive access for Power Center because the policies set on the devices from other management
software aect the Power Center power control function.
• The Baseboard Management Controller (BMC) user, through which Power Center communicates with devices, must be a local
user account whose roles include Administrator. The device must be congured to allow the Administrator to use at least one of
the cipher suite levels 0–3, and enable the IPMI over LAN setting.
• The WSman user, through which Power Center communicates with the chassis, must be a local user with the Administrator role.
The chassis must be congured to enable the Web Server service.
5