HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 83

Postinstallation Verification Procedure

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

172.20.66.2 172.20.66.3 172.20.66.4 172.20.66.9 172.20.66.10 QR0N01 QR0N02 QR0N03 QR0T00 QR0T00 (There might be additional entries in this file other than those for the interconnect names and addresses). 2. If the file is unpopulated, or requires an update, do the following: a. Backup the file by copying it to a new filename, so that you can restore the original file in the event of a problem. b. Edit the file with a text editor such as vi, adding interconnect names and TCP/IP addresses as appropriate. 9.4 Postinstallation Verification Procedure Use this procedure to verify a cluster after installation, or to perform a full cluster hardware check. It is assumed that you have performed the initial configuration procedures, or verified the configuration, as described in Section 9.3.1 and Section 9.3.2. 1. If you are not logged in to the controller, open a connection to the control processor as described in Section 9.2. The main menu is displayed, as shown in Example 9-1. 2. Select the option titled 9. Self Test. The self test is described in Section 11.4. Examine the output from the test and correct any test failures. If your cluster has more than one interconnect, repeat this step on each interconnect in the hierarchy. 3. Check all the node-to-interconnect link LEDs as follows: a. The control cards and clock generators installed in each interconnect in the hierarchy. b. The ports on each switch card installed in every interconnect. c. The ports on the QM500 PCI cards installed in the nodes. LED locations and their normal operation or error status are described in Chapter 10. 4. Log in to the control node and run the following tests: a. Run the jtest command on each interconnect in the hierarchy as follows: # /opt/qsnet/bin/jtest QR0(N/T)nn Where: • (N/T) specifies N or T to identify node-level or top-level interconnects. • nn specifies an integer representing the interconnect identification number. The interconnect hierarchy is listed in the /etc/hosts file, which is described in Section 9.3.2. Using the jtest diagnostic also verifies that you can log on to every interconnect in the hierarchy from the cluster's administrative node. See Section 11.2 for an explanation of the output from the jtest command b. For each interconnect, display the installed firmware as follows: jtest> info 1 - 5 - | F'ware Id: 41-3101613 | 2 3750 | Postinstallation Configuration and Testing 9-7

  • 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
172.20.66.2
QR0N01
172.20.66.3
QR0N02
172.20.66.4
QR0N03
172.20.66.9
QR0T00
172.20.66.10 QR0T00
(There might be additional entries in this file other than those for the
interconnect names and addresses).
2.
If the file is unpopulated, or requires an update, do the following:
a.
Backup the file by copying it to a new filename, so that you can restore
the original file in the event of a problem.
b.
Edit the file with a text editor such as
vi
, adding interconnect names and
TCP/IP addresses as appropriate.
9.4 Postinstallation Verification Procedure
Use this procedure to verify a cluster after installation, or to perform a full cluster
hardware check. It is assumed that you have performed the initial configuration
procedures, or verified the configuration, as described in Section 9.3.1 and
Section 9.3.2.
1.
If you are not logged in to the controller, open a connection to the control
processor as described in Section 9.2. The main menu is displayed, as shown
in Example 9-1.
2.
Select the option titled
9. Self Test
. The self test is described in
Section 11.4. Examine the output from the test and correct any test failures.
If your cluster has more than one interconnect, repeat this step on each
interconnect in the hierarchy.
3.
Check all the node-to-interconnect link LEDs as follows:
a.
The control cards and clock generators installed in each interconnect in
the hierarchy.
b.
The ports on each switch card installed in every interconnect.
c.
The ports on the QM500 PCI cards installed in the nodes.
LED locations and their normal operation or error status are described in
Chapter 10.
4.
Log in to the control node and run the following tests:
a.
Run the
jtest
command on each interconnect in the hierarchy as follows:
#
/opt/qsnet/bin/jtest QR0
(N/T)nn
Where:
•
(N/T)
specifies
N
or
T
to identify node-level or top-level interconnects.
•
nn
specifies an integer representing the interconnect identification
number.
The interconnect hierarchy is listed in the
/etc/hosts
file, which is
described in Section 9.3.2. Using the
jtest
diagnostic also verifies that
you can log on to every interconnect in the hierarchy from the cluster’s
administrative node. See Section 11.2 for an explanation of the output
from the
jtest
command
b.
For each interconnect, display the installed firmware as follows:
jtest>
info
<display truncated>
1 - 5 - | F’ware Id: 41-3101613 | 2 3750 |
<display truncated>
Postinstallation Configuration and Testing
9-7