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.
Starting with Red Hat® Enterprise Linux® (RHEL™) 6.2 and Novell® SUSE® Linux
Enterprise Server (SLES
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.
) 11 SP2, the QLogic qla4xxx driver (iSCSI driver for
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 Avii
Preface
Related Materials
Related Materials
For additional information, refer to the following:
This guide uses the following documentation conventions:
NOTE provides additional information.
Tex t i n 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 i n 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.
Tex t i n 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:
.
. For
Press CTRL+P.
Press the UP ARROW key.
viiiIS0054604-00 A
Tex t i n 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.
Preface
Technical Support
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 Aix
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 Web Site
Technical Support Web Site
Technical Support E-mail
Technical Training E-mail
Knowledge Database
The QLogic knowledge database is an extensive collection of QLogic product
information that you can search for specific solutions. We are constantly adding to
the collection of information in our database to provide answers to your most
urgent questions. Access the database from the QLogic Support Center:
http://support.qlogic.com.
QLogic Corporation
4601 Dean Lakes Blvd.
Shakopee, MN 55379 USA
www.qlogic.com
http://support.qlogic.com
support@qlogic.com
training@qlogic.com
xIS0054604-00 A
1Legacy 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 A1-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
Firmware is configured in
AUTO CONNECT
MODE. In this mode:
The firmware reads
the DDB entries from
the predefined area in
the Flash.
For a Send Target the
firmware initiates dis-
covery, discovers the
target, and initiates
login to the discov-
ered target.
The firmware posts an
AEN to the driver,
identifying each dis-
covered target.
For the DDBs that rep-
resent a Normal tar-
get, the firmware logs
into them and posts an
AEN to the driver to
report the login status.
Firmware is configured in NON
AUTO CONNECT MODE. In
this mode:
The driver reads the DDB
entries from the predefined
area in the Flash.
For a Send Target the
driver initiates a discovery
session through the mail-box command, queries the
firmware for discovered targets, and then initiates
login to the targets using
the mailbox command.
The firmware posts an AEN
to the driver to report login
status after login completes.
For DDBs which represent
a Normal Target, driver initiates login using mailbox
command. Then, the firmware posts an AEN to the
driver to report the login
status after login completes.
2Target
Persistence
1-2IS0054604-00 A
Persistence is maintained by storing Discovery Target and Normal
Target records on the
adapter Flash using the
QLogic application
a
.
Persistence is maintained by
storing Discovery Target and
Normal Target records in the
local file system using the
iscsiadm tool.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
firmware performs auto
discovery and login to the
boot targets based on the
target information saved
in the Flash, and posts an
AEN to inform the driver
of the targets and their
login status.
Session management or
Handling
re-login is handled by the
driver.
Login to boot targets is triggered by the driver, or the user
space is dependent on the
ql4xdisablesysfsboot
driver command line parameter:
For RHEL 6.2 it is enabled
by default, so that the driver
initiates the login.
For SLES 11 SP2 it is dis-
abled by default, so that
yast2-iscsi-client
must be used to perform
login.
Re-login is handled either by
iscsiadm and iscsid, or by
the driver, depending how the
session is initiated:
If iscsiadm created the
session, session management 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 session and is responsible for
re-login or session management.
Note: For more
details on adapter
mode and the
ql4xdisables-y
sfsboot driver,
refer to “Configur-
ing Boot from SAN
on RHEL 6.2” on
page 2-19.
Session re-login is
also initiated on
chip or adapter
reset.
5Network con-
figuration
IS0054604-00 A1-3
Adapter ports are configured using the QLogic
application
a
.
Adapter ports are configured
using iscsiadm for network
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.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Login and target scanning
is done in kernel space as
follows:
1. When the driver
receives an AEN for
the DDB indicating
that the target is
logged in, the driver
publishes the session
to the iSCSI transport
layer and unblocks the
session.
2. This triggers the SCSI
midlayer LUN scanning to discover all
LUNs behind the target.
a
Use the following command:
iscsiadm -m session
Login and target scanning is
done by user space as follows:
1. When the driver receives
an AEN for the DDB indicating that the target is
logged in, it sends an event
to the iscsid (user
space) indicating that the
session is in the logged-in
state.
2. iscsid then unblocks the
session and kicks off the
target/LUN scanning.
8Link Down
impact on
SCSI Device
Handling
No change in the behavior of session and SCSI
device state handling.
The default session
recovery time-out is equal
to the firmware keep alive
timeout. The default value
is 30 seconds. This can
be modified by the driver
command line parameter
ql4xkeepalive.
No change in the behavior of
session and SCSI device state
handling.
For Open-iSCSI, default
recovery time-out is 120 seconds. This can be configured
on an individual session basis
dynamically; that is, it does not
require driver unload.
Session recovery time-out can
be configured by modifying the
replacement_timeout
parameter in the node record.
1-4IS0054604-00 A
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
mapping/unmapping of LUNs
added to the
back-end storage
Session/Connection
objects
The driver handles the
following check condition/sense data:
UNIT_ATTENTION
ASC/ASCQ : 0x3F/0x0E
to figure out that a new
LUN has been added on
the back-end storage and
makes an upcall to the
SCSI midlayer to trigger a
LUN scan for that particular target.
The session object can
be destroyed using
QLogic applications
a
No explicit support to dynamically discover newly added
LUNs on the back-end storage. Requires manual rescanning using iscsiadm
command line option.
The session object lifecycle is
completely determined by
Open-iSCSI. If the node
record exists, sessions will be
created by iscsid and will
remain there unless logout is
explicitly issued using iscsi-adm.
11Multisession
handling
The QLogic applicationa
allows you to create multiple sessions using the
duplicate target option.
This duplicate target is
persistent in the Flash
Open-iSCSI also has multiple
session support—iscsiadm
allows creating multiple sessions for a single iface or a single port. The main difference is
that target records are persistent in user space as part of
node records.
Multisession using
qla4xxx will be
available from
RHEL 6.3 and
above.
IS0054604-00 A1-5
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
support existing Flash DDB
entries in the adapter.
iscsiadm has no control
over these sessions. Session
management of Flash DDB
entries is done by the driver
itself.
Note:iscsiadm
is not capable of
managing the
Flash target
entries.
Before migrating to
the Open-iSCSI
model, save this
DDB/target information to node
records using
iscsiadm and
use the QLogic
application
delete Flash
entries apart from
boot targets before
the upgrade. Then,
upgrade to the
Open-iSCSI
model. Boot targets are always in
the Flash in both
models.
a
to
1-6IS0054604-00 A
1–Legacy vs. Open-iSCSI
Functional Flows
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
13CHAPCHAP settings are
a
The QLogic management applications are iscli (SANsurfer® iSCSI CLI) and qaucli (QConvergeConsole® CLI).
With CHAP support in
iscsiadm, CHAP entries can
now be added, deleted, and
listed from the user space.
Note: Before you
migrate, delete all
CHAP information
from Flash using
the QLogic applica-
a
tion
, and then
update the same
CHAP information
in the respective
node records using
iscsiadm commands.
When migration
begins, any CHAP
information in the
Flash will be honored, 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 unidirectional and bidirectional CHAP
only for boot targets. In both models, CHAP
information for boot
targets is always
stored in Flash.
Functional Flows
This section provides functional flow diagrams for discovery, target login, and
session recovery.
IS0054604-00 A1-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-8IS0054604-00 A
1–Legacy vs. Open-iSCSI
Functional Flows
Figure 1-3. Open-iSCSI Discovery
IS0054604-00 A1-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-10IS0054604-00 A
Session Recovery
Figures 1-6 through 1-7 provide functional flow diagrams of the session recovery
process for IOCTL and Open-iSCSI.
1–Legacy vs. Open-iSCSI
Functional Flows
Figure 1-6. IOCTL Session Recovery
IS0054604-00 A1-11
1–Legacy vs. Open-iSCSI
Functional Flows
Figure 1-7. Open-iSCSI Session Recovery
1-12IS0054604-00 A
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.
1–Legacy vs. Open-iSCSI
State Transition Diagrams
Figure 1-8. IOCTL State Transition Diagram
IS0054604-00 A1-13
1–Legacy vs. Open-iSCSI
State Transition Diagrams
Figure 1-9. Open-iSCSI State Transition Diagram
1-14IS0054604-00 A
Loading...
+ 56 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.