HP 3PAR Windows Server 2008 and Windows Server 2012 Implementation Guide

HP 3PAR Windows Server 2008 and
Windows Server 2012 Implementation

Guide
Abstract
This implementation guide provides the information needed to configure the HP 3PAR Storage System with Microsoft® Windows®
Server 2008 or Windows Server 2012. Unless otherwise noted, information in the guide applies to servers running the Windows
Server 2012 operating system, to servers running the Windows Server 2008 operating system with Service Pack 1 (SP1) and
Service Pack 2 (SP2) on both x86 (32–bit) and x64 (64-bit) architectures, and to servers running Windows Server 2008 R2
on x64 (64-bit) architecture only.
HP Part Number: QL226-96705

Published: September 2012
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Windows® is a U.S. registered trademark of Microsoft Corporation.

Contents
1 Introduction...............................................................................................5
Supported Configurations..........................................................................................................5
HP X3000 and XP3000 G2 Storage Systems...............................................................................5
HP 3PAR OS Upgrade Considerations.........................................................................................6
Audience.................................................................................................................................6
Related Documentation..............................................................................................................6
Typographical Conventions........................................................................................................7
Advisories................................................................................................................................7
2 Performing Preliminary HP 3PAR Storage System and Host Configuration...........8
Configuring the HP 3PAR Storage System Host Persona and Ports (HP 3PAR OS 3.1.x or OS
2.3.x)......................................................................................................................................8
Configuring Ports on the HP 3PAR Storage System for a Direct Connection...................................8
Configuring Ports on the HP 3PAR Storage System for a Fabric Connection..................................8
Creating the Host Definition..................................................................................................9
Configuring the HP 3PAR Storage System Port Personas and Ports (HP 3PAR OS 2.2.x).....................10
Configuring HP 3PAR Storage System Ports for Direct Topology (HP 3PAR OS 2.2.x)...................10
Configuring HP 3PAR Storage System Ports for Fabric Topology (HP 3PAR OS 2.2.x)...................10
Creating the Host Definition (HP 3PAR OS 2.2.x)...................................................................11
Installing the HP 3PAR Host Explorer Software............................................................................12
Setting Up Multipathing...........................................................................................................12
Configuring Microsoft MPIO for HP 3PAR Storage..................................................................12
Configuring MPIO for Round Robin......................................................................................13
Setting Up and Zoning the Fabric.............................................................................................14
HP 3PAR Coexistence.........................................................................................................15
Configuration Guidelines for Fabric Vendors..........................................................................15
Target Port Limits and Specifications.....................................................................................16
3 Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System
Configuration for Fibre Channel....................................................................17
Checking the Host Server for Required Drivers............................................................................17
Installing and Configuring an Emulex Fibre Channel HBA............................................................17
Configuring the Emulex Support Driver..................................................................................17
Checking Emulex HBA Parameters and Connection Status.......................................................17
Installing and Configuring a QLogic Fibre Channel HBA..............................................................17
Configuring the QLogic Support Driver.................................................................................17
Checking QLogic HBA Parameters and Connection Status.......................................................18
Installing Veritas DMP Multipathing on the Windows Server 2008 Host.........................................18
Disabling the Write Cache Option for HP 3PAR LUNs..................................................................19
4 Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System
Configuration with iSCSI Storage...................................................................21
Setting Up the iSCSI Initiator and iSCSI Target Ports....................................................................21
Configuring the HP 3PAR Storage System for iSCSI......................................................................21
Using the Microsoft iSNS Server to Discover Registrations............................................................22
Configuring the iSCSI Initiator and Target for iSNS Server Usage.............................................22
Using the iSNS Server to Create a Discovery Domain.............................................................23
Establishing a Connection with the iSCSI Initiator Software...........................................................23
Establishing an iSCSI Session and Enabling Multipathing.............................................................28
Configuring Host iSCSI “no traffic” reattach................................................................................31
Configuring Host and Target CHAP...........................................................................................32
Setting Host CHAP.............................................................................................................32
Contents 3
Setting Target CHAP..........................................................................................................33
Setting Mutual (Bidirectional) CHAP.....................................................................................34
Removing CHAP................................................................................................................35
5 Setting Up a Windows Hyper-V Server/HP 3PAR Storage System
Configuration..............................................................................................36
Installing the Hyper-V Software.................................................................................................36
Configuring the Hyper-V Software.............................................................................................36
6 Allocating Storage for the Windows Server 2008/2012 Host.........................37
Creating Storage on the HP 3PAR Storage System.......................................................................37
Creating Virtual Volumes....................................................................................................37
Exporting VLUNs to the Windows Server 2008/2012 Host.....................................................38
Discovering LUNs...................................................................................................................38
Scanning for New Devices on an Windows Server 2008/2012 Host............................................39
Removing a Storage Volume from the Host.................................................................................40
7 Configuring the Windows Server 2008/2012 Host for an FCoE Connection....41
FCoE-to-FC Connectivity...........................................................................................................41
Configuring the FCoE Switch and FC Switch...............................................................................41
8 Booting from the HP 3PAR Storage System...................................................42
Configuring for iSCSI SAN Boot...............................................................................................42
Configuring the BIOS for Fibre Channel SAN Boot......................................................................42
Configuring for an HP 3PAR Storage System Boot: Emulex HBA...............................................42
Configuring for an HP 3PAR Storage System Boot: QLogic HBA...............................................42
Creating the Host Definition for an HP 3PAR Storage System Boot: FC...........................................43
Connecting the HP 3PAR Storage System to the Host: Fibre Channel..............................................43
Assigning LUN 0 as the Boot Volume........................................................................................43
Installing the Host OS onto LUN 0: Fibre Channel.......................................................................44
Connecting Multiple Paths for Fibre Channel SAN Boot...............................................................44
9 Using Failover Clustering with Microsoft MPIO..............................................45
10 Using Failover Clustering in a Virtualized Environment.................................46
11 Using the Veritas Cluster Server.................................................................47
Symantec SF 5.1.....................................................................................................................47
Installing the Veritas Cluster Server............................................................................................47
Setting SCSI-3 Persistent Reservation Support for the HP 3PAR Storage System................................47
12 Using Microsoft Failover Cluster with Veritas DMP.......................................50
Installing the Veritas DMP........................................................................................................50
4 Contents
1 Introduction
This implementation guide provides the information needed to configure the HP 3PAR Storage
System with Microsoft® Windows® Server 2008 or Microsoft® Windows® 2012. Unless otherwise
noted, information in this guide applies to servers running the following operating systems:
• Windows Server 2008 with Service Pack 1 (SP1) and Service Pack 2 (SP2), on both x86
(32-bit) and x64 (64-bit) architectures
• Windows Server 2008 R2 or Windows Server 2012, on x64 (64-bit) architecture only
This guide also applies to the HP X3000 G2 Storage System.
NOTE: This guide covers HP 3PAR Storage Systems running HP 3PAR Operating System (HP 3PAR
OS) 3.1.x, OS 2.3.x, and OS 2.2.x. Information covers all of these HP 3PAR OS versions unless
otherwise specified.
Although this implementation guide covers HP 3PAR OS 3.1.x, 2.3.x, and 2.2.x, Windows Server
2012 is supported only with HP 3PAR OS 3.1.x
Supported Configurations
A Windows Server 2008/2012 OS in a configuration with the HP 3PAR Storage System supports
fibre channel-connected storage, iSCSI storage, Fibre Channel over Ethernet (FCoE) (host-side
only), and Microsoft Hyper-V connected storage.
A configuration with a Windows Server 2008/2012 host requires the following software on the
host, depending on the host configuration and unless otherwise specified:
• Multipathing: native Microsoft MPIO
• iSCSI only:
◦ Microsoft iSCSI Initiator
◦ Booting from the HP 3PAR Storage Server: the Double-Take® Flex software iSCSI storage
For information about supported hardware and software platforms, see the HP Single Point of
Connectivity Knowledge (SPOCK) website:
http://www.hp.com/storage/spock
NOTE: For an iSCSI-connected configuration, consult the Microsoft iSCSI Software Initiator Version
2.8 Users Guide, downloadable from the Microsoft website.
In addition, HP 3PAR Host Explorer software is recommended for Windows Server 2008 servers
connected to an HP 3PAR Storage System running HP 3PAR OS 3.1.x or OS 2.3.x.
To obtain the HP 3PAR Host Explorer software, contact your HP account manager or HP Customer
Support.
HP X3000 and XP3000 G2 Storage Systems

An HP 3PAR Storage System connection to an HP X3000 or HP X3000 G2 Network Storage
System is supported via Fibre Channel with the HP X3000 operating system booted locally from
the host server internal disk. Follow the relevant sections of this implementation guide to connect
the HP 3PAR Storage System to the HP X3000 or HP X3000 G2.
The following sections of this document are relevant to X3000 configurations and must be followed:
• “Introduction” (page 5)
• “Performing Preliminary HP 3PAR Storage System and Host Configuration” (page 8)
Supported Configurations 5
• “Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System Configuration for
Fibre Channel” (page 17)
• “Booting from the HP 3PAR Storage System” (page 42)
• “Using Failover Clustering with Microsoft MPIO” (page 45)
HP 3PAR OS Upgrade Considerations

