Release Notes

Description: For the discovered HP servers, the 'Power Supply' details are not displayed under the subsystem health section
on the device's Overview page. This detail is missing as the third party API that is used to gather sensor health details, doesn't
provide the 'Power Supply' data. [85153]
Issue 8
Description: After the appliance time is configured as NTP or local time, then post system reboot a discrepancy is observed
between the 'Last Discovered' and the 'Last Edited' time for the Discovery jobs on the Discovery page (Monitor > Discovery).
[179309]
Issue 9
Description: For the discovered HP servers, the following field-replaceable unit (FRU) details are not displayed under the
device's Hardware page: Memory FRU details, BIOS - Part number and version, BMC controller - Part number. [75653]
Issue 10
Description: For the discovered Hyper-V servers, the Populated DIMM Slots and the Total DIMM Slots fields are displayed as
'0' on the device's Overview page. [IT-84431]
Issue 11
Description:For the discovered Windows servers using Open SSH, the MAC address is not displayed on the device's Hardware
> Device Management Info page. [181229]
Issue 12
Description: While discovering devices, a few invalid IP and IP-range formats are not being rejected resulting in 'failed'
Discovery jobs. [178692]
Resolution: Invalid IP or IP-range formats, as mentioned in the Context Help(i), must not be used for device discovery.
Issue 13
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 14
Description: The Guest information for the discovered Hyper-V 2012 R2 servers is not available on the device's Hardware page.
[159535]
Issue 15
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 16
Description: Server-initiated discovery is not triggered automatically in the appliance when a port-change announcement is
received.[167662]
Issue 17
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 18
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 19
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 20
Description: All the existing firmware compliance tasks will refresh automatically post device discovery. [146981]
7