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-11
A
Configuring and Administering the VNIC Interface
The VirtualNIC (VNIC) Upper Layer Protocol (ULP) works in conjunction with
firmware running on Virtual Input/Output (VIO) hardware such as the SilverStorm
®
Ethernet Virtual I/O Controller (EVIC™) or the InfiniBand/Ethernet Bridge Module
for IBM
®
BladeCenter
®
, providing virtual Ethernet connectivity.
The VNIC driver, along with QLogic EVIC’s two 10 Gigabit ethernet ports, enables
Infiniband clusters to connect to Ethernet networks. This driver also works with the
earlier version of the I/O controller, the VEx.
The QLogic VNIC driver creates virtual Ethernet interfaces and tunnels the
Ethernet data to/from the EVIC over InfiniBand using an InfiniBand reliable
connection.
The virtual Ethernet interface supports any Ethernet protocol. It operates like any
other interface: ping, ssh, scp, netperf, etc.
The VNIC interface must be configured before it can be used. To do so, perform
the following steps:
1. Discover the EVIC/VEx Input/Output Controllers (IOCs) present on the fabric
using the ib_qlgc_vnic_query command. For writing the configuration
file, you will need information about the EVIC/VEx IOCs present on the
fabric, such as their IOCGUID, IOCSTRING, etc. Use the
ib_qlgc_vnic_query tool to get this information.
When ib_qlgc_vnic_query is executed without any options, it displays
detailed information about all the EVIC/VEx IOCs present on the fabric. Run
it as a root user. For example:
# ib_qlgc_vnic_query
HCA No = 0, HCA = mlx4_0, Port = 1, Port GUID = 0x0002c903000010f9,
State = Active
IO Unit Info:
port LID: 0009
port GID: fe8000000000000000066a11de000070
change ID: 0003
max controllers: 0x02