Emulex LP9802 Download Drivers, Utilities, Manual, Firmware and BIOS

Introduction..............................................................................................................1
Emulex Boot Code Files....................................................................................1
Boot from SAN.........................................................................................................2
Windows Server 2008 and Windows Server 2003.............................................2
Configure Boot from SAN on Windows Server 2008 and Windows Server 2003 (x86 and x64)..........................................................2
Configure Boot from SAN on Windows Server 2008 and Windows Server 2003 (Itanium)..................................................................3
New Installation of Windows 2008 UEFI- Aware Operating System
on a UEFI-based x64 Server.................................................................3
Direct a UEFI-Based Server to a Windows Server 2008 OS Image (Installed as UEFI-Aware) Already Installed on the SAN.......................4
The GUID Partition Table......................................................................4
Install Windows Server 2008 on an FC Boot Disk (x86, x64 and Itanium)...5
Install Windows Server 2003 on an FC Boot Disk (x86, and x64
and Itanium)................................................................................................6
Linux and VMware.............................................................................................7
Configure Boot from SAN on Linux or VMware (x86 and x64).....................7
Configure Boot from SAN on Linux (PowerPC)...........................................7
Configure Boot from SAN on Linux (Itanium)..............................................7
Solaris...............................................................................................................8
Configure Boot from SAN on Solaris SFS (x86 and x64)............................8
Determine LUNs to Select for Boot from SAN.......................................8
Configure Boot from SAN on Solaris SFS (SPARC)....................................8
Configure Boot from SAN on Solaris LPFC (SPARC)..................................9
Install Solaris from a Network Image..................................................10
Install Solaris by Migrating an Image from a Local SCSI Disk.............11
Install, Update and Enable Boot Code...................................................................14
BIOS Utility............................................................................................................15
Start the BIOS Utility.................................................................................15
Enable an Adapter to Boot from SAN........................................................17
Configure Boot Devices...................................................................................17
Configure Adapter Parameters........................................................................21
Change the Default AL_PA (Arbitrated Loop Physical Address)................22
Change the PLOGI Retry Timer................................................................23
Change Topology......................................................................................24
Enable or Disable the Spinup Delay..........................................................25
Set Auto Scan...........................................................................................26
Enable or Disable EDD 3.0.......................................................................27
Enable or Disable the Start Unit Command...............................................28
Enable or Disable the Environment Variable.............................................29
Enable or Disable Auto Boot Sector..........................................................30
Change Link Speed...................................................................................31
Reset to Default Values.............................................................................32
Use Multi-Path Boot from SAN..................................................................33
OpenBoot..............................................................................................................34
Attribute Commands.................................................................................34
Functional Commands..............................................................................35
EFIBoot.................................................................................................................37
Install the EFI Utility..................................................................................37
Start the EFI Utility....................................................................................38

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Driver Images:

\rel_notes.txt the file you are reading
\DE311A5.PRG Lp8000 EFIBoot version 3.11a5
\CE311A5.PRG Lp9000 EFIBoot version 3.11a5
\HE311A5.PRG Lp9802 EFIBoot version 3.11a5
\QE311A5.PRG Lp850 EFIBoot version 3.11a5
\HE311A5.PRG Lp9802 EFIBoot version 3.11a5
\LE311A5.PRG Lp982 EFIBoot version 3.11a5
\TE311A5.PRG Lp10000 EFIBoot version 3.11a5
\ME311A5.PRG Lp1050 EFIBoot version 3.11a5
\EE311A5.PRG Lp101 EFIBoot version 3.11a5
\BE311A5.PRG Lp11000 EFIBoot version 3.11a5
\JE311A5.PRG Lp1150 EFIBoot version 3.11a5
\ZE311A5.PRG Lpe11000 EFIBoot version 3.11a5
\WE311A5.PRG Lpe1150 EFIBoot version 3.11a5
\ElxCli311a5.efi


***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Driver Images:

\310A7.txt The file you are reading
\DE310A7.PRG Lp8000 EFIBoot version 3.10A7
\QE310A7.PRG Lp850 EFIBoot version 3.10A7
\CE310A7.PRG Lp9000 EFIBoot version 3.10A7
\RE310A7.PRG Lp950 EFIBoot version 3.10A7
\HE310A7.PRG Lp9802 EFIBoot version 3.10A7
\LE310A7.PRG Lp982 EFIBoot version 3.10A7
\TE310A7.PRG Lp10000 EFIBoot version 3.10A7
\ME310A7.PRG Lp1050 EFIBoot version 3.10A7
\EE310A7.PRG Lp101 EFIBoot version 3.10A7
\ElxCli310A7.efi
***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Images:

\readme.txt this file you are reading
\SE310A6.PRG Lp7000 EFIBoot version 3.10a6
\DE310A6.PRG Lp8000 EFIBoot version 3.10a6
\CE310A6.PRG Lp9000 EFIBoot version 3.10a6
\HE310A6.PRG Lp9802 EFIBoot version 3.10a6
\QE310A6.PRG Lp850 EFIBoot version 3.10a6
\RE310A6.PRG Lp950 EFIBoot version 3.10a6
\LE310A6.PRG Lp982 EFIBoot version 3.10a6
\TE310A6.PRG Lp10000 EFIBoot version 3.10a6
\ME310A6.PRG Lp1050 EFIBoot version 3.10a6
\EE310A6.PRG Lp101 EFIBoot version 3.10a6
***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Driver Images:

\rel_notes.txt this file you are reading
\DE311A4.PRG Lp8000 EFIBoot version 3.11a4
\CE311A4.PRG Lp9000 EFIBoot version 3.11a4
\HE311A4.PRG Lp9802 EFIBoot version 3.11a4
\QE311A4.PRG Lp850 EFIBoot version 3.11a4
\HE311A4.PRG Lp9802 EFIBoot version 3.11a4
\LE311A4.PRG Lp982 EFIBoot version 3.11a4
\TE311A4.PRG Lp10000 EFIBoot version 3.11a4
\ME311A4.PRG Lp1050 EFIBoot version 3.11a4
\EE311A4.PRG Lp101 EFIBoot version 3.11a4
\BE311A4.PRG Lp11000 EFIBoot version 3.11a4
\JE311A4.PRG Lp1150 EFIBoot version 3.11a4
\ZE311A4.PRG Lpe11000 EFIBoot version 3.11a4
\WE311A4.PRG Lpe1150 EFIBoot version 3.11a4
\ElxCli311a4.efi


***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Driver Images:

\311A3.txt this file you are reading
\DE311A3.PRG Lp8000 EFIBoot version 3.11a3
\CE311A3.PRG Lp9000 EFIBoot version 3.11a3
\HE311A3.PRG Lp9802 EFIBoot version 3.11a3
\QE311A3.PRG Lp850 EFIBoot version 3.11a3
\HE311A3.PRG Lp9802 EFIBoot version 3.11a3
\LE311A3.PRG Lp982 EFIBoot version 3.11a3
\TE311A3.PRG Lp10000 EFIBoot version 3.11a3
\ME311A3.PRG Lp1050 EFIBoot version 3.11a3
\EE311A3.PRG Lp101 EFIBoot version 3.11a3
\BE311A3.PRG Lp11000 EFIBoot version 3.11a3
\JE311A3.PRG Lp1150 EFIBoot version 3.11a3
\IE311A3.PRG Lp111 EFIBoot version 3.11a3
\ZE311A3.PRG Lpe11000 EFIBoot version 3.11a3
\WE311A3.PRG Lpe1150 EFIBoot version 3.11a3
\YE311A3.PRG Lpe111 EFIBoot version 3.11a3
\ElxCli311a3.efi


***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit System
boot capability through the use of the EFI Shell. This EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61.

The EFIBoot supports:

(1) Multi-Topology : Fabric Point to Point; FC-AL: Private loop and Public
loop.

(2) EFI Protocols : Configuration, Component Name, Diagnostics and
Firmware Update Supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux Supported.

(4) Multi-Device path : Fibre/SCSI Device path Selectable through the Driver
configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs

(8) Multi-Mode : Supported.

(9) Multi-Utility : Setup and Firmware update supported.
Files included in this release:

EFI Byte Code Images:

\readme.txt this file you are reading
\SE300A9.PRG Lp7000 EFIBoot version 3.00a9
\DE300A9.PRG Lp8000 EFIBoot version 3.00a9
\CE300A9.PRG Lp9000 EFIBoot version 3.00a9
\HE300A9.PRG Lp9802 EFIBoot version 3.00a9
\QE300A9.PRG Lp850 EFIBoot version 3.00a9
\RE300A9.PRG Lp950 EFIBoot version 3.00a9
\LE300A9.PRG Lp982 EFIBoot version 3.00a9
\TE300A9.PRG Lp10000 EFIBoot version 3.00a9
\ME300A9.PRG Lp1050 EFIBoot version 3.00a9
\EE300A9.PRG Lp101 EFIBoot version 3.00a9
Native driver (SAL) Code Images:

\readme.txt this file you are reading
\HE300A9.PRG Lp9802 EFIBoot version 3.00a9
\LE300A9.PRG Lp982 EFIBoot version 3.00a9
\TE300A9.PRG Lp10000 EFIBoot version 3.00a9
\ME300A9.PRG Lp1050 EFIBoot version 3.00a9
\EE300A9.PRG Lp101 EFIBoot version 3.00a9
***** Important Note ******

(1) EFIBoot was not activated (Enabled)

If the adapter EFIBoot is not activated (enabled), this adapter will not be
configured. User must use LP6dutil or some other OS Utility to activate (enable)
the EFIBoot in order to make this card bootable.

Platform: Intel Itanium (64-bit) The current EFI (Extensible Firmware Interface) Boot provides 64-bit system
boot capability through the use of the EFI Shell. EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61 and 1.10.14.62.

EFIBoot supports:

(1) Multi-Topology : Fabric Point-to-Point; FC-AL: Private Loop and Public
Loop.

(2) EFI Protocols : Configuration, Component Name, Firmware Update, VPD,
LunCtrlAttrs and Diagnostics are supported.

(3) Operating System : Windows Server 2003 and Red-Hat Linux

(4) Multi-Device path : Fibre/SCSI device path selectable through the Driver
Configuration Protocol.

(5) Multi-Initiators : Up to 128 adapters in a system.

(6) Multi-Boot : Eight targets/controller selectable through the Driver
configuration Protocol.

(7) Multi-LUNs : Up to 4096 LUNs/target for a volume set device.
Up to 256 LUNs/target for a peripheral device.

(8) Multi-Mode : Peripheral and Volume Set devices are supported.

(9) Multi-Utility : Setup and firmware update are supported.
Files included in this release:

EFI Byte Code Driver Images:

\rel_notes.txt this file you are reading
\HE321A5.PRG Lp9802 EFIBoot version 3.21A5
\LE321A5.PRG Lp982 EFIBoot version 3.21A5
\TE321A5.PRG Lp10000 EFIBoot version 3.21A5
\ME321A5.PRG Lp1050 EFIBoot version 3.21A5
\EE321A5.PRG Lp101 EFIBoot version 3.21A5
\BE321A5.PRG Lp11000 EFIBoot version 3.21A5
\JE321A5.PRG Lp1150 EFIBoot version 3.21A5
\ZE321A5.PRG Lpe11000 EFIBoot version 3.21A5
\WE321A5.PRG Lpe1150 EFIBoot version 3.21A5
\YE321A5.PRG Lpe111 EFIBoot version 3.21A5
\ElxCli321A5.efi

***** Important Note ******

(1) EFIBoot was not enabled from loading to system memory:

If the adapter EFIBoot is not enabled from loading to system, this adapter
will not be configured. User must use LP6dutil or some other OS Utility to
enable the EFIBoot in order to make this card bootable.

(2) EFIBoot Bios was enabled to configure the adapter and No Link:

EFIBoot will wait for 15 seconds/adapter to confirm a link.

(3) If two or more adapters have same EFIBoot driver version, EFIBoot will
load only one driver.

(4) If there are adapters with different EFIBoot driver versions, EFIBoot
will load the highest version of the EFIBoot driver.

(5) In order to display Linkup speed, use the latest version of the firmware.

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\O150a8.txt The file you are reading

\SO150a8.PRG Lp7000 Open Firmware 1.50a8
\DO150a8.PRG Lp8000 Open Firmware 1.50a8
\CO150a8.PRG Lp9000 Open Firmware 1.50a8
\HO150a8.PRG Lp9802 Open Firmware 1.50a8
\TO150a8.PRG Lp10000 Open Firmware 1.50a8
\BO150a8.PRG Lp11000 Open Firmware 1.50a8
\ZO150a8.PRG Lpe11000 Open Firmware 1.50a8
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.50a8 ------------------------

1. The PCI device ID for Lpe11000 in make file wasn't a correct value,
and cause probe process does not find the Fcode image during POST.
The new release fixed this issue by update the correct PCI device
ID in make file. (CR18053)
----------------------- NEW CHANGES 1.50a7 ------------------------

1. The command of report-luns is not setup as external variable in
FCode, this caused the system fail to compile the report-luns into
the RAM during the boot time, and result a boot failure. The new
fix has setup the report-luns as external variable. (CR17926)
----------------------- NEW CHANGES 1.50a6 ------------------------

1. Added the Report LUN before Test Unit Ready command. (CR17835)

2. Added 60ms delay after PRLI and before the first Report Luns command
is sent out. (CR17836)

3. Changed the FCP Port Completion Timeout to 90 seconds for Start/Stop Unit
command, and others for 30 seconds timeout. (CR17837)

4. Fixed the bug on system hangs during "probe-scsi-all", because the timeout
for FCP completion was greater FCP Response. The new fix will be increased
FCP Response Timeout to 100 seconds for Start/Stop Unit command, and others
for 40 seconds timeout. (CR17838)

5. Fixed the bug for mishandle the return value of TUR when FC cable was not
connect properly during boot time and result an error message of
"STACK UNDERFLOW" issue. (CR17839)

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
This README applies to the following boot products:

SO133A1.PRG Lp7000 Open Boot 1.33A1
DO133A1.PRG Lp8000 Open Boot 1.33A1
CO133A1.PRG Lp9002 Open Boot 1.33A1
HO133A1.PRG Lp9802 Open Boot 1.33A1
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

--------------------------------------------------------------
----------------------- NEW CHANGES 1.32A0 ------------------------

1. Add the default topology mode without using "set-default-mode", and
the default topology mode is loop first, then point-to-point.

2. Set the default machine code to SUN machine instead of IBM. This
setting can takes care some of the SUN compatible machines. Also
change the default device-path for SUN and IBM machines.

3. Now able to boot with the new LP9802 Pegasus chipset.
----------------------- NEW CHANGES 1.33A0 ------------------------

1. Add firmware requested reset behavior for Error Attention 0x04.

2. Change the return stack value on fcp-luns to "0 0" when fcp-luns
command returns with an error.

3. Change the display LP9000 adapter on boot banner to LP9002.
----------------------- NEW CHANGES 1.33A1 ------------------------

1. Add the reset behavior for error attention 0x04 during runtime.

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

1. Open Boot Firmware Update Procedure

The Open Boot is loaded in the same way as a firmware update is
performed and is distributed as a .PRG file. It could download
through DOS based Lp6util if the adapter is first installed in a PC.
The procedure under DOS LP6DUTIL version 8.x is as follows:

(1) Option 5 Maintenance
(2) Select 1 Update Firmware.

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
readme.txt The file you are reading

SO140a0.PRG Lp7000 Open Boot 1.40a0
DO140a0.PRG Lp8000 Open Boot 1.40a0
CO140a0.PRG Lp9000 Open Boot 1.40a0
HO140a0.PRG Lp9802 Open Boot 1.40a0
TO140a0.PRG Lp10000 Open Boot 1.40a0

