Q-Logic 3200, 8200 User Manual 2

Download

Page 1

User’s Guide

Converged Network Adapters and

Intelligent Ethernet Adapters

8200 and 3200 Series

SN0054671-00 B

Page 2

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. Applications described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.

Document Revision History

Revision A, March 31, 2011

Revision B, October 31, 2011

Changes Sections Affected

Added “Intelligent Ethernet Adapters” to title. Title page

Renamed Windows Property Pages to QLogic

All

Device Windows Property Page.

Remove references to Release Notes. “Related Materials” on page xvi, “Supported Operating

Systems” on page 1-3, “ESX/ESXi Server” on page 1-11

Added “Intelligent Ethernet Adapters” to first

“Intended Audience” on page xvi

sentence.

Removed QLE8xxx nomenclature from agency certification where the requirements apply to

“EMI and EMC Requirements” on page xix, “CNS 13438: Class A” on page xx

both 8200 and 3200 Series adapters.

Added “iSCSI” to the first and second sen-

“What is a Converged Network Adapter?” on page 1-1

tences.

Under multi-boot capability, removed unified

“Features” on page 1-1

extensible firmware interface (UEFI).

Removed Step 1, Verify Package Contents.

Quick Start

Updated the instructions in “Step 2. Install the

Adapter Drivers” on page xxv.

Updated the instructions in “Step 3. Install

QConvergeConsole

” on page xxv.

Add instructions “Step 4. Update the Flash” on

page xxvi.

Added “multi-boot image” to the first bullet. “Additional Resources” on page xxvi

Changed the first sentence to “A Converged

“What is a Converged Network Adapter?” on page 1-1

Network Adapter is a multifunction adapter that combines the capabilities of a Fibre Channel adapter, an iSCSI adapter, and an Ethernet NIC.

ii SN0054671-00 B

Page 3

User’s Guide—Converged Network Adapters and

Intelligent Ethernet Adapters

Moved PXE parameter from Function parameter to Protocol parameter.

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

Changed section title (removed utility name). Removed Function parameter section.

Updated Readme file name. “Installing NIC in ESX/ESXi” on page 2-1, “Installing

Added ESXi to section title. “Installing NIC in ESX/ESXi” on page 2-1

Removed phantomcore Utility section. from “Linux NIC Driver Management Applications” on

Corrected values for Priority & VLAN Tag parameter in Tab le 2 -1 .

“Protocol” on page 1-9

Adapter—CNA Function Configuration Utility” on

page 1-5, “Protocol” on page 1-9, Function parameter

section (removed)

“Adapter Configuration Utility” on page 1-8

iSCSI in Linux” on page 3-1, “Installing iSCSI in ESX”

on page 3-2, “Installing FCoE in Linux” on page 4-1

page 2-6

“QLogic Device Windows Property Pages” on

page 2-9.

Added new section about link aggregation control protocol (LACP).

Changed the NPAR instructions. “NIC Partitioning (NPAR)” on page 2-38, and all asso-

Removed the note stating that external and internal loopback tests are not supported.

Corrected the name of the iSCSI VMware readme file.

Added the sentence “

Use Fast!UTIL to pro-

“Using LACP on 8200 Series Adapters for Windows”

on page 2-35

ciated subsections

“Linux Diagnostics” on page 2-73, “QLogic Device

Windows Property Page Diagnostics” on page 2-76

“Installing iSCSI in ESX” on page 3-2

“iSCSI Boot Setup Using Fast!UTIL” on page 3-6

gram the QLogic iSCSI adapter to boot from the SAN” to the end of the first paragraph.

Changed the iSCSI boot setting instructions. “Configuring iSCSI Boot Settings” on page 3-7

Changed section heading to add IPv4; removed note about IPv6 not being supported.

“DHCP Boot Setup for iSCSI Boot (IPv4)” on page 3-8

SN0054671-00 B Page iii

Page 4

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.

Added index. “Index” on page Index-1

from “Driver Parameters” on page 4-4

Page iv SN0054671-00 B

Page 5

Table of Contents

Preface

What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Laser Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

FDA Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Agency Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

EMI and EMC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

CNS 13438: Class A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

MIC: Class A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Product Safety Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Quick Start

Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Step 1. Install the Adapter Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Step 2. Install the Adapter Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Step 3. Install QConvergeConsole

Step 4. Update the Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

1 Product Overview

What is a Converged Network Adapter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

What is an Intelligent Ethernet Adapter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

SN0054671-00 B v

Page 6

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series

Functionality and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Adapter Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Physical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Standards Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Environmental Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Converged Network Adapter SuperInstaller Installation. . . . . . . . . . . . . . . . 1-5

QLogic Windows SuperInstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

QLogic Linux SuperInstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Multi-boot Image for 10Gb Converged Network Adapter—CNA Function

Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Multi-boot Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Converged Network Adapter Function Configuration Package

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Using QLflash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Updating the Multi-boot Code. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

QLflash Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Adapter Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

MinBW%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Restore to Non-NIC Partition Settings . . . . . . . . . . . . . . . . . . . . 1-9

Exit the CNA Function Configuration Utility . . . . . . . . . . . . . . . . 1-9

Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi. . . . . . . . . . . . 1-10

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

ESX/ESXi Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Tomcat Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Installing the QLogic Adapter CIM Provider . . . . . . . . . . . . . . . . . . . . 1-12

Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Subsequent Update Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Starting the QLogic Adapter CIM Provider . . . . . . . . . . . . . . . . . . . . . 1-13

Removing the QLogic Adapter CIM Provider . . . . . . . . . . . . . . . . . . . 1-13

Starting the QLogic Adapter vCenter Plug-in. . . . . . . . . . . . . . . . . . . . 1-15

Removing the QLogic Adapter vCenter Plug-in. . . . . . . . . . . . . . . . . . 1-15

Installing the Flash Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

vi SN0054671-00 B

Page 7

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters

Updating the Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Using the vCenter Plug-in on a Tomcat Server . . . . . . . . . . . . . . . . . . 1-17

Installing Tomcat on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Starting and Stopping Tomcat on Linux . . . . . . . . . . . . . . . . . . . 1-18

Installing Tomcat on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Starting and Stopping Tomcat on Windows . . . . . . . . . . . . . . . . 1-18

Installing the vCenter Plug-in on Tomcat . . . . . . . . . . . . . . . . . . 1-19

Plug-in Unregistration from a Manual Installation . . . . . . . . . . . . . . . . 1-19

Launching the Plug-in from vSphere Client . . . . . . . . . . . . . . . . . . . . . 1-20

2 Configuring NIC

Installing NIC in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Linux OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Using the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing NIC in ESX/ESXi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

ESX OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Using the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Installing NIC in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Windows OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Using the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Configuring PXE Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Configuring Driver Software Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Linux NIC Driver Management Applications . . . . . . . . . . . . . . . . . . . . 2-6

qaucli Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

ethtool Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

QLogic Device Windows Property Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Configuring NIC Driver Parameters with QCC GUI. . . . . . . . . . . . . . . 2-13

Configuring NIC Driver Parameters with QCC Interactive CLI . . . . . . 2-14

Configuring NIC Driver Parameters with QCC Non-Interactive CLI . . 2-14

VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

VLAN Configuration with QCC GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

VLAN Configuration with the QCC Interactive CLI . . . . . . . . . . . . . . . 2-14

VLAN Configuration with the QCC Non-Interactive CLI . . . . . . . . . . . 2-14

8200 and 3200 Series

SN0054671-00 B vii

Page 8

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series

Teaming/Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Windows Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Team MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Teaming Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Using the CLI for Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Using the Team Management GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Teaming Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Creating a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Modifying a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Deleting a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Saving and Restoring Teaming Configuration . . . . . . . . . . . . . . 2-34

Viewing Teaming Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Linux Bonding/Failover/Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Using LACP on 8200 Series Adapters for Windows . . . . . . . . . . . . . . 2-35

