Qlogic InfiniPath, Install Manual

Page: 41 / 74

3 – Software Installation
Downloading and Installing InfiniPath and OpenFabrics Software
IB0056101-00 C 3-7
Q
3.5.2
Installing the Software
The new tarball layout makes it easier to identify the software. The RPMs are now
organized in the following way:
InfiniPath_license, InfiniPath_release_notes, LEGAL (top level)
Documentation/
InfiniPath/
InfiniPath-Devel/
InfiniPath-MPI/
OpenFabrics/
OpenFabrics-Devel/
OpenSM/
OtherHCAs/
A complete list of RPMs is in appendix A .
Before installing, please take note of the following:
■
Make sure that all previously existing OpenFabrics RPMs (including the previous
OpenIB for PathScale Beta 1 and 2 RPMs) are uninstalled.
See section 3.20 for
more information on uninstalling.
■
Installing all the RPMs on all nodes is easiest. However, if you do not plan to run
OpenFabrics programs, you will only need to install the RPMs in the
InfiniPath
and
InfiniPath-MPI
directories. If you plan to run only
OpenFabrics programs, install the RPMs in the
InfiniPath
and
OpenFabrics
directories. If you plan to run both InfiniPath and OpenFabrics,
install all three of these RPMs.
■
You should only install the
OpenSM
RPM if you do not plan to use a switch-based
subnet manager. It should normally be installed on just two nodes. If installed, it
is enabled to be
on by default. This behavior can be modified. See section 3.10
for more information.
■
The kernel modules in this release are installed in this directory:
/lib/modules/‘uname -r‘/updates
This avoids replacing kernel modules which may be provided by your Linux
distribution, so they will be available if the InfiniPath software is removed. In this
release the module
ipath_core.ko
has been renamed to i
b_ipath.ko,
and
conflicts can arise if
ipath_core.ko
is also present. If it is found during
installation of the
infinipath-kernel
RPM,
ipath_core.ko
is renamed to
ipath_core.ko.bak
.
The RPMs need to be available on each node on which they will be used. One way
to do this is to copy the RPMs to a directory on each node that will need them.
Another way is to put the RPMs in a directory accessible (e.g., via NFS) to every