IBM TotalStorage SAN Volume Controller ++++++++++++++++++++++++++++++++++++++ ---------------------------------------------------------------------------- CONTENTS 1. Introduction 2. Available education. 3. Pre-Requisites 4. Code Levels 5. Installation Instructions 6. Further Documentation 7. Known issues and restrictions in this level 8. Maximum configurations. 9. Problems resolved in this build. ---------------------------------------------------------------------------- 1. INTRODUCTION This document describes how to install version 1.2.1.1 of the IBM TotalStorage SAN Volume Controller (2145) software. This release of software is a new release and adds features as detailed in section 9. Please refer to the Supported Software List and Supported Hardware List on the support website: http://www.ibm.com/storage/support/2145. This provides important information on the pre-requisites for this code level. --------------------------------------------------------------------------- 2. Available education A course on SAN Volume Controller Planning and Implementation is available. For further information or enrolment, contact your local IBM representative. --------------------------------------------------------------------------- 3. Pre-Requisites Before installing this code level please check the following pre-requisites are met. Also please note the concurrent upgrade (upgrade with IO running) restrictions. This may apply if you have not upgraded the base code since adding new SVC nodes. Check there are no errors in the error log or the front panel, use normal service procedures to resolve these errors before proceeding. If this is the first 1.2.1.x level build you are installing it is very important that you upgrade the SVC Console Code (GUI) after you install the SVC code. See the support website http://www.ibm.com/storage/support/2145 for more details. The 2145 or 2146 must be at a release level of 1.1.0.0 (0.13.03070300), 1.1.0.1 (0.14.0308070000), 1.1.1.0 (0.32.0311060000), 1.1.1.1 (0.33.0311250000), 1.1.1.2 (0.33.0401010000), 1.1.1.3 (0.33.0402160000), 1.2.0.0 (0.53.0404190000), 1.2.0.1 (0.53.0405060000), 1.2.0.2 (0.54.0406170000) or 1.2.1.0 (1.21.0410150000) for these clusters to be upgraded with no loss of data or configuration. For existing clusters please check which level your cluster is running before proceeding - Use "Displaying cluster properties using the SAN Volume Controller Console" in chapter 11 (Overview of creating a cluster using the SAN Volume Controller Console) of the Configuration guide to do this and look for the "code version". If your cluster is at one of these levels then please follow the upgrade instructions as given in Chapter 22 (Upgrading the SAN Volume Controller firmware using the SAN Volume Controller Console) of the Configuration Guide. If your cluster is not at one of these levels please contact IBM Support. This procedure takes you through the concurrent code load process, it will keep the SAN Volume Controller configuration and preserve all data virtualized by the cluster. If your cluster is running 1.1.0.0 (0.13.03070300) or 1.1.0.1 (0.14.0308070000) AND you have added new nodes or replaced existing ones in the cluster then please read the restriction below. If you are installing a new 2145 then you will need to follow the procedure shown below in section 6. This will upgrade the SVC's to the 1.2.1.1 level before the cluster is configured for use. Please note the warning at the beginning of the process and only proceed if you are sure there is no data on this machine. NOTE: CONCURRENT UPGRADE RESTRICTION If you are adding new nodes (running the latest manufacturing code) to an existing cluster running 1.1.0.0 or 1.1.0.1 level code it is possible you will notice I/O errors on AIX hosts when upgrading the code. This problem is introduced when a node that has 1.1.1.x or 1.2.x.x code installed is added to a cluster running 1.1.0.0 or 1.1.0.1. The node being added is downgraded to the level the cluster is running. When this cluster is upgraded to 1.1.1.x or 1.2.x.x the node or nodes that were added may produce IO errors. Simply quiescing I/O is not sufficient - filesystems will need to be unmounted so that SDD reports the paths as closed. You can alternatively delete vdisk to AIX host mappings prior to the upgrade and re-establish them afterwards. This problem will only happen with nodes that have been downgraded from 1.1.1.0 and are then upgraded to 1.1.1.x or 1.2.x.x --------------------------------------------------------------------------- 4. CODE LEVELS 2145 Software: 2145 Release Level 1.2.1.1 (1.21.0411190000) ---------------------------------------------------------------------------- 5. INSTALLATION INSTRUCTIONS $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ NOTE: This procedure will destroy any existing data or configuration. If you wish to preserve the SVC configuration and all data virtualized by the cluster then please follow the upgrade instructions given in Chapter 22 of the Configuration Guide. $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ * This procedure is for new installations only. Please read the introduction again to make sure you understand which procedure you wish to use. * Follow the instructions in chapter 11 (Overview of creating a cluster using the SAN Volume Controller Console) of the Configuration Guide in order to create a cluster on ONLY the first node. Do not add the other nodes at this point. * Use "Displaying cluster properties using the SAN Volume Controller Console" in chapter 11 of the Configuration guide to display the "code version". If it shows 1.2.1.1 (1.21.0411190000) then you do not need to perform any further actions. Continue to add nodes and configure your cluster as described in the configuration guide. If the reported version is 1.1.0.x, 1.1.1.0, 1.1.1.1, 1.1.1.2, 1.1.1.3, 1.2.0.0, 1.2.0.1, 1.2.0.2 or 1.2.1.0 then continue to follow this procedure. * Ensure that you have set a unique IP address for service mode. * Put the node into Service Mode (See "Service access navigation" described in Chapter 5 (Using the front panel of the SAN Volume Controller) of the Service Guide) 1. On the front panel, navigate to the 'Cluster' main field and then left to the 'Recover Cluster?' secondary field. 2. Press 'Select'. The screen should now say 'Service Access?' 3. Press and hold the 'Down' button. 4. Press and release the 'Select' button. 5. Release the 'Down' button. The node will restart and display the Service IP address. The front panel buttons are disabled whilst in this state. * Apply the upgrade package. 1. Follow the instructions in chapter 22 of the Configuration Guide to install the IBM2145_INSTALL_1.2.1.1 package. Note: At step 4 of the instructions, ensure you select the option to 'Skip prerequisite checking'. * Once upgraded, recreate the cluster on the node, instructions are in chapter 11 (Overview of creating a cluster using the SAN Volume Controller Console) of the Configuration Guide. You can now add the other nodes to the cluster and they will automatically be upgraded to 1.2.1.1 (1.21.0411190000). * After this process is complete, check that the software version number is 1.2.1.1 (1.21.0411190000) on the Cluster Properties panel as described in chapter 11 of the Configuration Guide. ---------------------------------------------------------------------------- 6. FURTHER DOCUMENTATION The following publications may be downloaded from http://www.ibm.com/storage/support/2145 Under 'Documentation'. - 2145 Command-Line Interface User's Guide - 2145 Planning Guide - 2145 Host Systems Attachment Guide - 2145 Installation and Hardware Reference Guide - 2145 Configuration Guide The website also includes hints and tips and other useful information you may wish to review. ---------------------------------------------------------------------------- 7. Known Issues with this build. The current product limitations can be found in the restrictions document, published on the support website http://www.ibm.com/storage/support/2145. ---------------------------------------------------------------------------- 8. Maximum configurations. The following lists show the maximum resources configurable in this release (maximum cluster size) VDisks Maximum number/cluster 4096 Maximum number per IO group 1024 Maximum size 2 TB (Linux & AIX 5.1: 1 TB) Maximum SCSI mappings/cluster 20 K Maximum SCSI mappings/host 512 Maximum VDisk Paths/host 8 (separately zoned Host Port to Node Port) MDisks Maximum number/cluster 4096 Maximum extents/cluster 4 M ( 2^22 = 4194304) Maximum Mdisk Groups/cluster 128 Hosts Maximum number/cluster 64 Maximum Host WWPNS/cluster 128 Maximum HBA Ports/host 4 Fabric Maximum SAN Ports/fabric 256 Maximum Clusters/fabric 2 Maximum Nodes/cluster 8 Storage Maximum Controllers/cluster 64 Maximum Controller Ports/cluster 128 Flash Copy Maximum number of Consistency Groups 128 Maximum concurrent Flash Copies 50% VDisks to 50% VDisks Maximum number of mappings per consistency group : 512 Remote Copy Maximum number of Consistency Groups 256 Maximum concurrent Remote Copies 1024 Data Migration Maximum concurrent Data Migrations 32 Persistent Reservations Maximum Registrations/cluster 132 K ---------------------------------------------------------------------------- 9. New features in this build EMC CX 300/500/700 Support added. APAR's resolved in this release; APAR DEFECT IC43471 Assert due to reserve being processed after vdisk delete Other defects resolved in this build that are not related to specific APARS DEFECT MDiskgrp restore object names corruption fix Improve Config backup CRON job diagnosis. Remove HL tracing to improve latency Cluster 900 fixes Flash Copy/HL assert fix Remote copy fibre failover fixes CSM performance fix Backup restore File permissions change Please refer to the support website http://www.ibm.com/storage/support/2145 for more information on supported hardware, software and product restrictions.