EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. For
the most up-to-date regulatory document for your product line, go to the EMC Powerlink website.
All other trademarks used herein are the property of their respective owners.
2
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
2Slot requirements of EMC-supported QLogic adapters ............................32
3QLogic BIOS settings for Fibre Channel HBAs ..........................................40
4Supported FC and FCoE in kernel driver versions ....................................49
5Supported FC and FCoE out of kernel driver versions .............................59
6QLogic v7.x series driver parameters ...........................................................79
7Supported iSCSI in kernel driver versions ..................................................89
8Supported iSCSI out of kernel driver versions ...........................................95
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
9
Tab les
10
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Preface
As part of an effort to improve and enhance the performance and capabilities
of its product line, EMC from time to time releases revisions of its hardware
and software. Therefore, some functions described in this document may not
be supported by all revisions of the software or hardware currently in use.
For the most up-to-date information on product features, refer to your
product release notes.
If a product does not function properly or does not function as described in
this document, please contact your EMC representative.
This guide describes the features and setup procedures for Linux
hosts with QLogic host bus adapters (HBAs) and converged network
adapters (CNAs) to EMC Symmetrix, EMC VNX series, and EMC
CLARiiON storage systems.
AudienceThis guide is intended for use by storage administrators, system
programmers, or operators who are involved in acquiring, managing,
or operating Symmetrix, VNX series, or CLARiiON, and host devices.
Readers of this guide are expected to be familiar with the following
topics:
◆Symmetrix, VNX series, and CLARiiON system operation
◆Linux operating environment
◆QLogic adapters and drivers
EMC Support MatrixFor the most up-to-date information, always consult the EMC Support
Matrix(ESM), available through E-Lab Interoperability Navigator
(ELN) at: http://elabnavigator.EMC.com, under the PDFs and Guides tab.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
11
Preface
IMPORTANT
!
CAUTION
!
Related
documentation
Conventions used in
this document
The following related documents are available on Powerlink:
◆EMC Host Connectivity Guide for Linux
◆EMC Linux iSCSI Attach Release Notes
◆The EMC Networked Storage Topology Guide has been divided into
several TechBooks and reference manuals. These are available
through the E-Lab Interoperability Navigator, Topology Resource Center tab, at http://elabnavigator.EMC.com.
◆For information on Unisphsere and Navisphere, refer to the
documentation on EMC Powerlink at
http://Powerlink.EMC.com.
EMC uses the following conventions for special notices.
Note: A note presents information that is important, but not hazard-related.
An important notice contains information essential to operation of
the software.
A caution contains information essential to avoid data loss or
damage to the system or equipment.
Typographical conventions
EMC uses the following type style conventions in this document:
NormalUsed in running (nonprocedural) text for:
•Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
•Names of commands, daemons, options, programs,
processes, services, applications, utilities, kernels,
notifications, system call, man pages
12
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Italic:
Courier
Courier bold
Courier italic
< >
[ ]
|
{ }
...
Preface
Used in procedures for:
•Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
•What user specifically selects, clicks, presses, or types
Used in all text (including procedures) for:
•Full titles of publications referenced in text
•Emphasis (for example a new term)
•Variables
Used for:
•System output, such as an error message or script
•URLs, complete paths, filenames, prompts, and syntax when
shown outside of running text
Used for:
•Specific user input (such as commands)
Used in procedures for:
•Variables on command line
•User input variables
Angle brackets enclose parameter or variable values supplied by
the user
Square brackets enclose optional values
Vertical bar indicates alternate selections - the bar means “or”
Braces indicate content that you must specify (that is, x or y or z)
Ellipses indicate nonessential information omitted from the
example
Where to get helpEMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Powerlink website (registration required) at:
http://Powerlink.EMC.com
Technical support — For technical support, go to EMC Customer
Service on Powerlink. To open a service request through Powerlink,
you must have a valid support agreement. Please contact your EMC
sales representative for details about obtaining a valid support
agreement or to answer any questions about your account.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
13
Preface
Your commentsYour suggestions will help us continue to improve the accuracy,
organization, and overall quality of the user publications. Please send
your opinion of this document to:
techpub_comments@EMC.com
14
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Invisible Body Tag
1
Introduction
This document describes the procedures for installing an
EMC-approved QLogic host bus adapter (HBA) or converged
network adapter (CNA) into a Linux host environment and
configuring the host for connection to an EMC storage array over
Fibre Channel, Fibre Channel over Ethernet (FCoE), or iSCSI.
◆ Purpose of this document................................................................. 16
This document is meant to assist in the installation and configuration
of QLogic Fibre Channel host bus adapters (HBAs) and Fibre
Channel Over Ethernet (FCoE) converged network adapters (CNAs),
and iSCSI HBAs in Linux environments. The focus of this document
is to enable the integrated QLogic driver in the Linux distributions
for EMC
®
-supported QLogic adapters or Fibre Channel adapters or
to set up Linux hosts using the EMC-supported driver for QLogic
adapters, available from the EMC-approved section of the QLogic
website.
Review the EMC Support Matrixor contact your EMC representative
for the latest information on qualified adapters, drivers, and Linux
distributions.
Note: EMC does not support mixing different types of Fibre Channel adapter
(including different types from the same vendor) in a server.
Fibre Channel
Fibre Channel over Ethernet
16
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
The Fibre Channel adapter driver functions as a device driver layer
below the standard Linux SCSI adapter driver. The Fibre Channel
interface therefore is transparent to the Linux disk administration
system.
EMC supports the QLogic Fibre Channel over Ethernet (FCoE)
Converged Network Adapter (CNA). FCoE adapters provide a
method to converge both Fibre Channel and Ethernet traffic over a
single physical link to a switch infrastructure which manages both
storage (SAN) and network (IP) connectivity within a single unit.
The benefits of FCoE technology become apparent in large data
centers:
◆Where dense, rack-mounted and blade server chassis exist.
◆Where physical cable topology simplification is a priority.
iSCSI
Introduction
◆In virtualization environments, where several physical storage
and network links are commonly required.
The installation of the QLogic FCoE CNA provides the host with an
Intel-based 10 gigabit Ethernet interface (using the existing in-box
drivers), and an QLogic Fibre Channel adapter interface, which
requires the installation of the supported driver revision.
Following installation of the proper driver for the FCoE CNA, the
Fibre Channel interface will function identically to that of a standard
QLogic Fibre Channel HBA, as the FCoE simply encapsulates Fibre
Channel traffic within ethernet frames. As such, FC-based content
within this document also applies directly to the QLogic FCoE CNAs.
In-depth information about FCoE and its supported features and
topologies can be found in the Fibre Channel over Ethernet (FCoE) TechBook available through the E-Lab Interoperability Navigator,
Topology Resource Center tab, at http://elabnavigator.EMC.com.
The iSCSI HBA provides PCI connectivity to SCSI using the iSCSI
protocol. iSCSI enables the use of IP-based SANs, which are similar to
Fibre Channel SANs. The QLA40xx-Series HBA implements the
TCP/IP and iSCSI protocols on the HBA and offloads the host of any
I/O protocol processing. This type of adapter is also referred to by
QLogic as an iSCSI Offload Engine (iSOE). Offloading the host frees
the system to perform other tasks and optimizes system performance.
The QLogic iSCSI HBA driver functions as a device driver layer
below the standard Linux SCSI adapter driver. The iSCSI interface,
therefore, is transparent to the Linux disk administration system.
Host connectivity
17
Introduction
Boot device support
Linux hosts using QLogic adapters have been qualified for booting
from EMC storage array devices interfaced through Fibre Channel
and iSCSI as specified in the EMC Support Matrix.
The EMC Symmetrix
®
, EMC VNX™ series, or EMC CLARiiON®
device that is to contain the Master Boot Record (MBR) for the host
must have a lower logical unit number (LUN) than any other device
visible to the host. This device should be mapped as /dev/sda by the
Linux operating system for the boot to succeed from the device.
Refer to Chapter 7, ”Configuring a Boot Device on an EMC Storage
Array,” for further information on booting from the SAN.troduction
18
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Zoning
FC and FCoE
Introduction
This section contains general configuration guidelines when
connecting a Linux server via Fibre Channel or iSCSI to an EMC
storage array.
Note: Multi-initiator zones are not recommended in a Linux fabric
environment.
When using Linux hosts in a fabric environment, the zoning must be
set up as single initiator and single target zoning. A single
initiator/single target zone is composed of one adapter and one EMC
storage array port. Storage array ports can be shared among adapters;
however, each adapter must be in its own zone.
Note: Multi-initiator zones are not recommended in a Linux fabric
environment.
iSCSI
Follow the guidelines outlined by EMC. Be aware that using
improper settings may cause erratic behavior. In particular, note the
following:
◆Each QLogic iSCSI HBA in a Linux server must be on a separate
subnet.
◆A single host can not mix HBAs and NICs to connect to the same
array or different arrays.
◆A single host may not attach to an EMC Fibre Channel Array and
an EMC iSCSI Array simultaneously.
◆QLogic SANsurfer or iscli are required to be installed in order to
configure iSCSI HBAs to connect to iSCSI targets
Zoning
19
Introduction
k
SPA 0 SPA 1 SPB 0 SPB 1
y
k
Figure 1 provides a zoning example.
Linux Server
HBA or NIC
sub-networ
HBA or NIC
sub-networ
Arra
Figure 1Zoning example
EMC storage array-specific settings
Refer to the EMC Host Connectivity Guide for Linux, available at
http://Powerlink.EMC.com, for EMC storage array-specific settings.
20
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Invisible Body Tag
2
Installation Steps
This chapter outlines the prerequisisites for first-time installation,
offers a summary of the installation steps with links to the
appropriate sections, and provides information on installing the
adapter.
Review the EMC Support Matrix for the latest information on
approved adapters and drivers.
◆ Prerequisites for first-time installation ........................................... 22
◆ Summary of installation steps.......................................................... 24
◆ Installing the adapter......................................................................... 27
Installation Steps
21
Installation Steps
IMPORTANT
!
Prerequisites for first-time installation
In order to complete a first-time installation of the QLogic adpater in
your server, you will need the following:
◆“Operating system” on page 22
◆“QLogic SANSurfer and SANSurfer CLI” on page 22
◆“BIOS and firmware” on page 22
◆“Linux driver” on page 23
Operating systemBefore the adapter is installed, the Linux operating system must be
installed and properly configured. Install the Linux kernel from the
distribution installation CD by following the procedure provided in
the distribution installation guide. Partition the boot drive, and select
the packages and services necessary for the host.
Include the kernel source/development package and the gcc
compiler tools during the installation. If these tools are not
installed, then the out-of-kernel driver installation may fail and the
driver will not be installed.
QLogic SANSurfer and
SANSurfer CLI
QLogic's SANsurfer program is a GUI-based utility and the
SANsurfer CLI is a text-based utility. Both applications may be
installed on any Linux system and used to manage, configure, and
update the EMC-approved QLogic adapters.
Complete documentation and the EMC-qualified versions of
SANsurfer and the SANsurfer CLI are available for download from
the EMC-approved section of the QLogic website at
http://www.qlogic.com.
Follow the Downloads > EMC links to your adapter for the
appropriate version.
BIOS and firmwareThe version of BIOS and firmware (adapter firmware for your iSCSI
HBA, and CEE/Menlo firmware for your CNA) per the EMC Support
Matrix for your supported configuration.
These are available for download from the EMC-approved section of
the QLogic website
22
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
at http://www.qlogic.com.
Installation Steps
Follow the Downloads > EMC links to your adapter for the
appropriate version.
Linux driverThe Linux driver for your HBA or CNA per theEMC Support Matrix
for your supported configuration.
EMC supports both in-kernel and out-of-kernel drivers.
Note: The installation of the in-kernel driver occurs when you install your
Linux distribution of choice.
Refer to the latest EMC Support Matrix for your specific Linux
distribution, kernel version, and driver to determine whether or not
you need to proceed with the following out-of-kernel instructions.
If your installation requires an out of kernel driver, download it from
the EMC-approved section of the QLogic website
at
http://www.qlogic.com.
Follow the Downloads > EMC links to your adapter for the
appropriate version.
Prerequisites for first-time installation
23
Installation Steps
Summary of installation steps
Ta bl e 1describes the procedures for installing an EMC-approved
QLogic adapters into a Linux host and configuring the host for
connection to an EMC Storage Array over Fibre Channel (FC) or Fibre
Channel over Ethernet (FCoE).
Tab le 1Installation steps (page 1 of 3)
StepInstructionsFor Fibre Channel, refer toFor Fibre Channel over
1Install the
adapter .
2Verify the
BIOS version
3Install the BIOS.
There are three states:
•If no
version is
installed
•If wrong
version is
installed
•If correct
version is
installed
“Installing the adapter” on
page 27
“Verifying the correct BIOS
version” on page 36
“Upgrading the adapter BIOS”
on page 37
“Upgrading the adapter BIOS”
on page 37
Proceed to step 4.Proceed to step 4.Proceed to step 4.
Ethernet (FCoE), refer to
“Installing the adapter” on
page 27
“Verifying the correct BIOS
version” on page 36
“Upgrading the adapter BIOS”
on page 37
“Upgrading the adapter BIOS”
on page 37
For iSCSI, refer to
“Installing the adapter” on
page 27
“Verifying the correct BIOS
version” on page 36
“Upgrading the adapter BIOS” on
page 37
“Upgrading the adapter BIOS” on
page 37
24
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Tab le 1Installation steps (page 2 of 3)
Installation Steps
StepInstructionsFor Fibre Channel, refer toFor Fibre Channel over
Ethernet (FCoE), refer to
4Install the driver.
There are two states:
•In kernelFor drivers listed in the
Support Matrix
drivers, there is no need to install
a driver since the process of
installing the operating system
has already included the driver.
Table 4 on page 49 lists
supported QLogic driver
versions .
If in kernel, proceed to Step 5.
•Out of
kernel
“Installation instructions for the
out of kernel QLogic driver” on
page 61
EMC
as in kernel
For drivers listed in the
Support Matrix
as in kernel
drivers, there is no need to install
a driver since the process of
installing the operating system
has already included the driver.
Table 4 on page 49 lists
supported QLogic driver
versions .
If in kernel, proceed to Step 5.
“Method 2: Installing the QLogic
v7.xx.xx/v8.xx.xx driver via the
QLogic installation script” on
page 65.
EMC
For iSCSI, refer to
For drivers listed in the EMC
Support Matrix as in kernel
drivers, there is no need to install
a driver since the process of
installing the operating system
has already included the
driver.
Table 7 on page 89 lists
supported QLogic driver
versions.
If in kernel, perform the steps
outlined in “Installation
instructions for the in kernel
QLogic driver in Linux 2.6.x
kernels” on page 91 to disable
the qla3xxx driver then proceed
to Step 5.
Proceed to either “Installation
instructions for the out of kernel
QLogic driver” on page 96
Summary of installation steps
25
Installation Steps
Tab le 1Installation steps (page 3 of 3)
StepInstructionsFor Fibre Channel, refer toFor Fibre Channel over
Ethernet (FCoE), refer to
5Install the firmware.
There are two states:
•Wrong
firmware
The adapter firmware is part of
the Linux driver and cannot be
altered..
Proceed to Step 6.
The adapter firmware is part of
the Linux driver and cannot be
altered.
“Updating the QLogic CEE
/Menlo firmware for FCoE
adapters” on page 130
Once corrected, proceed to Step
6.
•Correct
Proceed to Step 6.Proceed to Step 6.Once corrected, proceed to Step
firmware
6Connect to the
storage.
7Reconfigure
the device.
“Zoning and connection planning
in a Fibre Channel or Fibre
Channel over Ethernet
environment” on page 134
“Device reconfiguration
procedures for FC and FCoE” on
page 195
“Zoning and connection planning
in a Fibre Channel or Fibre
Channel over Ethernet
environment” on page 134
“Device reconfiguration
procedures for FC and FCoE” on
page 195
For iSCSI, refer to
“Updating the QLogic firmware
for iSCSI adapters” on page 131
Once corrected, proceed to Step
6.
6.
“Zoning and connection planning
in an iSCSI environment” on
page 135
Proceed to either “Device
reconfiguration procedures for
the iSCSI 3.x driver” on page 196
or “Device reconfiguration
procedures for the iSCSI 5.x
driver” on page 198
26
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing the adapter
2
1
3
2
1
3
Follow the instructions included with your adapter. The adapter
installs into a single slot.
To connect the cable to the adapter:
1. (Optical cable only) Remove the protective covers on each
2. Plug one end of the cable into the connector on the adapter as
Installation Steps
fiber-optic cable.
shown in the appropriate figure in this step. (The hardware might
be rotated 90 degrees clockwise from the orientation shown.)
• Fibre Channel adapter connectivity options include copper
cable with DB9 connector, SC optical, and LC optical cable, as
shown next.
– Copper cable with DB9 connector:
– SC optical cable:
– LC optical cable:
Installing the adapter
27
Installation Steps
2
1
3
• Fibre Channel over Ethernet converged network adapter
(CNA) connectivity options include LC optical and Cisco
SFP+, shown next.
– LC optical cable:
– Cisco SFP+ (Twinax cable)
3. Plug the other end of the cable into a connector on the storage
system or a hub/switch port.
4. Label each cable to identify the adapter and the
storage/switch/hub port to which it connects.
5. After connecting all adapters in the server, power up the server.
Matching the adapter with the correct PCI slot
When choosing an adapter for your server, it is important to know
which adapter is compatible with your server's PCI/PCI-X/PCI
Express slots. Certain adapter models have specific voltage
requirements or physical limitations that allow them to work only in
28
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
specific slots.
Installation Steps
Servers have several different bus slot types for accepting adapters:
◆PCI
◆PCI-X
◆PCI-X 2.0
◆PCI-Express
PCI slots can be 32-bit and 64-bit (denoted by their 124-pin or 188-pin
connectors.) These slots have plastic "keys" that prevent certain
adapters from fitting into them. These keys work with the cutout
notches in the adapter edge connector so that only compatible
adapters will fit into them. This is done because of the voltage
characteristics of the adapter. Inserting a 3.3v adapter into a 5v slot
would cause severe damage to both the adapter and the server.
Therefore, the slot keys denote the type of voltage provided by the
slot and effectively prevent a voltage incompatible adapter from
being inserted.
Figure 2 shows how PCI slots will appear with their keys and what
type of voltage is provided for each slot type.
Figure 2PCI slot types and voltage key locations
Installing the adapter
29
Installation Steps
Figure 3 shows the adapter edge connectors compatible with the PCI
slots shown in Figure 2 on page 29. Note adapter 5, which shows a
universal adapter edge connector. Universal adapters are compatible
with both 3.3 V and 5 V PCI slots.
Figure 3Adapter edge connectors
30
PCI-X(or PCI Extended) slots increase the speed with which data
travels over the bus. PCI-X slots appear identical to a 64-bit PCI slot
keyed for 3.3 V. (Refer to number 3 in Figure 2 on page 29 and
Figure 3.) PCI-X slots are backwards compatible with 3.3 V PCI
adapters and universal adapters. Inserting standard PCI adapters
into PCI-X slots will lower the bus speed as they cannot take
advantage of the improved performance.
PCI-X 2.0 is the next generation of PCI-X buses. PCI-X 2.0 increases
the bus speed again, providing more performance for adapters.
PCI-X 2.0 slots also appear identical to a 64-bit PCI slot keyed for 3.3
V. (Refer to number 3 in Figure 2 and Figure 3.) PCI-X 2.0 is also fully
backward compatible with 3.3 V PCI and PCI-X.
PCI Express (sometimes noted as PCIe) is a new bus type that uses
the existing PCI model, but implements it in a faster, serial protocol.
Because of the serial way it transmits data, the PCI Express bus slot
can be different sizes depending on the throughput it supports. PCI
Express slot speeds are expressed in "lanes" and are normally shown
as x1, x4, x8, and x16. Each type of slot is a different length (as shown
in Figure 4 on page 31) and adapter edge connectors will also be of
varying lengths depending on how many lanes they require for
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
throughput. Because of how PCI Express slots are keyed, an x1
adapter can be inserted in all four slot types, as the adapter will
negotiate with the slot to determine the highest mutually supported
number of lanes. However, an adapter requiring x16 lanes will not fit
into a smaller slot.
Figure 4PCI Express slots
Installation Steps
Figure 5 shows x1, x4, and x16 lane slots aligned on a mainboard. You
can see how the slots are keyed so that low-lane adapters can fit into
larger slots.
Figure 5PCI Express slots aligned
Installing the adapter
31
Installation Steps
QLogic offers adapters for each bus/slot type available. Tab le 2
shows each of the EMC-supported QLogic adapters, and their
respective slot requirements. Be sure to consult both your server user
guide and QLogic to ensure that the adapter you want to use is
compatible with your server's bus.
Tab le 2Slot requirements of EMC-supported QLogic adapters
Remember that some of the older adapters are tall (also referred to as
full-height) and may not fit into a server with a low-profile chassis.
These factors must be considered before implementing your
configuration to avoid unnecessary delays and possible equipment
swaps or returns.
Currently, the QLogic FCoE converged network adapters (CNAs)
require servers that can accommodate full-height, full-length PCI
Express adapters. Always refer to the EMC Support Matrix for the
32
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
most up-to-date information on which servers support these
adapters.
Installation Steps
Installing the adapter
33
Installation Steps
34
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Invisible Body Tag
3
Installing and Configuring
the BIOS Settings
This chapter describes the procedures for installing and configuring
the BIOS settings.
◆ Verifying and configuring the BIOS settings ................................. 36
◆ Manually setting the topology for QLogic Fibre Channel
After the adapter is installed, follow these steps during system boot
to verify and configure adapter firmware settings.
To use SANsurfer or SANsurfer CLI for this function refer to the
SANsurfer or SANsurfer CLI documentation you have downloaded.
Refer to the EMC Support Matrix for required BIOS versions for
qualified adapters.
Verifying the correct BIOS version
You can determine the BIOS version at boot time from the QLogic
banner or from the Fast!Util Options menu.
◆From the banner — Boot the host and watch for the banner
(shown in the QLA2340 example below, with the ROM BIOS
version highlighted):
• If the banner displays the required version, continue to the
section “EMC recommended adapter BIOS settings” on
page 39.
• If the banner does not display the required version, upgrade
the firmware as described under the “Upgrading the adapter
BIOS” on page 37; then proceed to “EMC recommended
adapter BIOS settings” on page 39.
◆From the QLogic Fast!Util Options menu:
a. Boot the host. When the QLogic banner appears, press
CTRL-Q to enter Fast!Util.
b. Select Configuration Settings from the Fast!Util Options
menu.
c. Select Adapter Settings from the Configuration Settings
menu.
36
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Upgrading the adapter BIOS
The BIOS may be upgraded using one of the following three
methods:
◆“Method One: Upgrading the adapter BIOS using the NVRAM
◆“Method 2: Upgrading the adapter BIOS using QLogic
◆“Method 3: Upgrading the adapter BIOS using QLogic SANsurfer
Installing and Configuring the BIOS Settings
d. Under Adapter Settings, note the BIOS version:
– If the banner displays the required version, continue to
“EMC recommended adapter BIOS settings” on page 39.
– If the banner does not display the required version,
upgrade the firmware as described under the “Upgrading
the adapter BIOS” on page 37; then proceed to “EMC
recommended adapter BIOS settings” on page 39.
file on a DOS bootable floppy” on page 37
SANsurfer” on page 38
CLI” on page 39
Method One: Upgrading the adapter BIOS using the NVRAM file on a DOS bootable floppy
Follow these steps to upgrade the QLogic BIOS using the NVRAM
file on a DOS bootable floppy:
1. Obtain the latest version of the BIOS from the QLogic website:
a. Access http://www.qlogic.com.
b. Click Downloads at the left side of the screen.
c. Click the EMC link below OEM Models.
d. Find the NVRAM file for the adapter(s) in your system, and
click the associated Download link to save the file.
2. The file is a self-extracting .zip containing the BIOS and NVRAM
files. Make sure flasutil.exe and the source files (BIN, DEF, DAT,
and BAT files) are in the same directory. EMC-specific settings are
contained in files named emcXXXX.def and emcXXXX.dat where
XXXX is the model number of the adapter.
These settings files (also referred to as NVRAM setting files)
should also be in the same directory with the flash utility and
source files. Note that some versions of BIOS may use different
filenames depending on the version and adapter model.
Verifying and configuring the BIOS settings
37
Installing and Configuring the BIOS Settings
3. Insert the BIOS upgrade installation diskette into the floppy
4. Reboot the host.
5. After the host has rebooted, a DOS prompt appears. Type
Be sure to check the readme included with the BIOS files to make
sure you have all of the appropriate files before proceeding.
a. Insert a diskette into a Microsoft Windows 9x machine.
b. Open any DOS window.
c. At the DOS prompt, format the diskette by entering:
format /s a:
d. At the DOS prompt, change directory (cd) to the location of
the saved zipped file, then extract the file to the diskette.
Note: The QLogic adapter(s) must be installed in the host before
proceeding.
drive.
flasutil /L /F and press Enter.
Note: The adapter BIOS upgrade might take a few minutes.
6. After the upgrade is complete, remove the diskette and reboot the
host. During startup, the QLogic banner should display the new
BIOS version.
Method 2: Upgrading the adapter BIOS using QLogic SANsurfer
The SANsurfer GUI may be downloaded from the EMC-approved
section of the QLogic website. To update the BIOS using the
SANsurfer CLI, refer to the QLogic provided documentation on their
website for detailed instructions.
To invoke the GUI, run the following command from a terminal
window:
/opt/QLogic_Corporation/SANsurfer/SANsurfer &
When upgrading the BIOS for QLogic 4 GB adapters, the minimum
required version of the QLogic SANsurfer GUI is 2.0.30b52.
When using QLogic QLA40xx-series HBAs, the minimum required
version of the QLogic SANsurfer GUI is 4.01.00.
38
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the BIOS Settings
Method 3: Upgrading the adapter BIOS using QLogic SANsurfer CLI
The SANsurfer CLI (scli) is installed as part of the qlinstaller or may
be downloaded from the EMC-approved section of the QLogic
website. To update the BIOS using the SANsurfer CLI, refer to the
QLogic provided documentation on their website for detailed
instructions.
To invoke the CLI, run the following command:
/opt/QLogic_Corporation/SANsurferCLI/scli
When upgrading the BIOS for QLogic 4 GB adapters, the minimum
required version of the QLogic SANsurfer CLI is 1.06.16build23.
When using QLogic QLA40xx-series HBAs, te minimum required
version of the QLogic SANsurfer CLI is 1.0.30.00.
EMC recommended adapter BIOS settings
EMC requires configuring the QLogic BIOS settings with the
EMC-approved NVRAM settings file. This file contains all of the
BIOS settings for the QLogic adapters that have been tested and
approved for connection to EMC storage arrays.
Refer to the EMC Support Matrixfor required NVRAM versions for
qualified adapters.
EMC recommended NVRAM settings for Linux
This section contains the recommended NVRAM settings for Linux
for the following adapters:
◆“Fibre Channel HBAs” on page 39
◆“Fibre Channel over Ethernet (FCoE) CNAs” on page 42
◆“iSCSI HBAs” on page 42
Fibre Channel HBAs
Tab l e 3 on pag e 40 lists the NVRAM parameters and their values. The
QLogic default values are those that ship with a standard adapter
that was not included in an EMC package. The EMC-recommended
settings depend upon whether failover functionality is used. The
settings listed under the No Failover Functionality heading are those
that have been pre-configured in the EMC-approved NVRAM file.
The settings listed under the With PowerPath
®
or VEERITAS DMP
Verifying and configuring the BIOS settings
39
Installing and Configuring the BIOS Settings
heading are those that have been tested and determined to be
applicable in a Linux environment.
The settings are configurable in NVRAM using the Host Adapter Settings, Advanced Settings, and Extended Firmware Settings
menus. To use SANsurfer or the SANsurfer CLI to modify the
NVRAM settings, refer to the SANsurfer or SANsurfer CLI
documentation from QLogic.
Tab le 3QLogic BIOS settings for Fibre Channel HBAs (page 1 of 2)
Extended Error LoggingDisabled •Disabled (Do not use
debugging)
•Enable (Use debugging)
•Disabled (Do not use
debugging)
•Enable (Use debugging)
Operation Mode000
Interrupt Delay Timer000
Selectable Boot settings
Selectable BootDisabledDisabledDisabled
(Primary) Boot Port Name, LUNWWNN*WWNN*WWNN*
Boot Port Name, LUN000
Boot Port Name, LUN000
Boot Port Name, LUN000
* The WWNN of the server's boot LUN must be listed in this field.
Note: The QLogic driver may override the EMC-recommended NVRAM
values. Unless otherwise specified, use the default implemented by the
driver.
The values for the Connection Options parameter are as follows:
◆0 for Loop Only
◆1 for Point-to-Point
◆2 for Loop preferred, otherwise Point-to-Point
Verifying and configuring the BIOS settings
41
Installing and Configuring the BIOS Settings
Note: For Linux attach, EMC recommends setting the Connection Options
parameter to 1 when attached to a fabric and to 0 when attached to an EMC
storage array directly.
Fibre Channel over Ethernet (FCoE) CNAs
EMC recommends the default settings for the QLogic CNAs. There
are no settings to the BIOS or NVRAM to alter.
iSCSI HBAs
The only settings that are required to complete the installation are
those of the intended iSCSI targets. The iSCSI targets must reside on
the same subnet as the initiator.
The iSCSI targets must be configured after the QLogic v3.x-series or
5.x-series driver has been installed and is operating. Additionally, to
establish these settings, the SANsurfer GUI or the SANsurferCLI
must be downloaded and installed on the host.
42
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the BIOS Settings
Manually setting the topology for QLogic Fibre Channel
adapters
The EMC default setting for the topology is set to 2 (Loop preferred;
otherwise, point to point).
For Linux environments, it is recommended that the Connection
Options parameter be set to 1 when attached to a fabric and to 0 when
directly attached to an EMC storage array.
Follow these steps to set the NVRAM variables for the topology:
1. Boot the host. When the QLogic banner appears, press Ctrl-Q to
enter the Fast!Util menu.
2. Select Configuration Settings from the Fast!Util Options menu.
3. Select Host Adapter Settings from the Configuration Settings
menu.
4. Select Connection Options (topology) and press Enter.
5. Select the appropriate topology and press Enter:
• FC-AL - 0 (loop only)
• FC-SW - 1 (point to point only)
6. Press ESC to return to the Fast!Util Options menu.
7. When prompted to save the changes made to the current adapter,
select Save Changes.
8. If you have more adapters to configure, choose Select Host Adapter and repeat steps 2 through 7 for each adapter.
9. Press ESC to exit the Fast!Util menu.
10. Reboot the host.
Manually setting the topology for QLogic Fibre Channel adapters
43
Installing and Configuring the BIOS Settings
Manually setting the data rate for QLogic Fibre Channel
adapters
The EMC default setting for the data rate on the QLA23xx/QLE23xx
adapters is Auto Select mode. If necessary, the mode may be set
manually to 1 GB, 2 GB, or Auto Select mode.
The EMC default setting for the data rate on the QLA24xx/QLE24xx
4 GB capable adapters is Auto Select mode. If necessary, the mode
may be set manually to 1 GB, 2 GB, 4 GB, or Auto Select mode.
To use SANsurfer or the SANsurfer CLI to modify the NVRAM
settings, refer to the SANsurfer or SANsurfer CLI documentation
from QLogic.
Note: For any device connected to the adapter, set the device data rate (if
applicable) before setting the adapter data rate.
Follow these steps for each QLogic adapter to be modified:
1. Boot the host. When the QLogic banner appears, press Ctrl-Q to
enter the Fast!Util menu.
44
2. Select Configuration Settings from the Fast!Util Options menu.
3. Select Host Adapter Settings from the Configuration Settings
menu.
4. Select the Data Rate setting and press Enter.
5. Select the appropriate speed for the device to which the QLA23xx
adapter will connect. The options are 0 for 1 GB/s, 1 for 2 GB/s,
and 2 for Auto Select.
6. Press ESC to return to the Fast!Util Options menu.
7. When prompted to save the changes made to the current adapter,
select Save Changes.
8. Repeat steps 2 through 7 for each adapter.
9. Press ESC to exit the Fast!Util menu.
10. Reboot the host.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Invisible Body Tag
4
Installing and Configuring
the Linux Host with the
QLogic Driver
This chapter describes the procedures for installing and configuring
the driver. It is divided into the following sections.
◆ QLogic SANsurfer and SANsurfer CLI.......................................... 47
◆ Fibre Channel and FCoE in kernel driver versions....................... 49
◆ Fibre Channel and FCoE out of kernel driver versions................ 59
◆ iSCSI in kernel driver versions......................................................... 89
◆ iSCSI out of kernel driver versions.................................................. 95
Installing and Configuring the Linux Host with the QLogic Driver
45
Installing and Configuring the Linux Host with the QLogic Driver
Introduction
Using the QLogic adapter with the Linux operating system requires
adapter driver software. The driver functions at a layer below the
Linux SCSI driver to present Fibre Channel (FC), FibreChannel over
Ethernet (FCoE) or iSCSI devices to the operating system as if they
were standard SCSI devices.
EMC supports the QLogic in kernel default drivers for FC and FCoE,
as listed in Ta b le 4 o n pa g e 4 9, in the distribution in most later
operating systems. Tabl e 5 on page 5 9 lists QLogic out of kernel
driver versions supported with corresponding OS updates for FC and
FCoE. (These driver versions require manual installation.)
Installation of these drivers are further discussed in the following
sections:
◆“Fibre Channel and FCoE in kernel driver versions” on page 49
◆“Fibre Channel and FCoE out of kernel driver versions” on
page 59
EMC also supports the QLogic in kernel default drivers for iSCSI, as
listed in Ta b le 7 o n pa ge 8 9, in the distribution in most later operating
systems. Tabl e 8 o n pa ge 95 lists QLogic out of kernel driver versions
supported with corresponding OS updates for iSCSI. (These driver
versions require manual installation.) Installation of these drivers are
further discussed in the following sections:
46
◆“iSCSI in kernel driver versions” on page 89
◆“iSCSI out of kernel driver versions” on page 95
Refer to the latest EMC Support Matrix for specific qualified kernel
versions and distributions.
Note: The support stated in the EMC Support Matrix supersedes versions
listed in this document.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
QLogic SANsurfer and SANsurfer CLI
QLogic's SANsurfer program is a GUI-based utility and the
SANsurfer CLI is a text-based utility. Both applications may be
installed on any Linux system and used to manage, configure, and
update the EMC-approved QLogic adapters.
Complete documentation and the EMC-qualified versions of
SANsurfer and the SANsurfer CLI are available for download from
the EMC-approved section of the QLogic website.
http://www.qlogic.com
◆For 4 GB QLogic adapters, the minimum required versions are:
• SANsurfer - 2.0.30b52
– SANsurfer CLI - 1.06.016 build 23
◆For 8 GB QLogic adapters, the minimum required versions are:
• SANsurfer - 2.0.32b
– SANsurfer CLI - 1.06.016 build 23
Note: For SANsurfer usage with Asianux 3.0 SP1 you will need to turn on the
portmap service. This is accomplished by issuing the following Linux
command as the root user.
IOCTL module for RHEL4
chkconfig portmap on
service portmap start
The RHEL4 in kernel driver needs the ioctl module to support
SANsurfer. Using out of kernel driver on RHEL4 does not have this
issue. For RHEL4 U3 and RHEL4 U4, the out of kernel ioctl module
needs to installed before you use SANsurfer.
Note: For RHEL4 U5 or above, the ioctl module is hooked up with the OS and
needs to be loaded manually.
The following is an example procedure to install the ioctl on RHEL4
U3 and RHEL4 U4:
1. Download QLogic Linux IOCTL Module from EMC- approved
site on the QLogic website.
2. Enter tar –xvf qioctl-install.tar
QLogic SANsurfer and SANsurfer CLI
47
Installing and Configuring the Linux Host with the QLogic Driver
3. Enter qioctl-install –install
The following is an example of load IOCTL module on RHLE4 U5
and above with command:
modprobe -v qioctlmod
RPM packages needed for RHEL5
To run the SANsurfer installer under Redhat 5 Linux, if the default
install is selected, the following RPMs need to be installed:
a. For models QLE8140, QLE8142, QLE8150, and QLE8152 only.
b. For model QLE8042 only.
√√√√
√√√√
√√√√
√√√√
a
a
a
a
√√√√
√√√√
√√√√
√√√√
52
What next?If the driver version is not listed in Ta bl e 4 , go to “Fibre Channel and
FCoE out of kernel driver versions” on page 59.
If the driver version is listed in Tab le 4 , refer to the appropriate
section:
◆“Installation instructions for the in kernel QLogic driver for Linux
2.4.x kernel” on page 53
◆“Installation Instructions for the in kernel QLogic driver in Linux
2.6.x kernels” on page 55
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Installation instructions for thein kernel QLogic driver for Linux 2.4.x kernel
The section contains the following instructions for enabling the
QLogic driver:
◆“Enabling the QLogic driver in RHEL 3.0” on page 53
◆“Enabling the QLogic driver in SLES 8” on page 54
Enabling the QLogic driver in RHEL 3.0
To enable this driver, follow these steps:
1. Ensure that the /etc/modules.conf file references an entry for
each installed QLogic adapter.
For each installed QLogic QLA23xx-series adapter, add an entry:
alias scsi_hostadapterN qla2300
where N is the sequential value of each QLogic adapter installed
in the system, beginning with the number after the last host
adapter number entry in the file. (The first host adapter entry
begins with zero.)
Example:
alias scsi_hostadapter1 qla2300
alias scsi_hostadapter2 qla2300
alias eth0 tg3
options scsi_mod max_scsi_luns=255
scsi_allow_ghost_devices=1
2. Whenever /etc/modules.conf is modified, a new ramdisk should
be created to reflect the changes made. Create a new ramdisk
image to include the newly added references to the QLogic
adapters:
cd /boot
mkinitrd -v initrd-$1.img
$1
where $1 is the v2.4.x kernel version currently running.
Installing and Configuring the Linux Host with the QLogic Driver
Enabling the QLogic driver in SLES 8
In order for the driver to be loaded at boot time, the driver must be
listed in the /etc/sysconfig/kernel and /etc/modules.conf files and
the ramdisk must be updated to reflect the changes.
To enable the driver:
1. Edit /etc/sysconfig/kernel:
vi /etc/sysconfig/kernel
a. Add a reference to the QLogic qla2300.o driver in the
a. Add this entry for each installed QLogic adapter:
alias scsi_hostadapterN qla2300
54
where N is the sequential value of each QLogic adapter installed
in the system, beginning with the number after the last host
adapter number entry in the file. (The first host adapter entry
begins with zero.)
Ensure that the QLogic adapter entries are listed after the internal
SCSI host adapter entry in both files.
Example:
alias parport_lowlevel parport_pc
alias scsi_hostadapter sym53c8xx
alias scsi_hostadapter1 qla2300
alias scsi_hostadapter2 qla2300
alias eth0 tlan
options scsi_mod max_scsi_luns=255
scsi_allow_ghost_devices=1
b. Save the changes and quit from vi.
3. Create a new ramdisk to reflect the changes made:
cd /boot
mkinitrd -k vmlinuz-
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
$1
-i initrd-
$1
Installing and Configuring the Linux Host with the QLogic Driver
where $1 is the v2.4.x kernel version currently running.
Example:
cd /boot
mkinitrd -k vmlinuz-2.4.21-295-smp -i initrd-2.4.21-295-smp
4. Reboot the system.
Installation Instructions for the in kernel QLogic driver in Linux 2.6.x kernels
If you are installing the OS after the adapter has been installed in the
server, the OS will automatically detect the adapter, change the
configure file, and build a RAM disk including the driver.
If you have completed a fresh installation of the OS without the
adapter and plan to install it at a later time, or are installing an
adapter in a server with an existing OS installed, refer to the
following sections to enable this driver:
◆“Enabling the QLogic driver in RHEL 4”, next
◆“Enabling the QLogic driver in RHEL 5” on page 56
◆“Enabling the QLogic driver in SLES 9” on page 57
◆“Enabling the QLogic driver in SLES10 and SLES 11” on page 57
Enabling the QLogic driver in RHEL 4
To enable this driver:
1. Ensure that the /etc/modprobe.conf file references an entry for
each installed QLogic adapter.
For each installed QLogic adapter, add an entry:
alias scsi_hostadapterN qla2xxx
where N is the sequential value of each QLogic adapter installed
in the system, beginning with the number after the last host
adapter number entry in the file. (The first host adapter entry
begins with zero.), qla2xxx is the driver name for the adapter
Example:
alias scsi_hostadapter3 qla2xxx
alias scsi_hostadapter4 qla2322
alias scsi_hostadapter5 qla2400
alias scsi_hostadapter6 qla6312
Fibre Channel and FCoE in kernel driver versions
55
Installing and Configuring the Linux Host with the QLogic Driver
Note: QLA2300 manages QLA2310, QLA2340, and QLA2342.
QLA 2322 manages QLE2360 and QLE2362.
QLA2400 manages QLA2460, QLS2462, QLE2460, and QLE2462.
QLA6312 manages QLE220.
2. Whenever /etc/modprobe.conf is modified, a new ramdisk
should be created to reflect the changes made. Create a new
ramdisk image to include the newly added references to the
QLogic adapters:
cd /boot
mkinitrd -v initrd-
where $1 is the v2.6.x kernel version currently running.
1. Ensure that the /etc/modprobe.conf file references an entry for
each installed QLogic adapter.
For installed QLogic adapter, add an entry:
alias scsi_hostadapterN qla2xxx
where N is the sequential value of QLogic adapter installed in the
system, beginning with the number after the last host adapter
number entry in the file. (The first host adapter entry begins with
zero.).
Example:
alias scsi_hostadapter1 qla2xxx
$1
.img
$1
56
2. Whenever /etc/modprobe.conf/ is modified, a new ramdisk
should be created to reflect the changes made. Create a new
ramdisk image to include the newly added references to the
QLogic adapters:
cd /boot
mkinitrd -v initrd-
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
$1
.img
$1
where $1 is the v2.6.x kernel version currently running.
Example:
mkinitrd -v initrd- 2.6.18-8.el5.img 2.6.18-8.el5
3. Reboot the host.
Enabling the QLogic driver in SLES 9
In order for the driver to be loaded at boot time, the driver must be
listed in the /etc/sysconfig/kernel and the ramdisk must be updated
to reflect the changes. To enable the driver:
1. Edit /etc/sysconfig/kernel:
vi /etc/sysconfig/kernel
a. Add a reference to the QLogic driver in the
INITRD_MODULES line:
INITRD_MODULES="reiserfs qla2xxx_conf qla2xxx"
b. Save the changes and quit from vi.
2. 2Create a new ramdisk to reflect the changes made:
Installing and Configuring the Linux Host with the QLogic Driver
cd /boot
mkinitrd -k vmlinuz-
$1
-i initrd-
$1
where $1 is the v2.6.x kernel version currently running.
Example:
cd /boot
mkinitrd -k vmlinuz- 2.6.5-7.244-smp -i initrd- 2.6.5-7.244-smp
3. Reboot the system.
Enabling the QLogic driver in SLES10 and SLES 11
If the server install the OS without the adapter, in order for the driver
to be loaded at boot time, the driver must be listed in the
/etc/sysconfig/kernel and the ramdisk must be updated to reflect
the changes. To enable the driver:
1. Edit /etc/sysconfig/kernel:
vi /etc/sysconfig/kernel
a. Add a reference to the QLogic qla2300.ko driver in the
INITRD_MODULES line:
INITRD_MODULES="piix megaraid_sas processor thermal fan reiserfs qla2xxx"
Fibre Channel and FCoE in kernel driver versions
57
Installing and Configuring the Linux Host with the QLogic Driver
b. Save the changes and quit from vi.
2. Create a new ramdisk to reflect the changes made:
cd /boot
mkinitrd -k vmlinuz-
$1
-i initrd-
$1
where $1 is the v2.6.x kernel version currently running.
Example:
cd /boot
mkinitrd -k vmlinuz- 2.6.16.21-0.8-smp -i initrd-
2.6.16.21-0.8-smp
3. Reboot the system.
58
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Fibre Channel and FCoE out of kernel driver versions
The following installation information is contained in this section:
◆“Supported out of kernel driver versions” on page 59
◆“Installation instructions for the out of kernel QLogic driver” on
page 61
◆“Uninstallation methods for the QLogic v7.xx.xx/v8.xx.xx
driver” on page 76
◆“QLogic SANsurfer and SANsurfer CLI” on page 47
◆“QLogic v7.x and v8.x series driver parameters” on page 79
Supported out of kernel driver versions
Note: Only the QLogic v7.07.xx and the v8.01.xx driver provides support for
the 4 GB-capable QLA24xx/QLE24xx-series adapters, not the less version
driver.
Ta bl e 5 lists the QLogic out of kernel driver versions supported with
corresponding OS updates. These driver versions require manually
installation.
Tab le 5Supported FC and FCoE out of kernel driver versions (page 1 of 2)
OS Driver versionSupported adapters
1/2 Gb4 Gb8 GbCNA
RHEL3 U2 6.07.02-RH2
SLES8 SP36.05.00
RHEL3 U4
RHEL3 U5
SLES8 SP47.03.00
RHEL3 U8
RHEL 3.9
Asianux 1.0 SP3
7.01.01-RH1
7.07.04b6
Fibre Channel and FCoE out of kernel driver versions
√
√
√
√
√√
59
Installing and Configuring the Linux Host with the QLogic Driver
Tab le 5Supported FC and FCoE out of kernel driver versions (page 2 of 2)
OS Driver versionSupported adapters
1/2 Gb4 Gb8 GbCNA
Miracle Linux SE 4.0
RedFlag DC Server 5.0
Haansoft Linux 2006 Server
RHEL4 U3
Miracle Linux SE 4.0 SP1
RedFlag DC Server 5.0 SP1
Haansoft Linux 2006 Server SP1
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
8.03.07.03.11.1-k
a. For model QLE8042 only.
b. For models QLE8140, QLE8142, QLE8150, and QLE8152 only.
c. For models QLE8240, QLE8242, QLE8250, and QLE8252 only.
√
√
√
√
a
b
b
c
Installing and Configuring the Linux Host with the QLogic Driver
Refer to the latest EMC Support Matrix for specific qualified kernel
versions and distributions.
Note: The support stated in the EMC Support Matrix supersedes versions
listed in this document.
Installation instructions for the out of kernel QLogic driver
This section contains the following information for installing the out
of kernel QLogic driver:
◆“Downloading the QLogic v7.x/v8.x-series driver for the
v2.4/v2.6.x kernel” on page 61
◆“Preinstallation instructions for the QLogic v7.xx.xx/v8.xx.xx
driver” on page 62
◆“Method 1: Installing the QLogic v7.xx.xx/v8.xx.xx driver via the
QLogic DKMS RPM” on page 63
◆“Method 2: Installing the QLogic v7.xx.xx/v8.xx.xx driver via the
QLogic installation script” on page 65
◆“Method 3: Installing the QLogic v7.xx.xx driver via the QLogic
RPM” on page 75
Downloading the QLogic v7.x/v8.x-series driver for the v2.4/v2.6.x kernel
Use the following procedure to download the EMC-approved QLogic
driver from the QLogic website.
1. Use a web browser to access the EMC-approved section of the
QLogic website at:
http://www.qlogic.com
2. Depending upon the EMC storage array being used, select the
appropriate link from one of the two following categories:
• EMC VNX series, CLARiiON, Symmetrix,
supported software
• EMC CLARiiON AX100 supported software
3. After selecting a category, find the adapter model being used and
select the link to be transferred to the page of resources for that
adapter.
Fibre Channel and FCoE out of kernel driver versions
and Celerra®
61
Installing and Configuring the Linux Host with the QLogic Driver
4. Find the desired and supported driver for the kernel version and
distribution, and click the associated Download link to save the
file.
Preinstallation instructions for the QLogic v7.xx.xx/v8.xx.xx driver
Perform the following steps prior to the installation:
1. Stop all I/O.
2. Unmount all filesystems attached to the QLogic driver.
3. If the Naviagent/CLI is installed and enabled on the host, then
the Naviagent/CLI service must be stopped.
To stop the Naviagent/CLI service, issue one of the two following
commands:
/etc/init.d/naviagentcli stop
or
service naviagentcli stop
4. If PowerPath is installed and enabled on the host, then the
PowerPath service must be stopped.
62
To stop the PowerPath service, issue one of the two following
commands:
/
etc/init.d/PowerPath stop
or
service PowerPath stop
5. If the QLogic SANsurfer daemon qlremote is installed and
enabled on the host, then the qlremote service must be stopped in
order for the driver to be removed from the currently running
kernel.
To stop the qlremote service, issue one of the two following
commands:
/etc/init.d/qlremote stop
or
service qlremote stop
What next?Select a method to install the driver onto the Linux host:
For the QLogic v7.xx.xx/v8.xx.xx driver:
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
◆To create a modular v7.xx.xx/v8.xx.xx driver using the DKMS
RPM, refer to “Method 1: Installing the QLogic v7.xx.xx/v8.xx.xx
driver via the QLogic DKMS RPM” on page 63.
Use the QLogic DKMS RPM to compile and install the modular
driver for Dell servers and attached to EMC storage arrays.
This method requires no manual edits for Dell servers attached to
EMC storage arrays. By installing the DKMS RPM, the necessary
files will be edited and the driver will be compiled and installed
automatically.
◆To create a modular v7.xx.xx/v8.xx.xx driver using the
installation script, refer to “Method 2: Installing the QLogic
v7.xx.xx/v8.xx.xx driver via the QLogic installation script” on
page 65.
Use the QLogic installation script to compile and install the
modular driver onto the systems attached to EMC storage arrays.
This method requires no manual edits for systems attached to
EMC storage arrays. By using the QLogic installation script, the
necessary files are edited and the driver is compiled and installed
automatically.
◆To create a modular v7.xx.xx driver using the QLogic RMP, refer
to“Method 3: Installing the QLogic v7.xx.xx driver via the
QLogic RPM” on page 75.
Use the QLogic RPM to compile and install the modular driver.
This method requires no manual edits for systems attached to
EMC storage arrays. By installing the QLogic RPM, the necessary
files will be edited and the driver will be compiled and installed
automatically.
Method 1: Installing the QLogic v7.xx.xx/v8.xx.xx driver via the QLogic DKMS RPM
This section guides you through the process of installing and utilizing
the DKMS RPM for Dell servers. The DKMS RPM will build and
install the QLogic driver modules and will modify the
/
etc/modprobe.conf file with the entries similar to the following:
options qla2xxx ql2xfailover=0
alias scsi_hostadapter2 qla2100
alias scsi_hostadapter3 qla2200
alias scsi_hostadapter4 qla2300
alias scsi_hostadapter5 qla2322
alias scsi_hostadapter6 qla6312
Fibre Channel and FCoE out of kernel driver versions
63
Installing and Configuring the Linux Host with the QLogic Driver
The following are example steps to integrate the QLogic driver. Also
refer to the README file in the driver package.
1. Boot into the qualified and supported kernel onto which the
driver will be installed.
2. Obtain the qla2xxx-v8.xx.xx1-2dkms.tgz package from the
EMC-approved section of the QLogic website as instructed under
the “Downloading the QLogic v7.x/v8.x-series driver for the
v2.4/v2.6.x kernel” on page 61.
3. Uncompress and extract the source files from the tar archive:
[root@l82bi205 extra]# tar zxvf qla2xxx-v8.xx.xx-2dkms.tar.gz
The initial decompression will provide you with the following:
->/usr/src/qla2xxx-v8.xx.xx
DKMS: add Completed.
Loading/Installing pre-built modules for 2.6.9-5.EL (x86_64).
A new ramdisk will be created automatically by the DKMS RPM
installation.
6. Reboot the host.
64
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Method 2: Installing the QLogic v7.xx.xx/v8.xx.xx driver via the QLogic installation script
This section guides you through the process of installing and utilizing
the QLogic installation script The script will build and install the
driver and will modify the
/etc/sysconfig/kernel files on SLES hosts.
Note: By default, the installation script will install the QLogic adapter SNIA
API libraries and the SANsurfer CLI.
/etc/modprobe.conf.local and
The following are example steps to install the QLogic driver via the
installation script. Also refer to the README file in the driver
package.
1. Boot into the qualified and supported kernel onto which the
driver will be installed.
2. Obtain the
qlafc-linux-8.xx.xx-1-install.tgz package from
EMC-approved section of the QLogic website as instructed under
the “Downloading the QLogic v7.x/v8.x-series driver for the
v2.4/v2.6.x kernel” on page 61.
3. Uncompress and extract the source files from the tar archive:
4. Install the QLogic driver via the installation script provided.
When using the -i switch, the driver will be compiled, the current
driver will be unloaded, and the newly compiled driver will be
loaded into the kernel.
Note: EMC does not support the persistent binding implementation
contained within the QLogic driver. As a result, it is recommended that
the driver be compiled and installed without persistent binding enabled.
This can be accomplished by using the 'dp' switch with the installation
script.
Fibre Channel and FCoE out of kernel driver versions
65
Installing and Configuring the Linux Host with the QLogic Driver
Proceed with the installation.
cd qlafc-linux-8.xx.xx-1-install/./qlinstall -i -dp
The qlinstall installation script provides the following features:
◆Installs the driver source RPM which installs the driver source
code in the following path:
/usr/src/qlogic/<driver_version-rpm_release>
◆Builds and installs the QLogic driver and configuration module
(
qla2xxx_conf.o) for the QLogic adapter model(s) installed in
the system.
◆Creates back-ups of important files and older drivers in the
◆Automatically loads the driver for the adapter model present.
◆Builds and installs the ramdisk with the latest driver and
configuration modules.
◆Installs the QLogic SNIA API Library V2.
66
◆Performs device discovery by default.
◆Provides the following command line options:
• To invoke the device discovery at a later stage.
• To rebuild the ramdisk excluding or including QLogic adapter
driver.
• To unload/load driver.
• To update the option ROM (BIOS, and so forth) on all
adapters.
• To update the NVRAM on all adapters.
• To pass driver parameters. For example:
ql_port_down_retry
(Overrides NVRAM default)
• To invoke the SANsurfer CLI (SCLI).
The SANsurfer CLI (SCLI) is a command line interface that provides
more flexibility for performing adapter configuration, device
discovery, Option ROM and NVRAM updates, etc.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
RHEL examplesAn example of the console output reported by the QLogic installation
Configuration saved on HBA port 0. Changes have been saved to
persistent storage.
Please reload the QLA driver module/rebuild the RAM disk for
Fibre Channel and FCoE out of kernel driver versions
67
Installing and Configuring the Linux Host with the QLogic Driver
the saved configuration to take effect.
Configuration saved on HBA port 1. Changes have been saved to
persistent storage.
Please reload the QLA driver module/rebuild the RAM disk for
the saved configuration to take effect.
Saved copy of /etc/modprobe.conf as
/usr/src/QLogic/v8.00.03-3/backup/modprobe.conf-2.6.9-5.EL-050505-161350.bak
Saved copy of /boot/efi/efi/redhat/initrd-2.6.9-5.EL.img as
/usr/src/QLogic/v8.00.03-3/backup/initrd-2.6.9-5.EL.img-050505-161350.bak
Target Information on all HBAs:
==============================
----------------------------------------------------------------------------HBA Port 0 - QLA2342 Port Name: 21-00-00-E0-8B-19-9A-54 Port ID: 6B-0F-00
----------------------------------------------------------------------------Path : 0
Target : 0
Device ID : 0x81
Port ID : 49-1B-00
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-60-10-60-12-70
Product Type : Disk
Number of LUN(s) : 26
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 1
Device ID : 0x82
Port ID : 48-1B-00
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-68-10-60-12-70
68
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Product Type : Disk
Number of LUN(s) : 26
Status : Online
----------------------------------------------------------------------------HBA Port 1 - QLA2342 Port Name: 21-01-00-E0-8B-39-9A-54 Port ID: 6B-0E-00
----------------------------------------------------------------------------Path : 0
Target : 0
Device ID : 0x81
Port ID : 49-1B-00
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-60-10-60-12-70
Product Type : Disk
Number of LUN(s) : 26
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 1
Device ID : 0x82
Port ID : 48-1B-00
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-68-10-60-12-70
Product Type : Disk
Number of LUN(s) : 26
Status : Online
Configuration saved. Changes have been saved to persistent storage.
Please reload the QLA driver module/rebuild the RAM disk for the
saved configuration to take effect.
Configuration saved. Changes have been saved to persistent storage.
Please reload the QLA driver module/rebuild the RAM disk
for the saved configuration to take effect.
70
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Saved copy of /etc/sysconfig/kernel as
/usr/src/qlogic/v8.00.03-1/backup/kernel-2.6.5-7.151-smp-042905-124100.bak
Saved copy of /etc/modprobe.conf.local as
/usr/src/qlogic/v8.00.03-1/backup/modprobe.conf-2.6.5-7.151-smp-042905-124100.ba
k
Saved copy of /boot/initrd-2.6.5-7.151-smp as
/usr/src/qlogic/v8.00.03-1/backup/initrd-2.6.5-7.151-smp-042905-124100.bak
Target Information on all HBAs:
==============================
----------------------------------------------------------------------------HBA Port 1 - QLA2340 Port Name: 21-00-00-E0-8B-13-C0-1E Port ID: 6A-1A-13
----------------------------------------------------------------------------Path : 0
Target : 0
Device ID : 0x81
Port ID : 6A-2E-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0206
Node Name : 50-06-01-60-90-60-12-5C
Port Name : 50-06-01-6A-10-60-12-5C
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 1
Device ID : 0x82
Port ID : 6C-1B-13
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-62-10-60-12-70
Product Type : Disk
Number of LUN(s) : 14
Fibre Channel and FCoE out of kernel driver versions
71
Installing and Configuring the Linux Host with the QLogic Driver
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 2
Device ID : 0x83
Port ID : 61-1A-13
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-6A-10-60-12-70
Product Type : Disk
Number of LUN(s) : 14
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 3
Device ID : 0x84
Port ID : 74-4A-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0206
Node Name : 50-06-01-60-90-60-12-5C
Port Name : 50-06-01-62-10-60-12-5C
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 4
Device ID : 0x85
Port ID : 74-55-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0217
Node Name : 50-06-01-60-88-20-12-BB
Port Name : 50-06-01-60-08-20-12-BB
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 5
Device ID : 0x86
Port ID : 6A-3A-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0217
Node Name : 50-06-01-60-88-20-12-BB
Port Name : 50-06-01-68-08-20-12-BB
Product Type : Disk
Number of LUN(s) : 1
72
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
----------------------------------------------------------------------------HBA Port 0 - QLA2340 Port Name: 21-00-00-E0-8B-13-77-20 Port ID: 74-3B-13
----------------------------------------------------------------------------Path : 0
Target : 0
Device ID : 0x81
Port ID : 61-1A-13
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Port Name : 50-06-01-6A-10-60-12-70
Product Type : Disk
Number of LUN(s) : 14
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 1
Device ID : 0x82
Port ID : 6A-2E-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0206
Node Name : 50-06-01-60-90-60-12-5C
Port Name : 50-06-01-6A-10-60-12-5C
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 2
Device ID : 0x83
Port ID : 6A-3A-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0217
Node Name : 50-06-01-60-88-20-12-BB
Port Name : 50-06-01-68-08-20-12-BB
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 3
Device ID : 0x84
Port ID : 6C-1B-13
Product Vendor : DGC
Product ID : RAID 3
Product Revision : 0207
Node Name : 50-06-01-60-90-60-12-70
Fibre Channel and FCoE out of kernel driver versions
73
Installing and Configuring the Linux Host with the QLogic Driver
Port Name : 50-06-01-62-10-60-12-70
Product Type : Disk
Number of LUN(s) : 14
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 4
Device ID : 0x00
Port ID : 74-4A-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0206
Node Name : 50-06-01-60-90-60-12-5C
Port Name : 50-06-01-62-10-60-12-5C
Product Type : Disk
Number of LUN(s) : 1
Status : Online
----------------------------------------------------------------------------Path : 0
Target : 5
Device ID : 0x85
Port ID : 74-55-13
Product Vendor : DGC
Product ID : LUNZ
Product Revision : 0217
Node Name : 50-06-01-60-88-20-12-BB
Port Name : 50-06-01-60-08-20-12-BB
Product Type : Disk
Number of LUN(s) : 1
Status : Online
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Method 3: Installing the QLogic v7.xx.xx driver via the QLogic RPM
This section guides you through the process of installing and utilizing
the QLogic driver RPM. The RPM builds and installs the qla2300.o
driver and modifies the
/etc/modules.conf file.
In /etc/modules.conf, the host adapter line for the qla2300.o driver
will be appended. The options line containing the addition of the
scsi_allow_ghost_devices and max_scsi_luns parameters will also be
appended to the file. This allows the host to correctly identify the
disconnected LUN 0 that is reported when attached to VNX series or
CLARiiON storage systems, and allows the SCSI stack to scan up to
255 devices.
The Unisphere
™
/Navisphere® Host Agent requires that the
disconnected LUN 0 be reported.
The QLogic RPM creates the QLogic v7.xx.xx driver as a module.
The following is an example of steps to install the QLogic driver RPM
along with example console output:
1. Boot into the qualified and supported kernel onto which the
driver will be installed.
2. Obtain the qla2x00-v7.03.00-1.i686.rpm package from
EMC-approved section of the QLogic website.
QLogic qla2300/qla2200 HBA driver installation supports the following distribution
and its different flavors :
Red Hat Advanced Server 2.1 / Red Hat Enterprise Linux 3.0 and SuSE SLES 8.
Please refer to SUPPORTED_KERNEL_VERSION.txt file in
/usr/src/qla2x00 path for details regarding different arch and kernel versions
supported
Installing qla2300 driver for 2.4.21-32.0.1.ELsmp...
Creating initial /usr/src/qla2x00/install.v7.03.00-1.log...
Please wait: Preparing qla2300 modular driver build
copying kernel-2.4.21-i686-smp.config to
/lib/modules/2.4.21-32.0.1.ELsmp/build/.config...
Building Kernel Dependencies
Make successful. File
/usr/src/qla2x00/make.2.4.21-32.0.1.ELsmp.v7.03.00-1.log created.
Saving copy of /etc/modules.conf as /etc/modules.conf.orig
install -d -o root -g root
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/
install -o root -g root qla2200.o qla2300.o
Fibre Channel and FCoE out of kernel driver versions
75
Installing and Configuring the Linux Host with the QLogic Driver
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/
install -o root -g root qla2200_conf.o
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/
install -o root -g root qla2300_conf.o
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/
depmod -a
make: Nothing to be done for
`/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/'.
depmod...
adding line: alias scsi_hostadapter2 qla2300_conf to /etc/modules.conf
adding line: alias scsi_hostadapter3 qla2300 to /etc/modules.conf
mkinitrd...
Installation of qla2300/qla2200 driver for 2.4.21-32.0.1.ELsmp
complete.
Ex: To load the qla2300 driver execute the following command:
# modprobe -v qla2300
Or Reboot the system for newly build ramdisk to load
qla2300 driver automatically for you
Installing the QLogic SNIA API library libqlsdm.so
in /usr/lib. API package is installed in the
/usr/src/qla2x00/ApiPkg path
Setting up QLogic HBA API library...
Please make sure the /usr/lib/libqlsdm.so file is not in use.
Done.
Example of the modified /etc/modules.conf:
[root@l82bi114 extra]# more /etc/modules.conf
alias eth0 e1000
alias eth1 e100
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsih
alias usb-controller usb-uhci
options scsi_mod max_scsi_luns=255 scsi_allow_ghost_devices=1
post-remove qla2200 rmmod qla2200_conf
post-remove qla2300 rmmod qla2300_conf
alias scsi_hostadapter2 qla2300_conf
alias scsi_hostadapter3 qla2300Installing and Configuring the QLogic HBA and the s
A new ramdisk is created automatically by the RPM installation.
4. Reboot the host.
Uninstallation methods for the QLogic v7.xx.xx/v8.xx.xx driver
This section describes how to successfully uninstall the QLogic
v7.xx.xx/v8.xx.xx driver from a Linux host.
The method used to uninstall the driver is dependent upon the
installation package:
◆“Method 1: Uninstalling the QLogicv7.xx.xx/v8.xx.xx driver via
QLogic DKMS RPM” on page 77
76
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
◆“Method 2: Uninstalling the QLogic v7.xx.xx/v8.xx.xx driver via
the QLogic installation script” on page 77
◆“Method 3: Uninstalling the QLogic v7.xx.xx driver via the
QLogic RPM” on page 78
Method 1: Uninstalling the QLogicv7.xx.xx/v8.xx.xx driver via QLogic DKMS RPM
This section provides guidance for uninstalling the QLogic
v7.xx.xx/v8.xx.xx driver via the QLogic DKMS RPM package. The
driver may be removed from the system with the 'e' switch for the
RPM command.
The following are example steps to uninstall the QLogic driver. Also
refer to the README file in the driver package.
1. Verify the driver names by querying the DKMS RPMs.
An example of the console output reported by the driver RPM
removal is as follows:
3. Verify that the
/etc/modprobe.conf.local files contain the information
/etc/modprobe.conf and
necessary for the server to boot and that a new ramdisk has been
created.
4. Reboot the host.
Method 2: Uninstalling the QLogic v7.xx.xx/v8.xx.xx driver via the QLogic installation script
This section provides guidance for uninstalling the QLogic
v7.xx.xx/v8.xx.xx driver via the QLogic installation script. The driver
may be removed from the system with the '
qlinstall script.
u' switch for the
The following are example steps to uninstall the QLogic driver. Also
refer to the README file in the driver package
1. Change to the directory where the installation script is located.
[root@l82bi116 /]# cd /qlafc-linux-8.xx.xx-install
2. Uninstall the QLogic driver with the following command:
Fibre Channel and FCoE out of kernel driver versions
77
Installing and Configuring the Linux Host with the QLogic Driver
An example of the console output reported by the driver removal
is as follows:
3. Verify that the
/etc/modprobe.conf file contains the information
necessary for the server to boot and that a new ramdisk has been
created. If the ramdisk has not been created as in the example
above, create one.
cd /boot
mkinitrd -v initrd-$1.img
$1
where $1 is the currently running v2.6.x kernel version.
Example:
cd /boot
mkinitrd -v initrd-2.6.9-11.ELsmp.img 2.6.9-11.ELsmp
4. Reboot the host.
Method 3: Uninstalling the QLogic v7.xx.xx driver via the QLogic RPM
This section provides guidance for uninstalling the QLogic v7.xx.xx
driver RPM. The QLogic RPM may be used to remove the driver with
the e switch for the RPM command.
3. Verify that the /etc/modules.conf file contains the information
necessary for the server to boot and that a new ramdisk has been
created. If the ramdisk has not been created, create one:
cd /boot
mkinitrd -v initrd-
$1
.img
$1
where $1 is the v2.4.x kernel version currently running.
Example:
cd /boot
mkinitrd -v initrd-2.4.21-27.0.4.ELsmp.img 2.4.21-27.0.4.ELsmp
78
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
4. Reboot the host.
QLogic v7.x and v8.x series driver parameters
The QLogic driver contains a number of parameters that may be
modified to perform failover functionality or to enhance
performance.
QLogic v7.x series driver parameters
The QLogic and EMC recommended values are in Tab l e 6 and
descriptions of the parameters follow the table.
The values to which these parameters are set are dependent upon the
environment and the type of applications and subsequent I/O being
used on the system. Currently, the values in the EMC default
recommendations column apply to both PowerPath and non-HA
connections. Keep in mind that these are merely guidelines as each
environment differs.
Note: EMC does not support the failover functionality within the QLogic
driver. As a result, parameters related to the failover functionality are not
used by EMC.
The changes to the parameters do not take effect until the driver is
reloaded or the host is rebooted.
Note: 0 = disabled; 1 = enabled
Tab le 6QLogic v7.x series driver parameters (page 1 of 3)
Description of QLogic v7.x-series driver parameters
When attaching to VNX series, CLARiiON, or Symmetrix storage
systems, EMC recommends that the
ql2xfailover parameters be set to zero.
ConfigRequired and
General driver
parameters
◆ql2xopts: string that defines additional driver options and
persistent binding info.
◆ql2xfailover: determines whether the failover functionality is
disabled or enabled.
Note: EMC does not support the failover functionality of the QLogic
driver.
◆ql2xmaxqdepth: defines the maximum queue depth reported to
the SCSI mid-layer per device and specifies the number of
outstanding requests per LUN.
◆ql2xmaxsectors: defines the maximum number of sectors
reported to the SCSI mid-layer per request for the adapter.
◆q2xmaxsgs: defines the maximum number of scatter-gather
entries reported to the SCSI mid-layer per request for the adapter.
◆ql2xlogintimeout: defines the login timeout value in seconds,
during the initial login.
◆qlport_down_retry: defines the maximum number of command
retries to a port that returns a PORT DOWN status.
◆ql2xretrycount: defines the maximum number of SCSI
mid-layer retries allowed per command.
◆max_srbs: defines the maximum number of simultaneous
commands allowed for an adapter.
◆displayConfig: defines whether to display the current driver
configuration. If 1, then the configuration used in
/etc/modules.conf is displayed.
Fibre Channel and FCoE out of kernel driver versions
81
Installing and Configuring the Linux Host with the QLogic Driver
◆ql2xintrdelaytimer: defines the amount of time for the
firmware to wait before generating an interrupt to the host as
notification of the request completion.
◆retry_gnnft: defines the number of times to retry GNN_FT in
order to obtain the Node Name and PortID of the device list.
◆ConfigRequired: If set to 1, then only devices configured and
passed through the
◆Bind: defines the method for target persistent binding method. If
set to 0, then the Portname is used; if set to 1, the PortID is used.
◆ql2xsuspendcount: defines the number of 6-second suspend
iterations to perform while a target returns a
◆ql2xdevflag: defines whether to display the abbreviated
persistent binding statements.
◆qfull_retry_count: defines the number of retries to perform on
a queue full status from a device.
◆qfull_retry_delay: defines the number of seconds to delay on
queue full status from a device.
◆extended_error_logging: defines whether to enable extended
error logging.
ql2xopts parameter are presented to the OS.
NOT_READY status.
82
◆ql2xplogiabsentdevice: defines whether to enable a PLOGI to
devices that are not present after a fabric scan. Per QLogic, this is
needed for several broken switches.
◆ql2xfdmienable: defines whether FDMI registration is enabled.
◆qlogin_retry_count: defines whether the login retry count will
be modified.
◆ql2xioctltimeout: defines the IOCTL timeout value in seconds
for pass-through commands.
◆ql2xprocessnotready: defines whether the driver handles
NOT_READYs.
◆ql2xuseextopts: defines whether the driver will use the
extended options saved in the module object itself, even if a string
Failover-specific
parameters
is defined via
◆MaxPathsPerDevice: defines the maximum number of paths to a
device.
◆MaxRetriesPerPath: defines the number of retries to perform on
ql2xopts.
the current path before failing over to the next path in the list.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
◆MaxRetriesPerIo: defines the total number of retries to perform
before failing the command and returning a
DID_NO_CONNECT
selection timeout to the OS.
◆qlFailoverNotifyType: defines the type of failover notification
mechanism to use when a failover or failback occurs.
◆recoveryTime: defines the recovery time in seconds required
before commands may be sent to a target device after a failback is
performed.
◆failbackTime: defines the delay in seconds before a failback is
performed to ensure that all paths are available.
Setting the parameter
values
The values of the general driver parameters may be modified at the
driver load time. This modification may be performed at the command line or by adding the parameters to the
/etc/modules.conf
file and including them in the ramdisk.
When attaching to VNX series, CLARiiON, and Symmetrix storage systems,
EMC recommends that the ConfigRequired and ql2xfailover
parameters be set to zero in the /etc/modules.conf file.
1. To load the QLogic driver onto the system with the parameters at
the command line, use:
modprobe qla2300.o extended_error_logging=1
In order for the modular driver to be loaded at boot time with
these parameters set to 0, a separate options line needs to be
added to the
/etc/modules.conf file.
2. Edit the file:
vi /etc/modules.conf
3. Add the options line for the appropriate driver settings.
options qla2300 extended_error_logging=1
Example:
alias parport_lowlevel parport_pc
alias eth0 eepro100
alias scsi_hostadapter cpqarray
alias scsi_hostadapter1 cpqarray
alias scsi_hostadapter2 qla2300
alias scsi_hostadapter3 qla2300
options scsi_mod max_scsi_luns=255 scsi_allow_ghost_devices=1
options qla2300 extended_error_logging=1
Fibre Channel and FCoE out of kernel driver versions
83
Installing and Configuring the Linux Host with the QLogic Driver
IMPORTANT
!
4. After the modification to /etc/modules.conf has been made, a
new ramdisk needs to be created and the host rebooted.
To create a new ramdisk, type the
• For Red Hat, type:
cd /boot
mkinitrd –v initrd-
where $1 is the v2.4.x kernel version currently running.
Example:
cd /boot
• For SuSE, type:
cd /boot
mkinitrd –i initrd-
where $1 is the v2.4.x kernel version currently running.
Example:
cd /boot
mkinitrd -i initrd-2.4.21-286-smp -k vmlinuz-2.4.21-286-smp
5. Reboot the host.
QLogic v8.x-series driver parameters
The QLogic driver contains a number of parameters that may be
modified, such as debug.
mkinitrd command:
$1
.img
$1
$1
-k vmlinuz-
$1
EMC does not recommend changing these parameters and defaults
should be left as is.
Setting the parameter values
The values of the general driver parameters may be modified at the
driver load time. This modification may be performed at the
command line or by adding the parameters to the
/etc/modprobe.conf file on RHEL 4.0 hosts and the
/etc/modprobe.conf.local file on SLES 9 hosts and including them
in the ramdisk.
84
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Note: When attaching to VNX series, CLARiiON, or Symmetrix storage
arrays, EMC recommends that the ConfigRequired and ql2xfailover
parameters be set to zero in the /etc/modules.conf file.
◆To load the QLogic driver onto the system with the parameters at
the command line, use:
modprobe qla2300 extended_error_logging=1
◆In order for the modular driver to be loaded at boot time with
these parameters set to 0, a separate options line needs to be
added to the
/etc/modprobe.conf.local file on SLES 9 hosts.
/etc/modprobe.conf file on RHEL 4.0 hosts and the
1. Edit the file appropriate for the distribution being used.
• For Red Hat distributions, edit:
vi /etc/modprobe.conf
• For SuSE distributions, edit:
vi /etc/modprobe.conf.local
2. Add the options line for the appropriate driver settings.
options qla2xxx extended_error_logging=1
For example, the /etc/modprobe.conf file on RHEL 4.0 might
look as follows:
alias eth0 tg3
alias eth1 tg3
alias scsi_hostadapter megaraid_mbox
alias scsi_hostadapter2 qla2xxx
alias scsi_hostadapter3 qla2xxx_conf
alias scsi_hostadapter4 qla2300
options qla2xxx extended_error_logging=1
And the /etc/modprobe.conf.local file on SLES 9 might look
as follows:
options qla2xxx extended_error_logging=1
3. After the modification to the file appropriate for your
distribution, a new ramdisk needs to be created and the host
rebooted.
• For Red Hat distributions, use:
cd /boot
mkinitrd -v initrd-
Fibre Channel and FCoE out of kernel driver versions
$1
.img
$1
85
Installing and Configuring the Linux Host with the QLogic Driver
where $1 is the currently running v2.6.x kernel version.
Example:
cd /boot
mkinitrd -v initrd-2.6.9-22.ELsmp.img
2.6.9-22.ELsmp
• For SuSE distributions, use:
cd /boot
mkinitrd -i initrd-$1 -k vmlinuz-$1
where $1 is the currently running v2.6.x kernel version.
Example:
cd /boot
mkinitrd -i initrd-2.6.5-7.201smp -k
vmlinuz-2.6.5-7.201smp
4. Reboot the host.
Displaying the QLogic v8.x-series driver parameter information via modinfo
The QLogic v8.x-series driver parameters and their definitions may
be viewed by using the
modinfo command. This command may be
used on any Linux kernel module.
Note: EMC does not support the failover functionality of the QLogic driver.
The modinfo command may be run on the qla2300, qla2xxx_conf,
and
qla2xxx modules. However, the parameter information is
reported only by the
qla2xxx module.
An example of the console output displayed when
the
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
modinfo is run on
Installing and Configuring the Linux Host with the QLogic Driver
An example of the console output displayed when modinfo is run on
the
qla2xxx module is as follows:
[root@l82bi205 ~]# modinfo qla2xxx
filename:
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/scsi/qla2xxx/qla2xxx.ko
version: 8.01.06
license: GPL
description: QLogic Fibre Channel HBA Driver
author: QLogic Corporation
parm: ql2xfdmienable:Enables FDMI registratons Default is 0 - no FDMI.
1 - perfom FDMI.
parm: ql2xfwloadbin:Option to enable loading of ISP24xx firmware via the
request_firmware() (hotplug) interface. If enabled, a file, ql2400_fw.bin,
(containing the firmware image) should be hotplug accessible.
parm: extended_error_logging:Option to enable extended error logging,
Default is 0 - no logging. 1 - log errors.
parm: ql2xioctltimeout:IOCTL timeout value in seconds for pass-thur
commands. Default is 66 seconds.
parm: ql2xprocessrscn:Option to enable port RSCN handling via a series
of lessfabric intrusive ADISCs and PLOGIs.
parm: ql2xprocessnotready:Option to disable handling of NOT-READY in the
driver. Default is 1 - Handled by the driver. Set to 0 - Disable the handling
inside the driver
parm: ql2xloginretrycount:Specify an alternate value for the NVRAM login
retry count.
parm: ql2xdoinitscan:Signal mid-layer to perform scan after driver load:
0 -- no signal sent to mid-layer.
parm: ql2xsuspendcount:Number of 6-second suspend iterations to perform
while a target returns a <NOT READY> status. Default is 10 iterations.
parm: Bind:Target persistent binding method: 0 by Portname (default); 1
by PortID; 2 by Nodename.
parm: ConfigRequired:If 1, then only configured devices passed in through
theql2xopts parameter will be presented to the OS
parm: ql2xintrdelaytimer:ZIO: Waiting time for Firmware before it
generates an interrupt to the host to notify completion of request.
parm: ql2xenablezio:Option to enable ZIO:If 1 then enable it otherwise
use the default set in the NVRAM. Default is 0 : disabled
parm: ql2xplogiabsentdevice:Option to enable PLOGI to devices that are
not present after a Fabric scan. This is needed for several broken
switches.Default is 0 - no PLOGI. 1 - perfom PLOGI.
parm: displayConfig:If 1 then display the configuration used in
/etc/modprobe.conf.
parm: ql2xretrycount:Maximum number of mid-layer retries allowed for a
command. Default value is 20,
parm: qlport_down_retry:Maximum number of command retries to a port that
returnsa PORT-DOWN status.
parm: ql2xlogintimeout:Login timeout value in seconds.
parm: ql2xmaxqdepth:Maximum queue depth to report for target devices.
parm: ql2xtgtemul:Enable/Disable target combining emulation.Default : 1
Enable target failover emulation for targets created by lunid matching : 0
Disable target failover emulation
Fibre Channel and FCoE out of kernel driver versions
87
Installing and Configuring the Linux Host with the QLogic Driver
parm: ql2xexcludemodel:Exclude device models from being marked as failover
capable.Combine one or more of the following model numbers into an exclusion mask:
0x20 - HSV210, 0x10 - DSXXX, 0x04 - HSV110, 0x02 - MSA1000, 0x01 - XP128.
parm: ql2xlbType:Load Balance Method : (0) None (1) static load balance
and Default : 0 All the luns exposed on the first active path : 1 For
static load balance across active optimised controller ports
parm: qlFailoverNotifyType:Failover notification mechanism to use when
a failover or failback occurs.
parm: MaxRetriesPerIo:How many total retries to do before failing the
command and returning to the OS with a DID_NO_CONNECT status.
parm: MaxRetriesPerPath:How many retries to perform on the current path
before failing over to the next path in the path list.
parm: MaxPathsPerDevice:Maximum number of paths to a device. Default 8.
parm: failbackTime:Delay in seconds before a failback is performed.
parm: recoveryTime:Recovery time in seconds before a target device is
sent I/O after a failback is performed.
parm: ql2xfailover:Driver failover support: 0 to disable; 1 to enable.
alias: pci:v00001077d00002432sv*sd*bc*sc*i*
alias: pci:v00001077d00002422sv*sd*bc*sc*i*
depends: scsi_mod
vermagic: 2.6.9-22.ELsmp SMP gcc-3.4
88
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
iSCSI in kernel driver versions
The following installation information is contained in this section:
◆“iSCSI supported in kernel driver versions” on page 89
◆“Installation instructions for the in kernel QLogic driver in Linux
2.6.x kernels” on page 91
iSCSI supported in kernel driver versions
Ta bl e 7 lists some examples of supported operating systems in kernel
driver versions.
Tab le 7Supported iSCSI in kernel driver versions (page 1 of 2)
OSDriver version
SLES 9 SP35.00.04
SLES 10 GA5.00.04-d5
Installing and Configuring the Linux Host with the QLogic Driver
RHEL 4.5
OEL 4.5
SLES 10 SP15.01.00-d7
RHEL 4.6
OEL 4.6
RHEL 4.7
Asianux 2.0 SP3
OEL 4.7
RHEL 4.8
Asianux 2.0 SP4
OEL 4.8
RHEL 5.1
Asianux 3.0 SP1
OEL 5.1
RHEL 5.2
OEL 5.2
5.00.04-d4
5.01.01.04
5.01.03-d0-RHEL4.7-02
5.01.03.00.04.08-d
5.01.00-k8_rhel5
5.01.00-k8_rhel5.1-01
iSCSI in kernel driver versions
89
Installing and Configuring the Linux Host with the QLogic Driver
Tab le 7Supported iSCSI in kernel driver versions (page 2 of 2)
OSDriver version
RHEL 5.3
Asianux 3.0 SP2
OEL 5.3
SLES 11 GA5.01.00-k8_sles11-04
SLES 11 GA (errata kernels equal to
or greater than 2.6.27.23-0.1.1)
SLES 11 SP15.01.00.00.11.01-k14
RHEL 5.4
OEL 5.4
RHEL 5.5
OEL 5.5
AX3 SP3
SLES 10 SP3 (kernel errata
2.6.16.60-0.57.1 and greater but less
than 2.6.16.60-0.67.1)
SLES 10 SP3 (kernel errata
2.6.16.60-0.67.1 and greater)
RHEL 5.65.02.04.02.05.06-d0
RHEL 5.7 5.02.04.01.05.07-d0
RHEL 6.05.02.00-k1
5.01.00.01.05.03-k9
5.01.00-k9_sles11-04
5.01.00.01.05.04-k9
5.01.03.03.10.3-d5
5.01.03.03.10.3-d6
90
SLES 10 SP45.02.06.00.10.4-d0
RHEL 6.15.02.00-k5
RHEL 6.25.02.00.00.06.02-k10
What next?If the driver version is listed in Tab le 7 , refer to the appropriate
section in “Installation instructions for the in kernel QLogic driver in
Linux 2.6.x kernels” on page 91.
If the driver version is not listed in Ta bl e 7, refer to “iSCSI out of
kernel driver versions” on page 95.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
Installation instructions for the in kernel QLogic driver in Linux 2.6.x kernels
CAUTIONThe qla3xxx driver which is used by the QLogic iSCSI HBA to
perform TCP/IP traffic will automatically be enabled along with
the qla4xxx driver. If the qla3xxx driver is activated, it will take over
the HBA, no iSCSI traffic may be conducted through the HBA, and
the server will appear to hang on boot. This is a known issue (Red
Hat Bugzilla #249556).
In order for the qla4xxx driver to function properly, the qla3xxx
driver must be removed or renamed and the initrd image rebuilt
without it.
After moving or removing the qla3xxx.ko driver, go to the
instructions in one of the following sections listed as appropriate for
your installation:
◆If you are installing the OS after the adapter has been installed in
the server, the OS will automatically detect the adapter, change
the configuration file, and build a RAM disk including the driver.
Even though this has been accomplished you will still need to
rebuild the initrd image to remove the qla3xxx driver from the
existing initrd that was built during the installation of the
operating system. Please refer to one of the following sections for
instruction on how to rebuild the initrd image:
• “Enabling the QLogic driver in RHEL 4” on page 92
• “Enabling the QLogic driver in RHEL 5” on page 92
• “Enabling the QLogic driver in SLES 9” on page 93
• “Enabling the QLogic driver in SLES10 and SLES 11” on
page 94
◆If you have completed a fresh installation of the OS without the
adapter and plan to install it at a later time, or are installing an
adapter in a server with an existing OS installed, refer to the
following sections to enable this driver:
• “Enabling the QLogic driver in RHEL 4” on page 92
• “Enabling the QLogic driver in RHEL 5” on page 92
• “Enabling the QLogic driver in SLES 9” on page 93
iSCSI in kernel driver versions
91
Installing and Configuring the Linux Host with the QLogic Driver
• “Enabling the QLogic driver in SLES10 and SLES 11” on
page 94
Enabling the QLogic driver in RHEL 4
To enable this driver:
1. Ensure that the /etc/modprobe.conf file references an entry for
each installed QLogic adapter.
For each installed QLogic adapter, add an entry:
alias scsi_hostadapterN qla4xxx
where N is the sequential value of each QLogic adapter installed
in the system, beginning with the number after the last host
adapter number entry in the file. (The first host adapter entry
begins with zero.), qla4xxx is the driver name for the adapter
Example:
alias scsi_hostadapter3 qla4xxx
2. Whenever /etc/modprobe.conf is modified, a new ramdisk
should be created to reflect the changes made. Create a new
ramdisk image to include the newly added references to the
QLogic adapters:
3. Reboot the host.
Enabling the QLogic driver in RHEL 5
To enable this driver:
1. Ensure that the /etc/modprobe.conf file references an entry for
92
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
cd /boot
mkinitrd -v initrd-$1.img
$1
where $1 is the v2.6.x kernel version currently running.
Installing and Configuring the Linux Host with the QLogic Driver
where N is the sequential value of QLogic adapter installed in the
system, beginning with the number after the last host adapter
number entry in the file. (The first host adapter entry begins with
zero.).
Example:
alias scsi_hostadapter1 qla4xxx
2. Whenever /etc/modprobe.conf/ is modified, a new ramdisk
should be created to reflect the changes made. Create a new
ramdisk image to include the newly added references to the
QLogic adapters:
cd /boot
mkinitrd -v initrd-
where $1 is the v2.6.x kernel version currently running.
Example:
mkinitrd -v initrd- 2.6.18-8.el5.img 2.6.18-8.el5
3. Reboot the host.
Enabling the QLogic driver in SLES 9
In order for the driver to be loaded at boot time, the driver must be
listed in the /etc/sysconfig/kernel and the ramdisk must be updated
to reflect the changes. To enable the driver:
1. Edit /etc/sysconfig/kernel:
vi /etc/sysconfig/kernel
a. Add a reference to the QLogic driver in the
INITRD_MODULES line:
INITRD_MODULES="reiserfs qla4xxx"
b. Save the changes and quit from vi.
2. 2Create a new ramdisk to reflect the changes made:
cd /boot
mkinitrd -k vmlinuz-
$1
.img
$1
-i initrd-
$1
$1
where $1 is the v2.6.x kernel version currently running.
Example:
cd /boot
mkinitrd -k vmlinuz- 2.6.5-7.244-smp -i initrd- 2.6.5-7.244-smp
iSCSI in kernel driver versions
93
Installing and Configuring the Linux Host with the QLogic Driver
3. Reboot the system.
Enabling the QLogic driver in SLES10 and SLES 11
If the server install the OS without the adapter, in order for the driver
to be loaded at boot time, the driver must be listed in the
/etc/sysconfig/kernel and the ramdisk must be updated to reflect
the changes. To enable the driver:
1. Edit /etc/sysconfig/kernel:
vi /etc/sysconfig/kernel
a. Add a reference to the QLogic qla4xxx.ko driver in the
INITRD_MODULES line:
INITRD_MODULES="piix megaraid_sas processor thermal fan reiserfs qla4xxx"
b. Save the changes and quit from vi.
2. Create a new ramdisk to reflect the changes made:
cd /boot
mkinitrd -k vmlinuz-
$1
-i initrd-
$1
where $1 is the v2.6.x kernel version currently running.
94
Example:
cd /boot
mkinitrd -k vmlinuz- 2.6.16.21-0.8-smp -i initrd-
2.6.16.21-0.8-smp
3. Reboot the system.
What’s next?Proceed to “Configuring the QLA40xx-Series HBA to discover iSCSI
targets” on page 136.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
iSCSI out of kernel driver versions
The following installation information is contained in this section:
◆“iSCSI supported out of kernel driver versions” on page 95
◆“Installing the Linux v2.4.x host and the QLogic v3.x-Series iSCSI
HBA driver” on page 96
◆“Installing the Linux v2.6.x host and the QLogic v5.x-Series iSCSI
HBA driver” on page 107
iSCSI supported out of kernel driver versions
Ta bl e 8 lists some examples of supported operating systems in kernel
driver versions.
Tab le 8Supported iSCSI out of kernel driver versions
Installing and Configuring the Linux Host with the QLogic Driver
Tab le 8Supported iSCSI out of kernel driver versions
OSDriver version
RHEL 4.6
RHEL 5.0
SLES 11 SP1
RHEL 6.0
RHEL 6.1
SLES 10 SP45.02.11.00.10.4-d2
a. For models QLE8240, QLE8242, QLE8250, and QLE8252 only.
5.01.01.04
5.02.11.00.05.06-c3
Refer to the latest EMC Support Matrix for specific qualified kernel
versions and distributions.
Note: The support stated in the EMC Support Matrix supersedes versions
listed in this document.
Installation instructions for the out of kernel QLogic driver
This section contains the following information for installing the out
of kernel QLogic driver:
◆“Installing the Linux v2.4.x host and the QLogic v3.x-Series iSCSI
HBA driver” on page 96
◆“Installing the Linux v2.6.x host and the QLogic v5.x-Series iSCSI
HBA driver” on page 107
a
a
Installing the Linux v2.4.x host and the QLogic v3.x-Series iSCSI HBA driver
Using the QLogic iSCSI HBA with the Linux operating system
requires EMC-approved HBA driver software and SANsurfer
Management software. The driver functions at a layer below the
Linux SCSI driver to present iSCSI devices to the operating system as
if they were standard SCSI devices.
Note: Refer to the latest EMC Support Matrix for specific qualified kernel
versions and distributions. The support stated in the EMC Support Matrix
supersedes versions listed in this document.
96
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Preinstallation instructions
Installing and Configuring the Linux Host with the QLogic Driver
This section provides the following instructions for installing the
QLogic v3.x-Series iSCSI driver:
◆“Preinstallation instructions,” next
◆“Downloading the QLogic v3.x-Series iSCSI driver for the v2.4.x
kernel” on page 98
◆“Installing QLogic v3.x-Series iSCSI driver via the QLogic DKMS
RPM, Method one” on page 99
◆“Installing QLogic v3.x-Series iSCSI driver via the QLogic
installation script, Method two” on page 101
Prior to the installation:
◆Processes holding the driver open must be stopped so that the
currently-loaded driver may be removed from the running
kernel.
◆All I/O must be stopped.
◆All filesystems attached to the QLogic driver must be
unmounted.
◆If the Naviagent/CLI is installed and enabled on the host, then
the Naviagent/CLI service must be stopped.
To stop the Naviagent/CLI service, issue one of the two following
commands:
/etc/init.d/naviagentcli stop
service naviagentcli stop
◆If PowerPath is installed and enabled on the host, then the
PowerPath service must be stopped.
To stop the PowerPath service, issue one of the two following
commands:
/etc/init.d/PowerPath stop
service PowerPath stop
◆If the QLogic SANsurfer daemon iqlremote is installed and
enabled on the host, then the
iqlremote service must be stopped
in order for the driver to be removed from the currently running
kernel.
iSCSI out of kernel driver versions
97
Installing and Configuring the Linux Host with the QLogic Driver
To stop the iqlremote service, issue one of the two following
commands:
/etc/init.d/iqlremote stop
service iqlremote stop
Downloading the QLogic v3.x-Series iSCSI driver for the v2.4.x kernel
Use the following procedure to download the EMC-approved QLogic
iSCSI driver from the QLogic website:
1. Use a web browser to access the EMC-approved section of the
QLogic website at the following url:
http://www.qlogic.com
2. Select the appropriate link from the EMC-approved section of the
QLogic website:
3. After selecting a category, find the HBA model being used and
select the link to be transferred to the page of resources for that
HBA.
4. Find the desired and supported driver for the kernel version and
distribution, and click the associated Download link to save the
file.
98
The QLogic v3.x-series iSCSI driver can be installed onto a Linux
v2.4.x host using one of the two following methods:
◆Method One—Use the QLogic DKMS RPM to compile and install
the modular driver for Dell systems running RHEL 3.0 and
attached to EMC storage arrays.
This method requires no manual edits for Dell servers attached to
EMC storage arrays. By installing the QLogic DKMS RPM, the
necessary files will be edited and the driver will be compiled and
installed automatically.
Note: Refer to “Installing QLogic v3.x-Series iSCSI driver via the QLogic
DKMS RPM, Method one” on page 99.
◆Method Two—Use the QLogic installation script to compile and
install the modular driver for RHEL 3.0 and SLES 8 systems
attached to EMC storage arrays.
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
Installing and Configuring the Linux Host with the QLogic Driver
This method requires no manual edits for systems attached to
EMC storage arrays. By installing the QLogic RPM, the necessary
files will be edited and the driver will be compiled and installed
automatically.
Note: Refer to “Installing QLogic v3.x-Series iSCSI driver via the QLogic
installation script, Method two” on page 101.
Installing QLogic v3.x-Series iSCSI driver via the QLogic DKMS RPM, Method one
This section guides you through the process of installing and utilizing
the DKMS RPM on RHEL 3.0 Dell systems. The DKMS RPM will
build and install the
/etc/modules.conf file.
In the
/etc/modules.conf file, the hostadapter line for the qla4010
driver will be appended. The
the
scsi_allow_ghost_devices and max_scsi_luns parameters
qla4010.o driver and will modify the
options line containing the addition of
will also be appended to the file. This will allow the host to correctly
identify-the disconnected LUN 0 that is reported when attached to
VNX series or CLARiiON storage systems as well as allow the SCSI
stack to scan up to 255 devices.
Note: The Unisphere/Navisphere Host Agent requires that the disconnected
LUN 0 be reported.
The DKMS RPM will create the QLogic v3.x-series driver as a
module.
Follow these steps to integrate the QLogic driver into RHEL 3.0 hosts:
1. Boot into the qualified and supported kernel onto which the
driver will be installed.
2. Obtain the
qliscsi-linux-3.22-1dkms.tar.gz package from
EMC-approved section of the QLogic website as instructed in
“Downloading the QLogic v3.x-Series iSCSI driver for the v2.4.x
kernel” on page 98.
3. Uncompress and extract the source files from the tar archive:
tar zxvf qliscsi-linux-3.22-1dkms.tar.gz
The initial decompression will provide you with the following:
Creating symlink /var/lib/dkms/qla4xxx/v3.22/source ->
/usr/src/qla4xxx-v3.22
DKMS: add Completed.
Loading/Installing pre-built modules for 2.4.21-4.EL (i686).
Preparing kernel 2.4.21-32.0.1.ELsmp for module build:
(This is not compiling a kernel, only just preparing kernel symbols)
Storing current .config to be restored when complete
Running Red Hat style preparation routine
make clean....
using
/lib/modules/2.4.21-32.0.1.ELsmp/build/configs/kernel-2.4.21-i686-smp.config