安装EMULEX HBA卡驱动

合集下载

Emulex 驱动程序 for Linux 版本 14.08.100 发布说明说明书

Release NotesPurpose and Contact InformationThese release notes describe the supported operating systems, new features, resolved issues, FC and NVMe driver known issues, and FC and NVMe driver technical tips associated with this release of the Emulex® drivers for Linux.For the latest product documentation, go to . If you have questions or require additional information, contact an authorized Broadcom® Technical Support representative at *****************************. Supported Operating SystemsThe following table provides information about the supported Linux operating systems, supported driver types, supported architectures, and degree of support in the Emulex HBA Manager, Elxflash, and Emulex HBA Capture utilities.Table 1: Supported Operating SystemsOperating Systems Driver Types x86_64Arm EmulexHBAManager(FullSupport)EmulexHBAManager(LimitedCLISupport)ElxflashEmulex HBACaptureRHEL 7.8-7.9, 8.3-8.7, 9.0-9.1 CentOS 7.8-7.9, 8.3-8.5Oracle Linux 7.8-7.9, 8.3-8.7, 9.0-9.1 (RHEL equivalent)Inbox andout-of-boxX—X—X XOracle Linux 7.x with UEK 5 or 6kernel,8.x with UEK 6 or 7 kernel, 9.x withUEK 7 kernelInbox X—X—X XSLES 12 SP4-SP5, SLES 15 SP2-SP4Inbox andout-of-boxX—X—X XUbuntu 18.04, 20.04, 22.04Inbox X—X(CLI only)—X XEmulex® Drivers for Linux Release 14.0.639.18New FeaturesThe lpfc_suppress_rsp parameter is now disabled (set to 0) by default.Resolved Issues⏹ A server reboot running NVMe boot from SAN (BFS) on the RHEL 9.0 operating system no longer stops responding during the shutdown process.⏹The issue of paths not recovering after a link bounces with a Loop Initialization Primitive (LIP) is resolved.⏹An unrecoverable operating system fault no longer occurs on unloading the driver using the rmmod command after the lpfc_tgt_queue_depth driver parameter has been set to 10.FC Driver Known Issues1.On Red Hat Virtualization (RHV) 4.4, dracut does not add the lpfc driver configuration file to initramfs .Workarounda.Edit the /usr/lib/dracut/dracut.conf.d/02-generic-image.conf file.b.Add a # before the hostonly=no string to comment out the entry.c.Rebuild the initramfs using dracut .2.On RHEL 8.4 inbox drivers, the diagnostic loopback tests always fail and might result in a timeout error.WorkaroundInstall any RHEL 8.4 supported out-of-box driver version.Citrix XenServer 7.2, Citrix Hypervisor 8.xInboxX—X (CLI only, bundled with driver)——X(OneCapture™ release 12.2)FusionOS 22.0.1Inbox X ——X —X RHEL 7.8-7.9, 8.3-8.7, 9.0-9.1Inbox and out-of-box —X —X —X Ubuntu 18.04.3, 20.04, 22.04Inbox —X —X —X openEuler 20.03 SP1, 20.03 SP3, 22.03Inbox and out-of-box —X —X —X Kylin V10 SP1, SP2Inbox —X —X —X UnionTech OS V20 1050EInbox—X—X—XTable 1: Supported Operating Systems (Continued)Operating Systems Driver Types x86_64Arm Emulex HBA Manager (Full Support)Emulex HBA Manager (Limited CLISupport)ElxflashEmulex HBA Capture3.An unrecoverable operating system fault might occur when generating a crash dump after successful installation of theSLES 15 SP2 operating system on a local device or an FC BFS LUN.WorkaroundInstall the SUSE maintenance update dracut-049.1+suse.183.g7282fe92-3.18.2.x86_64.rpm or later.4.On a UnionTech OS V20 server, an unrecoverable operating system fault might occur when deleting NPIV vPorts using sysfs commands.WorkaroundNone.5.On a UnionTech OS V20 server, an unrecoverable operating system fault might occur when a dump is performed usingHBACMD.WorkaroundNone.NVMe Driver Known Issues1.Unloading the Fibre Channel Protocol (FCP) driver using the modprobe -r command might cause issues on the initiatorbefore NVMe devices are disconnected.WorkaroundUnload the driver with rmmod lpfc, or if modprobe –r lpfc is required, wait for the device loss period of 60 seconds before unloading the driver.2.On the Oracle Linux 7.7 unbreakable enterprise kernel (UEK) R6 operating system, unloading a Linux FCP driver withNVMe connections might fail.WorkaroundDisconnect the NVMe connections before unloading the Linux FCP driver.3.On an NVMe controller, reconnectivity issues might occur during switch port toggles. This issue is an operating systemissue.WorkaroundThis issue is fixed in RHEL 8.6. For SLES, contact SUSE technical support.4.The SLES 15 SP3 installer might not discover the NVMe namespace to install the operating system.WorkaroundUse the nvmefc-dm kit to discover the NVMe namespace.5.In the fstab file, when an NVMe namespace mount point entry is included and the defaults option is specified, if theoperating system is rebooted, the operating system might go into emergency mode.WorkaroundsFor SLES15 SP3 and SLES15 SP4:Specify nofail as the mount option when creating the NVMe namespace fstab mount point entry.For RHEL7.x, RHEL8.x, RHEL9.x, SLES 12 SP5, and SLES 15 SP2:–Specify nofail as the mount option when creating the NVMe namespace fstab mount point entry.–Install the nvmf boot dracut module provided in the nvmefc-dm kit.6.On SLES 12 SP5, the nvmefc-boot-connections systemd unit is disabled after the operating system is installedusing NVMe BFS. This issue leads to the operating system failing to discover all NVMe subsystems when a large number of NVMe subsystems exist.WorkaroundManually enable the nvmefc-boot-connections systemd unit. See NVMe Driver Technical Tips, Item6, for more information.7.An unrecoverable operating system fault might occur when generating a crash dump after successful installation of theoperating system in the NVMe BFS namespace.WorkaroundFrom the NVMe BFS kit, extract and install the nvmefc-dm RPM that matches the installed operating system.# tar zxf elx-nvmefc-dm-<version>-<release>/nvmefc-dm-<version>-<release>.<OS>.tar.gz 8.If the operating system was installed using NVMe over FC BFS, and you are updating the firmware from version12.8.xxx.xx to version 14.0.xxx.xx, the NVMe storage might not be found, and the UEFI boot menu might not boot theoperating system.WorkaroundIn the UEFI configuration utility, enable the Generate and use a Port Based HostNQN option. Refer to the Emulex Boot for the Fibre Channel and NVMe over FC Protocols User Guide for details.9.If the operating system was installed using NVMe over FC BFS, and you are updating the firmware from version14.0.xxx.xx to version 12.8.xxx.xx, NVMe storage might not be found, and the UEFI boot menu might not boot theoperating system.WorkaroundUpdate the SAN storage configuration and add an adapter WWPN-based HostNQN to the storage array.FC Driver Technical Tips1.For secure boot of the RHEL operating system, download the public key file for the RHEL operating system from, and place it in the systems key ring before installing the signed lpfc driver for the RHEL operating system. Refer to the Red Hat documentation for instructions on adding a kernel module to the system.2.On Red Hat operating systems, the installer automatically searches for a DUD on a storage volume labeled OEMDRV. Fordetails, refer to the Red Hat documentation.3.Out-of-box Linux driver builds are built on, and are intended to be run on, general availability (GA) kernels for theirrespective distributions. If you need an out-of-box Linux driver build for a subsequent distribution’s errata kernel, you might need to recompile the driver from the Linux driver source file on the errata kernel.4.In the Emulex Drivers for Linux User Guide, there is a change to the value specified for the driver parameterlpfc_log_verbose in Step 5 in Section 2.5, Updating the Firmware. For details, refer to the Emulex Drivers for Linux User Guide.NVMe Driver Technical Tips1.Creation of N_Port ID Virtualization (NPIV) connections on initiator ports that are configured for NVMe over FC is notsupported. However, initiator ports can connect to FCP and NVMe targets simultaneously.2.NVMe disks might not reconnect after a device timeout greater than 60 seconds has occurred.WorkaroundYou must perform a manual scan or connect using the nvme connect-all CLI command.3.To enable autoconnect on the following operating systems, install nvme-cli from the operating system distributionmedia:–RHEL 8.3–SLES 15 SP2–SLES 12 SP54.To manually scan for targets or dynamically added subsystems, enter the following command (all on one line):nvme connect-all --transport=fc --host-traddr=nn-<initiator_WWNN>:pn-<initiator_WWPN>--traddr=nn-<target_WWNN>:pn-<target_WWPN>where:–<initiator_WWNN> is the WWNN of the initiator, in hexadecimal.–<initiator_WWPN> is the WWPN of the initiator, in hexadecimal.–<target_WWNN> is the WWNN of the target, in hexadecimal.–<target_WWPN> is the WWPN of the target, in hexadecimal.For example:# nvme connect-all --transport=fc --host-traddr=nn-0x20000090fa942779:pn-0x10000090fa942779 --traddr=nn-0x20000090fae39706:pn-0x10000090fae397065.If the following files are present on the system after the operating system is installed, the operating system has alreadyinstalled NVMe over FC autoconnect facilities. Do not install the Emulex autoconnect script file for inbox NVMe over FC drivers.–/usr/lib/systemd/system/nvmefc-boot-connections.service–/usr/lib/systemd/system/nvmefc-connect@.service–/usr/lib/udev/rules.d/70-nvmefc-autoconnect.rules6.Back up the initial ramdisk before upgrading the operating system.During an operating system upgrade, the kernel or nvme-cli might be upgraded. Back up the initial ramdisk before upgrading the operating system to ensure that the operating system is still bootable in the event that NVMe BFS fails because of a change in either the kernel or nvme-cli.Change the directory to /boot, and make a copy of the initial ramdisk.Example for SUSE operating systems:# cd /boot# cp initrd-$(uname -r) initrd-$(uname -r).bakExample for Red Hat operating systems:# cd /boot# cp initramfs-$(uname -r).img initramfs-$(uname -r).img.origCopyright © 2022 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, go to . All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others.。

Emulex卡安装及配置

EMC ClARiiON CX600安装Emulex卡识别LUN过程1.关闭主机，安装Emulex卡 (1)2.查看主机是否已经正确识别Emulex卡 (1)3.安装Emulex卡的驱动程序及管理工具包 (1)4.让主机正确使用Emulex卡 (14)4.1 Emulex命令行 (14)5. 装EMC阵列Agent软件 (15)5.1 确定Emc Lun Target号 (17)5.2 使Emulex卡识别多个Emc Luns (18)背景：1．EMC ClARiiON CX6002．EMC 32-port Switch3．F48004．Emulex Card1.关闭主机，安装Emulex卡.启动主机ok> boot –rEntering OBP ...Cannot Init Link.*** FCode LP9802 PCI_Bus (lpfc) Version 1.40a0 *** //OBP级别识别Emulex卡2.查看主机是否已经正确识别Emulex卡root@mdsales # /usr/platform/sun4u/sbin/prtdiag –v/N0/IB8/P1 PCI 29 B 5 33 33 2,0 ok lpfc-pci10df,f980/sd (block) LP98023.安装Emulex卡的驱动程序及管理工具包root@mdsales # tar xvf Solaris-5.02b-1a.tarx EmlxApps100a08.tar, 3530240 bytes, 6895 tape blocksx lpfc-5.02b-sparc.tar, 1359872 bytes, 2656 tape blocksx readme.first.txt, 1104 bytes, 3 tape blocksroot@mdsales # lsEmlxApps100a08.tar lpfc-5.02b-sparc.tar Solaris-5.02b-1a.tar readme.first.txtroot@mdsales # tar xvf lpfc-5.02b-sparc.tar //安装驱动x lpfc.1, 0 bytes, 0 tape blocksx lpfc.1/pkgmap, 1788 bytes, 4 tape blocksx lpfc.1/pkginfo, 284 bytes, 1 tape blocksx lpfc.1/install, 0 bytes, 0 tape blocksx lpfc.1/install/copyright, 493 bytes, 1 tape blocksx lpfc.1/install/postinstall, 10480 bytes, 21 tape blocksx lpfc.1/install/postremove, 2765 bytes, 6 tape blocksx lpfc.1/install/preremove, 1468 bytes, 3 tape blocksx lpfc.1/install/request, 2530 bytes, 5 tape blocksx lpfc.1/install/space, 23 bytes, 1 tape blocksx lpfc.1/reloc, 0 bytes, 0 tape blocksx lpfc.1/reloc/etc, 0 bytes, 0 tape blocksx lpfc.1/reloc/etc/system, 0 bytes, 0 tape blocksx lpfc.1/reloc/kernel, 0 bytes, 0 tape blocksx lpfc.1/reloc/kernel/drv, 0 bytes, 0 tape blocksx lpfc.1/reloc/kernel/drv/lpfc, 423476 bytes, 828 tape blocksx lpfc.1/reloc/kernel/drv/lpfc.conf, 10817 bytes, 22 tape blocksx lpfc.1/reloc/kernel/drv/sd.conf, 1185 bytes, 3 tape blocksx lpfc.1/reloc/kernel/drv/sparcv9, 0 bytes, 0 tape blocksx lpfc.1/reloc/kernel/drv/sparcv9/lpfc, 488600 bytes, 955 tape blocksx lpfc.1/reloc/usr, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/include, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/include/fcdiag.h, 19946 bytes, 39 tape blocksx lpfc.1/reloc/usr/lib, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/lib/libdfc.a, 32756 bytes, 64 tape blocksx lpfc.1/reloc/usr/lib/sparcv9, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/lib/sparcv9/libdfc.a, 40852 bytes, 80 tape blocksx lpfc.1/reloc/usr/sbin, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/sbin/lpfc, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/convert_path_lpfc, 2261 bytes, 5 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/dfc, 1095 bytes, 3 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/dfc32, 116440 bytes, 228 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/dfc64, 133144 bytes, 261 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/download_fmw_lpfc, 3495 bytes, 7 tape blocksx lpfc.1/reloc/usr/sbin/lpfc/resetqdepth, 1080 bytes, 3 tape blocksx lpfc.1/reloc/usr/share, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/share/man, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/share/man/man7d, 0 bytes, 0 tape blocksx lpfc.1/reloc/usr/share/man/man7d/lpfc.7d, 22065 bytes, 44 tape blocksx lpfc.1/reloc/usr/share/man/man7d/lpfn.7d, 14948 bytes, 30 tape blocks root@mdsales # pkgadd -d .The following packages are available:1 lpfc.1 Emulex LightPulse FC SCSI/IP Host Bus Adapter driver(sun4u) Release 5.02bSelect package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]:Processing package instance <lpfc.1> from </opt/sun/20051105>Emulex LightPulse FC SCSI/IP Host Bus Adapter driver(sun4u) Release 5.02blpfc (FCP) / lpfn (IP) combo driverCopyright (c) 2003, Emulex Corporation3535 Harbor Boulevard, Costa Mesa, CA 92626All rights reserved. This product and related documentation isprotected by copyright and distributed under licenses restrictingits use, copying, distribution and decompilation. No part of this product or related documentation may be reproduced in any form byany means without prior written authorization of Emulex Corporationand its licensors, if any.CAUTION: The lpfc driver will not work with any release of Solaris/SunOS earlier than 2.6/5.6. However, even for later releases, lpfc mayhave to be compiled specifically for that release of Solaris. This version of lpfc has been built under Solaris/SunOS 5.7 for sun4u.Rebuild manual pages database for section 7d [y,n,?] yUse IP networking over Fibre Channel [y,n,?] n //这里选择noUsing </> as the package base directory.## Processing package information.## Processing system information.11 package pathnames are already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.This package contains scripts which will be executed with super-user permission during the process of installing this package.Do you want to continue with the installation of <lpfc> [y,n,?] yInstalling Emulex LightPulse FC SCSI/IP Host Bus Adapter driver as <lpfc>## Installing part 1 of 1.[ verifying class <none> ]/usr/share/man/man7d/lpfc.7d/usr/share/man/man7d/lpfn.7d[ verifying class <manpage> ]/kernel/drv/lpfc/kernel/drv/lpfc.conf/kernel/drv/sparcv9/lpfc[ verifying class <driver> ]/usr/include/fcdiag.h/usr/lib/libdfc.a/usr/lib/sparcv9/libdfc.a/usr/sbin/lpfc/convert_path_lpfc/usr/sbin/lpfc/dfc/usr/sbin/lpfc/dfc32/usr/sbin/lpfc/dfc64/usr/sbin/lpfc/download_fmw_lpfc/usr/sbin/lpfc/resetqdepth[ verifying class <diagnostic> ]Modifying /etc/systemModifying /kernel/drv/sd.conf[ verifying class <sed> ]## Executing postinstall script.cat: cannot open //etc/hba.confUpdating /kernel/drv/lpfc.confUpdating /etc/system (moddir)catman -M //usr/share/man -w 7dThis may take a while ...Driver lpfc added to system.************IMPORTANT: You must reboot the system to start this driver.SCSI: If you are using lpfc to access disks, be sure tocheck the configuration file of your SCSI target driver(presumably sd.conf) to ensure that the driver willprobe for all of the targets/luns in your environment. NOTE: lpfc supports FCP and IP but wasn't configured for networking.ALL: Examine the contents of /kernel/drv/lpfc.conffor driver-specific variables and behavior.************Installation of <lpfc> was successful.*** IMPORTANT NOTICE ***This machine must now be rebooted in order to ensuresane operation. Executeshutdown -y -i6 -g0and wait for the "Console Login:" prompt.注：此时不要重启机器，等安装Application Kit后再重启。

Marvell网卡驱动安装说明

有效值：
- “启用优先级”
- “启用 VLAN”
- “启用优先级和 VLAN”
- “禁用优先级和 VLAN”
注意：仅启用驱动程序的功能以处理此类封包。
必须有协议或应用程序将此类封包传递给驱动程序。
电池模式连接检测 (Battery Mode Link Detection)
--------------------------------------------
默认值：“最快电池消耗速度”
有效值：
- “较慢电池消耗速度”：
连接速度切换至 10/100 Mbps 以减少功耗。
- “最快电池消耗速度”：
适配器以最高速度和最大功耗运行（无电量节省，
与系统由 AC 电源供电时相同）。
注意：对于每种适配器类型，此参数不可用。
所有驱动程序信息不显示（不推荐）。
速度和双工 (Speed & Duplex)
---------------------------
包含有关自动感应、双工功能和连接速度的信息。
默认值：“自动感应”
有效值：
- “自动感应” (Auto-Negotiation)
- “10Mbps 半双工”
- “10Mbps 全双工”
在“很大电量节省+(TM)”模式下，连接比在
“最大电量节省”模式下更快启动，但适配器
需要更多电能。
注意：对于每种适配器类型，此参数不可用。
电池消耗速度设置 (Battery Speed Settings)
---------------------------------------
设置电池为系统供电时适配器的连接速度。
- “CLPSS”（Check Local Ports and Segmentation

安装MOXA卡及NPORT驱动

MOXA的安装1、右键点击桌面上的“我的电脑”图标，然后点击菜单中的“属性”栏。

2、点击“硬件”窗口中的“设备管理器”。

3、双击“其他设备”中的“PCI串行口”。

4、点击“重新安装驱动程序”。

5、选择“否，暂时不”，然后点击“下一步”。

6、选择“从列表或指定位置安装（高级）”，点击“下一步”。

7、对于Windows XP系统，可以选择自动搜索安装和手动安装，这里选择手动安装，即“不要搜索，我要自己选择要安装的驱动程序”，点击“下一步”。

8、选择要安装的多串口卡，这里选择“MOXA S martio C104H/PCI Series（PCI Bus）”后，点击“从磁盘安装”。

9、在弹出的对话框中点击“浏览”，选择安装路径。

10、选择MOXA卡驱动所在的文件夹即“multi-bd”文件夹后，点击“打开”。

12、根据主机安装的操作系统，选择适合的文件夹，这里以Windows XP为例，选择“winxp”文件夹，点击“打开”。

14、选择“MXSPORT.INF”文件，点击“打开”。

15、点击“确定”。

16、点击“下一步”。

17、安装完成后，点击“完成”。

18、随后系统将自动搜索到串口，选择“从列表或指定位置安装（高级）”，点击“下一步”。

19、选择要安装的串口，这里选择“MOXA Port 0”后，点击“从磁盘安装”。

20、直接从下拉菜单中选择刚才串口卡的驱动安装路径，这里选择“F：\驱动\mullti-bd\software\winxp\industio”，点击“确定”。

21、点击“下一步”。

22、安装完成后，点击“完成”，即完成了串口0的安装。

23、重复步骤18～步骤21，完成其它三个串口的安装后，如果安装完全，设备管理器窗口应如下图显示。

NPORT驱动的安装1、双击NPORT驱动的安装文件“dssetup”。

2、点击“Next”。

3、可以选择默认，点击“Next”。

4、可以通过点击“Browse”选择安装路径，这里选择默认路径不更改，点击“Next”。

emulex驱动安装以及xen安装

emulex驱动安装以及xen安装Emulex网卡驱动安装在centos 6.0下安装src.rpm包，安装过程中，可能出现安装包的以来关系，直接安装相关的依赖包即可。

在redhat 6.0上，使用二进制包安装驱动，直接按照readme里面的方法进行驱动安装即可。

在centos 5.5上安装驱动，使用二进制包安装，但是不能够直接按照readme上面的方式进行安装。

首先解压二进制包。

例如centos 5.5对应的包为elx-be2net-dd-4.0.359.0-1-1.tar.gz，解压之后，进入解压的文件夹，继续解压即be2net_4.0.359.0-1.tar.gz，会出现对应不同系统的不同驱动版本。

进入相应的系统，例如CENTOS 5.5 应该进入系统RHEL5。

安装rpm包rpm –ivh *.rpm；若出现ksym问题，则使用命令rpm –ivh –nodeps *.rpm。

问题解决。

注释：--nodeps：不考慮相依屬性的關係，給他強制的安裝下去；Src.rpm包安装：首先需要确保rpm-build包已经安装，在安装src.rpm包时需要使用这个软件包。

安装方法如下：1、rpmbuild –rebuild *.src.rpm在较低版本使用时，会在/usr/src/redhat目录下出现BUILD RPMS SOURCES SPECS SRPMS这些目录。

而在高版本centos或者redhat中，会在当前目录下出现一个RPMS类似的文件夹，进入后与redhat里面的文件夹相同。

然后进入RPMS文件夹，直接安装RPM 包即可。

2、生成源码，再从源码包进行安装1. rpm -ivh filename.rpm #生成源码包2. cd /usr/src/redhat/SOURCES #在该目录找到生成的源码包3. cd srcdir #进入源码目录4. ./configure && make && make install #从源码安装。

esxi5.5 安装HBA卡驱动

