This README file contains the latest information about the IBM TotalStorage™ FAStT Storage Server controller firmware version 06.10.06.00 for the FAStT600 Turbo, FAStT700, FAStT900 storage subsystems. Refer to the IBM TotalStorage™ Support Web Site or CD for the IBM FAStT Storage Manager version 9 (Intel or Unix Operating Systems) Installation and Support Guides 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: 08/26/2004 Products Supported: --------------------------------------------------------- | | Machine Type (M/T) | Model | |-----------|--------------------|------------------------| | FAStT 900 | 1742 | 90X , 90U | |-----------|--------------------|------------------------| | FAStT 700 | 1742 | 1RX, 1RU | |-----------|--------------------|------------------------| | FAStT 600 | 1722 | 60U (Turbo option), | | Turbo | | 60X (Turbo option) | --------------------------------------------------------- Note: The FAStT Storage Server controller firmware version 06.10.xx.xx with its associated NVSRAM file are not available for the following FAStT Storage servers - FAStT100 (M/T 1724-all models), FAStT200 (M/T 3542-all models), FAStT500 (M/T 3552-all models) and FAStT600 Base and Single Controller (M/T 1722 models 60U, 60X, 6LU, 6LX). Please contact your IBM service representative or IBM resellers for availability of additional FAStT storage server models support with controller firmware version 6.10.xx in the future. ======================================================================= 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 -------------- The IBM TotalStorage™ FAStT Storage Server controller firmware version 06.10.06.00 release includes the FAStT Storage Server controller firmware and NVSRAM files for upgrading the following IBM machine types - 1722 Turbo (models 60X and 60U), 1742 (all models). The IBM TotalStorage FAStT Storage Manager version 9 Installation and Support Guide for Intel-based Operating System Environments or the IBM TotalStorage FAStT Storage Manager version 9 Installation and Support Guide for AIX, HP-UX, Solaris, and Linux on Power are available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. In addition, IBM FAStT Copy Services premium features - FlashCopy, VolumeCopy and Enhanced Remote Mirroring - are options purchased separately. The Copy Services premium features require a minimum level of FAStT storage server controller firmware installed. ------------------------------------------------------------------ | Premium Feature | Required controller firmware version | |--------------------------|---------------------------------------| | FlashCopy | 05.00.04.xx or higher | |--------------------------|---------------------------------------| | VolumeCopy | 05.40.xx.xx or higher | |--------------------------|---------------------------------------| | Enhanced Remote Mirror | 06.10.0x.xx or higher | ------------------------------------------------------------------ The FAStT storage partitioning premium feature is standard on all IBM FAStT storage subsystems with the exception of the IBM FAStT600 (machine type 1722 with Standard option) storage subsystem. Please contact IBM Marketing representatives or IBM resellers if you want to purchase the IBM FAStT storage partitioning premium feature option for it. The Turbo option of the IBM FAStT600 is shipped with the IBM FAStT storage partitioning premium feature enabled (8 partitions). The FAStT Storage Controller firmware 06.10.xx.xx for this release is available for IBM machine types 1722-60X/60U (with Turbo option), 1742-1RX/1RU and 1742-90X/90U only. The FAStT Storage Controller firmware 06.10.xx.xx for this release is not available for IBM machine types 3542, 3552, 1722-60X/60U (with Standard option) or 1722-6LX/6LU (single controller). However, the IBM FAStT Storage Manager 9.10 host software for this release will manage all FAStT storage server with the controller firmware 04.01.xx.xx or newer. But, any new features and updates that are introduced in this FAStT Storage Manager version 9.10 will not be available for any FAStT storage server controllers without the controller firmware version 06.10.xx.xx installed. Refer to the IBM Support Web Site for the latest Firmware and NVSRAM files for the IBM FAStT Storage Subsystems. http://www.ibm.com/storage/support/fastt ======================================================================= 1.1 Limitations --------------------- 1. If you are upgrading controller firmware in IBM FAStT500 storage controller (M/T 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. 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 FAStT 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. In addition, 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 change to window resize pointer, left click and hold to grip the window edge to resize it. 5. 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. 6. 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. 7. 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. 8. 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. 9. When alternately switching back and forth the roles of the logical drives in a remote mirrored relationship, Windows NT4, Windows 2000 and Server 2003 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 SMrepassist 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. 10. 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. 11. 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. 12. 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. 13. 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. 14. 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. 15. 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. 16. 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. 17. 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. 18. 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. 19. 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 20. 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. 21. 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. 22. 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. 22. Veritas DMP is not supported at this time in Windows operating environment. Please contact IBM representatives or resellers for the availability of support. 24. 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. 25. 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. 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. 27. After you replace a controller with a new controller in the single controller models of FAStT storage servers, the premium features become unauthorized and are out of compliance. Any premium features not supported by the firmware of the new controller are unavailable. The work-around is to upgrade the firmware in the new controller to the same level as the removed controller and re-enable the premium features using the key files that you were provided when the premium feature was originally enabled. 28. When you migrating drive Customer Replaceable Units (CRUs) from multiple FAStT storage servers into a single destination FAStT storage servers, all of the drive CRUs from the same FAStT storage server should be moved as a ‘set’ into the new destination FAStT storage server. Before moving the next ‘set’ of drive CRUs, ensure that all of the drive CRUs for a single ‘set’ have been moved to the destination FAStT storage server. If drive CRUs are not moved as a ‘set’ to the destination FAStT storage servers, the newly relocated array may not appear in the Subsystem Management window. 29. Enclosure IDs may be listed incorrectly in the Subsystem Management window, even if the Enclosure ID switch settings appear to be correct. This is because of the physical design and movement of the Enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which will return an incorrect Enclosure ID (this value is 0 in most cases) to the storage management software. When setting the Enclosure ID, ensure that the switch has actuated completely and has settled where the value is clearly visible in the viewing window. 30. To download controller firmware, you must select the drive where the firmware is located. If the drive you select does not respond, the File Selection dialog box will revert to the A: drive and display an error message that drive A: is not ready if there are no media in drive A:. 31. 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. Furthermore, if the EXP100 ESM firmware version is 953x or earlier, no IOs are allowed during the duration that the EXP100 ESMs are being updated with new firmware, including clustering reservation checking IOs. 32. The FAStT storage server when configured with the FAStT EXP100 SATA Drive Expansion Unit is currently reporting a higher frequency of informational events such as Destination Driver Events (DDEs) and FibreChannel link up/down events ... in the FAStT Controller event log compared to the FAStT storage server configured with Fibre Channel drives. Slower response times of SATA disk drives compared to Fibre Channel disk drives cause higher I/O retries from the FAStT storage server controllers, resulting in a greater number of informational events logged. In addition, the number of information events reported in the FAStT storage server event log will also grow in proportion to the increase in I/Os to the Logical Drives. In all cases, the FAStT storage server controller will always successfully service the timeout I/O on the subsequent retries. 33. 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. 34. Do not perform other storage management tasks, such as creating or deleting logical drives, reconstructing arrays, and so on, while downloading the FAStT storage server controller firmware and FAStT EXP ESM firmware. It is recommended that you close all storage management sessions (other than the session that you use to upgrade the firmware) to the FAStT storage server that you plan to update. 35. Inter-operability with tape devices is supported on separate HBA and switch zones. New limitations with version 9.10.xx.02 release 36. The FAStT Copy Service RVM is not supported at this time for FAStT600 Base and Single Controller storage servers models. 37. In the Storage Manager version 9 client Subsystem Management window, the preferred owner of a defined logical drive can not be changed if the logical drive is managed by the preferred owner/controller. There is no work-around. If the drive is currently managed by a non-preferred owner/controller, one can change the currently managed non-preferred owner/controller into currently managed preferred owner/controller. 38. Concurrent firmware download (downloading firmware/NVSRAM to the FAStT storage server controllers with IOs to the host servers) is not supported when upgrading the controller firmware from a 05.xx.xx.xx version to a 06.10.xx.xx version. ALL IOs must be stopped during the version 06.10.xx.xx controller firmware upgrade from a pre-06.10.xx.xx version. 39. Do not pull or inserting drives during the drive firmware download. In addition, ALL IOs must also be stopped during the drive firmware download. Otherwise, drives may be shown as missing, unavailable or failed. 40. Controller diagnostics will not run in a FAStT storage server with single controller. 41. When instructing to remove and reinsert or to replace a hard drive, wait at least 70 seconds before inserting either the removed existing drive or the new drive into the drive slot. Similarly, wait at least 70 seconds before reinserting either the removed existing ESM module or the new ESM module into the empty ESM slot in the EXP drive expansion enclosure. There is no work-around. 42. Staged firmware and NVSRAM download function is not available on the FAStT700 (machine type 1742) models with firmware 06.1x.00.00 in conjunction with IBM Storage Manager 09.1x.xx.xx." ======================================================================= 1.2 Enhancements ----------------- IMPORTANT: New features that are introduced with the FAStT Storage Manager version 9.1 host software will not be available for any FAStT storage server controllers without the controller firmware version 06.10.xx.xx installed. The FAStT storage server controller firmware version 6.10.xx.xx is available for the following FAStT storage server only - FAStT600 Turbo option, FAStT700 and FAStT900. Please contact your IBM service representative or IBM resellers for availability of additional FAStT storage server models support with controller firmware version 6.10.xx in the future. A summary list of the new features that are introduced with the FAStT Storage Manager version 9.1 host software for Microsoft Windows 2000 and Server 2003 operating systems in conjunction with the FAStT storage server controller firmware version 06.10.xx.xx is as followed: - Enhance Remote Mirroring support. Besides Metro Mirroring, IBM FAStT Storage Manager version 9.1 also supports Global Copy and Global Mirroring Remote Mirror options. Please refer the IBM FAStT Storage Manager Version 9 Copy Services User's Guide for more information. - Parallel hard drive firmware download support. Up to four different drive firmware packages can be downloaded to multiple drives of four different drive types simultaneously. Note: Drive firmware download is an offline management event. You must schedule downtime for the download because no IOs to the storage server are allowed during the drive firmware download process. - Staged controller firmware download support. The controller firmware and NVSRAM can be downloaded to the FAStT600 Turbo and FAStT900 storage server Flash area for later activation. Note: FAStT700 storage server does not support this functionality. - Full command-line SMcli support. - Support for both FC and SATA hard-drive technology EXP enclosures as long as the FC (EXP700, EXP500) and SATA (EXP100) EXP drive expansion enclosures are installed on different FAStT storage servers. - Improve FAStT storage manager client Subsystem Management GUI interface - Serviceability enhancements: This includes one-click collection of support data, drive diagnostic data, drive channel state management, controller ‘service mode’, reporting of none functional controller and ability to save host topology information. - Improve media error handling for better reporting of unreadable sectors in the FAStT storage server event log and persistent reporting of unreadable sectors. Please refer to the New Features section of the IBM FAStT Storage Manager version 9 Installation and Support Guide for Intel-based Operating System Environments for additional information about the the IBM FAStT Storage Manager version 9 enhancements. ======================================================================= 1.3 Prerequisites ------------------ N/A ======================================================================= 1.4 Dependencies ----------------- IMPORTANT: FASTT STORAGE SERVER CONTROLLER FIRMWARE VERSION 06.10.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X. TO DETERMINE THE FIRMWARE LEVEL OF AN EXP100 ESM, IDENTIFY THE PRODUCT LABEL LOCATED AT THE REAR OF THE EXP100 ENCLOSURE. ONLY LABELS ON WHICH THE FIELD REPLACEABLE UNIT (FRU) PART NUMBER READS 25R0156 POSITIVELY INDICATE THAT AN ESM MODULE IS RUNNING FIRMWARE VERSION 955X OR HIGHER. IF THERE IS NO LABEL OR THE PART NUMBER ON THE LABEL DOES NOT READ 25R0156, THE ESM MAY STILL HAVE THE FIRMWARE VERSION 955X OR HIGHER IF IT HAD BEEN PREVIOULSY UPGRADED. IF NECESSARY, CONTACT YOUR IBM REPRESENTATIVE, SUPPORT, OR RESELLER FOR ASSISTANCE. IBM FAStT Storage Manager host software version 09.1x.xx.xx provides full management support for IBM machine types 3552 and 3542 storage controllers that have at least firmware version 04.01.xx.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 09.1x.xx.xx supported management function on controllers with firmware version 04.xx.xx.xx to 04.xx.02.xx is controller firmware and NVSRAM download. ======================================================================= 2.0 Change History ----------------------------- ====================================================================== 2.1 Version History ----------------------------- This is the latest release of IBM FAStT TotalStorage™ controller firmware/ NVSRAM for the following FAStT storage server models - FAStT600 Turbo, FAStT700 and FAStT900. Version 06.10.06.00, 8/31/2004 for the FAStT600 Turbo, FAStT700, and FAStT900 This is a major controller firmware maintenance release. The new feature list is as follows: - Enhance Remote Mirroring support. Besides Metro Mirroring, IBM FAStT Storage Manager version 9 also supports Global Copy and Global Mirroring Remote Miror options. - Parallel hard drive firmware download. - Staged controller firmware download. - Full command-line SMcli support. - Improve FAStT storage manager client Subsystem Management GUI - Adding additional diagnostic features - Drive Channel status, hard drive sector failure list. Version 05.40.15.00, 7/29/2004 for the FAStT600 Turbo, FAStT700, and FAStT900. This is the controller firmware maintenance release. The fix list for FAStT700 and FAStT90 models is as follows: 76687 Memory fault while running sysReboot with Cluster 74957 Error encountered after Heavy Mirror Xor Traffic Phase, and RV 75268 Ancient I/0 aborted while running switch port fail (volume copy, snapshot 75682 Controller returns reservation conflict while running switch port fail test. 78203 (CL #78004) 242386 - RAID1 remained degraded after a drive pull/replac 78339 (CL #69661) Assigned drives of RAID1 VG came back as "offline" 78347 (CL #77338) Fatal vproc after replacing drive 78354 (CL #76490) C238953 - Host IO Read Errors in multiple configurations 78606 (CL #78357) disk array became unmanageable in benchmark 74117 (CL #70794) One volume never finishes reconstruction when co 74700 (CL #74488) (CL #74483) Continuous resets on Tachyon chip - 5884 contr 75324 (CL #74431) C224711 Timeout occurs on the client during a request to 75598 Panic: Assertion failed : registration = 0, file presReservableVolume. 76017 (CL #75805) Incomplete transfer of host information during v 76104 (CL #75661) Controller reboot due to ancient IO during sysRe 76109 (CL #75755) CMVC: 237648 Configuration loss of RAID 0 volume (SATA) 76181 (CL #75746) Ancient I/O (mode select I/O) during 2 second po 76269 (CL #75283) C236739 I/O error during controller offline testing with S 76727 (CL #75055) DCE operation on RAID 1 volume invalidates tray loss prote 76951 (CL #76881) IAF process hangs if multiple IAFs in progess on same volu 76965 (CL #76936) Unable to re-initiate volume group initialization after th 77501 (CL #77464) Controllers did not agree on the state of a spindown drive 77510 (CL #71143) Defragmentation fails 77555 (CL #75895) Request for ctlr resets to be blocked by ctlr du 77632 (CL #76702) Volume state not consistent between the controllers after 78048 (CL #74681) Mapping exceeds 32-lun limit for default host ty The fix list for FAStT600 Turbo models is as follows: 78203 (CL #78004) 242386 - RAID1 remained degraded after a drive pull/replac 78339 (CL #69661) Assigned drives of RAID1 VG came back as "offline" 78347 (CL #77338) Fatal vproc after replacing drive 78354 (CL #76490) C238953 - Host IO Read Errors in multiple configurations 78606 (CL #78357) disk array became unmanageable in benchmark 74117 (CL #70794) One volume never finishes reconstruction when co 74700 (CL #74488) (CL #74483) Continuous resets on Tachyon chip - 5884 contr 75324 (CL #74431) C224711 Timeout occurs on the client during a request to 76017 (CL #75805) Incomplete transfer of host information during v 76104 (CL #75661) Controller reboot due to ancient IO during sysRe 76109 (CL #75755) CMVC: 237648 Configuration loss of RAID 0 volume (SATA) 76181 (CL #75746) Ancient I/O (mode select I/O) during 2 second po 76251 (CL #76148) Controller assertion when validateCmdInfo routine calls cf 76269 (CL #75283) C236739 I/O error during controller offline testing with S 76727 (CL #75055) DCE operation on RAID 1 volume invalidates tray loss prote 76951 (CL #76881) IAF process hangs if multiple IAFs in progess on same volu 76965 (CL #76936) Unable to re-initiate volume group initialization after th 77501 (CL #77464) Controllers did not agree on the state of a spindown drive 77510 (CL #71143) Defragmentation fails 77537 (CL #75629) MEMORY FAULT in "symPrepareAltControllerInfo" 77555 (CL #75895) Request for ctlr resets to be blocked by ctlr du 77632 (CL #76702) Volume state not consistent between the controllers after 78048 (CL #74681) Mapping exceeds 32-lun limit for default host ty Version 05.40.11.0x, 4/31/2004 for the FAStT600 Turbo, FAStT700, and FAStT900. Fixed a problem with cache mirroring that caused the controller to disable the cache. The result was severe performance degradation. For FAStT700 and FAStT900, the controller firmware version was 05.40.11.03. For the FAStT600 Turbo, the new controller fimware version was 05.40.11.04. Version 05.40.11.01, 4/09/2004 for the FAStT600 Turbo, FAStT700, and FAStT900. This is the controller firmware and NVSRAM maintenance release. The fix list for FAStT700 and FAStT90 models is as follows: 75567 (CL #75479) Memory leak beginning in 5.40.xx.xx. 69629 Downloading controller firmware with offline volumes causes unfinished download pr 69872 (CL #69467) TD_PT1086 RLS baseline date after new device insertion is incorrect. 70891 (CL #70586) TD_PT1277 Drive size reported incorrectly for a closed drive 71206 tray number reported incorrectly during discovery 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 71782 (RW #68268) (CL #67670) Can't create volume if drive sizes are similar 72339 CMVC-hlpct_42401 Error importing a 7.3 Gig FlashCopy LUN 72676 (CL #70100) SMclient GUI reports array needs attention, but guru reports 72712 (CL #72672) TD_PT1461 Ancient I/O during sysReboots 72768 (CL #72449) controllers repeatedly panic during M1 -> S3 FW upgrade 69052 Drives not assigned to proper loop on 2882 69204 (CL #68807) Profile not reporting correct unconfigured capacity on volume group Modify the NVSRAM file to disable Cache Sync in the W2K het host region. The fix list for FAStT600 Turbo models is as follows: 75567 (CL #75479) Memory leak beginning in 5.40.xx.xx. 69629 Downloading controller firmware with offline volumes causes unfinished download pr 69872 (CL #69467) TD_PT1086 RLS baseline date after new device insertion is incorrect. 70105 (CL #70048) TD_PT1195 Diagnostic path to controller report down falsely 70891 (CL #70586) TD_PT1277 Drive size reported incorrectly for a closed drive 71206 tray number reported incorrectly during discovery 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 71782 (RW #68268) (CL #67670) Can't create volume if drive sizes are similar 72339 CMVC-hlpct_42401 Error importing a 7.3 Gig FlashCopy LUN 72676 (CL #70100) SMclient GUI reports array needs attention, but guru reports 72712 (CL #72672) TD_PT1461 Ancient I/O during sysReboots 72768 (CL #72449) controllers repeatedly panic during M1 -> S3 FW upgrade 69052 Drives not assigned to proper loop on 2882 69204 (CL #68807) Profile not reporting correct unconfigured capacity on volume group Modify the NVSRAM file to disable Cache Sync in the W2K het host region. Version 05.40.06.01, 12/19/2004 for the FAStT700 and FAStT900. Version 05.40.07.01, 12/19/2004 for the FAStT600 Turbo. First Maintenance Release Version 05.40.03.05, 9/21/2004 for the FAStT600 Turbo, FAStT700, and FAStT900. This is the initial release of the FAStT storage server controller firmware for the 05.40.xx.xx code thread. A list of new features are as follows: - Support for IBM TotalStorage FAStT600 Turbo - Support for VolumeCopy copy service premium feature - 256 logical drives per storage mapping partition - Persistent reservations - User control of network parameters. The user can now change the controller IP addresses via the Subsystem Management window interface. - Support for larger than 2TB arrays. The maximum logical drive size is still 2TB. - Support for the creation of logical drives with a segment size of 512K using the script engines or SMcli ======================================================================= 2.4 Code levels at time of release are as follows ------------------------------------------------- 1. Storage Controller Firmware versions: a. FAStT 900: FW_06100600_06100100 b. FAStT 700: FW_06100600_06100100 c. FAStT 600 Turbo: SNAP_06100600 2. Storage Controller NVSRAM versions: a. FAStT 900: N1742F900R910V02 b. FAStT 700: N1742F700R910V02 d. FAStT 600 Turbo: N1722F600R910V03 Refer to the following IBM TotalStorage™ Disk Storage Systems Technical Support web site for the latest released code levels. http://www.ibm.com/storage/support/fastt ======================================================================= 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 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 FAStT700 storage subsystems (machine type 1742 - models 1RU and 1RX): 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. When making serial connections to the FAStT storage controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the FAStT storage server serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 4. Fabric topology zoning requirement. To avoid possible problem at the host level, it is best practice that all Fibre Channel (FC) Switches must be zoned such that a single FC host bus adapter can only access one controller per storage array. In addition, this zoning requirement also ensures the maximum number of host connections can be seen and log into the controller FC host port. This is because if a FC HBA port is seen by both controller A and B host ports, it will be counted as two host connections to the storage subsystem - one for controller A port and one for controller B port. Note: The 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. ======================================================================= 4.0 Configuration Information ----------------------------- 4.1 Configuration Settings -------------------------- 1. By default the IBM FAStT Storage Manager 9.10 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 FAStT 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 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 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. - EnableAVT_W2K_S2003_noncluster.scr: The script will enable automatic logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003 non- cluster heterogenous host region. The default setting is to disable AVT for this heterogenous host region. This setting is one of the requirements for setting up the remote boot or SAN-boot. Do not use this script unless it is specifically mentioned in the applicable instructions. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT enabled) - DisableAVT_W2K_S2003_noncluster.scr: The script will disable the automatic logical drive transfer (AVT) for the Windows 2000/Server 2003 non-cluster heterogenous host region. This script will reset the Windows 2000/Server 2003 non-cluster AVT setting to the default. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT disabled) - EnableAVT_Linux.scr: The script will enable automatic logical drive transfer (AVT) for the Linux heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Linux.scr: The script will disable the automatic logical drive transfer (AVT) for the Linux heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. 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 FAStT Storage Manager 9.10. 1. The intermixing of FAStT EXP100 (SATA) and EXP 700 (FC) drive expansion enclosures in the same FAStT storage server is not supported. In addition, the FAStT100 (machine type 1724) can not be connected to EXP700 (FC) drive expansion enclosure. 2. 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. 3. 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 problem applying the update go to the following HelpCenter 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 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.