VMWare VSphere windows client version question

[GoingAlone]

Will be updating my esxi 5.5 host to build 4722766 from 12/2016. A couple questions

1. Does the newer build come with the newest client?

2. what vsphere client version should be used with build 4722766? Currently have 3237766.

Thanks in advance!

[jhague · Accepted solution]

‌You should be on 4032365 which correlates to 5.5 U3e - you can download from here - Download URLs for VMware vSphere Client (2089791) | VMware KB

[GoingAlone]

Thanks jhague!

Was doing a dry run of the latest 5.5 patch. As I mentioned below, I'm on the build 3248547 from 12/2015. Trying to go to 4722766. When I do the dry run, I am getting a dependency error

VIB VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.550.3.95.4345813 requires xhci-xhci >= 1.0-3vmw.550.3.95, but the requirement cannot be satisfied within the ImageProfile.

Still trying to find info on this. Do you have any idea why I'm getting this?  Do I need to update to a version prior to the newest one from the one I'm on?

Thanks!

[jhague]

‌It looks like that xhci version was introduced in a prior patch so I'd try installing that one first - VMware ESXi 5.5, Patch ESXi550-201609402-BG: Updates ehci-ehci-hcd, misc-drivers, xhci-xhci (2146719... - ESXi550-201609402-BG.

How are you installing? VUM?

[GoingAlone]

Don't have a vsphere server, so I use command line esxcli.

[a_p_]

I assume you are using the "esxcli software vib update ..." command? VMware introduces some additional vibs over time, which will not be installed using this command. Unless you are using custom drivers, it may be an option to update the host using the "esxcli software profile update ..." command.

André

[jhague]

maintenance mode

esxcli software profile update --depot=<path_to_patch_file> --profile=<e.g. ESXi-5.5.0-0123456-standard>

reboot - should do it....

If not try the staged approach.

John

[GoingAlone]

Yes Andre, I use the command you reference below. So I probable do not have this vib installed on my host, this is why I'm seeing this error? Will any of the patches that come after the version I'm on install this piece?

Command line used:

esxcli software vib update --depot /vmfs/volumes/datastore1/updates/ESXi550-201612001.zip --dry-run

[GoingAlone]

Thanks again jhague

I had seen something that referenced the use of the esxcli software profile update command.  Is there a way to do a dry run with this?  I take a staged approach is update each patch in the order they were released?

[a_p_]

Additional, new vibs will not be installed using the "vib update" command. You either need to install these additional vibs individually, or use the "profile updae" command, which will update currently installed vibs and install new vibs. The --dry-run option is available for the "profile update" command too.

If you are interested in getting an overview of the default vibs, and when additional vibs were introduced, take a look at https://esxi-patches.v-front.de/vm-5.5.0.html

André

[jhague]

‌Yes you should be able to use --dryrun. It should remove and replace the troublesome vib.

By staged I mean apply the patch I mentioned before first which is where that dependant vib was updated to the version it is complaining about.

[GoingAlone]

Gotchya! I found that you can add the dry run and this is what was produced. So it looks like the ehci will be removed and updated while the xhci will be installed but did not exist so it's not removed prior.

esxcli software profile update --depot /vmfs/volumes/datastore1/updates/ESXi550-201612001.zip -p ESXi-5.5.0-20161204001-standard --dry-run

Update Result

   Message: Dryrun only, host not changed. The following installers will be applied: [BootBankInstaller, LockerInstaller]

   Reboot Required: true

   VIBs Installed: VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.550.3.95.4345813, VMware_bootbank_esx-base_5.5.0-3.100.4722766, VMware_bootbank_esx-tboot_5.5.0-3.100.4722766,

VMware_bootbank_esx-ui_1.12.0-4722375, VMware_bootbank_misc-drivers_5.5.0-3.95.4345813, VMware_bootbank_sata-ahci_3.0-22vmw.550.3.89.4179633, VMware_bootbank_xhci-xhci_1.0-3vmw.550.3.95.4345813, VMware_locker_tools-light_5.5.0-3.92.4345810

   VIBs Removed: VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.550.3.78.3248547, VMware_bootbank_esx-base_5.5.0-3.78.3248547, VMware_bootbank_esx-tboot_5.5.0-2.33.2068190, VMware_bootbank_misc-drivers_5.5.0-3.78.3248547, VMware_bootbank_sata-ahci_3.0-22vmw.550.3.68.3029944, VMware_locker_tools-light_5.5.0-3.78.3248547

[GoingAlone]

So all in all, if you use the vib update (which I've used all along with no problems), run across a situation like this dependency error, you should then use the profile update instead? Maybe it's better to use profile update all the time instead?

I ran the the profile update dry run on the patch level i'm on and it comes back with installing VMware_bootbank_xhci-xhci_1.0-3vmw.550.3.78.3248547. This kind of confirms that this vib was never on my host.

Also wanted to include this link where I found helpful command lines when using the profile update option

http://thinkit.com.br/en/2016/09/22/dependencyerror-when-updating-standalone-hosts/

[jhague]

Generally speaking it's recommended to update the entire profile unless you have reason to do it in a more granular (per vib) fashion - explained really well in this blog. Are ESXi Patches Cumulative - VMware vSphere Blog - VMware Blogs

[GoingAlone]

Well, lesson learned! Should have been patching using the profile update all along.

Thanks again for all the info!

[rlee09]

Thanks for this post it resolved the issue.