NIC Partitioning (NPAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

NPAR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40

NIC Partitioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40

Personality Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

eSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Configuration Management Tools . . . . . . . . . . . . . . . . . . . . . . . . 2-44

NPAR Setup and Management Options . . . . . . . . . . . . . . . . . . . . . . . 2-46

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

QLogic OptionROM at POST . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47

QConvergeConsole (QCC) GUI . . . . . . . . . . . . . . . . . . . . . . . . . 2-51

QConvergeConsole (QCC) CLI . . . . . . . . . . . . . . . . . . . . . . . . . 2-55

QLogic Device Windows Properties Page . . . . . . . . . . . . . . . . . 2-60

NPAR Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

NPAR Configuration Parameters and Setup Tools . . . . . . . . . . . 2-70

Frequently Asked Questions about NPAR. . . . . . . . . . . . . . . . . . . . . . 2-71

NIC Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71

Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

viii SN0054671-00 B

Page 9

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters

NIC TroubleShooting/Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

NIC Linux Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

Linux Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

QLogic Device Windows Property Page Diagnostics . . . . . . . . . . . . . 2-76

Running Windows User Diagnostics. . . . . . . . . . . . . . . . . . . . . . 2-76

Windows Diagnostic Test Descriptions . . . . . . . . . . . . . . . . . . . . 2-81

Windows Diagnostic Test Messages . . . . . . . . . . . . . . . . . . . . . 2-83

NIC Troubleshooting Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87

3 Configuring iSCSI

iSCSI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing iSCSI in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Linux OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Deploying the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Driver System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing iSCSI in ESX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

ESX OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Using the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Installing the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Installing iSCSI in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Windows OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Using the Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

iSCSI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

iSCSI Configuration with QCC GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

iSCSI Configuration with Interactive QCC CLI . . . . . . . . . . . . . . . . . . 3-3

iSCSI Configuration with Non-Interactive CLI . . . . . . . . . . . . . . . . . . . 3-3

iSCSI Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuring an iSCSI Initiator in Linux . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuring an iSCSI Initiator in Windows. . . . . . . . . . . . . . . . . . . . . . 3-4

Configuring an iSCSI Initiator in VMware . . . . . . . . . . . . . . . . . . . . . . 3-6

iSCSI Name Server iSNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

8200 and 3200 Series

SN0054671-00 B ix

Page 10

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series

iSCSI Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

iSCSI Boot Setup Using Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Accessing Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Configuring iSCSI Boot Settings. . . . . . . . . . . . . . . . . . . . . . . . . 3-7

DHCP Boot Setup for iSCSI Boot (IPv4) . . . . . . . . . . . . . . . . . . . . . . . 3-8

iSCSI Boot Setup Using QCC CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Configuring iSCSI Boot using the QCC CLI . . . . . . . . . . . . . . . . 3-8

Configuring iSCSI DHCP Boot Options using QCC CLI. . . . . . . 3-8

Configuring iSCSI DHCP Boot Options using Interactive

QCC CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Configuring iSCSI DHCP Boot Options using Non-interactive

QCC CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

iSCSI Boot Setup Using QCC GUI . . . . . . . . . . . . . . . . . . . . . . . 3-9

iSCSI TroubleShooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

iSCSI Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

iSCSI Diagnostics using QCC GUI. . . . . . . . . . . . . . . . . . . . . . . 3-9

iSCSI Diagnostics using Interactive QCC CLI . . . . . . . . . . . . . . 3-9

iSCSI Troubleshooting Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

4 Configuring FCoE

Installing FCoE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Installing FCoE in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Linux OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Deploying the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Driver System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Boot From SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Firmware Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Installing FCoE in ESX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ESX OS Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Installing FCoE in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Packaging Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Windows OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

x SN0054671-00 B

Page 11

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters

8200 and 3200 Series

QLogic Adapter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Setting QLogic Adapter Parameters with the QCC GUI . . . . . . . . . . . 4-3

Setting QLogic Adapter Parameters with the Interactive QCC CLI . . 4-3 Setting QLogic Adapter Parameters with the Non-Interactive

QCC CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Target Persistent Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuring Persistent Binding with the QCC GUI . . . . . . . . . . . . . . . 4-3

Configuring Persistent Binding with the Interactive QCC CLI . . . . . . . 4-3

Configuring Persistent Binding with the Non-Interactive QCC CLI . . . 4-3

Boot Devices Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuring Boot Devices with the QCC GUI . . . . . . . . . . . . . . . . . . . 4-3

Configuring Boot Devices with the Interactive QCC CLI . . . . . . . . . . 4-3

Configuring Boot Devices with the Non-Interactive QCC CLI . . . . . . . 4-3

Configuring Boot Devices with the BIOS. . . . . . . . . . . . . . . . . . . . . . . 4-4

Virtual Ports (NPIV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Configuring NPIV with the QCC GUI. . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Configuring NPIV with the Interactive QCC CLI . . . . . . . . . . . . . . . . . 4-4

Configuring NPIV with the Non-Interactive QCC CLI . . . . . . . . . . . . . 4-4

Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Configuring FCoE Driver Parameters with the QCC GUI . . . . . . . . . . 4-4

Configuring FCoE Driver Parameters with the Interactive QCC CLI . 4-4 Configuring FCoE Driver Parameters with the Non-Interactive

QCC CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Selective LUNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Configuring Selective LUNS with the QCC GUI . . . . . . . . . . . . . . . . . 4-4

Configuring Selective LUNS with the Interactive QCC CLI . . . . . . . . 4-4

Configuring Selective LUNS with the Non-Interactive QCC CLI . . . . . 4-5

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

FCoE Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

FCoE Diagnostics using QCC GUI. . . . . . . . . . . . . . . . . . . . . . . 4-5

FCoE Diagnostics using Interactive QCC CLI . . . . . . . . . . . . . . 4-5

FCoE Troubleshooting Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

A Adapter LEDs

Glossary

Index

SN0054671-00 B xi

Page 12

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2-2 QLogic 8200 CNA Function Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2-3 BIOS: Boot Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2-4 Embedded NIC 1 QLogic PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2-5 Team Management Property Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

2-6 Creating a Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

2-7 Creating a Failsafe Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

2-8 Creating a Switch-Independent Load Balancing Team . . . . . . . . . . . . . . . . . . . . . . 2-24

2-9 Creating an 802.3ad Static Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

2-10 Creating an 802.3ad Dynamic Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

2-11 Confirming New Team Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

2-12 Adding a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

2-13 Modifying Advanced Team Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

2-14 Modifying Team Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

2-15 Modifying Failsafe Team Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

2-16 Modifying the Team Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

2-17 Enabling LACP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

2-18 LACP Configuration with One vPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

2-19 LACP Configuration with Two vPCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

2-20 Invalid LACP Configuration (One vPC Linked to Two Nexus 5x00s). . . . . . . . . . . . 2-37

2-21 Invalid LACP Configuration (Two vPCs Linked Separately to Two Nexus 5x00s) . . 2-37

2-22 NPAR Default Function Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

2-23 POST Test Screen Prompt to Enter Setup Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47

2-24 Function Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

2-25 Selecting NIC Function Type to Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49

2-26 Selecting iSCSI Function Type to Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49

2-27 Selecting FCoE Function Type to Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

2-28 Adjusting the Minimum Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

2-29 Saving Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51

2-30 NIC Partitioning Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53

2-31 NIC Partitioning—General Management Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

2-32 Selecting Option 6 to View NPAR Information Options . . . . . . . . . . . . . . . . . . . . . . 2-56

2-33 Selecting Option 2 to View NPAR Port Information . . . . . . . . . . . . . . . . . . . . . . . . . 2-56

2-34 NPAR Configuration Selection Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

2-35 Selecting NPAR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

2-36 Selecting to Modify Minimum Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

2-37 Setting Bandwidth Changes to Persist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

2-38 Selecting Function Type on Linux System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

2-39 Selecting Properties from the Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61

2-40 Enabling Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62

xii SN0054671-00 B

Page 13

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters

8200 and 3200 Series

2-41 Partition Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63

2-42 Selecting Convert to NIC from Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64

2-43 Selecting Configure Function for Function 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65

2-44 Entering New Bandwidth Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66

2-45 NIC Partition Management Property Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67

2-46 eSwitch Statistics for Function 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

2-47 Diagnostics Tests on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77

2-48 NIC Troubleshooting Diagram 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87

2-49 NIC Troubleshooting Diagram 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88

3-1 iSCSI Troubleshooting Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

4-1 FCoE Troubleshooting Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

List of Tables

Table Page

1-1 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

2-1 Windows Driver Configurable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2-2 Windows Teaming Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

2-3 NPAR Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

2-4 NPAR Management Tool and Driver Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 2-39

2-5 NPAR Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

2-6 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

2-7 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

2-8 NPAR Configuration Parameters and Setup Tools. . . . . . . . . . . . . . . . . . . . . . . . . . 2-70

2-9 NPAR Wake-on-LAN (WOL) and PXE Boot Support . . . . . . . . . . . . . . . . . . . . . . . . 2-70

2-10 Windows QConvergeConsole CLI—Selecting a Protocol in Menu Mode . . . . . . . . 2-78

2-11 Windows QConvergeConsole CLI—Selecting a Protocol in Legacy Mode . . . . . . . 2-78

2-12 Windows QConvergeConsole CLI—Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79

2-13 Windows QConvergeConsole CLI—Miscellaneous Commands . . . . . . . . . . . . . . . 2-79

2-14 Windows QConvergeConsole CLI—Diagnostic Test Commands . . . . . . . . . . . . . . 2-79

2-15 Running Windows Diagnostic Tests in the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81

2-16 Windows Diagnostic Test Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83

A-1 QLE824x and QLE324x LED Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

SN0054671-00 B xiii

Page 14

User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8200 and 3200 Series

xiv SN0054671-00 B

Page 15

Preface

This guide provides detailed instructions on the installation, configuration, and troubleshooting of 8200 and 3200 Series Adapters for Windows VMware 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.

. It also provides details on the use of QLogic adapter features to

What’s in This Guide

This guide is organized into the following sections and appendices:

 This Preface describes the intended audience, related materials, document

conventions used, license agreements, technical support, and legal notices.

 The Quick Start section provides high-level hardware and software

installation instructions for advanced users.

 The Product Overview provides a product introduction and specifications;

information about the multi-boot image (CNA Function Configuration Utility); and detailed installation instructions for the SuperInstaller and vCenter Plug-in for ESX/ESXi.

 The Configuring NIC section describes installing the NIC driver and agent

across operating systems (OSs); configuring the PXE boot; how to use driver parameters, VLANs, and teaming/bonding; and troubleshooting NIC issues.

, Linux®, and

 The Configuring iSCSI section describes installing the iSCSI driver and

agent across OSs; configuring iSCSI; how to use the iSCSI initiator, iSNS, and iSCSI boot; and troubleshooting iSCSI issues.

 The Configuring FCoE section describes installing the Fibre Channel over

Ethernet (FCoE) driver and agent across OSs; setting HBA parameters; configuring the boot device, N_Port ID virtualization (NPIV), driver parameters, and selective LUNs; and troubleshooting FCoE issues.

 The Glossary describes many of the terms used in this guide.

SN0054671-00 B xv

Page 16

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.

Related Materials

For additional information, refer to the 8200 and 3200 Series Adapters Read Me files, the QConvergeConsole User’s Guide, and the QConvergeConsole CLI User’s Guide, available on the QLogic Web site, Downloads page:

http://driverdownloads.qlogic.com

Documentation Conventions

This guide uses the following documentation conventions:

 The 8200 and 3200 Series Adapters are also referred to as QLogic Adapter

and adapters.

 NOTE: provides additional information.

 CAUTION!

causing damage to data or equipment.

 WARNING!!

causing personal injury.

 Tex t in blue font indicates a hyperlink (jump) to a figure, table, or section in

this guide, and links to Web sites are shown in underlined blue example:

 Table 9-2 lists problems related to the user interface and remote agent.

 See “Installation Checklist” on page 3-6.

 For more information, visit www.qlogic.com

 Tex t in bold font indicates user interface elements such as a menu items,

buttons, check boxes, or column headings. For example:

 Click Start, point to Programs, point to Accessories, and then click

 Under Notification Options, select the Warning Alarms check box.

indicates the presence of a hazard that has the potential of

. For

Command Prompt.

xvi SN0054671-00 B

Page 17

Preface

License Agreements

 Tex t 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:

cd /root and press ENTER.

Type

 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.

 Tex t 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).

 Topic titles between quotation marks identify related topics either within this

manual or in the online help, which is also referred to as the help system throughout this document.

License Agreements

Refer to the QLogic Software End User License Agreement for a complete listing of all license agreements affecting this product.

Technical Support

Customers should contact their authorized maintenance provider for technical support of their QLogic products. QLogic-direct customers may contact QLogic Technical Support; others will be redirected to their authorized maintenance provider.

Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.

QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays. For customers with extended service, consult your plan for available hours.

For details about available service plans, or for information about renewing and extending your service, visit the Service Program web page at

http://www.qlogic.com/services

SN0054671-00 B xvii

Page 18

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 Certification on the left. The QLogic Global Training Portal offers online courses, certification exams, and scheduling of in-person training.

Technical Certification courses include installation, maintenance and troubleshooting QLogic products. Upon demonstrating knowledge using live equipment, QLogic awards a certificate identifying the student as a certified professional. You can reach the training professionals at QLogic by e-mail at

training@qlogic.com

Contact Information

, click the Support tab at the top, then click Training and

Support Headquarters

QLogic Web Site

Technical Support Web Site

Technical Support E-mail

Technical Training E-mail

For Support phone numbers, see the Contact Support link at support.qlogic.com.

Knowledge Database

The QLogic knowledge database is an extensive collection of QLogic product information that you can search for specific solutions. We are constantly adding to the collection of information in our database to provide answers to your most urgent questions. Access the database from the QLogic Support Center:

http://support.qlogic.com

QLogic Corporation 4601 Dean Lakes Blvd. Shakopee, MN 55379 USA

www.qlogic.com

http://support.qlogic.com

support@qlogic.com

training@qlogic.com

xviii SN0054671-00 B

Page 19

Legal Notices

CLASS I LASER

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.

Class 1 Laser Product Caution—Class 1 laser radiation when open Appareil laser de classe 1 Do not view directly with optical instruments Produkt der Laser Klasse 1 Luokan 1 Laserlaite Attention—Radiation laser de classe 1

Preface

Legal Notices

Ne pas regarder directement avec des instruments optiques Vorsicht—Laserstrahlung der Klasse 1 bei geöffneter Abdeckung Direktes Ansehen mit optischen Instrumenten vermeiden

Agency Certification

The following sections contain a summary of EMC/EMI test specifications performed on the QLogic adapters to comply with radiated emission, radiated immunity, and product safety standards.

EMI and EMC Requirements

FCC Part 15 compliance: Class A

statement: This device complies with Part 15 of the FCC Rules. Operation is

subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

ICES-003 compliance: Class A This Class A digital apparatus complies

with Canadian ICES-003.Cet appareil numériqué de la classe A est conformé à la norme NMB-003 du Canada.

Varoitus—Luokan 1 lasersäteilyä, kun laite on auki Älä katso suoraan laitteeseen käyttämällä optisia instrumenttej

FCC compliance information

SN0054671-00 B xix

Page 20

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

AS/NZS CISPR22: Class A

CNS 13438: Class A

This is a Class A product. In a domestic environment, this product may cause radio interference, in which case, the user may be required to take adequate measures.

MIC: Class A

Korea RRA Class A Certified

A class equipment (Business purpose info/telecommunica-

tions equipment)

Product Name/Model Fibre Channel Adapter Certification holder—QLogic Corporation Manufactured date—Refer to date code listed on product Manufacturer/Country of origin QLogic Corporation/USA

As this equipment has undergone EMC registration for business purpose, the seller and/or the buyer is asked to beware of this point and in case a wrongful sale or purchase has been made, it is asked that a change to household use be made.

xx SN0054671-00 B

Page 21

Korean Language Format— Class A

Product Safety Compliance

UL, cUL product safety: 8200 and 3200 Series Adapters

UL60950-1 (2 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.

2006/95/EC low voltage directive: 8200 and 3200 Series Adapters

TUV: EN60950-1:2006+A11 2nd Edition EN60825-1:1994+A1+A2 EN60825-2:2004+A1 IEC60950-1 2nd Edition (2005) CB

Edition), 2007-03-3-27

Preface

Legal Notices

CB Certified to IEC 60950-1 2nd Edition

SN0054671-00 B xxi

Page 22

Preface Legal Notices

xxii SN0054671-00 B

Page 23

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). Before handling the adapter, use standard methods to discharge static electricity. Place the adapter on the bag when examining it. Retain the bag for future use.

