While upgrading to these releases, need to take care of Known issues of releases very carefully and also we should evaluate any existing client(3rd party, example like monitoring tools) uses SSLv3.
Good tip mentioned is, upgrade VC first and then ESXi due to one of known issues below.
<snip>
You need to update to latest vCenter Server 5.5 Update 3b version and then update to ESXi 5.5 Update 3b
<snip>
Info is @ VMware ESXi 5.5 Update 3b Release Notes
<snip of Release notes>
Miscellaneous Issues
- New ESXi does not get automatically added to vCenter Server inventory
If you update a previous version of vCenter Server and vSphere Update Manager to ESXi to 5.5 Update 3b, then after remediation task, ESXi does not get automatically added to VC inventory. Remediation process never gets completed and ESXi connection status in VC inventory is shown as disconnected.Workaround: When ESXi is rebooted after remediate process is started, enable SSLv3 on ESXi (which is disabled by default).
This will make sure ESXi gets added to VC inventory automatically in few minutes and Remediation as completed. For more information refer, KB 2139396
- New Connection failure between ESXi 5.5 Update 3b and View Composer earlier than 6.2 version
You cannot connect View Composer earlier than 6.2 version to ESXi 5.5 Update 3b in default state.
Workaround: You can enable SSLv3 on ESXi 5.5 Update 3b. For more information refer, KB 2139396
- New Attempts to upgrade ESXi 5.5 Update 3b to ESXi 6.0 Update 1 fails
Upgrading from ESXi 5.5 Update 3b to ESXi 6.0 Update 1 fails due to XHCI driver dependency conflict. This is issue is observed when you upgrade using a CD-ROM or esxcli method.
The following ESXCLI command throws upgrade error:
~ # esxcli software profile update -p ESXi-6.0.0-20150902001-standard -d /vmfs/volumes/datastore2/update-from-esxi6.0-6.0_update01.zip
[DependencyError]
VIB VMware_bootbank_xhci-xhci_1.0-3vmw.550.3.78.3223702 requires com.vmware.usb-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.Workaround: VMware recommends to upgrade the path for ESXi 5.5 Update 3b to ESXi 6.0 Update 1b.
- New Attempts to add an ESXi 5.5 update 3b host to a legacy vCenter Server fails
Attempts to add ESXi 5.5 U3b host to vCenter Server 5.5 Update 3 or earlier version fails with host communication error in the user interface.
Workaround: You need to update to latest vCenter Server 5.5 Update 3b version and then update to ESXi 5.5 Update 3b. If you don’t update to vCenter Server 5.5 Update 3b, then you need to enable SSLv3 on ESXi for all services. Enabling SSLv3 on ESXi will cause POODLE vulnerability.For more information refer, KB 2139396
<snip>
