Fujitsu SPARC M12-1
 
Fujitsu SPARC M12-2
 
Fujitsu SPARC M12-2S
 

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: M12-upset_xscfu

Fujitsu error codes:

01023001, 01023002, 01030003, 01024013, 01024014, 01040015,
01040016, 0186FFFE, 0186FFFF, 01A10002, 01A10003, 01A10009,
01A10027, 01AB0100, 01B80001, 01B80003, 01E40001

Details

Type

Hardware Fault

   upset_xscfu

Severity

Major

Description

A hard-to-diagnose failure of the XSCF occurred.

Failure types that are detected:

- unexpected failover 01A10002, 01A10003 the standby XSCF took over control and became the active XSCF, without an organized handover of
control from the active XSCF. This problem can only occur in M12-2S systems.

- process timeout: 01023001, 01023002, 01030003, 01A10009, 01B80003 during either XSCF startup or during the transition from XSCF standby state to XSCF active state, the XSCF "dual" process detected that one of the processes that it monitors did not start up correctly.

- process down: 01024013, 01024014, 0186FFFE, 0186FFFF an XSCF process either went down or dumped core, due to what is most likely and XSCFU hardware problem.

- Watchdog timeout: 01040015, 01040016 an XSCF encountered watchdog timeout, due to what is most likely and XSCFU hardware problem.

- Internal_error: 01A10027 an XSCF found its internal data inconsistent. This can be a result of firmware bug or any hardware failure.

- Selfcheck error: 01E40001 an XSCF found abnormality as missing file(s) on (u)SD card located on MBU/XSCFU or XSCFUX is/are found by selfcheck. This can be a result of firmware bug or any hardware failure. Note: Selfcheck error will not create any SNMP, mail or ASR events.

- Communication error: 01023001 an XSCF found communication error between XSCFs. This can be a result of firmware bug, contact problem of Dual cable or BB control cable, or any hardware failure.

- Spurious error: 01AB0100 an XSCF received error notification from hardware, but no detail can be obtained. This can be a result of firmware bug or any hardware failure.

- Firmware update: 01B80001 an XSCF faced failure while processing firmware update. This can be a result of corrupted update image, firmware bug or hardware failure in an XSCF.

This fault may occur either due to a hardware problem or a software problem on an XSCF.

NOTE:

For a XB-Box, XSCF function is on the XSCFUX.

Automated Response

If the failure is an unexpected failover: No immediate action is taken.

If the failure is a process timeout, process down, or watchdog timeout: The XSCF that detected the problem reboots. For M12-2S systems, if the XSCF that detected the problem is the active XSCF, then the standby XSCF will likely take over as the active XSCF.

If the failure is selfcheck error: The XSCF that detected the problem may keep running, but can create unexpected behaviour. Replacing the suspect FRU is recommended because firmware with missing file(s) may not be able to complete a firmware update correctly.

In all cases, the platform administrator should investigate the cause of the failure -- whether there was a hardware failure of the XSCF hardware or a software failure of the XSCF software.

Impact

Nothing is deconfigured.

Indicted Hardware

The XSCF is the 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