HPE 3PAR Microsoft Windows Server Implementation Guide · Beginning with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5, FCoE target support was added for Windows Server 2016. Beginning with

HPE 3PAR Microsoft Windows ServerImplementation Guide

Part Number: QL226-10599aPublished: December 2018Edition: 1

AbstractThis guide provides information for establishing communication between an HPE 3PARStoreServ Storage system and a host running Microsoft Windows Server 2019, MicrosoftWindows Server 2016, Microsoft Windows Server 2012, or Microsoft Windows Server 2008. Itis intended for system and storage administrators who manage system configurations andresource allocation for the HPE 3PAR StoreServ Storage system.

© Copyright 2012, 2018 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®, Xeon®, Intel Inside®, and the Intel Inside logo are trademarks of IntelCorporation in the U.S. 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 to the HPE 3PAR Microsoft Windows ServerImplementation Guide ........................................................................... 6

Audience....................................................................................................................................... 6HPE 3PAR OS versions reference................................................................................................6Supported configurations.............................................................................................................. 6HPE 3PAR OS upgrade considerations........................................................................................7HPE 3PAR coexistence.................................................................................................................7HPE 3PAR documentation............................................................................................................8

Configuring the HPE 3PAR StoreServ Storage and host—FC............9Workflow for configuring the HPE 3PAR StoreServ Storage and host—FC................................. 9Considerations for planning the configuration—FC...................................................................... 9

Target port limits and specifications—FC.........................................................................10HPE 3PAR Persistent Ports—FC..................................................................................... 11HPE 3PAR Smart SAN—FC............................................................................................ 12HPE 3PAR Priority Optimization—FC.............................................................................. 12HPE 3PAR Persistent Checksum—FC............................................................................ 13HPE 3PAR Express Writes—FC...................................................................................... 13

Configuring the HPE 3PAR StoreServ Storage ports—FC......................................................... 13Configuring ports on the HPE 3PAR StoreServ Storage—direct connection—FC...........14Creating a host definition—FC......................................................................................... 17Configuration guidelines for switch vendors—FC............................................................ 18

Configuring the host—FC........................................................................................................... 19Checking the host for required drivers............................................................................. 20Installing and configuring an Emulex HBA—FC...............................................................20Installing and configuring a QLogic HBA—FC................................................................. 20Installing and configuring a Brocade HBA—FC............................................................... 21Installing Veritas DMP multipathing on the Windows Server host....................................22Disabling the write cache option for HPE 3PAR LUNs .............................................. 23Setting up multipathing software—FC..............................................................................24

Configuring the HPE 3PAR StoreServ Storage and host—iSCSI..... 27Setting up multipathing software—iSCSI.................................................................................... 27Workflow for configuring the HPE 3PAR StoreServ Storage and host—iSCSI...........................27Considerations for planning the configuration—iSCSI................................................................28

Target port limits and specifications—iSCSI.................................................................... 28HPE 3PAR Persistent Ports—iSCSI.................................................................................29VLAN configuration and routing setup............................................................................. 30

Connecting the HPE 3PAR StoreServ Storage to the host—iSCSI............................................ 30Enterprise iSCSI...............................................................................................................30Setting up the initiator and target ports—iSCSI .............................................................. 30

Configuring the HPE 3PAR StoreServ Storage iSCSI ports....................................................... 30HPE 3PAR iSCSI IPv6 addressing and vLAN tagging................................................................32Configuring the host—Software iSCSI........................................................................................33

Establishing a connection with the initiator software—iSCSI........................................... 33Configuring host no traffic reattach—iSCSI .............................................................38Using the Microsoft iSNS server to discover registrations............................................... 39

3

Establishing an iSCSI logon session and enabling multipathing—iSCSI.........................40Configuring host and target CHAP...................................................................................43Checking Emulex HBA parameters and connection status..............................................48

Configuring the host—Hardware iSCSI...................................................................................... 48Hardware iSCSI support...................................................................................................48

Configuring the HPE 3PAR StoreServ Storage and host—FCoE..... 54Setting up multipathing software—FCoE.................................................................................... 54Workflow for configuring the HPE 3PAR StoreServ Storage and host—FCoE...........................54Considerations for planning the configuration—FCoE................................................................54

Target port limits and specifications—FCoE.................................................................... 55Windows host requirements.............................................................................................55VLAN configuration and routing setup............................................................................. 55HPE 3PAR Persistent Ports—FCoE.................................................................................56

Connecting the HPE 3PAR StoreServ Storage to the host—FCoE............................................ 57Setting up and zoning the fabric—FCoE..........................................................................57

Configuring the HPE 3PAR StoreServ Storage ports—FCoE.....................................................58Planning to configure ports—FCoE..................................................................................58Removing iSCSI port configuration—FCoE..................................................................... 58Changing an iSCSI configured port to FCoE................................................................... 59Configuring the HPE 3PAR StoreServ Storage ports—FCoE..........................................60

Creating the host definition—FCoE............................................................................................ 60Configuring the host—FCoE....................................................................................................... 60

Configuring the switch—FCoE......................................................................................... 61Using the Emulex CNA—FCoE........................................................................................62Using the QLogic CNA—FCoE........................................................................................ 67Configuring FCoE initiator to FC target............................................................................ 70Configuring FCoE initiator to FCoE target........................................................................71

Windows Hyper-V Server/HPE 3PAR StoreServ Storageconfiguration......................................................................................... 73

Hyper-V software installation...................................................................................................... 73Hyper-V software configuration...................................................................................................73

Allocating storage for the host............................................................ 74Creating storage on the HPE 3PAR StoreServ Storage ............................................................ 74

Virtual volumes creation...................................................................................................74Exporting VLUNs to the host............................................................................................76

Discovering LUNs....................................................................................................................... 76Scanning for new devices on a Windows Server host................................................................ 77Removing a storage volume from the Windows Server host...................................................... 78SCSI UNMAP primitive support for Windows Server 2019/2016/2012.......................................78ODX support for Windows Server 2019, Windows Server 2016, Windows Server 2012, andWindows Server 2012 R2........................................................................................................... 79

Booting the host from the HPE 3PAR StoreServ Storage................. 80Configuring for iSCSI SAN boot..................................................................................................80Configuring the BIOS for FC SAN boot.......................................................................................80

Configuring for an HPE 3PAR StoreServ Storage boot—Emulex HBA............................81Configuring for an HPE 3PAR StoreServ Storage boot—QLogic HBA............................ 81

Creating the host definition for an HPE 3PAR StoreServ Storage boot—FC..............................82Connecting the HPE 3PAR StoreServ Storage to the host—FC.................................................82

4

Assigning LUNs as the boot volume........................................................................................... 82Installing the host OS onto the FC boot volume......................................................................... 82Connecting multiple paths for FC SAN boot............................................................................... 83

Configuring additional HPE3PAR software features......................... 84HPE 3PAR All Flash Arrays........................................................................................................ 84HPE 3PAR Peer Motion, Online Import, and Storage Federation...............................................85HPE 3PAR Peer Persistence...................................................................................................... 86HPE 3PAR File Persona............................................................................................................. 87

Mounting SMB file shares in File Services using CLI commands.................................... 88

Using failover clustering in a virtualized environment......................90

Using failover clustering with Microsoft MPIO...................................91

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

Using Microsoft Clustering with Veritas DMP.................................... 95Installing Veritas DMP.................................................................................................................95

Websites................................................................................................ 97

Support and other resources...............................................................98Accessing Hewlett Packard Enterprise Support......................................................................... 98Accessing updates......................................................................................................................98Customer self repair....................................................................................................................99Remote support.......................................................................................................................... 99Warranty information...................................................................................................................99Regulatory information..............................................................................................................100Documentation feedback.......................................................................................................... 100

5

Introduction to the HPE 3PAR MicrosoftWindows Server Implementation Guide

This Hewlett Packard Enterprise (HPE) implementation guide provides information for establishingcommunication between the HPE 3PAR StoreServ Storage system and a host running Microsoft WindowsServer. It describes the steps for allocating storage on the HPE 3PAR StoreServ system.

NOTE:

• For predictable performance and results with the HPE 3PAR StoreServ Storage, the information in thisguide must be used in conjunction with the documentation provided by Hewlett Packard Enterprise forthe HPE 3PAR StoreServ Storage and the documentation provided by the vendor for its respectiveproducts.

• In addition to the OS patches mentioned in this guide, there might be patches referenced on the SPOCK website.

For information about supported hardware and software platforms, see the SPOCK website (SPOCKHome > 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 HPE 3PAR StoreServ Storage. It is assumed thatthe administrators are familiar with the host OS and the HPE 3PAR OS.

HPE 3PAR OS versions referenceThis guide references older versions of the HPE 3PAR OS that are not supported, such as 3.1.1, 3.1.2,3.1.3, and 3.2.1. These versions are mentioned to document when a storage feature was first introduced.This guide is not a statement of support.

For information about the latest supported hardware and software releases, refer to the Active/InactiveStatus of HPE 3PAR OS document on the SPOCK website (SPOCK Home > Software > 3PAR ArraySoftware > HPE 3PAR Product Safe Harbor, OS Active/Inactive Status).

Supported configurationsThe following types of host connections are supported between the HPE 3PAR StoreServ Storage andhosts running Windows Server 2019, Windows Server 2016, Windows Server 2012 (and 2012 R2), orWindows Server 2008 (and 2008 R2):

• FC (Fibre Channel)

• Software iSCSI initiator

• Hardware iSCSI initiator (supported on Windows Server 2008 R2 SP1 and later on x64 architectureonly)

• FCoE (Fibre Channel over Ethernet) initiator ports to FC HPE 3PAR OS target ports

• FCoE initiator ports to FCoE HPE 3PAR OS target ports:

6 Introduction to the HPE 3PAR Microsoft Windows Server Implementation Guide

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


https://h20272.www2.hpe.com/spock/

◦ Beginning with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5, FCoE target support was added forWindows Server 2016.

◦ Beginning with HPE 3PAR OS 3.2.1, FCoE target support was added to Windows Server 2008and Windows Server 2008 R2.

◦ Beginning with HPE 3PAR StoreServ Storage 3.1.3, FCoE target support was added forWindows Server 2012 and Windows Server 2012 R2.

• Microsoft Hyper-V

• FC connections between the HPE 3PAR OS and the host in both a fabric-attached and direct-connecttopology.

• A host running Windows Server 2019, Windows Server 2016, Windows Server 2012, or WindowsServer 2008 requires the following software, unless otherwise specified:

◦ Multipathing: Native Microsoft MPIO

◦ iSCSI only: Microsoft iSCSI initiator (not required for hardware iSCSI configurations)

HPE 3PAR OS upgrade considerationsAfter an HPE 3PAR StoreServ Storage OS upgrade—whether it is a major upgrade or an MU update inthe same release—the Windows server marks the HPE 3PAR LUNs as offline, but the data remainsintact. This is the expected behavior only in the following situations:

• HPE 3PAR LUNs are discovered by nonclustered Windows servers.

• HPE 3PAR LUNs are used in Microsoft Failover Clustering, but they are not configured as sharedstorage in the failover cluster.

If the HPE 3PAR LUNs are configured as shared storage in the Microsoft Failover Cluster, theWindows server will not see LUNs marked as offline

When HPE 3PAR LUNs are marked as offline, the Windows Server administrator must perform thesesteps to enable applications to access the LUNs:

1. From the Server Manager, select Tools > Computer Management > Storage > Disk Management.

2. Right-click each HPE 3PAR LUN, one at a time, and set the LUN to Online.

For details about supported host configurations and interoperability, see the SPOCK website (SPOCKHome > Explore Storage Interoperability With SPOCK > Explore 3PAR StoreServ Storageinteroperability).

More information

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

HPE 3PAR coexistenceThe HPE 3PAR StoreServ Storage array can coexist with other Hewlett Packard Enterprise storage arrayfamilies.

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

Introduction to the HPE 3PAR Microsoft Windows Server Implementation Guide 7


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

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


HPE 3PAR documentationType of documentation: See:

Current version of this implementationguide and other 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 StoreServStorage.

3. Under Product series, select your product series.

All Hewlett Packard Enterprise products Hewlett Packard Enterprise Support Center

8 Introduction to the HPE 3PAR Microsoft Windows Server Implementation Guide



https://sml-csr.ext.hpe.com/

https://sml-csr.ext.hpe.com/

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

Configuring the HPE 3PAR StoreServ Storageand host—FC

Hewlett Packard Enterprise recommends using the default values to configure the host unless instructedotherwise in the procedures.

Workflow for configuring the HPE 3PAR StoreServ Storageand host—FC

PlanningConsiderations

Connecting theStoreServto the host

Setting up andZoning the Fabric

Configuring theStoreServ

Storage PortsBooting Host

from StoreServStorage

Start

Setting upMultipathing

Software

ProvisioningStorage and Host

LUN Discovery

Using 3PARDevices on the

Host

Done

Configuring theHost

- Emulex HBA- Broadcom HBA- Cavium/Qlogic HBA

Figure 1: Configuring the HPE 3PAR StoreServ Storage and host—FC

Considerations for planning the configuration—FCWhen planning the configuration, review the following:

• Target port limits and specifications—FC on page 10

• HPE 3PAR Persistent Ports—FC on page 11

• HPE 3PAR Smart SAN—FC

• HPE 3PAR Priority Optimization—FC

• HPE 3PAR Persistent Checksum—FC on page 13

• HPE 3PAR Express Writes—FC

Configuring the HPE 3PAR StoreServ Storage and host—FC 9

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

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

• The maximum I/O queue depth per port on each HPE 3PAR StoreServ Storage HBA model follows:

HBA Protocol Array Bus Speed Ports Max. queuedepth

EmulexLPe12002

FC HPE 3PARStoreServ

7000

PCIe 8 Gb/s 2 3276

EmulexLPe12004


7000, 10000

PCIe 8 Gb/s 4 3276

EmulexLPe16002


7000, 8000,10000

PCIe 16 Gb/s 2 3072

EmulexLPe16004


8000, 9000,20000

PCIe 16 Gb/s 4 3072

EmulexLPe32002


8000, 9000,20000

PCIe 32 Gb/s 2 6144

• 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 Queue Full responsefrom the HPE 3PAR StoreServ Storage target port. This situation can result in erratic I/O performanceon each host. In this situation, throttle each host so that it cannot overrun the HPE 3PAR StoreServStorage port queues when the hosts are delivering their maximum number of I/O requests.

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

NOTE: Starting with HPE 3PAR OS 3.3.1, multiqueue processing is supported for the 16 Gb FC targetadapter. This feature ensures balanced CPU utilization and improved performance.

10 Configuring the HPE 3PAR StoreServ Storage and host—FC


HPE 3PAR Persistent Ports—FCThe HPE 3PAR Persistent Ports (or virtual ports) feature minimizes I/O disruption during an 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 that is automatically assigned by the system.Partner ports are assigned across array node pairs.

HPE 3PAR Persistent Ports allows an HPE 3PAR StoreServ Storage FC port to assume the identity of afailed WWN port while retaining its own identity. When a physical port assumes the identity of its partnerport, the assumed port is designated as a persistent port. Array port failover and failback with HPE 3PARPersistent Ports is transparent to most host-based multipathing software, which can keep all of the I/Opaths active.

NOTE: Implementation of the HPE 3PAR Persistent Ports feature does not eliminate the need to enableMicrosoft MPIO or install another supported multipathing software product.

For more information about HPE 3PAR Persistent Ports and a list of setup and connectivity guidelines,see the following documents:

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

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

More information

http://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.

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 loss of array port connectivityto the fabric.

To ensure that the HPE 3PAR Persistent Ports feature functions properly, observe the followingguidelines:

• The FC fabric must support N-Port ID Virtualization (NPIV), and NPIV must be enabled.

• HPE 3PAR StoreServ Storage FC partner ports must be connected to the same FC fabric, andpreferably to different FC switches in the fabric.

• The host-facing HBAs must be configured for point-to-point fabric connection. There is no support fordirect-connect loops.

For information about the HPE 3PAR Persistent Ports feature for an FCoE initiator to FC targetconfiguration (FCoE to FC switched), see Configuring FCoE initiator to FC target on page 70.



http://h17007.www1.hpe.com/us/en/storage/info-library/



HPE 3PAR Smart SAN—FCStarting 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





The HPE 3PAR Smart SAN TDPZ (target-driven peer zoning) feature enables customers to automatepeer zoning, which provides the following benefits:

• The creation of fewer zones

• The configuration of zones in minutes

• Reduced potential for errors and downtime

With HPE 3PAR Smart SAN, the administrator can configure and control zoning directly from theHPE 3PAR CLI. Otherwise, the administrator must preconfigure zones on the FC switch beforeconfiguring hosts and VLUNs on the HPE 3PAR StoreServ Storage.

Starting with HPE 3PAR OS 3.3.1, HPE 3PAR Smart SAN 2.0 is supported. With HPE 3PAR Smart SAN2.0, the target ports support device registration on the fabric using the Fabric Device ManagementInterface (FDMI). The switch CLI command enables you to display the FDMI data containing Target PortManagement information. Additional Smart SAN HBA attributes are registered only with Smart SAN-capable switches.

For information about supported FC switches and their firmware revisions with HPE 3PAR Smart SAN,see the SPOCK website (SPOCK Home > Other Hardware > 3PAR).

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

HPE 3PAR Priority Optimization—FCStarting with HPE 3PAR OS 3.1.2 MU2, the HPE 3PAR Priority Optimization feature is available. Thisfeature is a more efficient and dynamic solution for managing server workloads and can be used as analternative to setting host I/O throttles. Using this feature, a storage administrator can share storageresources more effectively by enforcing Quality of Service (QoS) limits on the array.

NOTE: No special settings are required on the host side to get the full benefit of HPE 3PAR PriorityOptimization. However, certain per-target or per-adapter throttle settings might need to be adjusted. Forinformation about using HPE 3PAR Priority Optimization on the HPE 3PAR StoreServ Storage, see thetechnical white paper HPE 3PAR Priority Optimization software.

OS expected behavior

Windows might take the LUN offline if the bandwidth QoS rule on the VVset that the VV/LUN belongs to istoo aggressive. In this situation, you must decrease the bandwidth QoS rule.




https://h20195.www2.hpe.com/v2/getpdf.aspx/4AA4-6961ENW.pdf

HPE 3PAR Persistent Checksum—FCThe HPE 3PAR Persistent Checksum feature is available on HPE 3PAR StoreServ 20000, 9000, and8000 Storage systems. It provides end-to-end data integrity protection from the host initiator HBA,through the data network, to the back-end drives on the HPE StoreServ Storage.

HPE 3PAR Persistent Checksum is based on the Data Integrity Field (DIF) protection model defined bythe SCSI T10 Technical Committee. It provides data protection when media and transmission errors arecaused by any component in the I/O stack. Detection and recovery features are built into the HPE 3PAROS to correct issues discovered by HPE 3PAR Persistent Checksum.

Supported HPE bundled HBA driver versions are required for HPE 3PAR Persistent Checksum over FC.Using these drivers, HPE 3PAR Persistent Checksum is enabled by default on the HPE 3PAR StoreServStorage. You do not need to configure anything on the array or the host HBA driver.

For information about supported HBAs, HBA driver versions, and host operating systems that supportHPE 3PAR Persistent Checksum (DIF capable), see Explore 3PAR StoreServ Storage interoperability onthe SPOCK website.

For more information about HPE 3PAR Persistent Checksum, see the technical white paper HPE 3PARStoreServ Architecture on the Hewlett Packard Enterprise Information Library website.

More information

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

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.

Configuring the HPE 3PAR StoreServ Storage ports—FCThis topic describes how to configure the HPE 3PAR StoreServ Storage ports for a direct connection or afabric connection.

NOTE:

• Each HPE 3PAR StoreServ Storage port connecting to a host HBA port through a direct connection ora fabric connection must be set to the correct host persona.

• To deploy Virtual Connect Direct-Attach Fibre Channel for HPE 3PAR StoreServ Storage systems,where the HPE 3PAR StoreServ Storage ports are cabled directly to the uplink ports on the VirtualConnect FlexFabric 10 Gb/24-port Module for c-Class BladeSystem, follow the instructions in Configuring ports on the HPE 3PAR StoreServ Storage—fabric connection—FC on page 16 .

For more information about Virtual Connect, Virtual Connect interconnect modules, and the VirtualConnect Direct-Attach Fibre Channel feature, see the Virtual Connect documentation on the HewlettPackard Enterprise Support Center website. See also the HPE SAN Design Reference Guide onthe SPOCK website (SPOCK Home > Design Guides > SAN Design Guide).


https://h20272.www2.hpe.com/SPOCK/







Prerequisites

Before configuring the HPE 3PAR StoreServ Storage ports for a direct connection or a fabric connection,read Configuration guidelines for switch vendors—FC on page 18.

More information

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

Configuring ports on the HPE 3PAR StoreServ Storage—direct connection—FC

This topic describes how to configure a direct connection to an FC HPE 3PAR StoreServ Storage targetinterface. Multiple HPE 3PAR host ports can be directly connected to the host HBA ports. You mustcomplete this procedure for each port being directly connected to the host.

Prerequisites

Before configuring the HPE 3PAR StoreServ Storage ports for a direct connection, read Directconnection support—FC on page 15.

Procedure

1. Take the port offline by using the controlport offline <node:slot:port> command. Forexample:

cli % controlport offline 0:1:1

2. Specify the connection type (-ct) by using the controlport config host -ct <connectiontype> <node:slot:port> command, where <connection type> is either loop or point. Forexample:

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

To determine which connection type to use, see the direct connection support table in Directconnection support—FC on page 15.

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

cli % controlport rst 0:1:1

4. Verify that the port is configured for a direct connection by using the showport -par command todisplay the connection type (ConnType) of the port.

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




Use the showport -par command to identify the maximum speed (MaxRate) of the port. In thisexample, port 0:1:1 has a maximum speed of 8 Gb/s, and port 2:1:1 has a maximum speed of 16Gb/s.

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

5. After all of the required HPE 3PAR StoreServ Storage ports have been configured, connect the hostHBA ports directly to the StoreServ Storage ports using cables with the appropriate specifications.

Direct connection support—FCSupport for direct connection to FC HPE 3PAR StoreServ Storage target interfaces is limited to specifichost adapters.

Starting with HPE 3PAR OS version 3.2.2 MU2, direct connection to a 16 Gb FC HPE 3PAR StoreServStorage target interface is supported.

Direct connection support table

The connection type of an HPE 3PAR array target port depends on the HPE 3PAR OS version on thearray, the array target port type, and the speed of the host FC adapter that will directly connect to thearray. Use the following table to determine the required connection type for the HPE 3PAR array.

HPE 3PAR OSversion

HPE 3PAR arraytarget port

Supported hostadapter port

Connection type Link speed

3.2.2 MU1 andearlier

8 Gb/s 4 Gb/s Loop 4 Gb/s

8 Gb/s Loop 8 Gb/s

16 Gb/s Loop 8 Gb/s

16 Gb/s Not supported Not supported Not supported

3.2.2 MU2 andlater versions of3.2.2

8 Gb/s 4 Gb/s Loop 4 Gb/s

8 Gb/s Loop 8 Gb/s

16 Gb/s Loop 8 Gb/s

16 Gb/s 8 Gb/s Point 8 Gb/s

16 Gb/s Point 16 Gb/s


3.3.1 GA and later 8 Gb/s8 Gb/s Loop 8 Gb/s

Table Continued


HPE 3PAR OSversion

HPE 3PAR arraytarget port

Supported hostadapter port

Connection type Link speed

16 Gb/s Loop 8 Gb/s

16 Gb/s8 Gb/s Point 8 Gb/s



For more information, see the SPOCK website (SPOCK Home > Explore Storage interoperability WithSPOCK > Explore 3PAR StoreServ Storage interoperability).

Configuring ports on the HPE 3PAR StoreServ Storage—fabric connection—FCThis topic describes how to configure ports on the HPE 3PAR StoreServ Storage for a fabric connection.You must complete steps 1 through 4 of this procedure for each port being connected to the switch fabric.

Procedure

1. Determine if a port is configured for a fabric connection by using the showport -par command.

cli % showport -par

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal TMWO Smart_SAN0:0:1 host point auto 16Gbps disabled disabled disabled disabled disabled unknown0:0:2 host point auto 16Gbps disabled disabled disabled disabled disabled disabled

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

2. If the port has not been configured for a fabric connection, take the port offline by using thecontrolport offline <node:slot:port> command.

CAUTION: Before taking the port offline, verify that it has not already been defined and that it isnot connected to a host. Otherwise, it will interrupt the existing host connection.

cli % controlport offline 1:5:1

3. Specify the connection type (-ct) by using the controlport config host -ct point<node:slot:port> command, where point indicates that the connection type is a fabricconnection. For example:

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

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



cli % controlport rst 1:5:1

5. Connect each host HBA port to the fabric, and then associate the WWN of each host HBA port withthe HPE 3PAR StoreServ Storage port to which it connects.

6. Complete zoning as required and described in the SAN Design Reference Guide.

7. Verify that the host is connected to the HPE 3PAR StoreServ Storage by using the showhostcommand.

cli% showhostId Name Persona -WWN/iSCSI_Name- Port 100000FD454EC763 0:2:3 100000FD454EC762 1:2:3

Creating a host definition—FCWith HPE 3PAR OS 3.2.1 and later, Hewlett Packard Enterprise requires host WindowsServer persona15 for Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012,Windows Server 2008 R2 SP1, or Windows Server 2008 SP2.

Procedure

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

cli% createhost -persona 15 windowshost 100000FD454EC763

For information about other options, see the HPE 3PAR OS Command Line Interface Reference onthe Hewlett Packard Enterprise Information Library website.

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

cli% showhostId Name Persona -WWN/iSCSI_Name- Port0 windowshost WindowsServer 100000FD454EC763 ---

More information


Changing host persona 2 to host persona 15Changing to host Windows Server (15) persona is an online procedure.

Prerequisites

Before changing the host persona, see the instructions for preventing loss of LUN mapping in theHPE 3PAR Operating System Update Planning Guide on the Hewlett Packard Enterprise InformationLibrary website.


https://support.hpe.com/hpsc/doc/public/display?docId=c00403562





Procedure

Change from host persona 2 to host persona 15 by using the HPE 3PAR CLI sethost command, andthen verify the change by using the showhost command.

cli% sethost -persona 15 windowshostcli% showhost

Id Name Persona -WWN/iSCSI_Name- Port0 windowshost WindowsServer 10000000C9606724 0:5:1 10000000C9606724 1:5:1

Changing host persona 6 or persona 1 to host persona 2Changing to host Generic-ALUA (2) persona is an offline procedure.

Prerequisites

Before changing the host persona, see the instructions for preventing loss of LUN mapping in theHPE 3PAR Operating System Update Planning Guide on the Hewlett Packard Enterprise InformationLibrary website.

Procedure

1. Stop all host I/O on the Windows Server host.

2. Shut down the host.

3. Issue the showhost command. Make sure that no active paths are shown.

4. To change the persona, issue the HPE 3PAR CLI sethost command.

5. To verify the setting, issue the HPE 3PAR CLI showhost command.

cli% sethost -persona 2 windowshostcli% showhost

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

6. Turn on the Windows Server. The host enables ALUA on all the LUN paths when it boots.

Configuration guidelines for switch vendors—FCBefore configuring the ports on fabrics to which the HPE 3PAR StoreServ Storage connects, observe thefollowing FC switch vendor guidelines:

• HPE B-series switch ports that connect to a host HBA port or to an HPE 3PAR StoreServ Storageport must be set to their default mode. Verify that each switch port is set to the correct mode by issuingthe portcfgshow command from the Brocade Telnet interface.




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.

Display the fill-word modes supported on an HPE Brocade 8 Gb switch running FOS firmware 6.3.1aor later by using the portcfgfillword command.

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

NOTE: All Gen 5 (16 Gb) and Gen 6 (32 Gb) HPE StoreFabric B-series switches automatically selectthe correct fill word. For legacy Gen 4 (8 Gb) switches, Hewlett Packard Enterprise recommendssetting the fill word to the preferred mode—mode 3 (aa-then-ia)—by using the portcfgfillwordcommand. If the fill word is not set correctly, er_bad_os counters (invalid ordered set) will increasewhen using the portstatsshow command while connected to 8 Gb HBA ports, as the er_bad_oscounters require the ARBFF-ARBFF fill word. Mode 3 also works correctly for lower-speed HBAs, suchas 4 Gb/2 Gb HBAs. For more information, see the Fabric OS Command Reference Manual and theFOS release notes on the Brocade website.

• HPE C-series/Cisco switch ports that connect to HPE 3PAR StoreServ Storage ports or host HBAports must be set to AdminMode = FX and AdminSpeed = auto port, with the speed set to autonegotiate.

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

Configuring the host—FCPerform the following tasks to configure the host:

• Checking the host for required drivers.

• Installing and configuring an Emulex HBA—FC.

• Install and configure a QLogic HBA—FC.

• Install and configure a Brocade HBA—FC.

• Install Veritas DMP multipathing on the Windows Server 2008 host.

• Disable the write cache option for 3PAR LUNs .

• Set up multipathing—FC.


https://www.broadcom.com/

NOTE: Hewlett Packard Enterprise recommends using the default values in the procedures unlessotherwise specified.

Checking the host for required driversSee the Microsoft website for any required packages, hotfixes, and updated drivers. See the SPOCKwebsite for supported drivers, and follow HBA vendor instructions.

You can also use the Emulex (Broadcom) OCManager software or the QLogic (Cavium)QConvergeConsole software to verify support for HBA driver versions.

More information


Installing and configuring an Emulex HBA—FCFor HBA installation instructions, driver support, and usage guidelines, see the Emulex installation andusage guide for the specific HBA. If your configuration includes Multipath I/O (MPIO), check forinformation about the required MPIO support driver.

NOTE: To boot from the HPE 3PAR StoreServ Storage, you must configure the BIOS. For instructions,see Configuring for an HPE 3PAR StoreServ Storage boot—Emulex HBA on page 81.

Configuring the Emulex HBA driverFor information about setting the Emulex HBA driver parameters, see the HBA driver documentation.

NOTE:

• When host ports access multiple targets on fabric zones, the target number (assigned by the hostdriver) for each discovered target can change when the host is booted and certain targets are notpresent in the zone. In this situation, the device node access point might change for devices. This canoccur with any fabric-connected storage—it is not specific to the HPE 3PAR StoreServ Storage.

• If you plan to perform an HPE 3PAR OS online upgrade, see the HPE 3PAR Operating System UpdatePlanning Guide in the Reference section of the Hewlett Packard Enterprise Information Librarywebsite.

• For information about how to avoid overwhelming a target port and to ensure continuous I/Ooperations, see Target port limits and specifications—FC on page 10.

Checking the Emulex HBA parameters and connection statusCheck the Emulex HBA parameters and the connection status by using the Emulex OCManager utility.

For more information about the Emulex HBA parameters, see Target port limits and specifications—FC.

Installing and configuring a QLogic HBA—FCFor HBA installation instructions, driver support, and usage guidelines, see the QLogic installation andusage guide for the specific HBA. If your configuration includes Multipath I/O (MPIO), check forinformation about the required MPIO support driver.

NOTE: To boot from the HPE 3PAR StoreServ Storage, you must configure the BIOS. For instructions,see Configuring for an HPE 3PAR StoreServ Storage boot—QLogic HBA on page 81.





More information

Configuring for an HPE 3PAR StoreServ Storage boot—QLogic HBA on page 81

Configuring the QLogic HBA driverFor information about setting the QLogic HBA driver parameters (such as the maximum number of LUNsper target and the Port Down Retry Count), see the HBA driver documentation.

NOTE:



• For information about how to avoid overwhelming a target port and to ensure continuous I/Ooperations, see Target port limits and specifications—FC on page 10.

Checking the QLogic HBA parameters and connection statusCheck the QLogic HBA parameters and the connection status by using the QLogic QConvergeConsolesoftware.

Installing and configuring a Brocade HBA—FCFor HBA installation instructions, driver support, and usage guidelines, see the Brocade installation andusage guide for the specific HBA. If your configuration includes Multipath I/O (MPIO), check forinformation about the required MPIO support driver.

Configuring the Brocade HBA driverFor information about setting the Brocade HBA driver parameters, see the HBA driver documentation.

NOTE:



Checking Brocade HBA parameters and connection statusCheck the Brocade HBA parameters and the connection status by using the Brocade Host ConnectivityManager utility.

To reduce the time to complete an MPIO path failover, Hewlett Packard Enterprise recommends settingthe path timeout value (TOV) to 14 seconds.




1. Right-click the FC port to be modified and select vHBA Configuration.

2. Change the Path TOV (seconds) value to 14.

3. Repeat steps 1 and 2 for each FC port.

4. Restart the host to activate the new setting.

Installing Veritas DMP multipathing on the Windows Server host

NOTE: Check for Veritas compatibility on the Veritas website. Otherwise, when Veritas attempts tovalidate the server components, you might see the error message NOT a supported OS, and theinstallation will fail.

If the configuration includes Veritas Storage Foundation software, configure it for use with the HPE 3PARStoreServ Storage.

Procedure

1. Install the latest Device Driver Installation (DDI) packet from the Veritas website.

2. Select 3PARDATA (V3PARAA) as the DMP device.


https://sort.veritas.com/documents


For more information, see the Veritas Storage Foundation for Windows Administration Guide andthe Veritas Storage Foundation and High Availability Solutions Installation and Upgrade Guide.

More information

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

Disabling the write cache option for HPE 3PAR LUNsHPE LUNs are always write cache enabled and, by design, cannot be disabled by user/administrator.

You can choose to ignore the message in the Write cache enabled information dialog box because theHPE 3PAR StoreServ Storage is a fault-tolerant redundant array. Disabling the cache is not required.



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

Click Close.

Setting up multipathing software—FC

• Windows Server 2019 and Windows Server 2016

Hewlett Packard Enterprise supports the following multipath solution:◦ Microsoft MPIO DSM

• Windows Server 2012 and Windows Server 2008

Hewlett Packard Enterprise supports the following multipath solutions:

◦ Microsoft MPIO DSM

◦ Veritas DMP/Veritas Infoscale Enterprise (Storage)

NOTE: For high-availability storage with I/O load balancing and improved system and applicationperformance, Windows Server 2012 and Windows Server 2008 require the native Microsoft MPIO andthe StorPort miniport driver.

Configuring Microsoft MPIO

Prerequisites

For a list of the required Microsoft hot fixes, see the SPOCK website. For more information about the hotfixes listed on the SPOCK website, see the Microsoft website.



https://www.microsoft.com

Procedure

1. If you have not already done so, check the HBA vendor documentation for the required supportdrivers and install them.

2. If necessary, install the HBA driver from the SPOCK website.

3. To determine if MPIO is currently installed, use the following command:

Get-WindowsOptionalFeature –Online –FeatureName MultiPathIO4. Open Server Manager and install the Multipath I/O feature.

5. Restart the Windows Server host.

6. Open the Windows Administrative Tools/Server ManagerToolsand click MPIO.

The MPIO Properties dialog box opens.

7. On the MPIO Devices tab, click Add.

The Add MPIO Support dialog box opens.

8. In the Device Hardware ID box, type 3PARdataVV, and then click OK.

9. On the Discover Multi-Paths tab, selectAdd support for iSCSI devices. Click add.

10. Reboot the server.



NOTE: You can also add the MPIO device 3PARdataVV by using the following MPIO CLI command:

mpclaim -r -I -d "3PARdataVV"

More information

http://www.hpe.com/storage/spockhttp://support.microsoft.com



http://support.microsoft.com

Configuring the HPE 3PAR StoreServ Storageand host—iSCSI

The HPE 3PAR StoreServ Storage supports Windows Server 2019, Windows Server 2016, WindowsServer 2012, and Windows Server 2008 software iSCSI initiators.

Beginning with HPE 3PAR OS 3.1.2, the HPE 3PAR StoreServ 10000 and 7000 Storage systemssupport hardware iSCSI initiators with supported converged network adapters (CNAs). Hardware iSCSIinitiators are also supported on the HPE 3PAR StoreServ 20000, 8000, and 9000 Storage systems. Formore information about supported configurations, see the SPOCK website. To configure supported CNAs,see the vendor documentation.

NOTE: Hewlett Packard Enterprise recommends the following:

• Use default values to configure your host unless otherwise specified in the following procedures.

• For more information about the Windows concepts and procedures described in this topic, see theMicrosoft iSCSI Software Initiator Users Guide.

More information


Setting up multipathing software—iSCSIFor information on setting up multipathing software, see Setting up multipathing software—FC.

Workflow for configuring the HPE 3PAR StoreServ Storageand host—iSCSI

Figure 2: Configuring the HPE 3PAR StoreServ Storage and host_iSCSI

Configuring the HPE 3PAR StoreServ Storage and host—iSCSI 27




Connecting theStoreServ to the

Host

Setting up theSwitch & iSCSI

Initiator


Storage Ports

Configuring theHost with

Software iSCSI

Configuring theHost with

Hardware iSCSI- Emulex CNA- Cavium/Qlogic CNA

Start


Software


LUN Discovery


Host

Done

CHAP forSoftware iSCSIBooting Host from

StoreServ Storage(HW iSCSI only)

CHAP forHardware iSCSI

Considerations for planning the configuration—iSCSIWhen planning your configurations, review the following:

• Target port limits and specifications—iSCSI on page 28

• HPE 3PAR Persistent Ports—iSCSI on page 29

• VLAN configuration and routing setup on page 30

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 onthe SPOCK website (SPOCK Home > Other Hardware > 3PAR).

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

28 Configuring the HPE 3PAR StoreServ Storage and host—iSCSI


HBA Protocol Array Bus Speed Ports Max. QueueDepth

QLogicQLE8242

iSCSI HPE 3PARStoreServ

7000, 10000

PCIe 10 Gbps 2 2048

QLogicEP8324

iSCSI HPE 3PARStoreServ

8000, 9000,20000

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 HPE 3PAR StoreServ Storage port. This condition can result in erratic I/Operformance on each host server. If this condition occurs, each host server should be throttled so thatit cannot overrun the HPE 3PAR StoreServ Storage port queues when all host servers are deliveringtheir maximum number of I/O requests.

More information


HPE 3PAR Persistent Ports—iSCSI

The HPE 3PAR Persistent Ports (or virtual ports) feature minimizes I/O disruption on an HPE 3PARStoreServ Storage online update, node-down, or cable pull event. Port shutdown or reset events do nottrigger this feature.

Each iSCSI target storage array port has a partner array port automatically assigned by the system.

Partner ports are assigned across array node pairs.

HPE 3PAR Persistent Ports allows an HPE 3PAR StoreServ Storage iSCSI port to assume the identity ofa failed 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 HPE 3PAR Persistent Ports technology does not negate the need for properly installed,configured, and maintained host multipathing software.

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

• Technical white paper HPE 3PAR StoreServ Persistent Ports at the Hewlett Packard EnterpriseSupport Center website.

• HPE 3PAR Command Line Interface Administrator's Manual, Using Persistent Ports for NondisruptiveOnline Software Upgrades at the Hewlett Packard Enterprise Information Library website.

More information







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

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

Connecting the HPE 3PAR StoreServ Storage to the host—iSCSI

Enterprise iSCSISupport for Enterprise iSCSI or iSCSI over data center bridging (DCB; lossless Ethernet) started withHPE 3PAR OS 3.2.2. DCB enhances Ethernet LANs for clustering and storage network use. HPE 3PARStoreServ 20000, 9000, and 8000 Storage systems support this feature.

With DCB, you can set up and configure different Ethernet traffic with different priorities. You can allocatebandwidth on links and eliminate packet loss due to queue overflow.

NOTE:

• No special settings are required on the HPE 3PAR iSCSI target port to support Enterprise iSCSI.

• Because each SAN environment is unique and has different requirements, no single switch networkconfiguration applies to all SAN environments. To configure iSCSI on an Ethernet switch that supportsDCB, see the switch vendor configuration guide.

For information about supported DCB Ethernet switches, see the SPOCK website (SPOCK Home >Design Guides > Other Configuration Guides).

More information

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

Setting up the initiator and target ports—iSCSI

Procedure

1. Connect the host iSCSI initiator ports and the HPE 3PAR StoreServ Storage iSCSI target ports to theswitches.

2. Verify that the iSCSI initiator discovers the HPE 3PAR StoreServ iSCSI target ports. Use the pingcommand to test connectivity to the HPE 3PAR StoreServ Storage iSCSI target ports.

Configuring the HPE 3PAR StoreServ Storage iSCSI portsSupport for IPv6 addressing, as well as IPv4 addressing, for iSCSI ports began with HPE 3PAR OS 3.2.2.3PAR StoreServ 20000, 9000 and 8000 Storage Systems support this feature. The iSCSI target ports on


http://www.hpe.com/networking/library


these arrays support multiple IP addresses for each iSCSI port. The IP addresses can be all IPv6, allIPv4, or a combination of both types of IP addressing.

The HPE 3PAR StoreServ 20000 and 8000 Storage systems also support vLAN tagging for iSCSI withboth IPv4 and IPv6 addressing. To configure the HPE 3PAR StoreServ 20000 or 8000 Storage systemswith IPv6, see HPE 3PAR iSCSI IPv6 addressing and vLAN tagging on page 32.

Procedure

IPv4 addressing for iSCSI:

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

cli % controlport config iscsi -f N:S:P

2. Check the current iSCSI port settings: use the showport -iscsi command.

Example showing ports offline and unconfigured:

cli % showport -iscsiN:S:P State IPAddr Netmask/PrefixLen Gateway TPGT MTU Rate iSNS_Addr iSNS_Port STGT VLAN0:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 1 1500 n/a 0.0.0.0 3205 1 Y0:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 2 1500 n/a 0.0.0.0 3205 2 Y1:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 101 1500 n/a 0.0.0.0 3205 101 Y1:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 102 1500 n/a 0.0.0.0 3205 102 Y

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

cli % controliscsiport addr 10.101.1.31 255.255.0.0 -f 0:3:1cli % controliscsiport addr 10.101.1.131 255.255.0.0 -f 1:3:1

4. Verify the configuration.

Example showing two ports ready:

cli % showport -iscsiN:S:P State IPAddr Netmask/PrefixLen Gateway TPGT MTU Rate iSNS_Addr iSNS_Port STGT VLAN0:3:1 ready 10.101.1.31 255.255.0.0 0.0.0.0 1 1500 10Gbps 0.0.0.0 3205 1 Y0:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 2 1500 n/a 0.0.0.0 3205 2 Y1:3:1 ready 10.101.1.131 255.255.0.0 0.0.0.0 101 1500 10Gbps 0.0.0.0 3205 101 Y1:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 102 1500 n/a 0.0.0.0 3205 102 Y

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

Example of the createhost command with Windows 2008 R2:

cli % createhost -iscsi -persona 15 sqa-dl380g5-08 iqn.1991-05.com.microsoft:sqa-dl380g5-08


NOTE: For more information about host personas and how to change the persona following an HPE3PAR OS upgrade, see Creating a host definition—FC on page 17.

With HPE 3PAR OS 3.2.1 and later, Hewlett Packard Enterprise requires host WindowsServerpersona 15 for Windows Server 2016, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2.

With HPE 3PAR OS 3.1.3 and later, Hewlett Packard Enterprise requires host WindowsServerPersona 15 for the following hosts:

• Windows Server 2019 (beginning with HPE 3PAR OS 3.2.2 MU6)

• Windows Server 2016 (beginning with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5)

• Windows Server 2012 R2

• Windows Server 2012



The iSCSI name/IQN must be obtained from the iSCSI initiator. For software iSCSI initiators, see Establishing a connection with the initiator software—iSCSI on page 33.

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

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

HPE 3PAR iSCSI IPv6 addressing and vLAN taggingTo configure the HPE 3PAR StoreServ Storage ports for iSCSI personality, follow these steps:

Procedure

1. Issue the following command:

cli % controlport config iscsi -f N:S:P

2. Check the current iSCSI port settings by issuing the showport -iscsi command. The followingexample shows ports offline and unconfigured (no IP address or vLAN tag) after the ports have beenset up with the iSCSI personality in the previous step.

cli % showport -iscsiN:S:P State IPAddr Netmask/PrefixLen Gateway TPGT MTU Rate iSNS_Addr iSNS_Port STGT VLAN0:6:1 offline :: 0 :: 61 1500 10Gbps :: 3205 61 - 0:6:2 offline :: 0 :: 62 1500 10Gbps :: 3205 62 - 1:6:1 offline :: 0 :: 161 1500 10Gbps :: 3205 161 - 1:6:2 offline :: 0 :: 162 1500 10Gbps :: 3205 162 - ----------------------------------------------------------------------------------------------------4


3. Issue the controliscsiport addr <netmask|prefix_len> [-f] <node:slot:port>command to set the IP addresses, prefix length, and vlan tag of the iSCSI target ports. For example:

cli % controliscsiport addr fd15:0816:c0::021 64 -vlan 816 -f 0:6:1

4. To display the IPv6 address and vlan tag of port 0:6:1, use the iscsivlan option in the showportcommand. For example:

cli % showport -iscsivlans 0:6:1N:S:P VLAN IPAddr Netmask/PrefixLen Gateway MTU TPGT STGT iSNS_Addr iSNS_Port0:6:1 816 fd15:816:c0::21 64 :: 1500 61 61 :: 3205

To see that port 0:6:1 is ready, issue the showport -iscsi command:

cli % showport -iscsi 0:6:1N:S:P State IPAddr Netmask/PrefixLen Gateway TPGT MTU Rate iSNS_Addr iSNS_Port STGT VLAN0:6:1 ready :: 0 :: 61 1500 10Gbps :: 3205 61 Y--------------------------------------------------------------------------------------------------1

If configured with vLAN, use showport -iscsivlans instead of showport -iscsi to display IPAddress:

cli % showport -iscsivlansN:S:P VLAN IPAddr Netmask/PrefixLen Gateway MTU TPGT STGT iSNS_Addr iSNS_Port0:6:1 - 10.101.1.61 255.255.255.0 10.101.1.1 1500 61 61 0.0.0.0 32050:6:2 - :: 0 :: 1500 62 62 :: 32050:6:2 62 fd15:816:c0:21 64 :: 1500 62 62 :: 32051:6:1 - 10.101.2.161 255.255.255.0 10.101.2.1 1500 161 161 0.0.0.0 32051:6:2 - :: 0 :: 1500 162 162 :: 32051:6:2 162 fd15:1816:c0:21 64 :: 1500 162 162 :: 3205----------------------------------------------------------------------------------------------6

NOTE: To configure IPv4 addressing and vLAN tagging on the HPE 3PAR StoreServ Storagesystems, follow the steps in Configuring the HPE 3PAR StoreServ Storage iSCSI ports on page 30,which describe how to configure IPv4 for the HPE 3PAR StoreServ Storage systems, with oneexception: When configuring an IPv4 address with the vLAN number that you want to assign to theIPv4 address, the -vlan option must be used.

Configuring the host—Software iSCSIHewlett Packard Enterprise recommends using default values to configure the HPE 3PAR StoreServStorage host, unless otherwise specified in the procedures that follow.

Establishing a connection with the initiator software—iSCSI

NOTE: With the exception of step 1, all steps are the same for Windows Server 2012 and WindowsServer 2008.


Procedure

1. To start the iSCSI initiator in Windows Server 2019, Windows Server 2016 or Windows Server 2012,click Server Manager > Tools > iSCSI Initiator.

To start the iSCSI initiator in Windows Server 2008, click Start > Programs > Administrative Tools >iSCSI Initiator.


2. From iSCSI Initiator Properties, select the Discovery tab.


3. On the Discovery tab Target portals area, click the Discover Portal... button, and in the DiscoverTarget Portal dialog box, enter the IP address of the portal you want to add.


4. To establish the connection, click Advanced. The Advanced Settings dialog box appears.

In the Connect using section of this dialog box:


a. In the Local Adapter drop-down menu, select Microsoft iSCSI Initiator.

b. In the Initiator IP: drop-down menu, select the IP address of the NIC adapter or CNA that you wantto use.

The CRC/Checksum is not required.

For more information about setting the CHAP login, see Configuring host and target CHAP on page43.

Click OK.

5. Click OK in the Discover Target Portal dialog box.

The Discovery tab in the iSCSI Initiator Properties window displays the port information.

6. Repeat these steps to connect additional target ports. Check the connections in the Discovery tab inthe iSCSI Initiator Properties window.

Configuring host no traffic reattach—iSCSIFollow these steps to reattach any dropped multipath connections that are currently not carrying traffic.

Procedure

1. Change the EnableNOPOut parameter for the iSCSI initiator in the Windows registry (iSCSI Ping):


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0005\Parameters]

NOTE: The \0005\ part of the registry path may be a different decimal number, such as \0003\,depending on your system setup.

2. Change the EnableNOPOut value from 00000000 to 00000001:

"EnableNOPOut"=dword:00000001

3. Restart the servers for the change to take effect.

Using the Microsoft iSNS server to discover registrationsThe Microsoft iSNS server is used to discover the iSCSI initiator and iSCSI targets on the dedicatednetwork. When the iSCSI initiator and iSCSI targets are registered with the iSNS server, theyautomatically start discovery of registered devices by querying the iSNS client/server via TCP/IP. Adatabase of these registrations is updated.

Configuring the initiator and target for iSNS server usage—iSCSI

Procedure

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

cli % showport -iscsiN: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:

cli % controliscsiport isns 10.0.0.60 0:1:1cli % controliscsiport isns 10.0.0.60 1:1:1

3. Verify the configuration setting for iSNS:

cli % showport -iscsiN: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

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

4. Use the Windows Server Add Features wizard to add the Internet Storage Name Server feature.


5. After the iSNS server is installed on another Windows Server, open the iSCSI Initiator and select theDiscovery tab. In the Discovery window, click the Add Server... button in the iSNS servers area.

6. Enter the IP address or DNS name, and then click OK.

Using the iSNS server to create a discovery domain

Procedure

1. Open the Windows Server domain discovery feature.

• Windows Server 2019, Windows Server 2016, Windows Server 2012, or Windows Server 2012 R2:Select Server Manager > Tools > iSNS Server > Discovery Domains.

• Windows Server 2008 or Windows Server 2008 R2: Select Start > Administrative Tools > iSNSServer > Discovery Domains.

2. In the window that opens, click the Create button. In the Create Discovery Domain pop-up window,enter the discovery domain or select the default and click OK.

3. Add iSNS to the iSCSI initiator.

a. Open iSCSI Initiator.

• Windows Server 2019, Windows Server 2016, Windows Server 2012, or Windows Server 2012R2: Select Server Manager > Tools > iSCSI Initiator.

• Windows Server 2008 or Windows Server 2008 R2: Select Start > Administrative Tools >iSCSI Initiator.

b. In the iSCSI initiator Properties, click the Discovery tab, click the Add Server in iSNS Serverssection, and enter iSNS-Server or iSNS-IP in the pop-up window's Add iSNS Server setting.

Establishing an iSCSI logon session and enabling multipathing—iSCSITo establish an iSCSI logon session with an HPE 3PAR StoreServ Storage iSCSI target port, follow thesesteps:

Procedure

1. Select the Targets tab.

This window displays the names and status of the ports you have already configured.

2. Click the Connect button to establish an iSCSI connection session with the HPE 3PAR StoreServStorage iSCSI target port.

The Connect to Target popup appears.


3. Click the Favorite Targets and Enable multi-path check boxes to select them.

Do not click OK.

4. Click the Advanced... button.

The Advanced Settings window appears.


5. In the Connect using section, choose the following options:

NOTE: The Microsoft iSCSI initiator will not work correctly if you have multiple local adapters, sourceIP addresses, and target ports and keep the default settings.

• Choose Microsoft iSCSI Initiator from the Local adapter drop-down menu.

• Choose the IP address of the NIC adapter or CNA in your system that will connect to the iSCSItarget port from the Initiator IP drop-down menu.

• Choose the IP address of the target portal (iSCSI target port) from the Target Portal IP drop-downmenu.

6. In the Advanced Settings window, click OK, and then click OK in the Connect to Target window.

The iSCSI initiator will establish an iSCSI session with the target port.

7. If desired, verify the connection:

In the Targets section of the iSCSI Initiator Properties window, the Status column for the target willshow the status as Connected.

8. Perform steps 4 through 7 to add the connection to the second target portal. The iSCSI InitiatorProperties window shows the status of both.


Configuring host and target CHAPThis topic contains the procedures for configuring the Challenge-Handshake Authentication Protocol(CHAP) and removing it.

1. Set host CHAP.

2. Set target CHAP.

3. Set mutual (bidirectional) CHAP.

4. Remove CHAP.

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

Procedure

1. Make sure that an iSCSI host definition was created on the HPE 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:


cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name

3. Use the sethost initchap <secret> <hostname> command to set initchap:

cli % sethost initchap MyChapSecret sqa-dl360g6-02-iscsiCalling "sethost initchap" for host sqa-dl360g6-02-iscsi. Continue?select q=quit y=yes n=no: y

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

cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name-25 sqa-dl360g6-02-iscsi sqa-dl360g6-02-iscsi

5. In the iSCSI Initiator Properties window, select the Targets tab and then choose the targets wherethe CHAP applies. Click Connect from Connect to Target, check the Enable multi-path, and thenclick the Advanced... button. On the Advanced Settings window, follow the steps:

a. Set the Microsoft iSCSI initiator for Local adapter.

b. Select the Initiator IP.

c. Select the Target Portal IP.

d. Check the Enable CHAP log on box.

e. Enter the CHAP secret for the Target secret.

NOTE: Enter MyChapSecret at the Target secret field.


Setting target CHAPTo set a target CHAP secret, configure it on both the HPE 3PAR StoreServ Storage and the WindowsServer host.

Procedure

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

cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name-

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

cli % sethost targetchap -f target_secret0 sqa-dl380g5-08

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

cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name 0 sqa-dl380g5-08 s055

4. In the iSCSI Initiator Properties window, click the Configuration tab. Click CHAP and enter theInitiator CHAP secret, then click OK.

NOTE: Enter target_secret0 from the example in step 2 at the Initiator CHAP secret field.


Setting mutual (bidirectional) CHAP

Procedure

1. Set the host CHAP secret following instructions in Setting host CHAP on page 43.

2. Set the target CHAP secret following instructions in Setting target CHAP on page 45.

3. Issue showhost -chap. The output shows both secrets set:

cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name 0 sqa-dl380g5-08 sqa-dl380g5-08 s055

Removing CHAPFollow these steps to remove the Challenge-Handshake Authentication Protocol (CHAP) from the HPE3PAR StoreServ Storage hosts.

Procedure

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


cli % 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:

cli % showhost -chapId Name -Initiator_CHAP_Name- -Target_CHAP_Name- 0 sqa-dl380g5-08 --

3. In the iSCSI Initiator Properties window, click the Targets tab where the CHAP applies; click theConnect button from the Connect to Target window and check the Enable multi-path option. Thenclick the Advanced... button and in the Advanced Settings window, follow these steps:

a. In the Local adapter field, select Microsoft iSCSI initiator.

b. Select the Initiator IP.

c. Select the Target portal IP.

d. Clear the Enable CHAP log on check box.


Checking Emulex HBA parameters and connection status

Procedure

1. Check the connection status using the Emulex OCManager utility.

2. Check the parameters.

Configuring the host—Hardware iSCSI

Hardware iSCSI supportStarting with HPE 3PAR OS 3.1.2.x, the HPE 3PAR StoreServ Storage systems introduce support forHardware iSCSI on Windows Server 2012 and Windows Server 2012 R2 and Windows Server 2008 R2SP1 with supported converged network adapters (CNAs). Hardware iSCSI Initiator support is also offeredon HPE 3PAR StoreServ 20000, 9000, and 8000 Storage systems and Windows Server 2016, WindowsServer 2012, Windows Server 2012 R2, and Windows Server 2008 R2 SP1 with HPE 3PAR OS 3.2.2MU3 and 3.2.1 MU5 and for Windows Server 2019 with HPE 3PAR OS 3.2.2 MU6.

This topic describes the basic Hardware iSCSI configuration using a CN1100E/CN1200E. For moreconfiguration information or for information about another CNA type, see the vendor-specificdocumentation.

NOTE:

• For Hardware iSCSI with QLogic CNAs, the ARP Redirect feature must be enabled in the host cardfirmware to support path failover with HPE 3PAR Persistent Ports.

This can be done through the QLogic Converge Console Utility. In the firmware settings of each iSCSIport, selected the IPv4 Network Settings, and then ensure ARP Redirect is checked.

• For the Hardware iSCSI with Emulex CNAs, the UCNA driver has an extended timeout value set to 90seconds. This setting determines the amount of time the UCNA driver will wait for the target to becomeavailable after it has lost connection to the target during an I/O operation.

If the iSCSI initiator loses a path to the target, this default value delays any MPIO operations until thetimeout is reached, causing a significant delay in I/O operations.

The following registry entry can be modified to reduce the delay in I/O operations. For example,reducing this value to 30 seconds can result in the delay in I/O operations being reduced to less than40 seconds.

This setting is required prior to connecting to iSCSI target.

Updating the timeout value for Emulex CNAs

1. In a command shell or PowerShell window, run the regedit command

2. In the registry editor window, navigate to the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\be2iscsi\Parameters\Device

3. Change the DriversParamaters string value, modifying it to eto=30 or adding eto=30 asrequired.

4. Restart the host for the setting to take effect.


Verify that the ETO setting is 30 in OCManager in the Target Portal Information for both adapter ports. Ifnot, set the ETO setting to 30 in OCManager.

The CNA can be configured by using either Dependent iSCSI (the IP address of the system is obtainedfrom the host NIC connections) or Independent iSCSI (the IP address is entered into the CNA card). TheCN1100E/CN1200E can be configured to boot from SAN. SCSI targets are entered into the card. Forgeneral information about the CN1100E/CN1200E, see the Hewlett Packard Enterprise SupportCenter.

Updating MaxRequestHoldTime value in QLogic CNAs

1. In a command shell or PowerShell window, run the regedit command.

2. In the registry editor window, navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e97b-e325-11ce-bfc1-08002be10318}\0006\Parameters

3. Change the MaxRequestHoldTime value to 0.

4. Restart the host for the setting to take effect.

For more information about supported models and configurations, see the SPOCK website.

The Software iSCSI configuration requirements (port setup, network connectivity, and VLANconfiguration) also apply to Hardware iSCSi configuration.

More information


Setting the static IP address

Procedure

1. After installing the CN1100E, boot the system. The following text appears in the BIOS:

Emulex 10Gb iSCSI Initiator BIOS..Press <Ctrl> <S> for iSCSISelect (M) Utility

2. Press Ctrl+S to enter the utility.


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

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




3. Select a controller and press Enter.

4. From the Controller Configuration screen, select Network Configuration and press Enter.

5. In the Network Configuration screen, select Configure Static IP Address and press Enter.

The screen for setting a static IP address appears.

6. After entering the IP address, subnet mask, and default gateway, click Save to return to the ControllerConfiguration menu.

Starting iSCSI hardware from SAN

Procedure

1. On the iSCSI Initiator Configuration screen (the first screen displayed), obtain the IQN for the cardand create a host definition on the HPE 3PAR StoreServ Storage.

For example:

createhost –iscsi –persona 15 ws2012host1 iqn.1990-07.com.emulex:a0-b3-cc-1c-94-e1

2. Assign a VLUN to the host definition to be used as the SAN boot LUN.

3. From the Controller Configuration menu, select Controller Properties.

4. On the properties screen, verify that boot support is enabled. If not, scroll to Boot Support andenable it, and then save and exit this screen.

5. From the Controller Configuration menu, select iSCSI Target Configuration.

6. From the iSCSI Target Configuration menu, select Add New iSCSI Target and press Enter.

7. Complete the information for the first iSCSI target. Make sure Boot Target is set to Yes.


8. After completing the information for the iSCSI target, click Ping to verify connectivity.

9. After a successful ping, click Save/Login.

10. After both controllers have been configured, use the showiscsisession command to display theiSCSI sessions on the HPE 3PAR StoreServ Storage and the host.

If everything is configured correctly, the following is displayed:

cli% showiscsisessionN:S:P -IPAddr-- TPGT TSIH Conns ------------iSCSI_Name------------ -------StartTime------- VLAN State0:2:1 11.2.1.10 21 15 1 iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 2018-07-24 20:48:15 PDT - ONLINE0:2:2 11.1.1.10 22 15 1 iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 2018-07-24 23:05:08 PDT - ONLINE1:2:1 11.2.1.10 121 15 1 iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 2018-07-24 20:48:15 PDT - ONLINE1:2:2 11.1.1.10 122 15 1 iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 2018-07-24 23:05:14 PDT - ONLINE------------------------------------------------------------------------------------------------------4 totalcli% showhost -d c3-dl380g10-07Id Name Persona ----------WWN/iSCSI_Name---------- Port IP_addr41 c3-dl380g10-07 WindowsServer iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 1:2:2 11.1.1.1041 c3-dl380g10-07 WindowsServer iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 0:2:2 11.1.1.1041 c3-dl380g10-07 WindowsServer iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 1:2:1 11.2.1.1041 c3-dl380g10-07 WindowsServer iqn.1995-05.com.emulex.a0-b3-cc-1c-94-e1 0:2:1 11.2.1.10----------------------------------------------------------------------------------

11. If you do not want to use CHAP as an authentication method, exit the CN1100E setup screens, andthen restart.

• To use CHAP as an authentication method:

a. Return to the Add/Ping iSCSI Target screen, select Authentication Method, and then selectOne-Way CHAP.


The CHAP Configuration screen is displayed.

b. Type the Target CHAP Name (the initiator IQN name) and Target Secret, and then click OK.c. On the Add/Ping iSCSI Target screen, select Authentication Method, and then select

Mutual CHAP.

The CHAP Configuration screen is displayed.


d. Type the Target CHAP Name (the initiator IQN name), the Target Secret, the Initiator CHAPName (the DNS name of the HPE 3PAR StoreServ Storage), and the Initiator Secret, andthen click OK.

• To remove CHAP authentication, on the Add/Ping iSCSI Target screen, select AuthenticationMethod, and then select None.

12. When using CHAP authentication, set the matching CHAP parameters for the host in the HPE 3PARStoreServ Storage, and then restart the host.

NOTE: If you do not want to configure CHAP by using the BIOS, edit the iSCSI initiator propertiesafter booting the system.

• If one-way CHAP is selected, enter the matching CHAP secret as follows:

cli% sethost initchap -f aaaaaabbbbbb ws2012host1cli% showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name-1 ws2012host1 ws2012host1 --

• If mutual CHAP is selected, enter the mutual CHAP secret as follows:

cli% sethost targetchap -f bbbbbbcccccc ws2012host1cli% showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name-1 ws2012host ws2012host1 S814root@jnodec103140:S99814#Id Name -Initiator_CHAP_Name- -Target_CHAP_Name-1 ws2012host1 ws2012host1 S814

13. After entering the CHAP secret, exit the BIOS and restart the host.


Configuring the HPE 3PAR StoreServ Storageand host—FCoE

FCoE target support was added in HPE 3PAR OS 3.1.3.

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

Setting up multipathing software—FCoEFor information on setting up multipathing software, see Setting up multipathing software—FC.

Workflow for configuring the HPE 3PAR StoreServ Storageand host—FCoE


Connecting theStoreServ to the

Host

Setting up andZoning the

Fabric


Storage Ports

Configuring theHost

- Emulex CNA- QLogic CNA

Start


Software


LUN Discovery


Host

Done

Booting Host fromStoreServ Storage

Figure 3: Configuring the HPE 3PAR StoreServ Storage and host—FCoE

Considerations for planning the configuration—FCoEWhen planning your configurations, review the following:

• Target port limits and specifications—FCoE on page 55

• Windows host requirements on page 55

54 Configuring the HPE 3PAR StoreServ Storage and host—FCoE

• VLAN configuration and routing setup on page 30

• HPE 3PAR Persistent Ports—FCoE on page 56

Target port limits and specifications—FCoETo 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 onthe SPOCK website (SPOCK Home > Other Hardware > 3PAR).

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

HBA Protocol Array Bus Speed Ports Max. QueueDepth

QLogicQLE8242

FCoE HPE 3PARStoreServ

7000, 10000

PCIe 10 Gbps 2 1748

QLogicQTH8362

FCoE HPE 3PARStoreServ

8000, 9000,20000

PCIe 10 Gbps 2 1748

Windows host requirementsThe Windows host must meet the CNA software requirements as seen in the individual 3PAR array FCoEconfiguration sets for Windows Server 2019, 2016, 2012, and 2008.

• To obtain CNA BIOS and firmware, see the Service Pack for ProLiant (SPP) website.

• To obtain CNA drivers, see the Hewlett Packard Enterprise Support Center website.

• To install the Emulex OCManager, the Qlogic QConvergeConsole Manager or Broadcom AdvancedControl Suite (BACS), see the Hewlett Packard Enterprise Support Center website.

For specific details on supported configurations, see the SPOCK website.

More information

http://www.hpe.com/servers/spphttp://www.hpe.com/support/hpeschttp://www.hpe.com/storage/spock

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

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

Configuring the HPE 3PAR StoreServ Storage and host—FCoE 55


http://www.hpe.com/servers/spp



• 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

HPE 3PAR Persistent Ports—FCoEThe HPE 3PAR Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HPE 3PARStoreServ Storage online upgrade, node-down or cable pull event. Port shutdown or reset events do nottrigger this feature.

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

HPE 3PAR Persistent Ports allow an HPE 3PAR StoreServ Storage FCoE 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 "Using Persistent Ports for Nondisruptive OnlineSoftware Upgrades" topic in the HPE 3PAR Command Line Interface Administrator’s Manual on the Hewlett Packard Enterprise Information Library website.

More information


HPE 3PAR Persistent Ports setup and connectivity guidelines—FCoEBeginning with HPE 3PAR OS 3.1.3:

• The HPE 3PAR Persistent Ports feature is supported for FCoE target ports (FCoE end-to-endconfigurations).

• The HPE 3PAR Persistent Ports feature is enabled by default for HPE 3PAR StoreServ Storage FCoEports during node-down events.

Follow the specific cabling setup and connectivity guidelines for HPE 3PAR Persistent Ports tofunction properly. Key elements for the HPE 3PAR Persistent Ports feature setup and connectivityare:

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

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

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





Connecting the HPE 3PAR StoreServ Storage to the host—FCoE

Setting up and zoning the fabric—FCoEFabric zoning controls which FCoE 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.

If you use an unsupported zoning configuration and an issue occurs, Hewlett Packard Enterprise mightrequire that you implement one of the supported zoning configurations as part of the corrective action.

NOTE:

• For high availability and clustered environments that require multiple initiators to access the same setof target ports, Hewlett Packard Enterprise recommends creating separate zones for each initiator withthe same set of target ports.

• Storage targets in the zone can be from either:

◦ The same HPE 3PAR StoreServ Storage system

◦ Multiple HPE 3PAR StoreServ Storage system

◦ A mixture of HPE 3PAR and other Hewlett Packard 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.

Employing fabric zoning using switch vendor methods (required)—FCoEEmploy fabric zoning by using the methods provided by the switch vendor to create relationships betweenhost HBA ports and HPE 3PAR StoreServ Storage ports before connecting either the host HBA ports orthe HPE 3PAR StoreServ Storage ports to the fabrics.

FCoE switch vendors support the zoning of the fabric end-devices in different zoning configurations.There are advantages and disadvantages with each zoning configuration. Select a zoning configurationthat best meets your needs.

For configuring HPE FlexFabric 5900 Switch settings for FCoE - FCoE connections refer to HPNetworking Single-Tier FC/FCoE Solution using HPE Rack Servers and HP Storage, document availableat www.hpe.com/h20195/v2/GetPDF.aspx/4AA5-5629ENW.pdf

Supported zoning configurations by the HPE 3PAR StoreServ Storage arrays—FCoE

• One initiator to one target per zone.

• One initiator to multiple targets per zone (zoning by HBA). Hewlett Packard Enterprise recommendsthis zoning configuration for the HPE 3PAR StoreServ Storage. Zoning by HBA is required forcoexistence with other Hewlett Packard Enterprise storage arrays.

Setting up fabric zoning—FCoE

Procedure

Set up fabric zoning by associating the device World Wide Names (WWNs) or the switch ports withspecified zones in the fabric. Use either the WWN method or the port zoning method with the HPE 3PAR


https://www.hpe.com/h20195/v2/GetPDF.aspx/4AA5-5629ENW.pdf

StoreServ Storage. Hewlett Packard Enterprise recommends the WWN zoning method as the zonesurvives changes of switch ports when moving cables in a fabric.

Verifying switch zoning and configurations—FCoE

• Complete the configuration of the storage port to the host and connect to the switch. For moreinformation, see Configuring the HPE 3PAR StoreServ Storage ports—FC.

• Create a zone configuration on the switch following the HPE SAN Design Reference Guide, and thenenable the zone set configuration.

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

Verifying switch zoning and configurations

After configuring, zoning, and connecting each host HBA port and HPE 3PAR StoreServ Storage port tothe fabrics, verify the following:

Procedure

Verify that each initiator is zoned with the correct targets by using the HPE 3PAR CLI showhostcommand.

Configuring the HPE 3PAR StoreServ Storage ports—FCoE

Planning to configure ports—FCoE

Procedure

1. If an iSCSI port is configured with an IP address or netmask, the configuration must be removedbefore it can be configured as an FCoE port. See Removing iSCSI port configuration—FCoE onpage 58.

2. If a port has previously been configured as an iSCSI port, change it to FCoE. See Changing an iSCSIconfigured port to FCoE on page 59.

3. If changing one port to an FCoE port, you must also change its port pair to be an FCoE port. Forexample, ports 0:3:1 and 0:3:2.

Removing iSCSI port configuration—FCoE

Procedure

Issue the following CLI command:


cli % controliscsiport delete -f <n:s:p>

Changing an iSCSI configured port to FCoE

Procedure

1. Run the showport command:

cli % showport

0:3:1 target ready - 000E1E05BEE6 iscsi iSCSI - - -0:3:2 target ready - 000E1E05BEE2 iscsi iSCSI - - -

2. Turn off the iSCSI ports:

cli % controlport offline 0:3:1cli % controlport offline 0:3:2cli % showport

0:3:1 target offline - 000E1E05BEE2 iscsi iSCSI0:3:2 target offline - 000E1E05BEE2 iscsi iSCSI

3. Change the topology to FCoE:

cli % controlport config fcoe 0:3:1cli % controlport config fcoe 0:3:2cli % controlport rst 0:3:1cli % controlport rst 0:3:2

0:3:1 target offline - 000E1E05BEE2 iscsi iSCSI0:3:2 target offline - 000E1E05BEE2 iscsi iSCSI

cli % showport

0:3:1 target ready 2FF70002AC000121 20310002AC000121 host FCoE - - -0:3:2 target ready 2FF70002AC000121 20320002AC000121 free FCoE - - -

4. Check the current settings of the FCoE ports by issuing showport -fcoe. For example:

cli % showport -fcoe

N:S:P ENode_MAC_Address PFC_Mask0:3:1 00-02-AC-07-01-21 0x080:3:2 00-02-AC-06-01-21 0x00


Configuring the HPE 3PAR StoreServ Storage ports—FCoE

Procedure

1. CNA ports on HPE 3PAR StoreServ 20000, 10000, 8000, and 7000 Storage arrays require a one-timeconfiguration by using the controlport command. (HPE 3PAR T-Class, and F-Class arrays do notsupport the CNA HBA.) For example, on a new FCoE configuration:

cli % showport

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

cli % showport -i

N:S:P Brand Model Rev Firmware Serial HWType0:3:1 QLOGIC QLE8242 58 0.0.0.0 PCGLT0ARC1K3U4 CNA0:3:2 QLOGIC QLE8242 58 0.0.0.0 PCGLT0ARC1K3U4 CNA

2. If State=config_wait or Firmware=0.0.0.0, use the controlport config fcoe <n:s:p>command to configure. Use the showport and showport -i commands to verify the configurationsetting. For example:

cli % controlport config fcoe 0:3:1cli % controlport config fcoe 0:3:2cli % showport 0:3:1 0:3:2

N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState0:3:1 target ready 2FF70002AC000121 20310002AC000121 host FCoE - - -0:3:2 target ready 2FF70002AC000121 20320002AC000121 free FCoE - - -

cli % showport -i 0:3:1 0:3:2

N:S:P Brand Model Rev Firmware Serial HWType0:3:1 QLOGIC QLE8242 58 4.11.122 PCGLT0ARC1K3U4 CNA0:3:2 QLOGIC QLE8242 58 4.11.122 PCGLT0ARC1K3U4 CNA

3. Check the current settings of the FCoE ports by issuing showport -fcoe. For example:

cli % showport -fcoe

N:S:P ENode_MAC_Address PFC_Mask0:3:1 00-02-AC-07-01-21 0x080:3:2 00-02-AC-06-01-21 0x00

Creating the host definition—FCoETo create the host definition, follow the procedure in Creating a host definition—FC on page 17.

Configuring the host—FCoEStarting with HPE 3PAR OS 3.2.1, FCoE target support was extended to include Windows Server 2008and Windows Server 2008 R2.


Starting with HPE 3PAR OS 3.1.3, FCoE target support was added for Windows Server 2012 andWindows Server 2012 R2.

Starting with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5,, FCoE target support was added for WindowsServer 2016.

For more information about supported configurations, see the SPOCK website.

The following topics describe setting up a Windows Fibre Channel over Ethernet (FCoE) configurationwith an HPE 3PAR StoreServ Storage. These instructions cover both end-to-end FCoE and FCoE initiatorto FC target.

More information


Configuring the switch—FCoEConnect the Windows (FCoE initiator) host ports and HPE 3PAR StoreServ Storage (FCoE target) portsto an FCoE-enabled switch.

Procedure

Using system BIOS to configure FCoE:

1. Launch the setup menu. The combination of keys for launching setup might be different depending onthe host being configured.

2. In the System Options pane, select NIC Personality Options.

3. In the PCI Slot 2 Pane, select FCoE for both Port 1 and Port 2.




4. PCI Slot 2 Port 1 and Port 2 now display FCoE.

5. Save the changes and exit the BIOS.

Using the Emulex CNA—FCoE

Preparing to use the Emulex CNA Driver—FCoE

Procedure

1. Choose between either the Emulex OOB (Out of Box) driver or the inbox driver.

Hewlett Packard Enterprise recommends either the Emulex OOB (Out of Box) driver or the inboxdriver provided in the base OS. To download the Emulex OOB driver, see the Hewlett PackardEnterprise Support Center website.

2. Look up the supported drivers.For a list of supported drivers, see the SPOCK website (SPOCK Home > Explore StorageInteroperability With SPOCK > Explore HPE 3PAR StoreServ Storage interoperability > Explore3PAR Block Persona interoperability).


Configuring FCoE host personality—Emulex CNA

Procedure

1. Using the system BIOS, configure FCoE. In the following example, the Setup menu was opened bypressing F9.

Figure 4: Configuring FCoE

2. Select System Options, and then select NIC Personality Options.


Figure 5: NIC Personality options

3. For PCI Slot 2, select FCoE for both Port 1 and Port 2.


Figure 6: Configuring the PCI Slot 2

4. Now PCI Slot 2 for Port 1 and Port 2 have been set to FCoE.


Figure 7: PCI Slot 2 Port 1 and Port 2

5. Save the changes, and then exit the BIOS.


Figure 8: Exiting the BIOS utility

SAN Boot Configuration:

If you are setting up the FCoE host to boot from the HPE 3PAR StoreServ Storage, complete the tasks in Booting the host from the HPE 3PAR StoreServ Storage before returning here to complete the rest ofthe tasks.

Using the QLogic CNA—FCoE

Preparing to use the QLogic CNA driver—FCoE

Procedure

1. Choose between either the QLogic OOB (Out of Box) driver or the inbox driver.

Hewlett Packard Enterprise recommends either the QLogic OOB (Out of Box) driver or the inbox driverprovided in the base OS. To download the QLogic OOB driver, see the Hewlett PackardEnterprise Support Center website.

2. Look up the supported drivers.For a list of supported drivers, see the SPOCK website (SPOCK Home > Explore StorageInteroperability With SPOCK > Explore HPE 3PAR StoreServ Storage interoperability > Explore3PAR Block Persona interoperability).


Configuring the FCoE host personality—QLogic CNA

Procedure

1. When the QLogic BIOS message appears, press Ctrl+S.

Figure 9: ProLiant QLogic BIOS message

2. The Comprehensive Configuration Management window appears.

3. Select the appropriate device.


Figure 10: Select the appropriate device

4. Select Device Hardware Configuration.

Figure 11: Select Device Hardware Configuration

5. Set Storage Personality to FCoE.


Figure 12: Set Storage Personality to FCoE

6. If Multi-Function Mode is enabled in your CCM (comprehensive configuration management) version,choose either SF (Single Function) or NPAR1.5 (NIC Partitioning) mode. For more information, seethe NPARs Configuration for HPE Network Adapters User Guide at the Hewlett Packard EnterpriseSupport Center website: www.hpe.com/support/hpesc

SAN Boot Configuration:

If you are setting up the FCoE host to boot from the HPE 3PAR StoreServ Storage, complete the tasks in Booting the host from the HPE 3PAR StoreServ Storage before returning here to complete the rest ofthe tasks.

Configuring FCoE initiator to FC target

NOTE: For complete and detailed instructions for configuring a server with a given Converged NetworkAdapter, see the CNA manufacturer documentation.

After the initiators are logged in to the HPE 3PAR StoreServ Storage target ports, the next processes willbe to create a host definition and provision storage to the host.

If an FCoE to FC configuration is set up, this diagram summarizes the general steps for configuring aCNA and FCoE Forwarder Switch:



Figure 13: Initiator FCoE to FC Target

Prerequisites

The FCoE switch or FCoE forwarder must be able to convert FCoE traffic to FC and be able to trunk thistraffic to the fabric where the HPE 3PAR StoreServ Storage target ports connect.

Procedure

1. Install the CNA card in the server similar to installing a PCIe card. See the server vendordocumentation for specific instructions.

2. Install the CNA card driver following the CNA card installation instructions. (Prerequisite: The serveris already running a supported OS.)

3. Physically connect the server CNA card ports to the FCoE Forwarder switch, and then configure theFCoE Forwarder switch ports. See the switch vendor documentation.

NOTE: It is not possible to connect a server with a CNA directly to the HPE 3PAR StoreServ Storage.An FCoE Forwarder switch must be used.

4. Configure the HPE 3PAR StoreServ Storage ports. See Configuring the HPE 3PAR StoreServStorage and host—FC on page 9.

5. Connect the HPE 3PAR StoreServ Storage port either to the FCoE Forwarder FC switch ports or theFC fabric connected to the FCoE Forwarder.

6. Create FC zones for the ports of host initiator and the HPE 3PAR StoreServ Storage target port.

Configuring FCoE initiator to FCoE targetIf an FCoE to FCoE configuration is set up, this diagram summarizes the general steps for configuring aCNA and FCoE Forwarder Switch:


Figure 14: Initiator FCoE to Target FCoE

After the initiators are logged in to the HPE 3PAR StoreServ Storage target ports, the next processes willbe to create a host definition and provision storage to the host.

Prerequisites

Configure HPE 3PAR StoreServ Storage ports for FCoE. See Configuring the HPE 3PAR StoreServStorage and host—FCoE on page 54.

Procedure

1. Install the CNA card in the server just like any other PCIe card. See the server vendor documentation.

2. Install the CNA card driver following the CNA card installation instructions. (Prerequisite: The serveris already running a supported OS.)

3. Physically connect the server CNA card ports to the FCoE fabric.

4. Configure the HPE 3PAR StoreServ Storage ports. See Configuring the HPE 3PAR StoreServStorage and host—FC on page 9.

5. Connect the HPE 3PAR StoreServ Storage ports to the FCoE fabric.

6. Create VLANs for the ports of host initiator and the HPE 3PAR StoreServ Storage target port.


Windows Hyper-V Server/HPE 3PARStoreServ Storage configuration

The following topics refer to a server with an x64-based processor running an x64 version of WindowsServer:







For details on Hyper-V operation, see the specific documentation on the Microsoft website.

Required: A hotfix, available from Microsoft, is required to support live storage migrations with WindowsServer 2012 using Cluster Shared Volumes on HPE 3PAR OS 3.1.2 and later. The hotfix must be appliedbefore updating the HPE 3PAR StoreServ Storage.