For information about planning an online HP 3PAR Operating System (HP 3PAR OS) upgrade, see
the HP 3PAR InForm Operating System Upgrade Pre-Planning Guide, which is available on the HP
Business Support Center (BSC) website:
http://www.hp.com/go/3par/
For complete details on supported host configurations, consult the HP SPOCK website:
http://www.hp.com/storage/spock
WARNING! On the first Windows Server 2008/2012 reboot following an HP 3PAR array
firmware upgrade, the Windows Server 2008/2012 will mark the HP 3PAR LUNs "offline". For
Windows Server 2008, the server administrator must use the Computer Management+Disk
Management option, right-click each of the HP 3PAR LUNs, and set the LUN online so that
application can access the HP 3PAR LUN.
For Windows Server 2012, there is a workaround to this problem: the administrator can change
the OS SAN Policy from Offline Shared to OnlineAll using the diskpart.exe command before
the Windows Server 2012 is rebooted. The SAN Policy on the Windows Server 2012 server can
be changed either before or after the HP 3PAR array firmware has been upgraded, but before the
Windows Server 2012 server is rebooted.
Audience
This implementation guide is intended for system and storage administrators who monitor and
direct system configurations and resource allocation for the HP 3PAR Storage System.
The tasks described in this guide assume that the administrator is familiar with Windows
Server 2008/2012 servers and with the HP 3PAR OS.
NOTE: This implementation guide is not intended to reproduce any third-party product
documentation. For details about devices such as host servers, HBAs, fabric switches, and
non-HP 3PAR software management tools, consult the appropriate third-party documentation.
Related Documentation
The following documents also provide information related to the HP 3PAR Storage System and the
HP 3PAR OS:
For information about… Read the…
Specific platforms supported HP 3PAR OS InForm Configuration Matrix
HP 3PAR OS CLI commands and their HP 3PAR Inform OS Command Line Interface Reference
usage
Using the HP 3PAR OS Management InForm Management Console Help

Console to configure and administer
the HP 3PAR Storage System
HP 3PAR Storage System concepts and HP 3PAR InForm OS Concepts Guide

terminology
6 Introduction
For information about… Read the…
Determining HP 3PAR Storage System • HP 3PAR E-Class/F-Class Storage System Physical Planning Manual
hardware specifications, installation
considerations, power requirements, • HP 3PAR S-Class/T-Class Storage System Physical Planning Manual
networking options, and cabling • HP 3PAR V-Class Storage System and Third Party Rack Physical Planning
Manual
Identifying storage server components HP 3PAR InForm OS 3.1.1 Messages and Operator's Guide
and detailed alert information
Using HP 3PAR Remote Copy HP 3PAR Remote Copy 3.1.1 Software User's Guide
Using HP 3PAR CIM HP 3PAR CIM API Programming Reference
Updating the HP 3PAR OS HP 3PAR InForm Operating System 3.1.1 Upgrade Pre-Planning Guide
To obtain a copy of this documentation, see the HP BSC website:

Typographical Conventions
This guide uses the following typographical conventions:
Typeface Meaning Example
ABCDabcd Used for dialog elements such as When prompted, click Finish to complete the
titles, button labels, and other screen installation.
elements.
ABCDabcd Used for paths, filenames, and screen Open the file
output. \os\windows\setup.exe
ABCDabcd Used to differentiate user input from # cd \opt\3par\console

screen output.
<ABCDabcd> Used for variables in filenames, # controlport offline <node:slot:port>

paths, and screen output.
[ABCDabcd] Used for options in user input. Modify the content string by adding the -P[x]
option after -jar inform.jar
# .\java -jar inform.jar -P[x]
Advisories
To avoid injury to people or damage to data and equipment, be sure to observe the cautions and
warnings in this guide. Always be careful when handling any electrical equipment.
NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this
guide.
Required
Requirements signify procedures that must be followed as directed in order to achieve a functional
and supported implementation based on testing at HP.
WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage
to data or the operating system.
CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
Typographical Conventions 7
2 Performing Preliminary HP 3PAR Storage System and Host
Configuration
Required
If you are setting up a fabric along with your installation of the HP 3PAR Storage System, see
“Setting Up and Zoning the Fabric” (page 14) before configuring or connecting the HP 3PAR
Storage System and host.
Configuring the HP 3PAR Storage System Host Persona and Ports (HP 3PAR
OS 3.1.x or OS 2.3.x)
For an HP 3PAR Storage System running HP 3PAR OS 3.1.x or OS 2.3.x, each HP 3PAR Storage
System port connecting to a host HBA port through a fabric or direct connection must be set to the
correct host persona.
NOTE: When deploying HP Virtual Connect Direct-Attach for HP 3PAR Storage where the HP 3PAR
Storage System ports are cabled directly to the uplink ports on the HP Virtual Connect FLexFabric
10 Gb/24-port Module for c-Class BladeSystem, follow the steps for configuring the HP 3PAR
Storage System ports for a fabric connection.
For more information about HP Virtual Connect, HP Virtual Connect interconnect modules, and the
HP Virtual Connect Direct-Attach feature, see Virtual Connect documentation and the HP SAN
Design Reference Guide. This documentation is available on the HP BSC website:
Configuring Ports on the HP 3PAR Storage System for a Direct Connection

To configure HP 3PAR Storage System ports for a direct connection to the Windows
Server 2008/2012 host on HP 3PAR OS 3.1.x or OS 2.3.x, complete the following steps:
1. To set up the HP 3PAR Storage System ports for a direct connection, issue the following set
of commands with the appropriate parameters for each direct connect port:
a. controlport offline <node:slot:port>
b. controlport config host –ct loop <node:slot:port>
where -ct loop specifies a direct connection.
c. controlport rst <node:slot:port>
Example:
# controlport offline 1:5:1

# controlport config host -ct loop 1:5:1
# controlport rst 1:5:1
2. After all ports have been configured, verify that the ports are configured for a host in a direct
connection by issuing the showport -par command on the HP 3PAR Storage System.
Configuring Ports on the HP 3PAR Storage System for a Fabric Connection

To configure ports for fabric using HP 3PAR OS 3.1.x or OS 2.3.x, follow these steps:
8 Performing Preliminary HP 3PAR Storage System and Host Configuration

1. To determine if a port has already been configured for a host port in fabric mode, issue
showport -par on the HP 3PAR Storage System.
2. If the port has not been configured, take the port offline before configuring it for connection
to a host server. To take the port offline, issue the HP 3PAR OS CLI command controlport
offline <node:slot:port>.
3. To configure the port to the host server, issue controlport config host –ct point
<node:slot:port>, where -ct point indicates that the connection type specified is a
fabric connection. For example:
# controlport config host –ct point 0:4:1
4. To bring the port online, issue controlport rst <node:slot:port>; for example:
5. Connect each host HBA port to the fabric. Each host HBA port's worldwide name (WWN)
should be associated with the HP 3PAR Storage System port it is connected to.
6. Complete the zoning; see “Setting Up and Zoning the Fabric” (page 14).
7. Issue showhost to verify that the host has connected to the HP 3PAR Storage System.
Creating the Host Definition

Before connecting the host to the HP 3PAR Storage System using HP 3PAR OS 3.1.x, create a host
definition for the Windows Server 2008/2012 host.
NOTE: HP requires host persona 2 for Windows Server 2008 R2 and Windows Server 2012
OS hosts, and host persona 1 for non-R2 Windows Server 2008 hosts. However, host persona 6
is automatically assigned following a rolling HP 3PAR OS upgrade from OS version 2.2.x. You
must change host persona 6 after such an upgrade either to host persona 2 (for Windows Server
2008 R2 and Windows Server 2012 hosts) or to host persona 1 (for Windows Server 2008 non-R2
hosts). Before changing host personas, refer to the HP 3PAR InForm Operating System 3.1.1
Upgrade Pre-Planning Guide for instructions to prevent loss of LUN mapping.
to obtain a copy of this documentation, go to the HP BSC website:
Host persona 1 enables two functional features: Host_Explorer, which requires the SESLun element
of host persona 1 and the UARepLun, which notifies the host of newly exported VLUNs and should
trigger a LUN discovery request on the host, making the VLUN automatically available on format.
However, Windows Server 2008/2012 does not support this feature, so you must scan LUNs
manually. Host persona 2 also enables the RTPG feature, which automatically enables active/active
multipathing on Windows Server 2008 R2 or Windows Server 2012 hosts.
1. To create host definitions, issue the createhost [options] <hostname> [<WWN>...]

