Subcomponent Isolation And Deconfiguration Displays - HP Integrity Superdome 2 16-socket User Manual

Timestamp: Thu Sep 10 18:34:12 2009
Serial Num: MYJ84901ZH
Parent Serial: 1Z34AB7890
Part Num: AH342-60003
Spare Part Num: AH342-60003
Manufacturer: HP
Product Name: CB900s i2
Board Serial Num: MYJ84901ZH
- FRU Data Extension -
Name: value
Name2: Value2
(Detailed info about FRU is provided here if it exists. E.g. For CPUs max freq will be provided here. If no
data, entire section omitted.)
--- Action - Indict ---
Event No: 4000
Provider: some_provider_name
Reason: Text reason of problem from WS-Man alert.
Reason: 3:1
Description: Text description of problem from ws-man Alert.
Bundle ID: 0x400000000000010D
Alert ID: 7400020091023220043
- Indicted / Acquitted -
Type Timestamp
Ind Thu Sep 10 18:34:11 2009
Acq Thu Sep 10 18:34:11 2009
---
- Supporting Symptoms -
Reason: Text reason of supporting symptom** (not from ws-man).
- SubFru Isolation -
SubFRUs requiring service shown here. If none, section omitted.
- SubFru Deconfiguration -
Deconfig'ed subFRUs shown here. If none, section omitted.
- Related Locations -
0x0B00FFFF03FFFF54 (Cohorts. If none, section omitted.)

Subcomponent isolation and deconfiguration displays

Subcomponent isolation refers to the subcomponents of a part that can require service. In these
cases, the component is indicted because the only way the subcomponent can be serviced is by
removing and servicing the entire component.
Subcomponent deconfigurations are also possible. These are indications of subcomponent failures.
The show <location> and show fru command output may contain "SubFru Isolation" and
"SubFru Deconfiguration" sections to communicate subcomponent health information. If a
subcomponent deconfiguration event occurs, the corresponding subcomponent Isolation will also
be set, which triggers an indictment of the parent component.
206 Using event logs
Entity Reason
CAE See reason above.
User User request