Qlogic QLE2740L-DEL, QLE2740-DEL, QLE2742-DEL, QLE2742L-DEL User Manual

Download

Page 1

User’s Guide

Fibre Channel Adapter

QLE2740-DEL, QLE2740L-DEL,

QLE2742-DEL, and QLE2742L-DEL

BK3254601-00 C

Third party information brought to

you courtesy of Dell EMC.

Page 2

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

This document is provided for informational purposes only and may contain errors. QLogic reserves the right, without notice, to make changes to this document or in product design or specifications. QLogic disclaims any warranty of any kind, expressed or implied, and does not guarantee that any results or performance described in the document will be achieved by you. All statements regarding QLogic's future direction and intent are subject to change or withdrawal without notice and represent goals and objectives only.

Document Revision History

Revision A, March 21, 2016

Revision B, April 19, 2016

Revision C, February 1, 2017

Changes Sections Affected

Updated the supported OSs:  Added a note stating that the OSs listed in this

guide may be more current than those listed in the Dell Update Packages Version xx.xx.xxx User’s Guide.

 For Windows, added support for Windows

Server 2016.

 For Linux, added support for Linux RHEL 7.3,

removed support for RHEL 7.1, changed RHEL

6.6 to RHEL 6.8, and changed SLES 12 SP0 to SLES 12 SP2.

 For VMware, added support for VMware ESXi

6.5 and removed support for ESXi 6.0, ESXi 5.5 U3, and ESXi 5.5 U2.

Added a reference to the Dell Update Packages Version xx.xx.xxx User’s Guide as a prerequisite.

Deleted the “Installation Options” section. Added a reference to the Dell Update Packages Version xx.xx.xxx User’s Guide, “Windows CLI Options” section.

Changed the section title from “Installing the ESXi

5.5 and 6.0 Fibre Channel Driver” to reflect changed OS support.

“Supported Operating Systems” on page xv

“Running the Dell Update Package in the GUI” on page 5

“Running the Dell Update Package from the Command Line” on page 11

“Installing the ESXi 6.5 and 6.0 U2 Fibre Channel Driver” on page 17

Changed the section title from “Updating an Existing Driver or Installing a New Driver for an Existing ESXi 5.5 or 6.0 Installation with esxcli” to reflect changed OS support.

In the second bullet, changed the VMware reference from “ESXi 5.5 and 6.0” to “ESXi 6.5 and 6.0 U2”.

“Updating an Existing Driver or Installing a New Driver for an Existing ESXi 6.5 or 6.0 U2 Installation with esxcli” on page 17

“Installation Package Contents” on page 19

ii BK3254601-00 C

Page 3

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

In the introductory paragraph, changed the environment reference from “ESXi 5.5 and ESXi 6.0” to “ESXi 6.5 and ESXi 6.0 U2”.

Changed the section title from “Installing the CIM Provider on an ESXi 5.5 or 6.0 Host”.

 In Step 1, changed from “ESXi 5.5” to “ESXi

6.5”

 In the note, changed from “ESXi 6.0” to “ESXi

6.0 U2”

Added a reference to the Dell Update Packages Version xx.xx.xxx User’s Guide,“Using Dell Update Packages” section.

In Table 3-10, for the ESXi Driver row, changed from “ESXi 6.0” to “ESXi 6.0 U2”.

In the introduction, added the “FEC is mandatory when operating at 32Gb line rate...” paragraph.

“Installing the QLogic Adapter CIM Provider” on page 26

“Installing the CIM Provider on an ESXi 6.5 or 6.0 U2 Host” on page 27

“Running the Firmware Update by Double-Clicking” on page 33

“Brocade Fabric Features” on page 92

“Enabling QLogic Forward Error Correction” on page 94

iii BK3254601-00 C

Page 4

Introduction

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

User’s Guide Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Functionality and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Citrix XenServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

1 Hardware Installation

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

PCIe Bus Slot Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installing the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Connecting to the SAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Driver Installation and Configuration

Windows Driver Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . 4

Running the Dell Update Package in the GUI . . . . . . . . . . . . . . . . . . . 5

Running the Dell Update Package from the Command Line. . . . . . . . 11

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Linux Driver Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing the Linux Fibre Channel Driver. . . . . . . . . . . . . . . . . . . . . . . 12

Building the Driver for RHEL 6.x and 7.x . . . . . . . . . . . . . . . . . . 13

Building the Driver for SLES 11 . . . . . . . . . . . . . . . . . . . . . . . . . 14

Building the Driver for SLES 12 . . . . . . . . . . . . . . . . . . . . . . . . . 15

iv BK3254601-00 C

Page 5

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

VMware Driver Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . 16

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing the ESXi 6.5 and 6.0 U2 Fibre Channel Driver. . . . . . . . . . . 17

Updating an Existing Driver or Installing a New Driver for

an Existing ESXi 6.5 or 6.0 U2 Installation with esxcli . . . . . . . 17

Verifying the Version of the Installed Driver . . . . . . . . . . . . . . . . 18

Installing QConvergeConsole VMware vCenter Server Plug-in . . . . . 18

Installation Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing QConvergeConsole VMware vCenter Server Plug-in

Plug-in Unregistration from a Manual Install. . . . . . . . . . . . . . . . 25

Uninstalling the QConvergeConsole VMware vCenter

Server Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing the QLogic Adapter CIM Provider . . . . . . . . . . . . . . . . 26

Uninstalling the QLogic Adapter CIM Provider . . . . . . . . . . . . . . 29

Installing QConvergeConsole VMware vSphere Web Client Plug-in. . 30

Uninstalling the QConvergeConsole VMware vCenter

Server Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

. . 19

3 Fibre Channel Configuration

Updating the Dell Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Running the Firmware Update by Double-Clicking . . . . . . . . . . . . . . . 33

Running the Firmware Update from the Command Line. . . . . . . . . . . 35

Using Fast!UTIL for Custom Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Adapter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Selectable Boot Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Restore Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Raw NVRAM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Advanced Adapter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Scan Fibre Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Fibre Disk Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Loopback Data Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Select Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Exit Fast!UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Setting Fibre Channel Adapter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setting Fibre Channel Adapter Parameters with

QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setting Fibre Channel Adapter Parameters with Interactive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setting Fibre Channel Adapter Parameters with Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

v BK3254601-00 C

Page 6

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

Configuring Target Persistent Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring Persistent Binding with QConvergeConsole GUI. . . . . . . 44

Configuring Persistent Binding with Interactive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring Persistent Binding with Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring Boot Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring Boot Devices with QConvergeConsole GUI. . . . . . . . . . . 46

Configuring Boot Devices with Interactive QConvergeConsole CLI . . 46 Configuring Boot Devices with Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Boot Devices with the BIOS. . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Virtual Ports (NPIV). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring NPIV with QConvergeConsole GUI . . . . . . . . . . . . . . . . . 47

Configuring NPIV with Interactive QConvergeConsole CLI. . . . . . . . . 47

Configuring NPIV with Noninteractive QConvergeConsole CLI . . . . . 47

Configuring NPIV Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting QoS by Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting QoS by Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring Fibre Channel Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Fibre Channel Driver Parameters with

QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Fibre Channel Driver Parameters with Interactive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Fibre Channel Driver Parameters with Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Fibre Channel Driver Parameters with

QConvergeConsole VMware vCenter Server Plug-in. . . . . . . . . . . . 54

Configuring Selective LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring OoOFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring OoOFR with QConvergeConsole GUI . . . . . . . . . . . . . . . 55

Configuring OoOFR with Interactive QConvergeConsole CLI. . . . . . . 55

Configuring OoOFR with Noninteractive QConvergeConsole CLI . . . 56

Configuring the UEFI Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Setting an FA-PWWN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Setting the FA-PWWN from the Adapter . . . . . . . . . . . . . . . . . . . . . . . 63

Setting FA-PWWN with QConvergeConsole GUI. . . . . . . . . . . . 64

Setting FA-PWWN with QConvergeConsole CLI . . . . . . . . . . . . 65

Setting FA-PWWN with QConvergeConsole VMware Plug-ins . 67

vi BK3254601-00 C

Page 7

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

Setting the FA-PWWN from the Brocade Switch. . . . . . . . . . . . . . . . . 67

Setting the FA-PWWN from the Switch . . . . . . . . . . . . . . . . . . . 67

Setting the Static FA-PWWN from the Switch. . . . . . . . . . . . . . . 68

Configuring and Verifying FA-BLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuring FA-BLD from the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . 68

Enabling Host Bus Adapter Port BIOS and Fabric-assigned

Boot LUN with QConvergeConsole GUI . . . . . . . . . . . . . . . . . 68

Configuring the Adapter and Boot Devices with

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring a Zone in a Brocade Switch . . . . . . . . . . . . . . . . . . 71

Verifying that FA-BLD is Operational. . . . . . . . . . . . . . . . . . . . . . . . . . 72

Adapter Side Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Using a Fabric-Assigned Boot LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Using a Fabric-Assigned Boot LUN in QConvergeConsole GUI. . . . . 74

Using a Fabric-Assigned Boot LUN in Interactive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Using a Fabric-Assigned Boot LUN with Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Using a Fabric-Assigned Boot LUN with QConvergeConsole

Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Running Diagnostics—Fibre Channel Ping and Trace Route . . . . . . . . . . . 76

Pinging and Viewing Trace of Routing Using Topology Map. . . . . . . . 76

Running a Fibre Channel CT Ping Test. . . . . . . . . . . . . . . . . . . . . . . . 77

Running a Fibre Channel CT Ping from

QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Running a Fibre Channel CT Ping from

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Running a Fibre Channel CT Ping from

QConvergeConsole VMware Plug-ins . . . . . . . . . . . . . . . . . . . 79

Fibre Channel Trace Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring CS_CTL QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

CS_CTL QoS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Enabling CS_CTL QoS Mode for the Initiator and Target Ports . . . . . 82

Verifying and Confirming CS_CTL Mode Setup for Each Port . . . . . . 82

Creating a Virtual Port from the Adapter’s Port in

QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Setting the QoS Priority Level for a Virtual Port in

QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configuring End-to-End CS_CTL QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configuring CS_CTL QoS on the Switch. . . . . . . . . . . . . . . . . . . . . . . 85

Configuring CS_CTL QoS on the Storage Device. . . . . . . . . . . . . . . . 86

vii BK3254601-00 C

Page 8

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

Configuring End-to-End CS_CTL QoS (continued)

Changing the QoS Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Changing the Priority Levels in Windows . . . . . . . . . . . . . . . . . . 86

Changing the Priority Levels in VMware ESXi . . . . . . . . . . . . . . 88

Configuring FDMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Brocade Switch FOS CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Brocade Fabric Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

FDMI Enhancements Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Enabling QLogic Forward Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . 94

FEC Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Enabling QLogic FEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Running Extended Link Service Commands . . . . . . . . . . . . . . . . . . . . . . . . 96

Link Cable Beacon Extended Link Service Command . . . . . . . . . . . . 96

Read Diagnostic Parameters Extended Link Service Command . . . . 96

A Troubleshooting

Fibre Channel Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Fibre Channel Diagnostics Using QConvergeConsole GUI . . . . . . . . 98

Fibre Channel Diagnostics Using Interactive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Fibre Channel Diagnostics Using Noninteractive

QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Fibre Channel Troubleshooting Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Troubleshooting with a Diagnostic Port (D_Port) . . . . . . . . . . . . . . . . . . . . . 102

Configuring D_Port on a Brocade Fibre Channel 16G or 32G Switch Checking D_Port Results from a Brocade Fibre Channel 16G or

32G Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Verifying D_Port Mode with QConvergeConsole GUI . . . . . . . . . . . . . 105

Verifying D_Port Mode with Interactive QConvergeConsole CLI . . . . 106

Verifying D_Port Mode with Noninteractive QConvergeConsole CLI

Verifying D_Port Mode with QConvergeConsole Plug-ins. . . . . . . . . . 107

B Specifications

Physical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Standards Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

. . 103

. . 106

viii BK3254601-00 C

Page 9

User’s Guide—Fibre Channel Adapter QLE274x-DEL and QLE274xL-DEL

C QConvergeConsole GUI

Introduction to QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Downloading QConvergeConsole Documentation. . . . . . . . . . . . . . . . . . . . 111

Downloading and Installing Management Agents . . . . . . . . . . . . . . . . . . . . 111

Installing the Agents from the QLogic Web Site . . . . . . . . . . . . . . . . . 112

Installing the Agents Using the Built-in Agent Installer . . . . . . . . . . . . 112

Installing QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2

Installing QConvergeConsole in a Windows Environment . . . . . . . . . 113

Installing QConvergeConsole in a Linux Environment . . . . . . . . . . . . 114

Installing QConvergeConsole in Silent Mode . . . . . . . . . . . . . . . . . . . 115

What Is in the QConvergeConsole Help System . . . . . . . . . . . . . . . . . . . . . 115

D Regulatory Information

Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Regulatory and Compliance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Laser Safety, FDA Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Agency Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

EMI and EMC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Product Safety Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

ix BK3254601-00 C

Page 10

Introduction

NOTE

This user’s guide covers the following products:

 QLogic

bracket

 QLogic QLE2740L-DEL single-port, low profile adapter with a low profile

bracket

 QLogic QLE2742-DEL dual-port, low profile adapter with a full-height

bracket

 QLogic QLE2742L-DEL dual-port, low profile adapter with a low profile

bracket

Throughout this document, the term adapter refers to any or all of these products.

This guide provides technical information about the adapters, including how to install and configure the adapter, as well as detailed descriptions of the adapter’s various uses and functions.

QLE2740-DEL single-port, low profile adapter with a full-height

Intended Audience

This guide is intended for system administrators and other technical staff members responsible for configuring and managing adapters installed on Dell PowerEdge® servers in Windows®, Linux®, or VMware® environments.

User’s Guide Content

This guide provides information in the following chapters and appendices:

 Chapter 1 Hardware Installation covers the hardware and software

requirements, safety precautions, a pre-installation checklist, PCI Express

(PCIe connecting it to the network.

 Chapter 2 Driver Installation and Configuration covers the installation of the

drivers included with the adapter on Windows, Linux, and VMware OSs.

) slot considerations, and procedures for installing the adapter and

x BK3254601-00 C

Page 11

Introduction

NOTE

Related Materials

 Chapter 3 Fibre Channel Configuration provides information about the

