Release Notes

Resolution/Workaround: Set the network interface to the VM Network during the OVF installation. After the virtual machine
is created, remap the networking to the VDS port group.
● Issue 21: The Service Tag is not displayed during a firmware update.
Description: In the firmware inventory and on the Select Update Bundles tab, the Service Tag information is not displayed
for the Dell PowerEdge 11th generation servers. This information is not displayed if VMware vCenter does not provide the
Service Tag.
Version affected: All
Resolution/Workaround: You can view the Service Tag information on the Host Overview page from where you launched
the firmware update.
● Issue 22: Associated Connection Profile is not displayed in the host compliance page when inventory is not able to get
iDRAC IP for the host.
Description: If the iDRAC IP is not retrieved because of non-responsive iDRAC, the inventory fails and host to be associated
with the connection profile is not displayed on the host compliance page.
Version affected: 1.6 and later
Resolution/Workaround: Reset the iDRAC to fix the issue of iDRAC not being responsive, and then rerun the inventory. If the
inventory is able to get the iDRAC IP, then the host will be associated with the correct connection profile.
● Issue 23: Using local host for host name causes issues in identifying the source of SNMP alerts.
Description: Starting with ESXi 5.1, a value of local host for the host name causes issues in identifying the source of SNMP
alerts. The use of local host is not supported and a Fully Qualified Domain Name (FQDN) must be used instead.
Version affected: 1.6 and later
Resolution/Workaround: When deploying an ESXi 5.1 server using DHCP, it is strongly recommended that a combination of
a DHCP reservation based on the selected NIC MAC addresses, and a DNS host entry using the reservation’s IP address
must be configured. You can view the MAC address in Deployment Wizard’s Server Identification page, Network Interface
drop-down, and provided to help identify the network interfaces. The DHCP reservation and DNS entry should be created
for the server prior to scheduling the deployment, and if properly configured, should set the hostname to the value from
DNS.
● Issue 24: Deployments failure error message displayed on R210 II machines.
Description: Timeout issue on R210 II systems produces a hypervisor deployments failure error due to failure of BIOS to boot
from attached ISO.
Version affected: 1.5.1 and later
Resolution/Workaround: Manually install hypervisor on the machine.
● Issue 25: Unable to boot to service partition while deploying OS ISO.
Description:Hypervisor deployments are failing on Dell 11th and 12th generation servers with this error displayed on the
screen during POST: "Warning: Unable to boot to Service Partition". There is a BIOS issue to identify the network ISO when
there is a local USB CD-ROM installed on the system and that USB CD- ROM is the only USB mass storage device plugged
into the system.
Version affected: 1.5.1 and later
Resolution/Workaround: Remove the local USB CD-ROM (note that not all local CD-ROM would expose this issue), or plug
in additional USB floppy or USB key on the system, or attach the virtual media (virtual floppy and virtual CD) from the
iDRAC.
● Issue 26: A firmware update fails with an error message saying that USC is in use and it must be retried after 30 seconds.
Description: During a firmware update, the update fails with the error message: If USC is in use, wait until USC has exited
and retry the action. Otherwise retry after 30 seconds to check if network connectivity caused this error.
Version affected:1.5.1 and later
Resolution/Workaround: To fix this issue, reset iDRAC and wait until iDRAC boots properly and try the firmware update
again.
● Issue 27: Events from different vCenter are posted to another vCenter from a shared OpenManage Integration appliance.
Description: This situation can occur when a bare-metal server that was deployed in one vCenter is rediscovered again as
bare-metal server but then selected for a hypervisor deployed in another vCenter. This situation occurs if the host that was
already on one of the registered vCenter was added to another registered vCenter. In this case the host on first vCenter
appears as disconnected.
6