•
If LUNs have been preconfigured in the /kernel/drv/sd.conf file, use the
devfsadm command to perform LUN rediscovery after configuring LUNS as
explained in
Configuring Emulex HBAs
Configure Emulex HBA as follows:
•
Edit the /kernel/drv/lpfc.conf driver configuration file to set up the HBA for
a SAN infrastructure:
topology = 2;
scan-down = 0;
•
If multiple HBAs and VxVM are used, adjust the following parameters to assure
correct VxVM behavior:
no-device-delay=0;
nodev-tmo=30;
linkdown-tmo=30; # verify, should be default value
•
Persistent bindings are necessary in a fabric topology and are used to bind a
SCSI target ID to a particular WWPN (of an array port). This is required to
guarantee that the SCSI target IDs will remain the same when the system is
rebooted. Persistent bindings can be set by editing the configuration file or by
using the lputil utility. The following example illustrates the binding of target 20
(lpfc instance 2) to WWPN 50060e8003285301 and the binding of target 30
(lpfc instance 0) to WWPN 50060e8003285311:
fcp-bind-WWPN="50060e8003285301:lpfc2t20",
"50060e8003285311:lpfc0t30";
(Replace the WWPNs above with the WWPNs for your array ports.)
•
For each LUN that needs to be accessed, add an entry to the /kernel/drv/sd.conf
file. For example, assume you want to access LUNs 1 and 2 through both paths.
You would add the following entries (preferably at the end of the file):
name="sd" parent="lpfc" target=20 lun=1;
name="sd" parent="lpfc" target=20 lun=2;
name="sd" parent="lpfc" target=30 lun=1;
name="sd" parent="lpfc" target=30 lun=2;
•
Perform a reconfiguration reboot to implement the changes to the configuration
files.
•
If LUNs have been preconfigured in the /kernel/drv/sd.conf file, use the
devfsadm command to perform LUN rediscovery after configuring LUNS as
explained in
22
Installation
Defining the
paths.
Defining the
paths.