Health Repository Viewer; Indictment Records - HP Integrity Superdome 2 16-socket User Manual

Onboard administrator command line interface user guide
Hide thumbs Also See for Integrity Superdome 2 16-socket:
Table of Contents

Advertisement

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
Event#
Rep
Location
Ent
21
SFW
1,1,0,0,0
21
20
SFW
1,1,0,0,0
20
19
PDHC
1,2
19
18
OA
1,1
18
17
PDHC
1,2
17
16
OA
1,1
16
15
ILO
1,1
15
14
OA
1,1
14
13
OA
1,1
13
12
OA
1,1
12
11
ILO
1,1
11

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
nPar:
AL Encoded Field
vPar
255:255
2 43801f4f01e10029 0000000000000000 SET_SECURE_MODE
255:255
2 4480223a01e10027 0100ff01ffffff94 MEM_DIMM_ENABLE_DONE
14:3
2 4480223800e10025 0100ff01ffffff94 DIMM_LOADING_ORDER_DONE
None
2 4480201f00e10023 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_SUCCESS
14:3
2 438028d300e10021 0000000000000150 BLADE_DIMM_VOLTAGE
None
2 4480201d00e1001f 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_CONTINUE
None
2 4b00260300e1001e 010000004f96aa53 OA_REQUESTS_POWER_CHANGE
None
2 4480201a00e1001c 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_WAITING
1
2 448025a900e1001a 0100ff03ffffff94 PARCON_NPAR_RSRC_ACTIVATION_SKIPPED
None
2 44801ff800e10018 0100ff01ffffff94 BLADE_STATUS_DEGRADED
None
2 4b00260300e10017 010000004f96aa1e OA_REQUESTS_POWER_CHANGE
AL: Alert Level
Data Field
Keyword
Timestamp
04/24/2012 06:29:23
04/24/2012 06:28:54
04/24/2012 06:28:03
04/24/2012 06:27:51
04/24/2012 06:27:49
04/24/2012 06:27:49
04/24/2012 06:27:47
04/24/2012 06:27:47
04/24/2012 06:27:45
04/24/2012 06:26:56
04/24/2012 06:26:54

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents