Brocade Adapters v2.3.0.0 Admin Guide

53-1001923-02 30 November 2010
Brocade Adapters
Administrators Guide
Supporting CNA models 1741, 1020, 1010, 1007 Supporting 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 Headquarters Brocade Communications Systems, Inc. 130 Holger Way San Jose, CA 95134 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: info@brocade.com Asia-Pacific Headquarters Brocade Communications Systems China HK, Ltd. No. 1 Guanghua Road Chao Yang District Units 2718 and 2818 Beijing 100020, China Tel: +8610 6588 8888 Fax: +8610 6588 9999 E-mail: china-info@brocade.com Asia-Pacific Headquarters Brocade Communications Systems Co., Ltd. (Shenzhen WFOE) Citic Plaza No. 233 Tian He Road North Unit 1308 13th Floor Guangzhou, China Tel: +8620 3891 2000 Fax: +8620 3891 2111 E-mail: china-info@brocade.com
European Headquarters Brocade Communications Switzerland Srl Centre Swissair Tour B - 4me tage 29, Route de l'Aroport Case Postale 105 CH-1215 Genve 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 E-mail: emea-info@brocade.com
Document History
Title
Brocade Adapters Administrators Guide Supporting HBA models 825, 815, 425, 415 Brocade Adapters Administrators Guide Supporting CNA models 1020, 1010 Supporting HBA models 825, 815, 425, 415
Publication number Summary of changes

53-1000881-01 53-1001256-01 New document
Date
June 2008
September 2009 Updates to support new features: 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 Updates to support the Brocade adapters. May 2010
Brocade Adapters Administrators Guide 53-1001587-01 Supporting CNA models 1020, 1010 Supporting HBA models 825, 815, 425, 415, 53-1001923-01 Brocade Adapters Administrators Guide Supporting CNA models 1020, 1010 Supporting HBA models 825, 815, 804, 425, 415
September 2010 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 Updates to support the Brocade 1741 adapter. November 2010
Brocade Adapters Administrators Guide 53-1001923-02 Supporting CNA models 1741, 1020, 1010 Supporting HBA models 825, 815, 804, 425, 415
Brocade Adapters Administrators Guide 53-1001923-02
iii
iv
Contents
About This Document

In this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . xviii Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx FCoE switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Other 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Common HBA and CNA features. . . . . . . . . . . . . . . . . . . . . . . . . . 3 HBA-only features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 CNA 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
HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Launching the application on Windows platforms. . . . . . . . . . . 13 Launching the application on Linux platforms. . . . . . . . . . . . . . 14 Launching the application on Solaris platforms . . . . . . . . . . . . 14 Remember password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Skip login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Changing an HCM application password . . . . . . . . . . . . . . . . . . 15 Changing an HCM agent password. . . . . . . . . . . . . . . . . . . . . . . 16 HCM configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Restore Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 HCM main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Legend Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Event severity icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Setting up out-of-band discovery for an adapter . . . . . . . . . . . . 22 Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 3
Host Configuration
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Host security authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Configuring security authentication using HCM (Host and HBA)26 Configuring security authentication using the BCU . . . . . . . . . . 27 Buffer credits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Opening the Basic Port Configuration dialog box . . . . . . . . . . . 29 Port logging level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Ethernet logging level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Port speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Frame data field size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Persistent binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 FC Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 QoS (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Path time out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Target rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 FCP-IM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuring Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Pre-boot configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Boot image update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Driver update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Changing the HCM timeout value . . . . . . . . . . . . . . . . . . . . . . . . 42 PXE boot support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring PXE boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Virtual port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Virtual port restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Creating a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Deleting a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
vi
HCM logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Configuring the HCM logging level using HCM. . . . . . . . . . . . . . 46 Advanced port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Opening the Advanced Port Configuration dialog box . . . . . . . . 47 Interrupt Control Coalesce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Name configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Dual role changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Name validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Defining a name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Editing the name fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Adding name entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Removing a name entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Exporting the properties for a WWN . . . . . . . . . . . . . . . . . . . . . . 52 Importing the properties for a WWN. . . . . . . . . . . . . . . . . . . . . . 53 Importing duplicated names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Teaming configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Teaming modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Configuring a team from the host level . . . . . . . . . . . . . . . . . . . 57 Adding and editing a team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Changing the primary port in a team . . . . . . . . . . . . . . . . . . . . . 58 Removing a team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Displaying teaming statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Adding a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 VLAN configuration conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Editing a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Removing a VLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Displaying VLAN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Management application support for FCoE . . . . . . . . . . . . . . . . . . . 63
Chapter 4
Monitoring
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Performance monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Controlling the polling frequency rate. . . . . . . . . . . . . . . . . . . . . 66 Resetting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Real-time performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Historical performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Master log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Filtering event log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Syslog support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Opening the Syslog Server Configuration dialog box. . . . . . . . . 73 Registering a host server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Removing a host server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Syslog host configuration using VMware . . . . . . . . . . . . . . . . . . 74
vii
Chapter 5
Diagnostics
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Fibre Channel diagnostics using HCM . . . . . . . . . . . . . . . . . . . . . . . . 75 Running a hardware-level test using HCM . . . . . . . . . . . . . . . . . 76 Running a Fibre Channel protocol-level test using HCM . . . . . . 77 Displaying test log details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Fibre Channel diagnostics using the BCU . . . . . . . . . . . . . . . . . . . . . 79 diag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 fcdiag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Ethernet diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Running an Ethernet test using HCM . . . . . . . . . . . . . . . . . . . . . 81 Running an Ethernet test using the BCU . . . . . . . . . . . . . . . . . . 82 Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Configuring beaconing using HCM . . . . . . . . . . . . . . . . . . . . . . . 82 Configuring beaconing using the BCU . . . . . . . . . . . . . . . . . . . . 83 SFP management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Displaying SFP information using the BCU. . . . . . . . . . . . . . . . . 83 Displaying SFP information using HCM . . . . . . . . . . . . . . . . . . . 83 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 supportSave 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
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
ix
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
Appendix C Appendix D Index
HCM Troubleshooting Glossary and Acronyms
xi
xii
Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35
HCM Login dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Change HCM Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Change HCM Agent Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Restore Data dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Host Connectivity Manager main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Setup for Discovery dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Fibre Channel Security Protocol Configuration - host-level dialog box. . . . . . . . 26 Basic Port Configuration dialog box - Windows, Linux, and VMware . . . . . . . . . 29 Boot-over-SAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Update Driver dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Basic Port Configuration dialog box - PXE Boot tab. . . . . . . . . . . . . . . . . . . . . . . 43 Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Configure HCM Logging Levels dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Advanced Port Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Configure Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Teaming Configuration dialog box (with VLAN support) . . . . . . . . . . . . . . . . . . . 57 VLAN Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Add VLAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 VLAN Configuration dialog box with PORT VLAN . . . . . . . . . . . . . . . . . . . . . . . . . 61 VLAN Configuration conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Edit VLAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Remove VLAN dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Reset statistics warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Realtime Performance dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Historical Performance dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 HCM Application Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Hardware-level diagnostic tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Protocol-level diagnostic tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Test Log Details for Echo Test dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Ethernet Tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 SFP Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
xiii
xiv
Tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16
Brocade Fibre Channel HBA models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Brocade Fibre Channel CNA models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 HCM tree pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Adapter operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 HCM product icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 HCM Master Log icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Basic port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Advanced port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Statistics monitored by component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Master Log fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Hardware-level test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Fibre Channel diag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Fibre Channel diagnostic tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Ethernet Test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 supportSave categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 supportSave collection sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
xv
xvi
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.
xvii
Document conventions
This section describes text formatting conventions and important notice formats used in this document.
Text formatting
The narrative-text formatting conventions that are used are as follows: bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles Identifies CLI output Identifies command syntax examples
italic text
code text
For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.
Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.
NOTE
A note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data.
DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.
xviii
Key terms
For 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. .
Corporation
Microsoft Corporation Sun Microsystems, Inc. Red Hat, Inc. Novell, Inc. VMware
Referenced Trademarks and Products

Windows Server, Windows XP, Windows Vista Sun, Solaris Red Hat, Red Hat Network, Maximum RPM, Linux Undercover SuSE Enterprise Server (SLES), Linux VMware, ESX Server
Related documentation
This section lists additional Brocade and industry-specific documentation that you might find helpful.
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a user ID and password.
xix
Adapters
For 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 switch
For information on the Brocade FCoE switch for connecting stand-up CNAs, refer to the following publications:
Converged Enhanced Ethernet Command Reference Converged Enhanced Ethernet Administrators Guide Fabric OS Command Reference Manual Fabric OS Administrators Guide Data Center Fabric Manager (DCFM) Users Guide
SAN
For 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 information
For 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
Other industry resources

For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website: http://www.fibrechannel.org 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: documentation@brocade.com Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xxi
xxii
Chapter
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 adapters

Brocade 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.
TABLE 1
Model Number
Brocade 825 Brocade 815 Brocade 804
Brocade Fibre Channel HBA models

Description
Dual-port stand-up HBA with a per-port maximum of 8 Gbps using a 8 Gbps SFP.1 Single-port stand-up HBA with a maximum of 8 Gbps using an 8 Gbps SFP.1 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. Dual-port stand-up HBA with a per-port maximum of 4 Gbps using a 4 Gbps SFP.2 Single-port stand-up HBA with a maximum of 4 Gbps using a 4 Gbps SFP.2
Number of Ports
2 1 2
Brocade 425 Brocade 415

1 2
2 1
A 4 Gbps SFP installed in Brocade 815 or 825 HBAs allows 4, 2, or 1 Gbps speed only. An 8 Gbps SFP installed in Brocade 425 or 415 HBAs allows 2 or 4 Gbps speed only.
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.
Converged network adapters
Converged network adapters

Table 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.
TABLE 2
Model Number
1741M 1020 1010 1007
1 1
Brocade Fibre Channel CNA models

Port Speed
10 Gbps maximum 10 Gbps maximum 10 Gbps maximum 10 Gbps maximum
Number of Ports
2 2 1 2
Adapter Type
Expansion Stand-up Stand-up Expansion
The 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.
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. The 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.
NOTE
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.
HCM software
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. All 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.
NOTE
Common HBA and CNA features

HCM 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 limitingrelies 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.
HCM software
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 ports 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 SANprovides the ability to boot the host operating system from a boot device
located somewhere on the SAN instead of the hosts local disk or direct attached storage. Specifically, this boot device is a logical unit number (LUN) located on a storage device.
Fabric-based boot LUN discoveryallows the host to obtain boot LUN information from the
fabric zone database.
Persistent bindingenables you to permanently assign a system SCSI target ID to a specific

Fibre Channel device.
Interrupt Coalescingprovides 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 moderationimplements 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 features
Brocade 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
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 Administrators Guide.
CNA and networking features

Brocade 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.
NOTE
The jumbo frame size set for the network driver cannot be greater than the setting on the attached FCoE switch or the switch cannot accept jumbo frames.
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 software
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
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

You 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). HCM features display differently depending on the configuration. All drivers install for the CNA and only the storage driver installs for an HBA.
NOTE
TABLE 3
HCM tree pop-up menus

Pop-up menu feature
Refresh All View Name Display Start Polling Define Names Update Boot Image Update Driver Basic Port Configuration Persistent Binding Authentication Change Agent or HCM User Password Teaming (for Windows) Teaming VLAN HCM Logging Levels Syslog Statistics > Teaming Performance > Enable Historical Data Collection SupportSave Backup HCM Data Restore HCM Data, VLAN, and Team Tree > Copy | Search | Collapse All | Expand All Refresh View Name Display Start Polling Define Names Update Boot Image Basic Port Configuration Persistent Binding Diagnostics Enable FC Trunking Enable Adapter Authentication Change Agent or HCM User Password HCM Logging Levels Syslog Statistics > Port Performance > Enable Historical Data Collection SupportSave Backup HCM Data Restore HCM Data, VLAN, and Team Tree > Copy | Search | Collapse All | Expand All
SAN component
Host
Converged Network Adapter (CNA), 10 Gbps
TABLE 3
CEE Port
HCM tree pop-up menus (Continued)

Refresh View Name Display Start Polling Define Names Port Configuration > Basic | Advanced Diagnostics Beacon > Port | Link Change Agent or HCM User Password HCM Logging Levels Syslog Statistics > Port | CEE | FCP IM Module | Firmware Performance >Real-time Historical Statistics | Enable Historical Data Collection SupportSave Backup HCM Data Restore HCM Data, VLAN, and Team Tree > Copy | Search | Collapse All | Expand All Refresh View Name Display Start Polling Define Names Persistent Binding Virtual Port > Create | Delete Enable Port FC-SP > Authentication | Authentication Statistics Change Agent or HCM User Password HCM Logging Levels Syslog Statistics > Fabric | IOC | FCoE Backup HCM Data Restore HCM Data, VLAN, and Team Tree > Copy | Search | Collapse All | Expand All Refresh View Name Display Start Polling Define Names VLAN Configuration Change Agent or HCM User Password HCM Logging Levels Syslog Statistics > Eth | Eth IOC | VLAN Backup HCM Data Restore HCM Data, VLAN, and Team Tree > Copy | Search | Collapse All | Expand All
FCoE Port
Ethernet Port
Drivers
TABLE 3
HCM tree pop-up menus (Continued)

Refresh View Name Display Define Name Update Boot Image Basic Port Configuration Persistent Binding Diagnostics Authentication Change Agent or HCM User Password HCM Logging Levels Syslog Statistics > Port Statistics Tree > Copy | Search | Collapse All | Expand All Refresh Define Names Port Configuration > Basic | Advanced Virtual Port > Create | Delete Diagnostics FC-SP Enable Port Persistent Binding Statistics > Port | FCP IM Module | Fabric | IOC | QoS Tree > Copy | Search | Collapse All | Expand All Refresh Logical Port Statistics Tree > Copy | Search | Collapse All | Expand All Refresh Define Names Statistics > Target | FCP IM Tree > Copy | Search | Collapse All | Expand All
Brocade HBA 4 Gbps or 8 Gbps
HBA Port
Base Port
Device
Drivers
Three 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.
NOTE
The 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.
10
Adapter support
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 support
The HBAs and CNAs are supported on the operating systems listed in Table 4. HCM cannot be installed on Windows Server Core.
NOTE
TABLE 4
Adapter operating system support

Description of adapter Operating systems supported
Type of adapter
Host Bus Adapter 815 825 415 425 804
8 Gbps HBA, 1 port 8 Gbps HBA, 2 port 4 Gbps HBA, 1 port 4 Gbps HBA, 2 port 8 Gbps HBA dual port card for HP Blade Server
Linux, Windows, VMware, Solaris Linux, Windows, VMware, Solaris Linux, Windows, VMware, Solaris Linux, Windows, VMware, Solaris Linux, Windows, VMware
Converged Network Adapter 1741M 1007 1010 1020 10 Gbps CNA, 2 port 10 Gbps CNA, 2 port for IBM Blade Center 10 Gbps CNA, 1 port 10 Gbps CNA, 2 port Linux, Windows, VMware, Solaris Linux, Windows, VMware Linux, Windows, VMware, Solaris Linux, Windows, VMware, Solaris
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.
11
Adapter support
12
Chapter
Getting Started with HCM Software
In this chapter
HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HCM main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Legend Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 18 20 21 23
HCM software launch

The 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 platforms

After 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 launch
Launching the application on Linux platforms

After 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 platforms

After 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 password
The 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.
14
HCM software launch
Changing an HCM application password

You 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 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, 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. Both the user name and passwords are case-sensitive.
NOTE
15
HCM software launch
Changing an HCM agent password

You 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. Both the user name and passwords are case-sensitive.
NOTE
16
HCM software launch
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 Data
You 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.
NOTE
Use 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.
17
HCM main window
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 window

From 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.
18
HCM main window
4. 1. 6. 2.
3.
5.
1. Menu bar 2. Device tree window 3. Master Log 4. Online help 5. System information 6. Context view
FIGURE 5
Host Connectivity Manager main window
19
Legend Help menu
Legend Help menu

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

On 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

Remote Port (Initiator) online Remote Port (Initiator) offline Remote Port (Target) online Remote Port (Target) offline Ethernet Port Base Port (link up) Base Port (link down) Virtual Port (online) Virtual Port (offline)
Host (agent up)
Host (agent down)
HBA online HBA offline CNA offline Port (with SFP) link up Port (with SFP) link down Port (without SFP) link up Port (without SFP) link down Mezzanine card
LUN
Pre-boot configured device FCoE Port
Beacon status
20
Discovery
Event severity icons

Table 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.
TABLE 6
Icon
HCM Master Log icons

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.
Discovery
Discovery 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.
NOTE
The HCM application enables you to discover Brocade adapters, ports, virtual ports, remote ports, and LUNs using out-of-band discovery only.
21
Discovery
Setting up out-of-band discovery for an adapter

When 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.
NOTE
Click 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.
NOTE
If 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.
22
Logging off HCM
Logging off HCM

End 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.
23
Logging off HCM
24
Chapter
Host Configuration
In this chapter
Host security authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffer credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PXE boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HCM logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced port configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Name configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teaming configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management application support for FCoE. . . . . . . . . . . . . . . . . . . . . . . . . .
25 28 28 38 41 43 44 46 47 49 55 56 59 63
Host security authentication

Use 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. Security authentication is not supported on Solaris platforms.
NOTE
25
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.
NOTE
Fibre 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
26
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 messages 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 BCU

Enter 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.
27
Buffer credits
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 10 credits per port at 2 Gbps 20 credits per port at 4 Gbps 40 credits per port at 8 Gbps
Refer to the Extended Fabrics concepts and planning section of the Fabric OS Administrators 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. You 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 Administrators Guide.
NOTE
TABLE 7
Basic port configuration options

Configurable using HCM
Yes Yes Yes Yes
Port configuration parameter

Port logging level1 Configure speed Frame data field size Persistent Binding Note: The persistent binding option is available on Windows platforms only. QoS (HBA only) Path Time Out Note: Path time out value (pathtov) is valid for firmware version 2.0 and higher. It is not supported on the Solaris operating system.
Configurable using the BCU

Yes Yes Yes Yes
For more information

Port logging level Port speed Frame data field size Persistent binding
Yes Yes
Yes Yes
QoS (HBA only) Path time out
28
TABLE 7
Basic port configuration options (Continued)

Yes Yes Yes Yes Target rate limiting
Target Rate Limiting FCP-IM IO profile on

1
If an Ethernet port is selected, the Basic Port Configuration dialog displays an additional feature called Eth Logging Level.
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.
NOTE
There 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
29
Port logging level

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.
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. 3. Click Apply to apply the changes. 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 level

The 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. 2. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 3. Select a value from the Eth Logging Level list. Supported values are Log Critical, Log Error, Log Warning, Log Info, and Log Invalid. 4. Click Apply to apply the changes. 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.
30
Port speed
Port 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 HBAs speed and the ports 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

1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 2. Select a value from the Configured Speed list. 3. Click Apply to apply the changes. 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 size

Buffer 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

1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 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. 4. Click OK to close the window.
31
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. The 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.
NOTE
Persistent binding
Persistent 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.
The Persistent Binding check box is not available for Solaris agents.
NOTE
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.
32
FC Trunking
The 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.
33
For more information about basic trunk group configuration on a Brocade switch, refer to the Brocade Fabric OS Administrators 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:
NOTE
The 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)

The 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):
NOTE
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 Administrators 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.
34
You enable or disable QoS settings on ports with the portCfgQos command. Refer to the Fabric OS Administrators 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.
NOTE
You 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 out

With 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

1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 2. Type a value in the Path Time Out field. 3. Click OK to close the window.
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.
35
Target rate limiting

The 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 ports 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. 1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 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. 4. Click OK to close the window.
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:
NOTE
You 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 profile
FCP-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

36



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: 1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 2. Enable the FCP-IM IO profile on feature by clicking the corresponding check box. 3. Click OK to close the window.
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 port_id --profile_off port_id 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). Specifies the ID of the module on which you want to set the profiling to on. Sets the port IO profiling off. 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.
37
Boot over SAN
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 hosts 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. Various 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.
NOTE
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. 1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 2. Click the Boot-over-SAN tab. The Boot-over-SAN dialog box, shown in Figure 9, displays.
38
Boot over SAN
FIGURE 9
Boot-over-SAN dialog box
3. Click the BIOS Enable check box to enable Boot over SAN.
NOTE
Auto 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.
39
Boot over SAN
Pre-boot configuration
Any 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.
NOTE
For 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 adapters 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 Administrators Guide for more information about creating zones.
40
Driver update
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 update
The 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. The 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.
NOTE
41
Driver update
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 value

If a timeout error occurs during adapter driver installation, you can change the Host Connectivity Managers 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
42
PXE boot support
PXE boot support

A 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.
43
Virtual port configuration

Virtual 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 ports 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 port

You 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.
44
NOTE
By 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 port

If the maximum number of virtual ports have already been created, the option to create virtual ports using HCM is disabled.
NOTE
Pre-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.
45
HCM logging levels
HCM logging levels

You 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 HCM

1. 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.
46
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.
TABLE 8
Advanced port configuration options

Configurable using HCM
Yes Yes Yes
Port configuration parameter

Interrupt Control Coalesce Interrupt Control Latency Interrupt Control Delay
Configurable using the BCU

Yes Yes Yes
Opening the Advanced Port Configuration dialog box

1. 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 Coalesce

Interrupt 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. If 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:
NOTE
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.
47
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.

NOTE
Interrupt 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.
48
Name configuration
Name configuration
The 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. You 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:
NOTE
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 validation
Note 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.
49
Name configuration
Defining a name
The 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.
NOTE
The 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 fields

Only 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.
50
Name configuration
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 entries

You 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. 2. Select Configure > Names from the Host Connectivity Manager. 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
5. Click OK to close the window. The new component is added to the Name list.
51
Name configuration
Removing a name entry

The Remove functionality clears the name and description values of a selected detached WWN. 1. Select an HBA, an HBA port, or a Virtual Port, a CNA or a CEE 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 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. 5. Click OK to close the window.
Exporting the properties for a WWN

You can export the properties for a world wide name in .csv, *.properties, or .txt file format. 1. Select an HBA, an HBA port, or a Virtual Port, a CNA or a CEE 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 displays. 3. Select one of the following from the Display list:
Current Host All WWNs Only Nodes Only Ports Only L_Ports Only V_Ports Only Remote Ports
52
Name configuration
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. 6. Click OK to close the window.
Importing the properties for a WWN

You can import the properties for a world wide name in .csv, *.properties, or .txt file format. 1. 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 displays. 2. Select one of the following from the Display list:
Current Host All WWNs Only Nodes Only Ports Only Remote 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. 6. Click OK to close the window.
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. 3. Navigate to the location of the *.properties file from which you will import properties for the selected device.
53
Name configuration
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. 3. Navigate to the location of the *.properties file from which you will import properties for the selected device. 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 names

The Duplicated Names dialog box, shown in Figure 17, displays when you import a file with a duplicate name. 1. 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 displays. 2. Import a file with duplicate names in the Configure Names dialog box. The Duplicated Names dialog box displays.
54
NPIV
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.
NPIV
N-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.
NOTE
NPIV is not supported on Solaris platforms.
55
Teaming configuration
A 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). Windows 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:
NOTE
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 modes
CNA 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.
56
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. Link 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.
NOTE
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. Teaming is available on Windows platforms only.
NOTE
FIGURE 18
Teaming Configuration dialog box (with VLAN support)
57
Adding and editing a team

If 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 team

The 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 team
1. 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.
58
VLAN configuration
Displaying teaming statistics

1. Select a team from the Teams field. 2. Click the Statistics button beneath the Team Name field. The Teaming Statistics dialog box displays. SeeTeaming Statistics dialog box (CNA only) on page 169 for a description of teaming statistics fields.
VLAN configuration
A 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.
NOTE
VLAN configuration is a Windows-only feature. There are three types of VLANS:
Regular VLANA 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 VLANA 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).
NOTE
If 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 VLAN
You 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.
NOTE
After 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:
59
VLAN configuration
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.
60
VLAN configuration
VLAN configuration conflicts

Figure 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 VLAN
You 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. 1. From the Ethernet port level, select an Ethernet port from the device tree. 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.
61
VLAN configuration
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 VLAN
You 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. 1. From the Ethernet port level, select an Ethernet port from the device tree. 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.
62
Management application support for FCoE
Displaying VLAN statistics

