Fujitsu M10-4S
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Fujitsu M10
 

Missing XB80 and BB00 chassis at power on of a newly configured M10-4S system using XBBOX crossbar units in an expansion rack may be due to a missing XSCF BB control cable.

Applies to:

Symptoms

In an XBBOX crossbar configuration using a single expansion rack with XB80, XB81, and some number of M10-4S building blocks, a XSCF dual cable is used to connect XB80 to XB81, and XSCF control cables run from each building block BB00, BB01, etcetera, to the XSCF interface units on XB80 and XB81.

In addition, a single XSCF BB control cable is run from port 16 of the XB80 XSCF IF unit to port 16 of the XB81 XSCF IF unit.  If the port 16 cable is not connected, XB81 will boot up as master and XB80 will come up as slave.  XB81, however will not detect the presence of XB80, nor will it detect the presence of BB00.  

A showlogs monitor may show the expected SCF:configuration changed messages for components of the missing BB00, but these components will fail to show up in showhardconf output.

The following error indications may appear in showlogs monitor output:

XSCF> showlogs monitor
Jun  8 00:35:01 localhost Alarm: /XBBOX#80:SCF:BB control cable detected unexpected
Jun  8 00:35:02 localhost Alarm: :SCF:Gaps between XBBOX-ID
Jun  8 00:35:02 localhost Alarm: /BB#0/CMUL:SCF:XSCF hang-up is detected
Jun  8 00:35:17 localhost Event: SCF:XSCF ready

The following error indications may appear in showlogs error output:

XSCF> showlogs error
Date: Jun 08 00:34:58 UTC 2013
    Code: 80000000-00a5ff0000ff0000ff-01a100050000000000000000
    Status: Alarm                  Occurred: Jun 08 00:32:37.379 UTC 2013
    FRU: /XBBOX#80
    Msg: BB control cable detected unexpected
Date: Jun 08 00:34:58 UTC 2013
    Code: 80000000-0000ff0000ff0000ff-018a00120000000000000000
    Status: Alarm                  Occurred: Jun 08 00:32:52.745 UTC 2013
    Msg: Gaps between XBBOX-ID
Date: Jun 08 00:34:59 UTC 2013
    Code: 80000000-0056010000ff0000ff-01a100020000000000000000
    Status: Alarm                  Occurred: Jun 08 00:33:54.033 UTC 2013
    FRU: /BB#0/CMUL
    Msg: XSCF hang-up is detected
 

Changes

This issue is typically seen during the initial installation of multiple M10-4S building blocks.  It could also occur should the affected XSCF BB control cable becomes disconnected.

Cause

An XSCF BB control cable from port 16 of the XB80 XSCF IF unit to port 16 of the XB81 XSCF IF unit may be missing or disconnected.

Solution

The problem is easily resolved by adding an XSCF BB control cable between XSCF interface port 16 on XB80 and XSCF interface port 16 on XB81.  The presence of the cable will cause each M10-4S building block and XBBOX to reset as seen in the output of showlogs power.

XSCF> showlogs power
Date                          Event              Cause             ID  Switch
Jun 08 00:32:33 UTC 2013      SCF Reset          Power On          01  Service
Jun 08 00:32:33 UTC 2013      SCF Reset          Power On          03  Service
Jun 08 00:32:34 UTC 2013      SCF Reset          Power On          81  Service
Jun 08 00:32:34 UTC 2013      SCF Reset          Power On          02  Service
Jun 08 00:32:34 UTC 2013      SCF Reset          Power On          00  Service
...at this point, the XB80 XSCF interface unit port 16 is connected to the XB81 XSCF interface unit port 16...
Jun 08 01:31:25 UTC 2013      SCF Reset          Self Reset        02  Service
Jun 08 01:31:27 UTC 2013      SCF Reset          Self Reset        80  Service
Jun 08 01:31:26 UTC 2013      SCF Reset          Self Reset        01  Service
Jun 08 01:31:26 UTC 2013      SCF Reset          Self Reset        00  Service
Jun 08 01:31:26 UTC 2013      SCF Reset          Self Reset        03  Service
Jun 08 01:31:27 UTC 2013      SCF Reset          Self Reset        81  Service
XSCF>

 

This solution has no attachment