Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Installing and Uninstalling
- Chapter 3: Configuration
- 3.1 FC Driver Configuration
- 3.2 vPort Configuration
- 3.3 FC Driver Performance Tuning
- Chapter 4: Configuring NVMe over FC
- Chapter 5: Troubleshooting
- Appendix A: FCP Driver BlockGuard Functionality
- Appendix B: Configuring NVMe over FC on a Target
- Appendix C: Native NVMe Multipathing
- Appendix D: Trunking Support
- Appendix E: FC-SP-2 Authentication (DH-CHAP) Support
- Appendix F: ARM Support
Broadcom DRVLin-UG128-100
25
Emulex Drivers for Linux User Guide
Attached scsi generic sg6 at scsi14, channel 0, id 0, lun 1,type 8
scsi scan: INQUIRY to host 14 channel 0 id 0 lun 2
Vendor: IBM Model: ULTRIUM-TD2 Rev: 38D0
Type: Sequential-Access ANSI SCSI revision: 03
Attached scsi tape st0 at scsi14, channel 0, id 0, lun 2
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 4503599627370495
Attached scsi generic sg7 at scsi14, channel 0, id 0, lun 2, type 1
scsi scan: INQUIRY to host 14 channel 0 id 0 lun 3
Vendor: IBM Model: ULTRIUM-TD2 Rev: 38D0
Type: Sequential-Access ANSI SCSI revision: 03
Attached scsi tape st1 at scsi14, channel 0, id 0, lun 3
st1: try direct i/o: yes (alignment 512 B), max page reachable by HBA 4503599627370495
Attached scsi generic sg8 at scsi14, channel 0, id 0, lun 3, type 1
This log output shows a controller at LUN 0, the medium changer at LUN 1, and two SCSI tape devices at LUNs 2 and 3.
The following example is the result of a scsi_id call:
scsi_id -g -s /sys/class/scsi_tape/nst0
1IBM ULTRIUM-TD2 1110133831
scsi_id -g -s /sys/class/scsi_tape/nst1
1IBM ULTRIUM-TD2 1110133994
Notice that the unique ID contains three values with space delimiters. A udev rule must have a unique ID for the device, so
that all three parts of this returned string are required. To do this, use the following command:
scsi_id -u -g -s /sys/class/scsi_tape/nst0
1IBM_____ULTRIUM-TD2_____1110133831
scsi_id -u -g -s /sys/class/scsi_tape/nst1
1IBM_____ULTRIUM-TD2_____1110133994
Creating the udev Persistent Name for SCSI Tape Device:
After you know the SCSI ID call needed to extract a unique ID, use the same process to create a udev persistent name for
a SCSI tape device as on a SCSI disk device.
The rule for the FC tape device follows:
BUS="scsi", SYSFS{vendor}="HP", SYSFS{model}="ULTRIUM 3-SCSI", PROGRAM="/sbin/scsi_id -p 0x83 -u
-g -s /sys/class/scsi_tape/nst%n",RESULT="350060b000029b592", SYMLINK="fc_lun_st%n"
The rule for the FC-SCSI tape device follows:
BUS="scsi", SYSFS{vendor}="IBM", SYSFS{model}="ULTRIUM-TD2", PROGRAM="/sbin/scsi_id -p 0x83 -u -g
-s /sys/class/scsi_tape/nst%n",RESULT="1IBM_____ULTRIUM-TD2_____1110133831",
SYMLINK="fc_lun_st%n"
BUS="scsi", RESULT="1IBM_____ULTRIUM-TD2_____1110133994", SYMLINK="fc_lun_st%n"
Create a new file named /etc/udev/rules.d/45-local.rules,and put the appropriate rule in it. Then run
udevtrigger to reload the udev rules, and the output of the rules will follow:
udevtrigger
ls -al /dev/fc*
lrwxrwxrwx 1 root root 3 Apr 7 15:03 fc_lun_st0 -> st0
lrwxrwxrwx 1 root root 3 Apr 7 15:03 fc_lun_st1 -> st1
3.1.5.4 Persistent Naming References
See the following reference for more information on persistent naming: www.reactivated.net/udevrules.php
by Daniel Drake (dsd)