HP XC System Software Release Notes for Version 4.0

• During OVP processing, which is using ib_prodmode_mon:
Testing infiniband_status ...
Searching /etc/hosts for Infiniband switches
Getting readings from IR0N00
No Infiniband switches were detected to be the master. Please verify that the
switches are accessible, configured and their system time is synchronized
with this system.
No errors found
12.3 Myrinet Interconnect
The following release notes are specific to the Myrinet interconnect.
12.3.1 Myrinet Monitoring Line Card Can Become Unresponsive
A Myrinet monitoring line card can become unresponsive for some time after it has been set up
with an IP address with DHCP. This is a problem known to Myricom. For more information, see
the following website:
http://www.myri.com/serve/cache/321.html
If the line card becomes unresponsive, reseat the line card by sliding it out of its chassis slot, then
slide it back in. You can do this while the system is up; doing so does not interfere with Myrinet
traffic.
12.3.2 The clear_counters Command Does Not Work on the 256 Port Switch
The /opt/gm/sbin/clear_counters command does not clear the counters on the Myrinet
256 port switch. The web interface to the Myrinet 256 port switch has changed from the earlier,
smaller switches.
To clear the switch counters, you must open an interactive Web connection to the switch and
use the menu commands to clear the counters. The gm_prodmode_mon script, which uses the
clear_counters command, will not clear the counters periodically, as it does on the smaller
switches.
This problem will be resolved in a future software update from Myricom.
12.4 QsNet
II
Interconnect
The following release notes apply to the QsNet
II
® interconnect.
12.4.1 Possible Conflict with Use of SIGUSR2
The Quadrics QsNet
II
software internally uses SIGUSR2 to manage the interconnect. This can
conflict with any user applications that use SIGUSR2, including for debugger use.
To work around this conflict, set the environment variable LIBELAN4_TRAPSIG for the application
to a different signal number other than the default value 12 that corresponds to SIGUSR2. Doing
this instructs the Quadrics software to use the new signal number, and SIGUSR2 can be once
again used by the application. Signal numbers are defined in the /usr/include/asm/signal.h
file.
12.4.2 The qsnet Database Might Contain Entries to Nonexistent Switch Modules
Depending on the system topology, the qsnet diagnostics database might contain entries to
nonexistent switches.
This issue is manifested as errors reported by the /usr/bin/qsctrl utility similar to the
following:
# qsctrl
qsctrl: failed to initialise module QR0N03: no such module (-7)
40 Interconnects