User’s Guide Converged Network Adapter 8200 and 3200 Series SN0054671-00 A
User’s Guide—Converged Network Adapter 8200 and 3200 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.
Table of Contents Preface What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters Functionality and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Adapter Specifications . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters Updating the Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the vCenter Plug-in on a Tomcat Server . . . . . . . . . . . . . . . . . . Installing Tomcat on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping Tomcat on Linux . . . . . . . . . . . . . . . . . . . Installing Tomcat on Windows . . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters Teaming/Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Team MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teaming Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the CLI for Teaming . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters Deploying the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Driver System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Installing iSCSI in ESX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 ESX OS Support . . . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters 4 Configuring FCoE Installing FCoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing FCoE in Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Features . . . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters Configuring FCoE Driver Parameters with the Non-Interactive QCC CLI Configuring FCoE Driver Parameters with the vCenter Plugin . . . . . . Selective LUNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Selective LUNS with the QCC GUI . . . . . . . . . . . . . . . . . Configuring Selective LUNS with the Interactive QCC CLI . . . . . . . . .
User’s Guide—Converged Network Adapter 8200 and 3200 Series Adapters 2-23 2-24 2-25 2-26 3-1 4-1 QLogic Adapter vCenter Plug-in with QoS Interface, Function eSwitch Configuration, and eSwitch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostics Tests on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIC Troubleshooting Diagram 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This guide provides detailed instructions on the installation, configuration, and troubleshooting of 8200 and 3200 Series Adapters 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.
Preface Intended Audience Intended Audience This guide is intended for those responsible for deploying QLogic Fibre Channel and Converged Network Adapters on Windows, Linux, and VMware: users ranging from end users, such as data center managers and system administrators, to the test and development community.
Preface License Agreements Key names and key strokes are indicated with UPPERCASE: Press the CTRL+P keys. Press the UP ARROW key. Text in italics indicates terms, emphasis, variables, or document titles. For example: For a complete listing of license agreements, refer to the QLogic Software End User License Agreement. What are shortcut keys? To enter the date type mm/dd/yyyy (where mm is the month, dd is the day, and yyyy is the year).
Preface Technical Support Training QLogic offers training for technical professionals for all iSCSI, Converged Network, InfiniBand, and Fibre Channel products. From the main QLogic web page at www.qlogic.com, click the Support tab at the top, then click Training and Certification on the left. The QLogic Global Training Portal offers online courses, certification exams, and scheduling of in-person training.
Preface Legal Notices Legal Notices Warranty For warranty details, please check the QLogic Web site at http://www.qlogic.com/Support/Pages/Warranty.aspx. Laser Safety FDA Notice This product complies with DHHS Rules 21CFR Chapter I, Subchapter J. This product has been designed and manufactured according to IEC60825-1 on the safety label of laser product.
Preface Legal Notices CE Mark 2004/108/EC EMC Directive compliance: EN55022:2006+A1:2007/CISPR22:2006: Class A (QLE8xxx) EN55024:1998 EN61000-3-2: Harmonic Current Emission EN61000-3-3: Voltage Fluctuation and Flicker Immunity Standards EN61000-4-2: ESD EN61000-4-3: RF Electro Magnetic Field EN61000-4-4: Fast Transient/Burst EN61000-4-5: Fast Surge Common/ Differential EN61000-4-6: RF Conducted Susceptibility EN61000-4-8: Power Frequency Magnetic Field EN61000-4-11: Voltage Dips and Interrupt VCCI: 2009-0
Preface Legal Notices Korean Language Format— Class A Product Safety Compliance UL, cUL product safety: 8200 and 3200 Series Adapters UL60950-1 (2nd Edition), 2007-03-3-27 UL CSA C22.2 60950-1-07 (2nd Edition) Use only with listed ITE or equivalent. Complies with 21 CFR 1040.10 and 1040.11.
Preface Legal Notices xviii SN0054671-00 A
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™ CAUTION! Keep the adapter in the antistatic bag until installation. The adapter contains parts that can be damaged by electrostatic discharge (ESD).
Quick Start Step 2. Install the Adapter Hardware Step 2. Install the Adapter Hardware To install the adapter hardware, you need to open the computer and locate the appropriate bus slot. If necessary, consult your computer system manual for instructions on how to remove the computer cover. Follow these steps to install the adapter hardware: 1. Power off the computer and all attached devices such as monitors, printers, and external components. 2. Disconnect the power cable. 3.
Quick Start Step 3. Install the Adapter Drivers 9. 10. Plug the appropriate Ethernet cable (either copper or optical) into the adapter. Optical models ship with optical transceivers already installed. The 8200 and 3200 Series Adapters will only operate with optical transceivers sold by QLogic. For copper connectivity, see the list of approved SFP+ direct-attach copper cables on QLogic's Web site: http://www.qlogic.com/Resources/Documents/LineCards/Copper_Cabl es_Support_Matrix_Line_Card.
Quick Start Step 4. Install QConvergeConsole™ Step 4. Install QConvergeConsole™ To install QConvergeConsole: 1. Go to the QLogic Driver Downloads/Documentation page at http://driverdownloads.qlogic.com. 2. Locate the QConvergeConsole package for the adapter product, as follows: 8200 Series Adapters: Click QLogic Products. Select Converged Network Adapters, the appropriate adapter model, and your operating system. Click Go. The product download page opens.
1 Product Overview 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. A Converged Network Adapter provides simultaneous Fibre Channel and Ethernet traffic over a shared 10Gb Ethernet link.
1–Product Overview Functionality and Features Preboot-eXecution environment (PXE) iSCSI (8200 Series Adapters only) Fibre Channel (8200 Series Adapters only) Unified extensible firmware interface (UEFI) PCIe 2.
1–Product Overview Adapter Specifications Flow control Locally Administered Address (LAA) Enhanced optimization with MSI, MSI-X, and NetQueue Supported Operating Systems The 8200 and 3200 Series adapters support commonly used operating systems: Windows, Linux, Solaris® and ESX®. For a detailed list of the currently supported operating systems, refer to the adapter’s Readme and Release Notes on the QLogic Web site: http://driverdownloads.qlogic.
1–Product Overview Adapter Specifications Environmental Specifications Table 1-1. Environmental Specifications Condition Operating Non-Operating Temperature Ranges (for Altitude=900 m or 2952.75 ft) 10°C to 55°C a –40°C to 65°C (50°F to 131°F) (–40°C to 149°F) 10°C to n°C b –40°C to 65°C (50°F to n°F ) (–40°F to 149°F) Temperature Gradient Maximum per 60 Min.
1–Product Overview Converged Network Adapter SuperInstaller Installation Converged Network Adapter SuperInstaller Installation QLogic Windows SuperInstaller Refer to the QLogic Windows SuperInstaller Readme file for information. QLogic Linux SuperInstaller Refer to the QLogic Linux SuperInstaller Readme file for information.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility Converged Network Adapter Function Configuration Package Contents The following files are included for updating the adapter multi-boot code: update.bat—DOS batch file that calls the executable files to update the adapter multi-boot. QLflash.exe—Utility to update multi-boot code and firmware. DOS4GW.exe—This file is required to use the QLflash.exe. p3pyyyyy.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility QLflash Command Line Options The executable file QLflash.exe is used by the UPDATE.BAT file to update your adapter multiboot-code. The application QLflash.exe may be used to read, write, or verify either the multi-boot image or the NVRAM on the adapter. The following paragraphs describe the command line options available with this utility.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility NOTE: If you used an FC RAID target in a cluster environment, you should enable the Enable Target Reset = Enabled (Advanced Adapter Settings). Use the /I option if the update utility, QLflash, does not detect your adapter. QLogic recommends disabling the internal disk before installing the OS or booting to the FCoE disk.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility Function The Function parameter applies only to only function 0 and function 1. Press the ENTER key to configure either PXE or iBFT settings. (The Function option is predicated on the Protocol that is selected.) Adapter Settings Press the ENTER key on the Function number to access Adapter Settings, and to configure PXE Boot or iBFT. PXE.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility Initiator Settings Enable DHCP (Enabled/Disabled: Default—Enabled) When Enable DHCP is set to Enabled, the adapter utilizes DHCP to obtain its IP address, subnet mask, and gateway IP address. Target Param From DHCP (Enabled/Disabled: Default—Enabled) When Target Param From DHCP is set to Enabled, the adapter uses DHCP to obtain the target IP address, subnet mask, and gateway IP address.
1–Product Overview Multi-boot Image for 10Gb CNA—CNA Function Configuration Utility Boot LUN Enter to specify the LUN of the boot device. (Depending on your configuration, it may not be necessary to change this option.) CHAP Type None—CHAP is not used. One-Way—Unidirectional CHAP is used. Mutual—Bidirectional CHAP is used. Target CHAP Name Enter to specify the target CHAP name. Target CHAP Secret Enter to specify the target CHAP secret.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Exit the CNA Function Configuration Utility Press the ENTER key to select from the following: Reboot System Return to Fast!UTIL Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi This section on installing the QLogic Adapter vCenter Plug-in contains the following: 1-12 Introduction Requirements Installing the QLogic Adapter CIM Provider Starting the QLogic Adapter CIM Provider Removing the
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Introduction The QLogic Adapter vCenter Plug-in is a user-interface extension to the vSphere™ Client that allows you to manage and configure QLogic adapters, including the NIC partitioning feature, on ESX and ESXi servers. When the you select an ESX or ESXi host that has QLogic adapters installed, the extension appears in the client as an additional tab named QLogic Adapter, as shown in Figure 1-1. Figure 1-1.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Requirements The QLogic Adapter vCenter Plug-in requires the components in Figure 1-2 to be installed and running. Figure 1-2. vCenter Plug-in Requirements QLogic provides the following components that must be installed on the ESX or ESXi Server, vCenter Server, and Tomcat Web Server. ESX/ESXi Server QLogic adapters with firmware and driver.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi vCenter Server QLogic XML configuration file to register the plug-in to the vCenter Server Tomcat Web Server QLogic Web-based extension to the vSphere Client Installing the QLogic Adapter CIM Provider The QLogic Adapter CIM Provider for VMware ESX was generated as a vSphere Installation Bundle (VIB) file. A VIB contains the complete set of files and binaries required to install the provider on VMware ESX/ESXi.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 3. Issue the vihostupdate command to install the offline bundle as follows: # vihostupdate.pl --install --bundle offline-bundle.zip --nosigcheck For available options, refer to the vihostupdate page. 4. Follow the on-screen instructions to complete the installation. You may need to reboot the ESXi system.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Removing the QLogic Adapter CIM Provider To remove the QLogic Adapter CIM Provider, use either the esxupdate or vihostupdate command. To uninstall the QLogic Adapter CIM Provider using the esxupdate command: 1. Query and find the existing VIB you are updating as follows: # esxupdate query --vib-view | grep qlogic For example, the VIB ID may have a format similar to the following: ESX/ESXi 4.0: cross_qlogic-nic-provider_400.x.x.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi NOTE: For more details on vihostupdate, refer to the documents on the VMware vSphere Command-Line Interface Documentation page, located here: http://www.vmware.com/support/developer/vcli/ Starting the QLogic Adapter vCenter Plug-in To start the QLogic Adapter vCenter Plug-in: 1. Start the VMware vSphere Client and connect to the vCenter Server by entering the IP address or name, user name, and password. 2. Click Login. 3.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Installing the Flash Utility For ESX, before you perform a Flash update on QLogic Adapters using the QLogic Adapter vCenter Plug-in, ensure that the QLflash utility is also installed on the ESX system. To install the QLflash utility on ESX: 1. Unzip the esx_qlflash.zip file, which contains the qlflash userworld executable. 2. Copy the QLflash binary file to the /usr/lib/vmware/bin/ directory. 3.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 7. When asked “Do you want to reset the adapter to activate the firmware immediately after successful update?,” click OK if you want the new firmware to take effect immediately. Or, click Cancel to have the new firmware take effect after the next system reboot. 8. Wait for the Flash update process to complete. Processing time depends on the network connection and the system configuration. Do not interrupt the update process.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Installing Tomcat on Linux To install Tomcat on a Linux OS: 1. Go to the following URL: http://tomcat.apache.org/download-55.cgi 2. Locate the following directory and file: Binary Distribution > Core > tar.gz (apache-tomcat-5.5.28.tar.gz) 3. Unzip the tar.gz file by issuing the following command: root # tar zxf file.tar.gz 4.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Starting and Stopping Tomcat on Windows To start and stop Tomcat on a Windows OS: 1. Go to Computer Management > Services and Application > Services > Apache Tomcat . 2. Right-click, and then select Start /Stop to initiate Tomcat service, or select Stop to halt the Tomcat service. Installing the vCenter Plug-in on Tomcat 1.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi For Perl: http://communities.vmware.com/docs/DOC-4530 1. Before you can use the script, download the appropriate VI SDK from VMware. For PowerShell, download vSphere PowerCLI: http://communities.vmware.com/community/vmtn/vsphere/automationtools/ powercli For Perl VI SDK, download vSphere SDK for Perl: http://www.vmware.com/support/developer/viperltoolkit/ 2.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 1-24 SN0054671-00 A
2 Configuring NIC This section describes the driver and QConvergeConsole (QCC) agent installation, configuration, operation, and troubleshooting of the NIC function of the 8200 and 3200 Series Adapters. Refer to the QCC User’s Guide for information on QCC Agents. Installing NIC in Linux Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Inbox Driver Update for Linux Readme file for information.
2–Configuring NIC Installing NIC in Windows Packaging Content Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Inbox Driver Update for ESX Readme file for information. ESX OS Support Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Inbox Driver Update for ESX Readme file for information.
2–Configuring NIC Configuring PXE Boot Configuring PXE Boot This section provides procedures for configuring the 8200 and 3200 Series Adapters to perform PXE boot. The example uses function 1 and NIC 1. To configure PXE boot: 1. Enter the system BIOS by pressing the F2 key. 2. On the BIOS window (Figure 2-1), select Integrated Devices, and then press the ENTER key. Figure 2-1. Dell BIOS: Integrated Devices 3. Set the Embedded NIC1 and NIC2 option to Enabled. 4.
2–Configuring NIC Configuring PXE Boot 7. On the CNA Function Configuration main window, ensure that Protocol is set to PXE (Figure 2-2). Figure 2-2. QLogic 8200 CNA Function Configuration 2-4 8. Press the ESC key to exit. 9. Select Save changes to save your edits, exit, and reboot the system. 10. During POST, press the F2 key to enter the BIOS system.
2–Configuring NIC Configuring PXE Boot 11. Select Boot Settings, and then press the ENTER key (Figure 2-3). Figure 2-3. BIOS: Boot Settings 12. SN0054671-00 A Select the Boot Sequence option, and then press the ENTER key.
2–Configuring NIC Configuring Driver Software Parameters 13. Select the Embedded NIC 1 QLogic PXE... entry, and then press the UP ARROW key to move this entry to the first position (Figure 2-4). Figure 2-4. Embedded NIC 1 QLogic PXE 14. Press the ESCAPE key, and then select Save changes and exit. The system reboots. 15. After the system reboot, follow the screen prompt for PXE boot server for the installation of OS of your choice.
2–Configuring NIC Configuring Driver Software Parameters qaucli Utility Install QConvergeConsole CLI (qaucli) from the following packages supplied by QLogic: QConvergeConsoleCLI-_linux_.install.tar.gz— Package file QConvergeConsoleCLI-_.
2–Configuring NIC Configuring Driver Software Parameters Sample Output 1: ethtool -S eth8 NIC statistics: xmit_called: 6 xmit_finished: 6 rx_dropped: 0 tx_dropped: 0 csummed: 0 rx_pkts: 0 lro_pkts: 0 rx_bytes: 0 tx_bytes: 468 lrobytes: 0 lso_frames: 0 xmit_on: 0 xmit_off: 0 skb_alloc_failure: 0 null skb: 0 null rxbuf: 0 rx dma map error: 0 In the following example, ethtool eth[n] lists interface settings.
2–Configuring NIC Windows Property Pages phantomcore Utility Use the phantomcore utility to collect a firmware dump that is useful for forwarding to QLogic Technical Support. To collect a firmware dump: 1. To turn off auto recovery in the driver, issue the following command: insmod qlcnic.ko auto_fw_reset=0 2. To collect the firmware dump, issue the following command: phantomcore -i The utility generates a core file that contains the firmware dump.
2–Configuring NIC Windows Property Pages Table 2-1. Windows Driver Configurable Parameters Property Completion Queue Size Description Specifies the size for the ring where command completion and incoming receive indication status will be posted. Registry Key: CompletionQueueSize Default: 16384 Values: 1024, 2048, 4096, 8192, 16384, 32768 Flow Control Sets the hardware flow control parameters. Registry Key: *FlowControl Default: Rx and Tx Enabled.
2–Configuring NIC Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Large Send Offload V1 IP4 Description Enables and disables TCP large send offload. Allows host TCP stack to give bigger than maximum segment size (MSS) packets to the driver, and then with the help of hardware, splits the larger segments into MTU size packets before sending on wire. Registry Key: *LsoV1IPv4 Default: Enabled.
2–Configuring NIC Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Max Ethernet Frame Size Description Specifies the Ethernet frame size for packet transmission and receive (includes the MAC header). Reg Key: MaxFrameSize Default: 1514 (corresponds to 1514 bytes on the wire + 4 bytes of CRC) Max: 9614 Min: 142 (Windows 2003), 590 (Windows 2008) Max Jumbo Buffers Specifies the number of jumbo-sized receive buffers allocated for the jumbo ring (not frame).
2–Configuring NIC Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Receive Side Scaling Rings Description Specifies the number of RSS rings used. Registry Key: MaxStatusRings Default: 2 Values: 1-4 TCP Checksum Offload IPv4 Enables and disables TCP transmit and receive checksum offload.
2–Configuring NIC VLAN Configuration Configuring NIC Driver Parameters with QCC GUI Refer to the QConvergeConsole Help System: Setting General NIC Port Parameters and Setting Advanced NIC Port Parameters for information. Configuring NIC Driver Parameters with QCC Interactive CLI Refer to the QConvergeConsole CLI User's Guide: section 7, “NIC Interactive Commands,” for information.
2–Configuring NIC Teaming/Bonding Team MAC Address At initialization, the teaming driver selects the team’s MAC address to be the MAC of one of the teamed adapters. In general, the first adapter to come up is chosen to be the preferred primary adapter. The preferred primary’s MAC address is assigned to the MAC address of the team. Alternately, you can choose any valid MAC address as the team’s static MAC address, also called the locally administered address (LAA).
2–Configuring NIC Teaming/Bonding Table 2-2. Windows Teaming Modes (Continued) Mode Failover Capability Switch Dependency System Fault Tolerance (SFT) Load Balancing Number of Ports per Team (Range a) Yes Yes Yes Yes 2–16 Dynamic 802.3ad a 16×16 ports can be aggregated per system: 16 ports per team and 16 teams per system. Failsafe Mode The failsafe mode provides Layer 2 fault tolerance. Failsafe provides high reliability through redundancy in the event of port failure.
2–Configuring NIC Teaming/Bonding Switch-Independent Load Balancing Mode Switch-independent load balancing mode provides a failsafe feature and supports transmit load balancing. For receive load balancing, use the 802.3ad modes. In this mode, the outbound traffic is efficiently distributed across the member adapters to increase the transmit bandwidth. Traffic load balancing is connection-based to avoid out-of-order packet delivery.
2–Configuring NIC Teaming/Bonding Static Link Aggregation (SLA) Static link aggregation (SLA, 802.3ad static protocols with generic trunking) is a switch-assisted teaming mode, where the switch must be 802.3ad compliant. The switch ports must be configured so that the switch perceives adapters from a LAG as a single, virtual adapter. In SLA, the ports on the switch are active by default. There is no negotiation between the switch and the teaming driver to decide on adapters participating in a LAG.
2–Configuring NIC Teaming/Bonding Using the CLI for Teaming You can view, create, configure, and delete teams using the QConvergeConsole utility.
2–Configuring NIC Teaming/Bonding 3. Click the Team Management tab to bring that page to the front (Figure 2-5) and perform teaming-related management. Figure 2-5.
2–Configuring NIC Teaming/Bonding Information on teaming configuration includes the following: Creating a Team Modifying a Team Deleting a Team Saving and Restoring Teaming Configuration Creating a Team To create a team: 1. To create a team, right-click the Teams folder icon, and then click Create Team (Figure 2-6). Figure 2-6. Creating a Team 2. SN0054671-00 A The software automatically picks a unique team name, or you may choose to enter your own team name.
2–Configuring NIC Teaming/Bonding 3. 2-22 On the Create Team dialog box, specify the following (see the message pane at the bottom of the dialog box for more details), and then click OK to return to the adapter properties: Name—Type a name for the new team. Type—Select the teaming mode by clicking either Failsafe Team, 802.3ad Static Team, 802.3ad Dynamic Team, or Switch Independent Load Balancing. If you select the 802.
2–Configuring NIC Teaming/Bonding The following figures show the configuration of various teaming modes. Figure 2-7.
2–Configuring NIC Teaming/Bonding Figure 2-8.
2–Configuring NIC Teaming/Bonding Figure 2-9. Creating an 802.
2–Configuring NIC Teaming/Bonding Figure 2-10. Creating an 802.
2–Configuring NIC Teaming/Bonding To confirm if a team has been successfully created, view the Team and Adapters pane on the Team Management page. Figure 2-11 shows an example of a newly-formed team. The Team Data pane on the right shows the properties, information, and status of the team or adapter that is currently selected in the Teams and Adapters pane on the left. Figure 2-11.
2–Configuring NIC Teaming/Bonding To add team members: 1. On the Team Management property page, right-click the unteamed adapter to add to a team. 2. On the shortcut menu, point to Add to Team, and then click the team to which you want to add the adapter (Figure 2-12). NOTE: You cannot add an adapter to a team that is already a member of another team. Teaming of teams is not supported. Figure 2-12.
2–Configuring NIC Teaming/Bonding To remove an adapter from a team: NOTE: A team must include at least one QLogic adapter. A QLogic adapter is allowed to be deleted from a team only if it is not the last QLogic teamed adapter. 1. On the Team Management property page, right-click the adapter to be removed from the team. 2. On the shortcut menu, click Remove from Team. 3. At least two adapters must be present in a team.
2–Configuring NIC Teaming/Bonding The team properties change takes effect immediately. Changing team properties causes the driver to reload, which could result in a momentary loss of connectivity. NOTE: To ensure that the properties of all teamed adapters and adapters with VLANs remain synchronized with the team properties, do not directly modify the adapter properties on the Advanced page.
2–Configuring NIC Teaming/Bonding To modify team composition: 1. On the Team Management page, in the left pane under Teams and Adapters, right-click the team name whose properties are to be changed. 2. On the shortcut menu, click Modify Team (Figure 2-14). Figure 2-14. Modifying Team Properties 3. In the Modify Team Properties dialog box, change the team parameters as needed, and then click OK.
2–Configuring NIC Teaming/Bonding Example 1: For a failsafe team, you can change the team name, assigned team static MAC address, preferred primary adapter, and failback type (Figure 2-15). Figure 2-15.
2–Configuring NIC Teaming/Bonding Example 2: You can change the team type and the corresponding team attributes. For example, you can change from failsafe to switch-independent load balancing, or from 802.3ad static team to 802.3ad dynamic team. Figure 2-16 shows a failsafe team modification, which shows the new team type and default values for team attributes. You can manually change attribute values. Figure 2-16. Modifying the Team Type Deleting a Team To delete a team: 1.
2–Configuring NIC Teaming/Bonding Saving and Restoring Teaming Configuration QLogic recommends that you periodically save the configuration to prevent any accidental loss of network topology and settings. Current configuration including the teams, VLANs, and properties can be saved to a file. Restoring an earlier configuration results in the destruction of the current configuration. To save a configuration: 1. On the Team Management page under Teams and Adapters, right-click the Teams folder. 2.
2–Configuring NIC NIC Partition (NPAR) NIC Partition (NPAR) The NPAR feature in QLogic adapters provides the ability to create multiple PCIe physical functions for each physical 10GbE port on the adapter. Each of the PCIe functions appears as an independent interface to the host operating system or hypervisor. Dual-port, 10Gb adapters configured as Ethernet-only adapters contain eight Ethernet functions.
2–Configuring NIC NIC Partition (NPAR) After you have configured NPAR mode, you can modify the minimum and maximum bandwidth per NPAR. The changes take effect immediately; no reboot is required. The minimum and maximum bandwidths are specified as percentages of the link bandwidth, where: Minimum bandwidth is the minimum guaranteed bandwidth to a partition. Maximum bandwidth is the maximum value that a partition is permitted to use.
2–Configuring NIC NIC Partition (NPAR) NOTE: The 8200 and 3200 Series Adapters have eSwitches. Because all of the interfaces are assigned to the hypervisor, eSwitch operation is transparent, and the system administrator is not required to perform any additional configuration. Configuring NPAR in the BIOS Refer to the Type section for information. Configuring NPAR in QCC GUI Refer to the QConvergeConsole Help System: Partitioning NIC Ports for information.
2–Configuring NIC NIC Partition (NPAR) Figure 2-17 shows the default view of QLogic Adapter tab in the vCenter Plug-in. Figure 2-17. vCenter Plug-in QLogic Adapter Tab Default View Figures 2-18 shows the configuration range of the 8200 Series Adapters without NPAR. Figure 2-18.
2–Configuring NIC NIC Partition (NPAR) Figures 2-19 shows the configuration range of the 8200 Series Adapters with NPAR. Figure 2-19. 8200 Series Configuration Range With NPAR Figures 2-20 shows the Configuration Range of the 3200 Series Adapters with NPAR. Physical functions 2–7 can be independently disabled. Figure 2-20. 3200 Series Configuration Range With NPAR To configure a physical function: 1. Select the function you want to change in the hierarchy on the left side of the screen.
2–Configuring NIC NIC Partition (NPAR) In the example in Figure 2-21, function 2 is disabled. To enable the function, NIC is selected from the Function Type menu. Figure 2-21. Enabling a Physical Function 2-40 3. Click Save Configuration. 4. Reboot your system for the change to take effect. 5. Open vCenter Plug-in. 6. Click the QLogic Adapter tab. 7. Right-click the adapter icon on the left side of the page, and then select Refresh.
2–Configuring NIC NIC Partition (NPAR) The selected function now reflects the change made in Step 2. For example, the change made in Figure 2-21 is reflected in Figure 2-22 (function 2 changed from Disabled to NIC. Figure 2-22. Port One Configured with NPAR Enabled NPAR Personality Changes Changing a function's personality requires the ESX Host to be rebooted for the change to take effect. Each personality configuration change must be saved using the Save Configuration button.
2–Configuring NIC NIC Partition (NPAR) Enabling NPAR To enable NPAR for a port in the QLogic vCenter Plug-in, do the following: 1. Select function 2 for port 0 and function 3 for port 1. 2. Click OK to accept the NPAR parameter(s) Successfully Changed! confirmation message. 3. Reboot the ESX Host. NOTE: This is the Server where the Converged Network Adapter or Intelligent Ethernet Adapter is installed. 4. Wait until the ESX Host again becomes connected in the Data Center.
2–Configuring NIC NIC Partition (NPAR) See Figure 2-23 for an illustration. Figure 2-23. QLogic Adapter vCenter Plug-in with QoS Interface, Function eSwitch Configuration, and eSwitch Statistics eSwitch The 8200 and 3200 Series adapters connect the physical ports to the physical functions on the PCIe bus through eSwitches. An eSwitch is a VLAN aware MAC lookup virtual switch implemented in the 8200 and 3200 Series Adapters.
2–Configuring NIC NIC TroubleShooting/Diagnostics NIC TroubleShooting/Diagnostics NIC Linux Diagnostics Linux Diagnostics This section covers the following information for user diagnostics for Linux NIC driver management applications: Running Linux User Diagnostics Linux Diagnostic Test Descriptions Linux Diagnostic Test Messages NOTE: The current release does not support external and internal loopback tests. Support is expected in a future release.
2–Configuring NIC NIC TroubleShooting/Diagnostics To perform a Flash test, issue the following command: qaucli -pr nic testflash [cna_port_inst] To perform a hardware test, issue the following command: qaucli -pr nic -testhw [cna_port_inst] To perform an interrupt test, issue the following command: qaucli -pr nic -testinterrupt [cna_port_inst] To perform a link test, issue the following command: qaucli -pr nic -testlink [cna_port_inst] To perform a register test, issue the following comm
2–Configuring NIC NIC TroubleShooting/Diagnostics # ethtool -t eth4 The test result is PASS The test extra info: Register_Test_on_offline 0 Link_Test_on_offline 0 Interrupt_Test_offline 0 Loopback_Test_offline 0 Linux Diagnostic Test Descriptions Internal Loopback Test performs internal packet loopback. Flash Test verifies the Flash read and write. Hardware Test verifies that the hardware is running. Interrupt Test enables and disables the interrupt and functional verification tests.
2–Configuring NIC NIC TroubleShooting/Diagnostics NOTE: Information on installing and starting the GUI version of QLogic's QConvergeConsole utility is provided in the QConvergeConsole User's Guide. All procedural information for that utility is covered in the QConvergeConsole Help System. To run user diagnostics in the GUI: 1. Access the Windows Control Panel, and then open the Device Manager. 2.
2–Configuring NIC NIC TroubleShooting/Diagnostics 4. Under Diagnostic Tests, select one or more check boxes indicating the tests you want to run: Hardware Test, Register Test, Interrupt Test, Loopback Test, and Link Test. (Windows Diagnostic Test Descriptions describes each test type.) 5. Click Run Tests. NOTE: Only one test can run at a time. Multiple tests can run sequentially.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-4. Windows QConvergeConsole CLI—Selecting a Protocol in Legacy Mode (Continued) Command Description qaucli -fc [options] Use Fibre Channel legacy command line scli [options] Use Fibre Channel legacy command line Diagnostic help commands, and command options available for each specific protocol, are available by specifying -h to the protocol, as shown in Table 2-5. Table 2-5.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-7.
2–Configuring NIC NIC TroubleShooting/Diagnostics For every test performed, the diagnostic utility shows the following data: Total number of attempts Number of successful completions Number of failures You can either perform all tests in succession, or perform only specific tests specified by the preceding command-line parameters. You can run additional diagnostics in the CLI as listed in the following table. To determine the cna_port_inst, issue the qaucli -nic –i command as shown in Table 2-8.
2–Configuring NIC NIC TroubleShooting/Diagnostics Windows Diagnostic Test Descriptions This section provides descriptions of the following Windows diagnostic tests: Hardware Test Register Test Interrupt Test Loopback Test Link Test Hardware Test The hardware test checks the status of various hardware blocks, including DMA engines, receive engine, and on-board processor meta cores. Register Test The register test performs device register read/write accesses.
2–Configuring NIC NIC TroubleShooting/Diagnostics Windows Diagnostic Test Messages If a test fails, an appropriate error code is generated and displayed, as shown in Table 2-9. Note that this table does not list error messages for the interrupt and link tests. Table 2-9.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-9.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-9.
2–Configuring NIC NIC TroubleShooting/Diagnostics QCC GUI Diagnostics Refer to the QConvergeConsole Help System: Performing NIC Port Diagnostics for information. QCC CLI Diagnostics QCC Interactive CLI Refer to the QConvergeConsole User's Guide for information. QCC CLI Diagnostics QCC Non-Interactive CLI Refer to the QConvergeConsole User's Guide, section 4, “NIC Noninteractive Commands,” for information.
2–Configuring NIC NIC TroubleShooting/Diagnostics NIC Troubleshooting Guidelines Figure 2-25.
2–Configuring NIC NIC TroubleShooting/Diagnostics Figure 2-26.
3 Configuring iSCSI iSCSI Overview This section describes the driver and agent installation, configuration, operation, and troubleshooting of the iSCSI function of the 8200 Series Converged Network Adapter. Installing iSCSI in Linux Refer to the iSCSI Adapter Inbox Driver Update for Linux Kernel 2.6.x Readme file for information. Packaging Content Refer to the iSCSI Adapter Inbox Driver Update for Linux Kernel 2.6.x Readme file for information.
3–Configuring iSCSI Installing iSCSI in ESX Installing iSCSI in ESX Refer to the iSCSI Driver for VMware ESX/ESXi 4.1 Readme file for information. Packaging Content Refer to the iSCSI Driver for VMware ESX/ESXi 4.1 Readme file for information. ESX OS Support Refer to the iSCSI Driver for VMware ESX/ESXi 4.1 Readme file for information. Using the Driver Refer to the iSCSI Driver for VMware ESX/ESXi 4.1 Readme file for information. Installing the Driver Refer to the iSCSI Driver for VMware ESX/ESXi 4.
3–Configuring iSCSI iSCSI Configuration iSCSI Configuration iSCSI Configuration with QCC GUI Refer to the QConvergeConsole Help System for information. iSCSI Configuration with Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide for information. iSCSI Configuration with Non-Interactive CLI Refer to the QConvergeConsole CLI User's Guide, “iSCSI Noninteractive Commands” section for information.
3–Configuring iSCSI iSCSI Initiator e. IP_Gateway [0.0.0.0]: Press the ENTER key to accept the default. f. Enable IPv6 [off]: Press the ENTER key to accept the default. 9. On the options menu that opens, select 3, Save changes and reset HBA (if necessary). 10. At the prompt for both ports, type Yes. 11. To return to the Converged Network Adapter (CNA) iSCSI Configuration menu, type p and press the ENTER key, and then type p and press the ENTER key again. 12.
3–Configuring iSCSI iSCSI Initiator 6. Select the Converged Network Port you want to configure. 7. Select 2, Configure IP Settings. 8. Complete the interactive list of settings as follows: a. Enable IPv4 [on]: Press the ENTER key to accept the default. b. DHCP to obtain IPv4 Network Information: [off]: Press the ENTER key to accept the default. c. IP_Address []: Type the IP address of the initiator system, and then press the ENTER key. d. IP_Subnet_Mask [255.255.255.
3–Configuring iSCSI iSCSI Name Server iSNS Configuring an iSCSI Initiator in VMware The software iSCSI initiator must be enabled for ESX/ESXi to be able to use it for accessing iSCSI storage. To configure an ESX/ESXi initiator: 1. Log in to the vSphere Client. 2. In the inventory panel, select a server to which to connect. 3. Click the Configuration tab. 4. In the Hardware panel, click Storage Adapters. 5.
3–Configuring iSCSI iSCSI Boot Accessing Fast!UTIL To access Fast!UTIL for PXE, iSCSI, and FCoE, respectively, press the CTRL+Q keys during the QLogic 8200 and 3200 Series Adapters BIOS initialization when the PXE, iSCSI, or FCoE QLogic banner displays. It may take a few seconds for the Fast!UTIL menu to appear.
3–Configuring iSCSI iSCSI Boot iBFT Boot Setup iBFT is a component of the Advanced Configuration and Power Interface Specification (ACPI) 3.0b standard that provides operating systems a standard way to boot from a software-initiated iSCSI protocol. This component utilizes software-based initiators. iSCSi Boot Setup Using QCC CLI Refer to the QConvergeConsole CLI User’s Guide for information. Configuring iSCSI Boot using the QCC CLI Refer to the QConvergeConsole CLI User’s Guide for information.
3–Configuring iSCSI iSCSI TroubleShooting iSCSI TroubleShooting iSCSI Diagnostics iSCSI Diagnostics using QCC GUI Refer to QConvergeConsole Help System: Pinging an iSCSI Port Target for information. iSCSI Diagnostics using Interactive QCC CLI Refer to the Interactive CLI User’s Guide for information.
3–Configuring iSCSI iSCSI TroubleShooting iSCSI Troubleshooting Diagram Figure 3-1.
4 Configuring FCoE This section describes the driver and agent installation, configuration, operation and troubleshooting of the FCoE function of the 8200 Series Converged Network Adapters. Installing FCoE Installing FCoE in Linux Refer to the Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update for Linux Kernel 2.6.x Readme file for information. Packaging Content Refer to the Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update for Linux Kernel 2.6.
4–Configuring FCoE Installing FCoE Firmware Installation Refer to the Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update for Linux Kernel 2.6.x Readme file for information. Installing FCoE in ESX Refer to the Fibre Channel and Fibre Channel over Ethernet (FCoE) Driver for VMware ESX/ESXi 4.0.x and 4.1 Readme file for information. Packaging Content Refer to the Fibre Channel and Fibre Channel over Ethernet (FCoE) Driver for VMware ESX/ESXi 4.0.x and 4.1 Readme file for information.
4–Configuring FCoE HBA Parameters HBA Parameters Setting HBA Parameters with the QCC GUI Refer to the QConvergeConsole Help System: Managing Fibre Channel and FCoE Adapters and Ports for information. Setting HBA Parameters with the Interactive QCC CLI Refer to the QConvergeConsole User’s Guide for information. Setting HBA Parameters with the Non-Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide, “Fibre Channel Noninteractive Commands” section for information.
4–Configuring FCoE Virtual Ports (NPIV) Configuring Boot Devices with the BIOS Refer to Using QLflash for information. Virtual Ports (NPIV) Configuring NPIV with the QCC GUI Refer to the QConvergeConsole Help System: Using Virtualization (NPIV) for information. Configuring NPIV with the Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide for information.
4–Configuring FCoE Troubleshooting Configuring Selective LUNS with the Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide for information. Configuring Selective LUNS with the Non-Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide, “Fibre Channel Noninteractive Commands” section for information. Troubleshooting FCoE Diagnostics FCoE Diagnostics using QCC GUI Refer to the QConvergeConsole Help System: Performing Diagnostics section for information.
4–Configuring FCoE Troubleshooting FCoE Troubleshooting Diagram Figure 4-1.
A Adapter LEDs The LED behavior for the 8200 and 3200 Series Adapters is defined in Table A-1. Table A-1.
A–Adapter LEDs A-2 SN0054671-00 A
Glossary adapter The board that interfaces between the host system and the target devices. Adapter is synonymous with host bus adapter, host channel adapter (HCA), host adapter, and adapter board. adapter port A port on the adapter board. adapter port beacon An LED on the adapter. Flashing it enables you to locate the adapter. alias A user-defined name for an adapter, adapter port, logical disk, or subsystem.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters device A computer subsystem, such an adapter card, which mediates data in a computer network. The term “device” is used interchangeably with “target” and “target device”. Fibre Channel High-speed serial interface technology that supports other higher layer protocols such as SCSI and IP, and is primarily used in SANs. Standardized under ANSI in 1994.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters logical unit number (LUN) A subdivision of a SCSI target. It is the small integer handle that differentiates an individual disk drive or partition (volume) within a common SCSI target device such as a disk array. Technically, a LUN can be a single physical disk drive, multiple physical disk drives, or a portion (volume) of a single physical disk drive.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters Because a path is a combination of an adapter and a target port, it is distinct from another path if it is accessed through a different adapter or it is accessing a different target port. Consequently, when switching from one path to another, the driver might be selecting a different adapter (initiator), a different target port, or both. This is important to the driver when selecting the proper method of failover notification.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters transmission control protocol/Internet protocol (TCP/IP) Basic communication language of the Internet. UEFI A specification detailing an interface that helps hand off control of the system for the pre-boot environment (that is, after the system is powered on, but before the operating system starts) to an operating system, such as Windows or Linux.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters Glossary-6 SN0054671-00 A
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 trademarks or registered trademarks of QLogic Corporation. Intel is a registered trademark of Intel Corporation.
