HP 3PAR Solaris Implementation Guide

For configurations that use Veritas Volume Manager for multipathing, virtual volumes should be
exported down multiple paths to the host server simultaneously. To do this, create a host definition
on the HP 3PAR StoreServ Storage that includes the WWNs of multiple HBA ports on the host
server.
NOTE: All I/O to an HP 3PAR StoreServ Storage port should be stopped before running any
HP 3PAR OS CLI controlport commands on that port. The HP 3PAR OS CLI controlport
command executes a reset on the storage server port while it runs and causes the port to log out
of and back onto the fabric. This event will be seen on the host as a "transient device missing"
event for each HP 3PAR StoreServ Storage LUN that has been exported on that port. In addition,
if any of the exported volumes are critical to the host server OS (e.g., the host server is booted
from that volume), the host server should be shut down before issuing the HP 3PAR OS CLI
controlport command.
Exporting LUNs to a Solaris Host with an iSCSI Connection
This section explains how to export VLUNs to the Solaris host when using an iSCSI connection.
The following set of commands is typically used to export a given HP 3PAR StoreServ Storage
virtual volume to all the connected host paths.
# createvv -tpvv -cnt 3 testcpg demo 2g
# createvlun demo.0 0 solarisiscsi
# showvlun -host solarisiscsi
Active vLUNs
Lun VVname Host ---------Host_WWN/iSCSI_Name--------- Port Type
0 demo.0 solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 0:3:1 host
0 demo.0 solarisiscsi iqn.1986-03.com.sun:01:0003bac3b2e1.45219d0d 1:3:1 host
----------------------------------------------------------------
2
VLUN Templates
Lun VVname Host -Host_WWN/iSCSI_Name- Port Type
0 demo.0 solarisiscsi ---------------- --- host
-----------------------------------------------
1
• Even though the HP 3PAR StoreServ Storage supports the exportation of VLUNs with LUN
numbers in the range from 0 to 16383, only VLUN creation with a LUN in the range from 0
to 255 is supported.
• This configuration does support sparse LUNs (the skipping of LUN numbers).
• LUNs may be exported in non-ascending order (e.g. 5, 7, 3, 200).
• Only 256 VLUNs can be exported on each interface. If you export more than 256 VLUNs,
VLUNs with LUNs above 255 will not appear on the Solaris host.
• If you are using Solaris multipath I/O (Solaris StorEdge Traffic Manager) you should avoid
reusing a LUN number to export a different HP 3PAR StoreServ Storage volume as the Solaris
format output preserves the disk serial number of the first device ever seen on that LUN number
since the last reboot.
CAUTION: If any I/O is performed on the old disk serial number, the I/O will be driven to the
new volume and can cause user configuration and data integrity issues. This is a general Solaris
issue with Solaris multipath I/O and is not specific to the HP 3PAR StoreServ Storage target.
The following is an example:
If the HP 3PAR StoreServ Storage volume demo.50 that has device serial number
50002AC01188003E is exported to LUN 50 and the format command output shows the correct
Exporting LUNs to a Solaris Host with an iSCSI Connection 53