Sun Storage 6320 System
 
Sun Storage 6120 Array
 

GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
 
GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
 

On Sun StorEdge 6120 RAID array and (SE) 6320 systems, attempts to make configuration changes to volume groups when there are more than 8 volumes in the group may fail and may also cause the RAID controller to go offline.

This issue can occur on the following platforms:

• Sun StorEdge 6120 array with firmware 3.1.5

In conjunction with:

• Sun StorEdge 6320 system with (baseline) firmware 1.2.4

Note: SE 6320 system versions prior to 1.2.4 and SE 6120 array firmware versions prior to 3.1.5 are not affected by this issue.

The RAID controller may go offline upon attempting to add a 9th volume into a volume group, either via the GUI or via Sun StorEdge Configuration Service (SSCS) and the operation will fail to complete. At the CLI you may receive an application error, and on the WebUI you will be asked to contact your system administrator. (The RAID controller which is acting as the master may go off line but can be re-enabled after the takeover by the alternate master).

Note: Other unspecified manipulations of the storage configuration may produce similar symptoms.

To work around the described issue (until firmware versions on BOTH the 6120 and 6320 can be upgraded as shown in the "Resolution" section below), follow one of these options:

a) If not using version 1.2.4, do not upgrade to 1.2.4

b) If you have already upgraded to 1.2.4:

- avoid manipulating volumes if you have 8 volumes or greater, and do not create more than 8 volumes

or

- downgrade to version 1.2.3.2 for the SE 6320 system (which includes firmware 3.1.4) or for StorEdge 6120 downgrade to firmware 3.1.4.

To downgrade the firmware version on the SE 6320, follow these steps:

1. Connect to the GUI with the appropriate hostname (http://hostname:<xxxx>) and login with your hostname, ID and password.
2. Click on the "Monitor" tab
3. Click on the "Monitor Devices" link
4. Click on the "Clear All Alerts"
5. Click on the "Manage" tab
6. Click on the "Service" link
7. Click on the "Inventory Maintenance" link, then click on "Generate New Inventory" to generate the up-to-date inventory list of the system. When it is completed, click "Save New Inventory" to update your list.
8. Click on "Revision maintenance" link, then click on "Create New Patch Report". Wait until the Step 2 "Select Patches" becomes "clickable" (You can tell the status by looking on "Patch Report Status"). When the "Select Patches" link is available, click it. You will see all available patches for your SP and 6120.
9. Mark under "select patch category" patch 115179-11, then click "Apply Selected" (Note: Please do not click on the "Apply All Devices").

Note 1: Please allow ample time for the patch to be applied, as the array configurations for the 6320 may vary. Also check to make sure that the 3.1.4 FW has been properly loaded for each array domain.

Note 2: IMPORTANT! During the update process, DO NOT FOLLOW results of the Patch Report Status, as it will be in a constant "RUNNING" state. Click "Show Log" and wait until you see a message that indicates the patch has completed installation.

This issue is resolved on the following platforms:

• Sun StorEdge 6120 array with firmware 3.1.6

in conjunction with:

• Sun StorEdge 6320 system with (baseline) firmware 1.2.5

Note: These firmware revisions share mutual dependencies specific to the System Processor. Both of these specific revisions must be installed to resolve this issue, and if upgrading to later versions, both must be upgraded according to specifications.

For more information on all 6920 procedures (and using the sscs(1M) commands), please see the "Sun StorEdge System Getting Started Guide" at http://docs.sun.com/app/docs?q=sscs and the "Sun StorEdge System 6920 Release Notes" at http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-5229-14.pdf

19-Oct-2005:

• Updated Contributing Factors and Resolution sections, re-release as Resolved

This solution has no attachment