HP 3PAR Solaris Implementation Guide Dec2011 c02663731

HP 3PAR Solaris Implementation Guide

AbstractThis implementation guide provides information for establishing communications between an HP 3PAR Storage System and a Solaris 8, 9 or 10 host running on the SPARC, x64, and x86 platforms. General information is also provided on the basic steps required to allocate storage on the HP 3PAR Storage System that can then be accessed by the Solaris host.

HP Part Number: QL226-96253 Published: December 201 1

Copyright 201 Hewlett-Packard Development Company, L.P. 1 Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 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 Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Java and Oracle are registered trademarks of Oracle and/or its affiliates.

Contents1 Introduction...............................................................................................6Supported Configurations..........................................................................................................6 InForm OS Upgrade Considerations............................................................................................6 Audience.................................................................................................................................6 Related Documentation..............................................................................................................7 Typographical Conventions........................................................................................................7 Advisories................................................................................................................................7

2 Configuring the HP 3PAR Storage System for Fibre Channel.............................9Configuring the HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.x.....................................9 Configuring Ports on the HP 3PAR Storage System in a Direct Topology.......................................9 Configuring Ports on the HP 3PAR Storage System in a Fabric Topology....................................10 Creating the Host Definition (Host Persona)............................................................................10 Configuring the HP 3PAR Storage System Running InForm OS 2.2.x..............................................11 Configuring Ports for an Emulex lpfc driver............................................................................11 Configuring Ports for a QLogic qla Driver..............................................................................12 Configuring Ports for a Solaris qlc or emlxs Driver..................................................................12 Configuring Ports for a JNI Tachyon driver.............................................................................13 Configuring Ports for a JNI Emerald driver.............................................................................13 Creating the Host Definition................................................................................................14 Setting Up and Zoning the Fabric.............................................................................................14 Configuration Guidelines For Fabric Vendors.........................................................................15 Target Port Limits and Specifications.....................................................................................15 Single Initiator to Single Target Zoning No Fan-In No Fan-Out.................................................16 Single Initiator to Single Target Zoning with Fan-Out from One HP 3PAR Storage System Port to Multiple Host Ports.............................................................................................................16 Single Initiator to Single Target Zoning with Fan-In from Multiple HP 3PAR Storage System Ports to One Host Port................................................................................................................17 Single Initiator to Single Target Zoning with Mixed Fan-In/Out Configurations...........................17 Non-Compliant Zoning Examples.........................................................................................18

3 Configuring the HP 3PAR Storage System for iSCSI.......................................19Configuring the HP 3PAR Storage System iSCSI Ports...................................................................19 Creating an iSCSI Host Definition on an HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.x.....................................................................................................................................20 Creating an iSCSI Host Definition on an HP 3PAR Storage System Running InForm OS 2.2.x.............22 Configuring CHAP Authentication (Optional)..............................................................................23 Enabling Unidirectional (Host) CHAP....................................................................................23 Disabling Unidirectional (Host) CHAP...................................................................................25 Enabling Bidirectional (Mutual) CHAP..................................................................................26 Disabling Bidirectional CHAP..............................................................................................27

4 Configuring the Host for a Fibre Channel Connection....................................29Installing the HBA...................................................................................................................29 Installing the SUN SAN Driver Packages....................................................................................29 Installing the HBA Drivers.........................................................................................................29 Installation Notes for Emulex lpfc Drivers...............................................................................30 Configuration File Settings for Emulex lpfc Drivers..............................................................31 Installation Notes for QLogic qla Drivers...............................................................................31 Configuration File Settings for QLogic qla Drivers..............................................................31 Installation Notes for Solaris qlc and emlxs Drivers.................................................................32 Configuration File Settings for Solaris qlc and emlxs Drivers................................................32 Installation Notes for JNI Tachyon fcaw and fca-pci drivers......................................................32Contents 3

Configuration File Settings for JNI Tachyon Drivers.............................................................34 Installation Notes for JNI Emerald JNIC146x Drivers...............................................................34 Configuration File Settings for JNI Emerald Drivers.............................................................35 Verifying the Driver Package Installation.....................................................................................36 Setting Up Dynamic Multipathing for the Solaris Host..................................................................36 Using Veritas Volume Manager VxDMP Multipathing..............................................................36 Verifying the VxDMP ASL Installation...............................................................................37 Using Sun StorageTek Traffic Manager (SSTM) Multipathing....................................................37 Edits to the /kernel/drv/scsi_vhci.conf file for SSTM Multipathing........................................38 Additional edit to the /kernel/drv/scsi_vhci.conf file for Solaris 8/9....................................38 Persistent Target Binding Considerations....................................................................................38 Persistent Target Binding for Emulex lpfc Drivers.....................................................................39 Persistent Target Binding for QLogic qla Drivers......................................................................40 Persistent Target Binding for Solaris qlc and emlxs Drivers.......................................................41 Persistent Target Binding for JNI Tachyon Drivers....................................................................41 Persistent Target Binding for JNI Emerald Drivers....................................................................41 System Settings for Minimizing I/O Stall Times on VLUN Paths......................................................42

5 Configuring the Host for an iSCSI Connection..............................................44Solaris Host Server Requirements..............................................................................................44 Setting Up the Ethernet Switch..................................................................................................45 Configuring the Solaris Host Ports.............................................................................................45 Setting Up the iSCSI Initiator for Target Discovery.......................................................................46 Using the Static Device Discovery Method.............................................................................46 Using the SendTargets Discovery Method..............................................................................47 Using the iSNS Discovery Method........................................................................................47 Initiating and Verifying Target Discovery...............................................................................48 Setting Up Multipathing MPXIO................................................................................................50

6 Allocating Storage for Access by the Solaris Host.........................................52Creating Storage on the HP 3PAR Storage System.......................................................................52 Creating Virtual Volumes for InForm OS 2.2.4 to 3.1.x............................................................52 Creating Virtual Volumes for InForm OS 2.2.3 and Earlier.......................................................53 Exporting LUNs to a Host with a Fibre Channel Connection..........................................................53 Creating a Virtual Logical Unit Number for Export..................................................................53 VLUN Exportation Limits Based on Host HBA Drivers...............................................................54 Exporting LUNs to a Solaris Host with an iSCSI Connection..........................................................54 Discovering LUNs on Fibre Channel Connections........................................................................56 Discovering LUNs for QLogic qla and Emulex lpfc Drivers........................................................56 Discovering LUNs for Solaris qlc and emlxs Drivers.................................................................56 Discovering LUNs for the JNI Tachyon Driver..........................................................................58 Discovering LUNs for the JNI Emerald Driver..........................................................................58 Discovering LUNs for Sun StorEdge Traffic Manager (SSTM )...................................................58 Discovering LUNs for Veritas Volume Managers DMP (VxDMP)...............................................60 Discovering LUNs on iSCSI Connections....................................................................................60 Removing Volumes for Fibre Channel Connections......................................................................61 Removing Volumes for iSCSI Connections...................................................................................61

7 Configuring the Host for an FCoE Connection..............................................63Solaris Host Server Requirements..............................................................................................63 Configuring the FCoE switch and FC switch................................................................................63 Configuring the Solaris Host Ports.............................................................................................63

4

Contents

8 Using the SunCluster Cluster Server.............................................................65 9 Using the Veritas Cluster Server..................................................................66 10 Booting from the HP 3PAR Storage System.................................................67Preparing a Bootable Solaris Image for Fibre Channel.................................................................67 Dump and Restore Method..................................................................................................67 Net Install Method.............................................................................................................67 Installing the Solaris OS Image onto a VLUN..............................................................................67 Configuring Additional Paths and Sun I/O Multipathing..............................................................69 Configuration for Multiple Path Booting.....................................................................................71 Additional Devices on the Booting Paths....................................................................................72 SAN Boot Example.................................................................................................................72

A Configuration Examples............................................................................74Example of Discovering a VLUN Using qlc/emlx Drivers with SSTM...............................................74 Example of Discovering a VLUN Using an Emulex Driver and VxVM..............................................74 Example of Discovering a VLUN Using a QLogic Driver with VxVM...............................................75 Example of UFS/ZFS File System Creation..................................................................................75 Examples of Growing a Volume................................................................................................76 Growing an SSTM Volume..................................................................................................76 Growing a VxVM Volume...................................................................................................78 VxDMP Command Examples....................................................................................................80 Displaying I/O Statistics for Paths........................................................................................80 Managing Enclosures.........................................................................................................80 Changing Policies..............................................................................................................81 Accessing VxDMP Path Information......................................................................................81 Listing Controllers..........................................................................................................81 Displaying Paths............................................................................................................81

B Patch/Package Information........................................................................83Minimum Patch Requirements for Solaris Versions........................................................................83 Patch Listings for Each SAN Version Bundle................................................................................85 HBA Driver/DMP Combinations...............................................................................................87 Minimum Requirements for a Valid QLogic qlc + VxDMP Stack................................................87 Minimum Requirements for a Valid Emulex emlxs + VxDMP Stack.............................................87 Default MU level Leadville Driver Table.................................................................................88

