bogun.netlify.app

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience. Mcgraw hill ryerson chemistry 11.

This release supports the Generation 2 versions of the IO Accelerator for BladeSystem c-Class and ProLiant servers, which includes the following models:

• QK761A, 365 GB MLC IO Accelerator for BladeSystem c-Class
• QK762A, 785 GB MLC IO Accelerator for BladeSystem c-Class
• QK763A, 1205 GB MLC IO Accelerator for BladeSystem c-Class
• 673642-B21 365 GB MLC IO Accelerator Gen2 for ProLiant
• 673644-B21 785 GB MLC IO Accelerator Gen2 for ProLiant
• 673646-B21 1205 GB MLC IO Accelerator Gen2 for ProLiant
• 673648-B21 2410 GB MLC IO Accelerator Gen2 Duo for ProLiant
• 721458-B21 3.0TB MLC IO Accelerator Gen2 for ProLiant
• 740320-B21 1.6TB MLC IO Accelerator ioScale2 for Proliant
• 740322-B21 3.2TB MLC IO Accelerator ioScale2 for Proliant

This release also provides a one-way upgrade path for Generation 1 IO Accelerators for HP BladeSystem c-Class G1-G7 servers, and ProLiant servers which include the following models:

• 600278-B21 160 GB SLC IO Accelerator Gen1 for ProLiant
• 600279-B21 320 GB SLC IO Accelerator Gen1 Duo for ProLiant
• 600281-B21 320 GB MLC IO Accelerator Gen1 for ProLiant
• 600282-B21 640 GB MLC IO Accelerator Gen1 Duo for ProLiant
• 641027-B21 1280 GB MLC IO Accelerator Gen1 Duo for ProLiant

Prerequisites:

Important Upgrade Notes:

• Upgrade Path: Depending on the current firmware version of the IO Accelerator, multiple firmware updates may be required to preserve internal structures. The minimum path is:
  • 1.2.4>1.2.7>2.2.0> 2.2.3->3.x.x
• Version 3.2.2 is the preferred upgrade path from version 2.x.x, allowing customers to obtain the latest software.
  • However, the upgrade from version 2.x.x to version 3.x.x requires a reformat of the HP IO Accelerator, erasing all user data on the device in the upgrade process.
  • A backup of all data on the HP IO Accelerator is mandatory before installing version 3.x.x
• Version 2.3.10 (Generation 1 HP IO Accelerator cards only) is recommended only for customers who have an installed base of HP IO Accelerators, which are running version 2.x.x of the install package, and choose not to upgrade to 3.x.x but still want the features of version 2.3.10.
• Existing cards will require a firmware upgrade to all cards in the server. You must manually update the firmware. (See the Firmware Update Procedure in the Installation section).
• Existing IO Accelerators configured with version 2.x.x must be upgraded before installing new 3.x.x IO Accelerator devices in the system.
• You must first uninstall any previous version before installing this software. See the procedure in the Installation section or review the installation notes which are included in the HP IO Accelerator User Guide.
• Back up all important data to a local disk or an externally attached volume. Do not back up to another IO Accelerator within the same system.
• Before upgrading, run a fio-bugreport command-line utility and save the output. This will capture device information for each device in the system.
• Before installing the IO Accelerator software, stop all virtual machines and put the ESXi host into maintenance mode (using vSphere client or vCLI).
• The offline bundle may be within a .zip archive. Unpack the offline bundle for installation.
• Install the HP IO Accelerator hardware using the steps in the IO Accelerator User Guide or included Fusion IO documentation. To locate the User Guide, please go to http://www.hp.com/ or http://www.hp.com/go/ioaccelerator and enter 'HPIOAcceleratorUserGuide' in the search field.


• vCLI Installation Overview
  In order to install and manage the IO Accelerator software and driver, you may install vCLI (vSphere Command-Line Interface) to run against your ESXi system. You should install a vCLI package on a physical machine running Linux or Windows. For more information on VMware's vCLI, see http://www.vmware.com/support/developer/vcli/ .
  NOTE: HP does not recommend using the vCLI on a virtual machine that is hosted on your ESXi system. The IO Accelerator installation and configuration processes involve putting the ESXi host into maintenance mode.
• A command line interface can also be used to install the IO Accelerator provided the user has access to the ESXi host server.

IO Accelerator Management Interface

ioSphere 3.9.0 is the latest ioDrive management interface and is included as a seperate download ioSphere_3.9-ESXi-5x.zip, in this release. it is recommended for use with 3.2.8 and later VSL versions.

