3par Aix Implementation Guide

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-97765Published: March 2014

Copyright 2014 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, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor'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 express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall

not 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.................................................................................................................................5

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........................................10Configuring 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.............................................................................................14OS Specific Expected Behavior............................................................................................14HP 3PAR OS Persistent Ports................................................................................................14

Fibre Channel...............................................................................................................15HP 3PAR OS Persistent Ports Limitations............................................................................15

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

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

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

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

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..............................................................................................................21

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

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

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

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

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

Contents 3

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

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

Creating Virtual SCSI Devices for Connected LPARs.....................................................................30Growing Virtual Volumes Exported to AIX LPARs.........................................................................33

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

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

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

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

9 Using Veritas Cluster Server with the AIX Hosts.............................................4610 Using Symantec Storage Foundation.........................................................4711 AIX Client Path Failure Detection and Recovery............................................48

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

12 Migrating the IBM Virtual I/O Server.........................................................49VIOS Migration Using the IBM Migration DVD...........................................................................49Requirements for Migrating VIOS..............................................................................................49Migrating from Previous VIOS Versions......................................................................................49Completing the VIOS Migration................................................................................................49

13 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

14 PowerVM Live Partition Mobility................................................................5315 Support and Other Resources...................................................................55

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

16 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 representative hardware and software configurations.

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 ConfigurationsFC connections are supported between the HP 3PAR StoreServ Storage and the AIX host server inboth 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:HP 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

HP Support CenterHP 3PAR StoreServ 7000 Storage

HP Support CenterHP 3PAR StoreServ 10000 Storage

HP Support CenterHP 3PAR Storage Systems

HP Support CenterHP 3PAR StoreServ Software Device Management

HP Support CenterHP 3PAR StoreServ SoftwareReplication

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 followingpage on the HP Support Center (SC) website:HP Support CenterFor complete details about supported host configurations and interoperability, consult the HPSPOCK website:HP 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.

Supported Configurations 5

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

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 FC and how to set up the fabric when running HP 3PAROS 3.1.x, OS 2.3.x, or OS 2.2.x. For information on setting up the physical connection for aparticular 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, seeSetting 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 b. controlport config host -ct loop

where -ct loop specifies a direct connection.

c. controlport rst 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 .

# controlport offline 1:5:1

3. To configure the port to the host server, issue controlport config host -ct point, 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 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] [...]

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 ---

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

NOTE: When the LUNs are presented to an AIX VIO client using NPIV, the AIX host OS (persona8) should be used. In the case of LUNs presented to the IBM Virtual I/O Server and then presentedto the AIX client using vSCSI, IBM Virtual I/O Server host OS (persona 8) should be used. BothAIX and IBM Virtual I/O Server host OS types use persona 8, which means, from a host perspective,that there is no difference in behavior from the array. The IBM Virtual I/O Server host OS can beused as an administrative tool to keep track of which LUNs are presented to the IBM Virtual I/OServer, and which are presented to the AIX VIO clients directly.

NOTE: See the HP 3PAR Command Line Interface Reference or the HP 3PAR Management ConsoleUsers Guide for complete details on using the controlport, createhost, and showhostcommands.These documents are available on the following page of the HP SC website:HP Support Center

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.

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 8 by issuing controlport

persona 8 , where is the port location, expressed as node:slot:port.2. Issue controlport vcn disable -f .

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

controlport persona 8 , where is the port location, expressed asnode:slot:port.

2. Issue controlport vcn disable -f 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 *(8) 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] [...]


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 FC end-devices have access to each other on the fabric. Zoning alsoisolates the host server and HP 3PAR StoreServ Storage ports from Registered State ChangeNotifications (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).FC switch vendors support the zoning of the fabric end-devices in different zoning configurations.There are advantages and disadvantages with each zoning configuration. Choose a zoningconfiguration based on your needs.The HP 3PAR StoreServ Storage array supports 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.

Connecting the HP 3PAR StoreServ Storage to the Host 11

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, available on the followingwebsite:HP SAN Design Reference GuideIf 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.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 following website:HP SAN Design Reference Guide

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.

Setting Up and Zoning the Fabric 13

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 HP 3PAR Priority Optimization (Quality of Service) on the HP 3PARStoreServ Storage array, please read the HP 3PAR Priority Optimization technical white paperavailable on the following website:HP 3PAR Priority Optimization

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 importantthat 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.

HP 3PAR OS Persistent PortsThe HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during anHP 3PAR StoreServ Storage online upgrade or node-down event (online upgrade, node reboot,or cable pull test). Port shutdown or reset events do not trigger this feature.Each FC target storage array port has a partner array port automatically assigned by the system.Partner ports are assigned across array node pairs.HP 3PAR OS Persistent Ports allows an HP 3PAR StoreServ Storage FC port to assume the identity(port IP address) of a failed port while retaining its own identity. Where a given physical portassumes the identity of its partner port, the assumed port is designated as a persistent port. Arrayport failover and failback with HP 3PAR OS Persistent Ports is transparent to most host-basedmultipathing software, which can keep all of its I/O paths active.

NOTE: Use of HP 3PAR OS Persistent Ports technology does not negate the need for properlyinstalled, configured, and maintained host multipathing software.

For a more complete description of the HP 3PAR OS Persistent Ports feature, its operation, and acomplete list of required setup and connectivity guidelines, see the following:

HP Technical white paper HP 3PAR StoreServ Persistent Ports (HP document#F4AA4-4545ENW)This document is available on the following HP SC website:HP Support Center

HP 3PAR Command Line Interface Administrators Manual, Using Persistent Ports forNondisruptive Online Software UpgradesThis document is available on the following HP SC website:HP Support Center


Fibre Channel

HP 3PAR OS Persistent Ports Setup and Connectivity Guidelines for FC

Starting with HP 3PAR OS 3.1.2, the HP 3PAR OS Persistent Ports feature is supported for FCtarget ports.Starting with HP 3PAR OS 3.1.3, the Persistent Port feature has additional functionality to minimizeI/O disruption during an array port loss_sync event triggered by a loss of array port connectivityto fabric.

HP 3PAR OS Persistent Ports Setup and Connectivity Guidelines for FC

Specific cabling setup and connectivity guidelines need to be followed for HP 3PAR OS PersistentPorts to function properly:

HP 3PAR StoreServ Storage FC partner ports must be connected to the same FC Fabric andswitch.

The FC fabric being used must support NPIV, and NPIV must be enabled.

The hostfacing HBAs must be configured for point-to-point fabric connection (there is nosupport for direct-connect loops).

HP 3PAR OS Persistent Ports LimitationsWhen the FC target port fails over to its partner port as part of the HP 3PAR OS Persistent Portsfeature, I/O will be redirected by the HP 3PAR StoreServ Storage to the partner port. During thepersistent port failover, an AIX host may detect and report a temporary path loss in the AIX errptlog. This applies to HP 3PAR ODM installations as well as to Symantec Storage Foundation/DMPinstallations with AIX and HP 3PAR StoreServ Storage.HP recommends enabling the 3par_pathmon.sh script that is provided with HP 3PAR ODM 3.1when using the HP 3PAR OS Persistent Port feature. See the README provided with the HP 3PARODM 3.1 for instructions and usage.The HP Persistent Ports feature is not supported with iSCSI.

Setting Up and Zoning the Fabric 15

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:HP SPOCK

For the AIX host

NOTE: The following examples do not necessarily reflect supported versions or the latest versionof AIX and VIOS. They are intended only as examples. See the HP SPOCK website for supportedversions of AIX and VIOS:HP SPOCK

To 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.

16 Connecting the Host Server with Fibre Channel

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 individual HBA FC ports that belong to an installed FC adapter, 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 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 fruFRU 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 Z9Device 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 on theAIX CLI:

# lscfg -vps -l fcs0 | grep -i networkNetwork Address.............10000000C94E6031

where 10000000C94E6031 is the HBA WWN.

Installing the IBM Fibre Channel HBA 17

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

Setting Host HBA Parameters DynamicTracking and FastFailThe following settings are required on the IBM FC HBAs for the DynamicTracking and FastFailparameters.Direct connect:

DynamicTracking disabled

FastFail enabled

Fabric connect:

DynamicTracking enabled

FastFail enabled

NOTE: These parameters need to be changed on the AIX host or the IBM Virtual I/O Server. Thehost requires 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 DynamicTracking 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 following options:

Dynamic Tracking of FC Devices to Yes.

FC Fabric Event Error RECOVERY Policy to FastFail

Apply change to DATABASE only to Yes

6. Exit the shell.7. Restart the AIX host or IBM Virtual I/O Server.

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/O


Server host. This installation must be performed by a user logged into the AIX system with rootprivileges.

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 following page of the HP SC website:HP Support Center

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 fscsi4

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

Enabled 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 ().

# lspath -l hdisk1 -F status name parent connectionEnabled 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.


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 and OS 2.3.x support the HP 3PAR ODM 3.1 for the AIX nativemultipathing solution (default path control module (PCM) and the native MPIO framework).

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

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 21

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 ().

# 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 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 documentation. To obtain this documentation,search the HP SC website:HP Support Center

Additional HP 3PAR ODM SettingsFor details about AIX HP 3PAR ODM, see the HP 3PAR ODM 3.1 Software for IBM documentation.To obtain this documentation, search the HP SC website:HP Support Center

NOTE: For AIX installations in other than en_US language convention, an ODM file must becopied to additional locations to enable the OS to correctly display the 3PAR VV label of an hdiskinstance. The copy (cp) commands are:cp /usr/lib/nls/msg/en_US/3par.cat /usr/lib/methods/3par.catandcp /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.

Installing the HP 3PAR ODM 3.1 to use with Veritas 23

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 diskhdisk0 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.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 and 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.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 www.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.

Installing Veritas as the Multipathing Solution 25

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.catandcp /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.


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 Administrators Manual. Fora comprehensive description of HP 3PAR OS commands, see the HP 3PAR Command Line InterfaceReference. To obtain a copy of this documentation, see the HP SC website: HP Support Center

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:ActionsProvisioningVirtual VolumeCreate Virtual Volume

2. 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 Users 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 following page of the HP SC website:HP Support Center

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

Creating Storage on the HP 3PAR StoreServ Storage 27

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 Administrators Manual

HP 3PAR Command Line Interface Reference

These documents are available on the following page of the HP SC website:HP Support Center

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]

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.

specifies name of the VV being exported as a virtual LUN.

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

indicates that is the starting LUN number.

indicates that hostname is the name of the host created inCreating 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.

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

Restrictions on Volume Size and NumberFollow the guidelines for creating virtual volumes (VVs) and Virtual LUNs (VLUNs) in the HP 3PARCommand Line Interface Administrators 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, 0511.

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

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

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


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

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:

Creating Virtual SCSI Devices for Connected LPARs 31

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.




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:

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

On VIOS2, the command is:

$ mkvdev -vdev hdisk23 -vadapter vhost0 -dev newvdev newvdev Available

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.

Growing Virtual Volumes Exported to AIX LPARs 33

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.

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 typically 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:

Growing Virtual Volumes Exported to AIX LPARs 35

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

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

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.

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

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

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

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 VIOStes

Documents

3par Aix Implementation Guide