PM/Myrinet Test Procedure

If your Myrinet network is Myrinet 2000 with serial or fiber link interface (M3S-PCI64B and M3F-PCI64B), please use myrinet2k network type and lanaiM2k.mcp firmware. In order to change network type in rpmtest and rcstest, you must modify your scorehosts.db on your server. Please refer to SCore System Installation on Server section.

1. Loopback test
   Issue the following commands:

   $ cd /opt/score/sbin
   $ ./rpminit comp0 myrinet
   $ ./rpmtest comp0 myrinet -dest 0 -ping
   	Success: Two numbers similar to "8     1.2269e-05" are printed
                    The first number is the data size (in bytes)
                    The second number is the latency (in seconds)
   	Failure: Error and dump messages are printed
   

   If this test fails, read the Troubleshooting section.

2. Point-to-Point test (Message)
   Make sure that the PM kernel driver and configuration file are also installed or accessible on all hosts. Issue the following commands:

   $ cd /opt/score/sbin
   $ ./rpmtest comp1 myrinet -reply
   

   Issue the following commands in another window on the server host:

   $ cd /opt/score/sbin
   $ ./rpmtest comp0 myrinet -dest 1 -ping
   	Results should be the same as the loopback test
   

   When the test finishes, do not forget to kill the pmtest process on the server host because the process is in an infinite loop.
   If this test fails, read the Troubleshooting section.

3. Point-to-Point test (Zero Copy)
   Issue the following commands:

   $ cd /opt/score/sbin
   $ ./rpmtest comp1 myrinet -vreply
   

   Issue the following commands in another window on the server host:

   $ cd /opt/score/sbin
   $ ./rpmtest comp0 myrinet -dest 1 -vwrite
   	Success: Two numbers similar to "8     913452" are printed
                    The first number is the data size (in bytes)
                    The second number is the bandwidth (in bytes/sec)
   	Failure: Error and dump messages are printed
   

   When the test finishes, do not forget to kill the pmtest process on the server host because the process is in an infinite loop.
   If this test fails, read the Troubleshooting section.

4. Total test
   This is the stress test. All hosts randomly send burst messages to other hosts. This test also verifies that the rsh command can be issued to all hosts. Issue the following commands:

   $ cd /opt/score/sbin
   $ ./rcstest comp0 myrinet -v
     starting master 0 : pe=4
     starting slave: 1 3 2
     testing*.*.*.*.*. ...
   	Success: '.'s and '*'s are printed.
   	Failure: Error messages are printed.
   
   

   To stop this test, press Ctrl-C or another interrupt command.
   If this test fails, read the Troubleshooting section.

Troubleshooting

Pminit causes an error.

• Myrinet cables are NOT connected.
• The Myrinet device driver is not installed.
• /dev/pmmyri/number has not been created by the mkpmmyridev.sh command.
• The permissions of /dev/pmmyri/number are not correct.
• There is no mcp file or no configuration file.
• The contents of the configuration file are not correct.
• No Myrinet card is installed.
• The Myrinet card is not tightly plugged in.
• The PCI bus clock on the motherboard is higher than 33MHz (ex: 37.5 MHz).
• The Myrinet card is damaged.

Loop back test fails.

• The Myrinet card is not connected to the Myrinet switch correctly.
• Some other processes using Myrinet exist on the host.
• The Myrinet card is not tightly plugged in.
• The Myrinet cable is damaged.
• The Myrinet card is not operating normally.
• The Myrinet switch is not operating normally.

Point-to-point test fails.

• The specification in the configuration file and the actual connection differ.
• Some other processes using Myrinet exist on some hosts.
• The trimer is set to 2000 on the Myrinet-2000 card. it should be set to 1280 because no Myrinet-2000 switches are available at that time (2000/10/25).
• The Myrinet card is not connected to the Myrinet switch correctly.
• The Myrinet cable is damaged.
• The Myrinet card is not operating normally.
• The Myrinet switch is not operating normally.
• Zero copy transfer is not supported on the machine.

Total test fails.

• The rsh does not work on your shell.
• If you use the bash as the root login shell and execute the cstest program under the root user, make sure that the PWD environment variable has been exported.
• All hosts do not have the same SCore files.
• A remote shell cannot change to the directory specified by the PWD shell environment variable. See the document for cstest for more information.
• The specification in the configuration file and the actual connection differ.
• Some other processes using Myrinet exist on some hosts.
• The trimer should be set to 2000 or 1280 on the Myrinet-2000 card. it should be set to 1280 for old type Myrinet switch, or 2000 for Myrinet-2000 switches.
• The Myrinet cable is damaged.
• The Myrinet card is not operating normally.
• The Myrinet switch is not operating normally.