Release Notes

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 14
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 15
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 16
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 17
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 18
Description: For Ubuntu devices, the OS Version under operating system information (from iDRAC/ISM) on the Device
Overview page is not displayed. [171103]
Issue 19
Description: With the Japanese version of the appliance, it is observed that the PDF export of the Warranty page contains
illegible characters. [176493]
Resolution: To get the PDF export of the Warranty page without the illegible characters, use the following workaround:
1. Export CSV report in Excel.
2. Change the encoding type to UTF-8.
3. Save it as PDF.
Issue 20
Description: When the appliance is configured to IPv6, it is unable to reach the targets like SMTP, syslog servers and share
through FQDNs which is resolvable to both IPv4 and IPv6. [153980]
Resolution: When the features that use FQDN fail, it is recommended to check the interface and use the corresponding IP. For
instance, if the primary network is enabled with only IPv6, and the FQDN expected to work on primary interface fails, user can
use IPv6 address in the place of FQDN as a workaround. This applies for secondary interface as well.
Issue 21
Description: Description: The Text User Interface (TUI) screen is not displayed until the 'Enter' key is pressed after updating
the appliance to version 3.4.1 on ESXi with large deployments involving 8,000 or more devices. [173206]
Issue 22
Description: Creating a report with chassis table columns and device table columns using a query with an 'or' will not generate
a report with expected result. [154713]
Issue 23
Description: When a Lead chassis retires and a backup chassis becomes the new lead on OpenManage Enterprise, the refresh
inventory marks the original backup chassis and its associated devices to be invisible and not shown in the UI. [161300]
Resolution: Discover the new Lead on OpenManage Enterprise.
Issue 24
Description: "Virtual identity by usage report" does not display the identity state as "Used" when the virtual identities were
assigned to a device from an external source. The current reports do not support the "Used" status, and instead display them as
either 'Reserved' or 'Assigned'. [160507]
Issue 25
14