HBA Admin Guide

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

Administrators Guide
Supporting HBA models 415, 425, 815, 825
Copyright 2008 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it. The product described by this document may contain open source software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software.
Brocade Communications Systems, Incorporated

Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 1745 Technology Drive San Jose, CA 95110 Tel: 1-408-333-8000 Fax: 1-408-333-8101 Email: [email protected] Asia-Pacific Headquarters Brocade Communications Singapore Pte. Ltd. 30 Cecil Street #19-01 Prudential Tower Singapore 049712 Singapore Tel: +65-6538-4700 Fax: +65-6538-0302 Email: [email protected]
European Headquarters Brocade Communications Switzerland Srl Centre Swissair Tour B - 4me tage 29, Route de l'Aroport Case Postale 105 CH-1215 Genve 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 Email: [email protected]
Document History
Title
Brocade Fibre Channel HBA Administrators Guide Brocade Fibre Channel HBA Administrators Guide
Publication number
53-1000881-01 53-1000881-02
Summary of changes
New document
Date
May 2008
December 2008 Updated document to include new features, including QoS, target rate limiting, BIOS, and Boot from SAN, upload boot code image.
Contents
About This Document

In this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xv Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Other industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii
Chapter 1
HCM Overview
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HCM features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Tree node pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Operating System (OS) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Driver operating system support. . . . . . . . . . . . . . . . . . . . . . . . . . 4 Local and remote management . . . . . . . . . . . . . . . . . . . . . . . . . . 5 OS-specific features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2
Getting Started with HCM Software

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Brocade Fibre Channel HBA Administrators Guide 53-1000881-02
iii
HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Launching the application on Windows platforms. . . . . . . . . . . . 7 Launching the application on Linux platforms. . . . . . . . . . . . . . . 8 Launching the application on Solaris platforms . . . . . . . . . . . . . 8 Remember password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Skip login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Changing an HCM application password . . . . . . . . . . . . . . . . . . . 9 Changing an HCM agent password. . . . . . . . . . . . . . . . . . . . . . . 10 Resetting a password or restoring a factory default password. 11 Backing up data after an uninstall . . . . . . . . . . . . . . . . . . . . . . . 11 HCM main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HCM product icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Setting up out-of-band discovery for an HBA . . . . . . . . . . . . . . . 14 Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 3
Host Configuration
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Host security authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Configuring security authentication using the GUI . . . . . . . . . . 18 Configuring security authentication using the BCU . . . . . . . . . . 20 Buffer credits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Virtual Port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Creating a Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Deleting a Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 HCM Logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Advanced port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Opening the Advanced Port Configuration dialog box . . . . . . . . 40 Queue Depth configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Interrupt Control Coalesce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Name configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Editing the name fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Adding name entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Removing a name entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Exporting the properties for a WWN . . . . . . . . . . . . . . . . . . . . . . 46 Importing the properties for a WWN. . . . . . . . . . . . . . . . . . . . . . 46 Importing duplicated names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 4
Monitoring
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Performance monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Polling frequency rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Resetting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
iv
Master Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Event severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Filtering event log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Syslog support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Opening the Syslog Server Configuration dialog box. . . . . . . . . 54 Registering a host server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Removing a host server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 5
Diagnostics
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Related Diagnostic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Diagnostics using the Brocade Command Line Utility (BCU) . . . . . . 58 diag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 fcdiag commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Diagnostics using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Running a hardware-level test using the GUI . . . . . . . . . . . . . . . 59 Hardware-level test parameters . . . . . . . . . . . . . . . . . . . . . . . . . 60 Running a protocol-level test using the GUI . . . . . . . . . . . . . . . . 61 Displaying test log details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Configuring beaconing using the BCU . . . . . . . . . . . . . . . . . . . . 64 Configuring beaconing using the GUI . . . . . . . . . . . . . . . . . . . . .64 SFP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Displaying SFP information using the BCU. . . . . . . . . . . . . . . . . 64 Displaying SFP information using the GUI . . . . . . . . . . . . . . . . . 65 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 supportSave collection sources . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 6
HCM Dialog Boxes

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Authentication Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . 71 Backup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Base Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Change HCM User Password dialog box . . . . . . . . . . . . . . . . . . . . . . 74 Change HCM Agent dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Configure Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Duplicated Names dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Event Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Fabric Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
FCP IM Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Fibre Channel Security Protocol dialog box . . . . . . . . . . . . . . . . . . . . 83 HBA Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 IOC Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 LPORTs Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Logical Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 LUN Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Master Log tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Persistent Binding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Port POM Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Port Tests Diagnostics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . .101 Protocol Tests Diagnostics dialog box . . . . . . . . . . . . . . . . . . . . . . .102 QoS Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Remote Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 SFP Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . .108 Target Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Test Log Details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Virtual Port Deletion dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Virtual Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Virtual Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Appendix A
Brocade Command Line Utility (BCU)

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Command Line Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 BCU commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 bios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 fcdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
vi
fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 fcpim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 IOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 lport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 pbind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 qos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 rport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 ratelim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 vport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Appendix B
FDMI FC-CTs
HBA Driver and FDMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Appendix C
Standards Compliance
Standards Compliance Publications . . . . . . . . . . . . . . . . . . . . . . . .159
Appendix D
SAN-based Virtual Machine Migration using SCVMM

System Center Virtual Machine Manager 2008 . . . . . . . . . . . . . . .161 Supported virtualization platforms . . . . . . . . . . . . . . . . . . . . . .162 N_Port ID Virtualization (NPIV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 NPIV benefits in a virtualization environment . . . . . . . . . . . . .162 Preparation to deploy NPIV in a virtualization environment . .162
Appendix E Index
Glossary
vii
viii
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
HCM Login dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Change HCM Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Change HCM Agent password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Host Connectivity Manager main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HCM product icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Setup for HBA Discovery dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Fibre Channel Security Protocol Configuration - host level dialog box . . . . . . . . 18 Fibre Channel Security Protocol Configuration - HBA level dialog box . . . . . . . . 19 Fibre Channel Security Protocol Configuration - port level dialog box . . . . . . . . 19 Basic Port Configuration dialog box - Windows, Linux, and VmWare . . . . . . . . . 23 Port disable/enable Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Persistent Binding dialog box - host level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Persistent Binding dialog box - HBA level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Persistent Binding dialog box - port level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Boot over SAN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Boot Code Image Upload dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Boot Code Image Upload browse dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configure HCM Logging Levels dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Advanced Port Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Configure Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Reset Statistics warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Master Log Filter dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 HCM Application Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Diagnostics - Port Tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Protocol-level tests dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Test Log Details for Echo Test dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Test Log Details for FC trace test dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 SFP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
ix
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
Driver operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 HCM operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 OS-specific features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Basic port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Advanced port configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Master Log fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 HCM Master Log icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Related diagnostic documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Hardware-level test parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 SFP management information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 supportSave categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 supportSave collection sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
xi
xii
About This Document
In this section
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiii xiv xiv xv xvi xvii xvii xvii
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, HCM 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, describe 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.
Chapter 6, HCM Dialog Boxes, lists the fields that are associated with the HCM GUI and
provides a definition for each field.
Appendix A, Brocade Command Line Utility (BCU), provides reference information for the Host
Connectivity Manager (HCM) commands that can be run from the Brocade Command Line Utility (BCU)
Appendix B, FDMI FC-CTs, provides reference information to support the Fabric Device
Management Interface (FDMI).
xiii
Appendix C, Standards Compliance, provides reference information for standards

compliance.
Appendix D, Glossary, provides reference information for common terms and acronyms.
Whats new in this document

The following changes have been made since this document was last released:
Information that was added: - New feature descriptions for basic port configuration: QoS, Target Rate Limiting, BIOS,
Boot-over-SAN
V_Port creation and deletion Monitor statistics for Fabric, IOC, Logical Port (L_Port), QoS, Remote Port (R_Port), Virtual Port (V_Port).
Information that was changed: - OS support (update VmWare, Solaris, Linux, Windows) - Screen changes - BCU commands
For further information about new features and documentation updates for this release, refer to the release notes.
Document conventions
This section describes text formatting conventions and important notice formats used in this document.
Text formatting
The narrative-text formatting conventions that are used are as follows: bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter 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.
xiv
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.
Key terms
For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. For definitions specific to this document, see Glossary on page 165. 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
xv
Additional information
This section lists additional Brocade and industry-specific documentation that you might find helpful.
Brocade resources
To get up-to-the-minute information, join Brocade Connect. Its free! Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and password. For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through: http://www.amazon.com For additional Brocade documentation, visit the Brocade Web site: http://www.brocade.com Release notes are available on the Brocade Connect Web site and are also bundled with the Fabric OS firmware.
Other industry resources

For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site: http://www.fibrechannel.org
xvi
Getting technical help

Contact your HBA support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available:
HBA model HBA operating system version Error numbers and messages received supportSave command output (see debug on page 128 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
Related documentation
Part Number
53-1000884-01 53-1000885-01 53-1000598-03 53-1000853-01
Document Title
Brocade Fibre Channel HBA Installation and Reference Manual supporting HBA models 815, 825, 415, and 425 Brocade Fibre Channel HBA Troubleshooting Guide supporting HBA models 815, 825, 415, and 425 Fabric OS Administrators Guide supporting Fabric OS v6.1.0 Fabric OS Troubleshooting and Diagnostics Guide supporting Fabric OS v6.1.0
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: [email protected] Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xvii
xviii
Chapter
HCM Overview
In this chapter
HCM software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HCM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tree node pop-up menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System (OS) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 2 3 4
HCM software
The Host Connectivity Manager (HCM) is a management software application for configuring, monitoring, and troubleshooting host bus adapters (HBAs) in a storage area network (SAN) environment that uses a supported Brocade HBA. 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
HBA. 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. The information in this guide is intended for OEMs, field service personnel, and customers who are installing Brocade hardware and HCM software.
HCM features
HCM features
The HBA management software has the following features:
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 items:
Brocade 8 Gbps and 4 Gbps Fibre Channel adapters HBA ports 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 Monitoring, which provides statistics for the following SAN components: Security authentication Fabric FCP IM IOC Logical port Port QoS Target Virtual port (vport) Security enables you to specify a CHAP secret and configure authentication parameters. Event notifications provide asynchronous notification of various conditions and problems
through a user-defined event filter.
Tree node pop-up menus
Tree node pop-up menus

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.
SAN component
Host
Pop-up menu feature

Refresh All Stop Polling Upload Boot Code Image Change Agent Password Configure Names Basic Port Configuration Persistent Binding Port Statistics FC SP Support Save Tree > Copy | Search | Collapse All | Expand All Refresh Define Name Upload Boot Code Image Basic Port Configuration Persistent Binding Port Statistics Diagnostics FC-SP Enable Adapter Tree > Copy | Search | Collapse All | Expand All Refresh Define Name Port Configuration > Basic | Advanced Persistent Binding Virtual Port > Create | Delete Statistics > Port | Fabric | IOC | QoS Diagnostics FC-SP > Authentication | Authentication Statistics Enable Port Beacon > Port | Link Tree > Copy | Search | Collapse All | Expand All
HBA
Port
Operating System (OS) support
Logical Port
Refresh Logical Port Statistics Tree > Copy | Search | Collapse All | Expand All Refresh Logical Port Statistics Virtual Port Statistics Define Name Delete Tree > Copy | Search | Collapse All | Expand All Refresh Define Name Statistics > Target Statistics | FCP IM Statistics Tree > Copy | Search | Collapse All | Expand All
VPort
Target Device

There are slight differences in the operating systems that are supported on the driver, on the Host Connectivity Manager (HCM), and the Brocade Command Line Utility (BCU), and the HCM agent.
Driver operating system support

Table 1 lists the operating systems supported on the driver. The Brocade Command Line Utility (BCU) is a standalone application that is installed as part of the driver package. The BCU is used primarily for managing HBAs installed on a local machine. The BCU is supported across all operating system versions listed in Table 1. Supported drivers vary with the operating system being used. For example, for Windows, the Storport miniport driver is supported (there is no support for the SCSI miniport driver) and for Solaris, only the Leadville-based driver is supported.
NOTE
TABLE 1

x86
32b 32b 32b 32b 32b 32b
Operating System
Windows Server 2003, SP2 Windows Server 2008 Linux SuSE Enterprise Server (SLES) 9.3, 9.4 Linux SuSE Enterprise Server (SLES) 10.1 Linux SuSE Enterprise Server (SLES) 10.2 Linux Red Hat Enterprise 4.6, 4.7
x64
64b 64b 64b 64b 64b 64b
IA64
64b 64b No support No support No support No support
SPARC
N/A N/A No support No support No support No support
TABLE 1

32b 32b 32b 64b 64b N/A No support N/A N/A No 64b N/A
Linux Red Hat Enterprise 5.1, 5.2 Solaris 10 VMware ESX 3.5, 3.5 U1, and ESX 3.5 U2
Note: The 8 Gbps FC HBA is supported on ESX 3.5 U2.
Local and remote management

The Host Connectivity Manager (HCM) can be installed on the local machine for managing HBAs installed on the local server. HCM can also be installed on a remote machine to manage distributed HBAs. You can run HCM on all available operating systems listed in Table 1. In addition, HCM can be installed on the Windows Vista and Windows XP operating system. All the operating systems supported on HCM are shown in Table 2. In addition to installing HCM on a local or remote machine, you can launch the HCM application from the Brocade Enterprise Fabric Connectivity Manager (EFCM).
NOTE
TABLE 2
HCM operating system support

x86
32b 32b 32b 32b 32b 32b 32b 32b 32b 32b 32b
Operating System
Windows Server 2003 Windows Server 2008 Windows Vista Windows XP Linux SuSE Enterprise Server (SLES) 9.3, 9.4 Linux SuSE Enterprise Server (SLES) 10.1 Linux SuSE Enterprise Server (SLES) 10.2 Linux Red Hat Enterprise 4.6, 4.7 Linux Red Hat Enterprise 5.1, 5.2 Solaris 10 VMWare ESC 3.5, 3.5 U1, 3.5 U2
x64
32b 32b 32b 64b 64b 64b 64b 64b 64b 32b N/A
IA64
64b 64b No support No support No support No support No support No support No support N/A N/A
SPARC
N/A N/A N/A N/A No support No support No support No support No support 64b N/A
OS-specific features
Some features are available only in specific operating system environments. These OS-specific features are identified in Table 3.
TABLE 3
Features
NPIV
Linux
Yes Yes No Yes Yes Yes
Windows
Yes Yes Yes Yes Yes Yes
VMware
Yes Yes No Yes Yes Yes
Solaris
No support No support No support No support Yes Yes
Fibre Channel Security (FC-SP) Authentication Target persistent mode MPIO mode and Path Time Out FC Ping diagnostic test FC Traceroute diagnostic test
Chapter
Getting Started with HCM Software
In this chapter
HCM software launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Changing an HCM application password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Logging off HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
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 Launching the application on Solaris platforms
Launching the application on Windows platforms

After installing the HCM software, locate Brocade HCM on the Windows platform by selecting Start > Programs > BROCADE_FCHBA. OR Click the desktop icon to launch the application. The following figure 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 older password to a new one using the HCM GUI.
HCM software launch
Launching the application on Linux platforms

After installing the HCM software, locate Brocade HCM on the Linux platform.
For the Gnome shell, double-click the BROCADE_FCHBA icon, and select Run to launch the
application.
For the KDE shell, single-click the BROCADE_FCHBA icon to launch the application.
OR Start the application from the command prompt using the following commands:
suse116208:~ # cd /opt/brocade/fchba/client suse116208:<installed directory>/fchba/client # ./BROCADE_FCHBA
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 BROCADE_FCHBA icon, and selecting run to launch the application. OR Start the application from the command prompt using the following commands: sun-116190# cd <installed directory>/fchba/client/ sun-116190# ./BROCADE_FCHBA You can use the shortcut for launching the application on Solaris platforms, by clicking on the desktop icon, only on machines that have a desktop, such as gnome.
NOTE
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

/data/HBAApplication.properties file.
Select the Skip Login check box if you do not want the Login dialog box to appear the next time
the application is started.
HCM software launch
Changing an HCM application password

You can change the default password of the application to a different password using the Change HCM Password dialog. Note the following when you change a password:
You must validate the user before you change the password by supplying the old 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 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. Passwords can be from 8 to 64 characters in length and can begin with an alphabetic, numeric or special character (for example, #pass1234). 5. Retype the new password in the Confirm New password field. 6. Click OK. Both the user name and passwords are case-sensitive.
NOTE
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. Note the following when you change a password:
Validate the user before you change the password by supplying the old 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 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. Passwords can be from 8 to 64 characters in length. They must begin with an alphabetic or numeric character. 5. Retype the new password in the Confirm New password field. 6. Click OK. Both the user name and passwords are case-sensitive.
NOTE
10
HCM software launch
Resetting a password or restoring a factory default password

After a successful installation, copy the /data/noitacitnehtua.properties file to your personal folder so that, in case the password is lost, you can overwrite the noitacitnehtua.properties file in the data folder with the local copy. This restores the factory default user name (Administrator) and password (password).
Backing up data after an uninstall

If you uninstall the Brocade HCM software, you are prompted to back up the application configuration data that was created during installation. The following application configuration files are backed up in the data directory:
HBAApplication.properties SetupDiscovery.properties HbaAliasdb.properties log4j.xml noitacitnehtua.properties
To restore the backed-up configuration data when you re-install the HCM, you must manually overwrite the new data directory contents with the backed-up data. This restores your previous settings.
11
HCM main window
HCM main window

From the Host Connectivity Manager main window, 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 Fibre Channel HBA Installation and Reference Manual supporting HBA models 815, 825, 415, and 425 for instructions on how to install both the driver and GUI, the driver only, or the GUI only.
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 4
Host Connectivity Manager main window
12
HCM product icons
HCM product icons

On the left side of the Host Connectivity Manager, there is a navigation tree for representing the managed host with HBAs 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. Figure 5 shows the product icons that represent the components that HCM manages.
FIGURE 5
HCM product icons
Discovery
Discovery enables you to contact the HBAs 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 HBAs in that host, connected to the SAN. The HCM application enables you to discover Brocade adapters, ports, virtual ports, remote ports, and LUNs using out-of-band discovery only.
NOTE
13
Discovery
Setting up out-of-band discovery for an HBA

When performing out-of-band discovery, you are managing the HBA 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 HBA 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 HBA Discovery dialog box displays.
FIGURE 6
Setup for HBA Discovery dialog box
2. From the Host Name list, select the host name from where you will discover the HBA. For the first time, the Host Name list will contain only the Local host. You must specify the Hostname 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.
14
Logging off HCM
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 HBAs that are installed in that server are refreshed each time the poll occurs.
NOTE
If the Keep Polling check box is checked, polling occurs after the specified polling interval. If the check box is not checked, polling stops. 6. Click OK.
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.
15
Logging off HCM
16
Chapter
Host Configuration
In this chapter
Host security authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffer credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot code image upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HCM Logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced port configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Name configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 22 22 33 35 37 39 40 43
Host security authentication

Authentication configuration can occur at three levels:
Host Adapter Port

Use the HCM GUI or the Brocade command line utility (BCU) to display the authentication settings and status. Diffie-Hellman (DH) key exchange is a public key cryptosystem where public values are exchanged to arrive at a symmetric key among the end entities. There are five well-known DH groups, however, only DH-CHAP group 0, called NULL DH, is supported in this release.
NOTE
Security authentication is not supported on Solaris platforms.
17
Configuring security authentication using the GUI

The security authentication dialog can be launched from host, HBA, and port levels.
NOTE
FC-SP is not available for Solaris agents. From the host level: 1. Select the host from the device tree. 2. Select Configure > FC-SP from the main menu. OR Right-click the host and select FC-SP 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
From an HBA level: 1. Select the HBA from the device tree. 2. Select Configure > FC-SP from the main menu. OR Right-click the HBA and select FC-SP from the list.
18
The Fibre Channel Security Protocol Configuration dialog at the HBA level displays.
FIGURE 8
From a port:
Fibre Channel Security Protocol Configuration - HBA level dialog box
1. Select a port from the device tree. 2. Select Configure > FC-SP > Authentication from the main menu. OR Right-click a port and select FC-SP > Authentication from the list. The Fibre Channel Security Protocol Configuration dialog at the port level displays.
FIGURE 9
Fibre Channel Security Protocol Configuration - port level dialog box
19
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. 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 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 command to display or configure security authentication for the ports.
bcu> bcu> bcu> bcu> bcu> bcu> auth auth auth auth auth auth -show <port_id> -policy <port_id> {on|off} -algo <port_id> <md5|sha1|ms|sm> -secret <port_id> <secret_string> --stats <port_id> --statsclr <port_id>
where: - -show port_id - -policy Displays the authentication settings and the current status. Specifies the ID of the port for which you want to display information. Sets the authentication policy and enable or disable authentication. 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.
port_id
20
on|off
Specifies the state of the authentication policy: policy 2/1 on means authentication is turned on, policy 2/1 off means authentication is turned off. Sets the authentication algorithm. Specifies the ID of the port for which you want to set the authentication algorithm. Specifies the hash algorithm: MD5 defines MD5 as the only hash algorithm (the default). SH1 defines SHA-1 as the only hash algorithm. MS defines the hash algorithm priority list of MD5 followed by SHA-1 for DH-CHAP authentication. SM defines the hash algorithm priority list of SHA-1, followed by MD5 for DH-CHAP authentication.
- -algo port_id
md5|sha1|ms|sm
- -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 maximum length of the secret is 63 bytes. The default secret for each interface is its pwwn without the colons; for example, 0102030405060708. 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.
- -stats port_id - -statsclr port_id
Refer to auth on page 123 for details about these commands.
21
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). 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 4 lists the features and configuration options.
TABLE 4
Basic port configuration options

Configurable using the GUI
Yes Yes Yes Yes
Port configuration parameter

Port logging level Configure speed Frame data field size Persistent Binding Note: The persistent binding option is available on Windows platforms only. QoS1 MPIO mode Path Time Out 2 Target Rate Limiting Boot over SAN Boot code image upload
1 2
Configurable using the BCU

Yes Yes Yes Yes
For more information

Port logging level Port speed Frame data field size Persistent binding
QoS MPIO Path Time Out Target rate limiting Boot over SAN Boot code image upload
QoS and Target Rate Limiting cannot be enabled at the same time. Path Time Out is available only when MPIO is disabled.
22
Opening the Basic Port Configuration dialog box

There are slight changes in HCMs basic port configuration dialog, depending on the operating system. 1. Select an HBA or port from the device tree. 2. Select Configure > Basic Port Configuration from the main menu. The Basic Port Configuration dialog box displays.
FIGURE 10
Basic Port Configuration dialog box - Windows, Linux, and VmWare
Port logging level

The number of messages logged by the host depends on the predetermined logging level. Although the HBA might generate many messages, only certain types of messages are logged based on the specified logging level.
Configuring the port logging level using the GUI

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, and Log Info. 3. Click Apply to apply the changes. 4. Click OK to save the changes and close the window.
23
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> [<Critical | Error | Warning | Info>] -m <fw|half|fcs|drv|aen|all>]
where: - -level port_id Specifies the number of messages logged by the host 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. fw | ha1 | fcs | drv | aen | all Specifies the mode. Refer to log on page 141 for details about this command.
Critical | Error | Warning | Info
Port speed
Beyond the number of ports, it is important to also consider port speed, which 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) and the speed options are 1 Gbps, 2 Gbps, 4 Gbps, and 8 Gbps. Auto-negotiate is the recommended setting, and it is the default. 8 Gbps ports do not support a port speed setting of 1 Gbps.
NOTE
Configuring the port speed using the GUI

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. Speed options are 1 Gbps, 2 Gbps, 4 Gbps, and 8 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. 3. Click Apply to apply the changes. A port disable/enable configuration dialog displays, confirming the configured speed, which will take effect when the port is disabled or enabled.
24
FIGURE 11
Port disable/enable Configuration dialog box
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> <1|2|4|8|auto>
where: - -speed Displays 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. Note: Values 1, 2, 4, and 8 mean a single-port speed setting. The speed value is a bit mask that specifies speeds to be considered for auto-negotiation. port_id Specifies the ID of the port for which you want to set the port speed. 1|2|4|8|auto Specifies the port speed. Supported values are:
auto - auto-negotiates the speed. 1 - 15 - bit mask of speeds 1/2/4/8 Gbps.

