This README file contains the latest information about the IBM TotalStorage™ DS4000/DS4000 Storage Server controller firmware version 05.3x.xx.xx. 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 publication for firmware and NVSRAM download instructions. For other related publications (refer to Related Publications in the installation and support guide) and the latest information and updated readme file. Last Update: 11/16/2004 Products Supported: ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4500 | DS4000 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | DS4000 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | DS4000 600 | 1722 | 6LX, 6LU, 60X and 60U | |------------|-----------|--------------|------------------------| | N/A | DS4000 500 | 3552 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | N/A | DS4000 200 | 3542 | 1RX, 1RU, 2RX and 2RU | ------------ --------------------------------------------------- Note: The controller firmware version 05.3x.xx.xx should not be loaded into the DS4100 storage server. 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 DS4000 storage server controller firmware release includes the IBM DS4000 05.3x.xx.xx Storage Server Controller Firmware and NVSRAM files for upgrading the following IBM machine types - 1722(all models), 1742 (all models), 3542 (all models ) and 3552 (all models). 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 publication is available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. In addition, IBM DS4000 FlashCopy and IBM DS4000 Remote Mirror premium feature options are purchased separately. The IBM FlashCopy option requires firmware version 05.00.04.xx or higher and the IBM Remote Mirror option requires firmware version 05.20.0x.xx or higher. The DS4000 storage partitioning premium feature is standard on all IBM DS4000 storage subsystems with the exception of the IBM DS4300 (machine type 1722) storage subsystem. Please contact IBM Marketing representatives or IBM resellers if you want to purchase the IBM DS4000 storage partitioning premium feature option for it. Refer to the IBM Support Web Site for the latest Firmware and NVSRAM files for the IBM DS4000 Storage Subsystems. ======================================================================= 1.1 Limitations --------------------- 1. Upgrading FAStT500 with 512MB Cache. If you are upgrading controller firmware on a FAStT500 (machine type 3552) with 512MB of cache, you will need to stop I/O and reboot the controller before upgrading firmware followed by NVSRAM. To determine Storage Controller cache level, perform the following: a. On a storage management station start the client software and select a storage subsystem. b. Select Tools -> Manage Device to open the Subsystem Management Window. c. Highlight the Storage Subsystem that you are upgrading and then select Storage Subsystem -> Profile. It may take a little time for it to create the Storage Subsystem profile. d. Under the Controllers heading is an entry that displays information similar to the following example: Cache/processor size (MB): 256/32 If this setting is listed as 512/32 you will need to arrange to perform this upgrade procedure at a time that you can stop I/O to the Storage Subsystem in order to ensure a successful firmware download and installation. 2. 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 not powering on drives and only the controller), the IBM DS4000 Storage Manager software will prompt you for a password when trying to start the software or trying 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 storage subsystem, the storage management software does not find the password data when you attempt password protected operations. Add one drive to the storage subsystem and retry the operation. Since the RAID controller unit should not be powered on until the expansion units are attached and powered on, this should be done by powering off the RAID controller unit, properly attaching all expansion units (with drives installed), to the RAID controller unit and powering them on, and then powering the RAID controller unit back on. At this point the storage subsystems can be re-discovered and managed using the IBM TotalStorage DS4000 Storage Manager version 9. 3. Auto LUN/Array Transfer is not enable for , IBM AIX and SUN Solaris OS's. If a controller fails over arrays to the alternate controller and the failed controller is replaced and brought back online, the arrays do not automatically transfer to the preferred controller. This must be done manually by selecting the redistributing arrays menu option in the storage subsystem window of the IBM DS 4000/DS4000 storage manager client program. 4. Display issues when using 256 color settings. A brownish hash pattern is displayed on the windows and in online help when running in 256 color mode. Run the Storage Manager 8 application in a higher display mode. 5. The DS 4000/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. 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 Client, the command may be cached. If the command is cached, the IBM DS4000 Storage Manager Client 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. If the controller in the IBM DS 4000 / DS4000 Storage Server with firmware 05.3x.xx.xx is connected to a SAN with more than 64 host connections per controller port that can log into the controllers, one must either use the switch zoning function or rearrange the SAN connections so that only the maximum number of host connections can be seen and log into the controller. The DS4000 Storage Subsystem DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 Storage DS4300 (IBM machine type 1722) has two ports per controller. The DS4000 storage Subsystem FAStT200 (IBM machine type 3542) has only one port per controller. 8. The IBM DS 4000/DS4000 Storage Server hardware and software is designed to have redundant paths from the host system to ensure the availability of storage. However, it is possible to connect a single host adapter from the host system to one of the controller minihubs and then connect this minihub to the minihub of the other controller. This configuration will create a FC-AL loop between the host adapter and the two IBM DS4000 Storage Server controllers and no redundant path to the host system. When you connect the two minihubs together, always connect the "IN" port of one minihub to the "OUT" port of the other minihub or vice versa. Do not connect the "IN" port of one to the "IN" port of the other minihub or the "OUT" port of one minihub to the "OUT" port of the other minihub. 9. When creating a Remote Mirror of a base volume the following restriction applies. First, you have created a snapshot of a base volume and the base volume is receiving I/O. Second, you decide to create a mirror relationship, using the base volume as the primary volume in the mirrored pair. As you create the mirror relationship, the snapshot volume is failed. The work around is to stop I/O to the base volume while you are creating the mirror relationship. Alternatively, if the mirror relationship is created before creating the snapshot volume, this will not happen. 10. In MSCS configurations, the MSCS service must be stopped and set to manual start after server rebooting, the clusdisk driver must have to be set to offline and, then, the 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 servive will not start after the new RDAC driver is installed because it can not bring the Quorum disk resource online. The problem is caused by the changing of the disk signatures. 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 11. Before updating the RDAC driver in a server that is setting up as San-boot, one of the two Fibre Channel (FC) cables that are connected to the server must be disconnected. The server will bluescreened during the reboot after the un-installation of the RDAC driver if one of the FC cables was not removed. (258127 - PR 82146) 12. Controller diagnostics will not run in a DS4000/DS4000 Storage server with single controller. ======================================================================= 1.2 Enhancements ----------------- N/A ======================================================================= 1.3 Prerequisites ------------------ N/A ======================================================================= 1.4 Dependencies ----------------- The IBM TotalStorage DS4000 Storage Manager version 9 provides full management support IBM machine types 3552 and 3542 storage subsystems that have at least firmware version 04.00.02.xx, IBM machine type 1742 (models 1RX, 1RU) storage subsystem that have at least firmware version 05.00.04.xx or IBM machine types 1742 (models 90X, 90U) and 1722 storage subsystem that have at least firmware version 05.3x.xx.xx. Only the IBM TotalStorage DS4000 Storage Manager version 9 supported management function on controllers with firmware version 04.xx.xx.xx to 04.xx.01.xx is controller firmware and NVSRAM download. ======================================================================= 2.0 Change History ----------------------------- ====================================================================== 2.1 Version History ----------------------------- FAStT200,500,700,900 --------------------- 05.30.19.00 07/2004 Third Maintenance Release 76117 Rebooting controller during FlashCopy/SnapShot 71777 Can't create volume if drive sizes are similar (181 and 146GB) 72991 hlpct_42401 Error importing a 7.3 Gig FlashCopy LUN 73058 C221434 Recovery guru indicates Subsystem errors when no error exists 72230 (CL #71757) AWM and Recovery Guru give conflicting status 78208 (CL #78004) 242386 - RAID1 remained degraded after a drive pull/replace 78344 (CL #77338) Fatal vproc after replacing drive 78606 (CL #78357) disk array became unmanageable in benchmark 73225 (CL #72542) Log Select with PCR bit set to 1 fails to reset drive stat 73409 (CL #70407) C221434 Recovery guru indicates Subsystem erro 73427 (CL #71088) Drives came back unassigned after powering off t 73686 (CL #72414) Inconsistent vdUnit structure between two controllers 75055 DCE operation on RAID 1 volume invalidates tray loss protection 75283 C236739 I/O error during controller offline testing with SUN and WS03 76013 (CL #75805) Incomplete transfer of host information during v 76148 Controller assertion when validateCmdInfo routine calls cfgSaveCmdInfo 76184 (CL #75746) Ancient I/O (mode select I/O) during 2 second po 76881 IAF process hangs if multiple IAFs in progess on same volume group 77497 (CL #77464) Controllers did not agree on the state of a spindown drive 77530 (CL #65736) How a Controller locks down on too many ECC errors should 77534 (CL #75629) MEMORY FAULT in "symPrepareAltControllerInfo" 77552 (CL #75895) Request for ctlr resets to be blocked by ctlr du 05.30.16.00 04/2004 Second Maintenance Release 71777 (RW #67670) Can't create volume if drive sizes are similar (181 and 146GB) 72991 (CL #72339) CMVC-hlpct_42401 Error importing a 7.3 Gig FlashCopy LUN 73058 (CL #70407) C221434 Recovery guru indicates Subsystem errors when no error exists 72244 (RW #71546) (CL #59229) CAL00622 Have FW check alt path to FC drive before failing 68894 Analysis of a MEL log shows Dacstore Scrub is repeating on a volume group 69761 (RW #68870) (CL #68351) TD_PT871 I/O Error after Sonoran 3 controller swapped into 69941 (CL #69630) There is a memory leak when sending DOMI messages. 70383 (CL #70309) C222814 Data Corruption on AIX hosts. 70419 (CL #68603) Ancient I/Os reported during sysReboot stress 70551 (CL #68445) C219318 CMVC 217537: Data miscompare while doing online controller 71550 (CL #62602) CAL01413 :Critical Event for Loss of Drive Path Redundancy - Modify the NVSRAM file to disable Cache Sync in the W2K het host region. 05.30.12.00 12/2003 First Maintenance Release 05.30.09.01 09/2003 Initial Web Release initially a fee base firmware. 05.30.09.00 09/2003 Initial Release and Upgrade from 04.xx.xx.xx DS4300 ----------- 05.34.04.00 Second Maintenance Release 72232 (CL #71757) AWM and Recovery Guru give conflicting status 78200 (CL #78004) 242386 - RAID1 remained degraded after a drive pull/replac 78345 (CL #77338) Fatal vproc after replacing drive 78606 (CL #78357) disk array became unmanageable in benchma 74127 (CL #70794) One volume never finishes reconstruction when 75769 C237800 Multiple Hot Spare failures. 76014 (CL #75805) Incomplete transfer of host information during v 76185 (CL #75746) Ancient I/O (mode select I/O) during 2 second 76248 (CL #76148) Controller assertion when validateCmdInfo routine calls 76265 (CL #75283) C236739 I/O error during controller offline testing 76723 (CL #75055) DCE operation on RAID 1 volume invalidates tray loss prote 77498 (CL #77464) Controllers did not agree on the state of a spindown drive 77531 (CL #65736) How a Controller locks down on too many ECC errors should 77535 (CL #75629) MEMORY FAULT in "symPrepareAltControllerInfo" 77553 (CL #75895) Request for ctlr resets to be blocked by ctlr du 77577 (CL #69894) Controller did not clear AEN after the failed drive was replaced 73409 (CL #70407) C221434 Recovery guru indicates Subsystem error 73275 (CL #73265) Pick up Mojave 2 Flash driver changes into Sonoran 3 threa 76148 Controller assertion when validateCmdInfo routine calls cfgSaveCmdInfo 75283 C236739 I/O error during controller offline testing with SUN and WS03 05.34.02.00 04/2004 First Maintenance Release The controller firmware version 05.34.xx.xx replaces the controller firmware version 05.33.xx.xx. 70561 (CL #68445) C219318 CMVC 217537: Data miscompare while doing online controller firmware downloads 70772 (CL #68894) Analysis of a MEL log shows Dacstore Scrub is repeating on a volume group 72993 (CL #72339) CMVC-hlpct_42401 Error importing a 7.3 Gig FlashCopy LUN 73059 (CL #70407) C221434 Recovery guru indicates Subsystem errors when no error exists 70385 (CL #70309) C222814 Data Corruption on AIX hosts. 70443 (CL #68872) Stable storage method write Header sends address of a pointer to main write Header method. 70444 (CL #67313) Memory fault when error reading drive headers at start-of-day. 67718 C214226 Logical drive shows rebuilding in Client but has finished in Controller. 67990 (CL #67720) Improve handling of drive reported parity/CRC error 68263 (CL #67670) Can't create volume if drive sizes are similar (181 and 146GB 68387 (CL #68281) Drive failed by controller still being logged after removing 68506 (CL #68410) "Link Error" component location = "none" in MEL 68580 (CL #68565) NVSRAM setting to ignore Sync Cache requests 68736 (CL #68330) DDE with devnum of 0 is logged when removed drive is present 69202 (CL #68807) Profile not reporting correct unconfigured capacity on volume group 05.33.07.00 09/2003 Initial Release 05.33.05.00 09/2003 Initial Release for Netware only ====================================================================== 2.2 This is a maintenance release of the DS4000 Storage Server controller firmware and NVSRAM. The fix lists for the 05.30.21.00 and 05.34.07.00 controller code threads are as followed: 05.34.07.00 code thread ----------------------- PR # CMVC # Problem Synopsis 71338 253097 Need a way to clear both SSTOR header and DBM database from a given dr 78095 253100 (CL #76791) Data corruption detected by hammer after transfe 78384 253101 (CL #75360) Data Corruption while running Triple Fault with 78437 253104 (CL #74842) Data corruption when pulling and replacing a dri 79063 253106 (CL #78862) Reconstruction active to a GHS for the second su 79479 253107 (CL #79298) Data corruption occurred after spindown of GHS d 79556 253109 (BST) The capacity of the hotspare shows in the loagical/physical view 79698 253111 (CL #79212) Data corruption during tripple fault test       79819 253112 (CL #70279) Divide by zero error while executing _cfgSetLunS 81761 255595f_1 memory leak problem with 5.34.02.00 81444 255496 DS4000 RAID 10 not any longer redundant after DVE 77628 253323 Volume state not consistent between the controllers 77580 253310 fControllers did not agree on the state of a drive 77878 253330 Memory fault during SOD when IAC received from 77950 253336 Memory fault while running sysReboot with 78049 253340 Mapping exceeds 32-lun limit for default host 78348 253394 Watchdog timeout while running I/Os and sysReboot 05.30.21.00 code thread ----------------------- PR # CMVC # Problem Synopsis 71338 253097 Need a way to clear both SSTOR header and DBM database from a given dr 78095 253100 (CL #76791) Data corruption detected by hammer after transfe 78384 253101 (CL #75360) Data Corruption while running Triple Fault with 78437 253104 (CL #74842) Data corruption when pulling and replacing a dri 79063 253106 (CL #78862) Reconstruction active to a GHS for the second su 79479 253107 (CL #79298) Data corruption occurred after spindown of GHS d 79556 253109 (BST) The capacity of the hotspare shows in the loagical/physical view 79698 253111 (CL #79212) Data corruption during tripple fault test       79819 253112 (CL #70279) Divide by zero error while executing _cfgSetLunS 79590 hlpct52107(CL #79573) hlpct52107 Multiple controllers go into PCI lockdown in a 81062 hlpct_53699 upgraded fw to 05.30.19, unconf capacity is appear 78999 hlpct_51223 mirroring relationship be established once isl out 81444 255496 DS4000 RAID 10 not any longer redundant after DVE 77628 253323 Volume state not consistent between the controllers 77580 253322 Controller did not clear AEN after the failed drive 77502 253310 fControllers did not agree on the state of a drive 77878 253330 Memory fault during SOD when IAC received from 77950 253336 Memory fault while running sysReboot with 78049 253340 Mapping exceeds 32-lun limit for default host 78348 253384 Fatal vproc after replacing drive 80018 253394 Watchdog timeout while running I/Os and sysReboot The controller firmware version 05.34.02.00 replaces the controller firmware version 05.33.07.00. ======================================================================= 2.3 Code levels at time of release are as follows ------------------------------------------------- a. Controller firmware version DS4500 : FW_05302100_05300300 DS4400 : FW_05302100_05300300 DS4300 (non-Turbo) : SNAP_05340700 FAStT500 : FW_05302100_05300300 FAStT200 : SNAP_05302100 b. NVSRAM versions: DS4500 : N1742F900R830V06 DS4400 : N1742R700R830V05 DS4300 (non-Turbo) : N1722F600R834V01 DS4300 (6LU/6LX) : N1722F60LR834V04 FAStT500 : N3552F500R830V05 FAStT200 : 1RU - N3542-1RUR830V09 2RU - N3542-2RUR830V12 Refer to the http://www.ibm.com/storage/support/DS4000 IBM TotalStorage™ Disk Storage Systems Technical Support web site for the latest released code levels. ======================================================================= 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 Important: You must install the firmware update prior to downloading the NVSRAM update. 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™ Disk Storage Systems Technical Support web site for the latest released drive expansion enclosure ESM firmware and the Fibre Channel hard drive firmware. 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. 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. 2. 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. - IBM DS4300 storage subsystem (machine type 1722): The standard configuration does not have the DS4300 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. ======================================================================= 4.0 Configuration Information ----------------------------- 4.1 Configuration Settings -------------------------- 1. By default the IBM DS4000 Storage Manager 9.1x 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.10. 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 1722, 1742, 3542 or 3552 storage subsystems as boot devices, contact IBM support for supported configurations and instructions for configuring LUNs in the IBM storage subsystems 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.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. - 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. 4. When you are configuring IBM machine type 1742 or 3552 storage controllers in host cluster Remote Mirror configurations, contact IBM support for supported host cluster configurations and instructions for configuring IBM storage controllers in clustered Remote Mirror configurations. ======================================================================= 4.2 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS4000 Storage Manager 9.10. 1. 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. 2. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 1722, 1742, 3542 and 3552. ======================================================================= 5.0 Unattended Mode --------------------- N/A ======================================================================= 6.0 WEB Sites and Support Phone Number ---------------------------------------- 6.1 IBM TotalStorage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 6.2 IBM TotalStorage™ Marketing 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 IMPORTANT: You should download the latest version of the DS4000 Storage Manager host software, the DS4000 storage server 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. ======================================================================= 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: 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.