What Does "Diagnostic data has been captured by the array" Mean ?

Asset ID:	1-71-1673415.1
Update Date:	2017-07-17
Keywords:

Solution Type Technical Instruction Sure

Solution 1673415.1 : What Does "Diagnostic data has been captured by the array" Mean ?

Applies to:

Sun Storage 6580 Array - Version All Versions and later
Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 2530-M2 Array - Version Not Applicable and later
Sun Storage 2540-M2 Array - Version Not Applicable and later
Sun Storage 6180 Array - Version All Versions and later
Information in this document applies to any platform.

Goal

This document describes the meaning of the alarm "Diagnostic data has been captured by the array" which is also known as REC_DDC_AVAILABLE.

Solution

DDC (Diagnostic Data Collection) is a mechanism to capture sufficient diagnostic information about the controllers and array state at the time of an unusual event, and store the diagnostic data for later retrieval/transfer to Oracle support for further analysis.

Unusual events triggering DDC can be:

Ancient I/O (refer to <Document 1663839.1> Sun Storage 2500, 2500-M2 and 6000 Arrays May Reboot Due to Ancient I/O).
Master abort due to bad address accessed by the fibre channel chip results in PCI error.
Destination device number registry corruption.
EDC Error returned by the disk drives.
Quiescence failure of volumes owned by the alternate controller.

The DDC mechanism triggers the following actions:

MEL events (Major Event Log) logged whenever DDC logs are available in the system.
The amber LED is lit on the array and the following alarm is raised in CAM (Sun Storage Common Array Manager):

Alarm ID   : alarm132
Description: Diagnostic data has been captured by the array.
Severity   : Minor
Element    : ---hidden---
GridCode   : 57.66.1106
Date       : <date and time>

If the system contains batteries that are sufficiently charged, the DDC information is persistent across power cycles and controller reboots.

When DDC data are available in the array and the above alarm is returned in CAM, it is necessary to proceed with the following steps and attach the information to an Oracle Service Request:

Collect a new supportdata from the array. Please refer to the <Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays.
Collect the DDC:
- Using the CAM CLI (Command Line):
  1. Execute the following command on the CAM server:
    
    # service -d <arrayname> -c download -t ddc -p <location where to save the file> -o <filename>
    
    Where `service` is under:
    
    Solaris: /opt/SUNWsefms/bin/
    Linux: /opt/sun/cam/private/fms/bin/
    Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin\
- Using the CAM BUI (Browser User Interface):
  1. Log into CAM.
  2. Select the array under "Storage Systems" on the left pane.
  3. Click on "Service Advisor" on the top right.
  4. Go through "Array Troubleshooting and Recovery" -> "Collecting DDC Data".
After you successfully collected the DDC and Oracle support confirmed that the alarm can be cleared, you can follow the steps below:
- Clearing the DDC alarm using the CAM CLI:
  1. Execute the following command on the CAM server:
    
    # service -d <arrayname> -c reset -t ddc
- Using the CAM BUI (Browser User Interface):
  1. Log into CAM.
  2. Select the array under "Storage Systems" on the left pane.
  3. Click on "Service Advisor" on the top right.
  4. Go through "Array Troubleshooting and Recovery" -> "Clearing Diagnostic Download Flag".

References

<NOTE:1663839.1> - Sun Storage 2500, 2500-M2 and 6000 Arrays May Reboot Due to Ancient I/O
<NOTE:1002514.1> - Collecting Sun Storage Common Array Manager Support Data for Arrays

Attachments

This solution has no attachment