--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.40A0 ------------------------

1. In some server system, the default "ihandle/devname" is not in the
OBP library, and that will issue a wrong device path in devalias.
In this release, the new function "devname-path" will substate the
word "ihandle/devname", and makes correct device path in devalias.
----------------------- NEW CHANGES 1.33A2 ------------------------

1. Update the Emulex Copyright.
----------------------- NEW CHANGES 1.33A1 ------------------------

1. Add the reset behavior for error attention 0x04 during runtime.
----------------------- NEW CHANGES 1.33A0 ------------------------

1. Add firmware requested reset behavior for the Error Attention 0x04.

2. Change the return stack value on fcp-luns to "0 0" when fcp-luns
command returns with an error.

3. Change the display LP9000 adapter on boot banner to LP9002.

----------------------- NEW CHANGES 1.32A0 ------------------------

1. Add the default topology mode without using "set-default-mode", and
the default topology mode is loop first, then point-to-point.

2. Set the default machine code into SUN machine instead of IBM. This
setting can takes care some of the SUN compatible machine. Also
change the default device-path for SUN and IBM machine.

3. Able to boot with the new lp9802 HBA.

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
readme.txt The file you are reading

SO140a0.PRG Lp7000 Open Boot 1.40a0
DO140a0.PRG Lp8000 Open Boot 1.40a0
CO140a0.PRG Lp9000 Open Boot 1.40a0
HO140a0.PRG Lp9802 Open Boot 1.40a0
TO140a0.PRG Lp10000 Open Boot 1.40a0

--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.40A0 ------------------------

1. In some server system, the default "ihandle/devname" is not in the
OBP library, and that will issue a wrong device path in devalias.
In this release, the new function "devname-path" will substate the
word "ihandle/devname", and makes correct device path in devalias.
----------------------- NEW CHANGES 1.33A2 ------------------------

1. Update the Emulex Copyright.
----------------------- NEW CHANGES 1.33A1 ------------------------

1. Add the reset behavior for error attention 0x04 during runtime.
----------------------- NEW CHANGES 1.33A0 ------------------------

1. Add firmware requested reset behavior for the Error Attention 0x04.

2. Change the return stack value on fcp-luns to "0 0" when fcp-luns
command returns with an error.

3. Change the display LP9000 adapter on boot banner to LP9002.

----------------------- NEW CHANGES 1.32A0 ------------------------

1. Add the default topology mode without using "set-default-mode", and
the default topology mode is loop first, then point-to-point.

2. Set the default machine code into SUN machine instead of IBM. This
setting can takes care some of the SUN compatible machine. Also
change the default device-path for SUN and IBM machine.

3. Able to boot with the new lp9802 HBA.

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\readme.txt This file you are reading

\SO141a4.PRG Lp7000 Open Firmware 1.41a4
\DO141a4.PRG Lp8000 Open Firmware 1.41a4
\CO141a4.PRG Lp9000 Open Firmware 1.41a4
\HO141a4.PRG Lp9802 Open Firmware 1.41a4
\TO141a4.PRG Lp10000 Open Firmware 1.41a4

\SO141a4.img Lp7000 Open Firmware 1.41a4 for image file
\DO141a4.img Lp8000 Open Firmware 1.41a4 for image file
\CO141a4.img Lp9002 Open Firmware 1.41a4 for image file
\HO141a4.img Lp9802 Open Firmware 1.41a4 for image file
\TO141a4.img Lp10000 Open Firmware 1.41a4 for image file
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.41A4 ------------------------

1. The "ct-req" info. was erased by adding the "memory erase" function
before "ct-req" dma-free in previous release which cause the fcode
fail to see the target in fabric mode, the new fixed is removed the
"memory erase" function from "ct-req" before the dma-free. (CR11852)
----------------------- NEW CHANGES 1.41A3 ------------------------

1. In some system server, during the DR, there is a WARNING message
with memory leaked issue. The new release corrected this issue by
adding additional memory erase functions to set to 0 all the previously
obtained dma memory before the fcode released out the dma and virtual
address mappings by dma-map-out and dma-free. (CR11350 & CR11351)

2. In the universal boot code, during the boot time, there is an
warning message "Warning: Fcode sequence resulted in a net stack
depth change of 1", the new release fixed issue by remove some
unnecessarily call function in the fcode. (CR11538)

3. In some system, if the HBA was fail on the initialization by pulling
or remove the cable during boot time, the .properties command in the
ok prompt will display the wrong mode number of the HBA. The new
fixed will not show any model number of the HBA in this scenario. If
the system initize the HBA properly, it will display the correct
model number of the HBA. (CR9842)

4. Added the new instruction for using the alpa to set the boot id in
readme file. (CR9781)

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
readme.txt The file you are reading

SO141a2.PRG Lp7000 Open Firmware 1.41a2
DO141a2.PRG Lp8000 Open Firmware 1.41a2
CO141a2.PRG Lp9000 Open Firmware 1.41a2
HO141a2.PRG Lp9802 Open Firmware 1.41a2
TO141a2.PRG Lp10000 Open Firmware 1.41a2

SO141a2.img Lp7000 Open Firmware 1.41a2 for image file
DO141a2.img Lp8000 Open Firmware 1.41a2 for image file
CO141a2.img Lp9002 Open Firmware 1.41a2 for image file
HO141a2.img Lp9802 Open Firmware 1.41a2 for image file
TO141a2.img Lp10000 Open Firmware 1.41a2 for image file
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.41A2 ------------------------

1. In some system server, the HBA adapter does not get initialized
when dyanmic reconfiguration is initiated on entire PCI I/O assemby,
and shows the error message " Segmentation Fault" by the system's
Fcode interpreter. The cause of this issue was the Forth word
"erase" can't use in device memory on some system server during DR,
"erase" should only be used on system memory. This release fixed
the issue by replace and use "do-loop" to zero out device memory
area instead. (CR9683)

2. There is an issue regarding the variable declaration, because the
variable of "#lun-a0" was declare as CONSTANT, if some system's
Fcode interpreter try to change or modified this variable during
program execution after it is declared, it can corrupts the Open
Firmware dictionary entry with error message "default catch".
This release fixed the issue by replace the "CONSTANT" to "VALUE"
for declared the variable of (#lun-a0) in fcp-luns. (CR9717)


----------------------- NEW CHANGES 1.41A1 ------------------------

1. When bring up some system server, there is an error message "Cannot
Configure Port" and cause fail to config the HBA port, The cause of
this failure was Fcode need issue a reset command before initialize
the HBA. (CR9064)

2. In some system server, when system comes up from cool boot, there is
an error message "Cannot Initialize Port", and cause fail to config.
The new fix is add mailbox restart command before reset and config
the HBA. (CR9400)

Platform: SPARC, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\O150a9.txt This file you are reading

\DO150a9.PRG Lp8000 Open Firmware 1.50a9
\CO150a9.PRG Lp9000 Open Firmware 1.50a9
\HO150a9.PRG Lp9802 Open Firmware 1.50a9
\MO150a9.PRG Lp1050 Open Firmware 1.50a9
\TO150a9.PRG Lp10000 Open Firmware 1.50a9
\BO150a9.PRG Lp11000 Open Firmware 1.50a9
\ZO150a9.PRG Lpe11000 Open Firmware 1.50a9

\DO150a9.bin Lp8000 Open Firmware 1.50a9 for bin file
\CO150a9.bin Lp9002 Open Firmware 1.50a9 for bin file
\HO150a9.bin Lp9802 Open Firmware 1.50a9 for bin file
\MO150a9.bin Lp1050 Open Firmware 1.50a9 for bin file
\TO150a9.bin Lp10000 Open Firmware 1.50a9 for bin file
\BO150a9.bin Lp11000 Open Firmware 1.50a9 for bin file
\ZO150a9.bin Lpe11000 Open Firmware 1.50a9 for bin file
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.50a9 ------------------------

1. In some special array, Fcode in loop mode display incorrect LUNs on
show-children or probe-scsi-all command. The new fix takes care this
issue by adding the SCSI inquiry command before calling the show-luns
command in show-children, and set the numbers of retry on busy status
to limits of 10 times. (CR20261)

2. If the search eVPD data (V2) is located near at the end of 108 bytes in
the VPD field, thus sometimes can cause fails to display the whole string
of eVPD (V2) data. To fix this display VPD data on V2 field issue, the
new fix changed the VPD dumped entry index to 20*n bytes, and change
the VPD search area to 28 bytes, this can cover the whole maximum length
of 80 bytes on V2 data field. (CR20262)

3. Fcode fails to issue a retry command with a check condition if the sense
data returning a response code 71h (deffered errors). The new fix added
support deferred error (71h & 73h) and current error (72h) on sense data
returned to returning check condition status, this will continue apply retry
command. (CR20264)

4. In some blade server, after "scan", Fcode issue a "unmap-regs" at "close",
then re-open again to "check" the FC device for setting up the FC targets
into the SMS boot menu, somehow the re-maping FC device into the
system virtual address spaces function is not working properly, and
cause the system not able to recognize any FC devices during "check".
The new fix removed the "unmap-regs" call at the "close", and system can
continue complete setup the FC targets into the boot menu, and this special
condition only apply to some systems only. (CR19585)

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\O150A4.txt The file you are reading

\SO150a4.PRG Lp7000 Open Firmware 1.50a4
\DO150a4.PRG Lp8000 Open Firmware 1.50a4
\CO150a4.PRG Lp9000 Open Firmware 1.50a4
\HO150a4.PRG Lp9802 Open Firmware 1.50a4
\MO150a4.PRG Lp1005 Open Firmware 1.50a4
\TO150a4.PRG Lp10000 Open Firmware 1.50a4
\BO150a4.PRG Lp11000 Open Firmware 1.50a4
--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding (binding a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 1.50a4 ------------------------

1. Added the new link speed selection feature that uses the command
"set-link-speed" to select the desired link speed. The new link
speed now can support up to 4 Gigabaud, and the default link speed
is Auto Select. (CR16047)

2. Added the new Fcode Diag Switch feature that uses the command
"set-fdiag-switch" to turn the diag switch on/off. If the Diag
switch is on, the detail debug error message will be print out
during POST or boot time if there is any link/boot failure.(CR16048)

3. Bug fixed where HBA did not retry under a LOGO response and caused
fabric boot failure. (CR15707)

4. Bug fixed where HBA did not retry the START/STOP command on a SCSI
Queue Full response and caused fabric boot failure. The new number
of retries for Queue Full is up to 10 times and then give up.(CR16049)

5. Changed the new number of retry condition for SCSI Busy to retry
forever. (CR16050)

6. Added the host "port-wwn" and "node-wwn" of the HBA into the reg
property during POST time which was required by system to
allow to collect the Host wwpn/wwnn info during boot.(CR16051)

7. Fixed the bug on fail to report fcp-lun on software BOOT format.
(CR16052)

8. Added the new feature "show-wwpn-child". User can use this command
to show the LUNs target with the desired WWPN only instead of all
WWPNs and LUNs.(CR16053)

Platform: SPARC, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\readme.txt This file you are reading

\DO301a1.PRG Lp8000 Open Firmware 3.01a1
\CO301a1.PRG Lp9000 Open Firmware 3.01a1
\HO301a1.PRG Lp9802 Open Firmware 3.01a1
\MO301a1.PRG Lp1050 Open Firmware 3.01a1
\TO301a1.PRG Lp10000 Open Firmware 3.01a1
\BO301a1.PRG Lp11000 Open Firmware 3.01a1
\ZO301a1.PRG Lpe11000 Open Firmware 3.01a1
\UO301a1.PRG LPe12000 Open Firmware 3.01a1

--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

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

----------------------- NEW CHANGES 3.01a1 ------------------------

1. Some variable in the scsidisk file was create as local variable, and
cause system fail to boot with "Last Trap: Illegal Instruction" error
message. The new fixed by change some variables to external variable
instead of local variable. (CR27598)

----------------------- NEW CHANGES 3.01a0 ------------------------

1. Support 8Gb/s HBA.
----------------------- NEW CHANGES 3.00a2 ------------------------
1. Fixed the issue if the len size of the decode-unit on device path /fp
is large than 2 digits, the decode-unit is fails to convert text
unit-string, and cause system is not bootable, and boot command
disabled. (CR25215)

2. Fixed the issue on some systems the probe-scsi-all command fails
if the HBA has no link. (CR25036)

3. In PCI Configuration Register there is a bit to control the HBA
bus master capability (BME). In dual channel HBA when one of the
Bus Master Enable bit is cleared can cause other channel HBA DMA
to be stuck, and cause system hangs or failure during the boot
time. This release takes care this issue by set the BME bit on
forever. (CR24911)(CR25005)

4. If there is some unsolicited frame coming from the switch or service
provider, and the Boot code is not configure to response the FC-CT
Unsolicited, this can cause the system hangs during boot or scan targets.
In order not to sent any FC-CT request, the new release removed the
mailbox config_ring command. (CR25233)

Platform: SPARC, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\readme.txt This file you are reading

\SO300a2.PRG Lp7000 Open Firmware 3.00a2
\DO300a2.PRG Lp8000 Open Firmware 3.00a2
\CO300a2.PRG Lp9000 Open Firmware 3.00a2
\HO300a2.PRG Lp9802 Open Firmware 3.00a2
\MO300a2.PRG Lp1005DC Open Firmware 3.00a2
\TO300a2.PRG Lp10000 Open Firmware 3.00a2
\BO300a2.PRG Lp11000 Open Firmware 3.00a2
\ZO300a2.PRG Lpe11000 Open Firmware 3.00a2


--------------- NOTES and CAUTIONS ---------------------
** Ensure that critical files on local boot disk are backed up
as a measure of protection.

(1) This procedure assumes there is already a 'local' boot disk.

(2) The size of the intended (target) fibre channel disk should
be big enough to hold all the file systems, and swap slice
of the local current boot disk.

(3) As there will probably be more than one logical disk drive on
the fibre channel adapter it will be necessary to use persistent
binding ('nailing' a specific scsi id to a specific wwpn or did).

(4) It will be necessary to correlate the intended boot disk displayed
by the 'probe-scsi-all' command to the devices displayed by the
operating system.

----------------------------------------------------------------------
----------------------- NEW CHANGES 3.00a2 ------------------------
1. Fixed the issue if the len size of the decode-unit on device path /fp
is large than 2 digits, the decode-unit is fails to convert text
unit-string, and cause system is not bootable, and boot command
disabled. (CR25215)

2. Fixed the issue on some systems the probe-scsi-all command fails
if the HBA has no link. (CR25036)

3. In PCI Configuration Register there is a bit to control the HBA
bus master capability (BME). In dual channel HBA when one of the
Bus Master Enable bit is cleared can cause other channel HBA DMA
to be stuck, and cause system hangs or failure during the boot
time. This release takes care this issue by set the BME bit on
forever. (CR24911)(CR25005)

4. If there is some unsolicited frame coming from the switch or service
provider, and the Boot code is not configure to response the FC-CT
Unsolicited, this can cause the system hangs during boot or scan targets.
In order not to sent any FC-CT request, the new release removed the
mailbox config_ring command. (CR25233)

5. Changed the display format on Fcode version number in .properties screen
from ASCII to Hex for IBM machine. (CR25617)

6. Update the copyright date from .properties command. (CR24936)

Contains: x86 BootBIOS 1.71a0, OpenBoot 1.50a9 and EFIBoot 3.11a5 This Universal Boot version 5.02a1 contains:

(1) x86 BootBIOS version 1.71a0
(2) OpenBoot version 1.50a9
(3) EFIBoot version 3.11a5

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\502a1.txt this file you are reading
\HU502a1.PRG LP9802 Universal Boot
\TU502a1.PRG LP10000 Universal Boot
\BU502a1.PRG LP11000 Universal Boot
\ZU502a1.PRG LPe11000 Universal Boot
\elxcli311a5.efi EFI 3.11a5 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 2.01a2, OpenBoot 3.01a1 and EFIBoot 4.00a1 This Universal Boot version 5.03a0 contains:

(1) x86 BootBIOS version 2.01a2
(2) OpenBoot version 3.01a1
(3) EFIBoot version 4.00a1

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\503a0.txt this file you are reading
\HU503a0.PRG LP9802 Universal Boot
\TU503a0.PRG LP10000 Universal Boot
\BU503a0.PRG LP11000 Universal Boot
\ZU503a0.PRG LPe11000 Universal Boot
\UU503a0.PRG LPe12000 Universal Boot
\elxcli400a1.efi EFI 4.00a1 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 2.00a1, OpenBoot 1.50a9 and EFIBoot 3.11a5 This Universal Boot version 5.02a4 contains:

(1) x86 BootBIOS version 2.00a1
(2) OpenBoot version 1.50a9
(3) EFIBoot version 3.11a5

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\502a4.txt this file you are reading
\HU502a4.PRG LP9802 Universal Boot
\TU502a4.PRG LP10000 Universal Boot
\BU502a4.PRG LP11000 Universal Boot
\ZU502a4.PRG LPe11000 Universal Boot
\elxcli311a5.efi EFI 3.11a5 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 1.70a3, OpenBoot 1.50a4 and EFIBoot 3.10a7 This Universal Boot version 5.01a4 contains:

(1) x86 BootBIOS version 1.70a3
(2) OpenBoot version 1.50a4
(3) EFIBoot version 3.10a7

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU501A4.PRG Lp9802 Universal Boot
\TU501A4.PRG Lp10000 Universal Boot
\BU501A4.PRG Lp11000 Universal Boot
\elxcli310a7.efi EFI 3.10a7 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 1.70a1, OpenBoot 1.41a4 and EFIBoot 3.10a6 This Universal Boot version 5.01a0 contains:

(1) x86 BootBIOS version 1.70a1
(2) OpenBoot version 1.41a4
(3) EFIBoot version 3.10a6

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU501A0.PRG Lp9802 Universal Boot
\TU501A0.PRG Lp10000 Universal Boot
\elxcli310a6.efi EFI 3.10a6 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 1.70a1, OpenBoot 1.41a4 and EFIBoot 3.00a9 This Universal Boot version 5.00a5 contains:

(1) x86 BootBIOS version 1.70a1
(2) OpenBoot version 1.41a4
(3) EFIBoot version 3.00a9

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU500A5.PRG Lp9802 Universal Boot
\TU500A5.PRG Lp10000 Universal Boot
\elxcli.efi EFI 3.00a9 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.
/*-------------------------------------------------------------------------------*/
/* History */
/*-------------------------------------------------------------------------------*/
Problems Fixed, Features added or Other Updates Since 5.00a4:
-----------------------------------------------------------------------------------

(1) Fixed the drivers had to be connected more than once: can now boot without
connecting through EFI Shell.

(2) Fixed when Firmware Update Protocol functions called, not able to create/
delete partition on targets: can now create/delete partition on targets
Problems Fixed, Features added or Other Updates Since 5.00a1:
-----------------------------------------------------------------------------------

(1) Fixed CR9254: Updated Readme document.

contains: x86 BootBIOS 1.70a3, OpenBoot 1.50a8 and EFIBoot 3.11a5 This Universal Boot version 5.01a9 contains:

(1) x86 BootBIOS version 1.70a3
(2) OpenBoot version 1.50a8
(3) EFIBoot version 3.11a5

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU502A0.PRG LP9802 Universal Boot
\TU502A0.PRG LP10000 Universal Boot
\BU502A0.PRG LP11000 Universal Boot
\ZU502A0.PRG LPe11000 Universal Boot
\elxcli311a5.efi EFI 3.11a5 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 1.70a3, OpenBoot 1.50a8 and EFIBoot 3.11a4 This Universal Boot version 5.01a9 contains:

(1) x86 BootBIOS version 1.70a3
(2) OpenBoot version 1.50a8
(3) EFIBoot version 3.11a4

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU501A9.PRG LP9802 Universal Boot
\TU501A9.PRG LP10000 Universal Boot
\BU501A9.PRG LP11000 Universal Boot
\ZU501A9.PRG LPe11000 Universal Boot
\elxcli311a4.efi EFI 3.11a4 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

contains: x86 BootBIOS 1.70a3, OpenBoot 1.50a4 and EFIBoot 3.11a3 This Universal Boot version 5.01a7 contains:

(1) x86 BootBIOS version 1.70a3
(2) OpenBoot version 1.50a4
(3) EFIBoot version 3.11a3

For detailed information about x86 BootBIOS, please refer to section II below,
for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can
boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In other
words, the platform is transparent and the user should not be concerned with any
differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot.

Universal Boot is a complete image, whenever it is enabled by any Emulex OS
utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This
is also true for disable.
Files included in this release:

\readme.txt this file you are reading
\HU501A7.PRG LP9802 Universal Boot
\TU501A7.PRG LP10000 Universal Boot
\BU501A7.PRG LP11000 Universal Boot
\ZU501A7.PRG LPe11000 Universal Boot
\elxcli311a3.efi EFI 3.11a3 Driver
Universal Boot Load Procedure

The Light Pulse Universal Boot is distributed as a .PRG file. This file may be
downloaded to the Adapter using the firmware upgrade procedure with the following
Utility in Various systems.

1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download
Universal Boot in EFI based systems.

2. LP6DUTIL.EXE : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for user
interface how to download EFIBoot in DOS PCI systems.

3. LPUTILNT : Windows Miniport Driver.

Please refer to the utility user manual for details on using the above tool.

4. Emulex Configuration Tool : Windows Port Driver.

Please refer to the elxcfg user manual for details on using the above tool.

Platform: Intel (32-bit) The current BIOS provides x86 boot capability through the use of INT13 system
BIOS calls. The BIOS supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
(2) Multi-initiators: Up to 64 adapters in a system
(3) Multi-LUNs: Up to 256 LUNs
(4) Multi-boot: Complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): Supports both EDD 3.0 and EDD 2.1
depending selection in BIOS Utility.
(6) Boot fail over feature: There are eight boot entries that can be configured.
If the first boot entry fails the system is still able to boot from the
second configured boot entry and so on.
B170A1.txt the file you are reading

SB170A1.PRG Lp7000 BIOS version 1.70A1
DB170A1.PRG Lp8000 BIOS version 1.70A1
CB170A1.PRG Lp9000 BIOS version 1.70A1
HB170A1.PRG Lp9802 BIOS version 1.70A1
TB170A1.PRG Lp10000 BIOS version 1.70A1

QB170A1.PRG Lp850 BIOS version 1.70A1
RB170A1.PRG Lp950 BIOS version 1.70A1
LB170A1.PRG Lp982 BIOS version 1.70A1
MB170A1.PRG Lp1050 BIOS version 1.70A1
EB170A1.PRG Lp101 BIOS version 1.70A1

Although a specific BIOS file for the LP6000 does not exist, all current
versions of BIOS will scan and process any LP6000 Adapters in the system.

***** Important Note ******

(1) BIOS downloading

This version of BIOS image has increased size from 44K to 48K. As a result, it might
fail during the downloading of the BIOS .prg file. One way to correct the problem
is to download the firmware .AWC file WITHOUT the BIOS image
(for example: dd390a7.awc). Then, download the BIOS .prg file.
(2) BIOS was not activated (Enabled)

If the adapter BIOS is not activated (enabled) by LP6dutil or other O.S. utility,
this adapter would not be configured. Also, there is "No BIOS support" message next
to this adapter in BIOS Utility. User must use LP6dutil or other O.S. Utility to
activate (enabled) the BIOS in order to make this card bootable.

Platform: Intel (32-bit) The current BIOS provides x86 boot capability through the use of INT13 system
BIOS calls. The BIOS supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
(2) Multi-initiators: Up to 64 adapters in a system
(3) Multi-LUNs: Up to 256 LUNs
(4) Multi-boot: Complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): Supports both EDD 3.0 and EDD 2.1
depending selection in BIOS Utility.
(6) Boot fail over feature: There are eight boot entries that can be configured.
If the first boot entry fails the system is still able to boot from the
second configured boot entry and so on.
\B163A2.txt this file you are reading

\SB163A2.PRG Lp7000 BIOS version 1.63a2
\DB163A2.PRG Lp8000 BIOS version 1.63a2
\CB163A2.PRG Lp9000 BIOS version 1.63a2
\HB163A2.PRG Lp9802 BIOS version 1.63a2
\TB163A2.PRG Lp10000 BIOS version 1.63a2

\QB163A2.PRG Lp850 BIOS version 1.63a2
\RB163A2.PRG Lp950 BIOS version 1.63a2
\LB163A2.PRG Lp982 BIOS version 1.63a2
\MB163A2.PRG LP1050 BIOS version 1.63a2

Although a specific BIOS file for the LP6000 does not exist, all current
versions of BIOS will scan and process any LP6000 Adapters in the system.

***** Important Note ******

(1) BIOS downloading

This version of BIOS image has increased size from 44K to 48K. As a result, it might
fail during the downloading of the BIOS .prg file. One way to correct the problem
is to download the firmware .AWC file WITHOUT the BIOS image
(for example: dd390a7.awc). Then, download the BIOS .prg file.
(2) BIOS was not activated (Enabled)

If the adapter BIOS is not activated (enabled) by LP6dutil or other O.S. utility,
this adapter would not be configured. Also, there is "No BIOS support" message next
to this adapter in BIOS Utility. User must use LP6dutil or other O.S. Utility to
activate (enabled) the BIOS in order to make this card bootable.

Platform: Intel (32-bit) The adapter boot BIOS provides x86 boot capability through the use of INT13
system BIOS calls. The adapter Boot BIOS supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
topologies.
(2) Multi-initiators: The adapter BIOS supports up to 64 Emulex LightPulse
adapters in a system.
(3) Multi-LUNs: The adapter BIOS supports up to 256 LUNs.
(4) Multi-boot: The adapter BIOS complies with the BIOS Boot Specification
(BBS).
(5) EDD (Enhanced Disk Drive Services): The adapter BIOS supports both the
EDD 3.0 and EDD 2.1 specifications depending on the selection in the
adapter BIOS configuration utility.
(6) Boot fail over feature: There are eight boot entries that can be
configured in the adapter BIOS configuration utility. If the first boot
entry fails the system is still able to boot from the second configured
boot entry and so on.
\2.00a1.txt this file you are reading

\DB200a1.PRG Lp8000 adapter boot BIOS version 2.00a1
\CB200a1.PRG Lp9000 adapter boot BIOS version 2.00a1
\HB200a1.PRG Lp9802 adapter boot BIOS version 2.00a1
\TB200a1.PRG Lp10000 adapter boot BIOS version 2.00a1
\BB200a1.PRG Lp11000 adapter boot BIOS version 2.00a1
\QB200a1.PRG Lp850 adapter boot BIOS version 2.00a1
\RB200a1.PRG Lp950 adapter boot BIOS version 2.00a1
\LB200a1.PRG Lp982 adapter boot BIOS version 2.00a1
\MB200a1.PRG Lp1050 adapter boot BIOS version 2.00a1
\JB200a1.PRG Lp1150 adapter boot BIOS version 2.00a1
\EB200a1.PRG Lp101 adapter boot BIOS version 2.00a1
\YB200a1.PRG LPe111 adapter boot BIOS version 2.00a1
\WB200a1.PRG LPe1150 adapter boot BIOS version 2.00a1
\ZB200a1.PRG LPe11000 adapter boot BIOS version 2.00a1

***** Important Note ******

(1) BIOS downloading

The adapter boot BIOS image has increased in size to 48K. As a result, it might
fail during the downloading of the BIOS .prg file. One way to correct the
problem is to download the firmware .AWC or file WITHOUT the BIOS image
(for example: cd393a0.awc) and then download the adapter boot BIOS .PRG file.
Firmware where only .ALL files are available contain firmware only, so the above
precautions do not apply.
(2) BIOS was not activated (Enabled)

If the adapter boot BIOS is not enabled by DOSLPCFG, LP6DUTIL or an Emulex O.S.
configuration utility, the adapter and the drives connected to the adapter
cannot not be configured to be used to boot the system. In addition if there is
a "No BIOS support" message displayed next to this adapter in the adapter BIOS
configuration utility the user must use DOSLPCFG or other Emulex O.S.
configuration utility to enable the adapter boot BIOS in order to allow this adapter
to be used a bootable controller by the host system.

Platform: Intel (32-bit) The current BIOS provides x86 boot capability through the use of INT13 system
BIOS calls. The BIOS supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
(2) Multi-initiators: Up to 64 adapters in a system
(3) Multi-LUNs: Up to 256 LUNs
(4) Multi-boot: Complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): Supports both EDD 3.0 and EDD 2.1
depending on the selection in the BIOS Utility.
(6) Boot fail over feature: There are eight boot entries that can be configured.
If the first boot entry fails the system is still able to boot from the
second configured boot entry and so on.

\readme.txt this file you are reading

\SB170a3.PRG Lp7000 BIOS version 1.70a3
\DB170a3.PRG Lp8000 BIOS version 1.70a3
\CB170a3.PRG Lp9000 BIOS version 1.70a3
\HB170a3.PRG Lp9802 BIOS version 1.70a3
\TB170a3.PRG Lp10000 BIOS version 1.70a3

\QB170a3.PRG Lp850 BIOS version 1.70a3
\RB170a3.PRG Lp950 BIOS version 1.70a3
\LB170a3.PRG Lp982 BIOS version 1.70a3
\MB170a3.PRG Lp1050 BIOS version 1.70a3
\EB170a3.PRG Lp101 BIOS version 1.70a3

***** Important Note ******

(1) BIOS downloading

This version of BIOS image has increased size from 44K to 48K. As a result, it might
fail during the downloading of the BIOS .prg file. One way to correct the problem
is to download the firmware .AWC file WITHOUT the BIOS image
(for example: dd390a7.awc). Then, download the BIOS .prg file.

(2) BIOS was not activated (Enabled)

If the adapter BIOS is not activated (enabled) by LP6dutil or other O.S. utility,
this adapter would not be configured. Also, there is "No BIOS support" message next
to this adapter in the BIOS Utility. User must use LP6dutil or other O.S. Utility
to activate (enabled) the BIOS in order to make this card bootable.

Platform: Intel (32-bit) The current BIOS provides x86 boot capability through the use of INT13 system
BIOS calls. The BIOS supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
(2) Multi-initiators: Up to 64 adapters in a system
(3) Multi-LUNs: Up to 256 LUNs
(4) Multi-boot: Complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): Supports both EDD 3.0 and EDD 2.1
depending selection in BIOS Utility.
(6) Boot fail over feature: There are eight boot entries that can be configured.
If the first boot entry fails the system is still able to boot from the
second configured boot entry and so on.
\B171A0.txt this file you are reading

\DB171a0.PRG Lp8000 BIOS version 1.71a0
\CB171a0.PRG LP9000 BIOS version 1.71a0
\HB171a0.PRG LP9802 BIOS version 1.71a0
\TB171a0.PRG LP10000 BIOS version 1.71a0
\BB171a0.PRG LP11000 BIOS version 1.71a0
\ZB171a0.PRG LPe11000 BIOS version 1.71a0