command. For example:
# createhost -persona 1 windowshost 10000000C9606724
Configuring the HP 3PAR Storage System Host Persona and Ports (HP 3PAR OS 3.1.x or OS 2.3.x) 9
2. To verify that the host has been created, issue the showhost command.
% showhost
Id Name Persona -WWN/iSCSI_Name- Port
0 windowshost Generic 10000000C9606724 ---
NOTE: See the HP 3PAR Inform OS Command Line Interface Reference or the InForm Management
Console Help for complete details on using the controlport, createhost, and showhost
commands.
These documents are available on the HP BSC website:
Configuring the HP 3PAR Storage System Port Personas and Ports (HP 3PAR
OS 2.2.x)
Required
Windows Server 2012 is supported only on HP 3PAR OS 3.1.1 MU2 and later.
This section explains these procedures for an HP 3PAR Storage System running HP 3PAR OS 2.2.x,
in separate subsections:
• Configuring HP 3PAR Storage System ports for direct topology
• Configuring HP 3PAR Storage System ports for fabric topology
• Creating the host definition
Configuring HP 3PAR Storage System Ports for Direct Topology (HP 3PAR OS 2.2.x)
Follow these steps:
1. To set the port persona for each HP 3PAR Storage System port that will connect to an HBA
on the host server, issue controlport persona 1 <node:slot:port>.
NOTE: The required port persona value for direct connect is 1.
2. To verify that each port has the correct persona and connection type, issue showport -par.
For example:
# showport -par
0:4:1 loop auto disable disable (1) g_ven, g_hba, g_os, 0, DC enabled
3. Connect each Host HBA port to its associated HP 3PAR Storage System port. Each host HBA
port's worldwide name (WWN) should be associated with the HP 3PAR Storage System port
it is connected to.
4. Issue showhost to verify that the host has connected to the HP 3PAR Storage System.
Configuring HP 3PAR Storage System Ports for Fabric Topology (HP 3PAR OS 2.2.x)
To set up HP 3PAR Storage System ports for fabric connect, complete the following steps for each
fabric connect port.
CAUTION: Do not take ports for fabric connection offline until you verify that the port has not
been previously defined. A previously defined fabric port might already be connected to hosts.
Taking a port offline in this scenario would interrupt the host connection. In cases where the HP 3PAR
Storage System ports are already configured for fabric, the port will not have to be taken offline.

Follow these steps:
1. To determine whether a port has already been configured for a host port in fabric mode, issue
showport -par on the HP 3PAR Storage System.
In the output below, loop denotes direct connect and point denotes fabric.
# showport -par
N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal
0:0:1 disk loop auto 2Gbps disabled disabled disabled enabled
0:4:1 host point auto 4Gbps disabled disabled disabled enabled
0:5:2 host loop auto 2Gbps disabled disabled disabled enabled
2. If the port has not been configured, take the port offline before configuring it to a host server;
issue controlport offline <node:slot:port>. For example:
3. To configure the port to the host server, issue the following command:
# controlport persona 7 <node:slot:port>

controlport vcn disable <node:slot:port>
For example:
# controlport persona 7 1:5:1

# controlport vcn disable 1:5:1
NOTE: The required port persona value for fabric is 7. For this port persona value, VCN
must be disabled.
4. To bring the port online, issue controlport rst <node:slot:port>; for example:
5. Connect each host HBA port to the fabric. Each host HBA port's worldwide name (WWN)
should be associated with the HP 3PAR Storage System port it is connected to.
6. Complete zoning; see “Setting Up and Zoning the Fabric” (page 14).
Creating the Host Definition (HP 3PAR OS 2.2.x)

Before connecting the host to the HP 3PAR Storage System, create a host definition for the Windows
2008 host:
Configuring the HP 3PAR Storage System Port Personas and Ports (HP 3PAR OS 2.2.x) 11
1. Issue createhost [options] <hostname> [<WWN>...].
For example:
# createhost windowshost 10000000C9606724
2. To verify that the host is created, issue the showhost command; for example:
% showhost
Id Name WWN/iSCSI_Name------------- Port
0 windowshost 10000000C9606724 ---
Installing the HP 3PAR Host Explorer Software

The HP 3PAR Host Explorer software is recommended for a configuration with a Windows OS
host that is connected to the HP 3PAR OS.
To install the HP 3PAR Host Explorer program, contact your HP account manager or HP Customer
Support for the CD, and follow instructions in the Host Explorer documentation.
Setting Up Multipathing
For high-availability storage with load balancing of I/O and improved system and application
performance, Windows Server 2008/2012 requires the native Microsoft MPIO and the StorPort
miniport driver. Also, a Windows Server 2008 server connected to an HP 3PAR Storage System
running HP 3PAR OS 2.2.x requires the Round Robin MPIO policy (the Veritas DMP I/O policy
setting is "Round Robin").
This section explains:
• Installing and configuring the native Microsoft MPIO for HP 3PAR storage
• Setting the MPIO policy to round robin for HP 3PAR OS 2.2.x
Configuring Microsoft MPIO for HP 3PAR Storage

Required
To resolve issues with MPIO path failover, it is recommended that Hot Fixes KB2406705 and
KB2522766 be installed for all versions of Windows Server 2008 up to and including Windows
Server 2008 R2 SP1.
NOTE: The procedure in this subsection requires rebooting.

Follow these steps:
1. If you have not already done so, check HBA vendor documentation for any required support
drivers, and install them.
2. If necessary, install the StorPort miniport driver.
3. If the MPIO feature is not enabled, open the Server Manager and install the MPIO feature.
This will require a reboot.
4. After rebooting, open the Windows Administrative Tools and click MPIO.
5. In the MPIO-ed Devices tab, click the Add button; the Add MPIO Support popup appears.
6. In the Device Hardware ID: text box, enter 3PARdataVV, and click OK. See “Adding MPIO
Support for HP 3PAR Devices ” (page 13).

Figure 1 Adding MPIO Support for HP 3PAR Devices
7. Reboot as directed.
NOTE: You can also use MPIO-cli to add 3PARdataVV. The command is:
"mpclaim -r -I -d "3PARdataVV"
Configuring MPIO for Round Robin

A Windows Server 2008 server connected to an HP 3PAR Storage System running HP 3PAR OS
2.2.x or later requires that the multipath policy be set to Round Robin.
Windows Server 2008 R2 or Windows 2012 servers do not need to change the multipath policy,
as it defaults to Round Robin.
If the server is running any supported Windows Server 2008 version prior to Windows Server
2008 R2, and if the Windows Server 2008 server is connected to an HP 3PAR array that is running
HP 3PAR OS 2.2.x, the multipath policy will default to failover and must be changed to Round
Robin. However, if the OS version on the HP 3PAR array is HP 3PAR OS 2.3.x or later, then you
must use HP 3PAR OS host persona 1 for the Windows Server 2008 server so that the multipath
policy defaults to Round Robin. For recommended host persona, see “Configuring the HP 3PAR
Storage System Port Personas and Ports (HP 3PAR OS 2.2.x)” (page 10).
To verify the default MPIO policy, follow these steps:
1. In the Server Manager, click Diagnostics; select Device Manager. Expand the Disk drives list.
2. Right-click an HP 3PAR drive to display its Properties window and select the MPIO tab. Select
Round Robin from the drop-down menu. See “Specifying MPIO Policy ” (page 14).
Setting Up Multipathing 13
Figure 2 Specifying MPIO Policy
3. Click OK.
Setting Up and Zoning the Fabric

NOTE: This section does not apply when deploying HP Virtual Connect Direct-Attach for HP 3PAR
Storage where the HP 3PAR Storage System ports are cabled directly to the uplink ports on the
HP Virtual Connect FLexFabric 10 Gb/24-port Module for c-Class BladeSystem. Zoning is
automatically configured based on the Virtual Connect SAN Fabric and server profile definitions.
For more information about HP Virtual Connect, HP Virtual Connect interconnect modules, and the
HP Virtual Connect Direct-Attach feature, see Virtual Connect documentation and the HP SAN
Design Reference Guide. This documentation is available on the HP BSC website:
Fabric zoning controls which Fibre Channel end-devices have access to each other on the fabric.
Zoning also isolates the host server and HP 3PAR Storage System ports from Registered State
Change Notifications (RSCNs) that are irrelevant to these ports.
You can set up fabric zoning by associating the device World Wide Names (WWNs) or the switch
ports with specified zones in the fabric. Although you can use either the WWN method or the port
zoning method with the HP 3PAR Storage System, the WWN zoning method is recommended
because the zone survives the changes of switch ports when cables are moved around on a fabric.
Required
Employ fabric zoning, using the methods provided by the switch vendor, to create relationships
between host server HBA ports and storage server ports before connecting the host server HBA
ports or HP 3PAR Storage System ports to the fabric(s).
Fibre Channel switch vendors support the zoning of the fabric end-devices in different zoning
configurations. There are advantages and disadvantages with each zoning configuration. Choose
a zoning configuration based on your needs.

The HP 3PAR arrays support the following zoning configurations:
• One initiator to one target per zone
• One initiator to multiple targets per zone (zoning by HBA). This zoning configuration is
recommended for the HP 3PAR Storage System. Zoning by HBA is required for coexistence
with other HP Storage arrays.
NOTE: The storage targets in the zone can be from the same HP 3PAR Storage System,
multiple HP 3PAR Storage Systems , or a mixture of HP 3PAR and other HP storage systems.
For more information about using one initiator to multiple targets per zone, see “Zoning by HBA”
in the “Best Practices” chapter of the HP SAN Design Reference Guide. This document is available
on the HP BSC website:
If you use an unsupported zoning configuration and an issue occurs, HP may require that you
implement one of the supported zoning configurations as part of the troubleshooting or corrective
action.
After configuring zoning and connecting each host server HBA port and HP 3PAR Storage System
port to the fabric(s), verify the switch and zone configurations using the HP 3PAR OS CLI showhost
command, to ensure that each initiator is zoned with the correct target(s).
HP 3PAR Coexistence
The HP 3PAR Storage System array can coexist with other HP array families.
For supported HP arrays combinations and rules, see the HP SAN Design Reference Guide, available
on the HP BSC website:
Configuration Guidelines for Fabric Vendors

Use the following fabric vendor guidelines before configuring ports on fabric(s) to which the
HP 3PAR Storage System connects.
• Brocade switch ports that connect to a host server HBA port or to an HP 3PAR Storage System
port should be set to their default mode. On Brocade 3xxx switches running Brocade firmware
3.0.2 or later, verify that each switch port is in the correct mode using the Brocade telnet
interface and the portcfgshow command, as follows:
brocade2_1:admin> portcfgshow
Ports 0 1 2 3 4 5 6 7
-----------------+--+--+--+--+----+--+--+--
Speed AN AN AN AN AN AN AN AN
Trunk Port ON ON ON ON ON ON ON ON
Locked L_Port .. .. .. .. .. .. .. ..
Locked G_Port .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. ..
where AN:AutoNegotiate, ..:OFF, ??:INVALID.
The following fill-word modes are supported on a Brocade 8 G/s switch running FOS firmware
6.3.1a and later:
admin>portcfgfillword
Usage: portCfgFillWord PortNumber Mode [Passive]
Mode: 0/-idle-idle - IDLE in Link Init, IDLE as fill word (default)
1/-arbff-arbff - ARBFF in Link Init, ARBFF as fill word
2/-idle-arbff - IDLE in Link Init, ARBFF as fill word (SW)
3/-aa-then-ia - If ARBFF/ARBFF failed, then do IDLE/ARBFF
Setting Up and Zoning the Fabric 15

HP recommends that you set the fill word to mode 3 (aa-then-ia), which is the preferred
mode using the portcfgfillword command. If the fill word is not correctly set, er_bad_os
counters (invalid ordered set) will increase when you use the portstatsshow command
while connected to 8 G HBA ports, as they need the ARBFF-ARBFF fill word. Mode 3 will
also work correctly for lower-speed HBAs, such as 4 G/2 G HBAs. For more information, see
the Fabric OS command Reference Manual supporting FOS 6.3.1a and the FOS release
notes.
In addition, some HP switches, such as the HP SN8000B 8-slot SAN backbone director switch,
the HP SN8000B 4-slot SAN director switch, the HP SN6000B 16 Gb FC switch, or the HP
SN3000B 16 Gb FC switch automatically select the proper fill-word mode 3 as the default
setting.
• McDATA switch or director ports should be in their default modes as G or GX-port (depending
on the switch model), with their speed setting permitting them to autonegotiate.
• Cisco switch ports that connect to HP 3PAR Storage System ports or host HBA ports should
be set to AdminMode = FX and AdminSpeed = auto port, with the speed set to auto negotiate.
• QLogic switch ports should be set to port type GL-port and port speed auto-detect. QLogic
switch ports that connect to the HP 3PAR Storage System should be set to I/O Stream Guard
disable or auto, but never enable.
Target Port Limits and Specifications

To avoid overwhelming a target port and ensure continuous I/O operations, observe the following
limitations on a target port:
• Maximum of 64 (32 for Hyper-V) host server ports per HP 3PAR Storage System port, with a
maximum total of 1,024 host server ports per HP 3PAR Storage System.
• I/O queue depth on each HP 3PAR Storage System HBA model, as follows:
◦ QLogic 2G: 497
◦ LSI 2G: 510
◦ Emulex 4G: 959
◦ HP 3PAR HBA 4G: 1638
◦ HP 3PAR HBA 8G: 3276 (V400/V800 systems only)

• The I/O queues are shared among the connected host server HBA ports on a first-come,
first-served basis.
• When all queues are in use and a host HBA port tries to initiate I/O, it receives a target queue
full response from the HP 3PAR Storage System port. This condition can result in erratic I/O
performance on each host server. If this condition occurs, each host server should be throttled
so that it cannot overrun the HP 3PAR Storage System port's queues when all host servers are
delivering their maximum number of I/O requests.
NOTE: When host server ports can access multiple targets on fabric zones, the assigned
target number assigned by the host driver for each discovered target can change when the
host server is booted and some targets are not present in the zone. This situation may change
the device node access point for devices during a host server reboot. This issue can occur
with any fabric-connected storage, and is not specific to the HP 3PAR Storage System.

3 Setting Up a Windows Server 2008 or 2012/HP 3PAR
Storage System Configuration for Fibre Channel
Checking the Host Server for Required Drivers
Check the Microsoft website for required packages and hotfixes, including updated drivers. Also
consult the HP 3PAR OS InForm Configuration Matrix for support drivers, and follow HBA vendor
instructions.
You can also use the Emulex One Command or QLogic QConvergeConsole software to verify
support for HBA driver versions.
Installing and Configuring an Emulex Fibre Channel HBA

For HBA installation instructions, driver support and usage guidelines, refer to the Emulex installation
and usage guide for each product type. If your configuration includes MPIO, check also for
information about any required MPIO support driver.
NOTE: For booting from the HP 3PAR Storage System, configuring the BIOS is required. For
further information, see “Configuring for an HP 3PAR Storage System Boot: Emulex HBA” (page 42).
Configuring the Emulex Support Driver

After installing the driver, set HBA driver parameters; consult the HBA driver documentation for
details.
To avoid overwhelming a target port and to ensure continuous I/O operations, observe the
limitations on a target port; see “Target Port Limits and Specifications” (page 16).
NOTE: When host server ports can access multiple targets on fabric zones, the assigned target
number (which is assigned by the host driver) for each discovered target can change when the
host server is booted and some targets are not present in the zone. This situation might change
the device node access point for devices during a host server reboot. This issue can occur with
any fabric-connected storage, and is not specific to the HP 3PAR Storage System.
NOTE: If you run HP 3PAR OS Rolling Upgrade, consult the HP 3PAR InForm Operating System
Upgrade Pre-Planning Guide.
To obtain a copy of this documentation, go to the HP BSC website:
Checking Emulex HBA Parameters and Connection Status

Use the Emulex One Command utility to check connection status.
Installing and Configuring a QLogic Fibre Channel HBA

For HBA installation instructions, driver support and usage guidelines, refer to the QLogic installation
and usage guide for each product type. If your configuration includes MPIO, check also for
information about any required MPIO support driver.
NOTE: For booting from the HP 3PAR Storage System, configuring the BIOS is required. For
further information, see “Configuring for an HP 3PAR Storage System Boot: QLogic HBA” (page 42).
Configuring the QLogic Support Driver

After installing the driver, set HBA driver parameters, such as maximum number of LUNs per target
and the Port Down Retry Count; consult the HBA driver documentation for details.
Checking the Host Server for Required Drivers 17

To avoid overwhelming a target port and to ensure continuous I/O operations, observe the
limitations on a target port; see “Target Port Limits and Specifications” (page 16).
NOTE: When host server ports can access multiple targets on fabric zones, the target number
assigned by the host driver for each discovered target can change when the host server is booted
and some targets are not present in the zone. This may change the device node access point for
devices during a host server reboot. This issue can occur with any fabric-connected storage, and
is not specific to the HP 3PAR Storage System.
NOTE: If you perform an HP 3PAR OS Rolling Upgrade, consult the HP 3PAR InForm Operating
System Upgrade Pre-Planning Guide, which is available on the HP BSC website:
Checking QLogic HBA Parameters and Connection Status

Use the QLogic QConvergeConsole software to check connection status.
Installing Veritas DMP Multipathing on the Windows Server 2008 Host

NOTE: Check with Veritas for supported compatibility:
http://www.symantec.com/business/support/index?page=content&
id=TECH148533&key=50276
Otherwise, when Veritas tries to validate server components, you might see the following error
message:
Error message as (NOT a supported OS)
In addition, the installation will fail.
If the configuration includes Veritas Storage Foundation software, configure it for use with the
HP 3PAR Storage System. Follow these steps:
1. Install the latest DDI packet from the Veritas website.
18 Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System Configuration for Fibre Channel
2. Select only 3PARDATA (V3PARAA) as your DMP device: see “Setting Up Veritas Storage for
the HP 3PAR Storage Server” (page 19).
Figure 3 Setting Up Veritas Storage for the HP 3PAR Storage Server
For details about this software, refer to the Veritas Storage Foundation for Windows
Administration Guide and the Veritas Storage Foundation & High Availability Solutions
Installation & Upgrade Guide.
Disabling the Write Cache Option for HP 3PAR LUNs

HP 3PAR virtual volumes/LUNs are write cache-enabled and, by design, cannot be turned off.
The following dialog box appears when Veritas Enterprise Administrator is invoked, and the left
tree on the graphical user interface (GUI) is expanded.
Disabling the Write Cache Option for HP 3PAR LUNs 19

You can ignore the message, as the HP 3PAR Storage System is a fault-tolerant redundant array.
Disabling of the cache is not required. You can uncheck the message to prevent it from appearing
every time Veritas Enterprise Administrator is invoked.
20 Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System Configuration for Fibre Channel
4 Setting Up a Windows Server 2008 or 2012/HP 3PAR
Storage System Configuration with iSCSI Storage
NOTE: HP recommends that you read the Microsoft iSCSI Software Initiator Users Guide for
Windows-specific concepts and procedures discussed in this chapter.
Setting Up the iSCSI Initiator and iSCSI Target Ports

Connect the host iSCSI initiator port(s) and the and the HP 3PAR Storage System iSCSI target ports
to the switches.
If you are using VLANs, make sure that the switch ports which connect to the HP 3PAR Storage
System iSCSI target ports and iSCSI Initiator ports reside in the same VLANs and/or that you can
route the iSCSI traffic between the iSCSI Initiator ports and the HP 3PAR Storage System iSCSI
target ports. Once the iSCSI Initiator and HP 3PAR Storage System iSCSI target ports are configured
and connected to the switch, you can use the ping command on the iSCSI Initiator host to make
sure that it sees the HP 3PAR Storage System iSCSI target ports.
NOTE: Switch VLAN configuration and routing setup and configuration are beyond the scope
of this document. Consult your switch manufacturer's guide for instructions about setting up VLANs
and routing.
Configuring the HP 3PAR Storage System for iSCSI

Follow these steps to set up the HP 3PAR Storage System for iSCSI storage:
1. (This step applies only to the HP 3PAR P10000 Storage.) If the HP 3PAR Storage System iSCSI
ports have not been configured for iSCSI, first use this command:
# controlport config iscsi -f N:S:P
2. Check the current iSCSI port settings: issue showport -iscsi. The following example shows
ports offline and unconfigured.
# showport -iscsi
N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec
iSNS_Port
0:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 31 1500 n/a 0 0.0.0.0 0.0.0.0
3205
0:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 32 1500 n/a 0 0.0.0.0 0.0.0.0
3205
1:3:1 offline 0.0.0.0 0.0.0.0 0.0.0.0 131 1500 n/a 0 0.0.0.0 0.0.0.0
3205
1:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 132 1500 n/a 0 0.0.0.0 0.0.0.0
3205
3. Issue controliscsiport addr to set the IP addresses and netmask addresses of the iSCSI
target ports; for example:
# controliscsiport addr 10.101.1.31 255.255.0.0 -f 0:3:1

# controliscsiport addr 10.101.1.131 255.255.0.0 -f 1:3:1
Setting Up the iSCSI Initiator and iSCSI Target Ports 21

4. Verify the configuration; the following example shows two ports ready:
# showport -iscsi
N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim
iSNS_Sec iSNS_Port
0:3:1 ready 10.101.1.31 255.255.0.0 0.0.0.0 31 1500 1Gbps 0 0.0.0.0
0.0.0.0 3205
0:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 32 1500 n/a 0 0.0.0.0
0.0.0.0 3205
1:3:1 ready 10.101.1.131 255.255.0.0 0.0.0.0 131 1500 1Gbps 0 0.0.0.0
0.0.0.0 3205
1:3:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 132 1500 n/a 0 0.0.0.0
0.0.0.0 3205
5. Issue createhost -iscsi [options] <hostname> [<iscsi_name>...].

Here is an example of a Windows 2008 R2 createhost command:
NOTE: HP recommends host persona 2 for Windows Server 2008 R2 and Windows Server
2012, and host persona 1 for non-R2 Windows Server 2008.
# createhost -iscsi -persona 1 sqa-dl380g5-08

iqn.1991-05.com.microsoft:sqa-dl380g5-08
6. Check the newly set up host with the showhost command. For example:
# showhost
Id Name Persona -------------WWN/iSCSI_Name-------------- Port
1 sqa-dl380g5-08 Generic iqn.1991-05.com.microsoft:sqa-dl380g5-08 ---
Using the Microsoft iSNS Server to Discover Registrations

Use the Microsoft iSNS server to discover the iSCSI initiator and iSCSI targets on the dedicated
network. When the iSCSI Initiator and iSCSI targets have registered with the iSNS server, they
automatically start discovery of the registered devices by querying the iSNS client/server via
TCP/IP. A database of these registrations is also maintained.
Installing and using the iSNS server consists of these procedures, explained in separate subsections:
• Installing the iSNS server
• Using the iSNS server to discover registrations
Configuring the iSCSI Initiator and Target for iSNS Server Usage
Follow these steps:
1. Issue showport -iscsi to verify whether the iSCSI target ports are configured for the iSNS
server; for example:
# showport -iscsi
N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port
0:1:1 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 3205
0:1:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 3205
1:1:1 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 3205
1:1:2 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
22 Setting Up a Windows Server 2008 or 2012/HP 3PAR Storage System Configuration with iSCSI Storage
2. Set up the IP addresses for iSNS; for example:
# controliscsiport isns 10.0.0.60 0:1:1
# controliscsiport isns 10.0.0.60 1:1:1
3. Verify the configuration setting for iSNS; for example:
# showport -iscsi
N:S:P State IPAddr Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec iSNS_Port
0:1:1 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 3205
0:1:2 offline 0.0.0.0 0.0.0.0 0.0.0.0 12 1500 n/a 0 0.0.0.0 0.0.0.0 3205
1:1:1 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 3205
1:1:2 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
4. Use the Windows Server 2008/2012 Add Features wizard to add the Internet Storage Name
Server feature.
5. Once the iSNS server is installed on another Windows Server 2008/2012 server, open the
iSCSI Initiator, click the Discovery 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

Follow these steps:
1. Click Start > Administrative Tools > iSNS Server > Discovery Domains tab.
2. In the window that appears, click the Create button. In the Create Discovery Domain popup,
enter the discovery domain or select the default; click OK.
3. To add iSNS to the iSCSI initiator, follow these steps:
1. Click Start > Administrative Tools > iSCSI Initiator.
2. From the iSCSI Initiator Properties, select the Discovery tab, click the Add Server in iSNS
Servers section, and enter iSNS-Server or iSNS-IP in the popup window's Add iSNS Server
setting.
Establishing a Connection with the iSCSI Initiator Software

This section explains procedures for configuring Microsoft iSCSI Initiator software to establish a
connection. All of the steps after step 1 are the same for both Windows Server 2008 and Windows
Server 2012. Follow these steps:
1. To start iSCSI Initiator in a Windows Server 2012 OS, click Start→Programs→Administrative
Tools+iSCSI Initiator, as shown in Figure 4 (page 24).
Establishing a Connection with the iSCSI Initiator Software 23

Figure 4 Starting the Windows Server 2012 iSCSI Initiator
To start iSCSI Initiator in a Windows Server 2008/2012 OS, click

Start→Programs→Administrative Tools+iSCSI Initiator, as shown in “Starting the Windows
Server 2008 iSCSI Initiator” (page 25).
Figure 5 Starting the Windows Server 2008 iSCSI Initiator
2. From iSCSI Initiator Properties select Discovery tab.

Figure 6 iSCSI Initiator Properties
3. From the Discovery tab, Target portals area, click the Discover Portal... button, and in the Add
Target Portal dialog box, enter the IP address of the portal you want to add, as shown in
“Specifying a Target Portal IP Address” (page 27).
Figure 7 Specifying a Target Portal IP Address
4. Establish the connection: click Advanced; the Advanced Settings dialog box appears, as shown
in “Configuring a Target Portal Connection” (page 27).
Figure 8 Configuring a Target Portal Connection

In the Connect using section of this dialog box, do the following:
• In the Local Adapter text field, select Microsoft iSCSI Initiator.
• In the Initiator IP: text field, select the IP address of the NIC adapter or converged network
adapter (CNA) that you want to use to connect to the iSCSI target.
The CRC/Checksum is not required.
For more information about setting the CHAP login, see “Configuring Host and Target CHAP”
(page 32).
5. Click OK in the Advanced Settings dialog box and again in the Discover Target Portal dialog
box. The Discovery tab in the iSCSI Initiator Properties window displays the port information,
as shown in “Target Portal Discovery” (page 28).
Figure 9 Target Portal Discovery
6. Repeat these steps to connect additional target ports. Check the connections in the Discovery
tab in the iSCSI Initiator Properties window.
Establishing an iSCSI Session and Enabling Multipathing

