Release Notes

Description: Creation of templates using an MX7000 chassis that is configured to both IPv4 and IPv6 fails if the appliance is
configured to use only IPv6. [167525]
Resolution: Ensure that both the appliance and the MX7000 chassis are configured to use the same protocol(s).
Issue 35
Description: The OpenManage Enterprise alert policies in de-branded MX7000 chassis are not deleted automatically when the
chassis is off-boarded and the chassis data is purged in the appliance. [166435]
Issue 36
Description: For the YX3X servers, few of the Subsystem Health section details, available on the individual device's Overview
page, such as the Storage, Temperature, and License details are displayed as 'No Data available,' even when their health status
is 'OK.' [155425]
Issue 37
Description: The 'From' address used for all email actions, such as Reports, Update, Discovery and Alert Policies, is dependent
on the SMTP server configuration. For some SMTP server configurations, the 'From' address is the Sender Email ID specified in
the Application settings (Application Settings > Console Preferences > Email Sender Settings > Sender Email ID) and
for others it is the username used for SMTP server authentication (Application Settings > Alerts > Email Configuration >
SMTP Server Network Address). [164204]
Issue 38
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 39
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 40
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 41
Description: Profile creation, editing and assigning requires the Boot to network ISO password has to be re-entered. [161247]
Issue 42
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 43
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 44
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 45
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 46
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]
15