NVMe initiator configuration in a Fibre Channel environment includes installing and configuring the nvme-cli package and for enabling the NVMe/FC initiator on the host.

About this task

The following procedure is for RHEL 8, SLES 12, and SLES 15 using Broadcom Emulex or QLogic NVMe/FC capable FC HBAs. For more information on which versions of these OS’s or HBA’s are supported, consult the Lenovo Storage Interoperation Center (LSIC).

NVMe initiator configuration in a Fibre Channel environment includes installing and configuring the nvme-cli package, and enabling the NVMe/FC initiator on the host.

These are the instructions for SUSE Linux Enterprise Server 12 SP4 and 32GB FC HBAs.

Steps

  1. Install the nvme-cli package:

    SLES 12 or SLES 15

    # zypper install nvme-cli

    RHEL 8

    # yum install nvme-cli

    1. For Qlogic, modify /lib/systemd/system/nvmefc-boot-connections.service after installing the Broadcom NVMe/FC autoconnect script to contain the following:

      [Unit]
Description=Auto-connect to subsystems on FC-NVME devices found during boot

[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo add > /sys/class/fc/fc_udev_device/nvme_discovery"

[Install]
WantedBy=default.target

  2. Enable and start the nvmefc-boot-connections service.

    systemctl enable nvmefc-boot-connections.service
    systemctl start nvmefc-boot-connections.service

Host-side setup for Emulex HBAs:

The following steps are for Emulex HBAs only.

  1. Set lpfc_enable_fc4_type to 3 to enable SLES12 SP4 as an NVMe/FC initiator.

    # cat /etc/modprobe.d/lpfc.conf
options lpfc lpfc_enable_fc4_type=3

  2. Re-build the initrd to get the Emulex change and the boot parameter change.

    # dracut --force

  3. Reboot the host to load the changes to the Ipfc driver.

    # reboot

    The host is rebooted and the NVMe/FC initiator is enabled on the host.

    After completing the host-side setup, connection of the NVMe over Fibre Channel ports occur automatically.