Refer to port on page 145 for details about this command.
Frame data field size

Fibre Channel data is organized in frames that can be concatenated into sequences to create large block transfers. The frame size depends on the HBA and the target and can be in the range of 512 bytes to 2 KB. The maximum amount of frame data is governed by buffer credits that, if insufficient for the link distance and speed, can severely limit performance.
Specifying the maximum frame size using the GUI

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. The default value is 2112. 3. Click Apply to apply the change. 4. Click OK to close the window.
25
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 current receive buffer size displays. 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> <df_size>
NOTE
where: - - dfsize port_id df_size Specifies the ID of the port for which you want to set the frame data field size. Specifies the maximum supported receive data field size, in decimal value. If set to auto, the driver default value displays.
Refer to port on page 145 for details about this command.
Persistent binding
Persistent binding is a feature of Fibre Channel (FC) host bus adapters that 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).
Configuring persistent binding using the GUI

The Persistent Binding dialog box can be launched at the host, HBA, or port level.
NOTE
Persistent Binding is available in the Windows environment only. From the host level: 1. Select a host and select Configure > Persistent Binding from the main menu. OR 2. Select and right-click a host in the device tree and select Persistent Binding from the list.
NOTE
The SCSI Target ID is unique. See the SCSI protocol for the valid target ID range.
26
The Persistent Binding dialog box (host level) displays, listing all the adapters in that host.
FIGURE 12
Persistent Binding dialog box - host level
From the HBA level: 1. Select an HBA and select Configure > Persistent Binding from the main menu. OR 2. Select and right-click an HBA in the device tree and select Persistent Binding from the list.
27
The Persistent Binding dialog box (HBA level) displays.
FIGURE 13
Persistent Binding dialog box - HBA level
From the port level: 1. Select a port and select Configure > Persistent Binding from the main menu. OR 2. Select and right-click a port in the device tree and select Persistent Binding from the list. The Persistent Binding dialog box (port level) displays.
FIGURE 14
Persistent Binding dialog box - port level
28
Enabling and disabling persistent binding using the GUI

Persistent binding can be enabled or disabled from the HCM GUI using the following steps: 1. Launch the Basic Port Configuration dialog at the port level. 2. Check or uncheck the persistent binding check box in the Basic Port Configuration dialog.
NOTE
The Persistent Binding check box is not available for Solaris agents.
Enabling and disabling persistent binding using the BCU

Target persistent binding enables target port world wide name binding to a persistent target ID for the OS stack. Using the -list operand, you can query the list of mappings from the persistent binding module. Enter the following command to configure target persistent binding.
bcu> pbind -enable <port_id> bcu> pbind --disable <port_id> bcu> pbind --list <port_id> [<pwwn>]
where: - -enable port_id - -disable port_id - -list port_id pwwn Enables target persistent binding. Specifies the ID of the port on which you want to enable persistent binding. Disables target persistent binding. Specifies the ID of the port for which you want to disable persistent binding. Queries the list of mappings from the persistent binding module. Displays the ID of the port for which you want to display information. Displays the ports world wide name.
Refer to pbind on page 144 for details about this command.
QoS
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 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):
HBA QoS 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.
29
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 Network (AN) license is required on the switch to enable QoS on the switch ports. You enable or disable QoS settings on ports with the portCfgQos command. Refer to the Fabric OS 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.
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 command to enable or disable QoS support on the HBA side.
bcu bcu bcu bcu bcu qos qos qos qos qos -enable <port_id> --disable <port_id> --query <port_id> --stats <port_id> --statsclr <port_id>
NOTE
where - -enable port_id - -disable port_id - -query port_id - -stats port_id - -statsclr port_id Enables QoS on the HBA. Specifies the ID of the port you want to enable. Disables QoS on the HBA. Specifies the ID of the port you want to disable. Displays details of the parameters exchanged during QoS negotiation. Specifies the ID of the port for which you want to query port information. Displays the statistics that are associated with the port. Specifies the ID of the port for which you want to display statistical information. Clears the statistics that are associated with the port. Specifies the ID of the port for which you want to clear statistical information.
30
MPIO
Multipathing solutions use redundant physical path components such as adapters, cables, and switches to create logical paths between the server and the storage device. In the event that one or more of these components fails, causing the path to fail, multipathing (MPIO) uses an alternate path for I/O so that applications can still access their data.
Specifying the MPIO using the GUI

1. Select Configure > Basic Port Configuration from the Host Connectivity Manager. The Basic Port Configuration dialog box displays. 2. Click the MPIO Mode Enable check box. 3. Click OK to close the window.
Specifying MPIO using the BCU

Enter the following command to set the MPIO mode to on or off. If the MPIO mode is off, you can specify an optional path time out value (TOV) in seconds (1 to 60). A timeout value of 0 is the default.
bcu> fcpim --mpiomode <port_id> {on|off [tov]}
where: - - mpiomode port_id on|off tov Specifies the ID of the port for which you want to enable or disable the FCP initiator mode. Specifies whether MPIO mode is enabled (on) or disabled (off). You can optionally specify the time out value (TOV).
Refer to fcpim on page 135 for details about this command.
Path Time Out

You can enable or edit the Path Time Out field only when MPIO is disabled.
Specifying Path Time Out using the GUI

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 text field. Its value range is 0 to 60. A timeout value of 30 is the default. 3. Click OK to close the window.
31
Specifying Path Time Out using the BCU

Enter the following command to set the MPIO mode to on or off. If the MPIO mode is off, you can specify an optional path time out value (TOV) in seconds (1 to 60). A timeout value of 30 is the default.
bcu> fcpim --mpiomode <port_id> {on|off [tov]}
where: - - mpiomode port_id on|off tov Specifies the ID of the port for which you want to enable or disable the FCP initiator mode. Specifies whether MPIO mode is enabled (on) or disabled (off). You can optionally specify the time out value (TOV).
Refer to fcpim on page 135 for details about this command.
Target rate limiting

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. Target rate limiting is new to version 1.1.
Configuring rate limiting on the HBA side using the BCU

Enter the following command to enable or disable rate limiting on the HBA side. 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 bcu bcu bcu ratelim ratelim ratelim ratelim -enable <port_id> --disable <port_id> --query <port_id> --defspeed <port_id>
NOTE
32
where - -enable port_id - -disable port_id - -query port_id - -defspeed port_id Enables target rate limiting. Specifies the ID of the port you want to enable. Disables target rate limiting on the HBA. Specifies the ID of the port you want to disable. Queries information about the port. This provides the ports status and information. Specifies the ID of the port for which you want to query port information. Displays the rate limiting speed. Specifies the rate limiting speed for the port. Options include 1 Gbps, 2 Gbps, and 4 Gbps.
Boot over SAN

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 HBA driver are installed on the remote device, the HBA BIOS and user-configurable boot instructions stored in HBA 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 HBA 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 Fibre Channel HBA Installation and Reference Manual for instructions. 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. All configuration is stored in HBA flash memory.
NOTE
33
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. 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.
FIGURE 15
Boot over SAN dialog box
3. Click the BIOS Enable check box to enable Boot Over SAN. 4. Select a speed from the list. Auto Negotiate is the default and the recommended setting. Other speed options include 1G, 2G, and 4G (for 4G cards) and 2G, 4G, and 8G (for 8G cards). 5. From the Boot Option list, select one of the following:
Auto Discovered from Fabric - 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. 6. 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 HBA to be accessible as boot LUNs. 7. Click OK. The Vendor Info, LUN Capacity, and Accessible status that correspond to the selected boot device and LUN display automatically.
34
Boot code image upload

Follow these steps to upload the latest boot code using either the HCM GUI or the BCU.
Updating boot code using the GUI

The ability to upload the boot code image is new to version 1.1. 1. Download the boot code (bfa_boot_fw) from www.brocade.com/hba to a folder on your local drive. 2. Launch HCM. 3. Right-click a host or adapter from the device tree select Upload Boot Code Image from the list.
NOTE
Right-clicking a host uploads the boot code image to all HBAs that are installed on the
host.
Right-clicking an adapter uploads the boot code image to the selected HBA only.
The Boot Code Image Upload dialog displays.
FIGURE 16
Boot Code Image Upload dialog box
4. Click the Browse button and navigate to the location of the boot code image.
35
FIGURE 17
Boot Code Image Upload browse dialog box
5. Select the boot code image and click Open. The selected file uploads. If an error occurs during the uploading process, an error message displays.
Uploading the boot code image using the BCU

Download the latest boot code file for installed Brocade HBAs from the Brocade HBA website and upload to the HBA installed on your host system using the following BCU commands. Enter the following command to upload the image file. boot commands are not available on Solaris platforms.
bcu boot -upload [-a] [adapter_id] <image_file> bcu boot --blunZone -c <BLUN> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#>
NOTE
where: - -upload adapter_id image_file -a - - blunzone c BLUN p port_wwn Updates the boot code in flash. Specifies the ID of the adapter (HBA). The adapter ID could be adapter_id, adapter-sn, adapter-name, adapter-hwpath. Specifies the name of the firmware image file. Indicates the boot code will be uploaded to all the Brocade HBAs found on the host. Do not specify the adapter ID if you specify -a. Creates the zonecreate command to be run on the switch. Specifies the boot LUN. Specifies the ports world wide name.
36
Virtual Port configuration
r rport_wwn l lun_id|lun#
Specifies the remote ports world wide name. Specifies the 8 hexadecimal-byte LUN number string or a one hexadecimal-byte LUN ID.