\QB171a0.PRG Lp850 BIOS version 1.71a0
\RB171a0.PRG LP950 BIOS version 1.71a0
\LB171a0.PRG LP982 BIOS version 1.71a0
\MB171a0.PRG LP1050 BIOS version 1.71a0
\JB171a0.PRG LP1150 BIOS version 1.71a0
\YB171a0.PRG LPe111 BIOS version 1.71a0
\EB171a0.PRG LP101 BIOS version 1.71a0
\WB171a0.PRG LPe1150 BIOS version 1.71a0
***** Important Note ******

(1) BIOS downloading

This version of BIOS image has increased size from 44K to 48K. As a result, it might
fail during the downloading of the BIOS .prg file. One way to correct the problem
is to download the firmware .AWC file WITHOUT the BIOS image
(for example: dd390a7.awc). Then, download the BIOS .prg file.
(2) BIOS was not activated (Enabled)

If the adapter BIOS is not activated (enabled) by LP6dutil or other O.S. utility,
this adapter would not be configured. Also, there is "No BIOS support" message next
to this adapter in BIOS Utility. User must use LP6dutil or other O.S. Utility to
activate (enable) the BIOS in order to make this card bootable.

Compatibility:

This kit supports the LP9802 series of PCI host adapters.

This kit includes the following files:

README.TXT The file you are reading

HD100A4.ALL All firmware components, no boot
HD100A4.DWC Functional firmware, no kernel/loader, no boot

HDEFAULT.CFL Configuration file for restoring default PCI_ID
HFPLUS1.CFL Configuration file to allow PCI ID = F981
HFPLUS2.CFL Configuration file to allow PCI ID = F982
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5

LP6DUTIL.EXE DOS-based diagnostic utility 9.0A10
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.0A10
Changes and Corrections:

PLEASE NOTE:
This firmware is not backward-compatible with Emulex legacy HBAs.
This product has significant changes in file naming and firmware
download methods. The HBA internal firmware structure is unlike
the traditional Emulex Light Pulse products.

The traditional .AWC files have been replaced with the
.ALL file. Downloading this file no longer indiscriminately
erases or resets any previously installed boot program
settings. Please see "Cautions and Warnings" for details.

The LP6DUTIL utility version 9.0a10 represents a departure from
the traditional command-line structure, and it now uses a
graphical-type user interface. It also uses a different method
of implementing scripts than did earlier LP6DUTIL versions.
Please read the LP6DUTIL document file for more information.

-- Changes in firmware version 1.00A4: --

Added code to enter old-port P2P mode in the manner required by
the Pegasus products. (CR 4966)

Added VPD compliance with PCI spec 2.2. The vendor-specific
method of VPD access has not been affected. (CR 5109, 5110,
6179)

Corrected an error which would cause the board to hang in
certain situations when accessing VPD or when the max tx dma
interrupt was set. (CR 5165)

A zero-length BDE is now processed without issuing an error.
(CR 5236)

Correct loop map information is now assured on READ_LA mailbox
command. (CR 5264)

ELS responses for firmware-created ELS requests (e.g. echo) were
corrected. (CR 5267)

Correct exchange ID is now verified when RRQ is received. (CR 5295)

The possibility of generating an extra LIP phase during loop init
was eliminated. (CR 5296)

Added interlocks to prevent subsequent mailbox commands from being
accepted before completion of the current mailbox command.
(CR 5297)

Compatibility:

This kit supports the LP9802 series of PCI host adapters.

This kit includes the following files:

README.TXT The file you are reading

HD100A2.ALL All firmware components, no boot
HD100A2.DWC Functional firmware only (no kernel/loader, no boot)

HDEFAULT.CFL Configuration file for restoring PCI_ID to default
HFPLUS1.CFL Configuration file to allow PCI ID = F981
HFPLUS2.CFL Configuration file to allow PCI ID = F982
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5

LP6DUTIL.EXE DOS-based diagnostic utility 9.0A9
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.0A9
Changes and Corrections:

This is the first release of firmware for this product.
Versions prior to this one were used for internal prototype test
runs, and were not formally released.

PLEASE NOTE:
This firmware is not backward-compatible with Emulex legacy HBAs.
This product has significant changes in file naming and firmware
download methods. The HBA internal firmware structure is unlike
the traditional Emulex Light Pulse products.

The traditional .AWC files have been replaced with
the .ALL file. Uploading this file no longer indiscriminately
erases or resets any previously installed boot program
settings. Please see "Cautions and Warnings" for details.

The LP6DUTIL utility version 9.0a9 represents a departure from
the traditional command-line structure, and it now uses a
graphical-type user interface. It also uses a different method
of implementing scripts than did earlier LP6DUTIL versions.
Please read the LP6DUTIL document file for more information.
Known Issues:
The following issues have been reported at the time of publication.
These issues may not yet have been verified or confirmed and may
apply to another product, such as the driver or hardware.

Loading the .ALL file without the boot code no longer automatically
disables the boot program. This is "as designed", and is not a
defect. If you want to disable the boot capability, use the
firmware utility.
Cautions and Warnings:

If you use LP6DUTIL to load the firmware into the HBA, you must
use version v9.0A9 or greater. The latest version of LP6DUTIL
is included in this kit.

Downloading the .ALL file will not erase boot code settings.
For details, please see "Known Issues".

Compatibility:

This kit supports the LP9802 PCI host adapter.

This kit includes the following files:

README.TXT The file you are reading

HD181A1.ALL All firmware components, no boot
HD181A1.DWC Functional firmware, no kernel/loader, no boot

HDEFAULT.CFL Configuration file for restoring default PCI_ID
HFPLUS1.CFL Configuration file to allow PCI ID = F981
HFPLUS2.CFL Configuration file to allow PCI ID = F982
FDEFPEG.CFL Configuration file to allow PCI ID = 1AE5

LP6DUTIL.EXE DOS-based diagnostic utility 9.0A13
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.0A13
Changes and Corrections:

-- These are the changes since 1.01A2, which was the previous
-- released version for the Pegasus HBA product line.

Provided merged code base modules for Thor and Pegasus products.
(CR 8569, 8570, 8571)

Several changes were implemented to more effectively address the HBA
reset response required by Power Management Reset and Dynamic Host
Reconfiguration. Modified PCI and PCIX setup routines, allowed earlier
access to expansion ROM, and improved FLASH access routines, all of which
provide faster access after an HBA reset.
(CR 8592, 8634, 8635, 9398, 7097, 6961, 6941, 5204, 8637, 8638, 7982)

Development, desk checks and source code review found possible problems
which had no reported instances of failure.
(CR 8529, 8491, 8789, 8790, 8791, 8434, 9394, 9320, 9170, 8439, 8489, 8490,
8176, 8474, 8475)

Added or refined features as per customer request.
(CR 8473, 8222, 8472, 8174, 8478, 8479)

Improved handling of parity error with host pointers in HBA SLIM memory.
(CR 8435)

Implemented a method recommended by the chip manufacturer to prevent a
rare occurrance of a single bit change in FLASH memory during repeated
read and reset of the HBA. (CR 8630)

Released buffers if exchange aborted during frame reception, to avoid
buffer credit stall. (CR 9239)

Improved handling of exchange buffers in the process of being transmitted
when an abort is received. (CR 9240)

To break an occasional hang during negotiation in p2p-first autotopology
mode with a switch, we now toggle the receiver after 4 seconds of
attempted negotiation and force p2p mode. (CR 8946, 8927, 9231)

Fixed detection of incorrectly set FCTL_RECIPIENT bit. HBA behavior now
fits the spec by dropping the frame. (CR 8175, 8476, 8477)

Corrected target mode handling of data sequences with no F_CTL End
Sequence. (CR 8530, 8531, 8532)

Compatibility:

This kit supports the LP9802 PCI host adapter.

This kit includes the following files:

README.TXT The file you are reading

HD101A2.ALL All firmware components, no boot
HD101A2.DWC Functional firmware, no kernel/loader, no boot

HDEFAULT.CFL Configuration file for restoring default PCI_ID
HFPLUS1.CFL Configuration file to allow PCI ID = F981
HFPLUS2.CFL Configuration file to allow PCI ID = F982
FDEFPEG.CFL Configuration file to allow PCI ID = 1AE5

LP6DUTIL.EXE DOS-based diagnostic utility 9.0A13
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.0A13
Changes and Corrections:

PLEASE NOTE:
This firmware is not backward-compatible with Emulex legacy HBAs.
This product has significant changes in file naming and firmware
download methods. The HBA internal firmware structure is unlike
the traditional Emulex Light Pulse products.

The traditional .AWC files have been replaced with the .ALL file.
Downloading an .ALL or .DWC file no longer erases or resets any
previous boot code or settings. Please see "Known Issues"
for details.

The LP6DUTIL utility version 9.0a13 represents a departure from
the traditional command-line structure, and it now uses a
graphical-type user interface. It also uses a different method
of implementing scripts than did earlier LP6DUTIL versions.
Please read the LP6DUTIL document file for more information.
-- Changes in firmware version 1.01a2: --

Increase "wait for active" timeout in point-to-point mode to allow more
time for optical module sync-up.
(CR 8206, 8208)
-- Changes in firmware version 1.01a1: --

Added support for out-of-order ACKs within a range of 1 to 7 from the
expected sequence count. (CR 5263, 5266, 6792)

On rare occasion (once every 200 to 4000 attempts), two Pegasus HBAs
would get stuck in sync while trying to bring up the link between them.
Added a 250 mS timeout and a means to force a retry by both HBAs.
(CR 7704,7705)

A method of handling internal buffers caused a problem when changing
to another port on a switch. We now insure that a change in topology
triggers proper buffer handling for this situation. (CR 6895, 7706)

Added a timeout function to avoid a possible stall waiting for ACK1.
(CR 7547, 7730)

Compatibility:

This kit supports the LP9802 PCI host adapter.

This kit includes the following files:

README.TXT The file you are reading

HD191A1.ALL All firmware components, no boot

LP6DUTIL.EXE DOS-based diagnostic utility 9.3a4
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.3a4

Several files, such as the .DWC file and .CFL files, have been
eliminated from this kit in order to simplify the update process and
ensure correct operation of the updated HBA.
Changes and Corrections:

-- Changes and corrections between 1.91a1 and 1.91a0:

Corrected an uninitialized variable in the Linux key check. (CR 14533)

Changed XRI buffer return behavior so that buffers are normally
returned without error in cases where the exchange has completed.
(CR 13413)

Improved handling of stale frames from completed exchanges so they
can no longer affect new exchanges. (CR 14479)
-- Changes and corrections between 1.91a0 and 1.90a4:

Ensure that resynch happens after link down. This remedies a problem
encountered only when connecting test equipment to the HBA. (CR 10135,
13634, 14443)

Ensure that we have at least one credit when doing REG LOGIN to
fabric port. (CR 12460, 12466, 14357)

Response to an unsolicited IP broadcast frame was corrected to comply
with FC spec. (CR 11019, 14596)

Interrupt handling of a PCI abort has been corrected so that the rare
out-of-order interrupt is no longer regarded as a cause for resetting
the HBA. (CR 11169, 13635, 14052, 14449)

Improved response and handling of Expansion ROM access requests
to enhance and ensure correct operation.
(CR 11170, 12155, 12354, 14361)

Allow use of a revised FLASH memory chip [Intel J3 rev C].
(CR 12213, 13078, 14451)

Ensure that no frames waiting for resources are accidentally released
on to the link when killing exchanges. (CR 12183, 13630, 14591, 14447)

Corrected a problem where the download of corrupted firmware would
return the proper error, but refuse any further commands.
(CR 13241, 14584)

Improved handling of the RESET_RING command to completely initialize
the ring and no longer return an unnecessary response.
(CR 13325, 13631, 13632, 13374, 14446, 14450, 14589)

Improved response to give priority to outstanding ACKs when in
target mode under heavy load. (CR 13327, 13633, 14445)

Added code to correctly process and count error counter overflows.
(CR 13328, 13629, 14444)

Compatibility:

This kit supports the LP9802 PCI host adapter.

This kit includes the following files:

README.TXT The file you are reading

HD190A4.ALL All firmware components, no boot
HD190A4.DWC Functional firmware, no kernel/loader, no boot

HDEFAULT.CFL Configuration file for restoring default PCI_ID
HFPLUS1.CFL Configuration file to allow PCI ID = F981
HFPLUS2.CFL Configuration file to allow PCI ID = F982
FDEFPEG.CFL Configuration file to allow PCI ID = 1AE5

LP6DUTIL.EXE DOS-based diagnostic utility 9.2a4
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.2a4
Changes and Corrections:

-- Changes and corrections between 1.90a0 and 1.81a1.

Added or refined features as per customer requests.
(CR 8663, 8636, 9182, 10120, 10574, 9811, 9864)

Corrected an internal word misalignment so that the SLI-1 mailbox
command returns the firmware revision data properly. (CR 9390)

Improved I/O transaction performance. (CR 10663)

Corrected a switch login problem in point-to-point-only mode with certain
transceivers. (CR 9406)

Change made to recognize a CLOSE in point-to-point mode. This corrects a
deadlock problem in OldPort mode when connecting to a switch.
(CR 9438)

Corrected an HBA hang / mailbox timeout problem after a disconnect with
an HP-UX system. (CR 9682, 10585)

Corrected an RPI handling problem between the HP-UX driver and firmware
when cables are swapped between two different HBAs. (CR 9714)

The firmware now accommodates the use of ST FLASH memory parts.
(CR 10089)

Corrected a rare condition where an incorrect IOCB could be returned to
the host if the exchange is aborted before the buffer list has been queued
by the host. (CR 10117, 10058)

Corrected a rare instance where the wrong exchange is aborted and the
IO_TAG is eventually reused. The abort is now matched to the correct
exchange by validating the IO_TAG. (CR 10118, 9809)

Corrected a response problem with an RRQ timeout. ABTS is now sent
if the RRQ to the host times out. (CR 10119, 9364)

Corrected the reason and explanation codes given to the tape drive
in an LS_RJT response to REC ELS. This allows the Solaris host to
retry the command. (CR 10121, 9489)

Improved resource depletion handling for small transfers.
(CR 10124, 9274)

Corrected a problem where a raid array would not be seen by two servers
that were connected into the same switch. (CR 10126, 10461, 9907)

FCP recovery has been improved by including the proper reason codes
for tapes. (CR 10173, 10575, 9530)

Compatibility:

This kit supports the LP9802 PCI host adapter.

This kit includes the following files:

README.TXT The file you are reading

HD191A5.ALL All firmware components, no boot

LP6DUTIL.EXE DOS-based diagnostic utility 9.3a6
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.3a6
Changes and Corrections:

-- Changes and corrections between 1.91a5 and 1.91a4:

Ensure proper DMA behavior upon channel reset. (CR 19091, 19096)

Pre-initialize configuration region to avoid errors if host reads it
before the initial configuration is complete. (CR 19177, 19187, 19188)

-- Changes and corrections between 1.91a4 and 1.91a3:

Several issues with FLASH access during reset of only one port have been
eliminated by synchronizing the flash access speed of both ports.
(CR 17472, 17475, 17539, 17542, 17625, 17626, 17647, 17648, 18212,
18213, 18307)

An exceptionally rigorous test produced a timeout where the rings other
than ring 0 were ignored. The firmware has been corrected to check all
four rings. (CR 15952, 16262, 16279, 16280, 16281, 16282, 16283)

Improved handling of queued data from tape. Recovery of CRC errors
no longer indirectly trigger an abort on slow PCI environments.
(CR 17410, 17510, 17520, 17608, 17610, 17633, 17634, 17635, 18280,
18343)

