Sun Storage 6540 Array
 
Sun Storage Flexline 280 Array
 
Sun Storage 6130 Array
 
Sun Storage 6140 Array
 
Sun Storage Flexline 240 Array
 
Sun Storage Flexline 380 Array
 

GCS>Sun Microsystems>Sun FAB>Standard>Reactive
 

Customer systems requiring movement of disk drives between any of the affected systems need careful planning to avoid problems related to "Dirty DACstore". These activities can be migration of drives to another system individually or by tray, to accomplish moving data, or simply adding capacity to an array.

Sun has facilitated the planning of drive migration by developing the Sun StorageTek Data in Place Migration Guide (hereafter called DIPM).

Data/Drive Migration will require:

1. An open Case/Service Request
2. A field engineer assignment to help the customer plan using the DIPM
3. Escalation into Tier 3/Backline/PTS to review the customer plan

The above listed Affected Platforms with any of the following tray types may be impacted by this service procedure:

CSM100_FC
CSM100_SATA
CSM200
FLA200
FLC200

• Requires Array firmware 06.19.23.XX or later to support all tray types
• Requires Sun StorageTek Common Array Manager (CAM) 5.1 or later
• Entire Tray migrations using Legacy FLA200, FLC200, or FLA300 trays where the destination array is managed by CAM, require a CAM version of 6.0 or later
• Requires SANtricity Storage Manager 09.19.G2.04 or later
• SANtricity is not supported for Sun StorEdge 6130 Arrays

Failure to follow and review the plans outlined in the DIPM can result in data loss, loss of access to the source and/or target array, service actions requiring lengthy outages and repair. Many of the documented symptoms in Sun Alert 103067 can and will occur.

When a drive tray is received with more than three drives with DACStore already present on the drives (dirty dacstore), the issue of pushing up the incorrect DACStore and NVSRAM to the controller exists. This can happen when the tray is attached to an array while it is powered off. Upon power up, the array controller scans all attached drives for sundry drives, and loads dacstore from the first set discovered. This can result in a mixed (merged) configuration when dirty trays are added to existing systems, or just a wrong (mismatched) configuration on "new" systems.

Service representative should follow the below steps when planning movement of disk drives between any of the affected systems.

1. Verify What Hardware is Being Moved.

You will need to know if:

* Only Drives are being moved, and if so, what link rates the drive can operate at. Then go to Step 2.

* Whole Trays are being moved, and if so, what link rates the trays can operate at. Then go to Step 3.

* If the Drives/Trays are being moved within the same array, and if so, whether there is a link rate change between trays.

2. Verify that the Drives Can Be Moved to the New Tray

For CSM200:

* CSM200 drives can only be changed between CSM200 trays

* 2Gb/s FC drives can only operate at 2Gb/s, and are otherwise bypassed. Make sure the link rate switch on the CSM200 is set appropriately.

* 4Gb/s FC drives can operate at any link rate

* 3Gb/s SATA drives can operate at any link rate

For CSM100_FC/FLA200/FLA300

* All drives are 2Gb/s Fibre Channel.

* Drives can only be changed between these tray types

For CSM100_SATA/FLC200

* All drives are 2Gb/s SATA

* Drives can only be changed between these tray types

3. Verify that the Tray can be managed Common Array Manager (CAM).

* CAM 5.1.x supports the 6130, 6140, and 6540 arrays using the CSM100 and CSM200 tray types only

* CAM 6.0 supports all Arrays and all Tray types, providing that the minimum firmware requirement is met(See Contributing Factors).

4. Use the Worksheet to identify the aspects of the Volumes, Virtual Disks, that exist on the Drives being Moved.

The DIPM can be found at below (Internal Only) URL;

http://pts-storage.west.sun.com/products/SE6130/documentation.html

Chapter 1 page 18, contains a worksheet to help you identify the volumes

There is no worksheet for the SANtricity Based Guide, but the CAM worksheet can be used.

5. Develop an Action Plan based on the Chapter

Chapter 2: Moving Drives/Trays to a new array for additional capacity (Data not preserved)

  Use this to move drive capacity to a new array. Requires destroying any Volumes or Vdisks on the drives being moved.

Chapter 3: Removing and Reinstalling a Virtual Disk (Data Preserved)

  Use this to move drives within the same array. Usually used to reorganize the drive layout across trays.

Chapter 4: Moving a Virtual Disk to a New Storage Array (Data Preserved)

  Use this to move just the drives in a given Vdisk to a target array with empty slots

Chapter 5: Move a Drive Tray to a new Storage Array (Data Preserved)

  Use this to move all drives in a single tray to a new storage array.

6. Collect Support Data for the Source and Target arrays.

Reference Infodoc 87242: Sun StorageTek [TM] 25xx/6130/6140/6540: How to collect supportData to troubleshoot array

7. Open an Escalation:

Open an escalation into Tier 3/Backline/PTS with:

* A Write Up of the proposed migration plan from Step 5
* Support Data from the Source Array
* Support Data from the Destination Array

The engineer engaged will review your plan against the support data contents and provide any feed back.

This will ensure that the Escalation engineer is engaged and knowledgeable prior to the execution of the approved migration plan.

• URL: http://pts-storage.west.sun.com/products/SE6130/documentation.html
• Other: Sun Alert 103067

This solution has no attachment