VLAN 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. 1. From the Ethernet port level, select an Ethernet port from the device tree. 2. Click Statistics on the Teaming Configuration dialog box. The VLAN Statistics dialog box displays. SeeVLAN Statistics dialog box (CNA only) on page 180 for a description of VLAN statistics fields.

The 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.
63
64
Chapter
Monitoring
In this chapter
Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Real-time performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Historical performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Master log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syslog support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65 67 69 70 72 72
Performance monitoring
The 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
Component
Local host HBA HBA port
Statistics monitored by component

Statistics monitored
Teaming Port Port FCP IM Module Fabric IOC QoS Realtime Historical Port Port CEE FCP IM Module Firmware Realtime Historical
CNA CEE port
65
Performance monitoring
TABLE 9
Ethernet port
Statistics monitored by component (Continued)
Eth Eth IOC VLAN Realtime Historical Fabric IOC FCoE Logical port Realtime Historical Logical port Virtual port Realtime Historical Remote port > Target statistics, FCP IM statistics
FCoE port
Logical port and remote port
Virtual port
Device* *No statistics are available for LUNs
Controlling the polling frequency rate

The faster the polling rate, the more quickly the HCM GUI receives indications from the host. However, faster polling rates consume more of your systems 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.
66
Real-time performance data
Resetting statistics
1. Click the Reset button on any of the Statistics dialog boxes. A warning dialog box, shown in Figure 25, displays.
FIGURE 25
2. Click Yes.
Reset statistics warning
All of the statistics are reset to 0.

Real-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.
67
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.
68
Historical performance data
Historical performance data

To 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 DayOne sample of historical data is collected for 30 minutes duration. Last 1 WeekTwo samples of historical data is collected for one hours duration. Last 1 MonthFour 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.
69
Master log
Master log
Event 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. To 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.
NOTE
TABLE 10
Field
Filter button
Master Log fields

Description
Click to launch the Master Log Filter dialog box. Click to clear the master log filter option set. Displays a numbering sequence in ascending order. Displays the event severity (informational, minor, major, or critical). Displays the world wide name (WWN) or the media access control (MAC) address of the device on which the event occurred. Displays the category of event, based on one of the following categories: Adapter Port LPort RPort ITNIM Audit IOC Eth Port Displays the subcategory of the main category.
Clear Filter button Sr No column Severity column WWN/MAC column Category column
Subcategory column
70
Master log
TABLE 10
Field
Master Log fields (Continued)

Description
Displays a brief description of the event. Displays the date and time when the event occurred.
Description column Date/Time column
Filtering event log entries

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. 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.
NOTE
The 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.
71
Application log
Application log
The 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
Run-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.
NOTE
FIGURE 29
HCM Application Log
Syslog support
Syslog 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. VMware 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.
NOTE
72
Syslog support
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 server

You can register up to three Syslog destinations on managed Fabric OS devices. 1. Select Configure > Syslog from the main menu. 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 server

1. 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. 5. Click OK to close the dialog box.
73
Syslog support
Syslog host configuration using VMware

VMware 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
74
Chapter
Diagnostics
In this chapter
Fibre Channel diagnostics using HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Channel diagnostics using the BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SFP management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75 79 80 82 83 84 84
Fibre Channel diagnostics using HCM

The 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. When you invoke a test on an adapter, you can run diagnostics for one or both ports within the selected adapter.
NOTE
75
Running a hardware-level test using HCM

1. 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.
NOTE
Click 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.
76
TABLE 11
Memory test
Hardware-level test parameters

Parameter
None
Hardware-level test
Test Options
You can enable or disable this test. Regardless of test cycle set value, the Memory Test will run only once. Integer from 0 - 4,294,967,295. The default value is 8192. Default value is A5A5A5A5. The number of times the test runs. The default value is 10.
NOTE: During the test, IOC is disabled.

PCI loopback test Frame Count Data Pattern Test Cycle Port loopback test Subtest ID
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.
Internal External Serdes
Link Speed Frame Count Test Cycle Data Pattern (hexadecimal)
2, 4, and 8 Gbps Integer from 0 - 4,294,967,295. The default value is 8192. The number of times the test runs. The default value is 10. Default value is A5A5A5A5. 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.
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.
Running a Fibre Channel protocol-level test using HCM

There 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. 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 32, is displayed. 3. Click the FC Protocol Tests tab.
77
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.
78
Fibre Channel diagnostics using the BCU
Displaying test log details

1. 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 BCU

Diagnostic 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 commands
The 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. The sfpshow and beacon commands are not applicable for the Brocade 1007 CNA expansion card. or the Brocade 1741M mezzanine card.
NOTE
79
Ethernet diagnostics
TABLE 12
Command
beacon
Fibre Channel diag commands

Description
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. Tests the data path from the IOC to the desired network loopback point (internal, serdes, external) and back. Tests the adapters memory blocks. Checks the communication path between the host and the I/O Controller (IOC). Sends a health check message from the host to firmware through message queues that are memory-mapped over the PCI. Displays small form factor pluggable (SFP) information. Displays the temperature of the adapter.
loopback memtest pciloopback queuetest sfpshow tempshow
fcdiag commands
Fibre Channel diagnostics include the tests shown in Table 13. Refer to diag on page 205 for details about this command.
TABLE 13
Command
fcping fctraceroute fcecho linkbeacon scsitest
Fibre Channel diagnostic tests

Description
Determines the basic connectivity between the Fibre Channel network points and monitors and measures network latency. Reports on a SAN path, including node hops and latency data. Sends an FC Echo Extended Link Services (ELS) request to a remote port. Blinks the LED light of the remote port of the link. Tests the SCSI components.
The 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.
80
Windows 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.
NOTE
Running an Ethernet test using HCM

The following procedure explains how to run an Ethernet test. 1. Select an Ethernet port from the device tree. 2. Select Configure > Diagnostics from the main menu. 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.
81
Beaconing
TABLE 14
Ethernet Test parameters

Subtest ID Link Speed Frame Count Test Cycle Data Pattern (hexadecimal)
Ethernet loopback test
External Serdes
NOTE: For an External Loopback test, you must plug in the loopback connector.
10 Gbps Integer from 1-131072 (128K). The default value is 65536 (64K). The number of times the test runs. The default value is 10. Default value is A5A5A5A5.
Running an Ethernet test using the BCU

Enter the following command to test the Ethernet data path from the host to Serdes or external loopback based on your selection.
NOTE
Before 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.
Beaconing
Beaconing 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. Port beaconing is not supported on the Brocade 804 mezzanine card or the Brocade 1007 CNA expansion card. or the Brocade 1741M mezzanine card.
NOTE
Configuring beaconing using HCM

You 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.
82
SFP management
Configuring beaconing using the BCU

Enter 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 management
The 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 BCU

Enter 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

The 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.
NOTE
83
Debugging
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 ports frame log.
portlogctl
Enables or disables the portlog. Refer to debug on page 203 for details about these commands.
supportSave
The 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.
84
supportSave
Before 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.
NOTE
TABLE 15
supportSave categories
Captured information
Adapter model and serial number Adapter firmware version Host model and hardware revision All support information Adapter configuration data All operating system and adapter information needed to diagnose field issues Information about all adapters in the system Firmware and driver traces Syslog message logs Windows System Event log.evt file HCM GUI-related engineering logs Events Adapter configuration data Environment information
supportSave level
System (or Host)
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 sources

Table 16 lists the sources from which you can gather supportSave information. Master and Application logs are saved when supportSave is initiated through HCM, but not through the BCU.
NOTE
TABLE 16
supportSave collection sources

supportSave information collected
Collects driver-related logs, HCM agent information, and configuration files. Collects driver-related and HCM Agent logs and configuration files. Collects HCM application data, driver information, HCM Agent logs, and configuration files.
Source of supportSave information

BFA based supportSave1 Internet browser HCM
85
supportSave
TABLE 16
DCFM
1
supportSave collection sources (Continued)