Step 1. 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. Remove the computer cover and find an empty PCIe

4. Pull out the slot cover (if any) by removing the screw or releasing the lever.

5. Install the low-profile bracket (if required).

SN0054671-00 B xxiii

x8 (or larger) bus slot.

Page 24

Quick Start

ADAPTER RETAINING BRACKET

LEVER

SLOT COVERS

SYSTEM CHASSIS

PCI EXPRESS x8 (OR LARGER) SLOT REQUIRED FOR QLOGIC ADAPTERS.

SCREW

ADAPTER

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).

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. 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.pdf

10. Plug in the power cable and turn on the computer.

xxiv SN0054671-00 B

Page 25

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. In the Select the Product Technology menu, select either

Converged Network Adapters or Intelligent Ethernet Adapters, as appropriate.

Quick Start

Step 2. Install the Adapter Drivers

d. In the Select the Model menu, select your QLogic Adapter.

e. In the Select the Desired Item menu, select Drivers.

f. Click Search.

5. Scroll through the options that are shown; select the appropriate driver.

6. Click Download Now.

7. Follow the installation instructions included in the Readme file for the downloaded driver.

Step 3. Install QConvergeConsole

To install QConvergeConsole:

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.

SN0054671-00 B xxv

Page 26

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. Follow the instructions in the QConvergeConsole readme file for installing the downloaded software.

Step 4. Update the Flash

Download and update the QLogic adapter with the latest required version of the Flash Image from http://driverdownloads.qlogic.com

The Flash image package for the 8200 and 3200 Series Adapters includes boot code, firmware, and the Flash update utility. Refer to the Readme file on the QLogic Web site for details on the package contents and update instructions (http://driverdownloads.qlogic.com

Additional Resources

 To obtain the most current drivers, management tools, multi-boot image,

user instructions, and documentation, please visit the QLogic Web site at

http://driverdownloads.qlogic.com

 See What’s in This Guide for descriptions of user instructions provided in

this document.

 For important product information, including warranty, laser safety, and

agency certification, and see the Legal Notices section.

 For descriptions and procedures related to QConvergeConsole, use the

built-in help system.

and download the latest versions.

xxvi SN0054671-00 B

Page 27

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.

What is an Intelligent Ethernet Adapter?

The Intelligent Ethernet Adapter is a multifunction adapter which, by default, supports one Ethernet function per port and can be expanded to four Ethernet functions per port.

Functionality and Features

This section provides the following information:

 “Functional Description” on page 1-1  “Features” on page 1-1  “Supported Operating Systems” on page 1-3

Functional Description

The 8200 Series Adapters are Converged Network Adapters, and the 3200 Series Adapters are Intelligent Ethernet Adapters (IEA). The 8200 Series Adapters support 210GbE Enhanced Ethernet, FCoE, and iSCSI. The 3200 Series Adapters support 210GbE Enhanced Ethernet ports.

Features

The 8200 and 3200 Series Adapters provide the following features:

 NIC partitioning (NPAR)

 Message signaled interrupts (MSI-X)

 Device management for LAN and SAN

SN0054671-00 B 1-1

Page 28

1–Product Overview Functionality and Features

 Multi-boot capability including:

 Preboot-eXecution environment (PXE)

 iSCSI (8200 Series Adapters only)

 Fibre Channel (8200 Series Adapters only)

 PCIe 2.0 8

 User diagnostics that can be run from the CLI and the GUI

 Ethernet functions include:

 210 GbE

 Priority and virtual LAN (VLAN) tagging

 Jumbo frames up to 9618 bytes

 Advanced teaming

 VLAN configuration and management

 Preservation of teaming and VLAN configuration information during

driver upgrade

 Enhanced Ethernet functions include:

 Priority-based flow control (802.1Qbb)

 Enhanced transmission selection (802.1Qaz)

 Data center bridging exchange protocol (802.1Qaz)

 Link aggregation (802.3ad)

 Advanced stateless offload features include:

 IP, TCP, and UDP checksums

 Large send offload (LSO)

 Large receive offload (LRO)

 Stateful offload features (8200 Series Adapters only) include:

 iSCSI

 FCoE

 Several advanced management features for iSCSI and Fibre Channel

adapters, including QConvergeConsole (QCC) (GUI and CLI) and NIC partitioning (NPAR)

 Interrupt management and scalability features including:

 Receive side scaling (RSS)

 Interrupt moderation

1-2 SN0054671-00 B

Page 29

 Flow control

 Locally administered address (LAA)

 Enhanced optimization with MSI, MSI-X, and NetQueue

Supported Operating Systems

1–Product Overview

Adapter Specifications

The 8200 and 3200 Series Adapters support commonly used operating systems (OSs): Windows, Linux, Solaris

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.com

Adapter Specifications

Physical Characteristics

The 8200 and 3200 Series Adapters are implemented as low-profile PCIe cards. The adapters ship with a full-height bracket for use in a standard PCIe slot or an optional spare low-profile bracket for use in a low-profile PCIe slot. Low-profile slots are typically found in compact servers.

Standards Specifications

The 8200 and 3200 Series adapters support the following standards specifications:

 IEEE: 802.3ae (10 Gb Ethernet)  IEEE: 8021q (VLAN)  IEEE: 802.3ad (Link Aggregation)  IEEE: 802.1p (Priority Encoding)  IEEE: 802.3x (Flow Control)  IEEE: 802.1Qbb (Priority Based Flow Control)  IEEE: 802.1Qaz (Enhanced Transmission Selection)  IPv4 Specification (RFC791)  IPv6 Specification (RFC2460)  TCP/UDP Specification (RFC793/768)  ARP Specification (RFC826)  SCSI-3 Fibre Channel Protocol (SCSI-FCP)  Fibre Channel Tape (FC-TAPE) Profile  SCSI Fibre Channel Protocol-2 (FCP-2)  Second Generation FC Generic Services (FC-GS-2)  Third Generation FC Generic Services (FC-GS-3)  iSCSI (RFC3720)

, and ESX®.

SN0054671-00 B 1-3

Page 30

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)

Temperature Ranges (for Altitude >900 m or 2952.75 ft)

Temperature Gradient Maximum

10°C to 55°C

(50°F to 131°F)

10°C to n°C

(50°F to n°F

10°C 20°C

–40°C to 65°C

(–40°C to 149°F)

)

–40°C to 65°C

(–40°F to 149°F)

per 60 Min.

Humidity Percent Ranges—Noncondensing

Humidity Gradient Maximum

20% to 80%

(Max. Wet bulb temper-

ature= 29°C)

10% 10%

5% to 95%

(Max. Wet bulb temper-

ature= 38°C)

per 60 Minutes

Altitude Ranges—Low Limits –15.2m (–50 ft) –15.2m (–50 ft)

Altitude Ranges—High Limits 3,048m (10,000 ft) 10,668m (35,000 ft)

Airborne Contaminants—ISA-71

Level

200LFM is required to operate at this temperature.

Use the following formulas to calculate the maximum operating temperature (in °C) for a specific

altitude. Use the first formula if the altitude is stated in meters and the second formula if the altitude is stated in feet.

Use the following formulas to calculate the maximum operating temperature (in °F) for a specific

altitude. Use the first formula if the altitude is stated in meters and the second formula if the altitude is stated in feet.

Maximum corrosive contaminant levels measured at =50% relative humidity; see Table 3 in

ISA-71.04-1985.

1-4 SN0054671-00 B

Page 31

1–Product Overview

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.

Multi-boot Image for 10Gb Converged Network Adapter—CNA Function Configuration Utility

This section contains the following information:

 “Operating System Support” on page 1-5

 “Multi-boot Package Contents” on page 1-5

 “Converged Network Adapter Function Configuration Package Contents” on

page 1-6

 “Using QLflash” on page 1-6

 “Updating the Multi-boot Code” on page 1-6

 “QLflash Command Line Options” on page 1-7

 “Adapter Configuration Utility” on page 1-8

Operating System Support

This multi-boot code supports DOS, Windows Server® 2008; Solaris x86; and Linux on IA32, AMD64, and Intel for OS information.

Multi-boot Package Contents

The multi-boot package for 8200 and 3200 Series Adapters is a compressed file that contains the 82xx/32xx BIOS, UEFI, PXE, and firmware. This package also includes the QLflash application.

x64-based systems. Refer to the Readme file

SN0054671-00 B 1-5

Page 32

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.bin—Combined binary file, which includes the binaries for the

BIOS, UEFI, PXE, and firmware.

Using QLflash

QLflash is a native DOS utility. Refer to the Readme file for more information. To run this utility, boot to a DOS hard drive or USB removable drive.

Utility Version:

/VER = Display version of the QLflash utility

Help Options:

/? = Help menu

Updating the Multi-boot Code

To write the multi-boot code to Flash memory:

1. Insert the QLogic Adapter in the system.

2. Boot to DOS.

3. Run the update script at the command prompt:

C:\>update.bat

This script program updates the multi-boot image on the adapter.

4. Reboot the system.

NOTE:

You can also use the QConvergeConsole (QCC) GUI/CLI to flash the multi-boot image. After the multi-boot code is updated, power cycle the server for the new changes to take effect.

1-6 SN0054671-00 B

Page 33

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. Use of QLflash will modify the way your adapter operates, and it must be used with extreme caution.

