HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 117

HP XC Soak Testing using qsnet2soaktest, 7 Using the swmlogger to Pass Events to syslog

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

• 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

  • 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
•
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