Viewing Faults and Logs

This chapter includes the following sections:

Faults

Viewing the Fault Summary

Procedure

  Command or Action Purpose

Step 1

Server# scope fault

Enters fault command mode.

Step 2

Server /fault # show discrete-alarm [detail]

Displays a summary of faults from discrete sensors.

Step 3

Server /fault # show threshold-alarm [detail]

Displays a summary of faults from threshold sensors.

Step 4

Server /fault # show pef [detail]

Displays a summary of platform event filters.

Example

This example displays a summary of faults from discrete sensors:

Server# scope fault
Server /fault # show discrete-alarm
Name         Reading              Sensor Status
------------ -------------------- ------------------------------------
PSU2_STATUS  absent               Critical            

Server /fault #

System Event Log

Viewing the System Event Log

SUMMARY STEPS

  1. Server# scope sel
  2. Server /sel # show entries [detail]

DETAILED STEPS

  Command or Action Purpose

Step 1

Server# scope sel

Enters the system event log (SEL) command mode.

Step 2

Server /sel # show entries [detail]

For system events, displays timestamp, the severity of the event, and a description of the event. The detail keyword displays the information in a list format instead of a table format.

Example

This example displays the system event log:

Server# scope sel
Server /sel # show entries
Time                Severity      Description                              
------------------- ------------- ---------------------------------------- 
[System Boot]       Informational " LED_PSU_STATUS: Platform sensor, OFF event was asserted" 
[System Boot]       Informational " LED_HLTH_STATUS: Platform sensor, GREEN was asserted" 
[System Boot]       Normal        " PSU_REDUNDANCY: PS Redundancy sensor, Fully Redundant was asserted" 
[System Boot]       Normal        " PSU2 PSU2_STATUS: Power Supply sensor for PSU2, Power Supply input lost (AC/DC) was deasserted" 
[System Boot]       Informational " LED_PSU_STATUS: Platform sensor, ON event was asserted" 
[System Boot]       Informational " LED_HLTH_STATUS: Platform sensor, AMBER was asserted" 
[System Boot]       Critical      " PSU_REDUNDANCY: PS Redundancy sensor, Redundancy Lost was asserted" 
[System Boot]       Critical      " PSU2 PSU2_STATUS: Power Supply sensor for PSU2, Power Supply input lost (AC/DC) was asserted" 
[System Boot]       Normal        " HDD_01_STATUS: Drive Slot sensor, Drive Presence was asserted" 
[System Boot]       Critical      " HDD_01_STATUS: Drive Slot sensor, Drive Presence was deasserted" 
[System Boot]       Informational " DDR3_P2_D1_INFO: Memory sensor, OFF event was asserted" 
2001-01-01 08:30:16 Warning       " PSU2 PSU2_VOUT: Voltage sensor for PSU2, failure event was deasserted" 
2001-01-01 08:30:16 Critical      " PSU2 PSU2_VOUT: Voltage sensor for PSU2, non-recoverable event was deasserted" 
2001-01-01 08:30:15 Informational " LED_PSU_STATUS: Platform sensor, ON event was asserted" 
2001-01-01 08:30:15 Informational " LED_HLTH_STATUS: Platform sensor, AMBER was asserted" 
2001-01-01 08:30:15 Informational " LED_HLTH_STATUS: Platform sensor, FAST BLINK event was asserted" 
2001-01-01 08:30:14 Non-Recoverable " PSU2 PSU2_VOUT: Voltage sensor for PSU2, non-recoverable event was asserted" 
2001-01-01 08:30:14 Critical      " PSU2 PSU2_VOUT: Voltage sensor for PSU2, failure event was asserted" 
--More--

Clearing the System Event Log

SUMMARY STEPS

  1. Server# scope sel
  2. Server /sel # clear

DETAILED STEPS

  Command or Action Purpose

Step 1

Server# scope sel

Enters the system event log command mode.

Step 2

Server /sel # clear

You are prompted to confirm the action. If you enter y at the prompt, the system event log is cleared.

Example

This example clears the system event log:

Server# scope sel
Server /sel # clear 
This operation will clear the whole sel.
Continue?[y|N]y

Cisco IMC Log

Viewing the CIMC Log

SUMMARY STEPS

  1. Server# scope cimc
  2. Server /cimc # scope log
  3. Server /cimc/log # show entries [detail]

DETAILED STEPS

  Command or Action Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope log

Enters the CIMC log command mode.

Step 3

Server /cimc/log # show entries [detail]

Displays CIMC events, including timestamp, the software module that logged the event, and a description of the event.

Example

This example displays the log of CIMC events:

Recovery-shell# fs-check [p3| p4]

Checks the file system of the specified partition and recover the corrupted file system.

Recovery-shell# activeimage

Shows the current active image that CIMC is running, which can be image 1 or image 2.

Recovery-shell# activeimage [1 | 2]

Changesthe active image to 1 or 2. If the specified image is already active, a message is displayed. Otherwise,the specified image is made active.

After you use the active image command, use the reboot command for the newly configured image to take effect.

Recovery-shell# reboot

Reboots the CIMC firmware.