Certain features (that is, the NVRAM options) may require additional data.

Files and passwords are not provided in this file.

QLflash Options

QLflash.exe <1...N | ALL> [options]

/SLT

SLT: Sets the application to silent mode

Use application return code for success or failure

1–Product Overview

/SIL=filename.ext

SIL: Load multiflash image from file

/PRV | /VPP | /PRN

PRV: Print firmware versions

VPP: Print VPD contents

PRN: Print MAC addresses and worldwide port name (WWPN)

/CFU=filename.ext | /CFS=filename.ext | /CFC=filename.ext

CFU: Flash board configuration from file

CFS: Save board configuration file (need template file BRDCFG.DAT)

CFC: Compare board configuration to a binary file

/NVU=filename.ext | /NVS=filename.ext | /NVC=filename.ext

NVU: Flash NVRAM from file

NVS: Save NVRAM to file (need template file NVRAM.DAT)

NVC: Compare Flash to NVRAM file

/UIL=filename.ext | /UIS=filename.ext | /UIC=filename.ext

UIL: Flash user information data from file

UIS: Save user information data to file

UIC: Compare user information data to a binary file

SN0054671-00 B 1-7

Page 34

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.

Adapter Configuration Utility

NOTE:

The CNA Function Configuration utility does not run on SUN™ SPARC systems.

This section provides detailed configuration information for advanced users who want to customize the configuration of the 8200 and 3200 Series Adapters and the connected devices. You can configure the adapters using the CNA Function Configuration utility.

To access the CNA Function Configuration utility, press ALT+Q during the adapter initialization (it may take a few seconds for the menu to appear). If you have more than one adapter, the utility will ask you to select the adapter you want to configure. After changing the settings, the utility reboots your system to load the new parameters.

CAUTION!

If the configuration settings are incorrect, your adapter may not function properly.

Upon entering the CNA Function Configuration utility, the following selections are available from the Setup Menu/Function Configuration menu:

 “Type” on page 1-9  “MinBW%” on page 1-9  “Protocol” on page 1-9  “Restore to Non-NIC Partition Settings” on page 1-9  “Exit the CNA Function Configuration Utility” on page 1-9

1-8 SN0054671-00 B

Page 35

Type

MinBW%

Protocol

1–Product Overview

Multi-boot Image for 10Gb Converged Network Adapter—CNA Function Configuration

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.

Enter to specify the percentage of bandwidth allocated to the function. The combined MinBW% values for a port’s functions cannot exceed 100 percent.

The Protocol parameter applies only to only function 0 and function 1.

 PXE—PXE will be supported on the NIC.

Adapter Settings

Press the ENTER key on the Function number to access Adapter Settings, and to configure PXE Boot.

PXE. The following settings are available when Protocol is set to PXE:

 Setup Menu Wait Time (0–15: the default is 5 seconds)

Specifies the time in seconds the menu will wait.

 Enable PXE Boot (Enabled/Disabled: Default—Disabled)

Enter to toggle between Enabled and Disabled. Use the Enable PXE Boot option to attempt a PXE boot on the selected function.

Restore to Non-NIC Partition Settings

Press the ENTER key to restore the NIC partition settings.

Exit the CNA Function Configuration Utility

Press the ENTER key to select from the following:

 Reboot System  Return to Fast!UTIL

SN0054671-00 B 1-9

Page 36

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 Plug-in” on page 1-15  “Removing the QLogic Adapter vCenter Plug-in” on page 1-15  “Installing the Flash Utility” on page 1-15  “Updating the Flash” on page 1-16  “Using the vCenter Plug-in on a Tomcat Server” on page 1-17  “Plug-in Unregistration from a Manual Installation” on page 1-19  “Launching the Plug-in from vSphere Client” on page 1-20

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. vSphere Client Showing QLogic Adapter Tab

1-10 SN0054671-00 B

Page 37

Requirements

The QLogic Adapter vCenter Plug-in requires the components in Figure 1-2 to be installed and running.

1–Product Overview

Installing the QLogic Adapter vCenter Plug-in for ESX/ESXi

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 Adapter with firmware and driver  QLogic Adapter CIM Provider

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

SN0054671-00 B 1-11

Page 38

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.

This section provides the following installation procedures for the CIM Provider:

 Initial Installation  Subsequent Update Installation

Initial Installation

To install the QLogic Adapter CIM Provider using the esxupdate command (ESX systems only):

1. Copy the offline-bundle.zip file into the root directory (/) of the ESX system.

2. Issue the esxupdate command as follows:

# cd /

# esxupdate --bundle offline-bundle.zip --nodeps –nosigcheck

--maintenancemode update

To install the QLogic Adapter CIM Provider from a remote host using the vSphere CLI vihostupdate command (ESXi systems only):

NOTE:

To update the provider from a remote host using the vihostupdate command, make sure that the ESXi system is in maintenance mode. To put the ESXi host in maintenance mode using vSphere Client, select Inventory, select Host, and then select Enter Maintenance Mode.

1. Copy the offline-bundle.zip file to any location on the host where either the vSphere CLI package is installed or the vSphere Management Assistant (vMA) is hosted.

2. Navigate to the location of the offline-bundle.zip file.

3. Issue the vihostupdate command to install the offline bundle as follows:

# vihostupdate.pl <conn_options> --install --bundle offline-bundle.zip --nosigcheck

For available options, refer to the vihostupdate page.

1-12 SN0054671-00 B

Page 39

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:

ttp://www.vmware.com/support/developer/vcli/

Subsequent Update Installation

To update the QLogic Adapter CIM Provider after a prior VIB installation:

1. Follow the instructions in “Removing the QLogic Adapter CIM Provider” on

page 1-13 to remove the existing VIB.

2. Follow the instructions in “Initial Installation” on page 1-12 to install the new VIB.

Starting the QLogic Adapter CIM Provider

1–Product Overview

After a system startup, the Small Footprint CIM Broker (SFCB) CIM object manager (CIMOM) in the ESX system should start automatically and load the QLogic Adapter CIM Provider when necessary.

For ESX systems, you can also manually stop, start, or restart the SFCB CIMOM by issuing the following commands.

To stop the SFCB CIMOM and the QLogic Adapter CIM Provider:

# /etc/init.d/sfcbd-watchdog stop

To start the SFCB CIMOM and the QLogic Adapter CIM Provider:

# /etc/init.d/sfcbd-watchdog start

To restart the SFCB CIMOM and the QLogic Adapter CIM Provider:

# /etc/init.d/sfcbd-watchdog restart

After starting the SFCB CIMOM, use a CIM client utility to query the QLogic Adapter CIM Provider for information.

Removing the QLogic Adapter CIM Provider

To remove the QLogic Adapter CIM Provider, use either the esxupdate or vihostupdate command.

SN0054671-00 B 1-13

Page 40

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. Remove the existing VIB as follows:

# esxupdate remove -b <vibID>

To uninstall from a remote host using the vihostupdate command:

NOTE:

To uninstall the provider from a remote host using the vihostupdate command, make sure that the ESX/ESXi system is in maintenance mode. To put the ESX/ESXi host in maintenance mode using vSphere Client, select Inventory, select Host, and then select Enter Maintenance Mode.

1. From a console on the host where the vSphere CLI package is installed or vMA is hosted, query to find the Bulletin ID of the existing provider:

# vihostupdate.pl <conn_options> --query\

For example, the Bulletin ID may have a format similar to the following:

ESX/ESXi 4.0: QLGC_NIC_PROVIDER-ESX-4.0.0-qlogic-nic-provider-x.x.x ESX/ESXi 4.1: QLGC_NIC_PROVIDER-ESX-4.1.0-qlogic-nic-provider-x.x.x

where x.x.x is the version number of the existing provider.

2. Remove the existing VIB as follows:

# vihostupdate.pl <conn_options> --remove --bulletin <bulletinID>

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/

1-14 SN0054671-00 B

Page 41

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.

 If you start and connect the vSphere Client directly to an ESX/ESXi

server, the vCenter plug-in does not open.

 If you have not already done so, create a data center and add the ESX

server.

4. In the left pane, select the IP address of the VMware server.

5. In the right pane, click the QLogic Adapter tab to view the Web page.

The vCenter plug-in retrieves the adapter information from the server.

1–Product Overview

NOTE:

If the server does not have the QLogic Adapter CIM Provider and adapters installed, or if the vCenter Plug-in installation and registration was not successful, the QLogic Adapter tab is not shown.

Removing the QLogic Adapter vCenter Plug-in

To remove the QLogic Adapter vCenter Plug-in:

1. In the Windows Control Panel, select Add or Remove Programs.

2. In the Add or Remove Programs dialog box, select the QLogic Adapter vCenter Plug-in, and then click Change/Remove.

3. Follow the instructions in the QLogic Adapter vCenter Plug-in installer to remove the plug-in.

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.

SN0054671-00 B 1-15

Page 42

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.

Updating the Flash

NOTE:

For ESX systems, before you perform a Flash update on a QLogic Adapter using the vCenter Plug-in, ensure that the QLflash utility is also installed. Follow the instructions in the Installing the Flash Utility section.

To update the Flash from the QLogic Adapter vCenter Plug-in:

1. Follow the instructions in “Starting the QLogic Adapter vCenter Plug-in” on

page 1-15 to start the vCenter plug-in.

2. In the left pane of the QLogic Adapter page, select the adapter, and then click the Update Adapter Flash Image link.

3. In the Select Flash File for Update dialog box, click Browse.

4. In the Choose File to Upload dialog box, select the .bin Flash file from the extracted Flash kit package that is compatible with your adapter, and then click Open.

5. In the Select Flash File for Update dialog box, click Send.

6. Verify the current Flash version and file version, and then click OK to continue the update.

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-16 SN0054671-00 B

Page 43

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.

Using the vCenter Plug-in on a Tomcat Server

VMware requires that all vCenter plug-ins are web-based applications hosted on a Tomcat Server, which can be downloaded and installed on Linux and Windows systems. Here is a link to Tomcat:

http://tomcat.apache.org/

1–Product Overview

The QLogic vCenter Plug-in supports Tomcat 5, 6, and 7. The installer dynamically detects the Tomcat version and installs accordingly.

This section provides the following procedures for using the vCenter Plug-in on a Tomcat Server:

 “Installing Tomcat on Linux” on page 1-17  “Starting and Stopping Tomcat on Linux” on page 1-18  “Installing Tomcat on Windows” on page 1-18  “Starting and Stopping Tomcat on Windows” on page 1-18

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

SN0054671-00 B 1-17

Page 44

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.sh

To stop Tomcat, issue the following command:

# $CATALINA_HOME/bin/shutdown.sh

Installing Tomcat on Windows

To install Tomcat on a Windows OS:

1. Go to either of the following URLs:

http://tomcat.apache.org/download-60.cgi

http://tomcat.apache.org/download-70.cgi

2. Locate the following directory and file:

Binary Distribution > Core > 32-bit/64-bit Windows Service Installer

3. To install the Tomcat service, get the 32-bit/64-bit Windows Service Installer, save it, and run it.

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 <version number>.

2. Right-click, and then select Start /Stop to initiate Tomcat service, or select Stop to halt the Tomcat service.

1-18 SN0054671-00 B

Page 45

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. On the Introduction window, click Next.

