Broadcom Emulex Drivers for Windows Quick Installation 11.0 and 11.1 User Guide

Broadcom Emulex Drivers for Windows Quick Installation  11.0 and 11.1 User Guide

Emulex Drivers for Windows Quick Installation Manual

Versions 11.0 and 11.1

March 1, 2016 pub-005267

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Corporate Headquarters San Jose, CA Website www.broadcom.com

Broadcom, the pulse logo, Connecting everything, the Connecting everything logo, Avago Technologies, and Emulex are among the trademarks of Broadcom Ltd. and/or its affiliates in the United States, certain other countries and/or the EU. Any other trademarks or trade names mentioned are the property of their respective owners.

Broadcom Ltd. 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 Ltd. is believed to be accurate and reliable. However, Broadcom Ltd. 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.

Copyright © 2003-2016 Broadcom Ltd. All Rights Reserved.

Emulex Driver for Windows Quick Installation Manual March 1, 2016

Table of Contents

Table of Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Driver Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 OneInstall Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.1 Loading the OneInstall Package using Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.2 Loading the OneInstall Package using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.2.1 Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 Driver Kit Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.1 Loading the Driver Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3 AutoPilot Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.1 Starting Installers from a Command Prompt or Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3.2 Running a Software Installation Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3.2.1 Option 1: Automatically Run AutoPilot Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3.2.2 Option 2: Run AutoPilot Installer Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4 Hardware-First Installation or Driver Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.4.1 Software-First Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4.2 Text-Only Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5 Broadcom Emulex iSCSI Crash Dump Driver (OCe14000-Series Adapters Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5.1 Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3: Installation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.1 AutoPilot Installer Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2 OneInstall Installer Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Broadcom Ltd.

- 3 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 1: Introduction Operating System Requirements

Chapter 1: Introduction

This document explains how to install the Broadcom ® Emulex ® drivers for Windows ® on your system.

This product supports the Broadcom family of converged network adapters (CNAs) and the Broadcom family of host bus adapters (HBAs) and converged fabric adapters (CFAs).

NOTE

For a complete list of firmware and adapters that are compatible with these drivers, see the Broadcom website.

1.1

Operating System Requirements

   One of the following operating systems must be installed:  Windows Server ® 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2: x64 versions, Enterprise and Server Core Windows 8 x64 base version, Pro and Enterprise Windows 8.1 x64 base version, Pro and Enterprise Windows 10 

NOTE

Windows 8 x64, Windows 8.1 x64, and Windows 10 drivers are Broadcom signed. You must accept the Broadcom certificate to install these client kits; support is provided by Broadcom, but not by Microsoft.

Check the Broadcom website for required updates to the Windows operating system or the Broadcom Emulex drivers.

NOTE

Microsoft patch KB2846340 must be installed on your system to successfully install the Network Interface Card (NIC) driver. If the patch is not installed on your system, the installation stops and prompts you to install it. This patch, from Microsoft's Knowledge Base (KB), is required for Windows Server 2008 SP2, Windows Server 2008 R2, and Windows Server 2012 and for Windows 8 client operating systems.

Broadcom Ltd.

- 4 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options OneInstall Installer

Chapter 2: Driver Installation Options

You can install the Windows drivers in two ways:   OneInstall Installer – Contains all the Broadcom Emulex Windows drivers (Broadcom Emulex Storport Miniport and NDIS Miniport drivers) and the OneCommand Manager application in a single download package. The OneInstall Installer can be run in Interactive Mode or Silent Mode.

Driver kits and AutoPilot Installer – Provides installation options ranging from simple installations with a few mouse clicks to unattended installations that use predefined script files and text-only installations.

NOTE

Microsoft patch KB2846340 must be installed on your system to successfully install the Network Interface Card (NIC) driver. If the patch is not installed on your system, the installation stops and prompts you to install it. This patch, from Microsoft's Knowledge Base (KB), is required for Windows Server 2008 SP2, Windows Server 2008 R2, and Windows Server 2012 and for Windows 7 and Windows 8 client operating systems.

If you are installing the NIC driver kit as an update to the Windows Server 2012 driver, some parameter defaults are different from the inbox driver. Select “reset to default” on the Advanced tab of the Device Manager property page after you install the Broadcom Emulex out-of-box driver. This returns all adapter and driver settings to the default values listed in this manual.

Low performance might occur if the Broadcom Emulex NIC driver is installed on a system meeting the following conditions before installing Microsoft KB2846837:   A Windows 8-based or Windows Server 2012-based computer with multi-core processors is in use.

Three or more Ethernet ports are installed on the computer.

Receive Side Scaling (RSS) is enabled and sets the RSS profile to use the “Closest” parameter for the Ethernet adapters. If these three conditions exist, install KB2846837 before installing the Broadcom Emulex NIC driver.

2.1

OneInstall Installer

The OneInstall package is a self-extracting executable file that installs the following software on your system:    All compatible protocol drivers:

Fibre Channel (FC)

— —

Fibre Channel over Ethernet (FCoE) internet Small Computer System Interface (iSCSI)

Network Interface Card or Controller plus RDMA over Converged Ethernet (NIC + RoCE) ElxPlus driver (supports the OneCommand Manager application, persistent binding, and LUN mapping and masking) OneCommand Manager application (management utility for Broadcom Emulex adapters)

NOTE

The Enterprise kit for the OneCommand Manager application does not operate locally on Windows Server Core. You must install the OneCommand Manager Core Kit (command-line interface only) to the Windows Server Core.

Broadcom Ltd.

- 5 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options OneInstall Installer

2.1.1

2.1.2

2.1.2.1

NOTE

The OneInstall Installer does not allow you to perform pre-installation tasks, unattended installations, or text-only installations. For these tasks, use the AutoPilot Installer kits.

Loading the OneInstall Package using Interactive Mode

To install the drivers using Interactive mode, perform these steps: 1.

2.

3.

4.

5.

6.

Download the OneInstall package from the Broadcom website.

Navigate to the OneInstall package in Windows Explorer.

Double-click the OneInstall package. The

Welcome

screen appears.

Click

Next

. The

Installation Options

screen appears.

Select the drivers and applications that you want to install and click

Next

. A progress screen appears while the OneInstall installer loads the selected drivers and applications. After the drivers and application software are loaded, an

Installation completed

screen appears.

Click

Finish

.

Loading the OneInstall Package using Silent Mode

Silent mode installation must be run from the from a batch file or from the command line.

If you run OneInstall from a batch file or from a command line prompt, the default Windows behavior starts OneInstall, then immediately continues with the next command. It does not wait until OneInstall has finished. As a result, the value of %ERRORLEVEL% will always be 0, because Windows successfully started OneInstall. It does

not

reflect an accurate OneInstall exit code.

To remedy this, run setup as follows: START /wait OneInstall-Setup-<

version

>.exe

echo %ERRORLEVEL% The "start /wait" ensures that the command does not return until setup has exited. The value of %ERRORLEVEL% now accurately reflects the OneInstall exit code.

Command Format

The format of the command is: OneInstall-Setup-<

version

>.exe <

install-mode

> <

options

> Where: <

version

> is the version number of the OneInstall package <

install-mode

> is one of the following: /q0 – (Interactive, non-silent install) This is the default.

/q1 – (non-Interactive install) This option displays status pages.

/q2 – (Silent install) This option is completely silent, no pages are displayed.

/q – This is the same as /q1 .

<

options

> specifies the kit, or kits, to install: ALL=1 – Install all drivers and the OneCommand Manager application (Default). Broadcom Ltd.

- 6 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options Driver Kit Installer

NOTE

On a CORE system, this will install all drivers and the OneCommand Manager Core Kit.

ALLCORE=1 – Install all drivers and the OneCommand Manager Core Kit.

DRIVERS=1 – Install all drivers. FC=1 – Install the FC driver only.

FCOE=1 – Install the FCoE driver only.

NIC=1 – Install the NIC driver only.

ISCSI=1 – Install the iSCSI driver only.

OCM=1 – Install the OneCommand Manager Enterprise Kit only.

NOTE

On a CORE system, this will install the OneCommand Manager Core Kit.

OMCORE=1 – Install the OneCommand Manager Core Kit only.

To install the drivers using Silent mode, perform these steps: 1.

2.

3.

Download the OneInstall package from the Broadcom website.

Open a DOS window.

Change directory to the folder containing your OneInstall package.

The following are examples of Silent mode commands: Start /wait OneInstall-Setup-10.4.94.4.exe /q2 ALL=1 Start /wait OneInstall-Setup-10.4.94.4.exe /q2 DRIVERS=1 Start /wait OneInstall-Setup-10.4.94.4.exe /q2 FCOE=1 NIC=1 OCM=1 Start /wait OneInstall-Setup-10.4.94.4.exe /q2 Start /wait OneInstall-Setup-10.4.94.4.exe /q2 ALLCORE=1 Start /wait OneInstall-Setup-10.4.94.4.exe /q2 OCMCORE=1

2.2

2.2.1

Driver Kit Installer

    Each driver kit contains and loads all the Windows drivers for a specific protocol, and includes ElxPlus.

FC driver package (elxdrvr-fc-<

version

>.exe) FCoE driver package (elxdrvr-fcoe-<

version

>.exe) iSCSI driver package (elxdrvr-iscsi-<

version

>.exe) NIC + RoCE driver package (elxdrvr-nic-<

version

>.exe)

NOTE

Updating the NIC protocol driver can temporarily disrupt operation of any NIC teams configured on the system.

Loading the Driver Kit

The driver kit copies the selected Broadcom Emulex drivers and applications onto your computer.

NOTE

This procedure does not install drivers, and no driver changes are made until you run the AutoPilot Installer.

To load the driver kit, perform these steps: Broadcom Ltd.

- 7 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options AutoPilot Installer 1.

2.

3.

4.

5.

Download the driver kit from the Broadcom website to your system.

Double-click the driver kit to run it. The Emulex Kit Welcome page appears. Click

Next

. The

Installation Options

window appears.

Select one or both of the following options:

— — Perform Installation of Software

– Copies the driver kit for your operating system to your computer.

Unpack All Drivers

– Extracts all drivers to the current user’s Documents folder. Select this option to perform boot from SAN installations.

The

Operation in progress

window shows the kit file loading progress. After the kit files are loaded, the

Installation completed

window appears.

If you want to continue with the installation, ensure that Start AutoPilot Installer is checked. Click

Next

.

2.3

AutoPilot Installer

   AutoPilot Installer runs after the driver kit is loaded and the OneCommand Manager application is installed. AutoPilot Installer can be installed at these times: Immediately after the driver kit has been loaded At a later time using an interactive installation Through an unattended installation AutoPilot Installer provides the following functions:       Command line functionality – Initiates an installation from a command prompt or script. Configuration settings can be specified in the command line.

Compatibility verification – Verifies that the driver to be installed is compatible with the operating system and platform.

Driver installation and update – Installs and updates drivers.

Multiple adapter installation capability – Installs drivers on multiple adapters, alleviating the need to manually install the same driver on all adapters in the system.

Driver diagnostics – Determines whether the driver is operating properly.

Silent installation mode – Suppresses all screen output (necessary for unattended installation).

NOTE

AutoPilot Installer does not allow you to install the driver if the minimum Windows service pack or Microsoft Storport driver update is not installed.

You can install the driver by using any of the following methods:    

NOTE

These installation methods are not mutually exclusive.

Hardware-first installation

. At least one Broadcom Emulex adapter must be installed before you can install the Broadcom Emulex drivers and utilities.

Software-first installation

. You can install drivers and utilities using AutoPilot Installer prior to the installation of any adapters. You do not need to specify the adapter models to be installed later. The appropriate drivers and utilities automatically load when you install the adapters.

Utility-Only installation

. If the drivers in the driver kit share the same version with those already installed on the system, you can reinstall or update the previously installed utility without reinstalling the drivers.

Text-Only installation

.

Text-based installation mode is used automatically when AutoPilot Installer is run on a Server Core system.

Broadcom Ltd.

- 8 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options AutoPilot Installer

2.3.1

2.3.2

2.3.2.1

2.3.2.2

 

Network installation.

You can place the driver kit installers on a shared network drive and install them across your local area network (LAN). Network-based installation is often used with unattended installation and scripting. This allows you to configure and install the same driver and utility versions on all the hosts in a storage area network (SAN).

Unattended installation

. You can run the driver kit installers and AutoPilot Installer with no user interaction from a command line or script. Unattended installation works for both hardware-first and software-first installations and all driver kits. An unattended installation operates in Silent mode (also referred to as Quiet mode) and creates an extensive report file with installation status.

NOTE

Complete driver and utilities documentation can be downloaded from the Broadcom website.

Starting Installers from a Command Prompt or Script

If a driver kit or an AutoPilot Installer is run from a command prompt or command script (batch file), the Windows command processor does not wait for the installer to run to completion. As a result, you cannot check the exit code of the installer before the next command is executed. Use the “start” command with the “/wait” option. This causes the command processor to wait for the installer to finish before it continues.

For more information on command line installation and configuration parameters, refer to the AutoPilot Installer Command Line and Configuration File Parameters section in the

Emulex Drivers for Windows User Manual.

Running a Software Installation Interactively

Two options are available when performing an installation interactively. These options assume you have already downloaded the driver kit installer from the Broadcom website.

Option 1: Automatically Run AutoPilot Installer

Use this option unless you have specific configuration needs. 1.

2.

3.

4.

Double-click the driver kit or run it from a command line. The command line parameter APargs allows you to specify arguments that are automatically passed to the AutoPilot Installer command. A

Welcome

window is displayed with driver kit version information and Broadcom contact information (refer to the AutoPilot Installer Command Line and Configuration File Parameters topic in the

Emulex Driver for Windows User Manual

for more information on command line installations).

Click

Next

to proceed to the

Installation Options

window.

For each installation option, the default installation location for that option is displayed. Browse to a different location, if desired. Click

Install

to continue the installation.

The

Progress

dialog is displayed. After all tasks complete, a

Finish

window is displayed. The Start AutoPilot Installer box is automatically selected.

Click

Finish

. AutoPilot Installer runs automatically. AutoPilot Installer completes one of the installations:

— —

Hardware-First Installation or Driver and Utility Update (

page 10 ).

Software-First Installation (

page 11

).

Option 2: Run AutoPilot Installer Separately

To access these options, run AutoPilot Installer after the driver kit loading has been completed. This allows you to change the configuration options supplied to the AutoPilot Installer.

1.

Perform steps 1 through 3 for Option 1: Automatically Run AutoPilot Installer .

Broadcom Ltd.

- 9 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016 Chapter 2: Driver Installation Options Hardware-First Installation or Driver Update 2.

3.

Clear the

Run AutoPilot Installer

check box on the

Finish

dialog.

Click

Finish

. The driver kit installer exits.

After the driver kit loading is complete, change the configuration in one of two ways:   Change the configuration file.

Supply parameters on the command line.

NOTE

Refer to the AutoPilot Installer Command Line and Configuration File Parameters section in the

Emulex Drivers for Windows User Manual

for more information on either of these configuration methods. After you have finished this step, you can run AutoPilot Installer at a later time, using either of the following methods:  

NOTE

If you are supplying options using the command line, you must run AutoPilot Installer from the command line.

Select

Programs>Emulex>AutoPilot Installer

in the Start menu. Run AutoPilot Installer from a command line by running theo following command: C:\Program Files\Emulex\AutoPilot Installer\APInstall.exe

NOTE

The location of APInstall.exe

might differ on your system, depending on your system's Program Files location. You can also specify a different location when you install the driver package.

2.4

Hardware-First Installation or Driver Update

The driver kit installer must be downloaded from the Broadcom website and installed before performing this installation.

NOTE

Updating the NIC protocol driver can temporarily disrupt operation of any NIC teams configured on the system.

NOTE

To update the Broadcom Emulex protocol drivers, begin this

procedure at step 2.

To perform a hardware-first installation, perform these steps: 1.

Install a new Broadcom Emulex adapter and power-on the system. If the Windows Found New Hardware wizard is displayed, click

Cancel

to exit; AutoPilot Installer performs this function. 2.

3.

NOTE

The installation continues.

If there are multiple adapters in the system, the Windows Found New Hardware wizard appears multiple times. Click

Cancel

to exit the wizard each time it appears.

Run AutoPilot Installer using any of the options listed in Running a Software Installation Interactively on page 9 .

When the

AutoPilot Installer Welcome

window appears, select an adapter in the list and click

Next

. Consider the following:  If you are updating the driver, the existing port settings are used, unless otherwise specified in the configuration file. These settings are pre-selected but can be changed. Set or change the settings, then click

Next

.

Broadcom Ltd.

- 10 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016

2.4.1

Chapter 2: Driver Installation Options Hardware-First Installation or Driver Update  4.

5.

6.

If you are initially installing a vendor-specific version of the Broadcom Emulex driver installation program, a

Driver Configuration

window may be displayed. This window includes one or more windows with questions that you must answer before continuing the installation process. In this case, answer each question and click

Next

on each window to continue.

Click

Next

. The installation is completed automatically. A dialog is displayed if Windows requires a reboot. After the installation is successful, a

Finish

window appears.

View or print a report, if desired.

— —

View Installation Report – The installation report is a text file with current Broadcom Emulex adapter inventory, configuration information, and task results. Print Installation Report – The Windows print dialog is displayed to select options for printing the installation report.

Click

Finish

to exit AutoPilot Installer.

NOTE

If the system must be rebooted, you are prompted to do so as

indicated in step 4; you must reboot before using the drivers or

utilities.

Software-First Installation

The driver kit must be downloaded from the Broadcom website and loaded before performing this installation. Either the full or core driver package can be installed; but only one can be installed on a system.

To perform a software-first installation, perform these steps: 1.

Run AutoPilot Installer using any of the options listed in

Figure 1 appears.

Running a Software Installation Interactively on page 9 .

Figure 1 AutoPilot Installer Warning (Software-First Installation)

2.

3.

4.

5.

Click

OK

. A

Welcome

window appears. Click

Next

. The installation automatically progresses.

After the installation is successful, the

Finish

window appears.

View or print a report, if desired.

— — View Installation Report

– The installation report is a text file with current Broadcom Emulex adapter inventory, configuration information, and task results.

Print Installation Report

– The Windows print dialog is displayed to select options for printing the installation report.

Click

Finish

to exit AutoPilot Installer. Broadcom Ltd.

- 11 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016

2.4.2

Text-Only Driver Installation

Chapter 2: Driver Installation Options Broadcom Emulex iSCSI Crash Dump Driver (OCe14000-Series Adapters Only) Text-based Installation mode is used automatically when the driver kit installer runs on a server with the Server Core installation option of Windows Server. During text-based installations, AutoPilot Installer uses a command prompt window. The driver kit installer notifies you when the driver is installed and also gives you an opportunity to stop the installation.

Whether AutoPilot installer is launched from the command line or run as a program, Windows always starts AutoPilot Installer as a separate stand-alone task. This means that AutoPilot Installer has its own command prompt window and cannot access others.

2.5

Broadcom Emulex iSCSI Crash Dump Driver (OCe14000-Series Adapters Only)

When you install the Broadcom Emulex NIC driver, you can choose to also install the Broadcom Emulex iSCSI crash dump driver (also referred to as the iSCSI Boot Firmware Table (iBFT) crash dump driver). The Broadcom Emulex iSCSI crash dump driver is intended only for crash dump/hibernation and is not loaded during a normal boot for regular network operations. The Broadcom Emulex iSCSI crash dump driver is named ocibftcd .

Because the Broadcom Emulex iSCSI crash dump driver is a special driver used only for dump, the driver cannot be installed using Windows Device Manager. The driver is provided as an installation option in all the Broadcom Emulex driver installer utilities. When running the NIC Driver Kit in silent mode, add the crashdriver=1 parameter to enable the Broadcom Emulex iSCSI Crash Dump Driver, (The default is 0.) For example: start /wait elxdrvr-nic-.exe /q2 crashdriver=1 When running OneInstall in silent mode, add the ibft=1 parameter to enable the Broadcom Emulex iSCSI Crash Dump Driver. (The default is 0.) For example: start /wait OneInstall-Setup-.exe /q2 ibft=1

NOTE NOTE

Not supported on Windows Server 2008 systems. Supported only on OCe14000-series adapters on systems that support booting into Windows using iBFT configuration. The Broadcom Emulex iSCSI crash dump driver is not supported on 32-bit, IA64 or ARM systems.

Broadcom Ltd.

- 12 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016

2.5.1

Supported Configurations

Chapter 2: Driver Installation Options Broadcom Emulex iSCSI Crash Dump Driver (OCe14000-Series Adapters Only) The dump miniport driver does not support network configurations on its own. The driver works with any iBFT configuration setting used to successfully boot into Windows. The supported network configurations are listed in

Table 1

.

Table 1 Supported Network Configurations Network Configurations

Crash dump modes Internet Protocol options IP configuration methods Port configuration MTU settings MPIO configuration Target discovery iSCSI Login redirection Boot LUN Id

Supported

Small Memory Dump Kernel Memory Dump Complete Memory Dump IPv4 IPv6 Autoconfigure Static IP DHCP Supported on any physical port used to boot into the system.

1514 bytes. However, the actual iSCSI boot might have occurred over a connection that used jumbo MTUs.

Yes Retrieved either through explicit configuration in iBFT menu or using DHCP Supports targets that enable iSCSI login redirection Supports crash dump on any LUN ID Broadcom Ltd.

- 13 -

Emulex Driver for Windows Quick Installation Manual March 1, 2016

Chapter 3: Installation Failure

The two possible failure scenarios are described in this chapter.

3.1

3.2

Chapter 3: Installation Failure AutoPilot Installer Failure

AutoPilot Installer Failure

If the AutoPilot Installer fails, the

Diagnostics

window shows that the adapter failed. If the adapter fails, do the following: 1.

2.

Select the adapter to view the reason why the adapter failed. The reason and suggested corrective action are displayed.

Perform the suggested corrective action and run AutoPilot Installer again.

NOTE

You can run AutoPilot Installer again from the Start menu (

Programs>Emulex>AutoPilot Installer

), or you can run APInstall.exe

from a command prompt.

OneInstall Installer Failure

If the OneInstall Installer fails, it might be because of the following:    The operating system prerequisites have not been met.

The individual kit installation failed. To check, run the installation interactively. If you encounter error messages when you run the installation interactively, those issues would also apply to an unattended installation. If an individual package failed to install properly, run that package's installer directly. This method displays status and error messages that can be used to diagnose the issue. (The OneInstall Installer does not provide this information because each package is installed silently.) Broadcom Ltd.

- 14 -

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement