Skip to main content

4.1.2 Identifying a Failure


4.1.2 Identifying a Failure
This section explains the method for identifying a failure. Use the flow described in "4.1.1 Confirming Whether There is a Failure" to determine the appropriate way of checking for a failure.
Checking the LED Indications
Identify the component requiring maintenance by checking the LEDs on both the front and rear panels of the PCI expansion unit, and the LEDs on the link card of the server to which the PCI expansion unit is connected. To maintain a component, determine its status from the LEDs and then start the maintenance work.
  1. LEDs on front of PCI expansion unit
    The status of the PCI expansion unit or fan unit can be determined by checking the LED or CHECK LED on the respective devices. For details, see "2.2.1 Front LEDs on the PCI Expansion Unit."
  2. LEDs on rear of PCI expansion unit
    By checking the LEDs mounted on the components that can be maintained, the status of each component or the error location can be determined. For details, see "2.2.2 Rear LEDs on the PCI Expansion Unit."
  3. LEDs on link card
    Check the LED on the link card of the server to which the PCI expansion unit is connected. For details, see "2.2.3 Link Card LEDs."
Checking Error Messages
Display the error messages to check the log information and obtain an error overview.
You can use either of the following two methods to check the error messages:
  1. Checking the error log information with the XSCF shell
    For details, see "12.1 Checking a Log Saved by the XSCF" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
  2. Checking messages on Oracle Solaris
    For details, see "12.2 Checking Warning and Notification Messages" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
Checking the Status
Execute the command to check the status of the PCI expansion unit, PCI Express (PCIe) card, or the system.
Table 4-1 lists the commands for checking the status.
Table 4-1  Status Check Commands
Type Command Description
XSCF ioxadm Displays information on the PCI expansion unit. The system administrator and service engineer can manage the PCI expansion unit by executing the ioxadm command.
OpenBoot PROM show-devs Displays device tree information on the PCIe card and other devices connected to the host. Execute this command from the ok prompt.
Oracle Solaris prtdiag Displays the system configuration and all Field Replaceable Units (FRUs) that have experienced failures. Execute this command from the Oracle Solaris super-user prompt.
"FRU" refers to any component that can be replaced by a field engineer.
The command execution examples shown here are based on the assumption that PCIe cards are inserted into all of the slots.
ioxadm Command
Execute the ioxadm command to check the environmental conditions (temperature, voltage, etc.) or LED indications of the PCI expansion unit.
  1. Log in to the XSCF shell.
  2. Execute the ioxadm command to check the environmental conditions of the specified PCI expansion unit.
    The following example shows the environmental conditions for the PCIBOX#2008 "2008" is the last four digits of the serial number of the PCI expansion unit.
