HP Integrity Superdome 2 8/16 HP Integrity Superdome 2 Onboard Administrator C - Page 203

Acquitting indictments, as the test completes.

Page 203 highlights

Deconfiguration is the act of disabling a component in the system. This happens when analysis finds that a component has a serious fault. A components deconfiguration status is composed of two parts: • "requested state" - What the user or Analysis Engine would like to have the component set to. • "current state" - How the component is actually configured in the system. IMPORTANT: Deconfiguration requests for components in active nPars can not be acted on until the nPar experiences a power-off/power-on cycle. Acquitting indictments Acquitting refers to clearing the component indictment and deconfiguration statuses, and is done when the part is serviced. Acquittals happen automatically in the following situations: • Component insertion - HR will assume that a component inserted into the system has received any required service. This applies to any components contained within the inserted unit as well. For example, DIMMs and CPU sockets on an inserted blade will be acquitted. Any deconfigurations will be reversed. • AC power cycle or CLI poweron xfabric command - HR will assume that the required service has been accomplished for the entire complex. All FRUs and sub-FRUs will be acquitted and reconfigured. • Cohort acquittal - When analysis of a single fault event results in indictment or suspicion records against multiple components, the records are linked together. If one is acquitted, the acquittal will be passed to the cohort FRUs as well. For example, if a cabled fabric link between the XFM and IOX has failed, the analysis engine will indict the cable connectors physical locations (representing the cable as the most likely component failure). Acquittal of the fabric cable connectors after cable service will acquit all for records. • HR test commands - The test camnet and test clocks commands will acquit all indictments specific to the test to be executed. Resources that fail the test will be re-indicted as the test completes. The test fabric command acquits each type (fabric, CAMNet, Global Clock) of indictment before initiating the test. NOTE: Indictments indicating faults in subcomponents not targeted by the tests will not be acquitted. For example, a blade indictment for CPU fault will not be acquitted by any of these test commands. • Start Link - Attempting to service a cabled link while in use will result in an indictment. The stop link command prevents these indictments and alerts caused by service actions and lights the appropriate LINK health LEDs to help identify the physical cable needing service. The start link command clears the link health LEDs, acquits, and attempts link retraining. • Manual Acquittal - The HR UI includes an acquit command that uses the component physical location or resource path as a parameter. Like other acquittals, the acquittal will act on all indictments for that component. • Component resumes normal function. Health Repository viewer 203

  • 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
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217

Deconfiguration is the act of disabling a component in the system. This happens when analysis
finds that a component has a serious fault. A components deconfiguration status is composed of
two parts:
“requested state” – What the user or Analysis Engine would like to have the component set
to.
“current state” – How the component is actually configured in the system.
IMPORTANT:
Deconfiguration requests for components in active nPars can not be acted on until
the nPar experiences a power-off/power-on cycle.
Acquitting indictments
Acquitting refers to clearing the component indictment and deconfiguration statuses, and is done
when the part is serviced. Acquittals happen automatically in the following situations:
Component insertion — HR will assume that a component inserted into the system has received
any required service. This applies to any components contained within the inserted unit as
well. For example, DIMMs and CPU sockets on an inserted blade will be acquitted. Any
deconfigurations will be reversed.
AC power cycle or
CLI poweron xfabric
command — HR will assume that the required
service has been accomplished for the entire complex. All FRUs and sub-FRUs will be acquitted
and reconfigured.
Cohort acquittal — When analysis of a single fault event results in indictment or suspicion
records against multiple components, the records are linked together. If one is acquitted, the
acquittal will be passed to the cohort FRUs as well.
For example, if a cabled fabric link between the XFM and IOX has failed, the analysis engine
will indict the cable connectors physical locations (representing the cable as the most likely
component failure). Acquittal of the fabric cable connectors after cable service will acquit all
for records.
HR test commands — The
test camnet
and
test clocks
commands will acquit all
indictments specific to the test to be executed. Resources that fail the test will be re-indicted
as the test completes. The
test fabric
command acquits each type (fabric, CAMNet,
Global Clock) of indictment before initiating the test.
NOTE:
Indictments indicating faults in subcomponents not targeted by the tests will not be
acquitted. For example, a blade indictment for CPU fault will not be acquitted by any of these
test commands.
Start Link — Attempting to service a cabled link while in use will result in an indictment. The
stop link
command prevents these indictments and alerts caused by service actions and
lights the appropriate LINK health LEDs to help identify the physical cable needing service.
The
start link
command clears the link health LEDs, acquits, and attempts link retraining.
Manual Acquittal – The HR UI includes an acquit command that uses the component physical
location or resource path as a parameter. Like other acquittals, the acquittal will act on all
indictments for that component.
Component resumes normal function.
Health Repository viewer
203