3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3PAR, Inc. 4209 Technology Drive Fremont, CA 94538 USA Part No.
Revision Notice This is the second release of this manual. A complete revision history is provided at the end of this document. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
PAR AIX 5.3, 6.1, and 7.1 Implementation Guide Table of Contents 1 Introduction 1.1 Supported Configurations 1.2 1.2 InForm OS Upgrade Considerations 1.2 1.3 Audience 1.2 1.4 Related Documentation 1.3 1.5 Organization 1.4 1.6 Typographical Conventions 1.5 1.7 Advisories 1.6 2 Configuring the InServ Storage Server for Fibre Channel 2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X 2.3 2.1.1 Configuring Ports for a Direct Connection 2.3 2.1.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4 Setting Up and Zoning the Fabric 2.8 2.9 2.4.1 Configuration Guidelines For Fabric Vendors 2.4.2 Target Port Limitations and Specifications 2.10 2.4.3 Configuration Diagrams for Zoning 2.11 2.4.3.1 Single Initiator to Single Target Zoning No Fan-In No Fan-Out 2.11 2.4.3.2 Single Initiator to Single Target Zoning with Fan-Out from One InServ Storage Server Port to Multiple Host Server Ports 2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4 Allocating Storage for Access by the AIX Host 4.1 Creating Storage on the InServ 4.1 4.1.1 Creating Virtual Volumes 4.2 4.1.2 Creating Thin Provisioned Volumes 4.3 4.1.3 Exporting LUNs to the Host 4.3 4.2 Exporting VLUNs to the AIX Server 4.4 4.2.1 Restrictions on Volume Size and Number 4.4 4.2.2 Scanning for New Devices on the AIX Host 4.4 5 Removing 3PAR Devices on an AIX Host Server 5.
3PAR AIX 5.3, 6.1, and 7.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1 Introduction In this chapter 1.1 Supported Configurations 1.2 1.4 Related Documentation 1.3 1.5 Organization 1.4 1.6 Typographical Conventions 1.5 1.7 Advisories 1.6 This implementation guide provides information for establishing communications between an InServ® Storage Server and a AIX 7.1, 6.1, and AIX 5.3 platforms.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide REQUIRED: For predictable performance and results with your 3PAR InServ Storage Server, the information in this guide must be used in concert with the documentation set provided by 3PAR for the InServ Storage Server and the documentation provided by the vendor for their respective products. 1.1 Supported Configurations For complete details on supported host configurations, consult the latest 3PAR InForm Configuration Matrix that is available on DCS. 1.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1.5 Organization This guide is organized as follows: ■ Chapter 1, Introduction (this chapter), provides an overview of this guide, including information on audience, related documentation, and typographical conventions. ■ Chapter 2, Configuring the InServ Storage Server for Fibre Channel, provides instructions for connecting the InServ to the AIX Server with a Fibre or iSCSI connection.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1.6 Typographical Conventions This guide uses the following typographical conventions: Typeface Meaning Example ABCDabcd Used for dialog When prompted, click Finish elements such as to complete the installation. titles, button labels, and other screen elements. ABCDabcd Used for paths, Open the file filenames, and \os\windows\setup.exe screen output. ABCDabcd Used to # cd \opt\3par\console differentiate user input from screen output.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1.7 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2 Configuring the InServ Storage Server for Fibre Channel In this chapter 2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X 2.3 2.1.1 Configuring Ports for a Direct Connection 2.3 2.1.2 Configuring Ports for a Fabric Connection 2.4 2.1.3 Creating the Host Definition 2.6 2.2 Configuring the InServ Storage Server Running InForm OS 2.2.X 2.6 2.2.1 Configuring Ports for a Direct Connection 2.6 2.2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4 Setting Up and Zoning the Fabric 2.8 2.4.1 Configuration Guidelines For Fabric Vendors 2.9 2.4.2 Target Port Limitations and Specifications 2.10 2.4.3 Configuration Diagrams for Zoning 2.11 2.4.4 Target Port Limits and Specifications 2.16 This chapter describes how to establish a connection between InServ Storage Server and AIX host using Fibre Channel and how to set up the fabric when running InForm OS 2.2.X and 2.3.X.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.1 Configuring the InServ Storage Server Running InForm OS 2.3.X This section describes how to configure InServ Storage Server ports running OS 2.3.X. REQUIRED: The following setup must be completed before connecting the InServ Storage Server port to a device. 2.1.1 Configuring Ports for a Direct Connection To configure the InServ Storage Server ports for a direct connection, complete the following steps.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2 After all ports have been configured, verify that the ports are configured for a host in a direct connection by issuing the showport -par command on the InServ Storage Server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1 To determine if a port has already been configured for a host port in fabric mode, issue showport -par on the InServ Storage Server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.1.3 Creating the Host Definition Before connecting the AIX host to the InServ Storage Server, create a host definition that specifies a valid host persona for each InServ Storage Server that is to be connected to a host HBA port through a fabric or a direct connection. 1 To create host definitions, issue the createhost [options] [...] command.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3 Verify that each port has the appropriate personality defined: # showport -par N:S:P ConnTypeCfgRate Class2 VCN -----------Persona------------ IntCoal 4:0:2 loop auto disable disable *(13) g_ven, g_hba, aix, 0, FA enabled 2.2.2 Configuring Ports for a Fabric Connection To configure the InServ Storage Server ports for a fabric connection, complete the following steps.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.3 Connecting the InServ Storage Server to the Host Server During this stage connect the InServ Storage Server to the host server directly or to the fabric. This set of tasks includes physically cabling the InServ Storage Server to the host server or fabric. 2.4 Setting Up and Zoning the Fabric Fabric zoning controls which devices have access to each other on the fabric.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.1 Configuration Guidelines For Fabric Vendors Use the following fabric vendor guidelines before configuring ports on fabric(s) to which the InServ Storage Server connects. ■ Brocade switch ports that connect to a host server HBA port or to an InServ Storage Server port should be set to their default mode. On Brocade 3xxx switches running Brocade firmware 3.0.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.2 Target Port Limitations and Specifications In order to avoid the overwhelming of a target port and ensure continuous I/O operations, refer to the following limitations on a target port: ■ Maximum of 64 host server ports per InServ Storage Server port, with a maximum total of 1,024 host server ports per InServ Storage Server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.3 Configuration Diagrams for Zoning This section describes various zoning configurations. 2.4.3.1 Single Initiator to Single Target Zoning No Fan-In No Fan-Out With a single initiator to single target zoning, in a no fan-in, no fan-out configuration, each HBA port is connected to only one InServ Storage Server port, as shown in Figure 2-1.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.3.2 Single Initiator to Single Target Zoning with Fan-Out from One InServ Storage Server Port to Multiple Host Server Ports With single initiator to single target zoning, in a fan-out configuration, the InServ Storage Server port is connected to more that one host port, as shown in Figure 2-2. Host Server A Host Server B Fabric Fabric Node 0 Node 1 InServ 0003_IG_R1 Figure 2-2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.3.3 Single Initiator to Single Target Zoning with Fan-In from Multiple InServ Storage Server Ports to One Host Server Port With single initiator to single target zoning, in a fan-in configuration a host server port connects to many InServ Storage Server ports, as shown in Figure 2-3. Host Server Fabric Fabric Node 0 Node 1 InServ 0002_IG_R1 Figure 2-3.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.3.4 Single Initiator to Single Target Zoning with Mixed Fan-In and Fan-Out Configurations With single initiator to single target zoning, in a fan-in and fan-out configuration, one InServ Storage Server connects to multiple host servers. Host Server A Host Server B Fabric Fabric Node 0 Node 1 InServ 0005_IG_R1 Figure 2-4. Single Initiator to Single Target Zoning with Fan-In and Fan-Out 2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.3.5 Non-Compliant Zoning Examples In the following example, the zoning rule of one initiator zoned to one target is not respected, as shown in Figure 2-5. Non-Compliant Zoning Host Server A Fabric Host Server B B A Node 0 C Fabric Node 1 InServ A No zoning B Multiple initiators to a single target C Single initiator to multiple targets 0001_IG_R1 Figure 2-5. Non-Compliant Zoning Setting Up and Zoning the Fabric 3PAR Confidential 2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 2.4.4 Target Port Limits and Specifications In order to avoid the overwhelming of a target port and ensure continuous I/O operations, refer to the following limitations on a target port: ■ Maximum of 64 host server ports per InServ Storage Server port, with a maximum total of 1,024 host server ports per InServ Storage Server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3 Connecting the Host Server with Fibre Channel In this chapter 3.1 Checking the Host Server for the Current OS Version 3.2 3.2 Installing the IBM Fibre Channel HBA 3.2 3.2.1 Setting up the IBM Fibre Channel HBA for use with the InServ 3.2 3.2.2 Displaying Firmware and Driver Versions for the IBM HBA 3.3 3.2.3 Displaying the IBM HBA WWNs 3.4 3.2.4 Detecting Auto Topology 3.4 3.2.5 Setting host HBA Parameters DynamicTracking and FastFail 3.4 3.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3.4 Installing Veritas as the Multipathing Solution 3.4.1 Installing the 3PARODM for use with Veritas 3.8 3.8 3.4.2 Installing the Veritas DMP Multipathing Modules 3.10 3.4.3 Configuring the Veritas DMP Multipathing 3.10 3.1 Checking the Host Server for the Current OS Version Before connecting the InServ storage server to the host server, verify support for the host server OS and HBA driver versions.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3.2.2 Displaying Firmware and Driver Versions for the IBM HBA If the IBM FC HBA is already installed in the host server, verify support on the InServ storage server by checking the model version, FRU number, and firmware levels for each IBM FC HBA connecting to the InServ storage server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3.2.3 Displaying the IBM HBA WWNs To display the FC HBA WWNs, issue lscfg -vps -l fcs0 | grep -i on the AIX CLI: # lscfg -vps -l fcs0 | grep -i “network” Network Address.............10000000C94E6031 where 10000000C94E6031 is the HBA WWN. 3.2.4 Detecting Auto Topology IBM FC HBAs auto-detect the topology during a host reboot. 3.2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 1 Select FC Adapter. 2 Select FC SCSI I/O Controller Protocol Device. 3 Select Change/Show Characteristics of a FC SCSI Protocol Device. 4 Select the appropriate FC SCSI Protocol Device. 5 Set the options: 6 ◆ Dynamic Tracking of FC Devices to Yes. ◆ FC Fabric Event Error RECOVERY Policy to FastFail ◆ Apply change to DATABASE only to Yes Reboot the AIX host server. 3.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide Please refer to 3PAR MPIO v2.2 for IBM AIX for upgrade and removal instructions. 3.3.2 Displaying the Path Status After Installing 3PAR MPIO After the installation of the 3PAR MPIO for AIX HBA, check path status and verify the connection between the host server and InServ Storage Server. ■ To display the FC device available on the AIX host, issue lsdev -Cc disk.
3PAR AIX 5.3, 6.1, and 7.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3.3.4 Additional Modules Available with 3PAR MPIO for AIX In the event of a failure, the customer support representative requires access to information regarding the installation and configuration of the AIX host. To access this information, use the utility 3par_explorer.sh. This utility is located in /usr/lpp/3PARmpio/bin. Additional information regarding the 3PAMPIO utilities and other useful information can be found in the 3PAR MPIO Read Me Document. 3.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4 Change and or verify that the InServ Storage Server port personas or host personas are set depending of the InForm OS version running, as described in This section describes how to configure InServ Storage Server ports running OS 2.3.X. and 2.1.1 Configuring Ports for a Direct Connection or 2.1.2 Configuring Ports for a Fabric Connection. 5 Issue the inst3par.sh script ./inst3par.sh. (The script is directly accessible from the / cdrom directory).
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3.4.2 Installing the Veritas DMP Multipathing Modules If VERITAS Volume Manager is used for AIX found in Storage Foundation 5.0 with MP1 version X follow the VERITAS Volume Manager Installation and User Guide, which is available from www.VERITAS.com. Install all prerequisite APARs as required in the VERITAS Installation Guide for AIX.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4 Allocating Storage for Access by the AIX Host In this chapter 4.1 Creating Storage on the InServ 4.1 4.1.1 Creating Virtual Volumes 4.2 4.1.2 Creating Thin Provisioned Volumes 4.3 4.1.3 Exporting LUNs to the Host 4.3 4.2 Exporting VLUNs to the AIX Server 4.4 4.2.1 Restrictions on Volume Size and Number 4.4 4.2.2 Scanning for New Devices on the AIX Host 4.4 4.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4.1.1 Creating Virtual Volumes # createaldvv -cnt 5 TESTLUNs 5G After devising a plan for allocating space for the AIX host, you need to create the required Virtual Volumes on the InServ Storage Server. You can create volumes that are provisioned from one or more Common Provisioning Groups (CPGs). Volumes can be fully provisioned from a CPG or can be thinly provisioned. You can optionally specify a CPG for snapshot space for fully provisioned volumes.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide Consult the InForm Management Console help and the 3PAR Command Line Reference for complete details on creating volumes for the InForm OS version that is being used on the InServ Storage Server. Please note that the commands and options available for creating a virtual volume may vary for earlier versions of the InForm OS. 4.1.2 Creating Thin Provisioned Volumes This section explains how to export Thin Provisioned volumes to the host.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4.2 Exporting VLUNs to the AIX Server This section describes how to discover exported devices to the AIX server. 4.2.1 Restrictions on Volume Size and Number Follow the instructions for creating Virtual Volumes (VVs) and Virtual LUNs (VLUNs) in the InForm OS CLI Administrator’s Manual while adhering to these cautions and guidelines: ■ This configuration supports sparse LUNs (meaning that LUNs may be skipped).
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide ■ Following the completion of the AIX command cfgmgr, display the exported LUNs by issuing lsdev -Cc disk on the AIX CLI. # lsdev -Cc disk hdisk0 Available 00-08-00 SAS Disk Drive hdisk1 Available 07-00-01 3PAR InServ Virtual Volume hdisk2 Available 07-00-01 3PAR InServ Virtual Volume ■ To display the LUN number for each exported InServ Storage Server LUN, issue lsattr - El hdisk1 | grep -i LUN on the AIX CLI.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 4.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 5 Removing 3PAR Devices on an AIX Host Server In this chapter 5.1 Removing Fibre Channel Connected Devices on the Host 5.2 5.2 Removing Fibre Channel Devices on the InServ Storage Server 5.3 This chapter explains how to remove the InServ storage server VVs from the AIX host server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 5.1 Removing Fibre Channel Connected Devices on the Host When removing InServ Storage Server VVs from the AIX host, complete the following steps: 1 Locate and verify details of the VV by issuing lsdev -Cc disk. 2 Remove the hdisk definition from the AIX host by issuing the rmdev -l hdiskN -d. NOTE: Remove the VVs from the host server before disconnecting the InServ storage server from the host server.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 5.2 Removing Fibre Channel Devices on the InServ Storage Server To remove a single exported VLUN from the AIX Host on the InServ, complete the following steps: 1 Issue showvlun -host aixhost on the InServ Storage Server. # showvlun -host aixhost Active VLUNs Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 TESTLUN.0 aixhost 10000000C9759527 1:4:1 host 1 TESTLUN.1 aixhost 10000000C9759527 1:4:1 host 0 TESTLUN.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 3 Issue shovlun -host aixhost to verify that the VLUN is removed on the InServ Storage Server. # showvlun -host aixhost Active VLUNs Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type 1 TESTLUN.1 aixhost 10000000C9759527 1:4:1 host 1 TESTLUN.1 aixhost 10000000C9759526 1:4:1 host 1 TESTLUN.1 aixhost 10000000C9759527 0:5:1 host 1 TESTLUN.1 aixhost 10000000C9759526 0:5:1 host 1 TESTLUN.1 aixhost 10000000C9759526 1:2:1 host 1 TESTLUN.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 6 Using IBM HACMP with AIX In this chapter 6.1 Installing IBM HACMP 6.1 6.2 HACMP Parameters for 3PAR Storage 6.2 6.1 Installing IBM HACMP 3PAR supports HACMP v5.4.1 when using 3PAR MPIO 2.2 for IBM AIX using enhanced concurrent volume groups in multihost environments. NOTE: The use of non-concurrent volume groups is not supported. There are no other special considerations for using HACMP. Refer to the 3PAR Multipath I/O 2.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide Refer to IBM HACMP documentation for HACMP planning, setup and usage. These IBM HACMP documents are of particular importance: ■ Concepts and Facilities Guide ■ Planning and Installation Guide ■ Administration Guide 6.2 HACMP Parameters for 3PAR Storage There are no special settings required for IBM HACMP when using enhanced concurrent volume groups that are different than specified by the IBM documentation when setting up concurrent volume groups. 6.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 7 Using IBM PowerHA 7.1 with AIX In this chapter 7.1 Installing IBM PowerHA 7.1 7.1 7.2 PowerHA 7.1 Parameters for 3PAR Storage 7.2 7.1 Installing IBM PowerHA 7.1 3PAR supports PowerHA 7.1 when using 3PAR MPIO 2.2 for IBM AIX using enhanced concurrent volume groups in multihost environments. There are no other special considerations for using PowerHA 7.1. Refer to the 3PAR Multipath I/O 2.2 for IBM AIX User’s Guide for additional information.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 7.2 PowerHA 7.1 Parameters for 3PAR Storage There are no special settings required for IBM PowerHA 7.1 when using enhanced concurrent volume groups that are different than specified by the IBM documentation when setting up concurrent volume groups. 7.2 PowerHA 7.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 8 Booting from the InServ Storage Server 8.1 Setting the Host HBA Parameters for a SAN Boot 8.1 8.2 Assigning LUNs as Boot Volumes 8.1 8.3 Installing the Host OS for a SAN Boot 8.2 For details about connecting the InServ Storage Server to the host, see Configuring the InServ Storage Server for Fibre Channel on page 2.1. 8.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 8.3 Installing the Host OS for a SAN Boot Installation of the AIX 7.1/6.1/5.3 operating system is supported when it is booted from the InServ Storage Server. No special requirements except for the installation of 3PAR MPIO v2.2 for AIX are needed to install the AIX 7.1/6.1/5.3 OS boot volume on InServ. Follow all recommended settings and guides as covered in this document.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide a Load the distribution CD containing the 3PAR MPIO for IBM AIX into the CD drive. CAUTION: Do NOT connect the AIX host to mixed HBA types on the Inserv Storage Server when using a direct connect mode.Boot failures or missing paths may result. Use only like HBA types on the InServ Storage Server. b Use smit update_all to install the 3PAR MPIO for IBM AIX from the distribution CD. Be sure to set the parameter ACCEPT new license agreements to Yes.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide ■ Issue cfgmgr –vl hdiskX in the AIX CLI, where X is the InServ Storage Server volume for the host boot.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 9 Using Veritas Cluster Server with the AIX Hosts There are no special settings required when using Veritas Cluster other than the Veritas ASL requirement. NOTE: The VERITAS DMP layer in VERITAS Volume Manager does not recognize the storage server virtual volumes as being mulitpathed until the 3PAR VERITAS ASL for the InServ Storage Server is installed. The VERITAS ASL for the 3PAR storage server can be obtained from http://seer.entsupport.symantec.com/.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide 9.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide Revision History Release level Revision summary 320-200187 Rev A First release of this Implementation Guide with content restructuring October 2009 for improved access and coverage of AIX 5.3 and AIX 6.1 on InServ Storage Servers running all currently supported InForm OS versions. 320-200187 Rev B Second release with content restructuring for improved access and June 2011 coverage of AIX 5.3, 6.1, and 7.
3PAR AIX 5.3, 6.1, and 7.1 Implementation Guide RH.
