HP IO Accelerator Version 3.2.3 Linux User Guide Abstract This document describes software requirements for all relevant HP IO Accelerators using Linux operating systems. This document is intended for system administrators who plan to install and use HP IO Accelerators with a Linux operating system. It is helpful to have previous experience with HP IO Accelerators and a Linux operating system. This user guide is intended for IO Accelerator software release 3.2.3 or later.
© Copyright 2011, 2013 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 ........................................................................................................................... 6 Contents summary ..................................................................................................................................... 6 Introduction .................................................................................................................................. 7 Overview ...................................................
Manually running the SNMP subagent ............................................................................................. 29 Subagent log file ........................................................................................................................... 29 Using the SNMP sample config files........................................................................................................... 30 Enabling SNMP test mode ..................................................................
Resources .................................................................................................................................. 59 Subscription service ................................................................................................................................. 59 For more information ............................................................................................................................... 59 Regulatory information ......................................
About this guide Contents summary • Instructions on downloading and installing the approved driver and utilities • Instructions on maintaining the IO Accelerator • Description of the following IO Accelerator models: o HP IO Accelerator for BladeSystem c-Class o HP PCIe IO Accelerator o HP PCIe IO Accelerator Duo CAUTION: Before upgrading to 3.x.x software and firmware, back up all data on the IO Accelerator. The 3.2.
Introduction Overview Designed around ioMemory, a revolutionary storage architecture, HP IO Accelerator is an advanced NAND flash storage device. With performance comparable to DRAM and storage capacity on par with hard disks, the IO Accelerator increases performance so that every server can contain internal storage that exceeds the I/O performance of an enterprise SAN. HP IO Accelerator is the first data accelerator designed specifically to improve the bandwidth for I/O-bound applications.
• QK762A: HP 785GB IO MLC Accelerator for BladeSystem c-Class • QK763A: HP 1.2 TB IO MLC Accelerator for BladeSystem c-Class IMPORTANT: Generation 2 IO accelerators for BladeSystem c-Class are only compatible with Gen8 and later server blades.
NOTE: MSI was disabled to obtain these statistics. Required operating environment The HP IO Accelerator with software 3.2.3 is supported for use in the following operating environments: • Red Hat Enterprise Linux 5 (AMD64/EM64T) • Red Hat Enterprise Linux 6 (AMD64/EM64T) • SUSE LINUX Enterprise Server 10 (AMD64/EM64T) • SUSE LINUX Enterprise Server 11 (AMD64/EM64T) CAUTION: Version 3.1.0 or greater of the driver software is not backward-compatible with any previous driver version.
BladeSystem c-Class IO Accelerators have two distinct designs for the respective server product lines. The G1 through G7 IO Accelerator adapter is provided in a c-Class Type 1 Mezzanine card form factor. It can be installed in both Type 1 and Type 2 mezzanine slots within the c-Class blade G1 through G7 servers, enabling a total of two cards in a half-height server blade, and three cards in a full-height server blade and up to 6 in a double-high, double-wide server (BL680c).
• Sufficient RAM to operate—The amount of RAM that the driver requires to manage the NAND flash varies according to the block size you select when formatting the device (filesystem format, not low-level format). For a virtual machine using an IO Accelerator directly (using PCI pass-through), consult the user guide for the installed operating system. The following table lists the amount of RAM required per 100GB of storage space, using various block sizes. The amount of RAM used in driver version 3.
Software installation Installation overview For the system requirements, including supported operating systems, consult the HP IO Accelerator Release Notes for this release. Before installing the IO Accelerator driver, make sure you have properly installed the IO Accelerator devices. For more information, see the HP IO Accelerator Hardware Installation Guide.
IMPORTANT: Exact package names vary, depending on the software and kernel version chosen. 3. Go to the HP website (http://www.hp.com/support), and then download all of the support rpm packages. These packages provide utilities, firmware, and other files. For example, see the following table. Package What is installed fio-util-.x86_64.rpm fio-firmware-.noa rch.rpm libvsl-.
Package type Installation location SNMP MIB /usr/share/fio/mib IMPORTANT: HP IO Accelerator Management Tool 3.0 Installation HP IO Accelerator Management Tool 3.0 is a free GUI solution for managing IO Accelerator devices. The tool is also available from the HP website (http://www.hp.com/support). Uninstall any previous versions of HP IO Accelerator Management Tool before installing the latest version.
IMPORTANT: If your kernel is a UEK, you also may need to use the --nodeps option. When using a .rpm source package for a non-running kernel, run the following command: $ rpmbuild --rebuild --define 'rpm_kernel_version ' iomemory-vsl-.src.rpm The new RPM package is located in a directory that is indicated in the output from the rpmbuild command. To find the package, look for the Wrote line.
Upgrade path Depending on the current version of your HP IO Accelerator device, to preserve the internal structure of the device, you might have to perform multiple upgrades. The following path is the minimum upgrade path that you must follow. Upgrade the HP IO Accelerator VSL software on the system, and upgrade the firmware to the compatible version in the following order: 1.2.4 > 1.2.7 > 2.1.0 > 2.2.3 > 3.2.
b. To uninstall the FSL, run a command similar to the following example. Specify the kernel version of the package you want to uninstall: $ rpm -e iomemory-vsl-2.6.18-194.el5-2.2.0.82-1.0 c. To uninstall the utilities, run the following command: $ rpm -e fio-util fio-snmp-agentx fio-common fio-firmware iomanager-gui iomanager-jre libfio libfio-doc libfusionjni fio-sysvinit fio-smis fio-snmp-mib libfio-deb 4. Install the new VSL and related packages: a.
fio-attach /dev/fct* 10. Using the following command, check the status of all devices: fio-status -a Your IO Accelerator devices are now successfully upgraded for this version of the HP IO Accelerator. You can now install any IO Accelerator Gen2 devices. Loading the IO Accelerator driver 1. Load the driver: $ modprobe iomemory-vsl The driver automatically loads at system boot. The IO Accelerator is now available to the operating system as /dev/fiox, where x is a letter.
NOTE: The init script is part of the fio-sysvinit package, which must be installed before you can enable the init script. To disable this loading of the IO Accelerator driver, enter the following command: $ chkconfig --del iomemory-vsl To re-enable the driver loading in the init script, enter the following command: $ chkconfig --add iomemory-vsl For more details, see "Using the init script (on page 19)".
The options file contains documentation for the various settings: two of which, MOUNTS and KILL_PROCS_ON_UMOUNT, are discussed in more detail in the "Handling IO Accelerator driver unloads (on page 20)." Mounting filesystems The IO Accelerator driver is not loaded in the initrd, and, (built kernel) therefore, using the standard method for mounting filesystems (/etc/fstab), does not work. To set up auto-mounting of a filesystem hosted on an IO Accelerator: 1. Add the mnt command to /etc/fstab. 2.
Module parameter Description Default (minimum/maxi mum) fio_dev_wait_timeout_secs 30 Number of seconds to wait for /dev/fio* files to show up during driver load. For systems not using udev, set this parameter to 0 to disable the timeout and avoid an unneeded pause during driver load. force_minimal_mode False Force minimal mode on the device. parallel_attach True Enable parallel attach of multiple devices.
If the output shows that the device is running in Minimal mode, download the latest firmware from the HP website (http://www.hp.com/support), and then use the HP IO Accelerator Management Tool application or the "fio-update-iodrive (on page 49)" utility to upgrade the firmware. CAUTION: Upgrade Path • Do not attempt to downgrade the firmware on any IO Accelerator device. • You must follow a specific upgrade path when upgrading an IO Accelerator device.
2. Edit the file to add an entry similar to the following: types = [ “fio”, 16 ] The parameter “16” represents the maximum number of partitions supported by the drive. For the IO Accelerator, this can be any number from 1 upwards. Do not set this parameter to 0. IMPORTANT: Do not run the udev command to load the IO Accelerator driver while LVM or MD is active. The init script will disconnect from the LVM volumes and MD devices before disconnecting from the Memory device.
IMPORTANT: For example, if the array consists of two devices, the command output will not display three lines in the mdadm.conf file– one line for the array, and a line for each device. Ensure that those lines are added to the mdadm.conf file so it matches the output of the command. For more details, see the mdadm and mdadm.conf manpages for your distribution. With these changes, on most systems the RAID 0 array will be created automatically upon restart. 6.
RAID 1 Create a mirrored set by using the fioa and fiob IO Accelerators: $ mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/fioa /dev/fiob To view your specific names, use the fio-status command.
/dev/fioc /dev/fiof \ /dev/fioe /dev/fioh \ /dev/fiog /dev/fiob # 8 Duos RAID10 $ mdadm --create --assume-clean --level=raid10 --layout=n2 -n 16 /dev/md0 \ /dev/fioa /dev/fiod \ /dev/fioc /dev/fiof \ /dev/fioe /dev/fioh \ /dev/fiog /dev/fioj \ /dev/fioi /dev/fiol \ /dev/fiok /dev/fion \ /dev/fiom /dev/fiop \ /dev/fioo /dev/fiob Understanding Discard (TRIM) support Discard (also known as TRIM) is enabled by default in this version of the IO Accelerator driver.
Setting up SNMP for Linux SNMP details for Linux The fio-snmp-agentx SNMP agent is an RFC 2741-compliant AgentX subagent. It can work with any RFC-compliant SNMP agent, such as Net-SNMP. The master SNMP agent defers queries to fio-snmp-agentx for supported MIBs. Files and directories File Description /usr/share/fio/mi HP MIB for the IO Accelerator b/cpqIODrive.mib /opt/fio/etc/snmp HP IO Accelerator SNMP configuration /fio-snmp-agent.co nf* /etc/snmp/snmpd Master SNMP configuration file .
To install Net-SNMP on Red Hat, use the following command: yum install net-snmp rsync Other Linux versions To install the Net-SNMP package on your Linux distribution, use the standard system package manger. The fio-snmp-mib package places MIB files in /usr/share/fio/mib directory. Configuring the SNMP master agent You can configure the Net-SNMP master agent daemon to set the network communications parameters, security, and other options by using the snmpd.conf text file.
2. Install the package using your operating systems package manager. For example, on Red Hat: rpm -Uvh fio-snmp-*.rpm The SNMP package places the MIB files in the /usr/share/fio/mib directory. Running and configuring the SNMP subagent An RPM to configure the SNMP files is available on the HP website (http://www.hp.com/go/support). The RPM is named hp-ioaccel-snmp-agent1-1.x86_64.rpm. To manually set up SNMP: 1. Configure the subagent by creating a fio-snmp-agentx.conf file. 2.
Using the SNMP sample config files When you install SNMP, the following sample config files are available: • /usr/share/doc/fio-snmp-agentx/conf/snmpd.conf.hp/ (master agent) • /usr/share/doc/fio-snmp-agentx/conf/fio-snmp-agentx.conf.hp/ (subagent) To customize and use the sample config files: 1. Rename the snmpd.conf and the fio-snmp-agentx.conf files. For example, snmpd.orig.conf and fiosnmp-agentx-orig.conf. The snmpd.conf file is located in /etc/snmp or the /usr/share/snmp directories.
The conditions for test mode include the following: • If the Admin has set the test_mode_enabled parameter from TRUE to FALSE, then the SNMP subagent does not attempt to run test mode but it continues processing data as usual from the IO Accelerator driver, storing the data in the MIB. • If the CONF file says that test_mode_enabled is TRUE, then the SNMP subagent first reads the testmode_file line to locate the testmode.ini file. Next, the subagent reads this file. • If the testmode.
# 13 = update InfoState = 2 InfoInternalTemp = 45 InfoAmbientTemp = 35 InfoWearoutIndicator = 2 ; 2=normal, 1=device is wearing out. InfoWritableIndicator = 2 ; 2=normal, 1=non-writable, 0=write-reduced, 3=unknown InfoFlashbackIndicator = 2 ; 2=normal, 1=flashback protection degraded.
Troubleshooting SNMP For SMH issues, ensure you have installed the latest web templates available for the IO Accelerator from the HP website (http://www.hp.com/go/support). If a new PSP has been loaded, the latest IO Accelerator templates should be installed after the PSP is installed. If the IO Accelerator is not viewable on the SMH, the port selected might already be in use. To verify whether the port is already in use: 1.
SNMP MIB SNMP MIB cpqIoDrvInfoFlashbackIndicator cpqIoDrvInfoWritableIndicator cpqIoDrvInfoInternalTemp cpqIoDrvInfoHealthPercentage cpqIoDrvInfoMinimalModeReason cpqIoDrvInfoReducedWriteReason cpqIoDrvInfoMilliVolts cpqIoDrvInfoMilliVoltsPeak cpqIoDrvInfoMilliVoltsMin cpqIoDrvInfoMilliWatts cpqIoDrvInfoMilliWattsPeak cpqIoDrvInfoMilliAmps cpqIoDrvInfoMilliAmpsPeak cpqIoDrvExtnFormattedBlockSize cpqIoDrvExtnCurrentRAMUsageU cpqIoDrvExtnCurrentRAMUsageL cpqIoDrvExtnPeakRAMUsageU cpqIoDrvExtnPeakRAMUsageL
Maintenance Maintenance tools The IO Accelerator includes software utilities for maintaining the device. 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 the HP IO Accelerator Management Tool User Guide.
• fio-update-iodrive For more information, see "Utilities reference (on page 40)." Enabling PCIe power override For PCIe IO Accelerators, if you have installed any dual IO Accelerator devices, such as the HP ioDrive2 Duo, then the device might require additional power than the minimum 25 W provided by PCIe Gen2 slots to properly function. Even if additional power is not required for your device, all dual IO Accelerator devices that receive additional power might benefit with improved performance.
in a slot that is not rated to provide 55W of power, your server hardware could experience a power drag. • The override parameter is a setting for the IO Accelerator VSL software by server and is not stored in the device. When moved to a new server, the device defaults to the 25 W power limit until an external power cable is added or the override parameter is enabled for that device in the new server. To determine the total PCIe slot power available for the new server, consult the manufacturer.
IMPORTANT: All commands require administrator privileges. To run the commands, log in as root or use sudo. IMPORTANT: If you came to this section from the Software Installation section, return to that section after you uninstall previous versions of the driver and utilities. Unloading the IO Accelerator driver Unload the IO Accelerator driver: $ modprobe –r iomemory_vsl Uninstalling the IO Accelerator driver RPM package Versions 1.2.
To disable auto_attach using the Linux init script: 1. Edit the following file: /etc/modprobe.d/iomemory-vsl.conf 2. Add the following line to the file: options iomemory_vsl auto_attach=0 3. Save the file. 4.
Utilities Utilities reference The IO Accelerator installation packages include various command line utilities, installed by default to the /usr/bin file. These utilities provide a number of useful manners to access, test, and manipulate your device.
You can specify multiple IO Accelerator devices. For example, /dev/fct1 /dev/fct2 indicates the second and third IO Accelerator devices installed on the system. You can also use a wildcard to indicate all IO Accelerator devices on the system. For example, /dev/fct* Option Description -c Attach only if clean. Quiet: disables the display of the progress bar and percentage. -q fio-beacon Description The fio-beacon utility enables all three LEDs on, to identify the specified IO Accelerator device.
Collecting fio-status Collecting fio-pci-check Collecting fio-pci-check -v Collecting fio-read-lebmap /dev/fct0 Collecting fio-read-lebmap -x /dev/stdout/dev/fct0 Collecting fio-read-lebmap -t /dev/fct0 Collecting fio-get-erase-count/dev/fct0 Collecting fio-get-erase-count -b /dev/fct0 Collecting lspci Collecting lspci -vvvvv Collecting lspci -tv Collecting messages file(s) Collecting procfusion file(s) Collecting lsmod Collecting uname -a Collecting hostname Collecting sar -r Collecting sar Collecting sar
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. The command displays a progress bar and percentage as it completes the process. NOTE: Before using this utility, be sure that the device you want to detach is not currently mounted and in use.
where is the name of the device node (/dev/fctx), where x indicates the device number: 0, 1, 2, and so on. For example, /dev/fct0 indicates the first IO Accelerator device installed on the system. Options Description -b Set the block (sector) size, in bytes or KiBytes (base 2). The default is 512 bytes. For example: -b 512B or -b 4K (B in 512B is optional). -f -q -s Force the format size, bypassing normal checks and warnings.
fio-snmp-agentx Description This utility is an SNMP subagent that implements the SNMP 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 [options] Options Description -f Forces the subagent to run in the foreground instead of as a daemon. -l : Log file to use. -s Sends errors to stderr instead of to syslog. fio-status Description Provides detailed information on installed devices.
CAUTION: Output Change Starting with version 3.0.0 and later, the standard formatting of fio-status output has changed. This will affect any custom management tools that used the output of this utility.
• PCIe bus current (average, maximum) • PCIe bus power (average, maximum) • PCIe power limit threshold (watts) • PCIe slot available power (watts) • PCIe negotiated link information (lanes and throughput) Block device information: • Manufacturer's code • Manufacturing date • Vendor and sub-vendor information • Format status and sector information (if device is attached) • FPGA ID and Low-level format GUID • PCIe slot available power • PCIe negotiated link information • Card tempera
CAUTION: If the device is in Read-only mode, perform a format using fio-format before running fio-sure-erase. The fio-sure-erase utility cannot erase the device if it is in Minimal mode. Updating the firmware might move the device out of Minimal Mode. If the device remains in Minimal mode, contact HP Support (http://www.hp.com/support) for assistance. IMPORTANT: Prior to reactivating the device, format the device with fio-format after running fio-sure-erase.
The following describes the steps taken in the Clear operation: 1. Creates a unity map of every addressable block (this allows fio-sure-erase to address every block, including previously unmapped bad blocks). 2. For each block, performs an erase cycle (every cell is pushed to 1). 3. Restores the bad block map. Formats the device (the purpose of this is to make the device usable again, the utility erases all of the headers during the clear).
CAUTION: • During a firmware upgrade, it is critical to maintain steady power or risk failure of the IO Accelerator device. Connecting a qualified UPS is recommended prior to performing a firmware upgrade. • It is critical to load the driver after each firmware upgrade step when scheduling sequential, multiple firmware upgrades (example: 1.2.7 to 2.1.0 to 2.3.1). If the driver is not loaded, the on-drive format will not be changed and there will be data loss.
Options Description -q Runs the update process without displaying the progress bar or percentage. -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): [[[[]:]]:][][.[]] -y Confirm all warning messages. 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. By pro-actively monitoring device age and health, you can ensure reliable performance over the intended product life.
block device, beyond specifying that the mount must be read-only. For example, under Linux, ext3 requires that -o ro, noload is used. The noload option directs the file system not to attempt to replay the journal. Read-only mode must be considered a final opportunity to migrate data off the device since device failure is more likely with continued use. The IO Accelerator might enter failure mode. In this case, the device is offline and inaccessible.
About flashback protection technology Like many other flash devices, NAND flash eventually fails with use. Those failures can be either permanent or temporary. Flashback Protection redundancy is designed to address those IO Accelerator chips that experience permanent failures, and provides additional protection above and beyond ECC for soft failures. Flashback technology provides a real-time RAID-like redundancy at the chip-level, without sacrificing user capacity or performance for fault tolerance.
Performance and tuning Introduction to performance and tuning HP IO Accelerator devices provide high bandwidth and high IOPS and are specifically designed to achieve low latency. As IO Accelerator devices improve in IOPS and low latency, the device performance may be limited by operating system settings and BIOS configuration. To take advantage of the revolutionary performance of IO Accelerator devices, you might have to tune these settings.
Setting NUMA affinity Servers with a NUMA (Non-Uniform Memory Access) architecture require special installation instructions in order to maximize ioMemory device performance. These servers include the HP ProLiant DL580 and HP DL980 Servers. On servers with NUMA architecture, during system boot, the BIOS on some systems will not distribute PCIe slots evenly among the NUMA nodes. Each NUMA node contains multiple CPUs.
NUMA configuration Introduction to NUMA architecture Servers with NUMA (Non-Uniform Memory Access) architecture require special installation instructions in order to maximize IO Accelerator device performance. These servers include the HP DL580 and the HP DL980 server. On servers with NUMA architecture, during system boot, the BIOS on some systems will not distribute PCIe slots evenly among the NUMA nodes. Each NUMA node contains multiple CPUs.
configuration creates a load balancing problem in the system when IO Accelerator devices are under heavy traffic. During these periods of high use, half of the processors in the system sit idle while the other half of the processors are 100% utilized, thus limiting the throughput of the IO Accelerator devices. To avoid this situation, you must manually configure the affinity of the IO Accelerator devices using the FIO_AFFINITY configuration parameter to distribute the work load across all NUMA nodes.
Resources Subscription service HP recommends that you register your product at the Subscriber’s Choice for Business website (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.
Regulatory information Safety and regulatory compliance For safety, environmental, and regulatory information, see Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the HP website (http://www.hp.com/support/Safety-Compliance-EnterpriseProducts). Turkey RoHS material content declaration Ukraine RoHS material content declaration Warranty information HP ProLiant and X86 Servers and Options (http://www.hp.
Support and other resources Before you contact HP Be sure to have the following information available before you call HP: • Active Health System log (HP ProLiant Gen8 or later products) Download and have available an Active Health System log for 3 days before the failure was detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning User Guide on the HP website (http://www.hp.com/go/ilo/docs).
providers or service partners) identifies that the repair can be accomplished by the use of a CSR part, HP will ship that part directly to you for replacement. There are two categories of CSR parts: • Mandatory—Parts for which customer self repair is mandatory. If you request HP to replace these parts, you will be charged for the travel and labor costs of this service. • Optional—Parts for which customer self repair is optional. These parts are also designed for customer self repair.
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.
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.
Support and other resources 67
Support and other resources 68
Acronyms and abbreviations ACPI Advanced Configuration and Power Interface DVFS dynamic voltage and frequency scaling IOPS input/output operations per second LEB Logical Erase Block LVM Logical Volume Manager MIB management information base NAND Not AND NUMA Non-Uniform Memory Architecture PSP HP ProLiant Support Pack RFC request for comments RHEL Red Hat Enterprise Linux RPM Red Hat Package Manager Acronyms and abbreviations 69
SMH System Management Homepage VSL virtual storage layer Acronyms and abbreviations 70
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index A about this guide 6 advanced NUMA configuration example 57 authorized reseller 61 B battery replacement notice 60 building a RAID 10 configuration across multiple IO Accelerator Duos 25 building driver from source package 14 building RPM package 14 C command-line utilities 35 common maintenance tasks 37 configuring RAID 23 configuring the SNMP master agent 28 configuring the SNMP subagent 29 contents summary 6 controlling driver loading 18 CSR (customer self repair) 61 customer self repair (CSR) 61
N T NAND flash and component failure 52 NUMA architecture 57 NUMA configuration 57 NUMA node override parameter 57 Taiwan battery recycling notice 60 technical support 61 telephone numbers 61 Trim support 26 troubleshooting SNMP 33 O one-time configuration 21 operating environment 9 overview 7 P PCIe power override, enabling 36 PCIe power, enabling 22 performance and tuning 55 performance and tuning, introduction 55 persistent configuration 21 phone numbers 61 R U uninstalling driver RPM package 38 u
