Release Notes

Issue 13: Windows Hyper-V guest information is missing when correlated with iDRAC during MX7000 discovery.

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 14: Incorrect managed state is displayed for MX7000 chassis when discovered using lower privileged credentials.

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 15: Managed state is not updated for devices when SNMP trap destination is manually set from iDRAC.

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 16: Incorrect inventory data after moving sled from lead to member chassis.

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 17 : Firmware compliance is executed on new device discovery.

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

Issue 18: Mismatch in device management IP for VxRail devices on Device Details and All Devices pages.

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 19: Servers reconfigured as VxRAIL post discovery, do not automatically group under HCI upon inventory refresh.

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 20: YX1X servers with iDRAC firmware version 1.98 or later show health status as 'unknown'.

Description: The All Devices page shows Health Status of the discovered YX1X servers with iDRAC firmware version 1.98 or

later as unknown.

Issue 21: iDRAC virtual console launch point is unavailable for proxied sleds.

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

managed state.

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

Issue 22: PowerVault MD3 storage arrays do not show the complete model numbers.

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]

Tasks

Issue 1

Description: For the failed alert-policy-triggered IPMI tasks, the task execution history on the Job Details page shows

duplication of the error message. [204404]

Issue 2

Description: The IPMI CLI command -I lanplus shell doesn't end automatically and the jobs associated with such tasks

would appear as 'In Progress' for a prolonged time on the Jobs page. [173061]

Resolution: You must run an Exit command to terminate such jobs.

Issue 3