M10-upset_ppar.config - PPAR(s) cannot be configured successfully

Asset ID:	1-79-1537464.1
Update Date:	2015-12-31
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1537464.1 : M10-upset_ppar.config - PPAR(s) cannot be configured successfully

Applies to:

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

Purpose

Provide additional information for message ID: M10-upset_ppar.config

Fujitsu fault codes:

018A0010, 018A0020, 018A0030, 018A0031, 018AF041, 018AF042,
018AF061, 018AF062, 018AF063, 018AF064, 018AF065, 018AF067, 018AF0C0,
02000e05, 02002c00, 02002c01, 02002c02, 02002c03

Details

Type

: Hardware Fault; upset_ppar.config

Severity

: Major

Description

Upset due to the fact that PPAR(s) cannot be configured successfully.

The reasons that the PPAR(s) could not be configured:

- no-ppar: 018A0020 Either the system has no PPAR or all the PPARs in the system has been deconfigured due to a prior fault;

- no-lsb: 018A0010, 018A0030, 018AF041, 018AF042, 018AF061, 018AF062, 018AF067, 018AF0C0 Either the PPAR has no LSB or all the LSBs in the PPAR have been deconfigured due to a prior fault;

- no-mem: 018AF064, 018AF065 Either the LSB has no memory or all the memory in the LSB has been deconfigured due to a prior fault;

- no-cpu: 018AF063 Either the LSB has no CPU chip or all the CPU chips in the XSB have been deconfigured due to a prior fault;

- no-xb-for-ppar: 018A0031 Either the system does not have appropriate XB-Box or interconnect between BBs, which is required to form the PPAR, or is entirely deconfigured due to a prior fault;

- faulty-component: 02000e05 There is a component in the LSB that has been diagnosed as faulty, and the configuration rules for this domain do not allow LSBs with faulty components;

- no-mem-for-hv-for-bb:02002c00 The LSB does not have enough memory to start Hypervisor on the LSB by deconfiguration due to a prior fault;

- no-mem-for-hv: 02002c01, 02002c02, 02002c03 The PPAR does not have enough memory to start Hypervisor on the PPAR by deconfiguration due to a prior fault.

Automated Response

: No immediate action will be taken.

Impact

: Nothing is deconfigured.

Indicted Hardware

For no-mem-for-hv-for-bb event, a building block will be specified.

For other case, an affected PPAR will be specified.

Suggested Action for System Administrator

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