• Use the Persistent Binding for Tape DEVICES.
• Persistent binding is a HOST-centric enforced way of directing an operating system to assign certain SCSI target IDs and LUNs.
• Persistent Name Binding support is for target devices.
• Persistent binding is provided for users to associate a SPECIFIED device World Wide Port Name (WWPN) to a specified SCSI target ID.
• For example, where a specific host will always assign SCSI ID 3 to the first router it FINDS, and LUNs 0, 1, and 2 to the three-tape drives attached to the router.

Practical examples:

For Emulex HBA on a Solaris host for setting up persistent binding:

# lputil
MAIN MENU

1. List Adapters
2. Adapter Information
3. Firmware Maintenance
4. Reset Adapter
5. Persistent Bindings

Using option 5 will perform a manual persistent binding and the file is: /kernel/drv/lpfc.conf file.

lpfc.conf file looks like:

fcp-bind-WWNN=”50060XY484411 c6c11:lpfc0t1″,
“50060XY4411 c6c12:lpfc1t2”;

sd.conf file looks like:
name=”sd” parent=”lpfc” target=1 lun=0;
name=”sd” parent=”lpfc” target=2 lun=0;

Reconfigure:

# touch /reconfigure
# shutdown -y -g0 -i6

Practical examples:

For Emulex HBA on a Solaris host for setting up persistent binding:

# lputil
MAIN MENU

Using option 5 will perform a manual persistent binding and the file is: /kernel/drv/lpfc.conf file.

lpfc.conf file looks like:

fcp-bind-WWNN=”50060XY484411 c6c11:lpfc0t1″,
“50060XY4411 c6c12:lpfc1t2”;

sd.conf file looks like:
name=”sd” parent=”lpfc” target=1 lun=0;
name=”sd” parent=”lpfc” target=2 lun=0;

Reconfigure:

# touch /reconfigure
# shutdown -y -g0 -i6