HP 3PAR VMware ESX Implementation Guide

For HP 3PAR OS 3.1.2 or later, using persona 11:
# showhost
Id Name Persona -WWN/iSCSI_Name- Port
0 ESXserver2 VMware 100000051EC33E00 --- 100000051EC33E01 ---
Use showhost -persona to show the persona name and Id relationship.
# showhost -persona
Id Name Persona_Id Persona_Name Persona_Caps
0 ESXserver1 6 Generic-legacy --
1 Esxserver2 11 VMware SubLun, ALUA
NOTE: If the persona is not correctly set, then use the sethost -persona <host
number> <hostname> command to correct the issue, where host number is 6 (for HP 3PAR
OS 3.1.1 or earlier) or 11 (recommended for HP 3PAR OS 3.1.2 or later).
A reboot of the ESX host is required if host persona is changed to 11. The host must be offline
or not connected in order to change the host persona from 6 to 11 or 11 to 6.
NOTE: See the HP 3PAR Command Line Interface Reference or the HP 3PAR Management Console
Users Guide for complete details on using the controlport, createhost, and showhost
commands.
These documents are available on the HP SC website:
HP Support Center
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:
• For information available on host port per target port and max total host ports per array, refer
to the HP 3PAR Feature Availability Matrix documentation available on the HP Single Point
of Connectivity Knowledge (HP SPOCK) website:
HP SPOCK
• I/O queue depth on each HP 3PAR StoreServ Storage HBA model, as follows:
◦ QLogic CNA: 1748 (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. If this condition occurs, each host should be throttled so that it
cannot overrun the HP 3PAR StoreServ Storage port's queues when all hosts are delivering
their maximum number of I/O requests.
NOTE: When host 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 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 reboot. This issue can occur with any fabric-connected storage, and is
not specific to the HP 3PAR StoreServ Storage.
Target Port Limits and Specifications 35