53-1002145-01 5 August 2011 Brocade Adapters Troubleshooting Guide Supporting CNA models 1741, 1020, 1010, 1007 Supporting HBA models 825, 815, 804, 425, 415 Supporting Fabric Adapter model 1860 ®
Copyright © 2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Brocade Adapters Troubleshooting Guide 53-1002145-01 iii
iv Brocade Adapters Troubleshooting Guide 53-1002145-01
Table of Contents About this Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Supported adapter hardware and software. . . . . . . . . . . . . . . . xii Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii CNAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General adapter problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Adapter not reported under server’s PCI subsystem. . . . . . . . . . 9 No adapters reported though BCU adapter --list command . . . 10 Port link is not active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Device drivers not loading for all adapter instances . . . . . . . . . 11 Installer program does not autorun . . . . . . . . . . . . . . . . . . . . . .
Network interface problems (CNA or NIC) . . . . . . . . . . . . . . . . . . . . . 32 Ethernet loopback test problems . . . . . . . . . . . . . . . . . . . . . . . . 32 Ethernet link ports or LOM not coming up on reboot in Linux . 33 Loss of adapter hardware address in Linux . . . . . . . . . . . . . . . . 33 Loss of adapter IP address in Linux . . . . . . . . . . . . . . . . . . . . . . 33 Network stack runs out of heap . . . . . . . . . . . . . . . . . . . . . . . . .
Additional references for isolating problems. . . . . . . . . . . . . . . . . . . 56 Chapter 3 Tools for Collecting Data In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 For detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Data to provide technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Data collection using host system commands . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Beaconing (stand-up adapters). . . . . . . . . . . . . . . . . . . . . . . . . . 89 Internal and external loopback tests . . . . . . . . . . . . . . . . . . . . . 90 Ethernet port loopback test (CNA) . . . . . . . . . . . . . . . . . . . . . . . 91 PCI loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Memory test . . . . . . . . . . . . . . . . . . . . . . . . . .
Persistent binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Displaying Persistent Binding settings through BCU . . . . . . . .109 Displaying Persistent Binding settings through HCM . . . . . . .109 Adapter properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 CNA Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 HBA Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Host operating system support for adapter drivers . . . . . . . . . . . . . . . . . . . xiv • Host operating system support for HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii • Document conventions . . . . . . . . . . . . . . . . . . . . . . .
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 adapter hardware and software This section provides an overview of Brocade adapter supported hardware and software. Fabric Adapters Brocade 1860 Fabric Adapter ports can be configured for CNA, NIC, or HBA operation using Brocade Command Utility (BCU) commands.
HBAs The following Fibre Channel host bus adapters (HBAs) are supported: • 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. • Brocade 804. Dual-port mezzanine HBA with a per-port maximum of 8 Gbps. This HBA installs on Hewlett Packard blade servers. • Brocade 815. Single-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps SFP+. • Brocade 825.
HBAs Brocade HBAs connect to Fibre Channel SANs through compatible fabric switches or connect directly to storage. For a current list of compatible switches, refer to the latest interoperability matrices on the adapters website at www.brocade.com/adapters. Host operating system support Refer to “Host operating system support for adapter drivers” for information on operating systems that support the Brocade Host Connectivity Manager (HCM), Brocade Command Line Utility (BCU), and adapter drivers.
• • • • • Windows Server Core for Windows 2008 (x86 and x64) Microsoft WinPE 3.0 for Windows 2008 (x86 and x64) Linux RHEL 4.9, 5.5, 5.6, 6.0, 6.1 SLES 10 and 11 (x86 and x64) Solaris 10 (x86, x64, and SPARC) NOTE Solaris is not supported on Brocade 804 or 1007 adapters. • VMware ESX Server 4.0, 4.1, 5.0 (x64) NOTE Drivers and BCU are supported on the VMware ESX platforms. HCM is supported only on the guest system on VMware. • Oracle Enterprise Linux (OEL) 5.6, 6.0 (x86 and x64), Oracle VM 3.
• • • • • • • Windows 2008 R2/SP1 (x64) Windows Server Core for Windows 2008 (x86 and x64) Windows 7 (x86 and x64) Microsoft WinPE 3.0 for Windows 2008 (x86 and x64) Linux RHEL 4.9, 5.5, 5.6, 6.0, 6.1 (x86 and x64) Linux SLES 10 and 11 (x86 and x64) Solaris 10 (x86, x64, and SPARC) NOTE Solaris is not supported on Brocade 804 or 1007 adapters. • Xen Hypervisor (x86 and x64) Refer to “Hypervisor support” on page xvi. • VMware ESX Server 4.0, 4.1, and 5.
NOTE HCM is a 32-bit application. To use HCM on Linux RHEL 6.0 x64 systems, you must install the x32-compatible libraries because they are not installed by default. • Linux SLES 10 and 11 (x86 and x64) • Solaris 11, except Open Solaris (x86, x64, and SPARC) • VMware ESX Server 4.0, 4.1, 5.0 (x64) NOTE HCM is not supported in ESXi systems. NOTE HCM is supported only on the guest operating system for VMware. • Oracle Enterprise Linux (OEL) 5.6, 6.
Document conventions This section describes text formatting conventions and important notice formats used in this document.
Notes, cautions, and warnings The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards. NOTE A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information. ATTENTION An Attention statement indicates potential damage to hardware or data.
Corporation Referenced Trademarks and Products Novell, Inc. SUSE Linux Enterprise Server (SLES) VMware, Inc. ESX Server SPARC International, Inc. SPARC Hewlett Packard Corp. BladeSystem IBM BladeCenter Dell PowerEdge Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. 1. Go to the adapters website at www.brocade.com/adapters. 2. Navigate to the adapters Downloads page. 3.
Blade servers and blade system enclosure components Brocade mezzanine and expansion card adapters 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 compatible 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.
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.
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 adapter port is assigned a MAC address during FCoE Initialization Protocol (FIP) operations. This MAC is assigned for the current FCoE communication only.
xxiv Brocade Adapters Troubleshooting Guide 53-1002145-01
Chapter Introduction to Troubleshooting 1 In this chapter • How to use this manual for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Gathering problem information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 How to use this manual for troubleshooting An adapter, such as an HBA, CNA, or Fabric Adapter is one component of a larger network consisting of switches, storage devices, host systems and the cabling and connections to these components.
1 How to use this manual for troubleshooting 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.
Gathering problem information 1 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.
1 Gathering problem information • 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.
Chapter 2 Isolating Problems In this chapter • How to use this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 • General adapter problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Fabric Adapter problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 • HBA problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 • CNA problems .
2 How to use this chapter TABLE 2 6 Isolate adapter problems (continued) Problem Category OS Specific “Host system freezes or crashes” “General adapter problems” All “Operating system errors (blue screen)” “General adapter problems” All “Driver event messages appearing in host system log files” “General adapter problems” All “BCU version mismatch warning” “General adapter problems” All “Errors or problems when entering BCU commands” “General adapter problems” All “bcu pcifn --list and
How to use this chapter TABLE 2 2 Isolate adapter problems (continued) Problem Category OS Specific “Installing Windows 2008 R2 DUD on UEFI system results in offline disk” “General adapter problems” “UEFI boot problems” Windows 2008 “Driver and operating system installation failure on boot LUN” “General adapter problems” “BIOS boot problems” All “Target not visible from host” “General adapter problems” “BIOS boot problems” Windows “Ctlr-B option does not display when booting host” “General
2 How to use this chapter TABLE 2 8 Isolate adapter problems (continued) Problem Category OS Specific “Ethernet link ports or LOM not coming up on reboot in Linux” “Network interface problems (CNA or NIC)” Linux “Loss of adapter hardware address in Linux” “Network interface problems (CNA or NIC)” Linux “Loss of adapter IP address in Linux” “Network interface problems (CNA or NIC)” Linux “Network stack runs out of heap” “Network interface problems (CNA or NIC)” VMware “NIC numbering unexp
General adapter problems TABLE 2 2 Isolate adapter problems (continued) Problem Category OS Specific “FCoE link is down” “FCoE and Fibre Channel problems” All “I/O problem on connected FCoE device” “FCoE and Fibre Channel problems” All “I/Os are not failing over immediately on path failure in MPIO setup” “FCoE and Fibre Channel problems” Windows Linux VMware “Disk I/O requests cause low throughput and high latency on Linux” “FCoE and Fibre Channel problems” Linux “Disk I/O requests cause
2 General adapter problems 3. 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. 4. Possible Cause: Adapter not compatible with host operating system or connected storage systems. Action: Verify compatibility by reviewing the Brocade interoperability matrices on the Brocade adapters website at www.brocade.com/adapters.
General adapter problems 2 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 or Fabric Adapter ports configured in HBA mode only). Action: Check the port topology setting on the switch using the Fabric OS portCfgShow command to ensure that Locked L_Port is OFF.
2 General adapter problems Action: Try rebooting the system to force a resource rebalance. If the problem persists, increase the system memory or disable some of the adapter instances. Installer program does not autorun On Windows systems, if the installer program does not automatically run from the DVD 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.
General adapter problems 2 NOTE Observe the LEDs on adapter ports (stand-up adapters only). Illuminated LEDs indicate connection, link activity, and connection speed negotiated with the attached device. For the meaning of LED operation, refer to the Brocade Adapters Installation and Reference Manual. • If the system freezes perform the following tasks: a. Verify whether the host system firmware supports PCIe specifications listed in the Brocade Adapters Installation and Reference Manual.
2 General adapter problems BCU version mismatch warning Output from BCU commands has the following warning message. WARNING: BCU and Driver versions don’t match !!! Possible Cause: Installation may be incomplete. Either the BCU or one or more driver instances were not upgraded to the latest version. Action: Remove the driver package, then reinstall. Refer to the “Software Installation” chapter in the Brocade Adapters Installation and Reference Manual.
General adapter problems 2 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. Possible Cause: Ethernet traffic problem NOTE This applies to CNAs or Fabric Adapter ports configured in CNA mode. Action: Run the Ethernet loopback serdes test on the suspected Ethernet port using the BCU diag --ethloopback command.
2 General adapter problems C:\Program Files\BROCADE\Adapter\driver\util\hbaagent\log\ Host system running Microsoft Windows fails to hibernate A host system with Microsoft Windows and a Brocade adapter fails to go into hibernation mode with the following message: The following items are preventing hibernation on this system. The system does not support hibernation. The storage drivers do not support hibernation." Possible cause: Microsoft hotfix KB932755 has not been installed on the server.
General adapter problems 2 Driver installation fails and system cannot be booted Installation of a new Windows 2008 driver package fails in systems where an adapter is used for booting over SAN and the operating system becomes unbootable. Possible Cause: Existing driver package that was accessing the remote boot LUN was removed and system was rebooted. Action: Install the new adapter driver without uninstalling the existing driver. This is the recommended procedure for updating adapter drivers.
2 General adapter problems Action: Take the following actions: • Rescan for the devices in the Device Manager. • Ignore the error message. Files needed for bfad.sys message appears If a “Files needed for bfad.sys” message appears on Windows systems when removing a driver, refer to the following possible cause and recommended action to help resolve the problem. Possible Cause: A “Files needed for bfad.sys” message will occur if you perform the following sequence of steps. 1.
General adapter problems 2 1. Action: Reassess the hardware configuration and distribute the adapters so no more than four 10Gbps Ethernet ports are used in a single system (maximum supported by VMware). This VMware limitation applies to Brocade CNA ports and Fabric Adapter ports configured in CNA mode. 2. Action: If there are a large number of Brocade HBA ports or Fabric Adapter ports configured in HBA mode in the system, try disabling MSI-X mode for Brocade ports using the following commands. a.
2 General adapter problems Action: If you are installing the brocade_driver_linux_.tar.gz driver package, the driver module compiles on the system during installation. If driver build errors result when you install the package, verify that the appropriate distribution kernel development packages are installed on your host system for the currently running kernel. These packages should include the gcc compiler and the kernel sources.
General adapter problems 2 Action: If booting the host from a remote boot device, verify whether “boot over SAN” configuration is complete and correct. For example, verify the following: • A zone is created on the attached switch that contains only the PWWN of the storage system port for the boot LUN and the PWWN of the adapter port. • BIOS or EFI is enabled to support boot over SAN from a specific adapter port. • BIOS or EFI is configured to boot from a specific LUN.
2 General adapter problems “29” is the device handle, and will be different in most systems. More than one Brocade adapter may display. b. Use the EFI shell dh command to display additional information about each Brocade adapter. This will include any attached Fibre Channel disk devices.
General adapter problems 2 Driver preinstallation problems The following problems may occur when drivers are preinstalled to your Windows host system driver store. Preinstallation failed when attempted twice in a row without inserting adapters Preinstallation of drivers fail when attempted twice in a row and adapters are not inserted in the system. Possible Cause: Windows restricts upgrading a preinstalled driver before installing the hardware.
2 General adapter problems Target not visible from host If the storage target configured for containing the boot LUN is not visible from the host, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. 1. Possible Cause: No fabric connectivity between adapter and target or target is not online.
General adapter problems 2 No target devices found or link down message displays in Brocade BIOS Configuration menu “No target devices found or link down” message displays on Brocade BIOS configuration menu during boot device discovery. 1. Possible Cause: There is no fabric connectivity between the Brocade adapter and target, or the target is not online.
2 General adapter problems d. Download the dud from the “Driver Update Disks (DUDs)” area. 2. Possible Cause: Missing or improper storage array LUN mask setting. Action: Check LUN mapping and masking using the storage array configuration applications. 3. Possible Cause: Missing or improper storage array LUN mask setting. Action: Check LUN mapping and masking using storage array configuration tools. 4. Possible Cause: Adapter driver not loaded. Action: The adapter driver may not be loaded.
Fabric Adapter problems 2 NOTE Action: Refer to Hewlett Packard (HP) Customer Advisory Document c01199684 on the HP technical support website for detailed information. Adapter : BIOS not installed displays during boot process An “Adapter : BIOS not installed” message displays when booting from an adapter. Possible Cause: Either the boot image is not present in the adapter option ROM or initialization of the adapter failed for some reason. 1. Boot image is not present in the adapters.
2 HBA problems HCM not discovering all Ethernet ports for vNICs vNICs are created for adapter on Windows systems, but HCM is not discovering all related Ethernet ports. Possible Cause: Agent started before network driver came online to discover ports. Action: Restart Brocade HCM Agent Service from Windows Services window. HBA problems This section provides information for resolving problems more specific to functions of HBAs or Fabric Adapter ports configured in HBA mode.
HBA problems 2 Action: Enter the bcu qos --query command for the adapter port connected to the switch. If the QoS state is “Unknown” instead of “Online” and total BB-Credits is “zero,” licenses may not be installed. Verify if licenses are installed by executing the Fabric OS licenseshow command on the switch. Install licenses as required. For more information about Fabric OS commands and QoS support, refer to the Fabric OS Administrator’s Guide. 2.
2 HBA problems 3. Possible cause: Required licenses not installed on the connected switch. Action: Verify if licenses are installed by executing the Fabric OS licenseshow command on the switch. Install licenses as required Action: Install the following licenses on the switch if necessary. • Server Application Optimization (SAO) license • Trunking license NOTE The switch where the HBA or Fabric Adapter port configured in HBA mode connects must be running Fabric OS 4.6.1 or greater.
CNA problems 2 CNA problems This section provides information for resolving problems more specific to functions of CNAs or Fabric Adapter ports configured in CNA mode. For additional information on troubleshooting problems on mezzanine card and expansion card adapters, refer to “Troubleshooting mezzanine card problems” on page 55. Cannot manage CNAs after attempting upgrade to 3.0 drivers On Windows 2003 systems with both HBAs and CNAs installed, BCU and the HCM Agent cannot manage the CNA adapter.
2 Network interface problems (CNA or NIC) Network interface problems (CNA or NIC) Use the following information to isolate problems that are more specific to the function of a CNA or Fabric Adapter port configured in CNA or NIC mode. For additional information on troubleshooting problems on mezzanine and expansion card adapters, refer to “Troubleshooting mezzanine card problems” on page 55. NOTE Switch command examples used in this section are for the Brocade 8000 Switch.
Network interface problems (CNA or NIC) 2 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 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. Action: Make sure that a script is configured for each adapter and LOM once drivers are installed.
2 Network interface problems (CNA or NIC) 2. Possible Cause: The IP address is not configured in the ifcfg-ethX script. Action: Manually configure IP address in ifcfg-ethX script. 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.
Network interface problems (CNA or NIC) 2 • Administratively up, but link is down. Running the Linux or VMware ifconfig command shows that the RUNNING flag is not set. 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. Action: If pinging a server on a different network.
2 Network interface problems (CNA or NIC) Applications using TDI driver stop responding Applications that use the TDI driver for network traffic may stop responding on Windows Server 2008 and Windows Vista systems. Possible Cause: Windows hotfix KB2029048 is not installed. Action: Download and install hotfix KB2029048. This hotfix is optional.
Network interface problems (CNA or NIC) 2 NOTE For CNAs and Fabric Adapter ports configured in CNA or NIC mode, link speed is always 10 Gbps. You cannot change this parameter. You can view and change these parameters for each port using Windows Device Manager. 1. Run devmgmt.msc to open the Device Manager window. 2. Expand Network Adapters. An instance of the adapter model should display for each installed adapter port. 3.
2 Network interface problems (CNA or NIC) 5. Symptom: “Illegal Configuration - Remove Port VLAN” message displays when you use the bcu vlan --list command or list VLANs through HCM. Possible Cause: VLAN or Passthru VLAN was created with BCU commands or HCM and user has modified the PVID on the port with VLANs to a nonzero value. Action. Use Device Manager to modify the PVID on the port with VLANs to a zero (0) value.
Network interface problems (CNA or NIC) 2 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 command. If offload parameters are on, information similar to the following displays in the output.
2 Network interface problems (CNA or NIC) Possible Cause: When the BNI driver is upgraded, the current configuration is saved, the old driver is removed, and the new driver installed. If a team is created and bound to Hyper-V, the virtual adapter in the team is removed when the BNI driver is removed. Therefore, the upper edge of the virtual adapter created through the Hyper-V manager for virtual managers will not have any lower edge bindings.
FCoE and Fibre Channel problems 2 FCoE and Fibre Channel problems This section provides resolution of the following: • Fibre Channel problems on HBAs and Fabric Adapter ports configured in HBA mode. • FCoE problems on CNAs and Fabric Adapter ports configured in CNA mode. 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.
2 FCoE and Fibre Channel problems • If counts for FLOGI sent and FLOGI accept fabric statistics do not match, suspect fabric problem or protocol issue between adapter and fabric. • 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.
FCoE and Fibre Channel problems 2 FCoE link is down NOTE This issue applies to CNAs and Fabric Adapter ports configured in CNA mode only. The FCoE link is down between the adapter and switch. 1. Possible Cause: The FCoE link is not administratively enabled. Action: Determine if the link is enabled by entering the BCU port --list command. If the port is administratively disabled, the “port state” field will show Disabled. Action: Enable the port by entering the BCU port --enable command. 2.
2 FCoE and Fibre Channel problems Action: Verify if the PWWN or NWWN has a zero value using one of these methods: • Windows system log or Linux /var/log/messages file displays a port error indicating a zero PWWN or NWWN. • Output from bcu port --query command for the port shows zero value for PWWN or NWWN. • Advanced Management Module (AMM) Open Fabric Manager (OFM) status page displays an error status for the corresponding port of the blade.
DCB network problems 2 Disk I/O requests cause low throughput and high latency on Linux If a high number of I/O requests is causing low throughput and high latency on Linux systems, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: The maximum input/output operations per second are too low on Linux hosts. Action: Refer to “Linux tuning” on page 113 for suggestions to optimize adapter performance in Linux systems.
2 HCM and HCM Agent problems Action: Check FCoE switch configuration using the appropriate Fabric OS command on the attached switch. Refer to the Fabric OS Command Reference Manual for information. Change configuration as necessary using appropriate Fabric OS command on the attached switch. Refer to the Fabric OS Command Reference Manual for information. 3. Possible Cause: The front-end Ethernet port on the FCoE switch is not configured as “switchport” or is not set to converged mode.
HCM and HCM Agent problems 2 Action: For Linux, Solaris, and VMware systems, perform the following steps to help isolate the problem: a. Verify that the agent is running by executing the appropriate status command for your operating system as described in the “Software Installation” chapter in the Brocade Adapters Installation and Reference Manual under “HCM Agent Operations.” b. If you receive a message that the hcmagent is stopped, restarting the agent should resolve the problem.
2 HCM and HCM Agent problems • Data collected on the adapter host from the bfa_supportsave feature using the bfa_supportsave command. Output collects to a file and location specified when the SupportSave feature runs. Action: For Windows systems, perform the following steps on to help isolate the problem: a. Verify that the agent is running by executing the appropriate status command for your operating system described in the Brocade Adapters Installation and Reference Manual.
HCM and HCM Agent problems 2 • Files from the output directory created after you execute the support save feature. To collect these files, execute the BCU bfa_supportsave command. Support data is collected to a file in your system’s tmp directory by default. For more information on using the Support Save feature, refer to “Support Save” on page 61. • Support data from the HCM application SupportSave feature. • Build information for the HCM application.
2 Verifying Fibre Channel and DCB links (stand-up adapters) 2. Select Host Connectivity Manager, right click, and then select Delete from the menu. 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.
Adapter driver installation verification 2 Common link problems can be caused by the following: • Damaged cables. (Note that damaged cables can also cause errors and invalid data on links.) • 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.
2 Adapter driver installation verification TABLE 4 Installation and Reference Manual references Information Chapter Hardware and software compatibility information. Product Overview Software installation packages supported by host operating system and platforms. Product Overview Hardware and software installation instructions. Installation Product specifications.
Adapter driver installation verification 2 • For CNAs and Fabric Adapter ports configured in CNA or NIC mode, when you expand Network adapters, an instance of Brocade 10G Ethernet Adapter should also display for each port installed. For example, if two two-port CNAs (total of four ports) are installed, four instances of the adapter model display (two under SCSI and RAID controllers and two under Network adapters).
2 Adapter driver installation verification • These commands display the location of the driver modules if loaded to the system: - The following command displays the storage driver module location. The module will have a bfa prefix. # modprobe -l bfa - The following command displays the network driver module location. The module will have a bfa prefix.
Troubleshooting mezzanine card problems 2 • cat /proc/vmware/version This displays the latest versions of installed drivers. For storage drivers look for a bfa entry and related build number. For network drivers, look for a bna entry and related build number. • rpm -qa|grep -i bfa This command prints the names of the Brocade adapter storage driver package (bfa) if installed. • rpm -qa|grep -i bna This command prints the names of the Brocade adapter network driver package (bna) if installed.
2 Additional references for isolating problems Additional references for isolating problems Refer to the following publications and to chapters in this manual for gathering information to further isolate and resolve adapter problems.
Chapter Tools for Collecting Data 3 In this chapter • For detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 • Data to provide technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 • Data collection using host system commands . . . . . . . . . . . . . . . . . . . . . . . 59 • Data collection using BCU commands and HCM . . . . . . . . . . . . . . . . . . . . .
3 For detailed information For detailed information This chapter provides basic instruction on tools useful for gathering information to isolate adapterproblems. For more detailed information on using these tools, refer to the Brocade Adapters Administrator’s Guide.
Data collection using host system commands 3 Data collection using host system commands Table 5 describes commands common to each supported operating system that you can use to gather information for troubleshooting problems. For details on these commands, refer to your system’s online help and documentation. NOTE Output from all of these commands is captured using the Support Save feature.
3 TABLE 5 Data collection using host system commands Host system data collection commands (continued) Task Linux Windows VMware Solaris1 Locating system log messages dmesg, /var/log/message* System Category in Windows Event Viewer (eventvwr.exe) /var/log/vmkernel* /var/log/vmkwarning*/proc /vmware/log /var/log/message* dmesg, /var/adm/message* Showing operating system distribution info (SuSE) cat /etc/SuSE-release, (RedHat) cat /etc/redhat-release systeminfo.
Data collection using BCU commands and HCM 3 Data collection using BCU commands and HCM You can collect a variety of information on installed Brocade adapters, such as firmware version installed, operational status, port speed, WWN, PCI data, configuration data, flash status, and other details for troubleshooting using BCU commands, HCM menu options, Management applications, such as Network Advisor, and host operating system commands.
3 Data collection using BCU commands and HCM • • • • • • • • • Adapter configuration data Environment information Data .
Data collection using BCU commands and HCM 3 • For Windows, use the Registry Edit tool (regedt32) or the BCU drvconf --key command. Following is the drvconf ---key command. bcu drvconf --key ioc_auto_recover --val 0 • For Solaris, edit /kernel/drv/bfa.conf using the following. ioc_auto_recover=0 NOTE Brocade 804 and 1007 adapters are not supported on Solaris systems so Solaris commands do not apply to these adapters.
3 Data collection using BCU commands and HCM 3. Click View to view the repository in an Internet browser window. The technical support information displays in an Internet browser window. Initiating Support Save through BCU commands Launching the Support Save feature using the bfa_supportsave command collects information for the selected adapter. For information on entering BCU commands, refer to “Using BCU commands” on page 65.
Data collection using BCU commands and HCM 3 4. Save the file, but rename with a “zip” extension. For example, supportSaveController.zip. 5. Open the file and extract contents using any compression utility program. Initiating Support Save through a port crash event If the port crashes and triggers a port crash event, Support Save data is collected at a system-wide level. An Application Log message is generated with the following message.
3 Data collection using Fabric OS commands (Brocade switches only) VMware ESX 5.0 and later systems For VMware ESX 5.0 and later systems, BCU commands are integrated with the esxcli infrastructure. To run a BCU command, use the following syntax: esxcli brocade bcu --command=”command” where: command BCU command, such as port --list.
Adapter event messages 3 • portLogShowPort Use this command to display the port log for a specified switch port. • portPerfShow Use this command to display throughput information for all ports on the switch. • portStatsShow Use this command to display hardware statistics counters for a specific switch port. • portShow Use this command to display information and status of a specified switch port, including the speed, ID, operating state, type, and WWN.
3 Adapter event messages • 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. You can view these HTML files using any internet browser application. Table 6 provides the default location where these message files install for each supported operating system.
Logs 3 NOTE Complete content for adapter driver event messages is included in Appendix A, “Adapter BIOS and Event Message Reference”. Logs Event and error messages that occur during adapter, driver, and HCM operation are important tools for isolating and resolving problems. These messages provide descriptions of an event or problem, severity, time and date of the event, and in some cases, cause and recommended actions.
3 Logs HCM logs You can view data about adapter operation through HCM logs that display in HCM. These logs display on the bottom of the HCM main window. Click the Master Log or Application Log to toggle between the following logs: • The Master Log displays informational and error messages during adapter operation. This log contains the severity level, event description, date and time of event, and the function that reported the event (such as a specific adapter port or remote target port).
Logs 3 • Event description, Date, and Time Brief description of event and date and the time when the event occurred. NOTE Complete content of adapter event messages is provided in Appendix A, “Adapter BIOS and Event Message Reference”. You can block events from displaying in the Master Log by severity, category, and WWN of adapter using the Master Log Filter dialog box. To display this dialog box, click the Filter button in the Master Log section of the main HCM screen.
3 Logs Click Apply to apply the changes. 4. Click OK to save the changes and close the window. Use the following steps to adjust port logging level for Fabric Adapter ports configured in NIC mode. 1. Select an Ethernet port from the device tree. 2. Select Configure > Eth Configuration. The Eth Configuration dialog box displays. 3. Select a value from the Port Logging Level list. Supported values are Log Critical, Log Error, Log Warning, and Log Info. 4. Click OK to save the changes and close the window.
Statistics 3 Statistics You can access a variety of statistics using BCU commands and HCM. Use these statistics to monitor adapter performance and traffic between the adapter and LUNs and isolate areas that impact performance and device login.
3 Statistics • The number of times a transmitted Fibre Channel authentication attempt was successful (Tx DHCHAP Successes) • • • • • • The number of rejected received Fibre Channel authentication attempts (Rx Auth Rjts) The number of received Fibre Channel authentication negotiation attempts (Rx Auth Negs) The number of completed received Fibre Channel authentication attempts (Rx Auth Dones) The number of received DH-CHAP challenge attempts (Rx DHCHAP Challenges) The number of received DH-CHAP replies (
Statistics 3 Displaying statistics through BCU Use the following BCU command to display DCB statistics. bcu dcb --stats where: 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. Displaying statistics through HCM Display the DCB Statistics dialog box using the following steps. 1.
3 Statistics Displaying FCoE statistics through BCU Use the fcoe --stats command to display FCoE statistics. fcoe -–stats where: port_id ID of the adapter port for which you want to display statistics. 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.
Statistics 3 Displaying fabric statistics through HCM Use the Fabric Statistics dialog box to monitor a variety of port data. 1. Launch the HCM. 2. Select the FC port from the device tree window. 3. Click Monitor > Statistics > Fabric Statistics. Displaying FCP initiator mode statistics Use the fcpim --stats command to display FCP initiator mode statistics and attributes. fcpim --stats [-l where: stats Displays FCP initiator mode statistics.
3 Statistics NOTE Enabling profiling will impact I/O performance, so use this command to analyze traffic patterns and not in production systems. Use the following command to enable profiling. fcpim --profile_on Use the following command to disable profiling. fcpim --profile_off where: port_id ID of the port for which you want to enable or disable profiling. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index.
Statistics 3 I/O performance Use the fcpim -ioperf command to display I/O performance in terms of IOPs and throughput for physical ports and I-T nexus (ITN) sessions for a logical port. Use the command with a physical port range or with a specific physical port ID. Using port range The following command displays IOPs and throughput for a range of physical ports. --ioperf [-l | -r] [-c count] [-i interval] where: port_range This is the adapter number/port number-adapter number/port number.
3 Statistics Logical port statistics Use HCM and BCU to display logical port statistics for the following: • • • • • • • • • • • • • • • • • • • Discover address (ADISC) Name server (NS) port logins (plogin) activity NS port response activity NS command activity Register symbolic port name (RSPN_ID) identifier activity Register FC4 type identifier (RFT_ID) activity Register FC4 type identifier (RFT_ID) activity “Get all port ID requests” for a given FC4 type (NS_GID_FT) activity Port logout (LOGO) MS co
Statistics 3 Displaying logical port statistics through BCU Use the lport --stats command to display logical port statistics. lport –-stats [-l ] where: 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. 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.
3 Statistics where: ID of port for which you want to display statistics. 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. Port Performance Use the BCU port --perf command to display throughput information, in number of bytes received and transmitted, for a specific physical port.
Statistics 3 Displaying statistics through BCU Use the port --stats BCU command to display statistics for a specified adapter port. port --stats where: 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. 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.
3 Statistics 3. Select the type of statistics that you want to run from the Statistics Name list. 4. Select the polling interval. 5. Click Apply to save your changes. To display the Historical Performance dialog box and graphs for a port, use the following steps. 1. Select a device for which you want to generate a historical performance graph. 2. Select Monitor > Performance. 3. Select the Enable Historical Data Collection check box to display the Historical Performance dialog box. 4.
Statistics 3 Displaying remote port statistics through BCU Use the rport --stats command to display remote port statistics. rport –-stats [-l ] 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. For example, to specify adapter 1, port 1 you would use 1/1 as the port identification. lpwwn Displays the logical PWWN.
3 Statistics vHBA statistics Display vHBA statistics on HBAs, CNAs, or Fabric Adapter ports configured in HBA or CNA mode. Use HCM and BCU to display statistics related to virtual host bus adapters (vHBA) associated with an FC or FCoE port.
Statistics • • • • • • • • • • 3 Heartbeat failures Firmware boots vNIC statistics timeouts Disable and enable requests Disable and enable replies Link toggle count CEE toggle count BPC statistics RAD statistics Ethernet ICO statistic timeouts You can also select options to keep running data, set the polling frequency, start polling data, and reset statistics. Displaying statistics through HCM To display statistics, perform the following steps: 1. Launch the HCM. 2.
3 Statistics Displaying virtual port statistics through HCM Display statistics by selecting Monitor > Statistics > Virtual Port Statistics. OR Right-click a virtual port on the device tree and select Virtual Port Statistics. Displaying virtual port statistics through BCU Use the vport --stats command to display statistics. vport --stats where: port_id ID of the port for which you want to display virtual rport statistics.
Diagnostics 3 VLAN statistics for a port (CNA and NIC) Use the BCU ethport command to display VLAN statistics for a specific port, such as transmit and receive bytes, duration, and status. ethport --vlanquery where: pcifn Specifies the PCIFN function number related to the port. vlan_id Specifies the VLAN identifier. The range for the VLAN ID is 1 to 4094.
3 Diagnostics Use the fcdiag --linkbeacon command to enable end-to-end beaconing. fcdiag --linkbeacon {on | off} where: 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. on | off Toggle on or off. If turned on, you can specify duration.
Diagnostics 3 speed For HBAs and Fabric Adapter ports configured in HBA mode only. For a 4 Gbps port, this is 2 or 4. For an 8 Gbps port, this is 2, 4, or 8. For a 16 Gbps port, this is 4, 8, or 16. frame count Integer from 0 to 4,294,967,295. Default is 8192. -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.
3 Diagnostics Performing Ethernet loopback tests through BCU Refer to “Performing loopback tests through BCU” on page 90. PCI loopback test Use BCU commands or HCM to perform a PCI loopback test for a specific port. In this test, a data pattern is sent from the host to adapter firmware through the PCI bus. The returned data is validated to determine PCI operation. NOTE You must disable the port before you run loopback tests.
Diagnostics 3 Memory test Use the BCU or the HCM to perform a memory test for the adapter. NOTE Performing the memory test disables the adapter. Performing a memory test through BCU Use the diag --memtest command to test the adapter’s memory blocks. diag --memtest where: ad_id ID of the adapter. Performing a memory test through HCM Use the Hardware Tests tab on the Diagnostics dialog box as follows to perform a memory test. 1. Launch the HCM. 2. Select Configure > Diagnostics. 3.
3 Diagnostics Issuing a ping command to end points through HCM Use the FC Protocol Tests tab on the Diagnostics dialog box to test the connection to Fibre Channel end points. Use the following steps to ping end points. 1. Launch the HCM. 2. Select Configure > Diagnostics to display the Diagnostics dialog box. 3. Click the FC Protocol Tests tab. 4. Select FC Ping Test. 5. Select the adapter port and target that you wish to ping. 6. Enter a test cycle if applicable. 7. Click Start.
Diagnostics 3 4. Select Queue Test. 5. Click Start. SCSI test Use the fcdiag --scsitest command to test SCSI components and display discovered LUN information, such as LUN number, device type and qualifier, vendor ID, product ID, revision number, size of LUN, and LUN status. fcdiag -–scsitest [-l ] where: port_id ID of the port from that you want to test. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index.
3 Diagnostics 6. Enter a test cycle if desired. 7. Click Start. Echo test Use the BCU and HCM to initiate an echo test between the adapter port and a Fibre Channel end point. This sends an ECHO command and response sequence between the adapter port and target port to verify connection with the target. Performing an echo test through BCU Use the fcdiag --fcecho BCU command to initiate an echo test between the adapter and remote port.
Collecting BIOS data 3 Collecting BIOS data Collect information on the currently configured BIOS and boot over SAN configuration using the BCU and HCM. Displaying BIOS data through BCU Use the bios --query BCU command to display such information as the boot over SAN enabled or disabled state, port speed, boot LUNs obtained from flash, and boot LUNs obtained from the fabric (only if automatic discovery of boot LUNs from the fabric is enabled).
3 Collecting SFP data (stand-up adapters) Collecting SFP data (stand-up adapters) This section provides an overview of BCU commands and HCM features that provide information on small form factor pluggable (SFP) transceivers. SFP properties BCU and HCM provide detailed information on the SFP transceiver for a selected port, such as its health status, port speed, connector type, minimum and maximum distance, as well as details on the extended link.
Collecting port data 3 Collecting port data This section provides an overview of BCU commands and HCM features that provide information on adapter ports. such as PWWN, node WWN, port type, configured speed, operating speed, configured topology, operating topology. link and port beaconing state, and other information.
3 Collecting port data • FCoE quality of service that specifies a priority value To display DCB port properties, use the following steps. 1. Select a DCB port in the device tree. 2. Click the Properties tab in the right pane. Displaying Ethernet port properties (CNA or NIC) You can display Ethernet properties for CNA ports or Fabric Adapter ports configured in CNA or NIC mode using the HCM Ethernet Port Properties panel.
Collecting port data • • • • • • 3 Fabric WWN Fibre Channel map ID FCoE forwarder writing or nonwriting mode Maximum speed supported Port operating topology Authentication status, algorithm, group, and error status Displaying FCoE port properties To display the HCM FCoE Port Properties panel, use these steps. 1. Select an FCoE port in the device tree. 2. Click the Properties tab in the right pane.
3 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, fabric name, and name server activity. To display logical port properties, use the following steps. 1. From the device tree, select a logical port. 2. Click the LPORTs Properties tab in the right panel.
Collecting port data 3 Displaying the port list Use the port --list BCU command to list all physical ports on the adapter along with their physical attributes, such as PWWN, media type, Fibre Channel address, port type, trunking state, speed, operating state, loopback mode state, and diagnostics state. For CNAs and Fabric Adapter ports configured in CNA mode, output also includes Ethernet and DCB link states.
3 FCP-IM I/O profiling FCP-IM I/O profiling This feature, available through BCU commands and HCM, can be enabled or disabled on a physical port. When enabled, the driver firmware categories I/O latency data into average, minimum, and maximum categories. Use this feature to analyze traffic patterns and help tune adapters, fabrics, and targets for better performance. Note that enabling this feature impacts I/O performance. View this information in the Port Statistics window.
Authentication settings 3 1. Select a local host icon from the device tree in Host Connectivity Manager (HCM). 2. Select Configure > Teaming. OR Right-click the local host icon and select Teaming. The Teaming Configuration dialog box displays. 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.
3 PHY module data Displaying authentication settings through BCU Use the BCU auth --show command to display authentication settings. auth --show 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. For example, to specify adapter 1, port 1, you would use 1/1 as the port identification.
Target rate limiting settings (HBA) 3 • Use the following command to determine operating speed of the remote port and QoS status. rport --query [-l ] where: port_id Specifies the ID of the port for which you want to query attributes of a remote port. rpwwn Remote PWWN. You can obtain the RPWWN from the BCU rport --list command. -l lpwwn Logical PWWN. This is an optional argument. If the -l lpwwn argument is not specified, the base port is used.
3 Persistent binding port_id ID of the port for which you want to display target rate limiting settings. 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. • Use the following BCU command to display target rate limiting enabled status and default speed.
Adapter properties 3 Displaying Persistent Binding settings through BCU Use the pbind --list BCU command to query the list of mappings for persistent binding on a specific port. pbind --list where: port_id ID of the port for which you want to display settings. pwwn Port World Wide Name Displaying Persistent Binding settings through HCM Launch the Persistent Binding dialog box as follows to determine SCSI target ID mappings: 1. Launch the HCM. 2.
3 Adapter properties • • • • • • • Hardware Path Serial number Temperature Driver Version Driver name Firmware version BIOS version To display the properties panel, perform the following steps: 1. Select a CNA or Fabric Adapter port configured in CNA mode 2. Click the Properties tab in the right pane.
Adapter queries 3 Adapter queries Use BCU commands 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. Enter the following command: adapter --list where: list Lists all adapters in the system. For each adapter in the system, a brief information line displays containing the adapter type, model number, serial number, and hardware path.
3 112 Adapter queries Brocade Adapters Troubleshooting Guide 53-1002145-01
Chapter Performance Optimization 4 In this chapter • Tuning storage drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 • Tuning network drivers (CNA or NIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Tuning storage drivers This section provides resources for optimizing performance in adapters by tuning the unified storage drivers on Linux, Windows, Solaris, and VMware systems.
4 Tuning storage drivers Robert Love, 2nd edition, 2005 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. To increase I/O write performance, set the pcie-max-read-reqsz parameter on your system.
Tuning storage drivers 4 • Interrupt delay Default: - 1125 microseconds on the Brocade 415, 425, 815, 825, and 1860 25 microseconds on the Brocade 804, 1007, 1010, 1020, and 1741 Valid Range: 0 through 1125 microseconds Note that the value of 0 disables the delay timeout interrupt.
4 Tuning network drivers (CNA or NIC) VMware tuning For performance tuning on VMware, refer to the following publications on the VMware website at www.vmware.com: • Performance Tuning Best Practices for ESX Server 3. Refer to the following sections: - Storage Performance Best Practices - Related Publications • Fibre Channel SAN Configuration Guide. Refer to “Using ESX Server with SAN: Concepts.
Tuning network drivers (CNA or NIC) TABLE 9 4 Default values for Windows tunable parameters Parameter Default Interrupt Moderation Enabled VLAN ID Disabled Priority and VLAN Support Enabled 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” appendix in the Brocade Adapters Installation and Reference Manual.
4 Tuning network drivers (CNA or NIC) 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 “Adapter Configuration” appendix 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.
Tuning network drivers (CNA or NIC) 4 Solaris tuning All Solaris tunable parameters for the network driver are optimized for best performance using default values. For details, refer to the “Adapter Configuration” appendix in the Brocade Adapters Installation and Reference Manual. For Solaris 10, you can enable support for jumbo packet frames and set the MTU size for these frames from 1,500 (default) to 9,000 bytes.
4 120 Tuning network drivers (CNA or NIC) Brocade Adapters Troubleshooting Guide 53-1002145-01
Appendix Adapter BIOS and Event Message Reference A 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. The message, possible cause, and user action are provided.
A Adapter driver event messages TABLE 12 Adapter BIOS messages (continued) Message Cause Recommended Action Failed: LUN. Adapter This adapter is unable to connect to the configured boot device. This error message is displayed only when boot option is set to Flash Values through the Brocade BIOS Configuration Utility. 1 Adapter : BIOS is disabled BIOS is disabled for this adapter.
Adapter driver event messages TABLE 13 A Driver event messages (continued) Message Severity Event Type Category Sub Category Cause Action Base port link is disabled: Hardware Address = [Base port MAC]. Warning Network driver 10 (EthPort) Disabled Ethernet port disabled by the user. No action required. Authentication enabled for base port: WWN = [Base port WWN]. Information Storage driver 8 (AUDIT) Enabled Authentication enabled by user command. No action required.
A Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Sub Category Cause Action Remote port (WWN = [remote port WWN]) offlined by logical port (WWN = [logical port WWN]). Information Storage driver 4 (RPORT) Offline Login nexus with remote port terminated by logical port. No action required. Remote port (WWN = [remote port WWN]) connectivity lost for logical port (WWN = [logical port WWN]).
Adapter driver event messages TABLE 13 A Driver event messages (continued) Message Severity Event Type Category Sub Category Cause Action Authentication unsuccessful for base port: WWN = [base port WWN or MAC]. Error Network and storage driver 2 (Port) Failure Authentication failure. Mismatch of FC-SP configuration between switch and HBA. Also, check the authentication secret setting. Base port enabled: Hardware Address = [base port WWN or MAC].
A Adapter driver event messages TABLE 13 Driver event messages (continued) Message Severity Event Type Category Sub Category Cause Action SFP removed: port [base port number], Hardware Address = [base port WWN or MAC]. Warning Network and storage driver (stand-up adapters only) 2 (Port) Removed SFP removed. Check if SFP is inserted properly. SFP POM level to [aggregated SFP temperature, voltage, rx and tx power level]: port [base port number], Hardware Address = [base port WWN or MAC].
Appendix B 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: • Table 14 provides details on messages that display during operation of the Host Connectivity Manager (HCM).
B HCM and Installer Message Reference TABLE 14 128 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes All statistics data displayed here will be lost if you do not save them. Do you want to proceed? Occurs when the user closes the any Statistics dialog box. Information message. Are you sure you wish to clear the selected Name(s)? Occurs when the user deletes the names in Configure Names using the Remove option.
HCM and Installer Message Reference TABLE 14 B Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Choose any of the event severity levels to filter. Occurs when the user selects an event severity level, and then clicks OK in the Master Log Filter dialog box. Select at least one severity level (such as major or minor), and then click OK in the Master Log Filter dialog box. Clear Filter cannot be performed while the Event Properties dialog is open.
B HCM and Installer Message Reference TABLE 14 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Enter a valid host name or IP address Occurs when the user clicks Add button in the Syslog Server Configuration dialog box without providing any host name or IP address or by providing an invalid host name or IP address. Enter a valid host name and IP address in the host name field of the Setup for Discovery dialog box.
HCM and Installer Message Reference TABLE 14 B Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Import of Names is complete, name(s) failed to import due to invalid WWW/MAC Address Occurs when user imports the names file with invalid WWNs or MAC addresses. Verify that all the WWNs and MAC addresses in the names file are valid. Installation is not complete beyond the timeout value.\nClosing the driver update operation.
B HCM and Installer Message Reference TABLE 14 132 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes No tests have been selected. Select one or more tests. Occurs when the user clicks Start without selecting any test. Select a test, and then click Start. Password cannot be blank. Occurs when the Password field is left blank. Enter a valid Password in the password field. Password changed for agent. Occurs when password is changed. Information message.
HCM and Installer Message Reference TABLE 14 B Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Restore data is successfully completed. Please restart HCM for new data to take effect. Occurs upon successful restore of backed-up HCM data. Information message. Select a valid driver file. Occurs when driver file field is left blank. Select the appropriate driver file. Selected driver file version {0} is not supported.
B HCM and Installer Message Reference TABLE 14 134 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes The changes will take effect only on port reset. Occurs when the user adds a new authentication policy or edits the existing authentication policy in the Fibre Channel Security Protocol dialog box. Information message. The CHAP Secret and Retype Secret fields must have at least 8 alphanumeric characters.
HCM and Installer Message Reference TABLE 14 B Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes The WWN or MAC address already exists in the All WWNs/MACs table. Edit the existing record(s). Record(s) with the same WWN address are highlighted. Occurs when user enters a WWN or MAC address which is already present the WWN/MAC field in the Devine Names dialog box.
B HCM and Installer Message Reference TABLE 14 136 Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes Uploading the driver file to the agent {0} Occurs when HCM GUI uploads the driver file to the agent. Information message. Uploading the driver file is successful. Occurs when driver file uploaded successfully to the Agent host. Information message. VLAN and Team configurations successfully restored.
HCM and Installer Message Reference TABLE 14 B Host Connectivity Manager messages (continued) Message Cause Corrective Action or Notes You do not have write permission to export file to the folder Occurs when user tries to export a names file to a folder where access is denied. Make sure the folder has write permission and then export names file to that folder. You have unsaved configurations.
B HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes Disk space calculation Occurs when the available space in /opt is less than 50MB. Free at least 50MB in /opt, and then try installation. Occurs when you remove the application. If you want to back up the data, click on “Backup” or else click “Don’t backup.” Occurs when Initrd file is backedup successfully in /boot. No action required.
HCM and Installer Message Reference TABLE 15 B Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes Please free up at least 50MB in the /opt directory and try the installation again. Occurs when the space in the /opt directory is less than 50MB. Free at least 50MB and then proceed with installation. Please note that your system is Windows 2003 x86 Service Pack 1. There is no brocade adapter driver available for Windows 2003Service Pack 1.
B HCM and Installer Message Reference TABLE 15 Brocade Adapter Software Installer messages (continued) Message Cause Corrective Action or Notes System dependencies not available. Occurs when you install drivers on a Linux system that does not contain the GCC and kernel rpm and when the variable "allow_unsupported_mod ules" in /etc/modprobe.d/unsupp orted-modules file is set to “0” Change the “0” in variable "allow_unsupported_mod ules" present in /etc/modprobe.d/unsupp orted-modules file to “1.
Index A adapter diagnostics, 89 event message files, 68 hardware supported, xii IP address lost, 33 list command, 111 queries, 111 query command, 111 software supported, xii statistics, 73 adapter BIOS messages, 121 adapter management, BCU, 65 adapter not registering with name server, 42 adapter not reported under PCI subsystem, 9 adapter not showing in fabric, 41 adapter properties, 109 application log, 70, 71 applications using TDI driver stop responding, 36 authentication settings, 105 authentication st
DCB port performance statistics, 83 DCB statistics, 74 device drivers not loading, 18 device drivers not loading in Windows problem, 11 device manager, 52 diagnostics adapter, 89 beaconing, 89 enabling through BCU, 89 enabling through HCM, 90 echo test enabling through BCU, 96 enabling through HCM, 96 Ethernet loopback tests enabling through HCM, 91 HBA temperature, 94 loopback tests, 90 enabling through BCU, 90 enabling through HCM, 91, 94 memory test, 93 enabling through BCU, 93 enabling through HCM, 93 P
G graphs, 81 graphs on performance, 81 H HBA PWWN, xxii serial number, xxii supported models, xiii HBA and CNA problems, 9 HBA memory test, 93 HBA problems, 28 HCM Agent not auto starting, 49 HCM logging levels, 72 HCM logs, 70 HCM not discovering all Ethernet ports for vNICs, 28 HCM not discovering ports for vNICs, 28 HCM options to collect data, 61 HCM time doesn’t match system, 50 host commands for collecting data, 59 host freezes or crashes, 12 host not booting from remote LUN, 20 host operating system
N network interface problems for CNAs and NICs, 32 network stack runs out of heap, 34 NIC numbering on VMware unexpected, 34 no adapters found on local host, 28 no adapters reported, 10 no target devices found or link down message, 25 O one adapter port participates in trunk, 29 operating system errors, 13 operating system support CNA, xiv Ethernet, xv FCoE, xv Fibre Channel, xiv Hypervisor, xvi port link not up, 10 port list command, 103 port log, 102 port logging levels, 71 port performance statistics t
problem adapter loses IP address, 33 adapter not registering with name server, 42 adapter not reported under PCI subsystem, 9 adapter not showing in fabric, 41 applications using TDI driver stop responding, 36 BCU shortcut missing, 16 BCU version mismatch, 14 binding issues with Hyper-V enabled, 39 BIOS not installed displays, 27 boot from SAN stops on HP hosts, 26 cannot boot over SAN, 26 cannot disable trunking, 30 cannot manage CNAs after attempting upgrade, 31 cannot remove Linux driver, 17 CNA, 31 CTL-
Q QoS performance issues, 28 QoS statistics, 85 displaying through BCU, 85 displaying through HCM, 85 quality of service (QoS), 106 quality of service not functioning, 29 R receive-side scaling (RSS) disables, 35 references for isolating problems, 56 remote port properties, 101 remote port statistics, 84 displaying through BCU, 85 displaying through HCM, 84 resolving BIOS boot problems, 23 resources for product information, xx RSS network throughput decreasing, 36 S SCSI target ID mappings, 108 serial num
support save differences between HCM, BCU, and browser, 65 using, 61 using BCU on ESX systems, 64 using HCM, 63 using Management applications, 63 using through BCU, 64 using through browser, 64 using through port crash event, 65 syslog support, 69 system not booting over SAN or local disk in Legacy BIOS, 20 T target not visible from remote host, 24 target rate limiting settings, 107 target statistics, 84 team --list command, 105 team --query command, 105 teaming configuration dialog box, 104 teaming errors
148 Brocade Adapters Troubleshooting Guide 53-1002145-01
