HBA Install and Reference Manual

53-1000884-02 December 19, 2008
Brocade Fibre Channel HBA

Installation and Reference Manual
Supporting HBA Models 815, 825, 415, 425
Copyright 2008 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it. 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://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated

Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 1745 Technology Drive San Jose, CA 95110 Tel: 1-408-333-8000 Fax: 1-408-333-8101 Email: info@brocade.com Asia-Pacific Headquarters Brocade Communications Singapore Pte. Ltd. 30 Cecil Street #19-01 Prudential Tower Singapore 049712 Singapore Tel: +65-6538-4700 Fax: +65-6538-0302 Email: apac-info@brocade.com
European Headquarters Brocade Communications Switzerland Srl Centre Swissair Tour B - 4me tage 29, Route de l'Aroport Case Postale 105 CH-1215 Genve 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 Email: emea-info@brocade.com
Document History
Title
Brocade Fibre Channel HBA Installation and Reference Manual Brocade Fibre Channel HBA Installation and Reference Manual
Publication number
53-1000884--01 53-1000884--02
Summary of changes
New document Revised for release 1.1
Date
June 2008 December 2008
Contents
About this document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . viii HBA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Fabric OS and switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Host operating system support. . . . . . . . . . . . . . . . . . . . . . . . . . viii Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . x Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Other industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii bfa_supportsave feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii HBA serial number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Port World-Wide Port Name (PWWN). . . . . . . . . . . . . . . . . . . . . . . . . xiii Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1
HBA product overview

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HBA product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HBA features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 HBA management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 HBA software overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Software installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Boot code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Items shipped with your HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Hardware and software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . 7 SFP transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Host systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 PCI-express slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Storage systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Host operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02
iii
Software installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Boot installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Downloading software and publications . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2
Installation
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 HBA hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 What you need for installation . . . . . . . . . . . . . . . . . . . . . . . . . . 17 ESD Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Installing the HBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Connecting the HBA to the fabric . . . . . . . . . . . . . . . . . . . . . . . . 20 Removing and installing SFP transceivers . . . . . . . . . . . . . . . . . 20 HBA software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Using the Brocade HBA Software Installer . . . . . . . . . . . . . . . . . 23 Using HBA Software Installer commands. . . . . . . . . . . . . . . . . . 26 HBA software removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Important notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Using the Brocade HBA Software Uninstaller . . . . . . . . . . . . . . 29 Using HBA Software Uninstaller commands . . . . . . . . . . . . . . . 31 HBA software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Manual installation, removal, and upgrade of driver packages. . . . 34 Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Windows systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Linux systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Solaris systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 VMware systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Modifying HCM Agent operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Linux and VMware systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Solaris systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Windows systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Replacing an HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 3
Troubleshooting installation problems

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Verifying HBA installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
iv
Troubleshooting installation problems. . . . . . . . . . . . . . . . . . . . . . . . 48 Verifying installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Errors installing source-based Linux drivers . . . . . . . . . . . . . . . 48 Files needed for bfad.sys message appears when removing driver 48 Cannot roll back driver on all HBA instances using Device Manager 49 Installer program does not autorun from CD (Windows only) . . 49 Host operating system not installing on remote boot . . . . . . . . 49 HBA not recognized by BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 HBA not recognized by operating system . . . . . . . . . . . . . . . . . . 50 Host system freezes or crashes . . . . . . . . . . . . . . . . . . . . . . . . . 50 Storage devices not recognized by host system . . . . . . . . . . . . 51 Confirming driver package installation . . . . . . . . . . . . . . . . . . . . . . . 52 Host Connectivity Manager (HCM) . . . . . . . . . . . . . . . . . . . . . . . 52 Using Support Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Initiating Support Save through HCM . . . . . . . . . . . . . . . . . . . . . 55 Initiating Support Save through BCU commands . . . . . . . . . . . 55 Initiating Support Save through the internet browser . . . . . . . . 56 Initiating Support Save through a port crash event. . . . . . . . . . 56 Support Save differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 bfa_supportsave collection on a port crash event . . . . . . . . . . 56
Chapter 4
HBA boot code

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Brocade BIOS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Brocade UEFI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Updating boot code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Using HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Using BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 General host and storage system requirements . . . . . . . . . . . . 61 Configuring boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Configuring BIOS using the Brocade configuration utility . . . . . 63 Configuring BIOS using HCM and BCU . . . . . . . . . . . . . . . . . . . . 69 Configuring UEFI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Installing operating system and driver on boot LUNs . . . . . . . . 73 Fabric based boot LUN discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Configuring fabric-based boot LUN discovery . . . . . . . . . . . . . . 82 Booting systems without operating system or local drive . . . . . . . . 83 Creating a WinPE image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Chapter 5
Specifications
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Physical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 PCI express interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Fibre channel interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Fiber optic cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 LED operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Environmental and power requirements . . . . . . . . . . . . . . . . . . . . . . 91 Fibre Channel standards compliance . . . . . . . . . . . . . . . . . . . . . . . . 91 Regulatory compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FCC warning (US only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 MIC Statement (Republic of Korea) . . . . . . . . . . . . . . . . . . . . . . 91 VCCI statement (Japan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 BSMI warning (Republic of Taiwan) . . . . . . . . . . . . . . . . . . . . . . 92 CE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Canadian requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Laser compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Safety and EMC regulatory compliance . . . . . . . . . . . . . . . . . . . 93 Environmental and safety compliance . . . . . . . . . . . . . . . . . . . . 94 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Appendix A
HBA configuration
Instance-specific persistent parameters . . . . . . . . . . . . . . . . . . . . . . 97 Driver-level parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Linux and VMware driver configuration parameters . . . . . . . . . 98 Windows driver configuration parameters . . . . . . . . . . . . . . . .100 Solaris driver configuration parameters. . . . . . . . . . . . . . . . . .101
Appendix B Index
List of acronyms
vi
About this document
In this chapter
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii HBA serial number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Port World-Wide Port Name (PWWN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
How this document is organized

This document 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, Introduction, provides a detailed product overview and description. Information on

HBA hardware and software compatibility is also included.
Chapter 2, Installation, provides procedures to install HBA hardware, connect to the fabric,
and install software, such as the Brocade Host Connectivity Manager (HCM) and driver packages.
Chapter. 3, Troubleshooting, provides help in troubleshooting common installation problems. Chapter 4, HBA Boot Code, describes host boot support available on the HBA and provides
an introduction to boot over SAN. It also includes procedures to update HBA boot code, configure boot over SAN, and configure fabric-based boot over SAN.
Chapter 5, Specifications, includes details on HBA physical characteristics, LED operation,

environmental requirements, and power requirements. Also included are Fibre Channel standards, regulatory, and safety compliancy information.
Appendix A, Modifying HBA Configuration Parameters, is optional for users who want to
modify values for HBA 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.
vii
Supported hardware and software

This section describes HBA hardware and software support.
HBA support
The following Fibre Channel host bus adapters (HBAs) are supported in this release.
Brocade 815. Single-port HBA with a per-port maximum of 8 Gbps using an 8 Gbps SFP+. Brocade 825. Dual-port HBA with a per-port maximum of 8 Gbps using an 8 Gbps SFP+. Brocade 415. Single-port HBA with a per-port maximum of 4 Gbps using a 4 Gbps SFP. Brocade 425 Dual-port HBA with a per-port maximum of 4 Gbps using a 4 Gbps SFP.
Notes:
This publication only supports the HBA models listed above 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.
Install only Brocade-branded SFPs in these HBAs.
Fabric OS and switch support

For a current list of compatible servers, switches, storage, and applications, refer to the Brocade HBA web site at www.brocade.com/hba.
Host operating system support

The following operating systems support Brocade Host Connectivity Manager (HCM), Brocade Command Line Utility (BCU), and HBA drivers:
Windows Server 2003, version R2 with SP2 Windows Server 2008 Windows NT (HCM support only) Windows 2000 (HCM support only) Linux RHEL4, RHEL5, SLES9, and SLES10 Solaris 10 (x86 and SPARC) VMware ESX Server 3.5
NOTE
Drivers, BCU, and HCM Agent are supported only on the VMware console Operating System. HCM is supported only on the guest operating system on VMware.
Windows Vista (HCM only) Windows XP (HCM only)
viii
Specific operating system service pack levels and other patch requirements are detailed in the current HBA release notes.
NOTE
Whats new in this document

This is a new document. For further information about new features not covered in this document and documentation updates for this release, refer to the HBA release notes.
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 for the HCM or BCU Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles Identifies BCU output Identifies command syntax examples
italic text
code text
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. Otherwise, this manual specifically notes those cases in which a command is case sensitive.
Command syntax conventions

Command syntax in this manual follows these conventions: command
--option, option -argument, arg
Commands are printed in bold. Command options are printed in bold. Arguments. Optional element.
[]
ix
variable ... value |
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...] Fixed values following arguments are printed in plain font. For example, --show WWN Boolean. Elements are exclusive. Example: --show -mode egress | ingress
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.
Key terms
For definitions specific to Brocade and Fibre Channel, see the technical glossaries on Brocade Connect. See Brocade resources on page xi for instructions on accessing Brocade Connect.
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.
Corporation
Microsoft Corporation
Referenced Trademarks and Products

Windows, Windows Server 2003, Windows Server 2008, Vista, XP, PE for Windows, Hyper V for Windows, Windows Automated Installation Kit (WAIK) Solaris Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise Server (SLES) ESX Server SPARC
Sun Microsystems, Inc. Red Hat Inc. Novell, Inc VMware Inc. SPARC International, Inc
Additional information
This section lists additional Brocade and industry-specific documentation that you might find helpful.
Brocade resources
Access a variety of HBA user resources such as the following through the Brocade HBA web site at www.brocade.com/hba.
Information about Brocade HBA features, benefits, and specifications. HBA software, drivers, and documentation downloads. Complete information on HBA compatibility with operating systems, server platforms, and
storage systems.
Support and warranty contact information.

Training courses on Brocade HBAs are also available. Select Course Catalog on the Education Services home page at (http://www.brocade.com/education/ To get up-to-the-minute information on all products and services, join Brocade Connect. Its free! Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and password. For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through: http://www.amazon.com For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location: http://www.brocade.com
xi
Other industry resources

White papers, online demos, and data sheets are available through the Brocade Web site at
http://www.brocade.com/products-solutions/.
Best practice guides, white papers, data sheets, and other documentation is available through
the Brocade Partner web site. For additional resource information, visit the Technical Committee T11 web site. This web site 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 web site: http://www.fibrechannel.org
Getting technical help

Contact your HBA support supplier for hardware, firmware, and software support, including product repairs and part ordering. Provide the following information:
bfa_supportsave output (refer to bfa_supportsave feature). 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.
bfa_supportsave feature
To expedite your support call, use the bfa_supportsave 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 Using Support Save on page 54.
HBA serial number

The HBA serial number and corresponding bar code are provided on the serial number label illustrated below. The serial number label is located on the end of the HBA opposite from the SFP receivers. Refer to Figure 1 on page 2 for location. *FT00X0054E9* FT00X0054E9 You can also display the serial number through the following HCM dialog boxes and BCU commands:
HBA Properties tab in HCM
xii
Select an HBA in the device tree, then click the Properties tab in the right pane.
BCU adapter --list command

For details on using HCM and BCU commands, refer to the Brocade Fibre Channel HBA Administrators Guide.
NOTE
Port World-Wide Port Name (PWWN)

Determine this through the following resources:
Label located on the end of the HBA opposite the SFP receiver slots. This label provides the
WWPN for each port. Refer to Figure 1 on page 2.
Brocade BIOS Configuration Utility.

Select the appropriate HBA port from the initial configuration utility screen, then select Adapter Settings to display the WWNN and PWWN for the port. For details, refer to Configuring BIOS using the Brocade configuration utility on page 63.
HCM Port Properties dialog box.

This dialog box displays the PWWN for each HBA port. To display this dialog box, click a port in the device tree, then click the Properties tab in the right pane.
The following BCU commands:

adapter --query <ad_id>
This command displays HBA information. The <ad_id> parameter is the HBAs serial number.
port --list <ad_id>
This command lists all the physical ports on the HBA along with their basic attributes. The <ad_id> parameter is the HBAs serial number.
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.
xiii
xiv
Chapter
In this chapter
This chapter contains general information about the Brocade Fibre Channel host bus adapters (HBAs). This chapter includes the following topics:
HBA product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Hardware and software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Software installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Boot installation packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Downloading software and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Brocade offers four models of Fibre Channel Fibre Channel PCIe Host Bus Adapters (Table 1). hereafter referred to in this publication as Brocade HBAs. These models provide reliable, high-performance host connectivity for mission-critical SAN environments.
TABLE 1
Model Number
Brocade 825 Brocade 815 Brocade 425 Brocade 415
Brocade Fibre Channel HBA Models

Port Speed
8 Gbps maximum 8 Gbps maximum
1 1
Number of Ports
2 1 2 1
4 Gbps maximum2 4 Gbps maximum
1. A 4 Gbps SFP installed in Brocade 815 or 825 HBAs allows 4, 2, or 1 Gbps only. 2. An 8 Gbps SFP+ installed in Brocade 425 or 415 HBAs allows 2 or 4 Gbps only.
NOTE
Install only Brocade-branded SFPs in these HBAs.
Using Brocade HBAs you can connect your server (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.
This publication only supports the HBA models listed in Table 1, and does not provide information about the Brocade 410 and 420 Fibre Channel HBAs, also known as the Brocade 400 Fibre Channel HBAs. Figure 1 on page 2 illustrates the Brocade 825 HBA. Please note that the illustration is representative and may have minor physical differences from the HBA that you purchased.
NOTE
FIGURE 1
825 HBA with low-profile mounting bracket
Table 2 describes HBA components illustrated in Figure 1.
TABLE 2
Number
1 2 3 4
HBA Components
Component
LEDs for port 1 SFP Fiber optic cable connectors for port 1 SFP and port 0 SFP LEDs for port 0 SFP Low-profile mounting bracket. Note: The HBA ships with the low-profile mounting bracket installed. PCIe x8 connector ASIC Serial number label Label showing PWWN for each port.
5 6 7 8
ATTENTION
Only use Brocade-branded SFP laser transceivers supplied with this product.
HBA features
The Brocade Fibre Channel HBA provides the following features for enhanced performance and connectivity in the SAN. For detailed HBA specifications, including Fibre Channel feature support, refer to Specifications on page 87.
500,000 IOPS per port for maximum IO transfer rates. 1,600 MBps throughput per port full duplex. Fabric-based boot logical unit number (LUN) discovery. Host Connectivity Manager (HCM) device management and Brocade Command Line Utility (BCU) tools. management frameworks.
Management APIs for integration with Brocade Data Center Fabric Manager (DCFM) and other 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. This feature is supported only on 8 Gbps ports installed on switch models that use Fabric OS 6.2 and above. The following licenses need to be installed on the switch connected to each HBA port (edge switch).
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 Operating System Administrators Guide.
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.
Target rate limiting. This feature throttles the Fibre Channel Protocol (FCP) read traffic rate to
slow-draining targets to reduce or eliminate network congestion and alleviate I/O slowdowns to 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.
N_Port ID Virtualization (NPIV). End-to-end beaconing between an HBA port and switch port to which it connects. (Requires
Brocade Fabric OS 6.1.0a 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 hosts local disk or direct attached storage. Specifically, this boot device is a logical unit number (LUN) located on a storage device.
Fabric-based boot LUN discovery, a feature that allows the host to obtain boot LUN information
from the fabric zone database.
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 HBA 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 HBA 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 in Windows Vista and Windows Server 2008. The Brocade HBAs support the following host and fabric specifications:
Small form-factor pluggable (SFP+) optics for enhanced serviceability. PCIe connector with eight lanes running at 250 Mhz. x86 and x64 Basic Input/Output System (BIOS), Unified Extensible Firmware Interface (UEFI),
and PCI BIOS 3.0.
Fibre Channel-Security Protocol (FC-SP) providing device authentication through key

management.
RoHS-6. Switch fabric topology. Point-to-point topology.
HBA management
HCM is a management software GUI for installing, configuring, troubleshooting, and monitoring Brocade Fibre Channel HBAs in a storage area network (SAN). HCM provides the following features:
Discovery of HBAs and connected storage devices in your SAN. HBA configuration. Persistent binding. End-to-end QoS. Target rate limiting. Performance monitoring, such as port and target statistics. bfa_supportsave feature. HBA diagnostics. Monitoring of HBA, port, target, and Fibre Channel Protocol (FCP) operation. Security features for HBA access. Event notifications for HBA conditions and problems.
The BCU, loaded with the driver package, provides commands that are comparable to HCM features for configuring, troubleshooting, and monitoring the HBA and device connections.
Using BCU commands

Some procedures in this manual reference BCU commands for HBA monitoring and configuration. To use BCU commands, access your systems command shell. BCU runs in two modes:
Direct mode, where you type the command at the command prompt. For example: Shell mode, accessed using the bcu shell. For example:
bcu> port --speed <port_id> <1|2|4|8|auto>. bcu port --speed <port_id> <1|2|4|8|auto>
To access the shell mode, type bcu shell. To exit out of shell mode, type exit.
HBA software overview

HBA software includes the HBA driver package, Host Connectivity Manager (HCM) agent, and the HCM application.
HBA driver package

The HBA driver, firmware, and HCM Agent load as a single package to your host system. Driver packages are available for each supported host operation system and platform. Refer to Software installation packages on page 7 for details on packages available for supported host systems. The following components are also installed with the driver package:
HBA driver
The driver acts as a translator between the HBA and the applications or operating systems that communicate with the HBA.
HBA firmware
Firmware installed in the HBAs on-board flash memory and operates on the HBAs 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. As examples, the firmware performs the following tasks:
Processes upper-layer protocols into Fibre Channels sequences and frames. Off loads the task of translating SCSI I/O requests to FCP command frames. Programs the HBA hardware state machine to process each I/O request without software intervention. Manages all link level operations, including link exceptions.
Brocade Command Line Utility (BCU)

An application installed on your host system from which you can enter commands to monitor, install, and configure Brocade HBAs.
HCM agent
The agent provides an interface for managing HBAs installed on the host through the HCM application.
Host Connectivity Manager (HCM)

HCM is a graphical user interface (GUI) based management software for installing, configuring, monitoring, and troubleshooting installed HBAs. HCM performs the client function for the management software. Install HCM on the host system for local management of HBAs installed in the host or on a network-attached system for remote management of these HBAs. Refer to HBA management on page 4 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.
NOTE
HCM is compatible with any version of the driver package.
Software installation options

Two installation options are available for HBA software:
Use the Brocade HBA Software Installer to install the HBA driver package, HCM, or both on your
host system. For more information, refer to Using the Brocade HBA Software Installer on page 23.
Install the HBA driver package only using your host systems native installation method. For
more information, refer to Manual installation, removal, and upgrade of driver packages on page 34.
NOTE
Only one driver installation is required for all HBAs installed in a host system. Refer to Software installation packages on page 9 for a complete list of driver and software installer packages that you can download from the HBA website at www.brocade.com/hba.
Boot code
The HBA boot code supports the following:
PCI BIOS2.1 and above, 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 The HBA boot code loads from Brocade HBA 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. You can download boot code from the HBA website (www.brocade.com/hba) to update the boot image on installed HBAs. You can also download ISO 9660 (.iso) optical disk image files to create boot LUNs and to program and configure boot images on HBAs installed in systems without operating systems or hard drives. Refer to Boot installation packages on page 15 for complete information.
Hardware and software compatibility
Items shipped with your HBA

The following items are shipped for installation
HBA with low-profile PCI mounting bracket attached One SFP or two SFPs, depending on your HBA model HBA standard (full-height) PCI mounting bracket Brocade Fibre Channel HBA Quick Installation Guide Instructions for downloading software

This section outlines important compatibility information.
SFP transceivers
Use only the following Brocade-branded small form factor pluggable (SFP) fiber optic transceivers in the Brocade Fibre Channel HBAs:
4Gbps SFP, P/N 57-1000013-01 8Gbps SFP+, P/N 57-1000012-01

All Brocade 815 and 825 HBAs ship with the 8 Gbps SFP+, and Brocade 415 and 425 HBAs ship with the 4 Gbps SFP.
NOTE
Host systems
Refer to the latest compatibility matrix posted through Brocade Connect or the Partner Network at www.brocade.com for a list of supported server models.
PCI-express slots
The Brocade Fibre Channel HBAs are compatible in PCI-Express (PCI-e) slots with the following specifications:
x8 lane or greater transfer interface. Gen1 (PCI Base Specification 1.0, 1.01a, and 1.1). Effective data rate is 16 Gbps. Gen2 (PCI Express Base Specification 2.0). Effective data rate is 32 Gbps."
NOTE
Install HBAs in PCI-Express slots with an x8 lane transfer interface or greater for best performance. You cannot install HBAs in PCI or PCI-X slots.
Storage systems
Using Brocade HBAs you can connect a server (host system) to a Fibre Channel SAN in switched fabric and point-to-point topologies. Refer to the latest compatibility matrix through Brocade Connect or the Partner Network at www.brocade.com for a list of supported storage systems.
Host operating systems

Table 3 provides information on compatible software operating systems and environments for the Brocade Fibre Channel HBAs.
NOTE
For the latest support information, refer to the release notes for your HBA software version.
TABLE 3
Note
Operating System Support Matrix

x86 x64 IA64 SPARC
Operating System
Windows1 Windows Server 2003 SP22 Windows Server 2008 Microsoft PE 2.0 for Windows 2008 Standard/Enterprise Server Microsoft PE 2.0 for Windows Vista Server Microsoft Hyper V for Windows 2008 Standard/Enterprise Server Microsoft WinPE for Windows 2008 Standard/Enterprise Server Windows Server Core for Windows 2008 Linux Red Hat Enterprise Linux (RHEL) 4.6 and 4.7 Red Hat Enterprise Linux (RHEL) 5.1 and 5.2 SUSE Linux Enterprise Server (SLES) 9.3 and 9.4 SUSE Linux Enterprise Server (SLES) 10.1 and 10.2 Solaris3 Solaris 10.5 VMware VMware ESX 3.5, 3.5 U1, 3.5 U24
32b 32b 32b 32b 32b 32b 32b
64b 64b 32b, 64b 32b, 64b 32b, 64b 32b, 64b 32b, 64b
64b 64b 64b No support No support 64b 64b
N/A N/A N/A NA N/A N/A N/A
32b 32b 32b 32b
32b, 64b 32b, 64b 32b, 64b 32b, 64b
64b 64b No support 64b
No support No support No support No support
32b
32b, 64b
N/A
64b
32b
32b, 64b
N/A
N/A
Software installation packages
1. For Windows, the Storport miniport driver is supported (there is no support for the SCSI miniport driver). 2. Before installing the driver package to a Windows Server 2003 system, install the following hot fix from the indicated location on the Microsoft Help and Support web site, then reboot the system. http://support.microsoft.com/kb/932755/en-uso 3. For Solaris, only the Leadville-based driver is supported. Note that the Solaris driver does not support NPIV, authentication, and fabric device management interface (FDMI). 4. The 8 Gbps FC HBA is supported on ESX 3.5 U2.

Download software installers, drivers, and documentation from the Brocade HBA web site at www.brocade.com/hba. Table 4 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:
An HBA Software Installer that you can use to install the driver package, HCM, or driver
package and HCM. Instructions are provided under HBA software installation on page 21.
A driver package that you can install using native instructions for your hosts operating
system. Installation procedures are provided under Manual installation, removal, and upgrade of driver packages on page 34.
An ISO 9660 (.iso) optical disk image containing all files listed in the supported software
installation packages table (Table 4 on page 9) and boot installation packages table (Table 5 on page 15). Use this image to create CDs or DVDs 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 CD 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. Download this image by selecting Download ISO Image link on the HBA website home page. brocade_hba_ISO_<date>.iso In Table 4, <version> indicates the software version number (for example v1-0-0), which will change for each release.
NOTE
TABLE 4
Operating System and Platform
Windows Server 2003 (x86 R2 SP2)
Supported software installation packages

Brocade HBA Software Installer Driver Package
bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package.
bfa_driver_win2003_x86_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on x86 platforms.
TABLE 4
Windows Server 2003 (x86_64 R2 SP2) Windows Server 2003 (IA-64 R2 SP2) Windows Server 2008 (x86) Windows Server 2008 (x86_64) Windows Server 2008 (IA-64) Windows XP SP2 (x86 and x86_64) Windows Vista (x86 and x86_64) Linux RHEL 4.6, 4.7 (x86)

bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package. bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package. bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package. bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package. Bfa_setup_windows_<version >.exe Installs HCM and appropriate driver package. bfa_setup_windows_<version >.exe Installs HCM only. bfa_setup_windows_<version >.exe Installs HCM only.
bfa_driver_win2003_x64_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on the EM64T and AMD64 platforms. bfa_driver_win2003_ia64_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on Itanium Edition IA-64 platforms. bfa_driver_win2008_x86_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on x86 platforms.
bfa_driver_win2008_x64_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on EM64T and AMD64 platforms.
bfa_driver_win2008_ia64_<version>.exe Storport miniport driver with HCM Agent for Standard/Enterprise Server on Itanium Edition IA-64 platforms. Driver N/A HCM application only for x86 platforms.
Driver N/A HCM application only for x86 platforms.
bfa_setup_linux_<version>.bin RHEL Binary Drivers Installs HCM and brocade-bfa-default-<version>_2.6.9_67.EL-0.i386.rpm appropriate driver brocade-bfa-hugemem-<version>_2.6.9_67.EL-0.i386.rpm package. brocade-bfa-smp-<version>_2.6.9_67.EL-0.i386.rpm brocade-bfa-default-<version>_2.6.9_78.EL-0.i386.rpm brocade-bfa-hugemem-<version>_2.6.9_78.EL-0.i386.rpm brocade-bfa-smp-<version>_2.6.9_78.EL-0.i386.rpm bfa_util_linux-<version>_noarch.rpm Latest precompiled drivers for 2.6.9-67 and 2.6.9-78 kernels and subsequent updates. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU.
10
TABLE 4
Linux RHEL 4.6, 4.7 (x86_64)

bfa_setup_linux_<version>.bin RHEL Binary Drivers Installs HCM and brocade-bfa-default-<version>_2.6.9_67.EL-0.x86_64.rpm appropriate driver brocade-bfa-largesmp-<version>_2.6.9_67.EL-0.x86_64.rpm package. brocade-bfa-smp-<version>_2.6.9_67.EL-0.x86_64.rpm brocade-bfa-default-<version>_2.6.9_78.EL-0.x86_64.rpm brocade-bfa-largesmp-<version>_2.6.9_78.EL-0.x86_64.rpm brocade-bfa-smp-<version>_2.6.9_78.EL-0.x86_64.rpm bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for 2.6.9-67 and 2.6.9-78 kernels and subsequent updates. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU. bfa_setup_linux_<version>.bin RHEL Binary Drivers Installs HCM and kmod-bfa-<version>_i686.rpm appropriate driver kmod-bfa-PAE-<version>_i686.rpm package. kmod-bfa-xen-<version>_i686.rpm bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for RHEL 5.1 and 5.2. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU. bfa_setup_linux_<version>.bin RHEL Binary Drivers Installs HCM and kmod-bfa-<version>_x86_64.rpm appropriate driver kmod-bfa-xen-<version>_x86_64.rpm package. bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for RHEL 5.1 and 5.2. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU. bfa_setup_linux_<version>.bin RHEL Binary Drivers Installs HCM and kmod-bfa-<version>_ia64.rpm appropriate driver kmod-bfa-xen-<version>_ia64.rpm package. bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for RHEL 5.1 and 5.2. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent.
Linux RHEL 5.1, 5.2 (x86)
Linux RHEL 5.1, 5.2 (x86_64)
Linux RHEL 5.1, 5.2 (IA64)
11
TABLE 4
Linux SLES 9.3, 9.4 (x86)

bfa_setup_linux_<version>.bin Novell Inc. Certified Distribution Installs HCM and brocade-bfa-<version>_2.6.5_7.308-0.i586.rpm appropriate driver brocade-bfa-<version>2.6.5_7.308-0.src.rpm package. brocade-bfa-<version>_2.6.5_7.<variable>-0.i586.rpm brocade-bfa-<version>_2.6.5_7.<variable>-0.src.rpm bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for 2.6.5-7.308 and 2.6.5-7.311 kernels for x86 platforms. The src RPM is the driver source. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1bfa_driver_linux-<version>.noarch.rpm Latest drivers and user applications, such as HCM Agent.
Linux SLES 9.3, 9.4 (x86_64)
bfa_setup_linux_<version>.bin Novell Inc. Certified Distribution Installs HCM and brocade-bfa-<version>_2.6.5_7.308-0.src.rpm appropriate driver brocade-bfa-<version>_2.6.5_7.308-0.x86_64.rpm package. brocade-bfa-<version>_2.6.5_7.311-0.src.rpm brocade-bfa-<version>_2.6.5_7.311-0.x86_64.rpm bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for 2.6.5-7.308 and 2.6.5-7.311 kernels. The src RPM is the driver source. The noarch RPM includes applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent.
12
TABLE 4
Linux SLES 10.1, 10.2 (x86)

bfa_setup_linux_<version>.bin Novell Inc. Certified Distribution Installs HCM and brocade-bfa-<version>-1.src.rpm appropriate driver brocade-bfa-kmp-bigsmp-<version>_2.6.16.46_0.12-0.i586.rpm package. brocade-bfa-kmp-debug-<version>_2.6.16.46_0.12-0.i586.rpm brocade-bfa-kmp-default-<version>_2.6.16.46_0.12-0.i586.rpm brocade-bfa-kmp-smp-<version>_2.6.16.46_0.12-0.i586.rpm brocade-bfa-kmp-xen-<version>_2.6.16.46_0.12-0.i586.rpm brocade-bfa-kmp-xenpae-<version>_2.6.16.46_0.12-0.i586.rpm brocade-bfa-kmp-vmi-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-bigsmp-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-vmipae-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-debug-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-xen-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-default-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-xenpae-1.0.0.02_2.6.16.60_0.21-0.i586.rpm brocade-bfa-kmp-smp-1.0.0.02_2.6.16.60_0.21-0.i586.rpm bfa_util_linux-<version>.noarch.rpm Latest precompiled drivers for 2.6.16.46-0.12 and 2.6.16.60-0.21 kernels for Linux 10 SP1 and SP2. The src RPM is the driver source. The noarch RPM includes user applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU.
Linux SLES 10.1, 10.2 (x86_64)
bfa_setup_linux_<version>.bin Novel Inc. Certified Distribution Installs HCM and brocade-bfa-<version>1.src.rpm appropriate driver brocade-bfa-kmp-debug-<version>_2.6.16.46_0.12-0.x86_64.rp package. m brocade-bfa-kmp-default-<version>_2.6.16.46_0.12-0.x86_64.r pm brocade-bfa-kmp-smp-<version>_2.6.16.46_0.12-0.x86_64.rpm brocade-bfa-kmp-xen-<version>_2.6.16.46_0.12-0.x86_64.rpm brocade-bfa-kmp-smp-1.0.0.02_2.6.16.60_0.21-0.x86_64.rpm brocade-bfa-kmp-debug-1.0.0.02_2.6.16.60_0.21-0.x86_64.rp m brocade-bfa-kmp-xen-1.0.0.02_2.6.16.60_0.21-0.x86_64.rpm brocade-bfa-kmp-default-1.0.0.02_2.6.16.60_0.21-0.x86_64.rp m
bfa_util_linux-<version>.noarch.rpm
Latest precompiled drivers for 2.6.16.46-0.12 and 2.6.16.60-0.21 kernels for Linux 10 SP1 and SP2. The src RPM is the driver source. The noarch RPM includes applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>_noarch.rpm Latest driver and user applications, such as HCM Agent and BCU.
13
TABLE 4
Linux SLES 10.1, 10.2 (IA-64)

N/A
Novell Inc. Certified Distribution brocade-bfa-<version>-1.src.rpm brocade-bfa-kmp-debug-<version>_2.6.16.46_0.12-0.ia64.rpm brocade-bfa-kmp-default-<version>_2.6.16.46_0.12-0.ia64.rpm brocade-bfa-kmp-debug-1.0.0.02_2.6.16.60_0.21-0.ia64.rpm brocade-bfa-kmp-default-1.0.0.02_2.6.16.60_0.21-0.ia64.rpm bfa_util_linux-<version>.noarch.rpm
Latest precompiled drivers for 2.6.16.46-.0.12 and 2.6.16.60-0.21 kernels for Linux 10 SP1 and SP2. The src RPM is the driver source. The noarch RPM includes applications such as the HCM Agent and BCU. Be sure to install this RPM after the driver RPM. 1 bfa_driver_linux-<version>.noarch.rpm Latest driver and user applications, such as HCM Agent and BCU. Solaris 10.5 (x86) bfa_setup_solaris10_x86_<ve rsion>.bin Installs HCM and appropriate driver package. bfa_setup_solaris10_x86_<ve rsion>.bin Installs HCM and appropriate driver package for operating system and platform.
2bfa_driver_solaris10_<version>.pkg
Leadville based driver with HCM Agent for x86 platforms.
Solaris 10.5 (x86)
2bfa_util_linux-<version>_noarch.rpm
Leadville based driver with HCM Agent for EM64T and AMD64 platforms.
Solaris 10.5 SPARC (x86_64) VMware 3.5 U2
bfa_setup_solaris10_sparc_<v 2bfa_util_linux-<version>_noarch.rpm ersion>.bin Leadville based driver with HCM Agent for SPARC platforms. Installs HCM and appropriate driver package. Note: Use appropriate HBA software installer listed in this column to install HCM on applicable guest operating system only. software installer and HCM are not supported on VMware console operating system. bfa_driver_esx35_<version>.tar.gz ESX 3.5 driver with HCM Agent for x86, EM64T, and AMD64 platforms.
1. This package is the source-based RPM for all RHEL and SLES Linux distributions. The driver module is compiled on the system during the RPM installation. 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: 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. 2. This package contains all drivers for Solaris distributions.
14
Boot installation packages

Download installation packages to support boot operations, such as boot from SAN and updating HBA boot code, from the Brocade HBA web site at www.brocade.com/hba. On the website, select your hosts operating system in the Operating Systems list to display the appropriate download screen, then select the Boot Code area. Table 5 describes the installation packages for boot support that you can download for each supported operating system. The table provides the package name, host system supported, and package description. The following 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. An Zip file is available for Windows 2003 systems.
A LiveCD ISO image (live_cd.iso) containing the HBA 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 HBAs 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 on page 82. This image contains the HBA driver, boot code, and minimum operating system to boot systems without installed operating systems or local drives.
An ISO 9660 (.iso) optical disk image containing all files listed in the supported software
installation packages table (Table 4 on page 9) and boot installation packages table (Table 5 on page 15). Use this image to create CDs 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 CD 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. Download this image by selecting Download ISO Image link on the HBA website home page. brocade_hba_ISO_<date>.iso
HBA boot image. This contains BIOS and UEFI boot code and firmware used by the boot code to
boot from the HBA. Load this code to option ROM on the HBA using the BCU boot --upload command.
TABLE 5

Driver Update Disk Image
bfa_w2k3_x86_dud.zip
1
Operating System (Platform)

Windows 2003 (x86) Windows 2003 (x86_64) Windows 2003 (IA-64) Windows 2008 (x86) Windows 2008 (x86_64) Windows 2008 (IA-64)
LiveCD
live_cd.iso live_cd.iso NA2. live_cd.iso live_cd.iso NA
2
Boot Code
bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw
bfa_w2k3_x64_dud.zip bfa_w2k3_ia64_dud.zip bfa_w2k8_x86_dud.zip3 bfa_w2k8_x64_dud.zip bfa_w2k8_ia64_dud.zip
15
Downloading software and publications
TABLE 5

Driver Update Disk Image
bfa_rhel4_dud.iso bfa_rhel51_i386_dud.iso bfa_rhel52_i386_dud.iso bfa_rhel51_x86_64_dud.iso bfa_rhel52_x86_64_dud.iso bfa_rhel51_ia64_dud.iso bfa_rhel52_ia64_dud.iso bfa_sles9sp4_dud.iso bfa_sles10sp1_dud.iso bfa_sles10sp2_dud.iso esxupdatecd.iso
Operating System (Platform)

LInux RHEL 4 (x86, x86_64) Linux RHEL 5 and later (x86) Linux RHEL 5 and later (x86_64) Linux RHEL 5 and later (IA-64) Linux SLES 9 (x86, x86_64, and IA-64) Linux SLES 10 SP1, SLES 10 SP2, and later (x86, x86_64, and IA-64) VMware 3.5 ESX
1.
LiveCD
live_cd.iso live_cd.iso live_cd.iso NA2 live_cd.iso live_cd.iso
Boot Code
bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw bfa_boot_fw
live_cd.iso
bfa_boot_fw
Zip file contains files for floppy disk.
2. LiveCD is not available for UEFI-based systems. Create an appropriate WinPE ISO image using steps under Creating a WinPE image on page 84. 3. Zip file contains files for floppy disk.
Downloading software and publications

To download all HBA software and boot code, use the following steps: 1. Access the Brocade HBA website at www.brocade.com\hba. 2. Select Linux, Solaris, VMware, Windows in the Operating Systems list to display the appropriate download screen for your operating system. 3. On the download screen, select the appropriate software from the HBA Software Installer, Drivers, and Boot Code areas. Select product publications from the Documentation section. 4. If downloading software, acknowledge the HBA Download Agreement. 5. When the File Download screen displays, save the file to an appropriate location on your system.
16
Chapter
Installation
In this chapter
HBA hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HBA software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HBA software removal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HBA software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual installation, removal, and upgrade of driver packages . . . . . . . . . . Modifying HCM Agent operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing an HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 21 28 33 34 44 46
HBA hardware installation

This section provides instructions for installing the HBA and connecting it to the fabric.
ATTENTION
What you need for installation

Phillips #1 screwdriver. HBA with appropriate mounting bracket attached. 62.5/125 or 50/125 micron multimode optical cable with LC duplex connectors to connect
the HBA to the fabric. Refer to Fiber optic cable on page 89 for specifications.
Fully operational host. Access to a host from user workstation either through LAN connection or direct attachment.
ESD Precautions
When handling the HBA, use correct electrostatic discharge (ESD) procedures.
Wear a wrist grounding strap connected to chassis ground (if host is plugged in) or a bench
ground.
Store the HBA in antistatic packaging.
17
Installing the HBA

ATTENTION
The HBA 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 HBA by the edge and not the board components or gold connector contacts. 1. Check that you have received all items listed in Items shipped with your HBA on page 7. 2. Remove the HBA 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 HBA. 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 HBA. If the panel is secured with a screw, remove the screw and save it for securing the HBAs bracket panel back in the slot.
NOTE
For best performance, install the HBA into a PCIe slot with an x8 lane or greater transfer interface. Also, do not install this HBA in a PCI slot. PCIe slots are shorter than PCI slots. 7. Remove all transceivers from the HBA if clearances inside your system case prohibit you from installing the HBA with transceivers installed. Follow instructions under Removing and installing SFP transceivers on page 20. Otherwise go on to the next step.
8. Install the longer, standard bracket on the HBA if the low-profile mounting bracket (shipped installed on HBA) does not fit your system case. Use the following steps. If the installed low-profile bracket works, go on to step 9. a. b. Make sure to remove all SFP transceivers from the HBA. Refer to Removing and installing SFP transceivers on page 20 for procedures. Remove the two screws attaching the bracket to the HBA card, and pull off the bracket. Refer to Figure 2.
18
FIGURE 2
c. d. e.
Removing or installing HBA mounting bracket
Carefully guide the new mounting bracket onto the HBA card, making sure the bracket mounting tabs align with the holes in the HBA card. Replace and tighten the two screws. Store the mounting bracket that you removed for future use.
9. Insert the HBA into the desired empty PCIe bus slot. Press firmly until the HBA seats. Refer to Figure 3 for seating directions.
Screw
Press Here
Press Here SFP Receivers
Edge of Host Board
PCI Express X8 Slot
19
FIGURE 3
Installing HBA in system chassis
10. Secure the HBAs 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. Make sure required SFPs are installed into HBA receivers. If any are not installed, refer to Removing and installing SFP transceivers on page 20 for procedures. 12. Replace the systems case or cover and tighten all screws.
Connecting the HBA to the fabric

Use only multimode fiber optic cable with LC connectors when connecting the HBA to the fabric. Refer to Fiber optic cable on page 89 for cable specifications. 1. Pull out the protective rubber inserts from the HBA SFP connectors (if installed). 2. Connect the cable from the fabric to the appropriate SFP LC connector on the HBA.
Removing and installing SFP transceivers

Use only the following Brocade-branded small form factor pluggable (SFP) optic transceivers in the Brocade Fibre Channel HBAs. Refer to Hardware and software compatibility on page 7 for part numbers.
NOTE
Removing SFP transceivers

1. Pull out the protective rubber plug from the SFP connector. 2. Using your thumb and forefinger, unlatch the bail from the side of the cable connector and pull the SFP straight out of the HBA receiver. Refer to Figure 4.
20
HBA software installation
0 PO RT
FIGURE 4
Removing or Installing SFP
Installing SFP transceivers

1. Orient the SFP in front of its slot on the HBA so that it can slide into the HBA receiver slot. The SFP can only be oriented one way into the slot. 2. Using the bail as a handle, carefully guide the SFP into an HBA receiver until it seats, then latch the bail.

Use information in this section to install the Host Connectivity Manager (HCM) and the specific driver package for your host platform using the Brocade HBA Software Installer application. For instructions to manually install, update, and remove HBA driver packages using steps native to your host system, refer to Manual installation, removal, and upgrade of driver packages on page 34. The Brocade HBA Software Installer application allows you to install all HBA software or to selectively install the HCM or driver package. For details on HCM, HBA drivers, and other HBA software components for each supported host system, refer to Hardware and software compatibility on page 7 and Software installation packages on page 9. Two installation options are available using the Brocade HBA Software Installer:
Installation using a GUI-based Brocade HBA Software Installer. Refer to Using the Brocade
HBA Software Installer on page 23.
Installation using Brocade HBA Software Installer commands from your systems command
line. This method completely installs the driver package, HCM, or both components without user interaction. Refer to Using HBA Software Installer commands on page 26.
21
Installation notes
Please read through the following notes before installing HBA software:
The Brocade HBA Software Installer is available for Windows, Linux, and Solaris operating
systems. You can use the appropriate Brocade HBA Software Installer to install HCM only on the VMware guest operating system. Find the installer program for your hosts operating system and platform under Software installation packages on page 9.
Windows systems bfa_setup_windows_<version>.exe Linux systems bfa_setup_linux_<version>.bin Solaris systems bfa_setup_<Solaris version>_<platform>_<version>.bin
HBA software installation using the Brocade HBA Software Installer is not supported on the
following systems:
Itanium edition IA-64 platforms with RHEL Linux operating systems. VMware console operating system. HCM installation using the HBA Software Installer is supported on the VMware guest operating system.
You must use the Brocade HBA Software Installer application to install HCM. You can install
HCM to the host system where the HBA is installed or to a separate remote management platform.
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/esxcfg-firewall -o 34568,tcp,in,https /usr/sbin/esxcfg-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 procedures under Modifying HCM Agent operation on page 44.
When installing the bfa_driver_linux-<version>.noarch.rpm driver package on Linux SLES 10 SP2 and SLES 9 SP4 systems, make sure that the LOAD_ UNSUPPORTED_MODULES_AUTOMATICALLY variable on your system is set to yes, or the driver will not load on system reboot. This variable is in the following configuration files:
SLES 10 SP2: /etc/sysconfig/hardware/config SLES 9 SP4: /etc/sysconfig/hotplug/
Only one driver installation is required for all HBAs installed in a host system. Root or administrator privileges are required for installing the driver package. The procedures in this section assume that the hosts operating system has been installed and
is functioning normally.
Before installing the driver package to a Windows Server 2003 system, install the following hot
fix from the indicated location on the Microsoft Help and Support web site, then reboot the system. This is a fix for an issue related to stop error when shutting down W2K3 SP2. http://support.microsoft.com/kb/932755/en-uso
22
You can elect to start or not start the HCM Agent during installation with the GUI-based HBA
Software Installer or Software Installer commands. If you elect to not start the agent, you can manually start the agent using instructions under Modifying HCM Agent operation on page 44
Using the Brocade HBA Software Installer

The Brocade HBA Software Installer operates on systems specified under Software installation packages on page 9. Use this GUI-based application to install the driver package only, the driver package and HCM, or HCM only to your system. To install the driver package, the driver package and HCM, or HCM only using Software Installer commands instead of the GUI-based application, refer to Using HBA Software Installer commands on page 26. To install the driver package only using your systems native installation procedures, refer to Manual installation, removal, and upgrade of driver packages on page 34. Use the following steps to install HBA software using the Brocade HBA Software Installer: 1. Download software from the Brocade HBA web site at www.brocade.com/hba using one of these options:
Download the appropriate Brocade HBA Software Installer executable (.exe or .bin) file for
your operating system: Find the installer program for your systems operating system and platform under Software installation packages on page 9.
Download an ISO 9660 (.iso) optical disk image containing the Brocade HBA 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 CD 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 CD, skip to step .
2. Execute the appropriate Brocade HBA Software Installer program (.exe or .bin file), depending on your hosts operating system and platform. The Brocade Software Installer Introduction screen displays with instructions for using the installer. 3. Click Next. 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 message displays prompting you to restore the data directory. Select either to restore or not to restore and continue installation. If this message does not display, go on to step 6. 6. If a message displays that an older version of the software already exists on your system, select either of the following options, then skip to step 9. If this message does not display, go on to step 7.
23
Existing configurations. The installer compares each configured property and keeps the
original value if different than the default value.
Default configurations. The installer upgrades the software and loads with default
configurations. 7. When the Choose Install Set screen displays, select which software you want to install, then select Next.
NOTE
The Choose Install Set and Choose Install Folder screens will not display if you are upgrading from an older version of the software.
.
8. 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 9.
Enter a location for installing the software. Select Choose to browse to a location on your file system. Select Restore Default Folder to enter the default installation folder.
9. When the following screen displays, select either OK to start the HCM Agent or Dont Start. If you select Dont Start, Review instructions on the screen to manually start the agent on Linux, Solaris, and Windows systems after you complete software installation. You can also find instructions to manually start the agent under Modifying HCM Agent operation on page 44.
24
The Package Location Information screen displays describing the location where software installed on your system 10. Select Next to continue. The Pre-Installation Summary screen displays. 11. Review information on the screen and select Install to confirm and begin the installation. 12. Select Done when the Install Complete screen confirms installation.
13. If a message or screen displays instructing you to restart or reboot the system, perform the action indicated.
NOTE
Reboot Solaris systems. A message will not display prompting you to reboot or restart.
25
14. Verify installation using tools available on your host system. Refer to Confirming driver package installation on page 52 for details. 15. When the driver is installed and the host system is connected to the fabric (refer to Connecting the HBA to the fabric on page 20), verify proper LED operation by referring to LED operation on page 90.
Using HBA Software Installer commands

Executing the following commands without parameters will launch the GUI-based installer described under Using the Brocade HBA Software Installer on page 23.
Windows systems
bfa_setup_windows_<version>.exe (Windows)
Linux and Solaris systems

sh bfa_setup_<Platform>_<version>.bin Execute these commands on the host systems command line with various parameters to automatically install the driver package, HCM application, or both without requiring further user interaction.
Windows systems
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH] -DFORCE_WIN_DRIVER_INSTALLATION=1 -DAgent_Start=0 -i silent

sh bfa_setup_<Platform>_<version>.bin -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH] -DFORCE_WIN_DRIVER_INSTALLATION=1 -DAgent_Start=0 -i silent
where
DCHOSEN_INSTALL_SET
Specifies to install either the driver, the GUI (HCM), or both.
DFORCE_WIN_DRIVER_INSTALLATION=1 - Windows systems only, this specifies to overwrite an existing HBA driver installed on
system. This may require a reboot if used.
For Solaris, Linux, and VMWare systems, overwrite an existing driver using the standard software installer command and parameters.
-DAgent_Start=0
By default, the HCM Agent starts after installation. -DAgent_Start=0 specifies to not start the HCM Agent automatically after installation.
-i silent
Specifies that the installation mode should be silent
Important notes
Review these notes before using the software installer commands.
Parameters are case-sensitive.
26
Before using any commands described in this section, you must download the Brocade HBA
Software Installer to your system from the Brocade HBA web site at www.brocade.com/hba. Use one of the following options:
Download the appropriate Brocade HBA Software Installer to your host system. Find the installer program for your servers operating system and platform under Software installation packages on page 9. Download an ISO 9660 (.iso) optical disk image. This contains the Brocade HBA 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.
To enter these commands, first change to the directory where the HBA software is installed (cd
<install directory>). Default install directories are the following;
Windows systems C:\Program Files\BROCADE\FCHBA Linux and Solaris systems /opt/brocade/fchba
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
Examples
Following are some examples of using commands and parameters to install HBA software.
To install the driver only in silent mode and start the HCM Agent automatically by default.
Windows systems
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=DRIVER -i silent
Linux or Solaris systems

sh bfa_setup_<Platform>_<version>.bin -DCHOSEN_INSTALL_SET=DRIVER -i silent
To install the driver and HCM in silent mode and not start the HCM Agent automatically.
Windows systems
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=BOTH -DAgent_Start=0 -i silent

sh bfa_setup_<Platform>_<version>.bin -DCHOSEN_INSTALL_SET=BOTH -DAgent_Start=0 -i silent
To overwrite an existing driver with the new driver on a Windows system using silent mode and
not start the HCM Agent automatically.
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=DRIVER -DFORCE_WIN_DRIVER_INSTALLATION=1 -DAgent_Start=0 -i silent
27
HBA software removal
To install HCM only without using silent mode and start the HCM Agent automatically.
Windows systems
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=GUI

sh bfa_setup_<Platform>_<version>.bin -DCHOSEN_INSTALL_SET=GUI
Installing HCM and driver package in default mode

To install both the HCM and the driver package on your system in silent mode, you can identify a default properties file after the bfa_setup command. The HCM Agent starts automatically after installation. 1. At the command line, change to the directory where the installer is located. 2. Use the following commands:
Windows
bfa_setup_windows_<version>.exe -f HCMDefaultInstall.properties
Linux:
bfa_setup_<Platform>_<version>.bin -f HCMDefaultInstall.properties
Solaris
bfa_setup_<Platform>_<version>.bin -f HCMDefaultInstall.properties

Use the following steps to remove the HBA driver package and HCM if installed using Brocade HBA Software Installer. Instructions are provided for using the GUI-based Brocade HBA Software Installer or HBA Software Installer commands. Instructions are provided for Windows, Solaris, and Linux systems.
Important notes
Review these notes for removing the Brocade HBA software from your system.
Use steps in this section to remove HCM. Use steps in this section to remove the HBA driver package only if you installed the package
using the Brocade HBA Software Installer. If you used native installation steps under Manual installation, removal, and upgrade of driver packages on page 34 to install the driver package, the following steps will not remove the driver package. Use steps for removing the driver under Manual installation, removal, and upgrade of driver packages.
28
Using the Brocade HBA Software Uninstaller

Use the following steps to remove software that was installed using the GUI-based Brocade HBA Software Installer. Instructions are provided for Windows, Linux, and Solaris systems.
Removing software on Windows systems

Use these procedures if HCM is installed on VMware and VMware operates as a guest on your Windows system. 1. At the command line, change to the directory where the installer is located.
cd <install directory>\UninstallBrocade FC HBA <version>
NOTE
NOTE
The default install directory is C:\Program Files\BROCADE\FCHBA. 2. Enter the following command to launch the Brocade HBA Software Uninistaller.
Uninstall.bat
3. When an introduction message displays about the uninstall, click Next. A screen displays with uninstall options. 4. Perform one of the following steps:
Select Complete Uninstall to remove the HBA driver and all other installed Brocade HBA
software components. Click Next and go on to step 5.
Select Uninstall Specific Features to selectively uninstall specific software components. A

screen displays where you can select features for removal. Remove check marks by features that you wish to uninstall, then click Uninstall to continue. 5. When a message box displays asking if you want to back up the data directory, click Backup or Dont Backup. If you select Backup, a dialog box displays prompting you to select a backup directory. Use the default directory or browse to another location. Select Start Backup to back up HCM and other configuration files: To restore the backed-up configuration data when you re-install software, you must manually overwrite the new data directory contents with the backed-up data. This restores your previous settings. 6. Select Uninstall to continue with software removal. 7. When a screen displays notifying you of a successful uninstall, click Done. 8. If a message for rebooting the system displays, select the reboot option and complete the software removal process.
29
Yes, restart my system No, I will restart my system myself
Removing software on Linux systems

Use these procedures if HCM is installed on VMware and VMware operates as a guest on your Windows system. 1. Change to the directory where the HBA Software Installer (FCHBA) application is installed using the following command:
cd <install directory>/UninstallBrocade FC HBA <version>
NOTE
<install directory> - default install directory is /opt/brocade/fchba. <version> - the application version, such as v1.0.1.
2. Enter the following command to launch the Brocade HBA Software Installer:
sh Uninstall.sh
3. When an introduction message displays about the uninstall, click Next. A screen displays with uninstall options. 4. Perform one of the following steps:

screen displays where you can select features for removal. Remove check marks by features that you wish to uninstall, then click Uninstall to continue. 5. When a message box displays asking if you want to back up the data directory, click Backup or Dont Backup. If you select Backup, a dialog box displays prompting you to select a backup directory. Select Restore Default to back up to the default directory or select Choose to browse to a directory location. Select Uninstall to continue with software removal. 6. When the screen displays notifying you of a successful uninstall, click Done.
Removing software on Solaris systems

1. Change to the directory where the HBA Software Installer (FCHBA) application is installed using the following command:
<install directory> - default install directory is /opt/brocade/fchba. <version> - the application version, such as v1.0.1.
2. Enter the following command to launch the Brocade HBA Software Installer:
sh Uninstall.sh
3. When an introduction message displays about the uninstall, click Next. A screen displays with uninstall options.
30
4. Perform one of the following steps:

screen displays where you can select features for removal. Remove check marks by features that you wish to uninstall, then click Uninstall to continue. 5. When a message box displays asking if you want to back up the data directory, click Backup or Dont Backup. If you select Backup, a dialog box displays prompting you to select a backup directory. Select Restore Default to back up to the default directory or select Choose to browse to a directory location. Select Uninstall to continue with software removal. 6. When the screen displays notifying you of a successful uninstall, click Done. 7. If a message to reboot the system displays, reboot your system manually to complete software removal.
Using HBA Software Uninstaller commands

The following steps explain how to use the HBA Software Uninstaller commands to remove 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 installer described under Using the Brocade HBA Software Uninstaller on page 29.
Windows systems
Uninstall.bat -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent

sh Uninstall.sh -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent
Execute these same commands on the host systems command line with various parameters to automatically install the driver package, HCM application, or both without requiring further user interaction.
Windows systems
Uninstall.bat -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH] -DEBUG=[true|false] -i silent

sh Uninstall.sh -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH] -DEBUG=[true|false] -i silent
where
DCHOSEN_INSTALL_SET
Specifies to remove either the driver, the GUI (HCM), or both.
DEBUG - Specifies whether the debug log messages are needed. Possible values are true or
false.
-i silent - Specifies that the uninstallation mode is silent.
31
Important Notes
Review these notes before using the software uninstaller commands.
Parameters are case-sensitive. Before using any commands described in this section, you must download the Brocade HBA
Software Installer to your system from the Brocade HBA web site at www.brocade.com/hba. Use one of the following options:
Download the appropriate Brocade HBA Software Installer to your host system. Find the installer program for your servers operating system and platform under Software installation packages on page 9. Download an ISO 9660 (.iso) optical disk image. This contains the Brocade HBA 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.
To enter uninstaller commands, first change to the directory where the HBA software is
installed (cd <install directory>).
Windows systems
cd <install directory>\UninstallBrocade FC HBA <version>
The default <install directory> is C:\Program Files\BROCADE\FCHBA. <version> is a version number, such as v1.0.0.

The default <install directory> is /opt/brocade/fchba. <version> is a version number, such as v1.0.0.
To launch the uninstaller in silent mode, you must use and provide values for both the following
parameters:
DCHOSEN_INSTALL_SET -i silent
Examples
To remove the driver only in silent mode with debug messages.
Windows systems
Uninstall.bat -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent

sh Uninstall.sh -DCHOSEN_INSTALL_SET=DRIVER -DEBUG=true -i silent
To remove the driver and HCM in silent mode, but without debug messages.
Windows systems
Uninstall.bat -DCHOSEN_INSTALL_SET=BOTH -DEBUG=false -i silent

sh Uninstall.sh -DCHOSEN_INSTALL_SET=BOTH -DEBUG=false -i silent
32
HBA software upgrade
To remove HCM only without using silent mode, but with debug messages.
Windows systems
Uninstall.bat -DCHOSEN_INSTALL_SET=GUI -DEBUG=true

sh Uninstall.sh -DCHOSEN_INSTALL_SET=GUI -DEBUG=true
HBA software upgrade

To upgrade HCM, the HBA driver package, or both, simply follow instructions under Using the Brocade HBA Software Installer on page 23 or Using HBA Software Installer commands on page 26. 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 - When upgrading the driver for Windows systems, you do not need to reboot after
installation.
When using the 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 with the new driver and start the HCM Agent automatically, use the following command.
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=DRIVER -DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent
For example, to overwrite the existing driver with the new driver and not start the HCM Agent, use the following command.
bfa_setup_windows_<version>.exe -DCHOSEN_INSTALL_SET=BOTH -DFORCE_WIN_DRIVER_INSTALLATION=1 -DAgent_Start=0 -i silent
Linux
When upgrading the driver for Linux systems, you do not need to reboot the host system after installation. The new driver is effective after system reboot.
Solaris
When upgrading the driver for Solaris systems, you must reboot the host system. The new driver is not effective until after system reboot.
VMware
When upgrading the driver for VMware systems, you must reboot the host system. The new driver is effective after system reboot.
33
Manual installation, removal, and upgrade of driver packages

This section provides instructions to manually install, uninstall, and upgrade the HBA driver package using instructions native to your host system. You can use these steps for installing the driver package on your system instead of using the Brocade HBA Software Installer.
NOTE
To upgrade existing software using the Brocade HBA Software Installer, refer to Using the Brocade HBA Software Installer on page 23. Instructions are provided for the following operating systems:
Windows systems on page 35. Linux systems on page 37. Solaris systems on page 41. VMware systems on page 43.
Installation notes
The following steps assume that the hosts operating system is functioning normally and that
all HBAs have been installed in the system.
Obtain the driver package for your host system operating system and platform from the
Brocade HBA home page (www.brocade.com/hba) using one of the following options:
Download the installation package from the Brocade HBA web site for your operating system and host platform. Refer to Software installation packages on page 9. Download an ISO 9660 (.iso) optical disk image containing the latest Brocade HCM, HBA 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 CD created with the ISO image will automatically start the correct installer program for your system. Make sure that the autorun feature is enabled.
Refer to Software installation packages on page 9 for details on driver packages and
operating system support.
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/esxcfg-firewall -o 34568,tcp,in,https /usr/sbin/esxcfg-firewall -o 34568,udp,out,https
For Windows, use Windows Firewall and Advanced Service (WFAS) to open port 34568.
34
Windows systems
Use the following procedures to install, remove, and update the driver package on a Windows system. Only one driver installation is required for all HBAs installed in a host system.
Installation Notes
Before installing the driver package for a Windows Server 2003 system, install the following
hot fix from the indicated location on the Microsoft Help and Support web site, then reboot the system: http://support.microsoft.com/kb/932755/en-uso (fix for an issue related to stop error when shutting down W2K3 SP2)
Although you can install the driver using the Windows Device Manager, use the driver installer
program (bfa_installer.exe) or Brocade GUI- or command-based application (bfa_setup_windows_<version>.exe) instead for installing, uninstalling, 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 HBA ports with the switch. With Device Manager, the driver cannot obtain the OS information to register these names.with the switch. 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.
Installing driver on Windows systems

This section provides steps to install the HBA driver package on Windows systems. Refer to Software installation packages on page 9 for a description of Windows driver packages. 1. Boot the host and log on with Administrator privileges. 2. Create an HBA Drivers directory in your hosts file system, if not already created. 3. Load the appropriate driver package for your operating system and platform to your host system. Refer to Software installation packages on page 9 for a list of Windows driver packages. 4. Extract the driver package to the folder you created in step 2 using the following steps: a. b. Double-click the package file (for example, bfa_driver_win2003_x86_<version>.exe) to extract the driver files. Enter a path or browse to the driver directory where you want to install the extracted files when prompted (for example, C:\HBA Drivers). Note that you can specify a directory other than the default directory.
5. When prompted to run the installer program to install the driver, click OK.
NOTE
For Windows 2008 systems, you must disable User Account Control (UAC) to use the installer program (bfa_installer.exe). To do this, select Control Panel > User Accounts > User Accounts to display the User Accounts task window, then turn User Account Control off.
35
6. Go to the Command Prompt and change directories (cd) to the path where you extracted files in step 4. 7. Enter the following command to install the driver package:
bfa_installer.exe /i bfad.inf
You can use these additional parameters for the installer command.
bfa_installer.exe /p /i /u /g /c <Driver INF file> [Flag(s)]
Where:
/p : preinstall driver package. /i : install driver package. /u : uninstall driver package. /g : get driver package path. < Driver INF file > is the full relative path to the driver INF file location. Flags: 1 - driver package repair. Flags: 4 - force driver package installation.
After entering the command, the system loads the driver. A message box may display indicating that the target (existing) driver is newer than the source (upgrade) driver. Depending on the number of HBAs installed, this message box may display more than once. Click Continue Anyway on each instance 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. 9. Verify installation by launching the Device Manager to display all installed devices. SCSI and RAID controllers should display in the list. When you expand this list of controllers, a Brocade 425/825 4G/8G FC HBA (2 port HBA) or Brocade 415/815 4G/8G FC HBA (1 port HBA) instance should display for each port on installed HBAs. 10. If device instances do not display and instead Fibre Channel Controller 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, SCSI and RAID controllers should display in the device list and should expand to include Brocade 425/825 4G/8G FC HBA (2 port HBA) or Brocade 415/815 4G/8G FC HBA (1 port HBA) instances for all installed HBA ports. 11. Start the HCM Agent using steps underModifying HCM Agent operation on page 44.
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 (refer to Connecting the HBA to the fabric on page 20), verify proper LED operation by referring to LED operation on page 90.
36
Removing driver from Windows systems

1. Determine if the HCM Agent is running using procedures under Modifying HCM Agent operation on page 44. If it is, stop the agent using steps under the same heading. 2. Go to the Command Prompt and change directories (cd) to the HBA Drivers directory or wherever your driver package is installed. 3. Enter the following command to remove the driver package:
bfa_installer.exe /u bfad.inf
You can use these additional parameters for the installer command.
bfa_installler.exe /p /i /u /g /c <Driver INF file> [Flag(s)]
Where:
/p : preinstall driver package. /i :install driver package. /u : uninstall driver package. /g : get driver package path. < Driver INF file > is the full relative path to the driver INF file location. Flags: 1- driver package repair.
After entering the command, a series of screens may display as the system removes the driver. 4. If required by your Windows system, reboot the host.
Upgrading driver on Windows systems

To update the driver, follow procedures under Installing driver on Windows systems on page 35.
NOTE
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 HBA firmware and reinitializes the Fibre Channel link.
Linux systems
Use the following procedures to install and remove the driver package on Linux systems.
Installing driver on Linux systems

The driver package is provided in the form of a binary RPM package. If you are using a supported Linux driver package and standard host configuration, you can use these RPMs. Refer to Software installation packages on page 9 for a description of packages and kernel versions that they support. There are installation options for Linux systems depending on whether you are installing RHEL or SLES packages. For RHEL systems, use bfa_driver_linux--<version>.noarch.rpm for all kernel versions listed in Table 4 on page 9. Verify that your version is supported by this package.
37
This package is the source-based RPM for RHEL and SLES Linux distributions. The driver module is compiled on the system during the RPM installation. 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. For SLES systems, use one of the following options:
NOTE
Use bfa_driver_linux--<version>.noarch.rpm. This package supports all kernel versions listed in

Software installation packages on page 7.
NOTE
When installing SLES drivers, the message bfa: module not supported by Novell Inc., 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.
Install a separate SLES driver package listed in Table 4 on page 9 appropriate for your kernel
version. These packages are precompiled binaries certified by Novell Inc. To install user applications, such as BCU and the HCM Agent, you must also install the bfa_util_linux-<version>.noarch.rpm package, but install the SLES driver package first. Use the following steps to install the driver package on Linux systems. 1. Log on to your system. 2. Verify that the appropriate distribution kernel development packages are installed for the currently running kernel, which include the gcc compiler and the kernel sources. If not, install the applicable RPMs before continuing. These are required to compile the driver module when installing the bfa_driver_linux--<version>.noarch.rpm. 3. Create an installation directory /opt/HBA. 4. Use the following command to display the kernel version for your operating system and platform, then find the appropriate package for your kernel version in Table 4 under Software installation packages on page 9:
uname -a
As an example, entering uname -a on your Linux SLES 10 SP1 (64 bit) system may display the following:
Linux 233x64SUSE10SP1 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux
Using the code highlighted in bold in the example, find the following SLES driver listed in Table 4 under Software installation packages on page 9: brocade-bfa-kmp-smp-<version>_2.6.16.46_0.12-1.x86_64.rpm 5. Load the RPM package to the /opt/HBA directory. 6. Install the RPM using the following options for RHEL and SLES packages. For RHEL and SLES drivers Use the following command:
rpm -Uvh bfa_driver_linux-<version>.noarch.rpm
38
Messages display such as the following:

Building bfa driver Install cli Install HBAAPI library Install HBAAGENT Load bfa driver
NOTE
For SLES drivers, the message bfa: module not supported by Novell Inc., setting U taint flag displays. You can complete installation and use this driver although it is not certified or supported by Novell in this format. Precompiled binary packages For both RHEL and SLES systems, you can install a precompiled binary package for your kernel version. These packages are listed in Software installation packages on page 9. Use the following steps: a. Install the driver using the following command:
rpm -Uvh <full rpm name>
For example, for the 2.6.5-7.97.308 kernel for Linux SLES 9 SP4 (64-bit) systems, enter rpm -Uvh brocade-bfa-<version>_2.6.5_7.308-1.x86_64.rpm.
NOTE
Installing the precompiled RPM does not automatically load the driver If you are not installing the user applications in bfa_util_linux-<version>.noarch.rpm, you must enter modprobe bfa to load the driver to your system. If installing the user applications included in bfa_util_linux-<version>.noarch.rpm, enter the following command.
rpm -Uvh bfa_util_linux-<version>.noarch.rpm
b.
NOTE
Installing this RPM automatically runs modeprobe to load the driver package installed in step a.
7.
Verify if the driver package is loaded to the system with the following commands:
rpm -qa|grep bfa
This command prints the names of the driver package (bfa) if installed.
lspci
This utility displays information about all PCI buses in the system and all devices connected to them.
lsmod
This command displays information about all loaded modules. If bfa appears in the list, the HBA driver is loaded to the system.
dmesg
This command prints kernel boot messages. For the bfa entry, HBA model and driver version should display if the hardware and driver are installed successfully.
39
8. Start the HCM Agent by using steps underModifying HCM Agent operation on page 44.
NOTE
Manually installing the driver package does not automatically start the HCM Agent. 9. When the driver is installed and the host system is connected to the fabric (refer to Connecting the HBA to the fabric on page 20) observe LED operation. Verify proper LED operation, by referring to LED operation on page 90.
Removing driver from Linux systems

Use the following steps to remove the RPM package. 1. Log on to your system. 2. Verify if the driver package is loaded to the system with the following command:
rpm -qa|grep bfa
3. Determine if the HCM Agent is running using procedures under Modifying HCM Agent operation on page 44. If it is, stop the agent using steps under the same heading. 4. Remove the RPM using the rpm -e command and exact RPM package name displayed during step 2. For drivers installed with the bfa_driver_linux-<version>.noarch package, use the following command:
rpm -e bfa_driver_linux-1.0.0.0.noarch
Where 1.0.0.0 is the release version of the package. Messages such as the following display as the driver is removed:
Uninstall CLI Uninstall HBAAPI Library Stopping and Uninstallingthe HBA Agent
For the precompiled SLES drivers in the Novell Inc. distribution, use the following commands: Removing the user applications:
rpm -e bfa_util_linux-<version>.noarch.rpm
Removing the driver:

rpm -e brocade-bfa-<version>_2.6.5_7.308-1.i586.rpm
NOTE
Remove the user applications RPM (if installed) before the driver RPM to avoid driver unload failure.
40
Upgrading driver on Linux systems

To update the driver package simply install the new driver and HCM package using steps under Installing driver on Linux systems on page 37. When upgrading the driver for Linux systems, you do not need to reboot the host system. The new driver is effective after system reboot.
NOTE
Solaris systems
Use the following steps to install, remove, and upgrade the HBA driver package on Solaris systems.
Installing driver on Solaris systems

Use the following steps to install the driver package. The package installs as a BFA package named bfa_driver_<operating system>_<version>.pkg. Refer to Software installation packages on page 9 for a description of host systems that this driver package supports.
NOTE
Root access is required to install or remove the BFA package. 1. Log on to the Solaris system as a super user. 2. Copy the bfa_driver_<operating sytem>_<version>.pkg to a temporary directory on your system.
NOTE
bfa_driver_<operating sytem>_<version>.pkg contains all drivers for specific Solaris distributions. For example, bfa_driver_solaris10_<version>.pkg contains all 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 package. 4. Perform the following steps: a. b. Enter the following command and press Enter.
pkgadd -d bfa_driver_<operating system>_<version>.pkg
When prompted to select the package(s) you wish to process, enter the appropriate value for the package and press Enter. The pkgadd program performs a series of checks, then asks whether to continue the installation.
c.
Type y and press Enter to continue. The following message displays when installation is complete:
Installation of <bfa> was successful.
5. Enter the following to restart, load the driver, and reconfigure the system:
reboot -r
41
6. Verify if the driver package is loaded to the system with the following commands:
modinfo|grep bfa
If the driver package is installed, bfa Brocade Fibre Channel Adapter Driver displays.
pkginfo -l
This displays details about installed drivers. 7. Start the HCM Agent by using steps underModifying HCM Agent operation on page 44.
NOTE
Manually installing the driver package does not automatically start the HCM Agent. 8. When the driver is installed and the host system is connected to the fabric (refer to Connecting the HBA to the fabric on page 20) turn on host power and observe LED operation. Verify proper LED operation, by referring to LED operation on page 90.
Removing driver from Solaris systems

Use the following steps to remove the bfa driver package. 1. Log on to your system as root user. 2. Determine if the driver package is installed using the following command:
pkginfo|grep bfa
If the driver package is installed, bfa Brocade Fibre Channel Adapter Driver displays. 3. Determine if the HCM Agent is running using procedures under Modifying HCM Agent operation on page 44. If it is, stop the agent using steps under the same heading. 4. From any directory, enter the following command to remove the driver:
pkgrm bfa
5. Respond to the prompt Do you want to remove this package? by entering y. 6. Respond to the prompt 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.
NOTE
Root access is required to remove the package.
42
Upgrading driver on Solaris systems

To update the driver package, simply install the new driver and HCM package using steps under Installing driver on Solaris systems on page 41. When upgrading the driver for Solaris systems, you must reboot the host system. The new driver is not effective until after system reboot.
NOTE
VMware systems
Use the following steps to install, remove, and upgrade the driver package on VMware 3.5 systems.
Installing driver on VMware systems

Install the driver as a BFA package. Refer to Software installation packages on page 9 for a description of host systems that this VMware driver package supports. 1. Copy VMware-bfa-bcu.tar.gz to the you systems /tmp directory. 2. Untar the file using the following command:
# tar zxf bfa_driver_esx35_<version>.tar.gz
3. Install the package using the following installation script:

# sh vmw-drv-install.sh
4. Reboot the system. 5. Verify if the driver package is loaded to the system with the following commands:
vmkload_mod -l
This lists installed driver names, R/O and R/W addresses, and if the ID loaded. Verify that an entry for bfa exists and that the ID loaded.
cat /proc/vmware/version
This displays the latest versions of installed drivers. Look for a bfa entry and related build number. 6. Start the HCM Agent by using steps under Modifying HCM Agent operation on page 44.
NOTE
7.
Manually installing the driver package does not automatically start the HCM Agent. When the driver is installed and host is connected to the fabric (refer to Connecting the HBA to the fabric on page 20) observe HBA LED operation. Verify proper LED operation by referring to LED operation on page 90.
Removing driver from VMware systems

Use the following steps to remove the VMware driver package. 1. Log on to your system. 2. Verify if the driver package is loaded to the system with the following command:
rpm -qa|grep bfa
43
Modifying HCM Agent operation
3. Determine if the HCM Agent is running using procedures under Modifying HCM Agent operation on page 44. If it is, stop the agent using steps under the same heading. 4. Remove the RPM using the rpm -e command and exact RPM package name displayed during step 2. Following is an example:
rpm -e VMware-esx-drivers-scsi-bfa-1.0.0-00000.i386.rpm
5. Reboot the system.
Upgrading driver on VMware systems

To update the driver package, simply install the new driver using steps under Installing driver on VMware systems on page 43.
NOTE
When upgrading the driver for VMware systems, you must reboot the host system. The new driver is effective after system reboot.

This section provides procedures for the following:
Verifying that the HCM Agent is running Starting the agent Stopping the agent Changing the agents default communication port
The HCM Agent will not start automatically if it stops unexpectedly during operation. You must restart the agent.
NOTE
Linux and VMware systems

Use the following options:
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
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
44
Changing the default communication port:

a. b. Change to the agent installation directory (default is /opt/hbaagent/conf). Edit abyss.conf to change the entry SecurePort 34568 to any other nonconflicting TCP/IP port (for example, SecurePort 4430).
Solaris systems
Determine agent operation

/lib/svc/method/hcmagentservice status
/lib/svc/method/hcmagentservice start

svcadm enable hcmagentservice
Stopping the agent

/lib/svc/method/hcmagentservice stop

svcadm disable hcmagentservice

a. b. Change to the agent installation directory (default is /opt/hbaagent/conf). Edit abyss.conf to change the entry SecurePort 34568 to any other nonconflicting TCP/IP port (for example, SecurePort 4430).
Windows systems
Determine agent operation

a. b. a. b. a. b. c. d. Run the services.msc command to display the Services window. Right-click Brocade HCM Agent Service and select Status. Run the services.msc command to display the Services window. Right-click Brocade HCM Agent Service and select Start. Run the services.msc command to display the Services window. Right-click Brocade HCM Agent Service and select Start. Right-click Brocade HCM Agent Service and select Properties. Select the Automatic option in Startup type.
45
Replacing an HBA
e. a. b. a. b. c. d. e. a. b.
Click OK. Run the services.msc command to display the Services window. Right-click Brocade HCM Agent Service and select Stop. Run the services.msc command to display the Services window. Right-click Brocade HCM Agent Service and select Stop. Right-click Brocade HCM Agent Service and select Properties. Select the Manual option in Startup type. Click OK. Change to the agent installation directory (default is c:\Program files\BROCADE\FCHBA\hbaagent\conf). Edit abyss.conf to change the entry SecurePort 34568 to any other nonconflicting TCP/IP port (for example, SecurePort 4430).
Stopping the agent
Replacing an HBA
If you are replacing an HBA, 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 HBA. Refer to documentation provided with your system to locate PCIe slots and cover removal procedures. 4. Unlatch the mounting bracket for the installed HBA or remove the screw (if applicable) securing it to the case. 5. Pull the HBA gently from PCIe connectors. 6. Install the new HBA following steps under HBA hardware installation on page 17. All configuration settings for the old HBA in the slot will automatically apply to the new HBA.
46
Chapter
In this chapter
Verifying HBA installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting installation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirming driver package installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Support Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47 48 52 54
This chapter provides a quick overview of common problems related to HBA installation and configuration that may occur after installing the HBA. Basic solutions are also provided. For more advanced troubleshooting, refer to the Brocade Fibre Channel HBA Troubleshooting Guide.
Verifying HBA installation

Following is a list of items to verify during and after installation to avoid possible problems. Verify the following and make corrections as necessary: 1. Make sure that the HBA is correctly installed and seated in host slot connector. Press firmly down on the top of the HBA to make sure it has snapped in place in the connector. Check your system hardware manual and Hardware and software compatibility on page 7 to verify that you installed the HBA in the correct slot. 2. Verify that all small form factor pluggable (SFP) optic receivers are correctly installed, seated, and latched in HBA SFP receiver slots. 3. Verify that all fiber optic cables are properly connected to the appropriate HBA port and seated in the SFP connector. 4. If configuration options apply to a specific HBA slot, make sure the correct options are configured for the slot where the HBA is installed, 5. Be sure that the correct driver package for the host operating system and platform is properly installed. 6. If the host system requires special configuration to enable HBAs, bus master slots, and interrupt request (IRQ) levels, verify these options in the system BIOS menu and in your system documentation. 7. Make sure that all attached Fibre Channel devices are powered up before you reboot the host. If not powered up, devices will be unavailable.
47

This section provides a summary common HBA problems that may occur during or immediately after installing HBAs and methods to resolve these problems.
Verifying installation
Problems with HBA operation may be due to improper hardware or software installation, incompatibility between the HBA and your host system, unsupported SFPs installed on the HBA, improper fiber optic cable connected to the fabric, or the HBA not operating within specifications. Determine if problems may exist because of these factors by reviewing your installation with information located in the following chapters in this manual.
TABLE 6
Information
Installation and Reference Manual references

Chapter
HBA product overview HBA product overview Installation Specifications
Hardware and software compatibility information. Software installation packages supported by host operating system and platforms. Hardware and software installation instructions. Product specifications.
Errors installing source-based Linux drivers

If you are installing the bfa_driver_linux--<version>.noarch.rpm package, the driver module compiles on the system during installation. If driver build errors result when you install the package, verify that the appropriate distribution kernel development packages are installed on your host system for the currently running kernel. These should include the gcc compiler and the kernel sources. If these are not installed, you may need to reinstall the operating system before continuing installation. Be sure to install everything including the developer library options.
Files needed for bfad.sys message appears when removing driver

When removing the driver with Device Manager or using the Brocade Software Uninstaller, program a message appears asking for Files needed for bfad.sys to complete the installation. This occurs if you perform the following sequence of steps: 1. Install the driver using the driver installer program (bfa_installer.exe) or Brocade Software Installer (GUI or command-based application). 2. Uninstall the Brocade HBA using Device Manager. 3. Re-install the driver using the driver installer program (bfa_installer.exe) or Brocade Software Installer (GUI or command-based application). 4. Uninstall the driver using the driver installer program (bfa_installer.exe). To avoid this problem, do not uninstall the driver using the Device Manager if you have used the Brocade installer programs to install driver instances. Always use the Brocade installer programs to remove the driver. If only one driver is present in the system, then the Brocade programs also remove the Fibre Channel devices from the Device Manager.
48
Cannot roll back driver on all HBA instances using Device Manager
When using the Windows Device Manager, you can only roll back the driver for the first HBA instance. This occurs if you perform the following sequence of steps: 1. Install the driver using the Brocade driver installer program (bfa_installer.exe) or Software Installer (GUI or command-based application). 2. Roll back driver HBA instances using Device Manager. To avoid this problem, use one of the following methods:
Install the driver for each HBA instances using the Device Manager, then roll back the driver
using Device Manager.
Use the driver installer program (bfa_installer.exe) or Brocade Software Installer (GUI or
command-based application) to install or upgrade the driver, then use the Brocade Software Uninstaller to roll back drivers on all HBA instances in one-step.
Installer program does not autorun from CD (Windows only)

When installing software from a CD created from the ISO image downloaded from www.brocade.com/hba, and installer program does not autorun, make sure that autorun is enabled on your system. Enable autorun if possible and reinsert CD. Try manually executing the LaunchWinSetup.cmd located on the installation CD.
Host operating system not installing on remote boot

If booting the host from a remote boot device, verify whether boot over SAN configuration is complete and correct. Refer to Boot Code chapter in the Brocade HBA Installation and Reference Manual for instructions.
HBA not recognized by BIOS

Determine whether the platform BIOS recognizes that the HBA is installed by examining system messages and errors. If the BIOS does not recognize the HBA, the following problems may exist:
HBA is not properly seated. Power down the system, then press firmly down on the top of the
HBA to make sure it has snapped into place in the connector.
System PCIe connector has malfunctioned. Try installing the HBA into another PCIe 8x or
greater slot.
Faulty fiber optic cable, cable connections, and HBA SFP transceiver. Disconnect all devices
from the HBA, then reboot the host system. If this fixes the problem, check carefully for faulty fiber optic cable and cable connections attached to the HBA and devices. Reseat SFP transceivers in the HBA. Determine whether the installed SFPs are faulty by observing LED operation by HBA ports. If all LEDs are flashing amber, the SFP is invalid. You can also verify SFP operation by replacing an SFP with an SFP in well-known good operating condition.
49
HBA not recognized by operating system

If the operating system does not recognize the HBA as a PCI device (for example, in Windows, the HBA does not display in Device Manager) the driver may not be properly installed. Verify driver installation using the following host system commands:
lspci (Linux/VMware)
This is a utility that displays information about all PCI buses in the system and devices connected to these buses. Entering lspci -vvn provides verbose output and displays vendor and device codes.
prtconf (Solaris)
This prints the system configuration, including configuration of system peripherals displayed as a device tree. Use prtconf -v for verbose mode.
Device Manager (Windows).

The HBA should display under SCSI and RAID Controllers. If the driver is not installed, try reinstalling it.
Host system freezes or crashes

If the BIOS and the operating system recognize the HBA, but the host system freezes or crashes during startup and does not boot, disconnect all devices from the HBA, then reboot the host system.
If the system does not freeze when rebooted and operates correctly, use the following
information to resolve the problem:
Check for faulty fiber optic cable and cable connections. Try rebooting the system without any connectivity to the switch. This will help isolate any hang caused by switch and device interactions. Reseat SFPs in the HBA. Determine whether the installed SFPs are faulty by observing LED operation by HBA ports. If all LEDs are flashing amber, the SFP is invalid and may not be a required Brocade model. You can also verify SFP operation by replacing them with SFPs in known operating condition. If the problem is resolved after replacement, original SFP is faulty. Check for conflicts with attached devices. Verify that data speed (1-8 Gbps) and connection topology (for example, point-to-point) for devices attached to the HBA are compatible with settings on the HBA port. Although auto may be set, configuring settings manually on the HBA port and devices may allow connection. Also, note that the HBA only supports point-to-point connection topology. Refer to the Brocade Fibre Channel HBA Administrators Guide for procedures to configure HBA ports.
NOTE
Observe the LEDs by HBA ports. Illuminated LEDs indicate connection, link activity, and connection speed negotiated with the attached device. Refer to LED Operation in the Specifications chapter of the Brocade Fibre Channel HBA Installation and Reference Manual.
50
If the system freezes perform the following tasks: - Verify if the host system firmware supports PCIe specifications listed in the Hardware and
Software Compatibility section, Introduction chapter, of the Brocade Fibre Channel HBA Installation and Reference Manual. If not, download a firmware update to support the HBA.
On Windows systems, determine when the system freezes during the boot process. If it freezes as the driver loads, uninstall and reinstall the driver. If it freezes during hardware recognition, uninstall both the driver and HBA, then reinstall both. Remove the HBA and reboot the system. If the system boots, reinstall the HBA. Reseat the HBA Uninstall and reinstall the driver Try installing the HBA into another host system. If the problem does not occur, the HBA may not be compatible with the original host system. If the problem occurs in the new system, replace the HBA.
Storage devices not recognized by host system

If attached devices are not available to the host, use the following information to resolve the problem:
Verify that devices are powered on. Verify that there are no configuration conflicts between attached device and HBA port. Verify
that the data speed (1-8 Gbps) and connection topology for devices attached to the HBA are compatible with settings on the HBA port. Although auto may be set, configuring settings manually on the HBA port and devices may allow connection. Also, note that the HBA does not support fabric loop or direct connection topology. Refer to the Brocade Fibre Channel HBA Administrators Guide for procedures to configure HBA ports.
NOTE
Observe the LEDs by HBA ports. Illuminated LEDs indicate connection, link activity, and connection speed negotiated with the attached device. Refer to LED Operation in the Specifications chapter of the Brocade Fibre Channel HBA Installation and Reference Manual.
Check for faulty fiber optic cable and cable connections at the HBA, switch, and attached
devices.
Reseat SFPs in the HBA. Determine if the installed SFPs are faulty by observing LED operation
by HBA ports. You can also verify SFP operation by replacing the SFP with an SFP in known operating condition.
Disconnect all devices, then reconnect one at a time until problem occurs. This can help you
isolate a problem device or cable.
Verify the zoning configuration on the switch is correct so that the host can reach and identify
storage.
51
Confirming driver package installation

HBA driver packages from Brocade contain the current driver, firmware, and HCM agent for specific operating systems. Make sure that the correct package is installed for your operating system. Refer to the installation chapter in the Brocade HBA Installation and Reference Manual. 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 hosts device manager.
Improper or erratic behavior of HCM (installed driver package may not support HCM version). Host operating system not recognizing HBA installation. Operating system errors (blue screen).
If driver is not installed, try re-installing the driver or re-installing the HBA hardware and then the driver. You can use HCM and tools available through your hosts operating system to obtain information such as driver name, driver version, HBA WWN, and HBA port WWNs.
NOTE
Host Connectivity Manager (HCM)

Use the following steps to display the HBA WWN, driver name and version, firmware name and version, and the BIOS version currently in operation 1. Launch HCM. 2. Select the HBA in the device tree. 3. Select the Properties tab in the right pane to display the Properties dialog box. The dialog box displays HBA properties.
Windows
You can use two methods to determine driver installation, depending on your Windows installation: the Driver Verifier and Device Manager. Driver Verifier Manager Verify whether the HBA driver (bfa driver) is loaded using 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.
52
Device Manager Verify if the driver is installed and Windows is recognizing the HBA using the following steps. 1. Open the Device Manager. 2. Expand the list of SCSI and RAID controllers. 3. Right-click Brocade Fibre Channel Adapter. If you do not see this entry or Fibre Channel Controller displays with a yellow question mark under Other Devices, the driver is not installed. 4. Select Properties to display the Properties dialog box. 5. 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 HBA hardware and then the driver.
Linux
Verify if the HBA driver installed successfully using the following commands:
# rpm -qa|grep -i bfa
This command prints the names of the Brocade HBA driver package (bfa) if installed.
# lspci
This is a utility that displays information about all PCI buses in the system and all devices connected to them.
# lsmod
This command displays information about all loaded modules. If bfa appears in the list, the HBA driver is loaded to the system.
# dmesg
This command prints kernal boot messages. For the bfa entry, HBA model and driver version should display if the hardware and driver are installed successfully.
# modprobe -l bfa
This verifies that the module has loaded. If bfa displays, the module has been loaded to the system.
Solaris
Verify if the HBA driver installed successfully using the following commands.
modinfo|grep bfa
If the driver package is installed, bfa Brocade Fibre Channel Adapter Driver should display.
pkgchk -nv bfa
This checks for and lists the installed HBA driver package files.
pkginfo -l
If the HBA driver package is installed, bfa_pkg should display with a complete install status in the list of installed packages.
53
Using Support Save
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 HBA driver installed successfully using the following commands:
vmkload_mod -l
This lists installed driver names, R/O and R/W addresses, and if the ID loaded. Verify that an entry for bfa exists and that the ID loaded.
cat /proc/vmware/version
This displays the latest versions of installed drivers. Look for a bfa entry and related build number.
Using Support Save

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 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. Through BCU, enter the bfa_supportsave command. Through your internet browser (Internet Explorer 6 or later or Firefox 2.0 or later), you can
collect bfa_supportsave output if you do not have root access, do not have access to file transfer methods such as FTP and SCP, or do not have access to the Host Configuration Manager (HCM). A bfa_supportsave collection can also occur automatically for a port crash event. The Support Save feature saves the following information:
NOTE
HBA model and serial number. HBA firmware version. Host model and hardware revision. All support information. HBA configuration data. All operating system and HBA information needed to diagnose field issues Information about all HBAs in the system. Firmware and driver traces. Syslog message logs.
54
Using Support Save
Windows System Event log .evt file. HCM GUI-related engineering logs Events HBA configuration data Environment information Data.xml file Vital CPU, memory, network resources HCM Agent (logs, configuration) Driver logs (bfa_supportsave output) Core files
Master and Application logs are saved when Support Save is initiated through HCM, but not through BCU.
NOTE
Initiating Support Save through HCM

Initiate 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 backup data and configuration files manually. For more information and additional options for using this feature, refer to the Brocade Fibre Channel HBA Administrators Guide.
Initiating Support Save through BCU commands

Use the bfa_supportsave command to Initiate Support Save through the BCU:
bfa_supportsave {output_dir]
where: [output_dir] An optional parameter that specifies the directory where you want output saved. If not specified, output is saved as a directory in the current working directory as bfa_ss_out.
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 feature, refer to the Host Connectivity Manager (HCM) Administrators Guide.
55
Using 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
where 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 bfa_supportsave file.
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 only driver-related logs and configuration files.
Browser
Collects driver-related and HCM Agent logs and configuration files.
HCM
Collects, HCM, driver-related, and HCM Agent logs and configuration files.
bfa_supportsave collection on 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.
56
Chapter
HBA boot code
In this chapter
Boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating boot code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fabric based boot LUN discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Booting systems without operating system or local drive. . . . . . . . . . . . . . .
NOTE
57 59 62 82 83
Please refer to the current release notes on the Brocade HBA website (www.brocade.com\HBA) for changes to boot support and procedures detailed in this chapter.
Boot support
The HBA supports the following system BIOS and platforms:
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 A single, updatable boot code image, stored in the HBA option read-only memory (option ROM) memory, contains all boot code for supported host platforms. By default, BIOS and UEFI are enabled on HBA ports for booting over SAN.
NOTE
57
Boot support
Brocade BIOS support

The Brocade HBA boot BIOS provides boot support for the Brocade HBAs 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 HBA ports. When HBA BIOS is enabled, the boot code loads from HBA 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 hosts operating system and HBA driver. The process for booting from these locations 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 62.
NOTE
You can enable or disable BIOS for boot over SAN, set port speed, and display HBA BIOS settings using BCU commands. By default, BIOS is enabled on all HBA 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: - 1 Gbps, 2 Gbps, 4 Gbps, and Auto for 415 and 425 HBA models - 2 Gbps, 4 Gbps, 8 Gbps, and Auto for 815 and 825 HBA models. Select a boot device from discovered targets. Enable one of the following boot LUN options: - Auto Discover. 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 82).
NOTE
Flash Values. The HBA will obtain the boot LUN information from flash memory. First LUN. The host boots from the first LUN visible to the HBA that is discovered in the fabric.
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 62.
58
Updating boot code
Brocade UEFI support

Unified Extensible Firmware Interface (UEFI) boot code for Brocade HBAs 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 HBA ports. The UEFI boot code loads from Brocade HBA 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 HBA 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 62. After the Brocade UEFI boot code integrates with the system UEFI during system boot, use configuration options in the UEFI drvcfg command to perform the following tasks. Configuration values are stored in HBA memory.
Enable or disable the HBA 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 hosts Boot Configuration menu as boot devices.
Set the port speed: - 1 Gbps, 2 Gbps, 4 Gbps, and Auto Select for 415 and 425 HBA models - 2 Gbps, 4 Gbps, 8 Gbps, and Auto Select for 815 and 825 HBA models.
For general information and configuration procedures for booting over SAN, refer to Configuring boot over SAN on page 62.
Updating boot code

Download the latest boot code file for installed Brocade HBAs from the Brocade HBA website (www.brocade.com/hba). On the website, select your hosts operating system in the Operating Systems list to display the appropriate download screen, then select the Boot Code area. Upload the boot code to the HBA installed on your host system using the Host Connectivity Manager (HCM) and BCU commands. Although BCU uploads the file from the hosts local drive, you can use HCM to upload from a remote system.
NOTE
All Brocade HBAs installed in a host system must use the same boot code version. You can determine the current BIOS version installed on your HBA 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 HBA Configuration Utility.
Entering the bcu adapter --query command. The installed BIOS version displays in the Flash
Information section of the command output.
Viewing the HBA Properties panel in HCM. To view the panel, select the HBA in the device tree,
then click the Properties tab in the right pane.
59
Updating boot code
Using HCM
Follow these steps to upgrade HBA flash memory with the latest boot code: 1. Download the boot code (bfa_boot_fw) from www.brocade.com/hba to a folder on your local drive. 2. Launch HCM. 3. Right-click a host or HBA in the device tree window and select Upload Boot Code Image from the list.
Right-clicking a host uploads the boot code image to all installed HBAs installed in the
host.
Right-clicking an HBA uploads the boot code image to the selected HBA only.
4. When the Boot Code Image Upload dialog box displays, browse to the boot code image that you downloaded in step 1. 5. Select the boot code file and click Open to upload.
Using BCU
1. Download the boot code image (bfa_boot_fw) from www.brocade.com/hba to a folder on your local drive. 2. Enter the following BCU command:
bcu boot --upload <adapter id> <image file> -a
where <ad_id> <image file> -a ID of the adapter (HBA) name of firmware image file. Indicates that the boot code should be uploaded to all installed Brocade HBAs found on the host. Note that the adapter id should not be specified if Introduction to boot over SAN
The Boot Over SAN feature allows a host to boot its operating system from a boot device located somewhere on the SAN instead of the hosts local disk or direct attached storage. 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. For more information on how the Brocade Boot BIOS functions to implement this feature, refer to Brocade BIOS support on page 58. Booting from a remote SAN location provides the obvious advantage of recovering quickly from a host or HBA malfunction. With the HBA 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 HBA from the old host into the new one with the same configuration, then booting the new host. The hosts 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 HBA, 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.
60
Updating boot code
If replacing the Brocade HBA in a host with a similar Brocade HBA, you will need to reconfigure
the HBA and storage to boot from the appropriate remote boot device. You must also update access on storage device ports to reflect the new HBAs PWWN. Finally, you must update the single-initiator target zone created for the HBA port and storage device port with the new HBA PWWN.
If replacing a host with a different model, you may be prompted to install the HBA driver for the
existing HBA. 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.
General host and storage system requirements

This section describes general requirements for the host system (server) and storage systems when configuring boot over SAN. 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.
Host system
Consider these requirements for your host system:
You may need to disconnect internal IDE hard drives to disable them in the system BIOS and
allow the HBA 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 CD-ROM, diskette, then Fibre Channel drive must be the boot order. After the
operating system installs, you can change this order if desired.
Boot over SAN is not supported on Solaris systems.
Storage system
Consider these requirements for your storage system:
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 HBA and storage are working properly before attempting a boot over SAN.
61
Configuring boot over SAN
The boot LUN must contain the appropriate operating system for the host and the HBA driver.
Refer toInstalling operating system and driver on boot LUNs on page 73 for details. Also, 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 HBA port has exclusive access to the LUN.
Accomplish this by binding an HBA port PWWN to a LUN. You can easily find an HBA port PWWN using the Brocade BIOS Configuration Utility (refer to Configuring BIOS using the Brocade configuration utility on page 63). 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.
Only one path to the boot LUN must be visible to the operating system during the hosts 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 HBA port world wide name (PWWN) and the target PWWN
to keep RCSN interruptions from other hosts to a minimum.
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.

You must configure boot over SAN on the HBA, as well as the storage device. This section provides complete procedures to configure the HBA to boot from a SAN device. References are provided in these steps to more specific procedures as required to complete the configuration on the storage device and in the fabric. These steps assume that the HBA and driver are installed on the host. 1. Verify that the HBAs contain the latest boot code and driver. You can use HCM or BCU commands. For HCM, perform the following steps. a. b. Select an HBA in the device tree. Click the Properties tab in the right pane. The HBA Properties panel displays. For BCU, enter the following command:
bcu adapter --query <adapter_id>
The installed BIOS version displays in the Flash Information section. 2. If the latest HBA BIOS and driver package are not installed, download the latest boot code and driver package from www.brocade.com/hba and upgrade your HBA and host system. Refer to the following instructions:
Driver package.
Manual installation, removal, and upgrade of driver packages on page 34.
BIOS.
Updating boot code on page 59.
62
3. Use your host systems boot menu to enable the system to boot from the CD/DVD, diskette, and then the appropriate HBA. If multiple HBAs are installed on your system, be sure to configure the system to boot from the appropriate HBA first in the boot order. Booting from the CD/DVD and diskette first allows you to install the host operating system and HBA 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 HBA in your system boot menu, or you may need to disable the hosts hard drive to boot from the HBA.
NOTE
If you need to disable the systems hard drive to allow booting from the HBA and wish to utilize both the boot from SAN feature and your systems hard drive, refer to your system documentation. Procedures for this configuration are beyond the scope of this publication. 4. 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 hosts operating system. 5. Determine which HBA port you want to use for booting from SAN and note its PWWN. To determine the PWWN for an installed HBA port, refer to Port World-Wide Port Name (PWWN) on page xiii. To find the PWWN for the port using the Brocade BIOS Configuration Utility, refer to Configuring BIOS using the Brocade configuration utility on page 63. 6. Using an appropriate storage management or configuration utility, bind the HBA ports PWWN to the selected LUN. 7. Create a new single-initiator target zone in the SAN fabric where the HBA 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 HBA port. Refer to the Brocade Fabric OS Administrators Guide for zoning procedures.
8. For BIOS systems, enable the HBA and boot devices for booting over SAN using the following sections of this chapter as appropriate:
Configuring BIOS using the Brocade configuration utility on page 63 Configuring BIOS using HCM and BCU on page 69
9. For UEFI systems, enable the HBA and boot devices for booting over SAN using instructions under Configuring UEFI on page 71. 10. Configure the LUN for booting your host system. Refer to procedures required by your host platform and operating system. 11. Install the hosts operating system and HBA driver on the boot LUN. The boot image consists of the HBA driver, host operating system, and other necessary files to allow the host to boot from the boot device. Refer to Installing operating system and driver on boot LUNs on page 73. 12. Boot the host from the SAN storage boot device using procedures required by your host system.
Configuring BIOS using the Brocade configuration utility

NOTE
Brocade BIOS configuration utility and Brocade BIOS configuration menu are used interchangeably in this manual.
63
The Brocade BIOS Configuration Utility allows you to perform the following operations on selected HBAs:
Enable or disable BIOS to support boot over SAN. - You must enable BIOS to support boot over SAN for an HBA port. If disabled, the host
system cannot boot from Fibre Channel disk drives.
The default setting for the HBA boot BIOS is enabled on all HBA ports.
Enable one of the following Boot Options: - Auto Discover

Host boots from LUN information provided by the fabric.
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 HBA. Select boot LUNs from discovered targets. Review HBA properties, such as the following: - Port speed - PWWN - NWNN - BIOS version
1. Power on the host system. 2. When you are prompted to enter the Brocade BIOS configuration menu, press Alt+B or Ctrl+B The Brocade BIOS Configuration Menu displays a list of installed HBA ports, similar to the following.
64
Under the HBA No column, 1/0 and 1/1 are the first port and second port respectively on the first installed HBA while 2/0 and 2/1 are the first and second port on the second installed HBA. A maximum of 8 ports can display on a screen. Select Page Up to go to a previous screen or Page Down to go to the next screen. 3. Select a port that you want to configure. A screen similar to the following displays.
4. Select one of the following:
Adapter Settings. Use the Adapter Settings screen to enable BIOS, HBA port speed, and
auto discovery of boot LUN information on the fabric. You can determine HBA WWWN 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 ports current BIOS version, NWWN, and PWPN. Table 7 on page 66 explains options available for BIOS, Port Speed, and Boot LUN settings.
65
TABLE 7
Field BIOS
Brocade BIOS Configuration Utility field descriptions

Description The value of BIOS must be Enable for the selected HBA 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 HBA port: NOTE: The default setting for all HBA ports is enabled.
Port Speed
Set the speed for HBA port. Set Auto, 2, 4, and 8 for 815 and 825 HBAs. Set Auto, 1, 2, and 4 for 415 and 425 HBAs. Auto allows HBA the port to automatically negotiate link speed with the connected port.
Boot LUN
Auto Discover. When enabled, LUN information, such as the location of boot LUN, is provided by the fabric (refer to Fabric based boot LUN discovery on page 35). 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 HBA that is discovered in the fabric.
BIOS Version PWWN NWWN
Displays the Brocades BIOS boot code version installed on the card. Displays the ports unique Port World Wide Name. Displays the ports Node World Wide Name.
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.
66
Enter - select a field and configure values. Left and Right arrow keys - change a value. Alt - S - save configuration values to HBA flash memory. Alt - Q - Exit the utility. Esc - go back a screen. Page Up or Page Down - go to preceding or next screen.
NOTE
7.
To restore factory default settings, press R. To configure boot devices, select Boot Device Settings from the initial menu screen for the HBA 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.
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.
67
9. Select a target from 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 HBA.
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 HBA port using the storage systems management or configuration utility (refer to step 6 under Configuring boot over SAN on page 62).
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.
68
11. Press Enter. The selected device will be added to the list of boot devices for the HBA.
12. Save or exit the configuration utility.
ATTENTION
Press the Alt and S keys to save the configuration or Alt and Q keys to exit without saving.
Configuring BIOS using HCM and BCU

You can enable or disable BIOS for booting over the SAN, set HBA port speed, display BIOS configuration parameters, select boot LUNs, and enable auto discovery using HCM dialog box options and BCU commands, You can only designate bootable devices (LUNs) using the Boot Device Settings feature of the Brocade BIOS Configuration Utility,
NOTE
Using HCM
Use the Boot-over-SAN tab on the Basic Port Configuration dialog box in HCM to perform the following tasks:
Enable or disable BIOS.

You must enable BIOS to support boot over SAN for an HBA port. If disabled, the host system cannot boot from Fibre Channel disk drives. The default setting for the HBA boot BIOS is enabled.
Set port speed for HBA ports. - Set Auto Negotiate, 2, 4, and 8 for 815 and 825 HBAs. - Set Auto Negotiate, 1, 2, and 4 for 415 and 425 HBAs.
Auto Negotiate allows HBA port to automatically negotiate link speed with the connected port.
69
Enable one of the following boot options: - Auto Discovered from Fabric
When enabled, the boot LUN identification is provided by the fabric (refer to Fabric based boot LUN discovery on page 35).
First Visible LUN The host boots from the first LUN visible to the HBA that is discovered in the fabric. User Configured LUNs. This table displays LUNs visible to the HBA. If you select this option, Up to four boot LUNs can be configured as boot devices. If you select this option, the system will attempt to boot the first LUN in the table, then each succeeding LUN in order. 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 HBA 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.
All configuration values are stored to HBA 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 Configuration chapter of the Brocade Fibre Channel HBA Administrators Guide.
Using BCU commands

Use the BCU commands to perform the following tasks:
Enable BIOS, set port speed, and configure boot LUN information.
You must enable BIOS to support boot over SAN for an HBA port. If disabled, the host system cannot boot from Fibre Channel disk drives. The default setting for the HBA boot BIOS is enabled. BIOS must be enabled on only one adapter port per host in order to boot from SAN. Use the following BCU command to enable BIOS, set port speed (if required), and configure target PWWN and LUN values.
bios --enable <port_id> [-s <speed>][-o <auto|flash|firstlun>[-p pos][-b pwwn,lun*]
where: port_id Specifies the ID of the port for which you want to set the ports boot from SAN attributes. This could be the adapter_id/port_id, port PWWN, port name, or port hardware path. Specifies the speed for the port as 2, 4, 8, or auto for 815 and 825 HBAs and 1, 2, 4, and auto for 415 and 425 HBAs. Default is autonegotiate. Begins options for obtaining boot LUN information (auto, flash, firstlun). Enables auto discovery. When enabled, the boot LUN identification is provided by the fabric. Refer to Fabric based boot LUN discovery on page 82 for more information.
-s <speed> - o: auto
70
flash
Boot LUN information is obtained from flash memory. Note that values are saved to flash when you configure them and save through the BIOS Configuration Utility, HCM, and BCU. The host boots from the first LUN visible to the HBA that is discovered in the fabric. 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. The host boots from the LUN information defined by the target PWWN and LUN value (lun*). Note: Specify pwwn as a colon-separated value and LUN ID as a decimal number. Note: The LUN must be the same LUN that you bound to the HBA port using the storage systems management or configuration utility (refer to step 6 under Configuring boot over SAN on page 62).
firstlun -p pos
-b pwwn,lun*
Disable BIOS and boot over SAN support for an HBA port using the following command:
bios --disable <port_id>
Display BIOS settings, current port speed, and boot LUN information for the selected port using
the following command:
bios --query <port_id>
where: port_id Specifies the ID of the port for which you want to set the ports interrupt attributes.
All configuration values are stored to HBA flash memory.
NOTE
For details on using BCU commands, refer to instructions for enabling boot over SAN using the BCU in the Configuration chapter of the Brocade HBA Administrators Guide.
Configuring UEFI
Use EFI shell commands to configure an UEFI system to boot over SAN. You can configure the following values, which are stored in HBA flash memory. You can use the drvcfg shell command to configure the following values:
Enable or disable the HBA 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 in the Boot Configuration menu as boot devices.
Set the port speed: - 1 Gbps, 2 Gbps, 4 Gbps, and Auto Select for 415 and 425 HBA models - 2 Gbps, 4 Gbps, 8 Gbps, and Auto Select for 815 and 825 HBA models.
71
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 for the Brocade Fibre Channel Adapter. In the following example, the Brocade HBA has a driver handle of 25.
D R V VERSION T D Y C I P F A E G G #D #C DRIVER NAME 2
IMAGE NAME
------------------------------------------------------------------------------------------------25 0000000A D X - Brocade Fibre Channel Adapter Bus D PciROM:03:00:00:003
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 HBA 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 HBA.
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 HBA port using the drvcfg -s 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 HBA ports, enter the following:
drvcfg -s 25 27
NOTE
The -s option for drvcfg provides prompts for setting HBA options. You can use the -v option (drvcfg -v 25 27) to check that options currently set on the HBA are valid. When you are prompted to enable the HBA port, press the Y or N key to enable or disable the port. When prompted, enter a port speed. To terminate and not save values that you have selected, press Esc.
a. b. c.
72
Following is example output from the command using drive handle 25 and controller handle 27.
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 HBA are valid. For example, enter drvcfg -v 29 3F.
NOTE
You could configure the other HBA 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 systems map output. Note that you can also enter the following EFI shell command to list all storage targets and LUNs visible to the HBA port. SAN drives display with Fibre as part of the device name.
dh -d [controller handle]
8. Refer to procedures for your systems Boot Configuration menu to verify that your host is configured to automatically boot from the target remote LUN. 9. Refer to instructions under Installing operating system and driver on boot LUNs on page 73 to install the hosts operating system and HBA driver to the LUN
Installing operating system and driver on boot LUNs

Use the following procedures in this section to install the hosts operating system, HBA driver, and other necessary files on an unformatted LUN that you have selected for booting the host system.
Windows Server 2003 on page 74 Windows Server 2008 on page 75 Linux (RHEL) on page 76 Linux (SLES 9) on page 78 Linux (SLES 10 and later) on page 78 VMware on page 79
Before using these procedures, be sure you have bound the PWWN of the appropriate HBA 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 62, Configuring BIOS using the Brocade configuration utility on page 63, and Configuring UEFI on page 71 for instructions.
73
Windows Server 2003

Use the following steps to install Windows Server 2003 and the HBA driver on an unformatted Fibre Channel disk connected to the HBA that you that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
Configuring BIOS using the Brocade configuration utility on page 63 on page 55. Configuring BIOS using HCM and BCU on page 69 on page 62. Configuring UEFI on page 71.
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 2003 installation. Refer to your operating system documentation for details. The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Power up your host system. 2. Download the appropriate Windows 2003 HBA driver update disk (dud) .zip file for your host platform from the Brocade HBA website at www.brocade.com/hba. Driver update disk files are provided for x86, x64, and Itanium IA-64 systems. Refer to Boot installation packages on page 15 for a list of driver update disk files. 3. Unzip the file and copy to a formatted diskette to create the HBA driver update disk. 4. Insert the Windows 2003 operating system installation media into the 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
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 devices(s): S=Specify Additional Device ENTER=continue F3=Exit. 6. Select S to specify additional devices.
NOTE
You must load the Brocade HBA driver by selecting S and using the following steps so that the system can access the boot LUN for Windows 2003 Server installation.
74
7.
When a message displays to insert the disk labeled manufacturer-supplied hardware support disk, insert the Brocade HBA driver update disk that you created in step 3 and press Enter. A list of devices displays.
8. Select Brocade's HBA 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 when the Brocade BIOS or UEFI installs successfully. System boot setup screens should also display a hard drive entry containing the Brocade HBA, boot LUN number, and target storage device.
Windows Server 2008

Use the following steps to install Windows Server 2008 and the HBA driver on an unformatted Fibre Channel disk that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
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
The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Power up your host system. 2. Download the appropriate Windows 2008 HBA driver update disk (dud) .zip file for your host platform from the Brocade HBA website at www.brocade.com/hba. Driver update disk files are provided for x86, x64, and Itanium IA-64 systems. Refer to Boot installation packages on page 15 for a list of driver update disk files. 3. Unzip the file and copy to a USB drive, CD, or formatted floppy diskette to create the HBA driver update disk. 4. Insert the Windows 2008 operating system installation DVD into the system drive and boot from the DVD.
75
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 HBA 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 HBA driver update files that you created in step 3. 9. Select Browse on the Load Driver dialog box and select the HBA 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 HBA models will display on the Select the drive to be installed screen. If not selected, drivers for all HBA models display. 11. Select the driver for the HBA 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 HBA 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 HBA 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 when the Brocade BIOS or UEFI installs successfully. System boot setup screens should also display a hard drive entry containing the Brocade HBA, boot LUN number, and target storage device.
Linux (RHEL)
Use the following steps to install RHEL 4, RHEL 5, and later, and the HBA driver on an unformatted Fibre Channel disk that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
Configuring BIOS using the Brocade configuration utility on page 63 on page 55.
76
Configuring BIOS using HCM and BCU on page 69 on page 62. Configuring UEFI on page 71.
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. The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Download the Brocade HBA driver update disk (dud) ISO file from the Brocade HBA website at www.brocade.com/hba that is appropriate for RHEL 4, RHEL5, and later. Refer to Boot installation packages on page 15 for a list of driver update disk files. 2. Create a driver update disk CD from the ISO image. 3. Insert the Linux Red Hat product CD #1 in the CD drive and boot the system. 4. At the boot prompt enter the following command:
linux dd
NOTE
5. 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 HBA driver at this stage so that the system can access the boot LUN for Linux installation. 6. From the Driver Disk Source window, select the driver source hdx (where x is the CD drive letter), then press Enter. The Insert Driver Disk window displays. 7. Insert the driver update disk that you created in step 2 into the CD or DVD drive. The driver loads automatically. 9. When the Disk Driver window displays prompting for more drivers to install, select No, then press Enter. 10. Insert the Linux Red Hat product CD #1 in the CD drive (remove the HBA driver update CD first if necessary), then press Enter. 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. 8. Select OK, then press Enter.
77
Linux (SLES 9)
Use the following steps to install SLES 9 and the HBA driver on an unformatted Fibre Channel disk that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
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. The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Download the Brocade HBA driver update disk (dud) ISO file appropriate for your Linux system from the Brocade HBA website at www.brocade.com/hba. Refer to Boot installation packages on page 15 for a list of driver update disk files. 2. Create a driver update disk CD from the ISO image. 3. Power up the host system. 4. Insert the SLES product CD #1 into the drive and boot the system. 5. When the main installation screen displays, press F6 to load the driver. A message displays to get your driver update floppy ready. 6. Select the Installation option, then press Enter. A message displays to insert the driver update floppy/CDROM.
NOTE
ATTENTION
You must load the Brocade HBA driver at this stage so that the system can access the boot LUN for Linux installation. 7. Replace the SLES product CD with the driver update disk that you created in step 2.
8. Continue responding to on-screen instructions and refer to your system documentation as necessary to format and complete installation on the target boot LUN.
Linux (SLES 10 and later)

Use the following steps to install SLES 10 and later and the HBA driver on an unformatted Fibre Channel disk that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
78
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. The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Download the Brocade HBA driver update ISO file appropriate for your Linux system from the Brocade HBA website at www.brocade.com/hba. Refer to Boot installation packages on page 15 for a list of these files. 2. Create a driver update disk CD from the ISO image. 3. Insert the SLES product CD #1 into the drive and boot the system. 4. When the main installation screen displays, press F6 to load the driver. The system prompts to select Yes, No, or File. 5. Select Yes. 6. Select the installation option, then press Enter 7. When the Please choose the driver update medium prompt displays, replace the SLES product CD with the SLES driver update disk that you created in step 2.
NOTE
ATTENTION
You must load the Brocade HBA driver at this stage so that the system can access the boot LUN for Linux installation. 8. Select CD drive (hdx) then press Enter. The driver update loads to the system. If the driver update was successful, a Driver Update OK message displays: 9. Press Enter. 10. If the system prompts you to update another driver, select BACK, then press Enter. 11. When the Make sure that CD number 1 message displays, insert the SLES product CD #1 into the drive and select OK. 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. After Windows installs on the remote LUN, the system should automatically reboot from the LUN.
VMware
Use the following steps to install VMware ESX 3.5 and the HBA driver on an unformatted Fibre Channel disk that you that you configured as a bootable device when setting up the HBA BIOS or UEFI on the host system. Reference the following instructions:
Configuring BIOS using the Brocade configuration utility on page 63 on page 55.
79
Configuring BIOS using HCM and BCU on page 69 on page 62. Configuring UEFI on page 71.
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 VMware installation. Refer to your operating system documentation for details. The following procedures load the operating system, HBA driver, and utilities to the designated boot LUN to allow HBA 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 page 81 after completing the following steps. 1. Be sure to reformat the target boot LUN before installing the boot image if the operating system is already installed. 2. Download the ESX server FC driver update ISO image from the Brocade HBA web site (www.brocade.com/hba). Refer to Boot installation packages on page 15 for a list of driver update files. 3. Create a an FC driver CD from the ISO image. This CD will contain the appropriate Linux and VMware drivers for the ESX system.] 4. Insert the FC Driver CD and reboot the system.
NOTE
ATTENTION
You must load the Brocade HBA driver at this stage so that the system can access the boot LUN for VMware installation. 5. When prompted for an upgrade or installation method, select the APIC/graphical mode. 6. When prompted for Installation Options, select Complete ESX Server install, formatting installation hard disks. 7. Select your language and appropriate options for keyboard and mouse customization. When the HBA driver loads successfully, you are prompted to insert the VMware operating system installation CD. 8. Insert the ESX Server CD and follow on-screen prompts to continue installation. 9. When a list of discovered storage targets displays, select the LUN for installation that you configured as a bootable device. 10. Continue responding to on-screen instructions and refer to your system documentation as necessary to format and complete installation on the target boot LUN. For detailed instructions, refer to the ESX Server 3.5 Installation and Upgrade Guide.
80
Installing the full driver package

The preceding procedures for each operating system under Installing operating system and driver on boot LUNs on page 73, do not install the HCM Agent and the full range of Brocade Command Line Utilities. To install the full driver package with HBA agent and all BCU commands, including bfa_supportsave, perform these additional procedures. 1. Compare the version of the full driver package that you wish to install with the version of the driver already installed on the boot LUN. There are a variety of methods to determine the driver version installed on your operating system. Refer to Confirming driver package installation on page 52 for more information. If the versions do not match, you will perform additional procedures to initialize the new package on your system. 2. Install the full driver package using steps for your operating system under HBA software installation on page 21
If the driver that you install and the driver already installed on the LUN match, perform
steps as normal to complete installation. You will be able to use the additional utilities and HCM Agent installed with the full package. For Linux systems, install the latest version of bfa_util_linux-<version>.noarch.rpm using instructions under Installing driver on Linux systems on page 41. This will install all package utilities without updating the driver. You do not need to reboot the system.
If the driver that you install and the driver already installed on the LUN do not match, go on
to step 3. 3. If the version of driver installed on the boot LUN and driver that you are installing do not match, perform these additional steps for your operating system: Windows Reboot the system to initialize the new driver. Linux Driver unloading will fail when the new driver package installs, To make the new driver become effective, perform the following steps: a. b. c. Change to the boot directory
cd /boot
Make a backup of the current RAMDISK image.

#cp initrd-[kernel_version].img initrd-[kernel_version].img.bk
Build RAMDISK image. RHEL

#mkinitrd -f initrd-[kernel_version].img [kernel_version]
SLES
#mk_initrd
d.
Reboot the system to load the new RAMDISK image.
VmWare Reboot the system to initialize the new driver.
81
Fabric based boot LUN discovery
Fabric based boot LUN discovery

This feature allows the hosts boot LUN information to be stored in the fabric zone database using a zone name containing the PWWN of an HBA port and zone members consisting of the storage target PWWN and LUN WWN. The HBA boot code can query the zone member list for the zone name that matches the HBA PWWN to determine the boot target and LUN. This feature is not supported on UEFI systems. To store the information, you must use the Fabric OS zoneCreate command to create a zone on the switch where the HBA is connected. The zonename operand will be BFA_[HBA port WWN]_BLUN. For example, if the HBA PWWN is 01:00:05:1E:01:02:03:04, the zone name will be the following: "BFA_0100051E01020304_BLUN". The member operands must be specially coded values for the target PWWN and LUN identification. To obtain the zoneCreate operand values, you run a command from your host systems command line. This command is loaded to your system as part of the driver package.
NOTE
Configuring fabric-based boot LUN discovery

Use the following steps to configure fabric-based boot LUN discovery. 1. Set the HBAs BIOS configuration to auto discovery using one of the following interfaces:
Brocade BIOS Configuration Utility

Adapter Settings > Boot LUN > Auto Discover
HCM
Basic Port Configuration > Boot-over-SAN > Auto Discovered from Fabric
BCU
bios --enable <port_id> -o auto
2. Enter the following BCU command to provide the zone name and zone members to use as operands in the Fabric OS zonecreate command.
bcu boot --blunZone -c <BLUN> -p <port_wwn> -r <rport_wwn> -r <rport_wwn> -l <lun_id | lun#>
where: c BLUN p port_WWN r rport_WWN l lun_id | lun# Specifies boot LUN The hexadecimal WWN of the HBA port connecting to the boot LUN. For example, 10:00:00:05:1e:41:9a:cb. The hexadecimal WWN of the remote storage targets port. For example, 50:00:00:05:1e:41:9a:ca. The hexadecimal LUN identification. You can provide this as a one-Byte value or an eight-Byte value (four-level LUN addressing). For example, an eight-Byte value could be 09AABBCCDDEEFF00.
82
Booting systems without operating system or local drive
NOTE
Enter blunZone without operands to display the command format. For example, enter the following:
bcu boot --blunZone -c BLUN -p 10:00:00:05:1e:41:9a:cb -r 50:00:00:05:1e:41:9a:ca -l 09AABBCCDDEEFF00
The command output will contain the proper encoding and be in the exact format for the FOS OS zoneCreate command. 3. Configure the zone on the switch using the Fabric OS zoneCreate command. Use the displayed output from the bfaZoneCreate command as the zonename and member operands:
zonecreate "zonename", "member[; member...]"
For example, if the output from blunZone is the following, you simply enter this for the zonecreate command operands on the switch.
"BFA_100000051E419ACB_BLUN","00:00:00:00:50:00:00:05; 00:00:00:01:1e:41:9a:ca; 00:00:00:02:DD:EE:FF:00; 00:00:00:03:09:AA:BB:CC"
4. Enter the FOS OS cfgSave command on the switch to save the zone configuration. The zone created is only an entity to store boot LUN data. There is no zone enforcement by the fabric. You must create a separate zone containing the HBA port and storage target port to ensure that the HBA port is able to see the target.
NOTE

This section provides generic procedures for using the following ISO 9660 (.iso) optical disk images to boot BIOS-based host systems that do not have an installed operating system or local drive. Once you boot the host system, you can use BCU commands to update the boot code on installed HBAs configure BIOS to boot over SAN and install the operating system and driver to a remote boot LUN.
LiveCD (live_cd.iso) that you can download from the Brocade HBA website at
\www.brocade.com/hba. Use this image to boot BIOS-based systems only.
WinPE ISO image that you can create for x86, x64, and Itanium Edition IA64 systems. You can
use a WinPE image to boot UEFI-based systems. To create these images, refer to Creating a WinPE image on page 84. For more detailed procedures to boot from a CD, refer to your host system documentation and online help. The following procedures assume that the Brocade HBA has been installed in the host system. 1. Obtain the LiveCD image from the brocade website or create a WinPE image for your system using steps under Creating a WinPE image on page 84. 2. the appropriate ISO image from the Brocade HBA website (www.brocade.com/hba) and create a CD. 3. Install the CD into the CD/DVD ROM drive and boot the system.
NOTE
83
4. When self-testing completes, access you systems boot manager menu and select the appropriate option to boot from the installed CD. 5. Follow on-screen prompts and instructions to boot from the CD. 6. Access your systems command shell so that you can use BCU commands. (Refer to Using BCU commands on page 5 for more information.) 7. To update HBA boot code, refer to steps under Using BCU on page 60. 8. To configure boot from SAN on an installed HBA, refer to Configuring boot over SAN on page 62 and Configuring BIOS using HCM and BCU on page 69. 9. To install the operating system and driver to a remote boot LUN, refer to Configuring boot over SAN on page 62 and Installing operating system and driver on boot LUNs on page 73.
Creating a WinPE image

Microsoft Windows Preinstallation Environment (Windows PE) is a bootable tool that provides minimal operating system features for installation, troubleshooting. and recovery. Please refer to the Microsoft Preinstallation Environment User's Guide for more information about Windows PE. You can customize WinPE to boot a diskless host system (system without a hard disk or operating system) that contains Brocade Fibre Channel HBAs and accomplish the following tasks.
Update the firmware and BIOS/EFI images in the HBA. The HBA tools and utilities bundled in
the driver aid in updating the HBA flash.
Install pre-configured Windows system images from a network share onto new computers that
access the storage through Brocade HBAs. Use the following procedures to customize a WinPE image with that includes the Brocade driver package and utilities for your system. 1. Download Windows Automated Installation Kit (WAIK) from Microsoft website. This kit is in .IMG format. 2. Create a CDROM from this image using CD burning software and install WAIK on a supported Windows system. 3. Select Download ISO Image on the Brocade HBA website www.brocade.com/hba and download the latest Brocade HBA ISO image. This image contains all supported driver packages. Each package contains the following files to create the customized WinPE image.
build_winpe.bat prep_winpe.bat
4. Create a CDROM from the Brocade HBA ISO image using CD burning software. 5. Insert the Brocade FCHBA CD into your systems CD/DVD drive. Examine the CD contents and determine the driver package for your operating system and host platform using information in Software installation packages on page 9. 6. Extract the driver package for the your platform into a local folder (such as C:\temp).
84
7.
Create the WinPE image using the following command:

build_winpe.bat <winpe-platform> <winpe-build-directory> <brocade-drivercd-root>
where <winpe-platform> can be x86, amd64, or ia64 <winpe-build-directory> is any folder where the WinPE image will be built <brocade-drivercd-root> points to the root of the Brocade FCHBA CD.
NOTE
The path in the directory arguments cannot contain spaces. As an example, to create a WinPE image for an IA64 platform in the C:\CustomUserWinPE directory when the Brocade FCHBA CD media is placed in drive E, enter the following.
build_winpe.bat ia64 C:\CustomWinPE E:\
This creates the a file named bfa_winpe_ia64.iso. 8. Burn the final ISO image into a CDROM using CD burning software.
85
86
Chapter
Specifications
In this chapter
Physical characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LED operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental and power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Channel standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regulatory compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87 90 91 91 91 96
Physical characteristics
The Brocade HBAs 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). HBAs are shipped with a low profile bracket installed and a standard bracket included for mounting in your host system (Table 8).
TABLE 8
Bracket Type
Low Profile Standard
HBA mounting brackets

Dimensions
1.84 cm by 8.01 cm (73 in. by 3.15 in.) 1.84 cm by 12.08 cm (73 in. by 4.76 in.)
PCI express interface

Use the Brocade HBAs in PCI Express computer systems with an Industry Standard Architecture/Extended Industry Standard Architecture (ISA/EISA) bracket type. On-board flash memory provides BIOS support over the PCI bus. The Brocade PCI Express interface supports PCI Express specifications Gen2 (PCI Base Specification 2.0) and Gen1 (PCI Base Specification 1.0, 1.1a, and 1.1). It operates as an x8 lane DMA bus master at 2.5 GHz, full duplex. Effective data rate on Gen2 systems is 32 Gbps and on Gen1 systems is 16 Gbps.
PCI system values

All Brocade HBAs share a common PCI Vendor ID (VID) value to allow drivers and BIOS to recognize them as supported Fibre Channel products. HBAs are also assigned PCI subsystem vendor IDs (SVIDs) and subsystem IDs (SSIDs) to allow drivers and BIOS to distinguish between individual host adapter variants. You can locate PCI device, vendor, and subsystem IDs for the installed Fibre Channel HBA through your hosts operating system tools. For example, if using Windows, use the following steps:
87
1. Access the Device Manager 2. Open the Properties dialog box for the HBA by right-clicking the HBA and selecting Properties from the short-cut menu. 3. Select the Details and Driver tabs to locate specific values.
Fibre channel interface

The Fibre Channel interface supports features outlined in Table 9.
TABLE 9
Feature
Port Speeds
Supported Fibre Channel features

Description
Brocade 825 and 815: An installed 8 Gbps SFP+ allows user-selectable or auto-negotiated speeds of 8, 4, or 2 Gbps per port. An installed 4 Gbps SFP allows user-selectable or auto-negotiated speeds of 4, 2, or 1 Gbps per port. Brocade 425 or 415: An installed 4 Gbps SFP allows user-selectable or auto-negotiated speeds of 4, 2, or 1 Gbps per port. An installed 8 Gbps SFP+ allows user-selectable or auto-negotiated speeds of 4 or 2 Gbps per port only.
Transceivers Connector ASIC
Multimode small form factor pluggable (SFP) LC
Provides the Fibre Channel functionality for all HBA models. Two on-board processors, each operating at 400 MHz, generate signal timing and link protocol in compliance with Fibre Channel standards. Stores firmware and HBA BIOS code 4 MB capacity 1600 MB at 8 Gbps 800 MB at 4 Gbps 400 MB at 2 Gbps
External serial FLASH memory Data Rate Per Port - Full Duplex Performance Per Port Distance Support Topology
500,000 IOPs (maximum) 50 m at 8 Gbps with 62.5/125 micron multimode fiber Point-to-Point (N_Port)
88
TABLE 9
Feature
Protocols
Supported Fibre Channel features

Description
Other Features
SCSI over FC (FCP) FCP3 - initiator mode only FC-SP ASIC Flip-flops Parity Protected ECC Memory Parity Protected Quality of Service (QoS) Target Rate Limiting Boot Over SAN T10 Data CRC NPIV Multiple Priority (VC_RDY) Frame-Level Load Balancing FC-SP Authentication Fabric-Based Boot LUN Discovery Persistent Binding Fabric-Based Configuration
ATTENTION
Fiber optic cable

Table 10 summarizes maximum distances supported for different fiber optic cable types. This table assumes a 1.5 dB connection loss and an 850 nm laser source.
TABLE 10
Port Speed
2 Gbps 4 Gbps 8 Gbps
Fiber optic cable specifications

OM1 (M6) Standard 62.5/125 micron
150 m 70 m Not recommended
OM2 (M5) Standard 50/125 micron

300 m 150 m 50 m
OM3 (M5E) Laser-optimized 50/125 micron -300

500 m 380 m 150 m
89
LED operation
LED operation
Figure 5 illustrates LED indicator locations on a Brocade 825 and a 415 HBA. LED indicators for each port are visible through the mounting brackets. Since the Brocade 825 operates at speeds up to 8 Gbps, each port has a 1-2, 4, and 8 Gbps LED. The 4 Gbps models, such as the Brocade 415, have a 1-2 and 4 Gbps LED for each port.
12 4
0 PORT
PORT
12 4
12 4
FIGURE 5
LED locations for 825 HBA (left) and 415 HBA (right)
Table 11 provides the meanings for LED operation on a specific port.
TABLE 11
LED Operation
LED operation
Meaning
Depending on LED illuminated, link is active at 1-2, 4, or 8 Gbps. Port is online (connected to an external device) but has no traffic. Note that only one of these LEDs will be steady green to indicate speed. Activity, such as data transfers, is occurring on active link. Beaconing is enabled on port. Unsupported SFP. Appropriate Brocade-branded SFP not installed.
LED is steady green
LED flickering green All LEDs flashing green All LEDs flashing amber
90
Environmental and power requirements

The following table lists environmental and power specifications for the HBAs.
TABLE 12
Property
Airflow

Requirement
None required. 0C to 50C (32F to 122F) 5% to 93% (relative-noncondensing) -43C to 73C (-40F to 163F) (dry bulb) 5% to 95% (relative-noncondensing) 6.3W Maximum not including SFP. Reduced in green power mode. 3.3V operation
Operating Temperature (dry bulb) Operating Humidity Nonoperating Temperature Nonoperating Humidity Power Dissipation
Operating Range
Fibre Channel standards compliance

The HBAs meet or exceed the Fibre Channel standards for compliance, performance, and feature capabilities as defined in the Brocade standards compliance list. This information is available at: http://www.brocade.com/products/interop/standards_compliance.jsp
Regulatory compliance
This section provides international regulatory compliance notices for the Fibre Channel HBAs.
FCC warning (US only)

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
MIC Statement (Republic of Korea)
91
VCCI statement (Japan)

This is Class B product based on the standard of the Voluntary Control Council For Interference by Information Technology Equipment (VCCI). If this equipment is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual.
BSMI warning (Republic of Taiwan)
CE statement
ATTENTION
This is a Class B product. In a domestic environment, this product might cause radio interference, and the user might be required to take corrective measures. The standards compliance label on the HBA contains the CE mark which indicates that this system conforms to the provisions of the following European Council directives, laws, and standards:
Electromagnetic Compatibility (EMC) Directive 89/336/EEC and the Complementary Directives

92/31/EEC, 93/68/EEC, and (2004/108/EEC).
Low Voltage Directive (LVD) 73/23/EEC and the Complementary Directive 93/68/EEC EN50082-2/EN55024:1998 (European Immunity Requirements) EN61000-3-2/JEIDA (European and Japanese Harmonics Spec) EN61000-3-3
Canadian requirements
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations, ICES-003 Class B.
92
Laser compliance
This equipment contains Class 1 laser products and complies with FDA Radiation Performance Standards, 21 CFR Subchapter I and the international laser safety standard IEC 825-2.
CAUTION Use only optical transceivers that are qualified by Brocade Communications Systems, Inc. and comply with the FDA Class 1 radiation performance requirements defined in 21 CFR Subchapter I, and with IEC 825-2. Optical products that do not comply with these standards might emit light that is hazardous to the eyes.
Safety and EMC regulatory compliance

Table 13 lists the regulatory compliance standards and certifications for which the HBA is certified.
TABLE 13
Country
Regulatory certifications and standards

Safety specification EMC specification
EN55022 or CISPR22 or AS/NZS CISPR22 C-Tick Mark Bi-Nat UL/CSA 60950-1 1st Ed or latest. cCSAus EN 60950-1 or latest TUV ICES-003 Class B ICES A and Statement CE EN55022:2006 Class B EN 55024 (Immunity) EN 61000-4-2 Security Level 3 Electrostatic Discharge EN 61000-4-3 Security Level 3 Radiated Fields EN 61000-4-4 Security Level 3 for eFT/Burst EN 61000-4-5 Security Level 3 for Surge Voltage EN 61000-4-6 Security Level 3 EN 61000-4-8 Magnetic Fields (N/A) EN 61000-4-11 Voltage Dips and Interruptions EN 61000-3-2 Limits for Harmonic Current Emissions EN 61000-3-3 (Voltage Fluctuations) CISPR22 and JEIDA (Harmonics) VCCI-B and Statement KN24 KN22 MIC Mark Class B IEC60950-1 or latest GOST Mark CNS14336(94) Class A or latest BSMI Mark Bi-Nat UL/CSA 60950-1 1st Ed or latest. cCSAus 51318.22-99 (Class B) and 51318.24-99 or latest GOST Mark CNS13438(95) Class A or latest BSMI Mark ANSI C63.4 FCC Class B and Statement
Australia and New Zealand Canada European Union (Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, The Netherlands, and United Kingdom)
Japan Republic of Korea
Russia Taiwan United States
93
Environmental and safety compliance

This section provides international environmental and safety compliance notices for the Fibre Channel HBAs.
Environmental Protection Use Period (EPUP) Disclaimer

In no event do the EPUP logos shown on the product and FRU's alter or expand that warranty that Brocade provides with respect to its products as set forth in the applicable contract between Brocade and its customer. Brocade hereby disclaims all other warranties and representations with respect to the information contained on this CD including the implied warranties of merchantability, fitness for a particular purposes and non-infringement. The EPUP assumes that the product will be used under normal conditions in accordance with the operating manual of the product.
(EPUP) EPUP FRU Brocade Brocade CD Br
ocade EPUP
China RoHS
The contents included in this section are per the requirements of the People's Republic of ChinaManagement Methods for Controlling Pollution by Electronic Information products.
RoHS
94
Names and Contents of the Toxic and Hazardous Substances or Elements In accordance with China's Management Measures on the Control of Pollution caused by Electronic Information products (Decree No. 39 by the Ministry of Information Industry), the following information is provided regarding the names and concentration level of Hazardous substances (HS) which may be contained in this product.
TABLE 14
Hazardous Substances/Toxic Substances (HS/TS) Concentration Chart
95
Safety
Safety
Because these boards are installed in a PCIe bus slot, all voltages are below the SELV 42.4 V limit.The adapters are recognized per Bi-Nat UL/CSA 60950-1 1st Ed. or later for use in the US and Canada. They also comply with IEC 60950-1 and EN60950-1. A CB Scheme certificate is available upon request
96
Appendix
HBA configuration
Information in this appendix is optional for power users who want to modify values for HBA instance-specific persistent and driver-level configuration parameters.
Instance-specific persistent parameters

