HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 113

Using the qsnet2_dmatest Utility

Get HP Cluster Platform Interconnects v2010 PDF manuals and user guides View all HP Cluster Platform Interconnects v2010 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

-h Displays the help (command usage) information. -x Exits automatically on encountering the first error. The default behavior is to ignore the error and continue. -s Exits with a status of 0 if all tests are passed, otherwise a status of 1. -D device_id Specifies a device identifier (rail) as 0, 1, or 0 1 (both). The default is 0 1 (both). Note HP Cluster Platform supports only single-rail configurations The output from the qselantest utility is extensive and a sample is provided in Appendix D. 12.3.2 Running the qselantestp Utility Under HP XC The HP XC operating environment supports a wrapper script named qselantestp (the p stands for parallel). The script automatically spawns a qselantest process on all the nodes, directing the output from each node into a data file in a /var/log/diag/quadrics/qselantestp, a global directory. When the test is complete, the wrapper script automatically parses the data file and reports which nodes have failed the test, if any, Only data from failed nodes is displayed when you run the qselantestp script from the administrative node. The qselantestp script command-line options are as follows: # qselantestp [-N nodelist][-d logdirectory] / [-t timeout][-clean] The default is to select all nodes, with a log directory of /var/log/diag/quadrics/qselantestp. The script times out after 3 minutes and kills any nodes which have not completed. These nodes are reported as failed to complete in the command output. 12.4 Using the qsnet2_dmatest Utility Use the qsnet2_dmatest command to send data on a link through a statically designated route. By setting the route you can sensitize and test individual links in the network. The test reports bandwidth for small and large data transfers as it ramps up, enabling you to verify performance. The qsnet2_dmatest command reports errors were detected during the test. Note Clusters might be configured with full bandwidth or reduced bandwidth, as defined in the configuration rules and cabling tables for your cluster. If your cluster has a reduced bandwidth you must also apply the qsnet2_dmatest node ID constraints defined in Section 12.11. Maintenance and Diagnostic Procedures 12-11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
-h
Displays the help (command usage) information.
-x
Exits automatically on encountering the first error. The default behavior
is to ignore the error and continue.
-s
Exits with a status of 0 if all tests are passed, otherwise a status of 1.
-D
device_id
Specifies a device identifier (rail) as
0
,
1
, or
01
(both). The default is
0
1
(both).
_______________________
Note
_______________________
HP Cluster Platform supports only single-rail configurations
The output from the
qselantest
utility is extensive and a sample is provided in
Appendix D.
12.3.2 Running the qselantestp Utility Under HP XC
The HP XC operating environment supports a wrapper script named
qselantestp
(the
p
stands for parallel). The script automatically spawns a
qselantest
process on all the nodes, directing the output from each node into a data file in a
/var/log/diag/quadrics/qselantestp
, a global directory.
When the test is complete, the wrapper script automatically parses the data file
and reports which nodes have failed the test, if any, Only data from failed nodes is
displayed when you run the
qselantestp
script from the administrative node.
The
qselantestp
script command-line options are as follows:
#
qselantestp [-N
nodelist
][-d
logdirectory
]
/
[-t
timeout
][-clean]
The default is to select all nodes, with a log directory of
/var/log/diag/quadrics/qselantestp
. The script times out after
3 minutes and kills any nodes which have not completed. These nodes are reported
as
failed to complete
in the command output.
12.4 Using the qsnet2_dmatest Utility
Use the
qsnet2_dmatest
command to send data on a link through a statically
designated route. By setting the route you can sensitize and test individual links in
the network. The test reports bandwidth for small and large data transfers as it
ramps up, enabling you to verify performance. The
qsnet2_dmatest
command
reports errors were detected during the test.
_________________________
Note
_________________________
Clusters might be configured with full bandwidth or reduced bandwidth,
as defined in the configuration rules and cabling tables for your cluster.
If your cluster has a reduced bandwidth you must also apply the
qsnet2_dmatest
node ID constraints defined in Section 12.11.
Maintenance and Diagnostic Procedures
12-11