Broadcom Emulex Software Kit Migration User guide

Broadcom
Brand
Broadcom
Model
Emulex Software Kit Migration
Type
User guide
Emulex® Software Kit Migration
User Guide
Version 11.2
December 30, 2016
pub-005841
Broadcom, the pulse logo, Connecting everything, Avago Technologies, the A logo, Emulex, LightPulse, OneCapture,
OneCommand, and OneConnect are among the trademarks of Broadcom and/or its affiliates in the United States,
certain other countries and/or the EU.
Copyright © 2003-2017 Broadcom. All Rights Reserved.
The term “Broadcom” refers to Broadcom Limited and/or its subsidiaries. For more information, please visit
www.broadcom.com.
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.
Corporate Headquarters Website
San Jose, CA www.broadcom.com
Emulex Software Kit Migration User Guide
December 30, 2016
Emulex Software Kit Migration User Guide
December 30, 2016
Table of Contents
Broadcom
- 3 -
Table of Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Supported Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.1 Inbox Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2 Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.3 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Driver Kit Designations and Application Kit Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2: Installing Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Installing Split Out-of-Box Drivers over Inbox Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.1 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.3 VMware Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.3 VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.4 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 3: Reverting Drivers and Applications to Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3 VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.4 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 4: Technical Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1.1 LightPulse-Specific or OneConnect-Specific Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1.2 Multiple ASICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1.3 Reverting to a Prior Driver Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1.4 Boot Code Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.1 Windows OneInstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.2 Downgrading from a LightPulse 11.2 Kit with LPe16000-series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.3 Downgrading from a LightPulse 11.2 Kit to a 11.0 Kit with LPe12000-Series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3.1 Unloading the lpfc and the brcmfcoe Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3.2 Installing a pre-11.2 Version of OneCommand Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.4.1 VMware Inbox Driver Installation over 11.2 Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.5.1 Running the Install Script of a pre-11.2 Kit Does Not Uninstall the Broadcom OneCommand CNA Manager . . . . . . . . . . . . . . . . . . . . . 36
4.6 Dell Applications Downgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Appendix A: Driver Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Appendix B: Quick Lookup Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
B.1 Quick Lookup Guide, LightPulse and OneConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
B.1.1 LightPulse Adapters and Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
B.1.2 OneConnect Adapters and Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Appendix C: Special Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
C.1 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Emulex Software Kit Migration User Guide
December 30, 2016
Table of Contents
Broadcom
- 4 -
C.2 VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Broadcom
- 5 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 1: Introduction
Supported Adapters
Chapter 1: Introduction
Beginning with software release 11.2, Emulex
®
LightPulse
®
adapters and OneConnect
®
adapters have independent
software kits.
This document provides special instructions and considerations for using the driver kits for LightPulse and
OneConnect adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers
and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTES
Detailed instructions for installing LightPulse kits are provided in
the driver and applications user guide for LightPulse adapters.
Detailed instructions for installing OneConnect kits are provided
in the driver and applications user guide for OneConnect
adapters.
The installation instructions in the user guides apply to “fresh”
installations of the LightPulse or OneConnect drivers, in which the
pre-11.2 drivers were never installed. They also apply going forward,
after the pre-11.2 drivers have been replaced by either LightPulse or
OneConnect drivers.
1.1 Supported Adapters
LightPulse software kits supports the following adapters:
LPe12000 series (FC protocol)
LPe16202/OCe15100 adapters (FC or NIC+FCoE protocol, depending on the SFPs installed)
LPe16000 series (FC protocol)
LPe31000 series (FC protocol)
LPe32000 series (FC protocol)
OneConnect software kits supports the following adapters:
OCe14000 series (NIC, iSCSI, and FCoE protocols)
OCe11000 series (NIC, iSCSI, and FCoE protocols)
1.2 Considerations
If you have both LightPulse and OneConnect adapters in your system and you are upgrading to 11.2, you must
install both kits before rebooting your system.
If you are downgrading from 11.2, you must first uninstall the 11.2 drivers and applications before rebooting
your system.
Existing driver configurations are maintained during the upgrade to 11.2.
Broadcom
- 6 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 1: Introduction
Driver Kit Designations and Application Kit Names
1.2.1 Inbox Drivers
Mixing Linux or ESXi inbox drivers with out-of-box drivers is not a supported configuration. If inbox drivers are
used, make sure to use inbox drivers for all protocols on all LightPulse and OneConnect adapters in the system.
Management applications will work with the inbox drivers.
1.2.2 Management Applications
Install LightPulse management applications from the LightPulse software kit to manage LightPulse adapters.
Install OneConnect management applications from the OneConnect software kit to manage OneConnect
adapters.
Both sets of management applications can run on the same system at the same time.
Management applications prior to the 11.2 release cannot be run with the 11.2 LightPulse or OneConnect
management tools on the same system. For instructions on reverting applications to a version earlier than 11.2,
see Chapter 3 Reverting Drivers and Applications to Previous Versions.
1.2.3 Firmware
A firmware update to version 11.2 is required for all OCe14000-series adapters, OCe11000-series adapters, and
LPe16202/OCe15100 adapters (in NIC+FCoE mode) in the system for UEFI boot code to operate properly.
1.3 Driver Kit Designations and Application Kit Names
The following table provides the original and new designations of the driver kits for each operating system.
Table 1 Driver Kit Designations
Kit Names Windows Linux ESXi Solaris
Original FC kit elxdrvr-fc elx-lpfc lpfc N/A
New LightPulse FC kit elxdrvr-fc elx-lpfc lpfc N/A
New OneConnect FC kit N/A N/A N/A N/A
Original FCoE kit elxdrvr-fcoe elx-lpfc lpfc elxfc
New LightPulse FCoE kit elxdrvr-fcoe elx-lpfc (same kit for FC) lpfc lpfcoe
New OneConnect FCoE kit brcmdrvr-fcoe brcmfcoe brcmfcoe elxfc
Original NIC kit elxdrvr-nic be2net elxnet elxnic
New LightPulse NIC kit elxdrvr-nic lpnic lpnic lpnic
New OneConnect NIC kit brcmdrvr-nic be2net elxnet elxnic
Original iSCSI kit elxdrvr-iscsi be2iscsi be2iscsi N/A
New LightPulse iSCSI kit N/A N/A N/A N/A
New OneConnect iSCSI kit brcmdrvr-iscsi be2iscsi be2iscsi N/A
Broadcom
- 7 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 1: Introduction
Additional Information
The following table provides the new names of the management applications:
1.4 Additional Information
Appendix A provides information about original and new names of driver files, which are embedded in the driver kits.
Appendix B provides illustrations that show the 11.2 kit names, driver names, operating systems, and applications
associated with the LightPulse and OneConnect software kits.
Appendix C contains special instructions on situations that might arise during installation.
Table 2 Application Kit Names
LightPulse Name OneConnect Name Description
OCManager BrcmOCManager Management GUI
HbaCmd BrcmHbaCmd Management CLI
OneCapture™ BrcmOneCapture Dump capture
Elxflash brcmflash Firmware download
linlpcfg brcmlinlpcfg Linux management tool
winlpcfg brcmwinlpcfg Windows management tool
elxcli-fc
elxlpfccli
lpniccli
lpniccli
elxcli-fcoe
brcmfcoecli
elxcli
elxnetcli
esxcli for ESXi 5.5 FC or FCoE
esxcli for ESXi 6.0/6.5 FC or FCoE
esxcli for ESXi 5.5 NIC
esxcli for ESXi 6.0/6.5 NIC
ELXOCM-VMware-vCenter BRCMOCM-VMware-vCenter Management GUI and CLI for VMware vCenter
esx-provider-emulex esx-provider-brcm CIM Provider
Broadcom
- 8 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Inbox Drivers
Chapter 2: Installing Drivers
This section provides instructions for installing and uninstalling the drivers in special situations.
2.1 Installing Split Out-of-Box Drivers over Inbox Drivers
2.1.1 Windows
There are no special procedures needed to install the new out-of-box drivers over existing inbox drivers on Windows.
Follow the installation instructions in the appropriate manual:
For LightPulse adapters, follow the instructions in the Emulex Drivers for Windows for LightPulse Adapters User
Guide, located on the Broadcom website at www.broadcom.com.
For OneConnect adapters, follow the instructions in the Emulex Drivers for Windows for OneConnect Adapters User
Guide, located on the Broadcom website at www.broadcom.com.
2.1.2 Linux
2.1.2.1 LightPulse FC and FCoE Driver with Only LightPulse Adapters Installed
NOTE The existing inbox lpfc driver cannot be removed; it can only be
superseded by an out-of-box driver. When a new out-of-box lpfc driver
is installed, it is placed in either the updates folder or the extras
folder. The Linux kernel then checks both of these folders. If an lpfc
driver is found, that driver is loaded into memory. Otherwise, the inbox
lpfc driver is loaded.
To install the LightPulse FC and FCoE driver with only LightPulse adapters installed in the system, do the following:
1. Issue the tar xvf elx-lpfc-dd-<Linux distribution version>-<driver version>.tar.gz
command.
2. Do one of the following:
— Run the elx_lpfc_install.sh installation script.
— Issue the rpm -ivh elx-lpfc-<driver version>_<Linux distribution version>.rpm
command.
2.1.2.2 OneConnect FCoE Driver with Only OneConnect Adapters Installed
To install the OneConnect FCoE driver with only OneConnect adapters installed in the system, do the following:
1. Issue the tar xvf brcmfcoe-dd-<Linux distribution version><driver version>.tar.gz
command.
2. Do one of the following:
— Run the brcmfcoe_install.sh installation script.
— Issue the rpm -ivh brcmfcoe-<driver version>_<Linux distribution version>.rpm
command.
The OneConnect FCoE driver, brcmfcoe, attaches to OneConnect adapters only. Because the inbox lpfc driver also
supports these adapters, the OneConnect out-of-box FCoE driver cannot load if the inbox lpfc driver has already been
loaded. Therefore, following the steps above will cause the LightPulse driver to be blacklisted to prevent it from
loading.
Broadcom
- 9 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Inbox Drivers
2.1.2.3 LightPulse FC and FCoE Driver and OneConnect FCoE Driver with a Combination of LightPulse and
OneConnect Adapters Installed
To install both the LightPulse FC and FCoE driver and the OneConnect FCoE driver on a system that has both
LightPulse and OneConnect adapters installed, perform the following steps:
1. For the LightPulse driver:
a. Issue the tar xvf elx-lpfc-dd-<Linux distribution version>-<driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_lpfc_install.sh installation script.
Issue the rpm -ivh elx-lpfc-<driver version>_<Linux distribution
version>.rpm command.
2. For the OneConnect driver:
a. Issue the tar xvf brcmfcoe-dd-<Linux distribution version><driver
version>.tar.gz command.
b. Do one of the following:
Run the brcmfcoe_install.sh installation script.
Issue the rpm -ivh brcmfcoe-<driver version>_<Linux distribution
version>.rpm command.
NOTE During the brcmfcoe driver installation, if LightPulse adapters are
detected, the lpfc driver is not blacklisted. Instead, a message prompts
you to install the out-of-box 11.2 or later lpfc driver to ensure the
operation of both LightPulse and OneConnect adapters on the
system.
3. Reboot the system.
2.1.2.4 LightPulse NIC Driver with Only LightPulse Adapters Installed
NOTE The existing inbox be2net driver cannot be removed; it can only be
superseded by an out-of-box driver. When a new out-of-box be2net
driver is installed, it is placed in either the updates folder or the
extras folder. The Linux kernel then checks both of these folders. If a
be2net driver is found, that driver is loaded into memory. Otherwise,
the inbox be2net driver is loaded.
To install the LightPulse NIC driver with only LightPulse adapters installed in the system, do the following:
1. Issue the tar xvf elx-lpnic-dd-<Linux distribution version>-<driver
version>.tar.gz command.
2. Do one of the following:
— Run the elx_lpnic_install.sh installation script.
— Issue the rpm -ivh elx-lpnic-<driver version>_<Linux distribution version>.rpm
command.
The LightPulse NIC driver, lpnic, attaches to LightPulse adapters only. Because the inbox be2net driver also supports
these adapters, the OneConnect out-of-box be2net driver cannot load if the inbox be2net driver has already been
loaded. Therefore, following the steps above will cause the OneConnect driver to be blacklisted to prevent it from
loading.
Broadcom
- 10 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Inbox Drivers
2.1.2.5 OneConnect NIC Driver with Only OneConnect Adapters Installed
To install the OneConnect NIC driver with only OneConnect adapters installed in the system, do the following:
1. Issue the tar xvf elx-be2net-dd-<Linux distribution version><driver
version>.tar.gz command.
2. Do one of the following:
— Run the elx_be2net_install.sh installation script.
— Issue the rpm -ivh elx-be2net-<driver version>_<Linux distribution version>.rpm
command.
2.1.2.6 LightPulse NIC Driver and OneConnect NIC Driver with a Combination of LightPulse and OneConnect Adapters
Installed
To install both the LightPulse NIC driver and the OneConnect NIC driver on a system that has both LightPulse and
OneConnect adapters installed, perform the following steps:
1. For the OneConnect driver:
a. Issue the tar xvf elx-be2net-dd-<Linux distribution version><driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_be2net_install.sh installation script.
Issue the rpm -ivh elx-be2net-<driver version>_<Linux distribution
version>.rpm command.
2. For the LightPulse driver:
a. Issue the tar xvf elx-lpnic-dd-<Linux distribution version>-<driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_lpnic_install.sh installation script.
Issue the rpm -ivh elx-lpnic-<driver version>_<Linux distribution
version>.rpm command.
NOTE During the lpnic driver installation, if OneConnect adapters are
detected, the be2net driver is not blacklisted. Instead, a message
prompts you to install the out-of-box 11.2 or later be2net driver to
ensure the operation of both LightPulse and OneConnect adapters on
the system.
3. Reboot the system.
2.1.3 VMware Drivers
2.1.3.1 LightPulse FC and FCoE Driver with Only LightPulse Adapters Installed
This driver maintains the lpfc driver binary name so it will update the existing inbox driver.
To install this driver, type:
esxcli software vib install –d <path to driver kit>/Emulex-FCoE-FC-lpfc-<driver
version>-offline-bundle-<VMware#>.zip
reboot
When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
Broadcom
- 11 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Inbox Drivers
For special instructions, see Appendix C: Section C.2, VMware.
2.1.3.2 OneConnect FCoE Driver with Only OneConnect Adapters Installed
This driver introduces the brcmfcoe driver binary name. This driver only supports OneConnect adapters. Because this
driver has a different binary name, it will not affect the existing inbox driver on installation.
To install this driver, first remove the lpfc driver, and then install the brcmfcoe driver. This prevents lpfc from claiming
its known PCI IDs in the server.
1. Remove the lpfc driver by typing:
esxcli software vib remove –n lpfc
2. Install the brcmfcoe driver by typing:
esxcli software vib install –d <path to driver kit>/brcm-FCoE-brcmfcoe-<driver
version>-offline-bundle-<VMware#>.zip
reboot
3. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.1.3.3 LightPulse FC and FCoE Driver and OneConnect FCoE Driver with a Combination of LightPulse and
OneConnect Adapters Installed
If your server configuration has both LightPulse and OneConnect adapters, you need to install both of the LightPulse
and OneConnect OOB drivers. Installing both drivers provides complete coverage for all adapter families.
NOTE Because your configuration is using LightPulse and OneConnect
adapters, the inbox lpfc driver is updated with an OOB LightPulse
driver to acquire the LightPulse adapters, and then the OOB
OneConnect driver is added to acquire the OneConnect adapters.
1. To install these drivers, type the following:
esxcli software vib install –d <path to driver
kit>/Emulex-FCoE-FC-lpfc-<driver version>-offline-bundle-<VMware#>.zip
esxcli software vib install –d <path to driver kit>/brcm-FCoE-brcmfcoe-<driver
version>-offline-bundle-<VMware#>.zip
2. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.1.3.4 LightPulse NIC Driver with Only LightPulse Adapters Installed
This driver introduces the lpnic driver binary name. This driver only supports LightPulse adapters. Because this driver
has a different binary name, it will not affect the existing inbox driver on installation.
To install this driver, first remove the elxnet driver, and then install the lpnic driver. This prevents elxnet from claiming
its known PCI IDs in the server.
1. Remove the elxnet driver by typing:
esxcli software vib remove –n elxnet
2. Install the lpnic driver by typing:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-lpnic-<driver version>.zip
Broadcom
- 12 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
reboot
3. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.1.3.5 OneConnect NIC Driver with Only OneConnect Adapters Installed
This driver maintains the elxnet driver binary name so it will update the existing inbox driver.
To install this driver, type:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-elxnet-<driver version>.zip
reboot
When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.1.3.6 LightPulse NIC Driver and OneConnect NIC Driver with a Combination of LightPulse and OneConnect Adapters
If your server configuration has both LightPulse and OneConnect adapters, you need to install both of the LightPulse
and OneConnect OOB drivers. Installing both drivers provides complete coverage for all adapter families.
NOTE Because your configuration is using LightPulse and OneConnect
adapters, the inbox elxnet driver is updated with an OOB OneConnect
driver to acquire the OneConnect adapters, and then the OOB
LightPulse driver is added to acquire the LightPulse adapters.
1. To install these drivers, type the following:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-elxnet-<driver version>.zip
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-lpnic-<driver version>.zip
2. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2 Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box
Drivers
2.2.1 Windows
There are no special procedures needed to install the new out-of-box drivers over existing out-of-box drivers on
Windows. Follow the installation instructions in the appropriate manual:
For LightPulse adapters, follow the instructions in the Emulex Drivers for Windows for LightPulse Adapters User
Guide, located on the Broadcom website at www.broadcom.com.
Broadcom
- 13 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
For OneConnect adapters, follow the instructions in the Emulex Drivers for Windows for OneConnect Adapters User
Guide, located on the Broadcom website at www.broadcom.com.
2.2.2 Linux
2.2.2.1 LightPulse FC and FCoE Driver with Only LightPulse Adapters Installed
NOTE An existing out-of-box lpfc driver cannot be removed; it can only be
superseded by another out-of-box driver. When a new out-of-box lpfc
driver is installed, it is placed in the updates or the extras folder.
The Linux kernel then checks both of these folders. If a new lpfc driver
is found, that driver is loaded into memory. Otherwise, the older lpfc
driver is loaded.
To install the LightPulse FC and FCoE driver with only LightPulse adapters installed in the system, do the following:
1. Issue the tar xvf elx-lpfc-dd-<Linux distribution version>-<driver version>.tar.gz
command.
2. Do one of the following:
— Run the elx_lpfc_install.sh installation script.
— Issue the rpm -ivh elx-lpfc-<driver version>_<Linux distribution version>.rpm
command.
2.2.2.2 OneConnect FCoE Driver with Only OneConnect Adapters Installed
To install the OneConnect FCoE driver with only OneConnect adapters installed in the system, do the following:
1. Issue the tar xvf brcmfcoe-dd-<Linux distribution version><driver version>.tar.gz
command.
2. Do one of the following:
— Run the brcmfcoe_install.sh installation script.
— Issue the rpm -ivh brcmfcoe-<driver version>_<Linux distribution version>.rpm
command.
The OneConnect FCoE driver, brcmfcoe, attaches to OneConnect adapters only. Because the pre-11.2 lpfc driver also
supports these adapters, the 11.2 or later OneConnect out-of-box FCoE driver cannot load if the pre-11.2 lpfc driver
has already been loaded. Therefore, following the steps above will cause the 11.2 or later LightPulse driver to be
blacklisted to prevent it from loading.
2.2.2.3 LightPulse FC and FCoE Driver and OneConnect FCoE Driver with a Combination of LightPulse and
OneConnect Adapters Installed
To install both the LightPulse FC and FCoE driver and the OneConnect FCoE driver on a system that has both
LightPulse and OneConnect adapters installed, perform the following steps:
1. For the LightPulse driver:
a. Issue the tar xvf elx-lpfc-dd-<Linux distribution version>-<driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_lpfc_install.sh installation script.
Issue the rpm -ivh elx-lpfc-<driver version>_<Linux distribution
version>.rpm command.
Broadcom
- 14 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2. For the OneConnect driver:
a. Issue the tar xvf brcmfcoe-dd-<Linux distribution version><driver
version>.tar.gz command.
b. Do one of the following:
Run the brcmfcoe_install.sh installation script.
Issue the rpm -ivh brcmfcoe-<driver version>_<Linux distribution
version>.rpm command.
NOTE During the 11.2 or later brcmfcoe driver installation, if LightPulse
adapters are detected, the pre-11.2 lpfc driver is not blacklisted.
Instead, a message prompts you to install the out-of-box 11.2 or later
lpfc driver to ensure the operation of both LightPulse and OneConnect
adapters on the system.
3. Reboot the system.
2.2.2.4 LightPulse NIC Driver with Only LightPulse Adapters Installed
NOTE An existing out-of-box be2net driver cannot be removed; it can only
be superseded by an out-of-box driver. When a new out-of-box be2net
driver is installed, it is placed in either the updates folder or the
extras folder. The Linux kernel then checks both of these folders. If a
be2net driver is found, that driver is loaded into memory. Otherwise,
the inbox be2net driver is loaded.
To install the LightPulse NIC driver with only LightPulse adapters installed in the system, do the following:
1. Issue the tar xvf elx-lpnic-dd-<Linux distribution version>-<driver
version>.tar.gz command.
2. Do one of the following:
— Run the elx_lpnic_install.sh installation script.
— Issue the rpm -ivh elx-lpnic-<driver version>_<Linux distribution version>.rpm
command.
The LightPulse NIC driver, lpnic, attaches to LightPulse adapters only. Because the pre-11.2 be2net driver also
supports these adapters, the OneConnect out-of-box 11.2 or later be2net driver cannot load if the pre-11.2 be2net
driver has already been loaded. Therefore, following the steps above will cause the OneConnect out-of-box 11.2 or
later driver to be blacklisted to prevent it from loading.
2.2.2.5 OneConnect NIC Driver with Only OneConnect Adapters Installed
To install the OneConnect NIC driver with only OneConnect adapters installed in the system, do the following:
1. Issue the tar xvf elx-be2net-dd-<Linux distribution version><driver
version>.tar.gz command.
2. Do one of the following:
— Run the elx_be2net_install.sh installation script.
— Issue the rpm -ivh elx-be2net-<driver version>_<Linux distribution version>.rpm
command.
Broadcom
- 15 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2.2.2.6 LightPulse NIC Driver and OneConnect NIC Driver with a Combination of LightPulse and OneConnect Adapters
Installed
To install both the LightPulse NIC driver and the OneConnect NIC driver on a system that has both LightPulse and
OneConnect adapters installed, perform the following steps:
1. For the OneConnect driver:
a. Issue the tar xvf elx-be2net-dd-<Linux distribution version><driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_be2net_install.sh installation script.
Issue the rpm -ivh elx-be2net-<driver version>_<Linux distribution
version>.rpm command.
2. For the LightPulse driver:
a. Issue the tar xvf elx-lpnic-dd-<Linux distribution version>-<driver
version>.tar.gz command.
b. Do one of the following:
Run the elx_lpnic_install.sh installation script.
Issue the rpm -ivh elx-lpnic-<driver version>_<Linux distribution
version>.rpm command.
NOTE During the 11.2 or later lpnic driver installation, if OneConnect
adapters are detected, the pre-11.2 out-of-box be2net driver is not
blacklisted. Instead, a message prompts you to install the out-of-box
11.2 or later be2net driver to ensure the operation of both LightPulse
and OneConnect adapters on the system.
3. Reboot the system.
2.2.3 VMware
2.2.3.1 LightPulse FC and FCoE Driver with Only LightPulse Adapters Installed
This driver maintains the lpfc driver binary name so it will update the out-of-box driver.
To install this driver, type:
esxcli software vib install –d <path to driver kit>/Emulex-FCoE-FC-lpfc-<driver
version>-offline-bundle-<VMware#>.zip
reboot
When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
Broadcom
- 16 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2.2.3.2 OneConnect FCoE Driver with Only OneConnect Adapters Installed
This driver introduces the brcmfcoe driver binary name. This driver only supports OneConnect adapters. Because this
driver has a different binary name, it will not affect the existing out-of-box driver on installation.
To install this driver, first remove the lpfc driver, and then install the brcmfcoe driver. This prevents lpfc from claiming
its known PCI IDs in the server.
1. Remove the lpfc driver by typing:
esxcli software vib remove –n lpfc
2. Install the brcmfcoe driver by typing:
esxcli software vib install –d <path to driver kit>/brcm-FCoE-brcmfcoe-<driver
version>-offline-bundle-<VMware#>.zip
reboot
3. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2.3.3 LightPulse FC and FCoE Driver and OneConnect FCoE Driver with a Combination of LightPulse and
OneConnect Adapters Installed
If your server configuration has both LightPulse and OneConnect adapters, you need to install both of the LightPulse
and OneConnect OOB drivers. Installing both drivers provides complete coverage for all adapter families.
NOTE Because your configuration is using LightPulse and OneConnect
adapters, the existing out-of-box lpfc driver is updated with an
out-of-box LightPulse driver to acquire the LightPulse adapters, and
then the out-of-box OneConnect driver is added to acquire the
OneConnect adapters.
1. To install these drivers, type the following:
esxcli software vib install –d <path to driver
kit>/Emulex-FCoE-FC-lpfc-<driver version>-offline-bundle-<VMware#>.zip
esxcli software vib install –d <path to driver kit>/brcm-FCoE-brcmfcoe-<driver
version>-offline-bundle-<VMware#>.zip
reboot
2. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2.3.4 LightPulse NIC Driver with Only LightPulse Adapters Installed
This driver introduces the lpnic driver binary name. This driver only supports LightPulse adapters. Because this driver
has a different binary name, it will not affect the existing out-of-box driver on installation.
To install this driver, first remove the elxnet driver, and then install the lpnic driver. This prevents elxnet from claiming
its known PCI IDs in the server.
1. Remove the elxnet driver by typing:
esxcli software vib remove –n elxnet
Broadcom
- 17 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2. Install the lpnic driver by typing:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-lpnic-<driver version>.zip
reboot
3. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2.3.5 OneConnect NIC Driver with Only OneConnect Adapters Installed
This driver maintains the elxnet driver binary name so it will update the existing out-of-box driver.
To install this driver, type:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-elxnet-<driver version>.zip
reboot
When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2.3.6 LightPulse NIC Driver and OneConnect NIC Driver with a Combination of LightPulse and OneConnect Adapters
Installed
If your server configuration has both LightPulse and OneConnect adapters, you need to install both of the LightPulse
and OneConnect OOB drivers. Installing both drivers provides complete coverage for all adapter families.
NOTE Because your configuration is using LightPulse and OneConnect
adapters, the existing out-of-box elxnet driver is updated with an
out-of-box OneConnect driver to acquire the OneConnect adapters.
Then the out-of-box LightPulse driver is added to acquire the
LightPulse adapters.
1. To install these drivers, type the following:
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-elxnet-<driver version>.zip
esxcli software vib install –d <path to driver kit>/esx-<OS
version>-lpnic-<driver version>.zip
2. When the server has rebooted, check the vmhba enumeration to driver binary as follows:
esxcli storage core adapter list
For special instructions, see Appendix C: Section C.2, VMware.
2.2.4 Solaris
2.2.4.1 LightPulse FCoE Driver with Only LightPulse Adapters Installed
Install the LightPulse out-of-box driver over the combined out-of-box driver.
1. Uninstall the combined out-of-box driver (elxfc) if it is present:
/elxfc_remove
Broadcom
- 18 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2. Install the lpfcoe driver for the LightPulse adapter.
Untar the driver kit:
tar –xf lpfcoe_kit-<driver version>-<OS version>-s11-i386.tar
Install the driver:
/lpfcoe_install
2.2.4.2 OneConnect FCoE Driver with Only OneConnect Adapters Installed
Install the elxfc driver for the OneConnect adapter.
Untar the driver kit:
tar –xf elxfc_kit-<driver version>-<OS version>-s11-i386.tar
Install the driver:
/elxfc_install
2.2.4.3 LightPulse FC and FCoE Driver and OneConnect FCoE Driver with a Combination of LightPulse and
OneConnect Adapters Installed
Install the LightPulse out-of-box driver over the combined out-of-box driver:
1. Uninstall the combined out-of-box driver (elxfc) if it is present:
/elxfc_remove
2. Install the lpfcoe driver for the LightPulse adapter:
a. Untar the driver kit:
tar –xf lpfcoe_kit-<driver version>-<OS version>-i386.tar
b. Install the driver:
/lpfcoe_install
3. Install the elxfc driver for the OneConnect adapter.
a. Untar the driver kit:
tar –xf elxfc_kit-<driver version>-<OS version>-i386.tar
b. Install the driver:
/elxfc_install
2.2.4.4 LightPulse NIC Driver with Only LightPulse Adapters Installed
Install the LightPulse out-of-box driver over the combined out-of-box driver.
1. Uninstall the combined out-of-box driver (elxnic) if it is present:
/elxnic_remove
2. Install the lpnic driver for the LightPulse adapter.
Untar the driver kit:
tar –xf lpnic_kit-<driver version>-<OS version>-i386.tar
Install the driver:
/lpnic_install
Broadcom
- 19 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 2: Installing Drivers
Installing Split Out-of-Box Drivers over Existing 11.1 or Earlier Out-of-Box Drivers
2.2.4.5 OneConnect NIC Driver with Only OneConnect Adapters Installed
Install the elxnic driver for the OneConnect adapter.
Untar the driver kit:
tar –xf elxnic_kit-<driver version>-<OS version>-i386.tar
Install the driver:
/elxnic_install
2.2.4.6 LightPulse NIC Driver and OneConnect NIC Driver with a Combination of LightPulse and OneConnect Adapters
Installed
Install the LightPulse out-of-box driver over the combined out-of-box driver:
1. Uninstall the combined out-of-box driver (elxfc) if it is present:
/elxfc_remove
2. Install the lpfcoe driver for the LightPulse adapter:
a. Untar the driver kit:
tar –xf lpfcoe_kit-<driver version>-<OS version>-i386.tar
b. Install the driver:
/lpfcoe_install
3. Install the elxfc driver for the OneConnect adapter.
a. Untar the driver kit:
tar –xf elxfc_kit-<driver version>-<OS version>-i386.tar
b. Install the driver:
/elxfc_install
Broadcom
- 20 -
Emulex Software Kit Migration User Guide
December 30, 2016
Chapter 3: Reverting Drivers and Applications to Previous Versions
Windows
Chapter 3: Reverting Drivers and Applications to Previous Versions
This section describes the downgrade process if you have 11.2 driver and OneCommand Manager for LightPulse or
OneCommand CNA Manager for OneConnect application kits installed and you want to revert to an earlier version.
This applies to both LightPulse and OneConnect 11.2 kits.
NOTE You must uninstall all 11.2 components before installing pre-11.2
components. Mixing 11.2 and pre-11.2 components will cause
unexpected results, such as adapters not being discovered by drivers
and management applications.
3.1 Windows
You must uninstall all 11.2 Windows components (drivers and management applications) before installing a pre-11.2
Windows kit.
To uninstall all 11.2 Windows components, do the following:
1. Launch the Control Panel from the start menu and select Programs and Features.
2. Click on all of the kits listed below that appear in the list of installed programs.
NOTE All of the 11.2 driver and management application kits must be
removed. Any combination of pre-11.2 and 11.2 kits is not supported.
— LightPulse driver kits:
Emulex/FC kit – 11.2.<version>
Emulex/FCoE kit – 11.2.<version>
Emulex/NIC kit – 11.2.<version>
— OneConnect Driver kits:
Broadcom/FCoE kit – 11.2.<version>
Broadcom/NIC kit – 11.2.<version>
Broadcom/iSCSI kit – 11.2.<version>
— LightPulse OneCommand Manager kits:
Emulex OCManager Enterprise 11.2.<version>
Emulex OCManager CLI 11.2.<version>
— OneConnect OneCommand CNA Manager kits:
Broadcom OCManager Enterprise 11.2.<version>
Broadcom OCManager CLI 11.2.<version>
3. Select uninstall. The selected components are uninstalled.
After the uninstallation process is complete, verify that the 11.2 drivers were uninstalled:
From the Computer Management screen, open the Device Manager (see Figure 1).
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56

Broadcom Emulex Software Kit Migration User guide

Broadcom
Brand
Broadcom
Model
Emulex Software Kit Migration
Type
User guide
Download PDF
report

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI

Related papers

Other documents