Troubleshooting guide

MX-2G or GM-2 software is required for use with the Myrinet-2000 M3-CLOS-ENCL-*

and M3-SPINE-ENCL-* switches. MX-2G and GM 2.1.x support multi-path, dispersive

routing, a technique that improves the utilization of the network bisection in large

networks.

GM-2 software is required for ethernet-emulation interoperability with M3-SW16-8E

switch line cards. MX-2G does not provide support for the M3-SW16-8E switch line

cards. If you are using GM-2, GM-2.1.x software is required in order to use both ports of

the two-port M3F2-PCIXE NICs.

For the purposes of this document, we shall only discuss a software installation on the

Linux operating system. Similar installation instructions exist for all of the other

supported operating systems and can be found on their respective OS-specific download

page (accessible via

http://www.myri.com/scs/).

V. MX-2G Software Installation

MX-2G installation is performed in three easy steps:

1. Configuring and compiling MX-2G.

2. Installing the MX-2G mcp and driver.

3. Enabling IP over Myrinet (ethernet emulation) (OPTIONAL)

For detailed installation instructions for MX with FMS diagnostic monitoring, refer to the

FMS webpage (http://www.myri.com/scs/fms/#install-mx).

The following installation instructions assume that your cluster is not diskless. If you

have a diskless cluster, please contact help@myri.com for the proper installation

procedure. We currently recommend MX-2G 1.1.6. For full details, please refer to

http://www.myri.com/scs/#downloads. After you have completed these installation steps,

proceed to Section VIII. Testing/Validation (page 27).

1. Configuring and compiling MX-2G.

Download MX-2G

http://www.myri.com/ftp/pub/MX/mx2g_1.1.6.tar.gz

gunzip -c mx2g_1.1.6.tar.gz | tar xvf -

cd mx-1.1.6

./configure

make

By default, we assume that the header and config files of your Linux kernel (required to

compile outside modules and either part of a kernel-headers or kernel-source package

depending on your distribution) are pointed by /lib/modules/`uname -r`/{source,build}.

If your Linux installation is not standard, or you are cross-compiling for a kernel different

from the one of the compile node you must configure with the following option: