IBM System Storage™ DS4000 Storage Manager version 9.60 for Sun Solaris 8, 9, ,10, and 10 x86 operating systems. Note: Sun Solaris host attachment to the IBM 1722-all models (DS4300), 1724-all models (DS4100), 1742-models 90U/90X (DS4500), 1814-all models (DS4200 and DS4700) and 1815-all models (DS4800) requires additional purchase of an IBM DS4100/DS4200/DS4300/DS4500/DS4700/DS4800 Sun Solaris Host Kit Option. The IBM DS4000 Sun Solaris Host Kit options contain the required IBM licensing to attach a Sun Solaris Host System to DS4100, DS4200, DS4300, DS4500, DS4700 or DS4800 storage subsystems. Please contact your IBM service representative or IBM resellers for purchasing information. NOTE TO SERVICE – Reference RETAIN # N/A (C) Copyright International Business Machines Corporation 1999, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in section 6.0 "Trademarks and Notices” in this document. IMPORTANT: DS4000 Storage Manager version 9.19.xx.12 and later is required for DS4000 storage subsystem users in countries implementing the new Daylight Saving Time (DST) rules (which includes U.S., Canada, Bermuda). Storage Manager version 9.19.xx.12 or later release includes revised DST transition dates to comply with provision of the Energy Policy Act of 2005 extension of Daylight Saving Time (DST) by four weeks, beginning in year 2007. Please refer to section 1.3 Enhancements for more information. Refer to the IBM System Storage™ Support Web Site or CD for the IBM DS4000 Storage Manager version 9 Installation and Support Guides for AIX, HP-UX, Solaris and Linux on POWER. This guide along with the DS4000 Storage Manager program Online Help provide the installation and support information. Last Update: 12/10/2007 Please refer to corresponding Change History document for more information on new features and modifications. Products Supported ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, | | | | | 88A, 88H, 80A, 80H | |------------|-----------|--------------|------------------------| | DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, | | | | | 70T, 70S, 72T, 72S, | |------------|-----------|--------------|------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | FAStT 600 | 1722 | 6LX, 6LU, 6LJ, 60X | | | | | 60U, 60J, 60K, 60L | |------------|-----------|--------------|------------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | |----------- |-----------|--------------|------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | |----------- |-----------|--------------|------------------------| | N/A | FAStT 500 | 3552 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | N/A | FAStT 200 | 3542 | 1RX, 1RU, 2RX and 2RU | ------------ --------------------------------------------------- ATTENTION: 1. The DS4000 storage subsystem controller firmware version 05.40.xx.xx and earlier along with its associated NVSRAM files should not be loaded into DS4000 storage subsystems connected to DS4000 EXP100 drive expansion enclosures. 2. For the DS4400 and the DS4100 storage subsystems - all models (Standard /dual controller and Single Controller), the controller firmware version 06.12.xx.xx and later must be used. 3. For the DS4300 storage subsystems with Single Controller option, the controller firmware version 05.34.xx.xx and its associated NVSRAM file must be used. Do not attempt to download the controller firmware version 06.xx.xx.xx into these DS4300 storage subsystem models with single controller option. 4. For the FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models) storage subsystems, the controller firmware version 05.30.xx.xx and its associated NVSRAM file must be used. Do not attempt to download the controller firmware version 06.xx.xx.xx into these DS4000 storage subsystems. 5. For the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems connected to the DS4000 EXP810 drive expansion enclosures, the latest controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP810 drive expansion enclosure attachment. 6. For the DS4700 and the DS4800 storage subsystems connected to the DS4000 EXP100 drive expansion enclosures, the controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4700 and the DS4800 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP100 drive expansion enclosure attachment. CONTENTS -------- 1.0 Overview 2.0 Installation and Setup Instructions 3.0 Configuration Information 4.0 Unattended Mode 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer ======================================================================= 1.0 Overview -------------- 1.1 Overview -------------- This IBM Storage Manager package includes IBM DS4000 Storage Manager host software version 9.60 for Sun Solaris™. This version 9.60 of the DS4000 Storage Manager host software is required for managing the DS4200-all models, the DS4300-standard (dual controller) or Turbo models, the DS4500- all models, the DS4700-all models and the DS4800-all models with controller firmware version 06.60.xx.xx. In addition, it is also recommended for managing the following DS4000 storage subsystems - the DS4100-all models and the DS4400-all models with controller firmware version 06.12.1x.xx or higher installed. NOTE: DS4000 controller firmware versions 6.12.xx.xx or 06.15.2x.xx * Attachment support for EXP710 and EXP100 SATA disk drive expansion enclosures. * No attachment support for EXP810 disk drive expansion enclosure. DS4000 controller firmware version 06.16.xx.xx * Attachment support for EXP710, EXP810 and EXP420 disk drive expansion enclosures. * No attachment support for EXP100 SATA disk drive expansion enclosure. DS4000 controller firmware version 06.19.xx.xx * Attachment support for EXP710, EXP810, and EXP100 SATA disk drive expansion enclosures for DS4300 with dual controller and DS4500. DS4000 controller firmware version 06.23.xx.xx * Attachment support for EXP710, EXP810, and EXP100 SATA disk drive expansion enclosures for DS4300 with dual controller, DS4500, DS4700 and DS4800. IBM Storage Manager host software version 9.60 new features and changes are described in the corresponding Change History document. Please refer to this document for more information on new features and modifications. The IBM DS4000 Solaris Storage Manager Software and the DS4000 storage subsystem controller Firmware and NVSRAM files are available for download from the IBM System Storage™ DS4000 Support web site http://www.ibm.com/servers/storage/support/disk/. The IBM DS4000 System Storage Manager version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER is also available on IBM's Support web site as a downloadable Portable Document format (PDF) file. The latest versions of these files are available on IBM System Storage™ DS4000 Support web site as PDF files. IMPORTANT: This release of IBM DS4000 Storage Manager host software supports all DS4000 storage subsystems with general released firmware versions from 05.30.xx.xx up to 06.60.xx.xx. Refer to the IBM DS4000 Support Web Site for latest DS4000 controller firmware and NVSRAM files for IBM machine types 1722, 1724, 1742, 1814, 1815, 3542 and 3552. The following table shows the first four digits of the latest controller firmware versions that are currently available for various models of the DS4000 storage subsystems. --------------------------------------------------- | DS4000 Storage | Controller firmware version | | Subsystem Model | | |------------------|--------------------------------| |------------------|--------------------------------| | DS4800 (1815) | 06.60.xx.xx | | | | |------------------|--------------------------------| | DS4700 (1814) | 06.60.xx.xx | |------------------|--------------------------------| | DS4500 (1742) | 06.60.xx.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.56.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.60.xx.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.60.xx.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4300 Single | 05.34.xx.xx | | Controller Opt. | (for DS4300 SCU | | (SCU)(1722) | only) | |------------------|--------------------------------| | DS4200 (1814) | 06.60.xx.xx | |------------------|--------------------------------| | DS4100 (1724) | 06.12.56.xx | | (standard dual | | | Single | | | controller Opt.)| | | | | |------------------|--------------------------------| | FAStT500 (3552) | 05.30.xx.xx | |------------------|--------------------------------| | FAStT200 (3542) | 05.30.xx.xx | --------------------------------------------------- Note: Controller firmware 06.23.xx.xx or higher is required for the DS4300-standard-dual controller or Turbo models, the DS4500-all models, the DS4700-all models and the DS4800-all models for attaching combinations of EXP810 and EXP100 storage expansion enclosures behind a DS4000 storage subsystem. New features introduced with controller firmware version 06.60.xx.xx or later are not available for DS4000 controllers with older firmware versions installed. The following table describes controller firmware versions required for attaching various models of DS4000 Storage Expansion Enclosures. --------------------------------------------------------------------- | Controller | EXP Storage Expansion Enclosures | | FW Version |------------------------------------------------------| | | EXP100 | EXP420 | EXP500 | EXP700 | EXP710 | EXP810 | |------------|---------|--------|--------|--------|--------|--------| |5.3x.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.40.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.41.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.42.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.0x.xx | Yes | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.1x.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.12.xx.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.14.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.15.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.16.2x.xx | No | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.8x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.9x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.19.xx.xx | Yes | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.23.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.60.xx.xx | Yes | Yes | No | No | Yes | Yes | --------------------------------------------------------------------- Note: EXP500 and EXP710/EXP100 can not be attached behind the same DS4000 storage subsystem. In addition, the EXP500 can only be intermixed with EXP700 if the fibre channel speed of the EXP700 and the DS4000 subsystem drive loop is set to 1Gbps. ======================================================================= 1.2 Limitations ---------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by DS4000 storage subsystem controller firmware and Storage Manager host software releases to indicate which controller firmware and Storage Manager host software release that they were first seen and documented. New limitations with Storage Manager Installer (SMIA) package version 09.60.xx.05 release. None New limitations with Storage Manager Installer (SMIA) package version 09.60.xx.03 release. 1. For this release, support For Solaris 10 x86 is I/O attach only. No DS4000 Storage Manager version 9.60 Client is supported. To manage the DS4000 storage subsystems that are IO attached to your Solaris 10 x86 server hosts, you must install a supported DS4000 Storage Manager client software (SMclient) on a management workstation and manage the DS4000 storage subsystem via out- of-band management method. 2. CMVC 394913 - 131733 Storage Manager 9.60.x5.03 Installer does not import previous configuration used in the Enterprise Management Window when upgrading the Storage Manager host software version 9.23.xx.xx to 9.60.xx.03. This limitation is fixed in SMIA installer package version 09.60.x5.05 for Solaris. 3. IBM DS4000 Storage Manager RDAC for Solaris 8 and 9 only. New limitations with Storage Manager Installer (SMIA) package version 09.23.xx.02 release. 1. None New limitations with Storage Manager Installer (SMIA) package version 09.23.xx.01 release. 1. Not compatible with Controller firmware 06.12.56.00. 2. Reflected Fibre Channel (FC) OPN frames occurs when intermixing the EXP810, EXP710 and EXP100s behind DS4700 or DS4800 storage subsystems. This behavior causes excessive drive side timeout, drive side link down and drive side link up events be posted in the DS4000 storage subsystem Event log (MEL.) It might also cause drives to be by-passed or failed by the controller. NEW DRIVE SIDE FC CABLING REQUIREMENT MUST BE ADHERED TO WHEN HAVING EXP100 CONNECTED TO THE DS4700 OR DS4800 STORAGE SUBSYSTEMS. Please refer to the latest version of the Installation, User's and Maintenance Guide for these storage subsystems that are posted in the IBM DS4000 Support web site for more information. http://www.ibm.com/servers/storage/support/disk/ 2. If a DS4000 subsystem undergoes any operation that causes the controller to reset and go through the start-of-day boot process while you are running MPXIO, you may see IO errors. A retry of the IO when the controller has finished SOD will be successfull. SUN bug 6471522 is used for tracking this issue. Action required is to contact SUN. New limitations with Storage Manager Installer (SMIA) package version 09.19.xx.12 release. None. New limitations with Storage Manager Installer (SMIA) package version 09.19.05.06 release. 1. Can not increase the capacity of RAID arrays. RAID arrays with certain combinations of selected segment size and number of drives that made up the arrays will exceed the available working space in controller dacstore, causing a reconfiguration request (like expanding the capacity of the array) to be denied. These combinations are generally the largest segment size (512KB) with the number of drives in the array is 15 drives or more. There is no work-around. C324144 105008 2. Interoperability problem between the Tachyon DX2 chip in the DS4500 and the DS4300 storage subsystem controllers and the Emulex SOC 422 chip in the EXP810 expansion enclosure ESMs causing up to 5 Fibre Channel loop type errors to be posted in the DS4000 storage subsystem Major Event Log during a 24 hour period. There is a small window in the SOC 422 chip that multiple devices can be opened at one time. This ultimately leads to Fibre Channel loop errors of Fibre Channel link up/down, Drive returned CHECK CONDITION, and Timeout on drive side of controller. IBM recommends the use of the Read-Link-Status function to monitor drive loop for any problems in the drive loop/channel. There is no work-around. 3. The single digit of the Enclosure IDs for all enclosures (including the DS4000 storage subsystem with internal drive slots) in a given redundant drive loop/channel pair must be unique. For example, with four enclosures attached to the DS4300, the correct enclosure ID settings should be x1, x2, x3, and x4 (where x can be any digit that can be set). Examples of incorrect settings would be 11, 21, 31, and 41 or 12, 22, 32, and 62. These examples are incorrect because the x1 digits are the same in all enclosure IDs (either 1 or 2). If you do not set the single digit of the enclosure IDs to be unique among enclosures in a redundant drive loop/channel pair, then drive loop/channel errors might be randomly posted in the DS4000 subsystem Major Event Log (MEL), especially in the cases where the DS4300 storage subsystems are connected to EXP810s and EXP100s. In addition, enclosure IDs with same single digits in a redundant drive loop/channel pair will cause the DS4000 subsystem controller to assign a soft AL_PA address to devices in the redundant drive loop/channel pair. The problem with soft AL_PA addressing is that AL_PA address assignment can change between LIPs. This possibility increases the difficulty of troubleshooting drive loop problems because it is difficult to ascertain whether the same device with a different address or a different device might be causing a problem. 4. If a DS4000 subsystem undergoes any operation that causes the controller to reset and go through the start-of-day boot process while you are attempting to add hardware, drives, or logical drives associated with the controller, the controller will send alert event notifications to the DS4000 subsystem Major Event Log (MEL) Log. The events indicate that the drives or the logical drives are offline or failed. The event notifications in the MEL Log are expected during the time that the controller is going through a boot process. The workaround is to wait at least 10 minutes after the controller reset is complete before moving logical drives or adding hardware. Use the DS4000 subsystem MEL to verify the time of the last controller reset event. 5. In the DS4300 and DS4500 Installation, User's and Maintenance guides, there are references that might mislead the user into thinking that IBM does not support partially-filled storage expansion enclosures or storage subsystems. IBM does support partially-filled storage expansion enclosures or storage subsystems as long as at least two drives are installed in the storage expansion or subsystem enclosures. However, IBM does not support partially-filled storage expansion enclosures or storage subsystems where the empty slots are required to keep the number of hard drives in the redundant drive loop/channel pair not exceeding the maximum of 112 drives per drive loop/channel. This is to prevent inadvertently inserting drives in those slots causing the controller of getting into the state that might result in lost of access to the storage subsystem. 6. In DS4000 storage subsystem configurations with controller firmware 6.15.2x.xx and higher installed, the performance of write intense workloads such as sequential Tape restores to DS4000 Logical drives with large I/O request sizes (e.g. 256kB) is degraded if the DS4000 logical drives are created with small segment sizes such as 8KB or 16KB. The work around is to create the DS4000 logical drives with segment size of 64KB or higher. 7. In the DS4000 configurations with large number of hosts performing heavy IOs to the DS4000 LUNs, the Sun HBA in a server might log in to the controller but not turn the path to the LUNs online after the controller goes through a rebooting process. As a result, the server loses access to the DS4000 LUNs when the path to the alternate controller fails or the alternate controller reboots. Note: The controller can reboot itself when it needs to be re-synchronized with the other controller. Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.62 release None Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.44 release for the DS4000 controller firmware version 6.12.27.xx and 6.16.8x.xx 1. If the JNI Fibre Channel HBAs are installed in a Solaris host with RDAC being used as multipath driver, the hot_add utility might not discover new LUNs when they are added to an existing DS4000 storage partition. Workaround: Reboot the Solaris server to discover newly added LUNs. 2. RDAC multipath/failover driver is not supported in SUN Solaris 10 environment. The only supported multipath/failover driver in Solaris 10 is Veritas DMP. RDAC multipath/failover driver is supported in SUN Solaris 8 and 9 environments. 3. There is not support for SUN MPXIO multipath driver in any supported SUN Solaris operating system environments. Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.09 release for the DS4000 controller firmware version 6.16.24.xx None Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.08 release for the DS4000 controller firmware version 6.16.24.xx 1. Controller firmware 06.16.xx.xx does not support EXP100 storage expansion enclosures. Do not download it into DS4000 storage subsystems that have EXP100 enclosures attached. After the 06.16.xx.xx controller firmware is activated, the DS4000 storage subsystem will not recognize the drives in EXP100 enclosures, causing loss of data availability to the RAID arrays and logical drives that are defined in those drives. The controller firmware version 6.15.xx.xx and earlier must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 2. The storage subsystem might not recognize the drives or drive expansion enclosure correctly which results in the displaying of error messages or the inability to perform storage subsystem management operations, such as creating logical drives or arrays or initializing arrays from the storage management software. This behavior could be caused by powering up a DS4000 storage subsystem without any drive expansion enclosures attached and then connecting one or more drive expansion enclosures to the storage subsystem after it completes boot process. The workaround is to make sure that the drive expansion enclosure(s) with at least two drives are connected to the DS4000 storage subsystem before you turn on the storage subsystem power. 3. Remove the drive(s) while the storage subsystem is online and then wait until the storage subsystem is going the boot process following a storage subsystem reboot event to reinsert the (new) drive(s) might cause the drives to be marked as failed after the storage subsystem completes the boot process. The workaround is to wait until the storage subsystem is back online before reinserting the drives. If the storage subsystem still does not recognize the drives, reconstruct the drives by using the Advanced -> Recovery -> Reconstruct menu function in the storage subsystem management window. 4. Uninstalling the storage manager host software package might leave the JAVA JRE directory behind. This problem might occur if you uninstall a copy of the SANtricity Storage Manager software that has been upgraded from a previous release. The newer installation package could not delete the JRE directory created with an older installation package. The workaround is to manually delete any directories left behind after uninstalling the software. 5. When creating remote logical drive mirrors through the SMCli script engine in the DS4000 Storage Manager client program, the following error might display during execution, stopping the remote logical drive mirror creation process: Error 173 - The operation cannot complete because the configuration number on the remote storage array is invalid. Some remote logical drive mirrors might have already been created. Rerun only the portion of the script that should be run to finish creating the rest of the remote logical drive mirrors. 6. A JavaScript error might cause the Glossary pop-up window to stay open when the help contents on the storage management software GUI are closed and reopened. Workaround None. This is a SUN JAVA defect. 7. After creating a maximum number of logical drives that include remote volume mirroring (RVM) logical drive pairs and FlashCopy, logical drive transfer occurs when two Solaris hosts, running with VERITAS Volume Manager 4.0, are rebooted. Because SMagent is responsible for the volume transfer, perform one of the following actions as a workaround: • Unmap the Access Volume Logical Unit Number (LUN) in the mapping view (the Access Volume is usually LUN 31), and then reboot the hosts. • (Recommended method): After each host reboots, type the following command to stop the SMagent: # SMagent stop 8. A host port might fail to reinitialize after a switch port failure. This condition will cause I/O errors if the second port fails. The workaround to reinitialize the host port manually by resetting the HBA host port from the host server. 9. If you use QLogic HBAs with driver version 4.17 on a Sun Fire V440 server, a system panic could occur. There is not any workaround besides do not use QLogic HBAs in a Sun Fire V440 server. 10. After you select a file on the firmware download or NVSRAM download dialog, double clicking on “..” in the dialog no longer moves the directory back one level. The workaround is do not select a firmware file until you are finished navigating through your directory structure. 11. (Solaris 9 and later) VERITAS DMP 4.1 could not access target 0 and LUN 0 after the QLogic QLA23xx driver is installed. The path to the device is available, but the VERITAS software is unaware of the device because of an entry in the sd driver configuration file. Workaround Edit the configuration file by using this procedure: a. Log on to the host as “root.” b. Change to the /kernel/drv directory. c. Open the sd.conf file, and locate the following line within the file: name=”sd” parent=”qla2300” target=0; d. Edit the target value from 0 to 2048 as shown here: name=”sd” parent=”qla2300” target=2048; e. Save the file, and reboot the host. NOTE: This information can also be found on QLogic’s web site as a technical bulletin called “Solaris No Path to Target0 LUN0” (TBU05004) 12. A node in a cluster running Sun Cluster 3.1 panics with a reservation error after a drive or controller failure. The reservation errors are caused by persistent reservation keys that stay in place on logical drives associated with controllers that fail repeatedly. There is no workaround. 13. All nodes in a cluster running Sun Cluster 3.1 will panic with a “Cluster lost operational quorum” error message if the node owning the MPxIO-enabled quorum is taken offline. This is a problem if the ssd driver patch is at level 113277-28 or later. The workaround is to make sure that one does not install a patch to the ssd driver to level 113277-28 or later on nodes in an MPxIO enabled quorum. 14. A controller taking a long time to complete the start-of-day (SOD) boot process or placed in Service mode could cause the ssd driver to time- out and send fatal errors to the host. This problem could lead to I/O errors. There is no workaround. 15. The device node name entries in VERITAS Volume Manager (after using the command vxdisk list, for example) might be incorrect after a change has been made to the devices in the fabric topology. This problem could cause inconsistent disk usage and possible I/O errors. The workaround is to run the vxdiskadm utility and choose option 20 to force VERITAS Volume Manager to update its device node name entries. Run the utility a second time to restore the disknaming conventions. 16. A host using the MPxIO failover driver reports INQ-83 errors, which means that the storage subsystem did not return the correct logical drives World Wide Name (WWN) to the host in the allocated time. To correct this problem, you must force the host to rescan the affected path for the devices by using the following procedure: a. Have VERITAS Volume Manager rescan for disks by entering the following command: vxdisk scandisks # b. Make sure that all paths are optimal and available by using the following command: vxdisk list # c. Find the affected path by sending the following command: luxadm fcode_download -p d. After the path address is known, force a LIP to cause a link initialization on the affected port using this command: luxadm -e forcelip NOTE: If running this procedure does not correlate devices and WWNs, reboot the host. 17. After a host reboot, the following error message might appear during vxdctl enable or vxconfigd startup. These error messages are harmless and can be ignored. get_geometry_info_common: /dev/vx/rdmp//fabric_331 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_331 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_330 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_330 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_332 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_332 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_328 fmt_page_code failed. ret 0x5 get_geometry_info_common: /dev/vx/rdmp//fabric_328 fmt_page_code failed. ret 0x5 18. Several logical drives on a storage array are configured to use MPxIO, but the access logical drive on the storage array is not. If an event triggers a reboot of a controller, it might cause all of the logical drives, except the access logical drive, to come back online. The workaround is to use the luxadm utility to bring the access logical drives back online, or force the host to rescan for devices. As an example, you could use this command: luxadm -e online Note: See the luxadm man page for more information about using this command. 19. (Solaris 8 and 9) A link failure event (such as a controller failure) does not trigger VERITAS DMP 4.1 to fail over to the alternate path on the Solaris 8 or 9 operating system. After this event occurs, it is possible that I/O might not continue to be written to the logical drives on the storage subsystem, and the host will not report any I/O errors. The workaround is to trigger another failover event to move the volumes back to their preferred owners. If this does not work, reboot the host to clear the error. 20. After setting up a VERITAS Cluster Server (VCS) service resource group, a resource switch to the other node might fail and possibly cause data corruption. Future import operations might also fail and the vxdisk list command outputs the disk with the "altused" tag. The workaround is do not use fencing with VCS. 21. VERITAS DMP will not work while the controllers are in service mode because DMP relies on Automatic Logical Drive/Volume Transfer (ADT/AVT) to move the logical drives to the controller that receives the I/O requests. When a controller is in service mode, the controller is not capable of successfully completing the I/O requests. Since the path to that controller is not "broken," DMP has no knowledge to fail over to the alternate controller. The I/O request gets retried repeatedly until the I/O timeout period has been reached and the request times out. NOTE: Any failover driver that relies on ADT/AVT has this limitation. 22. If persistent reservations are enabled, the VERITAS DMP failover driver might fail to detect the path to the controller after a start-of-day operation or a controller reboot. This results in I/O failures. The workaround is to disable persistent reservations if you are using VERITAS DMP. 23. If a cable is disconnected from a storage subsystem, the HBA driver on the host might fail to detect the offline path correctly because VERITAS DMP does not mark the offline path as disabled. This results in I/O activity not getting through to the correct volumes, and the VERITAS DMP path scanning daemon vxdctl enable stops responding. There is no workaround. 24. A split-brain condition (when one node survives and the other must be shut down, which can cause data corruption) might occurs when a Solaris host fails to correctly register with VERITAS vxfendg disks. The workaround is to clear the keys manually using the vxfenclearpre command when you encounter a split-brain condition. This command will remove Small Computer System Interface 3 (SCSI-3) registrations and reservations on the coordinator disks, as well as on the data disks in all shared disk groups. NOTE: Clearing the keys manually does not always work; sometimes it is necessary to bring all nodes down. To clear keys manually, perform the following steps: a. Shut down all other systems in the cluster that have access to the shared storage. This prevents data corruption. b. Start the script: # cd /opt/VRTSvcs/vxfen/bin # ./vxfenclearpre c. Read the script’s introduction and warning. Then, you can choose to let the script run. Do you still want to continue: [y/n] (default : n) y Note: Informational messages resembling the following might appear on the console of one of the nodes in the cluster when a node is ejected from a disk or LUN: scsi: WARNING: /sbus@3,0/lpfs@0,0/sd@0,1(sd91): Error for Command: Error Level:Informational scsi: Requested Block: 0 Error Block 0 scsi: Vendor: Serial Number: 0400759B006E scsi: Sense Key: Unit Attention scsi: ASC: 0x2a (), ASCQ: 0x4,FRU: 0x0 You may ignore these informational messages. Cleaning up the coordinator disks... Cleaning up the data disks for all shared disk groups... Successfully removed SCSI-3 persistent registration and reservations from the coordinator disks as well as the shared data disks. Reboot the server to proceed with normal cluster startup... # d. Restart all systems in the cluster. 25. If a host using the MPxIO failover driver cannot access all logical drive information during start-of-day, the storage array could go into a “silent” degraded mode. The problem causes the “logical drive not on preferred path” error to be logged if a forced failover has occurred. In this mode of operation there is no failover protection on the host and any event that causes disruption on the remaining path would cause I/O failures. In order to correct this problem, you must force the host to rescan the affected path for the devices. The following options can be done: • Remove the cable to the affected HBA port and reinsert it after 30 seconds. • Find the affected path by sending the following command: luxadm fcode_download -p After the path address is known, force a LIP to cause a link initialization on the affected port using this command: luxadm -e forcelip 26. During failover, the operating system might encounter a busy status from the storage subsystem. If the busy status is received after another storage subsystem status, the host might inadvertently fail I/O. To check if “busy too long” has been logged on the host, check the /var/adm/messages file using this commend -> grep “busy too long” /var/adm/messages. Please contact IBM Support for a status of a fix for this problem. Limitations with SMIA package version 09.15.xx.06 release for DS4000 controller firmware version 06.12.xx.xx and 06.15.xx.xx release 1. The following error message may be encountered under certain conditions when attempting to create a 2 TB LUN using the Create Logical drive wizard in the Subsystem Management window: "Error 4 - The operation cannot complete because of an incorrect parameter in the command sent to the controller." To avoid this error message, you must take certain steps while using the Create Logical Drive wizard to create a 2 TB LUN. Within the Specify Capacity/Name window within the create logical drive wizard, you must not manually specify the numeric value '2' in the New logical drive capacity field in tandem with the "TB" Units designator. If you do this, the Error 4 message will be issued and you will be unable to create the 2 TB LUN. Click on the up or down arrows next to the input field to select the desire capacity instead. When using the arrows, the program will display the correct maximum logical drive capacity value that can be specified for a given capacity unit (TB, GB, or MB). Limitations with SMIA package version 9.15.xx.xx and DS4000 controller firmware version 06.15.xx.xx release None Limitations with SMIA package version 9.14.xx.05 and DS4000 controller firmware version 06.14.xx.xx release None Limitations with SMIA package version 9.12.xx.08 and DS4000 controller firmware version 06.12.03.xx release 1. Do not cut and paste the information in the DS4000 Storage Manager online help into the DS4000 Storage Manager script command window or into the text file that will be used as input for the SMcli script engine. Extra space may be inserted in the required parameter names which will cause error(s) during the script command execution. (267873) 2. In the configuration that have both SATA-technology drives (EXP100) and Fibre-Channel technology drives (EXP700/EXP710/DS4100) behind the same DS4000 storage subsystem, do not download drives firmware to both SATA-technology drives and Fibre-Channel(FC) technology drives at the same time. Download the drive firmware to drives of a single drive technology (either SATA or FC) at a time. 3. Currently, IBM does not support Gold key Premium Feature as a chargeable upgrade. The Gold key Premium Feature is enable or disable depending on the DS4000 storage subsystem models. 4. The Asynchronous Remote Mirroring utility, asyncRVMUtil, is not supported. This utility is used to automatically synchronize the logical drives in the Remote Mirroring pairs. Please contact IBM representatives or resellers for the support of this utility in the future. 5. Do not add drive expansion enclosure(s) to the DS4000 storage subsystem drive loops/channels during the ESM firmware download. The ESM firmware download process might fail due to a disconnected FC loop. Either add the drive expansion enclosure(s) before initiating the ESM firmware download or wait until the ESM firmware download is completed before adding additional drive expansion enclosures to the drive loop/channel. (added 2/10/2006) 6. Small Form-factor Pluggable (SFP) hardware that is removed and then reinserted within 10 seconds might not be recognized by the controller. Device polling is done at 10-second intervals. Any device that is removed and replaced within the 10-second window will not be recognized. After removing SFP hardware, ALWAYS wait at least 20 seconds before replacing or reinserting it. (added 2/10/2006) 7. When connected through the DS4000 Storage Manager Agent and mapped volumes using Storage Partitioning on an in-band managed storage subsystem, the following error message might appear after a successful volume-to-LUN mapping operation: Error 62 - The operation cannot complete because the logical unit number (LUN) is already in use. Please enter another LUN. Verify that the volume-to-LUN mapping was created correctly. If it was, this error is erroneous and can be ignored. (added 2/10/2006) 8. After you disable a premium feature, the Disable Premium Feature dialog might go blank and no longer show any other enabled premium features to select. The workaround is to close and then re-open the dialog. (added 2/10/2006) 9. Removing the Ethernet network cable from a Solaris host while the DS4000 Storage Manager Agent software is running could cause networking problems that subsequently cause the screen refresh problems in DS4000 Storage Manager client program. The dialog windows will go blank for any functions that need access to files on the host, including downloading firmware files, saving profiles, saving error information, and so on. Do not remove the network cable from the Solaris host while the Storage Manager Agent software is running. (added 2/10/2006) Limitations with Storage Manager version 9.10.xx.05 and DS4000 controller firmware version 06.10.11.xx release 1. Do not update the DS4000 storage subsystem controller firmware to version 06.1x.xx.xx from versions 05.4x.xx.xx or earlier if the exp700 esm firmware of the attached exp700 was not at 9326. If the EXP700 ESM firmware is earlier than the 9326 versions, the EXP700 enclosure and the installed drives may not be displayed in the DS4000 subsystem management window after the controller firmware is upgraded to 06.1x.xx.xx version. The workaround is to update the EXP700 ESM firmware to the 9326 version first before upgrading the controller firmware to version 06.1x.xx.xx. (260160 - 82841) 2. When connecting the EXP100 drive expansion enclosures, one must set the single digit (X1) of the enclosure ID to unique values. This is to prevent the possibility that one of the drives in the EXP100 enclosures be assigned the same ALPA as the DS4000 controller blade under certain DS4000 storage subsystem reboot scenarios. (261188) Limitations with Storage Manager version 9.10.xx.02 and DS4000 controller firmware version 06.10.06.xx release 1. The DS4000 Copy Service RVM is not supported at this time for the DS4100 and the DS4300 storage subsystem with Standard or Single Controller options. (Note: With the release of the controller firmware version 06.12.16.00 or higher, the DS4100 with standard option is now supported Copy Service Remote Mirroring and VolumeCopy premium features.) 2. In the Storage Manager version 9 client Subsystem Management window, the preferred owner of a defined logical drive can not be changed if the logical drive is not managed by the preferred owner/controller. The Storage Manager client will grey-out (not allowing one to select) the controller that is currently managing the logical drive in the selection list of the new preferred owner/controller. One is allowed to only select the controller that is not managing the logical to be the new preferred owner. There is no work-around. 3. Concurrent firmware download (downloading firmware/NVSRAM to the DS4000 storage subsystem controllers with IOs to the host servers) is not supported when upgrading the controller firmware from a 05.xx.xx.xx version to a 06.1x.xx.xx version. ALL IOs must be stopped during the version 06.1x.xx.xx controller firmware upgrade from a 05.xx.xx.xx version. Note: For Sun Solaris hosts, concurrent firmware download is supported only when upgrading controller firmware between a 05.40.xx.xx version to another 5.40.xx.xx version, from a 05.41.5x.xx version to another 5.41.5x.xx version or from a 05.42.xx.xx version to another 5.42.xx.xx version or from a 06.1x.xx.xx version to another 6.1x.xx.xx version. 4. Do not pull or inserting drives during the drive firmware download. In addition, ALL IOs must also be stopped during the drive firmware download. Otherwise, drives may be shown as missing, unavailable or failed. 5. Controller diagnostics will not run in a DS4000 storage subsystem with single controller. 6. When instructed to remove and reinsert or to replace a hard drive, wait at least 70 seconds before inserting either the removed existing drive or the new drive into the drive slot. Then, wait up to 3 minutes for the drive to be spun up, recognized by the DS4000 storage subsystem and displayed in the Subsystem Management window before repeating the process for another hard drive. There is no work-around. Similarly, wait at least 70 seconds before reinserting either the removed existing ESM module or the new ESM module into the empty ESM slot in the EXP drive expansion enclosure. Then, wait up to 3 minutes for the ESM CRU to be recognized by the DS4000 storage subsystem and displayed in the Subsystem Management window before repeating the process for another ESM. There is no work-around. 7. Staged firmware and NVSRAM download function is not available on the DS4400 (machine type 1742) models with firmware 06.1x.00.00 in conjunction with IBM Storage Manager 09.1x.xx.xx. 8. Veritas DMP version 4.0 is not supported with Storage Manager version 9.10.xx.02 and controller firmware version 06.10.xx.xx. It is supported Storage Manager version 9.12.xx.xx and higher in conjunction with controller firmware version 06.12.xx.xx and higher. Limitations with Storage Manager version 8.4x.xx.xx (and earlier) and DS4000 controller firmware version 05.4x.xx.xx (and earlier) releases 1. Host groups can not be created at the default group level. Host groups MUST be created at the storage system level. If the storage partitioning premium feature is not enable, the default host group must be set to the correct host type. 2. RDAC and dynamic multipathing (DMP) coexistence is not supported. 3. Dynamic multipathing (DMP) requires the installation of VERITAS Volume Manager. 4. Dynamically changing the cache read ahead multiplier setting via the storage manager client may result in an error message indicating the operation has failed. Despite the error message, the request to change the cache read ahead multiplier will remain queued to the controllers and will eventually complete when I/O activity to the storage subsystem has subsided. In order to avoid the error message and any delays in the cache read ahead multiplier value changing, it is recommended to change the cache read ahead multiplier when the subsystem is in a quiesced state. 5. This following behavior applies for the direct Fibre Channel connection setup between the DS4300 storage subsystem host ports and the server HBA ports only. If all DS4300 host ports are occupied, the DS4300 event log may show "host-side data rate negotiation failed" error when the server is booted up, this is normal error that were generated during the host rate negotiation routine inside the DS4300 storage subsystem. 6. When configuring DS4000 Logical volumes to be used with Veritas Volume Manager on Solaris, the maximum capacity per disk is limited to 999GB. For 1024GB disk group support using Veritas Volume Manager, it is recommended to use multiple disks of sizes less than 999GB. 7. When managing the DS4000 storage subsystems with firmware version 05.3x.xx.xx, the Help window of the Subsystem Management window may not be displayed correctly the topics that are listed as result of executing a full text search. 8. When migrating array(s) from a dual controller DS4000 storage subsystem to a single controller DS4000 storage subsystem, you must first set the preferred owner of the to-be-migrated array(s) to be controller A before inserting it into the drive slots of a single controller DS4000 storage server. Otherwise, the array(s) will not be added to the single controller DS4000 storage subsystem correctly which might cause problems. 9. When managing a single controller DS4000 storage subsystem model, do not use the menu option - Configuration->Automatic... - in the Subsystem Management window to create LUNs. You might not be able to access or manage LUNs that are created this way. 10. After you replace a controller with a new controller in the single controller models of DS4000 storage subsystems, the premium features become unauthorized and are out of compliance. Any premium features not supported by the firmware of the new controller are unavailable. The work- around is to upgrade the firmware in the new controller to the same level as the removed controller and re-enable the premium features using the key files that you were provided when the premium feature was originally enabled. 11. When you migrating drive Customer Replaceable Units (CRUs) from multiple DS4000 storage subsystems into a single destination DS4000 storage subsystems, all of the drive CRUs from the same DS4000 storage subsystem should be moved as a ‘set’ into the new destination DS4000 storage subsystem. Before moving the next ‘set’ of drive CRUs, ensure that all of the drive CRUs for a single ‘set’ have been moved to the destination DS4000 storage subsystem. If drive CRUs are not moved as a ‘set’ to the destination DS4000 storage servers, the newly relocated array may not appear in the Subsystem Management window. 12. Enclosure IDs may be listed incorrectly in the Subsystem Management window, even if the Enclosure ID switch settings appear to be correct. This is because of the physical design and movement of the Enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which will return an incorrect Enclosure ID (this value is 0 in most cases) to the storage management software. When setting the Enclosure ID, ensure that the switch has actuated completely and has settled where the value is clearly visible in the viewing window. 13. To download controller firmware, you must select the drive where the firmware is located. If the drive you select does not respond, the File Selection dialog box will revert to the A: drive and display an error message that drive A: is not ready if there are no media in drive A:. 14. You must suspend all I/O while ESM firmware downloads if you select multiple enclosures for downloading ESM firmware. If you select only one enclosure for download at a time, you can download ESM firmware with I/Os. However, IBM recommends that you suspend all I/O activity to perform firmware upgrades. 15. If the EXP100 ESM firmware version is 953x or earlier, no IOs are allowed during the duration that the EXP100 ESMs are being updated with new firmware, including clustering reservation checking IOs. 16. The DS4000 storage subsystem when configured with the DS4000 EXP100 SATA Drive Expansion Unit is currently reporting a higher frequency of informational events such as Destination Driver Events (DDEs) and FibreChannel link up/down events ... in the DS4000 Controller event log compared to the DS4000 storage subsystem configured with Fibre Channel drives. Slower response times of SATA disk drives compared to Fibre Channel disk drives cause higher I/O retries from the DS4000 storage subsystem controllers, resulting in a greater number of informational events logged. In addition, the number of information events reported in the DS4000 storage subsystem event log will also grow in proportion to the increase in I/Os to the Logical Drives. In all cases, the DS4000 storage subsystem controller will always successfully service the timeout I/O on the subsequent retries. 17. When saving the DS4000 storage subsystem event log entries, it may take up to several minutes to save all entries in the event log depending on the DS4000 management workstation resources. However, the DS4000 Storage Manager client GUI will show the completion of the event log saving almost instantly. The work around is to check the file size of the file that the event log entries are saved periodically; if the file size does not change, the event log saving is completed. 18. Do not perform other storage management tasks, such as creating or deleting logical drives, reconstructing arrays, and so on, while downloading the DS4000 storage subsystem controller firmware and DS4000 EXP ESM firmware. It is recommended that you close all storage management sessions (other than the session that you use to upgrade the firmware) to the DS4000 storage subsystem that you plan to update. 19. VERITAS Volume Manager with Dynamic Multipathing (DMP) for Sun Solaris is not support for FASTtT100 storage subsystem. Please contact IBM resellers or representatives for the availability of such support in the future. 20. Interoperability with tape devices is supported on separate HBA and switch zones. 21. Interoperability with IBM Enterprise Storage Server and SDD multipath device driver is supported on separate HBA and switch zones. 22. If a Solaris host is equipped with JNI HBAs, controller reboots cause a transfer of ownership to the alternate controller. There is no workaround. This is the way JNI HBAs are designed to function. You can change back ownership by using the storage management software. (2/10/2006) 23. When the host has a single Fibre Channel connection from a JNI HBA to the host-side minihub of the storage subsystem, a situation might occur after controller reboot where the HBA locks up and fails to initialize the connection. Communication to that storage subsystem controller is lost. The workaround is to use a fabric switch topology instead of a direct Fibre Channel connection. (2/10/2006) ======================================================================= 1.3 Enhancements ----------------- The DS4000 Storage Manager version 9.60 host software for Sun Solaris operating systems in conjunction with controller firmware version 6.60.xx.xx provides supports for - The management of the IBM System Storage DS3300 with controller firmware version 6.50.xx.xx installed. - Support for DS4000 Controller Firmware 6.60.xx.xx. In addition, it also provides - Support for the new Daylight saving time as required by the enactment of the United State's Energy Policy Act of 2005. The Daylight Saving Time (DST) will begin at 2 a.m. on the second Sunday in March and end at 2 a.m. on the first Sunday of November instead of 2 a.m. on the first Sunday of April to 2 a.m. on the last Sunday of October. For the year of 2007, DST will start on March 11, 2007 and end on November 11, 2007. DS4000 storage subsystem users in countries implementing the new DST rules (which includes U.S., Canada, Bermuda) are recommended to upgrade to Storage Manager version 9.19.xx.12 or later before March 2007. Storage Manager version 9.19.xx.12 or later release includes revised DST transition dates to comply with provision of the Energy Policy Act of 2005 extension of Daylight Saving Time (DST) by four weeks, beginning in 2007. There are no data integrity or functional problems caused by an incorrect clock setting. From the DS4000 controller firmware standpoint, this change will have no impact. The software changes are in the Java Runtime software included with the Storage Manager host software. The DS4000 controller uses an internal time clock which is GMT time based. The Storage Manager client software will make the appropriate time changes for reporting the Major Event Log entries (MEL), subsystem information or subsystem configuration changes in the time zone that the management station is installed. If no updates are made to existing DS4000 Storage Manager host software. The primary impact is that Email alerts and Major Event Log (MEL) entries will be off by 1 hour for 3 weeks in the Spring and 1 week in the Fall because they will be translated improperly by the Java Runtime Engine that is currently in use. This is a cosmetic impact only; as noted above, all times within the DS4000 controller firmware are stored in GMT time. Such values will be incorrect for the three-week period but then will be correct later when viewed from DS4000 Storage Manager client software. Additional incorrect timestamps may be seen in diagnostic reports, various subsystem component information displayed in dialog boxes, and performance monitor. In addition to updating the DS4000 Storage Manager host software, additional operating systems patches may be needed for the host server/management station that the DS4000 Storage Manager host software is installed. This will ensure that no problems occur with the implementation of the new DST rule. Please refer to the support web site for your operating systems for more information. Various impact scenarios are described below: Host System DS4000 Impact Operating Storage System Manager No Update No Update The System and DS4000 Controller time stamps are in sync until March 11, to April 1, when the times are 1 hour earlier than the time in the areas where the change is effective. Updated No Update The system and DS4000 controller time stamps will be out of sync by 1:00 hour. For example, a MEL event at 3:00 p.m. on the system will be reported as 2:00 p.m. on the DS4000 MEL logs Not Updated Updated Same as above, except the DS4000 Storage Manager will report with the correct DST time. Updated Updated Best scenario. Everything reports the correct time Please refer to the New Features section of the IBM DS4000 Storage Manager version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER for additional information about the IBM DS4000 Storage Manager version 9 enhancements. ======================================================================= 1.4 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- Note: The IBM Storage Manager host software version 9.60 for Solaris OS new features and changes are described in the corresponding Change History document. Please refer to this document for more information on new features and modifications. This release of IBM DS4000 Storage Manager host software for Sun Solaris was tested on the following Sun servers and Operating System configurations: The minimum requirement is a Sun server with PCI and/or S-Bus Architecture with: 1. 1 GB system memory. 2. 480 Mhz Processor 3. Ethernet network interface card. 4. CDROM drive. 5. Mouse or similar pointing device. For SMclient, at least 150 MB of available on /opt and root-level (superuser) permission is required for installation Ensure the storage management station or the host acting as a storage management station is running one of the following operating systems: 1. Solaris 8.0 a. Solaris 8 Recommended Patch Cluster (108528-18,111293-04,111310-01,111111-03,108987-12) b. Solaris 8 Maintenance Update (MU) 7 Sun's latest recommended patches and security patches c. 117350-39 2. Solaris 9.0 a. 113454 SunOS 5.8 (v.14 or higher) b. Solaris 9 Maintenance Update (MU) 4 Sun's latest recommended patches and security patches c. 118558-29 3. Solaris 10.0 a. 118855-19 4. Solaris 10.0 x86 a. 118855-36 5. The DS4000 Storage Manager version 9.14 and higher host software installer wizard requires the installation of a graphics adapter in the SUN Solaris server for it to run. For SUN Solaris servers without the graphics adapter, individual host software installation packages are provided in the DS4000 Storage Manager Version 9.1x (where x is an appropriate release version like 9.14, 9.15, ... ) Support for SUN Solaris OSes CD under the directory named "/Solaris/Individual packages". These individual host software installation packages can also be downloaded at the IBM System Storage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ Code levels at time of release are as followed ------------------------------------------------- Starting with the DS4000 storage manager version 9.12, all of the host software packages are included in a single DS4000 Storage Manager host software installer wizard. During the execution of the wizard, the user will have a choice to install all or only certain software packages depending the need for a given server. The version of the host software installer wizard for this release is SMIA-SOL-09.60.05.05.bin. IMPORTANT: The DS4000 Storage Manager host software installer wizard requires the installation of a graphics adapter in the Solaris server for it to run. This wizard will install the following version of the host-software packages 1. IBM DS4000 Storage Manager RunTime version: 09.16.05.02 2. IBM DS4000 Storage Manager Client version: 09.60.G5.04 3. IBM DS4000 Storage Manager RDAC version: 09.10.05.01 IMPORTANT: In Solaris servers that are IO attached to the DS4700 and DS4800 storage subsystems using RDAC as multipath/failover driver, a RDAC patch version R789.091005-01 must be installed after the RDAC installation. This RDAC patch is included along with other DS4000 storage manager host software packages for SUN Solaris. 4. IBM DS4000 Storage Manager Agent version: 09.16.05.06 5. IBM DS4000 Storage Manager Utilities version: 09.16.05.06 In addition, for DS4000 configurations with SUN Solaris servers using Veritas Volume Manager (DMP) as multipath driver, you have to obtain the correct asl file for DS4000 storage subsystems using the following Veritas Support URL. http://seer.support.veritas.com/docs/275752.htm For SUN servers without the graphics adapter, individual host software installation packages are also provided in the sub-directory named "Individual packages". These individual host software installation packages can be downloaded at the IBM System Storage™ Disk Storage Systems Technical Support web site. Refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released code levels. Note: A supported IBM SAN FC Switch is required when attaching DS4000 storage subsystems to AIX and non-AIX servers in a Heterogeneous environment. ======================================================================= 1.5 Dependencies ----------------- ATTENTION: 1. DS4000 storage subsystem CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP700 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 9326 OR HIGHER. IF THE EXP700 ESM FIRMWARE IS EARLIER THAN THE 9326 VERSIONS, THE EXP700 ENCLOSURE AND THE INSTALLED DRIVES MAY NOT BE DISPLAYED IN THE DS4000 SUBSYSTEM MANAGEMENT WINDOW AFTER THE CONTROLLER FIRMWARE IS UPGRADED. THE CURRENT RELEASE ESM FIRMWARE VERSION FOR THE EXP700 ESM IS 9330. 2. DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X WHEN THE CONTROLLER FIRMWARE IS AT 06.1X.XX.XX. TO DETERMINE THE FIRMWARE LEVEL OF AN EXP100 ESM, IDENTIFY THE PRODUCT LABEL LOCATED AT THE REAR OF THE EXP100 ENCLOSURE. ONLY LABELS ON WHICH THE FIELD REPLACEABLE UNIT (FRU) PART NUMBER READS 25R0156 POSITIVELY INDICATE THAT AN ESM MODULE IS RUNNING FIRMWARE VERSION 955X OR HIGHER. IF THERE IS NO LABEL OR THE PART NUMBER ON THE LABEL DOES NOT READ 25R0156, THE ESM MAY STILL HAVE THE FIRMWARE VERSION 955X OR HIGHER IF IT HAD BEEN PREVIOUSLY UPGRADED. IF NECESSARY, CONTACT YOUR IBM REPRESENTATIVE, SUPPORT, OR RESELLERS FOR ASSISTANCE. IN ADDITION, IT IS NOT POSSIBLE TO UPGRADE THE ESM FIRMWARE FROM VERSION 953X TO VERSION 956X OR LATER DIRECTLY. THE 953X ESM MUST BE UPGRADED TO VERSION 9554 FIRST BEFORE IT CAN BE UPGRADED TO VERSION 956X. 3. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED BY THE 06.12.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 - ALL MODELS, THE DS4300 WITH STANDARD (DUAL CONTROLLER) OR TURBO OPTIONS, THE DS4400 AND THE DS4500. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM. 4. The only DS4000 storage subsystems that are supported by the 06.14.xx.xx or higher (06.14.xx.xx, 06.15.xx.xx, 06.16.xx.xx, 06.19.xx.xx, 6.23.xx.xx, or 6.60.xx.xx) controller firmware version are the DS4200 (06.16.88.xx or higher), DS4300 Standard-dual controller or Turbo models (06.19.xx.xx or higher), and the DS4500 (06.19.xx.xx or higher), DS4700 (06.16.4x.xx or higher) and DS4800 (06.14.xx.xx or higher) storage subsystems. Currently, there are not any controller firmware packages version 06.14.xx.xx and higher for other DS4000 storage subsystems. Do not download this controller firmware on any other DS4000 storage subsystems. 5. Always check the README files (especially the Dependencies section) that are packaged together with the firmware files for any required minimum firmware level requirements and the firmware download sequence for the DS4000 drive expansion enclosure ESM, the DS4000 storage subsystem controller and the hard drive firmware. 6. If the managed DS4000 storage subsystem had the FC/SATA intermix premium feature enable, do not upgrade the controller firmware from version 06.10.xx.xx to version 06.12.xx.xx until a FC/SATA intermix premium feature key file is generated and available. Once the controller firmware is upgraded to version 06.12.xx.xx, the FC/SATA intermix premium feature will be shown as out-of-compliance and the FC/SATA intermix premium feature key file is required to re-enable the feature. When the FC/SATA intermix premium feature is in out-of- compliance state, LUNs management functions like creations, deletions and modifications will not be operational. Please refer to the FC/SATA intermix premium feature activation card that was shipped with the FC/SATA intermix premium feature kit for instructions to generate the required premium key file. 7. The DS4700 and DS4800 storage subsystems do not support the attachment of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700 Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be attached to the DS4700 and DS4800 storage subsystems. 8. THE DS4000 STORAGE SERVER WITH CONTROLLER FIRMWARE VERSION 05.41.1X.XX MUST BE UPGRADED TO CONTROLLER FIRMWARE VERSION 05.41.5X.XX FIRST BEFORE IT CAN BE UPGRADED TO CONTROLLER FIRMWARE VERSION 06.1X.XX.XX OR LATER. OTHERWISE, THE ERROR 231-FIRMWARE INCOMPATIBLE WILL BE DISPLAYED. 9. DS4000 storage subsystem controller firmware versions 6.12.16.xx or higher and EXP100 storage expansion enclosure ESM firmware version 9563 or higher are required to provide support for the new 400G SATA drive options and CRUs (P/Ns 39M4570 and 39M4575, respectively) in addition to the new 250G SATA drive CRUs (P/N 40K6837.) This new 250G SATA drive CRU is functionally equivalent to the previously-released CRUs (P/N 90P1349). 10. This version 06.16.xx.xx of the DS4700 or DS4800 controller firmware is not compatible with the EXP100 SATA drive expansion enclosures. DO NOT download it into the DS4800 storage subsystems that have EXP100 drive expansion enclosures attached. After the 06.16.xx.xx controller firmware is activated, the DS4800 storage subsystem will not recognize the drives in EXP100 enclosures, causing loss of data availability to the raid arrays and logical drives that are defined in those drives. IBM recommends installing the controller firmware version 6.23.xx.xx and higher in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 11. Controller firmware 06.16.xx.xx or higher is required to support EXP810 storage expansion enclosures. 12. Controller firmware 06.16.4x.xx and higher is required for the DS4700 -all models and the DS4800-model 80A/80H. These models do not support older 06.16.xx.xx versions of controller firmware. The attachment of EXP100 enclosures is ONLY supported for these models only if the controller firmware is upgraded to version 6.23.xx.xx or higher. 13. In Solaris servers that are IO attached to the DS4700 and DS4800 storage subsystems using RDAC as multipath/failover driver, a RDAC patch version R789.091005-01 must be installed after the RDAC installation. This RDAC patch is included along with other DS4000 storage manager host software packages for SUN Solaris. 14. Controller firmware 06.16.88.xx and higher is required for the DS4200-all models. These models do not support older 06.16.xx.xx versions of controller firmware. The attachment of EXP100, EXP710 and EXP810 enclosures is not supported for these DS4200 models. 15. Controller firmware 06.19.xx.xx and higher is required for the DS4300- standard-dual controller or Turbo models and the DS4500-all models for attaching the EXP810 storage expansion enclosures. 16. Controller firmware 06.23.xx.xx and higher is required for the DS4700- all models and the DS4800-all models for attaching EXP810, EXP710 and EXP100 together behind a DS4000 storage subsystem. The intermix of EXP810 and EXP100 behind a DS4700 or DS4800 is supported only with controller firmware version 6.23.xx.xx and higher. IBM DS4000 Storage Manager host software version 09.6x.xx.xx provides full management support for IBM machine types 3552 and 3542 storage controllers that have at least firmware version 05.30.xx.xx, IBM Machine type 1742-900 and 1742 storage controllers that have at least firmware version 05.30.xx.xx, IBM Machine type 1722 storage controllers that have at least firmware version 05.3x.xx.xx, IBM Machine type 1724 storage controllers that have at least firmware version 05.42.xx.xx, IBM Machine type 1814 storage controllers that have at least firmware version 06.16.8x.xx or IBM Machine type 1815 storage controllers that have at least firmware version 06.14.xx.xx. The only IBM DS4000 Storage Manager version 09.6x.xx.xx supported management function on controllers with firmware version 04.xx.xx.xx to 04.00.02.xx is controller firmware and NVSRAM download. ======================================================================= 2.0 Installation and Setup Instructions ----------------------------------------- Note: The web-download Storage Manager version 9.60 host software package must be first unpacked (tar -xvz) into a user-defined directory. Then, go to this directory, locate the Solaris directory to access the Storage Manager version 9.60 host software installation file(s). 2.1 Step-by-step instructions for this code update are as followed ------------------------------------------------------------------- 1. Install and update the driver for the IBM DS4000 FC Host Bus Adapter. a. Install the hardware by using the instructions that come with the adapter. b. Install the Fibre Channel Host Bus Adapter driver by using the instructions provided with the adapter. 2. Install the new Storage Manager host software. If there is previous version (7.x, 8.x or 9.1x) of the IBM DS4000 Storage Manager host software (ie. SMRuntime, SMClient, RDAC, SMUtil and SMAgent packages) installed in the system, you have to uninstall it first before installing the new version of the storage manager host software. Refer to the IBM System Storage DS4000 Storage Manager version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER for detailed installation instructions. 3. If the managed DS4000 storage subsystem with controller firmware version 06.10.xx.xx installed had the FC/SATA intermix premium feature enable, do not continue with the next step until a FC/SATA intermix premium feature key file is generated and available. Once the controller firmware is upgraded to version 06.12.xx.xx, the FC/SATA intermix premium feature will be shown as out-of-compliance and the FC/SATA intermix premium feature key file is required to re-enable the feature. When the FC/SATA intermix premium feature is in out-of- compliance state, LUNs management functions like creations, deletions and modifications will not be operational. Please refer to the FC/SATA intermix premium feature activation card that was shipped with the FC/SATA intermix premium feature kit for instructions to generate the required premium key file. 4. Upgrade the DS4000 storage subsystem firmware in the following order - the DS4000 drive expansion enclosure ESM code, the DS4000 storage subsystem controller firmware and NVSRAM and then the hard drive firmware code. Refer to the IBM DS4000 Storage Manager version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER or the online help in the Subsystem Management window for detailed instructions. CAUTION: Always check the README files (especially the Dependencies section) that are packaged together with the firmware files for any required minimum firmware level requirements and the firmware download sequence for the DS4000 drive expansion enclosure ESM, the DS4000 storage subsystem controller and the hard drive firmware. 5. (if applicable) Re-enable the FC/SATA intermix premium feature using the premium key file. Refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the the latest DS4000 Storage Manager host software, the DS4000 controllers firmware, the drive expansion enclosure ESM firmware and the hard disk drive code. ======================================================================= 2.2 Supported FC HBAs for Sun Solaris platforms only ----------------------------------------------------- IBM has tested configurations with the following Fibre Channel Host Bus Adapters, device drivers and Storage Controller Firmware: 1. Vendor: JNI Model: FCE-6460 PCI 64-Bit Storage Controller Firmware: 06.6x.xx.xx OS: Solaris 8.0, 9.0 Driver: 5.3.1.1 2. Vendor: JNI Model: FCE-1473 S-Bus 64-Bit Storage Controller Firmware: 06.6x.xx.xx OS: Solaris 8.0, 9.0 Driver: 5.3.1.1 Note: Fabric attached only (2/10/2006) 3. Vendor: JNI Model: FCE2-1473 S-Bus 64-Bit Storage Controller Firmware: 06.6x.xx.xx OS: Solaris 8.0, 9.0 Driver: 5.3.1.1 Note: Fabric attached only (2/10/2006) 4. Vendor: JNI Model: FCX-6562, FCX2-6562 PCI-X 64-Bit Storage Controller Firmware: 06.2x.xx.xx OS: Solaris 8.0, 9.0 Driver: 5.3.1.1 5. Vendor: QLogic Model: QLA 2342 PCI-X 64-Bit Storage Controller Firmware 06.6x.xx.xx OS: Solaris 8.0, 9.0, 10.0 Driver: 4.18 6. Vendor: Emulex Model: LP9802 Storage Controller Firmware 06.6x.xx.xx OS: Solaris 8.0, 9.0, 10.0 Driver: 6.02h 7. Vendor: Emulex Model: LP10000 Storage Controller Firmware 06.6x.xx.xx OS: Solaris 8.0, 9.0, 10.0 Driver: 6.02h 8. Vendor: SUN Model: SG-XPCI2FC-QF2, SG-XPCI2FC-QF4, SG-XPCIE2FC-QF4, SG-XPCI1FC-EM2, SG-XPCI2FC-EM2 Storage Controller Firmware 06.60.xx.xx OS: Solaris 8.0, 9.0, 10.0 Driver: latest level Note: 1. While attaching a JNI 2Gb HBA to a IBM 2109 FC switch to run at 2 Gb mode, you must force the HBA to become a public loop device. For more information please refer to the Appendix F of the IBM System Storage DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER for more information. 2. Special version of fibre channel host bus adapter FCode is not required because Boot from SAN is not supported in Solaris operating environment. ======================================================================= 2.3 Helpful Hints ------------------ 1. The DS4500 and DS4300 storage subsystem have new recommended drive-side cabling instructions. The DS4500 instructions are documented in the IBM System Storage DS4500 Installation, Users. and Maintenance Guide (GC27-2051-00 or IBM P/N 42D3302). The DS4300 instructions are documented in the IBM System Storage DS4300 Installation, Users. and Maintenance Guide (GC26-7722-02 or IBM P/N 42D3300). Please follow the cabling instructions in these publication to cable the new DS4500 and DS4300 setup. If you have an existing DS4500 setup with four drive side minuhub installed that was cabled according to the previously recommended cabling instructions, please schedule down time as soon as possible to make changes to the drive side FC cabling. Refer to the IBM System Storage DS4500 and DS4300 Installation, Users. and Maintenance Guide for more information. 2. The DS4000 Storage Management dialog windows may be displayed cropped without the vertical and horizontal scroll bars. Just move the mouse pointer over the edge of the window until the mouse pointer change to window resize pointer, left click and hold to grip the window edge to resize it. 3. If you are unable to see the maximum number of drives during Automatic Configuration, you should be able to use Manual Configuration to select individual drives and select the maximum number of drives allowed. 4. Fabric topology zoning requirement. To avoid possible problem at the host level, all Fibre Channel Switches must be zoned such that a single host bus adapter can only access one controller per storage array. In addition, this zoning requirement also ensures the maximum number of host connections can be seen and log into the controller FC host port. This is because if a FC HBA port is seen by both controller A and B host ports, it will be counted as two host connections to the storage subsystem - one for controller A port and one for controller B port. Note: The DS4000 storage subsystems DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 storage subsystems DS4300 (IBM machine type 1722) and DS4100 (IBM machine type 1724) have two ports per controller. The DS4000 storage subsystem FAStT200 (IBM machine type 3542) has only one port per controller. The DS4000 storage subsystem DS4700 (IBM machine type 1814) has up to four ports per controller. The DS4000 storage subsystem DS4800 (IBM machine type 1815) has four ports per controller. 5. For partitioning in clusters. The partition must be done on the host group level not on the host level. This will allow all cluster hosts to see the same storage. 6. Do not delete the Access LUN or Access Volume. The Access LUN is required by the SMclient to communicate with the storage controllers when using the in-band management method. 7. Depending on the storage subsystem that you have purchased, you may have to purchase the FAST storage partitioning premium feature option or an option to upgrade the number of supported partitions in a storage subsystem. Please see IBM Marketing representatives or IBM resellers for more information. - IBM DS4100 storage subsystem (machine type 1724): The standard configuration does not have the FAST storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. - IBM DS4200 storage subsystem (machine type 1814): Depending on the ordering channels, the DS420 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage partitions. If the DS4200 storage subsystem is ordered with less than 64 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - IBM DS4300 storage subsystem (machine type 1722): The standard configuration does not have the FAST storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. The IBM DS4300 Turbo option comes with 8 partition storage partitioning premium option installed. An upgrade to 64 partitions can be purchased for the IBM DS4300 Turbo option. - IBM FAStT200, FAStT500, and DS4400 storage subsystems (machine type 3542, 3552 and 1742 - models 1RU and 1RX, respectively): The standard configuration has 64 partitions storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM DS4500 storage subsystem (machine type 1742 - models 90X and 90U): The standard configuration has 16 partition storage partitioning premium option installed. An upgrade from 16 to 64 partition storage partitioning premium feature option can be purchased. - IBM DS4700 storage subsystem (machine type 1814): Depending on the ordering channels, the DS4700-model 70 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage partitions. Similarly, the DS4700-model 72 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the DS4700 storage subsystem is ordered with less than 64 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - IBM DS4800 storage subsystem (machine type 1815): Depending on the ordering channels, the DS4800 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the subsystem is ordered with less than 64 partitions, an upgrade from 8 to 16, 8 to 64 or 16 to 64 partition storage partitioning premium feature option can be purchased. 8. Subsystems using dynamic multipathing (DMP) for the failover driver will need to manually do target and LUN definition in /kernel/drv/sd.conf. 9. When installing the SMibmasl.pkg the Solaris host will need a reboot -- -r. 10. To improve the reboot time of Sun 4800 Sunfire server or Sun servers with Solaris 9 installed, remove all ghost targets and LUNs from /kernel/drv/sd.conf file. Failure to remove ghost targets and LUNs may increase the boot time of the Sun servers. 11. Target volumes for VolumeCopy premium feature need the volume permissions changed. By default the VolumeCopy is set to read-only. The target volume permission for the VolumeCopy must be changed to read-write. 12. The DS4000 controller host ports or the Fibre Channel HBA ports can not be connected to a Cisco FC switch ports with "trunking" enable. You might encounter failover and failback problems if you do not change the Cisco FC switch port to "non-trunking" using the following procedure: a. Launch the Cisco FC switch Device Manager GUI. b. Select one or more ports by a single click. c. Right click the port(s) and select Configure, a new window pops up d. Select the "Trunk Config" tab from this window, a new window opens e. In this window under Admin, select the "non-trunk" radio button, it is set to auto by default. f. Refresh the entire fabric. 13. When making serial connections to the DS4000 storage controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the DS4000 storage subsystem serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 14. All enclosures (including DS4000 storage subsystem with internal drive slots) on any given drive loop/channel should have complete unique ID's, especially the single digit (x1) portion of the ID, assigned to them. For example, in a maximum configured DS4500 storage subsystem, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosure id's with the same single digit such as 11, 21 and 31 should not be used on the same drive loop/channel. In addition, for enclosures with mechanical enclosure ID switch like DS4300 storage subsystems, EXP100 or EXP710 storage expansion enclosures, do not use enclosure ID value of 0. The reason is with the physical design and movement of the mechanical enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which return an incorrect enclosure ID to the storage management software. The most commonly returned enclosure ID is 0 (zero). In addition to causing the subsystem management software to report incorrect enclosure ID, this behavior also result in enclosure ID conflict error with the storage expansion enclosure or DS4000 storage subsystem intentionally set the ID to 0. The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810 storage expansion enclosures did not have mechanical ID switches. Thus, they are not susceptible to this problem. In addition, these storage subsystems and storage expansion enclosures automatically set the Enclosure IDs. IBM recommendation is not make any changes to these settings unless the automatic enclosure ID settings resulting in non- unique single digit settings for enclosures (including the storage subsystems with internal drive slots) in a given drive loop/channel. 15. The ideal configuration for SATA drives is one drive in each EXP per array, one logical drive per array and one OS disk partition per logical drive. This configuration minimizes the random head movements that increase stress on the SATA drives. As the number of drive locations to which the heads have to move increases, application performance and drive reliability may be impacted. If more logical drives are configured, but not all of them used simultaneously, some of the randomness can be avoided. SATA drives are best used for long sequential reads and writes. 16. IBM recommends at least one hot spare per EXP100 drive expansion enclosure. A total of 15 hot-spares can be defined per DS4000 storage subsystem configuration. 17. Starting with the DS4000 Storage Manager (SM) host software version 9.12 or later, the Storage Manager client script window looks for the files with the file type of ".script" as the possible script command files. In the previous versions of the DS4000 Storage Manager host software, the script window looks for the file type ".scr" instead. (i.e. enableAVT.script for SM 9.12 or later vs. enableAVT.scr for pre-SM 9.12) ======================================================================= 3.0 Configuration Information ----------------------------- 3.1 Configuration Settings -------------------------- 1. By default the IBM DS4000 Storage Manager SMClient program does not automatically map logical drives. This means that the logical drives are not automatically presented to host servers. a. For a new installation, after creating new arrays and logical drives, create a storage partition with the host type of Sun-Solaris and map the logical drives to this partition. b. If you are upgrading the NVSRAM with Storage Partitions, you may have to change the default host type to match the host system OS. After upgrading the NVSRAM, the default host type is reset to Windows 2000/Server 2003 non-clustered for DS4000 storage server with controller firmware version 06.14.xx.xx or later. For DS4000 storage server with controller firmware version 06.12.xx.xx or earlier, it is reset to Windows non-clustered (SP5 or higher), instead. Refer to the IBM DS4000 Storage Manager online help to learn more about creating storage partitions and changing host types. 2. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815, 3542 or 3552 storage controllers as boot devices, contact IBM support for supported configurations and instructions for configuring IBM storage controllers as boot devices. 3. Running script files for specific configurations. Apply the appropriate scripts to your subsystem based on the instructions you have read in the publications or any instructions in the operating system readme file. A description of each script is shown below. - SameWWN.script: Setup RAID controllers to have the same World Wide Names. The World Wide Names (node) will be the same for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - DifferentWWN.script: Setup RAID controllers to have different World Wide Names. The World Wide Names (node) will be different for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - EnableDriveMigration.script: The Enable drive migration script scans the drives for configurations when they are added to a storage system and will also attempt to use configurations found on the newly added drives. The NVSRAM default will enable drive migration. - DisableDriveMigration.script: The disable drive migration script allows the addition of disk drives while the system is running. In addition, it identifies the drives as unused capacity regardless of past drive configuration. The NVSRAM default will enable drive migration. - EnableAVT_W2K_S2003_noncluster.script: The script will enable automatic logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003 non- cluster heterogenous host region. The default setting is to disable AVT for this heterogenous host region. This setting is one of the requirements for setting up the remote boot or SAN-boot. Do not use this script unless it is specifically mentioned in the applicable instructions. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT enabled) - DisableAVT_W2K_S2003_noncluster.script: The script will disable the automatic logical drive transfer (AVT) for the Windows 2000/Server 2003 non-cluster heterogenous host region. This script will reset the Windows 2000/Server 2003 non-cluster AVT setting to the default. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non- cluster host type with the appropriate host type that needs to have AVT/ADT disabled) 4. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815 or 3552 storage servers in host cluster Remote Mirror configurations, contact IBM support for supported host cluster configurations and instructions for configuring IBM storage controllers in a clustered Remote Mirror configurations. ======================================================================= 3.2 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS4000 Storage Manager Version 9.23. 1. The DS4100 (machine type 1724-all models) storage subsystem does not support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC) drive expansion enclosure. Please contact IBM representatives or resellers for the availability of such support in the future. 2. The DS4800 storage subsystem (machine type 1815-all models) does not support the attachment of the FAStT EXP500 and DS4000 EXP700 drive expansion enclosures. 3. The DS4200 (machine type 1814 - models 7VA/H) with controller firmware 6.16.88.xx installed does not support the attachment of the DS4000 EXP100 (SATA), EXP710 (FC) and EXP810 (SATA and FC) drive expansion enclosures. In addition, it does not support Fibre Channel disk drive options. 4. The IBM DS4000 EXP420 Expansion Enclosure is not supported attached to any other IBM DS4000 Storage Controllers except the DS4200. 5. The DS4100 with Single Controller option does not support the attachment of the DS4000 storage expansion enclosures. 6. The DS4300 storage subsystem with Single Controller option does not support the controller firmware version 06.1x.xx.xx. The correct firmware version for these DS4300 storage subsystem models is 05.34.xx.xx. 7. Fibre Channel loop environments with the IBM Fibre Channel Hub, machine type 3523 and 3534, in conjunction with the IBM Fibre Channel Switch, machine types 2109-S16, 2109-F16 or 2109-S8. In this configuration, the hub is connected between the switch and the IBM Fibre Channel RAID Controllers. 8. The IBM Fibre Channel hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1814, 1815, 3542 and 3552. 9. A configuration in which a server with only one FC host bus adapter connects directly to any DS4000 storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC host bus adapter connects to both controller ports of any DS4000 storage subsystem with dual controllers via Fibre Channel (FC) switch (SAN-attached configuration.) Note: The HBA(s) in the Sun server must have FC connection to both controller A and B ports of any DS4000 storage subsystem with dual controllers via FC switch attached or via direct attached. ======================================================================= 4.0 Unattended Mode --------------------- N/A ======================================================================= 5.0 WEB Sites and Support Phone Number ---------------------------------------- 5.1 IBM System Storage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 5.2 IBM System Storage™ Marketing Web Site: http://www.ibm.com/servers/storage/disk 5.3 You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426- 7378). IMPORTANT: You should download the latest version of the DS4000 Storage Manager host software, the DS4000 storage subsystem controller firmware, the DS4000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. To be notified of important product updates, you must first register at the IBM Support and Download Web site: www-1.ibm.com/servers/storage/disk/ Perform the following steps to register at the IBM Support and Download Web site: 1. Click on My Support in the Additional Support box in the right side of the DS4000 Support web page. 2. The Sign In window displays. Either enter your IBM ID and Password in the sign in area to sign in and proceed to step 6 or, if you are not currently registered with the site, click Register Now. 3. The My IBM Registration window Step 1 of 2 opens. Enter the appropriate information and click Continue to get to the second My IBM Registration window. 4. In the My IBM Registration window Step 2 of 2, enter the appropriate information and click Submit to register. 5. The My IBM Registration windows opens with the following message, “Thank you for registering with ibm.com. Continue to explore ibm.com as a registered user.” Click Edit Profile in the My IBM box on the right side of the window. 6. The My Support window opens. Click Add Products to add products to your profile. 7. Use the pull-down menus to choose the appropriate DS4000 storage server and expansion enclosures that you want to add to your profile. To add the product to your profile, select the appropriate box or boxes next to the product names and click Add Product. 8. Once the product or products are added to your profile, click Subscribe to Email folder tab 9. Select Storage in the pull down menu. Select Please send these documents by weekly email and select Downloads and drivers and Flashes to receive important information about product updates. Click Updates. 10. Click Sign Out to log out of My Support. ======================================================================= 6.0 Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM System Storage the e-business logo xSeries, pSeries HelpCenter UNIX is a registered of The Open Group in the United States and other countries. Microsoft, Windows, and Windows NT are of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. SUN, Solaris, Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. QLogic and SANsurfer are trademarks of QLogic Corporation. Other company, product, or service names may be trademarks or service marks of others. ======================================================================= 7.0 Disclaimer -------------- 7.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 7.2 Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.