Asset ID: |
1-79-1537313.1 |
Update Date: | 2016-01-06 |
Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
1537313.1
:
M10-xscfu - A hardware problem has been detected with an XSCFU or PSUBP
Related Items |
- Fujitsu M10-4
- Fujitsu M10-1
- Fujitsu M10-4S
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
|
In this Document
Applies to:
Fujitsu M10-4S Fujitsu M10-1 Fujitsu M10-4 SPARC
Purpose
Provide additional information for message IDs:
011F0001, 01022002, 01030002, 01400001, 01040013, 01040014, 01040017, 01040018, 01040019, 0104001A, 01040201, 01040301, 01041001, 01041002, 01048001, 01048002, 01048003, 01048004, 01048005, 01048006, 01048007, 01048010, 0192ffff, 01B80001, 01B80002, 01C10001
Details
Type
- Hardware Fault
- xscfu
Severity
- Major
Description
-
Hardware problem detected with an XSCFU or PSUBP (M10-4/M10-4S).
The hardware problems that can be detected are:
- rtc error - Problem detected reading or writing the RTC (Real Time Clock) on an XSCFU; - rtc_battery - Low battery detected on the RTC (Real Time Clock) on an XSCFU; - int_lan error - Problem detected on the LAN interface of this XSCFU; - int_lanif error - Problem detected on the LAN interface between the two XSCFs on a BB (Building Block) system. This problem is detected by any XSCFs, which are on CMULs or XSCFUXs. If the problem is detected on the slave XSCFU, the fact the problem exists will be communicated to the active XSCFU and the active XSCFU will generate the event; - int_serial error - Problem detected on the serial interface of this XSCFU; - int_serialif error - Problem detected on the serial interface between the two XSCFUs on a BB (Building Block) system. This problem is detected by either the active XSCF or the standby XSCF, which are on Building Block#00 or #01, or on XB-Box#80 or #81. If the problem is detected on the standby XSCFU, the fact the problem exists will be communicated to the active XSCFU and the active XSCFU will generate the event; - flash - Problem detected writing to flash memory during flashupdate. - SSD : 01040019 Problem detected while accessing SSD chip on PSUBP (for M10-1 / 4 / 4S) or XSCFIFU (for XB-Box). - uSD: 0104001A Problem detected while accessing uSD chip - system backup memory fault on PSUBP for M10-4/M10-4S
Automated Response
- For problems with the LAN interface and serial interface between the active XSCF and standby XSCF, failover from the active XSCF to the standby XSCF is disabled, and no communication between the XSCFs will take place.
For problems with the LAN interface between the active XSCF and slave XSCFs, no communication between the XSCFs will take place.-
For problems with flash memory, the flashupdate procedure is aborted.
For problems with SSD or uSD, XSCF firmware may crash and reboot. When the crashed XSCF is the master XSCF, and when the standby XSCF is available, the standby XSCF will become master XSCF.
If this failure is permanent, the XSCF may not be able to recover. If this is the case, the XSCF will stop with the check LED lit.
Impact
- For a low battery condition on the RTC battery, if there is only a single XSCF in the configuration, the XSCF will continue to run until the platform is powered down. However, the platform will not be able to be powered up (the platform becomes unbootable).
For a low battery condition on the RTC battery, if this is a redundant XSCF configuration, the XSCF will fail over to the standby XSCF and the faulty XSCF will be deconfigured. For an RTC error, if there is only a single XSCF in the configuration, the XSCF will be powered down and the platform will become unmanageable. For an RTC error, if this is a redundant XSCF configuration, the XSCF will fail over to the standby XSCF and the faulty XSCF will be deconfigured. For problems with the LAN interface and the serial interface between the active XSCF and the standby XSCF, the standby XSCF is deconfigured (XSCF failover will not be allowed). For problems with the LAN interface between the active XSCF and the slave XSCF, the slave XSCF is deconfigured (XSCF failover will not be allowed). For problems with flash memory, nothing is deconfigured.-
For problems with SSD or uSD, nothing is deconfigured unless the problem is permanent. (If it is permanent, the affected XSCF will stop)
Indicted Hardware
- For problems related to the RTC, the RTC battery, or flash memory, the XSCF is marked for replacement.
For problems with the LAN interface and the serial interface between the active XSCF and standby XSCF, both XSCFs are equally likely to be at fault. However, the standby XSCF is easier to replace, so the standby XSCF is the first suspect on the suspect list and the active XSCF is the second suspect on the suspect list. For problems with the LAN interface between the active XSCF and slave XSCFs, both XSCFs are equally likely to be at fault. However, the slave XSCF is easier to replace, so the slave XSCFU is the first suspect on the suspect list and the active XSCFU is the second suspect on the suspect list.
For problems with the uSD, the XSCF is the suspect.
As the uSD card on the XSCF board may be broken, it is not recommended to move the uSD card from original CMUL/MBU/XSCFUX to the new CMUL/MBU/XSCFUX when this failure is detected.
For problems with the SSD, the PSUBP (for M10-1 / 4/ 4S) or XSCFIFU (for XB-Box) is the first suspect. The second suspect is the CMUL (for M10-4 / 4S) /MBU (for M10-1) / XSCFUX (for XB-Box).
For M10-1 systems, XSCF function is on the MBU. For M10-4/4S systems, XSCF function is on the CMUL. System backup memory is on PSUBP. For a XB-Box, XSCF function is on the XSCFUX.
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)

Attachments
This solution has no attachment
|