C FCoE-to-FC Connectivity............................................................................90

Contents

5

1 IntroductionThis implementation guide provides information for establishing communications between an HP 3PAR Storage System and a Solaris 8, 9 or 10 host running on the SPARC, x64, and x86 platforms. General information is also provided on the basic steps required to allocate storage on the HP 3PAR Storage System that can then be accessed by the Solaris host. The information contained in this implementation guide is the outcome of careful testing of the HP 3PAR Storage System with as many representative hardware and software configurations as possible.

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

REQUIREDAll installation steps should be performed in the order described in this implementation guide.

Supported ConfigurationsFor complete details on supported host configurations, consult the HP 3PAR InForm OS 3.1.1 Configuration Matrix, which is available on HPs Business Support Center (BSC). To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate to your product page, click HP Support & Drivers, and then click Manuals.

InForm OS Upgrade ConsiderationsRefer to the HP 3PAR InForm OS 3.1.1 Upgrade Pre-Planning Guide (PN QL226-96033) for information and planning of an online HP 3PAR InForm Operating System upgrade. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate to your product page, click HP Support & Drivers, and then click Manuals.

AudienceThis implementation guide is intended for system and storage administrators who monitor and direct system configurations and resource allocation for HP 3PAR Storage Systems. The tasks described in this manual assume that the administrator is familiar with Sun Solaris and the HP 3PAR Inform OS. Although this guide attempts to provide the basic information that is required to establish communications between the HP 3PAR Storage System and the Solaris host, and to allocate the required storage for a given configuration, the appropriate HP 3PAR documentation must be consulted in conjunction with the Solaris host and HBA vendor documentation for specific details and procedures. This implementation guide does NOT intend to reproduce any third-party product documentation. For details about devices such as host servers, HBAs, fabric and Ethernet switches, and non-HP 3PAR software management tools, consult the appropriate third-party documentation.

6

Introduction

Related DocumentationThe following documents also provide information related to HP 3PAR Storage Systems and the InForm Operating System:For information about Specific platforms supported Read the HP 3PAR InForm OS 3.1.1 Configuration Matrix

InForm command line interface commands and their usage HP 3PAR InForm OS CLI Reference Using the InForm Management Console to configure and administer HP 3PAR Storage Systems HP 3PAR Storage System concepts and terminology Determining HP 3PAR Storage System hardware specifications, installation considerations, power requirements, networking options, and cabling Identifying storage server components and detailed alert information Using HP 3PAR Remote Copy Using HP 3PAR CIM HP 3PAR InForm OS Management Console Online Help HP 3PAR InForm OS Concepts Guide HP 3PAR Storage System S-Class/T-Class Storage Server Physical Planning Manual or the HP 3PAR Storage System E-Class/F-Class Storage Server and Third-Party Rack Physical Planning Manual HP 3PAR InForm OS Messages and Operators Guide HP 3PAR Remote Copy Users Guide HP 3PAR CIM API Programming Reference

Typographical ConventionsThis guide uses the following typographical conventions :Typeface ABCDabcd Meaning Example

Used for dialog elements such as When prompted, click Finish to complete the titles, button labels, and other screen installation. elements. Used for paths, filenames, and screen Open the file output. \os\windows\setup.exe Used to differentiate user input from screen output. Used for variables in filenames, paths, and screen output. Used for options in user input. # cd \opt\3par\console # controlport offline Modify the content string by adding the -P[x] option after -jar inform.jar # .\java -jar inform.jar -P[x]

ABCDabcd

ABCDabcd [ABCDabcd]

AdvisoriesTo avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. CAUTION: NOTE: guide. Cautions alert you to actions that can cause damage to equipment, software, or data.

Notes are reminders, tips, or suggestions that supplement the procedures included in this

Related Documentation

7

REQUIREDRequirements signify procedures that must be followed as directed in order to achieve a functional and supported implementation based on testing at HP. WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system.

8

Introduction

2 Configuring the HP 3PAR Storage System for Fibre ChannelThis chapter explains how to establish a Fibre Channel connection between the HP 3PAR Storage System and a Solaris host and covers InForm OS 2.2.x, 2.3.x, and 3.1.x versions. For information on setting up the physical connection for a particular HP 3PAR Storage System, see the appropriate HP 3PAR installation manual.

REQUIREDIf you are setting up a fabric along with your installation of the HP 3PAR Storage System, consult Setting Up and Zoning the Fabric (page 14) before configuring or connecting your HP 3PAR Storage System.

Configuring the HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.xThis section describes how to connect the HP 3PAR Storage System to a Solaris Host over a Fibre Channel network when running InForm OS 2.3.x to OS 3.1.x. For information on setting up a connection for OS 2.2.x, see Configuring the HP 3PAR Storage System Running InForm OS 2.2.x (page 11).

REQUIREDThe following setup must be completed before connecting the HP 3PAR Storage System port to a device.

Configuring Ports on the HP 3PAR Storage System in a Direct TopologyTo set up the HP 3PAR Storage System ports for a direct connection, issue the following set of commands with the appropriate parameters for each direct connect port.# controlport offline # controlport config host -ct loop # controlport rst

The -ct loop parameter specifies a direct connection. NOTE: While the server is running, HP 3PAR Storage System ports that leave (e.g., due to an unplugged cable) and return will be tracked by their WWN. The WWN of each port is unique and constant which ensures correct tracking of a port and its LUNs by the host HBA driver. If a fabric zoning relationship exists such that a host HBA port has access to multiple targets (for example, multiple ports on the HP 3PAR Storage System), the driver will assign target IDs (cxtxdx) to each discovered target in the order that they are discovered. The target ID for a given target can change in this case as targets leave the fabric and return or when the host is rebooted while some targets are not present.

Configuring the HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.x

9

Configuring Ports on the HP 3PAR Storage System in a Fabric TopologyTo set up the HP 3PAR Storage System ports for a fabric connection, complete the following steps for each fabric connected port. CAUTION: Before taking a port offline in preparation for a fabric connection, you should verify that the port has not been previously defined and that it is not already connected to a host as this would interrupt the existing host connection. If an HP 3PAR Storage System port is already configured for a fabric connection, you can ignore Configuring the HP 3PAR Storage System Running InForm OS 2.2.x (page 11) as you do not have to take the port offline. 1. To determine if a port has already been configured for a host port in fabric mode, issue the InForm CLI showport -par command.# showport -par N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal 0:0:1 disk loop auto 2Gbps disabled disabled disabled enabled 0:0:2 disk loop auto 2Gbps disabled disabled disabled enabled 0:0:3 disk loop auto 2Gbps disabled disabled disabled enabled 0:0:4 disk loop auto 2Gbps disabled disabled disabled enabled 0:4:1 host point auto 4Gbps disabled disabled disabled enabled 0:4:2 host point auto 4Gbps disabled disabled disabled enabled 0:5:1 host point auto 2Gbps disabled disabled disabled enabled 0:5:2 host loop auto 2Gbps disabled disabled disabled enabled 0:5:3 host point auto 2Gbps disabled disabled disabled enabled 0:5:4 host loop auto 2Gbps disabled disabled disabled enabled 1:0:1 disk loop auto 2Gbps disabled disabled disabled enabled 1:0:2 disk loop auto 2Gbps disabled disabled disabled enabled 1:0:3 disk loop auto 2Gbps disabled disabled disabled enabled 1:0:4 disk loop auto 2Gbps disabled disabled disabled enabled 1:2:1 host point auto 2Gbps disabled disabled disabled enabled 1:2:2 host loop auto 2Gbps disabled disabled disabled enabled 1:4:1 host point auto 2Gbps disabled disabled disabled enabled 1:4:2 host point auto 2Gbps disabled disabled disabled enabled

2.

If the port has not been configured, take the port offline before configuring it for the Solaris host by issuing the InForm CLI controlport offline command. For example:# controlport offline 1:5:1

3.

To configure the port for the host server, issue the controlport config host -ct point command. The -ct point parameter specifies a fabric connection. For example:# controlport config host -ct point 1:5:1 # controlport rst 1:5:1

Creating the Host Definition (Host Persona)Before connecting the Solaris host to the HP 3PAR Storage System, you need to create a host definition that specifies a valid host persona for each HP 3PAR Storage System that is to be connected to a host HBA port through a fabric or direct connection. Solaris uses the default generic host personality of 1. The following steps show how to create the host definition.

10

Configuring the HP 3PAR Storage System for Fibre Channel

1.

To create host definitions, issue the createhost command with the -persona option to specify the persona and the host name. For example:# createhost -persona 1 solarishost 1122334455667788 1122334455667799

2.

To verify that the host has been created, issue the showhost command.# showhost Id Name Persona -WWN/iSCSI_Name- Port 6 solarishost Generic 1122334455667788 --1122334455667799 ---

