IBM System Storage subsystem controller firmware version 07.60.63.00 for the DS4800-all models, DS4700-all models and DS4200-all models storage subsystems. NOTICE: This release of 7.60.63.00 firmware is only supported on the DS4800-all models, DS4700-all models, DS4200-all models storage subsystems. ===================================== BEFORE INSTALLING 07.60.63.00, PLEASE VERIFY ON SSIC (URL BELOW) THAT YOUR STORAGE ENVIRONMENT IS SUPPORTED: http://www.ibm.com/storage/support/config/ssic ===================================== (C) Copyright International Business Machines Corporation 1999, 2012. 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: AIX RDAC multipath driver (fcp_array) is not supported with storage subsystems having controller firmware version 7.60.xx.xx and later installed. AIX MPIO multipath driver should be used instead. Please refer following link for detail information: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.resources/RELNOTES/SC23520108.htm A problem causing recursive reboots exists while using 7.36.08 and 7.36.12 firmware on IBM System Storage DS4000 or DS5000 systems. This problem is fixed in 7.36.14.xx and above firmware. All subsystems currently using 7.36.08 and 7.36.12 firmware MUST run a file system check tool (DbFix) before and after the firmware upgrade to 7.36.14.xx or higher. Instructions for obtaining and using DbFix are contained in the 7.36.14.xx or later firmware package. Carefully read the firmware readme and the DbFix instructions before upgrading to firmware 7.36.14.xx or higher. For subsystems with firmware level 7.36.08 or 7.36.12, configuration changes should be avoided until a firmware upgrade to 7.36.14.xx or later has been completed successfully. Subsystems not currently using 7.36.08 or 7.36.12 do not need to run DbFix prior to upgrading to 7.36.14.xx or later. DbFix may be run after upgrading to 7.36.14.xx or later, but it is not required. DbFix is only applicable to subsystems using 7.36.xx.xx or later firmware. If problems are experienced using DbFix or the resulting message received is check Failed, DO NOT upgrade your firmware and contact IBM support before taking any further actions. Note: Before commencing with any firmware upgrade procedure, use the Storage Manager client to perform a Collect All Support Data capture. Save this support data capture on a system other than the one that is being upgraded. Refer to the IBM System Storage?Support Web Site or CD for the IBM DS Storage Manager version 10 Installation and Host Support Guide for firmware and NVSRAM download instructions. For other related publications, refer to Related Publications in the Installation, User's and Maintenance guide of your DS storage subsystem or storage expansion enclosures. Last Update: 09/28/2012 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, | |------------|-----------|--------------|-----------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | --------------------------------------------------------------- Notes: 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. --------------------------------------------------- | IBM Storage | Controller firmware version | | Subsystem Model | | |------------------|--------------------------------| | DS4800 (1815) | 07.60.xx.xx | | | (07.60.28.00 or later only) | |------------------|--------------------------------| | DS4700 (1814) | 07.60.xx.xx | | | (07.60.28.00 or later only) | |------------------|--------------------------------| | DS4200 (1814) | 07.60.xx.xx | | | (07.60.28.00 or later only) | --------------------------------------------------- ======================================================================= 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 -------------- The IBM System Storage?controller firmware version 07.60.63.00 release includes the storage subsystem controller firmware and NVSRAM files for the DS4200-all models, DS4700-all models and DS4800-all models. The IBM DS Storage Manager host software version 10.60.x5.17 or later is required to manage DS storage subsystems with controller firmware version 7.60.63.00 installed. NOTICE: This release of 7.60.63.00 firmware is only supported on the DS4800-all models, DS4700-all models, DS4200-all models storage subsystems. ATTENTION: DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS3000, DS4000 or DS5000 STORAGE SUBSYSTEM MODELS. The IBM System Storage DS Storage Manager version 10 Installation and Host Support Guide is available on IBM's Support Web Site as a down-loadable Portable Document Format (PDF) file. In addition, the FC/SATA intermix premium features and the Copy Services premium features; FlashCopy, VolumeCopy, and Enhanced Remote Mirroring are separately purchased options. The Storage partitioning premium feature is standard on all IBM DS3950, DS4000 and DS5000 storage subsystems with the exception of the IBM DS4100 (machine type 1724 with Standard or Single Controller options)and the DS4300 (machine type 1722 with Standard or Single Controller options) storage subsystems. Please contact IBM Marketing representatives or IBM resellers if you want to purchase additional Storage partitioning options for supported models. See section 3.3 "Helpful Hints" for more information. Refer to the IBM Support Web Site for the latest Firmware and NVSRAM files and DS Storage Manager host software for the IBM DS Storage Subsystems. http://www.ibm.com/support/ 1.1 Limitations --------------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by the 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. Upgrade to controller firmware 07.xx.xx.xx from 06.xx.xx.xx is done through the upgrade utility packaged with the host software if below 10.50.x5.19. The upgrade utility is a part of the Storage Manager client at 10.50.x5.19 and above. Click on the Setup tab in the Enterprise Management window and select "upgrade controller firmware". The storage subsystem must be optimal and the upgrade must be done non- concurrent to any I/O or configuration activity. Note: For limitations in certain operating system environments, refer to the readme file that is included in the DS Storage Manager host software package for that operating system environment. SVC supports concurrent ESM firmware upgrades for DS4000 models when they are running either 06.23.05.00 or later controller firmware. However, controllers running firmware levels earlier than 06.23.05.00 will not be supported for concurrent ESM upgrades. Customers in this situation, who wish to gain support for concurrent ESM upgrades, will need to first upgrade the DS4000 controller firmware level to 06.23.05.00 or later. This action is a controller firmware upgrade, not an ESM upgrade and concurrent controller firmware upgrades are already supported in conjunction with SVC. Once the controller firmware is at 06.23.05.00 or later, the ESM firmware can be upgraded concurrently. The condition when LUNs within a Raid array have split ownership between the two controllers could possibly see false positives on synthesized PFA has been corrected by CR151915. The stagnant I/O will be discarded. In order to utilize the stagnant I/O functionality, configure arrays so that all LUNs in an array are owned by one controller. Limitations with version 07.60.63.00 release. No new limitations. Limitations with version 07.60.52.00 release. No new limitations. Limitations with version 07.60.40.00 release. No new limitations. Limitations with version 07.60.28.00 release. 1. The 7.60.xx release includes the synthesized drive PFA feature. This feature will provide a critical alert if drive IOs respond slower than expected 30 times within a one hour period. There is a condition when LUNs within a RAID array have split ownership between the two controllers where false positives could be received on this. 2. When repeatedly remove and re-insert the fan module in the EXP5060 drive expansion enclosure, the fan module amber fault LED might stay lit and the recovery guru in the Storage manager might report that the fan is bad whereas the fan module is working perfectly fine. This condition persists even when the fan is replaced with a new fan module. Because the fan was removed and re-insert many times, the controller might run into timing problem between replacing the fan module and when the controller polls the ESM for status updates and misinterprets the status of the removed fan as ?failed? That status bit is never reset, causing the fan amber fault led to remain on and failed status to persist even after a new fan CRU is installed. If a replacement fan module exhibits these symptoms, place your hand over the fan and compare the air flow to the fan with good status on the opposite side of the enclosure. If air flow is similar you can assume the fan with failed status working properly. Schedule time for the DS subsystem can be placed offline so that the whole storage subsystem configuration can be power cycled to clear the incorrect status bit. Limitations with version 07.60.13.05 release. 1. When modifying the iSCSI host port attributes there can be a delay of up to 3 minutes if the port is inactive. If possible, connect a cable between the iSCSI host port and a switch prior to configuring any parameters. 2. When doing a Refresh DHCP operation in the Configure iSCSI port window, and the iSCSI port is unable to contact the DHCP server, the following inconsistent informational Mel events can be reported; - MEL 1810 DHCP failure - MEL 1807 IP address failure - MEL 1811 DHCP success. For this error to occur, the following specific conditions and sequence must have been met: - Before enabling DHCP, static addressing was used on the port and that static address is still valid on the network. - The port was able to contact the DCHP server and acquire an address. - Contact with the DHCP server is lost. - The user performs the Refresh DHCP operation from DS Storage Manager Client. - Contact with the DHCP server does not come back during the DHCP refresh operation and timeouts. Check the network connection to your iSCSI port and the status of the DHCP server before attempting the Refresh DHCP operation again. Limitations with version 07.60.13.00 release. 1. Brocade HBA does not support direct attach to storage subsystem. 2. Tivoli Productivity Center server does not retrieve the IPv6 address from an SMI-S provider on an IPv6 host. You must use an IPv4 host. 3. Linux clients in a VIOS environment should change their error recovery timeout value to 300 seconds and their device timeout value to 120 seconds. Default ibmvscsic error recovery timeout = 60, the command to change it to 300 is: echo 300 > /sys/module/ibmvscsic/parameters/init_timeout Default device timeout = 30, the command to change it to 120 is: echo 120 > /sys/block/sdb/device/timeout 4. Maximum sustainable IOPs falls slightly when going above 256 drives behind a DS5100 or DS5300. Typically adding spindles improves performance by reducing drive side contention. Not all IO loads will benefit by adding hardware. 5. Event mechanism cannot support level of events submitted to keep consistency group state parallel with repeated reboots and auto resync for more than 32 RVM LUNs. Although we support the user setting RVM consistency group volumes to auto resync, we advise not to use this setting as it can defeat the purpose of the consistency group in a disaster recovery situation. If the customer must do this then the number of RVM LUNs which are in a consistency group and also have auto resync set should be limited to 32. 6. If you switch from IPv6 to IPv4 and have an iSNS server running, you could see IPv6 address still showing up on the iSNS server. To clear this situation, disable then enable iSNS on the controllers after you disabled IPv6 support. 7. Long controller Start of Day times have been observed on the iSCSI DS5020 with a large number of mirrors configured with an Asynchronous w/ Write Order Consistency mirroring policy. Limitations with version 07.50.13.xx release. No new limitations. Limitations with version 07.50.12.xx release. 1. Start of day (a controller reboot) can take a very long time, up to 20 minutes, after a subsystem clear configuration on a DS5000 subsystem. This occurs on very large configurations, now that the DS5000 can support up to 448 drives, and can be exacerbated if there are SATA drives. 2. Veritas cluster server node failure when fast fail is enabled. Recommend setting dmp_fast_fail HBA flag to OFF. Frequency of this causing a node failure is low unless the storage subsystem is experiencing repeated controller failover conditions. 3. Brocade HBA does not support direct attach to storage subsystem. 4. At times the link is not restored when inserting a drive side cable into a DS5000 controller, a data rate mismatch occurs. Try reseating the cable again to clear the condition. 5. Due to a timing issue with controller firmware, using SMcli or the script engine to create LUNs and set LUN attributes will sometimes end with a script error. 6. Mapping host port identifiers to host via Script Editor hangs; fails via CLI with "... error code 1? This will occur when using the CLI/script engine to create an initial host port mapping. 7. Under certain high stress conditions controller firmware upgrade will fail when volumes do not get transferred to the alternate controller quick enough. Upgrade controller firmware during maintenance windows or under low stress IO conditions. 8. Concurrent controller firmware download is not supported in storage subsystem environments with attached VMware ESX server hosts running a level of VMware ESX older than VMware ESX 3.5u5 p20. Limitations with version 07.36.17.xx release. No new limitations. Limitations with version 07.36.14.xx release. No new limitations. Limitations with version 07.36.12.xx release. 1. For current PowerHA/XD (formerly HACMP)and GPFS support information, please review the interoperability matrix found at: http://www-03.ibm.com/systems/storage/disk/ds4000/interop-matrix.html -or- www.ibm.com/systems/support/storage/config/ssic/index.jsp Limitations with version 07.36.08.xx release. 1. After you replace a drive, the controller starts the reconstruction process on the degraded volume group. The process starts successfully, and it progresses through half of the volume group until it reaches two Remote Volume Mirroring (RVM) repository volumes. The first RVM repository volume is reconstructed successfully, but the process stops when it starts to reconstruct the second repository volume. You must reboot the owning controller to continue the reconstruction process. Limitations with version 07.30.21.xx release. 1. For current PowerHA/XD (formerly HACMP)and GPFS support information, please review the interoperability matrix found at: http://www-03.ibm.com/systems/storage/disk/ds4000/interop-matrix.html -or- http://www.ibm.com/systems/support/storage/config/ssic/index.jsp 2. When migrating or otherwise moving controllers or drive trays between between systems, always quiesce IO and allow the cache to flush before shutting down a system and moving components. 3. When utilitizing remote mirrors in a write consistency group, auto- synchronization can fail to resynchronize when a mirror link fails and gets re-established. Manual synchronization is the recommended setting when mirrors are spread across multiple arrays. 4. Using 8KB segment size (default) with large IOs on a RAID-6 volume can result in an ancient IO as a single IO will span several stripes. Adjusting the segment size to better match the IO sizes such as 16KB will improve this performance. 5. Doing volume defragmentation during peak IO activity can lead to an IO error. It is recommended that any volume defrag is done during off-peak or maintenance windows. 6. Doing RAID migration in large configurations during peak IO activity can take a very long time to complete. It is recommended that RAID migration is done during off-peak or maintenance windows. 7. When using legacy arrays running 7.10.23.xx firmware as a remote mirror with a DS5000 array can have performance issues causing "Data on mirrored pair unsynchronized" errors. Updating the legacy controller to 07.15.07.xx resolves this issue. 8. The IPv6 dynamic Link-Local address for the second management port on the controller is not set when you toggle Stateless Autoconfig from Disabled to Enabled. The IPv6 dynamic Link-Local address is assigned when the controller is rebooted. 9. DS5000 storage subsystems support legacy EXP810 storage expansions. If you are moving these expansions from an existing DS4000 system to the DS5000 system as the only expansions behind the DS5000, the DS4000 system must be running 07.1x.xx.xx controller firmware first. 1.2 Enhancements ----------------- No new enhancements. 1.3 Prerequisites ------------------ The IBM DS Storage Manager host software version 10.60.xx.xx or later is required to manage DS4200, DS4700 and DS4800 storage subsystems with controller firmware version 7.60.xx.xx installed. 1.4 Dependencies ----------------- The information in this section is pertinent to the controller firmware version 7.60.xx.xx release only. For the dependency requirements of previously released controller firmware versions, please consult the Dependencies section in the readme file that was packaged with each of those controller firmware releases. ATTENTION: 1. 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 storage/drive expansion enclosure ESM, the storage subsystem controller and the hard drive firmware. 2. The disk drives and ESM packages are defined in the Hard Disk Drive and ESM Firmware Update Package version 1.68 or later found at the IBM support web site. 1.5 Level Recommendations ----------------------------------------- 1. Storage Controller Firmware versions: a. DS4800: FW_DS4800_07606300 b. DS4700: FW_DS4700_07606300 c. DS4200: FW_DS4200_07606300 2. Storage Controller NVSRAM versions: a. DS4800: N1815D48R1060V12.dlp b. DS4700: N1814D47R1060V17.dlp c. DS4200: N1814D42R1060V17.dlp Note: The Ds3950/DS4000/DS5000 storage subsystems shipped from the factory may have NVSRAM versions installed with a different first character prefix. Both manufacturing NVSRAM version and the "N" prefixed NVSRAM version are the same. You do not need to update your DS3950/DS4000/DS5000 storage subsystem with the "N" prefixed NVSRAM version as stated above. For example, the N1815D480R923V08 and M1815D480R923V08 (or C1815D480R923V08 or D1815D480R923V08 or ...) versions are the same. Both versions share the same "1815D480R923V08" string value. Refer to the following IBM System Storage?Disk Storage Systems Technical Support web site for the latest released code levels. http://www.ibm.com/support/ ======================================================================= 2.0 Installation and Setup Instructions ----------------------------------------- Note: Before commencing with any firmware upgrade procedure, use the Storage Manager client to perform a Collect All Support Data capture. Save this support data capture on a system other than the one that is being upgraded. The sequence for updating your Storage Subsystem firmware may be different depending on whether you are updating an existing configuration, installing a new configuration, or adding drive expansion enclosures. ATTENTION: If you have not already done so, please check the Dependencies section for ANY MINIMUM FIRMWARE REQUIREMENTS for the storage server controllers, the drive expansion enclosure ESMs and the hard drives in the configurations. The order in which you will need to upgrade firmware levels can differ based on prerequisites or limitations specified in these readme files. If no prerequisites, or limitations, are specified, the upgrade order refered to in section 2.1 Installation For an Existing Configuration should be observed. If drive firmware upgrades are required, down time will need to be scheduled. The drive firmware upgrades require that there are no Host I/Os sent to the storage controllers during the download. Note: For additional setup instructions, Refer to the Installation, User's and Maintenance Guide of your storage subsystem or storage expansion enclosures. 2.1 Installation For an Existing Configuration ------------------------------------------------- 1. Upgrade the storage manager client program to the latest storage manager 10.60 or later version that is available from the IBM system storage support web site. Older versions of the storage manager client program will show that the new firmware file is not compatible with the to-be-upgraded subsystem, even when the existing version of the controller firmware installed in the DS storage subsystem is of 7.6x.xx.xx code thread. http://www.ibm.com/support/ 2. Download controller firmware and NVSRAM. Please refer to the IBM DS Storage Manager version 10 Installation and Host Support Guide for additional information. Important: It is possible to download the controller firmware and NVSRAM at the same time by selecting the option check box in the controller firmware download window. However if you have made any setting changes to the host parameters, downloading NVSRAM will overwrite those changes. These modifications must be reapplied after loading the new NVSRAM file. You may need to update firmware and NVSRAM during a maintenance window. To download controller firmware and NVSRAM using the DS Storage Manager application, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller Firmware Follow the online instructions. c. Reapply any modifications to the NVSRAM. Both controllers must be rebooted to activate the new NVSRAM settings. To download controller NVSRAM separately, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller => Controller NVSRAM. Follow the online instructions. c. Reapply and modifications to the NVSRAM. Both controllers must be rebooted to activate the new NVSRAM settings. 3. Update the firmware of the ESMs in the attached drive expansion enclosures to latest levels. (See 1.4 Dependencies) To download drive expansion ESM firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Environmental(ESM) Card Firmware. Follow the online instructions. Note: The drive expansion enclosure ESM firmware can be updated online with no downtime if both ESMs in each of the drive expansion enclosures are functional and one (and ONLY one) drive expansion enclosure is selected in the ESM firmware download window for ESM firmware updating at a time. SAN Volume Controller (SVC) customers are now allowed to download ESM firmware with concurrent I/O to the disk subsystem with the following restrictions. 1) The ESM Firmware upgrade must be done on one disk expansion enclosure at a time. 2) A 10 minute delay from when one enclosure is upgraded to the start of the upgrade of another enclosure is required. Confirm via the Storage Manager Application's "Recovery Guru" that the DS5000 status is in an optimal state before upgrading the next enclosure. If it is not, then do not continue ESM firmware upgrades until the problem is resolved. Note: Reference IBM System Storage?Disk Storage Systems Technical Support web site for the current ESM firmware versions for the drive expansion enclosures. 4. Make any hard disk drive firmware updates as required. FAILURE to observe the minimum firmware requirement might cause your storage subsystem to be OUT-OF-SERVICE. Check the IBM System Storage Disk Storage Systems Technical Support web site for the latest released hard drive firmware if you have not already upgraded drive firmware to the latest supported version. (See 1.4 Dependencies) To download hard disk drive firmware, do the following: a. Schedule down time because the drive firmware upgrades require that there are no HOST I/Os to be sent to the DS5000 controllers. b. Open the Subsystem Management window. c. Click Advanced => Maintenance => Download => Drive Firmware. Follow the online instructions. Note: with controller firmware version 06.1x.xx.xx or later, multiple drives from up to four different drive types can be updated at the same time. ======================================================================= 3.0 Configuration Information ----------------------------- 3.1 Configuration Settings -------------------------- 1. By default the IBM DS Storage Manager 10.60 or later does not automatically map logical drives if storage partitioning feature is enabled. This means that the logical drives are not automatically presented to host systems. For a new installation, after creating new arrays and logical drives; a. If your host type is not Windows, create a partition with your host type and map the logical drives to this partition. b. If your host type is Windows, you can map your logical drives to the "Default Host Group" or create a partition with a Windows host type. When upgrading from previous versions of IBM DS Storage Manager to version 10.60 or later. a. If upgrading with no partitions created and you have an operating system other than Windows, you will need to create a partition with your host type and map the logical drives from the "Default Host Group" to this partition. b. If upgrading with Storage Partitions and an operating system other than Windows is accessing the default host group, you will need to change the default host type. After upgrading the NVSRAM, the default host type is reset to Windows Server 2003/2008 non-clustered for DS 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 DS Storage Manager online help to learn more about creating storage partitions and changing host types. 2. 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.scr: 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.scr: 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. - EnableAVT_W2K_S2003_noncluster.scr: The script will enable automatic logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003 non- cluster heterogeneous host region. The default setting is to disable AVT for this heterogeneous 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.scr: 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) - EnableAVT_Linux.scr: The script will enable automatic logical drive transfer (AVT) for the Linux heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Linux.scr: The script will disable the automatic logical drive transfer (AVT) for the Linux heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - EnableAVT_Netware.script: The script will enable automatic logical drive transfer (AVT) for the NetWare Failover heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Netware.script: The script will disable the automatic logical drive transfer (AVT) for the NetWare Failover heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - disable_ignoreAVT8192_HPUX.script: This script will disable the DS4000 storage subsystem ignoring of AVT requests for the HP-UX server specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request for the LBA 8192 reads was implemented to prevent a possible occurrence of an AVT storm caused by the HP-UX server probing in the wrong order of available paths to the volume(s) when it detect server to LUN path failure. Use this script only when you do not have defined LVM mirrored volumes using the mapped logical drives from the DS4000 storage subsystems. Please contact IBM support for additional information, if required. - enable_ignoreAVT8192_HPUX.script: This script will enable the DS4000 storage subsystem ignoring of AVT requests for the HP-UX server specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request for the LBA 8192 reads was implemented to prevent a possible occurrence of an AVT storm caused by the HP-UX server probing in the wrong order of available paths to the volume(s) when it detect server to LUN path failure. Use this script only when you do have defined LVM mirrored volumes using the mapped logical drives from the DS4000 storage subsystems. Please contact IBM support for additional information, if required. 3.2 Unsupported configurations ------------------------------ The configurations that are currently not being supported with controller firmware version 07.60 or later in conjunction with DS Storage Manager version 10.60 are listed below: 1. Any DS4500, DSDS4400, DS4300, DS4100, FAStT500 and FAStT200 storage subsystems configurations are not supported with this version of controller firmware. 2. The EXP520 Expansion enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5020. EXP810 drive enclosures are also supported in the DS5020 with the purchase of a premium feature key. 3. The IBM EXP395 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS3950. EXP810 drive enclosures are also supported in the DS3950 with the purchase of a premium feature key. 4. The IBM EXP5000 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5100 and DS5300. EXP810 drive enclosures are also supported with the DS5100 and DS5300 once the RPQ is submitted and approved. 5. 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-S08. In this configuration, the hub is connected between the switch and the IBM Fibre Channel RAID Controllers. 6. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1815, 1814, 3542 and 3552. 7. A configuration in which a server with only one FC host bus adapter connects directly to any 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 DS storage subsystem with dual controllers via Fibre Channel (FC) switch (SAN-attached configuration.) 3.3 Helpful Hints ------------------ 1. Depending on the storage subsystem that you have purchased, you may have to purchase the 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. 2. When making serial connections to the DS storage controller, the baud rate is recommended to be set at 38400. Note: Do not make any connections to the DS3950/DS4000/DS5000 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. 3. All enclosures (including storage subsystems 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. The DS3950, DS5020, DS4200 and DS4700 storage subsystems and the EXP395, EXP520, EXP420, EXP810, and EXP5000 storage expansion enclosures do not have mechanical ID switches. 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. 4. The ideal configuration for SATA drives is 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. 5. 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 9.12 or later vs. enableAVT.scr for pre-9.12) 6. Inter-operability with tape devices is supported on separate HBA and switch zones. ======================================================================= 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/systems/support/storage/disk 5.2 IBM System Storage?Marketing Web Site: http://www-03.ibm.com/systems/storage/ 5.3 If you have any questions about this update, or problem applying the update go to the following HelpCenter World Telephone Numbers URL: http://www.ibm.com/planetwide IMPORTANT: You should download the latest version of the DS Storage Manager host software, the storage subsystem controller firmware, the drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. For more information about how to register for support notifications, see the following IBM Support Web page: ftp://ftp.software.ibm.com/systems/support/tools/mynotifications/overview.pdf You can also check the Stay Informed section of the IBM Disk Support Web site, at the following address: www.ibm.com/systems/support/storage/disk ======================================================================= 6.0 Trademarks and Notices ---------------------------- 6.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DS4000 DS5000 FAStT System Storage the e-business logo xSeries pSeries HelpCenter Microsoft Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product, and 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.