HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 121

Performing Drain Time Testing, 10 Performing Drain Time Testing under HP XC

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 121 highlights

These errors are filtered out unless you use jtest with the verbose option. 12.9 Performing Drain Time Testing Unlike the production mode testing described in Section 12.7.2 and the log file monitoring described in Section 12.7, drain time testing does have an impact on cluster availability. Users are requested to quit the system so that you can run a series of planned diagnostics, To ensure the stability of the interconnect, HP recommends that you run this series of tests at least once every two weeks for preventative maintenance purposes. You should archive the results of these tests for reference purposes and for verification of instances when the system was known to be operating correctly. The following tests are recommended during drain time. You can run all tests as scheduled jobs on all nodes. You must run the test in the specified sequence: 1. Environmental monitoring with qsnetstat, as described in Section 12.2.1. 2. The qsnetelantest, as described in Section 12.3 . 3. For systems running HP XC, run the qsnet2_level_test at level1, as described in Section 12.5. Note For systems not running HP XC, run the qsnet2_dmatest command on all nodes, as described in Section 12.4. Specify the -Un option argument where n is the number of levels in the cluster, as defined in the cluster's position file. (See Section 12.2.4 for information on the position file). 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 test constraints defined in Section 12.11. This condition applies to both the qsnet2_level_test command under HP XC and the qsnet2_dmatest command for systems not running HP XC. 4. qsportmap, as described in Section 12.16. 5. qsnet2_level_test at level2, as described in Section 12.5. 6. qsnet2_level_test at level3, as described in Section 12.5. 7. qsnet2_level_test at level4, as described in Section 12.5. As an alternative (and if it is supported by your configuration) you can run the qsnetsoaktest with its duration time set to 10 minutes as described in Section 12.6. 12.10 Performing Drain Time Testing under HP XC Clusters running HP XC can run the qsnet2_drain_test script to perform drain testing. This script runs the following tests in sequence: • /usr/bin/qsctrl (to check environmental conditions) • qsnet2_level_test level1 Maintenance and Diagnostic Procedures 12-19

  • 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
These errors are filtered out unless you use
jtest
with the verbose option.
12.9 Performing Drain Time Testing
Unlike the production mode testing described in Section 12.7.2 and the log file
monitoring described in Section 12.7, drain time testing does have an impact
on cluster availability. Users are requested to quit the system so that you can
run a series of planned diagnostics, To ensure the stability of the interconnect,
HP recommends that you run this series of tests at least once every two weeks
for preventative maintenance purposes. You should archive the results of these
tests for reference purposes and for verification of instances when the system
was known to be operating correctly.
The following tests are recommended during drain time. You can run all tests as
scheduled jobs on all nodes. You must run the test in the specified sequence:
1.
Environmental monitoring with
qsnetstat
, as described in Section 12.2.1.
2.
The
qsnetelantest
, as described in Section 12.3 .
3.
For systems running HP XC, run the
qsnet2_level_test
at
level1
, as
described in Section 12.5.
_______________________
Note
_______________________
For systems not running HP XC, run the
qsnet2_dmatest
command on all nodes, as described in Section 12.4. Specify the
-U
n
option argument where
n
is the number of levels in the cluster,
as defined in the cluster’s position file. (See Section 12.2.4 for
information on the position file).
_______________________
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 test constraints defined in Section 12.11. This
condition applies to both the
qsnet2_level_test
command
under HP XC and the
qsnet2_dmatest
command for systems not
running HP XC.
4.
qsportmap
, as described in Section 12.16.
5.
qsnet2_level_test
at
level2
, as described in Section 12.5.
6.
qsnet2_level_test
at
level3
, as described in Section 12.5.
7.
qsnet2_level_test
at
level4
, as described in Section 12.5.
As an alternative (and if it is supported by your configuration) you can run
the
qsnetsoaktest
with its duration time set to 10 minutes as described in
Section 12.6.
12.10 Performing Drain Time Testing under HP XC
Clusters running HP XC can run the
qsnet2_drain_test
script to perform drain
testing. This script runs the following tests in sequence:
•
/usr/bin/qsctrl
(to check environmental conditions)
•
qsnet2_level_test level1
Maintenance and Diagnostic Procedures
12-19