Release Notes

Issue 44
Description: Currently, the health status including PSU and temperature data is not displayed for the storage devices. [99821]
Resolution: N/A
Issue 45
Description: : The rollback feature is not supported on the MX7000 chassis. Also, the rollback operation fails on the M1000e, FX2, and
FX2s chassis. [110239]
Resolution: For M1000e, FX2, and FX2s chassis, create and associate a new baseline with the necessary firmware version to roll back.
Issue 46
Description: Currently, the alerts are not received by OpenManage Enterprise if the alerts are associated with the devices' IP address.
However, alerts are successfully received when associated with the device Service Tag. [106369]
Issue 47
Description: Invalid host names are displayed under the Source Name column and are also available for selection in some of the
OpenManage Enterprise tasks. [68214]
Issue 48
Description: Authentication by one-way and two-way trusts of AD users is not supported by the appliance.
Issue 49
Description: From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses. [102153]
Issue 50
Description: When PCIe cards are mapped to the FX2/FX2s chassis, migration of identities is not supported on the sleds in the same
FX2s chassis since the FQDDs differ.
Issue 51
Description: Console Upgrade from 3.0 through NFS Share fails. Also, console Upgrade through HTTPS (internal Share) fails when
upgrading from versions 3.0 and 3.1. [114683]
Resolution: Use the online method for updating, or use the HTTPS method. Ensure that the security certificates are signed by a trusted
third-party certificate authority while using the HTTPS method of update.
Issue 52
Description: The selected target devices or device groups while creating an alert policy in OpenManage Enterprise-Tech Release are
cleared when the appliance is updated. [115698]
Resolution: After updating the appliance, edit the alert policy and select the target devices or device groups to receive the group-specific
alerts.
Issue 53
Description: After you update the appliance from OpenManage Enterprise-Tech Release, the Syslog server messages do not retain the
standard format of <timestamp><hostname>_<Alert_Message>. The alerts are displayed as
"EEMI@123_[id]":Alert_Message. [115699]
Issue 54
Description: Few alerts from the PowerEdge R240, R340, T140, T340, and R740xd2 servers are received with unknown severity in the
OpenManage Enterprise appliance. [112404]
Issue 55
Description: While programmatically deploying the OpenManage Enterprise from Linux shell, if the argument provided for --name= in the
command line begins with a "$" then the argument is ignored and appliance is deployed with the name OPENMANAGE ENTERPRISE.
[121158]
Resolution: The --name= argument, which begins with "$" in the command line must be enclosed in single quotes, for example, --name=
'$OME-VM'.
Issue 56
Description: The Severity status in the Alert log for the alerts received from the PowerVault ME4 storage arrays is being reported as
Unknown by the appliance. This defect is due to the unavailability of the precanned MIBs for the PowerVault ME4 storage arrays in the
appliance console. [122657]
Issue 57
13