Troubleshooting guide

mx_stop_mapper

mx_msg_loop -n

mx_counters | grep Bad

where <hostname> is the name of the host on which the test is being run.

Note that after running the test, the mx_mapper process must be restarted on the

host, as follows:

cd <install_path>/sbin/

su root

mx_start_mapper

If you’re using GM-2, the gm_allsize "loopback test" is performed as follows:

1. Reset the host counters

cd <install_path>/bin/

su root

./gm_counters –C

2. On each node, run:

./gm_counters | grep badcrc__invalid

su root

killall gm_mapper

./gm_simpleroute --disable-software-loopback

./gm_allsize --min-size=10 --max-size=20 --count-per-length=10

./gm_counters | grep badcrc__invalid

Note that after running the test, the gm_mapper process must be restarted on the

host.

If you’re using GM-1, the gm_allsize "loopback test" is performed as follows:

1. Reload the GM-1 module on all nodes (resets the host counters to zero)

su root

/etc/init.d/gm start

2. Rerun the GM-1 mapper.

3. On each node, run:

./gm_counters | grep badcrc_cnt

./gm_allsize --min-size=10 --max-size=20 --count-per-length=10

./gm_counters | grep badcrc_cnt