Skip to main content

12.1.3 Checking the Error Log


12.1.3 Checking the Error Log
The error log is a fault information-related log. Use the showlogs command with the error operand specified to refer to the log for a notification or failure that occurred in the system.
Use Scenarios
The scenarios for using the error log on the XSCF are described below.
  1. A message was output to the domain console, the XSCF shell terminal, or XSCF Web, so the log is used to check whether a failure occurred.
  2. Notification was sent to the already registered e-mail address, so the log is used to check for fault information.
  3. A trap was generated by the SNMP manager, so the log is used to check for fault information.
Operation Procedure
  1. Execute the showlogs command with the error operand specified on the XSCF shell.
XSCF> showlogs error
Date: Oct 20 17:45:31 JST 2012
      Code: 00112233-444555666777-888999aaabbbcccdddeeefff
      Status: Warning Occurred: Oct 20 17:45:31.000 JST 2012
      FRU: /PSU#1
      Msg: ACFAIL occurred (ACS=3)(FEP type = A1)
Date: Oct 20 17:45:31 JST 2012
      Code: 00112233-444555666777-888999aaabbbcccdddeee000
      Status: Alarm Occurred: Oct 20 17:45:31.000 JST 2012
      FRU: /PSU#1
      Msg: ACFAIL occurred (ACS=3)(FEP type = A1)
  1. The following content is displayed in the above example.
  2. - Registered time (Date) as logged for the problem

     It is shown in local time.
  3. - DIAGCODE, which field engineers and service engineers use for troubleshooting

     (Code)
Note - Users are requested to report this code to a field engineer or service engineer. The code helps in finding an early solution to the problem.
  1. - Failure level (Status) of the part

     One of the following is displayed:
     Alarm: Failure or error of the relevant part
     Warning: Partial degradation or warning of the relevant part
     Information: Notification 
     Notice: System status notification
  2. - Time that the problem occurred (Occurred)

     It is shown in local time.
  3. - Replacement part possibly faulty (FRU)

     If the first, second, and third most likely faulty parts are displayed, they are delimited by a comma (,). If there are additional likely faulty parts, an asterisk (*) is displayed after the last comma (,). Each part is shown hierarchically in the format of the mounting path of the part. The determination of whether to display the second and subsequent most likely faulty parts depends on the detected fault location.

     The following cases show the meaning of the displayed "FRU:" content.
  4.   a. "/PSU#0,/PSU#1" is displayed.
       PSU#0 and PSU#1 have been detected as the first and second most likely faulty parts, respectively. This means each of the parts may need to be replaced depending on its condition.
  5. b. "/BB#1/XBU#0/CBL#0R,/XBBOX#80/XBU#0,/BB#1/XBU#0,*" is displayed.

     CBL#0R between BB#1 and XBBOX#80, XBU#0 in XBBOX#80, and XBU#0 in BB#1 have been detected as the first, second, and third most likely faulty parts, respectively, along with other parts also detected as such. This means each of the parts may need to be replaced depending on its condition.
  6.   c. "/BB#0/PCI#3" is displayed.
     BB#0/PCI#3 has been detected as a likely faulty part, and PCI slot 3 of BB-ID 0 has a problem. This means the device connected to PCI slot 3 may need to be replaced depending on its condition.
  7.   d. "/MBU/MEM#02A" is displayed.
     /MBU/MEM#02A has been detected as a likely faulty part, and memory slot 02A of the motherboard unit has a problem. This means memory slot 02A may need to be replaced depending on its condition.
  8.   e. "/BB#0/CMUL/MEM#02A" is displayed.
    /BB#0/CMUL/MEM#02A has been detected as a likely faulty part, and memory slot 02A of the CPU memory unit (lower) of BB-ID 0 has a problem. This means memory slot 02A may need to be replaced depending on its condition.
  9.   f. "/BB#0/CMUL/MEM#02A-03A" is displayed.
     /BB#0/CMUL/MEM#02A-03A has been detected as a likely faulty part, and memory slots 02A and 02B of the CPU memory unit (lower) of BB-ID 0 have problems. This means the memory in memory slots 02A and 02B may need to be replaced as a pair, depending on their condition.
  10. - One-row message outlining a problem (Msg)
Note - For details of the showlogs(8) command, see the man pages or the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual.