1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Adapter
  5. CNA 1010
  6. Troubleshooting manual

Brocade Communications Systems CNA 1010 Troubleshooting Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this 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

Advertisement

Table of Contents
loading

Related Manuals for Brocade Communications Systems CNA 1010

Summary of Contents for Brocade Communications Systems CNA 1010

  • Page 1 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...
  • Page 2 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.

  • Page 3: Table Of Contents

    Contents About this Document In this chapter ..........ix How this document is organized .
  • Page 4 General HBA and CNA problems ......8 Adapter not reported under server’s PCI subsystem..8 No adapters reported though BCU adapter --list command .
  • Page 5 FCoE and Fibre Channel problems ......31 Loss of sync and loss of signal errors in port statistics ..31 Fabric authentication failures .
  • Page 6 Statistics ..........62 Authentication statistics .
  • Page 7 Collecting teaming information (CNAs only) ....90 Displaying team data and statistics through HCM ..90 Displaying configured team data through BCU .
  • Page 8 viii Brocade Adapters Troubleshooting Guide 53-1001582-01...

  • Page 9: About This Document

    About this Document In this chapter • How this document is organized ........ix •...

  • Page 10: Supported Cna Hardware And Software

    NOTE This publication is a companion guide to be used with the Brocade Adapters Administrator’s Guide. 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: NOTE...
  • Page 11 HCM support 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 NOTE HCM is supported only on the guest operating system on Windows Server Core. •...

  • Page 12: Supported Hba Hardware And Software

    Ethernet support 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 •...

  • Page 13: Fabric Os And Switch Support

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

  • Page 14: Command Examples

    Optional element. variable Variables are printed in italics. In the help pages, values are underlined or enclosed in angled brackets < >. Repeat the previous element, for example “member[;member...]” value Fixed values following arguments are printed in plain font. For example, show WWN Boolean.

  • Page 15: Notice To The Reader

    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.

  • Page 16: Other Industry Resources

    • 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 •...
  • Page 17 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.
  • Page 18 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.

  • Page 19: Document Feedback

    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.
  • Page 20 Brocade Adapters Troubleshooting Guide 53-1001582-01...

  • Page 21: Chapter 1 Introduction To Troubleshooting

    Chapter Introduction to Troubleshooting In this chapter • How to use this manual for troubleshooting ......1 •...

  • Page 22: Gathering Problem Information

    Gathering problem information 3. Use the BCU commands, HCM features, and host operating system commands described in Chapter 3, “Tools for Collecting Data” to gather data for resolving problems.These tools include event logs, operating statistics, and diagnostics. 4. Consider these factors when isolating and resolving the problem: •...
  • Page 23 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. •...
  • Page 24 Gathering problem information 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.

  • Page 25: In This Chapter

    Chapter Isolating Problems In this chapter • How to use this chapter ......... . 5 •...
  • Page 26 How to use this chapter TABLE 2 Isolate adapter problems (continued) Problem Category OS Specific “Driver event messages appearing in host system log “General HBA and CNA problems” files” “BCU version mismatch warning” “General HBA and CNA problems” “I/O data traffic issues” “General HBA and CNA problems”...
  • Page 27 How to use this chapter TABLE 2 Isolate adapter problems (continued) Problem Category OS Specific “Unable to create more than 126 Virtual (NPIV) ports for “HBA problems only” HBA” “Ethernet loopback test problems” “Ethernet network interface problems (CNAs only)” “Ethernet link ports or LOM not coming up on reboot in “Ethernet network interface Linux Linux”...

  • Page 28: General Hba And Cna Problems

    General HBA and CNA problems TABLE 2 Isolate adapter problems (continued) Problem Category OS Specific “Disk I/O requests cause low throughput and high latency “FCoE and Fibre Channel VMware on VMware” problems” “CEE is not enabled” “CEE network problems (CNAs only)”...

  • Page 29: No Adapters Reported Though Bcu Adapter --List Command

    General HBA and CNA problems 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.

  • Page 30: Installer Program Does Not Autorun (Windows Only)

    General HBA and CNA problems 5. Possible Cause: Non-Brocade-branded SFP installed (stand-up adapters). If non-Brocade 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.
  • Page 31 General HBA and CNA problems Action: Disconnect all devices from the adapter, then reboot the host system. • If the system does not freeze when rebooted and operates correctly, use the following information to resolve the problem: a. Check for faulty cable and cable connections. b.

  • Page 32: Operating System Errors (Blue Screen)

    General HBA and CNA problems Operating system errors (blue screen) If critical errors display for the host system and the system blue screen appears, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: Adapter driver not loaded.

  • Page 33: I/O Data Traffic Issues

    General HBA and CNA problems I/O data traffic issues I/O data traffic issues are occurring, such as an application is not receiving data, FTP problems on an Ethernet network, data is not reaching a target on a Fibre Channel network, or ping failures. 1.

  • Page 34: Files Needed For Bfad.sys Message Appears

    General HBA and CNA problems NOTE If you remove the adapter driver (which requires a system reboot because the adapter was modified), and then reinstall the driver, installation will fail because the operating system cannot update the driver while a system reboot is pending. However, if you reboot the system after removing the driver, the operating system will not come up because the driver accessing the operating system was removed.

  • Page 35: Errors When Installing Brocade_Driver_Linux_.Tar.gz

    General HBA and CNA problems Errors when installing brocade_driver_linux_<versions>.tar.gz package If errors occur when installing the no architecture (noarch) brocade_driver_linux_<versions>.tar.gz driver package, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: Appropriate distribution kernel development packages are not installed on your host system for the currently running kernel.
  • Page 36 General HBA and CNA problems 9. Confirm that Hard Disk ‘x’ is present in the list. If not, return to step 3 and add Hard Disks to the boot order. 10. Select Commit Changes and press Enter. 11. Press Esc to return to Boot Manager. 12.
  • Page 37 General HBA and CNA problems 3. Possible Cause: The adapter is not compatible with the host operating system or connected storage systems. Action: Verify compatibility matrices on the Brocade website at www.brocade.com. Select Products & Solutions, and then select the Compatibility link. 4.

  • Page 38: Bios Boot Problems

    General HBA and CNA problems Driver and operating system installation failure on boot LUN Installation fails when installing drivers with the driver update disk (DUD) and an installing operating system to a remote LUN being used for booting over SAN. Possible Cause: The appropriate driver update disk (DUD) may not have been used for the host operating system and platform.
  • Page 39 General HBA and CNA problems 4. Possible Cause: There is a problem with the remote port. Action: Verify that the remote target port (rport) is reporting itself online by comparing rport online and rport offline statistics. Refer to “Remote port statistics” on page 70 for details on displaying these statistics.
  • Page 40 General HBA and CNA problems 2. Possible Cause: In HCM, the boot option is set to Auto Discovered from Fabric or First Visible LUN in the Boot over SAN dialog box. Action: Change the boot options to User Configured LUNs in the Boot Over SAN dialog box. Refer to the Boot Code chapter in the Brocade Adapters Installation and Reference Manual for details.

  • Page 41: Hba Problems Only

    HBA problems only Action: Perform the following steps. 1. Boot the server and press F10 when prompted to run BIOS Setup. 2. Select the Advanced menu. 3. Scroll down to IPMI and press Enter. 4. Scroll down to the System Event Log selection and press Enter. 5.

  • Page 42: Quality Of Service Not Functioning

    HBA problems only 1. Possible Cause: One or both of the required licenses are not installed on the edge switch connected to the HBA port: • Adaptive Networking (AN) license. • Server Application Optimization (SAO) license. Action: Enter the bcu qos --query command for the adapter port connected to the switch. If the QoS state is “Unknown”...

  • Page 43: Ethernet Network Interface Problems (Cnas Only)

    Ethernet network interface problems (CNAs only) Ethernet network interface problems (CNAs only) Use the following information to isolate problems that are more specific to CNA function. NOTE Switch command examples used in this section are for the Brocade 8000 Switch. Ethernet loopback test problems Errors occur during BCU Ethernet loopback tests.

  • Page 44: Ethernet Link Ports Or Lom Not Coming Up On Reboot In Linux

    Ethernet network interface problems (CNAs only) Ethernet link ports or LOM not coming up on reboot in Linux The host system’s LAN on motherboard (LOM) is not coming up or CNA ports are not visible after rebooting Linux host. 1. Possible Cause: A ifcfg-ethX script is not configured to bring up each LOM and CNA during the system boot process.

  • Page 45: Network Stack Runs Out Of Heap

    Ethernet network interface problems (CNAs only) Network stack runs out of heap The network stack on VMware systems is running out of heap space. Possible Cause: Enabling NetQueue and using jumbo frames has caused the network stack to run out of heap with default values set for netPktHeapMaxSize and netPktHeapMinSize. Leaving default values can result in unpredictable behavior.

  • Page 46: Teaming Errors

    Ethernet network interface problems (CNAs only) Action: To determine link state, run the ifconfig command for Linux or VMware systems. For Windows systems, run ipconfig /all or use Settings > Network Connections. Action: For the interface to send and receive packets, both the UP and RUNNING flags must be set.

  • Page 47: Vlan Creation And Operation Problems

    Ethernet network interface problems (CNAs only) Note that you can still create teams even though these conflicts exist. However to avoid conflicts, make sure the following parameters match for all ports added to a team: • Header data split • Receive side scaling •...

  • Page 48: Teaming Or Vlan Operations Through Hcm Fail

    Ethernet network interface problems (CNAs only) 3. Symptom: Right-clicking on a VLAN device in Device Manager, then selecting Update does not work. Possible Cause: The upgrade option for Brocade 10 Gig Ethernet service is not available. Action: Uninstall and install the service. 4.

  • Page 49: Poor Network Performance

    Ethernet network interface problems (CNAs only) SYSTEM\Current\ControlSet\Control\Windows Poor network performance Poor network performance apparent for Windows and Linux systems. 1. Symptom: Checksum offloads are disabled. Action: For Windows, verify if checksum offload parameters are enabled using the Advanced tab on the Network Adapters > Properties dialog box in Device Manager. Action: For Linux, run the ethtool -k <interface ID>...

  • Page 50: Fcoe And Fibre Channel Problems

    FCoE and Fibre Channel problems FCoE and Fibre Channel problems This section provides resolution of problems related to Fibre Channel and FCoE (CNAs only). Loss of sync and loss of signal errors in port statistics If the port is having loss of synchronization and signal errors, refer to the following descriptions of possible causes and recommended actions to help resolve the problem.

  • Page 51: Virtual Devices Not Listed In Name Server

    FCoE and Fibre Channel problems • If fabric offline counts increase and fabric maintenance is not occurring, this may indicate a serious fabric problem. Refer to your switch troubleshooting guide to isolate and resolve the problem. Virtual devices not listed in name server If virtual devices are not listed in the fabric’s name server, refer to the following descriptions of possible causes and recommended actions to help resolve the problem.

  • Page 52: I/O Problem On Connected Fcoe Device (Cnas Only)

    FCoE and Fibre Channel problems 2. Possible Cause: The FCoE license may not be installed on the connected switch. Action: Execute the Fabric OS licenseshow command on the connected switch to determine if the license is installed. Install license if not installed. For more information about Fabric OS commands and QoS support, refer to the Fabric OS Administrator’s Guide.

  • Page 53: Disk I/O Requests Cause Low Throughput And High Latency On Linux34

    FCoE and Fibre Channel problems Action: Configure PFC using the appropriate Fabric OS command on the attached switch while in switch configuration mode. 3. Possible Cause: Zoning is configured incorrectly on FCoE switch. Action: Verify zoning configuration on the attached switch using the appropriate Fabric OS command.

  • Page 54: Cee Network Problems (Cnas Only)

    CEE network problems (CNAs only) CEE network problems (CNAs only) This section provides information to resolve problems of CNA operation on the converged enhanced Ethernet (CEE) network. CEE is not enabled The CEE state does not show “CEE Linkup” when you run the BCU port --query command. 1.
  • Page 55 HCM and HCM Agent problems 1. Possible Cause: If the hcmagent process exited in VMware ESX 3.5 or 4.0, the HCM Agent may be configured to forward events to a remote Syslog host, but the outgoing UDP port 514 is blocked by the ESX firewall.
  • Page 56 HCM and HCM Agent problems NOTE You can change the default communication port (34568) for the agent using procedures in the “Software Installation” chapter in the Brocade Adapters Installation and Reference Manual under “HCM Agent Operations.” If HCM is still unable to connect to the HCM Agent after using the preceding steps, collect the following data and send to your Support representative for analysis: •...

  • Page 57: Unable To Completely Uninstall Hcm

    HCM and HCM Agent problems If you are managing a Windows 2008 host system through HCM from a remote system, the host’s firewall may be blocking TCP/IP port 34568. NOTE Use Windows Firewall and Advanced Service (WFAS) to open port 34568. NOTE You can change the default communication port (34568) for the agent using procedures in the Brocade Adapters Installation and Reference Manual.

  • Page 58: Time On Hcm Screens Does Not Match System Time

    Verifying Fibre Channel and CEE links (stand-up adapters) Method 2 1. Enter the following at the command prompt: Javaws -uninstall This installs all applications in the Java cache. Time on HCM screens does not match system time The time display on HCM screens, such as on the main HCM window and statistics dialog boxes, show time relative to GMT instead of the host system time zone.

  • Page 59: Adapter Driver Installation Verification

    Adapter driver installation verification • Cables that are not rated or compatible with adapter port speeds. Refer to cable specifications in the Brocade Adapters Installation and Reference Manual. • Faulty switch or adapter SFPs. Verify if an SFP is the problem by connecting a different link to the adapter port or, if convenient, replace the cable with a cable of known quality.

  • Page 60: Confirming Driver Package Installation With Hcm

    Adapter driver installation verification TABLE 4 Installation and Reference Manual references (continued) Information Chapter Hardware and software installation instructions. Installation Product specifications. Specifications Adapter driver packages from Brocade contain the current driver, firmware, and HCM Agent for specific operating systems. Make sure that the correct package is installed for your operating system.

  • Page 61: Confirming Driver Package Installation In Linux Systems

    This utility displays information about all PCI buses in the system and all devices connected to them. Fibre Channel: Brocade Communications Systems, Inc. displays for an HBA. Fibre Channel: Brocade Communications Systems, Inc. and Ethernet Controller display for a CNA if driver packages have correctly loaded.

  • Page 62: Confirming Driver Package Installation In Solaris Systems

    Adapter driver installation verification Confirming driver package installation in Solaris systems Verify if the adapter driver installed successfully using the following commands: NOTE These commands are not applicable for Brocade 804 adapters. • pkgchk -nv bfa This checks for and lists the installed adapter storage driver package files. •...

  • Page 63: Troubleshooting Mezzanine Card Problems

    Troubleshooting mezzanine card problems • lspci This utility displays information about all PCI buses in the system and all devices connected to them. Brocade Communications Fibre Channel displays for an HBA. Brocade Communications Fibre Channel and Ethernet Controller display for a CNA if driver packages have correctly loaded.
  • Page 64 Additional references for isolating problems • Fabric OS Troubleshooting and Diagnostic Guide. Provides help with isolating problems in other Brocade SAN components. • Your host’s operating system documentation and help system. Provides details on commands for gathering information and isolating problems. Brocade Adapters Troubleshooting Guide 53-1001582-01...

  • Page 65: Tools For Collecting Data

    Chapter Tools for Collecting Data In this chapter • For detailed information ......... 45 •...

  • Page 66: Data To Provide Support

    Data to provide support • Fabric OS Troubleshooting and Diagnostics Guide This guide provides detailed information on collecting troubleshooting information and isolating general SAN problems between the Brocade switch, host systems, and storage systems. • Fabric OS Command Reference Manual Fabric OS diagnostic and monitoring commands for Brocade switches.
  • Page 67 Data collection using host system commands TABLE 5 Host system data collection commands (continued) Task Linux Windows VMware Solaris Displaying memory usage top, vmstat -m Windows Task Manager, top, vmstat -m vmstat -s tasklist.exe Monitoring performance iostat, vmstat, sar Windows Task Manager, vmstat, VM Performance: iostat -nx 1 5, vmstat, perfmon.exe...

  • Page 68: Data Collection Using Bcu Commands And Hcm

    Data collection using BCU commands and HCM TABLE 5 Host system data collection commands (continued) Task Linux Windows VMware Solaris • Locating BNA device file /dev/bna* Windows Registry /dev/bna* (Release 1.0) - (HKEY_LOCAL_MACHINE /devices/pci*/pci*/ \HARDWARE\DEVICEMA fibre-channel@0:dev P\Scsi\Scsi Port x) ctl, •...
  • Page 69 Data collection using BCU commands and HCM Launching Support Save through BCU, DCFM, and during a port crash event collects the following information: • Adapter model and serial number • Adapter firmware version • Host model and hardware revision • All support information •...
  • Page 70 Data collection using BCU commands and HCM ioc_auto_recover=0 Initiating Support Save through HCM Launching the Support Save feature in HCM collects HCM application data. Initiate Support Save by selecting Tool > Support Save. Messages display during the Support Save operation that provide the location of the directory where data is saved.
  • Page 71 Data collection using BCU commands and HCM • The /tmp directory on Linux and Solaris systems. • The current directory for Windows systems. Following are examples of other parameters you can use with this command: • bfa_supportsave <dir> - Creates and saves the supportsave data under a directory name that you provide.

  • Page 72: Collecting Adapter Data Using Hcm

    Data collection using BCU commands and HCM Support Save differences Following are differences in data collection for the HCM, BCU, and browser applications of bfa_supportsave: • BCU - Collects driver-related logs, HCM Agent information, and configuration files. • DCFM - Collects only driver-related logs and configuration files. •...

  • Page 73: Data Collection Using Fabric Os Commands (Brocade Switches Only)55

    Data collection using Fabric OS commands (Brocade switches only) To access the shell mode, type bcu shell. To exit out of shell mode, type exit. Use the BCU adapter command to list and query available adapters seen by the driver. The bcu adapter --list command lists all adapters on the system with a brief summary of information such as model number, serial number, and adapter number.

  • Page 74: Adapter Event Messages

    Adapter event messages Use this command without parameters to display all zone configuration information (both defined and enabled). • portErrShow Use this command to display an error summary for all switch ports. • portLogShow Use this command to display the port log for ports on a switch. •...
  • Page 75 Adapter event messages • Event category • Cause of event • Recommended action • Date and time event occurred NOTE For details of all driver event messages, refer to Appendix A, “Adapter BIOS and Event Message Reference”. Message details are also contained in HTML files, which load your system when you install the adapter driver.

  • Page 76: Logs

    Logs TABLE 7 Event message files Event Catalog File Content bfa_aen_rport.html Remote port (R_Port) events. hba_error_codes.doc List of error codes and meanings for the following events: • Adapter - events relating to the adapter • Physical port • L_Port - logical port •...

  • Page 77: Hcm Logs

    Logs Syslog support You can configure the HCM Agent to forward events to a maximum of three system log destinations using the Syslog option on the HCM Configure menu. These events will display in the operating system logs for systems such as Solaris and Linux. For procedures to configure syslog destinations, refer to the Brocade Adapters Administrator’s Guide.

  • Page 78: Logging Levels Adjustment

    Logs IP over FC - Events pertaining to IP over Fibre Channel. VLAN - Events pertaining to a virtual LAN. PORT - Events pertaining to a physical port. LPORT - Events pertaining to a specific logical port (one logical port always exists per physical port).
  • Page 79 Logs Port logging level Adjust logging level for port logs using BCU commands and HCM. Adjusting the port logging level through HCM Adjust port logging level through HCM using the following steps. 1. Select Configure > Basic Port Configuration from HCM. The Basic Port Configuration dialog box displays.

  • Page 80: Statistics

    Statistics <port_id> ID of port for which you want to change the logging level. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1 you would use 1/1 as the port identification.

  • Page 81: Authentication Statistics

    Statistics • VLAN This section provides an overview of these statistics and how to access them. For more detail, refer to the Brocade Adapter’s Adapters Administrator’s Guide. Authentication statistics Use BCU commands and HCM to display statistics related to transmitted and received DH-CHAP attempts for a selected port.

  • Page 82: Cee Statistics (Cnas Only)

    Statistics CEE statistics (CNAs only) Use BCU commands and HCM to display converged enhanced Ethernet (CEE) statistics, such as the following: • Logical link layer discovery protocol (LLDP) frames transmitted, received, timed out, discarded, with error, type-length-values (TLVs) discarded, and TLVs unrecognized. •...
  • Page 83 Statistics • Transmitted multicast frames • Transmitted multicast VLANs • Transmitted broadcast octets • Transmitted broadcast frames • Transmitted broadcast VLANs • Transmitted errors • Transmitted VLAN filters • Transmitted filter MAC source addresses • Received unicast octets • Received unicast frames •...

  • Page 84: Ethernet Ioc Statistics (Cnas Only)

    Statistics <port_ID> The ID of the Ethernet port. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1 you would use 1/1 as the port identification.

  • Page 85: Fcoe Statistics (Cnas Only)

    Statistics Displaying statistics through BCU Use the BCU ethioc command to display Ethernet input/output controller (IOC) statistics such as serial number, model, PWWN, NWWN, firmware version, operating status, vendor ID, IOC type, interrupt coalescing status, and interrupt delay value. ethioc --query <port_id> ethioc --stats <port_id>...

  • Page 86: Ioc Statistics

    Statistics • If the adapter is not showing in the fabric, check the FLOGI sent and FLOGI accept statistics. If the counts do not match, the switch or fabric may not be ready to respond. This is normal as long as it does not persist. If the problem persists, this could indicate a problem in the fabric or a protocol issue between the adapter and fabric.

  • Page 87: Fcp Initiator Mode Statistics

    Statistics Displaying IOC statistics through BCU Use the ioc command to display IOC statistics. ioc -–stats --query <ioc_id> where: stats Displays IOC statistics. query Displays IOC attributes. ioc_id ID of the IOC controller for which you want to display attributes. The ioc --query command displays such attributes as adapter serial number, model number, PWWN, firmware and BIOS version, vendor identification, IOC type, and interrupt coalescing status.

  • Page 88: Logical Port Statistics

    Statistics Displaying FCP IM module statistics through BCU Use the fcpim command to display FCP initiator mode (FCP IM) module statistics. bcu fcpim --modstats <port_id> where: modstats Displays FCP IM module statistics. port_id ID of the port for which you want to display statistics. This could be the PWWN, port hardware path, or user-specified port name.

  • Page 89: Port Statistics

    Statistics Displaying logical port statistics through HCM Display logical port statistics by selecting Monitor > Statistics > Logical Port Statistics. Right-click a logical port from the device tree and select Logical Port Statistics. Displaying logical port statistics through BCU Use the lport --stats command to display logical port statistics. lport –-stats <port_id>...

  • Page 90: Remote Port Statistics

    Statistics Displaying statistics through HCM Use the Port Statistics dialog box to monitor a variety of port data. Launch this dialog box using the following steps: 1. Launch the HCM. 2. Select the base adapter port from the device tree window. 3.

  • Page 91: Quality Of Service Statistics (Hbas Only)

    Statistics rpwwn Displays the remote port’s PWWN. Quality of Service statistics (HBAs only) Use HCM and BCU to display quality of service (QoS) statistics for individual ports. You can display statistics for fabric login (FLOGI) activity, exchange link parameter (ELP) activity, and received QOS registered state change notifications (RSCNs).

  • Page 92: Vlan Statistics (Cnas Only)

    Statistics Displaying virtual port statistics through BCU Use the vport --stats command to display statistics. vport --stats <port_id> vpwwn where: port_id ID of the port for which you want to display rport statistics. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index.

  • Page 93: Diagnostics

    Diagnostics Diagnostics Diagnostics, available through BCU commands and HCM, evaluate the integrity of adapter hardware and end-to-end connectivity in the fabric. All of these diagnostics can be used while the system is running. NOTE Be sure to disable the port before running any type of port diagnostics. NOTE It is advisable to not perform other operations on the adapter while running HCM or BCU diagnostics.

  • Page 94: Internal And External Loopback Tests

    Diagnostics port_id ID of the port for which you want to run a link beacon test. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1, you would use 1/1 as the port identification.

  • Page 95: Ethernet Port Loopback Test (Cnas Only)

    Diagnostics -p pattern Hex number. Default value is A5A5A5A5. Performing loopback tests through HCM Use the Hardware Tests tab on the Diagnostics dialog box to perform a loopback test. 1. Launch the HCM. 2. Select Configure > Diagnostics. 3. Click the Hardware Tests tab. 4.

  • Page 96: Pci Loopback Test

    Diagnostics Performing Ethernet loopback tests through BCU Use the ethdiag --loopback command to run an Ethernet loopback test. bcu ethdiag --loopback <port_id> [-t <loopback_type] [-c <frame_count>] [-p pattern] where: port_id ID of the port for which you want to run the test. This could be the PWWN, port hardware path, or user-specified port name.

  • Page 97: Memory Test

    Diagnostics 3. Click the Hardware Tests tab. 4. Select PCI Loopback Test. You can modify the following parameters: • Frame count: Specifies the frame count as an integer from 0 to 4,294,967,295. • Data pattern: Specifies the data test pattern. Must be at least one hexadecimal word. •...

  • Page 98: Adapter Temperature

    Diagnostics Issuing a ping command to end points through BCU Use the fcdiag --fcping BCU command to test the connection to a Fibre Channel end point. fcdiag -–fcping <port_id> <rpwwn> [-l lpwwn] where: port_id ID of the adapter port from which you want to ping the remote port. This could be the PWWN, port hardware path, or user-specified port name.

  • Page 99: Trace Route

    Diagnostics Performing a queue test through BCU Use the diag --queuetest command to perform a queue test. bcu diag --queuetest <port_id> [-q <queue_number> where: port_id Adapter port number. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1, you would use 1/1 as the port identification.

  • Page 100: Echo Test

    Diagnostics 3. Click the FC Protocol Tests tab. 4. Select FC Trace Route. 5. Select the adapter port and target for which you wish to trace the route. 6. Enter a test cycle if desired. Click Start. Echo test Use the BCU and HCM to initiate an echo test between the adapter port and a Fibre Channel end point.

  • Page 101: Scsi Test

    Collecting BIOS data SCSI test Use the fcdiag --scsitest BCU command to test the SCSI link between the adapter and remote port. fcdiag –-scsitest <port_id> <rpwwn> [-l lpwwn] where: port_id ID of the port for which you want to test the SCSI link. This could be the PWWN, port hardware path, or user-specified port name.

  • Page 102: Collecting Lldp Data (Cnas Only)

    Collecting LLDP data (CNAs only) The Basic Port Configuration dialog box displays. 3. Click the Boot-over-SAN tab. The Boot over SAN dialog box displays. Collecting LLDP data (CNAs only) Collect information on the Link Layer Discovery Protocol (LLDP) associated with a specific CNA using the HCM LLDP Properties panel.

  • Page 103: Predictive Optical Monitoring (Pom)

    Collecting port data Initiating SFP properties through HCM Launch the port SFP properties dialog box as follows to display properties for a selected small form-factor pluggable (SFP) transceiver. 1. Launch the HCM. 2. Select a port in the device tree. 3.

  • Page 104: Displaying Cee Port Properties (Cnas Only)

    Collecting port data Displaying CEE port properties (CNAs only) Use the CEE Port Properties panel to display information for a selected converged Ethernet (CEE) adapter port. Information such as the following displays: • CEE port status • FCoE logical link status •...

  • Page 105: Displaying Fcoe Port Properties

    Collecting port data • Supported class • FC frame size • Maximum transmission unit (MTU) • Target rate limiting (TRL) enabled or disabled status • Default rate limit • Beaconing status • Fibre Channel Initialization Protocol (FCIP) online or offline state •...

  • Page 106: Displaying Logical Port Properties

    Collecting port data Displaying logical port properties Use the HCM LPorts Properties panel to display properties associated with a logical port, such as port and node WWN, Fibre Channel address, online or offline state, and name server activity. To display logical port properties, use the following steps. 1.

  • Page 107: Performing A Port Query

    Collecting teaming information (CNAs only) Performing a port query Use port --query BCU command to display information, such as port name, state, current and configured speed, topology, media type, received and transmitted BB_Credits, beacon status, QoS priority status, QoS flow identification, port binding status, beaconing status, target rate limiting (TRL) status, and TRL default speed.

  • Page 108: Displaying Configured Team Data Through Bcu

    Authentication settings 3. Select a team from the Teams list to display properties for the team. 4. Click the Statistics button beneath the Teams field to display statistics for the selected team. Display teaming statistics for all configured teams using the following steps. 1.

  • Page 109: Displaying Authentication Settings Through Bcu

    QoS settings (HBAs only) Displaying authentication settings through BCU Use the BCU auth --show command to display authentication settings. auth --show <port_id> where: port_id ID of the port for which you want to display authentication settings. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index.

  • Page 110: Target Rate Limiting Settings

    Target rate limiting settings The Port Properties panel displays • Use the Remote Port Properties panel in HCM to display information on QoS for the remote port. 1. From the device tree, select a remote port (target or initiator). 2. Click the Remote Port Properties tab in the right pane. The Remote Port Properties panel displays.

  • Page 111: Determining Settings Through Hcm

    Persistent binding Determining settings through HCM Launch the Remote Port Properties panel in HCM as follows to display information on target rate limiting and QoS for the remote port. 1. From the device tree, select a remote port (target or initiator). 2.
  • Page 112 Persistent binding Brocade Adapters Troubleshooting Guide 53-1001582-01...

  • Page 113: Chapter 4 Performance Optimization

    Chapter Performance Optimization In this chapter • Tuning storage drivers ......... . . 93 •...

  • Page 114: Solaris Tuning

    Tuning storage drivers Solaris tuning To increase I/O transfer performance, set the following parameters on your system: • Set the maximum device read/write directive (maxphy). • Set the disk maximum transfer parameter (ssd_max_xfer_size). Please refer to the Sun StorageTek SAM File System Configuration and Administration Guide document for details of the two parameters.”...

  • Page 115: Vmware Tuning

    Tuning network drivers (CNAs only) • Interrupt latency Default: 225 microseconds on the Brocade 415, 425, 815, and 825 5 microseconds on the Brocade 804,, 1010, and 1020 Valid Range: 0 through 225 microseconds Note that the value of 0 disables the latency monitor timeout interrupt. Message signaled interrupts (MSI-X) All Brocade adapters support MSI-X, an eXtended version of the MSI defined in PCI 3.0 specification.

  • Page 116: Windows Tuning

    Tuning network drivers (CNAs only) Windows tuning All Windows tunable parameters for the network driver are optimized for best performance using default values. For details on parameters in the following table, refer to the “Adapter Configuration” chapter in the Brocade Adapters Installation and Reference Manual. Table 9 provides default parameters for Windows tunable parameters.

  • Page 117: Linux Tuning

    Tuning network drivers (CNAs only) Linux tuning All Linux tunable parameters for the network driver are optimized for best performance using default values. For details on configuring the parameters in the following table, refer to the “Adapter Configuration” chapter in the Brocade Adapters Installation and Reference Manual. Table 10 provides default values for all Linux tunable parameters.
  • Page 118 Tuning network drivers (CNAs only) Jumbo packet size Recommendations to enhance performance Increase throughput by setting MTU to 9000 bytes. How to change values Refer to instructions for Windows “network driver parameters” in Appendix A of the Brocade Adapters Installation and Reference Manual. References for more tuning information Refer to the 10Gbps Networking Performance on ESX 3.5 Update 1 available through www.vmware.com.

  • Page 119: Appendix A Adapter Bios And Event Message Reference

    Appendix Adapter BIOS and Event Message Reference This appendix provides details on BIOS messages that display during operation of option ROM and event messages that display during operation of adapter drivers. Included in these details are the message, cause, and action the user should perform after viewing these messages. Adapter BIOS messages Table 12 provides details on BIOS-related messages generated during operation of option ROM.

  • Page 120: Adapter Driver Event Messages

    Adapter driver event messages TABLE 12 Adapter BIOS messages (continued) Message Cause Recommended Action Failed:<Disk: PWWN<Target's PWWN> This adapter is unable to connect to the Check the zoning information on the switch LUN<LUN Id>. Adapter<no> configured boot device. This error message is and verify if the target's WWN is in the displayed only when boot option is set to Flash same zone as the initiator's WWN.
  • Page 121 Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Cause Action Category Base port link is disabled: Hardware Warning Network driver Disabled Ethernet port No action Address = [Base port MAC]. (EthPort) disabled by the required.
  • Page 122 Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Cause Action Category Remote port (WWN = [remote port Information Storage driver 4 (RPORT) Offline Login nexus with No action WWN]) offlined by logical port (WWN remote port required.
  • Page 123 Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Cause Action Category Authentication unsuccessful for base Error Network and 2 (Port) Failure Authentication Mismatch of port: WWN = [base port WWN or storage driver failure.
  • Page 124 Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Cause Action Category SFP removed: port [base port Warning Network and 2 (Port) Removed SFP removed. Check if SFP is number], Hardware Address = [base storage driver inserted properly.

  • Page 125: Hcm And Installer Message Reference

    Appendix HCM and Installer Message Reference This appendix provides details on messages that display during operation of the Host Connectivity Manager (HCM) and Brocade Adapter Software Installer program. The following tables in this appendix provide reasons why these messages display and actions that you should take to resolve any problems associated with the messages: •...
  • Page 126 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Failed to restore the Occurs when there is VLAN/Teaming The VLAN and Teaming VLAN and Team configuration file is not present to restore when configuration save will only occur configurations.
  • Page 127 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes You are going to stop the This occurs when the user stops a diagnostics Information message. pending test(s) only. test before it finishes. All Started test(s) will continue to run.
  • Page 128 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Choose any of the event Occurs when the user selects an event severity Select at least one severity level severity levels to filter. level, and then clicks OK in the Master Log (such as major or minor), and then Filter dialog box.
  • Page 129 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes <WWN> is an invalid Occurs when the user adds a invalid WWN (for Add a valid WWN or MAC address in WWN or MAC example, 00:00:00:00:00:00:00:00) or invalid the Detached WWN/MAC field or MAC address (for example,...
  • Page 130 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Port <WWN> parameters Occurs when user makes configuration Information message. update succeeded. Note: changes and clicks Apply to save the Setting will be enforced configurations.
  • Page 131 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes VLAN and Team Occurs when the VLAN and Team Information message. configurations configurations are successfully restored in successfully restored. HCM. Failed to restore the Occurs when the restore of VLAN and Team Retry the operation.
  • Page 132 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Team name should start Occurs when the user provides an invalid team Make sure the team name starts with an alphabet. name. with a letter.
  • Page 133 HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Please select a VLAN. Occurs when the user clicks on Remove in the Select at least one VLAN row to VLAN Configuration dialog box without remove.
  • Page 134 HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages Message Cause Corrective Action or Notes Please note that your system is Windows 2003 x86 Occurs when you install Upgrade SP1 to SP2, and Service Pack 1. the driver on a Windows then try installing the 2003 x86 SP1 system driver.
  • Page 135 HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes No matching binary rpm found Occurs when a matching Click Yes to proceed with binary rpm is not found. the installation using the Do you want to install noarch rpm? noarch rpm or click No to Note:...
  • Page 136 HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes Found Backed up data. Occurs during the course If the user wishes to of installation when a restore the backed-up backup data is already data, the user can give Backed up configuration directory of HCM present in the system...
  • Page 137 HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes Path is not Valid. Occurs if provide an Enter a valid path to invalid path name or backup the files. leave the path field blank. You have entered an invalid backup output directory.
  • Page 138 HCM and Installer Message Reference Brocade Adapters Troubleshooting Guide 53-1001582-01...
  • Page 139 Index BIOS boot problems adapter BIOS not installed displays boot from SAN stops on HP hosts adapter cannot boot from CNA BIOS not installed message CTL-B option does not display when booting diagnostics driver and operating system install failure event message files LUN not visible from host IP address lost no target devices found or link down...
  • Page 140 diagnostics Ethernet link ports or LOM not coming up adapter Ethernet loopback tests beaconing enabling through BCU enabling through BCU enabling through HCM enabling through HCM Ethernet network interface problems echo test Ethernet port logging levels enabling through BCU Ethernet statistics enabling through HCM event logging levels Ethernet loopback tests...
  • Page 141 Linux network driver tuning fabric OS support Linux problem host support errors when installing driver package operating system support loss of adapter hardware address PWWN xvii loss of adapter IP address serial number xvii low throughput and high latency storage support poor network performance supported models Linux storage driver tuning...
  • Page 142 problem adapter not registering with name server network stack runs out of heap not reported under PCI subsystem NIC numbering on VMware unexpected not showing in fabric no adapters reported adapter BIOS not installed message adapter loses IP address BCU version mismatch boot from SAN stops on HP hosts cannot from CNA operating system errors...
  • Page 143 product information resources statistics properties for SFPs authentication displaying through BCU properties panel for HBA displaying through HCM publication references Ethernet Ethernet IOC fabric displaying through BCU QoS performance issues displaying through HCM QoS statistics FCIP IM module displaying through BCU displaying through BCU displaying through HCM displaying through HCM...
  • Page 144 VMware problem low throughput and high latency network stack runs out of heap target not visible from remote host NIC numbering unexpected target rate limiting settings VMware tuning target statistics team --list command team --query command teaming Configuration dialog box teaming errors Windows network driver tuning teaming information...

This manual is also suitable for:

Hba 415Cna 1020Hba 425Hba 804Hba 815Hba 825

Table of Contents