Identifying Service Action Keywords In System Event Logs - IBM Power Systems 7063-CR1 Service Manual

20. The service actions for all of the events that were identified in step 18 on page 12 must be performed
to successfully complete the repair. Record the SEL record IDs for the events that you identified in
step 18 on page 12. The SEL record ID is indicated by the leftmost digits of the SEL. Use the
ipmitool command to display SEL details for each SEL record ID that you recorded.
v To display SEL details by using the Petitboot command line, use the following command:
ipmitool sel get <SEL record ID>
Note: The SEL record ID must be entered in hexadecimal format. For example: 0x1a.
v To display SEL details remotely over the LAN, use the following command:
ipmitool -I lanplus -U <username> -P <password> -H <BMC IP address or BMC hostname> sel
get <SEL record ID>
Note: The SEL record ID must be entered in hexadecimal format. For example: 0x1a.
The sensor ID field contains sensor information in the format sensor name (sensor ID). Record the
sensor name, sensor ID, and event description. Then, go to "Identifying a service action by using
sensor and event information for the 7063-CR1" on page 14 and use the sensor name, sensor ID, and
event description that you recorded to determine the service action to perform.
This ends the procedure.

Identifying service action keywords in system event logs

System event logs (SELs) that have Asserted and any of the keywords indicated below in the description
require a service action.
Temperature and voltage service action keywords
v Transition to Critical from Less Severe
v Transition to Critical from Non-recoverable
v Transition to Non-recoverable
v Transition to Non-recoverable from Less Severe
v Upper Critical - going high
v Upper Non-recoverable – going high
Backplane service action keywords
v State Asserted
Chassis service action keywords
v General Chassis intrusion
Fan service action keywords
v Transition to Critical from Less Severe
v Transition to Non-recoverable from Less Severe
v Transition to Critical from Non-recoverable
v Device Removed / Device Absent
v Transition to degraded
v Install error
v Redundancy lost
v Non-redundant insufficient resources
Beginning troubleshooting and problem analysis
13