HP 3par Citrix Implementation Guide

HP 3PAR Citrix Implementation Guide

AbstractThis implementation guide provides the information you need to configure an HP 3PAR StoreServ Storage with Citrix 6.x or5.x. General information is also provided on the basic steps required to allocate storage on the HP 3PAR StoreServ Storagethat can then be accessed by the Citrix host.

HP Part Number: QL226-97876Published: September 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

Citrix is a registered trademark of Citrix Systems, Inc. and/or one more of its subsidiaries, and may be registered in the United States Patent and

Trademark Office and in other countries.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

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

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.2.x, 3.1.x or OS 2.3.x................7

Configuring 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

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

Configuration Guidelines for FC Switch Vendors....................................................................11Target Port Limits and Specifications for FC............................................................................12HP 3PAR Priority Optimization for FC...................................................................................13HP 3PAR OS Persistent Ports for FC.......................................................................................13

Setup and Connectivity Guidelines..................................................................................13

3 Configuring the HP 3PAR StoreServ Storage for iSCSI....................................15Configuring the HP 3PAR StoreServ Storage...............................................................................15Configuring Ports for an iSCSI Connection.................................................................................15Creating the Software iSCSI Host Definition................................................................................17Target Port Limits and Specifications..........................................................................................18HP 3PAR Priority Optimization for iSCSI.....................................................................................18HP 3PAR OS Persistent Ports for iSCSI........................................................................................19

Setup and Connectivity Guidelines.......................................................................................19

4 Connecting a Host with Fibre Channel/FCoE...............................................20Installing the Emulex HBA/CNA...............................................................................................20

Emulex OneCommand Command Line Interface.....................................................................20Modifying the nodev-tmo Parameter to a Value of 1...............................................................20

Installing the QLogic HBA/CNA...............................................................................................21SCLI Command Line Interface..............................................................................................22Modifying the qlport_down_retry Parameter to a Value of 10...................................................22

Setting Up Multipathing...........................................................................................................22Setting Up Device-mapper...................................................................................................22Modifying the /etc/multipath-enabled.conf File for Citrix 5.5...................................................23Modifying the /etc/multipath.conf File for Citrix 5.6 or 6.x.....................................................24Enabling Multipath.............................................................................................................25

HP 3PAR OS Persistent Ports for FCoE........................................................................................25Setup and Connectivity Guidelines.......................................................................................26

5 Connecting a Host with Software iSCSI.......................................................27Configuring Citrix 6.x or 5.6 for iSCSI.......................................................................................27

iSCSI on Citrix 6.x or 5.6....................................................................................................27Setting Up iSCSI for Citrix 6.x or 5.6....................................................................................27Configuring Citrix 6.x or 5.6 iSCSI Settings with Device Mapper Multipathing...........................28Starting the iSCSI Daemon for Citrix 6.x or 5.6......................................................................28Creating the iSCSI Connection in Citrix 6.x or 5.6 Using the iscsiadm Command.......................29

Discovering iSCSI Devices and Creating Storage Repositories with Citrix 6.x or 5.6.........................30Configuring CHAP for the iSCSI Host........................................................................................30

Setting the Host CHAP Authentication on the HP 3PAR StoreServ Storage..................................30Setting the Host CHAP for Citrix...........................................................................................31

Contents 3

Setting Up the Bidirectional CHAP on the HP 3PAR StoreServ Storage.......................................32Setting the Bidirectional CHAP for Citrix................................................................................32

6 Allocating Storage for Access by the Citrix Host...........................................35Creating Storage on the HP 3PAR StoreServ Storage...................................................................35

Creating Virtual Volumes....................................................................................................35Creating Thinly-provisioned Virtual Volumes...........................................................................36

Exporting LUNs to the Host......................................................................................................36Restrictions on Volume Size and Number...................................................................................37Discovering Fibre Channel Devices and Creating Storage Repositories with Citrix............................37

7 Booting the Host from the HP 3PAR StoreServ Storage...................................38HP 3PAR StoreServ Storage Setup Requirements..........................................................................38Citrix Host HBA BIOS Setup Considerations...............................................................................38

Booting from the HP 3PAR StoreServ Storage Using QLogic HBAs............................................38Booting from the HP 3PAR StoreServ Storage Using Emulex HBAs.............................................39Booting from the HP 3PAR StoreServ Storage Using Brocade HBAs...........................................40

Configuring the Brocade HBA using the BCU Utility....................................................................40

8 Modifying HP 3PAR Devices on the Host.....................................................41Displaying Detailed Device-mapper Node Information.................................................................41Removing a Storage Volume from the Host.................................................................................41

Citrix XenCenter................................................................................................................42Citrix XenServer Server (Host Console Tab)............................................................................42

9 Configuring Citrix Resource Pools................................................................4310 Using Citrix High Availability...................................................................4411 Support and Other Resources...................................................................45

Contacting HP........................................................................................................................45HP 3PAR documentation..........................................................................................................45Typographic conventions.........................................................................................................48HP 3PAR branding information.................................................................................................48

12 Documentation feedback.........................................................................49

4 Contents

1 IntroductionThis implementation guide provides the information you need to configure an HP 3PAR StoreServStorage with Citrix 5.x or 6.x XenServer. General information is also provided on the basic stepsrequired to allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by theCitrix host.The information contained in this implementation guide is the outcome of careful testing of the HP3PAR StoreServ Storage with as many representative hardware and software configurations aspossible.

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 ConfigurationsThe following types of host connections are supported between the HP 3PAR StoreServ Storageand hosts running the Citrix XenServer operating system (Citrix XenServer) OS:

Fibre Channel (FC)

Software iSCSI initiator

Fibre Channel over Ethernet (FCoE)

Fibre Channel connections are supported between the HP 3PAR StoreServ Storage and the citrixhost in both a fabric-attached and direct-connect topology.For information about supported hardware and software platforms, see the HP Single Point ofConnectivity Knowledge (HP SPOCK) website:http://www.hp.com/storage/spock

NOTE: For more information about HP 3PAR storage products, follow the links in Table 1:HP 3PAR Storage Products (page 5).

Table 1 HP 3PAR Storage Products

See...Product

HP Storage Information LibraryHP 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 ConsiderationsThis implementation guide refers to new installations for information about planning an onlineHP 3PAR Operating System (HP 3PAR OS) upgrade, see the HP 3PAR Operating System UpgradePre-Planning Guide, on the HP Storage Information Library:http://www.hp.com/go/storage/docsFor complete details about supported host configurations and interoperability, see the SupportMatrix on the HP SPOCK website:http://www.hp.com/storage/spock

Supported Configurations 5

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 citrix and the HP3PAR OS.This guide provides basic information for establishing communication between the HP 3PARStoreServ Storage and the citrix host and allocating the required storage for a given configuration.See the appropriate HP documentation in conjunction with the citrix host and Host Bus Adapter(HBA) documentation for specific details and procedures.

6 Introduction

2 Configuring the HP 3PAR StoreServ Storage for FibreChannel

This chapter explains how to establish a Fibre Channel connection between an HP 3PAR StoreServStorage and a citrix host using Fibre Channel and covers HP 3PAR OS 3.2.x and 3.1.x. Forinformation on setting up the physical connection for a particular HP 3PAR StoreServ Storage, seethe appropriate HP 3PAR installation manual.

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

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

This section describes how to configure the HP 3PAR StoreServ Storage.

NOTE:

Complete the following setup before connecting the HP 3PAR StoreServ Storage port to thehost.

When deploying HP Virtual Connect Direct-Attach Fibre Channel storage for HP 3PAR StoreServStorage systems, where the HP 3PAR StoreServ Storage ports are cabled directly to the uplinkports on the HP Virtual Connect FlexFabric 10 Gb/24-port Module for c-Class BladeSystem,follow the steps for configuring the HP 3PAR StoreServ Storage ports for a fabric connection.

For more information about HP Virtual Connect, HP Virtual Connect interconnect modules,and the HP Virtual Connect Direct-Attach Fibre Channel feature, and the HP SAN DesignReference Guide, see the HP Support Center website:HP Support Center

Download Brocade HBA drivers, firmware, and the BCU utility from the QLogic website at:http://www.qlogic.com. Specific Brocade drivers are named with a BR prefix, such as BR-xxxHBA model.This link will take you outside the Hewlett-Packard website. HP does not control and is notresponsible for information outside of HP.com.

Configuring the HP 3PAR StoreServ Storage for a Direct ConnectionTo configure HP 3PAR StoreServ Storage ports for a direct connection to the citrix host, completethe following steps:

NOTE: Direct connect is not supported by the 16 Gb Fibre Channel 3PAR StoreServ targetinterface.

In the following examples, loop denotes a direct connection and point denotes a fabricconnection.Run the following HP 3PAR OS command line interface (CLI) commands with the appropriateparameters for each direct connect port:

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

1. Take the port off line using the controlport offline command.Example:

# controlport offline 1:5:1

2. Run the controlport config host -ct loop command where-ct loop specifies a direct connection.Example:

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

3. Reset the port by running controlport rst command on the HP3PAR StoreServ Storage.Example:

# controlport rst 1:5:1

After all the ports are configured, verify that they are configured for a host in a direct connectionby running the showport -par command on the HP 3PAR StoreServ Storage.

NOTE: Target Mode Write Optimization (TWMO) is enabled starting in the HP 3PAR OS 3.2.1release. It is supported on 8 Gb Target HBAs in host connection mode.

# 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 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 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 fabric connections on the HP 3PAR OS CLI usethe following procedure. You must complete these steps for each port.1. Check if a port is configured for a host port in fabric mode by running the HP 3PAR OS CLI

command showport -par on the HP 3PAR StoreServ Storage.

# showport parN:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNoteWwn VCN IntCoal0:0:1 disk loop auto 2Gbps disabled disabled disabled enabled

8 Configuring the HP 3PAR StoreServ Storage for Fibre Channel

0: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 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 point 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

2. If the port has not been configured, take the port offline before configuring it for connectionto a host.

CAUTION: Before taking a port offline in preparation for a fabric connection, you mustverify that it was not previously defined and that it is not connected to a host because thiswould interrupt the existing host connection. If an HP 3PAR StoreServ Storage port is alreadyconfigured for a fabric connection ignore this step.

To take the port offline, run the controlport offline commandon the HP 3PAR StoreServ Storage. For example:

# controlport offline 1:5:1

3. To configure the port to the host, run the controlport config host -ct point command on the HP 3PAR StoreServ Storage, where -ct pointindicates that the connection type is a fabric connection. For example:

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

4. Reset the port by running the controlport rst command on theHP 3PAR StoreServ Storage. For example:

# controlport rst 1:5:1

Creating the Host DefinitionBefore connecting the citrix host to the HP 3PAR StoreServ Storage, create a host definition thatspecifies a valid host persona on the HP 3PAR StoreServ Storage that is to be connected to a hostHBA port through a fabric or a direct connection.1. To create host definitions, issue the createhost [options] [...]

command.In the following example, the generic indicates that the default persona is used.

# createhost -persona 1 Citrixhost 1122334455667788 1122334455667799Setting default host persona 1 (Generic)

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

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

# showhostId Name Persona -WWN/iSCSI_Name- Port 6 Citrixhost Generic 1122334455667788 --- 1122334455667799 ---

NOTE: HP recommends host persona 1. Using Host Persona 1 will enable the SES deviceon this host. As a result, exporting a LUN on ID 254 will require a host restart before it canbe discovered and used as a storage repository.

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 HP Storage Information Library at the following website:http://www.hp.com/go/storage/docs

Connecting the HP 3PAR StoreServ Storage to the HostDuring this stage, connect the HP 3PAR StoreServ Storage to the host directly or to the fabric. Thesetasks include the step to physically cable the HP 3PAR StoreServ Storage to the host or fabric.

Setting Up and Zoning the FabricNOTE: This section does not apply when deploying HP Virtual Connect Direct-Attach FibreChannel storage for HP 3PAR storage systems, where the HP 3PAR StoreServ Storage ports arecabled directly to the uplink ports on the HP Virtual Connect FlexFabric 10 Gb/24-port Modulefor c-Class BladeSystem. Zoning is automatically configured based on the Virtual Connect SANFabric and server profile definitions.For more information about HP Virtual Connect, HP Virtual Connect interconnect modules, HP VirtualConnect Direct-Attach Fibre Channel feature, and the HP SAN Design Reference Guide on thefollowing HP Support Center website:HP Support Center

Fabric zoning controls which FC end-devices have access to each other on the fabric. Zoning alsoisolates the host and HP 3PAR StoreServ Storage ports from Registered State Change Notifications(RSCNs) that are irrelevant to these ports.Set up fabric zoning by associating the device World Wide Names (WWNs) or the switch portswith specified zones in the fabric. Use either the WWN method or the port zoning method withthe HP 3PAR StoreServ Storage, the WWN zoning method is recommended because the zonesurvives 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 HBA ports and HP 3PAR StoreServ Storage ports before connecting the host HBAports or HP 3PAR StoreServ Storage ports to the fabrics.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 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.

NOTE:

For high availability and clustered environments that require multiple initiators to accessthe same set of target ports, HP recommends creating separate zones for each initiatorwith the same set of target ports.

The storage targets in the zone need to be from the same HP 3PAR StoreServ Storage ormultiple HP 3PAR StoreServ Storage systems.

If 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 corrective action.After configuring, zoning and connecting each host HBA port and HP 3PAR StoreServ Storageport to the fabrics, verify the switch and zone configurations using the HP 3PAR OS CLI showhostcommand, to ensure that each initiator is zoned with the correct targets.Verify the switch and zone configurations using the HP 3PAR OS CLI showhost command tomake sure each initiator is zoned with the correct targets after you complete the following tasks:

Complete configuration of the storage port to the host and connect to the switch. SeeConfiguring Ports on the HP 3PAR StoreServ Storage for a Fabric Connection (page 8) formore information.

Create a zone configuration on the switch following the HP SAN Design Reference Guideand enable the zone set configuration.

Use the showhost command to verify that the host is seen on the storage node.

Configuration Guidelines for FC Switch VendorsUse the following FC switch vendor guidelines before configuring ports on fabrics to which the HP3PAR StoreServ Storage connects. Brocade switch ports that connect to a host HBA port or to an HP 3PAR StoreServ Storage

port should be set to their default mode. On Brocade 3xxx switches running Brocade firmware3.0.2 or later, verify that each switch port is in the correct mode using the Brocade telnetinterface 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 Gb 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

Setting Up and Zoning the Fabric 11

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 Gb 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 and the FOS release notes, on the Brocadewebsite: https:/www.brocade.com

NOTE: This link will take you outside the Hewlett-Packard website. HP does not control andis not responsible for information outside of HP.com.

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 theHP SN3000B 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.

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

Maximum of 32 host ports per HP 3PAR StoreServ Storage port, with a maximum total of1,024 host ports per HP 3PAR StoreServ Storage.

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

Emulex 4 Gb: 959

HP 3PAR HBA 4 Gb: 1638

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

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

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. If this condition occurs, each host should be throttled so that itcannot overrun the HP 3PAR StoreServ Storage port's queues when all hosts are deliveringtheir maximum number of I/O requests.

NOTE:

When host ports can access multiple targets on fabric zones, the target number assignedby the host driver for each discovered target can change when the host is booted andsome targets are not present in the zone. This situation may change the device nodeaccess point for devices during a host restart. This issue can occur with anyfabric-connected storage, and is not specific to the HP 3PAR StoreServ Storage.

The maximum number of I/O paths supported is 16.


HP 3PAR Priority Optimization for FCThe HP 3PAR Priority Optimization feature introduced in HP 3PAR OS 3.1.2.MU2 is a more efficientand dynamic solution for managing server workloads and can be utilized as an alternative tosetting host I/O throttles. Using this feature, a storage administrator is able to share storageresources more effectively by enforcing quality of service limits on the array. No special settingsare needed on the host side to obtain the benefit of HP 3PAR Priority Optimization although certainper target or per adapter throttle settings may need to be adjusted in rare cases. For completedetails of how to use HP 3PAR Priority Optimization (Quality of Service) on HP 3PAR StoreServStorage arrays, see the HP 3PAR Priority Optimization technical whitepaper, on the HP website:HP 3PAR Priority Optimization

HP 3PAR OS Persistent Ports for FCThe HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HP3PAR StoreServ Storage online upgrade, node-down event, or cable pull. Port shutdown or resetevents 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 identityof a failed port (World Wide Port Name) while retaining its own identity. Where a given physicalport assumes the identity of its partner port, the assumed port is designated as a persistent port.Array port 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 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

The HP 3PAR Command Line Interface Administrators Manual, Using Persistent Ports forNondisruptive Online Software UpgradesThis document is available on the HP Storage Information Library at:http://www.hp.com/go/storage/docs

Setup and Connectivity GuidelinesStarting 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 the fabric.

Setting Up and Zoning the Fabric 13

Follow the specific cabling setup and connectivity guidelines so that HP 3PAR OS Persistent Portsfunction properly:

HP 3PAR StoreServ Storage FC partner ports must be connected to the same FC fabric, andpreferably to different FC switches on the fabric.

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

Configure the host-facing HBAs for point-to-point fabric connection (there is no support fordirect-connect loops).

For information regarding the Persistent Ports feature for an FCoE initiator to FC target configuration(FCoE to FC switched), see Configuring the HP 3PAR StoreServ Storage for Fibre Channel (page7).


3 Configuring the HP 3PAR StoreServ Storage for iSCSIConfiguring the HP 3PAR StoreServ Storage

To configure 1 Gb iSCSI target ports on the HP 3PAR StoreServ Storage for connection to an iSCSIInitiator, perform the following steps:1. Check the current settings of the iSCSI ports by issuing the showport -iscsi command.

The following examples are for the 1 Gb iSCSI ports on the array.

# showport -iscsiN:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port0:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 31 1500 n/a 0 0.0.0.0 0.0.0.0 32050:3:2 loss-sync 0.0.0.0 0.0.0.0 0.0.0.0 32 1500 n/a 0 0.0.0.0 0.0.0.0 32051:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 131 1500 n/a 0 0.0.0.0 0.0.0.0 3205

1:3:2 loss-sync 0.0.0.0 0.0.0.0 0.0.0.0 132 1500 n/a 0 0.0.0.0 0.0.0.0 3205

2. Set up the IP address and netmask address of the iSCSI target ports by issuing thecontroliscsiport addr [-f] command.

# controliscsiport addr 10.0.100.101 255.255.255.0 -f 0:3:1# controliscsiport addr 10.0.101.201 255.255.255.0 -f 1:3:1

3. Verify the changed settings by issuing the showport -iscsi command.

4. If the host is connected to the IP fabric and its Ethernet interface has been configured, you canissue the ping command to verify that the Ethernet switch ports where the HP 3PAR StoreServStorage iSCSI target ports and iSCSI Initiator host connect are visible to each other.

Configuring Ports for an iSCSI Connection10 Gb iSCSI ports on HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 arrays require aone-time configuration using the controlport command. HP 3PAR S-Class, T-Class, and F-Classdo not support 10 Gb HBAs. Use the showport and showport -i commands to verify theconfiguration setting.For example:

# showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol0:3:1 suspended config_wait - - cna -0:3:2 suspended config_wait - - cna -

# showport -iN:S:P Brand Model Rev Firmware Serial HWType0:3:1 QLOGIC QLE8242 58 0.0.0.0 PCGLT0ARC1K3SK CNA0:3:2 QLOGIC QLE8242 58 0.0.0.0 PCGLT0ARC1K3SK CNA

Configuring the HP 3PAR StoreServ Storage 15

NOTE: The steps for configuring iSCSI software on the HP 3PAR StoreServ Storage iSCSI portsto connect to a Host with Software iSCSI initiator are the same as for a Host with Hardware iSCSIinitiator.

1. If State=config_wait or Firmware=0.0.0.0, use the controlport config iscsi command to configure. Use the showport and showport -i commands to verifythe configuration setting.For example:

# controlport config iscsi 0:3:1# controlport config iscsi 0:3:2# showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol...

0:3:1 target ready - 2C27D7521F3E iscsi iSCSI0:3:2 target ready - 2C27D7521F3A iscsi iSCSI# showport -i...

N:S:P Brand Model Rev Firmware Serial HWType...

0:3:1 QLOGIC QLE8242 58 4.8.76.48015 PCGLT0ARC1K3U6 CNA0:3:2 QLOGIC QLE8242 58 4.8.76.48015 PCGLT0ARC1K3U6 CNA

2. If the State value is config_wait or the Firmware value is 0.0.0.0, enter thecontrolport config iscsi command to configure the iSCSI ports. Forexample:

# controlport config iscsi 0:3:1# controlport config iscsi 0:3:2

3. Confirm that the port is configured by entering the following commands: showport andshowport -i. A successful configuration shows the State value as ready and theFirmware value displays the firmware version. For example:

# showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol...

0:3:1 target ready - 2C27D7521F3E iscsi iSCSI0:3:2 target ready - 2C27D7521F3A iscsi iSCSI# showport -i...

N:S:P Brand Model Rev Firmware Serial HWType...

0:3:1 QLOGIC QLE8242 58 4.8.76.48015 PCGLT0ARC1K3U6 CNA0:3:2 QLOGIC QLE8242 58 4.8.76.48015 PCGLT0ARC1K3U6 CNA

4. Check the current settings of the iSCSI ports by issuing showport -iscsi.For example:

# showport -iscsiN:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port0:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 31 1500 n/a 0 0.0.0.0 0.0.0.0 32050:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 32 1500 n/a 0 0.0.0.0 0.0.0.0 32051:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 131 1500 n/a 0 0.0.0.0 0.0.0.0 32051:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 132 1500 n/a 0 0.0.0.0 0.0.0.0 3205----------------------------------------------------------------------------------------

4

16 Configuring the HP 3PAR StoreServ Storage for iSCSI

5. To set up the IP address and netmask address of the iSCSI target ports, run thecontroliscsiport addr [-f] command. For example:

# controliscsiport addr 10.100.0.101 255.255.0.0 -f 0:3:1# controliscsiport addr 10.101.0.201 255.255.0.0 -f 1:3:1

6. Verify the changed settings by issuing showport -iscsi.For example:

# showport -iscsiN:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port0:3:1 ready 10.100.0.101 255.255.0.0 0.0.0.0 31 1500 1Gbps 0 0.0.0.0 0.0.0.0 32050:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 32 1500 n/a 0 0.0.0.0 0.0.0.0 32051:3:1 ready 10.101.0.201 255.255.0.0 0.0.0.0 131 1500 1Gbps 0 0.0.0.0 0.0.0.0 32051:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 132 1500 n/a 0 0.0.0.0 0.0.0.0 3205--------------------------------------------------------------------------------------------------

4

7. Issue the controliscsiport ping command to verifythat the switch ports where the HP 3PAR StoreServ Storage iSCSI target ports and iSCSI initiatorhost connection are visible to each other.For example:

# controliscsiport ping 10.0.100.101 0:3:1Ping succeeded

NOTE: When the iSCSI initiator host port and the HP 3PAR StoreServ Storage target portare in different IP subnets, the gateway address for the HP 3PAR StoreServ Storage port shouldbe configured in order to avoid unexpected behavior.See the HP 3PAR Command Line Interface Reference or the HP 3PAR Management ConsoleUsers Guide for complete details on using the controliscsiport command.These documents are available on the HP Storage Information Library at:http://www.hp.com/go/storage/docs

Creating the Software iSCSI Host DefinitionThis section describes how to create an iSCSI host definition.

NOTE: If multiple initiator ports are used, add the following to /etc/sysctl.conf:

net.ipv4.conf.all.arp_filter = 1

NOTE: To be able to establish an iSCSI Initiator connection/session with the iSCSI target portfrom the host, you must create a host definition entry, create the iSCSI host definition, and configurethe HP 3PAR StoreServ Storage iSCSI target ports.For details, see Creating the iSCSI Connection in Citrix 6.x or 5.6 Using the iscsiadm Command(page 29).This link will take you outside the Hewlett-Packard website. HP does not control and is not responsiblefor information outside of HP.com.

Creating the Software iSCSI Host Definition 17

1. Verify that the iSCSI Initiator is connected to the iSCSI target port with the HP 3PAR OS CLIshowhost command.

# showhostId Name Persona ----------WWN/iSCSI_Name---------------- Port-- iqn.2010-07.com.dl380g5-11:dd59da96 0:3:1 iqn.2010-07.com.dl380g5-11:dd59da96 1:3:1

NOTE: HP recommends Host persona 1.

2. Create an iSCSI host definition entry by issuing the HP 3PAR OS CLI createhost -iscsi-persona 1 command.Example:

# createhost -iscsi -persona 1 DL380g5-11_Xen-iscsi iqn.2010-07.com.dl380g5-11:dd59da96Setting host persona 1 (Generic)

NOTE: For citrix 5.6 or 6.x, get the iSCSI initiator name from:

# cat /etc/iscsi/initiatorname.iscsiInitiatorName=iqn.2010-07.com.dl380g5-11:dd59da96InitiatorAlias=sqa-dl380g5-11

3. Verify that the host entry has been created.

Id Name Persona ----------WWN/iSCSI_Name---------------- Port0 DL380g5-11_Xen-iscsi Generic iqn.2010-07.com.dl380g5-11:dd59da96 0:3:1 iqn.2010-07.com.dl380g5-11:dd59da96 1:3:1

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

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

QLogic 1G: 512

QLogic 10G: 2048 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systemsonly)

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

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 port. This condition can result in erratic I/Operformance on each host. If this condition occurs, each host should be throttled so that itcannot overrun the HP 3PAR StoreServ port's queues when all hosts are delivering theirmaximum number of I/O requests.

HP 3PAR Priority Optimization for iSCSIThe HP 3PAR Priority Optimization feature introduced in HP 3PAR OS 3.1.2.MU2 is an efficientand dynamic solution for managing server workloads and can be used as an alternative to settinghost I/O throttles. Using this feature, a storage administrator can share storage resources effectively

18 Configuring the HP 3PAR StoreServ Storage for iSCSI

by enforcing quality of service limits on the array. No special settings are needed on the host sideto obtain the benefit of HP 3PAR Priority Optimization although certain per target or per adapterthrottle settings may need to be adjusted. For complete details on how to use HP 3PAR PriorityOptimization (Quality of Service) on HP 3PAR StoreServ Storage arrays, see the HP 3PAR PriorityOptimization technical whitepaper (HP document #4AA4-7604ENW) on the HP website:http://www8.hp.com/h20195/v2/GetDocument.aspx?docname=4AA4-7604ENW

HP 3PAR OS Persistent Ports for iSCSIThe HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HP3PAR StoreServ Storage online upgrade, node-down event, or cable pull event. Port shutdown orreset events do not trigger this feature.Each iSCSI 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 iSCSI port to assume the identityof a failed port (World Wide Port Name) while retaining its own identity. Where a given physicalport assumes the identity of its partner port, the assumed port is designated as a persistent port.Array port 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.



The 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

The HP 3PAR Command Line Interface Administrators Manual, Using Persistent Ports forNondisruptive Online Software UpgradesThis document is available on the HP Storage Information Library:http://www.hp.com/go/storage/docs

Setup and Connectivity Guidelines Starting with HP 3PAR OS 3.1.3, the HP 3PAR OS Persistent Ports feature is supported for

iSCSI. The HP 3PAR OS Persistent Ports feature is enabled by default for HP 3PAR StoreServStorage iSCSI ports during node-down events.

Follow the specific cabling setup and connectivity guidelines for HP 3PAR OS Persistent Portsto function properly.

A key element for iSCSI connectivity is that partner ports must share the same IP network.

A persistent port is not triggered with a Loss_of_Sync condition such as, cable pull or switchport disable event on the storage facing switch port or controlport offline .

HP 3PAR OS Persistent Ports for iSCSI 19

4 Connecting a Host with Fibre Channel/FCoEThis chapter describes the tasks necessary for connecting the host Fibre Channel or Fibre Channelover Ethernet (FCoE).

Installing the Emulex HBA/CNAInstall the Emulex host bus adapters (HBAs) or CNAs in the host according to the documentationprovided with the HBAs/CNAs and host.

Emulex OneCommand Command Line Interface1. Determine an Emulex driver that was already installed by the citrix installation by issuing the

following command:

# cat /sys/module/lpfc/version

If no Emulex driver was installed, see the HP SPOCK website for supported drivers:http://www.hp.com/storage/spockDownload the driver from one of the following websites and install it:http://www.citrix.comhttp://www.emulex.com/downloads

NOTE: These links will take you outside the Hewlett-Packard website. HP does not controland is not responsible for information outside of HP.com.

2. The Emulex FC/FCoE utility hbacmd is installed during the citrix installation.

Modifying the nodev-tmo Parameter to a Value of 1

NOTE: For citrix 6.x or 5.6, it is not required to change the Emulex driver parameter nodev-tmoto a value of 1.

This section describes how to modify the nodev-tmo parameter using hbacmd. See Emulexdocumentation for usage of hbacmd, available at the following website.http://www.emulex.com/downloads

NOTE: This link will take you outside the Hewlett-Packard website. HP does not control and isnot responsible for information outside of HP.com.

The tool is at /usr/sbin/ocmanager/hbacmd with default installation.Use the following procedure to obtain the available command usage and syntax as well as setnodev-tmo parameter:1. To display usage, issue ./hbacmd.2. To list installed HBA's Port WWN, issue the following command:

./hbacmd ListHBAs

3. To invoke the syntax for the SetDriverParam command, issue the following command:

# ./hbacmd Help DriverParams

20 Connecting a Host with Fibre Channel/FCoE

4. To set the nodev-tmo parameter, issue the following command:

# ./hbacmd SetDriverParam G P nodev-tmo 1

5. To verify that the parameter is set correctly, issue the following command:

# ./hbacmd GetDriverParam

Output from the foregoing commands is shown below:

# ./hbacmd ListHBAsManageable HBA List

Port WWN : 10:00:00:00:c9:7b:07:52Node WWN : 20:00:00:00:c9:7b:07:52Fabric Name: 10:00:08:00:88:a0:5c:adFlags : 8000f100Host Name : sqa-dl380g5-08Mfg : Emulex CorporationSerial No. : VM82281959Port Number: 0Mode : Initiator. . .

# ./hbacmd Help DriverParams. . .

SetDriverParam Flag1: {L G} L: Local (i.e. this adapter only) G: Global (i.e. all adapters on this host) Flag2: {P T} P: Permanent (i.e. Persists across reboot) T: Temporary Param: Name of parameter whose value is to be set Value: Input as decimal, prefix with 0x to input as hex. . .

./hbacmd SetDriverParam 10:00:00:00:c9:7b:07:52 G P nodev-tmo 1

# ./hbacmd GetDriverParams 10:00:00:00:c9:7b:07:52Driver Params for 10:00:00:00:c9:7b:07:52. Values in HEX format.DX string Low High Def Cur Exp Dyn00: log-verbose 0 ffff 0 0 1 101: lun-queue-depth 1 80 1e 1e 1 202: scan-down 0 1 1 1 1 203: nodev-tmo 0 ff 1e 1 1 104: topology 0 6 0 0 1 205: link-speed 0 8 0 0 1 206: fcp-class 2 3 3 3 1 2. . .

Installing the QLogic HBA/CNAInstall the QLogic host bus adapters/converged network adapters in the host based on thedocumentation provided with the HBAs/CNAs and host.

Installing the QLogic HBA/CNA 21

SCLI Command Line InterfaceUse scli with the in-box QLogic driver from the citrix installation.

For FC, the scli utility is installed under /opt/QLogic_Corporation/SANsurferCLI. For FCoE, the scli utility is installed under /opt/QLogic_Corporation/

QConvergeConsoleCLI. Verify version installed with rpm.

Example:

# rpm -qa scliscli-1.7.1-23

Make the following selection from the scli menu:

Select HBA Parameters from the Main Menu.

Modifying the qlport_down_retry Parameter to a Value of 10The scli utility refers to this parameter as Port Down Retry Count. See the documentation providedby QLogic for details about the scli tool.To set the value to 10, complete the following steps from the scli menu.1. Select Main MenuHBA ParametersConfigure HBA Parameters.2. Select Port Down Retry Count from the Configure Parameters menu and set it to 10.3. Select Commit Changes from the Configure Parameters menu.4. Repeat 1 through 3 for each HBA installed.5. To verify changes, use Display HBA Parameters from the HBA Parameters main menu.6. Add options qla2xxx qlport_down_retry=10 to /etc/modprobe.conf7. After restarting the host, check

/sys/module/qla2xxx/parameters/qlport_down_retry to confirm the changes.

NOTE: If the HP 3PAR StoreServ Storage array is running an HP 3PAR OS version earlierthan OS 3.1.3, set the qlport_down_retry setting to 1 rather than 10.

Example:

# cat /sys/module/qla2xxx/parameters/qlport_down_retry10

Setting Up Multipathing

Setting Up Device-mapperMultipath tools and Device-mapper packages are installed during default citrix OS installation.Check for installed Device-mapper packages by issuing rpm -qa |grep device-mapper:

# rpm -qa|grep device-mapperdevice-mapper-1.02.39-1.el5_5.2device-mapper-event-1.02.39-1.el5_5.2device-mapper-multipath-0.4.7-34.xs651


Modifying the /etc/multipath-enabled.conf File for Citrix 5.5The /etc/multipath.conf file is used by device mapper where the multipathing parametershave been set.Do notmodify /etc/multipath.conf. citrix links it to either /etc/multipath-enabled.confor /etc/multipath-disabled.conf depending on whether multipathing is enabled ordisabled.The default installed /etc/multipath-enabled.conf file must be edited to make the followingchanges:1. Verify devnode * in blacklist section is commented out or removed:

devnode *}

2. Edit the devices structure to add entries for HP 3PAR StoreServ Storage array and removeother product entries that are not needed.After all of the edits are made, the relevant sections of /etc/multipath-enabled.confdevices section should appear as follows:

# cat /etc/multipath-enabled.conf

defaults { polling_interval 5}

devices { device { vendor "3PARdata" product "VV" no_path_retry 12 features "0" hardware_handler "0" path_grouping_policy multibus path_selector "round-robin 0" rr_weight uniform rr_min_io 100 path_checker tur failback immediate }}

NOTE: The /etc/multipath-enabled.conf file is replaced when installing citrixupdates to the citrix. Reapply the multipath-enabled.conf changes to each host afterupdates. HP recommends creating a backup copy of the /etc/multipatch-enabled.conffile before upgrading to any MU on the citrix.

If SCSI devices such as the internal boot disk need to be excluded from being seen by devicemapper, the devices should be added into in devnode blacklist structure.Example: The system is booted through an internal SCSI boot disk and has a device instancesda, which is excluded from being seen by the device mapper by adding the devnodeblacklist structure. The resulting /etc/multipath-enabled.conf file blacklist sectionappears as follows:

# cat /etc/multipath-enabled.confblacklist { wwid 26353900f02796769 devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z]"

Setting Up Multipathing 23

devnode "^sda$" devnode "^sda[0-9]" devnode "^cciss!c[0-9]d[0-9]*"}

NOTE: Add other devices as necessary to the blacklist structure as per the configured host.

Modifying the /etc/multipath.conf File for Citrix 5.6 or 6.xThe /etc/multipath.conf file is used by device mapper where the multipathing parametershave been set.The default installed /etc/multipath.conf file must be edited to make the following changes:1. Verify that devnode * in the blacklist section is commented out or removed:

#blacklist {# devnode "*"#}

2. Edit the devices structure to add entries for HP 3PAR array and remove other product entriesthat are not needed.After all of the edits are made, the relevant sections of /etc/multipath.conf devicessection should appear as follows:

# cat /etc/multipath.conf

defaults { polling_interval 5}

devices { device { vendor "3PARdata" product "VV" no_path_retry 12 features "0" hardware_handler "0" path_grouping_policy multibus path_selector "round-robin 0" rr_weight uniform rr_min_io 100 path_checker tur failback immediate }}

NOTE: The /etc/multipath.conf file is replaced when installing citrix updates to thecitrix. Reapply the multipath-enabled.conf changes to each host after updates. HPrecommends creating a backup copy of the /etc/multipath.conf file before upgradingto any MU on the citrix.

If SCSI devices such as the internal boot disk need to be excluded from being seen by devicemapper, the devices should be added into in devnode blacklist structure.Example: The system is booted through an internal SCSI boot disk and has a device instancesda, which is excluded from being seen by the device mapper by adding the devnode


blacklist structure. The resulting /etc/multipath.conf file blacklist section appears asfollows:

# cat /etc/multipath.confblacklist { wwid 26353900f02796769 devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z]" devnode "^sda$" devnode "^sda[0-9]" devnode "^cciss!c[0-9]d[0-9]*"}

NOTE: Add other devices as necessary to the blacklist structure as per the configured host.

Enabling MultipathIf multipathing has not yet been enabled, use the following procedure to enable multipathing oneach citrix host with citrix XenCenter. For details, see Citrix XenServer Design: ConfiguringMultipathing for XenServer, available on the following website:Citrix Knowledge Center1. In the Resources pane, select the server and set it to Maintenance Mode.2. On the General tab, click Properties, then click the Multipathing tab.3. To enable multipathing, select the Enable multipathing on this server check box.4. Click OK to apply the new setting and close the dialog box.5. Exit from Maintenance Mode.

NOTE: Multipathing can also be enabled by using the Citrix XenServer CLI. For details, see theCitrix XenServer Administrators Guide for details, available at the Citrix Knowledge Center:Citrix Knowledge Center

HP 3PAR OS Persistent Ports for FCoEThe HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HP3PAR StoreServ Storage online upgrade or node-down event. Port shutdown or reset events do nottrigger this feature.Each FCoE 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 FCoE port to assume the identityof a failed port (World Wide Port Name) while retaining its own identity. Where a given physicalport assumes the identity of its partner port, the assumed port is designated as a persistent port.Array port 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.


HP 3PAR OS Persistent Ports for FCoE 25


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

the HP 3PAR Command Line Interface Administrators Manual, Using Persistent Ports forNondisruptive Online Software UpgradesThis document is available on the HP Storage Information Library :http://www.hp.com/go/storage/docs

Setup and Connectivity GuidelinesStarting with HP 3PAR OS 3.1.3 the HP 3PAR OS Persistent Ports feature is enabled by default forHP 3PAR StoreServ Storage FCoE ports during node-down events.Follow the specific cabling setup and connectivity guidelines for HP 3PAR OS Persistent Ports tofunction properly. Key elements for the HP 3PAR OS Persistent Ports feature setup and connectivityare:

HP 3PAR StoreServ Storage FCoE partner ports must be connected to the same FCoE network.

The same CNA port on host-facing HBAs in the nodes of a node pair must be connected tothe same FCoE network, and preferably to different FCoE switches on the network.

The FCoE network must support NPIV, and NPIV must be enabled.

A persistent port is not triggered with a Loss_of_Sync condition such as cable pull orswitch port disable event on the storage facing switch port or controlport offline .


5 Connecting a Host with Software iSCSIConfiguring Citrix 6.x or 5.6 for iSCSI

iSCSI on Citrix 6.x or 5.6iSCSI is installed by default with the install of citrix 6.x or 5.6. The iscsiadm utility is acommand-line tool that allows discovery and login to iSCSI targets. This tool also provides accessand management of the open-iscsi database. The following steps are required to discoverLUNs:1. Discover targets at a given IP address.2. Establish iSCSI login with the node record ID found during the target discovery process.3. Record iSCSI session statistics information.

NOTE: HP 3PAR storage systems do not support hardware iSCSI with Citrix XenServer.

Setting Up iSCSI for Citrix 6.x or 5.6In citrix 6.x or 5.6, you must manually create the initiatorname.iscsi file under /etc/iscsi.1. Create the /etc/iscsi/initiatorname.iscsi file.2. Add a line with theInitiatorName information:

InitiatorName= [InitiatorName from XenCenter]

For example:

InitiatorName=iqn.2011-10.com.3pardata:f8b6f263

You can adjust the iSCSI timers for better iSCSI session management and iSCSI I/O pathmanagement. iSCSI timers and session parameters are specified in /etc/iscsi/iscsid.conffile.The replacement_timeout iSCSI timeout parameter prevents I/O errors from propagating tothe application by controlling how long the iSCSI layer should wait for a timed-out path/sessionto reestablish itself before failing any commands on it. The default replacement_timeout valueis 120 seconds.To adjust the iSCSI timers, complete the following steps:1. Open /etc/iscsi/iscsid.conf and edit the following line to adjust

replacement_timeout:

node.session.timeo.replacement_timeout = [replacement_timeout]

2. Set this parameter to 15 seconds for a faster failover.

node.session.timeo.replacement_timeout = 15

NOTE: If the HP 3PAR StoreServ Storage array is running an HP 3PAR OS version earlierthan OS 3.1.3, set the replacement_timeout setting to 5 rather than 15.

Configuring Citrix 6.x or 5.6 for iSCSI 27

3. To control how often a ping is sent by the iSCSI initiator to the iSCSI target, change thefollowing parameter.

node.conn[0].timeo.noop_out_interval = [replacement_timeout]

To detect problems quickly in the network, the iSCSI layer sends iSCSI pings to the target. Ifthe ping times out, the iSCSI layer responds by failing running commands on the path wherethe pings failed.

4. Set this parameter to 10 seconds.

node.conn[0].timeo.noop_out_interval = 10

5. To specify the time to wait for a Nop-out response before failing the connection, change thefollowing parameter: node.conn[0].timeo.noop_out_timeout =[noop_out_timeout]

6. If the HP 3PAR array is running HP 3PAR OS 3.1.3 or later, set this parameter to 5 seconds:node.conn[0].timeo.noop_out_timeout = 5

7. To set the host log into the iSCSI nodes every time the iSCSI daemon is started or the host isrestarted, edit the iSCSI configuration in /etc/iscsi/iscsid.conf and change the valuesof the following default settings:

node.startup = automaticnode.conn[0].startup = automatic

NOTE: The node.conn[0] .startup variable is optional and not defined in the defaultiscsid configuration file.Consult citrix document CTX122852, iSCSI Service (open-iscsi) Startup Best Practices forXenServer for full details on configuring iSCSI startup on the Host.For more details, see the Citrix XenServer configuration limits, available at the Citrix KnowledgeCenter:http://support.citrix.comThis link will take you outside the Hewlett-Packard website. HP does not control and is notresponsible for information outside of HP.com.

8. To prevent one host from using up all the I/O buffers, you will need to throttle the host I/Oby reducing the node.session.cmds_max and node.session.queue_depth values.

9. Enable any other configuration changes such as CHAP authentication. For details, seeConfiguring CHAP for the iSCSI Host (page 30).

Configuring Citrix 6.x or 5.6 iSCSI Settings with Device Mapper MultipathingTo configure citrix 6.x or 5.6 iSCSI settings using Device Mapper multipathing, see Modifyingthe /etc/multipath.conf File for Citrix 5.6 or 6.x (page 24)

Starting the iSCSI Daemon for Citrix 6.x or 5.6To start the iSCSI daemon for the citrix host, complete the following steps:1. To start the open-iscsi module, issue the following command:

# service open-iscsi startStarting iSCSI initiator service: [ OK ]

28 Connecting a Host with Software iSCSI

Setting up iSCSI targets: iscsiadm: No records found!iscsiadm: no records found!

2. After open-iscsi is started, you can check the state of the open-iSCSI service run level informationwith the chkconfig command. Run level 5 should be on. For example:

# chkconfig --list | grep iscsiiscsi 0:off 1:off 2:off 3:off 4:off 5:on 6:off

Creating the iSCSI Connection in Citrix 6.x or 5.6 Using the iscsiadm CommandAfter connecting the host to the HP 3PAR StoreServ Storage iSCSI target port, use the iscsiadmcommand to create the iSCSI connection, complete following steps:1. Discover the target node using the iscsiadm command in discovery mode:

iscsiadm -m discovery -t sendtargets -p :.

For example:

# iscsiadm -m discovery -t sendtargets -p 10.0.100.101:326010.0.100.101:3260,31 iqn.2000-05.com.3pardata:20310002ac000079

2. The contents of the discovery can be viewed using the iscsiadm -m discovery command.For example:

# iscsiadm -m discovery10.0.100.101:3260 via sendtargets

3. Identify the iSCSI node login that record has been discovered from the discovery process.iscsiadm -m node -T -p :-l.For example:

# iscsiadm -m node -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.0.100.101:3260 -lLogging in to [iface: default, target: iqn.2000-05.com.3pardata:20310002ac000079, portal: 10.0.100.101,3260]Login to [iface: default, target: iqn.2000-05.com.3pardata:20310002ac000079, portal: 10.0.100.101,3260]: successful

4. The content of the login node can be viewed using the iscsiadm command.For example:

# iscsiadm -m node -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.0.100.101:326010.0.100.101:3260,31 iqn.2000-05.com.3pardata:20310002ac000079

5. Now examine the iSCSI session and content session of the node info by issuing iscsiadm-m session.For example:

# iscsiadm -m sessiontcp: [1] 10.0.100.101:3260,31 iqn.2000-05.com.3pardata:20310002ac000079

Configuring Citrix 6.x or 5.6 for iSCSI 29

Discovering iSCSI Devices and Creating Storage Repositories with Citrix6.x or 5.6

NOTE: iSCSI is not supported with citrix 5.5.

To discover iSCSI devices and create storage repositories with XenCenter, follow these steps:1. In the Resources pane, select the server to create a new storage repository.2. On the toolbar, click Storage, and then click New SR.3. Select Software iSCSI, and then click Next.4. Change the default name if necessary, and then click Next.5. Enter the IP address of the target host for iSCSI storage, and then click Discover IQNs.6. Select an appropriate IQN, and then click Discover LUNs. The host starts scanning for LUNs.7. Choose a discovered LUN on which to create a new storage repository.8. Click Finish to create a new storage repository.For details, see Citrix XenServer Design: Configuring Multipathing for XenServer, available at thefollowing website:http://support.citrix.com


Configuring CHAP for the iSCSI HostTwo Challenge-Handshake Authentication Protocol (CHAP) authentication configurations areavailable: Host CHAP authentication, where the HP 3PAR StoreServ Storage iSCSI target portauthenticates the iSCSI Initiator host when it tries to connect to it, and bidirectional (mutual) CHAPauthentication, where both the iSCSI target and host authenticate each other when the host triesto connect to the target.You must create an iSCSI host definition on the HP 3PAR StoreServ Storage before setting andconfiguring CHAP for the iSCSI host. See Creating the Software iSCSI Host Definition (page 17).

