ESXi patch 4 needed when updating using IBM Director - IBM System x, BladeCenter



Source

RETAIN tip: H207140

Symptom

An update may fail when IBM Director attempts to perform a firmware update on VMware ESXi.

Affected configurations

The system is configured with at least one of the following:

  • VMware vSphere Hypervisor 5.0 with IBM Customization Installable Base Install, Update 1
  • VMware vSphere Hypervisor 5.1 with IBM Customization Installable, any Update

This tip is not system specific.

This tip is not option specific.

Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Please see the compatibility page for more information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/

Solution

When the failure is encountered, one of the following two options should be performed:

Option 1:

  1. Apply the VMware vSphere ESXi 5.0 with IBM Customization Patch 4 from IBM FixCentral using VMware Update Manager by following the instructions in the document "Reconfiguring VMware vSphere Update Manager" at this URL:

    http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-update-manager-51-reconfig-guide.pdf

  2. After the system has been rebooted allow the IBM CIM providers to complete the initialization and loading process before continuing. This process can take up to 20 minutes. This will be fixed in a patch release in 1H2013.

Option 2:

Update using the CLI:

  1. Download the latest patch and unzip the contents. This will include the patch, source, and licenses.

  2. Copy the .zip file from the expanded contents to any folder on ESXi, for example, '/tmp/.'

  3. Run command esxcli software vib install -d /tmp/XXXXX.zip

    Note: The path must be full path.

  4. Check the running result, the installation should be successful.

  5. Reboot the system.

  6. Check the version of 'concretejob,' 'filetrans,' 'immpassthru,' and 'fwupdate.' They should be updated to version 500-2ACE16AUS.

  7. If the affected machine is an IBM PureFlex, the IMM version must be later than 27L, but non-PureFlex versions must be later than 27M.

  8. After the system has been rebooted, allow the IBM CIM providers to complete the initialization and loading process before continuing. This process can take up to 20 minutes. This will be fixed in a patch release in 1H2013.

IBM Director then can be used to perform firmware updates.

Additional information

VMwware periodically deletes the folder under the '/tmp' directory that houses the firmware updates that IBM Director deploys to the ESXi system to update.

Applicable countries and regions

 


Document id:  MIGR-5092003
Last modified:  2012-12-07
Copyright © 2014 IBM Corporation