HP B- Accelerators Linux manual Introduction

Page 10

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).

The Gen8 adapter is provided in a c-Class Type B Mezzanine card form factor. It can only be installed in Type B mezzanine slots within the Gen 8 or later servers, enabling one IO Accelerator in a half-height Gen8 server.

The Type I mezz card and the Type B mezz card are distinguished by the mezzanine connector. The type B card is slightly larger than a Type I mezz card.

The amount of free RAM required by the driver depends on the size of the blocks used when writing to the drive. The smaller the blocks, the more RAM is required. The table below lists the guidelines for each 80GB of storage. For the latest information, see the QuickSpecs sheet to the HP IO Accelerator for HP BladeSystem c-Classat HP Customer Support (http://www.hp.com/support).

The Remote Power Cut Module for the c-Class blade mezzanine card provides a higher level of protection in the event of a catastrophic power loss (for example, a user accidentally pulls the wrong server blade out of the slot). The Remote Power Cut Module ensures in-flight writes are completed to NAND flash in these catastrophic scenarios. Without the Remote Power Cut Module, write performance is slower. Writes are not acknowledged until the data is written to the NAND module, thereby slowing performance. When the Remote Power Cut Module is installed, writes are acknowledged by the IO Accelerator controller to the driver. The IO Accelerator controller then completes the write to the NAND module.

The IO Accelerators (QK761A, QK762A, and QK763A) for Gen 8 BladeSystem c-Class have the power cut functionality embedded on the card. They offer the protection without requiring the remote power cut module.

NOTE: The Remote Power Cut Module is used only in the AJ878B and BK836A models. Without the Remote Power Cut Module, write performance is slower.

HP PCIe IO Accelerator minimum requirements

An open PCI-Express slot—The accelerator requires a minimum of one half-length, half-height slot with a x4 physical connector. All four lanes must be connected for full performance. HP PCIe IO Accelerator Duo requires a minimum of a full-height, half-length slot with an x8 physical connection. If your system is using PCI 1.1, all x8 signaling lanes must be connected for full performance. If your system is using PCI 2.0, for full performance you only have to connect x4 signaling lanes.

NOTE: For PCIe IO Accelerators, using PCIe slots greater than x4 does not improve performance.

NOTE: The power cut feature is built into PCIe IO Accelerators; therefore, no Remote Power Cut Module is necessary.

300 LFM of airflow at no greater than 50°C. To protect against thermal damage, the IO Accelerator also monitors the junction temperature of its controller. The temperature represents the internal temperature of the controller, and it is reported in fio-statusreport. The IO Accelerator begins throttling write performance when the junction temperature reaches 78°C. If the junction temperature continues to rise, the IO Accelerator shuts down when the temperature reaches 85°C.

NOTE: If you experience write performance throttling due to high temperatures, see your computer documentation for details on increasing airflow, including fan speeds.

Introduction 10

Image 10
Contents HP IO Accelerator Version 3.2.3 Linux User Guide Page Contents Maintenance Resources Contents summary About this guideOverview IntroductionProduct naming Performance attributes IO Accelerator capacity 320GB 640GB Models AJ878B BK836ASupported firmware revisions Required operating environmentSupported hardware Introduction Introduction Installing RPM packages on SUSE, RHEL, and OEL Software installationInstallation overview $ uname -rRpm -Uvh iomemory-vsl-kernel-version-VSL-version.x8664.rpm Rpm -Uvh fio*.rpmBuilding the IO Accelerator driver from source Building an RPM installation package$ rpmbuild --rebuild iomemory-vsl-VSL-version.src.rpm Upgrading device firmware from VSL 1.x.x or 2.x.x to Fio-bugreport Upgrading procedure$ rpm -qa grep -i iomemory $ rpm -e iomemory-vsl-2.6.18-194.el5-2.2.0.82-1.0 Fio-update-iodrive iodriveversion.fff$ modprobe iomemory-vsl Controlling IO Accelerator driver loading # Provides iomemory-vsl # Required-Start boot.udevLoading the IO Accelerator driver Fio-attach /dev/fct$ chkconfig --add iomemory-vsl Using the init script$ chkconfig --del iomemory-vsl # blacklist iomemory-vslMounting filesystems Setting the IO Accelerator driver optionsUsing module parameters Handling IO Accelerator driver unloadsUpgrading the firmware One-time configurationPersistent configuration $ modprobe iomemory-vsl auto-attach=0Using the Logical Volume Manager Enabling PCIe powerUsing the device as swap Options iomemoryvsl preallocatememory=1072,4997,6710,10345Device /dev/fio Configuring RAIDDevice partitions Etc/mdadm.conf$ mdadm --detail --scan Chkconfig boot.md on Chkconfig mdadmd on$ mdadm --assemble --scan Building a RAID 10 across multiple devices Fio-statusUnderstanding Discard Trim support Discard Trim on LinuxFiles and directories Setting up Snmp for LinuxSnmp details for Linux Snmp master agentYum install net-snmp rsync Configuring the Snmp master agentInstalling the Snmp subagent Snmp agentX subagentManually running the Snmp subagent Running and configuring the Snmp subagentSubagent log file Using the Snmp sample config files Enabling Snmp test modePCI0100.0 Setting up Snmp for Linux Troubleshooting Snmp Supported Snmp MIB fieldsSnmp MIB Device LED indicators MaintenanceMaintenance tools Command-line utilitiesEnabling PCIe power override Fio-update-iodriveOptions iomemory-vsl externalpoweroverride=value Common maintenance tasksEnabling the override parameter Unloading the IO Accelerator driver Uninstalling the IO Accelerator driver RPM packageDisabling auto attach Etc/modprobe.d/iomemory-vsl.conf Unmanaged shutdown issuesDisabling the driver Options iomemoryvsl autoattach=0Fio-attach UtilitiesUtilities reference Fio-attach device optionsFio-beacon device options Fio-beaconFio-bugreport Tmp/fio-bugreport-20100121.173256-sdv9ko.tar.bz2Fio-detach Fio-detach device options Fio-formatFio-format options device Fio-pci-check Fio-pci-check optionsFio-snmp-agentx options Fio-snmp-agentxFio-status Fio-status device optionsUtilities Fio-sure-erase Fio-sure-erase options device Fio-update-iodrive Fio-update-iodrive options iodriveversion.fff Domainbusslot.func Nand flash and component failure Monitoring IO Accelerator healthHealth metrics Health monitoring techniques About flashback protection technology Software RAID and health monitoringDisabling Dvfs Performance and tuningIntroduction to performance and tuning Limiting Apci C-statesSetting Numa affinity Setting the interrupt handler affinityIntroduction to Numa architecture Numa configurationAdvanced configuration example Numa node override parameter13,14,18,19 Resources Subscription serviceFor more information Warranty information Safety and regulatory complianceRegulatory information HP contact information Support and other resourcesBefore you contact HP Customer Self RepairRéparation par le client CSR Riparazione da parte del cliente Reparaciones del propio cliente Reparo feito pelo cliente Support and other resources Support and other resources Support and other resources Acronyms and abbreviations SMH Documentation feedback Index Uninstalling utilities