Broadcom Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide

Broadcom Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide

Emulex® Elxflash and LpCfg Utilities for LightPulse® Adapters User Guide

Version 11.4

September 6, 2017 FlashUTIL-LPE-UG114-100

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Corporate Headquarters San Jose, CA Website www.broadcom.com

Broadcom, the pulse logo, Connecting everything, Avago Technologies, Avago, the A logo, Emulex, LightPulse, and OneCommand 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.

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

Table of Contents

Table of Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1 Elxflash Offline Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2 Elxflash Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Platform Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1.1 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2 Installing the Elxflash Offline Kit for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.1 Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2.2 Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3 Installing the Elxflash Offline Kit for Windows PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3.1 Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3.2 Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.4 Extracting the Driver Files from the Elxflash Offline Kit for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.5 Extracting the Elxflash Stand-alone Kit for Linux, Windows, and VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3: Elxflash Utility Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Using the fwmatrix.txt File Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2 Using Auto-Discovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.3 Auto-Discovery (/auto) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.4 Downgrade (/downgrade or /g) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.5 Force Firmware and Boot Code (/f) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.6 Force Boot Code (/fb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.7 Force Firmware (/ff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.8 Firmware Matrix Directory Change (/fmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.9 Help (/h or /?) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.10 Image Directory Change (/id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.11 Image Version Display (/iv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.12 Log (/log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.13 Preview (/p) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.14 Process FC HBAs Only (/fc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.15 Process UCNAs (/ucna) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.16 Query (/q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.17 Ramdrive (/ramdrive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.18 Rewrite (/rewrite or /e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.19 Silent (/s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.20 Discover CFAs Using SysFS (/sysfs) (LPe16202/OCe15100 Adapters Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.21 Update (/update) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.22 Verbose (/v) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.23 VPD (/vpd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.24 XML Output (/xml) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4: LpCfg Utility Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.1 Running the LpCfg Utility from the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.2 Running the LpCfg Utility Included with the Elxflash Stand-alone Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.2.1 Linux and VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.2.2 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.3 Supported Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.3.1 Help Command and General Adapter Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.3.1.1 Viewing the Syntax for Commands (help) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.3.1.2 Resetting an Adapter (reset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Broadcom - 3 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Table of Contents

4.3.1.3 Resetting an Adapter to the Factory Defaults (factorydefaults) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.3.1.4 Running a Power-on Self-Test (posttest) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.3.2 Viewing Adapter Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.3.2.1 Viewing Emulex Conventional Names Instead of VPD (/c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.3.2.2 Viewing the LpCfg Utility Version Information (version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2.3 Viewing VPD (vpd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2.4 Viewing Boot Device Information (readbootdevice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2.5 Viewing Boot Code Versions (listboot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2.6 Viewing Adapter Attributes (hbaattr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2.7 Viewing All Adapters in the System (listhba) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.3.2.8 Viewing the WWN of All Adapters in the System (listwwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3.2.9 Viewing the MAC Address (listmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3.2.10 Reading the MAC Address (readmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3.2.11 Viewing Firmware Program Revisions (listrev) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3.2.12 Viewing Selected Configuration Regions (readconfig) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.3.3 Firmware and Boot Code Download Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.3.3.1 Downloading a File (download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.3.3.2 Accessing the Flash Device Directly (directdownload) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.3.4 World Wide Name Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 4.3.4.1 Writing WWN and Updating NVPARMS (writewwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.3.4.2 Saving WWN Data to a File (savewwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.3.4.3 Restoring WWN and Updating NVPARMS (restorewwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.3.4.4 Restoring NVPARMS (restorenvwwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.3.4.5 Restoring the IEEE Address (restoredefwwn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.3.5 Boot Code Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.3.5.1 Enabling or Disabling Boot Code (enableboot or disableboot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.3.5.2 Selecting a Boot Device (setbootdevice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.5.3 Enabling or Disabling Boot Devices (enablebootdevice or disablebootdevice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.3.5.4 Read All Alternative Boot Devices (readaltboot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.3.5.5 Setting One or More Alternate Boot Devices (setaltboot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.3.5.6 Enable or Disable PXE Boot on NIC Devices (networkboot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.3.6 Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.3.6.1 Updating Configuration Regions (config) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.3.6.1.1 Update by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.3.6.1.2 Update by Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.3.6.2 Writing a Semi-Volatile MAC Address on a NIC Device (writesvmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.3.6.3 Restoring the Default Semi-Volatile MAC Address on a NIC Device (restoredefsvmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.3.7 Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.3.7.1 Running the External Loopback Test (extloopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.3.7.2 Running the Internal Loopback Test (intloopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.3.7.3 Running the PCI Loopback Test (pciloopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 4.3.8 Using Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.3.8.1 Repeating a Series of Commands (repeat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.3.8.2 Enabling or Disabling Test Messages on the Screen (screendisplay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.3.8.3 Updating Nonvolatile WWNN (scriptwwnn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.3.8.4 Updating Nonvolatile WWPN (scriptwwpn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.3.8.5 Updating Volatile WWNN (scriptvwwnn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.3.8.6 Updating Volatile WWPN (scriptvwwpn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.3.8.7 Creating a Log (logfile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.3.9 VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.3.9.1 Reading VLAN Priorities (readvlanprops) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.3.9.2 Restoring the Default Values for the VLAN ID and VLAN Priorities (restorevlanprops) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 4.3.9.3 Changing the VLAN ID and VLAN Priority on a Specified Adapter’s NIC Function (writevlanprops) . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5: Status Messages and Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.1 Elxflash Utility Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.2 LpCfg Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Broadcom - 4 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Table of Contents

Chapter 6: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6.1 Unsupported Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 6.2 Updating Adapters without Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Broadcom - 5 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 1: Introduction Elxflash Offline Kit

Chapter 1: Introduction

This document explains how to use the Emulex® Elxflash and LpCfg adapter management utility kits for Linux, Windows, and VMware pre-boot environments.

1.1

1.2

Elxflash Offline Kit

The Elxflash Offline kit allows you to configure Emulex adapters before you install or boot a server operating system. You can also use the Elxflash Stand-alone kit, which lets you update firmware on Emulex adapters without installing

any tools. See Section 4.2, Running the LpCfg Utility Included with the Elxflash Stand-alone Kit

, for more information.

The Elxflash Offline kit includes:   linlpcfg and elxflash for Linux winlpcfg and elxflash for Windows The linlpcfg and the winlpcfg are management utilities for adapter configuration and diagnostics for Linux and Windows, respectively. The LpCfg utility can also download firmware, but you must manually select the adapters to be updated.

Elxflash is a firmware download utility. When the /auto switch is used, Elxflash automatically chooses the best image to download. When the fwmatrix.txt

file is used, you choose the images to apply to the adapters.

NOTE

The Offline utility must be installed on your system before you can run it. While the stand-alone utility does not need to be installed before it is run, you must go to the directory into which the stand-alone utility was extracted and run it from the command prompt.

See

Chapter 4 , LpCfg Utility Command Line Interface , for further information about the offline utility.

Elxflash Utility

The Elxflash utility uses a command line interface allowing you to build scripts for automated and unattended firmware and boot code download solutions for Emulex LightPulse ® Fibre Channel (FC) host bus adapters (HBAs), and Fibre Channel over Ethernet/network interface card (NIC+FCoE) in production systems. You can also download firmware and boot code on local and remote machines simultaneously.

The Elxflash Stand-alone kit, which allows you to update firmware on Emulex adapters without any tools, is also

available. See Section 4.2, Running the LpCfg Utility Included with the Elxflash Stand-alone Kit

, for more information.

The Elxflash utility uses auto-discovery ( /auto ), so you do not need to maintain the fwmatrix.txt

configuration file. When auto-discovery is invoked, the utility automatically discovers local adapters and performs selected operations, such as: /ff (force firmware), /fb (force boot), /update , /downgrade , and /rewrite .

When using auto-discovery, you must populate the firmware and boot subdirectories with image files for specific adapter models. Auto-discovery uses Emulex-defined firmware and boot code file names in their respective directories.

If you do not want to use auto-discovery, the Elxflash utility can update the firmware or boot code of an adapter using the fwmatrix.txt

configuration file. When using the fwmatrix.txt

file, you must update each supported adapter's type, firmware, and boot code entries and place the corresponding firmware and boot code images into their respective directories. The fwmatrix.txt

file enables all operations that are used with auto-discovery.

Broadcom - 6 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

1.3

Command Syntax

Chapter 1: Introduction Command Syntax In all cases, the commands are given with the prefix

os

. When you enter any command, you must replace

os

with either:   ./lin – For the Linux LpCfg utility commands, for use on Linux machines.

win – For the WinPE LpCfg utility commands, for use on WinPE machines.

 

NOTE

WinPE is supported on FC adapters only. It is not supported on LPe16202/OCe15100 adapters in NIC+FCoE mode.

The LpCfg utility commands are not case-sensitive, nor are their arguments. You can enter them in uppercase, lowercase, or mixed case. However, for Linux operating systems, use linlpcfg (all lowercase) for the utility commands; for example, ./linlpcfg listhba .

The LpCfg utility commands use both of the following items: One space between the command name and the first argument.

One space between additional arguments.

NOTE

Do not put a space before or after the equal sign within an argument.

World Wide Name (WWN) values are reported and specified with two 4-byte hexadecimal words – WWN word 0 (w0) and WWN word 1 (w1). To make the full WWN, concatenate the w0 and w1 values.

For detailed information on the command line interface, see

Chapter 3 , Elxflash Utility Command Line Interface

, and

Chapter 4 , LpCfg Utility Command Line Interface .

1.4

Supported Platforms

For information on supported adapters and supported versions of operating systems and platforms, see http://www.broadcom.com

.

Broadcom - 7 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

1.5

Abbreviations

IEEE GUI ISO LUN MAC MILI ms NIC BIOS CFA EFI EROM FC FCoE HBA HEX PCI PCI_ID PE POST RHEL ROM RPM SAN SLES UCNA VPD VWWNN VWWPN WWN WWNN WWPN XML basic input/output system converged fabric adapter Extensible Firmware Interface erasable read-only memory Fibre Channel Fibre Channel over Ethernet host bus adapter hexadecimal Institute of Electrical and Electronics Engineers graphical user interface International Organization for Standards logical unit number media access control management interface library milliseconds network interface card Peripheral Controller Interconnect PCI device identification number Preinstallation Environment power-on self-test Red Hat Enterprise Linux read-only memory Red Hat Package Manager storage area network SuSE Linux Enterprise Server universal converged network adapter Vital Product Data Virtual World Wide Node Name Virtual World Wide Port Name World Wide Name World Wide Node Name World Wide Port Name Extensible Markup Language Chapter 1: Introduction Abbreviations Broadcom - 8 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 2: Installation Platform Prerequisites

Chapter 2: Installation

This chapter details prerequisites and procedures for installing and uninstalling the Elxflash Offline and Stand-alone kits for Linux, VMware, and Windows systems. It also describes the update procedure for each operating system.

2.1

2.1.1

Platform Prerequisites

The utilities included in the Elxflash Offline and Stand-alone kits for Linux have prerequisites that must be installed prior to installing the utilities. There are no prerequisites for installing the Elxflash Offline and Stand-alone kits on the VMware and Windows operating systems.

Linux

The Linux platform uses additional software, such as libraries, to run the different versions of the utility. This section identifies the prerequisites.

   

NOTE

The Linux driver must be installed on the system for the applications to work properly.

The following software must be installed to run the utility.

libnl ethtool lspci libsysfs (optional)

2.2

2.2.1

Installing the Elxflash Offline Kit for Linux

The Elxflash Offline kit for Linux uses an install script to install the elxflash and linlpcfg utilty RPM packages. The install script determines the correct architecture and distribution, and it updates the existing Elxflash Offline and Elxlinlpcfg RPM packages. If there are no existing Elxflash Offline or Elxlinlpcfg RPM packages, the install script installs the packaged Elxflash Offline and Elxlinlpcfg RPM packages.

To install the Elxflash Offline kit for Linux: 1.

2.

Untar the installation tarball.

Run the install script located on the root of the installation kit.

Example: $ tar zxvf elxflashOffline-linux-<

version

>-<

rel

>.tgz

$ cd elxflashOffline-linux-<

version

>-<

rel

> $ ./install.sh

Updating

To update an existing Elxflash Offline kit for a Linux installation, run the install.sh

script to update the Elxflash Offline and Elxlinlpcfg RPM packages.

Broadcom - 9 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

2.2.2

Uninstalling

Chapter 2: Installation Installing the Elxflash Offline Kit for Windows PE The Elxflash Offline kit for Linux uses an uninstall script to uninstall the utility. The uninstall script performs specific actions depending on the switches that are used.

  ./uninstall.sh

– Uninstalls the Elxflash Offline and Elxlinlpcfg RPM packages.

./uninstall.sh -h – Displays a summary of all available switches.

To uninstall the Elxflash Offline kit for Linux, run the uninstall script located on the root of the installation kit.

Example: $ cd elxflashOffline-linux-<

version

>-<

rel

> $ ./uninstall.sh

2.3

2.3.1

2.3.2

Installing the Elxflash Offline Kit for Windows PE

   1.

2.

3.

To install the Elxflash Offline kit for Windows PE: Unzip the Offline-WinPE-<

version

>-<

rel

>.zip

.

Change the directory to the correct architecture subdirectory.

Run setupElxAll-<

arch

>.exe

.

The following components are installed: Storport CNA driver Storport Fibre Channel (FC) driver winLpCfg – Elxflash Offline

NOTE

The setupElxAll-<

arch

>.exe

file is compatible only with WinPE. It does not function with any version of Windows Server.

Updating

To update an existing Elxflash Offline kit installation, run the same steps that you used for installing the Elxflash Offline kit for Windows PE previously.

The installer uninstalls the existing version and then installs the updated version.

Uninstalling

To uninstall the Elxflash Offline kit for Windows PE, run the following commands: cd \ProgramData\Tarma Installer\ setup.exe /remove Broadcom - 10 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

2.4

Chapter 2: Installation Extracting the Driver Files from the Elxflash Offline Kit for Windows

Extracting the Driver Files from the Elxflash Offline Kit for Windows

To extract the driver files from the Elxflash Offline kit, you can use the installer or the command line. When extracting these files, all files, both x64 and x86, are extracted to <

Drive

>:\My Documents\Emulex\Drivers . This location is hard-coded and cannot be changed.

NOTE

Extracting all the drivers takes an additional 28 MB. By default, Windows PE allocates only 32 MB of writable memory. The size of the writable memory can be increased when building the WinPE ISO image.

You can extract the driver files using the GUI mode by running the installer, or you can use the command line in silent mode.

To extract the drivers from the Elxflash Offline kit for Windows, perform these steps: 1.

2.

In GUI mode: a.

b.

c.

Run the installer.

From the Installation Options screen, select

Extract All Drivers

, and deselect

Install elxApp_Drivers (64-bit)

.

Click

Install

to continue.

In Silent mode, from the command line, type: start/wait SetupElxAll-x64.exe/q2 extract=2

NOTE

Values for the extract parameter are:  0 – Install the package; do not extract the drivers (default)   1 – Install the package; extract the drivers 2 – Do not install the package; extract the drivers

2.5

Extracting the Elxflash Stand-alone Kit for Linux, Windows, and VMware

     The Elxflash Stand-alone kit is not installed; you must extract it from its zip file. After you extract the utility, the following directories are created. The Linux executable files are extracted to the lx\ directory, the VMware executable files are extracted to the esxi\ directory, and the Windows executable files are extracted to the win\ directory.

boot\ firmware\ lx\ esxi\ win\ Broadcom - 11 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 2: Installation Extracting the Elxflash Stand-alone Kit for Linux, Windows, and VMware In Windows, for example, three directories are visible in the kit's root directory after you extract the stand-alone utility. The top-level boot directory and firmware directory are the default directories in which Elxflash looks for boot code and firmware images. Ensure that firmware and boot code are located in these directories.

# dir 07/05/2012 07:02 PM

.

07/05/2012 07:02 PM

..

07/02/2012 03:14 PM

boot 07/02/2012 03:14 PM firmware 07/02/2012 03:15 PM win The Elxflash Stand-alone kit for Linux has the same dependencies as the Elxflash Offline kits for Linux. The Elxflash Stand-alone kits for Windows and VMware do not have any dependencies. See

Section 2.1, Platform Prerequisites .

NOTE NOTE

Update and uninstall procedures for the Elxflash Stand-alone kit are not needed. When a new version is available, you extract it, replacing the older version.

To manage LightPulse adapters, you must install the operating system-specific FC drivers. To manage LPe16202/OCe15100 adapters, you must install the operating system-specific NIC drivers and the operating system-specific FC/FCoE or FCoE drivers.

Broadcom - 12 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface

Chapter 3: Elxflash Utility Command Line Interface

Firmware images are available on the Broadcom® support site at http://www.broadcom.com

. For all adapters, firmware image files are expected to be in the sub-directory named firmware

.

For all LPe16000-series, LPe31000-series, and LPe32000-series adapters, the firmware image file includes boot code. LPe12000-series adapters use a separate boot code image file, which is expected to be in the sub-directory named boot . Two supported modes for updating firmware and boot code are available for each Elxflash utility switch. The fwmatrix.txt

file mode allows you to specify the adapter models and firmware file (or firmware and boot files) to update. Auto-discovery mode automatically updates the discovered adapters with the contents of the firmware directory (and the boot directory, if applicable).

Regardless of the firmware update mode you choose, use the /query ( /q ) switch with all operational switches.

For example: # ./elxflash /q HBA=LPe32000, Port Type=FC, WWN=10:00:00:90:FA:94:2E:CA, PCI ID=E300, VID=10DF, SSID=E321, SVID=10DF, Firmware=11.2.50.48, Boot Code=11.2.50.35, Boot Enabled=1 HBA=LPe12002, Port Type=FC, WWN=10:00:00:00:C9:A1:80:00, PCI ID=F100, VID=10DF, SSID=F100, SVID=10DF, Firmware=UD202A1, Boot Code=UU700A2, Boot Enabled=1 HBA=LPe12002, Port Type=FC, WWN=10:00:00:00:C9:A1:80:01, PCI ID=F100, VID=10DF, SSID=F100, SVID=10DF, Firmware=UD202A1, Boot Code=UU700A2, Boot Enabled=1 If the /q switch is used with an operational switch, the results include an additional field called Supported Firmware or Supported Boot Code . Regardless of the mode and operational switch you choose, one of the following download summaries is displayed after the command is executed:   

NOTE

In this chapter, references to FCoE and NIC apply only to LPe16202/OCe15100 adapters in NIC+FCoE mode. References to FC apply to all other LightPulse adapters and to LPe16202 adapters in FC mode.

FC adapter download summary: <

date

><

time

> HBA=<

model

>, Port Type=<

port_type

>, WWN=<

wwn

>, Update=, Image=<

image

>, New=<

version

>, Old=<

version

>, Status=<

description

> FCoE adapter download summary <

date

><

time

> HBA=<

model

>, Port Type=<

port_type

>, WWN=<

wwn

>, Update=Firmware, Image=<

image

>, New=<

version

>, Old=<

version

>, Status=<

description

> NIC adapter summary <

date

><

time

> HBA=<

model

>, Port Type=<

port_type

>, MAC=<

mac_address

>, Update=Firmware, Image=<

image

>, New=<

version

>, Old=<

version

>, Status=<

description

> Return Code=<

n

> where <

description

> is Success or Error , and <

n

> = 0 for completion with no errors or a nonzero error code for any error.

Broadcom - 13 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

3.1

Using the fwmatrix.txt File Mode

Chapter 3: Elxflash Utility Command Line Interface Using the fwmatrix.txt File Mode To use the fwmatrix.txt

file, you must update the firmware and boot code directories with the appropriate firmware and boot code images. The fwmatrix.txt

file includes adapter entries followed by a firmware image file entry. An additional boot image entry is provided for LPe12000-series adapters.

NOTE

To avoid a firmware update failure, ensure that there are no spaces in the model names in the fwmatrix.txt

file.

When the Elxflash utility uses the fwmatrix.txt

file, it locates the adapter model entry and then attempts to download the specified firmware image file and, for LPe12000-series adapters, the specified boot code image file.

On an LPe16202/LPe15100 adapter running in NIC+FCoE mode, the Elxflash model name must include the highest protocol being used on that model. You can identify an adapter's Elxflash model name by running the /query command.

NOTE

On an LPe16202/LPe15100 adapter running in NIC+FCoE mode, the highest protocol is FCoE.

3.2

3.3

Using Auto-Discovery Mode

If the /auto switch is used with an operational switch, such as /update , the Elxflash utility automatically discovers adapters, and using the firmware and boot subdirectories, performs the operation specified by the switch on each adapter.

Auto-Discovery (/auto)

Usage: /auto The /auto switch instructs the Elxflash utility to ignore the fwmatrix.txt

file, automatically discover local adapters, and perform specified operations employing an additional switch using the firmware and boot directories.

      The /auto switch must be used with an additional operational switch, such as: /f /ff /fb /downgrade /rewrite /update Example usage: ./elxflash /auto /update /q – Updates the firmware and boot code using the firmware and boot directories.

  The fwmatrix.txt

file is ignored. The desired versions of firmware must be in the firmware directory.

Using the firmware subdirectory, the Elxflash utility automatically discovers the best matching firmware for each installed and supported adapter.

Broadcom - 14 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface Downgrade (/downgrade or /g)  If multiple versions of firmware or boot code are found for an adapter, the Elxflash utility uses the most recent version when performing the firmware update.

3.4

Downgrade (/downgrade or /g)

Usage: /downgrade or /g The /downgrade switch downgrades the firmware or boot code of each adapter if the currently installed versions are more recent than the downgrade versions. This switch cannot be used with the /update or /rewrite commands.

Example usage: ./elxflash /downgrade /auto /q – Downgrades the firmware or boot code using auto-discovery.

    a.

b.

c.

d.

e.

The fwmatrix.txt

file is ignored. The desired downgrade versions of firmware or boot code must be in their respective directories.

If the downgrade versions are older than the currently installed versions on the adapter, the downgrade versions are downloaded to the adapter.

If multiple downgrade versions of firmware or boot code are found for an adapter, the next-previous downgrade versions are downloaded to the adapter.

When performing the boot code downgrade operation, the Elxflash utility first tries to match by adapter family and boot type. If a match is not found, the Elxflash utility then tries to match by boot type. If the utility matches by boot type and multiple versions of boot code are detected, the utility chooses the downgrade file in the following order: Universal (U) Pair (P) Open (O) EFI (E) x86 (B) ./elxflash /downgrade /q – Downgrades the firmware or boot code using the fwmatrix.txt

file.

  For each installed and supported adapter, the current firmware or boot code versions are compared with the versions specified in fwmatrix.txt

.

If the downgrade version in fwmatrix.txt

is older than the currently installed version, the downgrade version of firmware or boot code is downloaded to that adapter.

3.5

Force Firmware and Boot Code (/f)

Usage: /f The /f switch forces a firmware and boot code download to an adapter regardless of the current version on the adapter, and it is performed regardless of any additional operational switches given on the command line. Also, see

Section 3.6, Force Boot Code (/fb)

, and

Section 3.7, Force Firmware (/ff ) .

Example usage: ./elxflash /f /auto /q – Forces a firmware and boot code download using auto-discovery.

 The fwmatrix.txt

file is ignored. The desired versions of firmware and boot code must be in their respective directories.

Broadcom - 15 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface Force Boot Code (/fb)  If multiple versions of firmware or boot code are found for an adapter, the Elxflash utility uses the most recent version when performing the firmware and boot code downloads.

./elxflash /f /q – Forces a firmware and boot code download using the fwmatrix.txt

file.

 For each installed and supported adapter, this command forces a download of firmware and boot code using the versions specified in the fwmatrix.txt

file.

3.6

3.7

Force Boot Code (/fb)

Usage: /fb The /fb switch forces a boot code download to an adapter regardless of the boot code version installed on the adapter, and it is performed regardless of any additional operational switches given on the command line.

Example usage: ./elxflash /fb /auto /q – Forces a boot code download using auto-discovery.

  The fwmatrix.txt

file is ignored. The desired versions of boot code must be in the boot directory.

If multiple versions of boot code are found for an adapter, the Elxflash utility uses the most recent version when performing the boot code download.

./elxflash /fb /q – Forces a boot code download using the fwmatrix.txt

file.

 For each installed and supported adapter, this command forces a download of boot code using the boot code version specified in the fwmatrix.txt

file.

NOTE

The /fb switch applies only to LPe12000-series adapters.

Force Firmware (/ff)

Usage: /ff The /ff switch forces a firmware download to an adapter regardless of the firmware version installed on the adapter or any additional operational switches given on the command line.

NOTE

Because boot code is included in the firmware image for LPe16000-series, LPe31000-series, and LPe32000-series adapters, this command has the same result as the /f command, which forces a firmware and boot code download.

Example usage: ./elxflash /ff /auto /q – Forces a firmware download using auto-discovery.

  The fwmatrix.txt

file is ignored. The desired versions of firmware must be in the firmware directory.

If multiple versions of firmware are found for an adapter, the Elxflash utility uses the most recent version when performing the firmware download.

./elxflash /ff /q – Forces a firmware download using the fwmatrix.txt

file.

 For each installed and supported adapter, this command forces a download of firmware using the firmware version specified in the fwmatrix.txt

file.

Broadcom - 16 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

3.8

Firmware Matrix Directory Change (/fmd)

Chapter 3: Elxflash Utility Command Line Interface Firmware Matrix Directory Change (/fmd) Usage: /fmd=<

directory

> The /fmd switch changes the location of the base directory in which fwmatrix.txt

is located.

3.9

Help (/h or /?)

Usage: /h or /?

The /h switch displays a help message detailing instructions on how to use the Elxflash utility.

3.10

Image Directory Change (/id)

Usage: /id=<

image_directory

> The /id switch is used to specify the location of the firmware and boot directories.

Example usage: ./elxflash /f /auto /id=/tmp /q – Forces a firmware and boot code download using auto-discovery.

    Elxflash looks for the firmware and boot directories in the /tmp directory.

The fwmatrix.txt

file is ignored. The desired versions of firmware and boot code must be in their respective directories.

In this example, firmware must be placed in the /tmp/firmware directory, and boot code must be placed in the /tmp/boot directory.

If multiple versions of firmware or boot code are found for an adapter, Elxflash uses the most recent versions when performing the firmware and boot code downloads.

./elxflash /f /id/tmp /q – Forces a firmware and boot code download using the fwmatrix.txt

file.

   Elxflash looks for the firmware and boot directories in the /tmp directory.

For each installed and supported adapter, a forced download of firmware and boot code occurs using the versions specified in the fwmatrix.txt

file.

In this example, firmware must be placed in the /tmp/firmware directory, and boot code must be placed in the /tmp/boot directory.

NOTE

This switch was /i in previous versions of the Elxflash utility.

3.11

Image Version Display (/iv)

Usage: /iv=<

image file

> The /iv switch shows the firmware image file’s version number. You must specify a path to the firmware image file for the command to decode the image file’s version.

Example usage: ./elxflash /iv=firmware/A11460.grp

1.1.46.0

Broadcom - 17 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

3.12

Log (/log)

Chapter 3: Elxflash Utility Command Line Interface Log (/log) Usage: /log=<

logfile

.txt> The /log switch appends the output of the Elxflash utility to a text file. Log can be used with any switch.

3.13

Preview (/p)

     Usage: /p The /p switch provides a download preview of all adapters the Elxflash utility can update using either auto-discovery or the fwmatrix.txt

file. The preview switch can be used with any of the operational switches, such as: /ff /fb /downgrade /rewrite /update When the preview switch is used, the Elxflash utility displays a download summary, but it does not actually perform the download.

NOTE

If the /p switch is used, the Status=<

description

> field displays Preview .

Each adapter's download preview displays the adapter's old and new image versions. The old image version represents the image version that is currently on the adapter. The new image version represents the image version the Elxflash utility would use during a download.

Example usage: ./elxflash /preview /auto /update – Previews an upgrade of firmware or boot code using auto-discovery.

   The fwmatrix.txt

file is ignored. The desired update versions of firmware or boot code must be in their respective directories.

If the update versions are later than the currently installed versions on the adapter, the Elxflash utility provides a download preview for each adapter that can be updated.

If multiple update versions of firmware or boot code are found for an adapter, the Elxflash utility provides a download preview using the most recent versions.

./elxflash /preview – Previews an upgrade of firmware or boot code using the fwmatrix.txt

file.

  For each installed and supported adapter, the current firmware and boot code versions are compared with the versions specified in the fwmatrix.txt

file.

If the update versions in the fwmatrix.txt

file are more recent than the currently installed versions, the Elxflash utility provides a download preview of firmware or boot code for each adapter that can be updated.

Broadcom - 18 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

3.14

Process FC HBAs Only (/fc)

Chapter 3: Elxflash Utility Command Line Interface Process FC HBAs Only (/fc) Usage: /fc The /fc switch causes Elxflash to act only on FC HBAs, including LPe16202/OCe15100 adapters in FC mode. It does not act on LPe16202/OCe15100 adapters in NIC+FCoE mode.

Example usage: ./elxflash /q /fc – Only FC HBAs are displayed for a query.

./elxflash /auto /up /fc – This command applies auto update only to FC HBAs.

When a firmware or boot code update is performed and the /fc switch is used, only FC adapters are updated; LPe16202/OCe15100 adapters in NIC+FCoE mode are not displayed.

3.15

Process UCNAs (/ucna)

Usage: /ucna The /ucna switch causes Elxflash to act only on LPe16202/OCe15100 adapters in NIC+FCoE mode.

Example usage: ./elxflash /q /ucna – Only LPe16202/OCe15100 adapters in NIC+ FCoE mode are displayed for a query.

./elxflash /auto /up /ucna – Apply auto update only to LPe16202/OCe15100 adapters in NIC+FCoE mode.

When a firmware/boot code update is performed and the /ucna switch is used, only LPe16202/OCe15100 adapters in NIC+FCoE mode are updated; FC HBAs are not displayed.

3.16

Query (/q)

Usage: /q The /q switch displays an adapter's model, WWN or MAC address, PCI_ID, firmware version, and boot code version. Query can be used with any switch.

Example usage: C:\elxflashStandalone-windows-10.0.567.22-1\win>elxflash.bat /q

NOTE

On FC adapters, the query switch displays boot code version information only if the adapter has boot code installed.

3.17

Ramdrive (/ramdrive)

NOTE

This command is available in the Windows Offline utility only.

Usage: /ramdrive=<

drive letter

>[:] The /ramdrive switch specifies the drive on which to create temporary files and log files. The default is drive X; the default drive in Windows PE.

Broadcom - 19 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

3.18

Rewrite (/rewrite or /e)

Chapter 3: Elxflash Utility Command Line Interface Rewrite (/rewrite or /e) Usage: /rewrite -or- /e The /rewrite switch updates the firmware or boot code of each adapter if the installed versions are earlier than, or the same as, the rewrite versions. This switch cannot be used with /update or /downgrade .

Example usage: ./elxflash /rewrite /auto – Rewrites the firmware or boot code using auto-discovery.

    a.

b.

c.

d.

e.

The fwmatrix.txt

file is ignored. The desired rewrite versions of firmware or boot code must be in their respective directories.

If the rewrite versions are more recent than, or the same as, the versions installed on the adapter, the rewrite versions are downloaded to the adapter.

If multiple rewrite versions of firmware or boot code are found for an adapter, the most recent versions are downloaded to the adapter.

When performing the boot code rewrite operation, Elxflash first tries to match by adapter family and boot type. If a match is not found, Elxflash then tries to match by boot type. If the utility matches by boot type, and multiple versions of boot code are detected, rewrite always chooses the boot code in the following order: Universal (U) Pair (P) Open (O) EFI (E) x86 (B) ./elxflash /rewrite – Rewrites the firmware or boot code using the fwmatrix.txt

file.

  For each installed and supported adapter, the current firmware or boot code versions are compared with the versions in fwmatrix.txt

file.

If the currently installed versions are less than or equal to the rewrite versions in fwmatrix.txt

file, the rewrite versions of firmware or boot code are downloaded to the adapter.

3.19

Silent (/s)

Usage: /s The /s switch prevents all output from being displayed.

Example usage: ./elxflash /f /auto /s – Forces a firmware and boot code download using auto-discovery and mutes all output to stdout.

   The fwmatrix.txt

file is ignored. The desired versions of firmware and boot code must be in their respective directories.

If multiple versions of firmware or boot code are found for an adapter, Elxflash uses the most recent versions when performing the firmware and boot code downloads.

No output is printed to stdout.

Broadcom - 20 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface Discover CFAs Using SysFS (/sysfs) (LPe16202/OCe15100 Adapters Only) ./elxflash /f /s – Forces a firmware and boot code download using the fwmatrix.txt

file and mutes all output to stdout.

  For each installed and supported adapter, a download of firmware and boot code is forced using the versions specified in the fwmatrix.txt

file.

No output is printed to stdout.

3.20

Discover CFAs Using SysFS (/sysfs) (LPe16202/OCe15100 Adapters Only)

NOTE

The libsysfs library must be installed. If the libsysfs library is not found, the /sysfs switch is not available.

Usage: /sysfs + operational switch /sysfs is an operational switch that discovers CFA (NIC) functions using the SysFS tool, and it discovers FC functions using the LpCfg tool. It also runs firmware downloads on CFAs using the ethtool utility or SysFS interface, and on FC adapters using the LpCfg utility. The /sysfs switch is used with any switch that displays adapter information; for example, /q , or any combination of switches that performs a download.

The following switches can be used:        /f – Force firmware and boot code /fb – Force boot code /ff – Force firmware /downgrade or /g /query or /q /rewrite or /e /update For example, ./elxflash /sysfs /auto /f discovers CFA NIC functions using SysFS and discovers legacy FC functions using LpCfg. It forces a firmware download on CFA adapters using ethtool or SysFS and forces a firmware and boot code download on legacy FC adapters using LpCfg.

NOTE

Only CFA NIC functions are displayed. Displaying FCoE functions is not supported.

When /sysfs is used, the VPD model name is not available.

The /sysfs switch is not supported by the Elxflash Stand-alone kit for VMware.

Example usage: /elxflash /sysfs /q

3.21

Update (/update)

Usage: /update The /update switch updates the firmware or boot code of each adapter if the currently installed versions are older than the update versions. This switch cannot be used with /downgrade or /rewrite .

Broadcom - 21 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface Verbose (/v) Example usage: ./elxflash /update /auto /q – Upgrades the firmware or boot code using auto-discovery.

    a.

b.

c.

d.

e.

The fwmatrix.txt

file is ignored. The desired update versions of firmware or boot code must be in their respective directories.

If the update versions are newer than the currently installed versions on the adapter, the update versions are downloaded to the adapter.

If multiple update versions of firmware or boot code are found for an adapter, the most recent versions are downloaded to the adapter.

When performing the boot code update operation, the Elxflash utility uses the most recent boot code version found. Because multiple compatible versions of boot code can exist, the most recent version is selected in the following order: Universal (U) Pair (P) Open (O) EFI (E) x86 (B)

NOTE

The most recent boot code version is downloaded regardless of the installed boot code. This allows upgrading from one type of boot code to another type.

./elxflash /update /q – Upgrades the firmware or boot code using the fwmatrix.txt

file.

  For each installed and supported adapter, the current firmware and boot code versions are compared with the versions specified in fwmatrix.txt

.

If the update versions in fwmatrix.txt

are more recent than the currently installed versions, the update versions of firmware or boot code are downloaded to that adapter.

3.22

Verbose (/v)

   Usage: /v The /v switch displays progress messages, and it can be used with any switch. When this switch is used, the following information is displayed: A download summary for all adapters that had successful or failed downloads A summary of unsupported adapters, if applicable A per-adapter message for each adapter the Elxflash utility did not update

3.23

VPD (/vpd)

   Usage: /vpd The /vpd command displays the VPD model name for supported adapters. You must use the vpd command with one of the following switches: /f – Force firmware and boot /fb – Force boot code /ff – Force firmware Broadcom - 22 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 3: Elxflash Utility Command Line Interface XML Output (/xml)      /xml – XML output /downgrade or /g /query or /q /rewrite or /e /update

NOTE

The /vpd command does not display any information if used without the switches listed previously. If you attempt to use the /vpd command without the switches listed previously, an error message is displayed.

If the /vpd command is used with the fwmatrix.txt

file, the model name in the fwmatrix.txt

file must match the VPD model name reported by Elxflash. Supported adapters include legacy FC adapters that support VPD.

3.24

XML Output (/xml)

Usage: /xml The /xml switch displays utility output in XML format.

Broadcom - 23 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Running the LpCfg Utility from the Command Prompt

Chapter 4: LpCfg Utility Command Line Interface

The LpCfg utility allows you to configure Emulex adapters before you install or boot a server operating system.

The LpCfg utility includes:   linlpcfg winlpcfg             

NOTE

Usage code and examples show

os

lpcfg.

Note that the

os

designation changes to ./lin if you are using LpCfg for Linux or VMware and to win if you are using LpCfg for Windows.

You can use the LpCfg utility to do the following: View information about an Emulex adapter Reset the adapter Return the adapter to its factory default settings Download firmware and boot code files Select a boot device Read and update WWNs Read MAC addresses Enable boot code Update configuration regions Set the adapter to use soft jumpers Run diagnostic tests Read and process script files Read, write, and reset VLAN IDs and VLAN Priorities

4.1

Running the LpCfg Utility from the Command Prompt

NOTE

The LpCfg utility is a command line utility and does not include a graphical user interface.

To run the LpCfg utility from the command prompt: 1.

2.

Boot the system with a supported operating system.

Start the LpCfg utility with a valid command or a valid script file name.

To start the LpCfg utility from the command line, move to the directory where the executable file resides and type:

os

lpcfg <

valid command

> Replace

os

with ./lin or win as appropriate.

  For example, starting the Linux or VMware LpCfg utility with a reset command: ./linlpcfg reset n=2 For example, starting the Windows LpCfg utility with a reset command: winlpcfg reset n=2 Broadcom - 24 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Running the LpCfg Utility Included with the Elxflash Stand-alone Kit

To start the LpCfg utility with a script file name, move to the directory where the LpCfg utility resides and type:

os

lpcfg @<

script file name

>  For example, starting the Windows LpCfg utility with script1.txt

in the c:\test directory: winlpcfg @C:\test\script1.txt

NOTE

To redirect screen output to a file, add <

filename

> at the end of each command.

For example:

os

lpcfg listboot n=1 >result.out

For more information on script files, see Section 4.3.8, Using Script Files

.

4.2

4.2.1

Running the LpCfg Utility Included with the Elxflash Stand-alone Kit

The Elxflash Stand-alone kit allows you to run Elxflash and LpCfg without installing the utilities. No drivers are included in the Stand-alone kit. No applications are installed, because the utility runs from inside the kit.

The Elxflash Stand-alone kit has the same capability as the Elxflash Offline kit, except you use the following scripts to run the utility:  

Linux

and

VMware

– linplcfg.sh

and elxflash.sh

Windows

– winlpcfg.bat

and elxflash.bat

Linux and VMware

1.

2.

3.

NOTE

Running 32-bit applications on Linux x86_64 is not supported. The sh scripts run only native executable files.

Extract the kit contents.

Change directory ( cd ) to ElxflashStandalone-linux-<

version

> .

The following directories must be present:

— — —

boot\ firmware\ lx\ For Elxflash, copy the firmware images to the firmware directory. Copy the boot images to the boot directory.

4.

NOTE

For Elxflash, each operating system architecture directory includes an fwmatrix.txt

file. You must use the fwmatrix.txt

directory that matches the current operating system architecture.

Change directory ( cd ) to the lx directory.

The following files and directories must be present:

— — — — —

i386\ x86_64\ ppc64\ elxflash.sh

linlpcfg.sh

The elxflash.sh

script configures the environment. Run Elxflash, and revert any changes before exiting. This script installs the MILI daemons if they are not already installed.

Broadcom - 25 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

4.2.2

Chapter 4: LpCfg Utility Command Line Interface Running the LpCfg Utility Included with the Elxflash Stand-alone Kit The linlpcfg.sh

script configures the environment. Run linlpcfg, and revert any changes before exiting. This script installs the MILI daemons if they are not already installed.

5.

NOTE

If OneCommand Manager is installed, the OneCommand Manager libraries are used by the Elxflash and linlpcfg utilities.

The linlpcfg.sh

and elxflash.sh

scripts call the native versions of Elxflash and linlpcfg. For example, on Linux x86_64, the 64-bit utilities are called.

The adapter being managed by the utilities included in the Elxflash Stand-alone kit must not be managed simultaneously by other Emulex utilities, including OneCommand Manager.

To update firmware and boot code on an adapter, type: # ./elxflash.sh /auto up To display a list of HBAs, type: # ./linlpcfg.sh listhba Each time Elxflash or LpCfg is run, a log file is created. On Linux these files are called: /var/log/clu/elxflash.log

/var/log/clu/linlpcfg.log

Windows

1.

2.

3.

Extract the kit contents.

Change directory ( cd ) to Elxflash Standalone-windows-<

version

> .

The following directories must be present:

— — —

boot\ firmware\ win\ For Elxflash, copy the firmware images to the firmware directory. Copy the boot images to the boot directory.

4.

NOTE

For Elxflash, each operating system architecture directory includes an fwmatrix.txt

file. You must use the fwmatrix.txt

directory that matches the current operating system architecture.

Change directory ( cd ) to the win directory.

The following files and directories must be present:

— — — —

win32\ x64\ elxflash.bat

winlpcfg.bat

The elxflash.bat

script configures the environment. Run Elxflash, and revert any changes before exiting. This script installs the MILI service if it is not already installed.

The winlpcfg.bat

script configures the environment. Run winlpcfg , and revert any changes before exiting. This script installs the MILI service if it is not already installed.

NOTE

The MILI service is temporarily installed. The service is removed after the script runs.

If OneCommand® Manager is installed, the OneCommand Manager libraries and OneCommand Manager MILI service are used by the Elxflash and winlpcfg utilities.

Broadcom - 26 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands 5.

The winlpcfg.bat

and elxflash.bat

scripts call the native versions of elxflash.exe

and winlpcfg.exe

. For example, on Windows x64, the 64-bit utilities are called.

The adapter being managed by the utilities included in the Elxflash Stand-alone kit must not be managed simultaneously by other Emulex utilities, including OneCommand Manager.

To update firmware and boot code on an adapter in Windows, type: # elxflash.bat /auto /up To display a list of HBAs in Windows, type from the win directory: # winlpcfg.bat listhba Each time Elxflash or LpCfg is run, a log file is created. On Windows these files are called: C:\clu\log\elxflash.log

C:\clu\log\winlpcfg.log

4.3

Supported Commands

   

Table 1

lists all of the LpCfg commands that are supported on Emulex adapters on various platforms.

 indicates commands that are supported on both winlpcfg and linlpcfg.

L indicates commands that are supported only on linlpcfg.

FCoE only

indicates commands that are supported only by LPe16202/OCe15100 adapters in FCoE mode.

NIC only

indicates commands that are supported by LPe16202/OCe15100 adapters in NIC mode.

Table 1 Supported Commands for LpCfg1 Commands

Operating Systems

FC Adapters x86

RHEL 6.7+ SLES 11 SP3+ WinPE 5+  L

x64

RHEL 6.7+ RHEL 7.2+ SLES 11 SP3+ SLES 12 SP2 WinPE 5+  L

PPC

RHEL 6.7+ RHEL 7.2+ SLES 11 SP3+ L L

LPe16202/OCe15100 Adapters in NIC+FCoE Mode x86

RHEL 6.7+ SLES 11 SP3+ N/A FCoE only N/A

x64

RHEL 6.7+ RHEL 7.2+ SLES 11 SP3+ SLES 12 SP2 N/A FCoE only N/A config directDownload Supported on LPe12000-series adapters only.

disableboot disablebootdevice download a=<

adapter name

> is supported on LPe12000-series adapters only.

enableboot enablebootdevice extloopback factorydefaults Not supported on LPe16202/OCe15100 adapters in NIC+FCoE mode.

              L L L L L L  N/A FCoE  N/A FCoE  N/A N/A FCoE  N/A FCoE  N/A Broadcom - 27 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

Table 1 Supported Commands for LpCfg1 (Continued) FC Adapters Commands

hbaattr h (Help) intloopback listboot listhba listrev listmac listwwn logfile networkboot pciloopback posttest Supported on LPe12000-series adapters only.

readaltboot readbootdevice readconfig readmac readvlanprops reset restoredefsvmac a restoredefwwn restorenwwn restorevlanprops restorewwn savewwn screendisplay scriptvwwnn scriptvwwpn scriptwwnn scriptwwpn setaltboot setbootdevice version vpd writesvmac a writevlanprops writewwn a.

x86

      N/A   N/A   N/A  This command is supported only on certain OEM-specific adapters.

       N/A       N/A    N/A N/A  N/A N/A         N/A       N/A    N/A N/A  N/A

x64

      N/A   N/A   Broadcom - 28 -

PPC

 L L L L L N/A L L N/A L L

LPe16202/OCe15100 Adapters in NIC+FCoE Mode x86

   N/A  FCoE only NIC only FCoE only   FCoE only N/A

x64

   N/A  FCoE only NIC only FCoE only   FCoE only N/A L L L N/A N/A L N/A L L N/A L L L L L L L L L L L N/A N/A L FCoE only FCoE only FCoE only   FCoE only  FCoE only FCoE only  FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only     FCoE only FCoE only FCoE only FCoE only   FCoE only  FCoE only FCoE only  FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only FCoE only     FCoE only

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.1

4.3.1.1

4.3.1.2

Help Command and General Adapter Management Commands

Use the following commands to view the online help, reset the adapter, or reset the adapter to factory defaults. You can also run a POST.

Viewing the Syntax for Commands (help)

To view the syntax for all available commands, type:

os

lpcfg help To view the syntax for a specific command, type:

os

lpcfg help <

command

> For example:

os

lpcfg help download returns a response similar to the following:   For Linux and VMware: download n=<

adapter

> i=<

path/image_filename

> or download a=<

adaptertype

> i=<

path/image_filename

> For Windows: download n=<

adapter

> i=<

path\image_filename

> or download a=<

adaptertype

> i=<

path\image_filename

>

Resetting an Adapter (reset)

This command resets a specific adapter or all adapters in the system.

ATTENTION

Executing a reset on an FC adapter that is being used to boot from SAN is not recommended. The reset might cause a loss of connectivity to the SAN and possible loss of data. To reset an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter you want to reset to a non-boot-from-SAN host and reset it from there.

 If the host with the reset target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The intended target adapter can now be reset, because it is not being actively used for boot from SAN.

To reset one adapter, type:

os

lpcfg reset n=<

adapter number

> To reset all adapters in the system, type

os

lpcfg reset n=all Broadcom - 29 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.1.3

4.3.1.4

Resetting an Adapter to the Factory Defaults (factorydefaults)

This command returns the adapter to the factory default profile and configuration. A reboot is required for the changes to take effect.

NOTE

The factorydefaults command is not supported on LPe16202/OCe15100 adapters in NIC+FCoE mode.

After a successful factory reset on LPe32000-series, LPe31000-series, or LPe16000-series adapters, the adapter is offline. Perform an immediate reboot to complete the reset and return the adapter to full functionality. An LPe12000-series adapter is online after the reset is complete and does not require a reboot.

ATTENTION

Restoring the factory defaults on an FC adapter that is being used to boot from SAN is not recommended. The restore command might cause a loss of connectivity to the SAN and possible loss of data. To restore the factory defaults on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to restore the defaults to a non-boot-from-SAN host and perform the restore defaults command from there.

 If the host with the restore defaults target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The factory defaults can now be restored on the intended target adapter, because it is not being actively used for boot from SAN.

To return an adapter to its default settings, type:

os

lpcfg factorydefaults n= The following example returns adapter number 1 to its default settings.

os

lpcfg factorydefaults n=1

Running a Power-on Self-Test (posttest)

This command runs a POST on the selected adapter.

ATTENTION

Running a POST on an FC adapter that is being used to boot from SAN is not recommended. The posttest command might cause a loss of connectivity to the SAN and possible loss of data. To run a POST on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to run POST to a non-boot-from-SAN host and run POST from there.

If the host with the posttest target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot from SAN adapters. The POST can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

Broadcom - 30 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.2

4.3.2.1

To run the adapter POST, type:

os

lpcfg posttest n=<

all

|

adapter number

> The following example runs a POST on adapter number 1.

os

lpcfg posttest n=1

Viewing Adapter Information

Use the following commands to view different kinds of adapter information, such as VPD, boot device information, and adapter attributes.

   

Viewing Emulex Conventional Names Instead of VPD (/c)

Adding /c to any command that uses the a= parameter to return adapter data causes the command to return an Emulex conventional model for the adapter rather than the model name of the adapter. /c can be used for any command that uses the model name. For instance, the following commands use the a= parameter and show this behavior. listhba config download directdownload

NOTE

The offline utility does not always display the model name of the adapter being tested.

In the following example, the VPD model name is reported for each adapter: # ./linlpcfg listhba Command: listhba HBA 1: 10000090 FA942ECA Functional FW: 11.2.50.48 devID:E300 Bus:8 Dev:0 Func:0 LPe32000-M2-D HBA 2: 10000000 C9A18000 Functional FW: US2.02A1 devID:F100 Bus:E Dev:0 Func:0 LPe12002-M8 HBA 3: 10000000 C9A18001 Functional FW: US2.02A1 devID:F100 Bus:E Dev:0 Func:1 LPe12002-M8 To list adapter information using the conventional name rather than the VPD, type # ./linlpcfg listhba /c The following information is returned: Command: listhba /c HBA 1: 10000090 FA942ECA Functional FW: 11.2.50.48 devID:E300 Bus:8 Dev:0 Func:0 LPe32000 HBA 2: 10000000 C9A18000 Functional FW: US2.02A1 devID:F100 Bus:E Dev:0 Func:0 LPe12002 HBA 3: 10000000 C9A18001 Functional FW: US2.02A1 devID:F100 Bus:E Dev:0 Func:1 LPe12002 The output from this command includes the Emulex conventional model name – LPe12002, rather than the VPD model name – LPe12002-M8.

Broadcom - 31 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.2.2

4.3.2.3

4.3.2.4

4.3.2.5

4.3.2.6

4.3.2.7

Viewing the LpCfg Utility Version Information (version)

This command shows the LpCfg utility version information.

To view this information, type:

os

lpcfg version

Viewing VPD (vpd)

This command shows the VPD of the adapter specified by its number.

To display VPD, type:

os

lpcfg vpd n=<

adapter number

>

Viewing Boot Device Information (readbootdevice)

This command shows the WWN, the LUN (in decimal format), and the topology in use for the currently selected boot device.

To show this information, type:

os

lpcfg readbootdevice n=<

adapter number

> The following example reads WWN and LUN for adapter number 1:

os

lpcfg readbootdevice n=1

Viewing Boot Code Versions (listboot)

This command lists all the boot code versions that are loaded in the flash of the adapter. If the selected adapter does not have boot code, it returns error code 39.

To list boot code versions, type:

os

lpcfg listboot n=<

adapter number

> The following example lists boot code versions that are loaded on adapter number 3:

os

lpcfg listboot n=3

Viewing Adapter Attributes (hbaattr)

This command displays adapter information.

To list the adapter attributes for all installed adapters, type:

os

lpcfg hbaattr To list the adapter attributes for one adapter, type

os

lpcfg hbaattr n=<

adapter_number

>

Viewing All Adapters in the System (listhba)

This command lists all installed adapters in the system. Information includes the adapter number, the IEEE address assigned by the manufacturer, the functional firmware, the adapter type, and possible mailbox errors.

To list all adapters in the system, type:

os

lpcfg listhba

NOTE

listhba with option /c displays the conventional model names instead of the model names contained in the VPD.

Broadcom - 32 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.2.8

4.3.2.9

4.3.2.10

4.3.2.11

4.3.2.12

Viewing the WWN of All Adapters in the System (listwwn)

This command lists all adapters installed in the system and shows the factory-assigned WWN, the nonvolatile WWPN, and the WWNN used to identify an adapter in the SAN.

The factory-assigned WWN is an IEEE address that cannot be changed in the field. The nonvolatile WWN can be modified in the field and persists after a restart of the operating system. The full factory-assigned WWN and nonvolatile WWN are a concatenation of the two 8-character values (word 0 and word 1) that are shown for each. You can modify the nonvolatile WWPN and WWNN using either the writewwn command or the scriptwwpn and scriptwwnn commands. For more information on the writewwn

command, see Section 4.3.4.1, Writing WWN and Updating NVPARMS (writewwn)

.

If the system does not have any Emulex adapters installed, it returns error code 45.

To show the WWN information, type:

os

lpcfg listwwn

Viewing the MAC Address (listmac)

This command shows the MAC address of a NIC port on an LPe16202/OCe15100 adapter in NIC+FCoE mode .

To view the MAC address of a NIC port, type:

os

lpcfg listmac n=<

adapter number

>

Reading the MAC Address (readmac)

This command shows the current, factory, and semivolatile MAC addresses for the adapter number specified.

The readmac command is supported only on LPe16202/OCe15100 adapters in NIC+FCoE mode. To view the MAC address of the adapter number specified, type:

os

lpcfg.exe readmac n=<

adapter number

> The following example lists information for adapter number 1: >

os

lpcfg.exe readmac n=1 Command: readmac n=1 adapter 1: Current MAC Address : 00-90-FA-30-43-AA Factory MAC Address : 00-90-FA-30-43-30 Semi-Volatile MAC Address: 00-90-FA-30-43-AA Command completed, NO Error

Viewing Firmware Program Revisions (listrev)

This command shows the firmware versions in the adapter’s flash memory, specified by their numbers.

To show revisions, type:

os

lpcfg listrev n=<

adapter number

> The following example lists information for adapter number 3:

os

lpcfg listrev n=3

Viewing Selected Configuration Regions (readconfig)

This command shows the contents of the selected configuration region up to the initialized length or the specified byte count (if the initialized length is less than the specified byte count). Valid region numbers are 0 to 32. You must initialize the configuration region first by writing data to it.

Broadcom - 33 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.3

4.3.3.1

NOTE

The readconfig command only supports reading configuration regions 0, 8, and 32 on the following adapters:  LPe16000-series adapters   LPe31000-series adapters LPe32000-series adapters To read a configuration, type:

os

lpcfg readconfig n=<

adapter number

> r=<

region number

> l=<

byte count

> The following example reads the configuration for adapter number 1, region 0, byte count 20:

os

lpcfg readconfig n=1 r=0 l=20

Firmware and Boot Code Download Commands

The following firmware and boot code download commands include a command to download a firmware or boot code file and a command to access the flash device directly.

Downloading a File (download)

This command downloads a firmware or boot code file to a specific adapter.

ATTENTION

Downloading a firmware or boot code file to an FC adapter that is being used to boot from SAN is not recommended. The download command might cause a loss of connectivity to the SAN and possible loss of data. To download a firmware or boot code file to an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to download the file onto a non-boot-from-SAN host and perform the download command from there.

If the host with the download target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The firmware or boot code file can now be downloaded onto the intended target adapter, because it is not being actively used for boot from SAN.

The adapter name is the name that appears when you run the listhba command. For more information on the listhba

command, see Section 4.3.2.7, Viewing All Adapters in the System (listhba) .

To download a firmware image file to an adapter specified by its number, type:

os

lpcfg download n=<

adapter number

> i=<

firmware image filename

> The following example downloads the uu513a10.prg

boot code file to adapter number 6; in this example, the boot code file is for an LPe12000 adapter:

os

lpcfg download n=6 i=uu513a10.prg

NOTE

Boot code on LPe16000-series, LPe31000-series, and LPe32000-series adapters is updated by downloading firmware. LpCfg does not support updating boot code separately for these adapters.

Broadcom - 34 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.3.2

Accessing the Flash Device Directly (directdownload)

This command accesses the flash device on the adapter directly without using the adapter firmware. This feature is useful in downloading a ROM file image if the firmware has been corrupted. The adapter name is the name that appears when you run the listhba command. You can also use default for the adapter name if only one single-port adapter or one dual-port adapter is in the system. For more information on the listhba command, see

Section 4.3.2.7, Viewing All Adapters in the System (listhba)

.

NOTE

You cannot use directdownload in a script file.

This command is supported only on LPe12000-series adapters.

ATTENTION

Accessing the flash device directly on an FC adapter that is being used to boot from SAN is not recommended. The directdownload command might cause a loss of connectivity to the SAN and possible loss of data. To run the directdownload command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to run the directdownload command to a non-boot-from-SAN host and run the command from there.

 If the host with the directdownload target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The directdownload command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

To access the flash device on the adapter directly, type one of the following (all on one line): In Windows:

os

lpcfg directdownload a=<

adapter name/default

> i=<

path\image_filename

> s=<

selection 0 or 1

> In Linux:

os

lpcfg directdownload a=<

adapter name/default

> i=<

path/image_filename

> s=<

selection 0 or 1

> where s=1 saves the existing VPD.

The following example accesses the flash device on an LPe12000 HBA in Windows: winlpcfg directdownload a=lpe12000 i=C:\image\ud100a8.rom s=1 The following example accesses the flash device if the offline utility cannot detect the adapter type and only one single-port adapter or one dual-port adapter is in the Windows system: winlpcfg directdownload a=default i=C:\image\ud100a8.rom s=1

ATTENTION

If s=0 , the ROM images used with the directdownload command might not contain certain VPD information; for example, serial number, adapter model, or manufacturer. Direct download of a ROM image that has not been confirmed to contain the correct VPD image updates the board's firmware, but it also clears the VPD. The board will function. If you use calls for VPD in your applications, the information might be changed or missing.

Broadcom - 35 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.4

4.3.4.1

World Wide Name Commands

The following commands allow you to use the WWN to update NVPARAMS, save WWN data to a file, and restore WWN data while updating NVPARAMS. You can also restore the NVPARAMS and the IEEE address.

Writing WWN and Updating NVPARMS (writewwn)

This command allows you to enter word 0 and word 1 of the WWPN or WWNN from the keyboard or from a barcode scanner to update a specified adapter’s NVPARMS with a new WWPN or WWNN. The new WWPN and WWNN are used the next time the adapter is discovered. The adapter stores the original WWPN and WWNN in another region of the memory so it can be used to identify the adapter as it was manufactured. The WWN can also be read with a barcode scanner.

ATTENTION

Running a writewwn command on an FC adapter that is being used to boot from SAN is not recommended. The writewwn command might cause a loss of connectivity to the SAN and possible loss of data. To write to the WWN and Update NVPARMS on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the writewwn command to a non-boot-from-SAN host and run writewwn from there.

 If the host with the writewwn target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now write the WWN or update the NVPARMS on the intended target adapter, because it is not being actively used for boot from SAN.

The writewwn command prompts you for the WWPN and WWNN data words, so it cannot be used in a script file. The scriptwwnn and scriptwwpn commands use values entered with the command, so they can be used in a script file.

ATTENTION

Use the writewwn command with caution. If you use the same WWPN or WWNN on more than one adapter in a fabric, unpredictable results might occur.

   

NOTE

Word 0 of WWNN and WWPN names must follow one of the following formats: 1 0 0 0 0

x x x

2

x x x x x x x

3

x x x x x x x

5

x x x x x x x

To modify the WWPN and WWNN, type:

os

lpcfg writewwn n=<

adapter number

> The offline utility prompts you to enter new data: WWPN word 0 WWPN word 1 WWNN word 0 WWNN word 1 Broadcom - 36 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.4.2

4.3.4.3

4.3.4.4

The following example writes the WWPN and WWNN for adapter number 1.

os

lpcfg writewwn n=1 Enter or Scan value for WWPN word 0 now Enter a value.

10000000 The system echoes what you entered, followed by the next prompt: 10000000 Enter or Scan value for WWPN word 1 now

Saving WWN Data to a File (savewwn)

This command reads the original words 0 and 1 of the IEEE address, installed by manufacturing, from configuration regions 16 (or 32) of the adapter (specified by its number), and it saves the configuration region information in the selected WWN file.

To save the WWN data to a file, type:

os

lpcfg savewwn n=<

adapter number

> c=<

wwn filename

> The following example reads the configuration region information on adapter number 4 and saves it to the contents of the ctwwn.sav

file:

os

lpcfg savewwn n=4 c=ctwwn.sav

Restoring WWN and Updating NVPARMS (restorewwn)

This command restores words 0 and 1 of the IEEE address from a specified file created with the savewwn command and uses them to update the NVPARMS port name with this IEEE address.

ATTENTION

Running a restorewwn command on an FC adapter that is being used to boot from SAN is not recommended. The restorewwn command might cause a loss of connectivity to the SAN and possible loss of data. To restore the WWN and Update NVPARMS on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the restorewwn command to a non-boot-from-SAN host and run restorewwn from there.

 If the host with the restorewwn target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now restore the WWN and update the NVPARMS on the intended target adapter, because it is not being actively used for boot from SAN.

To restore the WWN, type:

os

lpcfg restorewwn n=<

adapter number

> c=<

wwn filename

> The following example updates the NVPARMS on adapter number 4 with the ctwwn.sav

file.

os

lpcfg restorewwn n=4 c=ctwwn.sav

Restoring NVPARMS (restorenvwwn) ATTENTION

Running a restorenvwwn command on an FC adapter that is being used to boot from SAN is not recommended. The restorenvwwn Broadcom - 37 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.4.5

command might cause a loss of connectivity to the SAN and possible loss of data. To restore the NVPARMS on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to use the restorenvwwn command to a non-boot-from-SAN host and run the command from there.

If the host with the restorenvwwn target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now restore the NVPARMS on the intended target adapter, because it is not being actively used for boot from SAN.

This command restores the nonvolatile WWPN and WWNN to the adapter, replacing any volatile WWPN and WWNN data, without powering off the adapter.

If the adapter does not have firmware that supports the volatile WWN, the following error message appears: Write Volatile Parms Error. Reported Error 48 If this occurs, install firmware that supports the volatile WWN.

To restore the nonvolatile WWN, type:

os

lpcfg restorenvwwn n=<

adapter number

> The following example restores the nonvolatile WWN on adapter number 2.

os

lpcfg restorenvwwn n=2

Restoring the IEEE Address (restoredefwwn)

This command reads the IEEE address (assigned by the manufacturer) and writes it to the nonvolatile WWPN and WWNN.

ATTENTION

Running a restoredefwwn restoredefwwn command on an FC adapter that is being used to boot from SAN is not recommended. The command might cause a loss of connectivity to the SAN and possible loss of data. To restore the IEEE address on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to use the restoredefwwn command to a non-boot-from-SAN host and run restoredefwwn from there.

If the host with the restoredefwwn target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now restore the IEEE address on the intended target adapter, because it is not being actively used for boot from SAN.

To restore the IEEE address, type:

os

lpcfg restoredefwwn n=<

adapter number

> The following example restores the IEEE address on adapter number 2.

os

lpcfg restoredefwwn n=2 Broadcom - 38 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.5

4.3.5.1

Boot Code Commands NOTE

Offline utility boot commands apply only to x86 BootBIOs. They do not apply to UEFIBoot.

You must enable boot code before you can issue the setBootDevice and setAltBoot commands. If necessary, use the enableboot command to enable the boot code. See

Section 4.3.5.1, Enabling or Disabling Boot Code (enableboot or disableboot)

, for more information.

To set the boot device with the offline utility, run the following commands in this order: 1.

2.

3.

4.

5.

6.

Use the listboot command to verify that the boot code is present. See

Section 4.3.2.5, Viewing Boot Code Versions (listboot) , for more information.

Example:

os

lpcfg listboot n=1 Sample return for an LPe12000-series adapter with x86 BootBIOS enabled: BootBIOS 1 (enabled): UU11.40A2

Command completed, NO Error Sample return for an LPe12000-series adapter with x86 BootBIOS disabled: BootBIOS 1 (disabled): UU11.40A2

Command completed, NO Error Sample return for an LPe16000-series, LPe31000-series, or LPe32000- series adapter with x86 BootBIOS enabled: Boot Code (enabled) = 11.4.120.0

fc_universal_bios_version = 11.4.120.0

fc_x86_bios_version = 11.4.113.0

fc_efi_bios_version = 11.4.120.0

fc_fcode_version = 11.4.13.0

Command completed, NO Error Sample return for an LPe16000-series, LPe31000-series, or LPe32000-series adapter with x86 BootBIOS disabled: Boot Code (disabled) = 11.4.120.0

fc_universal_bios_version = 11.4.120.0

fc_x86_bios_version = 11.4.113.0

fc_efi_bios_version = 11.4.120.0

fc_fcode_version = 11.4.13.0

Command completed, NO Error Enable the boot code using the enableboot

command. See Section 4.3.5.1, Enabling or Disabling Boot Code (enableboot or disableboot)

, for more information.

Use the setbootdevice

command to configure the boot device. See Section 4.3.5.2, Selecting a Boot Device (setbootdevice) , for more information.

Enable the boot device that was configured in step 3 using the

enablebootdevice command. See

Section 4.3.5.3, Enabling or Disabling Boot Devices (enablebootdevice or disablebootdevice)

, for more information.

Run the readbootdevice command to verify the configuration. See

Section 4.3.2.4, Viewing Boot Device Information (readbootdevice)

, for more information.

Configure the system BIOS so the adapter boot device is the highest in the boot order.

Enabling or Disabling Boot Code (enableboot or disableboot)

This command enables or disables the boot code for the specified adapter.

ATTENTION

Enabling or disabling the boot code on an FC adapter that is being used to boot from SAN is not recommended. The enableboot or Broadcom - 39 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.5.2

disableboot command might cause a loss of connectivity to the SAN and possible loss of data. To run either of these commands on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to enable or disable the boot code to a non-boot-from-SAN host and run the command from there.

If the host with the target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The enableboot or disableboot command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

To enable boot code, type:

os

lpcfg enableboot n=<

adapter number

> i=1

NOTE

i is always set to 1 .

The following example enables boot code on adapter number 6:

os

lpcfg enableboot n=6 i=1 To disable boot code, type:

os

lpcfg disableboot n=<

adapter number

> The following example disables boot code on adapter number 6:

os

lpcfg disableboot n=6

Selecting a Boot Device (setbootdevice)

This command sets the boot device specified by its WWN, LUN, and desired topology.

  Set t=0 for arbitrated loop.

Set t=1 for point-to-point.

The selected device boots when the system reboots.

ATTENTION

Selecting a boot device on an FC adapter that is being used to boot from SAN is not recommended. The setbootdevice command might cause a loss of connectivity to the SAN and possible loss of data. To run the setbootdevice command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to run the setbootdevice command to a non-boot-from-SAN host and run the command from there.

If the host with the setbootdevice target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The setbootdevice command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

The boot code must be enabled before issuing the setbootdevice command.

Broadcom - 40 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.5.3

4.3.5.4

4.3.5.5

To set the boot device, type (all on one line):

os

lpcfg setbootdevice n=<

adapter number

> w0=<

wwpn word 0

> w1=<

wwpn word 1

> l=<

Decimal ID of LUN

> t=<

topology

>

NOTE

Enter the LUN in decimal format.

The following example sets the boot device on adapter number 1, LUN number 46, with a desired topology of arbitrated loop:

os

lpcfg setbootdevice n=1 w0=a1b2c3d4 w1=b946a4e8 l=46 t=0

NOTE

If port login fails after 50 ms, the command is retried once.

Enabling or Disabling Boot Devices (enablebootdevice or disablebootdevice)

After using the setbootdevice command, you can enable or disable the boot device by using the enablebootdevice or disablebootdevice command.

ATTENTION

Enabling or disabling the boot device on an FC adapter that is being used to boot from SAN is not recommended. The enablebootdevice or disablebootdevice command might cause a loss of connectivity to the SAN and possible loss of data. To run either command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to enable or disable the boot device to a non-boot-from-SAN host and run the command from there.

 If the host with the target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. Either command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

To enable the boot device, type:

os

lpcfg enablebootdevice n=<

adapter number

> To disable the boot device, type:

os

lpcfg disablebootdevice n=<

adapter number

>

NOTE

For the change to take effect, perform a system reboot.

Read All Alternative Boot Devices (readaltboot)

This command shows the WWN and LUN numbers in decimal format of all possible alternate boot devices. You can have up to seven alternate boot devices. This command also allows you to identify available alternate boot devices that can be configured using the setaltboot command.

To read all alternate boot devices, type:

os

lpcfg readaltboot n=<

adapter number

>

Setting One or More Alternate Boot Devices (setaltboot)

This command configures alternate boot devices. You can set up to seven alternate boot devices; that is,

index

i can be from 1 to 7.

Broadcom - 41 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.5.6

4.3.6

4.3.6.1

NOTE

The boot code must be enabled before you issue the setaltboot command.

index in this command does not refer to the same index as in the enableboot command.

To set up one or more alternate boot devices, type (all on one line):

os

lpcfg setaltboot n=<

adapter number

> i=<

index

> w0=<

wwpn word 0

> w1=<

wwpn word 1

> l=<

Decimal ID of LUN

> The following example sets the alternate boot device on adapter number 1, LUN number 3:

os

lpcfg setaltboot n=1 i=1 w0=12345678 w1=a842b6ed l=3

Enable or Disable PXE Boot on NIC Devices (networkboot) NOTE

This command is supported only on LPe16202/OCe15100 adapters in NIC mode.

This command allows you to enable or disable PXE boot on NIC devices.

To enable or disable PXE boot on a NIC device, type:

os

lpcfg networkboot n=<

adapter_number

> t=<

type

> s=<

status

> The following example enables PXE boot on adapter 1:

os

lpcfg networkboot n=1 t=pxe s=1 The following example disables PXE boot on adapter 1

os

lpcfg networkboot n=1 t=pxe s=0

Configuration Commands

Configuration commands allow you to update the configuration region of an adapter by name or by number.

Updating Configuration Regions (config)

Two forms of configuration are available:   Configure all adapters of a given adapter name at once Configure a single adapter by its number Valid region numbers range from 0 to 32.

4.3.6.1.1

Update by Name

To update a specified configuration region on all adapters of the same selected name, type:

os

lpcfg config a=<

adapter name

> r=<

region number

> c=<

configuration filename

>

NOTE

The adapter name is the name that appears when you run the listHBA command. For more information on the listHBA

command, see Section 4.3.2.7, Viewing All Adapters in the System (listhba)

.

The following example updates region 6 of all LP12000 adapters with ctplus1.cfl

:

os

lpcfg config a=lpe12000 r=6 c=ctplus1.cfl

Broadcom - 42 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.6.2

4.3.6.3

4.3.7

The following example updates region 17 of all ABC24-FC56 adapters with d:\dfplus1.cfl

:

os

lpcfg config a=ABC24-FC56 r=17 c=d:\dfplus1.cfl

NOTE

The size of the .cfl

file for configuration region update can be up to 2028 bytes.

4.3.6.1.2

Update by Number

To update a specified configuration region for one adapter, type:

os

lpcfg config n=<

adapter number

> r=<

region number

> c=<

configuration filename

> The following example updates region 17 of adapter number 4 with heplus1.cf1

:

os

lpcfg config n=4 r=17 c=heplus1.cfl

The following example updates region 6 of adapter number 2 with d:\dfplus1.cf1

:

os

lpcfg config n=2 r=6 c=d:\dfplus1.cfl

Writing a Semi-Volatile MAC Address on a NIC Device (writesvmac) NOTE

This command is supported only on OEM-specific LPe16202/OCe15100 adapters in NIC mode.

To write a semivolatile MAC address to an adapter, type:

os

lpcfg writesvmac n=<

adapter_number

> <

m=mac_address

> The following example writes the MAC address 0090FA112233 to adapter 1:

os

lpcfg writesvmac n=1 m=0090FA112233

Restoring the Default Semi-Volatile MAC Address on a NIC Device (restoredefsvmac) NOTE

This command is supported only on OEM-specific LPe16202/OCe15100 adapters in NIC mode.

To restore the default semivolatile MAC address to an adapter, type:

os

lpcfg restoredefsvmac n=<

adapter_number

> The following example restores the default MAC address to adapter 1:

os

lpcfg restoredefsvmac n=1

Diagnostic Tests

The following commands let you run diagnostic tests on your adapter.

Broadcom - 43 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.7.1

Running the External Loopback Test (extloopback) NOTE

extloopback is supported only on LPe12000-series adapters.

ATTENTION

Performing an extloopback test on an FC adapter that is being used to boot from SAN is not recommended. The extloopback command might cause a loss of connectivity to the SAN and possible loss of data. To perform an extloopback command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to perform the external loopback test onto a non-boot-from-SAN host and perform the test from there.

If the host with the test target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The extloopback command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

This command runs the external loopback test. You must put a loopback plug in each adapter port to be tested. You can test a specific adapter in the system. Specify the number of times you want the test to repeat, and direct the test response if an error is found.

The option on error choices are:    o=1 stops the test on the first error o=2 ignores three errors and either stops the test on the fourth error, or continues testing the next adapter on the fourth error o=3 ignores errors and continues the test

NOTE

The extloopback command does not support testing all installed adapters using n=all .

To run the external loopback test on an FC adapter, type:

os

lpcfg extloopback n=<

adapter number

> r=<

repeat count

> o=<

option on error

> where:  r = 1 to 4096 To run the external loopback test on an LPe16202/OCe15101 adapter in NIC+FCoE mode, type (all on one line):

os

lpcfg extloopback n=<

adapter number

> p=<

pattern

> c=<

byte count

> r=<

repeat count

>    p = 3 to 8-HEX byte pattern c = 1500 to 8192 r = 1 to 4096 The following example runs the external loopback test 50 times on FC adapter number 1 and stops the test if an error occurs:

os

lpcfg extloopback n=1 r=50 o=1 Broadcom - 44 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.7.2

Running the Internal Loopback Test (intloopback) ATTENTION

Performing an internal loopback test on an FC adapter that is being used to boot from SAN is not recommended. The intloopback command might cause a loss of connectivity to the SAN and possible loss of data. To perform an intloopback command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to perform the internal loopback test onto a non-boot-from-SAN host and perform the test from there.

If the host with the test target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The intloopback command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

This command runs the internal loopback test. You can run the test on a specific adapter in the system. Specify the number of times you want the test to repeat, and direct the test response if an error occurs.

The option on error choices are:    o=1 stops the test on the first error o=2 ignores three errors and either stops the test on the fourth error, or continues testing the next adapter on the fourth error o=3 ignores errors and continues the test

NOTE

intloopback does not support testing all installed adapters using n=all .

Do not use the internal loopback test on Emulex blade adapters.

To run the internal loopback test on an FC adapter, type:

os

lpcfg intloopback n=<

adapter number

> r=<

repeat count

> o=<

option on error

> where:  r = 1 to 4096 To run the internal loopback test on an LPe16202/OCe15100 adapter in NIC+FCoE mode, type (all on one line):

os

lpcfg intloopback n=<

adapter number

> p=<

pattern

> c=<

byte count

> r=<

repeat count

> t=<

type

>     where: p = 3 to 8-HEX byte pattern c = 1500 to 8192 r = 1 to 4096 t = 2 The following example runs the internal loopback test 100 times on FC adapter number 1 and stops the test if an error occurs:

os

lpcfg intloopback n=1 r=100 o=1 Broadcom - 45 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.7.3

4.3.8

Running the PCI Loopback Test (pciloopback) ATTENTION

Performing a PCI loopback test on an FC adapter that is being used to boot from SAN is not recommended. The pciloopback command might cause a loss of connectivity to the SAN and possible loss of data. To perform a pciloopback command on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:   Move the adapter on which you want to perform the PCI loopback test onto a non-boot-from-SAN host and perform the test from there.

If the host with the test target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. The pciloopback command can now be run on the intended target adapter, because it is not being actively used for boot from SAN.

This command runs the PCI loopback test. You can run the test on a specific adapter or on all adapters in the system. Specify the number of times you want the test to repeat, and direct the test response if an error occurs.

   The option on error choices are: o=1 stops the test on the first error o=2 ignores three errors and stops the test on the fourth error o=3 ignores errors and continues the test

NOTE

The pciloopback command supports testing all installed adapters using n=all on LPe12000-series adapters only.

To run the PCI loopback test, type:

os

lpcfg pciloopback n=

adapter number

> r=<

repeat count

> o=<

option on error

> The following example runs the PCI loopback test 100 times on all LPe12000-series adapters in the system and stops the testing if any errors occur.

os

lpcfg pciloopback n=all r=100 o=1

Using Script Files

Use script files to efficiently perform tasks. Script files are common sequences of commands you use when performing tasks.

   You can group commands together and run them using a script file. You can also enter comment lines, which begin with a semicolon. Each line follows the same command syntax as those documented in this manual. Using the offline utility, you can: Run commands entered in a script file. Use the @ command to run the script file.

Run commands multiple times. Add the repeat command as the last line of the script file.

Create a log of test results. Add the logfile command as the first line of the script file.

To run a script file type:

os

lpcfg @<

scriptname.txt

> Broadcom - 46 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.8.1

4.3.8.2

The following example runs the script script1.txt, which resides in the current directory and runs all the commands in that script file.

os

lpcfg @script1.txt

NOTE

To interrupt and stop any script, press

S

on the keyboard.

The following is a sample script file. Each command follows the syntax covered previously. The comment lines begin with a semicolon ( ; ): version screendisplay o=0 ;download a=lpe12000 i=c:\temp\ud201a12.all

;reset n=1 s=0 ;reset n=2 s=0 reset n=all s=0 listboot n=1 enableboot n=1 i=2 ; pciloopback n=1 r=10 o=1 ; pciloopback n=2 r=10 o=2 ; pciloopback n=all r=50 o=3 intloopback n=1 r=10 o=1 intloopback n=2 r=10 o=1 extloopback n=1 r=40 o=3 extloopback n=2 r=40 o=3 ;repeat r=10

Repeating a Series of Commands (repeat)

Enter this command at the end of a script file to repeat a series of commands from the beginning of the script file a specific number of times.

NOTE

To interrupt and stop the repeat command, press

S

on the keyboard.

To repeat the series of commands in the script file, add the following as the last line of the file: repeat r=<

repeat count

> The following example repeats the series of commands in the script file ten times.

repeat r=10

Enabling or Disabling Test Messages on the Screen (screendisplay)

This command enables or disables test message displays on the screen.

  o=0 – Prevents messages from appearing o=1 – Enables messages

NOTE

This command is supported only in script files.

To enable or disable test message displays on the screen, add the following line to the script: screendisplay o=<

display option

> In the following script file example, messages from the version and listhba commands appear in the log file and on the screen. After the screendisplay command is set to 0 , the result messages for all successive commands ( download , listboot , and enableboot ) appear only in the log file, not on the screen.

version listhba Broadcom - 47 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.8.3

screendisplay o=0 download a=lpe12000 i=c:\temp\ud201a12.all

listboot n=2 enableboot n=2 i=1

Updating Nonvolatile WWNN (scriptwwnn) ATTENTION

Running a scriptwwnn command on an FC adapter that is being used to boot from SAN is not recommended. The scriptwwnn command might cause a loss of connectivity to the SAN and possible loss of data. To update the nonvolatile WWNN on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the scriptwwnn command to a non-boot-from-SAN host and run the script from there.

 If the host with the target adapter is also hosting other boot-from SAN-adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now run the script to update the nonvolatile WWNN on the intended target adapter, because it is not being actively used for boot from SAN.

This command reads the WWNN words 0 and 1 from the command line to update the nonvolatile WWNN. You can also include this command in a script file. When the adapter is discovered, the new WWNN value is used. The adapter retains the original WWNN in another region of the firmware.

ATTENTION

Use the scriptwwnn command with caution. If you use the same WWNN on more than one adapter in a fabric, unpredictable results might occur.

To change WWNN words 0 and 1 from the command line, type:

os

lpcfg scriptwwnn n=<

adapter number

> w0=<

wwnn word 0

> w1=<

wwnn word 1

> The following example updates nonvolatile WWNN word 0 and word 1 for adapter number 1:

os

lpcfg scriptwwnn n=1 w0=10000345 w1=B620A1B2

NOTE

Word 0 of WWNN and WWPN names must follow one of the following formats: 1 0 0 0 0

x x x

2

x x x x x x x

3

x x x x x x x

5

x x x x x x x

If the scriptvwwnn command has been used previously, the adapter continues to use that WWNN until you change the WWNN with the restorenvwwn command.

Broadcom - 48 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.8.4

4.3.8.5

Updating Nonvolatile WWPN (scriptwwpn) ATTENTION

Running a scriptwwpn command on an FC adapter that is being used to boot from SAN is not recommended. The scriptwwpn command might cause a loss of connectivity to the SAN and possible loss of data. To update the nonvolatile WWPN on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the scriptwwpn command to a non-boot-from-SAN host and run the script from there.

 If the host with the target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now run the script to update the nonvolatile WWPN on the intended target adapter, because it is not being actively used for boot from SAN.

This command reads WWPN words 0 and 1 from the command line to update the nonvolatile WWPN. You can also include this command in a script file. When it is discovered, the adapter uses the new WWNN value. It does not use the original IEEE address assigned by manufacturing (located in Configuration Region 16 or 32).

ATTENTION

Use the scriptwwpn command with caution. If you use the same WWPN on more than one adapter in a fabric, unpredictable results might occur.

NOTE

If the scriptvwwnn command has been used previously, the adapter continues to use that WWPN until you change the WWPN with the restorenvwwn command.

To change WWPN words 0 and 1 from the command line, type:

os

lpcfg scriptwwpn n=<

adapter number

> w0=<

wwpn word 0

> w1=<

wwpn word 1

> The following example updates the nonvolatile WWPN word 0 word 1 for adapter number 1:

os

lpcfg scriptwwpn n=1 w0=20A2D6B8 w1=C920A1B2

Updating Volatile WWNN (scriptvwwnn) ATTENTION

Running a scriptvwwnn command on an FC adapter that is being used to boot from SAN is not recommended. The scriptvwwnn command might cause a loss of connectivity to the SAN and possible loss of data. To update the volatile WWNN on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the scriptvwwnn command to a non-boot-from-SAN host and run the script from there.

 If the host with the target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now run the script to update the volatile WWNN on the intended target adapter, because it is not being actively used for boot from SAN.

Broadcom - 49 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.8.6

This command reads the WWNN words 0 and 1 from the command line to update the volatile WWNN. The next time the adapter is discovered, it uses this new WWNN. It does not use the original IEEE address assigned by manufacturing (located in Configuration Region 16 or 32), nor does it use the value entered by the writewwn or scriptwwnn commands.

If the adapter does not have firmware that supports the volatile WWN, the following error message appears: Write Volatile Parms Error. Reported Error 48 If this occurs, install firmware that supports the volatile WWN.

NOTE

Word 0 of WWNN and WWPN names must follow one of the following formats: 1 0 0 0 0

x x x

2

x x x x x x x

3

x x x x x x x

5

x x x x x x x

After you issue this command, the volatile WWNN is used by the adapter until the restorenvwwn command is issued or the system is restarted.

ATTENTION

Use the scriptvwwnn command with caution. If you use the same volatile WWNN on more than one adapter in a fabric, unpredictable results might occur.

To change volatile WWNN words 0 and 1 from the command line, type:

os

lpcfg scriptvwwnn n=<

adapter number

> w0=<

wwnn word 0

> w1=<

wwnn word 1

> The following example updates the volatile WWNN word 0 word 1 for adapter number 1:

os

lpcfg scriptvwwnn n=1 w0=20A2D6B8 w1=C920A1B2

Updating Volatile WWPN (scriptvwwpn) ATTENTION

Running a scriptvwwpn command on an FC adapter that is being used to boot from SAN is not recommended. The scriptvwwpn command might cause a loss of connectivity to the SAN and possible loss of data. To update the volatile WWPN on an FC adapter, make sure the adapter is not currently being used to boot from SAN. There are two ways to do this:  Move the adapter on which you want to use the scriptvwwpn command to a non-boot-from-SAN host and run the script from there.

 If the host with the target adapter is also hosting other boot-from-SAN adapters, carry out a boot from SAN using one of the other boot-from-SAN adapters. You can now run the script to update the volatile WWPN on the intended target adapter, because it is not being actively used for boot from SAN.

This command reads the WWPN words 0 and 1 from the command line to update the volatile WWPN. The next time the adapter is discovered, it uses this new WWPN. It does not use the original IEEE address assigned by manufacturing (located in Configuration Region 16 or 32), nor does it use the value entered by the writewwn or scriptwwpn commands.

If the adapter does not have firmware that supports the volatile WWN, the following error message appears: Write Volatile Parms Error. Reported Error 48 Broadcom - 50 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.8.7

4.3.9

4.3.9.1

If this error message appears, install firmware that supports the volatile WWN.

NOTE

Word 0 of WWNN and WWPN names must follow one of the following formats: 1 0 0 0 0

x x x

2

x x x x x x x

3

x x x x x x x

5

x x x x x x x

After you issue this command, the volatile WWNN is used by the adapter until the restorenvwwn command is issued or the system is restarted.

ATTENTION

Use the scriptvwwnn command with caution. If you use the same VWWNN on more than one adapter in a fabric, unpredictable results might occur.

To change VWWPN words 0 and 1 from the command line, type:

os

lpcfg scriptvwwpn n=<

adapter number

> w0=<

wwpn word 0

> w1=<

wwpn word 1

> The following example updates the volatile WWPN word 0 word 1 for adapter number 1:

os

lpcfg scriptvwwpn n=1 w0=20A2D6B8 w1=C920A1B2

Creating a Log (logfile)

This command creates a log file with a specified directory and file name. The default log file is lpcfglog.txt

and is created in the system’s current directory.

NOTE

This command is supported only in script files. Make it the first command in the script.

To create a log file, type the following command in the script file: logfile l=<

filename

> The following example creates a file called lplog.txt

in the d:\ directory: logfile l=d:\log\lplog.txt

Results of all commands are recorded in a log file. Unless otherwise specified by the logfile command, the default log file is lpcfglog.txt

in the current directory.

VLAN Commands

Using the following commands, you can manage the VLAN ID and VLAN priorities on specified adapters.

Reading VLAN Priorities (readvlanprops)

This command shows the NIC function on an adapter's VLAN ID and VLAN Priority for the adapter number specified.

NOTE

readvlanprops is supported only on LPe16202/OCe15100 adapters in NIC+FCoE mode.

To read the VLAN priorities for the adapter specified, type:

os

lpcfg.exe readmac n=<

adapter number

> Broadcom - 51 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 4: LpCfg Utility Command Line Interface Supported Commands

4.3.9.2

4.3.9.3

The following example lists information for adapter number 1:

os

lpcfg.exe readvlanprops n=1 Command: readvlanprops n=1 adapter 1: VLANId : 1024 VLANPriority: 1 Command completed, NO Error

Restoring the Default Values for the VLAN ID and VLAN Priorities (restorevlanprops)

This command restores the adapter's default VLAN ID and VLAN Priority values, which are both set to 0, on the adapter number specified.

NOTE

restoredefvlanprops is supported only on LPe16202/OCe15100 adapters in NIC+FCoE mode..

To restore the VLAN ID and VLAN priorities for the adapter specified, type: >

os

lpcfg.exe restorevlanprops n=<

adapter number

>

Changing the VLAN ID and VLAN Priority on a Specified Adapter’s NIC Function (writevlanprops)

This command lets you change the VLAN ID and VLAN Priority on the specified adapter's NIC function. You can specify the VLAN ID and the VLAN Priority with the following values:   vlan_id – 0 to 4095. A value of 0 disables the VLAN ID.

vlan_priority – 0 to 7.

NOTE

writevlanprops is supported only on LPe16202/OCe15100 adapters in NIC+FCoE mode..

To change the VLAN ID and the VLAN Priority on a specified adapter’s NIC function, type:

os

lpcfg.exe writevlanprops n=<

adapter number

> i=<

vlan_id

> p=<

vlan_priority

> The following example changes the VLAN ID and VLAN Priority for adapter number 1:

os

lpcfg.exe writevlanprops n=1 i=1024 p=1 Command: writevlanprops n=1 i=1024 p=1 adapter 1: Command completed, NO Error Broadcom - 52 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

Chapter 5: Status Messages and Error Codes 5.1

Chapter 5: Status Messages and Error Codes Elxflash Utility Status Messages

Elxflash Utility Status Messages

2 3 4 The Elxflash utility takes a less stringent approach to reporting status messages when used with auto-discovery. An error message is returned only when the Elxflash utility reports a failure during a download or if the firmware and boot directories cannot be located.

Table 2

lists the supported Elxflash utility status messages.

Table 2 Elxflash Status Messages

0

Message Number Message Title

GOOD_ALL_UPGRADES_OK

Message Details

1 5 6 7 8 9 10 19 20 GOOD_NO_UPDATES_NEEDED ERROR_ALL_UPGRADES_FAILED ERROR_SOME_UPGRADES_FAILED ERROR_EMULEX_APPS_COMMAND ERROR_NO_SUPPORTED_HBA_FOUND ERROR_DIRECTORY_NOT_FOUND GOOD_NO_UPGRADES_AVAILABLE ERROR_NOT_ADMIN_USER ERROR_UNSUPPORTED_OS ERROR_UNSUPPORTED_ARCH ERROR_IMAGE_VERSION ERROR_MISSING_DEP Returned if any of the discovered adapters had a successful download performed.

Returned if any of the discovered adapters did not need an update, a downgrade, or a rewrite operation.

This message is never returned during a force firmware or force boot code download operation.

Returned if all attempted downloads failed.

Returned if some of the attempted downloads failed.

Returned if Elxflash cannot run an external executable, such as

os

lpcfg (elxflashOffline) Returned if no supported adapters are found.

Returned if the firmware or firmware boot or root of the package directory.

boot directories are missing. Depending on the operation, auto-discovery expects the directories to exist as subdirectories in the Returned if none of the discovered adapters had a matching image in the firmware or boot directories. In this case only, a matching image is an image that the adapter accepts regardless of the download operation being performed.

Returned when you attempt to run the executable file and do not have administrator (Windows) or root (Linux) privileges.

Used by the Exlflash Stand-alone execution scripts. Returned when the scripts are run on an unsupported operating system.

Used by the Exlflash Stand-alone execution scripts. Returned when the scripts are run on an unsupported architecture.

An error occurred when decoding the image version. The image file has an invalid extension, or Elxflash was unable to decode the image file's version.

NOTE

This is returned only when using the /iv=<

image_version

> switch.

Returned when a missing dependency is detected.

Broadcom - 53 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

5.2

LpCfg Error Codes

Table 3

lists the supported LpCfg error codes.

Table 3 LpCfg Error Codes

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 32 33 34 35 36 24 25 26 27 28 29 30 31

Error Code Description

No error Invalid adapter number Mailbox command error No valid boot (BIOS) code found Open file error Invalid configuration region Invalid adapter name Download error Invalid boot code index Link not up for external loopback test Link not up for internal loopback test Invalid jumper selection (in jumper command) Invalid alternate configuration region (in jumper command) PCI loopback test fails Adapter reset error Read configuration region error No VPD information available No command in command line Open log file error Read wakeup parameters error Update wakeup parameters error Incorrect test parameters Stopped by user Internal loopback test fails External loopback test fails Error exists after four retries Invalid command Incorrect syntax Command supported only in script files Read_rev error Dump configuration region error Read file error Short file error Read NVPARMS error Write NVPARMS error Command does not support all adapters Invalid LUN Broadcom - 54 Chapter 5: Status Messages and Error Codes LpCfg Error Codes

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017

Table 3 LpCfg Error Codes (Continued)

37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 70 71 72 73 74 75 76 77 53 54 55 56 57 58 59 60 62 63 64 65 66 67 68 69

Error Code

No boot (BIOS) code enabled Update configuration region error No boot (BIOS) found Dump memory error Update EROM error Delete load entry error Write WWN error Not supported in script files No Emulex adapter found Invalid alternate boot device index Cannot restart adapter Write volatile parameters error POST test error Incorrect symbols Invalid length Invalid topology No event log Read event log Invalid input value No libdfc library Non-numeric input No valid WWN Region cleanup Region initialization Unable to allocate memory DFC_InitDiagEnv error DFC_ReadPciCfg error No driver installed No valid driver Not valid adapter type Not valid image Long file error Incompatible image Not supported MILI service not started Script not supported MILI not started No NIC adapter Personality information Personality change Broadcom - 55 -

Description

Chapter 5: Status Messages and Error Codes LpCfg Error Codes

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 5: Status Messages and Error Codes LpCfg Error Codes

Table 3 LpCfg Error Codes (Continued)

78 79 80 83 87 88 89

Error Code

90 141 200

Description

Administrator rights error SLI-4 management error Reboot required Application is missing one or more dependencies.

The system must be rebooted to activate the new firmware image and the image must be downloaded again.

Duplicate MAC address Download failed due to missing digital signature. Please contact customer support for additional help. Download failed on adapter Stat 89.

Download failed due to invalid firmware digital signature. Please contact customer support for additional help. Download failed on adapter Stat 90.

General error from MILI General error Broadcom - 56 -

Emulex Elxflash and LpCfg Utilities for LightPulse Adapters User Guide September 6, 2017 Chapter 6: Troubleshooting Unsupported Driver

Chapter 6: Troubleshooting

When using Elxflash, some commands take precedence over others. For instance, the force firmware ( /ff ), force boot ( /fb ), and force firmware and boot code ( /f ) switches take precedence over the /downgrade , /update , and /rewrite switches. If /ff , /fb , or /f are used, the /downgrade , /update , and /rewrite switches are ignored.

The following examples illustrate this behavior:       ./elxflash /ff /update

/update is ignored.

Performs a force firmware operation on all installed and supported adapters.

./elxflash /fb /update

/update is ignored.

Performs a force boot code operation on all installed and supported adapters.

./elxflash /ff /downgrade

/downgrade is ignored

Performs a force firmware operation on all installed and supported adapters.

/elxflash /fb /downgrade

/downgrade is ignored.

Performs a force boot code operation on all installed and supported adapters.

./elxflash /ff /rewrite

/rewrite is ignored

Performs a force firmware operation on all installed and supported adapters.

./elxflash /fb /rewrite

/rewrite is ignored.

Performs a force boot code operation on all installed and supported adapters.

6.1

6.2

Unsupported Driver

The Elxflash utility reports an error similar to the following if an unsupported driver is installed on the system: elxflash: no supported Emulex HBA's found - Return Code=1 If an error similar to this example occurs, verify that the correct version of the driver is installed. For supported adapters, and supported versions of operating systems and platforms, go to http://www.broadcom.com

.

Updating Adapters without Boot Code

The Elxflash utility reports an adapter's boot code version as NONE when the adapter does not have boot code installed. The utility does not update, downgrade, or rewrite the boot area if boot code is not present, but firmware will still be updated or downgraded without boot code. You can force a boot code download using auto-discovery or the fwmatrix.txt

file.

Broadcom - 57 -

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

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

Download PDF

advertisement