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 on the specified hardware.
Use the diagxbu command to diagnose the crossbar cables and crossbar units connected to the specified SPARC M12-2S.
testsb command
The testsb command diagnoses the configuration of the specified physical system board (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: BB identification number displayed in the format of xx-0 (xx is the BB-ID)
  2. Test: Initial diagnosis status of the physical system board (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: Degradation status of the physical system board (PSB)
    Normal: The PSB is normal.
    Degraded: The physical system board (PSB) can operate but has a degraded component.
    Faulted: The physical system board (PSB) is not operating because a failure occurred or it cannot be controlled because of a communication failure.
Example: Execution example for the SPARC M12-2S in the 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 5.6.0 (2016/08/25 09:01)
Omitted
  <<Displayed execution results of "probe-scsi-all">>

/pci@8500/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b0003d PhyNum 14
/pci@8100/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Disk TOSHIBA AL13SEB600 3703 1172123568 Blocks, 600 GB
SASDeviceName 50000396f8120490 SASAddress 50000396f8120492 PhyNum 0
Target b
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b0003d PhyNum 14
  <<Displayed execution results of "show-devs">>

Omitted
/pci@8700/pci@4
/pci@8700/pci@4/pci@0
/pci@8700/pci@4/pci@0/pci@10
/pci@8600/pci@4
/pci@8600/pci@4/pci@0
/pci@8600/pci@4/pci@0/pci@10
/pci@8600/pci@4/pci@0/pci@1
/pci@8500/pci@4
/pci@8500/pci@4/pci@0
/pci@8500/pci@4/pci@0/pci@1
/pci@8500/pci@4/pci@0/pci@0
/pci@8500/pci@4/pci@0/pci@0/scsi@0
/pci@8500/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8500/pci@4/pci@0/pci@0/scsi@0/tape
/pci@8400/pci@4
/pci@8400/pci@4/pci@0
/pci@8400/pci@4/pci@0/pci@1
/pci@8400/pci@4/pci@0/pci@0
/pci@8400/pci@4/pci@0/pci@0/network@0,1
/pci@8400/pci@4/pci@0/pci@0/network@0
/pci@8300/pci@4
/pci@8300/pci@4/pci@0
/pci@8300/pci@4/pci@0/pci@9
/pci@8300/pci@4/pci@0/pci@8
/pci@8200/pci@4
/pci@8200/pci@4/pci@0
/pci@8200/pci@4/pci@0/pci@9
/pci@8200/pci@4/pci@0/pci@8
/pci@8100/pci@4
/pci@8100/pci@4/pci@0
/pci@8100/pci@4/pci@0/pci@11
/pci@8100/pci@4/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@1/usb@0
/pci@8100/pci@4/pci@0/pci@1/usb@0/hub@5
/pci@8100/pci@4/pci@0/pci@1/usb@0/hub@1
/pci@8100/pci@4/pci@0/pci@0/scsi@0
/pci@8100/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8100/pci@4/pci@0/pci@0/scsi@0/tape
/pci@8000/pci@4
/pci@8000/pci@4/pci@0
/pci@8000/pci@4/pci@0/pci@11
/pci@8000/pci@4/pci@0/pci@0
/pci@8000/pci@4/pci@0/pci@0/network@0,1
/pci@8000/pci@4/pci@0/pci@0/network@0
Omitted
PSB Test Fault
---- ------- --------

00-0 Passed Normal
XSCF>
Example: Execution example for the SPARC M12-2S in the 3BB 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#01: POST 5.6.0 (2016/08/25 09:01)
POST Sequence 01 Banner
LSB#00: POST 5.6.0 (2016/08/25 09:01)
LSB#02: POST 5.6.0 (2016/08/25 09:01)
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 MSCAN
POST Sequence 09 Cache
POST Sequence 0A Interrupt Queue
POST Sequence 0B Floating Point Unit
POST Sequence 0C Encryption
POST Sequence 0D Random number
POST Sequence 0E Cacheable Instruction
POST Sequence 0F Softint
POST Sequence 10 CPU Cross Call
POST Sequence 11 CMU-CH
POST Sequence 12 PCI-CH
POST Sequence 13 TOD
POST Sequence 14 MBC Check Before STICK Diag
POST Sequence 15 STICK Stop
POST Sequence 16 STICK Start
POST Sequence 17 CPU Speed Control
POST Sequence 18 SX
POST Sequence 19 RT
POST Sequence 1A RT/SX NC
POST Sequence 1B RT/SX Interrupt
POST Sequence 1C CPU Status Check
POST Sequence 1D System Configuration
POST Sequence 1E System Status Check
POST Sequence 1F Prepare To Start Hypervisor
POST Sequence Complete.
Omitted
SPARC M12-2S, No Keyboard
Copyright (c) 1998, 2016, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.38.5, 762.5000 GB memory available, Serial #268906560.
[ 3.0.7 ]
Ethernet address b0:99:28:a0:87:40, Host ID: 90073040.

<Execution results of probe-scsi-all command>
/pci@9500/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b00c7d PhyNum 14
* LSB#03
/pci@9100/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
* 600-GB HDD mounted in slot#0 and slot#1
Target a
Unit 0 Disk TOSHIBA AL13SEB600 3703 1172123568 Blocks, 600 GB
SASDeviceName 50000396f8120534 SASAddress 50000396f8120536 PhyNum 0
Target b
Unit 0 Disk TOSHIBA AL13SEB900AL14SE 3702 1758174768 Blocks, 900 GB
SASDeviceName 50000396880125e9 SASAddress 50000396880125ea PhyNum 1
Target c
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b00c7d PhyNum 14
/pci@8d00/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b0063d PhyNum 14
/pci@8900/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Disk TOSHIBA AL13SEB600 3703 1172123568 Blocks, 600 GB
SASDeviceName 50000396f812051c SASAddress 50000396f812051e PhyNum 0
Target b
Unit 0 Disk TOSHIBA AL13SEB600 3703 1172123568 Blocks, 600 GB
SASDeviceName 50000396c828404c SASAddress 50000396c828404e PhyNum 1
Target c
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b0063d PhyNum 14
/pci@8500/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b00ffd PhyNum 14
/pci@8100/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 20.00.07.00
Target a
Unit 0 Disk TOSHIBA AL13SEB600 3703 1172123568 Blocks, 600 GB
SASDeviceName 50000396f8120524 SASAddress 50000396f8120526 PhyNum 0
Target b
Unit 0 Disk TOSHIBA AL13SEB600AL14SE 3702 1172123568 Blocks, 600 GB
SASDeviceName 5000039678332c01 SASAddress 5000039678332c02 PhyNum 1
Target c
Unit 0 Encl Serv device FUJITSU BBEXP 1303
SASAddress 500000e0e0b00ffd PhyNum 14

<Execution results of show-devs command>
/pci@9700/pci@4
/pci@9700/pci@4/pci@0
/pci@9700/pci@4/pci@0/pci@10
/pci@9700/pci@4/pci@0/pci@10/network@0,1
/pci@9700/pci@4/pci@0/pci@10/network@0
/pci@9600/pci@4
/pci@9600/pci@4/pci@0
/pci@9600/pci@4/pci@0/pci@10
/pci@9600/pci@4/pci@0/pci@1
/pci@9500/pci@4
/pci@9500/pci@4/pci@0
/pci@9500/pci@4/pci@0/pci@1
/pci@9500/pci@4/pci@0/pci@0
/pci@9500/pci@4/pci@0/pci@0/scsi@0
/pci@9500/pci@4/pci@0/pci@0/scsi@0/disk
/pci@9500/pci@4/pci@0/pci@0/scsi@0/tape
/pci@9400/pci@4
/pci@9400/pci@4/pci@0
/pci@9400/pci@4/pci@0/pci@1
/pci@9400/pci@4/pci@0/pci@0
/pci@9400/pci@4/pci@0/pci@0/network@0,1
/pci@9400/pci@4/pci@0/pci@0/network@0
/pci@9300/pci@4
/pci@9300/pci@4/pci@0
/pci@9300/pci@4/pci@0/pci@9
/pci@9300/pci@4/pci@0/pci@8
/pci@9300/pci@4/pci@0/pci@8/network@0,3
/pci@9300/pci@4/pci@0/pci@8/network@0,2
/pci@9300/pci@4/pci@0/pci@8/network@0,1
/pci@9300/pci@4/pci@0/pci@8/network@0
/pci@9200/pci@4
/pci@9200/pci@4/pci@0
/pci@9200/pci@4/pci@0/pci@9
/pci@9200/pci@4/pci@0/pci@8
/pci@9100/pci@4
/pci@9100/pci@4/pci@0
/pci@9100/pci@4/pci@0/pci@11
/pci@9100/pci@4/pci@0/pci@1
/pci@9100/pci@4/pci@0/pci@0
/pci@9100/pci@4/pci@0/pci@1/usb@0
/pci@9100/pci@4/pci@0/pci@1/usb@0/hub@5
/pci@9100/pci@4/pci@0/pci@1/usb@0/hub@1
/pci@9100/pci@4/pci@0/pci@0/scsi@0
/pci@9100/pci@4/pci@0/pci@0/scsi@0/disk
/pci@9100/pci@4/pci@0/pci@0/scsi@0/tape
/pci@9000/pci@4
/pci@9000/pci@4/pci@0
/pci@9000/pci@4/pci@0/pci@11
/pci@9000/pci@4/pci@0/pci@0
/pci@9000/pci@4/pci@0/pci@0/network@0,1
/pci@9000/pci@4/pci@0/pci@0/network@0
/pci@8f00/pci@4
/pci@8f00/pci@4/pci@0
/pci@8f00/pci@4/pci@0/pci@10
/pci@8f00/pci@4/pci@0/pci@10/network@0,1
/pci@8f00/pci@4/pci@0/pci@10/network@0
/pci@8e00/pci@4
/pci@8e00/pci@4/pci@0
/pci@8e00/pci@4/pci@0/pci@10
/pci@8e00/pci@4/pci@0/pci@1
/pci@8d00/pci@4
/pci@8d00/pci@4/pci@0
/pci@8d00/pci@4/pci@0/pci@1
/pci@8d00/pci@4/pci@0/pci@0
/pci@8d00/pci@4/pci@0/pci@0/scsi@0
/pci@8d00/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8d00/pci@4/pci@0/pci@0/scsi@0/tape
/pci@8c00/pci@4
/pci@8c00/pci@4/pci@0
/pci@8c00/pci@4/pci@0/pci@1
/pci@8c00/pci@4/pci@0/pci@0
/pci@8c00/pci@4/pci@0/pci@0/network@0,1
/pci@8c00/pci@4/pci@0/pci@0/network@0
/pci@8b00/pci@4
/pci@8b00/pci@4/pci@0
/pci@8b00/pci@4/pci@0/pci@9
/pci@8b00/pci@4/pci@0/pci@8
/pci@8b00/pci@4/pci@0/pci@8/network@0,3
/pci@8b00/pci@4/pci@0/pci@8/network@0,2
/pci@8b00/pci@4/pci@0/pci@8/network@0,1
/pci@8b00/pci@4/pci@0/pci@8/network@0
/pci@8a00/pci@4
/pci@8a00/pci@4/pci@0
/pci@8a00/pci@4/pci@0/pci@9
/pci@8a00/pci@4/pci@0/pci@8
/pci@8900/pci@4
/pci@8900/pci@4/pci@0
/pci@8900/pci@4/pci@0/pci@11
/pci@8900/pci@4/pci@0/pci@1
/pci@8900/pci@4/pci@0/pci@0
/pci@8900/pci@4/pci@0/pci@1/usb@0
/pci@8900/pci@4/pci@0/pci@1/usb@0/hub@5
/pci@8900/pci@4/pci@0/pci@1/usb@0/hub@1
/pci@8900/pci@4/pci@0/pci@0/scsi@0
/pci@8900/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8900/pci@4/pci@0/pci@0/scsi@0/tape
/pci@8800/pci@4
/pci@8800/pci@4/pci@0
/pci@8800/pci@4/pci@0/pci@11
/pci@8800/pci@4/pci@0/pci@0
/pci@8800/pci@4/pci@0/pci@0/network@0,1
/pci@8800/pci@4/pci@0/pci@0/network@0
/pci@8700/pci@4
/pci@8700/pci@4/pci@0
/pci@8700/pci@4/pci@0/pci@10
/pci@8700/pci@4/pci@0/pci@10/network@0,1
/pci@8700/pci@4/pci@0/pci@10/network@0
/pci@8600/pci@4
/pci@8600/pci@4/pci@0
/pci@8600/pci@4/pci@0/pci@10
/pci@8600/pci@4/pci@0/pci@1
/pci@8500/pci@4
/pci@8500/pci@4/pci@0
/pci@8500/pci@4/pci@0/pci@1
/pci@8500/pci@4/pci@0/pci@0
/pci@8500/pci@4/pci@0/pci@0/scsi@0
/pci@8500/pci@4/pci@0/pci@0/scsi@0/disk
/pci@8500/pci@4/pci@0/pci@0/scsi@0/tape
/pci@8400/pci@4
/pci@8400/pci@4/pci@0
/pci@8400/pci@4/pci@0/pci@1
/pci@8400/pci@4/pci@0/pci@0
/pci@8400/pci@4/pci@0/pci@0/network@0,1
/pci@8400/pci@4/pci@0/pci@0/network@0
/pci@8300/pci@4
/pci@8300/pci@4/pci@0
/pci@8300/pci@4/pci@0/pci@9
/pci@8300/pci@4/pci@0/pci@8
/pci@8300/pci@4/pci@0/pci@8/network@0,3
/pci@8300/pci@4/pci@0/pci@8/network@0,2
/pci@8300/pci@4/pci@0/pci@8/network@0,1
/pci@8300/pci@4/pci@0/pci@8/network@0
/pci@8200/pci@4
/pci@8200/pci@4/pci@0
/pci@8200/pci@4/pci@0/pci@9
/pci@8200/pci@4/pci@0/pci@8
/pci@8100/pci@4
/pci@8100/pci@4/pci@0
/pci@8100/pci@4/pci@0/pci@11
/pci@8100/pci@4/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@8
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@1
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@11
/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@10
<a>/pci@8100/pci@4/pci@0/pci@11/pci@0/pci@0/pci@0/pci@1/p
diagxbu command
diagxbu is a command that diagnoses the crossbar units mounted in the specified SPARC M12-2S and the crossbar cables connected to the crossbar units.
To execute the diagxbu command, you need to specify the BB-ID of the SPARC M12-2S where the diagnosis begins, and also the BB-ID of the SPARC M12-2S 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 physical system board (PSB) in the SPARC M12-2S 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 SPARC M12-2S where the diagnosis begins.

    - target_bb: Enter the BB-ID of the SPARC M12-2S 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 physical system board (PSB) in the SPARC M12-2S 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 SPARC M12-2S where the diagnosis begins.

    - ppar_id: Enter the PPAR-ID of the SPARC M12-2S 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 BB-ID 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>