IBM System Storage™ DS Storage Manager version 10.70.xx.25 for Novell NetWare 6.5 with Service Pack 8 or higher. IMPORTANT: 1. Starting with the DS Storage Manager version 9.16 release, there is no longer an IBM System Storage™ DS Storage Manager host software package (i.e.. SMclient, SMutil) for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are I/O attached to the Novell Netware server hosts, you must install the DS Storage Manager client software (SMclient) on a Microsoft Windows or Linux management workstation and manage the DS4000/DS5000 storage subsystem via out-of-band management method. The SMclient program is included in the IBM System Storage™ DS Storage Manager version 10.70 for the 32bit (x86) version of Linux operating systems or the IBM System Storage™ DS Storage Manager version 10.70 for Microsoft Windows operating systems host software packages. These packages are available included in the DVD and are also 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 storage manager client software packages for Windows and Linux contain 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.v2.pdf file before use. This pdf file is packaged with the appropriate storage manager client software package. (C) Copyright International Business Machines Corporation 1999, 2009. 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 "Trademarks and Notices” in this document. Note: Novell NetWare host attachment to the IBM 1722-all models (DS4300), 1724-all models (DS4100), 1742-models 90U/90X (DS4500), 1814-all models (DS4200 and DS4700), 1815-all models (DS4800), and 1818-all models (DS5100 and DS5300) requires additional purchase of an IBM DS4100/DS4200/DS4300/DS4500/DS4700/DS4800/DS5100/DS5300 Novell NetWare Host Kit Option. The IBM DS4000/DS5000 Novell NetWare Host Kit options contain the required IBM licensing to attach a Novell NetWare Host System to DS4100, DS4200, DS4300, DS4500, DS4700, DS4800, DS5100, or DS5300 storage subsystems. Please contact your IBM service representative or IBM resellers for purchasing information. Refer to the IBM System Storage™ Support Web Site or DVD for the IBM System Storage DS Storage Manager Version 10 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/14/2010 Please refer to corresponding Change History document for more information on new features and modifications. Products Supported ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS5300 | N/A | 1818 | 53A | |------------|-----------|--------------|------------------------| | DS5100 | N/A | 1818 | 51A | |------------|-----------|--------------|------------------------| | 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 | ---------------------------------------------------------------- ATTENTION: 1. The DS4000 storage subsystem controller firmware version 05.40.xx.xx and earlier along with its associated NVSRAM files should not be loaded into DS4000 storage subsystems connected to DS4000 EXP100 drive expansion enclosures. 2. 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. 3. For the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems connected to the DS4000 EXP810 drive expansion enclosures, the latest controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP810 drive expansion enclosure attachment. 4. For the DS4700 and the DS4800 storage subsystems connected to the DS4000 EXP100 drive expansion enclosures, the controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4700 and the DS4800 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP100 drive expansion enclosure attachment. 5. 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. 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 ------------------- NOTE: DS4000 controller firmware versions 6.12.xx.xx * Attachment support for EXP710 and EXP100 SATA disk drive expansion enclosures for DS4300 and DS4500. * No attachment support for EXP810 disk drive expansion enclosure. DS4000 controller firmware version 06.60.xx.xx * Attachment support for EXP710, EXP810, and EXP100 SATA disk drive expansion enclosures for DS4300 with dual controller, DS4500, DS4700 and DS4800. * Attachment support for EXP420 for DS4200 only. DS4000/DS5000 controller firmware version 7.36.xx.xx * Supports DS4200, DS4700, DS4800, DS5100 and DS5300 only. DS4000/DS5000 controller firmware version 7.50.xx.xx * Supports DS4200, DS4700, DS4800, DS5100 and DS5300 only. DS4000/DS5000 controller firmware version 7.60.xx.xx * Supports DS3950, DS4200, DS4700, DS4800, DS5020, DS5100 and DS5300 only. Starting with the DS4000 Storage Manager version 9.16 release, there are not any IBM System Storage™ DS Storage Manager host software packages for the Novell Netware server operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware server hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the DS4000/DS5000 storage subsystem via out-of-band management method. The SMclient program is included in the IBM System Storage™ DS Storage Manager version 10.70 for the 32 and 64 bit version of Linux operating systems or the IBM System Storage™ DS Storage Manager version 10.70 for Microsoft Windows operating systems host software packages. The usage permission of the SMclient program in the IBM System Storage™ DS Storage Manager version 10.70 host software packages for Windows and Linux does not give the user the entitlement to the Windows or Linux host IO privileges. In those DS4000/DS5000 storage subsystems that require the Windows and Linux host entitlement kits/ options, these kits/options must be purchased before these servers can be IO attached to the DS4000/DS5000 storage subsystems. The IBM Storage Manager host software version 10.70 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. These IBM System Storage™ DS Storage Manager version 10.70 host software packages for Windows and Linux and DS4000/DS5000 storage subsystem firmware files are available for download from the IBM System Storage™ Disk Storage Systems Technical Support web site - http://www.ibm.com/systems/support/storage/disk. Please Refer to the IBM System Storage™ Support Web Site for the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide. This guide along with the DS Storage Manager program Online Help provide the installation and support information. The latest versions of these files are available on IBM System Storage™ Disk Storage Systems Technical Support web site as PDF files. Also, please refer to the readme file(s) that are included in the IBM System Storage™ DS Storage Manager version 10.70 host software package(s) for Windows and Linux for the latest information on usage and installation. IMPORTANT: This release of IBM DS Storage Manager host software supports all DS4000/DS5000 storage subsystems with general released firmware versions from 05.40.xx.xx up to 07.60.xx.xx. Refer to the IBM Support Web Site for latest DS4000/DS5000 controller firmware and NVSRAM files for IBM machine types 1722, 1724, 1742, 1814, 1815, 1818, 3542 and 3552. The following table shows the first four digits of the latest controller firmware versions that are currently available for various models of the DS4000/DS5000 storage subsystems. --------------------------------------------------- | IBM Storage | Controller firmware version | | Subsystem Model | | |------------------|--------------------------------| | DS5300 (1818) | 07.60.xx.xx | |------------------|--------------------------------| | DS5100 (1818) | 07.60.xx.xx | |------------------|--------------------------------| | DS4800 (1815) | 07.60.xx.xx | | | (07.60.28.00 or later only) | |------------------|--------------------------------| | DS4700 (1814) | 07.60.xx.xx | | | (07.60.28.00 or later only) | |------------------|--------------------------------| | DS4500 (1742) | 06.60.xx.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.56.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.60.xx.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.60.xx.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4200 (1814) | 07.60.xx.xx | | | (07.60.28.00 or later only) | |------------------|--------------------------------| | DS4100 (1724) | 06.12.56.xx | | (standard dual | | | Single | | | controller Opt.)| | --------------------------------------------------- Note: Controller firmware 06.23.xx.xx or later, is required for the DS4300-standard- dual controller or Turbo models, the DS4500-all models, the DS4700- all models and the DS4800-all models for attaching combinations of EXP810 and EXP100 storage expansion enclosures behind a DS4000 storage subsystem. New features introduced with controller firmware version 07.50.xx.xx or later are not available for DS4000 controllers with older firmware versions installed. The following table shows the controller firmware versions required for attaching the various models of the DS4000 Storage Expansion Enclosures. --------------------------------------------------------------------- | Controller | EXP Storage Expansion Enclosures | | FW Version |------------------------------------------------------- | | EXP100 | EXP420 | EXP500 | EXP700 | EXP710 | EXP810 | |------------|---------|--------|--------|--------|--------|--------| |5.3x.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.40.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.41.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.42.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.0x.xx | Yes | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.1x.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.12.xx.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.14.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.15.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.16.2x.xx | No | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.8x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.9x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.19.xx.xx | Yes | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.23.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.60.xx.xx | Yes | Yes | No | Yes | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |7.10.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |7.15.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |7.30.xx.xx | No | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |7.36.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |7.50.xx.xx | Yes | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |7.60.xx.xx | Yes | Yes | No | No | Yes | Yes | --------------------------------------------------------------------- ------------------------------------------------------------ | Controller |EXP Storage Expansion | | FW Version |Enclosures | | |----------------------|----------------------| | | EXP520 | EXP5000 | EXP395 | EXP5060 | |------------|---------|------------|---------|------------| |7.30.xx.xx | No | Yes | No | No | |------------|---------|------------|---------|------------| |7.36.xx.xx | No | Yes | No | No | |------------|---------|------------|---------|------------| |7.50.xx.xx | No | Yes | No | No | |------------|---------|------------|---------|------------| |7.60.xx.xx | Yes | Yes | Yes | Yes | ------------------------------------------------------------ Note: EXP500 and EXP710/EXP100 can not be attached behind the same DS4000 storage subsystem. In addition, the EXP500 can only be intermixed with EXP700 if the fibre channel speed of the EXP700 and the DS4000 subsystem drive loop is set to 1Gbps. ======================================================================= 1.2 Known Issues/Limitations ----------------------------------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by the 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. 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. New limitations with Storage Manager version 10.70.xx.10 release (controller firmware 07.70.xx.xx). 1. An IBM RPQ is required for Novell Netware host attachment to IBM DS4000/DS5000 Controller Subsystems with Firmware v07.60.xx.xx and higher. Please contact your IBM Marketing Representative or IBM Reseller for information on available Novell Netware host support with Controller Subsystem Firmware v07.60.xx.xx or higher. Novell host attachment is supported with controller firmware version 7.50.xx.xx and earlier. 2. Storage Manager “Error 1000 - Could not communicate with the storage...." can occur when actions such as clearing the configuration on a large system (i.e. 448 drives with a DS5300). The Storage Manager has a 120 second timeout and retries 2 more times when retrieving status. Some actions such as this may take 8 minutes or longer. 3. Array Management Window shows 2048 volume copies allowed when only 2047 maximum volume copies can be created. For a given array, at least one source volume will be present for the volume copy feature; hence, the actual number of “copy relationships” is one less than the maximum volume allowed. 4. FDE Drive in “Security Locked” state is reported as “incompatible” state in the drive profile. The drive can be recovered by importing the correct lock key. 5. Deselecting product components using keyboard when installing Storage Manager still installs them. You will have to use mouse for individual component selection. New limitations with Storage Manager version 10.60.xx.17 release (controller firmware 07.60.xx.xx). 1. This version of the Storage Manager installation package includes the IBM Storage Manager Profiler. This is also referred to as Support Monitor in some of the IBM publications. The following system restrictions apply: Note: Do not use laptops or I/O-attached hosts for installing the IBM Storage Manager Profiler unless these items fulfill all of the following requirements. 1. Minimum 1GB memory, 1.5 GB preferred 2. Minimum 1GB hard drive space, 1.5 GB preferred 3. On average 15 to 20 minutes installation duration 4. Static IP address required 5. The Storage Manager Profiler is installed by default with the IBM DS Storage Manager Install Anywhere (SMIA) package with the Typical (Full Installation) selection. To not install the Storage Manager Profiler, select Custom then deselect Support Monitor. 6. A pre-existing MySQL database on the host must be manually uninstalled before you can install the Storage Manager Profiler. 7. The Storage Manager Profiler installation includes the Apache Tomcat webserver application. Any other pre-existing applications that use Apache Tomcat must be uninstalled before you install the Storage Manager Profiler. 8. Make sure the Storage Manager Profiler directory structure is removed from antivirus and backup applications. 9. MS Internet Explorer and Mozilla Firefox are the only two Web browsers supported with the Storage Manager Profiler client application. 10. By default, the Storage Manager Profiler polls all storage subsystems for storage subsystem support data every day at 2:00am. Ensure that there is not heavy usage of the storage subsystem during this time period. This collection time schedule can be modified to start during the window that the storage subsystem has light usage by pointing your Web browser at http://localhost:9000/ and click on the Calendar icon to schedule the data collection frequencies and time. 11. The Storage Manager Profiler typically takes five minutes to seven minutes to collect data, but the time can increase for larger configurations. There have been exceptional instances where storage arrays took up to 20 minutes to capture the data when capturing the drive information. 12. If you have a large system, gathering support data takes longer, and the compressed files are larger. The Storage Manager Profiler compresses the collection data file to be between 2 MB and 5 MB. 13. Monitor each storage subsystem from one Storage Manager Profiler instance. Gathering data from a storage subsystem with multiple Storage Manager Profiler instances can cause problems. No mechanisms exist that prevent multiple Storage Manager Profiler instances from trying to find data from the same storage subsystem. 14. When multiple Storage Manager instances are installed in the environment, do not define the same storage subsystem twice in the Storage Manager Enterprise Management window. 15. The data collection process of the Storage Manager Profiler is multi- threaded with a polling mechanism in place to find the maximum number of storage subsystems at pre-defined timing intervals. The polling mechanism is not sequential. For example, if the upper limit on the number of storage subsystems from which the Storage Manager Profiler can find data is 20, and 60 storage subsystems are defined, 20 threads are gathered immediately, while the data from the remaining 40 storage subsystems are gathered as resources became available. The Storage Manager Profiler supports at least 10 storage subsystems. 16. The Storage Manager Profiler does not support in-band management of storage subsystems. 2. The online help of the Command Line Interface commands (SMcli commands) incorrectly showed the parameters of certain SMcli commands. The parameters that were shown incorrectly belong to the "disk" type parameter such as Drive, Drivechannels, DiskDrives, repositoryDrives ... These parameters were incorrectly shown with the additional word "disk" such as diskDrive, DiskDriveChannels, repositoryDiskDrive ... The SMcli command syntax checking engine will display the correct syntax for these parameters. Make the modifications as suggested by the SMcli command syntax checking engine. One can also refer to the pdf copy of the Command Line Interface and Script Commands Programming Guide - IBM System Storage DS4200, DS4700, and DS5000 in the IBM DS support web site for help on the SMcli command syntax. 3. The suggested recovery path in the mis-wired guru event might send the user down either the wrong path or very long path when trying to fix the first mis-wired port. The work-around is to use the cabling diagram in the EXP5060 Installation, User's and Maintenance guide or the DS5100 and DS5300 Installation, User's and Maintenance guide publications to fix the cabling mis-wired error. The pdf version of these pubs are available in the IBM DS support web site. 4. An IBM RPQ is required for Novell Netware host attachment to IBM DS4000/DS5000 Controller Subsystems with Firmware v07.60.xx.xx and higher. Please contact your IBM Marketing Representative or IBM Reseller for information on available Novell Netware host support with Controller Subsystem Firmware v07.60.xx.xx or higher. New limitations with Storage Manager version 10.60.xx.17 release (controller firmware 07.60.xx.xx). 1. An IBM RPQ is required for Novell Netware host attachment to IBM DS4000/DS5000 Controller Subsystems with Firmware v07.60.xx.xx and higher. Please contact your IBM Marketing Representative or IBM Reseller for information on available Novell Netware host support with Controller Subsystem Firmware v07.60.xx.xx or higher. 2. Novell Netware Server host attachment to the DS5020 and DS3950 Storage Controller Subsystems is not supported. 3. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. New limitations with Storage Manager version 10.60.xx.11 release (controller firmware 07.60.xx.xx). 1. An IBM RPQ is required for Novell Netware host attachment to IBM DS4000/DS5000 Controller Subsystems with Firmware v07.60.xx.xx and higher. Please contact your IBM Marketing Representative or IBM Reseller for information on available Novell Netware host support with Controller Subsystem Firmware v07.60.xx.xx or higher. 2. Novell Netware Server host attachment to the DS5020 Storage Controller Subsystems is not supported. 3. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. New limitations with Storage Manager Installer (SMIA) package version 10.50.xx.23 release. 1. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. 2. The output of the "list failover devices" command incorrectly lists the Storage Controllers as A/A instead of A/NA. This is a cosmetic issue and does not affect the performance of the Storage Controller. New limitations with Storage Manager Installer (SMIA) package version 10.50.xx.19 release. 1. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. New limitations with Storage Manager Installer (SMIA) package version 10.36.xx.13 release. 1. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. New limitations with Storage Manager Upgrade Utility package version 10.36.xx.07b release (controller firmware 07.36.xx.xx). 1. Upgrade of DS4000 to 7.xx.xx.xx using the upgrade tool with non-English OSes will end with an error. The current firmware column still shows the previous version, pending version will show 7.xx.xx.xx, instead of 'none'. Checking the upgrade tool log you will find: [12.11.2008 08:51:16] [rey-ds4700-1] [SUPPORT_SERVICES] [DownloadAndActivate] activation failed There are two ways to check the content of this log: 1. As long as the upgrade tool is still open: Use the 'View log' button 2. If the upgrade tool was closed already: For windows all logs can be found in this folder: C:\Program Files\IBM_DS4000FirmwareUpgrade\client For other operating systems, check in the appropriate folder. Syntax of the name is similar to 20081114_1501.log. Then check the profile. Here the new firmware can be found as pending: Current configuration: Firmware version: 06.60.17.00 NVSRAM version: N1814D470R916V17.dlp Pending configuration: Staged firmware download supported: Yes Firmware version: 07.36.12.00 NVSRAM version: N1814D47R1036V12.dlp This shows that firmware was loaded to controller but not yet activated. Workaround: After checking the items listed in Details section, activate the loaded firmware using this script command: activate storageSubsystem firmware; Mark the affected system in the Enterprise Management window of the Storage Manager. In the menu, go to Tools -> Execute script. A new window will show up. Paste the command in the upper part of this window and choose Tools -> Execute only. The activation will take a while and the controller will reboot. New limitations with Storage Manager Installer (SMIA) package version 10.36.xx.07 release. 1. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. Limitations with Storage Manager Installer (SMIA) package version 10.30.xx.09 release. 1. Novell Netware Server host attachment to the DS5300 and DS5100 Storage Controller Subsystems is not supported for this release. 2. There is not an IBM System Storage™ DS Storage Manager host software packages for the Novell Netware™ operating system environments. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware™ hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the subsystem out-of-band. Please review the Operating System limitations specific to Windows and Linux. In addition, review the controller firmware readme for limitations specific to the storage subsystem. New limitations with Storage Manager Installer (SMIA) package version 10.15.xx.xx release (controller firmware 07.15.xx.xx). 1. Reconfiguration operation (DRM) is delayed under some circumstances. When a drive fails before the DRM completes, it can take up to eight times as long for the DRM to complete. DRM reconfigurations to RAID 6 have the longest impact since there are four times as many calculations and writes that have to occur compared to other RAID levels. 2. Host Software display of controller current rate is wrong below 4Gbps. Host Software Client - AMW - Logical/Physical View - Controller Properties - Host Interfaces - Current rate is displaying "Not Available" when the controller negotiated speed is 2Gbps. When the controller negotiated speed is reduced to 1GBs, the Current rate displays "2Gbps" New limitations with Storage Manager Installer (SMIA) package version 10.10.xx.xx release (controller firmware 07.10.xx.xx). 1. Controller Alarm Bell icon does not appear as a flashing icon indicator on the screen to get the user's attention but the icon does change appearances. 2. Miswire of drive tray cabling with DS4700 and DS4200 can cause continuous reboot of a controller. To correct this situation, power down the subsystem, cable the drive trays correctly, and power the subsystem back up. 3. Controller button may appeared enabled and mislead the user that a controller is selected where in fact, a controller was not highlighted for the botton to appear ready. 4. Search key is not marked correctly in that page due a JavaHelp Bug with JavaHelp 2.0_01. A search for keyword "profile" ended with phase "prese 'nting p' rofile" being marked. 5. storageArrayProfile.txt should be renamed as storageSubsystemProfile.txt in Support Data. 6. Bullets Incorrectly Placed in Volume Modification Help Page 7. Unable to Escape out of Help Display. User will be required to close the window by using window close procedure (exit, etc.) 8. Bullets and Descriptions not aligned into same line in "Viewing mirror properties". 9. The Help window is not getting refreshed properly when using the AMW.Help window. Workaround is to close and reopen Storage Manager client. 10. CLI command failure for creation of volume(s) if capacity parameter syntax is not specified. A space will need to be used between the integer value and the units used in the capacity option of this command or, "create volume volumeGroup[4] capacity=15 GB…". 11. Customer will see high ITW counts displayed in GUI (RLS feature) and logs (files) for diagnostics (support bundle, DDC, etc.) and may be concerned that he has a problem. This will not cause a Critical MEL event. Known problem previously restricted, when a DS4700 or DS4200 controller reboots, these counters increment. 12. Single tray powercycle during IO activity causes drives in tray to become failed. Customer may see loss of drive (failed) due to timing issue of drive detection & spin-up of the drive. There are one of two conditions that result on power-up: - (Most likely) Drive will be marked as optimal/missing with the piece failed, or - (rarely) Drive will be marked as failed with the piece failed. Workaround is to unfail (revive) drive which restarts reconstruction of all pieces. 13. Event log critical Event 6402 was reported after creating 64 mirror relations. Eventually, the mirror state transitions to synchronizing and proceeds to completion on mirror creation. Workaround is to ignore the MEL logging since this occurs on creation of mirror volumes. 14. Reconfiguration operations during host IO may result in IO errors when arrays contain more than 32 LUNs. These operations include Dynamic Capacity Expansion, Defragmentation, Dynamic Volume Expansion, Dynamic RAID Migration. The workaround is to quiesce host IO activity during reconfiguration. 15. Heavy IO to a narrow volume group of SATA drives can result in host IO timeouts. A narrow volume group refers to an array built of very few drives; namely 1 drive RAID 0, 1x1 RAID 1, and 2 + 1 RAID 5. The workaround is to build arrays of SATA drives out of 4 + 1 or greater. 16. When managing the storage subsystem in-band, the upgrade utility will show the upgrade as failed. This is because of the update and reboot of the controllers when activating the new firmware. SMagent is not dynamic and will need to be restarted to reconnect to the storage subsystem. 17. Selecting and dragging text within the storage profile window causes the window to be continuously refreshed. Work around is to select and copy, do not drag the text. 18. When configuring alerts through the task assistant, the option stays open after selecting OK. The window only closes when the cancel button is selected. 19. The Performance Monitor displays error messages when the storage subsystem is experiencing exception conditions. The performance monitor has a lower execution priority within the controller firmware than responding to system IO and can experience internal timeouts under these conditions. 20. Critical MEL event (6402 - Data on mirrored pair unsynchronized) can occur under certain circumstances with synchronous RVM. The most likely scenario is when both primary and secondary are on a remote mirror and an error occurs with access to that host. Resynchronization should occur automatically, when automatic resynchronization is selected for a mirror relationship. However if any of the host sites should go down during this interval, recovery by the user is required. 21. A persistent miswire condition is erroneously reported through the recovery guru even though the subsystem is properly wired. The frequency of occurrence is low and is associated with an ESM firmware download or other reboot of the ESM. The ESM that is reporting the problem must be reseated to eliminate the false reporting. Not all miswire conditions are erroneous and must be evaluated to determine the nature of the error. 22. Drive path loss of redundancy has been reported during ESM download. This occurs when a drive port is bypassed. In some instances this is persistent until the drive is reconstructed. In other cases it can be recovered through an ESM reboot (second ESM download, ESM pull and replace). 23. Unexpected drive states have been observed during power cycle testing due to internal controller firmware contention when flushing MEL events to disk. The drives have been observed as reconstructing or replaced when they should have been reported as failed. Also volume groups have been reported degraded when all drives were assigned and optimal. An indication that this is the situation would be when drive reconstruction has not completed in the expected amount of time and does not appear to be making any progress. The work around is to reboot the controller owning the volume where the reconstruction has stalled. 24. Sometimes when an ESM is inserted a drive's fault line is asserted briefly. The fault line almost immediately returns to inactive, but the ESMs may bypass the drive. In these circumstances, the administrator will have to reconstruct the failed drive. 25. After a drive fail, a manually initiated copyback to a global hot spare may also fail. The work around is to remove the failed drive and reinsert it, then the copyback should resume and complete successfully. 26. When an erroneous miswire condition occurs (as mentioned above in 21), the recovery guru reports the miswire on one controller but not on the other. In this situation, ignore the other controller and use the information supplied by the controller reporting the problem. 27. Occasionally a controller firmware upgrade to 07.10 will unexpectedly reboot a controller an extra time. This could generate a diagnostic data capture, however the firmware upgrade is always successfull. 28. When managing previous releases of firmware (06.19 and prior), "working" gets displayed as "worki" during volume creation. 29. The Performance Monitor error window does not come to the front. You must minimize all other foreground windows to get to the error popup window. 30. When a disk array is in a degraded state, the array will report "needs attention" to both the EMW and the AMW. After taking appropriate corrective action, the AMW view of the array will report "fixing" but the EMW state remains at "needs attention". Both statuses are valid, when the fault state is resolved both views will change to "optimal". 31. Manual LUN path transfer of one LUN to its alternate path using nssmu causes all LUNs on the receiving controller to be automatically transferred to their alternate path. Use Storage Manager client to change the LUN ownership instead of Netware nssmu. 32. Configuring separate Email alerts when two Enterprise management windows are open on the same host will cause the alerts to disappear if one of the Enterprise windows is shut down and then restarted. It is recommended that if multiple Enterprise management windows needs to be open, that they are open on separate Hosts which will indeed allow the configuration of alerts to be saved if one of the enterprise management windows is shut down and restarted. Legacy restrictions that are still applicable: 1. Reflected Fibre Channel (FC) OPN frames occurs when intermixing the EXP810, EXP710 and EXP100s behind DS4700 or DS4800 storage subsystems. This behavior causes excessive drive side timeout, drive side link down and drive side link up events be posted in the DS4000 storage subsystem Event log (MEL.) It might also cause drives to be by-passed or failed by the controller. NEW DRIVE SIDE FC CABLING REQUIREMENT MUST BE ADHERED TO WHEN HAVING EXP100 CONNECTED TO THE DS4700 OR DS4800 STORAGE SUBSYSTEMS. Please refer to the latest version of the Installation, User's and Maintenance Guide for these storage subsystems that are posted in the IBM DS4000 Support web site for more information. http://www.ibm.com/systems/support/storage/disk 2. Can not increase the capacity of RAID arrays. RAID arrays with certain combinations of selected segment size and number of drives that made up the arrays will exceed the available working space in controller dacstore, causing a reconfiguration request (like expanding the capacity of the array) to be denied. These combinations are generally the largest segment size (512KB) with the number of drives in the array is 15 drives or more. There is no work-around. C324144 105008 3. Interoperability problem between the Tachyon DX2 chip in the DS4500 and the DS4300 storage subsystem controllers and the Emulex SOC 422 chip in the EXP810 expansion enclosure ESMs causing up to 5 Fibre Channel loop type errors to be posted in the DS4000 storage subsystem Major Event Log during a 24 hour period. There is a small window in the SOC 422 chip that multiple devices can be opened at one time. This ultimately leads to Fibre Channel loop errors of Fibre Channel link up/down, Drive returned CHECK CONDITION, and Timeout on drive side of controller. IBM recommends the use of the Read-Link-Status function to monitor drive loop for any problems in the drive loop/channel. There is no work-around. 4. The single digit of the Enclosure IDs for all enclosures (including the DS4000 storage subsystem with internal drive slots) in a given redundant drive loop/channel pair must be unique. For example, with four enclosures attached to the DS4300, the correct enclosure ID settings should be x1, x2, x3, and x4 (where x can be any digit that can be set). Examples of incorrect settings would be 11, 21, 31, and 41 or 12, 22, 32, and 62. These examples are incorrect because the x1 digits are the same in all enclosure IDs (either 1 or 2). If you do not set the single digit of the enclosure IDs to be unique among enclosures in a redundant drive loop/channel pair, then drive loop/channel errors might be randomly posted in the DS4000 subsystem Major Event Log (MEL), especially in the cases where the DS4300 storage subsystems are connected to EXP810s and EXP100s. In additon, enclosure IDs with same single digits in a redundant drive loop/channel pair will cause the DS4000 subsystem controller to assign a soft AL_PA address to devices in the redundant drive loop/channel pair. The problem with soft AL_PA addressing is that AL_PA address assignment can change between LIPs. This possibility increases the difficulty of troubleshooting drive loop problems because it is difficult to ascertain whether the same device with a different address or a different device might be causing a problem. 5. In DS4000 storage subsystem configurations with controller firmware 6.15.2x.xx and higher installed, the performance of write intense workloads such as sequential Tape restores to DS4000 Logical drives with large I/O request sizes (e.g. 256kB) is degraded if the DS4000 logical drives are created with small segment sizes such as 8KB or 16KB. The work around is to create the DS4000 logical drives with segment size of 64KB or higher. 6. Do not pull or insert drives during the drive firmware download. In addition, ALL I/Os must also be stopped during the drive firmware download. Otherwise, drives may be shown as missing, unavailable or failed. 7. Do not perform other storage management tasks, such as creating or deleting logical drives, reconstructing arrays, and so on, while downloading the DS4000 storage subsystem controller firmware and DS4000 EXP ESM firmware. It is recommended that you close all storage management sessions (other than the session that you use to upgrade the firmware) to the DS4000 storage subsystem that you plan to update. ======================================================================= 1.3 Enhancements --------------------------- There is not any enhancements for this release Storage Manager 10.70 for Novell Netware. Controller firmware 7.70.xx.xx is not supported in environment with Netware host attachments. Please refer to the New Features section of the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide for additional information about the IBM DS Storage Manager version 10 enhancements. ======================================================================= 1.4 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- 1. Netware 6.5 with support pack 8 or higher. 2. "Direct connection of the DS4300 to a host system running Microsoft Windows, Novell NetWare or x86 Linux is only supported using the IBM DS4000 FC2-133 Host Bus Adapter (HBA), IBM option part number 24P0960 or feature code 2104 with the last 6 digits of the 13 digit serial number of the HBA is H21160 or higher. For example, if the serial number is FFC0308H21161, the last 6 digits will be H21161, which indicates that this HBA meets the DS4300 direct connect prerequisite. In addition, direct connect to the NAS 300G (Machine Type 5196) Model G27 or Model G02 containing Feature Code 3706 is only supported if the last 6 digits of the 13 digit serial number of the HBA is above H21160. 3. Novell server with at least 2G of memory. Code levels at the time of release are as follows ------------------------------------------------------------------ IMPORTANT: Starting with the DS4000 Storage Manager version 9.16 release, there are not any IBM System Storage™ DS Storage Manager host software packages for the Novell Netware server operating system environment. To manage the DS4000/DS5000 storage subsystems that are IO attached to your Novell Netware server hosts, you must install the DS Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the DS4000/DS5000 storage subsystem via out- of-band management method. The SMclient program is included in the IBM System Storage™ DS Storage Manager version 10.70 for the 32 and 64 bit version of Linux operating systems or the IBM System Storage™ DS Storage Manager version 10.70 for Microsoft Windows operating systems host software packages. These IBM System Storage™ DS Storage Manager version 10.70 host software packages for Windows and Linux and DS4000/DS5000 storage subsystem firmware files are available for download from the IBM System Storage™ Disk Storage Systems Technical Support web site - http://www.ibm.com/systems/support/storage/disk. 1. For Microsoft Windows, the IBM DS Storage Manager Installer wizard version is 10.70.x5.25. SMIA-WS32-10.70.35.25.exe 2. For Linux, the DS Storage Manager Installer wizard version is 10.70.A5.25. SMIA-LINUX-10.70.A5.25.bin The storage Manager client and runtime programs are also available as individual host software packages. Refer to the http://www.ibm.com/systems/support/storage/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the latest supported host adapters, device drivers, and updated readme. Please also review section 2.2 in this README file. ======================================================================= 1.5 Dependencies -------------------------- 1. The IBM System Storage DS4000 Controller Firmware Upgrade Tool is required to upgrade any system from 6.xx controller firmware to the 7.50.xx.xx controller firmware. This tool has been integrated into Enterprise Management Window of the DS Storage Manager v10.70 Client. 2. 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 drive expansion enclosure ESM, the DS4000 storage subsystem controller and the hard drive firmware. 3. The DS5100 and DS5300 storage subsystems do not support the attachment of the DS4000 EXP100, EXP700, EXP710, or EXP420 drive expansion enclosures. EXP810 enclosure support by RPQ only. 4. The DS5000 EXP5000 drive expansion enclosure is supported attached to the DS5100 and DS5300 only. 5. 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. 6. Standard installation order for Storage Manager 10.70.xx.xx and controller firmware 07.x0.xx.xx: 1. SMruntime - always first 2. SMesm - required by client 3. SMclient 4. SMagent 5. SMutil 6. Controller firmware and NVSRAM 7. ESM firmware 8. Drive firmware 7. Automatic Logical Drive Transfer (ADT/AVT) must be disable for the new Novell Netware 6.5 native multipath driver. The version and release dates of the new driver modules are as follows (or later): a. MM.NLM - NetWare 6.5 Media Manager Version 3.22 April 4, 2006 b. NWPA.NLM - NetWare 6.5 NetWare Peripheral Architecture NLM Version 3.21 March 27, 2006 c. SCSIHD.CDM - Novell NetWare SCSI Fixed Disk Custom Device Module Version 3.03.06 March 29, 2006 d. LSIMPE.CDM - LSI Multipath Enhancer Version 1.02.04 Do not use any of the above modules whose release dates and versions are earlier than as stated above. Furthermore, newer version of these Novell NetWare 6.5 CDM and NLM modules might also be available in the Novell support web site. IBM recommends using the newer versions of these NetWare 6.5 CDM and NLM modules when they are available from the Novell support web site or NetWare 6.5 support packs. IBM DS Storage Manager version 10.70 host software requires the DS4000/DS5000 storage subsystem controller firmware be at version 05.40.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. ======================================================================= 2.0 Installation and Setup Instructions ---------------------------------------------------- Note: Refer to the Windows or Linux Storage Manager 10 packages as appropriate for installing host software on those systems. 2.1 Refer to the Host_Adapter directory on this installation CD for the applicable drivers or refer to the IBM Support Web Site for the latest supported host adapters, device drivers, and updated readme. At this time, the supported drivers are as follows: 1. IBM DS4000 Host Adapter device driver for NetWare version 7.00a for IBM DS4000/FAStT FC2, FC2-133 single and dual port and FC 4Gbps single and dual port FC HBAs 2. Novell NetWare native multipath/failover driver DO NOT USE THE NOVELL MULTIPATH DRIVER MODULES THAT ARE AVAILABLE WITH NetWare 6.5 SUPPORT PACK 5 OR EARLIER. There is a fix to the "LUN bouncing between controllers" problem in NetWare 6.5 SP5 and earlier with the IBM DS4000 storage subsystems. The problem was observed in large (>6 nodes) NetWare 6.5 cluster with cluster nodes sharing the same IBM DS4000 storage subsystem LUNs and being configured with the NetWare native multipath driver. When the nodes in the clusters scan all available Fibre Channel paths to discover LUNs as part of a server boot up process or as the result of executing "scan all LUNs", "scan for new devices" or "list failover devices" commands, the DS4000 storage subsystem LUNs will moved between controller A and B momentary. In certain cases, this "LUN bouncing between controllers" behavior could cause the server to mark all paths to a LUN as failed and deactivate it. The fixes required new version of the following Novell NetWare 6.5 CDM and NLM modules. The version and released date of the CDM and NLM modules that these fixes were first incorporated into were as follows: a. MM.NLM - NetWare 6.5 Media Manager Version 3.22 April 4, 2006 b. NWPA.NLM - NetWare 6.5 NetWare Peripheral Architecture NLM Version 3.21 March 27, 2006 c. SCSIHD.CDM - Novell NetWare SCSI Fixed Disk Custom Device Module Version 3.03.06 March 29, 2006 d. LSIMPE.CDM - LSI Multipath Enhancer Version 1.02.04 These files can be downloaded from the Novell support web site - http://support.novell.com/cgi-bin/search/searchtid.cgi?/2973674.htm. Do not use any of the above modules whose release dates and versions are earlier than as stated above. Furthermore, newer version of these Novell NetWare 6.5 CDM and NLM modules might also be available in the Novell support web site. IBM recommends using the newer versions of these NetWare 6.5 CDM and NLM modules when they are available from the Novell support web site or NetWare 6.5 support packs. In addition, the new Novell NetWare 6.5 native multipath driver requires the Automatic Logical Drive Transfer (ADT, aka. Automatic Volume Transfer (AVT)) mode/function to be disable. The ADT/AVT mode/function must be enable for previous version of LSIMPE.CDM, SCSIHD.CDM, MM.NLM and NWPA.NLM. It must be disabled for the stated above release dates and versions of LSIMPE.CDM, SCSIHD.CDM, MM.NLM and NWPA.NLM modules. To disable the AVT/ADT function so that the new Novell native multipath driver can be used, you must run the DS4000 "DisableAVT_Netware.script" SMcli script file. This file is placed in the script folder of the CD-ROM or the DS4000 storage manager host software package for Novell NetWare. Attention: If you do not install NetWare 6.5, or if you use an older version of the Novell native multipath driver in NetWare 6.5, do not load the new DS4000 NVRAM file that disable AVT/ADT. NetWare hosts with the new Novell native multipath driver (NetWare 6.5) and the previous Novell native multipath driver (NetWare 6.0, or NetWare 6.5 without the new native multipath driver installed) cannot share the same DS4000 storage subsystem using the same NetWare failover host type. This is because the different ADT/AVT enable/disable settings of the different Novell native multipath driver versions conflict with each other. Recommendation: If your system has NetWare version 6.0 (or earlier) installed, it is recommended that you upgrade to NetWare 6.5 to take advantage of this new Novell multipath driver. Always check the Novell support web site for the latest version of the LSIMPE.CDM. In some cases, the IBM Support web site for DS4000 product will have the LSIMPE.CDM that one should use until Novell releases the new maintenance pack that incorporates changes between Novell NetWare schedule maintenance releases. Check the README that is included in the DS4000 Storage Manager version 9 host software package for Novell NetWare OS for more info. IMPORTANT: The IBMSAN.CDM version 106e dated November 4th, 2002 is not supported for NW6 SP3 or later and for NW6.5. In addition, this driver will not recognize LUNs from the DS4100, DS4700 and DS4800 storage subsystems. This driver is for NW 6 SP2 and earlier and NW 5.1 SP6 only. ======================================================================= 2.3 Helpful Hints ------------------ 1. The DS4500 and DS4300 storage subsystem have updated recommended drive-side cabling instructions. 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 minuhub 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. The DS4000 Storage Management dialog windows may be displayed cropped without the vertical and horizontal scroll bars. Just move the mouse pointer over the edge of the window until the mouse pointer change to window resize pointer, left click and hold to grip the window edge to resize it. 3. 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. Depending on the storage subsystem that you have purchased, you may have to purchase the DS4000 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 DS4000 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 DS4300 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 (machine type 3542): The standard configuration has 16 partition storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM FAStT500 and DS4400 storage subsystems (machine type 3552 and 1742 - models 1RU and 1RX, respectively): The standard configuration has 64 partition 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 or 64 storage partitions. Similarly, the DS4700-model 72 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the DS4700 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 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 or 64 storage partitions. If the subsystem is ordered with less than 64 partitions, an upgrade from 8 to 16, 8 to 64 or 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. 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. 6. When making serial connections to the DS4000 storage controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the DS4000 storage subsystem serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 7. 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. 8. 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. 9. IBM recommends at least one hot spare per EXP100 drive expansion enclosure. A total of 15 hot-spares can be defined per DS4000 storage subsystem configuration. 10. Starting with the DS4000 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 10 client program does not automatically map logical drives when the IBM DS4000/DS5000 storage partitioning premium feature is enabled. This means that the logical drives after being created are not automatically presented to the host systems. a. For a new installation, after creating new arrays and logical drives, create a storage partition with the host type of Netware-failover (when using the Novell native fail-over driver) or Netware-IBMSAN (when using the IBMSAN fail-over driver) 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. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815, 1818 or 3552 storage subsystems in clustered Remote Mirror configurations, contact IBM support for supported cluster configurations and instructions for configuring IBM storage controllers in clustered Remote Mirror configurations. 4. 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_Netware.script: The script will enable automatic logical drive transfer (AVT) for the Netware Failover heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Netware.script: The script will disable the automatic logical drive transfer (AVT) for the Netware Failover heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. ======================================================================= 3.2 Hardware status and information -------------------------------------------------- For more information, refer to the IBM System Storage™ Disk Storage Systems Technical Support web site. ======================================================================= 3.3 Unsupported configurations ------------------------------------------- The following lists configurations that are currently not being supported with IBM DS4000 Storage Manager Version 10.70. 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 host bus adapter connects directly to any DS4000 storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC host bus adapter connects to both controller ports of any DS4000 storage subsystem with dual controllers via Fibre Channel (FC) switch (SAN-attached configuration.) ======================================================================= 4.0 Unattended Mode -------------------------------- None. ======================================================================= 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 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: www.ibm.com/systems/support/storage/subscribe/moreinfo.html 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 FAStT System Storage™ the e-business logo xSeries HelpCenter Linux is a registered trademark of Linus Torvalds. 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. Netware is a registered trademark of Novell Other company, product, and 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.