4. On the Please Wait window, wait while the QLogic Adapter vCenter Plug-in is configured for your system.

5. On the Choose Install Folder window, either accept the default installation directory, or click Choose to specify a different folder.

6. Click Install to install files to the installation directory specified in the previous step.

1–Product Overview

A progress window shows the status of the installation.

7. On the User Input window, type your vCenter Server IP address, username, and password, as well as the IP address of your local Tomcat Server. Then click Next to continue.

8. On the Please Wait window, wait while the QLogic Adapter vCenter Plug-in is configured for your system and registers the plug-in with the vCenter Server.

9. On the Registration Result window, click Finish to complete the plug-in installation.

Plug-in Unregistration from a Manual Installation

If you have performed a manual installation of the vCenter plug-in, you must perform a manual uninstall before running the vCenter installation wizard.

VMware provides two type of scripts for vCenter plug-in registration:

For Windows PowerShell

http://communities.vmware.com/docs/DOC-4521

For Perl:

http://communities.vmware.com/docs/DOC-4530

scripting:

SN0054671-00 B 1-19

Page 46

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. After you download and install the SDK and the registration script, follow the VMware instructions to register the vCenter Plug-in.

For example, the Perl unregister command is:

perl registerPlugin.pl --server="127.0.0.1"

-username="administrator" --password="password"

--key="com.qlogic.QLogicAdapterVIPlugIn" --action="remove"

3. Replace the username and password with the correct information to log into the vCenter Server.

Launching the Plug-in from vSphere Client

To launch the plug-in from vSphere client:

1. Start the vSphere Client and connect to the vCenter Server. (If you start and connect the vSphere Client directly to an ESX or ESXi server, the vCenter plug-in does not appear.)

2. If you have not already done so, create a data center and add the ESX server.

3. In the left pane, select the server.

A row of tabs appear in the right pane. If the server has QLogic Adapter CIM Provider and adapters installed, and if the vCenter plug-in installation and registration were successful, the QLogic Adapter tab appears in the tab row.

4. Click the QLogic Adapter tab to view a web page.

1-20 SN0054671-00 B

Page 47

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.

Packaging Content

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Inbox Driver Update Readme file for information.

Linux OS Support

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Inbox Driver Update Readme file for information.

Supported Features

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Inbox Driver Update Readme file for information.

Using the Driver

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Inbox Driver Update Readme file for information on installing the driver, removing the

driver, and driver system parameters.

Installing NIC in ESX/ESXi

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Driver for ESX/ESXi Readme file for information.

SN0054671-00 B 2-1

Page 48

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.

Using the Driver

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter Networking Driver for ESX/ESXi Readme file for information on installing and

removing the driver.

Installing NIC in Windows

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter NDIS Miniport Driver for Windows Readme file for information.

Packaging Content

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter NDIS Miniport Driver for Windows Readme file for information.

Windows OS Support

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter NDIS Miniport Driver for Windows Readme file for information.

Using the Driver

Refer to the Intelligent Ethernet Adapter and Converged Network Adapter NDIS Miniport Driver for Windows Readme file for information on installing and

removing the driver.

2-2 SN0054671-00 B

Page 49

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.

2–Configuring NIC

Configuring PXE Boot

Figure 2-1. Dell BIOS: Integrated Devices

3. Set the Embedded NIC1 and NIC2 option to Enabled.

4. Set the Embedded NIC1 option to Enabled with PXE.

5. Press the ESCAPE key twice, and then select Save changes and exit.

The system reboots.

6. (Optional) During POST, press the CTRL+Q keys to enter the QLogic 8200 Series / 3200 Series CNA Function Configuration window.

SN0054671-00 B 2-3

Page 50

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

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-4 SN0054671-00 B

Page 51

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. Select the Boot Sequence option, and then press the ENTER key.

SN0054671-00 B 2-5

Page 52

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.

Configuring Driver Software Parameters

Linux NIC Driver Management Applications

Overview

The following sections describe how to configure and manage the driver and adapter using Linux management utilities.

Viewing and Changing Adapter Properties on Linux

Use the following Linux utilities to view and change adapter properties:

 “qaucli Utility” on page 2-7  “ethtool Utility” on page 2-7

2-6 SN0054671-00 B

Page 53

qaucli Utility

2–Configuring NIC

Configuring Driver Software Parameters

Install QConvergeConsole CLI (qaucli) from the following packages supplied by QLogic:



QConvergeConsoleCLI-<version>_linux_<arch>.install.tar.gz—

Package file



QConvergeConsoleCLI-<version>_<arch>.rpm—RPM installer

package file

Example RPM Package Installation

To determine if QCC is installed and to find the full name of the installed QCC RPM package, issue the following command using the partial name

QConvergeConsoleCLI as an argument to grep:

rpm –qa | grep QConvergeConsoleCLI

1. To check for an older version of the RPM package, issue the following command:

ethtool Utility

rpm –qa QConvergeConsoleCLI

2. If an older version is found, erase that version by issuing the following command:

rpm –e QConvergeConsoleCLI

3. To install the new version, issue the following command:

rpm –ihv QConvergeConsoleCLI-1.0.00-04.i386.rpm

The utility is installed in the

/opt/QLogic_Corporation/QConvergeConsoleCLI directory.

Use the ethtool utility to view adapter statistics and configure interface options. For additional details, refer to qlcnic driver man page and ethtool man page.

Examples

To disable transmit segmentation offload, issue the following command, where

[n] represents a numerical value for a specific instance:

ethtool -K eth[n] tso off

To list interface statistics, issue the following command, where [n] represents a numerical value for a specific instance:

ethtool –S eth[n]

SN0054671-00 B 2-7

Page 54

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.

Sample Output 2

Ethtool eth8

Settings for eth8:

Supported ports: [ TP FIBRE ]

Supported link modes:

Supports auto-negotiation: No

Advertised link modes: 10000baseT/Full

Advertised auto-negotiation: No

Speed: 10000Mb/s

Duplex: Full

Port: FIBRE

PHYAD: 1

Transceiver: external

Auto-negotiation: off

Supports Wake-on: g

Wake-on: g

Current message level: 0x00000000 (0)

Link detected: yes

2-8 SN0054671-00 B

Page 55

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. On the adapter properties dialog box, click the Advanced tab to bring that page to the front.

4. On the Advanced page, configure the parameters specified in the Ta bl e 2 -1 .

5. (Optional) Click other tabs to bring those pages to the front and view or change settings, for example:

2–Configuring NIC

 Click the Information tab to view the configuration.

 Click the Details tab to view NIC driver details. On the Details page,

click items under Property to view the selected item's value.

 Click the Driver tab to update, rollback, disable, or uninstall the NIC

driver.

 Click the Resource tab to view resource settings.

 Click the Statistics tab to view the transmit and receive (general and

QLogic-customized) statistics gathered while the NIC is operational.

6. When you are through viewing and changing driver properties, click OK to close the dialog box, or click Cancel to revert to the previous driver configuration.

Table 2-1. Windows Driver Configurable Parameters

Property Description

Completion Queue Size Specifies the size for the ring where command com-

pletion and incoming receive indication status will be posted.

Registry Key: CompletionQueueSize Default: 16384 Value s: 1024, 2048, 4096, 8192, 16384,

32768

SN0054671-00 B 2-9

Page 56

2–Configuring NIC QLogic Device Windows Property Pages

Table 2-1. Windows Driver Configurable Parameters (Continued)

Property Description

Flow Control Sets the hardware flow control parameters.

Health Monitoring Checks health of firmware, monitors normal opera-

Interrupt Moderation Allows interrupt coalescing during receive and trans-

Registry Key: *FlowControl Default: Rx and Tx Enabled Value s: Disabled, Rx Enabled, Tx Enabled,

Rx and Tx Enabled

tion, and ensures recovery of the firmware.

mit operation. Registry Key: *InterruptModeration Default: Disabled Value s: Enabled, Disabled

IPv4 Checksum Offload Enables and disables IPv4 checksum offload.

Registry Key: *IPChecksumOffloadIPv4 Default: Rx and Tx Enabled. Value s: Disabled, Rx and Tx Enabled, Rx

Enabled, Tx Enabled

Large Receive Offload Enables and disables TCP large receive offload.

Enables collapsing of multiple MTU size TCP packets into bigger segments before handing these over to the host.

Registry Key: LRO Default: Enabled Value s: Enabled, Disabled

Large Send Offload V1 IP4 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 them on the wire.

Registry Key: *LsoV1IPv4 Default: Enabled. Value s: Enabled, Disabled Size of LSO v1: 64K

2-10 SN0054671-00 B

Page 57

2–Configuring NIC

QLogic Device Windows Property Pages

Table 2-1. Windows Driver Configurable Parameters (Continued)

Property Description

Large Send Offload V2 IP4 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.

Registry Key: *LsoV2IPv4 Default: Enabled Value s: Enabled, Disabled Size of LSO v2: 128K

Large Send Offload V2 IP6 Enables and disables TCP large send offload. Allows

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.

Registry Key: *LsoV2IPv6 Default: Enabled Value s: Enabled, Disabled Size of LSO v2: 128K

Locally Administered Address Defines the locally administered address (LAA) that

users and administrators can set on this interface. This address overrides the permanent address of the QLogic adapter (that may have been Flashed into the hardware).

Registry Key: NetworkAddress Format: Hexadecimal Options: Value (a value is required, enter the 12 hex

bytes of the MAC address to be used), or not present.

Max Ethernet Frame Size Specifies the Ethernet frame size for packet transmis-

sion and receipt (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)

SN0054671-00 B 2-11

Page 58

2–Configuring NIC QLogic Device Windows Property Pages

Table 2-1. Windows Driver Configurable Parameters (Continued)

Property Description

Max Jumbo Buffers Specifies the number of jumbo-sized receive buffers

Number of Receive Buffers Specifies the number of buffers allocated for receiving

Number of Transmit Buffers Specifies the number of stage buffers used by the

allocated for the jumbo ring (not frame). Reg Key: RxJumboRingSize Default: 4096 Value s: 1024, 2048, 4096, 8192

standard MTU size (1514 byte) packets. Registry Key: *ReceiveBuffers Value s: 1024, 2048,4096,8192,16384,32768 Default: 16384

driver during transmit. Registry Key: *TransmitBuffers Value s: 1024, 2048, 4096 Default: 1024

Priority & VLAN Tag Enables and disables support for 802.1pQ priority

tagging. This property must be enabled to set the VLAN ID.

Registry Key: PQTagging Default: Priority & VLAN Enabled Value s: Priority & VLAN Enabled; Prior-

ity & VLAN Disabled; Priority Disabled, VLAN Enabled; Priority Enabled, VLAN Disabled

Receive Side Scaling Enables and disables the RSS feature.

Registry Key: RSS Default: Enabled Value s: Enabled, Disabled

Receive Side Scaling Rings Specifies the number of RSS rings used.

Registry Key: MaxStatusRings Default: 2 Value s: 1-4

2-12 SN0054671-00 B

Page 59

2–Configuring NIC

QLogic Device Windows Property Pages

Table 2-1. Windows Driver Configurable Parameters (Continued)

Property Description

TCP Checksum Offload IPv4 Enables and disables the TCP transmit and receive