supportSave information collected
Collects only driver-related logs and configuration files.
Source of supportSave information
Refer to supportSave collection using a command prompt on page 87 for more information.
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.
NOTE
If 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
2. Click OK to close the dialog box.
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.
86
supportSave
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.
NOTE
If 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 agents 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.
87
supportSave
88
Appendix
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 appendix
Persistent Binding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port POM Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Properties panel (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Tests dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QoS Statistics dialog box (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Real-time Performance Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . Remote Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SFP Properties panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . Target Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teaming Configuration dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . Teaming Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Log Details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Deletion dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLAN Configuration dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . VLAN configuration - Add VLAN dialog box (CNA only) . . . . . . . . . . . . . . . . VLAN configuration - Edit VLAN dialog box (CNA only) . . . . . . . . . . . . . . . . VLAN Statistics dialog box (CNA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148 149 150 152 155 156 157 158 159 160 162 163 167 169 170 172 173 174 175 177 178 179 180
90
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 box

1. Select an HBA port from the device tree. 2. Select Configure > FC_SP > Authentication Statistics from the Host Connectivity Manager.
Fields and components

Field
Date Failures Successes Tx Auth Rjts Tx Auth Negs Tx Auth Dones Tx DHCHAP Replies Tx DHCHAP Challenges Tx DHCHAP Successes Rx Auth Rjts Rx Auth Negs Rx Auth Dones Rx DHCHAP Challenges Rx DHCHAP Replies Rx DHCHAP Successes
Description
The date the statistics were run. The number of times security authentication failed. The number of times security authentication succeeded. The number of rejected transmitted Fibre Channel authentication attempts. The number of transmitted Fibre Channel authentication negotiation attempts. The number of completed Fibre Channel authentication negotiation attempts. The number of transmitted DH-CHAP replies. The number of transmitted DH-CHAP challenge attempts. The number of times a transmitted Fibre Channel authentication attempt was successful. The number of rejected received Fibre Channel authentication attempts. The number of received Fibre Channel authentication negotiation attempts. The number of completed received Fibre Channel authentication attempts. The number of received DH-CHAP challenge attempts. The number of received DH-CHAP replies. The number of times a received DH-CHAP challenge was successful.
91
Using the dialog box

Refer 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
92
Backup dialog box
Backup dialog box

The Backup dialog box allows you to create a backup of data and configuration files.

Select any device from the device tree and select Tool > Backup Data from the Host Connectivity Manager.

Field
Output Directory text box Browse button Start Backup button Close button
Description
Enter the location of the directory in which you want to back up the data and configuration files. Click to browse to the location of the backup directory. Click to instruct the system to back up the data and configuration files to the designated location. Click to close and exit the Backup dialog box.
93
Base Port Properties panel
Base Port Properties panel

The Base Port Properties panel enables you to display the properties that are associated with the base port.
Opening the panel

1. From the device tree, select a base port. 2. In the right pane, click the Base Port Properties tab.

Field
Base Port Fabric Name FC Address FPMA MAC Address Node WWN Port WWN Roles State Switch IP Address Symbolic Name
Description
Indicates whether the port is a base port (true or false). The name of the Fabric associated with the base port. The Fibre Channel address of the base port. The Fabric-Provided Ethernet MAC address created using the FC_ID assigned by the Fabric. The world wide name of the device. The world wide name of the base port. The role of the base port; for example, FCP Initiator. Indicates whether the base port is online or offline. The IP address of the switch. The symbolic name associated with the base port.
94
CEE properties panel (CNA only)
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 panel

1. Select a CEE port in the device tree. 2. Click the CEE tab in the right pane.

Field
% Bandwidth CEE Status DCBCXP version Ethernet Link Layer CoS FCoE CoS FCoE Logical Link Status Network Priority Priority Group ID
Description
The bandwidth percentage for a given priority group. The status of the CEE configuration; for example, Active. The DCBCXP version type; for example, CEE. Specifies a cost of service (CoS) priority value between 0 (signifying best effort) and 7 (signifying real-time data) to differentiate traffic. The Fibre Channel Class of Service that specifies a priority value. The operational status of the FCoE logical link; for example, Up or Down. The network priority for communication between nodes. 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. Indicates whether priority flow control is enabled or disabled. Specifies an iSCSI cost of service (CoS) priority value between 0 (signifying best effort) and 7 (signifying real-time data) to differentiate traffic.
Priority Flow Control iSCSI CoS
95
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.

1. From the device tree, select a physical port of a CNA. 2. Select Monitor > Statistics > CEE Statistics from the Host Connectivity Manager.

Field
Keep running data checkbox Polling frequency in seconds text box Start polling button Reset button LLDP Tx Frames LLDP Rx Frames invalid LLDP Rx Frames new LLDP Rx Frames
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the CEE statistics. Click to reset all of the statistics to 0. Transmits the local network element (NE) data on a per-link basis to the remote NE at the other end of the link. The number of invalid received frames for LLDP. The number of new received frames for LLDP. 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. The number of unrecognized type-length-value (TLV) elements for LLDP. The number of type-length-value (TLV) elements for LLDP that were shut down. The number of LLDP frames that timed out between the local and remote ends of the link. The number of Converged Enhanced Ethernet (CEE) links that are up. The number of Converged Enhanced Ethernet (CEE) links that are down. The number of type-length-value (TLV) elements received for DCBX. The number of invalid type-length-value (TLV) elements received for DCBX. The number of DCBX LLDP frames that were not transmitted because of errors. The number of type-length-value (TLV) errors received for DCBX features.
LLDP Rx unrecognized TLVs LLDP Rx shutdown TLVs LLDP remote info aged DCBX phy link ups DCBX phy link downs DCBX Rx TLVs DCBX Rx TLVs invalid DCBX control TLV errors DCBX feature TLV errors
96
Field
DCBX new CEE cfg rcvd CEE status down CEE status up CEE hw cfg changed CEE invalid cfg
Description
The number of new configurations events received on the physical port of the CNA. The number of status down events on the physical port of the CNA. The number of status up events on the physical port of the CNA. The number of times the physical port of the CNA changed. The number of invalid configurations events received on the physical port of the CNA.
97

The Change HCM Password dialog box enables you to change an existing password for the application.

Select Configure > Change HCM Password from the Host Connectivity Manager.

Field
User Name Old password New password Confirm New password
Description
Type your user name. Type your existing password. Type a new password. Confirm your new password by retyping it.

Refer to the following topic for specific procedures using this dialog box:
98

The Change HCM Agent Password dialog box enables you to change an existing password for the host.

Select Configure > Change Password > Change Agent Password from the Host Connectivity Manager.

Field
Host Name User Name Old password New password Confirm New password
Description
Displays the IP address of the host. Type your user name. Type your existing password. Type a new password. Confirm your new password by retyping it.

99
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 panel

1. Select a CNA in the device tree. 2. Click the Properties tab in the right pane.

Field
CNA Parameters MAC Address Name Operating Status Manufacturer Model Description Max Speed Supported # of Ports OEM Info Card Type Hardware Path Serial # Temperature The adapters media access control address. The name representing the adapter. Whether the CNA is enabled or disabled. The company that manufactured the CNA. The description of the CNA. The maximum speed supported on the CNA, which is 10 Gbps. The number of ports associated with the CNA. Information about the original equipment manufacturer, if applicable. The adapter card type; for example, CNA. The hardware path of the CNA. The serial number of the CNA. The temperature of the CNA, both in Celsius and Fahrenheit.
Description
Driver Parameters It 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 Driver Version Driver Name Driver Version Firmware Parameters Firmware Version BIOS Version PCI Registers Vendor ID The identifier of the PCI Registers vendor. The version level of the firmware. The version level of the BIOS. The name of the host adapter driver. The version level of the host adapter driver. The name of the second driver, if applicable. The version level of the second driver, if applicable.
100
Field
Device ID Subsystem Vendor ID Current # of Lanes PCIe Generation Initial Negotiated # of Lanes OEM VPD Information (HP only) OEM Part # EDC MDC Misc Serial # Product Description IBM Information EC level FRU #
Description
The device ID of the PCI Register. The ID of the PCI subsystem vendor. The number of PCI lanes, in Gbps, each way between the PCI slot and the adapter. The number of times the PCI Register is generated. The set number of PCI lanes that were initially negotiated.
The name of the OEM (HP) The part number of the adapter, preceded by HP. For example, HP:AXXXXA. The identifier for the EDC type adapter. The identifier for the MDC type adapter. Miscellaneous information pertaining to the HP adapter. The serial number of the adapter, preceded by HP. For example, hp:aabbccddsss. An HP-specific description of the adapter.
The adapters EC level (IBM only). The adapters FRU number (IBM only).
101
CNA Port panel
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 panel

1. Select a CNA port in the device tree. 2. Click the Properties tab in the right pane.

Field
Port # Port WWN Node WWN Physical Port Type Name Local Port MAC Media CEE State CEE Error Reason
Description
The CNA expansion card ports number (0 or 1). The CNA expansion card ports world wide name. The CNA expansion cards world wide name. The type of port; for example, CNA. The CNA expansion card ports name. The media access control number assigned locally. The type of media; for example, mezzanine. The state of the converged ethernet (whether it is online or offline). The reason for the CEE error; for example, the physical link is down.
102
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.

1. Select a CNA port from the device tree. 2. Select Monitor > Statistics > Port Statistics from the Host Connectivity Manager.

Field
Keep running data checkbox Polling frequency in seconds text box Start polling button Reset button Date Port WWN Seconds since stats is reset Frames 64 bytes Frames 65-127 bytes Frames 128-255 bytes Frames 256-511 bytes Frames 512-1023 bytes Frames 1024-1518 bytes Frames 1519-1522 bytes Tx bytes Tx packets Tx multicast packets Tx broadcast packets Tx control frame Tx drops Tx jabber Tx FCS error Tx fragments
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the V_Port statistics. Click to reset all of the statistics to 0. The date and time of the most recent reset. The world wide name of the port about which statistics are displayed. The number of seconds since the port statistics reset (the counter returns to 0). The number of 64-byte frames. The number of frames with 65-127 bytes. The number of frames with 128-255 bytes. The number of frames with 256-511 bytes. The number of frames with 512-1023 bytes. The number of frames with 1024-1518 bytes. The number of frames with 1519-1522 bytes. The number of transmitted bytes. The number of transmitted packets. The number of transmitted multicast packets. The number of transmitted broadcast packets. The transmitted control frames. The number of transmitted frames dropped. The number of transmitted jabbers (illegal packet length). The number of frame check sequence (FCS) errors transmitted, which indicate that frames of data are corrupted. The number of transmitted frame packets that are fragmented.
103
Field
Rx bytes Rx packets Rx multicast packets Rx broadcast packets Rx control frames Rx unknown opcode Rx drops Rx jabber
Description
The number of received bytes. The number of received packets. The number of received multicast packets. The number of received broadcast packets. The number of received control frames, which assist in data frame delivery. The number of unknown opcode frames received. The number of received packet drops. 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). The number of frames that have a integral of 64 to 1518 length and contain a frame check sequence (FCS) error. The number of packets received with alignment errors. The number of frames received in which the 802.3 length field did not match the number of data bytes actually received. The number of frames received with at least one invalid data symbol. The number of received frames that are less than 64 bytes in length and contain an invalid FCS (includes integral and non-integral lengths). The number of received pauses. The number of received zero pauses. The number of transmitted pauses. The number of transmitted zero pauses. 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. The number of times a zero pause control frame was received by a congested FCoE port. 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. The number of times a zero pause control frame was transmitted to a congested FCoE port. The number of received iSCSI pauses. The number of received iSCSI zero pauses. The number of transmitted iSCSI pauses. The number of transmitted iSCSI zero pauses.
Rx FCS errors Rx alignment errors Rx frame len errors Rx code errors Rx fragments
Rx pause Rx zero pause Tx pause Tx zero pause Rx FCoE pause
Rx FCoE zero pause Tx FCoE pause
Tx FCoE zero pause Rx iSCSI pause Rx iSCSI zero pause Tx iSCSI pause Tx iSCSI zero pause
104

Port Statistics dialog box Controlling the polling frequency rate Resetting statistics Performance monitoring
105

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.

1. Select any device from the device tree. 2. Select Configure > Names from the Host Connectivity Manager.

Field
Display list Name
Description
Select a discovered host from the list. Current Host is the default. 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. The world wide name for all configured devices.
WWN/MAC
NOTE: You can also search for a name by typing the world wide name into the text box and clicking OK.
Operational Status Type Description Remove button Import Export Add button DCFM/FM format list Fix Duplicates button The operational status of the WWN/MAC (for example, Discovered). The type of device; for example, Node or Port. Displays a description of the device. Select a device to highlight it, then click the Remove button to remove the discovered device from the list. Click to import properties from a properties file for a selected device. Click to save properties to a properties file for a selected device. For undiscovered devices, type in the name of the ports name or the WWN and click the Add button to add it to the Display list. Select from the list to import properties in DCFM (Data Center Fabric Manager) / FM (Fabric Manager) or EFCM format. Click to fix any duplicate names.
106

Name configuration Adding name entries Removing a name entry Exporting the properties for a WWN Importing the properties for a WWN
107

The Define Name dialog box enables you to assign a name to an existing world wide name.

1. Right-click on an HBA, a CNA or a port in the device tree.
NOTE
You can not define a name on an FCoE port or an Ethernet port. 2. Type a name that represents the adapter or port.
NOTE
The 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
WWN/MAC Name Type Description
Description
The world wide name for the device. Enter a meaningful name for the device. The type of device; for example, Node or Port. Enter a description of the device.

108

The Duplicated Names dialog box enables you to display configured names that are redundant.

The Duplicated Names dialog box displays when you import a file with a duplicate name. 1. 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 displays. 2. Import a file with duplicate names in the Configure Names dialog box. The Duplicated Names dialog box displays.

Field
Append unique suffix for all repetitive names button User/Administrator will manually fix button Name WWN/MAC Operational Status Type Description
Description
Click to automatically add an incremental number to a duplicate name. Click if you want to manually fix a duplicate name. The port number with which the duplicated name is associated. The world wide name or media access control address with which the duplicated name is associated. The operational status of the duplicate WWN (for example, Discovered). The type of device; for example, Node or Port. A description of the duplicate name.

109
Eth IOC Statistics dialog box (CNA only)
Eth IOC Statistics dialog box (CNA only)

The Eth IOC Statistics dialog box enables you to display statistical information related to the Ethernet IOC.

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

Field
Keep running data checkbox Polling frequency in seconds text box Start polling button Reset button Date Mailbox Interrupts Enable Events Disable Events Heartbeat Failures Firmware Boots Stats Timeouts
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the Ethernet IOC statistics. Click to reset all of the statistics to 0. The date the Eth IOC statistics were run. The number of mailbox interrupts that occurred on the Ethernet IOC. The number of Enable events on the Ethernet IOC. The number of Disable events on the Ethernet IOC. The number of heartbeat failures on the Ethernet IOC. The number of firmware boots on the Ethernet IOC. The number of times the Eth IOC statistics timed out.

Adding a VLAN Editing a VLAN Removing a VLAN
110
Ethernet Port Properties panel (CNA only)
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 panel

1. Select an Ethernet port in the device tree. 2. Click the Properties tab in the right pane.

Field
Eth Port Information Eth Dev Port Type Current MAC address Factory MAC IOC ID Hardware Path State Eth Log Level PXE Boot Information PXE Boot Enabled VLAN ID Whether Preboot Execution Environment (PXE) is enabled. The VLAN identifier The name of the Ethernet device. The port type; for example, Ethernet. The current MAC address of the Ethernet port. The factory-configured MAC address for the CNA. The IOC ID of the Ethernet port. The hardware path of the Ethernet port. The status of the Ethernet port; for example, Linkup. The status of the Ethernet log; for example, Log Critical.
Description
111
Eth Port Statistics dialog box (CNA only)

The Eth Statistics dialog box enables you to display statistical information related to the Ethernet port.

1. Select an Ethernet port from the device tree. 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
Keep running data checkbox Polling frequency in seconds text box Start polling button Reset button Date TxF0 ucast octets TxF0 ucast vlan TxF0 mcast octets TxF0 mcast packets TxF0 ucast packets TxF0 mcast vlan TxF0 bcast octets TxF0 bcast packets TxF0 bcast vlan TxF0 errors TxF0 vlan filtered frames TxF0 SA check filtered frames RxF0 ucast octets RxF0 ucast packets RxF0 ucast vlan RxF0 mcast octets RxF0 mcast packets
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the Ethernet IOC statistics. Click to reset all of the statistics to 0. The date the Eth statistics were run. The number of transmitted unicast octets. The number of transmitted unicast VLANs. The number of transmitted multicast octets. The number of transmitted multicast frame packets. The number of transmitted unicast frame packets. The number of transmitted multicast VLANs. The number of transmitted broadcast octets. The number of transmitted broadcast frame packets. The number of transmitted broadcast VLANs. The number of transmitted errors. The number of transmitted VLAN filters. The number of transmitted filter MAC source addresses. The number of received unicast octets. The number of received unicast frames. The number of received unicast VLANs. The number of received multicast octets. The number of received multicast frames.
112
Field
RxF0 mcast vlan RxF0 bcast octets RxF0 bcast packets RxF0 bcast vlan RxF0 frame drops Rx completed Rx dropped Rx alloc failed Rx checksum errors Rx mac errors Rx small packets Rx large packets Rx lro Rx lro flush Rx low rxbuf count Tx ls04 Tx ls06 Tx ls0 Errors Tx tcp cs0 Tx ip4 cso Tx udp cs0 Tx checksum help Tx checksum help errors Tx map errors Tx res drops Tx small packets Tx large packets Tx out of wis count Tx wi waitq count Tx ctxt waitq count Tx max nbs per nbl CEE toggle count mbox intr disables
Description
The number of received multicast VLANs. The number of received broadcast octets The number of received broadcast frames. The number of received broadcast VLANs. The number of received frame drops. The number of received frames that completed. The number of received frames that dropped. The number of received allocation fails. The number of received checksum errors. The number of received mac errors. The number of small packets received by the port. The number of large packets received by the port. The number of packets received on the IRO server. The number of packets flushed from the IRO server. The number of received buffers. The number of transmitted IPv4 packets. The number of transmitted IPv6 packets. The number of transmitted IPv6 packet errors. The number of transmitted TCP packets with CS0 (the default priority class). The number of transmitted IP4 packets with CSO (the default priority class). The number of transmitted UDP packets with CS0 (the default priority class). Transmitted checksum help. The number of transmitted checksum help errors. The number of transmitted map errors. Transmitted packets that were dropped but are now resumed. The number of small transmitted packets. The number of large transmitted packets. The total number of transmitted packets with an out of wis route status. The total number of transmitted packets with a waitq route status. The total number of transmitted packets with a waitq route status saved to a text file (.ctxt). The maximum number of transmitted packets on the NBS console server. The number of CEE toggles. The number of Mbox interrupts that are disabled.
113
Field
Link toggle count mbox intr enables Tx stops Tx wakeups Tx res stops Tx hardware stop Rx schedules Rx hardware stops Rx resumes Rx rss config count Hardware stats updates
Description
The number of link toggles. The number of Mbox interrupts that are enabled. The number of stopped transmitted packets. The number of times stopped transmitted packets wake up. The number of stopped receive packets that are resumed. The number of stopped transmitted hardware packets. The schedules for receive packets. The number of stopped receive hardware packets. The number of resumed receive packets. The number of receive packets with an RSS configuration. The number of hardware statistics updates.
114
Event Properties dialog box
Event Properties dialog box

The Event Properties dialog box displays the properties associated with a selected event from the Master Log.

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

Field
Date/Time Time Severity WWN/MAC Event ID Category Description Root Cause
Description
The date when the event occurred. The time when the event occurred. The event severity (informational, minor, major, or critical). The world wide name (WWN) or media access control (MAC) of the device on which the event occurred. An identifier that corresponds to the event. The category of event; for example, Rport or ITNIM. A brief description of the event. The root cause of the event.

Master log Application log Filtering event log entries
115
Fabric Statistics dialog box (HBA only)
Fabric Statistics dialog box (HBA only)

The Fabric Statistics dialog box enables you to view statistics on a selected Fabric.

1. Select an HBA port from the device list. 2. Select Monitor > Statistics > Fabric Statistics from the Host Connectivity Manager.

Field
Keep running data check box Polling frequency in seconds text box Start polling button Reset button Num FLOGIs sent FLOGI response errors FLOGI accept errors FLOGI accepts received FLOGI rejects received Unknown responses for FLOGI Allocation waits prior to sending FLOGI FLOGIs received Incoming FLOGIs rejected Internal Fabric online notification sent to other modules Internal Fabric offline notification sent to other modules
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the V_Port statistics. Click to reset all of the statistics to 0. The number of Fabric logins sent. The number of Fabric login response errors. The number of times Fabric login attempts are accepted. The number of times Fabric logins are received. The number of times Fabric login attempts are rejected. The number of unknown Fabric login responses. The number of delayed Fabric login allocations. The number of times Fabric logins are received. The number of times Fabric logins are rejected. The number of internal notifications for Fabrics that are online that are sent to other modules. The number of internal notifications for Fabrics that are offline that are sent to other modules.

116
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 panel

Select an FCoE port in the device tree and click the Properties tab in the right pane.

Field
FCoE Port information State FCoE MAC Port WWN Node WWN Supported Classes Symbolic Name IOC ID Hardware Path Port Log FCoE information Priorities PG ID Bandwidth Fabric Parameters Port Type FC Address Local Port MAC Configured Port State Operating Port State Operating Speed Max Speed Supported Frame Data Field Size # of Lports The port type; for example, N_Port. The FCoE ports Fibre Channel address. The media access control address of the local port. Indicates whether the FCoE port is enabled or disabled. Indicates whether the port is online or offline. The configured speed of the FCoE port. The maximum speed that is supported on the FCoE port. The frame size, in bytes, of the FCoE port. The number of logical ports. Lists the available priorities. The priority group ID. Values are 0-7 and 15 (strict priority). The bandwidth percentage for a given priority group. The state of the FCoE port (online or offline). The FCoE ports media access control address. The FCoE ports world wide name. The nodes world wide name. The classes supported on the FCoE port; for example, Class2 and Class3. The nickname for the selected FCoE port. The IO Controller ID. The hardware path of the FCoE port. Indicates whether the port log is enabled or disabled.
Description
Operating Parameters Note: Beacon State and Link Beacon State are not supported on the Brocade 1007 CNA expansion card. Beacon State Indicates whether beaconing is turned on.
117
Field
Link Beacon State Path Time Out Logging Level Persistent Binding Target Rate Limit Default Rate Limit FC-SP Parameters Authentication Status Algorithm Group Error Status
Description
Indicates whether link beaconing is turned on. 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. The port logging level. Values include Log Critical, Log Error, Log Warning, and Log Info. Indicates whether persistent binding is turned on or off. Indicates that target rate limiting is enabled or disabled. The default rate limit, which is not applicable, because target rate limiting is not supported on the FCoE port.
Indicates whether FC-SP authentication is on or off. The status of FC-SP authentication. The configured authentication algorithm. The DH group, which is DH-null (group 0) which is the only option. The health status of the Fibre Channel Security Protocol parameters.
Using the panel

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

1. 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
Keep running data checkbox Polling frequency in seconds text box Start polling button Reset button Date Seconds since stats reset CEE link up CEE link down FIP link up FIP link down FIP failures Invalid mac assignments Vlan requests Vlan notifications Vlan notification errors Vlan request timeouts Vlan invalids Discovery requests Discovery responses
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the FCoE statistics. Click to reset all of the statistics to 0. The date the FCoE statistics were run. The number of seconds since the FCoE statistics were last reset. The number of Converged Enhanced Ethernet (CEE) links that are up. The number of CEE links that are down. The number of links with FCoE Initialization Protocol (FIP) that are up. The number of links with FCoE Initialization Protocol (FIP) that are down. The number of links with FCoE Initialization Protocol (FIP) requests that failed. The number of invalid media access control (MAC) assignments. The number of virtual LAN (VLAN) requests. The number of VLAN notifications. The number of virtual LAN (VLAN) notification errors. The number of times a virtual LAN (VLAN) request times out. The number of invalid virtual LAN requests. The number of discovery requests. The number of discovery responses.
119
Field
Discovery error frames Discovery unsolicited Discovery timeouts Discovery FCF not avail FIP link service req. unsupp. FIP link service req. errors FIP logos received Clear virtual link requests FIP operation unsupp. Tx FCoE unicast frames Tx FCoE unicast vlan frames FIP untagged frames Tx FCoE unicast octets Tx FCoE multicast vlan frames Tx FCoE multicast octets Tx FCoE multicast frames Tx FCoE broadcast frames Tx FCoE broadcast vlan frames Tx FCoE broadcast octets Tx timeouts Transmit parity err Transmit FID parity err Rx FCoE unicast octets Rx FCoE unicast frames Rx FCoE unicast vlan frames Rx FCoE multicast octets Rx FCoE multicast frames Rx FCoE multicast vlan frames Rx FCoE broadcast octets Rx FCoE broadcast frames Rx FCoE broadcast vlan frames
Description
The number error frames during discovery. The number of unsolicited discovery requests. The number of timeouts during discovery. The number of FCoE Forwarder (FCF) The number of unsupported FIP link service requests. The number of FIP link service request errors. The number of FIP logos received. The number of clear virtual link requests (needed to terminate virtual links to other ports). The number of FCoE Initialization Protocol (FIP) operations that are unsupported. The number of transmitted FCoE unicast frames. The number of transmitted FCoE unicast VLANs frames. The number of FCoE Initialization Protocol (FIP) frames that are untagged. The number of transmitted FCoE unicast octets. The number of transmitted FCoE multicast VLAN frames. The number of transmitted FCoE multicast octets. The number of transmitted FCoE multicast frames. The number of transmitted FCoE broadcast frames. The number of transmitted FCoE broadcast VLAN frames. The number of transmitted FCoE broadcast octets. The number of transmissions that timed out. The number of transmitted parity errors. The number of transmitted FCoE Initialization Protocol (FIP) parity errors. The number of received FCoE unicast octets. The number of received FCoE unicast frames. The number of received FCoE unicast VLANs. The number of received FCoE multicast octets. The number of received FCoE multicast frames. The number of received FCoE multicast VLAN frames. The number of received FCoE broadcast octets. The number of received FCoE broadcast frames. The number of received FCoE brocadcast VLAN frames.
120
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.

Select 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
Date num rport onlines num rport offlines num prli sent out num fcxp alloc waits num prli rsp errors num prli rsp accepts rport is an initiator prli rsp parsing errors num prli rsp rejects num timeouts detected num sler notification from bfa Total IO Requests Data in-bound requests Data out-bound requests Total IO completions Write data transfered in bytes Read data transfered in bytes Slowpath IO completions IO underrun IO overrun IO Request-Q wait IO Request-Q wait done No free IO tag
Description
The date and time of the most recent reset. The number of online R_Ports. The number of offline R_Ports. The number of process login (PRLI) requests sent. The number of FCXP allocation waits. The number of process login (PRLI) response errors. The number of process login (PRLI) response accepts. Whether the remote port is an initiator. The number of process login (PRLI) response parse errors. The number of process login (PRLI) rejected requests. The number of timeouts detected. The number of second-level errors recovered, reported by BFA. The total number of I/O operations on the port. The number of data requests for in-bound data only. The number of data requests for out-bound data only. The total number of I/O operations that completed successfully. The write data that was transferred, measured in bytes. The read data that was transferred, measured in bytes. The number of slowpath IO requests that are completed. The number of successful firmware I/O underrun operations. The number of successful firmware I/O overrun operations. The number of IO requests in the wait queue. The number of IO requests in the wait queue that are completed. The number of IO tags that are not free.
121
Field
IO timeouts IO failure due to target offline IO protocol errors IO SBC-3 protection errors fcp-2 error recovery failed Delayed freeing of IO tag Host IO abort requests Host IO abort completions IO clean-up requests IO path tov expired IO abort completions IO cleaned-up due to IOC down IO comp with unknown tags Abort request due to TM command Abort completion due to TM command IT Nexus create requests IT Nexus FW create requests IT Nexus FW create completions IT Nexus onlines IT Nexus offlines IT Nexus FW delete requests IT Nexus FW delete completions IT Nexus delete requests SLER events Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup failure No free TM tag TM Request-Q wait
Description
The number of IO timeouts. The number of IO failures caused by an offline target. The number of I/O protocol errors. Number of SCSI block data protection errors for SBC-3 (SCSI Block Command 3). The number of times an FCP-2 error recovery attempt failed. The number of IO tags with delayed freeing. The number of host IO abort requests. The number of Host IO aborts that completed. The number of IO clean-up requests. The number of IOs where the time out value has expired. The number of IO aborts that completed. The number of IOs that were cleaned up because the IO Controller went down. The number of IO completions with unknown tags. The number of requests aborted because of target mode (TM) commands. The number of target mode command requests resulting in an abort. The number of Initiator Target Nexus (ITN) create requests. The number of Initiator Target Nexus (ITN) firmware create requests. The number of Initiator Target Nexus (ITN) firmware create completions. The number of online Initiator Target Nexus (ITN). The number of offline Initiator Target Nexus (ITN). The number of Initiator Target Nexus firmware delete requests. The number of Initiator Target Nexus firmware delete completions. The number of Initiator Target Nexus delete requests. The number of second-level error recovery (SLER) events. The number of disabled IO controllers. The number of Initiator Target Nexus cleanup completions. The number of target mode (TM) requests. The number of target mode (TM) completions. The number of target mode (TM)-initiated IO cleanup requests that succeeded. The number of target mode (TM)-initiated IO cleanup requests that failed. The number of free target mode (TM) tags. The number of Q wait target mode (TM) requests
122
Field
TM Request-Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions TM firmware queue resumed
Description
The number of Q wait target mode (TM) requests that completed. The number of target mode requests that were cleaned up because the IO Controller went down. The number of target mode (TM) cleanup requests. The number of target mode (TM) cleanup completions. Whether the target mode firmware queue has resumed.

123
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).

Select 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
Keep running data check box Polling frequency in seconds text box Start polling button Reset button Date Total IO requests Data in-bound requests Data out-bound requests Total IO completions Write data transferred in bytes Read data transferred in bytes Slowpath IO completions IO underrun IO overrun IO request-Q wait IO request-Q wait done No free IO tag IO timeouts IO failure due to target offline IO protocol errors IO SBC-3 protection errors fcp-2 error recovery failed Delayed freeing of IO tag
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the FCP IM Module statistics. Click to reset all of the statistics to 0. The date and time of the most recent reset. The total number of I/O operations on the port. The number of data requests for in-bound data only. The number of data requests for out-bound data only. The total number of I/O operations that completed successfully. The write data that was transferred, measured in bytes. The read data that was transferred, measured in bytes. The number of slowpath IO requests that are completed. The number of successful firmware I/O underrun operations. The number of successful firmware I/O overrun operations. The number of IO requests in the wait queue. The number of IO requests in the wait queue that are completed. The number of IO tags that are not free. The number of IO timeouts. The number of IO failures caused by an offline target. The number of I/O protocol errors. Number of SCSI block data protection errors for SBC-3 (SCSI Block Command 3). The number of times an FCP-2 error recovery attempt failed. The number of IO tags with delayed freeing.
124
Field
Host IO abort requests Host IO abort completions IO clean-up requests IO path tov expired IO abort completions IO cleaned-up due to IOC down IO comp with unknown tags Abort request due to TM command Abort completion due to TM command IT Nexus create requests IT Nexus FW create requests IT Nexus FW create completions IT Nexus onlines IT Nexus offlines IT Nexus FW delete requests IT Nexus FW delete completions IT Nexus delete requests SLER events Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup failure No free TM tag TM Request - Q wait TM Request - Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions Aborted IO requests IO timeouts
Description
The number of host IO abort requests. The number of Host IO aborts that completed. The number of IO clean-up requests. The number of IOs where the time out value has expired. The number of IO aborts that completed. The number of IOs that were cleaned up because the IO Controller went down. The number of IO completions with unknown tags. The number of requests aborted because of target mode (TM) commands. The number of target mode command requests resulting in an abort. The number of Initiator Target Nexus (ITN) create requests. The number of Initiator Target Nexus (ITN) firmware create requests. The number of Initiator Target Nexus (ITN) firmware create completions. The number of online Initiator Target Nexus (ITN). The number of offline Initiator Target Nexus (ITN). The number of Initiator Target Nexus firmware delete requests. The number of Initiator Target Nexus firmware delete completions. The number of Initiator Target Nexus delete requests. The number of second-level error recovery (SLER) events. The number of disabled IO controllers. The number of Initiator Target Nexus cleanup completions. The number of target mode (TM) requests. The number of target mode (TM) completions. The number of target mode (TM)-initiated IO cleanup requests that succeeded. The number of target mode (TM)-initiated IO cleanup requests that failed. The number of free target mode (TM) tags. The number of Q wait target mode (TM) requests The number of Q wait target mode (TM) requests that completed. The number of target mode requests that were cleaned up because the IO Controller went down. The number of target mode (TM) cleanup requests. The number of target mode (TM) cleanup completions. The number of aborted I/O requests. The number of times an I/O operation timed out.
125
Field
IO retry for SQ error recovery Delayed freeing of IO resources Host IO abort requests IO cleaned-up due to IOC down TM cleaned-up due to IOC down Total IO count
Description
The number of I/O retries for sequence level error recovery. The number of times I/O resource freeing was delayed. The number of aborted I/O requests. The number of IOs that were cleaned up because the IO Controller went down. The number of target mode requests that were cleaned up because the IO Controller went down. The total number of IO operations.

126
Fibre Channel Security Protocol Configuration dialog box

The Fibre Channel Security Protocol Configuration dialog box enables you to define security authentication on selected ports.

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.
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
Port # Port WWN Port Name Authentication Status Algorithm Group Enable Authentication check box CHAP Secret Retype Secret Algorithm list
Description
The port number (0 or 1) for which you are configuring security authentication. The world wide name of the port for which you are configuring security authentication. The name of the port (for example, Port 0 or Port 1) for which you are configuring security authentication. Check to enable port security authentication. Indicates whether authentication is used. The configured algorithm. Options include MD5, SHA1, MD5SHA1, SHAMD5. Indicates the DH group value. DHNULL (group 0) is the only option. Check to enable FC-SP authentication on the selected device. Type the CHAP secret. Retype the CHAP secret to confirm. Select the type of algorithm. Options include the following: MD5 - A hashing algorithm that verifies a messages 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.
127
Field
Group list Apply button
Description
The DHNULL (group 0) is the only option available in the list. Click to apply the FC-SP settings.

128
Firmware Statistics dialog box

The Firmware Statistics dialog box enables you to display statistical information about the firmware.

1. 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
Keep running data check box Polling frequency in seconds text box Start polling button Reset button IOC Firmware
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the Firmware statistics. Click to reset all of the statistics to 0.
Enable RequestsThe number of IOC firmware enable requests. Disable RequestsThe number of IOC firmware disable requests. Get Attribute RequestsThe number of get attribute requests. Debug sync countThe number of debug synchronizations that occurred. Debug dump countThe number of debug dumps that occurred. Unknown RequestsThe number of IOC firmware requests that are unknown. Config RequestsThe total number of configuration requests on the IOC FC firmware. UpdateQ RequestsThe number of update Q requests on the IOC FC firmware. Interrupt Coalesce RequestsThe number of times an interrupt coalesce is requested. Unknown RequestsThe number of IOC FC firmware requests that are unknown. Set Interrupt RequestsThe number of Set Interrupt requests on the IOC FC firmware.
IOC FC Firmware
129
Field
Firmware IO
Description
host IO abortsThe number of host IO aborts in the firmware. host IO cleanupThe number of host IO cleanup attempts in the firmware. IO timeouts in f/wThe number of IO timeouts in the firmware. Frames parsed by f/wThe number of frames parsed by the firmware. data framesThe number of data frames in the firmware. fcp rsp framesThe number of FCS responses on the firmware IO. xfer_rdy framesThe number of transfer-ready frames. BLS ACC framesThe number of BLS ACC frames on the firmware IO. target abort framesThe number of aborted target frames on the firmware IO. unknown framesThe number of unknown frames on the firmware IO. itn CISC updated on rspThe number of CICSs updated on response. itn CISC updated on dataThe number of CICSs updated on data. itn CISC updated on xfer_rdyThe number of updates that occurred on xfer_rdy. data frames DMAed by f/wThe number of data frames dropped by the firmware. frames dropped by f/wThe number of times the firmware dropped frames. FCP data frames lostThe number of FCP data frames lost. RO Set in xfer_rdyThe number of RO set in xfer_rdy events on the firmware IO. xfer_rdy OOO errorThe 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 outThe number of ABTS timeouts on the firmware IO. ITN SLER initiatedThe number of Initiator Target Nexus (ITN) second-level error recoveries (SLER) initiated. REC timeoutsThe number of receive timeouts on the firmware IO. error RECThe number of errors received on the firmware IO. REC rsp invalidThe number of invalid receive responses. seqr IO abortThe number of sequential IO aborts. seqr IO retryThe number of sequential retries on the firmware IO. wait for seq initiativeThe number of sequential initiative waits on the firmware IO. FCP RSP-wrong IO stateThe number of times responses were in the wrong state. FCP RSP_underrunThe number of IO response underruns. FCP RSP_underrun for writeThe number of IO response underruns during write operations. FCP RSP_underrun errThe number of IO response underrun errors.
130
Field
Firmware IO (continued)
Description
FCP RSP_invalid residueThe number of invalid residue responses. FCP RSP_overrunThe number of overrun responses on the firmware IO. FCP RSP_overrun errThe number of overrun response errors on the firmware IO. FCP RSP_protocol errThe number of response protocol errors on the firmware IO. FCP RSP_sense data errThe number of response sense data errors on the firmware IO> FCP RSP_conf requestedThe number of RSP_conf requests on the firmware IO. target initiated IO abortThe number of RSP_target initiated IO aborts. IOH EDTOV timer eventThe number of Error Detect Time Out events. IOH FCP RSP excp eventThe number of FCP response exception events during firmware IO. IOH FCP conf eventThe number of FCP conf events during firmware IO. IOH multi-frm rsp eventThe number of multi-frame response events during firmware IO. IOH hit class2 eventThe number of hit class2 events during firmware IO. IOH miss other eventThe number of other events missed during firmware IO. IOH Seq. count error eventThe number of seq count error events during firmware IO. IOH length error eventThe number of length error events during firmware IO. IOH seq length error eventThe number of IOH seq length error events during firmware IO. IOH data oor eventThe number of IOH data events that are out of range during firmware IO. IOH RO OOO eventThe number of IOH RO events during firmware IO. IOH CPU owned eventThe number of CPU-owned events during firmware IO. IOH unexp frame eventThe number of unexpected frame events during firmware IO. IOH Error interruptThe number of interrupted errors during firmware IO.
131
Field
Firmware Port FPG
Description
InterruptsThe number of firmware port interrupts. Level 0 InterruptsThe number of Level 0 interrupts on the firmware port. 0 Caused InterruptsThe number of 0 cause interrupts on the firmware port. Interrupts OtherThe number of other interrupts on the firmware port. Interrupts Other IgnoredThe number of other interrupts that are ignored on the firmware port. Signal LostThe number of times loss of signal has occurred. Signal RegainedThe number of times loss of signal has been regained. Sync LostThe number of times loss of synchronization has occurred. Sync TimeoutThe number of times synchronization timeout has occurred. Sync RegainedThe number of times loss of synchronization has been regained. DIV2 OverflowThe number of DIV2 overflow events on the firmware port. DIV2 UnderflowThe number of DIV2 underflow events on the firmware port. EFIFO OverflowThe number of elastic FIFO (EFIFO) overflow events. EFIFO UnderflowThe number of elastic FIFO (EFIFO) underflow events. IDLE PrimitivesThe number of IDLE primitive events. LRR PrimitivesThe number of link reset response (LRR) primitive events. LR PrimitivesThe number of link reset (LR) primitive events. OLS PrimitivesThe number of Offline Sequence (OLS) primitive events. NOS PrimitivesThe number of not operational (link has failed) primitive events. LIP PrimitivesThe number of loop initialization (LIP) primitive events. ARBFO PrimitivesThe number of ARBFO primitive events that occurred on the firmware port. ARB PrimitivesThe number of ARB primitive events that occurred on the firmware port. MRK PrimitivesThe number of MRK primitive events that occurred on the firmware port. Unknown PrimitivesThe number of unknown primitive events that occurred on the firmware port. Module InsertsThe number of module inserts in the Physical Port State Machine (PHYSM). Module ExtractsThe number of module extracts in the Physical Port State Machine (PHYSM). Module Invalid EventsThe number of module invalid events in the Physical Port State Machine (PHYSM). Module Validation IgnoredThe number of module validation ignored events in the Physical Port State Machine (PHYSM). Laser FaultsThe number of laser fault events in the Physical Port State Machine (PHYSM).
Firmware Port PHYSM
132
Field
Firmware Port FCoE
Description
CEE linkupThe number of CEE linkups on the FCoE port. CEE linkdownThe number of CEE linkdowns on the FCoE port. FIP linkupThe number of FCoE Initialization Protocol (FIP) linkups. FIP linkdownThe number of FCoE Initialization Protocol (FIP) linkdowns. FIP failuresThe number of FCoE Initialization Protocol (FIP) failures. Invalid MAC assignmentsThe number of invalid MAC assigments on the FCoE port. Vlan requestsThe number of FCoE Initialization Protocol (FIP) VLAN requests. Vlan notificationsThe number of FCoE Initialization Protocol (FIP) VLAN notifications. Vlan error framesThe number of FCoE Initialization Protocol (FIP) VLAN error frames. Vlan request timeoutsThe number of FCoE Initialization Protocol (FIP) VLAN request timeouts. Vlan invalidWhether the VLAN is invalid. Discovery responsesThe number of FCoE Initialization Protocol (FIP) discovery responses. Discovery error framesThe number of FCoE Initialization Protocol (FIP) discovery error frames. Discovery unsolicitedThe number of unsolicited FCoE Initialization Protocol (FIP) discovery requests. Discovery requestsThe number of FCoE Initialization Protocol (FIP) discovery requests. Discovery timeoutsThe number of FCoE Initialization Protocol (FIP) discovery timeouts. Discovery FCF Not Avail.The FCoE Forwarder (FCF) is not available for discovery. Unsupported link serviceThe number of unsupported FCoE Initialization Protocol (FIP) link services. Link service error framesThe number of FCoE Initialization Protocol (FIP) link service error frames. LOGO requestsThe 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 operationThe number of unsupported FCoE Initialization Protocol (FIP) operations. Untagged FIP framesThe number of untagged FCoE Initialization Protocol (FIP) frames. Invalid version framesThe number of invalid FCoE Initialization Protocol (FIP) version frames.
Firmware Port FIP
133
Field
Firmware CT MAC
Description
MAC turned-on countThe number of times MAC has been turned on. Linkup countThe number of linkups on the Firmware CT. Lost signal countThe number of times loss of signal has occurred. MAC reset countThe number of times MAC has been reset. PCS reset countThe number of times PCS has been reset. DFE on count MAC serdes loopback countThe 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. CRC frame countThe cyclic redundancy check (CRC) frame count for the Ethernet module. RxA RDS underrun errorThe number of RxA RDS underrun errors on the Firmware CT module. RAD BPC overflow errorThe number of RAD BPC overflow errors on the Firmware CT module. RAD RLB BPC overflow errorThe number of RAD RLB BPS overflow errors on the Firmware CT module. BPC fcs errorThe number of BPC FCS errors on the Firmware CT module. TxA TSO header too longIndicates if the TxA TSO header is too long.
Firmware ETH sndcv MOD Firmware CT MOD

Controlling the polling frequency rate Resetting statistics Performance monitoring
134
Hardware Tests Diagnostics dialog box
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.

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

Field
Memory Test check box Ports list PCI Loopback Test check box Data Pattern Test Cycle text box Loopback Test check box Queue Test check box Subtest ID list Link Speed list Frame Count Stop on Error check box Test Log table Start button Stop button
Description
Check to run a Memory test on the port. Select a port from the list. Check to run a PCI Loopback test on the port. Type a data pattern. The default value is A5A5A5A5. Specify the number of times the test runs. The default value is 100. Check to run a Loopback test on the port. Check to run a Queue test on the port. Select a subtest from the list. The default is Internal. Select a link speed from the list. Type a frame count. The default value is 8192. Check to flag the system to stop running the test if an error occurs. Displays the time the test was run, the status of the test, and the result of the test. Click to run the selected test. Click to stop all pending tests.

Configuring beaconing using HCM supportSave on page 84
135
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 panel

1. Select an HBA in the device tree. 2. Click the Properties tab in the right pane.

Field
HBA Parameters Node WWN Name Operating Status Manufacturer Model Description Max Speed Supported # of Ports OEM info Card Type Chip Revision Hardware Path Serial # Temperature The adapter nodes world wide name. The name representing the adapter. Whether the HBA is enabled or disabled. The company that manufactured the HBA. The description of the HBA. The maximum speed supported on the HBA; for example, 8 Gbps. The number of ports associated with the HBA. Information about the original equipment manufacturer. The adapter card type; for example, FC or CNA. The revision level of the chip. The hardware path of the HBA. The serial number of the HBA. The temperature of the HBA, displayed in Celsius and Fahrenheit.
Description
Driver Parameters It 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 Driver Version Firmware Parameters Firmware Version BIOS Version PCI Registers Vendor ID Device ID Subsystem ID The identifier of the PCI Registers vendor. The device ID of the PCI Register. The ID of the PCI subsystem. The version level of the firmware. The version level of the BIOS. The name of the host adapter driver. The version level of the host adapter driver.
136
Field
Subsystem Vendor ID Current # of Lanes Initial Negotiated # of Lanes PCIe Generation
Description
The ID of the PCI subsystem vendor. The number of PCI lanes, in Gbps, each way between the PCI slot and the adapter. The set number of PCI lanes that were initially negotiated. The number of times the PCI Register is generated.
OEM Vital Product Data (VPD) Information Note: This information does not exist for the Brocade 1007 CNA expansion card. OEM Part # EDC The name of the original equipment manufacturer. The OEM part number of the HBA. 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. 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. The power rating (HP only). The value, 10 W, is the same for all adapters. The engineering change level for the card, represented by alphanumeric characters. The OEM FRU number of the HBA. The OEM serial number of the HBA. The OEM product description of the HBA. Displays information that is specific to the HBA vendor.
MDC
PW EC level FRU # Serial # Product Description Vendor Data
137

The Historical Performance dialog box allows you to generate a historical performance graph for a device

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.

Field
Statistics Name text box
Description
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. Select one of the following frequencies: Last 1 DayOne sample of historical data is collected for 30 minutes duration. Last 1 WeekTwo samples of historical data is collected for one hours duration. Last 1 MonthFour samples of historical data is collected for two hours duration.
Data for list
Apply button Statistics Counters options
Click to apply your configuration changes. 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 framesThe number of frames that were lost due to a lack of host buffers available. Errored framesThe number of frames received in error. Loss of sync countThe number of times loss of synchronization occurred. Loss of signal countThe number of times loss of signal occurred. Rx CRC err framesThe number of frames that have been received in error.

Real-time performance data Historical performance data
138
IOC Statistics dialog box
IOC Statistics dialog box

The IOC Statistics dialog box enables you to view statistics related to the input/output controller (IOC).

1. 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
Keep running data check box Polling frequency in seconds text box Start polling button Reset button IOC Driver: Mailbox Interrupt IOC Driver: Enable Events IOC Driver: Disable Events IOC Driver: Heartbeat Failures IOC Driver: Firmware Boots IOC Driver: Statistics Timeouts
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the IOC statistics. Click to reset all of the statistics to 0. The number of mailbox interrupts on the IOC driver. The number of enable events on the IOC driver. The number of disable events on the IOC driver. The number of heartbeat failures on the IOC driver. The number of firmware boots on the IOC driver. The number of statistics timeouts on the IOC driver.

139
LLDP Properties panel (CNA only)
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 panel

1. Select a CNA in the device tree. 2. Click the LLDP tab in the right pane.

Field
Chassis ID Port Description Port ID System Name System Description System Capabilities
Description
The MAC address associated with the local system. The user-configured port description. The port identification associated with the transmitting LLDP agent. The user-configured name of the local system. The system description containing information about the software and current image running on the system. 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. The age of the information propogated in LLDP frames. Time to live (TTL) values are measured in seconds.
Time to Live
140
Logical Port Statistics dialog box

The Logical Port Statistics dialog box enables you to display statistics that are related to a selected logical port.

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

NS
Field
Keep running data check box Polling frequency in seconds text box Start polling button Reset button Date ns_plogi_sent ns_plogi_rsp_err ns_plogi_acc_err ns_plogi_accepts NS command rejects ns_plogi_unknown_rsp ns_plogi_alloc_wait NS command retries NS command timeouts ns_rspnid_sent ns_rspnid_accepts ns_rspnid_rsp_err ns_rspnid_rejects ns_rspnid_alloc_wait ns_rftid_sent
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the logical port statistics. Click to reset all of the statistics to 0. The date and time of the most recent reset. The number of Name Server port logins sent. The number of Name Server response errors. The number of Name Server port login accept errors. The number of times Name Server port logins are accepted. The number of Name Server port login rejects. The number of unknown Name Server port login response errors. The number of delayed Name Server port login response errors. The number of name server command retries. The number of name server command timeouts. The number of times the Name Server Register Symbolic Port Name identifier was sent. The number of times the Name Server Register Symbolic Port Name identifier was accepted. The number of Name Server Register Symbolic Port Name identifier response errors. The number of Name Server Register Symbolic Port Name identifier rejects. The number of Name Server Register Symbolic Port Name identifier allocations. The number of Name Server Register FC4 Type identifier requests sent.
141
Field
ns_rftid_accepts ns_rftid_rsp_err ns_rftid_rejects ns_rftid_alloc_wait ns_rffid_sent ns_rffid_accepts ns_rffid_rsp_err ns_rffid_rejects ns_rffid_alloc_wait ns_gidft_sent ns_gidft_accepts ns_gidft_rsp_err ns_gidft_rejects ns_gidft_unknown_rsp ns_gidft_alloc_wait MS command retries MS command timeouts ms_plogi_sent ms_plogi_rsp_err ms_plogi_acc_err ms_plogi_accepts MS command rejects ms_plogi_unknown_rsp ms_plogi_alloc_wait Num of RSCN received Num portid format RSCN Unsolicited recv frames Dropped received frames Received plogi Received adisc
Description
The number of times the system accepted Name Server Register FC4 Type identifier requests. The number of Name Server Register FC4 Type identifier response errors. The number of times the system rejected Name Server Register FC4 Type identifier requests. The number of delayed Name Server Register FC4 Type identifier allocations. The number of Name Server RFID tag requests sent. The number of times the system accepted Name Server RFID tag requests. The number of Name Server RFID tag response errors. The number of Name Server RFID tag rejects. The number of Name Server RFID tag allocations. The number of Name Server Get all Port ID requests sent. The number of times the system rejectedName Server Get all Port ID requests. The number of delayed Name Server Get all Port ID allocations. The number of times a Name Server Get all Port ID request for a given FC4 type is rejected. The number of unknown responses associated with a Name Server Get all Port ID request for a given FC4 type. The number of delayed Name Server Get all Port ID requests for a given FC4 type allocations. The number of MS command retries. The number of times an MS command timed out. The number of port login requests sent. The number of response errors associated with a ms port login. The number of accept errors associated with a ms port login. The number of ms port login accepts. The number of MS command rejects. The number of ms port login unknown responses. The number of delayed ms plogin allocations. The number of Registered State Change Notifications received. The number of Registered State Change Notifications received by Port ID. The number of received frames that were unsolicited. The number of received frames that were dropped. The number of times port logins are received. The number of times discover address (ADISC) requests are received.
142
Field
Received prlo Received prli Received logo Received rpsc Received unhandled ELS Rport plogi retry timeout count Deleted rport (max retry of plogi) Total IO Requests Data in-bound requests Data out-bound requests Total IO completions Data transferred in bytes Slowpath IO completions IO underrun IO overrun IO Request-Q wait IO Request-Q wait done No free IO tag IO timeouts IO failure due to target offline IO protocol errors IO SBC-3 protection errors fcp-2 error recovery failed Delayed freeing of IO tag Host IO abort requests Host IO abort comps IO clean-up requests IO path TOV expired IO abort completions IO cleaned up due to IOC down IO comp with unknown tags Abort request due to TM command Abort completion due to TM command
Description
The number of times PRLOs are received. The number of times PRLIs are received. The number of times logouts are received. The number of Report Port Speed Capabilities (RPSC) requests received. The number of unhandled ELS requests. The total number of timeouts that occurred during port login attempts on the remote port. The number of remote ports deleted after the maximum number of port login retries. The total number of IO requests. The number of data requests for in-bound data only. The number of data requests for out-bound data only. The total number of IO operations that completed. The transferred data, measured in bytes. The number of I/Os completed in slowpath handling. The number of I/O underrun operations. The number of I/O overrun operations. The number of Q wait IO requests. The number of completed Q wait IO requests. The number of no free IO tags. The number of times an I/O timed out. The number of IO failures due to an offline target. The number of I/O protocol errors. The number of IO errors for SBC-3 (SCSI Block Command 3). The number of times an FCP-2 error recovery attempt failed. The number of IO tags with delayed freeing. The number of host IO abort requested. The number of completed host IO aborts. The number of IO clean up requests. The number of IOs where the time out value has expired. The number of IO aborts that completed. The number of IOs that were cleaned up because the IO Controller is offline. The number of IO completions with unknown tags. The number of target mode abort requests. The number of completed aborts because of a target mode command.
143
Field
IT Nexus create requests IT Nexus FW create requests IT Nexus FW create completions IT Nexus onlines IT Nexus offlines IT Nexus delete requests IT Nexus FW delete requests IT Nexus FW delete completions SLER requests Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup faulures No free TM tag TM Request-Q wait TM Request-Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions
Description
The number of Initiator Target Nexus (ITN) create requests. The number of Initiator Target Nexus (ITN) requested firmware create requests. The number of Initiator Target Nexus (ITN) requested firmware create completions. The number of Initiator Target Nexus (ITN) that are online. The number of Initiator Target Nexus (ITN) that are offline. The number of Initiator Target Nexus (ITN) requested deletes. The number of Initiator Target Nexus (ITN) requested firmware deletes. The number of Initiator Target Nexus (ITN) completed firmware deletes. The number of second level error recovery (SLER) event requests. The number of disabled IO controllers. The number of Initiator Target Nexus (ITN) completed cleanups. The number of task management requests. The number of task management completions. The number of successful task management initiated IO cleanups. The number of failed task management initiated IO cleanups. The number of free task management tags. The number of Q wait task management requests. The number of completed Q wait task management requests. The number of task management cleanups due to an offline IO controller. The number of requested task management cleanups. The number of completed task management cleanups.

144
LPORT Properties panel
LPORT Properties panel

The LPORT Properties panel enables you to display the properties that are associated with a logical port.
Opening the panel

1. From the device tree, select a physical port. 2. Click the LPORTs Properties tab in the right pane.

Field
Base Port FC Address FPMA MAC Address Node WWN Port WWN Roles State Switch IP Addr Switch NWWN Symbolic Name
Description
Indicates whether the logical port is used as the base port. The Fibre Channel address of the logical port. The Fabric-Provided Ethernet MAC address created using the FC_ID assigned by the Fabric. The adapters world wide name. The ports world wide name. The role of the logical port; for example, FCP Initiator. Displays whether the logical port is online or offline. The switchs IP address. The switch nodes world wide name. The symbolic name associated with the logical port.
145
Master Log tab
Master Log tab

The Master Log enables you to display a list of all events that have occurred.
Opening the tab

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.

Field
Filter button Sr No column Severity column WWN/MAC column Category column
Description
Click to launch the Master Log Filter dialog box. Displays a numbering sequence in ascending order. The event severity (informational, minor, major, or critical). The world wide name or the media access control (MAC) address of the device on which the event occurred. 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 Description column Date/Time column Clear Filter button Refresh button
The subcategory of the main event; for example, offline, online, disabled, or enabled. Displays a brief description of the event. The date and time when the event occurred. Click to clear the Master Log filter. Click to refresh the screen.
Using the tab

146

The Master Log Filter dialog box enables you to filter the events you receive by time, severity, category, or world wide name.

1. Select the Master Log tab, located at the bottom pane of the Host Connectivity Manager, 2. Click the Filter button.

Field
Event Time Event Severity Category WWN/MAC
Description
Type in a From and To value to represent the time during which events will be logged. Select one or all of the following values: Critical, Major, Minor, Information. Select an event category, for example, Rport or ITNIM, from the list. Select a world wide name (WWN) or media access control (MAC) address from the list.

147
Persistent Binding dialog box
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.

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

Field
At the host or CNA level Serial Number Hardware Path Port # Port WWN Name Persistent Type Target Name Remote Port WWN SCSI Target ID At the port level HBA or CNA Node HBA or CEE port Persistent type Target Name Remote Port WWN SCSI Target ID The world wide node name of the HBA or CNA node. The world wide name of the HBA or CNA port. The type of binding; for example, Port WWN. The SCSI target name. The world wide name of the remote port. The SCSI target identifier. The serial number of the CNA. The hardware path of the CNA. The port number of the CNA. The ports world wide name. The port name; for example, Port 0 or Port 1. The type of binding; for example, Port WWN. The SCSI target name. The world wide name of the remote port. The SCSI target identifier.
Description

148
Port POM Properties panel
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. Only Brocade-branded SFPs and SFPs+ are supported with the 8 Gbps FC HBAs and 10 Gbps CNAs.
NOTE
Opening the panel

1. Select a port in the device tree. 2. Click the POM tab in the right pane.

Field
Temperature(C) Bias Current (mA) Tx Power (mW) Rx Power (mW) Voltage Alarm/Warning
Description
The port temperature, measured in Celsius. The low-level DC current (the Bias Current), measured in mA. The transmitted power, measured in mW. The received power, measured in mW. The voltage; for example, 1.8V, 3.3V, or 5.0V. The state of the port POM.
149
Port Properties panel (HBA only)

The Port Properties panel enables you to display the properties that are associated with a selected HBA port. QoS properties apply only to the HBA.
NOTE
Opening the panel

1. Select a port in the device tree. 2. Click the Properties tab in the right pane.

Field
Port Parameters Port # Port WWN Node WWN Factory Port WWN Factory Node WWN Name FC Address Media Port Type Configured Port State Operating Port State Supported Classes Configured Speed Operating Speed The port number: 0 or 1. The ports world wide name. The adapters world wide name. The factory-assigned port world wide name. The factory-assigned adapter world wide name. The name that is manually assigned to the port. The ports Fibre Channel address. Type of media software; for example, 8G-sw. The port type; for example, N_Port. Indicates whether the port is enabled or disabled. Indicates whether the link is online or offline. The types of classes that are supported on the port; for example, Class-3. The configured port 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 HBAs speed and the ports SFP. Auto-negotiate is the recommended 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. The maximum speed that is supported on the port, which is 8 Gbps. The topology setting at which the port is operating. Only point to point (P2P) mode is supported. The maximum number of receive buffers. The maximum number of transmit buffers.
Description
Max Speed Supported Operating Topology Receive BB Credits Transmit BB Credits
150
Field
IOC ID Hardware Path Frame Data Field Size # of Lports Operating Parameters Link Beacon State Path Time Out Logging Level Target Rate Limit Default Rate Limit FC-SP Parameters Authentication Status Algorithm Group Error Status QoS Parameters Configured QoS State Operating QoS State Total BB Credit Priority Levels Persistent Binding
Description
The I/O controllers identifier. The hardware path of the HBA port. The frame size, in byres, of the port. The default is 2112. Select auto to set the frame data field size automatically. The number of logical ports in the configuration.
Indicates whether link beaconing is on or off. The value between 0 and 60 that specifies the time out session. The port logging level. Values include Log Critical, Log Error, Log Warning, Log Info, and Log Invalid. Indicates whether target rate limiting is on or off. Select the target rate limit from the list. Options include 1 Gbps, 2 Gbps, and 4 Gbps. The default is 2 Gbps.
Indicates whether FC-SP authentication is on or off. The status of Fibre Channel Security Protocol (FC-SP) authentication. The configured authentication algorithm. The DH Group (DH Null, group 0, is the only option). The health status of the Fibre Channel Security Protocol (FC-SP) parameters.
Indicates whether QoS is enabled or disabled. Indicates whether QoS is online or offline. The total number of receive buffers. QoS priority levels. Values include High, Medium, and Low. Indicates whether persistent binding is on or off.
Using the panel

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

Select Monitor > Statistics > Port Statistics from the Host Connectivity Manager.

Field
Keep running data check box Polling frequency in seconds text box Start polling button Reset button Date Frames 64 bytes Frames 65-127 bytes Frames 128-255 bytes Frames 256-511 bytes Frames 512-1023 bytes Frames 1024-1518 bytes Frames 1519-1522 bytes Tx bytes Tx packets Tx multicast packets Tx broadcast packets Tx control frame Tx drops Tx jabber Tx FCS errors Tx fragments Rx bytes Rx packets Rx multicast packets Rx broadcast packets
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the Port statistics. Click to reset all of the statistics to 0. The date and time of the most recent reset. The number of 64-byte frames. The number of frames with 65-127 bytes. The number of frames with 128-255 bytes. The number of frames with 256-511 bytes. The number of frames with 512-1023 bytes. The number of frames with 1024-1518 bytes. The number of frames with 1519-1522 bytes. The number of transmitted bytes. The number of transmitted packets. The number of transmitted multicast packets. The number of transmitted broadcast packets. The transmitted control frames. The number of transmitted frames dropped. The number of transmitted jabbers (illegal packet length). The number of frame check sequence (FCS) errors transmitted, which indicate that frames of data are corrupted. The number of transmitted frame packets that are fragmented. The number of received bytes. The number of received packets. The number of received multicast packets. The number of received broadcast packets.
152
Field
Rx control frames Rx unknown opcode Rx drops Rx jabber
Description
The number of received control frames, which assist in data frame delivery. The number of unknown opcode frames received. The number of received packet drops. 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). The number of frames that have a integral of 64 to 1518 length and contain a frame check sequence (FCS) error. The number of packets received with alignment errors. The number of frames received in which the 802.3 length field did not match the number of data bytes actually received. The number of frames received with at least one invalid data symbol. The number of received frames that are less than 64 bytes in length and contain an invalid FCS (includes integral and non-integral lengths). The number of received pauses. The number of received zero pauses. The number of transmitted pauses. The number of transmitted zero pauses. 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. The number of times a zero pause control frame was received by a congested FCoE port. 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. The number of times a zero pause control frame was transmitted to a congested FCoE port. The number of received iSCSI pauses. The number of received iSCSI zero pauses. The number of transmitted iSCSI pauses. The number of transmitted iSCSI zero pauses.
Rx FCS errors Rx alignment errors Rx frame len errors Rx code errors Rx fragments
Rx pause Rx zero pause Tx pause Tx zero pause Rx FCoE pause
Rx FCoE zero pause Tx FCoE pause
Tx FCoE zero pause Rx iSCSI pause Rx iSCSI zero pause Tx iSCSI pause Tx iSCSI zero pause
153

