| Sun Storage 6180 Array Release Notes, Release 6.6 |     |
|
Sun Storage 6180 Array Release Notes, Release 6.6 |
This document contains important release information about the Sun Storage 6180 Array running Sun StorageTek
Common Array Manager (CAM), Release 6.6. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the array.
The release notes consist of the following sections:
See the Sun StorageTek Common Array Manager software documentation and release notes for the CAM 6.6 release at:
http://docs.sun.com/app/docs/prod/stor.arrmgr
Look for the latest patches pertaining to your environment at:
http://sunsolve.sun.com/show.do?target=patchpage
1. In the Search box in the masthead, enter 6180.
2. Filter Results By: Downloads > Patches.
Patches related to the array are listed.
Array controller firmware version 7.60.18.13 includes expanded disk drive support, including support for encryption-capable drives (see TABLE 1 for a list of supported drives).
The firmware is provided with Sun StorageTek Common Array Manager (CAM)
v. 6.6.0, available for download at:
http://www.sun.com/storage/management_software/resource_management/cam
Click the “Buy Now” button to download the latest CAM software.
For more information about bug fixes, see the Sun StorageTek Common Array Manager Release Notes, v6.6.0.
The Sun Storage 6180 Array is a high-performance, enterprise-class, full 8 Gigabit per second (Gb/s) I/O Fibre Channel solution (with backend loop speeds of 2 or 4 Gb/s) that combines outstanding performance with the highest reliability, availability, flexibility, and manageability.
The Sun Storage 6180 Array is modular, rackmountable, and scalable from a single dual-controller tray (1x1) configuration to a maximum configuration of 1x7 with six additional CSM200 expansion trays behind one controller tray.
The software and hardware products that have been tested and qualified to work with the Sun Storage 6180 Array are described in the following sections. The Sun Storage 6180 Array requires Sun StorageTek Common Array Manager, v6.6 (or higher) software.
The Sun Storage 6180 Array requires firmware version 07.60.x.x. This firmware version (or higher) is installed on the array controllers prior to shipment and is delivered with Sun StorageTek Common Array Manager (CAM) v6.6.
To download the latest controller firmware, go to:
http://www.sun.com/storage/management_software/resource_management/cam
Click the “Buy Now” button to download the latest CAM software.
The CSM200 is the only expansion tray model supported by the Sun Storage 6180 Array. Refer to “Installing Firmware for Additional Expansion Modules” in the Sun StorageTek Common Array Manager Release Notes, v.6.6.0 or higher, for more information on the procedure to upgrade trays without data.
|
Caution - To add trays with data already on them, contact your service representative for assistance to avoid data loss. |
TABLE 1 lists the size, spindle speed, type, interface speed, and tray capacity for supported Fibre Channel (FC) and Serial Advanced Technology Attachment (SATA) disk drives for the Sun Storage 6180 Array. Additional legacy drives might also be supported with this product.
| Note - All disk drives supported in the Sun StorageTek 6140 Array are supported in the Sun Storage 6180 Array. |
The following list of supported disk drives replaces the listing in the Sun Storage 6180 Array Hardware Installation Guide.
This section describes supported data host software, HBAs, and switches.
This section provides a summary of the data host requirements for the Sun Storage 6180 Array. It lists the current multipathing software and supported host bus adapters (HBAs) by operating system.
You must install multipathing software on each data host that communicates with the Sun Storage 6180 Array.
For Solaris Operating System (OS) 9 data hosts, the multipathing software is part of the Sun StorageTek SAN Foundation software. Solaris OS 10 includes the multipathing software. For data hosts running supported versions of Solaris prior to Solaris OS 10, follow the instructions in the Hardware Installation Guide for Sun Storage 6180 Array to download and install the software from the Sun Download Center.
| Note - Single path data connections are not recommended. For more information, see Single Path Data Connections. |
TABLE 2 lists supported multipathing software by operating system.
|
STMS/MPxIO (see Special Instructions to Enable Multipath Failover for Solaris OS 9 Data Hosts) |
|||||
|
Update 6 or Update 5 with patch 140919-04 (SPARC), 140920-04 (x64/x86) |
|||||
| Note - The multipathing driver for the IBM AIX platform is Veritas DMP, bundled in Veritas Storage Foundation 5.0 for Sun Storage 6180 Array. Download the Array Support Library (ASL) from http://support.veritas.com/. |
2. Add the following entry to the /kernel/drv/ssd.conf file. This command sets the “not ready retries” count to 36.
ssd-config-list= "SUN SUN_6180", disk_to_modify; disk_to_modify=1,0x00004,0,0,36,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;
TABLE 3, TABLE 4, and TABLE 5 list 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:
http://www.sun.com/storagetek/storage_networking/hba/
You can download HBA drivers and other host software from the Sun Download Center at:
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.
|
Solaris 9[1] |
||||
|
Emulex LPe12000/LPe12002/LPe1250 |
||||
|
Emulex LPe12000/LPe12002/LPe1250 |
||||
The enterprise software applications listed in TABLE 7 are compatible with the Solaris OS on the data host.
The following FC fabric and multilayer switches are compatible for connecting data hosts and Sun Storage 6180 Array:
Network 2 Gb FC Switch - 8, 16, and 64
The following sections provide information about restrictions, known issues, and bugs filed against this product release. If a recommended workaround is available for a bug, it follows the bug description.
In a single path data connection, a group of heterogeneous servers is connected to an array through a single connection. Although this connection is technically possible, there is no redundancy, and a connection failure will result in loss of access to the array.
|
|
Caution - Because of the single point of failure, single path data connections are not recommended. |
CR 6846715: If you are connecting the Sun Storage 6180 Array to a data host running Solaris 9 OS, patch 122300-46 (SunOS 5.9: Kernel Patch) or higher is required for proper Vendor ID and Product ID (VID/PID) identification for the array.
Workaround: To download the patch from SunSolve, go to:
http://sunsolve.sun.com/patchfinder
1. In the Patch ID field, enter the first six digits of the patch ID and click Search.
Searching without the -xx patch ID suffix returns the most recent results.
2. Select a patch ID from the list.
It is recommended to use the most recent patches and the most recent revision of those patches.
Problem or Restriction: Windows Server 2003 only. When you configure a storage array as a boot device, the system shows a blue screen and does not respond when it is manually or automatically set to hibernate.
Workaround: If you use a storage array as a boot device for the Windows Server 2003 operating system, you cannot use the hibernation feature.
Problem or Restriction: Because of the potential conflict between a drive module intentionally set to 0 (zero) and a drive module ID switch error that causes a drive module ID to be accidentally set to 0, do not set your drive module ID to 0.
Problem or Restriction: Removing and reinserting drives during the drive firmware download process might cause the drive to be shown as unavailable, failed, or missing.
Workaround: Remove the drive, and either reinsert it or reboot the controllers to recover the drive.
Problem or Restriction: If you add a drive module by using the loop topology option during Environmental Services Monitor (ESM/IOM) firmware download, the ESM/IOM firmware download process might fail due to a disconnected loop. The drive module would come up correctly after being added to the loop.
Workaround: When adding the drive module, do not follow the loop topology option. If you add the drive module by connecting the ports to the end of the storage array without disconnecting the loop, the ESM/IOM firmware download is successful.
Problem or Restriction: Removing the drives while a storage array is online and then waiting to reinsert the drives until the storage array is starting after a reboot might cause the drives to be marked as failed after the storage array comes back online.
Workaround: Wait until the storage array is back online before reinserting the drives. If the storage array still does not recognize the drives, reconstruct the drives by using CAM software.
Problem or Restriction: After removing a second ESM/IOM from a storage array, the controller panics.
Workaround: After removing an ESM/IOM, wait at least 10 minutes before removing another ESM/IOM from the same storage array.
Problem or Restriction: When a Red Hat Enterprise Linux 5.1 host has more than two new volumes mapped to it, it hangs during reboot.
Workaround: Try three possible workarounds:
Problem or Restriction: Cache restore is attempted when the controller is attached to foreign drive modules, and there is data on the USB devices that the cache has not written to the drive modules.
|
|
Caution - Possible loss of data--Failure to perform this workaround could result in data loss. |
Before the power is turned off to the system, quiesce the system. You should quiesce the system before the controller or the drive module is moved. This process does not back up the cache, and it does not attempt to restore the data from the USB devices to the foreign drive modules.
Problem or Restriction: Linux. An I/O timeout error occurs after you enable a switch port. This problem occurs when two or more Brocade switches are used, and both the active and the alternative paths from the host are located on one switch, and both the active path and the alternative path from the storage array are located on another switch. For the host to detect the storage array on the other switch, the switches are cascaded, and a shared zone is defined between the switches. This problem occurs on fabrics managing high I/O traffic.
Workaround: Reconfigure the switch zoning to avoid the need for cascading. Limit the zones within each switch, and do not create zones across the switches. Configure the active paths from the host and the storage array on one switch, and all of the alternative paths from the host and the storage array on the other switch.
Problem or Restriction: With power-on diagnostics, some host interface card hardware defects are not found, including problems transferring data across the PCI express bus, interrupt failures, and issues with the internal buffers in the chip.
Workaround: Verify that the host interface cable connections into the Small Form-factor Pluggable (SFP) transceivers are secure. If the problem remains, replace the host interface card.
Problem or Restriction: An ancient I/O error is reported during a controller failure on a large configuration with more than 32 primary volumes on a single storage array.
Workaround: Configure large configurations with more than 32 primary mirrors on a single storage array, so that the metadata volume is contained in a pool that is made up of Fibre Channel drives. If Fibre Channel drives are not available, create a 1 + 1R1 SATA pool, so that it contains only the metadata volume with no other volumes on that pool.
You might be able to configure the metadata volume with other volumes on a SATA group if the pool will experience only a light I/O load. Because of the numerous variables involved, it is not possible to provide guidance on the load limits, so the risk would be assumed at the discretion of the user.
Problem or Restriction: Red Hat Enterprise Linux 5.2 PowerPC (PPC) only. On rare occasions, the host hangs during reboot.
Problem or Restriction: Windows Server 2003 only. No Automatic Synchronization MEL events are received when the controllers go through autocode synchronization (ACS) and a deferred lockdown.
Workaround: You must verify the firmware on the controllers.
Problem or Restriction: Linux Red Hat 5 and Linux SLES 10 SP1 only. After a controller failover in an open SAN environment, a controller comes back online, but the path is not rediscovered by the multi-path proxy (MPP). After a controller comes online in a fabric connection (through a SAN switch), it is possible that a link will not be established by the Emulex HBA driver. This behavior is seen only if the SAN switch is “default” zoned (all ports see all other ports). This condition can result in an I/O error if the other path is taken offline.
Workaround: Set all of the SAN switches to be “default” zoned.
Problem or Restriction: Linux SLES 10 SP2 only. I/O errors occur during a system reboot, and the host resets.
Problem or Restriction: AIX only. When you perform a firmware download with a heavy load, the download fails because the volumes take too long to transfer to the alternate controller.
Workaround: Execute the download again. To avoid this problem, perform the firmware updates during non-peak I/O activity times.
Problem or Restriction: Red Hat Enterprise Linux 4.7 only. When the controller is going through the start-of-day sequence, the drive channel does not achieve link speed detection and logs a Major Event Log (MEL) event. This event recovers within a few seconds, and a second MEL event occurs. The second MEL event indicates that the link speed detection was achieved.
Problem or Restriction: If the controllers are running firmware that uses 64-bit addressing, you cannot load firmware that uses 32-bit addressing if your storage array has these conditions:
Recent code changes have been implemented to fix a 32-bit addressing issue by using 64-bit addressing. After you have updated to a firmware version that uses the 64-bit addressing, do not attempt to reload firmware version that uses 32-bit addressing.
Workaround: If you must replace a firmware version that uses 64-bit addressing with a firmware version that uses 32-bit addressing, contact a Sun Technical Support representative. The Technical Support representative will delete all snapshots before starting the downgrade process. Snapshots of any size will not survive the downgrade process. After the firmware that uses 32-bit addressing boots and runs, no snapshot records will be available to cause errors. After the 32-bit addressing firmware is running, you can re-create the snapshots.
Problem or Restriction: This problem occurs when Internet Protocol Version 6 (IPV6) addresses have been disabled on a Sun Storage 6180 array. If the Internet Storage Name Service (iSNS) is enabled and set to obtain configuration data automatically from the Dynamic Host Configuration Protocol (DHCP) server, the IPV6 addresses will be discovered even though they were disabled on the ports of the controllers in the Sun Storage 6180 array.
Problem or Restriction: This problem occurs when you change the configuration for all of the ports in a storage array from using Dynamic Host Configuration Protocol (DHCP) to using static IP addresses or vice versa. If you are using Internet Storage Name Service (iSNS), the registration of the IP addresses for the ports will be lost.
Workaround: Use one of the following workarounds after you change the IP addresses:
Two problems exist in the documentation:
The Sun Storage 6180 documentation set contains discrepancies for certain array specifications.
Workaround: For the following specification categories, note the correct specification values.
50/60 Hz, 3.96 A max. operating @ 115 VAC, 2.06A max. operating @ 230 VAX (115 to 230 VAC range).
50/60 Hz, 3.90 A max. operating @ 115 VAC, 2.06A max. operating @ 230 VAX (90 to 264 VAC range)
The maximum weight of a fully populated controller or expansion tray is 93 pounds (42.18 kilograms).
The Sun Storage 6180 Array Hardware Installation Guide does not include an illustration of the optional DC Power connectors.
Correction--FIGURE 1 shows the location of the DC power connector and DC power switch at the back of each controller.
FIGURE 1 Sun Storage 6180 Array DC Power Option (Rear)
Related product documentation is available at the Sun documentation web site:
http://docs.sun.com/app/docs/prod/6180.array#hic
For translated versions of the documentation, go to the http://docs.sun.com web site, select your language, and search for the product documentation.
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.
Sun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by clicking the Feedback[+] link at:
Please include the title and part number of your document with your feedback:
Sun Storage 6180 Array Release Notes, Release 6.6, part number 821-1428-10.
| Sun Storage 6180 Array Release Notes, Release 6.6 | 821-1428-10 | |
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.