hpe 3par windows server 2003 implementation guide · introduction hewlett packard enterprise (hpe)...

HPE 3PAR Windows Server 2003Implementation Guide

Part Number: QL226-99600Published: June 2017

AbstractThis implementation guide provides the information needed to configure an HPE 3PARStoreServ Storage system with Microsoft Windows 2003 servers. This guide covers HPE3PAR StoreServ Storage systems running HPE 3PAR OS 3.3.x, 3.2.x and 3.1.x.

© Copyright 2012, 2017 Hewlett Packard Enterprise Development LP

NoticesThe information contained herein is subject to change without notice. The only warranties for HewlettPackard Enterprise products and services are set forth in the express warranty statements accompanyingsuch products and services. Nothing herein should be construed as constituting an additional warranty.Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions containedherein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession,use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, ComputerSoftware Documentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett PackardEnterprise website.

AcknowledgmentsIntel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation inthe United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

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

UNIX® is a registered trademark of The Open Group.

Contents

Introduction............................................................................................. 6Audience....................................................................................................................................... 6Supported configurations.............................................................................................................. 6HPE 3PAR OS upgrade considerations........................................................................................7HPE 3PAR documentation............................................................................................................7

Performing preliminary 3PAR StoreServ Storage and hostconfiguration........................................................................................... 8

Configuring the 3PAR StoreServ Storage host persona and ports............................................... 8Configuring ports on the HPE 3PAR StoreServ Storage for a direct connection—FC.......8Configuring ports on the 3PAR StoreServ Storage—fabric connection—FC...................10Create a host definition—FC............................................................................................ 11

Installing the Windows Null driver............................................................................................... 12Connect the 3PAR StoreServ Storage to the host—FC..............................................................13Set up multipathing—FC.............................................................................................................13Setting up and zoning the fabric—FC......................................................................................... 14

HPE 3PAR Smart SAN—FC............................................................................................ 15HPE 3PAR coexistence....................................................................................................15Configuration guidelines for switch vendors—FC............................................................ 15Target port limits and specifications—FC.........................................................................16HPE 3PAR Priority Optimization—FC.............................................................................. 18HPE 3PAR Persistent Ports—FC.....................................................................................18

HPE 3PAR Persistent Ports setup and connectivity guidelines—FC.................... 18HPE 3PAR Express Writes—FC................................................................................................. 19

Setting up a Windows Server 2003 and Windows Server2003 3PAR StoreServ Storage configuration—FC............................. 20

Checking the host for required drivers........................................................................................ 20Installing and configuring an Emulex HBA—FC......................................................................... 20

Configuring the Emulex support driver.............................................................................20Checking Emulex HBA parameters and connection status..............................................20

Installing and configuring a QLogic HBA—FC............................................................................ 21Configuring the QLogic support driver............................................................................. 21Checking QLogic HBA parameters and connection status.............................................. 21

Installing the HPE 3PAR MPIO on the host................................................................................ 21Installing Veritas DMP multipathing on the Windows Server 2003 host..................................... 22Disabling the write cache option for 3PAR LUNs ................................................................. 23

Setting up a Windows Server 2003 and 3PAR StoreServ Storageconfiguration—iSCSI............................................................................ 25

Setting up the initiator and target ports—iSCSI.......................................................................... 25Configuring the 3PAR StoreServ Storage—iSCSI...................................................................... 25Using the Microsoft iSNS server to discover registrations.......................................................... 27

Configuring the initiator and target for iSNS server usage—iSCSI.................................. 27Establishing a connection with the iSCSI Initiator software........................................................ 28

Contents 3

Establishing an iSCSI session and enabling multipathing.......................................................... 31Configure host and target CHAP................................................................................................ 34

Setting host CHAP........................................................................................................... 34Setting target CHAP.........................................................................................................37Set mutual (bidirectional) CHAP...................................................................................... 39Removing CHAP.............................................................................................................. 39

Target port limits and specifications—iSCSI............................................................................... 40HPE 3PAR Persistent Ports—iSCSI........................................................................................... 40

HPE 3PAR Persistent Ports setup and connectivity guidelines—FC............................... 41

Allocating storage for the Windows Server 2003 host...................... 42Creating storage on the HPE 3PAR StoreServ Storage............................................................. 42

Create virtual volumes......................................................................................................42Creating thinly provisioned virtual volumes......................................................................43Creating thinly deduplicated virtual volumes....................................................................43Creating thinly compressed virtual volumes.....................................................................44Exporting VLUNs to the host............................................................................................44Restrictions on volume size and number......................................................................... 44

Discovering LUNs....................................................................................................................... 44Scanning for new devices on a Windows Server 2003 host....................................................... 45Removing a storage volume from the host................................................................................. 46

Booting from the 3PAR StoreServ Storage........................................ 47Configuring for iSCSI SAN boot..................................................................................................47Configuring the BIOS for FC SAN boot.......................................................................................47

Configuring for a 3PAR StoreServ Storage boot—Emulex HBA......................................47Configuring for a 3PAR StoreServ Storage boot—QLogic HBA.......................................48

Creating the host definition for a 3PAR StoreServ Storage boot—FC........................................48Connecting the 3PAR StoreServ Storage to the host—FC.........................................................49Assigning LUNs as the boot volume........................................................................................... 49Installing the host OS onto the FC boot volume......................................................................... 49Connecting multiple paths for FC SAN boot............................................................................... 49

HPE 3PAR All Flash Array.................................................................... 50

Configuring File Persona..................................................................... 51HPE 3PAR File Persona............................................................................................................. 51

Using the Veritas Cluster Server......................................................... 52Symantec Storage Foundation................................................................................................... 52Installing the Veritas Cluster Server............................................................................................52Setting SCSI-3 Persistent Reservation support for the 3PAR StoreServ Storage...................... 52

Using Microsoft Clustering with Veritas DMP.................................... 55Installing the Veritas DMP...........................................................................................................55Setting SCSI-3 Persistent Reservation support for the 3PAR StoreServ Storage...................... 56

Using the HPE PolyServe Matrix Server............................................. 59

4 Contents

Websites................................................................................................ 60

Support and other resources...............................................................61Accessing Hewlett Packard Enterprise Support......................................................................... 61Accessing updates......................................................................................................................61Customer self repair....................................................................................................................62Remote support.......................................................................................................................... 62Warranty information...................................................................................................................62Regulatory information................................................................................................................63Documentation feedback............................................................................................................ 63

Contents 5

IntroductionHewlett Packard Enterprise (HPE) implementation guide provides the information needed to configure anHPE 3PAR StoreServ Storage system with Microsoft Windows 2003 servers.

NOTE:

• For predictable performance and results with the HPE 3PAR StoreServ Storage, the informationin this guide must be used in concert with the documentation provided by Hewlett PackardEnterprise for the HPE 3PAR StoreServ Storage and the documentation provided by the vendorfor their respective products.

• In addition to the OS patches mentioned in this guide, there might be additional patchesreferenced at the Storage Single Point of Connectivity Knowledge (SPOCK) website.

