Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1537365.1
Update Date:2017-03-17
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1537365.1 :   M10-upset.xscfu - A hard-to-diagnose failure of the XSCF occurred  


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
Purpose
Details
References


Applies to:

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

Purpose

Provide additional information for message ID: M10-upset.xscfu

Fujitsu error codes:

01023001, 01030003, 01040015, 01040016, 0186FFFE, 0186FFFF,
01A10002, 01A10003, 01A10009, 01B80003

Details

Type

Hardware Fault
   upset.xscfu

Severity

Major

Description

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

Four types of failures 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 M10-4S systems.

- process timeout: 01023001, 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: 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.

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

NOTE:

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

For M10-4/4S systems, XSCF function is on the CMUL.

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 M10-4S systems, if the XSCF that detected the problem is the active XSCF, then the standby XSCF will likely take over as the active XSCF.

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)


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback