Myrinet received Solaris-Ready certification in July 2001.		   Myrinet GM-2 Software
and Sun HPC ClusterTools Software
for Solaris
GM-2 Software Available
Solaris
Release		 Processor
UltraSPARC II, III UltraSPARC IIIi UltraSPARC IV x86 AMD64
Solaris 8 check mark check mark      
Solaris 9 check mark check mark   check mark  
Solaris 10 check mark check mark check mark check mark check mark

 

To download Myrinet software, you need a login and password.
If you don't already have these, please request them.

GM Source | ClusterTools Binary | ClusterTools Source | Performance

The GM-2 software release is meant principally for use with the PCIX-series Myrinet NICs. Although the GM-2 software also works with PCI64-series Myrinet NICs, it is not yet as well optimized for performance as GM 1.6.4. Upgrading sites with PCI64-based Myrinet NICs to GM-2 is only recommended for those who would like to take advantage of the new features of GM 2.

Note: GM Binary releases for Solaris are no longer available.

For UltraSPARC/Solaris 9 users, Myricom also supports a loadable Myrinet protocol module (Myrinet PM) for the Sun HPC ClusterTools 4.0 and 5.0 software. Myrinet PM is implemented directly over GM which exploits the low latency and high data rates of Myrinet.

For Solaris 10 users, Sun HPC ClusterTools 6 is required, and the Myrinet PM for ClusterTools 6 is not yet available. We recommend using MPICH-GM for MPI jobs.

The Solaris GM-2 software is distributed in source form only, and the Myrinet PM software is distributed both in source and in binary form. This GM-2 distribution will run under Solaris 8 and higher (32-bit and 64-bit kernels) on UltraSPARC processors, Solaris 9 and 10 on x86, and Solaris 10 on AMD64. The Myrinet PM software has been tested with Sun HPC ClusterTools 4.0 and 5.0 software.

How to use the table below: Generally, all hosts on a single Myrinet network must run the same version of GM. If you have multiple types of NICs on your network, you'll need to use the higher GM version, e.g., if you have PCI64 and PCIXD NICs, the preferred GM version is 2.0.x. If there are multiple versions in a box in the table, they are listed in order of usual preference. Additional information about the version choices is below the table.

Recommended-version GM-2 Source Downloads for Solaris
 Listed in Order of Usual Preference
NIC
Operating System/
Processor		 PCIXE
(Two port,
Lanai 2XP)		 PCIXF
(One port,
Lanai 2XP)
and
PCIXD
(Lanai XP)		 PCI64 Series
(Lanai 7 or 9)
Solaris 8, 9, 10
UltraSPARC II, III, IV		 GM-2.1.27a_Solaris GM-2.0.27a_Solaris
or
GM-2.1.27a_Solaris		 GM-2.0.27a_Solaris
or
GM-2.1.27a_Solaris
Solaris 9, 10
UltraSPARC IIIi and x86		 GM-2.1.27a_Solaris GM-2.0.27a_Solaris
or
GM-2.1.27a_Solaris		 GM-2.0.27a_Solaris
or
GM-2.1.27a_Solaris
Solaris 10
AMD64		 GM-2.1.27a_Solaris GM-2.0.27a_Solaris
or
GM-2.1.27a_Solaris		 not qualified on these hosts

Choices: GM-2.0.x and GM-2.1.x are compatible at the API level, but employ different protocols in the network, so for interoperability you should use the same GM version on all hosts in a Myrinet cluster.

Other considerations:

Current cautions and common problems:

Abbreviated Source Installation Instructions

To compile GM on Solaris UltraSPARC, x86, and AMD64 you will need the following tools:

UltraSPARC:

x86:

AMD64:

Please be sure to read the README files for detailed installation instructions and architecture-specific troubleshooting. Unresolved questions could also be answered in the FAQ.

GM installation is performed in four easy steps:

1. Configuring and compiling the GM driver

For performance reasons, there are two source tarballs from which to choose. 

        gunzip -c gm-2.0.27a_Solaris-sparc-streaming-{on,off}.tar.gz | tar xvf -
        cd gm-2.0.27a_Solaris
        ./configure [--disable-sparc-streaming]
        make
        cd binary

If you are building the driver for an UltraSPARC II, III, or IV machine, use the sparc-streaming-on tarball. If you are building the driver for an UltraSPARC IIIi machine, x86 machine, or AMD64 machine, use the sparc-streaming-off source tarball, and add the configure option --disable-sparc-streaming.

2. Loading the GM driver.

Select an installation directory path <GM_install_path>. It is usually best for <GM_install_path> to be the path to an NFS directory available on all machines that are to share this GM installation. The directory must be accessible using <GM_install_path> on all machines that are to share the installation. <GM_install_path> must be an absolute path. That is, it must start with "/". However, <GM_install_path> may contain symbolic links.

To install GM you must first run

        ./GM_INSTALL <GM_install_path>

to install the GM shared components. You may omit <GM_install_path> to install in /opt/gm/.

Next, you must run

        su root
        <GM_install_path>/sbin/gm_install_drivers
	/etc/init.d/gm start

on all of the machines in your cluster.

Details of these installation scripts can be found in the README-solaris. When the GM module is loaded, a mapper daemon called gm_mapper is started for each Myrinet NIC contained in the machine. The PIDs of the running gm_mappers are stored in /var/run/gm_mapper/pid.<board_id>.

Important notes:

If you wish for the driver to auto-load at boot, you must create appropriate links in the /etc/rcN directories to the /etc/init.d/gm and /etc/init.d/myri scripts. Alternatively, you may start and stop the drivers manually using

        /etc/init.d/gm start
        /etc/init.d/gm stop

or

        /etc/init.d/gm restart

to start, stop, or restart the driver, respectively.

For directions on how to uninstall the GM driver,

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

If you wish to run IP over Myrinet (ethernet emulation), the Solaris command to enable IP over GM is as follows: 

   /sbin/ifconfig myri0 plumb
   /sbin/ifconfig myri0 <ipaddr> up
where you must replace myri0 with the appropriate name (myri1, myri2, etc.) if you have more than one Myrinet NIC per host.

4. Testing the GM Installation.

Once the GM software has been properly installed on all of the hosts in your cluster, you are ready to validate your Myrinet installation by performing the following sequence of tests.

Each of these steps is detailed in the Troubleshooting section of the FAQ.

The test scripts (gm_board_info, gm_debug, gm_allsize, gm_stress) are available in <install_path>/bin in your GM installation. A README describing each of these tests can be found in <install_path>/bin/README.

Congratulations! You have successfully installed GM.

Refer to the Software and Documentation Page for details of GM-based software (MPICH-GM, VI-GM, PVM-GM, Sockets-GM). Currently only MPICH-GM, PVM-GM, and Sockets-GM can be used with GM-2. All other middleware requires GM-1. If you encountered difficulties during any phase of this installation process, we recommend that you first consult the README-solaris and FAQ, and if you still have unresolved questions, please feel free to contact technical support at help@myri.com.


Last updated: 21 September 2006