user manual

ManualsBrandsQ-Logic ManualsNetwork CablesQLogic Network Cables 8100 SERIES

FE0254601-00 A

User’s Guide

Converged Network Adapter

8100 Series

Summary of content (348 pages)

PAGE 1
User’s Guide Converged Network Adapter 8100 Series FE0254601-00 A
PAGE 2
User’s Guide Converged Network Adapter 8100 Series Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are for illustrative purposes only.
PAGE 3
Table of Contents Preface What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
User’s Guide Converged Network Adapter 8100 Series Adapters FCoE Network Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
User’s Guide Converged Network Adapter 8100 Series Adapters Removing the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Driver Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining the QLogic Firmware/Boot Code. . . . . . . . . . . . . . . . . . . . . Determining the Installed Firmware Version . . . . . . .
PAGE 6
User’s Guide Converged Network Adapter 8100 Series Adapters Upgrading the Boot Code (Firmware) . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the Boot Code Using the QConvergeConsole GUI . . Using QLogic BIOS and UEFI Utilities . . . . . . . . . . . . . . . . . . . . Management Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining the QLogic Adapter Management Tools . . . . . . . . . . . . . . . Installing and Launching QConvergeConsole . . . . . .
PAGE 7
User’s Guide Converged Network Adapter 8100 Series Adapters PXE Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites for PXE Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PXE Protocol Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the NIC in a Linux Environment . . . . . . . . . . . . . . . . . . . . . . . . NIC Driver Parameters (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
User’s Guide Converged Network Adapter 8100 Series Adapters 7 Configuring FCoE in a Windows Environment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation Mode (ZIO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupt Delay Timer (IDT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
User’s Guide Converged Network Adapter 8100 Series Adapters Online Storage Configuration and Reconfiguration . . . . . . . . . . . . . . . . . . . Adapter FCoE Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation Mode (ZIO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupt Delay Timer (zio_timer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Queue Depth (qla2xmaxqdepth) . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
User’s Guide Converged Network Adapter 8100 Series Adapters 9 Offline Utilities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
User’s Guide Converged Network Adapter 8100 Series Adapters List of Figures Figure Page i Illustration of Sample Motherboard and Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 1-1 Encapsulated Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-2 Combined SAN and LAN Function on One Converged Network Adapter . . . . . . . . 1-3 1-3 FCoE Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
User’s Guide Converged Network Adapter 8100 Series Adapters 3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45 3-46 3-47 3-48 3-49 3-50 3-51 3-52 3-53 3-54 3-55 3-56 3-57 3-58 3-59 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 xii Install Additional Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 13
User’s Guide Converged Network Adapter 8100 Series Adapters 4-20 4-21 4-22 4-23 4-24 4-25 4-26 4-27 4-28 4-29 4-30 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-26 5-27 5-28 5-29 5-30 5-31 5-32 Install the QConvergeConsole: Directory Containing Installer . . . . . . . . . . . . . . . . . Install the QConvergeConsole: Terminal Window—Verify Permission to Execute . Install the QConvergeConsole: Run in Terminal Selection . . . . . . . .
PAGE 14
User’s Guide Converged Network Adapter 8100 Series Adapters 5-33 5-34 5-35 5-36 5-37 5-38 5-39 5-40 5-41 5-42 5-43 5-44 5-45 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 6-25 6-26 6-27 6-28 6-29 6-30 6-31 6-32 xiv Add Hardware—Select Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Hardware—Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
User’s Guide Converged Network Adapter 8100 Series Adapters 6-33 6-34 6-35 6-36 6-37 6-38 6-39 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 8-1 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11 8-12 8-13 8-14 8-15 8-16 8-17 8-18 8-19 8-20 8-21 8-22 8-23 8-24 9-1 9-2 9-3 9-4 Examine the Bond0 Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ifconfig Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying that the VLAN 802.
PAGE 16
User’s Guide Converged Network Adapter 8100 Series Adapters 9-5 9-6 9-7 9-8 9-9 A-1 Selectable Boot Setting Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Fibre Channel Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Adapter Settings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
User’s Guide Converged Network Adapter 8100 Series Adapters 8-19 8-20 8-21 8-22 8-23 8-24 8-25 8-26 8-27 9-1 9-2 9-3 9-4 A-1 FC HBA Change LUN State Utility Package Files . . . . . . . . . . . . . . . . . . . . . . . . . . FC HBA Change LUN State Utility Command Line Options . . . . . . . . . . . . . . . . . . HBA Change LUN State Utility Command Examples . . . . . . . . . . . . . . . . . . . . . . . Set Device Command Timeout Utility Package Files . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 18
User’s Guide Converged Network Adapter 8100 Series Adapters xviii FE0254601-00 A
PAGE 19
Preface This guide provides detailed instructions on the installation, configuration, and troubleshooting of QLogic 8100 Series Converged Network Adapter for Windows®, Linux®, and VMware®. It also provides details on the use of QLogic adapter features to enhance the value of server virtualization using VMware ESX™/ESXi 4.0. Such features include virtual adapter configuration using N_Port ID virtualization (NPIV) and boot-from-SAN configuration.
PAGE 20
Preface Intended Audience  Section 7 describes the characteristics, configurations, and features of the QLogic 8100 Series Converged Network Adapter FCoE function for Windows.  Section 8 describes the characteristics, configurations, and features of the QLogic 8100 Series Converged Network Adapter FCoE function for Linux.  Section 9 describes offline adapter configuration and Flash programming utilities with the adapter multi-boot code for advanced users.
PAGE 21
Preface License Agreements       Text in blue font indicates a hyperlink (jump) to a figure, table, or section in this guide, and links to Web sites are shown in underlined blue. For example:  Table 9-2 lists problems related to the user interface and remote agent.  See “Installation Checklist” on page 3-6.  For more information, visit www.qlogic.com. Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings.
PAGE 22
Preface Technical Support Technical Support Customers should contact their authorized maintenance provider for technical support of their QLogic products. QLogic-direct customers may contact QLogic Technical Support; others will be redirected to their authorized maintenance provider. Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.
PAGE 23
Preface Legal Notices Knowledge Database The QLogic knowledge database is an extensive collection of QLogic product information that you can search for specific solutions. We are constantly adding to the collection of information in our database to provide answers to your most urgent questions. Access the database from the QLogic Support Center: http://support.qlogic.com. Legal Notices Warranty For warranty details, please check the QLogic Web site at http://www.qlogic.com/Support/warranty.aspx.
PAGE 24
Preface Legal Notices EMI and EMC Requirements FCC Part 15 compliance: Class A (QLE8xxx) FCC compliance information statement: 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. ICES-003 compliance: Class A (QLE8xxx) This Class A digital apparatus complies with Canadian ICES-003.
PAGE 25
Preface Legal Notices MIC: Class A (QLE81xx) Korea MIC Class Korean KCC: KN22 KN24(08.05.
PAGE 26
Preface Legal Notices xxvi FE0254601-00 A
PAGE 27
Quick Start Installation Instructions This Quick Start section describes how to install and configure your new QLogic Converged Network Adapter in four simple steps:  Step 1. Verify the Package Contents.  Step 2. Install the Adapter Hardware.  Step 3. Install the Adapter Drivers.  Step 4. Install QConvergeConsole Management Tools. CAUTION! Keep the adapter in the antistatic bag until installation. The adapter contains parts that can be damaged by electrostatic discharge (ESD).
PAGE 28
Quick Start Step 3. Install the Adapter Drivers 4. Pull out the slot cover (if any) by removing the screw or releasing the lever. 5. Install the low-profile bracket (if required). 6. Grasp the adapter by the top edge and seat it firmly into the appropriate slot (see the illustration below). 7. Refasten the adapter’s retaining bracket using the existing screw or lever. 8. Close the computer cover. 9. Plug the appropriate Ethernet cable (either copper or optical) into the adapter. 10.
PAGE 29
Quick Start Step 4. Install QConvergeConsole Management Tools 4. On the download page under Drivers, select the appropriate driver and download it to your system. 5. Follow the instructions provided in the driver read me file for installing the downloaded driver. Step 4. Install QConvergeConsole Management Tools To install the QConvergeConsole web management interface: 1. Go to the QLogic Driver Downloads/Documentation page at http://driverdownloads.qlogic.com. 2.
PAGE 30
Quick Start Additional Resources xxx FE0254601-00 A
PAGE 31
1 Product Overview  What is a Converged Network Adapter?  What is Enhanced Ethernet?  What is Fibre Channel over Ethernet (FCoE)?  QLogic Converged Network Adapter  Hardware Components  Software Components  Adapter Specifications What is a Converged Network Adapter? A Converged Network Adapter is a multifunction adapter that combines the capabilities of a Fibre Channel adapter and an Ethernet NIC.
PAGE 32
1–Product Overview What is Enhanced Ethernet? What is Enhanced Ethernet? Standard Ethernet is a best-effort network that may drop packets or deliver packets out of order when the network is busy or congested, resulting in retransmissions and time-outs. The SCSI payload carried by the Fibre Channel protocol does not react well to dropped or out-of-order packets. Therefore, standard Ethernet is not an acceptable choice to carry Fibre Channel payloads.
PAGE 33
1–Product Overview QLogic Converged Network Adapter Because the transmitting Fibre Channel frames require a lossless transport, an Ethernet network that transports FCoE frames must also provide the same lossless characteristics. Priority flow control (PFC) provides these lossless characteristics. PFC is a revised implementation of the IEEE 802.3X Ethernet standard, known as Pause, and is defined by the IEEE 802.1Qbb standard.
PAGE 34
1–Product Overview FCoE Network Deployment Table 1-2 describes the QLogic 8100 series Converged Network Adapters for standard servers. Table 1-2. 8100 Series Converged Network Adapters Model Ports Media Bus Speed PCIe Gen2 PCIe Gen1 Bus Width PCIe Gen2 PCIe Gen1 Bus Type I/O Rate QLE8150 Single Copper 5.0GHz 2.5GHz x4 x8 PCIe 10Gb QLE8152 Dual Copper 5.0GHz 2.5GHz x4 x8 PCIe 10Gb QLE8140 Single Optical 5.0GHz 2.5GHz x4 x8 PCIe 10Gb QLE8142 Dual Optical 5.0GHz 2.
PAGE 35
1–Product Overview Hardware Components In Figure 1-3, the FCoE adapter communicates to existing native Fibre Channel storage because of the translation capability of the switch. Figure 1-3. FCoE Deployment Hardware Components A typical 8100 Series Adapter has the following major components1: 1  ASIC (reduced instruction set computer (RISC) processor)  Nonvolatile memory (Flash)  NVRAM  Transceivers (SFP+)  LEDs Some adapters may have additional components not shown in this list.
PAGE 36
1–Product Overview Hardware Components Figure 1-4 shows the hardware components of a QLogic 8100 Series Adapter. Table 1-3 describes the 8100 Series Adapter components. Figure 1-4. 8100 Series Adapter Components Table 1-3. 8100 Series Adapter Components Hardware Component 1-6 Function ASIC The Converged Network Controller, also known as the intelligent storage peripheral (ISP) controller, is the heart of the adapter.
PAGE 37
1–Product Overview Hardware Components Table 1-3. 8100 Series Adapter Components (Continued) Hardware Component Function Transceivers Each transceiver is a removable device that functions both as transmitter and as a receiver. A transceiver and cable connect the adapter to other devices. A transceiver can be a QLogic-branded SR (short range), optical transceiver, or copper cables. For a list of QLogic approved copper cables, visit http://www.qlogic.com/Resources/Pages/Resources.
PAGE 38
1–Product Overview Hardware Components Figure 1-5. Driver Model Boot Code Boot code resides in the Flash memory on the adapter. The primary function of the boot code is to communicate with an external boot device before the operating system takes control when booting from a storage device or a pre-eXecution environment (PXE) boot server attached to the QLogic Converged Network Adapter. This type of configuration is called PXE boot (LAN) or boot from SAN.
PAGE 39
1–Product Overview Hardware Components Firmware The firmware module performs most of the FCoE and Ethernet protocol-related functions, thus freeing the system CPU and memory resources from protocol processing. This efficiency saves runtime system resources, such as CPU and memory. For the QLogic 8100 Series Adapter, the firmware comes as part of the multi-boot image, which comprises the boot code, FCoE firmware, message passing interface (MPI) firmware, and various offline utilities.
PAGE 40
1–Product Overview Hardware Components Table 1-4. Software and Firmware Components Component (QLogic Windows FCoE Driver Operating System Supported a Windows Windows NIC Driver Red Hat RHEL Novell SLES Linux NIC Driver (qlgc) QConvergeConsole Web Management GUI QConvergeConsole CLI QLogic SuperInstaller for Windows Install the teaming driver only if the teaming function is required. NIC management is provided by Windows Property Pages through Device Manager and QConvergeConsole CLI.
PAGE 41
1–Product Overview Hardware Components Table 1-4. Software and Firmware Components (Continued) Component (QLogic QLogic SuperInstaller for Linux Operating System Supported a Comments Red Hat RHEL Linux Utility that installs: Novell SLES  FC-FCoE and Ethernet Networking drivers.  QConvergeConsole command line interface (CLI) Management Tool.
PAGE 42
1–Product Overview Adapter Specifications Adapter Specifications The QLogic 8100 Series Adapters provide high-performance server connectivity to SAN and LAN networks. Table 1-5 lists the adapter physical and electrical specifications. NOTE: Some features may not be available for all 8100 Series Converged Network Adapters. Refer to the data sheet for the a list of adapter models and supported features. Table 1-5.
PAGE 43
1–Product Overview Adapter Specifications Table 1-5. Physical and Electrical Specification Specification BIOS Support Description QLogic adapters support the following boot images (boot from SAN and PXE boot):  PCI BIOS version 2.1 and 3.0  UEFI specification 1.10 and 2.x.  FCode for SPARC®-based systems Table 1-6.
PAGE 44
1–Product Overview Adapter Specifications Table 1-7.
PAGE 45
1–Product Overview Adapter Specifications Table 1-8. Ethernet Specifications (Continued) Specification Compliance Description  IEEE: 802.3ae (10Gb Ethernet)  802.1q (VLAN)  802.3ad (Link Aggregation)  802.1p (Priority Encoding)  802.3x (Flow Control)  IEEE 1149.1 (JTAG)  IPv4 Specification (RFC 791)  IPv6 Specification (RFC 2460)  TCP/UDP Specification (RFC 793/768)  ARP Specification (RFC 826) Enhanced Ethernet  Priority-based flow control (802.1Qbb rev.
PAGE 46
1–Product Overview Adapter Specifications Table 1-9. Management Specifications Specification QLogic Utilities Description  QConvergeConsole Web Management GUI, which is used to configure and manage QLogic Fibre Channel adapters, Intelligent Ethernet Adapters, and Converged Network Adapters within storage area networks (SANs).  QConvergeConsole CLI, which is used to configure and manage QLogic Fibre Channel adapters, Intelligent Ethernet Adapters, and Converged Network Adapters within SANs.
PAGE 47
2 Management Tools Overview QLogic provides the following tools with which to manage the QLogic 8100 Series Converged Network Adapter:  QConvergeConsole Web Management GUI  QConvergeConsole Management Agents (qlremote/netqlremote)  QConvergeConsole CLI  Offline Utilities QConvergeConsole Web Management GUI The QConvergeConsole management tool is a Web-based client/server application that allows for centralized management and configuration of QLogic adapters within the entire network (LAN and S
PAGE 48
2–Management Tools QConvergeConsole Management Agents (qlremote/netqlremote)  Configuration management – QConvergeConsole allows you to configure local and remote systems. With QConvergeConsole you can configure QLogic adapters and connected devices. It also lets you update adapter parameters, firmware, boot code, and drivers. NOTE: You can install the adapter driver before you install the adapter hardware.  Statistics – QConvergeConsole provides statistics for each host and adapter port.
PAGE 49
2–Management Tools QConvergeConsole CLI QConvergeConsole CLI The QConvergeConsole CLI is a unified CLI that manages Ethernet and Fibre Channel functions on QLogic adapters. The QConvergeConsole CLI non-interactive mode starts, performs the functions defined by the list of parameters provided, and then terminates. Use the noninteractive mode to run the QConvergeConsole CLI from a script file or when you want to perform a single operation. You can automate management and monitoring tasks using scripts.
PAGE 50
2–Management Tools Offline Utilities The offline utilities for UEFI servers are as follows:  EFICFG—This utility provides a UEFI shell into the server manufacturer’s boot-up menu interface, which configures advanced adapter features, including boot-from-SAN.  EFIUTIL—This utility installs the multi-boot image (including firmware) on the QLogic Converged Network Adapter. For more information about the offline utilities, refer to Section 9.
PAGE 51
3 Installation in a Windows Environment Overview This section describes how to install a QLogic Converged Network Adapter, including system requirements, hardware installation, driver installation, and software installation.
PAGE 52
3–Installation in a Windows Environment Downloading QLogic Drivers  The server motherboard must have a PCIe slot of at least x8 physical length. Both PCIe Gen 1 and Gen 2 slots are supported. QLogic 8100 Series Adapters operate on all eight lanes on a PCIe Gen 1 x8 slot, and automatically train down to use only four lanes on a PCIe Gen 2 x8 slot, thus saving energy by powering off the remaining four lanes of the PCIe Gen 2 x8 slot.
PAGE 53
3–Installation in a Windows Environment Downloading QLogic Drivers 4. In the selection list, click Converged Network Adapters in the first column. 5. In the selection list, click on the adapter model number in the second column. 6. In the third column, click the version of the Microsoft Windows operating system that is installed on the server. For example, in Figure 3-1, Windows Server 2008 R2 (64-bit) is selected for a QLE8152 adapter. Figure 3-1. Select an Adapter and a Windows Operating System 7.
PAGE 54
3–Installation in a Windows Environment Installing Hardware 8. Under Drivers, click the download link for the QLogic drivers. To enable all adapter capabilities, download both the FCoE (STOR Miniport) and NIC (NDIS Miniport) drivers (Figure 3-2). Figure 3-2. Download Drivers for Windows Servers 9. Read the QLogic license agreement, and then click Agree. 10. When prompted, click Save to save the driver file to your workstation.
PAGE 55
3–Installation in a Windows Environment Installing Hardware Install the Adapter To install the adapter: 1. Record the adapter model number, which can be found on the bar code label on the board. 2. Determine whether the server requires a full-height or a half-height adapter bracket. The QLogic 8100 Series Adapter ships with a full-height bracket installed and a spare half-height (low profile) bracket. To install the half-height bracket: a.
PAGE 56
3–Installation in a Windows Environment Installing Hardware  For QLE815x Series Adapters, see the list of approved copper cables at http://www.qlogic.com/Resources/Pages/Resources.aspx under Cable Support. 10. Connect the other end of the Ethernet cable to a supported switch. 11. Plug in the power cables and power up the server. Figure 3-3.
PAGE 57
3–Installation in a Windows Environment Installing Software 3.  If the QLogic BIOS banner does not appear, confirm that the adapter is seated properly. If necessary, install the adapter in another available PCIe x8 slot. If the BIOS banner still does not appear, verify that the adapter is compatible with the server. If the adapter is compatible with the server, contact your authorized maintenance provider for instructions on updating the motherboard BIOS.
PAGE 58
3–Installation in a Windows Environment Installing Software CAUTION! A reboot may be required to complete the installation of a QLogic driver. If a reboot is required, the driver installation process prompts for a reboot. NOTE: For Microsoft Windows 2003 operating systems, a Microsoft STOR miniport update is required before installing the FCoE driver. For boot-from-SAN, you must install the update immediately after installing the operating system.
PAGE 59
3–Installation in a Windows Environment Installing Software To obtain vendor ID and device ID information: 1. Right-click on the My Computer icon on the desktop or in the Start menu, and then select Manage. 2. Select Device Manager in the left pane. 3. In the right pane, under Other Devices, right click on any device and click Properties (Figure 3-5). Figure 3-5. Device Properties 4. FE0254601-00 A In the Device Properties window, click the Details tab.
PAGE 60
3–Installation in a Windows Environment Installing Software 5. In the Property drop-down list, select Device Instance Id (Windows Server 2003) or Hardware Ids (Windows 2008). Figure 3-6 shows sample vendor IDs and device IDs for QLogic 8100 NIC adapter (Windows 2003) and QLogic 8100 FCoE adapter (Windows 2008). QLogic 8100 NIC Windows 2003 QLogic 8100 FCoE Windows 2008 Figure 3-6. Sample QLogic Vendor IDs and Device IDs 6. Click Cancel to return to the Device Manager.
PAGE 61
3–Installation in a Windows Environment Installing Software 4. In the Computer Management window, select Device Manager in the left pane. 5. Scroll down the list of hardware types in the right pane. If you are installing the QLogic adapter drivers for the first time on this server, do the following; otherwise, go to Step 6: a. Click Other Devices to see a list of devices for which a driver is not installed on the server.
PAGE 62
3–Installation in a Windows Environment Installing Software Adapter under this section. Figure 3-9 shows typical entries for a dual-port QLogic 8100 Series Adapter. Figure 3-9. Typical QLogic 8100 Series Ethernet Adapter Port Entries b. To update the driver, right click Ethernet Controller, and then click Update Driver (Figure 3-10). Figure 3-10.
PAGE 63
3–Installation in a Windows Environment Installing Software 7. The Hardware Update Wizard starts. Select No, not this time, and then click Next (Figure 3-11). Figure 3-11. Starting the Hardware Update Wizard 8. Select Install from a list or specific location (Advanced), and then click Next. 9. Click Have Disk, and then navigate to the folder containing the extracted QLogic NIC driver that you downloaded in “Downloading QLogic Drivers” on page 3-2. 10. Select the setup information file (qlge.
PAGE 64
3–Installation in a Windows Environment Installing Software 12. Confirm that the QLogic 10Gb network adapter is shown in the list of network adapters (Figure 3-12), and then click Next. Figure 3-12. Confirming the Ethernet Adapter 13. The Microsoft Windows Hardware Update Wizard installs the NDIS driver for the QLogic adapter NIC function. 14. When the installation is complete, click Finish to close the Hardware Update Wizard.
PAGE 65
3–Installation in a Windows Environment Installing Software Adapter. For information about identifying QLogic devices in the Other Devices section, refer to “Identifying Unnamed Devices” on page 3-8. Figure 3-13. QLogic 8100 Series Adapter Device Entries b. To install the driver, right click Fibre Channel Controller, and then click Update Driver (Figure 3-14). Figure 3-14. Installing an FCoE Driver 6. If you are updating QLogic adapter drivers: a. Click SCSI and RAID Devices (for FCoE Drivers).
PAGE 66
3–Installation in a Windows Environment Installing Software b. To upgrade the driver, right click QLogic FCoE Adapter, and then click Update Driver (Figure 3-16). Figure 3-16. Updating an FCoE Driver 7. The Hardware Update Wizard starts. Select No, not this time, and then click Next. 8. Select Install from a list or specific location (Advanced), and then click Next. 9.
PAGE 67
3–Installation in a Windows Environment Installing Software 13. The Microsoft Windows Hardware Update Wizard proceeds to install the STOR Miniport driver for the QLogic adapter FCoE function. 14. When the installation is complete, click Finish to close the Hardware Update Wizard. Installing the NIC Driver for Windows Server 2008 This procedure describes how to install the NIC driver for one adapter port on a Windows Server 2008 using Device Manager.
PAGE 68
3–Installation in a Windows Environment Installing Software b. To install the driver, right click Ethernet Controller, and then click Update Driver Software (Figure 3-19). Figure 3-19. Installing an NIC Driver—Windows 2008 6. If you are updating QLogic adapter drivers: a. Click Network Adapters (for NIC drivers). Find each port of the QLogic adapter NIC function that is listed as QLogic10Gb PCI Ethernet Adapter under this section.
PAGE 69
3–Installation in a Windows Environment Installing Software 7. The Update Driver Software Wizard starts. Click Browse my computer for driver software (Figure 3-22). Figure 3-22. Starting the Update Driver Software Wizard 8. In the Update Driver Software–Ethernet Controller dialog box, click Browse, and then navigate to the folder containing the QLogic NIC driver that you downloaded earlier. Click Next. Figure 3-23. Select Driver Software 9.
PAGE 70
3–Installation in a Windows Environment Installing Software 10. When the installation is complete, the message Windows has successfully installed/updated your driver software appears. Click Close to exit. Installing the FCoE Driver for Windows Server 2008 This procedure describes how to install the FCoE driver for one adapter port on a Windows Server 2008 using Device Manager. For adapters with multiple ports, you must repeat this procedure for each port. To install the FCoE driver: 1.
PAGE 71
3–Installation in a Windows Environment Installing Software b. To install the driver, right click Fibre Channel Controller, and then click Update Driver Software... (Figure 3-25). Figure 3-25. Installing an FCoE Driver for Windows 2008 6. If you are updating QLogic adapter drivers: a. Click Storage controllers (for FCoE drivers). Find each port of the QLogic adapter FCoE function that is listed as QLogic FCoE Adapter under this section.
PAGE 72
3–Installation in a Windows Environment Installing Software 7. The Update Driver Software Wizard starts. Click Browse my computer for driver software (Figure 3-28). Figure 3-28. Starting the Update Driver Software Wizard 8. In the Update Driver Software–Ethernet Controller dialog box, click Browse, and then navigate to the folder containing the QLogic FCoE driver that you downloaded earlier (Figure 3-29). Click Next. Figure 3-29. Select Driver Software 9.
PAGE 73
3–Installation in a Windows Environment Installing Software 10. When the installation is complete, the message Windows has successfully installed/updated your driver software appears. Click Close to exit. 11. If a reboot is required to complete the driver installation or update, Windows will prompt you (Figure 3-30). If you are finished installing drivers for all ports, click Yes. Otherwise, click No and proceed with the installation. Figure 3-30.
PAGE 74
3–Installation in a Windows Environment Installing Software 6. In the third column, click the version of the Microsoft Windows operating system that is installed on the server. For example, in Figure 3-31, Windows Server 2008 R2 (64-bit) is selected for a QLE8152 adapter. Figure 3-31. Select an Adapter and a Windows Operating System 7. Click Go. 8. Under Drivers, click the download link for the Windows SuperInstaller (Figure 3-32).
PAGE 75
3–Installation in a Windows Environment Installing Software 10. Run the Windows SuperInstaller: a. Extract the setup.exe from the .ZIP file to a temporary location on your system drive. b. Use Windows Explorer to navigate to the temporary location. c. In Windows Explorer, double-click the following file: Setup.exe 11. Respond to prompts on the SuperInstaller screens to install the applications, agents, optional components, and drivers. 12.
PAGE 76
3–Installation in a Windows Environment Installing Software NOTE: Windows Server 2003 does not support the use of USB memory sticks or CD-ROMs; therefore, a 3.5-inch disk is required. Figure 3-34. Insert Driver Disk 6. Windows displays a list of drivers found on the disk (Figure 3-35). Select QLogic FCoE Adapter, and then press ENTER. Figure 3-35.
PAGE 77
3–Installation in a Windows Environment Installing Software 7. Windows presents a list of mass storage device drivers to load in addition to the standard drivers that have already been installed (Figure 3-36). If required, specify other devices, or press ENTER to continue with the installation. Figure 3-36. Install Additional Drivers 8. Continue with the standard Windows Server 2003 installation procedure.
PAGE 78
3–Installation in a Windows Environment Installing Software 3. When prompted to indicate the type of installation (Figure 3-37), click Custom (advanced). Figure 3-37. Windows Installation Type 4. When prompted to indicate where to install Windows (Figure 3-38), click Load Driver. Figure 3-38.
PAGE 79
3–Installation in a Windows Environment Installing Software 5. When prompted to select the driver to be installed (Figure 3-39), insert the QLogic driver disk (3.5-inch disk, USB memory stick, CD/DVD-ROM), click Browse, and then select the drive containing the QLogic driver disk. Figure 3-39. Insert the Driver Disk 6. Windows Setup presents a list of all drivers on the driver disk (Figure 3-40). Select QLogic FCoE Adapter from the list. Figure 3-40.
PAGE 80
3–Installation in a Windows Environment Removing the Driver 7. Windows loads the QLogic FCoE driver, and displays all LUNs that were presented to the QLogic adapter for a boot-from-SAN installation. If LUNs are found, Windows prompts you to select the disk/LUN on the SAN on which to install Windows Server 2008 (Figure 3-40). Figure 3-41. Select Disk/LUN on which to Install Windows 2008 8. Click Next to continue with the standard Windows Server 2008 installation procedure.
PAGE 81
3–Installation in a Windows Environment Verifying Driver Installation CAUTION! Do not attempt to manually remove any QLogic driver files from the operating system directories or remove any registry entries related to the QLogic drivers—this may disable the operating system. Verifying Driver Installation Verify every adapter installation to guarantee that the adapter drivers have been installed successfully and are operational. To verify the driver installation: 1.
PAGE 82
3–Installation in a Windows Environment Verifying Driver Installation c. In Device Manager, under Network Adapters (for NIC Drivers) and Storage Controllers (for FCoE Drivers), right click on a QLogic-labeled entry, and then click Properties (Figure 3-43). Figure 3-43. Network Adapters and Storage Controllers d. In the Properties dialog box, click the Driver tab and find the field Driver Version field. Figure 3-44 shows an example of a NIC adapter driver (version 1.0.1.
PAGE 83
3–Installation in a Windows Environment Firmware Upgrades Firmware Upgrades QLogic 8100 Series Converged Network Adapters ship with the latest firmware version. QLogic periodically releases new firmware versions, which can be downloaded from the QLogic Web site as part of a multi-boot image. Always use the latest firmware versions for enhanced performance and availability.
PAGE 84
3–Installation in a Windows Environment Firmware Upgrades 8. Under Boot Code, click the download link for the multi-boot image (Figure 3-46). The multi-boot image contains firmware, BIOS and UEFI drivers, and the FlasUTIL and EFIUTIL utilities. Make a note of the FCoE firmware version included in the multi-boot image. Figure 3-46. Download the Multi-boot Image 9. Read the license agreement, and then click Agree. 10.
PAGE 85
3–Installation in a Windows Environment Firmware Upgrades 1. In the QConvergeConsole web management GUI, in the left pane, expand the host to view the connected adapters. 2. Select the port QLogic 8100 Series Adapter for which to determine the installed firmware version. The HBA Info tabbed page identifies the firmware version (Figure 3-47). Figure 3-47.
PAGE 86
3–Installation in a Windows Environment Firmware Upgrades 3. Expand the physical Port 1, select the FCoE port, and then select the VPD tab (Figure 3-48) in the right pane. The Flash Image Version appears at the bottom of the Port Vital Product Data (VPD) list. Figure 3-48. Displaying the Multi-boot Image Version Upgrading the Firmware/Boot Code Using QConvergeConsole GUI or QConvergeConsole CLI Firmware is updated for the adapter and not for individual ports.
PAGE 87
3–Installation in a Windows Environment Firmware Upgrades 3. Under Flash, click Update Entire Image (Figure 3-52). Figure 3-49. QConvergeConsole—Update Entire Image 4. Click the Choose File button. The Open dialog box appears. 5. Navigate to and click on the file from which to update, then click Open. Make sure you select the correct file. NOTE: The Flash file must end with a .bin extension. Note that Flash files are unique to each adapter model. 6.
PAGE 88
3–Installation in a Windows Environment Installing Management Tools Updating Firmware Using QLogic BIOS and UEFI Utilities You can update firmware without a first installing an operating system on the server. Such firmware upgrades are considered offline upgrades. To update firmware on BIOS-based servers: 1. Boot the server into DOS using either a DOS bootable 3.5-inch disk or a USB memory stick containing the extracted multi-boot image. 2. Run the script update.bat. 3.
PAGE 89
3–Installation in a Windows Environment Installing Management Tools  Offline utilities provide adapter maintenance functions for special circumstances. Section 9 describes the offline utilities and their functions. The Windows operating system tool is the Windows Device Manager/Server Manager. Device Manager enables and disables the adapter port, updates adapter drivers, and provides access to version information of the currently installed drivers.
PAGE 90
3–Installation in a Windows Environment Installing Management Tools Installing and Launching the QConvergeConsole The QConvergeConsole Installer for Windows is a self-extracting utility that installs the QConvergeConsole and related files. After you install the application on the server, you can start using the QConvergeConsole by opening its main page in your browser window, either locally on the server where the QConvergeConsole is installed or remotely from another computer.
PAGE 91
3–Installation in a Windows Environment Installing Management Tools 2. Click Next. If the Apache Tomcat server is not installed, a message prompts whether you want to install Tomcat on your system (Figure 3-52). Figure 3-52. Install the QConvergeConsole: Install Tomcat on Your System 3. Click Yes. The Pre-Installation Summary dialog box (Figure 3-53) opens. Figure 3-53. Install the QConvergeConsole: Pre-Installation Summary 4. FE0254601-00 A Read the information, and then click Install.
PAGE 92
3–Installation in a Windows Environment Installing Management Tools During the installation, the installer notifies you of the installation status (Figure 3-54). Figure 3-54. Install the QConvergeConsole: Installation Status A message prompts you to confirm that you want to enable the Secure Socket Layer (SSL) feature, which allows you to run QConvergeConsole in a secured environment (Figure 3-55). Figure 3-55. Install the QConvergeConsole: Enable SSL Feature 5.
PAGE 93
3–Installation in a Windows Environment Installing Management Tools The Install Complete dialog box (Figure 3-56) opens. Figure 3-56. Install the QConvergeConsole: Install Complete Notification 6. Click Done to exit the installer. You have installed the QConvergeConsole on your server. 7. Install the management agents (NIC and FCoE) to remotely manage the server in which your adapter is physically installed.
PAGE 94
3–Installation in a Windows Environment Installing Management Tools Figure 3-57. QConvergeConsole Main Window on the Server Where QConvergeConsole Resides To open QConvergeConsole from a remote computer: Enter the IP address of the QConvergeConsole server, followed by the access port and application name in the browser's address bar using the following format: http://xxx.xxx.xxx.xxx:8080/QConvergeConsole/ In the following example, the Web address of the QConvergeConsole server displays (Figure 3-58).
PAGE 95
3–Installation in a Windows Environment Installing Management Tools Figure 3-58. Entering QConvergeConsole Web Address (Example) The initial main menu of the QConvergeConsole opens, as shown in Figure 3-59. Figure 3-59.
PAGE 96
3–Installation in a Windows Environment Installing Management Tools Installing and Launching the QConvergeConsole CLI You can install the QConvergeConsole CLI from the command prompt using the Microsoft® Windows Installer (MSI). Use one of the following methods:  Standard Windows Interactive (CLI) Installation  Quiet or Unattended Windows Installation  Passive Windows Installation  Overwrite Previous Windows Installations NOTE: You can also configure the installation using MSI commands.
PAGE 97
3–Installation in a Windows Environment Installing Management Tools Overwrite Previous Windows Installations Type the following for an installation that overwrites any previous installations without asking for confirmation. Type: QCCCLI.msi /i forceinstall=true Starting the QConvergeConsole CLI You can start the QLogic 8100 Series Converged Network Adapter in Windows in the following ways:  Double click the QCCCLI icon on the desktop.
PAGE 98
3–Installation in a Windows Environment Installing Management Tools 3-48 FE0254601-00 A
PAGE 99
4 Installation in a Linux Environment Overview This section describes how to install a QLogic 8100 Series Adapter in a Linux server, including system requirements, hardware installation, driver installation, and software installation. System Requirements Operating System Requirements The QLogic 8100 Series Adapter supports the following Linux operating systems:  Red Hat® Enterprise Linux  SUSE® Linux Enterprise Server NOTE: The QLogic 8100 Series Adapter supports both SLES and RHEL distributions.
PAGE 100
4–Installation in a Linux Environment Installing Hardware  The server motherboard must have a PCIe slot of at least x8 physical length. Both PCIe Gen 1 and Gen 2 slots are supported. QLogic adapters operate on all eight lanes on a PCIe Gen 1 x8 slot, and automatically train down to use only four lanes on a PCIe Gen 2 x8 slot, thus saving energy by powering off the remaining four lanes of the PCIe Gen 2 x8 slot.  A supported Linux operating system must be installed on the server.
PAGE 101
4–Installation in a Linux Environment Installing Hardware Install the Adapter To install the adapter: 1. Record the adapter model number, which can be found on the bar code label on the board. 2. Determine whether the server requires a full-height or a half-height adapter bracket. The QLogic 8100 Series Adapter ships with a full-height bracket installed and a spare half-height (low profile) bracket. To install the half-height bracket: a.
PAGE 102
4–Installation in a Linux Environment Installing Hardware 11. Connect the other end of the Ethernet cable to a supported switch. 12. Plug in the power cables and power up the server. Figure 4-1.
PAGE 103
4–Installation in a Linux Environment Installing Hardware Verify the Adapter Installation To verify that the adapter is properly installed and that it can be recognized as a PCIe device by the server: 1. While the host server is booting, verify that the adapter BIOS banner appears without errors. Some servers may require that you press the ESC key at the motherboard BIOS banner screen to enable the display of diagnostic messages. 2.
PAGE 104
4–Installation in a Linux Environment Installing Software Installing Software The FCoE driver (STOR Miniport) and NIC driver (NDIS Miniport) provide the adapter’s Fibre Channel and Ethernet capabilities, respectively. The adapter driver installation process depends on the Linux operating system version that is installed on the server and whether the operating system image resides on the server hard drive or on the SAN.
PAGE 105
4–Installation in a Linux Environment Installing Software 6. In the third column, click the version of the Linux operating system that is installed on the server, and then click Go. For example, in Figure 4-3, Linux Red Hat (64-bit) is selected for a QLE8152 adapter. Figure 4-3. Select an Adapter and a Linux Operating System 7. Under Drivers, click the download link FC-FCoE Adapter Driver for RHEL 5.x (Figure 4-4). Figure 4-4. Download the FCoE Adapter Driver 8.
PAGE 106
4–Installation in a Linux Environment Installing Software 10. Insert the RHEL 5 installation DVD into the optical drive on the server, or into another drive that contains the following packet files for the RHEL 5 version and architecture installed on the server:  kernel-headers-2.6.18-164.el5.x86_64.rpm  kernel-devel-2.6.18-164.el5.x86_64.rpm  glibc-headers-2.5-42.x86_64.rpm  glibc-devel-2.5-42.x86_64.rpm  libgomp-4.4.0-6.el5.x86_64.rpm  gcc-4.1.2-46.el5.x86_64.
PAGE 107
4–Installation in a Linux Environment Installing Software 14. In the directory that contains the driver source file, qla2xxx-src-x.xx.xx.xx.xx.xx-k.tar.gz, type the following commands to expand the compressed file: # tar -xzvf qla2xxx-src-x.xx.xx.xx.xx.xx-k.tar.gz # cd qla2xxx-src-x.xx.xx.xx.xx.xx-k 15. Execute the build.sh script to compile the driver modules from the source code. # ./extras/build.sh install The build.sh script does the following:  Builds the QLogic FCoE driver .ko files.
PAGE 108
4–Installation in a Linux Environment Installing Software a. Change to the directory that contains the RAMDISK images. # cd /boot b. Create a backup copy of the RAMDISK (initrd) image. # cp initrd-[kernel version].img initrd-[kernel version].img.bak c. Generate a new RAMDISK image containing the updated QLogic FCoE driver. # mkinitrd -f initrd-[kernel version].img `uname -r` Depending on the server hardware, the RAMDISK file name may be slightly different.
PAGE 109
4–Installation in a Linux Environment Installing Software Installing the FCoE Driver for RHEL 5.3 Boot-from-SAN The RHEL 5.3 operating system does not include the QLogic 8100 Series Adapter drivers. Therefore, to boot from SAN, you must load the adapter drivers during the operating system installation. QLogic provides a driver disk kit (DD-Kit) for RHEL 5.3 that contains the driver binaries for RHEL 5.3. To download, create, and install a DD-Kit for RHEL 5.3 on the SAN: 1.
PAGE 110
4–Installation in a Linux Environment Installing Software 7. Under Drivers, click the download link for FC-FCoE DD-Kit (Figure 4-8). Figure 4-8. Download the FC-FCoE DD-Kit 8. Read the QLogic license agreement, and then click Agree. 9. When prompted, click Save to save the driver file to the hard drive. The compressed file contains the source for the QLogic FC-FCoE driver. The file name has the following format: qla2xxx-src-x.xx.xx.xx.xx.xx-k.tar.gz 10.
PAGE 111
4–Installation in a Linux Environment Installing Software 14. Configure the server to boot from the optical drive, and power up the server. The system boots from the CD and stops at the boot: prompt (Figure 4-9). Figure 4-9. RHEL 5.3 Boot Screen 15. At the boot: prompt, press the F2. 16. In the Installer Boot Options screen, type linux dd at the boot prompt (Figure 4-10). Figure 4-10. RHEL 5.
PAGE 112
4–Installation in a Linux Environment Installing Software 17. The Driver Disk message box prompts you for a driver disk: click YES, and then press ENTER. 18. From the Driver Disk Source window, select the driver source:  If the driver disk is a 3.5-inch floppy disk, select fd0, and then press ENTER.  If the driver disk is a CD-ROM, select hdx (where x is the drive letter), and then press ENTER. 19.
PAGE 113
4–Installation in a Linux Environment Installing Software 6. In the third column, select the version of the Linux Operating System that is installed on the server, and then click Go (Figure 4-11). For example, in Figure 4-11, Linux Red Hat (64-bit) is selected for a QLE8152 adapter. Figure 4-11. Select an Adapter and a Linux Operating System 7. Under Drivers, click the download link Converged Network Adapter Networking Driver (Figure 4-12). Figure 4-12. Download the Networking Driver 8.
PAGE 114
4–Installation in a Linux Environment Installing Software 10. Insert the RHEL 5 installation DVD into the optical drive on the server, or into another drive that contains the following packet files for the RHEL 5 version and architecture installed on the server.  kernel-headers-2.6.18-164.el5.x86_64.rpm  kernel-devel-2.6.18-164.el5.x86_64.rpm  glibc-headers-2.5-42.x86_64.rpm  glibc-devel-2.5-42.x86_64.rpm  libgomp-4.4.0-6.el5.x86_64.rpm  gcc-4.1.2-46.el5.x86_64.
PAGE 115
4–Installation in a Linux Environment Installing Software 15. In the directory that contains the source driver file, qlge_x.x.x.xx-ddmmyy_xx_x.x.xx.tgz, type the following commands to expand the compressed file: # tar -xzvf qlge_x.x.x.xx-ddmmyy_xx_x.x.xx.tgz # cd qlge 16. Build and install the driver modules from the source code. # make install The GNU executes the makefile included in the qlge/ directory and then does the following:  Builds the QLogic networking driver .ko files  Copies the .
PAGE 116
4–Installation in a Linux Environment Installing Software c. Create a new RAMDISK image containing the updated QLogic networking driver. # mkinitrd -f initrd-[kernel version].img `uname -r` Depending on the server hardware, the RAMDISK file name may be slightly different. The command is successful if there is no output. d.
PAGE 117
4–Installation in a Linux Environment Verifying the Driver Installation Verifying the Driver Installation Verify every adapter to guarantee that the FCoE and networking adapter drivers have been installed successfully and operational. To verify the driver installation: 1. Use the lsmod command to list the loaded kernel modules, and then locate the QLogic FcoE (qla2xxx) and networking (qlgc) driver entries.  The following example lists kernel modules for the QLogic FCoE driver.
PAGE 118
4–Installation in a Linux Environment Removing Drivers  The following example displays the FCoE driver information: # modinfo -F version qla2xxx 8.03.01.06.05.06-k  The following example displays the networking driver information: # modinfo –F version qlgc 1.00.00.23 3. Observe the adapter Link/Enet Traffic LED and Storage Traffic LED for indications that the adapter is operating correctly. For specific LED indications, refer to Appendix A.
PAGE 119
4–Installation in a Linux Environment Firmware Upgrades Firmware Upgrades QLogic 8100 Series Converged Network adapters ship with the latest available firmware version. QLogic periodically releases new firmware versions, which can be downloaded from the QLogic Web site as part of a multi-boot image. Always use the latest firmware versions for enhanced performance and availability.
PAGE 120
4–Installation in a Linux Environment Firmware Upgrades 7. Under Boot Code, click the download link for the multi-boot image (Figure 4-15). The multi-boot image contains firmware, BIOS and UEFI drivers, and the FlasUTIL and EFIUTIL utilities. Make note of the FCoE firmware version included in the multi-boot image. Figure 4-15. Download the Multi-boot Image 8. Read the license agreement, and then click Agree. 9.
PAGE 121
4–Installation in a Linux Environment Firmware Upgrades NOTE: Ignore the driver firmware version listed under Information; it is not related to the installed adapter firmware version. QLogic 8100 Series Adapter drivers are not bundled with the firmware, and use the firmware that is resident on the adapter hardware. Figure 4-16. Displaying the Adapter Firmware Version 3. FE0254601-00 A Expand the Port node and select the FCoE port.
PAGE 122
4–Installation in a Linux Environment Firmware Upgrades 4. In the right pane, click the FCoE tab (Figure 4-17). The MPI firmware version is listed under the Information section. Figure 4-17. Displaying the Adapter MPI Firmware Version Displaying the Firmware Version Using sysfs The sysfs interface is available to advanced users to display the adapter firmware version.
PAGE 123
4–Installation in a Linux Environment Firmware Upgrades 3. Under Flash, click Update Entire Image (Figure 4-18). Figure 4-18. QConvergeConsole—Update Entire Image 4. In the Open pop-up window, browse to the temporary folder that contains the extracted multi-boot image, and then select the Flash file (.BIN). 5. Click Open. The QConvergeConsole reads the multi-boot image to determine the version information of the image file.
PAGE 124
4–Installation in a Linux Environment Management Tool Installation Using QLogic BIOS and UEFI Utilities You can update firmware without a first installing an operating system on the server. Such firmware upgrades are considered offline upgrades. To update firmware on BIOS servers: 1. Boot the server into DOS using either a DOS-bootable 3.5-inch disk or a USB memory stick containing the extracted multi-boot image. 2. Run the script update.bat. 3.
PAGE 125
4–Installation in a Linux Environment Management Tool Installation  Linux Network Interface Configuration Tools—A set of tools, including ifconfig and neat, that configure parameters such as IP address and network interface status. For more information about these tools, refer to the tool manual pages. Obtaining the QLogic Adapter Management Tools To download the QLogic management tools and documentation: 1. Go to the QLogic Web site: http://driverdownloads.qlogic.com. 2. Click QLogic Products. 3.
PAGE 126
4–Installation in a Linux Environment Management Tool Installation Installing and Launching QConvergeConsole To install and launch the QConvergeConsole: QConvergeConsole can be installed on a Linux host by running a Virtual Network Computing (VNC®) program on a Windows host to remotely control the installation. VNC Viewer is a VNC program that can remotely control QConvergeConsole installation on a Linux host. To install the QConvergeConsole in a Linux environment: 1.
PAGE 127
4–Installation in a Linux Environment Management Tool Installation 4. Click Run in Terminal. The installer extracts the files and installs QConvergeConsole in the directory /opt/QConvergeConsole_Installer (Figure 4-23). Figure 4-23. Install the QConvergeConsole: Installer Extracts FIles The InstallAnywhere window prepares to install the QConvergeConsole and opens the installation Introduction dialog box (Figure 4-24). Figure 4-24. Install the QConvergeConsole: Introduction 5.
PAGE 128
4–Installation in a Linux Environment Management Tool Installation The Pre-Installation Summary dialog box (Figure 4-25) opens. Figure 4-25. Install the QConvergeConsole: Pre-Installation Summary 6. 4-30 Read the information, and then click Install.
PAGE 129
4–Installation in a Linux Environment Management Tool Installation During the installation, the installer notifies you of the installation status (Figure 4-26). Figure 4-26.
PAGE 130
4–Installation in a Linux Environment Management Tool Installation The Install Complete dialog box (Figure 4-27) opens. Figure 4-27. Install the QConvergeConsole: Install Complete Notification 7. Click Done to exit the installer. You have installed the QConvergeConsole on your server. 8. Install the management agents (NIC andFCoE) to remotely manage the server in which your adapter is physically installed.
PAGE 131
4–Installation in a Linux Environment Management Tool Installation Figure 4-28. QConvergeConsole Main Window on the Server Where QConvergeConsole Resides To open QConvergeConsole from a remote computer: Enter the IP address of the QConvergeConsole server, followed by the access port and application name in the browser's address bar using the following format: http://xxx.xxx.xxx.xxx:8080/QConvergeConsole/ In the following example, the Web address of the QConvergeConsole server displays (Figure 4-29).
PAGE 132
4–Installation in a Linux Environment Management Tool Installation Figure 4-29. Entering QConvergeConsole Web Address (Example) The initial main menu of the QConvergeConsole opens, as shown in Figure 4-30. Figure 4-30.
PAGE 133
4–Installation in a Linux Environment Management Tool Installation Installing and Launching the QLogic Linux Tools The QLogic Linux utilities manage the adapter FCoE function. The QLogic Linux tools package (Linux-Tools-yyyymmdd-x.tgz) is a compressed file that contains the utility packages described in Table 4-1. Table 4-1. QLogic Linux Utilities Utility File Description ql-dynamic-tgt-lun-disc-x.xx.tgz Scans for newly added LUNs ql-hba-collect-x.x.
PAGE 134
4–Installation in a Linux Environment Management Tool Installation Table 4-2. QLogic Linux Utility Directories and Commands Directory Command ql-hba-snapshot-x.xx/ ./ql-hba-snapshot.sh ql-lun-state-online-x.x/ ./ql-lun-state-online.sh –i ql-set-cmd-timeout-x.x/ ./ql-set-cmd-timeout.sh -i For information about using the Linux utilities, refer to “Using the QLogic Linux Utilities” on page 8-41.
PAGE 135
5 Installation in a VMware Environment Overview This section describes how to install a QLogic 8100 Series Adapter in VMware® ESX/ESXi environments including, hardware installation, driver installation, and software installation. Installing Hardware CAUTION!  To minimize the risk of ESD damage, use a workstation anti-static mat and an ESD wrist strap.  Leave the adapter in its anti-static bag until you are ready to install it in the server.
PAGE 136
5–Installation in a VMware Environment Installing Hardware 5-2 c. Carefully remove the full-height bracket by pulling it away from the card. d. Fit the half-height bracket while aligning the slots for the SFP+ transceivers and LEDs. e. Fasten the half-height bracket using the screws provided. f. Reinstall the SFP+ transceivers by pressing them in until the transceivers clicks. 3. Power off the computer and all attached devices such as monitors, printers, and external components. 4.
PAGE 137
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers Figure 5-1. Adapter Hardware 12. Verify the LEDs on the adapter to ensure proper operation. For information about LED indications, refer to Appendix A. Installing the FCoE and Networking Drivers The QLogic 8100 Series Adapter driver is not included with the VMware ESX™/ESXi4.0 operating system. Therefore, you must download the drivers for VMware ESX/ESXi 4.0 from the QLogic Web site at http://driverdownloads.qlogic.com/.
PAGE 138
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers 5. Select VMware ESX/ESXi in the third column of the selection list, and then click Go (Figure 5-2). Figure 5-2. Select Adapter Software for VMware by Operating System 6. 7. In the Drivers table, click the links that correspond to the following descriptions to download the drivers:  Networking driver for VMware ESX/ESXi 4.0.x and 4.1  FC-FCoE driver for VMware ESX/ESXi 4.0.x, 4.
PAGE 139
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers 8. On the ESX host server, in maintenance mode, select the Summary tab (Figure 5-4). Figure 5-4. Selecting the Summary Tab 9. Right-click the storage icon, and then select Browse Datastore (Figure 5-5). Figure 5-5.
PAGE 140
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers 10. In the Datastore Browser, create a temporary folder in which to store the driver ISO files (Figure 5-6). Figure 5-6. Creating a Temporary Folder in Which to Store the Driver ISO Files 11. Click the Upload icon to upload the driver ISO files into the temporary folder (Figure 5-7). Figure 5-7. Opening the Temporary Driver Folder 12.
PAGE 141
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers 13. Change to the directory that contains the driver ISO files by issuing the following command: # cd /vmfs/volumes/Storage1//temp 14. Mount the first ISO file under the ESX host server by issuing the following command: # mount -o loop –t iso9660 .iso /mnt/cdrom 15.
PAGE 142
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers 24. Unmount the first ISO file from the ESX host server by issuing the following command: # umount /mnt/cdrom 25. Reboot the ESX host server to complete the driver installation and exit maintenance mode. Verifying Driver Installation To verify that the Converged Network Adapter drivers are installed on the VMware ESX/ESXi 4.
PAGE 143
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers The example in Figure 5-10 shows the details for FCoE adapter 3, including the current state, the firmware version, the driver version, and the boot code version. Figure 5-10. Displaying FCoE Adapter Driver Details 5. List details for the QLogic adapter networking driver by issuing the following command: ifconfig -a The example in Figure 5-11 shows all vmnic and vswif interfaces available on the host.
PAGE 144
5–Installation in a VMware Environment Installing the FCoE and Networking Drivers Figure 5-11.
PAGE 145
5–Installation in a VMware Environment Identifying QLogic Adapters Using vSphere Client 6. Display adapter networking driver and firmware versions for QLogic vmnic interfaces by issuing the following command: # ethtool –i vmnic[N] In this command, [N] is the adapter number that corresponds to a QLogic interface from the ifconfig –a display (Figure 5-11). A QLogic interface MAC address begins with 00:0C:DD. The example in Figure 5-12 shows networking driver version and firmware version for adapter 3.
PAGE 146
5–Installation in a VMware Environment Configuring NIC Using the vSphere Client Figure 5-13. Displaying Storage Adapters Using the vSphere Client 4. In the Hardware pane, select Network Adapters to display all network adapters, as shown in Figure 5-14. Figure 5-14. Displaying Network Adapters Using the vSphere Client Configuring NIC Using the vSphere Client To configure the NIC using the vSphere client: 5-12 1.
PAGE 147
5–Installation in a VMware Environment Configuring NIC Using the vSphere Client 3. Open the vSphere client, and then click the Configuration tab. 4. In the Hardware pane, select Networking, as shown in Figure 5-15. Figure 5-15. Configuring Networking Adapters 5. Select Add Networking . . in the upper right portion of the window. 6. In the Add Network Wizard, click Virtual Machine, and then click Next (Figure 5-16). Figure 5-16.
PAGE 148
5–Installation in a VMware Environment Configuring NIC Using the vSphere Client 7. Click the vmnic associated with the QLogic adapter to be connected to the new virtual switch, and then click Next. Figure 5-17. Selecting the Virtual Switch 8. 5-14 Modify the network label and VLAN ID if needed, and then click Next (Figure 5-18).
PAGE 149
5–Installation in a VMware Environment Configuring the Driver Parameters Figure 5-18. Modifying the Network Label and the VLAN ID 9. Click Finish to complete the addition of the networking interface. Configuring the Driver Parameters Use the esxcfg-module command to configure the QLogic Fibre Channel and Converged Network Adapter driver parameters. Configuration changes made using the esxcfg-module -s command are preserved across system reboots. To configure driver parameters: 1.
PAGE 150
5–Installation in a VMware Environment Configuring the Driver Parameters 4. Reboot the server to place the parameter changes into effect. # reboot Table 5-1 describes the configurable QLogic driver parameters. Table 5-1. esxcfg-module Configurable Driver Parameters Driver Parameter 5-16 Description ql2xallocfwdump Enables (1) or disables (0) allocation of memory for a firmware dump during adapter initialization. Memory allocation requirements vary by ISP type. The default is 0.
PAGE 151
5–Installation in a VMware Environment Configuring the Driver Parameters Table 5-1. esxcfg-module Configurable Driver Parameters (Continued) Driver Parameter FE0254601-00 A Description ql2xplogiabsentdevice Enables (1) or disables (0) PLOGI (port login) to devices that are not present after a fabric scan. Enabling this parameter is required to work around some Fibre Channel switch defects. The default is 0.
PAGE 152
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine Configuring a Hard Drive in a Virtual Machine To configure a hard drive in a virtual machine: 1. Open vSphere and exit maintenance mode on the vSphere client (Figure 5-19). Figure 5-19. Exiting Maintenance Mode 2. Power off the virtual machine that you are configuring. 3. Select the virtual machine in the left pane (Figure 5-20). Figure 5-20. Selecting the Virtual Machine 5-18 4. Click the Getting Started tab. 5.
PAGE 153
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine 6. Click Add in the Virtual Machine Properties window to add a device to the virtual machine (Figure 5-21). Figure 5-21.
PAGE 154
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine 7. Select a device. In this example, select Hard Drive to add a storage device to the virtual machine, and then click Next (Figure 5-22). Figure 5-22. Add Hardware—Device Type 8. Select the type of disk. Click Raw Device Mappings, and then click Next. (Figure 5-23). For an explanation of the virtual disk options, refer to your VMware documentation. Figure 5-23.
PAGE 155
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine 9. Select a target LUN. In this example, accept the selected LUN, and then click Next (Figure 5-24). Figure 5-24. Add Hardware—Select Target LUN 10. Select a datastore. In this example, accept the default, Store with Virtual Machine, and then click Next (Figure 5-25). Figure 5-25.
PAGE 156
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine 11. Select a compatibility mode. In this example, accept the default, Physical, and then click Next (Figure 5-26). Figure 5-26. Add Hardware—Compatibility Mode 12. Select advanced options. In this example, accept the default, and then click Next (Figure 5-27). Figure 5-27.
PAGE 157
5–Installation in a VMware Environment Configuring a Hard Drive in a Virtual Machine 13. Review the disk settings, and then click Finish to complete the configuration (Figure 5-28). Figure 5-28. Add Hardware—Ready to Complete 14. Observe the New Hard Disk (adding) entry in the Virtual Machine Properties window, and then click OK (Figure 5-29). Figure 5-29.
PAGE 158
5–Installation in a VMware Environment Configuring a Network Adapter in a Virtual Machine Configuring a Network Adapter in a Virtual Machine To configure a network adapter in a virtual machine: 1. Open vSphere and exit maintenance mode on the vSphere client (Figure 5-30). Figure 5-30. Exiting Maintenance Mode 2. Power off the virtual machine that you are configuring. 3. Select the virtual machine in the left pane (Figure 5-31). Figure 5-31. Selecting the Virtual Machine 5-24 4.
PAGE 159
5–Installation in a VMware Environment Configuring a Network Adapter in a Virtual Machine 6. Click Add in the Virtual Machine Properties window to add a device to the virtual machine (Figure 5-21). Figure 5-32.
PAGE 160
5–Installation in a VMware Environment Configuring a Network Adapter in a Virtual Machine 7. Select the Ethernet adapter device, and then click Next (Figure 5-33). Figure 5-33. Add Hardware—Select Adapter 8. Select the adapter type and network connection. For information about these options, refer to the VMware documentation. In this example, accept the default setting for adapter type, select Network Label, Virtual Machine Network, and then click Next (Figure 5-34). Figure 5-34.
PAGE 161
5–Installation in a VMware Environment Configuring a Network Adapter in a Virtual Machine 9. Review the adapter settings, and then click Finish to complete the adapter configuration (Figure 5-35). Figure 5-35. Add Hardware—Ready to Complete 10. Observe the New NIC (adding) entry in the Virtual Machine Properties window, and then click OK (Figure 5-36). Figure 5-36.
PAGE 162
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 Deploying NPIV for VMware ESX/ESXi 4.0 QLogic Fibre Channel and Converged Network Adapters support N_Port ID virtualization (NPIV) for Fibre Channel and FCoE SANs. NPIV enables each virtual machine to have its own Fibre Channel-FCoE WWPN by creating multiple virtual adapters on a single physical adapter. VMware ESX/ESXi 4.
PAGE 163
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 Assigning WWNs to Virtual Machines You can assign a WWN to a new virtual machine with an RDM disk when you create the virtual machine, or to an existing virtual machine that has been powered off. To create an NPIV-ready virtual machine: 1. Open the vSphere client, and then click Inventory in the navigation bar. Expand the inventory as needed. 2.
PAGE 164
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 5. Proceed through the configuration procedure (Name and Location, Datastore, Virtual Machine Version, Guest Operating System, CPUs, Memory, Network, SCSI Controller) as you would for any non-NPIV virtual machine. 6. Select a disk. In this example, click Raw Device Mappings, and then click Next (Figure 5-39). Figure 5-39.
PAGE 165
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 7. Select the LUN to attach to the VM, and then click Next (Figure 5-40). Figure 5-40. Create New Virtual Machine—Select Target LUN 8. Select the datastore on which to store the LUN mapping. In this example, click Store with Virtual Machine, and click Next (Figure 5-41). Figure 5-41.
PAGE 166
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 9. Select the compatibility mode. In this example, click Virtual, and then click Next (Figure 5-42). Figure 5-42. Create New Virtual Machine—Compatibility Mode 10. Select advanced options. In this example, accept the default, and then click Next. 11. Complete the creation process by clicking Edit the virtual machine settings, and then click Continue (Figure 5-43). Figure 5-43.
PAGE 167
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 12. Select the Options tab in the Virtual Machine Properties window. 13. Select Fibre Channel NPIV in the left pane, click Generate new WWNs, and then click Finish (Figure 5-44). Figure 5-44. Virtual Machine Properties—Generate New WWNs 14. FE0254601-00 A To confirm that the WWNs were generated for the port: a. Select the Getting Started tab, and then click Edit virtual machine settings. b.
PAGE 168
5–Installation in a VMware Environment Deploying NPIV for VMware ESX/ESXi 4.0 c. Confirm the node WWN and port WWN in the WWN Assignment field of the Virtual Machines Properties window (Figure 5-45). Figure 5-45. Confirm Node and Port WWNs NOTE:  Do NOT power on the virtual machine prior to configuring zoning and LUN masking.  For information on zoning configuration, refer to the FCoE switch documentation.  For information on LUN masking, refer to the storage array documentation.
PAGE 169
6 Configuring NIC Functionality in the Converged Network Adapter Overview QLogic 8100 series Converged Network Adapter provides both NIC and FCoE server connectivity to hosts. This section describes the NIC parameters, management tools and configuration options for the QLogic 8100 Series Adapter for a Windows environment and a Linux environment.
PAGE 170
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment To access the Device Manager: 1. Click Start, right-click My Computer, and then click Device Manager to display a list of devices, as shown in Figure 6-1. Figure 6-1. Accessing Device Manager 2. 6-2 Under Network Adapters, right-click the QLogic 10Gb PCI Ethernet Adapter, and then select Properties to display the Properties dialog box (Figure 6-2).
PAGE 171
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Figure 6-2. Adapters Properties Dialog Box Managing the NIC Function with the QConvergeConsole CLI The QConvergeConsole CLI configures the teaming and VLANs for the NIC function driver. The CLI also performs diagnostics, provides link status, and configures offload driver parameters. To access the QLogic QConvergeConsole CLI: 1.
PAGE 172
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Figure 6-3. Main Interactive Menu NIC Driver Parameters (Windows) Table 6-1 lists the QLogic 8100 Series Adapter NIC function driver parameters for Windows, their default values, and allowed values.
PAGE 173
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Table 6-1. NIC Driver Parameters for Windows Parameter Name Function Default Value Range Method to Configure CheckSumOffloadSupport Bucket to enable, disable all IP, TCP, UDP checksum offload driver capabilities Enable Disable Enable Windows Property Pages for QLogic adapter, navigate to Advanced tab or QConvergeConsole CLI FlowControl Enable or disable Flow Control.
PAGE 174
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Table 6-1. NIC Driver Parameters for Windows (Continued) Parameter Name Function Default Value Jumbo Packet Enables Jumbo Packet 1514 capability for TCP/IP packets. When large packets make up the majority of traffic, and additional latency can be tolerated, jumbo packets can reduce CPU use and improve wire efficiency.
PAGE 175
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Table 6-1. NIC Driver Parameters for Windows (Continued) Parameter Name PriorityVLANTag Function Enables the sending and receiving of IEEE 802.3ac tagged frames, which include: Default Value Range Method to Configure Enable Disable Enable Windows Property Pages for QLogic adapter, navigate to Advanced tab  802.1p QoS (Quality of Service) tags for priority-tagged packets  802.
PAGE 176
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Table 6-1. NIC Driver Parameters for Windows (Continued) Parameter Name Function Default Value Range Method to Configure TCPChecksumO ffloadIPv6 Computes (Tx) or verifies (Rx) the TCP checksum of packets in IPv6. This feature can improve performance and reduce CPU use. With Offloading enabled, the adapter computes or verifies the checksum for the operating system. Windows Server 2008 only.
PAGE 177
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Table 6-1. NIC Driver Parameters for Windows (Continued) Parameter Name Default Value Function Range Method to Configure UDPChecksumO ffloadIPv4 Computes (Tx) or verifies (Rx) the UDP checksum of packets for IPv4. This parameter can improve performance and reduce CPU use. With Offloading enabled, the adapter computes or verifies the checksum for the operating system.
PAGE 178
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment about the CheckSumOffload parameter, refer to Table 6-1 Do not turn off checksum offload unless you are debugging a checksum computation problem. TCP checksum offloading significantly reduced reduces host CPU use when using jumbo frames.  Stateless offload—QLogic 8100 Series Adapters support large send offloading (LSO).
PAGE 179
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Network applications that have a large number of short-lived connections, such as Web servers and data base servers, typically benefit from RSS. The RSS feature must be enabled on both the QLogic adapter and in the Microsoft Windows networking stack. By default, RSS is enabled on both the QLogic the CNA adapter (on a per port basis) and in the Microsoft Windows networking stack (globally).
PAGE 180
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 4. 5. Search for a DWORD named EnableRSS.  If none exists, RSS is enabled, and no action is required.  If a DWORD named EnableRSS exists, double-click EnableRSS, type 1, and then click OK to enable RSS. Restart the server on which the EnableRSS value has been modified.
PAGE 181
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Disabling RSS in the Microsoft Windows Networking Stack RSS can be disabled on the QLogic adapter on a per port basis by accessing the Windows property pages for the QLogic 10Gb PCI Ethernet adapter, or globally in Microsoft Windows.
PAGE 182
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Disabling RSS per Port Using the Windows Advanced Property Pages To disable RSS per port using the Windows Advanced Property pages (Figure 6-9): 1. Select ReceiveSideScaling under the Property box in the Advanced tab and set the value to Disabled. 2. Click OK to save the setting and deactivate RSS. Figure 6-9.
PAGE 183
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment HDS is disabled on QLogic 8100 Series Adapters by default and can be enabled using the Windows Advanced Property Pages for the QLogic 10Gb PCI Ethernet adapter port through the Windows Device Manager. To enable or disable HDS (Figure 6-10): 1. Select HeaderDataSplit under the Property box in the Advanced tab, and set the value to Enabled (or Disabled). 2.
PAGE 184
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment A protocol address, such as an IP address, is usually assigned to the physical adapter. However, when the QLogic NIC teaming driver and the QConvergeConsole CLI are used to create a team, the protocol address is assigned to the team adapter, and not to the physical adapters that make up the team.
PAGE 185
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Creating and Configuring a Team NOTE: Creating, modifying, or dissolving network teams resets the network connection. Do not attempt teaming configuration and reconfiguration on production systems. Two or more QLogic adapter ports must be available in a server to configure teaming; all members of the team must be QLogic adapter ports.
PAGE 186
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 6. The current VLAN/teaming driver version and the version to be installed are displayed. If this is correct, type Yes to proceed with the installation (Figure 6-12). Figure 6-12. Confirm VLAN/Teaming Driver Installation 6-18 7. When the VLAN/teaming driver installation is complete, type 8 and press ENTER to return to the main interactive menu. 8.
PAGE 187
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Figure 6-13. Creating a Team NOTE: Ports that have a VLAN ID assigned to them are not available to be team members. Remove VLAN IDs from a port to allow membership. For more information, refer to “VLAN Configuration” on page 6-52. 10. After successfully creating a team, a new logical interface appears in the Microsoft Windows Network Connections window as shown in Figure 6-14. Figure 6-14.
PAGE 188
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 11. Configure of the team by assigning a dynamic or static IP address to the QLogic VT-IM Miniport Driver logical interface. The windows command, ipconfig /all, lists the newly created team but not the physical interfaces in the team.
PAGE 189
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment After a team has been deleted, the corresponding QLogic VT-IM Miniport Driver logical interface is removed from the Microsoft Windows Network Connections window. Enter the Windows command, ipconfig /all, to list the physical network interfaces that comprised the team. VLAN Tagging VLAN is a logical grouping of network users and resources connected to a switch to segment a physical network.
PAGE 190
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 4. In the Host Level Info & Operations menu, type 2 and press ENTER to select Install/Update VLAN/Teaming Driver, All Adapters (Figure 6-16). Figure 6-16. Host Level Info & Operations Menu 5. At the prompt, Do you want to use external source for VLAN/Teaming driver?, choose one of the following (Figure 6-17):  No—Installs the VLAN/teaming driver bundled with the QConvergeConsole CLI.
PAGE 191
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 8. In the main Interactive Menu, type 4 and press ENTER to select Configure VLANs Menu. 9. In the Configure VLANs menu, type 3, and then press ENTER to select Add VLAN to Port or Team (Figure 6-18). a. Choose an entry from the list of available non-teamed physical ports and teams for which to assign a VLAN ID. b.
PAGE 192
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 12. After successfully assigning a VLAN ID to the team or interface, a new logical interface appears in the Microsoft Windows Network Connections window as shown in Figure 6-19, and the local area connection for the teaming logical interface would be disabled. Figure 6-19. VLAN Local Area Connection Entry 13.
PAGE 193
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment d. After successfully removing the VLAN ID assignment, press ENTER to return to the previous menu. Figure 6-20.
PAGE 194
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 1. Setup PXE boot and DHCP server. To setup a Microsoft Windows server as a DHCP and a OXE boot server, the following Windows services must be configured:  DHCP services  Remote installation services (RIS)  Windows deployment server (WDS) For detailed instructions about setting up a PXE boot server and a DHCP server, refer to the Microsoft documentation at http://technet.microsoft.com/.
PAGE 195
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment 3. Set up client servers BIOS boot order. Select 8100 Series NIC as the first boot device in the Boot order/Boot Device priority (Figure 6-21). The two QLogic UNDI v1.11 PXE-2 entries are dual-port QLogic 8100 Series Adapters. Figure 6-21. Boot Order in BIOS 4. Reboot the client system to boot over the network from the PXE boot server.
PAGE 196
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Windows Environment Figure 6-22. PXE Operation 6-28 1. As the server boots up, the QLogic adapter PXE boot code starts from the adapter Flash memory. This boot code is part of the multi-boot image that is resident on the QLogic adapter. 2. The PXE boot code broadcasts a DHCPDISCOVER message. 3.
PAGE 197
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Configuring the NIC in a Linux Environment Configuring the QLogic 8100 Series Adapter NIC function in RHEL 5 environments can be accomplished using the following built-in utilities and functions:  ethtool—An interface that displays and configures QLogic 8100 Series Adapter NIC function parameters. Use ethtool to configure offload settings and view network interface statistics.
PAGE 198
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Table 6-2.
PAGE 199
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Table 6-2. NIC Driver Parameters for Linux (Continued) Parameter Name mtu Description Jumbo Packet enables jumbo packet capability for TCP/IP packets. In situations where large packets make up the majority of traffic, and additional latency can be tolerated, Jumbo packets can reduce CPU use and improve wire efficiency. FCoE traffic uses an Ethernet frame size of 2554 bytes (baby jumbo).
PAGE 200
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment NOTE:  Reloading the QLogic NIC driver (qlge) does not interrupt the QLogic adapter FCoE function (qla2xxx). Neither does reloading the QLogic FCoE driver interrupt the NIC function.
PAGE 201
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 2. Add the options line for the appropriate driver setting (Figure 6-23), save the file, and then exit the editor. options qlge qlge_irq_type =1 qlge_mpi_coredump=0 Figure 6-23. Example modprobe.conf 3. Create a new RAMDISK (initrd image): a. Change directory to the location containing the RAMDISK images. For example: # cd /boot b. Create a backup copy of the RAMDISK (initrd) image.
PAGE 202
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Using sysfs The sysfs virtual file system, provided by Linux 2.6 kernels, is available in RHEL 5. It exports information about supported devices and drivers from the kernel device model into user space and configures devices and drivers. NOTE: Driver parameter changes that you make with sysfs are effective immediately, and do not interrupt I/O operations on the adapter.
PAGE 203
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 3. Verify that the values for the parameter have changed. The output of the following command should be 1 if the command in Step 2 was successful. For example: # cat /sys/module/qlge/parameters/ql2xmaxqdepth or cat /etc/bus/pci/drivers/qlge/module/parameters/qlge/qlge_irq_type Using ethtool To make temporary changes to the network configuration of a Ethernet device, use ethtool.
PAGE 204
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Making Persistent Changes Using ethtool To make changes that are persistent across reboots, choose one of the following:  Edit the file /etc/sysconfig/networking-scripts/ifcfg-ethX, add required ETHTOOL_OPTS, and then restart the network interface. Note that ETHTOOL_OPTS is limited to specifying only those parameters that are configured with the -s flag. 1.
PAGE 205
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Using ifconfig Use the Linux network interface configuration command ifconfig to modify the driver parameters that are listed in Table 6-2 that can be modified with ifconfig. For example: 1. Set the MTU of network interface eth0 to Jumbo # ifconfig eth0 mtu 9000 2. Verify that the MTU has been changed. # ifconfig eth0 Figure 6-26 shows the new MTU value Figure 6-26.
PAGE 206
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Figure 6-28. Verify NIC Driver qlge Figure 6-28 shows the PCI device IDs 85:00.0 and 85:00.1 are listed under the qlge section in sysfs. 3. List the contents of the soft link for the device ID. In Figure 6-29, find the net:ethX entries. The X in each entry represents the network interface ID, which indicates that the QLogic adapter NIC function is located in sysfs under /sys/class/net/ethX.
PAGE 207
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Figure 6-29 shows that the QLogic 8100 Series Adapter NIC function at PCI device ID 85:00.0 maps to eth0. QLogic driver parameters can now be displayed and configured through /sys/class/net/eth0. You can set network interface options and parameters using commands such as ifconfig and ethtool by querying with this network id (ethX).
PAGE 208
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Figure 6-30 shows the sample output for the eth0 interface, associating the driver with the interface and the location of the adapter hardware on the PCI bus. Figure 6-30. eth0 Interface Sample Output NOTE: Rebooting or reloading the QLogic FCoE driver (qlge), or adding other network interface cards may change the value of the network ID.
PAGE 209
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Switch Independent Bonding Switch independent teaming is implemented entirely at the adapter-host level. The Ethernet switch that is connected to the adapter is unaware of the team, and no switch involvement is required for team operation.
PAGE 210
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Ethernet Channel Bonding Driver The Linux bonding driver combines multiple network interfaces into a single logical bonded interface. The driver supports bonding modes such as failover and round-robin. The bonding driver also monitors link integrity. For bonding driver documentation, visit http://www.kernel.org/doc/Documentation/networking/bonding.txt.
PAGE 211
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Table 6-4. Linux Bonding Driver Parameters (Continued) Parameter Name Unit Description arp_ip_target IP address Specifies the IP addresses to use as ARP monitoring peers when arp_interval is > 0. These are the targets of the ARP request that are sent to determine the health of the link to the targets.
PAGE 212
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Table 6-4. Linux Bonding Driver Parameters (Continued) Parameter Name mode Unit Integer or string Description Specifies a bonding policy Default Value balance-rr or 0 Allowed Values  balance-rr or 0—Round-robin policy transmits packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
PAGE 213
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Table 6-4. Linux Bonding Driver Parameters (Continued) Parameter Name Unit use_carrier Default Value Description Specifies MII/ETHTOOL ioctls or netif_carrier_ok() for use by miimon to determine the link status. MII/ETHTOOL ioctls is less efficient and uses a deprecated calling sequence within the kernel.
PAGE 214
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment If the command produces no output, the bonding driver is already loaded. If the output is similar to Figure 6-32, the bonding driver has been successfully loaded. Figure 6-32.
PAGE 215
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 2. Load the Linux bonding driver module and specify parameters to be changed. One or more parameters can be specified separated by a space. The following command sets MII link monitoring frequency to 100ms and enables the round-robin policy mode: # modprobe -v miimon=100 mode=0 3.
PAGE 216
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment NOTE: Depending on the server hardware, the RAMDISK file name may be different. The command is successful if there is no output. d. Reboot the server for the new RAMDISK image to take affect by issuing the following command: # shutdown -r now 4.
PAGE 217
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment In this command:  bond0 is the bonding interface created by the ifconfig command in Step 1.  eth0 and eth1 are the QLogic adapter network interfaces form a part of this bond. Persistent Bonding Configuration NOTE: Persistent configuration changes are preserved across server reboots.
PAGE 218
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment a. Open the file /etc/sysconfig/network-scripts/ifcfg-ethx. For example: # vi /etc/sysconfig/network-scripts/ifcfg-eth0 b. Append the following commands to the file to modify the physical interface. MASTER=bond0 SLAVE=yes c. Save the file, and then exit the editor. 4. Repeat Step 3 for each physical network interface that is to be part of the bonding interface. 5.
PAGE 219
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 2. Enter the ifconfig command, and examine the output. Figure 6-34 shows that the bond0 interface status and IP address information. The MAC addresses for the two bonded ports (eth0 and eth1) are the same. After the bond has been brought down and the bonding driver removed, the original MAC addresses are restored. Figure 6-34.
PAGE 220
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment VLAN Configuration A virtual LAN (VLAN) is a logical grouping of network hosts connected to a switch to achieve a logical segmentation of a physical network. By default, all switches make up a broadcast domain in the layer-2 switched network. Creating a VLAN breaks up a broadcast domain into smaller domains within a switch by assigning different ports to different subnets.
PAGE 221
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Loading the VLAN 802.1q Kernel Module In most RHEL 5 environments, the VLAN 802.1q kernel module is loaded by default. VLAN interfaces cannot be created over the QLogic adapter NIC function without the VLAN 802.1q kernel module. To determine whether the VLAN 802.1q kernel module is loaded, issue the following command: # lsmod | grep 8021q If the command produces no output, the VLAN 802.
PAGE 222
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment This section describes nonpersistent and persistent configuration of VLAN interfaces over the NIC function using VLAN 802.1q Kernel Module and user space utilities. Nonpersistent configuration (ifconfig and vconfig) changes are lost across server reboots. Before configuring VLANs the physical/bond interface should be in an UP state in Linux. The following procedures assume that the Linux VLAN 802.
PAGE 223
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment b. Open the VLAN interface network configuration script with an editor, and make the following changes:  Replace the string DEVICE=eth0 with DEVICE=eth0.5.  Append the string VLAN=yes to the end of the file. Figure 6-36 shows the resulting file. Figure 6-36. Creating a Network Configuration File—VLAN Interface c. 2. Save the file, and then exit the editor.
PAGE 224
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 2. Enter the ifconfig command, and then examine the output. For example: # ifconfig eth0.5 This command shows the eth0.5 VLAN interface status, statistics, and IP address. Disabling a VLAN interface To disable a VLAN interface, enter the following command: # ifconfig down In this command, is the VLAN interface name.
PAGE 225
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Wake On LAN Wake on LAN is not supported for QLogic 8100 Series Adapters. PXE Boot PXE boot code is a part of the QLogic 8100 Series Adapter multi-boot image that enables a networked server to boot with the images provided by remote servers. The PXE protocol, illustrated in Figure 6-38, operates as follows: 1.
PAGE 226
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment Figure 6-38. PXE Flow Diagram 6-58 1. As the server boots up, it starts the QLogic adapter PXE boot code from the adapter Flash memory. This boot code is part of the multi-boot image that is resident on the QLogic adapter. 2. The PXE boot code broadcasts a DHCPDISCOVER message. 3.
PAGE 227
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 7. The PXE boot code downloads the executable boot file using TFTP and executes the boot file. Prerequisites for PXE Boot PXE boot requires the following:  A client server with a PXE-compliant BIOS or UEFI implementation and a QLogic 8100 Series Adapter. This server boots through PXE with Microsoft Windows.
PAGE 228
6–Configuring NIC Functionality in the Converged Network Adapter Configuring the NIC in a Linux Environment 6-60 FE0254601-00 A
PAGE 229
7 Configuring FCoE in a Windows Environment Overview The QLogic 8100 Series Converged Network Adapter is dual-function adapter comprising FCoE and NIC functions. This section describes the characteristics, configurations, and features of the FCoE function. Driver Parameters Table 7-1 lists the FCoE parameters, their default values, allowed values, and how to change values.
PAGE 230
7–Configuring FCoE in a Windows Environment Driver Parameters Table 7-1. Driver Parameters Parameter Description Default Range Configuration Method 0–2 seconds Fast!UTIL, QCon- 512, 1,024, 2,048 Fast!UTIL, QCon- Disabled Enabled, Disabled QConvergeConsole GUI or QConvergeConsole CLI Enables or disables the logging of driver-detected events that occur in the driver or the Fibre Channel bus.
PAGE 231
7–Configuring FCoE in a Windows Environment Driver Parameters Table 7-1. Driver Parameters Parameter Description Default Range Configuration Method 0, 8, 16, 32, 64, 128, 256 Fast!UTIL, QCon- Enabled Enabled, Disabled QConvergeConsole GUI or QConvergeConsole CLI Enables or disables the drivers to issue a Target Reset command to all devices on the loop when a SCSI Bus Reset command is issued.
PAGE 232
7–Configuring FCoE in a Windows Environment Driver Parameters Table 7-1. Driver Parameters Parameter Description Default Enable Fibre Channel Tape Support Enables or disables FCP-2 recovery. Disable this parameter if the Fibre Channel adapter is connected to a storage subsystem. Most storage subsystems do not support sending I/O from the same Fibre Channel adapter to both a storage subsystem and a tape device.
PAGE 233
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization Table 7-2. Operation Mode Values Values Operation 0 Disables ZIO mode. 5 Enables ZIO mode 5. DMA transfers response queue entries into the response queue. No interrupt is generated unless the Interrupt Delay Timer updates the Response Queue-Out Pointer register. 6 Enables ZIO mode 6.
PAGE 234
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization NPIV allows a single physical Fibre Channel adapter port to function as multiple logical ports, each with its own WWPN, as shown in Figure 7-1. Figure 7-1. N_Port ID Virtualization QLogic CNA NPIV Solution To complement Microsoft and other server virtualization software solutions, QLogic has extended virtualization capabilities to the adapter hardware through NPIV. All QLogic 8100 Series Adapters support NPIV.
PAGE 235
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization  QLogic 8100 Series Adapter driver—QLogic STOR Miniport Driver 9.1.8.17 or later.  QLogic QConvergeConsole GUI, version 1.0.28, or later; or QConvergeConsole CLI Build, version 1.0.0, build 46, or later.  Additional Microsoft software components may be required to deploy Microsoft Virtual Server 2005 or Windows Server 2008 Hyper-V. For more information, consult the specific Microsoft documentation.
PAGE 236
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization Figure 7-2. Select Port to Create a Virtual Port 4. In the Number of vPort to create box, select the number of virtual ports you want to create, then click Update. The Generated WWNs window displays unique WWNs for the selected number of vPorts. The generated WWN for multiple virtual ports supports the following: 7-8  The driver determines the number of vPorts allowed.
PAGE 237
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization NOTE: To benefit from I/O segregation and NPIV monitoring after creating a virtual port, configure zoning on the FCoE switch, and configure selective LUN presentation on the Fibre Channel or FCoE target array. For information about configuring the FCoE switch and target array, refer to the product documentation 7. Select Refresh from the Host drop-down menu and click OK when prompted to refresh the host.
PAGE 238
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization 2. Inspect the switch Fibre Channel database to verify that the vPort has logged into the connected NPIV-enabled FCoE switch. Refer to the corresponding switch documentation for details. 3. If possible, verify that the vPort has logged in to the storage array through the storage array management interface. 4.
PAGE 239
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization Figure 7-4. Select Virtual Ports to Delete 5. Click the Delete button, located at the bottom of the screen. A dialog box prompts you for a password. 6. Type the administrative password, and then click OK. A dialog box appears, asking if you want to refresh the host view. 7. Click OK to refresh the host immediately or click Cancel if you want to refresh the view at a later time.
PAGE 240
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization 3. Verify that none of the LUNs presented to the vPort through the zoned storage array ports are visible to the Microsoft Windows operating system. Check for the absence of these LUNs as disks by navigating to the Disk Manager through the Device Manager. Virtual Port Features and Limitations When using a virtual port, the Settings and Utilities tabs are not available in QConvergeConsole GUI.
PAGE 241
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization Implementing Adapter-Based Quality of Service The QLogic 8100 Series Adapter solution provides for standards-based quality of service (QoS), ensuring high-quality performance for applications that require preferential delivery. The QLogic QoS solution is based on assigning QoS levels to virtual ports (NPIV ports). You can configure QoS using the priority method or the bandwidth method, as shown in Figure 7-5.
PAGE 242
7–Configuring FCoE in a Windows Environment N_Port ID Virtualization NOTE: The QoS levels described in this section apply only to SAN and FCoE traffic. These QoS levels do not affect Ethernet traffic QoS levels and NIC traffic bounds.
PAGE 243
7–Configuring FCoE in a Windows Environment Boot from SAN Boot from SAN For legacy servers, the most common boot method was to boot from a direct-attached disk. When booting from a direct-attached disk, the server BIOS/UEFI locates the SCSI/IDE adapter BIOS, which contains instructions that enable the server to determine which of its internal direct-attach disks is the boot device. This boot method is called local boot.
PAGE 244
7–Configuring FCoE in a Windows Environment Boot from SAN  If failover capabilities are required during boot-from-SAN, multiple QLogic 8100 Series Adapters are required to create redundant paths to the boot device. Consult the server manufacturer’s documentation to determine the maximum number of QLogic 8100 Series Adapters that the server can support.
PAGE 245
7–Configuring FCoE in a Windows Environment Boot from SAN Confirm the following:  The adapter port has exclusive access to this LUN.  The LUN host type matches the operating system that is to be installed on this LUN. Each server must have its own dedicated boot LUN. Two servers cannot share the same boot LUN. Boot-from-SAN Configuration Boot-from-SAN requires the configuration of the QLogic 8100 Series Adapter, the FCoE switch, and the storage array.
PAGE 246
7–Configuring FCoE in a Windows Environment Boot from SAN Single-Path Configuration A single-path configuration is the simplest configuration for boot-from-SAN for QLogic 8100 Series Adapters. The single-path configuration consists of a single adapter port connected to a converged networking switch (FCoE switch), which is then connected to the storage controller (SP) of a storage array.
PAGE 247
7–Configuring FCoE in a Windows Environment Boot from SAN Multipath Topology Multipath topology provides fault tolerance through redundant SAN components: two adapter ports, two converged networking switches, and access to the boot LUNs through two independent storage array controllers. Figure 7-7 shows the SAN components and their connections. The server has access to the primary and alternate boot LUNs through two independent paths. A single point of failure is unlikely to with this configuration.
PAGE 248
7–Configuring FCoE in a Windows Environment Boot from SAN Configuring an Adapter to Boot-from-SAN This section describes how to configure a QLogic 8100 Series Adapter to boot the Microsoft Windows operating system from the SAN. 1. Install the QLogic 8100 Series Adapter, and update the firmware, if necessary. For information about updating the firmware, refer to “Firmware Upgrades” on page 3-33. 2. Connect the SAN components in a single-path topology, as shown in Figure 7-6.
PAGE 249
7–Configuring FCoE in a Windows Environment Boot from SAN i. Press ESC to return to the Configuration Settings menu. Select Selectable Boot Settings, and then press Enter. j. Enable the Selectable Boot option in the Selectable Boot Settings menu. Move the cursor to the Selectable Boot option, and then press ENTER (Figure 7-8). Figure 7-8. Selectable Boot Settings Menu k. Specify the primary boot LUN. Move the cursor to (Primary) Boot Port Name, Lun option. Type the LUN number, and then press ENTER.
PAGE 250
7–Configuring FCoE in a Windows Environment Boot from SAN 5. Configure the UEFI server (Windows Server 2008 only). To configure a BIOS server, refer to Step 4. The boot-from-SAN configuration process for UEFI servers depends on the server make and model. The following instructions configure the adapter for boot-from-SAN using the EFI shell.
PAGE 251
7–Configuring FCoE in a Windows Environment Boot from SAN i. Select Show Translation, under Information, from the Driver Configuration Main Menu (Figure 7-9). This option displays the target and LUN information. Main Menu NVRAM Parameters 1. Edit Adapter Settings 2. Edit Advanced Settings 3. Edit Database 4. Edit Boot Settings Information 5. Show Database 6. Show Translation 7. Show NVRAM Buffer 8. Info 9. Help Operation 10. Abandon 11. Write 12. Quit Figure 7-9.
PAGE 252
7–Configuring FCoE in a Windows Environment Boot from SAN n. Enable both Selective Login and Selective LUN Logins (Figure 7-10). Enabling Selective Logins restricts the discovery of targets [WWPNs] to what is specified in the database as a boot device. Enabling Selective LUN Logins restricts the discovery of LUNs to what is specified in the database as a boot device LUN number. Edit Boot Settings 0. Previous Menu 1. Enable Alternate Boot Device [n] 2. Enable Selective Login [n] Y 3.
PAGE 253
7–Configuring FCoE in a Windows Environment Boot from SAN 7. To configure a multipath/load-balanced boot-from-SAN configuration: a. Connect the second adapter port, as shown in Figure 7-7. b. Modify the storage array configuration to present the primary and alternate boot LUNs to both storage array controllers. c. Modify switch zoning to ensure that the second adapter port has access to both storage array controllers. d.
PAGE 254
7–Configuring FCoE in a Windows Environment Boot from SAN 7-26 FE0254601-00 A
PAGE 255
8 Configuring FCoE in a Linux Environment Overview The QLogic 8100 Series Converged Network Adapter is dual-function adapter comprising FCoE and NIC functions. This section describes the characteristics, configurations and features of the QLogic 8100 Series Adapter FCoE function for Linux. FCoE Driver Parameters for Linux Table 8-1 lists the FCoE driver parameters for Linux, their default values, allowed values, and configuration methods.
PAGE 256
8–Configuring FCoE in a Linux Environment FCoE Driver Parameters for Linux Table 8-1. FCoE Driver Parameters for Linux Description ql2xextended_error_l ogging Enables or disables the driver to print verbose logging information. 0 ql2xdevdiscgoldfw Enables or disables device discovery with golden firmware. 0 Enables or disables FDMI registration. 0 ql2xmaxqdepth Maximum queue depth reported to SCSI mid-level per device. The queue depth specifies the number of outstanding requests per LUN.
PAGE 257
8–Configuring FCoE in a Linux Environment FCoE Driver Parameters for Linux Table 8-1. FCoE Driver Parameters for Linux Parameter Interrupt Delay Timer Description The time interval, in 100ms increments, between the response queue update and the interrupt generation. Default 0 Range 0–255 Configuration Method Fast!UTIL, QConvergeConsole GUI, or QConvergeConsole CLI This parameter can be specified only if the Operation Mode parameter is enabled. Otherwise, this parameter is set to zero.
PAGE 258
8–Configuring FCoE in a Linux Environment FCoE Driver Parameters for Linux Table 8-1. FCoE Driver Parameters for Linux Parameter Description Default Maximum number of commands that a port can execute at one time. When a port reaches its execution throttle, the port can execute no new commands until the current command execution is complete. 65,535 Number of times that the software tries to log in to a device. 8 Port Down Retry Count Time to wait before reissuing a command to a port that is down.
PAGE 259
8–Configuring FCoE in a Linux Environment FCoE Driver Parameters for Linux Table 8-1. FCoE Driver Parameters for Linux Parameter Enable OoOFR Description Default Range Enables or disables out-of-order frame reassembly. This parameter reassembles out-of-order frames as they are received, minimizing network congestion by eliminating the re-transmission of frames and exchanges.
PAGE 260
8–Configuring FCoE in a Linux Environment Configuring Driver Parameters Using modprobe Table 8-1. FCoE Driver Parameters for Linux Parameter Description Default Enable Fibre Channel Tape Support Enables or disables FCP-2 recovery. Disable this parameter if the Fibre Channel adapter is connected to a storage subsystem. Most storage subsystems do not support sending I/O from the same Fibre Channel adapter to both a storage subsystem and a tape device.
PAGE 261
8–Configuring FCoE in a Linux Environment Configuring Driver Parameters Using modprobe 2. Load the QLogic FCoE driver module, and specify one or more parameters separated by a space. The following example enables MSI-X and Extended Error Logging: #modprobe –v qla2xxx ql2xenablemsix =1 ql2xextended_error_logging=1 3.
PAGE 262
8–Configuring FCoE in a Linux Environment Configuring Driver Parameters Using sysfs 3. Save and exit the file etc/modprobe.conf. 4. Create a new RAMDISK (initrd image): a. Change to the directory that contains the RAMDISK images by issuing the following command: # cd /boot b. Create a backup copy of the RAMDISK (initrd) image by issuing the following command: # cp initrd-[kernel version].img initrd-[kernel version].img.bak c.
PAGE 263
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-2. FCoE Driver Parameters that can be Modified with Sysfs Sysfs Location /sys/module/qla2xxx/parameters Driver Parameters ql2xmaxqdepth ql2xplogiabsentdevice ql2xqfullrampup ql2xqfulltracking /sys/class/scsi_host/hostX/ zio (operation mode) zio_timer (interrupt delay timer) To modify FCoE driver parameters using sysfs: 1.
PAGE 264
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-3. QConvergeConsole and Fast!UTIL Comparison Installation Required for RHEL 5 Utility Online or Offline How to Access Agent (qlremote), QConvergeConsole GUI, or QConvergeConsole CLI Yes Online, requires a functioning operating system to run Download from http://driverdownloads.qlogic.com/. For information about installing QLogic utilities, refer to “Management Tool Installation” on page 4-26.
PAGE 265
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities To configure a parameter from the list of HBA parameters: 1. Expand the port number in the system tree (left pane) of the QConvergeConsole browser window. 2. Click the FCoE port node. 3. Click the Parameters tab in the right pane, as shown in Figure 8-2. Figure 8-2.
PAGE 266
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities To configure a parameter from the list of advanced HBA parameters: 1. Expand the port number in the system tree (left pane) of the QConvergeConsole browser window. 2. Click the FCoE port node. 3. Click the Parameters tab in the right pane. 4. Click the Advanced HBA Parameters subtab, as shown in Figure 8-3. Figure 8-3.
PAGE 267
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-5.
PAGE 268
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Figure 8-5. Fast!UTIL Advanced Adapter Settings Displaying FCoE Driver Parameters Using sysfs Table 8-6 lists the FCoE driver parameters and sysfs locations by which you can display parameter values using sysfs. For information about configuring FCoE driver parameters using sysfs, refer to “Configuring Driver Parameters Using sysfs” on page 8-8.
PAGE 269
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-6. sysfs FCoE Driver Parameters and File Locations Sysfs Location /sys/module/qla2xxx/parameters Parameters ql2xallocfwdump ql2xdevdiscgoldfw Description Refer to “FCoE Driver Parameters for Linux” on page 8-1.
PAGE 270
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-6.
PAGE 271
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-6. sysfs FCoE Driver Parameters and File Locations Sysfs Location /sys/class/fc_host/h ostX/statistics /sys/class/scsi_host /hostX/ FE0254601-00 A Parameters Description loss_of_sync_count Number of times synchronization is lost nos_count Not operational primitive sequence (NOS) count.
PAGE 272
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-6.
PAGE 273
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Table 8-6.
PAGE 274
8–Configuring FCoE in a Linux Environment Configuring FCoE Parameters Using QLogic Utilities Figure 8-6. Locating QLogic 8100 Adapter PCI Devices Figure 8-6 shows PCI bus device IDs 85:00.2 and 85:00.3 for the two FCoE adapter ports. 3. Search the qla2xxx driver to verify that the driver is managing the PCI bus device ID as 85:00.2 and 85:00.3. For example: #ls –l /sys/bus/pci/drivers/qla2xxx The search list in Figure 8-7 shows that the PCI device IDs, 85:00.2 and 85:00.
PAGE 275
8–Configuring FCoE in a Linux Environment Online Storage Configuration and Reconfiguration Figure 8-8. Identifying the SCSI Host ID Figure 8-8 shows that the QLogic 8100 Series Adapter FCoE function at PCI device ID 85:00.2 maps to host6. QLogic driver parameters can now be configured using /sys/class/scsi_host/host6 and /sys/class/fc_host/host6. NOTE: Rebooting the server or reloading the QLogic FCoE driver (qla2xxx) may change the value of the SCSI host ID.
PAGE 276
8–Configuring FCoE in a Linux Environment Adapter FCoE Performance Tuning Adapter FCoE Performance Tuning The following FCoE driver parameters affect adapter performance:  Operation Mode  Interrupt Delay Timer  Execution Throttle  Frame Size (Fibre Channel)  Queue Depth The default values for Frame Size and Execution Throttle provide maximum performance for most environments.
PAGE 277
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization Queue Depth (qla2xmaxqdepth) The Queue Depth parameter specifies the maximum number of SCSI command buffers that an adapter port can allocate. This parameter determines the maximum number of outstanding commands that can execute on any one adapter port. The default for the Queue Depth parameter is 32, which provides the best performance for most environments.
PAGE 278
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization Figure 8-9. N_Port ID Virtualization QLogic CNA NPIV Solution To complement Linux server virtualization software solutions, QLogic has extended virtualization capabilities to the adapter hardware through NPIV. All QLogic 8100 Series Adapters support NPIV. QLogic supports creating, deleting, and managing NPIV ports through the FCoE driver sysfs interface. The sysfs virtual file system is available in all RHEL 5 installations.
PAGE 279
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization  A QLogic 8100 Series Adapter FCoE driver—qla2xxx, latest version.  QLogic 8100 Series Adapter FCoE firmware—the FCoE firmware is bundled with the multi boot image. Use the latest version. NOTE: QLogic 8100 Series Adapters support a maximum of 63 virtual ports per adapter port in RHEL 5 environments. This number may be limited by the capabilities of the FCoE switch.
PAGE 280
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization 4. To benefit from I/O segregation and NPIV monitoring after creating a virtual port, configure zoning on the FCoE switch, and configure selective LUN presentation on the Fibre Channel or FCoE target array. For information about configuring the FCoE switch and target array, refer to the switch and target array documentation. CAUTION! If you reload the FCoE driver (qla2xxx), or reboot the server, all virtual ports are discarded.
PAGE 281
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization Figure 8-10.
PAGE 282
8–Configuring FCoE in a Linux Environment N_Port ID Virtualization To disable a virtual port, issue the following command, where X is the port SCSI host ID: #echo 1 > /sys/class/scsi_host/hostX/vport_disable To verify that the virtual adapter port has been deleted:  Confirm that the sysfs entry for the virtual port has been removed from /sys/class/scsi_host/.  Confirm that the virtual port is no longer logged into the FCoE switch by inspecting its Fibre Channel name server database.
PAGE 283
8–Configuring FCoE in a Linux Environment Boot-from-SAN Figure 8-11. Comparing NPIV Physical and Virtual Ports Boot-from-SAN For legacy servers, the most common boot method was to boot from a direct-attached disk. When booting from direct-attached disk, the server BIOS/UEFI locates the SCSI/IDE adapter BIOS, which contains instructions that enable the server to determine which of its internal direct-attach disks is the boot device. This boot method is called local boot.
PAGE 284
8–Configuring FCoE in a Linux Environment Boot-from-SAN Because the boot device resides on the SAN, it simplifies server management. Separating the boot image from each server allows administrators to leverage the advanced capabilities of storage arrays to achieve high availability, improved data integrity, rapid provisioning, and more efficient storage management.
PAGE 285
8–Configuring FCoE in a Linux Environment Boot-from-SAN  Set the boot order in the system BIOS configuration menu: first, the optical drive, then the disk, and then the SAN-boot device. Placing the optical drive at the top of the boot order enables the server to boot from an RHEL 5 installation media, and then install the operating system on the SAN boot device. If the boot media is a PXE server (for LAN boot), place the QLogic 8100 Series Adapter at the top of the boot order.
PAGE 286
8–Configuring FCoE in a Linux Environment Boot-from-SAN Storage Array Requirements Some storage arrays cannot support boot-from-SAN for specific environments. Consult the storage array documentation to confirm that the array and the firmware support boot-from-SAN. Consider the storage array and any limitations regarding boot-from-SAN. Create and present an appropriately-sized LUN to the QLogic 8100 Series Adapter port. Ensure that:  The adapter port has exclusive access to this LUN.
PAGE 287
8–Configuring FCoE in a Linux Environment Boot-from-SAN Server Adapter Port 1 Converged Networking Switch Controller A Storage Array LUN 1 Primary Boot Device LUN 2 Alternate Boot Device LUN 3 Alternate Boot Device LUN 4 Alternate Boot Device Figure 8-12.
PAGE 288
8–Configuring FCoE in a Linux Environment Boot-from-SAN Server CNA Port 1 Converged Networking Switch 1 Controller A CNA Port 2 Converged Networking Switch 2 Controller B Storage Array LUN 1 (Primary Boot Device) LUN 2 (Alternate Boot Device) LUN 3 (Alternate Boot Device) LUN 4 (Alternate Boot Device) Figure 8-13.
PAGE 289
8–Configuring FCoE in a Linux Environment Boot-from-SAN Configuring an Adapter to Boot-from-SAN This section describes how to configure a QLogic 8100 Series Adapter to boot the RHEL 5 operating system from the SAN. 1. Install the QLogic 8100 Series Adapter, and update the firmware, if necessary. For information about updating the firmware, refer to “Firmware Upgrades” on page 4-21. 2. Connect the SAN components in a single-path topology as shown in Figure 8-12.
PAGE 290
8–Configuring FCoE in a Linux Environment Boot-from-SAN h. Press ESC to return to the Configuration Settings menu. Select Selectable Boot Settings, and then press ENTER. i. Enable the Selectable Boot option in the Selectable Boot Settings menu. Move the cursor to the Selectable Boot option, and then press ENTER (Figure 8-14). Figure 8-14. Selectable Boot Settings menu j. Specify the primary boot LUN. Move the cursor to (Primary) Boot Port Name, Lun option, and then press ENTER.
PAGE 291
8–Configuring FCoE in a Linux Environment Boot-from-SAN 5. Configure the UEFI server. To configure a BIOS server, refer to Step 4. The boot-from-SAN configuration process for UEFI servers depends on the server make and model. The following instructions configure the adapter for boot-from-SAN using the EFI shell. If a UEFI shell is not available on the server being configured, consult the server documentation for information about obtaining a shell or for alternate ways to configure the adapter. a.
PAGE 292
8–Configuring FCoE in a Linux Environment Boot-from-SAN i. Select Show Translation, under Information, from the Driver Configuration Main Menu (Figure 8-15). This option displays the target and LUN information. Main Menu NVRAM Parameters 1. Edit Adapter Settings 2. Edit Advanced Settings 3. Edit Database 4. Edit Boot Settings Information 5. Show Database 6. Show Translation 7. Show NVRAM Buffer 8. Info 9. Help Operation 10. Abandon 11. Write 12. Quit Figure 8-15. Driver Configuration Main Menu 8-38 j.
PAGE 293
8–Configuring FCoE in a Linux Environment Boot-from-SAN n. Enable both Selective Login and Selective LUN Logins (Figure 8-16). Enabling Selective Logins restricts the discovery of targets to what is specified in the database as a boot device. Enabling Selective LUN Logins restricts the discovery of LUNs to what is specified in the database as a boot device LUN number. Edit Boot Settings 0. Previous Menu 1. Enable Alternate Boot Device [n] 2. Enable Selective Login [n] Y 3.
PAGE 294
8–Configuring FCoE in a Linux Environment Boot-from-SAN 9. Set the SAN boot device (QLogic adapter for BIOS; fibre disk for UEFI) at the top of the boot order. 10. To configure a multipath/load-balanced boot-from-SAN configuration: a. Connect the second adapter port, as shown in Figure 8-13. b. Modify the storage array configuration to present the primary and alternate boot LUNs to both storage array controllers. c.
PAGE 295
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities 2. On the Advanced Boot Loader Configuration screen, select Change Drive Order. Figure 8-18. Select Advanced Boot Loader Options RHEL 5 Install step2 3. In the Edit Drive Order window, move the entry for the boot LUN up to the first entry, and then click OK. 4. Continue installing RHEL 5. Using the QLogic Linux Utilities This subsection describes how to obtain, install, and launch the QLogic Linux utilities.
PAGE 296
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-9.
PAGE 297
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Using the Utility This utility has a command line interface and a menu interface. Command Line Interface To start the Dynamic TGT-LUN Discovery command line interface, issue the following command followed by one or more command line options: # ./ql-dynamic-tgt-lun-disc.sh Table 8-11 lists the Dynamic TGT-LUN Discovery utility command line options and their abbreviations. Table 8-11.
PAGE 298
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-12. TGT-LUN Discovery Utility Tasks and Commands Task Command Examples Rescan all adapters # ./ql-dynamic-tgt-lun-disc.sh --scan Rescan all adapters and remove lost LUNs # ./ql-dynamic-tgt-lun-disc.sh --scan --refresh Rescan all adapters with a Run a proc-based scan # ./ql-dynamic-tgt-lun-disc.sh --scan --proc Rescan all adapters and set the maximum number of LUNs to be scanned # ./ql-dynamic-tgt-lun-disc.
PAGE 299
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-13 describes the main menu options. Table 8-13. Dynamic TGT-LUN Main Menu Option Description ALL HOSTS SCAN Scan all QLogic adapters in the system, and report new LUNs that are found.
PAGE 300
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-14. Select Host to Scan Menu (Continued) Option Description GO BACK TO PREVIOUS SCREEN Return to the main menu. QUIT Exit the menu interface. HBA Collect Utility The HBA Collect utility creates a compressed file containing debugging and configuration options from the RHEL 5 host. Run this utility when requested by QLogic Technical Support.
PAGE 301
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Package Contents Table 8-15 describes the files in the HBA Collect utility package. Table 8-15. HBA Collect Utility Package Files File Description COPYING GNU general public license that describes rights to copy, distribute, and use the open source content in this Linux tool. ql-hba-collect.sh Script file that gathers diagnostic information for troubleshooting on the RHEL 5 host ql-hba-snapshot-x.
PAGE 302
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities FC HBA Snapshot Utility The FC HBA Snapshot utility displays information about connected QLogic adapters, including the following:  WWPN  Port ID  All QLogic adapters in the system  LUNs  Parameters or options that can be passed to the QLogic driver  Statistics By default, the utility uses the sysfs Linux file system, but can also use the proc file system.
PAGE 303
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-17 describes the FC HBA Snapshot utility command line options. Table 8-17. FC HBA Snapshot Utility Command Line Options Option (Abbreviation) Description Host Number or --all (-a) Specifies the host number of the adapter for which to display information. If you omit the host number, the utility displays information for all hosts.
PAGE 304
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-18. FC HBA Snapshot Utility Command Example (Continued) Task List QLogic adapter driver parameters Command Example # ./ql-hba-snapshot.sh --parameters FC HBA Change LUN State Utility This utility is a combination command line/menu interface that changes the state (online/offline) of LUNs connected to a QLogic adapter, without rebooting the server.
PAGE 305
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Command Line Interface To use the command line interface, type one of the following commands: # ./ql-lun-state-online.sh or # ./ql-lun-state-online.sh --all where host number list a list of one or more SCSI host IDs (delimited by spaces) of the QLogic Converged Network Adapter physical or virtual ports. If you omit host number list and the --all option, the utility prompts you to correct your entry.
PAGE 306
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Menu Interface To open the menu interface, issue the following command: # ./ql-lun-state-online.sh –interactive  If no offline LUNs are found, the menu interface does not start, the utility informs you that no offline LUNs were found, and the utility closes.  If offline LUNs are found, the utility main menu appears, as shown in the example in Figure 8-21.
PAGE 307
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities The Set Device Command Timeout utility can set the timeout value for target devices on a selected host, or it can set a common value for all devices on all hosts. This utility sets a timeout value for each target port and applies to all LUNs that are visible through that target port. This utility does not apply to targets that are visible through QLogic adapter virtual ports.
PAGE 308
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-23 describes the Set Device Command Timeout utility command options. Table 8-23.
PAGE 309
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-24 lists a set of tasks and the commands that perform them for a target device with the following sysfs path: /sys/class/scsi_host/host4/device/rport-4:0-1 In this path, host=4 and target=0. Table 8-24. Set Device Command Timeout Utility Command Examples Task FE0254601-00 A Command Example Display the timeout value for all devices connected to QLogic adapters. # ./ql-set-cmd-timeout.
PAGE 310
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Menu Interface To open the Set Device Command Timeout utility menu interface, issue the following command to display the menu shown in Figure 8-22: # ./ql-set-cmd-timeout.sh –interactive Figure 8-22. Set Device Command Timeout Utility Main Menu Table 8-25 describes the Set Device Command Timeout Utility Main Menu Options. Table 8-25.
PAGE 311
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Figure 8-23 shows an example of the Select Target for HostX menu. The actual menu varies depending on the number of targets that are visible through the QLogic adapter port. Figure 8-23. Select Target for HostX Menu Table 8-26 describes the Select Target for HostX menu options. Table 8-26. Select Target for HostX Menu Options Option Description TargetX Target device for which to set or display timeout values.
PAGE 312
8–Configuring FCoE in a Linux Environment Using the QLogic Linux Utilities Table 8-27 describes the Modify/Display Timeout menu options. Table 8-27. Modify/Display Timeout Menu Options Option 8-58 Description MODIFY TIMEOUT Specify the timeout value, in seconds, for the selected target(s). DISPLAY TIMEOUT Display the current timeout value for the selected target(s). GO BACK TO MAIN MENU Return to the main menu. QUIT Exit the Set Device Command Timeout utility.
PAGE 313
9 Offline Utilities Overview QLogic provides offline adapter configuration and Flash programming utilities with the adapter multi-boot code for advanced users. The following utilities are available for adapters installed in both BIOS and UEFI servers:  Fast!UTIL  EFICFG  FlasUTIL  EFIUTIL The Fast!UTIL and EFICFG configuration utilities enable advanced users to customize the configuration of the QLogic 8100 Series Adapter and connected Fibre Channel devices.
PAGE 314
9–Offline Utilities Fast!UTIL The QLogic Flash programming utility is a DOS utility with command line options. Fast!UTIL The Fast!UTIL utility is for offline QLogic 8100 Series Adapters that are installed on BIOS servers. Fast!UTIL performs the following tasks:  Configures general and advanced adapter settings, selects boot devices, restores default adapter settings, and displays raw NVRAM data.  Displays information about Fibre Channel devices connected to the adapter.
PAGE 315
9–Offline Utilities Fast!UTIL After a few seconds, the system confirms that Fast!UTIL initialization is in progress. If more than one adapter is installed on the server, Fast!UTIL prompts you to select an adapter to configure (Figure 9-2). Figure 9-2. Selecting an Adapter After an adapter is selected, the Fast!UTIL Options menu appears (Figure 9-3). Figure 9-3.
PAGE 316
9–Offline Utilities Fast!UTIL The Fast!UTIL Options menu presents the following options:  Configuration Settings  Scan Fibre Channel Devices  Fibre Disk Utility  Loopback Data Test  Select Host Adapter  Exit Fast!UTIL After you make changes, the Fast!UTIL utility restarts the server to put those changes into effect.
PAGE 317
9–Offline Utilities Fast!UTIL Table 9-1 describes the parameters in the Adapter Settings window. Table 9-1. Adapter Setting Parameters Parameter BIOS Address Description I/O address where the QLogic BIOS code is stored when you start the Fast!UTIL utility or when the BIOS code is enabled by default. This is the address of the BIOS code in ROM shadow memory. Multiple adapters can be installed in the server, but only one BIOS instance is loaded for all adapters.
PAGE 318
9–Offline Utilities Fast!UTIL Table 9-1. Adapter Setting Parameters (Continued) Parameter Fibre Channel Tape Support Description Enables or disables FCP-2 recovery. Disable Fibre Channel Tape Support if the adapter is connected to a storage subsystem and not to a tape device. Most storage subsystems do not support sending I/O from the same adapter to both a storage subsystem and a tape device. The default is enabled.
PAGE 319
9–Offline Utilities Fast!UTIL Table 9-2. Selectable Boot Settings Window Parameters Parameter Selectable Boot Description Enables or disables specified boot devices.  If Selectable Boot is disabled, BIOS configures the first disk drive (LUN) it finds as the boot device.  If Selectable Boot is enabled and the Boot Port Name Lun parameter is unspecified, BIOS configures the first LUN 0 disk drive that it finds as the boot device.
PAGE 320
9–Offline Utilities Fast!UTIL NOTE: On some servers, the BIOS code supports selectable startup that overrides the Fast!UTIL selectable boot setting. In such cases, consult the server product documentation for information about configuring the boot device using the server’s Configuration/Setup Utility menu. Restore Default Settings The Restore Default Settings option restores the default adapter and NVRAM settings.
PAGE 321
9–Offline Utilities Fast!UTIL Table 9-3. Advanced Settings Window Parameters Parameter Description Execution Throttle The maximum number of commands that can run on one port. When the number of commands executing on a port reaches the execution throttle value, no new commands can be initiated until the current command finishes. This parameter can be 1–65,535. The default is 65,535. LUNs per Target The maximum number of LUNs per Fibre Channel port or FCoE target device.
PAGE 322
9–Offline Utilities Fast!UTIL Table 9-3. Advanced Settings Window Parameters (Continued) Parameter Description EV Controller Order Enables or disables loading the adapter BIOS if the Converged Network Adapter is selected as the first controller in the system BIOS\boot controller order. If this parameter is disabled, the adapter BIOS loads in any CMOS location, allowing the system to boot from a Fibre Channel drive (boot LUN), even after other devices, such as a 3.5-inch disk or CD-ROM drive.
PAGE 323
9–Offline Utilities Fast!UTIL Fibre Disk Utility CAUTION! Low-level formatting permanently removes all data on the disk. The Fibre Disk Utility option opens the Disk Utility Options window (Figure 9-8). This window displays information for all devices on the Fibre Channel loop and provides options to perform disk maintenance functions. The disk maintenance functions include low-level formatting, media verification, and data verification. You can also select a different disk. Figure 9-8.
PAGE 324
9–Offline Utilities EFICFG Exit Fast!UTIL The Exit Fast!UTIL option closes the Fast!UTIL utility. When prompted, choose to save the changes and restart the server to put configuration changes into effect. EFICFG The QLogic EFI Driver Configuration protocol displays and modifies configuration parameters stored in the adapter NVRAM. The QLogic EFI Driver Diagnostic protocol provides a minimal set of adapter diagnostics.
PAGE 325
9–Offline Utilities FlasUTIL The Driver Configuration Main Menu will be displayed. Do not redirect the output of the Driver Configuration protocol. Redirecting console output may cause failures. For a more detailed description of the EFI commands used in this procedure, refer to the EFI shell documentation provided with your computer or the EFI project documentation at http://www.intel.com/technology/efi/index.htm.
PAGE 326
9–Offline Utilities FlasUTIL 4. Boot the server with the QLogic 8100 Series Adapter using the disk or USB removable drive. 5. Change to the directory containing the multi-boot image on the disk or USB removable drive. Using FlasUTIL The FlasUTIL utility has a command line interface and a menu interface. The menu interface is function specific, and is not described in this guide.
PAGE 327
9–Offline Utilities FlasUTIL Table 9-4. FlasUTIL Command Line Options (Continued) Option Function /Q Quiet mode suppresses all messages on the display. /S xxxx Display the serial number of the adapter at address xxxx. If you omit the address, the command displays the serial numbers of all adapters. /V xxxx Display the current BIOS version of the adapter at address xxxx. If you omit the address, the command displays the BIOS version for all adapters.
PAGE 328
9–Offline Utilities EFIUTIL NOTE: Each multi-boot image version has its own update.bat file. Do not attempt to update a multi-boot image with an update.bat file from a different multi-boot image version. The script updates the multi-boot images for all the QLogic adapters with corresponding multi-boot image versions, as shown in Figure 9-9. Figure 9-9. FlasUTIL FW Upgrade In Progress 4. When the installation is complete, reboot the system.
PAGE 329
9–Offline Utilities EFIUTIL The utility can run in batch mode or in interactive mode (CLI mode). The mode of operation is determined by the number command line parameters used to start efiutil.
PAGE 330
9–Offline Utilities EFIUTIL 9-18 FE0254601-00 A
PAGE 331
A Adapter Port LEDs Figure A-1 shows the QLogic 8100 Series Adapter Storage Traffic and Link/Ethernet Traffic port LEDs. Each port has its own LEDs.  The Storage Traffic LED indicates the state of data traffic exchanged with the SAN.  The Link/Ethernet Traffic LED indicates the state of data traffic exchanged with the LAN. Observe the LED states, and refer to Table A-1 for indications of firmware or hardware conditions. Storage Traffic Link/Ethernet Traffic LED Figure A-1.
PAGE 332
A–Adapter Port LEDs Table A-1.
PAGE 333
B Cisco Nexus 5000 Series Switch Configuration This appendix describes how to use the switch CLI to configure the Cisco Nexus FCoE switch port as a virtual Fibre Channel port. This configuration enables communication between the Fibre Channel and FCoE devices attached to the switch. Configuring the Cisco Nexus FCoE switch involves the following steps: 1. Enable the FCoE function on the switch. 2. Create and configure the VLAN. 3. Configure the physical Ethernet interface switch port. 4.
PAGE 334
B–Cisco Nexus 5000 Series Switch Configuration Enable FCoE on the Switch Enable FCoE on the Switch To enable the FCoE function on the switch: 1. Determine whether the FCoE function is enabled on the switch by issuing the show feature command. In the following example, the FCoE function is disabled.
PAGE 335
B–Cisco Nexus 5000 Series Switch Configuration Create and Configure the VLAN 3. Save the current configuration to the switch nonvolatile memory, and then exit configuration mode by issuing the following commands: (config)# copy running-config startup-config (config)# exit 4. Reboot the switch by issuing the following command: # reload The switch may take several minutes to reboot. 5. When the reboot is complete, log in to the switch as the administrator. 6.
PAGE 336
B–Cisco Nexus 5000 Series Switch Configuration Create and Configure a Virtual Fibre Channel Interface 2. Enable LLDP on the Ethernet interface by issuing the following commands: (config-if)# lldp transmit (config-if)# lldp receive 3. Set the PFC mode for the interface by issuing the following command: (config-if)# priority-flow-control mode auto 4. Configure the switch port as a trunk port by issuing the following command: (config-if)# switchport mode trunk 5.
PAGE 337
B–Cisco Nexus 5000 Series Switch Configuration Verify that the Adapter Is Logged into the Switch Verify that the Adapter Is Logged into the Switch To verify that the switch has been properly configured and that the adapter has logged into the switch: 1. List the devices that have logged into the switch, and compare the device WWN with the information from the QLogic adapter port by entering the show flogi database command.
PAGE 338
B–Cisco Nexus 5000 Series Switch Configuration Verify that the Adapter Is Logged into the Switch B-6 FE0254601-00 A
PAGE 339
C Brocade CEE/FCoE Switch/Blade Configuration This appendix describes how to use the switch CLI to configure the Brocade FCoE switch port as a virtual Fibre Channel port. This configuration enables communication between the Fibre Channel and FCoE devices attached to the switch. Configuring the Brocade FCoE switch involves the following steps: 1. Enable the Ethernet Switch Service (optional for Brocade 8000 series FCoE switch) 2. Create and configure the FCoE VLAN. 3. Create and configure the CEE-MAP.
PAGE 340
C–Brocade CEE/FCoE Switch/Blade Configuration Enable the Ethernet Switch Service Enable the Ethernet Switch Service CAUTION! To complete the configuration described in this section, the Brocade FCoE blade must be power cycled. If you have a Brocade 8000 Series FCoE switch, the Ethernet switch service is enabled by default—proceed to “Create and Configure FCoE VLAN” on page C-3. To enable the Ethernet switch service on the Brocade FCoE 10-24 blade for Brocade DCX and DCX-4S backbone switches: 1.
PAGE 341
C–Brocade CEE/FCoE Switch/Blade Configuration Create and Configure FCoE VLAN Create and Configure FCoE VLAN To create and configure the FCoE VLAN: 1. Enter the CEE management shell, and move to the global configuration mode by issuing the following commands: admin> cmsh # configure terminal admin> cmsh # configure terminal Enter configuration commands, one per line. End with CNTL/Z. (config)# 2.
PAGE 342
C–Brocade CEE/FCoE Switch/Blade Configuration Create and Configure CEE-MAP 6. Create VLAN rules by issuing the following commands: swd77(config)# vlan classifier rule 1 proto fcoe encap ethv2 swd77(config)# vlan classifier rule 2 proto fip encap ethv2 7.
PAGE 343
C–Brocade CEE/FCoE Switch/Blade Configuration Configure LLDP/DCBX for FCoE 6. Verify the CEE-MAP configuration by issuing the following command: (config)# do show cee maps CEE Map demo Precedence 1 Priority Group Table 1: Weight 50, PFC Enabled, TrafficClass 3, BW% 40 2: Weight 50, PFC Disabled, TrafficClass 6, BW% 60 15.0: PFC Disabled 15.1: PFC Disabled 15.2: PFC Disabled 15.3: PFC Disabled 15.4: PFC Disabled 15.5: PFC Disabled 15.6: PFC Disabled 15.
PAGE 344
C–Brocade CEE/FCoE Switch/Blade Configuration Configure CEE Port 4. Verify the LLDP/DCBX configuration (Transmit TLVs) by issuing the following command: (config)# do show lldp LLDP Global Information system-name: swd77 system-description: Fibre Channel Switch.
PAGE 345
C–Brocade CEE/FCoE Switch/Blade Configuration Verify that the Adapter is Logged into the Switch Verify that the Adapter is Logged into the Switch To verify that the switch has been properly configured and that the adapter has logged into the switch: 1. List the devices that have logged into the switch by issuing the do fos fcoe command, and compare the device MAC/WWN with the information from the QLogic adapter port.
PAGE 346
C–Brocade CEE/FCoE Switch/Blade Configuration Verify that the Adapter is Logged into the Switch C-8 FE0254601-00 A
PAGE 347
PAGE 348
Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan ©2011 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic, the QLogic logo, and QConvergeConsole are registered trademarks of QLogic Corporation.