首先进入vsphere client 登入主机，进入配置→安全配置文件（如图）
在服务属性里启动SSH （如图）
完成以后在用像wincap这种FTP软件把驱动文件上传入系统的tmp文件下
然后SSH远程登录，输入esxcli software vib install –v /tmp/***(驱动文件名)运行OK
退出维护模式，重启主机。

1、将ESXI的SSH打开，用VCL连接到ESXI,在配置---安全配置---SSH---打开ssh
2、将下载的文件用winscp（Secure CRT工具也可以）传到esxi的/tmp下，我下的这个版本是vib
3、安装,用ssh工具login到esxi的控制台，安装时注意要加全路径，否则报错
esxcli software vibinstall -v
/tmp/lpfc-10.2.340.18-1OEM.550.0.0.1331820.x86_64.vib
4、安装完成后重启即可
执行以下命令进入维护模式并允许安装第三方包
# esxcli system maintenanceMode set -e true -t 0
# esxcli software acceptance set --level=CommunitySupported。

设置服务器通过HBA卡启动

设置服务器通过HBA卡启动目前服务器主流使用的是Qlogic和Emulex的HBA卡，可以通过FC-SAN 方式连接后端存储设备，通过FC连接的存储空间可以在服务器自检完HBA卡后就可以直接被主板发现，因此通过FC方式映射的磁盘可以直接当成服务器本地的磁盘；而IP-SAN就不具备该功能，它必须等到系统启动后ISCSI服务起来才能发现映射过来的LUN。

基于此项特性，FC-SAN组网直接将服务器的操作系统等其他程序直接安装在后端存储的LUN中。

服务器不需要本地硬盘，只要有HBA卡就可以安装操作系统正常使用。

Qlogic和Emulex的HBA卡都支持SAN启动功能，但必须手动开启。

开启HBA卡的SAN启动功能将存储的LUN通过FC方式映射给HBA卡。

Qlogic HBA设置在服务器开机后根据屏幕提示使用“ctrl+Q”进入Qlogic HBA配置界面依照下图操作即可选择连接存储设备的适配器将标记的地方设置成“enabled”选择“Boot Port Name Lun”回车选择映射过来的LUN在BIOS中讲该盘设置成第一块硬盘Emulex HBA卡设置选择连接存储设备的适配器依照系统提示输入“01”选择磁盘的标识安装操作系统安装操作系统到LUN前必须加载HBA卡驱动，否则系统发现不了映射的LUN。

可以使用在安装系统前使用软驱加载HBA卡驱动。

目前很多服务器都有虚拟媒体功能，自带虚拟软盘和光驱功能。

我们可以使用这个功能给设备逻辑虚拟一个软盘，将制作的镜像问价上传进去，在安装操作系统的时候手动加载。

以emulex HBA卡为例具体的步骤为：使用UltraISO软件制作软驱镜像文件新建软盘镜像任务在官网/cn/Service_Training/Service_Support_Center/D ownload_Center1/Engineer_Zone/Server/T8000/DriverSoftware/ 可以下载到EMULEX HBA卡驱动在驱动包中使用对应的压缩包制作IMG文件点击“连接”BMC会在该设备上虚拟出一个软驱，在安装系统的时候手动加载软驱上的驱动就可以把操作系统安装在LUN上了，以windows操作系统为例：Windows2003安装时加载好驱动就可以选择LUN作为系统的安装盘。

Linux安装Emulex网卡驱动

elx-be2net-dd-4.6.148.0/perf_tune_benet.sh
elx-be2net-dd-4.6.148.0/perf_tune_benet.txt
[root@localhost linux]# ls
elx-be2net-dd-4.6.148.0 elx-be2net-dd-4.6.148.0-1-1.tar.gz
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 4194 MB, 4194304000 bytes
Installing be2net package, RHEL6_64/kmod-be2net-4.6.148.0-1.rh6u3.x86_64.rpm ...
Preparing... ########################################### [100%]
[root@localhost linux]# tar -zxvf elx-be2net-dd-4.6.148.0-1-1.tar.gz
elx-be2net-dd-4.6.148.0/
elx-be2net-dd-4.6.148.0/SRPMS/
elx-be2net-dd-4.6.148.0/SRPMS/be2net-4.6.148.0-1.src.rpm
Disk /dev/mapper/VolGroup-lv_root: 11.4 GB, 11408506880 bytes

Linux系统上安装FC HBA卡驱动

分类：LINUX一、老版本的FC HBA卡驱动安装（qlinstall命令直接安装）：1、首先下载Qlogic HBA卡的驱动（qlafc-linux-8.02.23-3-install.tgz），上传到tmp目录，解压缩，并进入解压缩目录[root@redhattmp]# cd qlafc-linux-8.02.23-3-install2、解压缩后生成的文件：[root@redhat qlafc-linux-8.02.23-3-install]# lsagents qla2xxx-v8.02.23-3.noarch.rpm ql-pci.ids scli-1.7.2-7.i386.rpm scli-1.7.2-7.ppc64.rpmLinuxTools qlinstall README.qlinstall.txt scli-1.7.2-7.ia64.rpmset_driver_param3、执行安装命令：[root@redhat qlafc-linux-8.02.23-3-install]# ./qlinstall#*********************************************************## SANsurfer Driver Installer for Linux ## Installer Version: 1.01.00pre22 ##*********************************************************#Kernel version: 2.6.18-164.el5Distribution: Red Hat Enterprise Linux Server release 5.4 (Tikanga)Found following QLogic Adapter in the system1. QLE2460Installation will begin for following driver1. qla2xxx version: v8.02.23Warning: Found an installed driver. Version: v8.01.06Overriding the already installed version....Unloading any loaded driversUninstall of rpm version v8.01.06-1 beginning...Restoring original QLogic drivers....Removing installation changes from /etc/modprobe.conf....Building module dependency....depmod...QLA2XXX -- Rebuilding ramdisk image...Removing QLogic HBA API library...Done.Installing scli....Preparing packages for installation...scli-1.7.2-7Installing Driver...Preparing... ##################################################qla2xxx ##################################################QLA2XXX -- Building the qla2xxx driver, please wait...Installing intermodule.ko in /lib/modules/2.6.18-164.el5/kernel/kernel/QLA2XXX -- Installing the qla2xxx modules to/lib/modules/2.6.18-164.el5/kernel/drivers/scsi/qla2xxx/...Setting up QLogic HBA API library...Please make sure the /usr/lib/libqlsdm.so file is not in use.Installing ia32 api binary.Library 4.00 build25 already installed at /usr/lib/libqlsdm.so.Done.Loading module qla2xxx_conf version: v8.02.23....Loaded module qla2xxx_confLoading module qla2xxx version: v8.02.23....Loaded module qla2xxxBuilding default persistent binding using SCLIWarning: PrefOpenPreferenceFile: Failed to open preference file (/etc/agent.properties). Saved copy of /etc/modprobe.conf as/usr/src/qlogic/v8.02.23-3/backup/modprobe.conf-2.6.18-164.el5-082110-015423.bak Saved copy of /boot/initrd-2.6.18-164.el5.img as/boot/initrd-2.6.18-164.el5_QLA2XXX -- Rebuilding ramdisk image...Ramdisk created.Reloading the QLogic FC HBA drivers....Unloaded module qla2xxxLoading module qla2xxx_conf version: v8.02.23....Loaded module qla2xxx_confLoading module qla2xxx version: v8.02.23....Loaded module qla2xxxTarget Information on all HBAs:==============================Warning: PrefOpenPreferenceFile: Failed to open preference file (/etc/agent.properties). --------------------------------------------------------------------------------HBA Instance 0: QLE2460 Port 1 WWPN 21-00-00-1B-32-1E-75-A6 PortID 00-00-00--------------------------------------------------------------------------------No device connected to selected HBA (Instance 0)!Installing the qlinstall-autoload script in /etc/init.d/#*********************************************************## INSTALLATION SUCCESSFUL!! ## SANsurfer Driver installation for Linux completed ##*********************************************************#4、安装成功如果在/proc/scsi/目录下出现qla2xxx/目录说明安装已经成功，设备正常运行[root@redhat qlafc-linux-8.02.23-3-install]# cat /proc/scsi/qla2xxx/* |grep adapter-port scsi-qla0-adapter-port=2100001b321e75a6;[root@redhat qlafc-linux-8.02.23-3-install]#5、查看驱动版本：$ rpm -qa |grepqlaqla2xxx-v8.02.23-36、qlinstall命令其他参数qlinstall -h 查看帮助qlinstall -i 安装qlinstall -up 升级qlinstall -u 卸载二、新版本驱动安装（源码，src，需要手工生产ko文件）1、第一种方法看自带的readme文件2、第二种方法先安装老版本如8.02.23然后，解压新版本jason.wy@db067044.cm4:~ $ tar -xzf qla2xxx-src-8.03.01.06.05.06-k.tar.gzjason.wy@db067044.cm4:~ $ cd qla2xxx-src-8.03.01.06.05.06-kjason.wy@db067044.cm4:~/qla2xxx-src-8.03.01.06.05.06-k$使用make命令指定-C参数，在当前目录生成.ko文件jason.wy@db067044.cm4:~/qla2xxx-src-8.03.01.06.05.06-k$ make -C /usr/src/kernels/2.6.18-164.el5-x86_64 M=`pwd` modulesmake: Entering directory `/usr/src/kernels/2.6.18-164.el5-x86_64'CC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_os.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_init.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_mbx.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_iocb.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_isr.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_gs.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_dbg.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_sup.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_attr.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_mid.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla_nlnk.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2100_fw.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2200_fw.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2300_fw.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2322_fw.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2400_fw.oCC [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/ql2500_fw.oLD [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla2xxx.oBuilding modules, stage 2.MODPOSTCC /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla2xxx.mod.oLD [M] /home/jason.wy/qla2xxx-src-8.03.01.06.05.06-k/qla2xxx.komake: Leaving directory `/usr/src/kernels/2.6.18-164.el5-x86_64'将新生产的qla2xxx.ko文件，替换老版本的qla2xxx.ko文件以下内容为补充：6、查看HBA卡模块的信息jason.wy@db067043.cm4:~/qla2xxx-src-8.03.01.06.05.06-k$ /sbin/modinfo qla2xxx|head filename: /lib/modules/2.6.18-164.el5/kernel/drivers/scsi/qla2xxx/qla2xxx.ko version: 8.02.23license: GPLdescription: QLogicFibre Channel HBA Driverauthor: QLogic Corporationsrcversion: BBC3E01BB8B551306290FC7alias: pci:v00001077d00002532sv*sd*bc*sc*i*alias: pci:v00001077d00005432sv*sd*bc*sc*i*alias: pci:v00001077d00005422sv*sd*bc*sc*i*alias: pci:v00001077d00008432sv*sd*bc*sc*i*。

使用命令加U盘给esxi安装网卡驱动

使用命令加U盘给esxi安装网卡驱动使用命令加U盘给esxi安装网卡驱动问题描述：前几天公司来了一批机器DELL R720（服务器器配置如下：至强E5-5602,128G，1.06T，BCM5720网卡坑爹的网卡下面就阐述如何坑爹），安装esxi5.1，从官网上下载VMware-VMvisor-Installer-201210001-838463.x86_64 ISO安装，直接提示无法驱动网络。

这是最新版本的Esxi了，都无法驱动我滴个神呀好吧，我败了，我要把你整好。

------------------- 首先：在dcui界面下面f2，然后输入root用户名和密码后进入到一个bios like界面，找到troubleshooting选项，然后有一个ESXi Shell 选项，激活它之后alt + f1，然后输入root用户名和密码之后就是命令行了---------------------下面说说完成的步骤：1. 使用ESXi-Customizer-v2.7.1来将从vmware官网上下载的BCM5720的驱动打进ISO中，可以参看我另外的文档有如何操作；2. 将封装好的ISO放到光驱里安装，非常顺利。

3. 因为是5.1的838463的版本，vmware官网上有914609的版本的zip包，准备升级到最新版本。

使用esxcli命令升级然后重启。

4. 问题来了，重启后网卡驱动丢失，我去，我快疯了，不是吧，刚刚封装ISO就是因为网卡驱动，升级后居然也丢网卡驱动。

因为没有网卡了我只能用U盘将网卡的驱动包传到esxi主机本地存储上。

自己不明白一统的百度，谷歌。

在群里各种问。

终于在猫猫的指导下搞定了。

5. 以下内容非常重要！：1. 从键盘按住alt+F1进入编辑模式，root加密码进入命令行模式2. 输入 vim-cmd hostsvc/maintenance_mode_enter(使ESXI进入维护模式，这点非常重要)3. 输入 /etc/init.d/usbarbitrator stop (将USB仲裁关闭)4. 插入你的U盘，输入 esxcli storage core device list | grep –i usb (使用esxcli刷新USB口上的设备，这时会出现USB设备名称，将名称记住！)5. 输入 /vmfs/volumes/NO NAME(后面就会出现U盘的名称了)6. 输入 cd 进入U盘里，cp将U盘里的vib包拷贝到 /tmp下7. 输入 cd /tmp (进入tmp目录下查看你拷贝的文件是否存在)8. 在/tmp目录下输入chmod 777 XXXXXX.vib(修改你的vib包的权限，将vib包考到tmp是因为这里有执行的权限)9. 输入 esxcli software vib install –v /tmp/XXXXXXX.vib (通过esxcli来安装驱动包)10. 看到成功字样，说明你已经安装成功。

Emulex HBA Manager 应用程序 Linux 版 Release Notes说明书

Release Notes Emulex® HBA Manager Applicationfor LinuxRelease 12.8.614.12-1Purpose and Contact InformationThese release notes describe the supported operating systems, new features, resolved issues, known issues, and technical tips associated with this release of the Emulex® HBA Manager application for Linux.For the latest product source files and documentation, and for supported driver versions, go to . If you have questions or require additional information, contact an authorized Broadcom® Technical Support representative at*****************************.NOTE:The Emulex OneCommand™ Manager application has been renamed as the Emulex HBA Manager application.However, the following items within the application continue to use OneCommand:●Kit names●Script names●Directory names●Command namesNew FeaturesNo new features were introduced in this release.NOTE:This release supports the CentOS 7.7, 7.8, 7.9, 8.3, 8.4, and 8.5 operating systems. It does not support the CentOS Stream 8 operating system.Resolved Issues1.In the Emulex HBA Manager CLI, setting Strictly Local Management Mode now reenables elxhbamgrd.2.The Emulex HBA Manager GUI now resets autostart back to false when changing the management mode to StrictlyLocal Management with Daemons Disabled.3.On LPe35004 HBAs, the correct number of bytes read and written are now reported by Emulex HBA Manager portstatistics.Known Issues1.For an NVMe port, do not use the Emulex HBA Manager CLI utility to discover the host remotely. Otherwise, the porttype is displayed as FC instead of FC+NVMe.WorkaroundUse local management instead of remote management on NVMe ports.2.The online help in the release 12.8.xxx.xx Emulex HBA Manager GUI is not up to date. Refer to the Emulex HBAManager Application User Guide release 12.8 for up-to-date information about the following topics:–The correct illustration for adding a host–The instructions for installing the Emulex HBA Manager application without invoking a daemon–The description for the Function Summary area of the Host Information tab–Instructions for performing an immediate authentication–Procedures for managing firmware logging3.Revision A of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) does not support D_Port (also calledClearLink®) for Brocade® switches and MDS diagnostics for Cisco switches.4.Neither Revision A nor Revision B of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) andAFCT-57G5MZ-ELX (32GFC longwave optic transceiver) supports D_Port for Brocade switches.5.When the Emulex HBA Manager application is run on a Windows or Linux host, batch parameter update errors are notadded to the batch log.6.To perform a firmware dump on an LPe35000-series adapter on the Ubuntu 18.04 inbox driver (except on the Ubuntu18.04.3 HWE release), you cannot use the Emulex HBA Manager application. To perform a firmware dump on this driver,see Technical Tips, Item1, in these release notes.7.On LPe35000-series adapters, loopback tests are not functional on the Ubuntu 18.04 operating system (except on theUbuntu 18.04.3 HWE release).8.On LPe35000-series adapters, a host reboot is required after a firmware update on the Ubuntu 18.04 operating system(except on the Ubuntu 18.04.3 HWE release).9.The Emulex HBA Manager application GUI cannot be used to set a hash priority to a single value on an HBA port.WorkaroundUse hbacmd to set a hash priority to a single value on the HBA port. Ensure that the same hash priority value is set on the switch or authentication will fail.10.Boot from SAN is not supported if FC-SP-2 authentication (DH-CHAP) is enabled.11.Updating the NVMe BFS installation from RHEL 8.1 to a later RHEL 8.x release requires the rhel8u1_upgrade.shscript, which ensures that the NVMe BFS setup is maintained through the update process.The rhel8u1_upgrade.sh script is packaged in the nvmefc-dm--1.rhel8.tar.gz kit inside theelx-nvmefc-dm-<build>-n.tar.gz preinstallation kit. For more information about the preinstallation kit, refer to the Emulex Boot for the Fibre Channel and NVMe over FC Protocols User Guide.Technical Tips1.To perform a firmware dump on the Ubuntu 18.04 inbox driver (except on the Ubuntu 18.04.3 HWE release), perform thefollowing steps:a.Ensure that the latest Emulex HBA Manager core application kit for Linux is installed on the host.b.Download the LPe35000-series HBA FW Dump Tool from the Broadcom website at .c.Type the following commands to extract and install the tool:tar xzf elx-lpe-35000-fw-dump-tool-<version>-ds-1.tar.gzcd elx-lpe-35000-fw-dump-tool-<version>-ds-1/rpm -ivh elx-lpe-35000-fw-dump-tool-<version>.<platform>.rpmA window similar to the following is displayed.d.Type 1 and press Enter to select the port for which you want to perform the firmware dump.A window similar to the following is displayed.NOTE: A warning message appears if initiating a firmware dump on a specific port will also affect another port on the same adapter ASIC.e.Type the number of the port for which you want to perform the firmware dump, and press Enter.A window similar to the following is displayed.f.When the desired port is identified as the current port, type 2 and press Enter to initiate the firmware dump on thecurrent port.If the firmware dump is successful, the firmware dump tool closes automatically.g.Restart the elxhbamgrd service by typing the following command:service elxhbamgrd restartThis command allows such applications as the Emulex HBA Manager application to be refreshed.By default, the firmware dump file is available on the host in the /var/opt/Emulex/ocmanager/Dump/ directory after the elxhbamgrd service has been restarted.2.If you change the volatile World Wide Name (WWN) on an LPe16000-series adapter, a reboot is required.3.The Emulex HBA Manager application does not display the OS Device Name for LUNs attached to vPorts.In the LUN Information tab, under Mapping Information, the OS Device Name field displays N/A instead of the device name. All other information on the LUN Information tab is displayed correctly.4.When you install the Emulex HBA Manager application on a guest operating system, answers to the installer promptsare ignored.When you install the Emulex HBA Manager application on a guest operating system, you are presented withmanagement mode options (local only, full-management, read-only, and so on). Answers to these questions are ignored;all installations on guest operating systems are set to local only, read-only, and remote management.5. A port WWN setting configured at boot time using the BIOS tools might conflict with port WWN settings configured usingthe Emulex HBA Manager application.Some new systems allow the WWN for a port to be changed using the BIOS tools. Conflicts might occur if the WWN for the same port is permanently changed using the Emulex HBA Manager Change WWN feature. In such cases, the attempt to change the port WWN using the Change WWN feature might fail, or the port WWN configured by the BIOS tools will overwrite the setting configured by the Change WWN feature.6.Creating Secure Management users and groups after the Emulex HBA Manager application is installed in SecureManagement mode causes the GUI to fail.If the Secure Management users and groups are created after the Emulex HBA Manager application has been installed in Secure Management mode, when you attempt to start the Emulex HBA Manager application GUI as a member of a group, the application does not run. The operating system displays the following error message:-Bash: /usr/sbin/OneCommand Manager/OneCommand Manager: Permission deniedWorkaroundPerform one of the following actions:–Create the users and groups before you install the Emulex HBA Manager application in Secure Management mode.–Uninstall and reinstall the Emulex HBA Manager application.7.The elxhbamgrd daemon can take up to 30 seconds to stop.The behavior of the elxhbamgrd daemon is linked with the maximum timeout that the Linux kernel associates with the block BSG driver interface commands and with the Emulex HBA Manager application register for events function.8.Newly added LUNs on a storage array might not appear on the host machine Linux operating system or the Emulex HBAManager application.WorkaroundPerform one of the following actions:–Run the following script from the command shell:/usr/sbin/lpfc/lun_scan all–Reboot the host machine after the LUN has been added at the target array.9. A permanent driver parameter change fails if the system is rebooted too soon.When you make permanent driver parameter changes using the Emulex HBA Manager application, the application automatically makes the required entry in the /etc/modprobe.d/elx-lpfc.conf or equivalent file. Because the driver loads so early in the Linux machine boot sequence, the new contents of the/etc/modprobe.d/elx-lpfc.conf file must be reinserted into the Linux initial ramdisk file (using an operating system utility) for the driver to pick up the new driver parameter value on the next boot. Failure to generate a new initial ramdisk file prevents the driver from retrieving the new driver parameter value on subsequent driver loads (machine boots). The Emulex HBA Manager application automatically re-creates the initial ramdisk; however, it can take as long as 45 to 60 seconds after the driver parameter is changed for a complete initial ramdisk rebuild. If you reboot the machine immediately after the driver parameter change is made, the automatic re-creation of the initial ramdisk file by the Emulex HBA Manager application might fail to be completed. In these cases, this failure causes the driver to not obtain the new driver parameter value upon subsequent reboots.WorkaroundWait a minimum of 45 to 60 seconds after making the driver parameter change before rebooting the machine.10.A set link speed issue occurs after an SFP hot swap.LPe16000-series adapters do not support hot-swapping an SFP if the replacement SFP is not the same model as the original SFP. Two consequences occur in the Emulex HBA Manager application:–The Port Attributes tab in the Emulex HBA Manager application or the Emulex HBA Manager PortAttributes CLI command might display incorrect data for the Supported Link Speeds attribute. This issue is cosmetic.–Boot from SAN Management might be unable to set the Boot Code Link Speed parameter to 16 Gb/s.WorkaroundAfter changing the SFP, either reset the LPe16000 port or reboot the server.11.A dump command on a boot from SAN adapter might cause a system panic.When the Emulex HBA Manager application performs a dump of an adapter that is booting from a SAN and has no failover support, the operating system crashes when the adapter is taken offline to perform the boot and write the dump file to the host file system. The file system is unavailable because the adapter was taken offline.WorkaroundBefore performing a dump of an adapter, ensure that the desired adapter is not a boot from SAN adapter. Alternatively, provide failover support so that when the adapter is taken offline to perform the dump, the boot from SAN connection is maintained by the failover.12.When using Secure Management, if you belong to the ocmadmin group, you might be unable to change settings forremote adapters.WorkaroundSwitch to Full Management when changing the settings on a remote adapter.13.If the CLI (hbacmd) is used to perform a firmware download to a local adapter, and the Emulex HBA Manager applicationGUI is running while that firmware download is occurring, the Emulex HBA Manager application GUI might experience problems displaying information on various display tabs after the download completes. The value displayed for most of the fields on the affected tabs or dialogs is N/A.WorkaroundPerform one of the following actions:–Perform the firmware download using the Emulex HBA Manager application GUI instead of hbacmd.–When a firmware download has been performed by using hbacmd, if N/A is shown for most of the Emulex HBA Manager application GUI display fields, exit the GUI and then restart it. The fields are displayed correctly after doing this action.–Ensure that the Emulex HBA Manager application GUI is stopped or is not running prior to performing a firmware download using hbacmd.14.On SLES 12 SP4, initiating a firmware dump might result in an error message similar to the following:error: Invalid argument [arc/elx_lpe_35000_pci_device.app:TriggerFWDumps:510]Consider adding “iomem-relaxed” to grub cfg kernel commandline.[0x1000000090fa9483a2], [host8] [0000:01:00.0] Failed to trigger firmware dump.If this message appears, perform the following steps:a.Add the following kernel command line to the host grub configuration file:iomem=relaxedb.Reboot the host.c.Repeat the process to initiate a firmware dump.15.On Linux passthrough-only systems, the hbacmd listhba command might be slow to respond when adapters areattached to VMs.WorkaroundNone.16.Enabling and disabling a Fabric Assigned Port World Wide Name (FA-PWWN) might cause an adapter port’s WWPN tochange. The Emulex HBA Manager application discovery-tree might not display the port’s newly assigned WWPN.WorkaroundStop and restart the Emulex HBA Manager application services and daemons when prompted by the Emulex HBA Manager application.ing the Brocade Portdporttest command with the stop option causes the HBA to stop responding when runningD_Port from the switch. Disabling a port while running D_Port tests from the switch can cause the switch port to get stuck in D_Port mode.WorkaroundDo not stop D_Port tests while they are running from the switch. Do not disable a port while D_Port tests are running from the switch.If the HBA stops responding, remove the D_Port configuration from the switch port using the following commands. Refer to the Brocade switch documentation for more information.portdisable <portnumber>portcfgdport --disable <portnumber>portenable <portnumber>If the switch port is stuck in D_Port mode, use the portdporttest --exit command to clear the configuration.Copyright © 2022 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, go to . All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others.。

服务器HBA卡常见问题

服务器HBA卡常见问题服务器HBA卡常见问题⼀、概述：FC HBA，也即Fibre Channel Host Bus Adapter，光纤通道主机适配器，简称光纤适配器。

在FC⽹络环境中，主机需要和FC⽹络、FC存储设备（SAN磁盘阵列）连接时需要使⽤⼀种接⼝卡，就如同连接以太⽹需要以太⽹卡⼀样，这种接⼝卡就叫做FC HBA，简称FC HBA卡。

我司⽬前服务器上的的HBA卡主要有两种，属于不同⼚家：Emulex LPe31002驱动下载位置：Qlogic Qle2692：驱动下载位置：⼆、常⽤命令：（1）查看是否识别到硬件（两种卡是⼀致的）：lspci |grep -i fibre （注意：如果没有lspci命令，需要装相应的包lspciutils）（2）查看驱动版本：两个⼚家的驱动名称不⼀样：Qlogic：qla2xxxEmulex：lpfc刚升级驱动还没有加载时，可以直接看：modinfo lpfc | moremodinfo qla2xxx|more已经加载上去之后可以：（需要先查看在哪个host上）cat /sys/class/scsi_host/host18/lpfc_drvr_version （lpfc） Emulex LightPulse Fibre Channel SCSI driver 11.1.0.2cat /sys/class/scsi_host/host16/driver_version （qla2xxx） 10.00.00.06.07.6-k（3）查看固件版本：可以查看系统信息：cat /sys/class/scsi_host/host15/fwrev（lpfc） 12.6.182.8, sli-4:2:ccat /sys/class/scsi_host/host15/fw_version（qla2xxx） 8.08.03 (d0d5)emulex也可以⽤特定的⼯具查看：（需要先安装emulex固件,见下⽂）/usr/sbin/linlpcfg/elxflash /q（4）查看通道host(这⾥的通道相当于⽹卡的⽹⼝，⼀张⽹卡有两个⽹⼝，⽽⼀张HBA卡也有两个host)注意：实践发现，升级驱动之后，host会发⽣改变。

Emulex HBA型号7101684安全指南说明书

Sun Storage 16 Gb FC PCIe 通用 HBA (Emulex) 安全性
本文档介绍了使用 Sun Storage 16 Gb FC PCIe 通用 HBA (Emulex) 时要注意的一般安全原则和准则。
本文档未包含以下安全信息：
■ 有关 BIOS、Open Boot Prom (OBP) 和虚拟机管理程序的特定平台固件安全性 ■ 有关操作系统安全性的问题 ■ 硬件系统的物理安全性 ■ 外部联网基础结构的网络安全性 ■ 可信平台模块信息
可从以下网址获得有关该产品及相关产品的文档和资源：/cd/ E24649_01/index.html。
反馈
可以通过以下网址提供有关本文档的反馈：/goto/docfeedback。
使用本文档
7
8
Sun Storage 16 Gb 光纤通道 PCIe 通用主机总线适配器 (Emulex) 安全指南 • 2015 年 7 月
Sun Storage 16 Gb 光纤通道 PCIe 通用主机总线适配器 (Emulex) 安全指南
适用于 HBA 型号 7101684
文件号码 E41468-02 2015 年 7 月
文件号码 E41468-02
版权所有 © 2014, 2015, Oracle 和/或其附属公司。保留所有权利。
本软件或硬件是为了在各种信息管理应用领域内的一般使用而开发的。它不应被应用于任何存在危险或潜在危险的应用领域，也不是为此而开发的，其中包括可能会产生人身伤害的应用领域。如果在危险应用领域内使用本软件或硬件，贵方应负责采取所有适当的防范措施，包括备份、冗余和其它确保安全使用本软件或硬件的措施。对于因在危险应用领域内使用本软件或硬件所造成的一切损失或损害，Oracle Corporation 及其附属公司概不负责。

Emulex 8Gb FC单口和双口HBA产品指南（撤回产品）说明书

Emulex 8Gb FC Single-port and Dual-port HBAsProduct Guide (withdrawn product)Streamlined installation and management, plus unrivaled scalability and industry-leading virtualization support make the Emulex 8Gb Fibre Channel host bus adapters ideal solutions for enterprise and mixed-OS environments. With powerful management tools, they deliver maximum performance in the widest range of applications and environments.Figure 1 shows the single-port and dual-port adapters.Figure 1. Emulex 8Gb Fibre Channel single-port and dual-port HBAsDid you know?The configuration of the Emulex 8 Gb HBAs is fully integrated in the UEFI interface which results in an easy to use and intuitive way to set up the adapter. The HBAs provide the ability to build high-performance, highly available SANs and are easy to set up and integrate into existing SAN configurations. Emulex 8Gb HBAs use passive cooling devices to deliver enhanced thermal protection for highest reliability and maximum server availability.Click here to check for updatesServer support - ThinkSystemCountry availability: The ThinkSystem part numbers are only available in the following countries: China, Japan, and markets in the Asia Pacific region.The following tables list the ThinkSystem servers that are compatible.Table 2. Server support - ThinkSystem (Part 1 of 3)PartNumber Description Edge1S IntelV2AMD V3Intel V34XC7A08220ThinkSystem Emulex LPe12000-M8-L PCIe 8Gb 1-Port SFP+ FibreChannel AdapterN N N N N N N N N N N N N N N N N N N4XC7A08221ThinkSystem Emulex LPe12002-M8-L PCIe 8Gb 2-Port SFP+ FibreChannel AdapterN N N N N N N N N N N N N N N N N N N Table 3. Server support - ThinkSystem (Part 2 of 3)PartNumber Description Dense V32S Intel V2AMD V1Dense V24SV28S4XC7A08220ThinkSystem EmulexLPe12000-M8-L PCIe 8Gb 1-Port SFP+ Fibre ChannelAdapterN N N N N N N N N N N N N N N N N N N N4XC7A08221ThinkSystem EmulexLPe12002-M8-L PCIe 8Gb 2-Port SFP+ Fibre ChannelAdapter N N N N N N N N N N N N N N N N N N N N SE35(7Z46/7D1X)SE35V2(7DA9)SE36V2(7DAM)SE45(7D8T)SE455V3(7DBY)ST5V2(7D8K/7D8J)ST25V2(7D8G/7D8F)SR25V2(7D7R/7D7Q)SR635V3(7D9H/7D9G)SR655V3(7D9F/7D9E)SR645V3(7D9D/7D9C)SR665V3(7D9B/7D9A)SR675V3(7D9Q/7D9R)ST65V3(7D7B/7D7A)SR63V3(7D72/7D73)SR65V3(7D75/7D76)SR85V3(7D97/7D96)SR86V3(7D94/7D93)SR95V3(7DC5/7DC4) SD665V3(7D9P)SD665-NV3(7DAZ)SD65V3(7D7M)SD65-IV3(7D7L)ST65V2(7Z75/7Z74)SR63V2(7Z7/7Z71)SR65V2(7Z72/7Z73)SR67V2(7Z22/7Z23)SR635(7Y98/7Y99)SR655(7Y/7Z1)SR655ClientOSSR645(7D2Y/7D2X)SR665(7D2W/7D2V)SD63V2(7D1K)SD65V2(7D1M)SD65-NV2(7D1N)SN55V2(7Z69)SR85V2(7D31/7D32)SR86V2(7Z59/7Z6)SR95(7X11/7X12)Table 5. Operating system support for Emulex 8Gb FC Single-port HBA for Lenovo System x, 42D0485Operating systemsMicrosoft Windows Server 2008 R2Y Y Y N N N Y Y Y Y Y Y Y Microsoft Windows Server 2012Y Y Y Y Y Y Y Y Y Y Y Y Y Microsoft Windows Server 2012 R2Y Y Y Y Y Y Y Y Y Y Y N Y Microsoft Windows Server 2016N Y Y Y Y Y Y Y Y Y Y Y Y Microsoft Windows Server 2019N N N Y Y N N N Y N Y N N Microsoft Windows Server version 1709N N Y Y Y Y Y Y Y Y Y N N Microsoft Windows Server version 1803N N N N N N N N Y N Y N N Red Hat Enterprise Linux 5 Server Edition N N N N N N N N N N N N Y Red Hat Enterprise Linux 5 Server x64 Edition N N N N N N N N N N N N Y Red Hat Enterprise Linux 6 Server Edition N N N N N N N N N N N N Y Red Hat Enterprise Linux 6 Server x64 Edition Y Y N N Y Y Y Y Y Y Y N Y Red Hat Enterprise Linux 7Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.0N N N Y N N N N N N N N N SUSE Linux Enterprise Server 11 for AMD64/EM64T Y Y Y Y Y Y Y Y Y Y Y Y N SUSE Linux Enterprise Server 11 for x86N N N N N N N N N N N Y N SUSE Linux Enterprise Server 11 with Xen for AMD64/EM64TN Y Y Y N Y Y Y Y Y Y N N SUSE Linux Enterprise Server 12N Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 12 with Xen N N N N N Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 15N N Y Y Y Y N N Y N Y N N SUSE Linux Enterprise Server 15 with Xen N N Y Y Y Y N N Y N Y N N VMware vSphere 5.1 (ESXi)Y Y N N N Y Y Y N Y N Y Y VMware vSphere Hypervisor (ESXi) 5.5Y Y N N Y N Y Y Y Y Y N Y VMware vSphere Hypervisor (ESXi) 6.0Y Y Y Y Y Y Y Y Y Y Y N Y VMware vSphere Hypervisor (ESXi) 6.5Y N Y Y YYYYYYYY YVMware vSphere Hypervisor (ESXi) 6.7NNNYY Y Y N Y N Y N N[in box driver support only]Detail information please refer to Support Tip HT506708x 3850/3950 X 6 (3837)x 3850/3950 X 6 (6241, E 7 v 2)x 3850/3950 X 6 (6241, E 7 v 3)x 3850/3950 X 6 (6241, E 7 v 4)x 3250 M 6 (3633)n x 360 M 5 (5465)x 3500 M 5 (5464)x 3550 M 5 (5463)x 3550 M 5 (8869)x 3650 M 5 (5462)x 3650 M 5 (8871)x 3100 M 5 (5457)x 3250 M 5 (5458)111222212Table 6. Operating system support for ThinkSystem Emulex LPe12002-M8-L PCIe 8Gb 2-Port SFP+ Fibre Channel Adapter, 4XC7A08221Operating systemsMicrosoft Windows Server 2012 R2N N N N N N N Y Y Y Y Y Y Y Microsoft Windows Server 2016Y Y Y Y Y Y Y Y Y Y Y Y Y Y Microsoft Windows Server 2019Y Y Y Y Y Y Y Y Y Y Y Y Y Y Microsoft Windows Server version 1709N N N N N N N N N Y Y Y Y N Microsoft Windows Server version 1803N N N N N N N Y N N N N Y Y Red Hat Enterprise Linux 6.10N N N N N N N Y Y Y Y Y Y Y Red Hat Enterprise Linux 6.9N N N N N N N Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.3N N N N N N N Y Y Y N N Y Y Red Hat Enterprise Linux 7.4N N N N N N N Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.5N N N N N N N Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.6Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.7Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.8Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 7.9Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.0Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.1Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.2Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.3Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.4Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.5Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.6Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 8.7Y Y Y Y Y Y Y Y Y Y Y Y Y Y Red Hat Enterprise Linux 9.0Y Y Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 11 SP4N N N N N N N Y Y N Y Y Y Y SUSE Linux Enterprise Server 11 SP4 with Xen N N N N N N N Y Y N Y Y Y Y SUSE Linux Enterprise Server 12 SP2N N N N N N N Y Y N N N Y Y SUSE Linux Enterprise Server 12 SP2 with Xen N N N N N N N Y Y N N N Y Y SUSE Linux Enterprise Server 12 SP3N N N N N N N Y Y Y Y Y Y Y SUSE Linux Enterprise Server 12 SP4Y Y Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 12 SP4 with Xen Y Y Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 12 SP5Y Y Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 12 SP5 with Xen Y Y Y Y Y Y Y Y Y Y Y Y Y Y SUSE Linux Enterprise Server 15Y Y Y Y Y Y Y YYYYYYY S D 530 (X e o n G e n 2)S R 530 (X e o n G e n 2)S R 550 (X e o n G e n 2)S R 570 (X e o n G e n 2)S R 590 (X e o n G e n 2)S R 630 (X e o n G e n 2)S R 650 (X e o n G e n 2)S D 530 (X e o n G e n 1)S R 530 (X e o n G e n 1)S R 550 (X e o n G e n 1)S R 570 (X e o n G e n 1)S R 590 (X e o n G e n 1)S R 630 (X e o n G e n 1)S R 650 (X e o n G e n 1)TrademarksLenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web athttps:///us/en/legal/copytrade/.The following terms are trademarks of Lenovo in the United States, other countries, or both:Lenovo®ServerProven®System x®ThinkSystem®The following terms are trademarks of other companies:Intel® and Xeon® are trademarks of Intel Corporation or its subsidiaries.Linux® is the trademark of Linus Torvalds in the U.S. and other countries.Microsoft®, Windows Server®, and Windows® are trademarks of Microsoft Corporation in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others.。

浪潮服务器网卡驱动安装

服务器安装redhat 5.2系统无法识别网卡的情况下进入linux命令终端界面，使用命令[root@wapdbrac1 ~]# kudzu --probe --class=network界面上就会显示网卡的型号以及机器上都有几个网卡第一步：在网上下载这个网卡型号的linux版本驱动程序第二步：使用命令查看kernel包是否都装全了，具体如下：[root@localhost kernel]# rpm -qa | grep kernel如果装全了，会显示如下几个包：kernel-xen-devel-2.6.18-8.el5kernel-devel-2.6.18-8.el5kernel-2.6.18-8.el5kernel-xen-2.6.18-8.el5kernel-headers-2.6.18-8.el5如果没有装全，就在redhat enterprise Linux 5.2 ISO光盘的Server文件目录下可以找到对应的包，拷贝到某一具体目录下，进入目录后，用如下命令就可以进行安装：[root@localhost kernel]# rpm -ivh kernel-**.rpm注意：如果不装全这些包，在网卡编译时就会报错说找不到src目录文件。

第三步：把下载的网卡驱动文件拷贝到某一目录下，我放在了tmp目录下，解压：tar zcvf igb-3.2.9.tar（根据自己下的什么格式的压缩包来解压）第四步：进入解压到驱动程序目录，命令：cd igb-3.2.9进入src目录，命令：cd src执行清除网卡驱动命令：make clean执行安装网卡模块命令：make接着安装：make install接着挂接：depmod -a挂驱动：insmod ./ igb.ko查看是否成功：lsmod | grep igb，如显示有信息则成功注意：在上面一系列命令操作过程中，如无error，则就OK了，之前我在装的过程中，在make install这一步老报错，说找不到src目录，后来才知道是上面的kernel包少装的缘故。

HBA卡(EMULEX)详解

HBA卡(EMULEX)详解HBA卡全称主机总线适配器(Host Bus Adapter,HBA)是一个在服务器和存储装置间提供输入/输出(I/O)处理和物理连接的电路板和/或集成电路适配器。

HBA卡主要用于连接计算机内部总线和存储网络的设备。

HBA是服务器内部的I/O 通道与存储系统的I/O通道之间的物理连接。

HBA卡的作用就是实现内部通道协议PCI或Sbus和光纤通道协议之间的转换。

Emulex LightPulse®主机总线适配器（HBA）是专为有着最苛刻要求的企业开发的，已在市场上广泛普及，迄今为止已售出1100多万个端口。

经过全面实践验证、业界最高的可靠性可以保证最长的正常运行时间。

通过Emulex的OneCommand™ Manager应用提供的高级管理功能可通过省时的特性为企业带来巨大的可扩展性。

与其它HBA相比，这些特性能用一半的时间提供两倍的管理功能。

Emulex HBA的高性能：•高性能架构•最高的端口性能•在两个端口上提供高37%的数据吞吐量（IOPS）性能•支持多35%的vPort•在混合负载环境中提供一致的加速性能无以伦比的可靠性，可管理性，易部署性和性能表现优化的安装和管理、无以伦比的可扩展性以及业界领先的虚拟化支持都使得E m u l e x LightPulse 主机总线适配器（HBA）产品线成为各种规模企业以及混和操作系统存储区域网络（SAN）环境的理想选择。

LightPulse HBA系列产品具有强大的管理工具和广泛的平台支持，可在最广泛的应用和环境中提供最高性能。

公认的设计、架构和接口LightPulse HBA高度集成的设计可最大限度地减少组件数量，同时先进的错误检查及纠正方法确保了强大的数据完整性。

Emulex独立的固件和驱动程序架构，能够在不重启服务器的情况下完成特性和性能升级，同时所有型号的Emulex HBA使用通用的驱动程序。

Emulex服务器连接解决方案是专为简化数据中心管理流程，提高管理效率而设计的。

浪潮NF5230在redhat5.9下安装raid卡驱动完整配置说明

1、准备服务器驱动光盘和驱动U盘。

-在服务器机箱内。

2、手动加载浪潮驱动lsi2.1、将浪潮驱动光盘和U盘接入PC2.2、双击光驱2.3、点击创建驱动程序2.4、选择OS版本2.5、点击驱动制作2.6、对应实际情况，输入浪潮驱动U盘盘符；2.7、点击OK；2.8、检查是否成功。

3、安装linux3.1、/boot 200M ,swap 和内存一样大, / 剩余全部可用空间3.2、安装包安装市检察院要求安装。

右键全选。

3.3、将linux 5.9安装光盘放入cdrom等待自行加载到安装界面直接输入linuxdd然后按回车键，进入加载驱动盘界面。

切记点击’yes’，然后，会有驱动器列表，/dev/sda、/dev/sdb之类的，不要怕选错，从最后一个开始，选择后有驱动器的分区列表，/dev/sdb1、/dev/sdb2之类的，一个个进去试。

直到找到然后安装即可。

3.4、安装完成后，配置关闭防火墙，关闭selinux4、linux 5.9下，HBA卡驱动安装如果不确定是否安装好驱动，或者确定需要安装驱动，先联系浪潮客服，确定HBA卡型号！！以QlogicQLE2672为例4.1、检查系统是否有驱动在终端中输入/sbin/modinfo qla2xxx|head如果返回结果如上，则驱动已经有了。

因为不同HBA卡，和不同驱动版本问题，还有lsmod|grepqlelsmod|grepqla等方法。

可以逐一验证！4.2、安装驱动新装服务器的HBA卡，如果是Qlogic的可以到他的官网/pages/default.aspx选择对应型号和系统版本来搜索下载。

选择对应型号和系统版本来搜索下载。

4.3、比如QLE2672/QLogicDriverDownloads_UI/SearchProductPreviousRelea se.aspx?ProductCategory=39&Product=1179&Os=65&ResourceCategory=Drivers&grid=1找到对应系统版本驱动。