QLogic QLA2x00 HAM Driver for NetWare 4.x, 5.x, 6.x
===================================================
Contents
--------
1. OS Support
2. Supported Features
3. Release History
4. Creating the Driver Diskette
5. Installing the Driver
5.1. Initial OS installation with the QLogic Controller as Boot
5.2. Initial OS installation with the QLogic Controller as Add-On
5.3. Adding the QLogic Controller to the Existing OS
5.3.1. Adding the Driver for the First Time
5.3.2. Adding Additional QLogic QLA2x00 Controller
5.4. Updating the Existing QLogic Driver
6. Removing the Driver
7. Driver Optional Parameters
7.1. System Parameters
7.2. NVRAM Parameters
8. Limitations
9. Additional Notes
9.1. Novell NetWare support of QLogic HAM driver
9.2. PCI Hot Plug
9.3. 256 LUN Support
9.4. Support for DMI
9.5. Multipath support
9.6. Server Memory Recommendations
9.7. DOS Partition Recommendations
10. Diskette Content
11. Contacting QLogic
======================================================================
1. OS Support
-------------
This driver has been tested with NetWare 4.2, 5.1 and 6.0.
NOTE:
Novell do not support NW4.2 any longer;
if you do decide to use NW4.2, please be
sure to install support pack 9 (NW42SP9).
======================================================================
2. Supported Features
---------------------
* NetWare Multi-Processor Compliance
* NetWare PCI Hot Plug Compliance
* Driver 256 LUN Support
* Driver Adapter/Lun Failover
* Driver DMI and QMS Support
======================================================================
3. Release History
------------------
Please refer to Release Notes.
======================================================================
4. Creating the Driver Diskette
-------------------------------
Locate the driver you want on the QLogic website and click "Link to
driver." If prompted "What would you like to do with this file?"
choose "Save this program to disk". Specify a temporary location on
the hard drive and download the driver. Insert a blank diskette in
the diskette drive. Run the self-extracting file you just downloaded
specifying A:\ for "Unzip To Folder:".
======================================================================
5. Installing the Driver
------------------------
NOTE:
If using Netware 4.2, then Support Pack 9
or later is required to be be installed.
This section is divided into the following four sections:
1. Initial OS installation with the QLogic Controller as Boot.
2. Initial OS installation with the QLogic Controller as Add-on.
3. Adding the QLogic Controller to the Existing OS.
4. Updating the existing QLogic Driver.
Note:
The driver ham file resides on the default Netware DOS
directory C:\NWSERVER; you could shortcut the driver
install process by copying the ham file (and the ddi
file) to that directory, and editing the script file
STARTUP.NCF (in the same directory) to contain one
driver load line for each QLogic controller adapter;
for example:
LOAD QL2300.HAM /LUNS /SLOT=401
LOAD QL2300.HAM /LUNS /SLOT=402
======================================================================
5.1. Initial OS installation with the QLogic Controller as Boot
---------------------------------------------------------------
Perform the following steps to initially install NetWare on a
Fibre Channel (FC) disk drive attached to the QLA2x00 controller.
0. Enable the BIOS on the QLogic adapter, and
select the FC as the boot device.
1. If you haven't already done so, install DOS on the boot disk.
NOTE:
If installing NW6.x or NW5.x using the Express install option,
then do the following before step 2:
a. Create directory NWUPDATE at the root of the C: drive;
b. Copy the QLogic *.HAM and *.DDI files to directory
NWUPDATE on the C: drive.
NOTE:
If installing NW4.2, then do the following before step 2:
a. Create directory NWUPDATE at the root of the C: drive;
b. Copy file NWPA.NLM from Support Pack 9 (or later) to
directory NWUPDATE on the C: drive.
During installation, NW4.2 will use the NWPA.NLM from
the NWUPDATE directory instead of the one on the CD.
2. Follow the standard NetWare instructions to begin the installation.
3. When prompted to "Choose Storage Drivers - Disk Drivers",
press <Insert> to install an unlisted driver.
4. Insert the QLogic Fibre Channel Software diskette and
press <F3> to specify the path to the QLogic HAM driver:
A:\NETWARE
5. Press <Enter> to select the QLogic HAM driver.
6. Follow the standard NetWare installation procedure and complete
the installation.
======================================================================
5.2. Initial OS installation with the QLogic Controller as Add-On
-----------------------------------------------------------------
Perform the following steps to install Netware and the QLogic
driver on the device not attached to the QLA2x00 controller.
Same as section 5.1, except that at step 0,
the QLogic adapter BIOS should be disabled.
======================================================================
5.3. Adding the QLogic Controller to the Existing OS
----------------------------------------------------
Perform the following steps to add the driver to the existing NetWare
system.
5.3.1. Adding the Driver for the First Time
-------------------------------------------
NOTE:
If using NW4.2, then do the following before Step 1:
a. Create directory NWUPDATE at the root of the C: drive;
b. Copy file NWPA.NLM from Support Pack 9 (or later) to
directory NWUPDATE on the C: drive.
During installation, NW4.2 will use the NWPA.NLM from
the NWUPDATE directory instead of the one on the CD.
1. From the NetWare server prompt, load the appropriate NetWare
program:
LOAD INSTALL (NetWare 4.x)
LOAD NWCONFIG (NetWare 5.x, 6.x)
2. Select "Driver options" from the main menu.
3. Select "Configure disk and storage device drivers".
4. Select "Select an additional driver".
5. Press <Insert> to install an unlisted driver.
6. Insert the QLogic Fibre Channel Software diskette and
press <F3> to specify the path to the QLogic HAM driver:
A:\NETWARE
7. Press <Enter> to select the QLogic HAM driver and select "Yes"
to copy the driver from the diskette to the server directory.
======================================================================
5.3.2. Adding Additional QLogic QLA2x00 Controller
--------------------------------------------------
To support multiple adapters, add one LOAD command per adapter to
your STARTUP.NCF file (LOAD QL2x00.HAM SLOT=n). The "SLOT=n"
command line parameter is provided for specifying which adapter to
configure for each load instance. If the driver is loaded manually
from the server prompt and there are multiple adapters, the user
will be required to pick a slot number from a list.
The QLogic Fibre Channel QL2x00 HAM driver reads the onboard NVRAM
and supports all of the customized configuration parameters for the
adapter and the attached Fibre Channel devices. Use the <ALT-Q> key
combination during boot to access the adapter's configuration options.
======================================================================
5.4. Updating the Existing QLogic Driver
----------------------------------------
Perform the following steps if the driver is already installed
and you want to install an updated version of the driver.
1. From the NetWare server prompt, load the appropriate NetWare
program:
LOAD INSTALL (NetWare 4.x)
LOAD NWCONFIG (NetWare 5.x, 6.x)
2. Select "Driver options" from the main menu.
3. Select "Configure disk and storage device drivers".
4. Select "Deselect a selected driver".
5. Choose the QL2x00 HAM driver.
6. Select "Select an additional driver".
7. Press <Insert> to install an unlisted driver.
8. Insert the QLogic Fibre Channel Software diskette and
press <F3> to specify the path to the QLogic HAM driver:
A:\NETWARE
9. Press <Enter> to select the QLogic HAM driver and select "Yes"
to copy the driver from the diskette to the server directory.
10. Select "Select/Modify drivers parameter".
11. Insert the Slot Number and press <F10>.
12. Select "Save parameters and load driver".
======================================================================
6. Removing the Driver
----------------------
1. From the NetWare server prompt, load the appropriate NetWare
program:
LOAD INSTALL (NetWare 4.x)
LOAD NWCONFIG (NetWare 5.x, 6.x)
2. Select "Driver options" from the main menu.
3. Select "Configure disk and storage device drivers".
4. Select "Deselect a selected driver".
======================================================================
7. Driver Optional Parameters
-----------------------------
The HAM driver has two types of optional parameters:
1. System parameters (specified at driver load time)
2. NVRAM parameters (stored in the adapter's nvram)
These are described in the following subsections.
======================================================================
7.1. System Parameters
----------------------
Driver optional parameters are specified on the driver load line.
There are two categories of driver optional parameters:
Global - the parameter acts on all driver instances;
the value specified on the first instance
is used globally for all instances.
Instance - the parameter acts only on the individual
driver instance in which it is specified.
NOTE:
"QL2x00" refers to any one of the following:
2300, 2200, 2100.
The exception to this is the configuration file
"QL2x00.CFG" where the "x" character is literal.
SLOT=n
(Instance)
Specifies to NetWare the PCI slot number n of the
adapter for which to load this driver instance.
LOAD QL2x00.HAM SLOT=3
/LUNS
(Instance)
Specifies to NetWare to scan for all luns during the
load of this driver instance (otherwise NetWare will
only scan for lun zero devices); the scanned lun
number range is 0 to (n - 1) where n is specified
by the /MAXLUNS=n option.
LOAD QL2x00.HAM SLOT=3 /LUNS
/GNNFT
(Instance)
Uses a single GNNFT command to obtain a list of ports
from the fabric name server without needing to build
the list from an iteration sequence of indiviual GAN
commands (which time consuming); most newer fabric
switches support the GNNFT command.
LOAD QL2x00.HAM SLOT=3 /LUNS /GNNFT
/ALLPATHS
(Global)
Disables failover and reports to NetWare all devices
on all adapter paths; this allows upper layer modules
to do failover across a Netware server's multiple
adapters.
LOAD QL2x00.HAM SLOT=3 /LUNS /ALLPATHS
/PORTNAMES
(Global)
Internally tracks devices by portname rather than
nodename; this is required when storage luns do not
have a 1:1 correspondence across portnames; this
allows upper layer modules to do failover across
a storage subsystem's multiple ports.
LOAD QL2x00.HAM SLOT=3 /LUNS /PORTNAMES
/PORTDOWN=n
(Global)
Sets the port down timeout period to n seconds;
this is the timeout period for adapter link down
and storage port down; the expiration of this
timeout triggers failover if multiple paths/ports
are available.
LOAD QL2x00.HAM SLOT=3 /LUNS /PORTDOWN=n
/FAILBACK=n
(Global)
Sets the failback delay time period to n seconds;
this is the time period that elapses when some
port update has event occured before any attempt
is made to failback paths/ports.
LOAD QL2x00.HAM SLOT=3 /LUNS /FAILBACK=n
/BACKOFF
(Global)
Disables failback of I/O after a broken link or a
broken port has been restored and made operational.
LOAD QL2x00.HAM SLOT=3 /LUNS /BACKOFF
/IGNCFG
(Global)
Avoids reading the configuration file QL2x00.CFG,
and allow all devices to be reported to Netware;
this file is located in the default DOS directory
(C:\NWSERVER), and is written by QLogic SANsurfer
software or the CFG.NLM test tool.
LOAD QL2x00.HAM SLOT=3 /LUNS /IGNCFG
/REQCFG
(Global)
Requires reading the configuration file QL2x00.CFG,
and ignores all devices not specified therein, or
ignores all devices if this file does not exist;
this file is located in the default DOS directory
(C:\NWSERVER), and is written by QLogic SANsurfer
software or the CFG.NLM test tool.
LOAD QL2x00.HAM SLOT=3 /LUNS /REQCFG
/CONSOLE
(Global)
Sends system alerts to the server console when
failover and failback events occur.
LOAD QL2x00.HAM SLOT=3 /LUNS /CONSOLE
/MAXLUNS=n
(Global)
Set the maximum number of luns allowed during the
lun scan; the range of luns searched is 0 to (n-1);
this value is
LOAD QL2x00.HAM SLOT=3 /LUNS /MAXLUNS=256
/SKIPREPORT
(Instance)
Avoids executing the SCSI Report Luns command during
lun scanning; otherwise if this option is not used,
the information returned by the Report Luns is used
to optimize the lun scan by doing SCSI Inquiries to
the luns listed in the Report Luns information only.
LOAD QL2x00.HAM SLOT=3 /LUNS /SKIPREPORT
/INQUIRY
(Instance)
Force SCSI Inquiry commands to be used during the
lun scan regardless of the luns listed by the SCSI
Report Luns command; the existence of a particular
lun is determined solely by the results of the
Inquiry to that lun.
LOAD QL2x00.HAM SLOT=3 /LUNS /INQUIRY
/STARTUNIT
(Instance)
Sends the SCSI Start Unit command to each lun during
the lun scan; on some multiple port RAID subsystems,
this may cause lun ownership to tranfser across ports.
LOAD QL2x00.HAM SLOT=3 /LUNS /STARTUNIT
/COMPLEXTAG
(Instance)
Enables SCSI complex tag queuing; the hacb preserve
order contrl flag maps to ordered queue, and the hacb
priority contrl flag maps to head of queue; otherwise
if the absence of these hacb contrl flags maps to
simple queue tag.
LOAD QL2x00.HAM SLOT=3 /LUNS /COMPLEXTAG
/XRETRY=n
(Instance)
Extends the retry count to n for any IO command that
experiences failure with SCSI sense info SK/ASC/ASCQ
code in this list: 2/04/01, 6/8B/02.
LOAD QL2x00.HAM SLOT=3 /LUNS /XRETRY=10
/XTIMEOUT=n
(Instance)
Extends the timeout value to n seconds for any IO
command that experiences a timeout (ie. held by the
storage device for a long period of time).
LOAD QL2x00.HAM SLOT=3 /LUNS /XTIMEOUT=120
/QUALIFIED
(Instance)
Extends the Inquiry data lun present test to allow
RAID subsystem luns to be filtered as follows:
Luns returning 20 XX are reported,
Luns returning 20 00 are ignored.
LOAD QL2x00.HAM SLOT=3 /LUNS /QUALIFIED
/LUNZERO
(Instance)
Reports to NetWare lun 0 regardless of its actual
existence as determined by the response to the SCSI
Inquiry command, as long as the port was logged in;
this is used for RAID subsystems that do not report
any luns on a port until the subsystem is configured
for the first time.
LOAD QL2x00.HAM SLOT=3 /ALLPATHS /LUNZERO
======================================================================
7.2. NVRAM Parameters
---------------------
The QLogic adapter NVRAM settings are modified by entering Fast!UTIL
during server hardware boot (press ALT-Q when prompted by the adapter).
In Fast!UTIL, first select the host adapter, and then
select "Configuration Settings".
Then, under the following headings, you will see these parameters:
Host Adapter Settings
---------------------
+ Frame Size
: Loop Reset Dealy
+ Adapter Hard Loop Id
+ Hard Loop Id
Advanced Adapter Settings
-------------------------
+ Exexcution Throttle
+ Fast Command Posting
: >4GB Addressing
+ Luns Per Target
+ Enable LIP Reset
+ Enable LIP Full Login
+ Enable Target Reset
: Login Retry Count
+ Port Down Retry Count
+ Drivers Load Risc Code
= Enable Database Updates
: Disable Database Load
: IOCB Allocation
: Extended Error Logging
Extended Firmware Settings
--------------------------
= Exteneded Control Block
@ RIO Operation Mode
+ Connection Options
@ Class 2 Service
@ ACK0
+ Fibre Channel Tape Support
+ Fibre Channel Confirm
@ Command Reference Number
@ Read Transfer Ready
@ Response Timer
@ Interrupt Delay Timer
+ Data Rate
Key:
+ Used by Ham driver (change effects behaviour)
@ Default value expected by Ham driver (do Not change)
= Overridden by Ham driver (change has no effect)
: Not used by Ham driver (change has no effect)
NOTES
-----
1. Enable both of the following to support FC-Tape
(see "Extended Firmware Settings" above):
Fibre Channel Tape Support
Fibre Channel Confirm
2. The timeout for loop/link/port down is set [in seconds] by
(see "Advanced Adapter Settings" above):
Port Down Retry Count
For best results, set this parameter to 15 or 20 (seconds).
======================================================================
8. Limitations
--------------
See Server Memory Recommendations below.
======================================================================
9. Additional Notes
-------------------
9.1. Novell NetWare support of QLogic HAM driver
------------------------------------------------
This subsection only applies if you are using NetWare 4.11.
The following drivers are provided with Novell NetWare for supporting
various Fibre Channel devices through the Fibre Channel HAM driver:
SCSIHD.CDM NetWare CDM driver for supporting SCSI hard disk devices
SCSICD.CDM NetWare CDM driver for supporting SCSI CD-ROM devices
SCSIMO.CDM NetWare CDM driver for supporting SCSI magneto-optical
storage devices
NWTAPE.CDM NetWare CDM driver for supporting SCSI tape devices
(SBACKUP requires this driver)
NWASPI.CDM NetWare CDM driver for supporting SCSI devices through
the ASPI interface (see note below)
CDROM.NLM NetWare CD-ROM driver for supporting CD-ROM devices
After the HAM driver is loaded, the CDM drivers will be loaded
automatically by NetWare as needed.
NOTE: Contact Novell for any missing CDM drivers that you need.
(the NWASPI.CDM driver is missing on the NetWare 4.1 release.)
======================================================================
9.2. PCI Hot Plug
-----------------
NOTE:
This procedure addresses only the driver-related portion of the
PCI Hot Swap operation. The server must have PCI slots that are
capable of being powered up and down independently. Depending
on the server platform, this entire operation may be controlled
by a platform specific software module supplied by the platform
vendor. In such a case, these commands are issued directly to
the driver and do not require the operator to enter them.
PCI Hot Plug works by unloading a specific instance of the driver
associated with a specific host adapter. It allows a failed adapter
to be removed and replaced by an adapter of the same type without
disrupting the operation of other adapters of the same type. The
steps necessary to perform a hot swap operation are listed below.
1. Type "List Devices" or "List Storage Adapters" at the server
console. You will see a list similar to this example:
[V591-A0-D0:0] SCSI HARD DISK
[V591-A0-D1:0] SCSI HARD DISK
[V591-A1-D3:0] SCSI HARD DISK
[V591-A1-D4:0] SCSI HARD DISK
2. If it were desired to remove host adapter instance 0 controlling
the first two hard drives, the operator would enter the following
command:
REMOVE STORAGE ADAPTER A0
3. After the host adapter has been replaced, the operator would make
the new adapter operational by loading another instance of the
driver using the normal load command syntax. For example:
LOAD QL2x00.HAM SLOT=3
======================================================================
9.3. 256 LUN Support
--------------------
To find all LUNS, load the driver with the /LUNS qualifier.
For example:
LOAD QL2x00.HAM SLOT=3 /LUNS
Or, if the driver is already loaded, use the command SCAN ALL LUNS at
the server console prompt to find all LUNS (new and existing LUNS).
NOTE:
The following applies ONLY to QL2x00.HAM Version 5.xx and
later drivers:
* The driver reports actual LUN numbers without ID/LUN mapping.
* The driver reports virtual ID numbers to insulate NetWare
from the dynamic nature of fabrics.
With NetWare 4.11, to use more than 8 LUNs per ID,
the following modules MUST be updated:
a. SCSIHD.CDM for use with hard disk drives
b. SCSICD.CDM for use with cd-rom drives
c. SCSIMO.CDM for use with magneto-optical disk drives
d. SCSI2TP.CDM for use with tape drives
e. SCSICHGR.CDM for use with media changers
Newer versions of these modules are available from Novell.
With the older versions of these CDM modules,
only 8 LUNs per target ID are allowed, and you must
set the LUNs Per Target parameter to 8 in Fast!Util.
IMPORTANT:
With the new CDM modules, it is recommended that
you use the /MAXLUNS=n driver load switch, or set
the LUNs Per Target parameter in Fast!Util to the
required number of LUNs per target ID (see ** below).
If not using multiple LUNs per ID, set this parameter to 0.
** To set the LUNs Per Target parameter:
1. Reboot the hardware, and do ALT-Q when QL2x00 banner appears.
2. Select the desired adapter.
3. Select Configuration Settings.
4. Select Advanced Adapter Settings.
5. Select LUNs Per Target and change the LUNs Range.
6. Press ESC twice and select Save.
7. Press ESC again and select Reboot.
======================================================================
9.4. Support for DMI and QMS
----------------------------
This driver supports DMI (Desktop Management Interface) allowing
QLogic adapter information and statistics to be queried by a remote
Windows NT client running the QLogic QLview for Fibre application.
This driver also supports QMSJ (QLogic Management Software Java)
allowing SAN connected storage to be configured for failover.
Please refer to the readme files for QLview for Fibre, QLconfig,
and QMSJ for further information (see Contacting QLogic below).
======================================================================
9.5. Multipath support
-----------------------
The driver by default will present only one path to NetWare if multiple
adapters and/or multiple ports are connected to the same storage device.
This prevents volumes from being multiple mapped and causing mount
segment corruption.
To disable multipath mode and allow NetWare to see all paths, load
the driver with the /ALLPATHS and /PORTNAMES options, as shown here:
LOAD QL2x00.HAM SLOT=3 /LUNS /ALLPATHS /PORTNAMES
The /ALLPATHS and /PORTNAMES options are required if an upper layer
module is going to handle failover (it expects to see all paths).
======================================================================
9.6 Server Memory Recommendations
---------------------------------
In general, at least 256MB of memory is recommended.
For large numbers of large volumes, at least 512MB is recommended
in order to have best performance.
======================================================================
9.7 DOS Partition Recommendations
---------------------------------
In general it is recommended that you load DOSFAT.NSS in STARTUP.NCF
to allow NetWare to access the DOS partition using the attaching HAM
driver rather than the DOS INT 13 interface.
Doing this allows the attaching HAM driver to apply it's features to
any I/Os to the DOS partition (e.g. the QL2x00.HAM driver provides
a failover mechanism which the HBA BIOS does not provide).
The HAM driver and the corresponding CDM driver must be loaded prior
to loading DOSFAT.NSS; for example, STARTUP.NCF would contain:
LOAD SCSIHD.CDM
LOAD QL2300.HAM /LUNS
LOAD DOSFAT.NSS
You can also do this when the DOS partition is IDE attached.
======================================================================
10. Diskette Content
--------------------
\NETWARE\QL2x00.DDI Driver installation description file
\NETWARE\QL2x00.HAM NetWare HAM driver for supporting the QLogic
Fibre Channel PCI QLA2x00 host adapters
\NETWARE\RELEASE.TXT Release notes (change history)
\NETWARE\README.TXT This file
======================================================================
11. Contacting QLogic
---------------------
Please visit QLogic's website http://www.qlogic.com where you will
find product information, our latest Novell certified drivers and
links for technical assistance if needed.
======================================================================
Copyright (c) 2000 - 2002 QLogic Corporation. All rights reserved.
======================================================================
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.