Release Notes

for others it is the username used for SMTP server authentication (Application Settings > Alerts > Email Configuration >
SMTP Server Network Address). [164204]
Issue 28
Description: There is currently a discrepancy between the actual number of MIBs imported and the MIB count displayed on the
Monitor > MIB page. [160040]
Issue 29
Description: When NIC teaming is enabled on MX7000 chassis along with VLAN configuration, deploying of VLAN from the
OpenManage Enterprise console will overwrite the NIC teaming configurations to 'No teaming'. The LACP or other teaming
options would need to be reconfigured from MX7000.
Issue 30
Description: Appliance is unable to download the console upgrade from HTTP or HTTPS intranet share, when the intranet
share address is blocked in proxy filtering. [152092]
Resolution: If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download.
Issue 31
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 32
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 33
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 34
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 35
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 36
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 37
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 38
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 39
Description: OpenManage Enterprise could be impacted by the Linux TCP SACK vulnerability (CVE-2019-11477).
14