Emulex® Drivers for Linux User Guide Release 12.
Broadcom, the pulse logo, Connecting everything, Avago Technologies, Avago, the A logo, Emulex, OneCommand, and OneConnect are among the trademarks of Broadcom and/or its affiliates in the United States, certain other countries, and/ or the EU. Copyright © 2003–2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com.
Emulex Drivers for Linux User Guide Table of Contents Chapter 1: Introduction ...................................................................................................................... 5 1.1 Overview ....................................................................................................................................................................5 1.2 Abbreviations ...................................................................................................................
Emulex Drivers for Linux User Guide 3.2.3.2 vPort sysfs Entries ................................................................................................................................27 3.2.4 Monitoring vPorts with fc_vport .......................................................................................................................30 3.2.5 vPort Configuration Limits............................................................................................................................
Emulex Drivers for Linux User Guide Chapter 1: Introduction 1.1 Overview This guide provides installation, updating, uninstalling, configuring, and troubleshooting procedures for several types of Emulex®-supported drivers for Linux. This guide is applicable to several versions of drivers, operating systems, firmware, and adapters. For supported firmware versions and their latest release, refer to the Documents and Downloads area of www.broadcom.com for the specific adapter.
Emulex Drivers for Linux User Guide Table 1: Acronyms and Abbreviations (Continued) Acronym/Abbreviation Description FLOGI fabric login GnuPG GNU Privacy Guard I/O input/output IOCB input/output command block IOCBQ I/O command block queue IOPs input/output operations per second IOTAG input/output tag IP CSUM IP checksums ISR interrupt service routine LPFC Light Pulse Fibre Channel MB megabyte MDS Multilayer Director Switch MQ MultiQueue MSI message signaled interrupt MSI-X ex
Emulex Drivers for Linux User Guide Chapter 2: Installing and Uninstalling The Linux driver supports both FCP and NVMe over FC. Emulex releases Linux binary RPMs that are digitally signed using the GNU Privacy Guard (GnuPG) standard. This allows certification of the contents of the RPMs and verification that the contents have not been modified since they were created by Emulex. The RPMs have been digitally signed by Emulex with a GnuPG private key that is only held by Emulex.
Emulex Drivers for Linux User Guide 2.2 Emulex FC Driver Kit The Emulex FC driver kit contains the following: A zipped tar file that includes the driver binary RPMs for a specific driver version and Linux distribution. On select driver kits, the zipped tar file may also include any of the following RPMs: – nvmefc-connect RPM – elx-lpfc-vector-map RPM – elx-lpfc-extras RPM NOTE: Use only officially released Linux distribution kernels.
Emulex Drivers for Linux User Guide 5. Reboot the system to enable the newly added driver options in the ramdisk. 6. You can use the following command to verify if the version of the newly installed LPFC driver is correct: cat /sys/module/lpfc/version 2.2.2 Uninstalling the Emulex FC Driver Kit NOTE: You must run the uninstall script that shipped with the version of the driver kit you want to remove. To uninstall the Emulex FC driver, perform the following steps to install the Emulex FC driver: 1.
Emulex Drivers for Linux User Guide NOTE: NVMe over FC is supported on GA kernels, except on SLES 12 SP3. The minimum kernel on which the NVMe over FC driver can be installed on the SLES 12 SP3 operating system is maintenance kernel 718 (4.4.126-94.22.1) from SUSE, dated April 23, 2018. The NVMe over FC target drivers are meant for evaluation and testing during development only. They are not intended for production use.
Emulex Drivers for Linux User Guide Chapter 3: Configuration 3.1 FC Driver Configuration This section describes how to configure parameters for the FC driver. 3.1.1 FC Driver Parameters The FC driver parameters determine some aspects of the driver’s behavior. There are two main types, static and dynamic. Changes to the static parameters require a driver reload for the change to take effect.
Emulex Drivers for Linux User Guide Table 2: Static FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_enable_hba_heartbeat When enabled, the heartbeat logic in the FC driver is able Yes to detect whether the adapter is functional. If the heartbeat logic detects that the adapter is not functional, the driver will shut down the adapter. The disabled value is 0 (default). The enabled value is 1.
Emulex Drivers for Linux User Guide Table 2: Static FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_lun_queue_depth Specifies the default maximum number of commands Yes sent to a single logical unit (disk drive). The minimum value is 1. The maximum value is 512. The default value is 30. The value of lpfc_lun_queue_depth is dependent on the max_xri value received. The max_xri value might vary per adapter type.
Emulex Drivers for Linux User Guide Table 2: Static FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_ras_fwlog_func Configures the function on which firmware logging Yes support will be enabled. The minimum value is 0 (default). The maximum value is 7. Default value: Logging enabled on Function 0. LPe31000-series, Driver reload LPe32000-series, and LPe35000series adapters lpfc_ras_fwlog_level Configures the firmware logging level.
Emulex Drivers for Linux User Guide Table 2: Static FC Driver Parameters (Continued) Parameter lpfc_xri_split Broadcom Description sysfs Visible When enabled, this parameter defines the division of XRI Yes resources between SCSI and NVMe. This parameter is only used if the value of the lpfc_enable_fc4_type parameter is 3—register both FCP and NVMe and the port is not configured for NVMeT. The supported values are in percentages.
Emulex Drivers for Linux User Guide 3.1.1.2 Dynamic FC Driver Parameters Changes to the dynamic parameters take effect immediately. All lpfc dynamic parameters are read and written using sysfs. The following table lists the dynamic FC driver parameters.
Emulex Drivers for Linux User Guide Table 3: Dynamic FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_fcp_imax Yes Specifies the maximum number of fast-path FCP interrupts per second. For RHEL 7.5 and earlier kernels: The minimum value is 0 or OFF and 5000. The maximum value is 5,000,000. The default value is 0. For the following operating systems: – RHEL 8.0 and later – RHEL 7.
Emulex Drivers for Linux User Guide Table 3: Dynamic FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_link_speed Specifies the FC link speed. The possible values are: Yes 0 = Auto-select (default). 2 = 2 Gb/s. 4 = 4 Gb/s. 8 = 8 Gb/s. 16 = 16 Gb/s. 32 = 32 Gb/s. NOTE: For LPe32000-series and 35000-series adapters running 11.2 firmware or later, this parameter is ignored.
Emulex Drivers for Linux User Guide Table 3: Dynamic FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_topology For FC adapters, this parameter sets the link topology. Yes The possible values are: 0x0 = Loop first; if loop fails, then point-to-point (default). 0x2 = Point-to-point only. 0x4 = Loop only. 0x6 = Point-to-point first; if point-to-point fails, then loop.
Emulex Drivers for Linux User Guide 3.1.2.2 Persistent Configuration with the elx-lpfc.conf File To make the FC driver parameters persist across module loads and reboots, perform these steps: 1. In the /etc/modprobe.d directory, create a file with the driver name elx-lpfc.conf. 2. In /etc/modprobe.d/elx-lpfc.conf, use the options command to add the appropriate FC driver parameters and their desired values. For example, adding the following command to the elx-lpfc.
Emulex Drivers for Linux User Guide -r--r--r--rw-r--r-- 1 root root 4096 Feb 28 17:03 /sys/class/scsi_host/host7/lpfc_topology 1 root root 4096 Feb 28 17:03 /sys/class/scsi_host/host7/lpfc_use_adisc Temporary Configuration Parameters with sysfs: In the previous example, notice that the FC driver parameters are available as files. Reading a file displays the current value of a driver parameter. If the permissions allow it, you can write a value to the file and it will take effect immediately.
Emulex Drivers for Linux User Guide 3.1.5 Persistent Naming The generic device manager for the Linux kernel is udev, which primarily manages device nodes in the /dev directory. 3.1.5.1 Using udev to Discover Logical-to-Physical Mappings for sd Devices In Linux, the driver for SCSI disk drives is sd. A disk device name has an sd prefix. Persistent names for sd devices are provided in the /dev/disk/by-id directory.
Emulex Drivers for Linux User Guide – For UEFI boot In /boot/efi/EFI/redhat/grub.cfg, find the kernel line for the default boot. For example: kernel /boot/vmlinuz - ro root=/dev/sda2 2. Find the persistent name for the root partition (following root= on the kernel line) by using the instructions in Section 3.1.5.1, Using udev to Discover Logical-to-Physical Mappings for sd Devices. 3.
Emulex Drivers for Linux User Guide The following example uses a different FC tape vendor. Notice that the value returned is similar to the previous examples, with respect to the leading digit and the WWPN. /sbin/scsi_id -g -s sys/class/scsi_tape/nst0 35005076300015101 FC-SCSI Tape Device Example: The following is an example of an FC controller with multiple SCSI tape devices behind it (FC-SCSI tape device).
Emulex Drivers for Linux User Guide 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.
Emulex Drivers for Linux User Guide 3.2.2.1 Creating vPorts Using the mkvport.sh Script You can use the mkvport script to create vPorts. To see the usage information, run the script with no parameters specified. The mkvport.sh script uses the following syntax: ./mkvport.sh You must supply the physical port’s host number, WWPN, and WWNN when using the mkvport.sh script.
Emulex Drivers for Linux User Guide 3.2.3 vPort sysfs This section describes the vPort sysfs structure and vPort sysfs entries. 3.2.3.
Emulex Drivers for Linux User Guide Table 4: vPort sysfs Entries vPort sysfs Entries Type Range/Input Location and Description lpfc_peer_port_login Read/Write 0 = Off (default) 1 = On /sys/class/scsi_host/hostX/ lpfc_peer_port_login This entry sets the port behavior when discovering targets in the SAN. The default behavior (value = 0) logs in only to N_Ports that are physically located on a different port.
Emulex Drivers for Linux User Guide Table 4: vPort sysfs Entries (Continued) vPort sysfs Entries Type Range/Input Location and Description node_name Read-only 16-byte hexadecimal value /sys/class/fc_host/hostX/node_name /sys/class/fc_vports/vport-X:0-Z/ node_name These entries display the physical or vPort node name. You assign this value when the vPort is created, and it is transmitted to the fabric upon fabric login.
Emulex Drivers for Linux User Guide Table 4: vPort sysfs Entries (Continued) vPort sysfs Entries vport_delete Type Write- only Range/Input WWPN; WWNN Location and Description /sys/class/fc_host/hostX/vport_delete This entry deletes a vPort on the physical port on which hostX is located. The vPort matching the WWPN and WWNN is immediately deleted. This entry returns a 0 if the vPort deletion was successful. A nonzero value indicates that the vPort was not deleted.
Emulex Drivers for Linux User Guide The maximum number of LUNs supported on each driver port is 256. The maximum number of targets supported for each driver port is 255. The maximum number of driver ports in one zone is 64. This limit is based on the system’s ability to recover from link events within the time constraints of the default timers.
Emulex Drivers for Linux User Guide The default value (0) configures the driver for round-robin scheduling. A value of 1 configures scheduling by CPU. NOTE: This parameter is not only applicable for LPe12000-series adapters, and by default, the value is configured to CPU scheduling. 3.3.1.2 lpfc_fcp_imax The lpfc_fcp_imax parameter can be configured at driver load time. It also can be set dynamically as an sysfs entry.
Emulex Drivers for Linux User Guide Chapter 4: Configuring NVMe over FC NVMe over FC is supported on the following operating systems: RHEL 8.0 and later RHEL 7.6 and later SLES 15 and later SLES 12 SP3 and later For supported operating systems, see Section 2.5, Installing the NVMe over FC Driver. To configure NVMe over FC, you must perform the following procedures in the indicated sequence: 1. Attach NVMe over FC-based storage to the FC SAN.
Emulex Drivers for Linux User Guide 2. Reboot the system. After the system is rebooted, the configured protocols are enacted on the FC ports. The nvmefc-connect.rpm file, which is installed with the out-of-box Linux driver, automatically causes the initiator to connect to the target devices.
Emulex Drivers for Linux User Guide Information similar to the following is displayed: NVME-SUBSYS0 - NQN=NQN.2014-08.ORG.NVMEXPRESS:NVMF:UUID:19D48A6D-3644-4F65-8046-80BD88FE45A6 \ +- NVME0 FC TRADDR=NN-0X20000090FA942E16:PN-0X10000090FA942E16 HOST_TRADDR=NN-0X200000109B346F1F:PN0X100000109B346F1F +- NVME3 FC TRADDR=NN-0X20000090FA942E16:PN-0X10000090FA942E16 HOST_TRADDR=NN-0X200000109B346F20:PN0X100000109B346F20 NVME-SUBSYS1 - NQN=NQN.2014-08.ORG.
Emulex Drivers for Linux User Guide sdd └─3600000e00d2a0000002a017300360000 8:48 0 3G 0 disk 254:6 0 3G 0 mpath nvme0n1 259:0 0 3G 0 disk nvme0n2 259:1 0 3G 0 disk NOTE: The /dev/sde and /dev/sdf block devices, which were previously referred to on the NVMe target system, are now discovered by the NVMe initiator system, and they appear as the NVMe block devices /dev/nvme0n1 and /dev/nvme0n2. 4.
Emulex Drivers for Linux User Guide Chapter 5: Troubleshooting This section explains some of the situations in which your system can operate in an unexpected manner and some possible resolutions. 5.1 Hardware Situations and Resolutions Table 5 lists the hardware situations and their resolutions. Table 5: Hardware Situations and Their Resolutions Situation An unapproved optical transceiver is used to connect the adapter.
Emulex Drivers for Linux User Guide Table 6: FC Driver Situations and Their Resolutions (Continued) Situation Resolution rmmod hangs and module reference count is 0. Due to a small race condition in the kernel, it is possible for an rmmod command to hang. Issue the rmmod -w command. If this does not help, reboot the computer. rmmod fails to unload driver due to device or resource busy.
Emulex Drivers for Linux User Guide Table 6: FC Driver Situations and Their Resolutions (Continued) Situation Resolution These three situations can be resolved by upgrading the kernel. There are two ways to install the driver into an upgraded kernel. The method you use depends on whether you are updating the driver. A recently upgraded kernel cannot find the ramdisk. Upgrade the kernel using the same version of the driver.
Emulex Drivers for Linux User Guide 5.3 Log Messages 5.3.1 FC Driver Log Messages The following section describes retrieving and interpreting FC driver log messages. 5.3.1.1 Retrieving FC Driver Log Messages LPFC error log messages are logged in the /var/log/messages file. An example of an LPFC message follows: Jul 2 04:23:34 daffy kernel: lpfc 0000:03:06.0: 0:1305 Link Down Event x2f2 received Data: x2f2 x20 x110 In this example: lpfc 0000:03:06.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0125: FDISC Failed (x%x). Fabric out of resources The fabric rejected an FDISC because the switch cannot support additional virtual ports. Data: lsRjtError Severity: Error Log: Always Action: Reconfigure the switch to support more NPIV logins. If this issue persists, contact Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0138: ELS rsp: Cannot issue reg_login for REG_LOGIN mailbox command failed. Data: (1) nlp_DID (2) nlp_state (3) nlp_flag (4) nlp_rpi Severity: Error Log: LOG_ELS Action: None required. 0139: Ignoring ELS cmd tag completion Data This ELS command was aborted. Data: (1) ulpStatus (2) ulpWord[4] (3) ulpTimeout Severity: Error Log: LOG_ELS Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0147: Failed to allocate memory for RSCN event Memory could not be allocated to send the RSCN event to the management application. Data: None Severity: Error Log: LOG_ELS Action: None required. 0148: Failed to allocate memory for LOGO event Memory could not be allocated to send the LOGO event to the FC transport. Data: None Severity: Error Log: LOG_ELS Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0207: Device () sent invalid service parameters. Ignoring device. Invalid service parameters were received from DID. This remote port is ignored. Data: DID, WWN Severity: Error Log: Always Action: Verify the remote port's configuration. If this issue persists, report the error to Broadcom Technical Support. Run with verbose mode on for more details.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0227: Node Authentication timeout The driver has lost track of what N_Ports are being authenticated. Data: None Severity: Error Log: Always Action: None required. The driver should recover from this event. 0228: CLEAR LA timeout The driver issued a CLEAR_LA that never completed. Data: None Severity: Error Log: Always Action: None required. The driver should recover from this event.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0246: RegLogin failed The firmware returned a failure for the specified RegLogin. Data: (1) Did (2) mbxStatus (3) hbaState Severity: Error Log: Always Action: This message indicates that the firmware could not do RegLogin for the specified DID. There might be a limitation on how many nodes an HBA can see. 0249: Cannot issue Register Fabric login: Err %d\ Could not issue the fabric register login, the err
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0256: Issue FDISC: Cannot send IOCB\ Unable to send the fabric IOCB. Data: None Severity: Error Log: LOG_ELS Action: None required. 0257: GID_FT Query error The GID_FT CT request for the NameServer has failed. Data: None Severity: Error Log: LOG_ELS Action: Check the switch configuration. 0258: Register Fabric login error: The REG_LOGIN for the fabric has failed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0263: Discovery Mailbox error: state: Either the driver could not allocate resources or it could not send sparam_mbox or cfglink_mbox. Data: (1) address of sparam_mbox command (2) address of cfglink_mbox command Severity: Error Log: LOG_MBOX Action: Attempt to unload and reload the driver when it is convenient. 0264: No NPIV Fabric support The switch to which the port is connected does not support NPIV.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0273: Unexpected discovery timeout, vport State x%x The discovery process has timed out. Data: None Severity: Error Log: LOG_DISCOVERY Action: Verify that all targets are still visible. 0274: lpfc_nlp_put: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp>kref.refcount) Data: None Severity: Warning Log: LOG_NODE Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0281: lpfc_cleanup_node: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp->kref.refcount) Node cleanup was called to prepare the node for release. Data: None Severity: Warning Log: LOG_NODE Action: None required. 0282: ldid:x%x ndlp:x%pusgmap:x%x refcnt:%d, ndlp->nlp_DID, (void *)ndlp, lpfc_init.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0290: The SLI4 DCBX asynchronous event is not handled yet The SLI-4 DCBX asynchronous event is not handled yet. Data: None Severity: Error Log: LOG_SLI Action: None required. 0291: Allocated DMA memory size (x%x) is less than the requested DMA memory size (x%x) The asynchronous DCBX events are not handled in the driver. Data: None Severity: Error Log: LOG_INIT Action: Check the switch configuration.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0301: READ_SPARAM: no buffers The driver attempted to issue a READ_SPARAM mailbox command to the adapter, but there were no buffers available. Data: None Severity: Warning Log: LOG_MBOX verbose Action: This message indicates one of these two issues: (1) Kernel virtual memory is depleted. Check that the system meets minimum RAM requirements for the adapter.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0312: Ring handler: portRspPut is bigger then rsp ring The IOCB command rings put pointer is ahead of the get pointer. Data: None Severity: Error Log: LOG_SLI Action: None required. 0313: Ring handler: unexpected Rctl Type received The RCTL/Type of a received frame did not match any for the configured masks for the specified ring.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0322: Ring handler: unexpected completion IoTag The driver could not find a matching command for the completion received on the specified ring. Data: (1) ulpStatus, (2) ulpWord[4], (3) ulpCommand, (4) ulpContext Severity: Warning Log: LOG_SLI verbose Action: This error could indicate a software driver or firmware issue.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0336: Rsp Ring error: IOCB An IOCB error has occurred on the specified ring. Data: (1) ulpWord[0], (2) ulpWord[1], (3) ulpWord[2], (4) ulpWord[3], (5) ulpWord[4], (6) ulpWord[5], (7) irsp+6, (8) irsp+7 Severity: Warning Log: LOG_SLI verbose Action: If this issue persists, check the targets. If the targets are not the problem, report the error to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0346: Ring handler: unexpected ASYNC_STATUS evt_code W0 W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 The HBA received an asynchronous event that was not a temperature event. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0353: Active Mailbox cleared - mailbox timeout exiting The mailbox timeout handler has determined that the driver is in the process of completing this mailbox command. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 0357: MSI-X interrupt with no EQE SLI-4 adapter interrupt on the slow path but there is no associated EQE.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0364:Invalid param: SLI-4: The post-SGL function was passed an invalid XRI. Data: None Severity: Error Log: LOG_SLI Action: None required. 0365:Slow-path CQ identifier does not exist: The completion queue identifier passed in the event queue entry does not reference a valid completion queue. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0371: No entry from the CQ: identifier , type No completion queue event existed for this event queue entry. Data: None Severity: Error Log: LOG_SLI Action: None required. 0372: iotag is out of range: max iotag () The IOCB lookup cannot be performed because the iocb_tag is out of range. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0379: Feature Mismatch Data: The features passed in to the driver as module parameters do not match what the firmware can do. Setting to default values. Data: None Severity: Warning Log: LOG_MBOX, LOG_SLI Action: None required. 0381: Error %d during queue setup.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0387:Failed to allocate an iocbq Failed to get an IOCBQ from the list of available IOCBQs. Data: None Severity: Error Log: LOG_SLI Action: None required. 0388:Not a valid WCQE code: x The event code is invalid. This event will be dropped. Data: None Severity: Error Log: LOG_SLI Action: Ensure that the adapter firmware is current.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0397:The mbuf allocation failed The asynchronous link event handler could not allocate DMA for the READ_LA mailbox command. Data: None Severity: Error Log: LOG_SLI Action: None required. 0398 Invalid link fault code: The attempt to read the link attention register returned an unknown value. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0406: Adapter maximum temperature exceeded , taking this port offline The driver has received an error for the HBA indicating that the maximum allowable temperature has been exceeded. Data: (1) work_hs (2) work_status[0] (3) work_status[1] Severity: Error Log: LOG_INIT Action: Ensure that the server fans are not blocked. Shut down the server if the airflow is restricted.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0425:lpfc_restrict_login attribute cannot be set to %d, allowed range is [0, 1] The module parameter lpfc_restrict_login can only be set to 0 (off) or 1 (on). Data: None Severity: Error Log: LOG_INIT Action: Set lpfc_restrict_login = [0,1]. 0426: Failed to enable interrupt The driver failed to start the interrupt. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0434: PM resume failed to start worker thread: error= The driver's power management resume function could not start the worker thread. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver. 0435: Adapter failed to get Option ROM version status The driver could not read the HBA option ROM. Data: None Severity: Error Log: LOG_INIT Action: Reset the HBA.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0442: Adapter failed to init, mbxCmd CONFIG_PORT, mbxStatus Adapter initialization failed when issuing a CONFIG_PORT mailbox command. Data: (1) hbainit Severity: Error Log: Always Action: This error could indicate a hardware or firmware issue. If this issue persists, report the error to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0453: Adapter failed to init, mbxCmd READ_CONFIG, mbxStatus Adapter initialization failed when issuing a READ_CONFIG mailbox command. Data: None Severity: Error Log: Always Action: This error could indicate a hardware or firmware issue. If this issue persists, report the error to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0466: Outstanding I/O when bringing Adapter offline The I/O is still pending while attempting to stop the driver. Data: None Severity: Warning Log: LOG_INIT Action: None required. 0467: lpfc_topology attribute cannot be set to %d, allowed range is [0, 6], phba->brd_no, val. The lpfc_topology module parameter is invalid. Data: None Severity: Error Log: LOG_INIT Action: Use a value in the valid range.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0476: HBA not supporting SLI-3 or later SLI Revision: The HBA does not support SLI-3 or SLI-4. Data: None Severity: Error Log: LOG_INIT Action: This HBA does not support msi. Set lpfc_use_msi = 0. 0478: MSI request_irq failed (). The request_irq kernel API failed. Data: None Severity: Warning Log: LOG_INIT Action: Set lpfc_use_msi = 0.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0492: Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command Mailbox memory pool allocation error. Data: None Severity: Error Log: LOG_INIT Action: None required. 0493: SLI_CONFIG_SPECIAL mailbox failed with status Mailbox command failed. Data: None Severity: Error Log: LOG_INIT Action: Ensure that the adapter firmware is current. Unload and reload the driver.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0500: Failed allocate slow-path mailbox CQ Failed to allocate slow-path mailbox CQ. Data: None Severity: Error Log: LOG_INIT Action: None required. 0501: Failed allocate slow-path ELS CQ Failed to allocate slow-path ELS CQ. Data: None Severity: Error Log: LOG_INIT Action: None required. 0503: Failed allocate fast-path FCP Failed to allocate fast-path FCP.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0522: Fast-path EQ not allocated The fast-path EQ is not allocated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0523: Failed setup of fast-path EQ , rc = The fast-path EQ setup failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 0526: Fast-path FCP CQ not allocated The fast-path FCP is not allocated.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0535: Failed setup of fast-path FCP WQ , rc = The fast-path FCP WQ setup failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 0536: Slow-path ELS WQ not allocated The slow-path ELS WQ is not allocated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0538: Slow-path MQ not allocated The slow-path MQ is not allocated.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0545: lpfc_create_static_vport bad information header 0x%x 0x%x\n"\, le32_to_cpu(vport_info->signature), le32_to_cpu(vport_info->rev) & VPORT_INFO_REV_MASK); Invalid information header; the signature or revision is invalid. Data: None Severity: Error Log: LOG_INIT Action: None required. 0546: lpfc_create_static_vport failed to create vport Failed to create a vPort.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0705: Allocation request of command buffers will exceed max of . Reducing allocation request to The number of command buffers requested will exceed the maximum so a smaller quantity will be allocated. Data: None Severity: Warning Log: LOG_FCP verbose Action: None required. 0708: Allocation request of command buffers did not succeed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0722: Target Reset rport failure: rdata The reset of the target failed. Data: None Severity: Error Log: LOG_FCP Action: None required. 0723: SCSI layer issued Target Reset (%d, %d) The SCSI layer issued a target reset. Data: None Severity: Error Log: LOG_FCP Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 0735: FCP Read Check Error and Underrun Data HBA reported under run from storage array. Data: (1) vpi (2) fcpDI (3) res_id (4) fcpi_parm Severity: Warning Log: LOG_FCP_ERROR verbose Action: No action needed, informational. 0748: Abort handler timed out waiting for abort to complete:ret D LUN The abort handler timed out waiting for abort to complete.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1023: Warning - data may have been truncated. Data: reqdl: mesdl: A security message exchange operation failed because the response was missing or unreliable. Data: None Severity: Warning Log: LOG_SECURITY Action: Software driver warning. If this issue persists, report these errors to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) elx_mag1036: Authentication transaction reject - re-auth request reason exp An authentication was rejected and requested again due to reason as displayed with explanation. Data: (1) reason (2) explanation. Severity: Error Log: LOG_SECURITY Action: Software driver error. If this issue persists, report errors to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) elx_ msg1050: Authentication mode is disabled, but is required by the fabric Discovery failed because the switch fabric required authentication, but either authentication was not configured or the authentication mode for this port pair is disabled.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1210: Invalid cmd size: cmd cmdsz rspsz The management command for LPFC 2100 failed. Data: None Severity: Error Log: LOG_LIBDFC Action: None required. 1211: genreq alloc failed\n"); Resource allocation failure. Data: (1) return code Log: LOG_LIBDFC Severity: Error Action: Kernel memory resources are too low. 1223: menlo_write: couldn't alloc genreq Resource allocation failure.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1244: Unable to allocate response buffer memory. Could not allocate memory for the management command response. Data: None Severity: Error Log: LOG_LINK_EVENT Action: None required. 1257: lpfc_menlo_issue_iocb: handler set for . Data: None Log: LOG_LIBDFC Severity: Warning Action: None required. 1259: mbox: Issued mailbox cmd while in stopped state.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1304: Link Up Event ALPA map A link-up event was received. Data: (1) wd1, (2) wd2, (3) wd3, (4) wd4 Severity: Warning Log: LOG_LINK_EVENT verbose Action: If numerous link events are occurring, check the physical connections to the FC network. 1305: Link Down Event received A link-down event was received.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1400: Failed to initialize sgl list. Failed to initialize SGL list during initialization. Data: None Severity: Error Log: LOG_INIT Action: None required. 1401: Failed to enable pci device. Failed to enable PCI device during initialization. Data: None Severity: Error Log: LOG_INIT Action: None required. 1402: Failed to set up pci memory space. PCI initialization failed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1407: Failed to create scsi host. Initialization failed to create SCSI host. Data: None Severity: Error Log: LOG_INIT Action: None required. 1408: Failure HBA POST Status: sta_reg=0x%x, ""perr=x%x, sfi=x%x, nip=x%x, ipc=x%x, xrom=x%x, ""dl=x%x, pstatus=x%x\n", sta_reg.word0, bf_get(lpfc_hst_state_perr, &sta_reg), The HBA POST failed. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1414: Failed to set up driver resource. Initialization failed to set up driver resource. Data: None Severity: Error Log: LOG_INIT Action: None required. 1415: Failed to create scsi host. Initialization failed to create SCSI host. Data: None Severity: Error Log: LOG_INIT Action: None required. 1416: Failed to allocate sysfs attr Initialization failed to sysfs attribute.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1422: HBA Unrecoverable error: uerr_lo_reg=, uerr_hi_reg=, online0_reg=, online1_reg= The HBA notified the driver that it encountered an unrecoverable error. Data: None Severity: Error Log: LOG_INIT Action: Perform a dump from the Emulex OneCommand Manager application. Then, unload and reload the driver.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1429: Invalid PCI device group: Invalid HBA PCI device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1430: Failed to initialize sql list Failed to initialize SQL list. Data: None Severity: Error Log: LOG_INIT Action: None required. 1431: Invalid HBA PCI device group: Invalid HBA PCI device group detected.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1800: Could not issue unreg_vpi Driver attempt to unregister VPI failed. Data: None Severity: Error Log: LOG_VPORT verbose Action: Software driver error. If this issue persists, report these errors to Broadcom Technical Support. 1801: Create vport work array FAILED: cannot do scsi_host_get The driver was unable to get a reference to a SCSI host.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1821: Create VPORT failed. Invalid WWN format The port could not be created due to an invalid WWNN or WWPN format. Data: None Severity: Error Log: LOG_VPORT verbose Action: Provide a valid WWN when creating Vports. 1822: Invalid : An invalid WWN was used when creating a vPort.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1828: Vport Deleted A Vport was deleted. Data: None Severity: Error Log: LOG_VPORT verbose Action: No action, informational. 1829: CT command failed to delete objects on fabric. A command issued to the fabric to delete an associated resource for an object, such as for a port, failed. Data: None Severity: Error Log: LOG_VPORT verbose Action: Software driver error.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 1837: Vport_delete failed: Cannot delete static vport Static vPorts cannot be deleted. Data: None Severity: Error Log: LOG_VPORT Action: None required. 1838: Failed to INIT_VPI on vpi status Failed to INIT_VPI. Data: None Severity: Error Log: LOG_VPORT Action: None required. 2000: Failed to allocate mbox for read_FCF cmd Failed to allocate mailbox for READ_FCF command.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2007: Only Limited Edition cmd Format supported The SGL pages could not be unregistered from the firmware. Data: None Severity: Error Log: LOG_SLI Action: None required. 2008: Error posting all rpi headers The RPI headers could not be posted to the firmware. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2015: Invalid CT %x command Invalid command type in the IOCB is not supported. Data: None Severity: Error Log: LOG_SLI Action: None required. 2017: REG_FCFI mbxStatus error HBA state The REG_FCFI mailbox command failed. Data: None Severity: Error Log: LOG_MBOX Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2501: CQ_CREATE mailbox failed with status add_status , mbx status The mailbox command sent to create the completion queue failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2502: MQ_CREATE mailbox failed with status add_status , mbx status The mailbox command sent to create the mailbox queue failed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2507: MQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the mailbox queue failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2508: WQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the work queue failed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2513: POST_SGL_BLOCK mailbox command failed status add_status mbx status The mailbox command sent to post the SGL pages to the firmware failed. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2520: NOP mailbox command failed status x%x add_status x%x mbx status x%x, shdr_status, shdr_add_status, rc. The NOP mailbox command failed. Data: None Severity: Warning Log: LOG_INIT Action: None required. 2521: READ_FCF_RECORD mailbox failed with status add_status , mbx The READ_FCF_RECORD mailbox command failed.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2530: Mailbox command cannot issue The SLI layer in the driver is inactive. Data: (1) mb.mbxCommand (2) sli_flag (3) flag Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 2531: Mailbox command cannot issue Data: (1) mb.mbxCommand (2) sli_flag (3) flag Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2540: Ring handler: unexpected Rctl Type The received frame has an unsupported RCTL or FH_TYPE. Data: None Severity: Warning Log: LOG_SLI Action: None required. 2541: Mailbox command () cannot issue Data: (1) sli_mbox_opcode (2) sli_flag (3) flag Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2548: FCF Table full count tag The FCF table is full. Data: None Severity: Error Log: LOG_SLI Action: None required. 2549: FCF disconnected from network index tag The FCF disconnected from the network. Data: None Severity: Error Log: LOG_DISCOVERY Action: None required. 2550: UNREG_FCFI mbxStatus error HBA state .
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2556: UNREG_VFI mbox allocation failed HBA state Could not allocate memory for UNREG_VFI mailbox command. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required. 2557: UNREG_VFI issue mbox failed rc HBA state Could not issue the UNREG_VFI mailbox command. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2563: Failed to allocate memory for SCSI XRI management array of size . Initialization could not allocate memory to hold the XRIs. Data: None Severity: Error Log: LOG_SLI Action: None required. 2564: POST_SGL_BLOCK mailbox command failed status add_status mbx status The list of XRI SGEs failed to be registered with the firmware.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2574: Not enough EQs () from the pci function for supporting FCP EQs () Failed to create the minimum fast-path event queues. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2581: Not enough WQs () from the pci function for supporting FCP WQs () The driver was not configured with the minimum number of fast-path work queues. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2605: lpfc_dump_static_vport: memory allocation failed Failed to allocate mailbox memory. Data: None Severity: Error Log: LOG_MBOX Action: None required. 2606: No NPIV Fabric support No NPIV Fabric support. Data: None Severity: Error Log: LOG_ELS Action: None required. 2607: Failed to allocate init_vpi mailbox Failed to allocate the INIT_VPI mailbox command.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2619: Config region 23 has bad signature Configuration region 23 has an invalid signature. Data: None Severity: Error Log: LOG_INIT Action: None required. 2620: Config region 23 has bad version Configuration region 23 has an invalid version. Data: None Severity: Error Log: LOG_INIT Action: None required. 2621: Failed to allocate mbox for query firmware config cmd Failed to allocate mailbox memory.
Emulex Drivers for Linux User Guide Table 7: LPFC Error Log Messages and Their Descriptions (Continued) 2719: Invalid response length: tgt lun cmnd rsplen The response length for this FCP command is not supported. Data: None Severity: Error Log: LOG_FCP Action: None required. 2721: ndlp null for oxid %x SID %x\n, icmd->ulpContext, dfchba->ct_ctx[tag].SID); The node value for this SID is not in the node list. Data: None Severity: Warning Log: LOG_ELS Action: None required.
Emulex Drivers for Linux User Guide Appendix A: lpfc Driver BlockGuard Functionality This appendix describes how to enable BlockGuard and set lpfc driver module parameters. A.1 Overview The BlockGuard feature checks the integrity of data read from and written to the host to the disk and back through the SAN. This check is implemented through the DIF defined in the ANSI T10 standard. The Emulex lpfc driver supports T10 DIF Type 1.
Emulex Drivers for Linux User Guide A.2 Enabling BlockGuard BlockGuard is disabled by default. To enable it, the lpfc_enable_bg parameter must be passed to the driver as follows: insmod lpfc.ko lpfc_enable_bg=1 For a permanent configuration that will persist across system reboots, create the /etc/modprobe.d/elx-lpfc.conf file, and place the following line into it: options lpfc lpfc_enable_bg=1 Additional module parameters can be added to this line, separated by spaces. A.
Emulex Drivers for Linux User Guide The initiator operations are listed in the following table. Table 8: Initiator Operations Initiator Operation Initiator Host <-> Adapter Adapter <-> Target Comment NORMAL Unprotected Unprotected Used for unprotected I/O. READ_INSERT Protected Unprotected Reads the data from the target. The adapter then generates the protection data and transfers both data and protection data to the Initiator Host. No protection data is sent on the SAN.
Emulex Drivers for Linux User Guide A.4.1 lpfc_prot_mask This parameter controls the DIF operations that the driver registers with the operating system. The operating system selects an operation to use for each I/O command that matches the adapter DIF capability. The driver indicates its capabilities by the operations it registers with the operating system. If the parameter is not passed to the driver, the default DIX_TYPE0 is used.
Emulex Drivers for Linux User Guide Appendix B: Configuring NVMe over FC on a Target NOTE: Before configuring NVMe over FC on a target using native NVMe CLI commands, ensure that you have installed the latest Emulex firmware for the LPe31000-series, LPe32000-series, and LPe35000-series adapters. At this time, NVMe over FC on target devices is supported on SLES 12 SP3 and SLES 12 SP4 only. The NVMe target drivers are meant for evaluation and testing during development only.
Emulex Drivers for Linux User Guide └─3600000e00d2a0000002a017300350000 sdd └─3600000e00d2a0000002a017300360000 sde └─3600000e00d2a0000002a017300370000 sdf └─3600000e00d2a0000002a017300380000 254:5 0 3G 0 mpath 8:48 0 3G 0 disk 254:6 0 3G 0 mpath 8:64 0 3G 0 disk 254:7 0 3G 0 mpath 8:80 0 3G 0 disk 254:8 0 3G 0 mpath Record the block devices you want to use, for example /dev/sde, /dev/sdf, or /dev/nvme0n1. NOTE: Block devices are located in the /dev directory. 4.
Emulex Drivers for Linux User Guide 3. Navigate to the /subsystems/fctest1 subdirectory, and set the allow_any_host parameter to 1, by typing the following command: set attr allow_any_host=1 4. Navigate to the /subsystems/fctest1/namespaces subdirectory, and create namespace 1 by typing the following command: create 1 5. Navigate to the /subsystems/fctest1/namespaces/1 subdirectory, and set the device path to the backing storage device you recorded previously in Step 3 in Section B.
Emulex Drivers for Linux User Guide Information similar to the following is displayed: Parameter trsvcid is now ‘none’. The port connection has been created. You can create additional port connections by repeating Step 7 through Step 10, incrementing the port number each time. 11. Link the port to the subsystem by navigating to the /ports/1/subsystems directory and typing the following command: create where is the same name as the subsystem you created in Step 2.
Emulex Drivers for Linux User Guide NOTE: If a situation arises in which the initiator system boots before the target system, you must use the Linux issue_lip command after the target system is up. This command allows the initiator to discover the targets. On the initiator system, type the following command: echo 1 > /sys/class/fc_host/host/issue_lip where host represents the host number. If you want to clear the active configuration, perform the following steps: 1. Disable the initiator links. 2.
Emulex Drivers for Linux User Guide Appendix C: Native NVME Multipathing Two multipathing options can be used with NVMe storage: Device Mapper (DM) and Native NVMe Multipathing. DM is a general block-device multipathing framework that can work with devices of any protocol. DM supports the addition of hardware-specific handlers to help manage the storage device and its path management. DM has been used extensively with SCSI storage. DM can be used in its generic form with NVMe storage.
Emulex Drivers for Linux User Guide When Native NVMe Multipathing is not enabled, because each controller is seen as unique, namespaces for the subsystem are created for every controller on which the namespace is found. Processing of I/O requests by the device name are handled only by the controller, and they are blindly passed on to the storage device.
Emulex Drivers for Linux User Guide When Native NVMe Multipathing is enabled, you can display the list of subsystems that have been detected by the system using the new nvme list-subsys command. For example: nvme list-subsys nvme-subsys0 - NQN=nqn.2014-08.org.nvmexpress:NVMf:uuid:19d48a6d-3644-4f65-8046-80bd88fe45a6 \ +- nvme0 fc traddr=nn-0x20000090fa942e16:pn-0x10000090fa942e16 host_traddr=nn-0x200000109b346f1f:pn0x100000109b346f1f +- nvme3 fc traddr=nn-0x20000090fa942e16:pn-0x10000090fa942e16 host_tradd
Emulex Drivers for Linux User Guide Node SN Model Namespace Usage Format FW Rev /dev/nvme2n1 0000000000000000 Linux 1 268.44 GB / 268.44 GB 512 B + 0 B 4.4.131- /dev/nvme2n2 0000000000000000 Linux 1 268.44 GB / 268.44 GB 512 B + 0 B 4.4.131- /dev/nvme2n3 0000000000000000 Linux 1 268.44 GB / 268.44 GB 512 B + 0 B 4.4.131- /dev/nvme2n4 0000000000000000 Linux 1 268.44 GB / 268.44 GB 512 B + 0 B 4.4.131- /dev/nvme3n1 0000000000000000 Linux 1 268.44 GB / 268.
Emulex Drivers for Linux User Guide 0 crw------- 1 root root 246, 0 crw------- 1 root root 246, 0 crw------- 1 root root 246, 7 Jun 10 16:02 /dev/nvme7 8 Jun 10 16:02 /dev/nvme8 9 Jun 10 16:02 /dev/nvme9 This example demonstrates that one device node is created per namespace, with the form /dev/nvme{subsystem instance}n{namespace}.
Emulex Drivers for Linux User Guide lrwxrwxrwx 1 root subsys1/nvme1n2 lrwxrwxrwx 1 root subsys1/nvme1n3 lrwxrwxrwx 1 root subsys1/nvme1n4 lrwxrwxrwx 1 root nvme2/nvme2c224n1 lrwxrwxrwx 1 root nvme2/nvme2c224n2 lrwxrwxrwx 1 root nvme2/nvme2c224n3 lrwxrwxrwx 1 root nvme2/nvme2c224n4 lrwxrwxrwx 1 root nvme7/nvme2c230n1 lrwxrwxrwx 1 root nvme7/nvme2c230n2 lrwxrwxrwx 1 root nvme7/nvme2c230n3 lrwxrwxrwx 1 root nvme7/nvme2c230n4 lrwxrwxrwx 1 root subsys2/nvme2n1 lrwxrwxrwx 1 root subsys2/nvme2n2 lrwxrwxrwx 1 root
Emulex Drivers for Linux User Guide lrwxrwxrwx 1 root nvme4/nvme4c226n3 lrwxrwxrwx 1 root nvme4/nvme4c226n4 lrwxrwxrwx 1 root nvme8/nvme4c231n1 lrwxrwxrwx 1 root nvme8/nvme4c231n2 lrwxrwxrwx 1 root nvme8/nvme4c231n3 lrwxrwxrwx 1 root nvme8/nvme4c231n4 lrwxrwxrwx 1 root subsys4/nvme4n1 lrwxrwxrwx 1 root subsys4/nvme4n2 lrwxrwxrwx 1 root subsys4/nvme4n3 lrwxrwxrwx 1 root subsys4/nvme4n4 root 0 Jun 11 09:56 /sys/block/nvme4c226n3 -> ..
Emulex Drivers for Linux User Guide Appendix D: Trunking Support Before you configure trunking on the Emulex adapter, follow the Brocade® instructions for configuring trunking on the switch. NOTE: Before you enable or disable trunking on the Emulex adapter, follow the instructions from Brocade to enable or disable trunking on the switch. Dynamic D_Port cannot co-exist with the trunking feature (also called FC port aggregation) on LPe35000-series adapters.
Emulex Drivers for Linux User Guide An example of an LPe35004 adapter, showing 2-lane port aggregation with a single SCSI host follows. # cat /sys/class/scsi_host/host13/link_state Link Up - Ready Fabric Trunk port 0: Link Up Trunk port 1: Link Up # cat /sys/class/scsi_host/host14/link_state Link Up - Ready Fabric Trunk port 2: Link Up Trunk port 3: Link Up An example of an LPe35004 adapter, showing 4-lane port aggregation with a single SCSI host follows.
Emulex Drivers for Linux User Guide Appendix E: FC-SP-2 Authentication (DHCHAP) Support NOTE: DHCHAP is available only for physical ports, not for virtual ports. The authentication driver parameters are only available on local hosts and not for any remote hosts. Boot from SAN is not supported when DHCHAP authentication is enabled. DHCHAP is not supported on FA-PWWN ports. DHCHAP is not supported if Dynamic D_PORT is enabled.
