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
4–InfiniPath Cluster Setup and Administration
OpenFabrics Drivers and Services Configuration and Startup
IB6054601-00 H 4-17
A
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