Users Guide

4–NVM Express over Fibre Channel
Host Setup
109 BK3254601-00 J
11. (Optional) As needed, on the supported Linux OS, create a hostnqn file to
attach to remote FC-NVMe Storage Subsystems.
a. With the NVMe CLI already installed, issue the following command to
verify that the hostnqn file exists. For example:
# ls /etc/nvme/hostnqn
/etc/nvme/hostnqn
b. If the hostnqn file exists, issue the following command to view and
make note of the hostnqn data to use when mapping the host
initiator(s) to storage subsystems:
# cat /etc/nvme/hostnqn
nqn.2014-08.org.nvmexpress:uuid:1164eabb-e77f-4f15-ad16-c
efb43d1fc9
c. If the hostnqn file does not exist, issue the following command to
create it using the NVMe CLI:
# nvme gen-hostnqn
nqn.2014-08.org.nvmexpress:uuid:a0baf242-85fd-41e5-a524-e
253d8531282
d. Take the output from the nvme gen-hostnqn command and save it
to the hostnqn file. The edited file in the
/etc/nvme/hostnqn
directory should appear as follows.
nqn.2014-08.org.nvmexpress:uuid:a0baf242-85fd-41e5-a524-e
253d8531282
12. Reboot the system and verify that the correct driver and firmware versions
are installed. For example, issue the following QConvergeConsole CLI
command:
# qaucli -i 0
13. If NVMe devices do not appear, follow the procedures in “Unloading and
Reloading the Linux Driver” on page 113 and “Verifying the Availability of
FC-NVMe Devices” on page 111.
NOTE
The OOB driver must have the FC-NVMe option enabled to attach to
FC-NVMe storage devices. For details on using the FC-NVMe driver
option, see either the 10.01.xx.xx.xx.x-x driver documentation or the
example shown in Step 11.