Setting the Host CHAP Authentication on the HP 3PAR StoreServ StorageTo set the host CHAP authentication, an iSCSI host definition must have been created on the HP3PAR StoreServ Storage, and the HP 3PAR OS CLI sethost initchap command must be usedto set the host CHAP secret.For HP 3PAR OS 3.1.x, the output shows:

# showhostId Name Persona ----------WWN/iSCSI_Name----------- Port 0 Citrix Generic iqn.2010-07.com.dl380g5-11:dd59da96 ---

The following example uses the host CHAP password host_secret0 for the host. Be aware thatCHAP secret must be at least 12 characters long.

Set the host CHAP secret.

# sethost initchap -f host_secret0 Citrix


Verify the host CHAP secret.

# showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name- 0 Citrix Citrix --

Setting the Host CHAP for CitrixTo set the host CHAP for citrix, complete the following steps:1. Go to the iSCSI Initiator host console, or, at a terminal, edit the /etc/iscsid.conf file

and enable CHAP authentication:

# To enable CHAP authentication set node.session.auth.authmethod# to CHAP. The default is None.node.session.auth.authmethod = CHAP

2. Configure the host CHAP password for the discovery and login session by again editing theconfiguration file /etc/iscsid.conf file.

# To set a discovery session CHAP username and password for the initiator# authentication by the target(s), uncomment the following lines:discovery.sendtargets.auth.username = Citrixdiscovery.sendtargets.auth.password = host_secret0# To set a CHAP username and password for initiator # authentication by the target(s), uncomment the following lines:node.session.auth.username = Citrixnode.session.auth.password = host_secret0

NOTE: The OutgoingPassword must be the same as the host CHAP secret configured onthe HP 3PAR StoreServ Storage.

3. Perform discovery and login as described in Discovering iSCSI Devices and Creating StorageRepositories with Citrix 6.x or 5.6 (page 30).If the targets have been discovered previously, you must log out of the iSCSI sessions, deletethe node, and send target records before performing discovery and login. Complete thefollowing steps for each individual iSCSI login sessions:a. Perform an iSCSI Logout:

# iscsiadm -m node --logout -p 10.0.100.101

b. Remove the iSCSI Node:

# iscsiadm -m node -o delete -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.0.100.101,3260

c. Remove the SendTarget iSCSI Discovery:

# iscsiadm -m discovery -o delete -p 10.0.100.101

d. Stop and start the iSCSI daemon:

# service open-iscsi stopStopping iSCSI daemon: # service open-scsi start

Configuring CHAP for the iSCSI Host 31

Turning off network shutdown. Starting iSCSI daemon: [ OK ][ OK ]

e. Repeat the steps as described in Setting the Host CHAP Authentication on the HP 3PARStoreServ Storage (page 30) to rediscover the iSCSI target nodes and create the iSCSIlogin sessions.

Setting Up the Bidirectional CHAP on the HP 3PAR StoreServ StorageTo set bidirectional CHAP (mutual), complete the following steps. The HP CLI sethost initchapand sethost targetchap commands must be used to set bidirectional CHAP on the HP 3PARStoreServ Storage.1. Verify that a host definition has been created on the HP 3PAR StoreServ Storage. The following

example uses host_secret0 for the host CHAP password and target_secret0 for thetarget CHAP password.

NOTE: The following example uses the host CHAP password host_secret0 for the host.Be aware that CHAP secret must be at least 12 characters long.

2. Set the host CHAP secret.

# sethost initchap -f host_secret0 Citrix

3. Set the target CHAP secret.

# sethost targetchap -f target_secret0 Citrix

4. Verify the host and target CHAP secret.

# showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name- 0 Citrix Citrix S121

Setting the Bidirectional CHAP for CitrixTo configure the bidirectional CHAP for citrix, go to the iSCSI Initiator host console, or, at a terminal,edit the /etc/iscsi/iscsid.conf file and configure the host and target CHAP passwords fordiscovery and login sessions by completing the following steps

NOTE: Notice that two DiscoveryAddress variables with the same IP address for the HP3PAR StoreServ Storage iSCSI target port are required: one for the host CHAP username andpassword variables (OutgoingUsername and OutgoingPassword) and another one for targetCHAP username and password variables (IncomingUsername and IncomingPassword).

1. Perform the CHAP configuration settings for the host initiator:

# To enable CHAP authentication set node.session.auth.authmethod # to CHAP. The default is None.node.session.auth.authmethod = CHAP

# To set a discovery session CHAP username and password for the initiator# authentication by the target(s), uncomment the following lines:discovery.sendtargets.auth.username = Citrixdiscovery.sendtargets.auth.password = host_secret0

# To set a CHAP username and password for initiator


# authentication by the target(s), uncomment the following lines:node.session.auth.username = Citrixnode.session.auth.password = host_secret0

2. Perform the CHAP configuration setting for the target:

# To set a discovery session CHAP username and password for target(s)# authentication by the initiator, uncomment the following lines:discovery.sendtargets.auth.username_in = S121discovery.sendtargets.auth.password_in = target_secret0

# To set a CHAP username and password for target(s)# authentication by the initiator, uncomment the following lines:node.session.auth.username_in = S121node.session.auth.password_in = target_secret0

NOTE:

S121 is the target CHAP name, which can be displayed on the HP 3PAR StoreServStorage by running the command showhost -chap.

The OutgoingUsername and IncomingUsername variables can be set to anythingyou want, but the OutgoingPassword and IncomingPassword must match the hostCHAP password and target CHAP password configured on the HP 3PAR StoreServStorage.

3. Perform discovery and login as describe in Discovering iSCSI Devices and Creating StorageRepositories with Citrix 6.x or 5.6 (page 30).If the targets have been discovered previously, you must log out of the iSCSI sessions, deletethe node, and send target records before performing discovery and login. Complete thefollowing steps for each individual iSCSI login sessions:a. Perform an iSCSI Logout.

# iscsiadm -m node --logout -p 10.0.100.101

b. Remove the iSCSI Node.

# iscsiadm -m node -o delete -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.0.100.101,3260

c. Remove the SendTarget iSCSI Discovery.

# iscsiadm -m discovery -o delete -p 10.0.100.101

d. Stop and start the iSCSI daemon.To stop the iSCSI daemon:

# service open-iscsi stopStopping iSCSI daemon:# service open-iscsi startTurning off network shutdown. Starting iSCSI daemon: [ OK ][ OK ]

Configuring CHAP for the iSCSI Host 33

e. Repeat the steps as described in Creating the iSCSI Connection in Citrix 6.x or 5.6Using the iscsiadm Command (page 29) to rediscover the iSCSI target nodes and createthe iSCSI login sessions.


6 Allocating Storage for Access by the Citrix HostCreating Storage on the HP 3PAR StoreServ Storage

This section describes the general steps and commands that are required to create the virtualvolumes (VVs) that can then be exported for discovery by the citrix 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 Storage Information Library:http://www.hp.com/go/support/docs

Creating Virtual VolumesVirtual volumes are the only data layer visible to hosts. After devising a plan for allocating spacefor the citrix host, create the virtual volumes (VVs) on the HP 3PAR StoreServ Storage.Create volumes that are provisioned from one or more Common Provisioning Groups (CPGs).Volumes can be either fully provisioned or thinly provisioned. Optionally, specify a CPG for snapshotspace 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 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:

# createvv [options] [.] [g|G|t|T]

Here is an example:

# createcpg testcpg# createvv -cnt 5 testcpg TESTLUNS 5g

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

See 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 HP Storage Information Library:http://www.hp.com/go/storage/docs

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

Creating Storage on the HP 3PAR StoreServ Storage 35

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

HP 3PAR StoreServ Storage Concepts Guide

HP 3PAR Command Line Interface Administrators Manual

HP 3PAR Command Line Interface Reference

HP Storage Information Library at: http://www.hp.com/go/storage/docs

Exporting LUNs to the HostThis section explains how to export LUNs to the host as VVs, referred to as virtual LUNs (VLUNs).To export VVs as VLUNs, use the following command:createvlun [cnt] [.int] 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 the name of the VV exported as a virtual LUN.

indicates the starting LUN number.Example:

# createvlun cnt 5 TESTLUN.0 0

To verify that VLUNs were created:

# showvlun

Active VLUNsLun VVName HostName --------Host_WWN/iSCSI_Name-------- Port Type 0 TESTLUNS.0 Citrixhost 210100E08B31901B 0:4:1 host 1 TESTLUNS.1 Citrixhost 210100E08B31901B 0:5:1 host 2 TESTLUNS.2 Citrixhost 210100E08B31901B 1:2:1 host 3 TESTLUNS.3 Citrixhost 210100E08B31901B 1:4:1 host 4 TESTLUNS.4 Citrixhost 210100E08B31901B 1:5:1 host 0 TESTLUNS.0 Citrixhost 210000E08B31901B 0:4:1 host 1 TESTLUNS.1 Citrixhost 210000E08B31901B 0:5:1 host 2 TESTLUNS.2 Citrixhost 210000E08B31901B 1:2:1 host 3 TESTLUNS.3 Citrixhost 210000E08B31901B 1:4:1 host 4 TESTLUNS.4 Citrixhost 210000E08B31901B 1:5:1 host---------------------------------------------------------------------------

10 total

VLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 0 TESTLUNS.0 Citrixhost ---------------- --- host 1 TESTLUNS.1 Citrixhost ---------------- --- host 2 TESTLUNS.2 Citrixhost ---------------- --- host 3 TESTLUNS.3 Citrixhost ---------------- --- host 4 TESTLUNS.4 Citrixhost ---------------- --- host---------------------------------------------------------------------------

5 total

In the example above, there are five paths to the HP 3PAR StoreServ Storage from each HBA port.

36 Allocating Storage for Access by the Citrix 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 (such as 0, 5, 7, 3).

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

Testing was limited to 256 LUNs per storage server port (target) using LUN numbers 0 to 255.

The maximum LUN size that can be exported to a citrix host is 16 TB.

Citrix XenServer 6.x has a supported limit of 75 multipathed LUNs per host (used by storagerepositories).

For more details, see the Citrix XenServer configuration limits, available at the Citrix KnowledgeCenter: http://support.citrix.com


Discovering Fibre Channel Devices and Creating Storage Repositories withCitrix

To discover FC devices and create storage repositories with a Citrix XenServer host using citrixXenCenter, follow these steps:1. In the Resources pane, select the server to create a new storage repository.2. On the toolbar, click Storage, and then click New SR.3. Select Hardware HBA, and then click Next.4. Change the default name if necessary, and then click Next. The host starts scanning for LUNs.5. Choose a discovered LUN on which to create a new storage repository.6. Click Finish to create a new storage repository.

Restrictions on Volume Size and Number 37

7 Booting the Host from the HP 3PAR StoreServ StorageHP 3PAR StoreServ Storage Setup Requirements

Booting from the HP 3PAR StoreServ Storage is supported from version 5.6 Feature Pack 1 onwardsand on fabric and direct connect topologies.During the Citrix installation perform the following steps:1. On the Welcome to XenServer screen, press F2.2. At the boot prompt, enter multipath.3. If you are installing from PXE, add the following command to the PXE Linux configuration

file: device_mapper_multipath=yes.This chapter provides only a general overview of the procedures required to boot the CitrixXenServer operating system from the SAN.For further details, consult the Citrix Installation Guide, available on the Citrix website:http://www.citrix.com


Citrix XenServer boots to a remote disk on a SAN with multipathing enabled.A starting LUN can be exported from the array on any number from 0 to 255. Make sure youhave allocated enough space, when creating your virtual volumes, to be able to install Citrix 6.xor Citrix 5.6FP1 OS.

Citrix Host HBA BIOS Setup ConsiderationsThe HBA BIOS needs to be set up properly to handle booting from the HP 3PAR StoreServ Storage.

Booting from the HP 3PAR StoreServ Storage Using QLogic HBAsWhen booting from the HP 3PAR StoreServ Storage using a QLogic HBA, complete the followingsteps:1. During the host boot, press Ctrl-C or Alt-Q when prompted for the QLogic Fast!UTIL HBA utility.2. From the QLogic Fast!UTIL screen, choose Select Host Adapter menu and select the host adapter

from which you want to boot.3. When the Fast!UTIL Options menu appears, select Configuration Settings.4. Select Adapter Settings.5. Select Host Adapter BIOSEnabled, and then press Esc.6. From the Configuration Settings menu, select Selectable Boot Settings.7. From the Selectable Boot Settings menu, select Selectable Boot>Enabled.8. Arrow down to the next field, (Primary) Boot Port Name,LUN, and then press Enter.9. From the Select Fibre Channel Device menu, you should see the HP 3PAR device under ID0

with its Rev, Port Name, and Port ID shown. Press Enter.10. From the Select LUN menu, select the first line LUN 0 with a status of Supported, and press

Enter.11. Press Esc twice to return to the Configuration Settings Modified dialogue box.12. Select Save changes.13. Return to the Fast!UTIL Options menu and select Select host Adapter.14. Select your next HBA port to boot from and repeat these steps.15. When done, from the Fast!UTIL Options menu:

38 Booting the Host from the HP 3PAR StoreServ Storage

a. Select Exit Fast!UTILb. Select Reboot system

The settings will be saved and the host is restarted.

Booting from the HP 3PAR StoreServ Storage Using Emulex HBAsWhen booting from the HP 3PAR StoreServ Storage using an Emulex HBA, complete the followingsteps:1. During the host boot, press Alt-E or Ctrl-E when prompted by the Emulex HBA Utility, a screen

appears that will show the Emulex adapters in the system. Select and press Enter.a. A screen displays: The BIOS of the Adapter is Disabled. If the screen says, The BIOS of

the Adapter is Enabled, then skip to 2.b. Select option 2 Configure This Adapter's Parameters and press Enter.c. From the next screen Select option 1 Enable or Disable BIOS and press Enter. The following

message appears:The BIOS is Disabled!!Enable Press 1, Disable Press 2:

d. Select 1 and press Enter. The following message appears:The BIOS is Enabled!!

e. Press Esc twice.2. Select option 1 Configure Boot Devices, then press Enter. The following list appears:

List of Saved Boot Devices

3. Select option 1. Unused DID: WWPN: LUN:00 Primary Boot and pressEnter. The following dialog box appears:01. DID: WWPN: Lun:00 3PARdataVV 0000

4. Select the two digit number of the desired boot device 01 and press Enter. The followingdialogue box appears:Enter two digits of starting LUN (Hex):

5. Type 00 and press Enter.The following dialog box appears:DID: XXXXXX WWPN: 01. Lun:00 3PARdataVV 0000a. Select 01 and press Enter.

Another dialogue box will appear:1. Boot this device via WWPN2. Boot this device via DID

b. Select 1 and press Enter. The following screen appears:List of saved boot devices1 Used DID:000000 WWPN: Lun:00 Primary Boot

6. Press Esc twice to return to the Emulex Adapters in the System menu.7. Select the next HBA port to boot from and repeat these steps.8. When done, press x to exit.9. You will be prompted to restart the system. Select Y.

After the system comes up, make sure the citrix installation CD is in the drive tray to continuewith the next steps.

Citrix Host HBA BIOS Setup Considerations 39

Booting from the HP 3PAR StoreServ Storage Using Brocade HBAsWhen booting from the HP 3PAR StoreServ Storage using a Brocade HBA, complete the followingsteps:1. During the host boot, press Ctrl-B or Alt-B when prompted for the QLogic Fast!UTIL HBA utility.2. From the Brocade BIOS config menu, choose the Adapter port from which you want to boot.3. From the Adapter configuration menu select Adapter settings.4. Select Adapter Settings.5. Co

HP 3par Citrix Implementation Guide

Documents

Transcript of HP 3par Citrix Implementation Guide