VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts)
5 Replies Last post: Nov 12, 2009 7:50 AM by ajesha008  

ESX buildnumber is not reflected in the vi client posted: Nov 3, 2009 8:53 AM

Click to view Timothy@Corismo's profile Enthusiast 34 posts since
Aug 6, 2008

Hi all,

I just updated 3 ESX 4.0 hosts with the latest patches found on https://www.vmware.com/mysupport/download/ . I installed them manually on all hosts via the esxupdate scan|stage|update command. The updates were all succesfully applied. After the 3 updates the buildnumber is reflected in /proc/vmware/version. However if I log on the vCenter server or directly , I see a buildnumber 175625 which should be 193498 (or at least this is the vmkernel release in /proc/vmware/version). Executing vmware -v shows yet another buildnumber namely 171294.

There doesn't seem to be a problem with the patches. However in the future we plan to use vmware update manager in vSphere. What if the version number are not properly interpreted by this tool and it will try to update the host without this being needed?!

Thanks for helping out!

Timothy

Click to view AndreTheGiant's profile Guru 7,590 posts since
Aug 28, 2008
Click to view Troy Clavell's profile Guru vExpert 7,244 posts since
Oct 12, 2007
Click to view Poort443's profile Enthusiast 53 posts since
Mar 12, 2009
I have more or less the same issue, but I doubt it's normal behaviour. My buildnumber is 164009, while it should be 193498. This last number is only in /proc/vmware/version. I checked that all the patches in between are actually installed. I found I had this issue while working with VMware support trying to resolve another issue. They asked me to install the missing patches. If VMware support doesn't know about this, I don't think this is by design. I'm still looking into this trying to find a way to get the right buildnumber in vCenter.
Click to view ajesha008's profile Novice 10 posts since
Oct 22, 2009
Even I have the similar issue
Initially my Build No. is ESX 3.5.0, 163429 but even after applying 91 patches using VUM it shows the same build No. in vSphere Client, Im yet to check this in ESX directly.

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities