Release Notes

Issue 10

Description: If the IP configuration of a discovered device is changed during template deployment (from DHCP to Static or vice versa),

the Boot to Network ISO operation fails. This happens as the appliance is unable to ping the target post template deployment.[113576]

Issue 11

Description: Unable to set Target iSCSI IQN on BIOS-iSCSI via reference server template deployment, as it fails with Invalid

AttributeValue error. The default iSCSI Target IQN format of the iSCSI controllers of devices such as PowerVault ME4012 array and

Equallogic PS array, is not accepted as a valid IQN format for deployment with IDRAC version 3.34.34.34. [132601]

Resolution: Select 'BIOS' attributes only for deployment.

Issue 12

Description: Creation of a chassis template from a reference M1000e chassis which has Firmware versions 6.10 or later fails if SMBv1 is

disabled in the appliance. [129049]

Resolution: Enable SMBv1 in the appliance using Application Settings > Console preferences > SMB settings to create chassis

templates from M1000e chassis with firmware versions 6.10 or later.

Issue 13

Description: Template Deployment with iDRAC Management IP option "Set static IP for each device" fails with error message "connection

lost" with IPV6 IP (Legacy(3.1)). It works with IPV4.

Issue 14

Description: Template Deployment with iDRAC Management IP option "Set as DHCP" fails, and the task has to be tracked from iDRAC

for final status.

Others

Issue 1

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 2

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 3

Description: Upon an install or an upgrade to OpenManage Enterprise version 3.3.1 and configuration of network interface to DHCP, any

prior static IP settings will not be retained. [148789]

Issue 4

Description: The Timezone and NTP Server Address fields added to the Application Settings > Network > Time Configuration section

will remain blank and would not be displayed for a few minutes if the entered NTP server IP address is not reachable. [151221]

Issue 5

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 6

Description: Chassis health status shown in the chassis UI and the OMEnterprise console do 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 7

Dell EMC OpenManage Enterprise Version 3.3.1 Release Notes