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
A–mpirun Options Summary
Quiescence Options
IB6054601-00 H A-3
A
Quiescence Options
-disable-mpi-progress-check
This option disables the MPI communication progress check without disabling the
ping reply check.
If quiescence or a lack of ping reply is detected, the job and all compute
processes are terminated.
-i, -ping-interval,seconds
This options specifies the seconds to wait between ping packets to mpirun
(if -q > 0).
Default: 60
-q, -quiescence-timeout,seconds
This option specifies the wait time (in seconds) for quiescence (absence of MPI
communication or lack of ping reply) on the nodes. It is useful for detecting
deadlocks. A value of zero disables quiescence detection.
Default: 900
Verbosity Options
-job-info
This option prints brief job startup and shutdown timing information.
-no-syslog
When this option is specified, critical errors are not sent through syslog. By
default, critical errors are sent to the console and through syslog.
-V, -verbose
This option prints diagnostic messages from mpirun itself. The verbose option is
useful in troubleshooting.
Verbosity will also list the IPATH_* and PSM_* environment variable settings that
affect MPI operation.
Startup Options
-I, -open-timeout seconds
This option tries for the number of seconds to open the InfiniPath device. If
seconds is -1 (negative one), the node program waits indefinitely. Use this option
to avoid having all queued jobs in a batch queue fail when a node fails for some
reason, or is taken down for administrative purposes. The -t option is also
normally set to -1.