Brocade Communications Systems CNA 1010, HBA 415, CNA 1020, HBA 425, HBA 804 Troubleshooting Manual

...
53-1001582-01
®
22 June 2010
Brocade Adapters
Troubleshooting Guide
Supporting CNA models 1010 and 1020 Supporting HBA models 415, 425, 804, 815, and 825
Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 1745 Technology Drive San Jose, CA 95110 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: info@brocade.com
European Headquarters Brocade Communications Switzerland Sàrl Centre Swissair Tour B - 4ème étage 29, Route de l'Aéroport Case Postale 105 CH-1215 Genève 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 E-mail: emea-info@brocade.com
Asia-Pacific Headquarters Brocade Communications Systems China HK, Ltd. No. 1 Guanghua Road Chao Yang District Units 2718 and 2818 Beijing 100020, China Tel: +8610 6588 8888 Fax: +8610 6588 9999 E-mail: china-info@brocade.com
Asia-Pacific Headquarters Brocade Communications Systems Co., Ltd. (Shenzhen WFOE) Citic Plaza No. 233 Tian He Road North Unit 1308 – 13th Floor Guangzhou, China Tel: +8620 3891 2000 Fax: +8620 3891 2111 E-mail: china-info@brocade.com
Document History
Title Publication number Summary of changes Date
Brocade Adapters Troubleshooting Guide 53-1001253-01 New document June 2009
Brocade Adapters Troubleshooting Guide 53-1001253-02 New document September 2009
Brocade Adapters Troubleshooting Guide 53-1001582-01 Updates to support the 804
adapter.
June 2010
Contents
About this Document
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported CNA hardware and software . . . . . . . . . . . . . . . . . . . . . . . x
CNA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Fabric OS and switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Host operating system support. . . . . . . . . . . . . . . . . . . . . . . . . . . x
Supported HBA hardware and software . . . . . . . . . . . . . . . . . . . . . . xii
HBA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Fabric OS and switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Host operating system support. . . . . . . . . . . . . . . . . . . . . . . . . . xii
What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Other industry resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Providing details for support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx
Chapter 1 Introduction to Troubleshooting
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How to use this manual for troubleshooting . . . . . . . . . . . . . . . . . . . . 1
Gathering problem information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2 Isolating Problems
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How to use this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Brocade Adapters Troubleshooting Guide iii 53-1001582-01
General HBA and CNA problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Adapter not reported under server’s PCI subsystem. . . . . . . . . . 8
No adapters reported though BCU adapter --list command . . . . 9
Port link is not active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installer program does not autorun (Windows only) . . . . . . . . .10
Host system freezes or crashes . . . . . . . . . . . . . . . . . . . . . . . . .10
Operating system errors (blue screen). . . . . . . . . . . . . . . . . . . . 11
Driver event messages appearing in host system log files. . . . 12
BCU version mismatch warning . . . . . . . . . . . . . . . . . . . . . . . . .12
Errors or problems when entering BCU commands . . . . . . . . .12
Brocade BCU desktop shortcut missing. . . . . . . . . . . . . . . . . . .13
Installing driver update disk (DUD) results in wrong driver versions 13
I/O data traffic issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Driver installation fails and system cannot be booted . . . . . . . 14
Cannot remove Linux driver with uninstaller application or scripts14
Files needed for bfad.sys message appears . . . . . . . . . . . . . . .15
Cannot roll back driver on all adapter instances using Device
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Errors when installing brocade_driver_linux_<versions>.tar.gz
package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operating system crashes after invalid HCM operand . . . . . . . 16
UEFI boot problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
BIOS boot problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
HBA problems only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Quality of Service performance issues. . . . . . . . . . . . . . . . . . . . 22
Quality of Service not functioning. . . . . . . . . . . . . . . . . . . . . . . . 23
Unable to create more than 126 Virtual (NPIV) ports for HBA .23
Ethernet network interface problems (CNAs only) . . . . . . . . . . . . . . 24
Ethernet loopback test problems . . . . . . . . . . . . . . . . . . . . . . . . 24
Ethernet link ports or LOM not coming up on reboot in Linux .25
Loss of adapter hardware address in Linux. . . . . . . . . . . . . . . .25
Loss of adapter IP address in Linux . . . . . . . . . . . . . . . . . . . . . .25
Network stack runs out of heap . . . . . . . . . . . . . . . . . . . . . . . . . 26
NIC numbering unexpected on VMware systems . . . . . . . . . . .26
Ping to remote host is failing. . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Teaming errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
VLAN creation and operation problems . . . . . . . . . . . . . . . . . . .28
Teaming or VLAN operations through HCM fail . . . . . . . . . . . . .29
Poor network performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
iv Brocade Adapters Troubleshooting Guide
53-1001582-01
FCoE and Fibre Channel problems . . . . . . . . . . . . . . . . . . . . . . . . . .31
Loss of sync and loss of signal errors in port statistics . . . . . . 31
Fabric authentication failures. . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Adapter is not showing in the fabric . . . . . . . . . . . . . . . . . . . . . . 31
Virtual devices not listed in name server. . . . . . . . . . . . . . . . . .32
Adapter not registering with the name server or cannot access
storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
FCoE link is down (CNAs only). . . . . . . . . . . . . . . . . . . . . . . . . . .32
I/O problem on connected FCoE device (CNAs only). . . . . . . . .34
I/Os are not failing over immediately on path failure in MPIO setup 34 Disk I/O requests cause low throughput and high latency on Linux34 Disk I/O requests cause low throughput and high latency on VMware 34
CEE network problems (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . .35
CEE is not enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
HCM and HCM Agent problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Failed to connect to agent on host... error when using HCM . .35
Unable to completely uninstall HCM. . . . . . . . . . . . . . . . . . . . . .38
Time on HCM screens does not match system time . . . . . . . . .39
Verifying Fibre Channel and CEE links(stand-up adapters) . . . . . . .39
Adapter driver installation verification. . . . . . . . . . . . . . . . . . . . . . . .40
Confirming driver package installation with HCM . . . . . . . . . . . 41
Confirming driver package installation in Windows systems . . 41
Confirming driver package installation in Linux systems . . . . . 42
Confirming driver package installation in Solaris systems . . . .43
Confirming driver package installation in VMware systems . . .43
Troubleshooting mezzanine card problems. . . . . . . . . . . . . . . . . . . .44
Additional references for isolating problems. . . . . . . . . . . . . . . . . . . 44
Chapter 3 Tools for Collecting Data
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
For detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Data to provide support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Data collection using host system commands . . . . . . . . . . . . . . . . . 48
Data collection using BCU commands and HCM . . . . . . . . . . . . . . . 50
Support Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Collecting adapter data using HCM . . . . . . . . . . . . . . . . . . . . . .54
Collecting adapter data using BCU commands . . . . . . . . . . . . . 54
Data collection using Fabric OS commands (Brocade switches only)55
Adapter event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Host system logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
HCM logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Logging levels adjustment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Brocade Adapters Troubleshooting Guide v 53-1001582-01
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Authentication statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
CEE statistics (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
CEE query (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Ethernet statistics (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . .65
Ethernet IOC statistics (CNAs only). . . . . . . . . . . . . . . . . . . . . . . 66
FCoE statistics (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Fabric statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
IOC statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
FCP initiator mode statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Logical port statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Remote port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Quality of Service statistics (HBAs only) . . . . . . . . . . . . . . . . . . .73
Virtual port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
VLAN Statistics (CNAs only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Beaconing(stand-up adapters) . . . . . . . . . . . . . . . . . . . . . . . . . .75
Internal and external loopback tests . . . . . . . . . . . . . . . . . . . . . 76
Ethernet port loopback test (CNAs only) . . . . . . . . . . . . . . . . . .77
PCI loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Memory test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Pinging Fibre Channel end points. . . . . . . . . . . . . . . . . . . . . . . . 80
Adapter temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Queue test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Trace route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Echo test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
SCSI test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Test Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Collecting BIOS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Displaying BIOS data through BCU . . . . . . . . . . . . . . . . . . . . . . .84
Display BIOS data through HCM . . . . . . . . . . . . . . . . . . . . . . . . .84
Collecting LLDP data (CNAs only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Collecting SFP data (stand-up adapters). . . . . . . . . . . . . . . . . . . . . .85
SFP properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Predictive optical monitoring (POM) . . . . . . . . . . . . . . . . . . . . . .85
Collecting port data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Displaying port properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Displaying CEE port properties (CNAs only) . . . . . . . . . . . . . . . .86
Displaying Ethernet port properties (CNAs only) . . . . . . . . . . . . 87
Displaying FCoE port properties (CNAs only) . . . . . . . . . . . . . . . 87
Displaying FCoE port properties . . . . . . . . . . . . . . . . . . . . . . . . . 88
Displaying remote port properties . . . . . . . . . . . . . . . . . . . . . . .88
Displaying logical port properties . . . . . . . . . . . . . . . . . . . . . . . .88
Displaying virtual port properties . . . . . . . . . . . . . . . . . . . . . . . .88
Displaying the port log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Displaying the port list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Performing a port query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Displaying port speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
vi Brocade Adapters Troubleshooting Guide
53-1001582-01
Collecting teaming information (CNAs only) . . . . . . . . . . . . . . . . . . . 90
Displaying team data and statistics through HCM . . . . . . . . . .90
Displaying configured team data through BCU . . . . . . . . . . . . .90
Authentication settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Displaying authentication settings through HCM . . . . . . . . . . . 91
Displaying authentication settings through BCU . . . . . . . . . . . .91
QoS settings (HBAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Determining QoS settings through HCM. . . . . . . . . . . . . . . . . . .92
Target rate limiting settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Determining target rate limiting settings through BCU . . . . . . .92
Determining settings through HCM . . . . . . . . . . . . . . . . . . . . . .93
Persistent binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Displaying Persistent Binding settings through BCU . . . . . . . . .93
Displaying Persistent Binding settings through HCM . . . . . . . .94
Chapter 4 Performance Optimization
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Tuning storage drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Linux tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Solaris tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Windows tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
VMware tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Tuning network drivers (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Windows tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Linux tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
VMware tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Appendix A Adapter BIOS and Event Message Reference
Adapter BIOS messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Adapter driver event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Appendix B HCM and Installer Message Reference
Index
Brocade Adapters Troubleshooting Guide vii 53-1001582-01
viii Brocade Adapters Troubleshooting Guide
53-1001582-01

About this Document

In this chapter

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported CNA hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Supported HBA hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Providing details for support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

How this document is organized

This manual provides troubleshooting information on Brocade host bus adapters (HBAs) and converged network adapters (CNAs). It is organized to help you find the information that you want as quickly and easily as possible.
The document contains the following components:
Chapter 1, “Introduction to Troubleshooting” provides an introduction and approach to
troubleshooting adapter problems, as well as tips for gathering problem information. A checklist is also provided to verify that required procedures have been followed during installation.
Chapter 2, “Isolating Problems” provides information on common adapter problems and
procedures to diagnose and recover from these problems.
Chapter 3, “Tools for Collecting Data” provides a summary of diagnostic and monitoring tools
available through the Host Connectivity Manager (HCM), Brocade Command Line Utility (BCU), Fabric OS commands, and host system to help you isolate and resolve adapter-related problems.
Chapter 4, “Performance Optimization” contains guidelines for optimizing adapter
performance on your host system.
Appendix A, “Adapter BIOS and Event Message Reference” contains details on all event
messages generated by adapter drivers.
Brocade Adapters Troubleshooting Guide ix 53-1001582-01
NOTE
This publication is a companion guide to be used with the Brocade Adapters Administrator’s Guide.
NOTE
NOTE
NOTE
That publication provides detailed information on adapter monitoring and diagnostic tools in the HCM and the BCU.

Supported CNA hardware and software

This section describes CNA hardware and software support.
CNA support
The following Fibre Channel over Ethernet (FCoE) CNAs are supported in this release:
Install only Brocade-branded small form factor pluggables (SFPs) in these stand-up CNAs.
Brocade 1010. Single-por t CNA with a per-port maximum of 10 Gbps.
Brocade 1020. Dual-port CNA with a per-port maximum of 10 Gbps.
Fabric OS and switch support
Brocade CNAs must connect to Fibre Channel SANs and Ethernet data networks through a compatible FCoE switch. For a current list of compatible switches, refer to the latest compatibility matrices on the Brocade website at www.brocade.com. Select Products & Solutions, and then select the Compatibility link.
Host operating system support
This section describes operating systems support for Brocade Host Connectivity Manager (HCM), Brocade Command Line Utility (BCU), and CNA drivers.
Specific operating system release levels, service pack levels, and other patch requirements are detailed in the current HBA and CNA release notes.
Also refer to the latest Brocade compatibility matrices on the Brocade website at www.brocade.com for a list of supported host systems and operating systems. Select Products & Solutions, and then select the Compatibility link.
x Brocade Adapters Troubleshooting Guide
53-1001582-01
HCM support
NOTE
NOTE
NOTE
The following operating systems support HCM:
Windows 2003 R2 SP2 x86, x64, IA64
Windows Server 2008 x86, x64, IA64
Windows Server Core for Windows 2008 x86, x64, IA64
HCM is supported only on the guest operating system on Windows Server Core.
Linux RHEL4, RHEL5, SLES10, and SLES11
Solaris 10 (x86, x64, and SPARC)
VMware ESX Server 3.5 and 4.0x86, x64
HCM is supported only on the guest operating system on VMware.
Windows Vista (HCM only)
Windows XP (HCM only)
Specific operating system service pack levels and other patch requirements are detailed in the current HBA and CNA release notes for your adapter software version.
FCoE support
The following lists operating systems that support FCoE for the CNAs:
Windows 2003 x86, x64, IA64
Windows Server 2008 x86, x64, IA64
Microsoft Hyper V for Windows 2008 x86, x64, IA64
Windows Server Core 2008 x86, x64, IA64
Microsoft WinPE 2.x for Windows 2008 x86, x64, IA64
Linux RHEL4, RHEL5, SLES10, and SLES11 x86, x64, IA64
Solaris 10 (x86, x64, and SPARC)
VMware ESX Server 3.5 U5 and 4.0 x86, x64
Drivers, BCU, and HCM Agent are supported on the VMware “console” Operating System. HCM is supported only on the guest operating system on VMware.
Specific operating system service pack levels, update levels, and patch requirements are detailed in the current HBA and CNA release notes for your adapter software version.
Brocade Adapters Troubleshooting Guide xi 53-1001582-01
Ethernet support
NOTE
NOTE
The following lists operating systems that support Ethernet for the CNAs:
Windows 2003 R2 SP2 x86, x64
Windows Server 2008 x86, x64
Microsoft WinPE 2.x for Windows 2008 x86, x64
Windows Server Core x86, x64
Linux RHEL4, RHEL5, SLES10, and SLES11 x86, x64
VMware ESX Server 3.5 and 4.0x86, x64
Network drivers are not supported on IA-64 systems.
Specific operating system service pack levels, update levels, and patch requirements are detailed in the current HBA and CNA release notes for your adapter software version.

Supported HBA hardware and software

This section describes HBA hardware and software support.
HBA support
The following Fibre Channel host bus adapters (HBAs) are supported in this release:
Brocade 804. Dual-port mezzanine HBA with a per-port maximum of 8 Gbps. This HBA installs
in supported server blades that install in supported blade system enclosures.
Brocade 815. Single-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps
SFP+.
Brocade 825. Dual-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps
SFP+.
Brocade 415. Single-port stand-up HBA with a per-port maximum of 4 Gbps using a 4 Gbps
SFP.
Brocade 425 Dual-port stand-up HBA with a per-port maximum of 4 Gbps using a 4 Gbps SFP.
Install only Brocade-branded small form factor pluggable (SFPs) in stand-up HBAs. Mezzanine HBAs do not have SFPs and external port connectors, but utilize internal ports and connections to switch and I/O modules installed in the blade system enclosure.
Note the following about HBA support
This publication only supports the HBA models listed above and does not provide information
about the Brocade 410 and 420 Fibre Channel HBAs, also known as the Brocade 400 Fibre Channel HBAs.
Although you can install an 8 Gbps SFP+ into a Brocade 415 or 425 HBA, only 4 Gbps
maximum port speed is possible.
xii Brocade Adapters Troubleshooting Guide
53-1001582-01
Install only Brocade-branded SFPs in the HBAs.
Fabric OS and switch support
For a current list of servers, switches, and applications compatible with Brocade adapters, refer to the latest compatibility matrixes on the Brocade website at www.brocade.com. Select Products & Solutions, and then select the Compatibility link.

What’s new in this document

This document adds details on the Brocade 804 adapter. For further information about new features not covered in this document and documentation updates, refer to the release notes for your adapter software version.

Document conventions

This section describes text formatting conventions and important notice formats used in this document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
bold text Identifies command names
Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI
italic text Provides emphasis
Identifies variables Identifies paths and Internet addresses Identifies document titles
code text Identifies CLI output
Identifies command syntax examples
For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase.
Command syntax conventions
Command syntax in this manual follows these conventions:
command Commands are printed in bold.
--option, option Command options are printed in bold.
-argument, arg Arguments.
Brocade Adapters Troubleshooting Guide xiii 53-1001582-01
NOTE
ATTENTION
CAUTION
DANGER
[ ] Optional element.
variable Variables are printed in italics. In the help pages, values are underlined
enclosed in angled brackets < >.
... Repeat the previous element, for example “member[;member...]”
value Fixed values following arguments are printed in plain font. For example,
--show WWN
| Boolean. Elements are exclusive. Example:
--show -mode egress | ingress
or
Command examples
This book describes how to perform configuration tasks using the Fabric OS command line interface and the BCU interface, but does not describe the commands in detail. For complete descriptions of all commands, including syntax, operand description, and sample output, see the Fabric OS Command Reference and Brocade Adapters Administrator’s Guide.
Notes, cautions, and warnings
The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.
A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.
An Attention statement indicates potential damage to hardware or data.
A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data.
A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.
Key terms
For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. See “Brocade resources” on page xv for instructions on accessing MyBrocade.
xiv Brocade Adapters Troubleshooting Guide
53-1001582-01
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 Referenced Trademarks and Products
Microsoft Corporation Windows, Windows Server 2003, Windows Server 2008, Vista,
Oracle Corporation Solaris
Red Hat Inc. Red Hat Enterprise Linux (RHEL)
Novell, Inc. SUSE Linux Enterprise Server (SLES)
VMware, Inc. ESX Server
SPARC International, Inc. SPARC
Hewlett Packard Corp. BladeSystem
XP, PE for Windows, Hyper V for Windows, Windows Automated Installation Kit (WAIK)

Additional information

This section lists additional Brocade and industry-specific documentation that you might find helpful.
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID and password. A variety of resources for Brocade products is available.
Adapters
For adapter resources, such as product information, software, firmware, and documentation, visit the following websites:
HBA website at www.brocade.com/hba
CNA website at www.brocade.com/cna
For additional information on Brocade adapters, refer to the following publications:
Brocade FCoE CNA Quick Installation Guide (provided with your CNA model).
Brocade Fibre Channel HBA Quick Installation Guide (provided with your HBA model).
Brocade Adapters Installation and Reference Manual
Brocade Adapters Troubleshooting Guide xv 53-1001582-01
Brocade Adapters Administrator’s Guide
CIM Provider for Brocade Adapters Installation Guide
FCoE Switch
For information on the Brocade FCoE Switch for connecting stand-up CNAs, refer to the following publications:
Brocade 8000 Hardware Reference Manual
WebTools Administrator’s Guide
EZSwitchSetup Administrator’s Guide
Fabric OS Command Reference Manual
Blade servers and blade system enclosure components
Brocade mezzanine are compatible with blade servers, switch modules, interconnect modules, I/O modules, and other components that install in supported blade system enclosures. For compatibility information, visit the blade server and blade system enclosure manufacturer’s website. Also refer to the Hardware Compatibility section in Chapter 1 of the Brocade Adapters Installation and Reference Manual.
SAN information
White papers, online demonstrations, and data sheets are available through the Brocade website at:
http://www.brocade.com/products-solutions/products/index.page
For additional Brocade documentation, visit the Brocade website:
http://www.brocade.com
Other industry resources
For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications:
http://www.t11.org
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website:
http://www.fibrechannel.org

Providing details for support

Contact your Brocade FCoE CNA support supplier for hardware, firmware, and software support, including product repairs and part ordering. Provide the following information:
xvi Brocade Adapters Troubleshooting Guide
53-1001582-01
1. General information:
Brocade adapter model number
Host operating system version
Software name and software version, if applicable
syslog message logs
bfa_supportsave output.
To expedite your support call, use the bfa_supportsave feature to collect debug information from the driver, internal libraries, and firmware. You can save valuable information to your local file system and send it to support personnel for further investigation. For details on using this feature, refer to “Support Save” on page 48.
Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions.
Description of any troubleshooting steps already performed and the results.
2. Adapter serial number:
The adapter serial number and corresponding bar code are provided on the serial number label illustrated below. This label is affixed to the adapter card.
*FT00X0054E9*
FT00X0054E9
You can also display the serial number through the following HCM dialog boxes and BCU commands:
Adapter Properties tab in HCM.
Select an adapter in the device tree, then click the Properties tab in the right pane.
BCU adapter --list command.
This command lists all adapters in the system and information such as model and serial numbers.
3. Port World-Wide Name (PWWN).
Determine this through the following resources:
Label affixed on adapter card provides the WWPN for each port.
Brocade BIOS Configuration Utility.
Select the appropriate adapter port from the initial configuration utility screen, then select Adapter Settings to display the WWNN and PWWN for the port. For details, refer to the Boot Code chapter in the Brocade Adapters Installation and Reference Manual.
Port Properties tab in HCM.
Select a port for a specific adapter in the device tree, then click the Properties tab in the right pane.
The following BCU commands:
Brocade Adapters Troubleshooting Guide xvii 53-1001582-01
NOTE
Command Function
port --query <port_id> Displays port information, including the PWWN
for the FCoE port. The port_id parameter is the port number.
port --list Lists all the physical ports on the adapter along
with their basic attributes, such as the PWWN.
4. Media access control (MAC) addresses (CNAs only)
The CNA card MAC address can be found in HCM by selecting the CNA in the device tree and clicking the Properties tab in the right pane. This displays the CNA Properties panel. Look for the MAC Address field.
The CNA MAC address can be found in HCM by selecting the CNA in the device tree and clicking the Properties tab in the right pane to display the CNA Properties panel. Look for the MAC Address field.
Each port has a “burned-in” local port MAC address. This is the source MAC for LLDP communications between the CNA and FCoE switch. To find this MAC address, select a CEE port in the HCM device tree, then click the Properties tab in the right pane to display the port Properties panel. Look for the Local port MAC field.
The Ethernet MAC address is used for normal Ethernet operations. To find this MAC address using HCM, select an Ethernet port in the HCM device tree, then click the Properties tab in the right pane to display the port Properties panel. Look for the Current MAC address and Factory MAC address fields.
Each enode logging in to the fabric through a local CNA port is assigned a MAC address during FCoE Initialization Protocol (FIP) operations. This MAC is assigned for the current FCoE communication only. To find this MAC address, perform one of the following tasks:
Select an FCoE port in the HCM device tree, then click the Properties tab in the right
pane to display the port Properties panel. Look for the FCoE MAC field.
Enter the port --query port_id BCU command. Look for the FCoE MAC.
MAC addresses assigned during FCoE initialization operations cannot be changed using device management applications.
The FCoE Forwarder (FCF) MAC address is the address of the attached FCoE switch. Select an FCoE port in the HCM device tree, then click the Properties tab in the right pane to display the port Properties panel. Look for the FCF MAC field.
You can also determine port MAC addresses using the following BCU commands:
Command Function
port ---query port_id Displays port information, including the MAC
addresses. The <port_id> parameter is the port number.
port ---list Lists all the physical ports on the adapter along
with their Ethernet and FCoE MAC addresses.
xviii Brocade Adapters Troubleshooting Guide
53-1001582-01
NOTE
For details on using HCM and BCU commands, refer to the Brocade Adapters Administrator’s Guide.

Document feedback

Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to:
documentation@brocade.com
Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
Brocade Adapters Troubleshooting Guide xix 53-1001582-01
xx Brocade Adapters Troubleshooting Guide
53-1001582-01
Chapter

Introduction to Troubleshooting

In this chapter

How to use this manual for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Gathering problem information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

How to use this manual for troubleshooting

An adapter, such as an HBA or CNA, is one component of a larger network consisting of switches, storage devices, host systems and the cabling and connections to these components. Although there may be a problem in the adapter or an adapter component, the problem could also originate in another network component or connections between these components. Before removing and replacing adapters, launching adapter diagnostics, or even gathering statistics on adapter operation, it is important that you perform the following tasks:
1. Fully describe the problem and gather complete information about the symptoms that suggest a problem exists. Refer to “Gathering problem information” on page 2.
1
2. Isolate or resolve the problem by first using information in Chapter 2, “Isolating Problems”.
Adapter problems are organized under the following categories:
“General HBA and CNA problems”
“HBA problems only”
“Ethernet network interface problems (CNAs only)”
“FCoE and Fibre Channel problems”
“CEE network problems (CNAs only)”
Search through the list of problems in Tabl e 2 on page 5. Problems are organized in the table by problem title, category, and whether the problem is operating-system-specific. Click on a problem to go to the chapter section containing details of possible causes and actions for resolution.
Each problem section in Chapter 2 provides a complete description of the problem, possible causes, and actions for resolution. Fixes and actions may reference BCU commands, HCM features, and host operating system commands. These are described in Chapter 3, “Tools for
Collecting Data” which you can use to further isolate or resolve the problem.
Other helpful sections in Chapter 2 include the following:
“Verifying Fibre Channel and CEE links (stand-up adapters)” on page 38.
“Adapter driver installation verification” on page 39.
“Troubleshooting mezzanine card problems” on page 43.
“Additional references for isolating problems” on page 43
Brocade Adapters Troubleshooting Guide 1 53-1001582-01

Gathering problem information

NOTE
1
3. Use the BCU commands, HCM features, and host operating system commands described in
4. Consider these factors when isolating and resolving the problem:
Chapter 3, “Tools for Collecting Data” to gather data for resolving problems.These tools include
event logs, operating statistics, and diagnostics.
Can the issue be resolved using the latest supported combination of host system BIOS,
operating system, operating system updates, or adapter drivers?
Refer to “Software installation and driver packages” and “Operating system support” in Chapter 1 of the Adapters Installation and Reference Manual for details on driver packages and operating system support. Also refer to the latest release notes on
www.brocade.com/hba or www.brocade.com/cna.
Does the issue persist when the adapter is installed in a different platform or blade server
or connected to a different switch port?
Does the problem persist if using a different SFP or cable?
Can this problem be reproduced on one or more adapters, ports, or host system? Can you
identify specific steps that consistently reproduce this problem on one or more hosts?
Is the problem documented in release notes for the adapter, operating system, or host
system BIOS?
Is the problem documented in release notes for the switch and target storage system?
Is unexpected behavior intermittent or always present?
If the problem is in a Fibre Channel or FCoE switch, storage device, or in connectivity between these components, refer to the documentation, help systems, or service providers of that equipment.
5. If you cannot resolve the problem, gather and provide problem information to your adapter support provider for resolution.
If troubleshooting information in this manual does not resolve problems, check the installed version of the adapter (chip revision) and driver (fw version) using the BCU adapter --query command. To use this command, refer to “Collecting adapter data using BCU commands” on page 52. Also refer to release notes posted on the Brocade adapter website for known problems relating to the adapter and driver versions. The HBA website is www.brocade.com/hba. The CNA website is
www.brocade.com/cna.
Gathering problem information
Perform the following tasks to obtain as much information as possible before contacting technical support. Be sure to take careful notes for use as a record and reference.
Describe the symptoms that you are observing. Be specific. Here are some examples:
- User experiences, such as slow performance or file access.
- Expected storage devices not visible from the HCM or host system’s storage management
application.
- Adapter not recognized by host system BIOS.
- Adapter not recognized as PCI device by host system operating system.
2 Brocade Adapters Troubleshooting Guide
53-1001582-01
Gathering problem information
- LEDs not functioning on an adapter port that is connected to the fabric (stand-up
adapters).
- All LEDs on adapter port flashing amber.
What happened prior to the observed symptoms?
Describe all observed behavior that is unexpected and compare against expected behavior.
Gather information for support:
- Use appropriate tools on storage targets to gather information such as disk, tape, and
controller model and firmware levels.
- Run the bfa_supportsave BCU command on the host system and save output to a file on
your system.
This command captures all driver, internal libraries, firmware, and other information needed to diagnose suspected system issues. You can save captured information to the local file system and send it to support personnel for further investigation.
- Run the Fabric OS supportSave command on any Brocade switch and save output. This
command collects RASLOG, TRACE, supportShow, core file, FFDC data and other support information.
For details on using the Support Save feature, refer to “Support Save” on page 48.
Draw a topology map of the SAN from the adapters to the storage targets. Include the
components described in Table 1.
l
TABLE 1 Topology map details
1
Component How to identify
adapter Model, World-Wide Name (WWN),
and driver release level.
Fibre Channel switches Model, WWN, and Fabric OS
version.
Fiber optic links between adapter, switches, and storage ports
Host hardware Model and hardware revision.
The bfa_supportsave and FOS supportsave commands can provide current information for the topology map. Also, consider using the Brocade SAN Health products to provide information on your SAN environment, including an inventory of devices, switches, firmware versions, and SAN fabrics, historical performance data, zoning and switch configurations, and other data. Click the Services & Support tab on www.brocade.com for more information on these products.
Port WWNs connected to all links.
Run appropriate diagnostic tools for storage targets.
Determine what has changed in the SAN. For example, if the SAN functioned without problems
before installing the adapter, then the problem is most likely in the adapter installation or configuration, adapter hardware, or adapter driver package. Other examples of things to investigate might be changes in the connected switch or storage system firmware, or an offline switch.
For stand-up adapters, investigate disconnected or faulty cables between the adapter, switch, or storage controller fiber optic ports. Check if target storage devices are correctly connected to the switch and are turned on.
Brocade Adapters Troubleshooting Guide 3 53-1001582-01
Gathering problem information
1
Record the time and frequency of symptoms and the period of time symptoms have been
Determine if unexpected behavior is intermittent or always present.
List steps that have been taken to troubleshoot the problem, including changes attempted to
For mezzanine adapters, make sure that the adapter, the blade server where the adapter is installed, and the modules in the blade system enclosure that support adapter operation are compatible. Verify that the blade server and modules that support adapter operation are installed in the appropriate enclosure bays. Also check whether target storage devices are connected to the appropriate switch, interconnect module, or I/O module in the blade system enclosure and are turned on.
observed.
isolate the problem.
4 Brocade Adapters Troubleshooting Guide
53-1001582-01
Chapter

Isolating Problems

In this chapter

How to use this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General HBA and CNA problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
HBA problems only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Ethernet network interface problems (CNAs only) . . . . . . . . . . . . . . . . . . . . 23
FCoE and Fibre Channel problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
CEE network problems (CNAs only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
HCM and HCM Agent problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Verifying Fibre Channel and CEE links (stand-up adapters) . . . . . . . . . . . . . 38
Adapter driver installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Troubleshooting mezzanine card problems. . . . . . . . . . . . . . . . . . . . . . . . . . 43
Additional references for isolating problems . . . . . . . . . . . . . . . . . . . . . . . . . 43
2

How to use this chapter

Operation problems are arranged in this chapter in these categories:
“General HBA and CNA problems”
“HBA problems only”
“Ethernet network interface problems (CNAs only)”
“FCoE and Fibre Channel problems”
“CEE network problems (CNAs only)”
Use Tabl e 2 to quickly navigate to sections in this chapter that cover specific adapter problems. Each problem section in this chapter contains a description of the problem, possible causes, and actions for resolution. Click on the problem to link to the appropriate problem section.
TABLE 2 Isolate adapter problems
Problem Category OS Specific
“Adapter not reported under server’s PCI subsystem” “General HBA and CNA problems” All
“No adapters reported though BCU adapter --list command”
“Port link is not active” “General HBA and CNA problems” All
“Host system freezes or crashes” “General HBA and CNA problems” All
“Operating system errors (blue screen)” “General HBA and CNA problems” All
“General HBA and CNA problems” All
Brocade Adapters Troubleshooting Guide 5 53-1001582-01
How to use this chapter
2
TABLE 2 Isolate adapter problems (continued)
Problem Category OS Specific
“Driver event messages appearing in host system log files”
“BCU version mismatch warning” “General HBA and CNA problems” All
“I/O data traffic issues” “General HBA and CNA problems” All
“Driver installation fails and system cannot be booted” “General HBA and CNA problems” Windows
“Installer program does not autorun (Windows only)” “General HBA and CNA problems” Windows
“Files needed for bfad.sys message appears” “General HBA and CNA problems” Windows
“Cannot roll back driver on all adapter instances using Device Manager”
“Errors when installing brocade_driver_linux_<versions>.tar.gz package”
“Operating system crashes after invalid HCM operand” “General HBA and CNA problems” Linux
“System will not boot over SAN or on local disk in Legacy BIOS mode”
“Host not booting from remote LUN” “General HBA and CNA problems”
“Boot devices not available in host’s Boot Manager menu” “General HBA and CNA problems”
“Driver and operating system installation failure on boot LUN”
“Driver and operating system installation failure on boot LUN”
“Target not visible from host” “General HBA and CNA problems”
“Ctlr-B option does not display when booting host” “General HBA and CNA problems”
“No target devices found or link down message displays in Brocade BIOS Configuration menu”
“Unable to boot from the stored boot device settings in the adapter”
“Remote LUNs are not visible to the host” “General HBA and CNA problems”
“Cannot boot over SAN from installed CNAs” “General HBA and CNA problems”
“Boot from SAN may stop on some Hewlett Packard hosts” “General HBA and CNA problems”
“Adapter <port id>: BIOS not installed displays during boot process”
“Quality of Service performance issues” “HBA problems only” All
“Quality of Service not functioning” “HBA problems only” All
“General HBA and CNA problems” All
2008
“General HBA and CNA problems” Windows
“General HBA and CNA problems” Linux
“General HBA and CNA problems” “UEFI boot problems”
“UEFI boot problems”
“UEFI boot problems”
“General HBA and CNA problems” “UEFI boot problems”
“General HBA and CNA problems” “BIOS boot problems”
“BIOS boot problems”
“BIOS boot problems”
“General HBA and CNA problems” “BIOS boot problems”
“General HBA and CNA problems” “BIOS boot problems”
“BIOS boot problems”
“BIOS boot problems”
“BIOS boot problems”
“General HBA and CNA problems” “BIOS boot problems”
All
All
All
All
All
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
6 Brocade Adapters Troubleshooting Guide
53-1001582-01
How to use this chapter
TABLE 2 Isolate adapter problems (continued)
Problem Category OS Specific
2
“Unable to create more than 126 Virtual (NPIV) ports for HBA”
“Ethernet loopback test problems” “Ethernet network interface
“Ethernet link ports or LOM not coming up on reboot in Linux”
“Loss of adapter hardware address in Linux” “Ethernet network interface
“Loss of adapter IP address in Linux” “Ethernet network interface
“Network stack runs out of heap” “Ethernet network interface
“NIC numbering unexpected on VMware systems” “Ethernet network interface
“Poor network performance” “Ethernet network interface
“VLAN creation and operation problems” “Ethernet network interface
“Teaming or VLAN operations through HCM fail” “Ethernet network interface
“Ping to remote host is failing” “Ethernet network interface
“Teaming errors” “Ethernet network interface
“Loss of sync and loss of signal errors in port statistics” “FCoE and Fibre Channel
“Fabric authentication failures” “FCoE and Fibre Channel
“Adapter is not showing in the fabric” “FCoE and Fibre Channel
“Virtual devices not listed in name server” “FCoE and Fibre Channel
“Adapter not registering with the name server or cannot access storage”
“FCoE link is down (CNAs only)” “FCoE and Fibre Channel
“I/O problem on connected FCoE device (CNAs only)” “FCoE and Fibre Channel
“I/Os are not failing over immediately on path failure in MPIO setup”
“Disk I/O requests cause low throughput and high latency on Linux”
“HBA problems only” All
problems (CNAs only)”
“Ethernet network interface problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems (CNAs only)”
problems”
problems”
problems”
problems”
“FCoE and Fibre Channel problems”
problems”
problems”
“FCoE and Fibre Channel problems”
“FCoE and Fibre Channel problems”
All
Linux
Linux
Linux
VMware
VMware
Linux Windows
Windows
Windows 2003
All
Windows
All
All
All
All
All
All
All
Windows Linux VMware
Linux
Brocade Adapters Troubleshooting Guide 7 53-1001582-01

General HBA and CNA problems

2
TABLE 2 Isolate adapter problems (continued)
Problem Category OS Specific
“Disk I/O requests cause low throughput and high latency on VMware”
“CEE is not enabled” “CEE network problems (CNAs
“Failed to connect to agent on host... error when using HCM”
“Unable to completely uninstall HCM” “HCM and HCM Agent problems” Windows
“Time on HCM screens does not match system time” “HCM and HCM Agent problems” Windows
General HBA and CNA problems
This section provides possible resolutions for common problems that could with installed CNAs or HBAs. For additional information on troubleshooting problems on mezzanine or expansion card adapters, refer to “Troubleshooting mezzanine card problems” on page 43.

Adapter not reported under server’s PCI subsystem

The adapter is installed but not visible as a device in the host system’s PCI subsystem.
Verify whether the adapter is visible as a PCI device by executing your host’s operating system command to list PCI devices in the system. For details on this command, refer to the “List PCI Devices” row in Table 5 on page 46. If the adapter is not in the device list, refer to the following descriptions of possible causes and recommended actions to help resolve the problem.
“FCoE and Fibre Channel problems”
only)”
“HCM and HCM Agent problems” All
VMware
All
Server 2003
1. Possible Cause: Card not seated in host system connector properly.
Action: Reseat the adapter.
2. Possible Cause: Host system connector issues.
Action: Install an adapter of known working condition to determine whether there is a connector malfunction.
Action: Try installing the adapter into a different slot, if available.
3. Possible Cause: Adapter not compatible with host operating system or connected storage systems.
Action: Verify compatibility by reviewing the Brocade compatibility matrices on the Brocade website at www.brocade.com. Select Products & Solutions, and then select the Compatibility link.
8 Brocade Adapters Troubleshooting Guide
53-1001582-01
General HBA and CNA problems
2

No adapters reported though BCU adapter --list command

If the adapter does not display when the BCU adapter --list command is initiated, refer to the following descriptions of possible causes and recommended actions to help resolve the problem.
1. Possible Cause: Adapter is not reported under server’s PCI subsystem.
Action: Verify if the adapter is visible as a PCI device by executing your host’s operating system command to list PCI devices in the system. For details on this command, refer to the “List PCI Devices” row in Table 5 on page 46.
Action: If the adapter does not appear in the list of PCI devices, refer to “Boot devices not
available in host’s Boot Manager menu” on page 16 for possible causes and recommended
actions.
2. Possible Cause: Adapter driver is not loaded.
Action: Verify if the adapter is visible as a PCI device by executing your host’s operating system command to list PCI devices in the system. For details on these commands, refer to the “List PCI Devices” row in Table 5 on page 46.

Port link is not active

The link between the adapter and switch port does not appear to be active because of adapter LED operation (stand-up adapters only), lack of data over the link, or the BCU port --query or port --list command shows that the link state is down. Refer to “Displaying the port list” on page 86 for more information.
Refer to the following descriptions of possible causes and recommended actions or fixes for the problems:
1. Possible Cause: SFP or cable problems (stand-up adapters).
Action: Ensure that the SFPs and cables are connected properly on both adapter and switch sides. Check for any cable damage.
2. Possible Cause: Switch port is disabled or switch is disabled.
Action: Execute either the Fabric OS switchShow or portShow commands on the attached switch to ensure that the switch or individual port is not disabled or offline. Use appropriate switch commands to enable the port.
3. Possible Cause: Adapter port is disabled.
Action: Verify port state using the HCM Port Properties dialog box or BCU port --list command. Use BCU port --enable command to enable the port.
4. Possible Cause: Adapter’s port speed or topology mismatch with the switch port (HBAs only).
Action: Check the port topology setting on the switch using the Fabric OS portCfgShow command to ensure that Locked L_Port is OFF. Use the portCfgLport command to change the setting to OFF if required.
Action: Check the switch port speed using the Fabric OS portCfgShow command to verify that speed is either AUTO or matches the speed of the attached adapter port (for example, the speed setting for both ports is 4 Gbps).
Action: Check port speed on the adapter with the BCU port --list or port --query commands to display the current and configured speed. Refer to “Displaying port speed” on page 87 and
“Performing a port query” on page 87 for details on using these commands.
Brocade Adapters Troubleshooting Guide 9 53-1001582-01
General HBA and CNA problems
NOTE
2
5. Possible Cause: Non-Brocade-branded SFP installed (stand-up adapters). If non-Brocade
6. Possible Cause: Firmware failure. In most cases this causes a heartbeat failure, and if
branded SFPs are inserted on the adapter or switch, the port link will not come up.
Action: On the switch, execute the Fabric OS switchShow command to verify that “Mod_Inv” (invalid module) does not display for the port state.
Action: On the adapter, execute the port --list or port --query BCU commands to verify display in the Sfp field. Refer to “Displaying the port list” on page 86 and “Performing a port query” on page 87. If an unsupported SFP is detected, the Sfp field displays “us” (unsupported SFP) for port --list, and the Media field displays “Unsupported SFP” for port --query.
For additional actions and fixes for the port link not coming up, refer to “Verifying Fibre Channel
and CEE links (stand-up adapters)” on page 38.
auto-recovery is enabled, the driver recovers. No corrective action is needed.
Action: If link does not recover and BCU port --list command shows fcoe and eth state is link down, download the latest driver package from the Brocade adapter website (www.brocade.com/hba or www.brocade.com/cna). Remove and reinstall the driver package using instructions in the “Software Installation” chapter of the Brocade Adapters Installation and Reference Manual.

Installer program does not autorun (Windows only)

If the installer program does not automatically run from the CD that you create with the ISO file
containing all supported software installation packages, refer to the following descriptions of possible causes and recommended actions to help resolve the problem.
This ISO file can be downloaded from the CNA and HBA websites (www.brocade.com/hba or
www.brocade.com/cna).
Possible Cause: Autorun is not enabled on your system.
Action: Refer to “Installer program does not autorun (Windows only)” on page 10 for more information to isolate this problem.

Host system freezes or crashes

If the BIOS and the operating system recognize the adapter, but the host system freezes or crashes during startup and does not boot, refer to the following descriptions of possible causes and recommended actions to help resolve the problem
Possible Causes:
Conflicts with adapter port operating speed or topology of attached devices.
Adapter not compatible with host system.
Faulty fiber optic cabling and connections (stand-up adapters only).
Faulty or unseated SFPs or unsupported SFPs (stand-up adapters only).
10 Brocade Adapters Troubleshooting Guide
53-1001582-01
Loading...
+ 114 hidden pages