EMC Fibre Channel with QLogic Host Bus Adapters for the Linux v2 ...

EMC Fibre Channel with QLogic Host Bus Adapters 

for the Linux v2.4.x Kernel Environment 

and the v6.x-Series and v7.x-Series Drivers 

P/N 300-001-161 

REV A05 

EMC Corporation 

Corporate Headquarters: 

Hopkinton, MA 01748 -9103 

1-508 -435 -1000 

www.emc.com

Copyright © 2001–2005 EMC Corporation. All rights reserved. 

Published: November, 2005 

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. 

Trademark Information 

ii 

EMC Fibre Channel with QLogic HBAs for the Linux v2.4.x Kernel Environment

Contents 

Preface........................................................................................................................... vii 

Chapter 1 

Chapter 2 

Introduction 

Overview........................................................................................... 1-2 

Related Documentation ........................................................... 1-2 

QLogic SANsurfer and SANsurferCLI Utilities................... 1-2 

Host Connectivity..................................................................... 1-3 

Array-Specific Settings.................................................................... 1-4 

For CLARiiON Arrays ............................................................. 1-4 

For Symmetrix Arrays.............................................................. 1-4 

Boot Device Support........................................................................ 1-5 

Zoning ............................................................................................... 1-6 

Useful Linux Utilities and Functions ............................................ 1-7 

Installing and Configuring the QLogic HBA and the 

v6.x-Series and v7.x-Series Drivers 

Installing the HBA ........................................................................... 2-2 

Configuring the BIOS Settings................................................ 2-2 

Verifying the Correct BIOS Version....................................... 2-2 

Upgrading the HBA BIOS .............................................................. 2-4 

Upgrading the HBA BIOS Using QLogic SANsurfer.......... 2-4 

Upgrading the HBA BIOS Using QLogic SANsurferCLI ... 2-4 

Upgrading the HBA BIOS Using the NVRAM File on a 

DOS-Bootable Diskette ............................................................ 2-5 

EMC-Recommended HBA BIOS Settings ............................. 2-6 

EMC-Recommended NVRAM Settings for Linux............... 2-6 

Manually Setting the Topology for QLogic HBAs............... 2-8 

Manually Setting the Data Rate for QLogic HBAs .............. 2-9 

EMC Fibre Channel with QLogic HBAs for the Linux v2.4.x Kernel Environment 

iii

Contents 

Special Instructions for CLARiiON CX200 Direct-Connect 

Dual-Host Oracle9iRAC and RHEL 2.1 Cluster Manager 

Configurations with QLogic QLA234x-Series HBAs ........ 2-10 

Special Instructions for Setting the FC-AL Loop ID for 

CLARiiON CX200 Direct-Connect Oracle9iRAC and RHEL 

2.1 Cluster Manager Configurations with QLogic 

QLA234x-Series HBAs........................................................... 2-10 

Configuring the Linux v2.4.x Host with the QLogic v6.x-Series 

and v7.x-Series HBA Drivers ....................................................... 2-12 

Installation Instructions for the QLogic v6.x-Series 

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

Installation Instructions for the QLogic v7.x-Series 

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

QLogic v7.x-Series Driver Parameters........................................ 2-44 

Enabling Persistent Binding for the QLogic Linux Driver ...... 2-50 

Using SANsurfer to Enable Persistent Binding ................. 2-50 

Additional Notes ........................................................................... 2-55 

Linux Device-Naming Convention...................................... 2-55 

Device Reconfiguration: Procedures ................................... 2-58 

Device Reconfiguration: Device Numbering ..................... 2-61 

HPQ Server-Specific Note ..................................................... 2-62 

(CLARiiON Only) Required /etc/modules.conf Edit for 

RHEL 2.1, RHEL 3.0, and SLES 8.0 Default Modular 

Kernels ..................................................................................... 2-63 

(CLARiiON Only) Linux Navisphere Agent Limitation with 

fdisk on CLARiiON................................................................ 2-65 

(CLARiiON only) Linux Navisphere Agent Limitation with 

VERITAS Volume Manager v3.2 on CLARiiON ............... 2-68 

(CLARiiON only) Linux Navisphere Agent Requirement for 

RHEL 2.1 Intel Itanium Systems .......................................... 2-69 

(CLARiiON Only) Linux Navisphere Agent Requirement for 

RHEL 3.0 Intel Itanium Systems .......................................... 2-69 

Incorporating EMC Fibre Channel.............................................. 2-71 

Chapter 3 

Configuring a Boot Device on the EMC Storage Array 

Cautions and Restrictions for Booting from an EMC Storage 

Array.................................................................................................. 3-2 

CLARiiON-Specific Cautions and Restrictions.................... 3-2 

Symmetrix-Specific Cautions and Restrictions .................... 3-3 

Common Limitations ...................................................................... 3-4 

CLARiiON-Specific Limitations............................................. 3-5 

Symmetrix-Specific Limitations ............................................. 3-6 

iv 


Contents 

Configuring a Symmetrix Boot Device ........................................ 3-7 

Preparing the Symmetrix Storage System............................ 3-7 

Preparing the Host................................................................... 3-7 

Configuring the QLogic BIOS for SAN Boot ....................... 3-8 

Configuring a CLARiiON Boot Device...................................... 3-11 

Preparing the CLARiiON Storage Array............................ 3-11 

Preparing the Host................................................................. 3-11 

Configuring the QLogic BIOS for SAN Boot ..................... 3-12 

Installing Supported RHEL 2.1, RHEL 3.0, and SLES 8 Releases 

onto the EMC Boot Device with the QLogic v6.x-Series and 

v7.x-Series Drivers ........................................................................ 3-15 

Building the QLogic v7.x-Series Driver Diskette .............. 3-15 

Installing RHEL 2.1 and RHEL 3.0 onto the EMC Storage 

Array with the QLogic v7.x-Series Driver Diskette .......... 3-16 

Upgrading the Kernel................................................................... 3-18 

Appendix A 

Setting Up External Boot for IBM Blade Server HS40 

(8839) 

Configuring an HS40 BladeCenter Server to Boot from an 

External Array ............................................................................... A-2 

Index 


v

Contents 

vi 


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 guide 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 guide, please contact your EMC representative. 

Information in this guide includes the following: 

◆ Installation of QLogic HBAs and the v6.x-Series and v7.x-Series 

Drivers 

◆ 

◆ 

Configuration information for Symmetrix attach 

Configuration information for CLARiiON attach 

Audience 

This document is intended for use by storage administrators, system 

programmers, or operators who are involved in acquiring, managing, 

or operating Symmetrix, CLARiiON, and host devices. 

Readers of this guide are expected to be familiar with the following 

topics: 

◆ 

◆ 

◆ 

Symmetrix or CLARiiON system operation 

Linux operating environment 

QLogic HBAs and drivers 


vii

Preface 

Conventions Used in 

This Guide 

EMC uses the following conventions for notes and cautions. 

A note presents information that is important, but not hazard-related. 

! 

CAUTION 

A caution contains information essential to avoid data loss or 

damage to the system or equipment. The caution may apply to 

hardware or software. 

Typographical Conventions 

EMC uses the following type style conventions in this guide: 

AVANT GARDE 

Keystrokes 

Palatino, 

bold 

Palatino, 

italic 

◆ 

◆ 

◆ 

◆ 

Dialog box, button, icon, and menu items in text 

Selections you can make from the user interface, 

including buttons, icons, options, and field 

names 

New terms or unique word usage in text 

Book titles 

Courier, 

italic 

Courier 

Symbolic arguments used in examples of command 

line syntax. 

Command line arguments and parameters when 

used in text, system prompts and displays, and 

specific filenames or complete paths. For example: 

working root directory [/user/emc]: 

c:\Program Files\EMC\Symapi\db 

Courier, 

bold 

◆ 

◆ 

User entry. For example: 

symmpoll -p 

Command names when used in text. 

viii 


Preface 

Where to Get Help 

For questions about technical support, call your local sales office or 

support provider. 

If you have a valid EMC service contract, contact EMC Customer 

Service at: 

United States: (800) 782-4362 (SVC-4EMC) 

Canada: (800) 543-4782 (543-4SVC) 

Worldwide: (508) 497-7901 

Follow the voice menu prompts to open a service call and select the 

applicable product support. 

Sales and Customer 

Service Contacts 

Your Comments 

For additional information on the EMC products and services 

available to customers and partners, refer to the EMC Powerlink 

Website at: 

http://powerlink.emc.com 

Your suggestions will help us continue to improve the accuracy, 

organization, and overall quality of the user publications. Please send 

your opinion of this guide to: 

techpub_comments@emc.com 


ix

Preface 

x 


Invisible Body Tag 

1 

Introduction 

◆ Overview.............................................................................................1-2 

◆ Related Documentation.....................................................................1-2 

◆ QLogic SANsurfer and SANsurferCLI Utilities ............................1-2 

◆ Host Connectivity ..............................................................................1-3 

◆ Array-Specific Settings ......................................................................1-4 

◆ Boot Device Support..........................................................................1-5 

◆ Zoning..................................................................................................1-6 

◆ Useful Linux Utilities and Functions ..............................................1-7 

Introduction 1-1

1 

Introduction 

Overview 

This document is meant to assist in the installation and configuration 

of QLogic Host Bus Adapters (HBAs) and the v6.x-series and 

v7.x-series driver on Linux v2.4.x hosts. The focus of this document is 

to enable the integrated QLogic driver in the Linux distributions and, 

alternatively, to configure Linux hosts using the QLogic v7.x-series 

driver downloadable from the EMC-approved section of the QLogic 

website and using the QLogic driver integrated into the Linux kernel. 

Related 

Documentation 

Refer to the EMC Support Matrix for supported server and HBA 

combinations. The support matrix is available at: 

http://www.emc.com/interoperability/ 

For information on Navisphere, refer to the EMC ® Navisphere ® 

documentation in the Documentation Library on EMC Powerlink: 

http://powerlink.emc.com 

QLogic SANsurfer 

and SANsurferCLI 

Utilities 

The QLogic SANsurfer program is a GUI-based utility, and the 

SANsurferCLI 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 HBAs. 

Complete documentation and the EMC-qualified versions of 

SANsurfer and the SANsurferCLI are available for download from 

the EMC-approved section of the QLogic website: 

http://www.qlogic.com/support/oem_emc.asp 

For 4 GB QLogic HBAs, the minimum required versions are: 

◆ 

SANsurfer — 2.0.30b52 

◆ SANsurfer CLI — 1.06.16 build 23 

1-2 EMC Fibre Channel with QLogic HBAs for the Linux v2.4.x Kernel Environment

Introduction 

1 

Host Connectivity 

Review the EMC Support Matrix or contact your EMC representative 

for the latest information on qualified HBAs, drivers, and Linux 

distributions. 

EMC does not support mixing different types of Fibre Channel HBA 

(including different types from the same vendor) in a server. 

The Fibre Channel HBA 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. 

Overview 1-3

1 

Introduction 

Array-Specific Settings 

EMC CLARiiON ® and Symmetrix ® storage systems must be 

configured for Linux connectivity. Follow the guidelines in this 

section. 

For CLARiiON Arrays 

When attaching a Linux host to a CLARiiON array, follow the 

appropriate guidelines, depending on the environment: 

◆ 

◆ 

◆ 

If the Linux host using QLogic HBAs is not using a failover driver 

such as EMC PowerPath or VERITAS DMP, then the failover 

mode on the CLARiiON must be set to 0. 

If the Linux host is using EMC PowerPath ® , then the failover 

mode must be set to 1. This is the default setting for PowerPath 

enabled hosts. 

If the Linux host is using VERITAS VxVM/DMP, the failover 

mode must be set to 2. 

For Symmetrix 

Arrays 

When attaching a Linux host using QLogic HBAs to a Symmetrix 

system, use the Linux default FA settings: 

Director Bit 

SCP3 

PTOP 

VCM 

EAN 

C * 

Default Setting 

SCSI-3 

Point to Point 

Volume Logix 

Enable Auto Negotiation 

Common Serial Number 

* The C-bit is required when VERITAS VxVM/DMP is being used and for the native failover 

functionality within the Egenera BladeFrame OS. 


Introduction 

1 

Boot Device Support 

Linux hosts using QLogic HBAs have been qualified for booting from 

EMC Storage Array devices interfaced through Fibre Channel as 

specified in the ESM (EMC Support Matrix). 

The Symmetrix or 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 

must be mapped as /dev/sda by the Linux operating system for the 

boot to succeed from the device. 

Refer to Chapter 3, Configuring a Boot Device on an EMC Storage Array, 

for further information on booting from the SAN. 

1 

Boot Device Support 1-5

1 

Introduction 

Zoning 

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 HBA and one EMC 

storage array port. Storage array ports can be shared among HBAs; 

however, each HBA must be in its own zone. 

Multi-initiator zones are not supported in a Linux fabric 

environment. 


Introduction 

1 

Useful Linux Utilities and Functions 

These utilities and functions can be helpful in performing 

configuration operations: 

Utility/Function 

fdisk 

fsck 

mkfs 

mount 

umount 

shutdown 

reboot 

insmod 

rmmod 

modprobe 

lsmod 

lspci 

modinfo 

Description 

Command used to create and manipulate Linux partition tables 

Command used to check and repair a Linux file system 

Command used to create Linux file system on a device 

Command used to attach the file system on a device to the file tree 

Command used to detach a file system 

Command used to shut down the system gracefully 

Command used to stop and restart the operating system 

Utility used to dynamically load a single module into a running kernel 

Utility used to unload loadable modules from the running kernel if they 

are not in use and if other modules are not dependent upon those being 

removed 

Utility used to load or remove a set of modules that can be either a 

single module or a stack of dependent modules 

Utility used to list the currently loaded modules. 

Utility used to display information about all of the system’s PCI buses 

and all of the devices connected to those buses. 

Utility used to query information regarding a kernel module. 

Useful Linux Utilities and Functions 1-7

1 

Introduction 


I 

2 

Installing and Configuring the 

QLogic HBA and the v6.x-Series 

and v7.x-Series Drivers 

This chapter describes the procedures for installing an 

EMC-approved QLogic host bus adapter (HBA) into a Linux host and 

configuring the host for connection to an EMC storage array over 

Fibre Channel. 

◆ Installing the HBA .............................................................................2-2 

◆ Upgrading the HBA BIOS.................................................................2-4 

◆ Configuring the Linux v2.4.x Host with the QLogic v6.x-Series 

and v7.x-Series HBA Drivers..........................................................2-12 

◆ Installation Instructions for the QLogic v6.x-Series Driver .......2-12 

◆ Installation Instructions for the QLogic v7.x-Series Driver .......2-16 

◆ QLogic v7.x-Series Driver Parameters..........................................2-44 

◆ Enabling Persistent Binding for the QLogic Linux Driver.........2-50 

◆ Additional Notes..............................................................................2-55 

Installing and Configuring the QLogic HBA and the v6.x-Series and v7.x-Series Drivers 2-1

2 

Installing and Configuring the QLogic HBA and the v6.x-Series and 

v7.x-Series Drivers 

Installing the HBA 

Install the Linux kernel (including kernel-source) from the distribution 

installation CD, following the procedure provided in the distribution 

installation guide. Partition the boot drive and select the 

packages and services necessary for the host. 

To install the QLogic HBA, follow the instructions included with the 

adapter. Each adapter installs into a single slot. 

Configuring the BIOS Settings 

After the HBA is installed, follow these steps to verify and configure 

HBA firmware settings. 

Refer to the EMC Support Matrix for required BIOS versions for qualified 

HBAs. 

Verifying the Correct BIOS Version 

The BIOS version may be determined at boot time from the QLogic 

banner or from the Fast!Util Options menu. 

◆ 

From the banner — Boot the host and wait for the banner to 

appear. (The following is a QLA2312 example, with the ROM 

BIOS version highlighted): 

Qlogic Corporation 

QLA2312 PCI Fibre Channel ROM BIOS Version 1.42 

Copyright © Qlogic Corporation 1993-2002 All rights reserved 

Press for Fast!UTIL 

www.qlogic.com 

◆ 

• If the banner displays the required version, proceed to 

EMC-Recommended HBA BIOS Settings on page 2-6. 

• If the banner does not display the required version, download 

and upgrade the firmware as described under the Upgrading 

the HBA BIOS on page 2-4; then proceed to EMC-Recommended 

HBA BIOS Settings on page 2-6. 

From the QLogic Fast!Util Options menu: 

a. Boot the host. When the QLogic banner appears, press CTRL-Q 

to enter Fast!Util. 




2 

b. Select Configuration Settings from the Fast!Util Options 

menu. 

c. Select Adapter Settings from the Configuration Settings 

menu. 

d. Under Adapter Settings, note the BIOS version: 

• If the banner displays the required version, proceed to 


• If the banner does not display the required version, 

download and upgrade the firmware as described under 

the Upgrading the HBA BIOS on page 2-4; then proceed to 


Installing the HBA 2-3

2 



Upgrading the HBA BIOS 

The BIOS may be upgraded using the QLogic SANsurfer GUI or 

SANsurferCLI text interface, or by using a DOS bootable floppy. 

Upgrading the HBA 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, 

refer to the QLogic provided documentation on their website 

for detailed instructions. 

To invoke the GUI, type the following command from a terminal 

window: 

/opt/QLogic_Corporation/SANsurfer/SANsurfer & 

When upgrading the BIOS for QLogic 4 GB HBAs, the minimum required 

version of the QLogic SANsurfer GUI is 2.0.30b52. 

Upgrading the HBA BIOS Using QLogic SANsurferCLI 

The SANsurferCLI (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 SANsurferCLI, refer to the 

QLogic provided documentation on their website for detailed 

instructions. 

To invoke the CLI, type the following command: 

/opt/QLogic_Corporation/SANsurferCLI/scli 

When upgrading the BIOS for QLogic 4 GB HBAs, the minimum required 

version of the QLogic SANsurfer CLI is 1.06.16 build 23. 




2 

Upgrading the HBA BIOS Using the NVRAM File on a DOS-Bootable Diskette 

Follow these steps to upgrade the QLogic BIOS using the NVRAM 

file on a DOS-bootable diskette: 

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 to the right of OEM and ISV 

approved/recommended drivers and firmware. 

d. Find the NVRAM file for the HBA(s) in your system, and click 

the associated Download link to save the file. 

2. The file is a self-extracting .zip file that must be extracted to a 

bootable floppy diskette, as follows: 

a. Insert a diskette into a Microsoft Windows 9x machine. 

b. Open any DOS window. 

c. At the DOS prompt, format the diskette: 

format /s a: 

d. At the DOS prompt, change (cd) to the directory in which you 

saved the zipped file, then extract the file to the diskette. 

The QLogic HBA(s) must be installed in the host before proceeding. 

3. Insert the BIOS upgrade installation diskette into the floppy 

drive. 

4. Reboot the host. 

5. After the host has rebooted, a DOS prompt appears. Type 

flasutil /L /F and press ENTER. 

The HBA 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. 

the HBA and Driver 

Upgrading the HBA BIOS 2-5

2 



EMC-Recommended HBA 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 Matrix for required NVRAM versions for 

qualified HBAs. 

EMC-Recommended NVRAM Settings for Linux 

The following table lists the NVRAM parameters and their values. 

The QLogic default values are those that ship with a standard HBA 

that wasn’t included in an EMC package. The EMC-recommended 

settings depend upon whether or not 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 VERITAS DMP 

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 SANsurferCLI to modify the NVRAM settings, 

refer to the SANsurfer or SANsurferCLI documentation from 

QLogic. 

Table 2-1 

QLogic BIOS Settings 

EMC Recommended Settings 

QLogic Default 

No Failover 

Functionality 

With PowerPath 

or VERITAS DMP 

Host Adapter Settings 

Host Adapter BIOS Disabled Disabled Disabled 

Frame Size 2048 2048 2048 

Loop Reset Delay 5 5 5 

Adapter Hard Loop ID Disabled Disabled Disabled 

Hard Loop ID 0 125 125 




2 

Table 2-1 

QLogic BIOS Settings (continued) 

Spinup Delay Disabled Disabled Disabled 

Connection Options (topology) 2 2 1 

Fibre Channel Tape Support Enabled Disabled Disabled 

Data Rate 2 2 2 

Advanced Adapter Settings 

Execution Throttle 16 256 256 

LUNs per Target 8 256 256 

Enable LIP Reset No No No 

Enable LIP Full Login Yes Yes Yes 

Enable Target Reset Yes Yes Yes 

Login Retry Count 8 8 8 

Port Down Retry Count 8 45 30 

Link Down Timeout 15 45 30 

Extended Error Logging Disabled Disabled Disabled 

RIO Operation Mode 0 0 0 

Interrupt Delay Timer 0 0 0 

Selectable Boot Settings 

Selectable Boot Disabled Disabled Disabled 

(Primary) Boot Port Name, WWNN WWNN WWNN 

LUN a 

Boot Port Name, LUN 0 0 0 



a.The WWNN of the server boot LUN must be listed in this field. 


2 



The values for the Connection Options parameter are: 

◆ 

◆ 

◆ 

0 for Loop Only 

1 for Point to Point 

2 for Loop preferred, otherwise Point to Point 

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. 

Manually Setting the Topology for QLogic HBAs 

The EMC default setting for the topology currently 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 attached to an EMC storage array directly. 

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. 





2 

Manually Setting the Data Rate for QLogic HBAs 

The EMC default setting for the data rate on QLA23xx and QLE23xx 

HBAs is Auto Select mode. If necessary, you can set the mode 

manually to 1GB, 2GB, 4GB (on 4 GB-capable QLA246x/QLE246x 

only), or Auto Select. 

To use SANsurfer or the SANsurferCLI to modify the NVRAM settings, 

refer to the SANsurfer or SANsurferCLI documentation from 

QLogic. 

For any device connected to the HBA, set the device data rate (if applicable) 

before setting the HBA data rate. 

Follow these steps for each QLogic HBA to be modified: 

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 the Data Rate setting and press ENTER. 

5. Select the appropriate speed for the device to which the QLA23xx 

HBA will connect. The options are 0 for 1GB/s, 1 for 2GB/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. 



2 



Special Instructions for CLARiiON CX200 Direct-Connect Dual-Host Oracle9iRAC 

and RHEL 2.1 Cluster Manager Configurations with QLogic QLA234x-Series HBAs 

For CLARiiON® CX200 direct-connect dual-host Oracle9i RAC or 

RHEL 2.1 Cluster Manager cluster configurations with QLA234x 

HBAs, the default HBA optic jumper position must be changed. 

! 

CAUTION 

Modifying the jumper setting without using the recommended 

firmware and/or drivers may cause a loss of connectivity. 

1. Remove the HBA from the server as instructed by the server 

guide. 

2. Locate jumper(s) J3 (QLA2340) or J3 and J4 (QLA2342), shown in 

the following figure. 

3. Move the jumper(s), onto pins 1–2 (if not already there). 

To return the jumper(s) to the default factory position, move the 

jumper(s) back to pins 2–3. 

Special Instructions for Setting the FC-AL Loop ID for CLARiiON CX200 

Direct-Connect Oracle9iRAC and RHEL 2.1 Cluster Manager Configurations with 

QLogic QLA234x-Series HBAs 

The FC-AL Loop ID for QLA234x-series HBAs must be set manually 

when directly attaching RHEL 2.1 hosts in Oracle9iRAC or RHEL 2.1 

Cluster Manager configurations. 

Follow the steps below to enable hard addressing and to set the loop 

ID on each HBA. Perform this procedure on both nodes in the cluster 

connected to the CX200. 

The topology must also be changed from the default Point to Point to 

Loop Only. Refer to Manually Setting the Topology for QLogic HBAs on 

page 2-8 for instructions. 

1. Boot the Linux host; press CTRL-Q when prompted to Press CTRL-Q 

for Fast!UTIL. This prompt appears with the QLogic startup 

banner. 




2 

2. After the Fast!UTIL program loads, the initial display depends on 

whether there are multiple QLogic HBAs installed in the server: 

• If there is only one QLogic HBA, the Fast!UTIL Options menu 

appears. 

• If there are multiple QLogic HBAs, a list of memory addresses 

occupied by those HBAs appears. 

Using the arrow keys, select the desired HBA and press ENTER. The 

Fast!UTIL Options menu appears. 

3. Select Configuration Settings from the Fast!UTIL Options menu, 

and press ENTER. 

4. Select Adapter Settings from the Configuration Settings menu. 

5. Select Adapter Hard Loop ID from the Host Adapter Settings 

menu and press ENTER until the value is Enabled. 

6. Select Hard Loop ID and press ENTER. 

Each HBA connected to the same SP must have a unique hard 

loop ID. For example, select 0 for all HBAs on one node, and 

select 1 for all HBAs on the other node. 

7. Enter a value for the loop ID and press ENTER. 

8. Press ESC to return to the Configuration Settings menu. 

9. Press ESC to return to the Fast!UTIL Options menu. 

10. When prompted to save changes made to the current adapter, 

select Save Changes and press ENTER. 

11. If there are more adapters to configure, choose Select Host 

Adapter, and repeat steps 3 through 11 for each adapter. 

12. Press ESC to exit Fast!UTIL. 


14. Repeat this procedure on all nodes in the cluster connected to the 

CX200. 

To restore EMC default HBA settings, either reload the approved 

EMC NVRAM file, or return to step 5 and ensure that Adapter Hard 

Loop ID is set to Disabled. 

Driver 


2 



Configuring the Linux v2.4.x Host with the QLogic v6.x-Series and 

v7.x-Series HBA Drivers 

Using the QLogic adapter with the Linux operating system requires 

HBA driver software. The driver functions at a layer below the Linux 

SCSI driver to present Fibre Channel devices to the operating system 

as if they were standard SCSI devices. 

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. 

Installation Instructions for the QLogic v6.x-Series Driver 

◆ 

Enabling the QLogic v6.05.00 Driver in SLES 8 SP3 

◆ Enabling the QLogic v6.04.01 Driver in RHEL 2.1 on page 2-14 

◆ 

Enabling the QLogic v6.07.02-RH2 Driver in RHEL 3.0 U2 on 

page 2-15 

The QLogic QLA2200 HBAs are supported only with the v6.x-series driver. 


EMC supports the QLogic v6.05.00 driver included in SuSE SLES 8 

distribution. However, the default driver in this distribution is the 

v6.06.00 driver. 

The following procedure should be used to enable the v6.05.00 driver. 

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. 

1. Edit the /etc/sysconfig/kernel file: 

vi /etc/sysconfig/kernel 

For QLogic QLA23xx-series HBAs, add the reference to the 

QLogic v6.05.00 qla2300-60500 driver in the INITRD_MODULES 

line: 

INITRD_MODULES=”scsi_mod sd_mod mptscsih qla2300-60500 reiserfs” 




2 

2. Save the changes and quit from vi. 

3. Edit the /etc/modules.conf file: 

vi /etc/modules.conf 

Add the entry for each installed QLogic QLA23xx-series HBA: 

alias scsi_hostadapterN qla2300-60500 

where N is the sequential value of each QLogic HBA 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 HBA entries are listed after the internal 

SCSI host adapter entry in both files. 

For example: 

alias parport_lowlevel parport_pc 

alias scsi_hostadapter sym53c8xx 

alias scsi_hostadapter1 qla2300-60500 

alias scsi_hostadapter2 qla2300-60500 

alias eth0 tlan 

options scsi_mod max_scsi_luns=255 scsi_allow_ghost_devices=1 

4. Save the changes and quit from vi. 

5. Create a new ramdisk to reflect the changes made: 

cd /boot 

mkinitrd –k vmlinuz-$1 –i initrd-$1 

where $1 is the v2.4.x kernel version currently running. 

For example: 

cd /boot 

mkinitrd –k vmlinuz-2.4.21-190 –i initrd-2.4.21-190 

6. Reboot the system. 

Configuring the Linux v2.4.x Host with the QLogic v6.x-Series and v7.x-Series HBA Drivers 2-13

2 



Enabling the QLogic v6.04.01 Driver in RHEL 2.1 

EMC supports the QLogic v6.04.01 driver included in the RHEL 2.1 

distribution. In RHEL 2.1 kernels v2.4.9-e.24 through v2.4.21-59, the 

QLogic v6.04.01 driver is the default driver within the kernel. The following 

procedure should be used to enable the v6.04.01 driver. 

1. Ensure that the /etc/modules.conf file references an entry for 

each installed QLogic HBA. 

For each installed QLogic HBA, add an entry: 

alias scsi_hostadapterN qla2300 




zero.) 

For example: 



alias scsi_hostadapter1 qla2300 




2. Whenever any modifications are made to the 

/etc/modules.conf file, 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 HBAs: 

cd /boot 

mkinitrd –v initrd-$1.img $1 


For example: 

cd /boot 

mkinitrd –v initrd-2.4.9-e.59smp.img 2.4.9-e.359mp 





2 

Enabling the QLogic v6.07.02-RH2 Driver in RHEL 3.0 U2 

EMC supports the default QLogic v6.07.02-RH2 driver integrated 

into the RHEL 3.0 U2 distribution. The following procedure should 

be used to enable the v6.07.02-RH2 driver. 



For each installed QLogic HBA, add an entry: 



the system, beginning with the number adter the last host adapter 


zero.) 

For example: 

alias parport_lowlevel partport_pc 




alias eth0 tg3 


2. Whenever any modifications are made to the 

/etc/modules.conf file, 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 HBAs: 

cd /boot 



Example: 

mkinitrd –v initrd-2.4.21-15.ELsmp.img 2.4.21-15.ELsmp 


2 


2 



Installation Instructions for the QLogic v7.x-Series Driver 

The QLogic QLA2200 HBAs are supported only with the v6.x-series driver. 

Enabling the QLogic v7.01.01-RH1 Driver in RHEL 2.1 U7 

EMC supports the QLogic v7.01.01-RH1 driver, which is integrated 

into the RHEL 2.1 U7 distribution. Follow these steps to enable the 

driver: 



For each installed QLogic QLA23xx-series HBA, add an entry: 





zero.) 

Example: 







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

cd /boot 

mkinitrd -v initrd-$1.img $1 


Example: 

mkinitrd -v initrd-2.4.9-e.62smp.img 2.4.9-e.62smp 





2 

Enabling the QLogic v7.01.01-RH1 Driver in RHEL 3.0 U4 and U5 

EMC supports the QLogic v7.01.01-RH1 driver included in RHEL 3.0 

U4 and U5 distributions. In the RHEL 3.0 kernel v2.4.21-27.EL and 

later, the QLogic v7.01.01-RH1 driver is the default driver integrated 

into the kernel. To enable this driver, follow these steps: 



For each installed QLogic QLA23xx-series HBA, add an entry: 





zero.) 

Example: 







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

cd /boot 



Example: 

mkinitrd -v initrd-2.4.21-27.ELsmp.img 2.4.21-27.ELsmp 



2 




EMC supports the QLogic v7.03.00 driver included as the default in 

the SuSE SLES 8 SP4 distribution. 

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. 

Follow these steps to enable the v7.03.00 driver: 

1. Edit /etc/sysconfig/kernel: 

vi /etc/sysconfig/kernel 

a. Add a reference to the QLogic qla2300.o driver in the 

INITRD_MODULES line: 

INITRD_MODULES="scsi_mod sd_mod mptscsih qla2300 reiserfs" 

b. Save the changes and quit from vi. 

2. Edit /etc/modules.conf: 


a. Add this entry for each installed QLogic HBA: 


where N is the sequential value of each QLogic HBA 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 HBA entries are listed after the 

internal SCSI host adapter entry in both files. 

Example: 






options scsi_mod max_scsi_luns=255 

scsi_allow_ghost_devices=1 

b. Save the changes and quit from vi. 




2 


cd /boot 

mkinitrd -k vmlinuz-$1 -i initrd-$1 


Example: 

cd /boot 

mkinitrd -k vmlinuz-2.4.21-295-smp -i initrd-2.4.21-295-smp 

4. Reboot the system. 

Installing the QLogic v7.03.00 and v7.07.00 Drivers 

The QLogic v7.03.00 driver is supported on QLA23xx and 

QLE23xx-series HBAs for RHEL 2.1 and for RHEL 3.0 kernels up to 

and including RHEL 3.0 U5. 

The QLogic v7.07.00 driver introduces support for the 4GB capable 

QLA24xx/QLE24xx-series HBAs. The v7.07.00 driver is supported 

only on RHEL 3.0 U6 at this time. 

Neither of these drivers is included in Red Hat or SuSE distributions 

and, therefore, they must be downloaded from the EMC-approved 

section of the QLogic website. 

Refer to the EMC Support Matrix for specific kernel versions supported. 

Versions listed in the support matrix supersede all revisions 

listed in this document. 

Downloading the QLogic v7.x-Series Driver for the v2.4.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 the following url: 

http://www.qlogic.com/support/oem_emc.asp 

2. Depending upon the EMC storage array being used, select the 

appropriate link from one of the following categories: 

• EMC CLARiiON > EMC Symmetrix & EMC Celerra 

supported software 

• EMC CLARiiON AX100 supported software 

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. 


2 



4. Find the desired and supported driver for the kernel version and 

distribution, and click the associated Download link to save the 

file. 

5. Select a method to install the driver onto the Linux host: 

• For the QLogic v7.03.00 driver: 

– To create a modular v7.03.00 driver using the DKMS RPM, 

refer to Installing the QLogic v7.03.00 Driver via the QLogic 

DKMS RPM: Method One on page 2-22. 

– To create a modular v7.03.00 driver using the QLogic RPM, 


RPM: Method Two on page 2-25. 

• For the QLogic v7.07.00 driver: 

– To create a modular v7.07.00 driver using the DKMS RPM, 


DKMS RPM: Method One on page 2-31. 

– To create a modular v7.07.00 driver using the QLogic RPM, 


Installation Script: Method Two on page 2-34. 

Installation Methods for the QLogic v7.03.00 Driver 

The QLogic v7.03.00 driver may be installed onto a Linux host using 

one of the following methods: 

◆ 

Method One — Use the DKMS RPM to compile and install the 

modular driver for Dell servers running RHEL 2.1, RHEL 3.0, and 

SLES 8 attached to EMC storage arrays. 

◆ Method Two — Use the QLogic RPM to compile and install the 

modular driver for RHEL 2.1, RHEL 3.0, and SLES 8 systems 

attached to EMC storage arrays. 

Here is a brief description of the installation methods for the v7.03.00 

driver: 

◆ 

◆ 

Method One — Requires no manual edits for servers attached to 

EMC storage arrays. By installing the DKMS RPM, the necessary 

files are edited and the driver is compiled and installed 

automatically. 

Method Two — Requires no manual edits for systems attached to 

EMC storage arrays. By installing the QLogic RPM, the necessary 

files are edited and the driver is compiled and installed 





2 

Note that prior to installing the QLogic driver, processes holding the 

driver open must be stopped so that the currently loaded driver can 

be removed from the running kernel. 

Perform the following steps prior to the installation: 

◆ Stop all I/O. 

◆ Unmount all filesystems attached to the QLogic driver. 

◆ If the Navisphere Agent/CLI is installed and enabled on the host, 

stop the Navisphere Agent/CLI service. 

To stop the Navisphere Agent/CLI service, type one of the 

following commands: 

/etc/init.d/Naviagentcli stop 

or 

service Naviagentcli stop 

◆ 

If PowerPath is installed and enabled on the host, stop the 

PowerPath service. 

To stop the PowerPath service, type one of the following 

commands: 

/etc/init.d/PowerPath stop 

or 

service PowerPath stop 

◆ 

If the QLogic SANsurfer daemon qlremote is installed and 

enabled on the host, stop the qlremote service so the driver can 

be removed from the currently running kernel. 

To stop the qlremote service, type one of the following 

commands: 

/etc/init.d/qlremote stop 

or 

service qlremote stop 


2 



Installing the QLogic v7.03.00 Driver via the QLogic DKMS RPM: 

Method One 

This section guides you through the process of installing and utilizing 

the DKMS RPM for RHEL 2.1, RHEL 3.0, and SLES 8 distributions. 

The DKMS RPM builds and installs the qla2200.o and qla2300.o 

drivers and modifies the /etc/modules.conf file. 

In the /etc/modules.conf file, the hostadapter line for the 

qla2200.o and qla2300.o drivers 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 CLARiiON storage arrays, and allows the 

SCSI stack to scan up to 255 devices. 

The Navisphere Host Agent requires that the disconnected LUN 0 be 

reported. 

The DKMS RPM creates the QLogic v7.x-series driver as a module. 

Follow these steps to integrate the QLogic driver into RHEL 2.1 or 3.0 

hosts: 

1. Boot into the qualified and supported kernel onto which the 

driver will be installed. 

2. Obtain the qla2x00-v7.03.00-1dkms.tgz package from 

EMC-approved section of the QLogic website as instructed under 

Downloading the QLogic v7.x-Series Driver for the v2.4.x Kernel on 

page 2-19. 

3. Uncompress and extract the source files from the tar archive: 

tar zxvf qla2x00-v7.03.00-1dkms.tgz 

The initial decompression provides the following: 

./qla2x00-v7.03.00/ 

./qla2x00-v7.03.00/README.dkms 

./qla2x00-v7.03.00/dkms-2.0.0-1.noarch.rpm 

./qla2x00-v7.03.00/qla2x00-v7.03.00-1dkms.noarch.rpm 

4. Install the DKMS RPM: 

cd qla2x00-v7.03.00 

rpm -ivh dkms-2.0.0-1.noarch.rpm 




2 

Output example: 

warning: dkms-2.0.0-1.noarch.rpm: V3 DSA signature: 

NOKEY, key ID 23b66a9d 

Preparing... 

########################################### [100%] 

1:dkms ########################################### 

[100%] 

5. Install the QLogic driver RPM: 

rpm -ivh qla2x00-v7.03.00-1dkms.noarch.rpm 

Example of console output reported by the RPM driver installation: 

root@l82bi114 qla2x00-v7.03.00]# rpm -ivh 

qla2x00-v7.03.00-1dkms.noarch.rpm 

Preparing... ########################################### [100%] 

1:qla2x00 ########################################### [100%] 

Creating symlink /var/lib/dkms/qla2x00/v7.03.00/source -> 

/usr/src/qla2x00-v7.03.00 

DKMS: add Completed. 

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 Generic preparation routine 

make mrproper.... 

using /lib/modules/2.4.21-32.0.1.ELsmp/build/configs/kernel-2.4.21 

-i686-smp.config 

make oldconfig..... 

make dep.................. 

Building module: 

cleaning build area.... 

make KERNELRELEASE=2.4.21-32.0.1.ELsmp SMP=1 all INCLUDEDIR=/ 

lib/modules/2.4.21-32.0.1.ELsmp/build/include.......... 


cleaning kernel tree (make mrproper).... 

DKMS: build Completed. 

Running module version sanity check. 

qla2200.o: 

- Original module 

- Found 

/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/qla2200.o 

- Storing in 

/var/lib/dkms/qla2x00/original_module/2.4.21-32.0.1.ELsmp/i686/ 

- Archiving for uninstallation purposes 

- Installation 


2 



- Installing to 

/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/addon/qla2200/ 

qla2300.o: 


- Found 

/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/scsi/qla2300.o 

- Storing in 

/var/lib/dkms/qla2x00/original_module/2.4.21-32.0.1.ELsmp/i686/ 

- Archiving for uninstallation purposes 




/etc/modules.conf: added 'options scsi_mod scsi_allow_ghost_devices=1 

max_scsi_luns=255' 

depmod.... 

Saving old initrd as /boot/initrd-2.4.21-32.0.1.ELsmp_old.img 

Making new initrd as /boot/initrd-2.4.21-32.0.1.ELsmp.img 

(If next boot fails, revert to the _old initrd image) 

mkinitrd.... 

DKMS: install Completed. 

Example of modified /etc/modules.conf: 

[root@l82bi114 qla2x00-v7.03.00]# more /etc/modules.conf 

alias eth0 e1000 


alias scsi_hostadapter mptbase 

alias scsi_hostadapter1 mptscsih 



alias usb-controller usb-uhci 


post-remove qla2200 rmmod qla2200_conf 


options scsi_mod scsi_allow_ghost_devices=1 max_scsi_luns=255 

A new ramdisk is created automatically by the DKMS RPM 

installation. 





2 

Installing the QLogic v7.03.00 Driver via the QLogic RPM: 

Method Two 


the QLogic driver RPM for RHEL 2.1, RHEL 3.0, and SLES 8 

distributions. The RPM builds and installs the qla2300.o driver and 

modifies the /etc/modules.conf file. 

In /etc/modules.conf, the hostadapter 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 

CLARiiON storage arrays, and allows the SCSI stack to scan up to 

255 devices. 


reported. 

The QLogic RPM creates the QLogic v7.03.00 driver as a module. 

Follow these steps to install the QLogic driver RPM onto RHEL 2.1, 

RHEL 3.0, and SLES 8 hosts: 



2. Obtain the qla2x00-v7.03.00-1.i686.rpm package from 


the Downloading the Driver section on page 2-17. 

3. Install the QLogic driver: 

[root@l82bi114 extra]# rpm -ivh qla2x00-v7.03.00-1.i686.rpm 

Preparing... ########################################### [100%] 

1:qla2x00 ########################################### [100%] 

Example of the console output reported by the driver RPM installation: 

Qlogic qla2300/qla2200 HBA Driver installation supports the 

following distribution and its different flavours : 

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 


2 



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 


install -o root -g root qla2200_conf.o 


install -o root -g root qla2300_conf.o 


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 scsi_hostadapter2 qla2300_conf 





2 

A new ramdisk is created automatically by the RPM installation. 


Uninstallation Methods for the QLogic v7.03.00 Driver 

This section describes how to successfully uninstall the QLogic 

v7.03.00 driver from a Linux host. 

The method used to uninstall the driver is dependent upon the installation 

package: 

◆ 

◆ 

Method One — Using the DKMS RPM 

Method Two — Using the QLogic RPM 

Uninstalling the QLogic v7.03.00 Driver via the QLogic DKMS 

RPM: Method One 

This section provides guidance for uninstalling the QLogic v7.03.00 

driver via the QLogic DKMS RPM package. The driver may be 

removed from the system with the e switch for the RPM command. 

1. Verify the driver names by querying the DKMS RPMs. 

[root@l82bi235 qla2x00-v7.03.00]# rpm -qa | grep dkms 

qla2x00-v7.03.00-1dkms 

dkms-2.0.0-1 

2. Type the following command to uninstall the QLogic driver RPM: 

[root@l82bi235 qla2x00-v7.03.00]# rpm -ev qla2x00-v7.03.00-1dkms 

Example of the console output reported by the driver RPM removal: 

Uninstall of qla2x00 module (version v7.03.00) beginning: 

-------- Uninstall Beginning -------- 

Module: qla2x00 

Version: v7.03.00 

Kernel: 2.4.21-27.0.4.ELsmp (i686) 

------------------------------------- 

Status: Before uninstall, this module version was ACTIVE on this 

kernel. 

qla2200.o: 

- Uninstallation 

- Deleting from: 



- Archived original module found in the DKMS tree 

- Moving it to: 



2 



qla2300.o: 





- Archived original module found in the DKMS tree 

- Moving it to: 


Saving old initrd as /boot/initrd-2.4.21-27.0.4.ELsmp_old.img 

Making new initrd as /boot/initrd-2.4.21-27.0.4.ELsmp.img 


mkinitrd.... 

Removing original_module from DKMS tree for kernel 2.4.21-27.0.4.ELsmp 

(i686) 

DKMS: uninstall Completed. 

------------------------------ 

Deleting module version: v7.03.00 

completely from the DKMS tree. 

------------------------------ 

Done. 

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. 


Uninstalling the QLogic v7.03.00 Driver via the QLogic RPM: 

Method Two 


driver RPM. The QLogic RPM may be used to remove the driver with 

the e switch for the RPM command. 

1. Verify the currently loaded QLogic driver RPM: 

[root@l82bi235 extra]# rpm -qa | grep qla 

qla2x00-v7.03.00-1 

2. Remove the driver using the RPM command: 

[root@l82bi235 extra]# rpm -ev qla2x00-v7.03.00-1 

Example of the console output reported by this driver removal: 

UNINSTALL of rpm version v7.03.00-1 beginning... 

Removing qla2300 from 2.4.21-27.0.4.ELsmp... 

Removing qla2300_conf from 2.4.21-27.0.4.ELsmp... 




2 

Previous qla2300 restored from 

/usr/src/qla2x00/qla2300.2.4.21-27.0.4.ELsmp.v7.03.00-1.orig 

Previous qla2300_conf restored from 

/usr/src/qla2x00/qla2300_conf.2.4.21-27.0.4.ELsmp.v7.03.00-1.orig 

depmod... 

Uninstall of qla2300 for 2.4.21-27.0.4.ELsmp complete. 

Removing qla2200 from 2.4.21-27.0.4.ELsmp... 

Removing qla2200_conf from 2.4.21-27.0.4.ELsmp... 

Previous qla2200 restored from 

/usr/src/qla2x00/qla2200.2.4.21-27.0.4.ELsmp.v7.03.00-1.orig 

Previous qla2200_conf restored from 

/usr/src/qla2x00/qla2200_conf.2.4.21-27.0.4.ELsmp.v7.03.00-1.orig 

depmod... 

Uninstall of qla2200 for 2.4.21-27.0.4.ELsmp complete. 

Restoring original /etc/modules.conf file. 

Restoring the original ramdisk image... 

Uninstall the QLogic SNIA API library libqlsdm.so 

Removing QLogic HBA API library... 

Done. 

Done. 



created. If the ramdisk has not been created, create one: 

cd /boot 



Example: 

cd /boot 

mkinitrd -v initrd-2.4.21-27.0.4.ELsmp.img 2.4.21-27.0.4.ELsmp 


Installation Methods for the QLogic v7.07.00 Driver 

The QLogic v7.07.00 driver may be installed onto RHEL 3.0 U6 Linux 

host using one of the two following methods: 

◆ 

◆ 

Method One — Use the DKMS RPM to compile and install the 

modular driver for Dell servers running RHEL 3.0 attached to 

EMC storage arrays. 

Method Two — Use the QLogic installation script to compile and 

install the modular driver onto RHEL 3.0 systems attached to 



2 



The following is a brief description of the installation methods for the 

v7.07.00 driver: 

◆ 

Method One — Requires no manual edits for Dell servers 

attached to EMC storage arrays. By installing the DKMS RPM, the 

necessary files are edited and the driver is compiled and installed 


◆ Method Two — 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 


Note that prior to installing the QLogic driver, processes holding the 

driver open must be stopped so that the currently loaded driver may 

be removed from the running kernel. Perform the following steps 

prior to the installation: 

◆ 

◆ 

◆ 

Stop all I/O. 

Unmount all filesystems attached to the QLogic driver. 

If the Navisphere Agent/CLI is installed and enabled on the host, 

stop the Navisphere Agent/CLI service. 




or 


◆ 




commands: 


or 


◆ 







2 


commands: 


or 


Installing the QLogic v7.07.00 Driver via the QLogic DKMS RPM: 

Method One 


the DKMS RPM for the RHEL 3.0 U6 release. The DKMS RPM builds 

and installs the qla2300 and qla2300_conf drivers and modifies the 

/etc/modules.conf file. 

In /etc/modules.conf, the hostadapter line for the qla2300 and 

qla2300_conf drivers 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 CLARiiON storage arrays, and allows the 

SCSI stack to scan up to 255 devices. 


reported. 

The DKMS RPM creates the QLogic v7.x-series driver as a module. 

Follow these steps to integrate the QLogic driver into RHEL 3.0 hosts: 



2. Obtain the qla2x00-v7.07.00-2dkms.tar.gz package from 




tar zxvf qla2x00-v7.07.00-2dkms.tar.gz 


qla2x00-v7.07.00-2dkms/ 

qla2x00-v7.07.00-2dkms/qla2x00-v7.07.00-2dkms.noarch. 

rpm 

qla2x00-v7.07.00-2dkms/dkms-2.0.5-1.noarch.rpm 

qla2x00-v7.07.00-2dkms/README.dkms 


2 



4. Install the DKMS RPM: 

cd qla2x00-v7.07.00-2dkms 

rpm -ivh dkms-2.0.5-1.noarch.rpm 

Output example: 

Preparing... ########################################### [100%] 

1:dkms ########################################### [100%] 

5. Install the QLogic driver RPM: 


Example of console output reported by the driver RPM installation: 


Preparing... ########################################### [100%] 

1:qla2x00 ########################################### [100%] 

Creating symlink /var/lib/dkms/qla2x00/v7.07.00/source -> 

/usr/src/qla2x00-v7.07.00 

DKMS: add Completed. 

Preparing kernel 2.4.21-37.ELsmp for module build: 

(This is not compiling a kernel, only just preparing kernel symbols) 

Running Red Hat style preparation routine 

make clean.... 

using 

/lib/modules/2.4.21-37.ELsmp/build/configs/kernel-2.4.21-i686-smp. 

config 

make oldconfig...... 

running dkms_mkkerneldoth.... 

Building module: 


make KERNELRELEASE=2.4.21-37.ELsmp SMP=1 all 

INCLUDEDIR=/lib/modules/2.4.21-37.ELsmp/build/include.......... 


DKMS: build Completed. 

Running module version sanity check. 

qla2300.o: 


- No original module exists within this kernel 



/lib/modules/2.4.21-37.ELsmp/kernel/drivers/addon/qla2200/ 

/etc/modules.conf: added 'options scsi_mod scsi_allow_ghost_devices=1 

max_scsi_luns=255' 




2 

depmod.... 

Saving old initrd as /boot/initrd-2.4.21-37.ELsmp_old.img 

Making new initrd as /boot/initrd-2.4.21-37.ELsmp.img 


mkinitrd.... 

DKMS: install Completed. 

An example of the modified /etc/modules.conf: 

[root@l82bi114 qla2x00-v7.07.00]# more /etc/modules.conf 










options scsi_mod scsi_allow_ghost_devices=1 max_scsi_luns=255 

As specified in the installation output, a new ramdisk is created 

automatically by the DKMS RPM installation. 

If additional changes to /etc/modules.conf are necessary, create 

a new ramdisk manually: 

cd /boot 



Example: 

cd /boot 




2 



Installing the QLogic v7.07.00 Driver via the QLogic Installation 

Script: Method Two 


the QLogic driver installation script for RHEL 3.0 U6 hosts. The 

installation script builds and installs the qla2300 and qla2300_conf 

drivers and modifies the /etc/modules.conf file. 

By default, the installation script installs the QLogic HBA SNIA API 

libraries, the SANsurferCLI, and the qlremote service. 

In /etc/modules.conf, the hostadapter line for the qla2300 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 CLARiiON 

storage arrays, and allows the SCSI stack to scan up to 255 devices. 


reported. 

Follow these steps to install the QLogic driver via the installation 

script onto RHEL 3.0 U6 hosts: 



2. Obtain the qlafc-linux-7.07.00-3-install.tgz package from 




tar zxvf qlafc-linux-7.07.00-3-install.tgz 


qlafc-linux-7.07.00-3-install/ 

qlafc-linux-7.07.00-3-install/README.qlinstall.txt 

qlafc-linux-7.07.00-3-install/qla2x00-v7.07.00-1. 

noarch.rpm 

qlafc-linux-7.07.00-3-install/set_driver_param 

qlafc-linux-7.07.00-3-install/scli-1.06.16-34.ppc64. 

rpm 

qlafc-linux-7.07.00-3-install/scli-1.06.16-34.i386. 

rpm 

qlafc-linux-7.07.00-3-install/qlinstall 




2 

qlafc-linux-7.07.00-3-install/scli-1.06.16-34.ia64. 

rpm 

4. Install the QLogic driver via the installation script provided. 

When using the -i switch, the driver is compiled, the current 

driver is unloaded, and the newly compiled driver is loaded into 

the kernel. 

Proceed with the installation: 

[root@l82bi116 ]# cd qlafc-linux-7.07.00-3-install 

[root@l82bi116 qlafc-linux-7.07.00-3-install]# ./qlinstall -i 

Example of console output reported by the installation script: 

#*********************************************************# 

# SANsurfer Driver Installer for Linux # 

# Installer Version: 1.00.04 # 

#*********************************************************# 

Kernel version: 2.4.21-37.ELsmp 

Distribution: Red Hat Enterprise Linux AS release 3 (Taroon Update 6 Beta) 

Found QLogic Fibre Channel Adapter in the system 

1: QLA2300 

Installation will begin for following driver(s) 

2: qla2x00 version: v7.07.00 

Preparing... ################################################## 

qla2x00 ################################################## 

Creating initial /usr/src/qlogic/v7.07.00-1/install.v7.07.00-1.log... 

Please wait: Preparing qla2x00 modular driver build 

\ 

Installing driver in /lib/modules/2.4.21-37.ELsmp/kernel/drivers/scsi.... 

Building module dependency.... 

depmod... 

Setting up QLogic HBA SNIA API library... 

Unloading any loaded drivers 

rmmod: module qla2300_conf is not loaded 

modprobe: post-remove qla2300 failed 

qla2300: Device or resource busy 

Loading module qla2300_conf version: v7.07.00.... 

Loaded module qla2300_conf 

Installing scli.... 

Preparing... ################################################## 

scli ################################################## 

Installation completed successfully. 

Building default persistent binding using SCLI 


2 



Configuration saved on HBA port 0. 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 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/modules.conf as 

/usr/src/qlogic/v7.07.00-1/backup/modules.conf-2.4.21-37.ELsmp-102805-111817.bak 


depmod... 

Saved copy of /boot/initrd-2.4.21-37.ELsmp.img as 

/usr/src/qlogic/v7.07.00-1/backup/initrd-2.4.21-37.ELsmp.img-102805-111818.bak 

Creating ramdisk 

mkinitrd... 

Ramdisk created. 

Reloading the QLogic FC HBA drivers.... 

Unloaded module qla2300_conf 

Loading module qla2300_conf version: v7.07.00.... 

Loaded module qla2300_conf 

Target Information on all HBAs: 

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

----------------------------------------------------------------------------- 

HBA Port 0 - QLA2300/2310 Port Name: 21-00-00-E0-8B-05-34-1C Port ID: 65-0A-13 

----------------------------------------------------------------------------- 

Path : 0 

Target : 0 

Device ID : 0x81 

Port ID : 6C-1B-13 

Product Vendor : DGC 

Product ID : RAID 5 

Product Revision : 0216 

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) : 8 

Status : Online 

----------------------------------------------------------------------------- 

Path : 0 

Target : 1 


Port ID : 6A-2D-13 







2 

Node Name : 50-06-01-60-90-60-12-5C 

Port Name : 50-06-01-6B-10-60-12-5C 




----------------------------------------------------------------------------- 

Path : 0 

Target : 2 


Port ID : 61-1A-13 




Node Name : 50-06-01-60-90-60-12-70 

Port Name : 50-06-01-6A-10-60-12-70 




----------------------------------------------------------------------------- 

Path : 0 

Target : 3 


Port ID : 74-4A-13 




Node Name : 50-06-01-60-90-60-12-5C 

Port Name : 50-06-01-62-10-60-12-5C 




----------------------------------------------------------------------------- 

----------------------------------------------------------------------------- 

HBA Port 1 - QLA2300/2310 Port Name: 21-00-00-E0-8B-05-3B-1C Port ID: 65-0B-13 

----------------------------------------------------------------------------- 

Path : 0 

Target : 0 


Port ID : 6C-1B-13 




Node Name : 50-06-01-60-90-60-12-70 

Port Name : 50-06-01-62-10-60-12-70 




----------------------------------------------------------------------------- 

Path : 0 

Target : 1 


Port ID : 6A-2E-13 


2 






Node Name : 50-06-01-60-90-60-12-5C 

Port Name : 50-06-01-6A-10-60-12-5C 




----------------------------------------------------------------------------- 

Path : 0 

Target : 2 


Port ID : 61-1A-13 




Node Name : 50-06-01-60-90-60-12-70 

Port Name : 50-06-01-6A-10-60-12-70 




----------------------------------------------------------------------------- 

Path : 0 

Target : 3 


Port ID : 74-49-13 




Node Name : 50-06-01-60-90-60-12-5C 

Port Name : 50-06-01-63-10-60-12-5C 




----------------------------------------------------------------------------- 

#*********************************************************# 

# INSTALLATION SUCCESSFUL!! # 

# SANsurfer Driver installation for Linux completed # 

#*********************************************************# 

By default, the QLogic installation script builds the persistent 

binding information for the HBAs installed in the system. This is 

performed during the installation by the SANsurfer CLI. If 

persistent binding is not required, then the installation should be 

run with the dp switch. 




2 

Example: 

[root@l82bi116 qlafc-linux-7.07.00-3-install]# ./qlinstall -i -dp 

Example of the modified /etc/modules.conf: 

[root@l82bi114 extra]# more /etc/modules.conf 










alias scsi_hostadapter2 qla2300_conf 


A new ramdisk is created automatically by the QLogic 

installation script. 

Verify that the /etc/modules.conf file contains the information 


created. 

If additional modifications to /etc/modules.conf are necessary, 

create a new ramdisk manually: 

• For Red Hat, type: 

cd /boot 

mkinitrd initrd-$1.img $1 

where $1 is the v2.4.x kernel version that is currently running. 

Example: 

cd /boot 

mkinitrd initrd-2.4.21-27.0.4.ELsmp.img 2.4.21-27.0.4.ELsmp 

• For SuSE, type: 

cd /boot 

mkinitrd -i initrd-$1 -k vmlinuz-$1 


Example: 

cd /boot 

mkinitrd -i initrd-2.4.21-286-smp -k vmlinuz-2.4.21-286-smp 



2 



Uninstallation Methods for the QLogic v7.07.00 Driver 

This section describes how to successfully uninstall the QLogic 

v7.07.00 driver from a Linux host. 

The method used to uninstall the driver is dependent upon the installation 

package: 

◆ 

◆ 

Method One — Using the DKMS RPM 

Method Two — Using the QLogic Installer Script 

Uninstalling the QLogic v7.07.00 Driver via the QLogic DKMS 

RPM: Method One 


driver via the QLogic DKMS RPM package. The driver may be 

removed from the system with the 'e' switch for the RPM command. 

1. Verify the driver names by querying the DKMS RPMs: 

[root@l82bi116 qla2x00-v7.07.00-2dkms]# rpm -qa | grep dkms 

dkms-2.0.5-1 

qla2x00-v7.07.00-2dkms 

2. Type the following command to uninstall the QLogic driver RPM: 

[root@l82bi116 qla2x00-v7.07.00-2dkms]# rpm -ev 

qla2x00-v7.07.00-2dkms 

Example of console output reported by the driver RPM removal: 

Uninstall of qla2x00 module (version v7.07.00) beginning: 

-------- Uninstall Beginning -------- 

Module: qla2x00 

Version: v7.07.00 

Kernel: 2.4.21-37.ELsmp (i686) 

------------------------------------- 

Status: Before uninstall, this module version was ACTIVE on this 

kernel. 

qla2300.o: 



/lib/modules/2.4.21-37.ELsmp/kernel/drivers/addon/qla2200/ 


- No original module was found for this module on this kernel. 

- Use the dkms install command to reinstall any previous module 

version. 

/etc/modules.conf: removed alias for 'qla2300' 




2 

/etc/modules.conf: removed 'options scsi_mod 

scsi_allow_ghost_devices=1 max_scsi_luns=255' 

Saving old initrd as /boot/initrd-2.4.21-37.ELsmp_old.img 

Making new initrd as /boot/initrd-2.4.21-37.ELsmp.img 


mkinitrd.... 

DKMS: uninstall Completed. 

------------------------------ 

Deleting module version: v7.07.00 

completely from the DKMS tree. 

------------------------------ 

Done. 



created. 

If additional changes to /etc/modules.conf are necessary, create 

a new ramdisk manually: 

cd /boot 



Example: 

cd /boot 



Uninstalling the QLogic v7.07.00 Driver via the QLogic 

Installation Script: Method Two 


driver via the QLogic installation script. The driver may be removed 

from the system with the u switch for the qlinstall script. 

1. Change to the directory where the installation script is located: 

[root@l82bi116 /]# cd /qlafc-linux-7.07.00-3-install 

2. Type the following command to uninstall the QLogic driver: 

[root@l82bi116 qlafc-linux-7.07.00-3-install]# ./qlinstall -u 

Example of console output reported by the driver removal: 

#*********************************************************# 


2 



# SANsurfer Driver for Linux Un-installation # 

#*********************************************************# 

Going to unload QLogic driver.... 

Unloaded module qla2300_conf 

Uninstall of rpm version v7.07.00-1 beginning.... 

Removing installation changes from /etc/modules.conf.... 


depmod... 

Creating ramdisk 

mkinitrd...No module qla2300 found for kernel 2.4.21-37.ELsmp, 

aborting. 

(bad exit status)/sbin/mkinitrd -f /boot/initrd-2.4.21-37.ELsmp.img 

2.4.21-37.ELsmp failed to execute 

Ramdisk creation failed 

Please restore backed up files from /usr/src/qlogic/v7.07.00-1/backup 

Removing QLogic HBA API library... 

#*********************************************************# 

# UN-INSTALLATION SUCCESSFUL!! # 

#*********************************************************# 


necessary for the server to boot and that a ramdisk has been 

created. 

If additional modifications to /etc/modules.conf are necessary, 

create a new ramdisk manually: 


cd /boot 

mkinitrd initrd-$1.img $1 


Example: 

cd /boot 

mkinitrd initrd-2.4.21-37.ELsmp.img 2.4.21-27.37.ELsmp 


cd /boot 

mkinitrd -i initrd-$1 -k vmlinuz-$1 





2 

Example: 

cd /boot 




2 



QLogic v7.x-Series Driver Parameters 

The QLogic driver contains a number of parameters that may be 

modified to perform failover functionality or to enhance performance. 

The QLogic and EMC recommended values are in the table 

below 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. 

Please keep in mind that these are merely guidelines as each 

environment differs. 

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 the following: 0 = disabled; 1 = enabled 

Table 2-2 

QLogic v7.x-Series Driver Parameters 

Parameters 

QLogic Default Values 

EMC Default 

Recommendations 

ql2xopts 

General Driver Parameters: 

ql2xfailover 0 0 

ql2xmaxqdepth 32 32 

ql2xmaxsectors 512 512 

ql2xmaxsgs 32 32 

ql2xlogintimeout 20 seconds 20 seconds 

qlport_down_retry 

ql2xretrycount 

0 (uses value specified in 

NVRAM) 

20 (standard mode)/30 

(failover mode) 

0 (uses value specified in 

NVRAM) 

20 (standard mode) 




2 

Table 2-2 

QLogic v7.x-Series Driver Parameters (continued) 

Parameters 




max_srbs 4096 4096 

displayConfig 1 1 

ql2xintrdelaytimer 3 3 

retry_gnnft 10 10 

ConfigRequired 0 0 

Bind 

ql2xsuspendcount 

0 (by Portname)/1 (by 

PortID) 

10 6-second suspend 

iterations 

0 (by Portname) 

10 6-second suspend 

iterations 

ql2xdevflag 0 0 

qfull_retry_count 16 retries 16 retries 

qfull_retry_delay 2 seconds 2 seconds 

extended_error_logging 0 0 

ql2xplogiabsentdevice 0 (no PLOGI) 0 (no PLOGI) 

ql2xfdmienable 0 (no FDMI) 0 (no FDMI) 

qlogin_retry_count 0 0 

ql2xioctltimeout 66 66 

ql2xprocessnotready 1 1 

ql2xuseextopts 0 0 

Failover-Specific Parameters: 

MaxPathsPerDevice 8 8 

MaxRetriesPerPath 3 3 

MaxRetriesPerIo (MaxRetriesPerPath * 

MaxPathsPerDevice) + 1 

(MaxRetriesPerPath * 

MaxPathsPerDevice) + 1 

QLogic v7.x-Series Driver Parameters 2-45

2 



Table 2-2 

QLogic v7.x-Series Driver Parameters (continued) 

Parameters 




Description of QLogic v7.x-Series Driver Parameters 

When attaching to CLARiiON and Symmetrix storage systems, EMC 

recommends that the ConfigRequired and ql2xfailover 

parameters be set to zero. 

General Driver Parameters: 

◆ ql2xopts: string that defines additional driver options and 

persistent binding info. 

◆ 

qlFailoverNotifyType 0 0 

recoveryTime 10 seconds 10 seconds 

failbackTime 5 seconds 5 seconds 

ql2xfailover: determines whether the failover functionality is 

disabled or enabled. 

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 HBA. 




2 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

displayConfig: defines whether to display the current driver 

configuration. If 1, then the configuration used in 

/etc/modules.conf is displayed. 

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 ql2xopts parameter are presented to the OS. 

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 NOT_READY status. 

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. 

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_READY’s. 

ql2xuseextopts: defines whether the driver will use the 

extended options saved in the module object itself, even if a string 

is defined via ql2xopts. 


2 



Failover-Specific Parameters: 

◆ MaxPathsPerDevice: defines the maximum number of paths to a 

device. 

◆ 

◆ 

◆ 

◆ 

◆ 

MaxRetriesPerPath: defines the number of retries to perform on 

the current path before failing over to the next path in the list. 

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 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 ConfigRequired=0 ql2xfailover=0 

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: 


3. Add the options line for the appropriate driver settings. 

options qla2300 ConfigRequired=0 ql2xfailover=0 




2 

Example: 


alias eth0 eepro100 

alias scsi_hostadapter cpqarray 

alias scsi_hostadapter1 cpqarray 




options qla2300 ConfigRequired=0 ql2xfailover=0 ql2xmaxqdepth=64 

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 mkinitrd command: 


cd /boot 



Example: 

cd /boot 

mkinitrd initrd-2.4.21-37.ELsmp.img 2.4.21-37.ELsmp 


cd /boot 

mkinitrd –i initrd-$1 -k vmlinuz-$1 


Example: 

cd /boot 




2 



Enabling Persistent Binding for the QLogic Linux Driver 

This section provides the instructions for enabling persistent binding 

for the QLogic Linux driver. 

In a fabric environment, EMC recommends, but does not require, 

enabling persistent binding. Without a persistent binding mechanism, 

the host cannot maintain a persistent logical routing of communication 

from a storage devices object across the fabric to an EMC 

storage array volume. If the physical configuration of the switch is 

changed (for example, cables are swapped or the host is rebooted), 

the logical route becomes inconsistent, which could cause possible 

data corruption. 

Please note that the persistent binding mechanism in the QLogic driver is 

target-based only, no LUN-based. 

Using SANsurfer to Enable Persistent Binding 

To use SANsurfer to enable persistent binding: 

1. Load the QLogic driver on the system. 

2. Use lsmod to verify that the driver is loaded: 

/opt/QLogic_Corporation/SANsurfer/SANsurfer & 

3. Log into the GUI. 

4. Start SANsurfer. 




2 

5. After SANsurfer is started, select localhost from the pull-down 

menu in the Connect to Host dialog, and click Connect, as shown 

in Figure 2-1. 

Figure 2-1 

SANsurfer, Connect to Host Dialog Box 

Enabling Persistent Binding for the QLogic Linux Driver 2-51

2 



The HBAs in the local system are displayed, as shown in 

Figure 2-2. 

Figure 2-2 

SANsurfer, HBA Port Information 




2 

6. Select the port by double clicking and information is provided, as 

shown in Figure 2-2. 

Figure 2-3 

SANsurfer, HBA Port Connection Settings 

Enabling Persistent Binding for the QLogic Linux Driver 2-53

2 



7. To enable persistent binding, select the Target Persistent Binding 

option to get the dialog as shown in Figure 2-4. 

Figure 2-4 

SANsurfer, Target Persistent Binding 

Installing and Configuring the HBA and Driver 




2 

Additional Notes 

This section contains the following: 

◆ 

Linux Device-Naming Convention 

◆ Device Reconfiguration: Procedures on page 2-58 

◆ Device Reconfiguration: Device Numbering on page 2-61 

◆ HPQ Server-Specific Note on page 2-62 

◆ (CLARiiON Only) Required /etc/modules.conf Edit for RHEL 2.1, 

RHEL 3.0, and SLES 8.0 Default Modular Kernels on page 2-63 

Linux Device-Naming Convention 

The four high-level device drivers in Linux are: 

sd — Direct access (disks) 

sg — SCSI generic interface 

sr — Data CD-ROMs 

st — Tapes 

The sg driver is a character-based device while the other three drivers 

are block-based devices. The sg driver is used primarily for scanners, 

CD writers, and printers. The sg device files are dynamically mapped 

to SCSI IDs/LUNs on the SCSI bus starting with the first SCSI controller. 

Block Device File Names 

A native device file name for block devices takes the following form: 

/dev/sdln 

where: 

◆ 

l is a letter denoting the physical drive.nstalling and Conf 

◆ n is a number denoting the partition on that physical drive. 

Usually, the partition number is not included when referring to the 

entire drive. 

Following this format, the disk device file names are as follows: 

/dev/sd[a-d][a-z][1-15] 

Additional Notes 2-55

2 



Linux kernel reserves 16 major numbers for SCSI devices. Each major 

number can have zero to 255 minor numbers. These minor numbers 

represent the partitions for a SCSI device. The Linux v2.4.x kernel 

supports up to 15 partitions per disk device. Partitions 1 through 4 

are the primary partitions, while partitions 5 and greater are the logical 

or extended partitions. These limitations are specific to the Intel 

platform. By default, slices are not used in Linux. 

Therefore, the product of 16 major numbers and 16 minor numbers 

yields 256 SCSI devices. As a result, the v2.4.x kernel is able to scan 

logical devices ranging from 0 through 255. 

The maximum of 256 SCSI devices includes non-EMC storage array 

devices, such as local SCSI disks. 

Red Hat Distributions 

SuSE Distributions 

By default, RHEL 2.1 and RHEL 3.0 distributions can scan LUN numbers 

from 0 through 255. However, only the first 128 SCSI devices discovered 

by the system are mapped to an sd device. Any gaps in 

devices presented to the system do not result in gaps in the sd device 

names. 

The first device can start at a non-zero LUN: 

Examples: 

◆ If you have allocated devices 0 through 255 to the Linux host, it 

can scan up to 255; however, only the first 128 devices (0 through 

127) are usable and accessible by the host. 

◆ 

If you have LUNs 128 through 255 assigned to a Linux host, you 

can scan through and use all of them. 

◆ If you have LUNs over 256 exported to a Linux host, the Linux 

hosts neither sees nor can access those devices with an address 

over 256. 

In total, a v2.4.x based Red Hat host could support disk devices from 

/dev/sda through /dev/sddx. 

By default, SuSE SLES 8 supports up to 256 devices as it reserves 16 

major numbers for SCSI devices. 

Each major number is allocated 0 to 255 minor numbers that are used 

to denote the partitions for a SCSI device. The product of 16 major 

numbers and 16 minor numbers yields up to 256 SCSI devices. 




2 

As a result, the kernel is able to scan logical devices ranging from 0 

through 255. The disk device file names are reported as /dev/sda 

through /dev/sdiu. 

Therefore, if LUNs 0 through 255 have been allocated to a SLES 8 

host, the SCSI stack scans and uses all 256 logical units. However, if 

logical units over 256 are presented to the SLES 8 host, the host can 

neither see nor access the devices with an address greater than 256. 

PowerPath Examples 

If EMC PowerPath® is installed, keep in mind that there is a limitation 

of 128 or 256 SCSI devices total per system, not per adapter. 

◆ 

◆ 

Example without PowerPath and 128 Devices 

If there are two HBAs or a dual channel HBA in the system and 

both ports/HBAs are going to be configured to see and access 

devices, the 128 devices must be divided between the two HBAs. 

For example, 64 devices would be allocated to each HBA. If 128 

devices were allocated to the first HBA, the second HBA would 

not be able to access any devices. The limitation of 128 SCSI 

devices is in the Linux SCSI subsystem and is per system, not per 

adapter. 

Example with PowerPath and 128 Devices 

Keep in mind that if 128 LUNs are presented to the Linux host via 

one HBA, then only that one HBA can see and access devices. 

In the case of PowerPath, if there are eight HBAs in a server and 

two paths to the storage per HBA, only eight devices may be 

allocated to the host: 

128 LUNs/ (8 HBAs * 2 paths) = 8 devices 

Character Device File Names 

The corresponding character device file names take the following 

form: 

/dev/sgN 

where N begins with zero and increments by one. 

The use of the alphabetic sg device file names /dev/sg[a-d][a-z] 

are now deprecated and are used as links to the sg numeric device 

filenames. 


2 



Current versions of Solutions Enabler and, therefore, inquiry require 

the existence of the deprecated alphabetic SCSI generic device file 

names. 

Not all Linux distributions provide corresponding sg device file 

names for the sd device file names. Additionally, because the alphabetic 

sg device file names are deprecated, some distributions, such as 

SuSE SLES 8 do not provide them at all. For example, on Red Hat 

releases there are generally 128 sd device file names, 16 sg numeric 

file names, and 16 sg alphabetic file names. On SuSE SLES 8, there are 

256 sd device file names, 64 sg numeric file names, and no sg alphabetic 

device file names. 

In order for the inquiry command to complete, the sg alphabetic file 

names must exist and must be linked to the sg numeric file names. 

The mknod command should be used to create any sg numeric file 

names needed and then use the ln command to create the link from 

the sg numeric to the sg alphabetic device file names. 

The Linux kernel assigns minor SCSI device numbers dynamically by 

assigning them only to devices that are actually connected to the host 

in the order of their SCSI IDs. This means that connecting an external 

SCSI device can change the minor numbers of all the internal SCSI 

devices with a higher SCSI ID. 

Device Reconfiguration: Procedures 

The Linux v2.4.x kernel lacks a command built into the kernel that 

allows for a dynamic SCSI channel reconfiguration like drvconfig or 

ioscan. 

The three methods of rescanning the SCSI bus in a Linux host are: 

◆ 

◆ 

◆ 

Rebooting the host. 

Unloading and reloading the modular QLogic driver. 

Echoing the /proc filesystem. 

Rebooting the Host 

Rebooting the host reliably detects newly added devices. The host 

may be rebooted after all I/O has stopped, whether the driver is 

modular or statically linked. 




2 

Unloading and Reloading the Modular QLogic Driver 

Depending upon the hardware configuration, it is possible to unload 

and reload the modular QLogic driver. This driver removal from and 

reinsertion into the kernel causes a scan of the SCSI bus and causes 

the driver to detect any newly added device(s). 

If the driver is to be removed from and then reinserted into the 

kernel, perform the following before removing the driver: 

◆ 

◆ 

◆ 

Stop all I/O. 

Unmount all filesystems attached to the QLogic driver. 

If the Navisphere Agent is installed and enabled on the host, stop 

the Navisphere Agent service. 




or 


◆ 




commands: 


or 


◆ 





commands: 


or 



2 



The modprobe command is a wrapper or an extension to the insmod 

and rmmod commands. The modprobe command uses and maintains a 

set of files that describe all the modules that are available for the 

current kernel in /lib/modules. 

The modprobe command may be used to load and unload an entire 

set of modules. (A set of modules can be a single module or a stack of 

dependent modules.) The modprobe command automatically loads 

all of the dependent modules needed in a module stack based on the 

information in modules.dep. 

EMC recommends using modprobe to load and unload the QLogic 

modular driver. 

The loading of the module is accomplished with either modprobe or 

insmod. These commands are used to install loadable kernel modules 

into a running kernel. The commands attempt to link a module into 

the running kernel by resolving the symbols from the kernel’s 

exported symbol table. 

The unloading of the module can be accomplished with the 

modprobe (with the -r switch) command or the rmmod command. 

These commands are used to unload the loadable modules from the 

running kernel if they are not in use and if other modules are not 

dependent upon them. 

Echoing the /proc Filesystem 

Echoing the /proc filesystem may be used to add and/or remove 

single SCSI devices. To add a device, the host, channel, target ID and 

LUN numbers for the device must be identified and added to the 

/proc/scsi/scsi file. 

If PowerPath is being used on this host, you must stop the PowerPath 

service must be stopped prior to echoing the/proc filesystem. To do 

this, type: 


After the PowerPath service has been stopped, the devices may be 

added to or removed from the system by echoing the /proc 

filesystem. 

There have been cases where echoing the /proc filesystem have not 

produced reliable results. Rebooting the host or unloading and reloading the 

Fibre Channel driver produce the most consistent results. 




2 

The command to be run follows this format: 

where: 

echo "scsi add-single-device 0 1 2 3" > /proc/scsi/scsi 

0 is the host ID. 

1 is the channel ID. 

2 is the target ID. 

3 is the LUN. 

This command adds the new device to the /proc/scsi/scsi file. 

If one does not already exist, a device file name may need to be created 

for the newly added device in the /dev directory. 

To remove a device, use the appropriate host, channel, target ID, and 

LUN numbers and issue a command similar to the following: 

echo "scsi remove-single-device 0 1 2 3" > /proc/scsi/scsi 

where: 

0 is the host ID. 

1 is the channel ID. 

2 is the target ID. 

3 is the LUN. 

Device Reconfiguration: Device Numbering 

In the Linux v2.4.x kernel, SCSI addresses are not used in the device 

file names as they are in other types of UNIX (Sun, SGI, HP-UX, and 

BSD, for example). Block device filenames take the form /dev/sdln, 

where l is the letter denoting the physical drive and n is the number 

denoting the partition on that physical drive. Disk device file names 

and major and minor numbers are assigned dynamically at boot time 

or device loading time in the order of discovery. 

Depending upon the hardware configuration, if a device is added 

and the system rebooted, the device numbering might change, possibly 

rendering the host's mount table inaccurate. For the most consistent 

results and to reduce the possibility of mount table inaccuracies, 

new devices should be appended (if possible) to the list of already 

attached devices. For example, if the host contains multiple HBAs, it 


2 



is best to append the new device to the last HBA and to the end of the 

device list attached to that HBA. This would eliminate the need to 

alter the preexisting entries in the mount table, since the new device 

could be appended to that as well. 

If a new device were added to the first out of two HBAs and the system 

rebooted, the device file names shift by one number and the 

mount table entries shift by one device file name. If there is only one 

HBA, the new device can more easily be appended to the list of the 

regularly attached devices and the mount table altered accordingly. 

HPQ Server-Specific Note 

When using HPQ systems, it is highly recommended that the HPQ 

SmartStart CD be run to configure the server prior to installing the 

Linux operating system. The SmartStart CD is shipped by HPQ with 

their systems, and is a bootable CD that is used to configure the 

server BIOS. If another operating system is selected other than Linux, 

there may be problems installing the operating system or using the 

drivers installed in the kernel. Follow these steps to select Linux as 

the primary operating system from the HPQ SmartStart CD: 

1. Boot the HPQ server using the SmartStart CD. 

2. Select the System Configuration Utility. 

3. After the System Configuration Utility has started, a window 

titled Steps in Configuring Your Computer appears, with the 

following options listed: 

Step 1: Important System Configuration Information 

Step 2: Add or Remove Boards 

Step 3: View or Edit Details 

Step 4: Examine Switches or Print Report 

Step 5: Save and Exit 

Select Step 3: View or Edit Details. 

4. In the new window, select Primary Operating System (the first 

item in the list); then select Unix from the list of possibilities. 

5. A list of UNIXes is displayed; select Linux from this list. Select 

Enter; then select Done. 

6. The console returns to the Steps in Configuring Your Computer 

window. Select Step 5: Save and Exit. 




2 

7. When prompted, select Save the configuration and restart the 

computer. 

8. When prompted again to save your configuration and reboot, 

press ENTER to reboot the system and to proceed with 

installation of the Linux operating system. 

(CLARiiON Only) Required /etc/modules.conf Edit for RHEL 2.1, RHEL 3.0, and 

SLES 8.0 Default Modular Kernels 

When a Linux host is attached to both SPs in a CLARiiON storage 

array, the driver will report a disconnected LUN 0 on SPB and a 

failure to read the capacity of the device. The Navisphere Host Agent 

requires that disconnected LUN 0 be reported properly.-39Installing and 

A device file name is allocated to the disconnected LUN 0 in the /dev 

filesystem, but the device cannot be mounted, partitioned, or otherwise 

accessed. 

An example of a disconnected LUN 0 being reported in 

/var/log/messages: 

Red Hat and SuSE have added a parameter to the SCSI stack 

(scsi_scan.c file) to allow access to devices marked as offline. 

For RHEL, the max_scsi_luns parameter must be enabled in 

/etc/modules.conf. In the default Red Hat kernels, 

CONFIG_SCSI_MULTI_LUN is disabled. As a result, if the target 0 LUN 

0 disappears from the storage group and the host is rebooted or the 

driver unloaded and reloaded, the host will see only the ghost LUNs 


2 



(with ArrayCommPath disabled) or the LUNZ (with 

ArrayCommPath enabled). 

By default, the SuSE SLES 8 kernel has enabled the 

CONFIG_SCSI_MULTI_LUN parameter. Therefore, there is no need to 

add the max_scsi_luns parameter to the /etc/modules.conf file 

on SLES 8 SP3. 

A kernel compilation is not required when appending the 

scsi_allow_ghost_devices parameter to /etc/modules.conf. 

Follow these steps to enable the new parameter in 

/etc/modules.conf: 

1. Change to the appropriate directory and edit the file: 


2. Append the following line to the file: 

• For Red Hat distributions use: 


Example: 



alias scsi_hostadapter1 lpfc 




• For SuSE distributions use: 

options scsi_mod scsi_allow_ghost_devices=1 

Example: 







options lpfc lpfc_topology=0x02 lpfc_automap=0 lpfc_scan_down=0 

lpfc_fcp_bind_WWPN=50060160006000ed:lpfc0t1,50060168006000ed:lpfc0 

t2,5006016006000ed:lpfc1t1,50060168006000ed:lpfc1t2 




2 


• For Red Hat distributions, use: 

cd /boot 

cp initrd-$1.img initrd-$1.img.orig 


where $1 is the currently running v2.4.x kernel version. 

Example: 

cd /boot 

cp initrd-2.4.21-15.0.4.ELsmp.img initrd-2.4.21-15.0.4.ELsmp.img.orig 

mkinitrd –v initrd-2.4.21-15.0.4.ELsmp.img 2.4.21-15.0.4.ELsmp 

• For SuSE distributions use: 

cd /boot 

cp initrd-$1 initrd-$1.orig 

mkinitrd –k vmlinuz-$1 –i initrd-$1 

Example: 

cd /boot 

cp initrd-2.4.21-266 initrd-2.4.21-266.orig 

mkinitrd –k vmlinuz-2.4.21-266 –i initrd-2.4.21-266 


(CLARiiON Only) Linux Navisphere Agent Limitation with fdisk on CLARiiON 

There is known issue with the Linux Navisphere Agent in which the 

Navisphere Agent does not close the sd devices before becoming a 

daemon and, as a result, the devices remain open. This may cause 

issues when attempting to access devices. 

For example, if the Navisphere Agent service is left running and 

someone runs fdisk to create new partitions on CLARiiON storage 

array devices, any attempt to make a new filesystem with mkfs on 

the newly created partition(s) will fail. 

An example of a warning issued when fdisk is run is: 

WARNING: Re-reading the partition table failed with 

error 16. Device or resource busy. The kernel still 

uses the old table. The new table will be used at 

next reboot. 


2 



Disabling the 

Navisphere Agent 

Service 

If, after receiving the above warning, the user attempts to run mkfs 

on a newly created filesystem, mkfs will also fail with an error 

similar to the following: 

mke2fs.ext2: No such device or address while trying to 

determine filesystem size 

This problem can be resolved in one of these ways (described in 

detail following the list): 

◆ 

◆ 

◆ 

◆ 

Disable the Navisphere Agent Service. 

Issue a Naviagent stop command:v 

• On RHEL, issue the command: 

service Naviagent stop 

• On SLES 8, issue the command: 

/etc/init.d/Naviagent stop 

Remove the Navisphere Agent RPM. 

Rescan the SCSI bus. 

After the Navisphere Agent registers the host with the CLARiiON 

array, the service can be disabled so that it does not start after 

rebooting. This may be done manually or by using the setup tool. 

◆ 

Manually: 

[root@l82bi180 root]# chkconfig --list Naviagent 

Naviagent 0:off 1:off 2:off 3:on 4:on 5:on 6:off 

[root@l82bi180 root]# chkconfig --level 345 Naviagent off 

[root@l82bi180 root]# chkconfig --list Naviagent 

Naviagent 0:off 1:off 2:off 3:off 4:off 5:off 6:off 

[root@l82bi180 root]# reboot 

◆ 

Using the curses-based setup tool on RHEL: 

a. At the command line, type setup and press ENTER. 




2 

The following curses-based menu appears: 

2-3 

b. Select Systems services option and scroll down to the 

Navisphere Agent service. 

c. Use the space bar to deselect the Navisphere Agent service. 

d. Quit out of the tool and reboot your host. 

2 

Issuing a Naviagent 

stop Command 

On RHEL, you can stop the Navisphere Agent service with either of the two 

following commands and then retype the fdisk/mkfs commands: 

service Naviagent stop 

/etc/rc.d/init.d/Naviagent stop x 

On SLES 8, you can stop the Navisphere Agent service with the 

following command and then retype the fdisk/mkfs commands: 

/etc/init.d/Naviagent stop 

Removing the 

Navisphere Agent 

RPM 

The Navisphere Agent RPM may be removed from the system 

entirely after it is used for the initial setup of the host on the 

CLARiiON array. 

Example: 

rpm -ev Naviagent-6.6.0.3.8-1 


2 



Rescanning the SCSI 

Bus 

The SCSI bus may be rescanned with a system reboot, or with a 

removal and reinsertion of the modular driver. (Refer to Device 

Reconfiguration: Procedures on page 2-58.) In either case, all I/O must 

be stopped and all other mounted file systems must be unmounted 

before rebooting or removing the modular driver. 

If the SCSI bus is not rescanned or the Navisphere Agent service not 

stopped, attempts to make a new filesystem with mkfs on the newly 

created partition will fail. 

(CLARiiON only) Linux Navisphere Agent Limitation with VERITAS Volume Manager 

v3.2 on CLARiiON 

The Linux Navisphere Agent holds open the devices to be used by 

VERITAS Volume Manager v3.2 during the initialization and 

installation of the CLARiiON devices. When this occurs, the message 

Devices busy or in use is reported. 

The issue with the Navisphere Agent and VERITAS Volume Manager 

v3.2 can occur on initialization and installation of the VxVM, as well 

as on subsequent reboots.lling and Configuring the HBA and Driver 

Here is an example of the error reported during vxinstall: 

If the devices were successfully partitioned during the installation, 

you might also run into an issue after subsequent reboots where the 

VxVM's rootdg becomes unavailable. You will receive errors when 

trying to issue VxVM commands; this is a result of the configuration 

daemon (vxconfigd) not running, and can happen if the Navisphere 

host agent is running. 




2 

There are two ways to resolve this problem: 

◆ 

Remove the Navisphere Agent RPM from the system entirely after it is 