checksum offload. Registry Key: *TCPChecksumOffloadIPv4 Default: Rx and Tx Enabled Value s: Disabled, Rx Enabled, Tx Enabled,

Rx and Tx Enabled

TCP Checksum Offload IPv6 Enables and disables the TCP transmit and receive

checksum offload. Registry Key: *TCPChecksumOffloadIPv6 Default: Rx and Tx Enabled Value s: Disabled, Rx Enabled, Tx Enabled,

Rx and Tx Enabled

UDP Checksum Offload IPv4 Enables and the disables the user datagram protocol

(UDP) transmit and receive checksum offload. Registry Key: *UDPChecksumOffloadIPv4 Default: Rx and Tx Enabled Value s: Disabled, Rx Enabled, Tx Enabled,

Rx and Tx Enabled

UDP Checksum Offload IPv6 Enables and disables the UDP transmit and receive

checksum offload. Registry Key: *UDPChecksumOffloadIPv6 Default: Rx and Tx Enabled Value s: Disabled, Rx Enabled, Tx Enabled,

Rx and Tx Enabled

VLAN ID for Setting If the Priority and VLAN Tag is enabled, this parame-

ter specifies a VLAN ID for this interface (also exposed through the standard object identifier (OID)).

Registry Key: VlanId Default: 0 (no VLAN) Range: 0-4094

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.

SN0054671-00 B 2-13

Page 60

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.

VLAN Configuration

VLAN Configuration with QCC GUI

Refer to the QConvergeConsole Help System: Setting Advanced NIC Port Parameters for information.

VLAN Configuration with the QCC Interactive CLI

Refer to the appropriate section in the QConvergeConsole CLI User's Guide for information.

VLAN Configuration with the QCC Non-Interactive CLI

Refer to the appropriate section in the QConvergeConsole CLI User's Guide for information.

Teaming/Bonding

Windows Teaming

You can group together multiple network adapters in a server to make a team. Individual adapters that are part of a team operate as a team rather than standalone adapters. A team provides traffic load balancing across the member adapters and fault tolerance when some, but not all, of the members lose connectivity.

To enable teaming functionality, install the teaming driver in addition to the basic NIC.

2-14 SN0054671-00 B

Page 61

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). Make sure any provided LAA is unique for the local Ethernet network. This provision gives the system administrator more flexibility in configuring the MAC address for a team when necessary.

Teaming Modes

Teaming is designed to improve reliability and fault tolerance of networks and to enhance performance by efficient load balancing.

The following NIC teaming modes are provided:

 Failsafe Mode ensures that an alternate standby or redundant adapter

becomes active if the primary network connection fails.

 Switch Independent Load-Balancing Mode ensures distribution of

transmit loads across the teamed adapters.

2–Configuring NIC

Teaming/Bonding

 Link Aggregation Modes (802.3ad static, 802.3ad dynamic (active and

passive link aggregation control protocol [LACP])) enables the use of multiple adapters together as a single, virtual adapter with the aggregated capacity of its individual adapters.

All team types—failsafe, switch-independent load balancing, and link aggregation—can be heterogeneous as well as homogeneous. Every team must have at least one QLogic Adapter.

Table 2-2 shows that failsafe and transmit load-balancing modes are switch

independent, which means they do not require switch configuration. LACP or

802.3ad require switch ports configured for LACP.

Table 2-2. Windows Teaming Modes

Mode

Failsafe Yes: Layer 2 No Yes No 2–16

Transmit load

balancing

Failover

Capability

Yes No Yes Yes: Layers

Switch

Dependency

System Fault

Tolerance

(SFT)

Load

Balancing

3 or 4

Number of

Ports per Team

(Range

2–16

)

SN0054671-00 B 2-15

Page 62

2–Configuring NIC Teaming/Bonding

Table 2-2. Windows Teaming Modes (Continued)

System Fault

Tolerance

(SFT)

Load

Balancing

Mode

Static

Failover

Capability

Yes Ye s Yes Yes 2–16

Switch

Dependency

802.3ad

Dynamic

802.3ad

16×16 ports can be aggregated per system: 16 ports per team and 16 teams per system.

Yes Yes Yes Yes 2–16

Failsafe Mode

The failsafe mode provides Layer 2 fault tolerance. Failsafe provides high reliability through redundancy in the event of port failure. When the primary network connection is down, data traffic is automatically transferred to a secondary, standby connection. The preferred primary adapter can be specified either by the system administrator or by the teaming driver (if the admin does not select the preferred adapter). When the teaming driver needs to make the selection, it selects the best adapter in terms of bandwidth, health, and capability. The preferred primary must always be a QLogic Adapter.

The administrator can also choose one of the following failback types to specify the behavior when connection to the preferred primary is restored after a period of failure:

Number of

Ports per Team

(Range

)

 None—When the preferred primary becomes operational again, the driver

does not automatically switch back the primary to the active adapter.

 Preferred Primary—When the preferred primary becomes operational

again, the driver automatically switches back the primary as the active adapter. The network traffic resumes to the primary adapter from the standby adapter. The traffic stays with the secondary adapter only as long as the primary adapter is down.

 Auto Select—Use this option to enable the teaming driver to automatically

select the best adapter based on parameters such as bandwidth, link state, health, and so on.

In failsafe mode, the standby adapter could be dissimilar in the individual features supported and capacity, and may come from a different vendor.

All the adapters in the team share a common team MAC address. This is either a locally administered MAC address or a default MAC address specified by the driver. Only one adapter at a time in the team is active for network traffic. No two same MAC addresses are exposed to the switch at the same time.

2-16 SN0054671-00 B

Page 63

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. Traffic load balancing is connection-based to avoid out-of-order packet delivery. The administrator can select one of the following load distribution types:

 Auto Select indicates that the load is distributed based on the target IP

address (IPv4 or IPv6) and port number. This option ensures a one-to-one correspondence between a traffic flow and a team adapter.

 MAC address based indicates that the load is distributed based on the

target MAC address.

In switch-independent load balancing, a team receives the traffic on the preferred primary adapter. If the preferred primary adapter fails, the receive load switches to a secondary adapter (failover operation). If the preferred primary adapter becomes operational again, the receive load fails back to the preferred primary adapter (failback operation). Thus, a switch-independent load balancing team also behaves like a failsafe team. Each time the preferred primary changes due to failover or failback, other network elements are notified of the change in the primary adapter through team gratuitous address resolution protocols (ARPs).

Link Aggregation Mode

link aggregation provides increased bandwidth and high reliability by combining several NICs into a single, logical, network interface called a link aggregation group (LAG). The link aggregation is scalable, meaning an adapter can be added or deleted either statically or dynamically from a team.

Traffic from all the team ports that form a LAG have the same MAC address, which is the MAC address of the team. If a new adapter joins the LAG, or an adapter forming the LAG fails, the LAG becomes operational again after a brief exchange of protocols between the switch and the server. QLogic Adapters are rapidly aggregated, with a latency of 1 to 2 seconds.

Two options are available in the link aggregation mode:

 Static link aggregation  Dynamic link aggregation

NOTE:

The switch must support the IEEE 802.3ad standard for the preceding two link aggregation modes to work.

SN0054671-00 B 2-17

Page 64

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 aLAG.

In SLA mode, the protocol stack responds to ARP requests with a single, advertised MAC address, and an IP address corresponding to the LAG. Each physical adapter in the team uses the same team MAC address during transmission. As the switch (at the other end of link) is aware of the trunking teaming mode, it appropriately modifies the forwarding table to indicate the trunk as a single virtual port. This modification ensures correct traffic routing on the receive side as well. In this mode, the switch also distributes receive traffic across the member adapters.

Dynamic Link Aggregation (DLA)

Dynamic link aggregation (DLA) with LACP is similar to SLA except that LACP allows self configuration of LAG through handshaking between the switch and the intermediate driver. For the team to function, LACP must be enabled at both ends of the link: the server and the switch. LACP (802.3ad dynamic) allows switch ports to dynamically communicate with the teaming driver, allowing controlled addition and removal of ports from the team.

Link aggregation mode has transmit load balancing and fail safety support. If a link connected through a participant port of a link-aggregated team goes down, LACP provides failover and load balancing across the remaining members of the team. In addition, if a new member port is added to the team or is removed from the team, the switch performs load rebalancing for the receive operation and the driver performs load balancing for the transmit operation, to accommodate the change in configuration.

Transmit load distribution in LACP provides the following options:

 None indicates no traffic distribution. Only a single “active” adapter is used

for transmit. The driver selects the active adapter based on LACP state information.

 Auto Select indicates that the load is distributed based on the target IP

address and port number. This option ensures a one-to-one correspondence between a traffic flow and a team adapter.

 MAC address based indicates that the load is distributed based on the

target MAC address.

2-18 SN0054671-00 B

Page 65

Using the CLI for Teaming

You can view, create, configure, and delete teams using the QConvergeConsole CLI utility.

To view a list of teams, issue the following command:

qaucli -nic –teamlist

To view team information, issue the following command:

qaucli -nic -teaminfo <team_inst|ALL>

To preview available ports before configuring a new team, issue the following command:

qaucli -nic -teamnew_portspreview

To configure a new team, issue the following command:

qaucli -nic -teamnew <team_type> <port_insts|ALL>

2–Configuring NIC

Teaming/Bonding

where port_insts are the ports indices separated by commas (for example, 1,2)

team_type is either 1=Fail Over or 2=Load Balanced.

and

To delete a team, issue the following command:

qaucli -nic -teamdel <team_inst|ALL>

Using the Team Management GUI

Use the Team Management property page to manage the following teaming-related activities:

 Viewing network topology  Creating, modifying, and deleting teams  Viewing and changing team properties  Adding and deleting virtual adapters

To open the Team Management property page:

1. In Windows, access the Computer Management dialog box, and then click Device Manager in the left pane.

2. Under Network adapters, right-click the QLogic 10Gigabit Ethernet adapter, and then select Properties.

SN0054671-00 B 2-19

Page 66

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. Team Management Property Page

On the Team Management page, the Teams and Adapters pane on the left lists the network devices currently present on this system, including:

 Teams and virtual adapters, as well as their member physical adapters  QLogic and other vendor adapters

Teaming Configuration

Teaming configuration includes creating, modifying, and deleting teams, and viewing team statistics on the Team Management property page. To launch the Team Management property page, see “Using the Team Management GUI” on

page 2-19.

2-20 SN0054671-00 B

Page 67

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

2–Configuring NIC

Teaming/Bonding

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. Team names must be unique on a system.

SN0054671-00 B 2-21

Page 68

2–Configuring NIC Teaming/Bonding

3. 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.3ad dynamic

option, you must also select one of the following options:

 Active LACP: LACP is a Layer 2 protocol that controls the

teaming of physical ports into an aggregated set. LACP discovers if a host’s ports are connected to a switch that supports aggregation on the connected ports and configures those ports into an aggregation bundle. For LACP to operate, one side has to be Active LACP. The Active LACP side of the protocol initiates the protocol.

 Passive LACP: The Passive LACP side responds to the active

LACP requests.

 Adapters to Add—Select the check box next to each adapter that

should form the team.

 Use default MAC Address—Select this check box to have the driver

assign a MAC address, or clear the check box to select a locally-administered MAC address from the list.

 Select Preferred Primary Adapter—Choose a preferred primary

