Release Notes

Description: For the discovered C9010 network switches, the Model field on the 'All Devices' and the 'Device Details' page is
displayed as 'Unknown.' [188383]
Issue 10
Description: When a C9010 network switch is rebooted or reloaded, the alerts received in the appliance are being categorized
as Miscellaneous with message 'Unknown trap received with enterprise OID...' [188382]
Issue 11
Description: When a Z9264 network switch is rebooted or reloaded, the alerts received in the appliance are being categorized
as Miscellaneous with message 'Unknown trap received with enterprise OID....' [ 194718]
Issue 12
Description: Post addition of the disk space using the Configure Appliance Disk Size feature in the Text User Interface (TUI) ,
deletion or reduction of the appliance's console expanded disk space is not supported . [192976]
Resolution: To remove a newly-added disk or to reverse the increase in size of an existing disk, you must revert to prior VM
snapshot that you are recommended to take as a backup before applying any disk configuration changes.
Issue 13
Description: For a logged-in AD user belonging to an imported child AD group, it is observed that multiple roles such as Device
Manager and Viewer are displayed upon a mouseover on the username on the appliance masthead right-hand corner. This
happens if the parent directory group and child directory group are imported with different privileges. For such AD users, the
role with the maximum privilege will be applied. [195183]
Issue 14
Description: After upgrading the appliance, you may notice an incorrect Elapsed Time for the Console Update Execution task
on the Job Details page. The displayed elapsed time exceeds the actual time taken for the completion of the task. [173882]
Issue 15
Description: Console upgrade fails from version 3.4.1 to version 3.6, if there are a large number (more than 2,000) unreachable
devices, in multiple discovery settings, in OpenManage Enterprise version 3.4.1. This happens as the long runtime of Discovery
task exceeds the maximum wait-time limit of 48 hours set for the initiation of other post-upgrade tasks. [201178]
Resolution: To prevent upgrade failure, in such rare scenarios, you can manually cancel the Discovery task to allow the
post-upgrade tasks to initiate and finish normally.
Issue 16
Description: An invalid audit log indicating 'console upgrade failure' is generated upon a successful upgrade of the appliance
from version 3.4 to version 3.5. This audit log can be ignored. [173311]
Issue 17
Description: The Console Update Execution job's status is displayed as 'Failed' on the Jobs page, if the appliance upgrade takes
more than 60 minutes. The 'Failed' status is due to a time out of the Console Update Execution job and can be ignored as this
has no functional impact on the upgrade process. [170688]
Issue 18
Description: The built-in Virtual Disk report contains duplicate or empty values if the virtual disks and physical disks don't have
any associations and are used individually. This issue is not observed if the VDs an PDs are being used together. [174851]
Resolution: It is recommended to use a custom report to get only the virtual disk data if the VDs and PDs are not associated.
Issue 19
Description: Even with the MX7000 onboarding preference set as 'Receive Chassis category alerts only' in the appliance,
you might receive alerts of all categories (iDRAC, Network IOMs, Storage IOMs) from the newly-onboarded MX7000 chassis.
[180323]
Resolution: To view only the MX7000 chassis category alerts on the Alert Log page, it is recommended that you use the
Advanced Filters.
Issue 20
Description: For Ubuntu devices, the OS Version under operating system information (from iDRAC/ISM) on the Device
Overview page is not displayed. [171103]
Issue 21
Description: With the Japanese version of the appliance, it is observed that the PDF export of the Warranty page contains
illegible characters. [176493]
13