Virtual ports (V_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.
NOTE
You cannot create a V_Port that already exists in the Names dialog. If you need to re-create a V_Port that has been deleted through an interface other than the currently-managing HCM or the V_Ports deleted on Linux servers reboot, you must first manually remove the V_Ports WWN from the Names dialog box in HCM. If you do not manually remove the V_Port from HCM, an error message displays that the V_Port already exists. See Removing a name entry on page 45 for instructions.
Creating a Virtual Port

V_Port configuration is new to version 1.1. Virtual ports are not supported for VMware and Solaris agents. 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. The Virtual Port Creation dialog box 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.
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.
37
FIGURE 18
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 text box. 6. Click OK to apply the changes and close the window.
Deleting a Virtual 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 pop-up warning message displays, asking for confirmation. 3. Click OK to continue. The Virtual Port Deletion dialog box displays. 4. Click the check box that corresponds to one or multiple virtual ports you want to delete, and click the Delete Selected button. If you want to delete all virtual ports, click the Delete All button.
NOTE
You can also select a base port from the device tree and delete it the same way you delete a virtual port.
38
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, TRACE, which is the most verbose and the default, is used.
Configuring the HCM logging level using the GUI

1. Select Configure >HCM Logging Levels from the Host Connectivity Manager. The Configure HCM Logging Levels dialog box displays.
FIGURE 19
Configure HCM Logging Levels dialog box
2. From both the Agent Communication Log and the Debug Log, select one of the following:
Trace, which is the most verbose. Debug Info Warning Error Fatal, which is the least verbose.
3. Click Apply to apply the change.
39
Advanced port configuration

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 5 lists the features and configuration options.
-
TABLE 5
Advanced port configuration options

Configurable using the GUI
Yes Yes Yes Yes
Port configuration parameter

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

Yes Yes Yes Yes
Opening the Advanced Port Configuration dialog box

1. Select an HBA or port from the device tree. 2. From the Host Connectivity Manager, select Configure > Port Configuration > Advanced. The Advanced Port Configuration dialog box displays.
FIGURE 20
Advanced Port Configuration dialog box
40
Queue Depth configuration

The queue depth is the number of I/O operations that can be run in parallel on a device. When the queue is full, the drive refuses to accept any additional SCSI commands. The device continues to refuse new commands until at least one command has been completed, freeing up space in the queue.
Configuring the queue depth using the GUI

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 queue depth (a value that represents the number of parallel I/O operations). The valid queue depth range is 0-2000. 3. Click OK.
Configuring the queue depth using the BCU

Enter the following command to set the queue depth.
bcu fcpim --qdepth <port_id> <q_depth_value>
where: - -qdepth port_id The number of I/O operations that can be run in parallel on a device. Specifies the ID of the port for which you want to enable or disable the FCP initiator mode.
q_depth_value Specifies the queue depth value.
Interrupt Control Coalesce

To avoid flooding the host system with too many interrupts, packets are collected and one single interrupt is generated for multiple packets. This is called interrupt coalescing. For receive operations, interrupts typically inform the host CPU that packets have arrived on the devices input queue. Without some form of interrupt moderation logic on the adapter, this might lead to an interrupt for each incoming packet. However, as the incoming packet rate increases, the device driver finishes processing one packet and checks to see if any more packets are on the receive queue before exiting the driver and clearing the interrupt. The driver then finds that there are more packets to handle and ends up handling multiple packets per interrupt as the packet rate increases, which means that the system gets more efficient as the load increases.
41
Configuring the Interrupt Control Coalesce using the GUI

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. Specify the latency monitor time out value in microseconds, if coalesce is set to on.
Latency time out values supported are 0-225 microseconds. Setting the latency time out value to 0 disables the latency monitor time out interrupt.
Specify the delay time out value in microseconds, if coalesce is set to on. Delay time out
values supported are 0-1125 microseconds. Setting the delay time out value to 0 disables the latency monitor time out interrupt. 3. Click OK.
Configuring Interrupt Control Coalesce using the BCU

The intr command sets the ports interrupt attributes.
NOTE
Note: The operation fails if the input parameters are out of the supported range. Enter the following command to set Interrupt control coalesce, latency, and delay.
bcu ioc --intr <ioc_id> <--coalesce|-c> {on | off} <Latency> <Delay>
where: - -intr port_id c coalesce Latency Specifies the ID of the port for which you want to set the ports interrupt attributes. Displays the coalescing flag values. Supported values are on or off. Specifies the latency monitor time out value in microseconds, if coalesce is set to on. Latency time out values supported are 0-225 microseconds. Setting the latency time out value to 0 disables the latency monitor time out interrupt. Specifies the delay time out value in microseconds, if coalesce is set to on. Delay time out values supported are 0-1125 microseconds. Setting the delay time out value to 0 disables the delay timeout interrupt.
Delay
42
NPIV
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 switch is 255. 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. only. No settings are available for vports from basic port configuration. NPIV is not supported on Solaris platforms.
NOTE
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 perform the following name tasks using either the Configure Names dialog or the Define Names dialog:
Associate a name that represents an adapter, port, virtual port, or remote port. 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.
You can launch the Define Names dialog by right-clicking an HBA, port, remote port, or V_port.
NOTE
43
Name configuration
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 HBA and HBA 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 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 discovered and detached (undiscovered) names.
FIGURE 21
Configure Names dialog box
2. Select a row and edit the name, the WWN, and the description, as needed. 3. Click OK.
44
Name configuration
Adding name entries

You can add up to 2000 names which are then stored in the HbaAliasdb.properties file. The entries persist during reboot. The WWN types are:
Node Port Remote Port V_Port Dual Role (port type that acts as initiator and target) Unknown
1. Select Configure > Names from the Host Connectivity Manager. 2. Type a name that represents an adapter, port, or storage device into the Name text box. 3. Type a valid WWN that corresponds to the name. 4. Click OK to close the window. The new component is added to the Name list.
Removing a name entry

The Remove functionality clears the name and description values of a selected detached WWN. 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 all the names available at the host. 2. 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. 3. 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. 4. Click OK to close the window.
45
Name configuration
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 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 L_Ports Only V_Ports Only Remote Ports
3. Click the Export button. The Save dialog box displays. You can save the properties file in .txt, .csv, or .properties format. 4. Name the file, and click Save. 5. Click OK to close the window.
Importing the properties for a WWN

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.
46
Name configuration
Importing properties in 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. 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=
Importing properties in Fabric Manager (FM) format

1. In the Configure Names dialog box, select FM Format and then select Import. 2. 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
3. Click OK.
47
Name configuration
Importing duplicated names

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. If there are duplicate names, the Duplicated Names dialog box displays.
FIGURE 22
Duplicated Names dialog box
2. Determine which method you will use to fix the name policy violation, and click the appropriate button.
Append incremental numbers for all repetitive names - Click to instruct the software to add
incremental numbers to fix the duplicated names.
I will fix them myself - Change duplicate names using the procedure in Editing the name
fields on page 44. 3. Click OK.
48
Chapter
Monitoring
In this chapter
Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Master Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Application log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Performance monitoring
The Host Connectivity Manager (HCM) Port Statistics window enables you to monitor the performance of the HBA and the traffic between the HBA and the LUNs. You can use the information to isolate and troubleshoot areas that impact application performance. The following components display statistics:
Fabric statistics FCP IM statistics IOC statistics Logical port statistics Port statistics QoS statistics Remote port statistics Virtual port (vport) statistics
49
Performance monitoring
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.
Controlling the polling frequency rate

To control port statistics polling, do one of the following from any of the Statistics dialog boxes. 1. Click the Start Polling box to manually poll the port statistics. 2. Type the polling rate in the Polling Frequency in Seconds text box. The range is between five and 3600 seconds. The default is five seconds. 3. Click the Stop Polling box to stop port statistics polling. 4. Check the Keep Running Data check box to see the trend.
Resetting statistics
1. Click the Reset button on any of the Statistics dialog box. A warning dialog displays.
FIGURE 23
Reset Statistics warning
2. Click Yes. All of the statistics are reset to 0.
50
Master Log
Master Log
The Master Log Properties dialog box, described in Table 6, displays a list of all events that have occurred. Event monitoring enables early fault detection and isolation on a selected HBA. You can filter the events based on the user-defined criteria shown in Figure 24.
TABLE 6
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 of the device on which the event occurred. Displays the category of event; for example, Rport or ITNIM. Displays the subcategory of the main category. Displays a brief description of the event. Displays the date and time when the event occurred.
Clear Filter button Sr No column Severity column WWN column Category column Subcategory column Description column Date/Time column
Event severities
Table 7 describes the icons that represent the four event types.
TABLE 7
Description
HCM Master Log icons
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.
51
Master Log
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 of a combination of the criteria shown in Figure 24.
NOTE
The Category is the type of event; for example, an adapter, port, or audit.
FIGURE 24
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.
52
Application log
Application log
The application log 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
FIGURE 25
HCM Application Log
53
Syslog support
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 log files. By default, the location is /opt/hcmagent/log/hbaEvents.log.
Opening the Syslog Server Configuration dialog box

1. Select an HBA from the device tree. 2. Select Configure > Syslog from the main menu. The Syslog Server Configuration dialog box displays.
FIGURE 26
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.
54
Syslog support
Removing a host server

1. Select Configure > Syslog from the main menu. The Syslog Server Configuration dialog box displays. 2. Select the host name in the list. 3. Click Remove to remove the host as a Syslog destination. 4. Click OK to close the dialog box.
55
Syslog support
56
Chapter
Diagnostics
In this chapter
Diagnostics using the Brocade Command Line Utility (BCU) . . . . . . . . . . . . Diagnostics using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beaconing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SFP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . supportSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58 59 64 64 66 66
Related Diagnostic Documentation

The information in this chapter is specific to commands that support the Brocade Fibre Channel HBA. You can run diagnostics using the Brocade Command Line Utility (BCU) or the Host Connectivity Manager (HCM) GUI. For more information, refer to the documentation listed in Table 8.
TABLE 8
Part Number
Related diagnostic documentation

Document Title
Brocade Fibre Channel HBA Installation and Reference Manual supporting HBA models 815, 825, 415, and 425 Brocade Fibre Channel HBA Troubleshooting Guide supporting HBA models 815, 825, 415, and 425 Fabric OS Administrators Guide supporting Fabric OS v6.1.0 Fabric OS Troubleshooting and Diagnostics Guide supporting Fabric OS v6.1.0
53-1000884-02 53-1000885-02 53-1000598-04 53-1000853-02
57
Diagnostics using the Brocade Command Line Utility (BCU)
Diagnostics using the Brocade Command Line Utility (BCU)

The purpose of diagnostic commands is to evaluate the integrity of the system hardware.
diag commands
diag commands monitor hardware components and can be performed while the system is running (they are non-disruptive).
Command
sfpshow tempshow beacon pciloopback loopback memtest
Description
Displays small form factor pluggable (SFP) information. Displays adapter information. Blinks the appropriate port LED for physical identification. Beaconing can occur at the port or the link level. Checks the communication path between the host and the IO Controller (IOC). Sends a health check message from the host to firmware through message queues that are memory-mapped over the PCI. Tests memory blocks of the adapter.
Refer to diag on page 130 for details about this command.
fcdiag commands
Fibre Channel diagnostics include the following tests on Fibre Channel components.
Command
fcping fctraceroute fcecho linkbeacon scsitest
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 link. Tests the SCSI components.
Refer to fcdiag on page 132 for details about this command.
58
Diagnostics using the GUI

You can run diagnostic tests using the GUI at the port level or the protocol level. When you invoke a test on an HBA, you can run diagnostics for one or both ports within the selected HBA.
NOTE
Running a hardware-level test using the GUI

1. Select an HBA 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 is displayed.
FIGURE 27
Diagnostics - Port Tests dialog box
59
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 9.
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.
Hardware-level test parameters

TABLE 9
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 will be disabled.

PCI loopback test Frame Count Data Pattern Test Cycle Port loopback test Subtest ID
Internal Serdes External loopback
NOTE: For an External Loopback test, you must plug in the loopback connector.
Link Speed
8 Gb HBA: 2 Gbps 4 Gbps 8 Gbps 4 Gb HBA 1 Gbps 2 Gbps 4 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.
Frame Count Test Cycle Data Pattern (hexadecimal)
60
Running a protocol-level test using the GUI

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 HBA 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 is displayed. 3. Click the Protocol Tests tab.
FIGURE 28
Protocol-level tests dialog box
61
Displaying test log details
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.

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 displays. See Figure 29 and Figure 30 for examples of test log detail. Fields and components
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
62
FIGURE 29
Test Log Details for Echo Test dialog box
FIGURE 30
Test Log Details for FC trace test dialog box
63
Beaconing
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 HBA side and the switch side.
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>[<duration>]
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 130 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 132 for details about this command.
Configuring beaconing using the GUI

1. Select Configure > Beacon from the Host Connectivity Manager. 2. Click either the Beacon Port check box or the Beacon Link check box to enable the feature.
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

Only Brocade-branded SFPs are supported with the 8 Gbps FC HBAs. The 8 Gbps SFP (which is bundled with the Brocade 815 or 825), is referred to as SFP+. The 4 Gbps SFP (which is bundled with the Brocade 415 or 425) is simply referred to as SFP. 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>
NOTE
Refer to diag on page 130 for details about this command.
64
SFP Management
Displaying SFP information using the GUI

1. Select a port in the device tree. 2. Click the SFP tab in the right pane. 3. The SFP Properties panel displays.
FIGURE 31
SFP Properties
Details about the port technology and extended link are described in Table 10.
TABLE 10
SFP category
SFP management information

SFP information displayed
Port technology
Extended information
SFP supported Connector type Transceiver Media Speed (in MBps) Extended ID Encoding Baud rate Length (9u, 50u, 62.5u, Cu) Vendor (name, OUI, part) Revision Wavelength Options BR Max BR Min Serial number Date code
65
Debugging
Debugging
The debug commands, listed below, capture all the support information needed to diagnose suspected system issues.
supportSave
Collects debug information from the driver logs and stores the error messages in an output file.
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 128 for details about these commands.
supportSave
The supportSave command collects debug information needed from the driver. 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 11.
TABLE 11
supportSave categories
Captured information
HCM GUI-related engineering logs Events Configuration files Operating-specific information Environment information Data.xml file Vital CPU, memory, network resources HCM Agent (logs, configuration) Driver logs (bfa_supportSave output) Install logs Core files
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. For example:
HCM Installation DIR\data\10.32.116.1\supportSave C:\Program Files\BROCADE\FCHBA\client\data\10.32.116.1\supportSave
66
supportSave
supportSave collection sources

Table 12 lists the sources from which you can gather supportSave information.
TABLE 12
supportSave collection sources

supportSave information collected
Driver-related logs and config files Driver-related logs andconfig files Agent log/config files Agent log and config files HCM GUI log and config files
Source of supportSave information

BCU-based supportSave Browser-based supportSave HCM-based supportsave
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.
supportSave collection using the GUI

There are two ways to trigger a support save collection using the GUI, explained in this section. 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.
supportSave collection on a port crash event

If the port crashes and triggers a port crash event, support save data is collected at a system-wide level. An application log message is generated with the following message:
Port Crash Support Save Completed
Port crash events have a CRITICAL severity and you can view the details in the Master Log and Application Log tables in HCM. For more information, refer to Master Log on page 51 and Application log on page 53.
67
supportSave
supportSave collection using a command prompt

Enter the following command to run the supportSave command.
bfa_supportSave [destination_directory]
Refer to diag on page 130 for details about these commands.
supportSave collection using a 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). 1. Open an Internet browser and type the following URL: https://localhost:34568/JSONRPCServiceApp/SupportSaveController.do where localhost is the IP address of the server from which you want to collect the 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.
68
Chapter
HCM Dialog Boxes
In this chapter
Authentication Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Backup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Base Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Change HCM User Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Change HCM Agent dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Configure Names dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Define Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Duplicated Names dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Event Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Fabric Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 FCP IM Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Fibre Channel Security Protocol dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 83 HBA Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 IOC Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 LPORTs Properties panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Logical Port Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 LUN Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Master Log tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Master Log Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Persistent Binding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Port POM Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Port Tests Diagnostics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Protocol Tests Diagnostics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 QoS Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Remote Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 SFP Properties panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Syslog Server Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Target Statistics dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Test Log Details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
69
In this chapter
Virtual Port Creation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Deletion dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Port Statistics dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113 114 115 116
70
Authentication Statistics dialog box
Authentication Statistics dialog box

The Authentication Statistics dialog box enables you to display statistical information related to transmitted and received DHCHAP attempts for a selected port. Opening the dialog box 1. Select a port from the device tree. 2. Select Configure > FC_SP > Authentication Statistics from the Host Connectivity Manager. Fields and components
Field
Date Auth Failures Auth Successes Tx Auth Rjts Tx Negs Tx Auth Dones Tx DHCHAP Challenges Tx DHCHAP Replies 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 DHCHAP challenge attempts. The number of transmitted DHCHAP replies. 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 DHCHAP challenge attempts. The number of received DHCHAP replies. The number of times a received DHCHAP challenge was successful.
Using the dialog box Refer to the following topics for specific procedures using this dialog box.
Configuring security authentication using the GUI Port Statistics dialog box Polling frequency rate Resetting statistics Performance monitoring
71
Backup dialog box
Backup dialog box

The Backup dialog box allows you to create backup of data and configuration files. Opening the dialog box Select Tool > Backup Data from the Host Connectivity Manager. Fields and components
Field
Output Directory text box Browse button Start Backup button Close button
Description
Enter the location of the directory in which you will back up the data and configuration files. Click to browse to the location of the backup directory. Click to instruct the system to backup the data and configuration files to the designated location. Click to close and exit the Backup dialog box.
72
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 properties panel 1. From the device tree, select a base port. 2. In the right pane, click the Base Port Properties tab. Fields and components
Field
Port WWN Node WWN FC Address State Symbolic Name Roles Base Port Switch NWWN Switch IP Address
Description
The world wide name of the base port. The world wide name of the device. The Fibre Channel address of the base port. Indicates whether the base port is online or offline. The symbolic name associated with the base port. The role of the base port; for example, FCP Initiator. The name of the base port. The world wide name of the switch. The IP address of the switch.
73
Change HCM User Password dialog box
Change HCM User Password dialog box

The Change HCM Password dialog box enables you to change an existing password for the application. Opening the dialog box Select Configure > Change HCM Password from the Host Connectivity Manager. Fields and components
Field
User Name Old password New password Confirm New password
Description
Displays the predefined user name (Administrator). Type your existing password. Type a new password. Confirm your new password by retyping it.
Using the dialog box Refer to the following topic for specific procedures using this dialog box.
74
Change HCM Agent dialog box
Change HCM Agent dialog box

The Change HCM Agent Password dialog box enables you to change an existing password for the host. Opening the dialog box Select Configure > Change Password > Change Agent Password from the Host Connectivity Manager. Fields and components
Field
Host Name User Name Old password New password Confirm New password
Description
Displays the IP address of the host. Displays the predefined user name (admin). Type your existing password. Type a new password. Confirm your new password by retyping it.
75

The Configure Names dialog box enables you to perform the following tasks:
Search by name or world wide name. Add a world wide name and an associated name for an adapter, port, or storage device that is
not yet discovered.
Remove a device from the Name display list. Import from or export properties to a file.
Opening the dialog box Select Configure > Names from the Host Connectivity Manager. Fields and components
Field
Display 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.
WWN The world wide name for all configured devices.
NOTE: You can also search for a name by typing the world wide name into the text box and clicking OK.
Type Description Remove Import Export Add button EFCM / FM format 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. Enables you to import properties in EFCM or FM format.
Name configuration Adding name entries Removing a name entry Exporting the properties for a WWN Importing the properties for a WWN
76
Define Name dialog box
Define Name dialog box

The Define Name dialog box enables you to assign a name to an existing world wide name. Opening the dialog box 1. Right-click on an HBA, port, remote port, or virtual port in the device tree. 2. Type a name that represents an adapter, port, or storage device.
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. Fields and components
Field
WWN Name Type Description
Description
The world wide name for the device. Enter a meaningful name for the device. Select the type of device from the list; for example, Node or Port. Enter a description of the device.
77

The Duplicated Names dialog box enables you to display configured names that are redundant. Opening the dialog box 1. Select Configure > Names from the Host Connectivity Manager. 2. Click Fix Duplicates. Fields and components
Field
Append incremental numbers for all repetitive names button I will fix them myself button Name WWN Operational Status 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 with which the duplicated name is associated. The operational status of the duplicate WWN (for example, Discovered). A description of the duplicate name.
78
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. Opening the dialog box 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. Fields and components
Field
Date/Time Time Severity WWN 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 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 Event severities Filtering event log entries
79
Fabric Statistics dialog box
Fabric Statistics dialog box

