XSCF monitor log warning 'PCI access error' is indicative of a Solaris diagnosed FMA fault ( FMD-8000-11 ).

Asset ID:	1-75-1472913.1
Update Date:	2012-08-16
Keywords:

Solution Type Troubleshooting Sure

Solution 1472913.1 : XSCF monitor log warning 'PCI access error' is indicative of a Solaris diagnosed FMA fault ( FMD-8000-11 ).

Applies to:

Sun SPARC Enterprise M4000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M8000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M9000-32 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M5000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M9000-64 Server - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Purpose

This document is intended to explain how to troubleshoot the XSCF monitor log warning message, "PCI access error".

Troubleshooting Steps

The warning message, "PCI access error", appearing in the XSCF monitor log (showlogs monitor) is indicative of a FMA detected fault on the domain.

Example:
Oct 22 16:31:22 xscf0 Warning: /IOU#3/PCI#0:DOMAIN:PCI access error

The monitor log message is accompanied by an XSCF FMA message of, FMD-8000-11 - Solaris Fault Manager unable to determine message summary

This indicates that the XSCF FMA failure dictionary does not contain a corresponding match for the FMA event detected on the domain. This is expected behavior.

fmdump -v output can be used to confirm the same FRU location (PCI adapter slot) as noted by the monitor log warning.

Example:
TIME UUID SUNW-MSG-ID
Oct 22 2011 07:31:22 1de9aa7a-fabc-45f2-8528-e31446233417 FMD-8000-11
100% fault.io.pciex.device-interr-corr

        Problem in: hc://:product-id=SUNW,SPARC-Enterprise:server-id=host:chassis-id=AKD1153109/chassis=0/ioboard=3/hostbridge=0/pciexrc=0
           Affects: -
               FRU: hc:///component=iou#3-pci#0
          Location: -

fmdump -V (upper case V) output can be used to determine the detecting domain (detected-by) and corresponding solaris-uuid of the domain FMA event.

Example:
TIME UUID SUNW-MSG-ID
Oct 22 2011 07:31:22.857982000 1de9aa7a-fabc-45f2-8528-e31446233417 FMD-8000-11

detected-by = DID#5
solaris-uuid = 1ffb591e-9880-c33d-ef7b-b2f745a669ec

Solaris is responsible for detecting IO faults of this type. Diagnosis must be made via domain FMA data (e.g., fmadm faulty, fmdump). Match the solaris-uuid event found with the above technique to the domain FMA event. The FMA code of the Solaris event can then be researched in My Oracle Support. XSCF (service processor) data alone is insufficient for diagnosis.

When opening a case for Oracle diagnosis please provide domain explorer. See DocID 1312847.1. The Oracle engineer will use the domain FMA data to make the diagnosis.

Attachments

This solution has no attachment