This README file contains the latest information about the IBM TotalStorage™ DS4100 Midrange disk system controller firmware version 05.42.xx.xx for the DS4100 storage subsystems with Single Controller Option. Refer to the IBM TotalStorage™ Support Web Site or CD for the IBM DS4000 Storage Manager Version 9 Installation and Support Guides for Windows 2000/Server 2003, Netware, ESX Server, and Linux or 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 "Online Help" provide the installation and support information. For other related publications (refer to related publications in the installation and support guide) and the latest information and updated README file. Last Update: 07/15/2005 Products Supported: ---------------------------------------------------- | | Machine Type | Model | |------------|--------------|------------------------| | DS4100 | | | | single | 1724 | 1SC (1S_) | | controller | | | |------------|--------------|------------------------| | EXP100 | 1710 | 10U, 10X | ---------------------------------------------------- The three character model of the DS4100 single controller midrange disk system starts with the characters 1S (like 1SC for example). The machine type of the DS4100 single controller is 1724. Attention: The DS4100 midrange disk system controller firmware file version 05.42.18.02 and its associated NVSRAM file must be used ONLY for the DS4100 with Single Controller Option - machine type 1724 model 1SC. This version of the firmware shall not be loaded on any DS4000 midrange disk systems other than the DS4100 1SC single controller model. In addition, even though the any versions of IBM TotalStorage™ DS4000 Storage Manager from 08.42.x or higher can be used for managing the DS4100 midrange disk systems, it is recommended to upgrade the DS4000 Storage Manager host software to the latest version posted in the IBM TotalStorage Support Web Site for the IBM DS4000 midrange disk systems. http://www.ibm.com/servers/storage/support/disk/ NOTE 1. The version of the currently support controller firmware for the DS4100 (FAStT100) with dual controllers (Standard/Base option) - M/T 1724/model 100 - is 06.12.xx.xx. All future maintenance releases for DS4100 dual controller model controller firmware will be with version 06.12.xx.00 controller firmware levels. See IBM TotalStorage Support web site for further details on migrating the DS4100 dual controller model from controller firmware 05.42.xx to 06.12.xx.00 level. 2. The DS4100 with single controller option - M/T 1724/ model 1SC/1S_ - will continue to be supported with 05.42.xx The controller in this model cannot be migrated to 06.12.xx.xx controller firmware level. ======================================================================= CONTENTS -------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer ======================================================================= 1.0 Overview ------------ This IBM Storage Manager release includes support for the IBM DS4100 midrange disk system controller firmware and NVSRAM files version 05.42.xx.xx for the following IBM machine type 1724 - model 1SC (the DS4100 storage subsystems with single controller option). Refer to the IBM TotalStorage™ Support Web Site or CD for the IBM DS4000 Storage Manager Version 9 Installation and Support Guides for Windows 2000/Server 2003, Netware, ESX Server, and Linux or the IBM TotalStorage DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX and Solaris. This guide along with the DS4000 Storage Manager Online Help provides the installation and support information. The DS4100 with single controller option (M/T1724, model 1SC/1S_) supports IBM DS4000 Copy Services premium features FlashCopy only. It does not support the DS4000 Copy Services premium features VolumeCopy and Remote Mirroring at this time. Please contact your IBM representatives or resellers for availability date of support. The DS4000 storage partitioning premium feature is not standard on IBM DS4100 with single controller option. Please contact IBM Marketing representatives or IBM resellers if you want to purchase the IBM DS4000 storage partitioning premium feature option for it. The IBM DS4000 Storage Manager Version 9 is shipped with IBM DS4100 midrange disk system. Refer to the IBM TotalStorage Support Web Site for the latest firmware and NVSRAM files for the IBM DS4000 midrange disk systems. http://www.ibm.com/servers/storage/support/disk/ ================================================================== 1.1 Limitations --------------- Limitations with version 05.42.18.00 controller firmware maintenance release and previous releases. 1. Do not cut and paste the information in the DS4000 Storage Manager Version 9 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. (IBM problem record 267873) 2. 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 midrange disk system models. 3. 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. 4. DS4000 Storage Manager prompts you for a password if all hard disk drives are removed from the storage subsystem. After removing all drives from a storage subsystem or if drives do not have power but the controller power is on. The IBM DS4000 Storage Manager will prompt you for a password when trying to start the software or when attempting to perform protected operations. Any password entered will fail. Password information is stored on a reserved area of each hard disk drive on the storage subsystem. Each drive stores a mirrored copy of the password data. When there are no drives in the disk system, the storage management software does not find the password data when you attempt password protected operations. Add one drive to the disk system and retry the operation. If the DS4000 controller unit has power, then turn power off the controller unit. The DS4000 controller unit shall not be powered on until the EXP expansion units are attached and powered on. Properly attach all expansion units (with drives installed), to the DS4000 controller unit and apply power to the EXP. The controller can now be powered on. At this point the midrange disk system can be re-discovered and managed using the IBM DS4000 Storage Manager. 5. Auto LUN/Array Transfer is not enable for IBM AIX and SUN Solaris operating systems. If arrays failover to an alternate controller and the failed controller is replaced and then brought back online, the arrays do not automatically transfer to the preferred controller. The operation must be done manually by selecting the redistributing arrays menu option in the storage subsystem window of the IBM DS4000 Storage Manager. 6. If you get "Error 21 - The operation cannot complete because a ... is in progress" error when you issue a Subsystem Management command from the IBM DS4000 Storage Manager, the command may be cached. If the command is cached, the IBM DS4000 Storage Manager will run the command as soon as the controller resources are available. Wait for at least ten minutes and check to see whether the command has been run. If not, re-attempt the command. 7. The DS4100 disk system 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 fibre channel link up/down events in the controller major event log compared to a DS4000 midrange disk system 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 DS4100 controller, resulting in a greater number of informational events logged. The number of information events reported in the system event log will continue to grow in proportion to data transfer to and from the logical drives. In all cases, the DS4100 controller will always successfully service the timeout I/O on the subsequent retries. 8. The DS4000 Copy Service Remote Mirroring and VolumeCopy features are not supported at this time for DS4100 midrange disk systems. 9. It may take up 12 minutes for the DS4100 to recover after an AC power brown-out event. 10. When connecting DS4000 drive expansion enclosures to the DS4100 midrange disk system, ensure that the unit digits(x1) of the drive expansion enclosure IDs are set to unique values. 11. IBM does not support the conversion an existing DS4100 single controller (DS4100 model 1S_) to a DS4100 dual controller DS4100 model 100)and vice versa. Please contact IBM resellers or representatives for support in the future. 12. There is not support for migrating arrays between a DS4100 single controller setup (DS4100 model 1S_) and a DS4100 dual controller setup (DS4100 model 100)and vice versa. Please contact IBM resellers or representatives for such support in the future. 13. There is no support for drive port in the DS4100 single controller CRU. The DS4100 model 1S_ does not support DS4000 EXP100 drive expansion enclosures. Please contact IBM resellers or representatives for such support in the future. 14. In Microsoft cluster, MSCS configurations, the MSCS service must be stopped and set to manual start after server is rebooted. The Clusdisk driver must be set to offline and the Windows server must be rebooted before uninstalling the RDAC driver in the server. If the Clusdisk driver is not set to offline and the MSCS service is not set to manual start, the MS cluster service will not start after the new RDAC driver is installed. The cluster cannot bring the Quorum disk resources online because the disk signature changes caused the problem. The workaround is stated in the first sentence of this paragraph. To recover from this problem, you must: 1. Look up the old disk signatures of the disk that are defined as cluster disk resources. They could be found either in the registry under the HKLM/System/CurrentControlSet/Services/Clusdisk/Parameters/Signatures registry key or in the cluster.log file. 2. Look up the new disk signatures of the disks that are defined as cluster disk resources using the dumpcfg utility that is packaged in the Microsoft Windows resource kit. 3. Compare the new and old disk signatures. If new disk signature did not match the old signature, you have to change the new disk signature to the old disk signature values by using the dumpcfg command. The syntax of the command is: dumpcfg.exe -s For example, dumpcfg.exe -s 12345678 0 15. In a SAN boot configuration, before updating the Windows RDAC driver in a Windows server, one of the two Fibre Channel (FC) cables that are connected to the server must be disconnected. The Windows server will blue screen during the reboot after the un-installation of the RDAC driver if one of the FC cables is not removed. (IBM problem record 258127) 16. When connecting the EXP100 enclosures, one must set the single digit (X1) of the enclosure ID to unique values. This will prevent the possibility that the controller has the same ALPA as one of the drives in the EXP100 enclosures. This can occur under certain DS4100 controller reboot scenarios. (IBM problem record 261188). ======================================================================= 1.2 Enhancements ---------------- This is a maintenance release of the controller firmware for the DS4100 storage subsystems with single controller option. Please refer to the section 2.1 - Version history for the list of defects that were fixed in this release. ======================================================================= 1.3 Prerequisites ----------------- - DS4100 midrange disk systems with controller firmware version 05.42.xx.xx. - DS4000 EXP100 storage expansion enclosures with ESM firmware version 955x or later. ======================================================================= 1.4 Dependencies ----------------- ATTENTION: DS4100 MIDRANGE DISK SYSTEM CONTROLLER FIRMWARE VERSION 05.42.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X. 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 RESELLER FOR ASSISTANCE. IBM DS4000 Storage Manager Version 8.42 or higher provides full management IBM machine type 1724 (DS4100) storage subsystems that have at least firmware version 05.42.xx.xx. ==================================================================== 2.0 Change History ------------------ ==================================================================== 2.1 Version history. This is the latest maintenance release of IBM DS4000 TotalStorage™ controller firmware / NVSRAM for the following DS4000 midrange disk system models: DS4100 Single controller model. Version 05.42.18.02 07/15/2005 (July, 2005 maintenance release) IBM Problem Record Abstract ------ ------------------------------------------------ 88617 Media Scan effectively disabled for volumes at or near 2TB 88719 CRC error on SATA drive forces retry 87706 Drive timeout value is too small 88091 Excessive error printfs for SATA drive can cause timeouts Version 05.42.18.00 03/18/2005 (March, 2005 maintenance release) IBM Problem Record Abstract ------ ------------------------------------------------ 260503 Storage Partition feature key changed after firmware upgrade and reboot 265068 Media Scan not running on all LUNs 260610 DACstore scrub loops with media scan enabled on one LUN 266752 Email Notification flood from Service Alert 274465 Clearing reservation doesn't set key length hlpct_53446 Free space decreased after delete logical volumes 269899 81850 Duplicate Solaris with DMP host type available while using DS4100 with 05.42.10.00 269900 82742 The controller creates a volume that is smaller than the requested size 269901 82744 The rawCapacity field of the VolumeCandidate should be RAID-factored max capacity rather than actual raw capacity 269902 82976 82452 FC drive failing causes dirty 269903 83561 83520 Memory fault in ssmTimer after excessive bad characters 269904 83612 Power Lines Disturbance causes Acorns to lockup on DS4100 controller 269905 83704 Download flags left set after firmware download fails 269906 83736 83514 During ESM CSB FW Download Test Controller Drive Tray 269907 83837 82874 Controller panic in SOD routines 269908 85249 84075 IO and sysReboot [StressX] test failed with max volumes 269909 85537 82793 The battery age is not updated when reading the profile from the GUI interface on DS4500. 269910 85731 84886 Read Capacity command returns the new capacity before the expansion of a volume is completed 269911 85753 85456 Data corruption after large VolGrp with 2 luns 269912 84892 84378 Potential IO/drive/tray failure is possible due to ESM/mapping failures 269146 83015 77888 76811 Microsoft SCSIPort driver sets a bit in the second byte of Read Capacity CDB which is a reserved bit. CDB validation should ignore this bit and process the command without error. 269914 84627 82306 DBM Blockset mismatch occurred during triple fault test, drive failure, controller reset and failover. Array experienced an exception. 269915 84745 83625 Bad record entry in DBM during watchdog test 269917 81491 No MEL entry when fan is removed from DS4100 controller or Drive Enclosure with firmware 05.42.10.00. 269932 81667 Alarm sounds with no fault light and not faults in MEL log during firmware download with additional drive enclosures attached 269919 83329 82259 (increase buf-t) The array controller has exhausted buf-t structures 269920 79824 70279 Divide by zero error while executing _cfgSetLunScrubRate. The controller was trying to set the scrub rate on a volume that was in a "closed" state. 269921 80084 79485 79298 Data corruption occurred after spindown of GHS drive during copy back followed shortly by reset of the controller. 269922 80220 73883 Drive firmware download failure in DS4100/iSATA combination. 269923 80468 80110 Data corruption reported during Failover and DSS 269924 80595 59651 Subsequent drive failure may cause the controller to use an incorrect "replaced" marked drive. 269925 80715 80081 79269 PANIC: DBM block set mismatch 269926 80756 78907 Data corruption while running I/O to flashcopy on fastt600 where the LBA in the head and tail did match as expected 269927 80938 Support for Hitachi 400GB SATA drive 269928 81164 fcdevs option 2 and 5 do not display Hitachi drives properly 269929 81570 81151 Getting a bcmWriteVPD failure using the MAPI command mfgVPDSet for Power Supply or Midplane VPD data 269930 82012 71065 ESM firmware download on DS4500 caused IO timeout to a drive. An alternate path is attempted but the error flags were not cleared. This error results in controller reboot and Destination Driver Events in the MEL and an "Ancient IO reboot" message in the exception log. hlpct_51223 82169 78999 Mirror relationship becomes out of sync when path is broken between switch ISL 269931 82234 82107 HP-UX LVM read causes continuous AVTs when controller is rebooted. LVM scans all available paths using a read of LBA 8192 for 2 blocks which causes continuous AVTs. 275769 82285 The array controller has exhausted its structures for handling IOs Version 05.42.10.00 - 11/24/2004 - Provides support for the DS4100 Single Controller models (1S_) - Support for the increase in the maximum number of EXP100 drive expansion enclosures that can be connected to a DS4100 midrange disk system. The maximum EXP100 drive enclosure that can be connected to DS4100 is now 7 instead of 4. IBM Problem Record Abstract ------- ------------------------------------------------- 79260 78101 76791 Fixed data corruption problem 79485 79298 Fix data corruption occurred after spindown of GHS 79591 79573 Fix multiple controllers go into PCI lockdown in a large number 79704 79212 Fix data corruption during triple fault test Version 05.42.06.00 - 6/25/2004 240352 76754 Fix ancient I/Os 242386 78004 Fix RAID1 remained degraded after a drive pull and replacement 238953 78355 76490 Fix Host IO Read Errors 78669 Fix IOS IOCTL problem 244474 78170 Fix multiple drive failures problem during power cycling - 05.42.03.0x - 6/18/2004 initial release - Support for IBM TotalStorage DS4100 midrange disk system. ==================================================================== 2.2 Code levels at time of release are as follows ------------------------------------------------- 1. Controller firmware versions (CD): The controller firmware file that is included in this CD release package can be used to install in a DS4100 midrange disk system only. DS4100 Model 1S_ (1SC): SNAP_05421802.dlp 2. Storage Controller NVSRAM versions: The controller NVSRAM file that is included in this web release package can be used to install in a DS4100 only. DS4100 Model 1S_ (1SC): N1724F10LR842V01.dlp Refer to the IBM TotalStorage™ Support web site for the latest released code levels. http://www.ibm.com/servers/storage/support/disk ===================================================================== 3.0 Installation and Setup Instructions --------------------------------------- 3.1 ATTENTION: a. The DS4100 with single controller does not support any drive expansion enclosure attachment. b. The controller firmware version 05.42.xx.xx should not be loaded into the DS4100 with dual controllers (M/T 1724, model 100). The latest version of the controller firmware in the 06.12.xx.xx firmware thread should be used instead. To download firmware, do the following: a. Open the Subsystem Management window. b. Click Storage Subsystem => Download => Firmware. Follow the online instructions. To download NVSRAM, do the following: a. Open the Subsystem Management window. b. Click Storage Subsystem => Download => NVSRAM. Follow the online instructions. 3.2 After the controller firmware and NVSRAM is updated, consider checking the IBM TotalStorage™ Support web site for the latest released drive expansion enclosure ESM firmware and the Fibre Channel or SATA hard drive firmware. http://www-1.ibm.com/servers/storage/support/index.html To download drive expansion ESM firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Download => Environmental (ESM) Card Firmware. Follow the online instructions. To download hard disk drive firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Download => Drive Firmware. Follow the online instructions. ==================================================================== 3.2 Helpful Hints ----------------- 1. The ideal configuration for SATA drives is one drive in each EXP100 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. 2. IBM recommends 1 hot spare per DS4100 disk system unit or EXP100 drive expansion enclosure. 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. Depending on the storage subsystem that you have purchased, you may have to purchase the DS4000 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. 5. 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 midrange disk system serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 6. SAN fabric topology zoning requirement. To avoid possible problem at the host level, it is best practice that all Fibre Channel (FC) Switches must be zoned such that a single FC host bus adapter can only access one controller per storage array. In addition, the zoning requirement also ensures the maximum number of host connections can be seen and log into the controller FC host port. 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 DS4100 midrange disk system (IBM machine type 1724) has two ports per controller. 7. Always connect the power supplies of the DS4100 and its drive expansion enclosures to separate power circuits to maximize protection against lost of power. Please refer to the IBM TotalStorage DS4100 Installation, User's and Maintenance Guide for more information and power on and power off sequence requirement for the DS4100. ======================================================================= 4.0 Configuration Information ----------------------------- 4.1 Configuration Settings -------------------------- 1. By default the IBM DS4000 Storage Manager Version 9 client, the controller firmware 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 NT, create a partition with your host type and map the logical drives to this partition. b. If your host type is Windows NT, you can map your logical drives to the "Default Host Group" or create a partition with a NT host type. When upgrading from previous versions of IBM DS4000 Storage Manager to Version 9. a. If upgrading with no partitions created and you have an operating system other than Windows NT, 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 NT is accessing the default host group, you will need to change the default host type. After upgrading, the default host type is reset to Windows NT. 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 1724 midrange disk system as boot devices, contact IBM support for supported configurations and instructions for configuring LUNs as operating system 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.scr: Setup DS4100 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 DS4100 controllers to have different World Wide Names. The World Wide Names (node) will be different for each controller pair. The NVSRAM default sets the DS4100 controllers to have the same World Wide Names. - EnableDriveMigration.scr: 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.scr: 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.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 heterogeneous 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. ======================================================================= 4.2 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS4000 Storage Manager 8.42 or higher. 1. The intermixing of DS4000 EXP100 (SATA), EXP710 and EXP 700 fibre channel drive expansion enclosures in the same DS4100 midrange disk system is not supported. 2. The DS4000 EXP100 storage expansion enclosure with ESM firmware version 953x and earlier should not be connected to the DS4100 disk system. In addition, the DS4100 disk system will not be able to upgrade the EXP100 enclosures from the 953X version to the required 955x version. 3. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 3542 and 3552. ======================================================================= 5.0 Unattended Mode ------------------- N/A ==================================================================== 6.0 WEB Sites and Support Phone Number -------------------------------------- 6.1 IBM TotalStorage™ Support: Disk Storage Systems web site: http://www.ibm.com/servers/storage/support/disk/ 6.2 IBM TotalStorage™ Disk Storage Systems: Overview Web Site: http://www.ibm.com/servers/storage/disk 6.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 IBM Directory of worldwide contacts IMPORTANT: You should download the latest version of the DS4000 Storage Manager software, the DS4000 disk system 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: http://www-1.ibm.com/servers/storage/support/index.html 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 disk system 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. ==================================================================== 7.0 Trademarks and Notices -------------------------- 7.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: DS4000 IBM FAStT TotalStorage™ the e-business logo xSeries pSeries HelpCenter Microsoft, Windows, and Windows NT 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. ==================================================================== 8.0 Disclaimer -------------- 8.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. 8.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.