Hp 3par Aix and Ibm Virtual Io Server

HP 3PAR AIX and IBM Virtual I/O ServerImplementation Guide

AbstractThis implementation guide provides information for establishing communications between an HP 3PAR StoreServ Storage andAIX 7.1, AIX 6.1, AIX 5.3, or IBM Virtual I/O Server platforms. General information is also provided on the basic steps requiredto allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by the AIX or IBM Virtual I/O Server host.

HP Part Number: QL226-97117Published: September 2013

© Copyright 2013 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

Windows® is a U.S. registered trademark of Microsoft Corporation.

Contents1 Introduction...............................................................................................5

Supported Configurations..........................................................................................................5HP 3PAR OS Upgrade Considerations.........................................................................................5Audience.................................................................................................................................6

2 Configuring the HP 3PAR StoreServ Storage for Fibre Channel..........................7Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or OS 2.3.x.........................7

Configuring Ports on the HP 3PAR StoreServ Storage for a Direct Connection...............................7Configuring Ports on the HP 3PAR StoreServ Storage for a Fabric Connection..............................8Creating the Host Definition..................................................................................................9

Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 2.2.x..........................................9Configuring Ports for a Direct Connection..............................................................................10Configuring Ports for a Fabric Connection.............................................................................10Creating the Host Definition................................................................................................10

Connecting the HP 3PAR StoreServ Storage to the Host................................................................11Setting Up and Zoning the Fabric.............................................................................................11

HP 3PAR Coexistence.........................................................................................................12Configuration Guidelines for Fabric Vendors..........................................................................12Target Port Limits and Specifications.....................................................................................13HP 3PAR Priority Optimization.............................................................................................13OS Specific Expected Behavior............................................................................................13Persistent Ports...................................................................................................................14

Persistent Ports Setup and Connectivity Guidelines.............................................................14Persistent Ports Limitations...............................................................................................16Unsupported Configurations...........................................................................................16

3 Connecting the Host Server with Fibre Channel............................................17Checking the Host Server for the Current OS Version...................................................................17Installing the IBM Fibre Channel HBA........................................................................................17

Setting up the IBM Fibre Channel HBA for use with the HP 3PAR StoreServ Storage....................17Displaying Firmware and Driver Versions for the IBM HBA.......................................................17Displaying the IBM HBA WWNs.........................................................................................18Detecting Auto Topology.....................................................................................................19Setting Host HBA Parameters DynamicTracking and FastFail.....................................................19

Installing HP 3PAR MPIO on the AIX Server (Local Boot Drive) when Using HP 3PAR OS 2.2.x or OS2.3.x.....................................................................................................................................19

Installing HP 3PAR MPIO for AIX..........................................................................................19Displaying the Path Status after Installing HP 3PAR MPIO........................................................20Additional Modules Available with HP 3PAR MPIO for AIX......................................................21Additional HP 3PAR MPIO Settings......................................................................................22

Installing HP 3PAR ODM for AIX MPIO on the AIX Server (Local Boot Drive) when Using HP 3PAROS 3.1.x or OS 2.3.x..............................................................................................................22

Installing HP 3PAR ODM for AIX MPIO.................................................................................22Displaying the Path Status After Installing HP 3PAR ODM........................................................22Additional Modules Available with HP 3PAR ODM for AIX......................................................24Additional HP 3PAR ODM Settings.......................................................................................24

Installing the HP 3PAR ODM 3.1 to use with Veritas.....................................................................24Installing Veritas as the Multipathing Solution.............................................................................25

Installing the HP 3PAR ODM 1.2 Definition for Use with Veritas................................................25Installing the Veritas DMP Multipathing Modules....................................................................26Configuring the Veritas DMP Multipathing.............................................................................27

Connecting the Host Server with a Fibre Channel Reservation Policy..............................................27

Contents 3

4 Allocating Storage for Access by the AIX or IBM Virtual I/O Server Host.........28Creating Storage on the HP 3PAR StoreServ Storage...................................................................28

Creating Virtual Volumes....................................................................................................28Creating Thinly-provisioned Virtual Volumes...........................................................................29Exporting LUNs to the AIX or IBM Virtual I/O Server Host.......................................................29

Exporting VLUNs to the AIX or IBM Virtual I/O Server Host..........................................................29Restrictions on Volume Size and Number..............................................................................30Scanning for New Devices on an AIX or IBM Virtual I/O Server Host.......................................30

Creating Virtual SCSI Devices for Connected LPARs.....................................................................31Growing Virtual Volumes Exported to AIX LPARs.........................................................................34

5 Removing HP 3PAR Devices on an AIX or IBM Virtual I/O Server Host.............37Removing Fibre Channel Connected Devices on the Host.............................................................37Removing Fibre Channel Devices on the HP 3PAR StoreServ Storage.............................................38

6 Using IBM HACMP 5.5 with AIX................................................................41Installing IBM HACMP.............................................................................................................41HACMP Parameters for HP 3PAR Storage...................................................................................41

7 Using IBM PowerHA 7.1 and PowerHA 6.1 with AIX......................................42Installing IBM PowerHA 7.1 or PowerHA 6.1...............................................................................42PowerHA 7.1 and PowerHA 6.1 Parameters for HP 3PAR Storage..................................................42

8 Booting from the HP 3PAR StoreServ Storage...............................................43Setting the Host HBA Parameters for a SAN Boot........................................................................43Assigning LUNs as Boot Volumes..............................................................................................43Installing the AIX or IBM Virtual I/O Server Host OS for a SAN Boot.............................................43

9 Using Veritas Cluster Server with the AIX Hosts.............................................4710 AIX Client Path Failure Detection and Recovery...........................................48

AIX Client Automatic Path Failure Detection and Recovery............................................................48Setting Auto Path Failure Detection and Recovery........................................................................48

11 Migrating the IBM Virtual I/O Server to V2.2.2.1 or V2.2.2.2.......................49VIOS Migration Using the IBM Migration DVD...........................................................................49Requirements for Migrating VIOS Version 2.2.2.1 or 2.2.2.2........................................................49Migrating to VIOS Version 2.2.2.1 or 2.2.2.2 from Previous VIOS Versions.....................................49Completing the VIOS Migration to VIOS Version 2.2.2.1 or 2.2.2.2..............................................49

12 Cabling for IBM Virtual I/O Server Configurations......................................51Cabling and Configuration for Fabric Configurations (Dual VIO)...................................................51Cabling and Configuration for Direct Connect Configurations (Dual VIO).......................................52

13 PowerVM Live Partition Mobility................................................................5314 Support and Other Resources...................................................................55

Contacting HP........................................................................................................................55HP 3PAR documentation..........................................................................................................55Typographic conventions.........................................................................................................58HP 3PAR branding information.................................................................................................58

15 Documentation feedback.........................................................................59

4 Contents

1 IntroductionThis implementation guide provides information for establishing communications between anHP 3PAR StoreServ Storage and AIX 7.1, AIX 6.1, AIX 5.3 platforms or an IBM Virtual I/O Server.General information is also provided on the basic steps required to allocate storage on the HP 3PARStoreServ Storage that can then be accessed by the AIX or IBM Virtual I/O Server host.The information contained in this implementation guide is the outcome of careful testing of theHP 3PAR StoreServ Storage with as many representative hardware and software configurationsas possible.

REQUIREDFor predictable performance and results with your HP 3PAR StoreServ Storage, the information inthis guide must be used in concert with the documentation set provided by HP for the HP 3PARStoreServ Storage and the documentation provided by the vendor for their respective products.

Supported ConfigurationsFibre Channel connections are supported between the HP 3PAR StoreServ Storage and the AIXhost server in both a fabric-attached and direct-connect topology.

NOTE: iSCSI connections are not supported with AIX.

For information about supported hardware and software platforms, see the HP Single Point ofConnectivity Knowledge (HP SPOCK) website:http://www.hp.com/storage/spockFor more information about HP 3PAR storage products, follow the links in “HP 3PAR StorageProducts” (page 5).

Table 1 HP 3PAR Storage Products

See...Product

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=5335712&lang=en&cc=us

HP 3PAR StoreServ 7000 Storage


HP 3PAR StoreServ 10000 Storage

http://h20180.www2.hp.com/apps/Nav?h_pagetype=s-001&h_lang=en&h_cc=us&

HP 3PAR Storage Systems

h_product=5044012&h_client=S-A-R163-1&h_page=hpcom&lang=en&cc=us


HP 3PAR StoreServ Software — Device Management



HP 3PAR StoreServ Software—Replication


HP 3PAR OS Upgrade ConsiderationsFor information about planning an online HP 3PAR Operating System (HP 3PAR OS) upgrade, seethe HP 3PAR Operating System Upgrade Pre-Planning Guide, which is available on the HP BusinessSupport Center (BSC) website:

Supported Configurations 5

http://www.hp.com/storage/spock







http://h20180.www2.hp.com/apps/Nav?h_pagetype=s-001&h_lang=en&h_cc=us&h_product=5044012&h_client=S-A-R163-1&h_page=hpcom&lang=en&cc=us












http://www.hp.com/go/bscFor complete details about supported host configurations and interoperability, consult the HPSPOCK website:http://www.hp.com/storage/spock

AudienceThis implementation guide is intended for system and storage administrators who monitor anddirect system configurations and resource allocation for the HP 3PAR StoreServ Storage.The tasks described in this guide assume that the administrator is familiar with AIX, IBM VirtualI/O Server, and the HP 3PAR OS.

NOTE: This implementation guide is not intended to reproduce or replace any third-party productdocumentation. For details about devices such as host servers, HBAs, fabric switches, andnon-HP 3PAR software management tools, consult the appropriate third-party documentation.

6 Introduction

http://www.hp.com/go/bsc


2 Configuring the HP 3PAR StoreServ Storage for FibreChannel

This chapter describes how to establish a connection between an HP 3PAR StoreServ Storage andan AIX or IBM Virtual I/O Server host using Fibre Channel and how to set up the fabric whenrunning HP 3PAR OS 3.1.x, OS 2.3.x, or OS 2.2.x. For information on setting up the physicalconnection for a particular storage system, see the appropriate HP installation manual.

REQUIREDIf you are setting up a fabric along with your installation of the HP 3PAR StoreServ Storage, see“Setting Up and Zoning the Fabric” (page 11) before configuring or connecting your HP 3PARStoreServ Storage.

Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.xor OS 2.3.x

This section describes how to configure the HP 3PAR StoreServ Storage running HP 3PAR OS 3.1.xor OS 2.3.x.

RequiredThe following setup must be completed before connecting the HP 3PAR StoreServ Storage port toa device.

Configuring Ports on the HP 3PAR StoreServ Storage for a Direct ConnectionTo configure HP 3PAR StoreServ Storage ports for a direct connection to the AIX or IBM Virtual I/O Server host, complete the following steps:1. To set up the HP 3PAR StoreServ Storage ports for a direct connection, issue the following set

of commands with the appropriate parameters for each direct connect port:a. controlport offline <node:slot:port>

b. controlport config host -ct loop <node:slot:port>

where -ct loop specifies a direct connection.

c. controlport rst <node:slot:port>

Example:

# controlport offline 1:5:1# controlport config host -ct loop 1:5:1# controlport rst 1:5:1

2. After all ports have been configured, verify that the ports are configured for a host in a directconnection by issuing the showport -par command on the HP 3PAR StoreServ Storage.In the following example, loop denotes a direct connection and point denotes a fabricconnection:

# showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal0:0:1 disk loop auto 2Gbps disabled disabled disabled enabled0:0:2 disk loop auto 2Gbps disabled disabled disabled enabled0:0:3 disk loop auto 2Gbps disabled disabled disabled enabled0:0:4 disk loop auto 2Gbps disabled disabled disabled enabled

Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or OS 2.3.x 7

0:4:1 host point auto 4Gbps disabled disabled disabled enabled0:4:2 host point auto 4Gbps disabled disabled disabled enabled0:5:1 host point auto 2Gbps disabled disabled disabled enabled0:5:2 host loop auto 2Gbps disabled disabled disabled enabled0:5:3 host point auto 2Gbps disabled disabled disabled enabled0:5:4 host loop auto 2Gbps disabled disabled disabled enabled1:0:1 disk loop auto 2Gbps disabled disabled disabled enabled1:0:2 disk loop auto 2Gbps disabled disabled disabled enabled1:0:3 disk loop auto 2Gbps disabled disabled disabled enabled1:0:4 disk loop auto 2Gbps disabled disabled disabled enabled1:2:1 host point auto 2Gbps disabled disabled disabled enabled1:2:2 host loop auto 2Gbps disabled disabled disabled enabled1:4:1 host point auto 2Gbps disabled disabled disabled enabled1:4:2 host point auto 2Gbps disabled disabled disabled enabled1:5:1 host loop auto 4Gbps disabled disabled disabled enabled1:5:2 host loop auto 4Gbps disabled disabled disabled enabled1:5:3 host loop auto 4Gbps disabled disabled disabled enabled1:5:4 host loop auto 4Gbps disabled disabled disabled enabled

Configuring Ports on the HP 3PAR StoreServ Storage for a Fabric ConnectionTo configure HP 3PAR StoreServ Storage ports for a fabric connection, complete the followingsteps for each port connecting to a fabric.1. To determine whether a port has already been configured for a host port in fabric mode, issue

showport -par on the HP 3PAR StoreServ Storage.

#showport -parN:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal0:0:1 disk loop auto 2Gbps disabled disabled disabled enabled0:0:2 disk loop auto 2Gbps disabled disabled disabled enabled0:0:3 disk loop auto 2Gbps disabled disabled disabled enabled0:0:4 disk loop auto 2Gbps disabled disabled disabled enabled0:4:1 host point auto 4Gbps disabled disabled disabled enabled0:4:2 host point auto 4Gbps disabled disabled disabled enabled0:5:1 host point auto 2Gbps disabled disabled disabled enabled0:5:2 host loop auto 2Gbps disabled disabled disabled enabled0:5:3 host point auto 2Gbps disabled disabled disabled enabled0:5:4 host loop auto 2Gbps disabled disabled disabled enabled1:0:1 disk loop auto 2Gbps disabled disabled disabled enabled1:0:2 disk loop auto 2Gbps disabled disabled disabled enabled

2. If the port has not been configured, take the port offline before configuring it for connectionto a host server. To take the port offline, issue the HP 3PAR OS CLI command controlportoffline <node:slot:port>.

# controlport offline 1:5:1

3. To configure the port to the host server, issue controlport config host -ct point<node:slot:port>, where -ct point indicates that the connection type specified is afabric connection. For example:

# controlport config host -ct point 1:5:1

8 Configuring the HP 3PAR StoreServ Storage for Fibre Channel

4. Reset the port by issuing the controlport rst <node:slot:port> command.

# controlport rst 1:5:1

Creating the Host DefinitionBefore connecting the AIX or IBM Virtual I/O Server host to the HP 3PAR StoreServ Storage, createa host definition that specifies a valid host persona for each HP 3PAR StoreServ Storage that is tobe connected to a host HBA port through a fabric or a direct connection. AIX uses the genericlegacy host persona of 8 for both the QLogic and Emulex HBAs. The following steps show how tocreate the host definition.1. To create host definitions on the HP 3PAR StoreServ Storage, issue the following command:

# createhost [options] <hostname> [<WWN>...]

AIX host example:

# createhost -persona 8 AIXhost 1122334455667788 1122334455667799

IBM Virtual I/O Server example:

# createhost -persona 8 VIOS 1122334455667788 1122334455667799

2. To verify that the host has been created, issue the showhost command.AIX example:

# showhostId Name Persona......-WWN/iSCSI_Name- Port 2 AIXhost AIX-legacy 1122334455667788 4:0:1 1122334455667799 5:0:1


# showhostId Name Persona -WWN/iSCSI_Name- Port 6 VIOS AIX-legacy 1122334455667788 --- 1122334455667799 ---

NOTE: See the HP 3PAR Command Line Interface Reference or the HP 3PAR Management ConsoleUser’s Guide for complete details on using the controlport, createhost, and showhostcommands.These documents are available on the HP BSC website:http://www.hp.com/go/bsc

Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 2.2.xThis section describes how to configure an HP 3PAR StoreServ Storage running HP 3PAR OS 2.2.x.

Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 2.2.x 9


RequiredThe following setup must be completed before connecting the HP 3PAR StoreServ Storage port toa device.

Configuring Ports for a Direct ConnectionTo configure the HP 3PAR StoreServ Storage ports for a direct connection, complete the followingsteps.1. Set each HP 3PAR StoreServ Storage port to port persona 13 by issuing controlport

persona 13 <X:X:X>, where <X:X:X> is the port location, expressed asnode:slot:port.

2. Issue controlport vcn disable -f <X:X:X>.

Configuring Ports for a Fabric ConnectionTo configure the HP 3PAR StoreServ Storage ports for a fabric connection, complete the followingsteps.Procedure 11. Set each storage server port that will connect to a fabric to port persona 14 by issuing

controlport persona 14 <X:X:X>, where <X:X:X> is the port location, expressed asnode:slot:port.

2. Issue controlport vcn disable -f <X:X:X> for each port.3. Verify that each port has the appropriate persona defined:

# showport -parN:S:P ConnTypeCfgRateClass2 VCN -----------Persona------------ IntCoal4:0:2 point auto disable disable *(14) g_ven, g_hba, aix, 0, FA enabled

Creating the Host DefinitionBefore connecting the AIX or IBM Virtual I/O Server host to the HP 3PAR StoreServ Storage, createa host definition for each HP 3PAR StoreServ Storage that is to be connected to a host HBA portthrough a fabric or a direct connection.1. To create host definitions on the HP 3PAR StoreServ Storage, issue the following command:

# createhost [options] <hostname> [<WWN>...]

AIX example:

# createhost AIXhost 1122334455667788 1122334455667799


# createhost -VIOS 1122334455667788 1122334455667799

2. To verify that the host has been created, issue the HP 3PAR OS CLI showhost command.

AIX example:

# showhost2 AIXhost 1122334455667788 4:0:1 1122334455667799 5:0:1



# showhostId Name -WWN/iSCSI_Name- Port6 VIOS 1122334455667788 --- 1122334455667799 ---

Connecting the HP 3PAR StoreServ Storage to the HostDuring this stage, connect the HP 3PAR StoreServ Storage to the host server directly or to the fabric.This set of tasks includes physically cabling the HP 3PAR StoreServ Storage to the host server orfabric.

Setting Up and Zoning the FabricFabric zoning controls which Fibre Channel end-devices have access to each other on the fabric.Zoning also isolates the host server and HP 3PAR StoreServ Storage ports from Registered StateChange Notifications (RSCNs) that are irrelevant to these ports.You can set up fabric zoning by associating the device World Wide Names (WWNs) or the switchports with specified zones in the fabric. Although you can use either the WWN method or the portzoning method with the HP 3PAR StoreServ Storage, the WWN zoning method is recommendedbecause the zone survives the changes of switch ports when cables are moved around on a fabric.

RequiredEmploy fabric zoning, using the methods provided by the switch vendor, to create relationshipsbetween host server HBA ports and storage server ports before connecting the host server HBAports or HP 3PAR StoreServ Storage ports to the fabric(s).Fibre Channel switch vendors support the zoning of the fabric end-devices in different zoningconfigurations. There are advantages and disadvantages with each zoning configuration. Choosea zoning configuration based on your needs.The HP 3PAR arrays support the following zoning configurations:

• One initiator to one target per zone

• One initiator to multiple targets per zone (zoning by HBA). This zoning configuration isrecommended for the HP 3PAR StoreServ Storage. Zoning by HBA is required for coexistencewith other HP Storage arrays.

NOTE: For high availability/clustered environments that require multiple initiators to accessthe same set of target ports, HP recommends that separate zones be created for each initiatorwith the same set of target ports.

NOTE: The storage targets in the zone can be from the same HP 3PAR StoreServ Storage,multiple HP 3PAR StoreServ Storages , or a mixture of HP 3PAR and other HP storage systems.

For more information about using one initiator to multiple targets per zone, see Zoning by HBA inthe Best Practices chapter of the HP SAN Design Reference Guide. This document is available onthe HP BSC website:http://www.hp.com/go/bscIf you use an unsupported zoning configuration and an issue occurs, HP may require that youimplement one of the supported zoning configurations as part of the troubleshooting or correctiveaction.

Connecting the HP 3PAR StoreServ Storage to the Host 11


After configuring zoning and connecting each host server HBA port and HP 3PAR StoreServ Storageport to the fabric(s), verify the switch and zone configurations using the HP 3PAR OS CLI showhostcommand, to ensure that each initiator is zoned with the correct target(s).

HP 3PAR CoexistenceThe HP 3PAR StoreServ Storage array can coexist with other HP array families.For supported HP arrays combinations and rules, see the HP SAN Design Reference Guide, availableon the HP BSC website:http://www.hp.com/go/bsc

Configuration Guidelines for Fabric VendorsUse the following fabric vendor guidelines before configuring ports on fabric(s) to which theHP 3PAR StoreServ Storage connects.

• Brocade switch ports that connect to a host server HBA port or to an HP 3PAR StoreServStorage port should be set to their default mode. On Brocade 3xxx switches running Brocadefirmware 3.0.2 or later, verify that each switch port is in the correct mode using the Brocadetelnet interface and the portcfgshow command, as follows:

brocade2_1:admin> portcfgshowPorts 0 1 2 3 4 5 6 7-----------------+--+--+--+--+----+--+--+--Speed AN AN AN AN AN AN AN AN Trunk Port ON ON ON ON ON ON ON ON Locked L_Port .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. .. where AN:AutoNegotiate, ..:OFF, ??:INVALID.

The following fill-word modes are supported on a Brocade 8 G/s switch running FOS firmware6.3.1a and later:

admin>portcfgfillwordUsage: portCfgFillWord PortNumber Mode [Passive]Mode: 0/-idle-idle - IDLE in Link Init, IDLE as fill word (default) 1/-arbff-arbff - ARBFF in Link Init, ARBFF as fill word 2/-idle-arbff - IDLE in Link Init, ARBFF as fill word (SW) 3/-aa-then-ia - If ARBFF/ARBFF failed, then do IDLE/ARBFF

HP recommends that you set the fill word to mode 3 (aa-then-ia), which is the preferredmode using the portcfgfillword command. If the fill word is not correctly set, er_bad_oscounters (invalid ordered set) will increase when you use the portstatsshow commandwhile connected to 8 G HBA ports, as they need the ARBFF-ARBFF fill word. Mode 3 willalso work correctly for lower-speed HBAs, such as 4 Gb/2 Gb HBAs. For more information,see the Fabric OS command Reference Manual supporting FOS 6.3.1a and the FOS releasenotes.In addition, some HP switches, such as the HP SN8000B 8-slot SAN backbone director switch,the HP SN8000B 4-slot SAN director switch, the HP SN6000B 16 Gb FC switch, or the HPSN3000B 16 Gb FC switch automatically select the proper fill-word mode 3 as the defaultsetting.

• McDATA switch or director ports should be in their default modes as G or GX-port (dependingon the switch model), with their speed setting permitting them to autonegotiate.

• Cisco switch ports that connect to HP 3PAR StoreServ Storage ports or host HBA ports shouldbe set to AdminMode = FX and AdminSpeed = auto port, with the speed set to auto negotiate.



NOTE: The IBM Virtual I/O Server setting to enable dynamic tracking is recommended forall fabric.

• QLogic switch ports should be set to port type GL-port and port speed auto-detect. QLogicswitch ports that connect to the HP 3PAR StoreServ Storage should be set to I/O Stream Guarddisable or auto, but never enable.

Target Port Limits and SpecificationsTo avoid overwhelming a target port and ensure continuous I/O operations, observe the followinglimitations on a target port:

• Maximum of 64 host server ports per HP 3PAR StoreServ Storage port, with a maximum totalof 1,024 host server ports per HP 3PAR StoreServ Storage.

• I/O queue depth on each HP 3PAR StoreServ Storage HBA model, as follows:

QLogic 2G: 497◦◦ LSI 2G: 510

◦ Emulex 4G: 959

◦ HP 3PAR HBA 4G: 1638

◦ HP 3PAR HBA 8G: 3276 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000systems only)

• The I/O queues are shared among the connected host server HBA ports on a first-come,first-served basis.

• When all queues are in use and a host HBA port tries to initiate I/O, it receives a target queuefull response from the HP 3PAR StoreServ Storage port. This condition can result in erratic I/Operformance on each host server. If this condition occurs, each host server should be throttledso that it cannot overrun the HP 3PAR StoreServ Storage port's queues when all host serversare delivering their maximum number of I/O requests.

NOTE: When host server ports can access multiple targets on fabric zones, the assignedtarget number assigned by the host driver for each discovered target can change when thehost server is booted and some targets are not present in the zone. This situation may changethe device node access point for devices during a host server reboot. This issue can occurwith any fabric-connected storage, and is not specific to the HP 3PAR StoreServ Storage.

HP 3PAR Priority OptimizationThe HP 3PAR Priority Optimization feature introduced in HP 3PAR OS versions 3.1.2.MU2 is amore efficient and dynamic solution from managing server workloads and can be utilized as analternative to setting host server I/O throttles. Using this feature, a storage administrator is able toshare storage resources more effectively by enforcing quality of service limits on the array. Nospecial settings are needed on the host side to obtain the benefit of Priority Optimization althoughcertain per target or per adapter throttle settings may need to be adjusted in rare cases. Forcomplete details of how to use Priority Optimization (Quality of Service) on HP 3PAR arrays, pleaseread the HP 3PAR Priority Optimization technical white paper available at http://www.hp.com/go/bsc.

OS Specific Expected BehaviorAs noted in the HP 3PAR Priority Optimization white paper, there is no limitation on the minimumnumber of IOPS and/or Bandwidth that can be set on a given VVset QoS Rule. It is important

Setting Up and Zoning the Fabric 13



that the workloads of the various applications are fully understood before applying any rules.Lowering the QoS cap beyond a sensible limit will result in higher I/O response times and reducedthroughput on the host and eventually Queue Full errors returned by the array to the host.An AIX host receiving Queue Full errors can respond by logging disk errors and failing the pathto the volume. These errors on the AIX host can be identified by running the AIX errpt commandand are identified as SC_DISK type errors with a description PATH HAS FAILED. These can befollowed by additional SC_DISK entries with a description PATH HAS RECOVERED. If these errorsare observed following a lowering of a VVset QoS Rule, the Rule setting should be consideredsuspect and the value may be too low for a sensible minimum limit.

