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

Health Repository viewer, Indictment Records

Page 202 highlights

S: Cause/Action The following alert threshold options are available: Alert thresholds will cause events at the selected threshold and below to be shown 2: Informational 3: Warning 5: Critical 7: Fatal The following event filter options are available: B: Blade P: Partition V: Virtual Partition U: Unfiltered Current alert threshold: Alert threshold 2 Current filter option: Unfiltered Current format option: Extended Keyword MP:VWR (,,+,-,?,H,C,F,I,L,J,D,K,E,R,T,B,P,V,U,/,\,N,2,3,5,7,) > Location: Enclosure, Device Bay, Socket, Core, Thread AL: Alert Level Event# Rep Location Ent nPar: vPar AL Encoded Field Data Field Keyword Timestamp 21 SFW 1,1,0,0,0 255:255 2 43801f4f01e10029 0000000000000000 SET_SECURE_MODE 21 04/24/2012 06:29:23 20 SFW 1,1,0,0,0 255:255 2 4480223a01e10027 0100ff01ffffff94 MEM_DIMM_ENABLE_DONE 20 04/24/2012 06:28:54 19 PDHC 1,2 14:3 2 4480223800e10025 0100ff01ffffff94 DIMM_LOADING_ORDER_DONE 19 04/24/2012 06:28:03 18 OA 1,1 None 2 4480201f00e10023 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_SUCCESS 18 04/24/2012 06:27:51 17 PDHC 1,2 14:3 2 438028d300e10021 0000000000000150 BLADE_DIMM_VOLTAGE 17 04/24/2012 06:27:49 16 OA 1,1 None 2 4480201d00e1001f 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_CONTINUE 16 04/24/2012 06:27:49 15 ILO 1,1 None 2 4b00260300e1001e 010000004f96aa53 OA_REQUESTS_POWER_CHANGE 15 04/24/2012 06:27:47 14 OA 1,1 None 2 4480201a00e1001c 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_WAITING 14 04/24/2012 06:27:47 13 OA 1,1 1 2 448025a900e1001a 0100ff03ffffff94 PARCON_NPAR_RSRC_ACTIVATION_SKIPPED 13 04/24/2012 06:27:45 12 OA 1,1 None 2 44801ff800e10018 0100ff01ffffff94 BLADE_STATUS_DEGRADED 12 04/24/2012 06:26:56 11 ILO 1,1 None 2 4b00260300e10017 010000004f96aa1e OA_REQUESTS_POWER_CHANGE 11 04/24/2012 06:26:54 Health Repository viewer The Health Repository User Interface displays the information from the HR database. The HR database contains current state and history covering both service events and the results of error events analysis. The following information is available in the HR display: • Description of each failure event on the system that results in a service request, even after a component is removed or replaced. • History of component identities installed in the system. Information in the HR database is stored as installation and action records. These records are organized with component physical location as the key. Indictment Records Indictment refers to a record specifying that a component requires service. The component or a subcomponent may or may not be deconfigured as a result. Each indictment record contains the following information: • The time of the error. • The cause of the error. • The subcomponent location of the error (when analysis allows). In cases when the failing component cannot be identified with certainty, analysis indicts the most probable component that will need to be replaced to solve the problem. 202 Using event logs

  • 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

S: Cause/Action
The following alert threshold options are available:
Alert thresholds will cause events at the selected threshold
and below to be shown
2: Informational
3: Warning
5: Critical
7: Fatal
The following event filter options are available:
B: Blade
P: Partition
V: Virtual Partition
U: Unfiltered
Current alert threshold: Alert threshold 2
Current filter option: Unfiltered
Current format option: Extended Keyword
MP:VWR (<cr>,<sp>,+,-,?,H,C,F,I,L,J,D,K,E,R,T,B,P,V,U,/,\,N,2,3,5,7,<Ctrl-b>) >
Location: Enclosure, Device Bay, Socket, Core, Thread
AL: Alert Level
Event#
Rep
Location
nPar:
AL Encoded Field
Data Field
Keyword
Ent
vPar
Timestamp
21
SFW
1,1,0,0,0
255:255
2 43801f4f01e10029 0000000000000000 SET_SECURE_MODE
21
04/24/2012 06:29:23
20
SFW
1,1,0,0,0
255:255
2 4480223a01e10027 0100ff01ffffff94 MEM_DIMM_ENABLE_DONE
20
04/24/2012 06:28:54
19
PDHC
1,2
14:3
2 4480223800e10025 0100ff01ffffff94 DIMM_LOADING_ORDER_DONE
19
04/24/2012 06:28:03
18
OA
1,1
None
2 4480201f00e10023 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_SUCCESS
18
04/24/2012 06:27:51
17
PDHC
1,2
14:3
2 438028d300e10021 0000000000000150 BLADE_DIMM_VOLTAGE
17
04/24/2012 06:27:49
16
OA
1,1
None
2 4480201d00e1001f 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_CONTINUE
16
04/24/2012 06:27:49
15
ILO
1,1
None
2 4b00260300e1001e 010000004f96aa53 OA_REQUESTS_POWER_CHANGE
15
04/24/2012 06:27:47
14
OA
1,1
None
2 4480201a00e1001c 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_WAITING
14
04/24/2012 06:27:47
13
OA
1,1
1
2 448025a900e1001a 0100ff03ffffff94 PARCON_NPAR_RSRC_ACTIVATION_SKIPPED
13
04/24/2012 06:27:45
12
OA
1,1
None
2 44801ff800e10018 0100ff01ffffff94 BLADE_STATUS_DEGRADED
12
04/24/2012 06:26:56
11
ILO
1,1
None
2 4b00260300e10017 010000004f96aa1e OA_REQUESTS_POWER_CHANGE
11
04/24/2012 06:26:54
Health Repository viewer
The Health Repository User Interface displays the information from the HR database. The HR
database contains current state and history covering both service events and the results of error
events analysis.
The following information is available in the HR display:
Description of each failure event on the system that results in a service request, even after a
component is removed or replaced.
History of component identities installed in the system.
Information in the HR database is stored as installation and action records. These records are
organized with component physical location as the key.
Indictment Records
Indictment refers to a record specifying that a component requires service. The component or a
subcomponent may or may not be deconfigured as a result. Each indictment record contains the
following information:
The time of the error.
The cause of the error.
The subcomponent location of the error (when analysis allows).
In cases when the failing component cannot be identified with certainty, analysis indicts the most
probable component that will need to be replaced to solve the problem.
202
Using event logs