Dell EMC OpenManage Enterprise Version 3.4 Release Notes

Discovery and inventory

Issue 1

Description: Discovery of Windows server(s) using non-admin credentials fails with an error message 'Unable to connect to the device over SSH because a connection error occurred.' This must be interpreted instead as 'Unable to perform the requested action because the device management endpoint authentication over SSH failed'. [158088]

Issue 2

Description: The Guest information for the discovered Hyper-V 2012 R2 servers is not available on the device's Hardware page. [159535]

Issue 3

Description: The correlation of Windows Hyper-V post MX7000 chassis CCD, fails to give the Guest VM information under Device details page. [167935]

Resolution: The sled discovery need to be done out of the MX7000 chassis and managed separately to view the guest details.

Issue 4

Description: Server-initiated discovery is not triggered automatically in the appliance when a port-change announcement is received.[167662]

Issue 5

Description: The Managed State of the previously 'Monitored' MX7000 chassis and sleds, on the All Devices page, is incorrectly displayed as 'Managed' post their rediscovery using the same lower privilege local or AD/LDAP credentials (Viewer or Device Manager) as before. [152154]

Issue 6

Description: If the SNMP trap destination is manually set in iDRAC as OpenManage Enterprise, the alerts are received and processed by the appliance. However, the device's Managed State displayed on the All Devices page remains the same as its initially discovered state of 'Monitored,' 'Managed,' or 'Managed with Alerts.' [158992]

Issue 7

Description: For the Multi-Chassis Management (MCM) group, a Chassis Refresh Inventory task for the 'lead' chassis does not fully update the sled inventory. A Chassis Refresh Inventory task is triggered in the appliance when a sled is removed from the lead chassis and added to a member chassis. [165191]

Resolution: To immediately update the sled inventory, trigger the refresh inventory of the sled manually. Otherwise, the sled inventory will be refreshed during the automatic daily inventory collection.

Issue 8

Description: All the existing firmware compliance tasks will refresh automatically post device discovery. [146981]

Issue 9

Description: The management IP on the Device Details page of the discovered VxRail devices does not match the management IP displayed on the All Devices page. [91653]

Issue 10

Description: If the onboarding state of the lead chassis and member chassis in an MCM group is in monitored state, the inventory task might fail if the MCM group is configured with more than 10 chassis. [108962]

Issue 11

Description: The exported inventory file lists values for component status and URL of the chassis is not listed. [108056]

Issue 12

Description: Servers that are reconfigured as VxRAIL do not automatically group under HCI upon refreshing the inventory. [116913]

Resolution: After a server is reconfigured as a VxRAIL, rediscover the device in the Discovery page. After rediscovery, the device is correctly grouped under HCI.

Issue 13

Description: The All Devices page shows health status of the discovered YX1X servers with iDRAC firmware version 1.98 or later as unknown.

Issue 14

Description: The iDRAC virtual console management launch point is unavailable in the All Devices page for sleds with a 'Proxied' onboarding state.

Resolution: Ensure the sleds are in a 'Managed' state.

Issue 15

Description: For the discovered PowerVault MD3 series storage arrays, the complete model numbers are not displayed by the appliance in the All Devices page. For these devices, the model numbers as returned from the SNMP walk are displayed. [119881]

Issue 16

Description: In order to support discovery with domain credentials, OpenManage Enterprise 3.2 and later uses SSH instead of WSMAN. Hence, all the Windows and Hyper-V devices discovered prior to updating the appliance have to be deleted and re-discovered using their SSH credentials.

Issue 17

Description: While creating sever discovery jobs with the Host OS option in the Create Discovery Job wizard, the check box Discover using SSH (Linux) in the Additional Settings dialog box is misleading and should be interpreted instead as Discover using SSH (Linux, Windows, and Hyper-V).