To establish an iSCSI logon session with an HP 3PAR Storage System iSCSI target port, follow
these steps:
1. Click the Targets tab. Its window displays the names and status of the ports you have
configured.
2. Click the Connect button to establish an iSCSI connection session with the HP 3PAR Storage
System iSCSI target port. The Connect to Target popup appears, as shown in “Connecting to
a Target” (page 29).
3. Select the Favorite Targets and Enable multi-path check boxes.
Figure 10 Connecting to a Target
4. Do not click OK; instead click the Advanced... button. The Advanced Settings window appears,
as shown in “Specifying Connection Parameters” (page 30).
Establishing an iSCSI Session and Enabling Multipathing 29

Figure 11 Specifying Connection Parameters
5. In this window, select the following settings in the Connect using section:
NOTE: If you leave the default settings for these options, the Microsoft iSCSI Initiator will
not work correctly, especially if you have multiple local adapters, source IP addresses, and
target ports.
• Local adapter drop-down menu: Microsoft iSCSI Initiator

• Initiator IP drop-down menu: IP address of the NIC adapter or CNA in your system that
will connect to the iSCSI target port
• Target Portal IP drop-down menu: IP address of the target portal (iSCSI target port)
6. Click OK in the Advanced Settings window and again in the Targets 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 will show the status as Connected. See “Verifying Connected
Status for Both Targets ” (page 31)
8. Perform Step 4 through Step 7 to add the connection to the second target portal. The iSCSI
Initiator Properties window shows the status of both; see “Verifying Connected Status for Both
Targets ” (page 31).
Figure 12 Verifying Connected Status for Both Targets
Configuring Host iSCSI “no traffic” reattach

Follow these steps to automatically reattach dropped multipath connections that are currently
carrying no traffic.
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\.
2. Change the <parameters> value from 00000000 to 00000001:
"EnableNOPOut"=dword:00000000
3. Reboot the server(s) for the change to take effect.
Configuring Host iSCSI “no traffic” reattach 31

Configuring Host and Target CHAP
This section contains procedures for configuring the Challenge-Handshake Authentication Protocol
(CHAP) and removing it, in separate subsections:
• “Setting Host CHAP” (page 32)
• “Setting Target CHAP” (page 33)
• “Setting Mutual (Bidirectional) CHAP” (page 34)
• “Removing CHAP” (page 35)
Setting Host CHAP

To set a host CHAP secret, configure it on both the HP 3PAR Storage System server and the Windows
Server 2008/2012 host. Follow these steps:
1. Make sure that an iSCSI host definition has been created on the HP 3PAR Storage System.
2. Use showhost -chap to show that no CHAP secret is already set up. In the output, host
CHAP appears as Initiator_CHAP_Name.
# showhost -chap
Id Name -Initiator_CHAP_Name- -Target_CHAP_Name
3. Issue sethost initchap <chap_name> <host_name> to set initchap.

For example:
root@xnodee86a:~# sethost initchap MyChapSecret sqa-dl360g6-02-iscsi

Calling "sethost initchap" for host sqa-dl360g6-02-iscsi. Continue?
select q=quit y=yes n=no: y
4. Issue showhost -chap to verify that initchap has been created.
root@xnodee86a:~# showhost -chap

Id Name -Initiator_CHAP_Name- -Target_CHAP_Name-
25 sqa-dl360g6-02-iscsi sqa-dl360g6-02-iscsi
5. In the iSCSI Initiator Properties window, click the Targets tab. In the Targets tab, choose the
targets where the CHAP applies. Click Connect from Connect to Target, then check the Enable
multi-path and click the Advanced... button. From the Advanced Settings windows, follow
these steps, as shown in “Setting Up the Target CHAP Secret for HP 3PAR Storage System
initchap” (page 33):
a. Set Microsoft iSCSI Initiator for Local adapter
b. Select Initiator IP
c. Select Target Portal IP
d. Check Enable CHAP log on box
e. Enter CHAP secret for Target secret
NOTE: Enter MyChapSecret (from the example in Step 3) at the Target secret field.
See “Setting Up the Target CHAP Secret for HP 3PAR Storage System initchap” (page 33).
Figure 13 Setting Up the Target CHAP Secret for HP 3PAR Storage System initchap
Setting Target CHAP

To set a target CHAP secret, configure it on both the HP 3PAR Storage System and the Windows
Server 2008/2012 host by following these steps:
1. Issue showhost -chap to show that no CHAP secret is already set up.
# showhost -chap
2. To set a CHAP secret for a target, issue sethost targetchap -chapname

<chapname>where <chapname> is the secret. For example:
# sethost targetchap -f target_secret0 sqa-dl380g5-08
Configuring Host and Target CHAP 33

3. To check results, issue showhost -chap; for example:
# showhost -chap
0 sqa-dl380g5-08 s055
4. In the iSCSI Initiator Properties window, click the Configuration tab. Click CHAP and enter the
Initiator CHAP secret, then click OK, as shown in “Setting Up Host CHAP for HP 3PAR Storage
System targetchap” (page 34).
NOTE: Enter target_secret0, from the example in step 2, at the Initiator CHAP secret
field. See “Setting Up Host CHAP for HP 3PAR Storage System targetchap” (page 34).
Figure 14 Setting Up Host CHAP for HP 3PAR Storage System targetchap
Setting Mutual (Bidirectional) CHAP

To set mutual (bidirectional) CHAP, follow these steps:
1. Set the host CHAP secret following instructions in “Setting Host CHAP” (page 32).
2. Set the target CHAP secret following instructions in “Setting Target CHAP” (page 33).
3. Issue showhost -chap. The output shows both secrets set:
# showhost -chap
0 sqa-dl380g5-08 sqa-dl380g5-08 s055
Removing CHAP
To remove CHAP from the HP 3PAR Storage System, follow these steps:
1. Issue sethost removechap; this command removes all CHAP information for all specified
hosts. For example:
# sethost removechap sqa-dl380g5-0

Calling "sethost removechap" for host sqa-dl380g5-08. Continue?
select q=quit y=yes n=no: y
2. To check status, issue showhost -chap; for example:
# showhost -chap
0 sqa-dl380g5-08 --
3. In the iSCSI Initiator Properties window, click the Targets tab where the CHAP applies; click
the Connect button from the Connect to Target window and check the Enable multi-path option.
Then click the Advanced... button and in the Advanced Settings window, follow these steps,
as shown in “Removing CHAP” (page 35):
a. Set Microsoft iSCSI Initiator for Local adapter.
b. Select Initiator IP
c. Select Target portal IP
d. Clear the Enable CHAP log on check box.
Figure 15 Removing CHAP
Configuring Host and Target CHAP 35

5 Setting Up a Windows Hyper-V Server/HP 3PAR Storage
System Configuration
NOTE: This chapter pertains to a Windows server with an x64-based processor running an x64
version of Windows Server 2008 Standard, Windows Server 2008 Datacenter, Windows Server
2008 Enterprise (SP1, SP2), Windows Server 2008 R2 Server, or Windows Server 2012.
For details on Hyper-V operation, consult its documentation on the Microsoft website.
Installing the Hyper-V Software

Hyper-V software is installed by installing the Hyper-V Role from the Server Manager.
For system requirements and known issues, consult the Microsoft Hyper-V Server 2008 Getting
Started Guide from the Microsoft Hyper-V website. Follow steps explained there to install the
Hyper-V management tool, create and set up a virtual machine, install the operating system and
integration services, and configure virtual networks.
Configuring the Hyper-V Software

To configure the Hyper-V software, follow instructions in the Microsoft Hyper-V Server 2008 Setup
and Configuration Tool Guide.
NOTE: No particular parameters need to be set in the Hyper-V software to work with the HP 3PAR
Storage System; no additional steps are necessary on the HP 3PAR Storage System to work with
a Windows Hyper-V server.
36 Setting Up a Windows Hyper-V Server/HP 3PAR Storage System Configuration

6 Allocating Storage for the Windows Server 2008/2012
Host
Creating Storage on the HP 3PAR Storage System
This section describes the basic method for creating storage.
For additional information, see the HP 3PAR InForm OS CLI Administrator’s Manual. For a
comprehensive description of HP 3PAR OS commands, see the HP 3PAR Inform OS Command
Line Interface Reference. To obtain a copy of this documentation, go to http://www.hp.com/go/
3par/, navigate to your product page, click HP Support & Drivers, and then click Manuals.
Creating Virtual Volumes

Virtual volumes are the only data layer visible to hosts. After devising a plan for allocating space
for host servers on the HP 3PAR Storage System, create the VVs for eventual export as LUNs to the
Windows Server 2008/2012 host server.
You can create volumes that are provisioned from one or more common provisioning groups
(CPGs). Volumes can be fully provisioned from a CPG or can be thinly provisioned. You can
optionally specify a CPG for snapshot space for fully-provisioned volumes.
Using the InForm Management Console:

1. From the menu bar, select:
Actions→Provisioning→Virtual Volume+Create Virtual Volume
2. Use the Create Virtual Volume wizard to create a base volume.
3. Select one of the following options from the Provisioning list:
• Fully Provisioned from PDs
• Fully Provisioned from CPG
• Thinly Provisioned
Using the HP 3PAR OS CLI:

