HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 112

Running the qselantest 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 112 highlights

• PCI X connectivity. • Interconnect link interface. • PIO latency and bandwidth. • DMA latency and bandwidth. • Data consistency. The diagnostics software provides an initialization script named /etc/init.d/qspost that enables you to run qselantest as a service when a node boots. Configure the script by using the following command: # chkconfig -add qspost This command adds symbolic links in the /etc/rc.d/rc3.d, /etc/rc.d/rc4.d and /etc/rc.d/rc5.d. initialization files. When qspost runs, it logs verbose output to time stamped files in /var/qselantest. Messages are posted to the /var/log/messages system log file, indicating a pass or fail and the error condition. Message details are contained in the verbose log. The qselantest diagnostic tests must pass cleanly on all nodes before the system can be considered to be operating correctly. This test verifies that each QM500 network adapter is seated correctly, is communicating correctly over the PCI bus, and is interfacing correctly with the Interconnect. The qselantest utility provides a thorough test of the node's QM500 PCI card and the link to which the card is connected. This test has a very high impact on node performance because it utilizes all resources of the QM500 PCI card and the link for the duration of the test. It will therefore decrement cluster performance by making the node unavailable for use for the duration of the test. Use the qselantest utility to perform the following checks and tests: • The QM500 PCI card is present in the node. • The clock speed is correct. • The thread processor is functioning. • The SDRAM memory in the QM500 PCI card is functioning. • The QM500 PCI card has a connection to the node's PCI-X bus. • There is a link interface between the QM500 PCI card and the interconnect. • The link DMA latency is within operational parameters. • The link bandwidth is within operational parameters. 12.3.1 Running the qselantest Utility To run the qselantest utility locally, log in to any node and use the following command: # /opt/qsnet/bin/qselantest -D 0 qselantest: testing device(s) 0 qselantest: No Errors Detected To run the qselantest utility on all nodes use the following command: # /cluster/bin/crsh -r all "nodename; /opt/qsnet/bin/qselantest -D 0" qselantest: testing device(s) 0 qselantest: No Errors Detected The following command options are available: 12-10 Maintenance and Diagnostic Procedures

  • 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
•
PCI X connectivity.
•
Interconnect link interface.
•
PIO latency and bandwidth.
•
DMA latency and bandwidth.
•
Data consistency.
The diagnostics software provides an initialization script named
/etc/init.d/qspost
that enables you to run
qselantest
as a service when a
node boots. Configure the script by using the following command:
#
chkconfig -add qspost
This command adds symbolic links in the
/etc/rc.d/rc3.d
,
/etc/rc.d/rc4.d
and
/etc/rc.d/rc5.d.
initialization files. When
qspost
runs, it logs verbose
output to time stamped files in
/var/qselantest
. Messages are posted to the
/var/log/messages
system log file, indicating a pass or fail and the error
condition. Message details are contained in the verbose log.
The
qselantest
diagnostic tests must pass cleanly on all nodes before the system
can be considered to be operating correctly. This test verifies that each QM500
network adapter is seated correctly, is communicating correctly over the PCI bus,
and is interfacing correctly with the Interconnect.
The
qselantest
utility provides a thorough test of the node’s QM500 PCI card
and the link to which the card is connected. This test has a very high impact on
node performance because it utilizes all resources of the QM500 PCI card and the
link for the duration of the test. It will therefore decrement cluster performance by
making the node unavailable for use for the duration of the test.
Use the
qselantest
utility to perform the following checks and tests:
•
The QM500 PCI card is present in the node.
•
The clock speed is correct.
•
The thread processor is functioning.
•
The SDRAM memory in the QM500 PCI card is functioning.
•
The QM500 PCI card has a connection to the node’s PCI-X bus.
•
There is a link interface between the QM500 PCI card and the interconnect.
•
The link DMA latency is within operational parameters.
•
The link bandwidth is within operational parameters.
12.3.1 Running the qselantest Utility
To run the
qselantest
utility locally, log in to any node and use the following
command:
#
/opt/qsnet/bin/qselantest -D 0
qselantest: testing device(s) 0
<display truncated>
qselantest: No Errors Detected
To run the
qselantest
utility on all nodes use the following command:
#
/cluster/bin/crsh -r all "nodename;
/opt/qsnet/bin/qselantest –D 0"
qselantest: testing
device(s) 0
<display truncated>
qselantest: No Errors Detected
The following command options are available:
12-10
Maintenance and Diagnostic Procedures