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
106
Emulex Drivers for Linux User Guide
Appendix B: Configuring NVMe over FC on a Target
NOTE: The following information applies to configuring NVMe over FC on a target system:
NVMe over FC is supported on LPe31000-series, LPe32000-series, and LPe35000-series adapters.
Before configuring NVMe over FC on a target using native NVMe CLI commands, ensure that you have
installed the latest Emulex firmware on the adapter.
NVMe over FC on target devices is supported on SLES 12 SP4 only.
The NVMe target drivers are meant for evaluation and testing during development only. They are not intended
for production use.
B.1 Configuring the elx-lpfc.conf File
To configure the elx-lpfc.conf file, perform the following steps:
1. Find the WWPNs of the HBAs that are available to be used as NVMe target ports by typing the following command:
cat /sys/class/fc_host/host*/<port_name>
Information similar to the following is displayed (the low number is usually port 0 of the adapter):
0x10000090fa931110
0x10000090fa931111
Record the WWPNs of the adapters you want to use as target ports; you will need this information in Step 5.
2. Find the WWNNs of the HBAs in Step 1 by typing the following command:
cat /sys/class/fc_host/host*/<node_name>
Information similar to the following is displayed:
0x20000090fa931110
0x20000090fa931111
Record the WWNNs of the adapters that you want to use as target ports; you will need this information in Step 9 in
Appendix B.2, Configuring Subsystems, Namespaces, and Ports.
3. NVMe subsystems and namespaces are created from the storage block devices on the target. An existing storage block
device on the target can be used by NVMe namespaces as their storage media. Display the available storage block
devices to share over the NVMe fabric by typing the following command:
lsblk
All block devices found by the target are displayed, for example:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 136.7G 0 disk
├─sda1 8:1 0 2G 0 part
├─sda2 8:2 0 40G 0 part
├─sda3 8:3 0 94.7G 0 part
└─3600508b1001037383941424344450400 254:0 0 136.7G 0 mpath
├─3600508b1001037383941424344450400-part1 254:1 0 2G 0 part [SWAP]
├─3600508b1001037383941424344450400-part2 254:2 0 40G 0 part /var/opt
└─3600508b1001037383941424344450400-part3 254:3 0 94.7G 0 part /home
sdb 8:16 0 3G 0 disk
└─3600000e00d2a0000002a017300340000 254:4 0 3G 0 mpath