For information about supported hardware and software platforms, see SPOCK (SPOCK Home >Explore Storage Interoperability With SPOCK > Explore HPE 3PAR StoreServ Storageinteroperability.

AudienceThis implementation guide is intended for system and storage administrators who monitor and directsystem configurations and resource allocation for the 3PAR StoreServ Storage.

The tasks described in this guide assume that the administrator is familiar with Windows Server 2003 andthe HPE 3PAR OS.

Supported configurationsThe following types of host connections are supported between the 3PAR StoreServ Storage and hostswith an Windows Server 2003 OS:

• FC (Fibre Channel)• Software iSCSI initiator

FC connections are supported between the 3PAR OS and the host in both a fabric-attached and direct-connect topology.

A configuration with an Windows Server 2003 host requires the following software on the host, dependingon the host configuration and unless otherwise specified:

• The 3PAR NULL driver for Windows Server 2003, is available as a zip file (QL226-10001.zip) atSoftware Depot. Search the Software Depot for 3PAR NULL INF for SCSI Enclosure Device.

http://www.hpe.com/support/softwaredepot• FC multipathing: HPE 3PAR MPIO or Veritas VxDMP• iSCSI only:

◦ Microsoft iSCSI initiator◦ Booting from the 3PAR OS: the Double-Take Flex software.◦ Multipathing: native Microsoft MPIO

NOTE:

For a Software iSCSI-connected configuration, see the HPE Windows Server 2008, WindowsServer 2003 Microsoft iSCSI Software Initiator Version 2.X Users Guide.

6 Introduction

http://www.hpe.com/support/softwaredepot

HPE 3PAR OS upgrade considerationsThis implementation guide refers to new installations. For information about planning an online HPE3PAR OS upgrade, see the HPE 3PAR Operating System Upgrade Planning Guide at the HewlettPackard Enterprise Information Library website.

For complete details about supported host configurations and interoperability, see the SPOCK website:SPOCK Home > Explore Storage Interoperability With SPOCK > Explore 3PAR StoreServ Storageinteroperability.

More Informationhttp://www.hpe.com/info/storage/docshttp://www.hpe.com/storage/spock

HPE 3PAR documentationType of documentation: See:

Current version of this implementationguide and additional HPE 3PAR StoreServstorage documentation:

Hewlett Packard Enterprise Information Library

Supported hardware and softwareplatforms:

The Single Point of Connectivity Knowledge (SPOCK)

Customer Self Repair procedures (media): Hewlett Packard Enterprise Customer Self RepairServices Media Library

1. Under Product category, select Storage.2. Under Product family, select 3PAR StoreServ

Storage.3. Under Product series, select your product series.

All Hewlett Packard Enterprise products: Hewlett Packard Enterprise Support Center

HPE 3PAR OS upgrade considerations 7

http://www.hpe.com/info/storage/docs


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





http://www.hpe.com/support/csr

http://www.hpe.com/support/csr

http://www.hpe.com/support/hpesc

Performing preliminary 3PAR StoreServStorage and host configuration

Required

If you are setting up a fabric along with your installation of the 3PAR StoreServ Storage, see Set up andzone the fabric—FC, before configuring or connecting the storage server and host.

NOTE: Hewlett Packard Enterprise recommends using default values to configure your host unlessotherwise specified in the following procedures.

Configuring the 3PAR StoreServ Storage host persona andports

For a 3PAR StoreServ Storage system running 3PAR OS 3.2.x or 3.1.x, each 3PAR StoreServ Storageport connecting to a host HBA port through a fabric or direct connection must be set to the correct hostpersona.

NOTE: When deploying HPE Virtual Connect Direct-attach FC Storage for 3PAR StoreServStorage, where the 3PAR StoreServ Storage ports are cabled directly to the uplink ports on theVirtual Connect FlexFabric 10 Gb/24-port Module for c-Class BladeSystem, follow the steps forconfiguring the 3PAR StoreServ Storage ports for a fabric connection.

For more information about Virtual Connect, Virtual Connect interconnect modules, and the VirtualConnect direct-attach feature, see the Virtual Connect documentation available by searching theHewlett Packard Enterprise Support Center website.

See also theHPE SAN Design Reference Guideat the Storage Single Point of ConnectivityKnowledge (SPOCK) website.

More Informationhttp://www.hpe.com/support/hpeschttp://www.hpe.com/storage/spock

Configuring ports on the HPE 3PAR StoreServ Storage for a directconnection—FC

A different FC array target port connection type is required depending on the HPE 3PAR OS version onthe array on the array, the array target port type, and the speed of host FC adapter that will directlyconnect to the array.

NOTE:

Support for direct connection to hosts using the 16 Gbps FC 3PAR StoreServ Storage target beginsat HPE 3PAR OS version 3.3.1 GA.

To identify the type of array target port adapter, use the showport -par command and identify theMaxRate listed for the port planned for direct connect. For example, array target port 0:1:1 is listed as8Gbps and 2:1:1 as 16Gbps:

8 Performing preliminary 3PAR StoreServ Storage and host configuration



cli % showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal TMWO Smart_SAN0:1:1 host loop auto 8Gbps disabled disabled disabled disabled enabled n/a1:1:1 host loop auto 8Gbps disabled disabled disabled disabled enabled n/a2:1:1 host point auto 16Gbps disabled disabled disabled disabled disabled unsupported3:1:1 host point auto 16Gbps disabled disabled disabled disabled disabled unsupported

Support for direct connection to FC 3PAR StoreServ Storage target interfaces is limited to specific hostadapters. For more information, see the SPOCK website (SPOCK Home →Explore Storageinteroperability With SPOCK →Explore 3PAR StoreServ Storage interoperability). Once you havedetermined your host has a supported adapter, use the Direct Connection Support table to determine therequired connection type to set on the HPE 3PAR array:

Table 1: Direct Connection Support

HPE 3PAR OSversion

3PAR Array FCTarget Port

Supported HostAdapter Port

Connection Type Link Speed

3.2.2 and earlier 8 Gbps 4 Gbps Loop 4 Gbps

8 Gbps Loop 8 Gbps

16 Gbps Loop 8 Gbps

16 Gbps Not supported Not supported Not supported

3.3.1 GA and later 8 Gbps 4 Gbps Loop 4 Gbps

8 Gbps Loop 8 Gbps

16 Gbps Loop 8 Gbps

16 Gbps 4 Gbps Loop 4 Gbps

8 Gbps Loop 8 Gbps

16 Gbps Point 16 Gbps

32 Gbps Point 16 Gbps

Configuring the FC 3PAR StoreServ Storage Target Interface for Direct Connection

Run the following HPE 3PAR CLI commands with the appropriate parameters for each direct connectport:

1. Take the port off line using the controlport offline <node:slot:port> command:

Performing preliminary 3PAR StoreServ Storage and host configuration 9

cli % controlport offline 0:1:1

2. Run the controlport config host -ct <connection type> <node:slot:port>command, where <connection type> specifies the required value loop or point for theconnection.

cli % controlport config host -ct loop 0:1:1

3. Reset the port by using the controlport rst <node:slot:port> command on the 3PARStoreServ Storage

cli % controlport rst 0:1:1

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

cli % showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal TMWO Smart_SAN0:1:1 host loop auto 8Gbps disabled disabled disabled disabled enabled n/a

or

cli % showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal TMWO Smart_SAN0:1:1 host point auto 8Gbps disabled disabled disabled disabled enabled n/a

More Informationhttp://www.hpe.com/storage/spock

Configuring ports on the 3PAR StoreServ Storage—fabric connection—FCTo configure 3PAR StoreServ Storage ports for fabric connections on the HPE 3PAR CLI, use thefollowing procedure. Complete this procedure for each port.

Procedure

1. Check if a port is configured for a host port in fabric mode by using the HPE 3PAR CLI showport -par command on the 3PAR StoreServ Storage.

10 Configuring ports on the 3PAR StoreServ Storage—fabric connection—FC


If the connection type ConnType value is point, the port is already configured for a fabric connection.If the ConnType value is loop, the port is a direct connection and has not been configured for a fabricconnection.

cli % showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal0:4:1 host point auto 8Gbps disabled disabled disabled enabled

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

CAUTION:

Before taking a port offline in preparation for a fabric connection, verify that it was not previouslydefined and that it is not connected to a host, because this would interrupt the existing hostconnection. If a 3PAR StoreServ Storage port is already configured for a fabric connection,ignore this step 2.

To take the port offline, run the controlport offline <node:slot:port> command on the3PAR StoreServ Storage. For example:

cli % controlport offline 1:5:1

3. To configure the port to the host, run the controlport config host -ct point<node:slot:port> command on the 3PAR StoreServ Storage, where -ct point indicates thatthe connection type is a fabric connection. For example:

cli % controlport config host -ct point 1:5:1

4. Reset the port by using the controlport rst <node:slot:port> command on the 3PARStoreServ Storage. For example:

cli % controlport rst 1:5:1

5. Connect each host HBA port to the fabric. Associate the world wide name (WWN) of each host HBAport with the 3PAR StoreServ Storage port where it connects.

6. Complete the zoning using the procedure in: Set up and zone the fabric—FC.7. Run the showhost command on the 3PAR StoreServ Storage to verify that the host has successfully

connected to the 3PAR StoreServ Storage.

Create a host definition—FCCreate a host definition for FC overview

Before connecting the host to the 3PAR StoreServ Storage using 3PAR OS 3.2.x or 3.1.x, create a hostdefinition for the host.

Hewlett Packard Enterprise recommends host Generic Persona 1 for supported hosts to enableHPE 3PAR Host Explorer functionality. However, host Generic-Legacy Persona 6 is automaticallyassigned following a rolling 3PAR OS upgrade from version 3.1.1. If appropriate, change host Generic-

Create a host definition—FC 11

Legacy Persona 6 after an upgrade to host Generic Persona 1. Host Generic Persona 1 enables twofunctional features: HPE 3PAR Host Explorer, which requires the SESLun element of host GenericPersona 1 and the UARepLun, which notifies the host of newly exported VLUNs and should trigger a LUNdiscovery request on the host, making the VLUN automatically available. However, Windows Server 2003does not support this feature, so scan LUNs manually.

For complete details about using the controlport, createhost, and showhost commands, see theHPE 3PAR Command Line Interface Reference or the HPE 3PAR StoreServ Management ConsoleUser’s Guide available at the Hewlett Packard Enterprise Storage Information Library.

Creating a host definition for FC

1. Create host definitions by using the createhost [options] <hostname> [<WWN>...]command. For example:

cli % createhost -persona 1 windowshost 10000000C9606724

2. Verify that the host was created by using the showhost command.

cli% showhost

Id Name Persona -WWN/iSCSI_Name- Port 0 windowshost Generic-ALUA 10000000C9606724 ---

More Informationhttp://www.hpe.com/info/storage/docs

Installing the Windows Null driverWith a 3PAR StoreServ Storage system running 3PAR OS 3.2.x and 3.1.x, the Microsoft null driver isrequired for a Windows Server 2003 configuration. If the Windows Server 2003 host does not alreadyhave the null driver installed, a popup appears for each installed storage device, as shown in the figurebelow.

12 Installing the Windows Null driver


Figure 1: NULL Driver Warning Popup

To install the null driver, download QL226-10001.zip from the HPE Software Depot website and followthe installation instructions in its documentation:


Connect the 3PAR StoreServ Storage to the host—FCDuring this stage, connect the 3PAR StoreServ Storage to the host directly or to the fabric. Theseprocedures include the task to physically cable the 3PAR StoreServ Storage to the host or fabric.

Required:

For FC, verify that the required drivers are installed and that they are configured correctly. For moreinformation, see Checking the host for required drivers.

Set up multipathing—FCHewlett Packard Enterprise supports the following multipath solutions for Windows Server 2003:

• 3PAR MPIO• Veritas DMP/Veritas Infoscale Enterprise (Storage)

Specific topics in Setting up a Windows Server 2003 and Windows Server 2003 3PAR StoreServStorage configuration—FC and Setting up a Windows Server 2003 and 3PAR StoreServ Storageconfiguration—iSCSI explain details of configuring the 3PAR StoreServ Storage and Windows Server2003 host for multipathing. Different software is required, depending on the connection type:

• FC: Use only 3PAR MPIO, explained in Installing the HPE 3PAR MPIO on the host.• iSCSI: Use only the native Microsoft MPIO, explained in Establishing an iSCSI session and

enabling multipathing.

Connect the 3PAR StoreServ Storage to the host—FC 13


Setting up and zoning the fabric—FCNOTE: This topic does not apply when deploying Virtual Connect Direct-Attach Fibre Channel forHPE 3PAR StoreServ Storage systems, where the HPE 3PAR StoreServ Storage ports are cableddirectly to the uplink ports on either the Virtual Connect FlexFabric 10 Gb/24-port Module for c-ClassBladeSystem or Virtual Connect FlexFabric 20/40 F8 Module for c-Class BladeSystem. Zoning isautomatically configured based on the Virtual Connect SAN Fabric and server profile definitions.

For more information about Virtual Connect, Virtual Connect interconnect modules, and the VirtualConnect Direct-Attach Fibre Channel feature, see the Hewlett Packard Enterprise Support Centerwebsite.

See also the HPE SAN Design Reference Guide at the SPOCK website (SPOCK Home > DesignGuides > SAN Design Guide).

Fabric zoning controls which FC end-devices have access to each other on the fabric. Zoning alsoisolates the host and HPE 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 ports withspecified zones in the fabric. Using the WWN method or HPE Smart SAN zoning is recommended withthe HPE 3PAR StoreServ Storage. These zoning methods allow the zone to survive changing of switchports when cables are moved around on a fabric and are also compatible with Persistent Port feature.PORT zoning or Hard zoning is not recommended as it is not compatible with Persistent Port Feature.

Required:

Employ fabric zoning, by using the methods provided by the switch vendor, to create relationshipsbetween host HBA/CNA ports and HPE 3PAR StoreServ Storage ports before connecting the hostHBA/CNA ports or HPE 3PAR StoreServ Storage ports to the fabrics.

FC switch vendors support the zoning of the fabric end-devices in different zoning configurations. Thereare advantages and disadvantages with each zoning configuration, so determine what is needed beforechoosing a zoning configuration.

For configuring HP FlexFabric 5900 switch settings for FCoE Host - FC Storage connections refer to HPENetworking Single-Tier FC/FCoE Solution using HPE Rack Servers and HPE Storage.

The HPE 3PAR StoreServ Storage 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 is recommended

for the HPE 3PAR StoreServ Storage. Zoning by HBA is required for coexistence with other HewlettPackard Enterprise storage systems.

NOTE:

◦ For high availability and clustered environments that require multiple initiators to access thesame set of target ports, Hewlett Packard Enterprise recommends creating separate zonesfor each initiator with the same set of target ports.

◦ The storage targets in the zone can be from the same HPE 3PAR StoreServ Storage, multipleHPE 3PAR StoreServ Storage systems, or a mixture of HPE 3PAR and other HewlettPackard Enterprise storage systems.

For more information about using one initiator to multiple targets per zone, see the HPE SAN DesignReference Guide at the SPOCK website (SPOCK Home > Design Guides > SAN Design Guide).

When using an unsupported zoning configuration and an issue occurs, Hewlett Packard Enterprise mightrequire implementing one of the supported zoning configurations as part of the corrective action.

14 Setting up and zoning the fabric—FC

Verify the switch and zone configurations by using the HPE 3PAR CLI showhost command. Verify thateach initiator is zoned with the correct targets after completing the following tasks:

• Complete configuration of the storage port to the host and connect to the switch.• Create a zone configuration on the switch following the HPE SAN Design Reference Guide and enable

the zone set configuration.• Use the showhost command to verify that the host is seen on the storage node.

More Informationhttp://www.hpe.com/support/hpeschttp://www.hpe.com/storage/spock

HPE 3PAR Smart SAN—FCBeginning with HPE 3PAR OS 3.2.2, the following HPE 3PAR StoreServ Storage systems supportHPE 3PAR Smart SAN on 16 Gb FC targets:

• HPE 3PAR StoreServ 20000 Storage• HPE 3PAR StoreServ 10000 Storage• HPE 3PAR StoreServ 9000 Storage• HPE 3PAR StoreServ 8000 Storage• HPE 3PAR StoreServ 7000 Storage

HPE 3PAR Smart SAN through its TDPZ (target-driven peer zoning) feature enables customers toautomate peer zoning, which results in the creation of fewer zones and enables configuration of zones inminutes. Through automation, it reduces the probability of errors and potential downtime. WithoutHPE 3PAR Smart SAN, an administrator must preconfigure zones on the FC switch, before configuringhosts and VLUNs on the HPE 3PAR StoreServ Storage. With HPE 3PAR Smart SAN, the administratorcan configure and control zoning directly from the HPE 3PAR CLI.

Beginning with HPE 3PAR OS 3.3.1, HPE 3PAR Smart SAN 2.0 is supported. With HPE 3PAR SmartSAN 2.0, the target ports support device registration on the fabric using the FDMI (Fabric DeviceManagement Interface) Protocol. The switch CLI command can be used to display the FDMI datacontaining Target Port Management information. Additional Smart SAN HBA attributes are only registeredwith Smart SAN capable switches.

For information about supported FC switches and their firmware revisions with HPE 3PAR Smart SAN,see the SPOCK website.

For more information about HPE 3PAR Smart SAN for HPE 3PAR, including configuration, see theHPE 3PAR Smart SAN 2.0 User Guide at the Hewlett Packard Enterprise Information Library website.

HPE 3PAR coexistenceThe HPE 3PAR StoreServ Storage can coexist with other Hewlett Packard Enterprise storage systemarray families.

For supported Hewlett Packard Enterprise storage system combinations and rules, see the HPE SANDesign Reference Guide at the SPOCK website (SPOCK Home > Design Guides > SAN DesignGuide).


Configuration guidelines for switch vendors—FCUse the following FC switch vendor guidelines before configuring ports on fabrics to which the HPE 3PARStoreServ Storage connects.

HPE 3PAR Smart SAN—FC 15




• Brocade switch ports that connect to a host HBA port or to an HPE 3PAR StoreServ Storage port mustbe set to their default mode. On Brocade 3xxx switches running Brocade firmware 3.0.2 or later, verifythat each switch port is in the correct mode by using the Brocade telnet interface and theportcfgshow 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.

The following fill-word modes are supported on a Brocade 8 Gb switch running FOS firmware 6.3.1aand later:

admin>portcfgfillword

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

Hewlett Packard Enterprise recommends setting the fill word to mode 3 (aa-then-ia), which is thepreferred mode, by using the portcfgfillword command. If the fill word is not correctly set,er_bad_os counters (invalid ordered set) will increase when using the portstatsshow commandwhile connected to 8 Gb HBA ports, as they need the ARBFF-ARBFF fill word. Mode 3 will also workcorrectly for lower-speed HBAs, such as 4 Gb/2 Gb HBAs. For more information, see the Fabric OSCommand Reference Manual and the FOS release notes, at the Brocade website.

NOTE:

In addition, some Hewlett Packard Enterprise switches, such as the HPE SN8000B 8-slot SANbackbone director switch, the HPE SN8000B 4-slot SAN director switch, the HPE SN6000B 16Gb FC switch, or the HPE SN3000B 16 Gb FC switch automatically select the proper fill-wordmode 3 as the default setting.

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

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

• QLogic switch ports must be set to port type GL-port and port speed auto-detect. QLogic switch portsthat connect to the HPE 3PAR StoreServ Storage must be set to I/O Stream Guard disable or auto,but never enable.

More Informationhttp://www.brocade.com/en.html

Target port limits and specifications—FCTo avoid overwhelming a target port and to ensure continuous I/O operations, observe the followinglimitations on a target port:

16 Target port limits and specifications—FC

http://www.brocade.com/en.html

• Follow the instructions for setting the maximum number of initiator connections supported per arrayport, per array node pair, and per array as shown in the HPE 3PAR Support Matrix documentation atthe SPOCK website (SPOCK Home > Other Hardware > 3PAR).

• Maximum I/O queue depth per port on each HPE 3PAR StoreServ Storage HBA model, as follows:

HBA Protocol Array Bus Speed Ports Max. QueueDepth

EmulexLP11002

FC HPE F200,F400, T400,T800

PCI-X 4 Gbps 2 959

HPE 3PARFC044X

FC HPE F200,F400, T400,T800

PCI-X 4 Gbps 4 1638

EmulexLPe12002

FC HPE 3PARStoreServ

7000

PCIe 8 Gbps 2 3276

EmulexLPe12004


7000, 10000

PCIe 8 Gbps 4 3276

EmulexLPe16002


7000, 8000,10000

PCIe 16 Gbps 2 3072

EmulexLPe16004


8000, 20000

PCIe 16 Gbps 4 3072

• The I/O queues are shared among the connected host HBA ports on a first-come, first-served basis.• When all queues are in use and a host HBA port tries to initiate I/O, it receives a target queue full

response from the HPE 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 it cannotoverrun the HPE 3PAR StoreServ Storage port's queues when all hosts are delivering their maximumnumber of I/O requests.

NOTE:

◦ With HPE 3PAR OS 3.3.1 and later, HPE 3PAR has implemented Multi-Queue processing forthe 16 Gb FC target adapter. This action allows for balanced CPU utilization and improvesperformance.

◦ When host ports can access multiple targets on fabric zones, the target number assigned bythe host driver for each discovered target can change when the host is booted and sometargets are not present in the zone. This situation might change the device node access pointfor devices during a host restart. This issue can occur with any fabric-connected storage, andis not specific to the HPE 3PAR StoreServ Storage.

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


Performing preliminary 3PAR StoreServ Storage and host configuration 17


HPE 3PAR Priority Optimization—FCStarting with HPE 3PAR OS 3.1.2 MU2, the HPE 3PAR Priority Optimization feature was introduced.This feature is a more efficient and dynamic solution for managing server workloads and can be used asan alternative to setting host I/O throttles. When using this feature, a storage administrator is able toshare storage resources more effectively by enforcing quality-of-service limits on the array.

NOTE:

It has been noticed that Windows may offline the device/LUN if the bandwidth QoS rule on theVVset that the device/LUN belongs to is too aggressive. If this is the case, you need to decrease thebandwidth QoS rule.

No special settings are needed on the host side to obtain the benefit of HPE 3PAR Priority Optimization.However, certain per target or per-adapter throttle settings might need to be adjusted in rare cases.

For complete details of how to use HPE 3PAR Priority Optimization (Quality of Service) on HPE 3PARStoreServ Storage, see the HPE 3PAR Priority Optimization technical whitepaper.

More Informationhttp://www.hpe.com/info/3PAR-Priority-Optimization

HPE 3PAR Persistent Ports—FCThe HPE 3PAR Persistent Ports (or virtual ports) feature minimizes I/O disruption during a HPE 3PARStoreServ Storage online upgrade or node-down event. Port shutdown or reset events do not trigger thisfeature.

Each FC target storage array port has a partner array port automatically assigned by the system. Partnerports are assigned across array node pairs.

HPE 3PAR Persistent Ports allows a HPE 3PAR StoreServ Storage FC port to assume the identity of afailed port (WWN port) while retaining its own identity. Where a given physical port assumes the identity ofits partner port, the assumed port is designated as a persistent port. Array port failover and failback withHPE 3PAR Persistent Ports is transparent to most host-based multipathing software, which can keep allof its I/O paths active.

NOTE:

Use of HPE 3PAR Persistent Ports technology does not negate the need for properly installed,configured, and maintained host multipathing software.

For a more complete description of the HPE 3PAR Persistent Ports feature, its operation, and a completelist of required setup and connectivity guidelines, see the following documents:

• Technical whitepaper HPE 3PAR StoreServ Persistent Ports (Hewlett Packard Enterprise document#F4AA4-4545ENW) at the Hewlett Packard Enterprise Support Center website.

• HPE 3PAR Command Line Interface Administrator’s Manual in the "Using Persistent Ports forNondisruptive Online Software Upgrades" topic at the Hewlett Packard Enterprise Information Librarywebsite.

More Informationhttp://www.hpe.com/support/hpeschttp://www.hpe.com/info/storage/docs

HPE 3PAR Persistent Ports setup and connectivity guidelines—FCStarting with HPE 3PAR OS 3.1.2, the HPE 3PAR Persistent Ports feature is supported for FC targetports.

18 HPE 3PAR Priority Optimization—FC

http://www.hpe.com/info/3PAR-Priority-Optimization



Starting with HPE 3PAR OS 3.1.3, the HPE 3PAR Persistent Ports feature has additional functionality tominimize I/O disruption during an array port loss_sync event triggered by a loss of array portconnectivity to the fabric.

Follow the specific cabling setup and connectivity guidelines so that HPE 3PAR Persistent Ports functionproperly:

• HPE 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 for direct-

connect “loops”.)• Hewlett Packard Enterprise recommends that Dynamic FCID assignment on the fabric or switch where

the HPE 3PAR target ports are connected to is turned OFF/disabled. This will help the Host to resumeI/O faster when Persistent Ports failover/failback occurs. Refer to the switch manufacturerdocumentation for guidance how to turn OFF/disable "Dynamic FCID assignment".

• WWN zoning is required for Persistent Ports to work.

HPE 3PAR Express Writes—FCWith HPE 3PAR OS 3.2.x and later, the HPE 3PAR Express Writes feature is enabled by default with 8Gb FC target ports in Host HBA mode with bit Express Write.

The HPE 3PAR Express Writes feature optimizes the performance for small block random writes.HPE 3PAR StoreServ Storage handles Express Write based on the I/O size and does not require anychanges in the host driver or kernel parameters.

NOTE:

For HPE 3PAR StoreServ Storage systems with 16 Gb FC target ports, the HPE 3PAR ExpressWrites feature is not supported.

HPE 3PAR Express Writes—FC 19

Setting up a Windows Server 2003 andWindows Server 2003 3PAR StoreServStorage configuration—FC

NOTE:

Hewlett Packard Enterprise recommends using default values to configure your host unlessotherwise specified in the following procedures.

Checking the host for required driversYou can also use the Emulex One Command or QLogic QConvergeConsole software to verify support forHBA driver versions.More Informationhttp://www.hpe.com/storage/spock

Installing and configuring an Emulex HBA—FCFor HBA installation instructions, driver support and usage guidelines, see the Emulex installation andusage guide for each product type. If your configuration includes MPIO, check also for information aboutany required MPIO support driver.

NOTE:

For booting from the HPE 3PAR StoreServ Storage, configuring the BIOS is required.

Configuring the Emulex support driverAfter installing the driver, set HBA driver parameters; consult the HBA driver documentation for details.

To avoid overwhelming a target port and to ensure continuous I/O operations, observe the limitations on atarget port; see Target port limits and specifications—FC on page 16.

NOTE: When host ports can access multiple targets on fabric zones, the assigned target number(as assigned by the host driver) for each discovered target can change when the host is booted andsome targets are not present in the zone. This situation might change the device node access pointfor devices during a host restart. This issue can occur with any fabric-connected storage, and is notspecific to the HPE 3PAR StoreServ Storage.

If you run HPE 3PAR OS Online Upgrade, see the HPE 3PAR Upgrade Pre-Planning Guide in theReference section of the Hewlett Packard Enterprise Information Library website.


Checking Emulex HBA parameters and connection status

Procedure

1. Check the connection status using the Emulex One Command utility.2. Check the parameters.

20 Setting up a Windows Server 2003 and Windows Server 2003 3PAR StoreServ Storage configuration—FC



Installing and configuring a QLogic HBA—FCFor HBA installation instructions, driver support and usage guidelines, see the QLogic installation andusage guide for each product type. If your configuration includes MPIO, check also for information aboutany required MPIO support driver.

NOTE:

For booting from the HPE 3PAR StoreServ Storage, configuring the BIOS is required.

Configuring the QLogic support driverAfter installing the driver, set HBA driver parameters, such as maximum number of LUNs per target andthe Port Down Retry Count; consult the HBA driver documentation for details.

To avoid overwhelming a target port and to ensure continuous I/O operations, observe the limitations on atarget port; see Target port limits and specifications—FC on page 16.

NOTE:

• When host ports can access multiple targets on fabric zones, the target number assigned by thehost driver for each discovered target can change when the host is booted and some targets arenot present in the zone. This action may change the device node access point for devices duringa host restart. This issue can occur with any fabric-connected storage, and is not specific to theHPE 3PAR StoreServ Storage.

• If you perform a HPE 3PAR OS Rolling Upgrade, see the HPE 3PAR Operating System UpgradePlanning Guide at the Hewlett Packard Enterprise Information Library website.


Checking QLogic HBA parameters and connection statusUse the QLogic QConvergeConsole software to check connection status.

Installing the HPE 3PAR MPIO on the hostFor multipathing with Fibre Channel storage in a configuration with a Windows Server 2003 host, use onlythe 3PAR MPIO. The information in this section applies to either a new installation or to an existinginstallation where 3PAR StoreServ Storage virtual volumes already exist on the server.

NOTE:

• Do not use the 3PAR MPIO package in conjunction with Veritas Volume Manager or other third-party MPIO.

• It is important that only one path is made available to the host during the operating systeminstallation. Additional paths can be connected once the 3PAR driver for Microsoft Multipath I/Ois installed.

Procedure

1. To install the MPIO software, follow instructions in the HPE 3PAR Multipath for Microsoft WindowsUser’s Guide for (IA64, x64, x86).

2. Open the Windows Server 2003 Computer Management window; click Device Manager. See thefigure below.

Installing and configuring a QLogic HBA—FC 21


Figure 2: Verifying Device Connections3. In this window, check for multipath disk devices, which should be listed after the 3PAR MPIO software

is installed, as shown in the figure above.

The 3PAR MPIO software creates an active/active failover environment for 3PAR storage devices. Ifsettings other than the default active/active environment are desired, use the 3PAR MPIO software toconfigure or manage the MPIO environment.

Installing Veritas DMP multipathing on the WindowsServer 2003 host

If the configuration includes Veritas Storage Foundation software, configure it for use with the 3PARStoreServ Storage. Follow these steps:

Procedure

1. On the Windows Server 2003 host, open the Symantec Product Installer GUI.2. Click Veritas Storage Foundation for Windows (Server Components) and then select DMP Device

Specific Modules (DSMs).3. Select only 3PARDATA (V3PARAA) as your DMP device.

22 Installing Veritas DMP multipathing on the Windows Server 2003 host

For details about this software, see the Veritas Storage Foundation for Windows AdministrationGuide and the Veritas Storage Foundation & High Availability Solutions Installation & UpgradeGuide.

Disabling the write cache option for 3PAR LUNsHPE 3PAR virtual volumes/LUNs are written cache-enabled and, by design, cannot be turned off.

The Veritas Enterprise Administrator dialog box appears when you open Veritas EnterpriseAdministrator with the left tree on the GUI expanded.

Disabling the write cache option for 3PAR LUNs 23

You can ignore the message because the HPE 3PAR StoreServ Storage is a fault-tolerant redundantarray. Disabling the cache is not required. You can clear the message to prevent it from appearing everytime Veritas Enterprise Administrator starts.

24 Setting up a Windows Server 2003 and Windows Server 2003 3PAR StoreServ Storage configuration—FC

Setting up a Windows Server 2003 and 3PARStoreServ Storage configuration—iSCSI

NOTE:

• Hewlett Packard Enterprise recommends that you read the Microsoft iSCSI Software InitiatorUsers Guide for Windows-specific concepts and procedures discussed in this chapter.

• Hewlett Packard Enterprise recommends using default values to configure your host unlessotherwise specified in the following procedures.

Setting up the initiator and target ports—iSCSIConnect the host iSCSI initiator ports and the 3PAR StoreServ Storage iSCSI target ports to the switches.

Once the iSCSI initiator and 3PAR StoreServ Storage iSCSI target ports are configured and connected tothe switch, you can use the ping command on the iSCSI initiator host to make sure that it sees the 3PARStoreServ Storage iSCSI target ports.

The 3PAR StoreServ Storage arrays support the following VLAN configurations:

• One initiator to one target per VLAN• One initiator to multiple targets per VLAN• Multiple initiators to one target per VLAN• Multiple initiators to multiple targets per VLAN

You must be able to route the iSCSI traffic between the iSCSI initiator ports and the 3PAR StoreServStorage iSCSI target ports. Once the iSCSI initiator and 3PAR StoreServ Storage iSCSI target ports areconfigured and connected to the switch, you can use the ping command on the iSCSI initiator host tomake sure that it sees the 3PAR StoreServ Storage iSCSI target ports.

NOTE:

Switch VLAN configuration and routing setup and configuration are beyond the scope of thisdocument. See your switch manufacturer's guide for instructions about setting up VLANs androuting.

Configuring the 3PAR StoreServ Storage—iSCSIFollow these steps to set up the 3PAR StoreServ Storage for iSCSI storage:

IPv4 addressing for iSCSI:

Procedure

1. If the 3PAR StoreServ Storage iSCSI ports were not configured for iSCSI, use this command:

# controlport config iscsi -f N:S:P

2. Check the current iSCSI port settings: use the showport -iscsi command. The following exampleshows ports offline and unconfigured:

Setting up a Windows Server 2003 and 3PAR StoreServ Storage configuration—iSCSI 25

# showport -iscsi

N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port0:01:01 ready 10.0.0.122 255.0.0.0 0.0.0.0 11 1500 1Gbps 0 0.0.0.0 0.0.0.0 32050.01.02 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 32051.01.01 ready 10.0.0.222 255.0.0.0 0.0.0.0 111 1500 1Gbps 0 0.0.0.0 0.0.0.0 32051.01.02 offline 0.0.0.0 0.0.0.0 0.0.0.0 112 1500 n/a 0 0.0.0.0 0.0.0.0 3205

3. Use the controliscsiport addr to set the IP addresses and netmask addresses of the iSCSItarget ports:

# controliscsiport addr 10.101.1.31 255.255.0.0 -f 0:3:1

4. Verify the configuration; the following example shows two ports ready:

showport -iscsi

N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port0:01:01 ready 10.0.0.122 255.0.0.0 0.0.0.0 11 1500 1Gbps 0 10.0.0.60 0.0.0.0 32050:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 32051:01:01 ready 10.0.1.222 255.0.0.0 0.0.0.0 111 1500 1Gbps 0 10.0.0.60 0.0.0.0 32050:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 3205

5. Use the createhost -iscsi [options] <hostname> [<iscsi_name>...]:

For example, with all 3PAR OS versions:

# createhost -iscsi sqa-dl380g5-08 iqn.1991-05.com.microsoft:sqa-dl380g5-08

6. Check the newly set up host with the showhost command:

# showhost

Id Name Persona -------------WWN/iSCSI_Name-------------- Port1 sqa-dl380g5-08 Windows Server iqn.1991-05.com.microsoft:sqa-dl380g5-08 ---

26 Setting up a Windows Server 2003 and 3PAR StoreServ Storage configuration—iSCSI

Using the Microsoft iSNS server to discover registrationsUse the Microsoft iSNS server to discover the iSCSI initiator and iSCSI targets on the dedicated network.When the iSCSI initiator and iSCSI targets are registered with the iSNS server, they automatically startdiscovery of registered devices by querying the iSNS client/server via TCP/IP. A database of theseregistrations is updated.

Installing and using the iSNS server consists of these procedures, explained in separate topics:

• Installing the iSNS server• Using the iSNS server to discover registrations

Configuring the initiator and target for iSNS server usage—iSCSIFollow these steps:

Procedure

1. Use the showport -iscsi command to find out if the iSCSI target ports are configured for the iSNSserver:

# showport -iscsi

N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS Prim iSNS Sec iSNS Port0:01:01 ready 10.0.0.122 255.0.0.0 0.0.0.0 11 1500 1Gbps 0 0.0.0.0 0.0.0.0 32050:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 32051:01:01 ready 10.0.1.222 255.0.0.0 0.0.0.0 111 1500 1Gbps 0 0.0.0.0 0.0.0.0 32051:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 112 1500 n/a 0 0.0.0.0 0.0.0.0 3205

2. Set up the IP addresses for iSNS:

# controliscsiport isns 10.0.0.60 0:1:1# controliscsiport isns 10.0.0.60 1:1:1

3. Verify the configuration setting for iSNS:

# showport -iscsi

N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS Prim iSNS Sec iSNS Port0:01:01 ready 10.0.0.122 255.0.0.0 0.0.0.0 11 1500 1Gbps 0 10.0.0.60 0.0.0.0 32050:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 32051:01:01 ready 10.0.1.222 255.0.0.0 0.0.0.0 111 1500 1Gbps 0 10.0.0.60 0.0.0.0 32051:01:02 offline 0.0.0.0 0.0.0.0 0.0.0.0 112 1500 n/a 0 0.0.0.0 0.0.0.0 3205

Using the Microsoft iSNS server to discover registrations 27

NOTE: To configure an iSNS server that uses IPv6 addressing, issue the controliscsiportisns command as in the previous step, but instead of typing an IPv4 address, type the IPv6address of the iSNS server.

Establishing a connection with the iSCSI Initiator softwareThis section explains procedures for configuring Microsoft iSCSI Initiator software to establish aconnection. Follow these steps:

Procedure

1. Download the latest version of the iSCSI Initiator software from the Microsoft Download Center.2. Click the iSCSI Initiator icon; click the Discovery tab as shown in the figure below.

Figure 3: iSCSI Initiator Properties, Discovery tab3. In the Discovery window, click the Add button, as shown in the figure below.

28 Establishing a connection with the iSCSI Initiator software

Figure 4: Adding a Target4. In the Add Target Portal dialog box that appears, enter the IP address of the portal you want to add,

as shown in the figure below.

Figure 5: Specifying a Target Portal IP Address5. Establish the connection: click Advanced; the Advanced Settings dialog box appears, as shown in

the figure below.


Figure 6: Configuring a Target Portal Connection

In the Connect by using section of this dialog box, do the following:

• In the Local Adapter text field, select Microsoft iSCSI Initiator.• In the Source IP text field, select the IP address of the network interface card (NIC) adapter or

converged network adapter (CNA) that you want to use to connect to the iSCSI target.

The CRC/Checksum is not required.

Setting CHAP logon information is explained later in this chapter, in Configure host and target CHAPon page 34.

6. Click OK in the Advanced Settings dialog box and again in the Add Target Portal dialog box. TheDiscovery tab in the iSCSI Initiator Properties window displays the port information, as shown in thefigure below.


Figure 7: Target Portal Discovery7. Repeat step 2 through step 6 to connect additional target ports. Check the connections in the

Discovery tab in the iSCSI Initiator Properties window.

Establishing an iSCSI session and enabling multipathingTo establish an iSCSI logon session with a 3PAR StoreServ Storage iSCSI target port, follow these steps:

1. Click the Targets tab. Its window displays the names and status of the ports you have configured, asshown in the figure below.

Establishing an iSCSI session and enabling multipathing 31

Figure 8: Displaying Port Names and Status2. Click the Log On button to establish an iSCSI logon session with the 3PAR StoreServ Storage iSCSI

target port. The Log On to Target popup appears, as shown in the figure below.

Figure 9: Logging On to a Target3. Click the Enable multi-path checkbox to enable multipathing.

NOTE:

The Microsoft iSCSI Initiator multipathing default setting for discovering devices is Active/Passive. To change the setting to Active/Active, follow instructions in the iSCSI Initiatordocumentation.


4. If you wish to have the connection to the 3PAR StoreServ Storage target port automatically restoredwhen the system is restarted, click the checkbox for that option.

NOTE:

If you do not choose to automatically restore the connection at bootup time for this target port,you won't be able to select this option later for this port; instead, you will have to close the iSCSIconnection to the target port and reestablish the iSCSI target connection.

5. DO NOT click OK; instead click the Advanced... button. The Advanced Settings window thatappears, as shown in the figure below.

Figure 10: Specifying Connection Parameters

In this window, select the following in the Connect by using section:

NOTE: If you leave the default settings for theLocal adapterand Source IP options, theMicrosoft iSCSI Initiator will not work correctly, especially if you have multiple local adapters,source IP addresses, and target ports.

• Local adapter drop-down menu: Microsoft iSCSI Initiator• Source IP drop-down menu: IP address of the NIC adapter or CNA adapter in your system

that will connect to the iSCSI target port• Target Portal drop-down menu: IP address of the target portal (iSCSI target port).

6. Click OK in the Advanced Settings window and again in the Log On to Target window.


The iSCSI initiator will establish an iSCSI session with the target port.7. If desired, verify the connection: in the in the Targets section of the iSCSI Initiator Properties

window, the Status column for the target will show the status as Connected.8. Perform step 2 through step 7 to add the connection to the second target portal. The iSCSI Initiator

Properties window shows the status of both; see the figure below.

Figure 11: Verifying Connected Status for Both Targets

Configure host and target CHAPThis topic contains procedures for configuring the Challenge-Handshake Authentication Protocol (CHAP)and removing it, in separate topics:

1. Setting host CHAP on page 342. Setting target CHAP on page 373. Set mutual (bidirectional) CHAP on page 394. Removing CHAP on page 39

Setting host CHAPTo set a host CHAP secret, configure it on both the 3PAR StoreServ Storage and the Windows Server2003 host. Follow these steps:

34 Configure host and target CHAP

Procedure

1. Make sure that an iSCSI host definition was created on the 3PAR StoreServ Storage.2. Use the showhost -chap command to show that no CHAP secret is already set up. In the output,

host CHAP appears as Initiator_CHAP_Name:

# showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name

3. Use the sethost initichap <chap_name> <host_name> command to set initchap,<chap_name> must be at least 12 characters long.

# sethost initchap MyChapSecret sqa-dl380g5-08

Calling "sethost initchap" for host sqa-dl380g5-08. Continue?select q=quit y=yes n=no: y

4. Use the showhost -chap command to verify that initchap was created:

# showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name 0 sqa-dl380g5-08 sqa-dl380g5-08

5. In the iSCSI Initiator Properties window, click the Discovery tab; then click Add in the TargetPortals section.


6. In the Add Target Portal popup that appears, enter the IP address of the 3PAR StoreServ StorageiSCSI target port for which you want to establish an iSCSI connection as shown but do not click OK.

7. Click the Advanced... button. The Advanced Settings window appears.


Configure the following:

• Local Adapter drop-down menu: select Microsoft iSCSI Initiator.• Source IP drop-down menu: choose the IP address of your host NIC interface or CNA that will

connect to the iSCSI target port.• Click the CHAP login information check box to select it.• Target secret text box: enter the host CHAP secret that you configured in step 3 with the sethost

command.8. Click OK in the Advanced Settings window and then click OK in the Add Target Portal window.

Setting target CHAPTo set a target CHAP secret, configure it on both the 3PAR StoreServ Storage and the Windows Server2003 host by following these steps:

1. Issue showhost -chap to show that no CHAP secret is already set up.

# showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name-

2. To set a CHAP secret for a target, issue sethost targetchap -chapname <chapname> where<chapname> is the secret. For example:

Setting target CHAP 37

# sethost targetchap -f target_secret0 sqa-dl380g5-08

3. To check results, issue showhost -chap. For example:

# showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name 0 sqa-dl380g5-08 s055

4. In the iSCSI Initiator Properties window, click the Secret button.

5. In the CHAP Secret Setup popup that appears, enter the secret you have set for the host.


Set mutual (bidirectional) CHAP

Procedure

1. Set the host CHAP secret following instructions in Setting host CHAP on page 34.2. Set the target CHAP secret following instructions in Setting target CHAP on page 37.3. Issue showhost -chap. The output shows both secrets set:

# showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name 0 sqa-dl380g5-08 sqa-dl380g5-08 s055

Removing CHAPFollow these steps to remove CHAP from the 3PAR StoreServ Storage hosts:

1. Issue sethost removechap; this command removes all CHAP information for all specified hosts.For example:

# sethost removechap sqa-dl380g5-0Calling "sethost removechap" for host sqa-dl380g5-08. Continue?select q=quit y=yes n=no: y

2. To check status, issue showhost -chap. For example:

# showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name-0 sqa-dl380g5-08 --

3. In the iSCSI Initiator, click Persistent Targets.4. Click the Details button; in the window that appears, highlight the target and click the Remove button.5. Log off the target by selecting the target and clicking the Log off ... button.

6. Remove the target: click the Discovery tab, highlight the target, and click the Remove button.

Set mutual (bidirectional) CHAP 39

7. Repeat these steps for each port.

Target port limits and specifications—iSCSITo avoid overwhelming a target port and ensure continuous I/O operations, observe the followinglimitations on a target port:

• Follow the instructions for setting the maximum number of initiator connections supported per arrayport, per array node pair, and per array as shown in the HPE 3PAR Support Matrix documentation atthe SPOCK website (SPOCK Home > Other Hardware > 3PAR).

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

HBA Protocol Array Bus Speed Ports Max. QueueDepth

QLogicQLA4052C

iSCSI F200, F400,T400, T800

PCI-X 1 Gbps 2 512

QLogicQLE8242

iSCSI HPE 3PARStoreServ

7000, 10000

PCIe 10 Gbps 2 2048

• The I/O queues are shared among the connected host server 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 queue fullresponse from the 3PAR StoreServ Storage port. This condition can result in erratic I/O performanceon each host server. If this condition occurs, each host server should be throttled so that it cannotoverrun the 3PAR StoreServ Storage port's queues when all host servers are delivering theirmaximum number of I/O requests.

HPE 3PAR Persistent Ports—iSCSIBeginning with 3PAR OS 3.1.3, the 3PAR Persistent Ports feature is supported for iSCSI.

40 Target port limits and specifications—iSCSI

The HPE 3PAR Persistent Ports (or virtual ports) feature minimizes I/O disruption on a 3PAR StoreServStorage in response to the following events:

• 3PAR OS firmware upgrade• Node maintenance that requires the node to be taken offline (e.g., adding a new HBA)• 3PAR node failure• Array target ports being taken offline administratively

Each iSCSI target storage array port has a partner array port automatically assigned by the system.Partner ports are assigned across array node pairs.

HPE 3PAR Persistent Ports allows a 3PAR StoreServ Storage iSCSI port to assume the identity of afailed port (IP address) while retaining its own identity. Where a given physical port assumes the identityof its partner port, the assumed port is designated as a persistent port. Array port failover and failbackwith HPE 3PAR Persistent Ports is transparent to most host-based multipathing software, which can keepall of its I/O paths active.

NOTE:

• Use of 3PAR Persistent Ports technology does not negate the need for properly installed,configured, and maintained host multipathing software.

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

For a more complete description of the 3PAR Persistent Ports feature, its operation, and a complete list ofrequired setup and connectivity guidelines, see the following documents:

• Technical white paper HPE 3PAR StoreServ Persistent Ports (Hewlett Packard Enterprise document#F4AA4-4545ENW) at the Hewlett Packard Enterprise Support Center website.

• HPE 3PAR Command Line Interface Administrator’s Manual in the "Using Persistent Ports forNondisruptive Online Software Upgrades" topic at the Hewlett Packard Enterprise Storage InformationLibrary website.

HPE 3PAR Persistent Ports setup and connectivity guidelines—FCStarting with HPE 3PAR OS 3.1.2, the HPE 3PAR Persistent Ports feature is supported for FC targetports.

Starting with HPE 3PAR OS 3.1.3, the HPE 3PAR Persistent Ports feature has additional functionality tominimize I/O disruption during an array port loss_sync event triggered by a loss of array portconnectivity to the fabric.

Follow the specific cabling setup and connectivity guidelines so that HPE 3PAR Persistent Ports functionproperly:

• HPE 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 for direct-

connect “loops”.)• Hewlett Packard Enterprise recommends that Dynamic FCID assignment on the fabric or switch where

the HPE 3PAR target ports are connected to is turned OFF/disabled. This will help the Host to resumeI/O faster when Persistent Ports failover/failback occurs. Refer to the switch manufacturerdocumentation for guidance how to turn OFF/disable "Dynamic FCID assignment".

• WWN zoning is required for Persistent Ports to work.

HPE 3PAR Persistent Ports setup and connectivity guidelines—FC 41

Allocating storage for the Windows Server2003 hostCreating storage on the HPE 3PAR StoreServ Storage

The following topics describe the general procedures and commands that are required to create thevirtual volumes (VVs) that can then be exported for discovery by the host.

For additional information, see the HPE 3PAR Command Line Interface Administrator’s Manual. For acomprehensive description of HPE 3PAR OS commands, see the HPE 3PAR Command Line InterfaceReference at the Hewlett Packard Enterprise Information Library Storage website.

Create virtual volumesVirtual volumes are the only data layer visible to hosts. After devising a plan for allocating space for theWindows host, create the VVs on the HPE 3PAR StoreServ Storage.

Create volumes that are provisioned from one or more Common Provisioning Groups (CPGs). Volumescan be either fully provisioned, thinly provisioned, or thinly deduplicated, or thinly compressed volumes.Optionally, specify a CPG for snapshot space for provisioned volumes.

For complete details on creating volumes for the HPE 3PAR OS version that is being used on the HPE3PAR StoreServ Storage, see the following documents:

• HPE 3PAR StoreServ Management Console User Guide• HPE 3PAR Management Console User Guide• HPE 3PAR OS Command Line Interface Reference

These documents are available at the Hewlett Packard Enterprise Information Library website.

NOTE:

The commands and options available for creating a VV might vary for earlier versions of the HPE3PAR OS.

Create VVs using the HPE 3PAR Management Console (MC)

Procedure

1. From the menu bar, select:

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

a. Fully Provisionedb. Thinly Provisionedc. Thinly Deduplicated (Supported with HPE 3PAR OS 3.2.1 MU1 and later)

Create VVs using the HPE 3PAR StoreServ Management Console (SSMC)

1. On the main menu, select:

Block Persona > Virtual Volume2. Click + Create virtual volume or select Create on the Actions menu.3. Follow the instructions on the dialog that opens and select one of the following virtual volume options:

42 Allocating storage for the Windows Server 2003 host

• Fully Provisioned• Thinly Provisioned• Thinly Deduplicated (Supported with HPE 3PAR OS 3.2.1 MU1 and later)• Thinly Compressed (Supported with 3PAR OS 3.3.1 and later)

Create VVs using the HPE 3PAR CLI

Create a fully provisioned or TPVV:

cli % createvv [options] <usr_CPG> <VV_name> [.<index>] <size>[g|G|t|T]

For example:

cli % createvv -cnt 5 testcpg TESTLUNS 5g


Creating thinly provisioned virtual volumes

IMPORTANT:

To create TPVVs, an HPE 3PAR Thin Provisioning license is required.

To create thinly provisioned virtual volumes (TPVVs), see the following documents:

• HPE 3PAR StoreServ Storage Concepts Guide• HPE 3PAR Command Line Interface Administrator’s Manual• HPE 3PAR OS Command Line Interface Reference

These documents are available at the Hewlett Packard Enterprise Information Library Storage website.


Creating thinly deduplicated virtual volumes

NOTE:

• With HPE 3PAR OS 3.3.1 and later, HPE 3PAR introduced a new all-inclusive licensing model forsoftware. Please refer to the HPE 3PAR StoreServ Storage Concepts Guide for moreinformation.

• With HPE 3PAR OS 3.2.1 MU1 and later, the HPE 3PAR Thin Deduplication feature issupported. To create thinly deduplicated virtual volumes (TDVVs), an HPE 3PAR ThinProvisioning license is required.

HPE 3PAR Thin Deduplication allows the creation of TDVVs from solid-state drive (SSD) commonprovisioning groups (CPGs). A TDVV has the same characteristics as a TPVV, with the additionalcapability of removing duplicated data before it is written to the volume. The TDVVs are managed like anyother TPVV. A TDVV must be associated with CPGs created from an SSD.

For more information about HPE 3PAR Thin Deduplication and Compression, see the followingdocuments:

Creating thinly provisioned virtual volumes 43



• HPE 3PAR StoreServ Storage Concepts Guide• HPE 3PAR Command Line Interface Administrator’s Manual• HPE 3PAR OS Command Line Interface Reference• HPE 3PAR Thin Technologies—Technical white paper containing best practices

These documents are available at the Hewlett Packard Enterprise Storage Information Library website.

Creating thinly compressed virtual volumes

NOTE:

With HPE 3PAR OS 3.3.1 and later, HPE 3PAR compressed virtual volumes are supported. Tocreate compressed volumes, an HPE 3PAR All-Inclusive Software License is required.

HPE 3PAR Thin Compression allows the creation of compressed virtual volumes from solid-state drive(SSD) common provisioning groups (CPGs). The compression feature is available on thinly provisioned(TPVV) and thinly deduplicated virtual volumes (TDVV). Virtual volumes can be marked for compressionduring their creation, or an existing virtual volume can be updated with the compression feature at runtime.

Exporting VLUNs to the hostFollow the instructions for creating virtual volumes (VVs) and virtual LUNs (VLUNs) in the 3PAR OS CLIAdministrator’s Guide.

Note the following guidelines:

• Sparse LUNs are supported (you can skip LUN IDs).• You can export LUNs in non-ascending order (for example, 0, 5, 7, 3).• The Windows Server 2003 system registers only LUNs 0 to 254.• The maximum number of usable LUNs per host port is 255. Although the 3PAR StoreServ Storage can

export LUNs 0 to 65535, only LUNs 0 to 254 should be used for Windows configurations.• With 3PAR OS 3.1.1 or later, the maximum LUN size supported by the Windows Server 2003 host is

16 TB.• Windows Server 2003 SP1 and higher support LUN size of 16 TB; some older versions of Windows

will not support an hdisk greater than 2 TB.

Restrictions on volume size and numberFollow the guidelines for creating virtual volumes (VVs) and virtual logical unit numbers (VLUNs) in theHPE 3PAR Command Line Interface Administrator's Manual while adhering to these cautions andguidelines:

• Beginning with HPE 3PAR OS 3.3.1 the maximum volume size has changed. Please refer to the HPE3PAR StoreServ Storage Concepts Guide and the HPE 3PAR OS 3.3.1 Release Notes for details.

• This configuration supports sparse LUNs (meaning that LUNs might be skipped). LUNs might also beexported in non-ascending order (such as 0, 5, 7, 3).

• The HPE 3PAR StoreServ Storage supports the exportation of VLUNs with LUNs in the range from 0to 16383.

• The maximum LUN size that can be exported to a host is 16 TB when the installed HPE 3PAR OSversion is 3.2.x or 3.1.x. A LUN size of 16 TB on a host is dependent on the installed version andupdate, since some older versions will not support a volume greater than 2 TB.

Discovering LUNsUse the Computer Management utility to display formation on the disks in the device.

44 Creating thinly compressed virtual volumes

Scanning for new devices on a Windows Server 2003 hostDisk devices on Windows servers can be used as basic disks or dynamic disks. The 3PAR StoreServStorage already provides most of the extra capabilities of dynamic disks. Hewlett PackardEnterprise strongly recommends that 3PAR StoreServ Storage volumes be used only as basic disksunless any of the additional features of dynamic disks are a requirement.

NOTE:

If dynamic disks are used, data corruption can occur if duplicate copies of the same volume areever concurrently exposed to a server. If you need duplicate copies, use the 3PAR StoreServStorage Virtual Copy feature, or break a Windows mirrored set of disks created on two discrete3PAR StoreServ Storage volumes.

For complete information on using dynamic disks, including special cautions for using dynamic diskson SAN-attached storage, see the Microsoft publicationBest Practices for Using Dynamic Disks onWindows Server 2003 Based-Computers, available at the following website:http://support.microsoft.com/kb/816307

When VLUNs are exported to the Windows Server 2003 server, they might not appear in the WindowsDisk Manager automatically. After a new VLUN is exported from a 3PAR StoreServ Storage iSCSI port,issue a re-scan from Windows Disk Manager or Windows Device Manager.

To scan for new devices on the Windows Server 2003 host, follow these steps:

Scanning for new devices on a Windows Server 2003 host 45

http://support.microsoft.com/kb/816307

http://support.microsoft.com/kb/816307

Procedure

1. In the Windows Computer Management window, click Device Manager.2. Right-click the machine name or right-click a particular device, and in the popup that appears, select

Scan for hardware changes. For example with a disk device selected:

Removing a storage volume from the hostTo remove a volume from the Windows Server 2003 host, follow standard Microsoft administrativeprocedures for removing a volume, and follow the 3PAR StoreServ Storage standard procedure toremove a volume.

NOTE: Removing a disk from an Windows Server 2003 host does not erase the data on the disk. Ifthere is concern about the data on the disk, consider using a third party utility that erases the dataon the disk before removing it from the Windows Server 2003 host.

46 Removing a storage volume from the host

Booting from the 3PAR StoreServ StorageFor details about connecting the 3PAR StoreServ Storage to the host, see Performing preliminary3PAR StoreServ Storage and host configuration on page 8.

Configuring for iSCSI SAN bootFor configurations that have iSCSI connections, the following are required:

• Double-Take Flex software• DHCP server• PXE server

See the latest version of the Double-Take Flex User’s Guide for full instructions.

NOTE:

The rest of this chapter consists of instructions for configuring for a 3PAR StoreServ Storage bootwith FC storage.

Configuring the BIOS for FC SAN bootThis topic explains specific host HBA settings required for booting from a 3PAR StoreServ Storage in afabric configuration. Use the Boot BIOS version listed on the SPOCK website:


To obtain a copy of this documentation, go to the following page of the Hewlett PackardEnterprise Support Center website:


NOTE: With the introduction of the Microsoft Storport driver, booting from a Storage Area Network(SAN) has become less problematic. For instructions on making the appropriate registry changes,see the Microsoft document titled How to add a registry value to a Windows Server 2003-basedcomputer that you start from a SAN so that the startup disk, the pagefile disks, and the cluster disksare all on the same SAN fabric. At the time this document was published, he Microsoft documentcould be located at the following website:http://support.microsoft.com/default.aspx?scid=kb;en-us;886569

See also to the Microsoft document Boot from SAN in Windows Server™ 2003 and Windows® 2000Server.

Configuring for a 3PAR StoreServ Storage boot—Emulex HBATo configure the Emulex HBA, complete the following procedure:

1. Boot the Windows Server 2003 system following the instructions in the BootBios update manual.2. Press Alt+E. For each Emulex adapter, set the following parameters:

• Select Configure the Adapter's Parameters.• Select Enable or Disable the BIOS; for SAN boot, ensure that the BIOS is enabled.• Press Esc to return to the previous menu.• Select Auto Scan Setting; set the parameter to First LUN 0 Device; press Esc to return to the

previous menu.• Select Topology.

Booting from the 3PAR StoreServ Storage 47



http://support.microsoft.com/default.aspx?scid=kb;en-us;886569

http://support.microsoft.com/default.aspx?scid=kb;en-us;886569

◦ Select Fabric Point to Point for fabric configurations.◦ Select FC-AL for direct connect configurations.

3. Press Esc to return to the previous menu if you need to set up other adapters. When you are finished,press x to exit and restart.

Configuring for a 3PAR StoreServ Storage boot—QLogic HBAUse the QLogic HBA Fast!UTIL utility to configure the HBA. Follow these steps:

1. Boot the Windows Server 2003 server; as the server is booting, press the Alt+Q or Ctrl+Q keys whenthe HBA BIOS prompts appear.

2. In the Fast!UTIL utility, click Select Host Adapter and then select the appropriate adapter.3. Click Configuration Settings > Adapter Settings.4. In the Adapter Settings window, set the following:

• Host Adapter BIOS: Enabled• Spinup Delay: Disabled• Connection Option:

◦ 0 for direct connect◦ 1 for fabric

NOTE:

Record the Adapter Port Name WWPN for creating the host definition as explained later inthis chapter.

5. Press Esc to exit this window.6. Click Selectable Boot Settings. In the Selectable Boot Settings window, set Selectable Boot

Device to Disabled.7. Press Esc twice to exit; when you are asked whether to save NVRAM settings, click Yes.8. Exit Fast!UTIL.

Creating the host definition for a 3PAR StoreServ Storageboot—FC

To create the host definition for booting from the 3PAR StoreServ Storage, use the createhost -persona 2 <hostname> [<WWN>...] command. For example:

# createhost -persona 2 windowshost 10000000C9606724

To verify that the host is created, use the showhost command.

% showhost

Id Name Persona -------------WWN/iSCSI_Name------------- Port 0 windowshost Generic-ALUA 10000000C9606724 ---

48 Configuring for a 3PAR StoreServ Storage boot—QLogic HBA

Connecting the 3PAR StoreServ Storage to the host—FCFor FC HBAs in a Windows Server 2003 host, you do not need to set any parameters for SAN boot otherthan those set in Installing and configuring an Emulex HBA—FC on page 20 and Installing andconfiguring a QLogic HBA—FC on page 21.

Assigning LUNs as the boot volumeThe Windows Server 2003 server must use a LUN specified as 0 as boot volume for an FC SAN boot. Tocreate LUN 0 and assign it as the boot volume, follow these steps:

1. On the 3PAR StoreServ Storage, create a VV of appropriate size.2. Export it to the Windows Server 2003 host and specify it as 0. For details, see Exporting VLUNs to

the host.3. Restrict the host to a single path connection to the 3PAR StoreServ Storage. Only a single path should

be available on the 3PAR StoreServ Storage and a single path on the host to the VLUN that will be theboot volume.

Installing the host OS onto the FC boot volumeThe 3PAR StoreServ Storage supports Windows Server 2003 host boot. You can install the WindowsServer 2003 OS to boot from the 3PAR StoreServ Storage. Follow all recommended settings and guides.

To install the Windows Server 2003 OS on 3PAR StoreServ Storage volumes, follow these steps:

NOTE:

Once 3PAR MPIO 1.0.22 for Windows Server 2003 has been installed, it cannot be uninstalled for ahost boot disk.

1. Make sure that the connection between the 3PAR StoreServ Storage and the Windows Server 2003host system is a single-path connection.

2. Follow standard procedures in the Microsoft documentation for installing the OS on a bootable device.

For details, see Boot from SAN in Windows Server™ 2003 and Windows® Server, available fromMicrosoft Corporation.

3. Restart the Windows Server 2003 system. The 3PAR StoreServ Storage volume is configured with theWindows Server 2003 OS.

4. If you have not already done so, install 3PAR MPIO 1.0.22 for Windows Server 2003 as explained in Installing the HPE 3PAR MPIO on the host.

Connecting multiple paths for FC SAN bootAfter the Windows Server 2003 host completely boots up and is online, connect additional paths to thefabric or the 3PAR disk storage system directly by completing the following tasks.

1. On the 3PAR StoreServ Storage, issue createhost -add <hostname> <WWN> to add theadditional paths to the defined 3PAR StoreServ Storage host definition.

2. On the Windows Server 2003 host, re-scan for devices; see Scanning for new devices on aWindows Server 2003 host.

3. Restart the Windows Server 2003 system.

Connecting the 3PAR StoreServ Storage to the host—FC 49

HPE 3PAR All Flash ArrayStarting with HPE 3PAR OS 3.2.1, HPE 3PAR introduced All-Flash-Arrays that deliver significantimprovements in performance, density, resiliency and data mobility.

Applications like OLTP, VDI, business analytics and various other data services are taking advantage ofthe improvements that these HPE 3PAR All-Flash-Arrays offer. To benefit from these improvements, noarray special settings are needed.

For more information on HPE 3PAR All-Flash-Arrays see the white paper HPE 3PAR StoreServ:Optimized for Flash available at the Hewlett Packard Enterprise Storage Information Library website.

NOTE:

For volumes on All-Flash-Arrays, executing a utility or command which defragments or attempts tooptimize data placement should be avoided. Such actions unnecessarily contributes to SSD devicewear. Unlike spinning media, an SSD device inherently has no rotational latency and, therefore,defragmentation or optimization provides no benefit. As to whether data management commandsrecognize SSD devices, consult the documentation or the vendor for your host OS and adjust theirbehavior accordingly.

50 HPE 3PAR All Flash Array

Configuring File PersonaHPE 3PAR File Persona

Starting with HPE 3PAR OS 3.2.1 MU2, the HPE 3PAR File Persona software is available. TheHPE 3PAR File Persona software provides file services and access to file storage by network protocolssuch as:

• Server Message Block (SMB)• Network file system (NFS)• Web Distributed Authoring and Versioning (WebDAV)

For information on supported HPE 3PAR StoreServ Storage models and client configurations, see theSPOCK website: SPOCK Home > Explore Storage Interoperability With SPOCK > Explore 3PARStoreServ Storage interoperability > Explore 3PAR File Persona interoperability.

For a complete description of the HPE 3PAR File Persona software, including required setup andguidelines, see the HPE 3PAR File Persona User Guide available at the Hewlett Packard EnterpriseInformation Library Storage website.

More Informationhttp://www.hpe.com/storage/spockhttp://www.hpe.com/info/storage/docs

Configuring File Persona 51



Using the Veritas Cluster ServerSymantec Storage Foundation

Symantec Storage Foundation (SF) 5.1 SP1 and SP2 have a space-reclamation feature to reclaim spacefrom a thinly-provisioned virtual volume. When working with an MS-Cluster and VxDMP, this feature is notsupported, as an MS-Cluster requires basic disks, and the space reclamation feature is available only ondynamic disks (the Veritas DMP I/O policy setting is "Round Robin").

Installing the Veritas Cluster ServerThe HPE 3PAR StoreServ Storage supports use with Veritas Cluster Server and there are no specialsetup considerations for the HPE 3PAR StoreServ Storage. For installation and setup instructions, seethe Veritas Cluster Server Installation Guide and the Veritas Cluster Server User's Guide.

Setting SCSI-3 Persistent Reservation support for the3PAR StoreServ Storage

For Veritas Cluster Server (VCS) V5.1 and later, you can enable or disable the SCSI 3 support. Followthese steps:

1. Download the latest device driver installation (DDI) package (DDI-2.1). See, https://www.veritas.com/support/en_US/article.TECH71253.

2. Save the DDI to a folder.

3. Extract the DDI files.4. Verify the 3PAR enable/disable script:

DisableSupportSCSI3V3paraa & EnableSupportSCSI3V3paraa

5. By default, the 3PAR Support for SCSI 3 appears as 0x00000000 (0) in the Data column. Toconfirm, click Start, click Run, and then click regedit > Computer > HKEY_LOCAL_MACHINE >SYSTEM > CurrentControlSet > Services > v3paraa > Parameters

52 Using the Veritas Cluster Server

https://www.veritas.com/support/en_US/article.TECH71253

https://www.veritas.com/support/en_US/article.TECH71253

6. To enable 3PAR SCSI-3 support, click the EnableSupportSCSI3V3paraa script, and then restart theserver after the script runs.

7. After the script runs, the 3PAR Support SCSI-3 appears as 0x00000000 (1) in the Data column.8. Open the Veritas Enterprise Administrator (VEA) to verify the new settings.

Using the Veritas Cluster Server 53

54 Using the Veritas Cluster Server

Using Microsoft Clustering with Veritas DMPThe 3PAR StoreServ Storage supports Microsoft Cluster with Veritas DMP (the Veritas DMP I/O policysetting is "Round Robin"). Follow Microsoft recommendations when setting up the cluster, as well asSymantec recommendations when setting up DMP to support Microsoft clustering. See the followingSymantec website: http://seer.entsupport.symantec.com/docs/306319.htm.

Installing the Veritas DMPCAUTION:In Windows Server 2003 R2 SP1 installations, Veritas Storage Foundation 5.1 & Veritas StorageFoundation HA 5.1 require the use of 8-byte long WWNs on every virtual volume exported from a3PAR StoreServ Storage array to the Windows Server host. Using 16-byte long WWN's instead withthe above Veritas Storage Foundation version may prevent the Veritas Storage Foundation softwarefrom recognizing 3PAR disks properly.

To verify the length of the WWN currently assigned to a virtual volume, issue the following command:

# showvv -d

The following example illustrates how both types of WWNs appear in the command's output. Please notethat testvv1 has a 16-byte WWN assigned against it whereas testvv2 has an 8-byte long WWN.

# showvv -d

Id Name Rd Mstr Prnt Roch Rwch PPrnt PBlkRemain ------------ VV_WWN------------- -----CreationTime------1 .srdata RW 1/0/- --- --- --- --- -- 60002AC00000000000000001000185E4 2012-08-17 09:44:48 PDT0 admin RW 1/0/- --- --- --- --- -- 60002AC00000000000000000000185E4 2012-08-17 09:41:04 PDT998 testvv1 RW 1/0/- --- --- --- --- -- 60002AC00000000000000382000185E4 2013-06-03 01:23:13 PDT999 testvv2 RW 1/0/- --- --- --- --- -- 50002AC003E885E4 2013-06-03 01:22:20 PDT

The WWN of a virtual volume cannot be changed during export. The change must be performed beforethe virtual volume is exported or after all its associated VLUNs are removed. To change the WWN of avirtual volume, issue the following command:

# setvv -wwn <new wwn> <vv name>

For example:

# setvv -wwn 50002AC003D885E4 testvv1

Using Microsoft Clustering with Veritas DMP 55

http://seer.entsupport.symantec.com/docs/306319.htm

The command assumes that 50002AC003D885E4 is the newly assigned WWN and testvv is the name ofthe virtual volume for which the WWN is being changed. To verify that the WWN change has taken place,use the showvv -d command and carefully review the output.

When installing Veritas DMP, be sure that 3PARDATA (VA3PARAA) is checked.

Setting SCSI-3 Persistent Reservation support for the3PAR StoreServ StorageProcedure

1. Download the latest device driver installation (DDI) package (DDI–2.1) at the Symantec website:http://www.symantec.com/business/support/index?page=content&id=TECH71253.

2. Save the DDI to a folder. See the figure below.

Figure 12: Saving the DDI to a Folder3. Extract the DDI files.4. Verify the 3PAR enable/disable script:

56 Setting SCSI-3 Persistent Reservation support for the 3PAR StoreServ Storage

http://www.symantec.com/business/support/index?page=content&id=TECH71253

http://www.symantec.com/business/support/index?page=content&id=TECH71253

DisableSupportSCSI3V3paraa & EnableSupportSCSI3V3paraa

5. By default, the 3PAR support for SCSI-3 appears as 0x00000000 (0) in the Data column. Toconfirm, click Start, click Run, and then click:

regedit > Computer > Hkey_LOCAL_MACHINE > CurrentControlSet > Services\v3paraa\Parameters. See the figure below.

Figure 13: V3PARAA Parameters6. To enable 3PAR SCSI-3 support, click the EnableSupportSCSI3V3paraa script (See the figure

below), then restart the server after the script runs.

Figure 14: Enabling Script Support7. After the script runs, the 3PAR support SCSI-3 appears as 0x00000000 (1) in the Data column.

8. Open the Veritas Enterprise Administrator (VEA) to verify the new settings (See the figure below).

Using Microsoft Clustering with Veritas DMP 57

Figure 15: Veritas Enterprise Administrator

58 Using Microsoft Clustering with Veritas DMP

Using the HPE PolyServe Matrix ServerThe 3PAR StoreServ Storage supports use with the PolyServe Matrix Server. See the HPE PolyServeMatrix Server Installation Guide for installation and configuration instructions.

Other than installation and configuration of 3PAR MPIO, there are no special setup considerations for the3PAR StoreServ Storage array. For installation of the 3PAR MPIO, see the HPE 3PAR Multipath I/O1.0.22 for Microsoft Windows User’s Guide for (IA64, x64, x86).

Using the HPE PolyServe Matrix Server 59

WebsitesGeneral websites

Hewlett Packard Enterprise Information Librarywww.hpe.com/info/EIL

Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrixwww.hpe.com/storage/spock

Storage white papers and analyst reportswww.hpe.com/storage/whitepapers

For additional websites, see Support and other resources.

60 Websites

http://www.hpe.com/info/EIL


http://www.hpe.com/storage/whitepapers

Support and other resources

Accessing Hewlett Packard Enterprise Support• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:

http://www.hpe.com/assistance• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center

website:


Information to collect

• Technical support registration number (if applicable)• Product name, model or version, and serial number• Operating system name and version• Firmware version• Error messages• Product-specific reports and logs• Add-on products or components• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the product

interface. Review your product documentation to identify the recommended software update method.• To download product updates:

Hewlett Packard Enterprise Support Centerwww.hpe.com/support/hpesc

Hewlett Packard Enterprise Support Center: Software downloadswww.hpe.com/support/downloads

Software Depotwww.hpe.com/support/softwaredepot

• To subscribe to eNewsletters and alerts:

www.hpe.com/support/e-updates• To view and update your entitlements, and to link your contracts and warranties with your profile, go to

the Hewlett Packard Enterprise Support Center More Information on Access to Support Materialspage:

www.hpe.com/support/AccessToSupportMaterials

IMPORTANT:

Access to some updates might require product entitlement when accessed through the HewlettPackard Enterprise Support Center. You must have an HPE Passport set up with relevantentitlements.

Support and other resources 61

http://www.hpe.com/assistance



http://www.hpe.com/support/downloads


http://www.hpe.com/support/e-updates

http://www.hpe.com/support/AccessToSupportMaterials

Customer self repairHewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If aCSR part needs to be replaced, it will be shipped directly to you so that you can install it at yourconvenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized serviceprovider will determine whether a repair can be accomplished by CSR.

For more information about CSR, contact your local service provider or go to the CSR website:

http://www.hpe.com/support/selfrepair

Remote supportRemote support is available with supported devices as part of your warranty or contractual supportagreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware eventnotifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on yourproduct's service level. Hewlett Packard Enterprise strongly recommends that you register your device forremote support.

If your product includes additional remote support details, use search to locate that information.

Remote support and Proactive Care informationHPE Get Connected

www.hpe.com/services/getconnectedHPE Proactive Care services

www.hpe.com/services/proactivecareHPE Proactive Care service: Supported products list

www.hpe.com/services/proactivecaresupportedproductsHPE Proactive Care advanced service: Supported products list

www.hpe.com/services/proactivecareadvancedsupportedproducts

Proactive Care customer informationProactive Care central

www.hpe.com/services/proactivecarecentralProactive Care service activation

www.hpe.com/services/proactivecarecentralgetstarted

Warranty informationTo view the warranty for your product or to view the Safety and Compliance Information for Server,Storage, Power, Networking, and Rack Products reference document, go to the Enterprise Safety andCompliance website:

www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional warranty informationHPE ProLiant and x86 Servers and Options

www.hpe.com/support/ProLiantServers-WarrantiesHPE Enterprise Servers

www.hpe.com/support/EnterpriseServers-WarrantiesHPE Storage Products

www.hpe.com/support/Storage-Warranties

62 Customer self repair

http://www.hpe.com/support/selfrepair

http://www.hpe.com/services/getconnected

http://www.hpe.com/services/proactivecare

http://www.hpe.com/services/proactivecaresupportedproducts

http://www.hpe.com/services/proactivecareadvancedsupportedproducts

http://www.hpe.com/services/proactivecarecentral

http://www.hpe.com/services/proactivecarecentralgetstarted

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

http://www.hpe.com/support/ProLiantServers-Warranties

http://www.hpe.com/support/EnterpriseServers-Warranties

http://www.hpe.com/support/Storage-Warranties

HPE Networking Productswww.hpe.com/support/Networking-Warranties

Regulatory informationTo view the regulatory information for your product, view the Safety and Compliance Information forServer, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard EnterpriseSupport Center:

www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemicalsubstances in our products as needed to comply with legal requirements such as REACH (Regulation ECNo 1907/2006 of the European Parliament and the Council). A chemical information report for this productcan be found at:

www.hpe.com/info/reach

For Hewlett Packard Enterprise product environmental and safety information and compliance data,including RoHS and REACH, see:

www.hpe.com/info/ecodata

For Hewlett Packard Enterprise environmental information, including company programs, productrecycling, and energy efficiency, see:

www.hpe.com/info/environment

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. To help usimprove the documentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). When submitting your feedback, include the document title, part number,edition, and publication date located on the front cover of the document. For online help content, includethe product name, product version, help edition, and publication date located on the legal notices page.

Regulatory information 63

http://www.hpe.com/support/Networking-Warranties

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

http://www.hpe.com/info/reach

http://www.hpe.com/info/ecodata

http://www.hpe.com/info/environment

mailto:[email protected]

hpe 3par windows server 2003 implementation guide · introduction hewlett packard enterprise (hpe)...

Documents