IBM System Storage DS Storage Manager version 10.86.x5.43 for Sun Solaris 10 U10 and Solaris 11 Sparc operating systems. Note: Sun Solaris host attachment to the IBM 1722-all models (DS4300), 1724- all models (DS4100), 1742-models 90U/90X (DS4500), 1814-all models (DS4200, DS4700, DS3950 and DS5020), 1815-all models (DS4800), 1818-all models (DCS3700, DS5100 and DS5300), and 1746-all models (DS3500) requires additional purchase of an IBM Sun Solaris Host Kit Option. The IBM DS4000/DS5000 Sun Solaris Host Kit options contain the required IBM licensing to attach a Sun Solaris Host System to the DS3500, DCS3700, DS3950, DS4100, DS4200, DS4300, DS4500, DS4700, DS4800,DS5020, DS5100, or DS5300 storage subsystems. Please contact your IBM service representative or IBM resellers for purchasing information. Important: A problem causing recursive reboots exists while using 7.36.08 and 7.36.12 firmware on IBM System Storage DS4000 or DS5000 systems. This problem is fixed in 7.36.14.xx and above firmware. All subsystems currently using 7.36.08 and 7.36.12 firmware MUST run a file system check tool (DbFix) before and after the firmware upgrade to 7.36.14.xx or higher. Instructions for obtaining and using DbFix are contained in the 7.36.14.xx or higher firmware package. Carefully read the firmware readme and the DbFix instructions before upgrading to firmware 7.36.14.xx or higher. For subsystems with firmware level 7.36.08 or 7.36.12, configuration changes should be avoided until a firmware upgrade to 7.36.14.xx or higher has been completed successfully. Subsystems not currently using 7.36.08 or 7.36.12 do not need to run DbFix prior to upgrading to 7.36.14.xx or higher. DbFix may be run after upgrading to 7.36.14.xx or higher, but it is not required. DbFix is only applicable to subsystems using 7.36.xx.xx or greater firmware. If problems are experienced using DbFix or the resulting message received is Check Failed, DO NOT upgrade your firmware and contact IBM support before taking any further actions. IMPORTANT: 1. This storage manager software package contains non-IBM code (Open Source code.) Please review and agree to the Non-IBM Licenses and Notices terms stated in the DS_Storage_Manager_Non_IBM_Licenses_and_Notices_v3.pdf file before use. 2. This is NOT the correct DS Storage Manager version 10.86 host software package for the Solaris 10 x86 operating systems. Please refer to the DS Storage Manager version 10.86 host software package for the Solaris x86 operating systems. (C) Copyright International Business Machines Corporation 1999, 2013. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in section 6.0 "Trademarks and Notices?in this document. Refer to the IBM System Storage Support Web Site or CD for the IBM System Storage DS Storage Manager Version 10.8 Installation and Host Support Guide. This guide along with the DS Storage Manager program Online Help provide the installation and support information. Last Update: 12/02/2013 Please refer to corresponding Change History document for more information on new features and modifications. CONTENTS -------- 1.0 Overview 2.0 Installation and Setup Instructions 3.0 Configuration Information 4.0 Unattended Mode 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer ======================================================================= 1.0 Overview -------------- 1.1 Overview -------------- The 10.86 version of the DS Storage Manager host software is required for managing all DS3500, and DCS3700 storage models with controller firmware version 07.86.xx.xx or higher. In addition, it is also recommended for managing models with controller firmware version 6.5x.xx.xx or higher installed. Notes: 1. There are separate IBM DS Storage Manager host software packages for Solaris x86 and Solaris Sparc operating systems. The Solaris and Solaris_x86 directories contain the files necessary for installing the IBM DS Storage Manager Version 10.86 host software. Please select the appropriate directory for your operating system environment. The host software and storage subsystem firmware files are packaged separately and are available for download from the IBM System Storage Disk Storage Systems Technical Support web site: http://www.ibm.com/systems/support/storage/disk 2. The IBM Storage Manager host software version 10.8x new features and changes are described in the corresponding Change History document. Please refer to this document for more information on new features and modifications. 3. The latest version of the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide is also available on IBM's Support web site as a downloadable Portable Document format (PDF) file. Products Supported ----------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |----------- |-----------|--------------|-------------------------| | DS5300 | N/A | 1818 | 53A | |----------- |-----------|--------------|-------------------------| | DS5100 | N/A | 1818 | 51A | |----------- |-----------|--------------|-------------------------| | DS5020 | N/A | 1814 | 20A | |----------- |-----------|--------------|-------------------------| | DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, | | | | | 88A, 88H, 80A, 80H | |----------- |-----------|--------------|-------------------------| | DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, | | | | | 70T, 70S, 72T, 72S, | |----------- |-----------|--------------|-------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |----------- |-----------|--------------|-------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |----------- |-----------|--------------|-------------------------| | DS4300 | FAStT 600 | 1722 | 60X, 60U, 60J, 60K | | | | | 60L | |----------- |-----------|--------------|-------------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | |----------- |-----------|--------------|-------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | |----------- |-----------|--------------|-------------------------| | DS3950 | N/A | 1814 | 94H, 98H, | |------------|-----------|--------------|-------------------------| | DCS3700 | N/A | 1818 | 80C | |------------|-----------|--------------|-------------------------| | DS3500 | N/A | 1746 | C2A, A2S, A2D, C4A, | | | | | A4S, A4D | ----------------------------------------------------------------- ATTENTION: 1. For the DS4400 and the DS4100 storage subsystems - all models (Standard /dual controller and Single Controller), the controller firmware version 06.12.xx.xx and later must be used. 2. The DS4300 with Single Controller option(M/T 1722-6LU,6LX,and 6LJ), FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models) storage subsystems can no longer be managed by DS Storage Manager version 10.50.xx.23 and higher. 3. For the DS3x00 storage subsystems, please refer to the readme files that are posted in the IBM DS3000 System Storage support web site for the latest information about their usage, limitations or configurations. http://www.ibm.com/systems/support/storage/disk ======================================================================= 1.2 Limitations ---------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by DS4000/DS5000 storage subsystem controller firmware and Storage Manager host software releases to indicate which controller firmware and Storage Manager host software release that they were first seen and documented. No new limitations with Storage Manager version 10.86.x5.43 release (controller firmware 07.86.xx.xx) No new limitations with Storage Manager version 10.86.xx05.0035 release (controller firmware 07.86.xx.xx) New limitations with Storage Manager version 10.86.xx05.0028 release (controller firmware 07.86.xx.xx) 1. During the GUI mode of the installation on SLES 11 SP2, need to use mouse to select the options instead of the keyboard enter key on SLES 11 SP2 during the installation or run the installation in console mode.(LSIP200317279) 2. When using OLH with JAWS screen reader, will have difficulty on navigating through the content in the Index Tab under Help content window due to incorrect and duplicate reading of the text. Please use the search/find tab in the OLH. (LSIP200331090) 3. When using the accessibility software JAWS 11 or 13, may hear the screen reading of a background window, even if the dialog is not in focus. Please use the INSERT+B key to get the reading reinitiated for the dialog in focus.(LSIP200329868) 4. Will not be able to find Tray tab on storage array profile dialog launch. User needs to navigate to Hardware tab to find Tray tab.(LSIP200332950) 5. Will not be able to perform multiple array upgrades having different firmware versions. Please choose to upgrade arrays having different firmware versions separately.(LSIP200335962) 6. May hit IO error if all the paths are lost due delayed uevent, Please always make sure to run 'multipath -v0' command to rediscover the returning path. This will prevent the host from encountering an IO error due to the host losing all paths should the alternate path fails. (LSIP200347725) 7. There may be some confusion when the data is compared between summary tab and storage array profile. There is no actual functionality issue. The way the contents are labelled is not consistent.(LSIP200354832) New limitations with Storage Manager version 10.84.xx.30 release (controller firmware 07.84.xx.xx). 1. On a more than 30 drive disk pool with T10-PI enabled, the reconstruction progress indicator never moves because a finish notification is not sent to Storage Manager. When seeing this issue, just putting the replacement drive in the storage subsystem will allow the reconstruction to resume. (LSIP200298553) No new limitations with Storage Manager version 10.83.xx.23 release (controller firmware 07.83.xx.xx). New limitations with Storage Manager version 10.83.xx.18 release (controller firmware 07.83.xx.xx). 1. A non-T10PI logical drive can not be "volumecopied" to a logical drive with T10 PI functionality enabled. A non-T10 PI logical drive can only be volumeCopied to a non-T10 PI logical drive.(LSIP200263988) 2. Initiating dynamic logical drive expansion (DVE) on logical drives that are part of an asynchronous enhanced remote mirroring (ERM) without write order consistency will result in an error that is misleading because the controller is sending incorrect return code. DVE can only perform on logical drives having asynchronous ERM with write order consistency or synchronous ERM relationship.(LSIP200287980) 3. Cache settings can not be updated on thin logical drives. They can only be updated on the repository drives that are associated with these thin logical drives.(LSIP200288041) 4. Wait at least two minutes after canceling a logical drive creation in the disk pool before deleting any logical drives just created in the disk pool from the cancelled logical drive creation process. (LSIP200294588) 5. T10PI errors were incorrectly reported in the MEL log for T10PI- enabled logical drives that are participated in an enhanced remote mirroring relationship during the logical drive initializations.(LSIP200296754) 6. Having more than 20 SSD drives in a storage subsystem will result in SSD premium feature "Out-of-Compliance" error. One has to remove the extra SSD drives to bring the total number of SSDs in the storage subsystem to 20 or less.(LSIP200165276) 7. Pressing shift + F10 does not display the shortcut or context menu for the active object in the Storage Manger host software windows. The work-around is to use right-click on the mouse or the Windows key on the keyboard. (LSIP200244269) 8. Storage Manager subsystem amangement window performance might be slow due to Java runtime memory leak. The work around is to close the Storage Manager client program after the management tasks are completed. (LISP200198341) New limitations with Storage Manager version 10.77.xx.28 release (controller firmware 07.77.xx.xx). 1. Only one EXP5060 drive slot with a 3 TB SATA drive inserted can have the ATA translator firmware updated at any one time if the inserted 3 TB drive has "Incompatible" status. Simultaneously updating ATA translator firmware on multiple 3 TB drives having an "Incompatible" status might result in an "interrupted" firmware download state that requires the power- cycling of the subsystem to clear it. This limitation is reduced with the Storage Manager version 10.83 and later. The timeout was increased to accommodate simultaneously updating ATA translator firmware on up to five 3 TB SATA drives having an "Incompatible". 2. The 3 TB NL SAS drive can only be used to create non-T10PI arrays and logical drives. However, in certain conditions, where there are not any available hot-spare drives for T10PI enabled arrays, it will be used by the controller as a hot-spare for a failed drive in these T10PI enabled arrays. The controller will operate properly in this scenario and there are no adverse affects to the system while the 3 TB NL SAS drive is being used as the hot spare in a T10PI enabled array. This limitation is removed with controller firmware version 7.83.xx.xx and later. Please upgrade the controller firmware version 7.83.xx.xx and later if there is need to create a T10 PI-enabled arrays using 3TB NL SAS drives. New limitations with Storage Manager version 10.77.xx.16 release (controller firmware 07.77.xx.xx). 1. When you switch between the Search tab and the TOC tab, the topic that was open in the Search tab is still open in the TOC tab. Any search terms that were highlighted in the Search tab are still highlighted in the TOC tab. This always happens when you switch between the Search tab and the TOC tab. Workaround: Select another topic in the TOC to remove all search term highlighting from all the topics. 2. Support tab in the AMW kept open for longer duration will result in display of unevenly spaced horizontal marks. If the storage Manager is kept open for long durations a few grey lines may be seen on the Support Tab after restoring the AMW. Re-launching the AMW eliminates this problem. 3. Kernel panic while loading RedHat 6.0 on Power PC installation. When trying to load the RHEL6 LoP installation to the system that has existing old OS(LPAR), the system panics. Workaround: For a rack system with an HMC, delete the LPAR and recreate a new one for the installation to work. For a rack system without an HMC and the Power Blade system, the user needs to go to Open Firmware Prompt and type in “dev nvram?and “wipe- nvram? The system will reboot afterward and need to process normal RHEL6 installation. 4. Node unfencing can fail during RHCS startup when automatically generated host keys are used. The cluster manager service (cman) will fail to start, and the user will see the error message “key cannot be zero?in the host log. A user is somewhat likely to hit the issue if the cluster.conf file uses does not have host keys defined manually. If the user forgoes use of SCSI reservation fencing altogether, and relies only on power fencing, they will not experience this issue. Bugzilla 653504 was submitted to RedHat for this issue. 5. RHCS services with GFS2 mounts cannot transfer between nodes when client mounts with NFSv4. When attempting to transfer a cluster service manually, while a client was connected using NFS version 4, the GFS2 mount points failed to unmount. This caused the service to go to the “failed? state. The mount point, along with any other mount points exported from the same virtual IP address, will become inaccessible. Not likely to happen if the user configures the cluster nodes not to allow mount requests from NFS version 4 clients. Red Hat Bugzilla #654333 was opened to discover the root cause and fix the problem 6. The storage subsystem configuration script contains the logical drive creation commands with incorrect T10PI parameter. The workaround is to manually edit the file to change instances of dataAssurance parameters to T10PI. 7. The DS3500 subsysem does not support External Key Management at this time. Please contact IBM resellers or represeantives for such support in the future. New limitations with Storage Manager version 10.70.xx.25 release (controller firmware 07.70.xx.xx). 1. Kernel Panic reported on Linux SLES10 SP3 during controller failover. Probability of this issue happening in the field is low. Workaround: Avoid placing controllers online/offline frequently. Novell was informed about this issue. Opened Novell Bugzilla NVBZ589196. 2. CHECK CONDITION b/4e/0 returned during ESM download on DS5000 The interposer running LP1160 firmware is reporting an Overlapped Command (0B/4E/00) for a Read Command containing an OXID that was very recently used for a previous read command on the same loop to the same ALPA. In almost all cases, this command will be re-driven successfully by the controller. Impact should be negligible. Workaround: Can be avoided by halting Volume I/O prior to downloading ESM firmware. 3. If a host sees RAID volumes from the same RAID module that are discovered through different interface protocols (fibre/SAS/iSCSI) failovers will not occur properly and hosts IOs will error out. If the user does not map volumes to a host that can be seen through different host interfaces this problem will not occur. Workaround: Place controller online and reboot the server to see all volumes again. 4. Linux guest OS reported I/O error during Controller Firmware Upgrade on ESX4.1 with Qlogic HBA. The user will see I/O errors during controller activation from the guest OS due to mapped devices becoming inaccessible and offline. Workaround: This issue occurs on various Linux guest OSes, so to avoid the issue the user should perform an offline (no I/O to controllers) controller firmware upgrade. 5. I/O Error on Linux RH 4.8 after rebooting controller on DS3500 iSCSI. The devices will be disconnected from the host until the iSCSI sessions are re-established. workaround: Restart the iSCSI service. Configure the iSCSI service to start automatically on boot. 6. CFW Upgrade on 4.1 w/SLES 11 fails with IO error on SLES 11 Guest partition. This issue occurred if there is filesystem volume in SLES11 VM. User will see I/O errors and Filesystem volumes in SLES11 VMs will be changed to read-only mode. Workaround: User can perform controller FW upgrade with either no I/O running on SLES11 VM or no Filesystem created in SLES11 VMs. 7. "gnome-main-menu" crashes unexpectedly while install HSW on Suse 10. The crashes appear to happen randomly with other applications as well.? After the crash the menu reloads automatically.?Dismiss the prompt and the host will reload the application.?This problem appears to be a vendor issue. 8. I/O errors on RHEL 4.8 guests on VMware 4.1 during controller reset. VMware has suggested VMware 4.1 P01 may resolve this issue. No support was issued for RHEL 4.8 guests under VMware 4.1 over SAS. Workaround: Use RHEL 5.5. 9. VMWare guest OS not accessible on iSCSI DS3524 (VMware SR 1544798051, VMware PR 582256). VMware has suggested VMware 4.1 P01 may resolve this issue. Workaround: Use Fibre Channel or SAS connectivity. 10. When DMMP is running in a BladeCenter SAS environment, I/O errors occur during failover and controller firmware operations. Support for Device Mapper and SLES 11.1 SAS has been restricted and will not be published. Workaround: Install RDAC. 11. SLES11.1ppc SAN boot fails on PS700 with 10 Gb Qlogic ethernet to DS3512. After configuration and install of Linux on a LUN using software iSCSI, the JS blade will not boot into the OS. Workaround: Use local boot, SAS or Fibre Channel. 12. ‘No response?messages from Device Mapper devices with volumes on non-preferred path. Any I/O operations against volumes mapped to failed devices will timeout or hang. Workaround: This problem requires the host to be rebooted in order to restart I/O successfully. Update SLES11.1 to maintenance update 20101008 containing kernel version 2.6.32.23-0.3.1. Note that this kernel version has not been fully certified by LSI and should only be used if this issue is encountered. Bugzilla #650593 contains issue details and fix provided by Novell. 13. LifeKeeper 7.2.0 recovery kits require multiple host ports to use SCSI reservations. Workaround: Use two single port SAS HBAs. In this case each port will be represented as a host, and LifeKeeper will identify both separately. Another way to avoid the issue is to use MPP as the failover driver. 14. Unexpected "jexec" messages during mpp installation/un-installation on SLES 11.1. Workaround: None - https://bugzilla.novell.com/show_bug.cgi?id=651156 15. I/O write errors on mounted LifeKeeper volumes before node resources transfers to another node. recovery: I/O can be restarted as soon as node resources are transferred to another node in the cluster. Workaround: None. 16. Solaris 10u8 guest OS disks become inaccessible on ESX35u5 during sysReboot on array controller. This can be avoided by not using raw device mappings and instead using virtual disks. If raw device mappings are required, they must be used with virtual compatability mode selected when adding the disks to the guest OS. Workaround: None. 17. Solaris 10u8 guest OSes reported I/O error during Controller Firmware Upgrade on ESX35U5 with Qlogic HBA. Permanent restriction. Workaround: Perform upgrade with no I/O. 18. Solaris guest OS reported I/O error during Controller reset on ESX35U5. The only recovery method is to rebooting the failed VM host. Permanent restriction. Please refer to the file LegacyStorageManagerLimitations-Solaris.chg in the Storage Manager host software download package or in the !Readme CD directory for information on the legacy limitions that might still be applicable for your environment. ======================================================================= 1.3 Enhancements ----------------- The DS Storage Manager version 10.86.x5.43 host software in conjunction with controller firmware version 7.86.32.00 and higher provides support for - Provide the following new functions - Add support for DCS3860 (7.86.36.01) - Provide the fixes for the field defects as shown in the changelist file. For more information, please view the IBM System Storage DS Storage Manager Version 10.8 Installation and Host Support Guide and the IBM System Storage DS Storage Manager Version 10 Copy Services User's Guide. IMPORTANT: Do not use Storage Manager host software version 10.77.x5.xx and earlier to manage storage subsystems with 3 TB NL SAS and SATA drive option installed. ======================================================================= 1.4 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- Note: 1. The IBM Storage Manager host software version 10.86 for Solaris OS new features and changes are described in the corresponding Change History document. Please refer to this document for more information on new features and modifications. 2. IBM recommends upgrading to Storage Manager version 10.83.x5.18 or later because it does not include the IBM Support Monitor Profiler code. This code has a security vulnerability that might allow unwanted XSS and SQL injections. If upgrading to Storage Manager version 10.83.x5.18 or later is not possible, one should remove the IBM Support Monitor Profiler code from the management station immediately. The instruction to uninstall IBM Support Monitor Profiler can be found in the IBM System Storage DS Storage Manager Version 10.8 Installation and Host Support Guide. This release of IBM DS Storage Manager host software for Sun Solaris was tested on the following Sun servers and Operating System configurations: The minimum requirement is a Sun server with PCI and/or S-Bus Architecture with: 1. 1 GB system memory. 2. 480 Mhz Processor 3. Ethernet network interface card. 4. CDROM drive. 5. Mouse or similar pointing device. For SMclient, at least 900 MB of available on /opt and root-level (superuser) permission is required for installation Ensure the storage management station or the host acting as a storage management station is running one of the following operating systems: 1. Solaris 10 U10 x86 and Sparc editions 2. Solaris 11 x86 and Sparc editions 3. The DS4000 Storage Manager version 9.14 and higher host software installer wizard requires the installation of a graphics adapter in the SUN Solaris server for it to run. For servers without the graphics adapter, you can execute the installer via sh -i console or individual host software installation packages are provided in the SM10.83_Solaris_Single-10.83.x5.18.tgz file. 4. Required installation order for Storage Manager 10.86.xx.xx and controller firmware 07.86.xx.xx or higher: 1. SMruntime - always first 2. SMesm - required by client 3. SMclient 4. SMagent 5. SMutil Note: Steps 1-5 will be done by the SMIA installer if the installation is performed using the SMIA installer. 6. Controller firmware and NVSRAM 7. ESM firmware 8. Drive firmware The Sun Solaris Multipath driver support is as follows; 1. SUN Solaris 10 U10 (x86 or Sparc) with MPxIO. 2. SUN Solaris 11 (x86 or Sparc) with MPxIO with TPGS. Code levels at time of release are as follows ----------------------------------------------- The version of the host-software installer wizard for this release is SMIA-SOLX86-10.86.xx05.0035.bin. Note: The web-download Storage Manager version 10.86 host software package must be first unpacked (tar -xvz) into a user-defined directory. Then, go to this directory, locate the Solaris directory to access the Storage Manager version host software installation file(s). Starting with the DS4000 storage manager version 9.12, all of the host software packages are included in a single Storage Manager host software installer wizard. During the execution of the wizard, the user will have a choice to install all or only certain software packages depending the need for a given server. There must be at least 990MB of free space in the /opt directory for the installer wizard to install the host software packages. * The DS3000/DS4000/DS5000 Storage Manager host software installer wizard requires the installation of a graphics adapter in the SUN Solaris X86 server for it to run. If you wish to use the wizard but do not have a graphics adapter, you can execute the installer via sh -i console to run in console mode. In addition, there must be at least 990MB of free space in the /opt directory for the installer wizard to install the host software packages. For Solaris X86 servers without the graphics adapter, individual host software installation packages are provided in the SM10.86_Solaris_x86_Single-xx05.0035.tgz file. This installer wizard will install the following version of the host- software packages SMruntime: 10.86.0005.0000 SMclient: 10.86.0G05.0035 SMesm: 10.86.0G05.0007 SMagent: 10.02.0005.0000 SMutil: 10.01.0005.0000 Refer to the IBM System Storage Interoperation Center (SSIC) web site - http://www.ibm.com/systems/support/storage/ssic/ for information on the latest supported OS, switches and HBA released code levels. ======================================================================= 1.5 Dependencies ----------------- ATTENTION: 1. The DS5020, DS3950, EXP5000, EXP810, EXP520, and EXP395 FC-SAS drives must have the FC-SAS interposer firmware version 2264 or later installed. Some drives with FC-SAS interposer firmware version earlier than version 2264 may report incorrect inquiry information during Start of Day. This causes the controller firmware to make the drive uncertified (incompatible), which in turn, causes the drive to no longer be accessible for I/Os. This condition will also cause the associated array to go offline. Since the array is no longer accessible, the controller firmware may not recover the cache for all LUNs under this array. This behavior may result in data not being written. If you believe that you have encountered this issue, please call IBM Support for assistance with the recovery actions. The FC-SAS interposer firmware version 2264 and later is available in the ESM/HDD firmware package version 1.78 or later. 2. The 3 TB SATA drive option for EXP5060 expansion enclosure requires ATA firmware version LW1613 and higher. The drive will be shown as "Incompatible" if it is installed in an EXP5060 drive slot with ATA translator firmware version older than LW1613. Please refer to the latest EXP5060 Installation, Users and Maintenance Guide for more information on working with the 3 TB SATA drive option. 3. The Storage Manager host software version 10.83.x5.18 or higher is required for managing storage subsystems with 3 TB NL FC-SAS drives. Storage manager version 10.83.x5.18 or higher in conjunction with controller firmware version 7.83.xx.xx and later allow the creation of T10PI-enabled arrays using 3 TB NL FC-SAS drives. 4. The IBM System Storage DS4000 Controller Firmware Upgrade Tool is required to upgrade any system from 6.xx controller firmware to the 7.xx.xx.xx controller firmware. This tool has been integrated into Enterprise Management Window of the DS Storage Manager v10.83 Client. 5. Always check the README files (especially the Dependencies section) that are packaged together with the firmware files for any required minimum firmware level requirements and the firmware download sequence for the DS4000/DS5000 drive expansion enclosure ESM, the DS4000/DS5000 storage subsystem controller and the hard drive firmware. IBM DS Storage Manager version 10.83 host software requires the DS4000 & DS5000 storage subsystem controller firmware be at version 06.xx.xx.xx or higher. The IBM DS4000 Storage Manager v9.60 supports storage subsystems with controller firmware version 04.xx.xx.xx up to 05.2x.xx.xx. The IBM DS Storage Manager v10.36 supports storage subsystems with controller firmware version 05.3x.xx.xx to 07.36.xx.xx. The IBM DS Storage Manager v10.70 supports storage subsystems with controller firmware version 05.4x.xx.xx to 07.70.xx.xx. ======================================================================= 2.0 Installation and Setup Instructions ----------------------------------------- Note: The web-download Storage Manager version 10.86 host software package must be first unpacked (tar -xvz) into a user-defined directory. Then, go to this directory, locate the Solaris directory to access the Storage Manager version 10.86 host software installation file(s). 2.1 Step-by-step instructions for this code update are as followed ------------------------------------------------------------------- 1. Install and update the driver for the IBM DS3000/DS4000/DS5000 FC Host Bus Adapter. a. Install the hardware by using the instructions that come with the adapter. b. Install the Fibre Channel Host Bus Adapter driver by using the instructions provided with the adapter. 2. Install the new Storage Manager host software. If there is previous version (7.x, 8.x or 9.1x) of the IBM DS4000 Storage Manager host software (ie. SMRuntime, SMClient, RDAC, SMUtil and SMAgent packages) installed in the system, you have to uninstall it first before installing the new version of the storage manager host software. Refer to the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide for detailed installation instructions. Note: The Storage Manager installer might take up to 5 minutes to display the end user license for machine code depending on the Operating System versions. Note: The Storage Manager installer might take up to 5 minutes to display the end user license for machine code (EULA) depending on the Operating System versions. Refer to the http://www.ibm.com/systems/support/storage/disk IBM System Storage Disk Storage Systems Technical Support web site for the the latest DS Storage Manager host software, the DS4000/DS5000 controllers firmware, the drive expansion enclosure ESM firmware and the hard disk drive code. ======================================================================= 2.2 Helpful Hints ------------------ 1. The DS4500 and DS4300 storage subsystem have updated recommended drive-side cabling instructions with the release of 06.23 controller firmware. The DS4500 instructions are documented in the IBM System Storage DS4500 Installation, Users, and Maintenance Guide (GC27-2051-00 or IBM P/N 42D3302). The DS4300 instructions are documented in the IBM System Storage DS4300 Installation, Users, and Maintenance Guide (GC26-7722-02 or IBM P/N 42D3300). Please follow the cabling instructions in these publication to cable the new DS4500 and DS4300 setup. If you have an existing DS4500 setup with four drive side minihub installed that was cabled according to the previously recommended cabling instructions, please schedule down time as soon as possible to make changes to the drive side FC cabling. Refer to the IBM System Storage DS4500 and DS4300 Installation, Users, and Maintenance Guide for more information. 2. For partitioning in clusters. The partition must be done on the host group level not on the host level. This will allow all cluster hosts to see the same storage. 3. Do not delete the Access LUN or Access Volume. The Access LUN is required by the SMclient to communicate with the storage controllers when using the in-band management method. 4. 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 DS4100 storage subsystem (machine type 1724): 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. - IBM DS4200 storage subsystem (machine type 1814): Depending on the ordering channels, the DS420 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage partitions. If the DS4200 storage subsystem is ordered with less than 64 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - IBM DS4300 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 DS4300 Turbo option comes with 8 partition storage partitioning premium option installed. An upgrade to 64 partitions can be purchased for the IBM DS4300 Turbo option. - IBM FAStT200, FAStT500, and DS4400 storage subsystems (machine type 3542, 3552 and 1742 - models 1RU and 1RX, respectively): The standard configuration has 64 partitions storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM DS4500 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. - IBM DS4700 storage subsystem (machine type 1814): Depending on the ordering channels, the DS4700-model 70 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16, 32, 64 or 128 storage partitions. Similarly, the DS4700-model 72 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16, 32, 64 or 128 storage partitions. If the DS4700 storage subsystem is ordered with less than 128 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - IBM DS4800 storage subsystem (machine type 1815): Depending on the ordering channels, the DS4800 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16, 32, 64, 128, 256 or 512 storage partitions. If the subsystem is ordered with less than 512 partitions, an upgrade from 8 to 16, 8 to 32, 8 to 64, 16 to 32, 16 to 64, 32 to 64, 32 to 128, 64 to 128, 64 to 256, 128 to 256, 128 to 512, or 256 to 512 partition storage partitioning premium feature option can be purchased. - IBM DS5300 and DS5100 storage subsystem (machine type 1818): the DS5300 and DS5100 storage subsystem is shipped with a user selected 8, 16, 32, 64, 128, 256 or 512 storage partitions. If the subsystem is ordered with less than 512 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. 5. Fabric topology zoning requirement with AIX fcp_array (RDAC) and Solaris RDAC only. 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 DS4000 storage subsystems DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 storage subsystems DS4300 (IBM machine type 1722) and DS4100 (IBM machine type 1724) have two ports per controller. The DS4000 storage Server FAStT200 (IBM machine type 3542) has only one port per controller. The DS4700 storage subsystem (IBM machine type 1814) has up to four ports per controller. The DS4800 storage subsystem (IBM machine type 1815) has four ports per controller. 6. Subsystems using dynamic multipathing (DMP) for the failover driver will need to manually do target and LUN definition in /kernel/drv/sd.conf. 7. When installing the SMibmasl.pkg the Solaris host will need a reboot -- -r. 8. To improve the reboot time of Sun 4800 Sunfire server or Sun servers with Solaris 9 installed, remove all ghost targets and LUNs from /kernel/drv/sd.conf file. Failure to remove ghost targets and LUNs may increase the boot time of the Sun servers. 9. Target volumes for VolumeCopy premium feature need the volume permissions changed. By default the VolumeCopy is set to read-only. The target volume permission for the VolumeCopy must be changed to read-write. 10. The DS4000 controller host ports or the Fibre Channel HBA ports can not be connected to a Cisco FC switch ports with "trunking" enable. You might encounter failover and failback problems if you do not change the Cisco FC switch port to "non-trunking" using the following procedure: a. Launch the Cicso FC switch Device Manager GUI. b. Select one or more ports by a single click. c. Right click the port(s) and select Configure, a new window pops up d. Select the "Trunk Config" tab from this window, a new window opens e. In this window under Admin, select the "non-trunk" radio button, it is set to auto by default. f. Refresh the entire fabric. 11. When making serial connections to the IBM DS storage controller, the baud rate is recommended to be set at either 38400 or 57600. Note: Do not make any connections to the IBM DS storage subsystem serial ports unless instructed by IBM Support. Incorrect use of the serial port might result in loss of configuration and/or loss of data. 12. All enclosures (including DS4000 storage subsystem with internal drive slots) on any given drive loop/channel should have complete unique ID's, especially the single digit (x1) portion of the ID, assigned to them. For example, in a maximum configured DS4500 storage subsystem, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosure id's with the same single digit such as 11, 21 and 31 should not be used on the same drive loop/channel. In addition, for enclosures with mechanical enclosure ID switch like DS4300 storage subsystems, EXP100 or EXP710 storage expansion enclosures, do not use enclosure ID value of 0. The reason is with the physical design and movement of the mechanical enclosure ID switch, it is possible to leave the switch in a “dead zone?between ID numbers, which return an incorrect enclosure ID to the storage management software. The most commonly returned enclosure ID is 0 (zero). In addition to causing the subsystem management software to report incorrect enclosure ID, this behavior also result in enclosure ID conflict error with the storage expansion enclosure or DS4000 storage subsystem intentionally set the ID to 0. The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810 storage expansion enclosures did not have mechanical ID switches. Thus, they are not susceptible to this problem. In addition, these storage subsystems and storage expansion enclosures automatically set the Enclosure IDs. IBM recommendation is not make any changes to these settings unless the automatic enclosure ID settings resulting in non- unique single digit settings for enclosures (including the storage subsystems with internal drive slots) in a given drive loop/channel. 13. The ideal configuration for SATA drives is one drive in each EXP per array, one logical drive per array and one OS disk partition per logical drive. This configuration minimizes the random head movements that increase stress on the SATA drives. As the number of drive locations to which the heads have to move increases, application performance and drive reliability may be impacted. If more logical drives are configured, but not all of them used simultaneously, some of the randomness can be avoided. SATA drives are best used for long sequential reads and writes. 14. IBM recommends at least one hot spare per EXP100 drive expansion enclosure. A total of 15 hot-spares can be defined per IBM DS storage subsystem configuration. 15. Starting with the IBM DS Storage Manager (SM) host software version 9.12 or later, the Storage Manager client script window looks for the files with the file type of ".script" as the possible script command files. In the previous versions of the DS4000 Storage Manager host software, the script window looks for the file type ".scr" instead. (i.e. enableAVT.script for SM 9.12 or later vs. enableAVT.scr for pre-SM 9.12) ======================================================================= 3.0 Configuration Information ----------------------------- 3.1 Configuration Settings -------------------------- 1. By default the IBM DS Storage Manager SMClient program does not automatically map logical drives. This means that the logical drives are not automatically presented to host servers. a. For a new installation, after creating new arrays and logical drives, create a storage partition with the host type of Sun-Solaris and map the logical drives to this partition. b. If you are upgrading the NVSRAM with Storage Partitions, you may have to change the default host type to match the host system OS. After upgrading the NVSRAM, the default host type is reset to Windows 2000/Server 2003 non-clustered for DS4000 storage server with controller firmware version 06.14.xx.xx or later. For DS4000 storage server with controller firmware version 06.12.xx.xx or earlier, it is reset to Windows non-clustered (SP5 or higher), instead. Refer to the IBM DS Storage Manager online help to learn more about creating storage partitions and changing host types. 2. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815, 1818, 3542 or 3552 storage controllers as boot devices, contact IBM support for supported configurations and instructions for configuring IBM storage controllers 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.script: 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.script: 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. - EnableAVT_W2K_S2003_noncluster.script: (Do not use this script when the installed storage subsystem controller firmware version is of 7.83.xx.xx and later) 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.script: 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) 4. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815, 1818 or 3552 storage servers in host cluster Remote Mirror configurations, contact IBM support for supported host cluster configurations and instructions for configuring IBM storage controllers in a clustered Remote Mirror configurations. ======================================================================= 3.2 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS Storage Manager Version 10.86. 1. The IBM EXP395 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS3950. EXP810 drive enclosures are also supported in the DS3950 with the purchase of a premium feature key. 2. The IBM EXP520 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5020. EXP810 drive enclosures are also supported in the DS5020 with the purchase of a premium feature key. 3. The IBM EXP5000 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5100 and DS5300. 4. The DS4100 (machine type 1724-all models) storage subsystem does not support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC) drive expansion enclosure. 5. The DS4800 storage subsystem (machine type 1815-all models) does not support the attachment of the FAStT EXP500 and DS4000 EXP700 drive expansion enclosures. 6. The DS4200 (machine type 1814 - models 7VA/H) does not support the attachment of the DS4000 EXP100 (SATA), EXP710 (FC) and EXP810 (SATA and FC) drive expansion enclosures. In addition, it does not support Fibre Channel disk drive options. 7. The IBM DS4000 EXP420 Expansion Enclosure is not supported attached to any other IBM DS4000 Storage Subsystems except the DS4200. 8. The DS4100 with Single Controller option does not support the attachment of the DS4000 storage expansion enclosures. 9. The DS5100 and DS5300 storage subsystems do not support the attachment of the DS4000 EXP100, EXP700, EXP710 drive expansion enclosures. The EXP810 is only supported through an RPQ process. 10. The DS5000 EXP5000 drive expansion enclosure is supported attached to the DS5100 and DS5300 only. 11. The DS4700 and DS4800 storage subsystems do not support the attachment of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700 Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be attached to the DS4700 and DS4800 storage subsystems. 12. The DS4300 storage subsystem with Single Controller option does not support the controller firmware version 06.xx.xx.xx. The correct firmware version for these DS4300 storage subsystem models is 05.34.xx.xx. 13. 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. 14. The IBM Fibre Channel hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1814, 1815, 3542 and 3552. 15. A configuration in which a server with only one FC/SAS/iSCSI host bus adapter connects directly to any IBM DS storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC/SAS/iSCSI host bus adapter connects to both controller ports of any IBM DS storage subsystem with dual controllers via FC/SAS/Ethernet switch (SAN-attached configuration.) Note: The HBA(s) in the Sun server must have FC connection to both controller A and B ports of any DS4000/DS5000 storage subsystem with dual controllers via FC switch attached or via direct attached. ======================================================================= 4.0 Unattended Mode --------------------- N/A ======================================================================= 5.0 WEB Sites and Support Phone Number ---------------------------------------- 5.1 IBM System Storage Disk Storage Systems Technical Support web site: http://www.ibm.com/systems/support/storage/disk 5.2 IBM System Storage Marketing Web Site: http://www.ibm.com/systems/storage 5.3 IBM System Storage Interoperation Center (SSIC) web site: http://www.ibm.com/systems/support/storage/ssic/ 5.4 You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426- 7378). IMPORTANT: You should download the latest version of the DS Storage Manager host software, the DS4000/DS5000 storage subsystem controller firmware, the DS4000/DS5000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. For more information about how to register for support notifications, see the following IBM Support Web page: ftp.software.ibm.com/systems/support/tools/mynotifications/overview.pdf You can also check the Stay Informed section of the IBM Disk Support Web site, at the following address: www.ibm.com/systems/support/storage/disk ======================================================================= 6.0 Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DS3000 DS3500 DCS3700 DCS3860 DS4000 DS5000 FAStT System Storage the e-business logo xSeries pSeries HelpCenter UNIX is a registered of The Open Group in the United States and other countries. Microsoft, Windows, and Windows NT are of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. SUN, Solaris, Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. QLogic and SANsurfer are trademarks of QLogic Corporation. Other company, product, or service names may be trademarks or service marks of others. ======================================================================= 7.0 Disclaimer -------------- 7.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. 7.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.