• Unzip and extract the files in ioSphere_3.9-ESXi-5x.zip into a common directory

• Locate the document Fusion-io_ioSphere_3.9.0_Installation_Guide_2014-06-11.pdf

• Install the management interface using the instructions in the guide

To ensure the integrity of your download, HP recommends verifying your results with the following MD5 Checksum values:

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.

Installation:

The following information is provided as a basic guide for installation. See the IO Accelerator user guide for more information.
VSL package: VSL328-ESXi5.zip

VERSION 3.2.8 File
Firmware file: ioaccelerator_3.2.8-20140508.fff
FW Version: 7.1.17.116786
Software Installation Overview:

1. Ensure the prerequisites have been satisfied before proceeding.
2. If needed, uninstall previous versions of the IO Accelerator driver, software and the utilities. Instructions for uninstalling current and previous versions of the driver are available below and also in the User guide.
3. Download the latest version of the IO Accelerator software and the driver command-line utilities to a remote machine.
4. Transfer the files to the target system using vCLI, VSphere or SCP (using SSH).
5. Install the software.
6. Reboot the ESXi system; this will load the driver and attach the IO Accelerator device(s).
7. Upgrade the firmware to the latest version if needed. See the Firmware Update section for more information.
   firmware file = <filename>.fff
8. Configure the IO Accelerator to support VM Disks.

I. Downloading the VMware ESXi Driver and support files:

1. Download the installation package to a remote machine running the vCLI or vSphere client.
2. Unzip the package. The IO Accelerator is available as an offline bundle. The files contained are:
   • scsi-iomemory-vsl-5X-3.2.8.1350-offline_bundle-1816421.zip [required driver and utilities]
   • ioaccelerator_3.2.8-20140508.fff [required - firmware file]
   • Documentation
3. Download and unzip the remote utilities package if installing from a remote Linux machine (optional).
   1. Install the rpm for the specific Linux distribution.
      • Example: fio-remote-util-<version>.x86_64.rpm
        Note: install the fio-remote-util for the appropriate Linux distribution on the remote machine.

II. Transfer the files to the ESXi server
Note: HP recommends saving the file(s) to a datastore on the host.
Example:. /vmfs/volumes/<datastore>/bundles, where <datastore> is the name of the datastore.
Transfer methods:

• vSphere Client
• vCLI vifs command
• SCP/WinSCP (using SSH)

Transfer all the files to the datastore using one of the above methods.
At the end of the transfer, /vmfs/volumes/datastore1/bundles will contain:

• scsi-iomemory-vsl-5X-3.2.8.1350-offline_bundle-1816421.zip
• ioaccelerator_3.2.8-20150508.fff

III. Install the IO Accelerator driver (command line)
Note: The VMware Update Manager (VUM) plug-in for Virtual Center Server may be used to install the IO Accelerator software on multiple hosts. Please see the vCenter Server documentation for more details on VUM.
To install the IO Accelerator driver and utilities, run the following commands against your ESXi system.

1. Ensure prerequisites are satisfied and the system is in maintenance mode.
2. SSH/login to the host system.
3. Install the IO Accelerator driver and utilities.
   • # esxcli software vib install -d <path>/<offline-bundle>.zip
     • the <offline-bundle> is the full path name of the offline bundle zip file on the hypervisor host.
     • the utilities are installed as part of this vib.
4. Reboot the ESXi host system.
5. To install the CIM provider (optional), run the following command:
   1. esxcli software vib install -d <cimprovider-bundle> -- no-sig-check
   2. cimprovider-bundle is the cimprovider zip file

• Ensure the firmware is up-to-date.
• Run fio-status from the host shell and look for the Firmware line, e.g. Firmware v6.0.0, rev 108609 Public
  • The firmware should be version 108609. All of these versions are in the ioaccelerator_108609_1.fff archive file.
• If the firmware is not up-to-date or the output shows the device is running in minimal mode, the firmware will need to be updated.

Upgrading the firmware:

1. Ensure the prerequisites are met, specifically
   • If the device was previously using IO Accelerator software 2.x or earlier, please upgrade to each release according to the prerequisites.
   • Ensure existing IO Accelerators are updated before installing new ones.
   • the host system is in maintenance/Tech Support mode.
