This README file contains the latest information about installing IBM TotalStorage™ FAStT Storage Manager for Windows NT 4.0, Windows 2000 and Windows Server 2003. Refer to the IBM TotalStorage™ Support Web Site or CD for the installation and support guide. For other related publications (refer to Related Publications in the installation and support guide) and the latest information and updated readme file. Last Update: 04/05/2004 Products Supported: ---------------------------------------------------- | | Machine Type | Model | |-----------|--------------|-------------------------| | FAStT 900 | 1742 | 90X , 90U | |-----------|--------------|-------------------------| | FAStT 600 | 1722 | 6LX , 6LU , 60X and 60U | |-----------|--------------|-------------------------| | FAStT 700 | 1742 | 1RX , 1RU | |-----------|--------------|-------------------------| | FAStT 500 | 3552 | 1RX , 1RU | |-----------|--------------|-------------------------| | FAStT 200 | 3542 | 1RX , 1RU , 2RX and 2RU | ---------------------------------------------------- Note: The FAStT Storage Server controller firmware version 05.40.xx.xx and earlier along with its associated NVSRAM files should not be loaded into FAStT storage servers connected to FAStT EXP100 drive expansion enclosures. For FAStT Storage Servers connected to FAStT EXP100 drive expansion enclosures, the controller firmware version 05.41.xx.xx and its associated NVSRAM file must be used instead. 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 -------------- 1.1 Overview -------------- This is the latest release of the IBM FAStT Storage Manager for Windows NT 4.0, Windows 2000 and Window Server 2003. The \SM8clientcode directory contains the files necessary for installing the IBM FAStT Storage Manager Software in the Microsoft Windows Operating System (OS) environments. There are three separate IBM FAStT Storage Manager host software packages for Microsoft Windows OSes - Windows NT 4.0 and Windows 2000, Window Server 2003 Intel Architecture 32bit and Window Server 2003 Intel Architecture 64bit. Please select the appropriate package for your operating system environment. The IBM TotalStorage FAStT Storage Manager version 8.4x Installation and Support Guide for Intel-based Operating System Environments is also available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. It contains the instructions for installing the IBM FAStT Storage Manager host software. Important: This release of IBM FAStT Storage Manager host software supports all FAStT Storage Servers with general released firmware versions from 04.00.02.xx up to 05.41.xx.xx. Because the FAStT Storage Servers with controller firmware 05.41.xx.xx are not supported in all FAStT-supported Operating System environments, there will be no IBM FAStT Storage Manager host software version 08.41.xx.xx packages for those Operating System environments. The IBM FAStT Storage Manager host software version 08.40.xx.xx packages will support the FAStT Storage Servers with general released firmware versions from 04.00.02.xx up to 05.40.xx.xx only. Refer to the IBM Support Web Site for latest FAStT controller firmware and NVSRAM files for IBM machine types 1722, 1742, 3542 and 3552. The latest controller firmware versions supporting FAStT600 storage servers available free-of-charge are of the 05.34.xx.xx code thread. The latest controller firmware versions supporting FAStT200, FAStT500, FAStT700 and FAStT900 storage servers available free-of-charge are of the 05.30.xx.xx code thread. You can upgrade FAStT600, FAStT700 and FAStT900 storage servers to the 5.40.xx.xx controller firmware version only by purchase option. In addition, the controller firmware version 05.41.xx.xx is shipped with IBM FAStT EXP100 drive expansion enclosure only. New features that are introduced with the controller firmware version 05.4x.xx.xx or newer will not be available for any FAStT storage server controllers without the controller firmware version 05.4x.xx.xx installed. Please contact your IBM service representative or IBM resellers for purchasing info. ======================================================================= 1.2 Limitations ---------------- 1. If you are upgrading controller firmware in IBM FAStT500 storage controller (MT 3552)with 512MB Cache, you will have to stop I/O and reboot both controllers before upgrading firmware followed by NVSRAM. You can reboot the controllers either by power cycling the storage subsystem or by pressing the Reset button on both controllers. The Reset button is located on the right of the indicator lights in the opening on the front of each controller unit. 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 FAStT 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 rediscovered and managed using the IBM FAStT Storage Manager software. 3. 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 FAStT Storage Manager Client, the command may be cached. If the command is cached, the IBM FAStT 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. 4. The Disable/Enable and Uninstall menu functions are not available when you right-click the RDAC Virtual Adapter entry in SCSI and RAID controllers list of the Device Manager folder. The folder is in the Computer Management window. You must use the Add/Remove program function in the Control Panel window to uninstall or to disable the IBM FAStT Storage Manager RDAC device. To re-enable the IBM FAStT Storage Manager RDAC device, follow the instructions in the IBM FAStT Storage Manager version 8.3 Installation and Support Guide for Windows NT and Windows 2000. 5. You must always uninstall IBM FAStT Storage Manager RDAC before you uninstall the Host Bus Adapter driver. Failure to do so may result in system hung or blue-screen. 6. When creating a Remote Mirror of a base logical drive, in the case where a FlashCopy of the base logical drive has already been created, the following restriction applies. If the Remote Mirror relationship is created while the base logical drive is receiving I/O, the FlashCopy logical drive will be failed. The work around is to quiesce I/O to the base logical drive while you are creating the remote mirror relationship. Alternatively, if the Remote Mirror relationship is created before creating the FlashCopy logical drive, the FlashCopy logical drive will not be failed. 7. When alternately switching back and forth the roles of the logical drives in a remote mirrored relationship, Windows NT4 and Windows 2000 may cache the file(s) on the logical drive(disk) in memory and use these cached data instead of going out to the disk to get the data. This windows OS behavior may make the data look like it was not synchronized between logical drives in a remote mirrored relationship. The fix to the problem is to dismount the primary logical drive in the server before demoting it to secondary role. In Microsoft Windows environment, this is best done by shutting down the server that the primary logical drive is mapped to. Then, promote the secondary logical drive to the primary role and hot_add it to the appropriate server. If the logical drive is of "Dynamic Disk" type, there is a possible solution without requiring server to be shut down. First, in the server that has the primary logical drive, run the SMrepassist program in the FAStT Storage Manager 8.xx util directory with the -f option to flush the cached data to disk. Then, promote the secondary logical drive and hot_add it to the appropriate server. Before promoting the logical drive to primary role in the original server, force a failure to the disk, for example, by running a chkdsk on the disk. Then, promote the logical drive to primary role in the original server and hot_add it. One may have to reactivate the disk after it is hot_added to the server. If the server environment prevents the server from being rebooted and the logical drive is of "basic disk" type, you may use the following steps 1. In the server that has the primary logical drive, run the SMFlashCopyAssist program in the FAStT Storage Manager 8.3x util directory with the -f option to flush the cached data to disk. 2. Using the FAStT Storage Manager to remove the LUN mapping of the logical drive that had the primary role from its server (host computer). 3. Promote the secondary role LUN to the primary role and hot_add it in the appropriate server assuming that the LUN mapping is already defined for this server in the FAStT storage subsystem. 4. Before promoting the logical drive to primary role in the original server, run Hot_add program or initiate a Scan for Hardware Changes task in the original server. This is to remove the logical drive from the available disks. In W2K, you may see Unsafe Removal of Devices messages. 5. Using the FAStT Storage Manager to add the LUN mapping of the logical drive that will be promoted to primary role to the original server(host computer). 6. Promote the Logical Drive to Primary role and hot_add it in the original server. If you are unable to hot_add the logical drive or the data still appears to be mismatched, you must reboot the server. 8. When the FAStT storage subsystem controller firmware is upgraded from any version 05.00.xx.xx or earlier to version 05.2x.xx.xx or later, all of the Windows 2000 servers that had LUNs mapped in this storage subsystem must be rebooted after the new FAStT storage subsystem controller firmware and NVSRAM are successfully applied. The reason is that when the new FAStT storage subsystem controller firmware is installed, the controller returns the first four bytes of the firmware revision in the Product Revision field of the SCSI LUN inquiry data. Windows 2000 uses the Product Revision data as part of the LUN identification. So, as the Product Revision data changes due to the new firmware revision level, Windows 2000 thinks that the LUNs with the old Product Revision data were removed from the server. When the 'scan for hardware changes' task is executed by running the FAStT storage manager hot_add utility or by selecting the Scan For Hardware Changes menu option of the Devices folder in the Computer Management window, Windows 2000 displays Unsafe Removal of Devices dialogs for these LUNs. The devices in these dialogs are RDAC Virtual Disks and xxxx SCSI devices where xxxx are either 1742, 3552 or 3542 depending on the model type of FAStT storage server(s) that the Windows 2000 server had LUNs mapped from. The Windows 2000 server will lose connectivity to the LUNs in the FAStT storage that has firmware updated. The server must be scanned again for hardware changes. If the logical drives are not added back to the server, one must reboot the server to reconnect to the logical drives. This problem will not occur when upgrading the FAStT storage subsystem controller firmware from version 05.20.xx.xx to version 05.3x.xx.xx or later because the product revision data field was fixed at 0520. 9. When the server HBA ports are directly connected to the FAStT storage server controllers, do not download firmware and NVSRAM files to the controllers with IOs being generated to the LUNs in the FAStT storage server. There is no IOs restriction in SAN Fabric environment i.e. when the HBA port are connected to the FAStT storage server controller ports via Fibre Channel switches. 10. The supplied SMrepassist utility did not utilize Microsoft Volume Shadow Services APIs to quiesce the LUNs. Appropriate steps are still need to shut down/quiesce the applications like MS Exchange and SQL Server before the FlashCopy logical drive can be made. 11. Rebooting a host server might cause its mapped LUNs move to a non-preferred path. Use the FAStT Storage Manager client program to redistribute the LUNs to their preferred path. 12. Uninstalling RDAC may cause Windows Dynamic disks to fail. After the new RDAC is installed and the server is rebooted, these disks must be reactivated and Chkdsk must be run. The work-around is to stop the applications and remove the drive letters or the mount points to these disks before uninstalling and reinstalling RDAC. 13. The current RDAC driver will coexist with Storport model driver as long as it is not the driver for the adapter that talks to the LUNs in the FAStT storage subsystems. Note: the current release drivers for all of the Fibre Channel host bus adapters that FAStT Storage Servers support are based on the Scsiport model. 14. In xSeries x330 server, when two of the Dynamic disks are mirrored together by the Windows OS and the LUN that these disks are defined on failovers/failbacks, the server might hang after failover. There is no work-around. 15. Dynamically changing the cache read ahead multiplier setting via the storage manager client may result in an error message indicating the operation has failed. Despite the error message, the request to change the cache read ahead multiplier will remain queued to the controllers and will eventually complete when I/O activity to the storage subsystem has subsided. In order to avoid the error message and any delays in the cache read ahead multiplier value changing, it is recommended to change the cache read ahead multiplier when the subsystem is in a quiesced state. 16. This following behavior applies for the direct Fibre Channel connection setup between the FAStT F600 storage server host ports and the server HBA ports only. If all FAStT F600 host ports are occupied, the FAStT600 event log may show "host-side data rate negotiation failed" error when the server is booted up, this is normal error that were generated during the host rate negotiation routine inside the FAStT 600 storage server. 17. Windows 2000 and Windows Server 2003 share the following host type options: - Windows 2000/Server 2003 non-clustered - Windows 2000/Server 2003 clustered If these host types do not appear in the host type pull down menu, use these host type options instead. - Windows 2000 non-clustered - Windows 2000 clustered 18. In a direct Fibre Channel connection between the FAStT storage server and the HBAs in the host server, the system bluescreen may occur if the FAStT storage server is powered off. The work around is to power down the server first before powering down the FAStT storage server. 19. Only logical drives that are configured as "Basic Disks" in the Windows Disk Management folder can have FlashCopy made. The FlashCopy of a logical drive configured as "Dynamic Disk" type will always be failed by the FAStT storage server when it is added to the host server. 20. There is not an IA-64 version of the FAStT Management Suite Java (FAStT_MSJ). Use the 32-bit version of the FAStT Management Suite Java for the Windows Server 2003 64-bit edition. However, one should uninstall it once the diagnostic is completed. It could cause the server to bluescreen in heavy IO loads. 21. Veritas DMP is not supported at this time in Windows operating environment. Please contact IBM representatives or resellers for the availability of support. 22. When managing the FAStT Storage Servers with firmware version 05.3x.xx.xx, the Help window of the Subsystem Management window may not be displayed correctly the topics that are listed as result of executing a full text search. 23. When migrating array(s) from a dual controller FAStT storage server to a single controller FAStT storage server, you must first set the preferred owner of the to-be-migrated array(s) to be controller A before inserting it into the drive slots of a single controller FAStT storage server. Otherwise, the array(s) will not be added to the single controller FAStT storage server correctly which might cause problems. 24. When saving the FAStT storage server event log entries, it may take up to several minutes to save all entries in the event log depending on the FAStT management workstation resources. However, the FAStT Storage Manager client GUI will show the completion of the event log saving almost instantly. The work around is to check the file size of the file that the event log entries are saved periodically; if the file size does not change, the event log saving is completed. 25. You must suspend all I/O while ESM firmware downloads if you select multiple enclosures for downloading ESM firmware. If you select only one enclosure for download at a time, you can download ESM firmware with I/Os. However, IBM recommends that you suspend all I/O activity to perform firmware upgrades. 26. When managing a single controller FAStT Storage Server model, do not use the menu option - Configuration->Automatic... - in the Subsystem Management window to create LUNs. You might not be able to access or manage LUNs that are created this way. ======================================================================= 1.3 Enhancements ----------------- Please refer to the New Features section of the IBM FAStT Storage Manager version 8.4x Installation and Support Guide for Intel-based Operating System Environments. ======================================================================= 1.4 Prerequisites ------------------ 1. It is a requirement to have support for greater than 8 LUNS installed before continuing with the installation. To support more than 8 LUNS, you must install Windows NT Service Pack 5 or greater. ======================================================================= 1.5 Dependencies ----------------- IBM FAStT Storage Manager version 08.4x.xx.xx provides full management support for IBM machine types 3552 and 3542 storage controllers that have at least firmware version 04.00.02.xx, IBM Machine type 1742-900 and 1742 storage controllers that have at least firmware version 05.00.04.xx or IBM Machine type 1722 storage controllers that have at least firmware version 05.3x.xx.xx. The only IBM FAStT Storage Manager version 08.4x.xx.xx 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 ----------------------------- This is the latest release of IBM FAStT TotalStorage™ Storage Manager Host software for Windows NT 4.0, Windows 2000 and Windows Server 2003. ======================================================================= 2.1 Key Features --------------------------------------------------------------------- - Support for FAStT600 single controller model 6LX, 6LU ======================================================================= 2.2 Client Code levels at time of release are as follows --------------------------------------------------------- Important: This release of IBM FAStT Storage Manager host software supports all FAStT Storage Servers with general released firmware versions from 04.00.02.xx up to 05.41.xx.xx. Because the FAStT Storage Servers with controller firmware 05.41.xx.xx are not supported in all FAStT supported Operating System environments, there will be no IBM FAStT Storage Manager host software version 08.41.xx.xx packages for those Operating System environments. The IBM FAStT Storage Manager host software version 08.40.xx.xx packages supports FAStT Storage Servers with general released firmware versions from 04.00.02.xx up to 05.40.xx.xx only. For Microsoft Windows NT4 and 2000: 1. IBM FAStT Storage Manager Client version: 08.41.G5.04 2. IBM FAStT Storage Manager RDAC version: a. Windows 2000: 08.41.95.02 b. Windows NT: 08.40.25.00 3. IBM FAStT Storage Manager Agent version: 08.41.25.01 4. IBM FAStT Storage Manager Utilities version: 08.41.25.00 For Microsoft Windows Server 2003 32 bit (IA-32): 1. IBM FAStT Storage Manager Client version: 08.40.G5.04 2. IBM FAStT Storage Manager RDAC version: 08.40.35.03 3. IBM FAStT Storage Manager Agent version: 08.40.35.00 4. IBM FAStT Storage Manager Utilities version: 08.40.35.00 For Microsoft Windows Server 2003 64 bit (IA-64): 1. IBM FAStT Storage Manager Client version: 08.40.G5.04 2. IBM FAStT Storage Manager RDAC version: 08.40.35.03 3. IBM FAStT Storage Manager Agent version: 08.40.35.00 4. IBM FAStT Storage Manager Utilities version: 08.40.35.00 Refer to the http://www.ibm.com/storage/support/fastt IBM TotalStorage™ Disk Storage Systems Technical Support web site for the latest released code levels. ======================================================================= 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 Step-by-step instructions for this code update are as follows ------------------------------------------------------------------ 1. Install and update the driver for the IBM FAStT, FC-2 or FC2-133 Host Bus Adapter. a. Install the hardware by using the instructions that come with the adapter. b. Install the IBM FAStT Host Adapter driver by using the instructions provided in the readme.txt file located in either the Host_Adapter directory on this installation CD or from the appropriate driver package that is downloaded from the IBM Support Web site. 2. Install the new Storage Manager host software from the appropriate CD-ROM directory for your Operating Systems or from the host software package that you downloaded from the IBM Support Web site. If there are previous version of the IBM FAStT Storage Manager version installed in the system, you do not need to uninstall it first before installing the new version of the storage manager software. You just have to click Yes in the pop-up window to overwrite the previous installation. Refer to the IBM FAStT Storage Manager version 8.4x Installation and Support Guide for Intel-based Operating System Environments for detailed installed instructions. ======================================================================= 3.2 Refer to the Host_Adapter directory on the installation CD for the applicable drivers. Refer to the http://www.ibm.com/storage/support/fastt IBM TotalStorage™ Disk Storage Systems Technical Support web site for the latest supported host adapters, device drivers, and updated readme. ======================================================================= 3.3 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 FAST storage partitioning premium feature option or an option to upgrade the number of supported partitions in a storage subsystem. Please see IBM Marketing representatives or IBM resellers for more information. - IBM FAStT600 storage subsystem (machine type 1722): The standard configuration does not have the FAST storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. The IBM FAStT600 Turbo option comes with 8 partition storage partitioning premium option installed. An upgrade to 64 partitions can be purchased for the IBM FAStT600 Turbo option. - IBM FAStT200, FAStT500, and FAStT700 storage subsystems (machine type 3542, 3552 and 1742 - models 1RU and 1RX, respectively): The standard configuration has 64 partition storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM FAStT900 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. 3. Do not delete the Access LUN or Access Volume. The Access LUN is required by the SMClient to communicate with the storage controllers when using the in-band management method. ======================================================================= 4.0 Configuration Information ----------------------------- 4.1 Configuration Settings -------------------------- 1. By default, the IBM FAStT Storage Manager 8.3 and higher firmware does not automatically map logical drives when the IBM FAStT storage partitioning premium feature is enabled. This means that the logical drives after being created are not automatically presented to the host systems. For a new installation, after creating new arrays and logical drives; a. If the host OS type is not Windows NT, create a partition with the appropriate OS host type and map the logical drives to this partition. b. If your host OS type is Windows NT non-clustered (SP5 or higher), you can map your logical drives to the "Default Host Group" or create a partition with Windows non-clustered (SP5 or higher) host type. When upgrading from previous versions of IBM FAStT Storage Manager to version 8.4x. a. If you are upgrading with no defined storage partitions in operating system other than Windows NT, you will need to create a storage partition with the appropriate operating system host type and map the logical drives from the "Default Host Group" to this partition. b. If you are upgrading with defined 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 to this operating system host type after upgrading. The FAStT Storage Manager upgrading will reset the default host type to Windows NT host type. Refer to the IBM FAStT 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 controllers as boot devices, contact IBM support for supported configurations and instructions for configuring LUNs in IBM FAStT 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 Hardware status and information ----------------------------------- New installations for IBM Machine types 1722, 1742, 3552, and 3542 should be installed with the IBM FAStT FC2-133 Host Bus Adapter and Microsoft Windows device driver version 8.2.3.63 or higher. For more information, refer to the IBM Support Web site. ======================================================================= 4.3 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM FAStT Storage Manager 8.4x. 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, 2109-S8 or 3534-F08. In this configuration, the hub is connected between the fibre channel switch and the IBM FAStT storage subsystem controller ports. 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/storage/support/fastt 6.2 IBM TotalStorage™ Marketing Web Site: http://www.storage.ibm.com/hardsoft/disk/fastt/index.html 6.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: 800-IBM-SERV (800-426-7378) Hardware Support #: 800-426-4378 Software Support #: 800-237-5511 6.4 Website for the World Wide Support Phone list: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. ======================================================================= 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 HelpCenter Linux is a registered trademark of Linus Torvalds. 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. 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.