Product specifications
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 Feature Overview
- 3 Step-by-Step Cluster Setup and MPI Usage Checklists
- 4 InfiniPath Cluster Setup and Administration
- Introduction
- Installed Layout
- Memory Footprint
- BIOS Settings
- InfiniPath and OpenFabrics Driver Overview
- OpenFabrics Drivers and Services Configuration and Startup
- Other Configuration: Changing the MTU Size
- Managing the InfiniPath Driver
- More Information on Configuring and Loading Drivers
- Performance Settings and Management Tips
- Host Environment Setup for MPI
- Checking Cluster and Software Status
- 5 Using QLogic MPI
- Introduction
- Getting Started with MPI
- QLogic MPI Details
- Use Wrapper Scripts for Compiling and Linking
- Configuring MPI Programs for QLogic MPI
- To Use Another Compiler
- Process Allocation
- mpihosts File Details
- Using mpirun
- Console I/O in MPI Programs
- Environment for Node Programs
- Environment Variables
- Running Multiple Versions of InfiniPath or MPI
- Job Blocking in Case of Temporary InfiniBand Link Failures
- Performance Tuning
- MPD
- QLogic MPI and Hybrid MPI/OpenMP Applications
- Debugging MPI Programs
- QLogic MPI Limitations
- 6 Using Other MPIs
- A mpirun Options Summary
- B Benchmark Programs
- C Integration with a Batch Queuing System
- D Troubleshooting
- Using LEDs to Check the State of the Adapter
- BIOS Settings
- Kernel and Initialization Issues
- OpenFabrics and InfiniPath Issues
- Stop OpenSM Before Stopping/Restarting InfiniPath
- Manual Shutdown or Restart May Hang if NFS in Use
- Load and Configure IPoIB Before Loading SDP
- Set $IBPATH for OpenFabrics Scripts
- ifconfig Does Not Display Hardware Address Properly on RHEL4
- SDP Module Not Loading
- ibsrpdm Command Hangs when Two Host Channel Adapters are Installed but Only Unit 1 is Connected to the Switch
- Outdated ipath_ether Configuration Setup Generates Error
- System Administration Troubleshooting
- Performance Issues
- QLogic MPI Troubleshooting
- Mixed Releases of MPI RPMs
- Missing mpirun Executable
- Resolving Hostname with Multi-Homed Head Node
- Cross-Compilation Issues
- Compiler/Linker Mismatch
- Compiler Cannot Find Include, Module, or Library Files
- Problem with Shell Special Characters and Wrapper Scripts
- Run Time Errors with Different MPI Implementations
- Process Limitation with ssh
- Number of Processes Exceeds ulimit for Number of Open Files
- Using MPI.mod Files
- Extending MPI Modules
- Lock Enough Memory on Nodes When Using a Batch Queuing System
- Error Creating Shared Memory Object
- gdb Gets SIG32 Signal Under mpirun -debug with the PSM Receive Progress Thread Enabled
- General Error Messages
- Error Messages Generated by mpirun
- MPI Stats
- E Write Combining
- F Useful Programs and Files
- G Recommended Reading
- Glossary
- Index

6–Using Other MPIs
Intel MPI
6-10 IB6054601-00 H
S
Running Platform MPI Applications
Here is an example of a simple mpirun command running with four processes,
over PSM:
$ mpirun -np 4 -machinefile mpihosts mpi_app_name
Once installed, Platform MPI uses the PSM transport by default. To specify PSM
explicitly, add -networks infinipath to the above command.
To run Scali MPI over IB Verbs, type:
$ mpirun -np 4 -machinefile mpihosts -networks ib,smp mpi_app_name
This command indicates that ib is used for inter-node communications, and smp
is used for intra-node communications.
To run over TCP (or IPoIB), type:
$ mpirun -np 4 -machinefile mpihosts -networks tcp,smp mpi_app_name
Further Information on Platform MPI
For more information on using Platform MPI, see: http://www.scali.com/
Intel MPI
Intel MPI version 3.1 is the version tested with this release.
Installation
Follow the instructions for download and installation of Intel MPI from the Intel web
site.
Setup
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