154
Protocol Tests dialog box
Protocol Tests dialog box

The Protocol Tests dialog box enables you to run diagnostic tests on Fibre Channel components.

1. Select Configure > Diagnostics from the Host Connectivity Manager. 2. Click the FC Protocol Tests tab.

Field
Echo Test check box FC Ping Test check box FC Trace Route check box Add button Remove button Remove All button Test Cycle text box Test Log table Port list Target list Logical Port list Stop on Error check box Start button Stop button
Description
Check to run an Echo Test on the selected port. Check to run an FC Ping Test on the selected port. Check to run an FC Traceroute on the selected port. Click to add a selected port, logical port, or target to the test list. Click to remove a selected port, logical port, or target from the test list. Click to remove all ports, logical ports, and targets from the test list. Specify the number of times the test runs. The default value is 100. Displays the time the test was run, type of test run, status of the test, configuration, and the results. Select a port on which the test will be run from the list. Select a target on which the test will be run from the list. Select a logical port on which the test will be run from the list. Check to flag the system to stop running the test if an error occurs. Click to run the selected test. Click to stop all pending tests.

Configuring beaconing using HCM supportSave collection sources
155
QoS Statistics dialog box (HBA only)
QoS Statistics dialog box (HBA only)

The QoS Statistics dialog box enables you to view statistics related to Quality of Service (QoS).

Select Monitor > Statistics > QoS Statistics from the Host Connectivity Manager.

Field
Date QoS ELP Accepted QoS ELP dropped QoS ELP received QoS ELP rejected QoS Flogi Acc received QoS Flogi rejects received QoS Flogi retries QoS Flogi sent QoS RSCN received
Description
The date and time of the most recent reset. The number of ELPs (Exchange Link Parameters) accepts sent. The number of ELPs dropped. The number of ELPs successfully received. The number of ELPs rejected. The number of QoS Fabric login (Flogi) accept requests received. The number of QoS Fabric login (Flogi) rejects received. The number of QoS Fabric login (Flogi) retries. The number of QoS Fabric login (Flogi) requests sent. The number of Registered State Change Notifications (RSCN) received.

156
Real-time Performance Statistics dialog box
Real-time Performance Statistics dialog box

The Realtime Statistics dialog box enables you to display the properties that are associated with the selected CEE port.

1. Select a CEE port in the device tree. 2. Select Performance > Realtime Statistics > Historical Statistics.

Field
Statistics Name list
Description
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 Apply button Statistics Counters
Select the polling interval. Options include 10 seconds, 20 seconds, or 30 seconds Click to save your configuration settings.
Tx bytes (Mbps)The number of transmitted bytes. Rx bytes (Mbps)The number of received bytes. Tx dropsThe number of dropped transmitted frames. Rx dropsThe number of dropped received frames. Tx FCS errorsThe number of frame check sequence (FCS) errors transmitted, which indicate that frames of data are corrupted. Rx FCS errorsThe number of frame check sequence (FCS) errors received, which indicate that frames of data are corrupted. Rx packetsThe number of received packets.
Port Statistics - Utilization (Mbps) graph Port Statistics - Errors/sec graph
Displays the ports utilization statistics, measured in Mbps. Displays the ports errors, measured in errors per second.
157
Remote Port Properties panel
Remote Port Properties panel

The Remote Port Properties panel enables you to display the properties that are associated with the remote port.
Opening the panel

1. From the device tree, select a remote port (target or initiator). 2. Click the Remote Port Properties tab in the right pane.
NOTE
If it is a target port, there are two tabs in the right pane: Properties and LUNs.

Field
Fibre Channel Parameters Port WWN Node WWN Symbolic Name Name FC Address Frame Data Field Size Status Supported Classes Remote Device Information Role The role of the remote device: target or initiator. The world wide name of the devices port. The world wide name of the device. The symbolic name associated with the remote port. The name associated with the device. The remote ports Fibre Channel address. The frame size, in byres, of the port. The default is 2112. Select auto to set the frame data field size automatically. The remote port status: online or offline. The types of classes that are supported on the remote port; for example, Class-3.
Description
FCP-IM IO Latency Information (if Profile is on) IO Size IO Latency Min IO Latency Max IO Latency Average Binding Information Bind Type Bus # Target ID The mode used to persistently bind target mappings. The unique identifying number for each PCI bus, assigned during system initialization. The identifier of the target device. The actual IO latency size. The minimum IO latency size. The maximum IO latency size. The average IO latency size.
158
Restore dialog box
Restore dialog box

You 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. Use 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:
NOTE
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

1. 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
Restore from previous backup data button Browse button Restore default data button Start Restore button
Description
Click to enable the Browse button, which enables you to locate the last backed-up file. Click to navigate to where the last backed-up file resides. If you click this button, the default configuration is restored. Click to restore the backed up data that you selected.
159

The SFP Properties panel enables you to display the properties that are associated with a selected small form-factor pluggable (SFP) transceiver. Brocade 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.
NOTE
Opening the panel

1. Select a port in the device tree. 2. Click the SFP or SFP+ tab in the right pane. Only Brocade-branded SFPs are supported with the 8 Gbps FC HBAs and SFPs+ with the 10 Gbps CNAs.
NOTE

Field
Port Technology SFP Supported Connector Type Transceiver Media Speed The name of the supported SFP. The type of port connector; for example, LC. SC, or Cu (copper cable). The type of transceiver; for example, XFP or GBIC. The type of media for the transceiver; for example, single mode. 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.
Description
Extended Information Identifier Encoding Baud Rate Length 9u The identifier for the extended link. Displays how the extended link is encoded, for example, 8B10B. The transmission rate, roughly equivalent to the number of bits per second. The length of the single-mode fiber optic cable, used in situations where gigabit performance is not required (for distances greater than 100 meters). The length of the fiber optic cable (for distances greater than 10 meters). The length of the fiber optic cable (for distances greater than 10 meters).
Length 50u Length 62.5u
160
Field
Length Cu Vendor Name Vendor OUI Vendor Part Revision Wavelength Options BR Max BR Min Serial # Date Code Refresh button
Description
The length of the copper cable (for distances greater than 1 meter, where optimum performance is required). The vendor of the extended link. The vendors organizational unique identifier (OUI). The part number of the extended link. The revision level of the extended link. The wavelength translation, which enables longer reach through lower attenuation. Displays details about the transceiver; for example, the type of port connector, type of transceiver, and enable/disable status. The upper bit rate limit at which the SFP transceiver meets its specifications. The lower bit rate limit at which the SFP transceiver meets its specifications. The serial number of the SFP. The date the SFP was manufactured. Click to refresh the screen.
161

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.

1. Select the host from the device tree. 2. Select Configure > Syslog from the main menu.

Field
Host name / IP Address text box Set this IP in all discovered agents in future check box Add button Remove button
Description
Enter the host name or IP address of the destination device. Click to set the device as a Syslog destination in all future discovered agents. Click to register the host as a Syslog destination. Click to remove the host as a Syslog destination.

Syslog support Registering a host server Removing a host server
162
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.

Select Monitor > Statistics > Remote port statistics > Target Statistics from the Host Connectivity Manager. OR Right-click a remote port and select Target Statistics.

Field
Date offlines onlines RSCN PLOGI sent PLOGI accepts PLOGI timeouts PLOGI failed PLOGI rejects PLOGI received PRLI received ADISC sent ADISC accepts ADISC failed ADISC rejects ADISC received ADISC rejected LOGO sent LOGO accepts LOGO failed LOGO rejected
Description
The date and time of the most recent reset. The remote ports that are offline. The remote ports that are online. The number of Fibre Channel Registered State Change Notifications (RSCNs) received. The number of times port logins (when two node ports in the SAN establish a connection between each other) occur. The number of times port logins are accepted. The number of times port logins time out. The number of times port logins fail. The number of times port logins are rejected. The number of times port logins are received. The number of times PRLIs are received. The number of discover address (ADISC) requests sent. The number of times discover address (ADISC) requests are accepted. The number of times discover address (ADISC) requests fail. The number of times discover address (ADISC) rejects. The number of times discover address (ADISC) requests are received. The number of times discover address (ADISC) requests are rejected. The number of times logouts occur. The number of times logouts are accepted. The number of times logouts fail. The number of times logouts are rejected.
163
Field
LOGO received RPSC received RPSC rejects RPSC sent RPSC accepts RPSC rejected RPSC failed uninit: create events uninit: exception events created: online events created: delete events created: IOC Down created: exception events fw create: f/w responses fw create: delete events fw create: offline events fw create: IOC down fw create: exception events online: offline events online: delete events online: IOC down events online: exception events fw delete: fw responses
Description
The number of times logouts are received. The number of Report Port Speed Capabilities (RPSC) requests received. The number of Report Port Speed Capabilities (RPSC) requests rejected. The number of Report Port Speed Capabilities (RPSC) requests sent. The number of accepted Report Port Speed Capabilities (RPSC) requests. The number of rejected Report Port Speed Capabilities (RPSC) requests. The number of failed Report Port Speed Capabilities (RPSC) requests The number of hardware abstraction layer (HAL) uninit create events. The number of hardware abstraction layer (HAL) uninit exception events. The number of hardware abstraction layer (HAL)-created online events. The number of hardware abstraction layer (HAL)-created delete events. The number of times hardware abstraction layer (HAL)-created I/O controllers were down. The number of hardware abstraction layer (HAL)-created exception events. The number of hardware abstraction layer (HAL) firmware-create responses. The number of hardware abstraction layer (HAL) firmware-created delete events. The number of hardware abstraction layer (HAL) firmware created offline events. The number of times hardware abstraction layer (HAL) firmwarecreated I/O controllers were down. The number of hardware abstraction layer (HAL) firmware-created exception events. The number of hardware abstraction layer (HAL) online and offline events. The number of hardware abstraction layer (HAL) online delete events. The number of hardware abstraction layer (HAL) online IOC down events. The number of hardware abstraction layer (HAL) online exception events. The number of hardware abstraction layer (HAL) fw Delete f/w responses.
164
Field
fw delete: delete events fw delete: IOC down events fw delete: exception events offline: delete events offline: online events offline: IOC down events offline: exception events delete: fw events delete: IOC down events delete: exception events delete pend: fw responses delete pend: IOC downs delete pend: exceptions off-pending: fw responses off-pending: deletes off-pending: IOC downs off-pending: exceptions IOC down: offline events IOC down: delete events IOC down: online events IOC down: exceptions
Description
The number of hardware abstraction layer (HAL) fw Delete Delete events. The number of hardware abstraction layer (HAL) fw Delete IOC down events. The number of hardware abstraction layer (HAL) fw Delete Exception events. The number of hardware abstraction layer (HAL) Offline Delete events. The number of hardware abstraction layer (HAL) Offline Online events. The number of hardware abstraction layer (HAL) offline IOC down events. The number of hardware abstraction layer (HAL) offline exception events. The number of hardware abstraction layer (HAL) delete f/w events. The number of hardware abstraction layer (HAL) Delete IOC down events. The number of hardware abstraction layer (HAL) delete exception events. The number of hardware abstraction layer (HAL) delete pend f/w responses. The number of hardware abstraction layer (HAL) delete pending IOC downs. The number of hardware abstraction layer (HAL) delete pending exceptions. The number of hardware abstraction layer (HAL) off-pending f/w responses. The number of hardware abstraction layer (HAL) off-pending deletes. The number of hardware abstraction layer (HAL) off-pending IOC downs. The number of hardware abstraction layer (HAL) off-pending exceptions. The number of hardware abstraction layer (HAL) IOC down offline events. The number of hardware abstraction layer (HAL) IOC down delete events. The number of hardware abstraction layer (HAL) IOC down online events. The number of hardware abstraction layer (HAL) IOC down exception events.
165

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

From 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
Teams list Team Name text box Team Mode list
Description
Lists existing teams. Lists the current team that was selected from the Teams 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. The teams media access control (MAC) address. The active Ethernet link between the host and the switch. 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) Lists all the ports that are available for selection. Lists the ports that were selected to be members of the team. Sets the primary interface for the team. 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.
MAC Address Active Link Transmit Policy list
Members list Selected Ports list Set Primary button Add button
Delete button
Click the Delete button beneath the Team Name text box to delete a team.
167
Field
Statistics button
Description
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 Add button Edit button Remove button Statistics button Apply button
The list of VLANs that are available to add, edit, remove, or display statistics. Click to launch the Add VLAN dialog box, where you can configure a new VLAN to be added to the VLANs list. Select an existing VLAN from the VLANs list and click to edit the VLAN. Select an existing VLAN from the VLANs list and click to edit the VLAN. Select an existing VLAN from the VLANs list and click to display the VLAN statistics. Click to apply your configuration changes.

VLAN configuration on page 59
168
Teaming Statistics dialog box (CNA only)
Teaming Statistics dialog box (CNA only)

The Teaming Statistics dialog box enables you to display statistics related to aggregated links (teams).

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

Field
Keep running data checkbox Polling frequency in seconds text box Start polling button Date Team ID Tx Packets Rx Packets Tx Error Packets Rx Error Packets Duration Status
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the Teaming statistics. The date the Teaming statistics were run. The Team ID associated with the team members. The number of transmitted packets. The number of received packets. The number of transmitted error packets. The number of received error packets. The length of time between byte transmission and reception. The connection status.

VLAN configuration on page 59
169
Test Log Details dialog box
Test Log Details dialog box

The Test Log Details dialog box enables you to view details about a selected port or protocol test.

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

Field
Time Test Status Configuration
Description
The date and time the test was run. The name of the test. The status of the test, for example, executing or pending. The name of the test component and its corresponding value. For example: Adapter world wide name Data pattern Frame count Port world wide name The test result, for example, test started or test complete.
Result

Running a hardware-level test using HCM Running a Fibre Channel protocol-level test using HCM
170

The Update Driver dialog box 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.
NOTE

Right-click a host from the device tree and select Update Driver from the list. The Update Driver dialog box displays.

Field
Select driver file to upgrade text box Browse button Start Installation button Installation Progress Details
Description
Enter the filename of the updated driver in the text box. Click to navigate to the location of the driver file to upgrade. After you have entered the upgraded driver file, click to install the new driver. Displays the driver installation progress details.

Driver update
171

The Virtual Port Creation dialog box enables you to create a new virtual port from a physical port or FCoE port.

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

Field
Physical Port WWN Virtual Port WWN text box
Description
Displays the world wide name for the physical port. 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. Click to auto-generate the virtual port world wide name. By default, auto-generate is selected. Click to regenerate the virtual port WWN and the virtual node WWN. 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. Enter the symbolic name associated with the virtual port. Enter the name for the virtual port. Enter a description for the virtual port.
Use auto-generated check box Generate Again button Virtual Node WWN text box
Symbolic Name text box Name text box Description text box

Virtual port configuration Creating a virtual port Deleting a virtual port
172
Virtual Port Deletion dialog box
Virtual Port Deletion dialog box

The Virtual Port Deletion dialog box enables you to delete an existing virtual port or FCoE port.

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 to continue.
NOTE
You cannot delete the base port.

Field
Deletion check box WWN Node WWN Symbolic Name Delete Selected button Delete All button Cancel button
Description
Check to select the virtual port to be deleted. The virtual ports world wide name. The virtual nodes world wide name. The symbolic name that is associated with the virtual port. Click to delete the selected virtual port. Click to delete all virtual ports that are displayed. Click to abort the operation.

173
Virtual Port Properties panel
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 panel

Select a virtual port from the device tree and click the Properties tab.

Field
Base Port Fabric Name FPMA MAC Address FC Address Node WWN Port WWN Preboot Created Roles State Symbolic name Switch IP address
Description
Indicates whether the virtual port is used as the base port. The name of the Fabric associated with the base port. The Fabric-Provided Ethernet MAC address created using the FC_ID assigned by the Fabric. The Fibre Channel address of the virtual port. The adapters world wide name. The ports world wide name. Indicates whether preboot was created on the virtual port (True or False). The role of the virtual port; for example, FCP Initiator. Indicates whether the virtual port is online or offline. The switchs symbolic name. The switchs IP address.
Using the panel

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

1. Select a virtual port from the device tree. 2. Select Monitor > Statistics > Virtual Port Statistics from the Host Connectivity Manager.

Field
Keep running data check box Polling frequency in seconds text box Start polling button Reset button Date FDISCs Sent FDISCs Accepts FDISC Retries FDISC Req Timeouts FDISC RSP Errors FDISC Bad Accepts FDISC Rejects FDISC Unknown Rsps FDISC Alloc Waits LOGOs Sent LOGO Accepts LOGO Rejects LOGO Rsp Errors LOGO Unknown RSPs LOGO Alloc Waits No NPIV Support Fabric Offlines Fabric Onlines Fabric Cleanups
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the V_Port statistics. Click to reset all of the statistics to 0. The date and time of the most recent reset. The number of Fabric discoveries sent. The number of times the system accepts Fabric discoveries. The number of times a Fabric discovery is attempted. The time that is required for a Fabric discovery. The number of Fabric discovery response errors. The number of bad accepts. The number of times the system rejects Fabric discoveries. The number of unknown Fabric discovery occurrences. The number of delayed Fabric discovery allocations. The number of times logouts occur. The number of times logouts are accepted. The number of times logouts are rejected. The number of logout response errors. The number of unknown logout occurrences. The number of delayed logout allocations. Indicates if there is no NPIV support. The number of fabrics that are offline. The number of fabrics that are online. The number of fabric cleanups.
175

176
VLAN Configuration dialog box (CNA only)
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.

1. Select an Ethernet port from the device tree. 2. Select Configure > VLAN Configuration from the main menu. OR Right-click the host and select VLAN Configuration from the list. The VLAN Configuration dialog displays.

Field
VLAN ID VLAN Name Add button Edit button Remove button
Description
Displays a list of configured VLAN identifiers. Displays a list of configured VLAN names. Click to launch the Add VLAN dialog box, which enables you to add a VLAN. Click to launch the Edit VLAN dialog box, which enables you to edit the VLAN name. Click to remove a VLAN. A confirmation error message displays.

VLAN configuration Adding a VLAN VLAN configuration conflicts Editing a VLAN Removing a VLAN
177
VLAN configuration - Add VLAN dialog box (CNA only)
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.

1. Select an Ethernet port from the device tree. 2. Select Configure > VLAN Configuration from the main menu. OR Right-click the host and select VLAN Configuration from the list.

Field
Port MAC VLAN ID text box VLAN Name text box Create Passthru checkbox
Description
The media access control address of the Ethernet port. The VLAN identifier. The VLAN name. Check to create a pass-through VLAN.

178
VLAN configuration - Edit VLAN dialog box (CNA only)
VLAN configuration - Edit VLAN dialog box (CNA only)

The Edit VLAN dialog box allows you to edit an existing VLAN.

1. Select an Ethernet port from the device tree. 2. Select Configure > VLAN Configuration from the main menu. OR Right-click the host and select VLAN Configuration from the list. 3. Click Edit on the VLAN Configuration dialog box.

Field
Port MAC VLAN ID text box VLAN Name text box
Description
The media access control address of the Ethernet port. The VLAN identifier. The VLAN name.

179
VLAN Statistics dialog box (CNA only)

The VLAN Statistics dialog box enables you to display statistics related to a selected virtual LAN. If 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.
NOTE

VLAN 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. 1. From the Ethernet port level, select an Ethernet port from the device tree. 2. Click Statistics on the Teaming Configuration dialog box. The VLAN Statistics dialog box displays.

Field
Keep running data checkbox Polling frequency in seconds text box Start polling button Date VLAN ID VLAN Name Tx Packets Rx Packets Tx Error Packets Rx Error Packets Duration Status
Description
Click to continue running statistical data. This is useful if you want to see a trend. Type a number for polling frequency. The range is between five and 3600 seconds and the default is five seconds. Click to manually poll the VLAN statistics. The date the VLAN statistics were run. The VLAN identifier. The VLAN name. The number of transmitted packets. The number of received packets. The number of transmitted error packets. The number of received error packets. The length of time between byte transmission and reception. The connection status.

VLAN configuration Adding a VLAN VLAN configuration conflicts Editing a VLAN
180
Removing a VLAN
181
182
Appendix
Brocade Command Utility
In this appendix
About the BCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCU commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . drvconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ethboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ethdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ethioc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ethlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ethport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fcdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fcoe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fcpim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ioc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pbind. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . qos (HBA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ratelim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
184 184 190 194 197 199 201 203 205 208 209 210 211 212 213 216 217 219 221 228 231 232 236 239 246 247 248 251 255 257
183
About the BCU
About the BCU

This 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 commands
The 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
bcu --help bcu <sub_command> --help Adapter commands bcu adapter --list --name --query --enable --disable Authentication commands bcu auth --show --policy --algo --secret --stats --statsclr <port_id> <port_id> <on | off> <port_id> <md5 | sha1 | ms | sm> <port_id> <secret_string> <port_id> <port_id> <ad_id > <adapter-name> <ad_id> <ad_id> <ad_id>
Operands
Synopsis
Lists all available sub-commands. Lists all details about the specific subcommand.
184
BCU commands
BIOS commands bcu bios --query --enable --disable Boot commands bcu boot --blunZone --update Converged Enhanced Ethernet (CEE) commands bcu cee --query --stats --statsclr Debug commands bcu debug --portlog --portlogclear --portlogctl 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 --tempshow --beacon --pciloopback --loopback --memtest --queuetest Driver configuration commands Note: Driver configuration commands are supported only on Windows operating systems. bcu drvconf --key --val <key_name> <value> <port_id> <ad_id> <port_id> <on | off> [<duration>] <port_id> -p <pattern> [-c <frame_count>] <port_id> [-t <loopback_type>] [-s <speed>] [-c <frame_count>] [-p <pattern>] <ad_id> <port_id> [-q <queue num>] <port_id> <port_id> <port_id> <enable | disable> <port_id> <port_id> <port_id> -c <cfg> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#> [adapter_id] <image_file> [-a] <port_id> <port_id> [-s speed] [-o auto|flash|firstlun] [-p pos] {-b pwwn,lun}* <port_id>
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
185
BCU commands
Ethernet Boot commands bcu ethboot --enable --disable --vlan --query Ethernet diagnostic commands bcu ethdiag --loopback <port_id> [-t <loopback-type>] [-c <frame_count>] [-p pattern] <port_id> <port_id> <port_id> <vlan_id> <port_id>
Ethernet I/O Controller (IOC) commands bcu ethioc --stats --statsclr --enable --disable --query Ethernet Log command bcu ethlog 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 --statsclr --vlanadd --vlanremove --vlanedit --vlanlist --vlanquery FC diagnostic commands bcu fcdiag --fcping --fctraceroute --fcecho --linkbeacon --scsitest FCoE VLAN commands bcu fcoe --enable --disable --stats --statsclr --vlanlist --vlanadd <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <vlan_tag> <port_id> <rpwwn> [-l lpwwn] <port_id> <rpwwn> [-l lpwwn] <port_id> <rpwwn> [-l lpwwn] <port_id> {on|off} <port_id> <rpwwn> [-l lpwwn] <port_id> <port_id> <port_id> <vlan_id> [<vlan_name>] <port_id> <vlan_id> <port_id> <vlan_id> <vlan_name> <port_id> <port_id> <vlan_id> --level <port_id> [Critical|Error|Warning|Info>] <port_id> <port_id> <port_id> <port_id> <port_id>
186
BCU commands
--vlandel --query FCP initiator mode commands bcu fcpim --query --stats --statsclr --pathtov --modstats --modstatsclr --profile_on --profile_off --ioperf I/O Controller (IOC) commands (Storage) bcu ioc --stats --statsclr --enable --disable --fwstats --fwstatsclr --intr --query Log commands bcu log --level
<port_id> <vlan_tag> <port_id> <vlan_tag>
<port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn> <port_id> <tov> <port_id> <port_id> <port_id> <port_id> <port_range> [-l | r] [-c count] [-i interval] <port_id> [-l [pwwn]] [-r [pwwn]] [-c count] [-i interval]
<port_id> <port_id> <port_id> <port_id> <ioc_id> <ioc_id> <port_id> <-coalesce | c> {on | off} [<-l <usecs>] [-d <usecs>] <port_id>
<port_id> [<Critical|Error|Warning|Info>] [-m <fw|hal|fcs|drv|aen|all>]
Logical port (lport) commands bcu lport --list --query --stats --statsclr Phy command bcu phy --update <ad_id | -a> <binary file> <port_id> <port_id> [-l <lpwwn>] <port_id> [-l <lpwwn>] <port_id> [-l <lpwwn>]
Port commands (physical port) bcu port --list --name --enable --disable --stats <port_id> [port_name] <port_id> <port_id> <port_id>
187
BCU commands
--statsclr --query --topology --speed --dfsize --trunk --perf Target persistent binding commands
<port_id> <port_id> <port_id> [p2p] <port_id> <speed> <port_id> [dfsize] <port_id> [<off|on <port_list>> <port_range|all> [-c count] [-i interval]
Note: Target persistent binding is available in Windows operating systems only. bcu pbind QoS commands Note: QoS commands apply to the 8 Gbps HBA only. bcu qos --enable --disable --query --stats --statsclr Target rate limiting commands bcu ratelim --enable --disable --query --stats --statsclr Remote port (rport) commands bcu rport --list --query --stats --statsclr --osname Teaming (Windows only) commands bcu team <port_id> [-l <lpwwn>] <port_id> rpwwn [-l <lpwwn>] <port_id> rpwwn [-l <lpwwn>] <port_id> rpwwn [-l <lpwwn>] <port_id> [-l <lpwwn>] <port_id> [-s <default-speed>] <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> --list <port_id>
--list --query --create --remove --addport --remport

--name --primary <team-name> <team-name> <team_mode> <port-id1> [<port_idn>] <team_name> <team-name> <port-id1> [..<port_idn>] <team-name> <port-id1> [..<port_idn>] <team_name> <new_team_name> <team_name> <port_id>
188
BCU commands
--xmit_policy --vlanadd --vlanremove --vlanedit --vlanlist --vlanquery Trunk commands bcu trunk --enable --disable --query Virtual port (vport) commands
<team_name> {l2|l3|l4} <team_name> <vlan_id> [<vlan_name>] <team_name> <vlan_id> <team_name> <vlan_id> <vlan_name> <team_name> <team_name> <vlan_id>
<ad_id> <ad_id> <ad_id>
Note: vport commands are not supported on Solaris platforms. bcu vport --create --delete --query --stats --statsclr Windows event log printing (Windows only) bcu winlog <port_id> vpwwn [-n <vnwwn>] [-s <sname>] <port_id> vpwwn <port_id> vpwwn <port_id> vpwwn <port_id> vpwwn
189
adapter
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. When 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. When invoked without operands, this command displays the usage. --enable ad_id --disable ad_id --list --name Enables the adapter. Specifies the ID of the adapter you want to enable. Disables the adapter. Specifies the ID of the adapter you want to disable. Lists all adapters in the system. For each adapter in the system, a brief summary line is displayed. 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. Queries or displays adapter information. Specifies the ID of the adapter for which you want to query.
NOTE
Operands
--query ad_id
190
adapter
Example
bcu adapter --list AD # NP 1 2 3 4 2 2 2 2 HW-path 0000:01:00 0000:09:00 0000:1c:00 0000:0a:00 Type FC FC CNA CNA Model-Info 825 825 1020 1020 Serial-num ALX0301D062 ALX0411D01K ARZ0351D00B ARZ0351D003 Name - - - --
bcu adapter --query 1 Example:# bcu adapter --query 1 Adapter Information: card type - FC model info: 825 OEM info: N/A num ports: 2 max speed: 8 Gbps chip revision: Rev-B hw path: 16:00 Serial Num: ALX0301D062 name: 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
191
adapter
bcu adapter --query 3 Adapter 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
192
adapter
bcu adapter --name 1 emc-fab3_ad5 adapter BRCD1234567s name set to emc_fab3_ad5 bcu adapter --name 1 adapter BRCD1234567s name is emc_fab3_ad5
See Also
ioc, port
193
auth
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:

Synopsis
Port ID Adapter ID Port world wide name Port Name Port hardware path
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 Operands
Configure and display authentication settings and status. --algo port_id Sets the authentication algorithm. Specifies the ID of the port for which you want to display information.
md|sha1|ms|sm
MD5 - A hashing algorithm that verifies a messages integrity using

--policy 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
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. Specifies the ID of the port for which you want to set the authentication policy. 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.
port_id on|off
194
auth
--secret port_id secret_string
Sets the shared secret. Note: You cannot clear the secret. Specifies the ID of the port for which you want to set the shared secret. 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. Displays the authentication settings and current status. Specifies the ID of the port for which you want to display information. Displays the authentication statistics. Specifies the ID of the port for which you want to display information. Clears the authentication statistics. Specifies the ID of the port for which you want to clear statistical information.
--show port_id --stats port_id --statsclr port_id Example
Here is an example of the output when authentication is successful:

bcu auth --show 1/0 port 1/0 Port Status Linkdown Auth success Hash Type MD5 Group Type DH-NULL
Here is an example of the output when authentication failed:

bcu auth --show 1/0 port 1/0 Port Status Linkdown Auth failed Hash Type MD5 Group Type DH-NULL
Here is an example of the output when authentication is not enabled:

bcu auth --show 1/0 port 1/0 Port Status Linkup Auth no_auth Hash Type Group Type
bcu auth --policy 2/1 on Authentication turned on bcu auth --policy 2/1 off Authentication turned off bcu auth --secret 5/0 mypasswd Authentication secret set bcu auth --stats 4/1 successes: 1 failures: 0
195
auth
auth_rx_stats: auth_rjts: 0 auth_negs: 0 auth_dones: 0 dhchap_challenges: 2 dhchap_replies: 0 dhchap_successes: 1 auth_tx_stats: auth_rjts: 0 auth_negs: 2 auth_dones: 0 dhchap_challenges: 0 dhchap_replies: 2 dhchap_successes: 0 auth --statsclr 4/1 Successfully cleared auth stats
See Also
None
196
bios
bios
Enables 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. Refer 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:
NOTE

Operands
Adapter ID Port ID Port WWN Port name Port hardware path Queries the boot-over-SAN configuration. Specifies the ID of the port for which you want to display information. Enables the boot over SAN configuration. Specifies the ID of the port for which you want to set the ports boot from SAN attributes. Specifies the port speed as auto-negotiate. Specifies the following options for obtaining boot LUN information. This list displays only if BIOS is enabled and Fabric Discovery is disabled.
--query port_id --enable port_id s speed
o auto|flash|firstlun
autoEnables fabric discovery. When enabled, the boot LUN

p pos identification is provided by the fabric. flashThe 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. firstlunThe host boots from the first LUN visible to the adapter that is discovered in the fabric.
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.
197
bios
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 systems management or configuration utility.
--disable port_id Example
Disables boot over SAN for the specified port, if enabled. Specifies the ID of the port for which you want to disable the boot over SAN configuration.
# bcu bios --query 1/0 boot over SAN: enabled port speed: Auto Boot luns discovered from the fabric boot lun 0: target wwn: 10:20:30:40:50:60:70:80 lun: 1000-a5d4-e800-0000 boot lun 1: target wwn: 10:20:30:40:50:60:70:80 lun: 0400-0000-0000-0000 boot lun 2: target wwn: 10:20:30:40:50:60:70:82 lun: 012c-0000-0000-0000 boot 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 cards BIOS: Enabled/Disabled Number of boot luns: 8 Boot LUN 0 : <Targets WWN>, <LUN> Boot LUN 1 : <Targets WWN>, <LUN> Boot LUN 2 : <Targets WWN>, <LUN> Boot LUN 3 : <Targets WWN>, <LUN> Boot LUN 4 : <Targets WWN>, <LUN> Boot LUN 5 : <Targets WWN>, <LUN> Boot LUN 6 : <Targets WWN>, <LUN> Boot LUN 7 : <Targets WWN>, <LUN> # bcu bios --enable 1/0 -b 11:22:33:44:55:66:77:88,0 boot cfg updated. bcu bios --enable 1/0 -s 1 -o auto -b 11:22:33:44:55:66:77:88,0 boot cfg updated. bcu bios --disable 1/0 boot over san disabled
See Also
boot
198
boot
boot
Allows the hosts 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. A 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. On 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 Operands Boot commands allows the hosts boot LUN information to be stored in the fabric zone database using a zone name and to update the boot code in flash. --blunZone -c cfg -p port_wwn -r rport_wwn -l lun_id -l lun# --update adapter_id Generates the zonecreate command to be run on the switch. Specifies the boot LUN (BLUN) of the boot command. Specifies the world wide name of the port. Specifies the world wide name of the remote port (rport). Specifies the ID of the logical unit. The LUN ID is specified as a hexadecimal byte; for example, FF. Specifies the number of the logical unit. The LUN number is specified as a hexadecimal, eight-byte string; for example, 09AABBCCDDEEFF00. Updates the boot code in flash. 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. Specifies the name of the boot code image file. 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.
NOTE
NOTE
image_file -a
199
boot
Example
bcu boot --update 1 brocade_adapter_boot_fw_v2-2-0-0 Boot code updated successfully A 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
200
cee
cee
Displays Converged Enhanced Ethernet (CEE) information on the port. The port_id could be any of the following:
Adapter ID or port ID Port name Port hardware path

NOTE
All 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 port_id --stats port_id --statsclr port_id Queries the CEE port information. Specifies the ID of the adapter (CNA). Displays the CEE port statistics. Specifies the ID of the converged network adapter for which you will print the statistics. Clears the CEE port statistics. Specifies the ID of the port for which you want to clear statistical information.
bcu cee --query 1/0 CEE status: Active ---------------------------------------Remote LLDP-Attributes ---------------------------------------Time to Live 120 Chassis ID 00:05:1e:54:18:ce Port ID Te 0/4 Port Desc -System Name -System Desc -System Cap BRIDGE ---------------------------------------Operational CEE Map: --------------------Priority Group Table <PGID: Weight %, PFC 0: Weight 0, PFC 1: Weight 80, PFC 2: Weight 20, PFC 3: Weight 0, PFC 4: Weight 0, PFC 5: Weight 0, PFC 6: Weight 0, PFC 7: Weight 0, PFC
status for the group> Disabled Enabled Disabled Disabled Disabled Disabled Disabled Disabled
201
cee
Priority Table CoS: 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: Up Network Priority: 0 DCBCXP version: CEE 2 bcu cee --stats 1/0 CEE Statistics: LLDP Tx Frames LLDP Rx Frames LLDP Rx Frames invalid LLDP Rx Frames new LLDP Rx unrecognized TLVs LLDP Rx shutdown TLVs LLDP remote info aged out DCBX phy link ups DCBX phy link downs DCBX Rx TLVs DCBX Rx TLVs invalid DCBX control TLV errors DCBX feature TLV errors DCBX new CEE cfg rcvd CEE status down CEE status up CEE hw cfg changed CEE invalid cfg
: : : : : : : : : : : : : : : : : :
560 563 0 6 6 0 0 2 1 4 0 0 0 2 1 2 2 2
bcu cee --statsclr 1/0 Successfully reset the port cee statistics
See Also
None
202
debug
debug
The debug commands gather support information on Fibre Channel components. The port ID can be any one of the following:

Synopsis
bcu debug --portlog <port_id> bcu debug --portlogclear <port_id> bcu debug --portlogctl <port_id> <enable | disable>
Captures 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. 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 --portlogclear port_id --portlogctl port_id enable disable Specifies the ID of the port for which you want to display the FC frame logs and other control messages. Clears the ports frame log. Specifies the ID of the port for which you want to clear the ports frame log. Enables or disables the portlog. Specifies the ID of the port for which you want to enable or disable the portlog. Enables the portlogclear command. Disables the portlogclear command.
Example
bcu debug --portlog 10/0 Total records present = 14 --------------------------------------------------------------------------time event port code args --------------------------------------------------------------------------08:35:28.430 fwm 10/0 00 00001234, 00050001 08:35:28.431 mbox 10/0 01 00001234, 00050001 08:35:28.433 ioctl 10/0 90 101d9910,0 08:35:28.433 Tx 10/0 164 02fffffd, 00fffffd, 0005ffff, 10000000 08:35:28.433 Rx 10/0 0 c0fffffd, 00fffffd, 00050006 08:35:28.433 Rx 10/0 164 03fffffd, 00fffffd, 00050006, 02000000 08:35:28.433 Tx 10/0 0 c0fffffd, 00ffffd, 00050006 08:35:28.433 ioctl 10/0 91 103646d8, 0 08:35:28.466 ioctl 10/0 a7 3c, 1 08:35:28.483 Tx 10/0 96 02fffffd, 00fffffd, 0006ffff, 11100060
203
debug
08:35:28.483 Rx 10/0 0 c0fffffd, 00fffffd, 00060007 08:35:28.483 Rx 10/0 96 03fffffd, 00fffffd, 00060007, 02100060 08:35:28.483 Tx 10/0 0 c0fffffd, 00fffffd, 00060007 08:35:28.483 ioctl 10/0 a1 0,0 --------------------------------------------------------------------------# bcu debug --portlog 1/1 Total records present = 26 --------------------------------------------------------------------------Time Module Event Len Log info --------------------------------------------------------------------------13fe083a Driver drvstrt 0 Driver Attach 14471130 HAL pstchg 0 Port Linkup 1447135f FCXP Tx 140 01290000,00000000,00080000,03000000 14471361 FCXP Tx 32 01290000,00000000,00080000,62000000 14471498 FCXP Rx 116 01980000,6c000000,051e7609,02000000 1447149c FCXP Tx 301 20290000,00000000,00080000,01000000 1447150d FCXP Rx 4 01980000,6d000000,051e7609,02000000 1447190e FCXP Rx 16 20980000,6e000000,051e7609,01000000 14471910 FCXP Tx 76 20290000,00000000,00080000,01000000 14471a29 FCXP Rx 16 20980000,6f000000,051e7609,01000000 14471a2b FCXP Tx 48 20290000,00000000,00080000,01000000 14471b28 FCXP Rx 16 20980000,70000000,051e7609,01000000 14471b2a FCXP Tx 44 20290000,00000000,00080000,01000000 14471b2d FCXP Tx 140 01290000,00000000,00080000,03000000 14471c11 FCXP Rx 116 01980000,71000000,051e7609,02000000 14471c18 FCXP Tx 176 20290000,00000000,00080000,01000000 14471c19 FCXP Tx 48 20290000,00000000,00080000,01000000 14471d1a FCXP Rx 16 20980000,72000000,051e7609,01000000 14471e0e FCXP Rx 16 20980000,73000000,051e7609,01000000 14472027 FCXP Rx 788 20980000,74000000,051e7609,01000000 14472029 FCXP Tx 48 20290000,00000000,00080000,01000000 14472144 FCXP Rx 24 20980000,75000000,051e7609,01000000 14613597 FCXP Tx 176 20290000,00000000,00080000,01000000 14613745 FCXP Rx 16 20980000,76000000,051e7609,01000000 147fb9b6 FCXP Tx 176 20290000,00000000,00080000,01000000 147fbb68 FCXP Rx 16 20980000,77000000,051e7609,01000000 --------------------------------------------------------------------------bcu debug --portlogclear 1/0 portlog cleared bcu debug --portlogctl 1/0 enable portlog enabled bcu debug --portlogctl 1/0 disable portlog disabled bcu debug --portlogctl 1/0 disable portlog disabled
See Also
None
204
diag
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:
NOTE
The 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 Operands Displays the group of diagnostic commands that are non-destructive and indicates when the adapter is running at a normal operation state. --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. Specifies the ID of the port on which you want to display the SFP attributes. Reads the adapters temperature sensor registers of the adapter. This is an online diagnostic test. Specifies the ID of the adapter for which you want to display temperature sensor registers. Options include the following temperature settings:
port_id --tempshow ad_id
below min normal above max sensor fault
205
diag
--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. Specifies the ID of the port for which you want to beacon. Turns end-to-end beaconing on or off. 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. Sends a health check message back and forth from the host to the IO Controller (IOC) through the host engine over the PCI. Specifies the ID of the port for which you want to send a health check message. Displays the data pattern. Tests the data path from the IOC to the desired network loopback point (internal, serdes, external) and back. This is an offline diagnostic test. Specifies the ID of the port on which you want to run a loopback test.
port_id on | off duration
--pciloopback port_id -p pattern --loopback port_id
-c frame_count Specifies the frame count.
-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 --memtest ad_id --queuetest port_id -q queue num Specifies the pattern (must be one hex word). Performs a generic memory test using different algorithms. Specifies the ID of the adapter on which you want to test the memory blocks. Sends a health check message from the host to firmware through message queues memory mapped over the PCI. This is an online diagnostic test. Specifies the ID of the port on which you want to run a queuetest. Specifies the queue number from 0 to 3. If the queue number is not specified, all queues are tested.
206
diag
Example
bcu diag --sfpshow 1/0 Identifier: 3 SFP Connector: 7 LC Transceiver: 540c402000000000 200,400,800_MB/s M5,M6,SN,I, Encoding: 1 8B10B Baud 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: BROCADE Vendor OUI: 00:05:1e Vendor PN: 57-1000012-01 Vendor Rev: A Wavelength: 352 (units nm) Options: 001a Rx_LOS TX_FAULT TX_DISABLE BR Max: 0 BR Min: 0 Serial No: UAA40808000004A Date Code: 080224 Temperature: 37.593750 Centigrade Current: 6.348000 mAmps Voltage: 3.419400 V RX Power: 0.467000 mW Tx Power: 0.562000 mW Alarm/Warning: 00000000
See Also
fcdiag
207
drvconf
drvconf
Sets the basic parameters for the driver to function properly. Note: The drvconf commands are supported on Windows platforms only. Synopsis Description bcu --drvconf [-key <key_name>] [--val <value>] Changes the values for basic Windows registry entry parameters. You 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 --val value The name of the bfa key. Sets the value of the bfa key. See below for possible values and default settings.
NOTE
Possible key name and value ranges are as follows:

See Also
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
None
208
ethboot
ethboot
A 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 Operands Enables or disables Ethernet Boot on the port or configures the VLAN ID to use for the specified port. --enable port_id --disable port_id --vlan port_id --query port_id Example Enables Ethernet Boot (PXE) for the specified port. Specifies the ID of the port on which you want to enable PXE. Disables the Ethernet Boot (PXE) for the specified port. Specifies the ID of the port on which you want to disable PXE. Sets the VLAN ID to be used during Ethernet Boot (PXE) for the specified port. Specifies the ID of the port on which you want to set the VLAN ID. The supported VLAN ID range is 0-4094. Displays the Ethernet Boot (PXE) configuration on the specified port. Specifies the ID of the port on which you want to display the PXE configuration.
bcu ethboot --query 1/0 Boot Enable: Enabled VLAN ID: 0
See Also
ethdiag ethioc ethlog ethport
209
ethdiag
ethdiag
The 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 Description Operands bcu ethdiag --loopback <port_id> [-t <loopback_type] [-c <count>] [-p pattern] Runs the Ethernet diagnostic loopback test and indicates when the adapter is running at a normal operation state. --loopback port_id Runs the port loopback test. You must disable the Ethernet port prior to executing the loopback test. 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 -p pattern Example 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. Specifies the pattern (must be one hex word), with no 0x prefix.
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/0 bcu ethdiag --loopback 1/0 -t ext -c 1024 -p test1
See Also
port
210
ethioc
ethioc
Displays or clears Ethernet IOC statistics. The port_id could be any of the following:
Adapter ID or port ID 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 Operands Enables or disables Ethernet IOC on the port and displays and clears Ethernet IOC statistics. --enable port_id --disable port_id --query port_id --stats port_id --statsclr port_id Example Enables the Ethernet IOC, if it is currently disabled. Specifies the ID of the Ethernet port you want to enable. Disables the Ethernet IOC, if it is currently enabled. Specifies the ID of the Ethernet port you want to disable. Queries the attributes of the Ethernet IOC. Specifies the ID of the Ethernet port you want to query. Displays the Ethernet IOC statistics. Specifies the ID of the Ethernet port for which you will display the statistics. Clears the Ethernet IOC level statistics. Specifies the ID of the Ethernet port for which you will reset the statistics.
bcu ethioc --stats 1/0 IOC host statistics: mailbox interrupts: 40771 enable events: 1 disable events: 0 heartbeat failures: 0 firmware boots: 0 stats timeouts: 0 bcu ethioc --statsclr 1/0 Successfully reset the ioc level stats
See Also
None
211
ethlog
ethlog
Sets the log level for each Ethernet driver. The port_id could be any of the following:
Adapter ID or port ID Ethernet port name Ethernet port hardware path

Synopsis Description bcu ethlog --level <port_id> [<Critical|Error|Warning|Info>] 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. --level port_id Sets the log level of the Ethernet driver. Specifies the ID of the Ethernet port for which you will set the log level. level 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 --level Log level is Info bcu ethlog 1/0 --level Warning Log level set to Warning
Operands
Critical|Error|Warning|Info
See Also
None
212
ethport
ethport
With 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 doesnt belong to any VLAN but instead contains 802.1x priority information. All 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 Operands 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. --vlanadd port_id vlan_id vlan_name --vlanremove port_id vlan_id --vlanedit port_id vlan_id --vlanlist port_id vlan_id --vlanquery port_id vlan_id --stats Configures a new VLAN ID on the port. Specifies the ID of the port on which you want to add a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Specifies the VLAN name. Removes an existing VLAN ID from the port. Specifies the ID of the port from which you want to remove a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Modifies an existing VLAN on the port. Specifies the ID of the port on which you want to modify a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Lists the configured VLANs on the port. Specifies the ID of the port on which you want to list configured VLANs. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Displays the VLAN information on the port. Specifies the ID of the port for which you want to display the VLAN details. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Displays Ethernet port statistics.
NOTE
new_vlan_name Specifies a different name for the VLAN.
213
ethport
port_id --statsclr port_id Example
Specifies the ID of the Ethernet port for which you want to display statistics. Clears Ethernet port statistics. Specifies the ID of the Ethernet port for which you want clear statistics.
bcu ethport vlanlist 1/0
# bcu ethport --stats 4/0 Ethernet 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:0 rx dropped:0 rx alloc failed:0 rx checksum errors:0 rx mac errors:0 rx small packets:0 rx large packets:0 rx lro :0 rx lro flush:0 rx low rxbuf count:0 tx lso4 :0 tx lso6 :0 tx lso errors:0 tx tcp cso:0 tx udp cso:0 tx ip4 cso:0 tx checksum help:0 tx checksum help errors :0 tx map errors:0 tx res drops:0 tx small packets:0 tx large packets:0 tx out of wis count:0 tx wi waitq count:0 tx ctxt waitq count:0
214
ethport
tx max nbs per nbl:0 link toggles:0 cee toggles:0 mbox intr disables:0 mbox_intr_enables:0 tx stops:0 tx wakeups:0 tx res stops:0 tx hardware stop:0 rx schedules:0 rx hardware stops:0 rx resumes:0 rx rss config count:0 hardware stats updates:0 bcu ethport --statsclr 4/0 ethport stats cleared bcu ethboot --query 1/0 Boot Enable: Enabled VLAN 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
215
fabric
fabric
Prints and resets Fabric statistics. Synopsis bcu fabric --stats <port_id> bcu fabric --statsclr <port_id> Description Operands Displays or clears Fabric statistics. --stats port_id --statsclr port_id Example Prints the fabric statistics. Specifies the ID of the fabric port for which you will print the statistics. Resets the fabric statistics. Specifies the ID of the fabric port for which you will reset the statistics.
bcu fabric --stats 1/0 Fabric Stats: FLOGI sent: 114 FLOGI rsp errors: 0 FLOGI accept errors: 0 FLOGI accepts: 58 FLOGI rejects: 0 FLOGI unknown rsp: 0 FLOGI alloc wait: 0 FLOGI received: 0 FLOGI rejected: 0 fabric offlines: 57 fabric onlines: 58
See Also
None
216
fcdiag
fcdiag
Runs diagnostic tests on Fibre Channel components. The 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 Operands Fibre Channel diagnostic tests evaluate the integrity of Fibre Channel components. --fcping port_id rpwwn -l lpwwn --fctraceroute port_id rpwwn -l lpwwn --fcecho port_id rpwwn -l lpwwn --linkbeacon port_id on | off Determines the basic connectivity between two Fibre Channel network points and monitors and measures network latency. Specifies the ID of the port to which you want to issue a ping command. Specifies the remote port world wide name to which you want to issue a ping command. 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. Reports on a SAN path, including node hops and latency data. Specifies the ID of the port on which you want to run the fctraceroute command. Specifies the remote port world wide name. 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. Sends an FC Echo Extended Link Services (ELS) request to a remote port. Specifies the ID of the port from which you want to run the fcecho command. Specifies the remote port world wide name on which you want to run the fcecho diagnostic test. 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. Blinks (toggles) the link beacon. Specifies the ID of the port for which you want to run the linkbeacon command. Specifies if the linkbeacon test is on or off.
NOTE
217
fcdiag
--scsitest port_id rpwwn -l lpwwn Example
Tests the SCSI components and displays the discovered LUN information. Specifies the ID of the port for which you want to run the scsitest command. Specifies the remote port world wide name. 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.
#bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:eb Error: Reject from attached fabric #bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:eb FC Traceroute completed successfully. Path Info: Switch WWN Switch Domain ID 127 127 Ingress Port # Egress Port #
10:00:08:00:88:03:31:8b 10:00:08:00:88:03:31:8b
5 11
11 5
#bcu fcdiag --fctraceroute 2/0 50:05:07:63:04:13:46:e1 FC Traceroute Failed. Reason : Destination Port not in Fabric #bcu fcdiag --fcecho 2/0 50:05:07:63:04:13:46:eb FC ECHO completed successfully #bcu fcdiag --scsitest 1/0 20:20:00:11:0d:ef:f7:00 LUN# Type/ Qualifier 00/000 Vendor Product Revision Size* LUN status** Online
SANBlaze
VirtuaLUN Disk
v5.5
939800
*Size is expressed in bytes from Read capacity response (Max LBA* block size) **Status: All commands successfully expressed by Online One or more commands failed expressed by <SCSIcommand><SCSI status>/<ASC value>/<ASCQ value>. ASC and ASCQ valid for Check Condition. RL: Report LUN SI: SCSI Inquiry RC: Read Capacity command RD: Read (10) command
See Also
diag
218
fcoe
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 Operands Enables or disables the Fibre Channel over Ethernet (FCoE) port. --enable port_id --disable port_id --stats port_id --statsclr port_id Example Enables the FCoE port, if currently disabled. This command has no effect if the FCoE port is already enabled. Specifies the ID of the FCoE port that you want to enable. Disables the FCoE port, if currently enabled. Specifies the ID of the FCoE port that you want to disable. Displays the statistics for the FCoE port. Specifies the FCoE port for which you want to view statistics. Clears the statistics for the FCoE port. Specifies the FCoE port on which you want to clear statistics.
#bcu fcoe --enable 2/1 Port enabled. #bcu fcoe -enable 2/1 ERROR: Port is already enabled. # bcu fcoe --stats 2/1 FCoE port statistics: Seconds since stats reset CEE link up CEE link down FIP link up FIP link down FIP failures Invalid mac assignments Vlan requests Vlan notifications Vlan notification errors Vlan request timeouts Vlan invalids
: : : : : : : : : : : :
0 1 0 1 0 0 0 1 1 0 0 0
219
fcoe
Discovery requests Discovery responses Discovery error frames Discovery unsolicited Discovery timeouts Discovery FCF not avail FIP link service req unsupp. FIP link service req errors FIP logo Clear virtual link requests FIP operation unsupp. FIP untagged frames Tx FCoE unicast frames Tx FCoE unicast vlan frames Tx FCoE unicast octets Tx FCoE mutlicast frames Tx FCoE mutlicast vlan frames Tx FCoE multicast octets Tx FCoE broadcast frames Tx FCoE broadcast vlan frames Tx FCoE broadcast octets Tx timeouts Transmit parity err Transmit FID parity err Tx pause frames Tx zero pause frames Tx first pause frames Rx pause frames Rx zero pause frames Rx first pause frames Rx unicast octets Rx unicast frames Rx unicast vlan frames Rx multicast octets Rx multicast frames Rx multicast vlan frames Rx broadcast octests Rx broadcast frames Rx broadcast vlan frames
: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :
1 1 0 0 0 0 0 0 0 0 0 0 12 11 1868 42 0 3872 0 0 0 0 0 0 0 0 0 0 0 0 4264 14 14 4550 38 0 0 0 0
#bcu fcoe -statsclr 2/1 Successfully reset the FCoE stats.
See Also
None.
220
fcpim
fcpim
Enables 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 Operands Enables or disables fast failover of the Fibre Channel Port (FCP) initiator mode I/O and displays or clears statistics. --stats port_id rpwwn -l lpwwn --statclr port_id rpwwn -l lpwwn --pathtov port_id tov Displays statistics related to the Fibre Channel port initiator mode. Specifies the ID of the port for which you want to display statistical information. Specifies the world wide name of the remote port for which you want to display statistics. Specifies the world wide name of the logical port or vport for which you want to display statistics. Clears statistics related to the Fibre Channel port initiator mode. Specifies the ID of the port for which you want to clear statistical information. Specifies the world wide name of the remote port for which you want to clear statistics. Specifies the world wide name of the logical port or vport for which you want to clear statistics. Sets the path time out value for the target device. Specifies the ID of the port for which you want to query. 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.
221
fcpim
--query port_id rpwwn -l lpwwn --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 lpwwn -r rpwwn Example With profile off:
Queries the fcpim attributes. Specifies the ID of the port for which you want to query. Specifies the world wide name of the remote port for which you want to query. Specifies the world wide name of the local port or vport for which you want to query. Displays statistics related to the Fibre Channel port initiator module. Specifies the ID of the module for which you want to display statistical information. Clears statistics related to the Fibre Channel port initiator mode. Specifies the ID of the module for which you want to clear statistical information. 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). Specifies the ID of the module on which you want to set the profiling to on. Sets the port IO profiling off. Specifies the ID of the module on which you want to set the profiling to off. Sets the performance attributes for the port. Specifies the range of ports on which you want to monitor performance. Sets if the port is a local port or a remote port. Specifies how many times the output will be printed on the screen. Specifies the output interval, in seconds. Specifies the ID of the port on which you want to monitor performance. Specifies the local ports port world wide name for which you want to monitor performance. If the lpwwn is not specified, the base port is used. Specifies the remote ports port world wide name for which you want to monitor performance. If the rpwwn is not specified, the base port is used.
bcu fcpim --query 1/1 20:01:00:11:0d:6f:6b:45 FCP IM state: online Data retransmission support: Supported REC support: Supported Task retry identification support: Not Supported Confirmed completions support: Supported IO profile support: OFF
With profile on:

# bcu fcpim --query 1/0 20:01:00:11:0d:8f:31:00 FCP IM state : online Data retransmission support : Not Supported REC support : Supported Task retry identification support : Not Supported Confirmed completions support : Not Supported
222
fcpim
IO profile start time IO completions: < 512B 512B to < 1K 1K to < 2K 2K to < 4K 4K to < 8K 8K to < 16K 16K to < 32K 32K to < 64K 64K to < 128K 128K to < 256K 256K to < 512K 512K to < 1M 1M to < 2M > 2M
: 1284043686 : : : : : : : : : : : : : : 0 0 0 0 0 0 0 0 0 0 0 0 0 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
223
fcpim
max average 512K to < 1M min max average 1M to < 2M min max average > 2M min max average
: 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0
# bcu fcpim --stats 1/0 20:01:00:11:0d:8f:31:00 ITNIM Stats: num rport online num rport offline num prli sent out num fcxp alloc waits num prli rsp errors num prli rsp accepts rport is an initiator prli rsp parsing errors num prli rsp rejects num timeouts detected num sler notification from BFA
: : : : : : : : : : :
1 0 1 0 0 1 0 0 0 0 0
HAL fcpim statistics Total IO Requests : 0 Data in-bound requests : 0 Data out-bound requests : 0 Total IO Completions : 0 Write data transfered in bytes : 0 Read data transfered in bytes : 0 Slowpath IO completions : 0 IO underrun : 0 IO overrun : 0 IO Request-Q wait : 0 IO Request-Q wait done : 0 No free IO tag : 0 IO timeouts : 0 IO failure due to target offline: 0 IO protocol errors : 0 IO SBC-3 protection errors : 0 fcp-2 error recovery failed : 0 Delayed freeing of IO tag : 0 Host IO abort requests : 0 Host IO abort completions : 0 IO clean-up requests : 0 IO path tov expired : 0 IO abort completions : 0 IO cleaned-up due to IOC down : 0 IO comp with unknown tags : 0 Abort request due to TM command : 0 Abort completion due to TM command: 0 IT Nexus create requests : 0 IT Nexus FW create requests : 0
224
fcpim
IT Nexus FW create completions IT Nexus onlines IT Nexus offlines IT Nexus FW delete requests IT Nexus FW delete completions IT Nexus delete requests SLER events Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup failure No free TM tag TM Request-Q wait TM Request-Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions Total data transfered in bytes # bcu fcpim --modstats 1/0 FCPIM module Stats: FCPIM module Active ITNIM Stats:
: : : : : : : : : : : : : : : : : : : :
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Total IO Requests : 0 Data in-bound requests : 0 Data out-bound requests : 0 Total IO Completions : 0 Write data transfered in bytes : 0 Read data transfered in bytes : 0 Slowpath IO completions : 0 IO underrun : 0 IO overrun : 0 IO Request-Q wait : 0 IO Request-Q wait done : 0 No free IO tag : 0 IO timeouts : 0 IO failure due to target offline: 0 IO protocol errors : 0 IO SBC-3 protection errors : 0 fcp-2 error recovery failed : 0 Delayed freeing of IO tag : 0 Host IO abort requests : 0 Host IO abort completions : 0 IO clean-up requests : 0 IO path tov expired : 0 IO abort completions : 0 IO cleaned-up due to IOC down : 0 IO comp with unknown tags : 0 Abort request due to TM command : 0 Abort completion due to TM command: 0 IT Nexus create requests : 0 IT Nexus FW create requests : 0 IT Nexus FW create completions : 0 IT Nexus onlines : 0 IT Nexus offlines : 0 IT Nexus FW delete requests : 0 IT Nexus FW delete completions : 0
225
fcpim
IT Nexus delete requests SLER events Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup failure No free TM tag TM Request-Q wait TM Request-Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions Total data transfered in bytes
: : : : : : : : : : : : : : :
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
FCPIM module Deleted ITNIM Stats: Aborted IO requests IO timeouts IO retry for SQ error recovery Delayed freeing of IO resources Host IO abort requests Total IO count IO cleaned-up due to IOC down TM cleaned-up due to IOC down : : : : : : : : 127 0 0 129 2 1301027 0 0
bcu fcpim --statsclr 1/0 50:05:00:05:1e:13:9c:00 Successfully reset the fcpim level stats bcu fcpim --modstatsclr 1/1 Successfully reset the fcpim modstats Warning: All active ITNIM stats are cleared. bcu fcpim --pathtov 1/0 1 path timeout is set to 1 bcu fcpim --profile_on 1/1 fcpim profile is ON. Warning: fcpim profile ON will affect IO Performance. # bcu fcpim --profile_off 1/1 fcpim profile off # bcu fcpim --ioperf 1/0-1/1 Port 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
226
fcpim
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
227
ioc
ioc
Enables 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 port_id --disable port_id --fwstats ioc_id --fwstatsclr ioc_id --intr port_id coalesce | c on | off Enables the IO Controller (IOC). If the IOC is already enabled, the command is ignored. Specifies the port of the IO Controller (IOC) you want to enable. 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. Specifies the ID of the port you want to disable. Displays the IOC level statistics on the specified port. Specifies the ID of the I/O Controller firmware for which you want to display statistical information. Clears the IOC firmware level statistics on the specified I/O Controller. Specifies the ID of the I/O Controller firmware for which you want to clear statistical information. Sets the interrupt attributes for the port. Specifies the ID of the port on which you want to set interrupt attributes. Sets the coalesce flag. Sets the ports interrupt attributes. Possible values are on or off.
228
ioc
-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. 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. Queries the attributes of the Storage IOC with the IOC ID. Specifies the port of the IO Controller (IOC) you want to enable. Displays the IOC level statistics on the specified port. Specifies the ID of the port for which you want to display information. Clears the IOC level statistics on the specified port. Specifies the ID of the port for which you want to clear statistical information.
-d delay
--query ioc_id --stats port_id --statsclr port_id
Example
#bcu ioc --query 1/0 chip rev: manufacturer: serial#: model_descr: pwwn: nwwn: f/w ver: bios ver: port count: status is: ssid: vendor id: device id: pci function: IOC type: interrupt coalescing: interrupt delay: interrupt latency: # bcu ioc --stats 1/0 Num suspends: 7 bcu ioc --statsclr 1/0 ioc stats cleared. bcu ioc --enable 1/0 ioc is enabled bcu ioc --enable ad1_p0 ioc is already enabled bcu ioc --disable 1/0 ioc is disabled
Rev-B Brocade ARZ0351D00B 1020 10:00:00:05:1e:55:1d:3c 20:00:00:05:1e:55:1d:3c pvt_bld03 05/05/2009 15.12.12 2 operational 0x0014 0x1657 0x0014 0 on 25 us 0 us
bcu ioc --disable ad1_p0 ioc is already disabled bcu --intr 1/0 --coalesce off interrupt coalescing has been turned off
229
ioc
bcu ioc --intr 1/0 --coalesce on The intr settings have been configured with value(s): Coalesce: on bcu ioc --intr 1/0 --coalesce on 12 19 The intr settings have been configured with value(s): Coalesce: on Delay: 19 (micro-seconds) Latency: 12 (micro-seconds)
See Also
adapter lport
230
log
log
Sets the log level for each module. If no log level is specified, the current level is used. Synopsis Description bcu log --level <port_id> [<Critical|Error|Warning|Info>] [-m <fw|hal|fcs|drv|aen|all>] 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. --level port_id Specifies the number of messages logged by the host, which depends on the predetermined logging level. Specifies the ID of the port for which you want to set the log level. 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
Operands
Critical|Error|Warning|Info
Example
#bcu log --level 2/0 FW log level is Warning HAL log level is Warning FCS log level is Warning DRV log level is Warning AEN log level is Warning #bcu log --level 2/0 info Log level set to Info #bcu log --level 2/0 FW log level is Info HAL log level is Info FCS log level is Info DRV log level is Info AEN log level is Info
See Also
None
231
lport
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 ports port world wide name Logical port NWWN - logical ports 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 port_id --query port_id -l lpwwn --stats port_id -l lpwwn --statsclr port_id -l lpwwn Lists all the lports for a specified port. Specifies the ID of the port for which you want to display information. Lists the attributes of the logical port. Specifies the ID of the port for which you want to display information. Specifies the logical ports world wide name for which you want to display information. If the lpwwn is not specified, the base port is used. Displays the logical ports statistics. Specifies the ID of the port for which you want to display statistical information. Specifies the logical ports world wide name for which you want to display statistical information. If the lpwwn is not specified, the base port is used. Clears the logical ports statistics. Specifies the ID of the port for which you want to clear statistical information. Specifies the logical ports port world wide name for which you want to clear statistical information. If the lpwwn is not specified, the base port is used.
232
lport
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_port0 State: Online FC address: 0c0100 Port wwn: aa:bb:cc:dd:ee:ff:aa:bb Node wwn: cc:dd:cc:aa:ff:cc:aa:ff Symbolic name: FC4 Role: fcpim ipfc bcu lport --query hba5_port0 - 1 01:bb:cc:dd:ee:ff:00:01 State: Online FC address: 0c0101 Port wwn: 01:bb:cc:dd:ee:ff:00:01 Node wwn: 01:bb:cc:dd:ee:ff:00:00 # bcu lport --stats 1/0 ns_plogi_sent ns_plogi_rsp_err ns_plogi_acc_err ns_plogi_accepts NS command rejects ns_plogi_unknown_rsp ns_plogi_alloc_wait NS command retries NS command timeouts ns_rspnid_sent ns_rspnid_accepts ns_rspnid_rsp_err ns_rspnid_rejects ns_rspnid_alloc_wait ns_rftid_sent ns_rftid_accepts ns_rftid_rsp_err ns_rftid_rejects ns_rftid_alloc_wait ns_rffid_sent ns_rffid_accepts ns_rffid_rsp_err ns_rffid_rejects ns_rffid_alloc_wait ns_gidft_sent ns_gidft_accepts ns_gidft_rsp_err ns_gidft_rejects
: : : : : : : : : : : : : : : : : : : : : : : : : : : :
3 0 0 3 0 0 0 0 0 3 3 0 0 0 3 3 0 0 0 3 3 0 0 0 3 3 0 0
233
lport
ns_gidft_unknown_rsp : 0 ns_gidft_alloc_wait : 0 MS command retries : 0 MS command timeouts : 0 ms_plogi_sent : 3 ms_plogi_rsp_err : 0 ms_plogi_acc_err : 0 ms_plogi_accepts : 3 MS command rejects : 0 ms_plogi_unknown_rsp : 0 ms_plogi_alloc_wait : 0 Num of RSCN received : 0 Num portid format RSCN : 0 Unsolicited recv frames : 0 Dropped received frames : 0 Received plogi : 0 Received prli : 0 Received adisc : 0 Received prlo : 0 Received logo : 0 Received rpsc : 0 Received unhandled ELS : 0 Rport plogi retry timeout count : 8 Deleted rport (max retry of plogi): 0 Total IO Requests : 0 Data in-bound requests : 0 Data out-bound requests : 0 Total IO Completions : 0 Write data transfered in bytes : 0 Read data transfered in bytes : 0 Slowpath IO completions : 0 IO underrun : 0 IO overrun : 0 IO Request-Q wait : 0 IO Request-Q wait done : 0 No free IO tag : 0 IO timeouts : 0 IO failure due to target offline: 0 IO protocol errors : 0 IO SBC-3 protection errors : 0 fcp-2 error recovery failed : 0 Delayed freeing of IO tag : 0 Host IO abort requests : 0 Host IO abort completions : 0 IO clean-up requests : 0 IO path tov expired : 0 IO abort completions : 0 IO cleaned-up due to IOC down : 0 IO comp with unknown tags : 0 Abort request due to TM command : 0 Abort completion due to TM command: 0 IT Nexus create requests : 0 IT Nexus FW create requests : 0 IT Nexus FW create completions : 0 IT Nexus onlines : 0 IT Nexus offlines : 0 IT Nexus FW delete requests : 0 IT Nexus FW delete completions : 0 IT Nexus delete requests : 0 SLER events : 0
234
lport
Num IOC disables IT Nexus cleanup completions TM Requests TM Completions TM initiated IO cleanup success TM initiated IO cleanup failure No free TM tag TM Request-Q wait TM Request-Q wait done TM cleaned-up due to IOC down TM cleanup requests TM cleanup completions Total data transfered in bytes # bcu lport --statsclr hba5_port0 lport stats cleared
: : : : : : : : : : : : :
0 0 0 0 0 0 0 0 0 0 0 0 0
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/0 Port FC Addr: 860e01 Port Type: Base Port (State: Linkup) Port PWWN: 10:00:00:05:1e:8e:b6:02 Port NWWN: 20:00:00:05:1e:8e:b6:02 Symbolic name: 1020 | 2.3.0.0 | HB081222-RH4u7x86 | Red Hat Enterprise Linux AS release 4 (Nahant Update 7) | Role: FCP Initiator Fabric Name: 10:00:00:05:1e:90:13:98 Switch IP Addr: 10.32.82.134 FPMA MAC Addr: 0e:fc:00:86:0e:01 825 bcu lport --query [root@HB081222-RH4u7x86 ~]# bcu lport --query 2/0 Port FC Addr: 8a0600 Port Type: Base Port (State: Linkup) Port PWWN: 10:00:00:05:1e:0f:1a:b1 Port NWWN: 20:00:00:05:1e:0f:1a:b1 Symbolic name: 825 | 2.3.0.0 | HB081222-RH4u7x86 | Red Hat Enterprise Linux AS release 4 (Nahant Update 7) | Role: FCP Initiator Fabric Name: 10:00:00:05:1e:05:09:29 Switch IP Addr: 10.32.82.138
See Also
None
235
pbind
pbind
Enables 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 Description bcu pbind --list <port_id> Queries the list of mappings or clears existing persistent binding settings. The pbind command is only supported on the Windows platform. Operands --list port_id See Also None Queries the list of mappings from the persistent binding module. Specifies the ID of the port for which you want to display information.
NOTE
236
phy
phy
The 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. PHY 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 Operands Updates the PHY firmware and queries the attributes and statistics of the external PHY module. --update ad_id | a Updates the firmware on a specified adapter. 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. Specifies the firmware image file that will be used to update the specified adapter. Displays the PHY module attributes for the specified port. Specifies the port on which the PHY module attributes will be displayed. Displays the PHY module statistics for the specified port. Specifies the port on which the PHY module statistics will be displayed.
NOTE
binary file --query port_id --stats port_id Examples
#bcu phy --update 1 fwimg Updating Phy Firmware on Successfully updated the Updating Phy Firmware on Successfully updated the
the port 1/0 Firmware the port 1/1 Firmware
#bcu phy --query 1/0 Phy Module attributes: Phy status: Good Firmware version: 0x920c Link partner auto-negotiation ability: Yes PHY auto-negotiation ability: Yes AN complete: No PMA/PMD link status: Link up PMA/PMD signal detected: No PCS link status: Link up
237
phy
#bcu phy --stats 1/0 Phy Module statistics: Phy stats status: Good Link breaks after linkup: 0 PMA/PMD receive fault: Detected PMA/PMD transmit fault: Detected PCS receive fault: Detected PCS transmit fault: Detected Speed negotiations: 1 TX EQ trainings: 0 TX EQ timeouts: 4 CRC errors: 4
See Also
None
238
port
port
Lists the port commands (the physical ports on the adapter), along with their basic attributes. The port ID can be any one of the following:
NOTE
1 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:

Operands --list
Adapter ID Port ID Port WWN Port name (user assigned) Port hardware path 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.
239
port
--name port_id port_name
Queries or sets the port name. You can clear the port name using an empty string ( ). Specifies the ID of the port for which you want to display information. 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. Enables the physical port if it is disabled. Specifies the ID of the port you want to enable. 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. Specifies the ID of the port you want to disable. Displays the physical port-level statistics. Specifies the ID of the port for which you want to display statistical information. Clears port-level statistics. Specifies the ID of the port for which you want to clear statistical information. Queries and displays port-related details for a port. Specifies the ID of the port for which you want to display information. 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. Specifies the ID of the port for which you want to set the port speed. 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).
--enable port_id --disable
port_id --stats port_id --statsclr port_id --query port_id --speed
port_id 1|2|4|8|10
--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 port_list
Specifies the ID of the port for which you want to enable or disable trunking. Specifies a comma-separated list of all the ports within the adapter (identified by the port ID).
240
port
--dfsize
Queries or sets the ports 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. Specifies the ID of the port for which you want to set the data field 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. Queries or sets the port topology. Note: The topology operand is not applicable to CNAs. Specifies the ID of the port for which you want to display or set the topology. Specifies the topology type. Supported topology mode is point-to-point (p2p). Displays the data throughput for a given port and for a given interval. Specifies the port range; for example, 1/0, 1/0-2/1, or all. Specifies the number of iterations of the display. The default behavior is to continually refresh; you can terminate the default with CTRL-C. Specifies the interval delay value, in seconds. The default interval value is 1 second.
port_id df_size
--topology port_id p2p --perf port_range -c count -i interval 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_p0 Port 1/0s name set to emc_fab3_ad5_p0
241
port
# bcu port --name 1/0 Port 1/0s name is emc_fab3_ad5_p0 # bcu port --enable 2/1 port enabled # bcu port --enable 2/1 port is already enabled # bcu port --disable 2/1 port disabled # bcu port --disable 2/1 port is already disabled # bcu port --stats 4/0 Physical port statistics (FC HBA): tx_frames : 385508684 tx_words : 38422038819 rx_frames : 514011477 rx_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 : 65-127 byte frames : 128-255 byte frames : 256-511 byte frames : 512-1023 byte frames : 1024-1518 byte frames: 1519-1522 byte frames: tx_frames : tx_bytes : tx_mcast frames : tx_bcast frames : tx_drop frames : tx_jabber frames : tx_fcs_error frames : tx_control frames : tx_fragments : rx_frames : rx_bytes : rx_mcast frames : rx_bcast frames : rx_control frames :
1315 704210587 336 1250 2337 281686685 0 422530324 181971963859 1710 754 0 0 0 0 0 563372638 187640498430 1847 7423 0
242
port
rx_unknown_op frames rx_drop frames rx_jabber frames rx_fcs_error frames rx_align_err frames rx_length_err frames rx_code_error rx_fragments tx_pause tx_zero_pause rx_pause rx_zero_pause tx_fcoe_pause tx_fcoe_zero_pause rx_fcoe_pause rx_fcoe_zero_pause
: : : : : : : : : : : : : : : :
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
# bcu port --statsclr dell_s1_ad0_p1 port stats cleared # bcu port --query 1/0 port id: 1/0 port type: FC port instance: 0 port name: Media: sw pwwn: 10:00:00:05:1e:53:0e:ca nwwn: 20:00:00:05:1e:53:0e:ca state: Linkup Speed: current: 8G configured: Auto Topology: current: P2P SNIA port type: N supported classes: Class-3 symbolic name: Brocade-825 | 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: 8 QOS: Disabled TRL: Disabled TRL default speed: 1G Path TOV: 45 seconds Beacon status: Off pbind status: Enabled Portlog: Enabled # bcu port --query 3/0 port id: port type: port instance: port name: Media: Speed: CNA/CEE status: FCoE: MAC: pwwn:
3/0 CNA 2 sw 10G CEE Linkup 00:05:1e:55:3a:18 10:00:00:05:1e:55:3a:18
243
port
nwwn: state: supported classes: symbolic name: Microsoft Windows Server maximum frame size: receive bb credits: transmit bb credits: QOS: TRL: TRL default speed: Path TOV: Beacon status: pbind status: Portlog: Vlans: Eth: MAC: Factory MAC: state: OS Eth Device: # bcu port --topology 1/1 p2p Topology set to p2p # bcu port --speed 1/1 auto Port speed set # bcu port --trunk 1/0 on 0,1 Port trunking enabled
20:00:00:05:1e:55:3a:18 Linkup Class-3 BR-1020 | 2.0.0.006 | C06_I3650_83110 | 2003 R2 | Service Pack 2 2112 48 74 Disabled Disabled 1G 45 seconds Off Enabled Enabled -00:05:1e:55:3a:1a 00:05:1e:55:3a:1a Linkup Local Area Connection 5
# 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 2112 Setting will be enforced after port --disable and port--enable # bcu port --dfsize 1/1 auto Port maximum receive data field size set to driver default.
244
port
# bcu port --perf 1/0-1/1 Port 1/0 1/1 Type FC ETH FC ETH ======================================================== TX RX TX RX TX RX TX RX ======================================================== 181.4M 182.6M 0 0 0 0 0 0 182.6M 183.5M 0 0 0 0 0 0 # bcu port --perf all -c 3 -i 2 Port 1/0 1/1 2/0 2/1 Type 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
245
qos (HBA only)
qos (HBA only)

The 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 Operands Enables or disables Quality of Service (QoS). The QoS commands apply to the 8 Gbps HBA only. QoS is not supported on the CNA. --enable port_id --disable port_id Example See Also Enables Quality of Service (QoS). Specifies the ID of the port on which QoS is enabled. Disables QoS. Specifies the ID of the port on which QoS is disabled.
NOTE
bcu qos --query 1/0
None
246
ratelim
ratelim
Enables or disables target rate limiting support on the HBA side. The 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 ports 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:
NOTE
Adapter ID Port ID Port WWN Port name (user assigned) Port hardware path
You 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 port_id Enables target rate limiting, if currently disabled. Specifies the ID of the port you want to enable.
NOTE
-s default-speed Sets the target rate limiting speed on the HBA. Options are 1 Gbps, 2 Gbps, and 4 Gbps. --disable port_id See Also None Disables target rate limiting on the HBA, if currently enabled. Specifies the ID of the port you want to disable.
247
rport
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 Operands Lists all the remote ports (rports) under a given port ID. --list port_id -l lpwwn --osname port_id -l lpwwn --query port_id rpwwn -l lpwwn Lists all remote ports accessible for a given logical port. Specifies the ID of the port for which you want to display rport information. 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. Lists all the osnames of the remote ports that are visible through the local port. Specifies the ID of the port for which you want to display osnames. Specifies the logical port world wide name. This is an optional argument. Displays detailed attributes of a remote port. Specifies the ID of the port for which you want to query attributes of a remote port. Specifies the remote port world wide name for which you want to query attributes. Specifies the logical port world wide name for which you want to query attributes of a remote port. This is an optional argument. Note: If the -l lpwwn argument is not specified, the base port is used. --stats port_id rpwwn -l lpwwn --statsclr port_id rpwwn -l lpwwn Displays remote port statistics. Specifies the ID of the port for which you want to display information. Displays the remote ports port world wide name. Displays 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. Clears the remote port statistics. Specifies the ID of the port for which you want to clear remote port statistics. Specifies the remote ports port world wide name for which you want to clear remote port statistics Displays the logical port world wide name. This is an optional argument.
248
rport
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 2048 01f701 50:06:01:60:41:e0:68:c0 U/0 --online T 2048 01f202 50:06:0e:80:03:75:5e:05 U/0 --online T 2048 01f002 20:02:00:0e:11:10:fc:25 U/0 --online T 2048 01ff01 50:05:07:63:0e:04:12:ef U/0 --online T 2048 01fe01 50:06:01:60:3c:e0:0c:a3 U/0 --online T 2048 01fc01 50:01:43:80:01:3b:fb:38 U/0 --online T 2048 01f601 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:04 RPORT FC Address: 01f701 RPORT port wwn: 50:06:01:68:41:e0:68:c0 RPORT node wwn: 50:06:01:60:c1:e0:68:c0 Status: online Class of Service: Class-3 Function: Target Data Field size: 2048 Cont.Incr.seq_cnt(CISC): Not Supported Current Speed: --symbolic name: DGC LUNZ 0324 Vendor: DGC Product ID: DISK Product Rev: 0324 QOS priority: Unknown QOS flow id: 0 TRL enforced: No bcu rport --stats 1/0 aa:bb:cc:dd:ee:ff:00:01 offlines: 1 onlines: 2 RSCN : 0 PLOGI sent: 2 PLOGI accepts : 2 PLOGI timeouts: 0 PLOGI failed: 0 PLOGI rejects : 0 PLOGI received: 0 PRLI received: 0 ADISC sent: 0 ADISC received: 0 ADISC rejects : 0 ADISC accepts : 0 ADISC failed: 0 ADISC rejected: 0 LOGO sent: 0 LOGO accepts: 0 LOGO failed: 0 LOGO rejected: 0 LOGO received: 0 RPSC received: 0 RPSC rejects: 0 RPSC sent: 8 RPSC accepts: 0 RPSC failed: 8
249
rport
RPSC rejected:
HAL rport statistics: uninit: create events: uninit: exception events: created: online events: created: delete events: created: IOC down: created: exception events: fw create: f/w responses: fw create: delete events: fw create: offline events: fw create: IOC down: fw create: exception events: online: offline events: online: delete events: online: IOC down events: online: exception events: fw delete: fw responses: fw delete: delete events: fw delete: IOC down events: fw delete: exception events: offline: delete events: offline: online events: offline: IOC down events: offline: exception events: delete: fw responses: delete: IOC down events: delete: exception events: delete pend: fw responses: delete pend: IOC downs: delete pend: exceptions: off-pending: fw responses: off-pending: deletes: off-pending: IOC downs: off-pending: exceptions: IOC down: offline events: IOC down: delete events: IOC down: online events: IOC down: exceptions:
1 0 1 0 0 0 2 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
bcu rport --statsclr 1/0 aa:bb:cc:dd:ee:ff:00:01 Successfully reset the rport level stats
See Also
None
250
team
team
Teaming 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 Operands Configures ports and VLANs on the teaming interface. --list --query team_name --create team_name team_mode port_id --addport team_name port_id --remport team_name port_id Lists all the configured teams in the system. Queries the teaming configuration. Specifies the team name. Adds a new teaming interface to the system. Specifies the teaming interface name. Specifies the team mode. Supported values are 802.3ad, failover, and failback. Specifies up to a maximum of eight ports. Adds a specified port to an existing team. Specifies the team to which a port will be added. Adds one or more ports to the team. The maximum number of ports that can be added to a team is eight. Removes a specified port from an existing team. Specifies the team from which a port will be removed. Removes one or more ports from an existing team. The maximum number of ports that can be removed from a team is eight.
251
team
--name
Modifies the teams 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. Specifies the existing team name. Specifies the new team name. Modifies the teams 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. Specifies the teaming interface name where the primary interface resides.. Specifies the port that is designated as the primary. Modifies the teams policy for traffic load balancing. This command applies to the 802.3ad teaming mode only. Specifies the existing team name. The transmit policy. Supported values include the following policies:
team_name --primary
new_team_name
team_name port_id --xmit_policy team_name xmit_policy
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 team_name --vlanadd team_name vlan_id vlan_name --vlanremove team_name vlan_id --vlanedit team_name vlan_id vlan_name --vlanlist team_name Removes an existing teaming interface from the system. Specifies the teaming interface name to be removed from the system. Configures a new VLAN ID on the team. Specifies the name of the teaming interface on which you want to add a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Specifies the VLAN name. Removes an existing VLAN ID from the teaming interface. Specifies the name of the team from which you want to remove a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Modifies the VLAN name attribute of the specified VLAN on the team. Specifies the name of the teaming interface on which you want to modify a VLAN. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094. Specifies a different name for the VLAN. Lists the configured VLANs on the teaming interface. Specifies the name of the team on which you want to list configured VLANs.
252
team
--vlanquery team_name vlan_id Examples
Displays the VLAN information on the team. Specifies the name of the team for which you want to display the VLAN details. Specifies the VLAN ID. The supported range for the VLAN ID is 0-4094.
# bcu team --list ---------------------------------------------Team Id Team modeMAC address ---------------------------------------------team-1 802.3ad 1:2:3:4:5:6 team-2 failback 2:4:1:2:5:6 team-3 failover 2:4:1:2:5:7 ---------------------------------------------# bcu team --vlanlist team-1 -------------------------------Vlan id Vlan Name -------------------------------1 VLAN0001 3000 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/1 Added interface 1/0 to the Team ABC Added interface 1/1 to the Team ABC
253
team
# bcu team --create ABC failover 1/0 1/1 Team ABC created successfully # bcu team --name ABC XYZ Team name ABC is changed to XYZ successfully # bcu team --primary ABC 1/1 Team ABC primary settings changed successfully # bcu team --xmit_policy ABC l3_l4 Team ABC transmit policy settings changed successfully # bcu team --remport ABC 1/0 Removed 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.
254
trunk
trunk
When 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:

