This post is more than 5 years old
4 Posts
0
21781
December 5th, 2012 22:00
Update Dell Customized ESXi 5.0 -> Dell Customized ESXi 5.1 using VMWare Update Manager
we have a four host cluster with r620s. vcenter and vum are already upgraded to 5.1. i'd like to update the hosts using the dell custom ISO. I've seen many threads that touch on this, but have yet to get a straight answer. Has anyone successfully updated updated Dell Customized ESXi 5.0 -> Dell Customized ESXi 5.1 using VMWare Update Manager?
Note: at present, hypervisor is installed to internal drives (not sd).
DELL-Chris H
Moderator
•
9.6K Posts
1
December 6th, 2012 06:00
Qionized,
Here is the straight answer you have been looking for. You should not have any issues updating the Dell Customized 5.0 to the Dell Customized 5.1. The issues you may have heard were due to updating from Dell Customized ISO 5.0 to the VMware version 5.1 (NOT Dell version), it was causing it to not see the NICS.
Let me know if this was what you wanted to know, or if you have any other questions.
qionized
4 Posts
0
December 11th, 2012 12:00
i can confirm this worked. however, two caveats:
1.) after upgrading VCenter to 5.1, the hosts required a reboot so that the refreshed bootbank could be detected by update manager; after upgrading vcenter/VUM, running an compliance check on the hosts returns "Not Compatible". after reboot of the host, the check correctly "out of compliance" and VUM can take care of things from there.
2.) during the ESXi upgrade, a message appears on the VMHost requiring you to hit to confirm that you would like to reboot and finish the install--it's possible that the reboot would eventually happen anyway, but nothing in the dialog (i forget the exact text) indicated this. basically, this means that *manual* intervention is required to complete the upgrade process. make sure you have console and/or drac access before proceeding. this is the first ESXi upgrade i've ever done, so i don't know if this is always the case, or if something can be changed in the dell custom image to bypass this.