HP 3PAR VMware ESX Implementation Guide Abstract This implementation guide provides information for establishing communications between an HP 3PAR StoreServ Storage and a VMware ESX host. General information is also provided on the basic steps required to allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by the ESX host.
© Copyright 2013 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.
Contents 1 Introduction...............................................................................................6 Supported Configurations..........................................................................................................6 HP 3PAR OS Upgrade Considerations.........................................................................................7 Audience................................................................................................................................
Script Alternative for Path Policy Changes on Storage Devices without a Host Reboot..............46 Performance Considerations for Multiple Host Configurations........................................................47 ESX/ESXi Handling SCSI Queue Full and Busy Messages from the HP 3PAR StoreServ Storage Array...............................................................................................................................47 VMware ESX Releases through ESX 3.5 Update 3............................
HP 3PAR documentation..........................................................................................................85 Typographic conventions.........................................................................................................88 HP 3PAR branding information.................................................................................................88 11 Documentation feedback..........................................................................
1 Introduction This implementation guide provides information for establishing communications between an HP 3PAR StoreServ Storage and a VMware ESX host. General information is also provided on the basic steps required to allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by the ESX host.
HP 3PAR OS Upgrade Considerations For information about planning an online HP 3PAR Operating System (HP 3PAR OS) upgrade, see the HP 3PAR Operating System Upgrade Pre-Planning Guide, which is available on the HP Business Support Center (BSC) website: http://www.hp.com/go/bsc For complete details about supported host configurations and interoperability, consult the HP SPOCK website: http://www.hp.
2 Configuring the HP 3PAR StoreServ Storage for Fibre Channel This chapter explains how to establish a Fibre Channel connection between the HP 3PAR StoreServ Storage and a VMware ESX host and covers HP 3PAR OS 3.1.x, OS 2.3.x, and 2.2.x versions. For information on setting up the physical connection for a particular HP 3PAR StoreServ Storage, see the appropriate HP 3PAR installation manual. Configuring the HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or OS 2.3.
2. If the port has not been configured, take the port offline before configuring it for the ESX host by issuing the following HP 3PAR OS CLI command: controlport offline [node:slot:port] CAUTION: Before taking a port offline in preparation for a direct or fabric connection, you should verify that the port has not been previously defined and that it is not already connected to a host as this would interrupt the existing host connection.
2. To create host definitions, issue the createhost command with the -persona option to specify the persona and the host name. For HP 3PAR OS 3.1.1 or earlier: # createhost -persona 6 ESXserver1 10000000C9724AB2 10000000C97244FE For HP 3PAR OS 3.1.2: # createhost -persona 11 ESXserver1 10000000C9724AB2 10000000C97244FE 3. To verify that the host has been created, issue the showhost command. For HP 3PAR OS 3.1.
NOTE: For configurations that are intended to have more than one host type (for example, an ESX host and a Windows host) connected to a shared HP 3PAR StoreServ Storage HBA port via fabric connections, see to the Heterogeneous Host Support Guide on the HP BSC website for the required HP 3PAR StoreServ Storage port settings and interoperability considerations: http://www.hp.com/go/bsc NOTE: By default, the VMware ESX host supports failover.
Creating the Host Definition Before connecting the ESX host to the HP 3PAR StoreServ Storage, create a host definition for each HP 3PAR StoreServ Storage that is to be connected to a host HBA port through a fabric or a direct connection. 1. To create host definitions, issue the HP 3PAR OS CLI createhost command with the appropriate host name. For example: # createhost ESXserver1 10000000C9724AB2 10000000C97244FE 2. To verify that the host has been created, issue the HP 3PAR OS CLI showhost command.
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 StoreServ Storage, the WWN zoning method is recommended because the zone survives the changes of switch ports when cables are moved around on a fabric.
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.
◦ HP 3PAR HBA 4G: 1638 ◦ HP 3PAR HBA 8G: 3276 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systems only) • The I/O queues are shared among the connected host HBA ports on a first-come, first-served basis. • When all queues are in use and a host HBA port tries to initiate I/O, it receives a target queue full response from the HP 3PAR StoreServ Storage port. This condition can result in erratic I/O performance on each host.
In HP 3PAR Storage arrays with more than two nodes, failover behavior occurs on node pairs; that is, if node 0 goes down, ports on node 0 fail over to node 1, if node 2 goes down, ports on node 2 fail over to node 3, and so on. Conversely, when node 1 goes down, ports on node 1 fail over to node 0, and when node 3 goes down, ports on node 3 fail over to node 2. When the downed node is up again, the failed-over ports automatically fail back to their original ports.
Before Persistent Ports is active, the output of the showhost command displays as follows: # showhost Id Name 1 server1 Persona Generic ---------------WWN/iSCSI_Name--------------5001438009AE770E 5001438009AE770C 5001438009AE770E 5001438009AE770C Port 0:1:1 0:1:1 1:1:1 1:1:1 When Persistent Ports is active, the output of the showhost command, under the Port column, shows both the physical port and the physical port where Persistent Ports is active.
3 Configuring the HP 3PAR StoreServ Storage for iSCSI This chapter explains how to establish an iSCSI connection between the HP 3PAR StoreServ Storage and the VMware ESX host. If you are running specific CNA cards, a software or hardware iSCSI initiator can be used. For details about hardware iSCSI configuration, see “Hardware iSCSI Support” (page 25).
3. Issue the HP 3PAR OS CLI showport -iscsi command to check the current settings of the iSCSI ports: # showport -iscsi N:S:P State IPAddr iSNS_Port 0:1:1 offline 0.0.0.0 3205 1:1:1 offline 0.0.0.0 3205 0:1:1 offline 0.0.0.0 3205 1:1:1 offline 0.0.0.0 3205 4. Netmask Gateway TPGT MTU Rate DHCP iSNS_Prim iSNS_Sec 0.0.0.0 0.0.0.0 11 1500 n/a 0 0.0.0.0 0.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.0 0.0.0.0 0.0.0.0 111 1500 n/a 0 0.0.0.0 0.0.0.0.0 0.0.0.0 0.0.0.
ESX/ESXi uses the generic legacy host persona of 6 for HP 3PAR OS 3.1.1 or earlier. As of HP 3PAR OS 3.1.2, a second host persona 11 (VMware), which enables asymmetric logical unit access (ALUA) is available. Host persona 11 (VMware) is recommended for new ESX/ESXi installations and is required for ESX/ESXi hosts configured as part of a HP 3PAR Peer Persistence configuration.
ports must have been set up and an iSCSI connection/session must be established. The iSCSI connection/session is established by following the steps in “Setting Up the Ports for an iSCSI Connection” (page 18) and the steps in “Configuring the Host for an iSCSI Connection” (page 65) through section “Configuring the VMware iSCSI Initiator” (page 72) (ESX host setup). The following example of host definition creation depicts a VMware iSCSI initiator iqn.1998-01.com.
The following example uses the CHAP secret (CHAP password) host_secret3 for the ESX host. Be aware that the CHAP secret must be at least 12 characters long. 2. On the ESX host’s VI/vSphere client, open the Storage Adapters tab, then select the iSCSI Software Adapter, and select the Properties link. Then, on the General tab, click CHAP. For ESX 3.5, select the CHAP Authentication tab, and then select the Use the following CHAP credentials radio button. Figure 1 CHAP Authentication in ESX 3.
Figure 2 CHAP Credentials in ESX/ESXi 4.x or ESX/ESXi 5.x 3. 4. Enter the CHAP Secret (must be at least 12 characters long). Use the same secret that you enter on the storage side. Click OK when you are done. A warning screen appears indicating that a reboot of the ESX host is required. NOTE: A server reboot is required for ESX 3.5. For ESX 4.x and ESXi 5.x, a rescan of the HBA should pick up the changes.
5. 6. Click OK again to confirm. On the HP 3PAR StoreServ Storage, issue the HP 3PAR OS CLI sethost command with the initchap parameter to set the CHAP secret for the ESX host. # sethost initchap -f host_secret3 ESX1 NOTE: If mutual CHAP on ESX is being configured, then target CHAP will need to be configured on the HP 3PAR StoreServ Storage as well as initiator CHAP. Set target CHAP secret using the HP 3PAR OS CLI sethost command with the targetchap parameter.
Figure 3 CHAP Credentials in ESX 4.x and 5.x Issue the HP 3PAR OS CLI showhost -chap command to verify that the specified CHAP secret has been set for the host definition. For Initiator chap # showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name0 ESX1 ESX1 -For mutual chap # showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name0 ESX1 ESX1 s331 Hardware iSCSI Support At ESX 5.0 and above, hardware iSCSI is supported using the CN1100E CNA card and other Emulex BE3 models.
2. Press Ctrl+S to enter the utility. Figure 4 iSCSI Utility 3. 4. 5. Select a controller and press Enter. From the Controller Configuration screen, select Network Configuration and press Enter. In the Network Configuration screen, select Configure Static IP Address and press Enter. The screen for setting a static IP address displays. Figure 5 Setting a Static IP Address 6. After entering the IP address, subnet mask, and default gateway, click Save to return to the Controller Configuration menu.
1. After entering the iSCSI Initiator Configuration screen, which will be the first screen displayed, obtain the IQN for the card and create a host definition on the HP 3PAR StoreServ Storage. For example: # createhost –iscsi –persona 11 Esx50Sys1 iqn.1990-07.com.emulex:a0-b3-cc-1c-94-e1 2. 3. 4. 5. 6. 7. Assign a VLUN to this host definition to be used as the SAN boot LUN. From the Controller Configuration menu, select Controller Properties. In the properties screen, verify that boot support is enabled.
11. If you do not want to use CHAP as an authentication method, exit the CN1100E setup screens and reboot now. If you would like to use CHAP as an authentication method, return to the Add/Ping iSCSI Target screen as shown in “Adding an iSCSI Target” (page 27), select Authentication Method, and then choose one of the following options: • Select One-Way CHAP (see “One-Way CHAP” (page 28)). Figure 7 One-Way CHAP The CHAP Configuration screen appears (see “CHAP Configuration for One-Way CHAP” (page 28)).
Figure 9 CHAP Configuration for Mutual CHAP Fill in the Target CHAP Name (the initiator IQN name), the Target Secret, the Initiator CHAP Name (which is the DNS name of the storage), and an Initiator Secret, and then click OK. • If you want to remove CHAP authentication later on, in the Authentication Method setting on the Add-Ping iSCSI Target screen (“One-Way CHAP” (page 28)), select None. 12.
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: • I/O queue depth on each HP 3PAR StoreServ Storage HBA model, as follows: ◦ QLogic 1G: 512 ◦ QLogic 10G: 2048 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systems only) • The I/O queues are shared among the connected host HBA ports on a first-come, first-served basis.
4 Configuring the HP 3PAR StoreServ Storage for FCoE Setting Up the FCoE Switch, FCoE Initiator, and FCoE target ports Connect the ESX host FCoE initiator port(s) and the HP 3PAR StoreServ Storage FCoE target ports to the FCoE switch(es). NOTE: FCoE switch VLANs and routing setup and configuration is beyond the scope of this document. Consult your switch manufacturer's documentation for instructions of how to set up VLANs and routing. 1.
NOTE: If changing the config from iSCSI to FCoE, follow the steps below. 1. Issue the showportcommand. # showport 0:3:1 target 0:3:2 target 2. ready ready - 000E1E05BEE6 iscsi 000E1E05BEE2 iscsi iSCSI iSCSI - - Turn off the iSCSI ports: # controlport offline 0:3:1 # controlport offline 0:3:2 showport 0:3:1 target offline - 000E1E05BEE2 iscsi iSCSI0:3:2 target offline 000E1E05BEE2 iscsi iSCSI 3.
Creating the Host Definition Before connecting the ESX host to the HP 3PAR StoreServ Storage, a host definition needs to be created that specifies a valid host persona (host mode) for each HP 3PAR StoreServ Storage port that is to be connected to a host HBA port through a fabric or direct connection. • ESX/ESXi uses the generic legacy host persona of 6 for HP 3PAR OS 3.1.1 or earlier. • As of HP 3PAR OS 3.1.
Use showhost -persona to show the persona name and Id relationship. # showhost -persona Id Name Persona_Id 0 ESXserver1 6 1 Esxserver2 11 Persona_Name Generic-legacy VMware Persona_Caps -SubLun, ALUA NOTE: If the persona is not correctly set, then use the sethost -persona command to correct the issue, where host number is 6 (for HP 3PAR OS 3.1.1 or earlier) or 11 (for HP 3PAR OS 3.1.2). A reboot of the ESX host is required if host persona is changed to 11.
5 Configuring the Host for a Fibre Channel Connection This chapter describes the procedures and considerations that are required to set up an ESX host to communicate with an HP 3PAR StoreServ Storage over a Fibre Channel connection. Installing the HBA and Drivers Before setting up the ESX host, make sure the host adapters are installed and operating properly. If necessary, consult the documentation provided by the HBA vendor for instructions.
To change Path TOV value (repeat for all ports) follow the example below. Also this command can be included in ESX host startup such that it will be run automatically. # esxcli brocade bcu --command="fcpim --pathtov 1/0 14" path timeout is set to 14 To query a port# after a change was made, follow the example below: # esxcli brocade bcu --command="vhba --query 1/0" PCI Function Index : 1/0/0 Firmware Ver : 3.0.0.
NOTE: VMware and HP recommend the LSI logic adapter emulation for Windows 2003 Servers. The LSI Logic adapter is also the default option for Windows 2003 when creating a new virtual machine. HP testing has noted a high incidence of Windows 2003 virtual machine failures during an ESX multipath failover/failback event when the BUS Logic adapter is used with Windows 2003 VMs.
Fibre Channel” (page 39) for procedures on implementing and configuring the round-robin path policy on ESX/ESXi 4.0 and later with an HP 3PAR StoreServ Storage. • A path policy of "round-robin" is the preferred multipath implementation for ESX/ESXi 4.0 and later. For procedures on implementing and configuring the round-robin path policy on ESX/ESXi 4.0 and later with an HP 3PAR StoreServ Storage, see “Configuring Round Robin Multipathing on ESX 4.x or later for Fibre Channel” (page 39).
• A path policy of MRU (most recently used) does not maintain or reinstate balancing of I/O load after a failover/failback multipath event. This could leave I/O in an unplanned for and unbalanced state which may yield significant I/O performance issues. Implementation of an MRU path policy is not recommended by HP.
Figure 10 LUN Set to Round Robin Managing a round robin I/O path policy scheme through the VI/vSphere client GUI for a large network can be cumbersome and challenging to maintain because the policy must be specified for each LUN individually and updated whenever new devices are added.
NOTE: • SATP rule changes cannot be affected through vSphere GUI. • SATP rule changes through esxcli commands populate the esx.conf file. • A custom SATP rule is an added SATP rule that modifies or redefines parameters of an existing SATP default rule, defines the targeted devices to be affected, and is given a unique custom rule name. • A custom SATP rule cannot be changed/edited.
ESX/ESXi 4.0 GA - 4.0 Ux NOTE: • Though ESX 4.0 GA - 4.0 Ux supports custom SATP rules, the -P options for setting PSP (path policy) within the custom rule are not supported. PSP must be defined within the default SATP rules. • ESX 4.0 GA - 4.0 Ux has a known issue wherein no attempt should be made to change iops from its default value of 1000 (iops = 1000). If the iops value is changed, upon the next host reboot, an invalid value for iops is picked up and iops are then unpredictable.
CAUTION: The procedure for changing the default SATP rules to use the round robin I/O multipathing policy is intended to apply only to VMware hosts using HP 3PAR StoreServ Storage LUNs. If the host is sharing storage from other vendors, then before making any I/O policy changes, consideration should be given to the effect that changing the default rules will have on the storage environment as a whole.
To remove the above Active-Active custom SATP rule: # esxcli storage nmp satp rule remove -s "VMW_SATP_DEFAULT_AA" -P "VMW_PSP_RR" -O iops=100 –c "tpgs_off" -V "3PARdata" -M "VV" -e "HP 3PAR Custom iSCSI/FC/FCoE Rule" HP 3PAR custom SATP rule for use with persona 11/VMware (ALUA compliant array port presentation) # esxcli storage nmp satp rule add -s "VMW_SATP_ALUA" -P "VMW_PSP_RR" -O iops=100 -c "tpgs_on" -V "3PARdata" -M "VV" -e "HP 3PAR Custom iSCSI/FC/FCoE ALUA Rule" To remove the above ALUA custom SA
SATP Custom Rules and Associated Defined Parameters To list SATP custom rules and associated defined parameters, issue the following commands: ESXi 5.x example For persona 11: For persona 6: ESX/ESXi 4.x example # esxcli nmp satp listrules | grep -i 3par VMW_SATP_ALUA 3PARdata VV tpgs_on HP 3PAR Custom iSCSI/FC/FCoE ALUA Rule Show Device Information To show device information, issue the following commands: ESXi 5.x example # esxcli storage nmp device list naa.
ESX/ESXi 4.x example The command is the same for ESX/ESXi 4.x. The output shown is for ESX 4.0: # esxcli nmp device list naa.50002ac000b40125 Device Display Name: 3PARdata Fibre Channel Disk (naa.
ESX/ESXi 4.x # esxcli nmp device list -d naa.50002ac0005800ac NOTE: occur: If I/O is active to a LUN and an attempt is made to modify the path policy, a failure can error during the configuration of the host: sysinfoException; Status=Busy: Message=Unable to Set If this problem occurs during an attempt to change the path policy, reduce the I/Os to that LUN and then try making the desired changes.
VMware ESX Release 3.5 Update 4 through ESX 4.x and ESXi 5.0 As of VMware ESX release 3.5 update 4, and including ESX 4.0 GA and ESX 4.1 (with all ESX 4.x updates) , and ESXi 5.0 (with all updates), an algorithm has been added that allows ESX to respond to Queue Full and Busy SCSI messages from the storage array. The Queue Full or Busy response by ESX is to back off of I/O for a period of time, thus helping to prevent overdriving of the HP 3PAR StoreServ Storage ports.
Follow-up Actions/Recommendations for ESX 3.5 Update 3 and Earlier The behavior of the HP 3PAR StoreServ Storage port being overrun is limited only to ESX 3.5 update 3 and earlier servers. Other HP-supported operating systems handle Queue Full notifications by backing off on I/O for a period of time. HP currently does not have any HP 3PAR StoreServ Storage firmware to address this issue but there are recommendations that can help prevent this problem from occurring as detailed in the following sections.
Example 2 (set up as follows): • LSI 2G FC HBA installed on the HP 3PAR StoreServ Storage • 12 ESX hosts attached to a LSI port on the HP 3PAR StoreServ Storage Formula: 510 / 12 = 42.xxx (recommended max target port queue depth = 42) Setting tgt_queue_depth for Emulex in ESX 3.x (example) To set the tgt_queue_depth for an Emulex FC HBA in ESX 3.x to something other than the default requires a multistep process: 1. Shut down all of the virtual machines. 2. Log into the ESX service console as root. 3.
3. Make a backup copy of /etc/vmware/esx.conf. cp /etc/vmware/esx.conf /etc/vmware/esx.conf.orig 4. Identify the QLogic HBA module that is currently loaded. vmkload_mod -l | grep qla2300 Depending on the model of the HBA, the module can be one of the following: qla2300_707 (ESX 3.0.x) qla2300_707_vmw (ESX 3.5) 5. The target port queue depth can now be modified via the service console command line using VMware supplied binaries. The example shows the qla2300_707 module.
ESX extensions that make use of these primitives are collectively referred to as vStorage APIs for Array Integration (VAAI). The VMware primitives enable an ESX/ESXi host to convey virtual machine operations to storage hardware at a meta level instead of at the traditional data level. This reduces operational latency and traffic on the FC fabric/iSCSI network. Some of these primitives enable the storage hardware to participate in block allocation and de-allocation functions for virtual machines.
NOTE: VAAI Plugin 2.2.0 is required if the ESXi 5.x server is connected to two or more arrays that are running a mix of OS HP 3PAR OS 2.3.1.x and OS 3.1.x. For LUNs on HP 3PAR OS 3.1.x, the default VMware T10 plugin will be effective, and for storage LUNs on HP 3PAR OS 2.3.x, HP 3PAR VAAI Plugin 2.2.0 will be effective. For more information, refer to the HP 3PAR VAAI Plug-in Software for VMware vSphere User's Guide (HP part number QL226-96072).
additional disk space is added, use the Retry option on the warning message to bring the VM back to the read-write state. If you select the Cancel option, the VM is rebooted. In the following example, an HP 3PAR StoreServ Storage TPVV volume was created with a warning limit of 60%, as shown in the showvv -alert command. When the warning limit is reached, the HP 3PAR StoreServ Storage sends a soft threshold error asc/q: 0x38/0x7 and ESX continues to write.
Figure 11 Virtual Machine Message — Retry and Cancel options Additional New Primitives Support on ESXi 5.x HP 3PAR OS 3.1.1 or later supports additional new primitives, called TP LUN Reporting, where the ESXi 5.x is notified that a given LUN is a thin provisioning LUN by enabling the TPE bits of the READ Capacity (16) and enables the host to use features such as sending the UNMAP command to these LUNs. The TPE bit is enabled for TPVVs and R/W snapshot of TPVV base.
VAAI Plugin Verification NOTE: VAAI Plugin 2.2.0 must be installed if an ESXi 5.x server is connected to two or more arrays that are running a mix of HP 3PAR OS 2.3.x and 3.1.x. For LUNs from HP 3PAR OS 3.1.x, the default VMware T10 plugin will be effective, and for storage LUNs from HP 3PAR OS 2.3.x, HP 3PAR VAAI Plugin 2.2.0 will be effective. To verify that VAAI 2.2.0 is installed on ESXi 5.
• On ESX 4.1, you can verify that the VAAI Plugin is installed and enabled on devices using the following commands: • To show the version of the installed VAAI plugin: # esxupdate --vib-view query | grep 3par cross_3par-vaaip-inserv_410.1.1-230815 installed • To show that the claim rule is in effect for the HP 3PAR devices discovered: • To show that the VAAI is supported on the device: # esxcfg-scsidevs -l naa.
Figure 12 Hardware Acceleration for HP 3PAR devices VMware All Paths Down All Paths Down (APD), a feature of the VMware ESXi host used in cases where all paths to the VM go down because of storage failure or administrative error, is properly handled in ESX 5.1 as a result of feature enhancement performed by VMware. Previously, in ESX versions 5.0 or 4.1, the host would try continuously to revive the storage links and, as a result, performance would be impacted for working VMs.
6 Configuring the Host as an FCoE Initiator Connecting to a FC target or an FCoE Target All contents of the Fibre Channel section of this guide apply to FCoE connectivity as well. See the following sections: • “Multipath Failover Considerations and I/O Load Balancing” (page 37) • “Performance Considerations for Multiple Host Configurations” (page 47) • “ESX/ESXi 4.1, ESXi 5.
Figure 13 Configuring FCoE 2. In the System Options pane, select NIC Personality Options. Figure 14 NIC Personality Options 3. 60 In the PCI Slot 2 Pane, select FCoE for both Port 1 and Port 2.
Figure 15 Configuring the PCI Slots 4. PCI Slot 2 Port 1 and Port 2 now display FCoE. Figure 16 PCI Slot 1 and Slot 2 Configured for FCoE 5. Save the changes and exit the BIOS.
Figure 17 Exiting the BIOS Utility Configuring an HP 3PAR StoreServ Storage Port for a FCoE Host Connection When setting up FCoE initiator to FC target, there is nothing unique that needs to be configured on the HP 3PAR StoreServ Storage. The initiator coming from the host adapters through the FCoE Forwarder switch is treated as just another Fibre Channel device connecting to the HP 3PAR StoreServ Storage ports.
Figure 18 Initiator FCoE to FC Target NOTE: For complete and detailed instructions for configuring a server with a given Converged Network Adapter, refer to the CNA manufacturer documentation. The FCoE switch or FCoE forwarder must be able to convert FCoE traffic to FC and also be able to trunk this traffic to the fabric that the HP 3PAR StoreServ Storage target ports are connected to. 1. 2. 3. 4. 5.
Figure 19 Initiator FCoE to Target FCoE 1. 2. 3. 4. 5. Install the CNA card in the server just like any other PCIe card - refer to the server vendor documentation. Install the CNA card driver following the CNA card installation instructions (it assumes the server is already running a supported operating system). Physically connect the server CNA card ports to the FCoE fabric.
7 Configuring the Host for an iSCSI Connection This chapter describes the procedures for setting up an ESX software iSCSI configuration with an HP 3PAR StoreServ Storage. The instructions in this chapter should be used in conjunction with the VMware vSphere Storage Guide. Setting Up the Switch, iSCSI Initiator, and iSCSI target ports Connect the ESX host iSCSI initiator port(s) and the HP 3PAR StoreServ Storage iSCSI target ports to the switch(es).
NOTE: When multiple teamed NICs are configured, all HP 3PAR StoreServ Storage iSCSI ports and ESX iSCSI NICs must be in the same VLAN of the IP switch. NOTE: 66 NIC teaming is not supported in ESXi 5.
Installing Virtual Machine Guest Operating System The VMware ESX documentation lists recommended virtual machine guest operating systems (GOS) and their installation and setup as virtual machines. Refer to the VMware ESX documentation for information on setting up your virtual machine configuration. CAUTION: In VMware KB 51306, VMware identifies a problem with RHEL 5 (GA), RHEL 4 U4, RHEL 4 U3, SLES 10 (GA), and SLES 9 SP3 guest operating systems.
3. Click the Add Networking Link. The Add Network wizard appears. 4. Select VMkernel and click Next. This lets you connect to the VMkernel which runs services for iSCSI storage to the physical network. The Network Access page appears. Select Create a Virtual Switch and select the NICs that will be used for iSCSI. (In this example, 2 NICs are selected to configure an active/active teamed NICs that will connect to the HP 3PAR storage array.) Click Next. In ESX 4.
8. Click OK to complete. NOTE: HP recommends an Active/Active NIC Teaming configuration for best failover performance. NIC Teaming however, is not supported with ESXi 5.x. 9. Click Next.
10. Enter a network label. Click Next. 11. Specify the IP settings that will be used for the iSCSI network. Click Next. 12. Review the information. Click Finish . Configuring a Service Console Connection for the iSCSI Storage The following steps describe how to configure the Service Console connection for the iSCSI storage. 1. From the Configuration tab, and the Networking tab, click Properties for the vSwitch associated with the VMkernel port you just created for the iSCSI network. 2. 3. 4.
5. 6. Enter the Network Label and IP address for the Service console used to communicate with the iSCSI software initiator. The IP address must be in the same subnet as the iSCSI. Click Next. A window appears showing the changes/additions that have been made. 7. 8. Click Finish. Close all windows associated with the network configuration.
9. Check the Configuration display. The new network configuration is displayed with the addition of the iSCSI network. You should now be able to ping the HP 3PAR StoreServ Storage ports that were previously defined from the COS. Configuring the VMware iSCSI Initiator The following steps show how to configure the VMware iSCSI initiator. 1. With the Configuration tab selected, click the Security Profile→Firewall Properties option from the Software menu box. 2. 3.
4. In the ESX host, select the Configuration tab. Then select iSCSI Software Adapter in Storage Adapter. 5. Click the Properties tab. 6. Select the General tab. 7. Click Configure... 8. Select the Enabled check box for the status. 9. Click OK. 10. Click the Dynamic Discovery tab. Dynamic discovery enables the Send Targets discovery method, where the initiator sends the Send Targets request to discover and log into the targets.
11. 12. 13. 14. 74 Click Add.... Enter the IP address of one of the previously defined HP 3PAR StoreServ Storage iSCSI ports. Click OK. Add additional HP 3PAR StoreServ Storage iSCSI ports if they exist and have been defined on the system.
15. When all of the desired HP 3PAR StoreServ Storage iSCSI ports have been added to the Dynamic Discovery tab, close this window.
16. Reboot the ESX host. If virtual machines are active, shut them down or suspend them. The ESX host and HP 3PAR StoreServ Storage should now be configured for use. Using the showhost command on the HP 3PAR StoreServ Storage, the new iSCSI connections should now show as present. # showhost Id Name -- ----------------WWN/iSCSI_Name---------------- Port iqn.1998-01.com.vmware:hpdl380-01-11a38a59 0:1:2 iqn.1998-01.com.
NOTE: If you are running W2K8 VM Cluster with RDM-shared LUNs, then individually change these specific RDM LUNs from Round Robin policy to Fixed Path policy. NOTE: HP recommends changing the ESX Scsi.ConflictRetries from its default value of 80 to a value of 200 when connected to an HP 3PAR StoreServ Storage running HP 3PAR OS version 2.2.4 or prior.
8 Allocating Storage for Access by the ESX Host This chapter describes the basic procedures that are required to create and export virtual volumes so they can be utilized by the VMware ESX host. For complete details on creating and managing storage on the HP 3PAR StoreServ Storage, consult the appropriate HP 3PAR documentation.
Creating Virtual Volumes for HP 3PAR OS 2.2.3 or Earlier When running HP 3PAR OS 2.2.3 or earlier, the createaldvv command can be used to create virtual volumes on the HP 3PAR StoreServ Storage that can then be exported and discovered by the ESX host. Here is the general form of the command: # createaldvv [options] [.] [g|G|t|T] Here is an example: # createaldvv -cnt 5 TESTLUNs 5G This will create five virtual volumes of 5 Gb each in size, fully provisioned from PDs.
http://www.hp.com/go/bsc Concerning TPVVs, ESX VMFS-3 does not write data to the entire volume at initialization and it can be used with TPVVs without any configuration changes to VMFS. A further examination of this subject, recommendations, and limitations are explored in the HP document 3PAR Utility Storage with VMware vSphere. Creating a VLUN for Export Creation of a VLUN template enables export of a VV as a VLUN to one or more ESX hosts.
Consult the HP 3PAR Management Console Users Guide and the HP 3PAR Command Line Interface Reference for complete details on exporting volumes and available options for the HP 3PAR OS version that is being used on the HP 3PAR StoreServ Storage. These documents are available on the HP BSC website: http://www.hp.com/go/bsc NOTE: The commands and options available for creating a virtual volume may vary for earlier versions of the HP 3PAR OS.
Figure 20 Detaching a LUN Host and Storage Usage Eventlog and Host Log Messages All HP 3PAR system debug messages can be seen using the showeventlog -debug cli command. On the ESX host, errors are reported in /var/log/vmkernel files. Use the showalert HP 3PAR OS CLI command to see alerts and warnings posted from the HP 3PAR StoreServ Storage.
At an interval of every 5 minutes, an ESX host such as ESXi 5.x sends REPORT LUN commands and discovers any new LUNs. On ESXi 5.x, the following vmkernel log message is not harmful and can be ignored: 34:41.371Z cpu0:7701)WARNING: ScsiDeviceIO: 6227: The device naa.50002ac00026011b does not permit the system to change the sitpua bit to 1. For ESXi 5.x, the Virtual Disk max disk can be only 2 TB, even though the physical LUN seen on the system is 16 TB.
9 Booting the VMware ESX Host from the HP 3PAR StoreServ Storage This chapter provides a general overview of the procedures that are required to boot the VMware ESX operating system from the SAN. In a boot-from-SAN environment, each ESX host’s operating system is installed on a the HP 3PAR StoreServ Storage, rather than on the host’s internal disk. In this situation, you should create a separate virtual volume for each ESX host to be used for the boot image.
10 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
For information about: See: Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide 86 Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems HP 3PAR Secure Service Custodian Configuration Utility Reference Using the CLI to configure and manage HP 3PAR Remote Copy HP 3PAR Remote Copy Software User’s Guide Updating HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage system compo
For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physic
Typographic conventions Table 4 Document conventions Convention Element Bold text • Keys that you press • Text you typed into a GUI element, such as a text box • GUI elements that you click or select, such as menu items, buttons, and so on Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values • Code variables • Command variables Bold monospace text • Commands you enter into a command line interface • System
11 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.