Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Determining detailed build number information for VMware hosts (1012514)

Last Updated: 3/31/2015Categories: How toTotal Views: 205220Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Details

In some cases, after patches have been installed on an ESX host, different build numbers are reported for different components. This article provides details of the build information for 4.0.x and newer hosts.

For information on ESX 3.0x or ESX 3.5.x hosts, see Determining detailed build number information for VMware ESX 3.0.x and 3.5.x hosts (1001179).

Solution

VMware ESX hosts are patched according to a model where each patch bundle only updates a few components of the ESX installation at a time. Not all components of the installation are upgraded during each patch installation. When a patch is applied, the build number of the updated components changes. As a result, the ESX installation can have different components at different build numbers, depending upon which patch bundles have been applied.

You can view the build number for different components of upgraded versions of ESX 4.0.x. This article provides instructions on how to determine the build number of:

The system level

The build number

The patches applied to the host

The currently installed RPMs

The host agent component

RPMs and VIBs in patches before installation

RPMs and VIBs in patches after installation

RPM in a specific bulletin

For more information on how to determine the build number of other VMware products, see Determining VMware Software Version and Build Number (392).

To determine the system level of a host:

Note: This displays the build number of the latest update applied (for example, ESX 4.0.0 Update 1):

Log in to the ESX service console or locally to the ESXi host.

In the command prompt, run the command:

#vmware -l

You see an output similar to:

#VMware ESX 4.0.0 Update 1

The system level base installation of the ESX host will be displayed in the query output. This is the system level with no updates applied.

To determine the build number of a host:

Note: This displays the build number of ESX. The build number for ESX changes for any GA (general availability) or update release (like ESX 4.0 Update 1). Because patch releases do not deliver a vmware-esx-vmware-release rpm, they do not affect the build number displayed by vmware -v.

Log in to the ESX service console or locally to the ESXi host.

In the command prompt, run the command:

#vmware -v

You see an output similar to:

#VMware ESX 4.0.0 build-208167

To determine the patches or updates applied on the ESX host:

Log in to the ESX service console.

In the command prompt, run the command:

#esxupdate query

Lines in the output indicate the names and of patches that might have been applied after the original installation. Typical output is similar to:

----Bulletin ID---- -----Installed----- -------------Summary-------------
ESX400-200906401-BG 2009-07-08T18:02:49 Updates VMX
ESX400-200906412-BG 2009-07-08T18:02:49 Updates esxupdate
ESX400-200906404-BG 2009-07-08T18:02:49 Updates CIM

To view the build numbers of all RPMs currently installed on the ESX host:

Log in to the ESX service console.

In the command prompt, type:

rpm -qa | grep -i vmware

This method reports build numbers for all ESX components (RPMs) including VMX, host agent, VMkernel, drivers, and so on.

To view the current build number of the host agent component:

Log in to the ESX host using the VI Client.

Choose Help > About Vmware vSphere

Note: In ESX 4.0, the packages are called VIBs (vSphere Installation Bundle). The VIB name contains details about the RPMs, including the versions.

To view the build numbers of RPMs and VIB details contained in a patch bundle before it is installed:

Download the patch bundle zip files as described in the patch bundle installation instructions.

Before installing the patch, change to the directory that you use as your esxupdate repository. For example, if your repository is located at /var/updates, type:

#cd /var/updates

In the command prompt, type:

#esxupdate --bundle patchbundlename.zip info

Where patchbundlename represents the name of patch bundle.

To view the build numbers of RPMs and VIB details contained in a patch bundle after it is installed:

Log in to the ESX Server service console.

In the command prompt, type:

# esxupdate info

This command lists all the VIBs.

To view the build numbers of RPMs in a specific bulletin contained in a patch bundle after it is installed:

Log in to the ESX Server service console.

In the command prompt, type:

# esxupdate info -b bulletinname

Where bulletinname represents the name of the bulletin you are reviewing, such as ESX400-200906413-BG.

Sample output for the command: esxupdate info -b bulletinname:

Id

- ESX400-200906413-BG

Releasedate

- 2009-07-09T00:00:00-08:00

Vendor

- VMware, Inc.

Summary

- Updates vmkernel iSCSI Driver

Severity

- critical

Category

- critical

Installdate

- 2009-07-02T16:25:56.709691+05:30

Description

- This patch fixes an issue where iSCSI targets might disappear during controller fault or failover of an EqualLogic array. Currently, this issue has only been observed on EQL hardware. However it might not be specific to EQL arrays. Please see http://kb.vmware.com/kb/1012232 for more details

Kburl

-http://kb.vmware.com/kb/1012232

List of constituent VIBs:

-rpm_vmware-esx-iscsi_4.0.0-0.5.175625@i386
rpm_vmware-hostd-esx_4.0.0-0.5.175625@i386

Another method of finding out the information above is using vSphere PowerCLI.

To determine the system level and build number of an ESX 4.0 host using PowerCLI:

Open the PowerCLI command prompt.

Connect to the ESX or ESXi host which reported the warning using the command:

Connect-VIServer -Server ESXHostnameOrIPAddress

Note: Authenticate using an administrative user, such as root.

Run this command:

get-view -ViewType HostSystem -Property Name, Config.Product | select Name,{$_.Config.Product.FullName},{$_.Config.Product.Build} | ft -auto

To determine the patches or updates applied on the host, run this command:

Get-VMHost hostname | Get-VMHostPatch | Select Id,InstallDate,Description | ft -auto

For more information about esxupdate commands in vCLI, see the vSphere Command-Line Interface Reference.

To determine the patches or updates applied on the ESXi host:

Log in locally to the ESXi host.

In the command prompt, run the command:

#esxcli software vib list

Note: For more information, see Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508).

Additional Information
For translated versions of this article, see:

Español:

Português:

日本語: VMware ESX ホストの詳しいビルド番号情報を判断する (2083805)

简体中文: 确定 VMware 主机的详细内部版本号信息 (2088016)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant