QLogic 7104-2M-CABLE InfiniBand cable

QLogic Host Channel Adapter and QLogic
OFED Software Install Guide
QLogic OFED Version 1.4
IB0056101-00 H
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no
responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its
use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications
described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no
representation nor warranty that such applications are suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
No part of this document may be copied nor reproduced by any means, nor translated nor transmitted to any magnetic
medium without the express written consent of QLogic Corporation. In accordance with the terms of their valid QLogic
agreements, customers are permitted to make electronic and paper copies of this document for their own exclusive
use.
The QHT7040, QHT7140, QLE7140, QLE7240, and QLE7280 QLogic Host Channel Adapters are covered by the
following patent: 7308535.
Document Revision History
Rev. 1.0, 8/20/2005
Rev. 1.1, 11/15/05
Rev. 1.2, 02/15/06
Rev. 1.3, Beta 1, 4/15/06
Rev 1.3, 6/15/06
Rev. 2.0 Beta, 8/15/06, QLogic Version Number IB0056101-00 A
Rev. 2.0 Beta 2 10/15/06, QLogic Version Number IB0056101-00 B
Rev. 2.0 11/30/06, QLogic Version Number IB0056101-00 C
Rev. 2.0 3/23/07, QLogic Version Number IB0056101-00 D
Rev. 2.1 8/24/07, QLogic Version Number IB0056101-00 E
Rev. 2.2 5/27/08, QLogic Version Number IB0056101-00 F
Rev. 2.2 9/5/08, QLogic Version Number IB0056101-00 G
Rev. QLogic OFED 1.4 4/30/09, QLogic Version Number IB0056101-00 H
Changes
ii
Sections Affected
Product name changed from InfiniPath to QLogic
OFED. Version number changed to 1.4. Instances
of InfiniPath changed where appropriate; some
filenames and output messages still have the old
name.
All
QLogic subnet manager name changed from Host
Subnet Manager (HSM) to QLogic Fabric Manager.
All
IB0056101-00 H
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Removed $ or # at beginning of lines indicating
All
commands. The #, if cut and pasted from the document, may be interpreted as a shell command.
Removed references to ipath_ether, now obsolete.
All
In the second bullet, removed references to Ethernet emulation stacks and TCP (related to
now-obsolete ipath_ether). Added that Infinipath uses a protocol that is optimized for MPI over
Verbs.
“Interoperability” on page 1-3
Changed the definition of #.
Table 1-1 on page 1-4
Updated list of product documentation.
“Documentation” on page 1-5
Updated contact information.
“Contact Information” on page 1-5
Combined What’s New in This Release and New
Features sections (now called Features). Updated
section with current release and feature information.
“Feature Overview” on page 2-1
Added Other Changes section.
Added Continued Support section (information
moved/added from What’s New in This Release
and New Features sections).
Removed Compiler Support and Supported Linux
Distributions and Kernel sections. This information
is still in Software Installation chapter.
Updated software components information.
“Features” on page 2-1
Modified installation checklist. Clarified which drivers are configured and which are optional. Added
two methods of installation to the list.
“Software Installation” on page 3-2
Reference to location
/sys/bus/pci/drivers/ib_ipath/00/
changed to
/sys/class/infiniband/ipath0/device/
boardversion
“Form Factors” on page 4-2
Deleted reference to MTRR BIOS setting.
“Configuring the BIOS” on page 4-4
Deleted paragraph about BIOS Setup utility.
Added a NOTE about the Page Attribute Table
(PAT) mechanism.
IB0056101-00 H
iii
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Replace EM64T with 64-bit Intel Xeon.
“Supported Linux Distributions” on page 5-2
Updated list of InfiniPath/OpenFabrics® distributions and kernels (Table 5-1).
Added NOTE that support for RHEL4 U4 and
SLES 1.0. has been removed.
Removed NOTE stating that Fedora Core 4 and
Fedora Core 5 are not supported.
Starting with “Choose the Appropriate Download
Files” on page 5-5, this section has been
changed/updated extensively. In general: OFED,
QLogic InfiniBand Fabric Suite, and Installer Tool
information has been added. RPM information has
been updated. ipath_ether has been removed.
“Software Installation” on page 5-1
Split the Install section into three separate sections.
“Software Installation” on page 5-1
“Configuring Drivers and Services” on page 6-1
“Installation Verification and Additional Settings” on
page 7-1
Added distribution identifiers rhel4, rhel5, and
sles10 (Table 5-2).
“Distribution Identifiers” on page 5-3
Updated compiler support information (moved
from Feature Overview section).
“Compiler Support” on page 5-3
Updated list of what to keep in mind when setting
up the environment.
“Set Up Your Environment” on page 5-3
Added a table of required OS packages
(Table 5-3).
Added a table of specific component requirements
(Table 5-4).
New section
“Install a Previous Version of QLogicIB-Basic” on
page 5-27
Consolidated and updated Configuring the InfiniPath Drivers and InfiniPath and OpenFabrics
Driver Overview; moved to new section.
6 Configuring Drivers and Services
Updated section
“InfiniPath and OpenFabrics Driver Overview” on
page 6-1
Consolidated section into an introduction; removed
configuration information and the NOTE stating
that the following instructions work for all distributions.
“OpenFabrics Drivers and Services Configuration
and Startup” on page 6-1
Page iv
IB0056101-00 H
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Added a last step to restart.
Updated the NOTE about setting datagram mode.
In the first paragraph, updated information about
where the package can be installed/enabled, and
when OpenSM is not needed.
“Configure the IPoIB Network Interface” on
page 6-2
“OpenSM” on page 6-3
Added second paragraph about the Installer tool.
Added third paragraph about rpm install with
OpenSM.
Added last paragraph about where to find more
information about OpenSM.
Updated the second paragraph to list with which
OCS downloads SRP is available.
“SRP” on page 6-4
New section
“Using QLogic SRP” on page 6-4
Added second, third, and fourth paragraphs to discuss the VNIC driver and the virtual Ethernet interface.
“Configuring and Administering the VNIC Interface” on page 6-6
Updated the output for the
ib_qlgc_vnic_query command in Step 1.
Added that the command in Step 5 must be done
as a root user.
Added instructions for setting up Intel® MPI.
“MPI over uDAPL” on page 6-13
Added more details about setting the switch MTU
default to 4K.
“Other Configuration: Changing the MTU Size” on
page 6-14
Changed section name from Configuring the
ib_ipath driver to Managing the Infinipath driver.
Updated section: this driver now runs as a system
service.
“Managing the InfiniPath Driver” on page 6-14
Split Stopping and Starting the InfiniPath Software
into two sections.
“Configure the InfiniPath Driver State” on
page 6-15
“Configure the InfiniPath Driver State” on
page 6-15
Changed commands for checking the configuration state and enabling/disabling the driver.
“Configure the InfiniPath Driver State” on
page 6-15
Removed paragraph about OpenSM.
“Start, Stop, or Restart InfiniPath” on page 6-15
Changed commands to restart the driver.
Noted that you do not have to be a root user to run
the command to determine which InfiniPath and
OpenFabric modules are running.
IB0056101-00 H
v
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
New section
“Unloading the Driver/Modules Manually” on
page 6-16
Changed name of Adapter Settings section.
“Adapter and Other Settings” on page 7-2
In the second bullet (IB MTU size), removed the
statements about 4K MTU, which no longer apply.
In the fourth bullet (MaxPayload size), changed
recommendation to using a size of 256.
Added fifth bullet (write combining).
Added sixth bullet (PCIe bus width).
In Step 4, added that missing RPMs can be found.
“Customer Acceptance Utility” on page 7-3
Deleted Troubleshooting item:
ifup on ipath_ether on SLES 10 Reports
"unknown device"
Appendix A
Deleted reference to MTRR BIOS setting.
“BIOS Settings” on page A-2
Deleted section Version Number Conflict with
opensm-* on RHEL5 Systems, and associated
subsections.
Was on page A-4.
Changed name of infinipath-kernel package
to kernel-ib package. Changed the associated
command.
“Missing Kernel RPM Errors” on page A-2
New section
“openmpi_gcc Fails to Install Because of Dependency on gfortran (RHEL 4)” on page A-4
Changed libgcc RPM name for RHEL4.
“mpirun Installation Requires 32-bit Support” on
page A-4
Changed glibc RPM name.
Added new Configuration Issues section and subsections.
“ibsrpdm Command Hangs when Two Adapters
are Installed but only Unit 1 is Connected to the
Switch” on page A-5
“Outdated ipath_ether Configuration Setup Generates Error” on page A-5
New Appendix for write combining. MTRR Mapping and Write Combining settings information
moved here and have been updated.
“Write Combining” on page B-1
New section
“PAT and Write Combining” on page B-2
Page vi
“Verify Write Combining is Working” on page B-1
“MTRR Mapping and Write Combining” on
page B-2
IB0056101-00 H
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Deleted entries pertaining to ipath_ether.
Table C-1 on page C-1
VNIC configuration file name changed to
qlgc_vnic.cfg. Added more information in the
Description column.
In the Description column for /etc/modprobe.conf and /etc/modprobe.conf.local, added that the PAT WC
option is set here.
Removed /etc/sysconfig/ics_inic.cfg
file.
Change main configuration file from /etc/sysconfig/infinipath to /etc/infiniband/openib.conf.
/etc/sysconfig/infinipath is still used to
set the ipath_mtrr script.
Removed /etc/sysconfig/network/ifcfg.template template.
VNIC config file sample file name changed to
qlgc_vnic.cfg.sample.
The name of the file that explains the entries in the
configuration file changed to
/usr/share/doc/initscripts-*/
sysconfig.txt.
Change name of Appendix RPM Descriptions to
Package Descriptions.
“Package Descriptions” on page D-1
Updated first paragraph to include information
about QLogicIB-Basic.
Updated tables of all RPMs. Moved all documentation RPMs together. New table for OpenSM-Devel
RPMs. Updated OtherMPIs.
Moved table “InfiniPath and OpenFabrics RPMs to
Use for Each Node in a Cluster” from Software
Installation section.
New section
“Package Names with the QLogicIB-Basic Download” on page D-1
Added “InfiniPath” to section title. Updated section
to add build identifiers to RPM name.
“InfiniPath RPM Version Numbers and Identifiers”
on page D-2
Moved information about non-InfiniPath component naming to a new section.
“OpenFabrics RPM Names” on page D-2
New section
“InfiniPath and OpenFabrics RPMs” on page D-3
IB0056101-00 H
vii
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Split Documentation and InfiniPath RPMs into multiple sections; updated all RPM names and
descriptions.
“Documentation RPMs” on page D-3
“InfiniPath RPMs” on page D-3
“Other Adapters” on page D-9
“Other MPIs” on page D-10
Moved information in first paragraph describing
when to install the RPMs in the following tables;
this information now proceeds the table to which it
applies.
“OpenFabrics RPMs” on page D-5
Removed OpenFabrics Documentation/RPMs
table.
Was Table C-5 on page C-4
Updated all RPM names so they are not version-specific.
Table D-5 on page D-5
Removed ib-bonding RPM.
Removed rhel4-ofed-* RPM.
Added compat-dapl* RPMs.
Added scsi-target-* RPM.
Added tgt-* RPM.
Modified all RPM names so they are not version-specific.
Table D-7 on page D-9
Added compat-dapl-devel-* RPM.
Removed ibsim-2.2* RPM.
Modified all RPM names so they are not version-specific.
Table D-8 on page D-9
Moved opensm-devel-* RPM to this table.
Modified all RPM names so they are not version-specific.
Table D-9 on page D-9
Modified all RPM names so they are not version-specific.
Table D-10 on page D-10
Added libmlx4-devel-* RPM.
Page viii
IB0056101-00 H
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Updated all RPM names so they are not version-specific.
Table D-11 on page D-10
Removed mpitest_mvapich_intel* RPM.
Removed mpitests_mvapich_pathscale*
RPM.
Removed mpitests_mvapich_pgi* RPM.
Added mpitests_mvapich2* RPM.
Added mvapich2_gcc-* RPM.
Added mvapich_gcc_qlc-* RPM.
Changed names/descriptions of mvapich RPM
files compiled with Intel, PathScale, and PGI.
Added openmpi_gcc_qlc-* RPM.
Changed names/descriptions of openmpi RPMs
compiled with Intel, PathScale, and PGI.
Changed name of qlogic-mpi-register-*
RPM.
Added table footnote about file names with -qlc.
Updated table footnote with latest compiler versions. Removed footnote about Intel-compiled versions. Updated footnote a.
IB0056101-00 H
ix
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
Notes
Page x
IB0056101-00 H
Table of Contents
1
Introduction
Who Should Read this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How this Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventions Used in this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
Feature Overview
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Continued Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
2-1
2-2
2-2
2-4
Step-by-Step Installation Checklist
Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
1-1
1-2
1-3
1-3
1-4
1-5
1-5
3-1
3-2
Hardware Installation
Hardware Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Form Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling and Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optical Fibre Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety with Electricity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unpacking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify the Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of the Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unpacking the QLogic Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IB0056101-00 H
4-1
4-1
4-2
4-3
4-4
4-4
4-5
4-5
4-5
4-5
4-8
xi
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Installation for QLE7240, QLE7280, or QLE7140 with PCI
Express Riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual Adapter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Installation for QHT7140 with HTX Riser . . . . . . . . . . . . . .
Hardware Installation for QLE7240, QLE7280, and QLE7140
Without a PCI Express Riser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Installation for the QHT7140 Without an HTX Riser . . . . . .
Switch Configuration and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling the Adapter to the InfiniBand Switch . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
4-9
4-9
4-9
4-12
4-15
4-16
4-17
4-17
4-18
Software Installation
Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Nodes in a Cluster Environment . . . . . . . . . . . . . . . . . . . . . .
Supported Linux Distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribution Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compiler Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Up Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Choose the Appropriate Download Files . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install QLogicIB-Basic with the Installer Tool . . . . . . . . . . . . . . . . . . . . . . . .
About rpm Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using rpm to Install InfiniPath and OpenFabrics . . . . . . . . . . . . . . . . .
RPM Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install QLogic OFED User-level Software with the rpm Command . . . . . . .
Rebuild or Reinstall the kernel-ib Driver with rpm After a Kernel
Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rebuild the kernel-ib Driver on an Unsupported Distribution or an
Unsupported Distribution/Kernel Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install QLogic OFED Using Rocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Frontend and Compute Nodes . . . . . . . . . . . . . . . . . . . . . . . . .
Rocks Installation on an Existing Frontend Node . . . . . . . . . . . . . . . .
Install QLogic OFED Using a Platform OCS Kit . . . . . . . . . . . . . . . . . . . . . .
Install the QLogic InfiniBand Fabric Suite Software . . . . . . . . . . . . . . . . . . .
Install Lustre Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installed Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remove Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstall Using the Installer Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstall InfiniPath and OpenFabrics RPMs . . . . . . . . . . . . . . . . . . . .
xii
4-9
5-1
5-1
5-2
5-3
5-3
5-3
5-5
5-8
5-14
5-15
5-17
5-18
5-20
5-20
5-21
5-21
5-22
5-23
5-24
5-24
5-24
5-26
5-26
5-26
IB0056101-00 H
A
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Uninstall Software with Rocks or Platform OCS . . . . . . . . . . . . . . . . .
Install a Previous Version of QLogicIB-Basic . . . . . . . . . . . . . . . . . . .
Downgrading RPMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
Configuring Drivers and Services
InfiniPath and OpenFabrics Driver Overview . . . . . . . . . . . . . . . . . . . . . . . .
OpenFabrics Drivers and Services Configuration and Startup. . . . . . . . . . .
Configure the IPoIB Network Interface . . . . . . . . . . . . . . . . . . . . . . . .
OpenSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using QLogic SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using OFED SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring and Administering the VNIC Interface . . . . . . . . . . . . . . .
MPI over uDAPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Configuration: Changing the MTU Size . . . . . . . . . . . . . . . . . . . . . . .
Managing the InfiniPath Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure the InfiniPath Driver State . . . . . . . . . . . . . . . . . . . . . . . . . .
Start, Stop, or Restart InfiniPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unloading the Driver/Modules Manually . . . . . . . . . . . . . . . . . . . . . . .
Further Information on Configuring and Loading Drivers . . . . . . . . . . . . . . .
7
6-1
6-1
6-2
6-3
6-4
6-4
6-4
6-6
6-13
6-14
6-14
6-15
6-15
6-16
6-17
Installation Verification and Additional Settings
LED Link and Data Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adapter and Other Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Acceptance Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A
5-26
5-27
5-27
7-1
7-2
7-3
Installation Troubleshooting
Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Spontaneously Reboots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Some HTX Motherboards May Need Two or More CPUs in Use . . . .
BIOS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable Advanced Configuration and Power Interface (ACPI) . . . . . . .
Issue with Supermicro® H8DCE-HTe and the QHT7040 . . . . . . . . . .
Software Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Missing Kernel RPM Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resolving Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
openmpi_gcc Fails to Install Because of Dependency on
gfortran (RHEL 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mpirun Installation Requires 32-bit Support . . . . . . . . . . . . . . . . . . .
Lockable Memory Error on Initial Installation of InfiniPath. . . . . . . . . .
IB0056101-00 H
A-1
A-1
A-1
A-2
A-2
A-2
A-2
A-2
A-3
A-4
A-4
A-4
xiii
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
Configuration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-5
ibsrpdm Command Hangs when Two Adapters are Installed but only Unit 1
is Connected to the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-5
Outdated ipath_ether Configuration Setup Generates Error . . . . .
A-5
B
Write Combining
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify Write Combining is Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAT and Write Combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTRR Mapping and Write Combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Edit BIOS Settings to Fix MTRR Issues . . . . . . . . . . . . . . . . . . . . . . .
Use the ipath_mtrr Script to Fix MTRR Issues. . . . . . . . . . . . . . . .
C
Configuration Files
D
Package Descriptions
Package Names with the QLogicIB-Basic Download. . . . . . . . . . . . . . . . . .
Different Nodes May Use Different RPMs . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath RPM Version Numbers and Identifiers . . . . . . . . . . . . . . . . . . . . .
OpenFabrics RPM Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath and OpenFabrics RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenFabrics RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other MPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
B-1
B-1
B-2
B-2
B-2
B-3
D-1
D-2
D-2
D-2
D-3
D-3
D-3
D-5
D-9
D-10
IB0056101-00 H
A
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
List of Figures
Figure
Page
4-1
QLogic QLE7280 with IBA7220 ASIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7
4-2
QLogic QLE7140 Card with Riser, Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7
4-3
QLogic QHT7040/QHT7140 Full and Low Profile Cards with Riser, Top View . . . .
4-8
4-4
PCIe Slot in a Typical Motherboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4-5
QLogic PCIe Host Channel Adapter Assembly with Riser Card . . . . . . . . . . . . . . . 4-11
4-6
Assembled PCIe Host Channel Adapter with Riser . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4-7
HTX Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4-8
QLogic QHT7140 Adapter with Riser Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4-9
Assembled QHT7140 with Riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4-10 QHT7140 Without Riser Installed in a 3U Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
List of Tables
Table
1-1
2-1
4-1
4-2
5-1
5-2
5-3
5-4
5-5
5-6
7-1
7-2
C-1
D-1
D-2
D-3
D-4
D-5
D-6
D-7
D-8
D-9
D-10
D-11
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QLogic Adapter Model Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adapter Models and Related Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QLogic InfiniBand Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath/OpenFabrics Supported Distributions and Kernels . . . . . . . . . . . . . . . . .
Distribution Identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Operating System Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specific Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Available Packages for QLogic OFED 1.4 Release . . . . . . . . . . . . . . . . . . . . . . . . .
INSTALL Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LED Link and Data Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ipath_checkout Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath-Devel/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
InfiniPath-MPI/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenFabrics/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenFabrics-Devel/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenSM/RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenSM-Devel/RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Host Channel Adapters/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Host Channel Adapters-Devel/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OtherMPIs/RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IB0056101-00 H
Page
1-4
2-3
4-1
4-3
5-2
5-3
5-4
5-4
5-5
5-13
7-1
7-4
C-1
D-3
D-3
D-4
D-4
D-5
D-8
D-9
D-9
D-9
D-10
D-10
xv
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
Notes
xvi
IB0056101-00 H
1
Introduction
This chapter describes the contents, intended audience, and organization of the
QLogic Host Channel Adapter and QLogic OFED Software Install Guide.
The QLogic Host Channel Adapter and QLogic OFED Software Install Guide
contains instructions for installing the QLogic host channel adapters and the
QLogic InfiniPath® and OpenFabrics® software. The following adapters are
covered in this guide:
„
„
„
„
QLE7140 PCI Express® (PCIe®)
QLE7240 PCI Express
QLE7280 PCI Express
QHT7040/QHT7140 HyperTransport Expansion (HTX™)
Who Should Read this Guide
This installation guide is intended for cluster administrators responsible for
installing the QLogic QLE7140, QLE7240, QLE7280 or QHT7040/QHT7140
adapter and QLogic InfiniPath software on their Linux® cluster. Additional detailed
installation information and instructions for administering the QLogic cluster can
be found in the QLogic Host Channel Adapter and QLogic OFED Software Users
Guide.
The QLogic Host Channel Adapter and QLogic OFED Software Install Guide
assumes that you are familiar with both cluster networking and the specific
hardware that you plan to use. Before installing the adapter, you should have
basic knowledge of your host and target operating systems, and working
knowledge of message passing concepts.
This document does not contain all the information you need to use basic Linux
commands or to perform all system administration tasks. For this information, see
the software documentation you received with your system.
IB0056101-00 H
1-1
S
1–Introduction
How this Guide is Organized
How this Guide is Organized
The QLogic Host Channel Adapter and QLogic OFED Software Install Guide is
organized into these sections:
1-2
„
Section 1, Introduction, contains an overview of the host channel adapters
and software, describes interoperability with other products, lists all related
documentation, and provides QLogic contact information.
„
Section 2, Feature Overview, contains features for this release, the
supported QLogic adapter models, supported distributions and kernels, and
a list of the software components.
„
Section 3, Step-by-Step Installation Checklist, provides a high-level
overview of the hardware and software installation procedures.
„
Section 4, Hardware Installation, includes instructions for installing the
QLogic QLE7140, QLE7240, QLE7280, QHT7040, and QHT7140 host
channel adapters.
„
Section 5, Software Installation, includes instructions for installing QLogic
OFED 1.4, which includes the QLogic InfiniPath® and OpenFabrics software.
„
Section 6, Configuring Drivers and Services, includes instructions for
configuring and using the drivers and services available with QLogic
OFED 1.4.
„
Section 7, Installation Verification and Additional Settings, provides
instructions for verifying that the software has been properly installed, the
drivers are loaded, and that the fabric is active and ready to use. Information
on adapter performance tuning is also provided.
„
Appendix A, Installation Troubleshooting, contains troubleshooting
information about issues that may occur during installation.
„
Appendix B, Write Combining, contains information about settings that will
ensure better performance.
„
Appendix C, Configuration Files, contains descriptions of the configuration
and configuration template files used by the QLogic InfiniPath and
OpenFabrics software.
„
Appendix D, Package Descriptions, describes the InfiniPath and
OpenFabrics software packages.
„
Index lists major subjects and concepts with page numbers for easy
reference.
IB0056101-00 H
A
1–Introduction
Overview
Overview
The material in this documentation pertains to a QLogic OFED cluster. A cluster is
defined as a collection of nodes, each attached to an InfiniBand™-based fabric
through the QLogic interconnect. The nodes are Linux-based computers, each
having up to 16 processors.
The QLogic host channel adapters are InfiniBand 4X. The Double Data Rate
(DDR) QLE7240 and QLE7280 adapters have a raw data rate of 20Gbps (data
rate of 16Gbps). For the Single Data Rate (SDR) adapters, the QLE7140 and
QHT7140, the raw data rate is 10Gbps (data rate of 8Gbps). The QLE7240 and
QLE7280 can also run in SDR mode.
The QLogic adapters utilize standard, off-the-shelf InfiniBand 4X switches and
cabling. The QLogic interconnect is designed to work with all InfiniBand-compliant
switches.
NOTE:
If you are using the QLE7240 or QLE7280, and want to use DDR mode,
then DDR-capable switches must be used.
QLogic OFED OpenFabrics software is interoperable with other vendors’
InfiniBand host channel adapters running compatible OpenFabrics releases.
There are several options for subnet management in your cluster:
„
Use the embedded Subnet Manager (SM) in one or more managed switches
supplied by your InfiniBand switch vendor.
„
Use a host-based Subnet Manager. QLogic provides one, QLogic Fabric
Manager, as a part of the QLogic InfiniBand Fabric Suite download.
„
Use the Open source Subnet Manager (OpenSM) component of
OpenFabrics.
Interoperability
QLogic InfiniPath participates in the standard InfiniBand subnet management
protocols for configuration and monitoring. Note that:
„
InfiniPath OpenFabrics (including Internet Protocol over InfiniBand (IPoIB))
is interoperable with other vendors’ InfiniBand adapters running compatible
OpenFabrics releases.
„
The QLogic MPI stack is not interoperable with other InfiniBand host channel
adapters and target channel adapters. Instead, it uses an
InfiniBand-compliant, vendor-specific protocol that is highly optimized for
QLogic MPI and MPI over Verbs.
IB0056101-00 H
1-3
S
1–Introduction
Conventions Used in this Guide
NOTE:
See the OpenFabrics web site at www.openfabrics.org for more information
on the OpenFabrics Alliance.
Conventions Used in this Guide
This guide uses the typographical conventions listed in Table 1-1.
Table 1-1. Typographical Conventions
Convention
command
Fixed-space font is used for literal items such as commands, functions, programs, files and pathnames, and program output.
variable
Italic fixed-space font is used for variable names in programs and
command lines.
concept
Italic font is used for emphasis and concepts, as well as for documentation names/titles.
user input
Bold fixed-space font is used for literal items in commands or constructs that you type.
$
Indicates a command line prompt.
#
Indicates a command line prompt as a root user.
[]
Brackets enclose optional elements of a command or program construct.
...
Ellipses indicate that a preceding element can be repeated.
>
A right caret identifies the cascading path of menu commands used
in a procedure.
QLogic
OFED 1.4
NOTE:
1-4
Meaning
The current version number of the software included in this documentation.
Indicates important information.
IB0056101-00 H
A
1–Introduction
Documentation
Documentation
The product documentation includes:
„
„
„
„
„
„
„
The QLogic Host Channel Adapter and QLogic OFED Software Install Guide
The QLogic Host Channel Adapter and QLogic OFED Software Users Guide
The QLogic Fabric Software Installation Guide
The QLogic ULP Configuration Guide
Release Notes
Quick Start Guide
Readme file
For more information on system administration, using the QLogic
Message-Passing Interface (MPI), and troubleshooting adapter hardware and
software, see the QLogic Host Channel Adapter and QLogic OFED Software
Users Guide.
Contact Information
Support Headquarters
QLogic Corporation
4601 Dean Lakes Blvd
Shakopee, MN 55379
USA
QLogic Web Site
www.qlogic.com
Technical Support Web Site
support.qlogic.com
Technical Support Email
support@qlogic.com
Technical Training Email
tech.training@qlogic.com
Additional contact information is available from the Contact Support area of the Technical Support Web Site.
IB0056101-00 H
1-5
1–Introduction
Contact Information
S
Notes
1-6
IB0056101-00 H
2
Feature Overview
This section contains the features for this release, the supported QLogic adapter
models, supported distributions and kernels, and a list of the software
components.
Features
The QLogic OFED 1.4 software release contains the complete OFED 1.4, plus
additional QLogic improvements, including an enhanced QLogic Host Channel
Adapter driver. The InfiniPath 2.3 components (libraries, QLogic
Message-Passing Interface/Performance Scaled Messaging (MPI/PSM), and
utilities) are also included. QLogic also supplies MVAPICH and OpenMPI
compiled with new versions of four different compilers (see the following list).
The following features and enhancements are included in the QLogic OFED 1.4
release:
„
Installation improvements. A single software load is provided for InfiniBand
host channel adapters from QLogic and other vendors supported by OFED.
The software is available in the following package formats:
‰
Text User Interface (TUI) installer (with the QLogicIB-Basic download).
TUI is used for installation on smaller clusters. Software can be
installed either by itself or through FastFabric™ (if the QLogic
InfiniBand Fabric Suite (IFS) is purchased).
‰
Software packaged for use with the rpm install method.
‰
A subset of the software (the accelerated MPI stack, precompiled
versions of MVAPICH and Open MPI, and other user-level tools) can
be installed on top of stock OFED or on an IB-enabled distribution.
‰
Software packaged for the Rocks installation method.
‰
Software packaged for the Platform Open Cluster Stack (OCS)
installation method.
„
Write Combining (WC) mappings for the PIO buffers is now configured by
default using the x86 Page Attribute Table (PAT) mechanism.
„
MVAPICH and OpenMPI are compiled with new versions of the following
compilers: GCC, PGI, Intel®, and PathScale™.
IB0056101-00 H
2-1
S
2–Feature Overview
Features
„
The QLogic InfiniBand Fabric Suite (IFS) is available separately for
purchase. It includes FastFabric, the QLogic Fabric Manager, Fabric Viewer,
and the InfiniServ Host Software. The QLogic OFED 1.4 software is
supported by IFS.
„
Support for new compiler versions (PathScale 3.x, PGI 7.x, PGI 8.x,
Intel 10.x, Intel 11.x)
„
Support for new Linux distributions, including RHEL 4 U7
„
Performance enhancements and bug fixes
Other Changes
The following changes have been made to the software since the last release:
„
ipath_ether Ethernet emulation has been removed; IPoIB-CM can be
used instead.
„
The /etc/init.d/infinipath command to start the InfiniPath service
has been replaced by the /etc/init.d/openibd command.
„
The infinipath-kernel RPM no longer exists; it has been integrated
into the kernel-ib RPM.
Continued Support
The following features are still supported in this release:
„
Multiple high-performance native PSM MPI implementations. (PSM is
QLogic’s accelerated library for high performance MPIs). In addition to
QLogic MPI, the currently supported MPI implementations are HP-MPI,
Open MPI, MVAPICH, and Scali (Platform). Open MPI provides MPI-2
functionality, including one-sided operations and dynamic processes. These
all offer the same high performance as QLogic MPI.
QLogic MPI can be run exclusively on a single node without the installation
of the host channel adapter hardware.
2-2
„
Dual PCIe QLogic adapters per node.
„
4K Maximum Transfer Unit (MTU) is supported and is on by default. To take
advantage of 4KB MTU, use a switch that supports 4KB MTU. QLogic also
supports 2KB switches, as well as 4KB MTU switches configured for 2KB
MTU. QLogic switches with firmware version 4.2.x or later are
recommended.
IB0056101-00 H
A
2–Feature Overview
Features
This version of the QLogic OFED software provides support for all of the QLogic
adapters in Table 2-1.
Table 2-1. QLogic Adapter Model Numbers
QLogic Model
Number
Description
QHT7040
Single port 10Gbps SDR 4X InfiniBand to HTX adapter. For
systems with HTX expansion slots.
QHT7140 a
Single port 10Gbps SDR 4X InfiniBand to HTX adapter. For
systems with HTX expansion slots.
QLE7140
Single port 10Gbps SDR 4X InfiniBand to PCI Express x8
adapter. Supported on systems with PCI Express (PCIe) x8 or
x16 slots.
QLE7240
Single port 20Gbps DDR 4X InfiniBand to PCI Express x8
adapter. Supported on systems with PCI Express x8 or
x16 slots.
QLE7280
Single port 20Gbps DDR 4X InfiniBand to PCI Express x16
adapter. Supported on systems with PCI Express x16 slots.
The QLE7280 is backward compatible; it can also be used with
PCIe adapters that connect to x8 slots.
Table Notes
PCIe is Gen 1
a
The QHT7140 has a smaller form factor than the QHT7040, but is otherwise the same. Throughout
this document, the QHT7040 and QHT7140 are collectively referred to as the QHT7140 unless
otherwise noted.
Additional up-to-date information can be found on the QLogic web site,
specifically:
„
The high performance computing page at
www.qlogic.com/Products/HPC_products_landingpage.aspx
„
The InfiniBand host channel adapter page at
www.qlogic.com/Products/HPC_products_infipathhcas.aspx
IB0056101-00 H
2-3
S
2–Feature Overview
Software Components
Software Components
This release includes all of OFED 1.4 with enhancements (QLogic OFED 1.4),
including a new version of the VNIC tools and driver, and support for the QHT7xxx
and QLE7xxx adapters. The software includes the QLogic InfiniPath Host
Channel Adapter driver, libraries, QLogic MPI, Subnet Management Agent, and
associated utilities.
Included components are:
„
InfiniPath driver
„
InfiniPath libraries, utilities, configuration, and support tools, including
ipath_checkout, ipath_control, ipath_pkt_test, and
ipathstats
„
QLogic MPI
„
PSM support for accelerated MPI
„
OpenMPI and MVAPICH (with PSM support) built with the GNU, PGI,
PathScale, and Intel compilers, with corresponding mpitests and
mpi-selector
„
QLogic MPI benchmarks and utilities
„
OpenFabrics protocols, libraries, and utilities
„
QLogic VNIC module
„
QLogic IB tools
This release provides support for the following protocols and transport services:
„
„
„
„
„
IPoIB (TCP/IP networking in either Connected or Datagram mode)
Sockets Direct Protocol (SDP)
Open source Subnet Manager (OpenSM)
Reliable Datagram Sockets (RDS)
iSCSI Extensions for RDMA (iSER)
This release supports two versions of SCSI RDMA Protocol (SRP):
„
„
OFED SRP
QLogic SRP
No support is provided for Reliable Datagram (RD).
More details about the hardware and software can be found in Section 4 and
Section 5.
2-4
IB0056101-00 H
3
Step-by-Step
Installation Checklist
This section provides an overview of the hardware and software installation
procedures. Detailed steps are found in Section 4 “Hardware Installation” and
Section 5 “Software Installation”.
Hardware Installation
The following steps summarize the basic hardware installation procedure:
1.
Check that the adapter hardware is appropriate for your platform. See
Table 4-1.
2.
Check to see that you have the appropriate cables and switches, as
described in “Cabling and Switches” on page 4-3.
3.
Check to see that you are running a supported Linux distribution/kernel. See
Table 5-1.
4.
Verify that the BIOS for your system is configured for use with the QLogic
adapter. See “Configuring the BIOS” on page 4-4.
5.
Following the safety instructions in “Safety with Electricity” on page 4-5.
Unpack the adapter (“Unpacking Information” on page 4-5) and verify the
package contents.
6.
Install the adapter by following the instructions in “Hardware Installation” on
page 4-9.
7.
Cable the adapter to the switch, as described in “Cabling the Adapter to the
InfiniBand Switch” on page 4-17. Check that all InfiniBand switches are
configured.
8.
Follow the steps in “Completing the Installation” on page 4-18 to finish the
installation.
IB0056101-00 H
3-1
S
3–Step-by-Step Installation Checklist
Software Installation
Software Installation
The following steps summarize the basic QLogic OFED 1.4 software installation
and startup. These steps must be performed on each node in the cluster.
3-2
1.
Make sure that the host channel adapter hardware installation has been
completed according to the instructions in “Hardware Installation” on
page 4-1.
2.
Verify that the Linux kernel software is installed on each node in the cluster.
The required kernels and supported Linux distributions for both QLogic
InfiniPath and OpenFabrics are defined in Table 5-1.
3.
Make sure that your environment has been set up as described in “Set Up
Your Environment” on page 5-3.
4.
Download your version of the QLogic InfiniPath/OpenFabrics software from
the QLogic web site to a local server directory. See “Choose the Appropriate
Download Files” on page 5-5.
5.
Install the selected packages on each cluster node using the corresponding
method as described in one of the following sections:
„
“Install QLogicIB-Basic with the Installer Tool” on page 5-8
„
“Using rpm to Install InfiniPath and OpenFabrics” on page 5-15
„
“Install QLogic OFED User-level Software with the rpm Command” on
page 5-18
„
“Install QLogic OFED Using Rocks” on page 5-21
„
“Install QLogic OFED Using a Platform OCS Kit” on page 5-23
„
“Install the QLogic InfiniBand Fabric Suite Software” on page 5-24
6.
The system can be rebooted after all the software has been installed.
7.
The configuration file for the ib_ipath driver is set up correctly at
installation and is loaded automatically during system boot once the RPMs
have been installed. However, if you want to change the configuration file,
see “Managing the InfiniPath Driver” on page 6-14.
8.
If you want to configure the optional OpenFabrics driver ipoib (and it has
not been configured with the Install tool), or if you have used the rpm install
method, configure the driver as described in “Configure the IPoIB Network
Interface” on page 6-2.
9.
If you want to use the optional OpenFabrics services (OpenSM, SRP,or
VNIC), configure them as described in “OpenSM” on page 6-3, “SRP” on
page 6-4, or “Configuring and Administering the VNIC Interface” on
page 6-6.
IB0056101-00 H
A
3–Step-by-Step Installation Checklist
Software Installation
10.
Check the system state by observing the LEDs. See “LED Link and Data
Indicators” on page 7-1.
11.
You can optimize your system and adapter for the best performance. See
“Adapter and Other Settings” on page 7-2. Also see the Performance
Settings and Management Tips section in the QLogic Host Channel Adapter
and QLogic OFED Software Users Guide.
12.
Perform the recommended health checks. See “Customer Acceptance
Utility” on page 7-3.
13.
After installing the QLogic InfiniPath and OpenFabrics software, refer to the
QLogic Host Channel Adapter and QLogic OFED Software Users Guide for
more information about using QLogic InfiniPath, QLogic MPI, and
OpenFabrics products. Refer to the QLogic ULP and Tools Reference Guide
for more information about configuring and using QLogic SRP, QLogic VNIC,
and the Enablement Tools. The QLogic Fabric Software Installation Guide
also has information on installing the QLogic InfiniBand Fabric Suite.
IB0056101-00 H
3-3
3–Step-by-Step Installation Checklist
Software Installation
S
Notes
3-4
IB0056101-00 H
4
Hardware Installation
This section lists the requirements and provides instructions for installing the
QLogic InfiniPath Interconnect adapters. Instructions are included for the QLogic
DDR PCI Express adapters, the QLE7240 and QLE7280; the QLogic PCIe
adapter and PCIe riser card, QLE7140; and the QHT7040 or QHT7140 adapter
hardware and HTX riser card. These components are collectively referred to as
the adapter and the riser card in the remainder of this document.
The adapter is a low-latency, high-bandwidth, high message rate cluster
interconnect for InfiniBand. The QLogic interconnect is InfiniBand 4X, with a raw
data rate of 20Gbps (data rate of 16Gbps) for the QLE7240 and QLE7280; and
10Gbps (data rate of 8Gbps) for the QLE7140, QHT7040, and QHT7140.
OpenFabrics is interoperable with other vendors’ InfiniBand host channel
adapters running compatible OpenFabrics releases.
Hardware Installation Requirements
This section lists hardware and software environment requirements for installing
the QLogic QLE7240, QLE7280, QLE7140, QHT7040, or QHT7140.
Hardware
QLogic interconnect adapters are for use with UL listed computers. The following
statement is true for all the adapters:
This device complies with part 15 of the FCC Rules. Operation is subject to
the following two conditions: (1) This device may not cause harmful
interference, and (2) this device must accept any interference received,
including interference that may cause undesired operations.
Different adapters work on different platforms. Table 4-1 shows the relationship
between the adapter model and different types of motherboards.
Table 4-1. Adapter Models and Related Platforms
IB0056101-00 H
QLogic
Model
Number
Platform
QLE7240
PCI Express systems
Standard PCI Express x8 or x16 slot
QLE7280
PCI Express systems
Standard PCI Express x16 slot
Plugs Into
4-1
S
4–Hardware Installation
Hardware Installation Requirements
Table 4-1. Adapter Models and Related Platforms (Continued)
QLogic
Model
Number
Platform
QLE7140
PCI Express systems
Standard PCI Express x8 or x16 slot
QHT7040
Motherboards with HTX connectors
HyperTransport HTX slot
QHT7140
Motherboards with HTX connectors
HyperTransport HTX slot
Plugs Into
Installation of the QLE7240, QLE7280, QLE7140, QHT7040, or QHT7140 in a 1U
or 2U chassis requires the use of a riser card. See Figure 4-4 for an illustration of
a PCI Express (PCIe) slot in a typical motherboard. See Figure 4-7 for an
illustration of an HTX slot for a typical AMD Opteron™ motherboard.
The motherboard vendor is the optimal source for information about the layout
and use of HyperTransport and PCI Express-enabled expansion slots on
supported motherboards.
Form Factors
The QLE7240, QLE7280, and QLE7140 are the model numbers for the adapters
that ship in the standard PCI Express half-height, short-form factor. These
adapters can be used with either full-height or low-profile face plates.
The QHT7040 is the model number for the adapter that ships in the HTX
full-height factor. The HTX low-profile form factor is referred to as the QHT7140. It
is the same as the QHT7040, except for its more compact size. In either case, the
adapter is backward and forward compatible for the motherboards in which it is
supported. The QHT7040 and QHT7140 HTX adapters are collectively referred to
as the QHT7140 unless otherwise stated.
When the QHT7040 or QHT7140 adapter is installed with the riser card, it may
prevent some or all of the other PCI expansion slots from being used, depending
on the form factor of the adapter and motherboard.
Run ipath_control -i to see information on which form adapter is installed.
The file /sys/class/infiniband/ipath0/device/boardversion
contains the same information. For more information, see the Useful Programs
and Files appendix in the QLogic Host Channel Adapter and QLogic OFED
Software Users Guide.
4-2
IB0056101-00 H
A
4–Hardware Installation
Hardware Installation Requirements
Cabling and Switches
The cable installation uses a standard InfiniBand (IB) 4X cable. Any InfiniBand
cable that has been qualified by the vendor should work. For SDR, the longest
passive copper IB cable that QLogic has currently qualified is 20 meters. For
DDR-capable adapters and switches, the DDR-capable passive copper cables
cannot be longer than 10 meters. Active cables can eliminate some of the cable
length restrictions.
InfiniBand switches are available through QLogic.
NOTE:
If you are using the QLE7240 or QLE7280 and want to use DDR mode, then
DDR-capable switches must be used.
The copper cables listed in Table 4-2 are available from QLogic.
Table 4-2. QLogic InfiniBand Cables
Product Number
Description
7104-1M-Cable
4x-4x cable—1 meter
7104-2M-Cable
4x-4x cable—2 meters
7104-3M-Cable
4x-4x cable—3 meters
7104-4M-Cable
4x-4x cable—4 meters
7104-5M-Cable
4x-4x cable—5 meters
7104-6M-Cable
4x-4x cable—6 meters
7104-7M-Cable
4x-4x cable—7 meters
7104-8M-Cable
4x-4x cable—8 meters
7104-9M-Cable
4x-4x Cable—9 meters
7104-10M-Cable
4x-4x cable—10 meters
7104-12M-Cable
4x-4x cable—12 meters (SDR only)
7104-14M-Cable
4x-4x cable—14 meters (SDR only)
7104-16M-Cable
4x-4x cable—16 meters (SDR only)
7104-18M-Cable
4x-4x cable—18 meters (SDR only)
For cabling instructions, see “Cabling the Adapter to the InfiniBand Switch” on
page 4-17.
IB0056101-00 H
4-3
4–Hardware Installation
Hardware Installation Requirements
S
Optical Fibre Option
The QLogic adapter also supports connection to the switch by means of optical
fibres through optical media converters such as the EMCORE™ QT2400. Not all
switches support these types of convertors. For more information on the
EMCORE convertor, see www.emcore.com.
Intel® and Zarlink™ also offer optical cable solutions. See www.intel.com and
www.zarlink.com for more information.
Configuring the BIOS
To achieve the best performance with QLogic adapters, you need to configure
your BIOS with specific settings. The BIOS settings, which are stored in
non-volatile memory, contain certain parameters characterizing the system. These
parameters may include date and time, configuration settings, and information
about the installed hardware.
NOTE:
The Advanced Configuration and Power Interface (ACPI) BIOS option must
be enabled.
For more information, see “Enable Advanced Configuration and Power Interface
(ACPI)” on page A-2 and the Troubleshooting section of the QLogic Host Channel
Adapter and QLogic OFED Software Users Guide.
Some other BIOS settings can be adjusted for better adapter performance. See
“Adapter and Other Settings” on page 7-2.
For specific instructions about BIOS settings, follow the hardware documentation
that came with your system.
NOTE:
The x86 Page Attribute Table (PAT) mechanism that allocates Write
Combining (WC) mappings for the Programmed Input/Output (PIO) buffers
has been added and is now the default. This was previously a BIOS setting.
For more information, see “Write Combining” on page B-1.
4-4
IB0056101-00 H
A
4–Hardware Installation
Safety with Electricity
Safety with Electricity
Observe these guidelines and safety precautions when working around computer
hardware and electrical equipment:
„
Locate the power source shutoff for the computer room or lab where you are
working. This is where you will turn OFF the power in the event of an
emergency or accident. Never assume that power has been disconnected
for a circuit; always check first.
„
Do not wear loose clothing. Fasten your tie or scarf, remove jewelry, and roll
up your sleeves. Wear safety glasses when working under any conditions
that might be hazardous to your eyes.
„
Shut down and disconnect the system’s power supply from AC service
before you begin work, to insure that standby power is not active. Power off
all attached devices such as monitors, printers, and external components.
Note that many motherboards and power supplies maintain standby power
at all times. Inserting or removing components while standby is active can
damage them.
„
Use normal precautions to prevent electrostatic discharge, which can
damage integrated circuits.
Unpacking Information
This section provides instructions for safely unpacking and handling the QLogic
adapter. To avoid damaging the adapter, always take normal precautions to avoid
electrostatic discharge.
Verify the Package Contents
The QLogic adapter system should arrive in good condition. Before unpacking,
check for any obvious damage to the packaging. If you find any obvious damage
to the packaging or to the contents, please notify your reseller immediately.
List of the Package Contents
The package contents for the QLE7240 adapter are:
„
„
„
QLogic QLE7240
Additional short bracket
Quick Start Guide
Standard PCIe risers can be used, typically supplied by your system or
motherboard vendor.
IB0056101-00 H
4-5
S
4–Hardware Installation
Unpacking Information
The package contents for the QLE7280 adapter are:
„
„
„
QLogic QLE7280
Additional short bracket
Quick Start Guide
Standard PCIe risers can be used, typically supplied by your system or
motherboard vendor.
The package contents for the QLE7140 adapter are:
„
„
QLogic QLE7140
Quick Start Guide
Standard PCIe risers can be used, typically supplied by your system or
motherboard vendor. The contents are illustrated in Figure 4-2.
The package contents for the QHT7140 adapter are:
„
„
„
QLogic QHT7140
HTX riser card for use in 1U or 2U chassis
Quick Start Guide
The contents are illustrated in Figure 4-3.
The IBA6120, IBA6110, and IBA7220 are the QLogic ASICs, which are the central
components of the interconnect. The location of the IBA7220 ASIC on the adapter
is shown in Figure 4-1. The location of the IBA6120 ASIC on the adapter is shown
in Figure 4-2. The location of the IBA6110 ASIC on the adapter is shown in
Figure 4-3.
4-6
IB0056101-00 H
A
4–Hardware Installation
Unpacking Information
PCI Express
Edge Connectors
InfiniBand
Connector
Face Plate
IBA7220 ASIC
Figure 4-1. QLogic QLE7280 with IBA7220 ASIC
PCI Express Riser Card. Not
supplied; shown for reference.
PCI Express
Edge Connectors
InfiniBand
Connector
IBA6120 ASIC
Face Plate
Figure 4-2. QLogic QLE7140 Card with Riser, Top View
IB0056101-00 H
4-7
S
4–Hardware Installation
Unpacking Information
HTX Riser Card
HTX Edge
Connectors
InfiniBand
Connector
IBA6110 ASIC
QHT7140 Low
Profile Card
Face Plate
PathScale
InfiniBand
Connector
Face Plate
PathScale
QHT7040 Full Height
Short Card
Figure 4-3. QLogic QHT7040/QHT7140 Full and Low Profile Cards with Riser, Top
View
Unpacking the QLogic Adapter
Follow these steps when unpacking the QLogic adapter:
4-8
1.
When unpacking, ground yourself before removing the QLogic adapter from
the anti-static bag.
2.
Grasping the QLogic adapter by its face plate, pull the adapter out of the
anti-static bag. Handle the adapter only by its edges or the face plate. Do not
allow the adapter or any of its components to touch any metal parts.
3.
After checking for visual damage, store the adapter and the riser card in their
anti-static bags until you are ready to install them.
IB0056101-00 H
A
4–Hardware Installation
Hardware Installation
Hardware Installation
This section contains hardware installation instructions for the QLE7240,
QLE7280, QLE7140, QHT7040, and QHT7140.
Hardware Installation for QLE7240, QLE7280, or QLE7140
with PCI Express Riser
Installation for the QLE7240, QLE7280, and QLE7140 is similar. The following
instructions are for the QLE7140, but can be used for any of these three adapters.
Most installations will be in 1U and 2U chassis, using a PCIe right angle riser card.
This results in an installation of the adapter that is parallel to the motherboard.
This type of installation is described first. Installation in a 3U chassis is described
in “Hardware Installation for the QHT7140 Without an HTX Riser” on page 4-16.
Installing the QLogic QLE7140 in a 1U or 2U chassis requires a PCIe right angle
riser card.
A taller riser card can be used if necessary. The QLE7140 can connect to any of
the standard compatible PCI Express riser cards.
Dual Adapter Installation
If you have a motherboard with dual PCIe slots, dual adapters can be installed.
The adapters must match. For example, on a motherboard with two x16 slots,
dual QLE7280 adapters can be installed, but not a QLE7240 adapter and a
QLE7280 adapter. Check the design of your motherboard to see how riser cards
can be used.
Follow the instructions in “Installation Steps” on page 4-9.
See the Using MPI section in the QLogic Host Channel Adapter and QLogic
OFED Software Users Guide for information on using the IPATH_UNIT
environment variable to control which host channel adapter to use.
Installation Steps
To install the QLogic adapter with a PCIe riser card:
1.
The BIOS should already be configured properly by the motherboard
manufacturer. However, if any additional BIOS configuration is required, it
usually needs to be done before installing the QLogic adapter. See
“Configuring the BIOS” on page 4-4.
2.
Shut down the power supply to the system into which you will install the
QLogic adapter.
3.
Take precautions to avoid electrostatic damage (ESD) to the cards by
properly grounding yourself or touching the metal chassis to discharge static
electricity before handling the cards.
IB0056101-00 H
4-9
S
4–Hardware Installation
Hardware Installation
4.
Remove the cover screws and cover plate to expose the system’s
motherboard. For specific instructions on how to do this, follow the hardware
documentation that came with your system.
5.
Locate the PCIe slot on your motherboard. Note that the PCIe slot has two
separate sections, with the smaller slot opening located towards the front
(see Figure 4-4). These two sections correspond to the shorter and longer
connector edges of the adapter and riser.
PCIe slot in
typical motherboard
Figure 4-4. PCIe Slot in a Typical Motherboard
4-10
6.
Determine if a blanking panel is installed in your chassis. If it is, remove it so
that the InfiniBand connector will be accessible. Refer to your system vendor
instructions for how to remove the blanking panel.
7.
Remove the QLogic adapter from the anti-static bag.
8.
Locate the face plate on the connector edge of the card.
IB0056101-00 H
A
4–Hardware Installation
Hardware Installation
9.
Connect the QLogic adapter and PCIe riser card together, forming the
assembly that you will insert into your motherboard. First, visually line up the
adapter slot connector edge with the edge connector of the PCIe riser card
(see Figure 4-5).
PCIe Riser Card
QLogic Adapter
Face Plate
LEDs
InfiniBand connector
Figure 4-5. QLogic PCIe Host Channel Adapter Assembly with Riser Card
10.
Holding the QLogic adapter by its edges, carefully insert the card slot
connector into the PCIe riser card edge connector, as show in Figure 4-5.
The result is a combined L-shaped assembly of the PCIe riser card and
QLogic adapter. This assembly is what you will insert into the PCIe slot on
the motherboard in the next step.
11.
Turn the assembly so that the riser card connector edge is facing the PCIe
slot on the motherboard, and the face plate is toward the front of the chassis.
12.
Holding this assembly above the motherboard at about a 45 degree angle,
slowly lower it so that the connector on the face plate clears the blanking
panel opening of the chassis from the inside. Slowly align the connector
edge of the riser card with the motherboard’s PCIe slot. The short section of
the connector must align with the short section of the slot.
IB0056101-00 H
4-11
S
4–Hardware Installation
Hardware Installation
13.
Insert the riser assembly into the motherboard’s PCIe slot, ensuring good
contact. The QLogic adapter should now be parallel to the motherboard and
about one inch above it (see Figure 4-6).
Figure 4-6. Assembled PCIe Host Channel Adapter with Riser
14.
Secure the face plate to the chassis. The QLogic adapter has a screw hole
on the side of the face plate that can be attached to the chassis with a
retention screw. The securing method may vary depending on the chassis
manufacturer. Refer to the system documentation for information about
mounting details such as mounting holes, screws to secure the card, or
other brackets.
The QLogic PCIe host channel adapter with PCIe riser card is now installed. Next,
install the cables as described in “Cabling the Adapter to the InfiniBand Switch” on
page 4-17. Then test your installation by powering up and verifying link status (see
“Completing the Installation” on page 4-18).
Hardware Installation for QHT7140 with HTX Riser
Most installations will be in a 1U and 2U chassis, using the HTX riser card. This
results in a horizontal installation of the QHT7140. This type of installation is
described in this section. Installation in a 3U chassis is described in “Hardware
Installation for the QHT7140 Without an HTX Riser” on page 4-16.
Installation of QLogic QHT7140 in a 1U or 2U chassis requires an HTX riser card.
NOTE:
The illustrations in this section are shown for the full height short form factor.
Installation of the HTX low profile form factor follows the same steps.
4-12
IB0056101-00 H
A
4–Hardware Installation
Hardware Installation
To install the QLogic adapter with an HTX riser card:
1.
The BIOS should be already be configured properly by the motherboard
manufacturer. However, if any additional BIOS configuration is required, it
will usually need to be done before installing the QLogic adapter. See
“Configuring the BIOS” on page 4-4.
2.
Shut down the power supply to the system into which you will install the
QLogic adapter.
3.
Take precautions to avoid electrostatic discharge (ESD) damage to the
cards by properly grounding yourself or touching the metal chassis to
discharge static electricity before handling the cards.
4.
Remove the cover screws and cover plate to expose the system’s
motherboard. For specific instructions on how to do this, follow the hardware
documentation that came with your system.
5.
Locate the HTX slot on your motherboard. Note that the HTX slot has two
separate connectors, corresponding to the connector edges of the adapter.
See Figure 4-7.
HTX Slot in a Typical Opteron Motherboard
Figure 4-7. HTX Slot
6.
IB0056101-00 H
Determine if a blanking panel is installed in your chassis. If it is, remove it so
that the InfiniBand connector will be accessible. Refer to your system vendor
instructions for how to remove the blanking panel.
4-13
S
4–Hardware Installation
Hardware Installation
7.
Remove the QLogic QHT7140 from the anti-static bag.
NOTE:
Be careful not to touch any of the components on the printed circuit
board during these steps. You can hold the adapter by its face plate or
edges.
8.
Locate the face plate on the connector edge of the card.
9.
Connect the QLogic adapter and HTX riser card together, forming the
assembly that you will insert into your motherboard. First, visually line up the
adapter slot connector edge with the edge connector of the HTX riser card
(see Figure 4-8).
HTX Riser Card
Face Plate
QLogic Adapter
LEDs
InfiniBand Connector
Figure 4-8. QLogic QHT7140 Adapter with Riser Card
4-14
10.
Holding the QLogic adapter by its edges, carefully insert the card slot
connector into the HTX riser card edge connector, as show in Figure 4-8.
The result is a combined L-shaped assembly of the HTX riser card and
QLogic adapter. This assembly is what you will insert into the HTX slot on
the motherboard in the next step.
11.
Turn the assembly so that the riser card connector edge is facing the HTX
slot on the motherboard, and the face plate is toward the front of the chassis.
12.
Holding this assembly above the motherboard at about a 45 degree angle,
slowly lower it so that the connector on the face plate clears the blanking
panel opening of the chassis from the inside. Slowly align the connector
edge of the HTX riser card with the motherboard’s HTX slot. The HTX riser
and HTX slot must line up perfectly.
IB0056101-00 H
A
4–Hardware Installation
Hardware Installation
13.
Insert the HT riser assembly into the motherboard’s HTX slot, ensuring good
contact. The QLogic adapter should now be parallel to the motherboard and
about one inch above it, as shown in Figure 4-9.
Figure 4-9. Assembled QHT7140 with Riser
14.
Secure the face plate to the chassis. The QLogic adapter has a screw hole
on the side of the face plate that can be attached to the chassis with a
retention screw. The securing method may vary depending on the chassis
manufacturer. Refer to the system documentation for information about
mounting details such as mounting holes, screws to secure the card, or
other brackets.
The QLogic QHT7140 with HTX riser card is now installed. Next, install the cables
as described in “Cabling the Adapter to the InfiniBand Switch” on page 4-17. Then
test your installation by powering up and verifying link status (see “Completing the
Installation” on page 4-18).
Hardware Installation for QLE7240, QLE7280, and QLE7140
Without a PCI Express Riser
Installing the QLogic QLE7240, QLE7280, or QLE7140 without a PCI Express
riser card requires a 3U or larger chassis.
Installation is similar to the QHT7140 HTX adapter, except that the card slot
connectors on these adapters fit into the PCIe slot rather than the HTX slot.
Follow the instructions in “Hardware Installation for the QHT7140 Without an HTX
Riser” on page 4-16, substituting the PCIe slot for the HTX slot.
IB0056101-00 H
4-15
4–Hardware Installation
Hardware Installation
S
Hardware Installation for the QHT7140 Without an HTX Riser
Installing the QLogic QHT7140 without an HTX riser card requires a 3U or larger
chassis. The card slot connectors on the QHT7140 fit into the HTX slot in a
vertical installation.
To install the QLogic adapter without the HTX riser card:
4-16
1.
The BIOS should already be configured properly by the motherboard
manufacturer. However, if any additional BIOS configuration is required, it
usually needs to be done before installing the QLogic adapter. See
“Configuring the BIOS” on page 4-4.
2.
Shut down the power supply to the system into which you will install the
QLogic adapter.
3.
Take precautions to avoid electrostatic discharge (ESD) damage to the
cards by properly grounding yourself or touching the metal chassis to
discharge static electricity before handling the cards.
4.
If you are installing the QLogic adapter into a covered system, remove the
cover screws and cover plate to expose the system’s motherboard. For
specific instructions on how to do this, follow the hardware documentation
that came with your system.
5.
Locate the HTX slot on your motherboard (see Figure 4-7).
6.
Remove the QLogic adapter from the anti-static bag. Hold the card by the
top horizontal section of the bracket, and the top rear corner of the card. Be
careful not to touch any of the components on the printed circuit card.
7.
Without fully inserting, gently align and rest the HTX card’s gold fingers on
top of the motherboard’s HTX slot.
IB0056101-00 H
A
4–Hardware Installation
Switch Configuration and Monitoring
8.
Insert the card by pressing firmly and evenly on the top of the horizontal
bracket and the top rear corner of the card simultaneously. The card should
insert evenly into the slot. Be careful not to push, grab, or put pressure on
any other part of the card, and avoid touching any of the components. See
Figure 4-10.
Figure 4-10. QHT7140 Without Riser Installed in a 3U Chassis
9.
Secure the face plate to the chassis. The QLogic adapter has a screw hole
on the side of the face plate that can be attached to the chassis with a
retention screw. The securing method may vary depending on the chassis
manufacturer. Refer to the system documentation for information about
mounting details such as mounting holes, and screws to secure the card, or
other brackets.
Next, install the cables, as described in “Cabling the Adapter to the InfiniBand
Switch” on page 4-17. Then test your installation by powering up the system (see
“Completing the Installation” on page 4-18).
Switch Configuration and Monitoring
The QLogic interconnect is designed to work with all InfiniBand-compliant
switches. Follow the vendor documentation for installing and configuring your
switches.
Cabling the Adapter to the InfiniBand Switch
Follow the recommendations of your cable vendor for cable management and
proper bend radius.
IB0056101-00 H
4-17
S
4–Hardware Installation
Completing the Installation
The QLE7240, QLE7280, QLE7140, QHT7040, and QHT7140 adapters are all
cabled the same way.
To install the InfiniBand cables:
1.
Check that you have removed the protector plugs from the cable connector
ends.
2.
Different vendor cables might have different latch mechanisms. Determine if
your cable has a spring-loaded latch mechanism.
„
If your cable is spring-loaded, grasp the metal shell and pull on the
plastic latch to release the cable. To insert, push and the cable snaps
into place. You will hear a short “click” sound from the cable connector
when it snaps in.
„
If your cable latch mechanism is not spring-loaded, push on the metal
case, then push the plastic latch to lock the cable in place.
3.
The InfiniBand cables are symmetric; either end can be plugged into the
switch. Connect the InfiniBand cable to the connector on the QLogic
QLE7240, QLE7280, QLE7140 or QHT7140. Depress the side latches of the
cable when connecting. (On some cables, this latch is located at the top of
the cable connector.) Make sure the lanyard handle on the cable connector
is slid forward toward the card connector until fully engaged.
4.
Connect the other end of the cable to the InfiniBand switch.
Completing the Installation
To complete the hardware installation:
4-18
1.
Complete any other installation steps for other components.
2.
Replace the cover plate and back panel.
3.
Verify that the power cable is properly connected.
4.
Turn on the power supply and boot the system normally.
5.
Watch the LED indicators. The LEDs will flash only once, briefly, at
power-up. The LEDs are functional only after the InfiniPath software has
been installed, the driver has been loaded, and the system is connected to
an InfiniBand switch. To use the LEDs to check the state of the adapter, see
“LED Link and Data Indicators” on page 7-1.
IB0056101-00 H
5
Software Installation
This section provides instructions for installing QLogic OFED 1.4, which includes
QLogic InfiniPath and the OpenFabrics software. The software includes drivers,
protocol libraries, QLogic’s implementation of the MPI message passing standard,
associated utilities, and example programs, including benchmarks. A complete list
of the provided software is in “Software Components” on page 2-4.
Cluster Setup
Information on clusters, supported distributions and kernels, and environment
setup is provided in “Types of Nodes in a Cluster Environment” on page 5-1,
“Supported Linux Distributions” on page 5-2, and “Distribution Identifiers” on
page 5-3.
Types of Nodes in a Cluster Environment
In a cluster environment, different nodes can be used for different functions, such
as launching jobs, developing software, or running jobs. The nodes are defined as
follows:
„
Front end node. This node launches jobs.
„
Compute node. This node runs jobs.
„
Development or build node. These are the machines on which examples
or benchmarks can be compiled.
Any machine can serve any combination of these three purposes, but a typical
cluster has many compute nodes and just a few (or only one) front end nodes.
The number of nodes used for development will vary. These node names are
used throughout this guide.
IB0056101-00 H
5-1
S
5–Software Installation
Cluster Setup
Supported Linux Distributions
The QLogic interconnect runs on AMD™ Opteron™ and 64-bit Intel Xeon systems
running Linux®. The currently supported distributions and associated Linux kernel
versions for InfiniPath and OpenFabrics are listed in Table 5-1.
The kernels are the ones that shipped with the distributions. All are for the x86_64
architecture.
Table 5-1. InfiniPath/OpenFabrics Supported Distributions and
Kernels
Distribution
InfiniPath/OpenFabrics Supported
Kernels
Red Hat® Enterprise Linux® (RHEL) 4.5
2.6.9-55 (U5)
RHEL 4.6
2.6.9-67 (U6)
RHEL 4.7
2.6.9-78 (U7)
CentOS 4.5
2.6.9.55
CentOS 4.6
2.6.9-67
CentOS 4.7
2.6.9-78
Scientific Linux 4.5
2.6.9.55
Scientific Linux 4.6
2.6.9-67
Scientific Linux 4.7
2.6.9-78
Red Hat Enterprise Linux 5.1 (RHEL 5.1)
2.6.18-53, 2.6.18-92
RHEL 5.2
2.6.18-92
CentOS 5.1
2.6.18-53, 2.6.18-92
CentOS 5.2
2.6.18-92
Scientific Linux 5.1
22.6.18-53, 2.6.18-92
Scientific Linux 5.2
2.6.18-92
SUSE® Linux Enterprise Server 10 SP 1
2.6.16.46
SUSE Linux Enterprise Server 10 SP 2
2.6.16.60
®
NOTE:
Support for RHEL4 U4 and SLES 10.0 has been removed.
5-2
IB0056101-00 H
A
5–Software Installation
Compiler Support
Distribution Identifiers
Distribution identifiers for this release are listed in Table 5-2. They are used in file
naming conventions.
Table 5-2. Distribution Identifiers
Distribution
Identifier
Used On
rhel4
Red Hat® Enterprise Linux® 4.5 (RHEL4.5), RHEL4.6, RHEL 4.7,
CentOS 4.5-4.7, Scientific Linux 4.5-4.7 for x86_64 systems
rhel5
Red Hat Enterprise Linux 5.1 (RHEL5.1), RHEL5.2, CentOS 5.1-5.2,
Scientific Linux 5.1-5.2, for x86_64 systems
sles10
SLES 10 SP1-SP2 for x86_64 systems
Compiler Support
QLogic MPI supports the following compilers:
„
„
„
„
„
GNU gcc 3.3.x, 3.4.x, 4.0, 4.1, 4.2.x, and 4.3.x compiler suites
PathScale Compiler Suite 3.0, 3.1 and 3.2
PGI 5.2, 6.0. 7.1, 7.2-4, and 8.0-3
Intel 9.x, 10.1, and 11.0
gfortran 4.1.x
PathScale Compiler Suite Version 3.x is now supported on systems that have the
GNU 4.0 and 4.1 compilers and compiler environment (header files and libraries).
Set Up Your Environment
Keep the following in mind when setting up the environment:
„
The runtime and build environments must be the same. Compatibility
between executables built on different Linux distributions cannot be
guaranteed.
„
You will need Administrator privileges on your machines.
„
If you are using the rpm install method, make sure that all previously existing
(stock) OpenFabrics RPMs are uninstalled. See “Uninstall InfiniPath and
OpenFabrics RPMs” on page 5-26 for more information. The Installer tool
will automatically uninstall previous RPMs before upgrades.
„
It is possible to have a cluster running with different kernel versions.
However, QLogic recommends and supports clusters where all nodes run
equivalent software.
IB0056101-00 H
5-3
S
5–Software Installation
Set Up Your Environment
Some operating system packages are required for OpenFabrics; they are listed in
Table 5-3.
Table 5-3. Required Operating System Packages
OS Distribution
Required Packages
All
gcc, glib, glibc
All (for development)
glib-devel, glibc-devel, glibc-devel-32bit
(to build 32-bit libraries on x86_86 and ppc64),
zlib-devel
Red Hat and Red
Hat-derived kernels
kernel-devel, rpm-build
SLES 10
kernel-source, rpm
There are also Operating System (OS) package requirements for some specific
components in QLogic OFED 1.4, as listed in Table 5-4.
Table 5-4. Specific Component Requirements
QLogic OFED
Component
QLogic infinipath* software (Listed as TrueScale
HCA Libs in the Installer)
Required OS Packages
openssh and openssh-server. Note that in the
SLES 10 distribution, openssh-server is a part of the
openssh package. These packages must be on every
node.
python. This package is required if the Multi-Purpose
Daemon (MPD) job launcher or the ipath_mtrr script
will be used.
5-4
MVAPICH
a Fortran compiler
MVAPICH2
libstdc++-devel, sysfsutils (SLES), libsysfs-devel (RedHat 5.0)
Open MPI
libstdc++-devel
ibutils
tcl-8.4, tcl-devel-8.4, tk, libstdc++-devel
QLogic openmpi_gcc*
libgfortran (on RHEL4)
IB0056101-00 H
A
5–Software Installation
Choose the Appropriate Download Files
Choose the Appropriate Download Files
This section assumes that the correct Linux kernel, a supported distribution, and
the required prerequisites (see Table 5-3 and Table 5-4) have been installed on
every node.
The components of the QLogic OFED 1.4 release can be found in all of the
following packages. Select the package that works best for you from the following
list:
„
„
„
„
„
„
QLogicIB-Basic with the Text User Interface (TUI) Installer
QLogic OFED 1.4 RPM Set
QLogic OFED 1.4 User-level RPM Set
Rocks Rolls
Platform Open Cluster Stack (OCS) Kits
QLogic InfiniBand Fabric Suite (available for purchase)
Check Table 5-5 for the package contents available for each type of download.
All files are available from the QLogic web site, http://www.qlogic.com. Follow the
Downloads tab to choose the appropriate download for your OS distribution, then
follow the instructions for installing the QLogic OFED software in the following
sections.
Table 5-5. Available Packages for QLogic OFED 1.4
Release
Package
QLogicIB-Basic
Description
Includes:
„ QLogic OFED 1.4
„ InfiniPath host channel adapter
driver
Installation and
Documentation
Follow the instructions in “Install
QLogicIB-Basic with the
Installer Tool” on page 5-8.
Related documentation:
„ Optimized stack for MPI (PSM)
„ Readme and Release Notes
„ QLogic MPI
„ QLogic Host Channel
Adapter and QLogic OFED
Software Install Guide
„ Other MPIs (MVAPICH and
Open MPI compiled with GCC,
PathScale, PGI, and Intel compilers)
„ User tools
„ QLogic SRP and VNIC
„ QLogic Host Channel
Adapter and QLogic OFED
Software Users Guide.
„ QLogic ULP Configuration
Guide
„ TUI Installer
„ QLogic IB Tools
IB0056101-00 H
5-5
S
5–Software Installation
Choose the Appropriate Download Files
Table 5-5. Available Packages for QLogic OFED 1.4
Release (Continued)
Package
QLogic
OFED 1.4 RPM
Set
Description
Includes:
„ QLogic OFED 1.4
„ InfiniPath host channel adapter
driver
Follow the instructions in “Using
rpm to Install InfiniPath and
OpenFabrics” on page 5-15
Related documentation:
„ Optimized stack for MPI (PSM)
„ Readme and Release Notes
„ QLogic MPI
„ QLogic Host Channel
Adapter and QLogic OFED
Software Install Guide
„ Other MPIs (MVAPICH and
Open MPI compiled with GCC,
PathScale, PGI, and Intel compilers)
„ User tools
QLogic
OFED 1.4
User-level Software RPM Set
Installation and
Documentation
Includes:
„ Optimized stack for MPI (PSM)
„ QLogic MPI
„ Other MPIs (MVAPICH and
Open MPI compiled with GCC,
PathScale, PGI, and Intel compilers)
„ QLogic Host Channel
Adapter and QLogic OFED
Software Users Guide.
Follow the instructions in “Install
QLogic OFED User-level Software with the rpm Command”
on page 5-18
Related documentation:
„ Readme and Release Notes
„ QLogic Host Channel
Adapter and QLogic OFED
Software Install Guide
„ QLogic Host Channel
Adapter and QLogic OFED
Software Users Guide.
For installation over OFED 1.4
supplied from OpenFabrics or
with Linux distribution
5-6
IB0056101-00 H
A
5–Software Installation
Choose the Appropriate Download Files
Table 5-5. Available Packages for QLogic OFED 1.4
Release (Continued)
Package
QLogic
OFED 1.4
Rocks Rolls
Description
Includes:
„ QLogic OFED 1.4
„ InfiniPath host channel adapter
driver
Installation and
Documentation
Follow the instructions in “Install
QLogic OFED Using Rocks” on
page 5-21
Related documentation:
„ Optimized stack for MPI (PSM)
„ Readme and Release Notes
„ QLogic MPI
„ QLogic Host Channel
Adapter and QLogic OFED
Software Install Guide
„ Other MPIs (MVAPICH and
Open MPI compiled with GCC,
PathScale, PGI, and Intel compilers)
„ User tools
„ QLogic Host Channel
Adapter and QLogic OFED
Software Users Guide
„ QLogic SRP and VNIC
„ FastFabric Enablement Tools
QLogic
OFED 1.4 Platform OCS Kits
Includes:
„ QLogic OFED 1.4
„ InfiniPath host channel adapter
driver
Follow the instructions in “Install
QLogic OFED Using a Platform
OCS Kit” on page 5-23
Related documentation:
„ Optimized stack for MPI (PSM)
„ Readme and Release Notes
„ QLogic MPI
„ QLogic Host Channel
Adapter and QLogic OFED
Software Install Guide
„ Other MPIs (MVAPICH and
Open MPI compiled with GCC,
PathScale, PGI, and Intel compilers)
„ User tools
„ QLogic Host Channel
Adapter and QLogic OFED
Software Users Guide.
„ QLogic SRP and VNIC
„ FastFabric Enablement Tools
QLogic InfiniBand Fabric
Suite
Includes:
„ QLogic FastFabric Toolset
„ QLogic Fabric Manager
„ QLogic Fabric Viewer
„ InfiniServ Host Software
„ QLogicIB-Basic
IB0056101-00 H
Follow the instructions in “Install
the QLogic InfiniBand Fabric
Suite Software” on page 5-24
This package can be purchased
separately. Follow the links on
the QLogic download page.
Documentation is included.
5-7
S
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
Install QLogicIB-Basic with the Installer Tool
The QLogicIB-Basic package has a Text User Interface (TUI) for easy installation
of the software. Use this method if you downloaded the QLogicIB-Basic package.
This method is suitable for use on small clusters.
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
Download the QLogicIB-Basic tar file for your distribution to a directory that
will not be deleted upon reboot. Then unpack the tar file by typing:
$ tar zxvf QLogicIB-Basic.<version>.tgz
The tar command creates a directory based on the tar file name and
places the RPMs and other files in this directory.
3.
After unpacking the .tgz file, change the directory to:
cd QLogicIB-Basic.<version>
4.
Log in as a root user, then type:
# ./INSTALL
If you need 32-bit support on 64 bit operating systems (OSs), invoke the
installer with ./INSTALL --32bit
A menu similar to the following displays:
QLogic Inc. InfiniBand <version> Software
1) Install/Uninstall Software
2) Reconfigure OFED IP over IB
3) Reconfigure Driver Autostart
4) Update HCA Firmware
5) Generate Supporting Information for Problem Report
6) Fast Fabric (Host/Chassis/Switch Setup/Admin)
X) Exit
5-8
IB0056101-00 H
A
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
5.
Type 1, which displays the menu for software installation. This menu
displays the packages to select for installation:
QLogic Inc. IB Install (version release) Menu
Please Select Install Action (screen 1 of 3):
0) OFED IB Stack
[
Install
][Available] 1.4.0.1.5
1) TrueScale HCA Libs
[
Install
][Available] 2.3.0.0.4237
2) QLogic IB Tools
[
Install
][Available] 4.4.0.0.29
3) OFED IB Development [
Install
][Available] 1.4.0.1.5
4) QLogic Fast Fabric
[Don’t Install][Not Avail]
5) QLogic SRP
[
Install
][Available] 1.4.0.0.12
6) QLogic Virtual NIC
[
Install
][Available] 1.4.0.0.11
7) OFED IP over IB
[
Install
][Available] 1.4.0.1.5
8) OFED SDP
[
Install
][Available] 1.4.0.1.5
9) OFED uDAPL
[
Install
][Available] 1.4.0.1.5
a) QLogic FM
[Don’t Install][Not Avail]
b) MVAPICH (gcc)
[
Install
][Available] 1.4.0.1.5
c) MVAPICH2 (gcc)
[
Install
][Available] 1.4.0.1.5
d) OpenMPI (gcc)
[
Install
][Available] 1.4.0.1.5
N) Next Screen
P) Perform the selected actions
I) Install All
R) Re-Install All
U) Uninstall All
X) Return to Previous Menu (or ESC)
Pressing the keys corresponding to menu items (0–9, a–d in the previous
example) toggles the selection for the given item.
The packages in this step are recommended for a new installation. QLogic
Fast Fabric (4) and QLogic FM (Fabric Manager) (a) are available only with
the QLogic InfiniBand Fabric Suite (purchased separately). MVAPICH2 (c)
does not run over QLogic PSM; it runs only over OpenFabrics Verbs.
TrueScale HCA Libs (1) contains the enhanced InfiniPath host channel
adapter driver; optimized stack for MPI(PSM) and QLogic MPI; and user
tools.
6.
IB0056101-00 H
Type n to proceed to the next menu. You can view the installation menus
(three total) by continuing to type n. (Typing x or pressing ESC returns you
to the top level menu; any changes you made will not be saved.)
5-9
S
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
The next menu contains the following choices:
QLogic Inc. IB Install (4.4.1.0.8 release) Menu
Please Select Install Action (screen 2 of 3):
0) MVAPICH/PSM (gcc)
[
Install
][Available] 1.4.0.1.5
1) MVAPICH/PSM (PGI)
[
Install
][Available] 1.4.0.1.5
2) MVAPICH/PSM (PSc)
[
Install
][Available] 1.4.0.1.5
3) MVAPICH/PSM (Intel) [
Install
][Available] 1.4.0.1.5
4) OpenMPI/PSM (gcc)
[
Install
][Available] 1.4.0.1.5
5) OpenMPI/PSM (PGI)
[
Install
][Available] 1.4.0.1.5
6) OpenMPI/PSM (PSc)
[
Install
][Available] 1.4.0.1.5
7) OpenMPI/PSM (Intel) [
Install
][Available] 1.4.0.1.5
8) MPI Source
[
Install
][Available] 1.4.0.1.5
9) OFED RDS
[
Install
][Available] 1.4.0.1.5
a) OFED SRP
[
Install
][Available] 1.4.0.1.5
b) OFED SRP Target
[Don’t Install][Available] 1.4.0.1.5
c) OFED iSER
[Don’t Install][Available] 1.4.0.1.5
d) OFED iSER Target
[Don’t Install][Available]
N) Next Screen
P) Perform the selected actions
I) Install All
R) Re-Install All
U) Uninstall All
X) Return to Previous Menu (or ESC)
PSc is an acronym for the PathScale compiler. QLogic recommends
choosing all items except for OFED SRP Target (b) and OFED iSER (c).
7.
Then type n. The following menu displays:
QLogic Inc. IB Install (4.4.1.0.8 release) Menu
Please Select Install Action (screen 3 of 3):
0) OFED iWARP
[Don’t Install][Available] 1.4.0.1.5
1) OFED Open SM
[Don’t Install][Available] 1.4.0.1.5
2) OFED Debug Info
[Don’t Install][Available] 1.4.0.1.5
N) Next Screen
P) Perform the selected actions
I) Install All
R) Re-Install All
U) Uninstall All
X) Return to Previous Menu (or ESC)
5-10
IB0056101-00 H
A
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
Open SM (1) should only be installed on one node in the cluster where it will
be used. If desired, Type 1 for Open SM.
8.
Type p to start the installation.
The installer will uninstall older OFED RPMs, then asks for input for a series
of operations. You can accept the defaults by pressing ENTER. Note the
following cases:
Install MPI with prefix compatible with mpi-selector
(/usr/mpi/qlogic) [y]: y
This default allows you to use the mpi-selector to choose between
different MPI implementations.
If you type y, make sure, after installation, that the environment variable
$MPICH_ROOT is set to the same prefix that is used here
(/usr/mpi/qlogic). When set, the $MPICH_ROOT variable allows QLogic
MPI to correctly locate header and library files for MPI compilation and
running parallel jobs. Typing n causes QLogic MPI to be installed in the
default directory /usr.
The next case is:
Configure OFED IP over IB IPV4 addresses now? [n]:
Type y if the IB IPV4 addresses and netmasks are available, and you want
to enter them now. Type n if the IB addresses are not available or you want
to add them later. IPoIB can be configured manually by following the
instructions in “Configure the IPoIB Network Interface” on page 6-2.
Finally, QLogic recommends answering n to the following:
Enable QLogic SRP (qlgc_srp) to autostart? [y]: n
Enable OFED SRP (openibd) to autostart? [y]: n
Additional instructions for using SRP are described in “SRP” on page 6-4.
9.
Once the install has completed, quit the installer by typing x until you have
exited.
10.
Reboot the machine.
NOTE:
If you want support for 32-bit programs, you can install the 32-bit libraries on
a 64-bit system by typing:
# ./INSTALL --32bit
IB0056101-00 H
5-11
S
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
The Installer can also be used as a Command Line Interface (CLI). There are
numerous options for installation/upgrade/uninstallation/autostart of all the
available components. Here are the available options:
./INSTALL [-r root] [-v|-vv] [-a|-n|-U|-F|-u|-s|-i comp|-e comp|-E
comp|-D comp] [-f] [--user_configure_options ’options’]
./INSTALL -C lists all the available components, which include:
ib_stack
opensm ofed_debug
mvapich_pgi_qlc
truescale
mvapich_pathscale_qlc
oftools
mvapich_intel_qlc
ib_stack_dev
openmpi_gcc_qlc
fastfabric
openmpi_pgi_qlc
qlgc_srp
openmpi_pathscale_qlc
qlgc_vnic
openmpi_intel_qlc
ofed_ipoib
ofed_mpisrc
ofed_sdp
ofed_rds
ofed_udapl
ofed_srp
qlgc_fm
ofed_srpt
mvapich
ofed_iser
mvapich2
ofed_isert
openmpi
ofed_iwarp
mvapich_gcc_qlc
The following additional component names are allowed for -E and -D options:
iba_mon
qlgc_fm_snmp
NOTE:
The component names are not the same as the RPM names in the RPM
downloads, even though they are RPM-based in most cases. See “Package
Descriptions” on page D-1 for more information.
5-12
IB0056101-00 H
A
5–Software Installation
Install QLogicIB-Basic with the Installer Tool
Table 5-6 summarizes Installer command line options.
Table 5-6. INSTALL Options
Command
IB0056101-00 H
Meaning
-a
Install all ULPs and drivers with default options.
-n
Install all ULPs and drivers with default options,
but with no change to autostart options.
-U
Upgrade/re-install all presently installed ULPs
and drivers with default options, and no change
to autostart options.
-i comp
Install the given component with default options.
This option can appear more than once on a
command line.
-f
Skip firmware upgrade during install.
--user_configure_options
’options’
Specify additional OFED build options for user
space srpms. Causes a rebuild of all user
srpms.
--kernel_configure_options
’options’
Specify additional OFED build options for driver
srpms. Causes a rebuild of all driver srpms.
--prefix dir
Specify an alternate directory prefix for installation. The default is /usr. Causes a rebuild of
needed srpms.
--no32bit
Disable install of 32-bit libraries on 64-bit OSs.
--32bit
Enable install of 32-bit libraries on 64 bit OSs (the
default is no32bit).
--rebuild
Force OFED rebuild.
--force
Force install even if distros do not match. Using
this option can result in undefined behaviors.
-F
Upgrade host channel adapter firmware with
default options.
-u
Uninstall all ULPs and drivers with default
options.
-s
Enable autostart for all installed drivers.
-r
Specify an alternate root directory. The default
is /.
5-13
S
5–Software Installation
About rpm Installation
Table 5-6. INSTALL Options (Continued)
Command
Meaning
-e comp
Uninstall the given component with default
options. This option can appear more than once
on a command line.
-E comp
Enable autostart of a given component. This
option can appear with -D or more than once on
a command line.
-D comp
Disable autostart of a given component. This
option can appear with -E or more than once on
a command line.
-v
Verbose logging
-vv
Very verbose debug logging.
-C
Output list of supported components.
--user_queries
Permit non-root users to query the fabric
(default).
--no_user_queries
Non-root users cannot query the fabric. Default
options retain existing configuration files.
About rpm Installation
Linux distributions of QLogic OFED (InfiniPath and OpenFabrics) software can be
installed from binary RPMs. RPM is a Linux packaging and installation tool used
by Red Hat, SUSE, and CentOS.
The following instructions are for a single node. Parallel command starters can be
used for installation on multiple nodes. The Yellowdog Updater, Modified (YUM)
can also be used for installation. However, these subjects are beyond the scope of
this document.
RPMs contain config files. The current config files will not be overwritten when
new RPMs are installed. New config files will contain the suffix .rpmnew and
can be found in /etc/sysconfig and /etc/infiniband. Check the new files
to see if there is anything you want to add to your standard config files.
5-14
IB0056101-00 H
A
5–Software Installation
About rpm Installation
NOTE:
„ For convenience, QLogic recommends installing the same set of RPMs
on all nodes (with the exception of OpenSM). Omitting the *-Static/*
and *-Debuginfo/* RPMs is recommended. Use the */32bit/*
RPMs only if you need them. Some RPMs are optional, depending on
which type of node is being used. To see which RPMs are required or
optional for each type of node, according to its function as a compute
node, front end node, development machine, or Subnet Manager (SM),
see Appendix D “Package Descriptions”.
„ Install the OpenSM RPM only if you do not plan to use a switch-based or
host-based SM. The OpenSM RPM is normally installed on the node on
which it will be used. If installed, it is off by default. This behavior can be
modified. See “OpenSM” on page 6-3 for more information.
„ Programs that incorporate the user IB Verbs interfaces, such as
diagnostics, benchmarks, Verbs-based MPIs (for example, Intel MPI),
and SDP sockets, must have the OpenFabrics RPMs installed.
„ Install the infinipath RPM on all nodes where you install the
mpi-frontend RPM.
„ The mpi-devel and infinipath-devel RPMs are installed when
the qlogic-mpi-register RPM is installed, as there are
dependencies.
„ Check that all older stock OFED RPMs have been uninstalled (“Uninstall
InfiniPath and OpenFabrics RPMs” on page 5-26).
Using rpm to Install InfiniPath and OpenFabrics
To install InfiniPath and OpenFabrics using rpm:
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
After downloading the appropriate tar file, type:
$ tar zxvf QLogicOFED<version>-<distribution>-x86_64.tgz
The tar command creates a directory based on the tar file name and
places the RPMs and other files in this directory.
3.
The RPMs must be available on each node on which they will be used. Copy
the RPMs to a directory on each node that will need them.
Log in as a root user, then type:
# cd QLogicOFED<version>-<distribution>-x86_64
Alternately, put the RPMs in a directory that is accessible (for example, via
Network File System (NFS)) to every node.
IB0056101-00 H
5-15
S
5–Software Installation
About rpm Installation
NOTE:
If you want to use the mpi-selector to switch between QLogic MPI
and other MPI implementations, install QLogic MPI in an alternate
location, consistent with that of the other MPIs. Skip to Step 5.
4.
To install InfiniPath, QLogic MPI, and OpenFabrics, type the following (as a
root user):
# rpm -Uvh InfiniPath/*.rpm InfiniPath-MPI/*.rpm \
InfiniPath-MPI/32bit/mpi-frontend-*.rpm \
InfiniPath-Devel/*.rpm Documentation/*.rpm OtherMPIs/*.rpm \
OpenFabrics/*.rpm OpenFabrics-Devel/*.rpm \
OtherHCAs/*.rpm OtherHCAs-Devel/*.rpm
Note that you need to install the
InfiniPath-MPI/32bit/mpi-frontend-*.rpm even if you do not plan
to use any other 32-bit RPMs. However, if you need 32-bit support, you can
add the other 32bit subdirectories to the rpm command.
Install the OpenSM RPM only if you do not plan to use a switch-based or
host-based SM. The OpenSM RPM is normally installed on the node where it
will be used. If installed, it is off by default. This behavior can be modified.
See “OpenSM” on page 6-3 for more information.
To add Open SM, type this command:
# rpm -Uvh OpenSM/*.rpm OpenSM-Devel/*.rpm
If you need 32-bit support, add the desired 32bit subdirectories to the rpm
commands.
Proceed to Step 6.
5.
To install QLogic MPI in an alternate location, type these commands instead
of those in Step 4:
# mkdir QLogic-MPI-prefixed
# mv InfiniPath-MPI/mpi-* \
InfiniPath-MPI/32bit/mpi-frontend-*.rpm \
InfiniPath-Devel/mpi-devel* \
OtherMPIs/qlogic-mpi-register* \
Documentation/mpi-doc* QLogic-MPI-prefixed/
Note that you need to install the
InfiniPath-MPI/32bit/mpi-frontend-*.rpm even if you do not plan
to use any other 32-bit RPMs. However, if you need 32-bit support, you can
add the other 32bit subdirectories to the rpm command.
5-16
IB0056101-00 H
A
5–Software Installation
About rpm Installation
Next, install all non-prefixed RPMs:
# rpm -Uvh InfiniPath/*.rpm \
InfiniPath-Devel/infinipath-devel*.rpm \
OpenFabrics/*.rpm OpenFabrics-Devel/*.rpm \
OtherHCAs/*.rpm OtherHCAs-Devel/*.rpm \
Documentation/infinipath-doc*.rpm \
Documentation/ofed-doc*.rpm \
OtherMPIs/mpi-selector*.rpm OtherMPIs/mpitests*.rpm \
OtherMPIs/mvapich*.rpm OtherMPIs/openmpi*.rpm
Finally, install the prefixed QLogic-MPI RPMs in /usr/mpi/qlogic:
# rpm -Uvh --prefix /usr/mpi/qlogic QLogic-MPI-prefixed/*.rpm
The desired prefix should be made available in the $MPICH_ROOT
environment variable, either by global shell configuration files or through
third-party environment management utilities such as mpi-selector or the
Environment Modules. This allows QLogic MPI to correctly locate header
and library files for MPI compilation and running parallel jobs. See the
QLogic Host Channel Adapter and QLogic OFED Software Users Guide for
details.
6.
Reboot.
RPM Organization
The complete RPM directories are organized as follows. Note that the suggested
installation does not include all possible RPM directories. Install the files in the
*-Devel directories if you are going use source code to do development work.
The *-Debuginfo directories contain debug information and possibly source
code, which may be useful for testing, debugging, and developing applications.
The *-Static directories contain the static versions of the libraries, which can
be used in place of the dynamic libraries when compiling and linking.
InfiniPath_license.txt,LEGAL.txt (top level)
Documentation/
InfiniPath/
InfiniPath/32bit
InfiniPath-Devel/
InfiniPath-MPI/
InfiniPath-MPI/32bit
OpenFabrics/
OpenFabrics/32bit/
OpenFabrics-Static/
OpenFabrics-Static/32bit/
IB0056101-00 H
5-17
S
5–Software Installation
Install QLogic OFED User-level Software with the rpm Command
OpenFabrics-Devel/
OpenFabrics-Devel/32bit/
OpenFabrics-Devel-Static/
OpenFabrics-Debuginfo/
OpenFabrics-Debuginfo/32bit/
OpenSM/
OpenSM/32bit/
OpenSM-Debuginfo/
OpenSM-Debuginfo/32bit/
OpenSM-Devel/
OpenSM-Devel/32bit/
OpenSM-Static/
OpenSM-Static/32bit/
OtherHCAs/
OtherHCAs-Debuginfo
OtherHCAs-Debuginfo/32bit/
OtherHCAs-Devel/
OtherHCAs-Devel/32bit/
OtherHCAs-Devel-Static/
OtherHCAs-Devel-Static/32bit/
OtherMPIs/
Install QLogic OFED User-level Software with the
rpm Command
The QLogic user-level software is for installation over OFED 1.4 supplied from
OpenFabrics or with Linux distribution.
For convenience, QLogic recommends that all RPMs are installed on all nodes.
The infinipath RPM must be installed on all nodes where you install the
mpi-frontend RPM.
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
After downloading the appropriate tar file, type:
$ tar zxvf
InfiniPath<version>-<date>-<distribution>-x86_64.tgz
The tar command creates a directory based on the tar file name and
places the RPMs and other files in this directory.
3.
5-18
The RPMs must be available on each node on which they will be used. Copy
the RPMs to a directory on each node that will need them.
IB0056101-00 H
A
5–Software Installation
Install QLogic OFED User-level Software with the rpm Command
Log in as a root user, then change directories by typing:
# cd InfiniPath<version>-<date>-<distribution>-x86_64
Alternately, put the RPMs in a directory that is accessible (for example, via
Network File System (NFS)) to every node.
NOTE:
If you want to use the mpi-selector to switch between QLogic MPI
and other MPI implementations, install QLogic MPI in an alternate
location, consistent with that of the other MPIs. Skip to Step 5.
4.
To install, type the following (as a root user):
# rpm -Uvh InfiniPath/*.rpm InfiniPath-MPI/*.rpm \
InfiniPath-Devel/*.rpm OtherMPIs/*.rpm \
Documentation/*.rpm
Proceed to Step 6.
5.
To install QLogic MPI in an alternate location, type these commands instead
of those in Step 4:
# mv InfiniPath-MPI/*.rpm InfiniPath-Devel/mpi-devel* \
Documentation/mpi-doc* QLogic-MPI-prefixed/
Next, install all non-prefixed RPMs by typing:
# rpm -Uvh InfiniPath/*.rpm \
InfiniPath-Devel/infinipath-devel*.rpm \
Documentation/infinipath-doc*.rpm OtherMPIs/*.rpm
Finally, install the prefixed RPMs in /usr/mpi/qlogic by typing:
# rpm -Uvh --prefix /usr/mpi/qlogic QLogic-MPI-prefixed/*.rpm
The desired prefix should be made available in the $MPICH_ROOT
environment variable, either by global shell configuration files or through
third-party environment management utilities such as mpi-selector or the
Environment Modules. This allows QLogic MPI to correctly locate header
and library files for MPI compilation and running parallel jobs. See the
QLogic Host Channel Adapter and QLogic OFED Software Users Guide for
details.
6.
IB0056101-00 H
Reboot the machine.
5-19
S
5–Software Installation
Rebuild or Reinstall the kernel-ib Driver with rpm After a Kernel Upgrade
The complete RPM directories for this download are organized as follows:
InfiniPath_license.txt,LEGAL.txt (top level)
Documentation/
InfiniPath/
InfiniPath-Devel/
InfiniPath-MPI/
OtherMPIs/
Rebuild or Reinstall the kernel-ib Driver with
rpm After a Kernel Upgrade
If you upgrade the kernel, then you must reboot and then rebuild or reinstall the
InfiniPath kernel modules (drivers).
To rebuild the drivers, type the following (as a root user):
# cd /usr/src/qlogic_ib/kernel-ib-<version>
# ./make-install.sh
# /etc/init.d/openibd restart
An alternative method is to reinstall the InfiniPath kernel modules and then restart
the InfiniPath service. To do so, type the following (as a root user):
# rpm -U --replacepkgs kernel-ib-*
# /etc/init.d/openibd restart
Rebuild the kernel-ib Driver on an
Unsupported Distribution or an Unsupported
Distribution/Kernel Pair
If the rpm install cannot correctly determine the underlying distribution/kernel
combination, a warning message displays. This error can occur if you perform the
installation on an unsupported distribution or on an unsupported
distribution/kernel pair.
In this case, use IPATH_DISTRO to override the distribution version provided in
either the /etc/redhat-release file or the /etc/SuSE-release file.
Here is an example. These commands must be entered as a root user:
# export IPATH_DISTRO=2.6.18_EL5.1 KVER=2.6.18-53.1.14.el5
# cd /usr/src/qlogic_ib/kernel-ib-<version>
# ./make-install.sh
# /etc/init.d/openibd restart
5-20
IB0056101-00 H
A
5–Software Installation
Install QLogic OFED Using Rocks
NOTE:
Using the override may not result in a buildable or working driver if your
distribution/kernel combination is not similar enough to a tested and
supported distribution/kernel pair.
Install QLogic OFED Using Rocks
Rocks is a distribution designed for managing clusters from the San Diego
Supercomputer Center (SDSC).
Rocks is a way to manage the kickstart automated installation method created by
Red Hat. By using the Rocks conventions, the installation process can be
automated for clusters of any size. A roll is an extension to the Rocks base
distribution that supports different cluster types or provides extra functionality.
QLogic extends the normal Rocks compute node appliance xml file by adding two
functions: one function installs the InfiniPath software, and the other function
loads the drivers after kickstart reboots the machine.
Install Frontend and Compute Nodes
Rocks is based on a set of kickstart graphs (xml files) that tell the frontend node
which pieces need to be installed on which type of compute nodes. The frontend
node installs from local RPMs, then the compute nodes collect the RPMs from the
frontend. First, install a Rocks frontend node if you do not already have one.
To install a Rocks frontend node:
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
Download the InfiniPath roll (.iso image) for your distribution and burn
the .iso image to a CD.
3.
Download the required rolls from the Rocks web site:
http://www.rocksclusters.org
a.
Follow the links to get the following .iso images that can be burned to a
CD or DVD:
„
„
„
or
„
IB0056101-00 H
Kernel/Boot Roll
Core Roll
OS Roll (disk 1 & 2)
Boot, Core, OS Roll DVD
5-21
5–Software Installation
Install QLogic OFED Using Rocks
S
Note that you may also need updates; look for the latest files with the
service-pack prefix. Make sure you downloaded the .iso images
correctly; verify by checking the md5 checksum from the web site.
b.
4.
5.
Burn the .iso image(s) to CDs or DVD.
Build the frontend node with the above .iso images (Step 2) from the Rocks
web site:
a.
Insert the Kernel/Boot Roll CD into your frontend machine. After the
frontend boots from the CD, follow the instructions on the screen.
Insert the OS Rolls and any other of the Rocks Rolls you need when
prompted.
b.
To install the InfiniPath roll, put the InfiniPath CD into the drive when
prompted if you wish to install additional Rolls. Follow the instructions.
For more details, see the Rocks installation documentation on the
Rocks web site: http://www.rocksclusters.org
Install the compute nodes. Login to the frontend node as a root user, and run
the command:
# insert-ethers
This command launches a program that captures compute node DHCP
requests and puts the information into the Rocks MySQL database. Follow
the instructions on the Rocks web site: http://www.rocksclusters.org
6.
Once Rocks is up and running, test the rocks cluster according to your own
testing procedures.
NOTE:
You can also get Rolls directly from Platform OCS or ClusterCorp. The web
sites are:
http://my.platform.com/products/platform-ocs
http://www.clustercorp.com/
Rocks Installation on an Existing Frontend Node
If the frontend node has already been installed, you can add the InfiniPath Roll to
the repository on the head node, update the master graph.xml, and re-install all
the compute nodes, as described in the following paragraphs. You must be logged
in as a root user to perform these tasks.
5-22
IB0056101-00 H
A
5–Software Installation
Install QLogic OFED Using a Platform OCS Kit
If you have a burned a CD version of InfiniPath Roll from the .iso image, type:
# mount /mnt/cdrom
# rocks-dist --install copyroll
# umount /mnt/cdrom
# cd /home/install
# rocks-dist dist
If you download the .iso image without burning a CD, type:
# mount -o loop <package>iso /mnt/cdrom
# rocks-dist --install copyroll
# umount /mnt/cdrom
# cd /home/install
# rocks-dist dist
Then use the following command for each node:
# shoot-node <compute_node_name>
or
Use the following command to rebuild the entire cluster:
# cluster-fork /boot/kickstart/cluster-kickstart
Install QLogic OFED Using a Platform OCS Kit
The Platform Open Cluster Stack (OCS) Kit is an ISO image that automatically
installs the drivers. Kits are a mechanism for packaging install scripts and
applications for easy installation onto a Platform OCS cluster. To get started:
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
Download the InfiniPath Platform OCS Kit (.iso image) for your distribution.
3.
Follow the instructions provided by Platform OCS for installing Kits. See
http://my.platform.com/products/platform-ocs
IB0056101-00 H
5-23
5–Software Installation
Install the QLogic InfiniBand Fabric Suite Software
S
Install the QLogic InfiniBand Fabric Suite
Software
The QLogic InfiniBand Fabric Suite software is part of the QLogic InfiniBand
Fabric Suite; however, it can be purchased separately. To install the QLogic
InfiniBand Fabric Suite:
1.
From the QLogic web site (www.qlogic.com), click the Downloads tab.
Locate your adapter model.
2.
Locate the QLogic InfiniBand Fabric Suite link and follow instructions for
purchasing the software.
3.
Follow the installation instructions in the current version of the QLogic Fabric
Software Installation Guide, available with the software or from the
Downloads tab on the QLogic web site.
Install Lustre Software
This section contains information about additional third-party software installation.
This InfiniPath release supports Lustre cluster filesystem Version 1.6.5.1. Lustre is
a fast, scalable Linux cluster file system that interoperates with InfiniBand. For
general instructions on downloading, installing, and using Lustre, go to:
http://www.lustre.org
Installed Layout
This section describes the default installed layout for the InfiniPath software and
QLogic-supplied MPIs.
The shared libraries are installed in:
/usr/lib for 32-bit applications
/usr/lib64 for 64-bit applications
MPI include files are in:
/usr/include
MPI programming examples and the source for several MPI benchmarks are in:
/usr/share/mpich/examples
5-24
IB0056101-00 H
A
5–Software Installation
Installed Layout
NOTE:
If QLogic MPI is installed in an alternate location, the argument passed to
--prefix (/usr/mpi/qlogic) replaces the default /usr prefix. QLogic
MPI binaries, documentation, and libraries are installed under that prefix.
However, a few configuration files are installed in /etc regardless of the
desired --prefix. The remaining InfiniPath libraries and tools stay in their
default installation location.
If you have installed the software into an alternate location, the
$MPICH_ROOT environment variable needs to match --prefix.
InfiniPath utility programs, as well as MPI utilities and benchmarks, are installed
in:
/usr/bin
Documentation is found in:
/usr/share/man
/usr/share/doc/infinipath
/usr/share/doc/mpich-infinipath
Note that license information is found only in usr/share/doc/infinipath.
InfiniPath user documentation can be found on the QLogic web site on the
software download page for your distribution.
Configuration files are found in:
/etc/sysconfig
Init scripts are found in:
/etc/init.d
The InfiniPath driver modules in this release are installed in:
/lib/modules/$(uname -r)/updates/kernel/drivers/infiniband/hw/ipath
Most of the other OFED modules are installed under the infiniband
subdirectory. Other modules are installed under:
/lib/modules/$(uname -r)/updates/kernel/drivers/net
The RDS modules are installed under:
/lib/modules/$(uname -r)/updates/kernel/net/rds
QLogic-supplied OpenMPI and MVAPICH RPMs with PSM support and compiled
with GCC, PathScale, PGI, and the Intel compilers are now installed in directories
using this format:
/usr/mpi/<compiler>/<mpi>-<mpi_version>-qlc
IB0056101-00 H
5-25
5–Software Installation
Remove Software Packages
S
For example:
/usr/mpi/gcc/openmpi-1.2.8-qlc
Remove Software Packages
This section provides instructions for uninstalling or downgrading the InfiniPath
and OpenFabrics software.
Uninstall Using the Installer Tool
Software packages can be removed by using the Installer tool. Instructions are
similar to those in “Install QLogicIB-Basic with the Installer Tool” on page 5-8,
except that you select the Uninstall option for the desired packages.
Uninstall InfiniPath and OpenFabrics RPMs
QLogic recommends uninstalling the OFED software before uninstalling the
InfiniPath software.
For both InfiniPath and OpenFabrics, QLogic recommends that you remove all the
packages at the same time.
1.
Use the script ofed_uninstall.sh to uninstall the OFED software. See
the OFED Installation release notes that are part of the OFED
documentation.
2.
To uninstall the InfiniPath software packages on any node with the rpm
command, type the following command (as a root user) using a bash shell:
# rpm -e --allmatches ‘rpm -qa | grep qlc‘
The qlc nomenclature is part of all the InfiniPath package names.
Uninstall Software with Rocks or Platform OCS
Follow the instructions for either Rocks or Platform OCS to uninstall software.
See:
http://www.rocksclusters.org
http://my.platform.com/products/platform-ocs
5-26
IB0056101-00 H
A
5–Software Installation
Remove Software Packages
Install a Previous Version of QLogicIB-Basic
If you need to install a previous version of QLogicIB-Basic, use the following
procedure.
1.
Uninstall all existing software using the following command:
iba_config -u
2.
Install the older version of the software using the installation procedures
provided in the documentation that was released for that specific version of
the software.
3.
Carefully review all configuration files for information that may need to be
discarded or edited that are specific to features in the newer release that
were not available in the older release.
4.
Reboot the server.
Downgrading RPMs
If you want to downgrade, remove both the InfiniPath and OpenFabrics RPMs,
then install the older bits. QLogic has determined that rpm flags like
"--oldpackage" do not generate a correct downgrade.
NOTE:
Use the rpm method for downgrading rather than the Installer tool.
IB0056101-00 H
5-27
5–Software Installation
Remove Software Packages
S
Notes
5-28
IB0056101-00 H
6
Configuring Drivers and
Services
This section provides instructions for configuring and using the drivers and
services available with QLogic OFED 1.4.
InfiniPath and OpenFabrics Driver Overview
The InfiniPath ib_ipath module provides low-level QLogic hardware support,
and is the base driver for both MPI/PSM programs and general OpenFabrics
protocols such as IPoIB and SDP. The driver also supplies the Subnet
Management Agent (SMA) component.
Optional configurable OpenFabrics components and their default settings at
startup are:
„
IPoIB network interface. This component is required for TCP/IP networking
for running Ethernet traffic over the InfiniPath link. It is not running until it is
configured.
„
VNIC. It is not running until it is configured.
„
OpenSM. This component is disabled at startup. You can install it on only
one node, or disable it on all nodes except where it will be used as an SM.
„
SRP (OFED and QLogic modules). SRP is not running until the module is
loaded and the SRP devices on the fabric have been discovered.
„
MPI over uDAPL (can be used by Intel MPI or HP®-MPI). IPoIB must be
configured before MPI over uDAPL can be set up.
Other optional drivers can now be configured and enabled, as described in
“OpenFabrics Drivers and Services Configuration and Startup” on page 6-1.
Complete information about starting, stopping, and restarting the InfiniPath
services is in “Managing the InfiniPath Driver” on page 6-14.
OpenFabrics Drivers and Services Configuration
and Startup
IPoIB, VNIC, OpenSM, SRP, and MPI over uDAPL configuration and startup is
explained in detail in the following sections.
IB0056101-00 H
6-1
S
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
Configure the IPoIB Network Interface
The following instructions show you how to manually configure your OpenFabrics
IPoIB network interface. This example assumes that you are using sh or bash as
your shell, all required InfiniPath and OpenFabrics RPMs are installed, and your
startup scripts have been run (either manually or at system boot).
For this example, the IPoIB network is 10.1.17.0 (one of the networks reserved for
private use, and thus not routable on the Internet), with a /8 host portion. In this
case, the netmask must be specified.
This example assumes that no hosts files exist, the host being configured has the
IP address 10.1.17.3, and DHCP is not used.
NOTE:
Instructions are only for this static IP address case. Configuration methods
for using DHCP will be supplied in a later release.
1.
Type the following command (as a root user):
# ifconfig ib0 10.1.17.3 netmask 0xffffff00
2.
To verify the configuration, type:
# ifconfig ib0
The output from this command will be similar to:
ib0
Link encap:InfiniBand HWaddr
00:00:00:02:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
inet addr:10.1.17.3
Bcast:10.1.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST
MTU:4096
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:128
RX bytes:0 (0.0 b)
3.
TX bytes:0 (0.0 b)
Type:
# ping -c 2 -b 10.1.17.255
The output of the ping command will be similar to the following, with a line
for each host already configured and connected:
WARNING: pinging broadcast address
PING 10.1.17.255 (10.1.17.255) 517(84) bytes of data.
174 bytes from 10.1.17.3: icmp_seq=0 ttl=174 time=0.022 ms
64 bytes from 10.1.17.1: icmp_seq=0 ttl=64 time=0.070 ms (DUP!)
64 bytes from 10.1.17.7: icmp_seq=0 ttl=64 time=0.073 ms (DUP!)
6-2
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
The IPoIB network interface is now configured.
4.
Restart (as a root user) by typing:
# /etc/init.d/openibd restart
NOTE:
„ The configuration must be repeated each time the system is rebooted.
„ IPoIB-CM (Connected Mode) is enabled by default. The setting in
/etc/infiniband/openib.conf is SET_IPOIB_CM=yes. To use
datagram mode, use change the setting to SET_IPOIB_CM=no.
OpenSM
OpenSM is an optional component of the OpenFabrics project that provides a
Subnet Manager (SM) for InfiniBand networks. This package can be installed on
all machines, but only needs to be enabled on the machine in the cluster that will
act as a subnet manager. You do not need to use OpenSM if any of your
InfiniBand switches provide a subnet manager, or if you are running a host-based
SM.
If you are using the Installer tool, you can set the OpenSM default behavior at the
time of installation.
If you are using the rpm install method, note that after installing the opensm
package, OpenSM is configured to be off after the next machine reboot. It only
needs to be enabled on the node that acts as the subnet manager, so use the
chkconfig command (as a root user) to enable it on the node where it will be
run:
# chkconfig opensmd on
The command to disable it on reboot is:
# chkconfig opensmd off
You can start opensmd without rebooting your machine by typing:
# /etc/init.d/opensmd start
You can stop opensmd again by typing:
# /etc/init.d/opensmd stop
If you want to pass any arguments to the OpenSM program, modify the following
file, and add the arguments to the OPTIONS variable:
/etc/init.d/opensmd
IB0056101-00 H
6-3
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
S
For example:
# Use the UPDN algorithm instead of the Min Hop algorithm.
OPTIONS="-R updn"
For more information on OpenSM, see the OpenSM man pages, or look on the
OpenFabrics web site.
SRP
SRP stands for SCSI RDMA Protocol. It was originally intended to allow the SCSI
protocol to run over InfiniBand for Storage Area Network (SAN) usage. SRP
interfaces directly to the Linux file system through the SRP Upper Layer Protocol
(ULP). SRP storage can be treated as another device.
In this release, two versions of SRP are available: QLogic SRP and OFED SRP.
QLogic SRP is available as part of the QLogicIB-Basic, Rocks Roll, and Platform
OCS downloads. It is not available as a part of the RPM downloads.
SRP has been tested on targets from Engenio™ (now LSI Logic®) and DataDirect
Networks™.
NOTE:
Before using SRP, the SRP targets must already be set up by your system
administrator.
Using QLogic SRP
If you installed QLogic SRP as part of the QLogicIB-Basic download, configure it
according to the steps shown in the QLogic ULP and Tools Reference Guide
(OFED+ Users Guide).
Using OFED SRP
To use OFED SRP, follow these steps:
1.
Add the line SRP_LOAD=yes to the module list in
/etc/infiniband/openib.conf to have it automatically loaded.
2.
Discover the SRP devices on your fabric by running this command (as a root
user):
# ibsrpdm
In the output, look for lines similar to these:
GUID:
0002c90200402c04
ID:
LSI Storage Systems SRP Driver 200400a0b8114527
service entries: 1
service[
6-4
0]: 200400a0b8114527 / SRP.T10:200400A0B8114527
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
GUID:
0002c90200402c0c
ID:
LSI Storage Systems SRP Driver 200500a0b8114527
service entries: 1
service[
0]: 200500a0b8114527 / SRP.T10:200500A0B8114527
GUID:
21000001ff040bf6
ID:
Data Direct Networks SRP Target System
service entries: 1
service[
0]: f60b04ff01000021 / SRP.T10:21000001ff040bf6
Note that not all the output is shown here; key elements are expected to
show the match in Step 3.
3.
Choose the device you want to use, and run the command again with the -c
option (as a root user):
# ibsrpdm -c
id_ext=200400A0B8114527,ioc_guid=0002c90200402c04,dgid=fe8000
00000000000002c90200402c05,pkey=ffff,service_id=200400a0b8114
527
id_ext=200500A0B8114527,ioc_guid=0002c90200402c0c,dgid=fe8000
00000000000002c90200402c0d,pkey=ffff,service_id=200500a0b8114
527
id_ext=21000001ff040bf6,ioc_guid=21000001ff040bf6,dgid=fe8000
000000000021000001ff040bf6,pkey=ffff,service_id=f60b04ff01000
021
4.
Find the result that corresponds to the target you want, and echo it into the
add_target file:
# echo
"id_ext=21000001ff040bf6,ioc_guid=21000001ff040bf6,dgid=fe800
0000000000021000001ff040bf6,pkey=ffff,service_id=f60b04ff0100
0021,initiator_ext=0000000000000001" >
/sys/class/infiniband_srp/srp-ipath0-1/add_target
5.
Look for the newly created devices in the /proc/partitions file. The file
will look similar to this example (the partition names may vary):
# cat /proc/partitions
major minor
IB0056101-00 H
#blocks
name
8
64
142325760 sde
8
65
142319834 sde1
8
80
71162880 sdf
8
81
71159917 sdf1
8
96
20480 sdg
8
97
20479 sdg1
6-5
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
6.
S
Create a mount point (as root) where you will mount the SRP device. For
example:
# mkdir /mnt/targetname
# mount /dev/sde1 /mnt/targetname
NOTE:
Use sde1 rather than sde. See the mount(8) man page for more
information on creating mount points.
Configuring and Administering the VNIC Interface
The VirtualNIC (VNIC) Upper Layer Protocol (ULP) works in conjunction with
firmware running on Virtual Input/Output (VIO) hardware such as the SilverStorm®
Ethernet Virtual I/O Controller (EVIC™) or the InfiniBand/Ethernet Bridge Module
for IBM® BladeCenter®, providing virtual Ethernet connectivity.
The VNIC driver, along with QLogic EVIC’s two 10 Gigabit ethernet ports, enables
Infiniband clusters to connect to Ethernet networks. This driver also works with the
earlier version of the I/O controller, the VEx.
The QLogic VNIC driver creates virtual Ethernet interfaces and tunnels the
Ethernet data to/from the EVIC over InfiniBand using an InfiniBand reliable
connection.
The virtual Ethernet interface supports any Ethernet protocol. It operates like any
other interface: ping, ssh, scp, netperf, etc.
The VNIC interface must be configured before it can be used. To do so, perform
the following steps:
1.
Discover the EVIC/VEx Input/Output Controllers (IOCs) present on the fabric
using the ib_qlgc_vnic_query command. For writing the configuration
file, you will need information about the EVIC/VEx IOCs present on the
fabric, such as their IOCGUID, IOCSTRING, etc. Use the
ib_qlgc_vnic_query tool to get this information.
When ib_qlgc_vnic_query is executed without any options, it displays
detailed information about all the EVIC/VEx IOCs present on the fabric. Run
it as a root user. For example:
# ib_qlgc_vnic_query
HCA No = 0, HCA = mlx4_0, Port = 1, Port GUID = 0x0002c903000010f9,
State = Active
IO Unit Info:
port LID:
0009
port GID:
fe8000000000000000066a11de000070
change ID:
0003
max controllers: 0x02
6-6
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
controller[ 1]
GUID:
00066a01de000070
vendor ID: 00066a
device ID: 000030
IO class : 2000
ID:
EVIC in Chassis 0x00066a00db00001e, Slot 1, Ioc 1
service entries: 2
service[ 0]: 1000066a00000001 /
InfiniNIC.InfiniConSys.Control:01
service[ 1]: 1000066a00000101 /
InfiniNIC.InfiniConSys.Data:01
IO Unit Info:
port LID:
000b
port GID:
fe8000000000000000066a21de000070
change ID:
0003
max controllers: 0x02
controller[ 2]
GUID:
00066a02de000070
vendor ID: 00066a
device ID: 000030
IO class : 2000
ID:
EVIC in Chassis 0x00066a00db00001e, Slot 1, Ioc 2
service entries: 2
service[ 0]: 1000066a00000002 /
InfiniNIC.InfiniConSys.Control:02
service[ 1]: 1000066a00000102 /
InfiniNIC.InfiniConSys.Data:02
HCA No = 0, HCA = mlx4_0, Port = 2, Port GUID = 0x0002c903000010fa,
State = Active
IO Unit Info:
port LID:
0009
port GID:
fe8000000000000000066a11de000070
change ID:
0003
max controllers: 0x02
IB0056101-00 H
6-7
S
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
controller[ 1]
GUID:
00066a01de000070
vendor ID: 00066a
device ID: 000030
IO class : 2000
ID:
EVIC in Chassis 0x00066a00db00001e, Slot 1, Ioc 1
service entries: 2
service[ 0]: 1000066a00000001 /
InfiniNIC.InfiniConSys.Control:01
service[ 1]: 1000066a00000101 /
InfiniNIC.InfiniConSys.Data:01
IO Unit Info:
port LID:
port GID:
change ID:
max controllers:
000b
fe8000000000000000066a21de000070
0003
0x02
controller[ 2]
GUID:
00066a02de000070
vendor ID: 00066a
device ID: 000030
IO class : 2000
ID:
EVIC in Chassis 0x00066a00db00001e, Slot 1, Ioc 2
service entries: 2
service[ 0]: 1000066a00000002 /
InfiniNIC.InfiniConSys.Control:02
service[ 1]: 1000066a00000102 /
InfiniNIC.InfiniConSys.Data:02
NOTE:
A VIO hardware card can contain up to six IOCs (and therefore up to
six IOCGUIDs); one for each Ethernet port on the VIO hardware card.
Each VIO hardware card contains a unique set of IOCGUIDs; for
example, IOC 1 maps to Ethernet Port 1, IOC 2 maps to Ethernet
Port 2, IOC 3 maps to Ethernet Port 3, etc.
2.
6-8
Create the VNIC interfaces using the configuration file
/etc/infiniband/qlgc_vnic.cfg.
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
Look at the qlgc_vnic.cfg.sample file to see how VNIC configuration
files are written. This file can be found with the OFED documentation, or in
the qlgc_vnictools subdirectory of the QLogicIB_Basic download. You
can use this configuration file as the basis for creating a configuration file by
replacing the destination global identifier (DGID), IOCGUID, and
IOCSTRING values with those of the EVIC/VEx IOCs present on your fabric.
QLogic recommends using the DGID of the EVIC/VEx IOC, as it ensures the
quickest startup of the VNIC service. When DGID is specified, the IOCGUID
must also be specified. For more details, see the qlgc_vnic.cfg sample
file.
3.
Edit the VirtualNIC configuration file,
/etc/infiniband/qlgc_vnic.cfg. For each IOC connection, add a
CREATE block to the file using the following format:
{CREATE; NAME="eioc2";
PRIMARY={IOCGUID=0x66A0130000105; INSTANCE=0; PORT=1; }
SECONDARY={IOCGUID=0x66A013000010C; INSTANCE=0; PORT=2;}
}
NOTE:
The qlgc_vnic.cfg file is case and format sensitive.
a.
Format 1: Define an IOC using the IOCGUID. Use the following format
to allow the host to connect to a specific VIO hardware card,
regardless of which chassis and/or slot the VIO hardware card resides:
{CREATE;
NAME="eioc1";
IOCGUID=0x66A0137FFFFE7;}
The following is an example of VIO hardware failover:
{CREATE; NAME="eioc1";
PRIMARY={IOCGUID=0x66a01de000003; INSTANCE=1; PORT=1; }|
SECONDARY={IOCGUID=0x66a02de000003; INSTANCE=1; PORT=1;}
}
NOTE:
Do not create EIOC names with similar character strings (for
example, eioc3 and eioc30). There is a limitation with certain
Linux operating systems that cannot recognize the subtle
differences. The result is that the user will be unable to ping
across the network.
IB0056101-00 H
6-9
S
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
b.
Format 2: Define an IOC using the IOCSTRING. Defining the IOC
using the IOCSTRING allows VIO hardware to be hot-swapped in and
out of a specific slot. The host attempts to connect to the specified IOC
(1, 2, or 3) on the VIO hardware that currently resides in the specified
slot of the specified chassis. Use the following format to allow the host
to connect to a VIO hardware that resides in a specific slot of a specific
chassis:
{CREATE;
NAME="eioc1";
IOCSTRING="Chassis 0x00066A0005000001, Slot 1, IOC 1";
RX_CSUM=TRUE;
HEARTBEAT=100; }
NOTE:
The IOCSTRING field is a literal, case-sensitive string. Its syntax
must be exactly in the format shown in the previous example,
including the placement of commas. To reduce the likelihood of
syntax error, use the command ib_qlgc_vnic_query -es.
Note that the chassis serial number must match the chassis Ox
(hex) value. The slot serial number is specific to the line card as
well.
Each CREATE block must specify a unique NAME. The NAME
represents the Ethernet interface name that will be registered with the
Linux operating system.
c.
Format 3: Start VNIC using DGID. Following is an example of a DGID
and IOCGUID VNIC configuration. This configuration allows for the
quickest start up of VNIC service:
{CREATE; NAME="eioc1";
DGID=0xfe8000000000000000066a0258000001;IOCGUID=0x66a0130
000001;
}
This example uses DGID, IOCGUID, and IOCSTRING:
{CREATE; NAME="eioc1";
DGID=0xfe8000000000000000066a0258000001;
IOCGUID=0x66a0130000001;
IOCSTRING="Chassis 0x00066A00010003F2, Slot 1, IOC 1";
}
6-10
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
4.
Create VirtualNIC interface configuration files. For each Ethernet interface
defined in the /etc/sysconfig/qlgc_vnic.cfg file, create an interface
configuration file, /etc/sysconfig/network-scripts/ifcfg-<NAME>
(or /etc/sysconfig/network/ifcfg-<NAME> on Linux 2.6 kernels),
where <NAME> is the value of the NAME field specified in the CREATE
block.
Following is an example of ifcfg-eiocx setup for Red Hat systems:
DEVICE=eioc1
BOOTPROTO=static
IPADDR=172.26.48.132
BROADCAST=172.26.63.130
NETMASK=255.255.240.0
NETWORK=172.26.48.0
ONBOOT=yes
TYPE=Ethernet
Following is an example of ifcfg-eiocx setup for SuSE and SLES
systems:
BOOTPROTO=’static’
IPADDR=’172.26.48.130’
BROADCAST=’172.26.63.255’
NETMASK=’255.255.240.0’
NETWORK=’172.26.48.0’
STARTMODE=’hotplug’
TYPE=’Ethernet’
5.
Start the QLogic VNIC driver and the QLogic VNIC interfaces. Once you
have created a configuration file, you can start the VNIC driver and create
the VNIC interfaces specified in the configuration file by running the
following command (as a root user):
# /etc/init.d/qlgc_vnic start
You can stop the VNIC driver and bring down the VNIC interfaces by running
the following command:
# /etc/init.d/qlgc_vnic stop
To restart the QLogic VNIC driver, run the following command:
# /etc/init.d/qlgc_vnic restart
If you have not started the InfiniBand network stack (InfiniPath or OFED),
then running the /etc/init.d/qlgc_vnic start command also starts
the InfiniBand network stack, since the QLogic VNIC service requires the
InfiniBand stack.
IB0056101-00 H
6-11
S
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
If you start the InfiniBand network stack separately, then the correct starting
order is:
„
„
Start the InfiniBand stack.
Start QLogic VNIC service.
For example, if you use InfiniPath, the correct starting order is:
# /etc/init.d/openibd start
# /etc/init.d/qlgc_vnic start
The correct stopping order is:
„
„
Stop QLogic VNIC service.
Stop the InfiniBand stack.
For example, if you use InfiniPath, the correct stopping order is:
# /etc/init.d/qlgc_vnic stop
# /etc/init.d/openibd stop
If you try to stop the InfiniBand stack when the QLogic VNIC service is
running, an error message displays, indicating that some of the modules of
the InfiniBand stack are in use by the QLogic VNIC service. Also, any
QLogic VNIC interfaces that you created are removed (because stopping
the InfiniBand network stack unloads the Host Channel Adapter driver,
which is required for the VNIC interfaces to be present).
In this case, do the following:
„
Stop the QLogic VNIC service by typing:
/etc/init.d/qlgc_vnic stop
„
Stop the InfiniBand stack again.
If you want to restart the QLogic VNIC interfaces, run the following
command:
# /etc/init.d/qlgc_vnic restart
You can get information about the QLogic VNIC interfaces by using the following
script (as a root user):
# ib_qlgc_vnic_info
This information is collected from the
/sys/class/infiniband_qlgc_vnic/interfaces/ directory, under which
there is a separate directory corresponding to each VNIC interface.
VNIC interfaces can be deleted by writing the name of the interface to the
/sys/class/infiniband_qlgc_vnic/interfaces/delete_vnic file. For
example, to delete interface veth0, run the following command (as a root user):
# echo -n veth0 >
/sys/class/infiniband_qlgc_vnic/interfaces/delete_vnic
6-12
IB0056101-00 H
A
6–Configuring Drivers and Services
OpenFabrics Drivers and Services Configuration and Startup
More information for configuration, starting and stopping the interface, and basic
troubleshooting is found in the QLogic OFED+ User Guide.
MPI over uDAPL
Intel MPI can be run over uDAPL, which uses IB Verbs. uDAPL is the user mode
version of the Direct Access Provider Library (DAPL), and is provided as a part of
the OFED packages. You will also have to have IPoIB configured.
The setup for Intel MPI is described in the following steps:
1.
Make sure that DAPL 1.2 (not version 2.0) is installed on every node. In this
release they are called compat-dapl. (Both versions are supplied with the
OpenFabrics RPMs.) They can be installed either with the installer with the
QLogicIB-Basic package or with rpm with the QLogic OFED 1.4 RPM set.
For example:
$ rpm -qa | grep compat-dapl
compat-dapl-1.2.12-1.x86_64.rpm
compat-dapl-debuginfo-1.2.12-1.x86_64.rpm
compat-dapl-devel-1.2.12-1.x86_64.rpm
compat-dapl-devel-static-1.2.12-1.x86_64.rpm
compat-dapl-utils-1.2.12-1.x86_64.rpm
2.
Verify that there is a /etc/dat.conf file. It should be installed by the
dapl- RPM. The file dat.conf contains a list of interface adapters
supported by uDAPL service providers. In particular, it must contain
mapping entries for OpenIB-cma for dapl 1.2.x, in a form similar to this
(all on one line):
OpenIB-cma u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2
"ib0 0" ""
3.
On every node, type the following command (as a root user):
# modprobe rdma_ucm
To ensure that the module is loaded when the driver is loaded, add
RDMA_UCM_LOAD=yes to the /etc/infiniband/openib.conf file.
(Note that rdma_cm is also used, but it is loaded automatically.)
4.
Bring up an IPoIB interface on every node, for example, ib0. See the
instructions for configuring IPoIB for more details.
For more information on using Intel MPI, see the “Using Other MPIs” section in the
QLogic Host Channel Adapter and QLogic OFED Software Users Guide.
IB0056101-00 H
6-13
6–Configuring Drivers and Services
Other Configuration: Changing the MTU Size
S
Other Configuration: Changing the MTU Size
The Maximum Transfer Unit (MTU) is set to 4K and enabled in the driver by
default. To change the driver default back to 2K MTU, add this line (as root) in
/etc/modprobe.conf (or in /etc/modprobe.conf.local on SLES):
options ib_ipath mtu4096=0
Restart the driver as described in “Managing the InfiniPath Driver” on page 6-14.
NOTE:
To use 4K MTU, set the switch to have the same 4K default. If you are using
QLogic switches, the following applies:
„ For the Externally Managed 9024, use 4.2.2.0.3 firmware
(9024DDR4KMTU_firmware.emfw) for the 9024 EM. This has the 4K
MTU default, for use on fabrics where 4K MTU is required. If 4K MTU
support is not required, then use the 4.2.2.0.2 DDR *.emfw file for
DDR externally-managed switches. Use FastFabric to load the firmware
on all the 9024s on the fabric.
„ For the 9000 chassis, use the most recent 9000 code 4.2.4.0.1. The 4K
MTU support is in 9000 chassis version 4.2.1.0.2 and above. For the
9000 chassis, when the FastFabric 4.3 (or later) chassis setup tool is
used, the user is prompted for the MTU. FastFabric can then set that
MTU in all the 9000 internally managed switches. The change will take
effect on the next reboot. Alternatively, for the internally managed 9000s,
the ismChassisSetMtu Command Line Interface (CLI) command can
be used. This should be executed on every switch and both
hemispheres of the 9240s.
For reference, see the FastFabric Users Guide Version 4.3 and the
SIlverStorm 9000 CLI Reference Guide Version 4.2. Both are available from
the QLogic web site.
For other switches, see the vendors’ documentation.
Managing the InfiniPath Driver
The startup script for ib_ipath is installed automatically as part of the software
installation, and normally does not need to be changed. It runs as a system
service.
The primary configuration file for the InfiniPath driver ib_ipath and other
modules and associated daemons is /etc/infiniband/openib.conf.
6-14
IB0056101-00 H
A
6–Configuring Drivers and Services
Managing the InfiniPath Driver
Normally, this configuration file is set up correctly at installation and the drivers are
loaded automatically during system boot once the RPMs have been installed.
However, the ib_ipath driver has several configuration variables that set
reserved buffers for the software, define events to create trace records, and set
the debug level.
If you are upgrading, your existing configuration files will not be overwritten.
The device files are:
/dev/ipath
/dev/ipath0, /dev/ipath1, ...
The numbered device files allow access to a specific InfiniPath unit.
See the ib_ipath man page for more details.
Configure the InfiniPath Driver State
Use the following commands to check or configure the state. These methods will
not reboot the system.
To check the configuration state, use this command. You do not need to be a root
user:
$ chkconfig --list openibd
To enable the driver, use the following command (as a root user):
# chkconfig openibd on 2345
To disable the driver on the next system boot, use the following command (as a
root user):
# chkconfig openibd off
NOTE:
This command does not stop and unload the driver if the driver is already
loaded.
Start, Stop, or Restart InfiniPath
Restart the software if you install a new InfiniPath release, change driver options,
or do manual testing.
You can start, stop, or restart (as a root user) InfiniPath support with:
# /etc/init.d/openibd [start | stop | restart]
IB0056101-00 H
6-15
S
6–Configuring Drivers and Services
Managing the InfiniPath Driver
This method will not reboot the system. The following set of commands shows
how to use this script.
If OpenSM is configured and running, it must be stopped before the openibd
stop command, and must be started after the openibd start command. Omit
the commands to start/stop opensmd if you are not running it on that node.
The sequence of commands to restart the driver are as follows:
# /etc/init.d/opensmd stop
# /etc/init.d/openibd stop
...
# /etc/init.d/openibd start
# /etc/init.d/opensmd start
The ... represents whatever activity you are engaged in after infinipath is
stopped.
An equivalent way to restart the driver this is to use same sequence shown
previously, except use the restart command instead of start and stop:
# /etc/init.d/opensmd stop
# /etc/init.d/openibd restart
# /etc/init.d/opensmd start
NOTE:
Stopping or restarting openibd terminates any QLogic MPI processes, as
well as any OpenFabrics processes that are running at the time.
You can check to see if opensmd is running by using the following command (as a
root user); if there is no output, opensmd is not configured to run:
# /sbin/chkconfig --list opensmd | grep -w on
When you need to determine which InfiniPath and OpenFabrics modules are
running, use the following command. You do not need to be a root user.
$ lsmod | egrep ’ipath_|ib_|rdma_|findex’
Unloading the Driver/Modules Manually
You can also unload the driver/modules manually without using
/etc/init.d/openibd. Use the following series of commands (as a root user):
# umount /ipathfs
# fuser -k /dev/ipath* /dev/infiniband/*
# lsmod | egrep ’^ib_|^rdma_|^iw_’ | xargs modprobe -r
6-16
IB0056101-00 H
A
6–Configuring Drivers and Services
Further Information on Configuring and Loading Drivers
Further Information on Configuring and Loading
Drivers
See the modprobe(8), modprobe.conf(5), and lsmod(8) man pages for
more information. Also see the file (on Red Hat systems):
/usr/share/doc/initscripts-*/sysconfig.txt
IB0056101-00 H
6-17
6–Configuring Drivers and Services
Further Information on Configuring and Loading Drivers
S
Notes
6-18
IB0056101-00 H
7
Installation Verification and
Additional Settings
This section provides instructions for verifying that the software has been properly
installed, the drivers are loaded, and that the fabric is active and ready to use.
Information on adapter performance tuning is also provided.
LED Link and Data Indicators
The LEDs function as link and data indicators once the InfiniPath software has
been installed, the driver has been loaded, and the fabric is being actively
managed by a subnet manager.
Table 7-1 describes the LED states. The green LED indicates the physical link
signal; the amber LED indicates the link. The green LED normally illuminates first.
The normal state is Green On, Amber On. The QLE7240 and QLE7280 have an
additional state, as shown in Table 7-1.
Table 7-1. LED Link and Data Indicators
LED States
Green OFF
Amber OFF
Indication
The switch is not powered up. The software is neither
installed nor started. Loss of signal.
Verify that the software is installed and configured with
ipath_control -i. If correct, check both cable connectors.
Green ON
Amber OFF
Signal detected and the physical link is up. Ready to talk
to SM to bring the link fully up.
If this state persists, the SM may be missing or the link
may not be configured.
Use ipath_control -i to verify the software state. If
all host channel adapters are in this state, then the SM is
not running. Check the SM configuration, or install and
run opensmd.
IB0056101-00 H
7-1
S
7–Installation Verification and Additional Settings
Adapter and Other Settings
Table 7-1. LED Link and Data Indicators (Continued)
LED States
Green ON
Amber ON
Indication
The link is configured, properly connected, and ready.
Signal detected. Ready to talk to an SM to bring the link
fully up.
The link is configured. Properly connected and ready to
receive data and link packets.
Green BLINKING (quickly)
Indicates traffic
Amber ON
Green BLINKING a
Locates the adapter
Amber BLINKING
This feature is controlled by ipath_control -b [On
| Off]
Table Notes
a
This feature is available only on the QLE7240 and QLE7280 adapters
Adapter and Other Settings
The following settings can be adjusted for better performance.
7-2
„
Use taskset to tune CPU affinity on Opteron systems with the
QLE7240, QLE7280, and QLE7140. Latency will be slightly lower for the
Opteron socket that is closest to the PCI Express bridge. On some chipsets,
bandwidth may be higher on this socket. See the QLogic Host Channel
Adapter and QLogic OFED Software Users Guide for more information on
using taskset. Also see the taskset(1) man page.
„
On the switch, use an IB MTU of 4096 bytes instead of 2048 bytes, if
available, with the QLE7240, QLE7280, and QLE7140. 4K MTU is
enabled in the InfiniPath driver by default. To change this setting for the
driver, see “Other Configuration: Changing the MTU Size” on page 6-14.
„
Use a PCIe Max Read Request size of at least 512 bytes with the
QLE7240 and QLE7280. QLE7240 and QLE7280 adapters can support
sizes from 128 bytes to 4096 bytes in powers of two. This value is typically
set in the BIOS.
„
Use a PCIe MaxPayload size of 256, where available, with the QLE7240
and QLE7280. The QLE7240 and QLE7280 adapters can support 128, 256,
or 512 bytes. This value is typically set by the BIOS as the minimum value
supported both by the PCIe card and the PCIe root complex.
„
Make sure that write combining is enabled. The x86 Page Attribute Table
(PAT) mechanism that allocates Write Combining (WC) mappings for the
PIO buffers has been added and is now the default. If PAT is unavailable or
IB0056101-00 H
A
7–Installation Verification and Additional Settings
Customer Acceptance Utility
PAT initialization fails for some reason, the code will generate a message in
the log and fall back to the MTRR mechanism. See “Write Combining” on
page B-1 for more information.
„
Check the PCIe bus width. If slots have a smaller electrical width than
mechanical width, lower than expected performance may occur. Use this
command to check PCIe Bus width:
$ ipath_control -iv
This command also shows the link speed.
Customer Acceptance Utility
ipath_checkout is a bash script that verifies that the installation is correct and
that all the nodes of the network are functioning and mutually connected by the
InfiniPath fabric. It must be run on a front end node, and requires specification of a
nodefile. For example:
$ ipath_checkout [options] nodefile
The nodefile lists the hostnames of the nodes of the cluster, one hostname per
line. The format of nodefile is as follows:
hostname1
hostname2
...
NOTE:
„ The hostnames in the nodefile are Ethernet hostnames, not IPv4
addresses.
„ To create a nodefile, use the ibhosts program. It will generate a list
of available nodes that are already connected to the switch. The
ibhosts program is described in more detail in the QLogic Host
Channel Adapter and QLogic OFED Software Users Guide.
ipath_checkout performs the following seven tests on the cluster:
1.
Executes the ping command to all nodes to verify that they all are
reachable from the front end.
2.
Executes the ssh command to each node to verify correct configuration
of ssh.
3.
Gathers and analyzes system configuration from the nodes.
4.
Gathers and analyzes RPMs installed on the nodes. Missing RPMs can be
found this way.
IB0056101-00 H
7-3
S
7–Installation Verification and Additional Settings
Customer Acceptance Utility
5.
Verifies QLogic hardware and software status and configuration. Includes
tests for link speed, PIO bandwidth (incorrect MTRR settings), and MTU
size.
6.
Verifies the ability to mpirun jobs on the nodes.
7.
Runs a bandwidth and latency test on every pair of nodes and analyzes the
results.
The options available with ipath_checkout are shown in Table 7-2.
Table 7-2. ipath_checkout Options
Command
Meaning
-h, --help
These options display help messages describing how a command is used.
-v, --verbose
-vv, --vverbose
-vvv, --vvverbose
These options specify three successively higher levels of
detail in reporting test results. There are four levels of detail
in all, including the case where none of these options are
given.
-c, --continue
When this option is not specified, the test terminates when
any test fails. When specified, the tests continue after a failure, with failing nodes excluded from subsequent tests.
-k, --keep
This option keeps intermediate files that were created while
performing tests and compiling reports. Results will be saved
in a directory created by mktemp and named
infinipath_XXXXXX or in the directory name given to
--workdir.
--workdir=DIR
Use DIR to hold intermediate files created while running
tests. DIR must not already exist.
--run=LIST
This option runs only the tests in LIST. See the seven tests
listed previously. For example, --run=123 will run only
tests 1, 2, and 3.
--skip=LIST
This option skips the tests in LIST. See the seven tests listed
previously. For example, --skip=2457 will skip tests 2, 4, 5,
and 7.
-d, --debug
This option turns on the -x and -v flags in bash(1).
In most cases of failure, the script suggests recommended actions. Please see
the ipath_checkout man page for more information and updates.
Also refer to the Troubleshooting appendix in the QLogic Host Channel Adapter
and QLogic OFED Software Users Guide.
7-4
IB0056101-00 H
A
Installation
Troubleshooting
The following sections contain information about issues that may occur during
installation. Some of this material is repeated in the Troubleshooting appendix of
the QLogic Host Channel Adapter and QLogic OFED Software Users Guide.
Many programs and files are available that gather information about the cluster,
and can be helpful for debugging. See the appendix Useful Programs and Files, in
the QLogic Host Channel Adapter and QLogic OFED Software Users Guide.
Hardware Issues
Some of the hardware issues that may occur during installation are described in
the following sections. Use the LEDs, as described in “LED Link and Data
Indicators” on page 7-1, to help diagnose problems.
Node Spontaneously Reboots
If a node repeatedly and spontaneously reboots when attempting to load the
InfiniPath driver, it may be because the QLogic adapter is not installed correctly in
the HTX or PCI Express slot.
Some HTX Motherboards May Need Two or More CPUs in Use
Some HTX motherboards may require that two or more CPUs be in use for the
QLogic adapter to be recognized. This is most evident in four-socket
motherboards.
IB0056101-00 H
A-1
S
A–Installation Troubleshooting
BIOS Settings
BIOS Settings
This section covers issues related to BIOS settings. You can check and adjust
BIOS settings using the BIOS Setup utility. For specific instructions, follow the
hardware documentation that came with your system.
Enable Advanced Configuration and Power Interface (ACPI)
This setting must be enabled. If ACPI is disabled, it may cause initialization
problems, as described in the Troubleshooting section of the QLogic Host
Channel Adapter and QLogic OFED Software Users Guide.
Issue with Supermicro® H8DCE-HTe and the QHT7040
The QLogic adapter may not be recognized at startup when using the Supermicro
H8DCE-HT-e and the QHT7040 adapter. To fix this problem, set the operating
system selector option in the BIOS for Linux. The option will look like:
OS Installation [Linux]
Software Installation Issues
Some problems can be found by running ipath_checkout. Run
ipath_checkout before contacting technical support.
Missing Kernel RPM Errors
Install the kernel-source, kernel-devel, and, if using an older release,
kernel-smp-devel RPMs for your distribution before installing the InfiniPath
RPMs, as there are dependencies. Table 5-3 on page 5-4 lists all the required
packages.
Use the uname -a command to find out which kernel is currently running, to
make sure that you install the version with which it matches.
If these RPMs have not been installed, you will see error messages like this when
installing InfiniPath:
Building and installing InfiniPath modules for 2.6.16_sles10
2.6.16.21-0.8-debug kernel
*** ERROR: /lib/modules/2.6.16.21-0.8-debug/build/.config is
missing.
***
Is the kernel-source rpm for 2.6.16.21-0.8-debug
installed?
================
================
A-2
IB0056101-00 H
A
A–Installation Troubleshooting
Software Installation Issues
Building and installing InfiniPath modules for 2.6.9_U4
2.6.9-42.ELsmp kernel
*** ERROR: /lib/modules/2.6.9-42.ELsmp/build/.config is missing.
***
Is the kernel-smp-devel rpm for 2.6.9-42.ELsmp
installed?
================
.
.
.
Install the correct RPMs by using the yum or yast commands, for example:
# yum install kernel-devel
NOTE:
Check your distribution’s documentation for more information on installing
these RPMs, and for usage of yum or yast.
Next, the kernel-ib package must be re-installed, with the --replacepkgs
option included. Then the infinipath service can be restarted. To do so, type
the following (as a root user):
# rpm -U --replacepkgs kernel-ib*
# /etc/init.d/openibd restart
Resolving Conflicts
Occasionally, conflicts may arise when trying to install "on top of" an existing set of
files that may come from a different set of RPMs. For example, if you install the
QLogic MPI RPMs after having previously installed Local Area Multicomputer
(LAM)/MPI, there will be conflicts, since both installations have versions of some
of the same programs and documentation. You would see an error message
similar to the following:
# rpm -Uvh Documentation/*rpm InfiniPath/*rpm
InfiniPath-Devel/*rpm InfiniPath-MPI/*rpm OpenFabrics/*rpm
OpenFabrics-Devel/*rpm OpenSM/*rpm
Preparing...
########################################### [100%]
file /usr/share/man/man3/MPIO_Request_c2f.3.gz from install of
mpi-doc-4321.776_rhel4_psc conflicts with file from package
lam-7.1.2-8.fc6
Use the following command to remove previously installed conflicting packages.
This command will remove all the available LAM packages:
# rpm -e --allmatches lam lam-devel lam-libs
IB0056101-00 H
A-3
A–Installation Troubleshooting
Software Installation Issues
S
After the packages have been removed, continue with the InfiniPath installation.
You can also use the --prefix option with the rpm command to relocate the
install directory of any packages that you need to move. See “Using rpm to Install
InfiniPath and OpenFabrics” on page 5-15 for more information.
openmpi_gcc Fails to Install Because of Dependency on
gfortran (RHEL 4)
On RHEL 4 distributions, libgfortran must be installed before installing the
QLogic openmpi_gcc* RPM; otherwise, the installation will fail. The
libgfortran* RPM is available as part of the RHEL 4 distribution.
mpirun Installation Requires 32-bit Support
On a 64-bit system, 32-bit glibc must be installed before installing the
mpi-frontend-* RPM. mpirun, which is part of the mpi-frontend-* RPM,
and requires 32-bit support.
If 32-bit glibc is not installed on a 64-bit system, an error like this displays when
installing mpi-frontend:
# rpm -Uv ~/tmp/mpi-frontend-2.3-14729.802_rhel4_qlc.i386.rpm
error: Failed dependencies:
/lib/libc.so.6 is needed by mpi-frontend-2.3
-14729.802_rhel4_qlc.i386
In older distributions, such as RHEL4, the 32-bit glibc is contained in the
libgcc RPM. The RPM name will be similar to this:
libgcc-<version>.EL4.i386.rpm
In newer distributions, glibc is an RPM name. The 32-bit glibc is named
similarly to:
glibc-<version>.i686.rpm OR
glibc-<version>.i386.rpm
Check your distribution for the exact RPM name.
Lockable Memory Error on Initial Installation of InfiniPath
During the first installation of InfiniPath software, /etc/initscript is created
or modified to increase the amount of lockable memory (up to 128 MB) for normal
users. This change will not take effect until the system is rebooted, and jobs may
fail with error messages about locking memory or failing mmap. This error is
described in the QLogic MPI Troubleshooting section “Lock Enough Memory on
Nodes When Using a Batch Queuing System” in the QLogic Host Channel
Adapter and QLogic OFED Software Users Guide.
This is not an issue when upgrading to a newer version of the InfiniPath software.
A-4
IB0056101-00 H
A
A–Installation Troubleshooting
Configuration Issues
Configuration Issues
ibsrpdm Command Hangs when Two Adapters are Installed
but only Unit 1 is Connected to the Switch
If multiple adapters (unit 0 and unit 1) are installed, and only unit 1 is connected to
the switch, the ibsrpdm command (to set up an SRP target) can hang. If unit 0 is
connected and unit 1 is disconnected, the problem does not occur.
When only unit 1 is connected to the switch, use the -d option with the ibsrpdm
command. Then, using the output from the ibsrpdm command, echo the new target
information into /sys/class/infiniband_srp/srp-ipath1-1/add_target.
For example:
# ibsrpdm -d /dev/infiniband/umad1 -c
# echo \
id_ext=21000001ff040bf6,ioc_guid=21000001ff040bf6,dgid=fe800000000
0000021000001ff040bf6,pkey=ffff,service_id=f60b04ff01000021 >
/sys/class/infiniband_srp/srp-ipath1-1/add_target
Outdated ipath_ether Configuration Setup Generates Error
Ethernet emulation (ipath_ether) has been removed in this release, and, as a
result, an error may be seen if the user still has an alias set previously by
modprobe.conf (for example, alias eth2 ipath_ether).
When ifconfig or ifup is run, the error looks similar to the following (assuming
ipath_ether was used for eth2):
eth2: error fetching interface information: Device not found
To prevent the error message, remove the following files (assuming
ipath_ether was used for eth2):
/etc/sysconfig/network-scripts/ifcfg-eth2 (for RHEL)
/etc/sysconfig/network/ifcfg-eth-eth2 (for SLES)
QLogic recommends using the IP over InfiniBand protocol (IPoIB-CM), included in
the standard OpenFabrics software releases, as a replacement for
ipath_ether.
IB0056101-00 H
A-5
A–Installation Troubleshooting
Configuration Issues
S
Notes
A-6
IB0056101-00 H
B
Write Combining
Introduction
Write combining improves write bandwidth to the QLogic chip by writing multiple
words in a single bus transaction (typically 64 bytes). Write combining applies only
to x86_64 systems.
The x86 Page Attribute Table (PAT) mechanism that allocates Write Combining
(WC) mappings for the PIO buffers has been added and is now the default.
If PAT is unavailable or PAT initialization fails, the code will generate a message in
the log and fall back to the Memory Type Range Registers (MTRR) mechanism.
If write combining is not working properly, lower than expected bandwidth may
occur.
The following sections provide instructions for checking write combining and for
using PAT and MTRR.
Verify Write Combining is Working
To see if write combining is working correctly and to check the bandwidth, run the
following command:
$ ipath_pkt_test -B
With write combining enabled, the QLE7140 and QLE7240 report in the range
of 1150–1500 MBps. The QLE7280 reports in the range of 1950–3000 MBps. The
QHT7040/7140 adapters report in the range of 2300–2650 MBps.
You can also use ipath_checkout (use option 5) to check bandwidth.
Although the PAT mechanism should work correctly by default, increased latency
and low bandwidth may indicate a problem. If so, the interconnect operates, but in
a degraded performance mode, with latency increasing to several microseconds,
and bandwidth decreasing to as little as 200 MBps.
Upon driver startup, you may see these errors:
ib_ipath 0000:04:01.0: infinipath0: Performance problem: bandwidth
to PIO buffers is only 273 MiB/sec
.
IB0056101-00 H
B-1
S
B–Write Combining
PAT and Write Combining
.
.
If you do not see any of these messages on your console, but suspect this
problem, check the /var/log/messages file. Some systems suppress driver
load messages but still output them to the log file.
Methods for enabling and disabling the two write combining mechanisms are
described in the following sections. There are no conflicts between the two
methods.
PAT and Write Combining
PAT is the default mechanism for allocating WC mappings for the PIO buffers. It is
set as a parameter in /etc/modprobe.conf (on Red Hat systems) or
/etc/modprobe.conf.local (on SLES systems). The default is:
option ib_ipath wc_pat=1
If PAT is unavailable or PAT initialization fails, the code generates a message in
the log and falls back to the MTRR mechanism. To use MTRR, disable PAT by
setting this module parameter to 0 (as a root user):
option ib_ipath wc_pat=0
Then, revert to using the MTRR-only behavior by following one of the two
suggestions in “MTRR Mapping and Write Combining” on page B-2.
The driver will need to be restarted after the changes have been made.
NOTE:
There is no WC entry in /proc/mtrr when using PAT.
MTRR Mapping and Write Combining
The following sections describe two methods for fixing MTRR issues.
See the Troubleshooting section of the QLogic Host Channel Adapter and QLogic
OFED Software Users Guide for more details on a related performance issue.
Edit BIOS Settings to Fix MTRR Issues
You can edit the BIOS setting for MTRR mapping. The BIOS setting looks similar
to:
MTRR Mapping
B-2
[Discrete]
IB0056101-00 H
A
B–Write Combining
MTRR Mapping and Write Combining
For systems with very large amounts of memory (32GB or more), it may also be
necessary to adjust the BIOS setting for the PCI hole granularity to 2GB. This
setting allows the memory to be mapped with fewer MTRRs, so that there will be
one or more unused MTRRs for the InfiniPath driver.
Some BIOS’ do not have the MTRR mapping option. It may have a different
name, depending on the chipset, vendor, BIOS, or other factors. For example, it is
sometimes referred to as 32 bit memory hole. This setting must be enabled.
If there is no setting for MTRR mapping or 32 bit memory hole, and you have
problems with degraded performance, contact your system or motherboard
vendor and ask how to enable write combining.
Use the ipath_mtrr Script to Fix MTRR Issues
QLogic also provides a script, ipath_mtrr, which sets the MTRR registers,
enabling maximum performance from the InfiniPath driver. This Python script is
available as a part of the InfiniPath software download, and is contained in the
infinipath* RPM. It is installed in /bin.
To diagnose the machine, run it with no arguments (as a root user):
# ipath_mtrr
The test results will list any problems, if they exist, and provide suggestions on
what to do.
To fix the MTRR registers, use:
# ipath_mtrr -w
Restart the driver after fixing the registers.
This script needs to be run after each system reboot. It can be set to run
automatically upon restart by adding this line in /etc/sysconfig/infinipath:
IPATH_MTRR_ACTIVE=1
See the ipath_mtrr(8) man page for more information on other options.
IB0056101-00 H
B-3
B–Write Combining
MTRR Mapping and Write Combining
S
Notes
B-4
IB0056101-00 H
C
Configuration Files
Table C-1 contains descriptions of the configuration and configuration template
files used by the InfiniPath and OpenFabrics software.
Table C-1. Configuration Files
Configuration File Name
Description
/etc/infiniband/qlgc_vnic.cfg
VirtualNIC configuration file. Create this file
after running ib_qlgc_vnic_query to
get the information you need. This file was
named /etc/infiniband/qlogic_vnic.cfg or
/etc/sysconfig/ics_inic.cfg in
previous releases. See the sample file
qlgc_vnic.cfg.sample (described
below) to see how it should be set up.
/etc/modprobe.conf
Specifies options for modules when added
or removed by the modprobe command.
Also used for creating aliases. The PAT
WC option is set here.
For Red Hat systems.
/etc/modprobe.conf.local
Specifies options for modules when added
or removed by the modprobe command.
Also used for creating aliases. PAT
write-combing option is set here.
For SLES systems.
IB0056101-00 H
/etc/infiniband/openib.conf
The primary configuration file for InfiniPath, OFED modules, and other modules
and associated daemons. Automatically
loads additional modules or changes IPoIB
transport type.
/etc/sysconfig/infinipath
Contains settings, including the one that
sets the ipath_mtrr script to run on
reboot.
C-1
S
C–Configuration Files
Table C-1. Configuration Files (Continued)
Configuration File Name
/etc/sysconfig/network/ifcfg<NAME>
Description
Network configuration file for network interfaces
When used for VNIC configuration,
<NAME> is in the form eiocX, where X is
the device number. There will be one
interface configuration file for each interface defined in /etc/infiniband/qlgc_vnic.cfg.
For SLES systems.
/etc/sysconfig/network-scripts/ifcfg-<NAME>
Network configuration file for network interfaces
When used for VNIC configuration,
<NAME> is in the form eiocX, where X is
the device number. There will be one
interface configuration file for each interface defined in /etc/infiniband/qlgc_vnic.cfg.
For Red Hat systems.
Sample Files
Description
qlgc_vnic.cfg.sample
Sample VNIC config file. It can be found
with the OFED documentation, or in the
qlgc_vnictools subdirectory of the
QLogicIB_Basic download. It is also
installed in /etc/infiniband.
/usr/share/doc/initscripts-*/
sysconfig.txt
File that explains many of the entries in the
configuration files
For Red hat systems
C-2
IB0056101-00 H
D
Package Descriptions
The following sections contain detailed descriptions of the packages for the
InfiniPath and OpenFabrics software. In this release, software may be installed in
several ways. With the QLogicIB-Basic download, which uses the Installer tool,
the package groupings are different than those in the RPM-based downloads.
Package Names with the QLogicIB-Basic
Download
The QLogicIB-Basic download has been packaged differently than the RPM
download. Some, but not all, of the underlying packages are RPMs. The Installer
tool groups the components as follows:
ib_stack
truescale
mvapich_gcc_qlc
mvapich_pgi_qlc
mvapich_pathscale_qlc
mvapich_intel_qlc
openmpi_gcc_qlc
openmpi_pgi_qlc
openmpi_pathscale_qlc
openmpi_intel_qlc
oftools
ib_stack_dev
fastfabric
qlgc_srp
qlgc_vnic
qlgc_fm
ofed_ipoib
ofed_sdp
ofed_udapl
mvapich
mvapich2
openmpi
ofed_mpisrc
ofed_rds
ofed_srp
ofed_srpt
ofed_iser
ofed_isert
ofed_iwarp
opensm
ofed_debug
IB0056101-00 H
D-1
D–Package Descriptions
Different Nodes May Use Different RPMs
S
Once the Installer tool has begun the installation, for some packages, the
underlying RPM names are displayed on the screen.
Different Nodes May Use Different RPMs
In a cluster environment, different nodes may be used for different functions, such
as launching jobs, software development, or running jobs. These nodes are
defined as follows:
„
Front end node. This node launches jobs. It is referred to as the front end
node throughout this document.
„
Compute node. These nodes run jobs.
„
Development or build node. These are the machines on which examples
or benchmarks can be compiled.
Any machine can serve any combination of these three purposes, but a typical
cluster has many compute nodes and just a few (or only one) front end nodes.
The number of nodes used for development will vary.
Although QLogic recommends installing all RPMs on all nodes, not all InfiniPath
software is required on all nodes. See Table D-2, Table D-3, or Table D-4 for
information on installation of software RPMs on specific types of nodes.
InfiniPath RPM Version Numbers and Identifiers
The InfiniPath RPMs that are shipped have the InfiniPath release number, build
identifiers, and distribution contained in the RPM name. The architecture is
designated by x86_64, noarch, or i386, and is dependent upon the distribution.
For example:
infinipath-<release>-<build_identifier>_<distro>_qlc.x86_64.rpm
Note that _qlc is always added after the distribution identifier.
In the InfiniPath tables in this appendix, the release and build identifiers are
contained in xxx. The distribution identifier plus _qlc is contained in yyy. Using
this convention, the previous RPM would be listed as:
infinipath-xxx_yyy.x86_64.rpm
OpenFabrics RPM Names
Non-InfiniPath components have their own version numbering, which can vary
depending on the source of the RPM. For example:
mvapich_gcc-1.1.0-3143.x86_64.rpm
1_1_0 is the 1.1.0 build for mvapich. In the following tables, the version number
is replaced by xxx.
D-2
IB0056101-00 H
A
D–Package Descriptions
InfiniPath and OpenFabrics RPMs
InfiniPath and OpenFabrics RPMs
If you are using the rpm method, QLogic recommends installing all RPMs on all
nodes, with the exception of the *-Static/*, *-Debuginfo/*, and *32bit/*
RPMs.
Some RPMs are optional. Since cluster nodes can be used for different functions,
it is possible to selectively install RPMs. For example, you can install the opensm
package for use on the node that will act as a subnet manager. If you want to
selectively install the RPMs, see the following tables for a comparison of required
and optional packages.
To generate a list of the InfiniPath software package contents on each RPM, type:
$ rpm -qlp rpm_file_name
Documentation RPMs
Table D-1. Documentation RPMs
RPM Name
infinipath-doc-xxx_yyy.noarch.rpm
Front End
Compute
Development
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
InfiniPath man pages
mpi-doc-xxx_yyy.noarch.rpm
Man pages for MPI functions and other
MPI documents
ofed-docs-xxx.x86_64.rpm
OpenFabrics documentation
InfiniPath RPMs
Table D-2. InfiniPath RPMs
RPM Name
infinipath-xxx_yyy.x86_64.rpm
Front End
Compute
Development
Optional
Required
Optional
Optional
Required
Optional
Utilities and InfiniPath configuration files
Contains ipath_checkout and
ipathbug-helpera
kernel-ib-xxx_yyy.x86_64.rpm
InfiniPath drivers and OpenFabrics kernel modules
IB0056101-00 H
D-3
S
D–Package Descriptions
InfiniPath RPMs
Table D-2. InfiniPath RPMs (Continued)
RPM Name
Front End
Compute
Development
infinipath-libs-xxx_yyy.x86_64.rpm
Optional
Required
Optional
infinipath-libs-xxx_yyy.i386.rpm
InfiniPath protocol shared libraries for
32-bit and 64-bit systems
Table Notes
a
If you want to use ipath_checkout and ipathbug-helper, install this RPM wherever you install
mpi-frontend.
Table D-3. InfiniPath-Devel/RPMs
RPM Name
Front End
Compute
Development
infinipath-devel-xxx_yyy.noarch.rpm
Optional
Optional
Optional
Optional
Optional
Required
Development files for InfiniPath
mpi-devel-xxx_yyy.noarch.rpm
Source code for the MPI development
environment, including headers and libs,
MPI examples, and benchmarks. Use to
build the examples or rebuild the benchmarks.
Table D-4. InfiniPath-MPI/RPMs
RPM Name
Front End
Compute
Development
mpi-benchmark-xxx_yyy.x86_64.rpm
Optional
Required
Optional
Required
Required
Optional
Optional
Required
Required
MPI benchmark binaries
mpi-frontend-xxx_yyy.i386.rpm
MPI job launch scripts and binaries,
including mpirun and MPD
mpi-libs-xxx_yyy.i386.rpm
mpi-libs-xxx_yyy.x86_64.rpm
Shared libraries for MPI
D-4
IB0056101-00 H
A
D–Package Descriptions
OpenFabrics RPMs
OpenFabrics RPMs
For ease of installation, QLogic recommends that all of the OpenFabrics RPMs
listed in Table D-5 be installed on all nodes. Version numbers are indicated
by xxx.
Table D-5. OpenFabrics/RPMs
RPM Name
compat-dapl-xxx.x86_64.rpm
uDAPL 1.2.12 support
compat-dapl-utils-xxx.x86_64.rpm
uDAPL 1.2.12 support
dapl-xxx.x86_64.rpm
uDAPL 2.0.15 support
dapl-utils-xxx.x86_64.rpm
uDAPL support
ibsim-xxx.x86_64.rpm
InfiniBand Fabric Simulator
ibutils-xxx.x86_64.rpm
ibutils provides InfiniBand (IB) network and path diagnostics.
ibvexdmtools-xxx.x86_64.rpm
Discover and use QLogic Virtual NIC devices via VNIC protocol over IB
infiniband-diags-xxx.x86_64.rpm
Diagnostic tools
iscsi-initiator-utils-xxx.x86_64.rpma
Server daemon and utility programs for iSCSI. Also iSER support
Comments
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
For Red Hat systems
libibcm-xxx.x86_64.rpm
Along with the OpenFabrics kernel drivers, libibcm provides a userspace IB connection management API.
libibcommon-xxx.x86_64.rpm
Common utility functions for IB diagnostic and management tools
IB0056101-00 H
Optional for
OpenFabrics
Required for
OpenSM
D-5
S
D–Package Descriptions
OpenFabrics RPMs
Table D-5. OpenFabrics/RPMs (Continued)
RPM Name
libibmad-xxx.x86_64.rpm
Low-layer IB functions for use by the IB diagnostic and management
programs. These include management datagrams (MADs), SA, SMP,
and other basic IB functions.
libibumad-xxx.x86_64.rpm
Provides the user MAD library functions that sit on top of the user MAD
modules in the kernel. These functions are used by IB diagnostic and
management tools, including OpenSM.
libibverbs-xxx.x86_64.rpm
Library that allows userspace processes to use InfiniBand Verbs as
described in the InfiniBand Architecture Specification. This library
includes direct hardware access for fast path operations. For this
library to be useful, a device-specific plug-in module must also be
installed.
libibverbs-utils-xxx.x86_64.rpm
Useful libibverbs example programs such as ibv_devinfo, which
displays information about IB devices.
libipathverbs-xxx.x86_64.rpm
Provides device-specific userspace driver for QLogic host channel
adapters
librdmacm-xxx.x86_64.rpm
Support for the new connection manager
librdmacm-utils-xxx.x86_64.rpm
Utilities for the new connection manager
libsdp-xxx.x86_64.rpm
Can be LD_PRELOAD-ed to have a sockets application use IB Sockets Direct Protocol (SDP) instead of TCP, transparently and without
recompiling the application
ofed-scripts-xxx.x86_64.rpm
OpenFabrics scripts
openib-diags-xxx.x86_64.rpm
Useful programs for troubleshooting and checking the state of the
adapter, IB fabric, and its components
D-6
Comments
Required for
OpenSM
Required for
OpenSM
Required for
OpenFabrics
Required for
OpenFabrics
Required for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Required for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
IB0056101-00 H
A
D–Package Descriptions
OpenFabrics RPMs
Table D-5. OpenFabrics/RPMs (Continued)
RPM Name
open-iscsi-xxx.x86_64.rpm a
Transport independent, multi-platform implementation of RFC3720
iSCSI with iSER support
Comments
Optional for
OpenFabrics
For SLES systems
opensm-libs-xxx.x86_64.rpm
Provides the library for OpenSM
perftest-xxx.x86_64.rpm
IB performance tests
qlgc_vnic_daemon-xxx.x86_64.rpm
Used with VNIC ULP service
qlvnictools-xxx.x86_64.rpm
Startup script, sample config file, and utilities
qperf-xxx.x86_64.rpm
IB performance tests
rds-tools-xxx.x86_64.rpm
Supports RDS
scsi-target-utils-xxx.x86_64.rpm
Contains the daemon and tools to setup SCSI (SRP) targets
sdpnetstat-xxx.x86_64.rpm
Provides network statistics for SDP
srptools-xxx.x86_64.rpm
Support for SRP
tgt-xxx.x86_64.rpm
Used for setting up SCSI (SRP) targets
Required for
OpenSM
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Table Notes
There are two versions of the dapl* packages: version 1_2_5 and version 2_0_7. QLogic recommends installing the 1_2_5 version for compatibility with most dapl applications.
a
iscsi-initiator-utils- and open-iscsi- are essentially the same, except that the former
is for Red Hat and the latter is for SLES.
IB0056101-00 H
D-7
S
D–Package Descriptions
OpenFabrics RPMs
The development RPMs in Table D-6 are needed only on the nodes where OFED
programs are compiled.
Table D-6. OpenFabrics-Devel/RPMs
RPM Name
compat-dapl-devel-xxx.x86_64.rpm
Development files for uDAPL support
dapl-devel-xxx.x86_64.rpm
Development files for uDAPL support
libibcm-devel-xxx.x86_64.rpm
Development files for the libibcm library
libibcommon-devel-xxx.x86_64.rpm
Development files for the libibcommon library
libibmad-devel-xxx.x86_64.rpm
Development files for the libibmad library
libibumad-devel-xxx.x86_64.rpm
Development files for the libibumad library
libibverbs-devel-xxx.x86_64.rpm
Libraries and header files for the libibverbs Verbs library
libipathverbs-devel-xxx.x86_64.rpm
Libraries and header files for the libibverbs Verbs library
librdmacm-devel-2.1-xxx.x86_64.rpm
Development files for the new connection manager
libsdp-devel-xxx.x86_64.rpm
Can be LD_PRELOAD-ed to have a sockets application use Sockets
Direct Protocol (SDP) instead of TCP
D-8
Comments
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabric
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
IB0056101-00 H
A
D–Package Descriptions
Other Adapters
The opensm package in Table D-7 should be installed only on the node that will
be used as a subnet manager.
Table D-7. OpenSM/RPM
RPM Name
opensm-xxx.x86_64.rpm
OpenSM provides an implementation of an InfiniBand subnet manager
and administrator. At least one per each InfiniBand subnet is required
to initialize the InfiniBand hardware.
Comments
Required for
OpenSM
Table D-8. OpenSM-Devel/RPM
RPM Name
opensm-devel-xxx.x86_64.rpm
Development files for OpenSM
Comments
Optional for
OpenSM
Other Adapters
The packages in Table D-9 should be installed only if other adapters are used.
Table D-9. Other Host Channel Adapters/RPMs
RPM Name
libcxgb3-xxx.x86_64.rpm
Support for the Chelsio 10GbE host channel adapter
libmlx4-xxx.x86_64.rpm
Userspace driver for Mellanox ConnectX™ InfiniBand host channel
adapters
®
libmthca-xxx.x86_64.rpm
Provides a device-specific userspace driver for Mellanox host channel
adapters for use with the libibverbs library
libnes-xxx.x86_64.rpm
Provides a userspace driver for NetEffect RNICs for use with the
libibverbs library
mstflint-xxx.1x86_64.rpm
Firmware update tool for other host channel adapters
IB0056101-00 H
Comments
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
Optional for
OpenFabrics
D-9
S
D–Package Descriptions
Other MPIs
Table D-9. Other Host Channel Adapters/RPMs (Continued)
RPM Name
tvflash-xxx.x86_64.rpm
Query and update the firmware flash memory for other host channel
adapters
Comments
Optional for
OpenFabrics
The development RPMs in Table D-10 are only needed on the nodes where
programs are compiled.
Table D-10. Other Host Channel Adapters-Devel/RPMs
RPM Name
libcxgb3-devel-xxx.x86_64.rpm
Development files for the Chelsio 10GbE host channel adapter
libmlx4-devel-xxx.x86_64.rpm
Development files for Mellanox ConnectX™ InfiniBand host channel
adapters
®
Comments
Optional for
OpenFabrics
Optional for
OpenFabrics
Other MPIs
The packages in Table D-11 should be installed if other MPI implementations are
required. RPMs that include yyy in the name are supplied by QLogic; others are
from OFED.
Table D-11. OtherMPIs/RPMs
RPM Name
mpi-selector-xxx.x86_64.rpm
Comments
Optional
Tool to select MPI compiled with different compilers
mpitests_mvapich_gcc-xxx.x86_64.rpm
Optional
MVAPICH MPI tests compiled with GNU
mpitests_mvapich2_gcc-xxx.x86_64.rpm
Optional
MVAPICH2 MPI tests compiled with GNU
mpitests_openmpi_gcc-xxx.x86_64.rpm
Optional
Open MPI tests compiled with GNU
mvapich_gcc-xxx.x86_64.rpm
Optional
MVAPICH compiled with GNU
D-10
IB0056101-00 H
A
D–Package Descriptions
Other MPIs
Table D-11. OtherMPIs/RPMs (Continued)
RPM Name
Comments
Optional
mvapich2_gcc-xxx.x86_64.rpm
MVAPICH2 compiled with GNU
Optional
mvapich_gcc_qlc-xxx.yyy.x86_64.rpm
MVAPICH compiled with GNU for PSM support
mvapich_intel_qlc-xxx.yyy.x86_64.rpm
a
Optional
MVAPICH compiled with Intel for PSM support
mvapich_pathscale_qlc-xxx.yyy.x86_64.rpm
Optional
MVAPICH compiled with PathScale for PSM support
Optional
mvapich_pgi_qlc-xxx.yyy.x86_64.rpm
MVAPICH compiled with PGI for PSM support
Optional
openmpi_gcc-xxx.x86_64.rpm
Open MPI compiled with GNU
Optional
openmpi_gcc_qlc-xxx.yyy.x86_64.rpm
Open MPI compiled with GNU for PSM support
openmpi_intel_qlc-xxx.yyy.x86_64.rpm
a
Optional
Open MPI compiled with Intel for PSM support
openmpi_pathscale_qlc-xxx.yyy.x86_64.rpm
Optional
Open MPI compiled with PathScale for PSM support
openmpi_pgi_qlc-xxx.yyy.x86_64.rpm
Optional
Open MPI compiled with PGI for PSM support
qlogic-mpi-register-xxx.yyy.noarch.rpma
Optional
Helps QLogic MPI interoperate with other MPIs through the
mpi-selector utility
Table Notes
Filenames with _qlc after the compiler name denote QLogic-built versions that enable PSM.
The complier versions used are: GNU 4.1, PathScale 3.0, Intel icc 11.0 (Version 11.0,
Build 20081105, Package ID: l_cproc_p_11.0.074), and PGI 7.2-5.
a
IB0056101-00 H
The mpi-devel and infinipath-devel RPMs will be installed when the
qlogic-mpi-register RPM is installed, as there are dependencies.
D-11
D–Package Descriptions
Other MPIs
S
Notes
D-12
IB0056101-00 H
Index
Symbols
/etc/ files C-1, C-2
/usr/share/doc/initscripts-*/
sysconfig.txt file C-2
A
ACPI 4-4, A-2
Adapter
form factors 4-2
model numbers 2-1, 2-3
not recognized A-1
other adapters/rpms D-9
package contents 4-5
QHT7140 installation with HTX riser 4-12
QHT7140 installation without an HTX riser
4-16
QLE7140/7240/7280 installation with PCI
Express riser 4-9
QLE7140/7240/7280 installation without a
PCI Express riser 4-15
supported 1-1
tuning for performance 7-2
other adapters-devel/rpm D-10
B
BIOS
configuring 4-4
settings A-2
settings to fix MTRR issues B-2
IB0056101-00 H
C
-c 7-4
Cables supported 4-3
CLI command line options 5-13
CLI components 5-12
Cluster 1-3
Compiler support 5-3
Compute nodes, installing with Rocks 5-21
Configuration files C-1
--continue 7-4
CPUs, HTX motherboards may require two or
more CPUs A-1
D
-d 7-4
--debug 7-4
Distribution identifiers 5-3
Document conventions 1-4
Documentation for InfiniPath 1-5
Downloading OFED package 5-5
Drivers
configuration and loading information 6-17
InfiniPath and OpenFabrics overview 6-1
IPoIB configuration 6-2
rebuilding kernel-ib on an unsupported
distribution/kernel pair 5-20
rebuilding or reinstalling kernel-ib after a
kernel upgrade 5-20
unloading manually 6-16
Index-1
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
E
***Error:/lib/modules/2.6.16.21-0.
8-debug/build/.config is
missing error message A-2
Error:Failed dependencies error
message A-4
eth2: error fetching interface
information: Device not
found error message A-5
F
file/usr/share/man/man3/MPIO_Reque
st_c2f.3.gz from install of
mpi-doc-2.1-4321.776_rhel4_p
sc conflicts with file from
package lam-7.1.2-8.fc6 error
message A-3
Form factors for adapters 4-2
Frontend node, install on an existing using
Rocks 5-22
Frontend node, installing with Rocks 5-21
H
-h 7-4
Hardware installation overview 3-1
Hardware requirements 4-1
--help 7-4
Host channel adapter, see Adapter
HTX motherboards may required two or more
CPUs A-1
I
ib_ipath
module 6-1
0000:04:01.0:infinipath0:Perform
ance problem: error message B-1
configuration 6-14
IBA6110 4-8
IBA6120 4-7
Index-2
S
IBA7220 4-7
ibsrpdm hangs A-5
InfiniBand Fabric Suite, installing 5-24
InfiniBand, unloading driver/modules manually
6-16
InfiniPath
configuring the driver state 6-15
devel/rpms D-4
documentation 1-5
documentation and InfiniPath rpms D-3
downgrading rpms 5-27
environment 5-3
interconnect overview 1-3
MPI/rpms D-4
OpenFabrics interoperability 1-3
rpms D-3
software, default installed layout 5-24
software, list of 2-4
starting, stopping, or restarting 6-15
supported Linux distributions 5-2
tar file, unpacking 5-15, 5-18
uninstalling 5-26
using rpm to install 5-15
Installer tool, uninstall using 5-26
Installing
hardware overview 3-1
hardware requirements for 4-1
Lustre 5-24
OFED using a Platform OCS kit 5-23
QHT7140 with HTX riser 4-12
QHT7140 without an HTX riser 4-16
QLE7140/7240/7280 with PCI Express riser
4-9
QLE7140/7240/7280 without a PCI Express
riser 4-15
QLogic InfiniBand Fabric Suite 5-24
QLogic MPI in an alternate location 5-16,
5-19
using Rocks for 5-21
software overview 3-2
using CLI 5-12
verifying installation 7-3
Interoperability, InfiniPath OpenFabrics 1-3
IB0056101-00 H
A
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
ipath
checkout 7-3, A-2
checkout options 7-4
ether configuration setup generates error
A-5
mtrr script to fix MTRR issues B-3
IPoIB driver configuration 6-2
K
-k 7-4
--keep 7-4
Kernel, missing kernel rpm errors A-2
kernel-ib driver, rebuild or reinstall after a
kernel upgrade 5-20
kernel-ib driver, rebuilding on an supported
distribution or unsupported
distribution/kernel pair 5-20
L
LEDs, blink patterns 7-1
Linux, supported distributions 5-2
Lockable memory error A-4
Lustre, installing 5-24
M
Model numbers for adapters 2-1, 2-3
MPI
other MPIs/rpms D-10
over uDAPL configuration 6-13
QLogic supplied 5-24
mpirun, installation requires 32-bit support
A-4
mpi-selector 5-16, 5-19
MTRR
editing BIOS settings to fix B-2
mapping and write combining B-2
using ipath_mtrr script to fix issues B-3
MTU size 7-2
MTU, changing the size 6-14
IB0056101-00 H
N
Node repeatedly reboots error A-1
Node types 5-1, D-2
O
OFED
files to download 5-5
installing user-level software with rpm 5-18
installing using a Platform OCS kit 5-23
installing using Rocks 5-21
package requirements 5-4
uninstalling 5-26
using OFED SRP 6-4
OpenFabrics
devel/rpms D-8
components 6-1
configuration 6-1
downgrading rpms 5-27
environment 5-3
interoperability with InfiniPath 1-3
operating system packages 5-4
rpms D-2, D-3, D-5
supported distributions 5-2
using rpm to install 5-15
OpenSM/rpms D-9
OpenSM, configuration and startup 6-3
Optical media converters 4-4
P
Package contents 4-5
PAT B-1
PAT and write combining B-2
PCIe
bus width 7-3
Max Payload size 7-2
Max Read Request size 7-2
Performance tuning 7-2
Platform OCS, uninstalling with 5-26
Platform OCS, using to install OFED 5-23
Index-3
S
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Protocols supported 2-4
Protocols, InfiniBand subnet management 1-3
Q
QHT7040 4-8
QHT7140 4-8
installation with HTX riser 4-12
installation without an HTX riser 4-16
QLE7140 4-7
QLE7140/7240/7280
installation with PCI Express riser 4-9
installation without a PCI Express riser 4-15
QLE7280 4-7
qlgc_vnic.cfg.sample file C-2
QLogic MPI, installing in an alternate location
5-16, 5-19
QLogic OFED, see OFED
QLogicIB-Basic
components D-1
install with the Installer Tool 5-8
installing a previous version 5-27
tar file, unpacking 5-8
R
RD 2-4
Rocks, installing OFED using 5-21
Rocks, uninstalling with 5-26
rpm
Error:/lib/modules/2.6.16.21-0.8
-debug/build/.config is
missing error message A-2
InfiniPath-devel D-4
InfiniPath-MPI D-4
OpenFabric D-5
OpenFabrics and InfiniPath D-3
OpenFabrics rpm D-2
OpenFabrics-devel D-8
OpenSM D-9
version numbers and identifiers D-2
choosing which to install 5-15
different sets on the same system A-3
Index-4
directories, list of 5-17
downgrading 5-27
installing OFED user-level software with
5-18
missing 7-3
missing kernel rpm errors A-2
using to install InfiniPath and OpenFabrics
5-15
other adapters D-9
other adapters-devel D-10
other MPIs D-10
--run=LIST 7-4
S
Safety precautions 4-5
--skip=LIST 7-4
Software
InfiniPath 2-4
InfiniPath default installed layout 5-24
installation overview 3-2
Lustre, installing 5-24
QLogic InfiniBand Fabric Suite, installing
5-24
removing 5-26
SRP 6-4
using QLogic 6-4
using OFED 6-4
Subnet management 1-3
Supermico H8DCE-HTe, problems with
QHT7040 A-2
Support, technical 1-5
Switch
configuration and monitoring 4-17
supported switches 1-3, 4-3
T
tar file, unpacking 5-8, 5-15, 5-18
taskset 7-2
Technical support 1-5
Terminology 1-4
Text User Interface, see TUI
IB0056101-00 H
A
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
Transport services supported 2-4
TUI, installing QLogic-IB Basic with 5-8
U
uDAPL, with MPI configuration 6-13
Uninstalling
InfiniPath 5-26
OFED 5-26
QLogicIB-Basic 5-27
using Rocks or Platform OCS 5-26
V
-v 7-4
--verbose 7-4
VNIC, configuration 6-6
-vv 7-4
--vverbose 7-4
-vvv 7-4
--vvverbose 7-4
W
--workdir=DIR 7-4
Write combining B-1
and MTRR mapping B-2
enabling 7-2
IB0056101-00 H
Index-5
QLogic Host Channel Adapter and QLogic OFED Software Install Guide
QLogic OFED Version 1.4
S
Notes
Index-6
IB0056101-00 H
Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway
Aliso Viejo, CA 92656 949.389.6000
Europe Headquarters QLogic (UK) LTD. Quatro House Lyon Way, Frimley Camberley Surrey, GU16 7ER UK
www.qlogic.com
+44 (0) 1276 804 670
© 2005-2009 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic and the QLogic logo
are registered trademarks of QLogic Corporation. QLA, SANsurfer, InfiniPath, and SilverStorm are trademarks or registered trademarks of QLogic
Corporation. AMD Opteron is a trademark of Advanced Microdevices Inc. BladeCenter and IBM are registered trademarks of International Business
Machines Corporation. DataDirect Networks is a trademark of DataDirect Networks, Inc. EMCORE is a trademark of EMCORE Corporation. HTX
is a trademark of the HyperTransport Technology Consortium. IBM and BladeCenter are registered trademarks of International Business Machines
Corporation. InfiniBand is a registered trademark and service mark of the InfiniBand Trade Association. Intel is a registered trademark of Intel
Corporation. Linux is a registered trademark of Linus Torvalds. LSI Logic and Engenio are trademarks or registered trademarks of LSI Logic
Corporation. Lustre is a registered trademark of Cluster File Systems, Inc. Mellanox is a registered trademark and ConnectX is a trademark of
Mellanox Technologies, Inc. PathScale is a trademark of PathScale LLC. PCI Express and PCIe are registered trademarks of PCI-SIG Corporation.
Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc. DataDirect Networks is a trademark of DataDirect Networks, Inc.
Supermicro is a registered trademark of Super Micro Computer Inc. SUSE is a registered trademark of Novell Inc. Zarlink is a trademark of Zarlink
Semiconductor Inc. HP is a registered trademark of Hewlett-Packard company. OpenFabrics is a registered trademark of OpenFabrics, Inc. All
other brand and product names are trademarks or registered trademarks of their respective owners. Information supplied by QLogic Corporation
is believed to be accurate and reliable. QLogic Corporation assumes no responsibility for any errors in this brochure. QLogic Corporation reserves
the right, without notice, to make changes in product design or specifications.