For more information about the required hotfix, see the Windows Server 2012 SPOCK configuration onthe SPOCK website.

More information


Hyper-V software installationHyper-V software is installed by installing the Hyper-V Role from the Server Manager.

For system requirements and known issues, search the Microsoft website for the Hyper-V Server GettingStarted Guide for your version of the Hyper-V software. Follow the steps explained there to install theHyper-V management tool, create, and set up a virtual machine, install the operating system andintegration services, and configure virtual networks.

Hyper-V software configurationSearch the Microsoft website for the Microsoft Hyper-V Server Setup and Configuration documentation foryour version of the Hyper-V software, and then follow those setup and configuration instructions.

NOTE: No particular parameters must be set in the Hyper-V software to work with the HPE 3PARStoreServ Storage. No additional steps are necessary on the HPE 3PAR StoreServ Storage to work witha Windows Hyper-V Server.

Windows Hyper-V Server/HPE 3PAR StoreServ Storage configuration 73



Allocating storage for the hostProcedure

1. Use the following command:

fsutil behavior set disabledeletenotify 1

This command disables the delete notifications for all volumes behavior. If you do notrun this command, it will take longer to complete the format operation, and the Disk Management utilitymay become unresponsive if you attempt to interrupt any pending format operations.

2. When all outstanding format operations are successfully complete, run the following command to re-enable the delete notifications for all volumes behavior:

fsutil behavior set disabledeletenotify 0

Creating storage on the HPE 3PAR StoreServ StorageThe 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 more 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 on the Hewlett Packard Enterprise Information Library website.

More information


Virtual volumes creationVirtual volumes (VVs) are the only data layer visible to hosts. After setting up a plan for allocating spacefor hosts on the HPE 3PAR StoreServ Storage, create the VVs for eventual export as LUNs to theWindows Server host.

Create volumes that are provisioned from one or more common provisioning groups (CPGs). Volumescan be fully provisioned, thinly provisioned, thinly deduplicated, or thinly compressed. Optionally, specify aCPG for snapshot space for provisioned volumes.

Thinly provisioned deduplicated virtual volumes

With HPE 3PAR OS 3.2.1 MU1 and later, the HPE 3PAR Thin Deduplication feature is supported. ToTDVVs, an HPE 3PAR Thin Provisioning license is required.

HPE 3PAR Thin Deduplication allows the creation of TDVVs from solid-state drive (SSD) CPGs. A TDVVhas the same characteristics as a TPVV, but with the added capability of removing duplicated data beforeit is written to the volume. The TDVVs are managed like any other TPVV. A TDVV must be associatedwith CPGs created from an SSD.

NOTE: For Windows Server hosts, Hewlett Packard Enterprise recommends setting the default NTFS filesystem allocation size to 16 KB when creating NTFS file systems on TDVVs. This ensures capacityefficiency on the volumes.

For information about creating volumes for the HPE 3PAR OS version on the HPE 3PAR StoreServStorage, see the following documents on the Hewlett Packard Enterprise Information Library website:

74 Allocating storage for the host



http://h17007.www1.hpe.com/us/en/storage/info-library/index.aspx

• HPE 3PAR StoreServ Storage Concepts Guide

• HPE 3PAR Command Line Interface Administrator’s Manual

• HPE 3PAR Command Line Interface Reference

NOTE: The commands and options available for creating a VV might vary for earlier HPE 3PAR OSversions.

Creating virtual volumes—HPE 3PAR MC 4.7To create a virtual volume in the HPE 3PAR Management Console, access the Create Virtual Volumewizard. This wizard allows you to create Thinly Deduped, Thinly Provisioned, and Fully Provisionedvolumes.

For more information, see the HPE 3PAR Management Console 4.7 User Guide on the Hewlett PackardEnterprise Information Library website.

Procedure

1. In the Manager Pane, select Provisioning.

2. In the Common Actions pane, click Create Virtual Volume.

The Create Virtual Volume wizard appears.

Creating virtual volumes—HPE 3PAR SSMC 3.4

Procedure

1. On the main menu, select Block Persona > Virtual Volume.

2. Click + Create virtual volume or select Actions > Create.

3. Select Fully Provisioned or Thin Provisioned.

4. If applicable, select Dedup (supported with HPE 3PAR OS 3.2.1 MU1 and later) or Compression(supported with HPE 3PAR OS 3.3.1 and later).

Creating virtual volumes—HPE 3PAR CLIThe createvv command creates volumes that are provisioned from one or more common provisioninggroups. Volumes can be fully provisioned from a CPG or can be thinly provisioned. Users can optionallyspecify a CPG for snapshot space for fully provisioned volumes and thinly provisioned volumes.

For more information, see the HPE 3PAR OS Command Line Interface Reference on the HewlettPackard Enterprise Information Library website.

Procedure

Create a fully provisioned or TPVV using the syntax:

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

For example:

Allocating storage for the host 75





cli % createvv -cnt 5 testcpg TESTLUNS 5g

More information


Exporting VLUNs to the hostFollow the instructions for creating virtual volumes (VVs) and virtual LUNs (VLUNs) in the HPE 3PARCommand Line Interface Administrator Guide on the Hewlett Packard Enterprise Information Librarywebsite.

Starting with HPE 3PAR OS 3.3.1, the maximum volume size has changed. For details, see the HPE3PAR StoreServ Storage Concepts Guide and the HPE 3PAR OS 3.3.1 Release Notes on the HewlettPackard Enterprise Information Library website.

Observe the following guidelines:

• This configuration supports sparse LUNs, meaning that LUNs might be skipped. LUNs might also beexported in nonascending order such as 0, 5, 7, 3.

• Windows Server registers only LUNs 0 to 255, but the HPE 3PAR StoreServ Storage can export LUNs0 to 65535. There are restrictions on the maximum number of LUNs supported when MPIO is used onthe host and the LUNs are presented to the Hyper-V virtual machines. For more information, see theMicrosoft Windows documentation.

• For FC, Windows can recognize up to 254 LUN IDs per target.

• For iSCSI, Windows can recognize up to 256 LUN IDs per target.

Discovering LUNsFor Windows Server 2008/2012/2016/2019, use the Server Manager to display information on the disks,or use the OCManager or QConvergeConsole GUI to discover devices.

Procedure

Using the Server Manager, click Storage, and then click Disk Management. For example:






You can also use the Emulex OCManager or QLogic QConvergeConsole to discover devices.

Scanning for new devices on a Windows Server hostDisk devices on Windows servers can be used as basic disks or dynamic disks. The HPE 3PARStoreServ Storage already provides most of the extra capabilities of dynamic disks. Hewlett PackardEnterprise strongly recommends that HPE 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 HPE 3PAR StoreServStorage Virtual Copy feature, or break a Windows mirrored set of disks created on two discreteHPE 3PAR StoreServ Storage volumes.

For information about dynamic disks with a Windows Server, see the following Microsoft website:

http://technet.microsoft.com/en-us/library/dd163552.aspx

When VLUNs are exported to the Windows Server, they might not appear in the Windows Disk Managerautomatically. After a new VLUN is exported from an HPE 3PAR StoreServ Storage iSCSI port, issue arescan from Windows Disk Manager or Windows Device Manager.

NOTE: Verify that Windows Disk Manager is closed while you are exporting LUNs, and then wait until theWindows Device Manager shows all the new LUN exports before opening the Windows Disk Manager.Once all LUNs show as available in the Windows Device Manager, it is safe to proceed to the WindowsDisk Manager to initialize and create disk partitions.


http://technet.microsoft.com/en-us/library/dd163552.aspx

Procedure

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

1. In the Windows Server Manager window, click Device Manager.

2. Right-click Disk drives.

3. In the popup that appears, select Scan for hardware changes.

Removing a storage volume from the Windows Serverhost

To remove a storage volume from the Windows Server host, follow the standard Microsoft administrativeprocedures for removing a volume, and follow the HPE 3PAR StoreServ Storage standard procedure forremoving a volume.

NOTE: Removing a disk from a Windows Server host does not erase the data on the disk. Considerusing a third-party utility that erases the data on the disk before removing it from the Windows Serverhost.

SCSI UNMAP primitive support for Windows Server2019/2016/2012

HPE 3PAR OS 3.1.1 introduced support for the UNMAP storage primitive (opcode 42h) which issupported by Windows Server 2012 and later with the NTFS file system. UNMAP causes the HPE 3PARStoreServ Storage to reclaim storage space on a thinly provisioned virtual volume (TPVV), includingdeduplicated and compressed virtual volumes, when data or files are deleted on a supported file system


type. This feature is useful in maintaining the volume as a thin volume with no storage disk spaceallocated for files that are deleted.

NOTE: Currently, the Windows Server 2016, Windows Server 2012, and Windows Server 2012 R2Resilient Filesystem (ReFS) does not support UNMAP primitive on thinly provisioned LUNs.

ODX support for Windows Server 2019, Windows Server2016, Windows Server 2012, and Windows Server 2012 R2

HPE 3PAR OS 3.1.2 introduces support for offloaded data transfer (ODX), which is supported byWindows Server 2019, Windows Server 2016, Windows Server 2012, and Windows Server 2012 R2 withthe NTFS file system.

Starting with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5, ODX is supported by Windows Server 2016.

In a traditional file transfer/copy operation between two LUNs on the same storage array, buffered-readand buffered-write operations are used on the host to complete the request. With arrays that supportODX, supported Windows versions can complete the request by offloading the file transfer to the storagearray. ODX minimizes latencies, maximizes array throughput, and reduces resource usage such as CPUand network consumption on the host. When you move or copy files, Windows Server offloads filetransfers transparently and automatically, regardless of whether you drag and drop files through FileExplorer or use the command-line file copy commands.

For more information about ODX, see the Microsoft website technet.microsoft.com/en-us/library/hh831628.aspx.


http://technet.microsoft.com/en-us/library/hh831628.aspx

http://technet.microsoft.com/en-us/library/hh831628.aspx

Booting the host from the HPE 3PARStoreServ Storage

For details about connecting the HPE 3PAR StoreServ Storage to the host, see Configuring the HPE3PAR StoreServ Storage and host—FC on page 9.

Configuring for iSCSI SAN bootHardware iSCSI SAN Boot is supported on added Windows Server 2019, Windows Server 2016,Windows Server 2012 and Windows Server 2008 R2 SP1 with HPE 3PAR StoreServ 20000, 10000,9000, 8000, and 7000 Storage systems.

For more information about supported configurations, see the SPOCK website.

NOTE: For SAN boot with hardware iSCSI using Emulex CNAs, do not use a LUN ID higher than 4 as theboot LUN. This setting is a requirement of the Emulex BIOS. Failing to do this action may result in thehost issues when attempting to SAN boot.

For more information, see vendor-specific documentation.

For configurations that have iSCSI connections on Windows Server 2008, the Double-Take Flex softwareis required.

NOTE: iSCSI SAN Boot using Double-Take Flex software is not supported on Windows Server 2012,Windows Server 2016, or Windows Server 2019.

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 an HPE 3PAR StoreServStorage boot with FC storage.

More information


Configuring the BIOS for FC SAN bootThis topic explains specific host HBA settings required for booting from an HPE 3PAR StoreServ Storagein a fabric configuration. Use the Boot BIOS version listed on the SPOCK website.

To obtain a copy of this documentation, go to the Hewlett Packard Enterprise Support Center website.

NOTE: With the introduction of the Microsoft Storport driver, booting from a Storage Area Network (SAN)has become less problematic. See the Microsoft support document Support for booting from a StorageArea Network (SAN), available at support.microsoft.com/kb/305547.

More information


80 Booting the host from the HPE 3PAR StoreServ Storage




https://support.hpe.com/hpesc/public/home

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



Configuring for an HPE 3PAR StoreServ Storage boot—Emulex HBA

Procedure

1. Boot the Windows Server system following the instructions in the BootBios update manual.

2. Press Alt+E.

For each Emulex adapter, set the following parameters:

a. Select Configure the Adapter's Parameters.

b. Select Enable or Disable the BIOS. For SAN boot, ensure that the BIOS is enabled.

c. Press Esc to return to the previous menu.

d. Select Auto Scan Setting; set the parameter to First LUN 0 Device. To return to the previousmenu, press Esc .

e. Select Topology.

f. Select Fabric Point to Point for fabric configurations.

g. Select FC-AL for direct connect configurations.

3. To return to the previous menu to set up other adapters, press Esc.

4. When you are finished, press x to exit and restart.

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

Procedure

1. Boot the Windows Server host, and as it is booting, press the Alt+Q or Ctrl+Q keys when the HBABIOS 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 or 1 for fabric

NOTE: Record the Adapter Port Name WWPN for creating the host definition. See Creating the hostdefinition for an HPE 3PAR StoreServ Storage boot—FC on page 82.

5. To exit this window, press Esc .

6. Click Selectable Boot Settings. In the Selectable Boot Settings window, set Selectable BootDevice to Disabled.

Booting the host from the HPE 3PAR StoreServ Storage 81

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 an HPE 3PAR StoreServStorage boot—FC

Procedure

1. To create the host definition for booting from the HPE 3PAR StoreServ Storage, use the createhost-persona 15 <hostname> [<WWN>...] command.

For example:

cli % createhost -persona 15 windowshost 10000000C9606724

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

cli % showhostId Name Persona -------------WWN/iSCSI_Name------------- Port 0 windowshost WindowsServer 10000000C9606724 ---

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

For FC HBAs on a Windows Server host, you do not need to set any SAN boot parameters, except forthose described in Installing and configuring a QLogic HBA—FC on page 20.

Assigning LUNs as the boot volumeThe Windows Server host must use a LUN as the boot volume for an FC SAN boot.

Procedure

To assign a LUN as the boot volume, follow these steps:

1. On the HPE 3PAR StoreServ Storage, create a VV of appropriate size.

2. Export it to the Windows Server host. For details, see Exporting VLUNs to the host on page 76. TheBoot LUN must be the lowest-ordered LUN number that exports to the host.

3. Restrict the host to a single path connection to the HPE 3PAR StoreServ Storage. Only a single pathmust be available on the HPE 3PAR StoreServ Storage and a single path on the host to the VLUN thatwill be the boot volume.

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

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

82 Booting the host from the HPE 3PAR StoreServ Storage

Procedure

1. It is recommended that the connection between the HPE 3PAR StoreServ Storage and the WindowsServer host system must be a single-path connection.

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

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

Connecting multiple paths for FC SAN bootAfter the Windows Server host completely boots up and is online, connect additional paths to the fabric orthe HPE 3PAR StoreServ Storage system directly by completing the following tasks.

Procedure

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

2. On the Windows Server host, rescan for devices. See Scanning for new devices on a WindowsServer host on page 77.

3. Restart the Windows Server system.

Booting the host from the HPE 3PAR StoreServ Storage 83

Configuring additional HPE3PAR softwarefeatures

This topic describes configuration of the following software features:

• HPE 3PAR All Flash Arrays on page 84

• HPE 3PAR Peer Motion, Online Import, and Storage Federation on page 85

• HPE 3PAR Peer Persistence on page 86

• HPE 3PAR File Persona on page 87

HPE 3PAR All Flash ArraysStarting 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 HPE 3PAR StoreServ: optimized for flashtechnical white paper on the Hewlett Packard Enterprise Information Library website.

84 Configuring additional HPE3PAR software features


NOTE:

• Windows Server (2012/2016/2019) hosts will identify various volume provisioning and file systemtypes as different "Media Types" in the "Optimize Drives" menu and will exhibit varying behavior afteroptimization. The following table designates the "Media Type" in the "Optimize Drives" menu and theexpected status after optimization:

Filesystem Type ProvisioningType

"OptimizeDrives" MediaTypeIdentificationWindows 2012R2and 2016/2019

Status AfterOptimizationWindows 2012R2

Status AfterOptimizationWindows2016/2019

NTFS Thin Provisioned Thin ProvisionedDrive

OK OK

ReFS Thin Provisioned Thin ProvisionedDrive

Optimization notavailable

OK

NTFS Full Provisioned Solid-State Drive Optimization notavailable


ReFS Full Provisioned Solid-State Drive Optimization notavailable


• For volumes on All Flash Arrays, executing a utility or command which defragments or attempts tooptimize data placement should be avoided. Such actions unnecessarily contribute to solid-state drive(SSD) device wear. Unlike spinning media, an SSD device inherently has no rotational latency and,therefore, defragmentation or optimization provides no benefit. As to whether data managementcommands recognize SSD devices, consult the documentation or the vendor for your host OS andadjust their behavior accordingly.

• SSD devices do not benefit from optimization and contribute to SSD device wear.

HPE 3PAR Peer Motion, Online Import, and StorageFederation

The HPE 3PAR StoreServ Storage supports data migration from one HPE 3PAR StoreServ Storage toanother HPE 3PAR StoreServ Storage. It also supports data migration from other, supported Storagearrays to the HPE 3PAR StoreServ Storage through Peer Motion and Online Import.

Beginning with HPE 3PAR OS 3.2.2, HPE 3PAR Peer Motion with Bidirectional Multi-Array FederatedStorage has been introduced and allows the creation of a multi-array, bidirectional peer motion federation.

Configuring additional HPE3PAR software features 85

CAUTION: Before performing Unidirectional or Bidirectional Peer Motion migrations, Path VerifyEnabled needs to be set in the MPIO settings on Windows Server configured hosts.

To configure the Path Verify Enabled MPIO setting:

• On Windows Server 2019/2016/2012, the setting can be found at Device Manager > DiskDrives. Right-click any of the HPE 3PAR disks, select Properties > MPIO > MS DSM Details,and then select the Path Verify Enabled check box.

• On Windows Server 2008, the setting can be found at Server Manager > Disk Management.Right-click any of the HPE 3PAR disks, select Properties > MPIO > MS DSM Details, and thenselect the Path Verify Enabled check box.

For additional information about HPE 3PAR Peer Motion and HPE 3PAR Online Migration, see the HPE3PAR Peer Motion and HPE 3PAR Online Import User Guide on the Hewlett Packard EnterpriseInformation Library website.

More information


HPE 3PAR Peer PersistenceHPE 3PAR Peer Persistence enables HPE 3PAR StoreServ Storage systems, located at metropolitandistances, to act as peers to each other, presenting a nearly continuous storage system to hosts andservers connected to them. This capability allows customers to configure a high-availability solutionbetween two sites or data centers, where switchover, failover, and switchback remain transparent to thehosts and applications or virtual machines running on those hosts.

For a complete description of the HPE 3PAR Peer Persistence feature and how to configure HPE 3PARStoreServ Storage for HPE 3PAR Peer Persistence with automatic transparent failover and manualtransparent switchover, see the HPE 3PAR Remote Copy Software User Guide on the Hewlett PackardEnterprise Information Library website.

For information about supported HPE 3PAR Peer Persistence configurations for Windows andexceptions, see the 3PAR Peer Persistence Host OS Support Matrix on the SPOCK website (SPOCKHome > Software > Array SW: 3PAR.

For information about supported hardware and software platforms, see the HPE 3PAR StoreServ StorageInteroperability for Windows (2008/2012/2016/2019) on the SPOCK website (SPOCK Home > Explore3PAR StoreServ Storage Interoperability > Explore 3PAR Block Persona interoperability).







NOTE:

• Host Windows Server persona (persona 15), which enables asymmetric logical unit access (ALUA),is required for Windows hosts configured as part of HPE 3PAR Peer Persistence configurations.

• Path Verify Enabled must be set in the MPIO settings on Windows Server hosts configured for anHPE 3PAR Peer Persistence implementation.

To configure the Path Verify Enabled MPIO setting:◦ With Windows Server 2019/2016/2012, the setting can be found at Properties > Device

Manager > Disk Drives. Right-click any of the HPE 3PAR disks, select MPIO > MS DSM Details,and then select the Path Verify Enabled check box.

◦ With Windows Server 2008, the setting can be found at Properties > Server Manager > DiskManagement. Right-click any of the HPE 3PAR disks, select MPIO > MS DSM Details, and thenselect the check box.

• Verify that MPIO LB (Load Balancing) Policy is set (changed) to Round Robin with Subset (RRWS) forthe VVs which are part of Peer Persistence configuration.

To Verify the LB Policy set with Windows Server 2019/2016/2012, the setting can be found atComputer Management > Storage > Disk Management. Right-click on any of the HPE 3PAR disks,select Properties > MPIO > MPIO Policy.

• Configuration of Windows hosts for HPE 3PAR Peer Persistence must follow the HPE 3PARMicrosoft Windows Server Implementation Guide.

More information:

www.hpe.com/info/storage/docs

www.hpe.com/storage/spock

More information

http://www.hpe.com/info/storage/docshttp://www.hpe.com/support/hpesc

HPE 3PAR File PersonaStarting 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 the SPOCK website (SPOCK Home > Explore Storage Interoperability With SPOCK > Explore 3PARStoreServ Storage interoperability > Explore 3PAR File Persona interoperability).

For more information about the HPE 3PAR File Persona software, including required setup andguidelines, see the HPE 3PAR File Persona User Guide on the Hewlett Packard Enterprise InformationLibrary website.

More information












Mounting SMB file shares in File Services using CLI commands

Procedure

1. Configure the IP interfaces on the host.

For instructions, see the Windows Server documentation for the deployed version of Windows.

NOTE: The requirements for configuring Windows Server clients to use File Services provided by theHPE 3PAR StoreServ Storage are the same as the requirements for other network file systems. Formore information about configuring hosts, see the Microsoft Windows documentation.

2. Look up the IP address of the Virtual File Server created in File Services by using the showvfscommand.

cli% showvfs

VFS FPG IPAddr State -Comment-vfs12 fpg12 10.10.1.115 normal -vfs11 fpg11 10.10.1.114 normal -vfs02 fpg02 10.10.1.113 normal -------------------------------------- 3 total

3. Look up the name of the SMB share you are mapping by using the showfshare smb -d command.

In this example, the SMB Share Name = fshare11, File Provisioning Group = fpg11, Virtual File Server= vfs11, File Store = fstore11, and Share Directory Path = sharedir11 were created in File Services.Share Name indicates the name to use to map the share.

cli% showfshare smb -d

Share Name : fshare11File Provisioning Group : fpg11Virtual File Server : vfs11File Store : fstore11Share Directory Path : ./sharedir11State : normalAccess Based Enumeration : falseAllow User Permissions : Everyone:fullcontrolDeny User Permissions : ---Allow Client IPs : ---Deny Client IPs : ---Client-Side Caching State : manualContinuous Availability : trueComment : --- -File access audit SMP options-None.

4. On Windows Clients, map the SMB file shares in File Services using the CLI commands.



C:\net use Z: \\10.10.1.114\fshare11 [/user:[domainname\]username] [{password | *}]] [/persistent:{yes | no}]


Using failover clustering in a virtualizedenvironment

The HPE 3PAR StoreServ Storage supports failover clustering in some VMware ESX/ESXi virtualizedenvironments as guest OS clustering. For setup and configuration purposes, this type of environment isconsidered a VMware ESX/ESXi configuration.

ESX/ESXi host servers must be set up as described in the HPE 3PAR VMware ESX/ESXi ImplementationGuide on the Hewlett Packard Enterprise Information Library website.

For more information about the configuration of a Windows Server failover cluster within a set of virtualmachines on VMWare ESX/ESXi hypervisor, see the latest VMware KBs.

More information


90 Using failover clustering in a virtualized environment



Using failover clustering with Microsoft MPIOThe HPE 3PAR StoreServ Storage supports failover clustering.

Procedure

Set up the cluster according to Microsoft recommendations.

Using failover clustering with Microsoft MPIO 91

Using the Veritas Cluster ServerVeritas Storage Foundation

Veritas Storage Foundation (SF) 5.1 SP1, SP2, and SF 6.0.x have a space-reclamation feature to reclaimspace from a thinly provisioned virtual volume (TPVV). When working with a failover cluster and VxDMP,this feature is not supported, as a failover cluster requires basic disks, and the space reclamation featureis available only on dynamic 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 the HPE3PAR StoreServ Storage

NOTE: This topic applies only to systems using Windows Server 2008 non-R2 operating systems withVeritas 5.1 GA.

Procedure

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 the Symantec website:

https://sort.veritas.com/asl

2. Save the DDI to a folder.

3. Extract the DDI files.

4. Verify the HPE 3PAR enable/disable script:

92 Using the Veritas Cluster Server

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

DisableSupportSCSI3V3paraa & EnableSupportSCSI3V3paraa

5. By default, the HPE 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

6. To enable HPE 3PAR SCSI-3 support, click the EnableSupportSCSI3V3paraa script, and then restartthe server after the script runs.

7. After the script runs, the HPE 3PAR Support SCSI-3 appears as 0x00000000 (1) in the Datacolumn.

8. To verify the new settings, open the Veritas Enterprise Administrator (VEA) .

Using the Veritas Cluster Server 93

94 Using the Veritas Cluster Server

Using Microsoft Clustering with Veritas DMPInstalling Veritas DMP

CAUTION: In Windows Server 2003 R2 SP1 installations, Veritas Storage Foundation 5.1 & VeritasStorage Foundation HA 5.1 require the use of 8-byte long WWNs on every virtual volume exportedfrom a 3PAR StoreServ Storage array to the Windows Server host. Using 16-byte long WWNsinstead with the previous Veritas Storage Foundation version may prevent the Veritas StorageFoundation software from 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. Note thattestvv1 has a 16-byte WWN assigned against it whereas testvv2 has an 8-byte long WWN.

# showvv -dId 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

The command assumes that 50002AC003D885E4 is the newly assigned WWN and testvv is the nameof the 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 theoutput.

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

Using Microsoft Clustering with Veritas DMP 95

96 Using Microsoft Clustering with Veritas DMP

WebsitesGeneral websitesHewlett Packard Enterprise Information Library

www.hpe.com/info/EILSingle Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix

www.hpe.com/storage/spockStorage white papers and analyst reports

www.hpe.com/storage/whitepapers

For additional websites, see Support and other resources.

Websites 97

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


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

Support and other resourcesAccessing 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 Centerwebsite:


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 tothe Hewlett Packard Enterprise Support Center More Information on Access to Support Materialspage:

www.hpe.com/support/AccessToSupportMaterials

98 Support and other resources

http://www.hpe.com/assistance



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

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

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

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

IMPORTANT: Access to some updates might require product entitlement when accessed throughthe Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up withrelevant entitlements.

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 information for your product, see the links provided below:

HPE ProLiant and IA-32 Servers and Optionswww.hpe.com/support/ProLiantServers-Warranties

HPE Enterprise and Cloudline Serverswww.hpe.com/support/EnterpriseServers-Warranties

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

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

Support and other resources 99

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/ProLiantServers-Warranties

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

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

http://www.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.

100 Support and other resources

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 Microsoft Windows Server Implementation Guide · Beginning with HPE 3PAR OS 3.2.2 MU3 and 3.2.1 MU5, FCoE target support was added for Windows Server 2016. Beginning with

Documents