VMware

VMware ESX Server 3.5 Driver CD for HP Smart Array P700m Controller

This ESX Server 3.5 driver CD includes support for version 2.4.66.84vm of the hpsa driver, which enables support for the HP Smart Array P700m controller.

For detailed information about ESX Server hardware compatibility, see the I/O Hardware Compatibility List.

Driver CD for VMware ESX Server 3.5 Update 3

Driver version: 2.4.66.84vm | 2008-12-15 | Build: 130318
Filename: esx350-hpsa-350.2.4.66.84vm-130318.iso
Md5sum: 825b906b3551112f269b5edc8e20076f

Caution:
  • This driver CD works only on ESX Server 3.5 Update 3.
  • Do not use this driver CD with ESX Server 3.5, ESX Server 3.5 Update 1, or ESX Server 3.5 Update 2.
  • After installing this driver, exercise caution when upgrading ESX Server or applying patches.

ISO File

This document contains the following sections:

Creating and Using the Driver CD

  1. Download the driver file.
  2. Check the md5sum of the downloaded file:

    md5sum esx350-hpsa-350.2.4.66.84vm-130318.iso

    where, esx350-hpsa-350.2.4.66.84vm-130318.iso is the full filename listed above. The md5 checksum output must match the md5sum listed with the filename. For example, the following command:
    md5sum esx350-hpsa-350.2.4.66.84vm-130318.iso

    results in the following output:
    825b906b3551112f269b5edc8e20076f esx350-hpsa-350.2.4.66.84vm-130318.iso

    See Verifying the integrity of downloaded installer files (KB 1537) for more information.

  3. Write the .iso image to a CD-ROM.
  4. To install ESX Server, refer the procedure detailed in the following section.

Installing ESX Server

You can use the driver CD in two different ways:

  • As a boot CD for new ESX Server installations.
  • As a driver update CD for existing ESX Server installations.

Driver CD as a Boot CD Only

The following procedure describes how to use the driver CD as a boot CD. Use this CD as a boot CD only when the new driver must enable the target device on which ESX Server 3.5 Update 3 will be installed.

  1. Place the driver CD in the CD-ROM drive of the host machine.
  2. Start the host machine.
  3. When prompted for an upgrade or installation, press Enter for graphical mode.
  4. Choose the language you prefer.
  5. Select a keyboard type.
  6. After you are prompted to swap the driver CD with the ESX Server installation CD, insert the ESX Server 3.5 Update 3 installation CD and continue with ESX Server installation.
    For detailed instructions, refer to the VI3 Installation and Upgrade Guide.
  7. After ESX Server is installed and the system reboots, log in to ESX Server.
  8. Verify that the driver is installed successfully:
    1. Run the esxupdate query command.
      A message containing the information about the driver appears.
    2. View the PCI ID XML file in the /etc/vmware/pciid/ directory.
      The driver information is available in the file.
    3. Check for the latest version of the driver module in the following directory:
      /usr/lib/vmware/vmkmod/
    4. To verify that the driver is loaded and functioning, enter vmkload_mod -l command.
      The driver is listed in the displayed list.

Driver CD as an Update CD Only

The following procedure describes how to use the driver CD to update or add the driver on an existing ESX Server 3.5 Update 3 system (for more information, refer to the Patch Management for ESX Server 3 Tech Note).

  1. Start the ESX Server machine and log in to service console as root.
  2. Place the driver CD in the CD-ROM drive of the server.
  3. Mount the driver CD.
  4. Change the directory to the VMupdates/RPMS/ on the driver CD.
  5. Run the esxupdate update command.

    Note: If the hardware is not already installed on the system, run the esxupdate command with the --noreboot option, shut down the host machine manually, install the hardware, and then boot the host machine. This allows you to install in a single boot.

    The server reboots after the driver update.
  6. Remove the driver CD from the CD-ROM drive before the system reboots.
  7. After the system reboots, log in to ESX Server.
  8. Verify that the driver is installed successfully:
    1. Run the esxupdate query command and verify that the information about the driver is mentioned in the resulting message.
    2. View the PCI ID XML file in the /etc/vmware/pciid/ directory.
      The driver information is available in the file.
    3. Check for the latest version of the driver module in
      /usr/lib/vmware/vmkmod/
    4. To verify that the driver is loaded and functioning, run the vmkload_mod -l command.
      The driver is listed in the displayed list.

