HP PCIe IO Accelerator for ProLiant Servers User Guide Part Number 607720-002 November 2010 (Second Edition)
© Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software.
Contents About this guide ........................................................................................................................... 7 Contents summary ..................................................................................................................................... 7 Introduction .................................................................................................................................. 8 Overview ...................................................
Manual installation on Windows Server ..................................................................................................... 45 Manual installation on Windows Server 2003 .................................................................................. 46 Manual installation on Windows Server 2008 .................................................................................. 47 Upgrading the device firmware using Windows ...................................................................
Device Tree ............................................................................................................................................ 71 Drive status ................................................................................................................................... 72 Device Report panel ................................................................................................................................ 75 Saving IO Accelerator information ......................
Using Windows page files with the IO Accelerator ....................................................................... 108 Introduction to Windows page files ......................................................................................................... 108 Configuring IO Accelerator paging support .............................................................................................. 108 RAM consumption .....................................................................................
About this guide Contents summary • Installing the IO Accelerator • Downloading and installing the approved driver and utilities • Maintaining the IO Accelerator • Description of the following IO Accelerator models: o HP PCIe IO Accelerator o HP PCIe IO Accelerator Duo This user guide is intended for IO Accelerator software release 2.1 or later. For version 1.2.7.x, see the previous version of this user guide.
Introduction Overview Designed around ioMemory, a revolutionary storage architecture, HP PCIe IO Accelerator is an advanced NAND flash storage device. With performance comparable to DRAM and storage capacity on par with hard disks, PCIe IO Accelerator increases performance so that every server can contain internal storage that exceeds the I/O performance of an enterprise SAN. PCIe IO Accelerator is the first data accelerator designed specifically to improve the bandwidth for I/Obound applications.
IO Accelerator Duo capacity 320GB 640GB 512B packet size) packet size) Access latency 26 μs (read) 29 μs (read) *Performance achieved using multiprocessor enterprise server • Enterprise data integrity • Field upgradeability • Green footprint, 7.5 watts nominal per device NOTE: MSI was disabled to obtain these statistics.
Supported firmware revisions Release Firmware revision 1.2.4 17350 1.2.7 36867 or 42014 1.2.8.4 43246 2.2 43674 Supported hardware NOTE: ESX supports a maximum of five IO Accelerators or two IO Accelerator Duos per system. HP PCIe IO Accelerator minimum requirements: • An open PCI-Express slot—The accelerator requires a minimum of one half-length, half-height slot with an x4 physical connector. All four lanes must be connected for full performance.
* The fio-format utility automatically formats the device to this block size unless specified differently. You can reduce memory use by selecting a 4K sector size, forcing the average written block size to be 4K or greater. For most systems, even when formatted with 512 byte sectors, actual memory use typically tracks 4K or greater average I/O size. The HP IO Accelerator Duo requires a PCIe Gen1 x8 slot or a PCIe Gen2 x4 slot.
Hardware installation Installing the HP PCIe IO Accelerator WARNING: To reduce the risk of personal injury or damage to the equipment, consult the safety information and user documentation provided with the server before attempting the installation. Many servers are capable of providing energy levels that are considered hazardous and are intended to be serviced only by qualified personnel who have been trained to deal with these hazards.
6. If applicable, remove the cover slot.
7. Grasp the PCIe IO Accelerator by the top edge and insert it gently, but firmly, into the available PCIe slot.
8. Secure the PCIe IO Accelerator retaining bracket using a screw or lever (depending on how your hardware is configured). 9. Replace the server access panel. 10. Plug in the power cable. 11. Power on the server. If your operating system detects the PCIe IO Accelerator and prompts you to install a driver for the device, click Cancel. 12. Install the driver and utilities software.
1. Locate the half-height bracket in your PCIe IO Accelerator package. CAUTION: Use care when removing the retaining screws. Do not twist or pull on the bracket until both screws are out as this can cause damage to components. To prevent damage to the PCIe IO Accelerator, use only a Philips #1 screwdriver. 2. Remove the two screws holding the full-height bracket to the PCIe IO Accelerator. 3. Remove the bracket carefully from the device.
4. Align the LEDs on the PCIe IO Accelerator with the holes in the half-height bracket. Be sure the bracket tabs are on the heat sink side of the device. 5. Attach the half-height bracket using a Philips #1 screwdriver to tighten the two screws.
CAUTION: Do not overly tighten screws. Overly tightening the screws might damage the device. 6. Return to "Installing the HP PCIe IO Accelerator (on page 12)" and begin with step 2. Installing the HP PCIe IO Accelerator Duo 1. Locate the serial and informational numbers on each side of your ioDrive Duo and record them. 2. Power off the computer and disconnect the power cable. 3. Remove the computer access panel. 4. Locate an available Gen1 x8 or Gen2 x4 PCIe slot.
6. Grasp the Duo by the top edge and seat it in the available PCIe slot.
7. Secure the Duo retaining bracket using a screw or lever (depending on how your hardware is configured). 8. If you are connecting to an external power supply, plug one end of the supplied cable into the Duo power connection and the other into the external power source. 9. Replace the computer access panel. 10. Plug in the power cable and power on the computer. 11. Your operating system might detect the Duo and prompt you to install a driver for the device. If so, click Cancel.
Linux environments Linux installation requirements The HP-provided Linux installers for the IO Accelerator do not contain binary driver modules. Instead, they build the binary driver RPMs specific to the active Linux kernel by using a source RPM for the driver and compiler or build tools. This action enables the use of customized kernels, but does place additional requirements on the system used for initial installation (also known as the build system).
• SMH webpage: hp_ioaccelerator_system_management_homepage_web_templates To install the IO Accelerator software: 1. If you are upgrading your IO Accelerator, backup your data. 2. Install the hardware. 3. Download and install software version 2.2: a. Go to the HP website (http://www.hp.com/support). b. Search for HP IO Accelerator, and navigate to the IO Accelerator product page. c. Select the appropriate files for your operating environment. d. Download the files. 4.
Example: bash hp_io_accelerator-2.2.0.60.4-rhel5.run 8. If the dialog package is installed on your server, the installer script presents a menu to control the installer. If the dialog package is not installed, then the following message appears: Performing standard install. For more advanced features of this installer please install the dialog package. 9. When the dialog is installed, you can choose which packages to install. HP recommends that you install the software RPMs.
The following is an example output showing that the system recognizes the IO Accelerator: Found 1 ioDrive in this system Fusion-io driver version: 2.2.0 build 60 fct0 Attached as 'fioa' (block device) HP 80GB IO Accelerator, Product Number:AJ876A SN:07644 Alt PN:507150-001 PCI:10:00.0 Firmware v5.0.5, rev 43674 80.47 GBytes block device size, 99 GBytes physical device size Sufficient power available: Unknown Internal temperature: avg 56.1 degC, max 56.6 degC Media status: Healthy; Reserves: 100.
Module parameter Default (min/max) Description force_minimal_mode False Force minimal mode on the device. parallel_attach True Enable parallel attach of multiple drivers. preallocate_memory False For the selected device, pre-allocate all memory necessary to have the drive usable as swap space. tintr_hw_wait 0 (0, 255) Interval (microseconds) to wait between hardware interrupts.
On systems that use scripts to load drivers, you can enable or disable an init script with the standard init script utility, chkconfig. By default, the IO Accelerator init script loads the driver at boot time.
3. With the blacklist command in place, reboot Linux. The IO Accelerator driver does not load. To restore driver auto-loading, replace the # symbol to comment out the line. Disabling the driver You can disable loading of the IO Accelerator driver at boot time on either udev or init script systems. This prevents the auto-attach process for diagnostic or troubleshooting purposes. Follow the steps in the "Disabling auto attach (on page 90)" section to disable or enable the auto attach functionality.
shutdown -h now IMPORTANT: For the firmware upgrade to write to the device properly, you must completely shut down the system, and then bring it all the way back up (not just perform a restart). The following is an example of the screen display during a firmware update. # fio-update-iodrive /usr/share/fio/firmware/ioaccelerator_43674.fff Device ID 0 (48:00.0) Updating device firmware from 42014 to 43674 WARNING: DO NOT TURN OFF POWER WHILE THE FIRMWARE UPDATE IS IN PROGRESS.
iv. If the HP IO Accelerator Management Tool is installed, uninstall it. o To uninstall 2.x driver, run the following command: modprobe –r iomemory_vsl If you have not unmounted any filesystems or RAID volumes that are using the IO Accelerator, this command might fail. 3. To uninstall the 2.2 packages, run the following commands in order. o To uninstall the HP IO Accelerator Management Tool: # rpm -qa | grep accelerator fio-firmware-ioaccelerator-43674.2-1.0 hp_io_accelerator_management_tool-gui-2.3.0.
# rpm -e iomemory-vsl-2.6.18-194.el5-2.2.0.82-1.0 To install the new driver, see "Downloading and installing the driver and utilities using Linux (on page 21)." NOTE: When upgrading from version 1.2.7.x to version 2.x, a firmware upgrade is required. For more information, see "Upgrading firmware using Linux (on page 27)." Each new release includes instructions. Make sure you read the Release Notes and the installation instructions to ensure no loss of data.
RAID0/Striped To create a striped set where fioa and fiob are the two IO Accelerators you want to stripe, enter the following command: $ mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/fcta /dev/fctb Use the fio-status command to view your specific names. Making an array persistent Use the following commands to have your RAID 0 array appear after restart: $ sudo sh -c 'echo "DEVICE /dev/fct*" >/etc/mdadm.conf' $ sudo sh –c 'mdadm --detail --scan >>/etc/mdadm.
Setting up SNMP for Linux Use the following procedures to set up SNMP for Linux. SNMP details for Linux The fio-snmp-agentx SNMP agent is an RFC 2741-compliant AgentX sub-agent. Optionally, you can use any RFC-compliant SNMP agent. The master SNMP agent defers queries to fio-snmp-agentx for supported MIBs. SNMP master agent The fio-snmp-agentx, provided in the fio-snmp-hp-mib package, requires an already-installed SNMP master agent.
#set the port that the agent listens on (defaults to 161) agentaddress 161 # simple access control (some form of access control is required) rocommunity public Running the SNMP master agent After you install and configure the master agent, you must start or restart the snmpd daemon for the new parameters to take effect. You can run snmpd from its installed location. This location is often /usr/sbin. For more information, see the snmpd manpage.
This command launches the IO Accelerator subagent using the net-snmp configuration file netsnmp. This file must reside in one of the net-snmp configuration directories: /etc/snmp/usr/share/snmp, /usr/lib/snmp, or $HOME/.snmp. The paths to these directories can be changed. See the manpage for snmp.config. After you launch the subagent, you can view your IO Accelerator management information using an SNMP MIB browser or by using a network management system that accesses cpqioDrv.MIB.
NOTE: For proper operation, the subagent file name must be fio-snmp-agentx.conf. When the SNMP Agentx runs, it reads the fio-snmp-agentx config file: ################################################################### # Example config file for fio-snmp-agentx SNMP AgentX subagent.
The SNMP Agentx now replaces any existing IO Accelerator driver data it has with any populated fields in the list of parameters. If a field is not populated, Agentx retains the existing data and reports it to the MIB. If a value in a field is present, then the Agentx replaces that data and reports it to the MIB. Agentx continues in test mode until the .ini file parameter is set to OFF. The test mode information is described in the testmode.ini file: # SNMP Test Mode sample file.
ExtnUsedPhysCapacityU = 4 ExtnUsedPhysCapacityL = 782330816 ExtnTotalLogCapacityU = 18 ExtnTotalLogCapacityL = 2690588672 ExtnAvailLogCapacityU = 14 ExtnAvailLogCapacityL = 3870457856 ExtnBytesReadU = 18 ExtnBytesReadL = 3690588672 ExtnPhysBytesWrittenU = 4 ExtnPhysBytesWrittenL = 2578550816 ExtnLogBytesWrittenU = 3 ExtnLogBytesWrittenL = 2 ; 2=normal, 1=flashback InfoPercentLifeRemaining = 95 Troubleshooting SNMP For SMH issues, ensure you have installed the latest web templates a
• cpqioDrvInfoStatus • cpqioDrvInfoName • cpqioDrvInfoSerialNumber • cpqioDrvInfoPartNumber • cpqioDrvInfoSubvendorPartNumber • cpqioDrvInfoSparesPartNumber • cpqioDrvInfoAssemblyNumber • cpqioDrvInfoFirmwareVersion • cpqioDrvInfoDriverVersion • cpqioDrvInfoUID • cpqioDrvInfoState • cpqioDrvInfoClientDeviceName • cpqioDrvInfoBeacon • cpqioDrvInfoPCIAddress • cpqioDrvInfoPCIDeviceID • cpqioDrvInfoPCISubdeviceID • cpqioDrvInfoPCIVendorID • cpqioDrvInfoPCISubvendorID • cpqi
• cpqioDrvExtnPhysicalBytesWrittenL Linux environments 39
Windows Server environments Uninstalling a previously-installed driver CAUTION: Upgrading an IO Accelerator from Version 1.2.x to Version 2.x is a one-way process. New firmware is required that is not compatible with 1.2.x systems. Be sure all data is backed up before continuing with the upgrade. Before installing a new driver, uninstall the previous version. 1. Go to the Start menu. 2. Open the Control Panel. 3. Select Add or Remove Programs. 4. Select the package or program.
4. Run the IO Accelerator installation program (Setup Wizard) as explained in "Using the Setup Wizard (on page 41)." CAUTION: The installation program does not remove previous versions of the software. If a previous version is removed after the newest version is installed, the driver does not load after a restart. If this occurs, run the Repair option in the installation program from Programs and Features (or Add or Remove Programs) in the Control Panel, and then restart the computer.
2. Click Next. The Installation Recommendations screen appears. 3. If you have a previous version of the IO Accelerator software installed, follow the directions on the screen to uninstall it. Otherwise, click Next. The Select Installation Folder screen appears.
4. If you want to use the default installation location (C:\Program Files\HP IO Accelerator), click Next. If you want to change the default location, click Browse, navigate to the folder you want, and then click Next. The Custom Setup screen appears. 5. If you want to use the default program features for the installation, click Next.
o Device Driver (required for the drive to be recognized in Windows® operating system) o HP IO Accelerator Management Tool (Java® Runtime Software) o SNMP (requires Microsoft® SNMP to be installed) o Utilities (Command Line Utilities) HP recommends that you select will be installed on local hard drive for each feature. If you change your mind later, you can use the Repair option in Programs and Features, or Add or Remove Programs in the Control Panel. The Configure Shortcuts screen appears. 6.
7. Click Install to begin installation. When installation is complete, the Completion screen appears. NOTE: You might be prompted to stop installation and start the Microsoft® SNMP service during the software installation. 8. Click Finish to exit the Wizard and launch the IO Accelerator software. The installation program performs the following: • Creates a folder for the IO Accelerator software components (the default path is C:\Program Files\HP IO Accelerator).
Manual installation on Windows Server 2003 The Windows Driver Wizard automatically detects the new IO Accelerator and begins to locate its driver after you restart the system. First, Windows prompts you to locate the software driver. 1. If you have not done so, download and run the IO Accelerator Windows® Setup program from the HP website (http://www.hp.com/support). 2. Return to the Update Driver dialog box. 3. Click Browse my computer for driver software.
Manual installation on Windows Server 2008 The Windows Driver Wizard automatically detects the new IO Accelerator and begins to locate its driver after you restart the system. First, Windows prompts you to locate the software driver. 1. Click Browse next to the path field. A file dialog box appears. 2. Select the folder that contains the IO Accelerator driver. The default is C:\Program Files\HP StorageWorks IO Accelerator\Drivers. 3. Click OK. 4. Click Next.
To discover old firmware: 1. Find the name of the latest firmware version as noted in the Release Notes. 2. Use the IO Accelerator Management Tool to check each IO Accelerator firmware version against the latest. 3. For instructions on how to update the firmware, see "Performing the upgrade (on page 48)." Viewing the firmware version The firmware version can be found in the Windows® System Event Log. It is reported by the IO Accelerator Management Tool and the fio-status command line utility.
All three external LED indicators light up during the update process. 5. Restart the computer to finish the firmware upgrade. Upgrading driver software using Windows Upgrading the driver software in Windows® operating systems depends on whether you are using a nonRAID or a RAID configuration. Upgrading driver software using Windows in a non-RAID configuration 1. See the Release Notes for your version of the driver for details on any additional steps to perform the upgrade.
5. Restart the computer. 6. Download the latest driver from the HP website (http://www.hp.com/support). 7. Either unzip or run the Windows® package to copy the files to a convenient directory. 8. Go to Device Manager. 9. In the console tree at the left, expand the HP IO Accelerator item. 10. Select System Devices with pre-2.1 drivers. 11. Remove all but one of the IO Accelerators from the tree. 12. Right-click the remaining IO Accelerator. 13. Click Update Driver Software.
2. Expand HP StorageWorks IO Accelerators, and then double-click HP StorageWorks IO Accelerator. The Properties dialog box appears. The Location field shows the bus number for your device (fct3 in the following example). NOTE: HP assigns bus numbers, which begin at 0. These numbers might or might not reflect the physical location of the bus. For example, the second slot from the edge of the motherboard may be Bus 2, but it might also be Bus 16, or another arbitrary number.
3. After the device is initialized, you can add partitions or volumes. For more information, see the Disk Management documentation. You can create dynamic volumes, which can be used in multi-disk RAID configurations (spanned, striped, or mirrored). For more information, see the Disk Management documentation. Creating a RAID configuration You can use your IO Accelerator as part of a RAID configuration. To do so, you must format the IO Accelerator as a dynamic volume.
For example, you can use the SNMP test mode to change the non-writeable indicator and generate a trap, or simulate a change to the physical or logical size of the device, and so forth. NOTE: To use SNMP test mode, you must have installed the SNMP option with your PCIe IO Accelerator. Using test mode registry values The following table shows the registry entries included for SNMP test values.
SNMP test registry entry Description collection. cpqioDrvInfoCurrentTe mp* Current temperature of the device in degrees Celsius. If this value is set above 78°C for ioDimm cards, a trap is generated. If set above 90°C for HP Mezzanine cards, a trap is generated.
• cpqIoDimmInfoName • cpqIoDimmInfoSerialNumber • cpqIoDimmInfoPartNumber • cpqIoDimmInfoSubvendorPartNumber • cpqIoDimmInfoSparePartNumber • cpqIoDimmInfoAssemblyNumber • cpqIoDimmInfoFirmwareVersion • cpqIoDimmInfoDriverVersion • cpqIoDimmInfoUID • cpqIoDimmInfoState • cpqIoDimmInfoClientDeviceName • cpqIoDimmInfoBeacon • cpqIoDimmInfoPCIAddress • cpqIoDimmInfoPCIDeviceID • cpqIoDimmInfoPCISubdeviceID • cpqIoDimmInfoPCIVendorID • cpqIoDimmInfoPCISubvendorID • cpqIoDimmIn
• cpqIoDimmInfoPowerlossProtectDisabled • cpqIoDimmInfoInternalTempHigh • cpqIoDimmInfoAmbientTemp • cpqIoDimmExtnTotalPhyslCapacityU • cpqIoDimmExtnTotalPhysCapacityL • cpqIoDimmExtnUsablePhysCapacityU • cpqIoDimmExtnUsablePhysCapacityL • cpqIoDimmExtnUsaedPhysCapacityL • cpqIoDimmExtnUsaedPhysCapacityL • cpqIoDimmExtnTotalLogCapacityU • cpqIoDimmExtnTotalLogCapacityL • cpqIoDimmExtnAvailLogCapacityU • cpqIoDimmExtnAvailLogCapacityL • cpqIoDimmExtnBytesReadU • cpqIoDimmExtnByte
Windows Installer logging options The Windows® Installer handles its installations through Msiexec.exe. The logging command is issued with the /L parameter. Options are indicated with an asterisk. For example, the following command turns on logging with verbose output (*v): msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log" The following logging options enable you to create different types of logs, depending on the information you need about the installation.
When the installation package is included in an .exe bootstrapper, do not use msiexec. in the command line. For example: "C:\MyPackage\Setup.msi" /L*V "example.log" Creating an uninstall log Launch the installer with the logging command, for example: "C:\MyPackage\Setup.exe" /L*V "example.log" This command puts the package into maintenance mode, and you can choose to uninstall it. Because the package was launched with logging, an uninstall log is generated.
NOTE: Do not leave this option active because every install or uninstall operation on an .msi file will create a new log. This action results in unnecessarily occupied disk space and makes your system crowded. Only use this option for debugging purposes. The logging policy is particularly useful for troubleshooting Active Directory and Group Policy deployments. In these cases, the installation is carried out without a user interface, and you cannot specify a command line for the .msi.
Message Suggested solution 2 Select your unattached IO Accelerator from the Device Tree. 3 Click Attach. 4 Confirm the Attach operation. Your IO Accelerator now attaches to the Windows® operating system. To re-enable auto attach at boot time, see "Enabling auto attach (on page 91).
VMWare ESX environments Creating the ESX IO Accelerator driver CD The IO Accelerator driver is distributed on the VMware ESX driver CD. To create the VMware ESX driver CD: 1. Download the appropriate driver .iso and .rpm packages from the HP website (http://www.hp.com/go/support). Examples: 2. o iomemory-vsl-esx-4.0-2.1.0.240.iso o fio-util-2.1.0.223-1.0.x86_64.rpm o fio-firmware-42895-1.0.noarch.rpm Write the .iso image to a CD-ROM. Installing the driver as part of a new ESX installation 1.
$ vihostupdate --install --nosigcheck --bundle=offlinebundle.zip 7. Restart the ESX host. 8. Exit maintenance mode. Installing the driver using esxupdate Before you install a new driver set using esxupdate, you must first remove any entry that begins with either of the following commands: • cross_vmware-esx-drivers-block-fio-drive • cross_vmware-esx-drivers-block-iomemory-vsl To remove previously installed drivers: 1.
The firmware and utilities are installed to the following locations Package type Installation location Utilities (ESX only) /usr/bin Firmware /usr/share/fio/firmware Configuring the IO Accelerator using ESX 1. Enter the following command to connect to the COS: ssh root@IP where IP is the IP address of the ESX system. 2. If the driver is loaded, disable driver auto load and reboot. For more information, see "Disabling the IO Accelerator VSL." 3.
8. Find the files with those UIDs in /vmfs/devices/disks/. Select the files with appended partition numbers. In this case: /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:1 /vmfs/devices/disks/mpx.vmhba3:C0:T1:L0:1 9. Enter the following command to pass that file to vmkfstools and create a vmfs format: vmkfstools -C vmfs3 -b 4M FILE -S LABEL where FILE is the file from above and LABEL is a handy label such as fio1.
Using the IO Accelerator as swap with ESX HP does not recommend using the IO Accelerator as swap space when using the ESX host. However, the IO Accelerator can be used as swap for virtual machines. To use the IO Accelerator as swap for a virtual machine: 1. Go to VMware vSphere Client > Configuration > Virtual Machine Swapfile Location. 2. Indicate the appropriate Datastore location as the virtual machine swapfile location.
HP IO Accelerator Management Tool Operating system support The following is the IO Accelerator Management Tool administrator console for IO Accelerators. The following content shows you how to use the IO Accelerator Management Tool to maintain the IO Accelerator at peak performance and troubleshoot any issues with the device. The IO Accelerator Management Tool runs on both Windows® and Linux platforms.
NOTE: Running the IO Accelerator Management Tool requires administrator privileges. Log in as root or use the sudo command to run the installation. 1. Go to the appropriate product page for your IO Accelerator: o HP IO Accelerator for BladeSystem c-Class (http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=39 00936&lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3900933&taskId=135) o HP PCIe IO Accelerator for ProLiant servers (http://h18004.www1.hp.
• The Device Report panel on the right displays details on one or more selected devices.
Performance report When you click the Performance tab, IO Accelerator Management Tool draws a real-time graph of selected attached devices throughput. You can view Read and Write versus Time, which measures throughput in megabytes per second, or you can separate the data into two graphs, Read (MB/sec) versus Time, and Write (MB/sec) versus Time. The lower left corner of each window displays how long the data has been captured, in minutes and seconds. You can re-size the window to gather more data.
• Page File Settings—Enables or disables the use of the IO Accelerator as a page file device. NOTE: A low-level format is not the same as an operating system file system format and should generally be performed only when recommended by HP Customer Support because the device is shipped pre-formatted. Detached IO Accelerator after installation An IO Accelerator might appear detached immediately after installation and the first time you run IO Accelerator Management Tool.
• The Ctrl-A key combination selects all the available items in a list (such as all the IO Accelerators in the Device Tree). Device Tree The Device Tree displays a tree view of all installed IO Accelerator devices on this computer. The computer is identified with the: • Server Name • IP Address • Operating System and version (if known) Each installed IO Accelerator is identified by name on a separate branch of the tree.
If you right-click the Tool Tip, the context menu appears. Drive status The tree also shows the status of each drive: attached, detached, which operation is in progress, or if an error condition exists.
• Drive Normal: When a drive is attached to the operating system and available to users, it appears as Status: Attached. When an IO Accelerator is attached, the Device Tree shows the device mount point just below the device name. If the drive is mounted to multiple file system mount points, only the first one appears in the Device Tree. In Windows® operating systems, the other mount points and detailed file system information can be seen by mousing over the device and waiting for the Tool Tip to appear.
• Drive Detached: When a drive is not available to the operating system or users, it appears as Status: Detached. This can be the result of: a Detach Device operation, the drive not functioning, or out-ofdate firmware.
• Operation in Progress: The device shows an activity icon. A message in the Device Report panel indicates which operation is executing, the percent complete, and an estimated time for completing the operation. • Error Conditions: When conditions require attention, IO Accelerator Management Tool shows warnings and errors in the Device Tree. Warnings are indicated by a yellow triangle with an exclamation point, while errors are indicated by a red stop sign with an exclamation point.
3. Press Ctrl-Click left mouse button to select two or more separate devices. The Device Report panel displays details about each device (individual devices might vary in what fields they report due to hardware differences): • Driver Version—Indicates the IO Accelerator driver software version. • Device Name—The number indicates the device serial number. • Status—Shows the status of the device. Normal is Attached.
Saving IO Accelerator information You can save the selected IO Accelerator information using the Copy feature. 1. Highlight one or more IO Accelerators in your Device Tree. Use the Shift or Ctrl keys to select which drives you wish to view. The IO Accelerator Management Tool displays information for each drive in the Device Report panel as you select it. 2. Click in the Device Report panel to change the focus to that list. 3.
When you open the Performance tab, it shows a combined view of read and write performance. To view the read and write data in separate windows, click the Separate View icon on the upper right corner of the Performance window. To switch back to Combined View, click the Combined View icon at the upper right of the Performance window. To select devices you want to monitor, click their images in the left panel.
• Detach Device—Detaches an IO Accelerator so you can perform a low-level format or upgrade the firmware. Detach works only on attached devices. To manage one or more IO Accelerators: 1. Click one of the IO Accelerators in the Device Tree. 2. Hold the left mouse button down to select several devices at once. 3. Use Ctrl-Click left mouse button to select two or more separate devices. Update firmware The Update Firmware operation lets you upgrade the IO Accelerator firmware.
To perform a firmware upgrade: 1. Download the IO Accelerator firmware upgrade file from and place it in a convenient directory. 2. Select the devices you want to upgrade in the Device Tree. 3. Click Update Firmware in the menu bar. 4. Select the IO Accelerator firmware file from the dialog box. The file naming convention is IO Accelerator_version.fff, where version is the numerical version of the firmware. For Linux, the default location for this file is /usr/share/fusionio/images.
The IO Accelerator Management Tool shows the default directories, so unless you have installed the firmware in a non-standard location, the Select Firmware File dialog box opens to the correct location. After you select a file from a given folder, that folder will be saved as the default place for the file chooser to open next time you perform a firmware update. 6. Click Next to proceed. The selected file appears in the confirmation dialog box.
7. Click Next to proceed 8. Click Update. The selected drives display a blue progress bar in the Device Report panel as the update occurs. This bar shows both the percentage and the estimated time remaining to complete the update. When the update completes, the IO Accelerator Management Tool displays a dialog box requesting you to reboot to complete the process. 9. Click OK. 10. Power down and restart the computer to ensure a full reset of the system and installation of the firmware.
To cancel the update, click the X at the upper right of the dialog box to exit. To select a different firmware update file, click Back to return to the File Selection dialog box. Attach Device The Attach Device operation creates a link so the IO Accelerator interacts with the operating system.
If the Attach Device operation fails, an error message appears. Attaching mixed attached/detached devices If you select a set of IO Accelerators to attach where some are attached and some are detached, the Confirm Attach dialog box displays a list of the drives and their statuses. When you click Attach, the IO Accelerator Management Tool connects only the detached devices (those marked Ready). Detach Device Detach Device disconnects your IO Accelerator from the operating system.
Use Attach to restore the operating system access to the IO Accelerator. Detaching mixed attached/detached devices If you select a set of IO Accelerators to detach where some are attached and some are detached, the Confirm Detach dialog box displays a list of the drives and their statuses. When you click Detach, the IO Accelerator Management Tool disconnects only the attached devices (those marked Ready).
o Maximum Write Performance—Formats the device for maximum write performance at the cost of approximately 50% capacity. 4. Choose an option and click Next. The IO Accelerator Management Tool program lists the selected devices to format and the approximate capacity after formatting for each device. 5. Click Format to perform the format.
The IO Accelerator Management Tool automatically detaches the selected devices. A blue progress bar displays in the Device Report panel, showing both the percentage of progress and the estimated time remaining to complete the format. When the format completes, the IO Accelerator Management Tool automatically reattaches the newlyformatted IO Accelerators for use by the operating system.
• About IO Accelerator Management Tool: Displays the version splash screen. • Exit: Closes the IO Accelerator Management Tool.
Maintenance Maintenance tools The IO Accelerator includes both software utilities to maintain the device and external LED indicators to display its status. You can also install SNMP as a monitoring option. The following are the most common tasks for maintaining your IO Accelerator. You can also use the IO Accelerator Management Tool application to perform firmware upgrades. For more information, see HP IO Accelerator Management Tool (on page 66).
Common maintenance tasks The following tasks are the most common tasks for maintaining your IO Accelerator. NOTE: All commands require administrator privileges. Log in as root or use sudo to run the commands. Uninstalling the IO Accelerator driver package Linux To uninstall the IO Accelerator driver package in Linux, enter the following command. For 1.2.x systems: $ rpm –e iodrive-driver For 2.x systems: $ rpm -e iomemory-vsl Windows® operating systems To uninstall the IO Accelerator Windows® driver: 1.
For 2.x systems: /etc/modprobe.d/iomemory-vsl.conf 2. Add the following line to that file: o For 1.2.x systems: options iodrive auto_attach=0 o For 2.x systems: options iomemory_vsl auto_attach=0 3. Save the file. To disable auto attach using the Linux udev script, add the following line to your /etc/modprobe.d/iomemory-vsl file: options iomemory-vsl auto_attach=0 Windows® operating systems To disable auto attach using a Windows® operating system: 1. Open the IO Accelerator Utilities folder.
1. Open the IO Accelerator Utilities folder. The default location is C:\Program Files\HP IO Accelerators\Utils\. 2. Double-click the autoattachenable.reg file. 3. If necessary, confirm that you want to modify the registry. This action resets the AutoAttach parameter in the Registry. The next time you reboot your Windows® operating system, your IO Accelerator automatically attaches.
Utilities Utilities reference The IO Accelerator installation packages include various command line utilities, installed by default to the /usr/bin file for Linux and the C:\Program Files\HP IO Accelerator\Utils folder for Windows Server®. These utilities provide a number of useful ways to access, test, and manipulate your device.
NOTE: To run these utilities from a command line using Windows Server®, you must either change directories to the directory that contains them (by default, C:\Program Files\HP IO Accelerator\Utils) or add that directory to your system path. See the documentation for your Windows® version for information about adding a directory to the system path. NOTE: The command-line utilities require administrator rights to run under Windows® operating systems.
• -p Print: Prints the PCI bus ID at to standard output. Usage and error information can be written to standard output rather than to standard error. fio-bugreport Description Prepares a detailed report of the device for use in troubleshooting problems. The results are saved in the /tmp directory in a file that indicates the date and time the utility was run. Example /tmp/fio-bugreport-20090921.173256-sdv9ko.tar.
Option Default (min/max) Description parallel_attach True Enable parallel attach of multiple drivers fio_preallocate_memory False For the selected device, preallocate all memory necessary to have the drive usable as swap space fio-detach Description Detaches and removes the corresponding /dev/fctx IO Accelerator block device. The fio-detach command waits until the device completes all read/write activity before executing the detach process.
• %: Percentage of device for user data • t/T: Number of terabytes to format • g/G: Number of gigabytes to format • m/M: Number of megabytes to format • • For example, setting the size as either 90% or 72 GB on an 80 GB PCIe IO Accelerator both result in the same capacity for user data—72GB. -u Quiet: Disables the display of the progress percentage and spinning activity icon. fio-pci-check Description Checks for errors on the PCI bus tree, specifically for IO Accelerators.
This utility is an SNMP sub-agent that implements the cpqIODrv.mib for the IO Accelerator driver. The fio-snmp-agentx utility communicates with the SNMP master agent via the agentx protocol. Syntax fio-snmp-agentx [-c, -f, -l , -m, -s, -h, -v] Options • -c : Sets the configuration file to use. The file elements are described in the following table. NOTE: Use this option only to change the name of the config file. Do not specify a path.
• -a: Prints all available information for each device.
fio-trim-config Description Enables or disables the Trim feature (Windows® service), which reclaims available space from the file system. It is generally recommended that Trim be enabled for best performance. Running this utility with no options displays the current Trim status. See "Trim support ("Trim support (Windows only)" on page 105)" for more information. NOTE: This utility affects all IO Accelerators in the system. You cannot enable or disable Trim for only selected devices.
• -s: Updates the devices in the specified slots using ‘*’ as a wildcard for devices. The slots are identified in the following PCIe format (as shown in lspci): [[[[]:]]:][][.[]] All three external LED indicators light up during the update process.
Monitoring IO Accelerator health NAND flash and component failure The IO Accelerator is a highly fault-tolerant storage subsystem that provides many levels of protection against component failure and the loss nature of solid state storage. However, as in all storage subsystems, component failures might occur. When a large enough number of data blocks is retired due to error, the NAND flash media is considered worn out.
HP 160GB SLC PCIe ioDrive for ProLiant Servers, Product Number:600278-B21 ... Media status: Healthy; Reserves: 100.00%, warn at 10.00%; Data: 99.12% Lifetime data volumes: ...Physical bytes written: 6,423,563,326,064 ...
heavy workload is evicted from a RAID group for failure to receive data at a sufficient rate. A drive in read-only mode is evicted when write I/Os are returned from the device as failed. Catastrophic failures are detected and handled just as though they were on traditional storage devices.
Trim support (Windows only) Introduction to Trim Trim is used to address a unique property of solid state drives. The issue occurs when a user deletes a file, and then the drive that contains the file does not recognize that it can reclaim that space. Instead, the drive reads the data as valid until the system informs the drive it can overwrite that data. With a typical hard drive you can continually write to the same sector of the drive without significant degradation.
Starting and stopping Trim To globally start or stop the Trim service through the IO Accelerator Management Tool, in the upper-left corner of the console screen, click the button to toggle the state of the service (either running or stopped). To start or stop the Trim service through the Windows® Services Manager: 1. Search for IO Accelerator Trim Service. 2. Click Start service or Stop service. Stopping the service only stops it for that session.
BitmapRetrievalDelayInMilliseconds This value affects how much impact Trim has on the CPU. The default is 25 milliseconds but can be any number between 0 (most aggressive) and 4,294,967,295 (not aggressive at all). Trim configurations Trim can be used with the following configurations and features: • RAID volumes (mirrored, spanned, or striped). NOTE: RAID 5 (striped with parity) is not currently supported. • Simple volumes (no RAID).
Using Windows page files with the IO Accelerator Introduction to Windows page files This section describes how to effectively use paging (swap) files on IO Accelerator devices with Windows® operating systems. Using a page file with a traditional disk drive places practical limits on the usable size of the page file and virtual memory due to the poor performance of disk drives in relation to RAM.
• it minimizes overall host memory consumption. On Windows® operating systems, NTFS will generally use a cluster size of 4K, so formatting to 512 is not useful except for applications that are compatible only with 512-byte sector sizes (such as Windows® XP and Windows Server® 2003). The indicated amount is needed per IO Accelerator that supports paging. You must carefully plan which IO Accelerators are used to hold a paging file.
To query the current value, run this command: fio-config -g FIO_PREALLOCATE_MEMORY An alternate method to manage (enable or disable) paging support is to use the IO Accelerator Management Tool. NOTE: You must reload the IO Accelerator driver for the new preallocation setting to take effect. Typically this can be done by restarting the machine or using disable/enable within Device Manager for each IO Accelerator instance.
page 109)" to properly enable page file support on one or more IO Accelerators. System drive paging file configuration By default, Windows® operating systems create and manage a page file on the system boot drive (typically a hard disk), which is where the operating system is installed. Maintaining a regular page file on the system hard disk is typically not optimal, because the hard disk I/O performance is many orders of magnitude slower than an IO Accelerator.
• Main Article Link: Pushing the Limits of Windows (http://blogs.technet.com/b/markrussinovich/archive/2008/07/21/3092070.aspx) • Specific section that documents virtual memory: Pushing the Limits of Windows: Virtual Memory (http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx) Verifying page file operation To verify that a page file is actively placed on an IO Accelerator, you can browse for hidden files at the drive root.
Resources Subscription service HP recommends that you register your product at the Subscriber’s Choice for Business website at www.hp.com/support (http://www.hp.com/support). After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. For more information For additional information, see the following HP websites: • HP BladeSystem technical resources (http://www.hp.
Technical support Before you contact HP Be sure to have the following information available before you call HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error messages • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level HP contact information For the name of the nearest HP authorized reseller: • See the Contact HP worldwi
• Optional—Parts for which customer self repair is optional. These parts are also designed for customer self repair. If, however, you require that HP replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product. NOTE: Some HP parts are not designed for customer self repair. In order to satisfy the customer warranty, HP requires that an authorized service provider replace the part.
Pour plus d'informations sur le programme CSR de HP, contactez votre Mainteneur Agrée local. Pour plus d'informations sur ce programme en Amérique du Nord, consultez le site Web HP (http://www.hp.com/go/selfrepair). Riparazione da parte del cliente Per abbreviare i tempi di riparazione e garantire una maggiore flessibilità nella sostituzione di parti difettose, i prodotti HP sono realizzati con numerosi componenti che possono essere riparati direttamente dal cliente (CSR, Customer Self Repair).
HINWEIS: Einige Teile sind nicht für Customer Self Repair ausgelegt. Um den Garantieanspruch des Kunden zu erfüllen, muss das Teil von einem HP Servicepartner ersetzt werden. Im illustrierten Teilekatalog sind diese Teile mit „No“ bzw. „Nein“ gekennzeichnet. CSR-Teile werden abhängig von der Verfügbarkeit und vom Lieferziel am folgenden Geschäftstag geliefert. Für bestimmte Standorte ist eine Lieferung am selben Tag oder innerhalb von vier Stunden gegen einen Aufpreis verfügbar.
el caso de todas sustituciones que lleve a cabo el cliente, HP se hará cargo de todos los gastos de envío y devolución de componentes y escogerá la empresa de transporte que se utilice para dicho servicio. Para obtener más información acerca del programa de Reparaciones del propio cliente de HP, póngase en contacto con su proveedor de servicios local. Si está interesado en el programa para Norteamérica, visite la página web de HP siguiente (http://www.hp.com/go/selfrepair).
Opcional – Peças cujo reparo feito pelo cliente é opcional. Essas peças também são projetadas para o reparo feito pelo cliente. No entanto, se desejar que a HP as substitua, pode haver ou não a cobrança de taxa adicional, dependendo do tipo de serviço de garantia destinado ao produto. OBSERVAÇÃO: Algumas peças da HP não são projetadas para o reparo feito pelo cliente. A fim de cumprir a garantia do cliente, a HP exige que um técnico autorizado substitua a peça.
Technical support 120
Technical support 121
Regulatory compliance notices Regulatory compliance identification numbers For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this regulatory model number.
Disposal of waste equipment by users in private households in the European Union This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment.
Acronyms and abbreviations CIM common information model CIMOM common information model object manager CMPI common manageability programming interface COS console operating system CPU central processing unit DA direct attached DIMM dual inline memory module DMTF Distributed Management Task Force DRAM dynamic random access memory EULA end user license agreement FAT file allocation table GUI graphical user interface Acronyms and abbreviations 124
GUID globally unique identifier HBA host bus adapter I/O input/output IOPS input/output operations per second iSCSI Internet Small Computer System Interface LEB Logical Erase Block LED light-emitting diode LVM Logical Volume Manager MIB management information base MOF managed object format MSI Message Signaled Interrupt NTFS NT File System PCI peripheral component interface PCIe peripheral component interconnect express Acronyms and abbreviations 125
RAID redundant array of inexpensive (or independent) disks RAM random access memory RFC request for comments RHEL Red Hat Enterprise Linux SAN storage area network SAS serial attached SCSI SCSI small computer system interface SFCB small footprint CIM broker SMH System Management Homepage SMI-S Storage Management Initiative Specification SNIA Storage Networking Industry Association SNMP Simple Network Management Protocol UID unit identification UPS uninterruptible power system Acronyms and abbr
USB universal serial bus VM Virtual Machine VSL virtual storage layer WBEM Web-Based Enterprise Management WMI Windows Management Instrumentation Acronyms and abbreviations 127
Index A About this guide 7 Adding a file system 50 Attach Device 82 attaching mixed attached/detached devices 83 authorized reseller 113 automated logging 57 B building a RAID 10 31 C checking for updated firmware 81 configuring IO Accelerator paging support 107 configuring RAID 30, 51 configuring the IO Accelerator using ESX 62 configuring the SNMP master agent 32 configuring the SNMP subagent 33 Contents summary 7 controlling driver loading 25 controlling Trim aggressiveness 105 creating a driver CD 60
HP Subscriber's Choice for Business 112 HP technical support 113 HP, contacting 113 navigating the HP IO Accelerator Management Tool 69 non-paged memory pool 108 I O identification number 121 installing ESX driver 60, 61 installing hardware 12, 18 installing software 65 installing software on a new system 39 installing software on an existing installation 60, 61 installing software using Linux 65 installing the HP Installer script 22 installing the SNMP subagent 33 installing utilities 61 introduction 8
SNMP master agent 32 SNMP MIB support 37, 53 SNMP, Linux details 32 SNMP, Windows details 51 software installation 39, 65 software RAID and health monitoring 102 starting Trim 105 stopping Trim 105 subagent log file 34 support 113 supported firmware revisions 10 supported hardware 10 system drive paging file configuration 110 VMware ESX and ESXi environments 60 W Windows installation 39 Windows Installer logging options 56 Windows page file management 109 Windows page files 107 Windows page files, introdu