To create a fully-provisioned or thinly-provisioned virtual volume, follow these steps:
1. Issue the following HP 3PAR OS CLI command:
createvv [options] <usr_CPG> <VV_name> [.<index>] <size>[g|G|t|T]
Here is an example:
# createvv -cnt 10 demo 5g
2. Issue showvv to check the volumes created:
# showvv
--Rsvd(MB)--- -(MB)-
Id Name Prov Type CopyOf BsId Rd -Detailed_State- Adm Snp Usr VSize
0 admin full base --- 0 RW normal 0 0 10240 10240

831 demo.0 full base --- 831 RW normal 0 0 5120 5120
Creating Storage on the HP 3PAR Storage System 37

NOTE: To create thinly-provisioned virtual volumes, an HP 3PAR Thin Provisioning license is

required.
Consult the InForm Management Console Help and the HP 3PAR Inform OS Command Line Interface
Reference for complete details on creating volumes for the HP 3PAR OS version that is being used
on the HP 3PAR Storage System.
These documents are available on the HP BSC website:
NOTE: The commands and options available for creating a virtual volume may vary for earlier
versions of the HP 3PAR OS.
Exporting VLUNs to the Windows Server 2008/2012 Host

Follow the instructions for creating virtual volumes (VVs) and virtual LUNs (VLUNs) in the HP 3PAR
InForm OS CLI Administrator’s Manual.
Note the following guidelines:
• Sparse LUNs are supported (you can skip LUNs).
• You can export LUNs in nonascending order (e.g. 0, 5, 7, 3).
• The Windows Server 2008/2012 system registers only LUNs 0 to 254.
• The maximum number of usable LUNs per host port is 255. Although the HP 3PAR Storage
System can export LUNs 0 to 65535, only LUNs 0 to 254 should be used for Windows
configurations.
• For an HP 3PAR OS earlier than version 2.3.1, the maximum LUN size supported by the
Windows Server 2008 host is 2 TB; for version 2.3.1 or later, the maximum LUN size supported
by the Windows Server 2008 host is 16 TB.
Discovering LUNs
Use the Server Manager utility to display formation on the disks: click Storage, and click Disk
Management. “Listing Disk Devices” (page 39) shows an example.
38 Allocating Storage for the Windows Server 2008/2012 Host

Figure 16 Listing Disk Devices
You can also use the Emulex One Command Manager or QLogic QConvergeConsole to discover
devices.
Scanning for New Devices on an Windows Server 2008/2012 Host

Disk devices on Windows servers can be used as basic disks or dynamic disks. The HP 3PAR
Storage System already provides most of the extra capabilities of dynamic disks. HP strongly
recommends that HP 3PAR Storage System volumes be used only as basic disks unless 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 are never concurrently exposed to a server. If you need duplicate copies, use the HP 3PAR
Storage System Virtual Copy feature, or break a Windows mirrored set of disks created on two
discrete HP 3PAR Storage System volumes.
For information about dynamic disks with a Windows Server 2008/2012 server, see the following
website:
http://technet.microsoft.com/en-us/library/dd163552.aspx
When VLUNs are exported to the Windows Server 2008/2012 server, they might not appear in
the Windows Disk Manager automatically. After a new VLUN is exported from an HP 3PAR Storage
System iSCSI port, issue a rescan from Windows Disk Manager or Windows Device Manager.
NOTE: Be sure that Windows Disk Manager is closed while you are exporting LUNs, and then
wait until the Windows Device Manager shows all of the new LUN exports before you open the
Windows Disk Manager. Once all LUNs have been shown as available in the Windows Device
Manager, it is safe to proceed to the Windows Disk Manager to initialize and create disk partitions.
To scan for new devices on the Windows Server 2008/2012 host, follow these steps:
Scanning for New Devices on an Windows Server 2008/2012 Host 39

1. In the Windows Server Manager window, click Device Manager.
2. Right-click Disk drives; in the popup that appears, select Scan for hardware changes, as shown
in “Scanning for New Devices ” (page 40).
Figure 17 Scanning for New Devices
Removing a Storage Volume from the Host

To remove a volume from the Windows Server 2008/2012 host, follow standard Microsoft
administrative procedures for removing a volume, and follow the HP 3PAR Storage System standard
procedure to remove a volume.
NOTE: Removing a disk from a Windows Server 2008/2012 host does not erase the data on
the disk. If there is concern about the data on the disk, you might want to use a third party utility
that erases the data on the disk before you remove it from the Windows Server 2008/2012 host.
40 Allocating Storage for the Windows Server 2008/2012 Host

7 Configuring the Windows Server 2008/2012 Host for
an FCoE Connection
This chapter describes the procedures for setting up a Windows Server 2008/2012 host to
communicate over an FCoE initiator between the Windows Server 2008/2012 host and an
HP 3PAR Storage System Fibre Channel target.
FCoE-to-FC Connectivity
Figure 18 (page 41) shows a basic “FCoE-to-FC Connectivity” diagrammatic overview.
Figure 18 FCoE-to-FC Connectivity
Configuring the FCoE Switch and FC Switch

Connect the Windows Server 2008/2012 (FCoE Initiator) host ports to the FCoE-enabled switch
and connect the HP 3PAR Storage System server (FC target) ports of a FC switch.
The FCoE switch must be able to convert FCoE traffic to FC and also be able to trunk this traffic to
the fabric that the HP 3PAR Storage System target ports are connected to. FCoE switch VLANs and
routing setup and configuration are beyond the scope of this document. Consult your switch
manufacturer's documentation for instructions of how to set up VLANs and routing.
FCoE-to-FC Connectivity 41
8 Booting from the HP 3PAR Storage System
For details about connecting the HP 3PAR Storage System to the host, see “Performing Preliminary
HP 3PAR Storage System and Host Configuration” (page 8).
Configuring for iSCSI SAN Boot

For configurations that have iSCSI connections on Windows Server 2008, the Double-Take Flex
software is required.
NOTE: SCSI SAN Boot is not supported on Windows Server 2012 at this time.
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 HP 3PAR Storage
System boot with Fibre Channel storage.
Configuring the BIOS for Fibre Channel SAN Boot

This section explains specific host HBA settings required for booting from an HP 3PAR Storage
System in a fabric configuration. Use the Boot BIOS version listed in the appropriate HP 3PAR OS
InForm Configuration Matrix.
To obtain a copy of this documentation, go to the HP BSC website:
NOTE: With the introduction of the Microsoft Storport driver, booting from a Storage Area
Network (SAN) has become less problematic.
Refer to http://support.microsoft.com/kb/305547.
Configuring for an HP 3PAR Storage System Boot: Emulex HBA

To configure the Emulex HBA, follow these steps:
1. Boot the Windows Server 2008/2012 system following the instructions in the BootBios update
manual.
2. Press Alt-E. For each Emulex adapter, set the following parameters:
• Select Configure the Adapter's Parameters.
• Select Enable or Disable the BIOS; for SAN boot, ensure that the BIOS is enabled.
• Press Esc to return to the previous menu.
• Select Auto Scan Setting; set the parameter to First LUN 0 Device; press Esc to
return to the previous menu.
• Select Topology.
◦ Select Fabric Point to Point for fabric configurations.
◦ Select FC-AL for direct connect configurations.

3. Press Esc to return to the previous menu if you need to set up other adapters. When you are
finished, press x to exit and reboot.
Configuring for an HP 3PAR Storage System Boot: QLogic HBA

Use the QLogic HBA Fast!UTIL utility to configure the HBA. Follow these steps:
1. Boot the Windows Server 2008/2012 server; as the server is booting, press the Alt-Q or
Ctrl-Q keys when the HBA BIOS prompts appear.

2. In the Fast!UTIL utility, click Select Host Adapter and then select the appropriate adapter.
3. Click Configuration Settings→Adapter Settings.
4. In the Adapter Settings window, set the following:
• Host Adapter BIOS: Enabled
• Spinup Delay: Disabled
• Connection Option:
◦ 0 for direct connect
◦ 1 for fabric
NOTE: Record the Adapter Port Name WWWPN for creating the host definition as explained
later in this chapter.
5. Press Esc to exit this window.

6. Click Selectable Boot Settings. In the Selectable Boot Settings window, set Selectable Boot
Device to Disabled.
7. Press Esc twice to exit; when you are asked whether to save NVRAM settings, click Yes.
8. Exit Fast!UTIL.
Creating the Host Definition for an HP 3PAR Storage System Boot: FC

To create the host definition for booting from the HP 3PAR Storage System, issue createhost
-persona 1 <hostname> [<WWN>...].
For example:
# createhost -persona 1 windowshost 10000000C9606724
To verify that the host is created, issue the showhost command.
% showhost
Id Name Persona -------------WWN/iSCSI_Name------------- Port
0 windowshost Generic 10000000C9606724 ---
Connecting the HP 3PAR Storage System to the Host: Fibre Channel