The Fabric Statistics dialog box enables you to view statistics on a selected Fabric. The ability to view fabric statistics is new to version 1.1. Opening the dialog box Select Monitor > Statistics > Fabric Statistics from the Host Connectivity Manager. Fields and components
Field
Date FLOGI sent FLOGI rsp errors FLOGI accepts FLOGI rejects FLOGI unknown rsp FLOGI alloc waits FLOGI received FLOGI rejected Fabric Offlines Fabric Onlines
Description
The date the Fabric statistics were captured. 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 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 Fabrics that are offline. The number of Fabrics that are online.
Port Statistics dialog box Polling frequency rate Resetting statistics Performance monitoring
80
FCP IM Statistics dialog box

The FCP IM Statistics dialog box enables you to display Fibre Channel Protocol Input Method (FCP IM) statistical information for initiators and targets. Opening the dialog box 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. Fields and components
Field
Date RPort Onlines RPort Offlines PRLI Sent Fcxp Alloc Waits PRLI Rsp Errors PRLI Rsp Accepts Num Times in Initiator Mode HAL Online Events HAL Offline Events HAL Create Events HAL Delete Events HAL Create Completions HAL Delete Completions HAL SLER Events HAL IOC Down Events HAL IO Cleanup Completions HAL Task Management Commands HAL TM FirmwareResponses HAL TM Successes HAL TM Failures HAL TM Related IO Cleanups HAL TM Firmware Queue Resumed HAL TM Affected by IOC Down Events
Description
The date and time of the most recent reset. The number of online rports. The number of offline rports. The number of PRLIs sent. The number of Fcxp allocation waits. The number of PRLI response errors. The number of PRLI response accepts. The number of times the RPort has been in initiator mode. The number of HAL online events. The number of HAL offline events. The number of HAL create events. The number of HAL delete events. The number of HAL create completions. The number of HAL delete completions. The number of HAL SLER events. The number of HAL IOC Down events. The number of HAL IO cleanup completions. The number of HAL task management commands. The number of HAL task management firmware responses. The number of HAL task management successes. The number of HAL task management failures. The number of HAL TM-related IO cleanups. The number of times the HAL task management firmware queue is resumed. The number of times HAL task management is affected by IOC down events.
81
Field
HAL TM Affected by ITN Offline HAL TM Offline Cleanup Completions HAL IO Requests HAL IO Completions
Description
The number of times HAL task management is affected when ITN is offline. The number of HAL task management offline cleanup completions. The number of HAL IO requests. The number of HAL IO completions.
82
Fibre Channel Security Protocol dialog box
Fibre Channel Security Protocol dialog box

The Fibre Channel Security Protocol (FC SP) dialog box enables you to define security authentication on selected ports. Opening the dialog box 1. Select an HBA in the device tree. 2. Select Configure > FC_SP > Authentication Statistics from the Host Connectivity Manager. Fields and components
Field
Port # Port WWN Port Name Authentication Status CHAP Secret Retype Secret Algorithm Group
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. Type the CHAP secret. Retype the CHAP secret to confirm. The configured algorithm. Options include md5, sha1, md5sha1, shamd5. Indicates the DH group value. DHNULL (group 0) is the only option.
Configuring security authentication using the GUI Port Statistics dialog box Polling frequency rate Resetting statistics Performance monitoring
83
HBA Properties panel
HBA Properties panel

The HBA Properties panel enables you to display the properties that are associated with a selected HBA. Opening the properties panel 1. Select an HBA in the device tree. 2. Click the Properties tab in the right pane. Fields and components
Field
HBA Parameters Node WWN Name Operating Status Manufacturer Model Description Hardware Path Serial # Temperature Chip Revision Driver Parameters Driver Name Driver Version Firmware Parameters Firmware Version BIOS Version PCI Registers Vendor ID Device ID Subsystem ID Subsystem Vendor ID Current # of Lanes PCI Generation Initial Negotiated # of Lanes The identifier of the PCI Registers vendor. The device ID of the PCI Register. The ID of the PCI subsystem. 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 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 adapters 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 hardware path of the HBA. The serial number of the HBA. The temperature of the HBA, both in Celsius and Fahrenheit. The revision level of the chip.
Description
84
IOC Statistics dialog box

The IOC Statistics dialog box enables you to view statistics related to the input/output controller (IOC). The ability to view IOC statistics is new to version 1.1. Opening the dialog box Select Monitor > Statistics > IOC Statistics from the Host Connectivity Manager. Fields and components
Field
IOC driver statistics Mailbox interrupts Start events Stop events Enable events Disable events Heartbeat failures Firmware boots Stats timeouts IOC firmware statistics Heartbeat count Config requests Enable requests Disable requests Stats requests Clear stats reqs Unknown requests Intr coalesce reqs Firmware IO statistics IO aborts Implicit IO aborts IO timeouts ABTS failures EDTOV timer events RECTOV timer events Seq level rec failures Unexpected frames The number of times an I/O abort has occurred. The number of times an implicit I/O abort has occurred. The number of times an I/O has timed out. The number of ASCII Block Terminal Services failures on the firmware I/O. The number of Error Detect Time Out events. The number of Receiver Time Out events. The number of sequential level receive failures. The number of unexpected frames on the firmware I/O. The number of IOC firmware heartbeats. The number of IOC firmware configuration requests. The number of IOC firmware enable requests. The number of IOC firmware disable requests. The number of times statistics are requested on the IOC firmware. The number of times a clear statistics request has occurred. The number of IOC firmware requests that are unknown. The number of interrupt coalesce requests. The number of mailbox interrupts on the IOC driver. The number of start events that have occurred on the IOC driver. The number of stop events that have occurred on the IOC driver. The number of enable events that have occurred on the IOC driver. The number of disable events that have occurred on the IOC driver. The number of heartbeat failures on the IOC driver. The number of times a firmware boot has occurred on the IOC driver firmware. The number of timeouts that have occurred on the IOC driver.
Description
85
Field
Unexp fr - good rsp Unexp fr - bad rsp Sequence count errors IO underruns IO underrun errors IO overruns IO overrun errors Data out of range IO protocol errors Target IO aborts Firmware port (FPG) statistics FPG interrupts FPG level 0 intrs FPG 0 cause intrs FPG intr other FPG intr other ignored FPG signal lost FPG signal regained FPG sync lost FPG sync timeout FPG sync regained FPG div2 overflow FPG div2 underflow FPG efifo overflow FPG efifo underflow FPG IDLE primitives FPG LRR primitives FPG LR primitives FPG OLS primitives FPG NOS primitives
Description
The number of unexpected frames on the firmware I/O that resulted in a good response. The number of unexpected frames on the firmware I/O that resulted in a bad response. The number of sequential count errors. The number of I/O underruns. The number of I/O underrun errors. The number of I/O overruns. The number of I/O overrun errors. The percent of data that is out of range. The number of I/O protocol errors. The number of times the target I/O aborts.
The number of firmware port interrupts. The number of level 0 interrupts on the firmware port. The number of 0 cause interrupts on the firmware port. The number of other-type interrupts on the firmware port. The number of other-type interrupts that were ignored on the firmware port. The number of times a signal was lost on the firmware port. The number of times a signal was regained on the firmware port. The number of times loss of sync on the firmware port has occurred. The number of times sync timeout on the firmware port has occurred. The number of synchronizations that were regained on the firmware port. The number of div2 overflow events on the firmware port. The number of div2 underflow events on the firmware port. The number of elastic FIFO (EFIFO) overflow events on the firmware port. The number of elastic FIFO (EFIFO) underflow events on the firmware port. The number of IDLE primitive events on the firmware port. The number of Link Reset Response Primitive (LRR) transmit events on the firmware port. The number of Link Reset Primitive (LR) transmit events on the firmware port. The number of Offline Sequence Primitive (OLS) transmit events on the firmware port. The number of not operational events that have occurred on the firmware port.
86
Field
FPG LIP primitives FPG ARBFO primitives FPG MRK primitives FPG unknown primitives Firmware port PHYSM statistics Module inserts Module extracts Module invalid events Module validation ignored Laser faults Signal loss count Sync loss count Firmware port SNSM statistics HWSM success HWSM failures HWSM timeouts SWSM success SWSM timeouts Firmware port LKSM statistics HWSM success HWSM failures HWSM timeouts SWSM success SWSM failures
Description
The number of loop initialization (LIP) events that occurred on the firmware port. The number of ARBFO primitive events that occurred on the firmware port. The number of MRK primitive events that occurred on the firmware port. The number of unknown primitive events that occurred on the firmware port.
The number of module inserts in the Physical Port State Machine (PHYSM). The number of module extracts in the Physical Port State Machine (PHYSM). The number of module invalid events in the Physical Port State Machine (PHYSM). The number of module validation ignored events in the Physical Port State Machine (PHYSM). The number of laser fault events in the Physical Port State Machine (PHYSM). The number of times loss of signal has occurred. The number of times loss of sync has occurred.
The number of Hardware State Machine (HWSM) successes for the firmware port speed negotiation state machine. The number of Hardware State Machine (HWSM) failures for the firmware port speed negotiation state machine. The number of Hardware State Machine (HWSM) timeouts for the firmware port speed negotiation state machine. The number of Software State Machine (SWSM) successes for the firmware port speed negotiation state machine. The number of Software State Machine (HWSM) successes for the firmware port speed negotiation state machine.
The number of Hardware State Machine (HWSM) successes for the firmware port link state machine (LKSM). The number of Hardware State Machine (HWSM) failures for the firmware port link state machine (LKSM). The number of Hardware State Machine (HWSM) timeouts for the firmware port link state machine (LKSM). The number of Software State Machine (SWSM) successes for the firmware port link state machine (LKSM). The number of Software State Machine (SWSM) failures firmware port link state machine (LKSM).
87
Field
SWSM timeouts Busy buffer failures Bufwait state entries Link failures Prim seq protocol errs LR tx started LRR tx started OLS tx started NOS tx started
Description
The number of Software State Machine (SWSM) timeouts for the firmware port link state machine (LKSM). The number of failures that have occurred due to a busy buffer. The number of buffer wait state entries. The number of link failures on the firmware port. The number of primitive sequence protocol errors. The number of times Link Reset Primitive (LR) transmit started. The number of times Link Reset Response Primitive (LRR) transmit started. The number of times Offline Sequence Primitive (OLS) transmit was started. The number of not operational (link has failed) transmissions on the firmware port.
88
LPORTs Properties panel
LPORTs Properties panel

The LPorts Properties panel enables you to display the properties that are associated with a logical port. Opening the properties panel 1. From the device tree, select a physical port. 2. Click the LPORTs Properties tab in the right pane. Fields and components
Field
Base Port FC 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 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.
89
Logical Port Statistics dialog box

The Logical Port Statistics dialog box enables you to display statistics that are related to a selected logical port. Opening the dialog box 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. Fields and components
Field
Date NS plogin sent NS plogin accepts NS plogin rsp errors NS plogin accept errors NS plogin rejects NS plogin unknown rsp NS plogin alloc wait NS RSPN_ID sent NS RSPN_ID rsp errors NS RSPN_ID_rejects NS RSPN_ID alloc wait NS RSPN_ID sent NS_RSPN_ID_accepts NS RFT_ID sent NS RFT_ID accepts NS RFT_ID rsp errors NS RFT_ID rejects NS RFT_ID alloc wait NS_GID_FT sent
Description
The date and time of the most recent reset. The number of Name Server port logins sent. The number of times Name Server port logins are accepted. The number of Name Server response errors. The number of Name Server port login accept errors. 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 Name Server Register Symbolic Port Name identifier. 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 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 FC4 Type identifier requests sent. 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 times a Name Server Get all Port ID request for a given FC4 type is sent.
90
Field
NS_GID_FT accepts NS_GID_FT rsp errors NS_GID FT rejects NS_GID FT unknown rsp NS_GID FT alloc wait NS timeouts NS retries Num RSCNs Num port_ID RSCNs
Description
The number of times a Name Server Get all Port ID request for a given FC4 type is accepted. The number of response errors associated with a Name Server Get all Port ID request for a given FC4 type. 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 Name Server timeouts. The number of Name Server retries. The number of Fibre Channels Registered State Change Notifications. The number of Fibre Channels Registered State Change Notifications by port ID.
91
LUN Properties panel
LUN Properties panel

The LUN Properties panel enables you to display the properties of a selected logical unit. Opening the properties panel Select a LUN from the device tree. The LUN parameters display in the right pane. Fields and components
Field
LUN LUN ID Capacity Block Size Vendor Product ID Product Revision Product Serial # Target WWN
Description
The logical unit number of the Fibre Channel Protocol (FCP) device. The logical unit identifier. The capacity of the logical unit. The block size of the logical unit, in bytes (for example, 512 Bytes). The vendor of the device to which the logical unit is assigned. The product identifier of the device to which the logical unit is assigned. The revision level of the device to which the logical unit is assigned. The serial number of the device to which the logical unit is assigned. The world wide name of the target device.
92
Master Log tab
Master Log tab

The Master Log enables you to display a list of all events that have occurred. Opening the Master Log 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. Fields and components
Field
Filter button Clear Filter button Refresh button Sr No column Severity column WWN column Category column
Description
Click to launch the Master Log Filter dialog box. Click to clear the Master Log Filter parameters. Click to refresh the Master Log. Displays a numbering sequence in ascending order. The event severity (informational, minor, major, or critical). The world wide name of the device on which the event occurred. The event categories are as follows: ADAPTER - Events pertaining to the adapter 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
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.
93

The Master Log Filter dialog box enables you to filter the events you receive by time, severity, category, or world wide name. Opening the dialog box 1. Select the Master Log tab, located at the bottom pane of the Host Connectivity Manager, 2. Click the Filter button. Fields and components
Field
Event Time Event Severity Category WWN
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: Major, Minor, Critical, Info. Select an event category, for example, Rport or ITNIM, from the list. Select a world wide name from the list.
94
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 HBA level, or the port level. Opening the dialog box 1. Select Configure > Basic Port Configuration from the Host Connectivity Manaager. 2. Click the Enable Persistent Binding check box. Persistent Binding is enabled. 3. Select Configure > Persistent Binding. Fields and components
Field
At the host or HBA level Serial Number Hardware path Port # Port WWN Name Persistent Type Target Name Remote Port WWN SCSI Target ID At the port level HBA Node HBA Port Persistent type Target Name Remote Port WWN SCSI Target ID The world wide node name of the HBA node. The world wide name of the HBA 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 HBA. The location of the storage controller (PCI slot number). The port number of the HBA. 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
Basic port configuration Persistent binding Configuring persistent binding using the GUI
95
Port Properties panel

The Port Properties panel enables you to display the properties that are associated with a selected HBA port. Opening the properties panel 1. Select a port in the device tree. 2. Click the Properties tab in the right pane. Fields and components
Field
Port Parameters Port # Port WWN Node WWN Port Type Name FC Address Configured Port State Operating State Configured Speed Operating Speed Max Speed Supported Configured Topology Operating Topology BB Credit Frame Data Field Size Hardware Path # of LPorts Boot over SAN Advanced Port Parameters Queue Depth Interrupt Control Coalesce Interrupt Control Latency Interrupt Control Delay Operating Parameters Beacon State Link Beacon State MPIO Mode State Indicates whether beaconing is on or off. Indicates whether link beaconing is on or off. Indicates whether multipathing mode is on or off. The number of I/O operations that can be run in parallel on a device. Indicates whether interrupt control is on or off. Sets the interrupt control latency value. Sets the interrupt control delay value. The port number: 0 or 1. The ports world wide name. The HBAs world wide name. The port type ( N_port). The name that is manually assigned to the port. The ports Fibre Channel address. Indicates whether the port is enabled or disabled. Indicates whether the link is online or offline. The configured speed of the port. The speed at which the port is operating. The maximum port speed that is supported on the port. The topology setting. The topology setting at which the port is operating. The maximum number of receive buffers. The frame size, in bytes, of the port. Indicates whether MPIO is enabled or disabled. The number of logical ports. The boot over SAN configuration.
Description
96
Field
Path Time Out Logging Level Persistent Binding 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 Bandwidth allocation High Bandwidth allocation Medium Bandwidth allocation Low
Description
The value between 0 to 60 that specifies the time out session. Note you can only enable or edit the path time out when MPIO is disabled. The port logging level. Values include Log Critical, Log Error, Log Warning, and Log Info. Indicates whether persistent binding is on or off. Indicates whether target rate limiting is on or off. Select the target rate limit from the list. Options include 1 Gbps (the default), 2 Gbps, and 4 Gbps.
Indicates whether FC-SP authentication is on or off. The status of 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 parameters.
Indicates whether QoS is enabled or disabled. Indicates whether QoS is online or offline. The number of receive buffers. QoS priority levels. Values include High, Medium, and Low. Percentage of bandwidth allocation for the High priority level. Percentage of bandwidth allocation for the Medium priority level. Percentage of bandwidth allocation for the Low priority level.
Using the property panel Refer to the following topics for specific procedures using this dialog box.
Configuring the port speed using the GUI Specifying the maximum frame size using the GUI Specifying the MPIO using the GUI Specifying Path Time Out using the GUI Configuring the HCM logging level using the GUI Configuring the queue depth using the GUI
97
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 are supported with the 8 Gbps FC HBAs. The 8 Gbps SFP (which is bundled with the Brocade 815 or 825), it is referred to as SFP+. The 4 Gbps SFP (which is bundled with the Brocade 415 or 425) is simply referred to as SFP. Opening the properties panel 1. Select a port in the device tree. 2. Click the POM tab in the right pane. Fields and components
Field
Temperature(C) Bias Current (mA) Tx Power (uvV) Rx Power (uvV) Voltage
NOTE
Description
The port temperature, measured in Celsius. The low-level DC current (the Bias Current), measured in mA. The transmitted power, measured in uVV. The received power, measured in uVV. The voltage; for example, 1.8V, 3.3V, or 5.0V.
98
Port Statistics dialog box

The Port Statistics dialog box enables you to monitor the performance of the HBA and the traffic between the HBA and the LUNs. You can use the information to isolate and troubleshoot areas that impact application performance. Opening the dialog box Select Monitor > Statistics > Port Statistics from the Host Connectivity Manager. Fields and components
Field
Date WWN Seconds since last reset Invalid TX Words Bad OS Count Encoding Error TX Frames RX Frames TX Words RX Words LIP Count NOS Count Error Frames Dropped Frames Link Failure Count Loss Of Sync Count Loss Of Signal Count Primitive Seq Protocol Err Count Undersized Frame Bad EOF Frame Oversized Frame Invalid CRC Count
Description
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 dialog box was reset. The number of invalid transmitted Fibre Channel words across all protocols and classes. The number of OS events that resulted in a bad response. Indicates whether there is a port encoding error. The number of total transmitted Fibre Channel frames across all protocols and classes. The number of total received Fibre Channel frames across all protocols and classes. The number of total transmitted Fibre Channel words across all protocols and classes. The number of total received Fibre Channel words across all protocols and classes. The number of loop initialization (LIP) events. The number of not operational (link has failed) events. The number of frames that have been received in error. The number of frames that were lost due to a lack of host buffers available. The number of times a link error has occurred. The number of times loss of sync has occurred. The number of times loss of signal has occurred. The number of primitive sequence protocol errors. The number of undersized frame errors. The number of end of frame (EOF) errors. The number of oversized frame errors. The number of frames received with invalid CRC.
99
Field
Invalid Ordered Set Nonframe Coding Err
Description
The number of invalid ordered sets. The number of nonframe coding errors.
100
Port Tests Diagnostics dialog box
Port Tests Diagnostics dialog box

The Port Tests diagnostics dialog box enables you to run tests on the port and to configure parameters such as link speed and frame count. Opening the dialog box 1. Select Configure > Diagnostics from the Host Connectivity Manager. 2. Click Port Tests. Fields and components
Field
Ports Memory Test PCI Loopback Test Data Pattern Test Cycle Loopback Test Subtest ID Link Speed Frame Count Stop on Error Time Test Status Start button Stop button
Description
Select a port from the list. Check to run a Memory test on the port. 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. 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. The test log displays the time the port test was run. The test log displays the type of test that was run. The test log displays the status of the test that was run. Click to run the selected test. Click to stop all pending tests.
Configuring beaconing using the GUI Displaying SFP information using the BCU supportSave collection sources
101
Protocol Tests Diagnostics dialog box
Protocol Tests Diagnostics dialog box

The Protocol Tests Diagnostics dialog box enables you to run test on Fibre Channel components. Opening the dialog box 1. Select Configure > Diagnostics from the Host Connectivity Manager. 2. Click Protocol Tests. Fields and components
Field
Echo Test FC Ping Test FC Traceroute Add Remove Remove All Test Cycle Test Log Stop on Error 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. The test log table displays the time the test was run, type of test run, status of the test, configuration, and the results. 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 the GUI Displaying SFP information using the BCU supportSave collection sources
102
QoS Statistics dialog box
QoS Statistics dialog box

The QoS Statistics dialog box enables you to view statistics related to Quality of Service (QoS). The ability to view QoS statistics is new to version 1.1. Opening the dialog box Select Monitor > Statistics > Port Statistics from the Host Connectivity Manager. Fields and components
Field
Flogi sent Flogi Acc received Flogi Rjt rcvd Flogi retries ELP rcvd ELP accepted ELP rejected ELP dropped QOS RSCN received
Description
The number of Fabric logins sent. The number of Fabric login accepts received. The number of Fabric login rejects received. The number of times a Fabric login was attempted. The number of ELPs (Exchange Link Parameters) sent. The number of ELP accepts sent. The number of ELP rejects sent. The number of ELPs dropped. The number of QoS RSCNs received.
103
Remote Port Properties panel

The Remote Port Properties panel enables you to display the properties that are associated with the remote port. Opening the properties 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. Fields and components
Field
Fibre Channel Properties Port WWN Node WWN Symbolic Name Name FC Address Frame Data Field Size State Supported Classes Device Type Remote Device Information Role Target Rate Limiting Enforced Target Rate Limiting Speed QoS Priority The role of the device (target or initiator) The status of traffic rate limiting, either on or off. 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 Fibre Channel address of the device. The frame size, in bytes, of the device. The status of the device, either online or offline. The supported classes; for example, Class2. The type of the device; for example, Disk or Tape.
Description
1 Gbps, 2 Gbps, and 4 Gbps.
The traffic rate limiting speed for the remote port. Options include The traffic priority (high, medium, or low) for a given source and destination traffic flow, assigned by the Fabric operating system (FOS) By default, all flows are marked as medium. The ID of the QoS traffic flow.
QoS Flow ID Vendor ID Vendor Product ID Product Revision Binding Information Bind Type Bus #
The vendor of the device. The devices identifier. The revision level of the device.
The persistent bind type; for example, FcID. The unique identifying number for each PCI bus, assigned during system initialization.
104
Field
Target ID
Description
The identifier of the target device.
LUN Tab Note: The LUN tab appears only when the remote port is a target. If the remote port is an initiator, only the Properties tab is displayed. LUN # Capacity LUN Name The logical unit number of the remote port. The capacity of the logical unit. The logical unit number. The logical unit name.
105
SFP Properties panel

The SFP Properties panel enables you to display the properties that are associated with a selected small form-factor pluggable (SFP) transceiver. Only Brocade-branded SFPs are supported with the 8 Gbps FC HBAs. The 8 Gbps SFP (which is bundled with the Brocade 815 or 825), is referred to as SFP+. The 4 Gbps SFP (which is bundled with the Brocade 415 or 425) is simply referred to as SFP. Opening the properties panel 1. Select a port in the device tree. 2. Click the SFP tab in the right pane. Fields and components
Field
Port Technology SFP Supported Connector Type Transceiver Media Speed Extended Information Extended ID 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). The length of the fiber optic 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. The name of the supported SFP. The type of port connector; for example, LC or SC. The type of transceiver; for example, XFP or GBIC. The type of media for the transceiver; for example, single mode. The port speed; for example, 1 Gbps, 2 Gbps, 4 Gbps, or 8 Gbps.
NOTE
Description
Length 50u Length 62.5u Length Cu Vendor Name Vendor OUI Vendor Part Revision Wavelength
106
Field
Options BR Max BR Min Serial # Date Code
Description
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.
107

The Syslog Server Configuration dialog box enables you to configure the host connectivity manager (HCM) to send Syslog messages to other computers through port 514. You can configure the HCM agent to forward events to a maximum of three Syslog destinations. Opening the dialog box 1. Select an HBA from the device tree. 2. Select Configure > Syslog from the main menu. Fields and components
Field
Hostname text box IP Address text box Set this IP in all discovered agents in future check box Add button Remove button
Description
Enter the host name of the destination device. Enter the 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
108
Target Statistics dialog box

The Target Statistics dialog box enables you to display statistical information for a selected remote port (RPort). Opening the dialog box Select Monitor > Statistics > Remote port statistics > Target Statistics from the Host Connectivity Manager. OR Right-click a remote port and select Target Statistics. Fields and components
Field
Date WWN Offlines RSCNs 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 LOGO Received HAL uninit Create Events HAL uninit Exception Events HAL Created Online Events
Description
The date and time of the most recent reset. The world wide name of the selected remote port. The remote ports that are offline. The number of Fibre Channels Registered State Change Notification (RSCN) 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 ADISC requests sent. The number of times ADISC requests are accepted. The number of times ADISC requests fail. The number of times ADISC rejects. The number of ADISC requests that are received. The number of times 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. The number of times logouts are received. The number of HAL uninit create events. The number of HAL uninit exception events. The number of HAL created online events.
109
Field
HAL Created Delete Events HAL Created IOC Down HAL Created Exception Events HAL fw Create f/w Responses HAL fw Create Delete Events HAL fw Create Offline Events HAL fw Create IOC Down HAL fw Create Exception Events HAL Online Offline Events HAL Online Delete Events HAL Online IOC down Events HAL Online Exception Events HAL fw Delete f/w Responses HAL fw Delete Delete Events HAL fw Delete IOC down Events HAL fw Delete Exception Events HAL Offline Delete Events HAL Offline Online Events HAL Offline IOC down Events HAL Offline exception events HAL Delete f/w Responses HAL Delete IOC down Events HAL Delete Exception Events HAL Delete Pend f/w Responses HAL Delete Pend IOC downs HAL Delete Pend Exceptions HAL Off-Pending f/w Responses HAL Off-Pending Deletes HAL Off-Pending IOC downs HAL Off-Pending Exceptions HAL IOC Down Offline Events HAL IOC Down Delete Events HAL IOC down Online Events HAL IOC Down Exception Events
Description
The number of HAL created delete events. The number of times HAL created IO controllers were down. The number of HAL created exception events. The number of HAL fw create responses. The number of HAL fw create delete events. The number of HAL fw Create offline events. The number of times HAL fw created IO controllers were down. The number of HAL fw create exception events. The number of HAL online and offline events. The number of HAL online delete events. The number of HAL online IOC down events. The number of HAL online exception events. The number of HAL fw Delete f/w responses. The number of HAL fw Delete Delete events. The number of HAL fw Delete IOC down events. The number of HAL fw Delete Exception events. The number of HAL Offline Delete events. The number of HAL Offline Online events. The number of HAL offline IOC down events. The number of HAL offline exception events. The number of HAL delete f/w responses. The number of HAL Delete IOC down events. The number of HAL delete exception events. The number of HAL delete pend f/w responses. The number of HAL delete pending IOC downs. The number of HAL delete pending exceptions. The number of HAL off-pending f/w responses. The number of HAL off-pending deletes. The number of HAL off-pending IOC downs. The number of HAL off-pending exceptions. The number of HAL IOC down offline events. The number of HAL IOC down delete events. The number of HAL IOC down online events. The number of HAL IOC down exception events.
110
111
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. Opening the dialog box 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. Fields and components
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 the GUI Running a protocol-level test using the GUI
112

The Virtual Port Creation dialog box enables you to create a new virtual port from a physical port. Opening the Virtual Port Creation dialog box 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. Fields and components
Field
Virtual Port WWN text box
Description
Enter a unique world wide name for the virtual port. NOTE: The default node WWN is the physical port node WWN. You must manually change it to a unique WWN for the virtual port.
Use auto-generated check box Generate Again button Virtual Node WWN text box
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. NOTE: The default node WWN is the physical port node WWN. You must manually change it to a unique WWN for the virtual port.
Symbolic Name text box Name text box Description text box
Enter the symbolic name associated with the virtual port. Enter the name for the virtual port. Enter a description for the virtual port.
Virtual Port configuration Creating a Virtual Port Deleting a Virtual Port
113
Virtual Port Deletion dialog box
Virtual Port Deletion dialog box

The Virtual Port Deletion dialog box enables you to delete an existing virtual port. Opening the Virtual Port Deletion dialog box: 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 pop-up warning message displays, asking for confirmation. 3. Click OK to continue. You can also select a base port from the device tree and delete it the same way you delete a virtual port. Fields and components
Field
Deletion check box WWN Node WWN Symbolic Name Delete Selected button Delete All button Cancel button
NOTE
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.
114
Virtual Port Properties panel
Virtual Port Properties panel

The Virtual Port Parameters properties panel enables you to display the properties that are associated with a virtual port. Opening the properties panel Select a virtual port from the device tree and click the Properties tab. Fields and components
Field
Port WWN Node WWN FC Address State Roles Base Port Switch NWWN Symbolic name Switch IP address
Description
The ports world wide name. The adapters world wide name. The Fibre Channel address of the virtual port. Indicates whether the virtual port is online or offline. The role of the virtual port; for example, FCP Initiator. Indicates whether the virtual port is used as the base port. The world wide name of the switch. The switchs symbolic name. The switchs IP address.
115
Virtual Port Statistics dialog box
Virtual Port Statistics dialog box

The Virtual Port Statistics dialog box enables you to view statistical information related to a selected virtual port. Opening the dialog box Select Monitor > Statistics > Virtual Port Statistics from the Host Connectivity Manager. Fields and components
Field
Date WWN FDISCs sent FDISC accepts FDISC retries FDISC req timeouts FDISC rsp errors FDISC bad accepts FDISC rejects FDISC unknown FDISC alloc waits FDISC alloc waits LOGOs sent LOGO accepts LOGO rejects LOGO rsp err LOGO unknown rsps LOGO alloc waits No NPIV support Fabric offlines Fabric onlines Fabric cleanups
Description
The date and time of the most recent reset. The world wide name of the virtual port. 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 times the system accepts Fabric discoveries. The number of times the system rejects Fabric discoveries. The number of unknown Fabric discovery occurrences. The number of delayed 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.
116
Appendix
Brocade Command Line Utility (BCU)
In this appendix
adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fcdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fcpim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pbind. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
121 123 128 130 134 132 135 137 141 142 144 145 149 155
Command Line Help

This appendix provides reference documentation for the Brocade Command Line Utility (BCU) supporting the Brocade Fibre Channel components. BCU runs in two modes:
Direct mode, where you type the command at the command prompt. For example:
bcu port --speed <port_id> <1|2|4|8|auto>
Shell mode, accessed using the bcu shell; for example, bcu> port --speed <port_id>
<1|2|4|8|auto>.
To access the shell mode, type bcu shell. To exit out of shell mode, type exit.
All the commands in this appendix are shown in the direct mode. For example: bcu port --speed <port_id> <1|2|4|8|auto>
117
BCU commands
BCU commands
The following table alphabetically lists the Brocade Command Line Utility (BCU) commands that are available for configuring the devices in a SAN environment that use a Brocade HBA.
Command
Adapter commands bcu adapter - -list - -name - -query - -enable - -disable Authentication commands bcu auth - -show - -policy - --algo - -secret - -stats - -statsclr Boot commands Note: boot commands are not available on Solaris platforms. bcu boot - - upload - - blunZone bcu bios - - enable - - disable - - query Debug commands bcu debug - -portlog - -portlogclear - -portlogctl Fabric commands bcu fabric - - stats - - statsclr FC diagnostic commands bcu fcdiag - -fcping - -fctraceroute - -fcecho - -linkbeacon <port_id> <rpwwn> [-l lpwwn] <port_id> <rpwwn> [-l lpwwn] <port_id> <rpwwn> [-l lpwwn] <port_id> {on | off} <port_id> <port_id> <port_id> <port_id> <port_id> <enable | disable> [-a] [adapter_id] <image_file> -c <BLUN> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#> <port_id> [-s <speed>] [-o <auto | flash | firstlun>] [-p pos] {-b pwwn, lun}* <port_id> <port_id> <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
118
BCU commands
- -scsitest FCP initiator mode commands
<port_id> <rpwwn> [-l lpwwn]
Note: fcpim - -mpiomode is not supported on Solaris platforms. bcu fcpim - -mpiomode - -stats - -statsclr - -query - -qdepth Help commands bcu - -help Lists all available sub-commands <port_id> {on | off [tov]} <port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> <q_depth_value>
bcu <sub_command> - -help IO Controller (IOC) commands bcu ioc - -stats - -query - -statsclr - -enable - -disable - -intr Log commands bcu log - -level
Lists all details about the specific sub_command.
<ioc_id> <ioc_id> <ioc_id> <ioc_id> <ioc_id> <ioc_id> <- -coalesce | c> {on | off} [<Latency> <Delay>]
<port_id> [<critical | error | warning | info>] [-m <fw | ha1 | fcs | drv | aen | all>]
Logical port (lport) commands bcu lport - -list - -query - -stats - -statsclr Diagnostic commands bcu diag - -sfpshow - -tempshow - -beacon - -pciloopback - -loopback - -memtest Port commands (physical port) bcu port - -list - -name - -enable <port_id> [port_name] <port_id> <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> <port_id> [-l <lpwwn>] <port_id> [-l <lpwwn>] <port_id> [-l <lpwwn>]
119
BCU commands
- -disable - -stats - -statsclr - -query - -topology - -speed - -dfsize - - topology Remote port (rport) commands bcu rport - -list - -query - -stats - -statsclr - -osname Target persistent binding
<port_id> <port_id> <port_id> <port_id> <port_id> {auto | p2p} <port_id> <1|2|4|8|auto> <port_id> [dfsize] <port_id> {auto|p2p}
<port_id> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> <rpwwn> [-l <lpwwn>] <port_id> [-l <lpwwn>]
Note: Target persistent binding is available in Windows operating systems only. It is not supported in other operating systems. bcu pbind - -enable - -disable - -list QoS commands bcu qos - - enable - - disable - -query - -stats - -statsclr Target rate limiting commands bcu ratelim - - enable - - disable - -query - -defspeed Virtual port (vport) commands Note: vport commands are not supported on Solaris platforms. bcu vport - -create - -delete - -query - -stats - -statsclr <port_id> <vpwwn> [-n <nwwn>] [-s <sname>] <port_id> <vpwwn> <port_id> <vpwwn> <port_id> <vpwwn> <port_id> <vpwwn> <port_id> <port_id> <port_id> <port_id> [<1|2|4>] <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> <port_id> [<pwwn>]
120
adapter
adapter
Displays and sets adapter configuration. Synopsis
bcu bcu bcu bcu bcu adapter adapter adapter adapter adapter --enable <ad_id> --disable <ad_id> -list -name <ad_id> <adapter-name> -query <ad_id>
Description Operands
Use this command to display and set adapter parameters. When invoked without operands, this command displays the usage. The following operands are supported: - -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. Specifies or sets the name of the adapter. Note: Use an empty string ( ) to clear a previous adapter name. Adapter names are stored persistently. ad_id Specifies the ID of the adapter for which you want to query. Specifies the serial number 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 the user does 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.
- -query ad_id
121
adapter
Example
# bcu adapter --query 1 Example:# bcu adapter --query 1 Adapter Information: model info: Brocade-825 (PROTOTYPE) num ports: 2 max speed: 8 Gbps chip revision: Rev-X hw path: 0000:0d:00 Serial Num: ALX0301D061 name: PCI Information: vendor id: 1657 device id: 0013 ssid: 0014 ssvid: 1657 PCIe Gen: PCIe lanes: Port Information: Port 0: pwwn: nwwn: hwpath: name: Port 1: pwwn: nwwn: hwpath: name: Flash Information: status: fw version: bios version: Gen1 8 (Initial number of lanes = 8)
10:00:00:05:1e:53:0e:4a 20:00:00:05:1e:53:0e:4a 0000:0d:00.0
10:00:00:05:1e:53:0e:4b 20:00:00:05:1e:53:0e:4b 0000:0d:00.1
good FCHBA1.1.0
See Also
port, IOC
122
auth
auth
Enables authentication configuration on a per-port basis and the ability to display authentication status and statistics. Note: port_id could be any of the following:

