Subcomponent Isolation And Deconfiguration Displays; Using Event Logs; Live Viewer - HP Integrity Superdome 2 16-socket Service Manual

Hp integrity superdome 2 user service guide
Hide thumbs Also See for Integrity Superdome 2 16-socket:
Table of Contents

Advertisement

- 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.

Using event logs

Event logs are generated by software or firmware when an event is detected. Some events that
cause event records to be generated are:
Hardware-related.
Example: fan or power supply failure.
Software-related.
Example: indicating that software reached a certain point in the code, or that a certain
amount of time has passed.
The OA can timestamp and filter events, then store and transfer them to event log readers. Log
entries can be read by management applications in:
Operating Systems
OAs
SEL viewers
FPL viewers
Live Event viewers
EAE
Log entries can be cleared by OS management applications or by the OA itself.
Events are classified into a number of severity levels, ranging from critical failure to non-error
forward progress notification. The severity level is encoded in the alert level data field on an event
record. Different system actions may result from generation of an event record, depending on alert
level.

Live viewer

The live event viewer provides a way for you to see records as they occur. The OA supports multiple
simultaneous live event viewers that are created and destroyed dynamically when requested. The
maximum number of simultaneous live event viewers is limited by the number of connections
supported by the OA.
Each live event viewer works independently from any other event viewer, meaning that each live
event viewer can select its own filter and format options without affecting other live event viewers.
72
Troubleshooting

Advertisement

Table of Contents
loading

Table of Contents