2. Ensure the firmware is on the ESXi host. If not, download the firmware and place the firmware onto the ESXi host (make note of the firmware location).
3. SSH into the host CLI, navigate to the directory that contains the firmware, and perform the upgrade:
   • fio-update-iodrive [-f -d <device-name>] <firmwarefile.fff>.
   • For example: fio-update-iodrive ioaccelerator_108609_1.fff or to force the upgrade fio-update-iodrive -f -d /dev/fct0 ioaccelerator_108609_1.fff
     NOTE: The firmware update process is expected to take significant time and may appear that the process is hung, but let it continue.
4. Reboot the host.
5. Verify the firmware version. Ensure the device does not have any warnings or is in minimal mode.
   1. For upgrades from 2.x to 3.x, perform the following additional steps:
      • Important Note: If upgrading from a 2.x version, the device will be in minimal mode and will warn that the upgraded devices are missing a lebmap. This is expected and will be resolved with the fio-format command.
      • WARNING: fio-format will erase the entire device including user data. Once the format is started, the device cannot be downgraded to a 2.x firmware version. Ensure data is backed up before proceeding.
      • Format each device.
        • fio-format <device>, e.g. fio-format /dev/fct0
      • Attach all IO Accelerator devices by running fio-attach for each device, for example:
        • fio-attach /dev/fct1
      • Check the status of all devices using fio-status
6. [AJ878B and BK836A products] Verify the powerloss protection is detected on AJ878B and BK836A units using the fio-status command.
   • >> Powerloss protection: protected.
     • If it does not show protected, ensure the remote power cap module is installed for each IO Accelerator device.

V. Uninstalling the IO Accelerator Software Package and Command-line Utilities
ESXi 5.0 uninstall command:esxcli [--server <servername>] software vib remove -n block-iomemory-vsl

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Important:

This software package contains the operating system driver, utilities, and firmware for the HP IO Accelerator products for VMware ESXi 5.x.

• The IO Accelerator devices cannot be installed as part of an ESX installation. It must be installed on an existing ESXi host system.
• An update/upgrade installation is not recommended. Instead uninstall the previous version of the IO Accelerator software before you install this version.
• A command-line interface is required to install the software. Options are vCLI or SSH/Shell.
• A command-line interface is needed to manage the device using the IO Accelerator utilities. The SMI-S Python scripts or the Tech Support Mode (TSM) can be used. See the VMware article on using the TSM: http://kb.vmware.com/kb/1017910
• The fio-remote-utilities require Python 2.6 and PyWBEM 0.7 installed on your remote machine. Consult your distribution documentation for instructions on how to install them.

WARNING:
If this is an upgrade from a IO Accelerator 2.x.x version to IO Accelerator 3.x.x, the update process will require a low-level media format (fio-format) of the device. No user data will be maintained during this process; be sure to make a complete backup.
Also, be sure to use the upgrade path listed in the Prerequisites section.

Known issues:

• It is mandatory that 365GB and 785GB ioDrive2 PCIe stand-up and mezzanine cards be upgraded to 3.1.5/108609 or later 3.x.x version.
• It recommended that all other Generation 1 and 2 stand-up and mezzanine cards upgrade to 3.1.5/108609 or later 3.x.x version as soon as possible.
• Using an IO Accelerator as an ESX CoreDump target is not supported.
• Using an IO Accelerator device as a boot device is not supported.
• There is no IO Accelerator manager for ESXi 5.x. This is a future enhancement
• There is no SNMP agent or SMI-s/CIM provider in this release. This is a future enhancement.
• The fio-status and ioManager utilities may show slot number as unavailable on some servers. This is a known issue and will be fixed in a future release.
• On the Blade mezzanine IO Accelerator for the AJ876A, AJ877A, and the AJ878A products, fio-status –a will show
  • PCIE slot available power: unavailable
  • External Power: NOT connected

PCIe slot available power and external power available fields do not apply for the c-Class blade mezzanine IO Accelerator. Sufficient power is provided to the IO Accelerator. This note will be updated in a future release.

Notes:
For the AJ878B and BK836A models, ensure the remote power cut module is installed.

• To verify the remote power cut module is installed on these models, type the command
  • # fio-status -a
    On each HP IO Accelerator, look for Powerloss: protected
    If any other messages appear for the Powerloss field, ensure the remote power cut module is installed.

• The AJ876, AJ878A, and AJ878A models do not contain the remote power cut module and will display: Powerloss: not available
• The QK761A, QK762A, and QK763A have the power cut function built into the product will display: Powerloss:protected

