VMware Cloud Community
The-Kevster
Contributor
Contributor

ESX Server shows 175625 even after updates?

I've just installed the last two batches of update bundes ESX400-200907001 and ESX400-200909001 but my ESX version in the vSphere client is still showing 175625 but according to the patches website it should show 193498. Here is the two commands I used to update the server which were successful.

esxupdate --bundle=https://hostupdate.vmware.com/software/VUM/OFFLINE/release-125-20090806-741959/ESX400-200907001.zip update

esxupdate --bundle=https://hostupdate.vmware.com/software/VUM/OFFLINE/release-150-20090917-796862/ESX400-200909001.zip update

And here's the output of an esxupdate query showing the update have installed successfully.

# esxupdate query

-


Bulletin ID---- -


Installed--- -


Summary--


ESX400-200906412-BG 2009-07-11T17:20:54 Updates esxupdate

ESX400-200906405-SG 2009-07-11T17:20:54 Updates krb5 and pam_krb5

ESX400-200906406-SG 2009-07-11T17:20:54 Updates sudo

ESX400-200906402-BG 2009-07-11T17:20:54 Updates ESX Scripts

ESX400-200906407-SG 2009-07-11T17:20:54 Updates curl

ESX400-200906404-BG 2009-07-11T17:20:54 Updates CIM

ESX400-200906408-BG 2009-07-11T17:20:54 Updates SCSI Driver for QLogic FC

ESX400-200906409-BG 2009-07-11T17:20:54 Updates LSI storelib Library

ESX400-200906411-SG 2009-07-11T17:20:54 Updates udev

ESX400-200906413-BG 2009-07-11T17:20:54 Updates vmkernel iSCSI Driver

ESX400-200907401-BG 2009-09-26T09:45:32 Updates vmklinux and vmkernel64

ESX400-200909404-BG 2009-09-26T09:51:35 Updates ixgbe

ESX400-200909401-BG 2009-09-26T09:51:35 Updates vmx and vmkernel64

ESX400-200909403-BG 2009-09-26T09:51:35 Updates bnx2x

ESX400-200909402-BG 2009-09-26T09:51:35 Updates VMware Tools

ESX400-200909406-BG 2009-09-26T09:51:35 Updates hpsa

ESX400-200909405-BG 2009-09-26T09:51:35 Updates perftools

Is this how it should look or has the update not succeeded? Thanks!

0 Kudos
6 Replies
AndreTheGiant
Immortal
Immortal

I've have the same built number (175625) after a manual upgrade (using zip files).

But seems ok, and also VUM say that hosts are compliant.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Brechreiz
Contributor
Contributor

I think the Problem is since update 18xxx. I updated my 2 ESX 4.0 Host with the latest patches and they show in Console Window Build 193498, but vcenter reports 175625. This was also the case with the former version 18xxx.

0 Kudos
Saju_C
VMware Employee
VMware Employee

Hi

Please refer the following KB

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101251...

The build number at server console is the version of the Vmware Kernel

The build number which you see at vSphere Client is the hostagent version number

So

after installing the latest patches your server console would show

193498, vSphere Client would show 175625. If you have installed patches

released on 08/06, then the console would show 181792 and vSphere

client would show 175625.

Thanks

CS

0 Kudos
Brechreiz
Contributor
Contributor

This answers my question. Thanks.

0 Kudos
vmwaredownload
Enthusiast
Enthusiast

were you able to upgrade to update 1??

0 Kudos
rjtd
Contributor
Contributor

I had the same problem.

If you use the vihostupdate utility (from vCLI) it should detect a conflict.

Only way I could get out with it was to backup my ESX configs, then revert to my alt bootbank and proceed with the update.

No errors were shown after that, and my vi-client and console show the same version.

0 Kudos