IBM System Storage SAN Volume Controller ++++++++++++++++++++++++++++++++++++++++ ------------------------------------------------------------------------------- CONTENTS 1. Introduction 2. Available Education 3. Pre-Requisites 4. Code Levels 5. Problems Resolved and New Features in this Build 6. Installation Instructions for New Clusters 7. Further Documentation 8. Known Issues and Restrictions in this Level 9. Maximum Configurations ------------------------------------------------------------------------------- 1. Introduction This document describes how to install version 4.1.1.3 of the IBM System Storage SAN Volume Controller (2145) software. This release of software is a service release, it addresses a number of APARs as detailed in Section 5 Please refer to the Recommended Software List and Supported Hardware List on the support website: http://www.ibm.com/storage/support/2145. ------------------------------------------------------------------------------- 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 I/O running) restrictions. Check there are no unfixed errors in the error log or on the front panel. Use normal service procedures to resolve these errors before proceeding. If you are upgrading from a code level below 4.1.1.0, it is important that you upgrade the SVC Console Code (GUI) before you install the SVC code. The latest level of the GUI (4.1.1.543 or later) is available from the same website as this code. SVCC 4.1.1.543 is not fully compatible with SVC versions earlier than 4.1.1.0. Therefore the new SVC Console should only be used with SVC clusters running previous versions of SVC code in order to upgrade to SVC V4.1.1.x. Please see the details in the download document for the SVC Console for more details. Only existing clusters at SVC 3.1.0.5 and 4.1.x.x can be concurrently upgraded to SVC 4.1.1.3. For existing clusters please check which level your cluster is currently running before proceeding. Refer to the Configuration Guide (v4.1.0) - Chapter 3 ("Using SAN Volume Controller Console"), section "Viewing Cluster Properties" to determine how to identify the code level currently installed on your cluster (Look for "Code Version"). If your cluster is at 3.1.0.5 or higher then please follow the upgrade instructions given in the Configuration Guide (v4.1.0) - Chapter 6 ("Upgrading the SAN Volume Controller software"), section "Upgrading the SAN Volume Controller software using the SAN Volume Controller Console". If you are running a version of SVC software older than 3.1.0.5 then you will have to perform multiple upgrades to install SVC 4.1.1 concurrently on your cluster. Please see the following web page for the full upgrade compatibility matrix. http://www.ibm.com/storage/support/software/sanvc/code If you are installing a new SVC Cluster then you will need to follow the procedure in section 6. This will upgrade the SVC cluster to the 4.1.1.3 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 cluster. ------------------------------------------------------------------------------- 4. Code Levels 2145 Software: 2145 Release Level 4.1.1.3 (5.15.0702010000) ------------------------------------------------------------------------------- 5. Problems Resolved and New Features in this Build New Features in SVC 4.1.1 Global Mirror (Asynchronous Replication) The V4.1.x Configuration Requirements and Guidelines document contains information on SVC Global Mirror. If you intend to use SVC Global Mirror, it is particularly important to read this document. DHCP available for the service mode IP address New Service features in SVC V4.1.1.x PTFs SVC V4.1.1.2 adds support for a new revision of the 2145-8F4 hardware platform. Please see the following flash for more details: http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1003028 New Features in SVC 4.1.0 Audit Logging Support for 4Gb/s SANs Support for new Operating Systems and Storage Controllers Support non-disruptive upgrade from 4F2 to 8F2 or 8F4 node types. New statistics for performance monitoring. Host access by port. APARs resolved in this release (4.1.1.3): Critical Fixes IC50888 All nodes lease expire due to failing FC switch port IC51142 SVC node asserts when creating a vdisk if the cluster is close to the virtualisation limit IC51503 SVC node asserts when running svcinfo commands during SVC upgrade IC51567 SVC Cluster Error 1001 when deleting a host object with more than 32 vdisks mapped to it IC51654 Potential loss of cache data during a UPS input power failure if using two 2145-4F2s on a 2145UPS (2U) High Importance Fixes IC51353 SVC node assert when receiving enexpected status response from storage controller IC51381 SVC node assert when using FlashCopy mapping with source and target vdisks in different IO groups IC51452 SVC node assert when copying files between SVC nodes IC51480 SVC node assert when experiencing excessive latency on Global Mirror inter-cluster link. IC51292 AIX hosts may write data to the wrong vdisk when changing existing vdisk-host mappings under IO. Suggested Fixes IC50134 SVC 8Fx node erroneously logs cluster error 1400 for working ethernet links IC50497 SVC Nm statistics include entries for mdisks which do not exist IC51249 SVC 8Fx node erroneously logs cluster errors 1100 or 1105 (system voltage errors) APARs fixed in previous releases: 4.1.1.2 NONE 4.1.1.1 IC49295 Node assert due to timing window in Metro Mirror IC49951 Improved cache destaging algorithm IC49952 New 3000/3001 error codes for high UPS temperature IC50470 Node assert due to SCSI Reserve activity during Flash Copy prepare IC50710 Incorrectly formatted 'v_stats' files IC50748 Node assert caused by fabric instability IC50835 Allow SVC quorum disks on StorageTeK FlexLine controllers IC50862 Allow storage controllers to reuse LUN UIDs IC50945 Single node assert IC50962 Automated T3 recovery fix IC51024 Node assert caused by fabric instability 4.1.0.3 IC50120 Node asserts during Metro Mirror background copy IC50195 Node assert when upgrading from V3.1 to V4.1 if LUN 0x5555 is present IC50298 Fenced adapter on DS8000 can result in mdiskgroups offline IC50300 Node asserts from “duplicate” WWPN login from same host HBA with different WWNN and fcid. IC50307 Problem upgrading from SVC V3.1 to V4.1 when using a storage controller with 8 FC ports IC50333 Node asserts due to multiple Target Resets from hosts IC50419 Node asserts during Metro Mirror IC50711 Improvements to 2145-UPS (2U) error handling 4.1.0.2 IC49635 Node assert when deleting a vdiskhostmap whilst the vdisk is under I/O IC50277 Node assert when backing out of an upgrade to SVC 4.1 4.1.0.1 IC43267 SVC Did not reliably identify an intermittently failing Fibre port IC46303 Node assert caused by corrupted cache control blocks IC47469 Persistent reserves not removed after vdiskhostmap is deleted IC47811 Mdisks become degraded if nodes are added to and then removed from a cluster with no storage mapped IC47977 Incomplete SNMP trap data sent for 1195 error IC48372 Single-fabric SAN disruption resulted in multiple node asserts IC48591 Node assert caused by running svcinfo lsvdisk with illegal filter arguments IC48627 Illegal SCSI read capacity call caused node assert IC48710 Failure to gracefully handle memory failure during SVC code upgrade IC48756 Single SAN disruption causes Lease Expiry IC48878 Persistent reserves cause a node assert following IO group outage IC48990 SVC core dump when shutting down node IC49105 Force deleting a vdisk in an active FlashCopy mapping causes Node Error 900 IC49365 Changing cluster name when in a Remote Cluster partnership causes node assert. IC49447 Allow SCSI port type 0x7F logins to SVC IC49535 Node assert relating to host IO group mappings IC49631 Config restore failure when renaming a vdisk ------------------------------------------------------------------------------- 6. Installation Instructions For New Clusters $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ NOTE: This procedure will destroy any existing data or configuration. If you wish to preserve the current SVC configuration and all data virtualized by the cluster then please follow the upgrade instructions given in Chapter 6 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 2 ("Creating a SAN Volume Controller cluster) of the Configuration Guide, refer to sections "Creating a cluster from the front panel" and "Creating a cluster using the SAN Volume Controller Console" in order to create a cluster on ONLY the first node. Do not add the other nodes at this point. * Follow the instructions in the section entitled "Viewing Cluster Properties" in chapter 3 ("Using the SAN Volume Controller Console") of the Configuration Guide to display the "code version". If the code version of the cluster is 4.1.1.3 (5.15.0702010000) then you do not need to perform any further actions. Continue to add nodes and configure your cluster as described in the configuration guide. Otherwise, continue to follow this procedure. * Ensure that you have set a unique IP address for service mode on the existing single node cluster. * Put the node in the existing single node cluster into Service Mode (See "Setting Service Mode under "Recover cluster 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. Open a web browser and point it at https:// 2. Enter the admin or service user and password that was configured when you set up the one node Cluster. 3. Click "Upgrade Software" on the left side of the web page. 4. Click the "Upload" button and upload the IBM2145_INSTALL_4.1.1.3 file. 5. Once the upload completes, press the "Continue" button. This will take you to a page with a list of available upgrade packages. 6. Select the File you just uploaded from the list of available software upgrade files, and check the "Skip prerequisite checking" box. Click the "Apply" button. 7. Click the "Confirm" Button. 8. The node will now reboot and apply the new software. Note: If upgrading from 3.1.0.5 or 4.1.0.x to 4.1.1.x then an SVC dump may be generated during this upgrade. This is expected and can be ignored. * Once upgraded, create a new cluster on the recently upgraded node. Instructions for this are in Chapter 2 ("Creating a SAN Volume Controller cluster") of the Configuration Guide. At this point you will have a new one node cluster running 4.1.1.3 code. * After this process is complete, check that the software version number is 4.1.1.3 (5.15.0702010000). * You can now add the other nodes to the cluster and they will automatically be upgraded to 4.1.1.3 (5.15.0702010000). ------------------------------------------------------------------------------- 7. Further Documentation All publications can be downloaded from the support website: http://www.ibm.com/storage/support/2145 ------------------------------------------------------------------------------- 8. Known Issues and Restrictions in this Level The current product limitations are detailed in the product restrictions document available here: http://www.ibm.com/storage/support/2145 Please read all the warnings in section 3 (pre-requisites). During upgrades to SVC 4.1.1.3, information about some objects which exist on the remote cluster will not be available. The affected commands are: svcinfo lsrcrelationship svcinfo lsrcrelationshipcandidate svcinfo lsrcconsistgrp svcinfo lsrcrelationshipprogress Please Read the following flashes before upgrading to SVC V4.1 Stopped Flash Copies May Result in Loss of I/O Access During Code Upgrade http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1002971 Setting an SVC IP Address to a Value Which Includes Unnecessary Leading Zeros Can Cause Loss of Ethernet Access to the SVC Cluster http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1002885 If an SVC Code Upgrade Stalls or Fails then Contact IBM Support for Further Assistance http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1002894 SVC 4.1 introduces new restrictions on the number of SSH connections which SVC will allow. Details can be found here: http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1002896 ------------------------------------------------------------------------------- 9. Maximum Configurations. The Maximum Configurations of SVC are documented in the SVC V4.1.x Configuration Requirements and Guidelines Document which is available from http://www-1.ibm.com/support/docview.wss?rs=591&uid=ssg1S1002858 -------------------------------------------------------------------------------