File Name: Readme_fw225.txt This README file contains the latest information about the IBM FAStT Storage Manager version 7.10 storage controller firmware for IBM machine type 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: 11/20/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.25 and updated NVSRAM files for IBM machine type 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. 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. 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. 3. 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. 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 7 application in a higher display mode. 5. 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). 1.3 Enhancements: N/A 1.4 Prerequisites: N/A 1.5 Dependencies: IBM FAStT Storage Manager version 7.10 requires IBM machine type 3552 storage controllers to have at least firmware version 04.xx.xx.xx. 2.0 Change History ----------------------------- 2.1 Problems fixed between IBM FAStT Storage Manager version 7.10 controller firmware 04.01.02.07 to 04.01.02.25. -55231 (CL #51092) Hung drive bus or bad drive causes excessive delays in SOD -55561 (CL #55338) Memory fault in liteDstControl while implementing a volume migration. -56656 Controller memory bug with 128 RAID-0 luns -56670 Controller(3542) reboots when shell command mon is run as a task -56774 (CL #44393) Need a guaranteed way of logging (persistant) RPA Parity Err -57082 removed/failed drive + rst ctl causes Het-Host to be disabl ccm_ -57176 AIX host lost access to a volume after a controller reboot. -52782 IO timeout on 3526 running spc benchmark -53994 OEM customer seeing RPA battery failures in MEL after upgrading to SM7.10. -55747 Memory Fault occurs when copyback drive is replaced after power cycle -56789 (RW #56669) (CL #54102) Temporary Loss of Communication With Controller During Scr -56544 LUN fails to reconstruct after insertion of drive. -56086 RATOV timer does not clear I/Os aborted by the host. -56310 Volumes not quiescing during cache reconfig. -56535 (CL #55074) iconMgrFlush causes memory fault -56667 Mode select does not return status if error occurs on cache purge call -56668 (CL #53665) Mode select to Page2C to transfer all the volumes including the UTM lu -56121 Out of Memory error -55397 (CL #54480) MFT: A panic occurred after doing twice reset configuration. -55543 (CL #55531) Potential Data Corruption due to mirroring incorrect data -55663 (CL #55228) Multiple volumes have same name and lun number after using script engi -55773 (CL #55450) C169843 : Single drive fails after pulling a Fibre cable (loss of path) -55823 2-drive RAID-1 multiple failures result in corrupted volume ref -55875 (CL #54195) Problems with Simplicity Fieldtools -55890 (CL #55115) Showing incorrect free capacity after starting DRM -55965 (CL #55944) Piece size corrupted by illegal DSS operation -56102 GHS drive does not spare after cold replace for pulled drive -56217 (CL #56183) Pulling, then replacing optimal drive from a configured LUN tgen (2) tg -55448 SOD "DevNum" issue ccm_ -55639 (CL #54138) SM7.10 MEL Logs marks data/parity errors as informational -55774 (CL #55450) C169843 : Single drive fails after pulling a Fibre cable (loss of path) -55450 C169843 : Single drive fails after pulling a Fibre cable (loss of path) -52085 GHS is failed after pulling a drive from a volume that is still being formated -53591 FW problem prevents GUI from updating until IAF completes -53757 Config Module Date is incorrect. -53763 Copyback didn't resume after the drive was replaced -53795 Symbol package downloads take too long. -53823 The ACS never take place on controller A after released it from reset -53841 We received a memory fault while downgrading from build 36 to 34. -53855 Seek errors during Copyback causes continuous retries. (3542) -53920 DSS continues to restart from 0% over and over, while there is a another volume is performing data scrubing -53964 Storage Volume Reference Change during I/Os and sysReboot. -54246 SSM doesn't retry drive open failures -54283 Testware terminates and shows warnings -54366 Controller never reaches sodMain after the power cycle. -54376 Memory fault after swapping in two ESMs with conflict -54445 Drive Channel #1 (Remote Loop) - Tachlite tests #4 and #6 are skipped rather than failing in Extended Diagnostics -54451 Trace code needed for SSM to monitor AENs, MEL events, and internal statuses (particularly RPA status) -54458 Two default LUNs created after a foreign controller swap. -54463 Need to add some diagnostic hooks into SSM to track events -54493 Operation fault after drive tray powered on -54672 Data corruption during I/O, controller failover and drive failures stress -54685 Mojave-1m using SYMft and script editor unable to create 117 vols w/perf_cntr=A -54784 fc 90 not clearing exchange count total on 4766 -54934 Unassigned drive is transferring storage partitions with it when migrating -55107 Unable to recover failed LUNS back to their perfered path. -55286 Symbol's volume StateStatus translation table is incomplete -55289 Copyback process incorrectly sets volume state to Optimal -55335 SM7.10 reconstruction of 2+1 RAID3 (180GB) volume never completes (degraded) -54453 Watchdog timeouts during controller failover stress. -54488 Cache isn't flushing at all. -54542 SM7.10 fails SOD w/Divide Error, w/parity scan in progress, numDriveGr -52687 IR 343 Preferred path changes when redistribute volumes executed -54319 (CL #53627) 4884 in reboot loop building luns with 484k stripe -54371 (CL #53558) obtainXCB does not look at queue heads correctly -54424 (CL #49262) Drive-side timeout value (in NVSRAM) is ignored by HDD (3552/3542 only) -53513 (CL #53481) Controllers unresponsive after all volume groups were marked offline. -53564 C164741 : Logical Drive became invisible after Rebuild/Copyback -53569 Sympathetic drive failures take volume offline -53773 (CL #53685) IAF does not complete after change in ownership -53848 (CL #53835) When data scrubbing was enabled, copyback did not start after the fail -53893 (CL #53885) 4884 & Mojave 2 VKI_TIMEOUT: no more timers Issue from SM7.02. -53322 Loss of Volumes while running controller sysReboots -53597 (CL #53169) Pull/Replace drive returned wrong status -54094 (CL #53973) Performance degradation was detected with AVT in SM7.10. -58341 Data Corruption after Controllers go Active/Passive 2.2 NVSRAM changes: 1. 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 type 3552: Package 04.01.02.25 b. For machine type 3552: Bootware 04.01.02.02 c. For machine type 3552: Appware 04.01.02.25 2. NVSRAM versions: a. 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 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.