HP 3PAR Solaris Implementation Guide

non-binded devices
hba0-persistent-binding-by-port-ID=0; # Persistent binding by FC port ID disabled
The current HBA driver instance matching to discovered target WWPN associations (for connected
devices) can be obtained from entries in the /var/adm/messages file generated from the last
server boot.
# grep fibre-channel-port /var/adm/messages
sunb1k-01 qla2300: [ID 558211 kern.info]
hba0-SCSI-target-id-0-fibre-channel-portname="20310002ac000040";
sunb1k-01 qla2300: [ID 558211 kern.info]
hba1-SCSI-target-id-0-fibre-channel-portname="21510002ac000040";
New or edited binding statement entries can be made active without rebooting the Solaris host by
issuing the following command:
# /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig -d qla2300
This command enables the persistent binding option in /kernel/drv/qla2300.conf:
hba0-persistent-binding-configuration=1;
CAUTION: This procedure should not be attempted while I/O is running through the qla driver
instances as it will briefly interrupt that I/O and may also change a discovered device's device
nodes if there have been changes made to the persistent binding statements.
While running with Persistent binding only enabled, only persistently bound targets and
their LUNs will be reported to the operating system.
If the persistent binding option is disabled in /kernel/drv/qla2300.conf, changes to persistent
target binding will only take effect during the next host server reboot.
hba0-persistent-binding-configuration=0;
While running with the persistent binding option disabled, both persistently bound targets and
their LUNs and non-bound targets and their LUNs are reported to the operating system.
For information about mapping discovered targets to specific target IDs on the host, consult the
/opt/QLogic_Corporation/drvutil/qla2300/readme.txt file that is loaded with the
qla driver.
For more information on setting the persistent target binding capabilities of the QLogic HBA qla
driver, consult the QLogic documentation that is available on the following website:
Qlogic
Persistent Target Binding for Solaris qlc and emlxs Drivers
When using the QLogic qlc and Emulex emlxs drivers supplied as part of the Solaris SAN Foundation
suite, the target IDs are either the hard address of the device (in a private loop) or the WWN. So,
no persistent target mapping is required.
System Settings for Minimizing I/O Stall Times on VLUN Paths
This section provides system settings that can help minimize I/O stall times on VLUN paths for FC
direct- or fabric-connected Solaris hosts.
System Settings for Minimizing I/O Stall Times on VLUN Paths 37