Sun Storage 2540-M2 Array
 
Sun Storage 2510 Array
 
Sun Storage 2540 Array
 
Sun Storage 6180 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage 6540 Array
 
Sun Storage 6580 Array
 
Sun Storage 6140 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-8914556241>

Applies to:

Symptoms

After replacing a controller, the controller is seen as Optimal, is working properly, and there are no symptoms of controller failure. However, the following alarm is reported under Sun Storage Common Array Manager (CAM):

In this example, Controller B has been replaced.

Cause

This can occur rarely after an actual error occurs and is corrected, and is due to an issue of the controllers becoming out of sync.

The alarms.txt file clearly indicates that the replaced controller (controller B in this example) was inserted running a different firmware than the running controller (controller A in this example). After ACS (Auto Code Sync) the controllers will run the same firmware. The running controller however may not update the failure list, causing stale data to remain in one of the controllers.

Solution

Ensure the controllers are indeed optimal. Refer to <Document 1021113.1> Sun Storage 2500, 2500-M2, 6000 and Flexline Arrays: Troubleshooting RAID Controller Failures.

• If any controller issue found, continue with the document above and skip this document.
• If the controllers are optimal, contact Oracle support to proceed further.

Internal notes for Oracle support engineer:

1. Collect the following shell commands output from BOTH controllers:
   
   
   -> loadDebug
   -> getRecoveryFailureList_MT
   -> unld “Debug”
   
   
   Important: The instructions in this document have to be used by an Oracle support engineer who received the required NetApp advanced training to access the shell. If you are not one of these engineers, you are not authorized to use these commands without guidance from one of these engineers. In that case, please open a collaboration SR with a TSC L2 engineer.

1. Check for stale data between the controllers. In the example below, Controller A is having stale information:
   
   
   ControllerA:
   
   -> loadDebug
   value = 0 = 0x0
   -> getRecoveryFailureList_MT
   1 Failures:
   ------------
    0 : Failure Type = 79 (REC_CTL_MISMATCH)
        ref = 070000000000000000000002
   
   value = 0 = 0x0
   -> unld "Debug"
   value = -1 = 0xffffffff
   -> exit
   
   ========================================================
   
   ControllerB:
   
   -> loadDebug
   value = 0 = 0x0
   -> getRecoveryFailureList_MT
   0 Failures:
   ------------
   
   value = 0 = 0x0
   -> unld "Debug"
   value = -1 = 0xffffffff
   -> exit

1. Reset the controller holding stale information (controller A in this example), and check the alarm in CAM after 10 minutes.

This solution has no attachment