used for the initial setup of the host on the CLARiiON array. 

Example: 

rpm -ev Naviagent-6.6.0.3.8-1 

◆ 

Install the Navisphere Agent, but stop the service from starting at 

boot time. The service can be stopped by using the setup tool as 

described under Disabling the Navisphere Agent Service on page 

2-35. 

(CLARiiON only) Linux Navisphere Agent Requirement for RHEL 2.1 Intel Itanium 

Systems 

The Navisphere Agent/CLI RPM for Linux is a 32-bit executable. 

Therefore, for RHEL 2.1 Itanium-based systems, the 

x86-compat-libs RPM package must be installed in order for the 

Linux Navisphere Agent/CLI RPM to install properly. 

(CLARiiON Only) Linux Navisphere Agent Requirement for RHEL 3.0 Intel Itanium 

Systems 

The Navisphere Agent/CLI RPM is supported on RHEL 3.0 IA64 

hosts. However, glibc-2.3.2-95.27 or later must be installed on the 

system in order for the Navisphere Agent/CLI RPM pkacage to 

install successfully on RHEL 3.0 IA64. 

Note that the x86-compat-libs RPM package that was required for 

RHEL 2.1 [IA64] is not available or necessary for RHEL 3.0 [IA64]. 

Refer to the following RPM query and installation output from a 

RHEL 3.0 [IA64] host: 

[root@l82bi021 /]# rpm -q compat-glibc 

package compat-glibc is not installed 

[root@l82bi021 /]# rpm -q x86-compat-libs 

package x86-compat-libs is not installed 

[root@l82bi021 /]# rpm -q compat-glibc.7x 

package compat-glibc.7x is not installed 

[root@l82bi021 /]# rpm -qa | grep compat 

compat-libstdc++-7.3-2.96.128 

[root@l82bi021 /]# rpm -qa | grep glibc 

glibc-2.3.2-95.30 

glibc-devel-2.3.2-95.30 

glibc-2.3.2-95.30 


2 



glibc-headers-2.3.2-95.30 

glibc-profile-2.3.2-95.30 

glibc-common-2.3.2-95.30 

glibc-kernheaders-2.4-8.34.1 

glibc-utils-2.3.2-95.30 

[root@l82bi021 /]# ls /emul 

ia32-linux ia32-Linux 

[root@l82bi021 /]# rpm -ivh Naviagentcli-6.7.0.4.7-1.i386.rpm 

Preparing... ########################################### [100%] 

1:Naviagentcli ########################################### [100%] 

[root@l82bi021 /]# rpm -ivh Navisphere Agentcli-6.16.0.4.63-1.i386.rpm 

Preparing... ########################################### [100%] 

1:Naviagentcli ########################################### [100%] 




2 

Incorporating EMC Fibre Channel 

After the EMC storage array has devices assigned with device 

addresses and the directors have been switched on line, the host can 

see all the target EMC devices assigned to that host interface. Devices 

are presented to the host in the same manner as devices accessed 

through a standard SCSI interface. 

Incorporating EMC Fibre Channel 2-71

2 





3 

Configuring a Boot 

Device on the EMC 

Storage Array 

EMC supports booting Linux from an EMC storage array through an 

EMC-qualified QLogic Fibre Channel HBA. (Refer to the EMC 

Support Matrix for specific HBAs, BIOS revisions, and drivers.) 

◆ Cautions and Restrictions for Booting from an EMC Storage Array 

3-2 

◆ Common Limitations.........................................................................3-4 

◆ Configuring a Symmetrix Boot Device ...........................................3-7 

◆ Configuring a CLARiiON Boot Device......................................... 3-11 

◆ Installing Supported RHEL 2.1, RHEL 3.0, and SLES 8 Releases 

onto the EMC Boot Device with the QLogic v6.x-Series and 

v7.x-Series Drivers ...........................................................................3-15 

◆ Upgrading the Kernel......................................................................3-18 

Configuring a Boot 

Device on the EMC 

Storage Aray 

3 

3-Configuring a Boot Device on the EMC Storage Aray 

Configuring a Boot Device on the EMC Storage Array 3-1

3 


Cautions and Restrictions for Booting from an EMC Storage Array 

! 

CAUTION 

If Linux loses connectivity long enough, the disks disappear from 

the system. To prevent further data from being lost in a situation 

like this, EMC recommends that the error behavior be changed 

from continue to remount read-only. To make this change, consult 

the manpage for tune2fs. A hard reboot is required to bring the 

system back to a usable state. 

! 

CAUTION 

The host should be configured with enough memory to eliminate 

the need for a swap partition. EMC cannot recommend an amount 

of memory as this varies greatly depending upon the environment. 

EMC recommends shutting down the host server during any 

maintenance procedures that could render the boot disk unavailable 

to the host. 

Any of these events have the potential to crash a system booting from 

an EMC storage array. 

CLARiiON-Specific Cautions and Restrictions 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

Lost connection to CLARiiON storage array (pulled or damaged 

cable connection). 

CLARiiON service and upgrade procedures, such as on-line 

CLARiiON FLARE upgrades and/or configuration changes. 

CLARiiON SP failures, including failed lasers. 

CLARiiON storage array power failure. 

Storage area network failures, such as failures in Fibre Channel 

switches, switch components, or switch power. 

Storage area network service and upgrade procedures, such as 

firmware upgrades or hardware replacements. 

Trespass of a CLARiiON LUN from one SP to the other. 



3 

Symmetrix-Specific Cautions and Restrictions 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

3 

Lost connection to Symmetrix system (pulled or damaged cable 

connection). 

Symmetrix service and upgrade procedures, such as on-line 

Symmetrix microcode upgrades and/or configuration changes. 

Symmetrix director failures, including failed lasers. 

Symmetrix system power failure. 

Storage area network service and upgrade procedures, such as 

firmware upgrades or hardware replacements. 

Storage area network failures, such as failures in Fibre Channel 

switches, switch components, or switch power. 

Cautions and Restrictions for Booting from an EMC Storage Array 3-3

3 


Common Limitations 

Boot configurations must not deviate from the following limitations 

established by EMC: 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

◆ 

The EMC Storage device must have enough disk space to hold the 

Linux operating system. 

A maximum of 32 volumes may be configured on the EMC 

storage array port that will be used to boot Linux. 

EMC recommends that you install, rather than upgrade, the 

kernel-source and kernel UP, SMP, and Hugemem RPMs. 

PowerPath is not supported on Linux v2.4.x hosts booting from 


Veritas VxVM/DMP is not supported on Linux v2.4.x hosts 

booting from EMC storage arrays. 

Hosts booting from an EMC storage array are limited to the use of 

one HBA. 

The Symmetrix or 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 must be mapped as /dev/sda by the Linux operating 

system for the boot to succeed from the device. 

Note that this includes the following cases: 

• Volume Logix database device when using Volume Logix in a 

Symmetrix environment — The installer will fail to write the 

MBR to this device, as it is write-protected. 

– To force the installer to avoid an attempt to write to this 

device, EMC recommends masking the LUN. The 

administrative host must first initialize the Volume Logix 

database. The LUN may then be masked by modifying the 

active configuration file to enable the ‘fba flag2’ to restrict 

access to the Volume Logix database. 

– An alternative to masking the VCM DB is to map the 

Volume Logix database device so that it is the highest LUN 

presented to the host. However, please be aware that the 

LUN number should not be higher than 254 (FE) if it is to 

be used by EMC Solutions Enabler or EMC ControlCenter ® 

running on a Microsoft Windows host. 

The EMC-recommended method is to use LUN masking. 



3 

◆ 

◆ 

◆ 

• CLARiiON ghost LUN — If the LUN 0 presented to a SCSI 

path is not owned by the SP attached to that path, a 

disconnected LUN 0 (ghost LUN) will be presented. The ghost 

LUN is not write-enabled so that the MBR cannot be written to 

it. Always ensure that the boot LUN is owned by the correct 

SP and does not trespass at any time; trespass of the boot LUN 

would result in a system crash. 

When attaching the Linux host to an EMC storage array, use the 

adapter in the lowest-numbered PCI slot in the server. To keep the 

configuration and installation simple, it is recommended that 

only that single HBA be cabled to the arrays. Ensure that the boot 

BIOS has been applied to the HBA. 

The installer installs the boot block onto only the first disk it sees. 

This includes SCSI and IDE drives in the server. If only EMC 

storage array devices attached to the system, the boot BIOS 

should be set to the first LUN the HBA sees. If there are other 

local disks in the system and depending on how Linux discovers 

the controllers and drives, the boot block may need to be on a 

local disk. 

Until Linux is fully installed, the host must be connected only to 

the EMC storage array onto which the operating system will be 

loaded. After the installation is complete and the host rebooted, 

the host may be connected to other storage arrays. 

CLARiiON-Specific Limitations 

◆ 

Prior to the installation on a CLARiiON LUN, the Linux host 

must have been manually registered on the array and assigned to 

a Storage Group. At least one LUN must be bound to the host’s 

Storage Group and owned by the SP connected to the HBA being 

used for the fabric boot. The CLARiiON storage array SP shouldb 

be zoned to the lowest-numbered channel in the server and the 

lowest-numbered path to the boot LUN must be the active path. 

◆ It is required that the boot LUN be assigned Host LUN ID 0. 

◆ 

During the installation procedure, it is recommended, but not 

required, that only one LUN be assigned to the Storage Group for 

ease of use. Once the installation has completed, additional LUNs 

may be added to the Storage Group. 

Common Limitations 3-5

3 


◆ 

Booting from the SAN requires the use of a Navisphere 

Management station with the Navisphere Manager GUI or CLI 

installed. The station must be separate from the boot server, but 

networked to the CLARiiON storage array. 

Symmetrix-Specific Limitations 

◆ 

◆ 

◆ 

When attached to a Symmetrix, the physical-to-logical split must 

be 1:8 or less (1:7, 1:6, etc.). EMC supports the use of any LUN 

from 00 through FF as a boot disk. 

Prior to the installation on a Symmetrix LUN, the Linux host HBA 

must have successfully logged into the array. Using Solutions 

Enabler from another system, assign a minimum of one LUN to 

the host. 

During the installation procedure, it is recommended, but not 

required, that only one LUN be assigned to the host for ease of 

use. Once the installation has completed, additional LUNs may 

be assigned to the host. 



3 

Configuring a Symmetrix Boot Device 

This section describes how to install an EMC-qualified version of 

Linux onto an EMC Symmetrix storage system connected to an 

Intel-based x86 and x86_64 class systems and AMD Opteron-based 

x86_64 class systems. 

Preparing the Symmetrix Storage System 

Note the following when preparing the Symmetrix system: 

◆ 

◆ 

◆ 

It is recommended that Volume Logix be enabled on the 

Symmetrix system for LUN masking purposes. 

During the installation procedure, only one LUN should be 

allocated to the host, so that the boot LUN may be identified 

easily. After the OS installation, additional LUNs may be 

allocated. 

Create a zone that includes the WWPN of the HBA to be used and 

one FA port. Add the newly-created zone to the zone 

configuration in the fabric and enable the zone configuration. 

Preparing the Host 

Note the following when preparing the host: 

◆ 

◆ 

◆ 

◆ 


one FA port. Add the newly-created zone to the zone 


The PCI Fibre Channel HBA must be the lowest-numbered PCI 

slot in the server. For example, if there are three adapters in the 

system in slots 2, 4, and 5, connect the cable to the adapter in slot. 

Do not connect cables to other adapters until the installation is 

complete and the host rebooted. 

SCSI hard disks are allowed in SAN boot configurations. 

However, the BIOS for the disk's SCSI adapters must be disabled. 

Any SCSI disks attached to the host should be disconnected 

during the operating system installation. 

For servers with SCSI CD-ROM drives, ensure that the BIOS is 

enabled on the SCSI channel that includes the CD-ROM. Disable 

the BIOS on any other integrated SCSI channels. 

Configuring a Symmetrix Boot Device 3-7

3 


◆ 

◆ 

For servers with IDE CD-ROM drivers, disable the BIOS on the 

server's integrated SCSI adapter(s). The SCSI BIOS is not required 

to boot from the CD-ROM. 

Disable the BIOS on any other HBAs in the system other than the 

QLogic HBA designated for booting. 

Configuring the QLogic BIOS for SAN Boot 

After the BIOS is installed and enabled, it must be configured for use 

for booting from EMC Symmetrix storage arrays. 

In cases where the host is booting from an internal drive and is being 

converted to boot from the SAN, QLogic SANsurfer may be used to 

configure the BIOS for SAN boot. Refer to the complete 

documentation and the EMC-qualified versions of SANsurfer, 

available for download from the EMC-approved section of the 

QLogic website. 

If this is a new Symmetrix SAN boot configuration, the BIOS may be 

configured at boot time using the Flas!UTIL utility. The following 

procedure describes how to configure the BIOS using Flas!UTIL: 

1. Connect the Symmetrix Fibre Channel port to the adapter in the 

lowest-numbered PCI slot in the server. For example, if there are 

three adapters in the system in slots 2, 4, and 5, connect the cable 

to the adapter in slot 2. Do not connect cables to the other 

adapters at this time. 

2. Boot the server, and press CTRL-Q when the QLogic banner 

(shown below) appears. 

Different HBA models may display different banners. Be sure to select 

CTRL-Q for the HBA to be configured. 






The banner display corresponds to the BIOS revision pertinent to 

the HBAs currently installed. Refer to the EMC Support Matrix for 

specific HBAs and BIOS revisions. 



3 

3. After Fast!UTIL loads, the display depends on whether there are 

multiple QLogic HBAs installed: 


appears. 

• If there are multiple QLogic HBAs, a list of addresses occupied 

by those HBAs appears. Since the Symmetrix system is 

attached to the lowest-numbered PCI slot, select the first 

adapter from the list, and press ENTER. The Fast!UTIL Options 

menu then appears. 

4. From the Fast!UTIL Options menu, select Configuration Settings 


5. From the Configuration Settings menu, select Adapter Settings 


6. From the Host Adapter Settings menu, select Host Adapter 

BIOS and press ENTER to enable it if it is not already enabled. 

Refer to the Table 2-1 on page 2-6 for recommended settings. 

7. Press ESC to exit the Configuration Settings menu. 

8. From the Configuration Settings menu, select Selectable Boot 

Settings and press ENTER. 

9. From the Selectable Boot Settings menu, select Selectable Boot 

Device and press ENTER to enable this option if it is not already 

enabled. 

10. Select Current Boot Node Name and press ENTER. 

The adapter scans for attached storage devices, which will then 

appear on the screen. 

11. Select the Symmetrix port from which the system will boot. Its 

entry will be similar to the following: 