Persistent Ports

NOTE: The Persistent Ports feature is not supported on HP 3PAR OS versions prior to 3.1.2.

The Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HP 3PAR Storageonline upgrade or node-down event. Currently, persistent ports are supported only with FibreChannel connections. Persistent Ports allows a Fibre Channel HP 3PAR Storage port to assume theidentity (port WWN) of a failed port while retaining its own identity. The solution uses the NPIVfeature for Fibre Channel. This feature does not work in direct-connect mode and is supported onlyon Fibre Channel target ports that connect to Fibre Channel fabric and are in point-to-point modewhere both the active and partner ports share the same fabric.Each Fibre Channel port has a partner port automatically assigned by the system. Where a givenphysical port assumes the identity of its partner port, the assumed port is designated as a persistentport. Array port failover and failback with Persistent Ports is transparent to most host-basedmultipathing software which, in most cases, can keep all its I/O paths active.The Persistent Ports feature is activated by default during node-down events (online upgrade ornode reboot). Port shutdown or reset events do not trigger this feature. Persistent Ports is enabledby default starting with the HP 3PAR OS 3.1.2 software.In the event that an HP 3PAR Storage node is downed during an online upgrade or node-downevent, the Fibre Channel target ports fail over to their partner ports. For example, in a two-nodeHP 3PAR Storage array configuration, if ports 0:1:1, 0:5:1 and 1:1:1, 1:5:1 are connected tothe fabric, then if node 0 goes down, ports 0:1:1, 0:5:1 fail over to ports 1:1:1, 1:5:1 and becomeactive while ports 1:1:1, 1:5:1 remain active.In HP 3PAR Storage arrays with more than two nodes, failover behavior occurs on node pairs;that is, if node 0 goes down, ports on node 0 fail over to node 1, if node 2 goes down, ports onnode 2 fail over to node 3, and so on. Conversely, when node 1 goes down, ports on node 1 failover to node 0, and when node 3 goes down, ports on node 3 fail over to node 2. When thedowned node is up again, the failed-over ports automatically fail back to their original ports.During the failover and failback process, a short pause in I/O could be experienced by the host.

NOTE: See limitations in the “Persistent Ports Limitations” (page 16) section below.

Persistent Ports Setup and Connectivity GuidelinesFor Persistent Ports to function properly, specific cabling setup and connectivity guidelines thatneed to be followed can be found in the HP 3PAR Command Line Interface Administrator’s Manual,“Using Persistent Ports for Nondisruptive Online Software Upgrades.” See this document for otherinformation about Persistent Ports as well.The fabric switch ports connecting to the HP 3PAR array ports must support NPIV and have thefeature enabled in order for Persistent Ports to work.The showport command output includes Partner and FailoverState columns that displaythe partner port <node>:<slot>:<port> information and failover state information, respectively.


FailoverState values represent the failover state of the two ports listed in the N:S:P andPartner columns. The FailoverState value can be one of the following:

• none: No failover in operation

• failover_pending: In the process of failing over to partner

• failed_over: Failed over to partner

• active: The partner port is failed over to this port

• active_down: The partner port is failed over to this port, but this port is down

• failback_pending: In the process of failing back from partnerUse the showport HP 3PAR CLI commands to get the state of the persistent ports. In the output ofthe showport command shown below, under the Partner column, port 1:1:1 is the partner portthat 0:1:1 would fail over to and 0:1:1 is the partner port to which 1:1:1 would fail over. WhenPersistent Ports is not active, the FailoverState for the ports would indicate none.

When a node is down during an online upgrade or node reboot, from the output of the showportcommand, the FailoverState column would show that Persistent Ports is active. In the examplebelow, node 1 has gone down, Persistent Ports for 1:1:1 has become active on port 0:1:1, andall filesystem I/O for port 1:1:1 is physically served by port 0:1:1.

Before Persistent Ports is active, the output of the showhost command displays as follows:

# showhostId Name Persona ---------------WWN/iSCSI_Name--------------- Port 1 server1 Generic 5001438009AE770E 0:1:1 5001438009AE770C 0:1:1 5001438009AE770E 1:1:1 5001438009AE770C 1:1:1

When Persistent Ports is active, the output of the showhost command, under the Port column,shows both the physical port and the physical port where Persistent Ports is active. In the examplebelow, port 0:1:1, logged in from each of the host HBA ports, appears twice, once for the physicalport and once again for the persistent port that is active on the physical port.

# showhostId Name Persona ---------------WWN/iSCSI_Name--------------- Port 1 server1 Generic 5001438009AE770E 0:1:1 5001438009AE770C 0:1:1 5001438009AE770E 0:1:1 5001438009AE770C 0:1:1

Setting Up and Zoning the Fabric 15

After the controller node has been successfully rebooted, the FailoverState for the ports changesback to none, as shown in the following example:

After the node has been successfully rebooted, the node entry of node 0 reappears in the GUI andI/O is still in progress.Manually, you can perform failover and failback using the controlport failover <N:S:P>and controlport failback <N:S:P> command options.

Persistent Ports LimitationsWhen the Fibre Channel target port fails over to its partner port as part of the Persistent Portsfeature, the AIX host may detect a path failure and I/O will be redirected to the partner port. Oncethe port fails back, the path will recover.Persistent Ports Technical White PaperTo learn more about Persistent Ports, refer to the following White Paper:http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA4-4545ENW.pdf

Unsupported ConfigurationsThe Persistent Ports feature is not supported with iSCSI.


http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA4-4545ENW.pdf

3 Connecting the Host Server with Fibre ChannelChecking the Host Server for the Current OS Version

Before connecting the HP 3PAR StoreServ Storage to the host server, verify support for the hostserver OS and HBA driver versions. See the HP SPOCK website for configuration and interoperabilityinformation:http://www.hp.com/storage/spock

For the AIX hostTo determine the current release information for the host server and HBA, display the current versionof the AIX host system version by issuing oslevel –s in the AIX CLI interface:

# oslevel –s7100-02-02-1316

The output communicates the following details:

• 7100 represents the OS version.

• 02 indicates the technology level.

• 02-1316 indicates the service pack.

For the IBM Virtual I/O ServerTo determine the current IBM Virtual I/O Server version, issue the ioslevel command throughthe IBM Virtual I/O Server CLI interface. Example:

$ ioslevel2.2.2.2

Installing the IBM Fibre Channel HBA

Setting up the IBM Fibre Channel HBA for use with the HP 3PAR StoreServ StorageFor HBA installation instructions, driver support and usage guidelines, refer to the IBM Installationand Usage Guide for each product type. The required drivers are located on Volume 1 of the IBMBase Installation CDs and are supplied with the hardware kit from IBM.After the installation of the host FC HBAs, power up the AIX or IBM Virtual I/O Server host server.

Displaying Firmware and Driver Versions for the IBM HBAIf the IBM FC HBA is already installed in the host server, verify support on the HP 3PAR StoreServStorage by checking the model version, FRU number, and firmware levels for each IBM FC HBAconnecting to the HP 3PAR StoreServ Storage.

Checking the Host Server for the Current OS Version 17


NOTE: For the IBM Virtual I/O Server, the commands within this section are performed from theIBM Virtual I/O Server oem_setup_env environment and are designated as starting with a " #" on the command line. To enter the oem_setup_env environment from the padmin user account,issue the AIX CLI command oem_setup_env.Assuming the IBM FC HBA is already installed in the host server, verify support on the HP 3PARStoreServ Storage by checking the model version, FRU number, and firmware levels for each IBMFC HBA connecting to the HP 3PAR StoreServ Storage.

• To display the IBM FC HBAs installed, issue lsdev | grep fcs on the AIX CLI:

# lsdev | grep fcsfcs0 Available 04-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)fcs1 Available 04-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)fcs2 Available 05-00 4Gb FC PCI Express Adapter (df1000fe)fcs3 Available 05-01 4Gb FC PCI Express Adapter (df1000fe)

• To display the HBA type, issue lscfg -vps -l fcs0 | grep -i <customer card>on the AIX CLI:The following example is for AIX 6.1 and later:

# lscfg -vps -l fcs0 |grep -i "customer card" Customer Card ID Number.....577D

577D is the IBM HBA model number.

• To display the HBA FRU number, issue lscfg -vps -l fcs0 | grep -i <fru> on theAIX CLI.

# lscfg -vps -l fcs0 | grep -i “fru”FRU Number..................10N9824

10N9824 is the FRU number.

• To display the Firmware levels for each installed IBM FC HBA, issue lscfg -vps -l fcs0| grep Z9 on the AIX CLI:

# lscfg -vps -l fcs0 | grep Z9

Device Specific.(Z9)........US1.10X5

US1.10X5 is the current HBA firmware.

Displaying the IBM HBA WWNsTo display the FC HBA WWNs, issue lscfg -vps -l fcs0 | grep -i <network> on theAIX CLI:

# lscfg -vps -l fcs0 | grep -i “network”

Network Address.............10000000C94E6031

where 10000000C94E6031 is the HBA WWN.

18 Connecting the Host Server with Fibre Channel

Detecting Auto TopologyIBM FC HBAs auto-detect the topology during a host reboot.

Setting Host HBA Parameters DynamicTracking and FastFail

RequiredHP requires that both of the parameters DynamicTracking and FastFail be enabled on each of theIBM FC HBAs connected to the HP 3PAR StoreServ Storage.Use the FastFail setting only when the connection type is direct connect. Use both FastFail andDynamic Tracking when the connection type is fabric.

NOTE: These parameters need to be changed on the AIX or the IBM Virtual I/O Server. The hostrequires a reboot to enable the changes once made.

When dynamic tracking of FC devices is enabled, the FC adapter driver can detect when the FiberChannel N_Port ID of a device changes and can reroute traffic destined for that device to the newaddress while the devices are still online.The following events can cause an N_Port ID to change:

• Moving a cable between a switch and storage device from one switch port to another.

• Connecting two separate switches via an Inter-Switch Link (ISL).

• Rebooting a switch.Setting the IBM FC HBA parameter of FastFail speeds up recovery time in the event of a pathfailure.To set up Dynamic Tracking and FastFail on an IBM FC HBA, complete the following steps, usingthe SMIT devices menu: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:

• Dynamic Tracking of FC Devices to Yes.

• FC Fabric Event Error RECOVERY Policy to FastFail

• Apply change to DATABASE only to Yes6. Restart the AIX or IBM Virtual I/O Server host.

Installing HP 3PAR MPIO on the AIX Server (Local Boot Drive) when UsingHP 3PAR OS 2.2.x or OS 2.3.x

This section describes how to install the HP 3PAR MPIO on the AIX server or the IBM Virtual I/OServer.

Installing HP 3PAR MPIO for AIXThis procedure applies to either a new installation or an existing installation where HP 3PARStoreServ Storage virtual volumes (VVs) already exist on an AIX 6.1, AIX 5.3, or IBM Virtual I/OServer host. This installation must be performed by a user logged into the AIX system with rootprivileges.

Installing HP 3PAR MPIO on the AIX Server (Local Boot Drive) when Using HP 3PAR OS 2.2.x or OS 2.3.x 19

NOTE: For the IBM Virtual I/O Server, the commands within this section are performed from theIBM Virtual I/O Server "oem_setup_env" environment and are designated as starting with a " #" on the command line. To enter the "oem_setup_env" environment from the 'padmin' user account,issue the AIX CLI command oem_setup_env.

Installation of the HP 3PAR MPIO requires a system reboot to become effective. The HP 3PAR MPIOsoftware will create an active/active failover environment to the HP 3PAR storage devices. SMITMPIO can be used to configure or manage the MPIO environment if settings other than the defaultactive/active environment are desired. The HP 3PAR MPIO package is not to be used in conjunctionwith Veritas Volume Manager.1. Load the distribution CD containing the HP 3PAR MPIO for IBM AIX into the CD drive.2. If you are installing HP 3PAR MPIO for the first time, issue SMIT on the AIX CLI to install the

HP 3PAR MPIO for IBM AIX from the distribution CD.If HP 3PAR MPIO has been previously installed, issue SMIT update_all on the AIX CLI.

NOTE: Be sure to set the parameter ACCEPT new license agreements to yes.

3. Restart the AIX or IBM Virtual I/O Server host.See the HP 3PAR MPIO v2.2 for IBM AIX for upgrade and removal instructions. This documentis available on the HP BSC website:http://www.hp.com/go/bsc

Displaying the Path Status after Installing HP 3PAR MPIOAfter the installation of the HP 3PAR MPIO for AIX HBA, verify that the HP 3PAR ODM has beeninstalled successfully:

# lslpp -l|grep -i 3par 3PARmpio.64 2.2.0.0 COMMITTED 3PAR Multipath I/O for IBM AIX

Check path status and verify the connection between the host server and HP 3PAR StoreServStorage.

• To display the FC device available on the AIX host or IBM Virtual I/O Server, issue lsdev-Cc disk.

# lsdev -Cc disk

