StorageTek 2500 Series Array Release Notes |
This document describes features of and requirements for Oracle’s StorageTek 2510, 2530, and 2540 arrays. It also includes the procedure for replacing the controller in a single-controller (simplex) array.
These release notes include the following sections:
Note - Single Expansion Storage Modules (ESMs) cannot be used with a duplex 25xx array. |
Array controller firmware version 07.35.74.10 is delivered with the CAM 6.10. It provides the hardware bug fixes listed in Notable Fixes.
See the Sun Storage Common Array Software Release Notes for CAM 6.10 bug fixes.
The StorageTek 2540, 2530, and 2510 arrays, along with the StorageTek 2501 expansion module, make up the 2500 family of arrays.
The StorageTek 2500 arrays contain disk drives for storing data and controllers that provide the interface between a data host and the disk drives. The StorageTek 2540 array provides Fibre Channel connectivity from the data host to the controller. The StorageTek 2530 array provides Serial Attached SCSI (SAS) connectivity from the data host to the controller. The StorageTek 2510 array supports Internet Small Computer Systems Interface (iSCSI) over Ethernet networks.
The StorageTek 2501 expansion module provides additional storage. You can attach the drive expansion tray to the StorageTek 2540, 2530, and 2510 arrays.
The Sun Storage Common Array Manager (CAM) software provides an easy-to-use interface from which you can configure, manage, and monitor StorageTek and Sun Storage arrays.
The updated firmware is delivered with CAM 6.10, which is available on My Oracle Support (MOS) https://support.oracle.com.
For detailed download steps, see:
Auto Service Request (ASR) is a feature of the array management software that monitors the array system health and performance and automatically notifies the Oracle Support when critical events occur. Critical alarms automatically generate a Service Request. The notifications enable Oracle Support to respond faster and more accurately to critical on-site issues.
You can enable ASR for your storage devices via the Sun Storage Common Array Manager software. Refer to the Sun Storage Common Array Manager Release Notes for more information.
Premium features require licenses which must be ordered separately:
Content for the 2540 controller tray only:
Ship kit for each 2501 expansion tray:
The software and hardware products that have been tested and qualified to work with the StorageTek 2500 Series Array are described in the following sections:
TABLE 1-1 lists the size and speed for the supported disk drives in the StorageTek 2500 Series array.
Note - Upgrading from a 06.xx.xx.xx version to 07.xx.xx.xx requires a special utility. Consult the Sun StorageTek 2500 Array Series Firmware Upgrade Utility Guide. |
For more information about supported disk drives, see the Sun System Handbook:
https://support.oracle.com/handbook_private/Systems/2510/components.html#Disks
https://support.oracle.com/handbook_private/Systems/2530/2530.html
https://support.oracle.com/handbook_private/Systems/2540/2540.html
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 Oracle sales or support representative.
The 2540 Array supports Fibre Channel-only connections to the data host.
TABLE 1-2 lists the supported host Operating Systems (OSs) and multipathing availability. HBAs can be ordered from Oracle’s respective manufacturers or directly from Oracle. For information about Oracle HBAs, go to: http://www.oracle.com/us/sun/index.htm .
You can download HBA drivers and other host software from My Oracle Support (MOS) at https://support.oracle.com . To download operating system updates, go to the web site of the operating systems company.
Dual path failover requires multipath software. Follow the instructions in the Sun StorageTek 2500 Series Array Hardware Installation Guide to download and install the software from MOS.
Solaris patches can be downloaded from: https://support.oracle.com .
The 2530 Array supports SAS-only connections to data hosts.
The table below lists supported 2530 data host platforms and indicates the kind of support they have for SAS connections.
For details on patches and supported VMware versions, go to: http://www.vmware.com/
For more information about Sun Cluster support, go to: http://www.oracle.com/us/sun/index.htm or contact your service engineer.
The 2510 Array supports iSCSI with Ethernet connections to Network Interface Cards (NICs) on the data host.
The table below lists the supported host OS and multipathing availability. You can download host software from the MOS Download operating system updates from the web site of the operating system company.
The table below lists the required patches for 2510 Solaris data hosts.
Note - Windows 2000 is no longer supported. |
Refer to the knowledge article SMART Battery Functionality in Sun StorageTek 2500 and Sun Storage 6000 Arrays (Doc ID 1207186.1) at My Oracle Support (MOS) https://support.oracle.com.
1. Verify your Common Array Management Software is at the 6.2.0 level or later.
Caution - Do NOT use the -f option to uninstall the previous version of CAM. |
See Downloading the Firmware to obtain the latest CAM information and version available.
For details, see the Sun StorageTek 2500 Series Controller Removal and Replacement document.
3. If CAM shows the array is in working order, no further action is needed.
4. If after two minutes from powering the array back up CAM still reports “Communication Lost,” then run the following:
# ./csmservice -i -a <array-name> -Z UNLOCK -w
# cd "c:\Program Files\Sun\Common Array Manager\Component\fms\bin"
# .\csmservice -i -a <array-name> -Z UNLOCK -w
# cd /opt/sun/cam/private/fms/bin/
# ./csmservice -i -a <array-name> -Z UNLOCK -w
Results: The correct controller firmware will be loaded, the array will reboot, and CAM should report array status.
Firmware revision 07.35.74.10 delivers the following fixes:
The following sections provide information about known issues and bugs filed against this product release:
Note - For the latest firmware information, go to: http://docs.oracle.com/cd/E24008_01/index.html and open the Array Baseline Firmware Reference PDF. |
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.
Please be aware that until batteries are fully charged, your system might experience lower than normal performance during: events that disable cache, battery learn cycle, battery charge cycle, battery charge level below necessary charge level (preceding a battery charge cycle).
Bug 6747684 - The controller redundancy lost event is showing the wrong controller slot in the component field on a 2530 array.
Workaround - Review CAM Service Advisor/Alarms for more information regarding which controller has actually lost redundancy.
Bug 6767895 - Create Volume command fails on first attempt using 25x0 controller, resulting in an error message similar to the following: “An unexpected internal system error occurred. Retry the operation and then contact your Oracle service representative if the error persists.”
Workaround -Try the operation again. It should work on the second attempt.
Bug 6529172 - A snapshot volume that is disabled can be automatically re-enabled after a firmware update occurs. If the snapshot volume is full, it can start generating warning events.
Workaround - Disable the snapshot again after the firmware update.
Bugs 6550702 and 6547615 - If you migrate an expansion module with licensed storage domains into an array that has a different number of licenses, an alarm will be generated.
Workaround -For a mismatch of license numbers, disable the licenses on the expansion module. Then, disable the storage domains on the expansion module. The array will return to the licenses for the array, and the alarm will clear. Add any new licenses, if needed.
Bug 6587720- The Array Service Required LED will light after powering down a data host, connecting FC cables between the HBA and controllers, and powering up the host server.
This is working as designed. Under a Direct Connect environment, rebooting the connected data host will cause a FC link down alarm. This is an expected alarm and the Amber Service Required LED is expected to illuminate. As soon as the link is back up, the Alarm should clear and the LED should turn off. The same behavior would be expected if a cable were unplugged from the HBA, or if there were an error with the HBA port or the HBA itself.
Under a switch environment, this will not occur unless a cable is unplugged from the switch, the switch is rebooted, or is having errors. Rebooting the host will not cause the link to go down because the link from the controller SFP to the switch will remain up.
Bug 6579069 - Using the “mpathadm” command to remove a path from the system or relocate from one path to another, the “Total Path Count” will not update until the system is rebooted.
Workaround - Reboot to clear the extra path.
When you use the Simplicity storage management software to download a firmware update file for an 2540 array module, the Select File button does not work.
Workaround - Enter the file path and file name into the Filename text box.
When CAM shows a disk is failed and the Service Advisor procedure for replacing drives is followed, the step to verify that the disk is ready to remove might not list the failed disk.
Workaround - Use an alternative menu option, Array Troubleshooting and Recovery, to view disk status.
Bug 6500605 -For Solaris 10u4 and Solaris 8 and 9, the host cannot see the storage device's management UTM LUN.
Note - This bug is fixed in S10u5. |
Workaround -Perform the following commands on the data host:
# setenv LD_LIBRARY_PATH /opt/SMgr/agent
# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep “Volume Access”
You should then receive output like the following, indicating which arrays have access LUNs visible to the agent:
/dev/rdsk/c5t200600A0B82458D4d31s2 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>] /dev/rdsk/c5t200700A0B82458D3d31s2 [Storage Array fms-lca1, Volume
Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
Bug 6514739 - If a bad SFP is inserted in the FC port of a 2540 array, there might be no indication 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 6736963 - When multiple arrays are discovered (using the Automatic scan subnet option), the Password Verification pop-up windows do not make reference to the array. Workaround - In progress.
Bug 6723212 - Sometimes the upgrade process appears to hang, and it appears the firmware did not install. The Graphical User Interface (GUI) eventually times out, and the log contains an “Error downloading file(s) to the array” message.
Workaround - Try the upgrade process again. If failure persists, upgrade to 6.70.54.11 before attempting to use the upgrade utility.
Note - For the latest firmware information, go to: http://docs.oracle.com/cd/E24008_01/index.html and open the Array Baseline Firmware Reference PDF. |
Bug 6594360 -After you upgrade to S10U3 (or later), the in-band management UTM LUNs are controlled by Solaris Traffic Manager (MPxIO). In most cases, in-band management will not fail as a result of this; however, it is best practice to ensure that the UTM LUNs are not controlled by MPxIO. Performing the following workaround task will help prevent problems.
Workaround -Use the format inquire command to get the eight-character Vendor (VID) and Product IDs. Use the procedure that follows.
1. Edit the file /kernel/drv/scsi_vhci.conf so it reads:
device-type-scsi-options-list = “SUN Universal Xport”, “disable-option”; disable-option = 0x7000000
2. Run the stmsboot -u command. Answer “y” to continue and reboot the system immediately.
Bug 6624755 - For iSCSI on the 2510 Array only, creating an initiator with the same name as a host returns error message 57: “The operation cannot complete because the identifier or name you provided already exists. Please provide another identifier or name and then retry the operation.”
Workaround - Do not create an initiator with the same name as a host.
Bug 6615356 - SYMbol task ServsymRpcHandle periodically dies, causing the management software to lose communication with the array.
The cause has been identified and will be corrected in future releases.
Workaround - Run the nicStop and nicStart commands. For more information, run nicHelp. If the issue persists, reboot the system.
Bug 6611655 - Negative counter values display for iSCSI Statistics large counter values. The values should be unsigned.
Workaround - From Administration->Performance, click Reset Values.
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 - Re-try the operation when there is less I/O traffic.
Product documentation for the 2500 Series array is available at:
http://www.oracle.com/technetwork/documentation/oracle-unified-ss-193371.html
Product documentation for Sun Storage Common Array Manager is available at:
http://www.oracle.com/technetwork/documentation/disk-device-194280.html.
These web sites provide additional resources:
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.