adapter for the team from the list of teamed adapters, or None to allow the driver to assign the preferred primary adapter.

 Failback Type—If this is a Failsafe Team, select a failback type of

None, Auto Select, or Preferred Primary.

 Load Balancing Type—If this is an 802.3ad Static Team or 802.3ad

Dynamic Team, select the type of load balancing: Auto, MAC Address Based, or None.

 Distribution Type—If this is a Switch Independent Load Balancing

team type, select a distribution type of either Auto Select or MAC Address Based.

 Advanced—Click this button to configure QLogic-specific team

capabilities such as RSS, MTU, or various offloads. These properties configure the member adapters to avoid any conflict after a team has been created.

2-22 SN0054671-00 B

Page 69

2–Configuring NIC

Teaming/Bonding

Figures 2-7 through 2-10 show the configuration of various teaming modes.

Figure 2-7. Creating a Failsafe Team

SN0054671-00 B 2-23

Page 70

2–Configuring NIC Teaming/Bonding

Figure 2-8. Creating a Switch-Independent Load Balancing Team

2-24 SN0054671-00 B

Page 71

2–Configuring NIC

Teaming/Bonding

Figure 2-9. Creating an 802.3ad Static Team

SN0054671-00 B 2-25

Page 72

2–Configuring NIC Teaming/Bonding

Figure 2-10. Creating an 802.3ad Dynamic Team

2-26 SN0054671-00 B

Page 73

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. Confirming New Team Creation

Modifying a Team

A team can be modified by:

 Adding or removing one or more team members to a team.  Modifying the team properties.

SN0054671-00 B 2-27

Page 74

2–Configuring NIC Teaming/Bonding

To add team members:

1. On the Team Management property page, right-click the unteamed adapter

2. On the shortcut menu, point to Add to Team, and then click the team to

NOTE:

to add to a team.

which you want to add the adapter (Figure 2-12).

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. Adding a Team

2-28 SN0054671-00 B

Page 75

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. If an adapter is no longer required to be a member of a team, it can be removed from the team.

To change a team property:

For the VLAN and teaming solution to work correctly, the properties of all teamed adapters and adapters with multiple VLANs must remain synchronized with the team properties. Ensure that you change the properties of a team and an adapter with VLANs only on the Team Management page.

1. On the Team Management page, in the right pane under Team Data, expand the Properties list.

2. Double-click the team property you need to change.

3. In the Advanced Team Properties dialog box (Figure 2-13), specify a new property value, and then click OK.

Figure 2-13. Modifying Advanced Team Properties

SN0054671-00 B 2-29

Page 76

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. If an adapter property becomes out of sync with its team properties, change either the team or adapter property so that they are the same on each, and then reload the team. To reload a team: On the Team Management page, in the left pane under Teams and Adapters, right-click the team name, and then click Reload Team.

2-30 SN0054671-00 B

Page 77

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.

SN0054671-00 B 2-31

Page 78

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. Modifying Failsafe Team Properties

2-32 SN0054671-00 B

Page 79

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. On the Team Management property page, in the left pane under Teams and Adapters, right-click the team name to be deleted.

2. On the shortcut menu, click Delete team.

SN0054671-00 B 2-33

Page 80

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. On the shortcut menu, click Save to File.

3. Enter a location to save the configuration.

To restore a configuration:

1. On the Team Management page under Teams and Adapters, right-click the Teams folder.

2. On the shortcut menu, click Restore From File.

3. Select a previously saved configuration file.

Viewing Teaming Statistics

You can view teaming and Ethernet statistics using the QConvergeConsole (QCC) CLI utility.

To view teaming statistics, issue the following command:

qaucli -nic -statport

To reset the Ethernet statistics counter, issue the following command:

qaucli -nic -sreset [cna_port_inst]

To display Ethernet port statistics, issue the following command:

qaucli -nic -statport [cna_port_inst]

To undo the reset of Ethernet statistics counters, issue the following command:

qaucli -nic -sunreset [cna_port_inst]

Linux Bonding/Failover/Aggregation

The Linux qlcnic driver supports all the standard bonding modes supported by the Linux bonding driver for bonding, failover, and aggregation. Refer to the Linux bonding driver documentation for additional details on the bonding modes.

2-34 SN0054671-00 B

Page 81

Using LACP on 8200 Series Adapters for Windows

NOTE:

This feature is available only on Cisco

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. Open the Server Manager and select Diagnostics > Device Manager > Network Adapters.

3. Right-click the first QLogic 10 Gigabit Ethernet CNA device and select Properties from the context menu (Figure 2-39).

4. Click the Team Management tab.

systems (Cisco FCoE switch).

2–Configuring NIC

Teaming/Bonding

5. In Teams and Adapters, click Teams, and then click Custom Settings.

The Teaming custom settings dialog box displays (Figure 2-17).

Figure 2-17. Enabling LACP

6. Select the Allow 802.3as team over CNA check box, and then click OK.

The network must be configured to a Cisco-supported configuration, as described in the following paragraphs. This information is from the Cisco support forum thread, https://supportforums.cisco.com/thread/2071713

SN0054671-00 B 2-35

Page 82

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. LACP Configuration with Two vPCs

An vFC cannot be bound from a server with multiple links in the same Nexus 5x00.

2-36 SN0054671-00 B

Page 83

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. Invalid LACP Configuration (Two vPCs Linked Separately to Two

Nexus 5x00s)

SN0054671-00 B 2-37

Page 84

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.com/en/US/docs/switches/datacenter/nexus5000/sw/fcoe/ 502_n1_1/Cisco_n5k_fcoe_config_gd_re_502_n1_1.pdf

 Cisco Nexus 5000 Series CLI Reference Manual

NIC Partitioning (NPAR)

NIC Partitioning (NPAR) provides the ability to create multiple physical functions on the PCIe bus that share a single physical port. Each physical function is a PCI endpoint (PCIe) that can have a device driver attached to it.

The NPAR feature in 8200 and 3200 Series Adapters allows you to partition a single 10GbE NIC port into up to four individual partitions with user-configurable bandwidth and interface type (personality). The partitioning options are not limited to NIC as the name NPAR indicates; it extends to converged fabric partitioning by enabling you to assign iSCSI or FCoE protocols to certain partitions.

For example, each partition can be either native Ethernet NIC, or configured to support iSCSI or FCoE storage devices with different PCIe endpoint device class code. Both iSCSI and FCoE operate in full hardware offload mode.

The QLogic NPAR solution is OS and switch agnostic, which means NPAR does not require a proprietary switch to operate; however, the adapter does require the OS-specific QLogic adapter driver for each supported protocol (NIC, iSCSI, and FCoE). It also means NPAR bandwidth allocation can regulate only transmit traffic (not receive traffic).

After you have configured the NIC partitions as desired on the 8200 and 3200 Series Adapters’ ports, you must reboot the server for the personality changes to take effect.

You can modify the minimum and maximum bandwidth for each NPAR. The changes take effect immediately without rebooting the server. The minimum and maximum bandwidths are specified as percentages of the link bandwidth, where:

 Minimum bandwidth is the minimum bandwidth guaranteed to a partition.

 Maximum bandwidth is the maximum value that a partition is permitted to

use.

2-38 SN0054671-00 B

Page 85

Setup Requirements

Table 2-3 and Ta bl e 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 Platforms

2–Configuring NIC

NIC Partitioning (NPAR)

Linux

 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

Windows

 XenServer® 6.0 and later

 Windows Server 2008 SP2, Windows Server 2008 R2

SP1

 Hyper-V

For the latest list of operating systems that support NPAR for QLogic Adapters, please check

http://driverdownloads.qlogic.com.

If a partitioned NIC is configured for use in a Hyper-V network virtualization stack, virtual message

queue (VMQ) must be enabled. To enable VMQ on a management OS with physical network adapters less than 10Gbps, enter the following command in a command prompt window: reg add

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VMSMP\Parameters /v BelowTenGigVmqEnabled /t REG_DWORD /d 1 /f

® a

Table 2-4. NPAR Management Tool and Driver Requirements

SW Components Description

Management Tools

QLogic OptionROM Flash image containing firmware and boot code

QLogic QConvergeConsole GUI/CLI

QLogic Device Windows Properties Page

Management tools that can be utilized for NPAR configuration and management

Can be used for NPAR configuration and management in Windows

Drivers

Adapter drivers NIC, FCoE, and iSCSI drivers

Management tools and drivers are located on the QLogic Web site

http://driverdownloads.qlogic.com

SN0054671-00 B 2-39

Page 86

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.

In addition to defining NPAR, this section describes:

 “NIC Partitioning Options” on page 2-40  “Personality Changes” on page 2-41  “Quality of Service” on page 2-42  “eSwitch” on page 2-43  “Configuration Management Tools” on page 2-44

NIC Partitioning Options

The NPAR feature in 8200 and 3200 Series Adapters provides the ability to create multiple PCIe physical functions for each physical 10 GbE port on the adapter. Each PCIe function appears as an independent interface to the host operating system or hypervisor.

When the 8200 and 3200 Series Adapters are configured as Ethernet-only, each adapter contains eight Ethernet functions.

By default, NPAR functionality is disabled on the adapters, having only two Ethernet functions enabled. Depending on the feature personality mapping supported on the adapter, you can enable additional Ethernet or storage functions.

The PCI function number assignment is as follows:

 Functions 0 and 1 are always NIC, function 0 for port 0 and function 1 for

port 1; any of the other functions can be individually enabled or disabled.

 NIC, iSCSI, and FCoE have fixed function numbers.

 Functions 2 and 3 can only be NIC personalities.

 Functions 4 and 5 can be iSCSI or NIC personalities.

 Functions 6 and 7 can be FCoE or NIC personalities.

 You can configure only one iSCSI and one FCoE personality for each

physical port.

The 8200 and 3200 Series Adapters support a maximum of 64 Layer-2 MAC address filters across all partitions, which limits the number of virtual network adapters that can be created on a partitioned NIC. The NIC driver evenly distributes the number of filters across all NIC partitions.

For example, if the NIC adapter has four NIC partitions, two NIC partitions per physical port, then each NIC partition gets 16 filters (64/4 = 16). In this case, do not create more than 16 virtual network adapters on any NIC function that is configured to be used by a Hyper-V network virtualization stack.

2-40 SN0054671-00 B

Page 87

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. NPAR Default Function Settings

Personality Changes

Based on your operating environment, you can use your preferred management tool to change or disable PCI functions on either physical port. Using this feature lets you divide each physical port into up to four partitions, configured to support one of the following PCI function types: NIC, FCoE, or iSCSI.

NOTE:

Throughout this section, the terms personality and function type are used interchangeably.

SN0054671-00 B 2-41

Page 88

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

Only one iSCSI and/or FCoE function per physical port. NIC, iSCSI, and FCoE have fixed function numbers. Functions 2–7 can be independently disabled.

Quality of Service

Quality of service (QoS) refers to the bandwidth allocation assigned to each partition used to send and receive data between the adapter port and connected devices.

Function Type

0 NIC 0 Always present. Always

1 NIC 1

2 NIC 0 NIC or disabled

3NIC 1

4 iSCSI/NIC 0 iSCSI, NIC, or disabled

5 iSCSI/NIC 1

6 FCoE/NIC 0 FCoE, NIC, or disabled