hdisk0 Available 00-08-00 SAS Disk Drivehdisk1 Available 07-00-01 3PAR InServ Virtual Volumehdisk2 Available 07-00-01 3PAR InServ Virtual Volumehdisk3 Available 07-00-01 3PAR InServ Virtual Volumehdisk4 Available 07-00-01 3PAR InServ Virtual Volumehdisk5 Available 07-00-01 3PAR InServ Virtual Volume

• To display the path status through the AIX CLI on hdisk1, issue lspath –l hdisk1:

# lspath -l hdisk1Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5



Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5

• To display the specific path information on hdisk1, issue lspath -l hdisk1 -F “statusname parent connection”.

NOTE: Highlighted text shows the details for node, slot, and port (<n:s:p>).

# lspath -l hdisk1 -F “status name parent connection”Enabled hdisk1 fscsi4 20510002ac0000b3,0Enabled hdisk1 fscsi4 20410002ac0000b3,0Enabled hdisk1 fscsi4 21210002ac0000b3,0Enabled hdisk1 fscsi4 21410002ac0000b3,0Enabled hdisk1 fscsi4 21510002ac0000b3,0Enabled hdisk1 fscsi5 20510002ac0000b3,0Enabled hdisk1 fscsi5 20410002ac0000b3,0Enabled hdisk1 fscsi5 21210002ac0000b3,0Enabled hdisk1 fscsi5 21410002ac0000b3,0Enabled hdisk1 fscsi5 21510002ac0000b3,0

• To display the basic path status for ALL MPIO devices, issue the command lspath.

# lspath

Enabled hdisk0 sas0Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5

Additional Modules Available with HP 3PAR MPIO for AIXIn the event of a failure, the customer support representative requires access to information regardingthe installation and configuration of the AIX or IBM Virtual I/O Server host. To access thisinformation, use the utility 3par_explorer.sh.This utility is located in /usr/lpp/3PARmpio/bin.Additional information regarding the HP 3PAR MPIO utilities and other useful information can befound in the HP 3PAR ODM 3.1 Software for IBM AIX Readme, which is available on the HP BSCwebsite:http://www.hp.com/go/bsc

Installing HP 3PAR MPIO on the AIX Server (Local Boot Drive) when Using HP 3PAR OS 2.2.x or OS 2.3.x 21


Additional HP 3PAR MPIO SettingsFor details about AIX 3PAR MPIO, see the Readme:3PAR® Multipath I/O 2.2 for IBM AIX on theHP BSC website:http://www.hp.com/storage/spock

Installing HP 3PAR ODM for AIX MPIO on the AIX Server (Local Boot Drive)when Using HP 3PAR OS 3.1.x or OS 2.3.x

This section describes how to install the HP 3PAR ODM for the AIX MPIO.

NOTE: HP 3PAR OS 3.1.x supports only the HP 3PAR ODM 3.1 for multipathing. HP 3PAR OS2.3.x supports both the HP 3PAR MPIO 2.2 and HP 3PAR ODM 3.1 for multipathing. It isrecommended that new 2.3.x installations use the HP 3PAR ODM 3.1 and AIX MPIO as themultipathing software.

Installing HP 3PAR ODM for AIX MPIOThis procedure applies to either a new installation or an existing installation where HP 3PARStoreServ Storage virtual volumes (VVs) already exist on an AIX 7.1, AIX 6.1, AIX 5.3, or IBMVirtual I/O Server system. This installation must be performed by a user logged into the AIX systemwith root privileges.

NOTE: For the IBM Virtual I/O Server, the commands within this section are performed from theIBM Virtual I/O Server oem_setup_env environment and are designated as starting with a " #" on the command line. To enter the oem_setup_env environment from the padmin user account,issue the AIX CLI command oem_setup_env.

Installation of the HP 3PAR ODM requires a system reboot to become effective. SMIT MPIO canbe used to configure or manage the MPIO environment. By default, the AIX MPIO is set toactive/active mode. The HP 3PAR ODM package is not to be used in conjunction with VeritasVolume Manager.1. Load the distribution CD containing the HP 3PAR ODM for IBM AIX into the CD drive.2. Issue SMIT on the AIX CLI to install the HP 3PAR MPIO for IBM AIX from the distribution CD.

If HP 3PAR MPIO has been previously installed, Issue SMIT update_all on the AIX CLI.

NOTE: Be sure to set the parameter ACCEPT new license agreements to yes.

3. Restart the AIX server or IBM Virtual I/O Server.For upgrade and removal instructions, see the HP 3PAR ODM 3.1 Software for IBM AIX Readme.

Displaying the Path Status After Installing HP 3PAR ODMAfter the installation of the HP 3PAR MPIO for AIX HBA, verify that the HP 3PAR ODM has beeninstalled successfully:

# lslpp -l|grep -i 3par 3PARmpio.64 3.1.0.0 COMMITTED 3PAR Multipath I/O for IBM



After the installation of the ODM for AIX MPIO, check path status and verify the connection betweenthe host server and HP 3PAR StoreServ Storage.

• To display the FC device available on the AIX or IBM Virtual I/O Server host, issue lsdev-Cc disk.

# lsdev -Cc disk

hdisk0 Available 00-08-00 SAS Disk Drivehdisk1 Available 07-00-01 3PAR InServ Virtual Volumehdisk2 Available 07-00-01 3PAR InServ Virtual Volumehdisk3 Available 07-00-01 3PAR InServ Virtual Volumehdisk4 Available 07-00-01 3PAR InServ Virtual Volumehdisk5 Available 07-00-01 3PAR InServ Virtual Volume

• To display the path status through the AIX CLI on hdisk1, issue lspath –l hdisk1:

# lspath -l hdisk1

Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi4Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5Enabled hdisk1 fscsi5

• To display the specific path information on hdisk1, issue lspath -l hdisk1 -F “statusname parent connection”.

NOTE: Highlighted text shows the details for node, slot, and port (<n:s:p>).

# lspath -l hdisk1 -F “status name parent connection”

Enabled hdisk1 fscsi4 20510002ac0000b3,0Enabled hdisk1 fscsi4 20410002ac0000b3,0Enabled hdisk1 fscsi4 21210002ac0000b3,0Enabled hdisk1 fscsi4 21410002ac0000b3,0Enabled hdisk1 fscsi4 21510002ac0000b3,0Enabled hdisk1 fscsi5 20510002ac0000b3,0Enabled hdisk1 fscsi5 20410002ac0000b3,0Enabled hdisk1 fscsi5 21210002ac0000b3,0Enabled hdisk1 fscsi5 21410002ac0000b3,0Enabled hdisk1 fscsi5 21510002ac0000b3,0

• To display the basic path status for ALL MPIO devices, issue the command lspath.

# lspath

Enabled hdisk0 sas0Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4

Installing HP 3PAR ODM for AIX MPIO on the AIX Server (Local Boot Drive) when Using HP 3PAR OS 3.1.x or OS 2.3.x 23

Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi4Enabled hdisk2 fscsi4Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5Enabled hdisk1 fscsi5Enabled hdisk2 fscsi5

Additional Modules Available with HP 3PAR ODM for AIXIn the event of a failure, the customer support representative requires access to information regardingthe installation and configuration of the AIX or IBM Virtual I/O Server host. To access thisinformation, use the utility 3par_explorer.sh.This utility is located in /usr/lpp/3PARmpio/bin.Additional information regarding the HP 3PAR MPIO utilities and other useful information can befound in the HP 3PAR ODM 3.1 Software for IBM AIX Readme, available on the HP BSC website:http://www.hp.com/go/bsc

Additional HP 3PAR ODM SettingsFor details about AIX HP 3PAR ODM, see the HP 3PAR ODM 3.1 Software for IBM AIX Readme,available on the HP BSC website:http://www.hp.com/go/bsc

NOTE: For AIX installs in other than en_US language convention, you must move an ODM fileto enable the OS to correctly display the 3PAR VV label on the hdisk instance. Use the followingcommand to copy the file to the appropriate location.cp /usr/lib/nls/msg/en_US/3par.cat /usr/lib/methods/3par.cat

andcp /usr/lib/nls/msg/en_US/3par.cat /usr/lib/nls/msg/X/3par.catWhere “X” is the language convention used at time of install other than en_US.

Installing the HP 3PAR ODM 3.1 to use with VeritasWhen using Veritas Volume Manager, installation of the HP 3PAR ODM 3.1 for Veritas VxVM forHP 3PAR OS 2.3.x or OS 3.1.x will permit command tag queue support, allowing a queue depthgreater than one.This procedure applies either to a new installation or to an existing installation where HP 3PARStoreServ Storage VVs already exist on an AIX 7.1, AIX 6.1, or AIX 5.3 system. A user loggedinto the AIX system as the superuser or with root privileges must perform this installation. Installationof the HP 3PAR ODM changes requires a system reboot to become effective.To Install the HP 3PAR ODM 3.1 Software for Veritas VxVM, follow these steps:1. Copy the 3parodm_vrts.tar.qz file to a temporary folder in your system.2. Unzip and untar the contents of the downloaded file.3. Execute smit install.4. Select Install and Update Software > Install Software.




5. Press F4 and select the location of the unzipped files.6. Press F4 for software to install and select the .bff file.7. Click Enter. The smit install installs the HP 3PAR ODM software. Upon completion, the

command status displays:OK

8. To verify the HP 3PAR ODM package after reboot, issue lslpp -ldevices.fcp.disk.3PAR.vxvm.rte. This command displays the package level andstate.For more detail regarding the HP 3PAR ODM 3.1 for Veritas VxVM, see the HP 3PAR ODM3.1 Software for Veritas VxVM Readme.

9. If the AIX system had previously defined HP 3PAR StoreServ Storage VVs, the hdisk definitionsappear as 3PAR InServ Virtual Volume. Any newly created or exported HP 3PARStoreServ Storage VVs will also have characteristics similar to those shown below:

# lsdev -Cc disk

hdisk0 Available 10-60-00-10,0 16 Bit LVD SCSI Disk Drivehdisk1 Available 20-58-01 3PAR InServ Virtual Volumehdisk2 Available 20-58-01 3PAR InServ Virtual Volumehdisk3 Available 20-60-01 3PAR InServ Virtual Volumehdisk4 Available 20-58-01 3PAR InServ Virtual Volumehdisk5 Available 20-60-01 3PAR InServ Virtual Volumehdisk6 Available 20-60-01 3PAR InServ Virtual Volume

Existing HP 3PAR virtual volumes or any newly created or exported HP 3PAR StoreServ StorageVVs have a default queue depth of 16 defined. To display this value, issue the following commandon the AIX CLI, where x is the hdisk number/definition.

# lsattr -El hdiskx | grep queue_depth

If required, changes may be applied to the new default queue depth of the HP 3PAR StoreServStorage VV. Any change made to the queue depth requires a system reboot to become effective.To change the device attribute for queue depth issue the following command on the AIX CLI:

# chdev -l hdiskx -a queue_depth=yy -P

Installing Veritas as the Multipathing SolutionIf Veritas is the multipathing solution, use the following section.

NOTE: For HP 3PAR OS 3.1.x, the HP 3PAR ODM 3.1 software for Veritas VxVM is used. ForHP 3PAR OS 2.2.x, the HP 3PAR ODM 1.2 software is used. For HP 3PAR OS 2.3.x, either theHP 3PAR ODM 1.2 or the HP 3PAR ODM 3.1 software is used.

Installing the HP 3PAR ODM 1.2 Definition for Use with VeritasWhen using Veritas Volume Manager, installation of the HP 3PAR ODM 1.2 definition for HP 3PAROS 2.3.x or OS 2.2.x will permit Command Tag Queue support allowing a queue depth greaterthan one.This procedure applies to either a new installation or an existing installation where HP 3PARStoreServ Storage VVs already exist on an AIX 7.1, AIX 6.1, or AIX 5.3 system. A user loggedinto the AIX system as the superuser or with root privileges must perform this installation. Installationof the HP 3PAR ODM 1.2 for Veritas VxVM changes requires a system reboot to become effective.

Installing Veritas as the Multipathing Solution 25

1. Insert the HP 3PAR ODM Definition for IBM AIX installation CD into the AIX server.2. On the AIX CLI, mount the CD-ROM by determining the device access name of the CD-ROM

device.In the following example, the CD-ROM is mounted via the AIX CLI, where X is the device name.

# mkdir -p /cdrom# mount -V cdrfs -o ro /dev/cdx /cdrom# cd /cdrom

3. Read the aixodm.pdf file contained on the installation CD for HP 3PAR ODM Definition forIBM AIX.

4. Change and/or verify that the HP 3PAR StoreServ Storage port personas or host personasare set depending on the HP 3PAR OS version running, as described in “Configuring theHP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or OS 2.3.x” (page 7).

5. Issue the inst3par.sh script ./inst3par.sh. (The script is directly accessible from the/cdrom directory).

6. In order for the results to be permanent, execute the <savebase> and <bosboot -a>commands. Observe caution when executing these two commands. Refer to AIX documentationfor details.

7. Reboot the AIX system after executing the bosboot command and waiting for commandcompletion to occur.

8. If the AIX system had previously defined HP 3PAR StoreServ Storage VVs, the hdisk definitionsappear as 3PAR InServ Virtual Volume. Any newly created or exported HP 3PARStoreServ Storage VVs will also have characteristics similar to those shown below:

# lsdev -Cc disk

