Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Installing and Uninstalling
- Chapter 3: Configuration
- 3.1 FC Driver Configuration
- 3.2 vPort Configuration
- 3.3 FC Driver Performance Tuning
- Chapter 4: Configuring NVMe over FC
- Chapter 5: Troubleshooting
- Appendix A: FCP Driver BlockGuard Functionality
- Appendix B: Configuring NVMe over FC on a Target
- Appendix C: Native NVMe Multipathing
- Appendix D: Trunking Support
- Appendix E: FC-SP-2 Authentication (DH-CHAP) Support
- Appendix F: ARM Support
Broadcom DRVLin-UG128-100
40
Emulex Drivers for Linux User Guide
5.3 Dynamic Firmware Logging
For firmware-related issues, you might want to refer to the firmware logs. Dynamic firmware logging allows you to collect the
firmware logs when required or when you encounter a firmware issue. You can also enable dynamic firmware logging in the
absence of the Emulex HBA Manager application to dynamically generate firmware logs directly from the driver.
To dynamically generate firmware logs, perform the following steps:
1. Enable lpfc_ras_fwlog_buffsize.
echo 1 > /sys/class/scsi_host/host#/lpfc_ras_fwlog_buffsize
lpfc_ras_fwlog_buffsize is the firmware logging host buffer size. For more information on
lpfc_ras_fwlog_buffsize, see Table 3, Dynamic FC Driver Parameters.
2. Mount debugfs.
mount -t debugfs - /debug
Use debugfs in the absence of the Emulex HBA Manager application.
Driver uninstall fails. 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.sh script exit message
appears.
The elx_lpfc_install.sh script contains exit messages that can be useful in
diagnosing installation issues.
The Emulex driver for Linux does not load in
ramdisk for a custom-built kernel.
Emulex does not support custom-built kernels. However, the Emulex installation
script attempts to install the driver into a ramdisk that follows the naming scheme
used by RHEL or SLES kernels.
The RHEL naming scheme for ramdisk images is:
/boot/initrd-KERNELVERSION.img
The SLES naming scheme for ramdisk images is:
/boot/initrd
If a custom-built kernel has a ramdisk image that does not follow the appropriate
naming scheme, change the name of the image using the following procedure:
1. Change the name of the ramdisk image to match the SLES naming scheme.
2. Update any file links to the ramdisk image.
3. Edit the boot loader configuration file (for example, /etc/lilo.conf, /etc/
yaboot.conf, /boot/grub/grub.conf, /boot/grub/menu.lst), find
any references to the old ramdisk image name, and replace them with the new
name.
4. Reboot the system to verify the changes.
5. Install the Emulex Linux driver kit.
The Linux SCSI subsystem sees only eight LUNs
when more are present.
Some SCSI drivers do not scan past eight LUNs when the target reports itself as a
SCSI-2 device.
To resolve this situation, force a SCSI bus scan with the following command:
/usr/sbin/lpfc/lun_scan
SUSE supplies a /bin/rescan-scsi-bus.sh script, which can be changed to
scan everything.
Table 6: FC Driver Situations and Resolutions (Continued)
Situation Resolution