XSCF> ioxadm env -te PCIBOX#2008
Location Sensor Value Resolution Units
PCIBOX#2008 AIRFLOW 180.000 0.000 CHM
PCIBOX#2008 P_CONSUMPTION 68.000 0.000 W
PCIBOX#2008/PSU#0 FAN 3936.000 0.000 RPM
PCIBOX#2008/PSU#1 FAN 3584.000 0.000 RPM
PCIBOX#2008/FAN#0 FAN 3374.000 0.000 RPM
PCIBOX#2008/FAN#1 FAN 3374.000 0.000 RPM
PCIBOX#2008/FAN#2 FAN 3374.000 0.000 RPM
PCIBOX#2008/IOB T_INTAKE 26.000 0.000 C
PCIBOX#2008/IOB T_PART_NO0 31.500 0.000 C
PCIBOX#2008/IOB T_PART_NO1 30.750 0.000 C
PCIBOX#2008/IOB T_PART_NO2 31.500 0.000 C
PCIBOX#2008/IOB V_12_0V 12.069 0.000 V
PCIBOX#2008/IOB V_3_3_NO0 3.293 0.000 V
PCIBOX#2008/IOB V_3_3_NO1 3.295 0.000 V
PCIBOX#2008/IOB V_3_3_NO2 3.291 0.000 V
PCIBOX#2008/IOB V_3_3_NO3 3.300 0.000 V
PCIBOX#2008/IOB V_1_8V 1.804 0.000 V
PCIBOX#2008/IOB V_0_9V 0.900 0.000 V
show-devs Command
Execute the show-devs command of OpenBoot PROM to display the path from the host server to the PCIe card on the I/O board.
  1. Display the ok prompt.
  2. Execute the show-devs command to check the device tree information.
{0} ok show-devs
/pci-performance-counters@8100
/pci-performance-counters@8000
/pci@8100
/pci@8000
/cpu@1f
/cpu@1e
/cpu@1d
/cpu@1c
/cpu@1b
/cpu@1a
/cpu@19
/cpu@18
/cpu@17
/cpu@16
/cpu@15
/cpu@14
/cpu@13
/cpu@12
/cpu@11
/cpu@10
/cpu@f
/cpu@e
/cpu@d
/cpu@c
/cpu@b
/cpu@a
/cpu@9
/cpu@8
/cpu@7
/cpu@6
/cpu@5
/cpu@4
/cpu@3
/cpu@2
/cpu@1
/cpu@0
/virtual-devices@100
/iscsi-hba
/virtual-memory
/memory@m7e00,60000000
/aliases
/options
/openprom
/chosen
/packages
/pci@8100/pci@4
/pci@8100/pci@4/pci@0
/pci@8100/pci@4/pci@0/pci@9
/pci@8100/pci@4/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@0/network@0,1
/pci@8100/pci@4/pci@0/pci@0/network@0
/pci@8000/pci@4
/pci@8000/pci@4/pci@0
/pci@8000/pci@4/pci@0/pci@8
/pci@8000/pci@4/pci@0/pci@2
/pci@8000/pci@4/pci@0/pci@1
/pci@8000/pci@4/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@8
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@1
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@11
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@10
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@1
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@11
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@10
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/FJSV,eulsa@0
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/FJSV,eulsa@0/tape
/pci@8000/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/FJSV,eulsa@0/disk
/pci@8000/pci@4/pci@0/pci@2/pci@0
/pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1
/pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4
/pci@8000/pci@4/pci@0/pci@1/network@0,1
/pci@8000/pci@4/pci@0/pci@1/network@0
/pci@8000/pci@4/pci@0/pci@0/scsi@0
/pci@8000/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8000/pci@4/pci@0/pci@0/scsi@0/tape
/virtual-devices@100/channel-devices@200
/virtual-devices@100/flashprom@0
/virtual-devices@100/rtc@5
/virtual-devices@100/console@1
/virtual-devices@100/channel-devices@200/virtual-domain-service@0
/virtual-devices@100/channel-devices@200/virtual-channel@3
/virtual-devices@100/channel-devices@200/virtual-channel-client@2
/virtual-devices@100/channel-devices@200/virtual-channel-client@1
/virtual-devices@100/channel-devices@200/virtual-channel@0
/iscsi-hba/disk
/openprom/client-services
/packages/obp-tftp
/packages/kbd-translator
/packages/SUNW,asr
/packages/dropins
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,probe-error-handler
/packages/SUNW,builtin-drivers
{0} ok
prtdiag Command
Execute the prtdiag command of Oracle Solaris to check the system configuration and any failed FRUs.
  1. Display the Oracle Solaris super-user prompt.
  2. Execute the prtdiag command to check the system configuration and any failed FRUs.
# prtdiag -v
System Configuration: Oracle Corporation sun4v SPARC M10-4
Memory size: 64000 Megabytes

------------------------Omitted------------------------


================================ IO Devices ================================
Slot + Bus Name + Model Speed
Status Type Path
----------------------------------------------------------------------------

/BB0/CMUL/SASHBA PCIE scsi-pciex1000,87 LSI,2308_2 5.0GTx8
/pci@8000/pci@4/pci@0/pci@0/scsi@0
/BB0/CMUL/NET0 PCIE network-pciex14e4,1656 2.5GTx1
/pci@8000/pci@4/pci@0/pci@9/network@0
/BB0/CMUL/NET1 PCIE network-pciex14e4,1656 2.5GTx1
/pci@8000/pci@4/pci@0/pci@9/network@0,1
/BB0/CMUL/NET2 PCIE network-pciex14e4,1656 2.5GTx1
/pci@8000/pci@4/pci@0/pci@a/network@0
/BB0/CMUL/NET3 PCIE network-pciex14e4,1656 2.5GTx1
/pci@8000/pci@4/pci@0/pci@a/network@0,1

------------------------Omitted------------------------


Chassis Serial Number
---------------------

2081203001
#
Checking Log Information
Execute the showlogs command to check the error log information.
  1. Log in to the XSCF shell.
  2. Execute the showlogs command to check the error log information.
    The log information is listed in order of date, with the oldest appearing first.
    The following example shows that an Alarm status occurred in PSU#1 of PCIBOX#2006 at 20:30:34 on Oct. 17.
XSCF> showlogs error -v
Date: Oct 17 20:30:34 JST 2016
Code: 80000408-00d4010000ff0000ff-110000256101000000000000
Status: Alarm Occurred: Oct 17 20:30:34.453 JST 2016
FRU: /BB#0/PCI#0/PCIBOX#2006/PSU#1
Msg: PSU failed
Diagnostic Code:
00003230 30360100 0000
00000000 00000000 0000
00000000 00000000 0000
01618800 00000000 80000000 00000000
00000000 00000000 0000