Fujitsu M10-4
 
Fujitsu M10-1
 
Fujitsu M10-4S
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
 

In this Document

Purpose

Details

References

Applies to:

Purpose

Provide additional information for message ID: M10-if.se-mbc-xscf

Fujitsu fault codes:

01400002, 018B0003

Details

Type

Hardware Fault

   if.se-mbc-xscf

Severity

Major

Description

Fault due to a serious error detected on the interface between an MBC chip and the XSCFU or XSCF function on MBU or CMUL.

This fault can occur on the interface between the currently active XSCFU and:

- an MBC chip on a MBU/CMUL;
- the TTY interface on an MBC chip on a MBU/CMUL;
- an MBC chip on an XSCFUX (for XB-Box);

For non-TTY-oriented faults, the maintenance bus between the XSCF and the MBC in question is disconnected. This means that the XSCF will:

- lose all I2C and JTAG access to chips and devices via the MBC chip;
- lose all DMA access to chips via the MBC chip
- lose all access to MBC registers;
- lose all ability to diagnose faults via the MBC chip

Additionally, if the failure is detected on MBC-CMU, and this is a non-TTY-oriented fault, then the XSCF will:

- lose all access to SRAM on the MBC-CMU chip;
- lose all use of the XSCF command interface using this MBCCMU chip.

For TTY-oriented faults, the TTY interface for this MBC-CMU chip becomes unusable.

NOTE:

For M10-1 systems, the XSCF is located on the MBU.

For M10-4 or M10-4S systems, the XSCF is located on the CMUL.

Automated Response

For M10-1 and M10-4 systems, if this is a TTY-oriented fault, then the domains lose access to the TTY interface and no further action is taken.

For M10-4S systems, if this is a TTY-oriented fault, then XSCF software will switch the TTY interface to another building block that belongs to the domain (if there is a working TTY interface on another building block in the domain). If there is no other building block with a working TTY interface in this PPAR, then the PPAR loses access to the TTY interface and no further action is taken.

If this is not a TTY-oriented fault, then no immediate action is taken.

In all cases, the platform administrator should schedule a service action.

Impact

For M10-1 and M10-4 systems, the platform becomes unbootable.

For M10-4S systems, a building block or XB-Box loses communication to the Master XSCF and is deconfigured.

Indicted Hardware

For M10-1 systems, the MBU is marked for replacement.

For M10-4 systems, the CMUL is marked for replacement.

For M10-4S systems without XB-Boxes, the CMUL, where slave XSCF is working, is the first suspect. The CMUL, where master XSCF is working, is the second suspect.

For M10-4S systems with XB-Boxes, the CMUL, where slave XSCF is working, is the first suspect. The XSCFUX, which is the master XSCF, is the second suspect

Suggested Action for System Administrator

The recommended service action for this event is to schedule replacement of the affected component(s) at the earliest possible convenience. Although the hardware may be functioning, it is not intended nor recommended that the faulted component(s) remain in the system for a prolonged period of time.

Refer to the following document for the latest procedures for displaying event content in preparation for submitting a service request and applying any post-repair actions that may be required.

PSH Procedural Article for Fujitsu M10 Diagnosis (Doc ID 1525156.1)

This solution has no attachment