Dell Brocade Adapters Quick Reference Guide Installation And Manual

2014-11-13

: Dell Dell-Brocade-Adapters-Quick-Reference-Guide-116808 dell-brocade-adapters-quick-reference-guide-116808 dell pdf

Open the PDF directly: View PDF .
Page Count: 272 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Contents
About This Document
Product Overview
Hardware Installation
Software Installation
Boot Code
Specifications
Adapter Configuration
MIB Reference
- In this appendix
List of Acronyms
Index

53-1002144-01

5 August 2011

Brocade Adapters

Installation and Reference Manual

Supporting CNA models 1741, 1020, 1010, 1007

Supporting HBA models 825, 815, 804, 425, 415

Supporting Fabric Adapter model 1860

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and

Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks,

MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other

countries. Other brands, products, or service names mentioned are or may be trademarks or service marks of their respective

owners.

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and

Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks,

MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other

countries. Other brands, products, or service names mentioned are or may be trademarks or service marks of their respective

owners.

The product described by this document may contain “open source” software covered by the GNU General Public License or other

open source license agreements. To find-out which open source software is included in Brocade products, view the licensing

terms applicable to the open source software, and obtain a copy of the programming source code, please visit

http://.brocade.com/support/oscd.

Brocade Communications Systems, Incorporated

Document History

Corporate and Latin American Headquarters

Brocade Communications Systems, Inc.

130 Holger Way

San Jose, CA 95134

Tel: 1-408-333-8000

Fax: 1-408-333-8101

E-mail: info@brocade.com

Asia-Pacific Headquarters

Brocade Communications Systems China HK, Ltd.

No. 1 Guanghua Road

Chao Yang District

Units 2718 and 2818

Beijing 100020, China

Tel: +8610 6588 8888

Fax: +8610 6588 9999

E-mail: china-info@brocade.com

European Headquarters

Brocade Communications Switzerland Sàrl

Centre Swissair

Tour B - 4ème étage

29, Route de l'Aéroport

Case Postale 105

CH-1215 Genève 15

Switzerland

Tel: +41 22 799 5640

Fax: +41 22 799 5641

E-mail: emea-info@brocade.com

Asia-Pacific Headquarters

Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)

Citic Plaza

No. 233 Tian He Road North

Unit 1308 – 13th Floor

Guangzhou, China

Tel: +8620 3891 2000

Fax: +8620 3891 2111

E-mail: china-info@brocade.com

Title Publication number Summary of changes Date

Brocade Adapters Installation and

Reference Manual

53-1001254-01 New document June 2009

Brocade Adapters Installation and

Reference Manual

53-1001254-02 Updates for Release 2.1 September 2009

Brocade Adapters Installation and

Reference Manual

53-1001254-03 Update for Release 2.2 May 2010

Brocade Adapters Installation and

Reference Manual

53-1001581-01 Updates to support Release

2.1.1 and the Brocade 804

adapter.

June 2010

Brocade Adapters Installation and

Reference Manual

53-1001254-04 Update for Brocade 1007

adapter

September 2010

Brocade Adapters Installation and

Reference Manual

53-1001926-01 Updates to support Release

2.3

October 2010

Brocade Adapters Installation and

Reference Manual

53-1001926-02 Updates to support Brocade

1741 adapter

November 2010

Brocade Adapters Installation and

Reference Manual

53-1002144-01 Updates to support Adapter

release 3.0 and Brocade

1860 adapter

August 2011

Title Publication number Summary of changes Date

Brocade Adapters Installation and Reference Manual v

53-1002144-01

Contents

About This Document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

How to use this document for installing adapters . . . . . . . . . . . xii

Supported adapter hardware and software . . . . . . . . . . . . . . . . . . . xiii

Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

CNAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Fabric OS and switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Host operating system support. . . . . . . . . . . . . . . . . . . . . . . . . . xv

Host operating system support for adapter drivers . . . . . . . . . . . . . xv

Fibre Channel support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

FCoE support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Ethernet support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Hypervisor support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Host operating system support for HCM . . . . . . . . . . . . . . . . . . . . . .xvii

What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx

Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx

Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Other industry resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Providing details for support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxii

Support Save overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Initiating Support Save through HCM . . . . . . . . . . . . . . . . . . . . xxvi

Initiating Support Save through BCU commands . . . . . . . . . . xxvi

Initiating Support Save through the internet browser . . . . . . . xxvi

Initiating Support Save through a port crash event. . . . . . . . .xxvii

Support Save differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvii

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvii

Chapter 1 Product Overview

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

vi Brocade Adapters Installation and Reference Manual

53-1002144-01

Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

AnyIO technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

WoL and SoL limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Host bus adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Stand-up models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Mezzanine models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Adapter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

FCoE features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Data Center Bridging and Ethernet features . . . . . . . . . . . . . . .22

HBA features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adapter management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

General adapter management . . . . . . . . . . . . . . . . . . . . . . . . . .32

Fabric Adapter management. . . . . . . . . . . . . . . . . . . . . . . . . . . .33

CNA management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

NIC Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

HBA management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Fabric Adapter management. . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Adapter software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Driver packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Management utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Host Connectivity Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Boot code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

CIM Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Adapter event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Software installation and driver packages. . . . . . . . . . . . . . . . .43

Software installation options . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Items shipped with your adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Boot installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Downloading software and publications . . . . . . . . . . . . . . . . . . . . . . 52

Using BCU commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Chapter 2 Hardware Installation

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

ESD precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Brocade Adapters Installation and Reference Manual vii

53-1002144-01

Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

What you need for installation . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Installing an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Connecting an adapter to a switch or direct-attached

storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Removing and installing SFP transceivers . . . . . . . . . . . . . . . . .59

Replacing an adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Brocade 804 HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Brocade 1007 CNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Brocade 1741 CNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter 3 Software Installation

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Installation notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Using the Brocade Adapter Software Installer . . . . . . . . . . . . . . . . .68

Using the GUI-based installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Software installation using Software Installer commands . . . . 76

Software removal using Adapter Software Uninstaller . . . . . . . 83

Software upgrade using Adapter Software Installer . . . . . . . . . 87

Software downgrade using Adapter Software Installer . . . . . . . 88

Installer log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Using software installation scripts and system commands. . . . . . . 89

Software installation and removal notes . . . . . . . . . . . . . . . . . .89

Driver installation and removal on Windows systems. . . . . . . . 91

Driver installation and removal on Linux systems . . . . . . . . . . .95

Driver installation and removal on Solaris systems . . . . . . . . . 97

Driver installation and removal on VMware systems . . . . . . . .99

Confirming driver package installation . . . . . . . . . . . . . . . . . . . . . .103

Confirming driver installation with HCM. . . . . . . . . . . . . . . . . .104

Confirming driver installation with Windows tools. . . . . . . . . .104

Confirming driver installation with Solaris tools . . . . . . . . . . .106

Confirming driver installation with VMware tools . . . . . . . . . .107

Verifying adapter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Installing SNMP subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Windows systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Linux systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Updating drivers with HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Installing HCM to a host from the HCM Agent. . . . . . . . . . . . . . . . .112

HCM Agent operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Managing the HCM Agent on Linux and VMware systems . . .112

Managing the HCM Agent on Solaris systems . . . . . . . . . . . . .113

Managing the HCM Agent on Windows systems . . . . . . . . . . .114

viii Brocade Adapters Installation and Reference Manual

53-1002144-01

HCM configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Backing up configuration data . . . . . . . . . . . . . . . . . . . . . . . . .115

Restoring configuration data. . . . . . . . . . . . . . . . . . . . . . . . . . .115

Setting IP address and subnet mask on CNAs . . . . . . . . . . . . . . . .115

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

VMware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Chapter 4 Boot Code

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Boot code updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Updating boot code with HCM. . . . . . . . . . . . . . . . . . . . . . . . . .119

Updating boot code with BCU commands . . . . . . . . . . . . . . . .120

Network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Brocade BIOS support for network boot. . . . . . . . . . . . . . . . . .121

Host system requirements for network boot . . . . . . . . . . . . . .122

Driver support for network boot . . . . . . . . . . . . . . . . . . . . . . . .122

Configuring network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Brocade BIOS support for boot over SAN . . . . . . . . . . . . . . . . .128

Brocade UEFI support for boot over SAN . . . . . . . . . . . . . . . . .129

Host system requirements for boot over SAN . . . . . . . . . . . . .130

Storage system requirements for boot over SAN. . . . . . . . . . .130

Disabling N_Port trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Configuring boot over SAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Operating system and driver installation on boot LUNs . . . . .148

Installing the full driver package on boot LUNs . . . . . . . . . . . .162

Fabric-based boot LUN discovery. . . . . . . . . . . . . . . . . . . . . . . . . . .163

Configuring fabric-based boot LUN discovery (Brocade

fabrics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Configuring fabric-based boot LUN discovery (Cisco

fabrics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Boot systems over SAN without operating system or local drive . .167

Using a LiveCD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Creating a WinPE image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Updating Windows driver on adapter used for boot over SAN . . . .170

Chapter 5 Specifications

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

PCI Express interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Adapter LED operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Environmental and power requirements . . . . . . . . . . . . . . . . .178

Brocade Adapters Installation and Reference Manual ix

53-1002144-01

Converged Network Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

PCI Express interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

Cabling (stand-up adapters) . . . . . . . . . . . . . . . . . . . . . . . . . . .183

Adapter LED operation (stand-up adapters) . . . . . . . . . . . . . .184

Environmental and power requirements . . . . . . . . . . . . . . . . .185

Host Bus Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

PCI Express interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Cabling (stand-up adapters) . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Adapter LED operation (stand-up adapters) . . . . . . . . . . . . . .191

Environmental and power requirements . . . . . . . . . . . . . . . . .192

Fibre Channel standards compliance . . . . . . . . . . . . . . . . . . . . . . .192

Regulatory compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Appendix A Adapter Configuration

In this appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Storage instance-specific persistent parameters . . . . . . . . . . . . . .203

Managing instance-specific persistent parameters . . . . . . . .205

Storage driver-level parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Linux and VMware driver configuration parameters . . . . . . . .206

Windows driver configuration parameters . . . . . . . . . . . . . . . .208

Solaris driver configuration parameters. . . . . . . . . . . . . . . . . .210

Network driver parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

VMware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

Enabling jumbo frames for Solaris . . . . . . . . . . . . . . . . . . . . . .224

Appendix B MIB Reference

In this appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Appendix C List of Acronyms

Index

xBrocade Adapters Installation and Reference Manual

53-1002144-01

Brocade Adapters Installation and Reference Manual xi

53-1002144-01

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

•Supported adapter hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . xiii

•Host operating system support for adapter drivers . . . . . . . . . . . . . . . . . . . xv

•Host operating system support for HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

•Providing details for support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

How this document is organized

This manual provides installation and reference information on Brocade host bus adapters (HBAs),

converged network adapters (CNAs), and Fabric Adapters. It is organized to help you find the

information that you want as quickly and easily as possible.

The document contains the following components:

•Chapter 1, “Product Overview,” provides a detailed product overview and description.

Information on adapter hardware and software compatibility is also included.

•Chapter 2, “Hardware Installation,” provides procedures to install adapter hardware and

connect to the fabric or switch. Also included are procedures to verify hardware and software

installation.

•Chapter 3, “Software Installation,” provides procedures to install software, such as the

Brocade Host Connectivity Manager (HCM) and driver packages. Also included are instructions

to verify software and hardware installation. Use this chapter to install software on the host

system where you have installed the adapter.

•Chapter 4, “Boot Code,” describes host boot support available on the adapter and provides an

introduction to boot over SAN. It also includes procedures to update adapter boot code,

configure boot over SAN, and configure fabric-based boot over SAN. Use this chapter when

configuring a host to boot its operating system from a boot device located somewhere on the

SAN instead of the host’s local disk or direct-attached storage.

•Chapter 5 “Specifications,” includes details on adapter physical characteristics, LED operation,

environmental requirements, and power requirements. Also included are Fibre Channel

standards, regulatory, and safety compliancy information.

xii Brocade Adapters Installation and Reference Manual

53-1002144-01

•Appendix A, “Adapter Configuration,” is optional for expert network administrators, who need to

modify values for adapter instance-specific persistent and driver-level configuration

parameters.

•Appendix B, “List of Acronyms,” provides a list of acronyms used in this publication and their

definitions.

•Appendix C, “MIB Reference,” provides information on the MIB groups and objects that support

the Simple Network Management Protocol (SNMP) for CNA adapters and Fabric Adapter ports

configured in CNA mode.

How to use this document for installing adapters

Figure 1 illustrates a flowchart of how to use chapters in this manual to install and configure

adapters.

FIGURE 1 Installing adapters using this document

· Install adapter drivers, utilities, and other

software in host system.

· Verify software and hardware installation.

· Configure HCM agent operation as necessary.

· Configure network addressing (CNA only).

Chapter 3

Appendix A

· Configure boot over SAN on BIOS- or UEFI-

based systems.

· Install operating system, adapter drivers,

utilities, and other software on boot devices.

· Configure fabric-based boot LUN discovery

if needed.

· Boot host systems without operating systems

or remote drives if needed.

Chapter 4

Chapter 2

Booting from

external

boot device?

Install adapter hardware in host system,

connect to switch, and verify installation.

NoYe s

Optional instructions for expert users.

Configure instance-specific and driver-level

parameters to control adapter operation.

Chapter 1

Determine host system compatibility,

required hardware, and required

software packages for installation.

Start

Brocade Adapters Installation and Reference Manual xiii

53-1002144-01

Supported adapter hardware and software

This section provides an overview of Brocade adapter supported hardware and software.

Fabric Adapters

Brocade Fabric Adapter ports can be configured for CNA, NIC, or HBA operation using Brocade

Command Utility (BCU) commands. Ports configured in CNA or NIC mode require appropriate

10GbE SFPs or direct-attached SFP+ with copper cables and operate at a 10 Gbps maximum rate.

Those configured in HBA mode require appropriate 8 or 16 Gbps Fibre Channel SFPs and operate

at an 8 or 16 Gbps maximum rate depending on the installed small form factor pluggable

transceiver (SFP+).

The Brocade 1860 is a single or dual-port stand-up adapter that ships in the following

configurations.

•Single-port model - 16 Gbps Fibre Channel SFP, 10GbE SFP, or no optics.

•Dual-port model - Two 16 Gbps Fibre Channel, two 10GbE SFPs, or no optics).

Note that although adapters may ship with specific optics (or no optics) installed, you can replace

with compatible optics, such as 8 Gbps FC SFPs, long-wave SFPs, and SFP+ direct-attach copper

cables. Refer to “Hardware compatibility” on page 4 for more information.

CNAs

The following Fibre Channel over Ethernet (FCoE) CNAs are supported:

•Brocade 1007. Dual-port mezzanine CNA with a per-port maximum of 10 Gbps. This is an IBM

compact form factor horizontal (CFFh) mezzanine-type adapter that installs on supported

server blades.

•Brocade 1010. Single-port stand-up CNA with a per-port maximum of 10 Gbps.

•Brocade 1020. Dual-port stand-up CNA with a per-port maximum of 10 Gbps.

•Brocade 1741. Dual-port mezzanine card CNA with a per-port maximum of 10 Gbps. This is a

small-form-factor (SFF) mezzanine card that mounts in a Dell blade server.

NOTE

Install only Brocade-branded small form factor pluggables (SFPs) in stand-up CNAs. Mezzanine CNAs

do not have SFPs and external port connectors, but utilize internal ports and connections to switch

and I/O modules installed in the blade system enclosure.

HBAs

The following Fibre Channel host bus adapters (HBAs) are supported:

•Brocade 415. Single-port stand-up HBA with a per-port maximum of 4 Gbps using a 4 Gbps

SFP.

•Brocade 425. Dual-port stand-up HBA with a per-port maximum of 4 Gbps using a 4 Gbps SFP.

•Brocade 804. Dual-port mezzanine HBA with a per-port maximum of 8 Gbps. This HBA installs

on Hewlett Packard blade servers that install in supported blade system enclosures.

xiv Brocade Adapters Installation and Reference Manual

53-1002144-01

•Brocade 815. Single-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps

SFP+.

•Brocade 825. Dual-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps

SFP+.

NOTE

Install only Brocade-branded small form factor pluggables (SFPs) in stand-up HBAs. Mezzanine

HBAs do not have SFPs and external port connectors, but utilize internal ports and connections to

switch and I/O modules installed in the blade system enclosure.

Note the following about HBA support

•This publication only supports the HBA models listed under “HBAs” on page xiv and does not

provide information about the Brocade 410 and 420 Fibre Channel HBAs, also known as the

Brocade 400 Fibre Channel HBAs.

•Although you can install an 8 Gbps SFP+ into a Brocade 415 or 425 HBA, only 4 Gbps

maximum port speed is possible.

Fabric OS and switch support

Brocade adapters support Brocade Fabric OS and switches.

Fabric Adapters

Support for Fabric Adapter ports depend on the following mode (CNA, HBA, or NIC) in which they

are configured:

•Ports on Fabric Adapters configured in CNA mode can connect to Fibre Channel SANs and

Ethernet data networks through a compatible FCoE switch. These ports can also connect to

standard Ethernet LAN switch. For a current list of compatible switches, refer to the latest

interoperability matrices on the adapters website at www.brocade.com/adapters.

•Ports configured in HBA mode support Fabric OS and connect to SANs through fabric switches

or connect directly to Fibre Channel storage arrays. For a current list of compatible switches,

refer to the latest interoperability matrices on the adapters website at

www.brocade.com/adapters.

•Ports configured in NIC mode fully support the Ethernet protocol and connect directly to the

Ethernet LAN.

CNAs

Brocade CNAs must connect to Fibre Channel SANs and Ethernet data networks through a

compatible FCoE switch. For a current list of compatible switches, refer to the latest interoperability

matrices on the adapters website at www.brocade.com/adapters.

HBAs

Brocade HBAs connect to Fibre Channel SANs through compatible fabric switches or connect

directly to Fibre Channel storage arrays. For a current list of compatible switches, refer to the latest

interoperability matrices on the adapters website at www.brocade.com/adapters.

Brocade Adapters Installation and Reference Manual xv

53-1002144-01

Host operating system support

Refer to “Host operating system support for adapter drivers” on page xv for information on

operating systems that support the Brocade Host Connectivity Manager (HCM), Brocade Command

Line Utility (BCU), and adapter drivers.

Host operating system support for adapter drivers

This section lists operating system support for all models of the following types of Brocade

adapters:

•Fabric Adapters - Refer to the following subsections depending on your port mode and SFP

configurations:

-“FCoE support” on page xvi and “Ethernet support” on page xvi for ports configured in CNA

mode.

-“Fibre Channel support” on page xv, for ports configured in HBA mode.

-“Ethernet support” on page xvi for ports configured in NIC mode.

•CNAs- Refer to the following subsections:

-“FCoE support” on page xvi

-“Ethernet support” on page xvi.

•HBAs - Refer to “Fibre Channel support” on page xv.

NOTE

Specific operating system release levels, service pack levels, and other patch requirements are

detailed in the current adapter release notes.

NOTE

Also refer to the latest Brocade interoperability matrices on the Brocade website at

www.brocade.com/adapters for a list of supported host systems and operating systems.

Fibre Channel support

The following lists operating systems that support Fibre Channel operation for HBAs and for Fabric

Adapter ports configured in HBA mode:

•Windows 2003 R2/SP2 (x86 and x64)

•Windows Server 2008 (Longhorn) (x86 and x64)

•Windows Server 2008 R2/SP1 (x64)

•Microsoft Hyper V for Windows 2008 x86, x64

•Windows 7 (x86 and x64)

•Windows Server Core for Windows 2008 (x86 and x64)

•Microsoft WinPE 3.0 for Windows 2008 (x86 and x64)

•Linux RHEL4.9, 5.5, 5.6, 6.0, 6.1

•Linux SLES 10 and 11 (x86 and x64)

xvi Brocade Adapters Installation and Reference Manual

53-1002144-01

•Solaris 10 (x86, x64, and SPARC)

NOTE

Solaris is not supported on Brocade 804 or 1007 adapters.

•VMware ESX Server 4.0, 4.1, 5.0 (x64)

NOTE

Drivers and BCU are supported on the VMware ESX platforms. HCM is supported only on the

guest system on VMware.

•Oracle Enterprise Linux (OEL) 5.6, 6.0 (x86 and x64), Oracle VM 3.0

FCoE support

The following lists operating systems that support FCoE operation for Brocade CNAs and Fabric

Adaptor ports configured in CNA mode:

•Windows Server 2008 (x86 and x64)

•Windows Server 2008 R2/SP1 (x64)

•Microsoft Hyper V for Windows 2008 x86, x64

•Windows 7 (x86 and x64)

•Windows Server Core for Windows 2008 (x86 and x64)

•Microsoft WinPE 3.0 for Windows 2008 (x86 and x64)

•Linux RHEL 4.9, 5.5, 5.6, 6.0, 6.1 (x86 and x64)

•Linux SLES 10 and 11 (x86 and x64)

•Solaris 10 (x86, x64, and SPARC)

NOTE

Solaris is not supported on Brocade 804 or 1007 adapters.

•VMware ESX Server 4.0, 4.1, 5.0 (x64)

NOTE

Drivers and BCU are supported on the VMware ESX platforms. HCM is supported only on the

guest system on VMware.

•Oracle Enterprise Linux (OEL) 5.6, 6.0 (x86 and x64)0

Ethernet support

The following lists operating systems that support Ethernet operation for Brocade CNAs and Fabric

Adaptor ports configured in CNA or NIC modes:

•Windows Server 2008 (x86 and x64)

•Windows 2008 R2/SP1 (x64)

•Windows Server Core for Windows 2008 (x86 and x64)

•Windows 7 (x86 and x64)

•Microsoft WinPE 3.0 for Windows 2008 (x86 and x64)

Brocade Adapters Installation and Reference Manual xvii

53-1002144-01

•Linux RHEL 4.9, 5.5, 5.6, 6.0, 6.1 (x86 and x64)

•Linux SLES 10 and 11 (x86 and x64)

•Solaris 10 (x86, x64, and SPARC)

NOTE

Solaris is not supported on Brocade 804 or 1007 adapters.

•Xen Hypervisor (x86 and x64)

Refer to “Hypervisor support” on page xvii.

•VMware ESX Server 4.0, 4.1, and 5.0 (x64)

NOTE

Drivers and BCU are supported on the VMware ESX platforms. HCM is supported only on the

guest system on VMware. Network drivers are not supported on IA-64 systems.

•Oracle Enterprise Linux (OEL) 5.6, 6.0 (x86 and x64)

Hypervisor support

The following lists operating systems that support hypervisor operation for Brocade adapters:

•Windows Server 2008 Hyper-V (x64)

•Linux RHEVH 6.x (x64)

•Linux XEN (x86 and x64)

•Linux KVM (x64)

•VMware ESX 4.0, 4.1, and 5.0 (x64)

•Oracle VM 3.0 (x64)

•Citrix XenServer 6.0 (x64)

Host operating system support for HCM

The following operating systems support HCM management for adapters.

•Windows Server 2008 (x86 and x64)

•Windows Server 2008 R2/SP1 (x86 and x64)

•Windows SBS 2011 (x64)

•Windows XP

•Windows Vista

•Windows 7 SP1 (x86 and x64)

•Linux 5.5, 5.6, 6.0, 6.1 (x86 and x64)

NOTE

HCM is a 32-bit application. To use HCM on Linux RHEL 6.0 x64 systems, you must install the

x32-compatible libraries because they are not installed by default.

•Linux SLES 10 and 11 (x86 and x64)

xviii Brocade Adapters Installation and Reference Manual

53-1002144-01

•Solaris 11, except Open Solaris (x86, x64, and SPARC)

•VMware ESX Server 4.0, 4.1, 5.0 (x64)

NOTE

HCM is not supported in ESXi systems.

NOTE

HCM is supported only on the guest operating system for VMware.

•Oracle Enterprise Linux (OEL) 5.6, 6.0 (x86 and x64)

NOTE

Specific operating system service patch levels and other patch requirements are detailed in the

current release notes for your adapter software version.

What’s new in this document

This document adds details on adapter software release 3.0 and the Brocade 1860 Fabric Adapter.

For further information about new features not covered in this document and documentation

updates, refer to the release notes for your adapter software version.

Document conventions

This section describes text formatting conventions and important notice formats used in this

document.

Text formatting

The narrative-text formatting conventions that are used are as follows:

bold text Identifies command names

Identifies the names of user-manipulated GUI elements

Identifies keywords and operands

Identifies text to enter at the GUI or CLI

italic text Provides emphasis

Identifies variables

Identifies paths and Internet addresses

Identifies document titles

code text Identifies CLI output

Identifies command syntax examples

For readability, command names in the narrative portions of this guide are presented in mixed

lettercase: for example, switchShow. In actual examples, command lettercase is often all

lowercase.

Brocade Adapters Installation and Reference Manual xix

53-1002144-01

Command syntax conventions

Command syntax in this manual follows these conventions:

Command examples

This book describes how to perform configuration tasks using the Fabric OS command line

interface and the BCU interface, but does not describe the commands in detail. For complete

descriptions of all commands, including syntax, operand description, and sample output, see the

Brocade Fabric OS Command Reference Manual and Brocade Adapters Administrator’s Guide.

Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of

increasing severity of potential hazards.

NOTE

A note provides a tip, guidance, or advice, emphasizes important information, or provides a

reference to related information.

ATTENTION

An Attention statement indicates potential damage to hardware or data.

CAUTION

A Caution statement alerts you to situations that can be potentially hazardous to you or cause

damage to hardware, firmware, software, or data.

DANGER

A Danger statement indicates conditions or situations that can be potentially lethal or extremely

hazardous to you. Safety labels are also attached directly to products to warn of these conditions

or situations.

command Commands are printed in bold.

--option, option Command options are printed in bold.

-argument, arg Arguments.

[ ] Optional element.

variable Variables are printed in italics. In the help pages, values are underlined or

enclosed in angled brackets < >.

... Repeat the previous element, for example “member[;member...]”

value Fixed values following arguments are printed in plain font. For example,

--show WWN

| Boolean. Elements are exclusive. Example: --show -mode egress | ingress

xx Brocade Adapters Installation and Reference Manual

53-1002144-01

Key terms

For definitions specific to Brocade and Fibre Channel, see the technical glossaries by logging into

http://my.brocade.com.

For definitions specific to this document, see Appendix C, “List of Acronyms”.

For definitions of SAN-specific terms, visit the Storage Networking Industry Association online

dictionary at:

http://www.snia.org/education/dictionary

Notice to the reader

This document may contain references to the trademarks of the following corporations. These

trademarks are the properties of their respective companies and corporations.

These references are made for informational purposes only.

Additional information

This section lists additional Brocade and industry-specific documentation that you might find

helpful.

Brocade resources

To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID

and password. A variety of resources for Brocade products is available.

Corporation Referenced Trademarks and Products

Microsoft Corporation Windows, Windows Server 2003, Windows Server 2008, Vista,

XP, PE for Windows, Hyper V for Windows, Windows Automated

Installation Kit (WAIK), and Windows 7

Oracle Corporation Solaris

Red Hat Inc. Red Hat Enterprise Linux (RHEL)

Novell, Inc. SUSE Linux Enterprise Server (SLES)

VMware Inc. ESX Server

SPARC International, Inc. SPARC

Hewlett Packard Corp. BladeSystem

IBM BladeCenter

Dell PowerEdge

Brocade Adapters Installation and Reference Manual xxi

53-1002144-01

Adapters

For adapter resources, such as product information, software, firmware, and documentation, visit

the adapters website www.brocade.com/adapters.

For additional information on Brocade adapters, refer to the following publications:

•The Brocade Quick Installation Guide (provided with your adapter model).

•Brocade Adapters Troubleshooting Guide

•Brocade Adapters Administrator’s Guide

•CIM Provider for Brocade Adapters Installation Guide

FCoE Switch

For information on the Brocade FCoE Switch for connecting stand-up CNAs and Fabric Adapter

ports configured in CNA mode, refer to the following publications:

•Brocade 8000 Hardware Reference Manual

•WebTools Administrator’s Guide

•EZSwitchSetup Administrator’s Guide

•Fabric OS Command Reference Manual

Blade servers and blade system enclosure components

The Brocade mezzanine card adapters are compatible with blade servers, switch modules,

interconnect modules, I/O modules, and other components that install in supported blade system

enclosures. For compatibility information, visit the compatible blade server and blade system

enclosure manufacturer’s website. Also refer to “Hardware compatibility” on page 10.

SAN information

White papers, online demonstrations, and data sheets are available through the Brocade website

at:

http://www.brocade.com/products-solutions/products/index.page

For additional Brocade documentation, visit the Brocade website:

http://www.brocade.com

Other industry resources

For additional resource information, visit the Technical Committee T11 website. This website

provides interface standards for high-performance and mass storage applications for Fibre

Channel, storage management, and other applications:

http://www.t11.org

For information about the Fibre Channel industry, visit the Fibre Channel Industry Association

website:

http://www.fibrechannel.org

xxii Brocade Adapters Installation and Reference Manual

53-1002144-01

Providing details for support

Contact your Brocade adapter support supplier for hardware, firmware, and software support,

including product repairs and part ordering. Provide the following information:

1. General information:

•Brocade adapter model number.

•Host operating system version.

•Software name and software version, if applicable.

•syslog message logs

•Support Save output

To expedite your support call, use the Support Save feature to collect debug information

from the driver, internal libraries, and firmware. You can save valuable information to your

local file system and send it to support personnel for further investigation. For details on

using this feature, refer to “Support Save overview” on page xxiv.

•Detailed description of the problem, including the switch or fabric behavior immediately

following the problem, and specific questions.

•Description of any troubleshooting steps already performed and the results.

2. Adapter serial number:

The adapter serial number and corresponding bar code are provided on the serial number

label illustrated below. This label is located on the adapter card.

You can also display the serial number through the following HCM dialog boxes and BCU

commands:

•Adapter Properties tab in HCM.

Select an adapter in the device tree, then click the Properties tab in the right pane.

•BCU adapter --list command.

This command lists all Brocade adapters in the system and information such as model and

serial numbers.

3. Port World-Wide Name (PWWN).

Determine the PWWN through the following resources:

•Label on the adapter card contains the PWWN for each port.

•Brocade BIOS Configuration Utility.

Select the appropriate adapter port from the initial configuration utility screen, then select

Adapter Settings to display the WNN and PWWN for the port. For details, refer to

“Configuring BIOS using the Brocade configuration utility” on page 136.

•Port Properties tab in HCM.

Select a port for a specific adapter in the device tree, then click the Properties tab in the

right pane.

*FT00X0054E9*

FT00X0054E9

Brocade Adapters Installation and Reference Manual xxiii

53-1002144-01

•The following BCU commands:

4. Media access control (MAC) addresses. These are applicable to CNAs and Fabric Adapter ports

configured in CNA mode only.

The MAC address can be found in HCM by selecting the adapter in the device tree and clicking

the Properties tab in the right pane to display the adapter Properties panel. Look for the MAC

Address field.

Each port has a “burned-in” local port MAC address. This is the source MAC for LLDP

communications between the adapter and FCoE switch. To find this MAC address, select a DCB

port in the HCM device tree, then click the Properties tab in the right pane to display the port

Properties panel. Look for the Local port MAC field.

The Ethernet MAC address is used for normal Ethernet operations. To find this MAC address

using HCM, select an Ethernet port in the HCM device tree, then click the Properties tab in the

right pane to display the port Properties panel. Look for the Current MAC address and Factory

MAC address fields.

Each enode logging in to the fabric through a local adapter port is assigned a MAC address

during FCoE Initialization Protocol (FIP) operations. This MAC is assigned for the current FCoE

communication only. To find this MAC address, perform one of the following tasks:

•Select an FCoE port in the HCM device tree, then click the Properties tab in the right

pane to display the port Properties panel. Look for the FCoE MAC field.

•Enter the port --query port_id BCU command. Look for the FCoE MAC.

NOTE

MAC addresses assigned during FCoE initialization operations cannot be changed using device

management applications.

The FCoE Forwarder (FCF) MAC address is the address of the attached FCoE switch. Select an

FCoE port in the HCM device tree, then click the Properties tab in the right pane to display the

port Properties panel. Look for the FCF MAC field.

You can also determine port MAC addresses using the following BCU commands:

Command Function

port ---query port_id Displays port information, including the PWWN

for the FCoE port. The <port_id> parameter is

the port number.

port ---list Lists all the physical ports on the adapter along

with their basic attributes, such as the PWWN.

Command Function

port --query port_id Displays port information, including the MAC

addresses. The <port_id> parameter is the

port number.

port --list Lists all the physical ports on the CNA along

with the adapter, Ethernet, and FCoE MAC

addresses.

xxiv Brocade Adapters Installation and Reference Manual

53-1002144-01

NOTE

For details on using HCM and BCU commands, refer to the Brocade Adapters

Administrator’s Guide.

Support Save overview

The Support Save feature is an important tool for collecting debug information from the driver,

internal libraries, and firmware. You can save this information to the local file system and send it to

support personnel for further investigation. Use one of the following options to launch this feature:

•In HCM, launch Support Save through the Tools menu.

•In Management applications, use the Technical SupportSave dialog box.

•For BCU, enter the bfa_supportsave command.

NOTE

For VMware ESX 5.0 and later systems, BCU commands are integrated with the esxcli

infrastructure. To initiate the BCU supportsave command, enter esxcli brocade supportsave on

the ESX system.

•Through your internet browser (Internet Explorer 6 or later or Firefox 2.0 or later), you can

collect Support Save output if you do not have root access, do not have access to file transfer

methods such as File Transfer Protocol (FTP) and Secure Copy (SCP), or do not have access to

the Host Connectivity Manager (HCM).

•A Support Save collection can also occur automatically for a port crash event.

Launching Support Save through BCU, HCM, and during a port crash event saves the following

information:

•Adapter model and serial number

•Adapter firmware version

•Host model and hardware revision

•All support information

•Adapter configuration data

•All operating system and adapter information needed to diagnose field issues

•Information about all adapters in the system

•Firmware and driver traces

•Syslog message logs

•Windows System Event log .evt file

•HCM GUI-related engineering logs

•Events

•Adapter configuration data

•Environment information

•Data .xml file

•Vital CPU, memory, network resources

•HCM Agent (logs, configuration)

•Driver logs

Brocade Adapters Installation and Reference Manual xxv

53-1002144-01

•Install logs

•Core files

•Details on the CNA or Fabric Adapter Ethernet interface, including IP address and mask.

•Status and states of all adapter ports, including the Ethernet, FCoE, and DCB ports on CNAs

and Fabric Adapters.

•DCB status and statistics for CNAs and Fabric Adapters

•Network driver information, Ethernet statistics, offload parameters, and flow control coalesce

parameters for CNAs and Fabric Adapters.

•Ethernet offload and flow control parameters for CNAs and Fabric Adapters.

NOTE

Before collecting data through the Support Save feature, you may want to disable auto-recovery on

the host system. When adapters are reset after an auto-recovery from a failure, traces initiated

before the failure may be lost or overwritten.

To disable auto-recovery, use the following commands:

•For Linux, use the following commands, then reboot the system:

-To disable auto-recovery for the network (BNA) driver.

insmod bna.o bnad_ioc_auto_recover=0

-To disable auto-recovery for the storage (BFA) driver.

insmod bfa.o ioc_auto_recover=0

•For VMware, use the following commands.

-To unload and load the network (BNA) driver with IOC auto-recovery disabled, use the

following commands:

esxcfg-module -u bna

esxcfg-module bna bnad_ioc_auto_recover=0

-To disable IOC auto-recovery for the network (BNA) driver across reboots, use the following

command:

esxcfg-module -s "bnad_ioc_auto_recover=0" bna

-To disable IOC auto-recovery for the storage (BFA) driver across reboots, use the following

command:

esxcfg-module -s "ioc_auto_recover=0" bfa

•For Windows use the Registry Edit tool (regedt32) or the BCU drvconf --key command.

Following is the drvconf ---key command:

bcu drvconf --key ioc_auto_recover --val 0

•For Solaris, edit /kernel/drv/bfa.conf using the following command:

ioc-auto-recover=0

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems.

xxvi Brocade Adapters Installation and Reference Manual

53-1002144-01

Initiating Support Save through HCM

Launching the Support Save feature in HCM collects HCM application data. Launch Support Save

by selecting Tools > Support Save.

Messages display during the Support Save operation that provide the location of the directory

where data is saved. If you are initiating Support Save from a remote management station and

receive a warning message that support files and Agent logs could not be collected, the HCM Agent

is unavailable on the remote host. Select Tools > Backup to back up data and configuration files

manually.

For more information and additional options for using this feature, refer to the Brocade Adapters

Administrator’s Guide.

Initiating Support Save through BCU commands

Use the bfa_supportsave command to Initiate Support Save through the BCU:

•bfa_supportsave -

-Creates and saves the supportsave output under the /tmp directory on Linux and Solaris

systems.

-Creates and saves the supportsave output under the current directory for Windows

systems.

•bfa_supportsave <dir> - Creates and saves the supportsave output under a directory name

that you provide.

•bfa_supportsave <dir> <ss_file_name> - Creates and saves the supportsave output under a

directory and file name that you provide. If the directory already exists, it will be overwritten.

NOTE

If specifying a directory, make sure that the directory does not already exist to prevent overwriting

the directory. Do not just specify a drive (such as C:) or C:\Program Files.

Messages display as the system gathers information. When complete, an output file and directory

display. The directory name specifies the date when the file was saved.

For more information on the bfa_supportsave command, refer to the Host Connectivity Manager

(HCM) Administrator’s Guide.

VMware ESX systems

For VMware ESX 5.0 and later systems, BCU commands are integrated with the esxcli

infrastructure. To initiate the BCU supportsave command, enter esxcli brocade supportsave to

initiate Support Save:

Initiating Support Save through the internet browser

Initiate bfa_supportsave through an internet browser.

1. Open an internet browser and type the following URL:

https://localhost:34568/JSONRPCServiceApp/SupportSaveController.do

Brocade Adapters Installation and Reference Manual xxvii

53-1002144-01

In this URL, localhost is the IP address of the server from which you want to collect the

bfa_supportsave information.

2. Log in using the factory default user name (admin) and password (password). Use the current

user name and password if they have changed from the default.

The File Download dialog box displays, prompting you to save the SupportSaveController.do

file.

3. Click Save and navigate to the location where you want to save the file.

4. Save the file, but rename it with a “zip” extension. For example:

supportSaveController.zip.

5. Open the file and extract contents using any compression utility program.

Initiating Support Save through a port crash event

If the port crashes and triggers a port crash event, Support Save data is collected at a system-wide

level. An Application Log message is generated with the following message:

Port Crash Support Save Completed

Port crash events have a CRITICAL severity and you can view the details in the Master Log and

Application Log tables in HCM.

Support Save differences

Following are differences in data collection for the HCM, BCU, and browser applications of

bfa_supportsave:

•BCU - Collects driver-related logs, HCM Agent information, and configuration files.

•Browser - Collects driver-related and HCM Agent logs and configuration files.

•HCM - Collects HCM application data, driver information, HCM Agent logs, and configuration

files.

NOTE

Master and Application logs are saved when Support Save is initiated through HCM, but not through

BCU.

Document feedback

Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and

completeness of this document. However, if you find an error or an omission, or you think that a

topic needs further development, we want to hear from you. Forward your feedback to:

documentation@brocade.com

Provide the title and version number of the document and as much detail as possible about your

comment, including the topic heading and page number and your suggestions for improvement.

xxviii Brocade Adapters Installation and Reference Manual

53-1002144-01

Brocade Adapters Installation and Reference Manual 1

53-1002144-01

Chapter

Product Overview

In this chapter

•Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

•Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

•Host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

•Adapter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

•Adapter management features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

•Adapter software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

•Items shipped with your adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

•Boot installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

•Downloading software and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

•Using BCU commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Fabric Adapters

The Brocade 1860 stand-up Fabric Adapter is a low-profile MD2 form factor PCI Express (PCIe) card

that installs in standard host computer systems. Figure 2 illustrates major components of the

dual-port Brocade 1860 Fabric Adapter. Brocade 1860 single or dual-port adapter models can ship

with the following configurations of small form factor pluggable (SFP) transceivers:

•Single-port model - 16 Gbps Fibre Channel SFP+, 10GbE SFP+, or without optics.

•Dual-port model - Two 16 Gbps Fibre Channel SFP+, two 10GbE SFP+, or without optics.

Although adapters may ship with specific optics (or no optics) installed, you can replace with

compatible optics, such as 8 Gbps FC SFPs, long-wave SFPs, and SFP+ direct-attach copper cables.

Refer to “Hardware compatibility” on page 4 for more information.

Please note that the following illustration is representative and may have minor physical

differences from the card that you purchased.

2Brocade Adapters Installation and Reference Manual

53-1002144-01

Fabric Adapters

FIGURE 2 Brocade 1860 Fabric Adapter (heat sink removed)

ATTENTION

Only use Brocade-branded SFP+ laser transceivers supplied with stand-up Fabric Adapters.

AnyIO technology

Although the Brocade 1860 can be shipped in a variety of SFP configurations, you can change port

function to the following modes using the Brocade AnyIO technology, provided the correct SFP is

installed for the port:

•HBA or Fibre Channel mode. This mode utilizes the Brocade Fibre Channel storage driver. An 8

or 16 Gbps Fibre Channel SFP can be installed for the port. The port provides Host Bus Adapter

(HBA) functions on a single port so that you can connect your host system to devices on the

Fibre Channel SAN. Ports with 8 Gbps SFPs configured in HBA mode can operate at 2, 4, or 8

Gbps. Ports with 16 Gbps SFPs configured in HBA mode can operate at 4, 8, or 16 Gbps.

Fabric Adapter ports set in HBA mode appear as “FC” ports when discovered in HCM. They

appear as “FC HBA” to the operating system.

NOTE

Fibre Channel mode and HBA mode may be used interchangeably in this document.

1LEDs for port 1 SFP

2 Cable connectors for port 1 and port 0 SFPs (Fiber optic SFP illustrated)

3LEDs for port 0 SFP

4 Low-profile mounting bracket.

Note: The adapter ships with the standard (full-height) mounting bracket

installed.

5 PCIe x8 connector

6ASIC

Brocade Adapters Installation and Reference Manual 3

53-1002144-01

Fabric Adapters 1

•Ethernet or NIC mode. This mode utilizes the Brocade network driver. A 10 GbE SFP or direct

attached SFP+ copper cable must be installed for the port. This mode supports basic Ethernet,

Data Center Bridging (DCB), and other protocols that operate over DCB to provide functions on

a single port that are traditionally provided by an Ethernet Network Interface Card (NIC). Ports

configured in this mode can operate up to 10 Gbps. Fabric Adapters that ship from the factory

with 10GbE SFPs installed or no SFPs installed are configured for Ethernet mode by default.

Fabric Adapter ports set in NIC mode appear as Ethernet ports when discovered in HCM. These

ports appear as “10 GbE NIC” to the operating system.

NOTE

Ethernet and NIC mode may be used interchangeably in this document.

•CNA mode. This mode provides all functions of Ethernet or NIC mode, plus adds support for

FCoE features by utilizing the Brocade FCoE storage driver. A 10 GbE SFP or direct attached

SFP+ copper cable must be installed for the port. Ports configured in CNA mode connect to an

FCoE switch. These ports provide all traditional CNA functions for allowing Fibre Channel traffic

to converge onto 10 Gbps DCB networks. The ports even appear as network interface

controllers (NICs) and Fibre Channel adapters to the host. FCoE and 10 Gbps DBS operations

run simultaneously.

Fabric Adapter ports set CNA mode appear as FCoE ports when discovered in HCM. These

ports appear as “10 GbE NIC” to the operating system.

Changing the port mode

You can change the mode of individual ports on an adapter using the following BCU commands:

•The bcu port --mode command allows you can change the mode of individual ports on the

adapter.

•The bcu adapter --mode command allows you can change all ports on the adapter to a specific

mode.

For more information on these commands, refer to the Brocade Adapters Administrator’s Guide.

As general steps to change a port’s operating mode, perform the following steps:

1. Change the mode using the bcu port --mode or bcu adapter --mode BCU commands.

2. Make sure the appropriate SFP (FC or 10 GbE) and driver packages are installed to operate the

port in the selected mode if they are not already installed. Refer to Table 9 on page 44 for

information on drivers.

3. Power-cycle the host system.

Dynamically changing the port mode is equivalent to plugging in a new device in the system. so

the system must be power-cycled for this configuration change to take effect.

NOTE

For Windows systems you must install the drivers for the new mode after the system is rebooted.

This is not required if the appropriate driver is already pre-installed in the system.

When you change the port mode, the port resets to factory defaults for physical functions (PF)

associated with the mode (refer to “Factory default PF configurations” on page 16). For details on

configuring ports for different operating modes, refer to the Brocade Adapters Administrator’s

Guide.

4Brocade Adapters Installation and Reference Manual

53-1002144-01

Fabric Adapters

Hardware compatibility

This section outlines important compatibility information.

SFP transceivers

Use only the Brocade-branded small form factor pluggable (SFP) transceivers described in this

section for stand-up Brocade Fabric Adapters.

Ports configured in CNA or NIC mode

Table 1 provides the type, description, and switch compatibility information for supported SFPs that

can be installed in ports configured in CNA or NIC mode.

Ports configured in HBA mode

Table 2 provides the type, description, and switch compatibility information for supported SFPs that

can be installed in ports configured in HBA mode.

TABLE 1 Compatible SFPs for ports configured in CNA or NIC mode

Type Description Switch Compatibility

10 Gbps SR (short range)

SFP+, 1490 NM

Optical short range SFP+ for

Distance depends on cable

type. Refer to “Cabling” on

page 176.

Any switch compatible with

the adapter

10 Gbps LR (long range)

SFP+, 10 km. 1310 NM

Optical long range SFP+ for

fiber optic cable 10 km (6.2

mi.)

Any switch compatible with

the adapter

1 meter direct-attached

SFP+ copper cable

SFP+ for 1-meter (3.2 feet)

maximum twinaxial copper

cable

Any switch compatible with

the cable.

3 meter direct-attached

SFP+ copper cable

SFP+ for 3-meter maximum

twinaxial copper cable (9.8

feet)

Any switch compatible with

the cable.

5 meter direct-attached

SFP+ copper cable

SFP+ for 5-meter maximum

twinaxial copper cable (16.4

feet)

Any switch compatible with

the cable.

TABLE 2 Compatible SFPs for ports configured in HBA mode

Type Description Switch Compatibility

8 Gbps SWL (short wave

laser) SFP+

SFP+ for fiber optic cable

Distance depends on cable

type. Refer to “Cabling” on

page 176.

Any switch compatible with

the adapter

8 Gbps LWL (long wave

laser) 10 km SFP+

SFP+ for fiber optic cable

Distance depends on cable

type. Refer to “Cabling” on

page 176.

Any switch compatible with

the adapter

Brocade Adapters Installation and Reference Manual 5

53-1002144-01

Converged network adapters 1

PCI express connections

Brocade Fabric Adapters are compatible with PCI express (PCIe) connections that have the

following specifications:

•x8 lane or greater transfer interface.

•Gen1 (PCI Base Specification 1.0, 1.01a, and 1.1).

•Gen2 (PCI Express Base Specification 2.0).

•Gen 3 (PCI Express Base Specification 3.0)

NOTE

Install adapters in PCI express connectors with an x8 lane transfer interface or greater for best

performance. You cannot install Fabric Adapters in PCI or PCI-X connectors.

Host systems and switches

For a current list of switches, servers, and applications compatible with Brocade stand-up

adapters, refer to the latest interoperability matrixes on Brocade’s website at

www.brocade.com/adapters.

Storage systems

Using Fabric Adapter ports configured in HBA mode, you can connect a server (host system) to a

Fibre Channel SAN in a switched fabric and point-to-point topology or directly to a storage array in a

point-to-point topology.

Using Fabric Adapter ports configured in CNA mode, you can connect a server (host system) to a

Fibre Channel SAN through connection with a compatible FCoE switch.

Refer to the latest Brocade interoperability matrices for a list of supported server models on

Brocade’s website at www.brocade.com/adapters.

Converged network adapters

Table 3 describes available Brocade FCoE PCIe Converged Network Adapters (CNAs) for PCIe x8

host bus interfaces, hereafter referred to as Brocade CNAs. These adapters provide reliable,

high-performance host connectivity for mission-critical SAN environments. Provided in the table are

the model number, port speed, number of ports, and adapter type for each CNA.

16 Gbps SWL (short

wave laser) SFP+

SFP+ for fiber optic cable

Distance depends on cable

type. Refer to “Cabling” on

page 176.

Any switch compatible with

the adapter

16 Gbps LWL (long wave

laser) 10 km SFP+

SFP+ for fiber optic cable

Distance depends on cable

type. Refer to “Cabling” on

page 176.

Any switch compatible with

the adapter

TABLE 2 Compatible SFPs for ports configured in HBA mode

Type Description Switch Compatibility

6Brocade Adapters Installation and Reference Manual

53-1002144-01

Converged network adapters

Two types of CNAs are available:

•Stand-up adapters.

These are low-profile MD2 form factor PCI Express (PCIe) cards, measuring 6.6 in. by 2.714 in.

(16.765 cm by 6.89 cm) that install in PCIe connectors in standard host systems.

•Mezzanine adapters.

These are smaller cards that mount on server blades that install in blade system enclosures.

The enclosures contain other system blades, such as switch and pass-through modules.

CNA ports connect to an FCoE switch. CNAs combine the functions of a Host Bus Adapter (HBA) and

Network Interface Card (NIC) on one PCIe x8 card. The CNAs even appear as network interface

controllers (NICs) and Fibre Channel adapters to the host. These CNAs fully support FCoE protocols

and allow Fibre Channel traffic to converge onto 10 Gbps Data Center Bridging (DCB) networks.

FCoE and 10 Gbps DCB operations run simultaneously.

The combined high performance and proven reliability of a single-ASIC design makes these CNAs

ideal for connecting host systems on Ethernet networks to SAN fabrics based on Brocade Fabric or

M-Enterprise operating systems.

Stand-up adapters

Stand-up type CNAs, such as the 1010 and 1020, are low-profile MD2 form factor PCI Express

(PCIe) cards that install in standard host computer systems. Figure 3 on page 7 illustrates major

components of the Brocade 1020 stand-up CNA with two fiber optic small form factor pluggable

(SFP) transceivers installed. Both stand-up CNAs also support direct-attached SFP+ copper cables.

Please note that the following illustration is representative and may have minor physical

differences from the card that you purchased.

TABLE 3 Brocade Fibre Channel CNAs

Model Number Port Speed Number of Ports Adapter Type

1007 10 Gbps maximum 2 Mezzanine

1020 10 Gbps maximum 2 Stand-up

1010 10 Gbps maximum 1 Stand-up

1741 10 Gbps maximum 2 Mezzanine

Brocade Adapters Installation and Reference Manual 7

53-1002144-01

Converged network adapters 1

FIGURE 3 Brocade 1020 stand-up CNA with low-profile mounting bracket (heat sink removed)

ATTENTION

Only use Brocade-branded SFP+ laser transceivers supplied with stand-up CNAs.

1LEDs for port 1 SFP

2 Cable connectors for port 1 and port 0 SFPs (Fiber optic SFP illustrated)

3LEDs for port 0 SFP

4 Low-profile mounting bracket.

Note: The CNA ships with the low-profile mounting bracket installed.

5 PCIe x8 connector

6ASIC

Note: This photo illustrates parts location only. The CNA may not look exactly like your model.

8Brocade Adapters Installation and Reference Manual

53-1002144-01

Converged network adapters

Mezzanine adapters

Mezzanine adapters are smaller modules than stand-up models. These mount on server blades

that install in blade system enclosures.

1007

Figure 4 illustrates major components of the Brocade 1007, which is an IBM combo form factor

horizontal (CFFh) CNA containing two ports operating at 10 Gbps. Please note that the following

illustration is representative and may have minor physical differences from the card that you

purchased.

FIGURE 4 Brocade 1007 CNA

NOTE

Labels showing the part number, PWWNs, port MAC addresses, model number, and serial number

for the Brocade 1007 CNA are on the reverse (top) side of the card.

1ASIC with heat sink

2 x8 PCIe interface connector.

3 Release lever. Pull to release adapter from blade server.

4 Holes for guiding card onto blade server system board mounting posts.

5 Holes for guiding card onto blade server system board mounting posts.

6 Midplane connectors

Brocade Adapters Installation and Reference Manual 9

53-1002144-01

Converged network adapters 1

The Brocade 1007 mounts on a server blade that installs in an IBM BladeCenter® enclosure. The

adapter uses FCoE to converge standard data and storage networking data onto a shared Ethernet

link. Ethernet and Fibre Channel communications are routed through the DCB ports on the adapter

to the blade system enclosure midplane, and then onto switch modules installed in the enclosure.

For information on installing the Brocade 1007 CNA on a server blade, refer to Chapter 2,

“Hardware Installation”. For additional information related to the supported blade server, blade

system enclosure, and other devices installed in the enclosure such as I/O modules and switch

modules, refer to the installation instructions provided with these products.

1741

The Brocade® BR1741M-k 2P Mezz Card, also known as the Brocade 1741 mezzanine card, is

small-form factor (SFF) mezzanine card containing two ports operating at 10 Gbps that mounts on a Dell

blade server. Figure 5 illustrates major components of the 1741 adapter. Please note that the following

illustration is representative and may have minor physical differences from the card that you purchased.

FIGURE 5 Brocade 1741 mezzanine card

1ASIC with heat sink

2 Port WWN and MAC address label

3 OEM PPID and part number label

4Brocade serial number label

10 Brocade Adapters Installation and Reference Manual

53-1002144-01

Converged network adapters

The Brocade 1741 mounts on supported blade servers that install in Dell™ PowerEdge™ M1000e

modular blade systems. It is used in conjunction with matching I/O modules, also installed in the

blade enclosure. The adapter uses FCoE to converge standard data and storage networking data

onto a shared Ethernet link. Ethernet and Fibre Channel communications are routed through the

DCB ports on the adapter to the enclosure backplane then to the I/O module.

For information on installing the Brocade 1741 CNA on a blade server, refer to Chapter 2,

“Hardware Installation”. For additional information related to the supported server blade, blade

enclosure, and other devices installed in the enclosure such as I/O and switch modules, refer to

the installation instructions provided with these products.

Hardware compatibility

This section outlines important compatibility information.

SFP transceivers (stand-up adapters)

Use only the Brocade-branded small form factor pluggable (SFP) transceivers described in Table 4

in Brocade stand-up CNAs. The table provides the type, description, and switch compatibility

information for supported SFPs.

Host systems and switches (stand-up adapters)

For a current list of switches, servers, and applications compatible with Brocade stand-up

adapters, refer to the latest interoperability matrixes on Brocade’s website at

www.brocade.com/adapters.

TABLE 4 Compatible SFPs for Brocade stand-up CNAs

10 Gbps SR (short range)

SFP+, 1490 NM

Optical short range SFP+ for

Distance depends on cable

type. Refer to “Cabling

(stand-up adapters)” on

page 183.

Any switch compatible with

the adapter

10 Gbps LR (long range)

SFP+, 10 km, 1310 NM

Optical long range SFP+ for

fiber optic cable 10 km (6.2

mi.)

Any switch compatible with

the adapter

1 meter direct-attached

SFP+ copper cable

SFP+ for 1-meter (3.2 feet)

maximum twinaxial copper

cable

Any switch compatible with

the cable.

3 meter direct-attached

SFP+ copper cable

SFP+ for 3-meter maximum

twinaxial copper cable (9.8

feet)

Any switch compatible with

the cable.

5 meter direct-attached

SFP+ copper cable

SFP+ for 5-meter maximum

twinaxial copper cable (16.4

feet)

Any switch compatible with

the cable.

Brocade Adapters Installation and Reference Manual 11

53-1002144-01

Converged network adapters 1

Server blades and blade system enclosures (mezzanine adapters)

Consider the following points when installing mezzanine adapters in blade servers and system

enclosures:

•For information on server blades and blade system enclosures that are compatible with

adapters, refer to the “Adapters Resources” section of www.brocade.com/adapters.

•For information about enclosures, server blades, I/O modules, switch modules, and optional

devices that are compatible with this adapter, visit the manufacturer websites for these

products. You can also contact your server blades or blade system enclosure marketing

representative or authorized reseller.

•To support each I/O module that you install in the blade system enclosure, you may also need

to install a compatible adapter in each server blade that you want to communicate with the I/O

module. Also, the adapter may only support switch modules or blades in specific I/O bays of

the enclosure. For additional information, refer to installation and user guides and the

interoperability guides provided for the blade server and blade system enclosure.

•The Brocade mezzanine adapter is compatible with the following types of modules that install

in the supported blade system enclosure:

-Pass-through modules

-I/O modules

-Switch modules

NOTE

For detailed information about these modules, see the installation and user guides and

interoperability guides provided for these modules and the blade system enclosure.

•You may be able to install only one mezzanine adapter per server blades. The maximum

number of adapters that you can install in the blade system enclosure varies according to the

type of enclosure that you are using because each type of enclosure may support a different

number of server blades. For additional compatibility information, see the installation, user

guides and interoperability guides provided for the blade server and the blade system

enclosure.

PCI express connections

Brocade CNAs are compatible with PCI express (PCIe) connections that have the following

specifications:

•x8 lane or greater transfer interface.

•Gen1 (PCI Base Specification 1.0, 1.01a, and 1.1).

•Gen2 (PCI Express Base Specification 2.0).

•Gen3 (PCI Express Base Specification 3.0).

NOTE

Install CNAs in PCI express connectors with an x8 lane transfer interface or greater for best

performance. You cannot install CNAs in PCI or PCI-X connectors.

12 Brocade Adapters Installation and Reference Manual

53-1002144-01

Host bus adapters

Storage systems

Using Brocade CNAs you can connect a server (host system) to a Fibre Channel SAN through

connection with a compatible FCoE switch. For a current list of compatible switches, servers, and

applications, refer to the latest interoperability matrices on Brocade’s website at

www.brocade.com/adapters.

NOTE

The CNA can connect with a network switch and perform NIC functions for network traffic.

WoL and SoL limitations

The following describes limitations of support for Wake on LAN (WoL) and Serial over LAN (SoL) for

the Brocade 1007 adapter:

•WoL. The adapter does not support WoL over its 10GbE links. WoL is supported using the IBM

BladeCenter 1GbE NIC included on the IBM server blades.

•SoL. The adapter does not support SoL over its 10GbE links. SoL is supported using the IBM

1GbE NIC included on the IBM server blades.

Host bus adapters

Brocade Table 5 provides the model number, port speed, number of ports, and adapter type for the

current Brocade Fibre Channel PCIe HBAs. These adapters provide reliable, high-performance host

connectivity for mission-critical SAN environments.

Two types of HBAs are available:

•Stand-up adapters.

These are low-profile MD2 form factor PCI Express (PCIe) cards, measuring 6.6 in. by 2.714 in.

(16.765 cm by 6.89 cm), that install in PCIe connectors in standard host systems.

•Mezzanine adapters.

These are smaller cards that mount on server blades that install in blade system enclosures.

Fibre Channel communications are routed through the adapter ports on the blader server to

the blade system enclosure midplane and onto the installed switch modules installed in the

enclosure.

TABLE 5 HBA model information

Model Number Port Speed Number of Ports Adapter Type

425 4 Gbps maximum1

1. A 4 Gbps SFP installed in Brocade 815 or 825 HBAs allows 4, 2, or 1 Gbps.

2Stand-up

415 4 Gbps maximum11Stand-up

804 8 Gbps maximum 2 Mezzanine

815 8 Gbps maximum2

2. An 8 Gbps SFP+ installed in Brocade 425 or 415 HBAs allows 4 or 2 Gbps only.

1Stand-up

825 8 Gbps maximum22Stand-up

Brocade Adapters Installation and Reference Manual 13

53-1002144-01

Host bus adapters 1

Using Brocade HBAs, you can connect your host system to devices on the Fibre Channel SAN. The

combined high performance and proven reliability of a single-ASIC design makes these HBAs ideal

for connecting hosts to SAN fabrics based on Brocade Fabric or M-Enterprise operating systems.

NOTE

This publication only supports the HBA models listed in Table 5, and does not provide information

about the Brocade 410 and 420 Fibre Channel HBAs, also known as the Brocade 400 Fibre Channel

HBAs.

Stand-up models

Figure 6 on page 13 illustrates major components of the Brocade 825 stand-up model HBA. Please

note that the following illustration is representative and may have minor physical differences from

the HBA that you purchased.

FIGURE 6 825 HBA with low-profile mounting bracket (head sink removed)

1 LEDs for port 1 SFP

2 Fiber optic cable connectors for port 1 and port 0 SFPs

3 LEDs for port 0 SFP

4 Low-profile mounting bracket. Note: The HBA ships with the low-profile mounting bracket installed.

5 PCIe x8 PCIe connector

6ASIC

7 Serial number label

8 Label showing PWWN for each port.

14 Brocade Adapters Installation and Reference Manual

53-1002144-01

Host bus adapters

ATTENTION

Use only Brocade-branded SFP laser transceivers on stand-up adapters that are supplied with the

adapter.

Mezzanine models

Figure 7 on page 14 illustrates major components of the Brocade 804 mezzanine HBA. This

mezzanine card installs in supported blade servers that install in Hewlett Packard BladeSystem

c-Class enclosures. Please note that the following illustration is representative and may have minor

physical differences from the HBA that you purchased.

FIGURE 7 804 mezzanine HBA

1Mounting screws

2ASIC

3 OEM serial and part number

4 PWWNs for adapter ports

5 Brocade serial and part number

Brocade Adapters Installation and Reference Manual 15

53-1002144-01

Host bus adapters 1

Hardware compatibility

This section outlines important compatibility information.

SFP transceivers (stand-up adapters)

Use only Brocade-branded small form factor pluggable (SFP) fiber optic 4 Gbps and 8 Gbps

transceivers in the Brocade Fibre Channel stand-up HBAs.

NOTE

All Brocade 815 and 825 HBAs ship with the 8 Gbps SFP+, and Brocade 415 and 425 HBAs ship

with the 4 Gbps SFP.

Host systems and switches (stand-up adapters)

Refer to the latest Brocade interoperability matrices at www.brocade.com/adapters for a list of

supported server models and switches.

Server blades and blade system enclosures (mezzanine adapters)

The Brocade 804 mezzanine HBA is compatible with blade servers, switch modules, interconnect

modules, and other components that install in supported blade system enclosures. For details on

blade servers and system enclosures that are compatible with this adapter, refer to the following:

•The interoperability matrices on Brocade’s website at www.brocade.com/adapters.

•Manufacturer websites for these products.

•Your blade server or blade system enclosure marketing representative or authorized reseller.

•Documentation provided for your blade server, blade system enclosure and enclosure

components.

PCI express connections

The Brocade Fibre Channel HBAs are compatible in PCI express (PCIe) connectors with the

following specifications:

•x8 lane or greater transfer interface.

•Gen1 (PCI Base Specification 1.0, 1.01a, and 1.1).

•Gen2 (PCI Express Base Specification 2.0).

•Gen3 (PCI Express Base Specification 3.0).

NOTE

Install HBAs in PCI express (PCIe) connectors with an x8 lane transfer interface or greater for best

performance. You cannot install HBAs in PCI or PCIx slots.

16 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

Storage systems

Using Brocade HBAs you can connect a server (host system) to a Fibre Channel SAN in a switched

fabric and point-to-point topology or directly to a storage array in a point-to-point topology. Refer to

the latest Brocade interoperability matrices for a list of supported server models on Brocade’s

website at www.brocade.com/adapters.

Adapter features

This section describes the features associated with all models of the following types of Brocade

adapters:

•Fabric Adapters - Refer to the following subsections depending on the port mode and SFP

configurations:

-“General features” on page 16.

-“FCoE features” on page 20, for ports configured in CNA mode.

-“Data Center Bridging and Ethernet features” on page 22, for ports configured in CNA or

NIC modes.

-“HBA features” on page 27, for ports configured in HBA mode.

•CNAs- Refer to the following subsections:

-“General features” on page 16.

-“FCoE features” on page 20.

-“Data Center Bridging and Ethernet features” on page 22.

•HBAs - Refer to the following subsections:

-“General features” on page 16.

-“HBA features” on page 27.

General features

Brocade adapters support the following general features for enhanced performance and

connectivity in the SAN and Ethernet networks.

I/O virtualization

Brocade adapters support physical function (PF) based I/O virtualization to provide data isolation

and sharing of the bandwidth resources. Depending on the adapter model or the operating mode

(CNA, HBA, or NIC) assigned to Fabric Adapter ports), from one to eight functions can be supported

per port on the PCI bus. These PFs can be seen as multiple adapters by the host operating system

or hypervisor.

Factory default PF configurations

For each type of adapter, each port has a set base or default PF as follows:

•For HBA models, each port has one Fibre Channel (FC) function.

•For CNA models, each port has one FC function and one Ethernet function.

Brocade Adapters Installation and Reference Manual 17

53-1002144-01

Adapter features 1

•For Fabric Adapters, the default number of PFs depends on the mode configured for the port.

Refer to Table 6.

vHBA

Virtual HBAs (vHBAs) are virtual port partitions that appear as virtual or logical HBAs to the host

operating system. vHBAs are supported on Brocade HBAs, CNAs, and Fabric Adapter ports

configured in HBA or CNA mode. Multiple vHBAs are not supported, therefore you cannot create or

delete them from an adapter. The default PF associated with an HBA port, the FCoE function on a

CNA port or Fabric Adapter port configured in CNA mode, or a Fabric Adapter port configured in HBA

mode is vHBA.

HCM discovers and displays all vHBAs as “FC.” For Fabric Adapter ports set in CNA mode, vHBAs

display as “FCoE.”

The following are limitations of vHBAs:

•Multiple vHBAs per port are not supported in release v3.0.

•Target Rate Limiting (TRL) and Quality of Service (QoS) are not supported at the vHBA level

(only at the physical port level).

•Boot over SAN is not supported at the vHBA level (only at the physical port level).

vNIC

Virtual Network Interface Cards (vNICs) are virtual port partitions that appear as a virtual or logical

NICs to the host operating system. vNICs are supported on Brocade CNAs and on Fabric Adapter 10

GbE ports configured in CNA or NIC mode. You cannot create or delete vNICs for Brocade CNA

models, such as the 1010 and 1020. Multiple vNICs are only supported on Fabric Adapter ports

(vNIC create and delete functions are supported).

For Fabric Adapter ports, you can create up to four Ethernet PFs per port using the BCU vnic -create

command. Therefore, for a two-port Fabric Adapter, eight total vNics are possible. Due to ESX

memory limitations, a total of 4 vNICs in a VMware ESX system is supported.

For each vNIC, you can configure bandwidth in increments of 100 Mpbs. The minimum bandwidth

is 100 Mbps and maximum bandwidth per vNIC is 10,000 Mbps.The maximum bandwidth per port

is also 10,000 Mbps. Therefore, you can divide the 10,000 Mbps among all PFs configured. For

example, if you configure four Ethernet PFs for a Fabric Adapter port, you can assign 1, 250 Mbps

per PF to reach the 10,000 Mbps maximum.

HCM discovers and displays all vNICs for a physical port as “Eth.”

The following are limitations of vNICs:

•vNICs are not supported on Brocade HBA modules.

•Multiple vNICs are not supported on Brocade CNA models, such as the 1010 and 1020.

•Teaming is not supported between vNICs configured on the same port.

TABLE 6 Factory default physical function (PF) configurations for Fabric Adapter ports.

Mode PFs configured per

port

PF configuration

per port

HBA 1 FC

CNA 2 Ethernet and FCoE

NIC 1 Ethernet

18 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

vHBA and vNIC BCU commands

Whether a port is configured for a single function or in the case of vNICs, multiple functions, each

PF is assigned a PCI function ID (pcfid). This pcfid is used as a parameter in BCU commands to

configure additional features or display information for that specific PF. For example, pcfid can be

used in certain BCU debug, authentication, diagnostic, Ethernet port, lport, rport, VLAN, and FCP

initiator mode commands, Specific vNIC and vHBA BCU commands are available for configuring

vHBAs and vNICs. Examples of these commands follow:

•vhba --query <pcifn> - Queries information about the virtual HBA.

•vhba --enable <pcifn> - Enables a vHBA on a specified adapter port for a specified PF.

•vhba –-disable <pcifn> - Disables a vHBA on a specified adapter port for a specified PCI

function.

•vhba --stats <pcifn> -Displays statistics for the virtual HBA.

•vhba --statsclr <pcifn> - Resets statistics for the virtual HBA.

For details on using these commands, refer to the Brocade Adapters Administrator’s Guide.

Following are available vNIC commands:

•vnic --create <port_id> [-b <bandwidth>] - Creates a new vNIC instance for a given adapter

port. You can specify the maximum bandwidth allowable for this vNIC.

•vnic --delete <pcifn> - Removes the specified vNIC instance.

•vnic --query <pcifn> - Queries information about the virtual NIC.

•vnic --enable <pcifn> - Enables a vNIC on a specified adapter port for a specified PCI function.

•vnic --disable <pcifn> - Disables a vNIC on a specified adapter port for a specified PCI function.

•vnic --stats <pcifn> - Displays statistics for the virtual NIC.

•vnic --statsclr <pcifn> - Resets vNIC statistics.

•vnic --bw <pcifn> <bandwidth> - Modifies the maximum allowable bandwidth for a vNIC.

For details on using these commands, refer to the Brocade Adapters Administrator’s Guide.

Other general adapter features

Following are brief descriptions of additional general features supported on Brocade CNA, HBA,

and Fabric Adapters:

•BIOS support:

-x86 and x64 Basic Input/Output System (BIOS)

-Unified Extensible Firmware Interface (UEFI)

-UEFI HII (Human Interface Infrastructure)

-PCI BIOS 2.1 or later

•Human Interaction Interface (HII) menu support. These menus are integrated into the UEFI

configuration browser. Options in these menus allow you to enable, disable, and set port speed

for adapter ports.

•Host Connectivity Manager (HCM) device management and Brocade Command Line Utility

(BCU) tools.

Brocade Adapters Installation and Reference Manual 19

53-1002144-01

Adapter features 1

•Hyper-V. This consolidates multiple server roles as separate virtual machines (VMs) using the

Windows Server 2008 operating system and provides integrated management tools to manage

both physical and virtual resources.

•Management APIs for integration with a Management application, such as Network Advisor,

and other management frameworks.

•Switch fabric topology - CNAs and Fabric Adapter ports configured in CNA mode can connect to

an FCoE switch through 10 GbE ports.

•PCIe interface with eight lanes. The adapter operates in Gen 1 and Gen 2 server connectors

that have the following specifications per lane:

-PCIe Gen 2 connector. Transfer rate of 5 Gigatransfers per second (GT/s) per lane. Data

rate of 500 MBps per lane.

-PCIe Gen 1 connector. Transfer rate of 2.5 GT/s per lane. Data rate of 250 MBps per lane.

•Plug-n-play and power management for all supported operating systems.

•RoHS-6. Certification by the of European Union Restriction of Hazardous Substances Directive

(RoHS) that adapter hardware components do not contain any of the six restricted materials.

These are mercury, chromium VI, cadmium, polybrominated biphenyl ether, lead, and

polybrominated biphenyl.

•Small form-factor pluggable (SFP+) optics on stand-up adapters for enhanced serviceability

(stand-up adapters only).

•Storage Management Initiative Specification (SMI-S).

Specification supporting the Common Information Model (CIM) Provider, which allows any

standard Common Information Model (CIM) and SMI-S based management software to

manage installed Brocade adapters.

NOTE

Although SMI-S Provider and CIM Provider may be used interchangeably, CIM is the more

generic term, while SMI-S is storage-specific.

•Windows Management Implementation (WMI).

•Windows Preinstallation Environment (WinPE), a minimal operating system with limited

services for Windows Server or Windows Vista used for unattended deployment of

workstations and servers. WinPE is designed for use as a standalone preinstallation

environment and as a component of other setup and recovery technologies. WinPE is

supported by Brocade Windows 2008 network and storage drivers.

•Windows Server 2008, RedHat Enterprise Linux (RHEL), SUSE Linux Enterprise (SLES), VMware

ESX Server, Solaris, and Oracle Enterprise Linux (OEL). For more details, refer to “Operating

system support” on page 40.

•Windows Server Core, a minimal server option for Windows Server 2008 operating systems

that provides a low-maintenance server environment with limited functionality. All

configuration and maintenance is done through command line interface windows or by

connecting to a system remotely through a management application.

•Windows 7. Windows 7 x86 is supported by Windows 2008 x86 drivers Windows 7 x64 is

supported by Windows 2008 R2 X64 drivers.

20 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

FCoE features

CNAs and Fabric Adapter ports configured in CNA mode support the following Fibre Channel over

Ethernet (FCoE) features:

Brocade CNAs support the following features:

•500,000 IOPS per port for maximum IO transfer rates.

•10 Gbps throughput per port full duplex

•Fibre Channel Security Protocol (FC-SP), providing device authentication through key

management.

•Boot over SAN. This feature provides the ability to boot the host operating system from a boot

device located somewhere on the SAN instead of the host’s local disk or direct attached Fibre

Channel storage. Specifically, this “boot device” is a logical unit number (LUN) located on a

storage device. Booting from a direct-attached device is also supported.

•Fabric-based boot LUN discovery, a feature that allows the host to obtain boot LUN information

from the fabric zone database.

NOTE

This feature is not available for direct-attached targets.

•Persistent binding. This enables you to permanently assign a system SCSI target ID to a

specific Fibre Channel device.

•Fibre Channel-Security Protocol (FC-SP) providing device authentication through key

management.

•FCoE Initialization Protocol (FIP) support for the following:

-FIP 2.0

-preFIP and FIP 1.03

-FIP Discovery protocol for dynamic FCF discovery and FCoE link management

-FPMA type FIP fabric login

-VLAN discovery for untagged and priority tagged FIP frames

-FIP discovery solicitation and FCP discovery

-Login (FIP and FCoE)

-FIP link down handling.

-FIP version compatibility

-FIP keep alive

-FIP clear virtual links

NOTE

The CNA FIP logic automatically adapts to the adequate FIP version and preFIP to enable

backward compatibility.

Brocade Adapters Installation and Reference Manual 21

53-1002144-01

Adapter features 1

•Interrupt Coalescing

This feature provides a method to delay generation of host interrupts and thereby combine

(coalesce) processing of multiple events. This reduces the interrupt processing rate and

reduces the time that the CPU spends on context switching. You can configure the following

parameters per port to adjust interrupt coalescing:

-Interrupt time delay. There is a time delay during which the host generates interrupts. You

can increase this delay time and thereby coalesce multiple interrupts events into one. This

results in fewer interrupts for interrupt events.

-Interrupt latency timer. An interrupt is generated when no new reply message requests

occur after a specific time period. You can adjust this time period and thereby minimize

I/O latency.

•Internet Protocol over Fibre Channel (IPFC) driver

This driver supports transmission of IP traffic over Fibre Channel links. It is only included in the

Linux “noarch” RPM package (brocade_driver_linux_<version>.tar.gz).

•LUN masking.

LUN masking establishes access control to shared storage to isolate traffic between different

initiators that are zoned in with the same storage target. LUN masking is similar to zoning,

where a device in a specific zone can communicate only with other devices connected to the

fabric within the same zone. With LUN masking, an initiator port is allowed to only access those

LUNs identified for a specific target.

Enable LUN masking on an adapter physical port through the HCM Basic Port Configuration

dialog box and the BCU fcpim –lunmaskadd command to identify the logical port (initiator) and

remote WWN (target) for the LUN number. Refer to the Brocade Adapter Administrator’s Guide

for more information on configuration.

This feature has following limitations.

-Only 16 LUN masking entries are allowed per physical port

-Multiple BCU instances for adding and deleting LUN masking are not supported

-This feature is only supported on Brocade HBAs and Fabric Adapters.

You can configure LUN masking for a particular target even without the actual devices being

present in the network.

When configuring boot over SAN, mask the boot LUN so that the initiator has exclusive access

to the boot LUN. Refer to the Brocade Administrator’s Guide for more information.

•N_Port ID Virtualization (NPIV). This allows multiple N_Ports to share a single physical N_Port.

This allows multiple Fibre Channel initiators to occupy a single physical port and reduce SAN

hardware requirements.

•Simple Network Management Protocol (SNMP)

SNMP is an industry-standard method of monitoring and managing network devices. Brocade

CNA adapters and Fabric Adapter ports configured in CNA mode provide agent and MIB

support for SNMP. For more information, refer to “Simple Network Management Protocol” on

page 34.

•Target rate limiting. You can enable or disable this feature on specific ports. Target Rate

Limiting relies on the storage driver to determine the speed capability of a discovered remote

ports, then uses this information to throttle FCP traffic rate to slow-draining targets. This

reduces or eliminates network congestion and alleviates I/O slowdowns at faster targets.

22 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

Target rate limiting is enforced on all targets that are operating at a speed lower than that of

the target with the highest speed. If the driver is unable to determine a remote port’s speed, 1

Gbps is assumed. You can change default speed using BCU commands. Target Rate Limiting

protects only FCP write traffic.

•vHBA

Virtual HBAs (vHBAs) are virtual port partitions that appear as virtual or logical HBAs to the

host operating system. Multiple vHBAs are not supported, therefore you cannot create or

delete them from an adapter. For more information, refer to“I/O virtualization” on page 16.

Data Center Bridging and Ethernet features

Brocade CNAs and Fabric Adapter ports configured in CNA or NIC mode support the following Data

Center Bridging (DCB) and Ethernet networking features:

•10 Gbps throughput per port full duplex

•1500 or 9600 byte (Jumbo) frames

These frames allow data to be transferred with less effort, reduces CPU utilization, and

increases throughput. Mini-jumbo frames are required to encapsulate FCoE frames on DCB.

Network administrators can change the jumbo packet size from the default setting using host

operating system commands as described in Appendix A, “Adapter Configuration”. Note that

the MTU size refers to the MTU for network configuration only. Internally, hardware will always

be configured to support FCoE frames that require mini-Jumbo size frames.

NOTE

The jumbo frame size set for the network driver cannot be greater than the setting on the

attached FCoE switch or the switch cannot accept jumbo frames.

•Simple Network Management Protocol (SNMP)

SNMP is an industry-standard method of monitoring and managing network devices. Brocade

CNAs and Fabric Adapter ports configured in CNA or NIC mode provide agent and MIB support

for SNMP. For more information, refer to “Simple Network Management Protocol” on page 34.

•Checksum/CRC offloads for FCoE packets, IPv4/IPv6 TCP and UDP packets, and IPv4 header.

The checksum offload supports Checksum offloads for TCP & UDP packets and IPv4 header.

This enables the CNA to compute the checksum, which saves host CPU cycles. The CPU

utilization savings for TCP checksum offload can range from few percent with MTU of 1500,

and up to 10-15% for MTU of 9000. The greatest savings are provided for larger packets.

•Data Center Bridging Capability Exchange Protocol (DCBCXP) (802.1)

Used between CNA or Fabric Adapter port configured in CNA mode and the FCoE switch to

exchange configuration with directly connected peers. Uses LLDP to exchange parameters

between two link peers.

•Enhanced transmission selection (802.1Qaz)

Provides guidelines for creating priority groups to enable guaranteed bandwidth per group.

More important storage data traffic can be assigned higher priority and guaranteed bandwidth

so it is not stalled by less-important traffic.

Brocade Adapters Installation and Reference Manual 23

53-1002144-01

Adapter features 1

•Ethernet flow control

Ethernet flow control is a mechanism for managing data transmission between two network

nodes to prevent a fast sender from over running a slow receiver. When an overwhelmed

receiver generates a PAUSE frame, this halts transmission for a specified period of time. Traffic

resumes when time specified in the frame expires or PAUSE zero is received.

•Flexible MAC address

•Hypervisor

Hypervisor is a processor-specific virtualization platform that allows multiple operating

systems to share a single server platform. Refer to “Hypervisor support” on page xvii for a list

of operating systems that support hypervisor operation for Brocade adapters:

•Brocade Network Intermediate Driver (BNI)

This provides support for multiple VLANs on ports and teams on Windows systems. This driver

is installed with the adapter software.

•Internet Small Computer System Interface (iSCSI) over DCB.

This feature leverages pre-priority-based flow control (PFC) and enhanced transmission

selection (ETS) features provided by Data Center Bridging (DCB) to Ethernet to enable more

lossless delivery of iSCSI traffic in data center environments. This feature enables fabric-wide

configuration of the iSCSI traffic. This is achieved by configuring the iSCSI traffic parameters on

the switches, which distribute those parameters to directly-attached, DCB-capable iSCSI

servers and targets. The adapter firmware obtains the iSCSI configuration from the switch

through the DCB Exchange Protocol (DCBX) and applies the configuration to the network driver

to classify the iSCSI traffic. The adapter will use this as a priority for all network traffic.

Note the following for the different adapter models:

-On CNA adapters and Fabric Adapter port configured in CNA mode, ETS support will only

be supported either between network and FCoE priority or one network and iSCSI priority.

-On Fabric Adapters, a separate transmit queue will be available for iSCSI traffic. This will

allow iSCSI traffic to be sent on separate queue and priority and not compete with network

traffic.

This feature is not supported on Solaris systems.

•Link aggregation (NIC teaming)

A network interface “team” is a collection of physical Ethernet interfaces (CNA ports and Fabric

Adapter port configured in CNA or NIC mode) acting as a single interface. Teaming overcomes

problems with bandwidth limitation and redundancy often associated with Ethernet

connections. Combining (aggregating) ports can increase the link speed beyond the limits of

one port and provide redundancy. You can team up to eight ports across multiple CNAs (and

Fabric Adapter ports configured in CNA or NIC mode) in three modes: failover, failback, or

802.3ad using BCU commands and HCM dialog boxes.

-Failover mode provides fault tolerance. Only one port in a team is active at a time (primary

port), and the others are in standby mode. If the primary port goes down, a secondary port

is chosen using a round-robin algorithm as the next primary. This port continues to be

primary, even if the original primary port returns.

24 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

-Failback mode is an extension of the Failover mode. In addition to the events that occur

during a normal failover, if the original primary port comes back up, that port again

becomes the primary port.

-802.3ad is an IEEE specification that includes Link Aggregation Control Protocol (LACP) as

a method to control how several physical ports bundle to form a single logical channel.

LACP allows a network device to negotiate automatic bundling of links by sending LACP

packets to the peer (a device directly connected to a device that also implements LACP).

This mode provides larger bandwidth in fault tolerance.

Configuration is required on the switch for NIC teaming to function.

Be aware when configuring ports for teaming that converged FCoE and network traffic is not

supported on ports that participate in an IEEE 802.3ad-based team. This must be enforced by

the user as there is no mechanism to control this in the software.

Teaming is implemented by Brocade in the intermediate drivers for Windows 2008 x86_64 and

R2, as well as Windows 2003 x86_64. Teaming is supported on Linux, Solaris, and VMware as

implemented by the specific operating system.

•Look ahead data split

Look ahead split is a security feature for using virtual machine shared memory for a virtual

machine queue, where the adapter splits the data packet so that look ahead data and post

look ahead data are transmitted to the shared memory allocated for this data.

•Multiple transmit (Tx) priority queues. Support for multiple transmit priority queues in the

network driver allows the driver to establish multiple transmit queues and specific priorities in

the ASIC. This feature enables Brocade CNAs and Fabric Adapter ports configured in CNA mode

to pass-link layer traffic using multiple transmit priorities without interfering with the assigned

priority for the FCoE or iSCSI traffic on the same port. This also allows handling of FCoE or iSCSI

priority changes propagated from the DCB switch. Multiple traffic priorities are used to ensure

that Quality of Service (QoS) is guaranteed across different traffic classes. The driver supports

one transmit queue on CNAs and eight on Fabric Adapters. If multiple vNICs are configured on

a Fabric Adapter, each vNIC instance has its own set of eight Tx Queues. To configure multiple

queues for sending priority tagged packets, refer to “Network driver parameters” on page 211.

Transmit NetQueues with multiple priorities allow VMware (version 4.1 or later) to assign

different priorities to transmit NetQueues to ensure QoS for different classes of traffic on an

ESX host. Multiple transmit priorities are supported in the following ways on Brocade adapters:

-On CNAs and Fabric Adapter ports configured in NIC mode, all eight priorities can be

assigned to transmit NetQueues by VMware.

-On CNAs only, every request to assign a priority different from the default network priority

will be denied. If a storage priority is reserved, one non-default priority could be assigned

to a transmit NetQueue.

-On Network Adapter ports configured in CNA mode, only allowed priorities can be assigned

to transmit NetQueues by VMware. Requests for a priority are denied if the priority

matches a reserved storage priority.

•Interrupt coalescing

Avoids flooding the host system with too many interrupts. This allows the system to reduce the

number of interrupts generated by generating a single interrupt for multiple packets.

Increasing the “coalescing timer” should lower the interrupt count and lessen CPU utilization.

Brocade Adapters Installation and Reference Manual 25

53-1002144-01

Adapter features 1

•Interrupt moderation

Implements dynamic selection interrupt coalescing values based on traffic and system load

profiles. Traffic is continuously monitored to place in categories between “high throughput

sensitive” and “high latency sensitive.” Similarly, the host system is monitored regularly to

place it in categories between “highly loaded” and “minimally loaded.” The driver dynamically

selects interrupt coalescing values based on this profiling.

•MSI-X

This is an extended version of Message Signaled Interrupts (MSI), defined in the PCI 3.0

specification. MSI-X helps improve overall system performance by contributing to lower

interrupt latency and improved utilization of the host CPU. MSI-X is supported by Linux RHEL5,

SLES 10 and 11, Windows 2008, and ESX 4.0 and 4.1.

•Network Boot (PXE and UNDI)

The preboot execution environment (PXE) mechanism, embedded in the CNA firmware,

provides the ability to boot the host operating system from a system located on the LAN

instead of the over the SAN or from host’s local disk. UNDI (universal network device interface)

is an application program interface (API) used by the PXE protocol to enable basic control of I/O

and performs other administrative chores like setting up the MAC address and retrieving

statistics through the adapter. UNDI drivers are embedded in the CNA firmware.

•Network Priority

The CNA and Fabric Adapter port configured in CNA mode support this feature, which provides

a mechanism to enable DCB flow control (802.1Qbb Priority-based Flow Control: Pause

802.1p) on network traffic. In addition, it guarantees mutual exclusion of FCoE and network

priorities to ensure proper enhanced transmission selection (ETS). This feature is not

supported on HBAs or Fabric Adapter ports configured in HBA mode.

This feature does not need enabled on the CNA, Fabric Adapter port configured in CNA mode,

or switch. Specific DCB attributes, including priorities for FCoE traffic, are configured on the

FCoE switch. These attributes propagate to the CNA DCB port through the DCBCXP. Adapter

firmware processes this information and derives priorities for network traffic. The network

driver is notified of the network priority and tags both FCoE and network frames with their

priorities.

•Priority-based flow control (802.1Qbb)

Defines eight priority levels to allow eight independent lossless virtual lanes. Pauses traffic

based on the priority levels and restarts traffic through a high-level pause algorithm.

•Receive side scaling (RSS) feature for advanced link layer

Enables receive processing to be balanced across multiple processors while maintaining

in-order delivery of data, parallel execution, and dynamic load balancing.

26 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

•Team Virtual Machine Queue (VMQ) support

VMQ support is provided by the Brocade Network Intermediate (BNI) driver for teaming (with no

VLANs). VMQ support allows classification of packets that the adapter receives using the

destination MAC address, and then routing the packets to different receive queues. Packets

can be directly transferred to a virtual machine’s shared memory using direct memory access

(DMA). This allows scaling to multiple processors by processing packets for different virtual

machines in on different processors. VMQ support provides the following features:

-Improves network throughput by distributing processing of network traffic for multiple

virtual machines (VMs) among multiple processors.

-Reduces CPU utilization by offloading receive packet filtering to NIC hardware.

-Avoids network data copy by using DMA to transfer data directly to VM memory.

-Splits network data to provide a secure environment.

-Supports live migration

VMQ support is only available on systems running Windows Server 2008 R2. Virtual machines

must be running Windows 7, Windows Server 2008 R2, Windows SErver 2008, or Windows

Vista with Integration Services Setup Disk installed.

•TCP segmentation offload (TSO) and large send offload (LSO)

Large chunks of data must be segmented to smaller segments to pass through network

elements. LSO increases outbound throughput by reducing CPU overhead. Offloading to the

network card, where segmentation can be done by the Transmission Control Protocol (TCP), is

called TCP segmentation.

•VLAN (802.1Q)

A Virtual LAN (VLAN) is a way to provide segmentation of an Ethernet network. A VLAN is a

group of hosts with a common set of requirements that communicate as if they were attached

to the same LAN segment, regardless of their physical location. A VLAN has the same

attributes as a physical LAN, but it allows end stations to be logically grouped together.

VLANS are implemented by Brocade in the intermediate drivers for Windows 2008 x86_64, as

well as Windows 2003 x86_64. VLANs are supported on Linux, Solaris, and VMware as

implemented by the specific operating system.

•MAC and VLAN filtering and tagging

A mechanism that allows multiple networks to transparently share the same physical network

link without leakage of information between networks. Adapter hardware filters data frames

from devices on a LAN so that only frames that match the MAC and VLAN for the configured

LAN are forwarded to that LAN.

•VLANs over teams. Specific VLANs can be configured to communicate over specific teams

using BCU commands and HCM. The function of the VLAN over a team is the same as a VLAN

on a single port. A team can support up to 64 VLANs, and the VLANs should have the same

MAC address as the team. Changing a team’s MAC address changes the address of VLANs

over the team. Changing the team name adds the name to the prefix of the VLAN’s display

name.

VLANs over teams is supported by the Brocade intermediate drivers for Windows 2008 x86_64

and R2 and later systems only. For more details on teaming, refer to Link aggregation (NIC

teaming) in this section. For more information on VLANs, refer to VLAN (802.1Q) in this section.

Brocade Adapters Installation and Reference Manual 27

53-1002144-01

Adapter features 1

•VLAN and Teaming Configuration Persistence

VLAN and teaming configurations can be maintained when updating drivers. Configurations

are automatically saved during upgrade and can be restored using BCU commands or HCM.

•VMware NetQueue

This feature improves performance in 10 GbE virtualized environments by providing multiple

receive and transmit queues, which allows processing to be scaled to multiple CPUs. The

Brocade adapter network driver (CNAs only) supports receive (Rx), as well as transmit (Tx)

NetQueues. This feature requires MSI-X support on host systems.

•VMware Network IO Control or NetIOC, also known as NetIORM (Network IO Resource

Management), is a QoS mechanism that allows different traffic types to coexist on a single

physical NIC in a predictable manner. A primary benefit of NetIOC is that it ensures that

adaptive transmit coalescing settings are not lost during data path or device reset.

•VMware VMdirect Path I/O

This allows quest operating systems to directly access an I/O device, bypassing the

virtualization layer. This can improve performance for ESX systems that use high-speed I/O

devices, such as 10 Gbps Ethernet.

•vNICs, or virtual network interface cards (NICs).

Virtual Network Interface Cards (vNICs) are virtual partitions that appear as a virtual or logical

NICs to the host operating system. vNICs are supported on Brocade CNAs and on Fabric

Adapter 10 GbE ports configured in CNA or NIC mode. Multiple vNICs are only supported on

Fabric Adapter ports.

Using BCU commands, you to create up to eight vNICs per Fabric Adapter ports configured in

CNA or NIC mode. You can configure features, such as vNIC teaming, for individual vNICs. For a

two-port Fabric Adapter, 16 total vNICs are possible. For more information, refer to “I/O

virtualization” on page 16.

HBA features

Brocade Fibre Channel HBAs and Fabric Adapter ports configured in HBA mode provide the

following features for enhanced performance and connectivity in the SAN.

•500,000 IOPS per port for maximum IO transfer rates.

•1,600 Mbps throughput per port full duplex.

•Host Connectivity Manager (HCM) device management and Brocade Command Line Utility

(BCU) tools.

•Management APIs for integration with a Management application, such as Network Advisor,

and other management frameworks.

•BIOS support:

-x86 and x64 Basic Input/Output System (BIOS)

-Unified Extensible Firmware Interface (UEFI)

NOTE

UEFI is not supported on the Brocade 804 adapter.

-PCI BIOS 2.1 or later

28 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

•LUN masking.

LUN masking establishes access control to shared storage to isolate traffic between different

initiators that are zoned in with the same storage target. LUN masking is similar to zoning,

where a device in a specific zone can communicate only with other devices connected to the

fabric within the same zone. With LUN masking, an initiator port is allowed to only access those

LUNs identified for a specific target.

Enable LUN masking on an adapter physical port through the HCM Basic Port Configuration

dialog box and the BCU fcpim –lunmaskadd command to identify the logical port (initiator) and

remote WWN (target) for the LUN number. Refer to the Brocade Adapter Administrator’s Guide

for more information on configuration.

This feature has following limitations.

-Only 16 LUN masking entries are allowed per physical port

-Multiple BCU instances for adding and deleting LUN masking are not supported

-This feature is only supported on Brocade HBAs and on Fabric Adapter ports configured in

HBA mode.

You can configure LUN masking for a particular target even without the actual devices being

present in the network.

When configuring boot over SAN, mask the boot LUN so that the initiator has exclusive access

to the boot LUN. Refer to the Brocade Administrator’s Guide for more information.

•Quality of Service (QoS) feature working in conjunction with the QoS feature on Brocade

switches to assign high, medium (default), or low traffic priority to a given source or destination

traffic flow.

The following licenses need to be installed on the edge switch connected to each HBA port or

Fabric Adapter ports configured in HBA mode:

-Adaptive Networking (AN) license.

-Server Application Optimization (SAO) license.

To determine if these licenses are installed on the connected switch, execute the Fabric OS

licenseshow command. For more information about Fabric OS commands and QoS support,

refer to the Fabric OS Administrator’s Guide.

•FCP-IM I/O Profiling

This feature, available through HCM, can be enabled or disabled on a physical port. When

enabled, the driver firmware categories I/O latency data into average, minimum, and maximum

categories. Use this feature to analyze traffic patterns and help tune HBAs, Fabric Adapter port

configured in HBA mode, fabrics, and targets for better performance. Note that enabling this

feature impacts I/O performance.

•Interrupt Coalescing

This feature provides a method to delay generation of host interrupts and thereby combine

(coalesce) processing of multiple events. This reduces the interrupt processing rate and

reduces the time that the CPU spends on context switching. You can configure the following

parameters per port to adjust interrupt coalescing:

Brocade Adapters Installation and Reference Manual 29

53-1002144-01

Adapter features 1

-Interrupt time delay. There is a time delay during which the host generates interrupts. You

can increase this delay time and thereby coalesce multiple interrupts events into one. This

results in fewer interrupts for interrupt events.

-Interrupt latency timer. An interrupt is generated when no new reply message requests

occur after a specific time period. You can adjust this time period and thereby minimize

I/O latency.

•16 Virtual Channels (VCs) per port. VC-RDY flow control can use these multiple channels for

Quality of Service (QoS) and traffic prioritization in physical and virtualized network

environments.

•Storage Management Initiative Specification (SMI-S)

Specification supporting the CIM Provider, which allows any standard Common Information

Model (CIM) and SMI-S based management software to manage installed Brocade adapters.

NOTE

Although SMI-S Provider and CIM Provider may be used interchangeably, CIM Provider is the

more generic term, while SMI-S is storage-specific.

•Target rate limiting.

You can enable or disable this feature on specific ports. Target Rate Limiting relies on the

storage driver to determine the speed capability of a discovered remote ports, then uses this

information to throttle FCP traffic rate to slow-draining targets. This reduces or eliminates

network congestion and alleviates I/O slowdowns at faster targets.

Target rate limiting is enforced on all targets that are operating at a speed lower than that of

the target with the highest speed. If the driver is unable to determine a remote port’s speed, 1

Gbps is assumed. You can change default speed using BCU commands. Target Rate Limiting

protects only FCP write traffic.

•N_Port ID Virtualization (NPIV).

Allows multiple N_Ports to share a single physical N_Port. Multiple Fibre Channel initiators can

share this single physical port and reduce SAN hardware requirements.

•N_Port Trunking works in conjunction with the Fibre Channel trunking feature on Brocade

switches, whereby the Fabric Operating System (OS) provides a mechanism to trunk two switch

ports of the same port group into one link. When trunking is enabled, two physical ports

belonging to the same Brocade dual-port adapter are trunked together to form a single pipe.

This provides advantages such as the following:

-Simplified management - for example, zoning and VM setup only require one WWN instead

of two if using two different ports.

-More VMs can be deployed on a single server.

-Higher throughput for such applications as video streaming.

-Single failures within a port group are completely transparent to upper level applications.

The following licenses must be installed on the switch connected to the HBA port or Fabric

Adapter port configured in HBA mode. Note that this is in line with the licenses required on the

switch for QoS to work with the adapter.

-Server Application Optimization (SAO) license

-Trunking license

30 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter features

Before enabling trunking, consider the following requirements:

-When trunking is enabled, a trunked logical port (Port 0) is created and reported per HBA

or Fabric Adapter port configured in HBA mode. Most BCU commands are applicable in

this logical port's context only.

-When configuring Fabric Zones and LUN Masking for Storage, use the PWWN for adapter

port 0.

-Both adapter ports should be connected to the same port group on the switch.

-Only two ports on the same adapter can participate in trunking and both of these should

be operating at the same speed.

-N_Port Trunking is supported on dual port HBA and Fabric Adapter models only.

-To enable or disable trunking on the adapter, you must perform configuration tasks on

both the switch using Fabric OS commands, as well as the adapter using BCU commands

and HCM. Refer to the Brocade Fabric OS Administrator’s Guide and Brocade Adapters

Administrator’s Guide for details.

•Server Application Optimization (SAO). When used with Brocade storage fabrics with enabled

SAO licensing, Brocade HBAs and Fabric Adapter ports configured in HBA mode can use

advanced Adaptive Networking features, such as QoS, designed to ensure Service Level

Agreements (SLAs) in dynamic or unpredictable enterprise-class virtual server environments

with mixed-SLA workloads.

•End-to-end link beaconing between an HBA port or Fabric Adapter port configured in HBA mode

and switch port to which it connects. (Requires Brocade Fabric OS 6.3x or above.)

•Boot over SAN. This feature provides the ability to boot the host operating system from a boot

device located somewhere on the SAN instead of the host’s local disk or direct-attached Fibre

Channel storage. Specifically, this “boot device” is a logical unit number (LUN) located on a

storage device. Booting from direct-attached Fibre Channel storage is also supported.

•Fabric-based boot LUN discovery, a feature that allows the host to obtain boot LUN information

from the fabric zone database.

NOTE

This feature is not available for direct-attached targets.

•Support for Hyper-V. Hyper-V consolidates multiple server roles as separate virtual machines

(VMs) using the Windows Server 2008 operating system and provides integrated management

tools to manage both physical and virtual resources.

•Support for Windows Preinstallation Environment (WinPE), a minimal operating system with

limited services for Windows Server or Windows Vista used for unattended deployment of

workstations and servers. WinPE is designed for use as a standalone preinstallation

environment and as a component of other setup and recovery technologies. WinPE is

supported by Brocade Windows 2008 adapter drivers.

•Support for Windows Server Core, a minimal server option for Windows Server 2008 operating

systems that provides a low-maintenance server environment with limited functionality. All

configuration and maintenance is done through command line interface windows or by

connecting to a system remotely through a management application. Windows Server Core is

supported by Windows Server 2008 adapter drivers.

•Support for MSI-X, an extended version of Message Signaled Interrupts (MSI), defined in the

PCI 3.0 specification. MSI-X helps improve overall system performance by contributing to lower

interrupt latency and improved utilization of the host CPU. MSI-X is supported by Linux RHEL 5,

RHEL 6, SLES 10, SLES 11, Windows 2008, and ESX Server 4.0, 4.1, and 5.0.

Brocade Adapters Installation and Reference Manual 31

53-1002144-01

Adapter management features 1

•Point-to-point topology.

•Management support for Storage Management Initiative Specification (SMI-S).

•Fibre Channel-Security Protocol (FC-SP) providing device authentication through key

management.

•FCoE Initialization Protocol (FIP) support for the following:

-FIP 2.0.

-preFIP and FIP 1.03.

-FIP Discovery protocol for dynamic FCF discovery and FCoE link management.

-FPMA and SPMA type FIP fabric login.

-FIP VLAN discovery.

-FIP discovery solicitation and FCP discovery.

-Login (FIP and FCoE).

-FIP link down handling.

-FIP version compatibility.

-FIP keep alive.

-FIP clear virtual links.

•Internet Protocol over Fibre Channel (IPFC) driver

This supports transmission of IP traffic over Fibre Channel links. This driver is only included in

the Linux “noarch” RPM package (brocade_driver_linux_<version>.tar.gz).

•vHBA

Virtual HBAs (vHBAs) are virtual port partitions that appear as virtual or logical HBAs to the

host operating system. Multiple vHBAs are not supported, therefore you cannot create or

delete them from an adapter. For more information, refer to“I/O virtualization” on page 16.

Adapter management features

The Host Connectivity Manager (HCM) and Brocade Command Line Utility (BCU) are the primary

management tools for HBAs, CNAs, and Fabric Adapters. You can load HCM as an optional

application through the Brocade Adapter Software Installer (BASI). BCU loads with the driver

package either through BASI or HCM. This section summarizes some of the features available with

these tools for managing CNAs, HBAs, and Fabric Adapters.

The Brocade Network Advisor also provides management features for adapters, such as adapter

discovery, in-context launch of HCM, authentication, and other features. Refer to the following

manuals for more details:

•Brocade Network Advisor SAN User Manual

•Brocade Network Advisor SAN and IP User Manual

Simple Network Management Protocol provides an industry-standard method of monitoring and

managing CNAs and Fabric Adapter ports configured in CNA or NIC mode. Refer to “Simple Network

Management Protocol” on page 34 for details.

32 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter management features

For the Brocade 1007 CNA, BIOS and UEFI boot code support Advanced Management Module

(AMM) connectivity and Blade Center Open Fabric Manager (BOFM) for configuring SAN and LAN

connections SAN target selection, and WWN virtualization. For more information, refer to

“BladeCenter Open Fabric Manager (BOFM)” on page 34.

This section describes the features associated with all models of the following types of Brocade

adapters:

•Fabric Adapters - Refer to the following subsections depending on your AnyIO and SFP port

configurations:

-“General adapter management” on page 32.

-“CNA management” on page 33, for ports configured in CNA or NIC modes.

-“HBA management” on page 36, for ports configured in HBA mode.

-“NIC Management” on page 35 for ports configured in NIC mode.

-“Fabric Adapter management” on page 36

•CNAs- Refer to the following subsections:

-“General adapter management” on page 32.

-“CNA management” on page 33.

•HBAs - Refer to the following subsections:

-“General adapter management” on page 32.

-“HBA management” on page 36.

General adapter management

Use BCU commands and HCM for installing, configuring, troubleshooting, and monitoring the

adapter and device connections. General HBA, CNA, and Fabric Adapter management functions

include the following:

•Discovery of adapters and connected storage devices

•Adapter diagnostics

•Event notifications for adapter conditions and problems

•Supportsave

•Port statistics

•Host security authentication

•Port logging level configuration

•Port configuration

•Virtual port configuration

•Virtual port statistics display

•Logical port statistics display

•Interrupt control coalescing

•Performance monitoring

Brocade Adapters Installation and Reference Manual 33

53-1002144-01

Adapter management features 1

Fabric Adapter management

Use BCU commands, HCM, and Simple Network Management Protocol (SNMP) to manage Fabric

Adapter ports. For a summary of available management features using HCM and BCU, refer to one

of the following sections, depending on whether the Fabric Adapter port is configured in CNA, HBA,

or NIC modes.

•“CNA management” on page 33

•“HBA management” on page 36

•“NIC Management” on page 35

CNA management

Use BCU commands and HCM to manage CNAs and Fabric Adapter ports configured in CNA mode.

Other available management tools include Simple Network Management Protocol (SNMP) and

BladeCenter Open Fabric Manager (Brocade 1007 adapter only).

FCoE management

HCM and BCU provide the provides the following functions for CNAs and for Fabric Adapter ports

configured in CNA mode.

•CNA port statistics display

•FCoE ports configuration

•Fibre Channel Security Protocol (FC-SP) configuration

•Enabling target rate limiting

•vHBA statistics monitoring

•Port, target, and Fibre Channel Protocol (FCP) operation monitoring

•Security features for FCoE access (FC-SP) configuration

•Virtual FCoE ports creation

•FCoE statistics display

•vNIC statistics display

•Fabric statistics display

•FCP IM Module statistics display

•Historical statistics

Data Center Bridging management

HCM and BCU provide the provides the following functions for CNAs and for Fabric Adapter ports

configured in CNA mode.

•DCB port statistics

•DCB statistics

•FCP IM Module statistics

•Historical statistics

34 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter management features

Ethernet management

HCM and BCU commands provide the provide the following functions for CNAs and for Fabric

Adapter ports configured in CNA or NIC modes:

•Teaming configuration

•Ethernet port statistics display

•vNIC statistics display

•VLAN configuration

•VLAN statistics display

•Ethernet logging level configuration

•VLANs over teaming configuration

•Persistent binding configuration

•NIC teaming, and VLAN statistics monitoring

•Preboot eXecution Environment (PXE) boot configuration

BladeCenter Open Fabric Manager (BOFM)

The Brocade 1007 CNA , BIOS and UEFI boot code support Advanced Management Module (AMM)

connectivity and BOFM for configuring SAN and LAN connections, SAN target selection, and WWN

virtualization. For more information, refer to the Installation and User’s Guide shipped with your

adapter.

NOTE

For CNAs, BOFM support in the Brocade Option ROM expects non-zero values for both PWWN and

NWWN for the FCoE port. If any of these values are zero, the FCoE link will not come up, and the port

status will display as Linkdown. Be sure to configure valid non-zero values for PWWN/NWWN when

using BOFM.

Simple Network Management Protocol

Simple Network Management Protocol (SNMP) is supported by CNAs and by Fabric Adapter for

ports configured in CNA or NIC mode.

SNMP is an industry-standard method of monitoring and managing network devices. This protocol

promotes interoperability because SNMP-capable systems must adhere to a common set of

framework and language rules. SNMP is based on manager-agent model consisting of an SNMP

manager, an SNMP master-agent, a database of management information (MIB), managed SNMP

devices, and the SNMP protocol.

Brocade CNA and Fabric Adapters provide the agent and management information base (MIB). The

SNMP master agent provides an interface between the manager and the managed physical

device(s) and uses the SNMP protocol, to exchange information defined in the MIB. Brocade

adapter SNMP support is through an extension to the master agent, called the subagent, which

processes SNMP queries for Brocade adapters. The subagent is only supported on Linux and

Windows systems. SNMP subagent files are copied to your host system when you install adapter

software through HCM and the Brocade Adapter Software Installer (BASI). You can then elect to

install the subagent using Brocade Windows or Linux installation scripts.

Brocade Adapters Installation and Reference Manual 35

53-1002144-01

Adapter management features 1

The agent accesses information about the adapter and makes it available to an SNMP network

management station. When active, the management station can get information or set information

when it queries the agent. The agent uses variables (also known as managed or MIB objects) to

report data such as the following.

•Model number

•Type of adapter

•Serial number

•Current status

•Hardware version

•Port statistics

•VLAN attributes and statistics

•Team attributes and statistics

All managed objects are contained in the MIB provided by the adapter. For information on the MIB

groups and objects supported by the adapter, refer to

The SNMP master agent also sends unsolicited messages (called traps) to the manager. These

traps, generated by the Brocade SNMP subagent, are for network adapter conditions that require

administrative attention. Adapter traps included notification of VLANs added or removed; team

members added or removed; team failover, failback, team added, and team removed; and port link

up and link down events.

For details on MIB groups and objects supported by Brocade adapters, refer to Appendix B, “MIB

Reference”.

NIC Management

Ports on Fabric Adapters only can be set to operate in NIC mode. These ports appear as 10 GbE

NICs to the host operating system.

BCU commands and HCM provide features for configuring, troubleshooting, and monitoring NIC

connections to the Ethernet LAN. For an overview, refer to “Ethernet management” on page 34. For

details, refer to the Brocade Adapter Administrator's Guide for full information.

In addition, BCU commands and HCM provide the following features specifically for NIC

management when Fabric Adapter ports configured in NIC or CNA mode:

•vNIC configuration (only available using BCU commands)

•vNIC teaming configuration

•vNIC statistics

•vNIC discovery and display in HCM

•vNIC enable and disable

SNMP provides an industry-standard method of monitoring and managing Fabric Adapters with

ports configured in NIC mode. For details, refer to “Simple Network Management Protocol” on

page 34.

Management applications, such as Network Advisor, provides management support for NICs,

including host and NIC discovery, in-context launch of HCM, statistics display, port and adapter

property display, and other features. Refer to the Brocade Network Advisor SAN User Manual or

Brocade Network Advisor SAN and IP User Manual.

36 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter management features

HBA management

BCU commands and HCM provide the following features for HBAs and for Fabric Adapter ports

configured in HBA mode:

•Port statistics display

•Discovery of adapters and connected storage devices in your SAN

•Adapter configuration

•Persistent binding

•End-to-end QoS

•Target rate limiting

•Performance monitoring, such as port and target statistics

•Supportsave operation

•Adapter diagnostics display

•N_Port trunking configuration

•Adapter, port, target, and Fibre Channel Protocol (FCP) operation monitoring

•Security features for adapter access.

•Event notifications for adapter conditions and problems.

•Monitor and analyze traffic between N_Port pairs through a mirrored port on the switch (HBA

Analyzer)

•Virtual FC ports creation

•vHBA statistics display

•FCP IM Module statistics display

•Fabric statistics display

•Port configuration

•LUN masking configuration

•Historical statistics

HCM and BCU commands provide the following features only for Brocade Fabric Adapter ports

configured in HBA mode:

•vHBA discovery and display in HCM

•vHBA enable and disable

•vHBA data query

•vHBA statistics display

Fabric Adapter management

Management features in BCU commands and HCM for Fabric Adapters are summarized under the

following sections, depending on the operating mode set for the Fabric Adapter port:

•Port set to CNA mode - “CNA management” on page 33

•Port set to HBA mode - “HBA management” on page 36

•Port set to NIC mode - “NIC Management” on page 35

Brocade Adapters Installation and Reference Manual 37

53-1002144-01

Adapter software 1

In addition to features summarized in the preceding sections of this guide, there are some unique

management features for Fabric Adapters, not available for HBAs and CNAs, including the

following:

•Configure port modes (CNA, HBA, NIC)

•Create, delete, enable, and disable vNICs.

•Query for information, display statistics, and set bandwidth for vNICs.

•Discover and display vNICs

•Discover and display vHBAs

•Enable and disable vHBAs

•Query for information and display statistics for vHBAs

Adapter software

Brocade adapter software includes the appropriate driver package for your host system,

management utilities, and the HCM application. You can install all of these components or

individual components using the Brocade Adapter Software Installer (BASI) GUI-based application

or commands.

Driver packages

A single adapter driver “package” is available for installing to each supported host operation

system and platform. Refer to “Software installation and driver packages” on page 43 for a list of

packages for each support host systems.

Three types of adapter drivers are provided in installation packages:

•Storage driver (all adapters)

This driver provides Fibre Channel frame transport for Brocade HBAs and Fabric Adapter ports

configured in HBA mode, as well as FCoE transport for Brocade CNAs. The installer logic

detects either a FCoE or Fibre Channel network and the appropriate driver support is provided

automatically.

NOTE

The storage driver will claim all installed Brocade adapters installed in a system. This driver will

be used instead of the driver originally installed for these adapters.

•Network driver (CNAs and Fabric Adapters only)

Driver for frame transport over Ethernet and basic Ethernet services. This driver only applies to

CNAs and Fabric Adapter ports configured in CNA mode only.

•Intermediate driver (CNAs and Fabric Adapters only)

For Windows systems only, this provides support for multiple VLANs on ports and teams. This

driver applies to CNAs and to Fabric Adapter ports configured in CNA or NIC mode. Note that

installing this driver changes the behavior of the network driver because it alters the binding of

the driver and protocols in the network stack. Before installing the intermediate driver, network

traffic goes from the protocols layer to the network driver directly. After installation, virtual

38 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter software

LANs created by BCU commands or HCM options are directly bound to upper protocols. All

traffic goes from the protocols layer to the VLANs, then to the network driver. You should not

enable TCP, IPV4, or other protocols or services for the network driver after installing the

intermediate driver.

Each driver package contains the following components:

•Driver for your host system. In most cases, both the required storage and network drivers are

included in installation packages. For systems not supporting network drivers, only the storage

driver is included.

•Firmware

Firmware is installed in the adapter’s on-board flash memory and operates on the adapter’s

CPU. It provides an interface to the host device driver and off-loads many low-level

hardware-specific programming tasks typically performed by the device driver. The firmware

provides appropriate support for both the storage and network drivers to manage the

hardware. Depending on the adapter model, it also provides the following functions:

-For CNAs and for Fabric Adapters with ports configured in CNA mode, it manages the

physical Ethernet link to present an Ethernet interface to the network driver and a virtual

FCoE link to the storage driver once DCB compliance is established for the link.

-For Fabric Adapters with ports configured in NIC mode, it manages the physical Ethernet

link to present an Ethernet interface to the network driver.

ATTENTION

The LLDP/DCBCXP engine is implemented in the firmware. Therefore, any other instance of

LLDP agent or software must not be used with a CNA or Fabric Adapter port configured in CNA

mode.

Management utilities

The following management Utilities are included with all driver packages.

•Brocade Command Line Utility (BCU)

An application from which you can enter commands to monitor, install, and configure Brocade

adapters.

•Brocade Adapter Software Installer (BASI).

This includes a GUI-based installer and command-line installer that provides options for

installing all adapter drivers, all adapter drivers and HCM, or HCM only for a specific operating

system and platform.

•Installation scripts.

These allow you to install drivers, the HCM agent, and utilities to your host system without

using the Brocade Adapter Software Installer.

For Windows systems, download the .exe file appropriate for your Windows system, extract

files, then run the brocade_installer.bat command.

Brocade Adapters Installation and Reference Manual 39

53-1002144-01

Adapter software 1

For Linux systems, download and extract the appropriate tar.gz file for your system. After

extracting files, execute the following commands, depending on your system:

-RHEL systems.

brocade_install_rhel.sh

-SLES systems

brocade_install_sles.sh

For VMware ESX and ESXi systems, download and extract the appropriate tar.gz file for your

system. After extracting files, execute the following commands, depending on your system:

-VmWare ESX 4.X

brocade_install.sh

-VmWare ESX 5.X

brocade_install_esxi.sh

-VmWare ESXi systems, use vMA commands and procedures under “Installation on ESXi

4.0 and 4.1 systems” on page 101.

For Solaris systems, download and extract the appropriate .tar file for your system. After

extracting the file, execute the brocade_install.sh command to install software.

•HCM agent

The agent provides an interface for managing adapters installed on the host through the HCM

application.

•CIM Provider

CIM Provider packages installed on your host system allow any standard Common Information

Model (CIM) and SMI-S based management software to manage installed Brocade adapters.

The appropriate CIM Provider rpm or msi package loads to your host system when you install

the network driver package using installation scripts or installation commands that are

“native” to your host system.

NOTE

The CIM Provider files do not load when you use the Brocade Adapter Software Installer (B ASI)

to install driver packages.

NOTE

If you want to integrate the provider with Common Information Model Object Manager (CIM

OM), install the SMI-S Provider packages using instructions in the SMI-S Provider for Brocade

Adapters Installation Guide or CIM Provider for Brocade Adapters Installation Guide.

NOTE

Although SMI-S Provider and CIM Provider may be used interchangeably, CIM is the more

generic term, while SMI-S is storage-specific.

40 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter software

•SNMP subagent.

Simple Network Management Protocol (SNMP) is an industry-standard method of monitoring

and managing network devices. SNMP is supported by CNAs and by Fabric Adapter ports

configured in CNA or NIC mode. SNMP support is provided through an extension to the SNMP

master agent, called the subagent, which processes SNMP queries for Brocade adapters. The

subagent is only supported on Linux and Windows systems. For more information on SNMP

support, refer to “Simple Network Management Protocol” on page 34.

SNMP subagent files are copied to your host system when you install adapter software through

HCM and the Brocade Adapter Software Installer (BASI). You can elect to install the subagent

using Brocade Windows or Linux installation scripts. Refer to “Installing SNMP subagent” on

page 109.

Operating system support

The following table provides general information on compatible software operating systems and

environments for Brocade adapter network and storage drivers.

TABLE 7 Operating system support for network and storage drivers

Operating System x86 x64 IA-64 SPARC

Windows1

Windows Server 20032Both drivers

supported - 32b

Both drivers

supported - 64b

Both drivers not

supported

N/A

Windows Server 20083Both drivers

supported - 32b

Both drivers

supported - 64b

Both drivers not

supported

N/A

Windows Server 20083

R2/SP14

Both drivers not

supported - 32b

Both drivers

supported - 64b

Both drivers not

supported

N/A

Windows 74Both drivers

supported - 32b

Both drivers

supported - 32b

Both drivers - not

supported

N/A

Microsoft WinPE 3.x for

Windows 2008

Standard/Enterprise Server

Both drivers

supported - 32b

Both drivers

supported - 64b

Both drivers not

supported

N/A

Windows Server Core for

Windows 2008

Both drivers - 32b Both drivers -

64b5

Both drivers - not

supported

N/A

Linux

Red Hat Enterprise Linux

(RHEL) 4.9, 5.5, 5.6, 6.0,

6.1

Both drivers

supported - 32b

Both drivers

supported - 32b,

64b

Both drivers not

supported

Both drivers not

supported

SUSE Linux Enterprise

Server (SLES) 10.3, 10.4,

11.0, 11.1

Both drivers

supported - 32b

Both drivers

supported - 32b,

64b

Both drivers not

supported

Both drivers not

supported

Xen Hypervisor Both drivers

supported - 32b

Both drivers

supported - 32b,

64b

Both drivers not

supported

Both drivers -

not supported

Solaris6

Brocade Adapters Installation and Reference Manual 41

53-1002144-01

Adapter software 1

Hypervisor support

Table 8 describes Hypervisor support for Brocade adapters.

NOTE

For the latest support information on specific operating system release levels, service pack levels,

and other patch requirements, please refer to the latest release notes for your adapter.

Solaris 10.0 Network driver

supported - 32b

Storage driver

supported - 32b

Network driver

supported - 32,

64b

Storage driver

supported - 32b,

64b

Both drivers not

supported

Both drivers

supported.

VMware ESX/ESXi

ESX 4.0, 4.1, 5.0 N/A Both drivers

supported - 64b

N/A N/A

Oracle Enterprise Linux

(OEL) 5.6, 6.0

Both drivers

supported - 32b

Both drivers

supported - 64b

N/A N/A

Oracle VM 3.0 Storage driver

supported -32b

N/A N/A N/A

1. For Windows, the Storport miniport driver is supported (there is no support for the SCSI miniport driver).

2. Support for Windows 2003 is limited to Fabric Adapter ports configured in HBA mode and HBAs. Hot fix

KB932755 (or later) is the minimum requirement and KB943545 is recommended.

3. For Windows 2008, hot fix KB968675 and KB2490742 are recommended. Hot fix KB958015 is recommended

for CNAs and Fabric Adapter ports configured in CNA mode. For Windows 2008 R2 KB977977 is recommended for

CNAs and Fabric Adapter ports configured in CNA mode

4. Supported by Windows 2008 drivers

5. Not supported on IEM64T systems.

6. For Solaris systems, only the Leadville-based storage driver is supported on adapters that support Solaris

systems. Note that the Solaris driver does not support NPIV, authentication, and fabric device management interface

(FDMI). Brocade 804 and 1007 adapters are not supported on Solaris systems.

TABLE 8 Hypervisor support for Brocade adapters

System x86 x84 Intel IA64 SPARC

VMware ESX 4.0, 4.1 N/A Yes N/A N/A

VMware ESX 5.0 N/A N/A N/A N/A

Windows Server 2008 Hyper-V N/A yes N/A N/A

RHEVH 6.x N/A yes N/A N/A

Linux XEN yes yes N/A N/A

Linux KVM N/A yes N/A N/A

Oracle VM 3.0 N/A yes N/A N/A

Citrix XenServer 6.0 N/A yes N/A N/A

TABLE 7 Operating system support for network and storage drivers (continued)

42 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter software

Host Connectivity Manager

Host Connectivity Manager (HCM) is a graphical user interface (GUI) based management software

for installing, configuring, monitoring, and troubleshooting installed adapters. HCM performs the

“client” function for the management software. You can only install HCM using the Brocade

Adapter Software Installer. The HCM agent is installed with the driver package on systems where

adapters are installed.

Install HCM on the host system containing Brocade adapters for local management or install on a

network-attached system for remote management of these adapters. Refer to “CNA management”

on page 33 or “HBA management” on page 36 for more information. HCM is available for all

commonly used operating systems, such as Windows, Solaris, and Linux platforms. HCM is

supported on VMware, but only when installed on the “guest” operating system. HCM is not

supported on VMware ESXi systems.

NOTE

HCM is compatible with any version of the driver package. HCM can also manage the current

version, as well as all previous versions of the HCM agent.

Boot code

The adapter boot code contains the following:

•PCI BIOS 2.1 or later, PCI firmware 3.0

Boot code for PCI system

•BIOS

Boot code for x86 and x64 platforms

•Unified Extensible Firmware Interface (UEFI)

Boot code for UEFI systems

NOTE

UEFI is not supported on the Brocade 804 adapter.

•Adapter firmware

The adapter boot code loads from Brocade adapter memory into system memory and integrates

with the host system (server) BIOS during system boot to facilitate booting from LUNs, which are

also referred to as “virtual drives,” “boot disks,” and “boot devices.”

To keep drivers and boot code synchronized, be sure to update your adapter with the latest boot

code image on the adapter website using these steps:

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Downloads list to display appropriate download files or

download the ISO image.

You can download driver packages or an ISO 9660 (.iso) optical disk image files to configure boot

LUNs and boot images for adapters installed in systems without operating systems or hard drives.

Refer to Chapter 4, “Boot Code” for complete information.

Brocade Adapters Installation and Reference Manual 43

53-1002144-01

Adapter software 1

CIM Provider

CIM Provider allows third-party SMI-S and CIM-based adapter management software to manage

Brocade adapters installed on a host system.

The appropriate CIM Provider rpm or msi package loads to your host system when you manually

install the driver package using instructions under “Using software installation scripts and system

commands” on page 89. The CIM Provider files do not load when you use the Brocade Adapter

Software Installer. The CIM Provider software is also available from the Brocade website at

www.brocade.com/adapters.

For more information on CIM Provider, including operating systems supported and available

installation packages, refer to the CIM Provider for Brocade Adapters Installation Guide.

NOTE

Although SMI-S Provider and CIM Provider may be used interchangeably, CIM is the more generic

term. SMI-S is storage-specific.

Adapter event messages

When applicable events occur during adapter operation, the adapter driver generates event

messages. These messages are captured in your host system logs and also display in the HCM

master log. All of these event log messages are contained in HTML files that load to your system

when you install adapter drivers. You can view these HTML files using any internet browser

application.

For details on event messages, event log locations on supported operating systems, and where

adapter event message HTML files are loaded to your host system, refer to the “Tools for Collecting

Data” chapter in the Brocade Adapters Troubleshooting Guide. In addition, you can view all event

messages in the “Message Reference” appendix of the same guide.

Software installation and driver packages

Table 9 on page 44 describes the software installation packages that you can download for each

supported host platform. The table provides the package name, host system supported, and

package description. Using the table, you can select the following to download for your specific host

platform:

•The Brocade Adapter Software Installer (.exe) application to install the driver package, HCM, or

driver package and HCM. Installation instructions are provided under “Using the Brocade

Adapter Software Installer” on page 68.

•A driver package that you can install using an installation script or “native” procedures for your

host’s operating system. Installation procedures are provided under “Using software

installation scripts and system commands” on page 89.

•An ISO 9660 (.iso) optical disk image containing all files listed in the supported software

installation packages table (Table 9 on page 44) and boot installation packages table

(Table 10 on page 51). Use this image to create CDs, DVDs, or USB drives to carry with you for

installation. The image also contains product documentation, such as product manuals,

current release notes, and licensing information. For Windows systems only, if using a DVD

created with the ISO image, the correct installer program will automatically execute for your

system. Make sure that the autorun feature is enabled.

44 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter software

Note that in the following ISO file name that the <date> will be replaced by the date of the

software.

brocade_adapter_software_ISO_<date>.iso

Download the driver package and boot image for your host system operating system and platform

from the Brocade adapter website. Use the following steps.

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Downloads list to display appropriate download files or

download the ISO image.

NOTE

In the package name, <version> indicates the software version number (for example v2-0-0), which

will change for each release. The <platform> indicates the host processor type, such as x86 or

x86_64. Network drivers are not supported on HBAs and Fabric Adapter ports configured in HBA

mode.

NOTE

Although the following table lists all adapter software packages that you can download for specific

operating systems and platforms, your adapter release may not be supported some of these

operating systems and platforms. Refer to “Operating system support” on page 40 and the latest

release notes for your adapter for more information.

TABLE 9 Supported software installation packages

Operating

System and

Platform

Brocade Adapter Software Installer Driver Package

Windows

Server

2003

(x86)

brocade_adapter_software_installer_

windows_<version>.exe

Installs HCM and appropriate driver

package.

brocade_driver_win2003_x86_<version>.exe

Storport miniport storage and network drivers with HCM

Agent for Standard/Enterprise Server on x86 platforms.

This package also contains installer script

(brocade_installer.bat).

Windows

Server

2003

(x86_64)

brocade_adapter_software_installer_

windows_<version>.exe

Installs HCM and appropriate driver

package.

brocade_driver_win2003_x64_<version>.exe

Storport miniport storage and network drivers with HCM

Agent for Standard/Enterprise Server on the EM64T and

AMD64 platforms. This package also contains installer

script (brocade_installer.bat).

Windows

Server

2008

(x86)1

brocade_adapter_software_installer_

windows_<version>.exe

Installs HCM and appropriate driver

package.

brocade_driver_win2008_x86_<version>.exe

Storport miniport storage and network drivers with HCM

Agent for Standard/Enterprise Server on EM64T and

AMD64 platforms. This package also contains installer

script (brocade_installer.bat).

Windows

Server

2008 R2

(x64)2

brocade_adapter_software_installer_

windows_<version>.exe

Installs HCM and appropriate driver

package.

brocade_driver_win2008_R2_x64_<version>.exe

Storport miniport storage and network drivers with HCM

Agent for Standard/Enterprise Server on EM64T and

AMD64 platforms. This package also contains installer

script (brocade_installer.bat).

Brocade Adapters Installation and Reference Manual 45

53-1002144-01

Adapter software 1

Windows

Server

2008

(x64)

brocade_adapter_software_installer_

windows_<version>.exe

Installs HCM and appropriate driver

package.

brocade_driver_win2008_x64_<version>.exe

Storport miniport storage and network drivers with HCM

Agent for Standard/Enterprise Server on EM64T and

AMD64 platforms. This package also contains installer

script (brocade_installer.bat).

Linux RHEL

4.9

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel4_<version>.tar.gz4

Linux RHEL

4.9

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel4_<version>.tar.gz4

Linux RHEL

5.5, 5.6

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel5_<version>.tar.gz4

Linux RHEL

5.5, 5.6

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel5_<version>.tar.gz4

Linux RHEL

6.0, 6.1

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.5

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel6_<version>.tar.gz4

Linux RHEL

6.0, 6.1

(x86_x64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.5

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_rhel6_<version>.tar.gz4

Linux SLES

10 SP3

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles10sp3_<version>.tar.gz4

Linux SLES

10 SP3

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles10sp3_<version>.tar.gz4

Linux SLES

10 SP4

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles10sp4_<version>.tar.gz4

Linux SLES

10 SP4

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles10sp4_<version>.tar.gz4

TABLE 9 Supported software installation packages (continued)

Operating

System and

Platform

Brocade Adapter Software Installer Driver Package

46 Brocade Adapters Installation and Reference Manual

53-1002144-01

Adapter software

Linux SLES

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles11_<version>.tar.gz4

Linux SLES

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles11_<version>.tar.gz4

Linux SLES

11 SP1

(x86)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles11sp1_<version>.tar.gz4

Linux SLES

11 SP1

(x86_64)

brocade_adapter_software_installer_

linux_<version>.bin

Installs HCM and appropriate driver

package.

•brocade_driver_linux_<version>.tar.gz3

•brocade_driver_linux_sles11sp1_<version>.tar.gz4

Solaris

10.0

(x86)

brocade_adapter_software_installer_

solaris10_x86_<version>.bin

Installs HCM and appropriate driver

package for operating system and

platform.

brocade_driver_solaris10_<version>.tar6

Leadville-based storage driver with user applications, such

as HCM Agent, Brocade Adapter Software Installer, and

BCU, for x86 platforms.

Solaris

10.0

(x86_x64)

brocade_adapter_software_installer_

solaris10_x86_<version>.bin

Installs HCM and appropriate driver

package for operating system and

platform.

brocade_driver_solaris10_<version>.tar6

Leadville-based storage driver with user applications, such

as HCM Agent, Brocade Adapter Software Installer, and

BCU, for x86 platforms.

Solaris

10.0

SPARC

(x86_64)

brocade_adapter_software_installer_

solaris10_sparc_<version>.bin

Installs HCM and appropriate driver

package.

brocade_driver_solaris10_<version>.tar6

Leadville-based storage driver with user applications, such

as HCM Agent, Brocade Adapter Software Installer, and

BCU, for SPARC platforms.

VMware

ESX/ESXi

(x64)

4.0

Note: Use appropriate Brocade

Adapter Software Installer listed in

this column to install HCM on

applicable “guest” operating system

only. The software installer is not

supported on ESX systems. The HCM

agent is not supported on ESXi

platforms.

brocade_driver_esx4x_<version>.tar.gz7

5.0 storage and network drivers with user applications,

such as HCM Agent, Brocade Adapter Software Installer,

and BCU for x86, EM64T, and AMD64 platforms.

VMware

ESX/ESXi

(x64)

4.1

Note: Use appropriate Brocade

Adapter Software Installer listed in

this column to install HCM on

applicable “guest” operating system

only. The software installer is not

supported on ESX systems. The HCM

agent is not supported on ESXi

platforms.

brocade_driver_esx41_<version>.tar.gz7

4.x storage and network drivers with user applications,

such as HCM Agent, Brocade Adapter Software Installer,

and BCU for x86, EM64T, and AMD64 platforms.

TABLE 9 Supported software installation packages (continued)

Operating

System and

Platform

Brocade Adapter Software Installer Driver Package

Brocade Adapters Installation and Reference Manual 47

53-1002144-01

Adapter software 1

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems.

NOTE

For the latest support information on specific operating system release levels, service pack levels,

and other patch requirements, please refer to the latest release notes for your adapter.

Downloading software and documentation

To download the software installer, driver packages, boot code, driver update disks, the CIM

provider, and documentation, perform the following steps:

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Download list to display appropriate download files or

download the ISO image.

VMware

ESX/ESXi

(x64)

5.0

Note: Use appropriate Brocade

Adapter Software Installer listed in

this column to install HCM on

applicable “guest” operating system

only. The software installer is not

supported on ESX systems. The HCM

agent is not supported on ESXi

platforms.

brocade_driver_esx50_<versison>.tar.gz7

4.x storage and network drivers with user applications,

such as HCM Agent, Brocade Adapter Software Installer,

and BCU for x86, EM64T, and AMD64 platforms.

1. Windows 2008 x86 drivers are used for Windows 7 x86 support.

2. Windows 2008 R2 X64 drivers support Windows 7 x64.

3. This package is the source-based RPM for all RHEL and SLES Linux driver distributions, as well as user

applications, such as HCM Agent, Brocade Adapter Software Installer, and BCU. The driver module is compiled on

the system during the RPM installation. An installer program is available for use when you untar this package. To

install this package, the appropriate distribution kernel development packages must be installed for the currently

running kernel, which include the gcc compiler and the kernel sources. Although this package installs SLES drivers,

the error message “bfa” or “bna” module not supported by Novell, setting U taint flag” displays. You can complete

installation and use this driver although in this format it is not certified or supported by Novell, Inc.

4. This package contains the latest precompiled RPMs for either RHEL or SLES distributions, as well as user

applications, such as HCM Agent, Brocade Adapter Software Installer, and BCU. An installer program is available for

use when you untar this package.

5. HCM is a 32-bit application. To use HCM on Linux RHEL 6.0 x64 systems, you must install the x32-compatible

libraries because they are not installed by default.

6. This package contains all network drivers, storage drivers, management utilities, and installation script for

Solaris distributions

7. This package contains all network drivers, storage drivers, management utilities, and installation script for

VMware ESX distributions. Note that you can use the VMware Image Builder PowerCLI to create a

brocade_esx50_<version>.zip offline bundle and brocade_esx50_<version>.iso ESX 5.0 installation image that

includes brocade drivers and utilities. Refer to your Image Builder documentation for details on using Image Builder

PowerCLI.

TABLE 9 Supported software installation packages (continued)

Operating

System and

Platform

Brocade Adapter Software Installer Driver Package

48 Brocade Adapters Installation and Reference Manual

53-1002144-01

Items shipped with your adapter

Software installation options

You can use the Brocade Adapter Software Installer or options in “native” installation scripts and

commands to install software on your host system:

•Brocade Adapter Software Installer

Use this to install the following components:

-Storage driver, network driver, and HCM

-Storage and network driver

-HCM only

For more information, refer to “Using the GUI-based installer” on page 69.

•Brocade “native” installer scripts and commands

For CNAs, use this to install the storage driver, network driver, and utilities.

For HBAs and Fabric Adapter ports configured in HBA mode, use this to install the storage

driver and utilities only.

For more information, refer to “Using software installation scripts and system commands” on

page 89.

NOTE

Only one driver installation is required for all types of adapters (CNA, HBA, or Fabric Adapter)

installed in a host system.

Refer to “Software installation and driver packages” on page 43 for a complete list of driver and

software installer packages that you can download from the Brocade adapter website at

www.brocade.com/adapters. On the adapters website, navigate to the Downloads page.

Items shipped with your adapter

This section describes items shipped with your adapter.

Stand-up adapters

The following items are shipped with stand-up adapters for installation:

•Adapter with the following PCI mounting bracket installed, depending on your adapter model:

-Low-profile PCI mounting bracket (all CNA and HBA models)

-Standard (full-height) PCI mounting bracket (Fabric Adapters)

•Loose adapter packaged with adapter, depending on your adapter model:

-Standard (full-height) PCI mounting bracket (all CNA and HBA models)

-Low-profile PCI mounting bracket (Fabric Adapters)

•One SFP or two SFPs, depending on your adapter model. Note that for CNAs and Fabric

Adapters, SFPs and copper cables may be purchased separately or shipped with the FCoE

switch.

•Adapter installation instructions

•Instructions for downloading software

Brocade Adapters Installation and Reference Manual 49

53-1002144-01

Boot installation packages 1

Mezzanine adapters

The following items may be shipped with adapters for installation, depending on the adapter model:

•Adapter

•Adapter installation instructions

•Important notices document and warranty card

•CD containing documentation for installing, removing, configuring, and troubleshooting the

adapter.

Boot installation packages

Download boot installation packages to support boot operations, such as boot from SAN, network

boot, and updating adapter boot code, from the Brocade website using the following steps:

1. Access the Brocade adapters website at www.brocade.com/adapters.

2. Navigate to the Downloads page.

3. Select your operating system from the Downloads list to display appropriate downloads.

4. On the download page, select the Boot Code area.

The following boot installation packages are available:

•Driver update disk (dud) ISO files containing the appropriate driver and necessary directory

structure to install with the host operating system on remote LUNs for boot over SAN

operations. ISO images are available for Windows 2008, Linux, Solaris, and VMware systems. A

Zip file is available for Windows 2003 and VMware ESX 5.0 systems.

NOTE

When installing the operating system to the remote boot LUN, you must use the driver update

disk (DUD) appropriate for the host operating system and platform or installation will fail. Also

note that two separate DUDs are available for each operating system to provide appropriate

storage and network files for your adapter model.

NOTE

For Microsoft Windows operating systems, the driver update disk does not verify prerequisite

checks as part of installation. Please review the operating system prerequisites and install the

necessary hotfixes after the operating system installation is complete.

•A LiveCD ISO image (live_cd.iso) containing the adapter driver, boot code, and minimum

operating system to allow you to boot BIOS-based host systems that do not have installed

operating systems or local drives. Once you boot the system, you can update the boot image on

installed adapters and configure boot from SAN using BCU commands.

NOTE

To boot UEFI-based host systems, you can create a WinPE ISO image using steps under

“Configuring fabric-based boot LUN discovery (Brocade fabrics)” on page 164. This image

contains the adapter driver, boot code, and minimum operating system to boot systems

without installed operating systems or local drives.

50 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot installation packages

•An ISO 9660 (.iso) optical disk image containing all files listed in the supported software

installation packages table (Table 9 on page 44) and boot installation packages table

(Table 10 on page 51). Use this image to create CDs or USB drives to carry with you for

installation. The image also contains product documentation, such as product manuals,

current release notes, and licensing information. For Windows systems only, if using a DVD

created with the ISO image, the correct installer program will automatically execute for your

system. Make sure that the autorun feature is enabled.

Note that in the following ISO file name, <date> will be replaced by the release date of the

software.

brocade_adapter_software_ISO_<date>.iso

Download this image from the Brocade adapters website at the Brocade adapters website

using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Perform one of the following steps:

•Select your operating system from the Downloads list to display appropriate download

files.

•Select Download ISO Image to download brocade_adapter_software_ISO_<date>.iso.

•Adapter boot code image. This contains BIOS and UEFI boot code and firmware used by the

boot code to boot from the adapter. Load this code to option ROM on the adapter using the

BCU boot --update command. Download this image from the Brocade adapters website using

the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the boot code image from the Boot Code section.

NOTE

To keep drivers and boot code synchronized, be sure to update your adapter with the latest

boot image whenever you install or update adapter driver packages. Refer to “Boot code

updates” on page 118 for instructions.

Table 10 describes the installation packages for boot support that you can download for each

supported operating system. The table provides the operating system, the driver update disk (DUD)

image, the LiveCD, and the boot code.

NOTE

Although the following table lists all boot packages that you can download for specific operating

systems and platforms, your adapter release may not be supported some of these operating

systems and platforms. Refer to “Operating system support” on page 40 and the latest release

notes for your adapter for more information.

Brocade Adapters Installation and Reference Manual 51

53-1002144-01

Boot installation packages 1

TABLE 10 Boot installation packages

Operating

System

(Platform)

Driver Update Disk Image LiveCD Boot Code

Windows

2003

(x86)

brocade_adapter_fc_w2k3_x86_dud_<version>.zip1live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Windows

2003

(x86_64)

brocade_adapter_fc_w2k3_x64_dud_<version>.zip1live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Windows

2008

(x86)

brocade_adapter_fc_w2k8_x86_dud_<version>.zip2

brocade_adapter_fcoe_w2k8_x86_dud_<version>.zip3

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Windows

2008

(x86_64)

brocade_adapter_fc_w2k8_x64_dud_<version>.zip2

brocade_adapter_fcoe_w2k8_x64_dud_<version>.zip3

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Windows

2008 R2

(x86_64)

brocade_adapter_fc_w2k8_r2_x64_dud_<version>.zip2

brocade_adapter_fcoe_w2k8_r2_x64_dud_<version>.zip3

NA brocade_adapter_

boot_fw_<version>

LInux

RHEL 4.9

(x86 and

x86_64)

brocade_adapter_rhel4_dud_<version>.iso4live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Linux RHEL

5.4, 5.5,

5.6, 6.0,

6.1 (x86)

brocade_fc_adapter_rhel54_i386_dud_<version>.iso5

brocade_nw_adapter_rhel54_i386_dud_<version>.iso6

brocade_fc_adapter_rhel55_i386_dud_<version>.iso5

brocade_nw__adapter_rhel55_i386_dud_<version>.iso6

brocade_fc_adapter_rhel56_i386_dud_<version>.iso5

brocade_nw__adapter_rhel56_i386_dud_<version>.iso6

brocade_fc_adapter_rhel60_i386_dud_<version>.iso5

brocade_nw__adapter_rhel60_i386_dud_<version>.iso6

brocade_fc_adapter_rhel61_i386_dud_version.iso5

brocade_nw_adapter_rhel61_i386_dud_version.iso6

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Linux RHEL

5.4, 5.5,

5.6, 6.0,

6.1

(x86_64)

brocade_fc_adapter_rhel54_x86_64_dud_<version>.iso5

brocade_nw_adapter_rhel54_x86_64_dud_<version>.iso6

brocade_fc_adapter_rhel55_x86_64_dud_<version>.iso5

brocade_nw_adapter_rhel55_x86_64_dud_<version>.iso6

brocade_fc_adapter_rhel56_x86_64_dud_<version>.iso5

brocade_nw_adapter_rhel56_x86_64_dud_<version>.iso6

brocade_fc_adapter_rhel60_x86_64_dud_<version>.iso5

brocade_nw_adapter_rhel60_x86_64_dud_<version>.iso6

brocade_fc_adapter_rhel61_x86_64_dud_<version>.iso5

brocade_nw_adapter_rh61_x86_64_dud_version.iso6

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Linux SLES

10, SP3,

SP4

(x86,

x86_64)

brocade_adapter_sles10sp3_dud_<version>.iso4

brocade_adapter_sles10sp4_dud_<version>.iso4

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Linux SLES

brocade_adapter_sles11_dud_<version>.iso4live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

52 Brocade Adapters Installation and Reference Manual

53-1002144-01

Downloading software and publications

To download all HBA software and boot code, use the following steps.

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Downloads list to display appropriate download files.

4. On the download screen, select the appropriate software from the Software Installer, drivers,

boot code, and Driver Update Disks (DUD) areas. Select product publications from the

Documentation section.

5. If downloading software, acknowledge the adapter Download Agreement.

Linux SLES

11 SP1

brocade_adapter_sles11sp1_dud_<version>.iso4live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

Solaris 10 brocade_adapter_sol_dud_<version>.iso7live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

VMware

ESX/ESXi

4.0

bfa_esx4x_<version>.iso8

bna_esx4x_<version>.iso9

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

VMware

ESX/ESXi

4.1

bfa_esx41_<version>.iso8

bna_esx41_<version>.iso9

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

VMware

ESX/ESXi

5.0

bfa_esx50_<version>.zip8

bna_esx50_<version>.zip9

live_cd_

<version>.iso

brocade_adapter_

boot_fw_<version>

1. Windows 2003 (w2k23) v3-0-0-0 only supports Fabric Adapter ports configured in HBA mode. Windows 2003

(w2k23) v2-3-0-2 only supports HBAs. Note that for Windows 2003, boot over SAN is not supported on CNAs, but only

on HBAs and Fabric Adapter HBA ports. After installing the boot package, be sure to upgrade to the latest driver.

2. 2008 DUDs support Fabric Adapters and HBAs. Zip file contains files for floppy disk.Windows.

3. Network drivers for CNAs and for Fabric Adapter ports configured in CNA or NIC mode. Zip file contains files for

floppy disk. For network boot, the network driver is injected as part of the PXE Server prior to Windows installation.

The driver is passed over during PXE installation on the server.

4. Storage drivers and network drivers are part of ISO package.

5. Drivers for HBAs, CNAs, and Fabric Adapter ports for boot over SAN. Note that you can use the VMware Image

Builder PowerCLI to create a brocade_esx50_<version>.zip offline bundle and brocade_esx50_<version>.iso ESX

5.0 installation image that includes brocade drivers and utilities. Refer to your Image Builder documentation for details

on using Image Builder PowerCLI.

6. Drivers for network (PXE) boot. Install these drivers after Fibre Channel drivers for network boot. Note that you

can use the VMware Image Builder PowerCLI to create a brocade_esx50_<version>.zip offline bundle and

brocade_esx50_<version>.iso ESX 5.0 installation image that includes brocade drivers and utilities. Refer to your

Image Builder documentarian for details on using Image Builder PowerCLI.

7. Solaris is not supported for the Brocade 804 and 1007 adapters.

8. Storage drivers for HBAs and Fabric Adapter ports configured in HBA mode.

9. Network drivers for CNAs and Fabric Adapter ports configured in CNA or NIC mode.

TABLE 10 Boot installation packages (continued)

Operating

System

(Platform)

Driver Update Disk Image LiveCD Boot Code

Brocade Adapters Installation and Reference Manual 53

53-1002144-01

Using BCU commands 1

6. When the File Download screen displays, save the file to an appropriate location on your

system.

Using BCU commands

Some procedures in this manual reference BCU commands for adapter monitoring and

configuration.

To use BCU commands, enter commands at the BCU> command prompt. For Windows systems,

launch the command prompt using the Brocade BCU desktop aa, which automatically installs to

your desktop with the adapter software. If installation fails (possibly because devices are not

present on the system), the shortcut is still created. The BCU shortcut provides quick access to the

installation folder where you can perform the following tasks:

•Run the Support Save feature

•Reinstall drivers

•Run adapter utilities

NOTE

Launching BCU on Windows systems through methods other than through the desktop shortcut is

not recommended and may result in display of inconsistent information.

To list all the commands and subcommands, type the following command:

bcu --help

To check the CLI and Driver version number, type the following command:

bcu --version

To launch a BCU command at the BCU> prompt, enter the command as in the following example:

port --list

NOTE

For complete details on BCU commands, refer to the Brocade Adapters Administrator’s Guide.

VMware ESX 5.0 and later systems

For VMware ESX 5.0 and later systems, BCU commands are integrated with the esxcli

infrastructure.

To run a BCU command, use the following syntax:

esxcli brocade bcu --command=”command”

where:

command BCU command, such as port --list.

For example:

esxcli brocade bcu --command="port -list"

54 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using BCU commands

Brocade Adapters Installation and Reference Manual 55

53-1002144-01

Chapter

Hardware Installation

In this chapter

•Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

•ESD precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

•Stand-up adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

•Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Introduction

This chapter provides instructions for installing and replacing the following types of Brocade

adapters:

•Stand-up HBA, CNA. and Fabric Adapters.

Instructions are also provided for removing and installing small form factor pluggable (SFP)

transceivers.

NOTE

Use only Brocade-branded SFP laser transceivers supplied for stand-up adapters.

•HBA mezzanine adapter

•CNA mezzanine adapter

NOTE

When installing Fabric Adapters with ports configured in CNA or NIC mode and CNAs on a VMware

systems, it is advisable to install the driver before the adapter so that the NICs will be properly

numbered in the system. Perform appropriate steps under Chapter 3, “Software Installation” then

return to this chapter.

To troubleshoot problems after installation, refer to the Brocade Adapters Troubleshooting Guide.

For details in items shipped with various adapter models for installation, refer to “Items shipped

with your adapter” on page 48.

ESD precautions

When handling the adapter, use correct electrostatic discharge (ESD) procedures:

•Be sure that you are properly grounded before beginning any installation.

•When possible, wear a wrist grounding strap connected to chassis ground (if system chassis is

plugged in) or a bench ground.

•Store the adapter in antistatic packaging.

56 Brocade Adapters Installation and Reference Manual

53-1002144-01

Stand-up adapters

Use information in this section to install stand-up adapter hardware on your host system.

What you need for installation

Have the following items available for installing the adapter hardware:

•Phillips #1 screwdriver.

•Adapter with appropriate mounting bracket attached.

•Appropriate cable with appropriate connectors to connect the adapter to the switch.

-For Fabric Adapter cable and SFP specifications, refer to “Cabling” on page 176.

-For CNA cable and SFP specifications, refer to “Cabling (stand-up adapters)” on page 183.

-For HBA and Fabric Adapter HBA port cable and SFP specifications, refer to “Cabling

(stand-up adapters)” on page 190.

•Fully operational host.

•Access to a host from your user workstation either through LAN connection or direct

attachment.

Installing an adapter

ATTENTION

The adapter can be damaged by static electricity. Before handling, use standard procedures to

discharge static electricity, such as touching a metal surface and wearing a static ground strap.

Handle the adapter by the edge and not the board components or gold connector contacts.

1. Check that you have received all items needed for installation. Refer to “Items shipped with

your adapter” on page 48.

2. Remove the adapter from its packaging and check for damage. If it appears to be damaged, or

if any component is missing, contact Brocade or your reseller support representative.

3. Make a backup of your system data.

4. Power down the host. Unplug all power cords and network cables.

5. Remove all covers necessary from the system to access the PCIe slot where you want to install

the adapter. Refer to documentation provided with your system to locate PCIe slots and cover

removal procedures.

6. Remove the blank bracket panel from the system that covers the PCIe slot where you want to

install the adapter. If the panel is secured with a screw, remove the screw and save it for

securing the adapter’s bracket panel back in the slot.

NOTE

For best performance, install the adapter into a PCIe slot with an x8 lane or greater transfer

interface. Also, do not install this adapter in a PCI slot. PCIe slots are shorter than PCI slots.

7. Remove all SFP transceivers from the adapter if clearances inside your system case prohibit

you from installing the adapter with transceivers installed. Follow the instructions under

“Removing and installing SFP transceivers” on page 59. Otherwise go on to the next step.

Brocade Adapters Installation and Reference Manual 57

53-1002144-01

Stand-up adapters 2

8. Install the longer, standard bracket on the adapter if the low-profile mounting bracket (shipped

installed on adapter) does not fit your system case. Use the following steps. If the installed

low-profile bracket works, go on to step 9.

a. Remove all SFP transceivers from the adapter. Refer to “Removing and installing SFP

transceivers” on page 59 for procedures.

b. Remove the two screws attaching the bracket to the adapter, and pull off the bracket. Refer

to Figure 8.

FIGURE 8 Removing or installing adapter mounting bracket

c. Carefully guide the new mounting bracket onto the adapter, making sure the bracket

mounting tabs align with the holes in the adapter.

d. Replace and tighten the two screws.

e. Store the mounting bracket that you removed for future use.

9. Insert the adapter into the desired empty PCIe bus slot. Press firmly until the adapter seats.

Refer to Figure 9 for seating directions.

58 Brocade Adapters Installation and Reference Manual

53-1002144-01

Stand-up adapters

FIGURE 9 Installing adapter in system chassis

10. Secure the adapter’s mounting bracket to the case using the method required for your case.

Note that in some systems, the bracket may secure to the case with a screw.

11. If you removed transceivers in step step 7, make sure to install adapter receivers. Refer to

“Removing and installing SFP transceivers” on page 59 for procedures.

12. Replace the system’s case or cover and tighten all screws.

Connecting an adapter to a switch or direct-attached storage

Use multimode fiber optic cable or twinaxial copper cable (Fabric Adapters with ports configured in

CNA mode and CNAs only) with appropriate connectors when connecting the adapter to the switch.

Use multimode fiber optic cable when connecting an HBA or Fabric Adapter port configured in HBA

mode to a switch or direct-attached storage. Refer to “Cabling (stand-up adapters)” on page 183

for cable specifications.

1Mounting screw

2 Top edge of adapter (press down into slot)

3PCI X8 slot

4 Edge of host board

5SFP receivers

Brocade Adapters Installation and Reference Manual 59

53-1002144-01

Stand-up adapters 2

1. Pull out the protective rubber inserts from fiber optic SFP connectors, if installed in adapters or

the switch.

2. Connect the cable from the switch to the appropriate SFP connector on the adapter.

Removing and installing SFP transceivers

User the following procedures to remove and install fiber optic SFP transceivers.

NOTE

Use only the Brocade-branded small form factor pluggable (SFP) transceivers in the Brocade

adapters. Refer to “Hardware compatibility” on page 10.

Removing transceivers

If you need to remove SFP transceivers from the adapter to provide clearance for installing into the

server cabinet, use the following steps.

1. Pull out the protective rubber plug from the SFP connector.

2. Remove the SFP.

•For SFPs with optical transceivers, use your thumb and forefinger to unlatch the bail from

the side of the cable connector. Using the bail or pull tab as a handle, pull the SFP straight

out of the receiver. Refer to the left illustration in Figure 10.

NOTE

For 16 Gbps optical transceivers, a pull tab may be available for pulling the SFP out of the

receiver.

•For copper SFPs with attached cables, use your thumb and forefinger to pull the tab on the

cable to release the SFP latch, then pull the SFP straight out of the receiver. Refer to the

right illustration in Figure 10.

NOTE

In the following figure, the fiber optic SFPs are shown illustration A, and the copper SFPs with

attached cable are shown in the illustration B.

60 Brocade Adapters Installation and Reference Manual

53-1002144-01

Stand-up adapters

FIGURE 10 Removing or installing fiber optic and copper SFPs

Installing transceivers

1. Orient the SFP in front of its slot on the adapter so that it can slide into the adapter receiver

slot. The SFP can only be oriented one way into the slot.

2. Carefully guide the SFP into the adapter’s receiver until it seats.

•For optical SFPs close the bail to latch the SFP into the receiver.

•For copper SFPs, push the SFP into the receiver until it clicks into place.

Replacing an adapter

If you are replacing an adapter, perform the following steps.

1. Make a backup of your system data.

2. Power down the host. Unplug all power cords and network cables.

3. Remove all covers necessary from the system to access the PCIe slot where you want to install

the adapter. Refer to documentation provided with your system to locate PCIe slots and cover

removal procedures.

4. Unlatch the mounting bracket for the installed adapter or remove the screw (if applicable)

securing it to the case.

5. Pull the adapter gently from PCIe connectors.

6. Install the new adapter following the appropriate steps for your adapter under “Stand-up

adapters” on page 56.

All configuration settings for the old adapter in the slot will automatically apply to the new adapter.

PORT

Brocade Adapters Installation and Reference Manual 61

53-1002144-01

Mezzanine adapters 2

Mezzanine adapters

Mezzanine adapters are smaller modules than stand-up models that mount on server blades that

install in blade system enclosures. Instead of connecting fiber optic cables between stand-up

adapters ports in traditional servers and switches, mezzanine adapters connect to switch or I/O

modules installed in the blade system enclosure through the enclosure midplane.

Use information in this section as a guideline for install these adapters in compatible blade servers

from supported manufacturers.

Brocade 804 HBA

To install the 804 mezzanine card adapter into the server blade, refer to the installation

instructions shipped with the adapter.

Also refer to the setup and installation guide and user guide for the blade system enclosure for the

following information:

•Instructions for removing and installing the server blade in the enclosure.

•Details about the association between the mezzanine bay and interconnect bays in the blade

system enclosure. The location where you install the mezzanine adapter determines where you

install the interconnect modules.

•Instructions for accessing the server blade through a console or workstation to install adapter

drivers and software.

For details on other devices that install in the blade system enclosure, refer to the Installation and

User Guide that came with the device.

For details on compatibility with blade servers, switch modules, I/O modules, and other devices

that install in the blade system enclosure, refer to “Server blades and blade system enclosures

(mezzanine adapters)” on page 11.

What you need for installation

Have the following available before installing the adapter:

•Mezzanine card shipping carton, which includes the mezzanine card and necessary

documentation.

•Fully operational blade server.

•Access to the blade server through local or remote console connection for installing adapter

drivers and software.

•Blade server installation and user guide.

•Blade system enclosure installation and user guides.

•Interconnect and switch module installation guides for the blade system enclosure.

NOTE

“Verifying adapter installation” on page 108 provides a list of general items to verify during and after

installing hardware and software to avoid possible problems. You can use the list to verify proper

installation and make corrections as necessary.

62 Brocade Adapters Installation and Reference Manual

53-1002144-01

Mezzanine adapters

Brocade 1007 CNA

For details on installing this adapter in a blade server, refer to the Installation and User Guide that

ships with the adapter.

The adapter (expansion card) Installation and User’s Guide provides full details on installation

guidelines, installing and removing the blade server from the blade system enclosure, installing

and removing the adapter from the blade server, resolving problems, obtaining help and technical

assistance, related documentation. safety, electronic emission notices, and important notes.

Review information in the adapter (expansion card) and blade system enclosure Installation and

User’s Guide about required location of switch modules in enclosure bays for connection to CNA

ports.

To support each I/O module that you install in the blade system enclosure, you may also need to

install a compatible CNA in each blade server that you want to communicate with the I/O module.

Refer to the documentation for your blade system enclosure for details.

For details on compatibility with blade servers, switch modules, I/O modules, and other devices

that install in the blade system enclosure, refer to “Server blades and blade system enclosures

(mezzanine adapters)” on page 11.

What you need for installation

Have the following available for installing the adapter:

•Adapter shipping carton, which includes the adapter and necessary documentation.

•Fully operational blade server.

•Access to blade server through local or remote console connection.

•Blade server or storage expansion unit Installation and User’s Guide.

•Blade system enclosure Installation and User’s Guides.

•I/O module installation guide for the blade system enclosure.

NOTE

“Verifying adapter installation” on page 108 provides a list of general items to verify during and after

installing hardware and software to avoid possible problems. You can use the list to verify proper

installation and make corrections as necessary.

Brocade 1741 CNA

For details on installing this mezzanine card on a blade server, refer to the supported blade

enclosure’s Hardware Owner’s Manual for the Dell™ PowerEdge™ M1000e modular blade system.

Refer to that manual for the following:

•Full details on installing and removing blades from the blade enclosure and installing and

removing mezzanine cards from blades.

•Guidelines for installing mezzanine cards. Before installing the mezzanine card, review the

installation guidelines, especially to identify blade slots for installing mezzanine cards and

enclosure bays for installing supported I/O modules.

•Guidelines for installing I/O modules. To support each I/O module that you install in the blade

enclosure, you may also need to install a compatible mezzanine card in each blade server that

you want to communicate with the I/O module.

Brocade Adapters Installation and Reference Manual 63

53-1002144-01

Mezzanine adapters 2

•Instructions for accessing the blade server through a console or workstation to install adapter

drivers and software.

What you need for installation

Have the following available for installing the adapter:

•Mezzanine card shipping carton, which includes the adapter and necessary documentation.

•Fully operational blade server.

•Access to the blade server through local or remote console connection.

•The blade enclosure’s Hardware Owner’s Manual.

Updating PHY firmware

The Ethernet PHY module, located in the 1740 mezzanine card port hardware only, aids in

communications to and from the Ethernet LAN. Instructions are provided in this section to update

this firmware if required.

Determining firmware version

To query the PHY module and determine attributes, such as the PHY module status and installed

firmware version, use the bcu phy --query command.

bcu phy --query <port_id>

where:

<port_id> ID of port for which you want to determine the firmware version. This could be

the PWWN, port hardware path, or user-specified port name. This could also

be the adapter-index/port-index. For example, to specify adapter 1, port 1 you

would use 1/1 as the port identification.

Updating firmware

Download the latest PHY firmware file and update the PHY using the bcu phy --update command.

bcu phy --update <ad_id> | -a <binary_file>

where:

-a If specified, update will apply to all adapters in the system that contain the

PHY module.

ad_id ID of the adapter.

file_name Name of binary firmware file.

NOTE

After updating the firmware, you must disable then enable the adapter to activate it.

64 Brocade Adapters Installation and Reference Manual

53-1002144-01

Mezzanine adapters

Brocade Adapters Installation and Reference Manual 65

53-1002144-01

Chapter

Software Installation

In this chapter

•Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

•Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

•Using the Brocade Adapter Software Installer. . . . . . . . . . . . . . . . . . . . . . . . 68

•Using software installation scripts and system commands . . . . . . . . . . . . . 89

•Confirming driver package installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

•Verifying adapter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

•Updating drivers with HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

•Installing HCM to a host from the HCM Agent. . . . . . . . . . . . . . . . . . . . . . . 112

•HCM Agent operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

•HCM configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

•Setting IP address and subnet mask on CNAs . . . . . . . . . . . . . . . . . . . . . . 115

Introduction

This chapter provides procedures to install the adapter driver, HCM, and other software using the

following options:

•“Using the Brocade Adapter Software Installer” on page 68.

•“Using software installation scripts and system commands” on page 89.

Procedures are also provided for removing software using the Brocade Adapter Software

Uninstaller (refer to “Software removal using Adapter Software Uninstaller” on page 83), and

upgrading software using the Brocade Adapter Software Installer (refer to “Software upgrade using

Adapter Software Installer” on page 87). Procedures are also provided for configuring HCM agent

operations, and setting the IP address and subnet mask on CNAs and Fabric Adapter ports

configured in CNA or NIC mode.

To troubleshoot problems after installation, refer to the Brocade Adapters Troubleshooting Guide.

To keep adapter drivers and boot code synchronized, be sure to update your adapter with the latest

boot image whenever you install or update adapter driver packages. Use the following steps:

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the Downloads page.

3. Select your operating system from the Downloads list or download the ISO image.

4. Download the boot image file from the “Boot Code” section.

5. Refer to “Boot code updates” on page 118 for instructions to install the image.

66 Brocade Adapters Installation and Reference Manual

53-1002144-01

Installation notes

Please read through the following notes before installing adapter software:

•For details on operating system requirements for installing adapter drivers, refer to “Operating

system support” on page 40 and “Software installation and driver packages” on page 43. Also

download the latest release notes from the Brocade adapters website using the following

steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list or download the ISO image.

d. Download the release notes from the “Documentation” section.

•Find the installer program for your host’s operating system and platform under “Software

installation and driver packages” on page 43. Following are generic names for the Installer

program for supported operating systems.

-Windows systems

brocade_adapter_software_installer_windows_<version>.exe

-Linux systems

brocade_adapter_software_installer_linux_<version>.bin

brocade_adapter_software_installer_linux_<platform>_<version>.bin

-Solaris systems

brocade_adapter_software_installer_Solaris10_<platform>_<version>.bin

NOTE

The <platform> variable in the installer commands is the host system architecture, such

as SPARC, x86, or x64.

•The Brocade Adapter Software Installer is not supported on the VMware ESX platforms for

installing drivers, HCM, or utilities. However, you can use an appropriate Brocade Adapter

Software Installer to install HCM on a “guest” system. For VMware, drivers and utilities are

provided as ISO images packed in a tarball. A Brocade installer script is available for

installation.

•To use the Brocade Adapter Software Installer on Linux RHEL 6.0 x64 systems, you must install

the x32-compatible libraries as they are not installed by default. Refer to “RHEL 6.x version x64

systems” on page 69 for procedures.

•Software installation or upgrade on a host system with a large number of adapters could take

much longer than normal.

•If you receive errors when launching the GUI-based Brocade Adapter Software Installer, such

as InvocationTargetException errors, your system may not be able to run a GUI-based

application. Instead use the instructions under “Software installation using Software Installer

commands” on page 76.

•Brocade 804 and 1007 adapters are not supported on Solaris systems so Solaris commands

in this section do not apply.

•After installing drivers on a Linux or Solaris system, you must reboot the system to enable the

drivers.

Brocade Adapters Installation and Reference Manual 67

53-1002144-01

Installation notes 3

•You must use the Brocade Adapter Software Installer application to install HCM to the host

system where the adapter is installed or to a separate remote management platform.You

cannot install HCM using the Brocade-provided installation scripts or your system’s “native”

installation commands. After installation, an HCM desktop shortcut is available on Windows

and Linux systems.

•Ensure that Visual Studio 2005 SP1 (or later) Redistributable package is installed on Windows

2003 R2 SP3 systems to avoid problems starting HCM Agent.

•There are firewall issues with HCM Agent on Windows 2008 and VMware systems. When

installing the driver package on these systems, open TCP/IP port 34568 to allow agent

communication with HCM.

-For VMware, use the following command to open port 34568:

/usr/sbin/cfg-firewall -o 34568,tcp,in,https

/usr/sbin/cfg-firewall -o 34568,udp,out,https

-For Windows, use Windows Firewall and Advanced Service (WFAS) to open port 34568.

Note that you can change the default communication port (34568) for the agent using the

procedures under “HCM Agent operations” on page 112.

•On Linux SLES 10 and 11 systems when installing the source-based (noarch) driver packages

(brocade_driver_linux_<version>.tar.gz) or when using the Brocade Adapter Software Installer

and the kernel has been upgraded to a version without pre-compiled binaries, perform the

following tasks to make sure the drivers will load on system reboot:

-For Linux SLES 10 systems, make sure that the LOAD_

UNSUPPORTED_MODULES_AUTOMATICALLY variable on your system is set to “yes.” This

variable is in the following configuration file.

/etc/sysconfig/hardware/config

-For Linux SLES 11, change the “allow_unsupported_modules” value from 0 to 1 in the

following file.

/etc/modprobe.d/unsupported-modules

•Only one driver installation is required for all Brocade adapters (HBAs, CNAs, or Fabric

Adapters) installed in a host system.

•Root or administrator privileges are required for installing the driver package.

•The procedures in this section assume that the host’s operating system has been installed and

is functioning normally.

•Before installing the driver on Windows systems, install the following hot fixes from the

Microsoft “Help and Support” website, then reboot the system:

-Windows 2003

KB932755 (or later) is the minimum requirement.

KB943545 is recommended if the HP command view management application is used to

manage HP EVA arrays in the target system.

-Windows 2008

KB968675 is recommended. This fixes a non-paged memory leak in a Windows 2008 storage

stack.

KB2490742 is recommended when installing storage drivers to avoid a “Ox000000B8” stop

error when shutting down or hibernating a system running Windows 7 or Windows Server 2008

R2.

68 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

KB958015 is recommended for CNAs and Fabric Adapter ports configured in CNA mode.

-Windows 2008 R2

KB977977 is recommended for CNAs and Fabric Adapter ports configured in CNA mode.

•Installing software with the Brocade Adapter Software Installer automatically starts the HCM

Agent. You can manually start and stop the agent using the instructions under “HCM Agent

operations” on page 112.

•When using the Brocade Adapter Software Installer to install HCM, a “Found Backed up data”

message displays if a backup directory exists for previously installed software. This message

prompts you to restore or not to restore old configuration data. Refer to “HCM configuration

data” on page 114 for more information.

•By default, the initrd file will be backed up automatically during Linux installations. During

installation, a dialog box displays with the location of the file. If a file exists, a dialog box

displays with its current location and allows you to overwrite the file, not overwrite the file, or

quit.

•For Windows systems, installing the management utilities creates a Brocade BCU desktop

shortcut on your system desktop. Use this to launch the BCU> command prompt and enter

BCU commands.

•Because the ESX 5.0 driver installation process does not enforce maintenance mode, it is

recommended that you put the host in maintenance mode since a system reboot is required

after installation.

Using the Brocade Adapter Software Installer

Use information in this section to install the Host Connectivity Manager (HCM) and driver packages

for your host platform using the Brocade Adapter Software Installer (BASI) application. Instructions

for using the GUI-based installer and command line installer are provided. The Brocade Adapter

Software Installer application allows you to install all software or to selectively install the HCM or

driver packages.

NOTE

The Brocade Adapter Software Installer is available for Windows, Linux, and Solaris operating

systems. For VMware systems, it will only operate on “guest” operating systems for installing the

HCM application. To install the driver and utilities package for VMware systems, refer to “Driver

installation and removal on VMware systems” on page 99.

For instructions on using the Brocade installation scripts and installation commands that are

“native” to your host operating system, refer to “Using software installation scripts and system

commands” on page 89.

For details on HCM, driver packages, and other adapter software components for each supported

host system, refer to “Adapter software” on page 37.

Two installation options are available when using the Brocade Adapter Software Installer:

•Installation using a GUI-based installer. Refer to “Using the GUI-based installer” on page 69.

•Installation using commands. This method completely installs the driver package, HCM, or all

components without user interaction. Refer to “Software installation using Software Installer

commands” on page 76.

Brocade Adapters Installation and Reference Manual 69

53-1002144-01

Using the Brocade Adapter Software Installer 3

NOTE

The storage driver will claim all installed Brocade Fiber Channel HBAs, FCoE CNAs, and Fabric

Adapter ports configured in HBA or CNA mode installed in a host system.

RHEL 6.x version x64 systems

The Brocade Adapter Software Installer and HCM are 32-bit applications. To use these applications

on Linux RHEL 6.x version x64 systems, you must install the x32-compatible libraries because they

are not installed by default.

To install these libraries, use the following steps.

1. Install glibc.i686 or select “Compatibility Libraries” under “Base System” when installing RHEL

6.x.

2. Install the following RPMs once you install RHEL 6.x:

NOTE

These RPMs should be available under the Packages folder on the RHEL 6.0 or 6.1 DVD.

•libX11-*.el6.i686.rpm

•libXau-*.el6.i686.rpm

•libXext-*.el6.i686.rpm

•libXi-*.el6.i686.rpm

•libXtst-*.el6.i686.rpm

•libxcb-*.el6.i686.rpm

•nss-softokn-freebl-*.el6.i686.rpm

•glibc-*.el6.i686.rpm

Using the GUI-based installer

The Brocade Adapter Software Installer (BASI) GUI-based application or commands are the

preferred methods to install the following components on your host system:

•Storage and network drivers

•Management Utilities. These include the HCM agent, BCU, BASI, installation scripts, CIM

provider, and SNMP agent files.

•HCM only

This application operates on systems specified under Table 9 on page 44. To use the

command-line version of this application, refer to “Software installation using Software Installer

commands” on page 76.

The Adapter Software Installer installs HCM, all driver packages, and management utilities based

on your host operating system. The HCM Agent starts automatically after installation. You can also

install software components using software installer scripts and “native” system commands (refer

to “Using software installation scripts and system commands” on page 89).

70 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

NOTE

The software installer is not supported on VMware ESX platforms. However, you can use the

appropriate Brocade Adapter Software Installer to install HCM to a guest system (Windows, Linux, or

Solaris). To install adapter drivers on VMware systems, refer to “Using software installation scripts

and system commands” on page 89.

Use the following steps to install all software required for Brocade adapters with the GUI-based

installer program.

NOTE

It is strongly recommended that you shut down the HCM application if it is running on your system.

1. Access the downloads pages of the adapters website using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

1. Navigate to the Downloads page.

2. Use one of these options to download software from the adapter’s Downloads page:

•View the appropriate download page for your host’s operating system by selecting an

operating system from the Download Individual Software Installers, Drivers, or Documents

list, then download the appropriate Brocade Adapter Software Installer or driver package

for your system.

Find the installer program for your system’s operating system and platform under

“Software installation and driver packages” on page 43.

•Select Download ISO Image to download an ISO 9660 (.iso) optical disk image containing

the Brocade Adapter Software Installer, individual driver packages, HCM, and

documentation. You can use this ISO file to create a CD that you can carry to your system

for installation.

NOTE

For Windows systems only. Using a DVD created with the ISO image will automatically start

the correct installer program for your system. Make sure that the autorun feature is

enabled. If using this DVD, you do not need to execute the installer program command

(.exe or .bin) as explained in step 2.

2. Execute the appropriate Brocade Adapter Software Installer program (.exe or .bin file),

depending on your host’s operating system and platform.

A progress bar displays as files are extracted.

When all files are extracted, a Brocade Adapter Software title screen displays.

3. When the Brocade Software Installer Introduction screen displays (Figure 11), read the

recommendations and instructions, then click Next.

Brocade Adapters Installation and Reference Manual 71

53-1002144-01

Using the Brocade Adapter Software Installer 3

FIGURE 11 Brocade Adapter Installer Introduction screen

4. When the License Agreement screen displays, select I accept the terms of the License

Agreement, then click Next to continue.

5. If a backup directory exists for previously installed software, a “Found Backed up data”

message displays prompting you to restore old configurations. Select either to restore or not to

restore and continue installation. Refer to “HCM configuration data” on page 114 for more

information. If this message does not display, go on to step 6.

6. If a screen such as the one in Figure 12 on page 72 displays listing software components already

installed on your system, select one of the following options, click Continue, then skip to

step 10.

•Install with existing configuration. The installer compares each configured property and

keeps the original value if different than the default value.

•Install with default configuration. The installer upgrades the software and loads with

default configurations.

NOTE

Existing versions of the adapter’s software components will be overwritten with the current

versions you are installing if you continue.

If this screen does not display, go on to step 7.

72 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

FIGURE 12 Existing software components installed screen

7. If message box displays prompting you to close all HCM applications, close all applications if

they are still running, then click OK.

The Choose Install Set screen displays (Figure 13 or Figure 14).

NOTE

This following screen displays for all adapter models except the Brocade 804 adapter.

FIGURE 13 Choose Install Set screen (models except the 804 adapter)

NOTE

The following screen displays for the Brocade 804 adapter only.

Brocade Adapters Installation and Reference Manual 73

53-1002144-01

Using the Brocade Adapter Software Installer 3

FIGURE 14 Choose Install Set screen (804 adapter only)

8. Select which software you want to install, then select Next.

If you are installing the management utilities and messages display warning that HCM agent

requires storage and network driver installation or does not match current driver installation,

click OK. and select the Management Utilities and Storage and Network Drivers options.

If a message displays warning that the installed boot image is not compatible with the driver

installation, perform one of the following steps:

•Select Yes to update the image and continue installation.

•Select No to not update the image and continue installation.

9. If the Choose Install Folder screen displays, prompting you to choose a destination folder for

the software, select either of the following options. If this screen does not display, go on to

step 10.

•Enter a location for installing the software where the default installation folder displays.

•Select Choose to browse to a location on your file system.

•Select Restore Default Folder to enter the default installation folder.

10. When the Package Location Information screen displays listing the installed software

components and their location on your system, select Next to continue.

11. When the Pre-Installation Summary screen displays (Figure 15 on page 74), review the

information and select Install to confirm and begin the installation.

74 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

FIGURE 15 Pre-Installation Summary screen

A progress bar displays showing installation progress for the various software components.

NOTE

For Windows systems, a Force Driver Installation message box displays if a better driver is

already installed for the adapter. If message displays, select OK to overwrite the existing driver

or Cancel to quit installation.

After software installs, the Install Complete screen displays listing installed drivers and other

components (Figure 16 on page 75).

Brocade Adapters Installation and Reference Manual 75

53-1002144-01

Using the Brocade Adapter Software Installer 3

FIGURE 16 Install Complete screen

12. Confirm that all software installed successfully. If the screen instructs you to restart or reboot

the system, select any options that apply.

13. Select Done.

14. Verify installation using tools available on your host system. Refer to “Confirming driver package

installation” on page 103 for details.

15. To make sure that the drivers and adapter boot code are synchronized, be sure to update your

adapter with the latest boot image from the Brocade website at www.brocade.com/adapters

whenever you install or update adapter driver packages. From the adapters website, navigate

to the drivers Downloads page. Access the appropriate download page by selecting your host’s

operating system from the Download Individual Software Installers, Drivers, or Documents list.

Refer to “Boot code updates” on page 118 for instructions to install the boot image.

NOTE

Installing management utilities on Windows systems creates a Brocade BCU shortcut on your

system desktop. Use this shortcut to launch the BCU> command prompt and enter BCU commands.

76 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

Software installation using Software Installer commands

Execute Brocade Adapter Software Installer commands detailed in this section on the host

system’s command line with your choice of parameters to step through the installation or

automatically install network and storage driver packages, the HCM application, or both without

requiring further user interaction. The HCM Agent starts automatically after installation.

For details on operating system requirements for installing adapter drivers, refer to “Operating

system support” on page 40 and “Software installation and driver packages” on page 43. Also

download the latest release notes from the Brocade adapters website at

www.brocade.com/adapters whenever you install or update adapter driver packages using the

following steps:

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the Downloads page.

3. Select your operating system from the Downloads list.

4. On the downloads page, download the release notes from the “Documentation” section.

Note that on systems without a configured GUI, using the installer command without parameters as

outlined in “Using the GUI-based installer” on page 69 may generate errors and the installer

program will fail. Using the installer command with parameters outlined in this section will allow

you to install all or individual adapter software components.

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems.

Following are the commands you can use for supported operating systems:

•Windows systems - possible commands

-Install drivers, HCM GUI, both, or management utilities. Overwrites the existing driver

installed on the system.

brocade_adapter_software_installer_windows_<version>.exe

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL]

-DFORCE_WIN_DRIVER_INSTALLATION=1

-i silent

-Install drivers and HCM GUI in silent mode (no interaction required).

brocade_adapter_software_installer_windows_<version>.exe -i silent

-Install drivers and the HCM GUI using a default installation properties file.

brocade_adapter_software_installer_windows_<version>.exe -f

HCMDefaultInstall.properties

-Install software in silent mode using default installation properties file. Note that this is

recommended for silent mode.

brocade_adapter_software_installer_windows_<version>.exe -1 silent -f

HCMDefaultInstall.properties

•Linux systems - possible commands

-x_86 and x_86_64 platforms

Install drivers, HCM GUI, both, or management utilities. Overwrites the existing driver

installed on system.

Brocade Adapters Installation and Reference Manual 77

53-1002144-01

Using the Brocade Adapter Software Installer 3

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL]

-DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent

Install drivers and HCM GUI in silent mode (no interaction required).

sh brocade_adapter_software_installer_linux_<version>.exe -i silent

Install drivers and the HCM GUI using a default installation properties file.

sh brocade_adapter_software_installer_linux_<version>.bin -f

HCMDefaultInstall.properties

Install software in silent mode using default installation properties file. Note that this is

recommended for silent mode.

sh brocade_adapter_software_installer_linux_<version>.bin -i silent -f

HCMDefaultInstall.properties

Install noarch driver when kernel-specific driver is not available and select to install HCM

GUI, both, or management utilities

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -DCONT_NOARCH_DRIVER=[NO|YES]

-i silent

Install drivers, HCM GUI, both, or management utilities. Overwrites the backed-up initrd

file.

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -DFORCE_INITRD_BACKUP=[NO|YES]

-i silent

•Solaris systems

-x_86 platforms

Install drivers, HCM GUI, both, or management utilities. Overwrites the existing driver

installed on system.

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL]-i silent

Install drivers and HCM GUI in silent mode (no interaction required).

sh brocade_adapter_software_installer_solaris10_x86_<version>.exe -i

silent

Install software in silent mode using default installation properties file. Note that this is

recommended for silent mode.

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin -i

silent -f HCMDefaultInstall.properties

Install software in silent mode using default installation properties file. Note that this is

recommended for silent mode.

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin -i

silent -f HCMDefaultInstall.properties

Install driver, HCM GUI, both, or management utilities. Overwrites the existing driver

installed on the system.

78 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -i silent

-SPARC platforms

Install driver, HCM GUI, both, or management utilities. Overwrites the existing driver

installed on the system.

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin

-DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -i silent

Installs drivers and HCM GUI in silent mode (no interaction required).

sh brocade_adapter_software_installer_solaris10_sparc_<version>.exe -i

silent

Install drivers and the HCM GUI using a default installation properties file.

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin -f

HCMDefaultInstall.properties

Install software in silent mode using default installation properties file. Note that this is

recommended for silent mode.

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin -i

silent -f HCMDefaultInstall.properties

Command options

Following are the options that you can modify and in command strings. You can also edit these

fields in the properties file to change the default install set:

•INSTALLER_UI=silent

Specifies that the installation mode should be silent.

•CHOSEN_INSTALL_SET=BOTH

Specifies to install either the network and storage driver packages, the GUI (HCM), or all

components.:

-BOTH - This parameter installs both the GUI and the driver. The HCM Agent starts

automatically after installation.

-DRIVER - This parameter installs only the driver. The HCM Agent starts automatically after

installation.

-GUI - This parameter installs only HCM.

-UTIL - This parameter installs the management utilities.

•CONT_NOARCH_DRIVER=[NO|YES]

Use for installing non-specific architecture drivers when kernel-specific driver is not available. If

set to YES, installs the noarch driver on Linux systems. No is the default value if you do not

specify the parameter as an argument.

Brocade Adapters Installation and Reference Manual 79

53-1002144-01

Using the Brocade Adapter Software Installer 3

•FORCE_WIN_DRIVER_INSTALLATION=1

Be sure to uncomment the "FORCE_WIN_DRIVER_INSTALLATION=1" to overwrite the existing

driver on Windows platform. Note that this may require system reboot.

For Linux or Solaris systems, use the standard DCHOSEN_INSTALL_SET command to overwrite

existing software.

•#FORCE_INITRD_BACKUP=YES

For Linux systems, a “YES” value overwrites the backed-up initrd file.

All parameters are case-sensitive and make sure to spell the parameters correctly.

Complete details on editing and executing the properties file are available under the “Guidelines

for silent installation” section located in the HCMDefaultproperties.file.

Important notes

Review these notes before using Brocade Adapter Software Installer commands.

•Brocade 804 and 1007 adapters are not supported on Solaris systems.

•Executing the following commands without parameters will launch the GUI-based installer

described under “Using the GUI-based installer” on page 69.

-Windows systems

brocade_adapter_software_installer_windows_<version>.exe

-Linux systems

sh brocade_adapter_software_installer_linux_<version>.bin

-Solaris systems

sh brocade_adapter_software_installer_solaris10_<x86_<version>.bin

sh brocade_adapter_software_installer_solaris10_<x64_<version>.bin

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin

•Complete details on editing and executing the properties file are available under the

“Guidelines for silent installation” section located in the HCMDefaultproperties.file.

•If you choose to install the driver, both the storage and network drivers will be installed.

•Software installation or upgrade on a host system with a large number of adapters could take

much longer than normal.

•Parameters are case-sensitive.

•Find the installer program for your server’s operating system and platform under “Software

installation and driver packages” on page 43. Before using any commands described in this

section, use the following steps to download the Brocade Adapter Software Installer to your

system.

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the Downloads page.

c. Perform on of the following steps:

•Select your hosts’s operating system from Download Individual Software Installers,

Drivers, or Documents list to display the Downloads page, then download the Brocade

Adapter Software Installer to your host system.

80 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

•Select Download ISO Image and download an ISO 9660 (.iso) optical disk image. This

contains the Brocade Adapter Software Installer, individual driver packages containing

installer scripts, HCM, and documentation. You can use this ISO file to create a CD

that you can carry to your system for installation.

•To enter these commands, first change to the directory where the adapter software is installed

(cd <install directory>). Default install directories are the following;

-Windows systems

C:\Program Files\BROCADE\Adapter

-Linux and Solaris systems

/opt/brocade/adapter

•On Windows XP, Vista, NT, 2000, and Windows 2003 service pack1, only the GUI will install for

all DCHOSEN_INSTALL_SET values (DRIVER, GUI, or BOTH).

•To launch the installer in silent mode, you must use and provide values for the following

parameters:

-DCHOSEN_INSTALL_SET

--i silent

•By default, the initrd file will backed up automatically during Linux installations. During

installation, a dialog box displays with the location of the file. If a file exists, a dialog box

displays with its current location and allows you to overwrite the file, not overwrite the file, or

quit.

•To make sure that the drivers and adapter boot code are synchronized, be sure to update your

adapter with the latest boot image from after you install or update adapter driver packages.

using the following steps.

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the Downloads page.

c. Select your operating system from the Downloads list.

d. Download the boot code image from the “Boot Code” area.

Refer to “Boot code updates” on page 118 for instructions to install the boot code image.

•Installing management utilities on Windows systems creates a Brocade BCU desktop shortcut

on your system desktop. Use this to launch the BCU> command prompt and enter BCU

commands. If installation fails (possibly devices are not present on the system), the shortcut is

still created. The BCU shortcut provides quick access to the installation folder where you can

perform the following tasks:

-Run the Support Save feature

-Reinstall drivers

-Run adapter utilities

NOTE

Launching BCU on Windows systems through methods other than through the desktop

shortcut is not recommended and may result in display of inconsistent information.

•Because the ESX 5.0 driver installation process does not enforce maintenance mode, it is

recommended that you put the host in maintenance mode since a system reboot is required

after installation.

Brocade Adapters Installation and Reference Manual 81

53-1002144-01

Using the Brocade Adapter Software Installer 3

Installation examples

Following are some examples of using commands and parameters to install adapter software:

•To install the storage and network drivers in silent mode and start the HCM Agent

automatically by default.

Windows systems

brocade_adapter_software_installer_windows_<version>.exe

-DCHOSEN_INSTALL_SET=DRIVER -i silent

Linux systems

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=DRIVER -i silent

Solaris systems

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin

-DCHOSEN_INSTALL_SET=DRIVER -i silent

sh brocade_adapter_software_installer_solaris10_x64_<version>.bin

-DCHOSEN_INSTALL_SET=DRIVER -i silent

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin

-DCHOSEN_INSTALL_SET=DRIVER -i silent

•To install the driver packages, HCM, and management utilities in silent mode.

Windows systems

brocade_adapter_software_installer_windows_<platform>_<version>.exe

-DCHOSEN_INSTALL_SET=BOTH UTIL -i silent

Linux systems

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=BOTH UTIL -i silent

Solaris systems

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin

-DCHOSEN_INSTALL_SET=BOTH UTIL -i silent

sh brocade_adapter_software_installer_solaris10_x64_<version>.bin

-DCHOSEN_INSTALL_SET=BOTH UTIL -i silent

•To overwrite existing driver packages with the new driver packages on a Windows system using

silent mode.

brocade_adapter_software_installer_windows_<version>.exe

-DCHOSEN_INSTALL_SET=DRIVER -DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent

•To install drivers in silent mode and overwrite the existing backed-up initrd file in Linux

systems.

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=BOTH -FORCE_INITRD_BACKUP=YES -i silent

82 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

•To install HCM interactively.

Windows systems

brocade_adapter_software_installer_windows_<platform>_<version>.exe

Linux systems

sh brocade_adapter_software_installer_linux_<version>.bin

Solaris systems

sh brocade_adapter_software_installer_solaris10_x86_<version>.bin

sh brocade_adapter_software_installer_solaris10_sparc_<version>.bin

•To install the noarch driver on Linux systems in silent mode.

sh brocade_adapter_software_installer_linux_<version>.bin

-DCHOSEN_INSTALL_SET=DRIVER -DCONT_NOARCH_DRIVER=YES -i silent

Installing HCM and driver package in silent mode using file option

By identifying the default installation properties file after the software installer command, HCM, the

storage driver, and the network driver are installed by default in silent mode. The HCM Agent starts

automatically after installation. This is the recommended method for silent installation.

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems, so Solaris options in this

section do not apply.

Use the following steps.

1. At the command line, change to the directory where the installer is located.

2. Use the following commands to initiate silent installation using the properties file.

•Windows systems

brocade_adapter_software_installer_windows_<version>.exe -f

HCMDefaultInstall.properties

•Linux systems

brocade_adapter_software_installer_linux_<version>.bin -f

HCMDefaultInstall.properties

•Solaris systems

brocade_adapter_software_installer_solaris10_x86_<version>.bin -f

HCMDefaultInstall.properties

brocade_adapter_software_installer_solaris10_sparc_<version>.bin -f

HCMDefaultInstall.properties

Brocade Adapters Installation and Reference Manual 83

53-1002144-01

Using the Brocade Adapter Software Installer 3

Software removal using Adapter Software Uninstaller

Use the following steps to remove the adapter driver packages and HCM. Instructions are provided

for using the GUI-based or command-based Brocade Adapter Software Installer. Instructions are

provided for Windows, Solaris, and Linux systems.

Important notes

Review these notes for removing the Brocade adapter software from your system:

•Use steps in this section to remove HCM.

•Before removing adapter software, It is strongly recommended that you stop the HCM agent

and shut down the HCM application if it is running on your system. For instructions on stopping

the HCM Agent, refer to “HCM Agent operations” on page 112.

•When removing HCM you may be prompted to backup existing configuration data. Refer to

“HCM configuration data” on page 114 for more information.

Using the Brocade Software Uninstaller

Use the following steps to remove software that was installed with the GUI-based Brocade Adapter

Software Installer, native system scripts, and system commands. Instructions are provided for

Windows, Linux, and Solaris systems.

NOTE

Also use these procedures if HCM is installed on VMware and VMware operates as a “guest” on your

Windows system.

1. Perform one of the following steps depending on your host operating system:

For Windows systems, perform one of the following steps:

•Select Brocade Adapter Software from the Windows Start menu, then select Uninstall

BROCADE Adapter Software.

•To use the command line, use the following steps.

a. At the command line, change to the directory where the installer is located.

cd <install directory>\UninstallBrocade Adapter Software <version>

NOTE

The default <install directory> is C:\Program Files\BROCADE\Adapter.

b. Enter the following command to launch the Brocade Adapter Software Uninistaller.

Uninstall.bat

84 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

For Linux and Solaris systems, perform the following steps.

a. Change to the directory where the Adapter Software Installer application is installed using

the following command:

cd <install directory>/UninstallBrocade Adapter Software <version>

where:

<install directory> - default install directory is /opt/brocade/adapter.

<version> - the application version, such as v3.0.

b. Enter the following command to launch the Brocade Adapter Software Installer:

sh Uninstall.sh

2. When an Introduction message displays about the uninstall, click Next.

3. If a message displays prompting you to close HCM, close the application if it is running, then

click OK on the message box.

4. When the Uninstall Options screen displays with uninstall options, select an option.

•Select Complete Uninstall to remove the driver packages and all other installed Brocade

adapter software components.

•Select Uninstall Specific Features to selectively uninstall specific software components.

5. Select Next.

•If you selected Complete Uninstall, a screen displays showing software removal progress.

•If you selected Uninstall Specific Features, a Choose Product Features screen displays

from which you can select features for removal. Remove check marks by features that you

wish to uninstall, then select Uninstall to continue with software removal.

Brocade Adapters Installation and Reference Manual 85

53-1002144-01

Using the Brocade Adapter Software Installer 3

6. If a message box displays asking if you want to back up HCM configurations, click Yes or No.

If you select Yes, a dialog box displays prompting you to select a backup directory. Use the

default directory or browse to another location. Select Uninstall to perform backup and remove

software.

A screen eventually displays notifying you of a successful uninstall. If a message displays on

this screen notifying you of leftover files in the installation path, make sure that you delete

these manually after removal completes.

7. Cli ck Done.

8. If a message for rebooting the system displays, select the reboot option to complete the

software removal process.

Removing Adapter Software from Windows 2008 Programs and Features list

If Brocade Adapter Software is still listed under the Programs and Features list after using the

software uninstaller to remove software on Windows 2008 systems, use the following steps to

remove it.

1. Go to the Programs and Features list (typically Control Panel>Programs>Programs and

Features

2. Right-click Brocade Adapter Software

3. Select Uninstall/Change.

Using Software Uninstaller commands

The following steps explain how to use the Adapter Software Uninstaller commands to remove the

network and storage driver packages and HCM from Windows, Linux, and Solaris systems. These

commands automatically remove software that you specify without using a GUI-based program that

requires user interaction.

Executing the following commands without parameters will launch the GUI-based uninstaller

described under “Using the Brocade Software Uninstaller” on page 83.

•Windows systems

Uninstall.bat

•Linux and Solaris systems

sh Uninstall.sh

Execute these same commands on the host system’s command line with various parameters to

automatically remove the network and storage driver packages, HCM application, both, or

management utilities without requiring further user interaction.

•Windows systems

Uninstall.bat -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -DEBUG=[true|false]

-i silent

•Linux and Solaris systems

sh Uninstall.sh -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL]

-DEBUG=[true|false]

-i silent

86 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

where:

•DCHOSEN_INSTALL_SET

Specifies to remove either the network and storage driver packages, the GUI (HCM),

management utilities, or all components.

•DEBUG - specifies whether the debug log messages are needed. Possible values are true or

false.

•i silent - specifies that the uninstallation mode is silent.

Important notes

Review these notes before using the software uninstaller commands.

•If you choose to remove the driver, both the storage and network drivers are removed.

•Parameters are case-sensitive.

•To enter uninstaller commands, first change to the directory where the adapter software is

installed (cd <install directory>).

-Windows systems

cd <install directory>\UninstallBrocade Adapter Software

The default <install directory> is C:\Program Files\BROCADE\Adapter.

-Linux and Solaris systems

cd <install directory>/UninstallBrocade Adapter Software

The default <install directory> is /opt/brocade/adapter.

•To launch the uninstaller in silent mode, you must use and provide values for both the following

parameters:

-DCHOSEN_INSTALL_SET

--i silent

Uninstall examples

•To remove the network and storage drivers only in silent mode with debug messages.

Windows systems

Uninstall.bat -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent

Linux or Solaris systems

sh Uninstall.sh -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent

•To remove the network and storage drivers, HCM, and management utilities in silent mode, but

without debug messages.

Windows systems

Uninstall.bat -DCHOSEN_INSTALL_SET=BOTH UTIL -DEBUG=false -i silent

Linux or Solaris systems

sh Uninstall.sh -DCHOSEN_INSTALL_SET=BOTH UTIL -DEBUG=false -i silent

Brocade Adapters Installation and Reference Manual 87

53-1002144-01

Using the Brocade Adapter Software Installer 3

•To remove HCM only without using silent mode, but with debug messages.

Windows systems

Uninstall.bat -DCHOSEN_INSTALL_SET=GUI -DEBUG=true

Linux or Solaris systems

sh Uninstall.sh -DCHOSEN_INSTALL_SET=GUI -DEBUG=true

Software upgrade using Adapter Software Installer

To upgrade HCM, adapter driver packages, or the driver packages and HCM, simply follow the

instructions under “Using the GUI-based installer” on page 69 or “Software installation using

Software Installer commands” on page 76. You do not need to remove the existing software first.

However, refer to the following important notes when upgrading, as procedures may vary from

first-time installation on specific operating systems.

•Windows systems

-When upgrading the driver for Windows systems, you do not need to reboot after

installation.

-The recommended procedure for upgrading Windows drivers is to install the new driver

without first removing the existing driver.

-When using the Brocade Adapter Software Installer commands for installation and an

existing driver is installed on the system, you must use the following parameter to

overwrite with the new driver.

-DFORCE_WIN_DRIVER_INSTALLATION=1

For example, to overwrite the existing driver packages with the new driver packages and

start the HCM Agent automatically, use the following command.

brocade_adapter_software_installer_windows_<platform>_<version>.exe

-DCHOSEN_INSTALL_SET=DRIVER -DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent

For example, to overwrite the existing drivers with the new drivers, use the following

command.

brocade_adapter_software_installer_windows_<platform>_<version>.exe

-DCHOSEN_INSTALL_SET=BOTH -DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent

-If VLAN configurations exist (CNAs and Fabric Adapter ports configured in CNA mode), a

backup message displays during upgrade or reinstallation of drivers. This message will

note the location where configurations were stored. You can restore these configurations

after installation completes.

•Linux systems

When upgrading the driver for Linux systems, you do not need to reboot the host system after

installation.

•Solaris systems

When upgrading the driver for Solaris systems, you must reboot the host system. The new

driver is effective after system reboot.

88 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using the Brocade Adapter Software Installer

•VMware systems

When upgrading the driver for VMware systems, you must reboot the host system. The new

driver is effective after system reboot. Because the ESX 5,0 driver installation process does not

enforce maintenance mode, it is recommended that you put the host in maintenance mode, as

since a system reboot is required after installation.

•Software installation or upgrade on a host system with a large number of adapters could take

much longer than normal.

NOTE

To make sure that the drivers and adapter boot code are synchronized, be sure to update your

adapter with the latest boot image from the Brocade adapters website at www.brocade.com/adapters

whenever you install or update adapter driver packages. On the website, navigate to the drivers

Downloads page. Select your operating system from the Downloads list or download the ISO image.

Refer to “Boot code updates” on page 118 for update instructions.

Software downgrade using Adapter Software Installer

Although driver and HCM downgrades are not supported, the following procedures are

recommended for downgrading between versions 3.0, 2.3, 2.2, 2.1, 2.0, and 1.1.

NOTE

Downgrading the driver is not supported when downgrading from 3.0 to earlier versions. However, it

is possible to restore the 3.0 configuration for version 2.3 if you explicitly save the configuration

before removing 3.0 and installing version 2.3.

Downgrading HCM and driver or HCM only

To downgrade HCM and adapter drivers or HCM only, follow these steps.

1. Uninstall HCM and drivers or HCM only using procedures under “Software removal using

Adapter Software Uninstaller” on page 83.

2. When a message box displays asking to back up the HCM configuration, be sure to click Yes

and proceed with the software removal. (Refer to “HCM configuration data” on page 114).

3. Install the desired version of the software using “Using the Brocade Adapter Software Installer”

on page 68.

4. During installation, when the “Found Backed up data” message displays prompting you to

restore old configurations, select to restore the data and continue with the installation.

Downgrading driver only

1. Uninstall existing drivers using the procedures under “Software removal using Adapter

Software Uninstaller” on page 83.

2. Install new drivers using the procedures under “Using the Brocade Adapter Software Installer”

on page 68.

Brocade Adapters Installation and Reference Manual 89

53-1002144-01

Using software installation scripts and system commands 3

Installer log

A status log is available after installation that provides complete status of installed software

components. The name of the installed component, version, and location in file system are

provided. The Installation_Status.log is in the following locations:

•Windows - <user home>/brocade

•Linux and Solaris - /var/log/brocade

Using software installation scripts and system commands

This section provides instructions for to use Brocade “native” installation scripts and commands to

install, remove, and upgrade individual driver package components described under “Driver

packages” on page 37. You can use these steps for installing software on your system instead of

using the Brocade Adapter Software Installer.

NOTE

To upgrade existing software using the Brocade Adapter Software Installer, refer to “Using the

GUI-based installer” on page 69.

Instructions are provided in this section for the following tasks:

•Selectively installing network drivers, storage drivers, and utilities to Windows, Linux, and

VMware systems using Brocade-provided installation scripts.

•Installing driver packages on Solaris systems using “native” system installer commands.

Software installation and removal notes

•The following steps assume that the host’s operating system is functioning normally and that

all adapters have been installed in the system.

•When upgrading Windows drivers, install the new driver without first removing the existing

driver. This is the is recommended procedure.

•Software installation or upgrade on a host system with a large number of adapters could take

much longer than normal.

•Download the driver package for your host system operating system and platform from the

Brocade adapters website at www.brocade.com/adapters. On the website, navigate to the

Downloads page. Select your operating system from the Downloads list or download the ISO

image

Note that you can also download an ISO 9660 (.iso) optical disk image containing the latest

Brocade HCM, adapter driver package, and documentation from which you can create a CD.

You can carry this CD to your system for installation.

NOTE

For Windows systems only, using a DVD created with the ISO image will automatically start the

correct installer program for your system. Make sure that the autorun feature is enabled.

90 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

•Refer to “Software installation and driver packages” on page 43 and “Operating system

support” on page 40 for details on driver packages and operating system support. Also

download the latest release notes on the Brocade adapters website at

www.brocade.com/adapters. On the website, navigate to the drivers Downloads page. Select an

operating system from the Download Individual Software Installers, Drivers, or Documents list, and

then download the release notes.

•There are firewall issues with HCM Agent on Windows 2008 and VMware systems. When

installing the driver package on these systems, open TCP/IP port 34568 to allow agent

communication with HCM.

-For VMware, use the following commands to open port 34568:

/usr/sbin/cfg-firewall -o 34568,tcp,in,https

/usr/sbin/cfg-firewall -o 34568,udp,out,https

-For Windows, use Windows Firewall and Advanced Service (WFAS) to open port 34568.

•The storage driver will claim all Brocade Fiber Channel HBAs, FCoE CNAs, and Fabric Adapters

with ports configured in HBA and CNA mode installed in a system.

•Installing a driver package or other adapter software does not automatically start the HCM

Agent. You must manually start the agent using instructions under “HCM Agent operations” on

page 112.

•If removing a driver package or other adapter software, first exit the HCM application and stop

the HCM Agent. Stop the agent using instructions under “HCM Agent operations” on page 112.

•Removing driver packages with system commands is not recommended since this only

removes the driver from the operating system stack and does not clean up the driver and utility

directories. Use the Brocade Adapter Software Uninstaller program instead.

•When upgrading Windows 2008 drivers on adapters used for booting over SAN, install the new

driver without removing the existing driver. Installation may fail and the operating system will

become unbootable if you remove the existing driver before installing a new driver.

•To make sure that the drivers and adapter boot code are synchronized, be sure to update your

adapter with the latest boot image f whenever you install or update adapter driver packages.

Use the following steps.

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the Downloads page.

c. Select your operating system from the Downloads list.

d. Download the boot image file from the “Boot Code” section.

e. Refer to “Boot code updates” on page 118 for instructions to install the image.

•Installing management utilities on Windows systems creates a Brocade BCU desktop shortcut

on your system desktop. Use this to launch the BCU> command prompt and enter BCU

commands.

•Since the ESX 5,0 driver installation process does not enforce maintenance mode, it is

recommended that you put the host in maintenance mode, since a system reboot is required

after installation.

Brocade Adapters Installation and Reference Manual 91

53-1002144-01

Using software installation scripts and system commands 3

Driver installation and removal on Windows systems

Use the following procedures to install, remove, and update driver packages on a Windows system.

Only one driver installation is required for all adapters (CNAs, HBAs, or Fabric Adapters) installed in

a host system.

Installation Notes

•Before installing the driver on Windows systems, install the following hot fixes from the Microsoft

“Help and Support” website, then reboot the system:

-Windows 2003

KB932755 (or later) is the minimum requirement.

KB943545 is recommended if the HP command view management application is used to

manage HP EVA arrays in the target system.

-Windows 2008

KB968675 is recommended. This fixes a non-paged memory leak in a Windows 2008 storage

stack.

KB2490742 is recommended when installing storage drivers to avoid a “Ox000000B8” stop

error when shutting down or hibernating a system running Windows 7 or Windows Server 2008

R2.

KB958015 is recommended for CNAs and Fabric Adapter ports configured in CNA mode.

-Windows 2008 R2

KB977977 is recommended for CNAs and Fabric Adapter ports configured in CNA mode.

•Although you can install the driver using the Windows Device Manager, use the driver installer

script (brocade_installer.bat) or use the Brocade GUI- or command-based Adapter Software

Installer (brocade_adapter_software_installer_windows_<platform>_<version>.exe) instead

for installing, removing, and upgrading the driver. The Brocade installer programs provide

these advantages:

-Automatically updates all Brocade adapters in one step. With Device Manager, you will

need to update each adapter instance.

-Enables the driver to register the symbolic names for the adapter ports with the switch.

With Device Manager, the driver cannot obtain the operating system information to

-Avoids errors, especially for Windows 2003 systems, that can occur from removing

software with the Device Manager that was originally installed with the Brocade installer

programs, then attempting future updates or removals.

•If removing driver packages or the HCM agent, determine if the HCM Agent is running using

procedures under “HCM Agent operations” on page 112. If it is, stop the agent using steps

under the same heading.

92 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

Installing and removing drivers on Windows systems

Use these steps to install storage and network driver packages on Windows systems. Refer to

“Software installation and driver packages” on page 43 for a description of Windows driver

packages.

1. Boot the host and log on with Administrator privileges.

NOTE

For Windows 2008 systems, you must disable User Account Control (UAC) to use the installer

program (brocade_installer.bat). To do this, select Control Panel > User Accounts > User

Accounts to display the User Accounts task window, then turn User Account Control off.

2. Create a “CNA Drivers” or “HBA Drivers” directory in your host’s file system depending on your

installed adapter or mode configurations for installed Fabric Adapter ports.

3. Download the appropriate .exe driver package for your system. Refer to “Software installation

and driver packages” on page 43 for a description of Windows driver packages.

4. Extract the driver packages to the folder you created in step 2 using the following steps.

a. Double-click the package file (for example, brocade_driver_win2003_x86_<version>.exe)

to extract the driver files.

b. Enter a path or browse to the driver directory where you want to install the extracted files

when prompted (for example, C:\Adapter Drivers). Note that you can specify a directory

other than the default directory.

5. Go to the command prompt and change directories (cd) to the path where you extracted files in

step 4.

6. Enter the following command, using appropriate parameters to install or uninstall the driver

package:

brocade_install.bat [INSTALL_OP=<INSTALL | UNINSTALL | PREINSTALL>]

[DRIVER_TYPE=<HBA | CNA | AUTO] [LOG_FILE_PATH=<path to installer log>]

[FORCED_INSTALL=TRUE] [SILENT_INSTALL=TRUE] [SNMP=TRUE] [SNMP_ONLY=TRUE]

[W2K8_HOTFIX=<[""]|[<KBnnnnnn>:<Required|Optional><Description>]]>]

[W2K3_HOTFIX=<[""]|[<KBnnnnnn>:<Required|Optional><Description>]]>]

where:

•INSTALL_OP=

INSTALL - Installs the storage and network drivers. This is the default behavior no options

are used with brocade_install.bat.

UNINSTALL - Removes all drivers corresponding to the DRIVER_TYPE option.

PREINSTALL - Depending on the DRIVER_TYPE option used, either the HBA, CNA (or both)

driver will install to the driver store on the host system, However, this driver is only used

when a new adapter is installed into an empty slot or an existing adapter is replaced. The

operating system will continue to load the existing driver until this occurs. This is useful in

mass deployment of operating systems when adapters have not been installed. Please

note that preinstallation will not automatically be attempted when the installer does not

find the corresponding hardware.

Brocade Adapters Installation and Reference Manual 93

53-1002144-01

Using software installation scripts and system commands 3

•DRIVER_TYPE=

HBA - The operation as specified by INSTALL_OP will be performed for Fibre Channel

drivers only.

CNA - The operation as specified by INSTALL_OP will be performed for network drivers only.

AUTO - The operation as specified by INSTALL_OP will be performed for the drivers for

adapters that are present in the system.

•LOG_FILE_PATH

Specify path to installer log. Quote marks need to enclose the path needs when it contains

a space. You can also specify system environmental variables for the path component. For

example, LOG_FILE_PATH="%ProgramFiles%"\Brocade\Adapter\Driver\util\myinstal.log".

•FORCED_INSTALL= TRUE

Use this option to force driver installation when the operating system displays messages

such as, “The existing driver on this system is already better than the new one you are

trying to install.”

•SILENT_INSTALL=TRUE

Use this in automated script environments to avoid displaying any Windows dialog boxes

during installation failure scenarios. In this case, you must analyze the log file to decode

any failures during driver installation, uninstallation, or preinstallation operations.

•W2K3_HOTFIX, W2K8_HOTFIX=

If INSTALL_OP = INSTALL, use this option to override the installed hot fix with a new hot fix

or to avoid checking for a hot fix.

To specify a new hot fix for override, use the format

“<KBnnnnnn>:<Required|Optional>:<Description>”. For example W2K8_HOTFIX=

“KB9987654:Required:newer_hotfix”.

To avoid checking for hot fix, use the value “”. For example, W2K3_HOTFIX=””.

•SNMP=TRUE

If management utilities containing SNMP files were installed, this installs the SNMP

subagent, drivers, and other utilities.

•SNMP_ONLY=TRUE

If management utilities containing SNMP files were installed, this installs the SNMP

subagent only.

After entering options to install the software, a message box may display indicating that the

target (existing) driver is newer than the source (upgrade) driver. Depending on the number of

adapters installed, this message box may display more than once.

NOTE

You can also use the brocade_install.bat command to install the SNMP subagent. For details,

refer to “Installing SNMP subagent” on page 109 for details.

7. Cli ck Continue Anyway each time the message box displays to continue.

As installation continues, a series of screens may display. The Command Prompt should return

when installation completes.

8. If required by your Windows system, reboot the host. VMware and Solaris require rebooting

after installation.

94 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

9. Verify installation by launching the Device Manager to display all installed devices.

•For CNAs, HBAs, and Fabric Adapters, when you expand the list of SCSI and RAID

controllers or Storage controllers an instance of the adapter model should display for

adapter port installed.

•For CNAs and Fabric Adapter ports configured in CNA or NIC mode, when you expand

Network adapters, an instance of Brocade 10G Ethernet Adapter should also display for

each port installed.

For example, if two two-port CNAs (total of four ports) are installed, four instances of the

adapter model display (two under SCSI and RAID controllers and two under Network adapters).

As another example, if only one port on a Fabric Adapter is configured in CNA or NIC mode, two

instances of the adapter model display (one under SCSI and RAID controllers and one under

Network adapters).

10. If device instances do not display and instead instances display with yellow question marks

under Other Devices, scan the Device Manager for hardware changes. To scan, right click on

any device in the list and select Scan for hardware changes.

After you scan for changes, the adapter should display in the Device Manager as described

under step 9.

11. If necessary, start the HCM Agent using steps under “HCM Agent operations” on page 112.

NOTE

Manually installing the driver package does not automatically start the HCM Agent.

12. When the driver is installed and the host system is connected to the fabric turn on host power

and verify adapter operation. Verify proper LED operation for stand-up adapters by referring to

“Adapter LED operation (stand-up adapters)” on page 184.

Command examples

Following are examples of using the brocade_install.bat command to install driver packages on

Windows systems.

•Install all drivers

brocade_install.bat

•Install all drivers in silent mode

brocade_install.bat SILENT_INSTALL=TRUE

•Uninstall all drivers

brocade_install.bat INSTALL_OP=UNINSTALL

•Install the Fibre Channel (storage) driver only

brocade_install.bat DRIVER_TYPE=HBA

•To uninstall FC driver only

brocade_install.bat INSTALL_OP=UNINSTALL DRIVER_TYPE=HBA

•Forcefully install the drivers

brocade_install.bat FORCED_INSTALL=TRUE

•Override the installed hotfix with a new hotfix

Brocade Adapters Installation and Reference Manual 95

53-1002144-01

Using software installation scripts and system commands 3

brocade_install.bat W2K8_HOTFIX= “KB9987654:Required:newer_hotfix”

•Avoid checking for hot fix

brocade_install.bat W2K3_HOTFIX=""

Upgrading driver on Windows systems

To update the drivers, follow procedures under “Installing and removing drivers on Windows

systems” on page 92.

Notes:

•When upgrading the driver for Windows systems, you do not need to reboot the host system as

the driver upgrades immediately. The upgrade reloads the adapter firmware and reinitializes

the link.

•When upgrading Windows 2008 drivers on adapters used for booting over SAN, install the new

driver without removing the existing driver. If you remove the existing driver before installing a

new driver, installation may fail and the operating system will become unbootable.

Driver installation and removal on Linux systems

Use the install script to selectively install storage driver packages, network driver packages, and

utilities to Linux systems.

The driver package is provided as an RPM package. If you are using a supported Linux driver

package and standard host configuration, you can use these RPMs. Refer to “Software installation

and driver packages” on page 43 for a description of packages and kernel versions that they

support.

1. Boot the host and log on with Administrator privileges.

2. Create an installation directory such as /opt/CNA or /opt/HBA, depending on your adapter.

3. Download the appropriate .tar.gz file for your Linux distribution. Refer to “Software installation

and driver packages” on page 43 for a description of Linux driver packages.

4. Extract the driver packages to the directory you created in step 2 using the following steps.

a. Enter a path or browse to the driver directory where you want to install the extracted files

when prompted (for example /opt/CNA or /opt/HBA). Note that you can specify a directory

other than the default directory.

b. To untar the source-based RPM for all RHEL and SLES Linux distributions.

tar -zxvf brocade_driver_linux_<version>.tar.gz

c. To untar the precompiled RPMs for RHEL distributions.

tar -zxvf brocade_driver_linux__rhel_<version>.tar.gz

d. To untar the precompiled RPMs for SLES distributions.

tar -zxvf brocade_driver_linux__sles_<version>.tar.gz

5. Enter the following command to run the installer on RHEL and SLES systems:

brocade_install_rhel.sh

[-u,-h][--update\--add\--rm-initrd][--force-uninstall][--snmp] [--snmp-only]

96 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

brocade_install_sles.sh [-u,-h] [--update\--add\--rm-initrd]

[--force-uninstall]

where:

-u Uninstalls driver RPM packages.

-h Displays help for install script.

Initial RAM disk options:

--update-initrd Updates or adds the storage driver (bfa) to initrd. Note that you should only

update the initrd if you are intending to use the boot from SAN feature. If the

storage driver (bfa) is listed under /etc/sysconfig/kernel (SUSE) and

/etc/modprobe.conf (RHEL), RPM installation automatically updates the

initrd.

--add-initrd Adds the driver to initrd and rebuilds.

--rm-initrd Removes the driver from initrd and rebuilds.

--force-uninstall Removes all installed drivers (network, storage, and utilities). Reboot may be

required if removal of bna or bfa driver fails.

--snmp If management utilities containing SNMP files were installed, this installs the

SNMP subagent, drivers, and other utilities.

--snmp-only If management utilities containing SNMP files were installed, this installs the

SNMP subagent only.

Examples:

•To install all RPMs (network, storage, and utilities), enter one of the following commands:

brocade_install_rhel.sh

brocade_install_sles.sh

•To install all RPMs and add storage (bfa) driver to initrd, enter one of the following

commands.

brocade_install_rhel.sh --update-initrd

brocade_install_sles.sh --update-initrd

•To remove all RPMs, enter one of the following commands:

brocade_install_rhel.sh -u

brocade_install_sles.sh -u

•To force removal of all RPMs, enter one of the following commands.

brocade_install_rhel.sh --force-uninstall

brocade_install_sles.sh --force-uninstall

•To display help, enter one of the following commands:

brocade_install_rhel.sh -h

brocade_install_sles.sh -h

6. Verify if a network or storage driver package is loaded to the system with the following

commands:

rpm -qa|grep bfa

This command prints the names of the storage driver package (bfa) if installed.

rpm -qa|grep bna

Brocade Adapters Installation and Reference Manual 97

53-1002144-01

Using software installation scripts and system commands 3

This command prints the names of the network driver package (bna) if installed.

lspci

This utility displays information about all PCI buses in the system and all devices connected to

them. Fibre Channel: Brocade Communications Systems, Inc. displays for an HBA or Fabric

Adapter port configured in HBA mode. Fibre Channel: Brocade Communications Systems, Inc.

and Ethernet Controller display for a CNA or Fabric Adapter port configured in CNA or NIC mode

if driver packages have correctly loaded.

lsmod

This command displays information about all loaded modules. If bfa appears in the list, the

storage driver is loaded to the system. If bna appears in the list, the network driver is loaded to

the system.

dmesg

This command prints kernel boot messages. Entries for bfa (storage driver) and bna (network

driver) should display to indicate driver activity if the hardware and driver are installed

successfully.

7. Start the HCM Agent by using steps under “HCM Agent operations” on page 112.

NOTE

Manually installing the driver package with installation scripts does not automatically start the

HCM Agent.

8. When the driver is installed and the system is connected to the fabric, verify adapter operation.

Verify LED operation for stand-up adapters by referring to “Adapter LED operation (stand-up

adapters)” on page 184.

Upgrading driver on Linux systems

To update the driver package simply install the new driver and HCM package using steps under

“Driver installation and removal on Linux systems” on page 95.

NOTE

When upgrading the driver for Linux systems, you do not need to reboot the host system. The new

driver is effective after system reboot.

Driver installation and removal on Solaris systems

Use the following steps to install, remove, and upgrade the driver and utility packages on Solaris

systems.

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems, so Solaris options do not

apply to these adapters.

Installing driver packages on Solaris systems

Use the following steps to install driver and utility packages to Solaris systems. Driver packages

install as the following:

•Storage drivers - bfa_driver_<operating system>_<version>.pkg

98 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

•Network drivers - bna_driver_<operating system>_<version>.pkg

•User utilities - brcd_util_<operating system>_<version>.pkg

Refer to “Software installation and driver packages” on page 43 for a description of host systems

that this driver package supports.

NOTE

Root access is required to install or remove the driver package.

1. Log on to the Solaris system as a super user.

2. Copy the brocade_driver_<operating system>_<version>.tar to a temporary directory on your

system.

NOTE

brocade_driver_<operating system>_<version>.tar contains all drivers for specific Solaris

distributions. For example, brocade_driver_solaris10_<version>.tar contains all storage

drivers for Solaris 10 systems, where <version> is the version number of the driver release.

3. Using the change directory (cd) command, change to the directory where you copied the driver

file.

4. Perform the following steps.

a. Enter the following command and press Enter to untar the file.

# tar xvf brocade_driver_<operating system>_<version>.tar

This extracts the driver, packages, utilities packages, and installation script:

•Storage drivers - bfa_driver_<operating system>_<version>.pkg

•Network drivers - bna_driver_<operating system>_<version>.pkg

•User utilities - brcd_util_<operating system>_<version>.pkg

•Installation script - brocade_install.sh

b. Enter the following command to remove all old packages (if installed) and install new ones.

# ./brocade_install.sh

5. Enter the following to restart, load the driver, and reconfigure the system:

# reboot --r

6. Verify if the driver and utility packages are loaded to the system with the following commands:

# pkginfo|grep bfa

# pkginfo|grep bna

# pkginfo|grep brcd-util

NOTE

You can use the pkginfo -l command to display details about installed drivers.

7. Start the HCM Agent by using steps under “HCM Agent operations” on page 112.

NOTE

Manually installing the driver package does not automatically start the HCM Agent.

Brocade Adapters Installation and Reference Manual 99

53-1002144-01

Using software installation scripts and system commands 3

8. When a driver is installed and the host system is connected to the fabric turn on host power

and verify adapter operation. Verify proper LED operation for stand-up adapters by referring to

“Adapter LED operation (stand-up adapters)” on page 184.

Removing driver packages from Solaris systems

Use the following steps to remove driver and utility packages.

NOTE

Root access is required to remove the packages.

1. Log on to your system as root user.

2. Determine if the driver and utility packages are installed using the following commands:

# pkginfo|grep bfa

# pkginfo|grep bna

# pkginfo|grep brcd-util

3. Determine if the HCM Agent is running using procedures under “HCM Agent operations” on

page 112. If it is, stop the agent using steps under the same heading.

4. From any directory, enter the following commands to remove installed packages:

# pkgrm bfa

# pkgrm bna

# bkgrm brcd-util

5. Respond to prompts “Do you want to remove this package?” by entering y.

6. Respond to prompts “Do you want to continue with the removal of this package?” by entering y.

After a series of messages, the following confirms removal:

# Removal of <bfa> was successful.

# Removal of <bna> was successful.

# Removal of <brcd-util> was successful.

Upgrading driver on Solaris systems

To update driver packages, simply install new packages using steps under “Installing driver

packages on Solaris systems” on page 97.

NOTE

When upgrading the drivers for Solaris systems, you must reboot the host system. The new drivers

are not effective until after system reboot.

Driver installation and removal on VMware systems

Instructions are provided in this section to install adapter drivers on ESX and ESXi systems.

NOTE

Since the ESX 5,0 driver installation process does not enforce maintenance mode, it is

recommended that you put the host in maintenance mode, as since a system reboot is required

after installation.

100 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

NOTE

Note that you can use the VMware Image Builder PowerCLI to create a

brocade_esx50_<version>.zip offline bundle and brocade_esx50_<version>.iso ESX 5.0

installation image that includes brocade drivers and utilities. Refer to your Image Builder

documentation for details on using Image Builder PowerCLI.

Installation on ESX 4.X and ESXi 5.0 systems

Use the following steps for ESX 4.X and ESXi 5.0 systems. For ESXi 4.X systems, use steps under

“Installation on ESXi 4.0 and 4.1 systems” on page 101.

Drivers are provided as ISO images packaged in a tarball. Use the install script to selectively install

storage and network driver packages with utilities to VMware systems. Refer to “Software

installation and driver packages” on page 43 for a description of host systems that this VMware

driver package supports.

1. Download, then copy the VMware driver package to your system’s /tmp directory.

2. From the temporary directory, extract the file using the following commands.

tar zxvf brocade_driver_<esxversion>_<driverversion>.tar.gz

3. Enter one of the following command to run the installer.

•For ESX 4.X systems, use the following command.

brocade_install.sh {-u,-h, -t}

where:

u Uninstalls driver RPM packages.

h Displays help for install script.

t Installs tools only.

•For ESX 5.0 systems, use the following command.

brocade_install_esxi.sh {-u,-h, -t}

where:

u Uninstalls driver RPM packages.

h Displays help for install script.

t Installs tools only.

Examples:

•To install network and storage RPMs with utilities, enter one of the following commands:

brocade_install.sh

brocade_install_esxi.sh

•To remove the storage and network RPM and utilities, enter one of the following command:

brocade_install.sh -u

brocade_install_esxi.sh -u

Brocade Adapters Installation and Reference Manual 101

53-1002144-01

Using software installation scripts and system commands 3

•To display help, enter one of the following commands:

brocade_install.sh -h

brocade_install_esxi.sh -h

4. Reboot the system.

5. Determine if the driver package is installed using the following commands:

esxcfg-module -l

This lists loaded module names. Verify that an entry for bfa exists for the storage driver and an

entry for bna exists for the network driver.

cat /proc/vmware/version

This displays the latest versions of installed drivers. Look for bfa (storage driver) and bna

(network driver) entries and related build number.

6. Start the HCM Agent by using steps under “HCM Agent operations” on page 112.

NOTE

Manually installing the driver package does not automatically start the HCM Agent.

7. When the driver is installed and host is connected to the fabric, turn on the host system and

verify adapter operation. Verify proper LED operation for stand-up adapters by referring to one

of the following locations:

•“Adapter LED operation (stand-up adapters)” on page 184.

•“Adapter LED operation (stand-up adapters)” on page 191

Installation on ESXi 4.0 and 4.1 systems

Drivers are provided as ISO images packaged in a tarball. Use the install script to selectively install

storage and network driver packages with utilities to VMware systems. Refer to “Software

installation and driver packages” on page 43 for a description of host systems that this VMware

driver package supports.

Prerequisites

•The vSphere Management Assistant (vMA) must be installed on an ESX system other than

where you are installing the driver. Download vMA from the VMware website. Once vMA is

downloaded please refer to the vSphere Management Assistant Guide for instructions on how

to deploy vMA.

•Put the ESXi server (where the driver is to be installed) in maintenance mode using vSphere

client. Using the vSphere Client, right click ESXi and select the Enter Maintenance Mode

option.

Procedure

1. Download the VMware driver package from the Brocade website, then copy it to a temporary

(/tmp) directory on your ESXi system.

2. From the temporary directory, extract the file using the following command:

tar zxvf brocade_driver_<esxversion>_<driverversion>.tar.gz

3. Power on the vMA virtual machine.

4. Follow instructions from vSphere Management Assistant Guide to set DHCP and the password.

102 Brocade Adapters Installation and Reference Manual

53-1002144-01

Using software installation scripts and system commands

5. Log in as vi-admin, using the password from step 4.

6. Copy the adapter driver iso file from the temporary directory to the vMA.

7. Run the following command for superuser privileges:

# sudo -s

8. When prompted for the password, enter the superuser account password (same as from

step 4).

9. Add the ESXi server IP Address to vMA using the following command.

# vifp addserver <ESXi address>

where

ESXi address ESXi server's IP Address where driver is to be installed.

10. Run the following command to make sure that the added ESXi server is listed in the vMA.

vifp listservers

11. Execute the following command on the vMA terminal.

# vifpinit <ESXi address>

where

ESXi address ESXi server's IP entered at step 9.

12. Mount the adapter driver iso file on a temporary directory such as /ISO. Create /ISO if does not

exist.

# mkdir -p /ISO

# mount -o loop <Brocade Driver ISO file> /ISO

As an example,

# mount -o loop bfa_esx40_2.3.0.0.iso /ISO

13. Scan the ESXi 4 host against the driver CD bulletin IDs using the following command.

# vihostupdate -s --bundle=<path of driver.zip in mount location>

As an example,

# vihostupdate -s --bundle=/ISO/offline-bundle/offline-bundle.zip

14. Install the driver CD bulletin IDs using the following command.

# vihostupdate -i --bundle=<path of driver.zip in mount location>

As an example,

# vihostupdate -i --bundle=/ISO/offline-bundle/offline-bundle.zip

15. Unmount the adapter driver ISO and delete the temporary “/ISO” directory created in step 12

using the following commands

# umount /ISO

# rmdir -p /ISO

16. Repeat steps 12-15 for each adapter driver to be installed.

17. After the host updates successfully, exit from maintenance mode.

Brocade Adapters Installation and Reference Manual 103

53-1002144-01

Confirming driver package installation 3

Using the vSphere Client, right click ESXi and choose the Exit Maintenance Mode option.

18. Reboot ESXi 4.

Right-click the ESXi 4 server and select Reboot.

NOTE

Be sure to reboot ESXi server where we are installing the driver and NOT the vMA

19. After the ESXi server has rebooted, run the following command to make sure the driver is

installed. The Brocade driver should show up in the list

# vihostupdate -q

Upgrading driver on VMware systems

To update the driver package, simply install the new driver using steps under “Driver installation

and removal on VMware systems” on page 99.

NOTE

When upgrading the driver for VMware systems, you must reboot the host system. The new driver is

effective after system reboot.

Confirming driver package installation

Adapter driver packages from Brocade contain the current driver, firmware, and HCM agent for

specific operating systems. Make sure the correct package is installed for your operating system.

Current driver packages are listed under “Software installation and driver packages” on page 43.

An out of date driver may cause the following problems:

•Storage devices and targets not being discovered by device manager or appearing incorrectly

in the host’s device manager.

•Improper or erratic behavior of HCM (installed driver package may not support HCM version).

•Host operating system not recognizing adapter installation.

•Operating system errors (blue screen).

NOTE

If the driver is not installed, try re-installing the driver or re-installing the adapter hardware and then

the driver.

You can use HCM and tools available through your host’s operating system to obtain information

such as driver name, driver version, adapter WWN, adapter PWWNs, firmware name and version,

and current BIOS version.

104 Brocade Adapters Installation and Reference Manual

53-1002144-01

Confirming driver package installation

Confirming driver installation with HCM

Following is the HCM procedure to display adapter information.

1. Launch HCM.

2. Select the adapter in the device tree.

3. Select the Properties tab in the right pane to display the Properties dialog box.

The dialog box displays adapter properties.

Confirming driver installation with Windows tools

You can use two methods to determine driver installation, depending on your Windows installation:

the Driver Verifier and Device Manager.

Driver Verifier Manager

Verify that the adapter storage driver (bfa) is loaded for HBAs, CNAs, Fabric Adapters and that the

storage driver and network driver (bna) are loaded for CNAs and Fabric Adapters with ports

configured in CNA or NIC mode using the Driver Verifier Manager tool (Verifier.exe). The verifier.exe

command is located in the Windows\System32 folder in Windows Server 2003 systems.

Select the option to display the following information about currently installed drivers:

•Loaded: The driver is currently loaded and verified.

•Unloaded: The driver is not currently loaded, but it was loaded at least once since you restarted

the system.

•Never Loaded: The driver was never loaded. This status can indicate that the driver's image file

is corrupted or that you specified a driver name that is missing from the system.

Device Manager

Verify if the driver is installed and Windows is recognizing the adapter using the following steps.

1. Open the Device Manager.

•For CNAs, HBAs, and Fabric Adapters, when you expand the list of SCSI and RAID

controllers or Storage controllers an instance of the adapter model should display for

adapter port installed.

•For CNAs and Fabric Adapter ports configured in CNA or NIC mode, when you expand

Network adapters, an instance of Brocade 10G Ethernet Adapter should also display for

each port installed.

For example, if two two-port CNAs (total of four ports) are installed, four instances of the

adapter model display (two under SCSI and RAID controllers and two under Network adapters).

As another example, if only one port on a Fabric Adapter is configured in CNA or NIC mode, two

instances of the adapter model display (one under SCSI and RAID controllers and one under

Network adapters).

2. Right-click an instance of your adapter displayed under Device Manager.

3. Select Properties to display the Properties dialog box.

Brocade Adapters Installation and Reference Manual 105

53-1002144-01

Confirming driver package installation 3

4. Click the Driver tab to display the driver date and version. Click Driver Details for more

information.

NOTE

If driver is not installed, try re-installing the driver or re-installing the adapter hardware and

then the driver.

Linux

Verify if the adapter driver installed successfully using the following commands:

•# rpm -qa|grep -i bfa

This command prints the names of the Brocade adapter storage driver package (bfa) if

installed.

•# rpm -qa|grep -i bna

This command prints the names of the Brocade adapter network driver package (bfa) if

installed.

•# lspci

This utility displays information about all PCI buses in the system and all devices connected to

them. Fibre Channel: Brocade Communications Systems, Inc. displays for an HBA or Fabric

Adapter port configured in HBA mode. Fibre Channel: Brocade Communications Systems, Inc.

and Ethernet Controller display for a CNA or Fabric Adapter port configured in CNA or NIC mode

if driver packages have correctly loaded.

•# lsmod

This command displays information about all loaded modules. If bfa appears in the list, the

storage driver is loaded to the system. If bna appears in the list, the network driver is loaded to

the system.

•# dmesg

This command prints kernel boot messages. Entries for bfa (storage driver) and bna (network

driver) should display to indicate driver activity if the hardware and driver are installed

successfully.

•These commands display the location of the driver modules if loaded to the system:

-The following command displays the storage driver module location. The module will have

a bfa prefix.

# modprobe -l bfa

-The following command displays the network driver module location. The module will have

a bfa prefix.

# modprobe -l bna

106 Brocade Adapters Installation and Reference Manual

53-1002144-01

Confirming driver package installation

Confirming driver installation with Solaris tools

Verify if the driver packages installed successfully using the following commands:

NOTE

Brocade 804 and 1007 adapters are not supported on Solaris systems, so commands in this section

do not apply to these adapters.

•These commands display information about loaded kernel modules.

modinfo|grep bfa

modinfo|grep bna

If the storage driver package is installed, bfa Brocade Fibre Channel Adapter Driver should

display.

If the network driver package is installed, bna Brocade Fibre Channel Adapter Driver should

display.

•These commands check for and lists the installed driver package files.

pkgchk -nv bfa

pkgchk -nv bna

•This command displays all available information about software packages or sets that are

installed on the system.

pkginfo -l

For example, if the storage driver package is installed, bfa_pkg should display with a

“complete” install status in the list of installed packages.

PKGINST: bfa

NAME: Brocade Fibre Channel Adapter Driver

CATEGORY: system

ARCH: sparc&i386

VERSION: alpha_bld31_20080502_1205

BASEDIR: /

VENDOR: Brocade

DESC: 32 bit & 64 bit Device driver for Brocade Fibre Channel adapters

PSTAMP: 20080115150824

INSTDATE: May 02 2008 18:22

HOTLINE: Please contact your local service provider

STATUS: completely installed

VMware

Verify if the adapter driver installed successfully using the following commands:

esxcli software vib list | grep bfa

Brocade Adapters Installation and Reference Manual 107

53-1002144-01

Confirming driver package installation 3

Confirming driver installation with VMware tools

Verify if the driver installed successfully using the following commands:

•The following commands print the names of the Brocade storage driver (bfa) if installed.

-For ESX 4.0 and 4.1 systems

# rpm -qa|grep -i bfa

-For ESX 5.0 systems

esxcli software vib list | grep bfa

•These commands print the names of the Brocade network driver (bna) if installed.

-For ESX 4.0 and 4.1 systems

# rpm -qa|grep -i bna

-For ESX 5.0 systems

esxcli software vib list | grep bfa

•This command lists loaded modules.

esxcfg-module -l

For the storage driver, verify that an entry for bfa exists and that the ID loaded.

For the network driver, verify that an entry for bna exists and that the ID loaded.

•This command displays the latest versions of installed drivers for ESX 4.X systems.

cat /proc/vmware/version

For the storage driver, verify that an entry for bfa exists.

For the network driver, verify that an entry for bna exists.

•These commands display the latest versions of installed drivers for ESX 5.0 systems

esxcli software vib list | grep bfa

esxcli software vib list | grep bna

•This command prints the names of the Brocade adapter storage driver package (bfa) if

installed.

rpm -qa|grep -i bfa

•This command prints the names of the Brocade adapter network driver package (bna) if

installed.

rpm -qa|grep -i bna

•This utility displays information about all PCI buses in the system and all devices connected to

them. Fibre Channel: Brocade Communications Systems, Inc. displays for an HBA or Fabric

Adapter port configured in HBA mode. Fibre Channel: Brocade Communications Systems, Inc.

and Ethernet Controller display for a CNA or Fabric Adapter port configured in CNA or NIC mode

if driver packages have correctly loaded.

# lspci

•This command displays information about all loaded modules. If bfa appears in the list, the

storage driver is loaded to the system. If bna appears in the list, the network driver is loaded to

the system.

108 Brocade Adapters Installation and Reference Manual

53-1002144-01

Verifying adapter installation

# lsmod

•This command prints kernel boot messages. Entries for bfa (storage driver) and bna (network

driver) should display to indicate driver activity if the hardware and driver are installed

successfully.

# dmesg

•These commands display the location of the driver modules if loaded to the system:

The following command displays the storage driver module location. The module will have a bfa

prefix.

# modprobe -l bfa

The following command displays the network driver module location. The module will have a

bfa prefix.

# modprobe -l bna

Verifying adapter installation

Problems with adapter operation may be due to improper hardware or software installation,

incompatibility between the adapter and your host system, improper configuration of the host

system, unsupported SFPs installed (stand-up adapters only), an improper cable connected from

adapter to the switch (stand-up adapters only), or an adapter is not operating within specifications.

Determine if problems exist because of these factors by verifying your installation with information

located in the following chapters in this manual.

•“Product Overview” on page 1.

This includes hardware and software compatibility information. This chapter also describes

software installation packages supported by host operating system and platforms.

•“Hardware Installation” on page 55.

This chapter provides hardware installation instructions.

•“Software Installation”

This chapter provides software installation instructions.

•“Specifications”

This chapter describes product specifications.

Following is a list of general items to verify during and after installation to avoid possible problems.

Verify the following and make corrections as necessary.

•Make sure that the adapter is correctly installed and seated in the connector in the host

system slot or connector. Press firmly down on the top of the adapter to make sure it has

seated in the connector. Check your system hardware manual and Fabric Adapter “Hardware

compatibility” on page 4, CNA “Hardware compatibility” on page 10, or HBA “Hardware

compatibility” on page 15 to verify that you installed the adapter in the correct slot.

•Make sure that the correct driver package for the host operating system and platform is

properly installed.

•If the host system requires special configuration to enable adapters, adapter connectors, and

interrupt request (IRQ) levels, verify these options in the system BIOS menu and in your system

documentation.

Brocade Adapters Installation and Reference Manual 109

53-1002144-01

Installing SNMP subagent 3

•Make sure that all Fibre Channel devices connected through the adapter and associated FCoE

or Fibre Channel switch are correctly connected, powered up, and operating correctly. If not

powered up, devices will be unavailable.

•Verify host system storage, switch, and operating system compatibility using the

interoperability matrices on the Brocade adapters website at www.brocade.com/adapters.

•Verify the following for stand-up adapters only:

-Observe LED operation on adapter and refer to the “Adapter LED operation” on page 177

for Fabric Adapters, “Adapter LED operation (stand-up adapters)” on page 191 for CNAs,

and “Adapter LED operation (stand-up adapters)” on page 184 for HBAs. LEDs are visible

through the adapter’s mounting bracket.

If LEDs indicate that the link between the adapter and switch is not operational, this could

mean that a problem on the link between the switch and adapter or that the driver is not

loaded and communicating with the switch.

-The adapter is installed in the appropriate connector in the host system.

-All small form factor pluggable (SFP) optic receivers are correctly installed, seated, and

latched in adapter SFP receiver slots.

-Cables are properly connected to the appropriate adapter port and seated in the SFP

connector.

-Correct options are configured for the slot where the adapter is installed,

•Verify the following for mezzanine adapters only:

-The blade server or server blade is turned on.

-The adapter is installed in the appropriate connector. On some blade servers or server

blades, connectors may only support a specific adapter type. Refer to your blade sever

documentation for help.

-Whether the blade server or server blade on which the adapter is installed is correctly

configured and installed in the blade system enclosure. Refer to your blade server and

blade system enclosure documentation for help.

-Any modules or blades in that support adapter operation are installed in the appropriate

enclosure bays and correctly configured. Refer to the documentation for your blade system

enclosure for help.

-The blade system enclosure is configured for adapter operation. Refer to your blade

system enclosure and documentation for blade system enclosure components for help.

-You are using the latest device drivers, firmware, and BIOS for the blade server (or server

blade) and other components in the blade system enclosure that support adapter

operation.

Installing SNMP subagent

Simple Network Management Protocol (SNMP) is supported by CNAs and by Fabric Adapters for

ports configured in CNA or NIC mode. For more information, refer to “Simple Network Management

Protocol” on page 34. Brocade adapter SNMP is supported through an extension to the SNMP

master agent, called the subagent, which processes SNMP queries for Brocade adapters. The

subagent is only supported on Linux and Windows systems. SNMP subagent files are copied to

your host system when you install adapter management utilities through HCM and the Brocade

Adapter Software Installer (BASI).

110 Brocade Adapters Installation and Reference Manual

53-1002144-01

Updating drivers with HCM

Windows systems

For Windows systems, use the following steps.

1. Go to the following directory where the SNMP files are installed.

c:\program files\brocade\adapter

2. Enter one of the following commands:

•brocade_install.bat SNMP=TRUE

Installs the SNMP subagent, drivers, and other utilities.

•brocade_install.bat SNMP_ONLY=TRUE

Installs only the SNMP subagent.

3. Start SNMP services using the following commands.

•service <snmpd> start

This starts the master agent “snmpd” service if it is not already running.

•service <bnasd> start

This starts the subagent “bnasd” service.

4. Start SNMP subagent services using the following steps.

a. Open Services (typically Start>Control Panel>Administrative Tools>Services)

b. Right-click SNMP and select Start.

Linux systems

1. Go to the following directory where the subagent files are installed.

/opt/brocade/adapter

2. For RHEL systems, enter one of the following commands:

•Enter brocade_install_rhel.sh --snmp to install the SNMP subagent, drivers, and other

utilities.

•Enter brocade_install_rhel.sh --snmp-only to install the SNMP subagent only

3. For SLES systems, enter one of the following commands:

•Enter brocade_install_rhel.sh --snmp to install the SNMP subagent, drivers, and other

utilities.

•Enter brocade_install_rhel.sh --snmp-only to install the SNMP subagent only

Updating drivers with HCM

You can update installed drivers on connected hosts using the Adapter Software dialog box in HCM.

Updating the driver updates all of the following components to the latest versions:

•Network and storage driver

•HCM Agent

•initrd file (Linux systems)

Brocade Adapters Installation and Reference Manual 111

53-1002144-01

Updating drivers with HCM 3

To update drivers with HCM, use the following steps:

1. Determine the correct driver package for your host system platform by reviewing Table 9 on

page 44.

2. Download the driver package for your host system operating system and platform from the

Brocade adapters website using se the following steps.

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the Downloads page.

c. Use one of these options to download the driver package:

•Select your host’s operating system from the Download Individual Software Installers,

Drivers, or Documents list, then select the driver package.

•Select Download ISO Image to download an ISO 9660 (.iso) optical disk image

containing the Brocade Adapter Software Installer, individual driver packages, HCM,

and documentation.

3. Select a host on the device tree, and then select Adapter Software under the Configure menu.

The Adapter Software dialog box displays.

4. Enter the filename of the updated driver in the Driver File text box.

Click the Browse button and navigate to the location of the driver file to update.

5. Select Start Update.

The selected file downloads. If an error occurs during the downloading process, an error

message displays.

6. Review the installation progress details that display in the dialog box to determine if the files

install successfully.

NOTE

During the installation, a warning message may display that the installed boot image is not

compatible with drivers being installed. You can obtain current boot image files from the

adapters website and install these through the Adapter Software dialog box. Refer to “Updating

boot code with HCM” on page 119 for instructions.

Notes

•This feature upgrades existing software installed on the host system. Downgrades are not

supported.

•During installation, dialog boxes validate installation success. Since the Solaris and VMware

ESX Server operating systems require a reboot for the driver update to take effect, successful

installation is not validated in the dialog boxes.

•Since the ESX 5,0 driver installation process does not enforce maintenance mode, it is

recommended that you put the host in maintenance mode, as since a system reboot is

required after installation.

112 Brocade Adapters Installation and Reference Manual

53-1002144-01

Installing HCM to a host from the HCM Agent

You can install HCM to any host system from a functioning HCM Agent on a server system. The

following are prerequisites for the server system:

•The adapter and driver package must be installed.

•The HCM agent must be running.

Use the following steps to install HCM:

1. Enter the following URL into your host system’s web browser:

https://server-host:34568/index.html

where:

server-host Is the IP address of a server system with the Brocade adapter and driver

installed and HCM Agent running.

34568 Is the TCP/IP port where the HCM Agent communicates with HCM.

2. Respond to prompts as required during HCM installation, and the HCM GUI will launch.

3. Log in to HCM when prompted.

To launch HCM in the future, use the HCM shortcut icon. On Windows, the shortcut is located under

Start menu > Brocade > Host Connectivity Manager. For Solaris, launch HCM from the command

prompt using the following command.

sh /opt/brocade/fchba/client/Host_Connectivity_Manager

HCM Agent operations

This section outlines the commands used to perform the following actions. The commands are

grouped and presented by operating system.

•Verifying that the HCM Agent is running

•Starting the agent

•Stopping the agent

•Changing the agent’s default communication port

NOTE

The HCM Agent will not start automatically if it stops unexpectedly during operation. You must restart

the agent.

Managing the HCM Agent on Linux and VMware systems

Use the following commands:

•Determining agent operation.

/usr/bin/hcmagentservice status

•Starting the agent (agent will not restart if system reboots or agent stops unexpectedly).

/usr/bin/hcmagentservice start

Brocade Adapters Installation and Reference Manual 113

53-1002144-01

HCM Agent operations 3

•Starting the agent (agent restarts if system reboots).

chkconfig –-add hcmagentservice

•Stopping the agent.

/usr/bin/hcmagentservice stop

•Stopping the agent from restart after system reboots.

chkconfig –-del hcmagentservice

•Changing the default communication port. Use the following steps.

a. Change to the agent installation directory (default is

/opt/brocade/adapter/hbaagent/conf).

b. Edit abyss.conf to change the entry “SecurePort 34568” to any other nonconflicting

TCP/IP port (for example, SecurePort 4430).

Managing the HCM Agent on Solaris systems

Use the following commands:

NOTE

The Brocade 804 and 1007 adapters are not supported on Solaris systems, so Solaris options do

not apply.

•Determining agent operation

svcs hcmagentservice

•Starting the agent (agent will not restart if system reboots or agent stops unexpectedly)

svcadm enable -t hcmagentservice

•Starting the agent (agent restarts if system reboots)

svcadm enable hcmagentservice

•Stopping the agent

svcadm disable -t hcmagentservice

•Stopping the agent from restart after system reboots

svcadm disable hcmagentservice

•Changing the default communication port

a. Change to the agent installation directory (default is

/opt/brocade/adapter/hbaagent/conf).

b. Edit abyss.conf to change the entry “SecurePort 34568” to any other nonconflicting

TCP/IP port (for example, SecurePort 4430).

114 Brocade Adapters Installation and Reference Manual

53-1002144-01

HCM configuration data

Managing the HCM Agent on Windows systems

Use the following options:

•Determining agent operation

a. Run the services.msc command to display the Services window.

b. Right-click Brocade HCM Agent Service and select Status.

•Starting the agent (agent will not restart if system reboots or agent stops unexpectedly)

a. Run the services.msc command to display the Services window.

b. Right-click Brocade HCM Agent Service and select Start.

•Starting the agent (agent restarts if system reboots)

a. Run the services.msc command to display the Services window.

b. Right-click Brocade HCM Agent Service and select Start.

c. Right-click Brocade HCM Agent Service and select Properties.

d. Select the Automatic option in Startup type.

e. Click OK.

•Stopping the agent

a. Run the services.msc command to display the Services window.

b. Right-click Brocade HCM Agent Service and select Stop.

•Stopping the agent from restart after system reboots

a. Run the services.msc command to display the Services window.

b. Right-click Brocade HCM Agent Service and select Stop.

c. Right-click Brocade HCM Agent Service and select Properties.

d. Select the Manual option in Startup type.

e. Click OK.

•Changing the default communication port

a. Change to the agent installation directory (default is

c:/opt/brocade/adapter/hbaagent/conf).

b. Edit abyss.conf to change the entry “SecurePort 34568” to any other nonconflicting

TCP/IP port (for example, SecurePort 4430).

HCM configuration data

HCM configuration data is compatible between versions 3.0.x.x, 2.3.x.x, 2.2.x.x, 2.1.x.x, 2.0, 1.1.x.x,

and 1.0. Configuration data backed up when prompted during software removal with the Adapter

Software Uninstaller and when using the HCM Backup Data dialog box includes the following:

•Adapter application data

•HCM user data

Brocade Adapters Installation and Reference Manual 115

53-1002144-01

Setting IP address and subnet mask on CNAs 3

•Alias data

•Setup discovery data

•Syslog data

•HCM logging data

•Support save data

Backing up configuration data

Use the HCM Backup Data dialog box to back up configuration data before removing HCM. Also, be

sure to back up data when the backup message displays when removing software with the Adapter

Software Uninstaller.

Following are default locations for HCM configuration data:

•Versions 1.1.0.8 and above - <user home>\HCM\data

•Versions 1.1.0.6 and below - <installation location>\FC HBA\data

Restoring configuration data

Follow these guidelines when restoring configuration data backed up during software removal or

with the HCM Backup Data dialog box:

•For HCM 2.0 and earlier, you can only restore data that you backed up during software removal

when you are prompted to restore data during software installation.

•For HCM 2.0 and later, you can restore data when prompted to do so during software

installation or by using the HCM Restore Data dialog box.

Setting IP address and subnet mask on CNAs

After installing a CNA or Fabric Adapter with ports configured in CNA or NIC mode, you must assign

an IP address and subnet mask to function on a DCB network. Work with your network

administrator to obtain the correct address and mask for your network.

Windows

1. From Control Panel, select Network Connections.

2. Right-click the installed “Brocade Ethernet XX” Network Adapter Interface instance and click

Properties.

3. In the This connection uses the following items box, click Internet Protocol (TCP/IP), then click

Properties.

4. Select Use following IP address radio button, and configure the IP address and subnet mask.

5. Click OK to apply the configuration.

116 Brocade Adapters Installation and Reference Manual

53-1002144-01

Setting IP address and subnet mask on CNAs

Linux

Following is an example for using the ifconfig command to set the IP address and subnet mask.

Note that a CNA and a Fabric Adapter with ports configured in CNA or NIC mode are typically named

“eth0.”

ifconfig eth0 193.164.1.10 netmask 255.255.255.0 up

VMware

Please refer to ESX/ESXi Configuration Guide on network configuration for VMware ESX/ESXi 4.x

and 5.0.

Brocade Adapters Installation and Reference Manual 117

53-1002144-01

Chapter

Boot Code

In this chapter

•Boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

•Boot code updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

•Network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

•Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

•Fabric-based boot LUN discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

•Boot systems over SAN without operating system or local drive . . . . . . . . 167

•Updating Windows driver on adapter used for boot over SAN . . . . . . . . . . 170

Boot support

Boot support is provided for Brocade adapters and drivers installed on your host.

•To note changes to boot support and procedures detailed in this chapter, please download the

current release notes for your adapter software version from the Brocade adapters website

using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the release notes from the “Documentation” section.

The following system BIOS and platforms support Brocade adapters:

•Peripheral Component Interconnect (PCI) firmware 3.0 and earlier PCI BIOS versions

Boot code for PCI system

•BIOS

Boot code for x86 and x86_x64 platforms

•Unified Extensible Firmware Interface (UEFI)

Boot code for UEFI systems

NOTE

UEFI is not supported on the Brocade 804 adapter.

•PXE (preboot eXecution environment) and UNDI (universal network device interface)

Network boot support for x86 and x86_x64 platforms.

118 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot code updates

A single, updatable boot code image, stored in the adapter option read-only memory (option ROM)

memory, contains all boot code for supported host platforms.

NOTE

By default, BIOS and UEFI are enabled on adapter ports for booting over SAN.

Boot code updates

The adapter boot code contains the following:

•PCI BIOS 2.1 or later, PCI firmware 3.0

Boot code for PCI system

•BIOS

Boot code for x86 and x64 platforms

•Unified Extensible Firmware Interface (UEFI)

Boot code for UEFI systems

NOTE

UEFI is not supported on the Brocade 804 adapter.

•Adapter firmware

Update the adapter with the latest boot code image for installed Brocade adapters from the

Brocade adapters website at using the following steps.

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Downloads list to display appropriate download files.

4. Download the boot code image from the “Boot Code” area.

Update the boot code image file to the adapter installed on your host system using the Host

Connectivity Manager (HCM) and BCU commands. Although BCU updates the file from the host’s

local drive, you can use HCM to update from a remote system.

NOTE

All Brocade adapters installed in a host system must use the same boot code version.

NOTE

To keep drivers and boot code synchronized, be sure to update your adapter with the latest boot

image after you install or update adapter driver packages. Be sure to update drivers before updating

the boot code.

You can determine the current BIOS version installed on your adapter using the following methods:

•Viewing the BIOS that displays on your system screen during hardware reinitialization, just

before you are prompted to press Ctrl and B or Alt and B to enter the Brocade adapter

Configuration Utility.

•Entering the bcu adapter --query command. The installed BIOS version displays in the Flash

Information section of the command output.

Brocade Adapters Installation and Reference Manual 119

53-1002144-01

Boot code updates 4

•Viewing the adapter Properties panel in HCM. To view the panel, select the adapter in the

device tree, then click the Properties tab in the right pane.

For servers with operating system and Brocade adapter drivers installed, you can use BCU

commands or HCM directly to update boot code on adapters.

For servers without a hard disk, operating system, and adapter drivers installed, you can download

Linux LiveCD ISO images and create WinPE ISO images to boot the server, then use BCU

commands to update the boot code. For instructions on using these ISO images, refer to “Boot

systems over SAN without operating system or local drive” on page 167.

Updating boot code with HCM

Follow these steps to upgrade adapter flash memory with the latest boot code.

1. Download the boot code image zip file (brocade_adapter_boot_fw_<version>.zip) from the

Brocade adapters website using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the boot code image from the “Boot Firmware” area.

2. Extract the boot code image file.

3. Launch HCM.

4. Select a host on the device tree, and then select Adapter Software from the Configure menu.

The Adapter Software dialog box displays.

5. Enter the filename of the boot image in the Boot Image File text box.

Click the Browse button and navigate to the location of the file to update.

6. Click Start Update.

The selected file downloads. If an error occurs during the downloading process, an error

message displays.

7. Review the installation progress details that display in the dialog box to determine if the files

install successfully.

NOTE

Since updating the Solaris and VMware ESX driver requires rebooting the system, the boot code

cannot be updated along with the driver using the Adapter Software dialog box. HCM will not restrict

selecting the Boot image for update on the Solaris or ESX platforms.

120 Brocade Adapters Installation and Reference Manual

53-1002144-01

Network boot

Updating boot code with BCU commands

Use the following procedure to update boot code using BCU commands.

1. Download the boot code image zip file (brocade_adapter_boot_fw_<version>.zip) from the

Brocade adapters website to a folder on your local drive using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the boot code image from the “Boot Code” area.

2. Extract the boot code image file.

3. Enter the following BCU command:

bcu boot --update <ad_id> <image file> -a

where:

<ad_id> ID of the adapter (adapter)

<image file> name of firmware image file

-a Indicates that the boot code should be updated on all installed Brocade

adapters found on the host. Note that the adapter identification (ad_id)

should not be specified if the -a option is specified.

Network boot

The Network or the preboot eXecution environment (PXE) boot feature allows a host to boot its

operating system from a system located somewhere on the Ethernet LAN instead of the host’s local

disk or over the SAN. Booting from a remote LAN location provides the obvious advantage of

recovering quickly from a host or adapter malfunction. With PXE BIOS enabled on the adapter for a

specific port ID (or a VLAN ID for a specified port), replacing an old host with a new one involves

installing the adapter from the old host into the new one with the same configuration, then booting

the new host. The host’s operating system automatically boots from the remote LAN device.

NOTE

Enabling VLAN during network boot requires support from the operating system and has not been

fully validated due to operating system limitations.

Although fast recovery from a malfunction is a big advantage, following are considerations for the

host and adapter, depending on the replacement situation:

•Even though you install a similar host, the new host may require unique System BIOS options

and other settings, or internal IDE drives may need to be disconnected or disabled to initiate a

network boot.

•If replacing the Brocade adapter in a host with a similar Brocade adapter, you will need to

reconfigure the adapter to boot from the appropriate remote boot device.

•If replacing a host with a different model, you may be prompted to install the adapter driver for

the existing adapter.

Brocade Adapters Installation and Reference Manual 121

53-1002144-01

Network boot 4

Booting servers over the network can significantly streamline server administration and facilitate

server deployment. Instead of manually configuring each individual server, boot images on

LAN-based systems can be cloned and assigned to groups of servers at the same time. This not

only simplifies initial configuration, but makes ongoing software updates and maintenance much

easier to administer. When boot images are centrally managed on the network, server security,

integrity, and ability to recover data are also enhanced.

Following are additional benefits of booting over the network:

•Disaster recovery.

•More control and efficiency for software distribution.

•Booting diskless systems such as thin clients and dedicated systems.

•Automating system maintenance such as backups.

•Automating system checking such as virus scanning.

•Ensuring security where a guaranteed secure system is needed.

•Centralized storage management and administration of client workstations.

•Increased host reliability since operating system boots from highly available devices.

•Improved security.

Brocade BIOS support for network boot

The PXE mechanism, embedded in the adapter firmware, provides the ability to boot the host

operating system from a remote system located on the Ethernet LAN instead of the over the SAN or

from the host’s local disk. UNDI (universal network device interface) is an application program

interface (API) used by the PXE protocol to enable basic control of I/O. It performs other

administrative chores like setting up the MAC address and retrieving statistics through the adapter.

UNDI drivers are embedded in the adapter firmware.

When PXE boot or PXE BIOS is enabled, the following occurs to execute the system boot process:

•The PXE client (or adapter) uses the Dynamic Host Configuration Protocol (DHCP) protocol to

obtain information on available PXE boot servers on the network, such as the IP addresses,

from a DHCP server.

•The client contacts the appropriate boot server and obtains the file path for a network

bootstrap program (NBP).

•The client downloads the NBP into the system’s RAM using Trivial File Transfer (TFTP), verifies

it, and finally executes it.

•The PXE protocol sets the proper execution environment, such as availability of basic network

IO services and areas of client memory, then transfer control to the NBP.

•The NBP loads other files, such as configuration files and executable files. This action can run

diagnostics, execute firmware update utilities, or boot an entire operating system over the

network.

The PXE boot client is implemented in the adapter firmware. It supports legacy BIOS for servers

that do not support UEFI or UEFI for the newer servers. The Client PXE code provides the following

services for use by BIOS or a downloaded NBP.

•Preboot Services API

This provides several global control and information functions.

122 Brocade Adapters Installation and Reference Manual

53-1002144-01

Network boot

•TFTP API

The TFTP (Trivial File Transfer Protocol) API enables opening and closing of TFP connections

and reading packets from and writing packets to a TFTP connection. The PXE client downloads

the PXE boot loader from an TFTP server.

•UDP API

The User Datagram Protocol (UDP) API enables opening and closing of UDP connections and

reading packets from and writing packets to a UDP connection.

•UNDI API

The Universal Network Device Interface (UNDI) API enables basic control of I/O through the

adapter. This allows the use of universal protocol drivers that can be used on any network

interface that implements this API. UNDI is used by the PXE protocol to enable basic control of

I/O and performs other administrative chores like setting up the MAC address and retrieving

statistics through the adapter.

The Brocade PXE BIOS Configuration Utility (embedded with the boot code), BCU commands, and

the HCM allow you to perform the following tasks:

•Enable or disable BIOS.

When enabled, the system BIOS can execute the Brocade BIOS code for a specific adapter port

for PXE boot over the network.

•Set a VLAN ID to be used during network boot for the specific port.

NOTE

Enabling VLAN during network boot requires support from the operating system and has not

been fully validated due to operating system limitations.

Host system requirements for network boot

Consider these requirements for your host system when configuring network boot:

•You may need to disconnect internal IDE hard drives to disable them in the system BIOS and

allow the adapter boot BIOS to boot from the remote system. Some systems may allow these

drives to be enabled in the system BIOS if they correctly support the bootstrap protocol.

•Typically, the boot order must be CD-ROM, diskette, then remote boot system. After the

operating system installs, you can change this order if desired.

Due to the variety of configurations and variables in a LAN installations, your specific environment

must determine any additional requirements to guide installation and configuration for best

results.

Driver support for network boot

Refer to “Boot installation packages” on page 49. Table 10 on page 51 for applicable DUDs for

supported operating systems. Notes following the table identify DUDs that support network boot.

Note the following:

•Windows 2008

For network boot, the network driver is injected as part of the PXE Server prior to Windows

installation. The driver is passed over during PXE installation on the server.

Brocade Adapters Installation and Reference Manual 123

53-1002144-01

Network boot 4

•Linux (RHEL)

For supported versions later than RHEL 4.9, “nw” drivers support network (PXE) boot. Install

these drivers after fc drivers. For RHEL 4.9, network drives are part of a single ISO package.

•Linux (SLES)

Network drivers are part of a single ISO package.

•VMware ESX

Network boot is currently not supported.

Configuring network boot

Configure Network Boot on the adapter using the Brocade PXE BIOS Configuration Utility, BCU

commands, and HCM.

Configuring PXE BIOS using the Brocade Configuration Utility

Use the following procedures to configure network boot using the PXE PXE BIOS Configuration

Menu.

1. Power on the host system.

2. Watch the screen as the system boots. When “Brocade PXE 2.1 BIOS 2010-11 All rights

reserved” displays, press Alt+B or Ctrl+B.

The Brocade PXE BIOS Configuration Menu displays a list of installed adapter ports, similar to

the following.

[

Under the Ad No column, 1/0 and 1/1 are the first port and second port respectively on the

first installed adapter while 2/0 and 2/1 are the first and second port on the second installed

adapter.

The Configuration Utility supports a maximum of 16 ports, and 8 ports can display on a screen

at a time. Select Page Up to go to a previous screen or Page Down to go to the next screen.

124 Brocade Adapters Installation and Reference Manual

53-1002144-01

Network boot

NOTE

To bypass functions and stop loading BIOS, you must to press X for each port. Press X within 5

seconds to bypass execution of functions displayed on screens. If you press X after 5 seconds,

the next function (instead of current function) will be bypassed.

3. Select a port that you want to configure.

A screen similar to the following displays showing the port’s current BIOS version, MAC

address, and BIOS settings.

4. Change any parameters by following the instructions at the bottom of the BIOS Configuration

Utility screen. For example, use the following keys to select and change information:

•Up and Down keys - Scroll to a different field.

•Enter - Select a field and configure values.

•Left and Right arrow keys - Change a value.

•Alt - S - Save configuration values to adapter flash memory.

•Alt - Q - Exit the utility.

•Esc - Go back a screen.

•Page Up or Page Down - Go to preceding or next screen.

NOTE

To restore factory default settings, press R.

5. Configure the following settings as required:

•Enable or disable BIOS to support network boot.

You must enable BIOS to support network boot for an adapter port. If disabled, the host

system cannot boot from a network system. The default state for Adapter ports is disabled.

•Enter a VLAN ID for the port to be used during network boot. Enter a value from 0 through

4094.

Brocade Adapters Installation and Reference Manual 125

53-1002144-01

Network boot 4

NOTE

Enabling VLAN during network boot requires support from the operating system and has

not been fully validated due to operating system limitations.

6. Save or exit the configuration utility.

•To save the configuration, press the Alt and S keys.

•To exit without saving press the Alt and Q keys.

Configuring PXE BIOS using HCM or BCU commands

You can enable or disable PXE BIOS on a specific adapter port for booting over the network and

configure a VLAN ID for the port to be used during network boot using HCM dialog box options and

BCU commands,

NOTE

Enabling VLAN during network boot requires support from the operating system and has not been

fully validated due to operating system limitations.

Configuring PXE BIOS using HCM

To configure BIOS using HCM, perform the following steps.

1. Select one of the following in the device tree.

•CNA

•CNA port

•Fabric Adapter port configured in CNA or NIC mode

2. Select Configure > Basic Port Configuration to display the Basic Port Configuration dialog box.

3. Select the PXE Boot tab to display network boot parameters.

4. Perform any or all of the following actions as appropriate for your needs:

•Click the PXE Boot enable check box to enable or disable BIOS.

You must enable BIOS to support network boot for an adapter port. If disabled, the host

system cannot boot from network systems. The default setting for the adapter boot BIOS is

disabled.

•Enter a VLAN ID between 0 through 4094 for the port to be used during network boot

NOTE

Enabling VLAN during network boot requires support from the operating system and has

not been fully validated due to operating system limitations.

5. Click OK to exit and save values.

All configuration values are stored to adapter flash memory.

For details in using HCM options to enable BIOS for network boot, refer to the instructions for

configuring PXE boot support using HCM in the Host Configuration chapter of the Brocade Adapters

Administrator’s Guide.

126 Brocade Adapters Installation and Reference Manual

53-1002144-01

Network boot

Configuring PXE BIOS using BCU commands

You can use BCU commands to configure PXE BIOS for the following:

•CNA port

•Fabric Adapter port configured in CNA or NIC mode

Use BCU commands for the following tasks:

•Enable BIOS for PXE boot

You must enable BIOS to support network boot for an adapter port. If disabled, the host system

cannot boot from network systems. The default setting for the adapter boot BIOS is disabled.

We recommend to only enable one adapter port per host to boot over the network.

bcu ethboot --enable <port_id>

where:

port_id Specifies the ID of the port for which you want to set network boot attributes.

This could be the adapter_id/port_id, port PWWN, port name, or port

hardware path.

•Disable BIOS for PXE boot:

bcu ethboot --disable <port_id>

where:

port_id Specifies the ID of the port for which you want to set network boot attributes.

This could be the adapter_id/port_id, port PWWN, port name, or port

hardware path.

•Enter a VLAN ID for a specific port for use when booting over the network:

bcu ethboot --vlan <port_id> <vlan_id>

where:

port_id Specifies the ID of the port for which you want to set network boot attributes.

This could be the adapter_id/port_id, port PWWN, port name, or port

hardware path.

VLAN id A value from 0 through 4094.

NOTE

Enabling VLAN during network boot requires support from the operating system and has not

been fully validated due to operating system limitations.

•Displays the PXE configuration on the specified port.

bcu ethboot --query <port_id>

where:

port_id Specifies the ID of the port for which you want to display configuration

information.

All configuration values are stored to adapter flash memory.

Brocade Adapters Installation and Reference Manual 127

53-1002144-01

Boot over SAN 4

NOTE

For details on using BCU commands, refer to instructions for ethboot in the Brocade Command Utility

appendix of the Brocade Adapters Administrator’s Guide.

Boot over SAN

The “Boot Over SAN” feature allows a host to boot its operating system from a boot device directly

attached to the host system or located somewhere on the SAN instead of the host’s local disk.

Specifically, this “boot device” is a logical unit number (LUN) located on a storage device. LUNs can

be specifically targeted to boot hosts running Windows, Linux, or VMware, or Solaris. For more

information on how the Brocade Boot BIOS functions to implement this feature, refer to “Brocade

BIOS support for boot over SAN” on page 128.

Booting from a remote SAN location provides the obvious advantage of recovering quickly from a

host or adapter malfunction. With the adapter boot BIOS enabled for booting over SAN and

configured with boot device locations and boot sequences, replacing an old host with a new one

involves installing the adapter from the old host into the new one with the same configuration, then

booting the new host. The host’s operating system automatically boots from the remote SAN boot

device.

Although fast recovery from a malfunction is a big advantage, following are considerations for the

host and adapter, depending on the replacement situation:

•Even though you install a similar host, the new host may require unique System BIOS options

and other settings, or internal IDE drives may need to be disconnected or disabled to boot over

SAN.

•If replacing the Brocade adapter in a host with a similar Brocade adapter, you will need to

reconfigure the adapter and storage to boot from the appropriate remote boot device. You

must also update access on storage device ports to reflect the adapter PWWN. Finally, you

must update the single-initiator target zone created for the adapter port and storage device

port with the new adapter PWWN.

•If replacing a host with a different model, you may be prompted to install the adapter driver for

the existing adapter.

Booting servers from SAN-attached storage can significantly streamline server administration and

facilitate server deployment. Instead of manually configuring each individual server, boot images

on SAN-attached storage can be cloned and assigned to groups of servers at the same time. This

not only simplifies initial configuration, but makes ongoing software updates and maintenance

much easier to administer. When boot images are centrally managed on the SAN, server security,

integrity, and ability to recover data are also enhanced.

Following are additional benefits of boot over SAN:

•Eliminating the requirement for local hard drives.

•Centralized storage management and administration of client workstations.

•Disaster recovery.

•More control and efficiency for software distribution.

•Increased host reliability since operating system boots from highly available storage devices.

•Improved security.

128 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Brocade BIOS support for boot over SAN

The Brocade adapter boot BIOS provides boot support for the Brocade adapters in x86 and x64

host platforms. The BIOS can discover up to 256 storage targets, such as RAID units, and the

logical unit numbers (LUNs) on those units when the LUNs are bound to adapter ports.

When adapter BIOS is enabled, the boot code loads from adapter option ROM into system random

access memory (RAM) and integrates with the host system (server) BIOS during system boot to

facilitate booting from LUNs, which are also referred to as “virtual drives” and “boot devices.” LUNs

targeted as boot devices must contain the boot image for the host’s operating system and adapter

driver. The process for booting from these locations is referred to as “booting over SAN.” Boot over

SAN can be supported on a maximum of 16 ports (for example, 8 dual-port adapters). For more

information and configuration procedures for booting over SAN, refer to “Configuring boot over

SAN” on page 131.

NOTE

You can enable or disable BIOS for boot over SAN, set port speed (HBAs and Fabric Adapter port

configured in HBA mode only), and display adapter BIOS settings using BCU commands. By default,

BIOS is enabled on all adapter ports.

The Brocade BIOS Configuration Utility (embedded with the boot code), BCU commands, and the

HCM allow you to perform the following tasks:

•Enable or disable BIOS.

When enabled, the system BIOS can execute the Brocade BIOS code to boot over SAN.

•Set port speed (HBAs and Fabric Adapter ports configured in HBA mode only):

•Review adapter properties, such as the following:

-Port speed

-PWWN

-NWWN

-BIOS version

•Select a boot device from discovered targets.

•Enable one of the following boot LUN options.

NOTE

To boot from direct-attached Fibre Channel targets, you must use the First LUN or Flash Values

options.

-Fabric Discovered. When enabled, boot information, such as the location of the boot LUN,

is provided by the fabric (refer to “Fabric-based boot LUN discovery” on page 163 for more

information).

Brocade Adapters Installation and Reference Manual 129

53-1002144-01

Boot over SAN 4

NOTE

Fabric-based boot LUN discovery (Fabric Discovered) is not supported for booting from

direct-attached Fibre Channel targets.

-First LUN. The host boots from the first LUN visible to the adapter that is discovered in the

fabric.

-Flash Values. Boot LUN information will be obtained from flash memory. Note that values

are saved to flash when you configure and save them through the BIOS Configuration

Utility and BCU.

NOTE

“Brocade BIOS configuration utility” and “Brocade BIOS configuration menu” are used

interchangeably in this manual.

For general information and configuration procedures for booting over SAN, refer to “Configuring

boot over SAN” on page 131.

Brocade UEFI support for boot over SAN

Unified Extensible Firmware Interface (UEFI) boot code for Brocade adapters allows boot support

on UEFI-based platforms. The UEFI boot code can discover storage targets, such as RAID units and

logical unit numbers (LUNs) when the LUNs are bound to adapter ports. The UEFI boot code loads

from Brocade adapter option ROM into system memory and integrates with the host system

(server) UEFI during system boot to facilitate booting from target LUNs, which are also referred to

as “virtual drives” and “boot devices.” LUNs targeted as boot devices must contain the boot image

for the host, which consists of the adapter driver, host operating system, and other files that allow

the host to boot from the LUN. The process for booting from a boot LUN is referred to as “booting

over SAN.” For more information and configuration procedures for booting over SAN, refer to

“Configuring boot over SAN” on page 131.

After the Brocade UEFI boot code integrates with the system UEFI during system boot, use

configuration options on your system to perform the following tasks. Configuration values are

stored in adapter memory.

•Enable or disable the adapter port.

When enabled, available Fibre Channel devices attach as UEFI devices and obtain UEFI device

names. Once the Fibre Channel devices have UEFI device names, you can select them using

the host’s Boot Configuration menu as boot devices.

•Set the port speed (HBAs only and Fabric Adapter ports configured in HBA mode).

For general information and configuration procedures for booting over SAN, refer to “Configuring

boot over SAN” on page 131.

NOTE

UEFI is not supported on the Brocade 804 adapter.

Legacy BIOS parameters

The following parameters configured in legacy BIOS and saved on the adapter when using the

Brocade BIOS Configuration Utility, CLI, or HCM, are only applicable when configured in legacy BIOS

mode on a UEFI-capable or non-UEFI capable system.

130 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

•Fabric Discovered (also known as Fabric Based Boot LUN Discovery)

•First LUN

•Flash Values

The following parameters, if saved on the adapter during legacy BIOS configuration, will apply if

UEFI is enabled on the system:

•Port speed (HBAs and Fabric Adapter port configured in HBA mode only)

•Enable or disable BIOS

If legacy BIOS is enabled on the system, these parameters will apply. Refer to “Brocade BIOS

support for boot over SAN” on page 128).

Fabric Based Boot LUN Discovery

Fabric Based Boot LUN Discovery (fabric discovered) is only applicable when configured in legacy

BIOS mode on a UEFI-capable or non-UEFI capable system.

NOTE

This feature is not supported for booting from direct-attached Fibre Channel targets.

Host system requirements for boot over SAN

Consider these requirements for your host system when configuring boot over SAN:

•You may need to disconnect internal IDE hard drives to disable them in the system BIOS and

allow the adapter boot BIOS to boot from the remote boot device. Some systems may allow

these drives to be enabled in the system BIOS if they correctly support the bootstrap protocol.

•Typically, the boot order must be CD-ROM, diskette, then Fibre Channel drive. After the

operating system installs, you can change this order if desired.

•Boot over SAN is not supported on Windows 2003 systems for CNA models and for Fabric

Adapter ports configured in CNA or NIC modes.

Due to the variety of configurations and variables in a SAN installations, your specific environment

must determine any additional requirements to guide installation and configuration for best

results.

Storage system requirements for boot over SAN

Consider these requirements for your storage system for booting over SAN:

•The SAN must be properly installed so that the location on the SAN containing the boot image

is visible to the host. Verify links between the adapter and storage are working properly before

attempting a boot over SAN.

•The boot LUN must contain the appropriate operating system for the host and the adapter

driver. For information on minimum operating system support for drivers, refer to “Boot

installation packages” on page 49 and “Operating system support” on page 40. Refer to

“Operating system and driver installation on boot LUNs” on page 148 for installation details.

Brocade Adapters Installation and Reference Manual 131

53-1002144-01

Boot over SAN 4

NOTE

Some storage devices need the appropriate host type associated with the logical drive

configured for the correct operating system. This is necessary so that the storage device can

send the correct format of inquiry data to the host. Refer to your storage system

documentation for specific requirements.

•Configure the storage system so that the adapter port has exclusive access to the LUN.

Accomplish this by binding an adapter port PWWN to a LUN. You can easily find an adapter port

PWWN using the Brocade BIOS Configuration Utility (refer to “Configuring BIOS using the

Brocade configuration utility” on page 136). Exclusive access to the LUN can also be assured

by using a LUN-management feature, such as LUN masking, zoning, or a combination of these.

NOTE

You should use LUN masking to avoid boot failures. To configure LUN masking using the

Brocade LUN Masking feature, refer to the Brocade Administrator’s Guide.

•Only one path to the boot LUN must be visible to the operating system during the host’s boot

process. If the storage device has multiple controller ports, only one port can be enabled or

connected to the SAN during the operating system boot process.

•Create a specific zone containing the adapter port world-wide name (PWWN) and the target

PWWN to keep RCSN interruptions from other hosts to a minimum.

•If trunking is enabled, use the PWWN of Adapter Port-0 when configuring Fabric Zones and

LUN Masking for storage.

•For Microsoft Windows and Linux environments, the SAN must be connected to the host

system in a switched fabric or point-to-point topology. Fibre Channel Arbitrated Loop (FC-AL)

connections are not supported.

Disabling N_Port trunking

The Fibre Channel N_Port Trunking feature works in conjunction with the trunking feature on

Brocade switches, whereby the Fabric Operating System (FOS) provides a mechanism to trunk

different switch ports of the same port group into one. Disabling the N_Port trunking feature on the

adapter when using boot over SAN requires specific procedures that are included in the Brocade

Adapters Administrator’s Guide. Refer to that guide for details.

Configuring boot over SAN

You must configure boot over SAN on the adapter, as well as the storage device. Use this section to

guide you through other sections in this chapter that contain complete procedures for configuring

the adapter to boot from a SAN device.

Instructions are provided in this section for configuring boot over SAN on BIOS-based systems using

the Brocade BIOS Configuration Utility, BCU commands, and HCM. You can also configure adapters

using the Legacy BIOS mode (if the system supports Legacy mode) or by using another non-UEFI

mode system.

Instructions are provided in this section for configuring boot over SAN on UEFI-based systems that

support EFI shell commands. Configuring Brocade adapters in UEFI mode may not be supported on

some host systems. However, since Brocade adapters ship with all ports enabled and

auto-negotiated speed enabled by default, adapters should work in most systems.

132 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Overview

Figure 17 on page 133 provides a flow chart for the “Procedures” on page 134 and information

elsewhere in this chapter to configure your adapter, host system, and remote boot device for

booting over SAN.

Brocade Adapters Installation and Reference Manual 133

53-1002144-01

Boot over SAN 4

FIGURE 17 Configuring boot over SAN

Verify latest BIOS version on installed adapter.

Verify latest adapter driver installed in

host system.

Step 2-3

Install adapter hardware in host system.

Install adapter software in host system.

Step 1

Configure host system to boot from adapter.

Step 5

Bind adapter PWWN to available LUN

for boot over SAN.

Step 6-8

Configure LUN for booting from host system.

Step 12

Optional. Install full driver package on boot LUN.

Step 14

Boot host system from storage boot device.

Step 15

Install adapter drivers, host operating system,

and necessary files on boot LUN.

Step 13

Create target zone in fabric containing

adapter port PWWN and LUN storage port.

Step 9

Install latest boot code and

adapter driver if needed.

Step 4

Are you installing

adapter in UEFI-based

host system?

Configure BIOS for booting over SAN.

Step 10

Configure UEFI for booting over SAN.

Step 11

No Ye s

Note: Step numbers reference

procedures on the following page.

134 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Procedures

The following procedures are illustrated in the flow chart in Figure 17 on page 133. You may be

referenced to more detailed sections of this chapter to complete some of these steps.

1. Install the adapter and software into the host system using instructions in Chapter 2,

“Hardware Installation” and Chapter 3, “Software Installation”.

2. Verify that the adapter contains the latest BIOS version. You can use HCM or BCU commands.

For HCM, perform the following steps.

a. Select an adapter in the device tree.

b. Click the Properties tab in the right pane to display the adapter Properties pane.

For BCU, enter the following commands.

a. Enter the following command to list the Brocade adapters installed in the system and their

adapter IDs.

bcu adapter --list

b. Enter the following command to display information about an adapter with a specific

adapter ID. The installed BIOS version displays in the Flash Information section of the

display.

bcu adapter --query <adapter_id>

3. Verify that the latest adapter driver is installed on your host system using information under

“Confirming driver package installation” on page 103.

For information on minimum operating system support for drivers, refer to “Software

installation and driver packages” on page 43 and “Operating system support” on page 40.

4. Install the latest adapter boot code and driver using the following steps.

a. Download the latest boot code and driver package from the Brocade adapters website

using the following steps.

1. Go to the adapters website at www.brocade.com/adapters.

2. Navigate to the adapters Downloads page.

3. Select your operating system from the Downloads list to display appropriate download

files.

4. Download the boot code image and driver package from the Downloads page.

b. Upgrade your adapter and boot code if necessary using the following steps.

1. Driver package. Refer to “Using software installation scripts and system commands”

on page 89.

2. Boot code. Refer to “Boot code updates” on page 118.

5. Use your host system’s boot menu to enable the system to boot from the CD/DVD, diskette,

and then the appropriate adapter. If multiple adapters are installed on your system, be sure to

configure the system to boot from the appropriate adapter first in the boot order. Booting from

the CD/DVD and diskette first allows you to install the host operating system and adapter

driver on the boot LUN, but you may change this after installation. Depending on your host

system, you may need to enable booting from the adapter in your system boot menu, or you

may need to disable the host’s hard drive to boot from the adapter.

Brocade Adapters Installation and Reference Manual 135

53-1002144-01

Boot over SAN 4

NOTE

If you need to disable the system’s hard drive to allow booting from the adapter and wish to

utilize both the boot from SAN feature and your system’s hard drive, refer to your system

documentation. Procedures for this configuration are beyond the scope of this publication.

6. Verify that the appropriate storage device is connected to the fabric and functioning. This

device must have at least one LUN available that is appropriate for booting your host’s

operating system.

7. Determine which adapter port you want to use for booting from SAN and note its PWWN.

To locate the PWWN for an installed adapter port, refer to the discussion on PWWN on

page xxii. To find the PWWN for the port using the Brocade BIOS Configuration Utility, refer to

“Configuring BIOS using the Brocade configuration utility” on page 136.

8. Configure the storage system so that the adapter port has exclusive access to the LUN.

Consider using the following methods:

•Using an appropriate storage management or configuration utility, bind the adapter port’s

PWWN to the selected LUN.

•Mask the boot LUN for exclusive access by the adapter port and avoid boot failures using

the BCU fcpim –lunmaskadd command and the LUN Masking tab on the HCM Basic Port

Configuration dialog box. Refer to the Brocade Administrator’s Guide for more information

on configuring the LUN Masking feature.

9. Create a new single-initiator target zone in the SAN fabric where the adapter and storage

device are attached. The zone should contain only the PWWN of the storage system port where

the boot LUN is located and the PWWN of the adapter port. Refer to the Brocade Fabric OS

Administrator’s Guide for zoning procedures.

10. For BIOS systems, use one of the following sections to enable or disable BIOS to boot over SAN,

set adapter port speed (HBAs and Fabric Adapter ports configured in HBA mode only), display

BIOS configuration parameters, select boot LUNs, and enable “Fabric Discovered.”

•“Configuring BIOS using the Brocade configuration utility” on page 136.

•“Configuring BIOS using HCM or BCU commands” on page 142.

11. For UEFI systems, enable the adapter and boot devices for booting over SAN using instructions

under “Configuring UEFI” on page 146.

12. Configure the LUN for booting your host system. Refer to procedures required by your host

platform and operating system.

13. Install boot image on the boot LUN. The boot image consists of the adapter driver, host

operating system, and other necessary files to allow the host to boot from the boot device.

Refer to “Operating system and driver installation on boot LUNs” on page 148.

For information on minimum operating system support for drivers, refer to “Boot installation

packages” on page 49 and “Operating system support” on page 40.

14. Install full driver package (drivers, utilities, HCM agent) to boot LUN. Refer to “Installing the full

driver package on boot LUNs” on page 162.

15. Boot the host from the SAN storage boot device using procedures required by your host

system. As the system boots, information about successful Brocade BIOS installation should

display. In addition, information should display about the Brocade adapter and boot LUN in the

systems boot device menu.

136 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Configuring BIOS using the Brocade configuration utility

NOTE

“Brocade BIOS configuration utility” and “Brocade BIOS configuration menu” are used

interchangeably in this manual.

The Brocade BIOS Configuration Utility allows you to perform the following operations on selected

adapters:

•Enable or disable BIOS to support boot over SAN.

-You must enable BIOS to support boot over SAN for an adapter port. If disabled, the host

system cannot boot from Fibre Channel disk drives.

-The default setting for the adapter boot BIOS is BIOS is enabled with Fabric Discovered on

all adapter ports.

•Enable one of the following Boot Options:

NOTE

For booting from direct-attached Fibre Channel targets, select the Flash Values or First LUN

options.

-Fabric Discovered

Host boots from LUN information provided by the fabric.

NOTE

Fabric-based boot LUN discovery (Fabric Discovered) is not supported for booting from

direct-attached targets.

-Flash Values

Host boots from LUN information stored in flash memory.

-First LUN

Host boots from the first visible LUN.

•Set port speed for the adapter (HBAs and Fabric Adapter ports configured in HBA mode only).

•Select boot LUNs from discovered targets.

•Review adapter properties, such as the following:

-Port speed

-PWWN

-NWWN

-BIOS version

To configure BIOS parameters using the Brocade BIOS Configuration Utility, use the following steps.

1. Power on the host system.

2. Watch the screen as the system boots. When “Brocade BIOS configuration utility” displays,

press Alt+B or Ctrl+B.

The Brocade BIOS Configuration Menu displays a list of installed adapter ports, similar to the

following.

Brocade Adapters Installation and Reference Manual 137

53-1002144-01

Boot over SAN 4

Under the Ad No column, 1/0 and 1/1 are the first port and second port respectively on the

first installed adapter while 2/0 and 2/1 are the first and second port on the second installed

adapter.

A maximum of 8 ports can display on a screen, and a maximum of 16 ports are supported by

the BIOS Configuration Utility. Select Page Up to go to a previous screen or Page Down to go to

the next screen.

NOTE

To bypass functions and stop loading BIOS, you must to press X for each port. Press X within 5

seconds to bypass execution of functions displayed on screens. If you press X after 5 seconds,

the next function (instead of current function) will be bypassed.

3. Select a port that you want to configure.

A screen similar to the following displays. (In the following example, port 0 on the Brocade

1020 CNA was selected.)

138 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

4. Select one of the following:

•Adapter Settings. Use the Adapter Settings screen to enable BIOS, adapter port speed

(HBAs and Fabric Adapter ports configured in HBA mode only), and discovery of boot LUN

information from the fabric. You can determine adapter N and PWWN. Proceed to step 5.

•Boot Device Settings. Use the Device Settings screen to select the boot target and LUN for

booting the host system. Proceed to step 7.

5. Select Adapter Settings and press Enter to begin adapter configuration.

A screen similar to the following displays showing the port’s current BIOS version, NWWN,

PWPN, and MAC (CNAs and Fabric Adapter ports configured in CNA mode only). Table 11 on

page 138 explains options available for BIOS, Port Speed, and Boot LUN settings.

TABLE 11 Brocade BIOS Configuration Utility field descriptions

Field Description

BIOS The value of BIOS must be Enable for the selected adapter port to

support boot over SAN. If this setting is set to Disable, the system will

not boot from the Fibre Channel disk drives that are connected to the

selected adapter port.

NOTE: The default setting for all adapter ports is enabled.

BIOS Version Displays the Brocade BIOS boot code version installed on the card.

Brocade Adapters Installation and Reference Manual 139

53-1002144-01

Boot over SAN 4

6. Change any parameters by following the instructions at the bottom of the BIOS Configuration

Utility screen. For example, use the following keys to select and change information:

•Up and Down keys - Scroll to a different field.

•Enter - Select a field and configure values.

•Left and Right arrow keys - Change a value.

•Alt - S - Save configuration values to adapter flash memory.

•Alt - Q - Exit the utility.

•Esc - Go back a screen.

•Page Up or Page Down - Go to preceding or next screen.

NOTE

To restore factory default settings, press R.

7. To configure boot devices, select Boot Device Settings from the initial menu screen for the

adapter port (step 4) and press Enter to designate a discovered LUN as a boot device.

A list of up to four boot devices display, showing the PWWN of the storage port and the LUN

number designated as a boot LUN. The first device listed is the primary boot device. The host

first tries to boot from the primary device, then the succeeding devices in the list.

Boot LUN •Fabric Discovered. When enabled, LUN information, such as the

location of the boot LUN, is provided by the fabric (refer to

“Fabric-based boot LUN discovery” on page 163).

•Flash Values. Boot LUN information will be obtained from flash

memory. Note that values are saved to flash when you configure

and save them through the BIOS Configuration Utility and BCU.

•First LUN. The host boots from the first LUN visible to the adapter

that is discovered in the fabric.

NOTE: To boot from direct-attached Fibre Channel targets, you must

use the First LUN or Flash Values options.

NOTE: Fabric-based boot LUN discovery (Fabric Discovered) is not

supported for booting from direct-attached targets.

NWWN Displays the port’s Node World-Wide Name.

PWWN Displays the port’s unique Port World-Wide Name.

MAC Displays the port’s Media Access Control (MAC) address for CNAs and

Fabric Adapter ports configured in CNA or NIC mode.

Port Speed Sets the speed for the adapter port.

NOTE: Auto allows the adapter port to automatically negotiate link

speed with the connected port. Auto is the only speed option for

the 10 Gbps CNAs and Fabric Adapter ports configured in CNA

or NIC mode.

TABLE 11 Brocade BIOS Configuration Utility field descriptions (continued)

140 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

8. Use the Up and Down arrow keys to select a boot device, then use one of the following options

to configure boot device settings:

•Press C to clear a selected boot device from the list.

•Press M to manually edit boot device information, then enter the PWWN and LUN values

for the boot device. Press M to exit.

•Select a device and press Enter. This displays additional screens that allow you to select

discovered LUNs as boot devices.

If you select a device under Boot Device Settings and press Enter, a screen similar to the

following displays listing all discovered boot targets.

9. Select a target on which you want to designate a boot LUN and press Enter.

A screen similar to the following displays listing device information and LUNs visible to the

adapter.

Brocade Adapters Installation and Reference Manual 141

53-1002144-01

Boot over SAN 4

10. Select the LUN on the target device you that want to designate as the boot LUN for the host.

This must be the same LUN that you bound to the adapter port using the storage system’s

management or configuration utility (refer to step 8 under “Procedures” on page 134).

NOTE

You only need to select the bootable LUN once. After the first boot, the same LUN will be used

until changed through the BIOS Configuration Utility.

11. Press Enter. The selected device will be added to the list of boot devices for the adapter.

12. Save or exit the configuration utility.

•To save the configuration, press the Alt and S keys.

•To exit without saving press the Alt and Q keys.

142 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Configuring BIOS using HCM or BCU commands

You can enable or disable BIOS for booting over the SAN, set adapter port speed (HBAs and Fabric

Adapter port configured in HBA mode only), display BIOS configuration parameters, select boot

LUNs, and enable automatic discovery of the boot LUN from the fabric using HCM dialog box

options and BCU commands,

NOTE

You can only designate bootable devices (LUNs) using the Boot Device Settings feature of the

Brocade BIOS Configuration Utility,

Configuring BIOS using HCM

To configure BIOS using HCM, perform the following steps.

1. Select an adapter in the device tree.

2. Select Configure > Basic Port Configuration to display the Basic Port Configuration dialog box.

3. Click the Boot-over-SAN tab to display the Boot over SAN dialog box.

4. Perform any or all of the following actions as appropriate for your needs:

•Enable or disable BIOS.

Click the BIOS Enable check box to enable boot over SAN. You must enable BIOS to

support boot over SAN for an adapter port. If disabled, the host system cannot boot from

Fibre Channel disk drives. The default setting for the adapter boot BIOS is enabled.

NOTE

For mezzanine adapters only, if BIOS was enabled through a blade system management

application, the Pre-boot BIOS Enable option will be selected and cannot be changed.The

BIOS Enable option will also be disabled.

•Set port speed for adapter ports.

NOTE

Auto Negotiate allows the port to automatically negotiate link speed with the connected

port. This is the only speed option for the 10 Gbps CNA and for Fabric Adapter ports

configured in CNA or NIC mode.

NOTE

For mezzanine adapters only, if speed was set through another application, such as the

blade system management application, a Pre-boot BIOS Speed will be indicated and

cannot be changed.

•Enable one of the following boot options:

NOTE

For booting from direct-attached Fibre Channel targets, select the First Visible LUN or User

Configurable LUN options.

•Fabric Discovered - When enabled, the boot LUN identification is provided by the fabric

(refer to “Fabric-based boot LUN discovery” on page 163).

Brocade Adapters Installation and Reference Manual 143

53-1002144-01

Boot over SAN 4

NOTE

Fabric-based boot LUN discovery (Fabric Discovered) is not supported for booting from

direct-attached Fibre Channel targets.

•First Visible LUN - The host boots from the first LUN visible to the adapter that is

discovered in the fabric.

•User Configured LUNs - Allows the user to select and prioritize the remote target and

LUN for booting over SAN.

The User Configured LUNs table displays LUNs visible to the adapter. If you select this

option, up to four boot user-configured LUNs can be configured as boot devices. If you

select User Configured LUNs, the system will attempt to boot the first LUN in the table,

then each succeeding LUN in order.

NOTE

For mezzanine adapters only, if LUNs have been configured through another application,

such as a blade system management application, these are considered “pre-boot”

configured LUNs. In pre-boot configurations, up to eight total LUNs can be configured as

boot devices for HBAs and Fabric Adapter ports configured in HBA mode. Up to two LUNs

can be configured for CNAs and Fabric Adapter ports configured in CNA mode.

Click the Boot Device PWWN and LUN fields to edit WWNs. For the LUN to be accessible to

the port it must be bound to the LUN using the appropriate management or configuration

utility for the storage system. In addition, a zone set must be created on the attached

switch containing PWWN of the storage system port where the boot LUN is located and the

PWWN of the adapter port.

Click the up and down arrows to the right of the table to reorder boot devices in the table.

Click the delete symbol (X) to remove a device from the table.

5. Click OK to exit and save values.

All configuration values are stored to adapter flash memory.

For details in using HCM options to configure BIOS and boot over SAN options, refer to the

instructions for enabling boot over SAN using HCM in the Host Configuration chapter of the

Brocade Adapters Administrator’s Guide.

Configuring BIOS using BCU commands

Use the BCU commands to perform the following tasks:

•Enable BIOS, set port speed (HBAs and Fabric Adapter ports configured in HBA mode only),

and configure boot LUN information.

You must enable BIOS to support boot over SAN for an adapter port. If disabled, the host

system cannot boot from Fibre Channel disk drives. The default setting for the adapter boot

BIOS is enabled. It is recommended to enable BIOS on only one adapter port per host for

booting over SAN.

Use the following BCU command to enable BIOS, set port speed (if required), and configure

target PWWN and LUN values.

bcu bios --enable <port_id> [-s <speed>][-o <auto|flash|firstlun>[-p pos][-b

pwwn,lun*]

where:

144 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

port_id Specifies the ID of the port for which you want to set the port’s boot from SAN

attributes. This could be the adapter_id/port_id, port PWWN, port name, or

port hardware path.

-s <speed> Specifies the speed for the port. Default is autonegotiate. Note that

autonegotiate is the only speed option for 10 Gbps CNAs and Fabric Adapter

ports configured in CNA or NIC mode.

- o: Begins options for obtaining boot LUN information (auto, flash, firstlun).

auto Enables automatic identification of the boot LUN from fabric. Refer to

“Fabric-based boot LUN discovery” on page 163 for more information. This

value is not supported for booting from direct-attached targets.

flash Boot LUN information is obtained from flash memory. Note that values are

saved to flash when you configure them and save them through the BIOS

Configuration Utility, HCM, and BCU.

firstlun The host boots from the first LUN visible to the adapter that is discovered in

the fabric.

-p pos Specifies the start position in the flash array of boot LUNs. The range is 0-3.

The default value of 0 means the existing PWWN, LUN information in flash

would be erased.

-b pwwn,lun* The host boots from the LUN information defined by the target PWWN and

LUN value (lun*).

Specify PWWN as a colon-separated value and the LUN ID as a hexadecimal

value (without 0x prefix).

The LUN must be the same LUN that you bound to the adapter port using the

storage system’s management or configuration utility (refer to step 8 under

“Procedures” on page 134).

•Disable BIOS and boot over SAN support for an adapter port using the following command:

bcu bios --disable <port_id>

•Display BIOS settings, current port speed, and boot LUN information for the selected port using

the following command:

bcu bios --query <port_id>

where:

port_id Specifies the ID of the port for which you want to set the port’s interrupt

attributes.

All configuration values are stored to adapter flash memory.

Brocade Adapters Installation and Reference Manual 145

53-1002144-01

Boot over SAN 4

NOTE

For details on using BCU commands, refer to instructions for enabling boot over SAN using BCU

commands in the Host Configuration chapter of the Brocade Adapters Administrator’s Guide.

146 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Configuring UEFI

Depending on your UEFI-based host system, different tools may be available to perform the

following tasks to configure the adapter values that are stored in adapter flash memory.

NOTE

UEFI is not supported on the Brocade 804 adapter.

•Enable or disable adapter ports for booting over SAN.

When enabled, available Fibre Channel devices attach as UEFI devices and obtain UEFI device

names. Once the Fibre Channel devices have UEFI device names, you can select them in the

systems Boot Configuration menu as boot devices.

•Set the port speed (HBAs and Fabric Adapter ports configured in HBA mode only).

NOTE

Autonegotiate is the only speed option for the 10 Gbps CNAs and Fabric Adapter ports

configured in CNA or NIC mode.

•Select LUNs for booting over SAN.

Depending on your system, different tools may be available to obtain adapter and controller handle

numbers that identify the appropriate adapter for configuration, enable adapter port(s), and

change port speeds. Although the following provides some examples using EFI shell commands,

refer to your system documentation and help system for specific details.

•On systems with EFI shell commands, you can use such commands as drvcfg, dh, and drivers

to configure adapter values (an example procedure for these systems follows).

•On some systems, you can access drvcfg and other commands from a menu system to

configure adapter values. Refer to instructions or online help provided for your system.

•On other systems, you will need to use BCU commands and the system’s BIOS menus to

configure adapter values. Refer to instructions or online help provided for your system. To use

HCM options or BCU commands, Refer to “Configuring BIOS using HCM or BCU commands” on

page 142.

The following procedures provide an example for configuring adapter values on systems that

support EFI shell commands.

1. Power on the host system.

2. When the EFI Boot Manager menu displays, select EFI Shell.

3. Enter the following EFI shell command to display the device or driver handle number for each

driver loaded on the system.

drivers -b

Output displays one screen at a time and includes the two-digit driver handle number, version,

and driver name. Look for entries labeled “Brocade Fibre Channel Adapter.” In the following

example, the Brocade adapter has a driver handle of 25.

VERSION

G#D

DRIVER NAME IMAGE NAME

25 0000000A D X - 2 - Brocade Fibre Channel Adapter Bus D PciROM:03:00:00:003

-------------------------------------------------------------------------------------------------

Brocade Adapters Installation and Reference Manual 147

53-1002144-01

Boot over SAN 4

4. Enter the following command to display all drivers and controllers that support the driver

configuration protocol.

drvcfg -c

Once the driver initializes, look for entries for the Brocade adapter driver handle that you found

in the previous step. In the following example, two controller handles (27 and 28) display for

driver handle 25. Each controller represents a port on the adapter.

Configurable Components

Drv[1F] Ctrl[20] Child[67] Lang[eng]

Drv[25] Ctrl[27] Lang[eng]

Drv[25] Ctrl[28] Lang[eng]

5. Configure an adapter port using the drvcfg -s command in the following format.

drvcfg -s [driver handle] [controller handle]

Following is an example of how to use this command with the driver and controller handles

from the previous steps.

a. To configure one of the adapter ports, enter the following:

drvcfg -s 25 27

NOTE

The -s option for drvcfg provides prompts for setting adapter options. You can use the -v

option (drvcfg -v 25 27) to check that options currently set on the adapter are valid.

b. When you are prompted to enable the adapter port, press the Y or N key to enable or

disable the port.

c. When prompted, enter a port speed (HBAs and Fabric Adapter ports configured in HBA

mode only).

d. To terminate and not save values that you have selected, press Esc, and go to the next

step.

Following is example output from the drvcfg command using driver handle 25 and controller

handle 27. Note that for a CNA and Fabric Adapter ports configured in CNA mode, an option to

set the port speed will not display as it does for an HBA or Fabric Adapter port configured in

HBA mode.

Set Configuration Options

Drv[25] Ctrl[27] Lang[eng]Bfa Fibre Channel Driver Configuration

======================================

Port nwwn 200000051E301492

Port pwwn 100000051E301492

Enable Brocade Fibre Channel adapter/port 1/0 (Y/N)? [Y] -->Y

Set Brocade Fibre Channel Adapter Port Speed 1/0 (0,2,4,8)? [Auto] -->Auto

Drv[25] Ctrl[27] Lang[eng] - Options set. Action Required is None

NOTE

Entering the drvcfg command with an -f option (drvcfg -f) sets adapter options to default

values. For example, enter drvcfg -f 25 27. Entering the command with the -v option (drvcfg -v)

checks whether options configured for the adapter are valid. For example, enter drvcfg -v 29

3F.

148 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

NOTE

You could configure the other adapter port using the drvcfg -s command by keeping the driver

handle the same and using the other controller handle (drvcfg -s 25 28).

6. Execute a reset EFI shell command to reinitialize the system.

When the system restarts, all available Fibre Channel devices display in map output as the EFI

Shell initializes. SAN drives display with “Fibre” as part of the device name.

7. Find the LUN that you have targeted for boot over SAN in the system’s map output.

Note that you can also enter the following EFI shell command to list all storage targets and

LUNs visible to the adapter port. SAN drives display with “Fibre” as part of the device name.

dh -d [controller handle]

8. Refer to procedures for your system’s Boot Configuration menu to verify that your host is

configured to automatically boot from the target remote LUN.

9. Refer to instructions under “Operating system and driver installation on boot LUNs” on

page 148 to install the host’s operating system and adapter driver to the LUN

Operating system and driver installation on boot LUNs

Use the procedures in this section to install the host operating system and adapter drivers on an

unformatted disk that you that you configured as a bootable device when setting up the adapter

BIOS or UEFI on the host system. Instructions are provided for the following:

•“Installing Windows Server 2003 and the driver”

•“Installing Windows Server 2008 and the driver”

•“Installing Linux RHEL 4.x or 5.x and the driver”

•“Installing Linux (SLES 10 and later) and the driver”

•“Installing Solaris and the driver”

•“Installing VMware and the driver”

•“Installation on systems supporting UEFI”

For information on operating system support for drivers, refer to “Boot installation packages” on

page 49 and “Operating system support” on page 40.

Before installing the operating system and adapter drivers, be sure you have bound the PWWN of

the appropriate adapter port to the designated boot LUN and have configured the BIOS or UEFI on

your host system for booting over SAN. Refer to “Configuring boot over SAN” on page 131,

“Configuring BIOS using the Brocade configuration utility” on page 136, and “Configuring UEFI” on

page 146 for instructions.

NOTE

The following procedures load the operating system, adapter drivers, and utilities to the designated

boot LUN to allow adapter operation and booting your host system from the LUN. However, the HCM

Agent and full range of Brocade Command Line Utilities, such as bfa_supportsave, are not installed.

To install the complete driver package with HCM Agent and full-range of utilities, refer to “Installing

the full driver package on boot LUNs” on page 162 after completing the following steps.

Brocade Adapters Installation and Reference Manual 149

53-1002144-01

Boot over SAN 4

Installing Windows Server 2003 and the driver

If the LUN you have targeted for booting the host system already has an operating system installed,

be sure to use options for reformatting the LUN during Windows Server 2003 installation. Refer to

your operating system documentation for details.

1. Driver update disk files are provided for x86 and x64 systems. Refer to “Boot installation

packages” on page 49 for a list of driver update disk files and the operating systems that

support these files. Also refer to “Operating system support” on page 40 for information on

operating system support for adapter drivers.

NOTE

For booting over SAN, you will need the fc dud file, brocade_adapter_fc_<operating

system>_<platform>_dud_<version>.zip. Note that only HBAs and Fabric Adapter HBA ports

are supported for boot over SAN in Windows 2003. For network boot, you will need the

brocade_adapter_nw_<operating system>_<platform>_dud_<version>.zip

NOTE

For Microsoft Windows operating systems, the driver update disk does not verify prerequisite

checks as part of installation. Please review the operating system prerequisites and install the

necessary hotfixes after the operating system installation is complete.

2. Download the appropriate Windows 2003 adapter driver update disk (dud) .zip file for your

host platform from the Brocade adapters website at www.brocade.com/adapters using the

following steps:

a. On the adapters website, navigate to the drivers Downloads page.

b. On the downloads page, select your host’s operating system from the Download Individual

Software Installers, Drivers, or Documents list to access the appropriate downloads.

c. Download the dud from the “Driver Update Disks (DUDs)” area.

3. Unzip the file and copy to a formatted disk to create the adapter driver update disk.

4. Insert the Windows 2003 operating system installation media into the host system’s CD/DVD

drive and boot from the CD or DVD.

5. Respond to prompts that display as Windows installs. When prompted to press F6 to install a

third-party SCSI or RAID driver, press F6.

NOTE

If you miss the message to press F6, you will need to reboot from the operating system CD or

DVD.

The following messages display:

Setup could not determine the type of one or more mass storage devices

installed on your system, or you have chosen to manually specify an adapter.

Currently, Setup will load support for the following mass storage device(s):

S=Specify Additional Device ENTER=continue F3=Exit.

6. Select S to specify additional devices.

NOTE

You must load the Brocade adapter driver by selecting “S” and using the following steps so that

the system can access the boot LUN for Windows 2003 Server installation.

150 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

7. When a message displays to insert the disk labeled manufacturer-supplied hardware support

disk, insert the Brocade adapter driver update disk that you created in step 3 and press Enter.

A list of devices displays.

8. Select Brocade's adapter from the list and press Enter.

The following message displays:

Setup will load support for the following mass storage device(s): Brocade Fibre Channel

Adapter.

9. Press Enter.

10. Remove the driver update disk after the driver update files load.

11. Continue responding to on-screen instructions and refer to your system documentation as

necessary to format and complete installation on the target boot LUN.

After Windows installs on the remote LUN, the system should automatically reboot from the

LUN.

Messages should display on the host system as BIOS or UEFI loads successfully. System boot

setup screens should also display a hard drive entry containing the Brocade adapter, boot LUN

number, and target storage device.

Installing Windows Server 2008 and the driver

Use the following steps to install Windows Server 2008 and the adapter driver on an unformatted

disk that you configured as a bootable device when setting up the adapter BIOS or UEFI on the host

system.

If the LUN you have targeted for booting over SAN already has an operating system installed, be

sure to use options for reformatting the LUN during Windows Server 2008 installation. Refer to your

operating system documentation for details.

NOTE

For HBAs and Fabric Adapter ports configured in HBA mode, you will need the fc dud file,

brocade_adapter_fc_<operating system>_<platform>_dud_<version>.zip. For CNAs and Fabric

Adapter ports configured in CNA mode, you will need the fcoe dud file,

brocade_adapter_fcoe_w2k8_x86_dud_<version>.zip>.

NOTE

For Microsoft Windows operating systems, the driver update disk does not verify prerequisite checks

as part of installation. Please review the operating system prerequisites and install the necessary

hotfixes after the operating system installation is complete.

1. Driver update disk files are provided for x86 and x64 systems. Refer to “Boot installation

packages” on page 49 for a list of driver update disk files and the operating systems that

support these files. Also refer to “Operating system support” on page 40 for information on

operating system support for adapter drivers.

2. Download the appropriate Windows 2008 adapter driver update disk (dud) .zip file for your

host platform from the Brocade adapters website at www.brocade.com/adapters using the

following steps:

a. On the adapters website, navigate to the drivers Downloads page.

b. On the downloads page, select your host’s operating system from the Download Individual

Software Installers, Drivers, or Documents list to access the appropriate downloads.

Brocade Adapters Installation and Reference Manual 151

53-1002144-01

Boot over SAN 4

c. Download the dud from the “Driver Update Disks (DUDs)” area.

3. Unzip the file and copy to a CD, USB drive, or formatted floppy disk to create the adapter driver

update disk.

4. Insert the Windows 2008 operating system installation DVD into the system drive and boot

from the DVD.

5. Respond to prompts that display on the Windows installer screens. Be sure to select a

Standard (Full Installation) and accept the software license.

6. When the Which type of installation do you want? screen displays, select Custom (advanced).

7. When the Where do you want to Install Windows? screen displays, select the Load Driver

option at the bottom of the screen.

The Load Driver dialog box displays, prompting you to insert the installation media containing

the driver files.

ATTENTION

You must load the Brocade adapter driver at this stage so that the system can access the boot

LUN for Windows 2008 Server installation.

8. Insert the media containing the Brocade adapter driver update files that you created in step 3.

9. Select Browse on the Load Driver dialog box and select the adapter driver update disk.

10. Click OK.

NOTE

If “Hide drivers that are not compatible with hardware on this computer” is selected, only

drivers for installed adapter models will display on the Select the drive to be installed screen. If

not selected, drivers for all adapter models display.

11. Select the driver for the adapter that you are configuring for boot over SAN and click Next.

After the driver loads, remote LUNs display on the Where do you want to install Windows?

screen that are visible to the adapter port.

12. Replace the driver update disk with the Windows 2008 DVD.

13. Select the LUN that you have identified as the boot device for the adapter port and click Next.

NOTE

Selecting Drive options (advanced) provides other options for editing the destination disk, such

as formatting a partition (when the operating system already installed) and creating a new

partition.

14. Continue responding to on-screen instructions and refer to your system documentation as

necessary to format and complete installation on the target boot LUN.

After Windows installs on the remote LUN, the system should automatically reboot from the

LUN.

Messages should display on the host system as the Brocade BIOS or UEFI loads successfully.

System boot setup screens should also display a hard drive entry containing the Brocade

adapter, boot LUN number, and target storage device.

152 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

Installing Linux RHEL 4.x or 5.x and the driver

Use the following steps to install RHEL and the adapter driver on an unformatted disk that you

configured as a bootable device when setting up the adapter BIOS or UEFI on the host system.

If the LUN you have targeted for booting the host system already has an operating system installed,

be sure to use options for reformatting the LUN during Linux installation. Refer to your operating

system documentation for details.

NOTE

The following procedures load the operating system, adapter driver, and utilities to the designated

boot LUN to allow adapter operation and booting your host system from the LUN. However, the HCM

Agent and full range of Brocade Command Line Utilities, such as bfa_supportsave, are not installed.

To install the complete driver package with HCM Agent and full-range of utilities refer to “Installing

the full driver package on boot LUNs” on page 162 after completing the following steps.

1. Refer to “Boot installation packages” on page 49 for a list of driver update disk files and the

operating systems that support these files. Also refer to “Operating system support” on

page 40 for information on operating system support for adapter drivers.

NOTE

For RHEL 5 x86 and x86_64 systems, install the fc DUD files for CNAs and Fabric Adapter ports

configured in CNA mode and for HBAs and Fabric Adapter ports configured in HBA mode. The

fc dud file format is brocade_fc_adapter_<operating system>_<platform>_dud_<version>.iso.

2. Download the appropriate RHEL adapter driver update disk (dud) .iso file for your host platform

from the Brocade adapters website using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapters Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the dud from the “Driver Update Disks (DUDs)” area.

3. Create a driver update disk CD or USB drive from the ISO image.

4. Insert the Linux Red Hat product CD #1 into the host system’s CD drive and boot the system.

5. At the boot prompt enter one of the following commands and press Enter:

•For booting over SAN, use the following command.

linux dd

•For booting over SAN with multi path, use the following command.

linux dd mpath

NOTE

The mpath option installs the operating system and driver to a LUN connected to the server

through multiple paths and provides a unique and single name for the device. If the mpath

option were not used in a multi-path configuration, a separate device instance would display

for each path during installation. By using the option, only one instance displays for the device,

although multiple paths still exist.

Brocade Adapters Installation and Reference Manual 153

53-1002144-01

Boot over SAN 4

6. When the Driver Disk message box displays the “Do you have a driver disk” prompt, select Yes,

then press Enter.

ATTENTION

You must load the Brocade adapter driver at this stage so that the system can access the boot

LUN for Linux installation.

7. Fro m the Driver Disk Source window, select the driver source hdx (where x is the CD or USB

drive letter), then press Enter.

The Insert Driver Disk window displays.

8. Insert the driver update disk (dud) that you created in step 3 into the CD or DVD.

9. Select OK, then press Enter.

The driver loads automatically.

10. When the Disk Driver window displays prompting for more drivers to install, select No or Yes

depending on the installed adapter and operating system, then press Enter.

For RHEL 5 and later on x86 and x86_x64 platforms install the fc dud for an HBA, Fabric

Adapter port configured in HBA mode, CNA, or Fabric Adapter port configured in CNA mode.

The fc file format is brocade_fc__adapter_<operating

system>_<platform>_dud_<version>.iso.

11. Insert the Linux Red Hat product CD #1 in the CD drive (remove the adapter driver update CD

first if necessary), then press Enter.

12. Continue responding to on-screen instructions and refer to your system documentation as

necessary to format and complete installation on the target boot LUN.

Installing Linux (SLES 10 and later) and the driver

Use the following steps to install SLES 10 and later and the adapter driver on an unformatted Fibre

Channel disk configured as a bootable device.

•For HBAs installed on SLES 11 on UEFI-supported systems, refer to “UEFI mode install and

boot with HBAs” on page 160. For Fabric Adapter ports configured in HBA mode, refer to the

following procedures.

•For CNAs and Fabric Adapter ports configured in CNA mode on SLES 11 on UEFI-supported

systems, refer to “UEFI mode install and boot with CNAs and Fabric Adapter ports configured in

CNA mode” on page 161.

If the LUN you have targeted for booting over SAN already has an operating system installed, be

sure to use options for reformatting the LUN during Linux installation. Refer to your operating

system documentation for details.

NOTE

If you are installing SLES 11 for systems with HBAs and Fabric Adapter ports configured in HBA mode

only, the appropriate drivers are included with the SLES product CD, so you can ignore steps 1

through 3 in the following procedures. However, if the driver is not detected on the SLES product CD

during installation, you should download the latest driver update ISO file, create a driver update disk

CD or USB drive, and use this to install drivers as outlined in the following steps.

154 Brocade Adapters Installation and Reference Manual

53-1002144-01

Boot over SAN

1. Refer to “Boot installation packages” on page 49 for a list of these files and the operating

systems that support these files. Also refer to “Operating system support” on page 40 for

information on operating system support for adapter drivers.

2. Download the Brocade adapter driver update .iso file appropriate for your SLES system from

the Brocade adapters website using the following steps:

a. Go to the adapters website at www.brocade.com/adapters.

b. Navigate to the adapter Downloads page.

c. Select your operating system from the Downloads list to display appropriate download

files.

d. Download the file from the “Driver Update Disks (DUDs)” area.

3. Create a driver update disk CD or USB drive from the ISO image.

4. Insert the SLES product CD #1 into the host system drive and follow your system procedures to

boot from the CD.

The main installation screen eventually appears.

5. Perform the following steps depending on your host platform:

•For SLES 10 systems, press F5.

When the system prompts to select Yes, No, or File, select Yes and press Enter.

•For SLES 11 systems, press F6.

When the system prompts to select Yes, No, or File, select Yes and press Enter.

6. When the “Please choose the driver update medium” prompt displays, install the CD or USB

drive containing the driver update disk that you created in step 3.

NOTE

You must load the Brocade adapter driver at this stage so that the system can access the boot

LUN for Linux installation. If you are installing SLES 11 drivers for HBAs and Fabric Adapter

ports configured in HBA mode only, drivers are located on the SLES product CD. You do not

have to use the SLES driver update disk to install drivers unless the appropriate driver is not

detected on the product CD.

7. Select the drive where the driver update disk is loaded then press Enter.

The driver update loads to the system.

If the driver update was successful, a “Driver Update OK” message displays:

8. Press Enter.

9. If the system prompts you to update another driver, select BACK, then press Enter.

10. When the “Make sure that CD number 1” message displays, insert the SLES product CD #1

into the drive and select OK.

11. Continue responding to on-screen instructions and refer to your system documentation as

necessary to format and complete installation on the target boot LUN.

After SLES installs on the remote LUN, the system should automatically reboot from the LUN.

Brocade Adapters Installation and Reference Manual 155

53-1002144-01

Boot over SAN 4

Installing RHEL 6.x or Oracle Enterprise Linux (OEL) 6.x and the driver

Use the following steps to install RHEL 6.x, RHEL 6.x U1, OEL 6.x, or OEL 6.x U1 and the adapter

driver on an unformatted disk that you configured as a bootable device when setting up the

adapter BIOS or UEFI on the host system.

If the LUN you have targeted for booting the host system already has an operating system installed,

be sure to use options for reformatting the LUN during Linux installation. Refer to your operating

system documentation for details.

The following instructions apply to Brocade adapter models 415, 425, 815, 825, 1010, 1020,

1007, 1741, and 1860. If using another adapter, you can install RHEL drivers as usual (refer to

“Installing Linux RHEL 4.x or 5.x and the driver” on page 152). This installs the noarch version of

the adapter drivers.