Monday, January 19, 2015

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


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):
  1. Log in to the ESX service console or locally to the ESXi host.
  2. At 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.
  1. Log in to the ESX service console or locally to the ESXi host.
  2. At 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:

  1. Log in to the ESX service console.
  2. At 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: 

  1. Log in to the ESX service console.
  2. At 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:

  1. Log in to the ESX host using the VI Client.
  2. 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:

  1. Download the patch bundle zip files as described in the patch bundle installation instructions.
  2. 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
  3. At 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:

  1. Log in to the ESX Server service console.
  2. At 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.

  1. Log in to the ESX Server service console.

    At 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:
  1. Open the PowerCLI command prompt.
  2. 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.
  3. 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:

  1. Log in locally to the ESXi host.
  2. At the command prompt, run the command:

    #esxcli software vib list
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001179

To determine the base build number of an ESX Server 3.5.x or 3.0.x host (the build number of the original installation):
1. Log in to the ESX Server Service Console.
2. At the command prompt issue the following command:
#esxupdate query
The base build number and version of the base installation on the ESX Server host will be displayed on the first line of the query output. Lines of the format x.y.z-<number> provide the VMware ESX Server software version number and build number. Additional lines in the output indicate the names and of patches that might have been applied after the original installation. Typical output will resemble the following:
  
 ------ Name ------ --- Install Date --- --- Summary --- 3.0.2-52542 16:35:05 11/29/07 Full 3.0.2 release of VMware ESX Server ESX-1001725 12:28:31 11/30/07 Security update for the bind package.
In this example, 52542 is the base build number of the original installation of ESX Server 3.0.2 and ESX-1001725 is the name of a patch that was subsequently applied to the host. In some cases, running the command esxupdate query will result in multiple lines of output. When contacting VMware technical support, supply both build numbers when asked for a base build number. In the following output, both 52542 and 61618 should be reported:
 ------ Name ------ --- Install Date --- --- Summary --- 3.0.2-52542 13:43:10 11/29/07 Full 3.0.2 release of VMware ESX Server 3.0.2-61618 14:27:16 11/29/07 3.0.2 Update 1 of VMware ESX Server
To view the build number of all components as they were originally installed with ESX Server 3.0.1 or ESX Server 3.0.0:
1. Log in to the ESX Server Service Console .
2. At the command prompt use one of the following:
    • For ESX Server 3.0.0, type esxupdate -l info 3.0.0-27701 and press Enter.
    • For ESX Server 3.0.1, type esxupdate -l info 3.0.1-32039 and press Enter.
    • For ESX Server 3.0.2, type esxupdate -l info 3.0.1-52542 and press Enter.
    • For ESX Server 3.5, type esxupdate -l info 3.5.0-64607 and press Enter.
The utililty will list all rpms that were installed with the release and provide version information.
To view the build numbers of all rpms currently installed on the ESX Server 3.5.x or 3.0.x host :
1. Log in to the ESX Server Service Console .
2. At the command prompt type:
rpm -qa VMware-\*
This method reports build numbers for all ESX Server components (rpms) including VMX, host agent, VMkernel, drivers, and so on.
To view the current build number of the VMX component of the ESX 3.5 or 3.0.x Server installation:
1. Log in to the ESX Server Service Console .
2. At the command prompt type vmware –v and press Enter.
To view the current build number of the 3.5 or 3.0.x host agent component:
1. Log into the ESX Server host through the VI Client.
2. Choose Help > About.
To view the build numbers of rpms contained in a patch bundle before it is installed:
1. Download and untar a patch bundle as described in the patch's installation instructions.
2. 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
3. Change to the directory of the patch you would like to examine. For example:
cd ESX-<xxx>
Where <xxx> is the patch number.
4. In the patch directory, type:
esxupdate -l info
To view the build numbers of rpms contained in a patch bundle after it is installed:
1. Log in to the ESX Server Service Console .
2. At the command prompt type:
esxupdate -l info ESX-<xxx>
Where <xxx> is the patch number you would like to examine.


http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1014508
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)