incorporated into the system in maintenance of the SPARC M10-4S chassis (including
the CPU memory unit) with the replacefru command.
6.3.2
Diagnosing the crossbar unit and crossbar cables
This section shows an example of the command for diagnosing the crossbar unit
mounted in the SPARC M10-4S chassis in a system with a building block
configuration. The command also diagnoses the crossbar cables in the chassis and
their connection status.
The following example shows the command for diagnosing the crossbar cable
between PPAR-ID 0 and BB-ID#1, and the crossbar unit.
<Description of options>
-b: Specifies the BB-ID of the SPARC M10-4S chassis for which bb_id diagnosis is
started.
bb_id can be an integer from 0 to 3 for the SPARC M10-4S (without the crossbar
box) or 0 to 15 for the SPARC M10-4S (with a crossbar box). This option can be
specified with -t or -p.
-p: Specifies the PPAR-ID of the physical partition on which the SPARC M10-4S
chassis that is the destination of ppar_id communication is operating. An integer
from 0 to 15 can be specified as the ppar_id, depending on the system configuration.
XSCF> diagxbu -b 1 -p 0
XBU diagnosis is about to start, Continue?[y|n] : y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120end
XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120end
completed.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90.....120end
completed.
*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".
Even during maintenance on the SPARC M10-4S chassis (including the CPU memory
unit) with the replacefru command, the diagxbu command is not executed. After
SPARC M10-4S maintenance work with the crossbar unit and crossbar cables
removed, use the diagxbu command to diagnose the condition of the crossbar unit
and crossbar cables and the crossbar cable connection status.
6.3.3
Checking the FRU status after maintenance
This section describes the procedure for confirming that the FRU is operating
normally after the completion of maintenance.
1.
Log in to the XSCF shell.
Chapter 6 Restoring the System
115