Changed handling of dropped FCP-2 tape data frames. Upon detecting a
missing frame, the firmware now automatically requests a retransmission
from the drive. (CR 14851, 15184, 16975, 18329)

The firmware now correctly handles intentional IOCB starvation.
(CR 16818, 16873, 16972, 17211)

An I/O timeout during tape operation was eliminated by delaying
processing of any FCP2 errors during discovery. (CR 17363, 18287, 18288)

Improved handling of linked FCP commands in order to avoid timeouts.
(CR 15602, 16114)

Implemented a workaround to avoid a hardware DMA overrun condition.
(CR 17780, 17834, 17908)

To avoid buffer deadlocks, the HBA now completes any existing DMA for
an exchange prior to allocating more free buffers. (CR 16862, 16874,
16973, 18347)

Dump command now correctly dumps memory above 1MB. (CR 18374)

Improved buffer handling logic during error conditions to avoid aborted
exchanges. (CR 17701, 18291, 18292, 18349)

Improved handling of erroneously-sized ECHO responses. (CR 18330,
18332, 18333)

The HBA now transmits all outstanding ACKs before processing any
previously blocked data. (CR 16354, 18334, 18335)

The transmit queue is now restarted after ACK handling to avoid a
transmit hang in Class 2. (CR 18362, 18363, 18364)

Introduction.............................................................................................................. 1
Prerequisites ..................................................................................................... 1
Things to Know Before You Download ............................................................. 1
Update Utilities ........................................................................................................ 2

Introduction
For information about any firmware release, see the release notes on the Emulex Web site. Release
notes include information such as new features, compatibility, known issues and resolved known issues.
This manual does not contain the procedures themselves. It serves as a guide to the publication that
contains the procedures you need.

Prerequisites
• Local boot disk.
• The intended Fibre Channel target should be big enough to hold all system files and the swap
slice of the current local boot disk.

Things to Know Before You Download
• Before you download the OneConnect or LightPulse files, create a directory for them.
• As a measure of protection, ensure that critical files on your local boot disk are backed up.
• Firmware may be bundled with boot code. Boot code allows you to designate a device that is
attached to the adapter as a boot drive. If you select a firmware image that includes boot code,
the update procedure will load both the new firmware and the boot code at the same time. After
updating, refer to the Emulex Boot Manual for procedures on enabling the boot code on your
adapter.
• Emulex firmware files support both OneConnect and LightPulse adapters.
• For OneConnect adapters:
• Firmware and boot code are provided in a single flash image called a .UFI file.
• The UFI file contains all of the files that support all OneConnect adapters. The latest
files for your adapter are installed automatically when you use an Emulex utility to
update the firmware.
• The UFI file contains both firmware and boot code.
• For LightPulse adapters:
• Firmware is provided in a .ZIP file as a .ALL file or a .AWC file. You must manually unzip
the .ALL or .AWC file from the .ZIP file before you can use an Emulex utility to install it.
• Firmware differs between adapter models. Make sure you download the appropriate
firmware for your adapter.
• The .ZIP file may or may not include a boot code (.PRG) file.

Table of Contents
Installation
Compatability
Prerequisites
Install HBA
Attach Media
Apply Power
View LEDs
Reference
Specifications
FCC and Regulatory Notices
Declaration of
Conformity
Laser Safety

Prerequisites
· The host computer must provide 3.3VDC bus power
The open 32-bit or 64-bit (64-bit recommended) PCI bus slot can be
either 3.3 VDC or 5.0 VDC signaling interface
·
· PCI bus clock rate of 66 MHz is preferred
Multimode fiber optic cable (50/125 m m or 62.5/125 m m) with LC
connectors, used with short-wave lasers

Install the Host Bus Adapter Board
Record IEEE and serial numbers.
Each host bus adapter port is shipped with a unique address identifier
called the IEEE address. Since this adapter has two ports, there are two
IEEE addresses. The IEEE address is used when configuring your
system. The serial number is used when communicating with Emulex.
All numbers are clearly marked on the board. We recommend that you
record these numbers before installing the adapter.
Turn off and unplug the computer.
Remove the computer case.
Remove the blank panel from an empty 32 or 64-bit PCI bus slot.
Compare the removed panel to the bracket on the host bus adapter.
Follow steps 5-8 to change the bracket if they are different sizes.

Note The host bus adapter comes with a standard PCI
bracket installed. The low profile mounting bracket is
shorter than the standard bracket; approximately
3.11 in. (7.9cm) compared to 4.75 in. (12.06 cm)
long.

Remove the mounting bracket screws from the top of the host bus
adapter.
Remove the bracket and store it for future use.
Align the new mounting bracket tabs with the holes in the HBA.
Replace the screws that attach the HBA to the bracket.
Insert the host bus adapter into the empty 32 or 64-bit PCI bus slot.
Press firmly until it is seated.
Secure the host bus adapter's mounting bracket to the case with the panel
screw or clip.
Replace the computer case and tighten case screws.
The host bus adapter is now installed in the PC and is ready for media
attachment.

Overview................................................................................................................ 1
Be Informed, Stay Informed, Stay Current 1
The Importance of Compatibility, Driver Updates and Firmware Updates 1
Driver Updates........................................................................................... 1
Firmware Updates...................................................................................... 2
Emulex Configuration Parameters 3
How Emulex Device Driver Configuration Parameters Work...................... 3
Emulex Applications 3
Troubleshooting...................................................................................................... 4
Observing the Problem 4
Isolating the Problem 4
SAN Components...................................................................................... 4
Server Components................................................................................... 5
Checklists 6
Connectivity Checklist................................................................................ 6
Installation Checklist.................................................................................. 7
Upgrade Checklist...................................................................................... 8
Configuration Checklist.............................................................................. 8
Tools to Collect Data 9
Driver Tools - Event Logging...................................................................... 9
The OneCommand Manager and HBAnyware Applications....................... 9
Other Ways to Collect Data...................................................................... 10
Common Problems 10
Hardware Issues...................................................................................... 10
Link Down................................................................................................ 10
Cannot See Devices or Drives................................................................. 11
Out-of-Date Driver Version....................................................................... 12
Out-of-Date Firmware Version.................................................................. 12
OneConnect and LightPulse LP21000 Adapters 13
OneConnect and LP21000 Checklist....................................................... 13
OneConnect and LP21000 Symptoms..................................................... 13
When to Contact Emulex...................................................................................... 14
Emulex Web Site and Emulex Support................................................................. 15
Emulex Support Page 15
Contact Emulex After Hours, Weekends or Holidays............................... 17
LED Reference Information.................................................................................. 18
Firmware Operation and Port Activity LEDs 18
Common LED States 18
Normal Link Up........................................................................................ 18
Link-Down or adapter waiting................................................................... 19
Heart-beat indication................................................................................ 19
OneConnect CNA LEDs........................................................................... 19
LP21000 LEDs......................................................................................... 19
LED Table................................................................................................ 21

Driver Updates
To update your driver, download the latest Emulex driver and utilities from the Emulex Web site. From
the main Emulex Web site, click Downloads, click your vendor and then click the link for your operating
system (OS).
Drivers for Windows
• The drivers for Windows include support for Windows Server 2008 R2, Windows Server 2008,
Windows Server 2003, Windows 2000 Server and Windows NT (No future versions of drivers for
Windows 2000 Server or Windows NT are planned.)
•The driver kit download includes the base driver and the OneCommand Manager application.
•If you are running Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 or Windows 2000 Server, the driver kit download includes AutoPilot Installer®, which enables you to quickly install or update drivers and utilities and configure adapters, drivers and utilities.

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SMI-S HBA Provider, compliant with the SMI-S 1.1.0 specification and certified against the SNIA-CTP v1.1.0.85 suite

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.1.6
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. HBAnyware WebLaunch Integration (Optional)
SECTION 7. Known Limitations
SECTION 8. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.5.1 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.1.0.85, and it is fully compliant with SMI-S v1.1.0.

SLP (Service Location Protocol) and OpenSSL are included with the Emulex
SMI-S HBA Provider kit on Windows and are installed by default if not
already present. See Section 2 for Linux specific details.

For security purposes, you might want to replace the sample certificates
(privkey.cert and elxhba.cert) with your own signed certificates.

NOTE: The included OpenSSL library was built to exclude support for the IDEA,
MDC2 and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
Members of the local group "Administrators" have full access to the CIM
server by default on Windows.

On Linux, the default user account is:
User Name: root
Password: pwd580

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 and Oracle Enterprise Linux 4 (x86)

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.1.6
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. HBAnyware WebLaunch Integration (Optional)
SECTION 7. Known Limitations
SECTION 8. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.5.1 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.1.0.85, and it is fully compliant with SMI-S v1.1.0.

SLP (Service Location Protocol) and OpenSSL are included with the Emulex
SMI-S HBA Provider kit on Windows and are installed by default if not
already present. See Section 2 for Linux specific details.

For security purposes, you might want to replace the sample certificates
(privkey.cert and elxhba.cert) with your own signed certificates.

NOTE: The included OpenSSL library was built to exclude support for the IDEA,
MDC2 and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
Members of the local group "Administrators" have full access to the CIM
server by default on Windows.

On Linux, the default user account is:
User Name: root
Password: pwd580

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 9 (ia64)

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.1.6
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. HBAnyware WebLaunch Integration (Optional)
SECTION 7. Known Limitations
SECTION 8. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.5.1 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.1.0.85, and it is fully compliant with SMI-S v1.1.0.

SLP (Service Location Protocol) and OpenSSL are included with the Emulex
SMI-S HBA Provider kit on Windows and are installed by default if not
already present. See Section 2 for Linux specific details.

For security purposes, you might want to replace the sample certificates
(privkey.cert and elxhba.cert) with your own signed certificates.

NOTE: The included OpenSSL library was built to exclude support for the IDEA,
MDC2 and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
Members of the local group "Administrators" have full access to the CIM
server by default on Windows.

On Linux, the default user account is:
User Name: root
Password: pwd580

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 9 (x86)

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.1.6
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. HBAnyware WebLaunch Integration (Optional)
SECTION 7. Known Limitations
SECTION 8. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.5.1 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.1.0.85, and it is fully compliant with SMI-S v1.1.0.

SLP (Service Location Protocol) and OpenSSL are included with the Emulex
SMI-S HBA Provider kit on Windows and are installed by default if not
already present. See Section 2 for Linux specific details.

For security purposes, you might want to replace the sample certificates
(privkey.cert and elxhba.cert) with your own signed certificates.

NOTE: The included OpenSSL library was built to exclude support for the IDEA,
MDC2 and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
Members of the local group "Administrators" have full access to the CIM
server by default on Windows.

On Linux, the default user account is:
User Name: root
Password: pwd580

Support Resources for PRIMEQUEST Servers
SLES9 SP3 (2.6.5-7.244)
SMI-S HBA Provider, compliant with the SMI-S 1.0.2 specification and certified against the SNIA-CTP v1.0.2.23 suite
Pre-packaged with OpenPegasus CIMOM v2.3.2, as a turnkey SMI-S agent for ease of installation and deployment

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.0.12
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. Known Limitations
SECTION 7. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.3.2 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.0.2.23, and it is fully compliant with SMI-S v1.0.2.

SLPD (Service Location Protocol) is included with the Emulex SMI-S HBA Provider
kit and run by default if the system does not have one. For security purposes,
you might want to replace the sample certificates (privkey.cert and elxhba.cert)
with your own signed certificates.

Please refer to "http://www.openssl.org/docs/HOWTO/" for more details on how
to create a certificate.

NOTE: The OpenSSL library was built to exclude support for the IDEA, MDC2
and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
By default, the following account is created only on Windows:
User Name: cimadmin
Password: pwd580

On Linux, the default user account is:
User Name: root
Password: pwd580

SUSE Linux Enterprise Server 9 Service Pack 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SMI-S HBA Provider, compliant with the SMI-S 1.0.2 specification and certified against the SNIA-CTP v1.0.2.23 suite
Pre-packaged with OpenPegasus CIMOM v2.3.2, as a turnkey SMI-S agent for ease of installation and deployment

RELEASE NOTES for Emulex SMI-S HBA Provider
Version 1.0.12
SECTION 1. Introduction
SECTION 2. System Prerequisites
SECTION 3. Supported and Tested Operating Systems
SECTION 4. Installation
SECTION 5. Directory Structure
SECTION 6. Known Limitations
SECTION 7. Frequently Asked Questions
SECTION 1. Introduction

The Emulex SMI HBA Provider is integrated/bundled with OpenPegasus Common
Information Model Object Manager (CIMOM) as a pre-packaged, ready to deploy
SMI-S agent. This package incorporates version 2.3.2 of the OpenPegasus
CIMOM ("http://www.openpegasus.org").

This release supports the FC HBA profile, Server profile and a partial
implementation of the Host Discovered Resources (HDR) profile. The Emulex
SMI-S HBA Provider is certified by SNIA Conformance Testing Program (CTP)
v1.0.2.23, and it is fully compliant with SMI-S v1.0.2.

SLPD (Service Location Protocol) is included with the Emulex SMI-S HBA Provider
kit and run by default if the system does not have one. For security purposes,
you might want to replace the sample certificates (privkey.cert and elxhba.cert)
with your own signed certificates.

Please refer to "http://www.openssl.org/docs/HOWTO/" for more details on how
to create a certificate.

NOTE: The OpenSSL library was built to exclude support for the IDEA, MDC2
and RC5 encryption algorithms.

License agreements for these Open Source components and the Emulex software
are found in the ancillary.txt file.

The Emulex SMI-S HBA Provider is registered under the namespace: root/emulex.
By default, the following account is created only on Windows:
User Name: cimadmin
Password: pwd580

On Linux, the default user account is:
User Name: root
Password: pwd580

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
Driver for Linux User Manual

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

SUSE Linux Enterprise Server 9 Service Pack 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Red Hat Enterprise Linux 5.0 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
HBAnyware Utility Version 4.0 Introduction.............................................................................................................. 1
Known Issues .................................................................................................... 1
Installing HBAnyware Components.......................................................................... 2
Installing the HBAnyware Utility......................................................................... 2
Installing the HBAnyware Utility with Web Launch............................................. 4
Installing the HBAnyware Utility Security Configurator ...................................... 5
Uninstalling the HBAnyware Security Configurator............................................ 6
Uninstalling HBAnyware Web Launch Only ....................................................... 7
Uninstalling the Utility Package ......................................................................... 7
Using the HBAnyware Components......................................................................... 8
Starting the HBAnyware Utility........................................................................... 8
Starting HBAnyware with Web Launch .............................................................. 8
Starting the HBAnyware Security Configurator .................................................. 8
Starting HBAnyware from the Command Line ................................................... 9
Examples of Modifications .................................................................... 9
The HBAnyware Utility Window Element Definitions ....................................... 10
The Menu Bar ........................................................................................... 11
The Toolbar ............................................................................................... 11
The Toolbar Buttons .................................................................................. 11
Sort Toolbar Buttons ........................................................................... 11
The Discovery-Tree................................................................................... 12
Discovery-Tree Icons .......................................................................... 12
Property Tabs............................................................................................ 13
Status Bar ................................................................................................. 13
Changing Management Mode ......................................................................... 13
Resetting HBAs ............................................................................................... 14
Discovering HBAs ........................................................................................... 14
Automatic Fibre Channel Discovery .......................................................... 14
Remote SAN Management Using TCP/IP Access Protocol....................... 15
Adding a Single Host .......................................................................... 15
Adding a Range of Hosts .................................................................... 16
Removing Hosts.................................................................................. 17
Configuring Discovery Settings ................................................................. 18
Sorting HBA Information.................................................................................. 19
Viewing Remote and Local HBAs.............................................................. 19
Viewing HBA Information................................................................................. 20
Viewing Discovery Information .................................................................. 20
Viewing Host Information .......................................................................... 21
The Host Information Tab.................................................................... 21
The Driver Parameters Tab................................................................. 22
Viewing General HBA Attributes ............................................................... 23
Viewing Detailed HBA Information ............................................................ 24
Viewing Fabric Information........................................................................ 26
Viewing Target Information........................................................................ 27
Viewing LUN Information........................................................................... 28
Masking and Unmasking LUNs (Windows, Solaris LPFC and
Solaris SFS)........................................................................................ 29
Viewing Port Statistics............................................................................... 31
Viewing Firmware Information ................................................................... 33
Viewing Target Mapping (Windows, Solaris LPFC and Solaris SFS)......... 34
Viewing Target Mapping (Linux) ................................................................ 35

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

