Skip to main content

A.2.4 Checking diagnosis results


A.2.4 Checking diagnosis results
Use the testsb command to perform an initial diagnosis of the specified physical system board (PSB).
Use the diagxbu command to diagnose the crossbar cables and crossbar units connected to the specified SPARC M10-4S chassis.
testsb command
The testsb command diagnoses the configuration of the specified PSB and the operation of each device mounted on the PSB. After completing the diagnosis, the command displays the results. You can also check the diagnosis results with the display of "Test" and "Fault" by the showboards command.

The displayed diagnosis results from testsb are as follows:
  1. PSB: PSB number
  2. Test: Initial diagnosis status of the PSB
    Unmount: The PSB cannot be recognized because it is not mounted or has failed.
    Unknown: The PSB has not been diagnosed.
    Testing: The initial diagnosis is in progress.
    Passed: The initial diagnosis ended normally.
    Failed: A failure occurred in the initial diagnosis.
  3. Fault: PSB degradation status
    Normal: The PSB is normal.
    Degraded: The PSB can operate but has a degraded component.
    Faulted: The PSB is not operating because a failure occurred or cannot be controlled because of a communication failure.
Example: Diagnosis example of SPARC M10-4S in 1BB configuration (normal end), including execution of show-devs and probe-scsi-all
XSCF> testsb -v -p -s -a -y
Initial diagnosis is about to start, Continue?[y|n] :y
PSB power on sequence started.
POST Sequence 01 Banner
LSB#00: POST 1.9.0 (2012/09/25 16:52)
:

<<Displayed execution results of "probe-scsi-all">>
/pci@8000/pci@4/pci@0/pci@0/scsi@0

FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00

Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 50000394281b6190 SASAddress 50000394281b6192 PhyNum 0
Target d
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 50000394281b5a44 SASAddress 50000394281b5a46 PhyNum 1

<<Displayed execution results of "show-devs">>
/pci@8100/pci@4/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,3
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,2
/pci@8100/pci@4/pci@0/pci@1/ethernet@0,1
/pci@8100/pci@4/pci@0/pci@1/ethernet@0
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,3/fp@0,0
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,3/fp@0,0/disk
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,2/fp@0,0
/pci@8100/pci@4/pci@0/pci@1/QLGC,qlc@0,2/fp@0,0/disk
:
PSB Test Fault
---- ------- --------

00-0 Passed Normal

XSCF>
Example: Diagnosis example of SPARC M10-4S in 4BB configuration (normal end), including execution of show-devs and probe-scsi-all
XSCF> testsb -v -p -s -a -y
Initial diagnosis is about to start, Continue?[y|n] :y
PSB power on sequence started.
LSB#03: POST 3.9.0 (2015/01/27 14:14)
LSB#02: POST 3.9.0 (2015/01/27 14:14)
LSB#01: POST 3.9.0 (2015/01/27 14:14)
POST Sequence 01 Banner
LSB#00: POST 3.9.0 (2015/01/27 14:14)
POST Sequence 02 CPU Check
POST Sequence 03 CPU Register
POST Sequence 04 STICK Increment
POST Sequence 05 Extended Instruction
POST Sequence 06 MMU
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory Address Line
POST Sequence 09 MSCAN
POST Sequence 0A Cache
POST Sequence 0B Floating Point Unit
POST Sequence 0C Encryption
POST Sequence 0D Cacheable Instruction
POST Sequence 0E Softint
POST Sequence 0F CPU Cross Call
POST Sequence 10 CMU-CH
POST Sequence 11 PCI-CH
POST Sequence 12 TOD
POST Sequence 13 MBC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Barrier Blade
POST Sequence 17 Single Barrier Bank
POST Sequence 18 Sector Cache
POST Sequence 19 SX
POST Sequence 1A RT
POST Sequence 1B RT/SX NC
POST Sequence 1C RT/SX Interrupt
POST Sequence 1D RT/SX Barrier
POST Sequence 1E Error CPU Check
POST Sequence 1F System Configuration
POST Sequence 20 System Status Check
POST Sequence 21 Start Hypervisor
POST Sequence Complete.

Omitted

SPARC M10-4S, No Keyboard
Copyright (c) 1998, 2015, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.36.1, 954.5000 GB memory available, Serial #268894481.
[ 2.11.0 ]
Ethernet address b0:99:28:a0:58:11, Host ID: 90070111.

<Execution results of probe-scsi-all command>
LSB#03
/pci@9800/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 17.00.00.00
 600-GB disks mounted in slot#0 and slot#1
Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 50000394281b6190 SASAddress 50000394281b6192 PhyNum 0
Target b
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 50000394281b5a44 SASAddress 50000394281b5a46 PhyNum 1
Target c
Unit 0 Encl Serv device FUJITSU NBBEXP 0d32
SASAddress 500000e0e04902fd PhyNum 14 /pci-performance-counters@8100

LSB#02
/pci@9000/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 17.00.00.00
Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 50000394281b4d98 SASAddress 50000394281b4d9a PhyNum 0
Target b
Unit 0 Encl Serv device FUJITSU BBEXP 0d32
SASAddress 500000e0e02709bd PhyNum 14