hdisk0 Available 10-60-00-10,0 16 Bit LVD SCSI Disk Drivehdisk1 Available 20-58-01 3PAR InServ Virtual Volumehdisk2 Available 20-58-01 3PAR InServ Virtual Volumehdisk3 Available 20-60-01 3PAR InServ Virtual Volumehdisk4 Available 20-58-01 3PAR InServ Virtual Volumehdisk5 Available 20-60-01 3PAR InServ Virtual Volumehdisk6 Available 20-60-01 3PAR InServ Virtual Volume

Existing HP 3PAR virtual volumes or any newly created or exported HP 3PAR StoreServ StorageVVs has a default queue depth of 16 defined. To display this value, issue the followingcommand on the AIX CLI, where x is the hdisk number/definition.

# lsattr -El hdiskx | grep queue_depth

If required, changes may be applied to the new default queue depth of the HP 3PAR StoreServStorage Virtual Volumes. Any change made to the queue depth requires a system reboot tobecome effective.To change the device attribute for queue depth issue the following command on the AIX CLI:

# chdev -l hdiskx -a queue_depth=yy -P

Installing the Veritas DMP Multipathing ModulesIf Veritas Volume Manager is used for AIX in Storage Foundation, follow the Veritas VolumeManager Installation and User Guide, which is available from www.symantec.com.


www.symantec.com

Install all prerequisite APARs as required in the Veritas Installation Guide for AIX.The Veritas DMP layer in Veritas Volume Manager does not recognize the storage server volumesas being multipathed until HP 3PAR ODM 3.1 software for Veritas VxVM is installed.The HP 3PAR ODM 3.1 software for Veritas VxVM can be obtained from http://seer.entsupport.symantec.com/.

Configuring the Veritas DMP MultipathingThere are no special considerations or configuration modifications that require changing whenusing the HP 3PAR StoreServ Storage, as long as the HP 3PAR ODM 3.1 software for VeritasVxVM is installed.

Connecting the Host Server with a Fibre Channel Reservation PolicyA reservation policy, which determines the type of reservation methodology that the device driverimplements when the device is opened, can be used to limit device access from other adapters,whether the adapters are on the same system or another system. The reservation policy on an HPdevice is controlled by the predefined ODM attribute reserve_policy. You can change thevalue of reserve_policy by invoking the AIX chdev command on an HP 3PAR MPIO device.Three different reservation policies can be set on HP 3PAR MPIO devices:No_reserver If you set HP 3PAR devices with this reservation policy, no reservation is made

on the devices. A device without reservation can be accessed by any initiatorat any time. I/O can be sent from all the paths of the HP 3PAR device. Thisis the default reservation policy of HP 3PAR MPIO 2.2 and HP 3PAR ODM3.1.

Single_path If you set this reservation policy for HP 3PAR MPIO devices, only thefail_over path selection algorithm can be selected for the devices. Withthis reservation policy, all paths are open on an HP 3PAR device; however,only one path makes a reservation on the device. I/O can be sent only throughthis path.

PR_exclusive With this reservation policy, a persistent reservation (PR) is made on the HP3PAR device with a PR key. Any initiators that register with the same PR keycan access the device. Normally, you should pick a unique PR key for a server.Different servers should each have a different, unique PR key. I/O is routedto all paths of the MPIO device, because all paths of an MPIO device areregistered with the same PR key.

NOTE: The PR_shared reservation policy is not supported by HP at this time.

NOTE: For AIX installs in other than en_US language convention, you must move an ODM fileto enable the OS to correctly display the 3PAR VV label on the hdisk instance. Use the followingcommand to copy the file to the appropriate location.cp /usr/lib/nls/msg/en_US/3par.cat /usr/lib/methods/3par.cat

andcp /usr/lib/nls/msg/en_US/3par.cat /usr/lib/nls/msg/X/3par.catWhere “X” is the language convention used at time of install other than en_US.

Connecting the Host Server with a Fibre Channel Reservation Policy 27

http://seer.entsupport.symantec.com/

http://seer.entsupport.symantec.com/

4 Allocating Storage for Access by the AIX or IBM VirtualI/O Server Host

Creating Storage on the HP 3PAR StoreServ StorageThis section describes the general steps and commands that are required to create the virtualvolumes (VVs) that can then be exported for discovery by the AIX or IBM Virtual I/O Server host.For additional information, see the HP 3PAR Command Line Interface Administrator’s Manual. Fora comprehensive description of HP 3PAR OS commands, see the HP 3PAR Command Line InterfaceReference. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigateto your product page, click HP Support & Drivers, and then click Manuals.

Creating Virtual VolumesYou 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 canoptionally specify a CPG for snapshot space for fully-provisioned volumes.

Using the HP 3PAR Management Console:1. From the menu bar, select:

Actions→Provisioning→Virtual Volume→Create Virtual Volume2. Use the Create Virtual Volume wizard to create a base volume.3. Select one of the following options from the Allocation list:

• Fully Provisioned

• Thinly Provisioned

Using the HP 3PAR OS CLI:To create a fully-provisioned or thinly-provisioned virtual volume, issue the following HP 3PAR OSCLI command:Here is an example:

# createvv -cnt 5 TESTLUNS 5G

NOTE: To create thinly-provisioned virtual volumes, an HP 3PAR Thin Provisioning license isrequired.

Consult the HP 3PAR Management Console User’s Guide and the HP 3PAR Command Line InterfaceReference for complete details on creating volumes for the HP 3PAR OS version that is being usedon the HP 3PAR StoreServ Storage.These documents are available on the HP BSC website:http://www.hp.com/go/bsc

NOTE: The commands and options available for creating a virtual volume may vary for earlierversions of the HP 3PAR OS.

28 Allocating Storage for Access by the AIX or IBM Virtual I/O Server Host

http://www.hp.com/go/3par/


Creating Thinly-provisioned Virtual VolumesTo create thinly-provisioned virtual volumes (TPVVs), see the following documents:

• HP 3PAR StoreServ Storage Concepts Guide

• HP 3PAR Command Line Interface Administrator’s Manual

• HP 3PAR Command Line Interface ReferenceThese documents are available on the HP BSC website:http://www.hp.com/go/bsc

Exporting LUNs to the AIX or IBM Virtual I/O Server HostThis section explains how to export LUNs to the host server as VVs, referred to as virtual LUNs(VLUNs).To export VVs as VLUNs, issue the following command:

createvlun [–cnt] <number of LUNs> <name_of_virtual_LUNs.int> <starting_LUN_number> <hostname/hostdefinition>

where:

• [–cnt] specifies the number of identical VVs to create using an integer from 1 through 999.If not specified, one virtual volume is created.

• <name_of_virtual_LUNs> specifies name of the VV being exported as a virtual LUN.

• <starting_LUN_number> indicates that is the starting LUN number.

• .int is the integer value. For every LUN created, the .int suffix of the VV name getsincremented by one.

• <hostname/hostdefinition> indicates that hostname is the name of the host created in“Creating the Host Definition” (page 9) or “Creating the Host Definition” (page 10).

Example:

# createvlun –cnt 5 TESTLUNS.0 0 hostname/hostdefinition

# createvlun -cnt 5 TESTLUNa.0 0 VIOS

WARNING! If the configuration being used has two IBM Virtual I/O Servers, the LUN numberswhen exported to each of the IBM Virtual I/O Servers must be identical. If this important note isnot adhered to, data corruption will occur.Example:

# createvlun -cnt 5 TESTLUNs.0 0 VIOS#one

# createvlun -cnt 5 TESTLUNs.0 0 VIOS#two

Exporting VLUNs to the AIX or IBM Virtual I/O Server HostThis section describes how to discover exported devices to the AIX or IBM Virtual I/O Server host.

Exporting VLUNs to the AIX or IBM Virtual I/O Server Host 29


Restrictions on Volume Size and NumberFollow the guidelines for creating virtual volumes (VVs) and Virtual LUNs (VLUNs) in the HP 3PARCommand Line Interface Administrator’s Manual while adhering to these cautions and guidelines:

• This configuration supports sparse LUNs (meaning that LUNs may be skipped). LUNs mayalso be exported in non-ascending order (e.g. 0, 5, 7, 3).

• The HP 3PAR StoreServ Storage supports the exportation of VLUNs with LUNs in the rangefrom 0 to 65535.

NOTE: AIX 7.1 supports only 512 LUNs per host HBA port, 0–511.

• Exported VLUNs will not be registered on the host until cfgmgr is run on the host.

• The maximum LUN size that can be exported to an IBM Virtual I/O Server is 2 TB when theinstalled HP 3PAR OS version is 3.1.x or 2.3.x.

• The maximum LUN size that can be exported to an AIX or IBM Virtual I/O Server host is 16TB when the installed HP 3PAR OS version is 3.1.x or 2.3.x. A LUN size of 16 TB on an AIXor IBM Virtual I/O Server host is dependent on the installed AIX technology level, since someolder versions of AIX will not support an hdisk greater than 2 TB.

CAUTION: If the configuration being used utilizes two IBM Virtual I/O Servers, the LUN numberswhen exported to each of the IBM Virtual I/O Servers must be identical. If this important note isnot adhered to data corruption will occur.

Scanning for New Devices on an AIX or IBM Virtual I/O Server HostThis section describes the steps to scan for new devices on an AIX or IBM Virtual I/O Server host.

• LUN discovery on the AIX or IBM Virtual I/O Server host is accomplished by issuing cfgmgron the AIX or through the IBM Virtual I/O Server CLI command line.

• Following the completion of the cfgmgr command, display the exported LUNs by issuinglsdev -Cc disk on the AIX CLI or through the IBM Virtual I/O CLI command line.AIX example:

# lsdev -Cc disk

hdisk0 Available 00-08-00 SAS Disk Drivehdisk1 Available 07-00-01 3PAR InServ Virtual Volumehdisk2 Available 07-00-01 3PAR InServ Virtual Volume


$ lsdev -type diskname status descriptionhdisk0 Available 3PAR InServ Virtual Volumehdisk1 Available 3PAR InServ Virtual Volumehdisk2 Available 3PAR InServ Virtual Volumehdisk3 Available 3PAR InServ Virtual Volumehdisk4 Available 3PAR InServ Virtual Volumehdisk5 Available 3PAR InServ Virtual Volume

• To display the LUN number for each exported HP 3PAR StoreServ Storage LUN for AIX, issuethe following command on the AIX CLI:

# lsattr -El hdisk1 | grep -i LUN


Example:

# lsattr -El hdisk1 | grep -i LUNlun_id 0x0 Logical unit number ID False

# lsattr -El hdisk2 | grep -i LUNlun_id 0x1000000000000 Logical unit number ID False

To display the LUN number in HEX for each exported HP 3PAR StoreServ Storage LUN forthe IBM Virtual I/O Server, issue the following command through the IBM Virtual I/O CLIcommand line:

$ lsdev -dev hdisk1 -attr | grep -i lun

Example:

$ lsdev -dev hdisk1 -attr | grep -i lunlun_id 0xa000000000000

• To display the exported raw LUN capacity in megabytes for AIX, issue the bootinfo -shdisk1 command on the AIX CLI. For example:

# bootinfo -s hdisk15120

To display the exported raw LUN capacity in megabytes, issue bootinfo -s hdisk1 fromthe oem_setup_env environment. For example:

# bootinfo -s hdisk171680

Creating Virtual SCSI Devices for Connected LPARsThis section describes the steps to create a virtual SCSI device to be used by a connected LPAR.In this example, assuming that virtual SCSI devices have been defined in the managed profiles forthe IBM Virtual I/O Server and that the LPAR is receiving its virtualized SCSI devices from the virtualI/O Server, a virtual device will be created by physical backing device hdisk22 that will bemapped to virtual adapter vhost0.

WARNING! In an environment where two IBM Virtual I/O Servers are used to access the samestorage, it is imperative to insure that the LUN numbers are identical on each IBM Virtual I/OServer when virtualizing those devices to an attached client. Failure to do so will result in datacorruption.

Verify that hdisk22 is connected to the IBM Virtual I/O Server by issuing the lsdev -typedisk | grep hdisk22 command.

$ lsdev -type disk | grep hdisk22hdisk22 Available 3PAR InServ Virtual Volume

Creating Virtual SCSI Devices for Connected LPARs 31

Check/Verify the physical LUN number that is associated with hdisk22 by issuing the lsdev-dev hdisk22 -attr | grep lun_id command.

$ lsdev -dev hdisk22 -attr | grep lun_idlun_id 0x1f4000000000000 Logical unit number ID False

Or issue lspath -dev hdisk22 to display the path status and the physical LUN numberassociated with hdisk22.

$ lspath -dev hdisk22status name parent connection

Enabled hdisk22 fscsi0 22410002ac000044,1f4000000000000Enabled hdisk22 fscsi0 22510002ac000044,1f4000000000000Enabled hdisk22 fscsi0 23220002ac000044,1f4000000000000Enabled hdisk22 fscsi0 23410002ac000044,1f4000000000000Enabled hdisk22 fscsi0 23510002ac000044,1f4000000000000Enabled hdisk22 fscsi1 22410002ac000044,1f4000000000000Enabled hdisk22 fscsi1 22510002ac000044,1f4000000000000Enabled hdisk22 fscsi1 23220002ac000044,1f4000000000000Enabled hdisk22 fscsi1 23410002ac000044,1f4000000000000Enabled hdisk22 fscsi1 23510002ac000044,1f4000000000000

