Fibre Channel Multi-protocol Port Driver for Windows 2000
Emulex Corporation
Release v2.11a2
September 28, 2001
The contents of this kit are listed below. This kit contains release notes and
necessary files to install the Fibre Channel Multi-protocol Port Driver in a
Windows 2000 system.
This release includes the following files:
README.TXT This file
emulex.sli A tag file
elxscsi.inf The setup file used by the SCSI Adapter install program
elxcfg.lnk The start menu link to the configuration program
txtsetup.oem The data file for bootable driver installation
elxsli2.cat Included only with the digitally-signed certified driver
oemsetup.inf The setup file used by the Network Add Adapter program
elxnet.sys The network driver for Intel platforms
elxsli2.sys The base and SCSI driver for Intel platforms
elxcfg.exe The configuration utility for Intel platforms
emulexhbaapi.dll Library supporting common HBA applications
hbaapi.dll Wrapper for emulexhbaapi.dll
Compatibility
* The LP7000E, LP8000, LP8000DC, LP850 HBAs with firmware version 3.03 or higher,
however to support all current driver features we recommend version 3.20
* All Boot Bios versions however we recommend 1.50 or higher
* Arbitrated loop, point to point and fabric topologies
* Upcoming LP9xxx HBA releases.
Prerequisites:
* Windows 2000 running on an x86 platform
* Windows 2000 Service Pack 1 (recommended when supporting 126 LUNs or more)
* Installed LP7000E, LP8000, LP8000DC, LP9000, LP950 or LP850
INSTALLATION INSTRUCTIONS:
To install the Multi-protocol Port Driver on an installed Windows 2000 system:
To install the Fibre Channel (SCSI) protocol stack:
1. Select "Start Menu"
2. Select "Settings" Program Group
3. Select "Control Panel" Program Group
4. Select "System" Icon
5. Select "Hardware" Tab
6. Open SCSI and Raid controllers item in list.
7. Double click on Emulex host bus adapter.
8. Select drivers tab.
9. Select Update Driver
10. Select specify location to search for drivers and indicate path to the
driver kit
11. Select the appropriate driver from the list of other drivers.
12. Repeat for each adapter in the system.
After installing the Emulex LP6000 SCSI port driver, Fibre Channel SCSI disk
devices will be automatically detected by Windows 2000 if the Automap SCSI Devices
option was selected. If the Automap SCSI devices option was not selected, launch
elxcfg.exe and map the devices as instructed below. A shortcut to the Emulex
Configuration Tool is located on the Start Menu under Programs.
To install the IP (LAN) protocol stack:
The Emulex Configuration Tool and the SCSI protocol stack must be installed
before installing the IP protocol stack.
1. Reboot the system.
2. Select "Start Menu"
3. Select "Programs"
4. Select the Emulex Configuration Tool5. In the Emulex Configuration Tool,
select a host bus adapter.
6. Press the Network button.
7. Select Enable Networking.
8. Change any other options.
9. Press OK.
10. Press Apply.
11. If enabling networking on more than 1 adapter, repeat steps 2-7.
12. The system should prompt for new hardware. If it does not, reboot the
system.
13. If the system rebooted, login and the system will prompt for new hardware.
14. Select Specify location to search for drivers and indicate path to the
driver distribution.
15. If the network driver does not start, use the Device Manager to disable
and then re-enable the network driver. This will cause the driver to
start.
Installation Options
NOTE: The installation options, when installing or updating a driver, will apply
for every adapter in the system. If there are multiple adapters in the system
requiring separate options, it is IMPERATIVE to install each one with the same
installation option and then modify as needed using the Configuration Tool. After
modification with the Configuration Tool, the system will require a reboot. Below
are the list of options presented during an installation or upgrade.
******* WARNING ********
If updating the SCSI portion of the driver and the network portion of the driver
is installed, it is recommended to remove the network portion of the driver before
beginning the updating procedure.
LP-X000 (Default Settings)
This option will only copy the driver files, it will not make any changes to the
registry. This setting should be used for any adapters added to a system that
already is using the Emulex Multi-Protocol driver.
Loop, Automap SCSI Devices
This is the basic loop and disk drive(s) configuration. No fabric, and automatically
discover disk drives when booted.
Loop, No Automap of SCSI Devices
This is for loop when other systems already reside on the loop. Selected this will
keep NT from trying to grab all of the devices on the loop. SCSI devices will have
to be mapped with the Emulex Configuration Tool before use.
Fabric, Automap SCSI Devices
This is the basic Fabric and disk drive(s) configuration. The connection to the
fabric is assumed to be point to point. SCSI Devices will be automatically mapped
when discovered.
Fabric, No Automap of SCSI Devices
Fabric, but don't automatically map SCSI devices when discovered.
Public Loop, Automap SCSI Devices
This is for a connection to a Fabric through an FL-Port. Automatically map SCSI
devices when discovered.
Public Loop, No Automap of SCSI Devices
This is for a public loop connection, but do not automatically map SCSI devices
when discovered.
NOTE: The installation options will apply for every adapter in the system. If there
are multiple adapters in the system requiring separate parameters, then it will be
necessary to modify the parameters with the configuration utility and then reboot.
Registry Options
The options for the device may be set in the SERVICES section of the registry under
the elxsli2 key. Options set under the elxsli2 key are global, meaning they apply as
the default for each adapter installed. The options listed as installation options
are the only globally supported options. The associated value names for each of the
options are listed below:
AllowAck0
If 1, and the device supports class 2, allow the use of ACK_0 for sequence
acknowledgment. If 0, do not allow ACK_0.
Default value: 0
Type: REG_DWORD
ALTOV
Value in milliseconds to be used for the Arbitrated Loop Timeout Value.
Default value: 15
Type: REG_DWORD
ARBTOV
Value in milliseconds to be used for the Arbitration Timeout Value.
Default value: 1000
Type: REG_DWORD
AttemptReEstablish
If 0, when a target disappears and then "quietly" reappears, it will not be detected.
A target has quietly reappeared when no LIP occurs for a device on a loop or no
RSCN is issued for a device on a switch. If 1, after a device disappears, the driver
will poll the Fibre Channel address of the device periodically to see if it has
reappeared.
Default value: 0
Type: REG_DWORD
AutoMap
Value 1 or 0, corresponding to the checked or not checked state of the Automatically
map SCSI devices check box.
Default value: 1
Type: REG_DWORD
BrokenRscn
If 0, the RSCN payload is used to determine whether devices have been added or
removed from the system. If 1, the RSCN payload is ignored and the Name Server
is queried for the new information.
Default value: 0
Type: REG_DWORD
DriverTraceMask
Bit mask of available trace options. Trace data is written into the system
event log and if the debugger is connected, to the debugger window.
Default value: 0
Type: REG_DWORD
Following is a list of trace types and the mask values. It is possible to
bitwise OR two or more trace types.
Trace Type Mask Value
SLI_TRACE_MAILBOX 0x00000001
SLI_TRACE_SCSI_ERR 0x00000002
SLI_TRACE_IOTAGS 0x00000004
SLI_TRACE_IOCB 0x00000008
SLI_TRACE_FABRIC 0x00000010
SLI_TRACE_SCSI_MAPPING 0x00000020
SLI_TRACE_INIT 0x00000040
SLI_TRACE_IOCTL 0x00000080
SLI_TRACE_SCSI_RESET 0x00000100
SLI_TRACE_LOGIN 0x00000200
SLI_TRACE_NET_XMIT 0x00000400
SLI_TRACE_NET_RECV 0x00000800
SLI_TRACE_WAIT_READY 0x00001000
SLI_TRACE_RECV_ELS 0x00002000
SLI_TRACE_DOWNLOAD 0x00004000
SLI_TRACE_PRLI 0x00008000
SLI_TRACE_REPORT_LUNS 0x00010000
SLI_TRACE_ENTRIES 0x00020000
SLI_TRACE_ELS_ERRORS 0x00040000
EDTOV
Value in milliseconds to be used for the Error Detect Timeout Value.
Default value: 1000
Type: REG_DWORD
InitLinkFlags
The InitLinkFlags is divided into several fields. Bits 1 to 3 are the
initialization type. If bits 1 to 3 are 000, the link will be initialized
as Arbitrated Loop. If bits 1 to 3 are 001, the link will be initialized as
Point to Point. The presence of a fabric is automatically detected in either
case.
Bit 23, if set, indicates the adapter should attempt the other topology type
if the first selection fails to initialize. This option is only available with
firmware that supports this option.
Bits 24 to 31 are the encoded speed value. If bits 24-31 are 0x00, the link speed
is discovered automatically. If bits 24-31 are 0x01, the link speed is forced to
1 Gigabit per second. If bits 24-31 are 0x02, the link speed is forced to
2 Gigabits per second. This option is only available with adapters that support
more than one link speed.
Default value: 0
Type: REG_DWORD
InterruptCoalesce
The InterruptCoalesce value is a combination of fields. The first field is bits 0 to
7, which is the number of I/Os that should complete before an interrupt occurs. Bits
8 to 14 are the number of milliseconds that will expire before an interrupt will occur
if some I/Os complete, but less than the number of I/Os specified in bits 0 to 7.
This option is only meaningful for adapters with firmware version 3.00 or later.
Default value: 0
Type: REG_DWORD
IosPerInterrupt
This is the maximum number of I/Os that the driver will complete in a single interrupt.
This value may be modified to achieve an overall system fairness.
Default value: 128
Type: REG_DWORD
HgpOffset
This value is the offset into SLIM to located the Host Get and Put pointers. If the
value is 0, the Host Get and Put pointers are located in system memory. The range
of this value should be between 0xc00 and 0xe00, although any value below 0xff0 is
accepted.
Default value: 0
Type: REG_DWORD
NodeId
The NodeId is a 32 bit quantity that is used with a fixed 32 bit value to create a
World Wide Node name for the entire system. The created World Wide Node name has the
value of 50000C90xxxxxxxx, where xxxxxxxx is the 32 bit value contained by NodeId.
It is up to the assignor of NodeId to ensure the uniqueness on a single fibre channel
network. If the value is 0, or the value is not present in the registry, the Node
World Wide name for the system is the Node World Wide Name of the first adapter
found by the driver. This value is normally set as a global flag. If set as an
adapter value, the only adapter for which it will have any meaning is the first
adapter found by the driver.
Default value: 0
Type: REG_DWORD
RetryPlogiOpenFailures
If non-zero, the driver will retry PLOGIs that fail with an open failure up to
3 times. If zero, the driver will assume a PLOGI that fails with an open failure
to indicate no device is present.
Default value: 0
Type: REG_DWORD
UseUniqueWwns
If non-zero, the driver will use the Node World Wide Name stored in the NVRAM
of each adapter. If zero, the driver will use the Node World Wide Name of the
first adapter found for all adapters. If zero and NodeId is non-zero, then the
driver will create a Node World Wide Name from NodeId and use it for all adapters.
Default value: 0
Type: REG_DWORD
LinkDownTimer
LinkDownTimer is the number of seconds the driver will wait after detecting a
link down condition before I/O will be returned with an error. If the link is
restored before the LinkDownTimer expires, the I/O will continue with no error
indication.
Default value: 30 seconds
Type: REG_DWORD
MapLuns
If 0, the driver will operate as before, each LUN will be addressed without any
address translation. If the value is 1, LUN mapping is enabled, and each NT LUN
number will be translated to a 64 bit Fibre Channel LUN number. For new LUNs, this
mapping will be done automatically by the driver. If the report LUNs command is
supported by the target, the first 256 LUNs reported may be used by NT. If the
value is 2, LUN mapping is enabled, but the driver will not automatically map LUNs.
Default value: 0
Type: REG_DWORD
MaximumLun
The Maximum Number of LUNs to probe for during device discovery.
Default value: 32
Type: REG_DWORD
MaximumQueueDepth
The maximum number of SCSI commands that may be issued to a single LUN before
one of the commands must complete.
Default value: 8
Type: REG_DWORD
MultipleScsiClaims
If 1, report each SCSI device for every port by which it is connected. If 0,
report the SCSI device only on the first port by which it is connected.
Default value: 0
Type: REG_DWORD
Network
This value is comprised of two single bit bit fields and one 16 bit integer. Bit 31
is the Network enable for the port. If Network Enable bit is set, then the network
driver can bind to this port. If the Network Enable bit is not set, then the network
driver will not be able to bind to this port. Bit 30 is the Class of Service bit.
If the Class of Service bit is set, network traffic will use Class 2. If the Class
of Service bit is not set, network traffic will use Class 3. Bits 15 - 0 are the
MTU to use for this network connection.
Default value: 1514 (Network Disabled, Class 3, MTU = 1514 bytes)
Type: REG_DWORD
NsQueryAll
If 1, request all N-Ports connected to the Fabric from the name server. If 0,
request only registered SCSI FCP devices.
Default value: 1
Type: REG_DWORD
QuickFail
QuickFail is useful in redundant path setups. When QuickFail is nonzero, then
I/O is returned with an error as soon as the WaitReadyTimeVal expires the first
time. Also, if a node is not present in the Name Server response after an RSCN,
the node is immediately marked off-line and I/O is returned. If set to 0, the
driver will send a PLOGI after the initial WaitReadyTimeVal expiration and
wait one additional WaitReadyTimeVal before returning I/O with an error.
Default value: 0
Type: REG_DWORD
RATOV
Value in seconds to be used for the Resource Allocation Timeout Value.
Default value: 2
Type: REG_DWORD
RegisterForStateChange
If 1, the driver will register for RSCN state change notifications if a
fabric is present. If 0, the driver will not register for the RSCN state
change notifications.
Default value: 1
Type: REG_DWORD
RetryAttempts
The number of times the driver will retry a command completing with a retryable status
before returning the status to the caller.
Default value: 64
Type: REG_DWORD
RetryTimer
The time in milliseconds the driver will wait before retrying a command.
Default value: 200
Type: REG_DWORD
RetryUnitAttention
If 1, the driver will retry commands that complete with Unit Attention status. If 0,
the driver will complete the command with appropriate status.
Default value: 0
Type: REG_DWORD
ScanDeviceIdOrder
If 0, then the local loop is scanned from ALPA 0x01 to ALPA 0xEF. If 1, then the
local loop is scanned from 0xEF to 0. Also, if 1, the NT ID for automapped SCSI
devices is the same as the device's Device ID.
Default value: 1
Type: REG_DWORD
ShowUnknowns
If 0, only LUNs with a Peripheral Qualifier of 0 will be reported in the Inquiry
buffer. If 1, then LUNs with a Peripheral Qualifier of 0 or 1 will be reported in
the Inquiry buffer.
Default value: 0
Type: REG_DWORD
TranslateQueueFull
If 1, the driver will translate SCSI Queue Full status to SCSI Busy status to work
around a behavior of the disk class driver. If 0, then the driver will not translate
the status.
Default value: 0
Type: REG_DWORD
UseReportLuns
If 1, the driver will use the SCSI Report LUNs command to determine the
presence of LUNs on SCSI devices. If 0, the driver will poll up to the
number of LUNs configured with the MaximumLun configuration option.
Default value: 0
Type: REG_DWORD
UseResetForRetry
If 0, the driver will retry commands internally. If 1, then the driver will retry
commands by completing them with a status of SRB_STATUS_BUS_RESET.
Default value: 0
Type: REG_DWORD
UseTargetReset
If 1, use the task management function target reset to emulate a SCSI bus reset.
If 0, use TPRLO.
Default value: 1
Type: REG_DWORD
WaitReadyTimeVal
The time in seconds the driver will wait for a device to become available before
commands to the device are returned with SCSI selection timeout errors. If the value
is -1, then the timer value used is 2 * R_A_TOV. If the timer value is 0, then the
driver will wait forever for the target to become available.
Default value: -1
Type: REG_DWORD
Below the elxsli2 key are keys for each adapter installed in the system. Currently,
the keys are the electrical PCI bus number and slot number of the adapter. Note that
the electrical slot number may not match the mechanical slot number. Each of the global
values may be overridden by using the same value name under the per adapter key. Also,
the following values are available under the adapter key:
DidPollList
A list of DWORDs representing a list of 3 byte fibre channel addresses to be checked
during polling. Using the binary editor in the registry editor, these DWORDs must be
entered in Little-Endian mode, i.e.. address 11 22 33 must be entered as 33 22 11 00.
Default value: <empty>
Type: REG_BINARY
ffTraceMask
Value 0 - 0xffffffff. This sets the trace mask on the FireFly. If the PCI Print
option is selected, then the resulting messages will be printed using KdPrint
from inside the driver.
Default value: 0
Type: REG_DWORD
NameServerDelay
Value 0-0xffffffff. This is the number of milliseconds the driver will wait before
sending a name server request. This delay takes effect after a link failure/FLOGI,
or the receipt of an RSCN.
Default value: 0
Type: REG_DWORD
QuickFail
Value 0 or 1. If QuickFail is 1, the wait ready timer will only have to expire
once before I/Os are returned to the upper levels. Also, when QuickFail is 1,
any devices not present in the name server data obtained after an RSCN will be
immediately marked as failed. This causes fail-over to occur more quickly.
If QuickFail is 1 and the adapter is connected to a multi-switch fabric, the
NameServerDelay value, see above, should be set to at least 800 milliseconds.
ScsiMap
A key that contains the map of World Wide Port names to SCSI IDs. Each value under
this key binds one World Wide Port name to a single SCSI ID. Each value uses the
16 digit hex representation of the World Wide Port name as the value name. The value
is the SCSI ID to which the World Wide Port name is mapped. Each value is of
type REG_DWORD.
Also contained in ScsiMap is the LUN mapping if LUN mapping is enabled. The value name
for each LUN map is created from the World Wide Port name of the device. The value
name is LunMappingXXXXXXXXXXXXXXXX, where XXXXXXXXXXXXXXXX is the 16 digit hex World
Wide Port name of the target. The LunMapping value is of type REG_BINARY and is an
array of SCSI LUN Mapping structures. The structure is defined as follows:
typedef sliLunMap {
LARGE_INTEGER FibreChannelLUN;
ULONG NtLUN: 8;
ULONG Disabled: 1;
ULONG Present: 1;
ULONG Pad: 22;
} SLI_LUN_MAP, *PSLI_LUN_MAP;
Config Utility
The configuration utility is contained in elxcfg.exe. To execute the utility,
use the browse function of the run command selection from the start menu. Find
the file elxcfg.exe. Select run command.
Available Adapters
The configuration utility will probe the registry for configured adapters. If
the adapter is configured, it will be listed in the Available Adapters list
box. If the adapter is also present in the system, the type of adapter and the
firmware revision will appear in the listing of the adapter.
All of the other options will be grayed until an adapter is selected. To
select an adapter, click on the appropriate entry in the Available Adapters
list box. This will ungray all of the options, as well as set the values
to the current configuration of the adapter.
Dialog Menu
The menu bar at the top of the dialog, under the title bar, has the submenus
for File, Configuration, Tuning, and Tools. The File submenu allows the user to
apply changes, delete the settings for a removed adapter, or exit the program.
The Configuration submenu allows the user to select a number of default
configurations. The Tuning submenu allows the user to manipulate settings that
change the way the adapter behaves. And, the Tools submenu are some tools that
are available to the user for debugging, downloading firmware to the adapter, etc.
File Menu
Apply
This option is used to apply any changes that have been made to the current
adapters configuration or SCSI mappings.
Remove
This option is only available for an adapter that is not currently present in
the system. This option will remove the adapter configuration and SCSI mappings
for the selected adapter. All of the configuration information will be completely
removed. It will not be possible to restore this information.
Exit
This option will exit the program. If the configuration or SCSI mappings for the
current adapter have been changed, a dialog will appear asking if the user would
like to apply the current changes, or continue, which will cause the changes to be
discarded.
Configuration Menu
Set
This option will bring up a list of default configurations that are equivalent to
the options available when the driver is installed. If the current configuration
of the current adapter matches one of the options, the option will be already
selected. If the current configuration does not match any of available preset
configurations, none of the configurations will be selected.
The user can select one of the default configurations and the when the OK button
is pressed, the current adapters configuration will be modified to match the
selected configuration. In most cases, a reboot will be required to cause the
adapter to start using the new configuration.
Tuning Menu
Performance
Selecting the Performance option will bring up the Performance Parameters
dialog. In the Performance Parameters dialog, the user may select values
for the Maximum Interrupt Latency, the Minimum and Maximum I/Os handled per
interrupt, and whether Host Get and Put pointers are in SLIM or system
memory.
The Max Interrupt Latency, Min I/O Completions per Interrupt, and Max I/O
Completions per Interrupt work together to tune the system performance. An
interrupt is generated by the adapter when: at least one command has completed
and the timer controlling the interrupt latency expires, the number of commands
completed equals the Min I/O Completions per Interrupt, or the the Max I/O
Completions per Interrupt was reached on the previous interrupt and there are
still completed commands waiting to be processed. These options are only
available with adapter firmware version 3.00 and later.
Host Pointers in SLIM, if checked, cause the driver to initialize the host
written queue pointers to be located in memory on the adapter. This has the
benefit that the adapter does not need to access system memory to read the
pointers.
Link Control
Selecting the Link Control option will bring up the Link Control Parameters
dialog box. Select one of Arbitrated Loop or Point to Point for the topology.
If the Automatic Topology Detection flags is checked, the adapter will first
attempt the selected topology type. If initialization fails, the adapter will
try the other topology. This option is only available if it is supported by
the adapter firmware.
The Link Speed box is used to select the link speed. The default choice is
AUTO. This option is only available if the adapter supports multiple link
speeds.
Timers
The Wait Ready Timer is used to return commands to unavailable devices. When a
command is received for a device that is not currently present, the driver will
wait for the Wait Ready Timer length for the device to become available. If it
does not become available in the time period, then the driver will return the command
and all subsequent commands for the device with SCSI selection timeout errors.
If the timer values is set to -1, then the driver will use 2 * R_A_TOV as the
timer value. If the timer is set to 0, then the driver will wait indefinitely for
devices to become available.
The Retry Timer and Retries boxes allow the user to configure the retry behavior of
the driver. The Retry Timer is the number in milliseconds the driver will wait before
retrying a command. The retries box is the number of times the driver will retry a
command completing with a retryable error before returning the command to the caller
with an error status.
The next set of controls allow the modification of some of the Fibre Channel
timers controlled by the adapter.
Tools Menu
Download Firmware
Selecting the Download Firmware option will allow the download of adapter
firmware. When this option is selected, a file open browser dialog is created.
Find the appropriate firmware image file and select open. The firmware
will be verified, downloaded, and the adapter restarted. When the firmware
download is complete, click the OK button in the status dialog.
If the selected adapter is not present, this option will be grayed and
unavailable.
Dump Memory
Selecting the Dump Memory option will launch the Adapter Memory Dump dialog.
To display adapter memory, enter the desired starting address in the Memory
Offset edit box, and the length in bytes of the memory to dump in the Count
edit box. Then click on the Reload button. The memory contents will be
displayed in the memory dump window. To close the window, click on the Done
button.
If the selected adapter is not present, this option will be grayed and
unavailable.
Reset SCSI Bus
Selecting the Reset Bus button option will cause a SCSI bus reset to be emulated
by the selected adapter.
If the selected adapter is not present, this option will be grayed and
unavailable.
Networking
Selecting the Networking option will bring up the Network Parameters dialog.
The Network Parameters dialog has a Network Enable check box used to enable or
disable networking on the particular adapter. The class of service is selected
by use of the Class 2 and Class 3 radio buttons. Only one of the two Class of
Service buttons may be selected. If a device does not handle Class 2, indicated
in the PLOGI, the adapter will use Class 3.
The MTU is selected by entering the appropriate value in decimal in the MTU edit
box. Clicking the OK button will update the current adapter configuration with
the changes made in the Network Parameters dialog. Clicking the Cancel button will
ignore any changes made in the Network Parameters dialog.
Adapter Controls
Under Adapter Controls, the first set of controls are used for general
configuration of the adapter.
Automatically Map SCSI Devices, if checked, tells the driver to automatically
map new SCSI devices as they are discovered. If the devices have already been
mapped, either by discovery or manually, this check box has no effect.
Query name server for all N-Ports, if checked, tells the driver to ask the name
server for all connected N-Ports. If the box is not checked, the driver will
ask for all registered SCSI FCP devices.
Allow Multiple paths to SCSI Targets, if checked, causes mapped SCSI devices to
be reported on each port by which it is connected. If not checked, mapped SCSI
devices are reported only on the first port by which it is connected.
If the Register for State Change box is checked and a fabric is present, the driver
will register with the fabric to receive Registered State Change Notification
(RSCN) ELS requests from the fabric. If the box is not checked, the driver will not
register with the fabric, even if it is present.
If the Use Report LUNs for SCSI-3 Devices box is checked and a target indicates that
it is SCSI-3, the driver will use the report LUNs SCSI command to determine the
LUNs that are present. If the target is not SCSI-3 or this box is not checked, the
LUNs are polled starting at 0 and incrementing until the maximum LUN value is
reached.
If the Use Name Server after RSCN is checked, the driver will ignore the payload
of the RSCN and query the name server for the latest list of devices. If the box
is not checked, the driver relies on the data in the RSCN payload to update the
view of the fabric.
If the LUN Mapping box is checked, all LUNs behind all targets are mapped. Since
Fibre Channel targets support a LUN number 64 bits long and the port driver under
NT only supports 8 bits, some sort of mapping is required. If the LUN Mapping box
is checked, unmapped LUNs are not accessible by NT. If the LUN Mapping box is not
checked, there is a one to one correspondence of Fibre Channel LUNs to NT LUNs.
In the case where LUN Mapping is not used, the Fibre Channel LUN is created as
follows:
00xx00000000
where the xx is the NT LUN number.
If the Automatic LUN Mapping box is checked, LUNs are automatically mapped by the
driver as they are discovered. Note that this may cause LUN numbers to "change".
For example, the LUN indicated by the SCSI Applet on the control panel may be
different from the actual LUN number on the device. The mapping can be viewed by
clicking on the LUN Mapping button described below.
The Enable Class 2 for SCSI Devices check box, if checked and the target device
indicates Class 2 capability in the PLOGI Accept, the driver will use Class 2
for communicating with the device. If the check box is clear, the driver will use
Class 3 for communicating will all SCSI devices.
Use PLOGI instead of PDISC after LIP, if checked, causes the driver to use PLOGI
for device discovery. If not checked, the driver will use PDISC.
The Scan in Device ID Order option, if not checked, causes the driver to scan the
local loop from ALPA 0x01 to ALPA 0xEF. If the option is checked, the driver will
scan the local loop from ALPA 0xEF to 0x01. Also, if the option is checked, the
driver will use the device's Device ID for its NT SCSI ID if the SCSI Automap
feature is used.
The Report Unknown SCSI Devices, if checked, causes the driver to make available
to upper level drivers all devices that have a Peripheral Qualifier value of
0 or 1. If not checked, only devices with a Peripheral Qualifier of 0 will
be made available to upper level drivers. Please see the SCSI 3 SPC document for
more detail on the Peripheral Qualifier value.
The Look For Disappearing Devices option, if checked, causes the driver to
try and find devices that have silently disappeared. An example might be a
smart hub has put a port on bypass without generating a LIP. If the device
encounters an error which causes it to be removed from the available devices
list in the driver and then the hub removes the bypass, then the device will
be rediscovered only with this option being checked. If the option is not
checked, a device will only 'reappear' if a LIP, a link failure and restoration,
or an RSCN is received.
The Translate Queue Full to Busy option allows the translation of SCSI Queue Full
status to SCSI Busy status. This is a work around for a behavior of the disk class
driver. If the box is checked, the translation is enabled. If the box is not checked,
the translation is disabled.
The Use Bus Reset for Retries, if checked, enables a mode where the driver does not
retry commands internally. Instead commands to be retried are returned to the caller
with SRB_STATUS_BUS_RESET status. This will normally result in a command retry.
The Retry Unit Attention box, if checked enables the port driver to retry Unit
Attention errors.
The Retry PLOGI Open Errors is a work around for some loops with targets that do not
respond to OPN(x,y) soon after loop initialization is complete. If the option is checked,
the driver will retry PLOGIs that fail with an open failure error, the device did not
respond to OPN(x,y).
The Enable FCP-2 Error Recovery option, when checked, will allow the use of the FCP-2
exchange error recovery protocol with SCSI targets that support the protocol. For this
option to be most effective, the Use PLOGI instead of PDISC after LIP option should be
unchecked.
Maximum Number of LUNs is the number of LUNs the driver will poll for during
device discovery. The minimum value is 1, the maximum value is 255.
Maximum Queue Depth is the number of outstanding commands to a single LUN.
The Static Poll Destination Address list is a list of 24 bit Fibre Channel
addresses that will be polled for devices when the adapter boots. To add an
entry, enter the 6 hex digits of the Fibre Channel address in the Address
Edit box. Then click the Add Address button. To delete an address from the
list, select the address in the list box by clicking on it and then clock
on the Delete Address button.
SCSI Targets
The SCSI Targets list box shows the current SCSI ID to Fibre Channel World
Wide Port name assignments. To add a new mapping, click on the Add Mapping
button. This will bring up a SCSI device selection dialog. If the adapter is
present, a list box with the currently available and unmapped Fibre Channel
devices will appear. Select the appropriate device and click the OK button.
This will bring up the SCSI ID selection dialog. This dialog has a list box
that contains all of the available SCSI IDs. Select the appropriate SCSI ID
from the list box and click on the OK button.
To modify an existing mapping entry, select the entry by clicking on it and
click the Modify button. This will raise the SCSI ID selection dialog.
Follow the above directions to complete the modification.
To delete an existing mapping entry, select the entry by clicking on it and
click the Delete Mapping button.
To access the LUN mapping for a target, select the Target in the Targets list
box and press the LUN Mapping button. The LUN Mapping button will only be
enabled if the LUN Mapping check box is checked for the adapter.
Clicking on the LUN Mapping button will bring up the LUN Mapping dialog for the
selected target. The LUN Mapping dialog will show the SCSI Id being used by the
target and the Port World Wide Name of the target. The current LUN map will be
displayed in the large box.
If LUN Mapping is disabled for this target, instead of displaying a list of mapped
LUNs, the message "LUN Map Disabled" is displayed. To Disable LUN Mapping for a
single target, select the "Disable LUN Mapping" button from the LUN Mapping dialog
for the target. This target will behave as if LUN mapping was not enabled for the
target.
To enable LUN Mapping on a target that has LUN Mapping disabled, select Enable LUN
Mapping from the LUN Mapping dialog for the target.
The Add, Modify, and Delete buttons in the LUN Mapping dialog are disabled when LUN
Mapping is disabled for a target.
To add a LUN mapping, click on the Add button. This will bring up the MAP LUN dialog.
In the MAP LUN dialog, the unmapped and available Fibre Channel LUNs for the target
will be displayed in a list box. The Fibre Channel LUN must be selected from this
list. The NT LUN may be selected from the drop down list box. The first available
LUN number will be selected as the default. When done, press the OK button. To exit
without making any changes, press the Cancel button.
To delete a LUN mapping, select the mapping to delete and press the Delete button.
This will delete the mapping, however, if the Automatic LUN Mapping check box is
checked, the LUN will be mapped again next time Disk Administrator is started.
To change the NT LUN portion of a mapped LUN, select the mapping to be modified and
click on the Modify button. This will bring up the MAP LUN dialog, but only the NT
LUN drop down list box will be enabled. Change the NT LUN and press the OK button.
To quit without making a change, press the Cancel button.
Errata
It is not expected that current NT utilities for the LP 6000 Miniport driver
will work with this driver.
Removal of the port driver does not remove the configuration utility. (CR#748)
Using the Emulex Configuration Tool to change the adapter firmware to an earlier
version may cause the system to lock or devices connected via the adapter to
become unavailable, requiring a reboot.
Changes from driver version 2.10a7
The driver will no longer generate an event log entry if the link speed is set to
1 GIG and the adapter is indeed capable of 1 GIG. (CR#3750)
The driver can now communicate with the Brocade switch internal IP port via Fibre
Channel. (CR#3751)
The driver now enables Scsi FCP-2 error recovery by default. (CR#3752)
The driver no longer retries SCSI commands to non-disk devices. (CR#3753)
ExcludeFromSelect directives have been added to the inf files for installation. (CR#3754)
The driver no longer causes the checked version of Windows 2000 and NT4.0 to
assert during initialization. (CR#3755)
The driver will no longer cause a BSOD when used with Computer Associates tape
backup utilities. (CR#3756)
The driver will no longer cause drives to spin down when the system is shutdown. (CR#3760)
The driver will resume I/O in a more timely fashion after receiving a LOGO from a
target device. (CR#3761)
Changes from driver version 2.11a0
The driver will now operate more efficiently with more than one adapter in a system.
(CR# 3871)
The driver now will issue a request sense when an FCP_RSP is received with check
condition status, but no sense data. (CR#3872)
The driver will correctly reinitialize if moved from a public loop to a private loop.
(CR#3875)
The driver now reports robotic changes as a "Changer" instead of "MediumChanger".
(CR#3881)
The driver will now verify the adapter type for BIOS downloads. (CR#3876)
Changes from driver version 2.11a1
The driver no longer has an interrupt sharing race condition that could result in a
hung I/O when two or more adapters share an interrupt. (CR#3971)
The driver will no longer have I/Os hang in the deferred completion queue. (CR#3971)
Changes from configuration utility version 1.40a1
The ability to select default configurations for an adapter has been added. (CR#3757)
The configuration utility has had major cosmetic changes to allow incorporation of the
above change.
Changes from configuration utility version 1.41a0
The utility now sets the Clariion Maximum LUN value when changing from standard
settings to Clariion settings. (CR#3877)
Changes from configuration utility version 1.41a1
The utility now sets all of the Clariion specific parameters correctly. (CR#3877)
*** NOTE ABOUT MAPPING ***
Targets and LUNs may be added dynamically by scanning for new devices with
the Windows 2000 device manager after the mapping parameters have been changed
via the Emulex Configuration Utility.
If devices are unmapped with the Emulex Configuration Utility, the devices are
immediately removed from the system.
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.