User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series SN0054671-00 B
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 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.
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters Moved PXE parameter from Function parameter to Protocol parameter. “Protocol” on page 1-9 Removed PXE note about LOM with PXE parameter. Removed bote and embedded LOM with the Protocol parameter. Removed references to iBFT. “Multi-boot Image for 10Gb Converged Network Adapter—CNA Function Configuration Utility” on page 1-5, “Protocol” on page 1-9, Function parameter section (removed) Changed section title (removed utility name).
User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters Removed iBFT section. from “Configuring iSCSI” on page 3-1 Removed the “Configuring FCoE Driver Parameters with vCenter Plugin” section. from “Driver Parameters” on page 4-4 Added index.
Table of Contents Preface What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Functionality and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adapter Specifications .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series 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 Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Teaming/Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Team MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teaming Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the CLI for Teaming . . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series NIC TroubleShooting/Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIC Linux Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QLogic Device Windows Property Page Diagnostics . . . . . . . . . . . . . Running Windows User Diagnostics. . . . . . . . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series iSCSI Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iSCSI Boot Setup Using Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring iSCSI Boot Settings. . . . . . . . . . . . . . . . . . . . . . . . . DHCP Boot Setup for iSCSI Boot (IPv4) . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series QLogic Adapter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting QLogic Adapter Parameters with the QCC GUI . . . . . . . . . . . Setting QLogic Adapter Parameters with the Interactive QCC CLI . . Setting QLogic Adapter Parameters with the Non-Interactive QCC CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series List of Figures Figure Page i Illustration of Server Motherboard and Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv 1-1 vSphere Client Showing QLogic Adapter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 1-2 vCenter Plug-in Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 2-1 Dell BIOS: Integrated Devices . . . . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series 2-41 2-42 2-43 2-44 2-45 2-46 2-47 2-48 2-49 3-1 4-1 Partition Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Convert to NIC from Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Configure Function for Function 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering New Bandwidth Values . . . .
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series xiv SN0054671-00 B
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, Converged Network, and Intelligent Ethernet 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 Text in Courier font indicates a file name, directory path, or command line text. For example: To return to the root directory from anywhere in the file structure: Type cd /root and press ENTER. Enter the following command: sh ./install.bin 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.
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 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-04 Class A A
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 xxii SN0054671-00 B
Quick Start Installation Instructions This Quick Start section describes how to install and configure your new QLogic converged network adapter in three simple steps: Step 1. Install the Adapter Hardware Step 2. Install the Adapter Drivers Step 3. Install QConvergeConsole® Step 4. Update the Flash 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 1. Install the Adapter Hardware 6. Grasp the adapter by the top edge and seat it firmly into the appropriate slot (see Figure i). LEVER ADAPTER SCREW ADAPTER RETAINING BRACKET PCI EXPRESS x8 (OR LARGER) SLOT REQUIRED FOR QLOGIC ADAPTERS. SLOT COVERS SYSTEM CHASSIS Figure i Illustration of Server Motherboard and Slots 7. Refasten the adapter’s retaining bracket using the existing screw or lever. 8. Close the computer cover. 9.
Quick Start Step 2. Install the Adapter Drivers Step 2. Install the Adapter Drivers To install the adapter drivers: 1. Go to the QLogic Driver Downloads/Documentation page at http://driverdownloads.qlogic.com. 2. Click QLogic Products. 3. Click Guided Search. A window opens prompting you to Enter your search criteria. 4. Provide the information necessary: a. In the Select a Product Type menu, select Adapters. b. In the Select by Model or by OS, select by Model. c.
Quick Start Step 4. Update the Flash c. In the Select the Product Technology menu, select either Converged Network Adapters or Intelligent Ethernet Adapters, as appropriate. d. In the Select the Model menu, select your QLogic Adapter. e. In the Select the Desired Item menu, select Management Tools. f. Click Search. 5. Scroll through the list that appears and select the QConvergeConsole version for your operating system. 6. Click Download Now. 7.
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, an iSCSI adapter, and an Ethernet NIC. A Converged Network Adapter provides simultaneous Fibre Channel, iSCSI, 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) 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 (OSs): Windows, Linux, Solaris®, and ESX®. For a detailed list of the currently supported operating systems, refer to the adapter’s Readme files on the QLogic Web site: http://driverdownloads.qlogic.
1–Product Overview Adapter Specifications Environmental Specifications The environmental specifications are listed in Table 1-1. 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. 10°C 20°C Humidity Percent Ranges—Noncondensing 20% to 80% (Max.
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 Converged Network Adapter—CNA Function Configuration 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 Converged Network Adapter—CNA Function Configuration QLflash Command Line Options The executable file QLflash.exe is used by the UPDATE.BAT file to update your adapter multi-boot 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 Converged Network Adapter—CNA Function Configuration 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 Converged Network Adapter—CNA Function Configuration Type Enter to set a function to a particular type: NIC—The function will support NIC protocol. None—The function will be disabled. iSCSI—The function will support iSCSI protocol. FCoE—The function will support FCoE protocol. NOTE: Functions 0 through 3 support only NIC or None. Functions 4 and 5 support NIC, iSCSI, or None. Functions 6 and 7 support NIC, FCoE, or None.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi This section on installing the QLogic Adapter vCenter Plug-in contains the following: “Introduction” on page 1-10 “Requirements” on page 1-11 “Installing the QLogic Adapter CIM Provider” on page 1-12 “Starting the QLogic Adapter CIM Provider” on page 1-13 “Removing the QLogic Adapter CIM Provider” on page 1-13 “Starting the QLogic Adapter vCenter
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.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 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. The offline-bundle.zip file contains the VIB and the necessary metadata to install the provider on VMware ESX/ESXi.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 4. Follow the on-screen instructions to complete the installation. You may need to reboot the ESXi system. 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/ Subsequent Update Installation To update the QLogic Adapter CIM Provider after a prior VIB installation: 1.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 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.x-000000 ESX/ESXi 4.1: cross_qlogic-nic-provider_410.x.x.x-000000 where x.x.x is the version number of the existing provider. 2.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 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. If the Security Warning dialog box appears, click Ignore to use the current SSL certificate.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 3. Add executable permission for QLflash by issuing the following command: # chmod +x qlflash 4. If it does not already exist, edit and append the /usr/lib/vmware/bin/qlflash entry in the /etc/vmware/UserWorldBinaries.txt file. For ESXi, the QLflash utility is not required, so no additional steps are necessary.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi CAUTION! The Flash update may take up to 10 minutes to complete. Do not cancel the task or reboot the server during this time. Doing so may corrupt the firmware on the adapter. 9. In the Flash update successful completion message box, click OK. 10. If you clicked OK in Step 7, you can click Refresh to verify the new firmware version. Otherwise, you must reboot the system for the new firmware to take effect.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 4. Create a symbolic link to a Tomcat directory by issuing the following command: # ln -s apache-tomcat-5.5.28 tomcat where setting variables include the following: export JAVA_HOME=/root/gwt/jdk1.6.0_17/ export CATALINA_HOME=/root/gwt/tomcat/ Starting and Stopping Tomcat on Linux To start Tomcat, issue the following command: # $CATALINA_HOME/bin/startup.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi Installing the vCenter Plug-in on Tomcat To install the vCenter Plus-in on a Tomcat Server: 1. Download the QLogic Adapter vCenter Plug-in installer EXE; for example, QLogic Adapter VI Plugin 1.0.4.exe. 2. Run the installer by double-clicking the EXE file or by typing the name of the EXE on a command prompt. The InstallAnywhere installer prepares to install the QLogic Adapter vCenter Plug-in. 3.
1–Product Overview Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi 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.
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 Inbox Driver Update Readme file for information.
2–Configuring NIC Installing NIC in Windows Packaging Content Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Driver for ESX/ESXi Readme file for information. ESX OS Support Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Driver for ESX/ESXi 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 B 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 QLogic Device Windows Property Pages QLogic Device Windows Property Pages To access the property pages in Windows: 1. Access the Device Manager as follows: a. On the Windows desktop, click Start, Control Panel, click Administrative Tools, and then click Computer Management. b. In the Computer Management dialog box, click Device Manager. 2. In the left pane of the Device Manager dialog box, right-click QLogic 10Gb Ethernet Adapter, and then click Properties. 3.
2–Configuring NIC QLogic Device Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Flow Control Description Sets the hardware flow control parameters. Registry Key: *FlowControl Default: Rx and Tx Enabled Values: Disabled, Rx Enabled, Tx Enabled, Rx and Tx Enabled Health Monitoring Checks health of firmware, monitors normal operation, and ensures recovery of the firmware. Interrupt Moderation Allows interrupt coalescing during receive and transmit operation.
2–Configuring NIC QLogic Device Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Large Send Offload V2 IP4 Description Enables and disables TCP large send offload. Allows the host TCP stack to give bigger than MSS packets to the driver, and then with the help of hardware, splits the larger segments into MTU size packets before sending them on the wire.
2–Configuring NIC QLogic Device Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property Max Jumbo Buffers Description Specifies the number of jumbo-sized receive buffers allocated for the jumbo ring (not frame). Reg Key: RxJumboRingSize Default: 4096 Values: 1024, 2048, 4096, 8192 Number of Receive Buffers Specifies the number of buffers allocated for receiving standard MTU size (1514 byte) packets.
2–Configuring NIC QLogic Device Windows Property Pages Table 2-1. Windows Driver Configurable Parameters (Continued) Property TCP Checksum Offload IPv4 Description Enables and disables the TCP transmit and receive checksum offload. Registry Key: *TCPChecksumOffloadIPv4 Default: Rx and Tx Enabled Values: Disabled, Rx Enabled, Tx Enabled, Rx and Tx Enabled TCP Checksum Offload IPv6 Enables and disables the TCP transmit and receive checksum offload.
2–Configuring NIC VLAN Configuration Configuring NIC Driver Parameters with QCC Interactive CLI Refer to the QConvergeConsole CLI User's Guide: section 7, “NIC Interactive Commands,” for information. Configuring NIC Driver Parameters with QCC Non-Interactive CLI Refer to the QConvergeConsole CLI User's Guide, section 4, “NIC Noninteractive 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 as 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) Static Yes Yes Yes Yes 2–16 Yes Yes Yes Yes 2–16 802.3ad 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.
2–Configuring NIC Teaming/Bonding Failsafe mode is inherent in all other teaming modes and is switch agnostic. 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.
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 CLI 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” on page 2-21 “Modifying a Team” on page 2-27 “Deleting a Team” on page 2-33 “Saving and Restoring Teaming Configuration” on page 2-34 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. The software automatically picks a unique team name, or you can 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 Figures 2-7 through 2-10 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 Teaming/Bonding Using LACP on 8200 Series Adapters for Windows NOTE: This feature is available only on Cisco® systems (Cisco FCoE switch). By default, link aggregation control protocol (LACP) is disabled on 8200 Series Adapters (it is enabled by default in the 3200 Series Adapters). Perform the following steps using QLogic Device Windows Properties Page to enable LACP on a 8200 Series Adapter. 1. Log in to the server that contains installed 8200 Series Adapters. 2.
2–Configuring NIC Teaming/Bonding A virtual fabric channel (vFC) can be bound inside a virtual port channel (vPC) because the Cicso Nexus® 5x00 (FCF) sees only one link. Figure 2-18 illustrates a valid configuration with one vPC. Figure 2-18. LACP Configuration with One vPC The vFC must be bound by a physical interface in a vPC configuration. If a server has four Converged Network Adapter ports, then two vPCs can be created, as shown in Figure 2-19. Figure 2-19.
2–Configuring NIC Teaming/Bonding The configurations in Figure 2-20 and Figure 2-21 are unsupported because the vPC can be bound to only one interface. Figure 2-20. Invalid LACP Configuration (One vPC Linked to Two Nexus 5x00s) Figure 2-21.
2–Configuring NIC NIC Partitioning (NPAR) For information on configuring Cisco Nexus switches for vPCs, see to the following: Cisco Nexus 5000 Series Configuring vPCs at: http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/ interfaces/configuration/guide/if_vPC.pdf http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/ configuration_guide_c07-543563.html Cisco Nexus 5000 Series FCoE Configuration Guide at: http://www.cisco.
2–Configuring NIC NIC Partitioning (NPAR) Setup Requirements Table 2-3 and Table 2-4 provide the requirements for applying NPAR functionality to 8200 and 3200 Series Adapters installed in host servers within SANs. Table 2-3. NPAR Operating System Requirements Operating Systems Linux Platforms RHEL5.6 and later, x86 and x64 RHEL6.0 and later, x64 only SLES10 SP4 and later, x64 only SLES11 SP1 and later, x64 only Citrix® XenServer® 6.
2–Configuring NIC NIC Partitioning (NPAR) NPAR Configuration This section defines NPAR configuration, options, and management tools you can use to set up NPAR on the 8200 and 3200 Series Adapters.
2–Configuring NIC NIC Partitioning (NPAR) The VLAN and teaming solutions on partitioned NIC functions have the following restrictions: A failsafe team cannot be created using NIC functions that belong to the same physical port. For example, physical function 2 (PF2) cannot be a backup for PF0 because both functions are partitions of the same physical port. 802.3ad link aggregation teams are not allowed on partitioned NIC functions. Figure 2-22 shows the default NPAR function settings. Figure 2-22.
2–Configuring NIC NIC Partitioning (NPAR) Table 2-5 shows the port identifications and the possible NPAR configurations. Table 2-5. NPAR Configuration Options Function Number Function Type Physical Port Number 0 NIC 0 1 NIC 1 2 NIC 0 3 NIC 1 4 iSCSI/NIC 0 5 iSCSI/NIC 1 6 FCoE/NIC 0 7 FCoE/NIC 1 Notes Always present. Always NIC. Cannot be disabled. NIC or disabled iSCSI, NIC, or disabled FCoE, NIC, or disabled Only one iSCSI and/or FCoE function per physical port.
2–Configuring NIC NIC Partitioning (NPAR) NPAR QoS allows NIC partitions to each allocate a minimum guaranteed portion of the available bandwidth. QoS bandwidth only applies only to NIC partitions. iSCSI partitions are not supported by the QoS bandwidth allocation. This brings up the possibility that, if the total minimum allocated bandwidth across the NIC partitions equals 100 percent, then the iSCSI partition will be limited to 1 percent of the NIC bandwidth portion in high-utilization conditions.
2–Configuring NIC NIC Partitioning (NPAR) Configuration Management Tools Depending on your operating environment and preferred system management techniques, you can use any of the following tools to set up NIC partitions (NPARs) on 8200 and 3200 Series Adapters’ ports to meet your system’s networking requirements: “QLogic OptionROM at POST” on page 2-44 “QConvergeConsole (QCC) GUI” on page 2-44 “QConvergeConsole (QCC) CLI” on page 2-45 “QLogic Device Windows Properties Page” on page 2-46 QLogic O
2–Configuring NIC NIC Partitioning (NPAR) Before configuring NPAR, do the following: Use the QLogic SuperInstaller for your host server’s operating system (Windows or Linux) to install the Fibre Channel/FCoE, NIC, and iSCSI drivers on the server where the adapters reside. To download the installers and drivers, go to http://driverdownloads.qlogic.com.
2–Configuring NIC NIC Partitioning (NPAR) QLogic Device Windows Properties Page Servers that run on supported Windows operating systems have the Windows-based tools available for configuring QLogic adapters. These tools enable you to use the QLogic Device Windows Properties Page to set up and manage NIC partitions. For system requirements, see “Setup Requirements” on page 2-39.
2–Configuring NIC NIC Partitioning (NPAR) The QConvergeConsole GUI and CLI tools work on both Linux and Windows Servers. If you prefer using a browser-based GUI interface, you can use the QConvergeConsole GUI to partition Ethernet ports into NIC, FCoE, or iSCSI partitions and establish quality of service (QoS) by adjusting the bandwidth settings. As an alternative, you can use QConvergeConsole CLI to set up partitions using a command line interface in either interactive or non-interactive mode.
2–Configuring NIC NIC Partitioning (NPAR) 2. Select the adapter you want to manage on the QLogic CNA Function Configuration screen. The screen displays a list of functions available to the selected adapter (Figure 2-24). Figure 2-24. Function Configuration Screen NOTE: For a list of NPAR configuration options, see “NPAR Setup” on page 2-68.
2–Configuring NIC NIC Partitioning (NPAR) 3. Move your cursor to the Type column for any function type you want to change (Figures 2-25 through 2-27). Figure 2-25. Selecting NIC Function Type to Change Figure 2-26.
2–Configuring NIC NIC Partitioning (NPAR) Figure 2-27. Selecting FCoE Function Type to Change 4. Move your cursor to the MinBW% column to adjust the minimum bandwidth (Figure 2-28) on each partition (between 0-100%). Figure 2-28.
2–Configuring NIC NIC Partitioning (NPAR) NOTE: Do not set any bandwidth percentages for the FCoE function. The adapter uses the enhanced transmission selection (ETS) settings for determining FCoE bandwidth. The NIC bandwidth settings configured in the Figure 2-28 are not a percentage of the line rate (10Gb): they are a percentage of the NIC bandwidth allocated to this NIC port through ETS on the switch. 5. Save your changes (Figure 2-29). Figure 2-29. Saving Configuration Changes 6.
2–Configuring NIC NIC Partitioning (NPAR) For procedures on installing and starting this management tool, refer to the QConvergeConsole User's Guide. For help configuring and managing the 8200 and 3200 Series Adapters using this management tool, refer to the QConvergeConsole online help system. To set up NIC partitions using the QCC GUI: 1. Configure NIC Partitions 2.
2–Configuring NIC NIC Partitioning (NPAR) 3. Select the NIC Partitioning tab. The NIC Partitioning Configuration page displays configuration details that apply to the selected NPAR configuration and personality options (Figure 2-30). Figure 2-30. NIC Partitioning Configuration Page 4. Select the physical port you want to configure from the Physical Port drop-down list. 5.
2–Configuring NIC NIC Partitioning (NPAR) NOTE: The NIC Partitioning page applies to NIC ports only for NPAR-enabled 8200 and 3200 Series Adapters. To set the QoS: 1. Expand a 8200 and 3200 Series Adapters node in the QConvergeConsole system tree. 2. Expand the physical Port 1 node and select the NIC port. The content pane displays two additional tabs that are not available on NIC ports for physical Port 2. 3. Select the NIC Partitioning tab, and then click the Management sub-tab.
2–Configuring NIC NIC Partitioning (NPAR) NPAR PCI Function Number. The function number (0, 1, 2, 3, 4, 5, 6, or 7) of the eight PCIe function numbers claimed by the adapter. NPAR Function Type. This field correlates to the personality of the selected NPAR (PCIe) function: NIC, iSCSI, or FCoE. Minimum Bandwidth (%). Use the UP ARROW and DOWN ARROW keys to scroll between 0% to 100% to set the bandwidth you want to guarantee for data sent over the selected partition.
2–Configuring NIC NIC Partitioning (NPAR) To set up NIC partitions using QCC CLI: 1. Start the QCC CLI interface and select option 6: NIC Partitioning Information (Figure 2-32). Figure 2-32. Selecting Option 6 to View NPAR Information Options 2. Enter option 2: NPAR Port Information (Figure 2-33). Figure 2-33.
2–Configuring NIC NIC Partitioning (NPAR) The NPAR Configuration Selection Page displays the current configuration (Figure 2-34). Figure 2-34. NPAR Configuration Selection Screen 3. Return to the main menu after viewing the NPAR information and select option 7: NIC Partitioning Configuration (Figure 2-35). Figure 2-35.
2–Configuring NIC NIC Partitioning (NPAR) 4. Select option 1: NPAR Configuration to display the NPAR Configuration menu, which provides the following options: 1: Bandwidth Configuration 2: Change PCI Function Personality 5. Configure the bandwidth settings to meet your system requirements. For example, to change the bandwidth of the function 1 NIC partition: a. Select option 1: Bandwidth Configuration. b. Select option 1: Function:1. c. Select option 1: Modify Minimum Bandwidth (Figure 2-36).
2–Configuring NIC NIC Partitioning (NPAR) f. Specify whether you want the bandwidth settings to persist across reboots (Figure 2-37). Figure 2-37. Setting Bandwidth Changes to Persist 6. Return to the NIC Partitioning Configuration Selection screen. 7. Change the personalities of each function to meet your system requirements. For example: a. Select option 2: Change PCI Function Personality. b. Select the port number, 1 or 2. c. Select the function number.
2–Configuring NIC NIC Partitioning (NPAR) Figure 2-38 shows the CLI commands leading to the option for changing a function type on a Linux system. Figure 2-38. Selecting Function Type on Linux System 8. Return to the main menu and select option 8: NIC Partitioning Statistics to view the Statistics. Navigate through the menu selections to view eSwitch statistics. 9. After you have finished setting the NIC partitions as desired, reboot the host server for the changes to take effect.
2–Configuring NIC NIC Partitioning (NPAR) Configure NPAR You can use the NIC Partition Management tab in the device properties page to enable NPAR and configure the 10GbE physical port into a multi-function storage and networking port. To set up NPAR on an 8200 and 3200 Series Adapters’ port: 1. Log in to the server that contains installed 8200 and 3200 Series Adapters. 2. Open the Server Manager and select Diagnostics > Device Manager > Network Adapters. 3.
2–Configuring NIC NIC Partitioning (NPAR) c. Select Enable Partition (Figure 2-40). Figure 2-40.
2–Configuring NIC NIC Partitioning (NPAR) When partitioning is enabled, the Adapter Properties page appears as shown in Figure 2-41. Figure 2-41. Partition Enabled 5. Click OK to close the message box that displays the following information: This change requires a reboot. Proceed? 6. Click OK to close the message box that displays the following information: Please reboot the system now 7. SN0054671-00 B Reboot the host server to make the changes take effect.
2–Configuring NIC NIC Partitioning (NPAR) Change Personalities To change function types (personalities) as needed for your network: 1. From the Server Manager, select Diagnostics > Device Manager > Network Adapters. 2. Right-click the desired QLogic 10 Gigabit Ethernet CNA device to change the function type and select Properties from the context menu. 3. On the NIC Partition Management tab, right-click one of the enabled functions and select Convert to from the context menu (Figure 2-42).
2–Configuring NIC NIC Partitioning (NPAR) Manage Bandwidth Using the NIC Partition Management tab in the Windows device properties page, you can allocate minimum and maximum bandwidth for each NIC function. 1. From the 8200 and 3200 Series Adapters Adapter Properties page, select the NIC Partition Management tab. 2. Right-click the function number for the port you want to configure and select Configure Function from the context menu (Figure 2-43). Figure 2-43.
2–Configuring NIC NIC Partitioning (NPAR) 3. Use the Configure Function dialog box to set the minimum and maximum bandwidth percentages, New Minimum BW (%) and New Maximum BW (%) (Figure 2-44). Figure 2-44. Entering New Bandwidth Values NOTE: Enhanced transmission service (ETS) only specifies the division of bandwidth between FCoE and non-FCoE traffic. It does not specify the bandwidth allocated to the NIC or iSCSI partitions. When the switch sets ETS values, the ETS bandwidth parameters take precedence.
2–Configuring NIC NIC Partitioning (NPAR) The new bandwidth values appear in the right pane of the NIC Partition Management property sheet (Figure 2-45). Figure 2-45. NIC Partition Management Property Sheet 6. Click OK at the bottom of the Properties page to close it. View eSwitch Statistics You can use the Window Device Manager’s NIC Partition Management window to view eSwitch statistics for enabled partitions. To display eSwitch statistics: 1.
2–Configuring NIC NIC Partitioning (NPAR) A window opens that displays the statistics (Figure 2-46). Figure 2-46. eSwitch Statistics for Function 0 3. After reviewing the statistics, click OK or Cancel to close the pop-up window. NPAR Setup This section provides NPAR reference tables you can use when configuring NIC partitions using the various tools available.
2–Configuring NIC NIC Partitioning (NPAR) Default Settings Before configuring NIC partitions, the 8200 and 3200 Series Adapters appear as a simple dual-port 10GbE adapter with the NPAR settings shown in Table 2-6. Table 2-6.
2–Configuring NIC NIC Partitioning (NPAR) NPAR Configuration Parameters and Setup Tools Table 2-8 identifies which parameters you can configure using each of the available management tools. Table 2-8.
2–Configuring NIC NIC Partitioning (NPAR) Frequently Asked Questions about NPAR NIC Partitioning Q: What is NIC Partitioning (NPAR)? NIC Partitioning (NPAR) is a method of dividing each QLogic Adapter Ethernet port into a maximum of four partitions or virtual ports (eight virtual ports per adapter). These virtual ports can be assigned NIC, FCoE, or iSCSI personalities, and users can apply QoS settings by flexibly allocating minimum guaranteed bandwidth to each virtual port.
2–Configuring NIC NIC Partitioning (NPAR) Q: What’s the difference between a physical function and a virtual function? Physical functions are full-featured PCIe functions that operate like normal PCI physical devices in terms of discovery, configuration, and management. Virtual functions are “lightweight” (minimized functionality support) PCIe functions that are derived from the physical PCIe functions. Q: Is NPAR included when I purchase my adapter? Yes. Full NPAR functionality comes with your purchase.
2–Configuring NIC NIC TroubleShooting/Diagnostics Networking Q: Why use teaming? Teaming allows for high link availability (fault tolerance). If one of the underlying physical NICs is broken or its cable has been unplugged, the OS will detect the fault condition and automatically move traffic to another NIC in the bond. This capability eliminates a single point of failure for any one physical NIC and makes the overall network connection fault tolerant. In addition, teaming helps with load balancing.
2–Configuring NIC NIC TroubleShooting/Diagnostics Running Linux User Diagnostics Linux user diagnostics include QConvergeConsole diagnostics and ethtool diagnostics. QConvergeConsole 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.
2–Configuring NIC NIC TroubleShooting/Diagnostics To display transceiver DMI data, issue the following command: qaucli -pr nic -trans [cna_port_inst] Ethtool Diagnostics To perform an adapter self-test using ethtool-based diagnostics, issue the following command: # ethtool -t eth offline The self-test includes the following: Loopback test Interrupt test Link test Register test Examples # ethtool -t eth8 offline The test result is PASS The test extra info: Register_Test_on_offline 0 Link
2–Configuring NIC NIC TroubleShooting/Diagnostics Link Test verifies that the port is linked, meaning that the port has a good cable attached to the port and that other end of the cable is connected to an operational Ethernet port, either another NIC port or a network device, such as a switch. Register Test verifies the NIC register read and write.
2–Configuring NIC NIC TroubleShooting/Diagnostics 3. On the adapter properties page, click the Diagnostics tab. Figure 2-47 shows the Diagnostics page. Figure 2-47. Diagnostics Tests on Windows 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” on page 2-81 describes each test type.) 5. Click Run Tests. NOTE: Only one test can run at a time.
2–Configuring NIC NIC TroubleShooting/Diagnostics To run user diagnostics in the CLI: Use QConvergeConsole CLI (qaucli), a unified command line utility, to manage all QLogic adapter models, including running user diagnostics. The overall option (-pr ) allows you to start the utility with a specific protocol type: NIC, iSCSI, or Fibre Channel. If you do not specify a protocol, all protocols are enabled by default.
2–Configuring NIC NIC TroubleShooting/Diagnostics Diagnostic help commands, and command options available for each specific protocol, are available by specifying -h to the protocol, as shown in Table 2-12. Table 2-12.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-14.
2–Configuring NIC NIC TroubleShooting/Diagnostics 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-15. Table 2-15. Running Windows Diagnostic Tests in the CLI Test Type External Loopback Command qaucli -nic -extloopback Where specifies the number of tests, 1–65535, and is either 0=Ignore or 1=Abort.
2–Configuring NIC NIC TroubleShooting/Diagnostics 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. Interrupt Test The interrupt test checks the ability of the hardware to create an interrupt and the ability of the driver to process the interrupt by forcing the generation of a predetermined number of interrupts.
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-16. Note that this table does not list error messages for the interrupt and link tests. Table 2-16.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-16.
2–Configuring NIC NIC TroubleShooting/Diagnostics Table 2-16.
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-48.
2–Configuring NIC NIC TroubleShooting/Diagnostics Figure 2-49.
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 Readme file for information. Packaging Content Refer to the iSCSI Adapter Inbox Driver Update Readme file for information. Linux OS Support Refer to the iSCSI Adapter Inbox Driver Update Readme file for information.
3–Configuring iSCSI Installing iSCSI in ESX Installing iSCSI in ESX Refer to the iSCSI Adapter Driver and IMA Plug-in for VMware ESX/ESXi 4.1.x Readme file for information. Packaging Content Refer to the iSCSI Adapter Driver and IMA Plug-in for VMware ESX/ESXi 4.1.x Readme file for information. ESX OS Support Refer to the iSCSI Adapter Driver and IMA Plug-in for VMware ESX/ESXi 4.1 Readme file for information. Using the Driver Refer to the iSCSI Adapter Driver and IMA Plug-in for VMware ESX/ESXi 4.1.
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 4. Start the system; press Ctrl+Q when the BIOS screen for the QLogic Adapter opens. The Fast!UTIL Options menu opens. 5. Select Configuration Settings. 6. Select Host Adapter Settings. 7. Enable the Host Adapter BIOS. 8. Press ESC to exit the Host Adapter Settings window. 9. Select iSCSI Boot Settings. 10. Enable iSCSI Boot. DHCP Boot Setup for iSCSI Boot (IPv4) DHCP boot provides a method for the iSCSI initiator to acquire target parameters from a DHCP server.
3–Configuring iSCSI iSCSI TroubleShooting iSCSI Boot Setup Using QCC GUI Refer to the Configuring Boot Settings section in the QConvergeConsole Help System for information. Configuring iSCSI Boot using the QCC GUI Refer to the Configuring Boot Settings section in the QConvergeConsole Help System for information. Configuring iSCSI DHCP Boot Options Refer to the Configuring Boot Settings section in the QConvergeConsole Help System 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 Linux Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update Readme file for information. Packaging Content Refer to the Linux Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update Readme file for information.
4–Configuring FCoE Installing FCoE Firmware Installation Refer to the Linux Fibre Channel Adapter and Converged Network Adapter Inbox Driver Update 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 QLogic Adapter Parameters QLogic Adapter Parameters Setting QLogic Adapter Parameters with the QCC GUI Refer to the QConvergeConsole Help System: Managing Fibre Channel and FCoE Adapters and Ports for information. Setting QLogic Adapter Parameters with the Interactive QCC CLI Refer to the QConvergeConsole CLI User’s Guide for information.
4–Configuring FCoE Virtual Ports (NPIV) Configuring Boot Devices with the BIOS Refer to “Using QLflash” on page 1-6 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 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. FCoE Diagnostics using Interactive QCC CLI Refer to the QConvergeConsole CLI User's Guide 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 B
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 path (continued) 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.
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters target The storage-device endpoint of a SCSI session. Initiators request data from targets (usually disk-drives, tape-drives, or other media devices). Typically, a SCSI peripheral device is the target but an adapter may, in some cases, be a target. A target can contain many LUNs. A target is a device that responds to a request by an initiator (the host system).
User’s Guide Converged Network Adapter 8200 and 3200 Series Adapters Glossary-6 SN0054671-00 B
Index –pr command 2-78 A adapter definition of Glossary-1 port beacon, definition of Glossary-1 port, definition of Glossary-1 adding team members 2-28 advanced stateless offload features 1-2 Agency certification, QLogic Adapters xix agents, remote 2-45 airborne contaminants 1-4 alias, definition of Glossary-1 altitude ranges 1-4 audience for this guide xvi B bandwidth adjusting 2-47 allocation 2-42 maximum 2-38, 2-55 minimum 2-38, 2-55 QCC CLI option 2-58 QCC GUI, setting with 2-53 user-config
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series defaults, NPAR 2-69 defaults, NPAR configuration 2-41 Device Manager 2-9 device, definition of Glossary-2 diagnostics ethtool 2-75 FCoE function 4-5 iSCSI function 3-9 Linux text messages 2-76 NIC, running in Linux 2-74 QCC CLI 2-86 QCC GUI 2-86 QLogic Device Windows Property Page 2-76 Windows QCC CLI diagnostic test commands 2-79 Windows test messages 2-83 DLA 2-18 documentation, related xvi downloading QLogic d
User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series function numbers 2-40 function, NPAR PCI function number 2-55 H hardware test 2-75, 2-81, 2-82, 2-83 Health Monitoring parameter 2-10 help commands for NIC diagnostics in QCC CLI 2-79 host server 2-51, 2-55 humidity specifications 1-4 I installing drivers for QLogic Adapters xxv NIC in VMware ESX 2-1 QCC CLI xxv QCC GUI xxv QLflash 1-15 QLogic Adapter CIM Provider 1-12 QLogic Adapter vCenter Plug-in on Tomcat S
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Linux bonding driver 2-34 bonding, failover, aggregation 2-34 diagnostic test descriptions 2-75 diagnostic test messages 2-76 FCoE, installing in 4-1 function type, changing using QCC CLI 2-60 iSCSI function, installing in 3-1 iSCSI initiator, configuring in 3-3 NIC diagnostics, running 2-74 NIC function, installing in 2-1 NPAR, supported platforms for 2-39 load balancing, definition of Glossary-2 local area netw
User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series NPAR changing personalities 2-41 configuration options 2-42, 2-69 configuration parameters 2-70 configuring 2-40 default configurations 2-41 default settings 2-69 definition of 2-38 drivers used with 2-39 management options 2-46 OptionROM, configuring with 2-47 options 2-40 overview 2-46 parameters 2-54 PCI function number 2-55 PCI function type 2-55 QCC CLI, configuring with 2-55 QCC GUI, configuring with 2-52 Q
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Q qaucli utility 2-7 QCC CLI boot devices, configuring with 4-3 configuring NPAR with 2-55 diagnostics 2-86 driver parameters, configuring with 4-4 FCoE diagnostics in 4-5 function type, changing on Linux 2-60 help commands for NIC diagnostics 2-79 installing xxv iSCSI boot options configuration 3-8 iSCSI boot setup 3-8 iSCSI diagnostics with 3-9 iSCSI function, configuring with 3-3 iSCSI initiator in Linux, conf
User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series QLogic Adapter vCenter Plug-in components needed for installation 1-11 description of 1-10 removing 1-15 starting 1-15 Tomcat Server, installing on 1-19 Tomcat Server, using on 1-17 unregistration from a manual installation 1-19 vSphere Client, launching from 1-20 QLogic Adapters definition of 1-1 features 1-1 installing xxiii LEDs A-1 physical characteristics 1-3 qlremote 2-45 QoS definition of 2-42, Glossary-4
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series teaming configuration, saving 2-34 creating a team 2-21 deleting a team 2-33 failsafe team 2-32 MAC address 2-15 members, adding 2-28 members, removing 2-29 modes 2-15 modifying a team 2-31, 2-33 NPAR restrictions 2-41 QCC CLI, using for 2-19 statistics 2-34 Windows 2-14 technical support xvii temperature ranges 1-4 terminology xvi tests external loopback 2-81 Flash 2-75, 2-81 hardware 2-75, 2-81, 2-82, 2-83 inte
User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Windows 2-46 diagnostic test descriptions 2-81 diagnostic test messages 2-83 diagnostics, running in QCC CLI 2-78 diagnostics, running in QCC GUI 2-76 FCoE, installing in 4-2 iSCSI initiator, configuring in 3-4 iSCSI, installing in 3-2 NIC, installing on 2-2 NPAR, supported platforms for 2-39 NPAR, using with 2-39 QLogic Device Windows property pages 2-9 teaming 2-14 Windows Device Manager bandwidth, modifying in
User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series Index-10 SN0054671-00 B
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, QLogic logo, Fast!UTIL, and QConvergeConsole are trademarks or registered trademarks of QLogic Corporation.