This README file contains the latest information about installing IBM TotalStorage™ FAStT Storage Manager version 8.3 for 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: 07/24/2003 Products Supported: --------------------------------------------------- | | Machine Type | Model | |-----------|--------------|------------------------| | FAStT 900 | 1742 | 90X , 90U | |-----------|--------------|------------------------| | FAStT 700 | 1742 | 1RX , 1RU | |-----------|--------------|------------------------| | FAStT 500 | 3552 | 1RX , 1RU | |-----------|--------------|------------------------| | FAStT 200 | 3542 | 1RX , 1RU ,2RX and 2RU | --------------------------------------------------- Note: This storage manager software release for Windows Server 2003 will not support FAStT 600 - machine type 1722, models 60X and 60U. ======================================================================= 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 IBM Storage Manager release includes the IBM FAStT Storage Manager version 8.3 for all versions of Windows Server 2003. The Win32 and the Docs CD-ROM directories contain the documentation and files necessary for installing the IBM FAStT Storage Manager Software for Windows Server 2003. The IBM FAStT Storage Manager version 8.3 Installation and Support Guide for Windows NT, Windows 2000 and Windows Server 2003 guide is also available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. Refer to the IBM Support Web Site for latest Firmware and NVSRAM files for IBM machine types 1722, 1742, 3542 and 3552 if you are at firmware version 05.00.xx.xx or higher. ======================================================================= 1.2 Limitations ---------------- 1. If you are upgrading controller firmware in IBM FAStT500 storage controller 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. The Windows 2000 RDAC Driver will not contain a Microsoft Digital Signature. When you install the IBM FAStT Storage Manager RDAC software package for the first time, the following message will appear: Software Package Unknown This message is expected and the user should proceed with the installation of the IBM FAStT Storage Manager RDAC software package. 3. 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. 4. Auto LUN/Array Transfer is not enable for Windows OS's. If a controller fails over arrays to the alternate controller and the failed controller is replaced and brought back online, the arrays will not automatically transfer to the preferred controller. This must be done manually by selecting the Redistribute Logical Drives menu option in the IBM FAStT storage manager client GUI. 5. 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. 6. The FAStT 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 changes to window resize pointer, left click and hold to grip the window edge to resize it. 7. 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. 8. If the controller in the IBM FAStT 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 FAStT Storage Subsystem FAStT900, FAStT700 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The FAStT Storage FAStT600 (IBM machine type 1722) has two ports per controller. The FAStT storage Subsystem FAStT200 (IBM machine type 3542) has only one port per controller. 9. If you define a large number of arrays, you may not be able to right-click a logical drive and get a pop-up menu in the Physical View of the Subsystem management window. The work around is to use the Logical Drive pull-down menu to select the logical drive options. 10. The IBM FAStT 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 FAStT 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. 11. 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 reenable 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. 12. 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. 13. If the IBM FAStT Storage Server is connected to a SAN with many other IBM FAStT Storage Servers, there may be ghost LUNs displayed in the Windows NT4 Disk Administrator. Use switch zoning to either limit the number of storage servers that the Host Bus Adapter(HBAs) in the NT4 host server can log into (single or dual HBAs per host server configuration) or create two separate paths from the NT4 host server to the storage server controllers A and B (dual HBAs per host server configuration.) 14. When creating a Remote Mirror of a base logical drive, the following restriction applies. First, you have created a flashcopy of a base logical drive and the base logical drive is receiving I/O. Second, you decide to create a remote mirror relationship, using the base logical drive as the primary logical drive in the remote mirrored pair. As you create the remote mirror relationship, the flashcopy logical drive is 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, this will not happen. 15. 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 shut down. First, in the server that has the primary logical drive, run the SMFlashCopyAssist program in the FAStT Storage Manager 8.3 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 by running a chkdsk on the disk for example. 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. 16. 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 rescaned 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 occurred 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. ======================================================================= 1.3 Enhancements ----------------- N/A ======================================================================= 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 8.3 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 type 1742 (models 90X, 90U) and 1722 storage subsystems that have at least firmware version 05.3x.xx.xx. The only IBM FAStT Storage Manager 8.3 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 Storage Manager version 8.3 for Windows Server 2003 only. This software package will not install in Windows 2000 and NT servers. ======================================================================= 2.1 Key Features added to IBM FAStT Storage Manager 8.3 with controller firmware level 05.3x.xx.xx. --------------------------------------------------------------------- See the IBM FAStT Storage Manager version 8.3 Installation and Support Guide for Windows NT, Windows 2000 and Windows Server 2003. ======================================================================= 2.2 Client Code levels at time of release are as follows --------------------------------------------------------- 1. IBM FAStT Storage Manager Client version: 08.33.35.02 2. IBM FAStT Storage Manager RDAC version: 08.30.35.02 3. IBM FAStT Storage Manager Agent version: 08.30.35.01 4. IBM FAStT Storage Manager Utilities version: 08.30.35.01 5. Microsoft Virtual Machine: msjavx86_3805 Refer to the http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/disk 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 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 the Host_Adapter directory on this installation CD. 2. Install the new Storage Manager version 8.3 software. If there are previous version of the IBM FAStT Storage Manager version installed in the system, uninstall it before installing the new version of the storage manager software. Refer to the IBM FAStT Storage Manager version 8.3 for Windows NT, Windows 2000 and Windows Server 2003 Installation and Support Guide for detailed installed and uninstalled instructions. ======================================================================= 3.2 Refer to the Host_Adapter directory on the installation CD for the applicable drivers. Refer to the http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/disk 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 FAStT200, FAStT500, and FAStT700 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 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 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. Note: The host type setting for the Windows Server hosts is the same as Windows 2000. Select either Windows 2000 Clustered or Window 2000 Non-Clustered host type if the correct host types of Windows 2000/Server 2003 Clustered or Windows 2000/Server 2003 Non-Clustered are not displayed in the host type pull down list. When upgrading from previous versions of IBM FAStT Storage Manager to version 8.3x. 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.1.5.62. 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.3x. 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://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/disk 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 problem applying the update go to the following Help Center World Telephone Numbers URL: http://www.ibm.com/planetwide ======================================================================= 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.