Installation guide

Enabling persistent binding
111
Connecting to the Storage
Enabling persistent binding
In a fabric environment, EMC recommends, but does not require,
enabling persistent binding in the driver. When using persistent
binding, EMC strongly recommends the use of binding via WWPN.
Without a persistent binding mechanism, the host will be unable
maintain persistent logical routing of the communication from a
storage device object across the fabric to an EMC storage array
volume. If the physical configuration of the switch is changed (for
example, cables are swapped or the host is rebooted), the logical
route becomes inconsistent, which could cause data corruption.
Please note that the persistent binding mechanism in the Emulex
driver is target-based only, not LUN-based.
Obtaining initiator and target information
The initiator and target information necessary for persistent binding
is logged in
/proc/scsi/lpfc/ N (where N indicates the file for each
adapter in the system) when the driver is loaded. The initiator and
target information is used to assign the persistent binding
information in
/usr/src/lpfc/lpfc.conf or /etc/modules.conf.
You can obtain the initiator and target information by grep'ing the
/proc/scsi/lpfc /N file for each adapter in the system.
For example:
cd /proc/scsi/lpfc
grep WWPN *
This example produces output similar to the following:
2:lpfc0t05 DID 6c0b13 WWPN 50:06:01:61:10:60:12:70 WWNN 50:06:01:60:90:60:12:70
2:lpfc0t06 DID 6c1713 WWPN 50:06:01:69:10:60:12:70 WWNN 50:06:01:60:90:60:12:70
3:lpfc2t02 DID 6c0b13 WWPN 50:06:01:61:10:60:12:70 WWNN 50:06:01:60:90:60:12:70
3:lpfc2t04 DID 6c1713 WWPN 50:06:01:69:10:60:12:70 WWNN 50:06:01:60:90:60:12:70
What next? To enable persistent binding for the modular driver, you must edit either
/usr/src/lpfc/lpfc.conf or /etc/modules.conf.
To edit one of these files, proceed to the appropriate section:
◆ “Editing /usr/src/lpfc/lpfc.conf” on page 112
◆ “Editing /etc/modules.conf” on page 114