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

Asset ID: 1-72-1489631.1
Update Date:2012-10-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1489631.1 :   Upgrading a Sun Storage 6140 Array to a Sun Storage 6180 Array May Create a Non-Compliant Slot Alarm.  


Related Items
  • Sun Storage 6140 Array
  •  
  • Sun Storage 6180 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
  •  


Upgrading array hardware from a Sun Storage 6140 to a Sun Storage 6180 may lead to the array that believe too many expansion trays are attached.

In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-6004376391>

Applies to:

Sun Storage 6180 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6140 Array - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

The problem described in this document is specific to a Sun Storage 6140 array being upgrading to a Sun Storage 6180 array by controller replacement.  There are two possible symptoms that may arise from this upgrade, depending on the Firmware version of the new controllers:

  • For controllers with 7.77.xx.xx or lower, you may see a Non-compliant slot limit alarm (90.66.1368).
  • For controllers with 7.80.xx.xx firmware, you will see non-compliant drives.
While it is possible for this error code (xx.66.1368) to be seen in any 25x0/25x0M2/6130/6x80 array, all other instances would be created by exceeding the maximum number of supported trays for that array. 

 

The first symptom is covered in this document.  If you encounter the second, please refer to Document  1471865.1 Upgrading Existing Storage Hardware to a Sun Storage 6x80 Array Running Firmware 7.80.xx.xx May Cause Existing Drives to Become Incompatible for the proper resolution.

The net affect of this alarm (90.66.1368) is that the configuration changes to the array are disallowed, until the issue is resolved.  In the meantime, all other array functions will behave as normal.

Changes

Upgrading the controllers in a Sun Storage 6140 array with 2 host ports per controller to a Sun Storage 6180 array that also has 2 host ports per controller. The Non-compliant slot limit alarm will not be seen when upgrading to a Sun Storage 6180 array that has 4 host ports per controller.

Cause

Depending on the controller type, the array has a different maximum tray support limit:

  • Sun Storage 6140/6180 array with 2 host ports per controller support up to 3 expansion trays.
  • Sun Storage 6140/6180 array with 4 host ports per controller support up to 6 expansion trays.

There are 3 supported upgrade paths from a Sun Storage 6140 to a Sun Storage 6180 array:

  • Sun Storage 6140 array with 2 host ports per controller to Sun Storage 6180 array with 2 host ports per controller.
  • Sun Storage 6140 array with 2 host ports per controller to Sun Storage 6180 array with 4 host ports per controller.
  • Sun Storage 6140 array with 4 host ports per controller to Sun Storage 6180 array with 4 host ports per controller.

Upgrade from Sun Storage 6140 array with 4 host ports per controller to Sun Storage 6180 array with 2 host ports per controller is not supported.

Only the first path above is known to create this alarm after an upgrade.  The new array mistakenly thinks that the previous array supported 6 expansion trays and generates the error because it does not.

Solution

Gather a supportdata, see Document  1002514.1 Collecting Support Data for Arrays using Sun StorageTek Common Array Manager, and open a Service Request for the proper resolution to this problem.

 

Oracle Internal Only

For TSC L1

  1. Please open a collaboration to L2.

For TSC L2

  • For customers who have not yet attempted the upgrade, find out the Firmware version on the new controllers before proceeding to avoid CR 717552.
  • For customers that have the incompatible drive problem, controllers running 7.80.xx.xx firmware, please see the Internal Only section of Document 1471865.1.
  • For customers that have successfully completed the upgrade but have a 90.66.1368 alarm:
  1. If the customer has any Premium Licenses, verify customer has valid keys for those features.
    1. Without removing the existing licenses, install the license keys again.
    2. If successful, proceed to step 2.
    3. If unsuccessful, Use the NetApp License Website to have the keys regenerated and then confirm their validity.
  2. Have the customer schedule an outage for 30 minutes.
  3. Log into one of the array controllers and execute a safeSysWipe from the shell.
  4. Re-install the Premium Licenses.
  5. Within 5 minutes the 90.66.1368 alarm should clear.
NOTE: Remapping of the volumes should not be needed.

 Reference <Bug 7193105> Upgrades from 6140 to 6180 Lite (Board ID 4980) will create a 90.66.1368 alarm

 


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