This README file contains the latest information about the IBM TotalStorage™ DS300 and DS400 Storage Server controller firmware version 6.04 Refer to the IBM TotalStorage™ Support Web Site or CD for the IBM ServeRAID™ Manager Installation and Support Guides for controller firmware 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: 7/15/2005 Products Supported: ----------------------------------------------------- | | Machine Type | Model | |-------------|--------------|------------------------| | DS300 | 1701 | 2RD ,2ES | |-------------|--------------|------------------------| | DS400 | 1700 | 2RD ,2ES | ----------------------------------------------------- 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 -------------- This IBM TotalStorage DS300 and DS400 release includes the IBM version 6.03 Storage Server Controller Firmware for upgrading the following IBM machine types - 1700-2RD,ES and 1701-2RD,ES. The IBM ServeRAID Manager version 7.24.x Installation and Support Guides are available on IBM's Support Web Site as a downloadable Portable Document Format (PDF file). Refer to the IBM Support Web Site for the latest Firmware files for the IBM DS300 & DS400 Storage Subsystems. http://www.ibm.com/servers/storage/support/disk/ ======================================================================= 1.1 Limitations --------------------- 1. Upgrading the single controller 1700/1701 models to this dual controller code is NOT supported. 2. The following functions are not supported in 1700/1701 (dual controller code): a) global hot-spare (only dedicated hot-spares are currently supported), b) RAID 50, c) Snapshot (greater then 4 base snaps). 3. The Management Station Service currently only runs on a Windows,IA32 bit platform. 4. The DS400 does not coexist on the same SAN, using the DS4000 HBA device driver for DS400, as the DS4000 (formally FAStT) Storage Subsystem. 5. The multipath DSM software for the DS4000 HBA FC2-133 must be installed, in conjunction with the corresponding DS4000 HBA device driver for DS400, in order to provide multipathing support. 6. The default password for the controller is passw0rd. 7. On the DS400, the loopback diagnostic function only works with port 0 on controller A. 8. On power up or storage subsystem reboot, one controller may not power up correctly. Telnet to the IP address of the controller that has powered up completely, at the prompt type the following: DS400[A]>administrator or admin then Enter. Administrator level password: type the administrator password then Enter. DS400[A]# controller peer enable then Enter This will reboot the controller that did not power up completely. If this procedure still does not work, reboot the entire enclosure. 9. If you receive an error message indicating that your Rhrdd service is being restarted, this could indicate a problem with the backchannel communication. To verify, establish a Telnet session to one of the controller management port IP addresses and issue the following command: device list. If you receive an RPC error message, please contact IBM support. 10. If you receive an error message indicating that your Stord service is being restarted, this could indicate a problem with loading the virtualization layer RAID device driver. To verify, establish a Telnet session to one of the controller management port IP addresses and issue the following command: device list. If you receive an error message or no devices are listed, please contact IBM support. 11. A Raid 10 array that is in a rebuild state may change to the synch state on a failover. This is OK. If the synchronization does not complete before the problem is fixed and a failback ensues, the array will go back to the rebuild state on the original owning controller. 12. Event log time stamp maybe off by one hour from the controller time due to daylight savings. 13. After a reboot, the data scrubbing rate will reset to the default state of High. 14. Sometimes the preferred owner of some LUNs may change after a reboot or a move. The preferred owner can be reset by doing a move of the LUN back to the other controller. 15. If the host system boots up prior to the storage subsystem completing its power up cycle, LUNs assigned to that host may not appear. Rescan for disks after the storage subsystem has powered up fully. 16. On occasion, when using ServeRAID Manager to create Arrays and/or Logical Drives, the creation may result in failure of all or part of the array or logical drive creation. Try creating the array again. 17. The maximum number of Basic arrays that can be created is 24. 18. In the CLI, if a command does not complete successfully, retry the command. 19. If your storage subsystem identifies arrays as being ALIEN, please contact IBM support to find out how to handle these arrays. 20. In the event a critical array fails over to the peer controller (or becomes critical while owned by the non-preferred controller), the array will not complete a rebuild until the array is manually moved back to its preferred controller. Critical arrays that are in the process of rebuilding will failover and continue to rebuild if the preferred controller goes down. 21. After a failover, a drive in an array could become unresponsive and disappear from the array, causing the array to become critical. On failback to the preferred controller the missing drive should return. There is no need to replace the drive. 22. If a drive is inserted into the enclosure from another DS300 or DS400 enclosure, that drive may contain metadata from the previous configuration. This can result in foreign or alien arrays being presented in the array list. These arrays must be destroyed before the drive can be used. 23. If a drive is removed, causing an array to go into a degraded or critical state, only replace the removed drive if a hot spare has not been assigned to that array. 24. After a reboot, some devices may show up as duplicate in the CLI. This can be resolved by performing an additional reboot. 25. It is possible for a dedicated hot-spare to go back to the RDY state after reboot. Recreate the hot-spare if this happens. 26. Logical drives mapped to multiple initiators that are installed in the same host system need to be mapped with the same logical drive / LUN combination on all initiators. 27. The amber LED on the disk drive may not light for a defunct drive nor flash for a rebuild on a hot-spare disk drive. The ServeRAID Manager GUI will display the rebuild status. 28. If a hard drive fails while the array is still synchronizing and the controller goes offline causing the array to failover to the alternate controller, a rebuild will not begin until the array has been failed back to the original controller and the synchronization has completed. 29. When a new replacement disk drive is reinserted into the same bay from which a disk drive had previously been removed (as a defunct drive), the rebuild may not start. If the rebuild of the array does not start, you need to define the replacement disk drive as a hotspare and assign it to the array to be rebuilt. 30. You must set the Cluster service to be dependent on the iSCSI service when using the MS iSCSI software initiator. For directions on how to do this refer to MS Technet article 883397. 31. When connecting shared disks for a MS iSCSI software initiator the drives must be mapped as persistent targets. To do this select the logical drive that you want to connect and then click logon. Then check the box that say "Automatically restore this connection when the system reboots". 32. LUN snapshots, when using the Flashcopy option can grow to 2x the size of the parent LUN, plus some additional 10-30MB. Please be aware that this space must be left as free space on the array to allow the LUN growth. 33. When a controller is in a failed state (all arrays moved to the remaining controller), do not do any array/LUN operations on the arrays/LUNS on the non-preferred controller. This includes such things as creating LUNs, creating snapshots, creating hotspares, etc. Wait until the bad controller or network is replaced and the arrays failed back to the 'preferred' controller before doing these array/LUN operations. 34. If a LUN or array or disk drive 'disappear' from the GUI or CLI or appear multiple times in the GUI or CLI, reboot the controllers. 35. Snapshot logical drives can not be mapped to the same host on a Windows 2000 host. Since the Snapshot logical drive contains the same disk signature as the base logical drive the Windows Disk Management tool will not know how to resolve this conflict. On a Windows 2003 host the disk signature will be changed if the snapshot logical drive is a read\write logical drive. It is always recommended to map the snapshot logical drives to a second host before accessing them. 36. To format an existing hard disk or partition on a shared cluster hard disk or partition, please refer to Microsoft support article 257937, at URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;257937 37. DS300 and DS400 only support U320 hard drives. ======================================================================= 1.2 Enhancements ----------------- DS300 ----------- Fixed issue with Data Scrubing DS400 ----------- Fixed issue with Data Scrubing ======================================================================= 1.3 Prerequisites ------------------ The system must be a dual controller DS400, Machine/Type: 1700/2RD, ES or DS300, Machine/Type: 1701/2RD,ES running either the 5.78 ,6.02 or 6.03 controller firmware. The management system must be running ServeRAID Manager v7.24. ======================================================================= 1.4 Dependencies ----------------- ServeRaid Manager provides the monitoring and Management Functions for the DS300 & DS400. This utility must be installed to provide notification of alerts to user level SNMP Trap Managers. ======================================================================= 2.0 Change History ----------------------------- ====================================================================== 2.1 Version History ----------------------------- DS300 ----------- 6.04 07/2005 Maintenance Release Fixed issue with data scrubing function 6.03 05/2005 Maintenance Release Fixed multiple CMVC defects associated with the following issues: Array/logical drive offline Background data scrubbing off Blink LED on controller Controller hangs Luns in transition MSCS cluster issues MS device logo issues ServeRAID Manager event reporting ServeRAID Manager info/status SnapShot creation Snapshot LUN issues 6.02 03/2005 Initial Dual Controller Model Release DS400 ----------- 6.04 07/2005 Maintenance Release Fixed issue with data scrubing function 6.03 05/2005 Maintenance Release Fixed multiple CMVC defects associated with the following issues: Array/logical drive offline Background data scrubbing off Blink LED on controller Controller hangs Luns in transition MSCS cluster issues MS device logo issues ServeRAID Manager event reporting ServeRAID Manager info/status SnapShot creation Snapshot LUN issues 6.02 03/2005 Maintenance Release Fixed multiple CMVC defects associated with the following issues: Array/Logical Drive offline Array/Logical Drive creation Array/Logical Drive controller ownership change Blink LED on controller Controller info/status Controller boot issue Controller hangs Diagnostic fix Duplicate Array/Logical Drives Error handling of HDD events Expansion fix and license key ISCSI initiator connectivity LUNs assessable to host LUNs in transition ServeRAID Manager event reporting ServeRAID Manager info/status reporting 5.87 12/2004 Initial Dual Controller Model Release ====================================================================== 2.2 ======================================================================= 2.3 Code levels at time of release are as follows ------------------------------------------------- DS300 : 6.04 DS400 : 6.04 Refer to the http://www.ibm.com/servers/storage/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 Installation from ServeRAID Manager GUI To download firmware, do the following: a. Start the ServeRaid Manager GUI. b. Click on the + sign next to Networked Storage and your Management Station, then select your storage subsystem from the menu. c. Right click on the subsystem that you wish to update and select Modify Enclosure Software and then Update Image. d. This launches the Software Update Wizard screen, select Next. e. Select xxx.xxx.xxx file from the location where the update image file is located, then select Next. f. Review the current image and new image to ensure that the correct image is going to be upgraded, then select Apply and confirm the selection. e. After the event monitor displays "Image Update Completed", the enclosure needs to be reset in order for the new image to take effect. 3.2 Installation from Command Line Interface (CLI) To download firmware, do the following: a. Open a Telnet session to the storage controller. Note: The default IP settings for the management port are, IP Address: 192.168.70.123, Subnet Mask: 255.255.255.0 Password: passw0rd (where the letter o is replaced with a zero 0 ) b. Place the DS400 firmware image on an FTP server that is also accessible to the storage subsystem. c. type ADMIN , then Enter d. type IMAGE UPLOAD ftp:///xx.xx.xx.upgrade, then Enter e. When asked if you want to replace IMAGE xxx type Y, then Enter f. Once the download is complete type System Reboot, then Enter g. When asked if you want to reboot, type Y, then Enter ======================================================================= 3.3 Helpful Hints ------------------ 1. If you lose connectivity to a controller, right click on the management station and select remove agent. Once the controller has been removed select add agent and add back the controller agent. 2. You will need to have the IQN of your iSCSI initiators before assigning the logical drives. Please use the proper software utility for finding this information before attempting to assign LUNs. If you need additional assistance, please refer to the "DS300 / DS400 Problem Determination Guide". 3. In some instances when a number of LUNs are assigned to a host, the Windows operating system will attempt to access the LUNs via the alternate path (if available) which can result in a long delay before the LUNs are available to the operating system. Assigning all the Arrays/Logical Drives to the A controller can minimize this from occurring. 4. IPfailover policies: There are four options to set for IPfailover; remote, local, local-remote and none. The default option is remote. This allows for: Eth2[A] to failover to Eth2[B] and Eth3[A] to failover to Eth3[B] and vice versa. The local option allows for failover between ethernet ports Eth2 and Eth3 within the same controller. There is no failover between controllers if this option is used. If this option is used you must also have ip forwarding or some other type of routing enabled within your network. The local-remote option allows for initial failover first between ethernet ports Eth2 and Eth3 on the same controller. Subsequent failovers will failover from ethernet port Eth2 to ethernet port Eth2 on the alternate controller or ethernet port Eth3 to ethernet port Eth3 on the alternate controllers. This option also requires support for ipforwarding or routing. The none option disables failover so that if a port fails those sessions will be dropped. ======================================================================= 4.0 Configuration Information ----------------------------- 4.1 Configuration Settings -------------------------- 1. By default the ServeRAID Manager software does not automatically map logical drives. This means that the logical drives are not automatically presented to host systems. All logical drives created in ServeRaid Manager must be assigned an access control list. The logical drive(s) may be assigned as unrestricted in iSCSI but a third party management software tool must then be used to control access to the assigned logical drive(s). 2. Access control is maintained per logical drive. You may assign the same logical drive to multiple hosts but you must then have some type of third party management software to control access to the logical drive. 3. When you are configuring IBM DS400 storage subsystems as a boot device, contact IBM support for supported configurations and instructions for configuring LUNs in the IBM storage subsystems as boot devices. ======================================================================= 4.2 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM TotalStorage™ DS400 1. Fibre Channel loop environments with the IBM Fibre Channel Hub/switch, 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. 2. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 1700. 3. The McData 4300 fabric switch, connected to IBM machine type 1700. ======================================================================= 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/servers/storage/support/disk 6.2 IBM TotalStorage™ Marketing Web Site: http://www.ibm.com/servers/storage/disk/ds/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 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.