
Dell EMC OpenManage Enterprise Version 3.1 Release Notes
Others
Issue 1
Description: A query group with switch and device power state together is not working as expected. [86481]
Resolution: Exclude switch power state while creating a query group.
Issue 2
Description: The management IP is incorrectly indicated if the server is discovered by using both the IPv4 and IPv6 addresses. [86196]
Resolution: Manually start the iDRAC Graphical User Interface (GUI).
Issue 3
Description: The target IP address is incorrectly listed in the task history of an alert policy that is created by running a remote script. [86424]
Resolution: N/A
Issue 4
Description: The 'Create template task' status changes from 'failed' to 'completed' when a device is deleted. [85795]
Resolution: Recreate the template if the device is deleted.
Issue 5
Description: Not all scheduled jobs are displayed in the Recent Tasks list. [86488]
Resolution: Go to the Jobs page to view the latest and complete list of jobs.
Issue 6
Description: Discovery operation fails by using IPMI commands on the CISCO server if a KG key is used. [78545]
Resolution: KG key is not supported for this device discovery.
Issue 7
Description: When a device is turned off, the console takes a few moments to display the updated health status. [86146]
Resolution: Refresh the browser, or wait for a few moments.
Issue 8
Description: An individual Chassis Management Controller (CMC) health may not be correctly displayed in the device drill-down operation. [85977]
Resolution: Always consider the CMC rollup health status.
Issue 9
Description: Certain SNMP alerts are undefined for the S4810 networking switch. [85016]
Resolution: N/A
Issue 10
Description: An unknown Error message occasionally displayed in the SNMP alert console. [84894]
Resolution: Ignore or click Dismiss.
Issue 11
Description: In the SNMP alert console, some alerts from OMSA correctly show the Message ID field, while others show N/A. [83579]
Resolution: N/A
Issue 12
Description: Discovery of an HP server by using IPMI command may not reflect the correct rollup health status. [85153]
Resolution: View the lower-level sensor health data.
Issue 13
Description: In the Execution Details section, data must be manually sorted in the table every time after moving to a new page. [81207]
Resolution: Sort information of a single page at a time.
Issue 14
Description: Currently, the health status including PSU and temperature data is not displayed for the storage devices. [99821]
Resolution: N/A
Issue 15
Description: : The rollback features 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 16
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 17
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 18
Description: In OpenManage Enterprise version 3.1, authentication by one-way and two-way trusts of AD users is not supported.
Issue 19
Description: From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses. [102153]
Issue 20
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 21
Description: The update task fails when you try to manually update OpenManage Enterpirse version 3.0 to 3.1 by using an internal share. [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 22
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 to OpenManage Enterprise version 3.1. [115698]
Resolution: After updating the appliance to version 3.1, edit the alert policy and select the target devices or device groups to receive the group-specific alerts.
Issue 23
Description: After you update the appliance from OpenManage Enterprise-Tech Release to OpenManage Enterprise version 3.1, the Syslog server messages do not retain the standard format of <timestamp><hostname>_<Alert_Message><timestamp><hostname>_<Alert_Message>. The alerts are displayed as "EEMI@123_[id]":Alert_Message"EEMI@123_[id]":Alert_Message. [115699]
Issue 24
Description: Few alerts from the PowerEdge R240, R340, T140, T340, and R740xd2 servers are received with unknown severity in the OpenManage Enterprise appliance. [112404]