Instance-specific persistent configuration parameters with valid value ranges are listed in Table 15. These values can be changed using the BCU commands provided in the table. These parameters are stored in the following locations on your system:
Linux and VMware - /etc/bfa.conf Solaris - /kernel/drv/bfa.conf Windows - Windows registry, under the following registry hive:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bfad\Parameters\Device Values for these parameters should not be changed in the repository directly; instead use the corresponding BCU commands listed in Table 15.
TABLE 15
Function
authorization algorithm
HBA Driver configuration options

Parameter
bfa#-auth-algo
Default Value
1
Possible Values
1: MD5 2: SHA1 3: MS 4: SM 0: on 1: off min chars - 0 max chars - 256 0: False 1: True min chars - 0 max chars - 64 0: Off 1: On min: 0 max: 1125 0 microns 225 microns
BCU Command
auth --algo
Notes
Not supported in Solaris. Not supported in Solaris. Not supported in Solaris.
authorization policy authorization secret fast failover for MPIO setup HBA name IOC interrupt coalesce IOC interrupt delay IOC interrupt latency
bfa#-auth-policy
off
auth --policy
bfa#-auth -secret
NA
auth --secret
bfa#mpiomode
fcpim --mpiomode Not supported in Solaris. adapter --name ioc --intr ioc --intr ioc --intr
adapter-serialnum -name bfa#-coalesce bfa#-delay bfa#-latency
NA 1 1125 225
97
Driver-level parameters
TABLE 15
Function
log level
HBA Driver configuration options

Parameter
bfa#-log-level
Default Value
4
Possible Values
1: Critical 2: Error 3: Warning 4: Info min: 0 max: 60 512 1024 2048 2112 min chars - 0 max chars - 64 0: auto select 1: 1 Gbps 2: 2 Gbps 4: 4 Gbps 8: 8 Gbps 1: point to point 3: autoselect 0: True 1: False min - 0 max - 2000
BCU Command
log --level
Notes
path time out value (TOV) port maximum frame size
bfa#-pathtov
30
fcpim --mpiomode Not supported in Solaris. port --dfsize
bfa#-maxfrsize
2112
port name port speed
bfa#-port-name bfa#-port-speed
NA 0
port --name port --speed
port topology port enable per target maximum SCSI queue depth value. virtual port
bfa#-port-topology bfa#-port-enable fcp#-qdepth
1 0 NA
port --topology port --enable port --disable fcpim --qdepth Not supported in Linux. Not supported in Solaris.
bfa#-vport-#
NA
NA
vport --create
The driver-level configuration parameters are global parameters used by all HBA driver instances. The default values for the driver configuration parameters are compiled into the driver. These parameters are should only be changed by power users with great caution.
NOTE
Linux and VMware driver configuration parameters

The driver-level configuration values in Table 16 on page 99 are in the following locations on your system:
Linux - /etc/modprobe.conf VMware - /etc/vmware/esx.conf
98
Table 16 describes the Linux and VMware configuration parameters.
TABLE 16
Parameter
Linux and VMware driver configuration parameters

Default Value
2048
Notes
Maximum I/O requests that can be queued by the SCSI transport layer. This parameter is passed to the SCSI layer during SCSI transport attach. Maximum Scatter gather elements supported (per I/O request). This parameter is passed to the SCSI layer during SCSI transport attach. Maximum SCSI requests per LUN. This parameter is passed to the SCSI layer during SCSI transport attach. Host name Auto-recover IOC (IO Controller) on heartbeat failure. BFA log level setting. See bcu log --level information in the Brocade HBA Administrators Guide for more information. Disable MSIx interrupt (and use INTx). Maximum number of FC transport requests. Maximum number of FCP IO requests. Maximum number of remote ports. Maximum number of Scatter gather pages. Maximum number of task management commands. Maximum number of unsolicited frame buffers. OS name. OS patch level. Number of elements in the request queue (used for driver-tofirmware communication). Delay (in seconds), after which an offline remote port's state machine will be removed. Number of elements in the response queue (used for firmware-todriver communication).
bfa_ioc_queue_depth
bfa_io_max_sge
128
bfa_lun_queue_depth host_name ioc_auto_recover log_level msix_disable num_fcxps num_ios num_rports num_sgpgs num_tms num_ufbufs os_name os_patch reqq_size rport_del_timeout rspq_size
32 NULL 1 2 (Error) 1 64 512 512 512 128 64 NULL NULL 256 30 (seconds) 64
Managing Linux driver configuration parameters

Either the driver configuration parameter values can be loaded with the driver or can be set in /etc/modprobe.conf before loading the driver. Following is are examples to disable IOC auto recovery:
Load driver with the parameter value.

modprobe bfa ioc_auto_recover=0
Add the following entry in /etc/modprobe.conf, then load the driver.

options bfa ioc_auto_recover=0
Display current driver configuration settings using the following command:

cat /sys/module/bfa/parameters/<parameter>
99
Managing VMware driver configuration parameters

To set a configuration parameter use the following steps: 1. Enter the following command
esxcfg-module -s 'param_name=param_value' bfa
2. When you have set all desired parameters, reboot the system. Following is an example to enable IOC auto recovery:
esxcfg-module -s 'ioc_auto_recovery=1' bfa
Important notes
esxcfg-module reads and updates from file /etc/vmware/esx.conf Editing this file directly is not recommended. Be careful not to over-write the existing options. Always query the existing configuration
parameter value before changing it using the following command:
esxcfg-module -q
Windows driver configuration parameters

The BFA driver configuration parameters are located under the registry hive: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bfad\Parameters\Device Table 17 describes the windows configuration parameters.
TABLE 17
Parameter
Windows driver configuration parameters

Default Value
2048 1 90 1
Notes
Maximum number of outstanding I/Os across all the targets connected per IOC. Auto recoveries IOC (IO Controller) on heartbeat failure. Delay in seconds, after which an offline remote port's state machine will be removed. Disable MSIx interrupt (and use line-based INTx).
bfa_ioc_queue_depth ioc_auto_recover rport_del_timeout msix_disable
Managing Windows driver configuration parameters

To change any driver configuration parameter, use the Registry Edit tool (regedt32). Following is an example sequence to rport_del_timeout parameter: 1. Navigate to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bfad\Parameters\Device 2. Click rport_del_timeout 3. Click Edit ? Modify.... 4. For Value data, enter 60. 5. Click OK
100
6. Use the following steps to reload the driver and reinitialize the HBA parameters from the modified registry: a. b. c. d. e. Quiesce all application access to disks that are connected through the HBA. Stop the Brocade HCM Agent Service (refer to Modifying HCM Agent operation on page 44 for instructions). Open the Windows Device Manager (devmgmt.msc), and navigate to SCSI and RAID controllers. To unload the driver, disable all Brocade 425/825 4G/8G FC HBA devices (each port has a device entry). To reload the driver, enable all Brocade 425/825 4G/8G FC HBA devices.
Notes:
We recommend using the applicable BCU command to dynamically update the value
(where available), rather than reloading the driver.
Disabling the devices will disrupt FC HBA connectivity. To find out if the driver has unloaded successfully after disabling the Brocade HBA
devices in the Device Manager, run any BCU command. This should result in an Error: No Brocade HBA Found message. If the driver did not unload for some reason, the BCU command should complete normally.
If the device icon display in Device Manager does not change to indicate that each
HBA port device is disabled and if a message displays when you attempt to disable the devices that your hardware settings have changed and you must restart your computer for changes to take effect, confirm that the hcmagent.exe (Brocade HCM Agent Service) is not running on the host and that there are no open handles to file systems on disks accessed through the HBA:
Solaris driver configuration parameters

Table 18 describes the Solaris configuration parameters.
TABLE 18
Parameter

Default Value
1 1 64 512 512 512 128 64
Notes
Auto recover IOC (IO Controller) on heartbeat failure. Disable MSIx interrupt (and use INTx). Maximum number of FC transport requests. Maximum number of FCP IO requests. Maximum number of remote ports. Maximum number of Scatter gather pages Maximum number of Task management commands. Maximum number of unsolicited frame buffers.
ioc_auto_recover msix_disable num_fcxps num_ios num_rports num_sgpgs num_tms num_ufbufs
101
TABLE 18
Parameter
reqq_size rspq_size

Default Value
256 64
Notes
Number of elements in the request queue (used for driver-to-firmware communication) Number of elements in the response queue (used for firmware-todriver communication).
Managing Solaris driver configuration parameters

To modify any driver parameter values, use the following steps: 1. Edit /kernel/drv/bfa.conf. For example, to disable ioc_auto_recover, change ioc-auto-recover = 1 to ioc-auto-recover = 0. 2. When you have set all desired parameters, reboot the system.
102
Appendix
List of acronyms
Following is a list of acronyms used in this publication and their meaning. BCU Brocade Command Line Utility BFA Brocade Fibre Channel adapter BIOS Basic Input/Output System DCFM Data Center Fabric Manager EMC Electromagnetic Compatibility ESD Electrostatic Discharge EPUP Environmental Protection Use Period FCP Fibre Channel Protocol FC-SP Fibre Channel-Security Protocol FDMI Fabric Device Management Interface GUI Graphical User Interface HCM Host Connectivity Manager HS/TS Hazardous Substances/Toxic Substances
103
List of acronyms
IRQ Interrupt Request ISA/EISA Industry Standard Architecture/Extended Industry Standard Architecture ISO International Standards Organization LVD Low Voltage Directive MSI Message Signaled Interrupts NPIV N_Port ID Virtualization NWWN Node World Wide Name PCI Peripheral Component Interconnect PCIe Peripheral Component Interconnect Express PWWN Port World Wide Name QoS Quality of Service RHEL Red Hat Enterprise Linux SAN Storage Area Network SFP Small Form Factor Pluggable SLES SUSE Linux Enterprise Server SMI-S Storage Management Initiative Specification
104
List of acronyms
SSID Subsystem ID SVID Subsystem Vendor Identification TRL Target Rate Limiting UAC User Account Control UEFI Unified Extensible Firmware Interface (UEFI) boot support VC Virtual Channel VCCI Voluntary Control Council For Interference by Information Technology Equipment VID Vendor ID VM Virtual Machine WFAS Windows Firewall and Advanced Service WHQL Windows Hardware Quality Lab WinPE Windows Preinstallation Environment WWN World-Wide Name WWPN World-Wide Port Name
105
List of acronyms
106
Index
A
acronyms used in manual, 103 agent, 5 autorun from CD not working, 49
booting without operating system, 83 BSMI warning, 92
C
Canadian requirements, 92 CE statement, 92 command line utility, 4, 5 communications port firewall issue, 34 compliance environmental and safety, 94 Fibre Channel standards, 91 laser, 93 regulatory, 91 safety and EMC, 93 components in HBAs, 2 configuring HBAs, 97 connecting HBA to fabric, 20
B
BCU, 4, 5 BCU commands, using, 5 bfa_supportsave, xii BIOS configuring with Brocade Utility, 64 configuring with HCM and BCU, 69 support, 58 BIOS configuration utility field descriptions, 66 boot code, 57 updating, 59 boot LUN discovery in fabric, 82 configuring, 82 boot LUNs installing full driver package, 81 installing Linux (RHEL), 76 installing Linux (SLES 10), 78 installing Linux (SLES 9), 78 installing operating system and driver, 73 installing VMware, 79 installing Windows 2003, 74 installing Windows 2008, 75 boot over SAN configuring, 62 configuring BIOS, 64, 69 configuring UEFI, 71 general requirements, 61 host requirements, 61 installing full driver package, 81 installing image on boot LUNs, 73 introduction, 60 storage requirements, 61 boot over SAN not working, 49 boot support for HBA, 57 booting without local drive, 83
D
default mode for installing software, 28 driver configuration parameters Linux and VMware, 98 Solaris, 101 Windows, 100 driver package, 5, 81 installing with software installer, 23 manually installing, 34 manually removing, 34 removing with software installer, 29 removing with software uninstaller commands, 31 upgrading, 34 driver-level configuration parameters, 98
E
environmental and power requirements, 91
107
environmental and safety compliance EPUP disclaimer, 94 RoHS statement, 94 error message when removing Windows driver, 48 error when rolling back driver, 49 errors installing source-based drivers, 48 event messages, 98
F
fabric based boot LUN discovery, 82 configuring, 82 fabric connection, 20 FCC warning, 91 features of HBA, 3 fiber optic cable recommendations, 89 Fibre Channel interface, 88 Fibre Channel standards compliance, 91 files needed for bfad.sys message, 48 firewall issue, 22, 34 firmware, 5
H
hardware installation fabric connection, 20 HBA, 18 HBA, 17 components, 2 configuration, 97 driver package, 5 installing with software installer, 23 manually installing, 34 manually removing, 34 removing with software installer, 28 removing with software uninstaller commands, 31 upgrading, 34 environmental and power requirements, 91 fabric OS support, viii fiber optic cables, 89 Fibre Channel interface, 88 firmware, 5 hardware and software compatibility, 7 host and fabric support, 3 host connectivity manager (HCM) removing with software uninstaller commands,
33 host platform support, 8 installation verifying, 47 LED operation, 90 management BCU, 4, 5 HCM, 4, 6 operating system support, viii, 8 PCI system values, 87 PCIe interface, 87 physical characteristics, 87 product overview, 1 PWWN, xiii replacing, 46 safety information, 96 serial number, xii software downloading from website, 16 installation options, 6 installation packages, 9, 15 installing with software installer, 21 overview, 5 removing with software installer, 28 removing with software uninstaller commands, 31 storage support, viii supported models, viii switch support, viii HBA not recognized by operating system, 50 HCM agent, 5 removing with software installer, 29 removing with software uninstaller commands, 33 HCM agent changing communications port, 44 firewall issue, 22, 34 modifying operation, 44 verifying operation, 44 HCM agent communications port changing, 44 firewall issue, 22, 34 host and fabric support for HBAs, 3 host connectivity manager (HCM) removing with software installer, 29 host connectivity manager (HCM) agent starting, 44 stopping, 44 host connectivity manager (HCM) description, 6 host platform support, 8 host system freezes, 50
108
I
installation verifying, 48 installing driver package manually, 34 installing driver package with software installer, 23 installing hardware, 17 installing to boot LUN, 81 instance-specific persistent configuration parameters, 97
P
PCI system values, 87 PCIe interface, 87 PCIe slots, 7 physical characteristics of HBA, 87 product overview, 1
R
regulatory compliance, 91 BSMI warning, 92 Canadian requirements, 92 CE statement, 92 FCC warning, 91 laser compliance, 93 MIC statement, 91 safety and EMC compliance, 93 VCCI statement, 92 removing driver and HCM, 32 removing driver package manually, 34 removing driver with software installer, 28 removing driver with software uninstaller commands, 31 removing HCM with software installer, 29 removing HCM with software uninstaller commands, 33 replacing HBA, 46 RoHS statement, 94
L
laser compliance, 93 LED operation, 90 Linux (RHEL) installing on boot LUN, 76 Linux (SLES 10) installing on boot LUN, 78 Linux (SLES 9) installing on boot LUN, 78 Linux systems driver configuration parameters, 98, 101 manually installing driver, 38 manually removing driver, 40 modifying agent operation, 44 removing driver and HCM with software uninstaller commands, 32 upgrading driver, 41 LiveCD image, 83 Lunux driver install errors, 48
S
safety and EMC compliance, 93 safety information, 96 serial number location, xii SFP Brocade, 1, 7 removing and installing, 20
M
managing HBAs, 4 MIC statement, 91 mounting bracket replacing mounting bracket, 18 types, 87
O
operating system does not recognize HBA, 50 operating system support, viii, 8
109
software compatibility, 7 downloading from website, 16 driver package, 5 HCM, 6 installation options, 6 installation packages, 9, 15 installing with software installer, 21 manually installing, 34 manually removing, 34 overview, 5 removing with software installer, 28 removing with software uninstaller commands, 31 software installer commands examples, 27 important notes, 26 using, 26 using default mode, 28 software uninstaller commands important notes, 32 Solaris systems driver configuration, 101 installing driver and HCM with software installer, 23 manually installing driver, 41 manually removing driver, 42 modifying agent operation, 45 upgrading driver, 43 starting HCM agent, 44 stopping HCM agent, 44 support save differences between HCM, BCU, and browser, 56 on port crash event, 56 using through BCU, 55 using through browser, 56 using through HCM, 55 using through port crash event, 56 support save feature using, 54
U
UEFI configuring, 71 support, 59 upgrading driver package, 34
V
VCCI statement, 92 verifying HBA installation, 47 VMware installing on boot LUN, 79 VMware systems driver configuration, 100 driver configuration parameters, 98 firewall issue, 22, 34 installing HCM, 22 manually installing driver, 43 manually removing driver, 43 modifying agent operation, 44 upgrading driver, 44
W
Windows 2003 installing on boot LUN, 74 Windows 2008 installing on boot LUN, 75 Windows systems driver configuration parameters, 100 firewall issue, 22, 34 installing driver and HCM with software installer, 23 manually installing driver, 35 manually removing driver, 37 modifying agent operation, 45 removing driver and HCM with software installer, 29 removing driver and HCM with software uninstaller commands, 32 WinPE creating ISO image, 84 WinPE image, 83 WWPN of HBA, xiii
T
technical help for product, xii troubleshooting devices not recognized by host, 51 HBA not recognized by BIOS, 49 HBA not recognized by operating system, 50 troubleshooting installation problems, 48
110

HBA Install and Reference Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HBA Install and Reference Manual

Uploaded by

Copyright:

Available Formats

53-1000884-02 December 19, 2008

Brocade Fibre Channel HBA

Brocade Communications Systems, Incorporated

About this document

HBA product overview

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Troubleshooting installation problems

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA boot code

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

About this document

How this document is organized

Chapter 1, Introduction, provides a detailed product overview and description. Information on

Chapter 5, Specifications, includes details on HBA physical characteristics, LED operation,

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Supported hardware and software

Install only Brocade-branded SFPs in these HBAs.

Fabric OS and switch support

Host operating system support

Windows Vista (HCM only) Windows XP (HCM only)

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Whats new in this document

Command syntax conventions

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

variable ... value |

Notes, cautions, and warnings

Notice to the reader

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Referenced Trademarks and Products

Support and warranty contact information.

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Other industry resources

Getting technical help

Description of any troubleshooting steps already performed and the results.

HBA serial number

HBA Properties tab in HCM

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

BCU adapter --list command

Port World-Wide Port Name (PWWN)

Brocade BIOS Configuration Utility.

HCM Port Properties dialog box.

The following BCU commands:

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA product overview

HBA product overview

Brocade Fibre Channel HBA Models

4 Gbps maximum2 4 Gbps maximum

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA product overview

825 HBA with low-profile mounting bracket

Table 2 describes HBA components illustrated in Figure 1.

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA product overview

Adaptive Networking (AN) license. Server Application Optimization (SAO) license.

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA product overview

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

RoHS-6. Switch fabric topology. Point-to-point topology.

Brocade Fibre Channel HBA Installation and Reference Manual 53-1000884-02

HBA product overview

Using BCU commands