StorageTek 2500 Series Array
|
|
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.
|
StorageTek 2500 Series Array Features
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.
About Common Array Manager Software
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.
Downloading Patches and Updates
Download the latest platform and firmware patch (see TABLE 1-1) from My Oracle Support (MOS).
For detailed patch download steps, see the Knowledge article 1296274.1 available on MOS.
- How to Download Common Array Manager (CAM) Software and Patches [ID 1296274.1]
Note - Each array should be managed by one CAM management host only. Installing the management software on more than one host to manage the same array can cause discrepancies in the information reported by CAM.
|
Platform and Firmware Patch IDs
TABLE 1-1 Platform and Firmware Patch IDs
Platform patch
|
Operating System
|
Firmware patch
|
Operating System
|
147416-xx
|
Solaris SPARC
|
147660-xx
|
Solaris
|
147417-xx
|
Windows
|
147661-xx
|
Windows
|
147418-xx
|
Linux
|
147662-xx
|
Linux
|
147419-xx
|
Solaris X86
|
|
|
Common Array Features
- Storage domain licenses are required to map additional initiators on data hosts to volumes.
- One drive expansion tray Serial Attached SCSI (SAS) connector per controller with 3GB/s drive expansion tray connection speed
- Maximum of 48 disk drives (one controller tray and three drive expansion trays)
- Maximum of 256 LUNs, with 32 per storage domain
- Dual redundant controllers
- SAS disk drives supported
- SATA disk drives supported
- 512-MB cache per controller or 1-GB mirrored cache, with the option for 1-GB cache per controller
Auto Service Request Feature
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
Premium features require licenses which must be ordered separately:
- 4, 8, 16, or 32 Storage Domains
- Enhanced Volume Snapshot (8 per volume and 128 per array)
- Volume-Copy
2500 Series Array Ship Kit Contents
Ship Kit Notes:
- StorageTek 2500 Series array controller and expansion trays are shipped separately.
- Small form-factor pluggables (SFPs) are included only with the StorageTek 2540 array.
- AC power cords are ordered and shipped separately.
- DC power cords are included with DC configurations.
- Cables for connecting the controller tray to the data host, such as Serial Attached SCSI (SAS), Fibre Channel (FC) fiber-optic, and Ethernet, are not included and can be ordered separately. SAS cables for inter-tray cabling are included with the StorageTek 2501 expansion tray ship kit.
Array Controller Kits
Common contents:
- One pair left and right end caps (plastic bezels)
- Two 6-meter RJ45-RJ45 Ethernet cables (one per controller module)
- One RJ45-DIN9 cable
- One RJ45-DB9 adapter
- One RJ45-DB9 adapter (with null modem)
- Documentation
- Accessing Documentation card
- Important Safety Information for Sun Hardware Systems
Content for the 2540 controller tray only:
- Four 4GB/s FC SFPs (2 per FC Controller module)
StorageTek 2501 Array Expansion Kit
Ship kit for each 2501 expansion tray:
- Two copper SAS cables (one per I/O module)
- One pair left and right end caps (plastic bezels)
- Accessing Documentation guide
System Requirements
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:
Firmware Requirements
- Firmware version 07.35.72.10 for CAM 6.9.x requires that controllers have a minimum of 512 MB of memory.
- You cannot upgrade directly from 6.x firmware to 07.35.72.10. You must first upgrade to the firmware bundled in the upgrade utility or in CAM 6.2.
- See the Sun StorageTek 2500 Series Array Firmware Utility Upgrade Guide about upgrading from 06.xx.xx.xx controller to firmware version 07.xx.xx.xx.
- Firmware is bundled with the CAM software download package. To download CAM, follow the procedure in Downloading Patches and Updates.
Supported Disk Drives
TABLE 1-2 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.
|
TABLE 1-2 Supported Disk Drives
Drive
|
Description
|
Seagate ST3146855SS
|
146GB - 15000 RPM SAS
|
Hitachi HUS153014VLS300
|
146GB - 15000 RPM SAS
|
Seagate ST3146356SS
|
146GB - 15000 RPM SAS
|
Seagate ST3300655SS
|
300GB - 15K RPM SAS
|
Hitachi HUS153030VLS300
|
300GB - 15K RPM SAS
|
Seagate ST3300656SS
|
300GB - 15K RPM SAS
|
Seagate ST3400755SS
|
400GB - 10000 RPM SAS
|
Seagate ST3450856SS
|
450GB - 15000 RPM SAS
|
Hitachi HUA721010KLA330
|
1TB - 7200 RPM SATA
|
Hitachi HDS725050KLA360
|
500GB - 7200 RPM SATA
|
Seagate ST3500630NS
|
500GB - 7200 RPM SATA
|
Hitachi HUA721050KLA330
|
500GB - 7200 RPM SATA
|
Seagate ST3750640NS
|
750GB - 7200 RPM SATA
|
Hitachi HUA721075KLA330
|
750GB - 7200 RPM SATA
|
Seagate ST373455SS
|
73.4GB - 15000 RPM SAS
|
Hitachi HUS153073VLS300
|
73GB - 15000 RPM SAS
|
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
Data Host Requirements
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.
2540 Array Data Host Requirements
The 2540 Array supports Fibre Channel-only connections to the data host.
TABLE 1-3 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 .
TABLE 1-3 Supported Data Host Platforms for 2540 Arrays
Host OS
|
Multipathing Support
|
Cluster Support
|
Solaris 9
|
SAN 4.4.12 and higher
|
Sun Cluster (SC)3.1
|
Solaris 10 SPARC
|
included in OS
|
SC 3.1, SC 3.2
|
Solaris 10 x64
|
included in OS
|
SC 3.1, SC 3.2
|
Windows 2003
|
MPIO
|
Microsoft Cluster Server
|
Linux
Red Hat 4/5;
SUSE 9/10 SP1
|
RDAC
|
Linux Cluster
|
Windows 2008
|
MPIO
|
Microsoft Cluster Server
|
ESX 3.5, ESX 3.0, ESX 3.0.2
|
included in OS
|
VMware HA
|
TABLE 1-4 Required Patches for Solaris Versions
Solaris Version
|
Required Patch (Minimum)
|
Solaris 9
|
SAN 4.4.12
113039-24 patch
|
Solaris 10 SPARC
|
120011-14
127127-11
|
Solaris 10 x86
|
120012-14
127128-11
|
2530 Data Host Requirements
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.
TABLE 1-5 Data Host Platform Support for 2530 Arrays
Host OS
|
SAS Support
|
Multipathing Support
|
Cluster Support
|
Solaris 10, SPARC
|
yes
|
Included in OS with patch 125081-10
|
SC 3.1, SC 3.2
|
Solaris 10, x86
|
yes
|
Included in OS with patch 125081-10
|
SC 3.1, SC 3.2
|
Windows 2003
|
yes
|
MPIO
|
Microsoft Cluster Server
|
Windows 2008
|
yes
|
MPIO
|
Microsoft Cluster Server
|
Red Hat 4/5;
SUSE 9/10 SP1
|
yes
|
RDAC
|
Linux Cluster
|
ESX 4.0, ESX3.5/U4
|
yes
|
Included in OS
|
VMware HA
|
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.
2510 Array Data Host Requirements
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.
TABLE 1-6 Supported Data Host Platforms for 2510 Arrays
Host OS
|
Multipathing Support
|
Cluster Support
|
Solaris 10 SPARC
|
included in OS
|
3.1 and 3.2
|
Solaris 10 x64
|
included in OS
|
3.1 and 3.2
|
Windows 2003
|
MPIO
|
Microsoft Cluster Server
|
Windows 2008
|
MPIO
|
Microsoft Cluster Server
|
Linux
Red Hat 4/5;
SUSE 9/10 SP1
|
RDAC
|
Linux Cluster
|
The table below lists the required patches for 2510 Solaris data hosts.
TABLE 1-7 Required Solaris Patches for 2510 Data Host Platforms
Solaris Version
|
Required Patch (Minimum)
|
Solaris 10 SPARC
|
Solaris 10 Update 1, Build 6 or later
118833-36
119090-25
|
Solaris 10 x64
|
Solaris 10 Update 1, Build 6 or later
118855-36
119091-26
|
Note - Windows 2000 is no longer supported.
|
Smart Battery Functionality
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.
Replacing a Simplex Controller
Note - If the controller is a replacement for a duplex controller environment, do not read further. Use the Service Advisor procedure to replace the unit. From the Sun Storage Common Array Manager application, click the Service Advisor button and follow the instructions.
|
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 Patches and Updates to obtain the latest CAM information and version available.
2. Replace the controller.
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:
# cd /opt/SUNWsefms/bin
# ./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.
Notable Fixes
Firmware revision 07.35.72.10 delivers the following fixes:
- 15417075 (CR6593602)--[ST2540] LUN mapping/unmapping or AVT event causes Host side FC bus to Reset
- 15564895 (CR6844287)-- ST2500: Controller reboot due to Exception Data Abort in TcpService on Exmoor firmware
- 15604152 (CR6901997)-- After controller reboot the Service Menu doesn’t display the real Speed/Duplex setting
- 15623331 (CR6927229)-- Battery Learn Cycle reported incomplete
- 15629287 ( 6934583)-- After the Firmware Update to 7.35.50.10 a 2540 reports write cache as inactive even if it is active
- 15640482 (CR6949074)-- 2500: IP address cannot be changed through GUI or CLI
- 15644797 (CR6954481)-- Watchdog Timeout from task "TcpService" after reinserting repository volumes drives in Snowmass.
- 15644810 (CR6954489)-- Data Abort _ZN6symrpc10TcpService6daemonEv reported on 4988
- 15655485 ( CR6968469)-- (symTask3): ASSERT: Assertion failed: false, file evfVolume.cc, line 3038
- 15656502 (CR6969709)-- Management port link down/up triggering connected data hosts seeing SCSI Unit Attention messages
- 15667928 (CR6983502)-- Both controllers rebooting with Exception: Data Abort
- 15669128 (CR6984981)-- storage array profile incorrectly interpreting SATA drive manufacturing date
- 15671399 (CR6987616)-- Exmoor smart battery gets failed during a learn cycle due to i2c bus errors
- 15671720 (CR6988049)-- ST2500: Component location mis-reported in the "Controller reset by its alternate" event type 0x400F
- 15680299 (CR6998633)-- ESM/IOM cards may reboot and cause errors in eventlog
- 15681765 (CR7000485)-- 2500: Update IOC FW to version 24.64.00
- 15681766 (CR7000486)-- Incorrect release of scatter gather list local chains in firmware on pended IOs to a missing device
- 15687073 (CR7006912)-- 2540 Reboot due to ancient I/O
- 15691840 (CR7012554)-- Seagate drive failure may also cause controller reboots
- 15697621 (CR7020305)-- ST2530: Battery Learn Cycle started very much later than scheduled.
- 15704087 (CR7029499)-- Controller reboots
- 15710549 (CR7038153)-- ST2500: Cannot reset battery age using CAM
- 15757273 (CR7115349)-- 2540:After replacement of one controller due to RPA error,Service Action Required LED lighting
- 15763203 (CR7125089)-- 2500LCA/2500M2/6x80/6x40: 7.x code can suspend media scan without warning.
- 15778119 (CR7152626)-- 2500LCA/6x40:Unable to reset battery near expiry via CAM due to non-GMT tz of mgt client
- 15788925 (CR7165515)-- Coverity Report on RESOURSE_LEAK - memory leak analysis uncovered 49 instances of memory leaks
- 15788926 ( 7165516)-- Memory leaks associated with calls to updateVolumeProperty
- 15788930 (CR7165520)-- Memory leak in getControllerDebugInfo_1
- 15788934 (CR7165524)-- Memory leaks associated with calls to updateVolumeProperty
- 15788949 (CR7165540)-- SUNBT7165540 reboot due to ’vdmExopExclOpMgr.cc, line 2916’
- 15788950 (CR7165541)-- Fix memory leak in sysFindSymbolFormat
- 15788952 (CR7165543)-- Fix potential memory leaks in PBM
- 15788953 (CR7165544)-- Coverity found resource leak in VDM
- 15788954 (CR7165546)-- SYMbol Server: Out of Memory
- 15788955 (CR7165547)-- Memory leak in fcn code that exchanges FcInterfaces via domi
- 15788956 (CR7165548)-- There is a memory leak in remoteOpen
- 15788957 (CR7165549)-- DOMI memory leak in auto-generated code
- 15788959 (CR7165551)-- utl::string() does a memory leak constantly
- 15788960 (CR7165553)-- PANIC:Invalid memory block at 0x31b2c28
- 15788963 (CR7165555)-- PANIC: Already freed memory block at 0x4bf6f5c
- 15788965 (CR7165557)-- PANIC: RAIDVolumeManager::lockOutDrives due to Invalid Adoption
- 15788966 (CR7165558)-- Unexpected Controller reboot due to a race condition during drive fail processing
- 15788968 (CR7165560)-- PANIC: Invalid memory block at 0x6e4cdb0
- 15788971 (CR7165563)-- Watchdog resets are reported as Alternate resets in FA log
- 15789006 (CR7165595)-- Controller B hitting PANIC initiated by Healthcheck
- 15789011 (CR7165600)-- Controller reboot after a drive failure
- 15789014 (CR7165603)-- Network Storms are causing controllers to reboot
- 15789020 (CR7165610)-- PANIC: Invalid memory block at 0x58d2628 while collecting Support Data
- 15789024 (CR 7165615)-- Reboot due to ancient IO during FO-FB with IO
- 15789025 (CR7165616)-- Ancient I/O
- 15789030 (CR7165621)-- PANIC: numbers of events mismatch: record diff 0x1fff, seq diff 0xffffffff
- 15789034 (CR7165624)-- Controller Reboot with Volume Copy results in an Ancient I/O error
- 15789035 (CR7165627)-- PANIC due to getRCB() method returning NULL pointer
- 15789037 (CR7165630)-- Ancient IO with sequential writes and prefetch
- 15789038 (CR7165631)-- PANIC: StateChangeMgr::incGenerationNumberAlt during straight I/O
- 15789039 (CR7165632)-- Ancient IO after sysReboot with heavy IO
- 15789040 (CR7165633)-- Reboot due to ancient IO, scsiOp 648f330
- 15791360 (CR7168377)-- 6x80/6x40/2500-LCA/2500-M2:Unable to recover multi-bit ECC errors by reading from alt controller
- 15792036 (CR7169253)-- 2500M2/2500LCA/6x40/6x80: DDC didn’t collect complete information after AIOs
- 15813179 (CR7195127)-- Enhancement to log additional lock information in a DDC
Known Issues
The following sections provide information about known issues and bugs filed against this product release:
Important Notes and Considerations
- Linux Red Hat Enterprise v5.1 is required for in-band management using the Linux OS.
- Wait 60 Seconds Before Replacing Drives--When a drive fails, wait 60 seconds after removing the failed drive before you put in a new drive.
- You must purchase a premium license to add storage domains.
- When Performing an Array Import, Do Not Modify Configuration: Configuring 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.
- Using a Volume Before It Is Fully Initialized--When you create a volume and label it, you can start using the volume before it is fully initialized.
- The maximum number of volumes per storage domain is 32.
- Do not map volumes to the hosts you created. Map the volumes only to host groups. If you map to hosts, you will have to change the mappings if you switch to a multipath configuration.
- When mapping multiple volumes, assign the first volume LUN number 0. A Solaris 10 data host does not need any changes to recognize LUN 0 of a target. The procedure to identify the target depends on this step.
- When converting from Simplex to Duplex arrays: Before you insert a second controller, you must change the array to “duplex” from the CAM Service Advisor and be sure each controller is set at the same firmware revision. Failure to perform these steps will cause the array to remain in simplex mode with the wrong revision of NVSRAM firmware and the firmware will not cross-load properly.
- After setting a tray to Duplex mode, “Validate revision level” prompts you to analyze the firmware revision level of the new controller. Note that the NVSRAM automatically updates with the firmware. For more information, see Service Advisor documentation.
Avoiding Firmware Issues
- Upgrading from an 06.xx.xx.xx version to an 07.xx.xx.xx version requires a special utility. Consult the Sun StorageTek 2500 Array Series Firmware Upgrade Utility Guide.
- Before inserting a second controller, change the array to “duplex,” following CAM Service Advisor procedures. Each controller must be at the same firmware level.
- For the latest firmware information, go to: http://docs.oracle.com/cd/E24008_01/index.html and open the Array Baseline Firmware Reference PDF.
Configuration, Firmware and Hardware Issues
Battery Events Do Not Identify the Battery’s Controller Location
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.
Cache is Disabled when Batteries are Charging
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 (preceeding a battery charge cycle).
Controller Slot Positions Contained in MEL Log are Unreliable
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.
Controller Tray and Drive Expansion Trays - Turning off the Power
|
Caution - Before turning off the power to the drive expansion trays connected to the controller tray, you must turn off the power to controller tray. Failure to do so may cause a volume configuration loss which is not reversible.
|
- When powering the array off, power must first be removed from the controller tray. When the controllers are powered down, the expansion trays can be powered down.
- Turn off the power switch on both power fan assemblies in the controller tray.
- Turn off the power switch on both power fan assemblies in all of the drive expansion trays connected to the controller tray.
- When powering-up the array, power must be applied to the expansion trays first, and the disks should be given time to spin up to speed. Then the controller tray can be powered up.
Create Volume Fails on ESM During First Attempt
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.
Disabled Snapshot can be Re-enabled after a Firmware Update
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.
Expansion Module with Licensed Domains Causes Event
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.
LED Lights After Data Host Power On
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.
mpathadm Does Not Reflect Accurate Path Count After Moving or Removing a Path
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.
Select File Button Does Not Work
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.
Service Advisor Does Not Verify Disk is Ready to be Removed
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.
SES vs. SD Paths for UTM LUNs.
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>]
Small Form-Factor Pluggable (SFP) May Not Generate a Fault Indicator
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.
Upgrade Utility Automatic Array Discovery Password Verify does not Reference the Array
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.
Upgrade Utility Intermittently Fails
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.
UTM LUNs Controlled by “Solaris Traffic Manager”
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.
iSCSI Issues
Initiator with the Same Name as a Host Creates an Error
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.
Out-of-Band Management May Lose Connectivity
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.
Values Returned for iSCSI Statistics Counters are Negative
Bug 6611655 - Negative counter values display for iSCSI Statistics large counter values. The values should be unsigned.
Workaround - From Administration->Performance, click Reset Values.
SAS Issues
Creating New Volumes During Heavy Input-Output Can Result In Errors
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
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.
Description
|
Title
|
Getting Started
|
Getting Started Guide for Sun StorageTek 2500 Series Storage Arrays
|
Array Installation
|
Sun StorageTek 2500 Series Array Hardware Installation Guide
|
CAM Release Notes
CAM User Guide
|
Sun Storage Common Array Manager Release Notes
Sun Storage Common Array Manager Administration Guide
|
Site Planning
|
Sun StorageTek 2500 Series Array Site Preparation Guide
|
Regulatory and Safety
|
Sun StorageTek 2500 Series Array Regulatory and Safety Compliance Manual
|
|
|
CAM Installation and Configuration
|
Sun Storage Common Array Manager Software Installation Guide
|
CAM CLI Quick Reference
|
Sun Storage Common Array Manager CLI Guide
|
Instructions for installing the Sun StorEdge Expansion cabinet
|
Sun StorEdge Expansion Cabinet Installation and Service Manual
|
Instructions for installing the Sun Rack 900/1000 cabinets
|
Sun Rack Installation Guide
|
Command-line-interface Help
|
sscs man pages
|
Replacement Procedures
|
Service Advisor
|
Documentation, Support, and Training
These web sites provide additional resources: