Technical data

Chapter 4

System Event Log Decoding

Introduction

194

Introduction

This chapter provides information to decode and interpret the System Event Log (SEL).

Accessing the SEL

The System Event Log is accessed through the ShMM clia using the sel command. The sel command

needs 2 arguments. The first argument specifies the IPMB address of the component that maintains the SEL

(20 in the example). The second argument identifies the number of entries from the end of the SEL to be

displayed (5 in the example).

# clia sel 20 5

Pigeon Point Shelf Manager Command Line Interpreter

0x0270: Event: at Apr 19 07:24:11 1970; from:(0x8e,0,0); sensor:(0x01,55);

event:0x1(asserted): "Upper Non-Critical", Threshold: 0x4b, Reading: 0x4b

0x0272: Event: at Apr 19 07:24:35 1970; from:(0x8e,0,0); sensor:(0x01,93);

event:0x1(asserted): "Upper Non-Critical", Threshold: 0x2d, Reading: 0x2d

0x0273: Event: at Apr 19 07:25:31 1970; from:(0x8e,0,0); sensor:(0x01,55);

event:0x1(deasserted): "Upper Non-Critical", Threshold: 0x4b, Reading: 0x48

Decoding an SEL Entry

The general format of an SEL entry is a colon and semicolon delineated set of fields. Entries are read from left

to right. The first field is the SEL ID. The SEL ID is a unique value generated by the ‘Event Receiver”. The

Event Receiver in the HP bh5700 ATCA 14-Slot Blade Server is the ShMM. Each field contains information

as specified in Table 4-1.

System Event Log Record Structure

Table 4-1 presents the format of the SEL Event Records and describes the information that each record field

contains.

Table 4-1 Raw SEL Event Record Data

Byte Field Description

Record ID ID used for SEL Record access.

Note: The Record ID values 0000h and FFFFh have special

meaning in the Event Access commands and must not be used as

Record ID values for slotted SEL Event Records.

3 Record Type [7:0] - Record Type

02h = system event record

C0h - DFh = OEM timestamped, bytes 8-16 OEM defined

E0h-FFh = OEM non-timestamped, bytes 4-16 OEM defined