Quadrics QsNetII Interconnect

• Verbose information is printed because -v is specified.
# /opt/qsnet/bin/qsnet2_level_test level3 -d
/cluster/image/default_root/var/log/diag/quadrics -N
n1r0,n2r0 -r 0 -clean -t 180
Starting Level 3 Test
Testing on nodes: n1r1,n2r1
Warning: timelimit expired
Killed
Test ran on nodes: n1r1,n2r1
Parsing output
level3: n1r1 (NodeId = 4)
route: -R4,5,D,D,D
ERROR: Test incomplete
level3: n2r1 (NodeId = 5)
route: -R5,4,4,D,D,D,D
ERROR: Test incomplete
Parsing complete
The preceding output identifies the physical position of the node on the network
(NodeId=4) and the route that was used to send data (-R4,5,D,D,D).
12.6 HP XC Soak Testing using qsnet2soaktest
The HP XC operating environment provides the qsnet2soaktest soak testing
script that you can use to exercise a system. The command syntax is as follows:
# qsnet2soaktest -t timeout ’benchmarking program and options’
The benchmarking program and options string is parsed by the script as a single
argument. It must consist of the name of a benchmarking program and all required
and optional arguments that are supported by the benchmarking program.
The qsnet2soaktest script runs the qsnetstat utility using the -l option,
which takes a snapshot of system. It then executes the benchmarking command
line, which is run to completion (unless its process is killed by a timeout due to
system problems). On completion, the script takes a second snapshot of the system
and parses its output to report if any delta errors have occurred during the soak test
period. The default benchmarking program is the qsnet2_level_test command
if you do not provide an alternative benchmarking program and options string.
If your cluster has an RMS installation, Quadrics also provides a soak test
script which utilizes the qsnet_dmatest utility, parsing the RMS database on
completion to report any errors.
12.7 Using the swmlogger to Pass Events to syslog
The swmlogger service enables swmserver interconnect management daemons to
log messages about the health of the interconnect to the cluster’s syslog facility.
This service is hosted by the cluster’s control node.
The swmlogger service listens on port 7200 for any messages broadcast by
swmserver daemons. If you specify the -d option, swmlogger runs in debug mode.
Debug mode causes messages to be logged stderr instead of syslog, and includes
more verbose output necessary for debugging swmlogger.
12.7.1 Events Recorded by swmlogger
When communication is been established with a interconnect module, the
swmlogger service might log the following messages:
Maintenance and Diagnostic Procedures 12-15