Sun Storage 6580 Array
 
Sun Storage Common Array Manager (CAM)
 
Sun Storage 2540-M2 Array
 
Sun Storage 2510 Array
 
Sun Storage 6540 Array
 
Sun Storage 2540 Array
 
Sun Storage 6130 Array
 
Sun Storage 6180 Array
 
Sun Storage J4200 Array
 
Sun Storage J4400 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage 2530 Array
 
Sun Storage J4500 Array
 
Sun Storage 6140 Array
 

PLA-Support>Sun Systems>DISK>Disk Software>SN-DK: CAM
 

Provide details to decoding Event or Grid codes.

Applies to:

Goal

This document will explain the format of Event Codes seen in arrays managed by Sun Storage Common Array Manager (CAM) as well as how to extract more information from this code.

Solution

CAM alarms contain useful information about problems that a given array may be seeing.  One of the components of the alarm is the "Grid Code" (also seen as the event code in other forms of the alarm).  Here is a typical alarm with the Grid Code highlighted:

Using the Grid or Event Code, we can decipher additional information about a problem.  This code is arranged in 3 parts separated by periods.  In the example above, those parts are 63, 66 and 1023.  The first part is used to identify the Source.  The value of 63 equates to a Sun StorageTek 6540 array (other possibilities are listed in the first table below).  The second part is the Event Type.  The value of 66 equates to a "ProblemEvent" (other possibilities are listed in the second table below).  And the last part is a Description of the Event Type.  The complete list of possible values for these Descriptions is too large for this document as well as the Description itself is self evident.

INTERNAL ONLY:

There are additional sources for arrays that CAM was supposed to support but never made it and should never be seen:

xx.66.9999 is a dummy GridCode which is returned by CAM each time it does not match the Fault ID from SYMbol to the array model. See for example <Document 1519083.1> Sun Storage Common Array Manager (CAM) Returns the Alarm with Event Code 93.66.9999 and Fault ID 434 for a Sun Storage 2500-M2 Array. 

Events that are not errors will not generate alarms.  For example, Revision Baseline Event indicates that the array is at the baseline.  As such, no further actions are needed.

Using the command ras_admin and the Grid Code, it is possible to obtain additional information about the failure, including the array type and what to do to resolve the problem:

Since ras_admin is only processing the Event Code and not an actual alarm, things like location will not match the actual alarm.  In this case, ras_admin has no idea which drive location actually failed and so it leaves a value in {}.  If there is more than one value, the subsequent instances will increment (1..2..).

This solution has no attachment