|
This document contains important release information about the Sun StorageTek 2500 Series Array or information that was not available 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 2500 Array.
These release notes cover the Sun StorageTek 2500 Series Array, Release 1.1 and Release 6.17.52 firmware, and related hardware issues. For information on management software requirements, operations, and issues, see the Sun StorageTek Common Array Manager Software Release Notes, Release 5.1.3 or higher.
The release notes consist of the following sections:
This section describes the main features of the Sun StorageTek 2500 Array, including the following:
The Sun StorageTek 2540 Array, the Sun StorageTek 2530 Array, the Sun StorageTek 2501 Expansion Module, and upcoming models are a family of storage products.
The Sun StorageTek 2500 Arrays contains disk drives for storing data and controllers that provide the interface between a management and/or data host and the disk drives. The Sun StorageTek 2540 Array provides a Fibre Channel connection from the data host to the controller. The Sun StorageTek 2530 Array provides a Serial Attached SCSI (SAS) connection from the data host to the controller.
The Sun StorageTek 2501 Expansion Module provides additional storage. You can attach the drive expansion tray to the Sun StorageTek 2540 and 2530 Arrays.
Note - SAS multipathing is supported for Windows and Linux data hosts. Only single-path is supported for Solaris data hosts pending the release of a new Solaris multipath driver.. |
Auto Service Request (ASR) is a new 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.
You enable the Auto Service Request capability by using a Sun StorageTek Common Array Manager software feature, Sun Connection, to register devices to participate in the ASR service. Refer to the Sun StorageTek Common Array Manager Release Notes, Release 5.1.2 or higher, for more information.
Premium features require licenses which must be ordered separately. (The 2500 Series Arrays provide two free storage domains.) The following premium features are available for 2500 Series Arrays:
Note - Storage domain licenses are required to map initiators on data hosts to volumes. |
The Sun StorageTek 2500 Series Array controller and expansion trays are shipped separately.The Ac power cords are ordered separately. The following is a list of the contents in the tray ship kits. There may also be read me first notices.
Content for the 2540 controller tray only:
Ship kit for each 2501 expansion tray:
The Sun StorageTek Common Array Manager software (5.1.2 and above) provides you with an easy-to-use interface to configure, manage, and monitor Sun StorageTek storage systems, including the Sun StorageTek 2500 Series Array. You can also use the Common Array Manager software to diagnose problems, view events, and monitor the health of your array. Each release of the Common Array Manager provides the latest firmware updates for all the arrays it supports and provides the means to upload the firmware to them.
The Common Array Manager is the only supported management software for the 2500 Series Array. Refer to the Release Notes and other Sun StorageTek Common Array Manager documentation described in Release Documentation."
Release 1.1 of the Sun StorageTek 2540 and 2530 Arrays support firmware release 6.17.52.10.
TABLE 1 lists the firmware files for Release 1.1. Updates to the firmware are included with releases of the Sun StorageTek Common Array Manager software or patches. For a listing of the firmware files in subsequent releases, refer to the Sun StorageTek Common Array Manager Release Notes or patch notes.
After you install the CAM software, these files will be located in:
TABLE 2 lists the firmware files for the StorageTek 2530 Array included in this release. After you install the CAM software, these files will be located in:
These firmware types are defined as follows:
The software and hardware products that have been tested and qualified to work with the Sun StorageTek 2500 Series Array are described in the following sections:
TABLE 3 lists the size, speed, and tray capacity for the supported Serial Attached SCSI (SAS) disk drives in the Sun StorageTek 2500 Series Array.
This section provides the data host requirements of the 2500 Series Array at the time this document was produced. These requirements can change; for complete up-to-date compatibility requirements, contact your Sun sales or support representative.
Data host requirements for 2540 arrays, which support Fibre Channel connections to the data host, are different from 2530 arrays, which use SAS connections to the data host.
Sun provides an online tool to get the latest information about supported hosts, HBAs, switches, and drivers.
https://extranet.stortek.com/interop/interop
Note - The 2540 Array supports Fibre Channel-only connections to the data host. The information in this section applies only to data hosts with Fibre Channel connections. |
TABLE 4 lists the supported host Operating Systems (OSs) and multipathing availability. HBAs must be ordered separately, from Sun or their respective manufacturers. Sun HBAs can be ordered from the following site: /www.sun.com/storagetek/storage_networking/hba/
You must install data host multipathing software on each data host that communicates with the Sun StorageTek 2540 Array. Follow the instructions in the Sun StorageTek 2500 Series Array Hardware Installation Guide to download and install the software from the Sun Download Center.
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.
Note - The patches listed in Table 4 are required for Solaris. |
Note - The 2530 Array supports SAS-only connections to data hosts. The information in this section applies only to data hosts with SAS connections. |
TABLE 6 lists supported 2530 data host platforms and indicates the kind of support they have for SAS connections.
The array installation procedures are described in the Sun StorageTek 2500 Series Array Hardware Installation Guide, Release 1.1 (part number 820-0015-10) that came with your array. Host Management upgrades are described in the Sun StorageTek Common Array Manager 5.1.2 Release Notes. This section describes release-specific steps for firmware upgrades that you must perform.
If you have a previous release of the 2500 Series Array firmware installed, the Common Array Manager upgrade software will detect it and provide a means to upgrade to the new firmware versions required for this release. The upgrade software is included on the Sun StorageTek 2500 Series Array CD, or in the package you obtain from the Sun Download Center: http://www.sun.com/software/download/
Upgrade the firmware on the array using the Common Array Manager interface after the software is installed and the array registered with the software.
You can upgrade the firmware on the 2540 Array without stopping I/O. For firmware for expansion modules, disk drives, and IOMs, it is recommended that a maintenance period of low activity be scheduled in order to execute the upgrade process.
1. On the Java Web Console page, click Sun StorageTek Common Array Manager.
2. Go to the Storage System Summary page and select the arrays to be upgraded.
3. Click the Upgrade Firmware button.
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 general issues related to the Sun StorageTek 2500 Series Array hardware and firmware.
Bug 6497666 - Release 1.1 does not support Veritas ASL.
Bugs 6544481 and 6496643 - The wrong tray type, SS3600, for 2500 Series Arrays and a host board type of 1, unknown, displays in the management software. The can be especially confusing on the new array information screen that displays when a new array is registered in the management software.
Workaround - Refer to the packing list shipped with the array if you need to check the tray type.
Bug 6541677 - Using the Service Advisor function to redistribute volume ownership may produces an error if the array has heavy data input/output.
Workaround - Schedule a maintenance period of low activity in order to redistribute volume ownership.
Bugs 6540408, 6538961, 6538960 - Watch out for sharp corners and edges on:
Workaround - Handle the array carefully to avoid the sharp corners and edges.
Bug 6507700 - IOM firmware upgrades may fail when the array is servicing a heavy amount of host IO.
Workaround - No IOM upgrades are scheduled at this time. If one occurs, schedule a maintenance period of low activity in order to execute the upgrade process.
If the upgrade fails, reset the controllers before updating the IOM firmware again.
Bug 6509762 - After a firmware upgrade to an Input-Output Module (IOM), the array will display a Check Condition - Microcode Changed message on all hosts.
After a firmware upgrade, an automatic failback was generated. When the switch port connecting the data host was enabled, the auto failback failed, indicating that it did not process the MICROCODE_CHANGED message.
Workaround - No IOM upgrades are scheduled at this time. If one occurs, there are two workarounds:
1) Perform a manual failover. The issue will not happen.
2) After updating the IOM firmware, manually forcing a failover and failback of all effected LUNs on any mapped Solaris host will clear out the condition.
Bug 6509331 - In Solaris, under heavy data traffic, host-initiated failover may generate error messages in /var/adm/messages even though the failover is successful.
Workaround - In the CLI, use the Solaris luxadm command to verify that the failover was successful.
$ luxadm di /dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
Vendor: SUN
Product ID: LCSM100_F
Revision: 0617
Serial Num: 1T60325953
Unformatted capacity: 3072.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x3
Device Type: Disk device
Path(s):
/dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
/devices/scsi_vhci/ssd@g600a0b8000245d4c0000310a458a852b:c,raw
Controller /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0
Device Address 202400a0b8245db7,5
Host controller port WWN 210000e08b883b2e
Class secondary
State STANDBY
Controller /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1,1/fp@0,0
Device Address 202500a0b8245db7,5
Host controller port WWN 210100e08ba83b2e
Class primary
State ONLINE
Note that the primary controller is online.
2. Issue the failover command.
An error message is generated indicating failure.
$ luxadm failover secondary /dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
Error: Unable to perform failover, standby path unavailable
3. Verify the path characteristics
$ luxadm di /dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
Vendor: SUN
Product ID: LCSM100_F
Revision: 0617
Serial Num: 1T60326060
Unformatted capacity: 3072.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x3
Device Type: Disk device
Path(s):
/dev/rdsk/c9t600A0B8000245D4C0000310A458A852Bd0s2
/devices/scsi_vhci/ssd@g600a0b8000245d4c0000310a458a852b:c,raw
Controller /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0
Device Address 202400a0b8245db7,5
Host controller port WWN 210000e08b883b2e
Class secondary
State ONLINE
Controller /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1,1/fp@0,0
Device Address 202500a0b8245db7,5
Host controller port WWN 210100e08ba83b2e
Class primary
State STANDBY
Note that the secondary controller is now online, indicating that the failover occurred.
Bug 6508950 - Configuring a duplex array for simplex can result in a critical event message showing channel path 2 as degraded. Channel path 2 is not part of a simplex configuration.
Workaround - Ignore the message for simplex configurations.
Bug 6514411 - Inserting a disk drive into a tray by pushing on its housing until it is all the way in causes the drive to stop without being fully inserted and with the drive handle protruding.
Workaround - The correct way to insert a disk drive into the tray is as follows:
1. Push the disk drive into the chassis by slowly pushing against the drive housing until the drive handle engages with the chassis.
2. When the handle starts to move itself downwards, push the disk drive handle down. This will crank the disk drive the rest of the way into the chassis.
When the drive is completely installed, the drive and handle will be flush with the other drives.
Caution - Do not insert a disk drive into a tray by pushing on its housing until it is all the way in. This can cause the handle to be stuck in the "up" position so it is unable to close. |
If the drive handle is stuck because the front lock tab is engaged in the tray's frame, carefully use a flat-bladed screwdriver to temporarily increase the gap between the tray frame and the drive and remove the drive.
Bug 6482519 - The luxadm probe command displays UTM LUNs on x86 platforms. The UTM (Management) LUN is a reserved space, normally hidden, where the specific configuration settings for your array are stored.
Bug 6487239 - Solaris only - If unconfigured LUNs are removed from the cfgadm -al list, they cannot be directly configured.
Workaround - Reboot the host and the LUNs will appear on the list again. Use the cfgadm -c option to remove specific paths.
Bug 6502673 - A battery replaced in a controller reports a failed battery event, while it is recharging. After the battery is fully recharged, this alarm will go away.
Bug 6503171 - Battery event messages do not specify which of the two controllers the referenced battery is in.
For battery events, the array only reports the tray where it occurs, not the slot.
Workaround - For non-critical events, collect the support data and find the corresponding event in the MEL log. For critical events, the third amber LED lights on the front of the controller with the failed battery.
Bug 6514739 - If a bad SFP is inserted in the FC port of a 2540 array, there may not an indication in the fault list that it is bad.
Certain failure modes of an SFP may not be detected by the array firmware immediately upon insertion and the management software could report the link state as optimal.
However, when you initiate I/O on the channel with the damaged SFP, it will be reported as failed.
Workaround - Check the fault LED and link LED for link failure. Check the event log for a failure event at the time of the SFP insertion and when you initiate I/O.
Bug 6514846 and 6514877- Over-temperature condition results in Power Fan CRU failed alarms. The front overtemp LED fails to light but the front panel amber LED does come on.
The controller firmware is set to report a temperature warning when any temperature sensor reaches 62 degrees. A temperature critical condition is reported at 67 degrees.
The power supply firmware will report the power supply as "failed" when it internally detects that the ambient temperature has reached 55 degrees. The controller firmware will report that failure status from the power supply, even though it is the temperature is below its usual threshold.
Workaround - Perform the following:
1. Check the temperature in the environment where the array is located and adjust to a cooler setting if necessary.
2. If the environmental temperature is adequate but the event log indicates a temperature in the Power/Fan CRU of 55 degrees or greater and if the problem persists for greater than 24 hours, contact support.
Bug 6545973 - Blue LED does not clear after replacing failed drive.
When a drive fails, LEDs display a solid light for the amber fault LED and blue LED that indicates that the drive can be replaced. Once the drive is replaced with a new or different drive, the amber fault LED clears on the drive enclosure, but the blue LED remains lit. The array enclosure fault LED behaves as expected.
Workaround - Use Sun StorageTek Common Array Manager software to revive the newly installed drive. The blue LED will clear. Note restrictions on reviving drives in the Common Array Manager online help.
Bug 6523608 - Refreshing a snapshot does not update to the filesystem if there is insufficient reserve space, yet a message displays indicating success. The array's event log says the resnap completed successfully.
Workaround - In the snapshot feature of the management software, configure snapshots to fail if sufficient reserve space is not available.
Bug 6523624 - If a firmware upgrade to an expansion module fails, the array may not clear the failed session automatically.
Workaround - After 20 minutes, retry the upgrade. If the upgrade fails again, power cycle the array to clear the failure.
Bug - A busy array can increase CAM response time.
Bug 6501029 - When the management software lists a disk as failed and the Service Advisor procedure for replacing drives is followed, the step to verify that the disk is ready to remove may not list the failed disk.
Workaround - Use an alternative menu option, Array Troubleshooting and Recovery, to view the status of the disk.
Bug 6535523 - For a single path driver, replacing a SAS controller may change the Target ID of the controller. This causes a LUN name change and the current LUNs will disappear.
Workaround - Do not use the array as a boot device. Edit the sd.conf file and add the new LUN names. Need info about drive renumbering. For details, see page 40.
Bug 6522947 - Removing a SAS controller results in outdated information on the Controller Details page in the management software. The status correctly reports the controller as removed. No work-around is available.
Bug 6522938 - For SAS, using the CLI to create a new volume on an array with high data input and output returns in a timeout and an error code of 4.
Workaround - Retry the operation when there is less I/O traffic.
Bug 6529719 - An attached failed warning message for SCSI devices can be generated when using an MPT driver for SAS.
You cannot use SCSI and SAS HBAs on the same data host.
This section describes known issues and bugs related to the online help, the command-line interface sscs man page, or any other Sun StorageTek 2500 Series Array release documentation.
The Sun StorageTek 2500 Series Array Hardware Installation Guide, part number 820-0015-10, lists Solaris 8 as supported. Only Solaris 9 and/or 10 are supported, depending on the application.
Bug 6541767 - Additional instructions are needed if the management software loses communication with the array.
Workaround - If the management software loses communication with the array, perform basic networking troubleshooting to reestablish the connection:
Bug 6537150 - The Service Advisor procedures for the 1500 Series Arrays lack an instruction to place the controller offline before removing and replacing a controller battery. The controller must be pulled to replaced the battery.
Workaround - Place the controller offline before removing the controller and replacing the battery.
The Sun StorageTek 2500 Series Array Hardware Installation Guide, Part No. 820-0015-xx, states in Chapter 2:
"Expansion trays must be added with the power to the array and I/O data transfer turned off."
This is incorrect. It is best to add an expansion tray to a running array instead of one that is powered off. Limiting I/O traffic is recommended for the duration of the reconfiguration.
The Sun StorageTek 2500 Array Hardware Installation Guide gives the default IP addresses right up front (Configuring IP Address of the Array Controllers), but does not include the netmask. The netmask for these defaults is 255.255.255.0
Page 75 of the Sun StorageTek 2500 Series Array Installation Guide references two min-DIN to RJ45 serial port cables. Only one RJ45-DIN9 cable is supplied, as well as the following adapters:
Bug 6515249 - In Chapter 2 of the Sun StorageTek 2500 Array Hardware Installation Guide the list of tools needed for the array installation in a rack does not list a flathead screwdriver, which is required if you need to loosen the rail extension screws.
In Chapter 5 of the Sun StorageTek 2500 Array Hardware Installation Guide the procedure in the section "Enabling Multipathing Software for Solaris 10 OS" now applies to the enabling of SAS multipathing as well. [Note -- Solaris SAS multipathing is not supported in this release.]
Bug 6533616 - Unable to reconcile SAS hosts with WWNs between controllers and array and accurately discover HBAs attached to the array. Refer to Appendix A for information on how to work with WWNs on SAS hosts.
This section provides useful operational information not documented elsewhere.
The 2500 Series array includes two storage domains. You must purchase a premium license to use additional storage domains.
Configure management objects while an import array job is running might interfere with the import. Be sure that everyone who uses the destination array does not configure any objects (including volumes, initiators, mappings, etc.) 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 approximately every 25 hours by a timer.
Each controller tray contains a user-replaceable lithium ion battery pack for cache backup in case of power loss. The on-board battery is capable of holding a 2-gigabyte cache for three days (72 hours). The service life of the battery pack is two years, at the end of which the battery pack must be replaced (it is field-replaceable).
Following is a list of documents related to the Sun StorageTek 2500 Series 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
In addition, the Sun StorageTek 2500 Series Array includes the following online documentation:
Contains system overview and configuration information.
Provides guided FRU replacement procedures with system feedback. You can access Service Advisor from the Sun StorageTek Common Array Manager software.
Provides help on man page commands available on a management host or on a remote CLI client.
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
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.
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.