Emulex® Drivers for Linux User Guide Release 12.
Broadcom, the pulse logo, Connecting everything, Avago Technologies, Avago, the A logo, Brocade, Emulex, ExpressLane, LightPulse, and OneCommand are among the trademarks of Broadcom and/or its affiliates in the United States, certain other countries, and/or the EU. Copyright © 2003–2020 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 vPort sysfs ......................................................................................................................................................28 3.2.3.1 vPort sysfs Tree ....................................................................................................................................28 3.2.3.2 vPort sysfs Entries ....................................................................................................................
Emulex Drivers for Linux User Guide Chapter 1: Introduction 1.1 Overview This guide provides procedures for installing, updating, uninstalling, configuring, and troubleshooting several types of drivers for Linux that are supported by Emulex®. This guide is applicable to several versions of drivers, operating systems, firmware, and adapters. For supported firmware versions and their latest release, go to www.broadcom.com.
Emulex Drivers for Linux User Guide Table 1: Acronyms and Abbreviations (Continued) Acronym/Abbreviation Description FPIN Fabric Performance Impact Notification GnuPG GNU Privacy Guard I/O input/output IOCB input/output control block IOCBQ input/output control block queue IOPS input/output operations per second IOTAG input/output tag ISR interrupt service routine LBA logical block address LPFC LightPulse® Fibre Channel MQ mailbox queue MSI message signaled interrupt MSI-X extende
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 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 held only by Emulex.
Emulex Drivers for Linux User Guide 2.2 Emulex FC Driver Kit The Emulex FC driver kit contains the following items: 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 might also include any of the following RPMs: – nvmefc-connect RPM – elx-lpfc-extras RPM NOTE: Use only officially released Linux distribution kernels.
Emulex Drivers for Linux User Guide Run the elx_lpfc_install.sh script with the -n option: ./elx_lpfc_install.sh -n This installs the lpfc driver along with nvmefc-connect rpm. After the elx_lpfc_install.sh script has finished running successfully, the NVMe over FC driver is installed. 5. Reboot the system to enable the newly added driver options in the ramdisk. 6.
Emulex Drivers for Linux User Guide To update the firmware using the sysfs command, perform the following steps: 1. Before you update the firmware, procure the model name of the adapter. cat /sys/class/scsi_host//modelname 2. Modify the firmware file name to the model name. 3. Copy the firmware file to /lib/firmware with the model name. cp .grp /lib/firmware/ 4. Run the following command and note the value for lpfc_log_verbose.
Emulex Drivers for Linux User Guide 2.6 Installing the NVMe over FC Driver This section describes how to install the out-of-box NVMe drivers. NOTE: The NVMe over FC target drivers are meant for evaluation and testing during development only. They are not intended for production use. NVMe over FC is supported on LPe31000-series, LPe32000-series, and LPe35000-series adapters. 2.6.
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 changes 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 shuts 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_irq_chann Defines the number of EQs (and MSI-X vectors) Yes requested. The default value is 0. A value of 0 means that the driver automatically determines a recommended amount of EQs, MSI-X vectors, and lpfc_hdw_queue to allocate based on system resources. This value is limited by the lesser of the number of CPUs and lpfc_hdw_queue.
Emulex Drivers for Linux User Guide Table 2: Static FC Driver Parameters (Continued) Parameter Description sysfs Visible lpfc_sg_seg_cnt Controls the scatter/gather maximum segment count Yes passed to the FC driver. This variable is applicable per SCSI command. For Emulex LPe12000-series adapters, the minimum value is 64 (default), and the maximum value is 4096. For all other adapters, the minimum value is 64 (default), and the maximum value is 510.
Emulex Drivers for Linux User Guide 3.1.1.2 Dynamic FC Driver Parameters Changes to most dynamic parameters take effect immediately; some do not take effect until a port reset occurs. 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_io_sched Determines which algorithm to use when scheduling Yes an FC I/O to an I/O channel. For more information, see Section 3.3, FC Driver Performance Tuning. The value 0 configures “schedule by hardware queue” (rather than round robin). A value of 1 (default) configures “schedule by CPU.
Emulex Drivers for Linux User Guide Table 3: Dynamic FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_nvme_enable_fb Enables NVMe first burst on initiator and target Yes functions. For an initiator, enabling this parameter means that an NVMET PRLI response with FBA enabled and an FB_SIZE set to a nonzero value is processed by the initiator for subsequent NVMe FCP I/O. Currently, this feature is not supported on NVMe targets.
Emulex Drivers for Linux User Guide Table 3: Dynamic FC Driver Parameters (Continued) Parameter Description sysfs Visible Applicable Adapters Activation lpfc_suppress_rsp Negotiates whether to suppress the RSP from a target Yes during a PLOGI. The minimum value is 0. The maximum value is 1. The default value is 1. LPe16000-series, LPe31000-series, LPe32000-series, and LPe35000-series adapters Dynamic lpfc_tgt_queue_depth Limits the number of outstanding commands per target Yes port.
Emulex Drivers for Linux User Guide 3.1.2 Configuring FC Driver Parameters You can configure FC driver parameters using any of the following methods: The modprobe command for temporary configuration The elx-lpfc.conf file for persistent configuration The sysfs interface (to view and modify parameters after loading the FC driver) NOTE: Not all parameters visible in the sysfs directory can be modified; some are read-only.
Emulex Drivers for Linux User Guide 3.1.2.3 Configuring Parameters with the sysfs Command sysfs is a virtual file system that exposes the structure of the system. It also includes interfaces to driver parameters through which the FC driver parameters can be viewed and modified. Because these interfaces are available only after driver load, only dynamic FC driver parameters can be changed. However, both static and dynamic FC driver parameters can be read through sysfs.
Emulex Drivers for Linux User Guide To modify the lpfc_log_verbose value to 0xffffffff: echo 0xffffffff > /sys/class/scsi_host/host7/lpfc_log_verbose Reading the lpfc_log_verbose file now shows a value of 0xffffffff: cat /sys/class/scsi_host/host7/lpfc_log_verbose 0xffffffff 3.1.3 Creating a New Ramdisk Image The elx_lpfc_install.sh script creates a ramdisk image that contains the FC driver for the currently running kernel.
Emulex Drivers for Linux User Guide 3.1.5.2 Configuring the System to Boot Using Persistent Names For SLES Operating Systems: NOTE: The SLES operating systems are configured by default with udev to provide persistent names for hard disks, including FC-attached disks. To use a persistent name for a boot, perform the following steps: 1. Do one of the following: – For x86 boot: In the /boot/grub/menu.lst file, find the kernel line for the default boot.
Emulex Drivers for Linux User Guide 3.1.5.3 Using udev with st Devices In Linux, the driver for SCSI tape drives is st. A tape device name has an st prefix. The udev rules for tape devices are the same as for disk devices. A unique ID must exist that persists across initiator reboots and persists regardless of discovery order. You must consider whether the tape device is an FC tape device or an FC-SCSI tape device (in which multiple SCSI tape devices reside behind an FC controller).
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
Emulex Drivers for Linux User Guide 3.1.6 ExpressLane Support The host servers do not distinguish between lower and higher priority workloads being sent to LUNs. For flash storage deployed in mixed storage environments, the combination of data from rotating media and flash devices can cause congestion on the network and reduced performance for the flash storage devices. The ExpressLane feature enables special priority queuing for selected LUNs (ExpressLane LUNs).
Emulex Drivers for Linux User Guide 3.2.2.1 Creating vPorts Using the mkvport.sh Script You can use the mkvport.sh 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 that matches 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 following vPort configuration limits have been tested with and are supported by the Emulex driver. Configurations that exceed one or more of these limits are unsupported. The maximum number of vPorts configurable on a physical port is 255. 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.
Emulex Drivers for Linux User Guide 3.3.1.2 lpfc_irq_chann The lpfc_irq_chann module parameter can be configured at driver load time. It defines the number of MSI-X vectors supported by the driver for each port. The driver is capable of supporting parallel I/O paths, and each I/O path is capable of posting and completing FCP and NVMe commands independent of the other. Each IRQ channel is composed of a unique MSI-X vector and an event queue.
Emulex Drivers for Linux User Guide Chapter 4: Configuring NVMe over FC NOTE: The NVMe over FC target drivers are meant for evaluation and testing during development only. They are not intended for production use. NVMe over FC is supported on LPe31000-series, LPe32000-series, and LPe35000-series adapters. 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 chapter explains some 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 Resolutions (Continued) Situation Resolution rmmod fails to unload an FC driver module due to ERROR: Module lpfc is in use. This message can appear when you attempt to remove the driver and a logical volume group is dependent on the driver. Driver unload is not supported in SAN-booted environments unless the inbox driver supports SAN boot. Otherwise, use the following steps to resolve this situation: 1.
Emulex Drivers for Linux User Guide Table 6: FC Driver Situations and Resolutions (Continued) Situation Driver uninstall fails. Resolution The elx_lpfc_install.sh --uninstall script fails with an error. Try the following solutions: Uninstall the Emulex HBA Manager application; refer to the Emulex HBA Manager Application User Guide for instructions. Unmount all FC disk drives. Unload the lpfc driver. Use rpm -e `rpm -qa | grep lpfc` to uninstall the lpfc driver RPM. The elx_lpfc_install.
Emulex Drivers for Linux User Guide 3. Collect firmware logs. cat /debug/lpfc/fn#/fw_log where # is the port for which you want to generate firmware logs. 5.4 FC Driver Log Messages The following sections describe retrieving and interpreting FC driver log messages. 5.4.1 Retrieving FC Driver Log Messages FC error log messages are logged in the /var/log/messages file. An example of an FC message follows: Jul 2 04:23:34 daffy kernel: lpfc 0000:03:06.
Emulex Drivers for Linux User Guide Table 7: Message Log Table (Continued) LOG Message Verbose Mask Definition Verbose Bit Verbose Description LOG_EVENT 0x00010000 CT, TEMP, DUMP, logging LOG_FIP 0x00020000 FIP events LOG_FCP_UNDER 0x00040000 FCP underruns errors LOG_SCSI_CMD 0x00080000 ALL SCSI commands LOG_NVME 0x00100000 NVME general events LOG_NVME_DISC 0x00200000 NVME discovery/connect events LOG_NVME_ABTS 0x00400000 NVME ABTS events LOG_NVME_IOERR 0x00800000 NVME I/O Error e
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0126: FDISC failed ulpStatus ulpWord4 Data: lsRjtError Severity: Error Log: Always Action: Reconfigure the switch to support more NPIV logins. If this issue persists, contact Broadcom Technical Support. 0127: ELS timeout An ELS IOCB command was posted to a ring and did not complete within ULP timeout seconds.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 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. 0140: PLOGI Reject: invalid name Invalid node WWN provided. Data: None Severity: Error Log: LOG_ELS Action: None required. 0141: PLOGI Reject: invalid pname Invalid port WWN provided.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 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. 0149: Failed to allocate memory for ELS event Memory could not be allocated to send the ELS event to the FC transport. Data: None Severity: Error Log: LOG_ELS Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0221: FAN timeout A link-up event was received without the login bit set, so the driver waits E_D_TOV for the fabric to send a FAN. If no FAN if received, a FLOGI will be sent after the timeout. Data: None Severity: Warning Log: LOG_DISCOVERY verbose Action: None required. The driver recovers from this condition by issuing a FLOGI to the fabric.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0231: RSCN timeout The driver has lost track of which N_Ports have RSCNs pending. Data: (1) fc_ns_retry (2) lpfc_max_ns_retry Severity: Error Log: Always Action: None required. The driver should recover from this event. 0233: Nodelist not empty Driver unloaded or hot plug detected a node still in use. Data: None Severity: Error Log: LOG_DISCOVERY Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0252: Cannot issue NameServer login Could not issue an ELS PLOGI to the NameServer DID. Data: None Severity: Error Log: LOG_ELS Action: Check the port connection and the switch configuration. 0253: Register VPI: Can’t send mbox\ Could not issue the REG_VPI mailbox command for this vPort. Data: None Severity: Error Log: LOG_MBOX Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0259: No NPIV Fabric support The switch to which the port is connected does not support NPIV. Data: None Severity: Error Log: LOG_ELS Action: Check the switch configuration. 0260: Register NameServer error: The REG_LOGIN mailbox command has failed for the NameServer.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0267: NameServer GFF Rsp Error ( ) Data: The NameServer GFF CT request failed. Data: (1) vports fc_flag (2) vports fc_rscn_id_cnt Severity: Error Log: LOG_DISCOVERY Action: Check the port and switch configurations. 0268: NS cmd Error ( ) The NameServer CT request failed.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0276: lpfc_nlp_get: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp>kref.refcount) A kref_get was attempted on a node that was being released. Data: None Severity: Warning Log: LOG_NODE Action: None required. 0277: lpfc_enable_node: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp->kref.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0285: Allocated DMA memory size is less than the requested DMA memorysize Memory allocation was truncated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0286: lpfc_nlp_state_cleanup failed to allocate statistical data buffer Memory allocation failed for node’s statistical data. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0294: PM resume Failed to enable interrupt The PCI resume (hot plug) could not get an interrupt vector. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver. 0297: Invalid device group While unloading the driver, the driver detected a PCI device that it should not have claimed. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0303: Ring handler: portRspPut is bigger then rsp ring The port rsp ring put index is larger than the size of the rsp ring. Data: None Severity: Error Log: Always Action: This error could indicate a software driver, firmware, or hardware issue. Report these errors to Broadcom Technical Support.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0317: iotag is out of range: max iotag wd0 The IoTag in the completed IOCB is out of range. Data: None Severity: Error Log: Always Action: This error could indicate a software driver, firmware or hardware issue. Report these errors to Broadcom Technical Support. 0318: Failed to allocate IOTAG. last IOTAG is The driver cannot allocate an IOTAG.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0328: Rsp Ring error: IOCB Data: The firmware has returned an error for this IOCB. Data: (1) , (2) Severity: Warning Log: LOG_SLI Action: None required. 0330: IOCB wake NOT set The completion handler associated with the IOCB was never called.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0342: Ring Cannot find buffer for an unsolicited iocb tag This is a multiple IOCB unsolicited command, and sufficient buffer space cannot be allocated for it. Data: None Severity: Error Log: LOG_SLI Action: None required. 0343: Ring Cannot find buffer for an unsolicited iocb tag No more preallocated buffers are available to handle unsolicited buffers.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0349: rc should be MBX_SUCCESS The next mailbox command on the mailbox queue has failed. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 0350: rc should have been MBX_BUSY Attempting to unregister a default RPI from an interrupt context, and the mailbox state is not busy. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0361:Unsupported CQ count. Cannot create an completion queue of this size. Data: None Severity: Error Log: LOG_SLI Action: None required. 0362:Unsupported MQ count. Cannot create a mailbox queue of this size. Data: None Severity: Error Log: LOG_SLI Action: None required. 0364:Invalid param: SLI-4: The post-SGL function was passed an invalid XRI.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0370: Invalid completion queue type The event queue entry is not for a mailbox or a work queue entry. Data: None Severity: Error Log: LOG_SLI Action: None required. 0372: iotag lookup error: max iotag () iocb_flag The IOCB lookup cannot be performed because the iotag is out of range. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC 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 8: FC Error Log Messages and Their Descriptions (Continued) 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. 0391:Error during rpi post operation The driver was trying to post pages to the firmware to keep target login information and encountered a failure.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0399 Invalid link attention type: The READ_LA mailbox command returned an invalid link type. Data: None Severity: Error Log: LOG_INIT Action: None required. 0401: Ignoring change to nodev_tmo because devloss_tmo is set Attempting to change the nodev timeout when the devloss has already been set. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0410: Cannot find virtual addr for mapped buf on ring The driver cannot find the specified buffer in its mapping table. Therefore, it cannot find the virtual address needed to access the data. Data: (1) phys (2) next (3) prev (4) postbufq_cnt Severity: Error Log: Always Action: This error could indicate a software driver or firmware issue.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0427: Cannot re-enable interrupt after slot reset The driver was unable to enable the interrupt after an HBA reset. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver. 0429: MSI-X fast-path request_irq failed () The driver received an error for the request_irq_call. Data: None Severity: Warning Log: LOG_INIT Action: Unload and reload the driver.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0436: Adapter failed to init, timeout, status reg The adapter failed during powerup diagnostics after it was reset. 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 8: FC Error Log Messages and Their Descriptions (Continued) 0448: Adapter failed to init, mbxCmd READ_SPARM, mbxStatus Adapter initialization failed when issuing a READ_SPARM 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 8: FC Error Log Messages and Their Descriptions (Continued) 0459: Adapter heartbeat still outstanding:last compl time was
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0474: Unable to allocate memory for issuing MBOX_CONFIG_MSI command Mailbox memory pool allocation error. Data: None Severity: Error Log: LOG_INIT Action: None required. 0475: Not configured for supporting MSI-X cfg_use_msi: 0x%x The lpfc_use_msi module parameter should have been set to 2. Data: None Severity: Error Log: LOG_INIT Action: Set module parameter lpfc_use_msi= 2.
Emulex Drivers for Linux User Guide Table 8: FC 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 8: FC Error Log Messages and Their Descriptions (Continued) 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. Data: None Severity: Error Log: LOG_INIT Action: None required. 0504: Failed allocate slow-path ELS WQ Failed to allocate slow-path ELS WQ.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0530: ELS CQ not allocated The ELS CQ is not allocated. Data: None Severity: Error Log: LOG_INIT Action: None required. 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. 0540: Receive Queue not allocated The Receive Queue is not allocated.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0546: lpfc_create_static_vport failed to create vport Failed to create a vPort. Data: None Severity: Warning Log: LOG_INIT Action: None required. 0582: Error during sgl post operation The SGL post operation failed. Data: None Severity: Error Log: LOG_MBOX, LOG_IP verbose Action: None required. 0602: Failed to allocate CQ_EVENT entry Failed to allocate a CQ_EVENT entry.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0708: Allocation request of command buffers did not succeed. Allocated buffers. The allocation request for the specified command buffers did not succeed. However, the specified number of buffers are allocated. Data: None Severity: Warning Log: LOG_FCP Action: None required. 0713: SCSI layer issued Device Reset (%d, %d) A device reset was issued.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 0727: TMF to TGT LUN failed (, ) The task management command failed. Data: None Severity: Error Log: LOG_FCP Action: None required. 0748: Abort handler timed out waiting for abort to complete:ret D LUN The abort handler timed out waiting for abort to complete. Data: None Severity: Error Log: Always Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC 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 8: FC Error Log Messages and Their Descriptions (Continued) 1400 - Failed to update xri-sgl size and mapping: %d Updatation of host els xri-sgl sizes and mappings failed. Data: None Severity: Error LOG: LOG_MBOX | LOG_SLI 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 8: FC Error Log Messages and Their Descriptions (Continued) 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. 1410: Failed to set up pci memory space. Initialization failed to set up PCI memory space.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1418: Invalid HBA PCI device group: Invalid HBA PCI device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1419: Invalid HBA PCI device group: Invalid HBA PCI device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1420: Invalid HBA PCI device group: Invalid HBA PCI device group detected.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1425: Invalid PCI device group: Invalid HBA PCI device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1426: Invalid PCI device group: Invalid HBA PCI device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1427: Invalid PCI device group: Invalid HBA PCI device group detected.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1432: Failed to initialize rpi headers. Failed to initialize RPI headers. Data: None Severity: Error Log: LOG_INIT Action: None required. 1476: Failed to allocate sysfs attr Failed to allocate sysfs attrIbutes. Data: None Severity: Error Log: LOG_INIT Action: None required. 1477: Failed to set up hba Failed to set up the HBA. Data: None Severity: Error Log: LOG_INIT Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1817: Fabric does not support NPIV - configuring single port mode The fabric reports no support for NPIV upon FLOGI. Data: None Severity: Warning Log: LOG_VPORT verbose Action: No action needed, informational. 1818: VPort failed init, mbxCmd READ_SPARM mbxStatus , rc = A pending mailbox command that was issued to initialize the port failed.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1824: NPIV enabled: Override lpfc_sli_mode parameter () to auto(0) The lpfc_enable_npiv and lpfc_sli_mode driver parameter settings conflict. The HBA must be configured for SLI-3 mode to support NPIV. Data: (1) lpfc_sli_mode Severity: Error Log: LOG_VPORT verbose Action: This is an informational message that indicates that the lpfc_enable_npiv and lpfc_sli_mode parameter settings are not compatible.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 1831: Create VPORT Interrupted The port creation process was unexpectedly interrupted at a critical time, and the operation was unsuccessful. Data: None Severity: Error Log: LOG_VPORT verbose Action: The process was interrupted while creating a vPort. Retry the command. 1832: No pending MBOX command to handle Data: None Severity: Error Log: LOG_MBOX Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2001: Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command Unable to allocate memory for issuing the SLI_CONFIG_SPECIAL mailbox command. Data: None Severity: Error Log: LOG_SLI Action: None required. 2002: Error Could not grow rpi count An error occurred because the RPI count could not be increased. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2011: Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command Data: None Severity: Error Log: LOG_SLI Action: None required. 2012: Mailbox failed , mbxCmd READ_CONFIG, mbxStatus The READ_CONFIG mailbox command failed. Data: None Severity: Error Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2500: EQ_CREATE mailbox failed with status add_status , mbx status The mailbox command sent to create the event queue failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2501: CQ_CREATE mailbox failed with status add_status , mbx status The mailbox command sent to create the completion queue failed.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2506: CQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the completion queue failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2507: MQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the mailbox queue failed.
Emulex Drivers for Linux User Guide Table 8: FC 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 8: FC Error Log Messages and Their Descriptions (Continued) 2523: Allocated DMA memory size () is less than the requested DMA memory size () The ADD_FCF_RECORD mailbox command failed to retrieve the length required from the firmware. Data: None Severity: Error Log: LOG_INIT Action: None required. 2524: Failed to get the non-embedded SGE virtual address The READ_FCF_RECORD mailbox command could not retrieve the SGE that was requested.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2533: Mailbox command () cannot issue Data: (1) sli4_mbox_opcode (2) sli_flag (3) MBX_NOWAIT Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 2535: Unsupported RQ count. () The RQ ring can only be 512, 1024, 2048, or 4096. Data: None Severity: Error Log: LOG_SLI Action: None required. 2536: Unsupported RQ count.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2543: Mailbox command () cannot issue The mailbox command does not have all of the fields set correctly. Data: (1) sli_mbox_opcode (2) sli_flag (3) flag Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 2544: Mailbox command () cannot issue The HBA cannot be accessed on the PCI bus.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2551: UNREG_FCFI mbox allocation failed HBA state The allocation for the UNREG_FCFI mailbox command failed. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required. 2552: UNREG_FCFI issue mbox failed rc HBA state The UNREG_FCFI mailbox command failed. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2559: Block sgl registration required DMA size great than a page. Attempting to register more SGEs with the firmware than can fit in a page. Data: None Severity: Warning Log: LOG_INIT Action: None required. 2562 - Failure to allocate an ELS sgl entry:%d Memory allocation failed for SGL entry. Data: None Severity: Error LOG: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 2574 - IO channels: hdwQ %d IRQ %d MRQ: %d Information about HWQ, interrupts, and MRQ. Data: None Severity: Error LOG: LOG_INIT Action: None required. 2579: Slow-path wqe consume event carries miss-matched qid: wcqe-qid=, sp-qid= The consumed entry does not have the queue ID of the slow-path. Data: None Severity: Warning Log: LOG_SLI Action: None required.
Emulex Drivers for Linux User Guide Table 8: FC 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 8: FC 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 - IO completion: Not an active IO The I/O was not an active I/O in the completion routine.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 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. 2726: READ_FCF_RECORD Indicates empty FCF table The driver requested the firmware for a list of FCF entries to connect to and the firmware responded indicating that the FCF table is empty.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 6072: NVME Completion Error: xri status x result x [x] placed x NVMe I/O completed with an error. Data: (1) sli4_xritag, (2) status, (3)result ,(4) parameter and (4) total_data_placed. Log: LOG_NVME_IOERR Severity: Info Action: This error could indicate a software driver, firmware, or hardware issue.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 6059: dptr err , nseg Scatter-gather data pointer is null. Data: (1) i and (2) nseg. Log: LOG_NVME_IOERR Severity: Error Action: This error could indicate a software driver issue. If this issue persists, report the error to Broadcom Technical Support. 6063: NVME DMA Prep Err: sg_cnt payload_length x NVMe DMA preparation failed.
Emulex Drivers for Linux User Guide Table 8: FC Error Log Messages and Their Descriptions (Continued) 6144: Outstanding NVME I/O Abort Request still pending on nvme_fcreq x, lpfc_ncmd xri x Outstanding NVMEe I/O abort request still pending. Data: (1) pnvme_fcreq and (2) sli4_xritag. Log: LOG_NVME_ABTS Severity: Error Action: None required. 6176: Lport x Localport x wait timed out. Pending . Renewing. NVMe port is waiting for I/O completion.
Emulex Drivers for Linux User Guide Appendix A: FCP Driver BlockGuard Functionality This appendix describes how to enable the BlockGuard feature and to set FCP 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 FCP 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 persists 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 9: 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 The lpfc_prot_mask 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: 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.
Emulex Drivers for Linux User Guide sdc └─3600000e00d2a0000002a017300350000 sdd └─3600000e00d2a0000002a017300360000 sde └─3600000e00d2a0000002a017300370000 sdf └─3600000e00d2a0000002a017300380000 8:32 0 3G 0 disk 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 that you want to use, for example /dev/sde, /dev/sdf, or /dev/nvme0n1.
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 that you recorded previously in Step 3 in Appendix 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.
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: 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 is 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 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_traddr=nn
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 following form: /dev/nvme{subsystem instance}n{namespace} Additionally, nodes are created for the controller instances /dev/nvme{controller instance}, but it is important to note that the subsystem instance and the controll
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 Trunking enables you to combine multiple physical FC links to form a single logical link (aggregated port). The aggregated port’s maximum link speed is the sum of the maximum link speeds of the individual physical links that comprise the aggregated port. For example, an aggregated port comprised of two physical links running at 32Gb/s each will have a potential logical (aggregate) link speed of 64Gb/s.
Emulex Drivers for Linux User Guide Following is an example of an LPe35004 adapter showing 2-lane port aggregation with a single SCSI host: # 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 Following is an example of an LPe35004 adapter showing 4-lane port aggregation with a single SCSI host: # cat /sys/class/scsi_host/host13/link_sta
Emulex Drivers for Linux User Guide Appendix E: FC-SP-2 Authentication (DH-CHAP) Support Fibre Channel Security Protocol-2 (FC-SP-2) DH-CHAP is a secret-based authentication and key management protocol that uses the CHAP algorithm augmented with an optional Diffie-Hellmann algorithm with hash priority (MD5 and SHA1). NOTE: The following information applies to DH-CHAP authentication: DH-CHAP is available only for physical ports, not for virtual ports.
Emulex Drivers for Linux User Guide Appendix F: ARM Support Emulex HBAs support ARM servers. This appendix describes information pertaining to ARM support. The following inbox Linux operating system distributions are the minimum versions supported on ARM servers: Oracle UEK 5 XenServer Citrix 7.4 XenServer Citrix 8.0 SLES 12 SP4 SLES 15 RHEL and CentOS 7.6 RHEL and CentOS 8.0 OEL 7.7 OEL 8.0 Debian, Ubuntu, National Univ Kylin 16.0.4, 18.0.4, 20.04 Deepin UnionTech UOS 16.0.4, 18.0.