For Fibre Channel HBAs in a Windows Server 2008/2012 host, you do not need to set any
parameters for SAN boot other than those set in “Installing and Configuring an Emulex Fibre
Channel HBA” (page 17) and “Installing and Configuring a QLogic Fibre Channel HBA” (page 17).
Assigning LUN 0 as the Boot Volume

The Windows Server 2008/2012 server must use a LUN specified as 0 as boot volume for a Fibre
Channel SAN boot. To create LUN 0 and assign it as the boot volume, follow these steps:
1. On the HP 3PAR Storage System, create a VV of appropriate size.
2. Export it to the Windows Server 2008/2012 host and specify it as 0. For details, see
“Exporting VLUNs to the Windows Server 2008/2012 Host” (page 38).
3. Restrict the host to a single path connection to the HP 3PAR Storage System. Only a single
path should be available on the HP 3PAR Storage System and a single path on the host to
the VLUN that will be the boot volume.
Creating the Host Definition for an HP 3PAR Storage System Boot: FC 43

Installing the Host OS onto LUN 0: Fibre Channel
The HP 3PAR Storage System supports Windows Server 2008/2012 host boot. You can install
the Windows Server 2008/2012 OS to boot from the HP 3PAR Storage System. Follow all
recommended settings and guides.
To install the Windows Server 2008/2012 OS on HP 3PAR Storage System volumes, follow these
steps:
1. It is recommended that the connection between the HP 3PAR Storage System and the Windows
Server 2008/2012 host system be a single-path connection.
2. Follow standard procedures in the Microsoft documentation for installing the OS on a bootable
device.
3. Reboot the Windows Server 2008/2012 system. The HP 3PAR Storage System volume is
configured with the Windows Server 2008/2012 OS.
Connecting Multiple Paths for Fibre Channel SAN Boot

After the Windows Server 2008/2012 host completely boots up and is online, connect additional
paths to the fabric or the HP 3PAR disk storage system directly by completing the following tasks.
1. On the HP 3PAR Storage System, issue createhost -add <hostname> <WWN> to add
the additional paths to the defined HP 3PAR Storage System host definition.
2. On the Windows Server 2008/2012 host, rescan for devices; see “Scanning for New Devices
on an Windows Server 2008/2012 Host” (page 39).
3. Reboot the Windows Server 2008/2012 system.

9 Using Failover Clustering with Microsoft MPIO
The HP 3PAR Storage System supports failover clustering. Set up the cluster according to Microsoft
recommendations.
45
10 Using Failover Clustering in a Virtualized Environment
The HP 3PAR Storage System supports Failover Clustering on some VMware ESX/ESXi virtualized
environments as Guest OS clustering. For the purposes of setup and configuration, such an
environment is to be considered a VMware ESX configuration.
Setup of the host ESX/ESXi servers should be in accordance with the HP 3PAR VMware ESX
Implementation Guide.
For additional information on the configuration of a Windows Server 2008/2012 Failover Cluster
within a set of virtual machines on VMware ESX, refer to VMware KB-000269-02 (for ESX/ESXi
4.0) or VMware KB-000271-00 (for ESX/ESXi 4.1).
46 Using Failover Clustering in a Virtualized Environment

11 Using the Veritas Cluster Server
Symantec SF 5.1
Symantec SF 5.1 SP1, SP2 introduces a space-reclamation feature to reclaim space 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
feature is available only on dynamic disks (the Veritas DMP I/O policy setting is "Round Robin").
Installing the Veritas Cluster Server

The HP 3PAR Storage System supports use with Veritas Cluster Server and there are no special
setup considerations for the HP 3PAR Storage System server. Refer to the Veritas Cluster Server
Installation Guide and the Veritas Cluster Server User's Guide for installation and setup instructions.
Setting SCSI-3 Persistent Reservation Support for the HP 3PAR Storage

System
For VCS 5.1 Windows, you can enable or disable the SCSI 3 support. Follow these steps:
1. Download latest DDI (DDI-2.1) at http://seer.entsupport.symantec.com/docs/326334.htm.
2. Save the DDI to a folder:
3. Extract DDI files.

4. Verify the HP 3PAR enable/disable script:
DisableSupportSCSI3V3paraa & EnableSupportSCSI3V3paraa
5. By default, the 3PAR Support for SCSI 3 appears as 0x00000000 (0) in the Data column.
To confirm, click
Start→Run→regedit→Computer→Hkey_LOCAL_MACHINE→CurrentControlSet→Services\v3paraa\Parameters.
Symantec SF 5.1 47
6. To enable HP 3PAR SCSI-3 support, click the EnableSupportSCSI3V3paraa script, then reboot
the server after the script runs.
7. After the script runs, the HP 3PAR Support SCSI-3 appears as 0x00000000 (1) in Data
column.
48 Using the Veritas Cluster Server

8. Open the Veritas Enterprise Administrator (VEA) to verify the new settings.
Setting SCSI-3 Persistent Reservation Support for the HP 3PAR Storage System 49
12 Using Microsoft Failover Cluster with Veritas DMP
The HP 3PAR Storage System supports Microsoft failover clustering with Veritas DMP on Windows
Server 2008, but not on Windows Server 2012. Follow Microsoft recommendations when setting
up the cluster, as well as Symantec recommendations when setting up DMP to support Microsoft
clustering (the Veritas DMP I/O policy setting is "Round Robin").
See http://seer.entsupport.symantec.com/docs/306319.htm
Installing the Veritas DMP

When installing Veritas DMP, be sure that 3PARDATA (VA3PARAA) is checked. See Figure 19
(page 50).
Figure 19 Setting Up Veritas Storage for the HP 3PAR Storage Server
50 Using Microsoft Failover Cluster with Veritas DMP

HP 3PAR Windows Server 2008 and Windows Server 2012 Implementation Guide

Uploaded by

Copyright:

Available Formats

HP 3PAR Windows Server 2008 and Windows Server 2012 Implementation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP 3PAR Windows Server 2008 and Windows Server 2012 Implementation Guide

Uploaded by

Copyright:

Available Formats

HP 3PAR Windows Server 2008 and

Windows Server 2012 Implementation

HP Part Number: QL226-96705

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

HP X3000 and XP3000 G2 Storage Systems

HP 3PAR OS Upgrade Considerations

For information about… Read the…

Specific platforms supported HP 3PAR OS InForm Configuration Matrix

Using the HP 3PAR OS Management InForm Management Console Help

HP 3PAR Storage System concepts and HP 3PAR InForm OS Concepts Guide

Using HP 3PAR CIM HP 3PAR CIM API Programming Reference

To obtain a copy of this documentation, see the HP BSC website:

Typeface Meaning Example

ABCDabcd Used to differentiate user input from # cd \opt\3par\console

<ABCDabcd> Used for variables in filenames, # controlport offline <node:slot:port>

Configuring Ports on the HP 3PAR Storage System for a Direct Connection

# controlport offline 1:5:1

Configuring Ports on the HP 3PAR Storage System for a Fabric Connection

8 Performing Preliminary HP 3PAR Storage System and Host Configuration

# controlport offline 0:4:1

# controlport config host –ct point 0:4:1

# controlport rst 0:4:1

Creating the Host Definition

1. To create host definitions, issue the createhost [options] <hostname> [<WWN>...]

# createhost -persona 1 windowshost 10000000C9606724

NOTE: The required port persona value for direct connect is 1.

10 Performing Preliminary HP 3PAR Storage System and Host Configuration

# controlport offline 1:5:1

# controlport persona 7 <node:slot:port>

# controlport persona 7 1:5:1

# controlport rst 1:5:1

Creating the Host Definition (HP 3PAR OS 2.2.x)

# createhost windowshost 10000000C9606724

Installing the HP 3PAR Host Explorer Software

Configuring Microsoft MPIO for HP 3PAR Storage

NOTE: The procedure in this subsection requires rebooting.

12 Performing Preliminary HP 3PAR Storage System and Host Configuration

Configuring MPIO for Round Robin

Setting Up and Zoning the Fabric

14 Performing Preliminary HP 3PAR Storage System and Host Configuration

Configuration Guidelines for Fabric Vendors

Setting Up and Zoning the Fabric 15

Target Port Limits and Specifications

◦ LSI 2G: 510

◦ Emulex 4G: 959

◦ HP 3PAR HBA 4G: 1638

◦ HP 3PAR HBA 8G: 3276 (V400/V800 systems only)

16 Performing Preliminary HP 3PAR Storage System and Host Configuration

Installing and Configuring an Emulex Fibre Channel HBA

Configuring the Emulex Support Driver

Checking Emulex HBA Parameters and Connection Status

Installing and Configuring a QLogic Fibre Channel HBA

Configuring the QLogic Support Driver

Checking the Host Server for Required Drivers 17

Checking QLogic HBA Parameters and Connection Status

Installing Veritas DMP Multipathing on the Windows Server 2008 Host

Figure 3 Setting Up Veritas Storage for the HP 3PAR Storage Server

Disabling the Write Cache Option for HP 3PAR LUNs

Disabling the Write Cache Option for HP 3PAR LUNs 19