Sun StorageTek 6540 Array Release Notes, Release 6.2
This document contains important release information about the Sun StorageTek 6540 Array or information that was unavailable at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the Sun StorageTek 6540 Array.
These Release Notes cover the Sun StorageTek 6540 Array and related hardware issues. For information about the management software for the array, see the latest Common Array Manager Software Release Notes. The CAM release is currently version 6.2.0 and the latest firmware version is 07.15.11.11.
Also, make sure you look for the latest patches pertaining to your environment. Select Patches & Updates from the following site:
The Release Notes consist of the following sections:
This section describes the main features of the Sun StorageTek 6540 Array, including the following:
The Sun StorageTek 6540 Array is a 4-Gb/2-Gb/1-Gb Fibre Channel (FC) array that offers both direct attached and storage attached network (SAN) access. The Sun StorageTek 6540 Array includes the following features:
The Sun StorageTek 6540 Array is available in a 4-Gbyte-cache, an 8-Gbyte-cache, and a 16-Gbyte-cache configuration, compared in TABLE 1.
Auto Service Request (ASR) is a feature of the array management software that monitors the array system health and performance and automatically notifies the Sun Technical Support Center when critical events occur. Critical alarms generate an automatic Service Request case. The notifications enable Sun Service to respond faster and more accurately to critical on-site issues.
The Auto Service Request capability in Sun StorageTek Common Array Manager software allows you to register devices to participate in the ASR service. Refer to the Sun StorageTek Common Array Manager Release Notes, Release 6.2.0 or higher, for more information.
Controller firmware 06.19.25.10 or higher allows tray mixing of 6540, 6140 and 6130 array controllers modules and the Sun StorageTek CSM100, CSM200, FLA200, FLC200, and FLA300 Expansion Modules.
|Note - To add trays with data already on them, contact your service representative for assistance to avoid data loss.|
Refer to “Upgrading Firmware for Adding Expansion Trays” in the Sun StorageTek Common Array Manager Release Notes, v.5.1.3 or higher, for more information on the procedure to upgrade trays without data. Also refer to Best Practices for Adding Expansion Modules
TABLE 2 lists the supported expansion modules.
Only Sun Service should install expansion modules with data. Refer to the Sun StorageTek Common Array Manager Release Notes, Release 6.2.0 or higher, for more information about supported expansion modules by array.
When you add a new CSM200 expansion module to an existing array in a production or active environment, it is best practice to cable and add the trays while the RAID controller module is powered on, in order to avoid a variety of issues including those listed below.
Before connecting any replacement drive or additional expansion module to an existing functioning array, it is best practice to contact Sun Microsystems Support Services. One reason for this is to avoid issues related to DACstore, the configuration and status database maintained by the array firmware, that stores its information on each of the disk drives.
Contact Sun Microsystems Support Services promptly upon experiencing any of the following symptoms:
|Note - Because corrective actions for a DACstore issue may require a configuration restoration, it is important to maintain a current image of the configuration using the export function in the CAM command line or GUI (as of CAM 6.2). It is always a best practice to maintain recoverable backups of your data.|
The software and hardware products that have been tested and qualified to work with the Sun StorageTek 6540 Array are described in the following sections:
You must have Sun StorageTek Common Array Manager, v5.00 or later software. Current CAM Release 6.2.0, is recommended.
TABLE 3 lists the size, speed, and tray capacity for the supported FC and SATA disk drives in the Sun StorageTek 6540 Array.
This section describes supported data host software, HBAs, and switches.
You must install multipathing software on each data host that communicates with the Sun Storage 6540 Array.
For Solaris OS 8 and 9 data hosts, the multipathing software is part of the Sun StorageTek SAN Foundation Kit (SFK) software. Solaris OS 10 includes the multipathing software. For data hosts running the Solaris OS, follow the instructions in the Sun StorageTek 6540 Array Hardware Installation Guide to download and install the software from the Sun Download Center.
TABLE 4 lists supported multipathing software by operating system.
TABLE 5, TABLE 6, TABLE 7, and TABLE 8 lists supported HBAs and other data host platform elements by operating system.
HBAs must be ordered separately from Sun or its respective manufacturers. Sun HBAs can be ordered from:
You can download HBA drivers and other host software from the Sun Download Center, http://www.sun.com/software/download/.
Download operating system updates from the web site of the operating system company.
You must install the multipathing software before you install any OS patches.
|Note - The multipathing driver for the IBM AIX platform is VERITAS DMP, bundled in VERITAS Volume Manager 3.x for the Sun StorageTek 6540 Array. Download the Array Support Library (ASL) from http://support.veritas.com/.|
The enterprise software applications listed in TABLE 9 are compatible with the Solaris OS on the data host.
The following FC fabric and multilayer switches are compatible for connecting data hosts and the Sun StorageTek 6540 Array:
Host management software upgrades are described in the Sun StorageTek Common Array Manager 6.2.0 Release Notes. This section describes release-specific steps for firmware and driver upgrades that you must perform:
New firmware files are included in each release of the Sun StorageTek Common Array Manager software, currently Release 6.2.0. When you install new management software from CD or web download and perform the Upgrade Firmware function, the software will detect older firmware versions and prompt you to upgrade to the new firmware versions required for this release. It is not necessary to uninstall the existing firmware.
If the software detects that there is no earlier version installed, it will perform a complete new installation. The software is available on the Sun StorageTek Common Array Manager CD, or in the package you obtain from http://www.sun.com/storagetek/management_software/resource_management/cam/get_it.html.
TABLE 1 shows the firmware files relevant to CAM Release 6.2.0.
The 06.xx versions of firmware are online upgrades and customer installable.
The transition from 06.xx to 07.xx firmware is an offline upgrade requiring a service call to implement. Contact Sun Microsystems Support Services at: http://www.sun.com/contact/support.jsp.
While firmware 07.15.11.11 is bundled with CAM Release 6.2.0, it is still required to first update the 6540 and FLX380 arrays to 07.10.25.10 via a service call. Once the array firmware is at a version of 07.xx, you can perform an online upgrade of the firmware to the 07.15.11.11 version.
The following procedure applies only to 06 level firmware and firmware upgrades after the 07.10.25.10 upgrade has been installed by Sun Service. Using the Common Array Manager interface, this procedure downloads the firmware binary on the management host to the array and upgrades the firmware running in the array.
1. Log in to the management host.
2. On the Java Web Console page, click Sun StorageTek Common Array Manager.
3. Go to the Storage System Summary page and select the arrays to be upgraded.
4. Click the Upgrade Firmware button.
5. Follow the prompts.
After installing software for the data hosts, go to SunSolve (http://www.sun.com/sunsolve) and download the SSD driver for data hosts running the Solaris 8 or 9 OS.
|Note - Patch 108974-49 or higher requires patch 108528-29 or higher. If needed, apply patch 108528-29 or higher first.|
1. Download the 108974-49 or higher patch from SunSolve.
2. Unpack the patch:
3. Read the README file:
4. Apply the patch with the patchadd command:
5. Reboot your system.
reboot -- -rdTo Update the SSD Driver for the Solaris 9 OS
|Note - Patch 113277-44 or higher requires patches 112233-02 and 112834-02, which are already included in most versions of the Solaris 9 OS. If they are needed, apply patches 112233-02 and 112834-02 first.|
1. Download the 113277-44 or higher patch from SunSolve.
2. Unpack the patch:
3. Read the README file:
4. Apply the patch with the patchadd command.
5. Reboot your system.
reboot -- -r
The following sections provide information about known issues and bugs filed against this product release:
If a recommended workaround is available for a bug, it follows the bug description.
This section describes known issues and bugs related to installing and initially configuring the Sun StorageTek 6540 Array.
Bug 6757957 - Replacement controllers have recently shipped with 7.x version firmware on them. If the primary controller is replaced while the array is powered on and a good secondary controller with 06.xx firmware exists, the replacement should auto code synchronize to the secondary controller. During a controller replacement the replacement controller occasionally does not auto code synchronize to the secondary controller as it should. Instead, the array automatically upgrades to 7.x code.
In such a case. the firmware on the controllers will not match the baseline firmware on the Common Array Manager Software 6.2.0 CD or download. An alarm will be generated.
Workaround - Download the following patch and follow the patch instructions to install it on the array.
Patch 140060-01 6xxx Array Firmware -- (Solaris)
Patch 140061-01 6xxx Array Firmware -- (Windows)
Patch 140062-01 6xxx Array Firmware -- (Linux)
Future replacement controllers will be updated to correct the problem.
CSM200 expansion trays can hold either 2 or 4 Gbps drives, but not within the same tray. Mixing 2 and 4 Gbps drive trays in the same tray group (drive channel) will run all drives at the lower speed.
Trays Groups that must run at the same drive speed:
Figure 2.4 from the Sun StorageTek 6540 Array Hardware Installation Guide shows 4 tray groups. If you have 2 Gbps drive trays to mix with 4 Gbps drive trays, you could add all the 2Gbps drives to trays with IDs of X0 and X2. The 4 Gbps drive trays could go in trays with IDs of X1 and X3.
This does not apply to new trays consisting of all 4 Gbps drives.
This section describes general issues related to the Sun StorageTek 6540 Array hardware and firmware.
|Caution - The front and back doors of the system cabinet must be closed for compliance to domestic and international EMI regulations as well as proper equipment cooling.|
Do not block or cover the openings of the system cabinet.
Cabinet airflow is from front to back. Allow at least 30 inches (76.2 cm) in front of the cabinet, and at least 24 (60.96 cm) inches behind the cabinet, for service clearance, proper ventilation, and heat dissipation.
Bug 6760780 - When controller firmware version 18.104.22.168 or higher is used in combination with snapshot processing, controller A may panic and reboot unexpectedly.
Bug 6753699 - When using controller firmware version 22.214.171.124 or higher, it is possible to see differing drive status between controllers A and B during a drive migration to a vertical volume group arrangement. This can occur for both assigned and unassigned drives.
Workaround - To synchronize drive status between controllers A and B, it is necessary to reboot both controllers.
Bug 6755990 - When using controller firmware version 126.96.36.199 or higher, if an event occurs which normally would cause a single data replication pair to become unsynchronized, all data replication pairs become unsynchronized at the same time. A restart of data synchronization then causes both controllers on the primary data replication array to reboot continuously.
Bug 6724873 - If an LSI server running LSI StoreAge Storage Virtualization Manager (SVM) is attached to a Sun StorageTek 6540 array running controller firmware version 188.8.131.52, one controller reboots with anomalous data approximately four minutes after ownership of a volume is changed on the array. The other controller will often need to be manually rebooted in order for the array management software to work again with that controller.
This issue has also been known to occur when a volume on the Sun StorageTek 6540 array is mapped to an LSI server.
Workaround - To prevent this issue from occurring, configure the LSI server StoreAge SVM and Data Path Module (DPM) as host in the SAN.
Bug 6680647 - When running data replication with an I/O block size of 4096 blocks, it is possible for the array controller to reboot with anomalous data.
Workaround - If running controller firmware version 06.xx.xx.xx, do not exceed a maximum data replication block size of 512 blocks. If running controller firmware version 07.xx.xx.xx, do not exceed a maximum data replication block size of 1024 blocks.
Bug 6747153 - When running controller firmware version 07.xx.xx.xx, both the GUI and command line interface (CLI) versions of the array management software report 0 for cache memory size.
Workaround - The following serial command can be used to gather the cache size:
Bug 6749000 - When a single tray stack contains a mix of FLA200 and FLC200 trays, and the FLA200 trays contain Fibre Channel (FC) drives, it is possible to receive excessive FLA200 Dynamic Data Exchange (DDE) errors within the Major Event Log (MEL) of the array management software.
Workaround - Excessive DDE errors may be ignored.
Bug 6438824 - There is a module on the array, physically labeled ESM, that is identified by Sun StorageTek Common Array Manager software as an input/output module (IOM).
If a volume failure on a Sun StorageTek 6540 Array results from failed disk drives and you introduce replacement drives that were part of a volume in use by another Sun StorageTek 6540 Array, the array might incorrectly initiate a volume migration process with the replacement drives.
Workaround - Perform one of the following tasks:
The patch panel modem power cord is not connected to the cabinet power strip from the factory. To use the modem, power up the system before connecting the modem power cord to the cabinet power strip.
The Sun StorageTek 6540 Array Site Preparation Guide (819-6524-nn) incorrectly cites the following information in Chapter 2 under cabinet Power Requirements:
This should state the following:
All components in the cabinet should operate on only two of the 20A circuits (16A loaded each), but in this case no AC redundancy would be in place (power only A0/A1 or B0/B1).
With all four 20A circuits powered (A0, A1, B0, B1), the cabinet will draw a maximum total of 32A from the four circuits. If the system were to draw more than that 32A, then full AC redundancy cannot be present.
The Sun Rack 1000-38 cabinet power distribution systems work at 180-264VAC only. Internal components will never be operated below 180V (200V nominal) when in this cabinet.
This section provides useful operational information not documented elsewhere.
If you power off, remove, or experience a failure of either of the power cooling units, the system generates battery alerts for both batteries as “transitioning to an unknown state.”
Even though the batteries are listed as being in an unknown state, they are still providing protection in the event of a cache failure. No workaround is required.
If you power off, remove, or experience a failure of either of the power cooling units (which also house the controller’s battery packs), the system generates battery alerts for both batteries as “transitioning to an unknown state.”
Workaround - You should not lose data unless the batteries fail, or unless you do not have adequate charges remaining in the batteries for cached data to finish being written to disk.
Controller tray IDs can be set to any number between 0 and 99. Expansion trays use the values 0 to 79. Controller trays should use the values 80 to 99 (except 85) to avoid duplicate tray IDs.
If tray IDs are duplicated, the array will not be able to detect the drives on one of the two trays that have the same ID (which one is arbitrary). Do not use ID 85 for the controller tray, as this number is the default setting that indicates everything is operating as expected.
If you create management objects while an “import array” job is running, it might interfere with the import. Be sure that everyone who uses the destination array does not modify or create any objects (including volumes, initiators, mappings, and so on) while the import is in progress.
When you create a volume and label it, you can start using the volume before it is fully initialized.
During bootup, the battery light might flash for an extended period. The battery charger performs a series of battery qualification tests before starting a battery charge cycle. This series of tests occurs at subsystem power-up. The tests are automatically reinitialized by a timer approximately every 25 hours.
Each controller tray contains a hot-pluggable lithium ion battery pack for cache backup in case of power loss. The on-board battery is capable of holding a 2-GB cache for up to three days (72 hours). The service life of the battery pack is three years, at the end of which the battery pack must be replaced (it is field-replaceable).
The Solaris data host format command might render one or more of the following listings:
STK-FLEXLINE380-0616 and STK-UniversalXport-0616
These are not data volumes and should be ignored.
The following is a list of documents related to the Sun StorageTek 6540 Array. For any document number with nn as a version suffix, use the most current version available.
You can search for this documentation online at http://www.sun.com/documentation.
If you need help installing or using this product, go to:
Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.