Release Notes
Table Of Contents
Discovery and inventory
Issue 1
Description: When the Administrator password is reset on any discovered chassis (MX7000, M1000e, VRTX,and FX2), there is
a disconnection of the chassis with the appliance for 600 seconds. During this interval, the Health State of the chassis on the All
Devices page is displayed as 'Disconnected' and the tasks initiated on the chassis and sleds fail. [198434]
Issue 2
Description: Post deletion of 8,000 devices from the appliance, the automatic onboarding task fails during the next discovery
cycle. [200458]
Resolution: Restart the services from the Text User Interface (TUI) page.
Issue 3
Description: The RaidControllerId attribute in the ServerRaidControllers component in OpenManage Enterprise inventory and
CIQ device data inventory have different values for the same device. [185745]
Issue 4
Description: The MX7000 I/O Modules(IOMs) discovered in OpenManage Enterprise version 3.4 might not be displayed on the
All Devices page post upgrade. [179763]
Resolution: Rediscover the MX7000 chassis, post an appliance upgrade from version 3.4.
Issue 5
Description: For third party devices such as the HPE Proliant servers, you might see duplicate entries if they are discovered
using multiple protocols. This duplication can be corrected by deleting the entries and rediscovering the device(s) using only the
IPMI protocol. [180572]
Issue 6
Description: For the discovered HP servers, the devices' Hardware Logs are not displayed as the third party library used by the
appliance is unable to extract the hardware logs for HP iLO servers. [170550]
Issue 7
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]
7