NOTE: HP recommends using host persona 1 for Solaris 10 (and above) hosts as it is required to enable Host Explorer functionality. However, host persona 6 is automatically assigned following a rolling upgrade from InForm OS 2.2.x. If appropriate, you can change host persona 6 after an upgrade to host persona 1. Host persona 1 enables two functional features: Host Explorer, which requires the SESLun element of Host persona 1 and UARepLun, which notifies the host of newly exported VLUNs and triggers a LUN discovery request on the host, making the VLUN automatically available in 'format'. NOTE: See the HP 3PAR InForm OS CLI Reference or the IMC help for complete details on using the controlport, createhost and showhost commands.

Configuring the HP 3PAR Storage System Running InForm OS 2.2.xThis section describes the steps that are required to connect the HP 3PAR Storage System to a Solaris host over a Fibre Channel network and to create the host definitions when running InForm OS 2.2.x. When setting up the HP 3PAR Storage System ports (Port Personas), consult the instructions for the type of HBA driver being used where X:X:X is the port location, expressed as .

REQUIREDThe following setup must be completed before connecting the HP 3PAR Storage System port to a device.

Configuring Ports for an Emulex lpfc driver Direct Connect: Ports configured to personality 4

# controlport persona 4 X:X:X

Verify port personality 4, connection type loop, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 1:3:2 loop auto 4Gbps disable disabled (4) emx, g_hba, g_os, 0, DC enabled

Fabric Connect: Ports configured to personality 7


Configuring the HP 3PAR Storage System Running InForm OS 2.2.x

1 1

Verify port personality 7, connection type point, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 0:5:1 point auto 4Gbps disable enabled (7) g_ven, g_hba, g_os, 0, FA enabled

Configuring Ports for a QLogic qla Driver Direct Connect: Ports configured to personality 1


Verify port personality 1, connection type loop, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 1:4:2 loop auto 2Gbps disable enabled (1) g_ven, g_hba, g_os, 0, DC enabled



Verify port personality 7, connection type point, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 0:5:1 point auto 4Gbps disable enabled (7) g_ven, g_hba, g_os, 0, FA enabled

Configuring Ports for a Solaris qlc or emlxs Driver Direct Connect: Ports configured to personality 1


Verify port personality 1, connection type loop, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 1:4:2 loop auto 2Gbps disable enabled (1) g_ven, g_hba, g_os, 0, DC enabled



Verify port personality 9, connection type point, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN -----------Persona------------ IntCoal 0:5:1 point auto 4Gbps disable enabled (9) g_ven,g_hba, g_os, 0, FA enabled

12


Configuring Ports for a JNI Tachyon driver Direct Connect: Ports configured to personality 3


Verify port personality 3, connection type loop, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN ----------Persona------------ IntCoal 1:4:2 loop auto 2Gbps disable disabled (3) jni, g_hba, g_os, 0, DC enabled


# controlport persona 7 X:X:X # controlport vcn disable X:X:X

Verify port personality 7, connection type point, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN ----------Persona----------- IntCoal 0:5:1 point auto 4Gbps disable disabled *(7) g_ven,g_hba, g_os, 0, FA enabled

WARNING! The Controlport Offline command for the HP 3PAR Storage System LSI 929 HBA requires firmware versions greater than 02.00.21 when connected to a JNI Tachyon host HBA.

Configuring Ports for a JNI Emerald driver Direct Connect: Ports configured to personality 3


Verify port personality 3, connection type loop, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRate Class2 VCN ----------Persona------------ IntCoal 1:4:2 loop auto 2Gbps disable disabled (3) jni, g_hba, g_os, 0, DC enabled



Verify port personality 7, connection type point, using the InForm CLI showport -par command.# showport -par N:S:P ConnType CfgRate MaxRat Class2 VCN -----------Persona------------ IntCoal. 0:4:1 point auto 4Gbps disable enabled(7) g_ven, g_hba, g_os, 0, FA enabled

Configuring the HP 3PAR Storage System Running InForm OS 2.2.x

13

Creating the Host DefinitionBefore connecting the Solaris host to the HP 3PAR Storage System, you need to create a host definition for each HP 3PAR Storage System that is to be connected to a host HBA port through a fabric or direct connection. 1. To create host definitions, issue the createhost command with the host name. For example:# createhost solarishost 1122334455667788 1122334455667799

2.

To verify that the host has been created, issue the showhost command.# showhost Id Name -WWN/iSCSI_Name- Port 0 sqa-solaris 1122334455667788 --1122334455667799 ---

NOTE: See the HP 3PAR InForm OS CLI Reference or the IMC help for complete details on using the controlport, showport, createhost and showhost commands.

Setting Up and Zoning the FabricFabric zoning controls which devices have access to each other on the fabric. The required use of single initiator to single target zoning isolates the host server and HP 3PAR Storage System ports from registered state change notifications (RSCNs) that are irrelevant to these ports. When Fibre Channel devices (Initiators and Targets) log in to the fabric, they register to receive RSCNs so that they can be notified in the event that there is a state change (left or came back in the fabric) of the device(s) they are zoned to. In the case that many devices (targets and Initiators) are part of the same zone, if one of the devices leaves and comes back into the fabric for any reason (device rebooted, unstable link between device and the fabric, faulty device port and/or fabric port, etc. etc) all of the devices (whether target or initiator) that are part of the same zone, will be notified of the state change for the device that left or came back into the fabric. This could cause disruption of I/O as devices that received the RSCN would have to take the necessary steps to handle the RSCN. Fabric zoning can be set up by associating the device World Wide Names (WWNs) or switch ports with specified zones in the fabric. Although you can use either the WWN or the switch port zoning method with the HP 3PAR Storage System, the WWN zoning method is recommended because the zone survives port changes to ports when cables are reconnected on a fabric. Use the methods provided by the switch vendor to create one Initiator-one Target relationships between host server HBA ports and storage server ports before you connect the host server HBA ports or HP 3PAR Storage System ports to the fabric(s).

REQUIREDWhen establishing zoning with the HP 3PAR Storage System, there must only be a single initiator zoned with a single target. If a customer experiences an issue using another zoning approach, HP may require the customer to implement this zoning approach as part of troubleshooting and/or corrective action. After connecting each host server HBA port and HP 3PAR Storage System port to the fabric(s), verify the switch and zone configurations using the InForm CLI showhost command, to ensure that each initiator is zoned with the correct target. In the following explanations, an initiator port (initiator for short) refers to a host server HBA port and a target port (target for short) refers to an HP 3PAR Storage System HBA port.14 Configuring the HP 3PAR Storage System for Fibre Channel

Configuration Guidelines For Fabric VendorsUse the following fabric vendor guidelines before configuring ports on the fabric to which the HP 3PAR Storage System connects. Brocade switch ports that connect to a host server HBA port or to an HP 3PAR Storage System port should be set in their default mode. On Brocade 3xxx switches running Brocade firmware 3.0.2 or later, verify that each switch port is in the correct mode using the Brocade telnet interface and the portcfgshow command as follows:

brocade2_1:admin> portcfgshow Ports 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.

McData switch or director ports should be in their default modes as type GX-Port with a speed setting of Negotiate. Cisco switch ports that connect to HP 3PAR Storage System ports or host HBA ports should be set to AdminMode = FX and AdminSpeed = auto port, with the speed set to auto negotiate. QLogic switch ports should be set to port type GL-port and port speed auto-detect. QLogic switch ports that connect to the HP 3PAR Storage System should be set to I/O Stream Guard disable or auto but never enable.

Target Port Limits and SpecificationsIn order to avoid the overwhelming of a target port and ensure continuous I/O operations, refer to the following limitations on a target port: Maximum of 64 host server ports per HP 3PAR Storage System port, with a maximum total of 1,024 host server ports per HP 3PAR Storage System. I/O queue depth on each HP 3PAR Storage System HBA model as follows: QLogic 2G: 497 LSI 2G: 510 Emulex 4G: 959 HP 3PAR HBA 4G: 1638 HP 3PAR HBA 8G: 3276

The I/O queues are shared amongst 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 will receive a target queue full response from the HP 3PAR Storage System port. This can result in erratic I/O performance on each host server. If this condition occurs, each host server should be throttled so that they cannot overrun the HP 3PAR Storage System port's queues when all host servers are delivering their maximum number of I/O requests.

Setting Up and Zoning the Fabric

15

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

Single Initiator to Single Target Zoning No Fan-In No Fan-OutIn a single initiator to single target zoning, no fan-in, no fan-out configuration, each HBA port is connected to only one HP 3PAR Storage System port (Figure 1 (page 16)). Figure 1 Single Initiator to Single Target Zoning No Fan-In/No Fan-Out

Single Initiator to Single Target Zoning with Fan-Out from One HP 3PAR Storage System Port to Multiple Host PortsFan-out refers to an HP 3PAR Storage System server port that is connected to more that one host port, as shown in Figure 2 (page 16). Figure 2 Single Initiator to Single Target Zoning with Fan-Out

16


NOTE: port.

A maximum of 64 host server ports can fan-out from a single HP 3PAR Storage System

Single Initiator to Single Target Zoning with Fan-In from Multiple HP 3PAR Storage System Ports to One Host PortFan-in refers to a host server port connected to many HP 3PAR Storage System ports. This is shown in Figure 3 (page 17). Figure 3 Single Initiator to Single Host Target Zoning with Fan-In

