Fujitsu M10-4S - Using Diagxbu to Find Loose or Mis-Cabled Fiber Cable Building Blocks

Asset ID:	1-71-1557937.1
Update Date:	2013-06-10
Keywords:

Solution Type Technical Instruction Sure

Solution 1557937.1 : Fujitsu M10-4S - Using Diagxbu to Find Loose or Mis-Cabled Fiber Cable Building Blocks

Applies to:

Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

In a M10-4s multiple building block configuration, all the fiber cables can make troubleshooting them very complex.
It is very hard to locate loose or crossed cables

Solution

If the LSB is allocated to a ppar the associated ppar must be powered off.

On the main XSCFU, use the diagxbu command to find loose, missing, or crossed cables. Please see the examples below.

TEST #1
----------------------------
No cables pulled , normal results

XSCF> diagxbu -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120....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.....780.....-
810.....840.....870.....900.....930.....960.....990.....1020.....1050.....-
1080....end
completed.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90.....120.....150.end
completed.

*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".
XSCF>

NOTE: It took about 16 minutes for the test to run normally with no errors on my lab 2 BB M10-4s configuration

TEST #2
-------------
Pulled cable from XBBOX#80 XBU1 L1 Pink (Pulling black cable = same error)

XSCF> diagxbu -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120.....150end
XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120end
A Hardware error occurred by XBU diagnosis.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90.end
completed.
A hardware error occurred. Please check the error log for details.

*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".
XSCF>
XSCF> showlogs -r -M error
Date: May 29 12:03:38 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 12:03:34.409 PDT 2013
    FRU: /BB#1/XBU#0/CBL#1L
    Msg: Cable connection test failure
Date: May 29 12:03:30 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 12:03:25.288 PDT 2013
    FRU: /BB#1/XBU#0/CBL#1L
    Msg: Cable connection test failure

NOTE: It took about 8 minutes for the test to find the error and then exit on my lab 2 BB M10-4s configuration

TEST #3
-------------
Pulled cable BB#00 XBU#0 0L Black (Pulling Pink cable = same error)

XSCF> diagxbu -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120.....150end
XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120end
A Hardware error occurred by XBU diagnosis.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90....end
completed.
A hardware error occurred. Please check the error log for details.

*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".

XSCF> showlogs -r -M error
Date: May 29 10:57:30 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 10:57:19.439 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 10:57:24 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 10:57:19.073 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure

TEST #4
-----------------------
Pulled cable XBBOX#81 XBU#0 0L black (Pulling Pink cable = same error)

TEST #5
-----------------------
Reversed(crossed) 2 cables on BB#0 (XBU#0 0L Black and XBU#0 0L Pink)

XSCF> diagxbu -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120.....end
XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120.end
A Hardware error occurred by XBU diagnosis.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90..end
completed.
A hardware error occurred. Please check the error log for details.

*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".

XSCF> showlogs -r -M error
Date: May 29 15:57:22 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 15:57:22.583 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 15:57:21 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 15:57:21.576 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 15:56:59 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 15:56:49.292 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 15:56:53 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 15:56:48.679 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure

TEST #6
-------------------------------------

Reversed(crossed) 2 cables on BB#0 (XBU#0 0L Black and XBU#1 0L Pink)

XSCF> diagxbu -b 0 -t 1
XBU diagnosis is about to start, Continue?[y|n] :y
Power on sequence started. [7200sec]
0..... 30..... 60..... 90.....120.....end
XBU diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120.end
A Hardware error occurred by XBU diagnosis.
Power off sequence started. [1200sec]
0..... 30..... 60..... 90..end
completed.
A hardware error occurred. Please check the error log for details.

*Note*
Please confirm the error of XBU by "showlogs error".
In addition, please confirm the degraded of XBU by "showstatus".
XSCF>
XSCF>
XSCF> showlogs -r -M error
Date: May 29 16:11:00 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:59.936 PDT 2013
    FRU: /BB#0/XBU#1/CBL#0L
    Msg: Cable connection test failure
Date: May 29 16:10:59 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:59.429 PDT 2013
    FRU: /BB#0/XBU#1/CBL#0L
    Msg: Cable connection test failure
Date: May 29 16:10:44 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:33.757 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 16:10:39 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:27.651 PDT 2013
    FRU: /BB#0/XBU#1/CBL#0L
    Msg: Cable connection test failure
Date: May 29 16:10:39 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:27.404 PDT 2013
    FRU: /BB#0/XBU#0/CBL#0L
    Msg: Cable connection test failure
Date: May 29 16:10:31 PDT 2013
    Code: 10000008-007cff0000ff0000ff-019204310000000000000000
    Status: Information            Occurred: May 29 16:10:26.494 PDT 2013
    FRU: /BB#0/XBU#1/CBL#0L
    Msg: Cable connection test failure

Attachments

This solution has no attachment