multiboot image (Fibre Channel Adapter Function Configuration Utility) and instructions for setting Fibre Channel Adapter parameters; persistent binding; configuring the boot device, N_Port ID virtualization (NPIV), and driver parameters; and reassembling out-of-order frames.

 Appendix A Troubleshooting provides information about Fibre Channel

diagnostics and a Fibre Channel troubleshooting diagram.

 Appendix B Specifications defines the physical characteristics and power

requirements and lists supported standards, interface, and environmental specifications.

 Appendix C QConvergeConsole GUI provides an overview of the

QConvergeConsole Web management interface.

 Appendix D Regulatory Information provides warranty, regulatory, and

compliance information.

Related Materials

For additional information, refer to the following QLogic documents:

 QConvergeConsole Help, available through QConvergeConsole GUI,

provides help topics on configuring and managing host servers and adapters using QConvergeConsole GUI.

 Installation Guide—QConvergeConsole GUI (part number SN0051105-00)

contains instructions for installing and starting QConvergeConsole GUI.

 User’s Guide—QConvergeConsole CLI (part number SN0054667-00)

provides specific command line use in both interactive and noninteractive modes.

 User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part

number SN0054677-00) provides reference material on using the QConvergeConsole VMware vCenter Server Plug-in and the QConvergeConsole VMware vSphere Web Client Plug-in.

To access QLogic documents, go to www.qlogic.com and click Downloads.

xi BK3254601-00 C

Page 12

Introduction

NOTE

CAUTION

Documentation Conventions

This guide uses the following documentation conventions:

 provides additional information.

 without an alert symbol indicates the presence of a hazard

that could cause damage to equipment or loss of data.

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

. For

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

Command Prompt.

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

 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, type

cd /root, and then press the ENTER key.

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

xii BK3254601-00 C

Page 13

Introduction

NOTE

Documentation Conventions

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

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

 QConvergeConsole CLI non-interactive command syntax conventions

include the following:

 Plain text indicates items that you must type as shown. For example:

 < > (angle brackets) indicate a variable whose value you must specify.

 qaucli -pr nic -ei

For example:

 <hba instance>

For CLI commands only, variable names are always indicated using angle brackets instead of italics.

 [ ] (square brackets) indicate an optional parameter. For example:

 [<file_name>] means specify a file name, or omit it to select

the default file name.

 | (vertical bar) indicates mutually exclusive options; select one option

only. For example:

 on|off  1|2|3|4

 ... (ellipsis) indicates that the preceding item may be repeated. For

example:

 x... means one or more instances of x.  [x...] means zero or more instances of x.

 ( ) (parentheses) and { } (braces) are used to avoid logical ambiguity.

For example:

 a|b c is ambiguous  {(a|b) c} means a or b, followed by c  {a|(b c)} means either a, or b c

xiii BK3254601-00 C

Page 14

Introduction Functionality and Features

Functionality and Features

This section provides the following information:

 Functional Description

 Key Features

 Supported Operating Systems

Functional Description

Functional descriptions for the adapters are as follows:

 QLE2740-DEL: A low profile, Gen6 32Gb, single-port Fibre Channel PCIe

adapter with a full-height bracket installed.

 QLE2740L-DEL: A low profile, Gen6 32Gb, single-port Fibre Channel PCIe

adapter with a low profile bracket installed.

 QLE2742-DEL: A low profile, Gen6 32Gb, dual-port Fibre Channel PCIe

adapter with a full-height bracket installed.

 QLE2742L-DEL: A low profile, Gen6 32Gb, dual-port Fibre Channel PCIe

Key Features

Key features of the adapters include:

 Centralized device management for SAN  Connectivity to 32Gb/16Gb/8Gb Fibre Channel networks  PCIe 3.0 x8  Full hardware offload for the Fibre Channel protocol  Message-signaled interrupts (MSI-X) and legacy interrupts (INT-X)  NPIV  Boot from SAN  Several advanced management features for 2700 Series Adapters:

adapter with a low profile bracket installed.

 QConvergeConsole (GUI and CLI) is available if you are running

Windows or Linux.

 QConvergeConsole VMware vCenter Server Plug-in is available if you

are running VMware ESXi.

xiv BK3254601-00 C

Page 15

Introduction

NOTE

Functionality and Features

Supported Operating Systems

Because the Dell Update Packages Version xx.xx.xxx User’s Guide is not updated in the same cycle as this Fibre Channel adapter user’s guide, consider the operating systems listed in this section as the more current.

The adapter supports the following operating systems. To view the most complete and current list, refer to the product release notes.

Windows

 Windows Server® 2016  Windows Server 2012 R2  Windows Server 2012  Windows Server 2008 R2 SP1  Windows Server 2008 SP2 x64  Windows Server 2008 SP2 x32

Linux

 Red Hat® Enterprise Linux (RHEL®) 7.3  RHEL 7.2  RHEL 6.8  RHEL 6.7

 SUSE  SLES 12 SP1  SLES 11 SP4

VMware

 vSphere®: VMware ESXi 6.5  vSphere: VMware ESXi 6.0 U2

Citrix XenServer

 Citrix XenServer 6.5

Linux Enterprise Server (SLES®) 12 SP2

For the most current versions of the OS and drivers supported by the adapter, refer to the release notes file (release.txt).

xv BK3254601-00 C

Page 16

1 Hardware Installation

WARNING

This chapter provides the hardware and software requirements, safety precautions, a pre-installation checklist, PCIe slot considerations, and procedures for installing the adapter and connecting it to the network.

Hardware and Software Requirements

Before you install the adapter, verify that the system meets the following hardware and software requirements.

 Hardware: For QLE274x-DEL Adapters port and slot assignments, refer to

the “Expansion Cards” section of the Hardware Owner’s Manual for your Dell PowerEdge server.

 Software: For information on the supported operating systems, firmware

versions, adapter drivers, and utilities, refer to the product release notes.

Safety Precautions

The adapter is being installed in a system that operates with voltages that can be lethal. Before you open the case of your system, observe the following precautions to protect yourself and to prevent damage to the system components.

For your safety, follow these precautions:

 Remove any metallic objects or jewelry from your hands and wrists.

 Make sure to use only insulated or nonconducting tools.

 Before you touch internal components, verify that the system is powered

OFF and is unplugged.

 Install or remove adapters in a static-free environment. The use of a properly

grounded wrist strap or other personal antistatic devices and an antistatic mat is strongly recommended.

1 BK3254601-00 C

Page 17

1–Hardware Installation

NOTE

Pre-Installation Checklist

1. Verify that your system meets the hardware and software requirements

listed in “Hardware and Software Requirements” on page 1.

2. Verify that your system is using the latest BIOS.

If you acquired the adapter software on a disk or from the Dell support Web site (http://support.dell.com files.

3. Check the adapter for visible signs of damage. Never attempt to install a

damaged adapter.

PCIe Bus Slot Considerations

), verify the path to the adapter driver

The size of the PCIe bus slot in which you install the adapter will affect the speed throughput. Tab le 1 -1 lists the approximate speed throughput for each bus slot size.

Table 1-2 lists the throughput needed to achieve line rates.

Table 1-2. Throughput Requirements to Achieve Line Rate

Number of 32G

FC Ports

Table 1-1. Approximate Speed Throughput per Bus Slot Size

PCIe Generation (Speed) Throughput

Slot Size

x8 slot

x16 slot

x32 slot

Model Number

PCIe Gen1 (2.5 GT/s)

~20Gbps (2.5 8) ~40Gbps (5 8) ~64Gbps (8 8)

~40Gbps (2.5

~80Gbps (2.532) ~160Gbps (5 32) ~256Gbps (832)

16) ~80Gbps (5 16) ~128Gbps (8 16)

PCIe Throughput

Required to Achieve

PCIe 2.0 (5 GT/s) PCIe 3.0 (8 GT/s)

Minimum PCIe Gen and

Line Rate

Slot Configurations

QLE2740-DEL,

QLE2740L-DEL

QLE2742-DEL,

QLE2742L-DEL

32Gbps (132Gbps)

64Gbps (2

2 BK3254601-00 C

32Gbps) PCIe 3.0 x8 and higher

PCIe 2.0 x8 and higher PCIe 3.0 x8 and higher

Page 18

1–Hardware Installation Installing the Adapter

Installing the Adapter

To install the QLE274x-DEL Adapters:

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 bus slot. For more

information about selecting a bus slot, see “PCIe Bus Slot Considerations”

on page 2.

4. Pull out the slot cover (if any).

5. Grasp the adapter by the top edge and seat it firmly into the appropriate slot.

6. Refasten the adapter’s retaining bracket.

7. Close the computer cover.

8. Plug the Fibre Channel cable into the adapter.

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

For more detailed information, refer to the Hardware Owner’s Manual for your Dell PowerEdge server.

Connecting to the SAN

To connect the QLE274x-DEL Adapters to the SAN, refer to the Hardware Owner’s Manual for your Dell PowerEdge server.

3 BK3254601-00 C

Page 19

2 Driver Installation and

NOTE

Configuration

If you need to update the Flash memory of multiple adapters simultaneously:  For QConvergeConsole GUI, refer to the “Update the Flash Using the

Flash Update Wizard” topic in the QConvergeConsole Help.

 For QConvergeConsole CLI, issue the -flashsupport command to

update the Flash memory for all cards supported by the specified file. For example:

qaucli -pr nic -flashsupport -i ALL -a p3p11179.bin

This chapter provides the following information about the drivers included with the adapters:

 “Windows Driver Installation and Configuration” on page 4

 “Linux Driver Installation and Configuration” on page 12

 “VMware Driver Installation and Configuration” on page 16

When you disable the firmware (for example, during a firmware dump or during a firmware update) in Windows or Linux with a QConvergeConsole agent, multiple application messages are generated. These messages are generated because the application cannot communicate with the adapter while the firmware is disabled. After the firmware is re-enabled, the errors will go away.

Windows Driver Installation and Configuration

You can run a software or driver Dell update package in two ways:

 Running the Dell Update Package in the GUI

 Running the Dell Update Package from the Command Line

4 BK3254601-00 C

Page 20

2–Driver Installation and Configuration

NOTE

Windows Driver Installation and Configuration

Running the Dell Update Package in the GUI

Before you begin, refer to the Dell Update Packages Version xx.xx.xxx User’s Guide, “Prerequisites and Features for Systems Running Windows” section.

To run the Dell update package in the GUI:

1. Double-click the icon representing the Dell update package file.

The actual file name of the Dell update package varies.

2. In the Dell Update Package window (Figure 2-1), click Install.

Figure 2-1. Dell Update Package Window

5 BK3254601-00 C

Page 21

2–Driver Installation and Configuration Windows Driver Installation and Configuration

3. In the QLogic Super Installer—InstallShield® Wizard’s Welcome window

(Figure 2-2), click Next.

Figure 2-2. QLogic InstallShield Wizard: Welcome Window

4. In the wizard’s License Agreement window (Figure 2-3 on page 7):

a. Read the QLogic End User Software License Agreement.

b. To continue, select I accept the terms in the license agreement.

6 BK3254601-00 C

Page 22

2–Driver Installation and Configuration Windows Driver Installation and Configuration

c. Click Next.

Figure 2-3. QLogic InstallShield Wizard: License Agreement Window

5. Complete the wizard’s Setup Type window (Figure 2-4) as follows:

a. Select one of the following setup types:

 Click Complete to install all program features.

 Click Custom to manually select the features to be installed.

b. To continue, click Next.

7 BK3254601-00 C

Page 23

2–Driver Installation and Configuration Windows Driver Installation and Configuration

If you selected Complete, proceed directly to Step 6 b.

Figure 2-4. InstallShield Wizard: Setup Type Window

6. If you selected Custom in Step 5, complete the Custom Setup window

(Figure 2-5 on page 9) as follows:

a. Select the features to install. By default, all features are selected. To

change a feature’s install setting, click the icon next to it, and then select one of the following options:

 This feature will be installed on the local hard drive—This

setting marks the feature for installation without affecting any of its subfeatures.

 This feature, and all subfeatures, will be installed on the

local hard drive—This setting marks the feature and all of its

subfeatures for installation.

 This feature will not be available—This setting prevents the

feature from being installed.

8 BK3254601-00 C

Page 24

2–Driver Installation and Configuration Windows Driver Installation and Configuration

b. Click Next to continue.

Figure 2-5. InstallShield Wizard: Custom Setup Window

7. In the InstallShield Wizard’s Ready To Install window (Figure 2-6), click

Install.

Figure 2-6. InstallShield Wizard: Ready to Install the Program Window

9 BK3254601-00 C

Page 25

2–Driver Installation and Configuration Windows Driver Installation and Configuration

The InstallShield Wizard installs the QLogic Adapter drivers and Management Software Installer.

8. When the installation is complete, the InstallShield Wizard Completed

window appears (Figure 2-7). Click Finish to dismiss the installer.

Figure 2-7. InstallShield Wizard: Completed Window

9. In the Dell Update Package window (Figure 2-8 on page 11), “Complete”

indicates successful installation.

 (Optional) To open the log file, click View Log. The log file shows the

progress of the DUP installation, any previous installed versions, any error messages, and other information about the installation.

 To close the Update Package window, click OK.

10 BK3254601-00 C

Page 26

2–Driver Installation and Configuration

NOTE

Windows Driver Installation and Configuration

Figure 2-8. Dell Update Package Window

Running the Dell Update Package from the Command Line

For a list of the CLI options for systems running Windows, a description of each option, and the command syntax, refer to the Dell Update Packages Version xx.xx.xxx User’s Guide, “Windows CLI Options” section.

Running the Dell update package from the command line, with no options specified, results in the same behavior as double-clicking the icon representing the Dell update package.

The actual file name of the Dell update package varies.

To run the Dell update package from the command line:

C:\><DUP_file_name>.EXE

The following shows the syntax for specifying options to customize the Dell update package installation behavior:

<DUP_file_name>.exe [/<option1>[=<value1>]] [/<option2>[=<value2>]]...

To display the GUI for guided installation, update, or extraction, use no options.

Examples

To update the system silently:

<DUP_file_name>.exe /s

To extract the update contents to the C:\mydir\ directory:

<DUP_file_name>.exe /s /e=C:\mydir

11 BK3254601-00 C

Page 27

2–Driver Installation and Configuration

NOTE

Linux Driver Installation and Configuration

To extract the driver components to the C:\mydir\ directory:

<DUP_file_name>.exe /s /drivers=C:\mydir

To install only the driver components:

<DUP_file_name>.exe /s /driveronly

To change from the default log location to C:\my path with spaces\log.txt:

<DUP_file_name>.exe /l="C:\my path with spaces\log.txt"

Linux Driver Installation and Configuration

This section provides the following procedures for installing drivers on a Linux system:

 Installation Overview

 Installing the Linux Fibre Channel Driver

Installation Overview

To install and configure the adapter drivers on a Linux system, refer to the driver release notes, readme, and installation instructions included in the package.

To install the Red Hat Package Manager (RPM), issue the following command as a root user:

rpm -Uvh <rpm name>

For example:

rpm -Uvh qla2xxx-kmp-default-

<driver-version_kernel-version>-<release>.x86_64.rpm

To uninstall the RPM, issue the following command as a root user:

rpm -e <rpm>

For example:

rpm -e qla2xxx-kmp-default-

<driver-version_kernel-version>-<release>

Installing the Linux Fibre Channel Driver

This section provides procedures for installing the Linux Fibre Channel driver for the following operating systems:

 Building the Driver for RHEL 6.x and 7.x

12 BK3254601-00 C

Page 28

2–Driver Installation and Configuration

NOTE

Linux Driver Installation and Configuration

 Building the Driver for SLES 11

 Building the Driver for SLES 12

Building the Driver for RHEL 6.x and 7.x

1. From the directory that contains the source driver file,

qla2xxx-src-vx.xx.xx.xx.06.x-k.tar.gz, issue the appropriate commands for your Linux version.

RHEL 6.x

# tar -xzvf qla2xxx-src-vx.xx.xx.xx.06.x-k.tar.gz

# cd qla2xxx-src-vx.xx.xx.xx.06.x-k

RHEL 7.x

# tar -xzvf qla2xxx-src-vx.xx.xx.xx.07.x-k.tar.gz

# cd qla2xxx-src-vx.xx.xx.xx.07.x-k

2. Build and install the driver modules from the source code by executing the

build.sh script as follows:

# ./extras/build.sh install

The build.sh script does the following:

 Builds the driver .ko files.

 Copies the .ko files to the appropriate /lib/modules/<kernel

version>/extra/qlgc-qla2xxx directory.

 Add the appropriate directive in the modprobe.conf (if applicable).

You can optionally complete either or both Step 3 and Step 4 of this procedure.

3. (Optional) To manually load the driver, issue the insmod or modprobe

command:

 To directly load the driver from the local build directory, issue the

following insmod commands in order:

# modprobe scsi_tgt.ko (if not already loaded)

# modprobe scsi_transport_fc.ko

# insmod qla2xxx.ko

 To load the driver using modprobe, issue the following command:

# modprobe -v qla2xxx

13 BK3254601-00 C

Page 29

2–Driver Installation and Configuration

NOTE

Linux Driver Installation and Configuration

 To unload the driver using modprobe, issue the following command:

# modprobe -r qla2xxx

4. (Optional) To automatically load the driver each time the system boots,

rebuild the RAM disk to include the driver as follows:

a. Create a backup copy of the RAMDISK image by issuing the following

commands:

# cd /boot

# cp initramfs-[kernel version].img initramfs-[kernel

version].img.bak

b. Create the new RAMDISK by issuing the following command:

# dracut -f

c. To load the driver, reboot the host.

Building the Driver for SLES 11

1. From the directory that contains the source driver file,

qla2xxx-src-vx.xx.xx.xx.11.x-k.tgz, issue the following commands:

# tar -xzvf qla2xxx-src-vx.xx.xx.xx.11.x-k.tgz

# cd qla2xxx-x.xx.xx.xx.xx.xx-k4

Where x.xx.xx.xx.xx.xx is the applicable version number.

2. Build and install the driver modules from the source code by executing the

build.sh script as follows:

# ./extras/build.sh install

The build.sh script does the following:

 Builds the driver .ko files.

 Copies the .ko files to the appropriate

/lib/modules/3.x.../updates directory.

 Adds the appropriate directive in the modprobe.conf file (if

applicable).

You can optionally complete either or both Step 3 and Step 4 of this procedure.

14 BK3254601-00 C

Page 30

2–Driver Installation and Configuration

NOTE

Linux Driver Installation and Configuration

3. (Optional) Manually load the driver for Linux.

 Edit the /etc/modprobe.d/unsupported_modules file to make

the following change:

allow_unsupported_modules 1 (replace 0 with 1)

 To load the driver using modprobe, issue the following command:

# modprobe -v qla2xxx

 To unload the driver using modprobe, issue the following command:

# modprobe -r qla2xxx

4. (Optional) Automatically load the driver by rebuilding the RAM disk to

include the driver.

Create a copy of the current RAMDISK by issuing the following commands:

# cd /boot

# cp initrd-[kernel version].img initrd-[kernel

version].img.bak

# mkinitrd

Depending on the server hardware, the RAMDISK file name may be different.

5. To load the driver, reboot the host.

Building the Driver for SLES 12

1. From the directory that contains the source driver file,

qla2xxx-src-vx.xx.xx.xx.12.x-k.tgz, issue the following commands:

# tar -xzvf qla2xxx-src-vx.xx.xx.xx.11.x-k.tgz

# cd qla2xxx-x.xx.xx.xx.xx.xx-k4

Where x.xx.xx.xx.xx.xx is the applicable version number.

2. Build and install the driver modules from the source code by executing the

build.sh script as follows:

# ./extras/build.sh install

The build.sh script does the following:

 Builds the driver .ko files.

 Copies the .ko files to the appropriate

/lib/modules/3.x.../updates directory.

15 BK3254601-00 C

Page 31

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

 Adds the appropriate directive in the modprobe.conf file (if

applicable).

You can optionally complete either or both Step 3 and Step 4 of this procedure.

3. (Optional) Manually load the driver for Linux.

 Edit the /etc/modprobe.d/unsupported_modules file to make

the following change:

allow_unsupported_modules 1 (replace 0 with 1)

 To load the driver using modprobe, issue the following command:

# modprobe -v qla2xxx

 To unload the driver using modprobe, issue the following command:

# modprobe -r qla2xxx

4. (Optional) To automatically load the driver each time the system boots,

rebuild the RAM disk to include the driver as follows:

a. Create a backup copy of the RAMDISK image by issuing the following

commands:

# cd /boot

# cp initramfs-[kernel version].img initramfs-[kernel

version].img.bak

b. Create the new RAMDISK by issuing the following command:

# dracut -f

5. To load the driver, reboot the host.

VMware Driver Installation and Configuration

This section provides the following procedures for installing drivers on a VMware system:

 Installation Overview

 Installing the ESXi 6.5 and 6.0 U2 Fibre Channel Driver

 Installing QConvergeConsole VMware vCenter Server Plug-in

 Installing QConvergeConsole VMware vSphere Web Client Plug-in

16 BK3254601-00 C

Page 32

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

Installation Overview

To install and configure the adapter drivers on a VMware system, refer to the driver release notes and readme files included in the package.

Installing the ESXi 6.5 and 6.0 U2 Fibre Channel Driver

The operating system manages and controls the driver installation process. To install the ESXi driver, follow the steps in this section.

This section provides the most common ways of installing and upgrading the driver. For other installation procedures, consult the operating system manuals and the driver readme file.

This section provides procedures for the following:

 “Updating an Existing Driver or Installing a New Driver for an Existing ESXi

6.5 or 6.0 U2 Installation with esxcli” on page 17

 “Verifying the Version of the Installed Driver” on page 18

Updating an Existing Driver or Installing a New Driver for an Existing ESXi 6.5 or 6.0 U2 Installation with esxcli

To use the driver bundle <offline-bundle>.zip):

1. Copy the driver bundle (<offline-bundle>.zip) to this ESXi host.

2. Install the driver bundle (<offline-bundle>.zip) as follows:

a. To create a temporary directory, issue the following commands:

mkdir /install

cd /install

b. Unzip the driver bundle in the temporary directory:

/install : unzip <offline-bundle>.zip

c. Issue the following command:

esxcli software vib install -n qlnativefc -d /install

To use the driver VIB:

1. Copy the driver VIB to this ESXi host by issuing the following command:

qlnativefc-<driver-version>.0.0.<esx-build>.x86_64.vib

17 BK3254601-00 C

Page 33

2–Driver Installation and Configuration VMware Driver Installation and Configuration

2. Install the driver VIB using the following esxcli commands:

a. To make a temporary directory, issue the following commands:

mkdir /install

cd /install

b. Issue the following command:

esxcli software vib install -v /install/<driver-vib>

Verifying the Version of the Installed Driver

To verify the installed package in the system, issue the following command:

esxcli software vib list | grep qla2xxx

The driver version is embedded in the VIB version.

For example, the output looks like the following:

# esxcli software vib list | grep qla2xxx

scsi-qla2xxx 911.k1.1-16vmw.500.0.0.406165 VMware VMwareCertified 2011-09-21

Installing QConvergeConsole VMware vCenter Server Plug-in

To use QConvergeConsole VMware vCenter Server Plug-in, install the following software in this order:

1. QConvergeConsole VMware vCenter Server Plug-in on the vCenter

Server

2. QLogic Adapter CIM Provider on the ESXi server

The following sections explain how to install and uninstall the required software:

 “Installation Package Contents” on page 19

 “Installing QConvergeConsole VMware vCenter Server Plug-in” on page 19

 “Plug-in Unregistration from a Manual Install” on page 25

 “Uninstalling the QConvergeConsole VMware vCenter Server Plug-in” on

page 26

 “Installing the QLogic Adapter CIM Provider” on page 26

 “Uninstalling the QLogic Adapter CIM Provider” on page 29

For information on installing the Plug-in, refer to “Installing QConvergeConsole

VMware vCenter Server Plug-in” on page 19.

18 BK3254601-00 C

Page 34

2–Driver Installation and Configuration VMware Driver Installation and Configuration

Installation Package Contents

The latest version of the QLogic Adapter CIM Provider and QConvergeConsole VMware vCenter Server Plug-in package contains the files needed to install both the Plug-in and the CIM Provider. Required files include the following (where x_x_x is the version number):

 QLogic_Adapter_VI_Plugin_x_x_x.exe—This file is the

QConvergeConsole VMware vCenter Server Plug-in installation package.

 qlogic_adapter_provider_vmware_esx55_60-x.x.x—This file

contains the QLogic Adapter CIM Provider installation package for ESXi 6.5 and 6.0 U2, where x.x.x is the version of the CIM Provider.

 readme.txt—This file is the Read Me document that covers hardware and

software requirements, operating system support, supported features, installation and removal instructions, known issues and workarounds, and support contact information.

 release_notes.txt—This file is the Release Notes document that lists

changes, fixes, known issues, and release details.

For detailed information on installing the QConvergeConsole VMware vCenter Server Plug-in, refer to “Installing QConvergeConsole VMware vCenter Server

Plug-in” on page 19.

For detailed information on installing the CIM Provider, refer to “Installing the

QLogic Adapter CIM Provider” on page 26.

Installing QConvergeConsole VMware vCenter Server Plug-in

To install the QConvergeConsole VMware vCenter Server Plug-in:

1. Download the QLogic_Adapter_VI_Plugin_x_x_x.exe file (where

x_x_x is the version number).

2. Run the installation either by double-clicking the .exe file, by typing the

name of the .exe file in a Run window, or by clicking Browse and locating the .exe file.

19 BK3254601-00 C

Page 35

2–Driver Installation and Configuration VMware Driver Installation and Configuration

The InstallAnywhere wizard opens, as shown in Figure 2-9.

Figure 2-9. InstallAnywhere Initial Window

3. In the QLogic Adapter VI Plug-in wizard’s Introduction window (see

Figure 2-10), click Next.

Figure 2-10. QLogic Adapter VI Plug-in Wizard: Introduction

20 BK3254601-00 C

Page 36

2–Driver Installation and Configuration VMware Driver Installation and Configuration

Wait while the wizard configures the plug-in (see Figure 2-11).

Figure 2-11. QLogic Adapter VI Plug-in Wizard: Configuring the Plug-in

4. Select the installation directory, and then click Install (see Figure 2-12).

Figure 2-12. QLogic Adapter VI Plug-in Wizard: Choose Install Folder

21 BK3254601-00 C

Page 37

2–Driver Installation and Configuration VMware Driver Installation and Configuration

Wait while the wizard performs the installation (see Figure 2-13).

Figure 2-13. QLogic Adapter VI Plug-in Wizard: Installing the Plug-In

22 BK3254601-00 C

Page 38

2–Driver Installation and Configuration VMware Driver Installation and Configuration

5. Type the requested information in the boxes, then click Next (see

Figure 2-14).

Figure 2-14. QLogic Adapter VI Plug-in Wizard: User Input

23 BK3254601-00 C

Page 39

2–Driver Installation and Configuration VMware Driver Installation and Configuration

Wait while the wizard finishes configuring the plug-in (see Figure 2-15).

Figure 2-15. QLogic Adapter VI Plug-in Wizard: Configuration in Progress

24 BK3254601-00 C

Page 40

2–Driver Installation and Configuration VMware Driver Installation and Configuration

6. When the Registration Result window (Figure 2-16) appears, click Finish to

exit.

Figure 2-16. QLogic Adapter VI Plug-in Wizard: Registration Result

7. After the installation completes, restart the TomcatTM service as follows:

 If the plug-in is installed on the VMware vCenter Server, restart the

VMware Virtual Center Management Web services.

 If the plug-in is installed on a server other than the vCenter Server,

restart the Apache Tomcat service.

Plug-in Unregistration from a Manual Install

If you have performed a manual install of the QConvergeConsole VMware vCenter Server Plug-in, you must perform a manual uninstall before running the plug-in Installation Wizard.

VMware provides two type of scripts for plug-in registration (and unregistration):

 For PowerShell scripting:

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

 For Perl®:

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

25 BK3254601-00 C

Page 41

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

Before you can use the script, you must download the appropriate VI SDK from VMware:

 For Perl VI SDK, download vSphere SDK for Perl:

http://www.vmware.com/support/developer/viperltoolkit/

 For PowerShell, download vSphere PowerCLI:

http://communities.vmware.com/community/vmtn/vsphere/automationtools/ powercli

After downloading and installing the SDK and the registration script, follow the VMware instructions to unregister the 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"

To log into the vCenter Server, replace administrator and password with the correct information.

Uninstalling the QConvergeConsole VMware vCenter Server Plug-in

To remove the QConvergeConsole VMware vCenter Server Plug-in:

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

(Windows Server 2008 or later only: select Programs and Features.)

2. In the Add or Remove Programs dialog box, select the QConvergeConsole

VMware vCenter Server Plug-in, and then click Change/Remove.

3. To remove the plug-in, follow the instructions in the QConvergeConsole

VMware vCenter Server Plug-in installer.

Installing the QLogic Adapter CIM Provider

This section describes how to install, start, and remove the QLogic Adapter CIM Provider for VMware ESXi. Because there are multiple zip packages, ensure that you pick the zip package that matches your environment: ESXi 6.5 and ESXi 6.0 U2.

The QLogic Adapter CIM Provider for VMware ESXi was generated as a VIB file. A VIB contains the complete set of files and binaries required to install the provider on VMware ESXi. The file offline-bundle.zip contains the VIB and the necessary metadata to install the provider on VMware ESXi.

26 BK3254601-00 C

Page 42

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

Initial Installation Methods

Initial installation methods for the CIM Provider include the following:

 Online. Refer to “Installing the CIM Provider on an ESXi 6.5 or 6.0 U2 Host”

on page 27.

 Offline. Refer to “Existing ESXi Installation Using VMware Update Manager”

on page 27.

 Remote. Refer to “Remote Installation of the CIM Provider on an ESXi Host”

on page 28.

Installing the CIM Provider on an ESXi 6.5 or 6.0 U2 Host

1. Copy the following file to the root directory (/) of the ESXi 6.5 system:

QLGC-ESX-5.5.0-qlogic-adapter-provideroffline_bundle-

xxxxxxx.zip

x.x.xx.xxxxxxx-

For an ESXi 6.0 U2 host, select the .zip file for that version instead.

2. Issue the esxcli commands as follows:

# cd /

# esxcli software acceptance set --level=CommunitySupported

# esxcli software vib install -d

file://<offline bundle>.zip --maintenance-mode

3. Reboot the system as required.

Existing ESXi Installation Using VMware Update Manager

An existing ESXi host has asynchronous drivers installed using VMware Update Manager (VUM). For more information, see “Using vSphere ESXi Image Builder CLI” in the vSphere Installation and Setup Guide at:

http://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

To install the asynchronous drivers:

1. Extract the contents of the asynchronous driver zip file.

2. Identify the offline-bundle.zip file or files.

3. From vCenter Server, go to Home, and then select Update Manager.

4. Click the Patch Repository tab.

5. Click the Import Patches link at the top right of the window.

6. Click Finish.

27 BK3254601-00 C

Page 43

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

The asynchronous driver is now added to the patch repository.

7. Create a baseline and remediate the ESXi host. For more information, refer

to Installing and Administering VMware vSphere Update Manager:

http://www.vmware.com/support/pubs/vum_pubs.html

Remote Installation of the CIM Provider on an ESXi Host

Before performing this procedure, ensure that the remote ESXi system is in Maintenance Mode. To do so 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 vSphere Management Assistant (vMA) is hosted.

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

3. To install the offline bundle, issue the vihostupdate command as

follows:

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

4. Follow the on-screen instructions to complete the installation. You might

need to reboot the ESXi system.

For more details on the vihostupdate command, see the vSphere Command-Line Interface Installation and Reference Guide at:

http://www.vmware.com/pdf/vsphere4/r40/vsp_40_vcli.pdf

Subsequent Update Installation

To update the QLogic Adapter CIM Provider after a prior VIB installation, follow the instructions in “Uninstalling the QLogic Adapter CIM Provider” on page 29 to remove the existing VIB. After completing the VIB removal, use the same steps in

“Initial Installation Methods” on page 27 to install the new VIB.

Starting the QLogic Adapter CIM Provider

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

28 BK3254601-00 C

Page 44

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

If the CIM Provider does not start automatically, you can 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.

Uninstalling the QLogic Adapter CIM Provider

You can uninstall the QLogic Adapter CIM Provider for your version of VMware. For information about removing the QLogic Adapter CIM Provider through a remote host, see the QLogic Adapter CIM Provider and vCenter Plug-in for VMware ESX/ESXi Readme file.

Uninstalling the CIM Provider from an ESXi 5.x Host

1. To view the VIB list, issue the following command:

# esxcli software vib list

2. To remove the QLogic Adapter CIM Provider, issue the following command:

# esxcli software vib remove --vibname qlogic-adapter-provider

--maintenance-mode –f

Uninstalling the CIM Provider from a Remote Host

Before performing this procedure, make sure that the ESXi system is in Maintenance Mode. To do so using the 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 and find the Bulletin ID of the existing provider:

# vihostupdate.pl <conn_options> --query

2. Remove the existing VIB by issuing the following command:

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

29 BK3254601-00 C

Page 45

2–Driver Installation and Configuration

NOTE

VMware Driver Installation and Configuration

For more details on vihostupdate, see the vSphere Command-Line Interface Installation and Reference Guide, located here:

http://www.vmware.com/pdf/vsphere4/r40/vsp_40_vcli.pdf

Installing QConvergeConsole VMware vSphere Web Client Plug-in

1. Gather the information necessary for the installation, including:

 IP address of the vCenter Server

 vCenter Server credentials (user name and password)

 Where to host the QConvergeConsole VMware vSphere Web Client

Plug-in (on vCenter Server or other server)

If you are hosting the QConvergeConsole VMware vSphere Web Client Plug-in on a non-vCenter Server, make sure the server has Tomcat running as a service and have the IP address of the Tomcat instance ready. Also, make sure the Tomcat CATALINA_HOME environment variable is set to the appropriate directory.

2. Run the installer on the server providing the Tomcat service. Provide the

information requested by the installer.

 On Windows, double-click the installer and follow the instructions on

the GUI provided.

 On Linux:

a. Make sure the user is the root user (or has root privileges).

b. Create the installer executable if one does not already exist.

Choose the installer for your system (32-bit or 64-bit), and then issue the following command:

chmod +x <installer>

Where <installer> is the file name of the installer.

c. Run the installer by issuing the following command:

./<installer>

Where <installer> is the file name of the installer.

d. Follow the instructions provided by the installer.

3. Restart the Tomcat service.

30 BK3254601-00 C

Page 46

2–Driver Installation and Configuration VMware Driver Installation and Configuration

If the QConvergeConsole VMware vCenter Server Plug-in is being hosted on the vCenter Server, you must restart the VMware Virtual Center Management Web services:

 In Windows, go to the Administrative Tools menu, select Services,

and then restart VMware Virtual Center Management Web services.

 On the vCenter Server Appliance (Linux), issue the following

command:

/etc/init.d/vmware-vpxd tomcat-restart

4. Restart any vSphere Web Client sessions.

If you are updating a previous version of the QConvergeConsole VMware vCenter Server Plug-in, restart the vSphere Web Client services;

 In Windows, go to the Administrative Tools menu, select Services,

and then restart VMware vSphere Web Client.

 On the vCenter Server Appliance (Linux), issue the following

command:

/etc/init.d/vsphere-client restart

Uninstalling the QConvergeConsole VMware vCenter Server Plug-in

To uninstall the QConvergeConsole VMware vCenter Server Plug-in, refer to the procedure for Windows or Linux:

 Windows. Uninstalling the QConvergeConsole VMware vCenter Server

Plug-in on Windows is initiated through the Windows Uninstall Programs control panel. Follow the uninstaller user interface to uninstall the plug-in.

 Linux. Uninstalling the QConvergeConsole VMware vCenter Server Plug-in

on Linux is initiated by the following command line command:

/opt/qlogic/QLogic\ Adapter\ Web\ Client\ Plugin/Uninstall_QLogic\ Adapter\ Web\ Client\ Plugin/Uninstall\ QLogic\ Adapter\ Web\ Client\ Plugin

Follow the prompts (user interface or console commands) to uninstall the plug-in by the root user.

31 BK3254601-00 C

Page 47

NOTE

Fibre Channel Configuration

This chapter provides the following information about configuring Fibre Channel:

 “Updating the Dell Firmware” on page 33

 “Using Fast!UTIL for Custom Configuration” on page 36

 “Setting Fibre Channel Adapter Parameters” on page 43

 “Configuring Target Persistent Binding” on page 44

 “Configuring Boot Devices” on page 45

 “Configuring Virtual Ports (NPIV)” on page 47

 “Configuring Fibre Channel Driver Parameters” on page 53

 “Configuring Selective LUNs” on page 54

 “Configuring OoOFR” on page 55

 “Configuring the UEFI Driver” on page 56

 “Setting an FA-PWWN” on page 63

 “Configuring and Verifying FA-BLD” on page 68

 “Using a Fabric-Assigned Boot LUN” on page 73

 “Running Diagnostics—Fibre Channel Ping and Trace Route” on page 76

 “Configuring CS_CTL QoS” on page 81

 “Configuring End-to-End CS_CTL QoS” on page 84

 “Configuring FDMI” on page 90

 “Enabling QLogic Forward Error Correction” on page 94

 “Running Extended Link Service Commands” on page 96

For information on configuring the Fibre Channel Adapter using VMware vCenter Server, refer to the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00), available at:

http://driverdownloads.qlogic.com

32 BK3254601-00 C

Page 48

3–Fibre Channel Configuration Updating the Dell Firmware

Updating the Dell Firmware

The firmware Dell update package is a Flash update utility only; it is not used for adapter configuration. To run the firmware Dell Update Package, double-click the executable file. Alternatively, run the firmware Dell Update Package from the command line, which supports several command line options.

Running the Firmware Update by Double-Clicking

For additional information, refer to the Dell Update Packages Version xx.xx.xxx User’s Guide, “Using Dell Update Packages” section.

To run the firmware Dell Update Package by double-clicking the executable file:

1. Double-click the icon representing the firmware Dell Update Package file.

When the Dell Update Package splash screen appears (Figure 3-1), click Install to continue.

Figure 3-1. Dell Update Package Splash Screen

33 BK3254601-00 C

Page 49

3–Fibre Channel Configuration Updating the Dell Firmware

2. Follow the installer instructions. If a warning message appears (Figure 3-2),

click Yes to continue the installation.

Figure 3-2. Continue Dell Update Package Installation

The installer indicates that it is loading the new firmware (Figure 3-3).

Figure 3-3. Loading New Firmware

34 BK3254601-00 C

Page 50

3–Fibre Channel Configuration Updating the Dell Firmware

3. When complete, the installer indicates the result of the installation

(Figure 3-4). Click Yes to elect to reboot.

4. To complete the installation, click Finish (Figure 3-5).

Figure 3-4. Result of Installation

Figure 3-5. Finish Installation

Running the Firmware Update from the Command Line

Running the firmware Dell update package from the command line, with no options specified, results in the same behavior as double-clicking the icon representing the Dell update package. Note that the actual file name of the Dell update package will vary.

C:\> Network_Firmware_2T12N_WN32_<version>_X16.EXE

35 BK3254601-00 C

Page 51

3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration

Figure 3-6 shows the options you can use to customize the Dell update package

installation behavior.

Figure 3-6. Command Line Options

Using Fast!UTIL for Custom Configuration

This section provides detailed configuration information for advanced users who want to customize the configuration of the adapters and connected devices using Fast!UTIL (the QLogic Fibre Channel Adapter BIOS utility) in a pre-OS environment.

To configure adapters using Fast!UTIL:

1. During the Host Bus Adapter BIOS initialization, press ALT+Q or CTRL+Q. It

may take a few seconds for the Fast!UTIL menu to appear.

2. When the Select Host Adapter window appears, select the adapter type.

3. In the Adapter Settings window (see “Adapter Settings” on page 37),

configure the adapter settings.

4. A message indicates that the configuration settings have been modified.

Select Save changes.

36 BK3254601-00 C

Page 52

3–Fibre Channel Configuration

CAUTION

Using Fast!UTIL for Custom Configuration

5. To load the new parameters, reboot the system.

If the configuration settings are incorrect, your 2700 Series Adapter may not function properly.

The Fast!UTIL Options menu provides the following options:

 “Configuration Settings” on page 37

 “Scan Fibre Devices” on page 41

 “Fibre Disk Utility” on page 42

 “Loopback Data Test” on page 42

 “Select Adapter” on page 42

 “Exit Fast!UTIL” on page 42

Configuration Settings

The following sections show and describe the 2700 Series Adapters Configuration Settings menu options in Fast!UTIL:

 “Adapter Settings” on page 37

 “Selectable Boot Settings” on page 39

 “Restore Default Settings” on page 40

 “Raw NVRAM Data” on page 40

 “Advanced Adapter Settings” on page 40

Adapter Settings

Table 3-1 describes the adapter settings.

Table 3-1. Adapter Settings

Setting Values Default Description

Host Bus Adapter BIOS

Enabled, Disabled

Disabled Disabling this setting disables the ROM BIOS on the 2700

Series Adapter, which frees space in upper memory. If you are booting from a Fibre Channel disk drive attached to the 2700 Series Adapter, you must enable this setting. See

“Selectable Boot Settings” on page 39 for details on specify-

ing the boot device.

Frame Size 512, 1024,

2048

2048 This setting specifies the maximum frame length supported

by the 2700 Series Adapter.

37 BK3254601-00 C

Page 53

3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration

Table 3-1. Adapter Settings (Continued)

Setting Values Default Description

Loop Reset Delay

Adapter Hard Loop ID

Hard Loop ID 0–125 0 If the Adapter Hard Loop ID setting is enabled, the adapter

Connection Options

Fibre Channel Tape Support

Data Rate 2, 4, 5, 6 2 This setting determines the data rate:

0–60 seconds

Enabled, Disabled

0, 1, 2 2 This setting defines the type of connection:

Enabled, Disabled

seconds

Disabled If the Adapter Hard Loop ID setting is enabled, the adapter

Enabled This setting enables FCP-2 recovery.

After resetting the loop, the firmware refrains from initiating any loop activity for the number of seconds specified in this setting.

attempts to use the ID specified in the Hard Loop ID setting.

attempts to use the ID specified in this setting.

 0—loop only (for the 8Gb data rate)  1—point-to-point only (for the 8Gb, 16Gb, and 32Gb

data rate)

 2—loop preferred, then point-to-point (for the 8Gb and

16Gb data rate)

 2—The adapter auto-negotiates and determines the data

rate.

 4—The adapter runs at 8Gbps.  5—The adapter runs at 16Gbps. Loop mode is not sup-

ported.

 6—The adapter runs at 32Gbps.

38 BK3254601-00 C

Page 54

3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration

Selectable Boot Settings

The Configuration Settings menu provides access to the Selectable Boot Settings options. If you enable the Host Bus Adapter BIOS in the adapter

settings, you can select the boot device, as shown in Table 3-2.

Table 3-2. Selectable Boot Settings

Enable

Selectable

Boot

No — The BIOS configures the first disk drive it finds as the boot

Yes None

Yes Specified The BIOS scans through the specified boot worldwide port

Boot

WWPN/

LUN

specified

Device Boot

device.

The BIOS configures the first disk drive it finds that is also LUN 0 as the boot device.

name (WWPN) and LUN list until it finds a disk drive. This drive is configured as the boot device.

The Selectable Boot Settings option allows you to specify up to four WWPNs or LUNs as boot devices.

To enable the Selectable Boot option and insert devices into boot device locations:

1. On the Configuration Settings menu, select Host Adapter Settings.

2. Enable the Host Bus Adapter BIOS and then press the ESC key to return

to the Configuration Settings menu.

3. On the Configuration Settings menu, select Selectable Boot Settings.

4. To enable or disable (toggle) the Selectable Boot option, press the ENTER

key. To move to the Primary location of the Selectable Boot List menu, press the DOWN ARROW key.

5. To see a list of accessible devices (in the Select Fibre Channel Device

menu), press ENTER.

6. Select a drive by pressing the UP ARROW and DOWN ARROW keys or the

PAGE UP and PAGE DOWN keys to scroll to the device that you want to put into your Selectable Boot menu list. Then press ENTER to select the requested device and load it into the Selectable Boot menu list.

39 BK3254601-00 C

Page 55

3–Fibre Channel Configuration

NOTE

Using Fast!UTIL for Custom Configuration

7. To specify an alternate boot device on the 2700 Series Adapter, use the

arrow keys to move to the next available alternate entry, press ENTER, select the disk drive you want, and press ENTER again. You can specify up to three alternate boot devices in this way.

System BIOS compatibility: To boot from a QLogic host 2700 Series Adapter in a computer system with a multiboot system BIOS, the 2700 Series Adapter must be included in the list of bootable devices in the system’s Boot menu.

Restore Default Settings

The Restore Defaults option restores the BIOS settings back to default.

Raw NVRAM Data

The Raw NVRAM Data option displays the 2700 Series Adapter’s NVRAM contents in hexadecimal format. This option is a QLogic troubleshooting tool; you cannot modify the raw NVRAM data.

Advanced Adapter Settings

On the Configuration Settings menu in Fast!UTIL, select Advanced Adapter Settings. Tab le 3- 3 describes the default settings for the 2700 Series Adapters.

Table 3-3. Advanced Adapter Settings

Setting Values Default Description

LUNs per Target

Enable LIP

Reset

Enable LIP Full Login

0, 8, 16, 32, 64, 128, 256

Yes, No No This setting determines the type of loop initialization pro-

Yes, No Yes When this setting is Yes, the 2700 Series Adapter’s reduced

128 This setting specifies the number of LUNs supported per

target if the target does not support the Report LUN command. Multiple LUN support is typically for redundant array of independent disks (RAID) boxes that use LUNs to map drives.

cess (LIP) reset used when the OS initiates a bus reset routine as follows:

 Yes = The driver initiates a global LIP reset to reset the

target devices.

 No = The driver initiates a global LIP reset with full login.

instruction set computer (RISC) controller log in to all ports after any LIP.

40 BK3254601-00 C

Page 56

3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration

Table 3-3. Advanced Adapter Settings (Continued)

Setting Values Default Description

Enable Target Reset

Port Down Retry Count

Link Down Timeout

Operation Mode

Interrupt Delay Timer

Yes, No Yes When this setting is Yes, the drivers issue a Target Reset

command to all devices on the loop when a SCSI Bus Reset command is issued.

0–255 8 This setting specifies the number of times the software tries

to log in to a device.

0–255 seconds

0, 5, 6 6 This setting specifies the reduced interrupt operation (RIO)

0–255 (100μs units)

seconds

2 (200μs) This setting contains the value used by a timer to set the

This setting specifies the number of seconds the software waits before resending a command to a port whose status indicates that the port is down.

This setting specifies the number of seconds the software waits for a link that is down to come up.

modes if they are supported by the software driver. The RIO modes allow posting multiple command completions in a single interrupt. This setting supports the following modes:

 0—Interrupt for every I/O completion  5—Interrupt when the interrupt delay timer expires  6—Interrupt when the interrupt delay timer expires or no

active I/Os

wait time before generating an interrupt.

Enable Interrupt

Loop support is available only at port speeds up to 16Gbps. At 32Gbps, loop is not supported.

Yes, No No This setting enables or disables the interrupt:

 Yes—This setting enables the BIOS to use the interrupt

request (IRQ) assigned to the 2700 Series Adapter.

 No—The BIOS polls for the 2700 Series Adapter's RISC

controller mailbox command completion status.

Scan Fibre Devices

The Scan Fibre Devices option scans the Fibre Channel loop and lists all the connected devices by loop ID. It lists information about each device; for example, vendor name, product name, and revision. This information helps when configuring your 2700 Series Adapter and attached devices.

41 BK3254601-00 C

Page 57

3–Fibre Channel Configuration

CAUTION

NOTE

Using Fast!UTIL for Custom Configuration

Fibre Disk Utility

The Fibre Disk Utility option scans the Fibre Channel loop and lists all the connected devices by loop ID. You can select a Fibre Channel hard disk and do one of the following tasks:

 Perform a low-level format  Verify the disk media  Verify the disk data (Some targets do not support this feature.)  Select a disk device

Performing a low-level format destroys all data on the disk.

Loopback Data Test

The Loopback Data Test option allows you to perform the following loopback tests:

 External loopback data test  Internal loopback data test

When running an external loopback data test, make sure that the Fibre Channel link is up or a loopback plug is attached to the 2700 Series Adapter before starting the test.

Select Adapter

If you have a multiport or multiple 2700 Series Adapters in the system, use the Select Adapter option to select and then configure or view the settings of a specific 2700 Series Adapter or one of its ports.

Exit Fast!UTIL

The Exit Fast!UTIL option allows you to exit the utility and reboot the system. After making changes to the 2700 Series Adapter in Fast!UTIL, make sure you save the changes before you reboot the system.

42 BK3254601-00 C

Page 58

3–Fibre Channel Configuration Setting Fibre Channel Adapter Parameters

Setting Fibre Channel Adapter Parameters

Use QConvergeConsole to set Fibre Channel adapter parameters:

 Setting Fibre Channel Adapter Parameters with QConvergeConsole GUI

 Setting Fibre Channel Adapter Parameters with Interactive

QConvergeConsole CLI

 Setting Fibre Channel Adapter Parameters with Noninteractive

QConvergeConsole CLI

Setting Fibre Channel Adapter Parameters with QConvergeConsole GUI

For information about how to set Fibre Channel adapter parameters using QConvergeConsole GUI, refer to the topic about managing Fibre Channel and Fibre Channel over Ethernet (FCoE) adapter ports in the QConvergeConsole Help.

Setting Fibre Channel Adapter Parameters with Interactive QConvergeConsole CLI

To set Fibre Channel adapter parameters with interactive QConvergeConsole CLI:

1. On the Fibre Channel Adapter Configuration menu, select HBA

Parameters.

2. On the port menu, select a port to open the HBA Parameters menu.

3. On the HBA Parameters menu, select the Configure HBA Parameters

option to open the Configure Parameters menu.

For more information, refer to the section about the Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Setting Fibre Channel Adapter Parameters with Noninteractive QConvergeConsole CLI

For information about how to set Fibre Channel adapter parameters using the noninteractive mode of QConvergeConsole CLI, refer to the section about the Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

43 BK3254601-00 C

Page 59

3–Fibre Channel Configuration

NOTE

Configuring Target Persistent Binding

Target persistent binding is supported only on Windows.

Use QConvergeConsole to configure target persistent binding:

 Configuring Persistent Binding with QConvergeConsole GUI

 Configuring Persistent Binding with Interactive QConvergeConsole CLI

 Configuring Persistent Binding with Noninteractive QConvergeConsole CLI

Configuring Persistent Binding with QConvergeConsole GUI

To bind target devices attached to an adapter port using QConvergeConsole GUI:

1. In the system tree, expand a Fibre Channel node.

2. In the system tree for a 2700 Series Adapter, select the physical port

number.

3. Click the Targets tab, and then click the Target Persistent Binding tab.

4. Choose the binding options:

 Select the Bind All check box to bind all the devices listed to adapter

ports.

 Select the Bind check box if you want to configure a specific port and

bind it to the target ID that you have selected from the Target I D list. If you do not want to configure the port, clear the check box. If you clear the check box, the corresponding port is unconfigured.

5. To save the configuration changes, click Save.

6. If the Security Check dialog box appears, type the password in the Enter

Password box, and then click OK.

7. The system overwrites any previously saved configuration for the current

adapter and displays a message box. Click OK to close the message box.

For more information, refer to the topic about binding target devices in the QConvergeConsole Help.

44 BK3254601-00 C

Page 60

3–Fibre Channel Configuration Configuring Boot Devices

Configuring Persistent Binding with Interactive QConvergeConsole CLI

To bind a target using interactive QConvergeConsole CLI:

1. On the Fibre Channel Adapter Configuration menu, select Target

Persistent Bindings.

2. On the port menu, select a port and then select Bind Target(s) to bind a

target to a port.

3. Select a target and specify a target ID to open the Target Persistent

Binding – FC Port Configuration menu with options to select more targets, save changes, or cancel the binding operation.

For more information, refer to the section about Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Configuring Persistent Binding with Noninteractive QConvergeConsole CLI

To bind a selected target to a specific adapter using the noninteractive mode of QConvergeConsole CLI, issue the following command:

# qaucli -pr fc -p (<hba instance> | <hba wwpn>) (<target wwnn> <target wwpn> <target port id> <target id>)

Where:

hba instance = Adapter number (use the -g command to find)

hba wwnn = Worldwide node name of the adapter

hba wwpn = Worldwide port name of the adapter target wwnn = Worldwide node name of the target target wwpn = Worldwide port name of the target

target port id = Port ID of the target

target id = ID to which the target is bound

For more information, refer to the section about Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Configuring Boot Devices

Use QConvergeConsole or Fast!UTIL to configure boot devices:

 Configuring Boot Devices with QConvergeConsole GUI

 Configuring Boot Devices with Interactive QConvergeConsole CLI

45 BK3254601-00 C

Page 61

3–Fibre Channel Configuration Configuring Boot Devices

 Configuring Boot Devices with Noninteractive QConvergeConsole CLI

 Configuring Boot Devices with the BIOS

Configuring Boot Devices with QConvergeConsole GUI

For information about configuring boot devices with QConvergeConsole GUI, refer to the topics about HBA parameters, viewing or modifying port parameters, and boot device selection in the QConvergeConsole Help.

Configuring Boot Devices with Interactive QConvergeConsole CLI

On the Fibre Channel Adapter Configuration menu, select Boot Devices Configuration to open the Boot Device Settings menu with options to view and

configure boot devices.

For information, refer to the section about the Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Configuring Boot Devices with Noninteractive QConvergeConsole CLI

To set a specific target as the boot device for a specific adapter, issue the following command:

# qaucli -pr fc -e (<hba instance> | <hba wwpn>) <target wwnn> <target wwpn> <target id> <lun id>

Where:

hba instance = Adapter number (use the -g command to find)

hba wwpn = Worldwide port name of the adapter target wwnn = Worldwide node name of the target target wwpn = Worldwide port name of the target

target id = ID to which the target is bound

lun id = ID of the LUN

For more information, refer to the “Fibre Channel Noninteractive Commands” section of the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Configuring Boot Devices with the BIOS

For information about boot device configuration with the Fast!UTIL BIOS utility, refer to “Using Fast!UTIL for Custom Configuration” on page 36 for information.

46 BK3254601-00 C

Page 62

3–Fibre Channel Configuration Configuring Virtual Ports (NPIV)

Configuring Virtual Ports (NPIV)

Use QConvergeConsole to configure virtual ports for N_Port ID virtualization and quality of service:

 Configuring NPIV with QConvergeConsole GUI

 Configuring NPIV with Interactive QConvergeConsole CLI

 Configuring NPIV with Noninteractive QConvergeConsole CLI

 Configuring NPIV Quality of Service

Configuring NPIV with QConvergeConsole GUI

For information about using virtualization (NPIV) in QConvergeConsole GUI, refer to in the QConvergeConsole Help.

To access the QConvergeConsole Help system while the GUI utility is running,

point to the gear icon , point to Help, and then click then click Browse Contents. To install QConvergeConsole GUI, see “Installing QConvergeConsole

GUI” on page 112.

Configuring NPIV with Interactive QConvergeConsole CLI

For information about using virtualization (NPIV) in the interactive mode of QConvergeConsole CLI, refer to the User’s Guide—QConvergeConsole CLI (part number SN0054667-00). To download the guide, go to www.qlogic.com Downloads.

and click

Configuring NPIV with Noninteractive QConvergeConsole CLI

To create a virtual port with an automatic WWPN using the noninteractive mode of QConvergeConsole CLI, issue the following command:

# qaucli -pr fc -vp (<hba instance> | <hba wwpn>) create auto

Where:

hba instance = Adapter number (use the -g command to find)

hba wwpn = Worldwide port name of the adapter

For more information, refer to the section about Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

47 BK3254601-00 C

Page 63

3–Fibre Channel Configuration Configuring Virtual Ports (NPIV)

Configuring NPIV Quality of Service

The QLogic 2700 Series Adapters solution provides for standards-based quality of service (QoS), ensuring high-quality performance for applications that require preferential delivery. The QLogic QoS solution is based on assigning QoS levels to virtual ports (NPIV ports). You can configure the QoS using the priority method or the bandwidth method, as shown in Figure 3-7.

Figure 3-7. Priority and Bandwidth-Based QoS

On a single physical port, you can configure QoS using the priority method or the bandwidth method, but not both.

 The priority method assigns priority levels (low, medium, or high) to virtual

ports based on the quality of service required for the applications or VMs using the virtual port. This method provides for various levels of latency requirements across virtual ports.

 The bandwidth method assigns a bandwidth percentage (0–100) or a

bandwidth rate (for example, 6Gbps) to applications or VMs that are using a virtual port. This method provides a minimum bandwidth guarantee. The bandwidth-based QoS configuration applies only when the total bandwidth requirement of the applications exceeds the available bandwidth. The bandwidth is not reserved for a specific virtual port, and unused bandwidth is shared among the other virtual ports.

48 BK3254601-00 C

Page 64

3–Fibre Channel Configuration

NOTE

Configuring Virtual Ports (NPIV)

The physical port or WWN always has high priority, independent of the bandwidth or priority scheme chosen for created virtual ports. You need not assign a QoS level to every virtual port that you create. If a QoS level is not assigned to a virtual port, the default is low priority (best effort), independent of the bandwidth or priority scheme. This flexibility allows you to focus on critical applications to ensure that the highest service level is provided. You can modify QoS levels for virtual ports using QConvergeConsole CLI.

To modify QoS levels, the configuration must meet the following hardware and software requirements:

 Server operating system: Microsoft

 Server support for MSI-X

 A QLogic 2700 Series Adapter

 Latest version of the QLogic STOR miniport driver, available from

http://support.dell.com

 Fibre Channel switch that supports NPIV

Windows Server 2008 or later

 Physical port attached in a point-to-point connection

Setting QoS by Bandwidth

Setting the QoS by bandwidth allocates up to 80 percent of the physical port’s bandwidth to its virtual ports. The remaining 20 percent is reserved to handle non-QoS applications and virtual ports.

Setting QoS by bandwidth guarantees bandwidth for each virtual port and to the application or virtual machine (VM) associated with that virtual port. The proper QoS setting can prevent bottlenecks that occur when VMs contend for port bandwidth.

Consider how much bandwidth is required to maximize application or VM performance and set the QoS level to 105 percent of that value. For example, if a mission-critical application on a VM requires 1Gb of bandwidth to transmit its data over the fabric, QLogic recommends a 1.05Gb bandwidth for the virtual port.

Alternatively, you can set the virtual port QoS values as a percentage of the total available bandwidth.

Setting QoS by bandwidth guarantees a minimum bandwidth to a virtual port, but not a maximum limit. If the application or virtual port requires more bandwidth than the QoS bandwidth value allows and the physical port has available bandwidth, the application receives the additional bandwidth. The port allocates additional bandwidth on demand up to the port capacity or until there is contention for bandwidth among the virtual ports.

49 BK3254601-00 C

Page 65

3–Fibre Channel Configuration

Phy QLE2742 0:

Virt QLE2742 0:

Virt QLE2742 1:

QLE2742

Configuring Virtual Ports (NPIV)

When the physical port is partitioned into four virtual ports, the port bandwidth is divided between the virtual ports according to traffic demands.

QConvergeConsole lets you configure QoS for each virtual port by setting minimum and maximum percentages of the physical port’s bandwidth for each virtual port. This feature lets you guarantee a transmission rate for each port that requires a specific bandwidth to run mission-critical applications for business continuity using virtual ports. The setting for a specific QoS can resolve bottlenecks that exist when VMs contend for port bandwidth.

To set the QoS by bandwidth percentage with QConvergeConsole GUI:

1. In the QConvergeConsole system tree pane on the left, expand a 2700 Series Adapter.

2. Select a virtual port.

3. In the content pane on the right, click the QoS tab.

4. In the QoS Type box, select Bandwidth.

5. In the View By box, select Bandwidth Percentage.

6. Move the slider to select a percentage between 1 percent to 100 percent. This selection indicates the bandwidth you want to guarantee for data transferred over the selected virtual port.

Figure 3-8 shows an example.

Figure 3-8. Setting the QoS by Bandwidth Percentage

7. Click Save.

50 BK3254601-00 C

Page 66

3–Fibre Channel Configuration Configuring Virtual Ports (NPIV)

To set the QoS by bandwidth speed with QConvergeConsole GUI:

1. In the QConvergeConsole tree pane on the left, expand a 2700 Series Adapter.

2. Select a virtual port.

3. In the content pane on the right, click the QoS tab.

4. In the QoS Type box, select Bandwidth.

5. In the View By box, select Bandwidth Speed.

6. Move the slider to select the bandwidth speed, as shown in Figure 3-9.

Figure 3-9. Setting the QoS by Bandwidth Speed

7. Click Save.

To set the QoS by bandwidth speed with interactive QConvergeConsole CLI:

1. On the Fibre Channel Adapter Configuration menu, select the QoS option.

2. From the port menu, select a port to open the QoS Type Menu. Select 2: QoS Bandwidth to set the bandwidth speed.

51 BK3254601-00 C

Page 67

3–Fibre Channel Configuration Configuring Virtual Ports (NPIV)

Setting QoS by Priority

To set the QoS by priority with QConvergeConsole GUI:

1. In the QConvergeConsole tree pane on the left, expand a 2700 Series Adapter.

2. Select a virtual port.

3. In the content pane on the right, click the QoS tab.

4. In the QoS Type box, select Priority.

5. Move the slider to select a low, medium, or high priority, as shown in

Figure 3-10.

Figure 3-10. Setting the QoS by Priority

6. Click Save.

To set the QoS by priority with interactive QConvergeConsole CLI:

1. From the Fibre Channel Adapter Configuration menu, select the QoS option.

2. From the port menu, select a port to open the QoS Type Menu. Select 1: QoS Priority to set the priority.

52 BK3254601-00 C

Page 68

3–Fibre Channel Configuration Configuring Fibre Channel Driver Parameters

Configuring Fibre Channel Driver Parameters

Use QConvergeConsole GUI, CLI, or VMware plug-in to configure Fibre Channel driver parameters:

 Configuring Fibre Channel Driver Parameters with QConvergeConsole GUI

 Configuring Fibre Channel Driver Parameters with Interactive

QConvergeConsole CLI

 Configuring Fibre Channel Driver Parameters with Noninteractive

QConvergeConsole CLI

 Configuring Fibre Channel Driver Parameters with QConvergeConsole

VMware vCenter Server Plug-in

Configuring Fibre Channel Driver Parameters with QConvergeConsole GUI

Refer to the topics about HBA parameters and viewing or modifying port parameters in the QConvergeConsole Help for information.

Configuring Fibre Channel Driver Parameters with Interactive QConvergeConsole CLI

To configure Fibre Channel driver parameters using interactive QConvergeConsole CLI:

1. On the Fibre Channel Adapter Configuration menu, select HBA Parameters.

2. On the port menu, select a port to open the HBA Parameters menu.

3. On the HBA Parameters menu, select Configure HBA Parameters to open the Configure Parameters menu with options to configure connection options, data rate, frame size, hard loop ID, loop reset delay, BIOS, Fibre Channel tape support, operation mode, interrupt delay timer, login retry count, port down retry count, LIP full login, link down time-out, target reset, LUNS per target, and receive out-of-order frames.

For more information, refer to the section about the Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

53 BK3254601-00 C

Page 69

3–Fibre Channel Configuration Configuring Selective LUNs

Configuring Fibre Channel Driver Parameters with Noninteractive QConvergeConsole CLI

To configure driver settings, issue the following command:

# qaucli -pr fc -fs (<hba instance> | <hba wwpn>) {(<param name> | <param alias>) <param value>}

Where:

hba instance = Adapter number (use the -g command to find)

hba wwpn = Worldwide port name of the adapter

param name = Name of the parameter param alias = Alias of the parameter param value = New value of the parameter

For more information, refer to the section about the Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

Configuring Fibre Channel Driver Parameters with QConvergeConsole VMware vCenter Server Plug-in

For details on how to configure the Fibre Channel driver parameters using the QConvergeConsole plug-in, see the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00).

Configuring Selective LUNs

The QConvergeConsole GUI cannot be used for configuring selective LUNs.

To configure selective LUNs with the interactive QConvergeConsole CLI, refer to the section about the Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

To configure selective LUNs with the noninteractive QConvergeConsole CLI, refer to the section about the Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).

54 BK3254601-00 C

Page 70

3–Fibre Channel Configuration Configuring OoOFR

Configuring OoOFR

Out-of-order frame reassembly (OoOFR) reassembles out-of-order frames as they are received, minimizing network congestion by eliminating the retransmission of frames and exchanges. To configure OoOFR, use either QConvergeConsole GUI or CLI.

Configuring OoOFR with QConvergeConsole GUI

To enable OoOFR with QConvergeConsole GUI:

1. In the QConvergeConsole system tree pane on the left, select a Fibre Channel port.

2. In the content pane on the right, click Parameters.

3. Click the Advanced HBA Parameters tab.

4. Select the Enable Receive Out of Order Frame check box.

Configuring OoOFR with Interactive QConvergeConsole CLI

To enable OoOFR with the interactive QConvergeConsole CLI:

1. On the Fibre Channel Adapter Configuration menu, select HBA Parameters.

2. On the port menu, select a port to open the HBA Parameters menu.

3. On the HBA Parameters menu, select Configure HBA Parameters to open the Configure Parameters menu.

4. Select 13: Enable Receive Out Of Order Frame.

55 BK3254601-00 C

Page 71

3–Fibre Channel Configuration Configuring the UEFI Driver

Configuring OoOFR with Noninteractive QConvergeConsole CLI

To enable OoOFR in the noninteractive mode of QConvergeConsole CLI, issue one of the following commands:

# qaucli -n <hba instance>|<hba wwpn> EnableReceiveOutOfOrderFrame 1

# qaucli -n <hba instance>|<hba wwpn> EO 1

Where:

hba instance = Adapter number (use the -g command to find)

hba wwpn = Worldwide port name of the adapter

To disable OoOFR in the noninteractive mode of QConvergeConsole CLI, issue one of the following commands:

# qaucli -n <hba instance>|<hba wwpn> EnableReceiveOutOfOrderFrame 0

# qaucli -n <hba instance>|<hba wwpn> EO 0

Configuring the UEFI Driver

This section provides information on configuring the unified extensible firmware interface (UEFI) driver contained in the multiboot image. UEFI 2.x systems use a human interface infrastructure (HII) to configure motherboard devices and plug-in adapters. QLogic Fibre Channel Adapters use an HII to configure adapter parameters and boot-from-SAN settings.

To configure the UEFI driver for Dell:

1. During system boot, press the key corresponding to your platform.

2. On the Dell System Setup window, select Device Settings, and then press the ENTER key.

56 BK3254601-00 C

Page 72

3–Fibre Channel Configuration Configuring the UEFI Driver

The Device Settings window opens and lists the devices installed in the system. Each listed device supports the HII. QLogic devices have one device settings entry per port. Each entry contains the adapter name and WWPN of the port. Figure 3-11 shows an example of the System Setup window for Device Settings.

Figure 3-11. Dell System Setup: Device Settings

3. In the Device Settings window, select your device and then press ENTER.

The Main Configuration Page for the selected device appears. The Main Configuration Page is the top-level menu of the adapter configuration pages.

Figure 3-12 shows an example of the Main Configuration Page.

Figure 3-12. Dell System Setup: Main Configuration

57 BK3254601-00 C

Page 73

3–Fibre Channel Configuration Configuring the UEFI Driver

4. On the Main Configuration Page, select Port Configuration Page and press ENTER.

The Port Configuration Page appears; Figure 3-13 shows an example.

Figure 3-13. Dell System Setup: Port Configuration

5. Use the Port Configuration Page to change adapter operational parameters, such as port speed. In most cases, use the default values. Table 3-4 describes the configurable options on the Port Configuration Page.

Table 3-4. Port Configuration Page Settings

Setting Description

Device Name Indicates the name of the adapter.

Port Number Indicates the index of the selected port (1 to N).

Figure 3-13 shows port 1 in a two-port adapter.

Port Speed Indicates the data rate of the Fibre Channel adapter

port. This value can be automatic or specified in Gbps. The adapters support 8Gbps, 16Gbps, and 32Gbps.

Port Connection Mode Indicates the connection mode of the Fibre Channel

adapter port. The adapters support the following:

 Loop Only  Point to Point  Loop Preferred, Otherwise Point To Point

World Wide Node Name Indicates the adapter port’s unique worldwide node

name (WWNN).

58 BK3254601-00 C

Page 74

3–Fibre Channel Configuration Configuring the UEFI Driver

Table 3-4. Port Configuration Page Settings (Continued)

Setting Description

Virtual World Wide Node Name

World Wide Port Name Indicates the adapter port’s unique WWPN.

Virtual World Wide Port Name

Loop support is available only at port speeds up to and including 8Gbps. At 16Gbps and 32Gbps,

loop is not supported.

Indicates the adapter port’s unique virtual WWNN.

Indicates the adapter port’s unique virtual WWPN.

6. To return to the Main Configuration Page, click Back.

7. On the Main Configuration Page, select Firmware and Device Information, and then press ENTER.

The Firmware and Device Information page provides the adapter and firmware version information, and port address information. Figure 3-14 shows an example.

Figure 3-14. Dell System Setup: Firmware and Device Information

59 BK3254601-00 C

Page 75

3–Fibre Channel Configuration Configuring the UEFI Driver

Table 3-5 describes the Firmware and Device Information settings.

Table 3-5. Firmware and Device Information Settings

Setting Description

Chip Type Type of intelligent storage peripheral (ISP) controller

PCI Device ID Unique PCI device ID of the adapter.

Bus:Device:Function PCI address of the adapter in the Bus:Device:Function

Family Firmware Version Adapter firmware version information.

EFI Driver Version Adapter extensible firmware interface (EFI) driver ver-

8. To return to the Main Configuration Page, click Back.

used in the adapter.

(BDF) notation.

sion information.

9. On the Main Configuration Page, select Fibre Channel Target Configuration, and then press ENTER.

The Fibre Channel Target Configuration page appears. Figure 3-15 shows an example.

Figure 3-15. Fibre Channel Target Configuration

60 BK3254601-00 C

Page 76

3–Fibre Channel Configuration

NOTE

Configuring the UEFI Driver

10. On the Fibre Channel Target Configuration page, select SAN storage devices for boot from SAN. With selective boot scan enabled, the target configuration determines which target LUNs to map. All other devices are ignored. Table 3-6 describes the Fibre Channel Target Configuration settings.

Table 3-6. Fibre Channel Target Configuration Settings

Boot Scan Selection Specifies the adapter initiator behavior for booting

Setting Description

the system from the specified Fibre Channel storage target(s) or fabric discovered target(s).

First FC Target World Wide Port Name

First FC Target LUN Specifies the LUN of the first Fibre Channel storage

