HP XC System Software Administration Guide Version 2.1

example, the test is run on rail 0 with the -clean o
ption to remove data from a previous
test that can corrupt the test results.
# qsnet2_level_test level3 -d \
/hptc_cluster/adm/logs/diag/quadrics \
-N n1,n2 -r 0 -clean -v -t 180
Example 3
The following example displays the output of this diagnostic test, run on three nodes, when
the timeout expires.
# qsnet2_level_test level3 -d \
/hptc_cluster/adm/logs/diag/quadrics/ \
-c -N n1,n2,n3 -t 180
Starting Level 3 Test
Testing on: n1,n2,n3
Warning: timelimit expired
Killed
Test ran on: n1,n2,n3
Parsing output
level3: n1 - (NodeId = 4)
ERROR: Test incomplete
level3: n2 - (NodeId = 3)
ERROR: Test incomplete
level3: n3 - (NodeId = 2)
ERROR: Test incomplete
Parsing complete
Example 4
The following example parses the output files created from a previous run of this command.
This example specifies the log file directory created after unzipping and extracting the
qsnet2_drain_test log file, which is described in the ne xt section .
# qsnet2_level_test level1 -d \
/var/log/diag/quadrics/qsnet2_drain_test/qsnet2_drain_test \
-parse
15.4.2.4 The qsnet2_drain_test Diagnostic Tool
This tool ru n s up to six tests for the Quadrics switches in an HP XC system; these tests are:
•Runstheqsctrl utility to check that the system interconnects a r e running within the
proper enviro nmental parameters for operation.
•Runsqsnet2_level_test at level 1.
•Runsqsnet2_level_test at level 2.
•Runsqsnet2_level_test at level 3.
•Runsqsportmap on federated systems to test the link cable connectivity.
•Runsqsnet2_level_test at level 4 on fed erated systems.
_________________________ Note _________________________
This command must be launched from the head node and it should b e run only
during allocated preventive maintenance t im e fram es because this diagnostic tool
uses the ad apter and th e lin k 100% of the time during the test and, as a result, has
great affect on machine performance.
The com mand fo rmat fo r qsnet2_drain_test ut ility is shown h ere:
15-10 Using Diagnostic Tools