The Physical LUN number associated with hdisk22 is "1f4"

mkvdev -vdev hdisk22 -vadapter vhost0 -dev newvdev

mkvdev -vdev hdisk22 -vadapter vhost0 -dev newvdev newvdev Available

Verify any needed information regarding the newly created virtual device by issuing lsmap -alland locating the hdisk22 backing device.

$ lsmap -allSVSA Physloc Client Partition ID--------------- -------------------------------------------- ------------------vhost0 U8203.E4A.10DB5C1-V5-C11 0x00000007

VTD newvdevStatus AvailableLUN 0x9600000000000000Backing device hdisk22Physloc U789C.001.DQD2174-P1-C1-T1-W22410002AC000044-L1F4000000000000

Once the LUNs have been virtualized and exported to the appropriate VHOST device definitionsusing the mkvdev command, the devices will not be visible on the AIX guest clients LPAR until thecfgmgr command is executed.

CAUTION: If dual IBM Virtual I/O Servers are configured and using the same physical devicesfrom the HP 3PAR StoreServ Storage, it is important to verify that the same physical LUN numbersare represented when creating virtual SCSI devices on each of the IBM Virtual I/O Servers. Failureto perform this step when using dual IBM Virtual I/O Servers will result in data corruption.

Example of cautionary scenario:


Assuming that dual IBM Virtual I/O Servers are configured named VIOS1 and VIOS2.

• From the IBM Virtual I/O Server named VIOS1, hdisk22 may be backed by physical deviceLUN 1f4.

• However, from the IBM Virtual I/O Server named VIOS2, hdisk22 may be backed byphysical device LUN 1f0.

From VIOS1:



where 1f4000000000000 indicates the physical LUN number.From VIOS2:



where 1f0000000000000 indicates the physical LUN number.However, hdisk23 on VIOS2 has the correct physical LUN number of 1f4000000000000.



Creating Virtual SCSI Devices for Connected LPARs 33

Therefore, when the virtual SCSI devices are created on each of the IBM Virtual I/O Servers, it isnecessary to use different hdisk definitions when using the mkvdev command to create the virtualSCSI device;On VIOS1, the command is:


On VIOS2, the command is:


In conclusion, when creating virtual SCSI devices to be used by connected LPARs, be sure to firstverify that the same physical LUN numbers are associated with each hdisk definition.

Growing Virtual Volumes Exported to AIX LPARsThis section explains how to grow HP 3PAR StoreServ Storage virtual volumes that are mapped toAIX LPARs being served by the VIO servers. This section assumes that HP 3PAR StoreServ Storagethinly provisioned virtual volumes (TPVVs) are being used as the exported volumes to the servedAIX Logical Partitions (LPARs). Also, it is assumed that all of the TPVVs associated with an AIX LPARwill have scalable volume groups created on the TPVVs being served to the AIX LPAR.

NOTE: This feature is supported only with HP 3PAR OS 2.3.1 and later.

In the following example the AIX LPAR being served by dual VIO servers already has six HP 3PARStoreServ Storage virtual volumes that are accessible.

# lsdev -Cc diskhdisk0 Available Virtual SCSI Disk Drivehdisk1 Available Virtual SCSI Disk Drivehdisk2 Available Virtual SCSI Disk Drivehdisk3 Available Virtual SCSI Disk Drivehdisk4 Available Virtual SCSI Disk Drivehdisk5 Available Virtual SCSI Disk Drive

From the HP 3PAR StoreServ Storage, two new TPVVs will be created, exported to the VIO servers,and then mapped to the AIX LPAR. The new virtual volumes accessible to the AIX LPAR will thenhave scalable volume groups created on each.Create two TPVVs named vol1 and vol2 in CPG AIX, with an initial size of 7 G each:

# createtpvv AIX vol1 7G# createtpvv AIX vol2 7G

Export each of the created TPVVs with LUN IDs of 500 and 501 to each of the VIO servers:

# createvlun -f vol1 500 VIOS1# createvlun -f vol2 501 VIOS1# createvlun -f vol1 500 VIOS2# createvlun -f vol2 501 VIOS2

On each VIO server, scan for the newly created TPVVs using the command cfgdev.


The new HP 3PAR StoreServ Storage TPVVs discovered on each VIO server in this example wereassigned the values hdisk7 and hdisk8 by each of the VIO servers.Map each of the TPVVs to the AIX LPAR through both VIO servers:

$ mkvdev -vdev hdisk7 -vadapter vhost0 -dev vol1vol1 Available$ mkvdev -vdev hdisk8 -vadapter vhost0 -dev vol2vol2 Available

On the AIX LPAR, scan for the new virtual SCSI devices previously mapped and list the disks:

# cfgmgr# lsdev -Cc diskhdisk0 Available Virtual SCSI Disk Drivehdisk1 Available Virtual SCSI Disk Drivehdisk2 Available Virtual SCSI Disk Drivehdisk3 Available Virtual SCSI Disk Drivehdisk4 Available Virtual SCSI Disk Drivehdisk5 Available Virtual SCSI Disk Drivehdisk6 Available Virtual SCSI Disk Drivehdisk7 Available Virtual SCSI Disk Drive

Create scalable volume groups volume1 and volume2 on the two new disks:

# mkvg -S -s 1 -y volume1 hdisk60516-1254 mkvg: Changing the PVID in the ODM.volume1# mkvg -S -s 1 -y volume2 hdisk70516-1254 mkvg: Changing the PVID in the ODM.volume2

Verify the volume group geometry on each of the newly created scalable volumes groups. In thisexample, the partition size is 7099 megabytes for each.

Growing Virtual Volumes Exported to AIX LPARs 35

The HP 3PAR StoreServ Storage virtual volumes will now be grown to different values for each ofthe exported TPVVs:

# growvv vol1 205G# growvv vol2 478G

NOTE: When TPVVs are grown and are exported to VIO servers it is important to wait for aperiod before attempting to grow the AIX LPAR volume groups. In this case one minute wait wasused. Wait time can vary depending on many factors on the VIOS; however, HP testing has showntwo minutes is adequate.When growing a virtual volume that is exported to an LPAR served by VIO servers, it is advisableto stop any I/O in progress to the volume group being grown or I/O stalls may be seen. An I/Ostall is defined as a period of time where no I/O will occur to the virtual volume being grown.

Following a wait as noted above, the volumes groups can be changed on the AIX LPAR indicatingthe new size:

# chvg -g volume10516-1712 chvg: Volume group volume1 changed. volume1 can include up to 1024 physical volumes with 262144 total physical partitions in the volume group.

# chvg -g volume20516-1712 chvg: Volume group volume2 changed. volume2 can include up to 1024 physical volumes with 524288 total physical partitions in the volume group.

The new hdisk sizes can be viewed using the bootinfo –s command, or the lspv commandcan be used to display the new volume group sizes:


5 Removing HP 3PAR Devices on an AIX or IBM Virtual I/OServer Host

This chapter explains how to remove the HP 3PAR StoreServ Storage VVs from the AIX or IBMVirtual I/O Server host. Before physically disconnecting cables from the host or HP 3PAR StoreServStorage, remove the VVs from each device in the following sequence:1. AIX or IBM Virtual I/O Server host.2. HP 3PAR StoreServ Storage

NOTE: Performing a clean removal in this fashion insures the hdisk entry is removed from theAIX device data base so that if another LUN is exported in the future with the same LUN andcharacteristics, a device mismatch does not occur on the AIX or IBM Virtual I/O Server host.

Removing Fibre Channel Connected Devices on the HostWhen removing HP 3PAR StoreServ Storage VVs from the AIX or IBM Virtual I/O Server host,complete the following steps.

For the AIX host1. 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 -dl hdiskN.

NOTE: Remove the VVs from the host server before disconnecting the HP 3PAR StoreServStorage from the host server.

3. Issue lsdev -Cc disk on the AIX CLI to ensure the VLUN is removed.Example:

# lsdev -Cc diskhdisk0 Available 00-08-00 SAS Disk Drivehdisk1 Available 07-01-01 3PAR InServ Virtual Volumehdisk2 Available 07-01-01 3PAR InServ Virtual Volume

# rmdev -dl hdisk1hdisk1 deleted

# lsdev -Cc diskhdisk0 Available 00-08-00 SAS Disk Drivehdisk2 Available 07-01-01 3PAR InServ Virtual Volume

Removing Fibre Channel Connected Devices on the Host 37

For the IBM Virtual I/O Server• Locate and verify details of the VV by issuing lsdev -type disk.

CAUTION: This procedure removes the mapped virtual defined device from an LPAR.

NOTE: If this device has been mapped by the IBM Virtual I/O Server to another LPAR, it ishighly advisable to remove the mapping before attempting to removed the hdisk definition.

Example:To remove hdisk22, first check to see whether hdisk22 is mapped to another LPAR byissuing the lsmap -all command. Scan the output for any backing device that shows upas hdisk22 and remove this mapping for this virtual vdev definition.The backing device in this case for hdisk22 is as follows:

VTD biglunStatus AvailableLUN 0x9600000000000000Backing device hdisk22Physloc U789C.001.DQD2174-P1-C1-T1-W22410002AC000044-L1F4000000000000

First, remove the mapping:

$ rmvdev -vdev hdisk22biglun deleted

Then, remove the device:

$ rmdev -dev hdisk22hdisk22 deleted

Removing Fibre Channel Devices on the HP 3PAR StoreServ StorageTo remove a single exported VLUN from the AIX or IBM Virtual I/O Server host on the HP 3PARStoreServ Storage, complete the following steps.

38 Removing HP 3PAR Devices on an AIX or IBM Virtual I/O Server Host

For the AIX host1. Issue showvlun -host aixhost on the HP 3PAR StoreServ Storage.

# showvlun -host aixhostActive VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type0 TESTLUN.0 aixhost 10000000C9759527 1:4:1 host1 TESTLUN.1 aixhost 10000000C9759527 1:4:1 host0 TESTLUN.0 aixhost 10000000C9759526 1:4:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:4:1 host0 TESTLUN.0 aixhost 10000000C9759527 0:5:1 host1 TESTLUN.1 aixhost 10000000C9759527 0:5:1 host0 TESTLUN.0 aixhost 10000000C9759526 0:5:1 host1 TESTLUN.1 aixhost 10000000C9759526 0:5:1 host0 TESTLUN.0 aixhost 10000000C9759526 1:2:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:2:1 host0 TESTLUN.0 aixhost 10000000C9759527 1:2:1 host1 TESTLUN.1 aixhost 10000000C9759527 1:2:1 host0 TESTLUN.0 aixhost 10000000C9759527 0:4:1 host1 TESTLUN.1 aixhost 10000000C9759527 0:4:1 host0 TESTLUN.0 aixhost 10000000C9759526 0:4:1 host1 TESTLUN.1 aixhost 10000000C9759526 0:4:1 host0 TESTLUN.0 aixhost 10000000C9759526 1:5:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:5:1 host0 TESTLUN.0 aixhost 10000000C9759527 1:5:1 host1 TESTLUN.1 aixhost 10000000C9759527 1:5:1 host-------------------------------------------------------20 total VLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type0 TESTLUN.0 aixhost ---------------- --- host1 TESTLUN.1 aixhost ---------------- --- host------------------------------------------------------2 total

2. Issue removevlun -f TESTLUN.0 0 aixhost on the HP 3PAR StoreServ Storage.3. Issue showvlun -host aixhost to verify that the VLUN is removed on the HP 3PAR

StoreServ Storage.

# showvlun -host aixhostActive VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type1 TESTLUN.1 aixhost 10000000C9759527 1:4:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:4:1 host1 TESTLUN.1 aixhost 10000000C9759527 0:5:1 host1 TESTLUN.1 aixhost 10000000C9759526 0:5:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:2:1 host1 TESTLUN.1 aixhost 10000000C9759527 1:2:1 host1 TESTLUN.1 aixhost 10000000C9759527 0:4:1 host1 TESTLUN.1 aixhost 10000000C9759526 0:4:1 host1 TESTLUN.1 aixhost 10000000C9759526 1:5:1 host1 TESTLUN.1 aixhost 10000000C9759527 1:5:1 host-------------------------------------------------------10 totalVLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type1 TESTLUN.1 aixhost ---------------- --- host------------------------------------------------------1 total

Removing Fibre Channel Devices on the HP 3PAR StoreServ Storage 39

For the IBM Virtual I/O Server1. Issue showvlun -host VIOS1 on the HP 3PAR StoreServ Storage.

# showvlun -host VIOS1

Active VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 VIOS1boot VIOS1 10000000C9759841 3:5:1 host 10 AIX61boot_client1 VIOS1 10000000C9759841 3:5:1 host 50 VIOStest.0 VIOS1 10000000C9759841 3:5:1 host 51 VIOStest.1 VIOS1 10000000C9759841 3:5:1 host 52 VIOStest.2 VIOS1 10000000C9759841 3:5:1 host 53 VIOStest.3 VIOS1 10000000C9759841 3:5:1 host

VLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 VIOS1boot VIOS1 ---------------- --- host 10 AIX61boot_client1 VIOS1 ---------------- --- host 50 VIOStest.0 VIOS1 ---------------- --- host 51 VIOStest.1 VIOS1 ---------------- --- host 52 VIOStest.2 VIOS1 ---------------- --- host 53 VIOStest.3 VIOS1 ---------------- --- host

2. Issue removevlun -f VIOStest.3 53 VIOS1 on the HP 3PAR StoreServ Storage.3. Issue showvlun -host VIOS1 to verify that the VLUN is removed on the HP 3PAR StoreServ

Storage.

# showvlun -host VIOS1

Active VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 VIOS1boot VIOS1 10000000C9759841 3:5:1 host 10 AIX61boot_client1 VIOS1 10000000C9759841 3:5:1 host 50 VIOStest.0 VIOS1 10000000C9759841 3:5:1 host 51 VIOStest.1 VIOS1 10000000C9759841 3:5:1 host 52 VIOStest.2 VIOS1 10000000C9759841 3:5:1 host

VLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 VIOS1boot VIOS1 ---------------- --- host 10 AIX61boot_client1 VIOS1 ---------------- --- host 50 VIOStest.0 VIOS1 ---------------- --- host 51 VIOStest.1 VIOS1 ---------------- --- host 52 VIOStest.2 VIOS1 ---------------- --- host

40 Removing HP 3PAR Devices on an AIX or IBM Virtual I/O Server Host

6 Using IBM HACMP 5.5 with AIXInstalling IBM HACMP

HP supports HACMP 5.5 when using HP 3PAR MPIO 2.2 and when using HP 3PAR ODM 3.1 forIBM AIX using enhanced concurrent volume groups in multihost environments.

NOTE: The use of non-concurrent volume groups is not supported.Persistent reservation with HACMP 5.5 is not supported. Shared volume groups managed byHACMP 5.5 and accessed through HP 3PAR MPIO 2..2 must be enhanced concurrent mode.

There are no other special considerations for using HACMP. See the HP 3PAR Multipath I/O 2.2for IBM AIX User’s Guide for additional information.See IBM HACMP documentation for HACMP planning, setup and usage. These IBM HACMPdocuments are of particular importance:

• Concepts and Facilities Guide

• Planning and Installation Guide

• Administration Guide

HACMP Parameters for HP 3PAR StorageThere are no special settings required for IBM HACMP when using enhanced concurrent volumegroups that are different from settings specified by the IBM documentation for setting up enhancedconcurrent volume groups.

Installing IBM HACMP 41

7 Using IBM PowerHA 7.1 and PowerHA 6.1 with AIXInstalling IBM PowerHA 7.1 or PowerHA 6.1

HP supports PowerHA 7.1 (requires Fix Pack 3 minimum) and PowerHA 6.1 when using HP 3PARODM 3.1 for IBM AIX using enhanced concurrent volume groups in multihost environments.There are no other special considerations for using PowerHA 7.1 and PowerHA 6.1. See theReadme: HP 3PAR ODM 3.1 for additional information.Refer to IBM PowerHA 7.1 and PowerHA 6.1 documentation for planning, setup and usage. TheseIBM PowerHA 7.1 and PowerHA 6.1 documents are of particular importance:

• Concepts and Facilities Guide

• Planning and Installation Guide

• Administration Guide

PowerHA 7.1 and PowerHA 6.1 Parameters for HP 3PAR StorageThere are no special settings required for IBM PowerHA 7.1 and PowerHA 6.1 when usingenhanced concurrent volume groups that are different than specified by the IBM documentationwhen setting up enhanced concurrent volume groups.

42 Using IBM PowerHA 7.1 and PowerHA 6.1 with AIX

8 Booting from the HP 3PAR StoreServ StorageFor details about connecting the HP 3PAR StoreServ Storage to the host, see “Configuring theHP 3PAR StoreServ Storage for Fibre Channel” (page 7).

Setting the Host HBA Parameters for a SAN BootThe IBM FC HBA does not require any setting parameters on the host side when booting from theHP 3PAR StoreServ Storage.

Assigning LUNs as Boot VolumesOn the HP 3PAR StoreServ Storage, create a VV of appropriate size and export a VLUN to thehost definition that will be used to represent the AIX or IBM Virtual I/O Server host definition forbooting from an HP 3PAR StoreServ Storage.For details, see “Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or OS2.3.x” (page 7) and “Exporting LUNs to the AIX or IBM Virtual I/O Server Host” (page 29).For the purpose of the AIX or IBM Virtual I/O Server installation, restrict the connection from thehost to the HP 3PAR StoreServ Storage to a single path. Only a single path should be availableon the HP 3PAR StoreServ Storage and a single path on the host to the VLUN VV that will be theAIX or IBM Virtual I/O Server boot volume.

Installing the AIX or IBM Virtual I/O Server Host OS for a SAN BootInstallation of the AIX 7.1, AIX 6.1, AIX 5.3, or IBM Virtual I/O Server operating system is supportedwhen it is booted from the HP 3PAR StoreServ Storage. No special requirements are needed toinstall the AIX 7.1, AIX 6.1, AIX 5.3, or IBM Virtual I/O Server OS boot volume on the HP 3PARStoreServ Storage except for the installation of HP 3PAR ODM 3.1 for HP 3PAR OS 3.1.x or OS2.3.x and MPIO v2.2 for HP 3PAR OS 2.3.x or OS 2.2.x for AIX. Follow all recommended settingsand guides as covered in this document.

NOTE: During the installation phase, restrict the number of paths to the HP 3PAR StoreServStorage AIX or IBM Virtual I/O Server boot volume to a maximum of one.

NOTE: Once HP 3PAR ODM 3.1 or HP 3PAR MPIO 2.2 for AIX or IBM Virtual I/O Server hasbeen installed, it cannot be de-installed for a host boot disk.

AIX or IBM Virtual I/O Server host boot is supported by the HP 3PAR StoreServ Storage. To installthe AIX or IBM Virtual I/O Server operating system on HP 3PAR StoreServ Storage volumes,complete the following steps:1. Configure the HP 3PAR StoreServ Storage for the AIX system. See “Configuring the HP 3PAR

StoreServ Storage Running HP 3PAR OS 3.1.x or OS 2.3.x” (page 7) and “Exporting VLUNsto the AIX or IBM Virtual I/O Server Host” (page 29).

2. For AIX, perform the following tasks:a. Enter the SMS Menu and choose the options to boot from the CD-ROM.b. Follow the standard procedure as outlined by IBM for installing AIX on a bootable device.

For details, see IBM AIX documentation.c. At the end of the installation options, prior to the OS install, change the installation settings

by selecting the HP 3PAR StoreServ Storage volume. Deselect any other installationdevices.

d. Install the AIX or operating system on the selected HP 3PAR StoreServ Storage volume.

Setting the Host HBA Parameters for a SAN Boot 43

3. For the IBM Virtual I/O Server, perform the following tasks:a. Select the HP 3PAR StoreServ Storage LUN from the IBM SMS Menu to contain the OS

image.b. Follow the standard procedure as outlined by IBM for installing the IBM Virtual I/O Server

on a bootable device. For details, see IBM AIX documentation.c. Install the or IBM Virtual I/O Server operating system on the selected HP 3PAR StoreServ

Storage volume.4. Reboot the AIX or IBM Virtual I/O Server system. The HP 3PAR StoreServ Storage volume is

configured with the AIX default PCM.5. Install the HP 3PAR MPIO 2.2, or the HP 3PAR ODM 3.1 for IBM AIX, by completing the

following tasks:

NOTE: The commands within this section are performed from the IBM Virtual I/O Serveroem_setup_env environment and are designated as starting with a " # " on the commandline. To enter the oem_setup_env environment from the padmin user account, issue the AIXCLI command oem_setup_env.

NOTE: This installation must be performed by a user logged into the AIX system as thesuperuser or with root privileges.

a. Load the distribution CD containing the HP 3PAR MPIO/HP 3PAR ODM 3.1 for IBM AIXinto the CD drive.

CAUTION: Do not connect the AIX or IBM Virtual I/O Server host to mixed HBA typeson the HP 3PAR StoreServ Storage when using a direct connect mode. Boot failures ormissing paths may result. Use only like HBA types on the HP 3PAR StoreServ Storage.

b. Use smit update_all to install the HP 3PAR MPIO/HP 3PAR ODM 3.1 for IBM AIXfrom the distribution CD.Be sure to set the parameter ACCEPT new license agreements to Yes.

c. On the AIX CLI, issue bosboot -aDd /dev/ipldevice.

# bosboot -aDd /dev/ipldevicebosboot: Boot image is 25235 512 byte blocks.

6. Reboot the AIX or IBM Virtual I/O Server host.

44 Booting from the HP 3PAR StoreServ Storage

7. After the AIX or IBM Virtual I/O Server host completely boots and is online, connect additionalpaths to the Fabric or the HP 3PAR disk storage system directly by completing the followingtasks.a. On the HP 3PAR StoreServ Storage, add additional paths to the host definition already

created. Use the HP 3PAR StoreServ Storage CLI command createhost -addhostname WWN to add the additional paths to the defined HP 3PAR StoreServ Storagehost definition.

b. On the AIX host CLI, execute the cfgmgr command.On the IBM Virtual I/O Server host CLI, in the oem_setup_env environment, executethe cfgmgr command.

c. Verify that all paths appear on the HP 3PAR StoreServ Storage by issuing the followingcommand.For the AIX host:

# showhost -h aixhost

For the IBM Virtual I/O Server:

# showhost VIOS

8. To add the additional paths to the boot device configuration, choose one of the followingmethods:• Issue /usr/lib/methods/cfgefscsi –l fscsiX on the AIX or IBM Virtual I/O

Server CLI, where X is the additional path’s FC SCSI controller protocol device.

# /usr/lib/methods/cfgefscsi -l fscsi1hdisk0 # /usr/lib/methods/cfgefscsi -l fscsi2hdisk0 # /usr/lib/methods/cfgefscsi -l fscsi3hdisk0

OR

• Issue cfgmgr –vl hdiskX in the AIX or IBM Virtual I/O Server CLI, where X is theHP 3PAR StoreServ Storage volume for the host boot.

# cfgmgr -vl hdisk0----------------attempting to configure device 'hdisk0'Time: 0 LEDS: 0x626invoking /usr/lib/methods/cfgscsidisk -l hdisk0 Number of running methods: 1----------------Completed method for: hdisk0, Elapsed time = 0return code = 0****************** no stdout ***************************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------calling savebasereturn code = 0****************** no stdout ***********

Installing the AIX or IBM Virtual I/O Server Host OS for a SAN Boot 45

****************** no stderr ***********Configuration time: 0 seconds

9. To verify that the AIX or IBM Virtual I/O Server host recognizes multiple paths, issue lspath–l hdiskX where X is the HP 3PAR StoreServ Storage volume for the host boot.

# lspath -l hdisk0Enabled hdisk0 fscsi0Enabled hdisk0 fscsi1Enabled hdisk0 fscsi2Enabled hdisk0 fscsi3

10. Issue bosboot -aDd /dev/ipldevice on the AIX or IBM Virtual I/O Server CLI.11. Reboot the AIX or the IBM Virtual I/O Server system.All HP 3PAR StoreServ Storage virtual volumes, including the selected HP 3PAR StoreServ Storageboot volumes and any additional paths are now configured with the HP 3PAR PCM.

46 Booting from the HP 3PAR StoreServ Storage

9 Using Veritas Cluster Server with the AIX HostsThere are no special settings required when using Veritas Cluster other than the Veritas ASLrequirement.

NOTE: For Veritas Storage Foundation versions prior to 5.x, the Veritas DMP layer in VeritasVolume Manager does not recognize the storage server virtual volumes as being multipathed untilthe HP 3PAR ODM 3.1 for Veritas ASL for the HP 3PAR StoreServ Storage is installed. Startingwith Storage Foundation 5.x, the HP 3PAR/HP Veritas ASL is not required.

The HP 3PAR ODM 3.1 for the HP 3PAR StoreServ Storage can be obtained from the followingwebsite:http://www.symantec.com/business/support/

47

http://www.symantec.com/business/support/

10 AIX Client Path Failure Detection and RecoveryThis chapter explains how to set up the AIX client LPARs to enable client automatic path failuredetection and recovery in the event an IBM Virtual I/O Server goes down for any reason.

AIX Client Automatic Path Failure Detection and RecoveryWhen one of the VIO servers goes down for any reason, the vscsi path coming from that servershows as failed with the lspath command when executed from the virtualized AIX client.

# lspathFailed hdisk0 vscsi0Enabled hdisk0 vscsi1

Setting Auto Path Failure Detection and RecoveryEven though the VIO server comes back as available, the lspath command will still show one ofthe paths as missing. For automatic path failure detection and recovery on the AIX client, set theattributes hcheck_interval and hcheck_mode to 60 and nonactive, respectively. This willcause a path failure to be detected automatically and recovered automatically once the path hasreturned.

chdev -l hdiskN -a hcheck_interval=60 -Pchdev -l hdiskN -a hcheck_mode=nonactive -P