Synopsis
bcu bcu bcu bcu bcu bcu
<adapter_id> <port_id> <port-pwwn> <port-name> <port-hwpath>

-show <port_id> -policy <port_id> {on|off} -algo <port_id> <md5|sha1|ms|sm> -secret <port_id> secret string --stats <port_id> --statsclr <port_id>
auth auth auth auth auth auth
Configure and display authentication settings and status. The following operands are supported: - -show port_id - -policy Prints the attributes. Specifies the ID of the port for which you want to display information. 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. Sets the authentication algorithm. Specifies the ID of the port for which you want to set the authentication algorithm. Specifies the hash algorithm:
port_id on|off
- -algo port_id
md5|sha1|ms|sm
md5 defines MD5 as the only hash algorithm (the default). sh1 defines SHA-1 as the only hash algorithm. ms defines the hash algorithm priority list of MD5 followed by SHA-1 for
DH-CHAP authentication. sm defines the hash algorithm priority list of SHA-1, followed by MD5 for DH-CHAP authentication.
123
auth
- -secret port_id secret string
Set 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 maximum length of the secret is 63 bytes. The default secret for each interface is its pwwn without the colons; for example, 0102030405060708. 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.
- -stats port_id - -statsclr port_id Example
bcu auth -show 1/0 port 1/0 Port Status Linkdown Auth uninit Hash Type SHA1 Group Type DH-NULL
bcu auth -show 2/1 port 2/1 Auth On Hash Type SHA1, MD5 Group Type DH-NULL
bcu auth -algo 2/1 sha1 Authentication algorithm set bcu auth -algo 2/1 ms Authentication algorithm set bcu auth --secret 5/0 mypasswd Authentication Secret set bcu auth --stats 4/1
See Also
None.
124
bios
bios
Enables the basic input/output system (BIOS) in preparation for Boot Over SAN. You must enable BIOS to support boot over SAN for an HBA port. If disabled, the host system cannot boot from Fibre Channel disk drives. The default setting for the HBA boot BIOS is enabled. BIOS must be enabled on only one adapter port per host in order to boot from SAN. The port_id can be any of the following:
<adapter_id/port_id> <port-pwwn> <port-name> <port-hwpath>
Refer to the Brocade Fibre Channel HBA Installation and Reference Manual for more information about configuring BIOS. Synopsis
bcu bcu {-b bcu bios -query <port_id> bios -enable <port_id> [-s speed] [-o auto|flash|firstlun] [-p pos] pwwn,lun}* bios -disable <port_id>
NOTE
The BIOS is the firmware code that, when first powered on, is a type of boot loader. TThe following operands are supported: - -query port_id - -enable port_id s speed 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 2, 4, 8, or auto for 815 and 826 HBAs and 1, 2, 4, and auto for 415 and 425 HBAs. The default is autonegotiate. Specifies the following options for obtaining boot LUN information.
o auto|flash|firstlun
auto - enables auto-discovery. When enabled, the boot LUN identification is

provided by the fabric.
flash - the HBA obtains the boot LUN information from flash memory.
p pos Values are saved to flash when you configure them and save them through the BIOS Configuration Utility, HCM, and BCU. firstlun - the host boots from the first LUN visible to the HBA 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.
125
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 HBA port using the storage systems management or configuration utility.
- -disable port_id See Also boot
Disables boot over SAN for the specified port, if enabled. Specify the ID of the port for which you want to disable the boot over SAN configuration.
126
boot
boot
Updates the boot code in flash. boot commands are not available on Solaris platforms. The adapter_id can be any of the following:
NOTE

