Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1000307.1
Update Date:2011-03-01
Keywords:

Solution Type  Sun Alert Sure

Solution  1000307.1 :   Sun StorEdge 3310 Controller With Firmware 3.66 Cannot Cross-Load With 3.25 Firmware  


Related Items
  • Sun Storage 3310 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Data Loss
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
200424


Product
Sun StorageTek 3310 SCSI Array

Bug Id
<SUNBUG: 6256504>

Date of Workaround Release
09-JUN-2005

Date of Resolved Release
12-JUL-2006

Impact

When attempting a hot-swap operation on a Sun StorEdge 3310 Controller with firmware 3.66, the automated firmware cross-load function may not complete properly. The settings may not get transferred correctly, and the new controller would be unusable. Access to data on logical disks assigned would be adversely affected, and may result in data corruption.


Contributing Factors

This issue can occur on the following platform: 

  • Sun StorEdge 3310 controller with firmware 3.66

Note: This issue is only seen where a SCSI RAID controller FRU with 3.66 firmware is inserted in a dual RAID controller 3310 as a replacement in a hot-swap operation.


Symptoms

Replacement of a dual controller for the SE 3310 in this situation could have one of the following results:

(1) the new controller would not cross-load:

    Primary controller serial number: 4710
   Redundancy mode: Active-Active
   Redundancy status: Scanning
   Secondary controller serial number: 0

2) the new controller would not cross-load, but may work:

    Primary controller serial number: 4710
   Redundancy mode: Active-Active
    Redundancy status: Enabled
    Secondary controller serial number: 0   

(3) the new controller would cross-load, and may even work, but after about 10 minutes the server will panic because of an issue on a filesystem belonging to the new controller's LUN:

    alloccgblk: can't find blk in cyl, pos:0, i:253, fs:/bb bno: 0

Workaround

Single Controller Environment:

This issue does not affect the Single Controller units, as 3.66 firmware is not supported. The current procedure in a single RAID controller environment is to downgrade the firmware to 3.25, and has already been documented.

Dual Controller Environment:

The following scenario assumes that the 3310 has one surviving controller, and the end user received a RAID controller with 3.66 BEFORE THE FIX HAS BEEN PUT IN PLACE. Also, a serial port connection is required to set the IP address in order to perform this procedure out of band:

  1. Stop all I/O to the array and unmount any filesystems or volumes mounted from the array
  2. Power off the RAID enclosure unit
  3. Remove the surviving RAID controller (physically pull out the RAID controller)
  4. Insert the FRU RAID controller
  5. Connect the serial port
  6. Power ON the unit and wait until it is initialized
  7. Set the IP address of the FRU to the desired number
  8. Power up the host (the host does not have to be physically connected to the RAID unit, as this is being done out of band)
  9. Invoke sccli out of band (<sccli> <IP Address>)
  10. Execute "reset nvram" (This resets the NVRAM structure)
  11. Execute "reset controller" (This resets the controller, and ensures a proper NVRAM reset)
  12. Remove the FRU RAID controller
  13. Insert the original surviving RAID controller
  14. Make sure original RAID controller initializes
  15. Manually insert the FRU RAID controller

Resolution

The manufacturing process to remedy this issue for 3310 controllers has been completed. In rare cases where existing systems may experience this issue, please see the "Workaround" section above for the resolution to this issue.



Modification History
Date: 12-JUL-2006

12-Jul-2006:

  • Updated Resolution section
  • State: Resolved.


Previously Published As
101729
Internal Comments


The root cause of the issue is the difference in the NVRAM structure between 3.25 and 3.66 firmware. Since the RAID controllers were downloaded from 4.11 to 3.66, a manual step was required to reset the NVRAM and reset the controllers prior to shipment. Unfortunately this was not done properly but in now corrected.



Note: A purge has been issued for all 3310 controller FRU's to resolve the problem with the corrupt firmware. The purge is now completed.


Internal Contributor/submitter
Uri.Yifrah@sun.com

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
Uri.Yifrah@sun.com

Internal Services Knowledge Engineer
david.mariotto@sun.com

Internal Escalation ID
1-8417956

Internal Sun Alert Kasp Legacy ID
101729

Internal Sun Alert & FAB Admin Info
Critical Category: Data Loss
Significant Change Date: 2005-06-09, 2006-07-12
Avoidance: Workaround
Responsible Manager: null
Original Admin Info: [WF 12-Jul-2006, Dave M: we were not notified that this had been fixed. Rerelease as Resolved with Workaround only]
[WF 09-Jun-2005, Dave M; final comments OK from Raj, send for release]
[WF 06-Jun-2005, Dave M; sending for review]
[WF 01-Jun-2005, Dave M; post-holiday, waiting for BU approval, got some clarifications from submitter, still not finished]
[WF 26-May-2005, Dave Mariotto: Start Draft]
Product_uuid
3db30178-43d7-4d85-8bbe-551c33040f0d|Sun StorageTek 3310 SCSI Array

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback