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
D–Troubleshooting
QLogic MPI Troubleshooting
D-14 IB6054601-00 H
S
Resolving Hostname with Multi-Homed Head Node
By default, mpirun assumes that ranks can independently resolve the hostname
obtained on the head node with gethostname. However, the hostname of a
multi-homed head node may not resolve on the compute nodes. To address this
problem, the following new option has been added to mpirun:
-listen-addr <hostname|IPv4>
This address will be forwarded to the ranks. To change the default, put this option
in the global mpirun.defaults file or in a user-local file.
If the address on the frontend cannot be resolved, then a warning is sent to the
console and to syslog. If you use the following command line, you may see
messages similar to this:
% mpirun-ipath-ssh -np 2 -listen-addr foo -m ~/tmp/hostfile-idev
osu_bcast
MPIRUN.<nodename>: Warning: Couldn’t resolve listen address ’foo’
on head node
(Unknown host), using it anyway...
MPIRUN.<nodename>: No node programs have connected within 60
seconds.
This message occurs if none of the ranks can connect back to the head node.
The following message may appear if some ranks cannot connect back:
MPIRUN.<nodename>: Not all node programs have connected within
60 seconds.
MPIRUN.<nodename>: No connection received from 1 node process on
node <nodename>
Cross-Compilation Issues
The GNU 4.x environment is supported in the PathScale Compiler Suite 3.x
release.
However, the 2.x QLogic PathScale compilers are not currently supported on
SLES 10 systems that use the GNU 4.x compilers and compiler environment
(header files and libraries).
QLogic recommends installing the PathScale 3.1 release.