Sun Storage 2540-M2 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage Common Array Manager (CAM)
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: ST25xx
 

Applies to:

Symptoms

Sun Storage Common Array Manager (CAM) reports the alarm type xx.66.1204 for "Tray.X.Drive.Y has DACstore data written by a later revision of firmware than exists on this array". Example:

If you collect a supportdata from the array and look at the file storageArrayProfile.txt, you will see the status "Incompatible" for the drives.

Example:

Please refer to <Document 1002514.1> Collecting Sun Storage Common Array Manager Array Support Data for the procedure to collect a supportdata.

Changes

This alarm can happen if a new Sun Storage 2500-M2 Array with the firmware 07.84.xx.xx is registered in CAM 6.9 without the following patches, and the user goes through the "Install Firmware Baseline" procedure to upload the firmware to the controllers.

Solaris SPARC:
147416-02 or higher: CAM 6.9 BUI Patch for Solaris on SPARC
147660-04 or higher: CAM 6.9 Firmware Patch for Solaris

Solaris x86:
147419-02 or higher: CAM 6.9 BUI Patch for Solaris on x86
147660-04 or higher: CAM 6.9 Firmware Patch for Solaris

Linux:
147418-02 or higher: CAM 6.9 BUI Patch for Linux x86
147662-03 or higher: CAM 6.9 Firmware Patch for Linux

Windows:
147417-02 or higher: CAM 6.9 BUI Patch for Windows
147661-03 or higher: CAM 6.9 Firmware Patch for Windows

Please refer to <Document 1526721.1> Minimum Sun Storage Common Array Manager (CAM) Release Supported with the Firmware (FW) 07.84.xx.xx.

Cause

New Sun Storage 2500-M2 Arrays are delivered with the firmware 07.84.xx.xx that has a new DAcstore which is not compatible with older firmware releases. When going through the "Install Firmware Baseline" procedure in CAM 6.9 without the above patches, CAM will push the firmware 07.80.xx.xx in place of 07.84.xx.xx on the array, and when both controllers reboot to activate the firmware, the process hang. If the array is power cycled, both controllers come back with the firmware 07.80 which cannot read the information from the DACstore on the drives. The array reports internal alarm that CAM converts to the event code 93.66.1204 for "Tray.X.Drive.Y has DACstore data written by a later revision of firmware than exists on this array".

Solution

 If you encounter this issue, please refer to <Document 1002514.1> Collecting Sun Storage Common Array Manager Array Support Data to collect a supportdata, and contact Oracle support.

Oracle Internal Only

For L1 engineers:

1. Open a collaboration with L2.

For L2 engineers:

1. Confirm that the customer's issue is related to this document.
2. If the issue is related to this document, please link the bug 16092250 to your SR and attach the supportdata to the bug.
3. Either use webex to remote connect to both controllers, or dispatch a field engineer onsite to execute "sysWipe" on both controllers. After the controllers reboot, the drives will have the DACstore revision 6 supported for 07.80, however if there was existing volumes, they will be deleted.
   
   
   If the telnet port is not enabled and if it is not posisble to enable it (when the array is in the state described in this document, it is probably not possible to enable the telnet port on the controllers) you will need to use the serial port to execute the above step 3.
    
4. Ensure to upgrade the customer's CAM server to 6.9.0_20 with all the platform and firmware patches as per the <Document 1296274.1> How to Download Common Array Manager (CAM) Software and Patches.
5. Upgrade the array to the latest firmware 07.84.xx.xx. Please refer to the <Document 1334718.1> Sun Storage[TM] 2540-M2 Firmware Matrix or <Document 1334754.1> Sun Storage[TM] 2530-M2 Firmware Matrix.

References

This solution has no attachment