Second FC Target World Wide Port Name

Second FC Target LUN Specifies the LUN of the second Fibre Channel stor-

Specifies the WWPN of the first Fibre Channel storage target.

target.

Specifies the WWPN of the second Fibre Channel storage target.

age target.

System UEFI compatibility: To boot from a QLogic host 2700 Series Adapter in a computer system with a multiboot system UEFI, the 2700 Series Adapter must be included as the first device in the list of bootable devices in the system’s Boot menu.

11. To return to the Main Configuration Page, click Back.

12. On the Main Configuration Page, select HBA Configuration Page, and then press ENTER.

61 BK3254601-00 C

Page 77

3–Fibre Channel Configuration Configuring the UEFI Driver

The HBA Configuration Page appears; Figure 3-16 shows an example.

Figure 3-16. Dell System Setup: HBA Configuration

13. Use the HBA Configuration Page to configure adapter operational parameters. In most cases, use the default values.

Table 3-7 describes the fields on the HBA Configuration Page.

Table 3-7. HBA Configuration Page Settings

Setting Description

FC Tape Enable Enables or disables Fibre Channel protocol (FCP-2)

recovery.

Loop Reset Delay Specifies the Fibre Channel arbitrated loop reset

delay for the port. After resetting the loop, the adapter firmware refrains from initiating any loop activity for the number of seconds specified. The range is 0 to 60.

Frame Payload Size Specifies the maximum Fibre Channel frame payload

size.

Port Login Retry Count Specifies the number of times the adapter firmware

initiator tries to log in to a target device port. The range is 0 to 255.

Port Login Timeout Specifies the time-out in milliseconds that the initiator

uses when attempting to log in to the target device port. The range is 0 to 255000.

62 BK3254601-00 C

Page 78

3–Fibre Channel Configuration Setting an FA-PWWN

Table 3-7. HBA Configuration Page Settings (Continued)

Port Down Retry Count Specifies the number of seconds the software retries

Link Down Timeout Specifies the number of milliseconds the Fibre Chan-

14. Click Back to return to the Main Configuration Page window.

15. Click Finish to save your changes and exit.

Setting Description

a command to a port returning port-down status. The range is 0 to 255.

nel uplink port can be offline before the system is notified that the SAN fabric connectivity is lost and the uplink port is marked as being down. The range is 1 to 255000.

Setting an FA-PWWN

This section provides the following information for fabric-assigned port world wide (FA-PWWN) name:

 Setting the FA-PWWN from the Adapter

 Setting the FA-PWWN from the Brocade Switch

Setting the FA-PWWN from the Adapter

From the adapter side, you can set the FA-PWWN using the following utilities:

 Setting FA-PWWN with QConvergeConsole GUI

 Setting FA-PWWN with QConvergeConsole CLI

 Setting FA-PWWN with QConvergeConsole VMware Plug-ins

63 BK3254601-00 C

Page 79

3–Fibre Channel Configuration Setting an FA-PWWN

Setting FA-PWWN with QConvergeConsole GUI

To set the FA-PWWN from the adapter using QConvergeConsole GUI:

Before setting the FA-PWWN, the port name appears on the Port Info page as shown in the example in Figure 3-17.

Figure 3-17. Before Setting the FA-PWWN in the GUI

1. In the QConvergeConsole GUI tree pane on the left, select an adapter, expand the adapter node, and then select a port.

2. In the content pane on the right, click the Parameters tab.

3. On the Parameters page, click the Advanced HBA Parameters tab.

4. Under Configure Port Advanced Parameters, select the Enable Fabric Assigned WWN check box, and then click Save.

64 BK3254601-00 C

Page 80

3–Fibre Channel Configuration Setting an FA-PWWN

After refreshing the Brocade® switch, the Port Info page shows the Port Name as shown in Figure 3-18.

Figure 3-18. New FA-PWNN Port Name in GUI

Setting FA-PWWN with QConvergeConsole CLI

To set the FA-PWWN from the adapter using QConvergeConsole CLI:

1. In interactive mode of QConvergeConsole CLI, select Main Menu, and then click Adapter Configuration.

2. Select HBA Parameters.

3. Select the appropriate port.

4. Select Configuration HBA Parameters.

5. Select Enable Fabric Assign WWN.

6. On the Enable Fabric Assign WWN Menu, select 1: Enable.

7. Select the option to Commit Changes.

The following shows an example of setting the FA-PWWN:

HBA Desc. : QLE2742 QLogic 2-port 32Gb Fibre Channel Adapter

FW Version : 7.04.00

WWPN : 21-00-00-OE-1E-11-4A-38

WWNN : 21-00-00-OE-1E-11-4A-38

Link : Online

===============================================================

1: Connection Options

2: Data Rate

3: Frame Size

4: Enable HBA Hard Loop ID

5: Hard Loop ID

6: Loop Reset Delay (seconds)

65 BK3254601-00 C

Page 81

3–Fibre Channel Configuration Setting an FA-PWWN

7: Enable BIOS

8: Enable Fibre Channel Tape Support

9: Operation Mode

10: Interrupt Delay Timer (100 microseconds)

11: Execution Throttle

12: Login Retry Count

13: Port Down Retry Count

14: Enable LIP Full Login

15: Link Down Timeout (seconds)

16: Enable Target Reset

17: LUNs per Target

18: Enable Receive Out of Order Frame

19: Enable LR

20: Enable Fabric Assign WWN

21: Commit Changes

22: Abort Changes

(p or 0: Previous Menu; m or 98: Main Menu; ex or 99: Quit)

Please enter selection: 20

QConvergeConsole

Version 1.1.3 (Build 22)

Enable Fabric Assign WWN Menu

1: Enable

2: Disable (current)

(p or 0: Previous Menu; m or 98: Main Menu; ex or 99: Quit)

Please enter selection: 1

After refreshing the Brocade switch, the Adapter Information shows the port name as shown in the following example.

QConvergeConsole

CLI - Version 1.1.3 (Build 22)

FC Adapter Information

1: FC Adapter Information

2: FC Port Information

3: FC VPD Information

4: FC Target/LUN Information

5: FC VFC Information

(p or 0: Previous Menu; m or 98: Main Menu; ex or 99: Quit)

Please enter selection: 2

QConvergeConsole

CLI - Version 1.1.3 (Build 22)

Adapter Information

HBA Model QLE2742 SN: RFE12340H08416

66 BK3254601-00 C

Page 82

3–Fibre Channel Configuration Setting an FA-PWWN

1: Port 1: WWPN: 21-00-00-0F-1F-11-4A-30 Link Down

2: Port 2: WWPN: 50-00-53-37-63-FA-00-05 Online

Setting FA-PWWN with QConvergeConsole VMware Plug-ins

For information about setting a FA-PWWN using the QConvergeConsole VMware vCenter Server Plug-in or QConvergeConsole VMware vSphere Web Client Plug-in, see the section “Managing a Fibre Channel Adapter Port” in the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00).

Setting the FA-PWWN from the Brocade Switch

From the Brocade switch, you can set a FA-PWWN and a static FA-PWWN. For the most current information, refer to the Brocade switch documentation.

Setting the FA-PWWN from the Switch

Figure 3-19 shows the FA-PWWN setting from the Brocade switch.

Figure 3-19. Setting the FA-PWWN from the Brocade Switch

After refreshing the Brocade switch, the Device Port WWN appears in Web Tools as shown in Figure 3-20.

Figure 3-20. Device Port WWN for Brocade Switch

67 BK3254601-00 C

Page 83

3–Fibre Channel Configuration Configuring and Verifying FA-BLD

Setting the Static FA-PWWN from the Switch

Figure 3-21 shows the static FA-PWWN setting from the Brocade switch.

Figure 3-21. Setting the Static FA-PWWN from the Brocade Switch

After refreshing the Brocade switch, the Device Port WWN appears in Web Tools as shown in Figure 3-22.

Figure 3-22. Device Port WWN (Static) for Brocade Switch

Configuring and Verifying FA-BLD

This section provides the following information on fabric-assigned boot LUN discovery (FA-BLD):

 Configuring FA-BLD from the Adapter

 Verifying that FA-BLD is Operational

 Adapter Side Restrictions

Configuring FA-BLD from the Adapter

On the adapter side, follow these procedures to configure fabric-assigned boot LUN discovery (FA-BLD) in the QConvergeConsole GUI and QConvergeConsole CLI.

Enabling Host Bus Adapter Port BIOS and Fabric-assigned Boot LUN with QConvergeConsole GUI

To enable the Host Bus Adapter Port BIOS:

1. In QConvergeConsole GUI, select the Host tab in the left pane.

2. In the system tree, expand the adapter node and then select a port node.

68 BK3254601-00 C

Page 84

3–Fibre Channel Configuration Configuring and Verifying FA-BLD

3. In the content pane on the right, click the Parameters tab.

4. On the Parameters page, click the HBA Parameters tab.

5. Select the Enable HBA Port BIOS check box.

6. Click Save.

Figure 3-23 shows an example.

Figure 3-23. Enabling Host Bus Adapter Port BIOS

To enable fabric-assigned boot LUN:

1. In QConvergeConsole GUI, select the Host tab in the left pane.

2. In the system tree, expand the adapter node and then select a port node.

3. In the content pane on the right, click the Parameters tab.

4. On the Parameters page, click the Boot Device Selection tab.

5. Select the Enable Fabric Assigned Boot LUN check box.

6. Click Save.

69 BK3254601-00 C

Page 85

3–Fibre Channel Configuration Configuring and Verifying FA-BLD

Figure 3-24 shows an example.

Figure 3-24. Enabling Fabric-Assigned Boot LUN

Configuring the Adapter and Boot Devices with QConvergeConsole CLI

To configure adapter and boot devices:

1. In QConvergeConsole CLI, navigate to Adapter Configuration and then select HBA Parameters.

2. Enter the port number.

3. Select Configure HBA Parameters.

4. Select Enable BIOS and set it to Enable.

5. In the Adapter Configuration, select Boot Device Configuration.

6. Enter the port number.

7. Select Configure Boot Device(s).

8. Set the Enable Fabric Assign Boot LUN to Enable.

9. Select Commit Changes.

70 BK3254601-00 C

Page 86

3–Fibre Channel Configuration Configuring and Verifying FA-BLD

Figure 3-25 shows an example of the adapter and boot device configuration.

Figure 3-25. Configuring Adapter and Boot Device

Configuring a Zone in a Brocade Switch

To configure a zone in a Brocade switch:

1. Create a boot LUN configuration as follows:

bootluncfg --add 50:00:53:37:63:FA:00:05 20:02:00:11:0d:51:5c:01 0000000000000000

2. Create a zone named with the following:

 Device’s PWWN  Specific information about the target WWN  LUN to be booted from

3. Add a zone to the zoneset configuration as follows:

cfgadd config, "BFA_5000533763fa0005_BLUN"

4. To save the zoneset, issue the following command:

cfgsave

5. Enable zoneset configuration to have it actively running:

cfgenable config

71 BK3254601-00 C

Page 87

3–Fibre Channel Configuration Configuring and Verifying FA-BLD

Figure 3-26 shows an example of a configured zone in a Brocade switch.

Figure 3-26. Configuring a Zone in a Brocade Switch

Verifying that FA-BLD is Operational

To verify if the FA-BLD is operational, use either Fast!UTIL or the system.

Figure 3-27 shows Fast!UTIL displaying the boot LUN.

Figure 3-27. Verifying FA-BLD with Fast!UTIL

72 BK3254601-00 C

Page 88

3–Fibre Channel Configuration Using a Fabric-Assigned Boot LUN

Figure 3-28 shows using the system, with a LUN ready to install or OS booted

from LUN.

Figure 3-28. Verifying FA-BLD from the System

Adapter Side Restrictions

The known fabric-assigned port world wide name (FA-PWNN) and FA-BLD restrictions include the following:

 Cannot be fully enabled from Fast!UTIL

 Do not use Restore Defaults from Fast!UTIL, QConvergeConsole GUI, or

QConvergeConsole CLI. Doing so causes these capabilities to become disabled.

Using a Fabric-Assigned Boot LUN

This section describes how to use a fabric-assigned boot LUN in the following utilities:

 Using a Fabric-Assigned Boot LUN in QConvergeConsole GUI

 Using a Fabric-Assigned Boot LUN in Interactive QConvergeConsole CLI

73 BK3254601-00 C

Page 89

3–Fibre Channel Configuration Using a Fabric-Assigned Boot LUN

 Using a Fabric-Assigned Boot LUN with Noninteractive QConvergeConsole

CLI

 Using a Fabric-Assigned Boot LUN with QConvergeConsole Plug-ins

Using a Fabric-Assigned Boot LUN in QConvergeConsole GUI

For details about how to use a fabric-assigned LUN in QConvergeConsole GUI, refer to the “Fabric-Assigned Boot LUN” topic in the QConvergeConsole Help.

Using a Fabric-Assigned Boot LUN in Interactive QConvergeConsole CLI

To use a fabric-assigned boot LUN with interactive QConvergeConsole CLI:

1. From the main menu, select the adapter type (Fibre Channel Adapter).

2. On the Fibre Channel Adapter Configuration menu, select Boot Devices Configuration.

appears.

3. On the Boot Device Settings menu, select Configure Boot Device(s), and then press the ENTER key.

4. Select Enable Fabric Assigned Boot LUN, and then press ENTER.

5. On the Enable Fabric Assign Boot LUN menu, type 1 to enable this feature.

Using a Fabric-Assigned Boot LUN with Noninteractive QConvergeConsole CLI

In noninteractive QConvergeConsole CLI, set a target as the fabric-assigned boot LUN for a specific adapter by issuing the following command:

# qaucli -pr fc -e <hba instance>|<hba wwpn> enable|disable FabricAssignBootLUN|fb

Where:

hba instance = Adapter number (use the -g command to find)

hba wwpn = Worldwide port name of the adapter

FabricAssignBootLUN or fb = Configure enable fabric-assigned boot LUN setting

74 BK3254601-00 C

Page 90

3–Fibre Channel Configuration Using a Fabric-Assigned Boot LUN

Using a Fabric-Assigned Boot LUN with QConvergeConsole Plug-ins

For information about using a fabric-assigned boot LUN for QConvergeConsole VMware vSphere Web Client Plug-in, see the section “Configure Fibre Channel Port Boot Parameters” in the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00).

To configure a 2700 Series Adapter boot device with QConvergeConsole VMware vCenter Server Plug-in:

