Q Logic Network Card 8200 SERIES CONVERGED NETWORK ADAPTERS User Guide |
User’s Guide
IOCTL to Open-iSCSI Interface
QLogic 4000 Series iSCSI Adapters and 8200 Series
Converged Network Adapters
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
Table of Contents
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii
vii
viii
viii
ix
ix
x
x
x
Functional Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Session Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
State Transition Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
1-2
1-7
1-8
2-2
2-2
2-4
2-4
Installing RHEL 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
3-2
3-2
IS0054604-00 A
iii
Download from Www.Somanuals.com. All Manuals Search And Download.
User’s Guide—IOCTL to Open-iSCSI Interface
QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters
3-2
3-2
3-3
3-3
3-4
3-4
3-4
3-6
3-6
3-7
3-8
3-8
3-9
Target Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Features Not Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Migrating to Open-iSCSI Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Linux Open-iSCSI README . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
List of Figures
Figure
Page
Interactive Discovery in IOCTL Mode (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
1-8
1-9
IOCTL iSCSI Target Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
iv
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
User’s Guide—IOCTL to Open-iSCSI Interface
QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters
Open-iSCSI Target Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
IOCTL Session Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Open-iSCSI Session Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
IOCTL State Transition Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Open-iSCSI State Transition Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Entering Fast!UTIL from the Adapter’s BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4
2-5
2-5
2-6
2-6
2-7
2-7
2-8
2-8
2-9
2-9
2-10 Selecting Alternate Boot Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-11 Providing Target IP Address for Alternate Boot Device . . . . . . . . . . . . . . . . . . . . . .
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 withiscsiBoot 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
Download from Www.Somanuals.com. All Manuals Search And Download.
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
Configurations and Tools for Checking iSCSI Sessions. . . . . . . . . . . . . . . . . . . . . . 2-33
1-2
2-3
3-4
3-6
vi
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
®
®
®
®
Starting with Red Hat Enterprise Linux (RHEL™) 6.2 and Novell SUSE Linux
Enterprise Server (SLES®) 11 SP2, the QLogic qla4xxxdriver (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 qla4xxxdriver, 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
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Related Materials
Related Materials
For additional information, refer to the following:
Technical Note, 2.10. Kernel
Release Notes for SUSE Linux Enterprise Server 11 Service Pack 2
Linux Open-iSCSI 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.
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 Courierfont 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
Download from Www.Somanuals.com. All Manuals Search And Download.
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
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
Downloading Firmware and Documentation
To download firmware and documentation:
1.
2.
Go to the QLogic Downloads and Documentation page:
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.
4.
In the search results list, locate and select the firmware and documentation,
for your product.
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.
6.
7.
Click Download Now.
Save the file to your computer.
If you have downloaded firmware, follow the installation instructions in the
Readme file.
IS0054604-00 A
ix
Download from Www.Somanuals.com. All Manuals Search And Download.
Preface
Technical Support
Training
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
Support Headquarters
QLogic Corporation
4601 Dean Lakes Blvd.
Shakopee, MN 55379 USA
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:
x
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
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:
IS0054604-00 A
1-1
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Summary of Major Differences
and Open-iSCSI models.
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
1
Firmware
Operational
Mode
Firmware is configured in Firmware is configured in NON
AUTO CONNECT
AUTO CONNECT MODE. In
this mode:
MODE. In this mode:
The firmware reads
the DDB entries from
the predefined area in
the Flash.
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 tar-
gets, and then initiates
For a Send Target the
firmware initiates dis-
covery, discovers the
target, and initiates
login to the discov-
ered target.
login to the targets using
the mailbox command.
The firmware posts an
AEN to the driver,
The firmware posts an AEN
to the driver to report login
status after login completes.
identifying each dis-
covered target.
For the DDBs that rep- For DDBs which represent
resent a Normal tar-
get, the firmware logs
into them and posts an
AEN to the driver to
report the login status.
a Normal Target, driver initi-
ates login using mailbox
command. Then, the firm-
ware posts an AEN to the
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
Target records on the
Normal Target records in the
local file system using the
adapter Flash using the iscsiadm tool.
QLogic applicationa.
1-2
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
3
Boot Target
During driver load, the
firmware performs auto
Login to boot targets is trig-
gered by the driver, or the user details on adapter
Note: For more
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- sfsbootdriver,
in the Flash, and posts an ter:
AEN to inform the driver
refer to “Configur-
ing Boot from SAN
on RHEL 6.2” on
For RHEL 6.2 it is enabled
of the targets and their
login status.
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.
4
Re-login
Handling
Session management or Re-login is handled either by
re-login is handled by the iscsiadmand iscsid, or by also initiated on
driver. the driver, depending how the chip or adapter
Session re-login is
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
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
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
Qlogic applicationa
6
How to view
sessions
logged in
Use the following command:
iscsiadm -m session
7
Target scan-
ning
Login and target scanning Login and target scanning is
is done in kernel space as done by user space as follows:
follows:
1. When the driver receives
1. When the driver
receives an AEN for
the DDB indicating
that the target is
an AEN for the DDB indi-
cating 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.
logged in, the driver
publishes the session
to the iSCSI transport
layer and unblocks the
session.
2. iscsid then unblocks the
session and kicks off the
target/LUN scanning.
2. This triggers the SCSI
midlayer LUN scan-
ning to discover all
LUNs behind the tar-
get.
8
Link Down
impact on
SCSI Device
Handling
No change in the behav- No change in the behavior of
ior of session and SCSI
device state handling.
session and SCSI device state
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
be configured by modifying the
replacement_timeout
ql4xkeepalive.
parameter in the node record.
1-4
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
9
Dynamic
map-
The driver handles the
following check condi-
tion/sense data:
No explicit support to dynami-
cally discover newly added
LUNs on the back-end stor-
age. Requires manual rescan-
ning using iscsiadm
ping/unmap-
ping of LUNs
added to the
back-end stor-
age
UNIT_ATTENTION
ASC/ASCQ : 0x3F/0x0E
command line option.
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 particu-
lar target.
10
Tearing Down The session object can
Session/Con- be destroyed using
nection
The session object lifecycle is
completely determined by
Open-iSCSI. If the node
record exists, sessions will be
created by iscsidand will
remain there unless logout is
explicitly issued using iscsi-
adm.
QLogic applicationsa
objects
The QLogic applicationa
Multisession
11
Open-iSCSI also has multiple Multisession using
handling
session support—iscsiadm
allows creating multiple ses-
sions for a single iface or a sin-
gle port. The main difference is
that target records are persis-
tent in user space as part of
node records.
allows you to create mul-
tiple sessions using the
duplicate target option.
This duplicate target is
persistent in the Flash
qla4xxxwill be
available from
RHEL 6.3 and
above.
IS0054604-00 A
1-5
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Summary of Major Differences
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
12
Flash DDBs
with
Open-iSCSI
model driver
Not applicable
The Open-iSCSI driver will
support existing Flash DDB
entries in the adapter.
Note: iscsiadm
is not capable of
managing the
Flash target
iscsiadm has no control
over these sessions. Session entries.
management of Flash DDB
Before migrating to
entries is done by the driver
itself.
the Open-iSCSI
model, save this
DDB/target infor-
mation to node
records using
iscsiadm and
use the QLogic
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
Download from Www.Somanuals.com. All Manuals Search And Download.
1–Legacy vs. Open-iSCSI
Functional Flows
Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued)
Serial
No.
Feature
IOCTL-based Driver Open-iSCSI-based Driver
Remarks
13
CHAP
CHAP settings are
With CHAP support in
Note: Before you
applied using the QLogic iscsiadm, CHAP entries can migrate, delete all
now be added, deleted, and
listed from the user space.
CHAP information
from Flash using
the QLogic applica-
update the same
CHAP information
in the respective
noderecordsusing
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
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
New Parameter: ql4disablesysfsboot
New Parameter: ql4disablesysfsboot
The ql4disablesysfsboot parameter is a new driver module parameter for
the Open-iSCSI based driver model (it is not supported by the ioctl based
driver). This parameter controls the behavior of boot target login in the
Open-iSCSI base driver, which provides two ways to log in to the boot targets.
Option 1: If ql4disablesysfsboot is 0, the Boot targets are exported
through sysfs and iscsistart will issue a login to the boot target (that is,
the login to the boot target will be triggered from the user space).
Option 2: If ql4disablesysfsboot is 1, the qla4xxx driver will handle
the login to the boot targets.
Some environments require support for driver login (Option 2) to the boot targets
for these reasons:
If the boot entry is a sendtarget entry, then iscsistart or
open-iscsicannot discover and log in to the discovered target.
The system will not boot up if you only do the kernel upgrade and do not
upgrade the iSCSI tools.
Boot from SAN Configuration Matrix
ql4xdisablesysfsboot module parameter and its corresponding effect on the
behavior of sysfs, iscsistart, and the qla4xxx driver when using the
sendtarget entry (ST) and the iSCSI target entry (NT).
NOTE
All boot from SAN cases assume that iSCSI BIOS is enabled.
2-2
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Boot from SAN Configuration Matrix
Table 2-1. Boot from SAN Configuration Matrix
ql4xdisablesysfsboot = 0
ql4xdisablesysfsboot = 1
Boot Target as
Normal target
(NT)
Boot Target as
Boot Target as
Normal target
Boot Target as
sendtarget (ST)
sendtarget (ST)
(NT)
Export boot target The Boot Target will The Boot Target will The Boot Target
The Boot Target
through sysfs
be exported through be exported through will not be
will not be
sysfs (with IP
address and port
only)
sysfs.
exported through exported through
sysfs. sysfs.
(/sys/firmware/
iscsi_bootx/
where x is 1, 2,...)
Note: If the iSCSI
BIOS login is dis-
abled, the entry
made at the boot
index will not be
exported to sysfs.
Note: If the iSCSI
BIOS login is dis-
abled, the entry
made at the boot
index will not be
exported to sysfs.
iscsistart
iscsistartdoes iscsistartlogs iscsistartwill iscsistartwill
not do discovery
and login to the dis-
covered targets.
in to the NT.
not log in to ST
targets.
not log in to NT
targets.
Note: If the iSCSI
BIOS login is dis-
abled, the driver will
handle logging in to
the boot target.
Driver
The driver scans the The driver does not The driver scans
Flash entries, cre-
ates the list of send- gets. The open-iscsi creates the list of normal target
The driver does-
log in to normal tar- the Flash entries, the login to the
(qla4xxx)
targets, and
discovers and logs
in to the targets.
tools (iscsistart) log sendtargets, and
which is config-
ured as boot tar-
gets.
in to boot targets.
discovers and
logs in to the tar-
gets.
IS0054604-00 A
2-3
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN
Configuring Boot from SAN
Boot from SAN Installation on SLES 11 SP2 and RHEL 6.2
To configure the adapter for BFS on SLES 11 SP2 or RHEL 6.2, follow these
steps:
1.
While the system is booting up, press CTRL+Q to enter Fast!UTIL on the
Figure 2-1. Entering Fast!UTIL from the Adapter’s BIOS
2-4
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN
Figure 2-16. Setting the Boot Mode to Manual
17. Save the settings for the port.
targets on the port.
19. Save the settings and reboot the system with the installation disk.
2-12
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN
Boot from SAN Installation on SLES 11 SP2
To configure the adapter for BFS on SLES 11 SP2, follow these steps:
1.
Figure 2-17. Entering the Boot BIOS
2.
Figure 2-18. Providing the withiscsi Boot Option
IS0054604-00 A
2-13
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN
3.
instructions on this screen to begin the installation.
Figure 2-19. Installation Welcome Screen
4.
Complete the installation by following the instructions on all subsequent
Figure 2-20. Media Check
2-14
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN on RHEL 6.2
Configuring Boot from SAN on RHEL 6.2
Installing RHEL 6.2
To install RHEL 6.2, follow these steps:
1.
Figure 2-28. Booting From the Installation Media
2.
Figure 2-29. Choosing to Test Media Disk or Skip Test
IS0054604-00 A
2-19
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
Configuring Boot from SAN on RHEL 6.2
3.
Select the network interface through which the installation is to be done, as
Figure 2-30 shows.
Figure 2-30. Selecting Network Interface for Installation
4.
Figure 2-31. Configuring the IP Address
2-20
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
ql4xdisablesysfsboot Settings and Adapter Boot Mode
ql4xdisablesysfsboot Settings and Adapter Boot
Mode
This section demonstrates the effect of the ql4xdisablesysfsbootparameter
under different adapter boot modes.
NOTE
For target discovery and login to work, the adapter’s IP address must be
configured using either BIOS settings or iscsiadm. The following examples
show the iscsiadmcommands to use to set the IP address.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:07:59:f2.ipv4.0 -n
iface.ipaddress -v 10.0.10.183 -o update
# iscsiadm -m iface -I qla4xxx.00:c0:dd:07:59:f2.ipv4.0 -n
iface.subnet_mask -v 255.255.0.0 -o update
# iscsiadm -m iface -I qla4xxx.00:c0:dd:07:59:f2.ipv4.0 -n
iface.gateway -v 10.0.0.1 -o update
# iscsiadm -m iface -I qla4xxx.00:c0:dd:07:59:f2.ipv4.0 -o apply
Use the following sysfs path to check if the IP address has been applied:
/sys/class/iscsi_host/host<Number>/ipaddress
iscisadmcommands or yast tool to use to check iSCSI sessions.
Table 2-2. Configurations and Tools for Checking iSCSI Sessions
Adapter
Configu- Target ql4xdisable
No.
Boot iscsiadm command
Remarks
ration
info
sysfsboot
Mode
1
Non-Boot Target info 1 or 0
from SAN is in the
firmware
Disable
To check sessions
Since the target info is
in the firmware, keep
ql4xdisablesysfs-
boot set to 1. The
driver does the login to
the target.
# iscsiadm -m session
(set up
using the
BIOS)
IS0054604-00 A
2-33
Download from Www.Somanuals.com. All Manuals Search And Download.
2–Boot from SAN
ql4xdisablesysfsboot Settings and Adapter Boot Mode
Table 2-2. Configurations and Tools for Checking iSCSI Sessions (Continued)
Adapter
Configu- Target ql4xdisable
No.
Boot iscsiadm command
Remarks
ration
info
sysfsboot
Mode
2
Non-Boot No target
1 or 0
Disable
Use iscsiadm for discov- Since there are no
ery and login to targets. The entries in Flash or firm-
from SANa
info is in
the firm-
ware
ware, target manage-
ment is done by
correct qla4xxxiface
must be used.
iscsiadmand isc-
sid. The driver is just
pass-through.
Discovery:
# iscsiadm -m
discovery -t st -p
<target IP> -I
<qla4xxx iface>
Login:
#iscsiadm -m node -l
To check the sessions:
# iscsiadm -m session
3
4
Boot from Boot tar-
1
0
Manual
Manual
To check sessions:
Since ql4xdisable-
sysfsboot= 1, the
qla4xxxdriver does
the login to the target.b
SAN
get info is
in the firm-
ware/
#iscsiadm -m session
Flash
Boot from Boot tar-
To check boot target info:
#iscsiadm -m fw
Since ql4xdisable-
sysfsboot= 0, the
driver will not log in to
boot targets. The iscsi
initiator tools (such as
iscsistart in
SAN
get info is
in the firm-
ware/
To check sessions:
# iscsiadm -m session
Flash
If login is not done automati-
cally use:
# iscsiadm -m fw -l
RHEL) do the login to
the boot targets.
a
b
In this configuration you can use the iscsi-client from yast to add targets and login to the targets.
This configuration is basically compatible with older qla4xxx infrastructure in SLES 11 SP1.
NOTE
In all these configurations you can use the iscsiadmcommand to do
additional discovery and login. The only exception is boot targets for Boot
from SAN. For Boot from SAN, target information must be in the firmware or
Flash, having been added using the CTRL+Q option of BIOS.
2-34
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Open-iSCSI Supported Features
Open-iSCSI Supported Features
Open-iSCSI support has been added to the QLogic iSCSI driver in Red Hat
Enterprise Linux 6.2 and SUSE Linux Enterprise Server 11 Service Pack 2.
Open-iSCSI infrastructure supports discovery, login to and logout from iSCSI
targets, and modification and display of iSCSI configuration parameters. The
QLogic iSCSI driver provides persistence through Flash and Open-iSCSI nodes
and sendtargets databases.
Discovery, Login, and Logout
Prior to RHEL 6.2 and SLES 11 SP2, discovery and login to iSCSI targets was
hardware offloaded and managed by the QLogic iSCSI adapter firmware. In
RHEL 6.2 and SLES 11 SP2, the Open-iSCSI infrastructure allows the system
administrator to manage QLogic iSCSI target discovery and login through the
QLogic adapter. This provides the system administrator with a uniform and
standard way to manage different vendor interfaces.
Boot Target Login
Default Behavior on RHEL 6.2
Open-iSCSI is enabled by default on RHEL 6.2 and login to boot targets is
triggered by iscsistartthrough sysfs. The default behavior can be changed by
setting ql4xdisablesysfsbootto 1, this disables exporting boot targets in
Flash to sysfs and login to boot targets is done by the driver.
1.
With ql4xdisablesysfsboot=0, list boot targets if present.
# iscsiadm -m fw
2.
Disable sysfs boot.
# echo "options qla4xxx ql4xdisablesysfsboot=1" >>
/etc/modprobe.d/qla4xxx.conf
3.
4.
Reload the qla4xxxdriver.
# rmmod qla4xxx
# modprobe qla4xxx
Update ramdisk.
Reboot the system, if the system is booted using the iSCSI boot target.
3-2
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Open-iSCSI Supported Features
NOTE
Refer to the following Red Hat Technical Note about issues and
workarounds when upgrading from RHEL 6.1 to RHEL 6.2:
Default Behavior on SLES 11 SP2
Open-iSCSI is enabled by default on SLES 11 SP2 and login to boot targets is
triggered by iscsiadmduring installation.
NOTE
The additional command line kernel parameter withiscsi=1must be
passed before beginning the OS installation. If not, the iSCSI disks will
not be detected.
The modules qla3xxxand qlcnicshould be loaded respectively for
the 1G and 10G QLogic iSCSI initiator entries to appear in the
iscsi-client through YaST.
The default behavior can be changed by setting the driver parameter
ql4xdisablesysfsboot to 1, in which case the boot targets in Flash are not
exported to sysfs, and the driver logs in to the boot targets. The kernel parameter
withiscsi=1is not used when ql4xdisablesysfsboot is set to 1.
NOTE
Refer to the following Release Notes for SLES 11 SP2 for the kernel
parameter withiscsi=1:
Persistence through Flash and Open-iSCSI Database
Prior to RHEL 6.2 and SLES 11 SP2, targets were made persistent by saving the
entries in Flash. In RHEL 6.2 and SLES 11 SP2, targets managed by Open-iSCSI
are made persistent by saving them in the user space node and sendtarget
persistent database.
For targets in Flash, auto-login is triggered by the QLogic iSCSI driver and
firmware. For targets saved in the Open-iSCSI persistent database, the iSCSI
daemon iscsid can be configured to automatically start discovery and login
through the sendtarget and node persistent databases.
IS0054604-00 A
3-3
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Managing QLogic iSCSI Adapters Using
iscsiadm
iSCSI Configuration Files and Persistent Databases
The Open-iSCSI daemon iscsid can be configured to use the default node
configuration and persistent database to automatically start discovery on startup.
and RHEL6.2.
Table 3-1. Configuration and Persistent Database Files
File Path and Name
Description
Configuration File—SLES 11 SP2 and RHEL 6.2
/etc/iscsi/iscsid.conf
Read by iscsid and iscsiadm on
startup; applied to all newly created nodes
Persistent Database Files—SLES 11 SP2
/etc/iscsi/nodes/<node_iqn_name>/
<ip_address:port_number>
Contains node-specific configuration
Persistent node database
/etc/iscsi/nodes
/etc/iscsi/sendtargets
Persistent Database Files—RHEL 6.2
Persistent Sendtargets discovery database
/var/lib/iscsi/nodes/<node_iqn_name>/ Contains node-specific configuration
<ip_address:port_number>
/var/lib/iscsi/nodes
Persistent node database
Persistent Sendtargets discovery database
/var/lib/iscsi/sendtargets
Configuring Targets for qla4xxx Using Open-iSCSI
To configure targets for qla4xxxusing Open-iSCSI, follow these steps:
1.
Configure the qla4xxxport.
# iscsiadm -m iface -I qla4xxx. 00:0e:1e:05:38:42.ipv4.0 -o update -n
iface.ipaddress -v 192.168.1.115
# iscsiadm -m iface -I qla4xxx. 00:0e:1e:05:38:42.ipv4.0 -o apply
3-4
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
2.
Discover the iSCSI target.
# iscsiadm -m discovery -t st -p 192.168.1.11 -I qla4xxx.00:0e:1e:05:38:42.ipv4.0
192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2
192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3
192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2
192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3
3.
List all discovered targets.
# iscsiadm -m node
192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3
192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2
192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2
192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3
4.
Log in to all discovered targets.
# iscsiadm -m node -l
Logging in to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.a3, portal: 192.168.1.8,3260] (multiple)
Logging in to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.a2, portal: 192.168.1.11,3260] (multiple)
Logging in to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.b2, portal: 192.168.1.12,3260] (multiple)
Logging in to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.b3, portal: 192.168.1.9,3260] (multiple)
Login to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.a3, portal: 192.168.1.8,3260] successful.
Login to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.a2, portal: 192.168.1.11,3260] successful.
Login to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.b2, portal: 192.168.1.12,3260] successful.
Login to [iface: qla4xxx.00:0e:1e:05:38:42.ipv4.0, target:
iqn.1992-04.com.emc:cx.ckm00101200392.b3, portal: 192.168.1.9,3260] successful.
5.
List all sessions.
#iscsiadm -m session
qla4xxx: [2] 192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2
qla4xxx: [3] 192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3
qla4xxx: [4] 192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2
qla4xxx: [5] 192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3
IS0054604-00 A
3-5
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
iSCSI Interface Configuration
iSCSI Configuration Parameters
Each iSCSI Host Bus Adapter, NIC, or network interface to which sessions are
bound should have its own iSCSI interface config file in /etc/iscsi/ifaces.
For hardware offload iSCSI, iscsiadmcreates ifaces for QLogic iSCSI ports.
Before the iface can be used, the IP address for the port must be set as shown in
interface config file fields.
Table 3-2. Hardware iSCSI Interface Config File Fields
Needed
Field Name
Description
Yes
iface.transport_name
iface.initiatorname
The iscsi_transport or driver to use for iface
No
Set if the /etc/iscsi/initiatorame.iscsi
initiatorname is not to be used for normal ses-
sions. For discovery sessions, /etc/iscsi/
initiatorname.iscsiis used.
Yes
Yes
iface.hwaddress
iface.ipaddress
Sets MAC address to bind by hardware address
The IP address configured for the iface, on the
same subnet as the target
No
iface.bootproto
Set to dhcp if IPv4 address must be obtained
dynamically through DHCP, or set to static if IPv4
address is set to a static IP address.
No
No
iface.vlan_priority
Used to set VLAN priority for the iSCSI interface
iface.vlan_state
(disable/enable)
Used to enable or disable the VLAN on the iSCSI
interface
No
No
No
iface.ipv6_linklocal
Used to specify the IPV6 Link Local Address with
the link local prefix of FE80::0/64
iface.ipv6_autocfg
(nd-neighbor discovery) address
Used to set the discovery protocol to obtain IPV6
iface.linklocal_autocfg
For transport like qla4xxx, this allows you to
autoconfigure the # IPV6 link local address based
on the MAC address of the iSCSI interface.
No
No
Required to set the IPv6 router discovery protocol
iface.router_autocfg
iface.state
Set to enable by default.To disable the iface, set it
to disable.
Yes
iface.iface_num
Used when more than one interface is configured
for a transport
3-6
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Example: IPv4 sample config file with static IP address
# BEGIN RECORD 2.0-872
iface.iscsi_ifacename = qla4xxx-3
iface.ipaddress = 192.168.1.75
iface.hwaddress = 00:0e:1e:04:93:92
iface.transport_name = qla4xxx
iface.bootproto = static
iface.subnet_mask = 255.255.255.0
iface.gateway = 192.168.1.1
iface.state = enable
iface.vlan = <empty>
iface.iface_num = 0
END RECORD
List All ifaces
# iscsiadm -m iface
Example:
# iscsiadm -m iface
default tcp,<empty>,<empty>,<empty>,<empty>
iser iser,<empty>,<empty>,<empty>,<empty>
qla4xxx-4032-2 qla4xxx,00:c0:dd:0b:13:f1,192.168.2.214,<empty>,<empty>
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 qla4xxx,00:c0:dd:0b:13:f1,<empty>,
<empty>,<empty>
qla4xxx.00:0e:1e:04:11:e2.ipv4.0 qla4xxx,00:0e:1e:04:11:e2,192.168.7.9,
<empty>,<empty>
bnx2i.00:00:00:00:00:00 bnx2i,00:00:00:00:00:00,<empty>,<empty>,<empty>
IS0054604-00 A
3-7
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Display iface Configuration Details
# iscsiadm -m iface -I <iface_name>
Example:
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0
# BEGIN RECORD 2.0-872.28.el6-1031
iface.iscsi_ifacename = qla4xxx.00:c0:dd:0b:13:f1.ipv4.0
iface.net_ifacename = <empty>
iface.ipaddress = 192.168.2.214
iface.hwaddress = 00:c0:dd:0b:13:f1
iface.transport_name = qla4xxx
iface.initiatorname = <empty>
iface.bootproto = <empty>
iface.subnet_mask = <empty>
iface.gateway = <empty>
iface.ipv6_autocfg = <empty>
iface.linklocal_autocfg = <empty>
iface.router_autocfg = <empty>
iface.ipv6_linklocal = <empty>
iface.ipv6_router = <empty>
iface.state = <empty>
iface.vlan_id = 0
iface.vlan_priority = 0
iface.vlan_state = <empty>
iface.iface_num = 0
iface.mtu = 0
iface.port = 0
# END RECORD
Create an iface
# iscsiadm -m iface -I <iface_name> -o new
NOTE
The iface.transport_nameis set to tcp by default, for a software
initiator. The iface.transport_nameshould be updated to qla4xxx for
Hardware Offload iface. The iface parameters ipaddress, hwaddress,
and initiatornamecan be updated using the -o update option as shown
3-8
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Example:
# iscsiadm -m iface -I qla4xxx-4
# BEGIN RECORD 2.0-872
iface.iscsi_ifacename = qla4xxx-4
iface.net_ifacename = <empty>
iface.ipaddress = <empty>
iface.hwaddress = <empty>
iface.transport_name = qla4xxx
iface.initiatorname = <empty>
iface.bootproto = <empty>
iface.subnet_mask = <empty>
iface.gateway = <empty>
iface.ipv6_autocfg = <empty>
iface.linklocal_autocfg = <empty>
iface.router_autocfg = <empty>
iface.ipv6_linklocal = <empty>
iface.ipv6_router = <empty>
iface.state = <empty>
iface.vlan_id = 0
iface.vlan_priority = 0
iface.vlan_state = <empty>
iface.iface_num = 0
# END RECORD
Update iface Network Parameters
# iscsiadm -m iface -I <iface_name> -o update -n <rec_name> -v <value>
# iscsiadm -m iface -I <iface_name> -o apply
# iscsiadm -m iface -I <iface_name> -o applyall
Where:
update updates the record <rec_name>with the specified <value>
apply causes the network settings to take effect on the specified iface
applyall causes the network settings to take effect on every iface
IS0054604-00 A
3-9
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Example: IPv4 Settings (static)
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o update -n
iface.ipaddress -v 192.168.2.214
qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o apply
qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 applied.
Example: IPv4 Settings (DHCP)
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o update -n
iface.bootproto -v dhcp
qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o apply
qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 applied.
Example: IPv6 Settings (manual)
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o update -n
iface.ipaddress -v fec0:ce00:7014:0041:1111:2222:1e04:9392
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o update -n
iface.ipv6.linklocal -v fe80:0000:0000:0000:0000:0000:1e04:9392
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o update -n
iface.ipv6.router -v fe80:0000:0000:0000:7ae7:d1ff:fe72:4048
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o apply
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 applied.
Example: IPv6 Settings (neighbor discovery)
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o update -n
iface.ipv6.autocfg -v nd
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 updated.
# iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 -o apply
qla4xxx.00:c0:dd:0b:13:f1.ipv6.0 applied.
3-10
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
NOTE
The target should be logged out before updating the network parameters.
iscsiadmwill give the following warning if a network parameter of an iface
with active sessions is updated:
iscsiadm: Updating iface while iscsi sessions are using
it. You must logout the running sessions then log back
in for the new settings to take affect.
Unidirectional and Bidirectional CHAP settings
# iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.com.vm-base:disk1 -o
update -n node.session.auth.authmethod -v CHAP
# iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.com.vm-base:disk1 -o
update -n node.session.auth.username -v chapuser
# iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.com.vm-base:disk1 -o
update -n node.session.auth.password -v chapsecret
# iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.com.vm-base:disk1 -o
update -n node.session.auth.username_in -v biuser
# iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.com.vm-base:disk1 -o
update -n node.session.auth.password_in -v bidirsecret
Example: Display changes made to the 192.168.1.84:3260 CHAP settings:
# iscsiadm -m node -p 192.168.1.84:3260
.
.
node.session.auth.authmethod = CHAP
node.session.auth.username = chapuser
node.session.auth.password = ********
node.session.auth.username_in = biuser
node.session.auth.password_in = ********
.
.
IS0054604-00 A
3-11
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Target Discovery
Discover Targets using sendtarget
# iscsiadm -m discovery -t st -p <target_ip:target_port> -I
<iface_name> -o new, delete, update, nonpersistent
In discovery mode, iscsiadmwill use the iscsid.conf discovery settings and
overwrite the discovery record settings with it. By default, it will remove records for
portals not returned. For portals returned, the discovery command will create a
new record or modify an existing one with values from iscsid.confand the
command line.
Values passed with the -ooption:
new—iscsiadmwill add records for portals that do not yet have records in
the database.
delete—iscsiadmdeletes records for portals that were not returned during
discovery.
update—iscsiadmupdates records for portals returned during discovery
using info from iscsid.confand command line.
nonpersistent—iscsiadmwill not store the portals found in node
database.
Example:
# iscsiadm -m discovery -t st -p 192.168.2.104 -I qla4xxx-3 -o new
192.168.2.104:3260,1
iqn.2001-05.com.equallogic:0-8a0906-32e33fe02-517000ecd724ea83-karen-1
192.168.2.104:3260,1
iqn.2001-05.com.equallogic:0-8a0906-eddd93203-dc1000ece454e721-karen-2
192.168.2.104:3260,1
iqn.2001-05.com.equallogic:0-8a0906-ef8d93203-e99000ece484e721-karen-3
192.168.2.104:3260,1
iqn.2001-05.com.equallogic:0-8a0906-f16d93203-92d000ece4b4e721-karen-4
3-12
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Adding a New discoverydb for sendtarget
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -I qla4xxx-3 -o new
New discovery record for [192.168.2.105,3260] added.
# cat /var/lib/iscsi/send_targets/192.168.2.105,3260/st_config
# BEGIN RECORD 2.0-872.28.el6-1031
discovery.startup = manual
discovery.type = sendtargets
discovery.sendtargets.address = 192.168.2.105
discovery.sendtargets.port = 3260
discovery.sendtargets.auth.authmethod = None
discovery.sendtargets.timeo.login_timeout = 15
discovery.sendtargets.use_discoveryd = No
discovery.sendtargets.discoveryd_poll_inval = 30
discovery.sendtargets.reopen_max = 5
discovery.sendtargets.timeo.auth_timeout = 45
discovery.sendtargets.timeo.active_timeout = 30
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
# END RECORD
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -I qla4xxx-3 -o update -n
discovery.sendtargets.auth.authmethod -v CHAP
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -o update -n
discovery.sendtargets.auth.username -v joe
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -o update -n
discovery.sendtargets.auth.password -v secret
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -I qla4xxx-3 --discover
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-32e33fe02-517000ecd724ea83-karen-1
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-eddd93203-dc1000ece454e721-karen-2
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-ef8d93203-e99000ece484e721-karen-3
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-f16d93203-92d000ece4b4e721-karen-4
IS0054604-00 A
3-13
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
# cat /var/lib/iscsi/send_targets/192.168.2.105,3260/st_config
# BEGIN RECORD 2.0-872.28.el6-1031
discovery.startup = manual
discovery.type = sendtargets
discovery.sendtargets.address = 192.168.2.105
discovery.sendtargets.port = 3260
discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = joe
discovery.sendtargets.auth.password = secret
discovery.sendtargets.timeo.login_timeout = 15
discovery.sendtargets.use_discoveryd = No
discovery.sendtargets.discoveryd_poll_inval = 30
discovery.sendtargets.reopen_max = 5
discovery.sendtargets.timeo.auth_timeout = 45
discovery.sendtargets.timeo.active_timeout = 30
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
# END RECORD
Remove sendtarget Node
# iscsiadm -m discoverydb -t st -p <target IP> -I <iface> -o delete
Example:
# iscsiadm -m discoverydb -t st -p 192.168.2.105 -I qla4xxx-3 -o
delete
Adding and Deleting Targets
Adding a New Target
# iscsiadm -m node -T <target name> -p <target portal> -I <iface>
-o new
Example:
# iscsiadm -m node -T iqn.2001-05.com.equallogic:0-8a0906-2d733fe02-d25000ecd
7a4eac6-bfs-2 -p 192.168.2.104:3260 -I qla4xxx-3 -o new
New iSCSI node [qla4xxx:[hw=00:0e:1e:04:11:e6,ip=192.168.2.212,net_if=,
iscsi_if=qla4xxx-3] 192.168.2.104,3260,-1 iqn.2001-05.com.equallogic:
0-8a0906-2d733fe02-d25000ecd7a4eac6-bfs-2] added
3-14
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
List All Targets
# iscsiadm -m node
Example:
# iscsiadm -m node
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-32e33fe02-517000ecd724ea83-karen-1
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-eddd93203-dc1000ece454e721-karen-2
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-ef8d93203-e99000ece484e721-karen-3
192.168.2.105:3260,1
iqn.2001-05.com.equallogic:0-8a0906-f16d93203-92d000ece4b4e721-karen-4
192.168.2.104:3260,-1
iqn.2001-05.com.equallogic:0-8a0906-2d733fe02-d25000ecd7a4eac6-bfs-2
Deleting a Target Node
# iscsiadm -m node -T <target name> -p <target portal> -I <iface>
-o delete
Example:
# iscsiadm -m node -T
iqn.2001-05.com.equallogic:0-8a0906-2d733fe02-d25000ecd7a4eac6-bfs
-2 -p 192.168.2.104:3260 -I qla4xxx-3 -o delete
Target Login and Logout
Login to a Target
# iscsiadm -m node -T <target name> -p <target portal> -I <iface> -l
Example:
# iscsiadm -d 7 -m node --targetname
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b --portal 192.168.2.24:3260
-I qla4xxx-3 -l
Logging in to [iface: qla4xxx-3, target:
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b, portal: 192.168.2.24,3260]
(multiple)
Login to [iface: qla4xxx-3, target:
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b, portal: 192.168.2.24,3260]
successful.
IS0054604-00 A
3-15
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Managing QLogic iSCSI Adapters Using iscsiadm
Login to All Targets
Not specifying the target name, portal, and iface name results in login to all portals
on all nodes/targets through each interface specified in the node configuration.
# iscsiadm -m node -l
To login to all portals on a node/target through each interface:
# iscsiadm -m node -T <target_name> -l
To login to all targets from the specified initiator port:
# iscsiadm -m node -I <iface_name> -l
Login All Sessions with Specified Parameters
For node mode, login all sessions with the node or conn startup values passed in,
except ones marked onboot, if all is passed in.
iscsiadm -m node -T <target_name> -p <target_portal> -I
<iface_name> -L all,manual,automatic
Logout from a Target
# iscsiadm -m node -T <target name> -p <target portal> -I <iface>
-u
Example:
# iscsiadm -d 7 -m node --targetname
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b --portal
192.168.2.24:3260 -I qla4xxx-3 -u
Logging out of [iface: qla4xxx-3, target:
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b, portal:
192.168.2.24,3260]
Logout of [sid: 32, target:
iqn.1986-03.com.hp:storage.msa2012i.0911d7e161.b, portal:
192.168.2.24,3260] successful.
Logout from All Targets
# iscsiadm -m node -u
To log out from all portals on a node/target through each interface:
# iscsiadm -m node -T <target_name> -u
To log out from all targets from the specified initiator port:
# iscsiadm -m node -I <iface_name> -u
3-16
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
3–Open-iSCSI User’s Guide
Features Not Supported
NOTE
If targets are logged in through Open-iSCSI, all targets should be logged out
before unloading the QLogic iSCSI driver, otherwise driver unload will fail
with the following error:
ERROR: Module qla4xxx is in use
Features Not Supported
The features below are not supported in Red Hat Enterprise Linux 6.2. These
features will be supported in Red Hat Enterprise Linux 6.3.
1.
2.
iSNS
Ping
Migrating to Open-iSCSI Driver
On a system that was successfully upgraded from RHEL 6.1 to RHEL 6.2,
discovery and login of targets in Flash is managed by the QLogic iSCSI driver and
firmware. These targets (except boot targets) are exported to sysfs and can be
viewed from sysfs.
NOTE
For information about upgrading from RHEL 6.1 to RHEL 6.2, refer to the
following Technical Note:
Because the RHEL 6.2 Inbox driver does not support the QLogic management
applications iscli(SANsurfer iSCSI CLI) and qaucli(QConvergeConsole
CLI), Open-iSCSI must be used for all new target management.
Targets added through iscsiadmare saved in the Open-iSCSI persistent
database. The operations listed in “Managing QLogic iSCSI Adapters Using
iscsiadm” on page 3-4 are available for management of targets added through
Open-iSCSI.
NOTE
Targets added from Flash cannot be managed using the iscsiadm
interface.
IS0054604-00 A
3-17
Download from Www.Somanuals.com. All Manuals Search And Download.
4 Known Issues
This section lists currently known issues and provides a brief explanation of each
issue.
QLogic Application Limitations
The RHEL 6.2 and SLES 11 SP2 inbox drivers do not support the following
QLogic applications:
iscli(SANsurfer iSCSI CLI)
qaucli(QConvergeConsole CLI)
The QLogic iSCSI driver and firmware handle discovery and login to targets
in Flash and also export them to sysfs where they can be viewed.
Target entries that have been made persistent in Flash on RHEL 6.2 and
SLES 11 SP2 cannot be managed by the Open-iSCSI iscsiadm interface.
All newly added targets can be managed by Open-iSCSI.
CHAP Limitations
At present, the CHAP entries in Flash cannot be updated or deleted using
iscsiadm.
IS0054604-00 A
4-1
Download from Www.Somanuals.com. All Manuals Search And Download.
4–Known Issues
CHAP Limitations
4-2
IS0054604-00 A
Download from Www.Somanuals.com. All Manuals Search And Download.
Download from Www.Somanuals.com. All Manuals Search And Download.
Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com
International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan
© 2012 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QConvergeConsole, QLogic, the
QLogic logo, and SANsurfer are registered trademarks of QLogic Corporation. Linux is a registered trademark of Linus Torvalds. Novell, SLES, and
SUSE are registered trademarks of Novell, Inc. Red Hat and RHEL are trademarks or registered trademarks of Red Hat, Inc. All other brand and
product names are trademarks or registered trademarks of their respective owners. Information supplied by QLogic Corporation is believed to be
accurate and reliable. QLogic Corporation assumes no responsibility for any errors in this brochure. QLogic Corporation reserves the right, without
notice, to make changes in product design or specifications.
Download from Www.Somanuals.com. All Manuals Search And Download.
|