Release Notes

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

Version Affected: All

Issue 3: While running the Firmware Update wizard, at the datacenter or cluster level, an error

message “The firmware repository file does not exist or is invalid.” may display. This may be due to

a daily background process that was unable to download and cache the catalog file from the

repository. This occurs if the catalog file is not reachable at the time the background process runs. .

Resolution/Workaround: After resolving any catalog connectivity issues that may exist, you can re-

initiate the background process by changing the firmware repository location and then setting it back

to the original location. Allow about 5 minutes for the background process to complete.

Version Affected: All

Issue 4: After completing the firmware updates using the Dell Management Plug-in, an inventory may

not be automatically initiated on the updated servers. The firmware versions displayed may show

previous values until a new inventory has completed. .

Resolution/Workaround: Verify inventory has completed successfully following a firmware update

and prior to viewing firmware versions or scheduling any new firmware update jobs.

Version Affected: All

Issue 5: Sometimes no hosts are listed after running the Connection Profile Wizard, even when there

are hosts managed on the vCenter.

Description: Sometimes no hosts are listed in the “Associated Hosts” page of create or update of

Connection Profile Wizard and the text “No Dell Hosts were found” is displayed even if there are hosts

managed on the vCenter. This issue is intermittant and the issue is due the caching on the browser.

Resolution/Workaround: The issue is resolved by clearing the browser cache. Press the F12 key on the

IE browser and then select the Cache->Clear Browser Cache

Version Affected: All

Issue 6: When Installing the Dell Management Plug-in for VMware vCenter I see the following error and

cannot proceed.

“Network card 'VirtualE1000' has a DVPort backing, which is not supported. This could be because the

host does not support VDS or because the host has not joined a VDS.”

Resolution/Workaround: Set the network interface to the VM Network during the OVF installation.

Then once the virtual machine is created remap the networking to the VDS port group.