Emulex Boot For NIC, iSCSI, and FCoE Protocols User Guide

Emulex® Boot for NIC, iSCSI, and FCoE Protocols
User Guide
Version 11.2
December 30, 2016
NIF-Boot-OCA-UG112
Emulex Boot for NIC, iSCSI, and FCoE Protocols User Guide
December 30, 2016
Corporate Headquarters Website

San Jose, CA www.broadcom.com
Broadcom, the pulse logo, Connecting everything, Avago Technologies, Avago, the A logo, Emulex, 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 by 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.
Boot for NIC, iSCSI, and FCoE Protocols User Guide Table of Contents
December 30, 2016
Table of Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Configuring the PXE Boot for NIC on OCe11100-Series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1 Pre-OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 PXE Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 Remotely Installing with the PXE for Windows Server 2008, 2008R2, 2012, 2012 R2, and Windows Server 2016 . . . . . . . . . . . . . . . . . 13
2.3 Remotely Installing with the PXE for Linux and Citrix Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 Using the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.1 Navigating the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.2 Running the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.3 Setting Up a PXE Bootable Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.4 Configuring Ports If UMC Is Disabled or Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.5 Configuring Universal Multichannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.6 Configuring Multichannel for Lenovo System x Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.7 Advanced Mode Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.8 Personality Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5 PXE Boot Parameters Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 3: Configuring PXE Boot for NIC on OCe14000-Series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1 Pre-OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 PXE Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3 Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4 Remotely Installing with PXE for Linux and Citrix Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5 Using the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5.1 Navigating the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5.2 Running the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5.3 Setting Up a PXE Bootable Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5.4 Configuring Ports If UMC Is Disabled or Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.5.5 Configuring Universal Multichannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.5.6 Configuring Multichannel for Lenovo System x Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6 PXE Boot Parameters Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 4: Configuring Boot from SAN for the FCoE Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.1 Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.1.1 Configuring Boot from SAN on Windows (x64) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.1.2 Configuring Boot from SAN on Windows (UEFI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.1.3 Installing a New Windows UEFI-Aware Operating System on a UEFI-Based x64 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.1.4 Directing a UEFI-Based Server to a Windows Server Operating System Image Already Installed on the SAN . . . . . . . . . . . . . . . . . . . . . 52
4.2 Installing Windows Server on a Boot Disk (x64) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3 Linux, Citrix, and VMware Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.3.1 Configuring Boot from SAN on Linux, Citrix, or VMware (x86 and x64) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.3.2 Configuring Boot from SAN on Linux or VMware (UEFI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4 Solaris Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.1 Configuring Boot from SAN on Solaris (x86 and x64) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.2 Determining LUNs to Select for Boot from SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 5: Configuring x86/x64 Platforms for the iSCSI Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.1 Constructing a Basic iSCSI SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2 Managing an iSCSI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2.1 Logging in to an iSCSI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.3 Configuring Boot from SAN for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.3.1 Setting Up Boot from SAN for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Broadcom
-3-
December 30, 2016
5.3.2 Booting from SAN for iSCSI MPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 6: Using the FCoE Boot BIOS Utility for x86 and x64 Architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.1 Navigating the FCoE BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.2 Starting the FCoE BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.3 Enabling an Adapter to Boot from SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.4 Scanning for Target Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.5 Configuring Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.6 Configuring FCoE FCF CEE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7 Configuring Advanced Adapter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.7.1 Changing the Port Login Retry Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.7.2 Enabling or Disabling the Spinup Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.7.3 Setting Auto Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.7.4 Enabling or Disabling EDD 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.7.5 Enabling or Disabling the Start Unit Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.7.6 Enabling or Disabling the Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.7.7 Enabling or Disabling Auto Boot Sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.8 Using Multipath Boot from SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.9 Resetting to Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 7: Updating and Enabling Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 8: Configuring iSCSI Boot Support with the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

8.1 Navigating the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.2 Setting Up a Basic iSCSI Boot Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.3 Booting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 9: Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.1 Selecting an Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.2 Viewing the Controller Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.2.1 Enabling Boot Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.2.2 Enabling IPv4 Boot Target Discovery using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.2.3 Enabling the MPIO Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.2.4 Configuring the iSCSI Initiator Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.3 Configuring Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.3.1 Selecting the IP Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.3.2 Configuring VLAN ID and VLAN Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.3.3 Configuring an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.4 Identifying a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
9.5 Erasing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 10: Configuring and Managing iSCSI Targets with the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
10.1 Adding iSCSI Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
10.1.1 Using the SendTargets Discovery to Add an iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
10.1.2 Manually Adding an iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
10.2 Managing an iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10.2.1 Viewing Target Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10.2.2 Editing a Target Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10.2.3 Viewing Advanced Target Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.2.4 Configuring LUN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.2.5 Logging In to and Out of a Configured Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.2.6 Removing a Configured Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.2.7 Booting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.3 Discovering Targets through DHCP for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.4 Enabling DHCP Discovery through the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Chapter 11: Configuring UEFI for Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

11.1 Navigating the Emulex NIC Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Broadcom
-4-
December 30, 2016
11.2 Starting the Emulex NIC Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

11.2.1 Advanced Mode Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
11.2.2 Configuring Boot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
11.2.3 Configuring iBFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
11.2.4 Configuring Personality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
11.2.5 Link Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.2.6 Configuring Virtual LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
11.2.7 Configuring the Adapter If UMC Is Disabled or Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11.2.8 Configuring Universal Multichannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
11.2.9 Configuring Multichannel for Lenovo System x Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.2.10 Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.2.11 Feature on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.3 Downloading Firmware and Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.4 Identifying a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.5 Erasing Ports and Adapter Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.6 UEFI NIC Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.6.1 EFI_DRIVER_DIAGNOSTICS_PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Chapter 12: Configuring UEFI for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

12.1 Navigating the Emulex iSCSI Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
12.2 Starting the Emulex iSCSI Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
12.3 Configuring MPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.4 Configuring Boot Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.5 Configuring TCP ACK Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.6 Viewing the Controller Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
12.7 Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
12.7.1 Configuring the IP Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
12.7.2 Configuring an IPv4 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
12.7.3 Configuring an IPv6 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
12.7.4 Configuring VLAN ID and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
12.8 Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
12.9 Adding and Configuring Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
12.9.1 Discovering and Adding Boot Targets through DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
12.9.2 Using the SendTargets Discovery to Add an iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
12.9.3 Manually Adding, Discovering, and Managing Boot Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
12.9.4 Setting a Boot Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
12.9.5 Selecting an Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
12.9.6 Pinging a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
12.9.7 Viewing Advanced Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
12.9.8 Logging In to or Out of a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12.9.9 Deleting a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12.9.10 Configuring LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12.9.11 iSNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
12.10 Erasing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Chapter 13: Configuring UEFI for FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

13.1 Navigating the Emulex FCoE Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
13.2 Starting the Emulex FCoE Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
13.3 Updating Firmware and Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
13.4 Enabling an Adapter to Boot from SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
13.5 Configuring CEE FCF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
13.6 Scanning for Fibre Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
13.7 Adding Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
13.8 Deleting Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
13.9 Changing Boot Device Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
13.10 Configuring Adapter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
13.10.1 Changing the Port Login Retry Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
13.10.2 Changing the Maximum LUNs per Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Broadcom
-5-
December 30, 2016
13.10.3 Changing Boot Target Scan Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

13.10.4 Changing Device Discovery Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
13.11 Resetting Emulex Adapters to Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
13.12 Displaying Adapter Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
13.13 Configuring Legacy Only Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
13.13.1 Enabling or Disabling the Spinup Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
13.13.2 Enabling or Disabling EDD 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
13.13.3 Enabling or Disabling the Start Unit Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.13.4 Enabling or Disabling the Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.13.5 Enabling or Disabling Auto Boot Sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.13.6 Configuring the Auto Scan Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.14 Requesting a Reset or Reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Chapter 14: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

14.1 Troubleshooting for the NIC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
14.1.1 Issues During the PXE Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
14.1.2 PXE Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
14.2 Troubleshooting for the iSCSI Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
14.3 Troubleshooting for the FCoE Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Appendix A: Configuring iSCSI through a DHCP Server Using Vendor-Specific Option 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
A.1 Format of Vendor-Specific Option 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
A.1.1 Description of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
A.1.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Appendix B: Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFIBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
B.1 Linux and Citrix PXE Server Remote Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
B.1.1 PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
B.1.2 Copying Files to the TFTP Server with the Graphical Version of the Network Booting Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Appendix C: Examples for Configuring and Booting UEFI NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

C.1 UEFI NIC Server Configuration Script for SLES11 SPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
C.1.1 NFS Server Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
C.1.2 DHCP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
C.1.3 TFTP Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
C.2 UEFI NIC Server Configuration Script for RHEL 6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
C.2.1 Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
C.2.2 NFS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
C.2.3 TFTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
C.2.4 PXE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
C.2.5 Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
C.3 Configuring the Lenovo System x HS22 Blade with e-Raptor MEZZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
C.4 UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
C.4.1 Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
C.4.2 PXE Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
C.4.3 Configure DHCPD6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
C.4.4 Configure TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
C.4.5 PXE Client Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Appendix D: Example for Installing and Booting UEFI FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Appendix E: Loading and Unloading UEFIBoot from the UEFI Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
E.1 Loading UEFIBoot from the UEFI Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
E.2 Unloading UEFIBoot from the UEFI Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Appendix F: Dell UEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

F.1 Accessing the Main Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
F.2 Main Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
F.2.1 Firmware Image Properties Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Broadcom
-6-
December 30, 2016
F.2.2 NIC Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

F.2.3 iSCSI Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
F.2.4 FCoE Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
F.2.5 Device Level Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
F.2.6 NIC Partitioning Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
F.3 Secure Firmware Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Appendix G: Configuring PXE Boot for NIC on Dell OCe14000-Based Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
G.1 Running the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
G.2 Navigating the PXESelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
G.3 Setting Up a PXE Bootable Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
G.3.1 Configuring NPar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
G.3.2 Selecting the Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
G.3.3 Configuring Boot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
21.3.1 Configuring Port Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
G.4 PXE Boot Parameters Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Broadcom
-7-
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 1: Introduction
December 30, 2016
Chapter 1: Introduction
This guide describes installing, enabling, and configuring boot code for Emulex® network interface card (NIC), Internet
Small Computer System Interface (iSCSI), and Fibre Channel over Ethernet (FCoE) adapters. This guide also describes
the Emulex boot from SAN implementation and its operation with distinct hardware and operating system
requirements.
Boot from SAN is the process of booting a server directly from a disk operating system image located on a storage area
network (SAN) by way of Emulex adapters using Emulex boot code. When booting from SAN, the storage device is
typically identified by its World Wide Port Name (WWPN) and a logical unit number (LUN). By extending the server
system boot basic input/output system (BIOS), boot from SAN functionality is provided by the boot BIOS contained on
an Emulex adapter in the server. If properly configured, the adapter then permanently directs the server to boot from
a logical unit (disk) on the SAN as if it were a local disk.
Broadcom provides the following types of boot code:
 Preboot Execution Environment (PXE) boot for NIC adapters in x86 and x64 systems
 x86 BootBIOS for FCoE adapters in x86 and x64 systems
 iSCSI boot for iSCSI adapters in x86 and x64 systems
 UEFIBoot for NIC, iSCSI, and FCoE adapters in x64 systems
UEFIBoot provides system boot capability through the use of the UEFI (Unified Extensible Firmware Interface)
shell. It also functions on UEFI 2.x-based platforms through the HII (Human Interface Infrastructure).
NOTE Emulex drivers support multipath boot configurations. See your

storage vendor's documentation for information on configuring
multipath booting.
The Emulex boot code and the following utilities provide a variety of capabilities:
 Boot from SAN across different networking protocols and operating systems
 UEFI configuration using the Emulex NIC, FCoE, and iSCSI configuration utilities
 PXESelect utility
— Configuring the port and adapter
— Configuring Universal Multichannel (UMC) support and personality options
 FCoE x86 BootBIOS utility
— Scanning for target devices
— Configuring boot devices and advanced adapter parameters
 iSCSISelect utility
— Setting up a basic configuration
— Configuring and managing iSCSI initiators and targets
The boot code is distributed in the same image used to flash the firmware. Several methods are available for flashing
the firmware and boot code image. See the documentation accompanying each utility for more information on the
flash procedure.
NOTE Screenshots in this guide are for illustrative purposes only. Your system
information can vary.
Broadcom
-8-
December 30, 2016 Abbreviation
1.1 Abbreviation
ACL Access Control List

API Application Programming Interface
ARI Alternative Routing-ID Interpretation
ARP Address Resolution Protocol
BBS BIOS Boot Specification
BIOS Basic Input/Output System
CHAP Challenge Handshake Authentication Protocol
CLI Command Line Interface
CNA Converged Network Adapter
DCBX Data Center Bridging Capabilities Exchange
DHCP Dynamic Host Control Protocol
DID device ID
DMA Direct Memory Access
DNS Domain Name System or Domain Name Server
EDD Enhanced Disk Device
EFI Extensible Firmware Interface
FC Fibre Channel
FCF Fibre Channel over Ethernet Forwarder
FCoE Fibre Channel over Ethernet
FoD Feature on Demand
FTP File Transfer Protocol
FUI FoD Unique Identifier
GPT GUID partition table
GUI Graphical User Interface
GUID Globally Unique Identifier
HBA Host Bus Adapter
HII Human Interface Infrastructure
HTTP Hypertext Transfer Protocol
iBFT iSCSI Boot Firmware Table
ICMP Internet Control Message Protocol
I/O input/output
IP Internet Protocol
IQN iSCSI Qualified Name
iSCSI Internet Small Computer System Interface
ISID Initiator Session Identifier
iSNS Internet Storage Name Service
JBOD just a bunch of disks
LAN Local Area Network
LED Light-emitting diode
LOM LAN on motherboard
Broadcom
-9-
LPVID logical port VLAN ID

LUN Logical Unit Number
MAC Media Access Control
MPIO Multipath I/O
MTU Maximum Transmission Unit
NBP Network Boot Program
NFS Network File System
NIC Network Interface Card
NPar NIC partitioning
NTFS New Technology File System
NVRAM Non-volatile Random-access Memory
OS Operating System
PCI Peripheral Component Interconnect (interface)
PCIe Peripheral Component Interconnect Express
PF physical function
POST Power-on Self-test
PXE Preboot Execution Environment
QoS Quality of Service
RAID Redundant Array of Independent Disks
RDMA Remote Direct Memory Access
RHEL Red Hat Enterprise Linux
RoCE RDMA over Converged Ethernet
ROM read-only memory
RSS Receive-side Scaling
SAN Storage Area Network
SCSI Small Computer System Interface
SFS SAN Foundation Software
SLES SUSE Linux Enterprise Server
SMB Server Message Block
SR-IOV Single Root I/O Virtualization
SVID service VLAN ID
TCP Transmission Control Protocol
TCP/IP TCP over Internet Protocol
TFTP Trivial File Transfer Protocol
TOE TCP Offload Engine
UEFI Unified Extensible Firmware Interface
UFP Unified Fabric Port
UMC Universal Multichannel
UNDI Universal Network Device Interface
USB Universal Serial Bus
VF virtual function
VLAN virtual local area network
VLAN ID VLAN identifier
Broadcom
- 10 -
VMQ virtual machine queue

WDS Windows Deployment Services
WoL Wake on LAN
WWN World Wide Name
WWNN World Wide Node Name
WWPN World Wide Port Name
Broadcom
- 11 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 2: Configuring the PXE Boot for NIC on OCe11100-Series Adapters
December 30, 2016 Pre-OS
Chapter 2: Configuring the PXE Boot for NIC on OCe11100-Series

Adapters
NOTE This section applies to Emulex OCe11100-series adapters. For
information on configuring Emulex OCe14000-series adapters, see
Chapter 3, Configuring PXE Boot for NIC on OCe14000-Series
Adapters.
This section describes using and configuring the PXE to boot computers using a network interface independent of
available data storage devices (such as hard disks) or installed operating systems.
The PXE protocol is a combination of DHCP and TFTP with subtle modifications to both. DHCP locates the appropriate
boot server or servers, and TFTP downloads the initial bootstrap program and additional files.
Network booting enables you to perform the following tasks:
 Boot diskless systems such as thin clients and dedicated systems.
 Deploy software and operating systems for your systems.
 Automate system maintenance, such as backups.
 Automate system checking, such as virus scanning.
 Ensure system security.
2.1 Pre-OS
The PXE can be used in a pre-OS environment. Pre-OS is the process of loading a small operating environment to
perform a client management task before loading the final operating system from the local hard drive. For example,
with a pre-OS you can scan the hard drive for viruses. This guarantees that the client is not infected before it starts.
Another example is the WDS using this feature to install operating systems on local disks or boot from SAN disks.
2.2 PXE Boot Process
After the PXE boot is enabled in the system UEFI and BIOS, the PXE client can boot up and start the PXE boot ROM
code. This is the boot code physically located on the NIC adapter.
Figure 1 shows the boot process.
NOTE To enable or disable the PXE boot, it must be enabled or disabled in

the system UEFI and BIOS; see the documentation that accompanied
the server for more information.
Broadcom
- 12 -
December 30, 2016 PXE Boot Process
Figure 1 PXE Boot Process
1. The PXE boot ROM sends a DHCP request extended with PXE specific options (step 1 in the figure).
2. The DHCP responses contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot server lists
(steps 2 through 5).
3. The PXE client attempts to download the specified NBP over TFTP from one of the specified boot servers (steps 6
and 7).
4. The PXE client executes the downloaded NBP (steps 8 and 9).
NOTE If any of these steps fail, the boot process typically continues using the
next available device in the boot sequence, depending on the system
configuration and boot order.
2.2.1 Remotely Installing with the PXE for Windows Server 2008, 2008R2, 2012, 2012 R2, and
Windows Server 2016
For remote installation with PXE, a network driver for the Emulex adapter must be part of the client's installation
image on the server. The current versions of Windows Server 2008 and Windows Server 2008 R2 do not include
network drivers for the Emulex adapter; however, Windows Server 2012, 2012 R2, and 2016 include the network driver
for the Emulex adapter.
To add the image and installation using the driver with the Remote Installation Service Setup:
Broadcom
- 13 -
December 30, 2016 Remotely Installing with the PXE for Linux and Citrix Servers
Select Start Menu > Programs > Administrative Tools > Remote Installation Services Setup
In addition to the network driver for the Emulex adapter, you must configure the following services to use the PXE for
remote installations:
 DHCP server
 Remote Installation Services
 Windows Deployment Services
Microsoft provides extensive documentation on deploying its operating systems for remote installations, and
different setups may be required depending on your individual implementation. Microsoft provides step-by-step
guides for its Windows Deployment Services for configuring the server, adding images, and installing an operating
system. It also includes instructions for more advanced tasks like creating multicast transmissions, creating custom
images, and performing an unattended installation.
For detailed information on deploying and managing remote installations on Windows Server 2008, Windows Server
2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 see the Microsoft website and
visit Microsoft TechNet. Search on the bulleted terms above to access Microsoft's wide-ranging documentation on
these subjects.
2.3 Remotely Installing with the PXE for Linux and Citrix Servers
Linux allows for PXE installation over a network using the NFS, TFTP, or HTTP protocols. If the system to be installed
contains an Emulex NIC adapter with PXE Boot support, it can be configured to boot from files on another networked
system rather than local media.
The Linux distributions provide extensive documentation on deploying and managing remote installations of the
Linux operating system using PXE. See the distribution's documentation for instructions on deploying a PXE
installation over the network.
image on the server. The current Linux distribution may or may not include network drivers for Emulex adapters. If it
does, the driver may need to be added to the operating system installation image, or added during installation. See
the distribution's documentation for instructions on adding drivers during installation.
2.4 Using the PXESelect Utility
This section describes how to configure the PXE boot options using the PXESelect utility.
2.4.1 Navigating the PXESelect Utility
Use the following methods to navigate the PXESelect utility:

 Press the up and down arrows on the keyboard to move through and select menu options or configuration fields.
If multiple adapters are listed, use the up and down arrows to scroll to the additional adapters.
 Press the Tab key to move to the next field or to select a row in a configuration dialog. Press shiftbar-Tab key to
move to the previous field.
 Press Enter to accept a selection, select a menu option, or change a configuration default.
 Press Esc to return to the previous menu or page, cancel a selection or dialog box, or exit the utility.
Broadcom
- 14 -
December 30, 2016 Using the PXESelect Utility
2.4.2 Running the PXESelect Utility
To run the PXESelect utility, start or restart the computer. When prompted, press Ctrl-P. If you are running the
PXESelect utility with multiple adapters, all of the adapters are displayed when you start the utility. For example:
Press <Ctrl><P> for PXESelect(TM)Utility
OCe14102B-UM NIC#0 Port#1 Base 0x00000380001A0000 @ Bus:1B Dev:00 Fun:00

OCe14102B-UM NIC#0 Port#2 Base 0x00000380001E0000 @ Bus:1B Dev:00 Fun:00
- Initializing ...Done.
The PXE Configuration menu appears after the boot BIOS initializes to begin the PXE configuration.
NOTE A UEFI-capable system typically does not display the prompt for
running the PXESelect utility unless it is configured for legacy booting.
See your system configuration manual for information on performing
a legacy boot. All configurations that can be performed in the
PXESelect utility can instead be performed in the UEFI configuration
utility. For more information on configuring UEFI, see Chapter 11,
Configuring UEFI for Ethernet.
2.4.3 Setting Up a PXE Bootable Network
After the PXE boot BIOS is initialized, you can use the PXESelect utility to set up a PXE bootable network by
configuring the adapters.
To configure adapters for a PXE boot:
1. At the following Controller Selection Menu), use the Tab key to select the adapter you want to configure and press
Enter.
Figure 2 Controller Selection Menu
NOTE The Controller Selection Menu appears only if two or more adapters
are connected.
The following Controller Configuration dialog appears.
Figure 3 Controller Configuration Dialog
Depending on the adapter, the following options are available:

— MultiChannel Mode – Allows you to access up to eight virtual network interfaces. For more information on
Multichannel mode, see Section 2.4.5, Configuring Universal Multichannel.
Broadcom
- 15 -
NOTE If you are using a Lenovo System x adapter, see Section 2.4.6,
Configuring Multichannel for Lenovo System x Adapters, for more
information on Multichannel mode.
— Advanced Mode Support – Enables you to run Advanced mode–aware drivers. For more information on
configuring Advanced mode, see Section 2.4.7, Advanced Mode Support.
— Personality – Allows you to select the protocols that can be configured on an adapter. For more information
on adapter personality, see Section 2.4.8, Personality Option.
2. After you set the options in the Controller Configuration dialog, select Save and press Enter.
3. To proceed, select Continue and press Enter.
The Port Selection Menu (Figure 4) appears.
4. Select the port you want to configure and press Enter.
Figure 4 Port Selection Menu
NOTE The Port Selection Menu appears if two or more ports are connected.
Depending on the installed adapter and the Multichannel mode setting, proceed to the following sections:
— If MultiChannel Mode is disabled, or it is not supported, see Section 2.4.4, Configuring Ports If UMC Is
Disabled or Not Supported, for additional configuration information.
— If MultiChannel Mode is enabled, see Section 2.4.5, Configuring Universal Multichannel, for additional
configuration information.
— If MultiChannel Mode is enabled and you are using Lenovo System x adapters, see Section 2.4.6, Configuring
Multichannel for Lenovo System x Adapters, for additional configuration information.
2.4.4 Configuring Ports If UMC Is Disabled or Not Supported
NOTE If UMC is enabled, for information on configuring UMC, see

Section 2.4.5, Configuring Universal Multichannel. If you are using a
Lenovo System x adapter, see Section 2.4.6, Configuring Multichannel
for Lenovo System x Adapters.
If UMC is disabled, or if it is not supported, the Port Configuration dialog (Figure 5) appears after you select a port in
the Port Selection Menu (Figure 4).
Broadcom
- 16 -
Figure 5 Port Configuration Dialog
NOTE Logical Link Status appears as N/A for storage functions.

The Port Configuration dialog enables you to perform the following tasks:
 Configure the PXE boot support
 Configure SR-IOV
 Configure the PXE VLAN ID and Priority
 Identify ports
 Erase the port and adapter configuration
2.4.4.1 Configuring the PXE Boot Support

To configure the PXE boot support:
1. On the Port Configuration dialog, use the Tab key to select the PXE Boot Support. A pop up appears.
2. Select Enabled or Disabled and press Enter.
3. Select Save and press Enter.
NOTE During system startup, the PXE contacts the DHCP server for an IP
address to boot from the network.
2.4.4.2 Configuring SR-IOV

If the system BIOS supports SR-IOV, you can enable it on the adapter. SR-IOV support can be enabled only if UMC is
disabled or not supported. For more information on SR-IOV configuration, see the appropriate Emulex drivers for
OneConnect® adapters user guide.
To configure SR-IOV:
1. On the Port Configuration dialog, use the Tab key to select SR-IOV. A pop up appears.
2.4.4.3 Configuring the PXE VLAN ID and Priority

To configure a PXE VLAN ID and set the priority level:
1. On the Port Configuration dialog, select Configure PXE VLAN ID/Priority and press Enter. The Configure PXE VLAN
ID/Priority menu (Figure 6) appears.
Broadcom
- 17 -
Figure 6 Configure PXE VLAN ID/Priority Menu
2. Use the Tab key to select PXE VLAN Support. A pop up appears.
a. For PXE VLAN Support, select Enabled and press Enter.
b. For the PXE VLAN ID, select a number from 0 to 4094 and press Enter.
c. For the PXE VLAN Priority level, select a number from 0 to 7 and press Enter. This unique value assigns a
priority to outbound packets containing a specified VLAN ID. Valid values range from 0 to 7, with 0 the
highest priority level.
After you exit the PXESelect utility, the system must reboot for the configuration to take effect.
2.4.4.4 Physically Identifying the Port

To physically determine which port you are configuring by causing the link and activity LEDs of that port to blink:
1. On the Port Configuration dialog, select Port Identification and press Enter. The following Port Identification pop
up appears.
Figure 7 Port Identification Pop Up
2. The LEDs on the adapter begin blinking. The selected port’s LED status indicators blink on the adapter until you
select Done on this pop up and press Enter.
NOTE Not all adapters have externally–visible LEDs. If you are using an add-in
card in a blade server environment, port identification is not
supported.
2.4.4.5 Erasing Ports and Adapter Configurations
NOTE On OCe11100-series adapters, if you select the Erasing Ports and

Adapter Configurations setting, all previous configuration settings are
returned to their factory default settings except for the current
personality selection. Performing this action ensures a clean
environment for new configuration settings to take effect.
To erase the ports and adapter configuration:
1. On the Port Configuration dialog, select Erase Configuration and press Enter. The system displays a warning
asking if you want to erase the current configuration for all ports of the adapter.
2. Press Y to delete the configuration. You will receive another warning asking you to confirm the permanent
removal of the configuration.
Broadcom
- 18 -
3. Press Y to delete the configuration.

To exit the PXESelect utility after erasing the ports and adapter configuration:
1. Follow the instructions on the bottom of the individual menu until you are prompted to exit.
2. Press Y to exit. Depending on the settings that were changed, a reboot may be necessary.
NOTE For older systems, depending on the memory allocation method

supported, the PXESelect utility automatically reboots even when
there are no changes made to the system.
2.4.5 Configuring Universal Multichannel
UMC provides the ability to configure multiple physical functions or I/O channels for each physical adapter port. For
more information on UMC support, refer to the Emulex Universal Multichannel Reference Manual.
NOTE If UMC is enabled and the adapter supports Virtual Fabric mode or
Unified Fabric Protocol mode, see Section 2.4.6, Configuring
Multichannel for Lenovo System x Adapters, for more information. If
UMC is disabled or not supported on the adapter, see Section 2.4.4,
Configuring Ports If UMC Is Disabled or Not Supported.
If UMC is enabled, you must configure the minimum and maximum
bandwidth settings for iSCSI and FCoE storage functions in the NIC
BIOS before they can be configured further from their respective
utilities (iSCSI or FCoE BIOS). Otherwise, the Logical Link for that
function will be shown as down, and you will not be able to log in to
targets or find LUNs behind those targets.
NOTE The PXE VLAN is not supported in UMC environments.

UMC functionality is supported on Emulex OneConnect adapters
running in 10Gb Ethernet mode only. UMC is not supported in 1GbE
mode.
If the Multichannel mode has changed since the last boot, a reboot
will occur when you exit the PXESelect utility.
To view the Multichannel Configuration dialog:
1. From the Port Selection Menu (Figure 4), select a port to configure and press Enter. The following Multichannel
Configuration dialog (Figure 8) appears.
Broadcom
- 19 -
Figure 8 Multichannel Configuration Dialog
NOTE The Logical Link Status appears as N/A for storage functions.
SR-IOV support can be enabled only if UMC is disabled.
If the system does not support UMC, it appears as N/A on the Switch
Independent Mode Configuration dialog).
2. From the Multichannel Configuration dialog (Figure 8), you can perform the following tasks:
— Configure PXE boot support – See Section 2.4.4.1, Configuring the PXE Boot Support, for instructions.
— Configure PXE VLAN ID/Priority – See Section 2.4.4.3, Configuring the PXE VLAN ID and Priority, for
instructions.
— Identify ports – See Section 2.4.4.4, Physically Identifying the Port, for instructions.
— Erase the port and adapter configuration – See Section 2.4.4.5, Erasing Ports and Adapter Configurations, for
instructions.
— Configure the minimum and maximum bandwidth for each channel – See Section 2.4.5.1, Configuring
Minimum and Maximum Bandwidth, for instructions.
— Configure the LPVID for each channel – See Section 2.4.5.2, Configuring LPVID, for instructions.
NOTE Your adapter or system may not support all UMC options.
2.4.5.1 Configuring Minimum and Maximum Bandwidth

To configure bandwidth:
1. On the MultiChannel Configuration dialog, use the Tab key to select Minimum Bandwidth or Maximum
Bandwidth.
— The Minimum Bandwidth value is the least amount of bandwidth that the function can provide. It is
represented as a percentage. The Minimum Bandwidth value must be less than or equal to the Maximum
Bandwidth value. The total of the Minimum Bandwidth values for all enabled functions on that port must be
equal to 100.
NOTE A Minimum Bandwidth value of 0 is a valid value. If all of the partitions’

Minimum Bandwidth values are zero, the bandwidth is distributed
equally among the current active partitions. If a specific partition’s
Minimum Bandwidth and Maximum Bandwidth values are 0, that
partition’s logical link will be brought down.
— The Maximum Bandwidth value is the greatest amount of bandwidth that the function can provide. It is
represented as a percentage.
2. Enter the value for the specified option and press Enter.
Broadcom
- 20 -
2.4.5.2 Configuring LPVID

The LPVID is used to enforce a VLAN ID on all traffic originating from an IP address, channel, or PCI function. If the
operating system for that PCI function has set up a VLAN ID, then the operating system–configured VLAN ID takes
precedence over the LPVID for transmit packets, while the operating system–configured VLAN ID and LPVID-tagged
packets will both be received. If the operating system has not set up any VLAN IDs, then the LPVID is used for tagging.
NOTE LPVID and user-configured VLAN IDs from the operating system must
be different.
LPVIDs also must be configured on the switch port.
Each LPVID must be unique and is relevant for NIC traffic only. The LPVID is not supported for storage functions. For
iSCSI storage functions, you must configure a VLAN ID through iSCSISelect or through the host. For more information,
see Section 9.3.2, Configuring VLAN ID and VLAN Priority.
During the PXE boot, when the UNDI Driver (BIOS) is functional, the PXE VLAN is used. However, after the NIC driver is
operational, the LPVID is used.
NOTE The PXE VLAN is not supported in UMC environments.

For example:
PXE Install OS
PXE Server configured with VLAN 5
PXE VLAN=5
LPVID for function 0=5
To configure LPVID:
1. On the MultiChannel Configuration dialog, use the Tab key to select LPVID. A dialog box appears.
2. Enter a value and press Enter. The LPVID range is 2 to 4094. A value of 0 disables the LPVID.
2.4.6 Configuring Multichannel for Lenovo System x Adapters
NOTE This section pertains to Emulex OneConnect adapters that support

Multichannel for Lenovo System x Virtual Fabric or UFP only.
If you want to enable Multichannel on Lenovo System x adapters, you must select a Multichannel mode.
To configure Multichannel:
1. From the Controller Configuration dialog (Figure 9), use the Tab key to select Multichannel Mode. A pop up
appears.
Figure 9 Controller Configuration Dialog - Lenovo System x Adapters
2. Select one of the following settings and press Enter:

— Switch Independent Mode
Broadcom
- 21 -
— IBM Virtual Fabric Mode

— IBM Unified Fabric Protocol Mode
— Disabled
NOTE For more information on the available Multichannel options, see

Section 2.4.6.1, Multichannel Modes.
4. To proceed, select Continue and press Enter.
With the Multichannel option selected, you can now configure Multichannel support. See Section 2.4.6.2,
Multichannel Configuration for Lenovo System x, for more information.
2.4.6.1 Multichannel Modes
NOTE The following modes are available on Lenovo System x adapters and
systems that support IBM Virtual Fabric mode and IBM Unified Fabric
Protocol mode only.
Multichannel for Lenovo System x is supported on Emulex
OneConnect adapters running in 10GbE mode only. Multichannel for
Lenovo System x is not supported in 1GbE mode.
Emulex OneConnect OCe11100-series adapters support a maximum
of four PFs per port in all Multichannel modes.
A Lenovo System x Virtual Fabric–enabled switch provides the ability to configure an LPVID for a virtual channel or I/O
channel on an adapter port. If Multichannel for Lenovo System x is supported on the system, the PXESelect utility
enables you to select one of the following modes:
 IBM Virtual Fabric Mode – Select this mode if an Emulex OneConnect adapter is attached to an Lenovo System x
Virtual Fabric–enabled switch.
 IBM Unified Fabric Protocol Mode – Select this mode if an Emulex OneConnect adapter is attached to a Lenovo
System x UFP–enabled switch.
NOTE Some Lenovo System x switches support both IBM Unified Fabric
Protocol mode and IBM Virtual Fabric mode.
 Switch Independent Mode – Select this mode if you are using a switch other than a Lenovo System x Virtual
Fabric or UFP-enabled switch. For more information on configuring Multichannel, see Section 2.4.5, Configuring
Universal Multichannel.
2.4.6.2 Multichannel Configuration for Lenovo System x

Multichannel for Lenovo System x provides the ability to configure multiple PCI functions or I/O channels for each
physical adapter port.
NOTE Setting up Multichannel for IBM Virtual Fabric mode or IBM Unified
Fabric Protocol mode depends on cooperation with adjacent switches.
For information on configuring Multichannel for Lenovo System x if
Switch Independent mode is enabled, see Section 2.4.5, Configuring
Universal Multichannel.
To view the configuration dialog:
1. From the Port Selection Menu (Figure 4), select the port you want to configure and press Enter. The configuration
dialog appears.
Broadcom
- 22 -
If you configure Multichannel for Lenovo System x on adapters that support IBM Virtual Fabric mode and IBM
Unified Fabric Protocol mode, the configuration dialog will depend on the Multichannel mode that has been
selected.
NOTE For illustration purposes, the dialogs in this section are for a system
with IBM Virtual Fabric mode enabled.
Figure 10 Virtual Fabric Mode Configuration Dialog

SR-IOV support can be enabled only if Multichannel mode is disabled.
If the system does not support Multichannel for Lenovo System x, it
appears as N/A on the configuration dialog.
The SVID, or Outer VLAN ID, appears in IBM Virtual Fabric mode and
IBM Unified Fabric Protocol mode. This value is provided by the
Lenovo System x switch and will appear if the protocol modes are
configured on the switch and the adapter. If the protocol modes are
not configured, a value of N/A appears.
2. From the configuration dialog, you can perform the following tasks:
— Configure PXE boot support – See Section 2.4.4.1, Configuring the PXE Boot Support, for instructions.
— Configure PXE VLAN ID/Priority – See Section 2.4.4.3, Configuring the PXE VLAN ID and Priority, for
instructions.
— Identify ports – See Section 2.4.4.4, Physically Identifying the Port, for instructions.
— Erase the port and adapter configuration – See Section 2.4.4.5, Erasing Ports and Adapter Configurations, for
instructions.
— Configure the LPVID for each channel – See Section 2.4.5.2, Configuring LPVID, for instructions.
NOTE An LPVID is optional in IBM Virtual Fabric mode, but it is required for
every function in Switch Independent mode.
If IBM Virtual Fabric mode or IBM Unified Fabric Protocol mode is
enabled, you must configure the minimum and maximum bandwidth
settings on the switch.
Broadcom
- 23 -
2.4.7 Advanced Mode Support
Advanced mode provides driver compatibility. With Advanced mode enabled, you can run Advanced mode-aware
drivers that provide the advanced capabilities listed in the following table. With Advanced mode disabled, you can run
older legacy inbox drivers that are not Advanced mode-aware with the latest firmware versions.
NOTE Advanced mode support is enabled by default on OCe11100-series

two-port and four-port adapters. On four-port adapters, the Advanced
mode setting is not provided in the PXESelect utility. The Advanced
mode setting on these platforms is implicitly enabled, and Advanced
mode-aware drivers must be installed. Compatibility with legacy
drivers requires that Advanced mode support be disabled on two-port
adapters.
Table 1 Advanced Mode Capabilities (by Operating System)
Advanced Mode Disabled

Operating System Advanced Mode Enabled
(Legacy Mode)
Windows 16 RSS queues 4 RSS Queues
NOTE Supported on Windows Server 2008 R2 and
later versions only.
VMQ lookahead split Lookahead split is silently ignored. A small
performance penalty for VMQs may occur.
NOTE VMQs are supported on Windows Server
2008 R2 and later versions only.
Linux and Citrix 16 RSS queues 4 RSS queues
VFs and PFs can be increased up to 30
VMware ESXi For both 1500 and 9000 MTU: 1500 MTU – 8 NetQueues per PF in non-VFA and 4
16 NetQueues per PF in non-VFA NetQueues per PF in VFA.
4 NetQueues per PF in VFA 9000 MTU – 4 NetQueues per PF in both VFA and
non-VFA
To configure Advanced mode support:

1. From the following Controller Configuration dialog (Figure 11), use the Tab key to select Advanced Mode
Support. A pop up appears.
Figure 11 Controller Configuration Dialog – Advanced Mode Support Selection

Broadcom
- 24 -
December 30, 2016 PXE Boot Parameters Default Values
2.4.8 Personality Option
The personality reflects the adapter protocols. This option specifies a list of available protocols that can be configured
on an adapter. Depending on the personalities for which the adapter is licensed, one or more of the following
selections appear:
 NIC
 iSCSI
 FCoE
The menu displays the available personalities only, including both free and licensed personalities.
The NIC personality implies that all of the enabled functions provide NIC/TOE functionality.
iSCSI and FCoE personalities are enabled on one function per adapter port and include NIC functionality on the other
enabled functions. Only one storage protocol is allowed on each port.
To select the personality of the adapter:
1. From the Controller Configuration dialog (Figure 12), use the Tab key to select Personality and press Enter. A
menu appears.
Figure 12 Controller Configuration Dialog – Personality Selection
2. Select NIC, iSCSI, or FCoE and press Enter.

NOTE If the Personality setting has changed since the last boot, a reboot will
occur when you exit the PXESelect utility.
2.5 PXE Boot Parameters Default Values
The default settings for the PXE Boot parameters are listed in the following table.
Table 2 PXE Boot Parameter Default Values
Parameter Default Value Valid Values

Advanced Mode Enabled two-port and four-port adapters Enabled
Disabled
PXE Boot Support The default for this parameter varies Enabled
depending on the vendor configuration Disabled
SR-IOV Disabled Enabled
Disabled
VLAN Support Disabled Enabled
Disabled
VLAN ID 0 0 to 4094
Broadcom
- 25 -
Table 2 PXE Boot Parameter Default Values (Continued)

VLAN Priority 0 0 to 7
Multichannel Mode The default for this parameter varies For Emulex adapters:
depending on the vendor configuration  Enabled
 Disabled
For Lenovo System x adapters:
 IBM Virtual Fabric Mode
 IBM Unified Fabric Protocol Mode
 Switch Independent Mode
 Disabled
Minimum Bandwidth 0% Must have a total of 100% across all ports
Maximum Bandwidth 0% From the minimum bandwidth value up to
100% (inclusive)
LPVID 0 2 to 4094
Broadcom
- 26 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 3: Configuring PXE Boot for NIC on OCe14000-Series Adapters
December 30, 2016 Pre-OS
Chapter 3: Configuring PXE Boot for NIC on OCe14000-Series

Adapters
NOTE This section applies only to Emulex OCe14000-series adapters. See
Chapter 2, Configuring the PXE Boot for NIC on OCe11100-Series
Adapters, for information specific to those adapters.
For a Dell OCe14000-based adapter, see Appendix G, Configuring PXE
Boot for NIC on Dell OCe14000-Based Systems.
This section describes using and configuring PXE to boot computers using a network interface independent of
available data storage devices (such as hard disks) or installed operating systems.
The PXE protocol is a combination of DHCP and TFTP with subtle modifications to both. DHCP locates the appropriate
boot server or servers, and TFTP downloads the initial bootstrap program and additional files.
Network booting enables you to perform the following tasks:
 Boot diskless systems such as thin clients and dedicated systems.
 Deploy software and operating systems for your systems.
 Automate system maintenance, such as backups.
 Automate system checking, such as virus scanning.
 Ensure system security.
3.1 Pre-OS
PXE can be used in a pre-OS environment. Pre-OS is the process of loading a small operating environment to perform
a client management task before loading the final operating system from the local hard drive. For example, with a
pre-OS you can scan the hard drive for viruses. This guarantees that the client is not infected before it starts. Another
example is the use of this feature by WDS to install operating systems on local disks or boot from SAN disks.
3.2 PXE Boot Process
After PXE boot is enabled in the system UEFI and BIOS, the PXE client can boot up and start up the PXE boot ROM. This
is the boot code physically located on the NIC adapter.
Figure 13, PXE Boot Process shows the boot process.
NOTE To enable or disable PXE boot, it must be enabled or disabled in the

system UEFI and BIOS; Refer to the documentation that accompanied
the server for more information.
Broadcom
- 27 -
December 30, 2016 Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016
Figure 13 PXE Boot Process
1. The PXE boot ROM sends a DHCP request extended with PXE specific options (step 1 in the figure).
2. The DHCP responses contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot server lists
(steps 2 through 5).
3. The PXE client attempts to download the specified NBP over TFTP from one of the specified boot servers (steps 6
and 7).
4. The PXE client executes the downloaded NBP (steps 8 and 9).
NOTE If any of these steps fail, the boot process typically continues using the
next available device in the boot sequence, depending on the system
configuration and boot order.
3.3 Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, 2012
R2, and 2016
image on the server. The current versions of Windows Server 2008 and Windows Server 2008 R2 do not include
network drivers for the Emulex adapter; however, Windows Server 2012, 2012 R2, and 2016 include the network driver
for the Emulex adapter.
Broadcom
- 28 -
December 30, 2016 Remotely Installing with PXE for Linux and Citrix Servers
To add the image and installation using the driver with the Remote Installation Service Setup:
Select Start Menu > Programs > Administrative Tools > Remote Installation Services Setup
In addition to the network driver for the Emulex adapter, you must configure the following services to use PXE for
remote installations:
 DHCP server
 Remote Installation Services
 Windows Deployment Services
Microsoft provides extensive documentation on deploying its operating systems for remote installations, and
different setups may be required depending on your individual implementation. Microsoft provides step-by-step
guides for its Windows Deployment Services for configuring the server, adding images, and installing an operating
system. It also includes instructions for more advanced tasks like creating multicast transmissions, creating custom
images, and performing an unattended installation.
For detailed information on deploying and managing remote installations on Windows Server 2008, Windows Server
2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016, see the Microsoft website and
visit Microsoft TechNet. Search on the bulleted terms above to access Microsoft's wide-ranging documentation on
these subjects.
3.4 Remotely Installing with PXE for Linux and Citrix Servers
Linux allows for PXE installation over a network using the NFS, TFTP, or HTTP protocols. If the system to be installed
contains an Emulex NIC or adapter with PXE Boot support, it can be configured to boot from files on another
networked system rather than local media.
The Linux distributions provide extensive documentation on deploying and managing remote installations of the
Linux operating system using PXE. See the distribution's documentation for instructions on deploying a PXE
installation over the network.
image on the server. The current Linux distribution may or may not include network drivers for Emulex adapters. If it
does, the driver may need to be added to the operating system’s installation image, or added during installation. See
the distribution's documentation for instructions on adding drivers during installation.
3.5 Using the PXESelect Utility
This section describes how to configure the PXE boot options using the PXESelect utility.
NOTE For Dell OCe14000-based adapters, see Appendix G, Configuring PXE

Boot for NIC on Dell OCe14000-Based Systems, for information on
using the PXESelect utility.
3.5.1 Navigating the PXESelect Utility

 Press the up or down arrows on the keyboard to move through and select menu options or configuration fields. If
multiple adapters are listed, use the up and down arrows to scroll to the additional adapters.
 Press the left or right arrows on the keyboard to move through and select setting options.
Broadcom
- 29 -
 Press Enter to accept a selection, select a menu option, or change a configuration default.
 Press the F7 key to save the changes on the screen.
3.5.2 Running the PXESelect Utility
To run the PXESelect utility, start or restart the computer. When prompted, press Ctrl-P. If you are running the

NOTE A UEFI-capable system typically does not display the prompt for
running the PXESelect utility unless it is configured for legacy booting.
See your system configuration manual for information on performing
a legacy boot. All configurations that can be performed in the
PXESelect utility can instead be performed in the UEFI configuration
utility. See Chapter 11, Configuring UEFI for Ethernet, for more
information.
3.5.3 Setting Up a PXE Bootable Network
To configure adapters for PXE boot:
1. From the following Controller List (Figure 14), use the up or down arrow keys to select the adapter you want to
configure and press Enter.
Figure 14 Controller List
NOTE The Controller List appears only if two or more adapters are
connected.
The following Controller Configuration dialog (Figure 15) appears.
Broadcom
- 30 -
Depending on the adapter, one or more of the following items are displayed:
— Controller Name – Displays the adapter’s name.
— Firmware Version – Displays the current firmware version.
— IPL Version – Displays the IPL version.
— MultiChannel – If UMC is enabled, you can access up to 16 virtual network interfaces. For more information
on UMC, see Section 3.5.5, Configuring Universal Multichannel.
NOTE If you are using a Lenovo System x adapter, see Section 3.5.6,
information.
On HP systems, you can select either Disable or Flex-10 for the
MultiChannel setting. If Flex-10 is selected, the settings are only
displayed and cannot be configured.
— Personality – This option specifies a list of available protocols that can be configured on an adapter. For
more information on adapter personality, see Section 3.5.4.1, Configuring Personality.
— SR-IOV – If the system BIOS supports SR-IOV, you can enable it if UMC is disabled or it is not supported. For
more information on SR-IOV configuration, see Section 3.5.4.2, Configuring SR-IOV.
— RoCE Profile – This setting is available only if the Personality is set to NIC+RoCE. For more information, see
Section 3.5.4.1.2, Configuring the RoCE Profile.
NOTE RoCE is available as Technical Preview only. Do not use RoCE in a

production environment.
— NIC Mode – This setting is available only if SR-IOV is enabled, Personality is set to NIC, and a two-port Emulex
OCe14000-series adapter is in use. For more information, see Section 3.5.4.3, Configuring NIC Mode.
2. After you set the options in the Controller Configuration dialog, press the F7 key to save the current settings.
3. Press F6 key to proceed.
NOTE To erase the current configuration, press the F8 key. See

Section 3.5.4.9, Erasing Ports and Adapter Configurations, for more
information.
The following Port Selection Menu appears.
Broadcom
- 31 -
NOTE The Port Selection Menu appears only if two or more ports are
connected.
4. Select the port you want to configure and press Enter. The Port Menu appears.
Depending on the installed adapter and the Multichannel setting, proceed to the following sections:
— If UMC is disabled or not supported, see Section 3.5.4, Configuring Ports If UMC Is Disabled or Not Supported,
for additional configuration information.
— If UMC is enabled, see Section 3.5.5, Configuring Universal Multichannel, for additional configuration
information.
— If UMC is enabled and you are using Lenovo System x adapters, see Section 3.5.6, Configuring Multichannel
for Lenovo System x Adapters, for additional configuration information.
3.5.4 Configuring Ports If UMC Is Disabled or Not Supported
NOTE If UMC is enabled, see Section 3.5.5, Configuring Universal

Multichannel. If you are using a Lenovo System x adapter, see
Section 3.5.6, Configuring Multichannel for Lenovo System x Adapters.
3.5.4.1 Configuring Personality

The personality reflects the adapter’s protocols. This option specifies a list of available protocols that can be configured
selections may appear:
 NIC – Implies that all the enabled functions provide NIC functionality
 iSCSI or FCoE – These personalities are enabled on one function per adapter port and include NIC functionality
on the other enabled functions
NOTE Only one of each storage protocol is allowed on each port.
NOTE Changing the personality to iSCSI or FCoE on one physical port also
changes the personality on all other ports from the same adapter.
 NIC+RoCE – Implies that all the enabled functions provide RoCE functionality.
 Custom – For information about custom personalities, see Section 3.5.4.1.1, Configuring the Custom Personality
Selection.
NOTE If NIC+RoCE is enabled, the RoCE Profile selection is available.

If SR-IOV is enabled, the NIC+RoCE personality setting is unavailable.
RoCE is supported on Windows and Linux only.
NOTE Two iSCSI functions and two FCoE functions are not allowed on a
single port.
Broadcom
- 32 -

1. From the Controller Configuration dialog (Figure 15), use the up or down arrow keys to select Personality.
2. Use the left or right arrow keys to select the desired personality.
3. Press the F7 key to save.
3.5.4.1.1 Configuring the Custom Personality Selection

The OCe14000-series adapters support the Custom personality mode when UMC is disabled. The OCe14000-series
adapters support NIC, iSCSI, and FCoE protocols on a single port. While the normal NIC, iSCSI, and FCoE personalities
support only NIC, NIC+iSCSI, or NIC+FCOE configuration on both ports, the Custom mode allows support for NIC,
iSCSI, and FCoE on both ports.
NOTE When using the Custom personality mode with UMC disabled, only
three functions are available on each port.
With UMC disabled, each port can be configured with one of the following configurations:
 One NIC function
 One NIC function and one iSCSI function
 One NIC function and one FCoE function
 One NIC function, one iSCSI function, and one FCoE function
NOTE Two of the same storage protocols are not supported on a single port.
Two NIC functions are not supported on a single port.
Therefore, on a 2-port controller you can potentially have 6 functions, while a 4-port controller can have up to 12
functions. The function-to-port mapping is detailed in the following two tables.
Table 3 Function-to-Port Mapping for 4-Port OCe14000-Series Adapters
Port 0 Port 1 Port 2 Port 3

0 1 2 3
4 5 6 7
8 9 10 11
Table 4 Function-to-Port Mapping for 2-Port OCe14000-Series Adapters
Port 0 Port 1
0 1
2 3
4 5
If you enable Custom mode, the personality may revert to NIC, iSCSI, or FCoE if an actual Custom configuration is not
defined. If Custom mode is enabled, the following conditions apply:
 If you leave all functions set to NIC, the configured personality is automatically switched from Custom to NIC.
 If you leave the functions configured the same as they would be for iSCSI, the configured personality is
automatically switched from Custom to iSCSI.
 If you leave the functions configured the same as they would be for FCoE, the configured personality is
automatically switched from Custom to FCoE.
Broadcom
- 33 -
NOTE If higher order functions have been enabled and you want to disable
them, you must first enable the Custom personality before the option
to disable the functions appears.
To select the Custom personality:
1. From the Controller Configuration dialog (Figure 15), use the up or down arrow keys to select the Personality
option.
2. Use the left or right arrow keys to select the Custom personality.
3. Press the F6 key to continue. The Port Selection Menu (Figure 16) appears.
4. On the Port Selection Menu, select the appropriate port. The following Port Menu appears.
Figure 17 Port Menu (UMC Disabled)
5. On the Port Menu, select NIC Configuration and press Enter. The following Channels List appears.
Figure 18 Channels List (UMC Disabled)
6. On the Channels List, select the channel you want to configure and press Enter. The following Channel
Configuration dialog appears.
Figure 19 Channel Configuration Dialog (UMC Disabled)
7. On the Channel Configuration dialog, use the up or down arrow keys to select Protocol.
8. Select the desired personality for the appropriate function using the arrow keys.
Broadcom
- 34 -
NOTE The iSCSI and FCoE personalities can only be enabled on one function
per adapter port.
3.5.4.1.2 Configuring the RoCE Profile
NOTE The RDMA application profile setting is available only when the
NIC+RoCE personality is selected.
Virtualization mode is set to None.
The RDMA application profile settings allow you to select the appropriate configuration for the particular system
setup. The RDMA application profile choices include:
 RoCE-1 – Not supported.
 RoCE-2 – The RoCE-2 profile supports Windows SMB Direct, Linux iSER, NFS-RDMA, and VM Migration.
To select a RoCE Profile:
1. From the Controller Configuration dialog (Figure 15), select the NIC+RoCE personality.
2. Use the up or down arrow keys to select RoCE Profile.
3. Use the left or right arrow keys to select the desired profile and press Enter.

If the system BIOS supports SR-IOV, you can enable it on the adapter. SR-IOV support can be enabled only if
Multichannel is disabled or not supported.
NOTE If SR-IOV is enabled, the NIC+RoCE personality setting is unavailable.

1. From the Controller Configuration dialog (Figure 15), use the up or down arrow keys to select SRIOV.
2. Use the left or right arrow keys to enable or disable SR-IOV.
For more information on SR-IOV configuration, see the appropriate Emulex driver user guide for OneConnect
adapters.
3.5.4.3 Configuring NIC Mode
NOTE This setting is available on two-port OCe14000-series adapters only if

SR-IOV is enabled and the personality is set to NIC.
This setting allows you to control the VF count on a two-port OCe14000-series adapter. The choices include:
 NIC – The VF count is restricted to 31 VFs per port and QoS is supported for those VFs.
NOTE For two-port OCe14000B-series adapters only, this setting supports up

to 63 VFs per port.
 NIC-ETS Disabled – The VF count is set to 63 VFs per port but QoS is not supported for those VFs.
Broadcom
- 35 -
NOTE This setting is not supported on OCe14000B-series adapters.

To select the NIC mode:
1. From the Controller Configuration dialog (Figure 15), ensure that the NIC personality is selected and SR-IOV is
enabled.
2. Use the up or down arrow keys to select the NIC mode.
3. Use the left or right arrow keys to select the desired setting and press Enter.
3.5.4.4 Loading Default Settings

If you want to erase the current configuration, from the Controller Configuration dialog (Figure 15) press the F8 key.
See Section 3.5.4.9, Erasing Ports and Adapter Configurations, for more information.
3.5.4.5 Selecting a Port

After you set the options in the Controller Configuration dialog (Figure 15), save your changes. To save the current
settings, press the F7 key.
To proceed to the Port Selection Menu (Figure 16):
1. From the Controller Configuration dialog (Figure 15), press the F6 key. The Port Selection Menu (Figure 16)
appears.
2. Select the port you want to configure and press Enter. The Port Menu (Figure 17) appears.
The Port Menu enables you to perform the following tasks:
 View NIC configuration information – See Section 3.5.4.6, Viewing NIC Configuration Information, for more
information.
 Configure boot options – See Section 3.5.4.7, Configuring Boot Options, for instructions.
 Configure port options – See Section 3.5.4.8, Configuring Port Options, for instructions.
3.5.4.6 Viewing NIC Configuration Information

To view the NIC configuration information:
1. From the Port Menu (Figure 17), use the up or down arrow keys to select NIC Configuration and press Enter.
Depending on the currently selected Personality setting, one of the following dialogs appear.
— If the Personality setting is set to iSCSI or FCoE, the Channels List (Figure 18) appears.
Select a channel using the up or down arrow keys and press Enter. The Channel Configuration dialog
(Figure 19) appears.
— If the Personality setting is set to NIC or NIC+RoCE, the Channel Configuration dialog (Figure 24) appears.
2. From the Channel Configuration dialog, you can view the following information:
— Function number
— Protocol
— Minimum bandwidth (Min BW)
— Maximum bandwidth (Max BW)
— Permanent and virtual MAC addresses
— Logical link status
— Assigned LPVID
— SR-IOV status
Broadcom
- 36 -
3.5.4.7 Configuring Boot Options

To view the Boot Configuration dialog:
1. From the Port Menu (Figure 17), select Boot Configuration and press Enter. The following Boot Configuration
dialog appears.
Figure 20 Boot Configuration Dialog
From the Boot Configuration dialog, you can configure PXE boot support.
3.5.4.7.1 Configuring PXE Boot Support

To configure PXE boot support:
1. On the Boot Configuration dialog (Figure 20), use the left or right arrow keys to enable or disable the PXE Boot
setting.
NOTE If PXE boot is enabled, during system startup PXE contacts the DHCP
server for an IP address to boot from the network.
3.5.4.8 Configuring Port Options

To view the Port Configuration dialog:
1. From the Port Menu (Figure 17), select Port Configuration and press Enter. The following Port Configuration
dialog appears.
2. From the Port Configuration dialog, you can perform the following tasks:
— View the physical link speed and link status.
— Configure PXE VLAN, including the PXE VLAN ID and priority – See Section 3.5.4.8.1, Configuring PXE VLAN,
for instructions.
— Identify the port – See Section 3.5.4.8.2, Physically Identifying the Port, for instructions.
3.5.4.8.1 Configuring PXE VLAN

To enable PXE VLAN:
1. On the Port Configuration dialog (Figure 21), use the up or down arrow keys to highlight the current PXE VLAN
setting.
Broadcom
- 37 -
2. Use the left or right arrow keys to set PXE VLAN to enabled.
To configure a PXE VLAN ID:
1. On the Port Configuration dialog (Figure 21), use the up or down arrow keys to highlight the current PXE VLAN ID
setting.
2. Use the left or right arrow keys to select a number from 1 to 4094.
To set the priority level:
1. On the Port Configuration dialog (Figure 21), use the up or down arrow keys to highlight the current PXE VLAN
Priority setting.
2. Use the left or right arrow keys to select a number from 0 to 7.
This unique value assigns a priority to outbound packets containing a specified VLAN ID. Valid values range from
0 to 7, with 0 being the highest priority level.
After you exit the PXESelect utility, the system will reboot for the configuration to take effect.
3.5.4.8.2 Physically Identifying the Port

1. On the Port Configuration dialog (Figure 21), press the F5 key.
2. The LEDs on the adapter begin blinking. The selected port’s LED status indicators blink on the adapter for
approximately 15 seconds.
supported.
3.5.4.9 Erasing Ports and Adapter Configurations
NOTE If this setting is selected, all previous configuration settings are

returned to their factory default settings. Performing this action
ensures a clean environment for new configuration settings to take
effect.
1. On the Controller Configuration dialog (Figure 15), press the F8 key to restore the factory default settings. The
system displays a warning asking if you want to erase the current configuration for all ports of the adapter.
2. Press Y to delete the configuration. The system displays another warning asking you to confirm the permanent
1. Follow the instructions on the bottom of the individual menus until you are prompted to exit.
2. Press Y to exit. Depending on the settings that were changed, a reboot may be necessary.

supported, the PXESelect utility automatically reboots even if no
changes were made to the system.
Broadcom
- 38 -
NOTE If UMC is enabled and the adapter supports Lenovo System x Virtual
Fabric mode or Lenovo System x UFP mode, see Section 3.5.6,
information. If UMC is disabled or not supported on the adapter, see
Section 3.5.4, Configuring Ports If UMC Is Disabled or Not Supported.
3.5.5.1 Enabling UMC

UMC provides the ability to configure multiple physical functions or I/O channels for each physical adapter port. For
more information on UMC support, refer to the Emulex Universal Multichannel Reference Manual.
NOTE If UMC is enabled, you must configure the minimum and maximum
bandwidths settings for iSCSI and FCoE storage functions in the NIC
BIOS before they can be configured further from their respective
function will still appear as down, and you will not be able to log in to
PXE VLAN is not supported in UMC environments.
running in 10GbE or 40GbE mode only. UMC is not supported in 1GbE
mode.
SR-IOV is not available if UMC is enabled.
To enable UMC:
1. From the Controller Configuration dialog (Figure 15), use the up or down arrow keys to select MultiChannel.
2. Use the left or right arrow keys to enable UMC.
3. Press the F6 key to proceed.
3.5.5.1.1 ARI Support

The OCe14000-series adapters support ARI, which provides the ability to configure additional PCI functions or I/O
channels for each physical adapter port if UMC is enabled.
You can configure up to 16 functions on a one-port OCe14400-series adapter, up to 8 functions per port on a one or
two-port OCe14100-series adapter, and up to 4 functions per port on a four-port OCe14100-series adapter.
The maximum number of functions allowed on an adapter is controlled by the adapter's IPL file and the system’s
support for ARI.
The following requirements must be met to support more than eight functions on an adapter.
 The system hardware (the motherboard and BIOS) must support ARI.
 ARI must be enabled in the system BIOS.
 The host operating system must support ARI:
— Windows Server 2012 and newer versions
— RHEL 6.4 and newer versions
— SLES 11 SP2 and newer versions
— SLES 12 and newer versions
— ESXi 5.5 and newer versions
 The application management tools, including the Emulex OneCommand® CNA Manager application, must
support ARI.
 ARI must be enabled in the firmware using the Emulex OneCommand CNA Manager application.
Broadcom
- 39 -
If these conditions are not met, you may be able to configure more than eight functions, but only up to eight
functions will be running and discovered after a reboot.
3.5.5.2 Configuring More than Four Functions per Port on OCe14000-Series Adapters
By default on 1-port or 2-port OCe14000-series adapters, only four functions are enabled when UMC is enabled. To
enable the other four functions, you must manually enable those functions for them to be operational.
To configure more than four functions per port on 1-port or 2-port OCe14000-series adapters, perform the following
steps:
1. Ensure that UMC is enabled. By default, UMC enables four functions per port. See Section 3.5.5.1, Enabling UMC,
for information on configuring UMC.
2. Select the Custom mode in the Controller Configuration dialog (Figure 15). This enables you to view all eight
functions per port. See Section 3.5.5.3.1, Configuring the Custom Personality Selection, for information on
selecting the Custom mode.
NOTE The options to enable and configure more than four functions per
physical port are not available unless Custom mode is selected.
3. To enable each function, change the function’s personality type to the desired protocol. See Section 3.5.5.3.1,
Configuring the Custom Personality Selection, for information on selecting the personality.
4. Assign the appropriate bandwidth and LPVID. See Section 3.5.5.7, Configuring Minimum and Maximum
Bandwidth, for information on configuring the bandwidth and Section 3.5.5.8, Configuring LPVID, for information
on configuring the LPVID.
3.5.5.3 Configuring Personality

The personality reflects the adapter’s protocols. This option specifies a list of available protocols that can be configured
selections appear:
on the other enabled functions

Two iSCSI functions and two FCoE functions are not allowed on a
single port.
 Custom – For information about custom personalities, see Section 3.5.5.3.1, Configuring the Custom Personality
Selection.
2. Use the left or right arrow keys to select the desired personality.
Broadcom
- 40 -
3.5.5.3.1 Configuring the Custom Personality Selection

The Custom personality allows you to select the protocol type for each function. The first function on the port must
always be assigned the NIC personality. The iSCSI and FCoE personalities can be enabled on one function per adapter
port only.
single port.
2. Use the left or right arrow keys to select the Custom personality.
3. Press the F6 key to continue. The Port Selection Menu (Figure 16) appears.
4. On the Port Selection Menu, select the appropriate port. The following Port Menu appears.
Figure 22 Port Menu (UMC Enabled)
5. On the Port Menu, select MultiChannel Configuration and press Enter. The following Channels List appears.
Figure 23 Channels List (UMC Enabled)
6. On the Channels List, select the channel that you want to configure and press Enter. The following Channel
Broadcom
- 41 -
Figure 24 Channel Configuration Dialog (UMC Enabled)
7. On the Channel Configuration dialog, use the up or down arrow keys to select Protocol.
8. Select the desired personality for the appropriate function using the arrow keys.
NOTE The iSCSI and FCoE personalities can only be enabled on one function
per adapter port.
3.5.5.4 Loading Default Settings

If you want to erase the current configuration, from the Controller Configuration dialog (Figure 15), press the F8 key.
See Section 3.5.4.9, Erasing Ports and Adapter Configurations, for more information.
3.5.5.5 Selecting a Port

After you set the options in the Controller Configuration dialog, press the F7 key to save your changes.
To proceed to the Port Selection menu:
1. From the Controller Configuration dialog (Figure 15), press the F6 key. The Port Selection Menu (Figure 16)
appears.
2. Use the up or down arrow keys to select the port you want to configure and press Enter. The Port Menu
The Port Menu enables you to perform the following tasks:
 Configure UMC options – See Section 3.5.5.6, Configuring UMC Options, for instructions.
 Configure boot options – See Section 3.5.4.7, Configuring Boot Options, for instructions.
 Configure port options – See Section 3.5.4.8, Configuring Port Options, for instructions.
NOTE PXE VLAN configuration options are available only when UMC is
disabled.
Broadcom
- 42 -
3.5.5.6 Configuring UMC Options

To configure the UMC options:
1. From the Port Menu (Figure 22), use the up or down arrow keys to select MultiChannel Configuration and press
Enter. The Channels List (Figure 23) appears.
2. Select a channel using the up or down arrow keys and press Enter. The following Channel Configuration dialog
appears.
Figure 25 Channel Configuration Dialog (UMC Enabled)
3. From the Channel Configuration dialog, you can perform the following tasks:
— View the function number.
— Select the protocol for each function, except for the first listed function. See Section 3.5.5.3, Configuring
Personality, for instructions.
— Configure the minimum and maximum bandwidth for each channel. See Section 3.5.5.7, Configuring
— View the permanent and virtual MAC addresses.
— View the logical link status.

— Configure the LPVID for each channel. For more information, see Section 3.5.5.8, Configuring LPVID.
— View the SR-IOV status.
NOTE SR-IOV is automatically disabled if UMC is enabled.

Your adapter or system may not support all UMC options.
3.5.5.7 Configuring Minimum and Maximum Bandwidth

1. On the Channel Configuration dialog (Figure 24), use the up or down arrow keys to select Min BW or Max BW.
2. Use the left or right arrow keys to select the desired bandwidth value.
— The Minimum Bandwidth value is the least amount of bandwidth the function can provide. It is represented
as a percentage. The Minimum Bandwidth value must be less than or equal to the Maximum Bandwidth
value. The total of the Minimum Bandwidth values for all enabled functions on that port must be equal to
100.

Broadcom
- 43 -
— The Maximum Bandwidth value is the greatest amount of bandwidth the function can provide. It is
3.5.5.8 Configuring LPVID

operating system for that PCI function has set up a VLAN ID, then the operating system–configured VLAN ID takes
precedence over the LPVID for transmit packets, while both the operating system–configured VLAN ID and LPVID–
tagged packets will be received. If the operating system has not set up any VLAN IDs, then the LPVID is used for
tagging.
be different.
LPVIDs must be configured on the switch port.
During PXE boot when the UNDI driver (BIOS) is functional, the PXE VLAN is used. However, after the NIC driver is
operational the LPVID is used.
NOTE PXE VLAN is not supported in UMC environments.

For example:
PXE Install OS
PXE Server configured with VLAN 5
PXE VLAN=5
LPVID for function 0=5
To configure LPVID:
1. On the Configure Channel dialog (Figure 25), use the use the up or down arrow keys to select LPVID.
2. Use the left or right arrow keys to select the desired LPVID value. The LPVID range is 2 to 4094. A value of 0
disables the LPVID.
NOTE This section pertains to certain Emulex OneConnect adapters that

support Multichannel for Lenovo System x Virtual Fabric or UFP only.
To select a Multichannel mode:
1. From the following Controller Configuration dialog (Figure 26), use the up or down arrow keys to select
Multichannel Mode.
Broadcom
- 44 -
Figure 26 Controller Configuration Dialog - Lenovo System x Adapters
2. Use the left or right arrow keys to select one of the following settings and press Enter:
— Virtual Fabric Mode (referred to as IBM Virtual Fabric Mode on some OCe14000-series adapters)
— Unified Fabric Protocol Mode (referred to as IBM Unified Fabric Protocol Mode on some OCe14000-series
adapters)
— Disabled
NOTE For more information on the available Multichannel modes, see

With the Multichannel mode selected, you can now configure Multichannel for Lenovo System x support. See
Section 3.5.6.3, Multichannel Configuration for Lenovo System x, for more information.
3.5.6.1 Configuring More than Four vNICs per Port on OCe14000-Series Adapters
By default on 1-port or 2-port OCe14000-series adapters, only four vNICs are enabled when Multichannel is enabled.
To enable the other four vNICs, you must manually enable those vNICs for them to be functional.
To configure more than four vNICs per port, perform the following steps:
1. Ensure that Multichannel is enabled. By default, Multichannel enables four vNICs per port. See Section 3.5.6,
Configuring Multichannel for Lenovo System x Adapters, for information on configuring Multichannel.
2. Select the Custom mode in the Controller Configuration dialog (Figure 26). This allows you to view all eight vNICs
per port. See Section 3.5.5.3.1, Configuring the Custom Personality Selection, for information on selecting the
Custom mode.
3. For each vNIC to be enabled, change the personality type to the desired protocol. See Section 3.5.5.3.1,
Configuring the Custom Personality Selection, for information on selecting the personality.
Bandwidth, for information on configuring the bandwidth and Section 3.5.5.8, Configuring LPVID, for information
on configuring the LPVID.
NOTE The following modes are available only on Lenovo System x adapters
and systems that support Virtual Fabric mode and Unified Fabric
Protocol mode.
Additional PFs are supported when ARI is enabled on the system. For
more information on ARI, see Section 3.5.5.1.1, ARI Support.
Broadcom
- 45 -
A Lenovo System x Virtual Fabric–enabled switch provides the ability to configure an LPVID for a virtual channel or I/O
channel on an adapter port. If Multichannel for Lenovo System x is supported on the system, the PXESelect utility
enables you to select one of the following modes:
 Virtual Fabric Mode – Select this mode if an Emulex OneConnect adapter is attached to an Lenovo System x
Virtual Fabric–enabled switch. This mode supports up to four PFs per port.
NOTE Virtual Fabric mode is not supported on 40GbE switches.

 Unified Fabric Protocol Mode – Select this mode if an Emulex OneConnect adapter is attached to a Lenovo
System x UFP-enabled switch. In this mode, the maximum PFs per port for each adapter configuration is listed
below:
— 2-port 10GbE adapters – 8 PFs per port
NOTE Some Lenovo System x switches support both Unified Fabric Protocol
mode and Virtual Fabric mode.
Fabric or UFP-enabled switch. In this mode, the maximum PFs per port for each adapter configuration is listed
below:
If this mode is enabled, see Section 3.5.5, Configuring Universal Multichannel, for information on configuring
Multichannel for Lenovo System x.
NOTE Multichannel for Lenovo System x is supported on Emulex

OneConnect adapters running in 10GbE mode only. Multichannel for
Lenovo System x is not supported in 1GbE mode.
3.5.6.3 Multichannel Configuration for Lenovo System x

NOTE By default on 1-port or 2-port OCe14000-series adapters using either

Virtual Fabric mode or Unified Fabric Protocol mode, only four vNICs
are enabled when Multichannel is enabled. To enable the other four
vNICs, you must manually enable those vNICs using the steps
provided in Section 3.5.6.1, Configuring More than Four vNICs per Port
on OCe14000-Series Adapters.
Setting up Multichannel for Lenovo System x Virtual Fabric or UFP
depends on cooperation with adjacent switches.
See Section 3.5.5, Configuring Universal Multichannel, for information
on configuring Multichannel for Lenovo System x if Switch
Independent mode is enabled.
To view the configuration dialog:
1. From Port Selection Menu (Figure 16), select the port you want to configure and press Enter. The configuration
dialog appears.
If you are configuring Multichannel for Lenovo System x, the configuration options will depend on the
Multichannel mode selected.
Broadcom
- 46 -
NOTE For illustration purposes, the dialogs in this section are for a system
with Virtual Fabric mode selected.
Figure 27 Virtual Fabric Mode MultiChannel Configuration Dialog
NOTE If the system does not support some of the Multichannel options, the
unavailable options are disabled on the Channel Configuration dialog.
2. From the Channel Configuration dialog (Figure 27), you can perform the following tasks:
— Select the protocol for each function, except for the first listed function. See Section 3.5.5.3, Configuring
Personality, for instructions.
— Configure the minimum and maximum bandwidth for each channel. See Section 3.5.5.7, Configuring
NOTE If Switch Independent mode is enabled, you must configure the

minimum and maximum bandwidth settings on the switch.
— View the logical link status.

— Configure the LPVID for each channel. For more information, see Section 3.5.5.8, Configuring LPVID.
NOTE An LPVID is optional for Virtual Fabric mode, but it is required for every
function if Switch Independent mode is selected.
— View the SR-IOV status.
NOTE SR-IOV is automatically disabled if Multichannel is enabled.
Broadcom
- 47 -
3.6 PXE Boot Parameters Default Values

UMC or Multichannel Mode The default for this parameter varies For Emulex adapters:
(Lenovo System x) depending on the vendor configuration.  Enabled
 Disabled
For Lenovo System x adapters:
 Virtual Fabric Mode
 Unified Fabric Protocol Mode
 Switch Independent Mode
 Disabled
Personality The default for this parameter varies If UMC is enabled:
depending on the vendor configuration.  NIC
 iSCSI
 FCoE
 Custom
If UMC and SR-IOV are disabled:
 NIC
 iSCSI
 FCoE
 NIC+RoCE
NOTE RoCE is supported on Windows and Linux only.
If UMC is disabled and SR-IOV is enabled:
 NIC
 iSCSI
 FCoE
Disabled
RoCE Profile RoCE-2 RoCE-2
NOTE This setting is only
available if the NIC+RoCE
personality is selected.
NOTE This setting is only
available if the Virtualization
mode is set to None.
Minimum Bandwidth 0% Must have a total of 100% across all enabled function
on that port
Maximum Bandwidth 0% From the minimum bandwidth value up to 100%
(inclusive)
LPVID 0 2 to 4094
depending on the vendor configuration. Disabled
Broadcom
- 48 -

PXE VLAN Disabled Enabled
Disabled
PXE VLAN ID 0 2 to 4094
PXE VLAN Priority 0 0 to 7
Broadcom
- 49 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 4: Configuring Boot from SAN for the FCoE Protocol
December 30, 2016 Windows Server
Chapter 4: Configuring Boot from SAN for the FCoE Protocol

When booting from SAN, the storage device is typically identified by its WWPN and a LUN. By extending the server
system BIOS, boot from SAN capability is provided by the boot BIOS contained on an Emulex adapter in the server. If
properly configured, the adapter then permanently directs the server to boot from a logical unit (disk) on the SAN as if
it were a local disk.
NOTE Not all procedures are required. Emulex adapters usually ship from the
factory with the latest version of boot code enabled, so you do not
need to enable boot code in those cases. However, if boot code is not
enabled, you must enable it. You may want to update the boot code if
a more current version is available at http://www.broadcom.com.
This section describes how to set up a system to boot from SAN. The specific procedure to follow is determined by the
system architecture and the operating system.
Table 6 Boot from SAN Procedures
Architecture Operating System Procedure

x86 and x64 Windows Server 2008, Section 4.2, Installing Windows Server on a Boot Disk (x64)
Windows Server 2008 R2,
Windows Server 2012,
Windows Server 2012 R2
Windows Server 2016
Linux Section 4.3.1, Configuring Boot from SAN on Linux, Citrix, or VMware
(x86 and x64)
VMware
Solaris (SFS driver) Section 4.4.1, Configuring Boot from SAN on Solaris (x86 and x64)
PowerPC Solaris (SFS driver) Section 4.4.1, Configuring Boot from SAN on Solaris (x86 and x64)
UEFI-based systems Windows Server 2008, Section 4.1.2, Configuring Boot from SAN on Windows (UEFI)
Windows Server 2008 R2, Section 4.3.2, Configuring Boot from SAN on Linux or VMware (UEFI)
Windows Server 2012,
Windows Server 2012 R2
Windows Server 2016
4.1 Windows Server
This section explains how to configure boot from SAN on Windows Server operating systems.
4.1.1 Configuring Boot from SAN on Windows (x64)
To configure boot from SAN:

1. If necessary, update the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code, for more
information.
2. If necessary, enable the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code, for more
information.
3. Enable the adapter to boot from SAN. See Section 6.3, Enabling an Adapter to Boot from SAN, for more
information.
4. Configure boot devices. See Section 6.5, Configuring Boot Devices, for more information.
Broadcom
- 50 -
December 30, 2016 Windows Server
5. If desired, configure the boot options on the adapter. See Section 6.7, Configuring Advanced Adapter Parameters,
for more information.
6. Install the operating system on a boot disk. For more information, see Section 4.2, Installing Windows Server on a
Boot Disk (x64).
4.1.2 Configuring Boot from SAN on Windows (UEFI)

1. If necessary, update the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code for more
information.
2. If necessary, enable the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code for more
information.
5. Install the operating system on a boot disk:
— For a new installation of a UEFI-aware operating system on a UEFI-based x64 server, see Section 4.1.3,
Installing a New Windows UEFI-Aware Operating System on a UEFI-Based x64 Server.
— To direct a UEFI-based server to a Windows operating system image that is already installed on the
SAN, see Section 4.1.4, Directing a UEFI-Based Server to a Windows Server Operating System Image Already
Installed on the SAN.
— To install Windows Server on an unformatted boot disk and configure the system to boot from the SAN disk
drive, see Section 4.2, Installing Windows Server on a Boot Disk (x64).
4.1.3 Installing a New Windows UEFI-Aware Operating System on a UEFI-Based x64 Server
This installation procedure assumes LUNs are created in the SAN storage device and zoned appropriately to the host
adapter's WWN.
To install a new Windows Server UEFI-aware operating system:
1. From the server system UEFI setup, verify that CD/DVD is the first device in the boot order list.
2. Enable the adapter BIOS setting to allow SAN boot in the Emulex UEFI configuration utility.
3. Configure the boot target and LUN in the Emulex UEFI configuration utility to select the desired target.
4. Boot the host server with the Windows Server DVD inserted. Follow the on-screen prompts to install the
appropriate version of Windows Server.
The Windows installation exposes all available and visible LUNs as disks and partitions numbered 0 to N, where N
is the highest number available. These numbers typically are the LUN numbers assigned by the array.
5. Select the disk on which you want to install the operating system.
6. Follow system prompts in the Windows installation.
NOTE By default, Microsoft Windows Servers install with a GPT-formatted

disk on an UEFI-aware server.
After the installation is complete, Windows Boot Manager, which is available from the Start Options menu of the host
server UEFI, is populated with a media device path pointing to the Windows boot loader utility.
The Windows Boot Manager option is inserted as the first boot option in the boot order list of the host server UEFI. The
CD/DVD is the second device in the boot order list.
Upon reboot, the system boots from the LUN set up on the SAN.
Broadcom
- 51 -
December 30, 2016 Installing Windows Server on a Boot Disk (x64)
4.1.4 Directing a UEFI-Based Server to a Windows Server Operating System Image Already
Installed on the SAN
This installation procedure assumes a LUN exists in the SAN storage device, is zoned appropriately to the host
adapter’s WWN, and a UEFI-aware operating system resides on the target LUN.
To direct an UEFI-based server to a Windows Server operating system Image (installed as UEFI-aware) already installed
on the SAN:
1. Enable network boot in the Emulex UEFI configuration utility. See Section 13.4, Enabling an Adapter to Boot from
SAN, for more information.
2. Configure the boot target and LUN in the Emulex UEFI configuration utility to point to the desired target. See
Section 13.7, Adding Boot Devices, for more information.
3. Select Boot Manager from the system UEFI configuration manager.
4. Select Add Boot Option.
5. Identify the desired target in the list, and continue down the explorer path until you locate the bootmgfw.efi
file. This file is the boot loader utility for the Windows Server UEFI-aware operating system installation.
6. Input a boot device description (for example, Win2K8_UEFI_SAN) and optional data (if desired) for this device and
select Commit Changes.
7. From the Windows Boot Manager, select Change Boot Order.
8. Move the previous input description name (Win2K8_UEFI_SAN) to the desired position in the boot order.
9. Select Commit Changes. The Start Options list now reflects the boot order changes.
Upon reboot, the server is able to boot from this target LUN on the SAN.
4.2 Installing Windows Server on a Boot Disk (x64)
This procedure installs Windows Server onto an unformatted disk drive and configures the system to boot from the
SAN disk drive.
NOTE The computer’s system BIOS may require that another adapter take
precedence over the Emulex adapter during boot. If this occurs, you
must disconnect or disable the other adapter. This lets you configure
and build the operating system on the drive connected to the Emulex
adapter.
To install Windows Server on a boot disk:
1. Install the Emulex driver for Windows as described in the Emulex Drivers for Windows User Guide for OneConnect
Adapters.
2. In Windows Explorer, navigate to the folder you specified during driver installation.
3. In the \AutoPilot Installer\Drivers\drivername folder, open the folder that corresponds to your
computer type, such as x64. drivername is the type of driver you downloaded.
4. Copy all the files in this folder onto a formatted floppy disk or a USB device.
5. Boot the target system with the Windows Server setup media. The system displays the Install Windows splash
screen.
6. Configure the values for the language, the time and date, and the keyboard. Click Next. Another splash screen
appears.
7. Click Install Now. The Where do you want to install Windows? pop up appears.
Broadcom
- 52 -
December 30, 2016 Linux, Citrix, and VMware Operating Systems
8. Click Load Driver. Browse to the floppy disk or USB device that contains the driver to load the driver for the
appropriate operating system. After selecting the driver, the correct driver location and driver are displayed under
the Select driver to be installed dialog.
9. Select Next. After the driver is loaded, the Where do you want to install Windows? pop up appears.
10. Select the drive you configured as the boot device. See Section 6.5, Configuring Boot Devices.
4.3 Linux, Citrix, and VMware Operating Systems
This section explains how to configure boot from SAN on Linux, Citrix, and VMware operating systems.
4.3.1 Configuring Boot from SAN on Linux, Citrix, or VMware (x86 and x64)

1. If necessary, update the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code, for more
information.
information.
information.
4. If necessary, enable spinup delay. See Section 6.7.2, Enabling or Disabling the Spinup Delay, for more information.
7. Use the driver on the operating system distribution disk to boot the system. If necessary, you can update the
driver to the latest version.
4.3.2 Configuring Boot from SAN on Linux or VMware (UEFI)

1. If necessary, update the latest boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code, for
more information.
information.
3. Configure boot devices. See Section 6.3, Enabling an Adapter to Boot from SAN, for more information.
5. Use the driver on the operating system distribution disk to boot the system. If necessary, you can update the
driver to the latest version.
4.4 Solaris Operating System
This section explains how to configure boot from SAN on the Solaris operating system.
Broadcom
- 53 -
December 30, 2016 Solaris Operating System
4.4.1 Configuring Boot from SAN on Solaris (x86 and x64)

1. If necessary, update the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code for more
information.
2. If necessary, enable the boot code on the adapter. See Chapter 7, Updating and Enabling Boot Code for more
information.
information.
4. If necessary, enable spinup delay. See Section 6.7.2, Enabling or Disabling the Spinup Delay, for more information.
7. Boot the Solaris installation CD and follow the prompts.
NOTE If you need help determining the LUNs to select for boot from SAN, see
Section 4.4.2, Determining LUNs to Select for Boot from SAN.
4.4.2 Determining LUNs to Select for Boot from SAN
To determine which LUNs to select:

1. Open a terminal window and leave it open.
2. In the terminal window, select the LUN you are going to use as the SAN boot disk (not the local drive) using the
luxadm probe command. This shows all the available LUNs. Record this LUN information, which is used
throughout this procedure. LUN 0 is used in the example:
luxadm probe
Found Fibre Channel device(s):

Node WWN:50060e8003823800 Device Type:Disk device
Logical Path:/dev/rdsk/c5t226000C0FF9833AFd6s2
Logical Path:/dev/rdsk/c5t226000C0FF9833AFd6s2
3. Copy the /dev/rdsk/nnn part of the path statement for a drive.
4. In the terminal window, use the luxadm display command to show the WWPN or the LUN for which you
selected the path in the prior step:
luxadm display </dev/rdsk/nnn>
5. Record this LUN or WWPN information for use in the procedure.
Broadcom
- 54 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 5: Configuring x86/x64 Platforms for the iSCSI Protocol
December 30, 2016 Constructing a Basic iSCSI SAN
Chapter 5: Configuring x86/x64 Platforms for the iSCSI Protocol

The iSCSI protocol is an IP-based standard for linking data-storage devices over a network and transferring data by
carrying SCSI commands over IP networks. An iSCSI network consists of one or more iSCSI storage units (targets)
connected through a copper or optical networking cable to 10GbE network switches and IP routers. One or more
servers are connected to this network, which are responsible for transferring data to or from the storage units.
When an operating system receives a request, it generates the SCSI command and then sends an IP packet over an
Ethernet connection. At the receiving end, the SCSI commands are separated from the request, and the SCSI
commands and data are sent to the SCSI controller and then to the SCSI storage device. iSCSI also returns a response
to the request using the same protocol.
5.1 Constructing a Basic iSCSI SAN
Three main components make up an iSCSI SAN:

 iSCSI initiator – The initiator allows a given machine to access the storage available in the iSCSI SAN. It requests
all SCSI operations like read or write. An initiator is usually located on the host (server) side, either as hardware
(iSCSI adapter) or software (iSCSI software initiator). To transport block (SCSI) commands over the IP network, an
iSCSI driver must be installed on the iSCSI host. An iSCSI driver is included with the Emulex adapter. For more
information on iSCSI initiators, see Chapter 9, Configuring and Managing the iSCSI Initiator with the iSCSISelect
Utility.
 iSCSI target – An iSCSI SAN has one or more iSCSI targets, which house and make available the storage used
within the SAN. The iSCSI target is the storage device itself or an appliance that controls and serves volumes or
virtual volumes. The target is the device that performs the SCSI command or bridges it to an attached storage
device. iSCSI targets can be disks, RAID arrays, or FC fabrics. For more information, see Chapter 10, Configuring
and Managing iSCSI Targets with the iSCSISelect Utility.
 Networking infrastructure – The networking infrastructure in an iSCSI SAN uses Ethernet transport. The
configuration and complexity of the storage network depend on its intended function and the required
capabilities.
5.2 Managing an iSCSI Session
To transmit information from an iSCSI initiator to an iSCSI target, the initiator must first establish a session with the
target through an iSCSI login process. The login process:
 Starts a TCP/IP connection
 Verifies that the iSCSI initiator has access to the iSCSI target (authentication)
 Allows negotiation of various parameters
5.2.1 Logging in to an iSCSI Session
An iSCSI session has two phases:

 Login phase – iSCSI parameters are negotiated using login requests and responses.
 Full featured phase – After authentication has occurred and operational parameters have been set, the initiator
begins to perform SCSI I/O functions.
Broadcom
- 55 -
December 30, 2016 Configuring Boot from SAN for iSCSI
5.2.2 Security
Because the iSCSI protocol operates in the internet environment, security is critical. The iSCSI SAN uses the CHAP
security method.
5.2.2.1 CHAP Authentication

CHAP authentication is used to periodically verify the identity of the initiator by the target using a challenge and
response mechanism. The challenge and response is established on the initial link and may be repeated at any time
afterward. For CHAP to work, the target must know the initiator's secret key, and the initiator must correctly respond
to the challenge.
Although the authentication is only one-way, you can negotiate CHAP in both directions for mutual authentication
with the help of the same secret set.
5.3 Configuring Boot from SAN for iSCSI
This section provides instructions for configuring boot from SAN for iSCSI on various operating systems using the
iSCSISelect utility. It also provides information on using the iSCSISelect utility to perform an MPIO boot configuration.
5.3.1 Setting Up Boot from SAN for iSCSI
In the iSCSI target configuration, you have the option of setting dual network paths to a single boot LUN.
NOTE iSCSI must be enabled for the port before configuring a boot target.
5.3.1.1 Windows Server

To set up boot from SAN for iSCSI on Windows Server:
1. Log in to the iSCSISelect utility by pressing the Ctrl-S keys when prompted.
2. Use the iSCSISelect utility to log in to a target from one adapter and configure it for boot. For more information,
see Chapter 9, Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility and Chapter 10,
Configuring and Managing iSCSI Targets with the iSCSISelect Utility.
If the iSCSISelect utility is configured properly, a message during boot time indicates that the iSCSI disk was
successfully connected.
3. Install a Windows Server operating system over the iSCSI LUN.
5.3.1.2 Linux and Citrix Servers

To set up boot from SAN for iSCSI on Linux or Citrix:
3. Install a Linux operating system over the iSCSI LUN. For more information on installing the driver, refer to the
Emulex Drivers for Linux User Guide for OneConnect Adapters, in the Documents and Downloads area of
http://www.broadcom.com. For iSCSI boot, you will need the following information:
For RHEL operating systems:
Broadcom
- 56 -
a. When running the vmlinuz command, include the dd parameter to indicate that a driver update will be
done.
b. When prompted for the type of device your installation involves, choose Specialized Storage Devices.
c. When prompted to select the drives on which you will install the operating system or any drives you want to
automatically mount to the system, select the iSCSI target device on the Other SAN Devices tab.
For SLES operating systems:
a. Set withiscsi=1 to indicate that a driver update will be done.
b. When prompted, click Configure iSCSI Disks to perform target login.
NOTE You may need to run certain iscsiadm commands to load the disk
after the iSCSI driver is installed. Refer to the iscsiadm documentation
5.3.1.3 ESXi Server

To install and configure boot from SAN on an ESXi server:
1. Log in to the iSCSISelect utility pressing the Ctrl-S keys when prompted.
3. Install an ESXi Server operating system over the iSCSI LUN. For more information on installing the driver, refer to
the Emulex Drivers for VMware User Guide for OneConnect Adapters in the Documents and Downloads area of
http://www.broadcom.com.
5.3.2 Booting from SAN for iSCSI MPIO
MPIO support allows the initiator to log in to dual sessions to the same target. In this way I/O can be sent over either
TCP/IP connection to the target. If one session fails another session can continue processing I/O without interrupting
the application. In iSCSI target configuration, you have the option of setting dual network paths to a single boot LUN.
NOTE Although MPIO boot support allows the initiator to log in to multiple
sessions, the iSCSI BIOS currently limits the number of sessions to two
iSCSI sessions for a single boot LUN.
5.3.2.1 Windows Server

To install and configure MPIO on Windows Server:
2. Use the iSCSISelect utility to log in to a target from one adapter and configure it for boot by following the steps in
Section 8.2, Setting Up a Basic iSCSI Boot Configuration.
NOTE Only one instance of the boot LUN must be visible to the server during
the installation. The installation might fail if multiple instances of the
boot LUN are available to the server. Disable the Spanning Tree
Protocol on any ports connected to Windows Server hosts booting
using iSCSI. The Spanning Tree Protocol is used to calculate the best
Broadcom
- 57 -
path between switches if there are multiple switches and multiple

paths through the network.
3. Install a Windows Server operating system over the iSCSI LUN.
4. After Windows Server is installed, install the MPIO software (such as Microsoft iSCSI Initiator), and reboot the
system.
5. After rebooting, verify that the boot LUN is detected by the MPIO driver. This can be done by either of the
following two methods:
— Look at the driver name for the disk device from Device Manager,
Or
— Use the MPIO GUI to check for device ID MS FT2005iSCSIBusType_0x9 under the MPIO Devices tab. The
Disk Manager does not show duplicate disks.
6. Reboot the system and log in to the iSCSISelect utility by pressing the Ctrl-S keys when prompted.
7. You can now add an additional boot path with the iSCSISelect utility.
To add an additional boot path to the same iSCSI LUN:
a. Follow the steps from Section 5.3.1.1, Windows Server, to set up the second path.
b. At the Add/Ping iSCSI Target menu, set a valid ISID Qualifier before adding the target. The ISID Qualifier can
be any number up to 65535. For more information on when an ISID value must be changed, see Section 5.3.2,
Booting from SAN for iSCSI MPIO.
c. After logging in to the target, from the iSCSI Target Configuration menu, set the Boot Target option for the
second target to Yes.
d. Press the F7 key to show the LUNs behind the target.
e. Select the same LUN you chose for the initial boot LUN, then press the F3 key to set it to bootable.
8. After Windows Server boots, the MPIO installs drivers on the second path and prompts for reboot. Reboot the
server.
5.3.2.2 Linux and Citrix Servers

To install and configure MPIO on Linux or Citrix:
2. Use the iSCSISelect utility to log in to a target from one adapter and configure it for boot by following the steps
from Section 5.3.1.2, Linux and Citrix Servers.
3. After the operating system is installed, install the MPIO software and reboot the system.
4. After rebooting, verify that the boot LUN is detected by the MPIO driver. Perform either of the following steps:
— To see if the multipath is running, type:
# /sbin/multipath
Or
— To see if the multipath daemon is running, type:
# ps -aelf | grep multipathd
5. If multipath is running, you can view the current multipath topology by typing
# /sbin/multipath -l
6. Reboot the system and log in to the iSCSISelect utility by pressing the Ctrl-S keys when prompted.
7. Use the iSCSISelect utility to add an additional boot path to the same iSCSI LUN. To do this, follow these steps:
Broadcom
- 58 -
a. Follow the steps from Section 5.3.1.2, Linux and Citrix Servers, to set up the second path.
b. When you get to the Add/Ping iSCSI Target menu, make sure you set a valid ISID Qualifier before adding the
target. The ISID Qualifier can be any number up to 65535. For more information on when an ISID value must
be changed, see Section 5.3.2, Booting from SAN for iSCSI MPIO.
c. After logging in to the target, from the iSCSI Target Configuration menu, set the Boot Target option for the
f. Follow the instructions on the bottom of the menus until you are prompted to exit.
g. Save your changes before you exit.
h. Press Y to exit the iSCSISelect utility.
8. After Linux boots, the MPIO installs drivers on the second path and prompts you to reboot. Reboot the server.
5.3.2.3 ESXi Server

To install and configure MPIO on an ESXi server:
2. Use the iSCSISelect utility to log in to a target from one adapter and configure it for boot by following the steps
from Section 5.3.1.3, ESXi Server.
3. After the ESXi server is installed, install the MPIO software and reboot the system. The ESXi Server is MPIO by
default.
4. Use the iSCSISelect utility to add an additional boot path to the same iSCSI LUN. To do this, follow these steps:
a. Follow the steps from Section 5.3.1.3, ESXi Server, to set up the second path.
b. When you access the Add/Ping iSCSI Target menu, set a valid ISID Qualifier before adding the target. The ISID
Qualifier can be any number up to 65535. For more information on when an ISID value must be changed, see
Section 5.3.2, Booting from SAN for iSCSI MPIO.
c. After you log in to the target, from the iSCSI Target Configuration menu, set the Boot Target option for the
f. Follow the instructions on the bottom of the menus until you are prompted to exit.
g. Save your changes before you exit.
h. Press Y to exit the iSCSISelect utility.
After the ESXi Server boots, the MPIO installs drivers on the second path and prompts for a reboot.
5. Reboot the server.
Broadcom
- 59 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 6: Using the FCoE Boot BIOS Utility for x86 and x64 Architectures
December 30, 2016 Navigating the FCoE BIOS Utility
Chapter 6: Using the FCoE Boot BIOS Utility for x86 and x64
Architectures
Before using the FCoE BIOS utility, verify that the boot code is enabled on the adapter as described in Chapter 7,
Updating and Enabling Boot Code.
NOTE This section reflects the most recent release of the FCoE BIOS utility.
Some selections may not be available if you are using an older version
of the utility.
After exiting the FCoE BIOS configuration utility, the system will
reboot whether or not any changes have been made.
6.1 Navigating the FCoE BIOS Utility
Use the following methods to navigate the FCoE BIOS utility:

 Press the Page Up key to scroll to the previous page.
 Press the Page Down key to scroll to the next page.
 Press Enter to select a menu option, to select a changed value, to select a row in a configuration dialog, or to
change a configuration default.
 Press Esc to go back to the previous menu.
6.2 Starting the FCoE BIOS Utility
NOTE Links must be established before starting the FCoE BIOS utility;
otherwise, you will receive an error message.
To start the FCoE BIOS utility:
1. Turn on the computer and press Alt-E or Ctrl-E immediately (within five seconds) when the Emulex bootup
message to start the FCoE BIOS utility appears. An adapter listing (Figure 28) appears.
NOTE If the bootup message does not appear, you must enable x86
BootBIOS. For more information, see Chapter 7, Updating and
Enabling Boot Code.
Broadcom
- 60 -
December 30, 2016 Starting the FCoE BIOS Utility
Figure 28 Emulex Adapter Listing
2. Select the adapter to configure and press Enter. The following main configuration menu appears.
Figure 29 Main Configuration Menu
Under normal circumstances, you would first configure boot devices using the FCoE BIOS utility. However, if the
adapter is not enabled to boot from SAN, you must first enable the adapter to do so.
Broadcom
- 61 -
December 30, 2016 Enabling an Adapter to Boot from SAN
6.3 Enabling an Adapter to Boot from SAN
To enable an adapter to boot from SAN, from the main configuration menu (Figure 29), select Enable/Disable Boot
from SAN and press Enter.
NOTE Adapters are disabled by default.

Boot from SAN must be enabled on one adapter to use remote boot functionality. After you enable an adapter, its
boot status appears.
Figure 30 BIOS Status
6.4 Scanning for Target Devices
To scan for target devices:

1. From the main configuration menu (Figure 29), select Scan for Target Devices. This option displays a list of
discovered target devices (Figure 31). It allows you to quickly verify zoning and SAN connectivity.
Broadcom
- 62 -
December 30, 2016 Configuring Boot Devices
Figure 31 Devices Present on the Adapter
2. Press Esc to return to the main configuration menu.
6.5 Configuring Boot Devices
To configure boot devices:

1. On the main configuration menu (Figure 29), select Configure Boot Devices and press Enter.
A list of eight boot devices appear (Figure 32). The primary boot device is the first entry shown. It is the first
bootable device. If the first boot entry fails, the system attempts to boot from the second bootable entry. If the
second boot entry fails, the system attempts to boot from the third bootable entry and so on.
NOTE This assumes the system BIOS supports BBS and the boot order in the
system BIOS is set using the mapped drives from the list of saved boot
devices.
Broadcom
- 63 -
Figure 32 List of Saved Boot Devices
2. Select a boot entry and press Enter. A list similar to the following one appears.
Figure 33 Device Selection List Example
3. Select 00 and press Enter to clear the selected boot entry, or select the WWPN or DID of a device to configure and
press Enter.
4. If you select a device, you are asked for the starting LUN (Figure 34). Use the up and down arrows to enter the
starting LUN in hexadecimal format and press Enter. The starting LUN can be any number from 0 to 255.
Broadcom
- 64 -
Figure 34 LUN Listing Dialog
5. A dialog similar to the following one appears. Press Enter.
Figure 35 Selected Boot Device Dialog
The following Boot Devices dialog (Figure 36) appears.
Broadcom
- 65 -
Figure 36 Boot Devices Dialog
6. Use the up and down arrows to select the boot method and press Enter. In the list that appears you can select to
scan and boot from the device by its unique WWPN or by its FC DID.
Figure 37 Primary Boot Device Setup
7. Press Enter to select the change.

8. Press Esc to return to the main configuration menu.
9. Reboot the system for the new boot path to take effect.
Broadcom
- 66 -
December 30, 2016 Configuring FCoE FCF CEE Parameters
6.6 Configuring FCoE FCF CEE Parameters
NOTE For DCBX configuration, the adapter is always in CEE mode.

An FCF is the bridging layer to connect FCoE to an FC network. The FCF is usually built into the FCoE switch.
The FCF contains routing information including the switch name, fabric name, and VLAN information used to send the
FCoE data to the correct FC fabric.
To configure CEE parameters:
1. If multiple VLANs or FCoE switches are set up and you want to select a particular VLAN to boot from every time,
select Configure FCF CEE Parameters from the main configuration menu (Figure 29) and press Enter. A list of
discovered FCFs appears.
Figure 38 FCF Listing
2. Select the FCF you want to boot from every time and save it to the adapter record by pressing Enter. The system
displays the following message (Figure 39).
Broadcom
- 67 -
December 30, 2016 Configuring Advanced Adapter Parameters
Figure 39 Save Edited Boot Record Dialog Box
3. Press Y to save the boot record. The main configuration menu (Figure 29) appears.
6.7 Configuring Advanced Adapter Parameters
The BIOS utility provides various options that can be modified to provide different behavior. Use the BIOS utility to
perform the following tasks:
 Change the port login retry timer.
 Enable or disable spinup delay.
 Set autoscan.
 Enable or disable EDD 3.0.
 Enable or disable the start unit command.
 Enable or disable the environment variable.
 Enable or disable the auto boot sector.
To access the adapter configuration menu, from the main configuration menu (Figure 29), select Configure Advanced
Adapter Parameters and press Enter. The following adapter configuration menu (Figure 40) appears.
Broadcom
- 68 -
Figure 40 Advanced Adapter Configuration Menu
The default settings are acceptable for most installations.

To reset all values to their defaults, from the main configuration menu (Figure 29), select Reset Adapter Defaults and
press Enter.
6.7.1 Changing the Port Login Retry Timer
This option is especially useful for Tachyon-based RAID arrays. Rarely, a Tachyon-based RAID array resets itself and the
port goes offline temporarily. When the port returns to operation, the port login scans the loop to discover the device.
The port login retry interval is the time it takes for one port login to scan the whole loop. You can choose:
 No Port Login Retry: 0 msec – Default
 50 msec takes 5 to 6 seconds per device
 100 msec takes 12 seconds per device
 200 msec takes 22 seconds per device
To set the interval for the port login retry timer:
1. On the main configuration menu (Figure 29), select Configure Advanced Adapter Parameters and press Enter. The
adapter configuration menu (Figure 40) appears.
2. Select Change PLOGI Retry Timer and press Enter. Information appears similar to the following menu.
Broadcom
- 69 -
Figure 41 Change the Port Login Retry Timer Menu
3. Select the retry timer interval.

4. Press Enter to accept the new interval.
5. Press Esc to return to the advanced adapter configuration menu.
6. For changes to take effect, reboot the system.
6.7.2 Enabling or Disabling the Spinup Delay
This option lets you enable or disable the disk spinup delay. The factory default setting is disabled.
If at least one boot device has been defined, and the spinup delay is enabled, the boot BIOS searches for the first
available boot device.
 If a boot device is present, the boot BIOS boots from it immediately.
 If a boot device is not ready, the boot BIOS waits for the spinup delay and, for up to three additional minutes,
continues the boot scanning algorithm to find another multiboot device.
If boot devices have not been defined and auto scan is enabled, the boot BIOS waits for five minutes before scanning
for devices.
 In an attached fabric, the boot BIOS attempts to boot from the first target found in the NameServer data.
To enable or disable the spinup delay:
1. On the main configuration menu (Figure 29), select Configure Advanced Adapter Parameters and press Enter. The
adapter configuration menu (Figure 40) appears.
2. Select Enable or Disable Spinup Delay and press Enter. Information appears similar to the following dialog.
Broadcom
- 70 -
Figure 42 Enable or Disable Spinup Delay Dialog
3. Select whether to enable or disable spinup delay.

4. Press Enter to accept the new value.
6.7.3 Setting Auto Scan
This option allows you to enable or disable the auto scan feature. Auto scan is available only when all eight boot
entries are unused (empty). The factory default for auto scan is disabled. If there is more than one adapter with the
same PCI Bus number in the system, and each has a boot drive attached, the first PCI-scanned adapter is the boot
adapter. Auto scan allows you to boot from the first boot device found in the FC fabric with the following options:
 Autoscan disabled – Default
 Any first device – The first adapter scans the fabric and the first disk discovered becomes the attempted boot
device
 First LUN 0 device – The first device discovered with LUN 0
 First NOT LUN 0 device – The first device discovered with a LUN other than 0
To set auto scan:
1. From the main configuration menu (Figure 29), select Configure Advanced Adapter Parameters and press Enter.
The adapter configuration menu (Figure 40) appears.
2. Select Auto Scan Setting and press Enter. The system displays the following Set Auto Scan menu.
Broadcom
- 71 -
Figure 43 Set Auto Scan Menu
3. Select the appropriate auto scan option.

4. Press Enter to accept the new scan option.
6.7.4 Enabling or Disabling EDD 3.0
EDD 3.0 provides additional data to the operating system boot loader during an INT-13h function 48h call (get device
parameters). This information includes the path to the boot device and the disk size. The default setting for EDD 3.0 is
enabled. If EDD 3.0 is disabled, the setting reverts to EDD 2.1.
To enable or disable EDD 3.0:
2. Select Enable or Disable EDD 3.0 and press Enter. The EDD 3.0 configuration dialog (Figure 44) appears.
Broadcom
- 72 -
Figure 44 Enable or Disable EDD 3.0 Dialog
3. Select whether to enable or disable EDD 3.0.

4. Press Enter to accept the change.
6.7.5 Enabling or Disabling the Start Unit Command
You must know the specific LUN to issue the SCSI start unit command. The default setting is disabled.
To enable or disable the start unit command:
The system displays the adapter configuration menu (Figure 40).
2. Select Enable or Disable Start Unit Command and press Enter. The Start Unit Command configuration dialog
Broadcom
- 73 -
Figure 45 Enable or Disable Start Unit Command Dialog
3. Select whether to enable or disable the start unit command.

6.7.6 Enabling or Disabling the Environment Variable
Sets the boot adapter order if the system supports the environment variable. The default setting is disabled.
To enable or disable the environment variable:
2. Select Enable or Disable Environment Variable and press Enter. The Environment Variable configuration dialog
Broadcom
- 74 -
Figure 46 Enable or Disable Environment Variable Dialog
3. Select whether to enable or disable the environment variable.

6.7.7 Enabling or Disabling Auto Boot Sector
This option automatically defines the boot sector of the target disk for the migration boot process, which applies to
HP MSA1000 arrays only. If there is no partition on the target, the default boot sector format is 63 sectors. The default
setting is disabled.
To enable or disable the auto boot sector format:
2. Select Enable or Disable Auto Boot Sector and press Enter. The Auto Boot Sector configuration dialog
Broadcom
- 75 -
December 30, 2016 Using Multipath Boot from SAN
Figure 47 Enable or Disable Auto Boot Sector Format Dialog
3. Select whether to enable or disable the auto boot sector.

4. Press Enter to accept the new value.
6.8 Using Multipath Boot from SAN
Multiboot BIOS is in compliance with BBS. The system must have a multiboot system BIOS to take advantage of this
option. The multiboot BIOS allows you to select any boot disk in the system BIOS setup menu. The boot disk can be an
FC drive, a SCSI drive, an IDE drive, a USB device, or a floppy drive. The Emulex BIOS supplies the first eight drives to the
system BIOS menu. The multiboot BIOS can override the FC drive selected in the BIOS utility.
For example, the system has eight FC disks only. The boot disk has DID 0203E4. However, you can select DID 1A14B5 in
the system BIOS setup menu. The boot device is the FC disk with DID 1A14B5 instead of DID 0203E4, as is set in the
BIOS utility.
If the system supports multiboot BBS, the local boot disk (drive C) is the first entry in multiboot on the system BIOS
setup menu. The list of entries is determined by the list of configured boot entries in the BIOS utility. For example:
Adapter 1: boot_entry0, boot_entry1
Adapter 2: boot_entry2, boot_entry3
The order of boot entries exported to multiboot (BBS) is
boot_entry0, boot_entry1, boot_entry2, and boot_entry3
Multiboot allows changing the boot order in the system BIOS, which allows any disk to become the primary boot (C)
drive.
Broadcom
- 76 -
December 30, 2016 Resetting to Default Values
6.9 Resetting to Default Values
The BIOS utility enables you to reset BIOS boot parameters to their factory default settings. These defaults are listed in
the following table.
NOTE The FCoE CEE parameters (FCF information) are not affected. Only
boot adapter specific information is cleared.
Table 7 Default Adapter Boot Parameter Values

Boot from SAN Disabled Enabled
Disabled
EDD 3.0 Enabled (EDD 3.0) Enabled (EDD 3.0)
Disabled (EDD 2.1)
Port Login Retry Timer Disabled Disabled
50 msec
100 msec
200 msec
Spinup Delay Disabled Enabled
Disabled
Auto Scan Disabled Enabled
Disabled
Start Unit Disabled Enabled
Disabled
Environmental Variable Disabled Enabled
Disabled
Auto Boot Sector Disabled Enabled
Disabled
To reset parameters to their factory default settings:

1. On the main configuration menu (Figure 29), select Reset Adapter Defaults and press Enter. The following
message pop up (Figure 48) appears.
Broadcom
- 77 -
December 30, 2016 Resetting to Default Values
Figure 48 Reset Adapter Configuration to Defaults Pop Up
2. Press Y. All settings revert to their factory default values.

3. Press Esc to return to the previous menu.
Broadcom
- 78 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 7: Updating and Enabling Boot Code
December 30, 2016
Chapter 7: Updating and Enabling Boot Code

Broadcom provides utilities to update and enable boot code. The utility you use depends on the operating system
and, in some cases, the driver type or system architecture. The following table indicates the utilities currently available
for each operating system.
Table 8 Utilities that Update and Enable Boot Code
Utilities Windows Linuxa VMwareb Solaris
OneCommand CNA Manager GUI X X X X

OneCommand CNA Manager CLI X X X X
Offline Utilities X X
UEFI Utilities X X X
OneCommand CNA Manager for VMware X
vCenter
OneConnect Flash Utilityc X X X X
CIM Provider X
ethtool X
FCA brcmadm Utility X
a. For the Citrix operating systems, the OneCommand CNA Manager application CLI is not supported locally, but can be
managed using a remote system. The OneCommand CNA Manager GUI application is not supported.
b. For VMware operating systems, the OneCommand CNA Manager application GUI and CLI are not supported locally,
but can be run remotely using a Windows system.
c. Not supported on IA64–based servers.
After you decide which utility to use, see the appropriate documentation for the proper procedures:
 OneCommand CNA Manager application – Refer to the OneCommand CNA Manager Application User Guide for
OneConnect Adapters or the OneCommand CNA Manager Command Line Interface User Guide for OneConnect
Adapters.
 Offline utilities – Refer to the Brcmflash and Lpcfg Management Utilities User Guide for OneConnect Adapters.
 UEFI utilities
— See Chapter 11, Configuring UEFI for Ethernet.
— See Chapter 12, Configuring UEFI for iSCSI.
— See Chapter 13, Configuring UEFI for FCoE.
 OneCommand CNA Manager for VMware vCenter – Refer to the OneCommand CNA Manager for VMware
vCenter User Guide for OneConnect Adapters.
 OneConnect Flash Utility – Refer to the Using the OneConnect Flash Utility to Update OneConnect Adapter
Firmware guide.
 CIM Provider – Refer to the CIM Provider Package Installation Guide for OneConnect Adapters.
 ethtool – Refer to the Emulex Drivers for Linux User Guide for OneConnect Adapters.
 FCA emlxadm utility – Refer to the FCA Utilities for Solaris User Guide for OneConnect Adapters.
Broadcom
- 79 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 8: Configuring iSCSI Boot Support with the iSCSISelect Utility
December 30, 2016 Navigating the iSCSISelect Utility
Chapter 8: Configuring iSCSI Boot Support with the iSCSISelect

Utility
This section provides quick installation instructions for setting up a basic boot configuration. For more information on
setting up an iSCSI initiator and adding an iSCSI target, see Chapter 9, Configuring and Managing the iSCSI Initiator
with the iSCSISelect Utility and Chapter 10, Configuring and Managing iSCSI Targets with the iSCSISelect Utility.
8.1 Navigating the iSCSISelect Utility
Use the following methods to navigate the iSCSISelect utility:

 Press the Tab key to move to the next field, and press shiftbar+Tab key to move to the previous field.
 Press Enter to accept a selection, select a menu option, to select a row in a configuration dialog, or to change a
configuration default.
8.2 Setting Up a Basic iSCSI Boot Configuration
By setting up a basic iSCSI boot configuration, you can configure the initiator, contact network devices, and set up an
iSCSI boot target. With iSCSI boot capability, the iSCSISelect utility can quickly and easily provide the target LUN disk
to the operating system through the BIOS. After setting up a basic iSCSI boot configuration, you can continue to use
the iSCSISelect utility to manage the Emulex OneConnect server iSCSI SAN environment.
When setting up a basic iSCSI boot configuration do the following:
 Configure the iSCSI initiator name and enable boot support
 Configure the network properties
 Add an iSCSI target and enable it as a boot target
 Set the boot LUN
 Reboot the system
To set up a basic iSCSI boot configuration:
2. From the following iSCSI Initiator Configuration dialog, set the initiator name.
Figure 49 iSCSI Initiator Configuration Dialog
3. Select Save and press Enter to save the initiator name.

4. Select Controller Configuration and press Enter.
— If you are running a single adapter, the Controller Configuration menu (Figure 51) appears.
Broadcom
- 80 -
December 30, 2016 Setting Up a Basic iSCSI Boot Configuration
— If you are running multiple adapters, the following Controller Selection menu appears.
5. From the Controller Selection menu (Figure 50), select the adapter and port then press Enter. For more
information, see Section 9.1, Selecting an Adapter.
6. After selecting the adapter, the following Controller Configuration menu appears.
Figure 51 Controller Configuration Menu
7. From this menu, select Controller Properties and press Enter. The following Controller Properties dialog
(Figure 52) appears. For more information on the Controller Properties dialog, see Section 9.2, Viewing the
Controller Properties.
Figure 52 Controller Properties Dialog
8. Verify that Boot Support is set to Enabled.

10. From the Controller Configuration menu (Figure 51), select Network Configuration and press Enter. The following
Network Configuration dialog (Figure 53) appears.
Broadcom
- 81 -
December 30, 2016 Booting the System
Figure 53 Network Configuration Dialog
11. Configure a network IP address. From the Network Configuration dialog, you can do the following:
— Select the IP version (IPv4, IPv6, or Dual). For more information, see Section 9.3.1, Selecting the IP Version.
— Set up an IP address. For more information, see Section 9.3.3, Configuring an IP Address.
12. If desired, configure a VLAN ID. For more information, see Section 9.3.2, Configuring VLAN ID and VLAN Priority.
13. After configuring the network, you can add a SCSI target. From the Controller Configuration menu (Figure 51),
select iSCSI Target Configuration, then select Add a New iSCSI Target. For more information, see Section 10.1,
Adding iSCSI Targets.
14. After configuring the iSCSI initiator and target, reboot the system.
8.3 Booting the System
After setting up the basic boot configuration, exit the iSCSISelect utility and the system automatically reboots. During
the next boot, the iSCSI BIOS logs into the configured iSCSI boot target and displays its target and LUN information in
the BIOS sign-on banner. For example:
<<< Press <Ctrl><S> for iSCSISelect(TM) Utility >>>
iSCSI#0 Port#1 Base 0x00000380002A0000 @ Bus:1B Dev:00 Fun:02

iSCSI#0 Port#2 Base 0x00000380002E0000 @ Bus:1B Dev:00 Fun:03
Initiator iSCSI Name: iqn.2014-05.com.emulex:iscsi-dell-init

Controller #0:0 Initiator IPV6 Address: FE80:0:0:0:290:FAFF:FE6B:BA2D
Controller #0:0 Initiator IPV4 Address: 0.0.0.0
Controller #0:1 Initiator IPV6 Address: FE80:0:0:0:290:FAFF:FE6B:BA35
Drive #0 MSFT VirtualHD 0 30720 MB

Drive Geometry 3FF 3F FF
BIOS Installed Successfully!
Broadcom
- 82 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 9: Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility
December 30, 2016 Selecting an Adapter
Chapter 9: Configuring and Managing the iSCSI Initiator with the

iSCSISelect Utility
The iSCSI initiator or host (also known as the iSCSI client) is a system that attaches to an IP network and initiates
requests and receives responses from an iSCSI target. Each iSCSI host is identified by a unique IQN.
After the initiator host system is running, you must configure the initiator to allow access to the iSCSI SAN. To do this,
you must:
1. Select an adapter. For more information, see Section 9.1, Selecting an Adapter.
2. Configure network properties. For more information, see Section 9.3, Configuring Network Properties.
9.1 Selecting an Adapter
To select an adapter:
1. Log in to the iSCSISelect utility by pressing the Ctrl-S keys when prompted. The system displays the Controller
Selection Menu.
2. Select an adapter to configure the iSCSI target. The following Controller Configuration menu (Figure 55) appears.
From this menu, you can configure and manage the iSCSI initiator and targets.
To verify that you are configuring the correct port, either:

 Perform port identification; for more information, see Section 9.4, Identifying a Port.
 Check the link status by connecting the port to a 10Gb/s switch port and checking the link status in the Network
Configuration dialog (Figure 57); if the status is Link Up, it is the correct port.
NOTE Verify that you back out of the Network Configuration dialog to the
Controller Configuration menu before checking the Network
Configuration dialog. This allows the Link Status field to refresh when
you insert or remove the cable from the adapter.
Broadcom
- 83 -
December 30, 2016 Viewing the Controller Properties
9.2 Viewing the Controller Properties
The Controller Properties dialog displays adapter information and allows you to configure adapter options such as
boot support, IPv4 boot target discovery using DHCP, MPIO port configuration, and the iSCSI initiator name.
To view the adapter properties:
1. From the Controller Configuration menu (Figure 55), select Controller Properties and press Enter. The Controller
Properties dialog appears.
Figure 56 Controller Properties Dialog
9.2.1 Enabling Boot Support
Boot support is provided for each port or function. If boot support is enabled, you can boot from the specified
function. If boot support is disabled, you will not be able to boot from the function.
To enable boot support:
1. From the Controller Properties dialog (Figure 56), select Boot Support and press Enter. A pop up appears.
3. To save your changes, select Save and press Enter.
9.2.2 Enabling IPv4 Boot Target Discovery using DHCP
To enable IPv4 boot target discovery using DHCP:

1. From the Controller Properties dialog (Figure 56), select Discover IPv4 Boot Target via DHCP and press Enter. A
pop up appears.
9.2.3 Enabling the MPIO Port
MPIO support allows the initiator to log in dual sessions to the same target. In this way I/O can be sent over either
TCP/IP connection to the target. If one session fails, another session can continue processing I/O without interrupting
the application. In iSCSI target configuration, you have the option of setting dual network paths to a single boot LUN.
sessions, the iSCSI BIOS limits the number of sessions to two iSCSI
sessions for a single boot LUN.
Broadcom
- 84 -
Follow these steps to configure MPIO boot support for each operating system.
1. Use the Emulex iSCSI configuration utility to configure the first path to a boot target.
2. Complete normal operating system installation.
3. Install third-party MPIO software for your operating system.
4. Configure the second path to a single boot LUN through the Emulex iSCSI configuration utility.
To enable MPIO support:
1. From the Controller Properties dialog (Figure 56), select MPIO Port and press Enter. A pop up appears.
9.2.4 Configuring the iSCSI Initiator Name
The iSCSI initiator name is a unique identifier for the initiator on the network and configures target access. It must be
unique to that system on the network and is identified by an IQN. The iSCSI initiator name is global to the entire
system. The iSCSI initiator name must also match the target's ACL. After you log in to the iSCSISelect utility, you can
configure the iSCSI initiator name from the iSCSI Initiator Configuration dialog.
NOTE When installing Microsoft software iSCSI initiator service, the iSCSI
initiator name for the Emulex OneConnect adapter will change and
any IQN name previously configured through the iSCSISelect utility
will be overridden. Though this will not affect existing boot sessions
and persistent sessions, new target logins can fail because the new
IQN name may not match the incoming initiator IQN names
configured on the target. To avoid this situation, after installing
Microsoft software, you must rename the IQN name to the IQN name
you had configured previously.
To configure the iSCSI initiator name:
1. From the Controller Properties dialog (Figure 56), select iSCSI Initiator Name and press Enter.
2. Set or change the iSCSI initiator name.
NOTE If there are multiple adapters in the system, the iSCSI initiator name
may be different for each adapter. If this happens, an error message
indicates an iSCSI initiator name mismatch. You must save a new
initiator name so the iSCSI initiator names match on all of the adapters.
If there were pre-existing sessions before the iSCSI initiator name
change, the pre-existing sessions use the original name that was used
to log in the first time. The new name is used for any sessions added
after the name change.
For Emulex adapters, the iSCSI Initiator Name setting is global across
all ports on the same adapter. Changing one port to a new initiator
name causes the other ports to reflect the new initiator name.
Some vendor adapters allow you to assign each port a different
initiator name, or all ports can have the same initiator name.
3. Select Save and press Enter to save the iSCSI initiator name.
Broadcom
- 85 -
December 30, 2016 Configuring Network Properties
9.3 Configuring Network Properties
The Network Configuration dialog displays the MAC address, port speed, and link status for the adapter. From the
Network Configuration dialog, you can configure the following items:
 IP version
 VLAN ID/priority
 IPv4 or IPv6 address
NOTE Certain menu items may not be available depending on the selected
IP Version.
To view the network configuration:
From the Controller Configuration menu (Figure 55), select Network Configuration and press Enter. The Network
9.3.1 Selecting the IP Version
To select the IP version:

1. From the Network Configuration dialog (Figure 57), select IP Version and press Enter. A pop up appears.
2. Select IPv4, IPv6, or DUAL and press Enter.
3. Select Save and press Enter to save the IP version.
9.3.2 Configuring VLAN ID and VLAN Priority
A VLAN is a way to partition the network. If the LAN is made up of all devices within a broadcast domain, a VLAN is a
broadcast domain made up of switches. You first create a VLAN and then assign ports to it. All ports in a single VLAN
are in a single broadcast domain.
You do not have to configure VLANs unless the network is already using them. Some reasons to use a VLAN include:
 A LAN increases in size with several devices.
 A LAN has increased broadcast traffic on it.
 Groups of users on a LAN need more security.
A VLAN ID, like an IP address or initiator name, is assigned a value to uniquely identify it on a network. A VLAN priority
is set to determine priority order for packets within a VLAN.
Broadcom
- 86 -
To configure a VLAN ID and VLAN priority:

1. On the Network Configuration dialog (Figure 57), select Configure VLAN ID/Priority and press Enter. The Configure
VLAN ID/Priority dialog appears.
Figure 58 Configure VLAN ID/Priority Dialog
2. Navigate to VLAN Support and select Enabled.

3. Set a VLAN ID number. This is a unique value you assign to each VLAN on a single device. Valid values range from
0 to 4094.
4. Set a VLAN priority, if necessary. This unique value assigns a priority to outbound packets containing a specified
VLAN ID. Valid values range from 0 to 7, with 0 the highest priority level.
6. Press Esc to return to the Network Configuration dialog.
9.3.3 Configuring an IP Address
An IP address is a logical address for the adapter and uniquely identifies the system on a TCP/IP network. Depending
on the IP version you selected, you can either configure an IPv4 address or an IPv6 address.
9.3.3.1 Configuring an IPv4 Address

The IP address can be determined statically (manually assigned) or dynamically (the DHCP server obtains an IP
address). The method you choose depends on your network configuration. If your network uses a DHCP
configuration, you can enable DHCP and obtain an IP address from the DHCP server. If a DHCP server is not available,
you must configure a static IP address.
NOTE For all Linux-based operating systems, enable DHCP when attempting
to assign an IP address to an iSCSI port, because the iSCSI firmware will
not detect it as a duplicate IP address if one already exists on a Linux
server. Otherwise, you must manually verify that the IP address you
assign is not already used.
If you are using target discovery through DHCP, you must add the root
path to the DHCP server and enable DHCP discovery through the
iSCSISelect utility.
To configure an IPv4 address:
1. On the Network Configuration dialog (Figure 57), verify that the IP Version is set to IPv4.
2. Select Configure IPv4 Address and press Enter. The Configure IPv4 Address dialog appears.
Broadcom
- 87 -
Figure 59 Configure IPv4 Address Dialog
3. From the Configure IPv4 Address dialog, you can do the following:
— Enable DHCP for automatic assignment of the IP address through a DHCP server. See Section 9.3.3.1.1,
Enabling DHCP, for more information.
— Configure a static IP address (if DHCP is disabled). See Section 9.3.3.1.2, Configuring a Static IPv4 Address, for
more information.
— Ping the iSCSI initiator. See Section 9.3.3.2, Pinging the iSCSI Initiator, for more information.
9.3.3.1.1 Enabling DHCP

Enabling DHCP provides the initiator with an IP address.
NOTE If you are using the DHCP server to obtain an IP address for the iSCSI
initiator, set up a reservation. A reservation assigns a specific IP address
based on the MAC address of the iSCSI function. If you do not reserve
an IP address through DHCP, you must set the lease length for the iSCSI
initiator IP address to unlimited. This prevents the IP address lease
from expiring.
To enable DHCP:
1. From the Configure IPv4 Address dialog (Figure 59), select ENABLED from the DHCP pop up and press Enter.
2. Select Save and press Enter. The DHCP IP Address dialog box appears.
Figure 60 DHCP IP Address Dialog Box
NOTE If you set a static IP address, a message warns that the static IP address
will be lost. Press Y to continue with enabling DHCP.
3. Click OK.
9.3.3.1.2 Configuring a Static IPv4 Address

If a DHCP server is not available, you must manually configure a static IPv4 address.
To configure a static IP address:
1. From the Configure IPv4 Address dialog (Figure 59), verify that DHCP is disabled.
2. Enter the IP address. This is a unique 32-bit address that specifies the location of each device or workstation in the
network. This address is required for communication to the iSCSI SAN. For an initiator with its own network
interface, you must assign an IP address in the same range as the iSCSI SAN.
Broadcom
- 88 -
3. Enter the subnet mask. The subnet mask provides a way to segment networks. All hosts (iSCSI initiators or targets)
on the same physical network usually have the same subnet mask. For example, if the initiator is in the subnet
255.255.xxx.xxx, all the hosts (initiators or targets) in a sub-network will have the same subnet mask.
4. Enter the default gateway information, if necessary. A gateway is a router on a computer network that serves as
an access point to another network and that an initiator uses by default. Any data to addresses not on the
initiator’s subnet are sent through the default gateway.
5. Select Save and press Enter to save the settings.
6. When you are prompted to save the changes, type Y.
9.3.3.1.3 Configuring an IPv6 Address

1. On the Network Configuration dialog (Figure 57), verify that the IP Version is set to IPv6.
2. Select Configure IPv6 Address and press Enter. The Configure IPv6 Address dialog appears.
Figure 61 Configure IPv6 Address Dialog
3. From the Configure IPv6 Address dialog, you can do the following:
— Enable auto-configuration for automatic assignment of the IP address. See Section 9.3.3.1.1, Enabling DHCP,
— Configure a static IP address (if Auto Configuration is disabled). See Section 9.3.3.1.5, Configuring a Static IPv6
Address, for more information.
— Ping the iSCSI initiator. See Section 9.3.3.2, Pinging the iSCSI Initiator, for more information.
9.3.3.1.4 Enabling Auto Configuration

To automatically configure the IPv6 address, from the Configure IPv6 Address dialog (Figure 61), select ENABLED from
the Auto Configuration pop up and press Enter.
9.3.3.1.5 Configuring a Static IPv6 Address

If Auto Configuration is disabled, you must manually configure a static IPv6 address.
To configure a static IP address:
1. From the Configure IPv6 Address dialog (Figure 61), enter the following information in the corresponding fields:
— Link Local Address – The unique address assigned to the port which is available for use inside the local
network but not outside of the local network.
— Routable Address 1 – A routable address assigned to the iSCSI port.
— Routable Address 2 – A second routable address assigned to the iSCSI port.
— Default Gateway – A gateway is a router on a computer network that serves as an access point to another
network and that an initiator uses by default.
2. Select Save and press Enter to save the settings.
3. You are prompted to save the changes, type Y.
Broadcom
- 89 -
December 30, 2016 Identifying a Port
9.3.3.2 Pinging the iSCSI Initiator

After you configure the IPv4 or IPv6 address, you can confirm your network settings by pinging the network. The ping
option verifies that the IP address is on the network. If there is another IP entity on that network when you ping, you
receive a ping reply back to confirm the network settings. Ping can be a diagnostic tool but it is also a validation that
your network is set up properly prior to target login.
To verify that a target is accessible and that you are connected to the network:
1. From the Configure IPv4 Address dialog (Figure 59) or Configure IPv6 Address dialog (Figure 61), select Ping and
press Enter.
2. In the Ping Target dialog box, enter the IP address of the iSCSI device to ping. You are notified that the ping is
successful. If the ping is unsuccessful, you will receive a failed message. For more information, see Section 14.2,
Troubleshooting for the iSCSI Protocol. The following screen is an example of a successful ping.
Figure 62 Successful Ping
NOTE The ping works for any IP address that supports ICMP (Echo).
If you cannot verify the network interface, see Section 14.2, Troubleshooting for the iSCSI Protocol.
9.4 Identifying a Port
Port identification, or beaconing, helps you determine which port you are configuring by blinking both the link and
the activity LEDS of that port.
LEDs blink on the back of the server so there is no confusion as to which physical port you are configuring with the
iSCSISelect utility. Port identification lets you correlate the iSCSI software configuration with the hardware port.
NOTE Not all adapters have LEDs that are externally visible. If you are using
an add-in card in a blade server environment, port identification is not
supported.
To identify a port, from the Controller Configuration menu (Figure 55), select Port Identification and press Enter. The
LED status indicators for the selected port blink on the adapter until you select Done and press Enter on the Port
Identification pop up (Figure 63).
Figure 63 Port Identification Pop Up
Broadcom
- 90 -
December 30, 2016 Erasing the Current Configuration
9.5 Erasing the Current Configuration
Erase Configuration erases the configuration of a single adapter. Configuration data is erased for both ports on the
selected adapter. The initiator name is global for all Emulex OneConnect adapters in the system. If you have more than
one adapter and you erase the configuration on the first one, the Erase Configuration option resets the initiator names
back to their default values. If you erase the configuration on the second adapter, the default values are reset only for
the second adapter and are not reset globally on all adapters.
NOTE You must select Erase Configuration to clear out existing IQN data if
you purchase a different or subsequent license for the adapter.
To erase an adapter configuration:
1. From the Controller Configuration menu (Figure 55), select Erase Configuration and press Enter.
2. A message appears asking if you want to erase the current configuration. Type Y.
3. You are cautioned that the operation removes any existing configuration permanently. Type Y.
After the adapter configuration is erased, the system displays the Controller Configuration menu (Figure 55).
Broadcom
- 91 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 10: Configuring and Managing iSCSI Targets with the iSCSISelect Utility
December 30, 2016 Adding iSCSI Targets
Chapter 10: Configuring and Managing iSCSI Targets with the

iSCSISelect Utility
An iSCSI target is any device that receives iSCSI commands. The device can be an end node, such as a storage device,
or it can be an intermediate device, such as a bridge between IP and FC devices. Each iSCSI target is identified by a
unique IQN, and each port on the adapter (or on a bridge) is identified by one or more IP addresses.
As the client system, the initiator initiates disk I/O. It communicates with the target, and the target serves the initiator
by providing resources to the initiator.
After you configure the iSCSI initiator and have verified that the network interface is working, you can log in to the
target to establish the connection. To do this, you must:
 Perform a login to the target (adding a target).
 Ping a target and verify that you can connect to it.
 Reboot the system.
10.1 Adding iSCSI Targets
After the initiator has been configured, you must make an iSCSI target available to the initiator host. Targets can be
discovered automatically using the SendTargets discovery mechanism, or you can manually configure targets.
Before you begin the login session, gather the following information:
 iSCSI target name (manual configuration only) – The target name you are adding. This name should be known to
you based on how you configured the iSCSI target. For more information, see Section 10.1.1, Using the
SendTargets Discovery to Add an iSCSI Target.
 iSCSI target IP address – The IP address of the target into which you are logging.
 TCP port number – The TCP port number of the target portal. Typically this is 3260, which is the well-known port
number defined for use by iSCSI.
10.1.1 Using the SendTargets Discovery to Add an iSCSI Target
The iSCSI initiator uses the SendTargets discovery to locate names of available targets. Use this method if an iSCSI
node has a large number of targets.
To configure an iSCSI target using the SendTargets discovery:
2. Select Controller Configuration and press Enter. The system displays a list of adapters.
3. Select an adapter and press Enter. The following Controller Configuration menu appears.
Broadcom
- 92 -
4. Select iSCSI Target Configuration and press Enter. The following iSCSI Target Configuration dialog appears.
Figure 65 iSCSI Target Configuration Dialog
5. Select Add New iSCSI IPv4 Target or Add New iSCSI IPv6 Target and press Enter. The following Add iSCSI Target
dialog appears.
Figure 66 Add/Ping iSCSI Target Dialog
6. Leave the iSCSI Target Name blank.

7. Enter the iSCSI target IP address.
8. Change the TCP port number value, if necessary. The default target port number is 3260.
9. Leave the Boot Target field set to No for now; you will return to this field later to enable the boot target.
10. If you are connecting dual sessions to the same target portal group, enter a unique ISID Qualifier, which can be
any number up to 65535. For more information on when an ISID value must be changed, see Section 5.3.2,
11. Set the Header Digest to Yes if you want to enable the header digest. If the Header Digest is set to Yes, and the
iSCSI initiator is set accordingly, the integrity of an iSCSI protocol data unit’s header segment is protected by
CRC32C checksum. The default is disabled.
12. Set the Data Digest to Yes if you want to enable the data digest. If the Data Digest is set to Yes, and the iSCSI
initiator is set accordingly, the integrity of an iSCSI protocol data unit’s data segment is protected by CRC32C
checksum. The default is disabled.
13. Select an authentication method (optional). If you are enabling an authentication method, you are prompted to
enter the CHAP configuration. For more information, see Section 10.2.2.1, Enabling CHAP Authentication.
14. Select Save/Login. A message reminds you that you have left the iSCSI Target name blank and that the
SendTargets mechanism will be used. To continue, press Y.
15. After you send the SendTargets request, the firmware attempts to log in to the target. If it is successful, the Targets
Discovered Via SendTargets dialog (Figure 67) displays a list of targets.
Broadcom
- 93 -
Figure 67 Targets Discovered Via SendTargets Dialog
16. Select the targets you want to add from the list and press the F3 key.
17. Add these targets to the list of iSCSI targets available for the initiator to log in to by selecting Add Selected iSCSI
Targets, and press Enter. If you enabled CHAP Authentication, you are prompted to enter the CHAP configuration
for each target, one at a time. For more information, see Section 10.2.2.1, Enabling CHAP Authentication.
18. From the Controller Configuration menu (Figure 64), select iSCSI Target Configuration and press Enter to view the
added target information.
NOTE If you set the Boot Target option in step 5 before adding the target, the
Boot Target appears as No. To enable Boot Target, continue with step
19. Otherwise, you have completed the procedure.
19. To enable Boot Target or make any other changes to the targets, select the target and press Enter. The Edit/Ping
iSCSI Target dialog (Figure 70) appears. From this dialog, you can edit the target.
10.1.2 Manually Adding an iSCSI Target
Use this method if an iSCSI node has a small number of targets, or if you want to restrict the targets that an initiator
can access. To manually configure a target, you must provide the iSCSI target name.
To configure an iSCSI target manually:
3. Select an adapter and press Enter. The Controller Configuration menu (Figure 64) appears.
4. Select iSCSI Target Configuration and press Enter. The iSCSI Target Configuration dialog (Figure 68) appears.
5. Select Add New iSCSI Target and press Enter. The Add/Ping iSCSI Target dialog (Figure 66) appears.
6. Enter the iSCSI target name, iSCSI target IP address, and TCP port number (the default target port number is
3260).
7. If you want to enable the target as a boot target, select Yes.
Broadcom
- 94 -
December 30, 2016 Managing an iSCSI Target
11. Select the Authentication Method. For more information, see Section 10.2.2.1, Enabling CHAP Authentication.
12. Select Save/Login and press Enter. If the firmware logs into the target successfully, you receive a successful login
message. Press Esc to go to the iSCSI Target Configuration dialog (Figure 68), where you can view information
about the added target.
13. To enable Boot Target or make any other changes to the targets, select the target and press Enter.
10.2 Managing an iSCSI Target
With the iSCSISelect utility, you can manage a target by viewing target details or by editing the target configuration.
10.2.1 Viewing Target Information
After successfully logging in to the target, you can view the details of the newly added target or manage the target.
From the Controller Configuration menu (Figure 64), select iSCSI Target Configuration and press Enter to view the
target information.
NOTE The iSCSISelect utility shows LUN information for the first 128 LUNs
only.
The following screen is an example of a target detail.
Figure 69 iSCSI Target Configuration Information
In the iSCSI Target Configuration dialog, the function keys located at the bottom of the menu help you manage the
target configuration.
 Press Enter to select the target configuration.
 Press the Delete key to delete the target.
 Press the F5 key to log in to the target.
 Press the F6 key to log out of the target.
 Press the F7 key to configure the LUN.
 Press Esc to return to the previous menu.
10.2.2 Editing a Target Configuration
After adding a target, you can edit the iSCSI target configuration or apply other management options to the target.
Broadcom
- 95 -
NOTE If you want to change the target name, you must delete the existing
target and add it again with the new target name.
To edit a target configuration:
1. From the iSCSI Target Configuration dialog (Figure 68), select the target and press Enter. The following Edit/Ping
iSCSI Target dialog appears.
Figure 70 Edit/Ping iSCSI Target Dialog
2. If you want to enable the target as a boot target, select Boot Target and select either Primary or Secondary in the
Boot Target pop up.
6. To select an authentication method to use when logging in to the target, select an authentication method from
the Authentication Method pop up. For more information about authentication methods, see Section 10.2.2.1,
Enabling CHAP Authentication.
7. To verify the target connection, select Ping and press Enter. For more information about ping, see Section 10.1,
Adding iSCSI Targets.
8. To view more target properties, select Advanced and press Enter. For more information on these properties, see
Section 10.2.3, Viewing Advanced Target Properties.
9. To save your changes, select Save/Login and press Enter. The system displays the iSCSI Target Configuration
dialog with the revised information.
10.2.2.1 Enabling CHAP Authentication

The iSCSISelect utility uses CHAP to authenticate initiators and targets for added network security. By using a
challenge and response security mechanism, CHAP periodically verifies the initiator's identity. This authentication
method depends on a secret key known to the initiator and the target only. Although the authentication can be
one-way, you can negotiate CHAP in both directions with the help of the same secret set for mutual authentication.
You must make sure, however, that what you configure on the target side matches the initiator side. The iSCSISelect
utility supports both one-way and mutual authentication.
Broadcom
- 96 -
10.2.2.1.1 Authenticating One-Way CHAP

With one-way CHAP authentication, the target authenticates the initiator. Use one-way CHAP authentication for a
one-way challenge and response security method.
To enable one-way CHAP authentication:
2. Select Controller Configuration. The system displays a list of adapters.
5. Select Add New iSCSI Target and press Enter.
6. Follow steps 5 to 11 in Section 10.1.1, Using the SendTargets Discovery to Add an iSCSI Target.
7. On the Add/Ping iSCSI Target dialog (Figure 66), select Authentication Method, select One-Way Chap, and press
Enter. The CHAP Configuration dialog box (Figure 71) appears.
Figure 71 One-Way Chap Configuration Dialog Box
8. Enter the target CHAP name and target secret, then select OK and press Enter.
The target CHAP name can be any name or sequence of numbers consisting of 12 to 16 characters. However, the
name and secret on the target side must match the name and target on the initiator side.
The target secret can be in string (for example, abcdefg23456) or hexadecimal (for example,
0x01234567890123456789ABCD) format.
— For string format, the secret can be any name or sequence of numbers with a minimum of 12 and a maximum
of 16 bytes, where each character equals one byte.
— For hexadecimal format, the secret must be a minimum of 12 and a maximum of 16 bytes long, where two
characters equal one byte and the character length must be even (24, 26, 28, 30, or 32).
— The following restrictions apply to hexadecimal formatting:
 The 0x representation requires an even number of hexadecimal values excluding the 0x (0-9, A-F). For
example, the secret 0x1234567890123456789ABCD is not allowed because the character length is odd,
with 23 hexadecimal values excluding the 0x. The secret 0x01234567890123456789ABCD is allowed,
with 24 hexadecimal values excluding the 0x.
 The hexadecimal representation of CHAP secrets must contain hexadecimal values only. The 0x
representation may include only the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f, A, B, C, D, E,
and F. No other characters are allowed.
After enabling the CHAP authentication, the Add/Ping iSCSI Target dialog (Figure 66) appears. For more
information, see Section 10.2.2.2, Pinging a Target.
10.2.2.1.2 Authenticating Mutual CHAP

With mutual CHAP authentication, the target authenticates the initiator and the initiator authenticates the target. Use
mutual CHAP authentication for a two-way challenge and response security method.
To enable mutual CHAP authentication:
Broadcom
- 97 -
5. Select Add New iSCSI Target and press Enter. The Add/Ping iSCSI Target dialog (Figure 66) appears.
6. Select Authentication Method, select Mutual Chap, and press Enter. The following CHAP Configuration dialog box
Figure 72 Mutual CHAP Configuration Dialog Box
7. Enter the target CHAP name, target secret, initiator CHAP name, and initiator secret. Select OK and press Enter.
The target CHAP name can be any name or sequence of numbers with a minimum of 12 and a maximum of 16
characters. However, the name and secret on the target side must match the name and target on the initiator
side.
The target secret can be in string (for example, abcdefg23456) or hexadecimal (for example,
0x01234567890123456789ABCD) format.
— For string format, the secret can be any name or sequence of numbers with a minimum of 12 and a maximum
of 16 bytes, where each character equals one byte.
— For hexadecimal format, the secret must be a minimum of 12 and a maximum of 16 bytes long, where two
characters equal one byte and the character length must be even (24, 26, 28, 30, or 32).
— The following restrictions apply to hexadecimal formatting:
 The 0x representation requires an even number of hexadecimal values excluding the 0x (0-9, A-F). For
example, the secret 0x1234567890123456789ABCD is not allowed because the character length is odd,
with 23 hexadecimal values excluding the 0x. The secret 0x01234567890123456789ABCD is allowed,
with 24 hexadecimal values excluding the 0x.
 The hexadecimal representation of CHAP secrets must contain hexadecimal values only. The 0x
representation may include only the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f, A, B, C, D, E,
and F. No other characters are allowed.
After enabling the CHAP authentication, the Add/Ping iSCSI Target dialog (Figure 66) appears.
10.2.2.2 Pinging a Target

To ping a target:
1. From the Controller Configuration menu (Figure 64), select iSCSI Target Configuration and press Enter. The iSCSI
Target Configuration dialog (Figure 68) appears.
2. Select Add/Ping iSCSI Target or Edit/Ping iSCSI Target and press Enter. The iSCSI Target IP Address is the address
that will be pinged.
3. From the Add/Ping iSCSI Target dialog (Figure 66) or the Edit/Ping iSCSI Target dialog (Figure 70), select Ping and
press Enter.
The following Ping Target information displays the results of the ping.
Broadcom
- 98 -
Figure 73 Ping Target Results
A ping can be unsuccessful for several reasons; for more information, see Section 14.2, Troubleshooting for the
iSCSI Protocol.
10.2.3 Viewing Advanced Target Properties
After logging in to a target, you can view more information about it by navigating to the Edit/Ping iSCSI Target dialog
(Figure 70), selecting the Advanced option, and pressing Enter. The Advanced Target Properties dialog appears.
Figure 74 Advanced Target Properties Dialog
10.2.4 Configuring LUN Settings
A LUN represents an individually addressable logical device that is part of a target. An initiator negotiates with a target
to establish connectivity to a LUN.
To configure a LUN:
1. From the iSCSI Target Configuration dialog (Figure 68), press the F7 key to show the LUNs associated with the
iSCSI node.
Broadcom
- 99 -
Figure 75 LUN Configuration Menu
2. If the target is a boot target, press the F3 key to set the boot LUN. By setting the LUN to bootable, you can confirm
that the boot target is configured properly and you can see the LUN that is booting. By looking at the LUN size,
you can also identify each target along with its LUN order.
NOTE The LUN order is determined by the target and is in the order listed.
If there are no LUNs available, the system displays the following message:
No LUN available, please check your configuration on the Target.
For more information, see Section 14.2, Troubleshooting for the iSCSI Protocol.
10.2.5 Logging In to and Out of a Configured Target
To log in to a target, from the iSCSI Target Configuration dialog (Figure 68), select the disconnected target, and then
press the F5key to establish the target session.
If you log out of a target, it is still included in the target list, with the status of disconnected. You are deleting the target
session only; you can log back in to it.
To log out of a target, from the iSCSI Target Configuration dialog (Figure 68), select the target and press the F6 key.
10.2.6 Removing a Configured Target
To fully remove a target, from the iSCSI Target Configuration dialog (Figure 68), select the disconnected target and
press the Delete key.
10.2.7 Booting the System
After configuring the iSCSI initiator and target, you must reboot the system for the configurations to take effect. When
you exit the iSCSISelect utility, the system automatically reboots, and during system startup the Emulex adapter BIOS
information appears. For example:
Broadcom
- 100 -
December 30, 2016 Discovering Targets through DHCP for iSCSI
<<< Press <Ctrl><S> for iSCSISelect(TM) Utility >>>
iSCSI#0 Port#1 Base 0x00000380002A0000 @ Bus:1B Dev:00 Fun:02

iSCSI#0 Port#2 Base 0x00000380002E0000 @ Bus:1B Dev:00 Fun:03
Initiator iSCSI Name: iqn.1990-07.com.emulex:00-90-fa-6b-ba-2c

Controller #0:0 Initiator IPV6 Address: FE80:0:0:0:290:FAFF:FE6B:BA2D
Controller #0:1 Initiator IPV6 Address: FE80:0:0:0:290:FAFF:FE6B:BA35
<Ctrl><S> Pressed-Utility will be invoked after BIOS initialization.
NOTE The iSCSI BIOS logs into the configured iSCSI boot target and shows its
target and LUN information in the BIOS sign-on banner only if you
have configured an iSCSI boot target. For more information, see
Section 8.2, Setting Up a Basic iSCSI Boot Configuration.
10.3 Discovering Targets through DHCP for iSCSI
For the target to be discovered by the initiator through DHCP, you must add the root path to the DHCP server:
1. From the following DHCP server window (Figure 76), select Scope Options, then right-click and select Configure
Options.
Figure 76 DHCP Server Window
2. From the General tab shown in the following dialog (Figure 77), select 017 Root Path.
Broadcom
- 101 -
December 30, 2016 Enabling DHCP Discovery through the iSCSISelect Utility
Figure 77 DHCP Server Scope Options
3. In the String Value field, add the location of the iSCSI target you want to use for iSCSI boot. Enter the string in the
following format:
iscsi: <ipaddress>:<protocol>:<iscsi port number>:<luns><target name>
For example:
iscsi:010.010.010.001:0:3260:0:iqn.1992-08.com.netap:sn.15729740
4. Click Apply. The DHCP server window is ready to discover boot targets.
10.4 Enabling DHCP Discovery through the iSCSISelect Utility
If the DHCP server supports DHCP discovery and you added the root path to the DHCP server, you can enable boot
target discovery using DHCP with the iSCSISelect utility. By enabling Discover IPv4 Boot Target via DHCP, you can use
DHCP discovery to provide the boot path from the DHCP server.
NOTE If you leave Discover IPv4 Boot Target via DHCP disabled (default), you
must manually configure iSCSI boot.
To enable DHCP discovery through iSCSISelect:
1. After configuring the iSCSI Initiator Name, select Controller Properties from the Controller Configuration menu
(Figure 64) and press Enter.
2. From the Controller Properties menu, select Discover IPv4 Boot Target via DHCP and press Enter. A pop up
appears.
3. To enable the function, select Enabled and press Enter.
Broadcom
- 102 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 11: Configuring UEFI for Ethernet
December 30, 2016 Navigating the Emulex NIC Configuration Utility
Chapter 11: Configuring UEFI for Ethernet

The UEFIBoot supports:
 UEFI version – 2.3.1 compatible drivers (backward compatible with 2.1)
 EDK2 compatible drivers
 The following UEFI protocols:
— NII protocol
— Configuration Access protocol
— Component Name2 protocol
— Driver Diagnostics protocol
— Platform to Driver Configuration protocol
— Firmware Management Protocol
 Switching of personalities from the HII menus using the multimode feature
 Enabling, disabling, and configuring UMC from HII
 Lenovo System x Blade Open Firmware Management Protocol and Universal Configuration Manager
NOTE Applies to Lenovo System x products only.

 Up to 96 physical adapters or 192 ports
 Single driver – support for all adapters in the system
This version of UEFIBoot is loaded from flash into system memory.
For more information on loading and unloading UEFIBoot, see Appendix E, Loading and Unloading UEFIBoot from the
UEFI Shell.
If UEFIBoot is loaded in a UEFI Shell, type drivers and press Enter to see if the driver is loaded.
NOTE If you are using a Dell adapter, see Appendix F, Dell UEFI for
information on using the Dell UEFI utility.
11.1 Navigating the Emulex NIC Configuration Utility
Use the following methods to navigate the Emulex NIC configuration utility:
 Press the up/down arrows on the keyboard to move through menu options or fields. If multiple adapters are
listed, use the up/down arrows to scroll to the additional adapters.
 Press the +, -, or Enter keys to change numeric values.
 Press Enter to select a menu option, to select a row in a configuration dialog, or to change a configuration default.
 Use the navigation entries on the page to move about the utility.
 Press Esc to exit the current screen and show the previous screen.
NOTE HP adapters in HP systems use the F10 key to save the current
configuration settings.
Broadcom
- 103 -
December 30, 2016 Starting the Emulex NIC Configuration Utility
11.2 Starting the Emulex NIC Configuration Utility
Depending on the vendor UEFI configuration, the Emulex NIC configuration utility may appear under different setup
menus in the vendor system firmware or BIOS (such as System Settings > Network).
To start the Emulex NIC configuration utility using the HII:
1. The Network dialog (Figure 78) shows a list of the adapters in the system. Your list may vary depending on the
installed adapters.
Figure 78 Network Dialog
2. Select an adapter and press Enter. The Emulex NIC Selection dialog (Figure 79) appears.
Broadcom
- 104 -
Figure 79 Emulex NIC Selection Dialog
The Emulex NIC Selection dialog shows the following adapter information and configuration options:
NOTE Some of the following options may or may not appear depending on
your adapter and the system in which it is installed.
— Firmware Version – The current firmware version installed on the adapter. The firmware version is the same
as the boot version.
— IPL Version – The current version installed on the adapter.
— EFI Driver Version – The current version of the EFI driver installed on the adapter.
— PCI Bus:Device:Function – The PCI bus, device, and function for the adapter. This information describes the
location of the adapter in the PCI configuration space.
— Link Speed – The current maximum port speed on the adapter.
— Advanced Mode (not shown) – See Section 11.2.1, Advanced Mode Support, for more information.
— Multichannel Mode – See Section 11.2.8, Configuring Universal Multichannel, for more information.
— Global SRIOV – The SRIOV setting on an adapter level. The SRIOV setting can be enabled on a port basis, only
if this parameter is set to Enabled.
— Controller Configuration – The available menu options depend on whether UMC is enabled or disabled. See
Section 11.2.7, Configuring the Adapter If UMC Is Disabled or Not Supported, or Section 11.2.8, Configuring
Universal Multichannel, for more information.
— Boot Mode (not shown) – See Section 11.2.2, Configuring Boot Mode, for more information.
NOTE If the system BIOS supports boot mode configuration, this feature is
not displayed in the menu.
— iBFT Configuration (not shown)- This menu is available only if Boot mode is disabled. See Section 11.2.3,
Configuring iBFT, for more information.
Broadcom
- 105 -
NOTE If the system BIOS supports iBFT configuration, this feature is not
displayed in the menu.
— Port Management – See Section 11.2.10, Port Management, for more information.
— Personality – See Section 11.2.4, Configuring Personality, for more information.
— Link Reconfiguration (not shown) – See Section 11.2.5, Link Reconfiguration, for more information.
— NIC Configuration – See Section 11.2.6, Configuring Virtual LAN Settings, for more information.
NOTE This menu item is available only when Multichannel mode is disabled.
— Emulex Flash Update Utility – See Section 11.3, Downloading Firmware and Boot Code, for more
information.
— FoD (Lenovo only; not shown) – See Section 11.2.11, Feature on Demand, for more information.
— Port Identification (not shown) – See Section 11.4, Identifying a Port, for more information.
— Erase Configuration (not shown)– See Section 11.5, Erasing Ports and Adapter Configurations, for more
information.
NOTE The Erase Configuration option is not available on HP adapters in HP

systems. Instead, use the F7 key to reset the configuration settings to
their factory default settings.
11.2.1 Advanced Mode Support
Advanced mode is a driver compatibility option. With Advanced mode enabled, you can run Advanced mode-aware
drivers that provide advanced capabilities as listed in the following table. With Advanced mode disabled, you can run
older legacy inbox drivers that are not Advanced mode-aware with the latest firmware versions.
NOTE Advanced mode support is enabled by default on Emulex

OCe11100-series two-port and four-port adapters. On four-port
adapters, the Advanced mode setting is not provided in the HII
utilities. The Advanced mode setting on these platforms is implicitly
enabled and Advanced mode-aware drivers must be installed.
Compatibility with legacy drivers requires that Advanced mode
support be disabled on two-port adapters.
Advanced mode is automatically enabled on Emulex
OCe14000-series adapters and it cannot be disabled.
Table 9 Advanced Mode Capabilities (by Operating System)

(Legacy Mode)
Windows 16 RSS queues 4 RSS queues
NOTE Supported on Windows Server 2008 R2 and
later versions only.
VMQ lookahead split Lookahead split is silently ignored. A small
performance penalty for VMQs may occur.
NOTE VMQs are supported on Windows Server 2008
R2 and later versions only.
Broadcom
- 106 -
Table 9 Advanced Mode Capabilities (by Operating System) (Continued)

(Legacy Mode)
Linux and Citrix 16 RSS queues 4 RSS queues
VFs and PFs can be increased up to 30.
VMware ESXi For both 1500 and 9000 MTU: 1500 MTU – 8 NetQueues per PF in non-VFA and
16 NetQueues per PF in non-VFA 4 NetQueues per PF in VFA.
4 NetQueues per PF in VFA 9000 MTU – 4 NetQueues per PF in both VFA and
non-VFA.
To configure Advanced mode support:
NOTE Changing the Advanced mode setting requires a reboot.

1. On the Emulex NIC Selection dialog (Figure 80), select Advanced mode and press Enter. A pop up appears.
Figure 80 Emulex NIC Selection Dialog with Advanced Mode Displayed
2. Select Enable or Disable and press Enter.

3. Reboot the system.
11.2.2 Configuring Boot Mode
This setting configures the boot mode.

 Enable – iSCSI hardware initiator boot mode
 Disable – iSCSI software initiator boot mode
NOTE If boot mode is disabled, the iBFT Configuration menu is available.
Broadcom
- 107 -
To configure boot mode:

1. On the Emulex NIC Selection dialog (Figure 79), select Boot Mode and press Enter. A pop up appears.
11.2.3 Configuring iBFT
NOTE Boot mode must be set to Disable to access the iBFT Configuration
menu.
Configuring iSCSI through the NIC interface (iBFT) is exactly the same as normal iSCSI configuration except it is
performed through the NIC interface. For this to occur, you must use the operating system’s NIC driver and an
iBFT-aware operating system.
To configure iBFT:
1. On the Emulex NIC Selection dialog (Figure 79), select iBFT Configuration and press Enter.
The iBFT Configuration dialog appears.
Figure 81 iBFT Configuration Dialog
The iBFT Configuration dialog enables you to perform the following tasks:
 Edit the iSCSI initiator name
 Enable multipath I/O
 Configure the CHAP authentication mode
 Configure the network settings
 Configure the primary or secondary targets
After completing the iBFT configuration, save your changes.
To save changes:
1. Press Esc to return to the Emulex NIC Selection dialog (Figure 79).
2. Select Save Changes and press Enter.
Broadcom
- 108 -
11.2.3.1 Changing the iSCSI Name

To edit the iSCSI initiator name:
1. On the iBFT Configuration dialog (Figure 81), select iSCSI Name and press Enter.
This is a global setting. The iSCSI initiator name configured on one adapter is reflected on all adapters in the
system.
NOTE HP systems are an exception to the previous statement. Each port on

an HP system can be configured with a unique initiator name.
11.2.3.2 Selecting MPIO

TCP/IP connection to the target. If one session fails, another session can continue processing I/O without interruption
to the application. In iSCSI target configuration, you have the option of setting dual network paths to a single boot
LUN.
You must follow these steps to configure MPIO boot support for each operating system.
To configure MPIO:
1. On the iBFT Configuration dialog (Figure 81), select Multipath I/O and press Enter. A pop up appears.
11.2.3.3 Configuring CHAP Authentication Mode

Broadcom uses the CHAP authentication method to authenticate initiators and targets for added network security. By
using a challenge and response security mechanism, CHAP periodically verifies the initiator's identity. This
authentication method depends on a secret key known to the initiator and the target only. Although the
authentication can be one-way, you can negotiate CHAP in both directions with the help of the same secret set for
mutual authentication. You must make sure however, that what you configure on the target side matches the initiator
side. Both one-way and mutual authentication are supported.
To configure the CHAP authentication method:
1. On the iBFT Configuration dialog (Figure 81), select CHAP Authentication Mode and press Enter. The system
displays a pop up.
2. Select None, One-way CHAP, or Mutual CHAP and press Enter.
— One-way CHAP – With one-way CHAP authentication, the target authenticates the initiator. Use one-way
CHAP authentication for a one-way challenge and response security method – you must configure the CHAP
ID and CHAP Secret, which is authenticated by the target.
— Mutual CHAP – With mutual CHAP authentication, the target authenticates the initiator and the initiator
authenticates the target. Use mutual CHAP authentication for a two-way challenge and response security
method – you must configure different CHAP and mutual CHAP IDs and CHAP secrets.
NOTE If you configure the CHAP parameters, verify that those parameters
match the parameters on the storage side.
Broadcom
- 109 -
3. Enter the appropriate CHAP ID and CHAP Secret and press Enter.
11.2.3.4 Configuring Network Settings

To configure the network settings:
1. On the iBFT Configuration dialog (Figure 81), select Network Configuration and press Enter. The Network
The Network Configuration dialog enables you to perform the following tasks:
 Configure the initiator’s IP version
 Configure TCP/IP parameters using DHCP
NOTE This option is available only if IPv4 is selected as the IP version.

 Configure iSCSI parameters using DHCP
NOTE This option is available only if TCP/IP Parameters via DHCP is enabled.
 Select the virtual LAN mode
After completing the network configuration, save your changes.
To save changes:
1. Press Esc to return to the iBFT Configuration dialog (Figure 81).
2. Press Esc again to return to the Emulex NIC Selection dialog (Figure 79).
11.2.3.4.1 Configuring the Initiator IP Version

To configure the initiator IP version:
1. On the Network Configuration dialog (Figure 82), select IP version and press Enter. The system displays a pop up.
2. Select IPv4, IPv6, or None and press Enter.
Broadcom
- 110 -
11.2.3.4.2 Configuring TCP/IP Parameters Using DHCP
NOTE This option is available only if IPv4 is selected as the IP Version.

This option controls the source of the initiator’s IP address through DHCP or static assignment.
To configure TCP/IP parameters using DHCP:

1. On the Network Configuration dialog (Figure 82), select TCP/IP Parameters via DHCP and press Enter. A pop up
appears.
3. If this setting is disabled, you must enter the following information for the iSCSI initiator:
— IPv4 address
— Subnet mask
— IPv4 default gateway
11.2.3.4.3 Configuring iSCSI Parameters Using DHCP
NOTE This option is available only if TCP/IP Parameters via DHCP is enabled.
This option enables you to retrieve the iSCSI target parameters using DHCP.
To configure iSCSI parameters using DHCP:
1. On the Network Configuration dialog (Figure 82), select iSCSI Parameters via DHCP and press Enter. The system
displays a pop up.
11.2.3.4.4 Selecting Virtual LAN Mode

If virtual LAN mode is enabled, a VLAN tag can be used by iSCSI boot.
To enable virtual LAN mode:
1. On the Network Configuration dialog (Figure 82), select Virtual LAN Mode and press Enter. The system displays a
pop up.
2. Select Enabled and press Enter.
11.2.3.5 Configuring the Primary and Secondary Targets

To configure the iSCSI target parameters:
1. On the iBFT Configuration dialog (Figure 81), select Primary Target or Secondary Target and press Enter.
NOTE Configuration of the primary and secondary targets is identical. For

this reason, this section covers the configuration of the primary target
only.
The Primary Target dialog (Figure 83) appears.
Broadcom
- 111 -
Figure 83 Primary Target Dialog
The Primary Target dialog enables you to configure the following items:
 Boot target
 iSCSI target name
 Target IP version
 Target IP address
 Target ISID qualifier
 Target TCP port
 Target boot LUN
 Target CHAP ID and secret
NOTE These options are available only if the initiator’s CHAP authentication
mode is properly set.
After completing the primary or secondary target configuration, you must save your changes.
To save changes:
1. Press Esc to return to the Emulex NIC Selection dialog (Figure 79).
11.2.3.5.1 Configuring the Boot Target
NOTE Only one boot target can be enabled at a time. If the primary target has
the boot target setting enabled, the secondary target must have the
boot target setting disabled.
To configure the boot target:
1. On the Primary Target dialog (Figure 83), select Boot to Target and press Enter. The system displays a pop up.
Broadcom
- 112 -
11.2.3.5.2 Changing the Target iSCSI Name

This setting specifies the IQN of the specified target.
To edit the iSCSI target name:
1. On the Primary Target dialog (Figure 83), select iSCSI Name and press Enter.
2. Edit the target name and press Enter.
11.2.3.5.3 Configuring the Target IP Version

To configure the target IP version:
1. On the Primary Target dialog (Figure 83), select IP version and press Enter. A pop up appears.
2. Select IPv4 or IPv6 and press Enter.
11.2.3.5.4 Configuring the Target IP Address

To configure the target IP address:
1. On the Primary Target dialog (Figure 83), select IP Address and press Enter.
2. Enter the target IP address and press Enter.
11.2.3.5.5 Configuring the Target ISID Qualifier

If you are connecting dual sessions to the same target portal group, enter a unique ISID Qualifier, which can be any
number up to 65535. For more information on when an ISID value must be changed, see Section 5.3.2, Booting from
SAN for iSCSI MPIO.
To configure the target ISID qualifier:
1. On the Primary Target dialog (Figure 83), select ISID Qualifier and press Enter.
2. Enter the target ISID qualifier value and press Enter.
11.2.3.5.6 Configuring the Target TCP Port

To configure the target TCP port:
1. On the Primary Target dialog (Figure 83), select TCP Port and press Enter.
2. Enter the target TCP port value and press Enter.
11.2.3.5.7 Configuring the Target Boot LUN

To configure the target boot LUN:
1. On the Primary Target dialog (Figure 83), select Boot LUN and press Enter.
2. Enter the target boot LUN value and press Enter.
11.2.3.5.8 Configuring the Target CHAP ID and Secret
NOTE These options are available only if the initiator’s CHAP authentication
mode has been properly set.
To configure the target CHAP ID and secret:
1. Ensure that the initiator’s CHAP authentication mode is properly set.
2. On the Primary Target dialog (Figure 83), select CHAP ID and press Enter.
3. Enter the target CHAP ID value and press Enter.
4. Select CHAP Secret and press Enter.
5. Enter the target CHAP secret value and press Enter.
Broadcom
- 113 -
11.2.4 Configuring Personality
The personality reflects the protocol or protocols of the adapter. This option specifies a list of available protocols that
can be configured on an adapter. Depending on the personalities for which the adapter is licensed, one or more of the
following selections appears:
 NIC – The NIC personality implies that all the enabled functions provide NIC/TOE functionality.
NOTE TOE functionality is not supported on Emulex OCe14000-series

adapters.
on the other enabled functions. Only one of each storage protocol is allowed on each port.
 NIC+RoCE – For more information on the NIC+RoCE personality, see Section 11.2.4.1, Selecting the NIC+RoCE
Personality.
NOTE The NIC+RoCE personality is available only on Emulex

OCe14000-series adapters running Windows or Linux with both UMC
and SR-IOV disabled.
 Custom (OCe14000-series adapters only)– For more information on the Custom personality, see
Section 11.2.4.2, Selecting the Custom Personality.
To view the personalities supported on the adapter:
1. Select Personality on the Emulex NIC Selection dialog (Figure 79), and then press Enter. The Personality Selection
dialog appears.
2. Select the current personality setting and press Enter. A pop up appears with a list of available personalities.
Broadcom
- 114 -
Figure 84 Personality Selection Dialog with Pop Up
To change the personality of the adapter:

1. On the Personality Selection pop up (Figure 84) select the desired personality and press Enter.
NOTE Additional configuration changes can be made after changing the

Personality setting; however, a reboot is required before the new
Personality setting will take effect.
11.2.4.1 Selecting the NIC+RoCE Personality
NOTE The NIC+RoCE personality is available only on Emulex

OCe14000-series adapters running Windows or Linux with both UMC
and SR-IOV disabled.
The NIC+RoCE personality implies that all the enabled functions provide RoCE functionality.
If NIC+RoCE is enabled, you must select a NIC+RoCE profile. The NIC+RoCE profile settings allows you to select the
appropriate configuration for your particular system setup. The RDMA application profile choices include:
 RoCE-2 – The RoCE-2 profile supports Windows SMB Direct, Linux iSER, NFS-RDMA, and VM Migration.
To select the NIC+RoCE personality:
1. From the Personality Selection dialog (Figure 84), select NIC+RoCE and press Enter. A pop up appears.
Broadcom
- 115 -
Figure 85 NIC+RoCE Profile Dialog with Pop Up
2. Select the desired NIC+RoCE profile and press Enter.


11.2.4.2 Selecting the Custom Personality

The Custom personality allows you to select the protocol type for each function. The iSCSI and FCoE personalities can
be enabled on only one function per adapter port.
single port.
1. From the Personality Selection dialog (Figure 84), select Custom and press Enter. The Custom Personality
Selection dialog appears.
Broadcom
- 116 -
Figure 86 Custom Personality Selection Dialog
2. Select the desired personality for the appropriate function from the pop up and press Enter.

11.2.5 Link Reconfiguration
NOTE This option is available only if the adapter supports link

reconfiguration.
NOTE This feature is not supported on all Emulex OCe14000-series adapters.

The Link Reconfiguration option allows you to modify the physical link configuration for the adapter from a list of
supported configurations.
To reconfigure the physical link for an adapter:
1. On the Emulex NIC Selection dialog (Figure 79), select Link Reconfiguration and press Enter.
The Link Reconfiguration dialog appears.
2. Select the Link Reconfiguration setting and press Enter. A pop up appears with a list of available configurations.
Broadcom
- 117 -
Figure 87 Link Reconfiguration Dialog with Pop Up
3. Select the desired configuration and press Enter.

4. Select Save Configuration and press Enter.
Changing the link configuration restores the adapter to default configuration. The adapter cannot be configured
further until a reboot.
11.2.6 Configuring Virtual LAN Settings
NOTE This feature is available only when Multichannel mode is disabled.
NOTE VLAN configuration is available only if the server's system BIOS does
not provide the option to configure VLAN.
To view the VLAN settings for the adapter:
1. Verify that Multichannel mode is set to Disabled on the Emulex NIC Selection dialog (Figure 79).
2. Select NIC Configuration on the Emulex NIC Selection dialog (Figure 79), and then press Enter. The NIC
Broadcom
- 118 -
Figure 88 NIC Configuration Dialog
The NIC Configuration dialog enables you to perform the following tasks:
 Enable or disable VLAN mode
 Configure the VLAN ID
 Configure the VLAN priority
NOTE For FTS adapters, an additional menu option is available called PXE
Boot. See Section 11.2.6.4, Enabling or Disabling PXE Boot, for more
information.
For HP adapters in HP systems, additional menu options are available.
These options include Legacy PXE Boot and HP Shared Memory
Feature. For more information, see and Section 11.2.6.6, Configuring
the HP Shared Memory Feature.
11.2.6.1 Enabling or Disabling VLAN Mode

To configure the VLAN mode:
1. On the NIC Configuration dialog (Figure 88), highlight the current Virtual LAN Mode setting.
2. Enable or disable the Virtual LAN Mode setting.
11.2.6.2 Configuring the VLAN ID
NOTE Virtual LAN mode must be enabled to configure this feature.

To configure a VLAN ID:
1. On the NIC Configuration dialog (Figure 88), highlight the current Virtual LAN ID setting.
2. Select a number from 1 to 4094.
Broadcom
- 119 -
11.2.6.3 Configuring the VLAN Priority
NOTE Virtual LAN mode must be enabled to configure this feature.

To set the VLAN priority level:
1. On the NIC Configuration dialog (Figure 88), highlight the current Virtual LAN Priority setting.
2. Select a number from 0 to 7.
0 to 7, with 0 being the highest priority level.
11.2.6.4 Enabling or Disabling PXE Boot
NOTE This feature is available for FTS adapters only.

1. On the NIC Configuration dialog (Figure 88), highlight the current PXE Boot setting.
2. Enable or disable the PXE Boot setting.
11.2.6.5 Configuring Legacy PXE Boot
NOTE This feature is available for HP adapters in HP systems only.

To configure legacy PXE boot support:
1. On the following NIC Configuration dialog, highlight the current Legacy PXE Boot setting.
Figure 89 NIC Configuration Dialog (HP Adapters Only)
2. Enable or disable the Legacy PXE Boot setting.

3. Press the F10 key to save the changes.
Broadcom
- 120 -
NOTE If Legacy PXE Boot is enabled, during system startup PXE contacts the
DHCP server for an IP address to boot from the network.
11.2.6.6 Configuring the HP Shared Memory Feature
NOTE This feature is available for HP adapters in HP systems only.

When this setting is enabled, the system no longer uses reserved memory regions so devices can be directly assigned
to guest virtual machines.
To set the HP Shared Memory Feature:
1. On the NIC Configuration dialog (Figure 89), highlight the current HP Shared Memory Feature setting.
2. Enable or disable the HP Shared Memory Feature.
3. Press the F10 key to save the changes.
11.2.7 Configuring the Adapter If UMC Is Disabled or Not Supported
NOTE If UMC is enabled on Emulex or HP adapters, see Section 11.2.8,

Configuring Universal Multichannel. If you are using a Lenovo System
x adapter, see Section 11.2.9, Configuring Multichannel for Lenovo
System x Adapters.
The Global SRIOV setting enables and disables SR-IOV on an adapter. When SR-IOV is enabled at the adapter level, it
can be turned off individually for each function if required. Disabling SR-IOV on all functions disables Global SRIOV.
The value of this setting is determined by the collective SR-IOV states of all functions on the adapter. If SR-IOV is
enabled on at least one function, then Global SRIOV will be set to enabled.
Figure 90 Global SRIOV Dialog
Broadcom
- 121 -
- If UMC is disabled or is not supported, and Global SRIOV is enabled, the following Controller Configuration menu
(Figure 91) appears when you select Controller Configuration on the Emulex NIC Selection dialog (Figure 79).
Figure 91 Controller Configuration Menu (UMC Disabled)
The Controller Configuration menu enables you to perform the following tasks:
 View the current configuration
 Configure SR-IOV
 Configure NIC mode
NOTE This setting is available only if SR-IOV is enabled, the Personality

Selection is set to NIC, and a two-port Emulex OCe14000-series
adapter is in use.
 Save the current configuration
11.2.7.1 Viewing the Configuration

To view the current configuration:
1. On the Controller Configuration menu (Figure 91), select View Configuration and press Enter. The View
Configuration information appears.
Broadcom
- 122 -
Figure 92 View Configuration
From the View Configuration screen, you can view information for that specific function, including the permanent
and current MAC addresses, the logical link status, and the SR-IOV status for NIC functions.
2. When you are finished viewing the configurations, press Esc to return to the Controller Configuration menu.

If the system BIOS supports SR-IOV, you can enable it. SR-IOV support can only be enabled if UMC is disabled or it is
not supported.
NOTE SR-IOV is not supported with the NIC+RoCE personality.

SR-IOV is only available for NIC functions and not for storage (iSCSI or
FCoE) functions.
1. On the NIC Configuration dialog (Figure 88), set the Global SRIOV parameter to Enabled.
2. On the Controller Configuration menu (Figure 91), select Configure SRIOV and press Enter. The Configure SRIOV
dialog appears.
Broadcom
- 123 -
Figure 93 Configure SRIOV Dialog
3. Select the current setting for a particular NIC function and a pop up appears.
5. When you are finished, press Esc to return to the Controller Configuration menu.
For more information on SR-IOV configuration, see the appropriate Emulex driver’s user guide.
11.2.7.3 Configuring NIC Mode
NOTE This setting is available only if SR-IOV is enabled, the Personality

Selection is set to NIC, and a two-port Emulex OCe14000-series
adapter is in use.
This setting allows you to control the VF count on a two-port Emulex OCe14000-series adapter. The choices include:
 NIC Only Profile – The VF count is restricted to 31 VFs per port and QoS is supported for those VFs.
NOTE For two-port Emulex OCe14000B-series adapters only, this setting

supports up to 63 VFs per port.
 NIC-ETS Disabled – The VF count is set to 63 VFs per port but QoS is not supported for those VFs.
NOTE This setting is not supported on Emulex OCe14000B-series adapters.

To select the NIC mode:
1. From the Configure SRIOV dialog (Figure 93), select the NIC Mode setting for a particular NIC function and a pop
up appears (Figure 94).
Broadcom
- 124 -
Figure 94 Configure NIC Mode Pop Up
2. Select NIC Only Profile or NIC-ETS Disabled and press Enter.
NOTE For two-port Emulex OCe14000B-series adapters only, the NIC Only
Profile setting supports up to 63 VFs per port.
The NIC-ETS Disabled setting is not supported on Emulex
OCe14000B-series adapters.
3. When you are finished, press Esc to return to the Controller Configuration menu.
11.2.7.4 Saving the Current Configuration

To save the configuration changes, on the Controller Configuration menu (Figure 91), select Save Current
Configurations and press Enter.
UMC provides the ability to configure multiple PCI functions or I/O channels for each adapter port. For more
information on UMC support, refer to the Emulex Universal Multichannel Reference Manual.
NOTE HP adapters support UMC, FLEX-10, and FLEX-QBG mode.

If UMC is enabled and the adapter also supports Virtual Fabric mode
or Unified Fabric Protocol mode, see Section 11.2.9, Configuring
Multichannel for Lenovo System x Adapters, for more information. If
UMC is disabled or not supported on the adapter, see Section 11.2.7,
Configuring the Adapter If UMC Is Disabled or Not Supported.
If UMC is enabled, you must configure the minimum and maximum
bandwidths settings for the iSCSI and FCoE storage functions in the
NIC BIOS before they can be configured through their respective
function will still show as down, and you will be unable to log in to
Broadcom
- 125 -

running in 10GbE mode only. UMC is not supported in 1GbE mode.
If UMC functionality is supported on the system, the Emulex UEFI NIC utility enables you to perform the following
tasks:
 Enable or disable UMC functionality (Multichannel mode)
 View the current adapter configuration
 Configure the minimum and maximum bandwidth for each channel
 Configure the LPVID for each channel
NOTE Your system may not support all UMC options.

For Emulex OCe14000-series adapters, the Emulex NIC configuration
utility displays all of the functions on a port, regardless of whether the
system supports ARI or not. For more information on ARI, see
Section 11.2.8.1, ARI Support.
To enable UMC support:
1. On the Emulex NIC Selection dialog (Figure 79), select Multichannel Mode and press Enter. A pop up appears.
2. Select Enable to activate UMC support and press Enter.
NOTE HP FLEX mode cannot be enabled in this menu. If an adapter is in FLEX

mode, the Multichannel mode is displayed as either FLEX-10 or
FLEX-QBG, as appropriate. Some settings, such as Multichannel and
Personality, and the Multichannel parameters, cannot be configured
from the UEFI BIOS utility in FLEX mode.
To configure the UMC configuration:
1. On the Emulex NIC Selection dialog (Figure 79), select Controller Configuration and press Enter. The following
Controller Configuration menu appears.
Figure 95 Controller Configuration Menu (UMC Enabled)
Broadcom
- 126 -
 View the current configuration of each function.
 Configure the minimum and maximum bandwidth percentage.
 Configure the LPVID per function.
 Save the current configuration.
11.2.8.1 ARI Support

The Emulex OCe14000-series adapters support ARI, which provides the ability to configure additional PCI functions or
I/O channels for each physical adapter port if UMC is enabled.
You can configure up to 16 functions on a one-port Emulex OCe14400-series adapter, up to 8 functions per port on a
one or two-port Emulex OCe14100-series adapter, and up to 4 functions per port on a four-port Emulex
OCe14100-series adapter.
support for ARI.
 The system hardware (the motherboard and BIOS) must support ARI.
 ARI must be enabled in the system BIOS.
 The host operating system must support ARI:
 The application management tools, including the Emulex OneCommand CNA Manager application must support
ARI.
 ARI must be enabled in the firmware using the Emulex OneCommand CNA Manager application.
11.2.8.2 Configuring More than Four Functions per Port on Emulex OCe14000-Series Adapters
By default on 1-port or 2-port Emulex OCe14000-series adapters, only four functions are enabled when UMC is
enabled. To enable the other four functions, you must manually enable those functions for them to be operational.
To configure more than four functions per port on 1-port or 2-port Emulex OCe14000-series adapters, you must
perform the following steps:
1. Ensure that UMC is enabled. By default, UMC enables four functions per port. See Section 11.2.8, Configuring
Universal Multichannel, for information on configuring UMC.
2. Select the Custom mode in the Personality Selection dialog (Figure 84). This enables you to view all eight
functions per port. See Section 11.2.4.2, Selecting the Custom Personality, for information on selecting the
Custom mode.
NOTE The options to enable and configure more than four functions per
physical port are not available unless Custom mode is selected.
3. For each function to be enabled, change the function’s personality type to the desired protocol. See
Section 11.2.4.2, Selecting the Custom Personality, for information on selecting the personality.
Broadcom
- 127 -
Bandwidths, for information on configuring the bandwidth and Section 11.2.8.5, Configuring the LPVID, for
information on configuring the LPVID.
11.2.8.3 Viewing the Configuration

To view the current UMC configuration:
1. On the Controller Configuration menu (Figure 95), select View Configuration and press Enter. The View
Configuration information appears.
Figure 96 UMC Configuration for Function 0
From the View Configuration display, you can view information for that specific function, including the
permanent and current MAC addresses, the logical link status, the minimum and maximum bandwidth settings,
and LPVID of all of the NIC functions.
NOTE Logical Link Status and LPVID for storage functions (iSCSI and FCoE)
appears as N/A.
2. When you are finished viewing the configurations, press Esc to return to the Controller Configuration menu.
11.2.8.4 Configuring Minimum and Maximum Bandwidths

1. On the Controller Configuration menu (Figure 95), select Configure Bandwidth and press Enter. The Configure
Bandwidth dialog (Figure 97) appears.
Broadcom
- 128 -
Figure 97 Configure Bandwidth Dialog
2. Select a specific function under Configure Minimum Bandwidth or Configure Maximum Bandwidth and press
Enter.
100.

— The Maximum Bandwidth value is the greatest amount of bandwidth the function can provide. It is
3. Enter the value for the specified function and press Enter.
NOTE To disable a function, set the Minimum Bandwidth and Maximum

Bandwidth values to 0.
4. When you are finished configuring bandwidths, press Esc to return to the Controller Configuration menu.
11.2.8.5 Configuring the LPVID

operating system for that PCI function has set up a VLAN ID, the operating system-configured VLAN ID takes
precedence over the LPVID for transmit packets while the operating system-configured VLAN ID and LPVID-tagged
packets will both be received. If the operating system has not set up any VLAN IDs, then the LPVID is used for tagging.
be different.
LPVIDs also need to be configured on the switch port.
Broadcom
- 129 -
To configure an LPVID:
1. On the Controller Configuration menu (Figure 95), select Configure LPVID and press Enter. The Configure LPVID
dialog appears.
Figure 98 Configure LPVID Dialog
2. Select the LPVID value for a specific function and press Enter.
3. Enter a value and press Enter. The LPVID range is 2 to 4094. A value of 0 disables the LPVID.
NOTE LPVID values 1 and 4095 are currently reserved and cannot be used or
configured.
4. When you are finished configuring LPVIDs, press Esc to return to the Controller Configuration menu.
11.2.8.6 Saving the Configuration

To save the configuration changes, on the Controller Configuration menu (Figure 95), select Save Configuration and
press Enter.
NOTE This section only pertains to certain Emulex OneConnect adapters that
support Multichannel for Lenovo System x Virtual Fabric or UFP.
adapter port.
NOTE Setting up Multichannel for Lenovo System x Virtual Fabric or UFP

depends on cooperation with adjacent switches.
Broadcom
- 130 -
To enable Multichannel for Lenovo System x support:

1. On the Emulex NIC Selection dialog (Figure 99), select Multichannel Mode and press Enter. A pop up appears.
Figure 99 Lenovo System x Multichannel Mode Selection Pop Up
2. Select one of the following settings and press Enter:

— Virtual Fabric Mode (referred to as IBM Virtual Fabric Mode on some Emulex OCe14000-series adapters and all
Emulex OCe11100-series adapters)
— Unified Fabric Protocol Mode (referred to as IBM Unified Fabric Protocol Mode on some Emulex
OCe14000-series adapters and all Emulex OCe11100-series adapters)
— Disabled
NOTE For more information on the available Multichannel modes, see

With the Multichannel mode selected, you can now configure Multichannel for Lenovo System x support. See
Section 11.2.9.3, Multichannel for Lenovo System x Configuration, for more information.
11.2.9.1 Configuring More than Four vNICs per Port on Emulex OCe14000-Series Adapters
By default on 1-port or 2-port Emulex OCe14000-series adapters, only four vNICs are enabled when Multichannel is
enabled. To enable the other four vNICs, you must manually enable those vNICs for them to be functional.
To configure more than four vNICs per port, you must perform the following steps:
1. Verify that Multichannel is enabled. By default, Multichannel enables four vNICs per port. See Section 11.2.9,
Configuring Multichannel for Lenovo System x Adapters, for information on configuring Multichannel.
2. Select the Custom mode in the Personality Selection dialog (Figure 84). This enables you to view all eight vNICs
per port. See Section 11.2.4.2, Selecting the Custom Personality, for information on selecting the Custom mode.
3. For each vNIC to be enabled, change the personality type to the desired protocol. See Section 11.2.4.2, Selecting
the Custom Personality, for information on selecting the personality.
Broadcom
- 131 -
Bandwidths, for information on configuring the bandwidth and Section 11.2.8.5, Configuring the LPVID, for
information on configuring the LPVID.
NOTE The following modes are available only on certain adapters and
systems that support Virtual Fabric mode and Unified Fabric Protocol
mode.
Additional PFs are supported when ARI is enabled on the system. For
more information on ARI, see Section 11.2.8.1, ARI Support.
A Lenovo System x Virtual Fabric-enabled switch provides the ability to configure an LPVID for a virtual channel or I/O
channel on an adapter port. If Multichannel for Lenovo System x is supported on the system, you can select one of the
following modes:
 Virtual Fabric Mode – Select this mode if an Emulex OneConnect adapter is attached to a Lenovo System x
Virtual Fabric-enabled switch. This mode supports up to four PFs per port.
NOTE This mode is referred to as IBM Virtual Fabric mode on some Emulex
OCe14000-series adapters and all Emulex OCe11100-series adapters.
Virtual Fabric mode is not supported on 40GbE switches.
 Unified Fabric Protocol Mode – Select this mode if an Emulex OneConnect adapter is attached to a Lenovo
System x UFP-enabled switch. In this mode, the maximum PFs per port for each adapter configuration is listed
below:
NOTE This mode is referred to as IBM Unified Fabric Protocol mode on some
Emulex OCe14000-series adapters and all Emulex OCe11100-series
adapters.
Some Lenovo System x switches support both Unified Fabric Protocol
mode and Virtual Fabric mode.
Fabric or UFP-enabled switch. In this mode, the maximum PFs per port for each adapter configuration is listed
below:
NOTE Multichannel for Lenovo System x functionality is supported on

Emulex OneConnect adapters running in 10GbE mode only.
Multichannel for Lenovo System x is not supported in 1GbE mode.
An LPVID is optional for Virtual Fabric mode, but it is required for
every function if using Switch Independent mode.
11.2.9.3 Multichannel for Lenovo System x Configuration

See the appropriate section below based on the mode you have selected.
Broadcom
- 132 -
11.2.9.3.1 Virtual Fabric Mode Configuration

To configure Multichannel for Lenovo System x if the Multichannel mode is set to Virtual Fabric mode:
Controller Configuration menu appears.
Figure 100 Virtual Fabric Mode Controller Configuration Menu
 View the current configuration of each function – See Section 11.2.8.3, Viewing the Configuration.
 Configure the LPVID per function – See Section 11.2.8.5, Configuring the LPVID.
 Save the current configuration – See Section 11.2.8.6, Saving the Configuration.
11.2.9.3.2 Unified Fabric Protocol Mode Configuration
NOTE By default on 1-port or 2-port Emulex OCe14000-series adapters, only

four vNICs are enabled when Multichannel is enabled. To enable the
other four vNICs, you must manually enable those vNICs using the
steps provided in Section 11.2.9.1, Configuring More than Four vNICs
per Port on Emulex OCe14000-Series Adapters.
To configure Multichannel for Lenovo System x if the Multichannel mode is set to Unified Fabric Protocol mode:
1. On the Emulex NIC Selection dialog (Figure 99), select Controller Configuration and press Enter. The Controller
Configuration menu (Figure 101) appears.
Broadcom
- 133 -
Figure 101 UFP Controller Configuration Menu
From the Controller Configuration menu, you can view the current configuration of each function. See
Section 11.2.8.3, Viewing the Configuration, for more information.
11.2.9.3.3 Switch Independent Mode Configuration
NOTE By default on 1-port or 2-port Emulex OCe14000-series adapters, only

four vNICs are enabled when Multichannel is enabled. To enable the
other four vNICs, you must manually enable those vNICs using the
steps provided in Section 11.2.9.1, Configuring More than Four vNICs
per Port on Emulex OCe14000-Series Adapters.
To configure Multichannel for Lenovo System x if the Multichannel mode is set to Switch Independent mode:
Controller Configuration menu (Figure 102) appears.
Broadcom
- 134 -
Figure 102 Switch Independent Mode Controller Configuration Menu
From the Controller Configuration menu, you can perform the following tasks:
 View the current configuration of each function – See Section 11.2.8.3, Viewing the Configuration.
 Configure the minimum and maximum bandwidth percentage – See Section 11.2.8.4, Configuring Minimum and
Maximum Bandwidths.
 Configure the LPVID per function – See Section 11.2.8.5, Configuring the LPVID.
NOTE An LPVID is required for every function if using Switch Independent

mode, but it is optional for Virtual Fabric mode and Unified Fabric
Protocol mode.
 Save the current configuration – See Section 11.2.8.6, Saving the Configuration.
11.2.10 Port Management
The Port Management option is used to enable or disable the physical ports.
If port 0 is disabled, it brings down the physical link for port 0 and the power consumption of the adapter is lowered;
however, the PCI functions associated with that port must remain enabled.
If any other port is disabled, all of the corresponding functions associated with that port are disabled and removed
from the PCI configuration space. Disabling these ports also lowers the power consumption of the adapter.
Enabling any of the ports restores the previously removed PCI functions and restores the power consumption to its
normal state.
NOTE Enabling and disabling ports is applicable in both Multichannel and

non-Multichannel configurations. If Multichannel mode is enabled, all
virtual functions associated with the disabled port are also disabled.
Broadcom
- 135 -
To configure port management:

1. On the Emulex NIC Selection dialog (Figure 99), select Port Management and press Enter. The following Port
Management dialog appears.
Figure 103 Port Management Dialog
2. Select the current setting for a particular port and a pop up appears.
4. When you are finished, select Save Port States to save the current settings.
5. Press Esc to return to the Controller Configuration menu.
NOTE A reboot is required for this setting to take effect.
11.2.11 Feature on Demand
NOTE The Feature on Demand function is available only on some Lenovo

System x adapters.
FoD is a Lenovo System x proprietary protocol that enables storage functions on Emulex adapters. This feature
requires a unique license key to be applied from Lenovo System x's Integrated Management Module. For more
information on obtaining a license key, contact your Lenovo System x representative.
The FoD Type and FUI fields are required by Lenovo System x to generate a unique license key for the specific adapter
for which you have requested a license. Each adapter in the system must obtain its own license key.
To view Feature on Demand information, from the Emulex NIC Selection dialog (Figure 99), select Feature On Demand
and press Enter. The Feature On Demand information appears.
Broadcom
- 136 -
December 30, 2016 Downloading Firmware and Boot Code
Figure 104 Feature On Demand
From the Feature On Demand screen, you can view information on the feature type, the FoD Unique Identifier, and its
current status.
 FoD Type – The FoD Type field is unique for each platform. Different products have different FoD types. For
example, LOM products have a different FoD type than mezzanine cards.
 FUI – The FUI field is internally generated by the Emulex firmware using the FoD type and the adapter’s serial
number. The FUI is unique to each adapter because each card has its own unique serial number.
 FoD Status – The FoD Status field indicates whether a license key has been applied properly or not.
— If the FoD status field is set to Enabled, it indicates that the FoD license key has been successfully applied and
FoD is enabled. If FoD is enabled, you will see all of the storage personalities under the Personality menu
option, including NIC, iSCSI, and FCoE.
— In all other cases, the FoD Status field indicates that a failure has occurred or that an FoD license has not been
applied.
11.3 Downloading Firmware and Boot Code
A single firmware image contains the latest version of the firmware and boot code.
The firmware and UEFI NIC, iSCSI, and FCoE drivers are contained in one image file with the .UFI extension. This file
must be flashed through the NIC interface exposed by HII.
To view the adapter’s current firmware and boot code version, follow the steps in Section 11.2, Starting the Emulex
NIC Configuration Utility.
The Emulex NIC Selection dialog displays the current firmware version for the selected adapter and a link to the
Emulex Flash Update Utility, which you can use to download firmware and boot code.
To download firmware and boot code:
1. In an open UEFI shell, copy the firmware and boot code file into a directory on the UEFI partition media.
Broadcom
- 137 -
Figure 105 UEFI Shell with Firmware and Boot Code File
2. Exit the UEFI shell and launch the Emulex NIC configuration utility.
3. From the Network device list, select the NIC adapter you want to modify and press Enter.
4. The Emulex NIC Selection dialog (Figure 79) shows information for the selected adapter. Select Emulex Flash
Update Utility and press Enter. The Emulex Flash Update Utility dialog (Figure 99) appears. This utility displays all
available media and installs the flash file on the adapter.
Figure 106 Emulex Flash Update Utility Dialog
5. Press Enter to select the media containing the flash file.

6. Navigate to the directory containing the flash file and press Enter (Figure 107).
Broadcom
- 138 -
Figure 107 Emulex Flash Update Utility with Directory Name
7. Use the arrow keys to select the flash file and press Enter.
8. Use the arrow keys to select Start Flash Update, and press Enter to begin the update process.
Figure 108 Emulex Flash Update Utility, Start Flash Update
Broadcom
- 139 -
NOTE This firmware flash procedure only flashes the physical interface that
was selected in the HII menu. All Emulex adapters must contain the
same firmware version to function properly. The above procedure
must be repeated for each physical interface installed in the system
before proceeding to the next step.
NOTE If a jumper is plugged into the ASIC GPIO pin on the adapter, it
indicates that only secure firmware versions are allowed to be flashed
on the adapter. Upgrade from earlier unsecure firmware versions does
not involve a digital signature check since the earlier code does not
support this feature. Therefore, upgrade to secure firmware versions
will be successful. If a secure version of the firmware (version 11.0 or
later) is installed on an Emulex OCe14000B-series adapter and you
want to update to an earlier unsecure version of firmware, you must
remove the secure firmware jumper block before performing the
update. See the adapter installation guide for more information.
Firmware upgrade from a secure firmware version to an unsecure
firmware version results in an error when the jumper is in place. If this
happens, an error message indicating digital signature failure appears.
9. The flash update begins. It takes about two minutes to complete.
Figure 109 Emulex Flash Update Utility, Completed
10. Reset the system. The latest version information for the adapter appears in the Emulex NIC Selection dialog
(Figure 79).
Broadcom
- 140 -
December 30, 2016 Identifying a Port
11.4 Identifying a Port
To physically identify a port on the Emulex NIC Selection dialog (Figure 79), select Port Identification and press Enter.
The LEDs on the adapter start blinking indicating the selected port.
supported.
If port identification is not supported on the system, you will receive a
message stating that it is not supported.
11.5 Erasing Ports and Adapter Configurations
NOTE On OCe11100-series adapters, if you select the Erasing Ports and

returned to their factory default settings except for the current
personality selection. You must perform this action to provide a clean
On OCe14000 series adapter, if you select the Erasing Ports and

returned to their factory default settings including the current
personality selection. Performing this action ensures a clean

their factory default settings.
To erase ports and the adapter configuration:
1. On the Emulex NIC Selection dialog (Figure 79), select Erase Configuration and press Enter (Figure 110) .
Broadcom
- 141 -
December 30, 2016 UEFI NIC Diagnostics
Figure 110 Erase Configuration
2. Press Enter to delete the adapter configuration, or press Esc to stop the operation.
11.6 UEFI NIC Diagnostics
The UEFI NIC driver diagnostics protocol can be used to run diagnostic tests on each NIC function of the card. This
protocol is used by a platform management utility to let you run driver specific diagnostics on an adapter.
11.6.1 EFI_DRIVER_DIAGNOSTICS_PROTOCOL
Syntax:
drvdiag [-c] [-l XXX] [-s] [-e] [-m] [driverhandle [devicehandle [childhandle]]]
Description:
The UEFI NIC driver diagnostics protocol can be used to run diagnostic tests on each NIC function of the card.
Diagnostics can be run in standard mode, extended mode, and manufacturing mode.
Parameters:
-c Diagnose all child devices.

-1 XXX Diagnose using the ISO 639-2 language specified by XXX.
-s Run diagnostics in standard mode.
Diagnostics in standard mode runs the LED test, Link test, Get MAC test, and the DMA
test (Read, Write, and Read and Write)
-e Run diagnostics in extended mode.
Diagnostics in extended mode runs the ARM Timer test, the MAC Loopback test, and
the Physical Loopback test.
Broadcom
- 142 -
December 30, 2016 UEFI NIC Diagnostics
-m Run diagnostics in manufacturing mode.

Diagnostics in manufacturing mode run the Low-level Subsystem Network Loopback
test.
driverhandle Handle of the driver being configured.
devicehandle Handle of a device the driverhandle is managing.
childhandle Handle of a device that is a child of the devicehandle.
Examples:
The following examples show you a way of using the EFI_DRIVER_DIAGNOSTICS_PROTOCOL.
The driver command identifies the handle of the driver:
Shell> drivers
122 Emulex 10G NIC

The drvdiag command lists all the devices available for diagnostics. Each Ctrl [XXX] corresponds to a NIC function,
which can be physical or virtual. The command returns handles for NIC functions on both ports.
Shell> driverdiag
Drv[122] Ctrl[121]
Drv[122] Ctrl[123]
To run the standard diagnostic tests on function 0:
Shell> drvdiag -s 122 121
To run the standard diagnostic tests on all NIC functions:
Shell> drvdiag -s 122
Broadcom
- 143 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 12: Configuring UEFI for iSCSI
December 30, 2016 Navigating the Emulex iSCSI Configuration Utility
Chapter 12: Configuring UEFI for iSCSI

NOTE For systems with multiple adapters, the UEFI system firmware or boot
code uses the highest version driver installed on any of the adapters.
Adapters with older versions of EFIBoot are managed by the more
recent version, but only as long as the adapter with the most recent
version is in the system. The latest firmware and boot code must be
installed on each adapter in the system to ensure that each adapter
runs the latest firmware and boot code.
UEFIBoot supports:
 Configuration Access and Component Name2 UEFI protocols.
 Selectable SCSI device path through the driver configuration protocol
 Up to 96 adapters in a system
 Up to 256 targets (selectable through the driver configuration protocol)
 Up to 256 LUNs
 Multiutility setup
This version of UEFIBoot is loaded from flash into system memory.
If UEFIBoot is loaded in a UEFI Shell, type drivers and press Enter to see if the driver is loaded.
12.1 Navigating the Emulex iSCSI Configuration Utility
The Emulex iSCSI configuration utility has menus and configuration dialogs. Use the following methods to navigate
them:
 Press the up and down arrows on the keyboard to navigate menu options or configuration fields. If multiple
adapters are listed, use the up and down arrows to scroll to the additional adapters.
 Press Enter to select an option.
12.2 Starting the Emulex iSCSI Configuration Utility
Depending on the vendor UEFI configuration, the Emulex iSCSI configuration utility may appear under different setup
menus in the vendor system firmware or BIOS (such as Storage).
To start the Emulex iSCSI configuration utility:
1. Select the Emulex iSCSI Utility for a particular function in the Storage dialog and press Enter.
Broadcom
- 144 -
December 30, 2016 Starting the Emulex iSCSI Configuration Utility
Figure 111 Storage Dialog
2. The Controller Configuration Menu appears.
3. Highlight iSCSI Initiator Name and press Enter to edit the initiator name.
This is a global setting. The initiator name configured on one adapter is reflected on all adapters in the system.
Broadcom
- 145 -
December 30, 2016 Configuring MPIO
NOTE HP systems are an exception. Each port on an HP system can be

configured with a unique initiator name.
4. To save changes, select Save Changes and press Enter.
12.3 Configuring MPIO
TCP/IP connection to the target. If one session fails another session can continue processing I/O without interruption
to the application. In iSCSI target configuration, you have the option of setting dual network paths to a single boot
LUN.
You must follow these steps to configure MPIO boot support for each operating system.
To configure MPIO:
1. From the Controller Configuration Menu (Figure 112), select MPIO Configuration and press Enter. The MPIO
Configuration pop up appears.
3. To save your changes, select Save Changes and press Enter.
12.4 Configuring Boot Support
Boot support is provided for each port or function. If boot support is enabled, you can boot from the specified
function. If boot support is disabled, you will not be able to boot from the function.
To configure boot support:
1. From the Controller Configuration Menu (Figure 112), select Boot Support and press Enter. The Boot Support pop
up appears.
3. To save your changes, select Save Changes and press Enter.
12.5 Configuring TCP ACK Delay
NOTE This functionality is available only on HP adapters that support UEFI.

TCP ACK delay is provided for each port or function. If TCP ACK delay is enabled, several ACK responses may be
combined into a single response. If TCP ACK delay is disabled, an ACK is sent for each TCP packet received.
Broadcom
- 146 -
To configure TCP ACK delay:

1. From the HP Controller Configuration Menu (Figure 113), select TCP Ack Delay and press Enter.
Figure 113 Configuring TCP ACK Delay

3. To save your changes, select Save.
12.6 Viewing the Controller Properties
To view the adapter properties:

1. From the Controller Configuration Menu (Figure 112), select Controller Properties and press Enter. The Controller
Properties menu (Figure 114) appears.
Broadcom
- 147 -
December 30, 2016 Configuring the Network
Figure 114 Controller Properties Menu
The Controller Properties menu displays the model number, description, BIOS version, and firmware version for the
adapter. From the Controller Properties menu, you can configure the discovery of the boot target using DHCP. See
Section 12.9.1, Discovering and Adding Boot Targets through DHCP, for more information.
12.7 Configuring the Network
To configure the network:

1. From the Controller Configuration menu (Figure 112), select Network Configuration and press Enter. The Network
Broadcom
- 148 -
The Network Configuration dialog displays the MAC address, port speed, and link status for the adapter. From the
Network Configuration dialog, you can configure the following items:
 IP version
 IPv4 address
 IPv6 address
 VLAN ID and priority
12.7.1 Configuring the IP Version
To configure the IP version:

1. On the Network Configuration dialog (Figure 115), select IP version and press Enter. The IP Version pop up
appears.
2. Select IPV4, IPV6, or DUAL MODE and press Enter.
12.7.2 Configuring an IPv4 Address

1. On the Network Configuration dialog (Figure 115), verify that the IP version is set to IPV4 or DUAL MODE.
2. Select Configure IPV4 Address and press Enter. The Configure IPV4 Address dialog (Figure 116) appears.
Broadcom
- 149 -
Figure 116 Configure IPV4 Address Dialog
From the Configure IPV4 Address dialog, you can do the following:
 Enable DHCP for automatic assignment of the IP address through a DHCP server. See Section 12.7.2.1,
Automatically Assigning an IP Address through a DHCP Server, for more information.
 Configure a static IP address (if Initiator IP via DHCP is disabled). See Section 12.7.2.2, Manually Assigning an IP
Address, for more information.
 Ping the iSCSI initiator. See Section 12.7.2.3, Pinging the iSCSI Initiator, for more information.
12.7.2.1 Automatically Assigning an IP Address through a DHCP Server

To enable DHCP for automatic assignment of the IP address through a DHCP server:
1. On the Configure IPV4 Address dialog (Figure 116), select Initiator IP via DHCP and press Enter. The Initiator IP via
DHCP pop up appears.
2. Select Enable and press Enter.
3. Select Save DHCP Settings and press Enter.
12.7.2.2 Manually Assigning an IP Address

To manually assign an IP address:
1. On the Configure IPV4 Address dialog (Figure 116), verify that the Initiator IP via DHCP is set to Disable. If you
change this setting from Enable to Disable, select Save DHCP Settings and press Enter.
2. Select Configure Static IP Address and press Enter. The Configure Static IP Address dialog (Figure 117) appears.
Broadcom
- 150 -
Figure 117 Configure Static IP Address Dialog
3. Enter the IP address, subnet mask, and default gateway in the corresponding fields.

To ping the iSCSI initiator:
1. On the Configure IPV4 Address dialog (Figure 116), select Ping and press Enter. A pop up text box appears.
2. Enter the IP address of the iSCSI initiator in the text box and press Enter.
— If the ping is successful, a reply message appears with the iSCSI initiator IP address.
— If the ping is unsuccessful, a failure message appears.
12.7.3 Configuring an IPv6 Address
NOTE For HP adapters in HP systems, all of the following IPv6 configuration

options are available from the Configure IPV6 Address dialog. The
instructions in the following sections still apply to HP adapters;
however, use the F10 key to save the configuration settings.
1. On the Network Configuration dialog (Figure 115), verify that the IP version is set to IPV6 or DUAL MODE.
2. Select Configure IPV6 Address and press Enter. The Configure IPV6 Address dialog (Figure 118) appears.
Broadcom
- 151 -
Figure 118 Configure IPV6 Address Dialog
From the Configure IPV6 Address menu, you can do the following:
 Enable automatic configuration of the IP address. See Section 12.7.3.1, Automatically Configure an IP Address, for
more information.
 Configure the IPv6 address. See Section 12.7.3.2, Configuring the IPv6 Address, for more information.
 Ping the iSCSI initiator. See Section 12.7.3.3, Pinging the iSCSI Initiator, for more information.
12.7.3.1 Automatically Configure an IP Address

To enable automatic IP address configuration:
1. On the Configure IPV6 Address dialog (Figure 118), select AutoConfiguration and press Enter. The
AutoConfiguration pop up appears.
2. Select Enable and press Enter.
3. Select Save AutoConfiguration and press Enter.
12.7.3.2 Configuring the IPv6 Address

To configure the IPv6 address:
1. On the Configure IPV6 Address dialog (Figure 118), select Configure IPV6 Address and press Enter. The Configure
IPV6 Address dialog (Figure 119) appears.
Broadcom
- 152 -
Figure 119 Configure IPV6 Address Settings Dialog
2. Enter the following information in the corresponding fields:

— Link Local Address – The unique address assigned to the port which is available for use inside the local
network but not outside of the local network.
— Routable Address 1 – A routable address assigned to the iSCSI port.
— Routable Address 2 – A second routable address assigned to the iSCSI port.
— Default Gateway – A gateway is a router on a computer network that serves as an access point to another
network and that an initiator uses by default.
4. Press Esc to exit the menu.

To ping the iSCSI initiator:
1. On the Configure IPV6 Address dialog (Figure 118), select Ping and press Enter. A pop up text box appears.
2. Enter the IP address of the iSCSI initiator in the text box and press Enter.
— If the ping is successful, a reply message appears with the iSCSI initiator IP address.
— If the ping is not successful, a failure message appears.
12.7.4 Configuring VLAN ID and Priority
A VLAN is a way of partitioning the network. If the LAN is made up of all devices within a broadcast domain, a VLAN is
a broadcast domain made up of switches. You first create a VLAN and then assign ports to a VLAN. All ports in a single
VLAN are in a single broadcast domain.
You do not have to configure VLANs unless the network is already using them. Some reasons why VLANs are used
include:
 A LAN increases in size with numerous devices.
Broadcom
- 153 -
 A LAN has extensive broadcast traffic on it.

 Groups of users on a LAN need more security.
A VLAN ID, like an IP address or initiator name, is assigned a value to uniquely identify it on a network. A VLAN priority
is set to determine what packet gets priority order within a VLAN.
To configure a VLAN ID and priority:
1. On the Network Configuration dialog (Figure 115), select Configure VLAN ID/Priority and press Enter. The
Configure VLAN ID/Priority dialog appears.
Figure 120 Configure VLAN/ID Priority Dialog
2. To enable VLAN support:

a. Select VLAN Support and press Enter. The VLAN Support pop up appears.
b. Select Enable and press Enter.
3. To assign a VLAN ID number:
a. Select VLAN ID and press Enter. This is a unique value you assign to each VLAN on a single device. Valid values
range from 2 to 4094.
b. Enter a VLAN ID value and press Enter.
4. To set a VLAN priority, if necessary:
a. Select VLAN PRIORITY and press Enter. This unique value assigns a priority to outbound packets containing a
specified VLAN ID. Valid values range from 0 to 7, with 0 being the highest priority level.
b. Enter a VLAN priority value and press Enter.
6. Press Esc to return to the Network Configuration dialog.
Broadcom
- 154 -
December 30, 2016 Updating Firmware
12.8 Updating Firmware
To update firmware, you must use the NIC firmware update utility, which revises the iSCSI function with a single
firmware download image. For more information on downloading firmware, see Section 11.3, Downloading Firmware
and Boot Code.
12.9 Adding and Configuring Targets
After the initiator has been configured, you must make an iSCSI target available to the initiator host. Targets can be
discovered automatically using the DHCP discover mechanism, the SendTargets discovery mechanism, or you can
manually configure targets.
Before you begin the login session, gather the following information:
 iSCSI target name (manual configuration only) – The target name you are adding. The iSCSI target name is not
required if you are using DHCP or SendTargets discovery. It is required for manually configured targets only. This
name should be known to you based on how you configured the iSCSI target.
 iSCSI target IP address – The IP address of the target into which you are logging.
 TCP port number – The TCP port number of the target portal. Typically this is 3260, which is the well-known port
number defined for use by iSCSI.
12.9.1 Discovering and Adding Boot Targets through DHCP
To automatically discover and add boot targets through DHCP:

1. On the Controller Properties dialog (Figure 114), set Discover Boot Target via DHCP to Enable and press Enter.
4. On the Controller Configuration Menu (Figure 112), select iSCSI Target Configuration and press Enter. The iSCSI
Target Configuration dialog (Figure 121) shows the discovered targets.
For more information on configuring a DHCP boot target, see Section 10.3, Discovering Targets through DHCP for
iSCSI.
Broadcom
- 155 -
December 30, 2016 Adding and Configuring Targets
12.9.2 Using the SendTargets Discovery to Add an iSCSI Target
The iSCSI initiator uses the SendTargets discovery mechanism to locate names of available targets. Use this method if
an iSCSI node has a large number of targets.
To configure an iSCSI target using the SendTargets discovery:
1. On the Controller Properties dialog (Figure 114), set Discover Boot Target via DHCP to Disable and press Enter.
4. From the Controller Configuration Menu (Figure 112), select iSCSI Target Configuration and press Enter. The iSCSI
Target Configuration dialog (Figure 121) appears.
5. Select Add Target and press Enter. The Add/Ping iSCSI Target dialog (Figure 123) appears.
6. Leave the iSCSI Target Name blank.
7. Enter the iSCSI target IP address.
8. Change the TCP port number value, if necessary. The default number is 3260.
Broadcom
- 156 -
enter CHAP configuration.
14. Select Save/Login. A message reminds you that you have left the iSCSI Target name blank and that the
SendTargets mechanism will be used. If you want to continue, press Y.
15. After you send the SendTargets request, the firmware attempts to log in to the target. If it is successful, the Targets
Discovered Via SendTargets dialog displays a list of targets.
Figure 122 Discovered Targets Dialog
16. Select the targets you want to add from the list and press the space bar.
17. Add these targets to the list of iSCSI targets available for the initiator to log in to by selecting Save Target and
press Enter. If you enabled CHAP Authentication, you are prompted to enter CHAP configuration for each target,
one at a time.
18. From the Controller Configuration Menu (Figure 112), select iSCSI Target Configuration and press Enter to view
the added target information.
NOTE If you set the Boot Target option in step 5 before adding the target, the
Boot Target appears as No. To enable Boot Target, continue with step
19. Otherwise, you have completed the procedure.
19. To enable Boot Target or make any other changes to the targets, select the target and press Enter. The Edit/Ping
iSCSI Target dialog (Figure 124) appears. From this dialog, you can edit the target.
12.9.3 Manually Adding, Discovering, and Managing Boot Targets
To manually add and discover boot targets:

1. On the Controller Properties dialog (Figure 114), set Discover Boot Target via DHCP to Disable and press Enter.
Broadcom
- 157 -
4. On the iSCSI Target Configuration dialog (Figure 121), select Add Targets and press Enter. The Add/Ping iSCSI
Target dialog appears.
Figure 123 Add/Ping iSCSI Target Dialog
5. Enter the target IP address and TCP port number (the default target port number is 3260).
enter CHAP configuration. For more information about authentication methods, see Section 12.9.5, Selecting an
Authentication Method.
11. Select Save/Login and press Enter to discover targets.
12.9.4 Setting a Boot Target
The discovered target must be set as a boot target to enable iSCSI boot.
To set a boot target:
1. On the iSCSI Target Configuration dialog (Figure 121), select the target name and press Enter. The Edit/Ping Target
dialog (Figure 124) appears.
Broadcom
- 158 -
Figure 124 Edit/Ping Target Dialog
2. Select the Boot Target option and press Enter. The Boot Target pop up appears.
3. Select Primary or Secondary and press Enter.
4. Select Save/Login and press Enter.
12.9.5 Selecting an Authentication Method
The Emulex iSCSI configuration utility uses CHAP to authenticate initiators and targets for added network security. By
using a challenge and response security mechanism, CHAP periodically verifies the initiator's identity. This
authentication method depends on a secret key known to the initiator and the target only. Although the
authentication can be one-way, you can negotiate CHAP in both directions with the help of the same secret set for
mutual authentication. You must make sure however, that what you configure on the target side matches the initiator
side. The Emulex iSCSI configuration utility supports both one-way and mutual authentication.
To configure the CHAP authentication method:
2. Select the Authentication Method option and press Enter. The Authentication Method pop up appears.
3. Select None, One-way CHAP, or Mutual CHAP and press Enter.
— One-way CHAP – With one-way CHAP authentication, the target authenticates the initiator. Use one-way
CHAP authentication for a one-way challenge and response security method – you must configure the
username and password (secret), which is authenticated by the target.
— Mutual CHAP – With mutual CHAP authentication, the target authenticates the initiator and the initiator
authenticates the target. Use mutual CHAP authentication for a two-way challenge and response security
method – you must configure different CHAP and mutual CHAP usernames and passwords.
NOTE When you configure the CHAP parameters, verify that those
parameters match the parameters on the storage side.
Broadcom
- 159 -
12.9.6 Pinging a Target
NOTE If you want to verify that you can connect to a target before you log in,
you must ping the target before you configure the target on the
Edit/Ping Target dialog.
To ping a target:
2. Select Ping and press Enter. If the ping is successful, the system displays a reply message pop up.
Figure 125 Successful Target Ping Pop Up
If the ping is not successful, the system displays a failure message. A ping can be unsuccessful for several reasons;
for more information, see Section 14.2, Troubleshooting for the iSCSI Protocol.
12.9.7 Viewing Advanced Properties
To view advanced properties:

1. On the Edit/Ping Target dialog (Figure 124), select Advanced Properties and press Enter. The Advanced iSCSI
Target Information dialog (Figure 126) appears.
NOTE You may need to select ..more to show additional configuration

options.
Broadcom
- 160 -
Figure 126 Advanced iSCSI Target Information Dialog
12.9.8 Logging In to or Out of a Target
To log in to or out of a target:

1. On the Edit/Ping Target dialog (Figure 124), select Login or Logout to explicitly log in to or log out of a target, and
then press Enter.

options.
12.9.9 Deleting a Target
NOTE A target can be deleted only if it is not a boot target.

If a target is set as a boot target:
1. On the Edit/Ping Target dialog (Figure 124), select Boot Target and press Enter. The Boot Target pop up opens.
2. Select No and press Enter.
To delete the target:
1. On the Edit/Ping Target dialog (Figure 124), select ..more to show additional configuration options.
2. Select Delete Target and press Enter.
12.9.10 Configuring LUNs
A LUN represents an individually addressable logical device that is part of a target. An initiator negotiates with a target
to establish connectivity to a LUN.
Broadcom
- 161 -
To configure a LUN:
1. On the Edit/Ping Target dialog (Figure 124), select LUN Configuration and press Enter. The LUN Configuration
dialog (Figure 127) opens.

options.
Figure 127 LUN Configuration Dialog
2. If the target is a boot target, select any single LUN as a boot LUN from the dropdown list.
NOTE If the target is not a boot target, you cannot select any LUNs.
12.9.11 iSNS Configuration
NOTE This functionality is available only on UEFI-capable HP adapters.

The iSNS Protocol allows automated discovery, management, and configuration of iSCSI and FC devices (using iFCP
gateways) on a TCP/IP network.
To view the iSNS Configuration dialog:
1. On the Controller Configuration Menu (Figure 112), select iSCSI Target Configuration and press Enter. The iSCSI
Target Configuration menu (Figure 128) appears.
Broadcom
- 162 -
Figure 128 iSCSI Target Configuration Menu
2. Select iSNS Configuration and press Enter. The iSNS Configuration dialog appears.
Figure 129 iSNS Configuration Dialog
The iSNS Configuration dialog enables you to perform the following tasks:
 Enable or disable iSNS discovery mode
 Enable or disable iSNS server discovery using DHCP
 Configure the iSNS server IP address and TCP port number manually
 View a list of available iSNS servers
12.9.11.1 Enabling iSNS Discovery

This option enables or disables iSNS discovery. iSNS targets are only discovered if this option is enabled.
To enable or disable iSNS discovery:
1. From the iSNS Configuration dialog (Figure 129), select iSNS Discovery Mode and press Enter. A pop up appears.
2. Select either Enable or Disable and press Enter.
3. Press the F10 key to save the current settings.
12.9.11.2 Enabling iSNS Server Discovery Using DHCP

This option discovers iSNS servers configured on the network using DHCP.
NOTE If you leave iSNS Server Discovery via DHCP disabled (default), you
must manually configure the iSNS server.
Broadcom
- 163 -
To enable or disable iSNS server discovery using DHCP:

1. From the iSNS Configuration dialog (Figure 129), select iSNS Server Discovery via DHCP and press Enter. A pop up
appears.
2. Select either Enable or Disable and press Enter.
3. Press <F10> to save the current settings.
12.9.11.3 Configuring the iSNS Server IP Address and TCP Port Number Manually
An iSNS server can also be configured manually by entering the server IP address and the TCP port. Only one iSNS
server can be configured at present.
NOTE This option is available only if the iSNS Server Discovery via DHCP
option is disabled.
To add an iSNS server manually:
1. From the iSNS Configuration dialog (Figure 129), select iSNS Server IP and press Enter.
2. Enter the iSNS server’s IP address and press Enter.
3. Select iSNS TCP Port and press Enter. The default iSNS Port is 3205. The valid range is 1024 to 65535.
4. Press the F10 key to save the current settings.
The added server appears under the Available Servers heading on the iSNS Configuration dialog as shown here.
Figure 130 Available Servers Dialog
12.9.11.4 Discovering Targets Using the iSNS Server

To configure targets using the iSNS server, from the iSNS Configuration dialog, select the iSNS server under the
Available Servers list (Figure 130) and press Enter. The iSNS server IP and TCP port information dialog appears
(Figure 131).
Broadcom
- 164 -
December 30, 2016 Erasing the Configuration
Figure 131 iSNS Server Options Dialog
The following iSNS server options are available on this dialog:

 Ping Server – Select this option to check connectivity to the server.
 Discover Targets – Select this option to show a list of targets available on the iSNS server.
One or more targets can be added by logging in to the targets individually. All added targets are listed under
Discovered Targets on the iSCSI Target Configuration menu (Figure 128).
 Remove Server – Select this option to remove the server from the Available Servers list.
NOTE This removes the server only and not the targets added by this server.
To remove the targets, select the target from the Discovered Targets
list under the iSCSI Target Configuration menu (Figure 128), select
Delete Target, and press Enter.
12.10 Erasing the Configuration
Erase Configuration erases the configuration of a single adapter. Configuration data is erased for both ports on the
selected adapter. Erase configuration restores the default settings for that particular adapter only. If an initiator name
is global for all adapters, the IQN configured on the first adapter is reflected on all adapters.

their factory default settings. For HP systems, the initiator name on all
ports of the selected adapter are reset to their respective default
values.
You must select Erase Configuration to clear out existing IQN data if
you purchase a different or subsequent license for the adapter.
To erase an adapter configuration:
1. From the Controller Configuration Menu (Figure 112), select Erase Configuration and press Enter (Figure 132).
Broadcom
- 165 -
December 30, 2016 Erasing the Configuration
Figure 132 Erase Configuration Dialog
2. Press Enter to erase the configuration, or press Esc to stop the operation.
When the adapter configuration is erased, the Controller Configuration Menu (Figure 112) appears.
Broadcom
- 166 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 13: Configuring UEFI for FCoE
December 30, 2016 Navigating the Emulex FCoE Configuration Utility
Chapter 13: Configuring UEFI for FCoE

NOTE If you have several adapters in your system, the UEFI system firmware
or boot code uses the highest version driver installed on any of the
adapters. Adapters with older versions of EFIBoot are managed by the
more recent version, but only as long as the adapter with the most
recent version is in the system. The latest firmware and boot code must
be installed on each adapter in the system to ensure that each adapter
runs the latest firmware and boot code.
UEFIBoot supports:
 Fabric point to-point topology only
 All applicable UEFI 2.3 driver protocols
 All UEFI-aware operating systems
 Selectable fibre or SCSI device path through the driver configuration application
 Up to 256 ports
 Up to eight boot targets (selectable through the driver configuration application)
 Up to 4096 LUNs
 Multiutility – Setup and firmware updates
The Emulex FCoE UEFIBoot is loaded from the flash in to the system memory.
To verify that the Emulex UEFIBoot driver is loaded, enter the UEFI Shell, type drivers, and then press Enter.
13.1 Navigating the Emulex FCoE Configuration Utility
Use the following methods to navigate the FCoE configuration utility:

Use the following methods to navigate the Emulex NIC configuration utility:
 Press the up/down arrows on the keyboard to move through menu options or fields. If multiple adapters are
listed, use the up/down arrows to scroll to the additional adapters.
 Press Enter to select a menu option, to select a row in a configuration dialog, or to change a configuration default.
 Use the navigation entries on the page to move about the utility.
13.2 Starting the Emulex FCoE Configuration Utility
To start the Emulex FCoE configuration utility using HII:

1. Exit the UEFI shell.
Broadcom
- 167 -
December 30, 2016 Starting the Emulex FCoE Configuration Utility
Figure 133 Exiting the UEFI Shell
The system displays a front page.
NOTE Depending on the vendor UEFI configuration, the menu item on the
front page that allows you to configure devices can be called Storage,
Device Manager, Device Settings, or something else; see the
documentation that accompanied the server.
2. Select the menu item that lets you configure devices. In the Device Manager (Figure 134), a list of all the adapters
in the system is shown. Your list may vary depending on the installed adapters.
Figure 134 Device Settings List
3. Select the adapter you want to configure and press Enter. The Emulex Adapter Configuration main menu
Broadcom
- 168 -
December 30, 2016 Updating Firmware and Boot Code
Figure 135 Emulex Adapter Configuration Main Menu
NOTE DCBX mode is always set to CEE and cannot be configured.ing
13.3 Updating Firmware and Boot Code
To update the firmware and boot code to the latest versions, you must use the NIC firmware update utility, which
revises the FCoE function with a single firmware and boot code image. For more information on revising firmware
versions, see Chapter 11, Configuring UEFI for Ethernet.
13.4 Enabling an Adapter to Boot from SAN
To enable an adapter to boot from SAN:

1. From the Device Manager list (Figure 134), select the adapter that you want to change the network boot setting
for and press Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
2. Select Set Boot from SAN and press Enter. A pop up appears.
3. Select Enable and press Enter. The selection is changed to NVRAM and the current setting appears.
Broadcom
- 169 -
December 30, 2016 Configuring CEE FCF Parameters
13.5 Configuring CEE FCF Parameters
To configure CEE FCF parameters:

1. From the Device Manager list (Figure 134), select the adapter to configure and press Enter. The Emulex Adapter
Configuration main menu (Figure 135) appears.
2. Select Configure CEE FCF Parameters and press Enter. The system displays a listing of the current CEE FCF record
information.
Figure 136 CEE Record Selection List
3. Select the CEE FCF record to modify and press Enter. The system displays the current record information.
Broadcom
- 170 -
December 30, 2016 Configuring CEE FCF Parameters
Figure 137 CEE FCF Record Information
4. Change the record information as needed.

— Set Record State can be set to unused, active, or boot.
— VLAN ID must be a three digit hexadecimal number.
— Switch Name (Low). Enter the low bits of the FC switch’s WWN to which to connect. This must be an 8-digit
hexadecimal number.
— Switch Name (Hi). Enter the high bits of the FC switch’s WWN to which to connect. This must be an 8-digit
hexadecimal number.
— Fabric Name (Low). Enter the low bits of the FC fabric’s WWN to which to connect. This must be an 8-digit
hexadecimal number.
— Fabric Name (Hi). Enter the high bits of the FC fabric’s WWN to which to connect. This must be an 8-digit
hexadecimal number.
5. Do one of the following:
— To save your changes, select Commit Changes and press Enter. The changed CEE FCF record information
appears.
— To discard all changes, select Discard Changes and press Enter. The system displays the CEE record selection
list (Figure 136).
— To discard your changes and use the CEE parameters from the FCF table, select Select From FCF Table and
press Enter. The system displays the FCF table parameters.
6. Press Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
Broadcom
- 171 -
December 30, 2016 Scanning for Fibre Devices
13.6 Scanning for Fibre Devices
When LUNs are set up on the SAN before POST has completed (that is, before the boot driver has been started), you
can select Scan for Fibre Devices or Add Boot Device to discover all available LUNs. Although this procedure does not
perform a complete adapter initialization, it runs faster than selecting Reconnect Devices.
NOTE If you dynamically add LUNs after POST has completed and the driver
has been started, you must select Reconnect Devices to perform a
complete adapter initialization and discovery. If this step is not
performed, all LUNs may not be properly discovered.
Select Reconnect Devices after adding any discovered LUNs to the
NVRAM list.
To scan for fibre devices:
1. From the Device Manager list (Figure 134), select the adapter you want to scan for fibre devices and press Enter.
The Emulex Adapter Configuration main menu (Figure 135) appears.
2. Select Scan for Fibre Devices and press Enter. A list of discovered targets appear. This list of discovered target
devices lets you quickly determine SAN connectivity only and provides you with a mechanism to have the port
logged in for zoning.
13.7 Adding Boot Devices
To add a boot device:

1. From the Device Manager list (Figure 134), select the adapter to which you want to add a boot device and press
Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
2. Select Add Boot Device and press Enter. A list of discovered targets appears (Figure 138).
Broadcom
- 172 -
December 30, 2016 Adding Boot Devices
Figure 138 SAN Discovery Targets List
3. Select a target and press Enter. The LUN list appears.
Figure 139 LUN Listing
4. Select a LUN from the list and press Enter. The SAN Discovery Target List (Figure 140) appears.
Broadcom
- 173 -
December 30, 2016 Deleting Boot Devices
Figure 140 SAN Discovery Target List
5. Select Commit Changes and press Enter to return to the Emulex Adapter Configuration main menu.
13.8 Deleting Boot Devices
To delete a boot device:

1. From the Device Manager list (Figure 134), select the adapter from which you want to delete a boot device and
press Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
2. Select Delete Boot Device and press Enter. The system displays a list of eight boot devices.
3. Select the device and press Enter. The Delete Boot Device dialog for that device appears (Figure 141).
Broadcom
- 174 -
December 30, 2016 Changing Boot Device Order
Figure 141 Delete Boot Device
4. Select DELETE and press Enter.

5. Select Commit Changes and press Enter to return to the Emulex Adapter Configuration main menu.
13.9 Changing Boot Device Order
NOTE The boot device order has no relationship to the system BIOS boot
device order. Changing the boot device order with this procedure only
changes the order in which the devices are discovered by UEFIBoot.
To change the boot device order:
1. From the Device Manager list (Figure 134), select the adapter for the boot device order you want to change and
2. Select Change Boot Device Order and press Enter. The Change Boot Device Order dialog (Figure 142) appears.
Broadcom
- 175 -
December 30, 2016 Changing Boot Device Order
Figure 142 Change Boot Device Order Dialog
3. Select Boot Device Order and press Enter.

4. Select a device from the list of eight boot devices and press Enter.
5. Use the + or - keys to change the order of the selected device in the dialog box and press Enter. The Change Boot
Device Order dialog (Figure 143) updates and displays the new boot device order.
Broadcom
- 176 -
December 30, 2016 Configuring Adapter Parameters
Figure 143 Change Boot Device Order with Revised Boot Order
6. Verify that the boot device list order is correct or make any additional changes you want and press Enter.
13.10 Configuring Adapter Parameters
This section explains how to configure the boot parameters for an adapter.
13.10.1 Changing the Port Login Retry Timer
This option lets you set the interval for the port login retry timer. This option is especially useful for Tachyon-based
RAID arrays. Under very rare occasions, a Tachyon-based RAID array resets itself and the port goes offline temporarily
in the loop. When the port comes to life, the port login retry interval scans the loop to discover this device.
You can choose:
 Disable (default setting)
 50 Msec
 100 Msec
 200 Msec
To change timer values:
1. From the Device Manager list (Figure 134), select the adapter you want to configure and press Enter. The Emulex
Adapter Configuration main menu (Figure 135) appears.
2. Select Configure HBA Parameters and press Enter. The Configure HBA Parameters dialog appears (Figure 144).
Broadcom
- 177 -
Figure 144 Configure HBA Parameters Dialog – Port Login Retry Timer Pop Up
3. Select PLOGI Retry Timer and press Enter. The Port Login Retry Timer pop up appears.
4. Select a retry timer option and press Enter. The screen is refreshed with the modified value.
NOTE Press Esc to return to the UEFI utility menu.

5. Select Commit Changes and press Enter to save the changes and return to the Emulex Adapter Configuration
main menu.
13.10.2 Changing the Maximum LUNs per Target
The maximum number of LUNs represents the maximum number of LUNs that are polled during device discovery. The
minimum value is 1 and the maximum value is 4096. The default is 256.
To change the maximum number of LUNs:
1. From the Device Manager list (Figure 134), select the adapter for the LUNs per Target information you want to
change and press Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
2. Select Configure HBA Parameters and press Enter. The Configure HBA Parameters dialog (Figure 145) appears.
Broadcom
- 178 -
Figure 145 Configure HBA Parameters Dialog
3. Select Maximum LUNs/Target and press Enter.

4. Enter a number from 1 to 4096 and press Enter. The screen is refreshed with the modified value.
NOTE The default and typical maximum number of LUNs in a target device is
256. A higher number of maximum LUNs causes the discovery to take
more time.
main menu.
13.10.3 Changing Boot Target Scan Method
This option is available only if none of the eight boot entries is configured to boot from the DID or WWPN. The Emulex
Adapter Configuration main menu is used to configure up to eight boot entries. With boot scan enabled, the first
device issues a Name Server Inquiry.
The boot scan options are:
 Boot Path from NVRAM Targets – Boot scan discovers LUNs saved to the adapter’s NVRAM only. Select up to
eight attached devices to use as potential boot devices. Limiting discovery to a set of eight selected targets can
greatly reduce the time it takes for the EFIBoot driver to complete discovery.
 Boot Path from Discovered Targets – Boot scan discovers all devices attached to the FC port. Discovery can take
a long time on large SANs if this option is used.
 Do not create boot path.
 EFIFCScanLevel: NVRAM Targets – Boot scan sets the EFIFCScanLevel environment variable to inform the driver
to configure targets in the NVRAM boot table only.
 EFIFCScanLevel - Discovered Targets – Boot scan sets the EFIFCScanLevel environment variable to inform the
driver to configure all available targets on the SAN.
Broadcom
- 179 -
To change the boot target scan method:

1. From the Device Manager list (Figure 134), select the adapter for the boot target scan method you want to
2. Select Configure HBA Parameters and press Enter. The Configure HBA Parameters dialog (Figure 145) appears.
3. Select Boot Target Scan Method and press Enter. The Boot Target Scan Method pop up appears.
Figure 146 Configure HBA Parameters Dialog – Boot Target Scan Method Pop Up
4. Select a boot scan option and press Enter. The screen is refreshed with the modified value.
NOTE If you have a large SAN and set the boot path to Boot Path Discovered
Targets, discovery takes a long time. Press Esc to return to the UEFI
utility menu.
main menu.
13.10.4 Changing Device Discovery Delay
This parameter sets a delay to occur after a loop initialization and before a scan is initiated to discover the target. The
default is off or 0 seconds. Change the default if you have an HP MSA1000 or HP MSA1500 RAID array, and if both of
the following conditions exist:
 The MSA array is direct connected or part of an arbitrated loop (for example, daisy chained with a JBOD).
 The boot LUN is not reliably discovered. In this case, a delay may be necessary to let the array complete a reset.
CAUTION Do not change the delay device discovery time if the MSA array is
connected to a fabric switch. Setting it to any other time guarantees
that the maximum delay time is seen on every loop initialization.
Broadcom
- 180 -
If both of the above conditions exist, typically set this parameter to 20 seconds. However, the delay should be only
long enough for the array to be reliably discovered after a reset. Your value may be different.
To change the delay device discovery value:
1. From the Device Manager list (Figure 134), select the adapter for the device discovery delay setting you want to
2. Select Configure HBA Parameters and press Enter. The Configure HBA Parameters dialog appears.
Figure 147 Configure HBA Parameters Dialog – Delay Device Discovery
3. Select Delay Device Discovery and press Enter. The Delay Device Discovery dialog appears.
4. Use the +/- keys to change the delay device discovery value in increments of 10 seconds and press Enter. The
screen is refreshed with the modified value.
main menu.
Broadcom
- 181 -
December 30, 2016 Resetting Emulex Adapters to Default Values
13.11 Resetting Emulex Adapters to Default Values
The UEFI utility enables you to clear the NVRAM target list and set all boot device WWNNs back to 0, along with setting
the adapter back to the default values. These default values are listed in the following table.
Table 10 Adapter Default Values

Enable/Disable BIOS Disabled Enabled
Disabled
Port Login Retry Timer Disabled Disabled
50 msec
100 msec
200 msec
Boot Target Scan Boot path from NVRAM targets Boot path from NVRAM targets
Boot path discovered targets
Do not create boot path
Maximum LUNs Setting 0256 0–4096
Delay Device Discovery 0000 0000–0255
Advanced Mode Enabled Enabled
Disabled
Disabled
VLAN Support Disabled Enabled
Disabled
VLAN ID 0 0–4094
VLAN Priority 0 0–7
UMC Support The default for this parameter varies Enabled
Function En/Dis Disabled Enabled
Disabled
Bandwidth 0% Must have a total of 100% across all ports.
LPVID 0 2–4094
Switch Option (Lenovo Virtual Fabric Mode Virtual Fabric Mode
System x Virtual Unified Fabric Protocol Mode
Fabric-capable
configuration, if Switch Independent Mode
available)
NOTE The following example sets the default values for FC/FCoE adapters
only. To set other adapters to their default settings, you must use the
utility for that specific protocol.
To set Emulex adapters to their default settings:
1. From the Device Manager list (Figure 134), select the adapter for the default settings you want to change and
Broadcom
- 182 -
December 30, 2016 Displaying Adapter Information
2. Select Set Emulex Adapter to Default Settings and press Enter. The Set Emulex Adapter to Default Settings dialog
Figure 148 Set Adapter Defaults Dialog
NOTE This sets the adapter to the FCoE driver default settings only.
3. Select Set Adapter Defaults and press Enter to set the adapter back to its default values. The Emulex Adapter
Configuration main menu (Figure 135) appears.
13.12 Displaying Adapter Information
The adapter information shown contains the following information about the selected adapter:
 Adapter status
 Network boot status
 Link speed
 Topology
 Firmware version
NOTE Refer to this firmware version if reporting an issue to Broadcom

Technical Support.
 Universal boot version
 EFI Boot version
To show adapter information:
1. From the Device Manager list (Figure 134), select the adapter for the information you want to view and press
Enter. The Emulex Adapter Configuration main menu (Figure 135) appears.
Broadcom
- 183 -
December 30, 2016 Configuring Legacy Only Settings
2. Select Display Adapter Info and press Enter. The system displays information about the selected
adapter(Figure 149).
Figure 149 Controller Information
13.13 Configuring Legacy Only Settings
Configuration settings for some adapters are available only through the Legacy Only Configuration Settings dialog.
The configuration settings include:
 Enabling or disabling spinup delay
 Enabling or disabling EDD 3.0
 Enabling or disabling start unit command
 Enabling or disabling environment variable
 Enabling or disabling auto boot sector
 Configuring the auto scan setting
To configure any of these settings:
1. From the Emulex Adapter Configuration main menu (Figure 135), select Legacy Only Configuration Settings and
press Enter. The Legacy Only Configuration Settings dialog appears (Figure 150).
Broadcom
- 184 -
Figure 150 Legacy Only Configuration Settings Dialog
13.13.1 Enabling or Disabling the Spinup Delay
This option lets you enable or disable the disk spinup delay. The factory default setting is disabled.
If at least one boot device has been defined, and the spinup delay is enabled, the boot BIOS searches for the first
available boot device.
 If a boot device is not ready, the boot BIOS waits for the spinup delay and, for up to three additional minutes,
continues the boot scanning algorithm to find another multiboot device.
If boot devices have not been defined and auto scan is enabled, then the boot BIOS waits for five minutes before
scanning for devices.
 In an attached fabric, the boot BIOS attempts to boot from the first target found in the NameServer data.
To enable or disable the spinup delay:
1. On the Legacy Only Configuration Settings dialog (Figure 150), select Enable or Disable Spinup Delay and press
Enter. A pop up appears.
3. Select Commit Changes and press Enter to save the changes and return to the Legacy Only Configuration
Settings dialog.
13.13.2 Enabling or Disabling EDD 3.0
EDD 3.0 provides additional data to the operating system boot loader during an INT-13h function 48h call (get device
parameters). This information includes the path to the boot device and the disk size. The default setting for EDD 3.0 is
enabled. If EDD 3.0 is disabled, the setting reverts to EDD 2.1.
Broadcom
- 185 -
To enable or disable EDD 3.0:

1. On the Legacy Only Configuration Settings dialog (Figure 150), select Enable or Disable EDD 3.0 and press Enter.
A pop up appears.
Settings dialog.
13.13.3 Enabling or Disabling the Start Unit Command
You must know the specific LUN to issue the SCSI start unit command. The default setting is disabled.
To enable or disable the start unit command:
1. On the Legacy Only Configuration Settings dialog (Figure 150), select Enable or Disable Start Unit Command
and press Enter. A pop up appears.
Settings dialog.
13.13.4 Enabling or Disabling the Environment Variable
Sets the boot adapter order if the system supports the environment variable. The default setting is disabled.
To enable or disable the environment variable:
1. On the Legacy Only Configuration Settings dialog (Figure 150), select Enable or Disable Environment Variable
and press Enter. A pop up appears.
Settings dialog.
13.13.5 Enabling or Disabling Auto Boot Sector
This option automatically defines the boot sector of the target disk for the migration boot process, which applies to
HP MSA1000 arrays only. If there is no partition on the target, the default boot sector format is 63 sectors. The default
To enable or disable the auto boot sector format:
1. On the Legacy Only Configuration Settings dialog (Figure 150), select Enable or Disable Auto Boot Sector and
press Enter. A pop up appears.
Settings dialog.
13.13.6 Configuring the Auto Scan Setting
This option lets you enable or disable the auto scan feature. Auto scan is available only when all eight boot entries are
unused (empty). The factory default for auto scan is disabled. Auto scan lets you boot from the first boot device found
in the FC fabric with the following options:
Broadcom
- 186 -
December 30, 2016 Requesting a Reset or Reconnect
 Any first device – The first adapter scans the fabric and the first disk discovered becomes the attempted boot
device
To configure auto scan:
1. On the Legacy Only Configuration Settings dialog (Figure 150), select Auto Scan Setting and press Enter. A pop up
appears.
2. Select the appropriate auto scan option and press Enter.
Settings dialog.
13.14 Requesting a Reset or Reconnect
After you have made certain changes to the UEFI BIOS, you may need to reset or reconnect the adapter for the
changes to take effect.
Reset forces the system to reboot after you exit the UEFIBoot (HII) utility.
Reconnect unloads and reloads the driver. This allows any changes to take effect immediately without requiring a
reboot.
To request a reset or reconnect, do the following:
1. From the Emulex Adapter Configuration main menu (Figure 135), select Request RESET or RECONNECT to Make
Changes Active. The Request RESET or RECONNECT to Make Changes Active dialog appears (Figure 151).
Figure 151 Request RESET or RECONNECT to Make Changes Active Dialog
Broadcom
- 187 -
December 30, 2016 Requesting a Reset or Reconnect
2. Do one of the following:

 To request a reset:
a. Set Request RESET to yes to notify the system BIOS that you want to perform a system reset.
b. Exit the UEFIBoot (HII) utility and return to the system BIOS setup screens.
c. A pop up window prompts you to reset the system. Any changed Emulex adapter settings become active
during the subsequent reboot.
 To request a reconnect:
a. Set Request RECONNECT to yes to notify the system BIOS that you want to perform a disconnect and
reconnect on the adapter port.
b. The changed Emulex adapter settings are activated without a system reset.
Broadcom
- 188 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Chapter 14: Troubleshooting
December 30, 2016 Troubleshooting for the NIC Protocol
Chapter 14: Troubleshooting

This section provides troubleshooting information for the supported networking protocols.
14.1 Troubleshooting for the NIC Protocol
This section provides troubleshooting information for the PXESelect utility.
14.1.1 Issues During the PXE Boot Process
Situation: If any of the following occur during the boot process:

 The PXE boot ROM sends a DHCP request extended with PXE specific options, but the request is not received.
 The DHCP responses do not contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot
server lists.
 The PXE client attempts to download the specified NBP over TFTP from one of the specified boot servers, but fails.
 The PXE client does not execute the downloaded NBP.
Outcome: If any of these issues occur, the boot process continues using the next available device in the boot
sequence.
Broadcom
- 189 -
14.1.2 PXE Error Codes
Table 11 PXE Error Codes
Error Codes Possible Reason Comment/Solution
Init Error Codes

PXE-E01: PCI Vendor and Device The PCI BIOS passes This message should never be seen in
IDs do not match! Bus/Device/Function numbers in AX the production level BIOS.
register when it initializes the
OptionROM. If the vendor ID & device
ID did not match the vendor ID and
the device ID in the PCI configuration
space for the device, with the UNDI
device PCI structure defined in UNDI
driver initialization code, the system
displays this error.
PXE-E04: Error reading PCI Any of the PCI BIOS INT 1Ah calls to This should not happen with any
Configuration space read the PCI configuration space production level motherboard BIOS.
failed.
PXE-E07: PXE BIOS calls not The PCI system BIOS does not This should not happen with any PCI
supported. support INT 1Ah services. BIOS as all PCI BIOS must support
these services.
ARP/TFTP Error Codes
PXE-E11:ARP timeout An ARP request is tried four times and Check the DHCP server settings. If
the client did not receive an ARP you are connected through a switch,
reply. also check the switch settings.
PXE-E32: TFTP Open timeout. A DHCP address and boot file name  Check that the TFTP is
has been obtained and attempts to configured properly.
download the file name from a  Check that the filename is
remote server. properly placed in the tftpboot
directory.
 Check that the PXE server is
configured for TFTP not MTFTP.
PXE-E35: TFTP read timeout. A TFTP server is not able to receive Check that the hardware and TFTP
the next packet. server are functioning properly.
PXE-E36: Error received from TFTP A TFTP server sends an error packet. Check the TFTP server settings and
server. boot file settings.
PXE-E38: TFTP cannot open A TFTP client is not able to open a Check that the correct boot file is
connection. TFTP connection with the TFTP copied into the default TFTP boot
server. path.
PXE-E3B: TFTP error-File not found A requested boot file is not found on Check that the correct boot file is
TFTP server. copied into the default TFTP boot
path.
PXE-E3C: TFTP error - Access The TFTP server does not have Check the file permissions for the
violation. enough access rights to open or read TFTP server.
the file.
PXE-E3F: TFTP packet size is invalid TFTP packet received is larger than Check the MTU on the Server side NIC
1456 bytes. interface.
Boot/DHCP Error Codes
PXE-E51: No DHCP or Proxy DHCP The client did not receive any valid Check that the boot file name is
offers were received. DHCP, BOOTP, or Proxy DHCP offers. configured correctly for PXE Clients in
the DHCP setup.
Broadcom
- 190 -
Table 11 PXE Error Codes (Continued)

PXE-E52: Proxy DHCP offers were The client did receive at least one Check that the DHCP server and PXE
received. No DHCP offers were valid proxyDHCP offer, but did not server are configured properly.
received. receive any valid DHCP or BOOTP
offers.
PXE-E53: No boot filename The client did receive a valid Check that the boot file name is
received. BOOTP/DHCP offer, but does not configured correctly for PXEClients in
have a boot file name to download in the DHCP setup.
the DHCP offer.
PXE-E55: Proxy DHCP service did The client issued a proxy DHCP Check that the DHCP server and TFTP
not reply to request on port 4011. request to the DHCP server on port server are properly configured on
4011 but did not receive a reply. different servers. This issue may
happen only if both are configured
on separate servers.
UNDI Error Codes
PXE-E60: Invalid UNDI API function The underlying UNDI drivers do not Check with the hardware vendor.
number support the UNDI API sent from
BaseCode/NBP.
PXE-E61: Media test failed, check No physical link exists on the PXE Check the cables on the NIC interface.
cable. client port on which the boot is
attempted.
PXE-E63: Error while initializing the An issue in initializing the hardware Check with the hardware vendor.
NIC. exists as part of the UNDI_Initialize
API.
BaseCode/UNDI Loader Error Codes
PXE-EC1: BaseCode ROM ID The UNDI boot module can not find
structure was not found. the BaseCode ROM ID structure. This
can be caused by a corrupted
BaseCode ROM image.
PXE-EC3: BaseCode ROM ID The BaseCode ROM ID structure is
structure is invalid. invalid. This can be caused by a
corrupted BaseCode image in ROM.
PXE-EC4: UNDI ROM ID structure The BaseCode loader module could
was not found. not locate the UNDI ROM ID
structure. The UNDI ROM image is
probably corrupted.
PXE-EC5: UNDI ROM ID structure is The UNDI ROM image is probably
invalid. corrupted.
PXE-EC8:!PXE structure was not The UNDI ROM image is probably
found in UNDI driver code corrupted.
segment.
Bootstrap and Discovery Error Codes
PXE-E74: Bad or missing PXE menu PXE tags were detected but the boot
and /or prompt information menu and/or boot prompt were not
found or were invalid.
PXE-E77: Bad or missing discovery Two possible reasons. One is that
server list. Multicast and Broadcast discovery are
both disabled. The other is that
Multicast and Broadcast are enabled,
but the server list tag is not found or
is invalid.
Broadcom
- 191 -
December 30, 2016 Troubleshooting for the iSCSI Protocol
Table 11 PXE Error Codes (Continued)

PXE-E78: Could not locate boot
server.
PXE-E79: NBP is too big to fit in free The NBP file size is larger than the free Check the NBP file size.
base memory. base memory.
Miscellaneous Error Codes
PXE-EA0: Network boot cancelled Pressing Ctrl+C keys during DHCP
by keystroke discovery.
14.2 Troubleshooting for the iSCSI Protocol
This section includes troubleshooting information for the iSCSISelect utility.
Table 12 Troubleshooting the iSCSISelect Utility
Issue Answer/Solution
iSCSI BIOS banner is not displayed during system post.  Check the motherboard BIOS configuration and make sure that the Option ROM is
enabled and is set for the PCIe slot into which the adapter is inserted.
 If the Option ROM is enabled and is set for the PCIe slot into which the adapter is
inserted and the issue remains, erase the adapter configuration. For more
information, Section 9.5, Erasing the Current Configuration.
Unable to ping iSCSI target IP address  Check cable connections and make sure they are securely connected at both ends.
Make sure the link light is ON at both ends of the cable.
 Verify that you have assigned a valid IP address with the correct subnet mask to the
interfaces connected to the network.
 Check for duplicate IP addresses.
 Make sure you are connected to the correct port.
 If the IP address is coming from DHCP, check that the DHCP server is up and
available.
 Is the target on a different subnet? Check the default gateway and make sure the IP
addresses of both the default gateway and the remote host are correct.
 Check link status under the Network Configuration dialog. If you try changing the
initiator link status, you can back out one screen then go back to the Network
Configuration dialog to see a view of the current link status.
Login to iSCSI target fails or login succeeds, but no  Check the initiator IQN name and the target IQN name. Verify that they are properly
LUNs are available. specified.
 Check the target's ACL settings (if any) to verify that the initiator's IQN name is listed
and can be recognized.
 Make sure that the target login parameters are compatible with the initiator's.
 If this checklist confirms that initiator and target are configured correctly and the
issue remains, erase the adapter configuration. For more information, see
Section 9.5, Erasing the Current Configuration.
Login to iSCSI target is successful, but iSCSI I/O causes Check the jumbo frame settings on the iSCSI target. If enabled, change the frame size to
the system to hang or freeze. 1514 and retry. This isolates any issues in the network related to jumbo frames. Jumbo
frames, if supported by the entire network, provide increased performance.
NOTE Emulex OneConnect adapters support jumbo frames.
Broadcom
- 192 -
December 30, 2016 Troubleshooting for the iSCSI Protocol
Table 12 Troubleshooting the iSCSISelect Utility (Continued)
Unable to boot from the iSCSI target.  Check the target setup. Check the target ACL to verify that the initiator's iSCSI name
is listed and can be recognized.
 Check the initiator name and make sure it is correct.
 If applicable, verify that you have selected the iSCSI LUN as the boot LUN in the
system BIOS setting.
 Check the system BIOS for boot device priority order. Make sure that the boot
device is at the top.
If using DHCP:
 If Boot Support is not enabled, enable it on the iSCSI Initiator dialog. (For more
information, see Chapter 9, Configuring and Managing the iSCSI Initiator with the
iSCSISelect Utility.)
 If DHCP boot support is enabled, check the DHCP setup and also verify that you
have added the root path to the DHCP server. For more information, see Section 8.2,
Setting Up a Basic iSCSI Boot Configuration.
 If this checklist confirms that the initiator and target are configured correctly and
the issue remains, erase the adapter configuration. For more information, see
Section 9.5, Erasing the Current Configuration.
BIOS post shows BIOS Not Installed message.  If you have not configured an iSCSI boot target, this is proper normal behavior.
 If you have configured an iSCSI boot target and the BIOS cannot find a bootable
LUN, then refer to the solutions provided in the issue Unable to boot from the iSCSI
target.
If solutions for issues 1-3 and 5-6 all fail. Use the iSCSISelect utility to erase the adapter configuration. To clear the adapter
configuration:
1. From the Controller Configuration menu, select Erase Configuration and press Enter.
2. The system displays a message asking if you want to erase the current
configuration. Press Y.
3. You are cautioned that the operation removes any existing configuration
permanently. Press Y.
NOTE If you have multiple adapters, you must erase the configuration of each adapter
separately. For more information, see Section 9.5, Erasing the Current Configuration.
After you erase the adapter configuration, reboot the system and then reconfigure the
adapter.
You receive this POST error message: In the iSCSI BIOS, the iSCSI initiator name can be different if there is more than one
Initiator iSCSI Name mismatch, Emulex adapter in the system. If the iSCSI initiator name is different on multiple adapters,
you receive a POST error message indicating an iSCSI name mismatch. You must enter
Please use iSCSISelect to set a the iSCSISelect utility and save a new initiator name on the first iSCSISelect utility menu
single name for all controllers. so the iSCSI initiator name on all adapters match. All logins from the multiple adapters
Press <Ctrl><S> to enter use the new name.
iSCSISelect. (Reboot required)
You receive any of the following POST error messages These POST messages indicate that you must reload the adapter firmware using the
or warnings: Emulex OneCommand CNA Manager application or one of the Emulex online or offline
Redboot Initialization failed... utilities. If the errors remain, contact Broadcom Technical Support.
Firmware Load failed...
DDR config failed...
DDR callibrate failed...
DDR test failed...
SEEPROM checksum failed...
Secondary firmware image loaded...
You receive this POST error message: The firmware loaded on this adapter is not supported. Load the appropriate firmware for
Firmware halted. This firmware the adapter.
does not support this controller.
Broadcom
- 193 -
December 30, 2016 Troubleshooting for the FCoE Protocol
14.3 Troubleshooting for the FCoE Protocol
Table 13 Troubleshooting the FCoE Protocol
Cisco Nexus switch configuration situations: Ensure that the FCoE switch ports are configured correctly for the adapter’s FCoE
 Windows creates the NTFS partition properly, but settings.
then reports that The hard disk
containing the partition or free
space you chose has a LUN greater
than 0. Setup cannot continue. (Dell
1850 server).
 Windows reboots successfully, but then gets
stuck during the GUI portion of the installation
right from the beginning. (HP DL385G2 server).
Broadcom
- 194 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix A: Configuring iSCSI through a DHCP Server Using Vendor-Specific Option 43
December 30, 2016 Format of Vendor-Specific Option 43
Appendix A: Configuring iSCSI through a DHCP Server Using

Vendor-Specific Option 43
An iSCSI initiator requires the following parameters to boot from a target:
 Its IP address
 Its unique node name
 The boot iSCSI target IP address
 The boot target name. If not available, this may be discovered using the iSCSI discovery protocol.
 The target non-default TCP port number (if applicable)
 Header and data digest settings to be used with the target
 Authentication parameters, if applicable
If your boot BIOS allows it, you can configure all of the above parameters from a centrally configured DHCP server
using vendor-specific option 43. This appendix documents this method of configuration. For this method, the initiator
must be configured (using non-DHCP means) with the appropriate DHCP vendor ID. The method and format for
specifying the vendor ID is outside the scope of this document. The initiator offers this Vendor ID to the DHCP server
to retrieve data in the format described in the following sections.
Two other configuration methods are not documented in this appendix:
 Manual configuration using iSCSISelect or SMCLP/MILI
 Pre-boot configuration using CLP /BIOS 3.0
A.1 Format of Vendor-Specific Option 43
The format for vendor-specific option 43 is as follows:

iscsi:<ipaddress>:<protocol>:<iscsi port number>:<lun>:<target name>
Fields enclosed in angular brackets (including the angular brackets) must be replaced with their corresponding
values. All fields are case insensitive.
See the example at the end of this document.
A.1.1 Description of Parameters
A.1.1.1 <ipaddress>
Replace this parameter with a valid IPv4 address in dotted decimal notation. This is a mandatory field.
A.1.1.2 <protocol>
Replace this parameter with a decimal number indicating the TCP port. The default TCP port is 3260.
A.1.1.3 <iscsi port number>

Replace this parameter with a decimal number ranging from 1 to 65535 (inclusive). It is an optional field.
A.1.1.4 <lun>
This parameter is a hexadecimal representation of the logical unit number of the boot device. It is an optional field. If
not provided, LUN 0 is assumed to be the boot LUN. It is an 8-byte number which must be specified as a hexadecimal
number consisting of 16 digits, with an appropriate number of 0’s padded to the left, if required.
Broadcom
- 195 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix A: Configuring iSCSI through a DHCP Server Using Vendor-Specific Option 43
December 30, 2016 Format of Vendor-Specific Option 43
A.1.1.5 <target name>

Replace this parameter with a valid iSCSI target ’iqn’ name of up to 223 characters. This is a mandatory field.
A.1.2 Example
iscsi:010.010.010.001:0:3260:0:iqn.1992-08.com.netap:sn.151729740
The above example specifies the following:
 Target IP address: 010.010.010.001
 Target protocol: 0
 Target TCP port: 3260
 Target boot LUN: 0
 Target iqn name: iqn.1992-08.com.netap:sn.151729740
Broadcom
- 196 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix B: Example for Installing and Configuring Linux or Citrix for PXE Boot and
December 30, 2016 UEFIBoot
Linux and Citrix PXE Server Remote Installation Procedure
Appendix B: Example for Installing and Configuring Linux or Citrix

for PXE Boot and UEFIBoot
This section provides examples for installing and configuring Linux and Citrix for PXE boot and UEFIBoot.
B.1 Linux and Citrix PXE Server Remote Installation Procedure
PXE configuration requires a PXE server and the PXE client.

Setting up a PXE server requires the following configurations:
 NFS server
 TFTP server
 DHCP server
 PXE boot server
The pxelinux functionality occurs in this order:
1. The client machine boots to PXE, which requests a DHCP address.
2. The DHCP server responds with an IP address for the client machine, the address of a TFTP server, and a filename
to load (pxelinux.0) from that server.
3. The client downloads pxelinux.0 from the specified TFTP server and executes it.
4. The pxelinux.0 file searches the pxelinux.cfg directory on the server for a configuration file that matches the
IP address of the machine. If no matches are found, it attempts to load a file called default.
5. The configuration file loaded by pxelinux.0 has instructions on what to do next. Some of the choices include boot
to local hard drive, boot to an image file (floppy image), or load vmlinuz and initrd.img.
6. The client searches for a configuration file with the IP address converted to hexadecimal (for example,
192.168.1.60 becomes C0A8013C) or the MAC address of your PXE boot client’s Ethernet card with a prefix of 01.
The MAC address must be separated with dashes instead of colons.
In this example, the client looks for the following configuration file names and uses the first one it finds.
01-00-00-C9-5B-75-A8
C0A8013C
C0A8013
C0A801
C0A80
C0A8
C0A
C0
C
default
7. The default file’s contents should look similar to the following:
prompt 1
default linux
timeout 100
label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=9216 noapic acpi=off
Broadcom
- 197 -
B.1.1 PXE Server
This section provides configuration scripts for the PXE server.
B.1.1.1 NFS Server Configuration Script

[root@bglinux156 ~]# mkdir /work
[root@bglinux156 ~]# mount 10.192.194.110:/work /mnt
[root@bglinux156 ~]# cd /mnt/
[root@bglinux156 ~]# cp -r rhel5564/ /work/ #copy the entire
directory to “/work”
[root@bglinux156 ~]# cd /work/rhel5564
[root@bglinux156 ~]# cp -r images/ /tftpboot/linux-install/
[root@bglinux156 ~]# vim /etc/exports###(Add “/work *(rw,sync)”)
[root@bglinux156 ~]# exportfs -a (reflect changes in NFS Server)
1. Restart NFS Services.
[root@bglinux156 ~]# /etc/rc.d/init.d/portmap restart
Stopping portmap: [ OK ]
Starting portmap: [ OK ]
[root@bglinux156 ~]# /etc/rc.d/init.d/nfslock restart
Stopping NFS locking: [ OK ]
Stopping NFS statd: [ OK ]
Starting NFS statd: [ OK ]
[root@bglinux156 ~]# /etc/rc.d/init.d/nfs restart
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
2. Check if the NFS services are running.
[root@bglinux156 ~]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 56782 nlockmgr
100021 1 tcp 44855 nlockmgr
100024 1 udp 766 status
100024 1 tcp 769 status
100011 1 udp 815 rquotad
100011 1 tcp 818 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
Broadcom
- 198 -
100003 3 tcp 2049 nfs

100003 4 tcp 2049 nfs
100005 1 udp 828 mountd
100005 1 tcp 831 mountd
100005 2 udp 828 mountd
100005 2 tcp 831 mountd
100005 3 udp 828 mountd
B.1.1.2 TFTP Server Setup

[root@bglinux156 ~]# vi /etc/xinetd.d/tftp
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot/linux-install #This line specifies
#path where the pxe boot searches for
#the images
disable = no #convert this line from yes to no
per_source = 11
cps = 100 2
flags = IPv4
}
[root@bglinux156 ~]# /sbin/chkconfig --level 345 xinetd on

[root@bglinux156 ~]# /sbin/chkconfig --level 345 tftp on
[root@bglinux156 ~]# service xinetd restart
B.1.1.3 DHCP Server Configuration

1. Install the following RPMs in the server if not installed:
[root@bglinux156 ~]# rpm -qa | grep dhcp
dhcpv6-client-1.0.10-18.el5
dhcp-devel-3.0.5-23.el5
dhcp-3.0.5-23.el5
2. Make the following entry in /etc/dhcpd.conf file:
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
ddns-update-style interim;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.50 192.168.1.90;
default-lease-time 3600;
max-lease-time 4800;
option subnet-mask 255.255.255.0;
option domain-name “pxe_text”;
option time-offset -8;
}
Broadcom
- 199 -
host bglinux45{
next-server 192.168.1.1;
hardware ethernet 00:00:C9:5B:75:A8;
fixed-address 192.168.1.60;
option host-name “linux-test”;
filename “pxelinux.0”;
}
###This sets up a DNS server that will assign IP Address 192.168.1.60
###to the client machine that has MAC Address “00:00:C9:5B:75:A8”
###assigned to a PXE capable NIC
###The only thing that needs to be changed in the above, is the MAC
###Address to match that of the NIC in the client box
###The IP address that follows the next-server option should be the IP
###address of the tftp server
[root@bglinux156 ~]# service dhcpd restart

Shutting down dhcpd: [ OK ]
Starting dhcpd: [ OK ]
B.1.1.4 PXE Boot Server Configuration

[root@bglinux156 ~]# rpm -qa | grep system-config-netboot
system-config-netboot-cmd-0.1.45.1-1.el5
system-config-netboot-0.1.45.1-1.el5
B.1.2 Copying Files to the TFTP Server with the Graphical Version of the Network Booting Tool
Copy the necessary files to start the installation to the TFTP server so they can be found when the client requests
them. Run the Network Booting Tool on the NFS, FTP, or HTTP server. A separate PXE server is not necessary.
To use the graphical version of the Network Booting Tool, you must be running the X Window System, have root
privileges, and have the redhat-config-netboot.rpm package installed.
To start the Network Booting Tool from the desktop, do one of the following:
 Go to the Main Menu Button (on the Panel) and select System Settings >Server Settings >Network Booting
Service.
Or
 Type the command system-config-netboot at a shell prompt. (For example, in an XTerm or a GNOME
terminal.)
NOTE If you are starting the Network Booting Tool for the first time, select
Network Install from the First Time Druid.
Copy the files necessary to start the installation to the TFTP server.
1. Select Configure > Network Installation from the pull-down menu (Figure 152).
Broadcom
- 200 -
Figure 152 Network Installation and Diskless Environment Window
The following Configure Network Installations window appears.
Figure 153 Configure Network Installations Window
2. Click Add.
The following Network Installation Dialog window (Figure 154) appears.
Broadcom
- 201 -
Figure 154 Network Installation Dialog Window
3. Enter the operating system identifier and description.

4. Select pxe as the protocol for installation.
5. Enter the IP address of the TFTP server (as set up in the DHCP server configuration) in the server IP address field.
6. Enter a directory location for the server.
The following Network Installation and Diskless Environment window shows the IP address of the TFTP server.
Figure 155 Network Installation and Diskless Environment Window with IP Address
B.1.2.1 Configuring the Host

To configure the host:
1. Double-click the IP address row in the Network Installation and Diskless Environment window (Figure 155). The
following Edit window (Figure 156) appears.
Broadcom
- 202 -
Figure 156 Edit Window
2. In the Hostname or IP Address/Subnet field, enter the IP address, fully qualified hostname, or a subnet of systems
that should be allowed to connect to the PXE server for installations. In Figure 156, the Hostname or IP
Address/Subnet field is the IP address of the client machine.
3. In the case of a multiboot environment, select an operating system preference.
4. Select the operating system identifier to install on this client. The list is populated from the network install
instances created from the Network Installation dialog box.
5. If you use a serial console, check the Serial Console check box.
6. Specify the location of a kickstart file, such as http://server.example.com/kickstart/ks.cfg. This
file can be created with the Kickstart Configuration.
NOTE Ignore the Snapshot name and Ethernet options. They are used for
diskless environments only.
7. Click OK. This closes the window and creates configuration files within:
/tftpboot/linux-install and /tftpboot/linux-install/pxelinux.cfg
8. Go to /tftpboot/pxelinux.cfg and open the file C0A8013C. The C0A8013C file is created when you
assign the client IP using system-config- netboot. This is the hexadecimal address of the IP assigned to
the client NIC. It is 192.168.1.60 in the example in Figure 155.
B.1.2.2 Enabling the PXE Client with a PXE-Enabled Adapter

The PXE client must have a PXE-enabled adapter.
1. Power on the PXE client.
2. In the Enabling Network Boot window, press the F12 key to enable network boot (Figure 157). Pressing the F12
key accesses the DHCP server IP and the Boot Linux image.
Broadcom
- 203 -
Figure 157 Enabling Network Boot Window
Broadcom
- 204 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix C: Examples for Configuring and Booting UEFI NIC
December 30, 2016 UEFI NIC Server Configuration Script for SLES11 SPx
Appendix C: Examples for Configuring and Booting UEFI NIC

This section provides examples for configuring and booting UEFI NIC.
C.1 UEFI NIC Server Configuration Script for SLES11 SPx
[root@orleansrhel5564 ~]# ls /root/sles11sp164/

SLES-11-SP1-DVD-x86_64-GM-DVD1.iso
[root@orleansrhel5564 ~]# mkdir test1
[root@orleansrhel5564 ~]# mkdir test2
[root@orleansrhel5564 ~]# mount -o loop
sles11sp164/SLES-11-SP1-DVD-x86_64-GM-DVD1.iso test1
[root@orleansrhel5564 ~]# ls test1
ARCHIVES.gz COPYING.degpg-pubkey-3d25d3d9-36e12d04.asc media.1
boot COPYRIGHT gpg-pubkey-7e2e3b05-4be037ca.asc NEWS
ChangeLog COPYRIGHT.degpg-pubkey-9c800aca-4be01999.asc pubring.gpg
content directory.yast gpg-pubkey-a1912208-446a0899.asc README
content.ascdocu gpg-pubkey-b37b98a9-4be01a1a.asc suse
content.keygpg-pubkey-0dfb3188-41ed929b.ascINDEX.gz
control.xmgpg-pubkey-1d061a62-4bd70bfa.asclicense.tar.gz
COPYING gpg-pubkey-307e3d54-4be01a65.ascls-lR.gz
[root@orleansrhel5564 ~]# mount -o loop test1/boot/x86_64/efi test2
[root@orleansrhel5564 ~]# ls -lar test2
total 28
-rwxr-xr-x 1 root root 48 May 20 2010 .packages.boot-efi
drwxr-xr-x 3 root root 2048 May 20 2010 efi
drwxr-x--- 20 root root 4096 Jan 5 14:04 ..
drwxr-xr-x 3 root root 16384 Jan 1 1970 .
[root@orleansrhel5564 ~]# ls -lar test2/efi/boot/
bootx64.efi elilo.conf initrd linux
[root@orleansrhel5564 ~]# ls -lar test2/efi/boot/
total 26838
-rwxr-xr-x 1 root root 3231872 May 20 2010 linux
-rwxr-xr-x 1 root root 23999623 May 20 2010 initrd
-rwxr-xr-x 1 root root 512 May 20 2010 elilo.conf
-rwxr-xr-x 1 root root 241318 May 20 2010 bootx64.efi
drwxr-xr-x 3 root root 2048 May 20 2010 ..
drwxr-xr-x 2 root root 2048 May 20 2010 .
[root@orleansrhel5564 ~]# cp test2/boot/efi/* /tftpboot/linux-install/
C.1.1 NFS Server Configuration Script
[root@bglinux156 ~]# /etc/rc.d/init.d/portmap restart

Stopping portmap: [ OK ]
Starting portmap: [ OK ]
[root@bglinux156 ~]# /etc/rc.d/init.d/nfslock restart
Stopping NFS locking: [ OK ]
Stopping NFS statd: [ OK ]
Starting NFS statd: [ OK ]
[root@bglinux156 ~]# /etc/rc.d/init.d/nfs restart
Broadcom
- 205 -
Shutting down NFS mountd: [ OK ]

Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services:[ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
#### Check if the NFS services are running:
[root@bglinux156 ~]# rpcinfo -p
100024 1 udp 766 status
100024 1 tcp 769 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 828 mountd
100005 1 tcp 831 mountd
100005 2 udp 828 mountd
100005 2 tcp 831 mountd
100005 3 udp 828 mountd
C.1.2 DHCP Server Configuration
[root@orleansrhel5564 ~]# cat /etc/dhcpd.conf

1. Install the following RPMs in the server if not installed:
[root@bglinux156 ~]# rpm -qa | grep dhcp
dhcpv6-client-1.0.10-18.el5
dhcp-devel-3.0.5-23.el5
dhcp-3.0.5-23.el5
2. Make the following entry in /etc/dhcpd.conf file:
#
#
Broadcom
- 206 -
#ignore client-updates;
subnet 192.168.47.0 netmask 255.255.255.0 {
range 192.168.47.50 192.168.47.100;
max-lease-time-4800;
option domain-name "pxe_test";
option time-offset -8; # Eastern Standard Time
}
# we want the nameserver to appear at a fixed address

host orleansrhel5564 {
next-server 192.168.47.1;#IP of the NFS Server
hardware ethernet 00:00:c9:5b:a5:26;#mac address of
#the client
#machine
fixed-address 192.168.47.60; #IP assigned to the

#client machine
option host-name "linux-test";
filename "bootx64.efi"; #Used for UEFI boot
}
###This sets up a DNS server that will assign IP Address 192.168.47.60

###to the client machine that has MAC Address "00:00:c9:5b:a5:26"
###assigned to a PXE(UEFI) capable NIC
###The only thing that needs to be changed in the above, is the MAC
###Address to match that of the NIC in the client box
###The IP address that follows the next-server option should be the IP
###address of the tftp server
[root@bglinux156 ~]# service dhcpd restart
C.1.3 TFTP Server Setup
[root@orleansrhel5564 ~]# cat /etc/xinetd.d/tftp

service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server_args = -s /tftpboot/linux-install
per_source = 11
cps = 100 2
flags = IPv4
Broadcom
- 207 -
December 30, 2016 UEFI NIC Server Configuration Script for RHEL 6.x
C.2 UEFI NIC Server Configuration Script for RHEL 6.x
This section provides UEFI NIC server configuration scripts to use on RHEL 6.x operating systems.
C.2.1 Setup Information
PXE client server: Dell R710 with Emulex adapter

PXE server: HP running RHEL 5.5 64 bit
C.2.2 NFS Configuration
[root@orleans ~]# mkdir /work

[root@orleans ~]# mount 10.192.194.110:/work /mnt #### Mounting network drive
[root@orleans ~]# cd /mnt/
[root@orleans ~]# cp -r rhel6364/ /work/ #### Copying rhel6.1-64 bit os to PXE
server mechine
[root@orleans ~]# vim /etc/exports ####(Add "/work *(rw,sync)"
[root@orleans ~]# exportfs -a ####(reflect changes in NFS Server)
#### Restart NFS services

[root@orleans ~]#/etc/rc.d/init.d/portmap restart
[root@orleans ~]# /etc/rc.d/init.d/nfslock restart
[root@orleans ~]# /etc/rc.d/init.d/nfs restart
#### Check if NFS is running fine
[root@orleans ~]# rpcinfo -p

100024 1 udp 766 status
100024 1 tcp 769 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
Broadcom
- 208 -
100005 1 udp 828 mountd

100005 1 tcp 831 mountd
100005 2 udp 828 mountd
100005 2 tcp 831 mountd
100005 3 udp 828 mountd
C.2.3 TFTP Configuration
[root@orleans ~]# vi /etc/xinted.d/tftp
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server_args = -s /tftpboot/linux-install
per_source = 11
cps = 100 2
flags = IPv4
}
##### Restart TFTP service
[root@orleans ~]# service xinetd restart

Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
[root@orleans ~]# chkconfig tftp on
C.2.4 PXE Configuration
[root@orleans ~]# cd /work/rhel6364/
[root@orleans RHEL6364]# cd images/pxeboot/
[root@orleans pxeboot]# cp -r * /tftpboot/linux-install/

#### Copy vmlinuz and initrd to TFTP root directory
[root@orleans pxeboot]# mkdir -p /root/test1
[root@orleans images]# cd /work/rhel6364/images/
[root@orleans images]# mount -o loop efiboot.img /root/test1 ###### Extract

efiboot.img to get bootx64.efi and BOOTX64.conf files
Broadcom
- 209 -
[root@orleans images]# cd /root/test1
[root@orleans test1]# cd efi/boot/
[root@orleans boot]# cp -r * /tftpboot/linux-install/ ###### Copy bootx64.efi

and BOOTX64.conf to TFTP root directory
#### Editing efidefault to the following content
[root@orleans boot]# cat /tftpboot/linux-install/efideault

default=0
timeout 10
splashimage=(nd)/splash.xpm.gz
title RHEL6364
root (nd)
splashimage /splash.xpm.gz
kernel /vmlinuz keymap=us lang=en_US method=nfs:192.168.1.1:/RHEL6364
ip=dhcp noipv6
initrd /initrd.im
C.2.5 Configuring DHCP
[root@orleans ~]# cat /etc/dhcpd.conf

#
ignore client-updates;
#allow booting;
#allow bootp;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.50 192.168.1.90;
max-lease-time 4800;
# option router 192.168.1.1;
option domain-name "pxe_text";
# option name-server 192.168.1.20;
option time-offset -8;
}
host bglinux45{
next-server 192.168.1.1; #### IP address of PXE server interface connected
back to back to PXE client interface
hardware ethernet 00:00:C9:BB:C7:8F; #### MAC address of PXE client interface
fixed-address 192.168.1.60; #### IP address to be assigned to PXE client
interface
option host-name "linux-test";
filename "bootx64.efi";
}
#### Restart DHCP service
Broadcom
- 210 -
December 30, 2016 Configuring the Lenovo System x HS22 Blade with e-Raptor MEZZ
[root@orleans ~]# service dhcpd restart

NOTE Reboot the system under test and boot from the PXE client interface.
C.3 Configuring the Lenovo System x HS22 Blade with e-Raptor MEZZ
To install and update the driver, follow these steps:

1. Press the F1 key during the system boot and log in to the following System Configuration and Boot Management
dialog.
Figure 158 System Configuration and Boot Management Dialog
2. Select Boot Manager and press Enter. The following Boot Manager dialog (Figure 159) appears.
Broadcom
- 211 -
Figure 159 Boot Manager Dialog
3. Select Boot from File and press Enter. The following File Explorer dialog (Figure 160) appears.
Broadcom
- 212 -
Figure 160 File Explorer Dialog
4. Select the card from which the UEFI NIC boot is to be performed. Press Enter.
A message similar to the following pop up appears.
Figure 161 ELILO Boot Message
The following Language Selection menu (Figure 162) appears.
Broadcom
- 213 -
Figure 162 Language Selection Menu
5. Select a language and click OK. The following Main Menu appears.
Figure 163 Main Menu
6. Select Expert and click OK. The following Expert menu (Figure 164) appears.
Broadcom
- 214 -
Figure 164 Expert Menu
7. Select Kernel Modules (Hardware Drivers) and click OK. The following Kernel Modules (Hardware Drivers) menu
appears.
Figure 165 Kernel Modules (Hardware Drivers) Menu
8. Select Add Driver Update and click OK. The following Driver Update Medium Selection listing (Figure 166)
appears.
Broadcom
- 215 -
Figure 166 Driver Update Medium Selection Listing
9. Select a medium and click OK. The following Driver Update List confirmation dialog box appears.
Figure 167 Driver Update List Dialog Box
10. Click OK. The Expert menu (Figure 164) appears.

11. Click Back. The Main Menu (Figure 163) appears.
12. Select Start Installation and click OK. The following Source Medium Selection menu (Figure 168) appears.
Figure 168 Source Medium Selection Menu
Broadcom
- 216 -
13. Select Network and click OK. The following Network Protocol Selection menu appears.
Figure 169 Network Protocol Selection Menu
14. Select NFS and click OK. The following Network Device Selection listing (Figure 170) appears.
Figure 170 Network Device Selection Listing
15. Select the device and click OK. The DHCP request is sent. A following dialog box prompts you to enter the IP
address of the NFS server.
Broadcom
- 217 -
Figure 171 NFS Server IP Address Dialog Box
16. Enter the IP address and press Enter. A following dialog box prompts you to enter the directory path of the server.
Figure 172 Server Directory Dialog Box
17. Enter the directory path and press Enter. The system displays, information similar to that shown in Figure 173 and
Figure 174.
Figure 173 Starting Script
Broadcom
- 218 -
December 30, 2016 UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2
Figure 174 Driver Update Confirmation
C.4 UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2
This section provides UEFI NIC PXE setup instructions for configuring IPv6 on the SLES11 SP2 operating system.
C.4.1 Setup Information
 PXE server: CISCO UCS C240 with SLES11 SP2 operating system
 PXE client server: DELL R620 Server F6PCP adapter installed
C.4.2 PXE Server Setup
Launch yast2
C.4.2.1 Configure Network Adapter

1. In the Network Devices section, select Network Settings.
2. Select the adapter port you wish the PXE server to use, then click Edit.
3. Select Statically assigned IP Address and enter the following settings:
— IP Address: 192.168.1.1
— Subnet Mask: /24
4. Under the Additional Addresses section, click Add to add an alias.
— Alias Name: ipv6static
— IP Address: fc00:ba49:1625:fb0f::137
— Netmask: /64
5. Click OK.
Broadcom
- 219 -
C.4.2.2 Disable Firewall

1. In the Security and Users section, select Firewall.
2. Select Disable Firewall Automatic Starting.
3. Click Stop Firewall Now.
C.4.2.3 Install Services

1. In the Network Services section, select DHCP Server.
2. Choose to install and accept all defaults.
3. Install NFS server, TFTP server, and FTP server one by one by accepting all defaults.
C.4.3 Configure DHCPD6
Brussels-sles11sp2:~ # vim /etc/dhcpd6.conf
preferred-lifetime 604800;
option dhcp-renewal-time 3600;
option dhcp-rebinding-time 7200;
allow leasequery;
option dhcp6.name-servers fc00:ba49:1625:fb0f::1;
option dhcp6.domain-search "pxetest.org";
option dhcp6.info-refresh-time 21600;
option dhcp6.bootfile-url code 59 = string;
# The subnet where the server is attached
# (i.e., the server has an address in this subnet)
subnet6 fc00:ba49:1625:fb0f::/64 {
option dhcp6.bootfile-url "tftp://[fc00:ba49:1625:fb0f::137]/bootx64.efi";
# Nine addresses available to clients
# (the tenth client should get NoAddrsAvail)
range6 fc00:ba49:1625:fb0f::42:10 fc00:ba49:1625:fb0f::42:99;
# Use the whole /64 prefix for temporary addresses
# (i.e., direct application of RFC 4941)
range6 fc00:ba49:1625:fb0f:: temporary;
}
Edit /etc/sysconfig/dhcpd and verify DHCPD6_INTERFACE is set to the network adapter port on which you
want the DHCP server to listen.
DHCPD6_INTERFACE="ethx"
C.4.4 Configure TFTP
Brussels-sles11sp2:~ # vim /etc/xinetd.d/tftp

# default: off
# description: tftp service is provided primarily for booting or when a \
# router need an upgrade. Most sites run this only on machines acting as
# "boot servers".
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
Broadcom
- 220 -
flags = IPv6 IPv4

user = root
server_args = -s /tftpboot
disable = no
per_source = 11
cps = 100 2
}
C.4.4.1 Configure ELILO Boot Loader

Retrieve ELILO from the installation DVD and create a configuration file:
1. Place the first SUSE Linux Enterprise Server install DVD in the DVD drive of the PXE Server.
2. Open a root terminal.
3. Mount the boot image and copy the contents.
Brussels-sles11sp2:~ # mkdir /tmp/efi-img
Brussels-sles11sp2:~ # mount -o loop /media/<name of
disc>/boot/x86_64/efi /tmp/efi-img
Brussels-sles11sp2:~ # cp /tmp/efi-img/efi/boot/* /tftpboot
C.4.4.2 Create /tftpboot/elilo.conf with the Following Contents

Brussels-sles11sp2:~ # vim /tftpboot/elilo.conf
prompt
timeout=50
delay=100
image=/linux
label=suse
initrd=/initrd
append="install=ftp://[fc00:ba49:1625:fb0f::137]/sles ipv6only=1 sysrq=1 dd
vga=791 manual=1 textmode=0 showopts"
C.4.4.3 Copy Installation Files for FTP Transfer

Brussels-sles11sp2:~ # cd /media/<name of disc>
Brussels-sles11sp2:~ # mkdir /srv/ftp/sles
Brussels-sles11sp2:~ # cp -r * /srv/ftp/sles
C.4.4.4 Configure FTP to Enable Support for IPv6

Brussels-sles11sp2:~ # vim /etc/vsftpd.conf
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
#
dirmessage_enable=YES
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#
nopriv_user=ftpsecure
#
# You may fully customise the login banner string:
#
#ftpd_banner="Welcome to FOOBAR FTP service."
#
Broadcom
- 221 -
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#
#ls_recurse_enable=YES
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#
#deny_email_enable=YES
#
# (default follows)
#
#banned_email_file=/etc/vsftpd.banned_emails
#
# If enabled, all user and group information in
# directory listings will be displayed as "ftp".
#
#hide_ids=YES
# Local FTP user Settings

#
# Uncomment this to allow local users to log in.
#
#local_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#
#local_umask=022
#
# Uncomment to put local users in a chroot() jail in their home directory
# after login.
#
#chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
#
#chroot_list_enable=YES
#
# (default follows)
#
#chroot_list_file=/etc/vsftpd.chroot_list
#
# The maximum data transfer rate permitted, in bytes per second, for
# local authenticated users. The default is 0 (unlimited).
#
#local_max_rate=7200
# Anonymus FTP user Settings
#
# Allow anonymous FTP?
Broadcom
- 222 -
#
anonymous_enable=YES
#
# Anonymous users will only be allowed to download files which are
# world readable.
#
anon_world_readable_only=YES
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#
anon_upload_enable=YES
#
# Default umask for anonymus users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#
#anon_umask=022
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#
anon_mkdir_write_enable=YES
#
# Uncomment this to enable anonymus FTP users to perform other write operations
# like deletion and renaming.
#
anon_other_write_enable=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#
#chown_uploads=YES
#chown_username=whoever
#
# The maximum data transfer rate permitted, in bytes per second, for anonymous
# authenticated users. The default is 0 (unlimited).
#
#anon_max_rate=7200
# Log Settings
#
# Log to the syslog daemon instead of using an logfile.
#
syslog_enable=YES
#
# Uncomment this to log all FTP requests and responses.
#
#log_ftp_protocol=YES
#
# Activate logging of uploads/downloads.
#
#xferlog_enable=YES
#
Broadcom
- 223 -
# You may override where the log file goes if you like. The default is shown
# below.
#
#vsftpd_log_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note: This disables the normal logging unless you enable dual_log_enable below.
#
#xferlog_std_format=YES
#
# You may override where the log file goes if you like. The default is shown
# below.
#
#xferlog_file=/var/log/xferlog
#
# Enable this to have booth logfiles. Standard xferlog and vsftpd's own style log.
#
#dual_log_enable=YES
#
# Uncomment this to enable session status information in the system process
listing.
#
#setproctitle_enable=YES
# Transfer Settings
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
#
connect_from_port_20=YES
#
# You may change the default value for timing out an idle session.
#
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#
#data_connection_timeout=120
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that turning on ascii_download_enable enables malicious remote parties
# to consume your I/O resources, by issuing the command "SIZE /big/file" in
# ASCII mode.
# These ASCII options are split into upload and download because you may wish
# to enable ASCII uploads (to prevent uploaded scripts etc. from breaking),
# without the DoS risk of SIZE and ASCII downloads. ASCII mangling should be
# on the client anyway..
#
Broadcom
- 224 -
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# Set to NO if you want to disallow the PASV method of obtaining a data
# connection.
#
#pasv_enable=NO
# PAM setting. Do NOT change this unless you know what you do!
#
pam_service_name=vsftpd
# Set to ssl_enable=YES if you want to enable SSL
ssl_enable=NO
# Limit passive ports to this range to assis firewalling
pasv_min_port=30000
pasv_max_port=30100
anon_mkdir_write_enable=YES
anon_root=/srv/ftp
anon_upload_enable=YES
chroot_local_user=NO
ftpd_banner=Welcome message
idle_session_timeout=900
local_enable=YES
log_ftp_protocol=YES
max_clients=10
max_per_ip=3
pasv_enable=YES
ssl_sslv2=NO
ssl_sslv3=NO
ssl_tlsv1=YES
write_enable=YES
listen=NO
listen_ipv6=YES
C.4.4.5 Restart the Necessary Services

Service nfsserver restart
Service xinetd restart
Service vsftpd restart
Service dhcpd6 restart
C.4.5 PXE Client Setup
To set up the PXE client:

1. Boot the server and press the F2 key to enter system setup.
2. Select System BIOS Settings > Boot Settings and change the boot mode to UEFI.
4. Press the F2 key to enter system setup.
5. Select System BIOS Settings > Boot Settings > UEFI Boot Settings and set the UEFI PXE boot protocol to IPv6 in
the following dialog.
Broadcom
- 225 -
Figure 175 UEFI Boot Settings Dialog

7. Press the F11 key and enter the UEFI boot manager. The following Boot Manager Main Menu (Figure 176) appears.
Broadcom
- 226 -
Figure 176 Boot Manager Main Menu
8. Select UEFI Boot Menu. The following UEFI Boot Menu (Figure 177) appears.
Broadcom
- 227 -
Figure 177 UEFI Boot Menu
9. Select Boot From File. The following File Explorer dialog appears.
Figure 178 File Explorer Dialog
Broadcom
- 228 -
10. Select the port on the client through which PXE boot must be performed and press Enter. The system displays a
status message and then displays the following Language Selection menu.
Figure 179 Language Selection Menu
11. Select a language and click OK. The following Main Menu appears.
Figure 180 Main Menu
12. Select Expert and click OK. The following Expert menu (Figure 181) appears.
Broadcom
- 229 -
Figure 181 Expert Menu
13. Select Kernel Modules (Hardware Drivers) and click OK. The following Kernel Modules (Hardware Drivers) menu
appears.
Figure 182 Kernel Modules (Hardware Drivers) Menu
14. Select Add Driver Update and click OK. The following Driver Update Medium Selection list (Figure 183) appears.
Broadcom
- 230 -
Figure 183 Driver Update Medium Selection List
15. Select a medium from the list and click OK. The Expert menu (Figure 181) appears.
16. Click Back. The Main Menu (Figure 180) appears.
17. Select Start Installation and click OK. The following Source Medium list appears.
Figure 184 Source Medium List
18. Select Network and click OK. The following Network Protocol list (Figure 185) appears.
Broadcom
- 231 -
Figure 185 Network Protocol List
19. Select FTP and click OK. The following Network Device list appears.
Figure 186 Network Device List
20. Select the device and click OK. The following dialog box prompts you for automatic configuration using DHCP.
Figure 187 Automatic Configuration via DHCP Dialog Box
21. Click Yes. The DHCP6 request is sent. The following dialog box (Figure 188) prompts you to enter the IPv6 address
of the FTP server.
Broadcom
- 232 -
Figure 188 FTP Server IPv6 Address Dialog Box
22. Enter the IPv6 address and press Enter. The following dialog box prompts you to enter the directory path of the
server.
Figure 189 Server Directory Path Dialog Box
23. Enter the server’s directory path and press Enter. A pop up will open if you must enter a username and password
for the FTP server.
24. Select NO for this selection and select NO for using HTTP Proxy. The installation begins and the system displays
the License Agreement page.
25. After you accept the license agreement, all of the operating system packages are downloaded using FTP over
IPv6.
Broadcom
- 233 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix D: Example for Installing and Booting UEFI FCoE
December 30, 2016
Appendix D: Example for Installing and Booting UEFI FCoE

The following steps use the Linux SLES operating system as an example.
1. Boot to UEFI linux from DVD.
2. Select UEFI boot from the BIOS boot manager or boot to shell and execute /efi/boot/elilo.efi from removable
media.
3. Follow normal boot instructions from YaST.
4. During the Installation Settings, select Partitioning, then select Custom partitioning (for experts).
5. In SystemViews, select a hard disk.
6. Select the Partitions tab as shown in the following window.
Figure 190 Partitions Tab
7. Delete any old partitions on the disk.

8. To create a GPT disklabel (UEFI does not support booting from disks with an MS-DOS partition table), click Expert
(above the Accept button).
9. Create a partition table and check GPT (required for UEFI boot).
10. To add an UEFI system partition (VFAT or FAT), click Add.
Broadcom
- 234 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix D: Example for Installing and Booting UEFI FCoE
December 30, 2016
11. Select a custom size (100 to 400MB) depending on what UEFI driver and utilities you want to store on the UEFI
system partition. In general, using 200MB is sufficient if the plug-in card detail for UEFI system partition is
unknown.
12. In the Formatting options dialog box, select Format Partition > File system > FAT.
13. Under Mounting options, select /boot/efi and click Finish. The boot drive now has a GPT disk label that contains a
FAT EFI boot partition.
14. Perform the remainder of the partitioning as with any Linux installation. The remainder of the installation is not
unique to UEFI, for example, add a swap partition and an EXT3 partition for root.
15. After the installation is completed, view the partitions using the parted -l command.
16. When the system boots, SUSE Linux Enterprise Server 11 SP1 now shows in the system Start Options.
Figure 191 UEFI FCoE Start Options
Broadcom
- 235 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix E: Loading and Unloading UEFIBoot from the UEFI Shell
December 30, 2016 Loading UEFIBoot from the UEFI Shell
Appendix E: Loading and Unloading UEFIBoot from the UEFI Shell

This section explains how to load and unload Offbeat from the UEFI shell.
E.1 Loading UEFIBoot from the UEFI Shell
The UEFI boot code is distributed with the firmware in a.UFI file. This file can be downloaded to a NIC, iSCSI, or FCoE
adapter through the HII interface in the NIC UEFI code.
E.2 Unloading UEFIBoot from the UEFI Shell
To unload UEFIBoot:
1. View Emulex driver handle information by typing drivers and pressing Enter at the shell prompt. The system
displays a list of drivers as shown in the following window.
Figure 192 Driver Listing
2. Write down the Emulex NIC, FCoE, or iSCSI driver handles. For the above case, the Emulex NIC driver handle is 122
and the Emulex iSCSI driver handle is 126.
3. To unload the Emulex NIC driver in the previous example, type unload 122 and press Enter.
4. To unload the Emulex iSCSI driver in the previous example, type unload 126 and press Enter.
Broadcom
- 236 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix F: Dell UEFI
December 30, 2016 Accessing the Main Configuration Page
Appendix F: Dell UEFI

The following sections define and describe the fields and configuration settings for Dell adapters using the Dell UEFI
utility.
The Dell UEFI adapter configuration utility is a unified configuration utility that lets you configure all of the available
protocols through a single GUI interface, unlike individual configuration utilities. The iSCSI and FCoE configuration can
be configured using these menus even if those functions are not physically present. The configuration will be applied
after those respective functions are enabled.
F.1 Accessing the Main Configuration Page
From the System Setup > Device Settings page, select the adapter you want to view.
Figure 193 Device Settings Page
The Main Configuration page (Figure 194) for that adapter appears.
F.2 Main Configuration Page
This page displays device information and lets you configure device parameters.
Broadcom
- 237 -
December 30, 2016 Main Configuration Page
Figure 194 Main Configuration Page
Table 14 Main Configuration Page Menu Options
Menu Option Description and Available Settings

Firmware Image Properties View adapter firmware version information. See Section F.2.1, Firmware Image Properties
Page, for more information.
NIC Configuration Configure boot protocol, Wake on LAN, link speed, and VLAN. See Section F.2.2, NIC
Configuration Page, for more information.
iSCSI Configuration Configure general, initiator, and target parameters for iSCSI boot. See Section F.2.3, iSCSI
NOTE This menu appears only when NIC + RDMA mode is disabled.
FCoE Configuration Configure FCoE boot parameters. See Section F.2.4, FCoE Configuration Page, for more
information.
NOTE This setting appears only when NIC + RDMA mode is disabled.
Device Level Configuration View and configure global device level parameters. See Section F.2.5, Device Level
NIC Partitioning Configuration Configure functionality of NIC partitions and view assigned addresses. See Section F.2.6, NIC
Partitioning Configuration Page, for more information.
NOTE This menu appears only when NIC + RDMA mode is disabled.
NIC Mode Always enabled.
NIC + RDMA Mode Configure port usage for both Ethernet and RDMA traffic.
NOTE When this setting is enabled, Par cannot be enabled.
NOTE This setting is at the port level. Therefore, one port can have NIC + RDMA mode
enabled while another port can have it disabled.
Broadcom
- 238 -
Table 14 Main Configuration Page Menu Options (Continued)

Blink LEDs Identify the physical port by blinking the port LED for up to 15 seconds.
Available settings are 0 to 15 seconds (default).
Device Name The name of the adapter.
Chip Type The name and revision of the chip.
PCI Device ID The PCI device ID of the port.
PCI Address The PCI address assigned by the BIOS.
Link Status The network link status reported by the adapter.
F.2.1 Firmware Image Properties Page
The Firmware Image Properties page displays adapter firmware version information.
Figure 195 Firmware Image Properties Page
Table 15 Firmware Image Properties Page Menu Options

Family Firmware Version Firmware version information for the installed adapter.
Controller IPL Version IPL version information for the installed adapter.
Controller BIOS Version BIOS version information for the installed adapter.
EFI Version UEFI driver version information for the installed adapter.
Broadcom
- 239 -
F.2.2 NIC Configuration Page
The NIC Configuration page allows you to configure the boot protocol, Wake on LAN, link speed, and VLAN.
Figure 196 NIC Configuration Page
Broadcom
- 240 -
Table 16 NIC Configuration Page Menu Options

Legacy Boot Protocol Select a non-UEFI network boot protocol.
Available settings may include:
 PXE (default)
 iSCSI
 FCoE
 PXE+iSCSI
 PXE+FCoE
 iSCSI+FCoE
 PXE+iSCSI+FCoE
 None
Wake On LAN Enable or disable Wake On LAN.
Available settings include:
 Enabled (default)
 Disabled
Virtual LAN Mode NOTE This setting is for legacy PXE boot only. For UEFI PXE VLAN
configuration through the system BIOS, refer to the Dell system
documentation.
Enable or disable virtual LAN mode.
 Enabled
 Disabled (default)
Virtual LAN ID NOTE This setting is for legacy PXE boot only. For UEFI PXE VLAN
configuration through the system BIOS, refer to the Dell system
documentation.
Specify the ID for VLAN mode. The VLAN ID valid range is 0 to 4095.
VIrtual LAN Priority Specify the Priority for VLAN mode. The VLAN Priority valid range is 0 to 7.
Physical Link Speed The current maximum port speed on the adapter.
Link Speed Specify the port speed used for the selected protocol.
 Auto Negotiated (default)
 1Gb/s
 10Gb/s
Option ROM Enable or disable legacy boot protocols in the Option ROM.
 Enabled
Hide Setup Prompt Enable or disable the option ROM setup prompt (banner) during POST.
 Enabled
Broadcom
- 241 -
Table 16 NIC Configuration Page Menu Options (Continued)

Boot Retry Count Control the number of retries in case of boot failure.
 No Retry (default)
 1 Retry
 2 Retries
 3 Retries
 4 Retries
 5 Retries
 6 Retries
 Indefinite Retries
Boot Strap Type Control the boot strap method used to boot to the operating system.
 Auto Detect (default)
Banner Message Timeout Control the number of seconds that the Option ROM banner appears
during POST. The valid range is 0 to 14. The default value is 8.
PCI Virtual Functions Advertised The number of PCI VFs to be advertised on this port in non-NPar mode. The
number of VFs advertised on this port must be less than or equal to the
number of VFs supported on this port. This value varies based on the
adapter in use. For dual port Emulex OCe14000-series adapters, the
maximum number of supported VFs per port is 24. For dual port Emulex
OCe14000B-series adapters, the maximum number of supported VFs per
port is 56. For quad-port adapters, the maximum number of supported VFs
per port is 28.
NOTE For Vindicator 2, Vindicator 3, Pavelow 2, Pavelow 3 adapters, the

requirement that both the legacy and the UEFI BIOS functionality be
the same mandates that the Legacy Boot Protocol be set to PXE on the
first port of the adapter when defaults are loaded.
PXE boot is enabled only when loading defaults on the first port due
to the architecture of the UEFI BIOS. The first port will have PXE Boot
enabled and the rest of the ports will be set to disabled.
When defaults are loaded on any port other than the first port, the
Legacy Boot Protocol will be set to None only on that specific port.
When defaults are loaded, the Virtualization mode is set to None
which in turn affects the Legacy Boot Protocol on all the other ports.
Hence on the ports other than the one on which the default is loaded,
the Legacy Boot Protocol will be set to None if a storage protocol was
selected earlier and PXE if PXE alone or PXE in combination with
storage protocol was selected earlier.
F.2.3 iSCSI Configuration Page
The iSCSI Configuration page (Figure 197) lets you configure general, initiator, and target parameters for iSCSI boot.
Broadcom
- 242 -
Figure 197 iSCSI Configuration Page
Table 17 iSCSI Configuration Page Menu Options

iSCSI General Parameters Configure general iSCSI parameters. See Section F.2.3.1, iSCSI General Parameters Page, for
more information.
iSCSI Initiator Parameters Configures iSCSI initiator parameters. See Section F.2.3.2, iSCSI Initiator Parameters Page, for
more information.
iSCSI First Target Parameters Enable connection and configure parameters for the first iSCSI target. See Section F.2.3.3,
iSCSI First Target Parameters Page, for more information.
iSCSI Second Target Parameters Enable connection and configure parameters for the second iSCSI target. See Section F.2.3.4,
iSCSI Second Target Parameters Page, for more information.
iSCSI Secondary Device Parameters Configures the iSCSI secondary boot device parameters. See Section F.2.3.5, iSCSI Secondary
Device Parameters Page, for more information.
iSCSI Target Dynamic Discovery Configures the iSCSI target dynamic discovery parameters. See Section F.2.3.6, iSCSI Target
Parameters Dynamic Discovery Parameters Page, for more information.
F.2.3.1 iSCSI General Parameters Page

The iSCSI General Parameters page (Figure 198) lets you configure the general iSCSI parameters.
Broadcom
- 243 -
Figure 198 iSCSI General Parameters Page
Table 18 iSCSI General Parameters Page Menu Options

TCP/IP Parameters via DHCP Control the source of the initiator IP address: DHCP or static assignment.
 Enabled
NOTE This option is specific to IPv4.
IP Auto-Configuration Control the source of the initiator IP address: DHCP or static assignment.
 Enabled
NOTE This option is specific to IPv6.
iSCSI Parameters via DHCP Enable the acquisition of iSCSI target parameters from DHCP.
 Enabled
CHAP Authentication Enable the ability of the initiator to use CHAP authentication when
connecting to the iSCSI target.
 Enabled
Broadcom
- 244 -
Table 18 iSCSI General Parameters Page Menu Options (Continued)

CHAP Mutual Authentication Setting to enable mutual CHAP authentication between the iSCSI initiator
and target.
To use mutual CHAP authentication, specify an initiator secret on the
Initiator Parameters page and configure that secret on the target.
 Enabled
IP Version Control whether IPv4 or IPv6 network addressing is used for the iSCSI
initiator.
 IPv4
 IPv6
 None (default) – Dual mode
Boot to Target Control whether the iSCSI initiator boots to the specified iSCSI target after
connection.
NOTE This is only applicable to UEFI iSCSI boot.
 Enabled
Virtual LAN Mode Enable or disable iSCSI Virtual LAN mode, which allows a VLAN tag to be
used by iSCSI boot.
 Enabled
Virtual LAN ID Specify the ID (tag) to be used for iSCSI VLAN mode. The valid range for the
VLAN ID is from 0 to 4095.
VIrtual LAN Priority Specify the Priority for VLAN mode. The VLAN Priority valid range is 0 to 7.
F.2.3.2 iSCSI Initiator Parameters Page

The iSCSI Initiator Parameters page lets you configure the iSCSI initiator parameters.
Broadcom
- 245 -
Figure 199 iSCSI Initiator Parameters Page
Table 19 iSCSI Initiator Parameters Page Menu Options

IP Address Specify the iSCSI Initiator IP address. The value should be in either IPv4 or
IPv6 format and can be 2 to 39 characters long.
IPv4 Address Specify the iSCSI Initiator IPv4 address. The value must be in IPv4 format
and can be 7 to 15 characters long.
IPv6 Address Specify the iSCSI Initiator IPv6 address. The value must be in IPv6 format
and can be 2 to 39 characters long.
Subnet Mask Specify the iSCSI Initiator IPv4 subnet mask. The value must be in IPv4
format and can be 7 to 15 characters long.
Subnet Mask Prefix Specify the iSCSI Initiator IPv6 subnet mask. The value must be in IPv6
Default Gateway Specify the iSCSI Initiator default gateway. The value should be in either
IPv4 or IPv6 format and can be 2 to 39 characters long.
IPv4 Default Gateway Specify the iSCSI Initiator IPv4 default gateway. The value must be in IPv4
IPv6 Default Gateway Specify the iSCSI Initiator IPv6 default gateway The value must be in IPv6
iSCSI Name Specify the initiator iSCSI Qualified Name (IQN). The valid range is 0 to 223
characters.
CHAP ID Specify the initiator CHAP ID. The valid range is 0 to 128 characters. If this
can be set on a per target basis, then the first target value must be stored
here.
CHAP Secret Specify the ISCSI Initiator CHAP Secret. The valid range is 0 or 12 to 16
characters. If this can be set on a per target basis, the value for the first
target must be stored here.
Broadcom
- 246 -
F.2.3.3 iSCSI First Target Parameters Page

The iSCSI First Target Parameters page lets you enable a connection for the first iSCSI target and configure parameters.
Figure 200 iSCSI First Target Parameters Page
Table 20 iSCSI First Target Parameters Page Menu Options

Connect Enable connecting to the first iSCSI target.
 Enabled
IP Address Specify the first target IP address. The value should be in either IPv4 or IPv6 format and can
be 2 to 39 characters long.
TCP Port Specify the first target TCP port number. The valid range is 1 to 65535.
Boot LUN Specify the first iSCSI storage target boot LUN. The valid range is 0 to
18446744073709551615.
iSCSI Name Specify the first iSCSI storage target initiator IQN. The valid range is 0 to 223 characters.
CHAP ID Specify the first ISCSI storage target CHAP ID. The valid range is 0 to 128 characters. If only a
single value of the CHAP ID is supported, then it is stored here.
CHAP Secret Specify the first ISCSI storage target CHAP Secret. The valid range is 0 or 12 to 16 characters.
If only a single value of the CHAP Secret is supported, then it is stored here.
IP Version Control whether IPv4 or IPv6 network addressing is used for the first iSCSI target.
 IPv4 (default)
 IPv6
Broadcom
- 247 -
Table 20 iSCSI First Target Parameters Page Menu Options (Continued)

Header Digest Enable the header digest for connecting to the iSCSI target.
 Enabled
The integrity of an iSCSI PDU header segment is protected by CRC32C checksum.
Data Digest Enable the data digest for connecting to the iSCSI target.
 Enabled
ISD Qualifier Initiator session identifier. Value should be in the range of 1 to 65535.
F.2.3.4 iSCSI Second Target Parameters Page

The iSCSI Second Target Parameters page lets you enable a connection for the second iSCSI target and configure
parameters.
Broadcom
- 248 -
Figure 201 iSCSI Second Target Parameters Page
Table 21 iSCSI Second Target Parameters Page Menu Options

Connect Enable connecting to the second iSCSI target.
 Enabled
IP Address Specify the second target IP address. The value should be in either IPv4 or IPv6 format and
can be 2 to 39 characters long.
TCP Port Specify the second target TCP port number. The valid range is 1 to 65535.
Boot LUN Specify the second iSCSI storage target boot LUN. The valid range is 0 to
18446744073709551615.
iSCSI Name Specify the second iSCSI storage target initiator IQN. The valid range is 0 to 223 characters.
CHAP ID Specify the second ISCSI storage target CHAP ID. The valid range is 0 to 128 characters. If
only a single value of the CHAP ID is supported for all targets, then it is stored here.
CHAP Secret Specify the second ISCSI storage target CHAP Secret. The valid range is 0 or 12 to 16
characters. If only a single value of the CHAP Secret is supported, then it is stored here.
IP Version Control whether IPv4 or IPv6 network addressing is used for the second iSCSI target.
 IPv4 (default)
 IPv6
F.2.3.5 iSCSI Secondary Device Parameters Page

The iSCSI Secondary Device Parameters page lets you configure the MAC address for a secondary iSCSI boot adapter.
Broadcom
- 249 -
Figure 202 iSCSI Secondary Device Parameters Page
Table 22 iSCSI Secondary Device Parameters Page Menu Options

Secondary Device MAC Address Configure the MAC address for a secondary iSCSI boot adapter in case of boot failure.
The MAC address can have a maximum of 17 characters with a colon (:) separator between
every two characters.
F.2.3.6 iSCSI Target Dynamic Discovery Parameters Page

The iSCSI Target Dynamic Discovery Parameters page lets you to discover the iSCSI targets.
Broadcom
- 250 -
Figure 203 iSCSI Target Dynamic Discovery Parameters Page
Table 23 iSCSI Target Dynamic Discovery Parameters Page Menu Options

IP Version Control whether IPv4 or IPv6 network addressing is used for the iSCSI target.
 IPv4
 IPv6
IP Address Specify the target IP address. The value should be in either IPv4 or IPv6 format and can be 2
to 39 characters long.
TCP Port Specify the target TCP port number. The valid range is 1 to 65535. The default value is 3260.
Header Digest Enable the header digest for connecting to the iSCSI target.
 Enabled
Data Digest Enable the data digest for connecting to the iSCSI target.
 Enabled
Broadcom
- 251 -
Table 23 iSCSI Target Dynamic Discovery Parameters Page Menu Options (Continued)

Authentication Method Select an authentication method (optional). If you are enabling an authentication method,
you are prompted to enter CHAP configuration.
 None (default)
 CHAP Authentication - Configure target side CHAP details. See Section F.2.3.6.1,
Configuring CHAP Authentication.
 CHAP Mutual Authentication - Configure target and initiator side CHAP details. See
Section F.2.3.6.2, CHAP Mutual Authentication.
Discovered Targets Check the connectivity and discover the listed targets. Click Discovered Targets, the iSCSI
Target Configuration dialog appears. See Section F.2.3.6.3, Configuring Discovered Targets,
for information on Configuring the target.
Ping Target Check the connectivity to the target portal IP defined in the IP Address tab and displays
success or failure messages.
F.2.3.6.1 Configuring CHAP Authentication

In the iSCSI Target Dynamic Discovery Parameters page (Figure 202), if you choose the Authentication
Method as CHAP Authentication. You must configure the target side CHAP details. With CHAP
Authentication, the target authenticates the initiator.
Table 24 CHAP Authentication Options

Target CHAP ID Specify the target CHAP ID. The valid range is 0 to 128 characters.
Target CHAP Secret Specify the target CHAP secret. The valid range is 0 or 12 to 16 characters.
Broadcom
- 252 -
F.2.3.6.2 CHAP Mutual Authentication

In the iSCSI Target Dynamic Discovery Parameters page (Figure 202), if you choose the Authentication
Method as CHAP Mutual Authentication. You must configure the target and initiator side CHAP details.
With CHAP Mutual Authentication, the target authenticates the initiator and the initiator authenticates
the target.
Table 25 CHAP Mutual Authentication Options

Target CHAP ID Specify the target CHAP ID. The valid range is 0 to 128 characters.
Target CHAP Secret Specify the target CHAP secret. The valid range is 0 or 12 to 16 characters.
Use Existing Initiator CHAP Details Enable using existing initiator CHAP details from the configured ISCSI initiator parameters.
 Enabled
Initiator CHAP ID Specify the initiator CHAP ID. The valid range is 0 to 128 characters. This option is available
only if the Use Existing Initiator CHAP Details is disabled.
Initiator CHAP Secret Specify the ISCSI Initiator CHAP Secret. The valid range is 0 or 12 to 16 characters. This option
is available only if the Use Existing Initiator CHAP Details is disabled.
Broadcom
- 253 -
F.2.3.6.3 Configuring Discovered Targets

The iSCSI Target Configuration page lets you select the target for which you want to update the priority.
Figure 206 iSCSI Target Configuration Page
1. Select the target for which you want to update the priority. The following Target Priority Selection Page appears.
Figure 207 Target Priority Selection Page
Broadcom
- 254 -
Table 26 iSCSI Target Dynamic Discovery Parameters Page Menu Options

iSCSI Target Name View the iSCSI Target Name.
IP Version View network addressing used for the iSCSI target.
IP Address View the target IP address.
TCP Port View the target TCP port number.
Boot Target Priority Select the Boot Target Priority.
Available options include:
 None (default)
 First
 Second
The priority chosen is reflected in the respective iSCSI Target Parameters Page.
F.2.4 FCoE Configuration Page
The FCoE Configuration page lets you configure FCoE boot parameters.
Figure 208 FCoE Configuration Page
Broadcom
- 255 -
Table 27 FCoE Configuration Page Menu Options

FCoE General Parameters Configure FCoE general parameters. See Section F.2.4.1, FCoE General Parameters Page, for
more information.
Legacy Only Configuration Settings Configure settings for some adapters. See Section F.2.4.2, Legacy Only Configuration
Settings Page, for more information.
Configure FCoE Targets Configure FCoE targets. See Section F.2.4.3, Configure FCoE Targets Page, for more
information.
World Wide Port Name Target The first FCoE storage target WWPN.
NOTE The Boot Scan Selection option must be set to Specified LUN before you can update
this field.
Boot LUN The first FCoE storage target LUN that will be used by the FCoE initiator as the system boot
device.
NOTE The Boot Scan Selection option must be set to Specified LUN before you can update
this field.
Connect Specify whether the FCoE initiator should connect to the first FCoE storage target defined.
 Enabled
F.2.4.1 FCoE General Parameters Page

The FCoE General Parameters page lets you configure FCoE general parameters.
Figure 209 FCoE General Parameters Page
Broadcom
- 256 -
Table 28 FCoE General Parameters Page Menu Options

Link Up Delay Time Specify how long (in seconds) the FCoE Initiator waits after an Ethernet link is established
before sending any data over the network. The valid range is 0 to 255 seconds.
LUN Busy Retry Count Specify the number of connection retries the FCoE boot initiator attempts if the FCoE target
LUN is busy. The valid range is 0 to 60.
Fabric Discovery Retry Count Specify the retry count for FCoE fabric discovery. The valid range is 0 to 60.
Boot Scan Selection Specify the adapter initiator behavior for booting the system from specified FC boot targets
or fabric discovered targets.
 Disabled (default) – Initiator does not attempt to boot.
 First LUN – Attempt boot from the first bootable LUN of the targets discovered by
adapter.
 First LUN 0 – Attempt boot from the first bootable LUN 0 of the targets discovered by
adapter.
 First LUN Not LUN 0 – Attempt boot from the first bootable LUN that is not LUN 0 of
the targets discovered by adapter.
 Fabric Discovered LUN – Attempt boot based on the LUN assignment provided by the
fabrics management infrastructure.
 Specified LUN – Initiator attempts to boot to the specified World Wide Port Name and
LUN for the first target.
F.2.4.2 Legacy Only Configuration Settings Page

The Legacy Only Configuration Settings page (Figure 210) lets you configure FCoE configuration settings for some
adapters.
Broadcom
- 257 -
Figure 210 Legacy Only Configuration Settings Page
Table 29 Legacy Only Configuration Settings Page Menu Options

Enable or Disable Spinup Delay This option allows you to enable or disable the disk spinup delay. The factory default
If at least one boot device has been defined, and the spinup delay is enabled, the boot BIOS
searches for the first available boot device.
 If a boot device is not ready, the boot BIOS waits for the spinup delay and, for up to
three additional minutes, continues the boot scanning algorithm to find another
multiboot device.
If boot devices have not been defined and auto scan is enabled, then the boot BIOS waits
for five minutes before scanning for devices.
 In an attached fabric, the boot BIOS attempts to boot from the first target found in the
NameServer data.
Enable or Disable EDD 3.0 EDD 3.0 provides additional data to the operating system boot loader during an INT-13h
function 48h call (get device parameters). This information includes the path to the boot
device and the disk size. The default setting for EDD 3.0 is enabled. If EDD 3.0 is disabled,
the setting reverts to EDD 2.1.
Enable or Disable Start Unit You must know the specific LUN to issue the SCSI start unit command. The default setting is
Command disabled.
Broadcom
- 258 -
Table 29 Legacy Only Configuration Settings Page Menu Options (Continued)

Enable or Disable Environment This option sets the boot adapter order if the system supports the environment variable.
Variable The default setting is disabled.
Enable or Disable Auto Boot Sector This option automatically defines the boot sector of the target disk for the migration boot
process, which applies to HP MSA1000 arrays only. If there is no partition on the target, the
default boot sector format is 63 sectors. The default setting is disabled.
Auto Scan Setting This option allows you to enable or disable the auto scan feature. Auto scan is available only
when all eight boot entries are unused (empty). The factory default for auto scan is
disabled. Auto scan allows you to boot from the first boot device found in the FC fabric with
the following options:
 Any first device – The first adapter scans the fabric and the first disk discovered
becomes the attempted boot device
F.2.4.3 Configure FCoE Targets Page

The Configure FCoE Targets page lets you configure the boot attributes.
Figure 211 Configure FCoE Targets Page
Broadcom
- 259 -
Table 30 Configure FCoE Configuration Page Menu Options

Clear All Boot Targets This option allows you to erase the boot list contents when you do not want to reset the
remaining FCoE parameters
Configure Boot Target This option allows you to configure boot targets 1 to 8. When you click on any of the
Configure Boot Target links an immediate FCoE scan of the SAN occurs and the SAN
Discovery Target List page (Figure 212) appears. The FCoE scan occurs only on the first
selection of he Configure Boot Target link. On subsequent selections of the Configure Boot
Target links the WWPN/LUN Target-List data obtained from the scan is stored internally and
re-displayed.
F.2.4.3.1 SAN Discovery Target List Page

The SAN Discovery Target List page lets you select a WWPN/LUN to trigger the dynamic update of the
corresponding FCoEWWPNTarget and FCoEBootTargetLUN xUEFI variable.
Figure 212 SAN Discovery Target List Page
Broadcom
- 260 -
Table 31 SAN Discovery Target List Page Menu Options

Clear this boot target This option allows you to clear the currently selected boot target.
Choose the first item in the list which is ALWAYS a00:00:00:00:00:00:00:00
WWPN and 00 LUN.
WWPN/LUN This option allows you to select the desired target to be used for FCoE boot
configuration for the particular boot target you are configuring. Only one
item from the displayed WWPN/LUN may be selected to trigger the
dynamic update of the corresponding FCoEWWPNTarget and
FCoEBootTargetLUN xUEFI variable.The FCoE boot BIOS driver target
boot-list table location corresponding to the Configure Boot Target
previously chosen will also be updated appropriately.
When you click on any of the WWPN/LUN the available LUNs for the
selected target are displayed in the SAN Discovery LUN List Page
(Figure 213).
Figure 213 SAN Discovery LUN List Page
Broadcom
- 261 -
F.2.5 Device Level Configuration Page
The Device Level Configuration page displays the global device level parameters and lets you configure them.
Figure 214 Device Level Configuration Page
Broadcom
- 262 -
Table 32 Device Level Configuration Page Menu Options

Virtualization Mode Specify the virtualization mode setting of the adapter.
 None (default)
 NPar
 SR-IOV
 NPar+SR-IOV
NOTE In the NPar+SR-IOV mode, SR-IOV is enabled only on the first partition on each port in
NPar and NPar-EP modes. The maximum number of VFs supported on each port is 24 for a
dual-port P1 adapter, 56 for a dual-port P2 adapter and 28 for a quad-port P1 or P2 adapter.
NOTE When the Virtualization mode is set to NPAR+SRIOV, the firmware chooses to apply the
NIC only profile to the adapter. If NParEP mode support is disabled, the first eight functions
of the adapter are by default set to NIC only.
NParEP Mode Enable more than eight partitions on the device. It must not be enabled if the system and
operating system do not support devices with more than eight PCI PFs.
NOTE This menu option is available only when the Virtualization mode is set to NPar.
 Enabled
 Disabled
RDMA Application Profile The RDMA application profile allows you to select the appropriate configuration for your
particular system setup.
NOTE This menu option is available only when the NIC+RoCE personality is selected.
NOTE This menu option is available only when the Virtualization mode is set to None.
The RDMA application profile choices include:
 RoCE-2 – The RoCE-2 profile supports Windows SMB Direct, Linux iSER, NFS-RDMA, and
VM Migration.
Broadcom
- 263 -
F.2.6 NIC Partitioning Configuration Page
The NIC Partitioning Configuration page (Figure 215) displays NIC partition information and lets you configure their
functionality.
Figure 215 NIC Partitioning Configuration Page
Table 33 NIC Partitioning Configuration Page Menu Options

Flow Control Setting Configure the type of flow control used by the adapter.
NOTE Ethernet flow control cannot be changed if priority flow control is enabled on the
switch ports and enabled in the firmware (through the Emulex OneCommand CNA Manager
application).
 TX: Send Pause on RX Overflow
 RX: Throttle TX on Pause Received
 TX / RX Flow Control
Global Bandwidth Allocation Assign TX bandwidth allocation across enabled partitions on the port. See Section F.2.6.1,
Global Bandwidth Allocation Page, for more information.
Partition n View the current partition state. One listing for each partition appears with n representing
the number of the partition.
Partition n Configuration View the partition configuration. One listing for each partition appears with n representing
the number of the partition.
See Section F.2.6.2, Partition Configuration Page, for more information.
Broadcom
- 264 -
F.2.6.1 Global Bandwidth Allocation Page

The Global Bandwidth Allocation page (Figure 216) lets you configure the TX bandwidth allocation across enabled
partitions on the port.
Figure 216 Global Bandwidth Allocation Page
Table 34 Global Bandwidth Allocation Page Menu Options

Partition n Minimum TX Bandwidth The minimum transmit bandwidth value is the least amount of bandwidth that the partition
can provide. It is represented as a percentage. One listing for each partition appears with “n”
representing the number of the partition. The valid range is 0 to 100 percent for each
enabled partition.
The minimum transmit bandwidth value must be less than or equal to the maximum
transmit bandwidth value. The total of the minimum transmit bandwidth values for all
enabled functions on that port must be equal to 100.
NOTE A minimum transmit bandwidth value of 0 is a valid value. If all of the partitions’
minimum transmit bandwidth values are zero, the bandwidth is distributed equally among
the current active partitions.
Partition n Maximum TX Bandwidth The maximum transmit bandwidth value is the greatest amount of bandwidth that the
function can provide. It is represented as a percentage. One listing for each partition
appears with “n” representing the number of the partition.
The valid range is 0 to 100 percent for each enabled partition.
F.2.6.2 Partition Configuration Page

The Partition Configuration page (Figure 217) and (Figure 218) display information for a particular partition and lets
you configure some partition parameters. A separate page for each available partition appears.
Only one storage function on each port is allowed. After a storage function is enabled on a partition, the storage
protocols appear as unavailable on the other partitions.
Broadcom
- 265 -
Figure 217 Partition 1 Configuration Page
Table 35 Partition 1 Configuration Page Menu Options

NIC Mode Enable or disable the NIC personality on the partition.
 Enabled
 Disabled
The default setting is Enabled on all partitions.
NOTE The NIC mode setting cannot be changed on Partition 1 of each port.
PCI Device ID The PCI device ID for the partition.
PCI Address The PCI address for the partition. This value is assigned by the system BIOS.
MAC Address The permanent MAC address assigned at the factory.
Virtual MAC Address A programmatically assignable MAC address for the partition.
PCI Virtual Functions Advertised The number of PCI VFs to be advertised on this partition. The number of VFs advertised on
this port must be less than or equal to the number of VFs supported on this port. This value
varies based on the adapter in use. For dual port Emulex OCe14000-series adapters, the
maximum number of supported VFs per port is 24. For dual port Emulex OCe14000B-series
adapters, the maximum number of supported VFs per port is 56. For quad-port adapters, the
maximum number of supported VFs per port is 28.
Broadcom
- 266 -
Figure 218 Partition 2 Configuration Page
Table 36 Partition 2 Configuration Page Menu Options

NIC Mode Enable or disable the NIC personality on the partition.
 Enabled
 Disabled
The default setting is Enabled on all partitions.
NOTE The NIC mode setting cannot be changed on Partition 1 of each port.
iSCSI Offload Mode Enable or disable the iSCSI offload personality on the partition.
 Enabled
FCoE Mode Enable or disable the FCoE personality on the partition.
 Enabled
PCI Device ID The PCI device ID for the partition.
PCI Address The PCI address for the partition. This value is assigned by the system BIOS.
MAC Address The permanent MAC address assigned at the factory.
iSCSI Offload MAC Address The permanent MAC address for iSCSI offload assigned at the factory.
FIP MAC Address The permanent FIP-MAC address for FCoE assigned at the factory.
Virtual MAC Address A programmatically assignable MAC address for the partition.
Broadcom
- 267 -
December 30, 2016 Secure Firmware Download
Table 36 Partition 2 Configuration Page Menu Options (Continued)

Virtual iSCSI Offload MAC Address Configure the MAC address for iSCSI offload.
The setting can have a maximum of 17 characters with a colon (:) separator between every
two characters.
Virtual FIP MAC Address A programmatically assignable FIP-MAC address for the partition FCoE.
World Wide Node Name The FC World Wide Node Name ID for FCoE. A maximum of 23 characters is supported. A
colon separator (:) must be used between every two characters.
Virtual World Wide Node Name Specify the FC World Wide Node Name ID for FCoE. A maximum of 23 characters is
supported. A colon separator (:) must be used between every two characters.
World Wide Port Name The FC World Wide Port Name ID for FCoE. A maximum of 23 characters is supported. A
colon separator (:) must be used between every two characters.
Virtual World Wide Port Name Specify the FC World Wide Port Name ID for FCoE. A maximum of 23 characters is supported.
A colon separator (:) must be used between every two characters.
F.3 Secure Firmware Download
A single firmware image contains the latest version of the firmware and boot code.
The firmware and UEFI NIC, iSCSI, and FCoE drivers are contained in one image file with the .UFI extension.
If a jumper is plugged into the ASIC GPIO pin on the adapter, it indicates that only secure firmware versions are
allowed to be flashed on the adapter. Upgrade from earlier unsecure firmware versions does not involve a digital
signature check since the earlier code does not support this feature. Therefore, upgrade to secure firmware versions
will be successful. If a secure version of the firmware (version 11.0 or later) is installed on an Emulex OCe14000B-series
adapter and you want to update to an earlier unsecure version of firmware, you must remove the secure firmware
jumper block before performing the update. See the adapter installation guide for more information. Firmware
upgrade from a secure firmware version to an unsecure firmware version results in an error when the jumper is in
place. If this happens, an error message indicating digital signature failure appears.
Broadcom
- 268 -
Boot for NIC, iSCSI, and FCoE Protocols User Guide Appendix G: Configuring PXE Boot for NIC on Dell OCe14000-Based Systems
December 30, 2016 Running the PXESelect Utility
Appendix G: Configuring PXE Boot for NIC on Dell OCe14000-Based

Systems
This section describes how to use the PXESelect utility to set up a PXE bootable network by configuring a Dell
OCe14000-based adapter.
NOTE For Dell adapter models D6T93, F6PCP, JJPC0, and P3V42, PXE boot can
be performed only on the first NIC partition on each port in the legacy
x86 BIOS.
For more information on the PXE protocol, the PXE Boot process, and remotely installing with PXE on different
operating systems, see Chapter 3, Configuring PXE Boot for NIC on OCe14000-Series Adapters.
G.1 Running the PXESelect Utility
To run the PXESelect utility, start or restart the computer. When prompted, press Ctrl-P keys. If you are running the

NOTE A UEFI-capable system typically does not show the prompt for running
the PXESelect utility unless it is configured for legacy booting. See
your system configuration manual for information on performing a
legacy boot. All configuration that can be performed in the PXESelect
utility can instead be performed in the UEFI configuration utility. See
Appendix F, Dell UEFI for more information.
G.2 Navigating the PXESelect Utility

 Press the up or down arrows on the keyboard to move through and select menu options or configuration fields. If
multiple adapters are listed, use the up and down arrows to scroll to the additional adapters.
 Press the left or right arrows on the keyboard to move through and select setting options.
 Press Enter to accept a selection, select a menu option, or to change a configuration default.
 Press the F7 key to save the changes on the screen.
Broadcom
- 269 -
December 30, 2016 Setting Up a PXE Bootable Network
G.3 Setting Up a PXE Bootable Network
To configure adapters for PXE boot:
1. From the following Controller List (Figure 219), use the up or down arrow keys to select the adapter you want to
configure and press Enter.
Figure 219 Controller List
NOTE The system displays the Controller List only if there are two or more
adapters connected.
The following Controller Configuration dialog appears.
Depending on the adapter, one or more of the following items are displayed:
— Controller Model – Displays the adapter’s model number.
— Firmware Version – Displays the current firmware version.
— IPL Version – Displays the IPL version.
— Virtualization Mode – Select one of the following options:
 NPar – If NPar is enabled, you can access up to eight virtual network interfaces (all partitions are set to
NIC by default). For more information on NPar support, see Section G.3.1, Configuring NPar.
 SRIOV – If the system BIOS supports SR-IOV, you can enable it. For more information on SR-IOV
configuration, refer to the appropriate Emulex driver’s user guide.
 NPar+SRIOV – SRIOV can be enabled over NPar supported adapters.
 None – If there is no virtualization mode selected, there is only one NIC function on each port and there
are no storage functions.
NOTE If the virtualization mode has changed since the last boot, a reboot will
— NParEP Support – If NParEP support is enabled, each port can be partitioned into isolated PFs (channels) up
to total of 16 functions. See Section G.3.2.2, Enabling NParEP Support, for more information.
Broadcom
- 270 -
NOTE NParEP support is only available on Dell 13G or newer systems.

— RDMA Application Profile – This setting allows you to select the appropriate configuration for the particular
system setup.
The RDMA application profile choices include:
 RoCE-1 – Not supported.
 RoCE-2 – The RoCE-2 profile supports Windows SMB Direct, Linux iSER, NFS-RDMA, and VM Migration.
2. After you set the options in the Controller Configuration dialog (Figure 220), press the F7 key to save the current
settings.
NOTE If you want to erase the current configuration, press the F8 key. See
Section G.3.3.10, Erasing Ports and Adapter Configurations, for more
information.
The following Port Selection Menu appears.
NOTE The Port Selection Menu appears only if there are two or more ports
connected.
4. Select the port you want to configure and press Enter. The following Port Menu appears.
Figure 222 Port Menu
5. From the Port Menu, you can select one of the following options:
— NPar Configuration – See Section G.3.1, Configuring NPar, for more information.
— Boot Configuration – See Section G.3.3, Configuring Boot Options, for more information.
— Port Configuration – See Section 21.3.1, Configuring Port Options, for more information.
Select the desired configuration option and press Enter.
Broadcom
- 271 -
G.3.1 Configuring NPar
NPar support provides the ability to configure multiple physical functions or I/O partitions for each physical adapter
port.
NOTE The settings in this menu can be configured only if the virtualization
mode is set to NPar. Otherwise, the settings in this menu are for
viewing purposes only.
If NPar support is enabled, you must configure the NPar settings
(minimum and maximum bandwidths) for iSCSI and FCoE storage
functions in the NIC BIOS before they can be configured further from
their respective utilities (iSCSI or FCoE BIOS). Otherwise, the Logical
Link for that function will still show as down, and you will not be able
to log in to targets or find LUNs behind those targets.
To configure NPar:
1. From Port Menu (Figure 222), select NPar Configuration and press Enter. The following Partition List appears.
Figure 223 Partition(s) List
2. Select the partition you want to configure and press Enter. The following Configure Partition dialog appears.
Figure 224 Configure Partition Dialog
3. From the Configure Partition dialog, you can perform the following tasks:
— Select the protocol for each function, except for PF #0 and PF #1.
— Configure the minimum and maximum bandwidth for each channel
G.3.2 Selecting the Protocol
This option specifies a list of available protocols that can be configured on an adapter. Depending on the protocols for
which the adapter is licensed, one or more of the following selections is available:
Broadcom
- 272 -
 iSCSI or FCoE – These protocols are enabled on one function per adapter port and include NIC functionality on
the other enabled functions

Two iSCSI functions and two FCoE functions are not allowed on a
single port.
 RoCE – The RoCE personality implies that all the enabled functions provide RoCE functionality.
NOTE The RoCE personality setting is available only when the Virtualization
mode is set to None and the RDMA application profile is set to RoCE-2.
 None – Allows you to disable that particular function (0 to 7).
To select the protocol:
1. From the Configure Partition dialog (Figure 224), use the left or right arrow keys to select the desired protocol.
— NIC
— iSCSI
— FCoE
— RoCE
— None
NOTE If the protocol selection has changed since the last boot, a reboot will
G.3.2.1 Configuring Minimum and Maximum Bandwidth

1. On the Configure Partition dialog (Figure 224), use the use the up or down arrow keys to select Min BW or Max
BW.
2. Use the left or right arrow keys to select the desired bandwidth value.
100.

equally among the current active partitions.
— The Maximum Bandwidth is the greatest amount of bandwidth the function can provide. It is represented as
a percentage.
G.3.2.2 Enabling NParEP Support
NOTE NParEP support is available only on Dell 13G or newer systems.

NParEP support provides the ability to configure additional PCI functions or I/O partitions for each physical adapter
port if NPar is enabled.
Broadcom
- 273 -
You can configure up to 16 functions on a one-port Emulex OCe14400-series adapter, up to 8 functions per port on a
one or two-port Emulex OCe14100-series adapter, and up to 4 functions per port on a four-port Emulex
OCe14100-series adapter.
support for NParEP.
 The Dell system hardware (the motherboard and BIOS) must support NParEP.
 The host operating system must support NParEP:
 The application management tools, including the Emulex OneCommand CNA Manager application, must support
NParEP.
 NParEP must be enabled in the firmware using the Emulex OneCommand CNA Manager application.
To enable NParEP:
1. From Controller Configuration dialog (Figure 220), select NParEP Support.
2. Select Enabled and press the F7 key to save.
If NParEP is enabled, the system displays additional functions on the following Partition List.
Figure 225 Partition(s) List (NParEP Enabled)
See Section G.3.1, Configuring NPar, for more information on configuring the additional functions.
G.3.3 Configuring Boot Options
To view the Boot Configuration dialog:

1. From the Port Menu (Figure 222), select Boot Configuration and press Enter. The following Boot Configuration
dialog appears.
Broadcom
- 274 -
Figure 226 Boot Configuration Dialog
From the Boot Configuration dialog, you can perform the following tasks:
— Configure PXE boot support – See Section G.3.3.1, Configuring PXE Boot Support, for instructions.
— Configure the Hide Setup prompt – See Section G.3.3.2, Configuring the Hide Setup Prompt, for instructions.
— Configure the banner message timeout – See Section G.3.3.3, Configuring the Banner Message Timeout, for
instructions.
— Configure the boot retry count – See Section G.3.3.4, Configuring the Boot Retry Count, for instructions.
G.3.3.1 Configuring PXE Boot Support

1. On the Boot Configuration dialog (Figure 226), use the left or right arrow keys to enable or disable the PXE Boot
setting.
G.3.3.2 Configuring the Hide Setup Prompt

This setting enables or disables the CTRL<P> setup prompt (banner) during POST.
To configure the Hide Setup prompt:
1. On the Boot Configuration dialog (Figure 226), use the left or right arrow keys to enable or disable the Hide Setup
Prompt setting.
G.3.3.3 Configuring the Banner Message Timeout

This setting controls the number of seconds that the PXE banner message appears during POST. The valid range is 0 to
14.
To configure the banner message timeout:
1. On the Boot Configuration dialog (Figure 226), use the left or right arrow keys to select the desired amount of
time (in seconds) for the Banner Message Timeout setting.
G.3.3.4 Configuring the Boot Retry Count

This setting specifies the number of boot retry attempts before control is returned to the system BIOS. Valid values
include:
 0 (no retry)
 1 to 6
 7 (indefinite retries)
Broadcom
- 275 -
To configure the boot retry count:

1. On the Boot Configuration dialog (Figure 226), use the left or right arrow keys to select the desired number of
retries for the Boot Retry Count setting.
21.3.1 Configuring Port Options
To view the Port Configuration dialog:

1. From the Port Menu dialog (Figure 222), select Port Configuration and press Enter. The following Port
2. From the Port Configuration dialog, you can perform the following tasks:
— Set the configured port speed – See Section G.3.3.5, Setting the Configured Port Speed, for instructions.
— View the physical link speed and link status.
— Configure WoL – See Section G.3.3.6, Configuring Wake on LAN, for instructions.
— Configure PXE VLAN, including the PXE VLAN ID and priority – see Section G.3.3.7, Configuring the PXE VLAN
ID and Priority, for instructions.
— Configure flow control – See Section G.3.3.8, Configuring Flow Control, for instructions.
NOTE Flow Control is only available when the Virtualization mode is set to
NPar.
— Identify the port – See Section G.3.3.9, Physically Identifying the Port, for instructions.
G.3.3.5 Setting the Configured Port Speed

To set the port speed:
1. On the Port Configuration dialog (Figure 227), use the left or right arrow keys to select Auto Negotiated, 10G, or
1G for the Configured Port Speed setting.
Broadcom
- 276 -
G.3.3.6 Configuring Wake on LAN

Wake on LAN configuration is dependent on the system BIOS and operating system settings. The following table
describes the different configurations.
Table 37 Wake on LAN Settings and Results
BIOS WoL Operating System WoL Results

Enabled Enabled Since the BIOS and operating system have the same setting,
after the operating system reboots, WoL is enabled.
Enabled Disabled After the operating system reboots, the driver disables
WoL.
Enabled Enabled, but changed to After the operating system reboots, WoL is set to Disabled,
Disabled after reboot so WoL is disabled.
Disabled Enabled After the operating system reboots, the driver does not
change WoL, so WoL is disabled.
Disabled Disabled Since the BIOS and operating system have the same setting,
after the operating system reboots, WoL is disabled.
NOTE For situations 2 to 5, in order to re-enable WoL, you must enable WoL in the operating system, reboot the
system, and then enable WoL in the system BIOS.
To configure Wake on LAN:

1. From the Port Configuration dialog (Figure 227), use the left or right arrow keys to enable or disable the Wake on
LAN setting.
G.3.3.7 Configuring the PXE VLAN ID and Priority

To configure a PXE VLAN ID and set the priority level:
1. On the Port Configuration dialog (Figure 227), use the left or right arrow keys to enable the PXE LAN setting.
2. For the PXE VLAN ID, use the left or right arrow keys to enter a number from 1 to 4094.
3. For the PXE VLAN Priority level, use the left or right arrow keys to enter a number from 0 to 7.
0 to 7, with 0 the highest priority level.
After you exit the PXESelect utility, the system will reboot for the configuration to take effect.
G.3.3.8 Configuring Flow Control

This setting allows you to configure the type of flow control used by the adapter.
NOTE Flow Control is only available when the Virtualization mode is set to
NPar.
Ethernet flow control cannot be changed if priority flow control is
enabled on the switch ports and enabled in the firmware (through
the Emulex OneCommand CNA Manager application).
To configure flow control:
1. From the Port Configuration dialog (Figure 227), use the left or right arrow keys to select one of the following
settings for the Flow Control setting.
— TX & RX
— TX (Send Pause on RX Overflow)
Broadcom
- 277 -
— RX (Throttle TX on Pause Received)

— Disabled
G.3.3.9 Physically Identifying the Port

1. On the Port Configuration dialog (Figure 227), press the F5 key.
2. The LEDs on the adapter begin blinking. The selected port LED status indicators blink on the adapter for
approximately 15 seconds.
NOTE Not all adapters have LEDs that are visible externally. If you are using
an add-in card in a blade server environment, the port identification or
beaconing capability does not work.
G.3.3.10 Erasing Ports and Adapter Configurations
NOTE If this setting is selected, all previous configuration settings are

returned to their factory default settings including the current
protocol selection. You must perform this action to provide a clean
1. On the Controller Configuration dialog (Figure 220), press the F8 key to restore the factory default settings. A
warning appears asking if you want to erase the current configuration for all ports of the adapter.
2. Press Y to delete the configuration. You will receive another warning asking you to confirm the permanent
1. Follow the instructions on the bottom of the individual menus until you are prompted to exit.
2. Press Y to exit. Depending on what settings were changed, a reboot may be necessary.

supported, the PXESelect utility automatically reboots even if no
changes were made to the system.
G.4 PXE Boot Parameters Default Values

Hide Setup Prompt Disabled Enabled
Disabled
Banner Message Timeout 8 0–14
Port Speed Auto Negotiated Auto Negotiated
10G
1G
Broadcom
- 278 -

PXE Boot Disabled Enabled
NOTE On some Dell LOMs, this setting is Disabled
enabled by default on port 1.
Boot Retry Count 0 0 (no retry)
1–7 Retries
Wake on LAN Enabled Enabled
Disabled
Flow Control TX & RX TX & RX
TX
RX
Disabled
PXE VLAN Disabled Enabled
Disabled
PXE VLAN ID 0 1–4094
PXE VLAN Priority 0 0–7
Virtualization Mode None NPar
SRIOV
None
NParEP Support Disabled Enabled
Disabled
Protocol NIC NIC
FCoE
iSCSI
RoCE
None
Min BW 25% The total bandwidth is distributed evenly across all the
enabled partitions.
Max BW 100% From the minimum bandwidth value up to 100%
(inclusive).
Broadcom
- 279 -

Emulex Boot For NIC, iSCSI, and FCoE Protocols User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Emulex Boot For NIC, iSCSI, and FCoE Protocols User Guide

Uploaded by

Copyright:

Available Formats

Emulex® Boot for NIC, iSCSI, and FCoE Protocols

Corporate Headquarters Website

Chapter 2: Configuring the PXE Boot for NIC on OCe11100-Series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3: Configuring PXE Boot for NIC on OCe14000-Series Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4: Configuring Boot from SAN for the FCoE Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5: Configuring x86/x64 Platforms for the iSCSI Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.3.2 Booting from SAN for iSCSI MPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 7: Updating and Enabling Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 8: Configuring iSCSI Boot Support with the iSCSISelect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 11: Configuring UEFI for Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

11.2 Starting the Emulex NIC Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 12: Configuring UEFI for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Chapter 13: Configuring UEFI for FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

13.10.3 Changing Boot Target Scan Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Chapter 14: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Appendix C: Examples for Configuring and Booting UEFI NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Appendix D: Example for Installing and Booting UEFI FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Appendix F: Dell UEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

F.2.2 NIC Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

NOTE Emulex drivers support multipath boot configurations. See your

ACL Access Control List

LPVID logical port VLAN ID

VMQ virtual machine queue

Chapter 2: Configuring the PXE Boot for NIC on OCe11100-Series

2.2 PXE Boot Process

NOTE To enable or disable the PXE boot, it must be enabled or disabled in

Figure 1 PXE Boot Process

2.4 Using the PXESelect Utility

2.4.1 Navigating the PXESelect Utility

Use the following methods to navigate the PXESelect utility:

2.4.2 Running the PXESelect Utility

OCe14102B-UM NIC#0 Port#1 Base 0x00000380001A0000 @ Bus:1B Dev:00 Fun:00

2.4.3 Setting Up a PXE Bootable Network

Figure 2 Controller Selection Menu

Figure 3 Controller Configuration Dialog

Depending on the adapter, the following options are available:

Figure 4 Port Selection Menu

2.4.4 Configuring Ports If UMC Is Disabled or Not Supported

NOTE If UMC is enabled, for information on configuring UMC, see

Figure 5 Port Configuration Dialog

NOTE Logical Link Status appears as N/A for storage functions.

2.4.4.1 Configuring the PXE Boot Support

2.4.4.2 Configuring SR-IOV

2.4.4.3 Configuring the PXE VLAN ID and Priority

Figure 6 Configure PXE VLAN ID/Priority Menu

2.4.4.4 Physically Identifying the Port

Figure 7 Port Identification Pop Up

2.4.4.5 Erasing Ports and Adapter Configurations

NOTE On OCe11100-series adapters, if you select the Erasing Ports and

3. Press Y to delete the configuration.

NOTE For older systems, depending on the memory allocation method

2.4.5 Configuring Universal Multichannel

NOTE The PXE VLAN is not supported in UMC environments.

Figure 8 Multichannel Configuration Dialog

2.4.5.1 Configuring Minimum and Maximum Bandwidth

NOTE A Minimum Bandwidth value of 0 is a valid value. If all of the partitions’

3. Select Save and press Enter.

2.4.5.2 Configuring LPVID

NOTE The PXE VLAN is not supported in UMC environments.

2.4.6 Configuring Multichannel for Lenovo System x Adapters

NOTE This section pertains to Emulex OneConnect adapters that support

Figure 9 Controller Configuration Dialog - Lenovo System x Adapters

2. Select one of the following settings and press Enter: