Brocade Adapters v2.3.0.0 Admin Guide

53-1001923-02 30 November 2010

®

Brocade AdaptersAdministrator’s Guide

Supporting CNA models 1741, 1020, 1010, 1007Supporting HBA models 825, 815, 804, 425, 415

Copyright © 2008-2010 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks, MyBrocade, and VCS are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned are or may be trademarks or service marks of their respective owners.

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 HeadquartersBrocade Communications Systems, Inc.130 Holger WaySan Jose, CA 95134 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: [email protected]

Asia-Pacific HeadquartersBrocade Communications Systems China HK, Ltd.No. 1 Guanghua RoadChao Yang DistrictUnits 2718 and 2818Beijing 100020, ChinaTel: +8610 6588 8888Fax: +8610 6588 9999E-mail: [email protected]

European HeadquartersBrocade Communications Switzerland SàrlCentre SwissairTour B - 4ème étage29, Route de l'AéroportCase Postale 105CH-1215 Genève 15Switzerland Tel: +41 22 799 5640Fax: +41 22 799 5641E-mail: [email protected]

Asia-Pacific HeadquartersBrocade Communications Systems Co., Ltd. (Shenzhen WFOE)Citic PlazaNo. 233 Tian He Road NorthUnit 1308 – 13th FloorGuangzhou, ChinaTel: +8620 3891 2000Fax: +8620 3891 2111E-mail: [email protected]

Document History

Title Publication number Summary of changes Date

Brocade Adapters Administrator’s Guide Supporting HBA models 825, 815, 425, 415

53-1000881-01 New document June 2008

Brocade Adapters Administrator’s GuideSupporting CNA models 1020, 1010Supporting HBA models 825, 815, 425, 415

53-1001256-01 Updates to support newfeatures:• Boot over SAN for the CNA• Windows NIC Teaming• Target Rate Limiting on

the CNA• Interrupt Coalescing on

the CNA• Network Priority• BCU commands to

support the new features

September 2009

Brocade Adapters Administrator’s GuideSupporting CNA models 1020, 1010Supporting HBA models 825, 815, 425, 415,

53-1001587-01 Updates to support the Brocade adapters.

May 2010

Brocade Adapters Administrator’s GuideSupporting CNA models 1020, 1010 Supporting HBA models 825, 815, 804, 425, 415

53-1001923-01 Updates to support the new CNA features:• FC trunking• PXE boot enable/disable• Message timeout• FCP-IM IO profile support• Update driver• Teaming VLAN• Statistics updates for CEE,

Ethernet Port, FCoE, FCP IM Module, IOC, Firmware, Port, Realtime for CEE Port, Logical Port

September 2010

Brocade Adapters Administrator’s GuideSupporting CNA models 1741, 1020, 1010 Supporting HBA models 825, 815, 804, 425, 415

53-1001923-02 Updates to support the Brocade 1741 adapter.

November 2010

Brocade Adapters Administrator’s Guide iii53-1001923-02

iv Brocade Adapters Administrator’s Guide53-1001923-02

Contents

About This Document

In this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiText formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiNotes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . xviiiKey terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixBrocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixAdapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxFCoE switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxSAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxAdditional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxOther industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Chapter 1 Host Management Overview

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

Host bus adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Common HBA and CNA features. . . . . . . . . . . . . . . . . . . . . . . . . . 3HBA-only features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4CNA and networking features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Tree node pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Adapter support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Getting Started with HCM Software

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Brocade Adapters Administrator’s Guide v53-1001923-02

HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Launching the application on Windows platforms. . . . . . . . . . .13Launching the application on Linux platforms. . . . . . . . . . . . . . 14Launching the application on Solaris platforms . . . . . . . . . . . . 14Remember password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Skip login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Changing an HCM application password . . . . . . . . . . . . . . . . . .15Changing an HCM agent password. . . . . . . . . . . . . . . . . . . . . . . 16HCM configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Restore Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

HCM main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Legend Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Event severity icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Setting up out-of-band discovery for an adapter . . . . . . . . . . . .22

Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Chapter 3 Host Configuration

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Host security authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Configuring security authentication using HCM (Host and HBA)26Configuring security authentication using the BCU . . . . . . . . . . 27

Buffer credits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Opening the Basic Port Configuration dialog box . . . . . . . . . . .29Port logging level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Ethernet logging level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Port speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Frame data field size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Persistent binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32FC Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33QoS (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Path time out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Target rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36FCP-IM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Configuring Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Pre-boot configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Boot image update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Driver update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Changing the HCM timeout value . . . . . . . . . . . . . . . . . . . . . . . .42

PXE boot support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Configuring PXE boot support . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Virtual port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Virtual port restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Creating a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Deleting a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

vi Brocade Adapters Administrator’s Guide53-1001923-02

HCM logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Configuring the HCM logging level using HCM. . . . . . . . . . . . . .46

Advanced port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Opening the Advanced Port Configuration dialog box . . . . . . . . 47Interrupt Control Coalesce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Name configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Dual role changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Name validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Defining a name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Editing the name fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Adding name entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Removing a name entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Exporting the properties for a WWN . . . . . . . . . . . . . . . . . . . . . .52Importing the properties for a WWN. . . . . . . . . . . . . . . . . . . . . .53Importing duplicated names . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Teaming configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Teaming modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Configuring a team from the host level . . . . . . . . . . . . . . . . . . . 57Adding and editing a team . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Changing the primary port in a team . . . . . . . . . . . . . . . . . . . . .58Removing a team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Displaying teaming statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . .59

VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Adding a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59VLAN configuration conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Editing a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Removing a VLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Displaying VLAN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Management application support for FCoE . . . . . . . . . . . . . . . . . . .63

Chapter 4 Monitoring

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

Performance monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Controlling the polling frequency rate. . . . . . . . . . . . . . . . . . . . .66Resetting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Real-time performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Historical performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Master log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Filtering event log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Syslog support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Opening the Syslog Server Configuration dialog box. . . . . . . . .73Registering a host server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Removing a host server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Syslog host configuration using VMware . . . . . . . . . . . . . . . . . . 74

Brocade Adapters Administrator’s Guide vii53-1001923-02

Chapter 5 Diagnostics

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Fibre Channel diagnostics using HCM. . . . . . . . . . . . . . . . . . . . . . . .75Running a hardware-level test using HCM . . . . . . . . . . . . . . . . . 76Running a Fibre Channel protocol-level test using HCM . . . . . . 77Displaying test log details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Fibre Channel diagnostics using the BCU . . . . . . . . . . . . . . . . . . . . .79diag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79fcdiag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Ethernet diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Running an Ethernet test using HCM . . . . . . . . . . . . . . . . . . . . . 81Running an Ethernet test using the BCU . . . . . . . . . . . . . . . . . .82

Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Configuring beaconing using HCM . . . . . . . . . . . . . . . . . . . . . . .82Configuring beaconing using the BCU . . . . . . . . . . . . . . . . . . . .83

SFP management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Displaying SFP information using the BCU. . . . . . . . . . . . . . . . .83Displaying SFP information using HCM . . . . . . . . . . . . . . . . . . .83

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84supportSave collection sources . . . . . . . . . . . . . . . . . . . . . . . . .85

Appendix A HCM Dialog Boxes

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Authentication Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . 91

Backup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Base Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

CEE properties panel (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

CEE Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . .96

Change HCM Password dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . .98

Change HCM Agent Password dialog box . . . . . . . . . . . . . . . . . . . . .99

CNA Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

CNA Port panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

CNA Port Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . .103

Configure Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Duplicated Names dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Eth IOC Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . .110

Ethernet Port Properties panel (CNA only) . . . . . . . . . . . . . . . . . . .111

Eth Port Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . .112

Event Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

viii Brocade Adapters Administrator’s Guide53-1001923-02

Fabric Statistics dialog box (HBA only). . . . . . . . . . . . . . . . . . . . . . .116

FCoE port properties panel (CNA only) . . . . . . . . . . . . . . . . . . . . . .117

FCoE Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . .119

FCP IM Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

FCP IM Module Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . .124

Fibre Channel Security Protocol Configuration dialog box . . . . . .127

Firmware Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Hardware Tests Diagnostics dialog box . . . . . . . . . . . . . . . . . . . . . .135

HBA Properties panel (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Historical Performance dialog box . . . . . . . . . . . . . . . . . . . . . . . . . .138

IOC Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

LLDP Properties panel (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . .140

Logical Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . .141

LPORT Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Master Log tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Persistent Binding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Port POM Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Port Properties panel (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Protocol Tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

QoS Statistics dialog box (HBA only) . . . . . . . . . . . . . . . . . . . . . . . .156

Real-time Performance Statistics dialog box . . . . . . . . . . . . . . . . .157

Remote Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Restore dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

SFP Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . .162

Target Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Teaming Configuration dialog box (CNA only) . . . . . . . . . . . . . . . . .167

Teaming Statistics dialog box (CNA only). . . . . . . . . . . . . . . . . . . . .169

Test Log Details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Update Driver dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Virtual Port Deletion dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Virtual Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Virtual Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . .175

VLAN Configuration dialog box (CNA only). . . . . . . . . . . . . . . . . . . .177

Brocade Adapters Administrator’s Guide ix53-1001923-02

VLAN configuration - Add VLAN dialog box (CNA only) . . . . . . . . . .178

VLAN configuration - Edit VLAN dialog box (CNA only) . . . . . . . . . .179

VLAN Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . .180

Appendix B Brocade Command Utility

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183

About the BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

BCU commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

bios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

cee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

drvconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

ethboot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

ethdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

ethioc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

ethlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

ethport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

fcdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

fcoe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

fcpim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

ioc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

lport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

pbind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

phy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

qos (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

ratelim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

rport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251

trunk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

vport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

x Brocade Adapters Administrator’s Guide53-1001923-02

Appendix C HCM Troubleshooting

Appendix D Glossary and Acronyms

Index

Brocade Adapters Administrator’s Guide xi53-1001923-02

xii Brocade Adapters Administrator’s Guide53-1001923-02

Figures

Figure 1 HCM Login dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 2 Change HCM Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 3 Change HCM Agent Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 4 Restore Data dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 5 Host Connectivity Manager main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 6 Setup for Discovery dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 7 Fibre Channel Security Protocol Configuration - host-level dialog box. . . . . . . . 26

Figure 8 Basic Port Configuration dialog box - Windows, Linux, and VMware . . . . . . . . . 29

Figure 9 Boot-over-SAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 10 Update Driver dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 11 Basic Port Configuration dialog box - PXE Boot tab. . . . . . . . . . . . . . . . . . . . . . . 43

Figure 12 Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 13 Configure HCM Logging Levels dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 14 Advanced Port Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 15 Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 16 Configure Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 17 Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 18 Teaming Configuration dialog box (with VLAN support) . . . . . . . . . . . . . . . . . . . 57

Figure 19 VLAN Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 20 Add VLAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 21 VLAN Configuration dialog box with PORT VLAN . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 22 VLAN Configuration conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 23 Edit VLAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 24 Remove VLAN dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 25 Reset statistics warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 26 Realtime Performance dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 27 Historical Performance dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 28 Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 29 HCM Application Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 30 Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Figure 31 Hardware-level diagnostic tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 32 Protocol-level diagnostic tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 33 Test Log Details for Echo Test dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 34 Ethernet Tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 35 SFP Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Brocade Adapters Administrator’s Guide xiii53-1001923-02

xiv Brocade Adapters Administrator’s Guide53-1001923-02

Tables

Table 1 Brocade Fibre Channel HBA models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Table 2 Brocade Fibre Channel CNA models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 3 HCM tree pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Table 4 Adapter operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 5 HCM product icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 6 HCM Master Log icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 7 Basic port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 8 Advanced port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 9 Statistics monitored by component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 10 Master Log fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Table 11 Hardware-level test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Table 12 Fibre Channel diag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Table 13 Fibre Channel diagnostic tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Table 14 Ethernet Test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Table 15 supportSave categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table 16 supportSave collection sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Brocade Adapters Administrator’s Guide xv53-1001923-02

xvi Brocade Adapters Administrator’s Guide53-1001923-02

About This Document

In this section

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

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

•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

•Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

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, “Host Management Overview,” provides a description of the Host Connectivity Manager (HCM) application software, the graphical user interface (GUI), system requirements, and supported operating systems.

• Chapter 2, “Getting Started with HCM Software,” explains how to launch the management software, set security passwords, discover SAN components, and log out.

• Chapter 3, “Host Configuration,” provides the procedures to configure operating parameters (basic and advanced), security authentication, and persistent binding using the Brocade Command Line Utility (BCU) or the GUI.

• Chapter 4, “Monitoring,” describes the HCM monitoring features.

• Chapter 5, “Diagnostics,” describes the non-destructive group of diagnostic commands that can be run from the BCU or the GUI.

• Appendix A, “HCM Dialog Boxes,” lists the fields that are associated with the HCM GUI and provides a definition for each field.

• Appendix B, “Brocade Command Utility,” provides reference information for the Host Connectivity Manager (HCM) commands that can be run from the Brocade Command Line Utility (BCU)

• Appendix C, “HCM Troubleshooting,” provides a summary of HCM navigation problems and workarounds.

• Appendix D, “Glossary and Acronyms,” provides reference information for common terms and acronyms.

Brocade Adapters Administrator’s Guide xvii53-1001923-02

Document conventions

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

Text formattingThe narrative-text formatting conventions that are used are as follows:

bold text Identifies command namesIdentifies the names of user-manipulated GUI elementsIdentifies keywords and operandsIdentifies text to enter at the GUI or CLI

italic text Provides emphasisIdentifies variablesIdentifies paths and Internet addressesIdentifies document titles

code text Identifies CLI outputIdentifies command syntax examples

For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.

Notes, cautions, and warningsThe following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.

NOTEA note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information.

ATTENTIONAn 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.

xviii Brocade Adapters Administrator’s Guide53-1001923-02

Key termsFor definitions specific to Brocade and Fibre Channel, see the Brocade Glossary.

For definitions specific to this document, see “Glossary and Acronyms” on page 261.

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

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

Notice to the reader

This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations.

These references are made for informational purposes only.

.

Related documentation

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

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

Corporation Referenced Trademarks and Products

Microsoft Corporation Windows Server, Windows XP, Windows Vista

Sun Microsystems, Inc. Sun, Solaris

Red Hat, Inc. Red Hat, Red Hat Network, Maximum RPM, Linux Undercover

Novell, Inc. SuSE Enterprise Server (SLES), Linux

VMware VMware, ESX Server

Brocade Adapters Administrator’s Guide xix53-1001923-02

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

AdaptersFor adapter resources, such as product information, software, firmware, and documentation, visit the adapters website at www.brocade.com/hba or www.brocade.com/cna, and complete the following steps:

1. Select your adapter product.

2. Click the Downloads tab.

The Downloads and Documentation page displays for the selected adapter.

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

• Brocade Adapters Troubleshooting Guide

• Brocade Adapters Installation and Reference Manual

• Brocade FCoE CNA Quick Installation Guide

• Brocade Fibre Channel HBA Quick Installation Guide

• CIM Provider for Brocade Adapters Installation Guide

FCoE switchFor information on the Brocade FCoE switch for connecting stand-up CNAs, refer to the following publications:

• Converged Enhanced Ethernet Command Reference

• Converged Enhanced Ethernet Administrator’s Guide

• Fabric OS Command Reference Manual

• Fabric OS Administrator’s Guide

• Data Center Fabric Manager (DCFM) User’s Guide

SANFor practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through:

http://www.amazon.com

White papers, online demos, and data sheets are available through the Brocade website at:

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

Additional informationFor additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location:

http://www.brocade.com

Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware.

xx Brocade Adapters Administrator’s Guide53-1001923-02

Other industry resourcesFor additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications:

http://www.t11.org

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

http://www.fibrechannel.org

For information about the Institute of Electrical and Electronics Engineers (IEEE) organization, visit the IEEE website:

http://standards.ieee.org/

Getting technical help

Contact your adapter support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available:

• Adapter model and serial number

• Adapter operating system version

• Error numbers and messages received

• supportSave command output (see “cee” on page 201 for details)

• 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

• Serial console and Telnet session logs

• Syslog message logs

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:

[email protected]

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.

Brocade Adapters Administrator’s Guide xxi53-1001923-02

http://www.t11.org

http://www.fibrechannel.org

xxii Brocade Adapters Administrator’s Guide53-1001923-02

Brocade Adapters Administrator’s Guide53-1001923-02

Chapter

1
Host Management Overview
In this chapter•Host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

•Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

•HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

•Tree node pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

•Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

•Adapter support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Host bus adaptersBrocade offers five models of Fibre Channel Host Bus Adapters (HBAs). These models provide reliable, high-performance host connectivity for mission-critical SAN environments. The Brocade HBAs are listed in Table 1.

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.

TABLE 1 Brocade Fibre Channel HBA models

Model Number Description Number of Ports

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

2

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

1

Brocade 804 Dual-port mezzanine HBA with a per-port maximum of 8 Gbps. This HBA installs in server blades that install in supported blade system enclosures.

2

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

2

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

1

1 A 4 Gbps SFP installed in Brocade 815 or 825 HBAs allows 4, 2, or 1 Gbps speed only.2 An 8 Gbps SFP installed in Brocade 425 or 415 HBAs allows 2 or 4 Gbps speed only.

1

Converged network adapters1

Converged network adaptersTable 2 describes available Brocade Converged Network Adapters (CNAs) for PCIe x 8 host bus interfaces, hereafter referred to as Brocade CNAs. These adapters provide reliable, high-performance host connectivity for mission-critical SAN environments.

Brocade CNAs combine the functions of a Host Bus Adapter (HBA) and Network Interface Card (NIC) on one PCIe x8 card. The CNAs even appear as network adapters (NIC) and Fibre Channel adapters to the host. These CNAs fully support FCoE protocols and allow Fibre Channel traffic to converge onto 10 Gbps Converged Enhanced Ethernet (CEE) networks. FCoE and 10 Gbps CEE operations are simultaneous.

The combined high performance and proven reliability of a single-ASIC design makes these CNAs ideal for connecting host systems on Ethernet networks to SAN fabrics based on Brocade Fabric or M-Enterprise operating systems.

NOTEThe Brocade 1007 CNA connects to the embedded switch modules or embedded interconnect modules on the Blade System chassis by way of an internal backplane and, therefore, no optical modules (SFPs) are involved. With the exception of no SFPs, the Brocade 1007 CNA functions the same as the other Brocade CNAs.

HCM software The Host Connectivity Manager (HCM) is a management software application for configuring, monitoring, and troubleshooting Brocade host bus adapters (HBAs) and converged network adapters (CNAs) in a storage area network (SAN) environment.

The management software has two components:

• The agent, which runs on the host.

• The management console, which is the graphical user interface client used to manage the adapter.

TABLE 2 Brocade Fibre Channel CNA models

Model Number Port Speed Number of Ports Adapter Type

1741M 10 Gbps maximum 2 Expansion

1020 10 Gbps maximum 2 Stand-up

1010 10 Gbps maximum 1 Stand-up

10071 10 Gbps maximum 2 Expansion

1The Brocade 1007 is a two-port 10 GbE converged network adapter that mounts on a blade server that installs in a blade system enclosure. The adapter uses FCoE to converge standard data and storage networking data onto a shared Ethernet link. Ethernet and Fibre Channel communication are routed through the CEE ports on the adapter to the blade system enclosure midplane and onto the installed switch modules installed in the enclosure.

For information on installing the Brocade 1007 CNA on a blade server, refer to the Brocade Adapters Installation and Reference Guide.

2 Brocade Adapters Administrator’s Guide53-1001923-02

HCM software 1

The information in this guide is intended for OEMs, field service personnel, and customers who are installing Brocade hardware and HCM software. For instructions about how to install the HCM software, refer to the Brocade Adapters Installation and Reference Manual.

You can manage the software on the host or remotely from another host. The communication between the management console and the agent is managed using JSON-RPC over HTTPS.

NOTEAll HCM, utility, CIM Provider, boot software, and driver installation packages, as well as the Driver Update Disk (DUD), are described in the Brocade Adapters Installation and Reference Manual.

Common HBA and CNA featuresHCM features that are common to both host bus adapters (HBAs) and to converged network adapters (CNAs) include the following:

• Discovery using the agent software running on the servers attached to the SAN, which enables you to contact the devices in your SAN.

• Configuration management , which enables you to configure local and remote systems. With HCM you can configure the following devices:

- Brocade 4 Gbps and 8 Gbps HBAs

- HBA ports (including logical ports, base ports, remote ports, and virtual ports) associated with the local host

- Brocade 10 Gbps single-port and 10 Gbps dual-port converged network adapters (CNAs)

- CEE ports

- FCoE ports (CNA only)

- Ethernet ports (CNA only)

• Diagnostics, which enables you to test the adapters and the devices to which they are connected:

- Link status of each adapter and its attached devices

- Loopback test, which is external to the adapter, to evaluate the ports (transmit and receive transceivers) and the error rate on the adapter

- Read/write buffer test, which tests the link between the adapter and its devices

- FC protocol tests, including echo, ping, and traceroute

- Ethernet loopback test (CNA only)

• Monitoring, which provides statistics for the SAN components.

• Security, which enables you to specify a CHAP secret and configure authentication parameters.

• Event notifications, which provide asynchronous notification of various conditions and problems through a user-defined event filter.

• Target rate limiting—relies on the storage driver to determine the speed capability of a discovered remote ports, then use this information to throttle FCP traffic rate to slow-draining targets. This reduces or eliminates network congestion and alleviates I/O slowdowns at faster targets.

Brocade Adapters Administrator’s Guide 353-1001923-02

HCM software1

Target rate limiting is enforced on all targets that are operating at a speed lower than that of the target with the highest speed. If the driver is unable to determine a remote port’s speed, 1 Gbps is assumed. You can change default speed using bcu commands. Target Rate Limiting protects only FCP write traffic.

• N_Port ID Virtualization (NPIV)— allows multiple N_Ports to share a single physical N_Port. This allows multiple Fibre Channel initiators to occupy a single physical port and reduce SAN hardware requirements.

• Fibre Channel Security Protocol (FC-SP)—provides device authentication through key management.

• End-to-end beaconing between an adapter port and switch port to which it connects. (Requires Brocade Fabric OS 6.3.x or above.)

• Boot over SAN—provides the ability to boot the host operating system from a boot device located somewhere on the SAN instead of the host’s local disk or direct attached storage. Specifically, this “boot device” is a logical unit number (LUN) located on a storage device.

• Fabric-based boot LUN discovery—allows the host to obtain boot LUN information from the fabric zone database.

• Persistent binding—enables you to permanently assign a system SCSI target ID to a specific Fibre Channel device.

• Interrupt Coalescing—provides a method to delay generation of host interrupts and thereby combine (coalesce) processing of multiple events. This reduces the interrupt processing rate and reduces the time that the CPU spends on context switching. You can configure the following parameters per port to adjust interrupt coalescing:

- Interrupt time delay. There is a time delay during which the host generates interrupts. You can increase this delay time and thereby coalesce multiple interrupts events into one. This results in fewer interrupts for interrupt events.

- Interrupt latency timer. An interrupt is generated when no new reply message requests occur after a specific time period. You can adjust this time period and thereby minimize I/O latency.

• Interrupt moderation—implements dynamic selection interrupt coalescing values based on traffic and system load profiles. Traffic is continuously monitored to place in categories between “high throughput sensitive” and “high latency sensitive.” Similarly, the host system is monitored regularly to place it in categories between “highly loaded” and “minimally loaded.” The driver dynamically selects interrupt coalescing values based on this profiling.

• Management APIs for integration with Brocade Data Center Fabric Manager (DCFM) and other management frameworks.

• Small form-factor pluggable (SFP and SFP+) optics for enhanced serviceability.

HBA-only featuresBrocade host bus adapters (HBAs) support the following features:

• N-Port Trunking (HBAs only)—enables trunking multiple physical ports to form a single logical port, which serves as a thick, resilient pipe (for example, two 8 Gbps ports to form a 16 Gbps port). N-Port trunking provides the benefits of simplified management with configuration tasks such as zoning and VM setup, because you need to specify only one WWN rather than two WWNs. With any single link failure between an HBA port and the switch, the second HBA port takes over the communication between the HBA port and the switch and this operation is transparent to the host, as both HBA ports share the same FCID.


HCM software 1

This feature works in conjunction with the trunking feature on Brocade switches. See “FC Trunking” on page 33 for more information.

This feature is supported only on 8 Gbps ports installed on Brocade switch models that use Fabric OS 6.4.1 or later. The following licenses need to be installed on the switch connected to the HBA port.

- Server Application Optimization (SAO) license

- Trunking license

• QoS (HBAs only)—the end-to-end Quality of Service (QoS) feature works 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 or later. The following licenses need to be installed on the FCoE switch connected to the CNA port.

- 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 on that switch. For more information about Fabric OS commands and QoS support, refer to the Fabric OS Administrator’s Guide.

CNA and networking featuresBrocade converged network adapters (CNAs) support the following features:

• 10 Gbps throughput per port full duplex

• 2500 or 9000-byte (Jumbo) frames

These frames allow data to be transferred with less effort, reduces CPU utilization, and increases throughput. Mini-jumbo frames are required to encapsulate FCoE frames on CEE.

NOTEThe jumbo frame size set for the network driver cannot be greater than the setting on the attached FCoE switch or the switch cannot accept jumbo frames.

• Data Center Bridging Capability Exchange Protocol (DCBCXP) (802.1)

Used between CNA and FCoE switch to exchange configuration with directly connected peers. Uses LLDP to exchange parameters between two link peers.

• Enhanced transmission selection (802.1Qaz)

Provides guidelines for creating priority groups to enable guaranteed bandwidth per group. More important storage data traffic can be assigned higher priority and guaranteed bandwidth so it is not stalled by less-important traffic.

• Ethernet flow control

Ethernet flow control is a mechanism for managing data transmission between two network nodes to prevent a fast sender from over running a slow receiver. When an overwhelmed receiver generates a PAUSE frame, this halts transmission for a specified period of time.Traffic resumes when time specified in the frame expires or PAUSE zero is received.

• Flexible MAC address


HCM software1

• Link aggregation (NIC teaming)

A network interface “team” is a collection of physical Ethernet interfaces (CNA ports) acting a single interface. Teaming overcomes problems with bandwidth limitation and redundancy often associated with Ethernet connections. Combining (aggregating) ports can increase the link speed beyond the limits of one port and provide redundancy. You can team up to eight ports across multiple CNAs in three modes: failover, failback, or 802.3ad.

- Failover mode provides fault tolerance. Only one port in a team is active at a time (primary port), and the others are in standby mode. If the primary port goes down, a secondary port is chosen using a round-robin algorithm as the next primary. This port continues to be primary, even if the original primary port returns.

- Failback mode is an extension of the Failover mode. In addition to the events that occur during a normal failover, if the original primary port comes back up, that port again becomes the primary port.

- 802.3ad is an IEEE specification that includes Link Aggregation Control Protocol (LACP) as a method to control how several physical ports bundle to form a single logical channel. LACP allows a network device to negotiate automatic bundling of links by sending LACP packets to the peer (a device directly connected to a device that also implements LACP). This mode provides larger bandwidth in fault tolerance.

Configuration is required on the switch for NIC teaming to function.

Be aware when configuring ports for teaming that converged FCoE and network traffic is not supported on ports that participate in an IEEE 802.3ad-based team. This must be enforced by the user as there is no mechanism to control this in the software.

• Link Layer Discovery Protocol (LLDP) (802.1AB)

A layer 2 protocol that allows a network device to advertise its identity and capabilities on the local network.

• Multiple virtual functions per Ethernet port

• Network Priority

The CNA supports this feature, which provides a mechanism to enable CEE flow control (802.1Qbb Priority-based Flow Control: Pause 802.1p) on network traffic. In addition, it guarantees mutual exclusion of FCoE and network priorities to ensure proper enhanced transmission selection (ETS). This feature is not supported on HBAs.

This feature does not need enabled on the CNA or switch. Specific CEE attributes, including priorities for FCoE traffic, are configured on the FCoE switch. These attributes propagate to the CNA CEE port through the DCBCXP. CNA firmware processes this information and derives priorities for network traffic. The network driver is notified of the network priority and tags both FCoE and Network frames with their priorities.

• Priority-based flow control (802.1Qbb)

Defines eight priority levels to allow eight independent lossless virtual lanes. Pauses traffic based on the priority levels and restarts traffic through a high-level pause algorithm.

• Receive side scaling (RSS) feature for advanced link layer

Enables receive processing to be balanced across multiple processors while maintaining in-order delivery of data, parallel execution, and dynamic load balancing.


Tree node pop-up menus 1

• TCP segmentation offload (TSO) and large send offload (LSO)

Large chunks of data must be segmented to smaller segments to pass through network elements. LSO increases outbound throughput by reducing CPU overhead. Offloading to the network card, where segmentation can be done by the Transmission Control Protocol (TCP), is called TCP segmentation.

• Virtual function-level statistics

• VLAN (802.1Q)

A Virtual LAN (VLAN) is a way to provide segmentation of an Ethernet network. A VLAN is a group of hosts with a common set of requirements that communicate as if they were attached to the same LAN segment, regardless of their physical location. A VLAN has the same attributes as a physical LAN, but it allows for end stations to be logically grouped together. The CNA supports multiple VLANs on ports.

• VLAN filtering and tagging

A mechanism that allows multiple networks to transparently share the same physical network link without leakage of information between networks. Switches are configured to insert an appropriate VLAN tag into all data frames arriving from devices in a given VLAN. After the frames are switched, the VLAN tag is stripped before the frame is sent back to the devices. In this way, traffic from devices in one VLAN cannot be leaked to another VLAN.

• VLAN discovery using proprietary logic

Provides the ability to discovery VLANs in the Ethernet network.

• VMware NetQueue

Improves performance in 10 GbE virtualized environments. Requires MSI-X support on host system.

• BIOS support:

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

- Unified Extensible Firmware Interface (UEFI)

- PCI BIOS 2.1 or later

Tree node pop-up menusYou can use the HCM GUI main menu or the Brocade Command Line Utility (BCU) to configure, monitor, and troubleshoot your SAN components. The instructions for using each feature are detailed in subsequent chapters of this document. For each SAN component, you can optionally right-click its icon and a pop-up menu displays (see Table 3).

NOTEHCM features display differently depending on the configuration. All drivers install for the CNA and only the storage driver installs for an HBA.


Tree node pop-up menus1

TABLE 3 HCM tree pop-up menus

SAN component Pop-up menu feature

Host Refresh AllView Name DisplayStart PollingDefine NamesUpdate Boot ImageUpdate DriverBasic Port ConfigurationPersistent BindingAuthenticationChange Agent or HCM User PasswordTeaming (for Windows) Teaming VLANHCM Logging LevelsSyslogStatistics > TeamingPerformance > Enable Historical Data CollectionSupportSaveBackup HCM DataRestore HCM Data, VLAN, and TeamTree > Copy | Search | Collapse All | Expand All

Converged Network Adapter (CNA), 10 Gbps

RefreshView Name DisplayStart PollingDefine NamesUpdate Boot ImageBasic Port ConfigurationPersistent BindingDiagnosticsEnable FC TrunkingEnable AdapterAuthenticationChange Agent or HCM User PasswordHCM Logging LevelsSyslogStatistics > PortPerformance > Enable Historical Data CollectionSupportSaveBackup HCM DataRestore HCM Data, VLAN, and TeamTree > Copy | Search | Collapse All | Expand All


Tree node pop-up menus 1

CEE Port RefreshView Name DisplayStart PollingDefine NamesPort Configuration > Basic | AdvancedDiagnosticsBeacon > Port | LinkChange Agent or HCM User PasswordHCM Logging LevelsSyslogStatistics > Port | CEE | FCP IM Module | FirmwarePerformance >Real-time Historical Statistics | Enable Historical Data CollectionSupportSaveBackup HCM DataRestore HCM Data, VLAN, and TeamTree > Copy | Search | Collapse All | Expand All

FCoE Port RefreshView Name DisplayStart PollingDefine NamesPersistent BindingVirtual Port > Create | DeleteEnable PortFC-SP > Authentication | Authentication StatisticsChange Agent or HCM User PasswordHCM Logging LevelsSyslogStatistics > Fabric | IOC | FCoE Backup HCM DataRestore HCM Data, VLAN, and TeamTree > Copy | Search | Collapse All | Expand All

Ethernet Port RefreshView Name DisplayStart PollingDefine NamesVLAN ConfigurationChange Agent or HCM User PasswordHCM Logging LevelsSyslogStatistics > Eth | Eth IOC | VLANBackup HCM DataRestore HCM Data, VLAN, and TeamTree > Copy | Search | Collapse All | Expand All

TABLE 3 HCM tree pop-up menus (Continued)


Drivers1

DriversThree types of adapter drivers are provided in installation packages:• Storage driver - This is a unified driver that provides Fibre Channel frame transport for Brocade

HBAs and FCoE transport for Brocade CNAs. The adapter logic detects either a FCoE or Fibre Channel network and the appropriate driver support is provided automatically.

NOTEThe unified storage driver will claim all installed Brocade Fiber Channel HBAs, as well as FCoE CNAs installed in a system. This driver will be used instead of the driver originally installed for the HBA.

• Network driver - This is the driver for frame transport over Ethernet and basic Ethernet services. This driver only applies to CNAs.

• Intermediate driver - This is for Windows systems only. It provides support for multiple VLANs on ports. This driver only applies to CNAs.

Brocade HBA4 Gbps or 8 Gbps

RefreshView Name DisplayDefine NameUpdate Boot ImageBasic Port ConfigurationPersistent BindingDiagnosticsAuthenticationChange Agent or HCM User PasswordHCM Logging LevelsSyslogStatistics > Port StatisticsTree > Copy | Search | Collapse All | Expand All

HBA Port RefreshDefine NamesPort Configuration > Basic | AdvancedVirtual Port > Create | DeleteDiagnosticsFC-SPEnable PortPersistent BindingStatistics > Port | FCP IM Module | Fabric | IOC | QoSTree > Copy | Search | Collapse All | Expand All

Base Port RefreshLogical Port StatisticsTree > Copy | Search | Collapse All | Expand All

Device RefreshDefine NamesStatistics > Target | FCP IMTree > Copy | Search | Collapse All | Expand All

TABLE 3 HCM tree pop-up menus (Continued)


Adapter support 1

The firmware is packaged with both the Storage driver and the Network driver so that it can be downloaded by either of the drivers. The firmware is also stored in the flash for SAN boot.

For more information about the driver packages, support for the drivers, and driver installation, refer to the Brocade Adapters Installation and Reference Manual.

Adapter supportThe HBAs and CNAs are supported on the operating systems listed in Table 4.

NOTEHCM cannot be installed on Windows Server Core.

For a complete list of supported operating systems for the Ethernet link layer driver and the FC/FCoE driver, refer to the Brocade Adapters Installation and Reference Manual.

For the latest support information, refer to the release notes for your adapter software version.

TABLE 4 Adapter operating system support

Type of adapter Description of adapter Operating systems supported

Host Bus Adapter

815 8 Gbps HBA, 1 port Linux, Windows, VMware, Solaris




804 8 Gbps HBA dual port card for HP Blade Server

Linux, Windows, VMware

Converged Network Adapter

1741M 10 Gbps CNA, 2 port Linux, Windows, VMware, Solaris

1007 10 Gbps CNA, 2 port for IBM Blade Center Linux, Windows, VMware

1010 10 Gbps CNA, 1 port Linux, Windows, VMware, Solaris

1020 10 Gbps CNA, 2 port Linux, Windows, VMware, Solaris


Adapter support1



Chapter

2
Getting Started with HCM Software
In this chapter•HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

•HCM main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

•Legend Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

•Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

•Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

HCM software launchThe following procedures describe how to launch the HCM application in Windows, Linux, and Solaris.

• “Launching the application on Windows platforms”

• “Launching the application on Linux platforms” on page 14

• “Launching the application on Solaris platforms” on page 14

Launching the application on Windows platformsAfter installing the HCM software, locate Brocade HCM on the Windows platform by selecting Start > Programs > Brocade Adapter Software > Host Connectivity Manager.

OR

Click the desktop icon to launch the application.

Figure 1 shows the screen that appears when HCM software is first launched.

FIGURE 1 HCM Login dialog box

The factory default user ID and password are Administrator and password. After you log in for the first time, you should change the default password to a new one using the HCM GUI.

13

HCM software launch2

Launching the application on Linux platformsAfter installing the HCM software, locate Brocade HCM on the Linux platform.

• If using a GNOME shell, double-click the Host_Connectivity_Manager icon to launch the application.

• If using a KDE shell, click the Host_Connectivity_Manager icon to launch the application.

OR

Start the application from the command prompt using the following commands:

suse116208:~ # cd /opt/brocade/adapter/client

suse116208:<installed directory>/adapter/client # ./Host_Connectivity_Manager

Launching the application on Solaris platformsAfter installing the HCM software, you can launch the Brocade HCM application on the Solaris platform by double-clicking on the Host_Connectivity_Manager icon.

OR

Start the application from the command prompt using the following commands:

sun-116190# cd <installed directory>/adapter/client/

sun-116190# ./Host_Connectivity_Manager

Remember passwordThe Login dialog has a check box to remember the password. If you check the Remember password check box, you do not need to enter the password the next time you launch the application.

Skip login Take one of the following actions to manage the Skip Login feature.

• Enable Skip Login by checking the Skip Login Dialog check box.

If the Skip Login check box is checked, it automatically disables the Remember password option.

• Disable Skip Login by setting hba-application.skip-login=false in the <user home>\HCM\data file.

• Select the Skip Login check box if you do not want the Login dialog box to appear the next time the application is started.


HCM software launch 2

Changing an HCM application passwordYou can change the default password of the application to a different password using the Change HCM Password dialog box.

Note the following when you change a password:

• You must validate your user identity by supplying your old password before you can change to a new password. The new password must be different than the old password.

• The password can begin with an alphabetic, numeric, or special character.

• The default minimum and maximum length of the password is 8 and 64 characters. You can configure the password length in the HBAApplication.properties file:

# min chars for the application passwordpassword_min=8#max chars for the application passwordpassword_max=64

• The password is encrypted and stored in the noitacitnehtua.properties file.

1. From the Host Connectivity Manager, select Configure > Change Password > Change Password for HCM User.

The Change HCM Password dialog box, shown in Figure 2, displays.

FIGURE 2 Change HCM Password dialog box

2. Type the current password for the account. The default user name and password are Administrator and password.

3. Type the new password of the account.

The new password must have at least one character different from the old password.

4. Retype the new password in the Confirm New password field.

5. Click OK.

NOTEBoth the user name and passwords are case-sensitive.


HCM software launch2

Changing an HCM agent passwordYou can change the default password of the agent to a different password using the Change HCM Agent Password dialog box.

Note the following when you change a password:

• You must validate your user identity by supplying your old password before you can change to a new password. The new password must be different than the old password.

• The password can begin with an alphabetic, numeric, or special character.

• The default minimum and maximum length of the password is 8 and 64 characters. You can configure the password length in the HBAApplication.properties file:

# min chars for the application password

password_min=8

#max chars for the application password

password_max=64

• The password is encrypted and stored in the noitacitnehtua.properties file.

1. From the Host Connectivity Manager, click Configure > Change Password > Change Agent Password.

The Change HCM Agent Password dialog box, shown in Figure 3, displays.

FIGURE 3 Change HCM Agent Password dialog box

2. Type the current password for the account. The default user name and password are admin and password.

3. Type the new password of the account.

The new password must have at least one character different from the old password.

4. Retype the new password in the Confirm New password field.

5. Click OK.

NOTEBoth the user name and passwords are case-sensitive.


HCM software launch 2

HCM configuration data HCM configuration data is compatible between HCM software versions 2.3.x.x, 2.2.x.x, 2.1.x.x, 2.0.x.x, and 1.1.x.x. Configuration data that is backed up when prompted during software removal with the Adapter Software Uninstaller and when using the HCM Backup dialog box includes the following:

The following application configuration files are backed up in the data directory:

• HBAApplication.properties

• SetupDiscovery.properties

• HbaAliasdb.properties

• log4j.xml

• noitacitnehtua.properties

• Syslog.properties

• Logging.properties

Restore DataYou can use the Restore Data dialog box to restore data that has been previously backed up. The Host Connectivity Manager (HCM) stores the location and version details of the most recently-taken backed up data and automatically points to the location of the data.

NOTEUse HCM 2.1 or later to restore backed up data. HCM 2.0 and earlier versions do not support the Restore Data feature.

The following data is restored:

• HBA application configuration data (HBAApplication.properties)

• HCM user authentication data (noitacitnehtua.properties)

• Alias Configuration data (HbaAliasdb.properties)

• Setup Discovery data (SetupDiscovery.properties)

• Syslog data (Syslog.properties)

• HCM Logging data (logging.properties and log4j.xml)

• SupportSave

Restoring backed up data

You must use HCM 2.1 or later to restore backed-up data.

1. Select the host, an HBA, or a port from the device tree.

2. Select Tool > Restore > HCM Data from the main menu.

The Restore Data dialog box, shown in Figure 4, displays.


HCM main window2

FIGURE 4 Restore Data dialog box

3. Click the Restore from previous backup data at option, and then click Browse and navigate to where the last backed up file resides.

OR

Click the Restore default data at option. If you click this option, the Browse field is grayed out and the last restored data file is automatically retrieved.

4. Click Start Restore.

5. Restart the HCM application for the restoration to take effect.

The backed up data that you selected is restored.

Restoring existing VLANs and teams

You must use HCM 2.2 or later to restore VLANs and teams. This is a Windows-only feature.

1. Select a host, a CNA, or a CEE port from the device tree.

2. Select Tool > Restore > VLAN and Team from the main menu.

An HCM message displays when the restoration is complete.

HCM main windowFrom the Host Connectivity Manager main window shown in Figure 5, you can manage all the adapters installed in this computer. Alternatively you can manage adapters installed in remote computers, if the computers are networked. Only one host can be managed at a time; multiple host management is not supported.

Refer to the Brocade Adapters Installation and Reference Manual for instructions on how to install both the driver and GUI, the driver only, or the GUI only.


HCM main window 2

FIGURE 5 Host Connectivity Manager main window

1. Menu bar2. Device tree window3. Master Log4. Online help5. System information

1.

2.

3.

6. Context view

5.

4.

6.


Legend Help menu2

Legend Help menuTo display the HCM product icons and the event severity icons, select Help > Legends from the Host Connectivity Manager.

HCM product iconsOn the left side of the Host Connectivity Manager, there is a navigation tree for representing the managed host with adapters and ports. Each tree node has an icon to represent the type of node. If the operational status is offline, link-down, or error, a small red diamond appears on the upper right corner of the icon.

Table 5 shows the product icons that represent the components that HCM manages.

TABLE 5 HCM product icons

Host (agent up) Remote Port (Initiator) online

Host (agent down) Remote Port (Initiator) offline

HBA online Remote Port (Target) online

HBA offline Remote Port (Target) offline

CNA offline Ethernet Port

Port (with SFP) link up Base Port (link up)

Port (with SFP) link down

Base Port (link down)

Port (without SFP) link up

Virtual Port (online)

Port (without SFP) link down

Virtual Port (offline)

Mezzanine card LUN

Pre-boot configured device

Beacon status

FCoE Port


Discovery 2

Event severity iconsTable 6 describes the icons that represent the four event types. Event filtering enables you to block events based on user-defined criteria (severity or type of log). Events that have been filtered out do not appear in the Master Log, For information about how to filter events, see “Filtering event log entries” on page 71.

DiscoveryDiscovery enables you to contact the adapters present in a specified host in your SAN. The setup discovery profile is saved in the SetupDiscovery.properties file to remember the history of each host and related attributes of discovered hosts.

When you log in to HCM, the specified host is automatically contacted (discovered) and displayed on the navigation tree. By default, the local host is automatically contacted (discovered) and displayed on the navigation tree. When you configure and turn on discovery, the application discovers Brocade adapters in that host, connected to the SAN.

NOTEThe HCM application enables you to discover Brocade adapters, ports, virtual ports, remote ports, and LUNs using out-of-band discovery only.

TABLE 6 HCM Master Log icons

Icon Description

Critical-level messages indicate that the software has detected serious problems that will eventually cause a partial or complete failure of a subsystem if not corrected immediately; for example, a power supply failure or rise in temperature must receive immediate attention.

Major messages represent conditions that do not impact overall system functionality significantly. For example, timeouts on certain operations, failures of certain operations after retries, invalid parameters, or failure to perform a requested operation.

Minor messages highlight a current operating condition that should be checked or it might lead to a failure in the future. For example, a power supply failure in a redundant system relays a warning that the system is no longer operating in redundant mode and that the failed power supply needs to be replaced or fixed.

Information-level messages report the current non-error status of the system components; for example, the online and offline status of a fabric port.


Discovery2

Setting up out-of-band discovery for an adapterWhen performing out-of-band discovery, you are managing the adapter remotely. The application connects to the agent running on the host server over the IP network and product information is copied back from the Brocade adapter to the server. If you do not configure the application to directly discover the devices, the connections and attached devices may not display correctly.

1. From the Host Connectivity Manager, click Discovery > Setup.

The Setup for Discovery dialog box, shown in Figure 6, displays.

FIGURE 6 Setup for Discovery dialog box

2. From the Host Name list, select the host name from where you will discover the adapter.

For the first time, the Host Name list will contain only the Local host. You must specify the host name or the IP address for discovering the remote servers. Only previously-discovered servers are available in the Host Name list.

3. Type the port number in the Port Number text box. The default is 34568.

4. Type in the user ID and password that will authenticate the SAN product with the agent. The default user ID and password are admin/password.

It is recommended you change the agent password on the host for security reasons.

NOTEClick the Remember Host check box if you do not want to type it in each time you set up discovery.

5. In the Polling Frequency (seconds) text box, specify the value for how frequently the application has to poll for newly discovered devices.

All parameters related to the adapters that are installed in that server are refreshed each time the poll occurs.

NOTEIf the Keep Polling check box is selected, polling occurs after the specified polling interval. If the check box is not selected, polling stops.

6. Click OK.


Logging off HCM 2

Logging off HCMEnd the HCM session using one of the following methods:

• From the Host Connectivity Manager, click File > Exit.

• Click the X in the upper-right corner of the HCM window to close it.


Logging off HCM2



Chapter

3
Host Configuration
In this chapter•Host security authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

•Buffer credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

•Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

•Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

•Driver update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

•PXE boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

•Virtual port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

•HCM logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

•Advanced port configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

•Name configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

•NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

•Teaming configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

•VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

•Management application support for FCoE. . . . . . . . . . . . . . . . . . . . . . . . . . 63

Host security authenticationUse the HCM GUI or the Brocade command line utility (bcu) to display the authentication settings and status. There are five well-known DH groups; however, only DH-CHAP group 0, called NULL DH, is supported in this release.

NOTESecurity authentication is not supported on Solaris platforms.

25

Host security authentication3

Configuring security authentication using HCM (Host and HBA)You can access the Fibre Channel Security Protocol Configuration dialog box by selecting the Host, an HBA, or an HBA port from the device tree.

NOTEFibre Channel Security Protocol (FC-SP) is not available for Solaris platforms.

1. Select the appropriate device based on how you want to configure security authentication:

• From the host level, select the host from the device tree.

• From the HBA level, select the adapter from the device tree.

• From an HBA port, select a port from the device tree. Security authentication is not supported on the CEE port or the Ethernet port.

2. Select Configure > Authentication from the main menu, or perform the appropriate following step to open the security authentication dialog box:

• From the host level, right-click the host and select Authentication from the list.

The Fibre Channel Security Protocol Configuration (host level) dialog box displays, as shown in Figure 7.

• From the adapter level, right-click the adapter and select Authentication from the list.

The Fibre Channel Security Protocol Configuration (adapter level) dialog box displays. This dialog box is identical to the Fibre Channel Security Protocol Configuration (host level) dialog box.

• From the adapter port level, right click a port and select FC-SP > Authentication from the list.

The Fibre Channel Security Protocol Configuration dialog at the host level displays.

FIGURE 7 Fibre Channel Security Protocol Configuration - host-level dialog box


Host security authentication 3

3. Configure the following parameters on the Port Security Authentication tab:

a. Select the Enable Authentication check box to enable or disable the authentication policy.

If authentication is enabled, the port attempts to negotiate with the switch. If the switch does not participate in the authentication process, the port skips the authentication process.

b. Type and retype the secret.

The maximum length of the secret is 63 bytes. The default secret for each interface is its port world wide name (PWWN) without the colons; for example, 0102030405060708. Select the algorithm type from the list:

• MD5 - A hashing algorithm that verifies a message’s integrity using Message Digest version 5.

• SHA1 - A secure hashing algorithm that computes a 160-bit message digest for a data file that is provided as input.

• MD5SH1 - Similar to the MD5 hashing algorithm, but used for DH-CHAP authentication.

• SHA1MD5 - Similar to the SHA1 hashing algorithm, but used for DH-CHAP authentication.

c. Select DHNULL as the group value (this is the only group that is supported).

4. Click Apply to apply the changes.

5. Click OK to save the changes and close the dialog box.

Configuring security authentication using the BCUEnter the following commands to display or configure security authentication for the ports:

• bcu auth --algo <port_id> <md|sha1|ms|sm>

• bcu auth --policy <port_id> {on|off}

• bcu auth --secret <port_id> “secret_string”

• bcu auth --show <port_id>

• bcu auth --stats <port_id>

• bcu auth --statsclr <port_id>

Refer to “auth” on page 194 for details about these commands.


Buffer credits3

Buffer credits Buffer-to-buffer credit flow control is implemented to limit the amount of data a port sends, based on the number and size of the frames sent from that port. This scheme allows Fibre Channel to be self-throttling, thereby allowing it to establish a reliable connection without the need to accommodate dropped frames due to congestion. Buffer credit limits between each device and the fabric are communicated at the time of fabric login. One buffer credit allows a device to send one frame of data (typically 1 or 2 KB). Buffer credits cannot be configured on an adapter.

The default BB Credit is 1. The baseline for the calculation is one credit per kilometer at 2 Gbps. This yields the following values for 10 km:

• 5 credits per port at 1 Gbps




Refer to the “Extended Fabrics concepts and planning” section of the Fabric OS Administrator’s Guide for detailed information about buffer credits.

Basic port configuration For each port, you can configure the following parameters using the Basic Port Configuration dialog box, the Brocade Command Line utility (BCU), or both. Table 7 lists the features and configuration options.

NOTEYou can view the converged enhanced ethernet (CEE) configuration using the Host Connectivity Manager (HCM), but you cannot configure the CEE switch using the HCM. To configure and manage the CEE switch, refer to the Converged Enhanced Ethernet Administrator’s Guide.

TABLE 7 Basic port configuration options

Port configuration parameterConfigurable using HCM

Configurable using the BCU For more information

Port logging level1 Yes Yes “Port logging level”

Configure speed Yes Yes “Port speed”

Frame data field size Yes Yes “Frame data field size”

Persistent BindingNote: The persistent binding option is available on Windows platforms only.

Yes Yes “Persistent binding”

QoS (HBA only) Yes Yes “QoS (HBA only)”

Path Time OutNote: Path time out value (pathtov) is valid for firmware version 2.0 and higher. It is not supported on the Solaris operating system.

Yes Yes “Path time out”


Basic port configuration 3

Opening the Basic Port Configuration dialog box You can access the Basic Port Configuration dialog box by selecting the Host, an HBA, or an HBA port a CNA, or an FCoE port from the device tree.

NOTEThere are slight changes in the HCM Basic Port Configuration dialog box, depending on the operating system. The MPIO mode enable check box is grayed out if HCM is managing a driver version later than than 2.0.0. The MPIO mode feature is no longer supported.

1. Select a device from the device tree.

2. Select Configure > Basic Port Configuration from the main menu.

The Basic Port Configuration dialog box, shown in Figure 8, displays.

FIGURE 8 Basic Port Configuration dialog box - Windows, Linux, and VMware

Target Rate Limiting Yes Yes “Target rate limiting”

FCP-IM IO profile on Yes Yes

1 If an Ethernet port is selected, the Basic Port Configuration dialog displays an additional feature called“Eth Logging Level.”

TABLE 7 Basic port configuration options (Continued)


Basic port configuration3

Port logging levelThe number of messages logged by the host depends on the predetermined logging level. Although the adapter might generate many messages, only certain types of messages are logged based on the specified logging level.

Configuring the port logging level using HCM

1. Select Configure > Basic Port Configuration from the Host Connectivity Manager.

The Basic Port Configuration dialog box displays.

2. Select a value from the Port Logging Level list.

Supported values are Log Critical, Log Error, Log Warning, Log Info, and Log Invalid.


4. Click OK to save the changes and close the window.

Configuring the port logging level using the BCU

Enter the following command to set the logging level on the port.

bcu log --level <port_id> [<level>] [-m <fw|ha1|fcs|drv|aen|all>]

Refer to “log” on page 231 for details about this command.

Ethernet logging levelThe number of messages logged by the host depends on the predetermined logging level. Although the Ethernet port might generate many messages, only certain types of messages are logged based on the specified logging level.

Configuring the Ethernet logging level using HCM

1. Select an Ethernet port from the Host Connectivity Manager device tree.



3. Select a value from the Eth Logging Level list.

Supported values are Log Critical, Log Error, Log Warning, Log Info, and Log Invalid.


5. Click OK to save the changes and close the window.

Configuring the Ethernet logging level using the BCU

Enter the following command to set the logging level on the port.

bcu ethlog --level <port_id> [<level>]

Refer to “ethlog” on page 212 for details about this command.



Port speedPort speed is the maximum amount of data that can pass through the port at a given second. The unit of measurement is in gigabits per second (Gbps). The available speed options depend on the HBA’s speed and the port’s SFP. Auto-negotiate is the recommended setting and it is the default.

Speed options for the 4 Gbps HBA (425 and 415) are 1 Gbps, 2 Gbps, 4 Gbps, and 8 Gbps. The 8 Gbps HBA supports the 1 Gbps speed at the driver level, but it does not support 1 Gbps in a BIOS/BOS configuration.

Configuring the port speed using HCM



2. Select a value from the Configured Speed list.


A port disable/enable configuration dialog box displays, confirming the configured speed, which will take effect when the port is disabled or enabled.

4. Click Yes to continue, or No to cancel the operation.

5. Click OK to close the window.

Configuring the port speed using the BCU

Enter the following command to set the port speed.

bcu port --speed <port_id> [<speed>]

Refer to “port” on page 239 for details about this command.

Frame data field sizeBuffer credits determine the maximum amount of frame data. If the number of buffer credits is not large enough to handle the link distance and speed, performance can be severely limited.

See “Buffer credits” on page 28 for information about buffer credits.

Specifying the maximum frame size using HCM



2. Select the frame size from the Frame Data Field Size list. Options include 512, 1024, 2048, 2112 Mbps and auto. The default value is 2112.

3. Click Apply to apply the change.




Configuring the frame data field size using the BCU

The dfsize command sets the ports maximum receive data field size. If you do not specify a value, the driver default receive buffer size displays, which is 2112.

NOTEThe new receive data field size takes effect when the port is re-enabled.

Enter the following command to set the frame data field size.

bcu port --dfsize <port_id> [<dfsize>]

Refer to “port” on page 239 for details about this command.

Persistent bindingPersistent binding enables you to permanently assign a system SCSI target ID to a specific FC device. Persistent binding can be achieved by binding to world wide port name (WWPN), world wide node name (WWNN), or device ID (DID).

You can access the Persistent Binding dialog box by selecting the Host or an HBA, a CNA, a CEE port, or an FCoE port from the device tree.

Enabling and disabling persistent binding using HCM

Persistent binding can be enabled or disabled from the HCM GUI using the following steps:

1. Launch the Basic Port Configuration dialog box at the port level.

2. Select or clear the Persistent Binding check box in the Basic Port Configuration dialog box.

NOTEThe Persistent Binding check box is not available for Solaris agents.

Enabling and disabling persistent binding using the BCU

Target persistent binding enables target port world wide name binding to a persistent target ID for the OS stack. Using the -list operand, you can query the list of mappings from the persistent binding module.

Enter the following commands to configure target persistent binding:

• bcu pbind --list <port_id> [<pwwn>]

• bcu pbind --clear <port_id>

Refer to “pbind” on page 236 for details about this command.



FC TrunkingThe FC Trunking feature works in conjunction with the trunking feature on Brocade switches, whereby the Fabric Operating System (FOS) provides a mechanism to trunk different switch ports of the same port group into one. When FC trunking is enabled, two physical ports belonging to the same Brocade dual-port HBA are trunked together to form a logical Fibre Channel port. Both HBA ports must be operating at the same speed while in trunk mode.

The following licenses must be installed on the switch connected to the HBA port.

• Server Application Optimization (SAO) license

• Trunking license

Before enabling trunking, consider the following requirements:

• When Trunking is enabled, a trunked logical port (Port 0) is created and reported per adapter. Most BCU commands are applicable in this logical port's context only.

• When configuring Fabric Zones, LUN Masking at the Storage, use the PWWN for Adapter port 0.

• Before enabling trunkng on the adapter, you must first enable trunking on the connected switch and assign the trunk area.

• Both adapter ports should be connected to the same port group on the switch.

• Only two ports on the same HBA can participate in trunking and both of these should be operating at the same speed.

• N_Port Trunking is supported on the dual port cards only: 425 and 825 HBAs.

• N_Port Trunking is on supported on 8 Gbps ports installed on switch models using Fabric OS 6.4.1 or later.

Disabling trunking

By default, the trunking feature is disabled on the HBA. If the trunking feature is enabled, you must do the following to disable the trunking on an HBA:

Disabling trunking if the adapter is used to boot over SAN

1. Disable port 1 (the second port) on the HBA using BCU commands or HCM.

2. Disable trunking on the HBA using BCU commands or HCM.

3. Shut down the operating system.

4. Disable trunking on the switch by disabling the previously-assigned trunk area.

5. Start the operating system.

6. Enable port 1 (the second port) on the HBA using BCU commands or HCM.

Disabling trunking If the adapter is not used to boot over SAN

1. Disable port 1 (the second port) on the HBA side using BCU commands or HCM.

2. Disable trunking on the HBA using BCU commands or HCM.

3. Disable trunking on the switch by disabling the previously-assigned trunk area.

4. Enable port 1 (the second port) on the HBA using BCU commands or HCM.



For more information about basic trunk group configuration on a Brocade switch, refer to the Brocade Fabric OS Administrator’s Guide.

Enabling and disabling FC trunking using HCM

1. Select Configure > Enable FC Trunking from the Host Connectivity Manager.

Enable or disable FC Trunking by selecting or clearing the Enable FC Trunking check box.

2. Click Enable Adapter.

FC Trunking is enabled on the selected adapter. The trunking configuration is restored when you reboot the host.

Enabling and disabling FC trunking using the BCU

Enter the following commands to configure FC trunking:

NOTEThe adapter ID can be any of the following: adapter index, serial number, adapter name, or hardware path.

• bcu trunk --enable <ad_id>

• bcu trunk --disable <ad_id>

• bcu trunk --query <ad_id>

Refer to “trunk” on page 255 for details about this command.

QoS (HBA only)

NOTEThe QoS feature is not supported on the converged network adapter (CNA).

Quality of Service (QoS) works in conjunction with the QoS feature on Brocade switch F_Ports. The Fabric operating system (FOS) provides a mechanism to assign traffic priority (high, medium, or low) for a given source and destination traffic flow. By default, all flows are marked as medium.

This feature is supported only on 8 Gbps HBA ports installed on specific switch models that use Fabric OS 6.2 and later. 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. Refer to the Fabric OS Administrator’s Guide for detailed information about QoS.

Configuring QoS on the switch side using the BCU

On the switch side, you can create QoS zones using the PWWNs that correspond to devices in a source/destination traffic flow. You need a Server Application Optimization (SAO) license installed on the switch to enable QoS. In addition, an Adaptive Networking (AN) license is required on the switch to enable QoS on the switch ports.



You enable or disable QoS settings on ports with the portCfgQos command. Refer to the Fabric OS Administrator’s Guide for details about this command on the switch side.

Configuring QoS on the HBA side using the BCU

There are three possible QoS states:

• Enabled, online - QoS is established with the switch.

• Enabled, offline - QoS negotiation failed and QoS was not established with the switch. Possible reasons for failure could be the license is not installed on the switch or QoS is not enabled on the port.

• Disabled.

NOTEYou must first enter the bcu port --disable <port_id> command, followed by the bcu port --enable <port_id> command, before the bcu qos --enable or bcu qos --disable commands take effect.

Enter the following commands to enable or disable QoS support on the HBA side:

• bcu qos --enable <port_id>

• bcu qos --disable <port_id>

• bcu qos --query <port_id>

• bcu qos --stats <port_id>

• bcu qos --statsclr <port_id>

Refer to “qos (HBA only)” on page 246 for details about this command.

Path time outWith path time out values (TOV), you can either force an immediate failover (by setting the TOV to 0) or you can specify a delay in seconds (1-60 seconds). The default TOV is 30.

Specifying path time out using HCM



2. Type a value in the Path Time Out field.


Specifying path time out using the BCU

Enter the following command to specify the optional path time out value in seconds (1 to 60). The default TOV is 30 seconds. A value of 0 is not allowed from the BCU.

bcu fcpim --pathtov <port_id> tov

Refer to “fcpim” on page 221 for details about this command.



Target rate limitingThe target rate limiting feature is used to minimize congestion at the adapter port caused by a slow drain device operating in the fabric at a slower speed. A remote port’s operating speed is determined from the fabric, and then the information is used to throttle the transmitted traffic rate to that remote port. Traffic destined to the remote port is limited to its current operating speed.

Limiting the data rate to slower targets ensures that there is no buffer-to-buffer credit back-pressure between the switch due to a slow-draining target.

Enabling and disabling rate limiting on the adapter side using HCM

Target rate limiting is supported only when the adapter port is connected to the fabric. Therefore, target rate limiting is not supported when the port is directly connected with another device.



2. Enable the Target Rate Limiting feature by clicking the corresponding check box.

3. Select the default rate limit from the list. Options include 1 Gbps, 2 Gbps, and 4 Gbps. The default is 2 Gbps.


Enabling and disabling rate limiting on the adapter side using the BCU

Enter the following commands to enable or disable rate limiting on the adapter side:

NOTEYou must first enter the bcu port --disable <port_id> command, followed by the bcu port --enable <port_id> command, before the bcu ratelim --enable or bcu ratelim --disable commands take effect.

• bcu ratelim --enable <port_id> ]

• bcu ratelim --disable <port_id>

• bcu ratelim --query <port_id>

• bcu ratelim --defspeed <port_id> [<1|2|4>]

Refer to “ratelim” on page 247 for details about this command.

FCP-IM profileFCP-IM profiling is used to gather the IO latency information based on IO size. The IO latency feature is turned on at the physical port level; however, profile data is gathered at the I-T nexus level.

If the FCP-IM Profile feature is turned on, the driver firmware categories the IO latency data into average, minimum, and maximum categories for the following IO sizes:

• Less than or equal to 8,000 IOs

IO latency minimum, maximum, and average is less than 54 milliseconds (ms).

• Greater than 8,000 but less than or equal to 64,000 IOs










• Greater than 512,000 but less than or equal to 1,000,000 IOs


• Greater than 1,000,000 IOs

IO latency minimum: 96 ms, IO latency maximum: 128 ms, IO latency average: 109 ms.

Enabling and disabling FCP-IM profile using HCM

Complete the following steps to set the port IO profiling to on or off using the HCM:



2. Enable the FCP-IM IO profile on feature by clicking the corresponding check box.


Enabling and disabling FCP-IM profile using the BCU

Enter the following commands to set the port IO profiling to on or off using the BCU:

--profile_on Sets the port IO profiling on. When set to on, the IO profile gathers the IO latency information based on size (average, minimum, and maximum).

port_id Specifies the ID of the module on which you want to set the profiling to on.

--profile_off Sets the port IO profiling off.

port_id Specifies the ID of the module on which you want to set the profiling to off.

Refer to “fcpim” on page 221 for details about this command.


Boot over SAN3

Boot over SAN Boot over SAN configuration using the Basic Port Configuration dialog box is enabled on all platforms if the HCM version is 1.1 or higher. The Boot over SAN feature is available for both the HBA and the CNA if the FCoE driver is installed and the version is 2.1 and above. If the driver version is lower than 2.1, Boot over SAN is available only on the HBA.

The Boot over SAN feature allows you to target remote boot devices (LUNs on SAN storage arrays) from which to boot the host system. When the host’s operating system and adapter driver are installed on the remote device, the adapter BIOS and user-configurable boot instructions stored in adapter flash memory allow the host to boot from the device.

NOTEVarious operating systems require you to follow specific guidelines to enable servers to boot from a SAN. Understanding these requirements is key to a successful deployment of a boot over SAN environment.

Boot LUNs are identified to adapter ports using the BIOS Configuration Utility and BCU commands. These utilities also allow you to enable or disable BIOS for booting the host system over SAN, set boot options, and set the port speed. Refer to the Brocade Adapters Installation and Reference Manual for instructions.

BIOS boot over SAN provides the ability for x86 and x86_64 systems to perform booting of the OS installed on the SCSI disk connected over the Fibre Channel SAN. The same BIOS capability is being extended for the CNA on FCoE fabric with enhancements to the FCoE login process (FCF discover and FIP Log-in).

This release will also extend EFI (Extensible Firmware Interface) Device Support for the Brocade Converged Network Adapter.

The maximum number of supported adapters (combined HBA and CNA) is limited to 16 and the maximum targets and LUNs that are displayed during discovery is limited to 256.

After you have configured boot devices using the BIOS Configuration Utility, you can enable or disable BIOS for Boot over SAN, set boot options, and set port speed using the HCM GUI. The port speed for the CNA is fixed at 10Gbps. All configuration information is stored in flash memory.

Configuring Boot over SAN The boot-LUN table lists the vendor information, LUN capacity, and whether the LUNs are accessible. These fields are not editable.

You can access the Boot-over-SAN dialog box by selecting the Host, an adapter or a physical port from the device tree.



2. Click the Boot-over-SAN tab.

The Boot-over-SAN dialog box, shown in Figure 9, displays.


Boot over SAN 3

FIGURE 9 Boot-over-SAN dialog box

3. Click the BIOS Enable check box to enable Boot over SAN.

NOTEAuto Negotiate is the only speed option for the 10 Gbps CNA card.

4. From the Boot Option list, select one of the following:

• Fabric Discovered - Enables Boot over SAN using boot LUN information stored in the fabric. This is the default setting.

• First Visible LUN - Enables Boot over SAN from the first discovered LUN in the SAN.

• User Configured LUNs - Allows the user to select and prioritize the remote target and LUN for booting over SAN.

5. Select the Boot Device Port WWN row in the table, then click the up and down arrows to move the row up or down in the table. The host will attempt to boot from the first LUN in the table, and then move on to succeeding LUNs.

• You can delete a row using the Delete button under the arrows.

• Click the Boot Device Port WWN and LUN fields to physically enter boot LUNs to the table. These LUNs must be visible to the adapter to be accessible as boot LUNs.

6. Click OK.

The Vendor Info, LUN Capacity, and Accessible status that correspond to the selected boot device and LUN display automatically.


Boot over SAN3

Pre-boot configurationAny parameters flagged with pre-boot were configured using a blade system management application. You cannot use HCM to create or modify a pre-boot configuration. If the port has been pre-boot disabled, note the following:

• The BIOS Enable option is disabled.

• The pre-boot configured LUNs in the LUN column are displayed as <LUN wwn> (Pre-boot), as shown in Figure 9. The maximum number of user-configured LUNs supported is four, and the maximum number of pre-boot-configured LUNs is eight.

NOTEFor the Brocade 1007 CNA expansion card, the maximum number of boot LUNs supported in pre-boot configuration is two.

• The configuration changes take affect after the next reset.

Configuring fabric-based boot LUN discovery

Use the following steps to configure fabric-based boot LUN discovery.

1. Set the adapter’s BIOS configuration to auto-discovery using one of the following interfaces:

• Brocade BIOS Configuration Utility

Adapter Settings > Boot LUN > Fabric Discover

• HCM

Refer to “Configuring Boot over SAN” on page 38 for instructions.

• 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 <cfg> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#>

Refer to “boot” on page 199 for details about this command.

3. Configure the zone on the switch using the Fabric OS zoneCreate command. Refer to the Brocade Adapters Installation and Reference Manual or the Fabric OS Administrator’s Guide for more information about creating zones.


Driver update 3

Boot image update You can update a boot image at the host level or at the adapter level.

At the host level, if the HCM version is lower than 2.1, the Update Boot Image menu is enabled only when one HBA is visible. If the agent version is 2.1 and higher, the Update Boot Image menu is always enabled if at least one adapter is visible and will update the image to all visible adapters.

Updating the boot image using HCM

1. Download the boot code (brocade_adapter_boot_fw_v2-2-0-0) from www.brocade.com/hba to a folder on your local drive.

2. Launch HCM.

3. Right-click a host or adapter from the device tree and select Update Boot Image from the list.

• Right-clicking a host downloads the boot image to all adapters that are installed on the host.

• Right-clicking an adapter downloads the boot image to the selected adapter only.

The Update Boot Image dialog box displays.

4. Click the Browse button and navigate to the location of the boot image.

5. Select the boot image and click Open.

The selected file downloads. If an error occurs during the downloading process, an error message displays.

Updating the boot image using the BCU

Enter the following command to update the boot image.

bcu boot --update [adapter_id] <image_file> [-a]

Refer to “boot” on page 199 for details about this command.

Driver updateThe Update Driver feature allows you to update the driver installed on the connected host to the latest version. The update is supported on HCM version 2.3 and higher; downgrades to older HCM versions are not supported.

NOTEThe Solaris operating system requires a reboot for the newly-installed adapter driver update to take effect; therefore, HCM cannot validate that the installation is correct and this is reflected in the Installation Progress Details area, shown in Figure 10.

1. Right-click a host from the device tree and select Update Driver from the list.

The Update Driver dialog box displays.


Driver update3

FIGURE 10 Update Driver dialog box

2. Enter the filename of the updated driver in the Select driver file to upgrade text box

OR

click the Browse button and navigate to the location of the driver file to upgrade.

3. Select the driver file and click Open.

The selected file downloads. If an error occurs during the downloading process, an error message displays.

4. Click the Start Installation button.

5. Review the installation progress details to determine if the driver file installed successfully.

Changing the HCM timeout valueIf a timeout error occurs during adapter driver installation, you can change the Host Connectivity Manager’s time out value by editing the HBAApplication.properties file, which is under <User Home>/HCM/data.

driver.update.start.timeout = 5

driver.update.end.timeout = 5

driver.update.solarisEsx.grace.timeout = 3


PXE boot support 3

PXE boot supportA Preboot Execution Environment (PXE) is a means to leverage Ethernet to acquire and launch files to successfully perform an action or a series of actions (for example, to install an operating system, to run diagnostics, to execute firmware update utilities, or to boot an entire operating system over the network). The PXE boot mechanism is embedded in the firmware of a converged network adapter (CNA).

You can request a PXE boot as an alternative to booting from the local disk or the SAN (boot over SAN). Once PXE boot is initiated, the network adapter makes a DHCP request. The response includes the Dynamic Host Configuration Protocol (DHCP) client IP address for the network adapter and also includes the IP address of a Trivial File Transfer Protocol (TFTP) server, along with a filename of a boot file. The boot file is retrieved over the network and then executed. The boot file then loads other files, such as configuration files and executables.

Refer to the Brocade Adapters Installation and Reference Manual for configuration details.

Configuring PXE boot support 1. Select a CNA from the device tree.

2. Select Configure > Basic Port Configuration from the main menu.

The Basic Port Configuration dialog box, shown in Figure 11, displays.

3. Select the PXE Boot tab.

FIGURE 11 Basic Port Configuration dialog box - PXE Boot tab

4. Click the PXE Boot enable check box to enable PXE Boot.

Ethernet packets are tagged with a VLAN ID. Valid VLAN ID values are from 1 through 4094.

5. Enter the VLAN ID in the VLAN ID field.

6. Click OK.


Virtual port configuration3

Virtual port configurationVirtual ports appear to the hosts as physical ports in the data network. One or more virtual ports are assigned to each host, and a host can access storage at a virtual port only if the virtual port has been assigned to the host.

Virtual port restrictions• You cannot create a virtual port that already exists in the Names dialog box. If you need to

re-create a virtual port that has been deleted through an interface other than the currently-managing HCM or the virtual ports deleted on Linux servers reboot, you must first manually remove the virtual port’s WWN from the Names dialog box in HCM. If you do not manually remove the virtual port from HCM, an error message displays that the virtual port already exists. See “Removing a name entry” on page 52 for instructions on how to manually remove a virtual port.

• The HCM GUI should post an error message for duplicate virtual ports (detected in the Vports.db file) and prompt the user to remove the duplicate, but it does not. Duplicate world wide names are not restricted when the BCU is used to create virtual ports. Do not use the BCU for virtual port management, because it does not handle duplicate virtual port WWNs. Use only the HCM GUI to manage virtual ports.

• Virtual port configurations are not persisted across reboot at the driver level.

Creating a virtual portYou create virtual ports on HBA ports and FCoE ports only; virtual ports are not supported on an adapter. Virtual ports are not supported for VMware and Solaris agents.

1. Select a physical HBA port or an FCoE port from the device tree.

2. Select Configure > Virtual Port > Create from the main menu.

OR

Right-click the physical port and select Virtual Port > Create from the list.

The Virtual Port Creation dialog box, shown in Figure 12, displays. The following fields are system-generated:

• Physical port world wide name.

• Virtual port world wide name - This WWN must be unique.

• Virtual node world wide name - The system returns the default node WWN, which is the physical port node WWN.


Virtual port configuration 3

NOTEBy default, the Use auto-generated check box is selected and the Generate Again button is enabled. You can still edit the Virtual Port WWN field if Use auto-generated is selected.

FIGURE 12 Virtual Port Creation dialog box

3. (Optional). Provide a symbolic name for the virtual port.

4. (Optional). Provide an alias name for the virtual port. By creating an alias, you can assign a familiar name to a device or group multiple devices into a single name. This can simplify cumbersome data entry and allows an intuitive naming structure.

5. (Optional). Enter descriptive information about the virtual port into the Description field.

6. Click OK to apply the changes and close the window.

Deleting a virtual portIf the maximum number of virtual ports have already been created, the option to create virtual ports using HCM is disabled.

NOTEPre-boot-created virtual ports are not labeled. If the virtual port is pre-boot-created, the Delete check box is disabled.

1. Select a virtual port from the device tree.

2. Select Configure > Virtual Port > Delete from the main menu.

OR

Right-click the virtual port and select Virtual Port > Delete from the list.

A warning message displays, asking for confirmation.

3. Click OK.


HCM logging levels3

HCM logging levelsYou can set the log level for the following modules:

• Agent communication log, where all messages are exchanged between the HCM GUI application and the HCM agent.

• HCM debug log, where messages are logged locally.

If you do not set an HCM log level, DEBUG, which is the default, is used.

Configuring the HCM logging level using HCM1. Select Configure >HCM Logging Levels from the Host Connectivity Manager.

The Configure HCM Logging Levels dialog box, shown in Figure 13, displays.

FIGURE 13 Configure HCM Logging Levels dialog box

2. From both the Agent Communication Log and the HCM Debug Log lists, select one of the following:

• Trace

• Debug, the most verbose and the default

• Info

• Warning

• Error

• Fatal, which is the least verbose

3. Click Apply to apply the change.


Advanced port configuration 3

Advanced port configuration You can access the Advanced Port Configuration dialog box by selecting an HBA port or an FCoE port from the device tree.

For each port, you can configure the following parameters using the Advanced Port Configuration dialog box, the Brocade Command Line utility (BCU), or both. Table 8 lists the features and configuration options.

Opening the Advanced Port Configuration dialog box1. Select an adapter port or an FCoE port from the device tree.

2. From the Host Connectivity Manager, select Configure > Port Configuration > Advanced.

The Advanced Port Configuration dialog box, shown in Figure 14, displays.

FIGURE 14 Advanced Port Configuration dialog box

Interrupt Control CoalesceInterrupt control coalescing allows the system to optimize CPU utilization by varying the number of interrupts generated. Increasing the latency monitor timeout value should result in a lower interrupt count and less CPU utilization, which may result in higher throughput.

NOTEIf the discovered agent version is lower than 2.2, the advanced port configuration features are disabled for a converged network adapter (CNA).

You can configure the following interrupt control coalescing parameters per port:

• Interrupt delay time - The host interrupt generation is delayed by the specified duration to coalesce multiple I/O interrupt events into one. Increasing this value results in fewer interrupts per multiple interrupt events.

TABLE 8 Advanced port configuration options

Port configuration parameter Configurable using HCM Configurable using the BCU

Interrupt Control Coalesce Yes Yes

Interrupt Control Latency Yes Yes

Interrupt Control Delay Yes Yes


Advanced port configuration3

• Interrupt latency timer - This value helps to minimize I/O latency by avoiding host interrupt generation to have to wait until the interrupt delay has expired for an I/O throughput.

Configuring the Interrupt Control Coalesce using HCM

1. Select a port from the device tree.

• From the Host Connectivity Manager, select Configure > Advanced Port Configuration.

The Advanced Port Configuration dialog box displays.

OR

• Right-click a port and select Port Configuration > Advanced.

2. Set the latency and delay values:

• Select On from the Interrupt Control Coalesce list.

NOTEInterrupt Control Coalesce is On by default.

• Specify the latency monitor timeout value in microseconds, if coalesce is set to on. Latency timeout values supported are 0-225 microseconds. Setting the latency timeout value to 0 disables the latency monitor time out interrupt.

The default latency values is 225 for an HBA, including the Brocade 804 mezzanine card, and 5 for a CNA).

• Specify the delay timeout value in microseconds, if coalesce is set to on. Delay timeout values supported are 0-1125 microseconds. Setting the delay timeout value to 0 disables the latency monitor time out interrupt.

The default delay value is 1125 for an HBA, including the Brocade 804 mezzanine card, and 25 for a CNA.

• Click OK.


Name configuration 3

Name configurationThe Host Connectivity Manager allows you to configure names as a method of providing familiar, simple names to world wide names for adapters, ports, virtual ports, and remote ports in the SAN. (A logical port can be a base port or a virtual port.) Only unique names are allowed.

NOTEYou can access the Define Name dialog box by right-clicking an adapter, port, remote port, or Virtual Port. You can access the Configure Names dialog box by selecting an HBA, an HBA port, or a Virtual Port, a CNA or a CEE port from the device tree.

You can perform the following name tasks using either the Configure Names dialog box or the Define Names dialog box:

• Associate a name that represents an adapter, port, virtual port, or remote port. Note the following points about names:

- Among all adapters, two cannot have duplicate names.

- Among all the ports, two cannot have duplicate names.

- A port and adapter can have the same name.

- You cannot associate a name for a storage device.

- Name changes on remote ports and virtual ports are sent to the *.properties file local to the HCM application but are not sent to the agent.

• Add a detached WWN and an associated name with Type and operational status as Unknown.

• Remove or disassociate a name from a WWN.

Dual role changes Dual role types were introduced in release 1.1 for situations where an Initiator WWN acts as a Target. In release 2.0, the design was changed to use a MAC or WWN + Type combination, enabling you to set your own name to the port (Initiator) as well as to a remote port (Target).

Since release 2.1, the dual role type has been eliminated, so if you import a data file from a release 2.0 or earlier which has a Dual Role type, the WWN is imported as an "Unknown" type and the application log displays "Dual Role" type is not supported.

If the name you imported already exists in the Names dialog box, the Fix Duplicates dialog box displays, showing the duplicated names. Refer to “Importing duplicated names” on page 54 for more information.

Name validationNote the following when you define a name:

• The name cannot begin with a number.

• The name cannot begin with an underscore ( _ ) or hyphen ( - ), however an underscore or hyphen character is allowed within the name; for example, name1_name-2.

• No special characters are allowed, except for an underscore or hyphen.

• The maximum length of the name is 15 characters.

• The maximum length of the description is 80 characters.


Name configuration3

Defining a nameThe Define Name dialog box enables you to assign a name to an existing world wide name (WWN) or media access control (MAC) address.

1. Select an adapter, a CNA or a CEE port from the device tree.

2. Select Configure > Define Names from the Host Connectivity Manager.

OR

Right-click a device from the device tree and select Define Names.

The Define Name dialog box, shown in Figure 15, displays.

FIGURE 15 Define Name dialog box

3. Enter a WWN or MAC address into the WWN/MAC field.

4. Enter a meaningful name for the selected adapter or port.

NOTEThe type of device is displayed in the Type field. The drop-down list is disabled.

5. Enter a description of the device.

6. Click OK.

Editing the name fieldsOnly the name, the world wide name (WWN), and the description fields are editable. Depending on the component, the following occurs when you edit the name fields:

• Name changes on the adapter and ports are sent to the agent and stored in the *.properties file.

• Name changes on remote ports and virtual ports are sent to the *.properties file local to the HCM application but are not sent to the agent.

1. Select a host, adapter, or port from the device tree.

2. Select Configure > Names from the Host Connectivity Manager.

OR

Right-click a device from the device tree and select Configure > Names.



The Configure Names dialog box, shown in Figure 16, displays all the discovered and detached (undiscovered) names.

FIGURE 16 Configure Names dialog box

3. Select a row and edit the name, the WWN, and the description, as needed.

4. Click OK.

Adding name entriesYou can add up to 2000 names which are then stored in the HbaAliasdb.properties file. The entries persist during reboot.

1. Select an HBA, an HBA port, or a Virtual Port, a CNA or a CEE port from the device tree.


OR

Right-click a device from the device tree and select Configure Names.

3. Type a name that represents an adapter, port, or storage device into the Name field.

4. Type a valid WWN that corresponds to the name. Valid WWW types are as follows:

• Node

• Port

• Remote Port

• V_Port

• Unknown


The new component is added to the Name list.


Name configuration3

Removing a name entryThe Remove functionality clears the name and description values of a selected detached WWN.



OR


The Configure Names dialog box displays all the names available at the host.

3. Select one of the following from the Display list:

• Current Host

• All WWNs

• Only Nodes

• Only Ports

• Only V_Ports

• Only Remote Ports

A list of names for the devices you selected displays.

4. Select a device to highlight it and click the Remove button to remove the discovered device from the list.

The Remove button clears the names of the discovered WWN and the entire row of the detached (undiscovered) WWN.


Exporting the properties for a WWNYou can export the properties for a world wide name in .csv, *.properties, or .txt file format.



OR


The Configure Names dialog box displays.


• Current Host

• All WWNs

• Only Nodes

• Only Ports

• Only L_Ports

• Only V_Ports




4. Click the Export button.

The Save dialog box displays. You can save the properties file in .txt, .csv, or .properties format.

5. Name the file, and click Save.


Importing the properties for a WWNYou can import the properties for a world wide name in .csv, *.properties, or .txt file format.


OR




• Current Host

• All WWNs

• Only Nodes

• Only Ports


3. Click the Import button.

The Open dialog box displays.

4. Navigate to the location of the *.properties file from which you will import properties for the selected device.

5. Name the properties file, and click Open.


Importing properties in EFCM format

You can use this procedure to import properties in Enterprise Fabric Connectivity Manager (EFCM) format.

1. In the Configure Names dialog box, select EFCM Format and then select Import.

2. Click OK.



Name configuration3

The format appears as follows.

# Names Export File V 1.0 : DO NOT DELETE / MOVE / MODIFY THIS LINE # For each row in the file the name should be followed by an '='# Column Format: WWN=Name=Type =Description# EFCM Names file Format [ Delimiter '=' ]####################################################################200000051e536b20=s=Node=200000051e536b43=bfa0=Node=100000051e536b20=a=Port=100000051e536b44=bfa0_port1=Port=100000051e536b43=bfa0_port0=Port=

4. Click OK.

Importing properties in DCFM or FM format

You can use this procedure to import properties in Data Center Fabric Manager (DCFM) or Fabric Manager (FM) format.

1. In the Configure Names dialog box, select DCFM/FM Format and then select Import.

2. Click OK.


The format appears as follows:

# Names Export File V 1.0 : DO NOT DELETE / MOVE / MODIFY THIS LINE # For each row in the file the name should be followed by an ','# Column Format: WWN,Name,Type ,Description# FM Names file Format [ Delimiter ',' ]####################################################################200000051e536b20,s,Node,200000051e536b43,bfa0,Node,100000051e536b20,a,Port,100000051e536b44,bfa0_port1,Port,100000051e536b43,bfa0_port0,Port,Adding a name and a WWN

4. Click OK.

Importing duplicated namesThe Duplicated Names dialog box, shown in Figure 17, displays when you import a file with a duplicate name.


OR



2. Import a file with duplicate names in the Configure Names dialog box.

The Duplicated Names dialog box displays.


NPIV 3

FIGURE 17 Duplicated Names dialog box

3. Determine which method you will use to fix the name policy violation, and click the appropriate button.

• Append unique suffix for all repetitive names - Click to instruct the software to add incremental numbers to fix the duplicated names.

• User/Administrator will manually fix - Change duplicate names using the procedure in “Editing the name fields” on page 50.

4. Click OK.

NPIVN-Port ID Virtualization (NPIV) enables a single Fibre Channel protocol port to appear as multiple, distinct ports. NPIV provides separate port identification within the fabric for each operating system image (partition) behind the port, as if each operating system image had its own unique physical port.

Each NPIV device has a unique virtual port ID (PID), port WWN, and node WWN. The virtual port has the same properties as an N_Port and is therefore capable of registering with all services of the fabric. In other words, multiple virtual devices emulated by NPIV appear no different than regular devices connected to a non-NPIV port. The maximum number of virtual PIDs for an N_Port on a FC switch is 255. For a CEE switch, the maximum number of V_Ports is 64.

NPIV is available at the physical port level or at the virtual fabric level. If virtual fabric ports are detected, then you cannot configure NPIV parameters at the physical port level. If virtual fabric ports are deleted on the switch port side, the NPIV parameters can then be configured at the physical port level. No settings are available for V_Ports from basic port configuration. for a description of teaming statistics fields.

NOTENPIV is not supported on Solaris platforms.


Teaming configuration3

Teaming configurationA network interface team is a collection of physical network (Ethernet) interfaces acting as a single interface. The primary requirement for teaming is to provide larger throughput in addition to load balancing and fault tolerance.

The following parameters must match for all ports when a team is created or when a port is being added to the team:

• Header Data Split (HDS)

• Receive Side Scaling (RSS)

• Offload parameters

• Port VLAN ID

• MTU size

• Link speed

To change these parameters, you use the Advanced Properties tab in the Windows Device Manager for the appropriate port instance on each adapter where you want to change parameters. For more information about changing parameters, refer to the Brocade Adapters Installation and Reference Manual (“Network Driver Parameters” section).

NOTEWindows 2008 x86, x64, and R2 supports VLANs, Teaming, and VLANs on Teams.Windows 2003 x86 and x64 supports VLANs and Teaming.

VLANs and Teaming are supported on Linux, Solaris, and VMware, but are implemented by the OS vendors.

As you configure teams, note the following points:

• There are a maximum of 16 adapters for a server, so the maximum number of teams on a server is eight.

• A team can have up to eight physical ports and a minimum of one port.

• A port can participate on only one team.

• Only one port can be primary, and all ports other than the primary port are secondary.

• You can view team members in the Teaming Configuration dialog box at the host level only.

Teaming modesCNA ports can be teamed in one of three modes:

• Failover

• Failback

• 802.3ad (dynamic)

The Failover mode provides fault tolerance. Only one port in a team is active at a time, and the others are in standby mode. This active port is called the primary port. If the primary port goes down, a secondary port is chosen (using a round-robin algorithm) to be the next primary.

The Failback mode is an extension of the Failover mode. In addition to the events that occur during a normal failover, if the original primary link (the port originally chosen to be the primary) comes back up, that port again becomes the primary port.


Teaming configuration 3

The Link Aggregation Control Protocol (LACP) is included in the IEEE 802.3ad specification as a method to control the bundling of several physical ports together to form a single logical channel. LACP allows a network device to negotiate an automatic bundling of links by sending LACP packets to the peer (directly connected to a device that also implements LACP). Switch-side configuration is also required for link aggregation to work.

NOTELink aggregation groups (LAGs) can result in redistribution of FCoE traffic across the adapter ports, which is unacceptable. Due to this challenge with IEEE 802.3ad protocol, be aware when you configure ports for teaming that converged traffic is not supported on ports that are participating in an IEEE 802.3ad-based team.

Configuring a team from the host level You can view team members in the Teaming Configuration dialog box at the host level.

1. Select the host from the device tree.

2. Select Configure > Teaming from the main menu.

OR

Right-click the host and select Teaming from the list.

The Teaming Configuration dialog box, shown in Figure 18, displays.

NOTETeaming is available on Windows platforms only.

FIGURE 18 Teaming Configuration dialog box (with VLAN support)


Teaming configuration3

Adding and editing a teamIf a VLAN exists on the the port of the adapter, you must first delete the VLAN before you create a team. To change the primary port in a team, refer to “Changing the primary port in a team.”

1. Click the Add button beneath the Team Name field.

2. Type a team name in the Team Name field.

The name can include up to 31 characters, must begin with a letter, can consist of letters, digits, hyphens, and underscore characters, but must not contain spaces.

3. Assign one or more ports from the Available Ports list, and click the right arrow button to move them to the Selected Ports list.

The system automatically assigns the MAC address.

4. Click OK.

The team now exists. You can edit the team by highlighting the team name on the Teaming Configuration dialog box.

Changing the primary port in a teamThe Set Primary feature is disabled if the team mode is set to 802.3ad, which enables link aggregation. Link aggregation only works if all the ports are part of the same switch. Failover and Failback, however, can work on multiple switches. You cannot run converged traffic (FCoE) if 802.3ad (link aggregation) is enabled.

To set or change the primary port in a team, complete the following steps:

1. Select an adapter from the Selected Ports list on the Teaming dialog box.

2. Click the Set Primary button.

The selected adapter will serve as the primary adapter (the master) and the other as the secondary adapter (the slave). The slave takes over if the master fails. If you are using more than two adapters, and you want a specific adapter to take over if the primary fails, you must specify a secondary adapter.

Failback is the process of restoring a device in a state of failover back to its original state, before the failure.

Removing a team1. Select a team from the Teams field.

2. Click the Delete button beneath the Team Name field.

The selected team is deleted from the Team Name field.


VLAN configuration 3

Displaying teaming statistics1. Select a team from the Teams field.

2. Click the Statistics button beneath the Team Name field.

The Teaming Statistics dialog box displays. See“Teaming Statistics dialog box (CNA only)” on page 169 for a description of teaming statistics fields.

VLAN configurationA Virtual LAN (VLAN) is a collection of network nodes that share the same broadcast domain regardless of their physical location or connection point to the network. A VLAN serves as a logical workgroup with no other physical barriers and allows users to share information and resources as though located on the same LAN.

NOTEVLAN configuration is a Windows-only feature.

There are three types of VLANS:

• Regular VLAN—A regular VLAN is identified using a VLAN ID (with a range of 1-4094, where 0 is used for an untagged VLAN) and a VLAN name.

• Passthru VLAN—A Passthru VLAN has VLAN ID 0 and PASSTHRU as its VLAN Name. It can be created or deleted at any time and is treated as a regular VLAN; however, a Passthru VLAN is not editable.

• Port VLAN (PVID)—You create a Port VLAN using Windows Device Manager. The VLAN ID is assigned when it is created and the VLAN name is PORT VLAN. You cannot create, edit, or delete a Port VLAN using the Host Connectivity Manager (HCM).

NOTEIf a PORT VLAN exists in the VLAN configuration, you cannot perform any add, delete, or edit operations on any VLAN. In addition, you cannot view statistical information on any VLAN.

Adding a VLANYou can access the VLAN Configuration dialog box by selecting an Ethernet port from the device tree. This procedure provides instructions about how to add a VLAN to an Ethernet port.

You can create a regular VLAN or a passthru VLAN only if a Port VLAN ID (PVID) does not exist. You cannot name a regular VLAN “PORT LAN” or “Passthru.”

NOTEAfter a VLAN or a Passthru VLAN has been created and assigned a non-zero PVID value using HCM or the BCU command, if you modify the the port VLAN using Device Manager on the port with VLANs, there is a possibility of inconsistency in data traffic on the Passthru VLAN. You will receive an illegal configuration warning, prompting you to remove the port VLAN. To avoid this inconsistency, using Device Manager, set the Port VLAN (PVID) to 0 on the port that has VLANs with a non-zero PVID value.

1. From the Ethernet port level, select an Ethernet port from the device tree.

2. Add a VLAN using one of the following methods:


VLAN configuration3

• Select Configure > VLAN Configuration from the main menu.

• Right-click an Ethernet port and select VLAN Configuration from the list.

• Click Add on the Teaming Configuration dialog box, shown in Figure 18.

The VLAN Configuration dialog box displays.

FIGURE 19 VLAN Configuration dialog box

3. Click the Add button that corresponds to the VLANs table.

4. Click Add on the VLAN Configuration dialog box (Figure 19).

The Add VLAN dialog box displays. Figure 20 shows a VLAN configuration before a passthru VLAN is configured.

FIGURE 20 Add VLAN dialog box

5. Enter a VLAN identifier in the VLAN ID field. The range is from 1 through 4094.

6. Enter a VLAN name in the VLAN Name field. The VLAN name must not exceed 31 characters.

7. (Optional) Click the Create Passthru check box to designate the VLAN as a Passthru VLAN.

8. Click OK.


VLAN configuration 3

VLAN configuration conflictsFigure 21 shows the VLAN Configuration dialog box if a Port VLAN exists in the configuration. When a Port VLAN exists, the VLAN Add, Edit, and Remove buttons are disabled.

FIGURE 21 VLAN Configuration dialog box with PORT VLAN

A Port VLAN cannot co-exist with a regular or Passthru VLAN. If the configuration includes a regular VLAN or a Passthru VLAN and a Port VLAN, an error message displays, as shown in Figure 22.

FIGURE 22 VLAN Configuration conflicts

You can remove a regular VLAN or Passthru VLAN from an invalid configuration using the instructions in “Removing a VLAN” on page 62. A regular VLAN or Passthru VLAN can be removed at any time. A Port VLAN, however, is not editable.

Editing a VLANYou can access the VLAN Configuration dialog box by selecting an Ethernet port from the device tree. This procedure provides instructions about how to edit an existing VLAN.

You cannot edit a Port VLAN or a Passthru VLAN.


2. Add a VLAN using one of the following methods:

• Select Configure > VLAN Configuration from the main menu.

• Right-click an Ethernet port and select VLAN Configuration from the list.

• Click Edit on the Teaming Configuration dialog box, shown in Figure 18.


VLAN configuration3

3. Click Edit on the VLAN Configuration dialog box

OR

Click Edit on the Teaming Configuration dialog box, shown in Figure 18.

The Edit VLAN dialog box, as shown in Figure 23, displays.

FIGURE 23 Edit VLAN dialog box

4. Type a new name in the VLAN Name field.

5. Click OK.

Removing a VLANYou can access the VLAN Configuration dialog box by selecting an Ethernet port from the device tree. This procedure provides instructions about how to remove an existing VLAN.


2. Select Configure > VLAN Configuration from the main menu.

OR

Right-click an Ethernet port and select VLAN Configuration from the list.

The VLAN Configuration dialog box displays.

3. Click Remove on the VLAN Configuration dialog box

OR

Click Remove on the Teaming Configuration dialog box, shown in Figure 18.

A warning dialog box, as shown in Figure 24, displays.

FIGURE 24 Remove VLAN dialog box

4. Click OK to remove the VLAN from the configuration.


Management application support for FCoE 3

Displaying VLAN statisticsVLAN Statistics for a team can only be opened if the VLANs are added to a team from the Teaming Configuration dialog box, shown in Figure 18.


2. Click Statistics on the Teaming Configuration dialog box.

The VLAN Statistics dialog box displays. See“VLAN Statistics dialog box (CNA only)” on page 180 for a description of VLAN statistics fields.

Management application support for FCoEThe converged network adapter (CNA) is supported in the Management application, version 10.3. The Management application v10.3 supports the following FCoE features:

• Virtual LANs (VLANs)

• Converged Enhanced Ethernet (CEE) switches and ports

• CEE maps

• Link Layer Discovery Protocol - Data Center Bridging Exchange (LLDP-DCBX) profiles

• Access control lists

• Spanning Tree Protocol (STP)

• 802.1x authentication

• FCoE login groups

• Virtual ports and trunks

For complete information about how these features are managed in the Management application, refer to the DCFM Enterprise User Manual, supporting DCFM 10.3.x or higher.


Management application support for FCoE3



Chapter

4
Monitoring
In this chapter•Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

•Real-time performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

•Historical performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

•Master log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

•Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

•Syslog support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Performance monitoringThe Host Connectivity Manager (HCM) Port Statistics window enables you to monitor the performance of the adapter and the traffic between the adapter and the LUNs. You can use the information to isolate and troubleshoot areas that impact application performance.

The components listed in Table 9 display statistics when the FCoE port node is selected. Refer to Appendix A, “HCM Dialog Boxes” for a description of each statistics field.

TABLE 9 Statistics monitored by component

Component Statistics monitored

Local host • Teaming

HBA • Port

HBA port • Port• FCP IM Module• Fabric• IOC• QoS• Realtime• Historical

CNA • Port

CEE port • Port• CEE• FCP IM Module• Firmware• Realtime • Historical

65

Performance monitoring4

Controlling the polling frequency rateThe faster the polling rate, the more quickly the HCM GUI receives indications from the host. However, faster polling rates consume more of your system’s CPU and network resources and can therefore slow the system.

To control port statistics polling, do one of the following from any of the Statistics dialog boxes.

1. Click the Start Polling check box to manually poll the port statistics.

2. Type the polling rate in the Polling Frequency in Seconds field. The range is between 5 and 3600 seconds. The default is 5 seconds.

3. Click the Stop Polling check box to stop port statistics polling.

4. Check the Keep Running Data check box to see the trend.

Ethernet port • Eth • Eth IOC• VLAN• Realtime• Historical

FCoE port • Fabric• IOC• FCoE

Logical port and remote port

• Logical port• Realtime• Historical

Virtual port • Logical port• Virtual port• Realtime• Historical

Device*

*No statistics are available for LUNs

• Remote port > Target statistics, FCP IM statistics

TABLE 9 Statistics monitored by component (Continued)


Real-time performance data 4

Resetting statistics1. Click the Reset button on any of the Statistics dialog boxes.

A warning dialog box, shown in Figure 25, displays.

FIGURE 25 Reset statistics warning

2. Click Yes.

All of the statistics are reset to 0.

Real-time performance dataReal-time performance enables you to collect data, displayed in utilization (Mbps) and errors per second from the following managed devices:

• Port statistics on both the HBA and the CNA

• Virtual Port statistics on the virtual port

• Ethernet Port statistics on the Ethernet node

• FCP IM statistics on the remote port

To generate a real-time performance graph for a device, complete the following steps.

1. Select the device for which you want to generate a real-time performance graph.

2. Select Configure > Performance > Realtime Statistics.


Real-time performance data4

The Realtime Performance dialog box, shown in Figure 26, displays.

FIGURE 26 Realtime Performance dialog box

3. Select the type of statistics you want to run from the Statistics Name list. You can display and filter real-time statistics on the port, virtual port, Ethernet port, or remote port.

4. Select the polling interval. Options include 10 seconds, 20 seconds, or 30 seconds.

5. Filter the real-time performance statistics by selecting or clearing the statistics counters check boxes. By default, all of the statistics counters are enabled.

6. Click Apply to save your changes.


Historical performance data 4

Historical performance dataTo generate a historical performance graph for a device, complete the following steps.

1. Select the device for which you want to generate a historical performance graph.

2. Select Monitor > Performance.

3. Select the Enable Historical Data Collection check box.

The Historical Performance dialog box, shown in Figure 27, displays.

FIGURE 27 Historical Performance dialog box

4. Select the type of statistics you want to run from the Statistics Name list. You can display and filter historical statistics on the port, virtual port, Ethernet port, or remote port.

5. Select one of the following frequencies from the Data for list:

• Last 1 Day—One sample of historical data is collected for 30 minutes’ duration.

• Last 1 Week—Two samples of historical data is collected for one hour’s duration.

• Last 1 Month—Four samples of historical data is collected for two hours’ duration.

6. Filter the historical performance statistics by selecting or clearing the statistics counters check boxes. By default, all of the statistics counters are enabled.

7. Click Apply to save your changes.


Master log4

Master logEvent monitoring enables early fault detection and isolation on a selected adapter. When applicable events occur during adapter operation, the adapter driver generates event messages. These messages are captured in your host system logs. These messages are also captured in an agtEvent.log file by the HCM agent and displayed in the HCM master log. Note that message display may differ in your host system log and the HCM master log; however, messages will most likely contain the following information:

• Message ID

• Description

• Severity level

• Event category

• Cause of event

• Recommended action

• Date and time event occured

Message details are also contained in HTML files, which load into your system when you install the adapter driver. You can view these HTML files using any internet browser application. Refer to the Brocade Adapters Troubleshooting Guide for details of all driver event messages.

NOTETo avoid processing of older events in first-time event discovery, an event will be considered for processing if it has occurred within the last 20 seconds, or not greater than the discovery interval. The agent and the HCM GUI application must be running in the same time zone and at the right time.

The Master Log Properties dialog box, described in Table 10, displays a list of all events that have occurred. You can filter the events based on the user-defined criteria shown in Figure 28.

TABLE 10 Master Log fields

Field Description

Filter button Click to launch the Master Log Filter dialog box.

Clear Filter button Click to clear the master log filter option set.

Sr No column Displays a numbering sequence in ascending order.

Severity column Displays the event severity (informational, minor, major, or critical).

WWN/MAC column Displays the world wide name (WWN) or the media access control (MAC) address of the device on which the event occurred.

Category column Displays the category of event, based on one of the following categories:• Adapter• Port• LPort• RPort• ITNIM• Audit• IOC• Eth Port

Subcategory column Displays the subcategory of the main category.


Master log 4

Filtering event log entriesEvent filtering enables you to block events based on user-defined criteria (severity or type of log). Events that have been filtered out do not appear in the Master Log.

1. Click the Filter button in the Master Log section of the bottom pane.

The Master Log Filter dialog box displays.

2. Filter the events using one or a combination of the criteria shown in Figure 28.

NOTEThe Category is the type of event. The categories are listed in Table 10.

FIGURE 28 Master Log Filter dialog box

3. Click Apply to save your changes, or click Cancel to exit the window.

OR

Click OK to save the changes and exit the window.

Description column Displays a brief description of the event.

Date/Time column Displays the date and time when the event occurred.

TABLE 10 Master Log fields (Continued)

Field Description


Application log4

Application logThe HCM Application Log, shown in Figure 29, displays all application-related informational and error messages, as well as the following attributes:

• Date and time the message occurred

• Severity of the message

• Description of the message

• The agent IP address

NOTERun-time memory information is logged in the application log whenever a supportSave is triggered from HCM or when the About dialog box is launched in HCM.

FIGURE 29 HCM Application Log

Syslog supportSyslog forwarding is the process by which you can configure the Host Connectivity Manager (HCM) agent to send Syslog messages to other computers through port 514. You can configure the HCM agent to forward events to a maximum of three Syslog destinations. These events will display in the operating system logs.

The HCM stores all the received events from the driver in the agtEvent.log file. By default, the location is /opt/hcmagent/log/hbaEvents.log in Linux and Solaris systems.

NOTEVMware ESX 3.5 and 4.0 blocks the Syslog outgoing port 514 by default. Therefore, you must configure the firewall if you use VMware ESX 3.5 or 4.0 and plan to use Syslog Host Configuration feature in DCFM or if you access HCM through DCFM. See “Syslog host configuration using VMware” on page 74 for more information.


Syslog support 4

Opening the Syslog Server Configuration dialog box 1. Select the host, an adapter, or a port from the device tree.

2. Select Configure > Syslog from the main menu.

The Syslog Server Configuration dialog box, shown in Figure 30, displays.

FIGURE 30 Syslog Server Configuration dialog box

Registering a host serverYou can register up to three Syslog destinations on managed Fabric OS devices.


The Syslog Server Configuration dialog box displays.

2. Enter the host name or IP address of the destination device into the Host Name/IP Address field.

3. Click Add to register the host as a Syslog destination.

4. Click OK to close the dialog box.

Removing a host server1. Select Configure > Syslog from the main menu.

The Syslog Server Configuration dialog box displays.

2. Enter the host name of the destination device into the Hostname field.

3. Enter the IP address of the destination device into the IP Address field.

4. Click Remove to remove the host as a Syslog destination.



Syslog support4

Syslog host configuration using VMwareVMware ESX 3.5 and 4.0 blocks the Syslog outbound port 514 by default. Therefore you must configure the firewall to allow outgoing port 514 for Syslog if you plan to use the Syslog host configuration feature in DCFM or if you access HCM through DCFM.

Use the following procedure if the outgoing UDP port 514 is blocked by the VMware ESX firewall.

1. Restart the HCM Agent if the firewall settings on port 514 change in VMware.

2. Use the following command to open port 514:

esxcfg-firewall -o 514,udp,out,syslog

3. Use the following command to block outgoing traffic through port 514:

esxcfg-firewall -c 514,udp,out,syslog



Chapter

5
Diagnostics
In this chapter•Fibre Channel diagnostics using HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

•Fibre Channel diagnostics using the BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

•Ethernet diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

•Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

•SFP management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

•Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

•supportSave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Fibre Channel diagnostics using HCMThe purpose of diagnostic commands is to evaluate the integrity of the system hardware. Be sure to disable the port(s) before running any type of port diagnostics. In addition, it is advisable that you do not perform other operations on the adapter while running HCM or BCU diagnostics.

NOTEWhen you invoke a test on an adapter, you can run diagnostics for one or both ports within the selected adapter.

75

Fibre Channel diagnostics using HCM5

Running a hardware-level test using HCM1. Select an adapter or an adapter port from the device tree. Hardware-level tests are not

supported on FCoE or Ethernet ports.

2. Select Configure > Diagnostics from the main menu.

OR

Right-click the component and select Diagnostics from the list

The Diagnostics dialog box, shown in Figure 31, displays.

FIGURE 31 Hardware-level diagnostic tests dialog box

3. Click the check box that corresponds to the port test you are running.

4. Specify the parameters based on parameter information found in Table 11.

NOTEClick the Stop on Error check box if you want the test to stop running if an error occurs.

5. Click Start to run the test.


Fibre Channel diagnostics using HCM 5

Running a Fibre Channel protocol-level test using HCMThere are three protocol-level tests:

• Echo test, which sends an FC Echo ELS to a remote port.

• FC ping test, which requests the management server to test the connectivity with a given remote port (without zoning restrictions). Not supported in Solaris operating systems.

• FC traceroute test, which requests to enumerate the route between two given end points. Not supported in Solaris operating systems.

To run one of the protocol-level tests, use the following procedure.

1. Select an adapter or port from the device tree.


OR

Right-click the component and select Diagnostics from the list.

The Diagnostics dialog box, shown in Figure 32, is displayed.

3. Click the FC Protocol Tests tab.

TABLE 11 Hardware-level test parameters

Hardware-level test Parameter Test Options

Memory test

NOTE: During the test, IOC is disabled.

None You can enable or disable this test. Regardless of test cycle set value, the Memory Test will run only once.

PCI loopback test Frame Count Integer from 0 - 4,294,967,295. The default value is 8192.

Data Pattern Default value is A5A5A5A5.

Test Cycle The number of times the test runs. The default value is 10.

Port loopback test

NOTE: For an External Loopback test, you must plug in the loopback connector.

For a Brocade 804 mezzanine card, a pass-through module is required for an External Loopback test.

Subtest ID • Internal• External• Serdes

Link Speed 2, 4, and 8 Gbps

Frame Count Integer from 0 - 4,294,967,295. The default value is 8192.


Data Pattern (hexadecimal) Default value is A5A5A5A5.

Queue test

Sends a health check message from host to firmware through message queues memory mapped over the PCI.

You can enable or disable this test.

Queue number from 0-3. Because the GUI only allows you to enable or disable the queue test (and not specify an integer), all the queues are tested.


Fibre Channel diagnostics using HCM5

FIGURE 32 Protocol-level diagnostic tests dialog box

4. Click the check box that corresponds to the protocol test you are running.

5. Select a port, target, and logical port from the lists, and click Add to add it to the test table.

6. Define how many times the test runs by specifying the test cycle number. The default test cycle number is 1.

7. Click Start to run the test.


Fibre Channel diagnostics using the BCU 5

Displaying test log details1. Select Configure > Diagnostics from the Host Connectivity Manager.

2. Run any diagnostic test.

3. Select and double-click a row of the test results in the bottom pane.

The Test Log Details dialog box, shown in Figure 33, displays.

FIGURE 33 Test Log Details for Echo Test dialog box

Fibre Channel diagnostics using the BCUDiagnostic commands evaluate the integrity of the system hardware. Be sure to disable the port before running any type of port diagnostics. In addition, it is advisable that you do not perform other operations on the adapter while running HCM or BCU diagnostics.

diag commandsThe diag commands shown in Table 12 monitor hardware components and can be performed while the system is running (they are non-disruptive). Refer to “diag” on page 205 for details.

NOTEThe sfpshow and beacon commands are not applicable for the Brocade 1007 CNA expansion card. or the Brocade 1741M mezzanine card.


Ethernet diagnostics5

fcdiag commandsFibre Channel diagnostics include the tests shown in Table 13. Refer to “diag” on page 205 for details about this command.

Ethernet diagnosticsThe Ethernet loopback test generates and sends out the desired number of packets and expects to receive the same number of packets through the loopback interface (Serdes or external). Each time a packet is sent it is selected from a different starting point of the data buffer so that any two consecutively transmitted packets will not be the same.

You must have the Ethernet card and the device driver installed and a loopback connector in place. The loopback connector is a standard RJ-45 connector.

TABLE 12 Fibre Channel diag commands

Command Description

beacon Blinks the appropriate port LED for physical identification. Beaconing can occur at the port or the link level.End-to-end (E2E) beaconing is a software feature that can be enabled on Brocade 8 Gbps HBAs to allow the local HBA to flash (beacon) and also cause the connected Fibre Channel switch port to uniquely beacon. Refer to the Brocade Adapters Installation and Reference Guide for details on E2E beaconing patterns.

loopback Tests the data path from the IOC to the desired network loopback point (internal, serdes, external) and back.

memtest Tests the adapter’s memory blocks.

pciloopback Checks the communication path between the host and the I/O Controller (IOC).

queuetest Sends a health check message from the host to firmware through mes-sage queues that are memory-mapped over the PCI.

sfpshow Displays small form factor pluggable (SFP) information.

tempshow Displays the temperature of the adapter.

TABLE 13 Fibre Channel diagnostic tests

Command Description

fcping Determines the basic connectivity between the Fibre Channel network points and monitors and measures network latency.

fctraceroute Reports on a SAN path, including node hops and latency data.

fcecho Sends an FC Echo Extended Link Services (ELS) request to a remote port.

linkbeacon Blinks the LED light of the remote port of the link.

scsitest Tests the SCSI components.


Ethernet diagnostics 5

NOTEWindows 64-bit platforms only: You must first create a VLAN on the port before you perform an Ethernet loopback test. If the port does not have a VLAN, an error message displays.

Running an Ethernet test using HCMThe following procedure explains how to run an Ethernet test.

1. Select an Ethernet port from the device tree.


OR

Right-click the component and select Diagnostics from the list.

The Diagnostics dialog box is displayed.

3. Click the Ethernet Tests tab.

The Ethernet Tests dialog box, shown in Figure 34, displays.

FIGURE 34 Ethernet Tests dialog box

The Ethernet Test options are described in Table 14.


Beaconing5

Running an Ethernet test using the BCUEnter the following command to test the Ethernet data path from the host to Serdes or external loopback based on your selection.

NOTEBefore you run the ethdiag test, disable the physical port using the bcu port --disable <port_id> command.

bcu ethdiag --loopback <port_id> [-t <loopback_type] [-c <count>] [-p pattern]

Refer to “ethdiag” on page 210 for details about this command.

BeaconingBeaconing is a continuous signaling of error conditions on a LAN. Beaconing can occur either on the port or on one or both sides of the link (known as end-to-end beaconing). Link end-to-end beaconing provides a mechanism to start beaconing on both the adapter side and the switch side.

NOTEPort beaconing is not supported on the Brocade 804 mezzanine card or the Brocade 1007 CNA expansion card. or the Brocade 1741M mezzanine card.

Configuring beaconing using HCMYou can configure beaconing from an HBA port or CNA port.

1. Select an HBA port, an FCoE port, or an Ethernet port from the device tree.

2. Select Configure > Beacon from the Host Connectivity Manager.

3. Click either the Port check box or the Link check box to enable the feature.

TABLE 14 Ethernet Test parameters

Ethernet loopback test

NOTE: For an External Loopback test, you must plug in the loopback connector.

Subtest ID • External• Serdes

Link Speed 10 Gbps

Frame Count Integer from 1-131072 (128K). The default value is 65536 (64K).


Data Pattern (hexadecimal) Default value is A5A5A5A5.


SFP management 5

Configuring beaconing using the BCUEnter the following command to blink the appropriate port LED for physical identification.

bcu diag --beacon <port_id> {on | off} [-t <secs>]

where:

duration Blinks the local port for the specified number of seconds. The default is 0, which means infinite blinking.

Refer to “diag” on page 205 for details about this command.

Enter the following command to blink the appropriate link for physical identification.

bcu fcdiag --linkbeacon <port_id> {on|off}

Refer to “fcdiag” on page 217 for details about this command.

SFP managementThe Port SFP dialog box enables you to display the properties that are associated with a selected small form-factor pluggable (SFP) transceiver.

Displaying SFP information using the BCUEnter the following command to view the SFP information. If the firmware detects a non-Brocade SFP, the port is disabled.

bcu diag --sfpshow <port_id>

Refer to “diag” on page 205 for details about this command.

Displaying SFP information using HCM

NOTEThe Brocade 804 mezzanine card and Brocade 1007 CNA expansion card connects to the embedded switch modules or embedded interconnect modules on the Blade System chassis by way of an internal backplane and, therefore, the SFP properties do not apply to the Brocade 804 or the Brocade 1007.

1. Select a port in the device tree.

2. Click the SFP tab in the right pane.

The SFP Properties panel, shown in Figure 35, displays.


Debugging5

FIGURE 35 SFP Properties panel

Details about the port technology and extended link are described in “SFP Properties panel” on page 160.

Debugging

The following debug commands capture all the support information needed to diagnose suspected system issues:

• portlog

Displays the log of FC frames and other main control messages that were sent out and received.

• portlogclear

Clears the port’s frame log.

• portlogctl

Enables or disables the portlog.

Refer to “debug” on page 203 for details about these commands.

supportSaveThe supportSave command collects debug information needed from the driver. You can collect supportSave information using the bfa_supportsave command or through the Data Center Fabric Manager (DCFM). HCM supportSave contains driver, agent, and HCM-related information.


supportSave 5

NOTEBefore collecting data using the supportSave feature, you may want to disable auto-recovery on the host system. This is because when adapters are reset after an auto-recovery from a failure, traces initiated before the failure can be lost or overwritten.

The captured debug information can be saved to the local filesystem and then sent to the supplier for further investigation. The information that is captured is detailed in Table 15.

The default location to where supportSave output is saved is under the IP address of the host from which it was collected, relative to the HCM installation directory, as follows:

USER HOME\HCM\data\10.32.116.1\supportsave

For example:

C:\Users\Administrator\HCM\data\10.32.116.1\supportsave

supportSave collection sourcesTable 16 lists the sources from which you can gather supportSave information.

NOTEMaster and Application logs are saved when supportSave is initiated through HCM, but not through the BCU.

TABLE 15 supportSave categories

supportSave level Captured information

System (or Host) Adapter model and serial numberAdapter firmware versionHost model and hardware revisionAll support informationAdapter configuration dataAll operating system and adapter information needed to diagnose field issuesInformation about all adapters in the systemFirmware and driver tracesSyslog message logsWindows System Event log.evt fileHCM GUI-related engineering logsEventsAdapter configuration dataEnvironment information

TABLE 16 supportSave collection sources

Source of supportSave information supportSave information collected

BFA based supportSave1 Collects driver-related logs, HCM agent information, and configuration files.

Internet browser Collects driver-related and HCM Agent logs and configuration files.

HCM Collects HCM application data, driver information, HCM Agent logs, and configuration files.


supportSave5

Automatic statistics collection

The port statistics log file is collected as part of the supportSave activity.

Port statistics collection occurs every eight hours and will be logged in to a rolling file under the /log/ directory. There are a maximum of five backup files and each file has a 100 KB size limit. A new backup file overwrites the oldest file.

Initiating supportSave using HCM

There are two ways to trigger a supportSave collection using the HCM GUI, explained in this section. You can also gather supportSave information for the adapter using the DCFM application. For information about supportSave using DCFM, refer to the Data Center Fabric Manager User Manual.

1. Select Tool > Support Save from the Host Connectivity Manager.

OR

Right-click a host from the device tree and select Support Save from the list.

NOTEIf the agent is up, it will use the advanced configuration. If there is no agent, it will use the basic configuration.

After the supportSave operation completes, the following message is displayed:

Support Save Completed and is located at

<HCM HOME Dir>/data/localhost/supportSave_Basic_<file_name>.zip


Initiating supportSave 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. For more information, refer to “Master log” on page 70 and “Application log” on page 72.

DCFM Collects only driver-related logs and configuration files.

1 Refer to “supportSave collection using a command prompt” on page 87 for more information.

TABLE 16 supportSave collection sources (Continued)

Source of supportSave information supportSave information collected


supportSave 5

supportSave collection using a command prompt

The bcu debug command does not support the bcu debug --supportsave command. The bfa_supportsave command, however, supports the following options:

• bfa_supportsave - To create and save the supportsave at /tmp.

• bfa_supportsave_dir - To create and save the supportsave under a directory name that you provide.

• bfa_supportsave <dir> <ss_file_name> - To create and save the supportsave under a directory and file name that you provide. If the directory already exists, it will be overwritten.

NOTEIf specifying a directory, make sure that the directory does not already exist to prevent overwriting the directory. Do not just specify a driver (such as C:) or C:\Program Files.

Messages display as the system gathers information. When complete, an output file and directory display. The directory name specifies the date when the file was saved.

Initiating supportSave using an Internet browser

You can use an Internet browser (Internet Explorer 6 or higher or Firefox 2.0 or higher) to collect and transfer supportSave information for the driver and the HCM agent.

Use a browser if you do not have root access, if you do not have access to file transfer methods such as FTP and SCP, or you do not have access to the Host Configuration Manager (HCM) or the Data Center Fabric Manager (DCFM).

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

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

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

2. Type the agent’s credentials using the factory default settings, admin and password.

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 supportSave file.

4. Rename the supportSaveController.do file as a zip file, using .zip as the extension. Use IZArc or winzip to unpack the file and analyze the contents.


supportSave5



Appendix

A
HCM Dialog Boxes
In this appendix•Authentication Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

•Backup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

•Base Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

•CEE properties panel (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

•CEE Statistics dialog box (CNA only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

•Change HCM Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

•Change HCM Agent Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

•CNA Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

•CNA Port panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

•CNA Port Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . 103

•Configure Names dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

•Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

•Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

•Eth IOC Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

•Ethernet Port Properties panel (CNA only). . . . . . . . . . . . . . . . . . . . . . . . . . 111

•Eth Port Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

•Event Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

•Fabric Statistics dialog box (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

•FCoE port properties panel (CNA only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

•FCoE Statistics dialog box (CNA only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

•FCP IM Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

•FCP IM Module Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

•Fibre Channel Security Protocol Configuration dialog box . . . . . . . . . . . . . 127

•Firmware Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

•Hardware Tests Diagnostics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

•HBA Properties panel (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

•IOC Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

•LLDP Properties panel (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

•Logical Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

•LPORT Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

•Master Log tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

•Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

89

In this appendixA

•Persistent Binding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

•Port POM Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

•Port Properties panel (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

•Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

•Protocol Tests dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

•QoS Statistics dialog box (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

•Real-time Performance Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . 157

•Remote Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

•Restore dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

•SFP Properties panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

•Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

•Target Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

•Teaming Configuration dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . 167

•Teaming Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

•Test Log Details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

•Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

•Virtual Port Deletion dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

•Virtual Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

•Virtual Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

•VLAN Configuration dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . 177

•VLAN configuration - Add VLAN dialog box (CNA only) . . . . . . . . . . . . . . . . 178

•VLAN configuration - Edit VLAN dialog box (CNA only) . . . . . . . . . . . . . . . . 179

•VLAN Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180


Authentication Statistics dialog box A

Authentication Statistics dialog box The Authentication Statistics dialog box enables you to display statistical information related to transmitted and received DH-CHAP attempts for a selected port.

Opening the dialog box1. Select an HBA port from the device tree.

2. Select Configure > FC_SP > Authentication Statistics from the Host Connectivity Manager.

Fields and components

Field Description

Date The date the statistics were run.

Failures The number of times security authentication failed.

Successes The number of times security authentication succeeded.

Tx Auth Rjts The number of rejected transmitted Fibre Channel authentication attempts.

Tx Auth Negs The number of transmitted Fibre Channel authentication negotiation attempts.

Tx Auth Dones The number of completed Fibre Channel authentication negotiation attempts.

Tx DHCHAP Replies The number of transmitted DH-CHAP replies.

Tx DHCHAP Challenges The number of transmitted DH-CHAP challenge attempts.

Tx DHCHAP Successes The number of times a transmitted Fibre Channel authentication attempt was successful.

Rx Auth Rjts The number of rejected received Fibre Channel authentication attempts.

Rx Auth Negs The number of received Fibre Channel authentication negotiation attempts.

Rx Auth Dones The number of completed received Fibre Channel authentication attempts.

Rx DHCHAP Challenges The number of received DH-CHAP challenge attempts.

Rx DHCHAP Replies The number of received DH-CHAP replies.

Rx DHCHAP Successes The number of times a received DH-CHAP challenge was successful.


Authentication Statistics dialog boxA

Using the dialog boxRefer to the following topics for specific procedures using this dialog box:

• “Configuring security authentication using HCM (Host and HBA)”

• “Port Statistics dialog box”

• “Controlling the polling frequency rate”

• “Resetting statistics”

• “Performance monitoring”


Backup dialog box A

Backup dialog box The Backup dialog box allows you to create a backup of data and configuration files.

Opening the dialog boxSelect any device from the device tree and select Tool > Backup Data from the Host Connectivity Manager.


Field Description

Output Directory text box Enter the location of the directory in which you want to back up the data and configuration files.

Browse button Click to browse to the location of the backup directory.

Start Backup button Click to instruct the system to back up the data and configuration files to the designated location.

Close button Click to close and exit the Backup dialog box.


Base Port Properties panelA

Base Port Properties panel The Base Port Properties panel enables you to display the properties that are associated with the base port.

Opening the panel1. From the device tree, select a base port.

2. In the right pane, click the Base Port Properties tab.


Field Description

Base Port Indicates whether the port is a base port (true or false).

Fabric Name The name of the Fabric associated with the base port.

FC Address The Fibre Channel address of the base port.

FPMA MAC Address The Fabric-Provided Ethernet MAC address created using the FC_ID assigned by the Fabric.

Node WWN The world wide name of the device.

Port WWN The world wide name of the base port.

Roles The role of the base port; for example, FCP Initiator.

State Indicates whether the base port is online or offline.

Switch IP Address The IP address of the switch.

Symbolic Name The symbolic name associated with the base port.


CEE properties panel (CNA only) A

CEE properties panel (CNA only)The CEE properties panel enables you to display the properties that are associated with a selected converged network adapter (CNA).

Operational CEE Configuration is displayed when the CEE Status is Active. The Remote CEE Configuration table is visible only when the CEE status is inactive and error reason is not one of the following.

• CEE_PHY_LINK_DOWN

• CEE_LLDP_SHUTDOWN_TLV_RCVD

• CEE_PROTOCOL_INIT

• CEE_LLDP_INFO_AGED_OUT

Opening the panel1. Select a CEE port in the device tree.

2. Click the CEE tab in the right pane.


Field Description

% Bandwidth The bandwidth percentage for a given priority group.

CEE Status The status of the CEE configuration; for example, Active.

DCBCXP version The DCBCXP version type; for example, CEE.

Ethernet Link Layer CoS Specifies a cost of service (CoS) priority value between 0 (signifying best effort) and 7 (signifying real-time data) to differentiate traffic.

FCoE CoS The Fibre Channel Class of Service that specifies a priority value.

FCoE Logical Link Status The operational status of the FCoE logical link; for example, Up or Down.

Network Priority The network priority for communication between nodes.

Priority Group ID The priority group ID. Values are 0-7 and 15 (strict priority). When coupled with bandwidth percentage and CoS, you can manage traffic by grouping like traffic together and giving each type a different priority level.

Priority Flow Control Indicates whether priority flow control is enabled or disabled.

iSCSI CoS Specifies an iSCSI cost of service (CoS) priority value between 0 (signifying best effort) and 7 (signifying real-time data) to differentiate traffic.


CEE Statistics dialog box (CNA only)A

CEE Statistics dialog box (CNA only)The CEE Statistics dialog box enables you to display the statistics that are associated with the link layer port.

Opening the dialog box1. From the device tree, select a physical port of a CNA.

2. Select Monitor > Statistics > CEE Statistics from the Host Connectivity Manager.


Field Description

Keep running data checkbox Click to continue running statistical data. This is useful if you want to see a trend.

Polling frequency in seconds text box Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds.

Start polling button Click to manually poll the CEE statistics.

Reset button Click to reset all of the statistics to 0.

LLDP Tx Frames Transmits the local network element (NE) data on a per-link basis to the remote NE at the other end of the link.

LLDP Rx Frames invalid The number of invalid received frames for LLDP.

LLDP Rx Frames new The number of new received frames for LLDP.

LLDP Rx Frames Collects the data received over the network link from the transmitting network element (NE), resulting in both the local NE and the remote NE having the port discovery data at each end of the network link.

LLDP Rx unrecognized TLVs The number of unrecognized type-length-value (TLV) elements for LLDP.

LLDP Rx shutdown TLVs The number of type-length-value (TLV) elements for LLDP that were shut down.

LLDP remote info aged The number of LLDP frames that timed out between the local and remote ends of the link.

DCBX phy link ups The number of Converged Enhanced Ethernet (CEE) links that are up.

DCBX phy link downs The number of Converged Enhanced Ethernet (CEE) links that are down.

DCBX Rx TLVs The number of type-length-value (TLV) elements received for DCBX.

DCBX Rx TLVs invalid The number of invalid type-length-value (TLV) elements received for DCBX.

DCBX control TLV errors The number of DCBX LLDP frames that were not transmitted because of errors.

DCBX feature TLV errors The number of type-length-value (TLV) errors received for DCBX features.


CEE Statistics dialog box (CNA only) A

DCBX new CEE cfg rcvd The number of new configurations events received on the physical port of the CNA.

CEE status down The number of status down events on the physical port of the CNA.

CEE status up The number of status up events on the physical port of the CNA.

CEE hw cfg changed The number of times the physical port of the CNA changed.

CEE invalid cfg The number of invalid configurations events received on the physical port of the CNA.

Field Description


Change HCM Password dialog boxA

Change HCM Password dialog box The Change HCM Password dialog box enables you to change an existing password for the application.

Opening the dialog boxSelect Configure > Change HCM Password from the Host Connectivity Manager.


Using the dialog boxRefer to the following topic for specific procedures using this dialog box:

• “Changing an HCM application password”

Field Description

User Name Type your user name.

Old password Type your existing password.

New password Type a new password.

Confirm New password Confirm your new password by retyping it.


Change HCM Agent Password dialog box A

Change HCM Agent Password dialog box The Change HCM Agent Password dialog box enables you to change an existing password for the host.

Opening the dialog boxSelect Configure > Change Password > Change Agent Password from the Host Connectivity Manager.



• “Changing an HCM application password”

Field Description

Host Name Displays the IP address of the host.

User Name Type your user name.

Old password Type your existing password.

New password Type a new password.

Confirm New password Confirm your new password by retyping it.


CNA Properties panelA

CNA Properties panel The CNA Properties panel enables you to display the properties that are associated with a selected Converged network adapter (CNA).

Opening the panel1. Select a CNA in the device tree.

2. Click the Properties tab in the right pane.


Field Description

CNA Parameters

MAC Address The adapter’s media access control address.

Name The name representing the adapter.

Operating Status Whether the CNA is enabled or disabled.

Manufacturer The company that manufactured the CNA.

Model Description The description of the CNA.

Max Speed Supported The maximum speed supported on the CNA, which is 10 Gbps.

# of Ports The number of ports associated with the CNA.

OEM Info Information about the original equipment manufacturer, if applicable.

Card Type The adapter card type; for example, CNA.

Hardware Path The hardware path of the CNA.

Serial # The serial number of the CNA.

Temperature The temperature of the CNA, both in Celsius and Fahrenheit.

Driver ParametersIt is possible to have multiple pairs of driver information, based on the number and types of drivers installed. The three driver possibilities include the CNA Network Driver, the FCoE Storage Driver, or a single, unified driver.

Driver Name The name of the host adapter driver.

Driver Version The version level of the host adapter driver.

Driver Name The name of the second driver, if applicable.

Driver Version The version level of the second driver, if applicable.

Firmware Parameters

Firmware Version The version level of the firmware.

BIOS Version The version level of the BIOS.

PCI Registers

Vendor ID The identifier of the PCI Register’s vendor.


CNA Properties panel A

Device ID The device ID of the PCI Register.

Subsystem Vendor ID The ID of the PCI subsystem vendor.

Current # of Lanes The number of PCI lanes, in Gbps, each way between the PCI slot and the adapter.

PCIe Generation The number of times the PCI Register is generated.

Initial Negotiated # of Lanes The set number of PCI lanes that were initially negotiated.

OEM VPD Information (HP only)

OEM The name of the OEM (HP)

Part # The part number of the adapter, preceded by HP. For example, HP:AXXXXA.

EDC The identifier for the EDC type adapter.

MDC The identifier for the MDC type adapter.

Misc Miscellaneous information pertaining to the HP adapter.

Serial # The serial number of the adapter, preceded by HP. For example, hp:aabbccddsss.

Product Description An HP-specific description of the adapter.

IBM Information

EC level The adapter’s EC level (IBM only).

FRU # The adapter’s FRU number (IBM only).

Field Description


CNA Port panelA

CNA Port panel The CNA port panel enables you to display the properties that are associated with a selected Converged network adapter (CNA) port.

Opening the panel1. Select a CNA port in the device tree.



Field Description

Port # The CNA expansion card port’s number (0 or 1).

Port WWN The CNA expansion card port’s world wide name.

Node WWN The CNA expansion card’s world wide name.

Physical Port Type The type of port; for example, CNA.

Name The CNA expansion card port’s name.

Local Port MAC The media access control number assigned locally.

Media The type of media; for example, mezzanine.

CEE State The state of the converged ethernet (whether it is online or offline).

CEE Error Reason The reason for the CEE error; for example, the physical link is down.


CNA Port Statistics dialog box (CNA only) A

CNA Port Statistics dialog box (CNA only)The CNA Port Statistics dialog box displays statistical information related to ports on a converged network adapter (CNA) port.

Opening the dialog box1. Select a CNA port from the device tree.

2. Select Monitor > Statistics > Port Statistics from the Host Connectivity Manager.


Field Description



Start polling button Click to manually poll the V_Port statistics.


Date The date and time of the most recent reset.

Port WWN The world wide name of the port about which statistics are displayed.

Seconds since stats is reset The number of seconds since the port statistics reset (the counter returns to 0).

Frames 64 bytes The number of 64-byte frames.

Frames 65-127 bytes The number of frames with 65-127 bytes.






Tx bytes The number of transmitted bytes.

Tx packets The number of transmitted packets.

Tx multicast packets The number of transmitted multicast packets.

Tx broadcast packets The number of transmitted broadcast packets.

Tx control frame The transmitted control frames.

Tx drops The number of transmitted frames dropped.

Tx jabber The number of transmitted jabbers (illegal packet length).

Tx FCS error The number of frame check sequence (FCS) errors transmitted, which indicate that frames of data are corrupted.

Tx fragments The number of transmitted frame packets that are fragmented.


CNA Port Statistics dialog box (CNA only)A

Rx bytes The number of received bytes.

Rx packets The number of received packets.

Rx multicast packets The number of received multicast packets.

Rx broadcast packets The number of received broadcast packets.

Rx control frames The number of received control frames, which assist in data frame delivery.

Rx unknown opcode The number of unknown opcode frames received.

Rx drops The number of received packet drops.

Rx jabber The number of received jabber frames (count of frames that exceed 1518 (non-VLAN) or 1522 (VLAN) bytes and contain an invalid FCS, including alignment errors).

Rx FCS errors The number of frames that have a integral of 64 to 1518 length and contain a frame check sequence (FCS) error.

Rx alignment errors The number of packets received with alignment errors.

Rx frame len errors The number of frames received in which the 802.3 length field did not match the number of data bytes actually received.

Rx code errors The number of frames received with at least one invalid data symbol.

Rx fragments The number of received frames that are less than 64 bytes in length and contain an invalid FCS (includes integral and non-integral lengths).

Rx pause The number of received pauses.

Rx zero pause The number of received zero pauses.

Tx pause The number of transmitted pauses.

Tx zero pause The number of transmitted zero pauses.

Rx FCoE pause The number of times a pause control frame was received by a congested FCoE port to wait a predetermined amount of time before retransmitting data.

Rx FCoE zero pause The number of times a zero pause control frame was received by a congested FCoE port.

Tx FCoE pause The number of times a pause control frame was transmitted to a congested FCoE port to wait a predetermined amount of time before retransmitting data.

Tx FCoE zero pause The number of times a zero pause control frame was transmitted to a congested FCoE port.

Rx iSCSI pause The number of received iSCSI pauses.

Rx iSCSI zero pause The number of received iSCSI zero pauses.

Tx iSCSI pause The number of transmitted iSCSI pauses.

Tx iSCSI zero pause The number of transmitted iSCSI zero pauses.

Field Description


CNA Port Statistics dialog box (CNA only) A







Configure Names dialog boxA

Configure Names dialog box The Configure Names dialog box enables you to add a world wide name and an associated name for an adapter, port, or storage device that is not yet discovered. You can also remove a device from the Name display list and import from or export properties to a file.

Opening the dialog box1. Select any device from the device tree.



Field Description

Display list Select a discovered host from the list. Current Host is the default.

Name The name for all configured devices.NOTE: You can also search for a name by typing the name into the text box and clicking OK.

Scope list The type of name; options include the Name itself or the WWN. After you have selected the type of name from the Scope list, type the name or WWN into the corresponding text box.

WWN/MAC The world wide name for all configured devices.NOTE: You can also search for a name by typing the world wide name into the text box and clicking OK.

Operational Status The operational status of the WWN/MAC (for example, Discovered).

Type The type of device; for example, Node or Port.

Description Displays a description of the device.

Remove button Select a device to highlight it, then click the Remove button to remove the discovered device from the list.

Import Click to import properties from a properties file for a selected device.

Export Click to save properties to a properties file for a selected device.

Add button For undiscovered devices, type in the name of the port’s name or the WWN and click the Add button to add it to the Display list.

DCFM/FM format list Select from the list to import properties in DCFM (Data Center Fabric Manager) / FM (Fabric Manager) or EFCM format.

Fix Duplicates button Click to fix any duplicate names.


Configure Names dialog box A


• “Name configuration”

• “Adding name entries”

• “Removing a name entry”

• “Exporting the properties for a WWN”

• “Importing the properties for a WWN”


Define Name dialog boxA

Define Name dialog box The Define Name dialog box enables you to assign a name to an existing world wide name.

Opening the dialog box1. Right-click on an HBA, a CNA or a port in the device tree.

NOTEYou can not define a name on an FCoE port or an Ethernet port.

2. Type a name that represents the adapter or port.

NOTEThe WWN and the Type are not editable.

3. Click OK to apply the change and close the window.

The new component is added to the Name list.








Field Description

WWN/MAC The world wide name for the device.

Name Enter a meaningful name for the device.


Description Enter a description of the device.


Duplicated Names dialog box A

Duplicated Names dialog box The Duplicated Names dialog box enables you to display configured names that are redundant.

Opening the dialog boxThe Duplicated Names dialog box displays when you import a file with a duplicate name.


OR



2. Import a file with duplicate names in the Configure Names dialog box.

The Duplicated Names dialog box displays.








Field Description

Append unique suffix for all repetitive names button

Click to automatically add an incremental number to a duplicate name.

User/Administrator will manually fix button

Click if you want to manually fix a duplicate name.

Name The port number with which the duplicated name is associated.

WWN/MAC The world wide name or media access control address with which the duplicated name is associated.

Operational Status The operational status of the duplicate WWN (for example, Discovered).


Description A description of the duplicate name.


Eth IOC Statistics dialog box (CNA only)A

Eth IOC Statistics dialog box (CNA only)The Eth IOC Statistics dialog box enables you to display statistical information related to the Ethernet IOC.

Opening the dialog box1. Select an Ethernet port from the device tree.

2. Select Monitor > Statistics > Eth IOC Statistics from the main menu.

OR

Right-click the Ethernet port and select Statistics > Eth IOC Statistics from the list.

The Eth IOC Statistics dialog at the host level displays.



• “Adding a VLAN”

• “Editing a VLAN”

• “Removing a VLAN”

Field Description



Start polling button Click to manually poll the Ethernet IOC statistics.


Date The date the Eth IOC statistics were run.

Mailbox Interrupts The number of mailbox interrupts that occurred on the Ethernet IOC.

Enable Events The number of Enable events on the Ethernet IOC.

Disable Events The number of Disable events on the Ethernet IOC.

Heartbeat Failures The number of heartbeat failures on the Ethernet IOC.

Firmware Boots The number of firmware boots on the Ethernet IOC.

Stats Timeouts The number of times the Eth IOC statistics timed out.


Ethernet Port Properties panel (CNA only) A

Ethernet Port Properties panel (CNA only)The Ethernet Port Properties panel enables you to display the properties that are associated with a selected Ethernet port.

Opening the panel1. Select an Ethernet port in the device tree.



Field Description

Eth Port Information

Eth Dev The name of the Ethernet device.

Port Type The port type; for example, Ethernet.

Current MAC address The current MAC address of the Ethernet port.

Factory MAC The factory-configured MAC address for the CNA.

IOC ID The IOC ID of the Ethernet port.

Hardware Path The hardware path of the Ethernet port.

State The status of the Ethernet port; for example, Linkup.

Eth Log Level The status of the Ethernet log; for example, Log Critical.

PXE Boot Information

PXE Boot Enabled Whether Preboot Execution Environment (PXE) is enabled.

VLAN ID The VLAN identifier


Eth Port Statistics dialog box (CNA only)A

Eth Port Statistics dialog box (CNA only)The Eth Statistics dialog box enables you to display statistical information related to the Ethernet port.


2. Select Monitor > Statistics > Eth Statistics from the main menu.

OR

Right-click the Ethernet port and select Statistics > Eth Statistics from the list.

The Eth Statistics dialog at the host level displays.


Field Description



Start polling button Click to manually poll the Ethernet IOC statistics.


Date The date the Eth statistics were run.

TxF0 ucast octets The number of transmitted unicast octets.

TxF0 ucast vlan The number of transmitted unicast VLANs.

TxF0 mcast octets The number of transmitted multicast octets.

TxF0 mcast packets The number of transmitted multicast frame packets.

TxF0 ucast packets The number of transmitted unicast frame packets.

TxF0 mcast vlan The number of transmitted multicast VLANs.

TxF0 bcast octets The number of transmitted broadcast octets.

TxF0 bcast packets The number of transmitted broadcast frame packets.

TxF0 bcast vlan The number of transmitted broadcast VLANs.

TxF0 errors The number of transmitted errors.

TxF0 vlan filtered frames The number of transmitted VLAN filters.

TxF0 SA check filtered frames The number of transmitted filter MAC source addresses.

RxF0 ucast octets The number of received unicast octets.

RxF0 ucast packets The number of received unicast frames.

RxF0 ucast vlan The number of received unicast VLANs.

RxF0 mcast octets The number of received multicast octets.

RxF0 mcast packets The number of received multicast frames.


Eth Port Statistics dialog box (CNA only) A

RxF0 mcast vlan The number of received multicast VLANs.

RxF0 bcast octets The number of received broadcast octets

RxF0 bcast packets The number of received broadcast frames.

RxF0 bcast vlan The number of received broadcast VLANs.

RxF0 frame drops The number of received frame drops.

Rx completed The number of received frames that completed.

Rx dropped The number of received frames that dropped.

Rx alloc failed The number of received allocation fails.

Rx checksum errors The number of received checksum errors.

Rx mac errors The number of received mac errors.

Rx small packets The number of small packets received by the port.

Rx large packets The number of large packets received by the port.

Rx lro The number of packets received on the IRO server.

Rx lro flush The number of packets flushed from the IRO server.

Rx low rxbuf count The number of received buffers.

Tx ls04 The number of transmitted IPv4 packets.

Tx ls06 The number of transmitted IPv6 packets.

Tx ls0 Errors The number of transmitted IPv6 packet errors.

Tx tcp cs0 The number of transmitted TCP packets with CS0 (the default priority class).

Tx ip4 cso The number of transmitted IP4 packets with CSO (the default priority class).

Tx udp cs0 The number of transmitted UDP packets with CS0 (the default priority class).

Tx checksum help Transmitted checksum help.

Tx checksum help errors The number of transmitted checksum help errors.

Tx map errors The number of transmitted map errors.

Tx res drops Transmitted packets that were dropped but are now resumed.

Tx small packets The number of small transmitted packets.

Tx large packets The number of large transmitted packets.

Tx out of wis count The total number of transmitted packets with an out of wis route status.

Tx wi waitq count The total number of transmitted packets with a waitq route status.

Tx ctxt waitq count The total number of transmitted packets with a waitq route status saved to a text file (.ctxt).

Tx max nbs per nbl The maximum number of transmitted packets on the NBS console server.

CEE toggle count The number of CEE toggles.

mbox intr disables The number of Mbox interrupts that are disabled.

Field Description


Eth Port Statistics dialog box (CNA only)A

Link toggle count The number of link toggles.

mbox intr enables The number of Mbox interrupts that are enabled.

Tx stops The number of stopped transmitted packets.

Tx wakeups The number of times stopped transmitted packets wake up.

Tx res stops The number of stopped receive packets that are resumed.

Tx hardware stop The number of stopped transmitted hardware packets.

Rx schedules The schedules for receive packets.

Rx hardware stops The number of stopped receive hardware packets.

Rx resumes The number of resumed receive packets.

Rx rss config count The number of receive packets with an RSS configuration.

Hardware stats updates The number of hardware statistics updates.

Field Description


Event Properties dialog box A

Event Properties dialog box The Event Properties dialog box displays the properties associated with a selected event from the Master Log.

Opening the dialog box1. Click the Master Log tab, located on the bottom pane of the Host Connectivity Manager.

A master summary of events on all discovered devices is displayed.

2. Double-click an event.



• “Master log”

• “Application log”

• “Filtering event log entries”

Field Description

Date/Time The date when the event occurred.

Time The time when the event occurred.

Severity The event severity (informational, minor, major, or critical).

WWN/MAC The world wide name (WWN) or media access control (MAC) of the device on which the event occurred.

Event ID An identifier that corresponds to the event.

Category The category of event; for example, Rport or ITNIM.

Description A brief description of the event.

Root Cause The root cause of the event.


Fabric Statistics dialog box (HBA only)A

Fabric Statistics dialog box (HBA only)The Fabric Statistics dialog box enables you to view statistics on a selected Fabric.

Opening the dialog box1. Select an HBA port from the device list.

2. Select Monitor > Statistics > Fabric Statistics from the Host Connectivity Manager.







Field Description

Keep running data check box Click to continue running statistical data. This is useful if you want to see a trend.




Num FLOGIs sent The number of Fabric logins sent.

FLOGI response errors The number of Fabric login response errors.

FLOGI accept errors The number of times Fabric login attempts are accepted.

FLOGI accepts received The number of times Fabric logins are received.

FLOGI rejects received The number of times Fabric login attempts are rejected.

Unknown responses for FLOGI The number of unknown Fabric login responses.

Allocation waits prior to sending FLOGI

The number of delayed Fabric login allocations.

FLOGIs received The number of times Fabric logins are received.

Incoming FLOGIs rejected The number of times Fabric logins are rejected.

Internal Fabric online notification sent to other modules

The number of internal notifications for Fabrics that are online that are sent to other modules.

Internal Fabric offline notification sent to other modules

The number of internal notifications for Fabrics that are offline that are sent to other modules.


FCoE port properties panel (CNA only) A

FCoE port properties panel (CNA only)The FCoE Port properties panel enables you to display the properties that are associated with a selected FCoE port.

Opening the panelSelect an FCoE port in the device tree and click the Properties tab in the right pane.


Field Description

FCoE Port information

State The state of the FCoE port (online or offline).

FCoE MAC The FCoE port’s media access control address.

Port WWN The FCoE port’s world wide name.

Node WWN The node’s world wide name.

Supported Classes The classes supported on the FCoE port; for example, Class2 and Class3.

Symbolic Name The nickname for the selected FCoE port.

IOC ID The IO Controller ID.

Hardware Path The hardware path of the FCoE port.

Port Log Indicates whether the port log is enabled or disabled.

FCoE information

Priorities Lists the available priorities.

PG ID The priority group ID. Values are 0-7 and 15 (strict priority).

Bandwidth The bandwidth percentage for a given priority group.

Fabric Parameters

Port Type The port type; for example, N_Port.

FC Address The FCoE port’s Fibre Channel address.

Local Port MAC The media access control address of the local port.

Configured Port State Indicates whether the FCoE port is enabled or disabled.

Operating Port State Indicates whether the port is online or offline.

Operating Speed The configured speed of the FCoE port.

Max Speed Supported The maximum speed that is supported on the FCoE port.

Frame Data Field Size The frame size, in bytes, of the FCoE port.

# of Lports The number of logical ports.

Operating ParametersNote: Beacon State and Link Beacon State are not supported on the Brocade 1007 CNA expansion card.

Beacon State Indicates whether beaconing is turned on.


FCoE port properties panel (CNA only)A

Using the panelRefer to the following topics for specific procedures using this dialog box:

• “Enabling and disabling rate limiting on the adapter side using HCM”

• “Enabling and disabling rate limiting on the adapter side using the BCU”

• “Configuring beaconing using HCM”

• “Configuring beaconing using the BCU”

Link Beacon State Indicates whether link beaconing is turned on.

Path Time Out The value between 1 and 60 that specifies the time-out session. 0 forces an immediate failover. The default time out value (TOV) is 30.

Logging Level The port logging level. Values include Log Critical, Log Error, Log Warning, and Log Info.

Persistent Binding Indicates whether persistent binding is turned on or off.

Target Rate Limit Indicates that target rate limiting is enabled or disabled.

Default Rate Limit The default rate limit, which is not applicable, because target rate limiting is not supported on the FCoE port.

FC-SP Parameters

Authentication Indicates whether FC-SP authentication is on or off.

Status The status of FC-SP authentication.

Algorithm The configured authentication algorithm.

Group The DH group, which is DH-null (group 0) which is the only option.

Error Status The health status of the Fibre Channel Security Protocol parameters.

Field Description


FCoE Statistics dialog box (CNA only) A

FCoE Statistics dialog box (CNA only)The FCoE Statistics dialog box enables you to display statistical information related to the Fibre Channel over Ethernet (FCoE) port.

Opening the dialog box1. Select an FCoE port from the device tree.

2. Select Monitor > Statistics > FCoE Statistics from the main menu.

OR

Right-click the FCoE port and select Statistics > FCoE Statistics from the list.

The FCoE Statistics dialog at the host level displays.


Field Description



Start polling button Click to manually poll the FCoE statistics.


Date The date the FCoE statistics were run.

Seconds since stats reset The number of seconds since the FCoE statistics were last reset.

CEE link up The number of Converged Enhanced Ethernet (CEE) links that are up.

CEE link down The number of CEE links that are down.

FIP link up The number of links with FCoE Initialization Protocol (FIP) that are up.

FIP link down The number of links with FCoE Initialization Protocol (FIP) that are down.

FIP failures The number of links with FCoE Initialization Protocol (FIP) requests that failed.

Invalid mac assignments The number of invalid media access control (MAC) assignments.

Vlan requests The number of virtual LAN (VLAN) requests.

Vlan notifications The number of VLAN notifications.

Vlan notification errors The number of virtual LAN (VLAN) notification errors.

Vlan request timeouts The number of times a virtual LAN (VLAN) request times out.

Vlan invalids The number of invalid virtual LAN requests.

Discovery requests The number of discovery requests.

Discovery responses The number of discovery responses.


FCoE Statistics dialog box (CNA only)A

Discovery error frames The number error frames during discovery.

Discovery unsolicited The number of unsolicited discovery requests.

Discovery timeouts The number of timeouts during discovery.

Discovery FCF not avail The number of FCoE Forwarder (FCF)

FIP link service req. unsupp. The number of unsupported FIP link service requests.

FIP link service req. errors The number of FIP link service request errors.

FIP logos received The number of FIP logos received.

Clear virtual link requests The number of clear virtual link requests (needed to terminate virtual links to other ports).

FIP operation unsupp. The number of FCoE Initialization Protocol (FIP) operations that are unsupported.

Tx FCoE unicast frames The number of transmitted FCoE unicast frames.

Tx FCoE unicast vlan frames The number of transmitted FCoE unicast VLANs frames.

FIP untagged frames The number of FCoE Initialization Protocol (FIP) frames that are untagged.

Tx FCoE unicast octets The number of transmitted FCoE unicast octets.

Tx FCoE multicast vlan frames The number of transmitted FCoE multicast VLAN frames.

Tx FCoE multicast octets The number of transmitted FCoE multicast octets.

Tx FCoE multicast frames The number of transmitted FCoE multicast frames.

Tx FCoE broadcast frames The number of transmitted FCoE broadcast frames.

Tx FCoE broadcast vlan frames The number of transmitted FCoE broadcast VLAN frames.

Tx FCoE broadcast octets The number of transmitted FCoE broadcast octets.

Tx timeouts The number of transmissions that timed out.

Transmit parity err The number of transmitted parity errors.

Transmit FID parity err The number of transmitted FCoE Initialization Protocol (FIP) parity errors.

Rx FCoE unicast octets The number of received FCoE unicast octets.

Rx FCoE unicast frames The number of received FCoE unicast frames.

Rx FCoE unicast vlan frames The number of received FCoE unicast VLANs.

Rx FCoE multicast octets The number of received FCoE multicast octets.

Rx FCoE multicast frames The number of received FCoE multicast frames.

Rx FCoE multicast vlan frames The number of received FCoE multicast VLAN frames.

Rx FCoE broadcast octets The number of received FCoE broadcast octets.

Rx FCoE broadcast frames The number of received FCoE broadcast frames.

Rx FCoE broadcast vlan frames The number of received FCoE brocadcast VLAN frames.

Field Description


FCP IM Statistics dialog box A

FCP IM Statistics dialog box The FCP IM Statistics dialog box enables you to display Fibre Channel Protocol Input Method (FCP IM) statistical information for initiators and targets.

Opening the dialog boxSelect Monitor > Statistics > Remote Port Statistics > FCP IM Statistics from the Host Connectivity Manager.

OR

Right-click a remote port from the device tree and select FCP IM Statistics.


Field Description


num rport onlines The number of online R_Ports.

num rport offlines The number of offline R_Ports.

num prli sent out The number of process login (PRLI) requests sent.

num fcxp alloc waits The number of FCXP allocation waits.

num prli rsp errors The number of process login (PRLI) response errors.

num prli rsp accepts The number of process login (PRLI) response accepts.

rport is an initiator Whether the remote port is an initiator.

prli rsp parsing errors The number of process login (PRLI) response parse errors.

num prli rsp rejects The number of process login (PRLI) rejected requests.

num timeouts detected The number of timeouts detected.

num sler notification from bfa The number of second-level errors recovered, reported by BFA.

Total IO Requests The total number of I/O operations on the port.

Data in-bound requests The number of data requests for in-bound data only.

Data out-bound requests The number of data requests for out-bound data only.

Total IO completions The total number of I/O operations that completed successfully.

Write data transfered in bytes The write data that was transferred, measured in bytes.

Read data transfered in bytes The read data that was transferred, measured in bytes.

Slowpath IO completions The number of slowpath IO requests that are completed.

IO underrun The number of successful firmware I/O underrun operations.

IO overrun The number of successful firmware I/O overrun operations.

IO Request-Q wait The number of IO requests in the wait queue.

IO Request-Q wait done The number of IO requests in the wait queue that are completed.

No free IO tag The number of IO tags that are not free.


FCP IM Statistics dialog boxA

IO timeouts The number of IO timeouts.

IO failure due to target offline The number of IO failures caused by an offline target.

IO protocol errors The number of I/O protocol errors.

IO SBC-3 protection errors Number of SCSI block data protection errors for SBC-3 (SCSI Block Command 3).

fcp-2 error recovery failed The number of times an FCP-2 error recovery attempt failed.

Delayed freeing of IO tag The number of IO tags with delayed freeing.

Host IO abort requests The number of host IO abort requests.

Host IO abort completions The number of Host IO aborts that completed.

IO clean-up requests The number of IO clean-up requests.

IO path tov expired The number of IOs where the time out value has expired.

IO abort completions The number of IO aborts that completed.

IO cleaned-up due to IOC down The number of IOs that were cleaned up because the IO Controller went down.

IO comp with unknown tags The number of IO completions with unknown tags.

Abort request due to TM command The number of requests aborted because of target mode (TM) commands.

Abort completion due to TM command

The number of target mode command requests resulting in an abort.

IT Nexus create requests The number of Initiator Target Nexus (ITN) create requests.

IT Nexus FW create requests The number of Initiator Target Nexus (ITN) firmware create requests.

IT Nexus FW create completions The number of Initiator Target Nexus (ITN) firmware create completions.

IT Nexus onlines The number of online Initiator Target Nexus (ITN).

IT Nexus offlines The number of offline Initiator Target Nexus (ITN).

IT Nexus FW delete requests The number of Initiator Target Nexus firmware delete requests.

IT Nexus FW delete completions The number of Initiator Target Nexus firmware delete completions.

IT Nexus delete requests The number of Initiator Target Nexus delete requests.

SLER events The number of second-level error recovery (SLER) events.

Num IOC disables The number of disabled IO controllers.

IT Nexus cleanup completions The number of Initiator Target Nexus cleanup completions.

TM Requests The number of target mode (TM) requests.

TM Completions The number of target mode (TM) completions.

TM initiated IO cleanup success The number of target mode (TM)-initiated IO cleanup requests that succeeded.

TM initiated IO cleanup failure The number of target mode (TM)-initiated IO cleanup requests that failed.

No free TM tag The number of free target mode (TM) tags.

TM Request-Q wait The number of Q wait target mode (TM) requests

Field Description


FCP IM Statistics dialog box A






TM Request-Q wait done The number of Q wait target mode (TM) requests that completed.

TM cleaned-up due to IOC down The number of target mode requests that were cleaned up because the IO Controller went down.

TM cleanup requests The number of target mode (TM) cleanup requests.

TM cleanup completions The number of target mode (TM) cleanup completions.

TM firmware queue resumed Whether the target mode firmware queue has resumed.

Field Description


FCP IM Module Statistics dialog boxA

FCP IM Module Statistics dialog box The FCP IM Module Statistics dialog box enables you to display statistical information for each initiator target nexus (ITN).

Opening the dialog boxSelect Monitor > Statistics > FCP IM Module Statistics from the Host Connectivity Manager.

OR

Right-click a port from the device tree and select Statistics > FCP IM Module Statistics.


Field Description



Start polling button Click to manually poll the FCP IM Module statistics.



Total IO requests The total number of I/O operations on the port.



Total IO completions The total number of I/O operations that completed successfully.

Write data transferred in bytes The write data that was transferred, measured in bytes.

Read data transferred in bytes The read data that was transferred, measured in bytes.

Slowpath IO completions The number of slowpath IO requests that are completed.

IO underrun The number of successful firmware I/O underrun operations.

IO overrun The number of successful firmware I/O overrun operations.

IO request-Q wait The number of IO requests in the wait queue.

IO request-Q wait done The number of IO requests in the wait queue that are completed.

No free IO tag The number of IO tags that are not free.

IO timeouts The number of IO timeouts.

IO failure due to target offline The number of IO failures caused by an offline target.


IO SBC-3 protection errors Number of SCSI block data protection errors for SBC-3 (SCSI Block Command 3).




FCP IM Module Statistics dialog box A

Host IO abort requests The number of host IO abort requests.

Host IO abort completions The number of Host IO aborts that completed.

IO clean-up requests The number of IO clean-up requests.

IO path tov expired The number of IOs where the time out value has expired.




Abort request due to TM command The number of requests aborted because of target mode (TM) commands.


The number of target mode command requests resulting in an abort.


IT Nexus FW create requests The number of Initiator Target Nexus (ITN) firmware create requests.

IT Nexus FW create completions The number of Initiator Target Nexus (ITN) firmware create completions.

IT Nexus onlines The number of online Initiator Target Nexus (ITN).

IT Nexus offlines The number of offline Initiator Target Nexus (ITN).

IT Nexus FW delete requests The number of Initiator Target Nexus firmware delete requests.

IT Nexus FW delete completions The number of Initiator Target Nexus firmware delete completions.

IT Nexus delete requests The number of Initiator Target Nexus delete requests.

SLER events The number of second-level error recovery (SLER) events.


IT Nexus cleanup completions The number of Initiator Target Nexus cleanup completions.

TM Requests The number of target mode (TM) requests.

TM Completions The number of target mode (TM) completions.

TM initiated IO cleanup success The number of target mode (TM)-initiated IO cleanup requests that succeeded.

TM initiated IO cleanup failure The number of target mode (TM)-initiated IO cleanup requests that failed.

No free TM tag The number of free target mode (TM) tags.

TM Request - Q wait The number of Q wait target mode (TM) requests

TM Request - Q wait done The number of Q wait target mode (TM) requests that completed.


TM cleanup requests The number of target mode (TM) cleanup requests.

TM cleanup completions The number of target mode (TM) cleanup completions.

Aborted IO requests The number of aborted I/O requests.

IO timeouts The number of times an I/O operation timed out.

Field Description


FCP IM Module Statistics dialog boxA






IO retry for SQ error recovery The number of I/O retries for sequence level error recovery.

Delayed freeing of IO resources The number of times I/O resource freeing was delayed.

Host IO abort requests The number of aborted I/O requests.



Total IO count The total number of IO operations.

Field Description


Fibre Channel Security Protocol Configuration dialog box A

Fibre Channel Security Protocol Configuration dialog box The Fibre Channel Security Protocol Configuration dialog box enables you to define security authentication on selected ports.

Opening the dialog boxSelect Configure > Authentication from the main menu, or perform the appropriate following step to open the security authentication dialog box:

• From the host level, right-click the host and select Authentication from the list.

The Fibre Channel Security Protocol Configuration (host level) dialog box displays.

• From the adapter level, right-click the adapter and select Authentication from the list.

The Fibre Channel Security Protocol Configuration (adapter level) dialog box displays. This dialog box is identical to the Fibre Channel Security Protocol Configuration (host level) dialog box.

• From the adapter port level, right click a port and select FC-SP > Authentication from the list.

The Fibre Channel Security Protocol Configuration dialog at the host level displays.


Field Description

Port # The port number (0 or 1) for which you are configuring security authentication.

Port WWN The world wide name of the port for which you are configuring security authentication.

Port Name The name of the port (for example, Port 0 or Port 1) for which you are configuring security authentication.

Authentication Check to enable port security authentication.

Status Indicates whether authentication is used.

Algorithm The configured algorithm. Options include MD5, SHA1, MD5SHA1, SHAMD5.

Group Indicates the DH group value. DHNULL (group 0) is the only option.

Enable Authentication check box Check to enable FC-SP authentication on the selected device.

CHAP Secret Type the CHAP secret.

Retype Secret Retype the CHAP secret to confirm.

Algorithm list Select the type of algorithm. Options include the following:• MD5 - A hashing algorithm that verifies a message’s integrity

using Message Digest version 5. • SHA1 - A secure hashing algorithm that computes a 160-bit

message digest for a data file that is provided as input.• MD5SH1 - Similar to the MD5 hashing algorithm, but used for

DH-CHAP authentication.• SHA1MD5 - Similar to the SHA1 hashing algorithm, but used for

DH-CHAP authentication.


Fibre Channel Security Protocol Configuration dialog boxA






Group list The DHNULL (group 0) is the only option available in the list.

Apply button Click to apply the FC-SP settings.

Field Description


Firmware Statistics dialog box A

Firmware Statistics dialog boxThe Firmware Statistics dialog box enables you to display statistical information about the firmware.

Opening the dialog box1. Select a CNA port.

2. Select Monitor > Statistics > Firmware from the Host Connectivity Manager.

OR

Right-click a CEE port from the device tree and select Statistics > Firmware.


Field Description



Start polling button Click to manually poll the Firmware statistics.


IOC Firmware • Enable Requests—The number of IOC firmware enable requests.

• Disable Requests—The number of IOC firmware disable requests.

• Get Attribute Requests—The number of get attribute requests.• Debug sync count—The number of debug synchronizations that

occurred.• Debug dump count—The number of debug dumps that

occurred.• Unknown Requests—The number of IOC firmware requests that

are unknown.

IOC FC Firmware • Config Requests—The total number of configuration requests on the IOC FC firmware.

• UpdateQ Requests—The number of update Q requests on the IOC FC firmware.

• Interrupt Coalesce Requests—The number of times an interrupt coalesce is requested.

• Unknown Requests—The number of IOC FC firmware requests that are unknown.

• Set Interrupt Requests—The number of Set Interrupt requests on the IOC FC firmware.


Firmware Statistics dialog boxA

Firmware IO • host IO aborts—The number of host IO aborts in the firmware.• host IO cleanup—The number of host IO cleanup attempts in

the firmware.• IO timeouts in f/w—The number of IO timeouts in the firmware.• Frames parsed by f/w—The number of frames parsed by the

firmware.• data frames—The number of data frames in the firmware.• fcp rsp frames—The number of FCS responses on the firmware

IO.• xfer_rdy frames—The number of transfer-ready frames.• BLS ACC frames—The number of BLS ACC frames on the

firmware IO.• target abort frames—The number of aborted target frames on

the firmware IO.• unknown frames—The number of unknown frames on the

firmware IO.• itn CISC updated on rsp—The number of CICSs updated on

response.• itn CISC updated on data—The number of CICSs updated on

data.• itn CISC updated on xfer_rdy—The number of updates that

occurred on xfer_rdy.• data frames DMA’ed by f/w—The number of data frames

dropped by the firmware.• frames dropped by f/w—The number of times the firmware

dropped frames.• FCP data frames lost—The number of FCP data frames lost.• RO Set in xfer_rdy—The number of RO set in xfer_rdy events on

the firmware IO.• xfer_rdy OOO error—The number of xfer_rdy_OOO errors on the

firmware IO.• Xfer_rdy unknown error— The number of transfer-ready errors of

unknown origin.• IO ABTS time out—The number of ABTS timeouts on the

firmware IO.• ITN SLER initiated—The number of Initiator Target Nexus (ITN)

second-level error recoveries (SLER) initiated.• REC timeouts—The number of receive timeouts on the firmware

IO.• error REC—The number of errors received on the firmware IO.• REC rsp invalid—The number of invalid receive responses.• seqr IO abort—The number of sequential IO aborts.• seqr IO retry—The number of sequential retries on the firmware

IO.• wait for seq initiative—The number of sequential initiative waits

on the firmware IO.• FCP RSP-wrong IO state—The number of times responses were

in the wrong state.• FCP RSP_underrun—The number of IO response underruns.• FCP RSP_underrun for write—The number of IO response

underruns during write operations.• FCP RSP_underrun err—The number of IO response underrun

errors.

Field Description



Firmware IO (continued) • FCP RSP_invalid residue—The number of invalid residue responses.

• FCP RSP_overrun—The number of overrun responses on the firmware IO.

• FCP RSP_overrun err—The number of overrun response errors on the firmware IO.

• FCP RSP_protocol err—The number of response protocol errors on the firmware IO.

• FCP RSP_sense data err—The number of response sense data errors on the firmware IO>

• FCP RSP_conf requested—The number of RSP_conf requests on the firmware IO.

• target initiated IO abort—The number of RSP_target initiated IO aborts.

• IOH EDTOV timer event—The number of Error Detect Time Out events.

• IOH FCP RSP excp event—The number of FCP response exception events during firmware IO.

• IOH FCP conf event—The number of FCP conf events during firmware IO.

• IOH multi-frm rsp event—The number of multi-frame response events during firmware IO.

• IOH hit class2 event—The number of hit class2 events during firmware IO.

• IOH miss other event—The number of other events missed during firmware IO.

• IOH Seq. count error event—The number of seq count error events during firmware IO.

• IOH length error event—The number of length error events during firmware IO.

• IOH seq length error event—The number of IOH seq length error events during firmware IO.

• IOH data oor event—The number of IOH data events that are out of range during firmware IO.

• IOH RO OOO event—The number of IOH RO events during firmware IO.

• IOH CPU owned event—The number of CPU-owned events during firmware IO.

• IOH unexp frame event—The number of unexpected frame events during firmware IO.

• IOH Error interrupt—The number of interrupted errors during firmware IO.

Field Description



Firmware Port FPG • Interrupts—The number of firmware port interrupts.• Level 0 Interrupts—The number of Level 0 interrupts on the

firmware port.• 0 Caused Interrupts—The number of 0 cause interrupts on the

firmware port.• Interrupts Other—The number of “other” interrupts on the

firmware port.• Interrupts Other Ignored—The number of other interrupts that

are ignored on the firmware port.• Signal Lost—The number of times loss of signal has occurred.• Signal Regained—The number of times loss of signal has been

regained.• Sync Lost—The number of times loss of synchronization has

occurred.• Sync Timeout—The number of times synchronization timeout

has occurred.• Sync Regained—The number of times loss of synchronization

has been regained.• DIV2 Overflow—The number of DIV2 overflow events on the

firmware port.• DIV2 Underflow—The number of DIV2 underflow events on the

firmware port.• EFIFO Overflow—The number of elastic FIFO (EFIFO) overflow

events.• EFIFO Underflow—The number of elastic FIFO (EFIFO) underflow

events.• IDLE Primitives—The number of IDLE primitive events.• LRR Primitives—The number of link reset response (LRR)

primitive events.• LR Primitives—The number of link reset (LR) primitive events.• OLS Primitives—The number of Offline Sequence (OLS)

primitive events.• NOS Primitives—The number of not operational (link has failed)

primitive events.• LIP Primitives—The number of loop initialization (LIP) primitive

events.• ARBFO Primitives—The number of ARBFO primitive events that

occurred on the firmware port.• ARB Primitives—The number of ARB primitive events that

occurred on the firmware port.• MRK Primitives—The number of MRK primitive events that

occurred on the firmware port.• Unknown Primitives—The number of unknown primitive events

that occurred on the firmware port.

Firmware Port PHYSM • Module Inserts—The number of module inserts in the Physical Port State Machine (PHYSM).

• Module Extracts—The number of module extracts in the Physical Port State Machine (PHYSM).

• Module Invalid Events—The number of module invalid events in the Physical Port State Machine (PHYSM).

• Module Validation Ignored—The number of module validation ignored events in the Physical Port State Machine (PHYSM).

• Laser Faults—The number of laser fault events in the Physical Port State Machine (PHYSM).

Field Description



Firmware Port FCoE • CEE linkup—The number of CEE linkups on the FCoE port.• CEE linkdown—The number of CEE linkdowns on the FCoE port.• FIP linkup—The number of FCoE Initialization Protocol (FIP)

linkups.• FIP linkdown—The number of FCoE Initialization Protocol (FIP)

linkdowns.• FIP failures—The number of FCoE Initialization Protocol (FIP)

failures.• Invalid MAC assignments—The number of invalid MAC

assigments on the FCoE port.

Firmware Port FIP • Vlan requests—The number of FCoE Initialization Protocol (FIP) VLAN requests.

• Vlan notifications—The number of FCoE Initialization Protocol (FIP) VLAN notifications.

• Vlan error frames—The number of FCoE Initialization Protocol (FIP) VLAN error frames.

• Vlan request timeouts—The number of FCoE Initialization Protocol (FIP) VLAN request timeouts.

• Vlan invalid—Whether the VLAN is invalid.• Discovery responses—The number of FCoE Initialization

Protocol (FIP) discovery responses.• Discovery error frames—The number of FCoE Initialization

Protocol (FIP) discovery error frames.• Discovery unsolicited—The number of unsolicited FCoE

Initialization Protocol (FIP) discovery requests.• Discovery requests—The number of FCoE Initialization Protocol

(FIP) discovery requests.• Discovery timeouts—The number of FCoE Initialization Protocol

(FIP) discovery timeouts.• Discovery FCF Not Avail.—The FCoE Forwarder (FCF) is not

available for discovery.• Unsupported link service—The number of unsupported FCoE

Initialization Protocol (FIP) link services.• Link service error frames—The number of FCoE Initialization

Protocol (FIP) link service error frames.• LOGO requests—The number of FCoE Initialization Protocol (FIP)

logout requests.• Clear virtual link req.—The number of FCoE Initialization

Protocol (FIP) clear virtual link requests.• Unsupported FIP operation—The number of unsupported FCoE

Initialization Protocol (FIP) operations.• Untagged FIP frames—The number of untagged FCoE

Initialization Protocol (FIP) frames.• Invalid version frames—The number of invalid FCoE

Initialization Protocol (FIP) version frames.

Field Description







Firmware CT MAC MAC turned-on count—The number of times MAC has been turned on.Linkup count—The number of linkups on the Firmware CT.Lost signal count—The number of times loss of signal has occurred. MAC reset count—The number of times MAC has been reset.PCS reset count—The number of times PCS has been reset.DFE on countMAC serdes loopback count—The number of loopbacks on the Serdes loopback type.MAC reset count (loopback)—The number of loopback resets for the MAC.PCS reset count (loopback)—The number of loopback resets for the PCS.

Firmware ETH sndcv MOD CRC frame count—The cyclic redundancy check (CRC) frame count for the Ethernet module.

Firmware CT MOD RxA RDS underrun error—The number of RxA RDS underrun errors on the Firmware CT module.RAD BPC overflow error—The number of RAD BPC overflow errors on the Firmware CT module.RAD RLB BPC overflow error—The number of RAD RLB BPS overflow errors on the Firmware CT module.BPC fcs error—The number of BPC FCS errors on the Firmware CT module.TxA TSO header too long—Indicates if the TxA TSO header is too long.

Field Description


Hardware Tests Diagnostics dialog box A

Hardware Tests Diagnostics dialog box The Hardware Tests dialog box enables you to run tests on the port and to configure parameters such as link speed and frame count.

Opening the dialog box1. Select an HBA, CNA, CEE port, or HBA port from the device tree.

2. Select Configure > Diagnostics from the Host Connectivity Manager.

3. Click the Hardware Tests tab.




• “supportSave” on page 84

Field Description

Memory Test check box Check to run a Memory test on the port.

Ports list Select a port from the list.

PCI Loopback Test check box Check to run a PCI Loopback test on the port.

Data Pattern Type a data pattern. The default value is A5A5A5A5.

Test Cycle text box Specify the number of times the test runs. The default value is 100.

Loopback Test check box Check to run a Loopback test on the port.

Queue Test check box Check to run a Queue test on the port.

Subtest ID list Select a subtest from the list. The default is Internal.

Link Speed list Select a link speed from the list.

Frame Count Type a frame count. The default value is 8192.

Stop on Error check box Check to flag the system to stop running the test if an error occurs.

Test Log table Displays the time the test was run, the status of the test, and the result of the test.

Start button Click to run the selected test.

Stop button Click to stop all pending tests.


HBA Properties panel (HBA only)A

HBA Properties panel (HBA only)The HBA Properties panel enables you to display the properties that are associated with a selected 4 Gbps or 8 Gbps Brocade HBA or mezzanine card.

Opening the panel1. Select an HBA in the device tree.



Field Description

HBA Parameters

Node WWN The adapter node’s world wide name.

Name The name representing the adapter.

Operating Status Whether the HBA is enabled or disabled.

Manufacturer The company that manufactured the HBA.

Model Description The description of the HBA.

Max Speed Supported The maximum speed supported on the HBA; for example, 8 Gbps.

# of Ports The number of ports associated with the HBA.

OEM info Information about the original equipment manufacturer.

Card Type The adapter card type; for example, FC or CNA.

Chip Revision The revision level of the chip.

Hardware Path The hardware path of the HBA.

Serial # The serial number of the HBA.

Temperature The temperature of the HBA, displayed in Celsius and Fahrenheit.

Driver ParametersIt is possible to have multiple pairs of driver information, based on the number and types of drivers installed. The three driver possibilities include the CNA Network Driver, the FCoE Storage Driver, or a single, unified driver.

Driver Name The name of the host adapter driver.

Driver Version The version level of the host adapter driver.

Firmware Parameters

Firmware Version The version level of the firmware.

BIOS Version The version level of the BIOS.

PCI Registers

Vendor ID The identifier of the PCI Register’s vendor.

Device ID The device ID of the PCI Register.

Subsystem ID The ID of the PCI subsystem.


HBA Properties panel (HBA only) A

Subsystem Vendor ID The ID of the PCI subsystem vendor.

Current # of Lanes The number of PCI lanes, in Gbps, each way between the PCI slot and the adapter.

Initial Negotiated # of Lanes The set number of PCI lanes that were initially negotiated.

PCIe Generation The number of times the PCI Register is generated.

OEM Vital Product Data (VPD) InformationNote: This information does not exist for the Brocade 1007 CNA expansion card.

OEM The name of the original equipment manufacturer.

Part # The OEM part number of the HBA.

EDC The engineering date code (HP only), displayed as A-YYWW, where A is the revision, YY is the year minus 1960, and WW is the week of the release. For example, A-4832 is Revision A, week 32 of 2008.

MDC The manufacturing date code (HP only), displayed as YYWW, where YY is the year minus 1960 and WW is the week of manufacturing. For example, 4915 is the 15th week of 2009.

PW The power rating (HP only). The value, 10 W, is the same for all adapters.

EC level The engineering change level for the card, represented by alphanumeric characters.

FRU # The OEM FRU number of the HBA.

Serial # The OEM serial number of the HBA.

Product Description The OEM product description of the HBA.

Vendor Data Displays information that is specific to the HBA vendor.

Field Description


Historical Performance dialog boxA

Historical Performance dialog box The Historical Performance dialog box allows you to generate a historical performance graph for a device

Opening the dialog box1. Select the device for which you want to generate a historical performance graph.

2. Select Monitor > Performance.

3. Select the Enable Historical Data Collection check box.



• “Real-time performance data”

• “Historical performance data”

Field Description

Statistics Name text box Select the type of statistics you want to run from the list. You can display and filter historical statistics on the port, virtual port, Ethernet port, or remote port.

Data for list Select one of the following frequencies:• Last 1 Day—One sample of historical data is collected for 30

minutes’ duration.• Last 1 Week—Two samples of historical data is collected for one

hour’s duration.• Last 1 Month—Four samples of historical data is collected for

two hours’ duration.

Apply button Click to apply your configuration changes.

Statistics Counters options Filter the historical performance statistics by selecting or clearing the following statistics counters check boxes. By default, all of the statistics counters are enabled.• Tx Words (Mbps)—The number of total transmitted Fibre

Channel words across all protocols and classes.• Rx Words (Mbps)—The number of total received Fibre Channel

words across all protocols and classes.• Dropped frames—The number of frames that were lost due to a

lack of host buffers available.• Errored frames—The number of frames received in error.• Loss of sync count—The number of times loss of

synchronization occurred.• Loss of signal count—The number of times loss of signal

occurred.• Rx CRC err frames—The number of frames that have been

received in error.


IOC Statistics dialog box A

IOC Statistics dialog box The IOC Statistics dialog box enables you to view statistics related to the input/output controller (IOC).

Opening the dialog box1. Select a physical port of the HBA or an FCoE port of a CNA from the device tree.

2. Select Monitor > Statistics > IOC Statistics from the Host Connectivity Manager.







Field Description



Start polling button Click to manually poll the IOC statistics.


IOC Driver: Mailbox Interrupt The number of mailbox interrupts on the IOC driver.

IOC Driver: Enable Events The number of enable events on the IOC driver.

IOC Driver: Disable Events The number of disable events on the IOC driver.

IOC Driver: Heartbeat Failures The number of heartbeat failures on the IOC driver.

IOC Driver: Firmware Boots The number of firmware boots on the IOC driver.

IOC Driver: Statistics Timeouts The number of statistics timeouts on the IOC driver.


LLDP Properties panel (CNA only)A

LLDP Properties panel (CNA only)The LLDP Properties panel enables you to display the link layer properties that are associated with the selected converged network adapter (CNA), both locally and remotely.

Opening the panel1. Select a CNA in the device tree.

2. Click the LLDP tab in the right pane.


Field Description

Chassis ID The MAC address associated with the local system.

Port Description The user-configured port description.

Port ID The port identification associated with the transmitting LLDP agent.

System Name The user-configured name of the local system.

System Description The system description containing information about the software and current image running on the system.

System Capabilities The primary functions performed by the system. The capabilities that the system supports are not configurable, but are based on the model of the product.

Time to Live The age of the information propogated in LLDP frames. Time to live (TTL) values are measured in seconds.


Logical Port Statistics dialog box A

Logical Port Statistics dialog box The Logical Port Statistics dialog box enables you to display statistics that are related to a selected logical port.

Opening the dialog boxSelect Monitor > Statistics > Logical Port Statistics from the Host Connectivity Manager

OR

Right-click a logical port (LPORT) from the device tree and select Logical Port Statistics.

Fields and componentsNS

Field Description



Start polling button Click to manually poll the logical port statistics.



ns_plogi_sent The number of Name Server port logins sent.

ns_plogi_rsp_err The number of Name Server response errors.

ns_plogi_acc_err The number of Name Server port login accept errors.

ns_plogi_accepts The number of times Name Server port logins are accepted.

NS command rejects The number of Name Server port login rejects.

ns_plogi_unknown_rsp The number of unknown Name Server port login response errors.

ns_plogi_alloc_wait The number of delayed Name Server port login response errors.

NS command retries The number of name server command retries.

NS command timeouts The number of name server command timeouts.

ns_rspnid_sent The number of times the Name Server Register Symbolic Port Name identifier was sent.

ns_rspnid_accepts The number of times the Name Server Register Symbolic Port Name identifier was accepted.

ns_rspnid_rsp_err The number of Name Server Register Symbolic Port Name identifier response errors.

ns_rspnid_rejects The number of Name Server Register Symbolic Port Name identifier rejects.

ns_rspnid_alloc_wait The number of Name Server Register Symbolic Port Name identifier allocations.

ns_rftid_sent The number of Name Server Register FC4 Type identifier requests sent.


Logical Port Statistics dialog boxA

ns_rftid_accepts The number of times the system accepted Name Server Register FC4 Type identifier requests.

ns_rftid_rsp_err The number of Name Server Register FC4 Type identifier response errors.

ns_rftid_rejects The number of times the system rejected Name Server Register FC4 Type identifier requests.

ns_rftid_alloc_wait The number of delayed Name Server Register FC4 Type identifier allocations.

ns_rffid_sent The number of Name Server RFID tag requests sent.

ns_rffid_accepts The number of times the system accepted Name Server RFID tag requests.

ns_rffid_rsp_err The number of Name Server RFID tag response errors.

ns_rffid_rejects The number of Name Server RFID tag rejects.

ns_rffid_alloc_wait The number of Name Server RFID tag allocations.

ns_gidft_sent The number of Name Server Get all Port ID requests sent.

ns_gidft_accepts The number of times the system rejectedName Server Get all Port ID requests.

ns_gidft_rsp_err The number of delayed Name Server Get all Port ID allocations.

ns_gidft_rejects The number of times a Name Server Get all Port ID request for a given FC4 type is rejected.

ns_gidft_unknown_rsp The number of unknown responses associated with a Name Server Get all Port ID request for a given FC4 type.

ns_gidft_alloc_wait The number of delayed Name Server Get all Port ID requests for a given FC4 type allocations.

MS command retries The number of MS command retries.

MS command timeouts The number of times an MS command timed out.

ms_plogi_sent The number of port login requests sent.

ms_plogi_rsp_err The number of response errors associated with a ms port login.

ms_plogi_acc_err The number of accept errors associated with a ms port login.

ms_plogi_accepts The number of ms port login accepts.

MS command rejects The number of MS command rejects.

ms_plogi_unknown_rsp The number of ms port login unknown responses.

ms_plogi_alloc_wait The number of delayed ms plogin allocations.

Num of RSCN received The number of Registered State Change Notifications received.

Num portid format RSCN The number of Registered State Change Notifications received by Port ID.

Unsolicited recv frames The number of received frames that were unsolicited.

Dropped received frames The number of received frames that were dropped.

Received plogi The number of times port logins are received.

Received adisc The number of times discover address (ADISC) requests are received.

Field Description


Logical Port Statistics dialog box A

Received prlo The number of times PRLOs are received.

Received prli The number of times PRLIs are received.

Received logo The number of times logouts are received.

Received rpsc The number of Report Port Speed Capabilities (RPSC) requests received.

Received unhandled ELS The number of unhandled ELS requests.

Rport plogi retry timeout count The total number of timeouts that occurred during port login attempts on the remote port.

Deleted rport (max retry of plogi) The number of remote ports deleted after the maximum number of port login retries.

Total IO Requests The total number of IO requests.



Total IO completions The total number of IO operations that completed.

Data transferred in bytes The transferred data, measured in bytes.

Slowpath IO completions The number of I/Os completed in slowpath handling.

IO underrun The number of I/O underrun operations.

IO overrun The number of I/O overrun operations.

IO Request-Q wait The number of Q wait IO requests.

IO Request-Q wait done The number of completed Q wait IO requests.

No free IO tag The number of no free IO tags.

IO timeouts The number of times an I/O timed out.

IO failure due to target offline The number of IO failures due to an offline target.


IO SBC-3 protection errors The number of IO errors for SBC-3 (SCSI Block Command 3).



Host IO abort requests The number of host IO abort requested.

Host IO abort comps The number of completed host IO aborts.

IO clean-up requests The number of IO clean up requests.

IO path TOV expired The number of IOs where the time out value has expired.


IO cleaned up due to IOC down The number of IOs that were cleaned up because the IO Controller is offline.


Abort request due to TM command The number of target mode abort requests.


The number of completed aborts because of a target mode command.

Field Description


Logical Port Statistics dialog boxA







IT Nexus FW create requests The number of Initiator Target Nexus (ITN) requested firmware create requests.

IT Nexus FW create completions The number of Initiator Target Nexus (ITN) requested firmware create completions.

IT Nexus onlines The number of Initiator Target Nexus (ITN) that are online.

IT Nexus offlines The number of Initiator Target Nexus (ITN) that are offline.

IT Nexus delete requests The number of Initiator Target Nexus (ITN) requested deletes.

IT Nexus FW delete requests The number of Initiator Target Nexus (ITN) requested firmware deletes.

IT Nexus FW delete completions The number of Initiator Target Nexus (ITN) completed firmware deletes.

SLER requests The number of second level error recovery (SLER) event requests.


IT Nexus cleanup completions The number of Initiator Target Nexus (ITN) completed cleanups.

TM Requests The number of task management requests.

TM Completions The number of task management completions.

TM initiated IO cleanup success The number of successful task management initiated IO cleanups.

TM initiated IO cleanup faulures The number of failed task management initiated IO cleanups.

No free TM tag The number of free task management tags.

TM Request-Q wait The number of Q wait task management requests.

TM Request-Q wait done The number of completed Q wait task management requests.

TM cleaned-up due to IOC down The number of task management cleanups due to an offline IO controller.

TM cleanup requests The number of requested task management cleanups.

TM cleanup completions The number of completed task management cleanups.

Field Description


LPORT Properties panel A

LPORT Properties panel The LPORT Properties panel enables you to display the properties that are associated with a logical port.

Opening the panel1. From the device tree, select a physical port.

2. Click the LPORTs Properties tab in the right pane.


Field Description

Base Port Indicates whether the logical port is used as the base port.

FC Address The Fibre Channel address of the logical port.


Node WWN The adapter’s world wide name.

Port WWN The port’s world wide name.

Roles The role of the logical port; for example, FCP Initiator.

State Displays whether the logical port is online or offline.

Switch IP Addr The switch’s IP address.

Switch NWWN The switch node’s world wide name.

Symbolic Name The symbolic name associated with the logical port.


Master Log tabA

Master Log tab The Master Log enables you to display a list of all events that have occurred.

Opening the tabClick the Master Log tab, located on the bottom pane of the Host Connectivity Manager.

A master summary of events on all discovered devices is displayed.


Using the tabRefer to the following topics for specific procedures using this dialog box:




Field Description

Filter button Click to launch the Master Log Filter dialog box.

Sr No column Displays a numbering sequence in ascending order.

Severity column The event severity (informational, minor, major, or critical).

WWN/MAC column The world wide name or the media access control (MAC) address of the device on which the event occurred.

Category column The event categories are as follows:• ADAPTER - Events pertaining to the adapter.• CEE - Events pertaining to Converged Enhanced Ethernet.• ETHPORT - Events pertaining to the Ethernet port.• IOC - Events pertaining to the IO Controller.• IP over FC - Events pertaining to IP over Fibre Channel.• VLAN - Events pertaining to a virtual LAN.• PORT - Events pertaining to a physical port.• LPORT - Events pertaining to a specific logical port (one logical

port always exists per physical port).• RPORT - Events pertaining to a specific remote port (could be

an initiator or target).• ITNIM - Events pertaining to an initiator-target nexus.• RSVD - Reserved.• AUDIT - Audit events.

Subcategory column The subcategory of the main event; for example, offline, online, disabled, or enabled.

Description column Displays a brief description of the event.

Date/Time column The date and time when the event occurred.

Clear Filter button Click to clear the Master Log filter.

Refresh button Click to refresh the screen.


Master Log Filter dialog box A

Master Log Filter dialog box The Master Log Filter dialog box enables you to filter the events you receive by time, severity, category, or world wide name.

Opening the dialog box1. Select the Master Log tab, located at the bottom pane of the Host Connectivity Manager,

2. Click the Filter button.






Field Description

Event Time Type in a From and To value to represent the time during which events will be logged.

Event Severity Select one or all of the following values: Critical, Major, Minor, Information.

Category Select an event category, for example, Rport or ITNIM, from the list.

WWN/MAC Select a world wide name (WWN) or media access control (MAC) address from the list.


Persistent Binding dialog boxA

Persistent Binding dialog box The Persistent Binding dialog box enables target port world wide name binding to a persistent target ID for the OS stack. You can view the Persistent Binding dialog box at the host level, the adapter level, or the port level.

Opening the dialog box1. Select a device that supports persistent binding from the device tree.

Devices that support persistent binding include the local host, the adapter, and the port.

2. Select Configure > Persistent Binding.



• “Basic port configuration”

Field Description

At the host or CNA level

Serial Number The serial number of the CNA.

Hardware Path The hardware path of the CNA.

Port # The port number of the CNA.


Name The port name; for example, Port 0 or Port 1.

Persistent Type The type of binding; for example, Port WWN.

Target Name The SCSI target name.

Remote Port WWN The world wide name of the remote port.

SCSI Target ID The SCSI target identifier.

At the port level

HBA or CNA Node The world wide node name of the HBA or CNA node.

HBA or CEE port The world wide name of the HBA or CNA port.

Persistent type The type of binding; for example, Port WWN.

Target Name The SCSI target name.

Remote Port WWN The world wide name of the remote port.

SCSI Target ID The SCSI target identifier.


Port POM Properties panel A

Port POM Properties panel The Port POM Properties panel enables you to monitor the SFP attributes. A notification is given for any parameters that are not within the configured power, temperature, voltage, and current specification policy.

NOTEOnly Brocade-branded SFPs and SFPs+ are supported with the 8 Gbps FC HBAs and 10 Gbps CNAs.

Opening the panel1. Select a port in the device tree.

2. Click the POM tab in the right pane.


Field Description

Temperature(C) The port temperature, measured in Celsius.

Bias Current (mA) The low-level DC current (the Bias Current), measured in mA.

Tx Power (mW) The transmitted power, measured in mW.

Rx Power (mW) The received power, measured in mW.

Voltage The voltage; for example, 1.8V, 3.3V, or 5.0V.

Alarm/Warning The state of the port POM.


Port Properties panel (HBA only)A

Port Properties panel (HBA only)The Port Properties panel enables you to display the properties that are associated with a selected HBA port.

NOTEQoS properties apply only to the HBA.




Field Description

Port Parameters

Port # The port number: 0 or 1.



Factory Port WWN The factory-assigned port world wide name.

Factory Node WWN The factory-assigned adapter world wide name.

Name The name that is manually assigned to the port.

FC Address The port’s Fibre Channel address.

Media Type of media software; for example, 8G-sw.

Port Type The port type; for example, N_Port.

Configured Port State Indicates whether the port is enabled or disabled.

Operating Port State Indicates whether the link is online or offline.

Supported Classes The types of classes that are supported on the port; for example, Class-3.

Configured Speed The configured port speed.

Operating Speed The speed at which the port is operating. The unit of measurement is in gigabits per second (Gbps). The available speed options depend on the HBA’s speed and the port’s SFP. Auto-negotiate is the recom-mended setting and it is the default.For the 4 Gbps HBA (425 and 415) and the mezzanine card (804), speed options are 1 Gbps, 2 Gbps, 4 Gbps, and 8 Gbps. The 8 Gbps HBA (825, 815) does not support the 1 Gbps speed.

Max Speed Supported The maximum speed that is supported on the port, which is 8 Gbps.

Operating Topology The topology setting at which the port is operating. Only point to point (P2P) mode is supported.

Receive BB Credits The maximum number of receive buffers.

Transmit BB Credits The maximum number of transmit buffers.


Port Properties panel (HBA only) A


• “Configuring the port speed using HCM”

• “Specifying the maximum frame size using HCM”

• “Specifying path time out using HCM”

• “Configuring the HCM logging level using HCM”

• “Enabling and disabling rate limiting on the adapter side using HCM”

IOC ID The I/O controller’s identifier.

Hardware Path The hardware path of the HBA port.

Frame Data Field Size The frame size, in byres, of the port. The default is 2112. Select auto to set the frame data field size automatically.

# of Lports The number of logical ports in the configuration.

Operating Parameters

Link Beacon State Indicates whether link beaconing is on or off.

Path Time Out The value between 0 and 60 that specifies the time out session.

Logging Level The port logging level. Values include Log Critical, Log Error, Log Warning, Log Info, and Log Invalid.

Target Rate Limit Indicates whether target rate limiting is on or off.

Default Rate Limit Select the target rate limit from the list. Options include 1 Gbps, 2 Gbps, and 4 Gbps. The default is 2 Gbps.

FC-SP Parameters

Authentication Indicates whether FC-SP authentication is on or off.

Status The status of Fibre Channel Security Protocol (FC-SP) authentication.

Algorithm The configured authentication algorithm.

Group The DH Group (DH Null, group 0, is the only option).

Error Status The health status of the Fibre Channel Security Protocol (FC-SP) parameters.

QoS Parameters

Configured QoS State Indicates whether QoS is enabled or disabled.

Operating QoS State Indicates whether QoS is online or offline.

Total BB Credit The total number of receive buffers.

Priority Levels QoS priority levels. Values include High, Medium, and Low.

Persistent Binding Indicates whether persistent binding is on or off.

Field Description


Port Statistics dialog boxA

Port Statistics dialog box The Port Statistics dialog box enables you to monitor the performance of the adapter and the traffic between the adapter and the LUNs. You can use the information to isolate and troubleshoot areas that affect application performance.

Opening the dialog boxSelect Monitor > Statistics > Port Statistics from the Host Connectivity Manager.


Field Description



Start polling button Click to manually poll the Port statistics.



Frames 64 bytes The number of 64-byte frames.







Tx bytes The number of transmitted bytes.

Tx packets The number of transmitted packets.

Tx multicast packets The number of transmitted multicast packets.

Tx broadcast packets The number of transmitted broadcast packets.

Tx control frame The transmitted control frames.

Tx drops The number of transmitted frames dropped.

Tx jabber The number of transmitted jabbers (illegal packet length).

Tx FCS errors The number of frame check sequence (FCS) errors transmitted, which indicate that frames of data are corrupted.

Tx fragments The number of transmitted frame packets that are fragmented.

Rx bytes The number of received bytes.

Rx packets The number of received packets.

Rx multicast packets The number of received multicast packets.

Rx broadcast packets The number of received broadcast packets.


Port Statistics dialog box A

Rx control frames The number of received control frames, which assist in data frame delivery.

Rx unknown opcode The number of unknown opcode frames received.

Rx drops The number of received packet drops.

Rx jabber The number of received jabber frames (count of frames that exceed 1518 (non-VLAN) or 1522 (VLAN) bytes and contain an invalid FCS, including alignment errors).

Rx FCS errors The number of frames that have a integral of 64 to 1518 length and contain a frame check sequence (FCS) error.

Rx alignment errors The number of packets received with alignment errors.

Rx frame len errors The number of frames received in which the 802.3 length field did not match the number of data bytes actually received.

Rx code errors The number of frames received with at least one invalid data symbol.

Rx fragments The number of received frames that are less than 64 bytes in length and contain an invalid FCS (includes integral and non-integral lengths).

Rx pause The number of received pauses.

Rx zero pause The number of received zero pauses.

Tx pause The number of transmitted pauses.

Tx zero pause The number of transmitted zero pauses.

Rx FCoE pause The number of times a pause control frame was received by a congested FCoE port to wait a predetermined amount of time before retransmitting data.

Rx FCoE zero pause The number of times a zero pause control frame was received by a congested FCoE port.

Tx FCoE pause The number of times a pause control frame was transmitted to a congested FCoE port to wait a predetermined amount of time before retransmitting data.

Tx FCoE zero pause The number of times a zero pause control frame was transmitted to a congested FCoE port.

Rx iSCSI pause The number of received iSCSI pauses.

Rx iSCSI zero pause The number of received iSCSI zero pauses.

Tx iSCSI pause The number of transmitted iSCSI pauses.

Tx iSCSI zero pause The number of transmitted iSCSI zero pauses.

Field Description


Port Statistics dialog boxA







Protocol Tests dialog box A

Protocol Tests dialog box The Protocol Tests dialog box enables you to run diagnostic tests on Fibre Channel components.

Opening the dialog box1. Select Configure > Diagnostics from the Host Connectivity Manager.

2. Click the FC Protocol Tests tab.




• “supportSave collection sources”

Field Description

Echo Test check box Check to run an Echo Test on the selected port.

FC Ping Test check box Check to run an FC Ping Test on the selected port.

FC Trace Route check box Check to run an FC Traceroute on the selected port.

Add button Click to add a selected port, logical port, or target to the test list.

Remove button Click to remove a selected port, logical port, or target from the test list.

Remove All button Click to remove all ports, logical ports, and targets from the test list.

Test Cycle text box Specify the number of times the test runs. The default value is 100.

Test Log table Displays the time the test was run, type of test run, status of the test, configuration, and the results.

Port list Select a port on which the test will be run from the list.

Target list Select a target on which the test will be run from the list.

Logical Port list Select a logical port on which the test will be run from the list.

Stop on Error check box Check to flag the system to stop running the test if an error occurs.

Start button Click to run the selected test.

Stop button Click to stop all pending tests.


QoS Statistics dialog box (HBA only)A

QoS Statistics dialog box (HBA only)The QoS Statistics dialog box enables you to view statistics related to Quality of Service (QoS).

Opening the dialog boxSelect Monitor > Statistics > QoS Statistics from the Host Connectivity Manager.







Field Description


QoS ELP Accepted The number of ELPs (Exchange Link Parameters) accepts sent.

QoS ELP dropped The number of ELPs dropped.

QoS ELP received The number of ELPs successfully received.

QoS ELP rejected The number of ELPs rejected.

QoS Flogi Acc received The number of QoS Fabric login (Flogi) accept requests received.

QoS Flogi rejects received The number of QoS Fabric login (Flogi) rejects received.

QoS Flogi retries The number of QoS Fabric login (Flogi) retries.

QoS Flogi sent The number of QoS Fabric login (Flogi) requests sent.

QoS RSCN received The number of Registered State Change Notifications (RSCN) received.


Real-time Performance Statistics dialog box A

Real-time Performance Statistics dialog boxThe Realtime Statistics dialog box enables you to display the properties that are associated with the selected CEE port.

Opening the dialog box1. Select a CEE port in the device tree.

2. Select Performance > Realtime Statistics > Historical Statistics.


Field Description

Statistics Name list The type of real time performance statistics. Options include:• Port statistics on both the HBA and the CNA• Virtual Port statistics on the virtual port• Ethernet Port statistics on the Ethernet node• FCP IM statistics on the remote port

Polling Interval list Select the polling interval. Options include 10 seconds, 20 seconds, or 30 seconds

Apply button Click to save your configuration settings.

Statistics Counters • Tx bytes (Mbps)—The number of transmitted bytes.• Rx bytes (Mbps)—The number of received bytes.• Tx drops—The number of dropped transmitted frames.• Rx drops—The number of dropped received frames.• Tx FCS errors—The number of frame check sequence (FCS)

errors transmitted, which indicate that frames of data are corrupted.

• Rx FCS errors—The number of frame check sequence (FCS) errors received, which indicate that frames of data are corrupted.

• Rx packets—The number of received packets.

Port Statistics - Utilization (Mbps) graph

Displays the port’s utilization statistics, measured in Mbps.

Port Statistics - Errors/sec graph Displays the port’s errors, measured in errors per second.


Remote Port Properties panelA

Remote Port Properties panel The Remote Port Properties panel enables you to display the properties that are associated with the remote port.

Opening the panel1. From the device tree, select a remote port (target or initiator).

2. Click the Remote Port Properties tab in the right pane.

NOTEIf it is a target port, there are two tabs in the right pane: Properties and LUNs.


Field Description

Fibre Channel Parameters

Port WWN The world wide name of the device’s port.

Node WWN The world wide name of the device.

Symbolic Name The symbolic name associated with the remote port.

Name The name associated with the device.

FC Address The remote port’s Fibre Channel address.

Frame Data Field Size The frame size, in byres, of the port. The default is 2112. Select auto to set the frame data field size automatically.

Status The remote port status: online or offline.

Supported Classes The types of classes that are supported on the remote port; for example, Class-3.

Remote Device Information

Role The role of the remote device: target or initiator.

FCP-IM IO Latency Information (if Profile is on)

IO Size The actual IO latency size.

IO Latency Min The minimum IO latency size.

IO Latency Max The maximum IO latency size.

IO Latency Average The average IO latency size.

Binding Information

Bind Type The mode used to persistently bind target mappings.

Bus # The unique identifying number for each PCI bus, assigned during system initialization.

Target ID The identifier of the target device.


Restore dialog box A

Restore dialog boxYou can use the Restore Data dialog box to restore data that has been previously backed up. The Host Connectivity Manager (HCM) stores the location and version details of the most recently-taken backed up data and automatically points to the location of the data.

NOTEUse HCM 2.1 or later to restore backed up data. HCM 2.0 and earlier versions do not support the Restore Data feature.

The following data is restored:

• HBA application configuration data (HBAApplication.properties)

• HCM user authentication data (noitacitnehtua.properties)

• Alias Configuration data (HbaAliasdb.properties)

• Setup Discovery Data (SetupDiscovery.properties)

• Syslog Data (Syslog.properties)

• HCM Logging Data (logging.properties and log4j.xml)

• SupportSave

Opening the dialog box1. Select the host, an adapter, or a port from the device tree.

2. Select Tool > Restore Data from the main menu.

The Restore Data dialog box displays.


Field Description

Restore from previous backup data button

Click to enable the Browse button, which enables you to locate the last backed-up file.

Browse button Click to navigate to where the last backed-up file resides.

Restore default data button If you click this button, the default configuration is restored.

Start Restore button Click to restore the backed up data that you selected.


SFP Properties panelA

SFP Properties panel The SFP Properties panel enables you to display the properties that are associated with a selected small form-factor pluggable (SFP) transceiver.

NOTEBrocade 804 mezzanine cards connect to the embedded switch modules or embedded interconnect modules on the Blade System chassis by way of an internal backplane and therefore, no optical modules (SFPs) are involved. With the exception of no SFPs, the Brocade 804 mezzanine FC HBA card functions the same as the other Brocade HBAs.


2. Click the SFP or SFP+ tab in the right pane.

NOTEOnly Brocade-branded SFPs are supported with the 8 Gbps FC HBAs and SFPs+ with the 10 Gbps CNAs.


Field Description

Port Technology

SFP Supported The name of the supported SFP.

Connector Type The type of port connector; for example, LC. SC, or Cu (copper cable).

Transceiver The type of transceiver; for example, XFP or GBIC.

Media The type of media for the transceiver; for example, single mode.

Speed The port speed. Options for the 8 Gbps HBA (825 and 815) are 2 Gbps, 4 Gbps, and 8 Gbps (1 Gbps not supported). Port speed options for the 4 Gbps HBA (425 and 415) and the mezzanine card (804) are 1 Gbps, 2 Gbps, 4 Gbps, and 8 Gbps. For the 10 Gbps CNA, the only speed option is auto-negotiate.

Extended Information

Identifier The identifier for the extended link.

Encoding Displays how the extended link is encoded, for example, 8B10B.

Baud Rate The transmission rate, roughly equivalent to the number of bits per second.

Length 9u The length of the single-mode fiber optic cable, used in situations where gigabit performance is not required (for distances greater than 100 meters).

Length 50u The length of the fiber optic cable (for distances greater than 10 meters).

Length 62.5u The length of the fiber optic cable (for distances greater than 10 meters).


SFP Properties panel A

Length Cu The length of the copper cable (for distances greater than 1 meter, where optimum performance is required).

Vendor Name The vendor of the extended link.

Vendor OUI The vendor’s organizational unique identifier (OUI).

Vendor Part The part number of the extended link.

Revision The revision level of the extended link.

Wavelength The wavelength translation, which enables longer reach through lower attenuation.

Options Displays details about the transceiver; for example, the type of port connector, type of transceiver, and enable/disable status.

BR Max The upper bit rate limit at which the SFP transceiver meets its specifications.

BR Min The lower bit rate limit at which the SFP transceiver meets its specifications.

Serial # The serial number of the SFP.

Date Code The date the SFP was manufactured.

Refresh button Click to refresh the screen.

Field Description


Syslog Server Configuration dialog boxA

Syslog Server Configuration dialog box The Syslog Server Configuration dialog box enables you to configure the host connectivity manager (HCM) to send Syslog messages to other computers through port 514. You can configure the HCM agent to forward events to a maximum of three Syslog destinations.

Opening the dialog box1. Select the host from the device tree.




• “Syslog support”

• “Registering a host server”

• “Removing a host server”

Field Description

Host name / IP Address text box Enter the host name or IP address of the destination device.

Set this IP in all discovered agents in future check box

Click to set the device as a Syslog destination in all future discovered agents.

Add button Click to register the host as a Syslog destination.

Remove button Click to remove the host as a Syslog destination.


Target Statistics dialog box A

Target Statistics dialog box The Target Statistics dialog box enables you to display statistical information for a selected remote port (R_Port) or FCoE port.

Opening the dialog boxSelect Monitor > Statistics > Remote port statistics > Target Statistics from the Host Connectivity Manager.

OR

Right-click a remote port and select Target Statistics.


Field Description


offlines The remote ports that are offline.

onlines The remote ports that are online.

RSCN The number of Fibre Channel Registered State Change Notifications (RSCNs) received.

PLOGI sent The number of times port logins (when two node ports in the SAN establish a connection between each other) occur.

PLOGI accepts The number of times port logins are accepted.

PLOGI timeouts The number of times port logins time out.

PLOGI failed The number of times port logins fail.

PLOGI rejects The number of times port logins are rejected.

PLOGI received The number of times port logins are received.

PRLI received The number of times PRLIs are received.

ADISC sent The number of discover address (ADISC) requests sent.

ADISC accepts The number of times discover address (ADISC) requests are accepted.

ADISC failed The number of times discover address (ADISC) requests fail.

ADISC rejects The number of times discover address (ADISC) rejects.

ADISC received The number of times discover address (ADISC) requests are received.

ADISC rejected The number of times discover address (ADISC) requests are rejected.

LOGO sent The number of times logouts occur.

LOGO accepts The number of times logouts are accepted.

LOGO failed The number of times logouts fail.

LOGO rejected The number of times logouts are rejected.


Target Statistics dialog boxA

LOGO received The number of times logouts are received.

RPSC received The number of Report Port Speed Capabilities (RPSC) requests received.

RPSC rejects The number of Report Port Speed Capabilities (RPSC) requests rejected.

RPSC sent The number of Report Port Speed Capabilities (RPSC) requests sent.

RPSC accepts The number of accepted Report Port Speed Capabilities (RPSC) requests.

RPSC rejected The number of rejected Report Port Speed Capabilities (RPSC) requests.

RPSC failed The number of failed Report Port Speed Capabilities (RPSC) requests

uninit: create events The number of hardware abstraction layer (HAL) uninit create events.

uninit: exception events The number of hardware abstraction layer (HAL) uninit exception events.

created: online events The number of hardware abstraction layer (HAL)-created online events.

created: delete events The number of hardware abstraction layer (HAL)-created delete events.

created: IOC Down The number of times hardware abstraction layer (HAL)-created I/O controllers were down.

created: exception events The number of hardware abstraction layer (HAL)-created exception events.

fw create: f/w responses The number of hardware abstraction layer (HAL) firmware-create responses.

fw create: delete events The number of hardware abstraction layer (HAL) firmware-created delete events.

fw create: offline events The number of hardware abstraction layer (HAL) firmware created offline events.

fw create: IOC down The number of times hardware abstraction layer (HAL) firmware- created I/O controllers were down.

fw create: exception events The number of hardware abstraction layer (HAL) firmware-created exception events.

online: offline events The number of hardware abstraction layer (HAL) online and offline events.

online: delete events The number of hardware abstraction layer (HAL) online delete events.

online: IOC down events The number of hardware abstraction layer (HAL) online IOC down events.

online: exception events The number of hardware abstraction layer (HAL) online exception events.

fw delete: fw responses The number of hardware abstraction layer (HAL) fw Delete f/w responses.

Field Description


Target Statistics dialog box A

fw delete: delete events The number of hardware abstraction layer (HAL) fw Delete Delete events.

fw delete: IOC down events The number of hardware abstraction layer (HAL) fw Delete IOC down events.

fw delete: exception events The number of hardware abstraction layer (HAL) fw Delete Exception events.

offline: delete events The number of hardware abstraction layer (HAL) Offline Delete events.

offline: online events The number of hardware abstraction layer (HAL) Offline Online events.

offline: IOC down events The number of hardware abstraction layer (HAL) offline IOC down events.

offline: exception events The number of hardware abstraction layer (HAL) offline exception events.

delete: fw events The number of hardware abstraction layer (HAL) delete f/w events.

delete: IOC down events The number of hardware abstraction layer (HAL) Delete IOC down events.

delete: exception events The number of hardware abstraction layer (HAL) delete exception events.

delete pend: fw responses The number of hardware abstraction layer (HAL) delete pend f/w responses.

delete pend: IOC downs The number of hardware abstraction layer (HAL) delete pending IOC downs.

delete pend: exceptions The number of hardware abstraction layer (HAL) delete pending exceptions.

off-pending: fw responses The number of hardware abstraction layer (HAL) off-pending f/w responses.

off-pending: deletes The number of hardware abstraction layer (HAL) off-pending deletes.

off-pending: IOC downs The number of hardware abstraction layer (HAL) off-pending IOC downs.

off-pending: exceptions The number of hardware abstraction layer (HAL) off-pending exceptions.

IOC down: offline events The number of hardware abstraction layer (HAL) IOC down offline events.

IOC down: delete events The number of hardware abstraction layer (HAL) IOC down delete events.

IOC down: online events The number of hardware abstraction layer (HAL) IOC down online events.

IOC down: exceptions The number of hardware abstraction layer (HAL) IOC down exception events.

Field Description


Target Statistics dialog boxA







Teaming Configuration dialog box (CNA only) A

Teaming Configuration dialog box (CNA only)The Teaming Configuration dialog box enables you to bundle several physical ports together to form a single, higher-bandwidth logical link. Teaming is also known as link aggregation. Aggregated links provide redundancy and fault tolerance.

Opening the dialog boxFrom the host level:

1. Select the local host from the device tree.

2. Select Configure > Teaming from the main menu.

OR

Right-click the local host and select Teaming from the list.

The Teaming Configuration dialog at the host level displays.


Field Description

Teams list Lists existing teams.

Team Name text box Lists the current team that was selected from the Teams list.

Team Mode list Lists the team mode. Values are 802.3ad, failover, and failback. Note that link aggregation groups only work if all the ports are part of the same switch but failover and failback can work if the ports are on multiple switches.

MAC Address The team’s media access control (MAC) address.

Active Link The active Ethernet link between the host and the switch.

Transmit Policy list The transmit policy for sending out packets. The values are:• l2 (source MAC XOR destination MAC) % (team member count).

l2 is the default.• l3-l4 ((source port XOR dest port) XOR ((source IP XOR dest IP)

and 0xffff) % (team member count)

Members list Lists all the ports that are available for selection.

Selected Ports list Lists the ports that were selected to be members of the team.

Set Primary button Sets the primary interface for the team.

Add button There are two Add buttons on the Teaming dialog:• Click the Add button beneath the Team Name text box to add a

team.• Click the Add button next to the VLANs table to launch the VLAN

Configuration dialog box.

Delete button Click the Delete button beneath the Team Name text box to delete a team.


Teaming Configuration dialog box (CNA only)A


• “VLAN configuration” on page 59

Statistics button There are two Statistics buttons on the Teaming dialog:• Click the Statistics button beneath the Team Name text box to

launch the Teaming Statistics dialog box.• Click the Statistics button next to the VLANs table to launch the

VLAN Statistics dialog box.

VLANs list The list of VLANs that are available to add, edit, remove, or display statistics.

Add button Click to launch the Add VLAN dialog box, where you can configure a new VLAN to be added to the VLANs list.

Edit button Select an existing VLAN from the VLANs list and click to edit the VLAN.

Remove button Select an existing VLAN from the VLANs list and click to edit the VLAN.

Statistics button Select an existing VLAN from the VLANs list and click to display the VLAN statistics.

Apply button Click to apply your configuration changes.

Field Description


Teaming Statistics dialog box (CNA only) A

Teaming Statistics dialog box (CNA only)The Teaming Statistics dialog box enables you to display statistics related to aggregated links (teams).

Opening the dialog box1. Select the local host icon from the device tree.

2. Select Configure > Teaming from the Host Connectivity Manager.

OR

Right-click the local host icon and select Teaming.

The Teaming dialog box displays.

3. Click the Statistics button beneath the Teams text box.



• “VLAN configuration” on page 59

Field Description



Start polling button Click to manually poll the Teaming statistics.

Date The date the Teaming statistics were run.

Team ID The Team ID associated with the team members.

Tx Packets The number of transmitted packets.

Rx Packets The number of received packets.

Tx Error Packets The number of transmitted error packets.

Rx Error Packets The number of received error packets.

Duration The length of time between byte transmission and reception.

Status The connection status.


Test Log Details dialog boxA

Test Log Details dialog box The Test Log Details dialog box enables you to view details about a selected port or protocol test.

Opening the dialog box1. Select Configure > Diagnostics from the Host Connectivity Manager.

2. Run any diagnostic test.

3. Select and double-click a row of the test results in the bottom pane.



• “Running a hardware-level test using HCM”

• “Running a Fibre Channel protocol-level test using HCM”

Field Description

Time The date and time the test was run.

Test The name of the test.

Status The status of the test, for example, executing or pending.

Configuration The name of the test component and its corresponding value. For example:• Adapter world wide name• Data pattern• Frame count• Port world wide name

Result The test result, for example, test started or test complete.


Update Driver dialog box A

Update Driver dialog box The Update Driver dialog box allows you to update the driver installed on the connected host to the latest version.

NOTEThe update is supported on HCM version 2.3 and higher; downgrades to older HCM versions are not supported.

Opening the dialog boxRight-click a host from the device tree and select Update Driver from the list.

The Update Driver dialog box displays.



• “Driver update”

Field Description

Select driver file to upgrade text box Enter the filename of the updated driver in the text box.

Browse button Click to navigate to the location of the driver file to upgrade.

Start Installation button After you have entered the upgraded driver file, click to install the new driver.

Installation Progress Details Displays the driver installation progress details.


Virtual Port Creation dialog boxA

Virtual Port Creation dialog box The Virtual Port Creation dialog box enables you to create a new virtual port from a physical port or FCoE port.

Opening the dialog box1. Select a physical port from the device tree.

2. Select Configure > Virtual Port > Create from the main menu.

OR

Right-click the physical port and select Virtual Port > Create from the list.



• “Virtual port configuration”

• “Creating a virtual port”

• “Deleting a virtual port”

Field Description

Physical Port WWN Displays the world wide name for the physical port.

Virtual Port WWN text box Enter a unique world wide name for the virtual port.The default node WWN is the physical port node WWN. You must manually change it to a unique WWN for the virtual port.

Use auto-generated check box Click to auto-generate the virtual port world wide name. By default, auto-generate is selected.

Generate Again button Click to regenerate the virtual port WWN and the virtual node WWN.

Virtual Node WWN text box Enter a unique world wide name for the virtual node.The default node WWN is the physical port node WWN. You must manually change it to a unique WWN for the virtual port.

Symbolic Name text box Enter the symbolic name associated with the virtual port.

Name text box Enter the name for the virtual port.

Description text box Enter a description for the virtual port.


Virtual Port Deletion dialog box A

Virtual Port Deletion dialog box The Virtual Port Deletion dialog box enables you to delete an existing virtual port or FCoE port.

Opening the dialog box1. Select a virtual port from the device tree.

2. Select Configure > Virtual Port > Delete from the main menu.

OR

Right-click the virtual port and select Virtual Port > Delete from the list.

A warning message displays, asking for confirmation.

3. Click OK to continue.

NOTEYou cannot delete the base port.






Field Description

Deletion check box Check to select the virtual port to be deleted.

WWN The virtual port’s world wide name.

Node WWN The virtual node’s world wide name.

Symbolic Name The symbolic name that is associated with the virtual port.

Delete Selected button Click to delete the selected virtual port.

Delete All button Click to delete all virtual ports that are displayed.

Cancel button Click to abort the operation.


Virtual Port Properties panelA

Virtual Port Properties panel The Virtual Port Properties panel enables you to display the properties that are associated with a virtual port or FCoE port.

Opening the panelSelect a virtual port from the device tree and click the Properties tab.






Field Description

Base Port Indicates whether the virtual port is used as the base port.

Fabric Name The name of the Fabric associated with the base port.


FC Address The Fibre Channel address of the virtual port.



Preboot Created Indicates whether preboot was created on the virtual port (True or False).

Roles The role of the virtual port; for example, FCP Initiator.

State Indicates whether the virtual port is online or offline.

Symbolic name The switch’s symbolic name.

Switch IP address The switch’s IP address.


Virtual Port Statistics dialog box A

Virtual Port Statistics dialog box The Virtual Port Statistics dialog box enables you to view statistical information related to a selected virtual port or FCoE port.

Opening the dialog box1. Select a virtual port from the device tree.

2. Select Monitor > Statistics > Virtual Port Statistics from the Host Connectivity Manager.


Field Description






FDISCs Sent The number of Fabric discoveries sent.

FDISCs Accepts The number of times the system accepts Fabric discoveries.

FDISC Retries The number of times a Fabric discovery is attempted.

FDISC Req Timeouts The time that is required for a Fabric discovery.

FDISC RSP Errors The number of Fabric discovery response errors.

FDISC Bad Accepts The number of bad accepts.

FDISC Rejects The number of times the system rejects Fabric discoveries.

FDISC Unknown Rsps The number of unknown Fabric discovery occurrences.

FDISC Alloc Waits The number of delayed Fabric discovery allocations.

LOGOs Sent The number of times logouts occur.

LOGO Accepts The number of times logouts are accepted.

LOGO Rejects The number of times logouts are rejected.

LOGO Rsp Errors The number of logout response errors.

LOGO Unknown RSPs The number of unknown logout occurrences.

LOGO Alloc Waits The number of delayed logout allocations.

No NPIV Support Indicates if there is no NPIV support.

Fabric Offlines The number of fabrics that are offline.

Fabric Onlines The number of fabrics that are online.

Fabric Cleanups The number of fabric cleanups.


Virtual Port Statistics dialog boxA







VLAN Configuration dialog box (CNA only) A

VLAN Configuration dialog box (CNA only)The VLAN Configuration dialog box enables you to create a logical work group consisting of up to 64 VLANs. You can also add, edit, or remove VLANs using the VLAN Configuration dialog box.



OR

Right-click the host and select VLAN Configuration from the list.

The VLAN Configuration dialog displays.



• “VLAN configuration”


• “VLAN configuration conflicts”



Field Description

VLAN ID Displays a list of configured VLAN identifiers.

VLAN Name Displays a list of configured VLAN names.

Add button Click to launch the Add VLAN dialog box, which enables you to add a VLAN.

Edit button Click to launch the Edit VLAN dialog box, which enables you to edit the VLAN name.

Remove button Click to remove a VLAN. A confirmation error message displays.


VLAN configuration - Add VLAN dialog box (CNA only)A

VLAN configuration - Add VLAN dialog box (CNA only)The Add VLAN dialog box allows you to create a VLAN. You can create a VLAN by selecting an Ethernet port.



OR









Field Description

Port MAC The media access control address of the Ethernet port.

VLAN ID text box The VLAN identifier.

VLAN Name text box The VLAN name.

Create Passthru checkbox Check to create a pass-through VLAN.


VLAN configuration - Edit VLAN dialog box (CNA only) A

VLAN configuration - Edit VLAN dialog box (CNA only)The Edit VLAN dialog box allows you to edit an existing VLAN.



OR


3. Click Edit on the VLAN Configuration dialog box.








Field Description

Port MAC The media access control address of the Ethernet port.

VLAN ID text box The VLAN identifier.

VLAN Name text box The VLAN name.


VLAN Statistics dialog box (CNA only)A

VLAN Statistics dialog box (CNA only)The VLAN Statistics dialog box enables you to display statistics related to a selected virtual LAN.

NOTEIf a PORT VLAN exists in the VLAN configuration, you cannot perform any add, delete, or edit operations on any VLAN. In addition, you cannot view statistical information on any VLAN.

Opening the dialog boxVLAN Statistics for a team can only be opened if the VLANs are added to a team from the Teaming Configuration dialog box, shown in Figure 18.


2. Click Statistics on the Teaming Configuration dialog box.

The VLAN Statistics dialog box displays.







Field Description



Start polling button Click to manually poll the VLAN statistics.

Date The date the VLAN statistics were run.

VLAN ID The VLAN identifier.

VLAN Name The VLAN name.

Tx Packets The number of transmitted packets.

Rx Packets The number of received packets.

Tx Error Packets The number of transmitted error packets.

Rx Error Packets The number of received error packets.

Duration The length of time between byte transmission and reception.

Status The connection status.


VLAN Statistics dialog box (CNA only) A



VLAN Statistics dialog box (CNA only)A



Appendix

B
Brocade Command Utility
In this appendix•About the BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

•BCU commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

•adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

•auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

•bios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

•boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

•cee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

•debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

•diag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

•drvconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

•ethboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

•ethdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

•ethioc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

•ethlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

•ethport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

•fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

•fcdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

•fcoe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

•fcpim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

•ioc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

•log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

•lport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

•pbind. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

•port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

•qos (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

•ratelim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

•rport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

•team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

•trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

•vport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

183

About the BCUB

About the BCUThis appendix provides reference documentation for the Brocade Command Line Utility (BCU) supporting the Brocade Fibre Channel components.

You must explictly open the command shortcut to the BCU in order to run the BCU and bfa_supportsave.bat commands. The command prompt shortcut (the Brocade “B” logo icon) to the desktop is automatically installed when the software is installed.

CAUTION

On Windows operating systems, if you are upgrading the Brocade driver from an earlier version, it is strongly recommended that you use the BCU shortcut that is automatically placed on the desktop during installation. Opening the BCU using the Start > Run command can result in inconsistent information displayed in the BCU.

To list all the commands and subcommands, type the following command:

bcu --help

To check the CLI and Driver version number, type the following command:

bcu --version

BCU commandsThe following table lists the Brocade Command Line Utility (BCU) commands alphabetically that are available for configuring the devices in a SAN environment that use a Brocade adapter.

Command Operands Synopsis

bcu --help Lists all available sub-commands.

bcu <sub_command> --help Lists all details about the specific subcommand.

Adapter commands

bcu adapter --list

--name <ad_id > <adapter-name>

--query <ad_id>

--enable <ad_id>

--disable <ad_id>

Authentication commands

bcu auth --show <port_id>

--policy <port_id> <on | off>

--algo <port_id> <md5 | sha1 | ms | sm>

--secret <port_id> <secret_string>

--stats <port_id>

--statsclr <port_id>


BCU commands B

BIOS commands

bcu bios --query <port_id>

--enable <port_id> [-s speed] [-o auto|flash|firstlun] [-p pos] {-b pwwn,lun}*

--disable <port_id>

Boot commands

bcu boot --blunZone -c <cfg> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#>

--update [adapter_id] <image_file> [-a]

Converged Enhanced Ethernet (CEE) commands

bcu cee --query <port_id>

--stats <port_id>


Debug commands

bcu debug --portlog <port_id>

--portlogclear <port_id>

--portlogctl <port_id> <enable | disable>

Diagnostic commands

Note: The sfpshow and beacon diagnostic tests are not available on the Brocade 804 mezzanine card or the Brocade 1007 CNA expansion card.

bcu diag --sfpshow <port_id>

--tempshow <ad_id>

--beacon <port_id> <on | off> [<duration>]

--pciloopback <port_id> -p <pattern> [-c <frame_count>]

--loopback <port_id> [-t <loopback_type>] [-s <speed>][-c <frame_count>] [-p <pattern>]

--memtest <ad_id>

--queuetest <port_id> [-q <queue num>]

Driver configuration commands

Note: Driver configuration commands are supported only on Windows operating systems.

bcu drvconf --key <key_name>

--val <value>

Possible key_name and value ranges are:

• key = bfa_ioc_queue_depth, value range [0-2048] default = 2048• key = bfa_lun_queue_depth, value range [0- 32] default = 32• key = ioc_auto_recover, value range [0-1] default = 1• key = rport_del_timeout, value range [0-90] default = 90• key = msix_disable, value range [0-1] default = 1• key = pbind_enable, value range [0-1] default = 0• key = fdmi_enable, value range [0-1] default = 0• key = bfa_max_xfer_len [--val

<64|128|256|512|1024|2048|4096|8192|16384>] default = 2048


BCU commandsB

Ethernet Boot commands

bcu ethboot --enable <port_id>

--disable <port_id>

--vlan <port_id> <vlan_id>

--query <port_id>

Ethernet diagnostic commands

bcu ethdiag --loopback <port_id> [-t <loopback-type>] [-c <frame_count>] [-p pattern]

Ethernet I/O Controller (IOC) commands

bcu ethioc --stats <port_id>


--enable <port_id>

--disable <port_id>

--query <port_id>

Ethernet Log command

bcu ethlog --level <port_id> [Critical|Error|Warning|Info>]

Ethernet Port commands

All ethport commands are available on Windows systems; ethport --stats and ethport --statsclr are also available on Linux systems.

bcu ethport --stats <port_id>


--vlanadd <port_id> <vlan_id> [<vlan_name>]

--vlanremove <port_id> <vlan_id>

--vlanedit <port_id> <vlan_id> <vlan_name>

--vlanlist <port_id>

--vlanquery <port_id> <vlan_id>

FC diagnostic commands

bcu fcdiag --fcping <port_id> <rpwwn> [-l lpwwn]

--fctraceroute <port_id> <rpwwn> [-l lpwwn]

--fcecho <port_id> <rpwwn> [-l lpwwn]

--linkbeacon <port_id> {on|off}

--scsitest <port_id> <rpwwn> [-l lpwwn]

FCoE VLAN commands

bcu fcoe --enable <port_id>

--disable <port_id>

--stats <port_id>


--vlanlist <port_id>

--vlanadd <port_id> <vlan_tag>


BCU commands B

--vlandel <port_id> <vlan_tag>

--query <port_id> <vlan_tag>

FCP initiator mode commands

bcu fcpim --query <port_id> <rpwwn> [-l <lpwwn>]

--stats <port_id> <rpwwn> [-l <lpwwn>]

--statsclr <port_id> <rpwwn> [-l <lpwwn>

--pathtov <port_id> <tov>

--modstats <port_id>

--modstatsclr <port_id>

--profile_on <port_id>

--profile_off <port_id>

--ioperf <port_range> [-l | r] [-c count] [-i interval] <port_id> [-l [pwwn]] [-r [pwwn]] [-c count] [-i interval]

I/O Controller (IOC) commands (Storage)

bcu ioc --stats <port_id>


--enable <port_id>

--disable <port_id>

--fwstats <ioc_id>

--fwstatsclr <ioc_id>

--intr <port_id> <-coalesce | c> {on | off} [<-l <usecs>] [-d <usecs>]

--query <port_id>

Log commands

bcu log --level <port_id> [<Critical|Error|Warning|Info>] [-m <fw|hal|fcs|drv|aen|all>]

Logical port (lport) commands

bcu lport --list <port_id>

--query <port_id> [-l <lpwwn>]

--stats <port_id> [-l <lpwwn>]

--statsclr <port_id> [-l <lpwwn>]

Phy command

bcu phy --update <ad_id | -a> <binary file>

Port commands (physical port)

bcu port --list

--name <port_id> [port_name]

--enable <port_id>

--disable <port_id>

--stats <port_id>


BCU commandsB


--query <port_id>

--topology <port_id> [p2p]

--speed <port_id> <speed>

--dfsize <port_id> [dfsize]

--trunk <port_id> [<off|on <port_list>>

--perf <port_range|all> [-c count] [-i interval]

Target persistent binding commands

Note: Target persistent binding is available in Windows operating systems only.

bcu pbind --list <port_id>

QoS commands

Note: QoS commands apply to the 8 Gbps HBA only.

bcu qos --enable <port_id>

--disable <port_id>

--query <port_id>

--stats <port_id>


Target rate limiting commands

bcu ratelim --enable <port_id> [-s <default-speed>]

--disable <port_id>

--query <port_id>

--stats <port_id>


Remote port (rport) commands

bcu rport --list <port_id> [-l <lpwwn>]

--query <port_id> rpwwn [-l <lpwwn>]

--stats <port_id> rpwwn [-l <lpwwn>]

--statsclr <port_id> rpwwn [-l <lpwwn>]

--osname <port_id> [-l <lpwwn>]

Teaming (Windows only) commands

bcu team --list

--query <team-name>

--create <team-name> <team_mode> <port-id1> [<port_idn>]

--remove <team_name>

--addport <team-name> <port-id1> [..<port_idn>]

--remport <team-name> <port-id1> [..<port_idn>]

--name <team_name> <new_team_name>

--primary <team_name> <port_id>


BCU commands B

--xmit_policy <team_name> {l2|l3|l4}

--vlanadd <team_name> <vlan_id> [<vlan_name>]

--vlanremove <team_name> <vlan_id>

--vlanedit <team_name> <vlan_id> <vlan_name>

--vlanlist <team_name>

--vlanquery <team_name> <vlan_id>

Trunk commands

bcu trunk --enable <ad_id>

--disable <ad_id>

--query <ad_id>

Virtual port (vport) commands

Note: vport commands are not supported on Solaris platforms.

bcu vport --create <port_id> vpwwn [-n <vnwwn>] [-s <sname>]

--delete <port_id> vpwwn

--query <port_id> vpwwn

--stats <port_id> vpwwn

--statsclr <port_id> vpwwn

Windows event log printing (Windows only)

bcu winlog


adapterB

adapter Displays and sets adapter parameters. The adapters are HBA models 815, 825, 415, and 425 and CNA single-port models 1010 and 1020. The adapter ID can be specified as adapter-index, adapter serial number, or adapter name.

NOTEWhen trunking is enabled, multiple physical ports are trunked together to form a logical Fibre Channel port.

Synopsis bcu adapter --enable <ad_id>

bcu adapter --disable <ad_id>

bcu adapter --list

bcu adapter --name <serial-no | adapter index> <adapter_name>

bcu adapter --query <ad_id>

Description Displays and sets commands that apply to the physical adapter. There can be one or more PCI functions per adapter, which are referred to as ports. Each port exposes a logical Fibre Channel port, which typically equates to a physical Fibre Channel port.

Operands When invoked without operands, this command displays the usage.

--enable Enables the adapter.

ad_id Specifies the ID of the adapter you want to enable.

--disable Disables the adapter.

ad_id Specifies the ID of the adapter you want to disable.

--list Lists all adapters in the system. For each adapter in the system, a brief summary line is displayed.

--name Displays or specifies the name of the adapter. The adapter name can be identified either by serial number or by adapter index.

Note: Use an empty string (“ “) to clear a previous adapter name. Adapter names are stored persistently.

serial-no | adapter index

Specifies the serial number or the ID of the adapter for which you want to display information.

adapter-name Specifies the adapter name. The name can include up to 15 characters, must begin with a letter, can consist of letters, digits, hyphens, and underscore characters, but must not contain spaces. This operand is optional; if you do not specify an adapter name, the current adapter name displays.

--query Queries or displays adapter information.

ad_id Specifies the ID of the adapter for which you want to query.


adapter B

Example bcu adapter --list

bcu adapter --query 1Example:# bcu adapter --query 1Adapter Information:

card type - FCmodel info: 825OEM info: N/Anum ports: 2max speed: 8 Gbpschip revision: Rev-Bhw path: 16:00Serial Num: ALX0301D062name:

PCI Information: vendor id: 0x1657 device id: 0x0013 ssid: 0x0014 ssvid: 0x1657

PCIe Gen: Gen 1 PCIe lanes: 8 (Initial number of lanes = 8)

Port Information: Port 0:

port type: FC/FCoE pwwn: 10:00:00:05:1e:53:0e:ca nwwn: 20:00:00:05:1e:53:0e:ca IOC ID: 0 hwpath: 16:00:00 name:

Port 1: port type: FC/FCoE pwwn: 10:00:00:05:1e:53:0e:cb nwwn: 20:00:00:05:1e:53:0e:cb IOC ID: 1 hwpath: 16:00:01 name:

Flash Information: status: good fw version: FCHBA2.2.0.0 bios version: brocade_adapter_boot_fw_v2-2-0-0

AD # NP HW-path Type Model-Info Serial-num Name

1 2 0000:01:00 FC 825 ALX0301D062 - -

2 2 0000:09:00 FC 825 ALX0411D01K - -

3 2 0000:1c:00 CNA 1020 ARZ0351D00B - -

4 2 0000:0a:00 CNA 1020 ARZ0351D003 --


adapterB

bcu adapter --query 3Adapter Information: model info: 1020

card type: CNA OEM info: N/A

num ports: 2 max speed: 10 Gbps chip revision: Rev-B hw path: 0000:1c:00 Serial Num: ARZ0351D00B name:PCI Information: vendor id: 0x1657 device id: 0x0014 ssid: 0x0014 ssvid: 0x1657

PCIe Gen: Gen1 PCIe lanes: 4 (Initial number of lanes = 4)Port Information: Port 0:

port type: FC/FCoE pwwn: 10:00:00:05:1e:55:1d:3c nwwn: 20:00:00:05:1e:55:1d:3c IOC ID: 0 hwpath: 0000:1c:00.0 name:

port type: Ethernet mac: 00:05:1e:55:1d:3e IOC ID: 2 hwpath: 0000:1c:00:2 name:

Port 1: port type: FC/FCoE pwwn: 10:00:00:05:1e:55:1d:3d nwwn: 20:00:00:05:1e:55:1d:3d IOC ID: 1 hwpath: 0000:1c:00.1 name:

port type: Ethernet mac: 00:05:1e:55:1d:3f IOC ID: 3 hwpath: 0000:1c:00:3 name:

Flash Information: status: good fw version: FCHBA2.0 bios version: FCHBA2.0


adapter B

bcu adapter --name 1 emc-fab3_ad5 adapter BRCD1234567’s name set to emc_fab3_ad5

bcu adapter --name 1 adapter BRCD1234567’s name is emc_fab3_ad5

See Also “ioc”, “port”


authB

auth Enables authentication configuration on a per-port basis and the ability to display authentication status and statistics. The port ID can be any one of the following:

• Port ID

• Adapter ID

• Port world wide name

• Port Name

• Port hardware path

Synopsis bcu auth --algo <port_id> <md|sha1|ms|sm>

bcu auth --policy <port_id> <on|off>

bcu auth --secret <port_id> <secret_string>

bcu auth --show <port_id>

bcu auth --stats <port_id>

bcu auth --statsclr <port_id>

Description Configure and display authentication settings and status.

Operands --algo Sets the authentication algorithm.

port_id Specifies the ID of the port for which you want to display information.

md|sha1|ms|sm

• MD5 - A hashing algorithm that verifies a message’s integrity using Message Digest version 5. MD5 produces a 128-bit digest and is the required authentication mechanism for LDAP v3 servers.

• SHA1 - A secure hashing algorithm that computes a 160-bit message digest for a data file that is provided as input.

• MD5SH1 - Similar to the MD5 hashing algorithm, but used for DH-CHAP authentication

• SHA1MD5 - Similar to the SHA1 hashing algorithm, but used for DH-CHAP authentication

--policy Turns authentication on or off. By default, the authentication policy is disabled. If authentication is enabled, the port attempts to negotiate with the switch. If the switch side does not participate in the authentication process, the port skips the authentication process. If the switch participates in the authentication and authentication fails, the port is placed in a link down state.

port_id Specifies the ID of the port for which you want to set the authentication policy.

on|off Specifies the state of the authentication policy: “policy 2/1 on” means authentication is turned on, “policy 2/1 off” means authentication is turned off.


auth B

--secret Sets the shared secret.

Note: You cannot clear the secret.

port_id Specifies the ID of the port for which you want to set the shared secret.

secret_string Specifies the secret string. The secret string must be 8 to 40 alphanumeric characters. The default secret for each interface is its pwwn without the colons; for example, 0102030405060708.

--show Displays the authentication settings and current status.


--stats Displays the authentication statistics.


--statsclr Clears the authentication statistics.

port_id Specifies the ID of the port for which you want to clear statistical information.

Example Here is an example of the output when authentication is successful:

bcu auth --show 1/0

Here is an example of the output when authentication failed:

bcu auth --show 1/0

Here is an example of the output when authentication is not enabled:

bcu auth --show 1/0

bcu auth --policy 2/1 onAuthentication turned on

bcu auth --policy 2/1 offAuthentication turned off

bcu auth --secret 5/0 “mypasswd”Authentication secret set

bcu auth --stats 4/1successes: 1failures: 0

port Port Status Auth Hash Type Group Type

1/0 Linkdown success MD5 DH-NULL


1/0 Linkdown failed MD5 DH-NULL


1/0 Linkup no_auth


authB

auth_rx_stats:auth_rjts: 0auth_negs: 0auth_dones: 0dhchap_challenges: 2dhchap_replies: 0dhchap_successes: 1

auth_tx_stats:auth_rjts: 0auth_negs: 2auth_dones: 0dhchap_challenges: 0dhchap_replies: 2dhchap_successes: 0

auth --statsclr 4/1Successfully cleared auth stats

See Also None


bios B

biosEnables the basic input/output system (BIOS) in preparation for Boot Over SAN. The BIOS is the firmware code that, when first powered on, is a type of boot loader.

NOTERefer to the Brocade Adapters Installation and Reference Manual for more information about configuring BIOS.

Synopsis bcu bios --query <port_id>

bcu bios --enable <port_id> [-s speed] [-o auto|flash|firstlun] [-p pos] {-b pwwn,lun}*

bcu bios --disable <port_id>

Description You must enable BIOS to support boot over SAN for a port. If disabled, the host system cannot boot from Fibre Channel disk drives. BIOS must be enabled on only one adapter port per host in order to boot from SAN. The default setting for the boot BIOS is enabled.

The port ID can be any of the following:

• Adapter ID

• Port ID

• Port WWN

• Port name


Operands --query Queries the boot-over-SAN configuration.


--enable Enables the boot over SAN configuration.

port_id Specifies the ID of the port for which you want to set the port’s boot from SAN attributes.

s speed Specifies the port speed as auto-negotiate.

o auto|flash|firstlun

Specifies the following options for obtaining boot LUN information. This list displays only if BIOS is enabled and Fabric Discovery is disabled.

• auto—Enables fabric discovery. When enabled, the boot LUN identification is provided by the fabric.

• flash—The adapter obtains the boot LUN information from flash memory. Values are saved to flash when you configure them and save them through the BIOS Configuration Utility, HCM, and BCU.

• firstlun—The host boots from the first LUN visible to the adapter that is discovered in the fabric.

p pos Specifies the position for storing the boot LUN information in the -b pwwn, lun operand. The range is 0-3. The LUN information specified in position 0 is used first to boot from SAN, then information specified for positions 1, 2, and 3.


biosB

b pwwn,lun Specifies the host boots from the LUN information defined by the target port world wide name (PWWN) and LUN value (lun*). Specify the PWWN as a colon-separated value and the LUN as a 64-bit decimal value.

The LUN must be the same LUN that you bound to the port using the storage system’s management or configuration utility.

--disable Disables boot over SAN for the specified port, if enabled.

port_id Specifies the ID of the port for which you want to disable the boot over SAN configuration.

Example # bcu bios --query 1/0boot over SAN: enabledport speed: AutoBoot luns discovered from the fabricboot lun 0: target wwn: 10:20:30:40:50:60:70:80 lun: 1000-a5d4-e800-0000boot lun 1: target wwn: 10:20:30:40:50:60:70:80 lun: 0400-0000-0000-0000boot lun 2: target wwn: 10:20:30:40:50:60:70:82 lun: 012c-0000-0000-0000boot lun 3: target wwn: 00:00:00:00:00:00:00:01 lun: 8cd9-3907-0000-0000

Pre-boot Configuration:Speed: 2/4/8/Auto for 8G cardsBIOS: Enabled/DisabledNumber of boot luns: 8Boot LUN 0 : <Target’s WWN>, <LUN>Boot LUN 1 : <Target’s WWN>, <LUN>Boot LUN 2 : <Target’s WWN>, <LUN>Boot LUN 3 : <Target’s WWN>, <LUN>Boot LUN 4 : <Target’s WWN>, <LUN>Boot LUN 5 : <Target’s WWN>, <LUN>Boot LUN 6 : <Target’s WWN>, <LUN>Boot LUN 7 : <Target’s WWN>, <LUN>

# bcu bios --enable 1/0 -b 11:22:33:44:55:66:77:88,0boot cfg updated.

bcu bios --enable 1/0 -s 1 -o auto -b 11:22:33:44:55:66:77:88,0boot cfg updated.

bcu bios --disable 1/0boot over san disabled

See Also “boot”


boot B

bootAllows the host’s boot LUN information to be stored in the fabric zone database using a zone name containing the PWWN of an adapter port and zone members consisting of the storage target PWWN and LUN WWN. The adapter boot code can query the zone member list for the zone name that matches the adapter PWWN to determine the boot target and LUN.

NOTEA system reboot is required for the newly-updated image to be effective.

Refer to the Brocade Adapters Installation and Reference Manual for information about creating zones on the switch where the adapter is connected.

NOTEOn Solaris systems, the Update Boot Image menu is disabled if the host does not have a Fibre Channel HBA card or if the driver version is 1.1.0.7 or lower.

Synopsis bcu boot --blunZone -c <cfg> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#>

bcu boot --update [adapter_id] <image_file> [-a]

Description Boot commands allows the host’s boot LUN information to be stored in the fabric zone database using a zone name and to update the boot code in flash.

Operands --blunZone Generates the zonecreate command to be run on the switch.

-c cfg Specifies the boot LUN (BLUN) of the boot command.

-p port_wwn Specifies the world wide name of the port.

-r rport_wwn Specifies the world wide name of the remote port (rport).

-l lun_id Specifies the ID of the logical unit. The LUN ID is specified as a hexadecimal byte; for example, FF.

-l lun# Specifies the number of the logical unit. The LUN number is specified as a hexadecimal, eight-byte string; for example, 09AABBCCDDEEFF00.

--update Updates the boot code in flash.

adapter_id Specifies the ID of the adapter on which boot code is updated. The adapter id could be any one of the following: adapter serial number, adapter name, or adapter hardware path.

image_file Specifies the name of the boot code image file.

-a Indicates the boot code is updated to all the Brocade adapters found on the host. The adapter_id is not specified if -a is specified.


bootB

Example bcu boot --update 1 brocade_adapter_boot_fw_v2-2-0-0Boot code updated successfullyA reboot of the system is needed for the newly updated image to be effective.

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

To create the zone, copy the following line and run this command from the switch command line.

zonecreate “BFA_100000051E419ACB_BLUN”,”00:00:00:00:50:00:00:05; 00:00:00:01:1e:41:9a:ca; 00:00:00:02:09:aa:bb:cc, 00:00:00:03:dd:ee:ff:00”

See Also “bios”


cee B

ceeDisplays Converged Enhanced Ethernet (CEE) information on the port. The port_id could be any of the following:

• Adapter ID or port ID

• Port name


NOTEAll switches must be in non-willing mode.

Synopsis bcu cee --query <port_id>

bcu cee --stats <port_id>

bcu cee --statsclr <port_id>

Operands --query Queries the CEE port information.

port_id Specifies the ID of the adapter (CNA).

--stats Displays the CEE port statistics.

port_id Specifies the ID of the converged network adapter for which you will print the statistics.

--statsclr Clears the CEE port statistics.


bcu cee --query 1/0CEE status: Active----------------------------------------Remote LLDP-Attributes----------------------------------------Time to Live 120Chassis ID 00:05:1e:54:18:cePort ID Te 0/4Port Desc --System Name --System Desc --System Cap BRIDGE---------------------------------------- Operational CEE Map:--------------------- Priority Group Table <PGID: Weight %, PFC status for the group> 0: Weight 0, PFC Disabled 1: Weight 80, PFC Enabled 2: Weight 20, PFC Disabled 3: Weight 0, PFC Disabled 4: Weight 0, PFC Disabled 5: Weight 0, PFC Disabled 6: Weight 0, PFC Disabled 7: Weight 0, PFC Disabled


ceeB

Priority TableCoS: 0 1 2 3 4 5 6 7----------------------------------------------PGID: 2 2 1 2 2 2 2 2

FCoE Priority Table 2

FCoE Logical Link Status: UpNetwork Priority: 0DCBCXP version: CEE2

bcu cee --stats 1/0CEE Statistics:LLDP Tx Frames : 560LLDP Rx Frames : 563LLDP Rx Frames invalid : 0LLDP Rx Frames new : 6LLDP Rx unrecognized TLVs : 6LLDP Rx shutdown TLVs : 0LLDP remote info aged out : 0DCBX phy link ups : 2DCBX phy link downs : 1DCBX Rx TLVs : 4DCBX Rx TLVs invalid : 0DCBX control TLV errors : 0DCBX feature TLV errors : 0DCBX new CEE cfg rcvd : 2CEE status down : 1CEE status up : 2CEE hw cfg changed : 2CEE invalid cfg : 2

bcu cee --statsclr 1/0Successfully reset the port cee statistics

See Also None


debug B

debug The debug commands gather support information on Fibre Channel components. The port ID can be any one of the following:

• Port ID

• Adapter ID


• Port Name


Synopsis bcu debug --portlog <port_id>

bcu debug --portlogclear <port_id>

bcu debug --portlogctl <port_id> <enable | disable>

Description Captures all the support information needed to diagnose suspected system issues.

Operands --portlog Displays the log of FC frames and other main control messages that were sent out and received.

If the port log is disabled, the following message displays as the first line: Refer to the portlogctl command for more information: WARNING: port log is disabled.

port_id Specifies the ID of the port for which you want to display the FC frame logs and other control messages.

--portlogclear Clears the port’s frame log.

port_id Specifies the ID of the port for which you want to clear the port’s frame log.

--portlogctl Enables or disables the portlog.

port_id Specifies the ID of the port for which you want to enable or disable the portlog.

enable Enables the portlogclear command.

disable Disables the portlogclear command.

Examplebcu debug --portlog 10/0Total records present = 14---------------------------------------------------------------------------time event port code args---------------------------------------------------------------------------08:35:28.430 fwm 10/0 00 00001234, 0005000108:35:28.431 mbox 10/0 01 00001234, 0005000108:35:28.433 ioctl 10/0 90 101d9910,008:35:28.433 Tx 10/0 164 02fffffd, 00fffffd, 0005ffff, 1000000008:35:28.433 Rx 10/0 0 c0fffffd, 00fffffd, 0005000608:35:28.433 Rx 10/0 164 03fffffd, 00fffffd, 00050006, 0200000008:35:28.433 Tx 10/0 0 c0fffffd, 00ffffd, 0005000608:35:28.433 ioctl 10/0 91 103646d8, 008:35:28.466 ioctl 10/0 a7 3c, 108:35:28.483 Tx 10/0 96 02fffffd, 00fffffd, 0006ffff, 11100060


debugB

08:35:28.483 Rx 10/0 0 c0fffffd, 00fffffd, 0006000708:35:28.483 Rx 10/0 96 03fffffd, 00fffffd, 00060007, 0210006008:35:28.483 Tx 10/0 0 c0fffffd, 00fffffd, 0006000708:35:28.483 ioctl 10/0 a1 0,0---------------------------------------------------------------------------

# bcu debug --portlog 1/1Total records present = 26---------------------------------------------------------------------------Time Module Event Len Log info---------------------------------------------------------------------------13fe083a Driver drvstrt 0 Driver Attach14471130 HAL pstchg 0 Port Linkup1447135f FCXP Tx 140 01290000,00000000,00080000,0300000014471361 FCXP Tx 32 01290000,00000000,00080000,6200000014471498 FCXP Rx 116 01980000,6c000000,051e7609,020000001447149c FCXP Tx 301 20290000,00000000,00080000,010000001447150d FCXP Rx 4 01980000,6d000000,051e7609,020000001447190e FCXP Rx 16 20980000,6e000000,051e7609,0100000014471910 FCXP Tx 76 20290000,00000000,00080000,0100000014471a29 FCXP Rx 16 20980000,6f000000,051e7609,0100000014471a2b FCXP Tx 48 20290000,00000000,00080000,0100000014471b28 FCXP Rx 16 20980000,70000000,051e7609,0100000014471b2a FCXP Tx 44 20290000,00000000,00080000,0100000014471b2d FCXP Tx 140 01290000,00000000,00080000,0300000014471c11 FCXP Rx 116 01980000,71000000,051e7609,0200000014471c18 FCXP Tx 176 20290000,00000000,00080000,0100000014471c19 FCXP Tx 48 20290000,00000000,00080000,0100000014471d1a FCXP Rx 16 20980000,72000000,051e7609,0100000014471e0e FCXP Rx 16 20980000,73000000,051e7609,0100000014472027 FCXP Rx 788 20980000,74000000,051e7609,0100000014472029 FCXP Tx 48 20290000,00000000,00080000,0100000014472144 FCXP Rx 24 20980000,75000000,051e7609,0100000014613597 FCXP Tx 176 20290000,00000000,00080000,0100000014613745 FCXP Rx 16 20980000,76000000,051e7609,01000000147fb9b6 FCXP Tx 176 20290000,00000000,00080000,01000000147fbb68 FCXP Rx 16 20980000,77000000,051e7609,01000000---------------------------------------------------------------------------

bcu debug --portlogclear 1/0portlog cleared

bcu debug --portlogctl 1/0 enableportlog enabled

bcu debug --portlogctl 1/0 disableportlog disabled

bcu debug --portlogctl 1/0 disableportlog disabled

See Also None


diag B

diag Lists the non-destructive group of diagnostic commands. The port can be identified using the adapter index, the port index, the port name, or the port world wide name.

Before you run the loopback test, disable the physical port using the bcu port --disable <port_id> command. Before you run the memtest, disable the adapter using the bcu adapter --disable <ad_id> command.

The port ID can be any one of the following:

• Port ID

• Adapter ID


• Port Name


NOTEThe sfpshow and beacon diag commands are not supported on the Brocade 804 mezzanine card or the Brocade 1007 expansion card.

Synopsis bcu diag --sfpshow <port_id>

bcu diag --tempshow <ad_id>

bcu diag --beacon <port_id> <on | off> [<duration>]

bcu diag --pciloopback <port_id> -p <pattern> [-c <frame_count>]

bcu diag --loopback <port_id> [-t <loopback_type>] [-s <speed>] [-c <frame_count>]

[-p <pattern>]

bcu diag --memtest <ad_id>

bcu diag --queuetest <port_id> [-q <queue num>]

Description Displays the group of diagnostic commands that are non-destructive and indicates when the adapter is running at a normal operation state.

Operands --sfpshow Displays the SFP information. Note: A notification occurs for any parameter that is not within the configured power, temperature, voltage, and current specification or policy.

port_id Specifies the ID of the port on which you want to display the SFP attributes.

--tempshow Reads the adapter’s temperature sensor registers of the adapter. This is an online diagnostic test.

ad_id Specifies the ID of the adapter for which you want to display temperature sensor registers. Options include the following temperature settings:

• below min

• normal

• above max

• sensor fault


diagB

--beacon Controls the port and link end-to-end beaconing. End-to-end (E2E) beaconing can be enabled on Brocade 8 Gbps HBAs to allow the local HBA to flash (beacon) and also cause the connected Fibre Channel switch port to also uniquely beacon. This is an online diagnostic test.

port_id Specifies the ID of the port for which you want to beacon.

on | off Turns end-to-end beaconing on or off.

duration Displays the beacon time duration in seconds. Beaconing is automatically turned off after the specified duration. If the duration is set to 0, beaconing continues until it is explicitly turned off. The default duration is 0.

--pciloopback Sends a health check message back and forth from the host to the IO Controller (IOC) through the host engine over the PCI.

port_id Specifies the ID of the port for which you want to send a health check message.

-p pattern Displays the data pattern.

-c frame_count Specifies the frame count.

--loopback Tests the data path from the IOC to the desired network loopback point (internal, serdes, external) and back. This is an offline diagnostic test.

port_id Specifies the ID of the port on which you want to run a loopback test.

-t loopback_type Specifies the loopback test type. Possible values include the following test types:

• int - Internal loopback, the default• serdes - SerDes loopback• ext - External loopback).

If the loopback type is not specified, all loopback tests run.

-s speed Specifies the link speed as 10, 8, 4, 2, or 1 Gbps. This is an optional parameter. If not specified, the following speeds are tested:

• 10, 8, 4, and 2 Gbps speeds are tested on the 10 Gbps adapter. The default speed for the 10 Gbps FCoE CNA is 10 Gbps.

• 8, 4, and 2 Gbps speeds are tested on the 8 Gbps adapter. The default speed for the 8 Gbps and 4 Gbps FC HBA is 4 Gbps.

• 4, 2, and 1 Gbps speeds are tested on the 4 Gbps adapter.

-c frame_count Specifies the frame count.

-p pattern Specifies the pattern (must be one hex word).

--memtest Performs a generic memory test using different algorithms.

ad_id Specifies the ID of the adapter on which you want to test the memory blocks.

--queuetest Sends a health check message from the host to firmware through message queues memory mapped over the PCI. This is an online diagnostic test.

port_id Specifies the ID of the port on which you want to run a queuetest.

-q queue num Specifies the queue number from 0 to 3. If the queue number is not specified, all queues are tested.


diag B

Example bcu diag --sfpshow 1/0Identifier: 3 SFPConnector: 7 LCTransceiver: 540c402000000000 200,400,800_MB/s M5,M6,SN,I,Encoding: 1 8B10BBaud Rate: 85 (units 100 megabaud)Length 9u: 0 (units km)Length 9u: 0 (units 100 meters)Length 50u: 5 (units 10 meters)Length 62.5u: 3 (units 10 meters)Length Cu: 0 (units 1 meter)Vendor Name: BROCADEVendor OUI: 00:05:1eVendor PN: 57-1000012-01Vendor Rev: AWavelength: 352 (units nm)Options: 001a Rx_LOS TX_FAULT TX_DISABLEBR Max: 0BR Min: 0Serial No: UAA40808000004ADate Code: 080224Temperature: 37.593750 CentigradeCurrent: 6.348000 mAmpsVoltage: 3.419400 VRX Power: 0.467000 mWTx Power: 0.562000 mWAlarm/Warning: 00000000

See Also “fcdiag”


drvconfB

drvconf Sets the basic parameters for the driver to function properly.

Note: The drvconf commands are supported on Windows platforms only.

Synopsis bcu --drvconf [-key <key_name>] [--val <value>]

Description Changes the values for basic Windows registry entry parameters.

NOTEYou can directly change these values by editing the Windows registry entries for these values, or you can use the drvconf commands for the same purpose.

Operands --key key_name The name of the bfa key.

--val value Sets the value of the bfa key. See below for possible values and default settings.

Possible key name and value ranges are as follows:

• key = bfa_ioc_queue_depth, value range [0-2048] default = 2048

• key = bfa_lun_queue_depth, value range [0- 32] default = 32

• key = ioc_auto_recover, value range [0-1] default = 1

• key = rport_del_timeout, value range [0-90] default = 90

• key = msix_disable, value range [0-1] default = 1

• key = pbind_enable, value range [0-1] default = 0

• key = fdmi_enable, value range [0-1] default = 0

• key = bfa_max_xfer_len [--val <64|128|256|512|1024|2048|4096|8192|16384>] default = 2048

See Also None


ethboot B

ethbootA Preboot Execution Environment (PXE) boot is an alternative to booting from the local disk or the SAN (boot over SAN). Once PXE boot is initiated, the network adapter makes a DHCP request. The response includes the Dynamic Host Configuration Protocol (DHCP) client IP address for the network adapter and also includes the IP address of a Trivial File Transfer Protocol (TFTP) server, along with a filename of a boot file. The boot file is retrieved over the network and then executed. The boot file then loads other files, such as configuration files and executables.

Refer to the Brocade Adapters Installation and Reference Manual for configuration details.

Synopsis bcu ethboot --enable <port_id>

bcu ethboot --disable <port_id>

bcu ethboot --vlan <port_id> <vlan_id>

Description Enables or disables Ethernet Boot on the port or configures the VLAN ID to use for the specified port.

Operands --enable Enables Ethernet Boot (PXE) for the specified port.

port_id Specifies the ID of the port on which you want to enable PXE.

--disable Disables the Ethernet Boot (PXE) for the specified port.

port_id Specifies the ID of the port on which you want to disable PXE.

--vlan Sets the VLAN ID to be used during Ethernet Boot (PXE) for the specified port.

port_id Specifies the ID of the port on which you want to set the VLAN ID. The supported VLAN ID range is 0-4094.

--query Displays the Ethernet Boot (PXE) configuration on the specified port.

port_id Specifies the ID of the port on which you want to display the PXE configuration.

Example bcu ethboot --query 1/0Boot Enable: EnabledVLAN ID: 0

See Also “ethdiag”“ethioc”“ethlog”“ethport”


ethdiagB

ethdiagThe Ethernet Port Loopback Test generates and sends out the desired number of packets and expects to receive the same number of packets through the loopback interface (Serdes or external). Each time a packet is sent it is selected from a different starting point of the data buffer so that any two consecutively transmitted packets will not be the same.

Before you run the ethdiag test, disable the physical port using the bcu port --disable <port_id> command.

Synopsis bcu ethdiag --loopback <port_id> [-t <loopback_type] [-c <count>] [-p pattern]

Description Runs the Ethernet diagnostic loopback test and indicates when the adapter is running at a normal operation state.

Operands --loopback Runs the port loopback test. You must disable the Ethernet port prior to executing the loopback test.

port_id Specifies the ID of the port on which you want to run a loopback test.

-t loopback-type Specifies the loopback type. Possible values are serdes or ext (external). The default is serdes.

-c frame count Specifies the number of loopback frames to be sent during the test. Possible values are 1 to 131072 frames and the default number is 65536.

-p pattern Specifies the pattern (must be one hex word), with no 0x prefix.

Example To run the ethdiag test over adapter 1, port 0 in the external mode, with a count of 1024 frames and a pattern of test1, run the following command:

bcu port --disable 1/0bcu ethdiag --loopback 1/0 -t ext -c 1024 -p test1

See Also “port”


ethioc B

ethiocDisplays or clears Ethernet IOC statistics. The port_id could be any of the following:


• Ethernet port name

• Ethernet port hardware path

Synopsis bcu ethioc --enable <port_id>

bcu ethioc --disable <port_id>

bcu ethioc --query <port_id>

bcu ethioc --stats <port_id>

bcu ethioc --statsclr <port_id>

Description Enables or disables Ethernet IOC on the port and displays and clears Ethernet IOC statistics.

Operands --enable Enables the Ethernet IOC, if it is currently disabled.

port_id Specifies the ID of the Ethernet port you want to enable.

--disable Disables the Ethernet IOC, if it is currently enabled.

port_id Specifies the ID of the Ethernet port you want to disable.

--query Queries the attributes of the Ethernet IOC.

port_id Specifies the ID of the Ethernet port you want to query.

--stats Displays the Ethernet IOC statistics.

port_id Specifies the ID of the Ethernet port for which you will display the statistics.

--statsclr Clears the Ethernet IOC level statistics.

port_id Specifies the ID of the Ethernet port for which you will reset the statistics.

Example bcu ethioc --stats 1/0IOC host statistics:

mailbox interrupts: 40771enable events: 1disable events: 0heartbeat failures: 0firmware boots: 0stats timeouts: 0

bcu ethioc --statsclr 1/0Successfully reset the ioc level stats

See Also None


ethlogB

ethlogSets the log level for each Ethernet driver. The port_id could be any of the following:


• Ethernet port name

• Ethernet port hardware path

Synopsis bcu ethlog --level <port_id> [<Critical|Error|Warning|Info>]

Description The number of messages logged by the host depends on the predetermined logging level. Although the CNA might generate many messages, only certain types of messages are logged based on the specified logging level.

Operands --level Sets the log level of the Ethernet driver.

port_id Specifies the ID of the Ethernet port for which you will set the log level. level

Critical|Error|Warning|Info

Specifies the severity level. Possible values are Critical, Error, Warning, and Info. If no level is set, the default setting is used, which is Warning.

Example bcu ethlog 1/0 --levelLog level is Info

bcu ethlog 1/0 --level WarningLog level set to Warning

See Also None


ethport B

ethportWith port-based VLANs, each physical switch port is configured with a set of VLANs that you can configure using the ethport commands. The supported range for the VLAN ID is 0-4094, where a VLAN ID of 0 is used to identify priority frames; that is, the frame doesn’t belong to any VLAN but instead contains 802.1x priority information.

NOTEAll ethport commands are available on Windows systems; ethport --stats and ethport --statsclr are also available on Linux systems.

Synopsis bcu ethport --vlanadd <port_id> <vlan_id> <vlan_name>

bcu ethport --vlanremove <port_id> <vlan_id>

bcu ethport --vlanedit <port_id> <vlan_id> <new_vlan_name>

bcu ethport --vlanlist <port_id>

bcu ethport --vlanquery <port_id>

bcu ethport --stats <port_id>

bcu ethport --statsclr <port_id>

Description Adds, removes, and edits VLANs on a port, lists configured VLANs on the port, or displays details about the VLAN. In addition, displays or clears statistical information on the Ethernet port.

Operands --vlanadd Configures a new VLAN ID on the port.

port_id Specifies the ID of the port on which you want to add a VLAN.

vlan_id Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094.

vlan_name Specifies the VLAN name.

--vlanremove Removes an existing VLAN ID from the port.

port_id Specifies the ID of the port from which you want to remove a VLAN.


--vlanedit Modifies an existing VLAN on the port.

port_id Specifies the ID of the port on which you want to modify a VLAN.


new_vlan_name Specifies a different name for the VLAN.

--vlanlist Lists the configured VLANs on the port.

port_id Specifies the ID of the port on which you want to list configured VLANs.


--vlanquery Displays the VLAN information on the port.

port_id Specifies the ID of the port for which you want to display the VLAN details.


--stats Displays Ethernet port statistics.


ethportB

port_id Specifies the ID of the Ethernet port for which you want to display statistics.

--statsclr Clears Ethernet port statistics.

port_id Specifies the ID of the Ethernet port for which you want clear statistics.

Example bcu ethport vlanlist 1/0

# bcu ethport --stats 4/0Ethernet port statistics:txf0_ucast_octets:0 txf0_ucast:0 txf0_ucast_vlan:0 txf0_mcast_octets:0 txf0_mcast:0 txf0_mcast_vlan:0 txf0_bcast_octets:0 txf0_bcast:0 txf0_bcast_vlan:0 txf0_errors:0 txf0_filter_vlan:0 txf0_filter_mac_sa:0 rxf0_ucast_octets:0 rxf0_ucast:0 rxf0_ucast_vlan:0 rxf0_mcast_octets:0 rxf0_mcast:0 rxf0_mcast_vlan:0 rxf0_bcast_octets:0 rxf0_bcast:0 rxf0_bcast_vlan:0 rxf0_frame_drops:0 rx completed:0rx dropped:0rx alloc failed:0rx checksum errors:0rx mac errors:0rx small packets:0rx large packets:0rx lro :0rx lro flush:0rx low rxbuf count:0tx lso4 :0tx lso6 :0tx lso errors:0tx tcp cso:0tx udp cso:0tx ip4 cso:0tx checksum help:0tx checksum help errors :0tx map errors:0tx res drops:0tx small packets:0tx large packets:0tx out of wis count:0tx wi waitq count:0tx ctxt waitq count:0


ethport B

tx max nbs per nbl:0link toggles:0cee toggles:0mbox intr disables:0mbox_intr_enables:0tx stops:0tx wakeups:0tx res stops:0tx hardware stop:0rx schedules:0rx hardware stops:0rx resumes:0rx rss config count:0hardware stats updates:0

bcu ethport --statsclr 4/0ethport stats cleared

bcu ethboot --query 1/0Boot Enable: EnabledVLAN ID: 0

bcu ethport --vlanlist 1/0 -------------------------------- Vlan id Vlan Name -------------------------------- 1 VLAN0001 3000 VLAN3000 -------------------------------

bcu ethport --vlanquery 1/0 1 vlan id: 1 vlan name: VLAN0001 vlan statistics: Tx Bytes: 200 Rx Bytes: 100 Duration: 2:30:32 Status: Connected

See Also None


fabricB

fabricPrints and resets Fabric statistics.

Synopsis bcu fabric --stats <port_id>

bcu fabric --statsclr <port_id>

Description Displays or clears Fabric statistics.

Operands --stats Prints the fabric statistics.

port_id Specifies the ID of the fabric port for which you will print the statistics.

--statsclr Resets the fabric statistics.

port_id Specifies the ID of the fabric port for which you will reset the statistics.

Example bcu fabric --stats 1/0Fabric Stats:FLOGI sent: 114FLOGI rsp errors: 0FLOGI accept errors: 0FLOGI accepts: 58FLOGI rejects: 0FLOGI unknown rsp: 0FLOGI alloc wait: 0FLOGI received: 0FLOGI rejected: 0fabric offlines: 57fabric onlines: 58

See Also None


fcdiag B

fcdiagRuns diagnostic tests on Fibre Channel components.

NOTEThe fcdiag --linkbeacon command is not supported on the Brocade 804 HBA.

Synopsis bcu fcdiag --fcping <port_id> <rpwwn> [-l lpwwn]

bcu fcdiag --fctraceroute <port_id> <rpwwn> [-l lpwwn]

bcu fcdiag --fcecho <port_id> <rpwwn> [-l lpwwn]

bcu fcdiag --linkbeacon <port_id> {on|off}

bcu fcdiag --scsitest <port_id> <rpwwn> [-l lpwwn]

Description Fibre Channel diagnostic tests evaluate the integrity of Fibre Channel components.

Operands --fcping Determines the basic connectivity between two Fibre Channel network points and monitors and measures network latency.

port_id Specifies the ID of the port to which you want to issue a ping command.

rpwwn Specifies the remote port world wide name to which you want to issue a ping command.

-l lpwwn Specifies the logical port world wide name. This is an optional argument. The base port is specified as 0; otherwise, the port is a virtual port.

--fctraceroute Reports on a SAN path, including node hops and latency data.

port_id Specifies the ID of the port on which you want to run the fctraceroute command.

rpwwn Specifies the remote port world wide name.


--fcecho Sends an FC Echo Extended Link Services (ELS) request to a remote port.

port_id Specifies the ID of the port from which you want to run the fcecho command.

rpwwn Specifies the remote port world wide name on which you want to run the fcecho diagnostic test.


--linkbeacon Blinks (toggles) the link beacon.

port_id Specifies the ID of the port for which you want to run the linkbeacon command.

on | off Specifies if the linkbeacon test is on or off.


fcdiagB

--scsitest Tests the SCSI components and displays the discovered LUN information.

port_id Specifies the ID of the port for which you want to run the scsitest command.

rpwwn Specifies the remote port world wide name.


Example #bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:ebError: Reject from attached fabric

#bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:ebFC Traceroute completed successfully. Path Info:

#bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:e1FC Traceroute Failed. Reason : Destination Port not in Fabric

#bcu fcdiag --fcecho 2/0 50:05:07:63:04:13:46:ebFC ECHO completed successfully

#bcu fcdiag --scsitest 1/0 20:20:00:11:0d:ef:f7:00

One or more commands failed expressed by <SCSIcommand><SCSI status>/<ASC value>/<ASCQ value>. ASC and ASCQ valid for Check Condition.RL: Report LUNSI: SCSI InquiryRC: Read Capacity commandRD: Read (10) command

See Also “diag”

Switch WWN Switch Domain ID

Ingress Port # Egress Port #

10:00:08:00:88:03:31:8b 127 5 11

10:00:08:00:88:03:31:8b 127 11 5

LUN# Type/Qualifier

Vendor Product Revision Size* LUN status**

0 00/000 SANBlaze VirtuaLUN Disk

v5.5 939800 Online

*Size is expressed in bytes from Read capacity response (Max LBA* block size)**Status: All commands successfully expressed by Online


fcoe B

fcoe Lists the Fibre Channel over Ethernet (FCoE) port commands. The FCoE port can be identified by the adapter index, the FCoE port index, the FCoE port name, or the FCoE port world wide name.

CAUTION

Disabling the FCoE port is a destructive operation that affects the normal operation of the FCoE port. If the FCoE port is taken offline, all remote Fibre Channel Port (FCP) sessions are logged out and all outstanding I/Os are terminated.

Synopsis bcu fcoe --enable <port_id>

bcu fcoe --disable <port_id>

bcu fcoe --stats <port_id>

bcu fcoe --statsclr <[port_id>

Description Enables or disables the Fibre Channel over Ethernet (FCoE) port.

Operands --enable Enables the FCoE port, if currently disabled. This command has no effect if the FCoE port is already enabled.

port_id Specifies the ID of the FCoE port that you want to enable.

--disable Disables the FCoE port, if currently enabled.

port_id Specifies the ID of the FCoE port that you want to disable.

--stats Displays the statistics for the FCoE port.

port_id Specifies the FCoE port for which you want to view statistics.

--statsclr Clears the statistics for the FCoE port.

port_id Specifies the FCoE port on which you want to clear statistics.

Example #bcu fcoe --enable 2/1Port enabled.

#bcu fcoe -enable 2/1ERROR: Port is already enabled.

# bcu fcoe --stats 2/1FCoE port statistics:Seconds since stats reset : 0CEE link up : 1CEE link down : 0FIP link up : 1FIP link down : 0FIP failures : 0Invalid mac assignments : 0Vlan requests : 1Vlan notifications : 1Vlan notification errors : 0Vlan request timeouts : 0Vlan invalids : 0


fcoeB

Discovery requests : 1Discovery responses : 1Discovery error frames : 0Discovery unsolicited : 0Discovery timeouts : 0Discovery FCF not avail : 0FIP link service req unsupp. : 0FIP link service req errors : 0FIP logo : 0Clear virtual link requests : 0FIP operation unsupp. : 0FIP untagged frames : 0Tx FCoE unicast frames : 12Tx FCoE unicast vlan frames : 11Tx FCoE unicast octets : 1868Tx FCoE mutlicast frames : 42Tx FCoE mutlicast vlan frames : 0Tx FCoE multicast octets : 3872Tx FCoE broadcast frames : 0Tx FCoE broadcast vlan frames : 0Tx FCoE broadcast octets : 0Tx timeouts : 0Transmit parity err : 0Transmit FID parity err : 0Tx pause frames : 0Tx zero pause frames : 0Tx first pause frames : 0Rx pause frames : 0Rx zero pause frames : 0Rx first pause frames : 0Rx unicast octets : 4264Rx unicast frames : 14Rx unicast vlan frames : 14Rx multicast octets : 4550Rx multicast frames : 38Rx multicast vlan frames : 0Rx broadcast octests : 0Rx broadcast frames : 0Rx broadcast vlan frames : 0

#bcu fcoe -statsclr 2/1Successfully reset the FCoE stats.

See Also None.


fcpim B

fcpimEnables or disables fast failover of initiator mode I/O. The default setting is off.

Synopsis bcu fcpim --stats <port_id> <rpwwn> [-l <lpwwn>]

bcu fcpim --statclr <port_id> <rpwwn> [-l <lpwwn>]

bcu fcpim --pathtov <port_id> <tov>

bcu fcpim --query <port_id> <rpwwn> [-l <lpwwn>]

bcu fcpim --modstats <port_id>

bcu fcipim --modstatsclr <port_id>

bcu fcpim --profile_on <port_id>

bcu fcipim --profile_off <port_id>

bcu fcpim --ioperf <port_range> [-l | -r] [-c count] [-i interval] <port_id> [-l [lpwwn]] [-r [rpwwn]] [-c count] [-i interval]

Description Enables or disables fast failover of the Fibre Channel Port (FCP) initiator mode I/O and displays or clears statistics.

Operands --stats Displays statistics related to the Fibre Channel port initiator mode.

port_id Specifies the ID of the port for which you want to display statistical information.

rpwwn Specifies the world wide name of the remote port for which you want to display statistics.

-l lpwwn Specifies the world wide name of the logical port or vport for which you want to display statistics.

--statclr Clears statistics related to the Fibre Channel port initiator mode.


rpwwn Specifies the world wide name of the remote port for which you want to clear statistics.

-l lpwwn Specifies the world wide name of the logical port or vport for which you want to clear statistics.

--pathtov Sets the path time out value for the target device.

port_id Specifies the ID of the port for which you want to query.

tov Specifies the optional path time out value in seconds (1 to 60). The default TOV is 30 seconds. A value of 0 is not allowed.


fcpimB

--query Queries the fcpim attributes.

port_id Specifies the ID of the port for which you want to query.

rpwwn Specifies the world wide name of the remote port for which you want to query.

-l lpwwn Specifies the world wide name of the local port or vport for which you want to query.

--modstats Displays statistics related to the Fibre Channel port initiator module.

port_id Specifies the ID of the module for which you want to display statistical information.

--modstatsclr Clears statistics related to the Fibre Channel port initiator mode.

port_id Specifies the ID of the module for which you want to clear statistical information.

--profile_on Sets the port IO profiling on. When set to on, the IO profile gathers the IO latency information based on size (average, minimum, and maximum).

port_id Specifies the ID of the module on which you want to set the profiling to on.

--profile_off Sets the port IO profiling off.

port_id Specifies the ID of the module on which you want to set the profiling to off.

--ioperf Sets the performance attributes for the port.

port_range Specifies the range of ports on which you want to monitor performance.

l | r Sets if the port is a local port or a remote port.

-c count Specifies how many times the output will be printed on the screen.

-i interval Specifies the output interval, in seconds.

port_id Specifies the ID of the port on which you want to monitor performance.

-l lpwwn Specifies the local port’s port world wide name for which you want to monitor performance. If the lpwwn is not specified, the base port is used.

-r rpwwn Specifies the remote port’s port world wide name for which you want to monitor performance. If the rpwwn is not specified, the base port is used.

Example With profile off:

bcu fcpim --query 1/1 20:01:00:11:0d:6f:6b:45FCP IM state: onlineData retransmission support: SupportedREC support: SupportedTask retry identification support: Not SupportedConfirmed completions support: SupportedIO profile support: OFF

With profile on:

# bcu fcpim --query 1/0 20:01:00:11:0d:8f:31:00FCP IM state : onlineData retransmission support : Not SupportedREC support : SupportedTask retry identification support : Not SupportedConfirmed completions support : Not Supported


fcpim B

IO profile start time : 1284043686IO completions: < 512B : 0 512B to < 1K : 0 1K to < 2K : 0 2K to < 4K : 0 4K to < 8K : 0 8K to < 16K : 0 16K to < 32K : 0 32K to < 64K : 0 64K to < 128K : 0 128K to < 256K : 0 256K to < 512K : 0 512K to < 1M : 0 1M to < 2M : 0 > 2M : 0

IO latency based in IO size in Millisecond: < 512B min : 0 max : 0 average : 0 512B to < 1K min : 0 max : 0 average : 0 1K to < 2K min : 0 max : 0 average : 0 2K to < 4K min : 0 max : 0 average : 0 4K to < 8K min : 0 max : 0 average : 0 8K to < 16K min : 0 max : 0 average : 0 16K to < 32K min : 0 max : 0 average : 0 32K to < 64K min : 0 max : 0 average : 0 64K to < 128K min : 0 max : 0 average : 0 128K to < 256K min : 0 max : 0 average : 0 256K to < 512K min : 0


fcpimB

max : 0 average : 0 512K to < 1M min : 0 max : 0 average : 0 1M to < 2M min : 0 max : 0 average : 0 > 2M min : 0 max : 0 average : 0

# bcu fcpim --stats 1/0 20:01:00:11:0d:8f:31:00

ITNIM Stats:num rport online : 1num rport offline : 0num prli sent out : 1num fcxp alloc waits : 0num prli rsp errors : 0num prli rsp accepts : 1rport is an initiator : 0prli rsp parsing errors : 0num prli rsp rejects : 0num timeouts detected : 0num sler notification from BFA : 0

HAL fcpim statisticsTotal IO Requests : 0Data in-bound requests : 0Data out-bound requests : 0Total IO Completions : 0Write data transfered in bytes : 0Read data transfered in bytes : 0Slowpath IO completions : 0IO underrun : 0IO overrun : 0IO Request-Q wait : 0IO Request-Q wait done : 0No free IO tag : 0IO timeouts : 0IO failure due to target offline: 0IO protocol errors : 0IO SBC-3 protection errors : 0fcp-2 error recovery failed : 0Delayed freeing of IO tag : 0Host IO abort requests : 0Host IO abort completions : 0IO clean-up requests : 0IO path tov expired : 0IO abort completions : 0IO cleaned-up due to IOC down : 0IO comp with unknown tags : 0Abort request due to TM command : 0Abort completion due to TM command: 0IT Nexus create requests : 0IT Nexus FW create requests : 0


fcpim B

IT Nexus FW create completions : 0IT Nexus onlines : 0IT Nexus offlines : 0IT Nexus FW delete requests : 0IT Nexus FW delete completions : 0IT Nexus delete requests : 0SLER events : 0Num IOC disables : 0IT Nexus cleanup completions : 0TM Requests : 0TM Completions : 0TM initiated IO cleanup success : 0TM initiated IO cleanup failure : 0No free TM tag : 0TM Request-Q wait : 0TM Request-Q wait done : 0TM cleaned-up due to IOC down : 0TM cleanup requests : 0TM cleanup completions : 0Total data transfered in bytes : 0

# bcu fcpim --modstats 1/0FCPIM module Stats:

FCPIM module Active ITNIM Stats:

Total IO Requests : 0Data in-bound requests : 0Data out-bound requests : 0Total IO Completions : 0Write data transfered in bytes : 0Read data transfered in bytes : 0Slowpath IO completions : 0IO underrun : 0IO overrun : 0IO Request-Q wait : 0IO Request-Q wait done : 0No free IO tag : 0IO timeouts : 0IO failure due to target offline: 0IO protocol errors : 0IO SBC-3 protection errors : 0fcp-2 error recovery failed : 0Delayed freeing of IO tag : 0Host IO abort requests : 0Host IO abort completions : 0IO clean-up requests : 0IO path tov expired : 0IO abort completions : 0IO cleaned-up due to IOC down : 0IO comp with unknown tags : 0Abort request due to TM command : 0Abort completion due to TM command: 0IT Nexus create requests : 0IT Nexus FW create requests : 0IT Nexus FW create completions : 0IT Nexus onlines : 0IT Nexus offlines : 0IT Nexus FW delete requests : 0IT Nexus FW delete completions : 0


fcpimB

IT Nexus delete requests : 0SLER events : 0Num IOC disables : 0IT Nexus cleanup completions : 0TM Requests : 0TM Completions : 0TM initiated IO cleanup success : 0TM initiated IO cleanup failure : 0No free TM tag : 0TM Request-Q wait : 0TM Request-Q wait done : 0TM cleaned-up due to IOC down : 0TM cleanup requests : 0TM cleanup completions : 0Total data transfered in bytes : 0

FCPIM module Deleted ITNIM Stats:

Aborted IO requests : 127IO timeouts : 0IO retry for SQ error recovery : 0Delayed freeing of IO resources : 129Host IO abort requests : 2Total IO count : 1301027IO cleaned-up due to IOC down : 0TM cleaned-up due to IOC down : 0

bcu fcpim --statsclr 1/0 50:05:00:05:1e:13:9c:00Successfully reset the fcpim level stats

bcu fcpim --modstatsclr 1/1Successfully reset the fcpim modstatsWarning: All active ITNIM stats are cleared.

bcu fcpim --pathtov 1/0 1path timeout is set to 1

bcu fcpim --profile_on 1/1fcpim profile is ON.Warning: fcpim profile ON will affect IO Performance.

# bcu fcpim --profile_off 1/1fcpim profile off

# bcu fcpim --ioperf 1/0-1/1Port IOPs Throughput=========================== 1/0 706 353.0 MB/s 1/1 0 0 1/0 701 350.5 MB/s 1/1 0 0 1/0 681 340.5 MB/s 1/1 0 0 1/0 703 351.5 MB/s 1/1 0 0

# bcu fcpim --ioperf 1/0 -l -r -c 3 -i 2


fcpim B

Port lport WWN rport WWN IOPs Throughput============================================================================= 1/0 10:00:00:05:1e:55:46:51 20:03:00:11:0d:45:0a:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:01:00:11:0d:6f:6b:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:45:09:00 0 346.0 MB/s 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:ef:f7:00 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:16 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:15 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:53:02:f3 0 0

<pause 2 sec> 1/0 10:00:00:05:1e:55:46:51 20:03:00:11:0d:45:0a:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:01:00:11:0d:6f:6b:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:45:09:00 0 344.7 MB/s 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:ef:f7:00 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:16 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:15 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:53:02:f3 0 0 <pause 2 sec> 1/0 10:00:00:05:1e:55:46:51 20:03:00:11:0d:45:0a:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:01:00:11:0d:6f:6b:00 0 0 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:45:09:00 0 344.2 MB/s 1/0 10:00:00:05:1e:55:46:51 20:02:00:11:0d:ef:f7:00 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:16 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:a2:53:15 0 0 1/0 10:00:00:05:1e:55:46:51 10:00:00:05:1e:53:02:f3 0 0 <exits>

See Also “ioc”“vport”


iocB

iocEnables or disables the I/O Controller (IOC), which refers to the combination of port and the firmware controlling it.

The port can be identified using the adapter index, the port index, the port world wide name or the port name.

Synopsis bcu ioc --enable <port_id>

bcu ioc --disable <port_id>

bcu ioc --fwstats <ioc_id>

bcu ioc --fwstatsclr <ioc_id>

bcu ioc --intr <port_id> <-coalesce | -c> {on|off} [<-l <usecs>]<-d <usecs>]

bcu ioc --query <ioc_id>

bcu ioc --stats <port_id>

bcu ioc --statsclr <port_id>

Description The IOC commands allow you to set the interrupt attributes for the port.

CAUTION

Disabling the IOC is a destructive operation.

Operands --enable Enables the IO Controller (IOC). If the IOC is already enabled, the command is ignored.

port_id Specifies the port of the IO Controller (IOC) you want to enable.

--disable Caution: Disabling the IOC is a destructive operation. Disables the port of the IO Controller (IOC). If the IOC is already disabled, the command is ignored.

port_id Specifies the ID of the port you want to disable.

--fwstats Displays the IOC level statistics on the specified port.

ioc_id Specifies the ID of the I/O Controller firmware for which you want to display statistical information.

--fwstatsclr Clears the IOC firmware level statistics on the specified I/O Controller.

ioc_id Specifies the ID of the I/O Controller firmware for which you want to clear statistical information.

--intr Sets the interrupt attributes for the port.

port_id Specifies the ID of the port on which you want to set interrupt attributes.

coalesce | c Sets the coalesce flag.

on | off Sets the port’s interrupt attributes. Possible values are on or off.


ioc B

-l usecs Sets the latency monitor timeout value. Latency can be between 0 to 225 microseconds. A latency value of 0 disables latency monitor timeout interrupt. The default latency value is 5 for an HBA and 5 for a CNA.

-d delay Sets the delay timeout interrupt value. A delay can be between 0 to 1125 microseconds. A delay value of 0 disables the delay timeout interrupt. The default delay value is 25 for an HBA and 25 for a CNA.

--query Queries the attributes of the Storage IOC with the IOC ID.

ioc_id Specifies the port of the IO Controller (IOC) you want to enable.

--stats Displays the IOC level statistics on the specified port.


--statsclr Clears the IOC level statistics on the specified port.


Example #bcu ioc --query 1/0chip rev: Rev-Bmanufacturer: Brocadeserial#: ARZ0351D00Bmodel_descr: 1020pwwn: 10:00:00:05:1e:55:1d:3cnwwn: 20:00:00:05:1e:55:1d:3cf/w ver: pvt_bld03 05/05/2009 15.12.12bios ver:port count: 2status is: operationalssid: 0x0014vendor id: 0x1657device id: 0x0014pci function: 0IOC type: interrupt coalescing: oninterrupt delay: 25 usinterrupt latency: 0 us

# bcu ioc --stats 1/0Num suspends: 7

bcu ioc --statsclr 1/0ioc stats cleared.

bcu ioc --enable 1/0ioc is enabled

bcu ioc --enable ad1_p0ioc is already enabled

bcu ioc --disable 1/0ioc is disabled

bcu ioc --disable ad1_p0ioc is already disabledbcu --intr 1/0 --coalesce offinterrupt coalescing has been turned off


iocB

bcu ioc --intr 1/0 --coalesce onThe intr settings have been configured with value(s):

Coalesce: on

bcu ioc --intr 1/0 --coalesce on 12 19The intr settings have been configured with value(s):

Coalesce: onDelay: 19 (micro-seconds)Latency: 12 (micro-seconds)

See Also “adapter”“lport”


log B

logSets the log level for each module. If no log level is specified, the current level is used.

Synopsis bcu log --level <port_id> [<Critical|Error|Warning|Info>] [-m <fw|hal|fcs|drv|aen|all>]

Description The number of messages logged by the host depends on the predetermined logging level. Although the adapter might generate many messages, only certain types of messages are logged based on the specified logging level.

Operands --level Specifies the number of messages logged by the host, which depends on the predetermined logging level.

port_id Specifies the ID of the port for which you want to set the log level.

Critical|Error|Warning|Info

Specifies the severity level. Supported log levels include Critical, Error, Warning, or Info. If no level is set, the default setting is used, which is Warning.

-m fw|hal|fcs|drv|aen|all

Example #bcu log --level 2/0FW log level is WarningHAL log level is WarningFCS log level is WarningDRV log level is WarningAEN log level is Warning

#bcu log --level 2/0 infoLog level set to Info

#bcu log --level 2/0FW log level is InfoHAL log level is InfoFCS log level is InfoDRV log level is InfoAEN log level is Info

See Also None


lportB

lport Lists the logical port (lport) commands.

Synopsis bcu lport --list <port_id>

bcu lport --query <port_id> [-l lpwwn]

bcu lport --stats <port_id> [-l lpwwn]

bcu lport --statsclr <port_id> [-l lpwwn]

Description Lists all the logical ports (lports) under a given port ID. A logical port is a port that is logged into a fabric. Possible logical port type values are the following:

• Base port

• Virtual port

• Logical port PWWN - logical port’s port world wide name

• Logical port NWWN - logical port’s port node world wide name

• FC addr - FC address of the logical port

Possible roles supported by the logical port are FCP initiator mode (IM), FCP target mode (FCPTM), and IP over FC support (IP).

Operands --list Lists all the lports for a specified port.


--query Lists the attributes of the logical port.


-l lpwwn Specifies the logical port’s world wide name for which you want to display information. If the lpwwn is not specified, the base port is used.

--stats Displays the logical port’s statistics.


-l lpwwn Specifies the logical port’s world wide name for which you want to display statistical information. If the lpwwn is not specified, the base port is used.

--statsclr Clears the logical port’s statistics.


-l lpwwn Specifies the logical port’s port world wide name for which you want to clear statistical information. If the lpwwn is not specified, the base port is used.


lport B

Example # bcu lport --list 5/1 Port ID: 5/1 Port Name:ad5_p1 Port PWWN:11:22:33:44:55:66:77:88 Port NWWN:10:22:33:44:55:66:77:88 Port HW path:1.5.3.0 Num lports: 4 -------------------------------------------------------------------------- PT Logical Port PWWN Logical Port NWWN FC Addr FC4 Roles -------------------------------------------------------------------------- BP aa:bb:cc:dd:ee:ff:00:01 aa:bb:cc:dd:ee:ff:00:02 645500 IM VP 01:bb:cc:dd:ee:ff:00:01 01:bb:cc:dd:ee:ff:00:00 645501 IM, IP VP 02:bb:cc:dd:ee:ff:00:01 02:bb:cc:dd:ee:ff:00:00 645502 IM, VP 04:bb:cc:dd:ee:ff:00:01 04:bb:cc:dd:ee:ff:00:00 645503 IM

bcu lport --query hba5_port0State: OnlineFC address: 0c0100Port wwn: aa:bb:cc:dd:ee:ff:aa:bbNode wwn: cc:dd:cc:aa:ff:cc:aa:ffSymbolic name:FC4 Role: fcpim ipfc

bcu lport --query hba5_port0 - 1 01:bb:cc:dd:ee:ff:00:01State: OnlineFC address: 0c0101Port wwn: 01:bb:cc:dd:ee:ff:00:01Node wwn: 01:bb:cc:dd:ee:ff:00:00

# bcu lport --stats 1/0ns_plogi_sent : 3ns_plogi_rsp_err : 0ns_plogi_acc_err : 0ns_plogi_accepts : 3NS command rejects : 0ns_plogi_unknown_rsp : 0ns_plogi_alloc_wait : 0NS command retries : 0NS command timeouts : 0ns_rspnid_sent : 3ns_rspnid_accepts : 3ns_rspnid_rsp_err : 0ns_rspnid_rejects : 0ns_rspnid_alloc_wait : 0ns_rftid_sent : 3ns_rftid_accepts : 3ns_rftid_rsp_err : 0ns_rftid_rejects : 0ns_rftid_alloc_wait : 0ns_rffid_sent : 3ns_rffid_accepts : 3ns_rffid_rsp_err : 0ns_rffid_rejects : 0ns_rffid_alloc_wait : 0ns_gidft_sent : 3ns_gidft_accepts : 3ns_gidft_rsp_err : 0ns_gidft_rejects : 0


lportB

ns_gidft_unknown_rsp : 0ns_gidft_alloc_wait : 0MS command retries : 0MS command timeouts : 0ms_plogi_sent : 3ms_plogi_rsp_err : 0ms_plogi_acc_err : 0ms_plogi_accepts : 3MS command rejects : 0ms_plogi_unknown_rsp : 0ms_plogi_alloc_wait : 0Num of RSCN received : 0Num portid format RSCN : 0Unsolicited recv frames : 0Dropped received frames : 0Received plogi : 0Received prli : 0Received adisc : 0Received prlo : 0Received logo : 0Received rpsc : 0Received unhandled ELS : 0Rport plogi retry timeout count : 8Deleted rport (max retry of plogi): 0Total IO Requests : 0Data in-bound requests : 0Data out-bound requests : 0Total IO Completions : 0Write data transfered in bytes : 0Read data transfered in bytes : 0Slowpath IO completions : 0IO underrun : 0IO overrun : 0IO Request-Q wait : 0IO Request-Q wait done : 0No free IO tag : 0IO timeouts : 0IO failure due to target offline: 0IO protocol errors : 0IO SBC-3 protection errors : 0fcp-2 error recovery failed : 0Delayed freeing of IO tag : 0Host IO abort requests : 0Host IO abort completions : 0IO clean-up requests : 0IO path tov expired : 0IO abort completions : 0IO cleaned-up due to IOC down : 0IO comp with unknown tags : 0Abort request due to TM command : 0Abort completion due to TM command: 0IT Nexus create requests : 0IT Nexus FW create requests : 0IT Nexus FW create completions : 0IT Nexus onlines : 0IT Nexus offlines : 0IT Nexus FW delete requests : 0IT Nexus FW delete completions : 0IT Nexus delete requests : 0SLER events : 0


lport B

Num IOC disables : 0IT Nexus cleanup completions : 0TM Requests : 0TM Completions : 0TM initiated IO cleanup success : 0TM initiated IO cleanup failure : 0No free TM tag : 0TM Request-Q wait : 0TM Request-Q wait done : 0TM cleaned-up due to IOC down : 0TM cleanup requests : 0TM cleanup completions : 0Total data transfered in bytes : 0

# bcu lport --statsclr hba5_port0lport stats cleared

The following are examples of a Brocade 1020 expansion card versus a Brocade 825 card query:

1020 bcu lport --query

[root@HB081222-RH4u7x86 ~]# bcu lport --query 1/0Port FC Addr: 860e01Port Type: Base Port (State: Linkup)Port PWWN: 10:00:00:05:1e:8e:b6:02Port NWWN: 20:00:00:05:1e:8e:b6:02Symbolic name: 1020 | 2.3.0.0 | HB081222-RH4u7x86 | Red Hat Enterprise Linux AS release 4 (Nahant Update 7) |Role: FCP InitiatorFabric Name: 10:00:00:05:1e:90:13:98Switch IP Addr: 10.32.82.134FPMA MAC Addr: 0e:fc:00:86:0e:01

825 bcu lport --query

[root@HB081222-RH4u7x86 ~]# bcu lport --query 2/0Port FC Addr: 8a0600Port Type: Base Port (State: Linkup)Port PWWN: 10:00:00:05:1e:0f:1a:b1Port NWWN: 20:00:00:05:1e:0f:1a:b1Symbolic name: 825 | 2.3.0.0 | HB081222-RH4u7x86 | Red Hat Enterprise Linux AS release 4 (Nahant Update 7) |Role: FCP InitiatorFabric Name: 10:00:00:05:1e:05:09:29Switch IP Addr: 10.32.82.138

See Also None


pbindB

pbindEnables target port world wide name (WWN) binding to a persistent target ID for an operating system (OS) stack. Persistent binding is available on the Windows operating system only.

Synopsis bcu pbind --list <port_id>

Description Queries the list of mappings or clears existing persistent binding settings.

NOTEThe pbind command is only supported on the Windows platform.

Operands --list Queries the list of mappings from the persistent binding module.


See Also None


phy B

phyThe PHY module aids in communication to and from the Ethernet. The PHY command updates the firmware and queries the attributes and statistics of the external PHY module.

NOTEPHY commands are applicable to CNAs version 2.3 that are installed with the PHY module only (version 2.3 and later).

Synopsis bcu phy --update <ad_id | -a> <binary file>

bcu phy --query <port_id>

bcu phy --stats <port_id>

Description Updates the PHY firmware and queries the attributes and statistics of the external PHY module.

Operands --update Updates the firmware on a specified adapter.

ad_id | a Specifies the adapter ID on which the firmware will be updated. If -a is specified, the update occurs on all eligible adapters on the system. An adapter is eligible if it contains the external PHY hardware.

binary file Specifies the firmware image file that will be used to update the specified adapter.

--query Displays the PHY module attributes for the specified port.

port_id Specifies the port on which the PHY module attributes will be displayed.

--stats Displays the PHY module statistics for the specified port.

port_id Specifies the port on which the PHY module statistics will be displayed.

Examples #bcu phy --update 1 fwimgUpdating Phy Firmware on the port 1/0Successfully updated the FirmwareUpdating Phy Firmware on the port 1/1Successfully updated the Firmware

#bcu phy --query 1/0Phy Module attributes:Phy status: GoodFirmware version: 0x920cLink partner auto-negotiation ability: YesPHY auto-negotiation ability: YesAN complete: NoPMA/PMD link status: Link upPMA/PMD signal detected: NoPCS link status: Link up


phyB

#bcu phy --stats 1/0Phy Module statistics:

Phy stats status: GoodLink breaks after linkup: 0PMA/PMD receive fault: DetectedPMA/PMD transmit fault: DetectedPCS receive fault: DetectedPCS transmit fault: DetectedSpeed negotiations: 1TX EQ trainings: 0TX EQ timeouts: 4CRC errors: 4

See Also None


port B

portLists the port commands (the physical ports on the adapter), along with their basic attributes. The port ID can be any one of the following:

• Port ID

• Adapter ID


• Port Name


NOTE1 Gbps speed is not valid for an 8 Gbps HBA; 4 Gbps speed is not valid for a 4 Gbps HBA.

Synopsis bcu port --list

bcu port --name <port_id> [port_name]

bcu port --enable <port_id>

bcu port --disable <port_id>

bcu port --stats <port_id>

bcu port --statsclr <port_id>

bcu port --query <port_id>

bcu port --topology <port_id> [p2p]

bcu port --speed <port_id> [1|2|4|8|10|auto]

bcu port --trunk <port_id> [<off | on <port_list>> ]

bcu port --dfsize <port_id> [dfsize]

bcu port --perf <port_range|all> [-c count] [-i interval]

Description Lists all the physical ports for a given port identifier. Possible port identifiers could be any one of the following:

• Adapter ID

• Port ID

• Port WWN

• Port name (user assigned)


Operands --list Lists all the physical ports along with their basic attributes.

Note: A new trunked port entry is listed along with physical ports when adapter trunking is enabled. The suffix ‘T’ and the port number indicates the trunked port corresponds to all adapter ports.


portB

--name Queries or sets the port name. You can clear the port name using an empty string (“ “).


port_name Specifies a new name for the port. The name can include up to 15 alphanumeric characters and must begin with an alphabetic letter. Naming a port is optional; if you do not specify a port name, the current port name displays.

--enable Enables the physical port if it is disabled.

port_id Specifies the ID of the port you want to enable.

--disable Disables the physical port, if currently enabled. This is a destructive operation and affects normal operation of the port. The port is taken offline, all remote FCP sessions are logged out, and all outstanding I/Os are terminated. You are prompted before disabling occurs.


--stats Displays the physical port-level statistics.


--statsclr Clears port-level statistics.


--query Queries and displays port-related details for a port.


--speed Queries or sets the port speed. The port speed can be changed dynamically (when the port is enabled). If the port is disabled, the new port speed setting takes effect when the port is re-enabled.

port_id Specifies the ID of the port for which you want to set the port speed.

1|2|4|8|10

Queries or sets the port speed. Possible values are auto (to auto-negotiate the speed) and 1, 2, 4, 8, and 10 Gbps speeds. The 10 Gbps speed is only valid for the Converged Network Adapter (CNA).

Note: The 1 Gbps speed is not valid for an 8 Gbps HBA (825, 815) and the 8 Gbps speed is not valid for a 4 Gbps HBA (425, 415).

All speeds are valid for a mezzanine card (804).

--trunk Enables or disables port trunking.

Note: To ensure that other physical port resources are available, their respective ports must be disabled; otherwise, the trunked operation will fail.

port_id Specifies the ID of the port for which you want to enable or disable trunking.

port_list Specifies a comma-separated list of all the ports within the adapter (identified by the port ID).


port B

--dfsize Queries or sets the port’s maximum receive data field size. If you do not specify a value, the current receive buffer size displays.

Note: The new receive data field size takes effect when the port is re-enabled.

port_id Specifies the ID of the port for which you want to set the data field size.

df_size Indicates the maximum supported receive data field size, in decimal value. Possible values are 512, 1024, 2048, and 2112. If set to ‘auto,’ the default value is used, which is 2112.

--topology Queries or sets the port topology.

Note: The topology operand is not applicable to CNAs.

port_id Specifies the ID of the port for which you want to display or set the topology.

p2p Specifies the topology type. Supported topology mode is point-to-point (p2p).

--perf Displays the data throughput for a given port and for a given interval.

port_range Specifies the port range; for example, 1/0, 1/0-2/1, or all.

-c count Specifies the number of iterations of the display. The default behavior is to continually refresh; you can terminate the default with CTRL-C.

-i interval Specifies the interval delay value, in seconds. The default interval value is 1 second.

Example # bcu port --list ------------------------------------------------------------------------ Port# Type PWWN/MAC FC Addr/ Media State Spd Eth dev ------------------------------------------------------------------------ 1/0 fc 10:00:00:05:1e:0a:31:66 011f00 sw Linkup 8G 1/1 fc 10:00:00:05:1e:0a:31:67 -- -- Linkdown --- 2/0 fc 10:00:00:05:1e:53:0e:ca 059e80 sw Linkup 4G 2/1 fc 10:00:00:05:1e:53:0e:cb 059c80 sw Linkup 4G 3/0 cee 00:05:1e:55:3a:18 -- sw CEE Linkup 10G fcoe 10:00:00:05:1e:55:3a:18 120804 Linkup eth 00:05:1e:55:3a:1a eth2 Linkup 3/1 cee 00:05:1e:55:3a:19 -- sw CEE Linkup 10G fcoe 10:00:00:05:1e:55:3a:19 120801 Linkup eth 00:05:1e:55:3a:1b eth3 Linkup ------------------------------------------------------------------------ # bcu port --list (When adapter trunking is enabled) ------------------------------------------------------------------------ Port# Type PWWN/MAC FC Addr/ Media State Spd Eth dev ------------------------------------------------------------------------ 1/0 cee 00:05:1e:a1:28:8b -- sw Linkdown --- fcoe 10:00:00:05:1e:a1:28:8b -- Linkdown 2 fc-T 10:00:00:05:1e:61:69:9b 010800 sw Linkup 8G 2/0 fc 10:00:00:05:1e:61:69:9b -- sw Linkup 4G 2/1 fc 10:00:00:05:1e:61:69:9c -- sw Linkup 4G ------------------------------------------------------------------------

# bcu port --name 1/0 emc_fab3_ad5_p0Port 1/0’s name set to emc_fab3_ad5_p0


portB

# bcu port --name 1/0 Port 1/0’s name is emc_fab3_ad5_p0

# bcu port --enable 2/1port enabled

# bcu port --enable 2/1port is already enabled

# bcu port --disable 2/1 port disabled

# bcu port --disable 2/1port is already disabled

# bcu port --stats 4/0Physical port statistics (FC HBA):

tx_frames : 385508684 tx_words : 38422038819

rx_frames : 514011477rx_words : 38687649865

lip_count : 0 nos_count : 0 link_failures : 1 loss_of_syncs : 0 loss_of_signals : 0 primseq_errs : 0 invalid ordered set : 0 nonframe coding err : 0 invalid_crcs frames : 0 undersized frames : 0 oversized frames : 0 bad EOF frames : 0 error_frames : 0 dropped_frames : 0

# bcu port --stats 4/0 Physical port statistics: 64 byte frames : 1315 65-127 byte frames : 704210587 128-255 byte frames : 336 256-511 byte frames : 1250 512-1023 byte frames : 2337 1024-1518 byte frames: 281686685 1519-1522 byte frames: 0 tx_frames : 422530324 tx_bytes : 181971963859 tx_mcast frames : 1710 tx_bcast frames : 754 tx_drop frames : 0 tx_jabber frames : 0 tx_fcs_error frames : 0 tx_control frames : 0 tx_fragments : 0 rx_frames : 563372638 rx_bytes : 187640498430 rx_mcast frames : 1847 rx_bcast frames : 7423 rx_control frames : 0


port B

rx_unknown_op frames : 0 rx_drop frames : 0 rx_jabber frames : 0 rx_fcs_error frames : 0 rx_align_err frames : 0 rx_length_err frames : 0 rx_code_error : 0 rx_fragments : 0 tx_pause : 0 tx_zero_pause : 0 rx_pause : 0 rx_zero_pause : 0 tx_fcoe_pause : 0 tx_fcoe_zero_pause : 0 rx_fcoe_pause : 0 rx_fcoe_zero_pause : 0

# bcu port --statsclr dell_s1_ad0_p1port stats cleared

# bcu port --query 1/0port id: 1/0port type: FCport instance: 0port name:Media: swpwwn: 10:00:00:05:1e:53:0e:canwwn: 20:00:00:05:1e:53:0e:castate: LinkupSpeed: current: 8G configured: AutoTopology: current: P2PSNIA port type: Nsupported classes: Class-3symbolic name: Brocade-825 | 2.0.0.006 | C06_I3650_83110 | MicrosoftWindows Server 2003 R2 |Service Pack 2maximum frame size: 2112receive bb credits: 48transmit bb credits: 8QOS: DisabledTRL: DisabledTRL default speed: 1GPath TOV: 45 secondsBeacon status: Offpbind status: EnabledPortlog: Enabled

# bcu port --query 3/0port id: 3/0port type: CNAport instance: 2port name:Media: swSpeed: 10GCNA/CEE status: CEE LinkupFCoE: MAC: 00:05:1e:55:3a:18 pwwn: 10:00:00:05:1e:55:3a:18


portB

nwwn: 20:00:00:05:1e:55:3a:18 state: Linkup supported classes: Class-3 symbolic name: BR-1020 | 2.0.0.006 | C06_I3650_83110 |

Microsoft Windows Server 2003 R2 | Service Pack 2 maximum frame size: 2112 receive bb credits: 48 transmit bb credits: 74 QOS: Disabled TRL: Disabled TRL default speed: 1G Path TOV: 45 seconds Beacon status: Off pbind status: Enabled Portlog: Enabled Vlans: --Eth: MAC: 00:05:1e:55:3a:1a Factory MAC: 00:05:1e:55:3a:1a state: Linkup OS Eth Device: Local Area Connection 5

# bcu port --topology 1/1 p2pTopology set to p2p

# bcu port --speed 1/1 autoPort speed set

# bcu port --trunk 1/0 on 0,1 Port trunking enabled # bcu port --trunk 1/0 on 0,1 ERROR: Port trunking enable failed. Disable IOC 1 before adding it to the trunk group.

# bcu port --trunk 1/0 off Port trunking disabled

# bcu port --trunk 1/0 Port trunking is currently enabled. Ports in trunk group: 0, 1

# bcu port --dfsize 1/1 2112Setting will be enforced after port --disable and port--enable

# bcu port --dfsize 1/1 autoPort maximum receive data field size set to driver default.


port B

# bcu port --perf 1/0-1/1Port 1/0 1/1Type FC ETH FC ETH========================================================TX RX TX RX TX RX TX RX========================================================181.4M 182.6M 0 0 0 0 0 0182.6M 183.5M 0 0 0 0 0 0

# bcu port --perf all -c 3 -i 2Port 1/0 1/1 2/0 2/1Type FC ETH FC ETH FC FC=================================================================================TX RX TX RX TX RX TX RX TX RX TX RX=================================================================================184.5M 185.6M 0 0 0 0 0 0 401.6M 402.9M 0 0<After 2 sec>186.9M 185.6M 0 0 0 0 0 0 402.9M 401.7M 0 0<After 2 sec>185.7M 186.6M 0 0 0 0 0 0 400.9M 402.0M 0 0<Stops after 2 iterations>

See Also “adapter”“ioc”


qos (HBA only)B

qos (HBA only)

NOTEThe QoS feature is not supported on the converged network adapter (CNA).

Quality of Service (QoS) works in conjunction with the QoS feature on Brocade switch F_ports. The Fabric operating system (FOS) provides a mechanism to assign traffic priority (high, medium, or low) for a given source and destination traffic flow. By default, all flows are marked as medium.

Synopsis bcu qos --enable <port_id>

bcu qos --disable <port_id>

Description Enables or disables Quality of Service (QoS). The QoS commands apply to the 8 Gbps HBA only. QoS is not supported on the CNA.

Operands --enable Enables Quality of Service (QoS).

port_id Specifies the ID of the port on which QoS is enabled.

--disable Disables QoS.

port_id Specifies the ID of the port on which QoS is disabled.

Example bcu qos --query 1/0

See Also None


ratelim B

ratelim Enables or disables target rate limiting support on the HBA side.

NOTEThe target rate limiting feature is not supported on the converged network adapter (CNA).

Synopsis bcu ratelim --enable <port_id> [-s <default-speed>

bcu ratelim --disable <port_id>

Description The target rate limiting feature is used to minimize congestion at the HBA port due to a slow drain device operating in the fabric at a slower speed. A remote port’s operating speed is determined from the fabric. Traffic destined to the remote port is limited to its current operating speed.

The default rate limit is 1 Gbps. Target rate limiting (TRL) is supported only when the HBA port is connected to the fabric. Therefore, TRL is not supported when the port is directly connected with another device.

Possible port identifiers could be any one of the following:

• Adapter ID

• Port ID

• Port WWN

• Port name (user assigned)


NOTEYou must first enter the bcu port --disable <port_id> command, followed by the port --enable command, before the ratelim --enable or ratelim --disable commands take effect.

Operands --enable Enables target rate limiting, if currently disabled.

port_id Specifies the ID of the port you want to enable.

-s default-speed Sets the target rate limiting speed on the HBA. Options are 1 Gbps, 2 Gbps, and 4 Gbps.

--disable Disables target rate limiting on the HBA, if currently enabled.


See Also None


rportB

rport Lists the commands that apply to a remote port in a fabric. A remote port is a port that is physically separated from the adapter.

Synopsis bcu rport --list <port_id> [-l <lpwwn>]

bcu rport --osname <port_id> [-l <lpwwn>]

bcu rport --query <port_id> <rpwwn> [-l <lpwwn>]

bcu rport --stats <port_id> <rpwwn> [-l <lpwwn>]

bcu rport --statsclr <port_id> <rpwwn> [-l <lpwwn>]

Description Lists all the remote ports (rports) under a given port ID.

Operands --list Lists all remote ports accessible for a given logical port.

port_id Specifies the ID of the port for which you want to display rport information.

-l lpwwn Specifies the logical port world wide name. This is an optional argument.

Note: If the -l lpwwn argument is not specified, the base port is used.

--osname Lists all the osnames of the remote ports that are visible through the local port.

port_id Specifies the ID of the port for which you want to display osnames.

-l lpwwn Specifies the logical port world wide name. This is an optional argument.

--query Displays detailed attributes of a remote port.

port_id Specifies the ID of the port for which you want to query attributes of a remote port.

rpwwn Specifies the remote port world wide name for which you want to query attributes.

-l lpwwn Specifies the logical port world wide name for which you want to query attributes of a remote port. This is an optional argument.


--stats Displays remote port statistics.


rpwwn Displays the remote port’s port world wide name.

-l lpwwn Displays the logical port world wide name. This is an optional argument.


--statsclr Clears the remote port statistics.

port_id Specifies the ID of the port for which you want to clear remote port statistics.

rpwwn Specifies the remote port’s port world wide name for which you want to clear remote port statistics

-l lpwwn Displays the logical port world wide name. This is an optional argument.


rport B

Example bcu rport --list 2/0

---------------------------------------------------------------------------FC Addr Remote Port PWWN QOS-P/F SPD State F df_sz---------------------------------------------------------------------------01fd01 50:00:1f:e1:50:10:09:48 U/0 --- online T 204801f701 50:06:01:60:41:e0:68:c0 U/0 --- online T 204801f202 50:06:0e:80:03:75:5e:05 U/0 --- online T 204801f002 20:02:00:0e:11:10:fc:25 U/0 --- online T 204801ff01 50:05:07:63:0e:04:12:ef U/0 --- online T 204801fe01 50:06:01:60:3c:e0:0c:a3 U/0 --- online T 204801fc01 50:01:43:80:01:3b:fb:38 U/0 --- online T 204801f601 20:16:00:a0:b8:42:20:ac U/0 --- online T 2048---------------------------------------------------------------------------

bcu rport --query 1/0 21:00:00:04:cf:75:6a:04RPORT FC Address: 01f701RPORT port wwn: 50:06:01:68:41:e0:68:c0RPORT node wwn: 50:06:01:60:c1:e0:68:c0Status: onlineClass of Service: Class-3Function: TargetData Field size: 2048Cont.Incr.seq_cnt(CISC): Not SupportedCurrent Speed: ---symbolic name: DGC LUNZ 0324Vendor: DGCProduct ID: DISKProduct Rev: 0324QOS priority: UnknownQOS flow id: 0TRL enforced: No

bcu rport --stats 1/0 aa:bb:cc:dd:ee:ff:00:01offlines: 1onlines: 2RSCN : 0PLOGI sent: 2PLOGI accepts : 2PLOGI timeouts: 0PLOGI failed: 0PLOGI rejects : 0PLOGI received: 0PRLI received: 0ADISC sent: 0ADISC received: 0ADISC rejects : 0ADISC accepts : 0ADISC failed: 0ADISC rejected: 0LOGO sent: 0LOGO accepts: 0LOGO failed: 0LOGO rejected: 0LOGO received: 0RPSC received: 0RPSC rejects: 0RPSC sent: 8RPSC accepts: 0RPSC failed: 8


rportB

RPSC rejected: 0

HAL rport statistics: uninit: create events: 1 uninit: exception events: 0 created: online events: 1 created: delete events: 0 created: IOC down: 0 created: exception events: 0 fw create: f/w responses: 2 fw create: delete events: 0 fw create: offline events: 0 fw create: IOC down: 0 fw create: exception events: 0 online: offline events: 1 online: delete events: 0 online: IOC down events: 0 online: exception events: 0 fw delete: fw responses: 1 fw delete: delete events: 0 fw delete: IOC down events: 0 fw delete: exception events: 0 offline: delete events: 0 offline: online events: 1 offline: IOC down events: 0 offline: exception events: 0 delete: fw responses: 0 delete: IOC down events: 0 delete: exception events: 0 delete pend: fw responses: 0 delete pend: IOC downs: 0 delete pend: exceptions: 0 off-pending: fw responses: 0 off-pending: deletes: 0 off-pending: IOC downs: 0 off-pending: exceptions: 0 IOC down: offline events: 0 IOC down: delete events: 0 IOC down: online events: 0 IOC down: exceptions: 0

bcu rport --statsclr 1/0 aa:bb:cc:dd:ee:ff:00:01Successfully reset the rport level stats

See Also None


team B

teamTeaming is supported only on the Windows operating system.

Synopsis bcu team --list

bcu team --query <team_name>

bcu team --create <team_name> <team_mode> <port_id1> [..<port_idn>]

bcu team --addport <team_name> <port_id1> [..<port_idn>]

bcu team --remport <team_name> <port_id1> [..<port_idn>]

bcu team --name <team_name> <new_team_name>

bcu team --primary <team_name> <port_id>

bcu team --xmit_policy <team_name> {l2 | l3_l4}

bcu team --remove <team_name>

bcu team --vlanadd <team_name> <vlan_id> [<vlan_name>]

bcu team --vlanremove <team_name> <vlan_id>

bcu team --vlanedit <team_name> <vlan_id> <vlan_name>

bcu team --vlanlist <team_name>

bcu team --vlanquery <team_name><vlan_id>

Description Configures ports and VLANs on the teaming interface.

Operands --list Lists all the configured teams in the system.

--query Queries the teaming configuration.

team_name Specifies the team name.

--create Adds a new teaming interface to the system.

team_name Specifies the teaming interface name.

team_mode Specifies the team mode. Supported values are 802.3ad, failover, and failback.

port_id Specifies up to a maximum of eight ports.

--addport Adds a specified port to an existing team.

team_name Specifies the team to which a port will be added.

port_id Adds one or more ports to the team. The maximum number of ports that can be added to a team is eight.

--remport Removes a specified port from an existing team.

team_name Specifies the team from which a port will be removed.

port_id Removes one or more ports from an existing team. The maximum number of ports that can be removed from a team is eight.


teamB

--name Modifies the team’s primary interface name. This command applies to the failover or failback teaming modes only. By default, the system selects a primary interface which you can modify.

team_name Specifies the existing team name.

new_team_name Specifies the new team name.

--primary Modifies the team’s primary interface name. The command is applicable only to failover and failback modes. By default, the system selects a primary interface which the user can modify using this command.

team_name Specifies the teaming interface name where the primary interface resides..

port_id Specifies the port that is designated as the primary.

--xmit_policy Modifies the team’s policy for traffic load balancing. This command applies to the 802.3ad teaming mode only.

team_name Specifies the existing team name.

xmit_policy The transmit policy. Supported values include the following policies:

• 12 (Default) => (source MAC XOR destination MAC) % (team member count)

• 13_14 => ((source port XOR dest port)• XOR ((source IP XOR dest IP) AND 0xffff) % (team member count)

--remove Removes an existing teaming interface from the system.

team_name Specifies the teaming interface name to be removed from the system.

--vlanadd Configures a new VLAN ID on the team.

team_name Specifies the name of the teaming interface on which you want to add a VLAN.


vlan_name Specifies the VLAN name.

--vlanremove Removes an existing VLAN ID from the teaming interface.

team_name Specifies the name of the team from which you want to remove a VLAN.


--vlanedit Modifies the VLAN name attribute of the specified VLAN on the team.

team_name Specifies the name of the teaming interface on which you want to modify a VLAN.


vlan_name Specifies a different name for the VLAN.

--vlanlist Lists the configured VLANs on the teaming interface.

team_name Specifies the name of the team on which you want to list configured VLANs.


team B

--vlanquery Displays the VLAN information on the team.

team_name Specifies the name of the team for which you want to display the VLAN details.


Examples # bcu team --list----------------------------------------------Team Id Team modeMAC address ----------------------------------------------team-1 802.3ad 1:2:3:4:5:6team-2 failback 2:4:1:2:5:6team-3 failover 2:4:1:2:5:7----------------------------------------------

# bcu team --vlanlist team-1 --------------------------------Vlan id Vlan Name--------------------------------1 VLAN00013000 VLAN3000--------------------------------

# bcu team --vlanquery team-1 Teaming Information: Team Id: team-1 Team mode: 802.3ad MAC Address: 1:2:3:4:5:6 Mtu: 1500 Num of ports: 2 Member info: 1/0: Local Area Connection 2 (UP) 1/1: Local Area Connection 3 (DOWN) Xmit policy: L2 Statistics: Tx Bytes : 200 Rx Bytes : 100 Duration : 2:30:32 Status : Connected

# bcu team --vlanquery team-2 Teaming Information:

Team Id: team-2 Team mode: failback MAC Address: 2:4:1:2:5:6 Mtu: 1500 Num of ports: 2 Member info: 2/0: Local Area Connection 2 (UP) (Primary) (Active) 3/0: Local Area Connection 3 (UP) Statistics: Tx Bytes : 1200 Rx Bytes : 1100 Duration : 12:30:32 Status : Connected

# bcu team --addport ABC 1/0 1/1Added interface 1/0 to the Team ABCAdded interface 1/1 to the Team ABC


teamB

# bcu team --create ABC failover 1/0 1/1Team ABC created successfully

# bcu team --name ABC XYZTeam name ABC is changed to XYZ successfully

# bcu team --primary ABC 1/1Team ABC primary settings changed successfully

# bcu team --xmit_policy ABC l3_l4Team ABC transmit policy settings changed successfully

# bcu team --remport ABC 1/0Removed interface 1/0 from the Team ABC

# bcu vlan --query 1 team-1 vlan id: 1 vlan name: VLAN0001 vlan statistics: Tx Bytes: 200 Rx Bytes: 100 Duration: 2:30:32 Status: Connected

See Also None.


trunk B

trunkWhen trunking is enabled, multiple physical ports are trunked together to form a logical Fibre Channel port. The adapter ID can be any of the following:

• adapter index

• serial number

• adapter name

• hardware path

Synopsis bcu trunk --enable <ad_id>

bcu trunk --disable <ad_id>

bcu trunk --query <ad_id>

Description Enabling and disabling trunking for an adapter brings down all the adapter ports and then brings them up to apply the settings.

Operands When invoked without operands, this command displays the usage.

--enable Enables adapter trunking if currently disabled.

ad_id Specifies the ID of the adapter you want to enable.

--disable Disables adapter trunking if currently enabled.

ad_id Specifies the ID of the adapter you want to disable.

--query Queries or displays trunk attributes.

ad_id Specifies the ID of the adapter for which you want to query.

Example # bcu trunk --query 1Trunk state: OnlineLink state*: LinkupPort address: 010800Port id: 2/0Port state: EnabledLink state: LinkupDeskew value: 15 nsecPort id: 2/1Port state: EnabledLink state: LinkupDeskew value: 16 nsec

*Link state can be any one of the following:

Linkup The trunking negotiation is successful and the link is up.

Linkdown The link is down due to port disable, cable removal, or remote port down.

MisSpd The speed mismatch between the links corresponding to the trunked ports.

MisGrp The trunked ports are connected to different trunk groups on the switch.

MisMode The trunked ports have different configurations (for example, one trunked port has trunking enabled and another port has QoS and trunking enabled).


trunkB

# bcu trunk --query 2Trunk state: OfflineLink state: LinkDownPort address: --Port id: 2/0Port state: EnabledLink state: LinkDownDeskew value: --Port id: 2/1Port state: EnabledLink state: LinkDownDeskew value: --

See Also “adapter”, “port”


vport B

vportLists the commands that apply to a virtual port.

Synopsis bcu vport --create <port_id> <vpwwn> [-n <vnwwn>] [-s <sname>]

bcu vport --delete <port_id> <vpwwn>

bcu vport --query <port_id> <vpwwn>

bcu vport --stats <port_id> <vpwwn>

bcu vport --statsclr <port_id> <vpwwn>

Description The vport commands enable you to create and delete vports and display statistics about them.

NOTEThe vport commands are not supported on Solaris platforms.

Operands --create Adds a new V_Port in the base fabric. If the virtual fabric ID is not specified, the V_Port is created in the base fabric. FCP initiator mode is supported.

port_id Specifies the ID of the port for which you want to add a new V_Port.

vpwwn Adds the virtual port by its world wide name. The V_Port WWN is a required argument.

n vnwwn Adds the virtual port by the node’s world wide name for the V_Port. This is an optional argument. If not specified, the base port node’s world wide name is used.

s sname Adds the symbolic name for the virtual port. This is an optional argument.

--delete Deletes the specified V_Port. This deletes all associated objects, such as any associated login sessions and active I/O requests.

port_id Specifies the ID of the port for which you want to delete a V_Port.

vpwwn Deletes the virtual port by its world wide name. The V_Port WWN is a required argument.

--query Queries information about the V_Port. This provides the V_Port’s status and information associated with FC-4s. If no port WWN is specified, the information provided is for the base V_Port.

port_id Specifies the ID of the port for which you want to query V_Port information.

vpwwn Queries the virtual port by its world wide name. The V_Port WWN is a required argument.

--stats Displays the statistics that are associated with the V_Port. If you do not specify the port’s world wide name, the statistics listed are for the base V_Port.


vpwwn Displays the statistics for the virtual port by its world wide name. The V_Port WWN is a required argument.


vportB

--statsclr Clears the statistics that are associated with the V_Port. If you do not specify the port’s world wide name, the statistics listed are for the base V_Port.


vpwwn Clears the statistics for the virtual port by its world wide name. The V_Port WWN is a required argument.

Example bcu vport --query 1/0 10:00:00:05:1e:ae:e3:03Port wwn: 10:00:00:05:1e:ae:e3:03Node wwn: 20:00:00:05:1e:ae:e3:a4FC Addr: dd0504State: onlineRole: FCP initiator

bcu vport --stats hba5_port0fdisc sent: 15fdisc accepts: 7fdisc retries: 8fdisc timeouts: 2fdisc rsp err: 18fdisc acc bad: 9fdisc rejects: 3fdisc unknown: 0fdisc alloc waits: 6logo sent: 12logo accepts: 8logo rejects: 4logo rsp err: 4logo unknown rsp: 6logo alloc waits: 6no npiv: 7fab offline: 5fab online: 8fab cleanup: 9

bcu vport --statsclr hba5_port0vport stats cleared

See Also None



Appendix

C
HCM Troubleshooting
This appendix discusses known problems with HCM usability features and the workaround.

HCM tab navigation

Problem There are various places within the Host Connectivity Manager (HCM) where you cannot navigate without using the mouse on the KDE GUI on the Linux operating system. If you use the tab key to enter any of the fields listed below, you cannot exit the field without using the mouse.

The problem includes any of the following right pane properties:

Host > Properties fields

Host > Adapter fields

Adapter > Properties fields

Adapter > Ports fields

Port > Properties fields

Port > LPORT fields

Port > SFP fields

Port > POM fields

Base Port > Properties

Base Port > Remote Properties

Target > Properties

Target > LUNs

LUN > Properties

Master Log Details

Application Log Details

Workaround The Ctrl + Tab combination is the default in KDE GUI on Linux platforms. Therefore, the Ctrl + Tab combination is intercepted by the KDE shell. To navigate HCM using the keyboard, you must manually disable the Ctrl+ Tab shortcut.

259

HCM does not restrict duplicate WWNs if BCU is used to create V_PortsC

HCM does not restrict duplicate WWNs if BCU is used to create V_Ports

Problem The HCM GUI should post an error message for duplicate V_Ports (detected in the Vports.db file) and prompt the user to remove the duplicate when it detects duplicate world wide names (WWNs), but it does not. The HCM does not restrict duplicate WWNs when the BCU is used to create V_Ports.

Workaround Do not use the BCU for virtual port management, because it does not handle duplicate V_Port world wide names. Instead, use only the HCM GUI to manage V_Ports.

HCM returns incorrect time after using Microsoft timezone.exe tool to update Windows

Problem After using the Microsoft timezone.exe tool to update Windows, the operating system time and date information passed by Windows to Java is incorrect. This causes Java applications to fail, returning a time of GMT instead of the required local time.

Microsoft has made available two separate tools for customers to update their Operating Systems for the North America DST 2007 changes. The first is called TZEdit.exe and the second is called timezone.exe. The tool timezone.exe does not modify certain Windows Registry settings in a consistent way, which causes the Java time and date calculations to malfunction and incorrectly return a time of GMT by default.

Workaround In situations where the formal patch update, or Hotfix, from Windows cannot be applied, use TZEdit.exe in preference to timezone.exe. If you have already run the timezone.exe tool, your system will not be correctly updated. To correct this, follow the recommended procedure using TZEdit.exe. Please refer to http://support.microsoft.com/kb/914387 for details on how to configure daylight saving time for Microsoft Windows systems.



Appendix

D
Glossary and Acronyms
Available BB_Credit

A value used by a transmitter to determine permission to transmit frames and, if so, how many. The transmitter may transmit a frame when the available BB_Credit is greater than zero.

Available_receive_buffers

The current number of buffers in a receiving port that are available for receiving frames at link rate.

Bandwidth The maximum information-carrying capacity of a system.

Baud The encoded bit rate per second.

BCU Brocade Command Line Utility (BCU).

Beaconing A continuous signaling of error conditions on a LAN. Beaconing can occur either on the port or on one or both sides of the link (known as end-to-end beaconing).

Byte A group of eight data bits.

CEE Converged Enhanced Ethernet.

Class of service A frame delivery scheme exhibiting a specified set of delivery characteristics and attributes.

Credit Permission given by a receiving port to a sending port to send a specified number of frames.

DCB Data Center Bridging.

DCBX DCB Capability Exchange Protocol.

DCFM Data Center Fabric Manager

Domain_ID An eight-bit value that identifies a domain.

FCoE Fibre Channel over Ethernet.

FCP The Fibre Channel Protocol for mapping SCSI-3 operations to Fibre Channel.

FLOGI FC Fabric Login request.

FL_Port A switch port that is capable of arbitrated loop operations and is connected to one or more NL_Ports in an arbitrated loop topology.

FOS Fabric Operating System.

FPMA Fabric Provided MAC Address.

F_Port Fabric Port. A port on a switch to which an N_Port connects.

261

Glossary and AcronymsD

HBA The host bus adapter is a hardware facility in a node that provides an interface attachment.

HCM Host Connectivity Manager.

IOC I/O Controller.

ITL Initiator-Target-LUN. An Initiator Port (HBA controller) talks to one Target Port addressing one LUN.

LLDP Link Layer Discovery Protocol.

Lossless Ethernet MAC

A full duplex Ethernet MAC supporting at least 2.5KB jumbo frames and implementing extensions to avoid Ethernet frame loss resulting from congestion.

LUN Logical unit number. An address for an individual disk drive or virtual partition (volume) within a storage device.

LUN mapping A process that makes a LUN available to some hosts and unavailable to other hosts.

MAC Media Access Control.

MIB Management Information Base.

MTU Maximum Transfer Unit.

N_Port A node port (a Fibre Channel host or storage port in a fabric or point-to-point connection) that is assumed to be incapable of arbitrated loop operations.

NPIV N_Port ID Virtualization (NPIV) enables a single Fibre Channel protocol port to appear as multiple, distinct ports, providing separate port identification within the fabric for each operating system image behind the port (as if each operating system image had its own unique physical port).

Persistent binding A Fibre Channel (FC) host bus adapter (HBA) feature that enables you to permanently assign a system SCSI target ID to a specific FC device, even though the device’s ID on the FC loop may be different each time the FC loop initializes.

PFC Priority Flow Control.

Port A generic reference to an N_Port, NL_Port, F_Port, FL_Port, E_Port, or other type of Fibre Channel port.

Port name A 64-bit unique identifier assigned to each Fibre Channel port. The port name is communicated during the login and port discovery processes.

R_Port Remote port in a fabric. A remote port is a port that is physically separated from the adapter.

SNMP Simple network management protocol, defined for providing network management and monitoring functions.

SAN A storage area network configuration allowing multiple systems and storage devices to be interconnected using storage command protocols.

Switch_Name A 64-bit unique Fibre Channel name assigned to a switch.


Glossary and Acronyms D

TLV Type Length Value, where:

• Type is a numeric code that indicates the kind of field this part of the message represents.

• Length is the size of the value field, typically measured in bytes.

• Value is a variable-sized set of bytes that contain data for this part of the message.

Topology An interconnection scheme that allows multiple Fibre Channel ports to communicate. For example, point-to-point and arbitrated loop are Fibre Channel topologies.

VF Virtual Fabric.

VLAN Virtual Local Area Network.

WWNN World Wide Node Name. The unique name for any particular node in the fabric; for example, an HBA.

WWPN World Wide Port Name. The unique name for any particular port in the fabric. A WWNN can have multiple associated WWPNs.


Glossary and AcronymsD


Index

Aadapter command, 190, 255adapters

HBA models, 1supported operating systems, 11

advanced port configuration options, 47application log, 72auth command, 194Authentication Configuration dialog box, 127authentication, security, 27

Bbase port properties panel, 94beaconing

configuring using HCM, 82configuring using the BCU, 83

boot groups, 38boot LUN discovery, 4boot over SAN

description of, 38buffer credits, 28

CCEE

properties, 96CEE features

data center bridging capability exchange protocol (DCBX), 6

priority-based flow control (PFC), 6CNA

Ethernet features, 5FCoE features, 4product overview, 2throughput per port, 5

CNA expansion card port panel, 102CNA port statistics panel, 103

commandadapter, 190, 255auth, 194debug, 84, 203diag, 79, 205fabric, 216fcdiag, 80, 217fcpim, 221IOC, 228log, 46, 231lport, 232port, 239portlog, 84portlogclear, 84portlogct, 84rport, 248vport, 257

Configure Names dialog box, 106configuring

HCM logging level, 46interrupt control coalesce, 48NPIV, 55persistent binding, 32port speed, 31QoS using the BCU, 34queue depth, 41rate limiting using the BCU, 36security authentication using HCM, 26

DDCBCXP, 5debug command, 84, 203Define Name dialog box, 108diag command, 205diagnostics

running Ethernet test, 81running port-level test, 76, 77types of tests, 3


dialog boxAuthentication Configuration, 127Configure Names, 106Define Master Log Filter, 147Define Name, 108Event Properties, 115Historical Performance, 138Persistent Binding, 148Protocol Tests diagnostics, 155Security Authentication, 127Test Log Details, 170Update Driver, 171

discoverydescription of, 3setting up, 21setting up out-of-band, 22

driverintermediate, 10network, 10storage, 10

driver types, 10

Eenhanced transmission selection, 5enhanced transmission selection (ETS), 5Ethernet diagnostic test, running from HCM, 81Ethernet flow control, 5event categories, 146event logs, how to filter, 71Event Properties dialog box, 115event severities, 21events, master log, 70

Ffabric command, 216fcdiag command, 217FCoE features of CNA, 4fcpim command, 221FCP-IM profile, 36FC-SP, 4filtering event log entries, 71flow control, 6frame data field size

specifying using HCM, 31specifying using the BCU, 32

HHBA Properties panel, 100, 136HCM

authentication, 15, 16change password dialog box, 98features, 3logging level configuration, 46main window, 18master log icons, 21product icons, 20software overview, 2statistics monitoring, 3

Historical Performance dialog box, 138host management, remote, 3

Iintermediate driver, 10interrupt coalescing

FCoE, 4interrupt control coalesce

configuring using the GUI, 48interrupt moderation, 4IOC command, 228

Jjumbo frames, 5

Llaunching HCM

on Linux, 14on Solaris, 14on Windows, 13

Linux, launching HCM, 14LLDP, 6log

application, 72master log, 70test, 79

log command, 46, 231log off, 23login, how to skip, 14lport command, 232


MMAC addressing, 5management software components, 2Master Log Filter dialog box, 147Master Log properties, 70Master Log Properties tab, 146monitoring statistics, 3

Nname configuration, 49NetQueues, 7network driver, 10network priority, 6NPIV, 4NPIV configuration, 55N-Port trunking, 4

Ooperating systems supported on adapters, 11

Ppanel

CNA expansion card port, 102CNA expansion card port statistics, 103HBA Properties, 100, 136Port POM, 149Port SFP, 160Port Statistics, 152remote port properties, 145, 158

passwordhow to change, 15, 16

path time outspecifying using HCM, 35specifying using the BCU, 35

persistent binding, 4configuring using HCM, 32configuring using the BCU, 32

Persistent Binding dialog box, 148persistent binding, configuring, 32port 514, troubleshooting firewall issues, 74port command, 239

port configurationadvanced, 47basic options, 28opening the advanced dialog box, 47opening the basic dialog box, 29port speed, 31

port logging levelconfiguring using HCM, 30configuring using the BCU, 30

Port POM panel, 149port properties panel, 150Port SFP panel, 160port speed


Port Statistics panel, 152port test diagnostics, 135port-level diagnostic tests, running from HCM, 77port-level test

how to run using HCM, 76portlog command, 84portlogclear command, 84portlogct command, 84priority flow control (PFC), 6product overview, 2properties

CEE, 96importing in EFCM format, 53importing in FM format, 54

Protocol Tests diagnostics dialog box, 155

Qquality of service (QoS), 5quality of service (QoS), configuring, 34queue depth

configuring using the BCU, 41

Rrate limiting configuration, 36receive side scaling (RSS), 6remote host management, 3Remote port properties panel, 145, 158resetting statistics, 67rport command, 248


SSAN components, types listed in device tree, 8security authentication


Security Authentication dialog box, 127SFP

displaying using HCM, 83displaying using the BCU, 83

SFP management, 83skip login, 14Solaris, launching HCM, 14statistics, resetting, 67storage driver, 10supportSave

categories of information, 85collecting on a port crash event, 86collecting using a browser, 87collecting using HCM, 86collecting using the BCU, 87collection sources, 85configuring using the BCU, 87

syslog host, unblocking port 514, 74

Ttarget rate limiting, 3target rate limiting (TRL), 3TCP segmentation offload, 7teaming, 6test log details, 79Test Log Details dialog box, 170tree node pop-up menus, 7trunking

N-Port, 4

UUpdate Driver dialog box, 171

VVLAN, 7VLAN filtering, 7VLAN tagging, 7

VMware ESX 3.5 and 4.0troubleshooting firewall issues, 74

vport command, 257

WWindows, launching HCM application, 13WWN

adding a name, 54exporting, 52importing, 53removing, 52


Documents

Brocade Adapters v2.3.0.0 Admin Guide