File Name: Readme_fw207A.txt This README file contains the latest information about the IBM FAStT Storage Manager version 7.10 storage controller firmware for IBM machine types 3526, 3542, and 3552. Refer to the IBM 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 (See Section 6.1 below). Last Update: 09/11/01 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 7.10 storage controller firmware version 04.01.02.07 and updated NVSRAM files for IBM machine types 3526, 3542, and 3552. (see section 2.2 below for NVSRAM changes). The IBM FAStT Storage Manager version 7.10 Installation and Support Guide is available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. (see Section 6.1 below). 1.2 Limitations: 1. Copyback problem. A condition exists under 7.01, 7.02, and 7.10 code levels that may cause a logical drive to become unmapped in Storage Partitioning, resulting in the Operating system being unable to access the Logical drive. The problem may manifest itself in one of the following ways: a. Improper implementation of ECA051 b. Failure of the first drive in any array, takeover by the Hot Spare drive, then copyback to the new drive, once the failed drive has been replaced. If a reset of the controllers is performed, the logical drive may become missing under the array in the Storage Manager 7 subsystem management window. Once either of the above conditions has occurred and the controllers have been reset, all Logical drives in the affected array will become unmapped. It may be possible to remap the volume back into Storage Partitioning. To do this, right click on the Host group that the affected Logical drive belonged to and choose "Define New Mapping". If this option is grayed out, please contact your local HelpCenter for assistance in recovering the volume. This problem has been identified and will be corrected in a future release of 7.10 Firmware targeted for the third quarter of this year. Customers wishing to avoid this problem will be required to upgrade to the new level of Firmware as there will be no fix available for the 7.01 and 7.02 releases. 2. Performance issue under 7.10 code. A performance issue has been identified affecting logical drives with a segment size of 64K or greater when large sequential writes are staged to the drives. Typically, large sequential writes are performed by large database applications such as Oracle and Microsoft Exchange. During the large sequential write operation only, performance will be decreased. Normal read and write operations will not be affected. This problem has been isolated to 7.10 code only and will be fixed in a future maintenance release of the firmware, targeted for the third quarter of this year. 3. Upgrading FAStT500 with 512MB Cache. If you are upgrading from IBM FAStT Storage Manager Version 7.02 ( firmware level 04.00.02 or 04.00.03) to IBM FAStT Storage Manager Version 7.10 (firmware level 04.01.02) on a FAStT500 (machine type 3552) with 512MB of cache, you will need to stop I/O and reboot the controller before upgrading firmware followed by NVSRAM. To determine Storage Controller cache level, perform the following; a. On a storage management station start the client software and select a storage subsystem. b. Select Tools -> Manage Device to open the Subsystem Management Window. c. Highlight the Storage Subsystem that you are upgrading and then select Storage Subsystem -> Profile. It may take a little time for it to create the Storage Subsystem profile. d. Under the Controllers heading is an entry that displays information something 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. 4. Upgrading to 16 storage partitions on machine type 3542. Upgrading to Storage Manager 7.10 firmware version 04.01.02 and NVSRAM will enable 16 storage partitions on machine type 3542. However, the Storage Manager Client will indicate that the storage controller premium features are Out of Compliance. To clear this message, contact IBM Support and provide your Feature Enable Identifier. You can obtain your Feature Enable Identifier from the Subsystem Management window of Storage Manager 7. Use the following procedure to obtain your Feature Enabler Identifier: Click storage subsystem -> premium features -> list Contact IBM Support to obtain a feature key file for enabling the 16 partition premium feature. Refer to the Storage Manager 7 online help for more information. 5. 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. 6. Auto LUN/Array Transfer is not supported. 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 redistributing arrays. 7. 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 7 application in a higher display mode. 8. Error message Service Error 100 after installing Storage Manager 7.10 host-agent software. Causes of this include the following: a. The host-agent software does not find any controllers at firmware version 4.x. b. Controllers at firmware version 4.x have the access volume disabled with NVSRAM configuration settings. c. NVSRAM on a controller in a storage subsystem that you are attempting to manage has the access volume logical unit number (LUN) set to a number that is already in use by another logical drive. d. NVSRAM on controllers in a storage subsystem that you are attempting to manage contains an access volume LUN that is not supported by operating systems and installed patches (for example, the access volume is configured as LUN 31, but the operating system and service packs only support 8 LUNs). 9. Redundancy check on machine type 3542 can take up to 10 times longer than on other controller platforms. A redundancy check (parity scan) uses the VERIFY operation which is not implemented in hardware on this platform. Parity checking will take a longer on 3542 based arrays. 1.3 Enhancements: N/A 1.4 Prerequisites: N/A 1.5 Dependencies: IBM FAStT Storage Manager version 7.10 requires IBM machine type 3526, 3542,or 3552 storage controllers that have at least firmware version 04.x. If the user is installing IBM FAStT Storage Manager version 7.10 onto a host with 3526 controllers that are at firmware 3.x, refer to the IBM FAStT Storage Manager 7 Migrate package located on the IBM web site at http://www.ibm.com/pc/support for instructions on upgrading the controllers to firmware 4.x. This process requires a Windows NT 4.0 Client with a direct network connection. 2.0 Change History ----------------------------- 2.1 Problems fixed between IBM FAStT Storage Manager version 7.10 controller firmware 04.01.02.03 to 04.01.02.07. -53787 MFT: Controller goes into debug when failing a drive with SM7client. -53387: Client will not allow a downgrade from Mojave1M to Mojave1 -53388: We have a customer incidence where a LUN went missing after a controller failure.  -53490: C164710 : Linux is seeing a UTM that should not be seen -49837: Make ECC error handling on bridge controllers consistent with SHV -51633: Created a 30 drive Raid 1. Offlined the volume. Cannot bring back online. -51827: 3542 alarm does not clear immediately after pressing the alarm reset button -52306: MFT:  After doing a reset config with a GHS in the system, the ghs is still there  -52332: Startup fails with LED 41 when NVSRAM not initialized -52400: Memory fault after cold pull of GHS -52437: Reconfiguration after drive tray recovery mangles device definitions -52466 MFT:  A Drive that is part of a volume goes unassign after reviving it from being failed -52508: Need to change bcmLib.c to properly use VKI/VNI macros -52537: Write cache and CM disabled after FW upgrade via write-buffer/mode page -52624: Mel log not retreivable after syswipe or new config.  Need access to MEL logs after syswipe or new config. -52682: GHS copyback stuck -52691: Modify dstReceiveMessage to support the ICM_UNSUPPORTED_MESSAGE return type.dst -52751 MFT: drive that i swapped became offline during  warm  pull -52774 MFT:  An IAF to a volume still continues after a syswipe completes, cause drives to be failed -52797: Mode Sense to page 0x3a is showing 1 ghs on one controller and 2 on the other controller -52893: If AWS is enabled, 3526 will crash during SOD. -52985: Controller is dropping the PLOGI if it comes in too quickly. -53069: 3526 receiving "DST : Invalid Queue Tag.."  messages during 1024 or 2048 volume creation script execution -53077: Add page D0 to the list of Supported Pages VPD page -53137 MFT: Memory error doing reconfigure of the segment size of the volume 2.2 NVSRAM changes: 1. From NV3526R710NT003 to NV3526R710NT005. a. Linux RedHat 7.1 support. b. Force Unit Access (FUA) caching option enabled. 2. From NV3542R710NT007 to NV3526R710NT011 and from NV3542R710NT008 to NV3542R710NT012. a. Linux RedHat 7.1 support. b. Force Unit Access (FUA) caching option enabled. 3. From NV3552R710NT004 to NV3552R710NT008. a. Linux RedHat 7.1 support. b. Force Unit Access (FUA) caching option enabled. 2.3 Code levels for this release are as follows: 1. Firmware versions: a. For machine types 3526, 3542, and 3552: Package 04.01.02.07 b. For machine types 3526 and 3552: Bootware 04.01.02.00 c. For machine types 3526 and 3552: Appware 04.01.02.07 d. For machine type 3542: Snapware 04.01.02.07 2. NVSRAM versions: a. For machine type 3526: NV3526R710NT005 b. For machine type 3542, model -1RX or 1RU: NV3542R710NT011 c. For machine type 3542, model 2RX or 2RU: NV3542R710NT012 d. For machine type 3552: NV3552R710NT008 3.0 Installation and Setup Instructions -------------------------------------------------------- 3.1 Important: You must download firmware version 04.01.02 before you download NVSRAM. To download firmware version 04.01.02, 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 Helpful Hints 1. The IBM FAStT Storage Manager will prompt you for a password if an attempt is made to manage a storage subsystem where the FAStT RAID Controller Unit does not have access to any hard disk drives. This will occur even if no password has been setup. The automatic discovery will discover each storage subsystem as two separate storage subsystems. To prevent this from occurring, ensure that at least one FAStT EXP500 Expansion Unit with at least one drive is properly attached to the FAStT500 RAID Controller Unit in each storage subsystem that is being managed. Since the RAID controller unit should not be powered on until the expansion units are attached and powered on, this should be done by powering off the RAID controller unit, properly attaching all expansion units (with drives installed), to the RAID controller unit and powering them on, and then powering the RAID controller unit back on. At this point the storage subsystems can be re-discovered and managed using the IBM FAStT Storage Manager 7.10 software. 2. If you are unable to see the maximum number of drives during Automatic Configuration, you should be able to use Manual Configuration to select individual drives and select the maximum number of drives allowed. 4.0 Configuration Information ------------------------------------------- 4.1 Configuration Settings: 1. By default the IBM FAStT Storage Manager 7.10 firmware release 04.01.02 does not automatically map logical drives. 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. Refer to the IBM FAStT Storage Manager online help to learn more about creating storage partitions and changing host types. 2. 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. - 3526CTLdual.scr: Enables the detection and error reporting for missing or unresponsive controllers in a 3526 Dual RAID controller configuration. If either RAID controller is removed or not responding, it is detected and reported through the IBM FAStT Storage Manager software. The 3526 NVSRAM default is enabled to detect a missing or unresponsive alternate controller. - 3526CTLsingle.scr: This script disables the detection and error reporting of the missing alternate controller in a 3526 single RAID controller configuration. After executing this script, the IBM FAStT Storage Manager 7.10 software will not report the missing alternate RAID Controller. The machine type 3526 NVSRAM default is enabled to detect a missing alternate controller. - 3526EXPdualPS.scr: This script enables the detection and error reporting of a missing or unresponsive alternate power supply in an IBM Storage Expansion Unit configured with dual power supplies while attached to the 3526. If either Storage Expansion Unit power supply is removed or not responding, it is detected and reported through the IBM FAStT Storage Manager 7.10 software. Machine type 3526 NVSRAM default is enabled to detect a missing or unresponsive alternate power supply in an IBM Storage Expansion Unit. - 3526EXPsinglePS.scr: This script disables the detection and error reporting of a missing alternate power supply in an IBM Storage Expansion Unit configured with a single power supply and attached to the 3526. After executing this script, the IBM FAStT Storage Manager 7.10 software will not report the missing alternate power supply in an IBM Storage Expansion Unit. The 3526 NVSRAM default is enabled to detect a missing alternate power supply in an IBM Storage Expansion Unit. 4.2 Unsupported configurations The following lists configurations that are currently not being supported with IBM FAStT Storage Manager 7.10. 1. Fibre Channel loop environments with the IBM Fibre Channel Hub, machine type 3523, in conjunction with the IBM Fibre Channel Switch, machine types 2109-S16 or 2109-S8. In this configuration, the hub is connected between the switch and the IBM Fibre Channel RAID Controllers. 2. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 3542 and 3552. 5.0 Unattended Mode --------------------------------- N/A 6.0 WEB Sites and Support Phone Number ---------------------------------------------------------------- 6.1 IBM Support Web Site: http://www.ibm.com/pc/support 6.2 IBM eServer xSeries Marketing Web Site: http://www.ibm.com/pc/us/eserver/xseries/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 the e-business logo xSeries HelpCenter Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. 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.