Omitted

<Execution results of show-devs command>
8 GFC card mounted in LSB#03 PCI slot#0
/pci@9900/pci@4/pci@0/pci@0/emlx@0,1
/pci@9900/pci@4/pci@0/pci@0/emlx@0
/pci@9900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0
/pci@9900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/tape
/pci@9900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/disk
/pci@9900/pci@4/pci@0/pci@0/emlx@0/fp@0,0
/pci@9900/pci@4/pci@0/pci@0/emlx@0/fp@0,0/tape
/pci@9900/pci@4/pci@0/pci@0/emlx@0/fp@0,0/disk

8 GFC card mounted in LSB#02 PCI slot#0
/pci@9100/pci@4/pci@0/pci@0/emlx@0,1
/pci@9100/pci@4/pci@0/pci@0/emlx@0
/pci@9100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0
/pci@9100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/tape
/pci@9100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/disk
/pci@9100/pci@4/pci@0/pci@0/emlx@0/fp@0,0
/pci@9100/pci@4/pci@0/pci@0/emlx@0/fp@0,0/tape
/pci@9100/pci@4/pci@0/pci@0/emlx@0/fp@0,0/disk

8 GFC card mounted in LSB#01 PCI slot#0
/pci@8900/pci@4/pci@0/pci@0/emlx@0,1
/pci@8900/pci@4/pci@0/pci@0/emlx@0
/pci@8900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0
/pci@8900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/tape
/pci@8900/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/disk
/pci@8900/pci@4/pci@0/pci@0/emlx@0/fp@0,0
/pci@8900/pci@4/pci@0/pci@0/emlx@0/fp@0,0/tape
/pci@8900/pci@4/pci@0/pci@0/emlx@0/fp@0,0/disk

8 GFC card mounted in LSB#00 PCI slot#0
/pci@8100/pci@4/pci@0/pci@0/emlx@0,1
/pci@8100/pci@4/pci@0/pci@0/emlx@0
/pci@8100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0
/pci@8100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/tape
/pci@8100/pci@4/pci@0/pci@0/emlx@0,1/fp@0,0/disk
/pci@8100/pci@4/pci@0/pci@0/emlx@0/fp@0,0
/pci@8100/pci@4/pci@0/pci@0/emlx@0/fp@0,0/tape
/pci@8100/pci@4/pci@0/pci@0/emlx@0/fp@0,0/disk

Omitted

/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
PSB Test Fault
---- ------- --------

00-0 Passed Normal
01-0 Passed Normal
02-0 Passed Normal
03-0 Passed Normal
XSCF>
diagxbu command
diagxbu is a command that diagnoses the crossbar cables and crossbar units connected to the specified SPARC M10-4S chassis.
A crossbar unit is mounted in a SPARC M10-4S chassis or crossbar box and connected by crossbar cables. To execute the diagxbu command, you need to specify the SPARC M10-4S chassis where the diagnosis begins, and also the SPARC M10-4S chassis connected as the communication destination.
If the diagnosis results show that a failure occurred in the crossbar cables and crossbar units, you can check it with the showlog error command. Also, if a crossbar unit is degraded, you can check it with the showstatus command.

The two ways of using diagxbu are as follows: specify the BB-ID of the cable connection destination; or specify the PPAR-ID of the cable connection destination.
  1. How to specify the BB-ID of the cable connection destination
    If a system board (PSB) in the chassis connected by crossbar cables has not been incorporated into a physical partition (PPAR), or if the power to the incorporating physical partition is off, specify the BB-ID of the cable connection destination.
    - bb_id: Enter the BB-ID of the chassis where the diagnosis begins.

    - target_bb: Enter the BB-ID of the chassis connected by the crossbar cables (multiple BB_IDs can be specified).
XSCF> diagxbu -y -b bb_id -t target_bb
  1. How to specify the PPAR-ID of the cable connection destination
    If the system board (PSB) in the chassis connected by crossbar cables has been incorporated into a physical partition and the power to the physical partition is on, specify the PPAR_ID of the cable connection destination.
    - bb_id: Enter the BB-ID of the chassis where the diagnosis begins.

    - ppar_id: Enter the PPAR_ID of the chassis connected by crossbar cables (only one PPAR_ID can be specified).
XSCF> diagxbu -y -b bb_id -p ppar_id
Example: Diagnosis of the crossbar cables and crossbar units between BBID 0 and BB-ID 1
XSCF> diagxbu -y -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30.end

XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120.....150.....180.....210.....240.....|

270.....300.....330.....360.....390.....420.....450.....480.....510.....|

540.....570.....600.....630.....660.....690.....720.....750...end

completed.
Power off sequence started. [1200sec]
0..... 30..... 60....end

completed.
*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".
XSCF> showboards -a
PSB PPAR-ID(LSB) Assignment Pwr Conn Conf Test Fault
---- ------------ ----------- ---- ---- ---- ------- --------

00-0 00(00) Assigned n n n Passed Normal
01-0 01(00) Assigned n n n Passed Normal
02-0 02(00) Assigned n n n Passed Normal
03-0 03(00) Assigned n n n Passed Normal
XSCF>