This task must be performed for each hdisk on the AIX client.The AIX client will need to be rebooted for the 'hcheck_interval' attribute changes to takeeffect.As new disks are added to the AIX client, the command to set the 'hckeck_interval' must beperformed for each new hdisk added. The same is true if an hdisk is removed (using the rmdev-l hdiskN -d command) from the AIX client and added again later.For further information regarding path failure detection and recovery, see the IBM manual at thefollowing website:http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/configuring_mpio_for_the_virtual_client.pdf

48 AIX Client Path Failure Detection and Recovery

http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/configuring_mpio_for_the_virtual_client.pdf

http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/configuring_mpio_for_the_virtual_client.pdf

11 Migrating the IBM Virtual I/O Server to V2.2.2.1 orV2.2.2.2

VIOS Migration Using the IBM Migration DVDThis section covers the precautions that must be adhered to if the IBM Virtual I/O Server is beingmigrated to VIOS version 2.2.2.1 or 2.2.2.2 from previous versions of VIOS using the IBM MigrationDVD. This section only applies to those IBM Virtual I/O Servers that have the VIOS Boot Disklocated on the HP 3PAR storage array. It is always strongly recommended that the VIOS systemand configuration be backed up in the event an issue occurs during the migration procedure.

Requirements for Migrating VIOS Version 2.2.2.1 or 2.2.2.2Before starting the VIOS migration to VIOS version 2.2.2.1 or 2.2.2.2 from previous versions ofVIOS using the IBM Migration DVD, reduce the number of paths to the VIOS boot disks on theHP 3PAR array to a single path.

WARNING! Before starting the VIOS migration to VIOS version 2.2.2.1 or 2.2.2.2 from previousversions of VIOS using the IBM Migration DVD, reduce the number of paths to the VIOS boot diskson the HP 3PAR array to a single path. Failure to perform this step may result in the inability toboot the VIOS from HP 3PAR array once the migration has completed.

REQUIREDIt is strongly recommended that the VIOS system and system configuration be backed up in theevent a issue occurs during the migration procedure.Once the number of paths have been reduced to a single path from the host to the HP 3PARStoreServ Storage and from the fabric to the HP 3PAR StoreServ Storage volumes containing theVIOS boot disk and related system disks, proceed with the upgrade using the IBM Migration DVD.

CAUTION: Once the number of paths have been reduced to a single path from the host to theHP 3PAR StoreServ Storage, proceed with the upgrade using the IBM Migration DVD.

Migrating to VIOS Version 2.2.2.1 or 2.2.2.2 from Previous VIOS VersionsOnce the requirements called out in “Booting from the HP 3PAR StoreServ Storage” (page 43)have been adhered to, follow the instructions covered in the IBM documentation on migrating yourIBM Virtual I/O Server to VIOS version 2.2.2.1 or 2.2.2.2. Install all mandatory updates asrequired that pertain to your environment as described by IBM. IBM procedures to perform theVIOS migration can be found on the following website:http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/home.html

Completing the VIOS Migration to VIOS Version 2.2.2.1 or 2.2.2.21. When VIOS is booted from HP 3PAR StoreServ Storage, reduce the numbers of paths to the

VIOS boot device to a single path.2. Perform the migration using the IBM documentation.3. Once the migration is complete, re-install HP 3PAR MPIO, making sure to use the options:

SOFTWARE to install 3PARmpio AUTOMATICALLY install requisite software? no OVERWRITE same or newer versions? yes ACCEPT new license agreements? yes

VIOS Migration Using the IBM Migration DVD 49

http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/home.html

4. Perform bosboot -aDd /dev/ipldevice.5. Reboot the VIO server.6. Add additional paths to the VIOS system disks that were removed in “Requirements for

Migrating VIOS Version 2.2.2.1 or 2.2.2.2” (page 49).7. Issue the bosboot -aDd /dev/ipldevice command.8. Reboot the VIO server.9. Verify all paths as operational.

50 Migrating the IBM Virtual I/O Server to V2.2.2.1 or V2.2.2.2

12 Cabling for IBM Virtual I/O Server ConfigurationsThis chapter provides cabling and configuration details for connections between the HP 3PARStoreServ Storage and the IBM Virtual I/O Server.

Cabling and Configuration for Fabric Configurations (Dual VIO)The following diagram shows the cabling and configuration for a fabric configuration:

Figure 1 Cabling and Configuration for Fabric Configurations

Cabling and Configuration for Fabric Configurations (Dual VIO) 51

Cabling and Configuration for Direct Connect Configurations (Dual VIO)The following diagram shows the cabling and configuration for a direct connect configuration:

Figure 2 Cabling and Configuration for Direct Connect Configurations

52 Cabling for IBM Virtual I/O Server Configurations

13 PowerVM Live Partition MobilityIBM live partition mobility (LPM) allows the migration of an active AIX partition from one physicalserver to another. The partition can be powered off, or fully active with users logged in and I/Oin progress.LPM is simply a function of the IBM Virtual I/O Server. To make an IBM Virtual I/O Server capableof LPM, the servers must be licensed through the COD product enablement under PowerVM.Additionally, when initially building an IBM Virtual I/O Server, the LPAR must be enabled as amover service partition. When building a mobile partition, the option to allow this partition to besuspended must be enabled.For detailed instructions about setting up this environment, refer to IBM documentation on theinstallation and configuration specifics of PowerVM.All resources defined to a mobile partition must be virtualized. This includes disks presented to themobile partition by means of vSCSI or NPIV.HP 3PAR ODM must be installed on the IBM Virtual I/O Server that is hosting the mover servicepartition. This package must be installed whether or not the IBM Virtual I/O Server is locally bootedfrom the internal hard-drive or SAN booted from the HP 3PAR disk array. If N_Port ID Virtualization(NPIV)-type disks are being used over virtualized FC on the mobile partition, the HP 3PAR ODMmust also be installed on the mobile partition.

NOTE: All IBM Virtual I/O Server FC HBAs connected to the HP 3PAR storage array must haveboth Dynamic Tracking and Fast_Fail enabled. Failure to set these options may result inan error during pre-migration validation. This is especially true if a Fibre Channel path has a failedpath.

To change the FC HBA options for Dynamic Tracking and Fast_Fail, issue the followingcommand from each HP 3PAR-connected IBM Virtual I/O Server from the oem_setup_env shell

NOTE: An IBM Virtual I/O Server reboot is required to make these changes permanent.

$ oem_setup_env

To set up Dynamic Tracking and FastFail on an IBM Fibre Channel HBA, complete the followingsteps, using the SMIT Devices menu: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 following options:

• Dynamic Tracking of FC Devices+Yes

• FC Fabric Event Error RECOVERY Policy+FastFail

• Apply change to DATABASE only+Yes6. Exit the shell.7. Reboot the IBM Virtual I/O Server.At this point, devices may be presented to the IBM Virtual I/O Server and exported to the mobileLPAR by creating a vSCSI device mapped through a vhost.There are no other 3PAR/HP SAN array-specific settings required to support LPM.For information about supported versions of HP 3PAR ODM and PowerVM Virtual I/O Server, seethe appropriate interoperability information, which is available on HP SPOCK:

53


NOTE: LPM is not supported by HP 3PAR OS 2.2.4.

54 PowerVM Live Partition Mobility


14 Support and Other ResourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/support

Before contacting HP, collect the following information:

• Product model names and numbers

• Technical support registration number (if applicable)

• Product serial numbers

• Error messages

• Operating system type and revision level

• Detailed questionsSpecify the type of support you are requesting:

Support requestHP 3PAR storage system

StoreServ 7000 StorageHP 3PAR StoreServ 7200, 7400, and 7450 Storagesystems

3PAR or 3PAR StorageHP 3PAR StoreServ 10000 Storage systemsHP 3PAR T-Class storage systemsHP 3PAR F-Class storage systems

HP 3PAR documentation

See:For information about:

The Single Point of Connectivity Knowledge for HPStorage Products (SPOCK) website:

Supported hardware and software platforms


The HP 3PAR StoreServ Storage site:Locating HP 3PAR documentshttp://www.hp.com/go/3parTo access HP 3PAR documents, click the Support link foryour product.

HP 3PAR storage system software

HP 3PAR StoreServ Storage Concepts GuideStorage concepts and terminology

HP 3PAR Management Console User's GuideUsing the HP 3PAR Management Console (GUI) to configureand administer HP 3PAR storage systems

HP 3PAR Command Line Interface Administrator’sManual

Using the HP 3PAR CLI to configure and administer storagesystems

HP 3PAR Command Line Interface ReferenceCLI commands

HP 3PAR System Reporter Software User's GuideAnalyzing system performance

HP 3PAR Host Explorer User’s GuideInstalling and maintaining the Host Explorer agent in orderto manage host configuration and connectivity information

HP 3PAR CIM API Programming ReferenceCreating applications compliant with the Common InformationModel (CIM) to manage HP 3PAR storage systems

Contacting HP 55

http://www.hp.com/support


http://www.hp.com/go/3par


HP 3PAR-to-3PAR Storage Peer Motion GuideMigrating data from one HP 3PAR storage system to another

HP 3PAR Secure Service Custodian Configuration UtilityReference

Configuring the Secure Service Custodian server in order tomonitor and control HP 3PAR storage systems

HP 3PAR Remote Copy Software User’s GuideUsing the CLI to configure and manage HP 3PAR RemoteCopy

HP 3PAR Upgrade Pre-Planning GuideUpdating HP 3PAR operating systems

HP 3PAR F-Class, T-Class, and StoreServ 10000 StorageTroubleshooting Guide

Identifying storage system components, troubleshootinginformation, and detailed alert information

HP 3PAR Policy Server Installation and Setup GuideInstalling, configuring, and maintaining the HP 3PAR PolicyServer HP 3PAR Policy Server Administration Guide

56 Support and Other Resources


Planning for HP 3PAR storage system setupHardware specifications, installation considerations, power requirements, networking options, and cabling information

for HP 3PAR storage systems

HP 3PAR StoreServ 7000 Storage Site Planning ManualHP 3PAR 7200, 7400, and 7450 storage systemsHP 3PAR StoreServ 7450 Storage Site Planning Manual

HP 3PAR StoreServ 10000 Storage Physical PlanningManual

HP 3PAR 10000 storage systems

HP 3PAR StoreServ 10000 Storage Third-Party RackPhysical Planning Manual

Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7000 Storage Installation GuideInstalling 7200, 7400, and 7450 storage systems andinitializing the Service Processor HP 3PAR StoreServ 7450 Storage Installation Guide

HP 3PAR StoreServ 7000 Storage SmartStart SoftwareUser’s Guide

HP 3PAR StoreServ 7000 Storage Service GuideMaintaining, servicing, and upgrading 7200, 7400, and7450 storage systems HP 3PAR StoreServ 7450 Storage Service Guide

HP 3PAR StoreServ 7000 Storage Troubleshooting GuideTroubleshooting 7200, 7400, and 7450 storage systemsHP 3PAR StoreServ 7450 Storage Troubleshooting Guide

HP 3PAR Service Processor Software User GuideMaintaining the Service ProcessorHP 3PAR Service Processor Onsite Customer Care(SPOCC) User's Guide

HP 3PAR host application solutions

HP 3PAR Recovery Manager Software for Oracle User'sGuide

Backing up Oracle databases and using backups for disasterrecovery

HP 3PAR Recovery Manager Software for MicrosoftExchange 2007 and 2010 User's Guide

Backing up Exchange databases and using backups fordisaster recovery

HP 3PAR Recovery Manager Software for Microsoft SQLServer User’s Guide

Backing up SQL databases and using backups for disasterrecovery

HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere User's Guide

Backing up VMware databases and using backups fordisaster recovery

HP 3PAR VSS Provider Software for Microsoft WindowsUser's Guide

Installing and using the HP 3PAR VSS (Volume Shadow CopyService) Provider software for Microsoft Windows

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Implementation Guide

Best practices for setting up the Storage Replication Adapterfor VMware vCenter

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Troubleshooting Guide

Troubleshooting the Storage Replication Adapter for VMwarevCenter Site Recovery Manager

HP 3PAR VAAI Plug-in Software for VMware vSphereUser's Guide

Installing and using vSphere Storage APIs for ArrayIntegration (VAAI) plug-in software for VMware vSphere

HP 3PAR documentation 57

Typographic conventionsTable 2 Document conventions

ElementConvention

Bold text • Keys that you press

• Text you typed into a GUI element, such as a text box

• GUI elements that you click or select, such as menu items, buttons,and so on

Monospace text • File and directory names

• System output

• Code

• Commands, their arguments, and argument values

<Monospace text in angle brackets> • Code variables

• Command variables

Bold monospace text • Commands you enter into a command line interface

• System output emphasized for scannability

WARNING! Indicates that failure to follow directions could result in bodily harm or death, or inirreversible damage to data or to the operating system.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

NOTE: Provides additional information.

RequiredIndicates that a procedure must be followed as directed in order to achieve a functional andsupported implementation based on testing at HP.

HP 3PAR branding information• The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ

Storage system."• The operating system previously referred to as the "InForm OS" is now referred to as the "HP

3PAR OS."• The user interface previously referred to as the "InForm Management Console (IMC)" is now

referred to as the "HP 3PAR Management Console."• All products previously referred to as “3PAR” products are now referred to as "HP 3PAR"

products.

58 Support and Other Resources

15 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

59

mailto:[email protected]

Documents

Hp 3par Aix and Ibm Virtual Io Server