7 FCoE/NIC 1

Physical Port

Number

Notes

NIC. Cannot be disabled.

Each physical port on the 8200 and 3200 Series Adapters can send and receive data at up to 10Gbps in both directions at the same time. When the physical port is partitioned into four partitions, the port bandwidth is divided between each port partition according to traffic demands.

You can set QoS for each port partition by setting minimum and maximum percentages of the physical port's bandwidth for each partition. This feature helps guarantee a transmission rate for each partition that requires a particular bandwidth to run critical applications using port partitions. The setting for a given QoS can resolve bottlenecks that exist when virtual machines (VMs) contend for port bandwidth.

Enhanced transition selection (ETS) controls the actual bandwidth allocation at the network port. The bandwidth allocation under ETS is typically 50 percent for FCoE traffic and 50 percent for Non-FCoE traffic (NIC and iSCSI). Therefore, NPAR QoS allocations among the NIC partitions for a given port allocate a percentage of the Non-FCoE portion of the bandwidth.

2-42 SN0054671-00 B

Page 89

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.

To ensure that iSCSI has more than 1 percent of bandwidth available in high-utilization conditions, set the total NPAR QoS minimum bandwidth settings so that they equal less than 100 percent.

Example

 An NPAR enabled port has two NIC partitions, one iSCSI partition, and one

FCoE partition.

 ETS allocates 50 percent of the network bandwidth to FCoE traffic and

50 percent to non-FCoE traffic.

 The NPAR QoS minimum bandwidth setting for each NIC partition is

50 percent.

eSwitch

This setting means that each NIC partition is guaranteed 50 percent of 50 percent of 10Gb, or 2.5Gb each.

 If at any time the FCoE partition is using 5Gb of bandwidth and each NIC

partition is using 2.5Gb, then the iSCSI partition is left with only 50Mb of bandwidth.

 If, however, the NIC partitions each allocated 45 percent of the non-FCoE

traffic, then the total allocated bandwidth would be 90 percent.

 The remaining 10 percent (or 500 Mb) would then be effectively

reserved for the iSCSi partition.

The 8200 and 3200 Series Adapters support embedded switch (eSwitch) functionality, which provides a basic VLAN-aware Layer-2 switch for Ethernet frames. Each physical port has one instance of an eSwitch, which supports all NPARs on that physical port.

The eSwitch operation is transparent and the administrator does not need to perform any specific configuration. The ability to view eSwitch statistics depends on your operating environment and management tool.

The QLogic drivers download the VM MAC addresses to the firmware, which enables the firmware and hardware to switch the packets destined for VMs on the host.

For traffic to flow from one eSwitch to another, it must first pass through an external switch or have been forwarded by a VM that has a path through both eSwitches.

SN0054671-00 B 2-43

Page 90

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 OptionROM at POST

The QLogic OptionROM is flashed on the 8200 and 3200 Series Adapters at the factory. When you first start the server that contains 8200 and 3200 Series Adapters, the power-on self test (POST) starts. Running the POST test gives you access to the OptionROM utility.

For procedures on setting up NPAR and eSwitch parameters using the OptionROM while powering up the host server, see “QLogic OptionROM at POST”

on page 3-10.

QConvergeConsole (QCC) GUI

The QConvergeConsole unified adapter Web management interface is a web-based client/server application that allows for centralized management and configuration of QLogic adapters within the entire network (LAN and SAN).

On the server side, the QConvergeConsole runs as an Apache Tomcat Server web application. After the application is launched on the web server, you can connect to the QConvergeConsole's GUI through a browser, either locally on the server or remotely from another computer. Your browser window becomes the client used to connect to servers that host the 8200 and 3200 Series Adapters and connected storage devices within the network.

In addition to the configuration and management tools available through the QConvergeConsole GUI, the QCC enables you to partition and configure NIC ports and eSwitch parameters on 8200 and 3200 Series Adapters.

Follow the procedures in the QConvergeConsole User’s Guide to install the application on a Windows or Linux server. Before using the QCC GUI to configure NPAR on your 8200 and 3200 Series Adapters, you must also install the drivers on the server where the 8200 and 3200 Series Adapters reside.

2-44 SN0054671-00 B

Page 91

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

 Make sure the remote agents are running on the Tomcat Server where the

QCC GUI application resides:

 Fibre Channel/FCoE (  NIC (  iSCSI (

netqlremote)

iqlremote)

qlremote)

For help using the QCC GUI, use the help system, available through the QCC GUI browser-based menu option Help > Browse Contents.

For procedures on setting up NPAR and eSwitch parameters using the QCC GUI, see “QConvergeConsole (QCC) CLI” on page 3-21.

QConvergeConsole (QCC) CLI

QConvergeConsole (QCC) CLI is a management utility that centralizes management and configuration of QLogic adapters within the entire network (LAN and SAN).

QCC manages iSCSI, Ethernet, and FCoE functions on 8200 and 3200 Series Adapters installed in a Linux or Windows environment.

In addition to the configuration and management capabilities available through the QConvergeConsole CLI, the QCC CLI enables you to partition and configure NIC ports and eSwitch parameters on 8200 and 3200 Series Adapters.

Follow the procedures for your operating system in the QConvergeConsole CLI User’s Guide to install the application on the host server.

For command references needed while using QCC CLI, refer to the

QConvergeConsole CLI User’s Guide.

Before using QCC CLI to configure NPAR on your 8200 and 3200 Series Adapters, you must install the OS-specific drivers on the server where the 8200 and 3200 Series Adapters reside. You can use the QLogic SuperInstaller for your host server’s operating system (Windows or Linux) to install the Fibre Channel/FCoE, NIC, and iSCSI drivers. To download the drivers, go to

http://driverdownloads.qlogic.com

For procedures on setting up NPAR and eSwitch parameters using the QCC CLI, see “QConvergeConsole (QCC) CLI” on page 3-21.

SN0054671-00 B 2-45

Page 92

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.

For procedures on using this native server management tool on a Windows Server to configure NPAR on the 8200 and 3200 Series Adapters’ NIC ports, see

“Windows Device Manager” on page 3-27.

NPAR Setup and Management Options

This section describes how to configure NIC partitions (NPARs) on 8200 and 3200 Series Adapters installed in a host server within a SAN. Procedures for establishing quality of service (QoS) for each partition and viewing the eSwitch parameters and statistics are included.

This section provides setup procedures using the following management tools:

Overview

 “QLogic OptionROM at POST” on page 2-47  “QConvergeConsole (QCC) GUI” on page 2-51  “QConvergeConsole (QCC) CLI” on page 2-55  “QLogic Device Windows Properties Page” on page 2-60

NOTE:

These procedures assume you have either local or remote access to a host server with at least one installed 8200 and 3200 Series Adapter, as well as the necessary drivers and management tools.

Depending on your operating environment and preferred system management techniques, you can use any of the tools described in this section to set up NIC partitions (NPARs) on 8200 and 3200 Series Adapters’ ports to meet your system’s networking requirements.

When you first start the server that contains the 8200 and 3200 Series Adapters, the power-on self test (POST) starts. Running POST gives you access to one of the configuration tools you can use to set up NIC partitions on 8200 and 3200 Series Adapters’ ports: QLogic OptionROM.

2-46 SN0054671-00 B

Page 93

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.

On Windows host servers, you can use the QLogic Device Windows Properties Page to set up and manage NIC partitions (for more information, see “QLogic

Device Windows Properties Page” on page 2-60).

QLogic OptionROM at POST

When you first start the host server that contains 8200 and 3200 Series Adapters, the power-on self test (POST) starts. Running the POST test gives you access to the OptionROM utility.

To set up NPAR using OptionROM:

1. When the screen prompts you to enter the setup menu (Figure 2-23) during the POST test, press Ctrl+Q to enter the OptionROM setup.

2–Configuring NIC

NIC Partitioning (NPAR)

Figure 2-23. POST Test Screen Prompt to Enter Setup Menu

SN0054671-00 B 2-47

Page 94

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-48 SN0054671-00 B

Page 95

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. Selecting iSCSI Function Type to Change

SN0054671-00 B 2-49

Page 96

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. Adjusting the Minimum Bandwidth

2-50 SN0054671-00 B

Page 97

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).

2–Configuring NIC

NIC Partitioning (NPAR)

Figure 2-29. Saving Configuration Changes

6. Reboot the host server after completing NPAR configuration.

QConvergeConsole (QCC) GUI

The QConvergeConsole is a web-based client/server application that allows for centralized management and configuration of QLogic adapters within the entire network (LAN and SAN). On the server side, QConvergeConsole runs as an Apache Tomcat Server web application. After the application is launched on the web server, you can connect to QConvergeConsole's GUI through a browser, either locally on the server or remotely from another computer. Your browser window becomes the client used to connect to servers that host the 8200 and 3200 Series Adapters and connected storage devices within the network.

You can use QCC GUI to configure and manage 8200 and 3200 Series Adapters installed on either Linux or Windows host servers.

SN0054671-00 B 2-51

Page 98

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. Set Up Quality of Service (QoS)

Configure NIC Partitions

You can use QCC to configure and manage NPAR functions for both physical ports through the NIC Partitioning tab, available only on Port 1. You can enable or disable NPAR functions on either physical port and must reboot the operating system to apply the changes. When the NPAR function is enabled, each physical port divides its bandwidth PCIe functions, configured to support one of the following function types: NIC, FCoE, or iSCSI. QCC represents each function type as a personality.

function between four physical functions or physical

For tables that show the default NPAR function settings, as well as the possible configurations, see “NPAR Setup” on page 2-68.

Table 2-5 shows the port identifications and the possible NPAR configurations.

To configure the NIC partitions and change personalities:

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.

2-52 SN0054671-00 B

Page 99

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. If you want to change its function type, select the NIC partition and select the desired protocol from the Function Type drop-down list.

6. Click Save to save any changes. The Security Check dialog box may appear. In the Enter Password box, type the password, and then click OK.

7. Reboot the operating system to apply the changes.

8. Verify that the configured ports have the most current drivers installed.

9. If necessary, update the driver for the port protocol.

Set Up Quality of Service (QoS)

QConvergeConsole lets you set quality of service (QoS) for each partition by setting minimum and maximum percentages of the physical port's bandwidth for each partition.

SN0054671-00 B 2-53

Page 100

2–Configuring NIC NIC Partitioning (NPAR)

NOTE:

To set the QoS:

1. Expand a 8200 and 3200 Series Adapters node in the QConvergeConsole

2. Expand the physical Port 1 node and select the NIC port. The content pane

3. Select the NIC Partitioning tab, and then click the Management sub-tab.

The NIC Partitioning page applies to NIC ports only for NPAR-enabled 8200 and 3200 Series Adapters.

system tree.

displays two additional tabs that are not available on NIC ports for physical Port 2.

The NIC Partitioning Management General page displays configuration details that apply to the selected NPAR (Figure 2-31).

Figure 2-31. NIC Partitioning—General Management Page

4. Click the down arrow and select the NIC partition (NPAR0, NPAR1, NPAR2, or NPAR3) from the drop-down list.

Information and configuration fields related to the selected NIC partition include:

 Default MAC Address. The MAC address set at the manufacturer.

 Location. The logical location in the system: PCI bus number, device

number, and function number.

2-54 SN0054671-00 B