Supported Devices and Features:

HP IO Accelerators for BladeSystem c-Class are designed for two form factors.

• Generation 1 HP IO Accelerators use a Type 1 form factor for HP ProLiant G1-G7 BladeSystem c-Class Servers.
  • Includes IO Accelerator product with part numbers of AJ876A, AJ877A, AJ878A, AJ878B, BK836A
  • Supports either the 2.x.x or the 3.x.x versions of the IO Accelerator software.
  • Is not compatible with HP ProLiant Gen8 BladeSystem c-Class servers.
• Generation 2 HP IO Accelerator use a Type B form factor for HP ProLiant Gen8 BladeSystem c-Class Servers
  • Includes IO Accelerator product with part numbers of QK761A, QK762A, and QK763A
  • Requires IO Accelerator Software version 3.1.1 or greater
  • Is not compatible with HP ProLiant G1-G7 BladeSystem c-Class servers.

HP IO Accelerators for ProLiant Servers.

• Generation 1 HP IO Accelerators for HP ProLiant Servers.
  • Includes IO Accelerator product with part numbers of 600278-B21, 600279-B21, 600280-B21, 600281-B21, 641027-B21
  • Supports either the 2.x.x or the 3.x.x versions of the IO Accelerator software.
  • Is compatible with supported HP ProLiant G6-Gen8 servers
• Generation 2 HP IO Accelerators for HP ProLiant Servers.
  • Includes IO Accelerator product with part numbers of 673642-B21, 673644-B21, 673646-B21, 673648-B21, 721458-B21, 740320-B21, 740322-B21
  • Supports the 3.x.x versions of the IO Accelerator software.
  • Is compatible with supported HP ProLiant G6-Gen8 servers

IO Accelerator Software version 3.2.8 supports the following Operating Systems:

• Microsoft Windows Server 2012 x64
• Microsoft Windows Server 2008 x64, R2
• Red Hat Enterprise Linux 5, 6 (AMD64/EM64T)
• SUSE Linux Enterprise Server (SLES) 11 (AMD64/EM64T)
• VMware ESXi 5.1/5.5
• OEL 5, 6
• CentOS 5, 6
• Solaris 11
• Ubuntu 12

This software package contains the operating system driver, utilities, and firmware for the HP IO Accelerator products for VMware ESXi 5.x.

• The IO Accelerator devices cannot be installed as part of an ESX installation. It must be installed on an existing ESXi host system.
• An update/upgrade installation is not recommended. Instead uninstall the previous version of the IO Accelerator software before you install this version.
• A command-line interface is required to install the software. Options are vCLI or SSH/Shell.
• A command-line interface is needed to manage the device using the IO Accelerator utilities. The SMI-S Python scripts or the Tech Support Mode (TSM) can be used. See the VMware article on using the TSM: http://kb.vmware.com/kb/1017910
• The fio-remote-utilities require Python 2.6 and PyWBEM 0.7 installed on your remote machine. Consult your distribution documentation for instructions on how to install them.

WARNING:
If this is an upgrade from a IO Accelerator 2.x.x version to IO Accelerator 3.x.x, the update process will require a low-level media format (fio-format) of the device. No user data will be maintained during this process; be sure to make a complete backup.
Also, be sure to use the upgrade path listed in the Prerequisites section.

Known issues:

• It is mandatory that 365GB and 785GB ioDrive2 PCIe stand-up and mezzanine cards be upgraded to 3.1.5/108609 or later 3.x.x version.
• It recommended that all other Generation 1 and 2 stand-up and mezzanine cards upgrade to 3.1.5/108609 or later 3.x.x version as soon as possible.
• Using an IO Accelerator as an ESX CoreDump target is not supported.
• Using an IO Accelerator device as a boot device is not supported.
• There is no IO Accelerator manager for ESXi 5.x. This is a future enhancement
• There is no SNMP agent or SMI-s/CIM provider in this release. This is a future enhancement.
• The fio-status and ioManager utilities may show slot number as unavailable on some servers. This is a known issue and will be fixed in a future release.
• On the Blade mezzanine IO Accelerator for the AJ876A, AJ877A, and the AJ878A products, fio-status –a will show
  • PCIE slot available power: unavailable
  • External Power: NOT connected

PCIe slot available power and external power available fields do not apply for the c-Class blade mezzanine IO Accelerator. Sufficient power is provided to the IO Accelerator. This note will be updated in a future release.