Release Notes

Resolution: If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download.
Issue 39
Description: Profile creation, editing and assigning requires the Boot to network ISO password has to be re-entered. [161247]
Issue 40
Description: After a fresh install or an upgrade to OpenManage Enterprise and configuration of network interface to DHCP,
any prior static IP settings will not be retained. [148789]
Issue 41
Description: The Timezone and NTP Server Address fields added to the Application Settings > Network > Time
Configuration section will remain blank and will not be displayed for a few minutes if the entered NTP server IP address
is not reachable. [151221]
Issue 42
Description: Addition of a new network interface in hypervisors fails immediately after upgrading the OpenManage Enterprise
from version 1.0 to version 3.3.1 (1.0>3.0>3.1>3.2>3.3.1). An error message "Failed to reconfigure virtual machine
Config-7 1.0 to 3.3.1. The attempted operation cannot be performed in the current state
(Powered on)" is displayed. [146752]
Resolution: Power off the virtual machine, add a new network interface, and then power on the virtual machine if the upgrade
workflow is 1.0>3.0>3.1>3.2>3.3.1.
Issue 43
Description: Chassis health status shown in the chassis UI and the OMEnterprise console does not match. This happens
because the chassis UI shows the chassis controller's health, whereas the OMEnterprise shows the overall health of the chassis.
Hence, it is recommended to check the component-related health status for M1000e, FX2s and VRTX chassis. [85977]
Issue 44
Description: Emails for alert policies don't work when the same event is generated twice within 2 minutes. Email action for
alerts containing the same message ID and content are triggered every 2 minutes to avoid many repeated/redundant alert
messages in the inbox.[148407]
Issue 45
Description: While creating a customized device discovery job protocol for SNMP devices, the displayed default settings of 3 in
the Retries box and 3 seconds in the Timeout box can be overlooked and should be customized as desired. [147416]
Issue 46
Description: When updating local shares for a manual upgrade for versions without any installed plugins (such as 3.1 and 3.2),
the audit log displays warning entries such as 'Unable to retrieve the source file of type Plugin Catalog because the file does not
exist' and 'The status of downloading the Plugin Catalog is Failed'. These error messages do not have any functional impact on
the upgrade process and can be ignored. [144379]
Issue 47
Description: Clicking Check Update on OpenManage Enterprise version 3.2, where PowerManager plugin is not installed, an
error CGEN1003- Unable to complete the operation because an empty payload is not allowed for
this request is displayed.
Resolution: This error can be ignored as it is for information purpose only. There is no functional impact of this error and the
user can go ahead with the upgrade.
Issue 48
Description: OpenManage Enterprise could be impacted by the Linux TCP SACK vulnerability (CVE-2019-11477).
Resolution: OpenManage Enterprise includes CentOS kernel patches for the TCP SACK Panic issues and carries the updated
kernel-3.10.0-957.21.3.el7.x86_64.rpm including fixes for the CVE-2019-11477 vulnerability.
Issue 49
Description: Post console update Time interval should be enabled manually in alert policy as it is disabled by default.
Issue 50
Description: Alert policies have been recategorized since OpenManage Enterprise version 3.3.1. The alert policies from
appliance versions before 3.3.1 need to be recreated after the appliance upgrade.
Issue 51
Description: A query group with switch and device power state together is not working as expected. [86481]
16