Synopsis Description
<adapter_id> <adapter-sn> <adapter-name> <adapter-hwpath>
bcu boot -upload [-a] [adapter_id] <image_file> bcu boot --blunZone -c <BLUN> -p <port_wwn> -r <rport_wwn> -l <lun_id | lun#>
The following operands are supported: - -upload adapter_id image_file a all - - blunzone c BLUN p port_wwn r rport_wwn l lun_id|lun# Updates the boot code in flash. Specifies the ID of the adapter (HBA). Specifies the name of the firmware image file. Indicates the boot code will be uploaded to all the Brocade HBAs found on the host. Do not specify the adapter_id if you specify -a. Creates the zonecreate command to be run on the switch. Specifies the boot LUN. Specifies the ports world wide name. Specifies the remote ports world wide name. Specifies the LUN as a one-hexadecimal byte (LUN ID) or an 8 hexadecimalbyte (LUN #).
Example
bcu -blunZone -c BLUN -p 10:00:00:05:1e:41:9a:cb -r 50:00:00:05:1e:41:9a:ca -1 09AABBCCDDEEFF00 Please copy the following line and run this command from the switch command line to create the zone. The zone name created below should be included in an effective cfg. 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
127
debug
debug
Gathers all the support information. 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. The following operands are supported: - -portlog Displays the log of FC frames and other main control messages that were sent out and received. If the portlog is disabled, the following message displays as the first line: Refer to bcu debug 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 1/0 Total records present = 256 --------------------------------------------------------------------------Time Module Event Len Log info --------------------------------------------------------------------------5f54f984 FCXP Rx 4 231f141d,001f1400,214cffff,01000000 5f54f986 FCXP Rx 4 231f141d,001f1400,214cffff,02000000 5f54fabc FCXP Rx 4 231f141d,001f21ef,214effff,02000000 5f54fd8a FCXP Rx 4 231f141d,00fffffe,2150099f,02000000 5f551ab9 FCXP Rx 16 031f1400,00fffffc,215209a0,01000000 5f551abf FCXP Tx 56 02fffffc,001f1400,0000ffff,01000000 5f551f4c FCXP Rx 16 031f1400,00fffffc,215409a3,01000000 5f551f4f FCXP Tx 56 02fffffc,001f1400,0000ffff,01000000 5f5523f4 FCXP Rx 16 031f1400,00fffffc,215609a6,01000000 5f5523f8 FCXP Tx 56 02fffffc,001f1400,0000ffff,01000000 5f552879 FCXP Rx 16 031f1400,00fffffc,215809a7,01000000 5f55287b FCXP Tx 56 02fffffc,001f1400,0000ffff,01000000 5f552dc1 FCXP Rx 16 031f1400,00fffffc,205609ad,01000000 5f630e44 UF Rx 40 221f1400,00fffffd,09aeffff,61040008 5f630e59 FCXP Tx 36 23fffffd,001f1400,09aeffff,02000000 5f630e6b FCXP Tx 148 221f141d,001f1400,0000ffff,03000000 5f630f3d FCXP Rx 4 23fffffd,001f1400,09aeffff,01000000 5f637343 FCXP Rx 0 221f141c,001f1400,0000ffff 5f819ba8 FCXP Tx 148 221f141c,001f1400,0000ffff,03000000 5ff0652d FCXP Rx 0 221f141d,001f1400,0000ffff
128
debug
600b1c96 600fb7c0 6029b887 609ca9a9 60badd22 60bbfc3d 6148ee29 614e1847 614e188c 614e18e3 614e18fc 614e1902 614e1905 614e1922 614e1923 614e1a54 614e1d70 614e3bc2 614e3bc8 614e404e 614e4051 614e44d3 614e44d6 614e496d 614e496f 614e4df2 615c1a9b 615c1ab0 615c1abf ......
FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP UF FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP FCXP UF FCXP FCXP
Tx Rx Tx Rx Tx Rx Rx Tx Rx Tx Tx Tx Tx Rx Rx Rx Rx Rx Tx Rx Tx Rx Tx Rx Tx Rx Rx Tx Tx
148 0 148 0 148 0 0 48 48 48 48 36 56 4 4 4 4 16 56 16 56 16 56 16 56 16 40 36 148
221f141d,001f1400,0000ffff,03000000 221f141c,001f1400,0000ffff 221f141c,001f1400,0000ffff,03000000 221f141d,001f1400,0000ffff 221f141d,001f1400,0000ffff,03000000 221f141c,001f1400,0000ffff 221f141d,001f1400,0000ffff 221f1400,001f141e,0000ffff,05000000 221f1400,001f141e,2058ffff,05000000 221f21ef,001f141e,0000ffff,05000000 22fffffe,001f141e,0000ffff,05000000 231f141e,001f1400,2058ffff,02000000 02fffffc,001f1400,0000ffff,01000000 231f141e,001f1400,2058ffff,01000000 231f141e,001f1400,2058ffff,02000000 231f141e,001f21ef,205effff,02000000 231f141e,00fffffe,206e09b2,02000000 031f1400,00fffffc,206c09ba,01000000 02fffffc,001f1400,0000ffff,01000000 031f1400,00fffffc,207209bc,01000000 02fffffc,001f1400,0000ffff,01000000 031f1400,00fffffc,207009bf,01000000 02fffffc,001f1400,0000ffff,01000000 031f1400,00fffffc,207609c0,01000000 02fffffc,001f1400,0000ffff,01000000 031f1400,00fffffc,20cc09c3,01000000 221f1400,00fffffd,09c6ffff,61040008 23fffffd,001f1400,09c6ffff,02000000 221f141e,001f1400,0000ffff,03000000
bcu debug --portlogclear 1/0 port log is successfully cleared bcu debug --portlogctl 1/0 enable portlog enabled bcu debug --portlogctl 1/0 disable portlog disabled
See Also
None.
129
diag
diag
Lists the non-destructive group of diagnostic commands. You must disable the port prior to executing the loopback test. You must disable the adapter prior to executing the memtest. Synopsis
bcu bcu bcu bcu [-p bcu bcu diag --sfpshow <port_id> diag --tempshow <ad_id> diag --pciloopback <port_id> [-p <pattern>] [-c <frame_count>] diag --loopback <port_id> [-t <loopback-type>] [-s <speed>] [-c <frame_count>] <pattern>] diag --memtest <ad_id> diag --beacon <port_id> <on | off> [<duration>]
NOTE
Displays the group of diagnostic commands that are non-destructive and indicates when the adapter is running at a normal operation state. The following operands are supported: - -sfpshow Monitors the attributes of the SFP. Note: A notification occurs for any parameter that is not within the configured power, temperature, voltage, and current policy. Specifies the ID of the port on which you want to monitor the SFP attributes. Blinks the appropriate port LED for physical identification. Specifies the ID of the port for which you want to beacon. Specifies if beaconing is to be turned on or off. Specifies the length of time between blinks. 0, meaning infinite beaconing, is the default. Runs the port loopback test. You must disable the port prior to executing the loopback test. Specifies the ID of the port on which you want to run a loopback test. Specifies the length of time between blinks. Specifies the loopback speed. Possible values are 1, 2, 4, and 8. Specifies the frame count. Specifies the pattern (must be one hex word). Tests the adapters memory blocks. You must disable the adapter prior to executing the memtest. Specifies the ID of the port on which you want to run a memory test.
port_id - -beacon port_id on | off duration - -loopback port_id duration -s speed -c frame count -p pattern - -memtest ad_id
-t loopback-type Specifies the loopback type. Possible values are int, serdes, and ext.
130
diag
- -pciloopback port_id p pattern -c frame count - -tempshow ad_id Example
Sends a health check message from the host to firmware through message queues memory mapped over the PCI. Specifies the ID of the port for which you want to send a health check message. Displays the data pattern. Specifies the frame count. Reads the adapters temperature sensor registers. Specifies the ID of the adapter for which you want to display temperature sensor registers.
bcu diag --sfpshow 1/0 Identifier: 3 SFP Connector: 7 LC Transceiver: 540c404000000000 200,400,800_MB/s M5,M6,SN,S, 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: 2 (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: 5203 (units nm) Options: 003a Rx_LOS TX_FAULT TX_DISABLE RATE_SELECT BR Max: 0 BR Min: 0 Serial No: UAF10738000010P Date Code: 070916 Temperature: 34.691406 Centigrade Current: 6.628000 mAmps Voltage: 3.414000 V RX Power: 0.340000 mW Tx Power: 0.464000 mW bcu diag --tempshow 1 temperature: 38.520200 C
See Also
fcdiag
131
fcdiag
fcdiag
Runs diagnostic tests on Fibre Channel components. Note: port_id could be any of the following:

Synopsis
bcu bcu bcu bcu bcu
<adapter_id> <port_id> <port-pwwn> <port-name> <port-hwpath>

fcdiag fcdiag fcdiag fcdiag fcdiag -fcping <port_id> <rpwwn> [-l <lpwwn>] --fctraceroute <port_id> <rpwwn> [-l <lpwwn>] --fcecho <port_id> <rpwwn> [-l <lpwwn>] --linkbeacon <port_id> {on | off} --scsitest <port_id> <rpwwn> [-l <lpwwn>]
Operands
The following operands are supported. - -fcping port_id rpwwn lpwwn - -fctraceroute port_id rpwwn lpwwn - -fcecho port_id rpwwn lpwwn - -linkbeacon port_id Specifies the ID of the port for which you want to run the fcecho command. Specifies the remote port world wide name. Specifies the logical port world wide name. This is an optional argument. Blinks (toggles) the link beacon. Specifies the ID of the port for which you want to run a linkbeacon test. Enables link beaconing by turning it on or off. If it is turned on, you can specify duration. Determines the basic connectivity between two Fibre Channel network points and monitors and measures network latency. Specifies the ID of the port you want to ping. Specifies the remote port world wide name you want to ping. Specifies the logical port world wide name. This is an optional argument. 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.
mode {on|off} | t duration
132
fcdiag
- -scsitest port_id rpwwn lpwwn See Also diag
Tests the SCSI components. Specifies the ID of the port for which you want to run a linkbeacon test. Specifies the remote port world wide name. Specifies the logical port world wide name. This is an optional argument.
133
fabric
fabric
Prints and resets fabric statistics. Synopsis Operands
bcu fabric -stats <port_id> bcu fabric --statsclr <port_id>
The following operands are supported: - -stats port_id - -statsclr port_id 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.
Example
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.
134
fcpim
fcpim
Enables or disables FCP initiator mode. bcu fcpim - -mpiomode is not available on the Solaris operating system. Synopsis
bcu bcu bcu bcu bcu fcpim fcpim fcpim fcpim fcpim -query <port_id> <rpwwn [-l <lpwwn>] --stats <port_id> <rpwwn [-l <lpwwn>] --statsclear <port_id> <rpwwn [-l <lpwwn>] --mpiomode <port_id> {on|off [tov]} --qdepth <port_id> <q_depth_value>
NOTE
Enables or disables fast failover of the Fibre Channel Port (FCP) initiator mode I/O and displays or clears statistics. The following operands are supported: - -query port_id rpwwn lpwwn - -stats port_id rpwwn lpwwn - -statsclr port_id rpwwn lpwwn - -mpiomode port_id on|off tov Queries the FCPIM attributes. Specifies the ID of the port for which you want to enable or disable the FCP initiator mode. Specifies the remote port world wide name. Specifies the logical port world wide name. This is an optional argument. Displays statistics related to the Fibre Channel port. Specifies the ID of the port for which you want to display information. Specifies the remote port world wide name. Specifies the logical port world wide name. This is an optional argument. Displays statistics related to the Fibre Channel port. Specifies the ID of the port for which you want to display information. Specifies the remote port world wide name. Specifies the logical port world wide name. This is an optional argument. Sets the mpiomode to on or off. If mpiomode is off, you can specify an optional path time out value (TOV). Specifies the ID of the port for which you want to enable or disable the FCP initiator mode. Specifies whether MPIO mode is enabled or disabled and optional path time out value (TOV) in seconds (1 to 60). A value of 0 triggers the default time out value, which is 30. Specifies the ID of the port for which you want to enable or disable the FCP initiator mode.
- -qdepth port_id
q_depth_value Specifies the queue depth value.
135
fcpim
Example
bcu fcpim --stats 1/0 50:00:1f:e1:50:0d:da:a9 rport onlines: 4 rport offlines: 3 PRLI sent: 4 PRLI Accepts: 4 PRLI error responses: 0 PRLI responses parse err: 0 fcxp alloc waits: 0 Second level err recovery: 0 Num times in initiator mode: 0 HAL fcpim statistics online events: offline events: create events: delete events: create completions: delete completions: SLER events: IOC down events: IO cleanup completions: task management commands: TM firmware responses: TM successes: TM failures: TM related IO cleanups: TM firmware queue resumed: TM affected by IOC down events: TM affected by ITN offline: TM offline cleanup completions: IO requests: IO completions:
4 3 1 0 4 2 0 1 3 0 0 0 0 0 0 0 0 0 456026 456026
See Also
IOC vport
136
IOC
IOC
IO Controller (IOC) refers to the combination of port and the firmware controlling it. Synopsis
bcu bcu bcu bcu bcu bcu ioc ioc ioc ioc ioc ioc -stats <ioc_id> -statsclr <ioc_id> -enable <ioc_id> -disable <ioc_id> --query <ioc_id> --intr <ioc_id> <--coalesce|-c> {on | off} [<Latency> <Delay>]
Description
Displays the IOC statistics and enables you to clear the statistics and enable or disable the IOC.
CAUTION:
Disabling the IOC is a destructive operation.
Operands
The following operands are supported: - -stats ioc_id - -statsclr ioc_id - -enable ioc_id - -disable ioc_id - -query ioc_id - -intr Displays the port level statistics. Specifies the ID of the port for which you want to display information. Clears the port level statistics. Specifies the ID of the port for which you want to clear statistical information. 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. 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. Queries IOC information. Specifies the ID of the port for which you want to display information. Sets the ports interrupt attributes. Note: The operation fails if the input parameters are out of the supported range. ioc_id coalesce|c Latency Specifies the ID of the port for which you want to set the ports interrupt attributes. Displays the coalescing flag values. Supported values are on or off. Sets the latency monitor time out values in microseconds, if coalesce is set to on. Latency time out values supported are 0-225 microseconds. Setting the latency time out value to 0 disables the latency monitor time out interrupt. Sets the delay time out values in microseconds, if coalesce is set to on. Delay time out values supported are 0-1125 microseconds. Setting the delay time out value to 0 disables the latency monitor time out interrupt.
Delay
137
IOC
Example
# bcu ioc --stats 1/0 IOC driver statistics: mailbox interrupts: start events: stop events: enable events: disable events: heartbeat failures: firmware boots: stats timeouts: IOC firmware statistics: heartbeat count: config requests: enable requests: disable requests: stats requests: clear stats reqs: unknown requests: intr coalesce reqs: Firmware IO statistics: IO aborts: implicit IO aborts: IO timeouts: ABTS failures: EDTOV timer events: RECTOV timer events: seq level rec failures: unexpected frames: unexp fr - good rsp: unexp fr - bad rsp: sequence count errors: IO underruns: IO underrun errors: IO overruns: IO overrun errors: data out of range: IO protocol errors: target IO aborts: Firmware port FPG statistics: FPG interrupts: FPG level 0 intrs: FPG 0 cause intrs: FPG intr other: FPG intr other ignored: FPG signal lost: FPG signal regained: FPG sync lost: FPG sync timeout: FPG sync regained: FPG div2 overflow: FPG div2 underflow: FPG efifo overflow: FPG efifo underflow: FPG IDLE primitives: FPG LRR primitives: FPG LR primitives: FPG OLS primitives: FPG NOS primitives: FPG LIP primitives: FPG ARBF0 primitives:
5 0 0 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 24 0 24 0 24 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
138
IOC
FPG MRK primitives: 0 FPG unknown primitives: 0 Firmware port PHYSM statistics: module inserts: 0 module extracts: 0 module invalid events: 0 module validation ignored: 0 laser faults: 0 signal loss count: 0 sync loss count: 0 Firmware port SNSM statistics: HWSM success: 0 HWSM failures: 0 HWSM timeouts: 0 SWSM success: 2 SWSM timeouts: 0 Firmware port LKSM statistics: HWSM success: 0 HWSM failures: 0 HWSM timeouts: 0 SWSM success: 0 SWSM failures: 0 SWSM timeouts: 0 busy buffer failures: 0 bufwait state entries: 0 link failures: 0 prim seq protocol errs: 0 LR tx started: 0 LRR tx started: 0 OLS tx started: 0 NOS tx started: 0
bcu ioc --statsclr 1/0 Successfully reset the ioc level stats bcu ioc --enable 1/0 port id 1/0 enabled bcu ioc --enable 1/0 Error: IOC is already enabled bcu ioc --disable 1/0 port id 1/0 disabled bcu ioc --disable 1/0 Error: IOC is already disabled bcu ioc --intr 1/0 --coalesce off Interrupt coalescing has been turned off bcu ioc --intr 1/0 --coalesce on Interrupt coalescing has been turned on bcu ioc --intr 1/0 --coalesce on 10 50 The intr settings have been configured with value(s) Coalesce; on Delay: 50 (micro-seconds) Latency: 10 (micro-seconds)
139
IOC
bcu ioc --intr 1/0 --coalesce on 256 1125 Error: command --intr syntax is incorrect or one of the parameters is incorrect
See Also
adapter lport
140
log
log
Sets the log level for each module. If no log level is specified, the current level is used. Synopsis
bcu log -level <port_id> [<Critical|Error|Warning|Info>] [-m <fw|ha1|fcs|drv|aen|all>]
Description
The number of messages logged by the host depends on the predetermined logging level. Although the HBA might generate many messages, only certain types of messages are logged based on the specified logging level. The following operand is supported: - -level port_id Specifies the number of messages logged by the host 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. fw | ha1 | fcs | drv | aen | all Specifies the mode.
Operands
Critical | Error | Warning | Info
See Also
None.
141
lport
lport
Lists the logical port (lport) commands. A logical port is a port that is logged into a fabric. Synopsis
bcu bcu bcu bcu lport lport lport lport -list <port_id> -query <port_id> [-l <lpwwn>] -stats <port_id> [-l <lpwwn>] --statsclr <port_id> [-l <lpwwn>]
Lists all the logical ports (lports) under a given port_id. The following operands are supported: - -list port_id - -query port_id lpwwn - -stats port_id lpwwn - -statsclr port_id 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.
Example
bcu lport --list 1/0 Port ID: 1/0 Port Name: Port PWWN: 10:00:00:05:1e:53:0e:4a Port NWWN: 20:00:00:05:1e:53:0e:4a HW Path: 0000:0d:00.0 Num LPORTs: 1
PT
BP
FC Addr
062100
LPORT PWWN
10:00:00:05:1e:53:0e:4a
LPORT NWWN
20:00:00:05:1e:53:0e:4a
FC4 Roles
IM
142
lport
# bcu lport --query 1/0 Port FC Addr: 062100 Port Type: Base Port (State: Linkup) Port PWWN: 10:00:00:05:1e:53:0e:4a Port NWWN: 20:00:00:05:1e:53:0e:4a Symbolic name: Brocade-825 | 1.0.0 | hba-rh5x-2950-iu23 | Red Hat Enterprise Linux Server release 5 (Tikanga) | Role: FCP Initiator Switch NWWN: 10:00:00:05:1e:41:22:40 Switch IP Addr: 10.32.116.71 # bcu lport --stats 1/0 NS PLOGI sent: NS PLOGI accepts: NS PLOGI rsp errors: NS PLOGI accept errors: NS PLOGI rejects: NS PLOGI unknown rsp: NS PLOGI alloc wait: NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS RSPN_ID RSPN_ID RSPN_ID RSPN_ID RSPN_ID RFT_ID RFT_ID RFT_ID RFT_ID RFT_ID GID_FT GID_FT GID_FT GID_FT GID_FT GID_FT sent: accepts: rsp errors: rejects: alloc wait: sent: accepts: rsp errors: rejects: alloc wait: sent: accepts: rsp errors: rejects: unknown rsp: alloc wait:
2 2 0 0 0 0 0 2 2 0 0 0 2 2 0 0 0 2 2 0 0 0 0 0 0
NS timeouts: NS retries:
RSCN received : 0 port_id RSCN received : 0 # bcu lport --statsclr 1/0 Successfully reset the lport level stats
See Also
None.
143
pbind
pbind
Lists, enables, and disables target persistent binding. pbind is only supported on the Windows platform. Synopsis
bcu pbind -enable <port_id> bcu pbind --disable <port_id> bcu pbind --list <port_id> <pwwn>
NOTE
Enables target port world wide name binding to a persistent target ID for the OS stack. The following operands are supported: - -enable port_id - -disable port_id - -list port_id pwwn Enables target persistent binding. Specifies the ID of the port on which you want to enable persistent binding. Disables target persistent binding. Specifies the ID of the port for which you want to disable persistent binding. Queries the list of mappings from the persistent binding module. Specifies the ID of the port for which you want to display information. Specifies the world wide name of the port for which you want to display information.
See Also
None.
144
port
port
Lists the port commands (the physical ports on the HBA). Note: port_id could be any of the following:

Synopsis
bcu bcu bcu bcu bcu bcu bcu bcu bcu bcu
<adapter_id/port_id> <port-pwwn> <port-name> <port-hwpath>

port port port port port port port port port port -list -name <port_id> [port_name] -enable <port_id> -disable <port_id> -stats <port_id> --statsclr <port_id> --query <port_id> -speed <port_id> <1|2|4|8|auto> --dfsize <port_id> [df_size] --topology <port_id> <auto|p2p>
Operands
The following operands are supported: - -list - -name port_id port_name Lists all the physical ports along with their basic attributes. Queries or set 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 characters, must begin with an alphabetic letter, can consist of letters, digits, hyphens, and underscore characters, and no spaces. 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. Note: For scripting, use the -f option to force the operation. port_id - -stats port_id - -statsclr port_id 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.
- -enable port_id - -disable
145
port
- -query port_id - -topology
Queries and displays port-related information for a port. Specifies the ID of the port for which you want to display information. Displays or sets the port topology. The port topology can be changed dynamically (when the port is enabled). If the port is disabled, the new topology setting takes effect when the port is re-enabled. Specify the ID of the port for which you want to display topology information. The topology setting. Supported values are:
port_id val
auto - auto-discovers the topology. p2p - point-to-point mode.

- -speed Queries or sets the port speed. The port speed can be changed dynamically (when the port is enabled). If the port is disabled, the new port speed setting takes effect when the port is re-enabled. Note: Values 1, 2, 4, and 8 mean a single-port speed setting. The speed value is a bit mask that specify speeds to be considered for auto-negotiation. 1Gbps speed is not valid for an 8 Gbps HBA; 8Gbps speed is not valid for a 4 Gbps HBA. port_id speed Specifies the ID of the port for which you want to set the port speed. Specifies the port speed. Supported values are:
auto - auto-negotiates the speed. 1 - 15 - bit mask of speeds 1/2/4/8 Gbps.

- -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. port_id df_size 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. If set to auto, the driver default value displays. dfsize values include 512, 1024, 2048, and 2112. Queries or sets the port topology. Specifies the ID of the port for which you want to display or set the topology. Specifies the topology type as either auto or point-to-point. Note: The topology setting will take effect after the port - - disable and port - enable commands are executed. Example
bcu port --list
- -topology port_id auto|p2p
Port #
1/0 1/1 2/0 2/1 3/0
FC Addr
010000 -- 010100 ---
PWWN
10:00:00:04:1e:53:04:f0 10:00:00:05:1e:53:04:f1 10:00:00:05:1e:0a:41:98 10:00:00:05:1e:0a:41:99 10:00:00:05:1e:53:0b:ad
Sfp
sw -sw -sw
State
Linkup Linkdown Linkup Linkdown Linkdown
Spd
4G --8G -----
Type
N -N ---
146
port
bcu port --name 1/0 emc_fab3_ad5_p0 Port 1/0s name set to emc_fab3_ad5_p0 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 1/0 tx_frames: tx_words: rx_frames: rx_words: lip_count: nos_count: link_failures: loss_of_syncs: loss_of_signals: primseq_errs: invalid ordered set: nonframe coding err: invalid_crcs frames: undersized frames: oversized frames: bad EOF frames: error_frames: dropped_frames:
101606 4833130 96183 1211891 0 0 0 0 0 0 0 2 0 0 0 0 0 0
bcu port --statsclr 1/0 Successfully reset the port level stats bcu port --speed 1/0 auto Setting will be enforced after port --disable and --enable bcu port --speed 1/0 Current port speed is: 8G Configured port speed is: Auto bcu port --dfsize 1/1 2112 Setting will be enforced after port --disable and --enable bcu port --dfsize 1/1 auto Setting will be enforced after port --disable and --enable
See Also
adapter IOC
147
qos
qos
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. 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. Synopsis
bcu bcu bcu bcu bcu qos qos qos qos qos --query <port_id> -enable <port_id> --disable <port_id> -stats <port_id> --statsclr <port_id>
Enables or disables Quality of Service (QoS) support on the HBA side. The following operands are supported: - -enable port_id - -disable port_id - -query port_id - -stats port_id - -statsclr port_id Enables QoS on the HBA. Specifies the ID of the port you want to enable. Disables QoS on the HBA. Specifies the ID of the port you want to disable. Displays QoS details and details of the parameters exchanged during QoS negotiation. Specifies the ID of the port for which you want to query port information. Displays the statistics that are associated with the port. Specifies the ID of the port for which you want to display statistical information. Clears the statistics that are associated with the port. Specifies the ID of the port for which you want to clear statistical information.
Example
#bcu qos --query 1/0 QOS State: Online Total bb_credits: 34
148
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 bcu bcu bcu bcu rport rport rport rport rport -list <port_id> [-l <lpwwn>] -query <port_id> <rpwwn> [-l <lpwwn>] -stats <port_id> <rpwwn> [-l <lpwwn>] --statsclr <port_id> <rpwwn> [-l <lpwwn>] --osname <port_id> [-l<lpwwn>]
Operands
The following operands are supported: - -list port_id lpwwn - -osname port_id lpwwn - -query port_id rpwwn lpwwn Lists all remote parts 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. Displays the operating system. Specifies the ID of the port to the operating system. Displays 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 lpwwn - -statsclr port_id rpwwn 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. Note: If the -l lpwwn argument is not specified, the base port is used.
149
rport
- -osname port_id lpwwn Examples
Displays the device name of each remote LUN. Specifies the ID of the port to view the device names. Displays the logical port world wide name for which you want to view the device names. This is an optional argument.
bcu rport --list 1/0 Num RPORTs = 2 --------------------------------------------------------------------------FC Addr Remote Port PWWN QOS-P/F SPD State F df_sz --------------------------------------------------------------------------010600 50:06:0e:80:10:03:4a:96 U/0 4G online T 2048 011900 50:08:05:f3:00:01:16:21 U/0 2G online T 2048 bcu rport --list 1/0 Num RPORTs = 9 --------------------------------------------------------------------------FC Addr Remote Port PWWN QOS-P/F SPD State F df_sz --------------------------------------------------------------------------010001 2d:27:00:11:0d:01:00:01 U/0 4G online T 2048 010006 2d:27:00:11:0d:01:00:06 U/0 4G online T 2048 010002 2d:27:00:11:0d:01:00:02 U/0 4G online T 2048 010007 2d:27:00:11:0d:01:00:07 U/0 2G* online T 2048 010003 2d:27:00:11:0d:01:00:03 U/0 2G* online T 2048 010008 2d:27:00:11:0d:01:00:08 U/0 1G* online T 2048 010004 2d:27:00:11:0d:01:00:04 U/0 4G online T 2048 010005 2d:27:00:11:0d:01:00:05 U/0 4G online T 2048 010201 29:fd:00:11:0d:03:00:01 U/0 4G online T 2048 -------------------------------------------------------------------------Note : The * next to speed indicates that the TRL is enforced. # bcu rport --list 1/0 Num RPORTs = 12 --------------------------------------------------------------------------FC Addr Remote Port PWWN QOS-P/F SPD State F df_sz --------------------------------------------------------------------------010001 2d:27:00:11:0d:01:00:01 H/1 8G online T 2048 010006 2d:27:00:11:0d:01:00:06 H/1 8G online T 2048 010002 2d:27:00:11:0d:01:00:02 H/2 8G online T 2048 010007 2d:27:00:11:0d:01:00:07 H/2 8G online T 2048 010201 29:fd:00:11:0d:03:00:01 L/1 8G online T 2048 010203 29:fd:00:11:0d:03:00:03 L/1 8G online T 2048 010205 29:fd:00:11:0d:03:00:05 L/1 8G online T 2048 010207 29:fd:00:11:0d:03:00:07 L/1 8G online T 2048 010103 2d:26:00:11:0d:02:00:03 M/1 8G online T 2048 010107 2d:26:00:11:0d:02:00:07 M/2 8G online T 2048 010104 2d:26:00:11:0d:02:00:04 M/3 8G online T 2048 010108 2d:26:00:11:0d:02:00:08 M/4 8G online T 2048 ---------------------------------------------------------------------------
150
rport
bcu rport --stats 1/0 offlines: 0 onlines: 1 RSCN : 0 PLOGI sent: 1 PLOGI accepts : 1 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
2f:ff:00:06:2b:0d:31:e5
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:
1 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
151
rport
IOC down: exceptions:
bcu rport -- statsclr 1/0 2f:ff:00:06:2b:0d:31:e5 Successfully reset the rport level stats
See Also
None.
152
ratelim
ratelim
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. Target rate limiting is new to version 1.1. 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. Synopsis
bcu bcu bcu bcu ratelim ratelim ratelim ratelim -enable <port_id> --disable <port_id> --query <port_id> --defspeed <port_id> [<1|2|4>]
NOTE
Enables or disables target rate limiting support on the HBA side. The following operands are supported: - -enable port_id - -disable port_id - -query port_id - -defspeed port_id Enables target rate limiting. Specifies the ID of the port you want to enable. Disables target rate limiting on the HBA. Specifies the ID of the port you want to disable. Queries information about the port. This provides the ports status and information. Specifies the ID of the port for which you want to query port information. Displays or sets the default target rate limiting speed. Specifies the ID of the port for which you want to view or set the default target rate limiting. Options are 1 Gbps, 2 Gbps, and 4 Gbps.
153
supportSave
supportSave
Gathers all the support information. Unless you define a directory for the supportSave information, all supportSave files are saved in the directory from where the command is run. Synopsis
bfa_supportsave [destination_directory]
NOTE
The bfa_supportshow command outputs much of the same information as the bfa_supportsave command, but to the command line screen rather than the output file. Description Operands Captures all the support information needed to diagnose suspected system issues. The following operand is supported: - -destination_directory Saves the collected supportsave information into an output file. Example
# bfa_supportsave ====================== Fetching Driver trace for port 1/0 ====================== Done. ====================== Fetching Driver trace for port 1/1 ====================== Done. ===================== Fetching Firmware trace for port 1/0 ===================== Done. ===================== Fetching Firmware trace for port 1/1 ===================== Done. ========================= Fetching supportshow details ========================= Done. ============================== Creating a tar ball ============================= Done. ======= Output file ./bfa_ss_out_2008-06-03_04_53_10/bfa_supportsave.tgz =======
NOTE
154
vport
vport
Lists the commands that apply to a virtual port. Note: vport commands are not supported on Solaris platforms. Synopsis
bcu bcu bcu bcu bcu vport vport vport vport vport -create <port_id> <vpwwn> [-n <nwwn>] [-s <sname>] --delete <port_id> <vpwwn> --query <port_id> <vpwwn> --stats <port_id> <vpwwn> --statsclr <port_id> <vpwwn>
vport commands enable you to create and delete vports and display statistics about them. The following operands are supported: - -create Adds a new vport in the base fabric. Primary identification for a vport is the port wwn. A node wwn can optionally be assigned to a vport. One or more FC-4 protocols must be enabled for a vport. Specifies the ID of the port for which you want to add a new vport. 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 vport. 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 vport. 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 vport. Deletes the virtual port by its world wide name. The V_Port WWN is a required argument. Queries information about the vport. This provides the vports status and information associated with FC-4s. If no port WWN is specified, the information provided is for the base vport. Specifies the ID of the port for which you want to query vport 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 vport. If you do not specify the ports world wide name, the statistics listed are for the base vport. 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.
port_id vpwwn n nwwn
s sname - -delete port_id vpwwn - -query
port_id vpwwn - -stats port_id vpwwn
155
vport
- -statsclr port_id vpwwn Example
Clears the statistics that are associated with the vport. If you do not specify the ports world wide name, the statistics listed are for the base vport. 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 --stats 1/0 28:18:00:0c:29:00:02:69 FDISCs sent: 7 FDISC accepts: 7 FDISC retries: 0 FDISC req timeouts: 0 FDISC rsp errors: 0 FDISC bad accepts: 0 FDISC rejects: 0 FDISC unknown rsps: 0 FDISC alloc waits: 0 LOGOs sent: LOGO accepts: LOGO rejects: LOGO rsp errors: LOGO unknown rsps: LOGO alloc waits: No NPIV support: Fabric offlines: Fabric onlines: Fabric cleanups: 0 0 0 0 0 0 0 6 6 0
See Also
fcpim IOC
156
Appendix
FDMI FC-CTs
HBA Driver and FDMI

The HBA driver participates in the FC-GS5-compliant Fabric Device Management Interface (FDMI) when connected to a fabric. The HBA is expected to register and deregister its information in the fabric; based on this information, the fabrics HBA management server will service the HBA information query requests.
Code (hex)
0200 0210 0211
Mnemonic
RHBA RPRT RPA
Description
Register HBA Register Port Register Port Attributes
Attributes in request CT_IU

HBA Identifier, Registered Port List, HBA Attribute Block HBA Identifier, Port_Name, Port Attribute Block Port_Name, Port Attribute Block
157
HBA Driver and FDMI
158
Appendix
Standards Compliance
Standards Compliance Publications

Ref #
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Publication Number
INCITS 352 NCITS TR-25:1999 ANSI X3.230:1994 ANSI X3.297:1997 ANSI X3.303:1998 ANSI/INCITS 373:2003 INCITS TR-30-2002 ANSI X3.272:1996 NCITS 332: 1999 ANSI INCITS 350-2003 ANSI INCITS 366-2003 NCITS TR-19:1998 NCITS TR-20:1998 RFC-4338 (this obsoletes RFC-2625) PCI-SIG Document PCI-SIG Document PCI-SIG Document PCI-SIG Document
Description
Fibre Channel Physical Interfaces (FC-PI) Fibre Channel Methodologies for Jitter Specification (FC-MJS) Fibre Channel Physical and Signaling Interfaces (FC-PH) Fibre Channel Physical and Signaling Interface - 2 (FC-PH-2) Fibre Channel Physical and Signaling Interface - 3 (FC-PH-3) Fibre Channel Framing and Signaling Interface (FC-FS) Fibre Channel - Methodologies for Interconnects (FC-MI) Fibre Channel Arbitrated Loop (FC-AL) Fibre Channel Arbitrated Loop (FC-AL-2) Fibre Channel Protocol for SCSI, Second Version (FCP-2) SCSI Architecture Model - 2 Private loop SCSI direct attach (FC-PLDA). Technical Report Fabric Loop Attachment (FC-FLA) Technical report. Internet Protocol and ARP over Fibre Channel, June 1999 (IP over FC profile) PCI Local Bus Specification Rev 2.3, March 29, 2002 PCI Local Bus Hot-Plug Specification, Rev 1.0, october 6, 1997. Adapter Card Requirements section only. PCI-X Addendum to the PCI Local Bus Specification. Rev 1.0a. July 24, 2000 PCI-Express Card Electromechanical Specification, Rev 1.0a. April 15, 2003 PCI-Express Base Specification, Rev 1.0a, April 15, 2003
Revision
Rev 13 Rev 10 Rev 4.3 Rev 7.4 Rev 9.4 Rev 1.9 Rev 1.92 Rev 4.5 Rev 7.0 Rev 8.0 Rev 24 Rev 2.1 Rev 2.7 January 206 N/A N/A N/A Rev 1.1 Dated 3/28/2005 Rev 1.1 Dated 3/28/2005 ECN to Rev 1.0a dated 8/12/2003
19
PCI-SIG Document
20
PCI-SIG Document
PCI-Express - Root Complex Discovery Topology, August 12, 2003
159
Standards Compliance Publications
21 22
PCI-SIG Document PCI-SIG Document
PCI-Express Reset Limit Adjustment, July 14, 2003 Errata for PCI-Express Base Specification, Rev 1.0a, October 7, 2003
ECN dated 7/14/2003 Rev1.0a dated 10/7/2003
160
Appendix
SAN-based Virtual Machine Migration using SCVMM
This section discusses preparing and deploying a virtual machine on a LUN that is connected to a virtual HBA port in a Microsoft SCVMM 2008 environment.
System Center Virtual Machine Manager 2008

The System Center Virtual Machine Manager (SCVMM) provides centralized administration of a virtual server and enables increased physical server utilization and rapid provisioning of new virtual machines. Some of the benefits of the SCVMM 2008 are as follows:
Support for VMs running on a Windows Server 2008

SCVMM 2008 fully utilizes the foundational features and services of the Windows Server 2008 and the Microsoft Hyper-V Server. VMM 2008 supports all Hyper-V functionality while providing Virtual Machine Manager (VMM)-specific functions such as the Intelligent Placement, the Self-Service Portal, and the Integrated Library.
Multi-vendor virtualization support

Virtualization support for virtual machines running on Microsoft Virtual Server and VMWare ESX.
Performance and Resource Optimization (PRO)

PRO is a new feature of VMM that can dynamically respond to failure scenarios or poorly-configured components that are identified in hardware, operating systems, or applications.
Host Cluster support for High Availability (HA) virtual machines

VMM 2008 is fully cluster-aware, meaning it can detect and manage Hyper-V host clusters as a single unit.
Windows PowerShell integration

VMM is written completely around Windows PowerShell, an administrator-focused command shell and scripting language with more than 170 standard command-line tools and consistent syntax and utilities. With view code buttons throughout the UI, administrators can easily see and modify PowerShell scripts for future use. To learn more about Virtual Machine Manager, refer to the following white paper from Microsoft: http://download.microsoft.com/download/0/8/9/089003c8-5b65-4e5b-bdf6-4b2e02968ad1/S CVMM2008_White_Paper_final_090208PD.pdf
161
N_Port ID Virtualization (NPIV)
Supported virtualization platforms

Virtual Machine Manager (VMM) is supported on the following platforms:
Microsoft Windows Server 2008 Microsoft Hyper-V Server Microsoft Virtual Server 2005 R2 SP1 VMWare ESX with Virtual Center

The NPIV feature allows users to virtualize and share a single physical N_Port. Brocade Fibre Channel HBAs support the NPIV feature and the Brocade Host Connectivity Manager (HCM) provides support for creating, deleting, and managing NPIV ports.
NPIV benefits in a virtualization environment

Brocade NPIV support extends the virtualization capabilities provided by Microsoft SCVMM. Storage administrators can create virtual HBA ports and configure them to access LUNs in multiple zones. Virtual machines created on these LUNs can be easily migrated to other hosts without having to reconfigure any switch zoning or LUN masking settings at the storage array.
Preparation to deploy NPIV in a virtualization environment

The following are prerequisites for successfully deploying the NPIV feature on Brocade HBAs in a System Center Virtual Machine Manager (SCVMM) environment.
Hardware requirements
Brocade Fibre Channel HBA NPIV-capable Fibre Channel switch Server hardware x64 architecture-based server with 2.8 GHz or faster processor clock speed and with
hardware-assisted virtualization support enabled in the BIOS
2 GB of RAM recommended 200 GB of available hard-disk space DVD-ROM drive
162
Other prerequisites and dependencies

Microsoft Windows Server 2008 or later (must include Hyper-V) Brocade Host Connectivity Manager Multipathing I/O software from your storage array vendor. Hardware providers from your storage array vendor. Microsoft SCVMM 2008
Microsoft .NET Framework 2.0 (included in installation) Microsoft .NET Framework 3.0 (included in installation) Microsoft SQL Server 2005 Express Edition with Service Pack 2 (included in installation)
or Microsoft SQL Server 2005 Standard or Enterprise Editions with Service Pack 2 (separate installation)
Microsoft Windows PowerShellTM 1.0 Microsoft Windows Remote Management (WinRM) Microsoft Internet Information Server 7.0 (needed for Self-Service Portal only)
For more details and the most up-to-date information, refer to the documentation at http://www.microsoft.com/systemcenter/scvmm.
163
164
Appendix
Glossary
E
BCU Brocade Command Line Utility (BCU) Beaconing A continuous signaling of error conditions on a LAN. Beaconing can occur either on the port or on one or both sides of the link (known as end-to-end beaconing). Buffer Credit A system and method for providing flow control for a computer network. 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. DH Group Diffie-Hellman (DH) key exchange is a public key cryptosystem where public values are exchanged to arrive at a symmetric key among the end entities. There are five well-known DH groups, however, only DH-CHAP group 0, called NULL DH, is supported in this release. FOS Fabric Operating System. F_Port Fabric Port. A port on a switch to which an N_Port connects. HBA Host Bus Adapter HCM Host Connectivity Manager IOC I/O Controller ITL Initiator-Target-LUN. An Initiator Port (HBA controller) talks to one Target Port addressing one LUN. JSON Java Script Object Notation. A lightweight computer data interchange format. It is a text-based format for representing data structures and arrays.
165
Glossary
JSON-RPC A remote procedure call protocol encoded in JSON. Logging level The number of messages logged by the host computer depends on a predetermined logging level. Although many messages might be generated by the HBA, only certain types of messages are typically logged. Restrictions on message logging might be imposed by the operating system of the host computer. LUN Logical unit number. An address for an individual disk drive or virtual partition (volume) within a storage device. LUN mapping A process that makes a LUN available to some hosts and unavailable to other hosts. N_Port Node Port. A Fibre Channel host or storage port in a fabric or point-to-point connection. NPIV N_Port ID Virtualization (NPIV) enables a single Fibre Channel protocol port to appear as multiple, distinct ports, providing separate port identification within the fabric for each operating system image behind the port (as if each operating system image had its own unique physical port). Persistent binding A Fibre Channel (FC) host bus adapter (HBA) feature that enables you to permanently assign a system SCSI target ID to a specific FC device, even though the devices ID on the FC loop may be different each time the FC loop initializes. R_Port Remote port in a fabric. A remote port is a port that is physically separated from the adapter. SLER Sequence Level Error Recovery WWNN World Wide Node Name. The unique name for any particular node in the fabric; for example, an HBA. WWPN World Wide Port Name. The unique name for any particular port in the fabric. A WWNN can have multiple associated WWPNs.
166
Index
A
adapter command, 121 advanced port configuration options, 40 application log, 53 auth command, 123 Authentication Configuration dialog box, 83 authentication, security, 20
C
command adapter, 121 auth, 123 debug, 66, 128 diag, 58, 130 fabric, 134 fcdiag, 58, 132 fcpim, 135 IOC, 137 log, 39, 141 lport, 142 pbind, 144 port, 145 portlog, 66 portlogclear, 66 portlogct, 66 rport, 149 supportSave, 66, 154 vport, 155 Configure Names dialog box, 76 configuring NPIV, 43 configuring persistent binding using the CLI, 26 configuring port speed, 24 configuring QoS using the CLI, 29 configuring rate limiting using the CLI, 32 configuring security authentication using the GUI, 18
B
backing up data prior to uninstalling, 11 base port properties panel, 73 beaconing configuring using the BCU, 64 configuring using the GUI, 64 boot groups, 34 boot over SAN description of, 33 buffer credits, 22
D
debug command, 66, 128 Define Name dialog box, 77 diag command, 130 diagnostics related documentation, 57 running port-level test, 59, 61 types of tests, 2
167
dialog box Authentication Configuration, 83 Configure Names, 76 Define Master Log Filter, 94 Define Name, 77 Event Properties, 79 Persistent Binding, 95 Protocol Tests diagnostics, 102 Security Authentication, 83 Test Log Details, 112 discovery description of, 2 setting up, 13 setting up out-of-band, 14 documentation related for diagnostics, 57
HCM authentication, 9, 10 change password dialog box, 74 features, 2 main window, 12 master log icons, 51 product icons, 13 software overview, 1 statistics monitoring, 2 HCM logging level configuration, 39 host management, remote, 1 host security authentication, 17
I
interrupt control coalesce, 41 configuring using the BCU, 42 configuring using the GUI, 42 IOC command, 137
E
event categories, 93 event logs, how to filter, 52 Event Properties dialog box, 79 event severities, 51 events, master log, 51
L
launching HCM on Linux, 8 on Solaris, 8 on Windows, 7 Linux, launching HCM, 8 log application, 53 master log, 51 test, 62 log command, 39, 141 log off, 15 login, how to skip, 8 lport command, 142 LUN properties panel, 92
F
fabric command, 134 fcdiag command, 132 fcpim command, 135 FDMI specifications, 157 filtering event log entries, 52 frame data field size specifying using the BCU, 26 specifying using the GUI, 25
H
HBA Properties panel, 84
M
management software components, 1 Master Log Filter dialog box, 94 Master Log properties, 51 Master Log Properties tab, 93 monitoring statistics, 2 MPIO specifying using the BCU, 31 specifying using the GUI, 31
168
N
name configuration, 43 nickname association tasks, 43 NPIV benefits in a virtualization environment, 162 deployment in a virtualization environment, 162 description of, 162 hardware requirements, 162 prerequisites and dependencies, 163 NPIV configuration, 43
O
operating systems, support for, 4 operating system-specific features, 6
P
panel HBA Properties, 84 LUN properties, 92 Port POM, 98 Port SFP, 106 Port Statistics, 99 remote port properties, 89, 104 password how to change, 9, 10 how to reset, 11 path time out specifying using the BCU, 32 specifying using the GUI, 31 pbind command, 144 persistent binding configuring using the BCU, 29 configuring using the GUI, 26, 29 Persistent Binding dialog box, 95 persistent binding, configuring, 26 polling frequency rate control, 50 port command, 145 port configuration advanced, 40 basic options, 22 opening the advanced dialog box, 40 opening the basic dialog box, 23 port speed, 24
port logging level configuring using the BCU, 24 configuring using the GUI, 23 Port POM panel, 98 port properties panel, 96 Port SFP panel, 106 port speed configuring using the BCU, 25 configuring using the GUI, 24 Port Statistics panel, 99 Port Test diagnostics dialog box dialog box Port Test diagnostics, 101 port-level diagnostic tests, running from GUI, 61 port-level test how to run using the GUI, 59 portlog command, 66 portlogclear command, 66 portlogct command, 66 properties importing in EFCM format, 47 importing in FM format, 47 Protocol Tests diagnostics dialog box, 102
Q
quality of service (QoS), configuring, 29 queue depth configuring using the BCU, 41 configuring using the GUI, 41
R
rate limiting configuration, 32 remote host management, 1 Remote port properties panel, 89, 104 resetting a password, 11 resetting statistics, 50 rport command, 149
S
SAN components, types listed in device tree, 3
169
SCVMM description of, 161 multi-vendor virtualization support, 161 performance and resource optimization, 161 support for HA virtual machines, 161 support for virtual machines running on a Windows Server, 161 Windows PowerShell integration, 161 security authentication configuring using the BCU, 20 configuring using the GUI, 18 Security Authentication dialog box, 83 SFP displaying using the BCU, 64 displaying using the GUI, 65 management information, 65 SFP management, 64 skip login, 8 Solaris launching HCM, 8 specifications, FDMI, 157 statistics, resetting, 50 supportSave categories of information, 66 collecting on a port crash event, 67 collecting using a browser, 68 collecting using the BCU, 68 collecting using the GUI, 67 collection sources, 67 configuring using the CLI, 68 supportSave command, 66, 154
virtualization benefits using NPIV, 162 deploying with NPIV, 162 supported platforms, 162 using NPIV, 162 vport command, 155
W
Windows launching HCM application, 7 Windows SCVMM description of, 161 performance and resource optimization, 161 support for HA virtual machines, 161 support for multi-vendor virtualization, 161 support for virtual machines, 161 Windows PowerShell integration, 161 WWN adding a name, 47 exporting, 46 importing, 46 removing, 45
T
test log details, 62 Test Log Details dialog box, 112 tree node pop-up menus, 3
U
uninstalling the software, 11
V
Virtual Machine Manager, supported virtualization platforms, 162
170

HBA Admin Guide

Uploaded by

Copyright:

Available Formats

HBA Admin Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HBA Admin Guide

Uploaded by

Copyright:

Available Formats

What are some of the main features discussed in the document?

What are some of the main features discussed in the document?

What are some of the configuration options available for ports?

What are some of the configuration options available for ports?

53-1000881-02 December 19, 2008

Brocade Fibre Channel HBA

Brocade Communications Systems, Incorporated

About This Document

Getting Started with HCM Software

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

HCM Dialog Boxes

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Command Line Utility (BCU)

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

SAN-based Virtual Machine Migration using SCVMM

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

About This Document

How this document is organized

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

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Appendix C, Standards Compliance, provides reference information for standards

Whats new in this document

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Notes, cautions, and warnings

Notice to the reader

Referenced Trademarks and Products

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Other industry resources

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Getting technical help

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Tree node pop-up menus

Tree node pop-up menus

Pop-up menu feature

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Operating System (OS) support

Operating System (OS) support

Driver operating system support

Driver operating system support

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Operating System (OS) support

Driver operating system support

Note: The 8 Gbps FC HBA is supported on ESX 3.5 U2.

Local and remote management

HCM operating system support

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Brocade Fibre Channel HBA Administrators Guide 53-1000881-02

Getting Started with HCM Software

HCM software launch

Launching the application on Windows platforms

HCM Login dialog box