NOTE:

A maximum of four HP 3PAR Storage System ports can fan-in to a single host server port.

Single Initiator to Single Target Zoning with Mixed Fan-In/Out ConfigurationsThe following figure (Figure 4 (page 17)) shows a single initiator to a single target zoning with fan-in and fan-out from one HP 3PAR Storage System to multiple host servers. Figure 4 Single Initiator to Single Target Zoning with Fan-In and Fan-Out

Setting Up and Zoning the Fabric

17

Non-Compliant Zoning ExamplesIn the following examples, the zoning rule of one initiator zoned to one target is not respected. Non-compliant zoning is shown in Figure 5 (page 18). Figure 5 Non-Compliant Zoning

18


3 Configuring the HP 3PAR Storage System for iSCSIThis chapter explains how to establish an iSCSI connection between the HP 3PAR Storage System and the Solaris host. For information on setting up the physical connection, see the appropriate HP 3PAR installation manual.

Configuring the HP 3PAR Storage System iSCSI PortsThis section applies to configurations based on installed NICs, up to and including 1-GB port speed. Each HP 3PAR Storage System iSCSI target port that will be connected to an iSCSI initiator must be set up appropriately for your configuration, as described in the following steps. The following example shows the default HP 3PAR Storage System iSCSI port settings, before configuration:# showport -iscsi N:S:P State IPAddr Netmask Gateway TPGT 0:3:1 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 0:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 1:3:1 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0 1:3:2 loss_sync 0.0.0.0 0.0.0.0 0.0.0.0

MTU 131 132 131 132

Rate 1500 1500 1500 1500

DHCP iSNS_Prim iSNS_Sec iSNS_Port n/a 0 0.0.0.0 0.0.0.0 3205 n/a 0 0.0.0.0 0.0.0.0 3205 n/a 0 0.0.0.0 0.0.0.0 3205 n/a 0 0.0.0.0 0.0.0.0 3205

Each HP 3PAR Storage System iSCSI target port that will be connected to an iSCSI Initiator must be set up appropriately for your configuration as described in the following steps. 1. Set up the IP and netmask address on the iSCSI target port using the InForm CLI controliscsiport command. Here is an example:# controliscsiport addr 10.1.0.110 255.0.0.0 -f 0:3:1 # controliscsiport addr 11.1.0.110 255.0.0.0 -f 1:3:1

2.

To verify the iSCSI target port configuration, issue the InForm CLI showport -iscsi command.# showport -iscsi N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port 0:3:1 ready 10.1.0.110 255.0.0.0 0.0.0.0 31 1500 1Gbps 0 0.0.0.0 0.0.0.0 3205 0: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 3205 1:3:1 ready 11.1.0.110 255.0.0.0 0.0.0.0 131 1500 1Gbps 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

NOTE: Make sure the IP switch ports, (where the HP 3PAR Storage System iSCSI target ports and iSCSI Initiators host are connected), are able to communicate with each other. You can use the ping command for this purpose on the Solaris host. 3. If the Solaris host uses the Internet Storage Name Service (iSNS) to discover the target port, configure the iSNS server IP Address on the target port by issuing the InForm CLI controliscsiport command with the isns parameter.# controliscsiport isns 11.0.0.200 -f 1:3:1 # showport -iscsi N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port 1:3:1 ready 11.1.0.110 255.0.0.0 0.0.0.0 31 1500 1Gbps 0 Configuring the HP 3PAR Storage System iSCSI Ports 19

11.0.0.200 0.0.0.0 3205 - - -

NOTE: The Solaris OS does not have its own iSNS server, so a Windows server that has been installed with the iSNS package must be used to provide the iSNS server functions instead. 4. Each HP 3PAR Storage System iSCSI port has a unique name, port location, and serial number as part of its iqn iSCSI name. Use the InForm CLI showport command with the -iscsiname parameter to get the iSCSI name.# showport -iscsiname N:S:P IPAddr ---------------iSCSI_Name---------------0:3:1 10.1.0.110 iqn.2000-05.com.3pardata:20310002ac00003e 0:3:2 0.0.0.0 iqn.2000-05.com.3pardata:20320002ac00003e 1:3:1 11.1.0.110 iqn.2000-05.com.3pardata:21310002ac00003e 1:3:2 0.0.0.0 iqn.2000-05.com.3pardata:21320002ac00003e

5.

Use the ping command on the Solaris host to verify that the HP 3PAR Storage System target is pingable, and use the route get command to check that the configured network interface is used for the destination route. Example: After configuring the host and HP 3PAR Storage System ports, 1 1.1.0.1 is the 10 HP 3PAR Storage System target IP Address, 1 1.1.0.40 is host IP Address and the host uses a ce2 network interface to route the traffic to the destination.# ping 11.1.0.110 11.1.0.110 is alive # route get 11.1.0.110 route to: 11.1.0.110 destination: 11.0.0.0 mask: 255.0.0.0 interface: ce2 flags:

As an alternative, you can use controliscsiport to ping the host from the HP 3PAR Storage System ports.# controliscsiport ping [] # controliscsiport ping 1 11.1.0.40 1:3:1 Ping succeeded

For information on setting up target discovery on the Solaris host, see Section (page 46).

Creating an iSCSI Host Definition on an HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.xYou will need the Host iqn name/names to create the iSCSI host definition on the HP 3PAR Storage System.# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 Initiator node alias: Login Parameters (Default/Configured): Header Digest: NONE/-

20

Configuring the HP 3PAR Storage System for iSCSI

Data Digest: NONE/Authentication Type: NONE RADIUS Server: NONE RADIUS access: unknown Configured Sessions: 1

The following steps show how to create the host definition for an iSCSI connection. 1. You can verify that the iSCSI Initiator is connected to the iSCSI target port by using the InForm CLI showhost command.# showhost Id Name --

Persona ---------------WWN/iSCSI_Name--------------- Port Generic iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 0:3:1 iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 1:3:1

2.

Create an iSCSI host definition entry by issuing the InForm CLI createhost -iscsi command.# createhost -iscsi solaris-host-01 iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 Setting default host persona 1 (Generic)

# showport -iscsi N:S:P State IPAddr Netmask iSNS_Prim iSNS_Sec iSNS_Port 0:3:1 ready 10.100.0.101 255.0.0.0 0.0.0.0 0.0.0.0 3205 1:3:1 ready 10.101.0.201 255.0.0.0 0.0.0.0 0.0.0.0 3205

Gateway TPGT 0.0.0.0 31 0.0.0.0 131

MTU 1500 1500

Rate DHCP 1Gbps 0 1Gbps 0

NOTE: HP 3PAR recommends host persona 1 for Solaris 10 (and above) hosts as it is required to enable Host Explorer functionality. However, host persona 6 is automatically assigned following a rolling upgrade from 2.2.x. If appropriate, you can change host persona 6 after an upgrade to host persona 1. Host persona 1 enables Host Explorer, which requires the SESLun element of Host persona 1. Newly exported vLUNs can be seen in 'format' by issuing devfsadm -i iscsi. To register the data vLUN 254 on Solaris 'format', a host reboot is required. NOTE: You must configure the HP 3PAR Storage System iSCSI target port(s) and establish an iSCSI Initiator connection/session with the iSCSI target port from the host to be able to create a host definition entry. For details, see Configuring the Host for an iSCSI Connection (page 44). 3. Verify that the host entry has been created.# showhost Id Name 1 solaris-host-01

Persona ---------------WWN/iSCSI_Name--------------- Port Generic iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 0:3:1 iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 1:3:1

The showhost -d command provides more details on the connection.# showhost -d Id Name

Persona ---------------WWN/iSCSI_Name---------------

Port

Creating an iSCSI Host Definition on an HP 3PAR Storage System Running InForm OS 3.1.x or 2.3.x

21

IP_addr 1 solaris-host-01 10.1.0.40 1 solaris-host-01 11.1.0.40

Generic iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 Generic iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940

0:3:1 1:3:1

# showiscsisession N:S:P --IPAddr--- TPGT TSIH Conns -----------------iSCSI_Name-----------------------StartTime------0:3:1 10.105.3.10 31 11351 1 iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 2010-02-25 07:47:38 PST 1:3:1 10.105.4.10 131 11351 1 iqn.1986-03.com.sun:01:ba7a38f0ffff.4b798940 2010-02-25 07:47:37 PST

Creating an iSCSI Host Definition on an HP 3PAR Storage System Running InForm OS 2.2.xYou will need the Host iqn name/names to create the iSCSI host definition on the HP 3PAR Storage System. The following steps show how to create the host definition for an iSCSI connection. 1. You can verify that the iSCSI Initiator is connected to the iSCSI target port by using the InForm CLI showhost command.# showhost Id Name -----------WWN/iSCSI_Name------------ Portiqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 1:3:1 iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 0:3:1

2.

Create an iSCSI host definition entry by issuing the InForm CLI createhost -iscsi command.# createhost -iscsi solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d

3.

Verify that the host entry has been created.# showhost Id Name -----------WWN/iSCSI_Name------------ Port 1 solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 0:3:1 iqn.1986 03.com.sun:01:0003bac3b2e1.45219d0d 1:3:1

The showhost -d command provides more details on the connection.# showhost -d Id Name -----------WWN/iSCSI_Name------------ Port IP_addr 1 solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 0:3:1 10.1.0.40 2 solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 1:3:1 11.1.0.40 # showiscsisession N:S:P --IPAddr-- TPGT TSIH Conns ---iSCSI_Name-- ------StartTime------0:3:1 10.1.0.40 31 24435 1 iqn.1986-3.com.sun:01:0003bac3b2e1.45219d0d Fri Dec 08 11:57:50 PST 2006 1:3:1 11.1.0.40 131 17955 1 iqn.1986-3.com.sun:01:0003bac3b2e1.45219d0d Fri Dec 08 12:06:58 PST 2006

22


Configuring CHAP Authentication (Optional)Solaris supports Challenge-Handshake Authentication Protocol (CHAP) for higher security connectivity. CHAP uses the notion of challenge and response and has two authentication types supported by the InForm OS. Unidirectional or Host CHAP authentication is used when the HP 3PAR Storage System iSCSI target port authenticates the iSCSI Host initiator when it tries to connect. Bidirectional (Mutual) CHAP authentication adds a second level of security where both the iSCSI target and host authenticate each other when the host tries to connect to the target.

Enabling Unidirectional (Host) CHAPTo set the host CHAP authentication after an iSCSI host definition has been created on the HP 3PAR Storage System, use the InForm CLI sethost initchap command to set the host CHAP secret. Example: a. Verify that a host definition has been created.# showhost Id Name -----------WWN/iSCSI_Name------------ Port solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 0:3:1 iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 1:3:1

NOTE:

The CHAP secret length must be between 12 and 16 characters.

The following example sets host_secret0 as the host secret key.# sethost initchap -f host_secret0 solarisiscsi

b.

Verify the host CHAP secret.# showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name1 solarisiscsi solarisiscsi -

c.

Set the secret key host-secret0 on the host.# iscsiadm modify initiator-node --CHAP-secret

Enable CHAP as the authentication method after the secret key is set.# iscsiadm modify initiator-node --authentication CHAP

d.

Enable CHAP as the authentication method.# iscsiadm modify target-param --authentication CHAP iqn.2000-05.com.3pardata:21310002ac00003 # iscsiadm modify target-param --authentication CHAP iqn.2000-05.com.3pardata:20310002ac00003

Configuring CHAP Authentication (Optional)

23

e.

Verify that the authentication is enabled.# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d Initiator node alias: Login Parameters (Default/Configured): Header Digest: NONE/Data Digest: NONE/Authentication Type: CHAP CHAP Name: iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d - - # iscsiadm list target-param -v Target: iqn.2000-05.com.3pardata:21310002ac00003e Alias: Bi-directional Authentication: disabled Authentication Type: CHAP CHAP Name: iqn.2000-05.com.3pardata:21310002ac00003e - - -

NOTE: In the example above, the default target CHAP Name is the target port iSCSI name (iqn.2000-05.com.3pardata:21310002ac00003e) and host CHAP Name is the initiator port iSCSI name (iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d). f. Create a new iSCSI connection session. Example: If you are using SendTargets as a discovery method, remove and add back the discovery address to create a new connection session.# iscsiadm remove discovery-address 11.1.0.110:3260 # iscsiadm add discovery-address 11.1.0.110:3260

Or to apply for all connected targets:# iscsiadm modify discovery --sendtargets disable # iscsiadm modify discovery --sendtargets enable

g.

Invoke devfsadm to discover the devices after the host is verified by the target.# devfsadm -i iscsi

Use a similar procedure if other discovery methods are being used.# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:00144fb0534c.4a4e0673 Initiator node alias: Login Parameters (Default/Configured): Header Digest: NONE/NONE Data Digest: NONE/NONE Authentication Type: NONE RADIUS Server: NONE RADIUS access: unknown Configured Sessions: 1

24


Disabling Unidirectional (Host) CHAPTo disable unidirectional CHAP, issue the iscsiadm command with the appropriate parameter as shown in the following example.bash-3.00# iscsiadm modify initiator-node -a none bash-3.00# iscsiadm list target bash-3.00# iscsiadm modify target-param --authentication none For example: bash-3.00# iscsiadm modify target-param --authentication none iqn.2000-05.com.3pardata:20320002ac0000af bash-3.00# iscsiadm modify target-param --authentication none iqn.2000-05.com.3pardata:21310002ac0000af bash-3.00# iscsiadm list target-param -v Target: iqn.1986-03.com.sun:01:00144fb0534c.4a4e0673 Alias: Bi-directional Authentication: disabled Authentication Type: NONE Login Parameters (Default/Configured): Data Sequence In Order: yes/Data PDU In Order: yes/Default Time To Retain: 20/Default Time To Wait: 2/Error Recovery Level: 0/First Burst Length: 65536/Immediate Data: yes/Initial Ready To Transfer (R2T): yes/Max Burst Length: 262144/Max Outstanding R2T: 1/Max Receive Data Segment Length: 8192/Max Connections: 1/Header Digest: NONE/NONE Data Digest: NONE/NONE Configured Sessions: 1 Target: iqn.2000-05.com.3pardata:20320002ac0000af Alias: Bi-directional Authentication: enabled Authentication Type: NONE Login Parameters (Default/Configured): Data Sequence In Order: yes/Data PDU In Order: yes/Default Time To Retain: 20/Default Time To Wait: 2/Error Recovery Level: 0/First Burst Length: 65536/Immediate Data: yes/Initial Ready To Transfer (R2T): yes/Max Burst Length: 262144/Max Outstanding R2T: 1/Max Receive Data Segment Length: 8192/65536 Max Connections: 1/Header Digest: NONE/Data Digest: NONE/Configured Sessions: 1 iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:00144fb0534c.4a4e0673 Initiator node alias: Login Parameters (Default/Configured): Header Digest: NONE/NONE Data Digest: NONE/NONE Authentication Type: NONE RADIUS Server: NONE


25

RADIUS access: unknown Configured Sessions: 1

On the HP 3PAR Storage System, remove CHAP for the host:# sethost removechap solarisiscsi

Enabling Bidirectional (Mutual) CHAPTo set bidirectional CHAP, a host definition must already be defined on the HP 3PAR Storage System. The InForm CLI sethost initchap and sethost targetchap commands are used to set bidirectional CHAP on the HP 3PAR Storage System as described in the following steps. 1. On the HP 3PAR Storage System, create and verify the host and target CHAP secrets.# sethost initchap -f host_secret0 solarisiscsi # sethost targetchap -f target_secret0 solarisiscsi # showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name1 solarisiscsi solarisiscsi S062

NOTE: The Target Chap name is set by default to the HP 3PAR Storage System name. Use the InForm CLI showsys command to determine the HP 3PAR Storage System name. 2. Enter the Host Chap secret key host_secret0 on the host.# iscsiadm modify initiator-node --CHAP-secret

3.

Enable the Host CHAP authentication after the secret key is set.# iscsiadm modify initiator-node --authentication CHAP

4.

Enable target or bidirectional authentication for each connected target port.# iscsiadm list target Target: iqn.2000-05.com.3pardata:21310002ac00003e - Target: iqn.2000-05.com.3pardata:20310002ac00003e # iscsiadm modify target-param -B enable iqn.2000-05.com.3pardata:21310002ac00003e # iscsiadm modify target-param -B enable iqn.2000-05.com.3pardata:20310002ac00003e

5.

Enter the Target Chap secret key target_secret0 for each connected target.# iscsiadm modify target-param --CHAP-secret iqn.2000-05.com.3pardata:21310002ac00003e # iscsiadm modify target-param --CHAP-secret iqn.2000-05.com.3pardata:20310002ac00003e

26


6.

Enable CHAP as the authentication method.# iscsiadm modify target-param --authentication CHAP iqn.2000-05.com.3pardata:21310002ac00003 # iscsiadm modify target-param --authentication CHAP iqn.2000-05.com.3pardata:20310002ac00003

7.

Set the CHAP name for the HP 3PAR Storage System for the iSCSI targets (Use the InForm CLI showsys command to determine the HP 3PAR Storage System name).# iscsiadm modify target-param --CHAP-name s062 iqn.2000-05.com.3pardata:21310002ac00003e # iscsiadm modify target-param --CHAP-name s062 iqn.2000-05.com.3pardata:20310002ac00003e

8.

Verify that bidirectional authentication is enabled.# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d Login Parameters (Default/Configured): Authentication Type: CHAP CHAP Name: iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d - # iscsiadm list target-param -v Target: iqn.2000-05.com.3pardata:20310002ac00003e Alias: Bi-directional Authentication: enabled Authentication Type: CHAP CHAP Name: -S062 Login Parameters (Default/Configured):

9.

Remove and create a new iSCSI session and invoke devfsadm -i iscsi to discover the targets and all the LUNs. NOTE: CHAP authentication will not be in effect for the most recently added devices until the current connection is removed and a new connection session is enabled. To enable authentication for all the devices, stop all associated I/O activity and unmount any file systems before creating the new connection session. This procedure is required each time a change is made to the CHAP configuration.

Disabling Bidirectional CHAPTo disable the CHAP authentication, follow these steps: 1. On the HP 3PAR Storage System, issue the sethost removechap command.# sethost removechap solarisiscsi # showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name1 solarisiscsi -- --

2.

On the host, disable and remove the target CHAP authentication on each target.# iscsiadm list target # iscsiadm modify target-param -B disable iqn.2000-05.com.3pardata:21310002ac00003e # iscsiadm modify target-param -B disable iqn.2000-05.com.3pardata:20310002ac00003e


27

# iscsiadm modify target-param --authentication NONE iqn.2000-05.com.3pardata:21310002ac00003 # iscsiadm modify target-param --authentication NONE iqn.2000-05.com.3pardata:20310002ac00003e # iscsiadm modify initiator-node --authentication NONE

3.

Verify that authentication is disabled.# iscsiadm list initiator-node scsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d Login Parameters (Default/Configured): Authentication Type: NONE # iscsiadm list target-param -v Target: iqn.2000-05.com.3pardata:20310002ac00003e Alias: Bi-directional Authentication: disabled Authentication Type: NONE

28


4 Configuring the Host for a Fibre Channel ConnectionThis chapter describes the procedures that are required to set up a Solaris host to communicate with an HP 3PAR Storage System over a Fibre Channel connection using a supported HBA.

Installing the HBABefore setting up the Solaris host, make sure the host adapters are installed and operating properly. If necessary, consult the documentation provided by the HBA vendor. When the server boots after the HBA installation, the /var/adm/messages directory will contain messages for each HBA port. These messages will vary depending on the HBA type and drivers that are being used.

Installing the SUN SAN Driver PackagesSolaris 10 The required Sun SAN software is installed as part of the OS distribution. Consult the Solaris OS minimum patch listings in Chapter 6 (page 52). NOTE: For Solaris 10, a Sun MPXIO patch is required that contains MPXIO fixes applicable for SCSI 3 reservations if SUN cluster is to be configured. For SPARC-based servers, use patch 127127-1 and for x86 based servers use patch 127128-1 For availability of later versions, 1 1. check the following Web site: http:/support.oracle.com/CSP/ui/flash.html. Solaris 8/9 Install the appropriate Sun SAN software package for Solaris 8 or 9 hosts available at the following location: http://www.oracle.com/us/products/servers-storage/storage/ storage-networking/index.htm Consult the Solaris OS minimum patch listings in Chapter 6 (page 52).

Installing the HBA DriversIf necessary, install the appropriate drivers for the type of HBA that is being used. For QLogic and Emulex HBAs, you have the option of using the (qlc or emlxs) drivers supplied with the Solaris SAN package or you can use the drivers supplied by the HBA vendor. Emulex LPFC Driver package(s) and driver installation instructions are available at: http://www.emulex.com/ QLogic QLA (qla2300) Driver package(s) and driver installation instructions are available at: http://www.qlogic.com/ NOTE: The SAN package may have an updated release of the emlxs /qlc drivers (also known as the Leadville drivers). For JNI HBAs, install the JNIfcaPCI (FCI-1063) or JNIfcaw (FC64-1063) driver package for the Solaris OS. The driver install package files fca-pci.pkg and fcaw.pkg contain the JNIfcaPCI, JNIfcaw and JNIsnia drivers. NOTE: The JNI HBA drivers are currently only supported for Solaris OS versions 8 and 9 in InForm OS 2.3.x. Refer to the Inform OS support matrices for updated information and support for Solaris 10.Installing the HBA 29

For more details, consult the appropriate driver installation notes in this section for the type of HBA being installed. You can also consult the HP Single Point of Connectivity Web site (HP SPOCK) to determine which drivers are appropriate for a given HBA or version of the Solaris OS: www.hp.com/storage/

Installation Notes for Emulex lpfc DriversThe following notes apply when connecting to a Solaris host that utilizes an Emulex HBA with an lpfc driver: The default or as installed parameter settings will allow the host to connect in either direct or fabric modes. Direct Connect: Configured by editing /kernel/drv/lpfc.conf and then running the udated_drv utility. On versions of Solaris prior to version 9, you have to manually reboot the host server to update the host with the modified driver configuration settings. Fabric Connect: Configured by editing /kernel/drv/lpfc.conf and then running the udated_drv utility. On versions of Solaris prior to version 9, you have to manually reboot the Solaris host to update with the modified driver configuration settings. The sd.conf file is read by the SD driver at boot time, so supporting entries for new LUNs must exist prior to the last server reboot. Add entries to the /kernel/drv/sd.conf file between the boundary comments generated by the Emulex driver package during installation.# Start lpfc auto-generated configuration -- do NOT alter or delete this line name="sd" parent="lpfc" target=0 lun=0; name="sd" parent="lpfc" target=0 lun=1; ... name="sd" parent="lpfc" target=0 lun=255; # End lpfc auto-generated configuration -- do NOT alter or delete this line

A line is required for each LUN number (pre 6.20 driver requirement). For fabric configurations, entries must be made for all target LUNs that will be exported from the HP 3PAR Storage System to the Solaris host. These entries can be restricted to the Emulex lpfc driver only, so a useful strategy is to add entries for all possible LUNs (0 to 255) on target 0. Testing at HP did not reveal any noticeable increase in server boot time due to the probing of non-existent LUNs. WARNING! Installing version 6.21g of the lpfc driver for Solaris may be significantly different than in previous releases. Follow the driver instructions precisely as instructed for initial installation. Failure to follow the proper installation steps could render your system inoperable.

30

Configuring the Host for a Fibre Channel Connection

NOTE: Emulex lpfc drivers 6.20 and above do not require LUN and Target entries in the /kernel/drv/sd.conf file. The lpfc driver can support up to 256 targets, with a maximum of 256 LUNs per target; additional LUNs will not be visible on the host. Solaris 8/9 LUN discovery for driver 6.21g requires the following command: /opt/HBAnyware/hbacmd RescanLuns HBAnyware software is available from the Emulex lpfc driver download site: http:// www.emulex.com/ NOTE: When adding specific entries in the sd.conf file for each LUN number that is expected to be exported from the HP 3PAR Storage System ports, new entries have to be added each time additional VLUNs are exported with new LUNs. Unless the host port will be communicating with more than one HP 3PAR Storage System port, Target=0 entries are sufficient. If a host port is communicating with more than a single HP 3PAR Storage System, then specific entries are required for the other targets (pre 6.20 driver requirement).

Configuration File Settings for Emulex lpfc DriversIn the following example, all default values in the /kernel/drv/lpfc.conf file were used except for the Link_down_timeout variable that is changed to reduce I/O stall timings.# # Determine how long the driver will wait [0 - 255] to begin linkdown # processing when the hba link has become inaccessible. Linkdown processing # includes failing back commands that have been waiting for the link to # come back up. Units are in seconds. linkdown-tmo works in conjuction # with nodev-tmo. I/O will fail when either of the two expires. linkdown-tmo=1; default is linkdown-tmo=30

WARNING! Any changes to the driver configuration file must be tested before going into a production environment.

Installation Notes for QLogic qla DriversThe following notes apply when connecting to a Solaris host that utilizes a QLogic HBA with a qla2300 driver. The default or as installed parameter settings in the /kernel/drv/qla2300.conf file will allow the host to connect in either direct or fabric modes. NOTE: The currently supported QLogic driver versions, as listed in the current InForm OS Configuration Matrix, do not require target and LUN entries in the /kernel/drv/sd.conf file.

Configuration File Settings for QLogic qla DriversIn the following example, all default values in the /kernel/drv/qla2300.conf file were used except for the hbaa0-link_down_timeout option that is used to reduce I/O stall timings.# Amount of time to wait for loop to come up after it has gone down # before reporting I/O errors. # Range: 0 - 240 seconds hba0-link-down-timeout=1; default is hba0-link-down-timeout=60; DO NOT LOWER below 30 for solaris 9

WARNING! Any changes to the driver configuration file must be tested before going into a production environment. WARNING! DO NOT LOWER the qla2300.conf variable hba0-link-down-timeout below 30 seconds for Solaris 9 hosts.Installing the HBA Drivers 31

Installation Notes for Solaris qlc and emlxs DriversThe following notes apply when connecting to a Solaris host that utilizes a QLogic or Emulex HBA and relies on the qlc or emlxs drivers supplied as part of the Sun SAN installation. The default or as installed parameter settings in the /kernel/drv/qlc.conf or /kernel/drv/emlxs.conf files allow the host to connect in either direct or fabric modes. Early versions of Sun's qlc and emlxs drivers had a very limited set of parameters available for adjustment. Testing was performed with all of the parameters listed in these configuration files set to their originally installed or default settings. NOTE: 4 GB/s Sun StorageTek SG- SG-xxxxxxx-QF4 and QLogic QLA24xx will be limited to 256 LUNs per target unless patch 1 19130 or 1 19131 is at revision -21 or higher.

Configuration File Settings for Solaris qlc and emlxs DriversNo configuration settings are required for Solaris qlc and emlxs drivers; the default /kernel/ drv/qlc.conf and /kernel/drv/emlxs.conf configuration settings are supported. WARNING! MPXIO on fp is enabled by default, so that running the stmsboot -e command erases the original fp.conf and replace it with a 2-line file. As a workaround, run stmsboot -d -D fp to disable the fp MPXIO first, then you should be able to run stmsboot -e successfully without loss of the fp HBA.

Installation Notes for JNI Tachyon fcaw and fca-pci driversThe following notes apply when connecting to a Solaris host that utilizes a JNI Tachyon HBA and relies on the fcaw and fca-pci drivers. NOTE: These technical notes only apply to InForm OS 2.2.x.

Direct Connect: Configured by editing the /kernel/drv/fca-pci.conf or /kernel/drv/fcaw.conf files:fca_nport = 0; # initialize on a loop public_loop = 0; # initialize according to what fca_nport is set to

Fabric Connect: Configured by editing the /kernel/drv/fca-pci.conf or /kernel/drv/fcaw.conf files:fca_nport = 1; # initialize as N_Port public_loop = 0; # initialize according to what fca_nport is set to

The JNIsnia package is included with the driver installation but is optional and is not required to access the HP 3PAR Storage System from the Solaris host. The driver packages and driver installation instructions are available at: http://www.amcc.com The fca-pci.conf and fcaw.conf files will be installed in the /kernel/ drv directory when the driver package is installed. In both direct connect and fabric configurations, (where each host HBA port logically connects to only one HP 3PAR Storage System port), each initiator (host server HBA port) can only discover one target (HP 3PAR Storage System port). For these configurations, persistent target binding in the HBA driver, although possible, is not required since there will only be one target found by each host HBA driver instance. When the binding parameters in the /kernel/drv/fca-pci.conf or /kernel/drv/fcaw.conf files

32


are left at their default settings, each instance of the JNI driver will automatically discover one HP 3PAR Storage System port and assign it a target value of 0 each time the Solaris host is booted. The following example shows the default fca-pci.conf settings:def_hba_binding = "fca-pci*"; def_wwpn_binding = "$xxxxxxxxxxxxxxxx"; def_wwnn_binding = "$xxxxxxxxxxxxxxxx"; def_port_binding = "xxxxxx"; Default fcaw.conf settings: def_hba_binding = "fcaw*"; def_wwpn_binding = "$xxxxxxxxxxxxxxxx"; def_wwnn_binding = "$xxxxxxxxxxxxxxxx"; def_port_binding = "xxxxxx";

If changes in the mapping of a device to its device node (/dev/rdsk/cxtxdx) cannot be tolerated for your configuration, you can assign and lock target IDs based on the HP 3PAR Storage System port's World Wide Port Name by adding specific target binding statements in the /kernel/drv/fca-pci.conf or /kernel/drv/fcaw.conf file. Refer to the fca-pci or fcaw driver documentation and the /opt/JNIfcaPCI/technotes or /opt/JNIfcaw/technotes files for more information about mapping discovered targets to specific target IDs on the host. The Solaris sd SCSI driver will only probe for targets and LUNs that are configured in the /kernel/ drv/sd.conf file. For fabric configurations, entries must exist for all target/LUNs that are exported from the HP 3PAR Storage System to the Solaris host. The sd.conf file is read by the sd driver at boot time, so supporting entries for new LUNs must exist prior to the last server reboot. These entries can be restricted to the JNI fca-pci or fcaw driver only, thus, a useful strategy is to add entries for all possible LUNs (0 to 255) on target "0". For instance, add the following entries to the sd.conf file: JNI fcaw driver:name="sd" parent="fcaw" target=0 lun=0; ... name="sd" parent="fcaw" target=0 lun=255;

JNI fca-pci driver:name="sd" parent="fca-pci" target=0 lun=0; ... name="sd" parent="fca-pci" target=0 lun=255;

Testing at HP did not reveal any noticeable increase in server boot time due to the probing of non-existent LUNs. For some installations, you may want to place specific entries for the actual LUN numbers exported from the HP 3PAR Storage System ports in the sd.conf file. However, this approach requires additional entries and a reboot of the Solaris host when new VLUNs are later exported with new LUN numbers.

Installing the HBA Drivers

33

NOTE: Each target/LUN entry in sd.conf for non-existent LUNs (a LUN that has not yet been exported from the HP 3PAR Storage System) will result in probed fail messages from the fca-pci or fcaw driver in the /var/adm/messages file and on the server console each time the driver scans for devices in response to the Solaris devfsadm command. These messages can be minimized or eliminated by populating /kern/drv/sd.conf with fewer entries. HP recommends that the sd.conf file be populated with all possible target/LUN combinations that may be exported from the HP 3PAR Storage System, despite the probe fail messages, to avoid having to reboot the host server to register newly exported HP 3PAR Storage System LUNs. NOTE: Target=0 entries are sufficient unless a host port will detect more than one HP 3PAR Storage System port, or the one that is detected has been persistently bound to a different target number. In this case, entries will be required for other targets. The optional EZFibre GUI utility is available at http://www.amcc.com/. This utility provides a view of each JNI HBA port on the server and the targets and LUNs each has acquired. This utility can also be used to statically target bind discovered targets and LUNsif that is a requirement of your specific configuration.

Configuration File Settings for JNI Tachyon DriversThe following /kernel/drv/fcaw.conf configuration settings were used for testing purposes by HP on a fabric connection:fca_nport = 1; public_loop = 0; def_wwpn_binding = "$xxxxxxxxxxxxxxxx"; def_wwnn_binding = "$xxxxxxxxxxxxxxxx"; def_port_binding = "xxxxxx";

Installation Notes for JNI Emerald JNIC146x DriversThe following notes apply when connecting to a Solaris host that utilizes a JNI Emerald HBA and relies on the JNIC146x drivers. NOTE: These technical notes only apply to InForm OS 2.2.X.

Direct Connect: Configured by editing the /kernel/drv/jnic146x.conf file:FcLoopEnabled = 1; FcFabricEnabled = 0; automap = 2;

Fabric Connect: Configured by editing the /kernel/drv/jnic146x.conf file:FcLoopEnabled = 0; FcFabricEnabled = 1; automap = 1;

Install the JNI driver package version 5.3.1.3. The driver install package file JNIC146x.pkg contains the JNIC146x and JNIsnia packages. The JNIsnia package is optional and is not required to access the HP 3PAR Storage System from the Solaris host. The driver packages and driver installation instructions are available at http://www.amcc.com. The jnic146x.conf file

34


will be installed in the /kernel/drv directory as the driver package is installed. Edit the /kernel/ drv/jnic146x.conf file by adding the following entries. Direct Connect:FcLoopEnabled=1;# disable loop mode FcFabricEnabled=0;# enable fabric mode automap=2;# automap target/LUN's For Fabric Connect: FcLoopEnabled=0;# disable loop mode FcFabricEnabled=1;# enable fabric mode automap=1;# automap target/LUN's

Unload and reload the jnic146x driver so that the edits to /kernel/drv/jnic146x.conf take effect.# /opt/JNIC146x/jnic146x_unload # /opt/JNIC146x/jnic146x_load

Verify that each JNI HBA is loaded with FCode firmware version 3.91. There will be messages for each HBA port in the /var/adm/messages file. NOTE: If the HBAs are not using FCode firmware version 3.9.1 or later, upgrade the FCode firmware. FCode firmware and installation instructions are available as install packages (specific to each HBA model) from: http://www.amcc.com/ JNIC146x driver versions 5.3 and greater do not require LUN and target entries in the/kernel/drv/sd.conf file. The optional EZFibre GUI utility is available at http://www.amcc.com/. This utility gives a view of each JNI HBA port in the server and the targets and LUNs each has acquired. This utility can also be used to statically target bind discovered targets and LUNs if that is a requirement of your specific configuration. Perform a reconfigure reboot of the host server (reboot -- -r) or create the file/reconfigure so that the next server boot will be a reconfiguration boot.# touch /reconfigure

Configuration File Settings for JNI Emerald DriversThe following /kernel/drv/jnic146x.conf configuration settings were used for testing purposes by HP. All default values are used except for the following variations: Direct Connect:FcLoopEnabled = 1; # use for direct connections FcFabricEnabled = 0; # use for direct connections automap = 2; # use for direct connections

Fabric Connect:FcLoopEnabled = 0; # use for fabric connections FcFabricEnabled = 1; # use for fabric connections automap = 1; # use for fabric connections Installing the HBA Drivers 35

Verifying the Driver Package InstallationTo verify that the driver has loaded properly, use the appropriate modinfo command for the type of driver you are installing.# modinfo | egrep "lpfc|qla2300|qlc|emlxs|jni]"

Relevant messages are recorded in the /var/adm/messages file for each port that has an associated driver and can be useful for verification and troubleshooting. NOTE: The Solaris supplied emlxs driver may bind to the Emulex HBA ports and prevent the Emulex lpfc driver from attaching to the HBA ports. Emulex provides an emlxdrv utility as part of the "FCA Utilities" available for download from www.emulex.com. You can use the emlxdrv utility to adjust the driver bindings on a per HBA basis on the server between the Emulex lpfc driver and the Sun emlxs driver. You may need to use this utility if the lpfc driver does not bind to the Emulex based HBAs upon reconfigure-reboot. Solaris 8 requires that the emlxdrv pkg be removed before installing the lpfc driver.

Setting Up Dynamic Multipathing for the Solaris HostTwo options for multipathing (Veritas Volume Manager VxDMP and Sun StorEdge Traffic Manager SSTM) are supported by the Solaris OS.

Using Veritas Volume Manager VxDMP MultipathingAs an option, you can use Veritas Volume Manager for multi-path load balancing and failover. Install a supported version of Veritas Volume Manager using the Veritas Volume Manager user guide. Veritas Volume Manager and its user guide are available from:http:// www.veritas.com/ Refer to the HP 3PAR InForm OS Configuration Matrix for a list of supported Veritas Volume Manager versions. NOTE: Refer to Allocating Storage for Access by the Solaris Host (page 52) for supported driver/DMP combinations. To enable the Veritas DMP driver to manage multipathed server volumes, install the Array Support Library (ASL) for HP 3PAR Storage Systems (VRTS3par package) on the Solaris host. This ASL is installed automatically with the installation of 5.0MP3 and above. For older versions of VxDMP, the ASL will need to be installed separately. Install the VRTS3par package from the VRTS3par_SunOS_50 distribution package for Veritas Volume Manager versions 5.0 and 5.0MP1. Install the VRTS3par package from the VRTS3par_v1.2_SunOS_40 distribution package for Veritas Volume Manager versions 4.0 and 4.1.

These VRTS3par packages are available from http://support.veritas.com/. NOTE: Some distributions of the Veritas software include a VRTS3par package that is copied to the host server as the Veritas software is installed. This package is likely to be an older VRTS3par package (version 1.0 or 1.1), which should not be used. Instead, install the current VRTS3par package from the Veritas support site. The following setting on the enclosure is required if long failback times are causing some concern. This enclosure setting can be used with 5.0GA, 5.0MP1, 5.0MP3 and 5.1GA VxDMP:# vxdmpadm setattr enclosure recoveryoption=timebound iotimeout=60

36


If not set, I/O will eventually failback to the recovered paths. The default value for the enclosure is "fixed retry=5". To return the setting to default:# vxdmpadm setattr enclosure recoveryoption=default

Verifying the VxDMP ASL InstallationTo confirm that the Veritas VxDMP driver has been registered to claim the HP 3PAR Storage System, issue the Veritas vxddladm listsupport libname=libvx3par.so command.# vxddladm listsupport libname=libvx3par.so ATTR_NAME ATTR_VALUE ======================================================================= LIBNAME libvx3par.so VID 3PARdata PID VV ARRAY_TYPE A/A ARRAY_NAME 3PARDATA

You can also consult the following file:# /opt/VRTS/bin/vxddladm listversion

WARNING! Failure to claim the HP 3PAR Storage System as an HP 3PAR array will affect the way devices are discovered by the multipathing layer. WARNING! The minimum supported software installation version for VxDMP_5.0MP3 is VxDMP_5.0MP3_RP1_HF3 with vxdmpadm settune dmp_fast_recovery=off. This tunable can be left at default values with later versions VxDMP_5.0MP3_RP2_HF1 and VxDMP_5.0MP3_RP3. CAUTION: You may need to reboot the host if you wish to reuse vLUN numbers with the following VxDMP versions: VxDMP_5.0MP3_RP3 or VxDMP_ 5.1. Veritas has enhanced data protection code which may be triggered if a vLUN number is reused, "Data Corruption Protection Activated".

Using Sun StorageTek Traffic Manager (SSTM) MultipathingThe Solaris 10 OS contains the Solaris FC and Storage Multipathing software (Sun StorageTek Traffic Manner - SSTM). The following notes apply for various OS versions. Solaris 8/9/10 For all releases of Solaris, edit the /kernel/drv/scsi_vhci.conf file to allow StorEdge Traffic Manager (SSTM) to recognize HP 3PAR VLUNs on the host system (see section Section (page 38) for context change). An additional variable change is required for Solaris 8 and 9 (see section Section (page 38) for context change.) Solaris 10

Setting Up Dynamic Multipathing for the Solaris Host

37

Additionally, to enable Sun StorageTek Traffic Manager (SSTM) for all HBAs on Solaris 10 systems, issue the stmsboot -e command to enable multipathing (stmsboot -d will disable multipathing). CAUTION: When running Solaris 10 MU7, enabling SSTM on a fresh install using stmsboot -e can corrupt the fp.conf configuration. To avoid this, issue stmsboot -d -D fp to disable the fp mpxio. You should then be able to run stmsboot -e successfully without loss of the fp HBA. For more information on this workaround, consult: http://bugs.opensolaris.org/bugdatabase view_bug.do;jsessionid=8de823511efa700410638295d36c?bug_id=6811044

Edits to the /kernel/drv/scsi_vhci.conf file for SSTM MultipathingEdit the /kernel/drv/scsi_vhci.conf file and add the appropriate entries for the InForm OS version that is being used by the HP 3PAR Storage System. InForm 2.3.x and 3.1.xdevice-type-scsi-options-list = "3PARdataVV", "symmetric-option", "3PARdataSES", "symmetric-option"; symmetric-option = 0x1000000;

InForm 2.2.xdevice-type-scsi-options-list = "3PARdataVV", "symmetric-option"; symmetric-option = 0x1000000;

Additional edit to the /kernel/drv/scsi_vhci.conf file for Solaris 8/9Edit the /kernel/drv/scsi_vhci.conf file to enable StorEdge Traffic Manager (SSTM) globally for all HBAs in the system by changing the parameter mpxio-disable to a value of no. Add the following entry at the end of the file:mpxio-disable="no"; (default is "yes")

NOTE:

After editing the configuration file, perform a reconfiguration reboot of the Solaris host.

SPARC: issue reboot -- -r x64/x86: create the file /reconfigure so that the next server boot will be a reconfiguration boot. # touch /reconfigure NOTE: For detailed installation instructions, consult the Solaris Fiber Channel and Storage Multipathing Administration Guide located at the following address: http://www.sun.com/storage/san/ This document includes instructions for enabling Solaris I/O Multipathing on specific Sun HBA ports but does not apply for other HBAs.

Persistent Target Binding ConsiderationsPersistent target binding ensures that the mapping of a given target to a physical storage device remains the same from one reboot to the next. In most cases, where each HBA port logically38 Configuring the Host for a Fibre Channel Connection

connects to only one HP 3PAR Storage System port, it is not necessary to specifically implement persistent target binding through configuration of the HBA driver since each initiator (Solaris host HBA port) can only discover one target (HP 3PAR Storage System port) as shown in Figure 6 (page 39). Figure 6 Persistent Target Binding

While the HP 3PAR Storage System is running, departing and returning HP 3PAR Storage System ports (e.g., un-plugged cable) are tracked by their World Wide Port Name (WWPN). The WWPN of each HP 3PAR Storage System port is unique and constant which ensures correct tracking of a port and its LUNs by the host HBA driver. However, in configurations where multiple HP 3PAR Storage System ports are available for discovery, some specific target binding may be necessary. The following section describes considerations for implementing persistent binding for each type of HBA that is supported by the Solaris OS.

Persistent Target Binding for Emulex lpfc DriversBy having the Automap set to a value of 1 and the fcp-bind-method set to a value of 2 in the /kernel/drv/lpfc.conf file, each HP 3PAR Storage System port will automatically be discovered and assigned a target value of 0 each time the host server is booted. For configurations where a host HBA port logically connects to more than one HP 3PAR Storage System port, it can be useful to persistently bind each storage server port to a specified target ID. This process is discussed in Section (page 14). For more information on setting the persistent target binding capabilities of the Emulex HBA lpfc driver, consult the Emulex documentation that is available from the following location: //http:/www.emulex.com/

Persistent Target Binding Considerations

39

Persistent Target Binding for QLogic qla DriversBy leaving the binding parameters at their default settings in /kernel/drv/qla2300.conf, each instance of the qla driver will automatically discover one HP 3PAR Storage System port and assign it a target value of 0 each time the Solaris host is booted. The target component of the device node for each HP 3PAR Storage System volume will be assigned a target "t" component equal to 0. The following example shows the default settings:hba0-persistent-binding-configuration=0; # 0 = Reports to OS discovery of binded and non-binded devices hba0-persistent-binding-by-port-ID=0; # Persistent binding by FC port ID disabled

If a fabric zoning relationship exists such that a host HBA port has access to multiple targets (for example, multiple ports on the HP 3PAR Storage System) the driver will assign target IDs (cxtxdx) to each discovered target in the order that they are discovered. In this case, the target ID for a given target can chan

Documents

HP 3PAR Solaris Implementation Guide Dec2011 c02663731