Introduction.............................................................................................................. 1
Installing lputil .......................................................................................................... 1
Starting lputil............................................................................................................ 2
Discovering HBAs.................................................................................................... 4
Viewing HBA Information......................................................................................... 4
Resetting an HBA .................................................................................................... 5
Updating an HBA’s Firmware or Boot Code ............................................................. 5
Enabling or Disabling Boot Code ............................................................................. 6
Downloading PCI Configuration............................................................................... 7
Setting Up Persistent Binding (Solaris Only)............................................................ 7
Using the Command Line Interface ......................................................................... 9
Examples of lputil Commands................................................................... 11

Introduction
The LightPulse® diagnostic utility (lputil) for Linux and Solaris is a console application that enables you
to manage local Emulex® host bus adapters (HBAs).
Use lputil to do any of the following:
• Discover HBAs
• View HBA information
• Reset HBAs
• Update firmware or boot code on the local HBA
• Enable or disable the boot code on the HBA
• Download PCI Configuration
• Set Up Persistent Binding (Solaris only)
• Use the Command Line Interface (CLI)
Prerequisites
Before using lputil, ensure the following prerequisites are met:
• The Emulex driver is installed.
• The lputil utility is installed.
• If you are updating firmware, the firmware file is downloaded to a local drive. Firmware versions
differ between HBA versions. Make sure you have downloaded the appropriate firmware for your
HBA.
• I/O activity on the bus is quieted.
• Any software that relies on the HBA to be available is stopped or paused.
Installing lputil
To install lputil:
1. Download the lputil.tar file from the Emulex Web site to a directory on a local drive on the server.
2. Untar the contents of the lputil.tar file.
3. Run the lputil installation script.

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Red Hat Enterprise Linux 5.0 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
Driver for Linux User Manual

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

SUSE Linux Enterprise Server 9 Service Pack 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Red Hat Enterprise Linux 4 Update 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Oracle Enterprise Linux 4 Update 4 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)Asianux 2.0 SP2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)
Driver for Linux User Manual

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
HBAnyware Utility User Manual

Introduction.............................................................................................................. 1
Known Issues .................................................................................................... 1
Installing HBAnyware Components.......................................................................... 2
Installing the HBAnyware Utility......................................................................... 2
Installing the HBAnyware Utility with Web Launch............................................. 4
Installing the HBAnyware Utility Security Configurator ...................................... 5
Uninstalling the HBAnyware Security Configurator............................................ 6
Uninstalling HBAnyware Web Launch Only ....................................................... 7
Uninstalling the Utility Package ......................................................................... 7
Using the HBAnyware Components......................................................................... 8
Starting the HBAnyware Utility........................................................................... 8
Starting HBAnyware with Web Launch .............................................................. 8
Starting the HBAnyware Security Configurator .................................................. 8
Starting HBAnyware from the Command Line ................................................... 9
Examples of Modifications .................................................................... 9
The HBAnyware Utility Window Element Definitions ....................................... 10
The Menu Bar ........................................................................................... 11
The Toolbar ............................................................................................... 11
The Toolbar Buttons .................................................................................. 11
Sort Toolbar Buttons ........................................................................... 11
The Discovery-Tree................................................................................... 12
Discovery-Tree Icons .......................................................................... 12
Property Tabs............................................................................................ 13
Status Bar ................................................................................................. 13
Changing Management Mode ......................................................................... 13
Resetting HBAs ............................................................................................... 14
Discovering HBAs ........................................................................................... 14
Automatic Fibre Channel Discovery .......................................................... 14
Remote SAN Management Using TCP/IP Access Protocol....................... 15
Adding a Single Host .......................................................................... 15
Adding a Range of Hosts .................................................................... 16
Removing Hosts.................................................................................. 17
Configuring Discovery Settings ................................................................. 18
Sorting HBA Information.................................................................................. 19
Viewing Remote and Local HBAs.............................................................. 19
Viewing HBA Information................................................................................. 20
Viewing Discovery Information .................................................................. 20
Viewing Host Information .......................................................................... 21
The Host Information Tab.................................................................... 21
The Driver Parameters Tab................................................................. 22
Viewing General HBA Attributes ............................................................... 23
Viewing Detailed HBA Information ............................................................ 24
Viewing Fabric Information........................................................................ 26
Viewing Target Information........................................................................ 27
Viewing LUN Information........................................................................... 28
Masking and Unmasking LUNs (Windows, Solaris LPFC and
Solaris SFS)........................................................................................ 29
Viewing Port Statistics............................................................................... 31
Viewing Firmware Information ................................................................... 33
Viewing Target Mapping (Windows, Solaris LPFC and Solaris SFS)......... 34
Viewing Target Mapping (Linux) ................................................................ 35

SUSE Linux Enterprise Server 9 Service Pack 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Red Hat Enterprise Linux 4 Update 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Oracle Enterprise Linux 4 Update 4 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)Asianux 2.0 SP2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)
HBAnyware Utility User Manual

Introduction.............................................................................................................. 1
Known Issues .................................................................................................... 1
Installing HBAnyware Components.......................................................................... 2
Installing the HBAnyware Utility......................................................................... 2
Installing the HBAnyware Utility with Web Launch............................................. 4
Installing the HBAnyware Utility Security Configurator ...................................... 5
Uninstalling the HBAnyware Security Configurator............................................ 6
Uninstalling HBAnyware Web Launch Only ....................................................... 7
Uninstalling the Utility Package ......................................................................... 7
Using the HBAnyware Components......................................................................... 8
Starting the HBAnyware Utility........................................................................... 8
Starting HBAnyware with Web Launch .............................................................. 8
Starting the HBAnyware Security Configurator .................................................. 8
Starting HBAnyware from the Command Line ................................................... 9
Examples of Modifications .................................................................... 9
The HBAnyware Utility Window Element Definitions ....................................... 10
The Menu Bar ........................................................................................... 11
The Toolbar ............................................................................................... 11
The Toolbar Buttons .................................................................................. 11
Sort Toolbar Buttons ........................................................................... 11
The Discovery-Tree................................................................................... 12
Discovery-Tree Icons .......................................................................... 12
Property Tabs............................................................................................ 13
Status Bar ................................................................................................. 13
Changing Management Mode ......................................................................... 13
Resetting HBAs ............................................................................................... 14
Discovering HBAs ........................................................................................... 14
Automatic Fibre Channel Discovery .......................................................... 14
Remote SAN Management Using TCP/IP Access Protocol....................... 15
Adding a Single Host .......................................................................... 15
Adding a Range of Hosts .................................................................... 16
Removing Hosts.................................................................................. 17
Configuring Discovery Settings ................................................................. 18
Sorting HBA Information.................................................................................. 19
Viewing Remote and Local HBAs.............................................................. 19
Viewing HBA Information................................................................................. 20
Viewing Discovery Information .................................................................. 20
Viewing Host Information .......................................................................... 21
The Host Information Tab.................................................................... 21
The Driver Parameters Tab................................................................. 22
Viewing General HBA Attributes ............................................................... 23
Viewing Detailed HBA Information ............................................................ 24
Viewing Fabric Information........................................................................ 26
Viewing Target Information........................................................................ 27
Viewing LUN Information........................................................................... 28
Masking and Unmasking LUNs (Windows, Solaris LPFC and
Solaris SFS)........................................................................................ 29
Viewing Port Statistics............................................................................... 31
Viewing Firmware Information ................................................................... 33
Viewing Target Mapping (Windows, Solaris LPFC and Solaris SFS)......... 34
Viewing Target Mapping (Linux) ................................................................ 35

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

Introduction.............................................................................................................. 1
Known Issues .................................................................................................... 1
Installing HBAnyware Components.......................................................................... 2
Installing the HBAnyware Utility......................................................................... 2
Installing the HBAnyware Utility with Web Launch............................................. 4
Installing the HBAnyware Utility Security Configurator ...................................... 5
Uninstalling the HBAnyware Security Configurator............................................ 6
Uninstalling HBAnyware Web Launch Only ....................................................... 7
Uninstalling the Utility Package ......................................................................... 7
Using the HBAnyware Components......................................................................... 8
Starting the HBAnyware Utility........................................................................... 8
Starting HBAnyware with Web Launch .............................................................. 8
Starting the HBAnyware Security Configurator .................................................. 8
Starting HBAnyware from the Command Line ................................................... 9
Examples of Modifications .................................................................... 9
The HBAnyware Utility Window Element Definitions ....................................... 10
The Menu Bar ........................................................................................... 11
The Toolbar ............................................................................................... 11
The Toolbar Buttons .................................................................................. 11
Sort Toolbar Buttons ........................................................................... 11
The Discovery-Tree................................................................................... 12
Discovery-Tree Icons .......................................................................... 12
Property Tabs............................................................................................ 13
Status Bar ................................................................................................. 13
Changing Management Mode ......................................................................... 13
Resetting HBAs ............................................................................................... 14
Discovering HBAs ........................................................................................... 14
Automatic Fibre Channel Discovery .......................................................... 14
Remote SAN Management Using TCP/IP Access Protocol....................... 15
Adding a Single Host .......................................................................... 15
Adding a Range of Hosts .................................................................... 16
Removing Hosts.................................................................................. 17
Configuring Discovery Settings ................................................................. 18
Sorting HBA Information.................................................................................. 19
Viewing Remote and Local HBAs.............................................................. 19
Viewing HBA Information................................................................................. 20
Viewing Discovery Information .................................................................. 20
Viewing Host Information .......................................................................... 21
The Host Information Tab.................................................................... 21
The Driver Parameters Tab................................................................. 22
Viewing General HBA Attributes ............................................................... 23
Viewing Detailed HBA Information ............................................................ 24
Viewing Fabric Information........................................................................ 26
Viewing Target Information........................................................................ 27
Viewing LUN Information........................................................................... 28
Masking and Unmasking LUNs (Windows, Solaris LPFC and
Solaris SFS)........................................................................................ 29
Viewing Port Statistics............................................................................... 31
Viewing Firmware Information ................................................................... 33
Viewing Target Mapping (Windows, Solaris LPFC and Solaris SFS)......... 34
Viewing Target Mapping (Linux) ................................................................ 35

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
Base driver and install script (273 KB gz file)

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
2. Description of Install Procedure
3. Known Issues
3.1 PCI Hot Plug Support for applications
3.1.1 Observed problem
3.1.2 Workaround
3.2 Deletion of Vports/PCI Hot Unplug
3.2.1 Observed Problem
3.2.2 Background
3.3 lspci utility displays "Unknown Device" for LPe12000 HBAs
3.3.1 Observed Problem
3.3.2 Background
3.4 Speed of LPe12000 HBA (8Gb) is incorrectly displayed by HBAnyware
3.4.1 Observed Problem
3.4.2 Background
3.5 Port disabled on system boot or HBA reset with authentication enabled
3.5.1 Observed Problem
3.5.2 Workaround
3.6 LILO Boot Loader is not supported - i386 and x86_64 architectures
3.6.1 Observed Problem
3.6.2 Background
3.7 Order of lpfc module in initrd module list
3.7.1 Observed Problem
3.7.2 Workaround
3.8 Devloss timeout after swapping ports
3.8.1 Observed Problem
3.8.2 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 5
SuSE Linux Enterprise Server 10 (SP1 or higher)

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the -devel package
which matches the kernel package with the same version as the
currently running kernel must be installed for the LPFC driver
build to succeed. For example, a system with the 2.6.18-7 kernel
would need the kernel-devel-2.6.18-7 package.

1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the LPFC driver build to succeed. For example, a
system with the 2.6.16.46-0.7-bigsmp kernel would need the
kernel-source-2.6.16.46-0.7 package.

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Base driver and install script

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
2. Description of Install Procedure
3. Known Issues
3.1 PCI Hot Plug Support for applications
3.1.1 Observed problem
3.1.2 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 5

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the -devel package
which matches the kernel package with the same version as the
currently running kernel must be installed for the LPFC driver
build to succeed. For example, a system with the 2.6.18-7 kernel
would need the kernel-devel-2.6.18-7 package.
2. Description of Install Procedure

The lpfc-install script installs the LPFC driver RPM. This RPM
installs the driver sources to the /usr/src/lpfc directory, builds
the driver for the currently running kernel, and then installs the
driver to the proper directory for the currently running kernel.

Once the RPM is installed, the lpfc-install script creates a new
ramdisk for the currently running kernel so that the 'lpfc' driver
is loaded when the kernel is initialized during system startup.
3. Known Issues

3.1 PCI Hot Plug Support for applications

3.1.1 Observed problem

PCI Hot Plug has been found to cause applications (HBAnyware utilities or
third party applications) that use the Emulex libraries (i.e. HBAAPI), to
misbehave or malfunction.

3.1.2 Workaround

A user should stop all applications that are accessing LPFC's HBAAPI
interface (HBAnyware utilities or third party applications) before
performing PCI Hot Plug of an LPFC HBA.

Use the following command to stop the HBAnyware application:
#/usr/sbin/hbanyware/stop_hbanyware

After performing PCI Hot Plug of the HBA you can restart the applications.

SUSE Linux Enterprise Server 9 Service Pack 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Base driver, application helper module and install script

1. System Requirements
2. Description of Changes
3. Release Notes
3.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
3.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
3.3 Kernel Upgrade
3.4 Changing Target Timeout
3.4.1 Background
3.4.2 Observed Problem
3.4.3 Workaround
3.5 Machine Check Exception
3.5.1 Observed problem
3.5.2 Workaround
----------------------------------------------------------------------

1. System Requirements

The following distributions of Linux are supported by the Emulex
drivers:

Red Hat Enterprise Linux 4
SuSE Linux Enterprise Server 9

2. Description of Install Procedure

The lpfc-install script installs both the LPFC driver and the LPFC
DFC driver RPMs. These RPMs install their driver sources to the
/usr/src/lpfc directory, build their drivers for the currently
running kernel, and then install the drivers to the proper
directory for the currently running kernel.

Once the RPMs are installed, the lpfc-install script creates a new
ramdisk for the currently running kernel so that the 'lpfc' driver
is loaded when the kernel is initialized during system startup.
The 'elxlpfc' init script is also installed and configured to start
and stop the 'lpfcdfc' driver during system startup and shutdown.

3. Release Notes

3.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the kernel development
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.9-5.EL kernel would need the
kernel-devel-2.6.9-5.EL package, and a system with the
2.6.9-5.ELsmp kernel would need the kernel-smp-devel-2.6.9-5.EL
package.