1. In the QConvergeConsole VMware vCenter Server Plug-in, click the QConvergeConsole tab.

2. In the tree pane on the left, select a 2700 Series Adapter port.

3. Click the Boot tab.

4. On the Boot Device Selection page, select the Enable Fabric Assigned Boot LUN check box. Figure 3-29 shows an example.

Figure 3-29. Fabric-Assigned Boot LUN in QConvergeConsole VMware vCenter

Server Plug-in

For details, refer to the “Boot Device Selection” topic in QConvergeConsole Help.

75 BK3254601-00 C

Page 91

3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route

5. Click Save.

Any previously saved configuration for the current 2700 Series Adapters is overwritten.

Running Diagnostics—Fibre Channel Ping and Trace Route

This section provides the following information on how to run Fibre Channel ping and trace route diagnostics:

 Pinging and Viewing Trace of Routing Using Topology Map

 Running a Fibre Channel CT Ping Test

 Fibre Channel Trace Route

Pinging and Viewing Trace of Routing Using Topology Map

The QConvergeConsole GUI topology map uses the common transport (CT) layer to enable the adapter’s initiator port to ping or run a trace route that will navigate across the environment through multiple ports of the switch or switches and to the target.

Table 3-8 compares the differences between the Ping Test, CT Ping Test, and the

CT FTR Tests.

Table 3-8. Ping Test, CT Ping Test, and CT FTR Test

Ping Test CT Ping Test CT FTR Test

SCSI layer ping CT or Fibre Channel ping CT or Fibre Channel trace route

Uses SCSI inquiry command Uses echo through an external

link

Can operate on any SCSI device Can operate with all Fibre Chan-

nel devices that support CT or an external link

Requires scan of physical topology

Can operate with all devices that are connected through a port that supports CT or an external link

76 BK3254601-00 C

Page 92

3–Fibre Channel Configuration

NOTE

Running Diagnostics—Fibre Channel Ping and Trace Route

Supported configurations for Fibre Channel ping and trace route include:

 QLogic 2700 Series Adapters

 Brocade Switches with Based Fabric OS

(FOS) v6.0.0a

The switch and the Fibre Channel end device must both support the Fibre Channel ping and trace route feature. See Table 3-10 on page 93 for the supported Fibre Channel software version.

Running a Fibre Channel CT Ping Test

You can run a Fibre Channel CT ping test from QConvergeConsole GUI, QConvergeConsole CLI, or the QConvergeConsole VMware plug-ins, as described in this section.

Running a Fibre Channel CT Ping from QConvergeConsole GUI

To run a Fibre Channel CT ping test from QConvergeConsole GUI:

1. In the QConvergeConsole GUI left pane, click the Host tab.

2. On the Host page, expand the adapter node and then select a port.

3. In the content pane on the right, click the Diagnostics tab.

4. On the Diagnostics page, click the General Diagnostics tab.

77 BK3254601-00 C

Page 93

3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route

5. On the General Diagnostics page (see Figure 3-30), complete the Test Configuration options, and then click CT Ping Test to start the test.

Figure 3-30. Running the Fibre Channel CT Ping Test

A caution message appears for the diagnostic CT ping test (Figure 3-31).

Figure 3-31. CT Ping Test Caution

6. Ensure that the port has no active I/O operations, and then either click Yes to proceed or No to cancel the test.

78 BK3254601-00 C

Page 94

3–Fibre Channel Configuration

NOTE

Running Diagnostics—Fibre Channel Ping and Trace Route

Running a Fibre Channel CT Ping from QConvergeConsole CLI

To run a Fibre Channel CT ping test from QConvergeConsole CLI:

1. From the QConvergeConsole CLI FC Diagnostics menu, select 7: CT Ping Test.

2. From the HBA Model list, select the port that you want to ping.

3. From the CT Ping Test menu, select 4: Start Diagnostic Test.

The following shows example output from the CT ping test.

----------------------------------------------

Diagnostics Test Configuration

----------------------------------------------

Diagnostic Mode : CT Ping Number of tests (1-10000) : 10 Number of Pass : 1 Test Increment (1-10000) : 1 Abort On Error : Ignore Test Continuous : OFF

---------------------------------------------------

ID Data Link Sync Signal Invalid Diagnostic

Port/Loop Miscompare Failure Loss Loss CRC Status

--------- ---------- ------- -------- --------- --------- ----------

01-0B-01 0 0 0 0 0 Success

The default setting will repeat 10 times with output similar to the preceding for each pass of the test.

Running a Fibre Channel CT Ping from QConvergeConsole VMware Plug-ins

For information about running Fibre Channel CT ping from the QConvergeConsole VMware vCenter Server Plug-in or QConvergeConsole VMware vSphere Web Client Plug-in, see the section “Diagnostic Tests—Fibre Channel Port” in the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00).

Fibre Channel Trace Route

To run a Fibre Channel trace route from QConvergeConsole GUI:

1. In the system tree pane on the left, click the Host tab.

2. In the content pane on the right, click the Topology tab.

3. Next to Topology, select the Physical option.

4. In the topology map, right-click the applicable adapter.

5. Select the FC Trace Route option.

79 BK3254601-00 C

Page 95

3–Fibre Channel Configuration

NOTE

Running Diagnostics—Fibre Channel Ping and Trace Route

6. In the Target Selection dialog box, select the target to run the trace route.

7. Click Trace.

Figure 3-32 shows an example.

Figure 3-32. Running Fibre Channel Trace Route from QConvergeConsole GUI

The Fibre Channel trace route output from QConvergeConsole GUI shows a symbol of a red payload that starts from the host. The travel across the route is also highlighted in red. The payload enters and exits from the appropriate port on each switch as it traverses the path until it reaches the selected target.

The results appear as a success message output from the following:

 QConvergeConsole GUI  QConvergeConsole CLI  Diagnostics area

You can also execute the CT FTR test.

80 BK3254601-00 C

Page 96

3–Fibre Channel Configuration

NOTE

Configuring CS_CTL QoS

For information about using Fibre Channel trace route in QConvergeConsole VMware vCenter Server Plug-in or QConvergeConsole VMware vSphere Web Client Plug-in, see the section “Diagnostic Tests—Fibre Channel Port” in the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00).

Configuring CS_CTL QoS

For information about end-to-end CS_CTL QoS, see “Configuring

End-to-End CS_CTL QoS” on page 84.

This section provides the following information on class-specific control (CS_CTL) quality of service (QoS):

 CS_CTL QoS Features

 Enabling CS_CTL QoS Mode for the Initiator and Target Ports

 Verifying and Confirming CS_CTL Mode Setup for Each Port

 Creating a Virtual Port from the Adapter’s Port in QConvergeConsole GUI

 Setting the QoS Priority Level for a Virtual Port in QConvergeConsole GUI

CS_CTL QoS Features

The following highlights some of the features of the CS_CTL QoS:

 Traffic priority classification for QLogic Gen6 Fibre Channel SAN. QoS at the

packet level is realized by using the CS_CTL field, which is specified in the FC-FS-2 specification. QoS allows one to prioritize frames between a host and target, depending on the value of the CS_CTL field in the FC Frame header.

 Extending QoS from the fabric to the host

 Enables QLogic Fibre Channel users to rapidly scale server virtualization

without compromising service-level agreements

 Benefits for both physical and virtual server deployments

 Supported configuration:

 QLogic 2700 Series Adapters

 CS_CTL-based QoS is end-to-end (requires target to support

CS_CTL)

81 BK3254601-00 C

Page 97

3–Fibre Channel Configuration Configuring CS_CTL QoS

Enabling CS_CTL QoS Mode for the Initiator and Target Ports

Figure 3-33 shows how to enable CS_CTL QoS mode for the initiator and target

ports.

Figure 3-33. Enabling CS_CTL QoS Mode

Verifying and Confirming CS_CTL Mode Setup for Each Port

Figure 3-34 shows how to verify the CS_CTL mode setup for each port.

Figure 3-34. CS_CTL Mode Setup for Each Port

Creating a Virtual Port from the Adapter’s Port in QConvergeConsole GUI

To create a virtual port in QConvergeConsole GUI:

1. In the QConvergeConsole GUI content pane on the left, select the Host tab.

2. On the Host page, expand the adapter node, and then select a port.

3. In the content pane on the right, select the Virtual tab.

4. On the Virtual page under Create New Virtual Port, specify the Number of vPort to create, and then click Update.

5. Click Create.

82 BK3254601-00 C

Page 98

3–Fibre Channel Configuration Configuring CS_CTL QoS

Figure 3-35 shows how to create a virtual port from the adapter’s port in

QConvergeConsole GUI.

Figure 3-35. Creating a Virtual Port

83 BK3254601-00 C

Page 99

3–Fibre Channel Configuration

NOTE

Configuring End-to-End CS_CTL QoS

Setting the QoS Priority Level for a Virtual Port in QConvergeConsole GUI

Figure 3-36 shows how to set the QoS priority level for a virtual port in

QConvergeConsole GUI.

Figure 3-36. Setting the QoS Priority Level

By default, the QoS of the physical port is set to High, and the QoS of the virtual port is set to Low.

Configuring End-to-End CS_CTL QoS

For information about CS_CTL QoS that is not end-to-end, see “Configuring

CS_CTL QoS” on page 81.

QLogic’s class specific control (CS_CTL) QoS implementation is an end-to-end solution, encompassing the initiator (2700 Series Adapters), the switches, and the target (storage). The 2700 Series Adapter stamps the priority value (high, medium, low) in the CS_CTL field of the Fibre Channel frame. All three entities (initiator, switch, and target) honor this priority value at their respective levels.

84 BK3254601-00 C

Page 100

3–Fibre Channel Configuration

NOTE

Configuring End-to-End CS_CTL QoS

Therefore, when all three entities support QoS (and it is enabled on the switch and the target), a default priority value is populated in all FCP_CMND, FCP_DATA, FCP_XFER_RDY, FCP_RSP, and FCP_CONFIRM frames.

QoS must be supported by both the switch and target devices. At the time of publication, CS_CTL QoS has been tested only on the

Brocade SW6510 switch with Fabric OS (FOS) version 7.3.0a.

The following sections describe how to configure end-to-end CS_CTL QoS and change the default priority levels:

 Configuring CS_CTL QoS on the Switch

 Configuring CS_CTL QoS on the Storage Device

 Changing the QoS Priority Levels

Configuring CS_CTL QoS on the Switch

To enable CS_STL QoS on the Brocade SW6510 switch:

1. From the switch, issue the following command:

root> configurechassis

Configure...

2. A list of attributes appear one at a time. After either accepting the default or entering a different value, the next attribute appears.

 Press ENTER to accept the default for cfgload attributes,

Custom attributes, and system attributes.

 Type y for fos attributes.

 Type 1 for CSCTL QoS Mode.

For example:

cfgload attributes (yes, y, no, n): [no]

Custom attributes (yes, y, no, n): [no]

system attributes (yes, y, no, n): [no]

fos attributes (yes, y, no, n): [no] y

CSCTL QoS Mode (0 = default; 1 = auto mode): (0..1) [0] 1

3. Reboot the switch.

4. To verify that CS_CTL QoS is enabled, issue the following command:

root> configshow -all | grep fos.csctlMode

85 BK3254601-00 C

Qlogic QLE2740L-DEL, QLE2740-DEL, QLE2742-DEL, QLE2742L-DEL User Manual

Table of Contents

Introduction

Intended Audience

User’s Guide Content

Related Materials

Documentation Conventions

Functionality and Features

Functional Description

Key Features

Supported Operating Systems

Windows

Linux

VMware

Citrix XenServer

1 Hardware Installation

Hardware and Software Requirements

Safety Precautions

Pre-Installation Checklist

PCIe Bus Slot Considerations

Installing the Adapter

Connecting to the SAN

Windows Driver Installation and Configuration

Running the Dell Update Package in the GUI

Running the Dell Update Package from the Command Line

Examples

Linux Driver Installation and Configuration

Installation Overview

Installing the Linux Fibre Channel Driver

Building the Driver for RHEL 6.x and 7.x

Building the Driver for SLES 11

Building the Driver for SLES 12

VMware Driver Installation and Configuration

Installation Overview

Installing the ESXi 6.5 and 6.0 U2 Fibre Channel Driver

Updating an Existing Driver or Installing a New Driver for an Existing ESXi 6.5 or 6.0 U2 Installation with esxcli

Verifying the Version of the Installed Driver

Installing QConvergeConsole VMware vCenter Server Plug-in

Installation Package Contents

Installing QConvergeConsole VMware vCenter Server Plug-in

Plug-in Unregistration from a Manual Install

Uninstalling the QConvergeConsole VMware vCenter Server Plug-in

Installing the QLogic Adapter CIM Provider

Uninstalling the QLogic Adapter CIM Provider

Installing QConvergeConsole VMware vSphere Web Client Plug-in

Uninstalling the QConvergeConsole VMware vCenter Server Plug-in

Fibre Channel Configuration

Updating the Dell Firmware

Running the Firmware Update by Double-Clicking

Running the Firmware Update from the Command Line

Using Fast!UTIL for Custom Configuration

Configuration Settings

Adapter Settings

Selectable Boot Settings

Restore Default Settings

Raw NVRAM Data

Advanced Adapter Settings

Scan Fibre Devices

Fibre Disk Utility

Loopback Data Test

Select Adapter

Exit Fast!UTIL

Setting Fibre Channel Adapter Parameters

Setting Fibre Channel Adapter Parameters with QConvergeConsole GUI

Setting Fibre Channel Adapter Parameters with Interactive QConvergeConsole CLI

Setting Fibre Channel Adapter Parameters with Noninteractive QConvergeConsole CLI

Configuring Target Persistent Binding

Configuring Persistent Binding with QConvergeConsole GUI

Configuring Persistent Binding with Interactive QConvergeConsole CLI

Configuring Persistent Binding with Noninteractive QConvergeConsole CLI

Configuring Boot Devices

Configuring Boot Devices with QConvergeConsole GUI

Configuring Boot Devices with Interactive QConvergeConsole CLI

Configuring Boot Devices with Noninteractive QConvergeConsole CLI

Configuring Boot Devices with the BIOS

Configuring Virtual Ports (NPIV)

Configuring NPIV with QConvergeConsole GUI

Configuring NPIV with Interactive QConvergeConsole CLI

Configuring NPIV with Noninteractive QConvergeConsole CLI

Configuring NPIV Quality of Service