ID VENDOR PRODUCT REV NODE NAME Port ID 

12 EMC Symmetrix 5568 50060482BFD06C02 0000E4 

12. A list of LUNs appears in a new window. 

Select the LUN to be used as the boot device and press ENTER. 

Configuring a Symmetrix Boot Device 3-9

3 


On Symmetrix systems, you should select the LUN number of the first 

visible device to the selected Symmetrix port. 

13. Press ESC at the Selectable Boot Settings menu to return to the 

Configuration Settings menu. 

14. Press ESC at the Configuration Settings menu to return to the 

Options menu. 

15. Select Save Changes and press ENTER. 

16. Press ESC to exit Fast!UTIL. 




3 

Configuring a CLARiiON Boot Device 

This section describes how to install an EMC-qualified version of 

Linux onto an EMC CLARiiON storage array connected to an 

Intel-based x86 and x86_64 class systems and AMD Opteron-based 

x86_64 class systems. 

Preparing the CLARiiON Storage Array 

Note the following when preparing the CLARiiON array: 

◆ 

◆ 

◆ 

It is recommended that Access Logix be enabled on the 

CLARiiON array for LUN masking purposes. 

Boot device support requires a Navisphere Management station 

with Navisphere Manager GUI or CLI installed. The station must 

be separate from the server being installed and must be 

networked to the CLARiiON array. 

Before installing Linux onto a CLARiiON array, the array must 

have one bound LUN allocated to the Storage Group for the 

server being installed. The LUN must be owned by the SP 

connected to the boot HBA. 

◆ During the installation procedure, only one LUN should be in the 

boot Storage Group, so that the boot LUN may be identified 

easily. After the installation, additional LUNs may be added to 

the host's Storage Group. 

If LUNs need to be created, refer to the EMC Navisphere Manager 

documentation for the array type. 

Preparing the Host 

Note the following when preparing the host: 

◆ 

◆ 


one SP port. Add the newly-created zone to the zone 


EMC recommends using port 0 on the SP for consistency. 

Configuring a CLARiiON Boot Device 3-11

3 


◆ 

◆ 

◆ 

◆ 

◆ 

The PCI Fibre Channel HBA must be the lowest-numbered PCI 

slot in the server. For example, if there are three adapters in the 

system in slots 2, 4, and 5, connect the cable to the adapter in slot. 

Do not connect cables to other adapters until the installation is 

complete and the host rebooted. 

SCSI hard disks are allowed in SAN boot configurations. 

However, the BIOS for the disk's SCSI adapters must be disabled. 

Any SCSI disks attached to the host should be disconnected 

during the operating system installation. 

For servers with SCSI CD-ROM drives, ensure that the BIOS is 

enabled on the SCSI channel that includes the CD-ROM. Disable 

the BIOS on any other integrated SCSI channels. 

For servers with IDE CD-ROM drivers, disable the BIOS on the 

server's integrated SCSI adapter(s). The SCSI BIOS is not required 

to boot from the CD-ROM. 

Disable the BIOS on any other HBAs in the system other than the 

QLogic HBA designated for booting. 

Configuring the QLogic BIOS for SAN Boot 

After the BIOS is installed and enabled, it must be configured for use 

for booting from EMC CLARiiON storage arrays. 

In cases where the host is booting from an internal drive and is being 

converted to boot from the SAN, QLogic SANsurfer may be used to 

configure the BIOS for SAN boot. Refer to the complete 

documentation and the EMC-qualified versions of SANsurfer, 

available for download from the EMC-approved section of the 

QLogic website. 

If this is a new CLARiiON SAN configuration, the BIOS may be 

configured at boot time using the Flas!UTIL utility. The following 

procedure describes how to configure the BIOS using Flas!UTIL: 

1. Connect the CLARiiON SP Fibre Channel port to the adapter in 

the lowest-numbered PCI slot in the server. 

2. Boot the server, and press CTRL-Q when the QLogic banner 

(shown below) appears. 

Different HBA models may display different banners. Be sure to select 

CTRL-Q for the HBA to be configured. 



3 






The banner display corresponds to the BIOS revision pertinent to 

the HBAs currently installed. Refer to the EMC Support Matrix for 

specific HBAs and BIOS revisions. 

3. After Fast!UTIL loads, the display depends on whether there are 

multiple QLogic HBAs installed: 


appears. 

• If there are multiple QLogic HBAs, a list of addresses occupied 

by those HBAs appears. Since the Symmetrix system is 

attached to the lowest-numbered PCI slot, select the first 

adapter from the list, and press ENTER. The Fast!UTIL Options 

menu then appears. 

4. From the Fast!UTIL Options menu, select Configuration Settings 


5. From the Configuration Settings menu, select Adapter Settings 


6. From the Host Adapter Settings menu, select Host Adapter 

BIOS and press ENTER to enable it if it is not already enabled. 

Refer to the Table 2-1 on page 2-6 for recommended settings. 

7. Press ESC to exit the Configuration Settings menu. 

8. From the Configuration Settings menu, select Selectable Boot 

Settings and press ENTER. 


Device and press ENTER (if it is not already enabled). 


The adapter scans for attached storage devices, appears. 

Depending upon the CLARiiON model, the HBA may not yet detect any 

LUNs, or it may detect a LUNZ labeled device. This behavior is 

acceptable and to be expected. 

Configuring a CLARiiON Boot Device 3-13

3 


11. Skip from the BIOS configuration to a separate host that has EMC 

Navisphere management software installed and is attached to the 

CLARiiON array. 

Since the operating system is not yet installed, the Navisphere 

Agent and/or Navisphere CLI is not running on the Linux host. 

Therefore, the HBA may need to be registered manually. 

From the management host, manually register the host's HBA 

and add the host to the newly created Storage Group using 

Navisphere management software. 

12. Return to the BIOS configuration and reboot the host. 

When the QLogic banner appears (as shown in step 2), press 

CTRL-Q. 

13. Once Fast!UTIL loads, select the Configuration Settings menu 


14. From the Configuration Settings menu, select the Selectable 

Boot Settings menu and press ENTER. 


Device and press ENTER to enable this option if it is not already 

enabled. 


The adapter scans for attached storage devices, and a list of the 

available LUN(s) appears. Select the CLARiiON port WWN from 

which the host will boot. Then select the LUN to be used as the 

boot device and press ENTER. 

On CLARiiON arrays, the desired boot LUN is 000. 

17. Press ESC in the Selectable Boot Settings menu to return to the 

Configuration Settings menu. 

18. Press ESC in the Configuration Settings menu to return to the 

Options menu. 

19. Select Save Changes and press ENTER. 

20. Press ESC to exit the Fast!UTIL menu. 




3 

Installing Supported RHEL 2.1, RHEL 3.0, and SLES 8 Releases onto 

the EMC Boot Device with the QLogic v6.x-Series and v7.x-Series 

Drivers 

EMC supports specific kernel and driver revisions when booting 

from the SAN. Currently, the majority of quarterly updates from Red 

Hat and Service Pack updates from SuSE contain an EMC-qualified 

version of the QLogic v6.x-series or v7.x-series driver. As specified on 

the EMC Support Matrix, the QLogic drivers integrated within the 

RHEL 2.1, RHEL 3.0, and SLES 8 updates may be used for booting 

from the SAN. Alternatively, the integrated QLogic driver may be 

used for the initial installation and then it may be upgraded to the 

QLogic v7.03.00 driver. 

When using the QLogic driver integrated into the distribution, there 

isn’t a requirement to create a driver diskette image. 

Using the RHEL 2.1, RHEL 3.0, or SLES 8 CDs, boot the server to be 

installed. The installation may be performed as it would when using 

an internal disk driver. 

If the driver integrated into the kernel is not supported by EMC, it 

may be used for initial installation. After the initial installation is 

completed, then the driver should be updated to an approved version 

of the driver. 

Refer to the EMC Support Matrix for the most recent information on qualified 

kernel and driver releases as well as architectures. 

Building the QLogic v7.x-Series Driver Diskette 

In some instances, it may be desirable to install the RHEL 2.1 or 

RHEL 3.0 Linux host using the QLogic driver that is outside of the 

kernel and posted to the EMC-approved section of the QLogic 

website. In cases such as this, a driver diskette image must be created. 

The driver diskette will provide the correct driver and information 

necessary for the Red Hat Installer to access the EMC storage array 

devices presented over the fabric. The driver diskette installation 

method allows devices to be discovered at installation time, for which 

the device drivers are not part of the standard distribution. 

Installing Supported RHEL 2.1, RHEL 3.0, and SLES 8 Releases onto the EMC Boot Device with the QLogic 3-15

3 


The process of building a driver diskette for RHEL is described in 

detail on several websites. The following website provides details 

and supplementary information on the build process. 

http://people.redhat.com/dledford 

Doug Ledford’s website contains the necessary kit to build driver 

diskettes, as well as detailed information on the function and 

development of driver diskettes. 

The entire build process must be performed on a Red Hat host that 

contains the kernel source tree for the target version of RHEL for 

which the driver diskette is being built. To ensure that the necessary 

source tree exists, the most straightforward method is to install the 

kernel-source RPMs from the RHEL 2.1 or 3.0 distributions on your 

build host. 

Follow the instructions as specified on Doug Ledford’s website to 

build the driver diskette image. Once the driver diskette has been 

successfully created, the RHEL installation may be performed. 

Installing RHEL 2.1 and RHEL 3.0 onto the EMC Storage Array with the QLogic 

v7.x-Series Driver Diskette 

Using the driver diskette created in the previous section, the 

installation of RHEL 2.1 or RHEL 3.0 may be performed. Before 

beginning the installation of the OS, perform the steps described in 

the Configuring the BIOS for SAN Boot section. 

To install with a driver diskette onto the EMC storage array device, 

use the following steps: 

1. Boot the server to be installed from the CD-ROM. 

2. At the boot: prompt, type the command linux dd (Linux driver 

diskette), and press ENTER. 

3. The installation will prompt you with the question: 

Do you have a device driver disk? 

Select YES. 

4. Next, the installation will prompt for the driver diskette to be 

inserted into the system: 

Insert your driver disk and press “OK” to continue. 

Insert the device driver diskette as instructed, and click OK. 



3 

5. When asked for the type of installation to perform, select Custom. 

By selecting the Custom installation option, you will have 

complete control of the boot device selection and manipulation. 

From this point, follow the normal installation process. 

Although EMC does not make recommendations on the 

installation selections, it is worthwhile to create a boot diskette for 

the installation, to aid in troubleshooting any possible 

connectivity problems. 

6. On completion of the installation, the system will boot into the 

newly installed OS. 

3-14 Configuring a Boot Device on the EMC Storage 

Installing Supported RHEL 2.1, RHEL 3.0, and SLES 8 Releases onto the EMC Boot Device with the QLogic 3-17

3 


Upgrading the Kernel 

After successfully completing the installation and rebooting the host, 

the kernel may be upgraded to a newer kernel revision to take 

advantage of fixes and features incorporated into the newer kernel 

errata. 

Please refer to the EMC Support Matrix for supported kernel revisions. 

EMC recommends installing the kernel packages, rather than 

upgrading them, so that either kernel version may be used for boot. 

In addition, if a boot diskette was created during the original 

installation, an updated copy should be created after the upgrade. 



A 

Setting Up External Boot 

for IBM Blade Server 

HS40 (8839) 

This appendix contains information on setting up external boot for 

IBM Blade Server HS40. 

◆ 

Configuring an HS40 BladeCenter Server to Boot from an External 

Array...................................................................................................A-2 

Setting Up External Boot for IBM Blade Server HS40 (8839) A-1

A 

Setting Up External Boot for IBM Blade Server HS40 (8839) 

Configuring an HS40 BladeCenter Server to Boot from an 

External Array 

IBM HS40 (8839) Blade Servers encounter a dual-port HBA conflict 

when attempting to configure boot BIOS to boot from an external 

array. To configure an HS40 BladeCenter server to boot successfully 

follow the steps below. 

1. Create a single zone containing the HBA port from which you 

want to boot. This prevents any conflicts with the other fibre 

port. 

2. Configure the QLogic BIOS to boot from the EMC array as 

described in Chapter 3. 

During server POST, be sure that the QLogic banner displays the 

selected boot LUN correctly before continuing. 

3. Reboot the host and press F1 to enter the server BIOS 

Configuration/Setup Utility. 

4. Select Devices and I/O Ports, and press ENTER. 

5. Select IDE Configuration Menu, and press ENTER. 

6. Select the Onboard PCI IDE Controller, and press ENTER. Under 

the options menu, set this IDE Controller to disabled. This will 

disable the internal IDE disk drives. 

7. Press ESC twice to return to the IDE Configuration Menu and 

then select Start Options, and press ENTER. 

8. Select Startup Sequence Options, and press ENTER. 

9. Select Third Startup Device, and press ENTER. 

10. Select HAx PortID xxxxxx xxxxx, and press ENTER. This boot 

device will be replaced as the Third Startup Device in the 

Startup Sequence Options. 

11. Press ESC until you are prompted to save your changes. Then exit 

the BIOS Configuration/Setup Utility. 

From this point, you may install the Linux operating system to the 

external boot disk using the normal Fibre Channel installation 

procedures described earlier in this document. 

A-2 EMC Fibre Channel with QLogic HBAs for the Linux v2.4.x Kernel Environment

Index 

B 

boot device, CLARiiON, configuring 3-11 

boot device, Symmetrix, configuring 3-7 

C 

cautions 

CLARiiON 3-2 

Symmetrix 3-3 

CLARiiON 

cautions 3-2 

FLARE upgrades 3-2 

ghost LUN 3-5 

limitations 3-5 

restrictions 3-2 

configuration 

utilities 1-7 

F 

FLARE upgrades 3-2 

functions, Linux 1-7 

H 

HBA 

installation 2-6 

K 

kernel packages 3-18 

L 

limitations 

CLARiiON 3-5 

Symmetrix 3-6 

LUN masking 3-4 

N 

NVRAM file 2-5 

NVRAM parameters 2-6 

Q 

QLogic BIOS 

NVRAM file 2-5 

R 

restrictions 

CLARiiON 3-2 

Symmetrix 3-3 

S 

single initiator zone 1-6 

Symmetrix 

cautions 3-3 

limitations 3-6 

microcode upgrades 3-3 

restrictions 3-3 

EMC Fibre Channel with QLogic HBAs for the Linux v2.4.x Kernel Environment i-1

Index 

U 

upgrades 

CLARiiON FLARE 3-2 

Symmetrix microcode 3-3 

utilities, configuration 1-7 

V 

Volume Logix 3-4 

Z 

zoning, Linux hosts 1-6 

i-2

EMC Fibre Channel with QLogic Host Bus Adapters for the Linux v2 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?