3.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.5-7.139-bigsmp kernel would need the
kernel-source-2.6.5-7.139 package.

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Base driver and install script

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
2. Description of Install Procedure
3. Informational
3.1 Packaging Change Involving The Application Helper Module
3.1.1 Background
3.1.2 Observed Behavior
4. Known Issues
4.1 Uninstalling the Driver Kit on Boot-from-SAN Configurations
4.1.1 Observed problem
4.1.2 Resolution
4.2 Machine Check Exception
4.2.1 Observed problem
4.2.2 Workaround
4.3 Loading order of LPFC driver in initial ramdisk
4.3.1 Background
4.3.2 Observed Problem
4.3.3 Workaround
4.4 System panic while unloading the lpfc module
4.4.1 Background
4.4.2 Observed Problem
4.4.3 Resolution
4.5 PCI Hot Plug Support for applications
4.5.1 Observed problem
4.5.2 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 4 (Update 3 or higher)
SuSE Linux Enterprise Server 9 (SP2 or higher)

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the kernel development
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.9-22.EL kernel would need the
kernel-devel-2.6.9-22.EL package, and a system with the
2.6.9-22.ELsmp kernel would need the kernel-smp-devel-2.6.9-22.EL
package.

1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.5-7.139-bigsmp kernel would need the
kernel-source-2.6.5-7.139 package.

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Base driver and install script

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
2. Description of Install Procedure
3. Informational
3.1 Packaging Change Involving The Application Helper Module
3.1.1 Background
3.1.2 Observed Behavior
4. Known Issues
4.1 Uninstalling the Driver Kit on Boot-from-SAN Configurations
4.1.1 Observed problem
4.1.2 Resolution
4.2 Machine Check Exception
4.2.1 Observed problem
4.2.2 Workaround
4.3 Loading order of LPFC driver in initial ramdisk
4.3.1 Background
4.3.2 Observed Problem
4.3.3 Workaround
4.4 System panic while unloading the lpfc module
4.4.1 Background
4.4.2 Observed Problem
4.4.3 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 4 (Update 3 or higher)
SuSE Linux Enterprise Server 9 (SP2 or higher)

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the kernel development
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.9-22.EL kernel would need the
kernel-devel-2.6.9-22.EL package, and a system with the
2.6.9-22.ELsmp kernel would need the kernel-smp-devel-2.6.9-22.EL
package.

1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.5-7.139-bigsmp kernel would need the
kernel-source-2.6.5-7.139 package.

SUSE Linux Enterprise Server 9 Service Pack 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Use this file only with the RHEL 4 Update 2 or SLES9 SP3 distributions, which contain the 8.0.16.17 driver -- do not use with the driver kit above

1. System Requirements
2. Description of Changes
3. Release Notes
3.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
3.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC Application Helper Module:

Red Hat Enterprise Linux 4 Update 1
SuSE Linux Enterprise Server 9 SP2

2. Description of Changes

The ioctl-install script installs the LPFC Application Helper
Module RPM. This RPM installs the module sources to the
/usr/src/lpfcdfc directory, builds the module for the currently
running kernel, and then installs the module to the proper
directory for the currently running kernel.

Once the RPM is installed, the 'elxlpfc' init script is installed
and configured to start and stop the 'lpfcdfc' driver during system
startup and shutdown.

3. Release Notes

3.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the kernel development
package with the same version as the currently running kernel must
be installed for the Application Helper Module build to succeed.
For example, a system with the 2.6.9-6.37.EL kernel would need the
kernel-devel-2.6.9-6.37.EL package, and a system with the
2.6.9-6.37.ELsmp kernel would need the
kernel-smp-devel-2.6.9-6.37.EL package.

3.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the Application Helper Module build to succeed.
For example, a system with the 2.6.5-7.166-bigsmp kernel would need
the kernel-source-2.6.5-7.166 package.

SUSE Linux Enterprise Server 9 Service Pack 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
HBAnyware utility 2.1a25, lputil 2.0a9 (169 MB tar file)

HBAnyware 2.1a25 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 2.1a25
SSC version 2.1a25
DFC Library version 80.161-5
Lputil version 2.0a9
HBAAPI version 2.1.a

Dependencies:

lpfc driver version 8.0.16.17 or later
HBAnyware is dependant on lpfc being installed, so install lpfc first if it is not already installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.

Installing HBAnyware

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. su to root
5. Run the install script: ./install
Uninstalling HBAnyware

1. Complete steps 1 through 4 from "Installing HBAnyware" above.
2. Run the uninstall script: ./uninstall
Running the HBAnyware GUI

1. su to root
2. Run the script /usr/sbin/hbanyware/hbanyware
ppc64/sles8 NOTE:
If you want to use the 64bit HBAAPI libraries you must replace the following line in /etc/hba.conf:
com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so
with this line
com.emulex.emulexapilibrary /usr/lib64/libemulexhbaapi.so

ppc64/(non-sles8) and amd64 NOTE:
If you want to use the 64bit HBAAPI libraries you must add the following line in /etc/hba.conf:
com.emulex.emulexapilibrary /usr/lib64/libemulexhbaapi.so

HBAnyware Help:
To view the HBAnyware help pages or to access the Emulex Technical support pages you must have one of the
following web browsers installed:
mozilla, konqueror
Helpful scripts

/usr/sbin/hbanyware/stop_hbanyware - This script will stop all HBAnyware daemons and GUIs.
Run this if you need to unload the driver.

/usr/sbin/hbanyware/start_rmserver - This script will re-start the rmserver daemon.
Run this if you manually load the lpfc driver.

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
HBAnyware utility 3.2a16, lputil 2.0a14

HBAnyware 3.2a16 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 3.2a16
SSC version 3.2a16
DFC Library version 2.15.1007-1-1
Lputil version 2.0a14
HBAAPI version 2.1.e

Dependencies:

lpfc driver version 8.1.10.12 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install
8. When prompted, answer the following question:

Select desired mode of operation for HBAnyware

1 Local Mode : HBA's on this Platform can be managed by HBAnyware
clients on this platform only.
2 Managed Mode : HBA's on this Platform can be managed by local or
remote HBAnyware clients
3 Remote Mode : Same as '2' plus HBAnyware clients on this Platform
can manage local and remote clients.

Enter the number '1' or '2' or '3'
9. When prompted, answer the following question:

Do you want to allow user to make subsequent management mode changes
using 'set_operating_mode' script
Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware
to start GUI or type /usr/sbin/hbanyware/hbacmd list
to run script utility

Red Hat Enterprise Linux 5.0 and later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
HBAnyware utility 3.4a14 (198 MB tar file)

HBAnyware 3.4a14 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 3.4a14
SSC version 3.4a14
DFC Library version 3.0.13-1
Lputil version
HBAAPI version 2.1.g

Dependencies:

lpfc driver version 8.2.0.22 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install
8. When prompted, answer the following question:

Select desired mode of operation for HBAnyware

1 Local Mode : HBA's on this Platform can be managed by HBAnyware
clients on this platform only.
2 Managed Mode : HBA's on this Platform can be managed by local or
remote HBAnyware clients
3 Remote Mode : Same as '2' plus HBAnyware clients on this Platform
can manage local and remote clients.

Enter the number '1' or '2' or '3'
9. When prompted, answer the following question:

Do you want to allow user to make subsequent management mode changes
using 'set_operating_mode' script
Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware
to start GUI or type /usr/sbin/hbanyware/hbacmd list
to run script utility

Red Hat Enterprise Linux 5.0 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
HBAnyware utility 4.0a31 (179 MB tar file)

HBAnyware 4.0a31 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 4.0a31
SSC version 4.0a31
DFC Library version 3.0.25-1-1
HBAAPI version 2.1.g
Multipulse version 3.0.30-1
FCAUTHD version 1.17-1-1
Dependencies:

lpfc driver version 8.2.0.29 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install
8. When prompted, answer the following question:

Select desired mode of operation for HBAnyware

1 Local Mode : HBA's on this Platform can be managed by HBAnyware
clients on this platform only.
2 Managed Mode : HBA's on this Platform can be managed by local or
remote HBAnyware clients
3 Remote Mode : Same as '2' plus HBAnyware clients on this Platform
can manage local and remote clients.

Enter the number '1' or '2' or '3'
9. When prompted, answer the following question:

Do you want to allow user to make subsequent management mode changes
using 'set_operating_mode' script
Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware
to start GUI or type /usr/sbin/hbanyware/hbacmd list
to run script utility

SUSE Linux Enterprise Server 9 Service Pack 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Red Hat Enterprise Linux 4 Update 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Oracle Enterprise Linux 4 Update 4 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)Asianux 2.0 SP2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)
HBAnyware utility 3.4a14, Application helper module 2.0.30

HBAnyware 3.4a14 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 3.4a14
SSC version 3.4a14
DFC Library version 80.164-8
Lputil version
HBAAPI version 2.1.g

Dependencies:

lpfc driver version 8.0.16.40 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install
8. When prompted, answer the following question:

Select desired mode of operation for HBAnyware

1 Local Mode : HBA's on this Platform can be managed by HBAnyware
clients on this platform only.
2 Managed Mode : HBA's on this Platform can be managed by local or
remote HBAnyware clients
3 Remote Mode : Same as '2' plus HBAnyware clients on this Platform
can manage local and remote clients.

Enter the number '1' or '2' or '3'
9. When prompted, answer the following question:

Do you want to allow user to make subsequent management mode changes
using 'set_operating_mode' script
Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware
to start GUI or type /usr/sbin/hbanyware/hbacmd list
to run script utility

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
HBAnyware utility 3.0a14, lputil 2.0a13, Application helper module 2.0.15 (187 MB tar file)

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

HBAnyware 3.2a7 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 3.2a7
SSC version 3.2a7
DFC Library version 80.163-11
Lputil version 2.0a14
HBAAPI version 2.1.d
DFC helper module

Dependencies:

lpfc driver version 8.0.16.32 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.

HBAnyware requires the kernel development environment as described here:

This kit installs the Emulex Application Helper Module for the
currently running kernel. Since this installation procedure builds
the module for the currently running kernel, the kernel development
environment must be installed. For systems running Red Hat Enterprise
Linux (RHEL) 4, the appropriate kernel-devel package is required; for
example, a system with the 2.6.9-22.EL kernel would need the
kernel-devel-2.6.9-22.EL package, and a system with the 2.6.9-22.ELsmp
kernel would need the kernel-smp-devel-2.6.9-22.EL package. For
systems running SuSE Linux Enterprise Server (SLES) 9, the appropriate
kernel-source package is required; for example, a system with the
2.6.5-7.139-bigsmp kernel would need the kernel-source-2.6.5-7.139
package.
A log of each installation and uninstallation is recorded in the
following file:

/usr/src/lpfcdfc/utils-install.log
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install

SUSE Linux Enterprise Server 9 Service Pack 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Red Hat Enterprise Linux 4 Update 2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)
Oracle Enterprise Linux 4 Update 4 or later (x86 and x64 architectures)
Asianux 2.0 SP2 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures)

HBAnyware 3.3a20 Linux Installation Instructions

This installation kit contains the following components:

HBAnyware version 3.3a20
SSC version 3.3a20
DFC Library version 80.164-2
Lputil version 2.0a14
HBAAPI version 2.1.d_1

Dependencies:

lpfc driver version 8.0.16.34 or later

HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.
Installing HBAnyware:

1. Copy the applications kit tar file to a directory on the install machine
2. cd to the directory which you copied the tar file
3. Untar the file: tar -xvf tarfilename
4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
5. su to root
6. If earlier HBAnyware version currently installed, type : ./uninstall
7. Run the install script: ./install
8. When prompted, answer the following question:

Select desired mode of operation for HBAnyware

1 Local Mode : HBA's on this Platform can be managed by HBAnyware
clients on this platform only.
2 Managed Mode : HBA's on this Platform can be managed by local or
remote HBAnyware clients
3 Remote Mode : Same as '2' plus HBAnyware clients on this Platform
can manage local and remote clients.

Enter the number '1' or '2' or '3'
9. When prompted, answer the following question:

Do you want to allow user to make subsequent management mode changes
using 'set_operating_mode' script
Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware
to start GUI or type /usr/sbin/hbanyware/hbacmd list
to run script utility

Red Hat Enterprise Linux 5.0 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) SUSE Linux Enterprise Server 10 SP1 or later (x86 and x64, Intel Itanium2 and PowerPC 64-bit architectures) Oracle Enterprise Linux 5 or later (x86 and x64 architectures)
Base driver and install script (288 KB gz file)

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
2. Description of Install Procedure
3. Known Issues
3.1 PCI Hot Plug Support for applications
3.1.1 Observed problem
3.1.2 Workaround
3.2 Deletion of Vports/PCI Hot Unplug
3.2.1 Observed Problem
3.2.2 Background
3.3 lspci utility displays "Unknown Device" for LPe12000 HBAs
3.3.1 Observed Problem
3.3.2 Background
3.4 Speed of LPe12000 HBA (8Gb) is incorrectly displayed by HBAnyware
3.4.1 Observed Problem
3.4.2 Background
3.5 Port disabled on system boot or HBA reset with authentication enabled
3.5.1 Observed Problem
3.5.2 Workaround
3.6 LILO Boot Loader is not supported - i386 and x86_64 architectures
3.6.1 Observed Problem
3.6.2 Background
3.7 Order of lpfc module in initrd module list
3.7.1 Observed Problem
3.7.2 Workaround
3.8 Devloss timeout after swapping ports
3.8.1 Observed Problem
3.8.2 Workaround
3.9 Suspend to disk and Resume support
3.9.1 Observed Problem
3.9.2 Background
3.10 Deleting vports while devices are in use
3.10.1 Observed Problem
3.10.2 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 5
SuSE Linux Enterprise Server 10 (SP1 or higher)

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the -devel package
which matches the kernel package with the same version as the
currently running kernel must be installed for the LPFC driver
build to succeed. For example, a system with the 2.6.18-7 kernel
would need the kernel-devel-2.6.18-7 package.

SUSE Linux Enterprise Server 9 Service Pack 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Red Hat Enterprise Linux 4 Update 2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures) Oracle Enterprise Linux 4 Update 4 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)Asianux 2.0 SP2 or later (Intel x86, Intel Itanium2, Intel EM64T, AMD64, and PowerPC 64-bit architectures)
Base driver and install script

1. System Requirements
1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement
1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement
2. Description of Install Procedure
3. Informational
3.1 Packaging Change Involving The Application Helper Module
3.1.1 Background
3.1.2 Observed Behavior
4. Known Issues
4.1 Uninstalling the Driver Kit on Boot-from-SAN Configurations
4.1.1 Observed problem
4.1.2 Resolution
4.2 Machine Check Exception
4.2.1 Observed problem
4.2.2 Workaround
4.3 Loading order of LPFC driver in initial ramdisk
4.3.1 Background
4.3.2 Observed Problem
4.3.3 Workaround
4.4 System panic while unloading the lpfc module
4.4.1 Background
4.4.2 Observed Problem
4.4.3 Resolution
4.5 PCI Hot Plug Support for applications
4.5.1 Observed problem
4.5.2 Workaround
4.6 Storage Array discovery issues in direct-attach configurations
4.6.1 Observed problem
4.6.2 Workaround

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

1. System Requirements

The following distributions of Linux are supported by the Emulex
LPFC driver:

Red Hat Enterprise Linux 4 (Update 3 or higher)
SuSE Linux Enterprise Server 9 (SP2 or higher)

1.1 Red Hat Enterprise Linux 'kernel-devel' Package Requirement

For Red Hat Enterprise Linux installations, the kernel development
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.9-22.EL kernel would need the
kernel-devel-2.6.9-22.EL package, and a system with the
2.6.9-22.ELsmp kernel would need the kernel-smp-devel-2.6.9-22.EL
package.

1.2 SuSE Linux Enterprise Server 'kernel-source' Package Requirement

