Release Notes

Dell Management Plug-in for VMware vCenter version 1.7 Release Notes

Issue 18: After deploying ESX 4.1u3(800380), OMSA is not configured.

Description: ESX 4.1 base, U1, U2, and U3 all require SSH to be enabled on Dell PowerEdge 11

generation servers at the time when inventory is run to determine if the OMSA is configured correctly.

If Dell Management Plug-in was used to deploy ESX 4.1 base, u1, u2, u3, it installs and configures

OMSA correctly. However, since SSH is not enabled, it shows the host as Not configured on the host

compliance page. In addition, if ESX 4.1 was installed outside and OMSA was installed and configured

using Dell Management Plug-in, and then the user turned off SSH later, the host shows as “Not

configured.” The system must have SSH enabled to show the correct status.

Resolution/Workaround: Either the user has to ignore the wrong status or keep SSH enabled at all

times.

Version Affected: 1.5 and later.

Issue 19: Deployment with IPV6 enabled may add host to vCenter with IPV6 address.

Description: If an IPV6 address was used to add the host to the vCenter, then the inventory will fail

on that host.

Resolution/Workaround: The workaround is to remove the host from the connection profile, remove

the host from the vCenter tree, then add the host back to the vCenter tree using the hostname, and

then add the newly added host to the connection profile.

Version Affected: 1.6 and later

Issue 20: Using localhost for hostname causes problems identifying the source of SNMP alerts.

Description: Starting with ESXi 5.1, a value of localhost for the hostname causes problems in

identifying the source of SNMP alerts. The use of localhost is not supported and a Fully Qualified

Domain Name FQDN should be used instead.

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 be configured. The MAC address is visible from the

Deployment Wizard’s Server Identification screen, 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.

Version Affected: 1.6 and later