Known Issues

The following issues are known to occur with hpsa driver version 2.4.66.84 in ESX Server 3.5 Update 3.

  • BusLogic Virtual SCSI Adapter Is Not Supported

    If you create virtual machines using BusLogic adapter, the system might stop functioning during path failover and display an error. The BusLogic virtual SCSI adapter is not supported for the HP Smart Array controllers such as P700m, P212, P410, P410i, and P812 in ESX Server. Virtual machines running Windows operating system and using the BusLogic virtual SCSI adapter might display an error on a blue screen, while virtual machines running Linux operating system might display I/O errors.

    Workaround
    When you create virtual machines, select the default option for adapter, the LSI Logic adapter. Do not use the legacy BusLogic virtual adapter.

  • ESX Server 3.5 Does Not Consider Referred Path Selection

    ESX Server allows you to choose and save preferred paths. In ESX Server 3.5, HP Smart Array controllers using the hpsa driver might not retain the selection of preferred path in multipath configurations.

    Workaround
    Use array-based LUN ownership settings to distribute load across controllers on each array.

  • HPSA Controller Does Not Appear In the VI Client if Logical Disks Are Not Available at Boot Time

    The HP Smart Array controller does not appear in the Storage Controllers list under the Storage Management tab in the VI Client, if the logical disks are not configured or added to the controller while starting ESX Server machine. This issue affects all ESX Server versions for all HPSA controllers (including P700m, P212, P410, P410i, and P812) using the hpsa driver.

    Workaround
    Configure and present at least one logical disk before booting the ESX Server host.
    If the ESX Server host is already started, reboot the it. The ESX Server host recognizes the new logical disks while rebooting, if they are the first logical disks configured or presented to the server.

  • Reduced LUN Capability When Operating in ESX Server Multipath Configurations

    When you use multipath configurations, if the number of LUNs visible to ESX Server is more than the maximum limit, the hpsa driver ignores excess LUNs, and displays a warning message in the /var/log/vmkernel file of the ESX Server machine. Some LUNs might also have fewer redundant paths than expected.
    The hpsa device driver used for the HP Smart Array P700m controller with the HP MSA2012sa storage array in ESX Server operating systems is limited to have a maximum of 256 LUNs. In multipath configurations, each path to a LUN is counted as a separate LUN so that multipath reduces the maximum usable LUNs per ESX Server.

    Workaround
    Reduce the number of LUNs until the product of LUNs and paths is less than 256 (LUNs * Number of paths < 256), and if necessary, reduce the LUN count until each LUN has the expected number of paths.

  • In Multipathing Configurations the Number of Paths Per LUN Is Inconsistent

    The hpsa driver in ESX Server might reduce the number of supportable LUNs below the expected maximum limit of 256 when the controller is used in multipath configurations. In multipath configurations, if all four paths are configured, the total supportable LUNs is reduced to 64. In certain multipath configurations, because each target path consumes an available LUN slot, the total number of supportable LUNs might be reduced to 60.

    Workaround
    Reduce the number of LUNs on a server until the product of LUNs and paths is less than 256 (LUNs * Number of paths < 256), and if necessary, reduce the LUN count depending on use of multipath until each LUN has the expected number of paths.
    The following example shows a configuration with the maximum supportable LUNs presented to an ESX Server installation on four paths, providing all LUNs with the expected number of usable paths:

    • Path 1: 63 LUNs seen through this path; Total LUN count (63 + 1 path) is less than 256
    • Path 2: 63 LUNs seen through this path; Total LUN count (63 + 63 + 2 paths) is less than 256
    • Path 3: 63 LUNs seen through this path; Total LUN count (63 + 63 + 63 + 3 paths) is less than 256
    • Path 4: 63 LUNs seen through this path; Total LUN count (63 + 63 + 63 + 63 + 4 paths) = 256