Q-Logic 8200 SERIES, IS0054604-00 A User Manual

Loading...

User’s Guide IOCTL to Open-iSCSI Interface

QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters

IS0054604-00 A

User’s Guide—IOCTL to Open-iSCSI Interface

QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters

Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.

Document Revision History

Revision A, June 19, 2012

Changes

Sections Affected

Initial release

ii

IS0054604-00 A

Table of Contents

Preface

 

What is in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vii

 

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vii

 

Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii

 

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii

 

Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ix

 

Downloading Firmware and Documentation . . . . . . . . . . . . . . . . . . . .

ix

 

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

x

 

Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

x

 

Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

x

1

Legacy vs. Open-iSCSI

 

 

Summary of Major Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2

 

Functional Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7

 

Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

 

Target Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-10

 

Session Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-11

 

State Transition Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-13

2

Boot from SAN

 

 

New Parameter: ql4disablesysfsboot . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

 

Boot from SAN Configuration Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

 

Configuring Boot from SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4

 

Boot from SAN Installation on SLES 11 SP2 and RHEL 6.2 . . . . . . . .

2-4

 

Boot from SAN Installation on SLES 11 SP2. . . . . . . . . . . . . . . . . . . .

2-13

 

Configuring Boot from SAN on RHEL 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . .

2-19

 

Installing RHEL 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-19

 

ql4xdisablesysfsboot Settings and Adapter Boot Mode . . . . . . . . . . . . . . . .

2-33

3

Open-iSCSI User’s Guide

 

 

Open-iSCSI Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

 

Discovery, Login, and Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

IS0054604-00 A

iii

User’s Guide—IOCTL to Open-iSCSI Interface

QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters

 

 

 

 

 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Boot Target Login

3-2

 

Default Behavior on RHEL 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

 

Default Behavior on SLES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . .

3-3

 

Persistence through Flash and Open-iSCSI Database . . . . . . . . . . . .

3-3

 

Managing QLogic iSCSI Adapters Using iscsiadm . . . . . . . . . . . . . . . . . .

3-4

 

iSCSI Configuration Files and Persistent Databases . . . . . . . . . . . . .

3-4

 

Configuring Targets for qla4xxx Using Open-iSCSI . . . . . . . . . . . . .

3-4

 

iSCSI Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6

 

iSCSI Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . .

3-6

 

List All ifaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-7

 

Display iface Configuration Details . . . . . . . . . . . . . . . . . . . . . . .

3-8

 

Create an iface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-8

 

Update iface Network Parameters . . . . . . . . . . . . . . . . . . . . . . .

3-9

 

Unidirectional and Bidirectional CHAP settings . . . . . . . . . . . . .

3-11

 

Target Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-12

 

Discover Targets using sendtarget . . . . . . . . . . . . . . . . . . . . . . .

3-12

 

Adding a New discoverydb for sendtarget . . . . . . . . . . . . . . . . .

3-13

 

Remove sendtarget Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-14

 

Adding and Deleting Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-14

 

Adding a New Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-14

 

List All Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-15

 

Deleting a Target Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-15

 

Target Login and Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-15

 

Login to a Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-15

 

Login to All Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-16

 

Login All Sessions with Specified Parameters . . . . . . . . . . . . . .

3-16

 

Logout from a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-16

 

Logout from All Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-16

 

Features Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-17

 

Migrating to Open-iSCSI Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-17

 

Linux Open-iSCSI README . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-18

4

Known Issues

 

Figure

 

List of Figures

Page

 

 

1-1

Noninteractive Discovery in IOCTL Mode (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

1-2

Interactive Discovery in IOCTL Mode (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

1-3

Open-iSCSI Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

1-4

IOCTL iSCSI Target Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-10

iv

IS0054604-00 A

User’s Guide—IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters

 

 

 

1-5

. . . . . . . . . . . . . . . . . . . . . . . . . . .Open-iSCSI Target Login

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

1-6

IOCTL Session Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1-7

Open-iSCSI Session Recovery . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 1-12

1-8

IOCTL State Transition Diagram . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 1-13

1-9

Open-iSCSI State Transition Diagram . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 1-14

2-1

Entering Fast!UTIL from the Adapter’s BIOS. . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-4

2-2

Selecting the Port to Be Configured. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-5

2-3

Fast!UTIL Options Menu—Selecting Configuration Settings

. . . . . . . . . . . . . . . . . . 2-5

2-4

Selecting the Host Adapter Settings Option. . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-6

2-5

Selecting the Initiator IP Settings . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-6

2-6

Providing the Initiator IP Address. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-7

2-7

Configuration Settings Menu . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-7

2-8

Selecting Primary Boot Device Settings. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-8

2-9

Providing Target IP Address for Primary Boot Device . . . . .

. . . . . . . . . . . . . . . . . . 2-8

2-10

Selecting Alternate Boot Device Settings. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-9

2-11

Providing Target IP Address for Alternate Boot Device . . . .

. . . . . . . . . . . . . . . . . . 2-9

2-12

Fast!UTIL Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-10

2-13

Selecting the Primary LUN. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-10

2-14

List of Devices on the Port . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-11

2-15

Editing Alternate Boot Device Settings . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-11

2-16

Setting the Boot Mode to Manual. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-12

2-17

Entering the Boot BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-13

2-18

Providing the withiscsi Boot Option . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-13

2-19

Installation Welcome Screen . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-14

2-20

Media Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-14

2-21

iSCSI Initiator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-15

2-22

Selecting System Probing . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-15

2-23

Selecting the Installation Mode . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-16

2-24

Setting the Clock and Time Zone. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-16

2-25

Selecting the Server Base Scenario . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-17

2-26

Preparing the Hard Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-17

2-27

Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-18

2-28

Booting From the Installation Media. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-19

2-29

Choosing to Test Media Disk or Skip Test . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-19

2-30

Selecting Network Interface for Installation . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-20

2-31

Configuring the IP Address . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-20

2-32

Start of RHEL 6.2 Installation . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-21

2-33

Selecting the Language for the Installation . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-22

2-34

Selecting the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-23

2-35

Selecting Storage Device Type . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-24

2-36

Verifying Paths to the Disk . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-25

2-37

Specifying the Host Name . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-26

2-38

Selecting the Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-27

2-39

Entering the Root Credentials . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-28

2-40

Selecting the Partition Layout Type . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . 2-29

IS0054604-00 A

v

User’s Guide—IOCTL to Open-iSCSI Interface

QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters

 

 

 

 

2-41

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Selecting the Installation Type

2-30

2-42

Installation in Progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-31

2-43

Installation Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-32

List of Tables

Table

 

Page

1-1

Differences Between IOCTL and Open-iSCSI Driver Models . . . . . . . . . . . . . . . . .

1-2

2-1

Boot from SAN Configuration Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

2-2

Configurations and Tools for Checking iSCSI Sessions. . . . . . . . . . . . . . . . . . . . . .

2-33

3-1

Configuration and Persistent Database Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4

3-2

Hardware iSCSI Interface Config File Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6

vi

IS0054604-00 A

Preface

Starting with Red Hat® Enterprise Linux® (RHEL™) 6.2 and Novell® SUSE® Linux Enterprise Server (SLES®) 11 SP2, the QLogic qla4xxx driver (iSCSI driver for Linux) supports the Open-iSCSI tool iscsiadm. As a result, iscsiadm can now be used to perform management functions (configuring network settings, managing iSCSI targets, and so on) on QLogic 4000 Series 1GbE iSCSI Adapters and 8200 Series 10GbE Converged Network Adapters.

What is in This Guide

This document describes the differences between the legacy (IOCTL-based) and Open-iSCSI management models of the QLogic qla4xxx driver, and provides brief guidelines for migrating from the legacy to the Open-iSCSI model.

This preface specifies the intended audience, lists related documents, describes the typographic conventions used in this guide, and provides technical support and contact information.

The remainder of this user’s guide is organized into the following chapters:

Section 1 Legacy vs. Open-iSCSI describes the major differences between the legacy driver which has an IOCTL-based interface for user space application communications, and the Open-iSCSI model.

Section 2 Boot from SAN provides information on configuring Boot from SAN (BFS) when migrating to the Open-iSCSI model.

Section 3 Open-iSCSI User’s Guide provides a User’s Guide for Open-iSCSI.

Section 4 Known Issues provides a list of currently known issues.

Intended Audience

This document is intended for end users who manage QLogic 4000 Series iSCSI adapters or 8200 Series Converged Network Adapters on Linux (RHEL 6.2, SLES 11 SP2, or later), using the IOCTL-based management model.

IS0054604-00 A

vii

Preface

Related Materials

Related Materials

For additional information, refer to the following:

Technical Note, 2.10. Kernel

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_T echnical_Notes/kernel_issues.html

Release Notes for SUSE Linux Enterprise Server 11 Service Pack 2 http://www.novell.com/linux/releasenotes/i386/SUSE-SLES/11-SP2/

Linux Open-iSCSI README http://www.open-iscsi.org/docs/README

Documentation Conventions

This guide uses the following documentation conventions:

NOTE provides additional information.

Text in blue font indicates a hyperlink (jump) to a figure, table, or section in this guide, and links to Web sites are shown in underlined blue. For example:

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

See “Installation Checklist” on page 3-6.

For more information, visit www.qlogic.com.

Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings. For example:

Click the Start button, point to Programs, point to Accessories, and then click Command Prompt.

Under Notification Options, select the Warning Alarms check box.

Text in Courier font indicates a file name, directory path, or command line text. For example:

To return to the root directory from anywhere in the file structure: Type cd /root and press ENTER.

Enter the following command: sh ./install.bin

Key names and key strokes are indicated with UPPERCASE:

Press CTRL+P.

Press the UP ARROW key.

viii

IS0054604-00 A

Preface

Technical Support

Text in italics indicates terms, emphasis, variables, or document titles:

For a complete listing of license agreements, refer to the QLogic Software End User License Agreement.

What are shortcut keys?

To enter the date type mm/dd/yyyy (where mm is the month, dd is the day, and yyyy is the year).

Topic titles between quotation marks identify related topics either within this manual or in the online help, which is also referred to as the help system throughout this document.

Technical Support

Customers should contact their authorized maintenance provider for technical support of their QLogic products. QLogic-direct customers may contact QLogic Technical Support; others will be redirected to their authorized maintenance provider. Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.

For details about available service plans, or for information about renewing and extending your service, visit the Service Program web page at http://www.qlogic.com/services.

Downloading Firmware and Documentation

To download firmware and documentation:

1.Go to the QLogic Downloads and Documentation page: http://driverdownloads.qlogic.com.

2.Under QLogic Products, type the QLogic model name in the search box.

Alternatively, you can click Guided Search to obtain assistance in locating the firmware and documentation to download.

3.In the search results list, locate and select the firmware and documentation, for your product.

4.View the product details Web page to ensure that you have the correct firmware and documentation.

Click the Read Me and Release Notes icons under Support Files for additional information.

5.Click Download Now.

6.Save the file to your computer.

7.If you have downloaded firmware, follow the installation instructions in the

Readme file.

IS0054604-00 A

ix

Preface

Technical Support

Training

QLogic Global Training maintains a Web site at www.qlogictraining.com offering online and instructor-led training for all QLogic products. In addition, sales and technical professionals may obtain Associate and Specialist-level certifications to qualify for additional benefits from QLogic.

Contact Information

QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays. For customers with extended service, consult your plan for available hours. For Support phone numbers, see the Contact Support link at support.qlogic.com.

Support Headquarters

QLogic Corporation

 

4601 Dean Lakes Blvd.

 

Shakopee, MN 55379 USA

QLogic Web Site

www.qlogic.com

Technical Support Web Site

http://support.qlogic.com

Technical Support E-mail

support@qlogic.com

Technical Training E-mail

training@qlogic.com

Knowledge Database

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

x

IS0054604-00 A

1 Legacy vs. Open-iSCSI

This section describes the major differences between the legacy driver which has an IOCTL-based interface for user space application communications, and the Open-iSCSI model.

This section includes the following topics:

“Summary of Major Differences” on page 1-2

“Functional Flows” on page 1-7

“State Transition Diagrams” on page 1-13

IS0054604-00 A

1-1

1–Legacy vs. Open-iSCSI Summary of Major Differences

Summary of Major Differences

Table 1-1 summarizes the major differences between the legacy IOCTL-based and Open-iSCSI models.

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

1

Firmware

Firmware is configured in

Firmware is configured in NON

 

 

Operational

AUTO CONNECT

AUTO CONNECT MODE. In

 

 

Mode

MODE. In this mode:

this mode:

 

 

 

The firmware reads

The driver reads the DDB

 

 

 

the DDB entries from

entries from the predefined

 

 

 

the predefined area in

area in the Flash.

 

 

 

the Flash.

For a Send Target the

 

 

 

 

 

 

 

For a Send Target the

driver initiates a discovery

 

 

 

firmware initiates dis-

session through the mail-

 

 

 

covery, discovers the

box command, queries the

 

 

 

target, and initiates

firmware for discovered tar-

 

 

 

login to the discov-

gets, and then initiates

 

 

 

ered target.

login to the targets using

 

 

 

The firmware posts an

the mailbox command.

 

 

 

AEN to the driver,

The firmware posts an AEN

 

 

 

identifying each dis-

to the driver to report login

 

 

 

covered target.

status after login completes.

 

 

 

For the DDBs that rep-

For DDBs which represent

 

 

 

resent a Normal tar-

a Normal Target, driver initi-

 

 

 

get, the firmware logs

ates login using mailbox

 

 

 

into them and posts an

command. Then, the firm-

 

 

 

AEN to the driver to

ware posts an AEN to the

 

 

 

report the login status.

driver to report the login

 

 

 

 

status after login com-

 

 

 

 

pletes.

 

 

 

 

 

 

2

Target

Persistence is main-

Persistence is maintained by

 

 

Persistence

tained by storing Discov-

storing Discovery Target and

 

 

 

ery Target and Normal

Normal Target records in the

 

 

 

Target records on the

local file system using the

 

 

 

adapter Flash using the

iscsiadm tool.

 

 

 

QLogic application a.

 

 

1-2

IS0054604-00 A

1–Legacy vs. Open-iSCSI Summary of Major Differences

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

3

Boot Target

During driver load, the

Login to boot targets is trig-

Note: For more

 

 

firmware performs auto

gered by the driver, or the user

details on adapter

 

 

discovery and login to the

space is dependent on the

mode and the

 

 

boot targets based on the

ql4xdisablesysfsboot

ql4xdisables-y

 

 

target information saved

driver command line parame-

sfsboot driver,

 

 

in the Flash, and posts an

ter:

refer to “Configur-

 

 

AEN to inform the driver

For RHEL 6.2 it is enabled

ing Boot from SAN

 

 

of the targets and their

by default, so that the driver

on RHEL 6.2” on

 

 

login status.

initiates the login.

page 2-19.

 

 

 

 

 

 

 

For SLES 11 SP2 it is dis-

 

 

 

 

abled by default, so that

 

 

 

 

yast2-iscsi-client

 

 

 

 

must be used to perform

 

 

 

 

login.

 

 

 

 

 

 

4

Re-login

Session management or

Re-login is handled either by

Session re-login is

 

Handling

re-login is handled by the

iscsiadm and iscsid, or by

also initiated on

 

 

driver.

the driver, depending how the

chip or adapter

 

 

 

session is initiated:

reset.

 

 

 

If iscsiadm created the

 

 

 

 

session, session manage-

 

 

 

 

ment is handled using

 

 

 

 

iscsid (in other words,

 

 

 

 

handled by the user space).

 

 

 

 

For the target record which

 

 

 

 

is persistent in the Flash,

 

 

 

 

the driver initiates the ses-

 

 

 

 

sion and is responsible for

 

 

 

 

re-login or session man-

 

 

 

 

agement.

 

 

 

 

 

 

5

Network con-

Adapter ports are config-

Adapter ports are configured

 

 

figuration

ured using the QLogic

using iscsiadm for network

 

 

 

applicationa.

configuration. By default,

 

 

 

 

iscsiadm creates an iface

 

 

 

 

for each QLogic adapter port.

 

 

 

 

The iface name is of the form

 

 

 

 

qla4xxx.00:0e:1e:04:8b:2e

 

 

 

 

. You can change or update

 

 

 

 

the network setting for the port

 

 

 

 

using various iface parameters

 

 

 

 

and iface operations.

 

 

 

 

 

 

IS0054604-00 A

1-3

1–Legacy vs. Open-iSCSI Summary of Major Differences

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

6

How to view

Qlogic applicationa

Use the following command:

 

 

sessions

 

iscsiadm -m session

 

 

logged in

 

 

 

 

 

 

 

 

 

 

 

7

Target scan-

Login and target scanning

Login and target scanning is

 

 

ning

is done in kernel space as

done by user space as follows:

 

 

 

follows:

1. When the driver receives

 

 

 

 

 

 

 

1. When the driver

an AEN for the DDB indi-

 

 

 

receives an AEN for

cating that the target is

 

 

 

the DDB indicating

logged in, it sends an event

 

 

 

that the target is

to the iscsid (user

 

 

 

logged in, the driver

space) indicating that the

 

 

 

publishes the session

session is in the logged-in

 

 

 

to the iSCSI transport

state.

 

 

 

layer and unblocks the

2. iscsid then unblocks the

 

 

 

session.

session and kicks off the

 

 

 

 

 

 

 

2. This triggers the SCSI

target/LUN scanning.

 

 

 

midlayer LUN scan-

 

 

 

 

ning to discover all

 

 

 

 

LUNs behind the tar-

 

 

 

 

get.

 

 

 

 

 

 

 

8

Link Down

No change in the behav-

No change in the behavior of

 

 

impact on

ior of session and SCSI

session and SCSI device state

 

 

SCSI Device

device state handling.

handling.

 

 

Handling

The default session

For Open-iSCSI, default

 

 

 

 

 

 

recovery time-out is equal

recovery time-out is 120 sec-

 

 

 

to the firmware keep alive

onds. This can be configured

 

 

 

timeout. The default value

on an individual session basis

 

 

 

is 30 seconds. This can

dynamically; that is, it does not

 

 

 

be modified by the driver

require driver unload.

 

 

 

command line parameter

Session recovery time-out can

 

 

 

ql4xkeepalive.

 

 

 

be configured by modifying the

 

 

 

 

replacement_timeout

 

 

 

 

parameter in the node record.

 

 

 

 

 

 

1-4

IS0054604-00 A

1–Legacy vs. Open-iSCSI Summary of Major Differences

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

9

Dynamic

The driver handles the

No explicit support to dynami-

 

 

map-

following check condi-

cally discover newly added

 

 

ping/unmap-

tion/sense data:

LUNs on the back-end stor-

 

 

ping of LUNs

UNIT_ATTENTION

age. Requires manual rescan-

 

 

added to the

ning using iscsiadm

 

 

ASC/ASCQ : 0x3F/0x0E

 

 

back-end stor-

to figure out that a new

command line option.

 

 

age

LUN has been added on

 

 

 

 

 

 

 

 

the back-end storage and

 

 

 

 

makes an upcall to the

 

 

 

 

SCSI midlayer to trigger a

 

 

 

 

LUN scan for that particu-

 

 

 

 

lar target.

 

 

 

 

 

 

 

10

Tearing Down

The session object can

The session object lifecycle is

 

 

Session/Con-

be destroyed using

completely determined by

 

 

nection

QLogic applicationsa

Open-iSCSI. If the node

 

 

objects

 

record exists, sessions will be

 

 

 

 

created by iscsid and will

 

 

 

 

remain there unless logout is

 

 

 

 

explicitly issued using iscsi-

 

 

 

 

adm.

 

11

Multisession

The QLogic applicationa

Open-iSCSI also has multiple

Multisession using

 

handling

allows you to create mul-

session support—iscsiadm

qla4xxx will be

 

 

tiple sessions using the

allows creating multiple ses-

available from

 

 

duplicate target option.

sions for a single iface or a sin-

RHEL 6.3 and

 

 

This duplicate target is

gle port. The main difference is

above.

 

 

persistent in the Flash

that target records are persis-

 

 

 

 

tent in user space as part of

 

 

 

 

node records.

 

 

 

 

 

 

IS0054604-00 A

1-5

1–Legacy vs. Open-iSCSI Summary of Major Differences

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

12

Flash DDBs

Not applicable

The Open-iSCSI driver will

Note: iscsiadm

 

with

 

support existing Flash DDB

is not capable of

 

Open-iSCSI

 

entries in the adapter.

managing the

 

model driver

 

iscsiadm has no control

Flash target

 

 

 

over these sessions. Session

entries.

 

 

 

management of Flash DDB

Before migrating to

 

 

 

entries is done by the driver

 

 

 

the Open-iSCSI

 

 

 

itself.

 

 

 

model, save this

 

 

 

 

 

 

 

 

DDB/target infor-

 

 

 

 

mation to node

 

 

 

 

records using

 

 

 

 

iscsiadm and

 

 

 

 

use the QLogic

 

 

 

 

applicationa to

 

 

 

 

delete Flash

 

 

 

 

entries apart from

 

 

 

 

boot targets before

 

 

 

 

the upgrade. Then,

 

 

 

 

upgrade to the

 

 

 

 

Open-iSCSI

 

 

 

 

model. Boot tar-

 

 

 

 

gets are always in

 

 

 

 

the Flash in both

 

 

 

 

models.

 

 

 

 

 

1-6

IS0054604-00 A

1–Legacy vs. Open-iSCSI Functional Flows

Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)

Serial

Feature

IOCTL-based Driver

Open-iSCSI-based Driver

Remarks

No.

 

 

 

 

 

 

 

 

 

13

CHAP

CHAP settings are

With CHAP support in

Note: Before you

 

 

applied using the QLogic

iscsiadm, CHAP entries can

migrate, delete all

 

 

applicationa.

now be added, deleted, and

CHAP information

 

 

 

listed from the user space.

from Flash using

 

 

 

 

the QLogic applica-

 

 

 

 

tiona, and then

 

 

 

 

update the same

 

 

 

 

CHAP information

 

 

 

 

in the respective

 

 

 

 

node records using

 

 

 

 

iscsiadm com-

 

 

 

 

mands.

 

 

 

 

When migration

 

 

 

 

begins, any CHAP

 

 

 

 

information in the

 

 

 

 

Flash will be hon-

 

 

 

 

ored, but it must be

 

 

 

 

updated in the

 

 

 

 

node records using

 

 

 

 

iscsiadm.

 

 

 

 

Open-iSCSI CHAP

 

 

 

 

management is not

 

 

 

 

supported in RHEL

 

 

 

 

6.2 and SLES 11

 

 

 

 

SP2.

 

 

 

 

CTRL+Q options

 

 

 

 

let you set unidi-

 

 

 

 

rectional and bidi-

 

 

 

 

rectional CHAP

 

 

 

 

only for boot tar-

 

 

 

 

gets. In both mod-

 

 

 

 

els, CHAP

 

 

 

 

information for boot

 

 

 

 

targets is always

 

 

 

 

stored in Flash.

 

 

 

 

 

a The QLogic management applications are iscli (SANsurfer® iSCSI CLI) and qaucli (QConvergeConsole® CLI).

Functional Flows

This section provides functional flow diagrams for discovery, target login, and session recovery.

IS0054604-00 A

1-7

1–Legacy vs. Open-iSCSI Functional Flows

Discovery

Figures 1-1 through 1-3 provide functional flow diagrams of the discovery process for IOCTL and Open-iSCSI.

Figure 1-1. Noninteractive Discovery in IOCTL Mode (Legacy)

Figure 1-2. Interactive Discovery in IOCTL Mode (Legacy)

1-8

IS0054604-00 A

1–Legacy vs. Open-iSCSI Functional Flows

Figure 1-3. Open-iSCSI Discovery

IS0054604-00 A

1-9

1–Legacy vs. Open-iSCSI Functional Flows

Target Login

Figures 1-4 through 1-5 provide functional flow diagrams of the target login process for IOCTL and Open-iSCSI.

Figure 1-4. IOCTL iSCSI Target Login

Figure 1-5. Open-iSCSI Target Login

1-10

IS0054604-00 A

1–Legacy vs. Open-iSCSI Functional Flows

Session Recovery

Figures 1-6 through 1-7 provide functional flow diagrams of the session recovery process for IOCTL and Open-iSCSI.

Figure 1-6. IOCTL Session Recovery

IS0054604-00 A

1-11

1–Legacy vs. Open-iSCSI Functional Flows

Figure 1-7. Open-iSCSI Session Recovery

1-12

IS0054604-00 A

1–Legacy vs. Open-iSCSI State Transition Diagrams

State Transition Diagrams

Figures 1-8 through 1-9 provide state transition diagrams for IOCTL and Open-iSCSI. These diagrams illustrate the management of the session/target life cycle.

Figure 1-8. IOCTL State Transition Diagram

IS0054604-00 A

1-13

1–Legacy vs. Open-iSCSI State Transition Diagrams

Figure 1-9. Open-iSCSI State Transition Diagram

1-14

IS0054604-00 A

+ 56 hidden pages