Release Notes

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 23
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 24
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 25
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 26
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 27
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 28
Description: After the console is upgraded, there is a delay of approximately 15 minutes in the initiation of the Post Upgrade task by the
appliance. [130142]
Issue 29
Description: When an already imported MIB is renamed and parsed through API the trap status is reported as 'Existing' instead of
'Imported.'[111854]
Issue 30
Description: Ignore alert policy created for warranty, firmware compliance, configuration compliance alert will be ignored only if alert is
generated from the same device from which ignore policy was created. In other cases, alert will be received and not ignored. [124596]
Issue 31
Description: SSH Private key can be applied while adding a remote script in the Script Execution page. [129366]
Issue 32
Description: The Schedule advanced filter in the Monitor > Discovery page incorrectly displays even those discovery jobs which have
completed their initial scheduled run. [128842]
Issue 33
Description: In order to leverage performance improvements made in the Active Directory login, users have to delete and re-import the
user groups in OpenManage Enterprise version 3.2.
Issue 34
Description: The .CSV files, that record the deleted alerts from the Alert log, fail to capture the Device Name and the Device IP details of
the alerts received from the undiscovered devices.[132915]
Issue 35
Description: Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays an
Application timeout error. [133201]
Dell EMC OpenManage Enterprise Version 3.2.1 Release Notes
7