HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 85

Diagnostic Flowchart

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

12. On systems not running HP XC, use the following procedure: a. Determine whether your system is a full bandwidth or reduced bandwidth configuration. If the cluster has a reduced bandwidth configuration, follow the additional test rules defined in Section 12.11. b. Run the qsnet2_dmatest on the appropriate nodes, depending on the cluster bandwidth. Specify the U1, U2, U3, U4, and U5 level arguments as explained in Section 12.4. Verify that all specified nodes pass on all levels. 13. On systems running HP XC, run the selftest as described in Section 11.4. After the self test is complete, use the neterror command to check the database for errors On systems not running HP XC, perform a generic soak test as described in Section 12.13. 14. Clusters installed with HP XC are configured during the installation process to use the swmlogger to record events in a database. For systems not running HP XC, configure the swmlogger to log events to the syslog utility, as described in Section 12.7. 9.5 Diagnostic Flowchart The flowchart shown in Figure 9-1 shows the sequence of steps for performing diagnostic tests and system verification. Postinstallation Configuration and Testing 9-9

  • 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
12.
On systems not running HP XC, use the following procedure:
a.
Determine whether your system is a full bandwidth or reduced bandwidth
configuration. If the cluster has a reduced bandwidth configuration,
follow the additional test rules defined in Section 12.11.
b.
Run the
qsnet2_dmatest
on the appropriate nodes, depending on the
cluster bandwidth. Specify the U1, U2, U3, U4, and U5 level arguments as
explained in Section 12.4. Verify that all specified nodes pass on all levels.
13.
On systems running HP XC, run the
selftest
as described in Section 11.4.
After the self test is complete, use the
neterror
command to check the
database for errors
On systems not running HP XC, perform a generic soak test as described
in Section 12.13.
14.
Clusters installed with HP XC are configured during the installation process
to use the
swmlogger
to record events in a database. For systems not running
HP XC, configure the
swmlogger
to log events to the
syslog
utility, as
described in Section 12.7.
9.5 Diagnostic Flowchart
The flowchart shown in Figure 9-1 shows the sequence of steps for performing
diagnostic tests and system verification.
Postinstallation Configuration and Testing
9-9