HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 127

Collecting QM500 Manufacturer Data VPD, 13 Running a Network Soak Test, 14 Using the qsdiagadm

Page 127 highlights

address if you replace a control processor card. The TCP/IP address for the new interconnect should remain the same. 12.12 Collecting QM500 Manufacturer Data (VPD) The manufacturing (VPD) data, such as its part number and serial number, for each QM500 PCI card is recorded in a file named vpd on each node. To obtain this data from a node, use the following procedure: 1. Change default to the data directory as follows: # cd /proc/qsnet/elan4/device0 2. Display the file content as follows: # cat vpd PN: QM500b EC: XX SN: K76A7A1BFPW955 FN: A1 MN: 0000 Z0: 686a232b MT: 0104-042-203636 MV: 1.00 MS: 00000000 DT: 00 DV: 00 DS: 00 DG: 00 DD: 00 # Use the following procedure to obtain the VDP data for all QM500 cards in all the nodes 1. Log in to the administrative server 2. Run the following command: # crsh -r all "nodename; cat /proc/qsnet/elan4/device0/vpd" 3. Data is displayed for each node in turn, in the same format shown in the previous example. Each data set is preceded by the node name, such as admin-0 or n3r0. 12.13 Running a Network Soak Test On systems not running HP XC, perform a generic soak test as follows: 1. Run the qsnetstat command using the -l argument, as described in Section 12.2.1. 2. Launch the /opt/qsnet/bin/qsnetsoak exerciser tool to generate heavy data traffic on the network. 3. Repeat the qsnetstat command to obtain the results delta compared to the preceding run, as described in Section 12.2.1. 12.14 Using the qsdiagadm Command Use the qsdiagadm command to create the diagnostics database. This command creates the database entries, sets the interconnect network type, and builds a link Maintenance and Diagnostic Procedures 12-25

  • 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

address if you replace a control processor card. The TCP/IP address for the new
interconnect should remain the same.
12.12 Collecting QM500 Manufacturer Data (VPD)
The manufacturing (VPD) data, such as its part number and serial number, for
each QM500 PCI card is recorded in a file named
vpd
on each node. To obtain this
data from a node, use the following procedure:
1.
Change default to the data directory as follows:
#
cd /proc/qsnet/elan4/device0
2.
Display the file content as follows:
#
cat vpd
PN: QM500b
EC: XX
SN: K76A7A1BFPW955
FN: A1
MN: 0000
Z0: 686a232b
MT: 0104-042-203636
MV: 1.00
MS: 00000000
DT: 00
DV: 00
DS: 00
DG: 00
DD: 00
#
Use the following procedure to obtain the VDP data for all QM500 cards in all
the nodes
1.
Log in to the administrative server
2.
Run the following command:
#
crsh -r all "nodename; cat /proc/qsnet/elan4/device0/vpd”
3.
Data is displayed for each node in turn, in the same format shown in the
previous example. Each data set is preceded by the node name, such as
admin-0
or
n3r0
.
12.13 Running a Network Soak Test
On systems not running HP XC, perform a generic soak test as follows:
1.
Run the
qsnetstat
command using the
-l
argument, as described in
Section 12.2.1.
2.
Launch the
/opt/qsnet/bin/qsnetsoak
exerciser tool to generate heavy
data traffic on the network.
3.
Repeat the
qsnetstat
command to obtain the results delta compared to the
preceding run, as described in Section 12.2.1.
12.14 Using the qsdiagadm Command
Use the
qsdiagadm
command to create the diagnostics database. This command
creates the database entries, sets the interconnect network type, and builds a link
Maintenance and Diagnostic Procedures
12-25