53-1002144-01 5 August 2011 Brocade Adapters Installation and Reference Manual 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.
Title Publication number Summary of changes Date Brocade Adapters Installation and Reference Manual 53-1001926-02 Updates to support Brocade November 2010 1741 adapter Brocade Adapters Installation and Reference Manual 53-1002144-01 Updates to support Adapter release 3.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi How to use this document for installing adapters . . . . . . . . . . . xii Supported adapter hardware and software . . . . . . . . . . . . . . . . . . . xiii Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii CNAs . . . . . . . . . . . .
Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 AnyIO technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Mezzanine adapters . . . . . . . .
Stand-up adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 What you need for installation . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Installing an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Connecting an adapter to a switch or direct-attached storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Removing and installing SFP transceivers . . . . . . . . . . . . . . . . .
HCM configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Backing up configuration data . . . . . . . . . . . . . . . . . . . . . . . . .115 Restoring configuration data. . . . . . . . . . . . . . . . . . . . . . . . . . .115 Setting IP address and subnet mask on CNAs . . . . . . . . . . . . . . . .115 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Converged Network Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 PCI Express interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Cabling (stand-up adapters) . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Adapter LED operation (stand-up adapters) . . . . . . . . . . . . . .184 Environmental and power requirements . . . . . . . . . . . . . . . . .
x Brocade Adapters Installation and Reference Manual 53-1002144-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Supported adapter hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . xiii • Host operating system support for adapter drivers . . . . . . . . . . . . . . . . . . . xv • Host operating system support for HCM . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . .
• Appendix A, “Adapter Configuration,” is optional for expert network administrators, who need to modify values for adapter instance-specific persistent and driver-level configuration parameters. • Appendix B, “List of Acronyms,” provides a list of acronyms used in this publication and their definitions.
Supported adapter hardware and software This section provides an overview of Brocade adapter supported hardware and software. Fabric Adapters Brocade Fabric Adapter ports can be configured for CNA, NIC, or HBA operation using Brocade Command Utility (BCU) commands. Ports configured in CNA or NIC mode require appropriate 10GbE SFPs or direct-attached SFP+ with copper cables and operate at a 10 Gbps maximum rate.
• Brocade 815. Single-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps SFP+. • Brocade 825. Dual-port stand-up HBA with a per-port maximum of 8 Gbps using an 8 Gbps SFP+. NOTE Install only Brocade-branded small form factor pluggables (SFPs) in stand-up HBAs. Mezzanine HBAs do not have SFPs and external port connectors, but utilize internal ports and connections to switch and I/O modules installed in the blade system enclosure.
Host operating system support Refer to “Host operating system support for adapter drivers” on page xv for information on operating systems that support the Brocade Host Connectivity Manager (HCM), Brocade Command Line Utility (BCU), and adapter drivers.
• 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.
• 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 xvii. • VMware ESX Server 4.0, 4.1, and 5.0 (x64) NOTE Drivers and BCU are supported on the VMware ESX platforms. HCM is supported only on the guest system on VMware. Network drivers are not supported on IA-64 systems.
• 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.0 (x86 and x64) NOTE Specific operating system service patch levels and other patch requirements are detailed in the current release notes for your adapter software version. What’s new in this document This document adds details on adapter software release 3.
Command syntax conventions Command syntax in this manual follows these conventions: command Commands are printed in bold. --option, option Command options are printed in bold. -argument, arg Arguments. [] 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.
Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries by logging into http://my.brocade.com. For definitions specific to this document, see Appendix C, “List of Acronyms”. 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.
Adapters For adapter resources, such as product information, software, firmware, and documentation, visit the adapters website www.brocade.com/adapters. For additional information on Brocade adapters, refer to the following publications: • • • • The Brocade Quick Installation Guide (provided with your adapter model).
Providing details for support Contact your Brocade adapter support supplier for hardware, firmware, and software support, including product repairs and part ordering. Provide the following information: 1. General information: • • • • • Brocade adapter model number. Host operating system version. Software name and software version, if applicable.
• The following BCU commands: Command Function port ---query port_id Displays port information, including the PWWN for the FCoE port. The parameter is the port number. port ---list Lists all the physical ports on the adapter along with their basic attributes, such as the PWWN. 4. Media access control (MAC) addresses. These are applicable to CNAs and Fabric Adapter ports configured in CNA mode only.
NOTE For details on using HCM and BCU commands, refer to the Brocade Adapters Administrator’s Guide. Support Save overview The Support Save feature is an important tool for collecting debug information from the driver, internal libraries, and firmware. You can save this information to the local file system and send it to support personnel for further investigation. Use one of the following options to launch this feature: • In HCM, launch Support Save through the Tools menu.
• • • • Install logs Core files Details on the CNA or Fabric Adapter Ethernet interface, including IP address and mask. Status and states of all adapter ports, including the Ethernet, FCoE, and DCB ports on CNAs and Fabric Adapters. • DCB status and statistics for CNAs and Fabric Adapters • Network driver information, Ethernet statistics, offload parameters, and flow control coalesce parameters for CNAs and Fabric Adapters. • Ethernet offload and flow control parameters for CNAs and Fabric Adapters.
Initiating Support Save through HCM Launching the Support Save feature in HCM collects HCM application data. Launch Support Save by selecting Tools > Support Save. Messages display during the Support Save operation that provide the location of the directory where data is saved. If you are initiating Support Save from a remote management station and receive a warning message that support files and Agent logs could not be collected, the HCM Agent is unavailable on the remote host.
In this URL, localhost is the IP address of the server from which you want to collect the bfa_supportsave information. 2. Log in using the factory default user name (admin) and password (password). Use the current user name and password if they have changed from the default. The File Download dialog box displays, prompting you to save the SupportSaveController.do file. 3. Click Save and navigate to the location where you want to save the file. 4. Save the file, but rename it with a “zip” extension.
xxviii Brocade Adapters Installation and Reference Manual 53-1002144-01
Chapter Product Overview 1 In this chapter • Fabric Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Converged network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 • Host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 • Adapter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Fabric Adapters 1 2 3 6 4 FIGURE 2 5 Brocade 1860 Fabric Adapter (heat sink removed) 1 LEDs for port 1 SFP 2 Cable connectors for port 1 and port 0 SFPs (Fiber optic SFP illustrated) 3 LEDs for port 0 SFP 4 Low-profile mounting bracket. Note: The adapter ships with the standard (full-height) mounting bracket installed. 5 PCIe x8 connector 6 ASIC ATTENTION Only use Brocade-branded SFP+ laser transceivers supplied with stand-up Fabric Adapters.
Fabric Adapters 1 • Ethernet or NIC mode. This mode utilizes the Brocade network driver. A 10 GbE SFP or direct attached SFP+ copper cable must be installed for the port. This mode supports basic Ethernet, Data Center Bridging (DCB), and other protocols that operate over DCB to provide functions on a single port that are traditionally provided by an Ethernet Network Interface Card (NIC). Ports configured in this mode can operate up to 10 Gbps.
1 Fabric Adapters Hardware compatibility This section outlines important compatibility information. SFP transceivers Use only the Brocade-branded small form factor pluggable (SFP) transceivers described in this section for stand-up Brocade Fabric Adapters. Ports configured in CNA or NIC mode Table 1 provides the type, description, and switch compatibility information for supported SFPs that can be installed in ports configured in CNA or NIC mode.
Converged network adapters TABLE 2 1 Compatible SFPs for ports configured in HBA mode Type Description Switch Compatibility 16 Gbps SWL (short wave laser) SFP+ SFP+ for fiber optic cable Distance depends on cable type. Refer to “Cabling” on page 176. Any switch compatible with the adapter 16 Gbps LWL (long wave laser) 10 km SFP+ SFP+ for fiber optic cable Distance depends on cable type. Refer to “Cabling” on page 176.
1 Converged network adapters TABLE 3 Brocade Fibre Channel CNAs Model Number Port Speed Number of Ports Adapter Type 1007 10 Gbps maximum 2 Mezzanine 1020 10 Gbps maximum 2 Stand-up 1010 10 Gbps maximum 1 Stand-up 1741 10 Gbps maximum 2 Mezzanine Two types of CNAs are available: • Stand-up adapters. These are low-profile MD2 form factor PCI Express (PCIe) cards, measuring 6.6 in. by 2.714 in. (16.765 cm by 6.89 cm) that install in PCIe connectors in standard host systems.
Converged network adapters 1 1 2 3 6 4 5 Note: This photo illustrates parts location only. The CNA may not look exactly like your model. 1 LEDs for port 1 SFP 2 Cable connectors for port 1 and port 0 SFPs (Fiber optic SFP illustrated) 3 LEDs for port 0 SFP 4 Low-profile mounting bracket. Note: The CNA ships with the low-profile mounting bracket installed.
1 Converged network adapters Mezzanine adapters Mezzanine adapters are smaller modules than stand-up models. These mount on server blades that install in blade system enclosures. 1007 Figure 4 illustrates major components of the Brocade 1007, which is an IBM combo form factor horizontal (CFFh) CNA containing two ports operating at 10 Gbps. Please note that the following illustration is representative and may have minor physical differences from the card that you purchased.
Converged network adapters 1 The Brocade 1007 mounts on a server blade that installs in an IBM BladeCenter® enclosure. The adapter uses FCoE to converge standard data and storage networking data onto a shared Ethernet link. Ethernet and Fibre Channel communications are routed through the DCB ports on the adapter to the blade system enclosure midplane, and then onto switch modules installed in the enclosure.
1 Converged network adapters The Brocade 1741 mounts on supported blade servers that install in Dell™ PowerEdge™ M1000e modular blade systems. It is used in conjunction with matching I/O modules, also installed in the blade enclosure. The adapter uses FCoE to converge standard data and storage networking data onto a shared Ethernet link. Ethernet and Fibre Channel communications are routed through the DCB ports on the adapter to the enclosure backplane then to the I/O module.
Converged network adapters 1 Server blades and blade system enclosures (mezzanine adapters) Consider the following points when installing mezzanine adapters in blade servers and system enclosures: • For information on server blades and blade system enclosures that are compatible with adapters, refer to the “Adapters Resources” section of www.brocade.com/adapters.
1 Host bus adapters Storage systems Using Brocade CNAs you can connect a server (host system) to a Fibre Channel SAN through connection with a compatible FCoE switch. For a current list of compatible switches, servers, and applications, refer to the latest interoperability matrices on Brocade’s website at www.brocade.com/adapters. NOTE The CNA can connect with a network switch and perform NIC functions for network traffic.
Host bus adapters 1 Using Brocade HBAs, you can connect your host system to devices on the Fibre Channel SAN. The combined high performance and proven reliability of a single-ASIC design makes these HBAs ideal for connecting hosts to SAN fabrics based on Brocade Fabric or M-Enterprise operating systems. NOTE This publication only supports the HBA models listed in Table 5, and does not provide information about the Brocade 410 and 420 Fibre Channel HBAs, also known as the Brocade 400 Fibre Channel HBAs.
1 Host bus adapters ATTENTION Use only Brocade-branded SFP laser transceivers on stand-up adapters that are supplied with the adapter. Mezzanine models Figure 7 on page 14 illustrates major components of the Brocade 804 mezzanine HBA. This mezzanine card installs in supported blade servers that install in Hewlett Packard BladeSystem c-Class enclosures. Please note that the following illustration is representative and may have minor physical differences from the HBA that you purchased.
Host bus adapters 1 Hardware compatibility This section outlines important compatibility information. SFP transceivers (stand-up adapters) Use only Brocade-branded small form factor pluggable (SFP) fiber optic 4 Gbps and 8 Gbps transceivers in the Brocade Fibre Channel stand-up HBAs. NOTE All Brocade 815 and 825 HBAs ship with the 8 Gbps SFP+, and Brocade 415 and 425 HBAs ship with the 4 Gbps SFP.
1 Adapter features Storage systems Using Brocade HBAs you can connect a server (host system) to a Fibre Channel SAN in a switched fabric and point-to-point topology or directly to a storage array in a point-to-point topology. Refer to the latest Brocade interoperability matrices for a list of supported server models on Brocade’s website at www.brocade.com/adapters.
Adapter features 1 • For Fabric Adapters, the default number of PFs depends on the mode configured for the port. Refer to Table 6. TABLE 6 Factory default physical function (PF) configurations for Fabric Adapter ports. Mode PFs configured per port PF configuration per port HBA 1 FC CNA 2 Ethernet and FCoE NIC 1 Ethernet vHBA Virtual HBAs (vHBAs) are virtual port partitions that appear as virtual or logical HBAs to the host operating system.
1 Adapter features vHBA and vNIC BCU commands Whether a port is configured for a single function or in the case of vNICs, multiple functions, each PF is assigned a PCI function ID (pcfid). This pcfid is used as a parameter in BCU commands to configure additional features or display information for that specific PF.
Adapter features 1 • Hyper-V. This consolidates multiple server roles as separate virtual machines (VMs) using the Windows Server 2008 operating system and provides integrated management tools to manage both physical and virtual resources. • Management APIs for integration with a Management application, such as Network Advisor, and other management frameworks. • Switch fabric topology - CNAs and Fabric Adapter ports configured in CNA mode can connect to an FCoE switch through 10 GbE ports.
1 Adapter features FCoE features CNAs and Fabric Adapter ports configured in CNA mode support the following Fibre Channel over Ethernet (FCoE) features: Brocade CNAs support the following features: • 500,000 IOPS per port for maximum IO transfer rates. • 10 Gbps throughput per port full duplex • Fibre Channel Security Protocol (FC-SP), providing device authentication through key management. • Boot over SAN.
Adapter features 1 • Interrupt Coalescing This feature provides a method to delay generation of host interrupts and thereby combine (coalesce) processing of multiple events. This reduces the interrupt processing rate and reduces the time that the CPU spends on context switching. You can configure the following parameters per port to adjust interrupt coalescing: - Interrupt time delay. There is a time delay during which the host generates interrupts.
1 Adapter features Target rate limiting is enforced on all targets that are operating at a speed lower than that of the target with the highest speed. If the driver is unable to determine a remote port’s speed, 1 Gbps is assumed. You can change default speed using BCU commands. Target Rate Limiting protects only FCP write traffic. • vHBA Virtual HBAs (vHBAs) are virtual port partitions that appear as virtual or logical HBAs to the host operating system.
Adapter features 1 • Ethernet flow control Ethernet flow control is a mechanism for managing data transmission between two network nodes to prevent a fast sender from over running a slow receiver. When an overwhelmed receiver generates a PAUSE frame, this halts transmission for a specified period of time. Traffic resumes when time specified in the frame expires or PAUSE zero is received.
1 Adapter features - Failback mode is an extension of the Failover mode. In addition to the events that occur during a normal failover, if the original primary port comes back up, that port again becomes the primary port. - 802.3ad is an IEEE specification that includes Link Aggregation Control Protocol (LACP) as a method to control how several physical ports bundle to form a single logical channel.
Adapter features 1 • Interrupt moderation Implements dynamic selection interrupt coalescing values based on traffic and system load profiles. Traffic is continuously monitored to place in categories between “high throughput sensitive” and “high latency sensitive.” Similarly, the host system is monitored regularly to place it in categories between “highly loaded” and “minimally loaded.” The driver dynamically selects interrupt coalescing values based on this profiling.
1 Adapter features • Team Virtual Machine Queue (VMQ) support VMQ support is provided by the Brocade Network Intermediate (BNI) driver for teaming (with no VLANs). VMQ support allows classification of packets that the adapter receives using the destination MAC address, and then routing the packets to different receive queues. Packets can be directly transferred to a virtual machine’s shared memory using direct memory access (DMA).
Adapter features 1 • VLAN and Teaming Configuration Persistence VLAN and teaming configurations can be maintained when updating drivers. Configurations are automatically saved during upgrade and can be restored using BCU commands or HCM. • VMware NetQueue This feature improves performance in 10 GbE virtualized environments by providing multiple receive and transmit queues, which allows processing to be scaled to multiple CPUs.
1 Adapter features • LUN masking. LUN masking establishes access control to shared storage to isolate traffic between different initiators that are zoned in with the same storage target. LUN masking is similar to zoning, where a device in a specific zone can communicate only with other devices connected to the fabric within the same zone. With LUN masking, an initiator port is allowed to only access those LUNs identified for a specific target.
Adapter features 1 - Interrupt time delay. There is a time delay during which the host generates interrupts. You can increase this delay time and thereby coalesce multiple interrupts events into one. This results in fewer interrupts for interrupt events. - Interrupt latency timer. An interrupt is generated when no new reply message requests occur after a specific time period. You can adjust this time period and thereby minimize I/O latency. • 16 Virtual Channels (VCs) per port.
1 Adapter features Before enabling trunking, consider the following requirements: - When trunking is enabled, a trunked logical port (Port 0) is created and reported per HBA or Fabric Adapter port configured in HBA mode. Most BCU commands are applicable in this logical port's context only. - When configuring Fabric Zones and LUN Masking for Storage, use the PWWN for adapter port 0. - Both adapter ports should be connected to the same port group on the switch.
Adapter management features 1 • Point-to-point topology. • Management support for Storage Management Initiative Specification (SMI-S). • Fibre Channel-Security Protocol (FC-SP) providing device authentication through key management. • FCoE Initialization Protocol (FIP) support for the following: - FIP 2.0. - preFIP and FIP 1.03. - FIP Discovery protocol for dynamic FCF discovery and FCoE link management. - FPMA and SPMA type FIP fabric login. - FIP VLAN discovery.
1 Adapter management features For the Brocade 1007 CNA, BIOS and UEFI boot code support Advanced Management Module (AMM) connectivity and Blade Center Open Fabric Manager (BOFM) for configuring SAN and LAN connections SAN target selection, and WWN virtualization. For more information, refer to “BladeCenter Open Fabric Manager (BOFM)” on page 34.
Adapter management features 1 Fabric Adapter management Use BCU commands, HCM, and Simple Network Management Protocol (SNMP) to manage Fabric Adapter ports. For a summary of available management features using HCM and BCU, refer to one of the following sections, depending on whether the Fabric Adapter port is configured in CNA, HBA, or NIC modes.
1 Adapter management features Ethernet management HCM and BCU commands provide the provide the following functions for CNAs and for Fabric Adapter ports configured in CNA or NIC modes: • • • • • • • • • • Teaming configuration Ethernet port statistics display vNIC statistics display VLAN configuration VLAN statistics display Ethernet logging level configuration VLANs over teaming configuration Persistent binding configuration NIC teaming, and VLAN statistics monitoring Preboot eXecution Environment (PXE
Adapter management features 1 The agent accesses information about the adapter and makes it available to an SNMP network management station. When active, the management station can get information or set information when it queries the agent. The agent uses variables (also known as managed or MIB objects) to report data such as the following.
1 Adapter management features HBA management BCU commands and HCM provide the following features for HBAs and for Fabric Adapter ports configured in HBA mode: • • • • • • • • • • • • • • Port statistics display • • • • • • • Virtual FC ports creation Discovery of adapters and connected storage devices in your SAN Adapter configuration Persistent binding End-to-end QoS Target rate limiting Performance monitoring, such as port and target statistics Supportsave operation Adapter diagnostics display N_Po
Adapter software 1 In addition to features summarized in the preceding sections of this guide, there are some unique management features for Fabric Adapters, not available for HBAs and CNAs, including the following: • • • • • • • Configure port modes (CNA, HBA, NIC) Create, delete, enable, and disable vNICs. Query for information, display statistics, and set bandwidth for vNICs.
1 Adapter software LANs created by BCU commands or HCM options are directly bound to upper protocols. All traffic goes from the protocols layer to the VLANs, then to the network driver. You should not enable TCP, IPV4, or other protocols or services for the network driver after installing the intermediate driver. Each driver package contains the following components: • Driver for your host system. In most cases, both the required storage and network drivers are included in installation packages.
Adapter software 1 For Linux systems, download and extract the appropriate tar.gz file for your system. After extracting files, execute the following commands, depending on your system: - RHEL systems. brocade_install_rhel.sh - SLES systems brocade_install_sles.sh For VMware ESX and ESXi systems, download and extract the appropriate tar.gz file for your system. After extracting files, execute the following commands, depending on your system: - VmWare ESX 4.X brocade_install.sh - VmWare ESX 5.
1 Adapter software • SNMP subagent. Simple Network Management Protocol (SNMP) is an industry-standard method of monitoring and managing network devices. SNMP is supported by CNAs and by Fabric Adapter ports configured in CNA or NIC mode. SNMP support is provided through an extension to the SNMP master agent, called the subagent, which processes SNMP queries for Brocade adapters. The subagent is only supported on Linux and Windows systems.
Adapter software TABLE 7 1 Operating system support for network and storage drivers (continued) Solaris 10.0 Network driver supported - 32b Storage driver supported - 32b Network driver supported - 32, 64b Both drivers not supported Both drivers supported. Storage driver supported - 32b, 64b VMware ESX/ESXi ESX 4.0, 4.1, 5.0 N/A Both drivers supported - 64b N/A N/A Oracle Enterprise Linux (OEL) 5.6, 6.0 Both drivers supported - 32b Both drivers supported - 64b N/A N/A Oracle VM 3.
1 Adapter software Host Connectivity Manager Host Connectivity Manager (HCM) is a graphical user interface (GUI) based management software for installing, configuring, monitoring, and troubleshooting installed adapters. HCM performs the “client” function for the management software. You can only install HCM using the Brocade Adapter Software Installer. The HCM agent is installed with the driver package on systems where adapters are installed.
Adapter software 1 CIM Provider CIM Provider allows third-party SMI-S and CIM-based adapter management software to manage Brocade adapters installed on a host system. The appropriate CIM Provider rpm or msi package loads to your host system when you manually install the driver package using instructions under “Using software installation scripts and system commands” on page 89. The CIM Provider files do not load when you use the Brocade Adapter Software Installer.
1 Adapter software Note that in the following ISO file name that the will be replaced by the date of the software. brocade_adapter_software_ISO_.iso Download the driver package and boot image for your host system operating system and platform from the Brocade adapter website. Use the following steps. 1. Go to the adapters website at www.brocade.com/adapters. 2. Navigate to the adapters Downloads page. 3.
Adapter software TABLE 9 1 Supported software installation packages (continued) Operating System and Platform Brocade Adapter Software Installer Driver Package Windows Server 2008 (x64) brocade_adapter_software_installer_ windows_.exe Installs HCM and appropriate driver package. brocade_driver_win2008_x64_.exe Storport miniport storage and network drivers with HCM Agent for Standard/Enterprise Server on EM64T and AMD64 platforms.
1 Adapter software TABLE 9 46 Supported software installation packages (continued) Operating System and Platform Brocade Adapter Software Installer Driver Package Linux SLES 11 (x86) brocade_adapter_software_installer_ linux_.bin Installs HCM and appropriate driver package. • • brocade_driver_linux_.tar.gz3 brocade_driver_linux_sles11_.tar.gz4 Linux SLES 11 (x86_64) brocade_adapter_software_installer_ linux_.bin Installs HCM and appropriate driver package.
Adapter software TABLE 9 1 Supported software installation packages (continued) Operating System and Platform Brocade Adapter Software Installer Driver Package VMware ESX/ESXi (x64) 5.0 Note: Use appropriate Brocade Adapter Software Installer listed in this column to install HCM on applicable “guest” operating system only. The software installer is not supported on ESX systems. The HCM agent is not supported on ESXi platforms. brocade_driver_esx50_.tar.gz7 4.
1 Items shipped with your adapter Software installation options You can use the Brocade Adapter Software Installer or options in “native” installation scripts and commands to install software on your host system: • Brocade Adapter Software Installer Use this to install the following components: - Storage driver, network driver, and HCM Storage and network driver HCM only For more information, refer to “Using the GUI-based installer” on page 69.
Boot installation packages 1 Mezzanine adapters The following items may be shipped with adapters for installation, depending on the adapter model: • • • • Adapter Adapter installation instructions Important notices document and warranty card CD containing documentation for installing, removing, configuring, and troubleshooting the adapter.
1 Boot installation packages • An ISO 9660 (.iso) optical disk image containing all files listed in the supported software installation packages table (Table 9 on page 44) and boot installation packages table (Table 10 on page 51). Use this image to create CDs or USB drives to carry with you for installation. The image also contains product documentation, such as product manuals, current release notes, and licensing information.
Boot installation packages TABLE 10 1 Boot installation packages Operating System (Platform) Driver Update Disk Image LiveCD Boot Code Windows 2003 (x86) brocade_adapter_fc_w2k3_x86_dud_.zip1 live_cd_ .iso brocade_adapter_ boot_fw_ Windows 2003 (x86_64) brocade_adapter_fc_w2k3_x64_dud_.zip1 live_cd_ .iso brocade_adapter_ boot_fw_ Windows 2008 (x86) brocade_adapter_fc_w2k8_x86_dud_.
1 Downloading software and publications TABLE 10 Boot installation packages (continued) Operating System (Platform) Driver Update Disk Image LiveCD Boot Code Linux SLES 11 SP1 brocade_adapter_sles11sp1_dud_.iso4 live_cd_ .iso brocade_adapter_ boot_fw_ Solaris 10 brocade_adapter_sol_dud_.iso7 live_cd_ .iso brocade_adapter_ boot_fw_ VMware ESX/ESXi 4.0 bfa_esx4x_.iso8 bna_esx4x_.iso9 live_cd_ .
Using BCU commands 1 6. When the File Download screen displays, save the file to an appropriate location on your system. Using BCU commands Some procedures in this manual reference BCU commands for adapter monitoring and configuration. To use BCU commands, enter commands at the BCU> command prompt. For Windows systems, launch the command prompt using the Brocade BCU desktop aa, which automatically installs to your desktop with the adapter software.
1 54 Using BCU commands Brocade Adapters Installation and Reference Manual 53-1002144-01
Chapter 2 Hardware Installation In this chapter • Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • ESD precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Stand-up adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Mezzanine adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Stand-up adapters Stand-up adapters Use information in this section to install stand-up adapter hardware on your host system. What you need for installation Have the following items available for installing the adapter hardware: • Phillips #1 screwdriver. • Adapter with appropriate mounting bracket attached. • Appropriate cable with appropriate connectors to connect the adapter to the switch. - For Fabric Adapter cable and SFP specifications, refer to “Cabling” on page 176.
Stand-up adapters 2 8. Install the longer, standard bracket on the adapter if the low-profile mounting bracket (shipped installed on adapter) does not fit your system case. Use the following steps. If the installed low-profile bracket works, go on to step 9. a. Remove all SFP transceivers from the adapter. Refer to “Removing and installing SFP transceivers” on page 59 for procedures. b. Remove the two screws attaching the bracket to the adapter, and pull off the bracket. Refer to Figure 8.
2 Stand-up adapters 1 2 2 5 4 1 Mounting screw 2 Top edge of adapter (press down into slot) 3 PCI X8 slot 4 Edge of host board 5 SFP receivers FIGURE 9 3 Installing adapter in system chassis 10. Secure the adapter’s mounting bracket to the case using the method required for your case. Note that in some systems, the bracket may secure to the case with a screw. 11. If you removed transceivers in step step 7, make sure to install adapter receivers.
Stand-up adapters 2 1. Pull out the protective rubber inserts from fiber optic SFP connectors, if installed in adapters or the switch. 2. Connect the cable from the switch to the appropriate SFP connector on the adapter. Removing and installing SFP transceivers User the following procedures to remove and install fiber optic SFP transceivers. NOTE Use only the Brocade-branded small form factor pluggable (SFP) transceivers in the Brocade adapters. Refer to “Hardware compatibility” on page 10.
2 Stand-up adapters A B . 0 PO RT FIGURE 10 1 0 PO RT 1 Removing or installing fiber optic and copper SFPs Installing transceivers 1. Orient the SFP in front of its slot on the adapter so that it can slide into the adapter receiver slot. The SFP can only be oriented one way into the slot. 2. Carefully guide the SFP into the adapter’s receiver until it seats. • For optical SFPs close the bail to latch the SFP into the receiver.
Mezzanine adapters 2 Mezzanine adapters Mezzanine adapters are smaller modules than stand-up models that mount on server blades that install in blade system enclosures. Instead of connecting fiber optic cables between stand-up adapters ports in traditional servers and switches, mezzanine adapters connect to switch or I/O modules installed in the blade system enclosure through the enclosure midplane.
2 Mezzanine adapters Brocade 1007 CNA For details on installing this adapter in a blade server, refer to the Installation and User Guide that ships with the adapter. The adapter (expansion card) Installation and User’s Guide provides full details on installation guidelines, installing and removing the blade server from the blade system enclosure, installing and removing the adapter from the blade server, resolving problems, obtaining help and technical assistance, related documentation.
Mezzanine adapters 2 • Instructions for accessing the blade server through a console or workstation to install adapter drivers and software. What you need for installation Have the following available for installing the adapter: • • • • Mezzanine card shipping carton, which includes the adapter and necessary documentation. Fully operational blade server. Access to the blade server through local or remote console connection. The blade enclosure’s Hardware Owner’s Manual.
2 64 Mezzanine adapters Brocade Adapters Installation and Reference Manual 53-1002144-01
Chapter Software Installation 3 In this chapter • Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 • Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 • Using the Brocade Adapter Software Installer. . . . . . . . . . . . . . . . . . . . . . . . 68 • Using software installation scripts and system commands . . . . . . . . . . . . .
3 Installation notes Installation notes Please read through the following notes before installing adapter software: • For details on operating system requirements for installing adapter drivers, refer to “Operating system support” on page 40 and “Software installation and driver packages” on page 43. Also download the latest release notes from the Brocade adapters website using the following steps: a. Go to the adapters website at www.brocade.com/adapters. b. Navigate to the adapters Downloads page.
Installation notes 3 • You must use the Brocade Adapter Software Installer application to install HCM to the host system where the adapter is installed or to a separate remote management platform.You cannot install HCM using the Brocade-provided installation scripts or your system’s “native” installation commands. After installation, an HCM desktop shortcut is available on Windows and Linux systems.
3 Using the Brocade Adapter Software Installer KB958015 is recommended for CNAs and Fabric Adapter ports configured in CNA mode. - Windows 2008 R2 KB977977 is recommended for CNAs and Fabric Adapter ports configured in CNA mode. • Installing software with the Brocade Adapter Software Installer automatically starts the HCM Agent. You can manually start and stop the agent using the instructions under “HCM Agent operations” on page 112.
Using the Brocade Adapter Software Installer 3 NOTE The storage driver will claim all installed Brocade Fiber Channel HBAs, FCoE CNAs, and Fabric Adapter ports configured in HBA or CNA mode installed in a host system. RHEL 6.x version x64 systems The Brocade Adapter Software Installer and HCM are 32-bit applications. To use these applications on Linux RHEL 6.x version x64 systems, you must install the x32-compatible libraries because they are not installed by default.
3 Using the Brocade Adapter Software Installer NOTE The software installer is not supported on VMware ESX platforms. However, you can use the appropriate Brocade Adapter Software Installer to install HCM to a guest system (Windows, Linux, or Solaris). To install adapter drivers on VMware systems, refer to “Using software installation scripts and system commands” on page 89. Use the following steps to install all software required for Brocade adapters with the GUI-based installer program.
Using the Brocade Adapter Software Installer FIGURE 11 3 Brocade Adapter Installer Introduction screen 4. When the License Agreement screen displays, select I accept the terms of the License Agreement, then click Next to continue. 5. If a backup directory exists for previously installed software, a “Found Backed up data” message displays prompting you to restore old configurations. Select either to restore or not to restore and continue installation.
3 Using the Brocade Adapter Software Installer FIGURE 12 7. Existing software components installed screen If message box displays prompting you to close all HCM applications, close all applications if they are still running, then click OK. The Choose Install Set screen displays (Figure 13 or Figure 14). NOTE This following screen displays for all adapter models except the Brocade 804 adapter. .
Using the Brocade Adapter Software Installer FIGURE 14 3 Choose Install Set screen (804 adapter only) 8. Select which software you want to install, then select Next. If you are installing the management utilities and messages display warning that HCM agent requires storage and network driver installation or does not match current driver installation, click OK. and select the Management Utilities and Storage and Network Drivers options.
3 Using the Brocade Adapter Software Installer FIGURE 15 Pre-Installation Summary screen A progress bar displays showing installation progress for the various software components. NOTE For Windows systems, a Force Driver Installation message box displays if a better driver is already installed for the adapter. If message displays, select OK to overwrite the existing driver or Cancel to quit installation.
Using the Brocade Adapter Software Installer FIGURE 16 3 Install Complete screen 12. Confirm that all software installed successfully. If the screen instructs you to restart or reboot the system, select any options that apply. 13. Select Done. 14. Verify installation using tools available on your host system. Refer to “Confirming driver package installation” on page 103 for details. 15.
3 Using the Brocade Adapter Software Installer Software installation using Software Installer commands Execute Brocade Adapter Software Installer commands detailed in this section on the host system’s command line with your choice of parameters to step through the installation or automatically install network and storage driver packages, the HCM application, or both without requiring further user interaction. The HCM Agent starts automatically after installation.
Using the Brocade Adapter Software Installer 3 sh brocade_adapter_software_installer_linux_.bin -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -DFORCE_WIN_DRIVER_INSTALLATION=1 -i silent Install drivers and HCM GUI in silent mode (no interaction required). sh brocade_adapter_software_installer_linux_.exe -i silent Install drivers and the HCM GUI using a default installation properties file. sh brocade_adapter_software_installer_linux_.bin -f HCMDefaultInstall.
3 Using the Brocade Adapter Software Installer sh brocade_adapter_software_installer_solaris10_x86_.bin -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -i silent - SPARC platforms Install driver, HCM GUI, both, or management utilities. Overwrites the existing driver installed on the system. sh brocade_adapter_software_installer_solaris10_sparc_.bin -DCHOSEN_INSTALL_SET=[DRIVER|GUI|BOTH|UTIL] -i silent Installs drivers and HCM GUI in silent mode (no interaction required).
Using the Brocade Adapter Software Installer 3 • FORCE_WIN_DRIVER_INSTALLATION=1 Be sure to uncomment the "FORCE_WIN_DRIVER_INSTALLATION=1" to overwrite the existing driver on Windows platform. Note that this may require system reboot. For Linux or Solaris systems, use the standard DCHOSEN_INSTALL_SET command to overwrite existing software. • #FORCE_INITRD_BACKUP=YES For Linux systems, a “YES” value overwrites the backed-up initrd file.
3 Using the Brocade Adapter Software Installer • Select Download ISO Image and download an ISO 9660 (.iso) optical disk image. This contains the Brocade Adapter Software Installer, individual driver packages containing installer scripts, HCM, and documentation. You can use this ISO file to create a CD that you can carry to your system for installation. • To enter these commands, first change to the directory where the adapter software is installed (cd ).
Using the Brocade Adapter Software Installer 3 Installation examples Following are some examples of using commands and parameters to install adapter software: • To install the storage and network drivers in silent mode and start the HCM Agent automatically by default. Windows systems brocade_adapter_software_installer_windows_.exe -DCHOSEN_INSTALL_SET=DRIVER -i silent Linux systems sh brocade_adapter_software_installer_linux_.
3 Using the Brocade Adapter Software Installer • To install HCM interactively. Windows systems brocade_adapter_software_installer_windows__.exe Linux systems sh brocade_adapter_software_installer_linux_.bin Solaris systems sh brocade_adapter_software_installer_solaris10_x86_.bin sh brocade_adapter_software_installer_solaris10_sparc_.bin • To install the noarch driver on Linux systems in silent mode. sh brocade_adapter_software_installer_linux_.
Using the Brocade Adapter Software Installer 3 Software removal using Adapter Software Uninstaller Use the following steps to remove the adapter driver packages and HCM. Instructions are provided for using the GUI-based or command-based Brocade Adapter Software Installer. Instructions are provided for Windows, Solaris, and Linux systems. Important notes Review these notes for removing the Brocade adapter software from your system: • Use steps in this section to remove HCM.
3 Using the Brocade Adapter Software Installer For Linux and Solaris systems, perform the following steps. a. Change to the directory where the Adapter Software Installer application is installed using the following command: cd /UninstallBrocade Adapter Software where: - default install directory is /opt/brocade/adapter. - the application version, such as v3.0. b.
Using the Brocade Adapter Software Installer 3 6. If a message box displays asking if you want to back up HCM configurations, click Yes or No. If you select Yes, a dialog box displays prompting you to select a backup directory. Use the default directory or browse to another location. Select Uninstall to perform backup and remove software. A screen eventually displays notifying you of a successful uninstall.
3 Using the Brocade Adapter Software Installer where: • DCHOSEN_INSTALL_SET Specifies to remove either the network and storage driver packages, the GUI (HCM), management utilities, or all components. • DEBUG - specifies whether the debug log messages are needed. Possible values are true or false. • i silent - specifies that the uninstallation mode is silent. Important notes Review these notes before using the software uninstaller commands.
Using the Brocade Adapter Software Installer 3 • To remove HCM only without using silent mode, but with debug messages. Windows systems Uninstall.bat -DCHOSEN_INSTALL_SET=GUI -DEBUG=true Linux or Solaris systems sh Uninstall.
3 Using the Brocade Adapter Software Installer • VMware systems When upgrading the driver for VMware systems, you must reboot the host system. The new driver is effective after system reboot. Because the ESX 5,0 driver installation process does not enforce maintenance mode, it is recommended that you put the host in maintenance mode, as since a system reboot is required after installation.
Using software installation scripts and system commands 3 Installer log A status log is available after installation that provides complete status of installed software components. The name of the installed component, version, and location in file system are provided. The Installation_Status.
3 Using software installation scripts and system commands • Refer to “Software installation and driver packages” on page 43 and “Operating system support” on page 40 for details on driver packages and operating system support. Also download the latest release notes on the Brocade adapters website at www.brocade.com/adapters. On the website, navigate to the drivers Downloads page.
Using software installation scripts and system commands 3 Driver installation and removal on Windows systems Use the following procedures to install, remove, and update driver packages on a Windows system. Only one driver installation is required for all adapters (CNAs, HBAs, or Fabric Adapters) installed in a host system.
3 Using software installation scripts and system commands Installing and removing drivers on Windows systems Use these steps to install storage and network driver packages on Windows systems. Refer to “Software installation and driver packages” on page 43 for a description of Windows driver packages. 1. Boot the host and log on with Administrator privileges. NOTE For Windows 2008 systems, you must disable User Account Control (UAC) to use the installer program (brocade_installer.bat).
Using software installation scripts and system commands 3 • DRIVER_TYPE= HBA - The operation as specified by INSTALL_OP will be performed for Fibre Channel drivers only. CNA - The operation as specified by INSTALL_OP will be performed for network drivers only. AUTO - The operation as specified by INSTALL_OP will be performed for the drivers for adapters that are present in the system. • LOG_FILE_PATH Specify path to installer log. Quote marks need to enclose the path needs when it contains a space.
3 Using software installation scripts and system commands 9. Verify installation by launching the Device Manager to display all installed devices. • For CNAs, HBAs, and Fabric Adapters, when you expand the list of SCSI and RAID controllers or Storage controllers an instance of the adapter model should display for adapter port installed.
Using software installation scripts and system commands 3 brocade_install.bat W2K8_HOTFIX= “KB9987654:Required:newer_hotfix” • Avoid checking for hot fix brocade_install.bat W2K3_HOTFIX="" Upgrading driver on Windows systems To update the drivers, follow procedures under “Installing and removing drivers on Windows systems” on page 92. Notes: • When upgrading the driver for Windows systems, you do not need to reboot the host system as the driver upgrades immediately.
3 Using software installation scripts and system commands brocade_install_sles.sh [-u,-h] [--update\--add\--rm-initrd] [--force-uninstall] where: -u Uninstalls driver RPM packages. -h Displays help for install script. Initial RAM disk options: --update-initrd Updates or adds the storage driver (bfa) to initrd. Note that you should only update the initrd if you are intending to use the boot from SAN feature. If the storage driver (bfa) is listed under /etc/sysconfig/kernel (SUSE) and /etc/modprobe.
Using software installation scripts and system commands 3 This command prints the names of the network driver package (bna) if installed. lspci 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 or Fabric Adapter port configured in HBA mode. Fibre Channel: Brocade Communications Systems, Inc.
3 Using software installation scripts and system commands • Network drivers - bna_driver__.pkg • User utilities - brcd_util__.pkg Refer to “Software installation and driver packages” on page 43 for a description of host systems that this driver package supports. NOTE Root access is required to install or remove the driver package. 1. Log on to the Solaris system as a super user. 2. Copy the brocade_driver__.
Using software installation scripts and system commands 3 8. When a driver is installed and the host system is connected to the fabric turn on host power and verify adapter operation. Verify proper LED operation for stand-up adapters by referring to “Adapter LED operation (stand-up adapters)” on page 184. Removing driver packages from Solaris systems Use the following steps to remove driver and utility packages. NOTE Root access is required to remove the packages. 1. Log on to your system as root user.
3 Using software installation scripts and system commands NOTE Note that you can use the VMware Image Builder PowerCLI to create a brocade_esx50_.zip offline bundle and brocade_esx50_.iso ESX 5.0 installation image that includes brocade drivers and utilities. Refer to your Image Builder documentation for details on using Image Builder PowerCLI. Installation on ESX 4.X and ESXi 5.0 systems Use the following steps for ESX 4.X and ESXi 5.0 systems. For ESXi 4.
Using software installation scripts and system commands 3 • To display help, enter one of the following commands: brocade_install.sh -h brocade_install_esxi.sh -h 4. Reboot the system. 5. Determine if the driver package is installed using the following commands: esxcfg-module -l This lists loaded module names. Verify that an entry for bfa exists for the storage driver and an entry for bna exists for the network driver. cat /proc/vmware/version This displays the latest versions of installed drivers.
3 Using software installation scripts and system commands 5. Log in as vi-admin, using the password from step 4. 6. Copy the adapter driver iso file from the temporary directory to the vMA. 7. Run the following command for superuser privileges: # sudo -s 8. When prompted for the password, enter the superuser account password (same as from step 4). 9. Add the ESXi server IP Address to vMA using the following command.
Confirming driver package installation 3 Using the vSphere Client, right click ESXi and choose the Exit Maintenance Mode option. 18. Reboot ESXi 4. Right-click the ESXi 4 server and select Reboot. NOTE Be sure to reboot ESXi server where we are installing the driver and NOT the vMA 19. After the ESXi server has rebooted, run the following command to make sure the driver is installed.
3 Confirming driver package installation Confirming driver installation with HCM Following is the HCM procedure to display adapter information. 1. Launch HCM. 2. Select the adapter in the device tree. 3. Select the Properties tab in the right pane to display the Properties dialog box. The dialog box displays adapter properties.
Confirming driver package installation 3 4. Click the Driver tab to display the driver date and version. Click Driver Details for more information. NOTE If driver is not installed, try re-installing the driver or re-installing the adapter hardware and then the driver. Linux Verify if the adapter driver installed successfully using the following commands: • # rpm -qa|grep -i bfa This command prints the names of the Brocade adapter storage driver package (bfa) if installed.
3 Confirming driver package installation Confirming driver installation with Solaris tools Verify if the driver packages installed successfully using the following commands: NOTE Brocade 804 and 1007 adapters are not supported on Solaris systems, so commands in this section do not apply to these adapters. • These commands display information about loaded kernel modules. modinfo|grep bfa modinfo|grep bna If the storage driver package is installed, bfa Brocade Fibre Channel Adapter Driver should display.
Confirming driver package installation 3 Confirming driver installation with VMware tools Verify if the driver installed successfully using the following commands: • The following commands print the names of the Brocade storage driver (bfa) if installed. - For ESX 4.0 and 4.1 systems # rpm -qa|grep -i bfa - For ESX 5.0 systems esxcli software vib list | grep bfa • These commands print the names of the Brocade network driver (bna) if installed. - For ESX 4.0 and 4.
3 Verifying adapter installation # lsmod • This command prints kernel boot messages. Entries for bfa (storage driver) and bna (network driver) should display to indicate driver activity if the hardware and driver are installed successfully. # dmesg • 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.
Installing SNMP subagent 3 • Make sure that all Fibre Channel devices connected through the adapter and associated FCoE or Fibre Channel switch are correctly connected, powered up, and operating correctly. If not powered up, devices will be unavailable. • Verify host system storage, switch, and operating system compatibility using the interoperability matrices on the Brocade adapters website at www.brocade.com/adapters.
3 Updating drivers with HCM Windows systems For Windows systems, use the following steps. 1. Go to the following directory where the SNMP files are installed. c:\program files\brocade\adapter 2. Enter one of the following commands: • brocade_install.bat SNMP=TRUE Installs the SNMP subagent, drivers, and other utilities. • brocade_install.bat SNMP_ONLY=TRUE Installs only the SNMP subagent. 3. Start SNMP services using the following commands.
Updating drivers with HCM 3 To update drivers with HCM, use the following steps: 1. Determine the correct driver package for your host system platform by reviewing Table 9 on page 44. 2. Download the driver package for your host system operating system and platform from the Brocade adapters website using se the following steps. a. Go to the adapters website at www.brocade.com/adapters. b. Navigate to the Downloads page. c.
3 Installing HCM to a host from the HCM Agent Installing HCM to a host from the HCM Agent You can install HCM to any host system from a functioning HCM Agent on a server system. The following are prerequisites for the server system: • The adapter and driver package must be installed. • The HCM agent must be running. Use the following steps to install HCM: 1. Enter the following URL into your host system’s web browser: https://server-host:34568/index.
HCM Agent operations 3 • Starting the agent (agent restarts if system reboots). chkconfig –-add hcmagentservice • Stopping the agent. /usr/bin/hcmagentservice stop • Stopping the agent from restart after system reboots. chkconfig –-del hcmagentservice • Changing the default communication port. Use the following steps. a. Change to the agent installation directory (default is /opt/brocade/adapter/hbaagent/conf). b. Edit abyss.
3 HCM configuration data Managing the HCM Agent on Windows systems Use the following options: • Determining agent operation a. Run the services.msc command to display the Services window. b. Right-click Brocade HCM Agent Service and select Status. • Starting the agent (agent will not restart if system reboots or agent stops unexpectedly) a. Run the services.msc command to display the Services window. b. Right-click Brocade HCM Agent Service and select Start.
Setting IP address and subnet mask on CNAs • • • • • 3 Alias data Setup discovery data Syslog data HCM logging data Support save data Backing up configuration data Use the HCM Backup Data dialog box to back up configuration data before removing HCM. Also, be sure to back up data when the backup message displays when removing software with the Adapter Software Uninstaller. Following are default locations for HCM configuration data: • Versions 1.1.0.8 and above - \HCM\data • Versions 1.1.0.
3 Setting IP address and subnet mask on CNAs Linux Following is an example for using the ifconfig command to set the IP address and subnet mask. Note that a CNA and a Fabric Adapter with ports configured in CNA or NIC mode are typically named “eth0.” ifconfig eth0 193.164.1.10 netmask 255.255.255.0 up VMware Please refer to ESX/ESXi Configuration Guide on network configuration for VMware ESX/ESXi 4.x and 5.0.
Chapter 4 Boot Code In this chapter • Boot support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Boot code updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Boot over SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Boot code updates A single, updatable boot code image, stored in the adapter option read-only memory (option ROM) memory, contains all boot code for supported host platforms. NOTE By default, BIOS and UEFI are enabled on adapter ports for booting over SAN. Boot code updates The adapter boot code contains the following: • PCI BIOS 2.1 or later, PCI firmware 3.
Boot code updates 4 • Viewing the adapter Properties panel in HCM. To view the panel, select the adapter in the device tree, then click the Properties tab in the right pane. For servers with operating system and Brocade adapter drivers installed, you can use BCU commands or HCM directly to update boot code on adapters.
4 Network boot Updating boot code with BCU commands Use the following procedure to update boot code using BCU commands. 1. Download the boot code image zip file (brocade_adapter_boot_fw_.zip) from the Brocade adapters website to a folder on your local drive using the following steps: a. Go to the adapters website at www.brocade.com/adapters. b. Navigate to the adapters Downloads page. c. Select your operating system from the Downloads list to display appropriate download files. d.
Network boot 4 Booting servers over the network can significantly streamline server administration and facilitate server deployment. Instead of manually configuring each individual server, boot images on LAN-based systems can be cloned and assigned to groups of servers at the same time. This not only simplifies initial configuration, but makes ongoing software updates and maintenance much easier to administer.
4 Network boot • TFTP API The TFTP (Trivial File Transfer Protocol) API enables opening and closing of TFP connections and reading packets from and writing packets to a TFTP connection. The PXE client downloads the PXE boot loader from an TFTP server. • UDP API The User Datagram Protocol (UDP) API enables opening and closing of UDP connections and reading packets from and writing packets to a UDP connection.
Network boot 4 • Linux (RHEL) For supported versions later than RHEL 4.9, “nw” drivers support network (PXE) boot. Install these drivers after fc drivers. For RHEL 4.9, network drives are part of a single ISO package. • Linux (SLES) Network drivers are part of a single ISO package. • VMware ESX Network boot is currently not supported. Configuring network boot Configure Network Boot on the adapter using the Brocade PXE BIOS Configuration Utility, BCU commands, and HCM.
4 Network boot NOTE To bypass functions and stop loading BIOS, you must to press X for each port. Press X within 5 seconds to bypass execution of functions displayed on screens. If you press X after 5 seconds, the next function (instead of current function) will be bypassed. 3. Select a port that you want to configure. A screen similar to the following displays showing the port’s current BIOS version, MAC address, and BIOS settings. 4.
Network boot 4 NOTE Enabling VLAN during network boot requires support from the operating system and has not been fully validated due to operating system limitations. 6. Save or exit the configuration utility. • To save the configuration, press the Alt and S keys. • To exit without saving press the Alt and Q keys.
4 Network boot Configuring PXE BIOS using BCU commands You can use BCU commands to configure PXE BIOS for the following: • CNA port • Fabric Adapter port configured in CNA or NIC mode Use BCU commands for the following tasks: • Enable BIOS for PXE boot You must enable BIOS to support network boot for an adapter port. If disabled, the host system cannot boot from network systems. The default setting for the adapter boot BIOS is disabled.
Boot over SAN 4 NOTE For details on using BCU commands, refer to instructions for ethboot in the Brocade Command Utility appendix of the Brocade Adapters Administrator’s Guide. Boot over SAN The “Boot Over SAN” feature allows a host to boot its operating system from a boot device directly attached to the host system or located somewhere on the SAN instead of the host’s local disk. Specifically, this “boot device” is a logical unit number (LUN) located on a storage device.
4 Boot over SAN Brocade BIOS support for boot over SAN The Brocade adapter boot BIOS provides boot support for the Brocade adapters in x86 and x64 host platforms. The BIOS can discover up to 256 storage targets, such as RAID units, and the logical unit numbers (LUNs) on those units when the LUNs are bound to adapter ports.
Boot over SAN 4 NOTE Fabric-based boot LUN discovery (Fabric Discovered) is not supported for booting from direct-attached Fibre Channel targets. - First LUN. The host boots from the first LUN visible to the adapter that is discovered in the fabric. - Flash Values. Boot LUN information will be obtained from flash memory. Note that values are saved to flash when you configure and save them through the BIOS Configuration Utility and BCU.
4 Boot over SAN • Fabric Discovered (also known as Fabric Based Boot LUN Discovery) • First LUN • Flash Values The following parameters, if saved on the adapter during legacy BIOS configuration, will apply if UEFI is enabled on the system: • Port speed (HBAs and Fabric Adapter port configured in HBA mode only) • Enable or disable BIOS If legacy BIOS is enabled on the system, these parameters will apply. Refer to “Brocade BIOS support for boot over SAN” on page 128).
Boot over SAN 4 NOTE Some storage devices need the appropriate host type associated with the logical drive configured for the correct operating system. This is necessary so that the storage device can send the correct format of inquiry data to the host. Refer to your storage system documentation for specific requirements. • Configure the storage system so that the adapter port has exclusive access to the LUN. Accomplish this by binding an adapter port PWWN to a LUN.
4 Boot over SAN Overview Figure 17 on page 133 provides a flow chart for the “Procedures” on page 134 and information elsewhere in this chapter to configure your adapter, host system, and remote boot device for booting over SAN.
Boot over SAN Note: Step numbers reference procedures on the following page. 4 Step 1 · Install adapter hardware in host system. · Install adapter software in host system. Step 2-3 · Verify latest BIOS version on installed adapter. · Verify latest adapter driver installed in host system. Step 4 Install latest boot code and adapter driver if needed. Step 5 Configure host system to boot from adapter. Step 6-8 Bind adapter PWWN to available LUN for boot over SAN.
4 Boot over SAN Procedures The following procedures are illustrated in the flow chart in Figure 17 on page 133. You may be referenced to more detailed sections of this chapter to complete some of these steps. 1. Install the adapter and software into the host system using instructions in Chapter 2, “Hardware Installation” and Chapter 3, “Software Installation”. 2. Verify that the adapter contains the latest BIOS version. You can use HCM or BCU commands. For HCM, perform the following steps. a.
Boot over SAN 4 NOTE If you need to disable the system’s hard drive to allow booting from the adapter and wish to utilize both the boot from SAN feature and your system’s hard drive, refer to your system documentation. Procedures for this configuration are beyond the scope of this publication. 6. Verify that the appropriate storage device is connected to the fabric and functioning. This device must have at least one LUN available that is appropriate for booting your host’s operating system. 7.
4 Boot over SAN Configuring BIOS using the Brocade configuration utility NOTE “Brocade BIOS configuration utility” and “Brocade BIOS configuration menu” are used interchangeably in this manual. The Brocade BIOS Configuration Utility allows you to perform the following operations on selected adapters: • Enable or disable BIOS to support boot over SAN. - You must enable BIOS to support boot over SAN for an adapter port. If disabled, the host system cannot boot from Fibre Channel disk drives.
Boot over SAN 4 Under the Ad No column, 1/0 and 1/1 are the first port and second port respectively on the first installed adapter while 2/0 and 2/1 are the first and second port on the second installed adapter. A maximum of 8 ports can display on a screen, and a maximum of 16 ports are supported by the BIOS Configuration Utility. Select Page Up to go to a previous screen or Page Down to go to the next screen. NOTE To bypass functions and stop loading BIOS, you must to press X for each port.
4 Boot over SAN 4. Select one of the following: • Adapter Settings. Use the Adapter Settings screen to enable BIOS, adapter port speed (HBAs and Fabric Adapter ports configured in HBA mode only), and discovery of boot LUN information from the fabric. You can determine adapter N and PWWN. Proceed to step 5. • Boot Device Settings. Use the Device Settings screen to select the boot target and LUN for booting the host system. Proceed to step 7. 5.
Boot over SAN - TABLE 11 4 Brocade BIOS Configuration Utility field descriptions (continued) Boot LUN • • • Fabric Discovered. When enabled, LUN information, such as the location of the boot LUN, is provided by the fabric (refer to “Fabric-based boot LUN discovery” on page 163). Flash Values. Boot LUN information will be obtained from flash memory. Note that values are saved to flash when you configure and save them through the BIOS Configuration Utility and BCU. First LUN.
4 Boot over SAN 8. Use the Up and Down arrow keys to select a boot device, then use one of the following options to configure boot device settings: • Press C to clear a selected boot device from the list. • Press M to manually edit boot device information, then enter the PWWN and LUN values for the boot device. Press M to exit. • Select a device and press Enter. This displays additional screens that allow you to select discovered LUNs as boot devices.
Boot over SAN 4 10. Select the LUN on the target device you that want to designate as the boot LUN for the host. This must be the same LUN that you bound to the adapter port using the storage system’s management or configuration utility (refer to step 8 under “Procedures” on page 134). NOTE You only need to select the bootable LUN once. After the first boot, the same LUN will be used until changed through the BIOS Configuration Utility. 11. Press Enter.
4 Boot over SAN Configuring BIOS using HCM or BCU commands You can enable or disable BIOS for booting over the SAN, set adapter port speed (HBAs and Fabric Adapter port configured in HBA mode only), display BIOS configuration parameters, select boot LUNs, and enable automatic discovery of the boot LUN from the fabric using HCM dialog box options and BCU commands, NOTE You can only designate bootable devices (LUNs) using the Boot Device Settings feature of the Brocade BIOS Configuration Utility, Configur
Boot over SAN 4 NOTE Fabric-based boot LUN discovery (Fabric Discovered) is not supported for booting from direct-attached Fibre Channel targets. • First Visible LUN - The host boots from the first LUN visible to the adapter that is discovered in the fabric. • User Configured LUNs - Allows the user to select and prioritize the remote target and LUN for booting over SAN. The User Configured LUNs table displays LUNs visible to the adapter.
4 Boot over SAN port_id Specifies the ID of the port for which you want to set the port’s boot from SAN attributes. This could be the adapter_id/port_id, port PWWN, port name, or port hardware path. -s Specifies the speed for the port. Default is autonegotiate. Note that autonegotiate is the only speed option for 10 Gbps CNAs and Fabric Adapter ports configured in CNA or NIC mode. - o: Begins options for obtaining boot LUN information (auto, flash, firstlun).
Boot over SAN 4 NOTE For details on using BCU commands, refer to instructions for enabling boot over SAN using BCU commands in the Host Configuration chapter of the Brocade Adapters Administrator’s Guide.
4 Boot over SAN Configuring UEFI Depending on your UEFI-based host system, different tools may be available to perform the following tasks to configure the adapter values that are stored in adapter flash memory. NOTE UEFI is not supported on the Brocade 804 adapter. • Enable or disable adapter ports for booting over SAN. When enabled, available Fibre Channel devices attach as UEFI devices and obtain UEFI device names.
Boot over SAN 4 4. Enter the following command to display all drivers and controllers that support the driver configuration protocol. drvcfg -c Once the driver initializes, look for entries for the Brocade adapter driver handle that you found in the previous step. In the following example, two controller handles (27 and 28) display for driver handle 25. Each controller represents a port on the adapter.
4 Boot over SAN NOTE You could configure the other adapter port using the drvcfg -s command by keeping the driver handle the same and using the other controller handle (drvcfg -s 25 28). 6. Execute a reset EFI shell command to reinitialize the system. When the system restarts, all available Fibre Channel devices display in map output as the EFI Shell initializes. SAN drives display with “Fibre” as part of the device name. 7.
Boot over SAN 4 Installing Windows Server 2003 and the driver If the LUN you have targeted for booting the host system already has an operating system installed, be sure to use options for reformatting the LUN during Windows Server 2003 installation. Refer to your operating system documentation for details. 1. Driver update disk files are provided for x86 and x64 systems.
4 Boot over SAN 7. When a message displays to insert the disk labeled manufacturer-supplied hardware support disk, insert the Brocade adapter driver update disk that you created in step 3 and press Enter. A list of devices displays. 8. Select Brocade's adapter from the list and press Enter. The following message displays: Setup will load support for the following mass storage device(s): Brocade Fibre Channel Adapter. 9. Press Enter. 10. Remove the driver update disk after the driver update files load.
Boot over SAN c. 4 Download the dud from the “Driver Update Disks (DUDs)” area. 3. Unzip the file and copy to a CD, USB drive, or formatted floppy disk to create the adapter driver update disk. 4. Insert the Windows 2008 operating system installation DVD into the system drive and boot from the DVD. 5. Respond to prompts that display on the Windows installer screens. Be sure to select a Standard (Full Installation) and accept the software license. 6.
4 Boot over SAN Installing Linux RHEL 4.x or 5.x and the driver Use the following steps to install RHEL and the adapter driver on an unformatted disk that you configured as a bootable device when setting up the adapter BIOS or UEFI on the host system. If the LUN you have targeted for booting the host system already has an operating system installed, be sure to use options for reformatting the LUN during Linux installation. Refer to your operating system documentation for details.
Boot over SAN 4 6. When the Driver Disk message box displays the “Do you have a driver disk” prompt, select Yes, then press Enter. ATTENTION You must load the Brocade adapter driver at this stage so that the system can access the boot LUN for Linux installation. 7. From the Driver Disk Source window, select the driver source hdx (where x is the CD or USB drive letter), then press Enter. The Insert Driver Disk window displays. 8.
4 Boot over SAN 1. Refer to “Boot installation packages” on page 49 for a list of these files and the operating systems that support these files. Also refer to “Operating system support” on page 40 for information on operating system support for adapter drivers. 2. Download the Brocade adapter driver update .iso file appropriate for your SLES system from the Brocade adapters website using the following steps: a. Go to the adapters website at www.brocade.com/adapters. b.
Boot over SAN 4 Installing RHEL 6.x or Oracle Enterprise Linux (OEL) 6.x and the driver Use the following steps to install RHEL 6.x, RHEL 6.x U1, OEL 6.x, or OEL 6.x U1 and the adapter driver on an unformatted disk that you configured as a bootable device when setting up the adapter BIOS or UEFI on the host system. If the LUN you have targeted for booting the host system already has an operating system installed, be sure to use options for reformatting the LUN during Linux installation.
4 Boot over SAN 8. When prompted to load the driver, insert the driver update disk (dud) that you created in step 3 into the CD, DVD, or USB drive. 9. Follow system prompts to load the driver and continue with operating system installation. Refer to your system documentation as necessary to format and complete installation on the target boot LUN. 10. Reboot the system. The system will default to the Unbreakable Kernel. The following message may display: No root device found.
Boot over SAN 4 Installation procedure 1. Refer to “Boot installation packages” on page 49 for a list of these files and the operating systems that support these files. Also refer to “Operating system support” on page 40 for information on operating system support for adapter drivers. 2. Download the Brocade adapter driver update .iso file appropriate for your system from the Brocade adapters website using the following steps: a. Go to the adapters website at www.brocade.com/adapters. b.
4 Boot over SAN If devices are configured, a menu should display such as the following: 7. Press “5” to select Apply Driver Updates. 8. Replace the Solaris installation DVD with the install time update CD or USB drive that you created in step 3. ATTENTION You must load the Brocade storage driver at this stage so that the system can access the boot LUN for Solaris installation. 9. When the update completes, press “e” to eject the install time update CD or USB drive containing the driver update. 10.
Boot over SAN 4 NOTE Note that you can use the VMware Image Builder PowerCLI to create a brocade_esx50_.zip offline bundle and brocade_esx50_.iso ESX 5.0 installation image that includes brocade drivers and utilities. Refer to your Image Builder documentation for details on using Image Builder PowerCLI. 1. Refer to “Boot installation packages” on page 49 for a list of driver update files and the operating systems that support these files.
4 Boot over SAN 14. When you reboot the system, be sure to set up BIOS to boot from the LUN where you installed ESX. Installation on systems supporting UEFI The newer IBM 3xxx M2 and Dell 11G x86_64 systems can operate in either UEFI mode or Legacy BIOS mode. There are various differences in loading the operating system and drivers to these systems for HBAs, CNAs, or Fabric Adapters with ports configured in CNA or HBA modes.
Boot over SAN 4 continue and complete SLES 11 installation. Once the installation is complete, the boot loader configuration can be fixed using the yast2->system->boot loader->Section Management->Edit tool. The identity of the proper root file system can be found in the /var/log/boot.msg file, associated with the fall-back message for the failed mount of the root file system.
4 Boot over SAN The driver loads to the system. If the driver update was successful, a “Driver Update OK” or similar message displays: 10. Press Enter. 11. If the system prompts you to update another driver, select BACK, then press Enter. 12. When prompted to insert the SLES 11 product CD #1, insert the CD into the drive and select OK. 13. Continue responding to on-screen instructions and refer to your system documentation as necessary to format and complete installation on the target boot LUN.
Fabric-based boot LUN discovery 4 Linux Driver unloading will fail when the new driver package installs, To make the new driver become effective, perform the following steps. a. Change to the boot directory. All platforms - cd /boot b. Make a backup of the current RAMDISK image. #cp initrd-[kernel_version].img initrd-[kernel_version].img.bk c. Build the RAMDISK image. RHEL #mkinitrd -f initrd-[kernel_version].img [kernel_version] SLES #mk_initrd d. Reboot the system to load the new RAMDISK image.
4 Fabric-based boot LUN discovery NOTE Fabric-based boot LUN discovery is not supported for booting from direct-attached targets. Configuring fabric-based boot LUN discovery (Brocade fabrics) For Brocade fabrics, the following methods are available to store the boot LUN information in the fabric zone database: • Using the Fabric OS bootluncfg command to transparently configure the boot LUN.
Fabric-based boot LUN discovery 4 bcu boot --blunZone -c -p -r -l where: c cfg Specifies boot LUN (use -c BLUN). p port_WWN The hexadecimal WWN of the adapter port connecting to the boot LUN. For example, 10:00:00:05:1e:41:9a:cb. r rport_WWN The hexadecimal WWN of the remote storage target’s port. For example, 50:00:00:05:1e:41:9a:ca. l lun_id | lun# The hexadecimal LUN identification.
4 Fabric-based boot LUN discovery • The “member” command must be specially coded values for the target PWWN and LUN identification (for example, 06:00:00:02:DD:EE:FF:00). To obtain the zone name and member values, you will run the BCU boot --blunZone command from your host system’s command line. Use the following steps to configure fabric-based boot LUN discovery. 1.
Boot systems over SAN without operating system or local drive 4 4. Enter the following command to name the zone for a specific VSAN, for example VSAN 8. switch (config)# zone name [name] where name Use the output from the boot --blunZone command. For example, from the output example shown in step 3, you would use switch (config)# zone name BFA_100000051E419ACB_BLUN vsan 8 5. Enter the following command to add the zone members.
4 Boot systems over SAN without operating system or local drive • WinPE ISO image that you can create for x86 and x64 platform. You can use a WinPE image to boot UEFI-based systems. To create these images, refer to “Creating a WinPE image” on page 169. For more detailed procedures to create a bootable CD or USB drive from the ISO image, refer to documentation for your CD or USB drive burning software.
Boot systems over SAN without operating system or local drive 4 Creating a WinPE image Microsoft Windows Preinstallation Environment (Windows PE) is a bootable tool that provides minimal operating system features for installation, troubleshooting. and recovery. Please refer to the Microsoft Preinstallation Environment User's Guide for more information about Windows PE.
4 Updating Windows driver on adapter used for boot over SAN Updating Windows driver on adapter used for boot over SAN When updating the driver on Windows 2008 systems where the adapter is used for booting over SAN, install the new adapter driver without removing the existing driver. This is the recommended procedure to update drivers.
Chapter 5 Specifications In this chapter • • • • • • Fabric Adapters 171 Converged Network Adapters 179 Host Bus Adapters 187 Fibre Channel standards compliance 192 Regulatory compliance 192 Safety 198 Fabric Adapters The Brocade stand-up Fabric Adapters are low-profile MD2 form factor PCI Express (PCIe) cards, measuring 6.6 in. by 2.731 in. (16.765 cm by 6.93 cm). One and two-port models are available. Ports support 10 GbE, 8 Gbps FC, or 16 FC small form factor pluggable (SFP+) optics.
5 Fabric Adapters • Single Root I/O Virtualization (SRIOV), which provides a total of 256 functions. This includes a maximum of 16 Physical Functions (PFs) and 255 Virtual Functions (VFs) for a dual-port adapter. • Support for 2, 0000 MSI-X interrupt vectors. • Support for INT-X. PCI system values All Brocade Fabric Adapters share a common PCI Vendor ID (VID) value to allow drivers and BIOS to recognize them as supported Fibre Channel and network devices.
Fabric Adapters TABLE 13 5 Fabric Adapter hardware specifications (continued) Feature Description External serial FLASH memory • • Fibre Channel performance 500,000 IOPs (maximum) 1,000,000 IOPS per dual-port adapter Throughput per port (full-duplex mode): • 1600 MB at 16 Gbps • 1600 MB at 8 Gbps • 800 MB at 4 Gbps • 400 MB at 2 Gbps Ethernet performance 10.312 Gbps throughput per port Line rate performance for 700-byte packets. Low latency: receive 1.5us, transmit 2us.
5 Fabric Adapters TABLE 13 Fabric Adapter hardware specifications (continued) Feature Description Supported Ethernet protocols and features • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 174 803.3ae (10 Gbps Ethernet) 802.1q (VLAN) 802.1q (tagging) 802.1P (tagging) 802.1Qaz (enhanced transmission selection) 802.1Qbb (priority flow control) 802.1AB (Link Layer Discovery Protocol) 802.3ad (link aggregation) 802.1p (priority encoding) 802.
Fabric Adapters TABLE 13 5 Fabric Adapter hardware specifications (continued) Feature Description Supported FCoE protocols and features • • • • • Fibre Channel Protocols and features Other adapter features Brocade Adapters Installation and Reference Manual 53-1002144-01 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • VMware VM direct path I/O support LKA (Link Keep Alive) protocol Look ahead split preFIP, FIP 1.03, and FIP 2.0 (FC-BB5 rev.
5 Fabric Adapters Cabling This section describes cabling specifications for Fabric Adapters. Table 20 lists the supported cabling for Ethernet transceivers for stand-up adapters. TABLE 14 GbE transceiver cable specifications Transceiver Cable Minimum Length Maximum Length Ethernet 10 Gbps SR (short range) SFP+ 1490 nm OM1 - 6.25/125 multimode OM2 - 50/125 multimode OM3 - 50/125 multimode OM4 - 50/125 multimode NA 33m (104.98 ft.) 82m (269 ft.) 300m (984.25 ft.) 550 m (1804 ft.
Fabric Adapters 5 NOTE For stand-up adapters, use only Brocade-branded SFP laser transceivers supplied with the adapters Adapter LED operation Figure 19 illustrates LED indicator locations on a Brocade dual-port 1860 (A) and a Brocade single-port (B) stand-up Fabric Adapters. LED indicators for each port are visible through the mounting brackets.
5 Fabric Adapters TABLE 16 LED operation State On Off Fast flashing green2 Power on Link established Receive and Transmit FC activity Off Slow flashing green Off Power on Port in Ethernet mode No link Off On Off Power on Ethernet link established No activity Off On Fast flashing green Power on Link established Receive and Transmit FCoE activity Off Fast flashing green Off Power on Link established Receive and Transmit Ethernet activity only Off Fast flashing green Fast flashing gre
Converged Network Adapters TABLE 17 5 Environmental and power requirements (continued) Property Requirement Power Consumption adapter and optics 9 W typical with SFP running 16 Gbps traffic Operating Voltage 12V Converged Network Adapters Two types of CNAs are available: • Stand-up adapter • Mezzanine adapter The Brocade stand-up CNAs are low-profile MD2 form factor PCI Express (PCIe) cards, measuring 6.60 in. by 2.71 in. (16.77 cm by 6.89 cm).
5 Converged Network Adapters PCI system values All Brocade FCoE CNAs share a common PCI Vendor ID (VID) value to allow drivers and BIOS to recognize them as supported Fibre Channel and network devices. CNAs are also assigned PCI subsystem vendor IDs (SVIDs) and subsystem IDs (SSIDs) to allow drivers and BIOS to distinguish between individual host adapter variants. You can locate PCI device, vendor, and subsystem IDs for the installed FCoE CNAs through your host’s operating system tools.
Converged Network Adapters TABLE 19 5 CNA hardware specifications (continued) Feature Description Supported Ethernet protocols and features • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Brocade Adapters Installation and Reference Manual 53-1002144-01 803.3ae (10 Gbps Ethernet) 802.1q (VLAN) 802.1q (tagging) 802.1P (tagging) 802.1Qaz (enhanced transmission selection) 802.1Qbb (priority flow control) 802.1AB (Link Layer Discovery Protocol) 802.
5 Converged Network Adapters TABLE 19 CNA hardware specifications (continued) Feature Description Supported FCoE protocols and features • • • • • • Other features • • • • • • • • • • • • • • VMware NetIOC VMware VM Direct Path I/O Look-ahead data split LKA (Link Keep Alive) protocol preFIP, FIP 1.03, and FIP 2.0 (FC-BB5 rev. 2 compliant) • FIP discovery protocol for dynamic FCF discovery and FCoE link management. • FPMA and SPMA type FIP fabric login.
Converged Network Adapters 5 Cabling (stand-up adapters) Table 20 lists the supported cabling for adapter transceiver types. TABLE 20 Transceiver and cable specifications Transceiver Cable Minimum Length Maximum Length Ethernet 10 Gbps SR (short range) SFP+ 1490 nm OM1 - 6.25/125 multimode OM2 - 50/125 multimode OM3 - 50/125 multimode OM4 - 50/125 multimode NA 33m (104.98 ft.) 82m (269 ft.) 300m (984.25 ft.) 550 m (1804 ft.
5 Converged Network Adapters Adapter LED operation (stand-up adapters) Figure 19 illustrates LED indicator locations on a Brocade 1020 (A) and a Brocade 1010 (B) stand-up CNA. LED indicators for each port are visible through the mounting brackets. A B Lnk Act 0 PORT 1 PORT Lnk Act FIGURE 19 0 Lnk Act LED locations for Brocade 1020 CNA (A) and Brocade 1010 CNA (B) Table 21 describes operation for the following LEDs visible on the CNA: • Lnk - Link state (up or down).
Converged Network Adapters TABLE 21 5 LED operation Lnk Act Storage State Beacon flashing green Beacon flashing green3 Beacon flashing green3 Port beaconing function. Beacon flashing green Beacon flashing green4 Beacon flashing green4 End-to-end beaconing function. CNA port and port on connected switch beacon. Flashing amber5 Off Off Unsupported SFP. 1. 1 second on / 1 second off 2. 50 msec on / 50 msec off 3. 1 sec on / 250 msec off 4. 1 sec on / 250 msec off 5.
5 Converged Network Adapters Mezzanine CNAs This section provides specifications for mezzanine CNAs. Brocade 1007 CNA Table 23 lists environmental and power specifications for the Brocade 1007 CNA. TABLE 23 Environmental and power requirements for Brocade 1007 CNA mezzanine card Property Requirement Airflow Provided by blade system enclosure. Altitude Operating - 3,048 meters (10,000 ft.) Nonoperating - 12,193 meters (40,000 ft.
Host Bus Adapters TABLE 24 5 Environmental and power requirements for Brocade 1741 CNA mezzanine card Property Requirement Operating Voltage Per PCIe 2.0 specifications Dimensions 3.6 in. by 1.5 in. by 3.3 in. (9.144 cm by 3.81 cm by 8.382 cm) The Brocade 1741 mezzanine adapter conforms to environmental and power specifications for the supported server blades and blade system enclosures where they install. Refer to the documentation provided for these products for more information.
5 Host Bus Adapters • Supports PCI Express specifications Gen2 (PCI Base Specification 2.0) and Gen1 (PCI Base Specification 1.0, 1.1a, and 1.1). • Operates as an x8 lane DMA bus master at 2.5 GHz, full duplex. • Effective data rate on Gen2 systems is 32 Gbps and on Gen1 systems is 16 Gbps. • On-board flash memory provides BIOS support over the PCI bus.
Host Bus Adapters TABLE 26 5 Supported Fibre Channel features (continued) Feature Description Cable connector (stand-up adapters) LC ASIC • • External serial FLASH memory Data Rate Per Port - Full Duplex • • • • • Provides the Fibre Channel functionality for all HBA models. Two on-board processors, each operating at 400 MHz, generate signal timing and link protocol in compliance with Fibre Channel standards.
5 Host Bus Adapters Cabling (stand-up adapters) Table 27 summarizes maximum distances supported for different fiber optic cable types. This table assumes a 1.5 dB connection loss and an 850 nm laser source. TABLE 27 190 Fibre Channel transceiver and cable specifications Transceiver type Speed OM1 (M6) 62.5/125 micron OM2 (M5) 50/125 micron OM3 (M5E) 50/125 micron OM4 (M5F) 50/125 micron Single Mode Media (9 microns) SWL 2 Gbps 150 m (492 ft.) 300 m (984 ft.) 500 m (1640 ft.
Host Bus Adapters 5 Adapter LED operation (stand-up adapters) Figure 20 illustrates LED indicator locations on a Brocade 825 and a Brocade 815. LED indicators for each port are visible through the mounting brackets. Since the Brocade 825 operates at speeds up to 8 Gbps, each port has a 1|2, 4, and 8 Gbps LED. The 4 Gbps models, such as the Brocade 415 and Brocade 425, have a 1|2 and 4 Gbps LED for each port.
5 Fibre Channel standards compliance Environmental and power requirements This section provides environmental and power specifications for the stand-up and mezzanine HBAs. Stand-up HBAs The following table provides environmental and power specifications for the stand-up HBAs. TABLE 29 Environmental and power requirements Property Requirement Airflow None required.
Regulatory compliance • • • • • • 5 425 HBA 815 HBA 825 HBA 1010 CNA 1020 CNA 1860 Fabric Adapter FCC warning (US only) This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
5 Regulatory compliance VCCI statement (Japan) This is Class B product based on the standard of the Voluntary Control Council For Interference by Information Technology Equipment (VCCI). If this equipment is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual. BSMI warning (Republic of Taiwan) CE statement ATTENTION This is a Class B product.
Regulatory compliance 5 Laser compliance This equipment contains Class 1 laser products and complies with FDA Radiation Performance Standards, 21 CFR Subchapter I and the international laser safety standard IEC 825-2. CAUTION Use only optical transceivers that are qualified by Brocade Communications Systems, Inc. and comply with the FDA Class 1 radiation performance requirements defined in 21 CFR Subchapter I, and with IEC 825-2.
5 Regulatory compliance Environmental and safety compliance This section provides international environmental and safety compliance notices for Brocade adapters. Environmental Protection Use Period (EPUP) Disclaimer In no event do the EPUP logos shown on the product and FRUs alter or expand that warranty that Brocade provides with respect to its products as set forth in the applicable contract between Brocade and its customer.
Regulatory compliance TABLE 31 5 Hazardous Substances/Toxic Substances (HS/TS) concentration chart Brocade Adapters Installation and Reference Manual 53-1002144-01 197
5 Regulatory compliance Safety Because these boards are installed in a PCIe bus slot, all voltages are below the SELV 42.4 V limit.The adapters are recognized per Bi-Nat UL/CSA 60950-1 1st Ed. or later for use in the US and Canada. They also comply with IEC 60950-1 and EN60950-1.
Regulatory compliance 5 Mezzanine adapters The regulatory information in this section pertains to the following mezzanine adapters. • 804 HBA • 1007 CNA • 1741 CNA Brocade 804 HBA For the Brocade 804 HBA, refer to the regulatory compliance information in the Mezzanine Card Installation Instructions that ship with your adapter and to information in your blade system enclosure documentation.
5 Regulatory compliance VCCI statement (Japan) This is Class A product is based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance might arise. When such trouble occurs, the user might be required to take corrective actions. CE statement ATTENTION This is a Class A product.
Regulatory compliance 5 Safety and EMC regulatory compliance Table 30 lists the regulatory compliance standards and certifications for which the adapter is certified.
5 202 Regulatory compliance Brocade Adapters Installation and Reference Manual 53-1002144-01
Appendix A Adapter Configuration In this appendix • Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Storage instance-specific persistent parameters . . . . . . . . . . . . . . . . . . . . • Storage driver-level parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Network driver parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Storage instance-specific persistent parameters TABLE 33 Adapter instance-specific parameters Function Parameter Default Value Possible Values BCU Command Notes authorization algorithm bfa#-auth-algo 1 1: MD5 2: SHA1 3: MS 4: SM auth --algo Not supported in Solaris. authorization policy bfa#-auth-policy off 0: on 1: off auth --policy Not supported in Solaris. authorization secret bfa#-auth -secret NA min chars - 0 max chars - 256 auth --secret Not supported in Solaris.
Storage instance-specific persistent parameters TABLE 33 A Adapter instance-specific parameters (continued) Function Parameter Default Value Possible Values BCU Command port speed bfa#-port-speed 0 0: auto select port --speed 1: 1 Gbps (HBAs) 2: 2 Gbps (HBAs) 4: 4 Gbps (HBAs) 8: 8 Gbps (HBAs) 16:16 Gbps (HBAs) 10: 10 Gbps (CNAs) Notes Brocade 425 and 415, and 804 support 1, 2, 4, and 8 Gbps Brocade 1860 support 2,4,8, and 16 Gbps 8 Gbps HBAs support 1 Gbps at the driver level, but not in a BIOS
A Storage driver-level parameters Modifying PCIe max read request size Refer to the comment section in the /kernel/drv/bfa.conf file on your system for an example. Storage driver-level parameters The driver-level configuration parameters are global parameters used by all storage driver instances. The default values for the driver configuration parameters are compiled into the driver. NOTE These parameters are should only be changed by power users with great caution.
Storage driver-level parameters TABLE 34 A Linux and VMware driver configuration parameters Parameter Default Value Notes os_patch NULL OS patch level. reqq_size 256 Number of elements in each request queue (used for driver-tofirmware communication). rport_del_timeout 30 (seconds) Delay (in seconds), after which an offline remote port will be deleted. rspq_size 64 Number of elements in each request queue (used for firmware-todriver communication).
A Storage driver-level parameters Examples Following is an example to set the LUN queue depth. esxcfg-module -s 'lun_queue_depth=1' bfa Following is an example to disable FDMI. esxcfg-module -s 'fdmi_enable=0 bfa' bfa Important notes Observe these notes when modifying driver configuration parameters: • The esxcfg-module reads and updates from the file /etc/vmware/esx.conf. • Editing this file directly is not recommended. • Be careful not to overwrite the existing options.
Storage driver-level parameters A • If the device icon display in Device Manager does not change to indicate that each HBA port device is disabled and if a message displays when you attempt to disable the devices that your hardware settings have changed and you must restart your computer for changes to take effect, confirm that the hcmagent.exe (Brocade HCM Agent Service) is not running on the host and that there are no open handles to file systems on disks accessed through the adapter.
A Storage driver-level parameters • • • • key = ioc_auto_recover, value range [0-1] default = 1 key = rport_del_timeout, value range [0-90] default = 90 key = msix_disable, value range [0-1] default = 1 key = fdmi_enable, value range [0-1) default = 1 Following is an example for disabling FDMI. bcu drvconf --key fdmi_enable --val 0 Solaris driver configuration parameters Table 36 describes the Solaris configuration parameters. NOTE Brocade 804 and 1007 adapters are not supported on Solaris systems.
Network driver parameters A Network driver parameters The driver configuration parameters are global parameters used by all network driver instances. The default values for the driver configuration parameters are compiled into the driver. Network drivers are only used for CNAs and for Fabric Adapter ports configured in CNA or NIC mode. The driver-level configuration values discussed in this section are in the following locations on your system: • Linux - /etc/modprobe.conf • VMware - /etc/vmware/esx.
A Network driver parameters TABLE 37 Network driver configuration parameters (continued) Function Default Value Possible Values Method to Configure Notes Locally Administered Address N/A Hexadecimal value for MAC address Device Manager Overrides the burned-in MAC address. Priority and VLAN Disable Enable Disable Device Manager Enables hardware-assisted VLAN tagging. Receive Buffers 32 32-1024 Device Manager Tunes receive buffer value.
Network driver parameters A Managing Windows driver configuration with Device Manager Use the Windows Device Manager to configure the following parameters: • • • • • • • • • • • • • Autorecovery Flow Control Interrupt Moderation IPv4 Checksum Offload Jumbo Packet Size Large Segmentation Offload V1 IPv4 (LSOv1) Large Segmentation Offload V2 IPv4 (LSOv2) Large Segmentation Offload V2 IPv6 (LSOv2) Locally Administered Network Address Priority and VLAN support Receive Side Scaling (RSS) TCP/UDP IPv4 Checksu
A Network driver parameters [ FIGURE 21 Properties dialog box for adapter port (Advanced tab) 5. Select the Property that you want to configure and select the Value. 6. Click OK when finished. 7. Repeat steps 2 through 5 for each port that you want to configure. NIC Teaming When adapter ports are configured as members of NIC teams, an instance of the team name (Team#Team_Name) appears in the Device Manager.
Network driver parameters FIGURE 22 A Advanced Properties dialog box for team An instance of a physical port that is part of a team displays in the Device Manager as “Team#Team Name” followed by the physical adapter name, for example, “Team#Failover Brocade 10G Ethernet Adapter.” Right-clicking this instance displays a Properties dialog box labeled “Team#Failover Brocade 10G Ethernet Adapter.” The Advanced tab contains the same parameters as shown in Figure 21 on page 214 for the physical port.
A Network driver parameters Linux Table 38 describes the instance-specific network configuration parameters available for Linux hosts. TABLE 38 Network driver configuration parameters Function Default Value Possible Values Method to Configure Notes Log Level 3 0 = EMERG 3 = Warning 6 = INFO 7 = DEBUG Module parameter (bnad_log_level) Linux log level Interrupt Moderation (Set for receive interrupts) On On Off ethtool -C command Reduces context switching and CPU utilization.
Network driver parameters A Managing Linux driver configuration with ethtool Following are examples of using the ethtool K commands to change adapter settings for driver parameters: • TCP-UDP Checksum Offload To enable or disable TCP-UDP checksum offload, enter the following command: ethtool -K|--offload ethX [rx on|off] [tx on|off] where: ethx Adapter position in server. For example, eth0 is the first Ethernet interface found in the system, eth1 is the second, eth2 is the third, and so on.
A Network driver parameters rx Receive on or off tx Transmit on or off Managing Linux driver configuration with module parameter Either the driver configuration parameter values can be loaded with the driver or can be set in /etc/modprobe.conf before loading the driver. Following are examples of using modprobe to change network driver configuration: • This example, sets the Linux logging level to debugging mode and loads the driver with the parameter value.
Network driver parameters A VMware Table 39 describes the instance-specific network configuration parameters available for VMware hosts. You can list all module parameters that you can configure for the network driver using the following command. vmkload_mod -s bna TABLE 39 Network driver configuration parameters Function Default Value Possible Values Method to Configure Notes Jumbo Packet Size 1500 1500-9000 esxcfg-vswitch command • • • Sets MTU size.
A Network driver parameters TABLE 39 Network driver configuration parameters (continued) Function Default Value Possible Values Method to Configure Notes Other NetQueue Configuration • Number of NetQueues and filters • Heap values NA NA esxcfg-module Refer to “Configuring NetQueue” on page 221. Legacy Ethernet pause NA VM Client interface autoneg: off, on rx: off, on tx: off, on ethtool -A command Flow control mechanism for Ethernet.
Network driver parameters IP address IP address for VMkernel NIC subnet mask Subnet mask for VMkernel NIC MTU size MTU size (1500-9000 kb) A • Following is an example to configure a VLAN ID for a port group on a specific virtual switch. esxcfg-vswitch -v -p where: VLAN ID ID of 0-4094. A value of 0 disables VLANs. port group name Name of port group you have configured for virtual switch.
A Network driver parameters You can use ethtool to obtain hardware statistics to verify traffic over different receive and transmit queues. You can also use the VMware vsish utility to display current NetQueue information, such as maximum number of queues, number of active queues, and default queue identification. Use the following example procedures to enable or disable NetQueue, change the number of NetQueues and filters, and to set system heap values appropriately for using NetQueue and jumbo frames.
Network driver parameters TABLE 40 A NetQueues and filters per NetQueue for CNAs CPUs NetQueues (no default) NetQueues (jumbo) Receive Filters per NetQueue 1 0 0 0 2 1 1 63 4 3 3 21 8 7 3 9 16 7 3 9 32 7 3 9 64 7 3 9 128 7 3 9 Table 41 summarizes NetQueues and Receive Filters per NetQueue values per number of CPUs for Fabric Adapter ports configured in CNA mode.
A Network driver parameters Enabling jumbo frames for Solaris For Solaris 10, you can enable support for jumbo packet frames and set the MTU size for these frames up to 9000. Use the following steps: 1. Add the following line to the bna.conf file. This file is located in /kernel/drv/bna.conf. bfa_port-mtu= where: x BNA (Brocade Network Adapter) driver instance number mtu_value 1500 to 9000 NOTE Size must not be greater than size set on the FCoE switch. 2. Reload the driver. 3.
Appendix B MIB Reference In this appendix Table 42 provides information on the MIB groups and objects that support the Simple Network Management Protocol for CNA adapters and Fabric Adapter ports configured in CNA mode. For more information on adapter SNMP support, refer to “Simple Network Management Protocol” on page 34.
B In this appendix TABLE 42 Supported MIB groups and objects for SNMP (continued) Group MIB Objects Function Physical Group (Port Attributes) portAdapterIndex Adapter index of the port portIndex Port Index portLinkStatus Port link status portDuplexMode Port duplex mode portAutonegotiateMode Port autonegotiate mode enabled or disabled portMaxSpeed Max speed of the port ethAdapterIndex Adapter Index of the interface ethPortIndex Interface port index ethLargeReceiveOffload Enabled or d
In this appendix TABLE 42 B Supported MIB groups and objects for SNMP (continued) Group Statistics Group (VLAN Statistics) Logical Group (VLAN Attributes) Logical Group (Team Attributes) MIB Objects Function portMacRxBytes Number of bytes received portMacRxPackets Number of packets received portMacTxBytes Number of bytes transmitted portMacTxPackets Number of packets transmitted portRxCRCErrors Number of packets received with CRC errors portHeartbeatErrors Number of heartbeat errors vL
B In this appendix TABLE 42 Supported MIB groups and objects for SNMP (continued) Group Logical Group (Team Members) Traps and Events Group 228 MIB Objects Function teamSpeed Team speed teamAdapterIndex Index of the adapter teamPortIndex Index of the port teamMemberType Type of the team member teamMemberStatus Status of the member teamMemberMACAddress MAC address of the member vLANAdded VLAN added vLANRemoved VLAN removed teamMemberAdded Team member added teamMemberRemoved Team
Appendix List of Acronyms C Following is a list of acronyms used in this publication and their meaning.
C List of Acronyms CFFh Compact Form Factor Horizontal CFFv Compact Form Factor Vertical CIM Common Information Model CIOv Channel I/O Virtualization CNA Converged Network Adapter DCBCXP Data Center Bridging Capability Exchange Protocol DHCP Dynamic Host Configuration Protocol (DHCP) DCB Data Center Bridging DCBX Data Center Bridging Exchange DMA Direct Memory Access EMC Electromagnetic Compatibility EPUP Environmental Protection Use Period ESD Electrostatic Discharge ETS Enhanced Transmission Selection F
List of Acronyms C FCoE Fibre Channel over Ethernet FCP Fibre Channel Protocol FC-SP Fibre Channel-Security Protocol FDMI Fabric Device Management Interface FIP FCoE Initialization Protocol FTP File Transfer Program GUI Graphical User Interface GZME Get Zone Member List HBA Host Bus Adapter HCM Host Connectivity Manager HS/TS Hazardous Substances/Toxic Substances initrd Initial RAM disk IRQ Interrupt Request ISA/EISA Industry Standard Architecture/Extended Industry Standard Architecture KVM Keyboard, Vide
C List of Acronyms LUN Logical Unit Number iSCSI Internet Small Computer System Interface ISO International Standards Organization LACP Link Aggregation Control Protocol LSO Large Send Offload LVD Low Voltage Directive MAC Media Access Control MSI Message Signaled Interrupts MSI-X Message Signaled Interrupts Extended MTU Maximum Transmission Unit NBP Network Bootstrap Program NDIS Network Driver interface Specification NETIOC Network I/O Control NIC Network Interface Card NPIV N_Port ID Virtualization NWW
List of Acronyms C OEL Oracle Enterprise Linux PF Physical function PHY Physical layer PFC Pre-Priority-Based Flow Control( PCI Peripheral Component Interconnect PCIe Peripheral Component Interconnect Express POM Pluggable Optical Module PWWN Port World Wide Name PXE Preboot eXecution Environment QoS Quality of Service RHEL Red Hat Enterprise Linux RPSC Remote Port Speed Capability SAN Storage Area Network SCP Secure Copy SFCB Small Footprint CIM Broker SFP Small Form Factor Pluggable Brocade Adapters In
C List of Acronyms SLES SUSE Linux Enterprise Server SMI-S Storage Management Initiative Specification SoL Serial Over LAN SSID Subsystem ID SVID Subsystem Vendor Identification SRIOV Single Root I/O Virtualization (SRIOV) TCP Transmission Control Protocol TFTP Trivial File Transfer TLV type-length-values TSO TCP Segmentation Offload TRL Target Rate Limiting UAC User Account Control UDP User Datagram Protocol UEFI Unified Extensible Firmware Interface (UEFI) boot support UNDI Universal Network Device Inte
List of Acronyms C VCCI Voluntary Control Council For Interference by Information Technology Equipment VID Vendor ID vHBA Virtual Host Bus Adapter VM Virtual Machine vNIC Virtual Network Interface Card VLAN Virtual Local Area Network VMQ Virtual Machine Queue WFAS Windows Firewall and Advanced Service WHQL Windows Hardware Quality Lab WinPE Windows Preinstallation Environment WMI Windows Management Initiative WoL Wake on LAN WWN World-Wide Name WWPN World-Wide Port Name Brocade Adapters Installation and
C 236 List of Acronyms Brocade Adapters Installation and Reference Manual 53-1002144-01
Index Numerics 1007 adapters, 199 804 adapters, 199 A acronyms used in manual, 229 adapter boot code, 42, 118 event message files, 43 hardware supported, xiii management BCU, 53 CIM Provider, 43 HCM, 42 software downgrading, 88 upgrading, 87 software installer, 68 software supported, xiii adapters, 199 configuring, 203 connecting to switch or storage, 58 general features, 16 management HCM, 32 management using BCU, 32 AnyIO mode changing, 3 description, 2 B BCU, 31, 32, 35, 38 BCU commands using, 53 usin
C Canadian requirements 1741 adapters, 200 stand-up adapters, 194 CE statement 1741 adapters, 200 stand-up adapters, 194 checksum offloads, 22 CIM Provider, 39, 43 CIM Provider installation package, 43 CNA boot image, 50 DCB features, 22 driver packages, 37 environmental and power requirements, 178 Ethernet features, 22 fabric OS support, xiv FCoE features, 20 firmware, 38 hardware specifications, 180 host compatibility, 5, 10, 12 host support, xv illustration, 7 installing driver package with software inst
drivers install and remove with BASI, 68 install and remove with install script on Solaris, 97 intermediate, 23 IPFC, 21 update with HCM, 110 E electrostatic discharge precautions, 55 enhanced transmission selection, 22 environmental and power requirements CNA mezzanine cards, 186 stand-up CNAs, 178, 185 stand-up Fabric Adapters, 178 stand-up HBAs, 192 environmental and safety compliance EPUP disclaimer, 196 RoHS statement, 196 ESX systems BCU commands, 53 Ethernet flow control, 23 Ethernet management BCU,
HBA boot image, 50 driver packages, 37 features, 27 firmware, 38 hardware specifications, 188 host and fabric support, 31 host support, 15 illustration, 8, 9, 13, 14 installing driver package with software installer, 69 IOPs per port, 27 LED operation, 191 low-profile bracket, 8, 9, 13, 14 management applications, 31, 35 management with BCU, 38 PCI system values, 188 PCIe interface, 187 PCIe support, 15 physical characteristics, 187 product overview, 12 PWWN, xxii serial number, xxii software downloading fr
K N KCC statement 1741 adapters, 199 stand-up adapters, 193 N_Port trunking, 29 requirements, 30 NetQueues, 27 NetQueues and filters CNAs, 222 Fabric Adapters, 223 NetQueues, configuring, 221 network boot, 25 configuring BIOS with BCU commands, 126 configuring BIOS with HCM, 125 configuring with BIOS utility, 123 driver support, 122 general requirements, 122 network boot introduction, 120 network driver, 37 configuring parameters, 211 network driver configuration parameters Linux, 216 VMware, 219 Windows
PCI system values CNA, 180 Fabric Adapter, 172 HBA, 188 PCIe interface, 19 CNA, 179 Fabric Adapter, 171 HBA, 187 PCIe support CNA, 11 Fabric Adapter, 5 HBA, 15 persistent binding, 20 PHY firmware, updating, 63 PHY module firmware determining firmware version, 63 updating, 63 physical characteristics of CNAs, 179 physical characteristics of Fabric Adapters, 171 physical characteristics of HBAs, 187 preinstall option, 92 product information resources, xx product overview, 5, 12 publications download, 52 PWWN
software compatibility, 4, 10, 15 downloading from website, 52 driver package, 37 HCM, 42 installation packages, 43 installing, 65 installing with scripts and commands, 89 installing with software installer, 68 overview, 37 removal with scripts and commands, 89 removing with software installer, 83 using software uninstaller commands, 85 software installation options, 48 scripts, 38 software installation options, 43 software installation packages, 44 software installer, 38, 43, 48 command options, 78 command
V VCCI statement 1741 adapter, 200 stand-up adapters, 194 verifying HBA installation, 108 virtual channels per port, 29 VLAN, 26 VLAN configuration persistence, 27 VLAN filtering, 26 VLAN tagging, 26 VMware installation on boot LUN, 158 VMware systems firewall issue, 67, 90 installing driver on ESX, 100 installing driver on ESXi, 101 installing driver with script, 100 installing HCM, 66 modifying agent operation, 112 network driver configuration parameters, 219 removing driver with script, 100 storage drive
