HP 3PAR Solaris Implementation Guide

However, in configurations where multiple HP 3PAR StoreServ Storage ports are available for
discovery, some specific target binding may be necessary. The following section describes
considerations for implementing persistent binding for each type of HBA that is supported by the
Solaris OS.
Persistent Target Binding for Emulex lpfc Drivers
By having the automap parameter set to a value of 1 and the fcp-bind-method set to a value of
2 in the /kernel/drv/lpfc.conf file, each HP 3PAR StoreServ Storage port will automatically
be discovered and assigned a target value of 0 each time the host server is booted. For
configurations where a host HBA port logically connects to more than one HP 3PAR StoreServ
Storage port, it can be useful to persistently bind each storage server port to a specified target ID.
This process is discussed in Section (page 10). For more information on setting the persistent target
binding capabilities of the Emulex HBA lpfc driver, consult the Emulex documentation that is
available on the following website:
Emulex
Persistent Target Binding for QLogic qla Drivers
By leaving the binding parameters at their default settings in /kernel/drv/qla2300.conf,
each instance of the qla driver will automatically discover one HP 3PAR StoreServ Storage port
and assign it a target value of 0 each time the Solaris host is booted. The target component of the
device node for each HP 3PAR StoreServ Storage volume will be assigned a target "t" component
equal to 0.
The following example shows the default settings:
hba0-persistent-binding-configuration=0; # 0 = Reports to OS discovery of binded and
non-binded devices
hba0-persistent-binding-by-port-ID=0; # Persistent binding by FC port ID disabled
If a fabric zoning relationship exists such that a host HBA port has access to multiple targets (for
example, multiple ports on the HP 3PAR StoreServ Storage) the driver will assign target IDs (cxtxdx)
to each discovered target in the order that they are discovered. In this case, the target ID for a
given target can change as targets leave the fabric and return or when the host is rebooted while
some targets are not present. If changes in the mapping of a device to its device node (/dev/
rdsk/cxtxdx) cannot be tolerated for your configuration, you can assign and lock the target IDs
based on the HP 3PAR StoreServ Storage port's World Wide Port Name by adding specific target
binding statements in the /kernel/drv/qla2300.conf file. These statements associate a
specified target ID assignment to a specified WWPN for a given instance of the qla driver (a host
HBA port).
For example, to bind HP 3PAR StoreServ Storage WWPN 20310002ac000040 to target ID 6
for qla2300 instance "0", you would add the following statement to
/kernel/drv/qla2300.conf:
hba0-SCSI-target-id-6-fibre-channel-port-name="20310002ac000040";
With this binding statement active, a target with a WWPN of 20310002ac000040 that is
discovered on the host HBA port for driver instance 1, will always receive a target ID assignment
of 6, thus yielding a device node like the one shown in the following example.
/dev/rdsk/c4t6d20s2
hba0-persistent-binding-configuration=0; # 0 = Reports to OS discovery of binded and
36 Configuring the Host for a Fibre Channel Connection