For SuSE Linux Enterprise Server installations, the kernel-source
package with the same version as the currently running kernel must
be installed for the LPFC 8.0 driver build to succeed. For
example, a system with the 2.6.5-7.139-bigsmp kernel would need the
kernel-source-2.6.5-7.139 package.

Emulex LightPulse PCI Fibre Channel Adapter
for Novell Netware 5.1, 6.0, and 6.5

Emulex Corporation

Release 2.20e September 30, 2005
This Readme file contains the description of the 2.20e version
of the LPFC.HAM driver for the Emulex LightPulse adapter family
and Novell NetWare 5.1, 6.0 and 6.5. It provides support for
switched Fabric operation and multi-initiator environments and
for up to 16 adapter channels using single or dual channel HBAs.

The Emulex LPFC.HAM driver has been tested in the following
environments:

1. OS Versions:
- Netware 6.5 with Support Pack 3 (NW65SP3)
- NetWare 6.0 with Support Pack 5 (NW6SP5 )
- NetWare 5.1 with Support Pack 7 (NW51SP7)
- untested with Netware 5.0 with Support Pack 6a (SP6a).
Netware 5.0 is supported by Novell, however no future work is planned for this version.
- NetWare 4.2 is not supported at this time; use Emulex driver version 1.23c to support NetWare 4.2.
2. Arbitrated Loop Environment
3. Switched Fabric Environment
4. Emulex Fibre Channel adapters
- LP11000 series adapters (minimum firmware revision 1.91a1)
- LP1150 series adapters (minimum firmware revision 1.91a1)
- LPe11000 series adapters (minimum firmware revision 1.91a1)
- LPe1150 series adapters (minimum firmware revision 1.91a1)
- LP10000 series adapters (minimum firmware revision 1.91a1)
- LP1050 series adapters (minimum firmware revision 1.91a1)
- LP101 series adapters (minimum firmware revision 1.82a0)
- LP9802DC, LP9802 and LP982 (minimum firmware version 1.91a1)
- LP9402DC, LP9002L, LP9002DC, LP9000 or LP952L (recommended firmware version 3.92a2)
- LP8000, LP8000DC and LP850
-- If your HBA has a Dragonfly chip version 2.00 or greater
use firmware version 3.92a2.
-- If your HBA has a Dragonfly chip below version 2.00,
use firmware version 3.30a7.
- LP7000E (minimum firmware version 3.21a0)
5. Suitable target hardware; lpfc.ham complies with SAN protocols
for switched fabrics and arbitrated loops.

This release includes the following files:

1. LPFC.HAM - Emulex Fibre Channel adapter HAM driver
2. lpfc.ddi - driver description file
3. readme.txt - readme file (this file)
INSTALLATION INSTRUCTIONS ON AN EXISTING NETWARE SERVER:

1. The server must support PCI 2.2 standard slots or PCI-X 1.1
standard slots.

2. At the server console load the install program. On
Netware 6.5 enter

LOAD HDETECT

On Netware 6.0, 5.1, or 5.0, enter

LOAD NWCONFIG

3. Select "Driver Options".

4. Select "Configure disk and storage device drivers".

5. Select "Select an additional driver".

6. Press to install a driver not on the list.
(If there is a previously installed version of the driver,
this will update and replace it).

Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Installation, Configuration and Troubleshooting (2,727 KB)

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Installation, Configuration and Troubleshooting

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25

Solaris 10 Updates and the lpfc
Driver
The behavior of the Solaris operating system changes beginning with Solaris 10 Update 1 (also referred
to as Solaris 10 1/06 release). Starting with this version, a bare-metal installation of the operating system
automatically discovers all SFS-recognized HBAs (Sun-branded, Emulex, or EMC-branded) and binds
them to the “emlxs” SFS driver. A subsequent installation of lpfc will not discover and bind these HBAs;
you must use the emlxdrv utility to unbind the HBAs from the SFS driver as described in this document.

Note: You do not need to follow the procedure described in this document in the following
circumstances:
• If the server contains any Sun-branded HBAs, which are recognized
and supported only by the emlxs driver and not by the lpfc driver; you
must use the emlxs driver on all HBAs.
• If you installed an earlier version of Solaris and bound the HBAs to the
lpfc driver; updating to Solaris 10 Update 1 (or later) by applying
patches will not unbind the HBAs from the lpfc driver.

Prerequisites:
• SPARC platform
• Solaris 10 Update 1 or later installed on a local drive
• Sun released patch 120222-06 or later installed
• Emulex® FCA utility version 1.00m (which includes emlxdrv 1.00j for SPARC) or later installed
(see the Emulex FCA Utilities Reference Manual for installation instructions)
• Emulex lpfc driver not yet installed
To unbind the HBAs from the SFS driver, do the following:
1. Start the emlxdrv utility as described in the Emulex FCA Utilities Reference Manual.
2. Type the following command at the emlxdrv prompt:
clear_all
This unbinds from emlxs all HBAs that are recognized by both emlxs and lpfc drivers.
3. Exit the emlxdrv utility by typing the following:
q
Install the lpfc driver as instructed in the documentation that accompanies the driver.

Solaris 10 Updates and the lpfc
Driver
The behavior of the Solaris operating system changes beginning with Solaris 10 Update 1 (also referred
to as Solaris 10 1/06 release). Starting with this version, a bare-metal installation of the operating system
automatically discovers all SFS-recognized HBAs (Sun-branded, Emulex, or EMC-branded) and binds
them to the “emlxs” SFS driver. A subsequent installation of lpfc will not discover and bind these HBAs;
you must use the emlxdrv utility to unbind the HBAs from the SFS driver as described in this document.

Note: You do not need to follow the procedure described in this document in the following
circumstances:
• If the server contains any Sun-branded HBAs, which are recognized
and supported only by the emlxs driver and not by the lpfc driver; you
must use the emlxs driver on all HBAs.
• If you installed an earlier version of Solaris and bound the HBAs to the
lpfc driver; updating to Solaris 10 Update 1 (or later) by applying
patches will not unbind the HBAs from the lpfc driver.

Prerequisites:
• SPARC platform
• Solaris 10 Update 1 or later installed on a local drive
• Sun released patch 120222-06 or later installed
• Emulex® FCA utility version 1.00m (which includes emlxdrv 1.00j for SPARC) or later installed
(see the Emulex FCA Utilities Reference Manual for installation instructions)
• Emulex lpfc driver not yet installed
To unbind the HBAs from the SFS driver, do the following:
1. Start the emlxdrv utility as described in the Emulex FCA Utilities Reference Manual.
2. Type the following command at the emlxdrv prompt:
clear_all
This unbinds from emlxs all HBAs that are recognized by both emlxs and lpfc drivers.
3. Exit the emlxdrv utility by typing the following:
q
Install the lpfc driver as instructed in the documentation that accompanies the driver.

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit) Solaris 10 Updates and the lpfc
Driver
The behavior of the Solaris operating system changes beginning with Solaris 10 Update 1 (also referred
to as Solaris 10 1/06 release). Starting with this version, a bare-metal installation of the operating system
automatically discovers all SFS-recognized HBAs (Sun-branded, Emulex, or EMC-branded) and binds
them to the “emlxs” SFS driver. A subsequent installation of lpfc will not discover and bind these HBAs;
you must use the emlxdrv utility to unbind the HBAs from the SFS driver as described in this document.

Note: You do not need to follow the procedure described in this document in the following
circumstances:
• If the server contains any Sun-branded HBAs, which are recognized
and supported only by the emlxs driver and not by the lpfc driver; you
must use the emlxs driver on all HBAs.
• If you installed an earlier version of Solaris and bound the HBAs to the
lpfc driver; updating to Solaris 10 Update 1 (or later) by applying
patches will not unbind the HBAs from the lpfc driver.

Prerequisites:
• SPARC platform
• Solaris 10 Update 1 or later installed on a local drive
• Sun released patch 120222-06 or later installed
• Emulex® FCA utility version 1.00m (which includes emlxdrv 1.00j for SPARC) or later installed
(see the Emulex FCA Utilities Reference Manual for installation instructions)
• Emulex lpfc driver not yet installed
To unbind the HBAs from the SFS driver, do the following:
1. Start the emlxdrv utility as described in the Emulex FCA Utilities Reference Manual.
2. Type the following command at the emlxdrv prompt:
clear_all
This unbinds from emlxs all HBAs that are recognized by both emlxs and lpfc drivers.
3. Exit the emlxdrv utility by typing the following:
q
Install the lpfc driver as instructed in the documentation that accompanies the driver.

LPFC Driver
Important Information about Solaris 10 Update 1
Base driver, HBAnyware utility 2.1a18, HBAnyware Security Configurator 2.1a18 and lputil 2.0a9

HBAnyware 2.1a18 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.02c, or later
hbaapi 2.0e

Java Runtime Environment

Version 1.4 or later of the Java Runtime Environment (JRE) must
be installed. HBAnyware will not run under earlier versions of
the JRE.

HBAnyware and hbacmd currently will not run under Solaris 6.

The JRE and instructions for installation can be found at http://java.sun.com/downloads/index.html

JAVA NOTE:
HBAnyware needs the java runtime binaries and libraries, so their path needs to be included in the PATH
environment variable. For example, if your java runtime binaries are in /usr/java/bin, then include this path
in your PATH environment variable. (bash> export PATH="$PATH:/usr/java/bin")


HBAnyware is dependant on lpfcdriver being installed, so install lpfcdriver first if it is not already installed.

1. Run the pkgrm routine to remove any previous version of HBAnyware: pkgrm HBAnyware
2. Copy the HBAnyware-2.1a18-sparc.tar.gz file to a directory on the install machine
3. cd to the directory which you copied the tar file
4. Unzip the file: gunzip HBAnyware-2.1a18-sparc.tar.gz
5. Untar the file: tar -xvf HBAnyware-2.1a18-sparc.tar
6. Run the pkgadd routine: pkgadd -d .
7. When prompted by pkadd, choose to install HBAnyware
Running the HBAnyware GUI

1. su to root
2. Run the script /usr/sbin/hbanyware/hbanyware
Helpful scripts

/usr/sbin/hbanyware/stop_hbanyware - This script will stop all HBAnyware daemons and GUIs.
Run this if you need to unload the driver.

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Base driver, HBAnyware utility 2.1a18, HBAnyware Security Configurator 2.1a18 and lputil 2.0a9

HBAnyware 2.1a18 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.02c, or later
hbaapi 2.0e

Java Runtime Environment

Version 1.4 or later of the Java Runtime Environment (JRE) must
be installed. HBAnyware will not run under earlier versions of
the JRE.

HBAnyware and hbacmd currently will not run under Solaris 6.

The JRE and instructions for installation can be found at http://java.sun.com/downloads/index.html

JAVA NOTE:
HBAnyware needs the java runtime binaries and libraries, so their path needs to be included in the PATH
environment variable. For example, if your java runtime binaries are in /usr/java/bin, then include this path
in your PATH environment variable. (bash> export PATH="$PATH:/usr/java/bin")


HBAnyware is dependant on lpfcdriver being installed, so install lpfcdriver first if it is not already installed.

1. Run the pkgrm routine to remove any previous version of HBAnyware: pkgrm HBAnyware
2. Copy the HBAnyware-2.1a18-sparc.tar.gz file to a directory on the install machine
3. cd to the directory which you copied the tar file
4. Unzip the file: gunzip HBAnyware-2.1a18-sparc.tar.gz
5. Untar the file: tar -xvf HBAnyware-2.1a18-sparc.tar
6. Run the pkgadd routine: pkgadd -d .
7. When prompted by pkadd, choose to install HBAnyware
Running the HBAnyware GUI

1. su to root
2. Run the script /usr/sbin/hbanyware/hbanyware
Helpful scripts

/usr/sbin/hbanyware/stop_hbanyware - This script will stop all HBAnyware daemons and GUIs.
Run this if you need to unload the driver.

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Base driver, HBAnyware utility 2.1a18, HBAnyware Security Configurator 2.1a18 and lputil 2.0a9

This kit contains the following components:

lpfc-6.02f-sparc.tar - Emulex Fibre Channel Solaris Driver
EmlxApps300a39-Solaris.tar - Emulex Applications kit
readme.first.txt - this file

It is important that the components of this kit be installed in the
appropriate order:

1) The driver kit must be installed first, followed by the applications
kit. Instructions for installing the driver kit can be found on the
Emulex website - www.emulex.com, under /ts/docfc/solframe.htm.

2) Once the driver has been successfully installed, then the applications
kit must be installed. Instructions for installing the applications kit
can be found in the README.txt file contained in the EmlxApps300a39-Solaris.tar package.

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
emlxadm version 1.00r and emlxdrv version 1.00k for SPARC; emlxdrv is needed for a fresh installation of Solaris 10 Update 1 (75.5 KB tar file)

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
emlxadm version 1.00q and emlxdrv version 1.00j for SPARC; emlxdrv is needed for a fresh installation of Solaris 10 Update 1 (77 KB tar file)

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
emlxadm version 1.00q and emlxdrv version 1.00j for SPARC; emlxdrv is needed for a fresh installation of Solaris 10 Update 1 (77 KB tar file)

Solaris 2.6, 7, 8, 9 and 10 (32-bit and 64-bit)
Installing and using the FCA utilities

Installation ...............................................................................................1
Driver Information .................................................................................................... 1
Supported Features........................................................................................... 1
New Features in this Release............................................................................ 1
Prerequisites ..................................................................................................... 2
For the lpfc Driver Kit .................................................................................. 2
Compatibility...................................................................................................... 2
Things to Know Before You Download .............................................................. 3
Known Issues .................................................................................................... 3
Installing the Driver Kit ............................................................................................ 3
Driver Kit Install Script Options.......................................................................... 4
Driver Kit Directory Structure ............................................................................. 4
Installing the Driver on Unsupported Linux Distributions.......................................... 5
Upgrading the Kernel or Applying a Distribution Service Pack or Update ................ 5
Installing the Driver Kit into an Upgraded Kernel ............................................... 5
Booting From a Non-Zero LUN Attached to an Emulex Adapter .............................. 6
Installing the HBAnyware Utility ............................................................................... 6
Uninstalling the Driver Kit .................................................................................. 7
Configuration ..........................................................................................8
Driver Configuration Methods Using modprobe and
/etc/modprobe.conf............................................................................................ 8
Temporary Configuration Method ................................................................ 8
Persistent Configuration Method ................................................................. 8
Temporary Driver Configuration by Read/Write to sysfs .................................... 9
Creating a New Ramdisk Image ...................................................................... 10
For Installed lpfc Driver Kits ...................................................................... 10
For Distribution In-Box lpfc Drivers............................................................ 10
Dynamically Adding LUNs and Targets............................................................ 10
Driver Parameters Reference Table ................................................................ 11
Using udev for Persistent Naming ................................................................... 15
Using udev to Discover Logical to Physical Mappings for sd Devices ....... 15
Configuring the System to Boot From SAN Using Persistent Names ........ 15
Using udev with st Devices ....................................................................... 16
Further Information About Persistent Names ............................................ 17
Working with Virtual Ports (vports)......................................................................... 18
Creating, Deleting and Displaying vports......................................................... 18
The mkvport.sh Script ............................................................................... 18
The rmvport.sh Script................................................................................ 19
The lsvport.sh Script ................................................................................. 19
The vport Sysfs Tree ....................................................................................... 19
Driver Version 8.2.8.14 sysfs Structure............................................................ 20
Vport sysfs Entries .................................................................................... 21
Vport Configuration Limits ............................................................................... 23
DHCHAP Authentication and Configuration ........................................................... 24
Authentication Configuration Parameters ........................................................ 25
Setting Remote and Local Passwords ............................................................. 25