Sun Storage Flexline 380 Array
 
Sun Storage Flexline 240 Array
 
Sun Storage Flexline 280 Array
 
Sun Storage 6540 Array
 
Sun External I/O Expansion Unit
 

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

Certain Sun StorageTek CSM200 X-Option trays are shipped with an existing DACstore (array metadata), resulting in one or more of the following conditions:

- Loss of management and data access

- Inability to apply feature licenses

- Inability to upgrade firmware

- Component details showing up incorrectly or receiving alarms

- Host operating systems reporting the wrong product identifier, array registration or discovery (may hang or fail to complete)

- Issues with multipathing failover 

This issue can occur on the following platforms:

• Sun StorageTek CSM200 Expansion Tray for 6130, 6140 and 6540 Storage Arrays
• Sun StorageTek CSM200 Expansion Tray for FLX240, FLX280 and FLX380 Storage Arrays

when either of the following conditions are met:

- CSM200 Expansion Tray X-Options are added to the array with the RAID module powered off

- CSM200 trays and associated drives that may have been pre-configured prior to shipping

The most prominent symptom is that an affected storage array appears to the management interface or data host inquiry as a 6140 or CSM200_R instead of 6130, 6540, 6140, or FLX240, FLX280, FLX380, CSM100_R, or OPENstorage.

- CSM100_R_FC is the 6130 Array

- FLEXLINE 380 is the Flexline 380 or Sun StorageTek 6540 Array

- OPENstorage D280 is the Flexline 280 Array

- OPENstorage D240 is the Flexline 240 Array

To confirm this symptom, a comparison must be made between the Controller Board ID, Product ID, and NVSRAM version.

For Common Array Manager (CAM):

1. Use the Troubleshooting-> FRUs-> Controllers-> Controller Name link to get the entry for the Board ID field.

2. Compare that to the output of option 1 of "csmservice -s" for the NVSRAM loaded. Example "csmservice -s" option 1 output (see Section 4 for command path):

    Enter your selection 0 - 6: 1
    Analyzing array ... Please wait ...
    Controller: CSM200_R - Version 06.19.25.10
    NVSRAM: N399X-619843-004

For SANtricity Storage Manager(SANtricity):

Use the Controller Menu-> Properties, and compare the Board ID to the NVSRAM loaded. NVSRAM is identified by a standard format of Nxxxx-xxxxxx-xxx. The first and second field of the NVSRAM version, "Nxxxx-xxxxxx", should match the Board ID and Product ID as follows:

N288X-619855 should have a board ID of "288x" and a Product ID of OPENstorage D240

N2882--619843 should have a board ID of "2882" and a Product ID of CSM100_R

N399X-619843 should have a board ID of "3992" or "3994" and a Product ID of CSM200_R

N6091-619843 should have a board ID of "6091" and a Product ID of FLEXLINE 380

N588X-619855 should have a board ID of "5884" and a Product ID of OPENstorage D280

Other symptoms may include:

• Alarms or alerts are generated for drive channels degraded on FLX380 or 6540 arrays, where the array channels shown are 1, 1, 1, 2, and should be 1 through 4 for each tray. This causes a false display and false alarm in the management interface.
• Loss of access to the array, and the controller 7-Segment LEDs show a constantly changing letter and number combination instead of a stable number. This indicates a controller boot loop.
• The IP address on the controller is wrong or has been changed.
• CAM cannot register the array.
• Firmware updates fail when done via CAM.
• Feature Enabler Identifiers are duplicated in SANtricity/CAM, preventing the addition of Feature Licenses.
• Array WWN changes (can cause loss of access within SAN switch zoning).

The corrective action requires a service interruption.

Note: This issue is documented in the STK6540 Release Notes at http://docs.sun.com/source/819-6521-14/6540_Release_Notes.html  on pgs 16-17. However, the workaround mentioned in the Release Notes does not work (no -p option with csmservice).

For any addition of new CSM200 expansion trays to an existing array in a production or active environment, cable and add the trays while the RAID Controller Module is powered on. The issue will be avoided altogether.

For new installations of RAID Controllers plus expansions, or for systems that have no data on them but match the symptoms above:

1. Register the RAID head and check for the correct NVSRAM revision. If incorrect, continue to step 2.

2. Reload the correct NVSRAM. For CAM 5.1 and above, use "csmservice -s".

Solaris Location:

/opt/SUNWstksm/bin/csmservice

/var/sadm/swimages/<array_model>/CRM-F-NVSRAM/image.fw

Windows Location:

%Program Files%\Sun\Common Array Manager\Component\SunStorageTekSoftwareManager\bin\csmservice

%Program Files%\Sun\Common Array Manager\Component\SunStorageTekSoftwareManager\<array_model>\CRM-F-NVSRAM\image.fw

Linux Location:

/opt/sun/cam/private/csmservice

/opt/sun/cam/share/fw/<array_model>/CRM-F-NVSRAM

For SANtricity:

Use the Advanced Menu-> Maintenance-> Sub-menu-> Download Sub-menu-> Download NVSRAM

The NVSRAM files are located on the SANtricity CD-ROM Shipped with the unit.

3. Reset the configuration. For CAM, use the "Reset Configuration" button under the "Administration" menu tree for the array name.

4. Verify that the NVSRAM version is correct and the product ID strings have been corrected on the array. For CAM, you will need to remove and re-register the array to pick up the product ID correctly.

Notes:

1. All corrective actions for this issue require loss of host access to the array during the NVSRAM update, due to the boot cycle of the array controllers. An outage will be required.
2. Some corrective actions require a configuration reset and restore of the affected array. It is recommended that backups of the data on the affected array be up to date.

CSM200 Expansion trays packaged in at the factory after August 29, 2007 no longer have this issue due to a change in the manufacturing process, ensuring that the drives enclosed no longer contain any system data.

Customers choosing to migrate drives or trays from a Sun StorageTek 6140 array to another array that supports the CSM200 trays are still exposed to this issue, if performed while the RAID Controller Module is powered off. A "Best Practice" recommendation is to involve Sun Support Services for any type of drive or data migration between arrays, due to the symptoms and resolutions described in this alert.

• Update Synopsis, Impact, and Contributing Factors sections

• Updated Relief/Workaround section

This solution has no attachment