Synopsis
adapter index serial number adapter name hardware path
bcu trunk --enable <ad_id> bcu trunk --disable <ad_id> bcu trunk --query <ad_id>
Enabling and disabling trunking for an adapter brings down all the adapter ports and then brings them up to apply the settings. When invoked without operands, this command displays the usage. --enable ad_id --disable ad_id --query ad_id Enables adapter trunking if currently disabled. Specifies the ID of the adapter you want to enable. Disables adapter trunking if currently enabled. Specifies the ID of the adapter you want to disable. Queries or displays trunk attributes. Specifies the ID of the adapter for which you want to query.
Example
# bcu trunk --query 1 Trunk state: Online Link state*: Linkup Port address: 010800 Port id: 2/0 Port state: Enabled Link state: Linkup Deskew value: 15 nsec Port id: 2/1 Port state: Enabled Link state: Linkup Deskew value: 16 nsec *Link state can be any one of the following: Linkup Linkdown MisSpd MisGrp MisMode The trunking negotiation is successful and the link is up. The link is down due to port disable, cable removal, or remote port down. The speed mismatch between the links corresponding to the trunked ports. The trunked ports are connected to different trunk groups on the switch. The trunked ports have different configurations (for example, one trunked port has trunking enabled and another port has QoS and trunking enabled).
255
trunk
# bcu trunk --query 2 Trunk state: Offline Link state: LinkDown Port address: -Port id: 2/0 Port state: Enabled Link state: LinkDown Deskew value: -Port id: 2/1 Port state: Enabled Link state: LinkDown Deskew value: --
See Also
adapter, port
256
vport
vport
Lists 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. The vport commands are not supported on Solaris platforms. Operands --create port_id vpwwn n vnwwn 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. Specifies the ID of the port for which you want to add a new V_Port. Adds the virtual port by its world wide name. The V_Port WWN is a required argument. Adds the virtual port by the nodes world wide name for the V_Port. This is an optional argument. If not specified, the base port nodes world wide name is used. Adds the symbolic name for the virtual port. This is an optional argument. Deletes the specified V_Port. This deletes all associated objects, such as any associated login sessions and active I/O requests. Specifies the ID of the port for which you want to delete a V_Port. Deletes the virtual port by its world wide name. The V_Port WWN is a required argument. Queries information about the V_Port. This provides the V_Ports status and information associated with FC-4s. If no port WWN is specified, the information provided is for the base V_Port. Specifies the ID of the port for which you want to query V_Port information. Queries the virtual port by its world wide name. The V_Port WWN is a required argument. Displays the statistics that are associated with the V_Port. If you do not specify the ports world wide name, the statistics listed are for the base V_Port. Specifies the ID of the port for which you want to display statistical information. Displays the statistics for the virtual port by its world wide name. The V_Port WWN is a required argument.
NOTE
s sname --delete port_id vpwwn --query
port_id vpwwn --stats
port_id vpwwn
257
vport
--statsclr port_id vpwwn Example
Clears the statistics that are associated with the V_Port. If you do not specify the ports world wide name, the statistics listed are for the base V_Port. Specifies the ID of the port for which you want to clear statistical information. Clears the statistics for the virtual port by its world wide name. The V_Port WWN is a required argument.
bcu vport --query 1/0 10:00:00:05:1e:ae:e3:03 Port wwn: 10:00:00:05:1e:ae:e3:03 Node wwn: 20:00:00:05:1e:ae:e3:a4 FC Addr: dd0504 State: online Role: FCP initiator bcu vport --stats hba5_port0 fdisc sent: 15 fdisc accepts: 7 fdisc retries: 8 fdisc timeouts: 2 fdisc rsp err: 18 fdisc acc bad: 9 fdisc rejects: 3 fdisc unknown: 0 fdisc alloc waits: 6 logo sent: 12 logo accepts: 8 logo rejects: 4 logo rsp err: 4 logo unknown rsp: 6 logo alloc waits: 6 no npiv: 7 fab offline: 5 fab online: 8 fab cleanup: 9 bcu vport --statsclr hba5_port0 vport stats cleared
See Also
None
258
Appendix
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_Ports
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. 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.
Workaround
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.
260
Appendix
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 Baud BCU Beaconing The maximum information-carrying capacity of a system. The encoded bit rate per second. Brocade Command Line Utility (BCU). 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). A group of eight data bits. Converged Enhanced Ethernet. A frame delivery scheme exhibiting a specified set of delivery characteristics and attributes. Permission given by a receiving port to a sending port to send a specified number of frames. Data Center Bridging. DCB Capability Exchange Protocol. Data Center Fabric Manager An eight-bit value that identifies a domain. Fibre Channel over Ethernet. The Fibre Channel Protocol for mapping SCSI-3 operations to Fibre Channel. FC Fabric Login request. A switch port that is capable of arbitrated loop operations and is connected to one or more NL_Ports in an arbitrated loop topology. Fabric Operating System. Fabric Provided MAC Address. Fabric Port. A port on a switch to which an N_Port connects.
Byte CEE Class of service Credit DCB DCBX DCFM Domain_ID FCoE FCP FLOGI FL_Port FOS FPMA F_Port
261
HBA HCM IOC ITL LLDP
The host bus adapter is a hardware facility in a node that provides an interface attachment. Host Connectivity Manager. I/O Controller. Initiator-Target-LUN. An Initiator Port (HBA controller) talks to one Target Port addressing one LUN. Link Layer Discovery Protocol. A full duplex Ethernet MAC supporting at least 2.5KB jumbo frames and implementing extensions to avoid Ethernet frame loss resulting from congestion.
Lossless Ethernet MAC
LUN LUN mapping MAC MIB MTU N_Port NPIV
Logical unit number. An address for an individual disk drive or virtual partition (volume) within a storage device. A process that makes a LUN available to some hosts and unavailable to other hosts. Media Access Control. Management Information Base. Maximum Transfer Unit. 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. 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). 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 devices ID on the FC loop may be different each time the FC loop initializes. Priority Flow Control. A generic reference to an N_Port, NL_Port, F_Port, FL_Port, E_Port, or other type of Fibre Channel port. A 64-bit unique identifier assigned to each Fibre Channel port. The port name is communicated during the login and port discovery processes. Remote port in a fabric. A remote port is a port that is physically separated from the adapter. Simple network management protocol, defined for providing network management and monitoring functions. A storage area network configuration allowing multiple systems and storage devices to be interconnected using storage command protocols. A 64-bit unique Fibre Channel name assigned to a switch.
Persistent binding
PFC Port Port name R_Port SNMP SAN Switch_Name
262
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. Virtual Fabric. Virtual Local Area Network. World Wide Node Name. The unique name for any particular node in the fabric; for example, an HBA. World Wide Port Name. The unique name for any particular port in the fabric. A WWNN can have multiple associated WWPNs.
VF VLAN WWNN WWPN
263
264
Index
A
adapter command, 190, 255 adapters HBA models, 1 supported operating systems, 11 advanced port configuration options, 47 application log, 72 auth command, 194 Authentication Configuration dialog box, 127 authentication, security, 27
B
base port properties panel, 94 beaconing configuring using HCM, 82 configuring using the BCU, 83 boot groups, 38 boot LUN discovery, 4 boot over SAN description of, 38 buffer credits, 28
C
CEE properties, 96 CEE features data center bridging capability exchange protocol (DCBX), 6 priority-based flow control (PFC), 6 CNA Ethernet features, 5 FCoE features, 4 product overview, 2 throughput per port, 5 CNA expansion card port panel, 102 CNA port statistics panel, 103
command adapter, 190, 255 auth, 194 debug, 84, 203 diag, 79, 205 fabric, 216 fcdiag, 80, 217 fcpim, 221 IOC, 228 log, 46, 231 lport, 232 port, 239 portlog, 84 portlogclear, 84 portlogct, 84 rport, 248 vport, 257 Configure Names dialog box, 106 configuring HCM logging level, 46 interrupt control coalesce, 48 NPIV, 55 persistent binding, 32 port speed, 31 QoS using the BCU, 34 queue depth, 41 rate limiting using the BCU, 36 security authentication using HCM, 26
D
DCBCXP, 5 debug command, 84, 203 Define Name dialog box, 108 diag command, 205 diagnostics running Ethernet test, 81 running port-level test, 76, 77 types of tests, 3
265
dialog box Authentication Configuration, 127 Configure Names, 106 Define Master Log Filter, 147 Define Name, 108 Event Properties, 115 Historical Performance, 138 Persistent Binding, 148 Protocol Tests diagnostics, 155 Security Authentication, 127 Test Log Details, 170 Update Driver, 171 discovery description of, 3 setting up, 21 setting up out-of-band, 22 driver intermediate, 10 network, 10 storage, 10 driver types, 10
H
HBA Properties panel, 100, 136 HCM authentication, 15, 16 change password dialog box, 98 features, 3 logging level configuration, 46 main window, 18 master log icons, 21 product icons, 20 software overview, 2 statistics monitoring, 3 Historical Performance dialog box, 138 host management, remote, 3
I
intermediate driver, 10 interrupt coalescing FCoE, 4 interrupt control coalesce configuring using the GUI, 48 interrupt moderation, 4 IOC command, 228
E
enhanced transmission selection, 5 enhanced transmission selection (ETS), 5 Ethernet diagnostic test, running from HCM, 81 Ethernet flow control, 5 event categories, 146 event logs, how to filter, 71 Event Properties dialog box, 115 event severities, 21 events, master log, 70
J
jumbo frames, 5
L
launching HCM on Linux, 14 on Solaris, 14 on Windows, 13 Linux, launching HCM, 14 LLDP, 6 log application, 72 master log, 70 test, 79 log command, 46, 231 log off, 23 login, how to skip, 14 lport command, 232
F
fabric command, 216 fcdiag command, 217 FCoE features of CNA, 4 fcpim command, 221 FCP-IM profile, 36 FC-SP, 4 filtering event log entries, 71 flow control, 6 frame data field size specifying using HCM, 31 specifying using the BCU, 32
266
M
MAC addressing, 5 management software components, 2 Master Log Filter dialog box, 147 Master Log properties, 70 Master Log Properties tab, 146 monitoring statistics, 3
N
name configuration, 49 NetQueues, 7 network driver, 10 network priority, 6 NPIV, 4 NPIV configuration, 55 N-Port trunking, 4
O
operating systems supported on adapters, 11
P
panel CNA expansion card port, 102 CNA expansion card port statistics, 103 HBA Properties, 100, 136 Port POM, 149 Port SFP, 160 Port Statistics, 152 remote port properties, 145, 158 password how to change, 15, 16 path time out specifying using HCM, 35 specifying using the BCU, 35 persistent binding, 4 configuring using HCM, 32 configuring using the BCU, 32 Persistent Binding dialog box, 148 persistent binding, configuring, 32 port 514, troubleshooting firewall issues, 74 port command, 239
port configuration advanced, 47 basic options, 28 opening the advanced dialog box, 47 opening the basic dialog box, 29 port speed, 31 port logging level configuring using HCM, 30 configuring using the BCU, 30 Port POM panel, 149 port properties panel, 150 Port SFP panel, 160 port speed configuring using HCM, 31 configuring using the BCU, 31 Port Statistics panel, 152 port test diagnostics, 135 port-level diagnostic tests, running from HCM, 77 port-level test how to run using HCM, 76 portlog command, 84 portlogclear command, 84 portlogct command, 84 priority flow control (PFC), 6 product overview, 2 properties CEE, 96 importing in EFCM format, 53 importing in FM format, 54 Protocol Tests diagnostics dialog box, 155
Q
quality of service (QoS), 5 quality of service (QoS), configuring, 34 queue depth configuring using the BCU, 41
R
rate limiting configuration, 36 receive side scaling (RSS), 6 remote host management, 3 Remote port properties panel, 145, 158 resetting statistics, 67 rport command, 248
267
S
SAN components, types listed in device tree, 8 security authentication configuring using HCM, 26 configuring using the BCU, 27 Security Authentication dialog box, 127 SFP displaying using HCM, 83 displaying using the BCU, 83 SFP management, 83 skip login, 14 Solaris, launching HCM, 14 statistics, resetting, 67 storage driver, 10 supportSave categories of information, 85 collecting on a port crash event, 86 collecting using a browser, 87 collecting using HCM, 86 collecting using the BCU, 87 collection sources, 85 configuring using the BCU, 87 syslog host, unblocking port 514, 74
VMware ESX 3.5 and 4.0 troubleshooting firewall issues, 74 vport command, 257
W
Windows, launching HCM application, 13 WWN adding a name, 54 exporting, 52 importing, 53 removing, 52
T
target rate limiting, 3 target rate limiting (TRL), 3 TCP segmentation offload, 7 teaming, 6 test log details, 79 Test Log Details dialog box, 170 tree node pop-up menus, 7 trunking N-Port, 4
U
Update Driver dialog box, 171
V
VLAN, 7 VLAN filtering, 7 VLAN tagging, 7
268

Brocade Adapters v2.3.0.0 Admin Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brocade Adapters v2.3.0.0 Admin Guide

Uploaded by

Copyright:

Available Formats

53-1001923-02 30 November 2010

Brocade Communications Systems, Incorporated

Publication number Summary of changes

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

About This Document

Host Management Overview

Getting Started with HCM Software

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

HCM Dialog Boxes

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Command Utility

Brocade Adapters Administrators Guide 53-1001923-02

Appendix C Appendix D Index

HCM Troubleshooting Glossary and Acronyms

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

About This Document

How this document is organized

Chapter 1, Host Management Overview, provides a description of the Host Connectivity

Chapter 3, Host Configuration, provides the procedures to configure operating parameters

Appendix C, HCM Troubleshooting, provides a summary of HCM navigation problems and

Brocade Adapters Administrators Guide 53-1001923-02

Notes, cautions, and warnings

Brocade Adapters Administrators Guide 53-1001923-02

Notice to the reader

Referenced Trademarks and Products

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Other industry resources

Getting technical help

Brocade Adapters Administrators Guide 53-1001923-02

Brocade Adapters Administrators Guide 53-1001923-02

Host Management Overview

Host bus adapters

Brocade Fibre Channel HBA models

Brocade 425 Brocade 415

Brocade Adapters Administrators Guide 53-1001923-02

Converged network adapters

Converged network adapters

Brocade Fibre Channel CNA models

Brocade Adapters Administrators Guide 53-1001923-02

Common HBA and CNA features

Brocade Adapters Administrators Guide 53-1001923-02

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

Persistent bindingenables you to permanently assign a system SCSI target ID to a specific

Interrupt Coalescingprovides a method to delay generation of host interrupts and thereby

Interrupt moderationimplements dynamic selection interrupt coalescing values based on

Brocade Adapters Administrators Guide 53-1001923-02

Server Application Optimization (SAO) license Trunking license

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

CNA and networking features

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

Enhanced transmission selection (802.1Qaz)

Ethernet flow control

Flexible MAC address