Emulex LP8000DC 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

Contains: x86 BootBIOS, OpenBoot and EFIBoot This Combined Boot version 5.01a0 contains:

(1) x86 BootBIOS version 1.70a1
(2) OpenBoot version 1.41a4

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

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

\readme.txt this file you are reading
\SC501A0.PRG Lp7000 Combined Boot
\DC501A0.PRG Lp8000 Combined Boot
\CC501A0.PRG Lp9002 Combined Boot
Combined Boot Load Procedure

The Light Pulse Combined 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. 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.

2. LPUTILNT : Windows Miniport Driver.

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

3. Emulex Configuration Tool : Windows Port Driver.

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

Contains: x86 BootBIOS, OpenBoot and EFIBoot This Combined Boot version 5.01a0 contains:

(1) x86 BootBIOS version 1.70a1
(2) OpenBoot version 1.41a4

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

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

\readme.txt this file you are reading
\SC501A0.PRG Lp7000 Combined Boot
\DC501A0.PRG Lp8000 Combined Boot
\CC501A0.PRG Lp9002 Combined Boot
Combined Boot Load Procedure

The Light Pulse Combined 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. 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.

2. LPUTILNT : Windows Miniport Driver.

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

3. Emulex Configuration Tool : Windows Port Driver.

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

Contains: x86 BootBIOS, OpenBoot and EFIBoot This Combined Boot version 5.01a4 contains:

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

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

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

\readme.txt this file you are reading
\DC501A4.PRG Lp8000 Combined Boot
\CC501A4.PRG Lp9002 Combined Boot
Combined Boot Load Procedure

The Light Pulse Combined 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. 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.

2. LPUTILNT : Windows Miniport Driver.

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

3. Emulex Configuration Tool : Windows Port Driver.

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

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: 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
\DO131A5.PRG Lp8000 Open Firmware 1.31A5
--------------- 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.30a5 ------------------------

1. Fixed bug on inputting a invalid LUN number got an "Unexpected SCSI
command encountered.", then tried a good command, and cause the
machine hung.

2. Fixed bug on inputting a invalid WWPN number and continue to access
LOGO and PLOGI instead of exit.

3. Disable the message "Can't open disk label package" on IBM machine
for non-bootable disks.

----------------------- NEW CHANGES 1.30a6 ------------------------

1. Bug fixed for FCODE map-in doesn't match decoded register error.
Especially for true 64-bit machine.

2. Bug fixed for "Error: can't free iommu-list" due to the data
structure memory allocation problem on true 64-bit machine.

3. Enhanced the behavior to relogin if a target logs out during
the boot sequence.

4. Added auto-topology support - try coming up in point to point
mode first, if unsuccessful try coming up in loop mode. This
release can not set loop only or point to point only mode. These
topology options will be added to the next release.

5. Fixed bug to check the FCP_RSP_LEN_VALID bit in the FCP_RESP frame,
before using the FCP_RSP_LEN field to calculate the starting
address of the sense data.

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, 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).
O141a0.txt The file you are reading

SO141a0.PRG Lp7000 OpenBoot 1.41a0
DO141a0.PRG Lp8000 OpenBoot 1.41a0
CO141a0.PRG Lp9000 OpenBoot 1.41a0
HO141a0.PRG Lp9802 OpenBoot 1.41a0
TO141a0.PRG Lp10000 OpenBoot 1.41a0

--------------- 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.41A0 ------------------------

1. In some UNIX server, the OS Fcode interpreter does not contains the
word "vendor-id" or "device-id" in their library, during the DR
login, it will cause the segmentation error if the Fcode is using
those words to locate the vendor or device ids' address in PCI config
space. This new fix will use the "my-space" method instead.

2. The boot device path is report incorrect path on devalias in some
latest release server, and cause boot failure. This release takes
care the issue by replace new device path function.
----------------------- 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.

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.

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.

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)

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)

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).
\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: 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. This Emulex BootBIOS currently supports:

(1) Multi-topology: Fabric Point to Point; FC-AL: Private loop and Public loop
(2) Multi-initiators: Up to 8 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 a selection in Emulex BIOS Utility.
(6) Boot fail over feature: There are eight boot entries that can be configured.
If the first boot entry fails, the system will attempt to boot from the
the other configured boot drives, in order.
This release note applies to the following boot products:

SB162A1.PRG Lp7000 BootBIOS version 1.62a1
DB162A1.PRG Lp8000 BootBIOS version 1.62a1
CB162A1.PRG Lp9002 BootBIOS version 1.62a1
HB162A1.PRG Lp9802 BootBIOS version 1.62a1
QB162A1.PRG Lp850 BootBIOS version 1.62a1
RB162A1.PRG Lp950 BootBIOS version 1.62a1
LB162A1.PRG Lp982 BootBIOS version 1.62a1
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 Notes ******

(1) BIOS downloading

This version of BIOS image has increased in size to 48K. On some HBAs,
attempting to download a new .PRG file may fail only if there is not
enough empty space in the FLASH. One way to correct the problem
on those HBAs is to first download a .DWC image which does not contain
boot code (for example: dd390a7.dwc). This will clear enough space
to allow the boot .PRG file to be downloaded.

(2) BIOS was not activated (enabled)

If the adapter BIOS is not activated (enabled) by LP6DUTIL or other Emulex driver
utility, the adapter will not be configured. Also, a "No BIOS support" message
will be displayed next to this adapter in the Emulex BootBIOS Utility. The user
must use LP6DUTIL or other Emulex driver utility to activate (enable) the BootBIOS
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: Upto 8 adapters in a system
(3) Multi-LUNs: Upto 256 LUNs
(4) Multi-boot: it complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): it supports both EDD 3.0 and EDD 2.1
depending selection in BIOS Utility.
(6) Boot fail over feature: it is always there since BIOS version 1.20. There
are eight boot entries that can be configured. If the first boot entry failed
for whatever reason, it is still able to boot from the second configured boot
entry and so on.
\B161A1.txt the file you are reading

\DB161A1.PRG Lp8000 BIOS version 1.61A1

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 had increased size from 42K to 44K. As a result, it might
fail during the downloading BIOS .prg file. One way to correct the problem is to
download whenever the firmware .AWC WITHOUT BIOS image (for example: dd380a0.awc).
Then, downloading 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: Upto 8 adapters in a system
(3) Multi-LUNs: Upto 256 LUNs
(4) Multi-boot: it complies with the BIOS Boot Specification (BBS).
(5) EDD (Enhanced Disk Drive Services): it supports both EDD 3.0 and EDD 2.1
depending selection in BIOS Utility.
(6) Boot fail over feature: it is always there since BIOS version 1.20. There
are eight boot entries that can be configured. If the first boot entry failed
for whatever reason, it is still able to boot from the second configured boot
entry and so on.
\readme.txt this file you are reading

\SB160A7.PRG Lp7000 BIOS version 1.60A7
\DB160A7.PRG Lp8000 BIOS version 1.60A7
\CB160A7.PRG Lp9000 BIOS version 1.60A7
\QB160A7.PRG Lp850 BIOS version 1.60A7
\RB160A7.PRG Lp950 BIOS version 1.60A7

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 had increased size from 42K to 44K. As a result, it might
fail during the downloading BIOS .prg file. One way to correct the problem is to
download whenever the firmware .AWC WITHOUT BIOS image (for example: dd380a0.awc).
Then, downloading 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.
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 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.
readme.txt the file you are reading

SB163A1.PRG Lp7000 BIOS version 1.63a1
DB163A1.PRG Lp8000 BIOS version 1.63a1
CB163A1.PRG Lp9000 BIOS version 1.63a1
HB163A1.PRG Lp9802 BIOS version 1.63a1

QB163A1.PRG Lp850 BIOS version 1.63a1
RB163A1.PRG Lp950 BIOS version 1.63a1
LB163A1.PRG Lp982 BIOS version 1.63a1

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.
\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 software kit supports the LP80xx series of PCI host adapters.
The host adapters which are referred to as LP80xx are:

LP8000 LP8000DC

This kit includes the following files. Those marked with a "plus"
sign (+) are available from the Emulex website.

README.TXT The file you are reading
C311REL.TXT Combination BootBIOS and OpenBoot release notes
B160REL.TXT BootBIOS release notes
O131REL.TXT OpenBoot release notes

DDC390a7.DWC Firmware files for the HBA, with BootBIOS
DDC390a7.AWC + Firmware files with loader and BootBIOS
DD390a7.* + Firmware files without BootBIOS
/prg_kit/*.* The individual SLI, BIOS, POST, and Config files
which can be used to create the firmware above

LP6DUTIL.TXT LP6DUTIL text-based software manual
LP6DUTIL.EXE LP6000/7000/8xxx/9xxx DOS-based diagnostic 8.7a8

DEV_ID.TXT Information on setting PCI ID values
DFPLUS1.CFL Configuration file to allow PCI ID = F801
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5
DDEFAULT.CFL Configuration file for restoring PCI ID to default
Changes and Corrections:

Inactive exchange control blocks now have their X_ID obscured to insure
that they will not affect active exchanges.
(CR 3916, 3917, 3653, 3656)

Adapter firmware invalidly resets the sequence flags on an S_ID mismatch.
This was found only under very heavy load, in extreme circumstances,
in target mode. This has been fixed.
(CR 3792, 3791)

Improved operation of E_D_TOV timer when closing exchange.
(CR 3794, 3793)

Corrected self-test problem reporting wrong internal test number.
(CR 3788, 3803)

Improved wake-up failure reporting capability. Added the ability to
read the additional wake-up errors from SLIM memory. (CR 3804, 3807)

Due to the length of time required to close out an aborted exchange with
a remote port which is not responding, the "early abort notification" is
now forced into the active state for timed-out commands. (CR 3853, 3854)

Solved a timeout problem when switching from LOOP to P2P when connected
to a switch port. (CR 3806, 3856)

Added extra delay to TX/RX DMA timeout trap to allow for special PCI
bus designs. (CR 3860, 3861)

A data transfer which completed after the link went down was
incorrectly flagged as an internal BIU error. Fixed. (CR 3616, 3478)

Corrected response to READ_LA mailbox command so that valid current and
link down state information is returned. (CR 3630, 3635)

A method of detecting and correcting a single-bit FLASH error was added
for the 128K FLASH boot sector. This addresses all known instances of
charge migration in the FLASH. (CR 3709, 3710)

Compatibility:

This software kit supports the following PCI host adapters:

LP8000 LP8000DC

This kit includes the following files:

README.TXT The file you are reading
C322a0.TXT Combination Boot release notes
B170A1.TXT BootBIOS release notes
O141A2.TXT OpenBoot release notes

DDC392A2.DWC Firmware with Combination Boot
DDC392A2.AWC Firmware with loader and Combination Boot
DD392A2.DWC Firmware with no boot code
DD392A2.AWC Firmware with loader, no boot code
/prg_kit/*.* The individual SLI, boot, loader, and config files
which can be used to create the firmware above

DEV_ID.TXT Information on setting PCI ID values
DFPLUS1.CFL Configuration file to allow PCI ID = F801
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5
DDEFAULT.CFL Configuration file for restoring PCI ID to default

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

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

Several symptoms, ranging from I/O errors to HBA hang, were caused by
the power management reset process and Solaris "Dynamic Reconfiguration"
process, both of which required a change in the HBA to assure that the
PCI configuration was ready within a very short time after HBA reset.
(CR 5204, 6941, 6961, 7097, 8634, 8635, 8637, 8638, 9398, 10212)

Enabled use of LP952 with Open Source Linux 2.01 and newer.
(CR 9362)

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

When several commands were issued to the HBA and then one was aborted,
the firmware would occasionally not throw away all the frames for the
aborted exchange. The result was that the HBA would stop transmitting
R-RDY and no further credit would be issued. The rare instance in which
this could happen has been corrected. (CR 9393)

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 has been corrected. (CR 10117, 10058)

WWN upon receipt of a fiber login is now validated to avoid a problem
where the switch tries to access the HBA as a G-port,
(CR 10229, 10568, 10569)

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

A switch login problem in point-to-point-only mode with certain
transceivers has been corrected. (CR 9406)

A CLOSE in point-to-point mode is no longer ignored. This corrects a
deadlock problem in OldPort mode when connecting to a switch.
(CR 9438)

Compatibility:

This software kit supports the following PCI host adapters:

LP8000 LP8000DC

This kit includes the following files:

README.TXT The file you are reading
C321A1.TXT Combination BootBIOS and OpenBoot release notes
B163A2.TXT BootBIOS release notes
O140A0.TXT OpenBoot release notes

DDC391A3.DWC Firmware files for the HBA, with boot code
DDC391A3.AWC Firmware files with loader and boot code
DD391A3.* Firmware files without boot code
/prg_kit/*.* The individual SLI, Boot, POST, and Config files
which can be used to create the firmware above

LP6DUTIL.EXE LP6000/7000/8xxx/9xxx DOS-based diagnostic 9.0a13
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.0A13

DEV_ID.TXT Information on setting PCI ID values
DFPLUS1.CFL Configuration file to allow PCI ID = F801
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5
DDEFAULT.CFL Configuration file for restoring PCI ID to default
Changes and Corrections:

Added or refined features as per customer request.
(CR 8174, 8478, 8479, 8222, 8472, 8473,4932, 4933, 4934, 4935, 4936,
4937, 4938, 4939, 4940, 4588, 4650, 4684)

Development, desk checks and source code review found possible problems
which had no reported instances of failure.
(CR 8489, 8490, 8439, 8176, 8474, 8475, 8194, 8486, 8487, 7029, 7525,
7548, 7551, 7555, 7556, 7570, 7604, 7605,6838, 7094, 7095)

Corrected adapter response to improper command caused by driver bug.
(CR 7756, 7971, 7972, 7973)

Eliminated abort response for broadcast frames which fail checks.
(CR 7907, 7908, 7909, 7549)

Corrected handling of frames in target mode where header and CRC are
valid but payload is undersized. Behavior changed to discard the frame
and generate a LIP. (CR 7670, 7953, 7954, 7898)

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

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

Target mode IOCB response was corrected to send proper XRI value.
(CR 7547, 7730, 8993)

To prevent a two second general timeout and error when in target mode
waiting for an ACK1, a timer was invoked specifically for that situation.
(CR 7547, 7730, 8993)

Buffer management was modified to rebuild the buffer structure during
the topology change for link-down/link-up conditions.
(CR 6895, 7706, 9028)

The solution to a very rare instance during which link does not come up
when two Pegasus boards are directly connected has been applied to all
models of HBA. (CR 7704, 7705)

Compatibility:

This software kit supports the following PCI host adapters:

LP8000 LP8000DC

This kit includes the following files:

README.TXT The file you are reading
C500A5.TXT Combination Boot release notes

DDC393A0.AWC Firmware with loader and Combination Boot
DD393A0.AWC Firmware with loader, no boot code

LP6DUTIL.EXE DOS-based HBA diagnostic utility 9.3a4
LP6DUTIL.DOC LP6DUTIL diagnostic utility document
SAMPLESCRIPT.TXT An example script for LP6DUTIL 9.3a4
Changes and Corrections:
Corrected response in a RCV_SEQ_LIST64 IOCB. (CR 11220)

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

Parity errors due to loop init received during speed negotiation
are now processed properly. (CR 13463, 14239, 14241)

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)

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

Invalid exchange handling was improved by not issuing an error when
buffers are returned for use. (CR 13413, 14593)

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

Receiving a LIP while loop master and while waiting for LIHA will no
longer cause a timeout. (CR 13636, 13638, 14448, 14595)

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

Corrected a dropped IWRITE command when using discontinuous buffer
descriptor entries (BDEs). (CR 10342, 10447, 14597)

Allow use of a different FLASH memory chip [AM29LV160DB].
(CR 14599, 13059, 12545)

An uninitialized value (usually zero) was being returned for the ED_TOV
value when a default value of 10 was actually being used by the
firmware. The reported value is now correctly intialized to 10.
(CR 14108, 14603)

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

Compatibility:

This software kit supports the LP80xx series of PCI host adapters.
The host adapters which are referred to as LP80xx are:

LP8000 LP8000DC

This kit includes the following files. Those marked with a "plus"
sign (+) are available from the Emulex website.

README.TXT The file you are reading
C311REL.TXT Combination Intel-Boot and Open-Boot release notes
B160REL.TXT BootBIOS release notes
O131REL.TXT OpenBoot release notes

DDC330a7.DWC Firmware files for the HBA, with BootBIOS
DDC330a7.AWC + Firmware files with loader and BootBIOS
DD330a7.* + Firmware files without BootBIOS
/prg_kit/*.* The individual SLI, BIOS, POST, and Config files
which can be used to create the firmware above

LP6DUTIL.TXT LP6DUTIL text-based software manual
LP6DUTIL.EXE LP6000/7000/8xxx/9xxx DOS-based diagnostic 8.7a8

DEV_ID.TXT Information on setting PCI ID values
DFPLUS1.CFL Configuration file to allow PCI ID = F801
FDEFAULT.CFL Configuration file to allow PCI ID = 1AE5
DDEFAULT.CFL Configuration file for restoring PCI ID to default
Changes and Corrections:

Inactive exchange control blocks now have their X_ID obscured to insure
that they will not affect active exchanges.
(CR 3916, 3917, 3653, 3656)

Adapter firmware invalidly resets the sequence flags on an S_ID mismatch.
This was found only under very heavy load, in extreme circumstances,
in target mode. This has been fixed.
(CR 3792, 3791)

Improved operation of E_D_TOV timer when closing exchange.
(CR 3794, 3793)

Corrected self-test problem reporting wrong internal test number.
(CR 3788, 3803)

Improved wake-up failure reporting capability. Added the ability to
read the additional wake-up errors from SLIM memory. (CR 3804, 3807)

Due to the length of time required to close out an aborted exchange with
a remote port which is not responding, the "early abort notification" is
now forced into the active state for timed-out commands. (CR 3853, 3854)

Solved a timeout problem when switching from LOOP to P2P when connected
to a switch port. (CR 3806, 3856)

Added extra delay to TX/RX DMA timeout trap to allow for special PCI
bus designs. (CR 3860, 3861)

Corrected HBA memory initialization problem with the BootBIOS utility
setting P2P mode on the LP8000. (CR 3647)

Corrected response to READ_LA mailbox command so that valid current and
link down state information is returned. (CR 3630, 3635)

A method of detecting and correcting a single-bit FLASH error was added
for the 128K FLASH boot sector. This addresses all known instances of
charge migration in the FLASH. (CR 3709, 3710)

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.

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.

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

Prerequisites
One open 32-bit or 64-bit (recommended) PCI bus slot with a 3.3 VDC
or 5.0 VDC signaling interface
·
· Maximum PCI bus clock rate of 33 MHz
· Media and connectors (user supplied)
Multimode fiber optic cable (50/125 m m or 62.5/125 m m) with
dual SC connectors, used with short wave lasers
¨
Single mode fiber optic cable (9/125 m m) with dual SC
connectors, used with long wave lasers
¨
¨ Copper duplex cabling with DB9 connectors (also called DE9)

Install Host Bus Adapter Board
Record IEEE address and serial number.
Each host adapter is shipped with a unique address identifier called the
IEEE address. The Fibre Channel industry uses a World Wide Name
(WWN) derived from the IEEE address, and this number is need for
arbitrated loop connectivity. The serial number is used when
communicating with Emulex. Both numbers are clearly marked on the
board. We recommend that you record these numbers before installation.
1.
2. Turn off and unplug the computer.
3. Remove the computer case.
4. Remove the blank panel from an empty 32- or 64-bit PCI bus slot.
Insert host adapter board into the empty 32- or 64-bit PCI bus slot.
Press firmly until the board is seated.
5.
Secure the host adapter's mounting bracket to the case with the panel
screw.
6.
7. Replace the computer case and tighten case screws.
The host adapter is now installed in the PC and is ready for media attachment.

Change the GBIC Connector
A GBIC, or Gigabit Interface Converter, is a connector that offers a flexible
choice of copper or fiber optic media. A GBIC supports either short wave or long
wave optical transmission. These types are available:
· Short-wave fiber optic GBIC with dual SC connectors
· Long-wave fiber optic GBIC with dual SC connectors
· Copper GBIC with DB9 connector
Caution An Emulex supplied GBIC is required to maintain regulatory
compliance with worldwide certifications (for example, FCC,
C-Tick, CE, and so on).
A GBIC should be matched with its cabling to obtain optimum performance and
distance. For example, a short wave fiber optic GBIC best supports either
62.5/125 or 50/125 multimode cable, while a long wave fiber optic GBIC
functions best with 9/125 single mode cable.

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

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 (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)
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)
SMI-S HBA Provider, compliant with the SMI-S 1.1.0 specification and certified against the SNIA-CTP v1.1.0.85 suite

Pre-packaged with OpenPegasus CIMOM v2.5.1, as a turnkey SMI-S agent for ease of installation and deployment
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

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

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)

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 ...............................................................................................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, 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)
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.

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

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.

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

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

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

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 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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information. 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 8, 9 and 10 (32-bit and 64-bit)
Note: Emulex recommends installing driver version 6.11cx2, which adds a critical fix to the previously posted 6.11c driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases 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 8, 9 and 10 (32-bit and 64-bit)
Note Emulex recommends installing driver version 6.10gx2, which adds a critical fix to the previously posted 6.10g driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases 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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note Emulex supports current Solaris x86 systems through an SFS driver
Note For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases 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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note Emulex supports current Solaris x86 systems through an SFS driver
Note For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
lputil Utility User Manual

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.

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note - Emulex supports current Solaris x86 systems through an SFS driver
Note - For legacy lpfc drivers that are not listed under Previous Releases
LPFC Driver for Solaris 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

This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Base driver, HBAnyware utility 3.3a22 and lputil 2.0a13

HBAnyware 3.3a19 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.20g, emlxsdriver 2.20a, or later
hbaapi 2.0.f

Java Runtime Environment

Version 1.5 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. HBAnyware and hbacmd target OS versions
include Solaris 5.8, 5.9, 5.10, and 5.11.

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 a driver being installed, so install lpfcdriver or emlxsdriver first if it is not already installed.

1. Run the pkgrm routine to remove any previous version of HBAnyware: pkgrm HBAnyware
2. Run the unpack script : ./unpack_apps
to obtain correct package version
3. Unzip the file: gunzip HBAnyware-3.3a19-sparc.tar.gz
4. Untar the file: tar -xvf HBAnyware-3.3a19-sparc.tar
5. Run the pkgadd utility: pkgadd -d .
6. When prompted by pkgadd, choose to install HBAnyware
7. When prompted by pkgadd, answer the HBAnyware installation option questions
Running the HBAnyware GUI

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

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note Emulex recommends installing driver version 6.10gx2, which adds a critical fix to the previously posted 6.10g driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
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 8, 9 and 10 (32-bit and 64-bit)
Note: Emulex recommends installing driver version 6.11cx2, which adds a critical fix to the previously posted 6.11c driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases

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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note Emulex supports current Solaris x86 systems through an SFS driver
Note For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
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

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note - Emulex supports current Solaris x86 systems through an SFS driver
Note - For legacy lpfc drivers that are not listed under Previous Releases
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

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note Emulex supports current Solaris x86 systems through an SFS driver
Note For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
emlxadm version 1.01a 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 8, 9 and 10 (32-bit and 64-bit)
Note: Emulex recommends installing driver version 6.11cx2, which adds a critical fix to the previously posted 6.11c driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
emlxadm version 1.01a 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 8, 9 and 10 (32-bit and 64-bit)
Note Emulex recommends installing driver version 6.10gx2, which adds a critical fix to the previously posted 6.10g driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note - Emulex supports current Solaris x86 systems through an SFS driver
Note - For legacy lpfc drivers that are not listed under Previous Releases
emlxadm version 1.01a 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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note - Emulex supports current Solaris x86 systems through an SFS driver
Note - For legacy lpfc drivers that are not listed under Previous Releases
Instructions for using emlxdrv

Introduction.............................................................................................................. 1
Fibre Channel Overview .................................................................................... 1
The Solaris Fibre Channel Stack ....................................................................... 1
Installing the Utilities................................................................................................ 3
Compatibility...................................................................................................... 3
Installing or Updating the Utilities Using the emlxu_install Script....................... 4
Removing the Utilities Using the emlxu_remove Script ..................................... 5
Installing the Utilities Package Manually............................................................ 6
Removing the Utilities Package Manually.......................................................... 7
Updating the Utilities Package Manually ........................................................... 7
Using the emlxadm Utility ........................................................................................ 8
Modes of Operation (emlxadm) ......................................................................... 8
Interactive Mode (emlxadm)........................................................................ 8
CLI Mode (emlxadm)................................................................................... 9
Command Descriptions (emlxadm) ................................................................. 11
Using the emlxdrv Utility ........................................................................................ 31
Modes of Operation (emlxdrv) ......................................................................... 31
Interactive Mode (emlxdrv)........................................................................ 31
CLI Mode (emlxdrv)................................................................................... 33
Command Descriptions (emlxdrv) ................................................................... 33

This document provides the information needed to use the Emulex® emlxadm and elmxdrv utility
programs. For system administrators, this document includes information about the installation and
removal of these utilities.
At the very least, system administrators should be familiar with Solaris and the Sun StorEdge SAN
Foundation Software (SFS) and should have access to standard system documentation. Anyone
working with this product should have some familiarity with the nature and use of Fibre Channel.

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note Emulex recommends installing driver version 6.10gx2, which adds a critical fix to the previously posted 6.10g driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
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

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with this Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note Emulex supports current Solaris x86 systems through an SFS driver
Note For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
Base driver, HBAnyware utility 3.3a22 and lputil 2.0a13 (21.5 MB tar file)

Solaris 8, 9 and 10 (32-bit and 64-bit)
Note Emulex recommends installing driver version 6.10gx2, which adds a critical fix to the previously posted 6.10g driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
Base driver, HBAnyware utility 3.0a17 and lputil 2.0a13

HBAnyware 3.0a17 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.10b, or later
hbaapi 2.0f

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. HBAnyware and hbacmd target OS versions
include Solaris 5.8, 5.9, and 5.10.

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. Run the unpack script : ./unpack_apps
to obtain correct package version
3. Unzip the file: gunzip HBAnyware-3.0a17-sparc.tar.gz
4. Untar the file: tar -xvf HBAnyware-3.0a17-sparc.tar
5. Run the pkgadd utility: pkgadd -d .
6. When prompted by pkadd, choose to install HBAnyware
7. When prompted by pkadd, answer the HBAnyware installation option questions
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 8, 9 and 10 (32-bit and 64-bit)
Note: Emulex recommends installing driver version 6.11cx2, which adds a critical fix to the previously posted 6.11c driver. Driver functionality and behavior are otherwise identical.
Note Emulex supports current Solaris x86 systems through an SFS driver
For a legacy lpfc driver for Solaris 9 x86, or for Solaris 8 SPARC legacy drivers that are not listed under Previous Releases
Base driver, HBAnyware utility 3.1a12 and lputil 2.0a13

HBAnyware 3.1a12 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.11c, emlxsdriver 2.20a, or later
hbaapi 2.0f

Java Runtime Environment

Version 1.5 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. HBAnyware and hbacmd target OS versions
include Solaris 5.8, 5.9, and 5.10.

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 a driver being installed, so install lpfcdriver or emlxsdriver first if it is not already installed.

1. Run the pkgrm routine to remove any previous version of HBAnyware: pkgrm HBAnyware
2. Run the unpack script : ./unpack_apps
to obtain correct package version
3. Unzip the file: gunzip HBAnyware-3.1a12-sparc.tar.gz
4. Untar the file: tar -xvf HBAnyware-3.1a12-sparc.tar
5. Run the pkgadd utility: pkgadd -d .
6. When prompted by pkadd, choose to install HBAnyware
7. When prompted by pkadd, answer the HBAnyware installation option questions
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 8, 9 and 10 (32-bit and 64-bit)
Note This driver version requires patch #112438 for
Solaris 8 operation.
Starting with Solaris driver version 6.20, the driver no longer uses the sd.conf and st.conf files to limit the storage presented to the OS. If your environment uses these files to perform LUN or target masking, refer to the driver manual for important configuration information.
Note - Emulex supports current Solaris x86 systems through an SFS driver
Note - For legacy lpfc drivers that are not listed under Previous Releases
Base driver, HBAnyware utility 3.4a15, emlxdrv utility 1.00l; emlxdrv is needed for a fresh installation of Solaris 10 Update 1

HBAnyware 3.4a15 Solaris Installation Instructions

Dependencies:

lpfcdriver 6.21a, emlxsdriver 2.20a, or later
hbaapi 2.0.f

Java Runtime Environment

Version 1.5 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. HBAnyware and hbacmd target OS versions
include Solaris 5.8, 5.9, 5.10, and 5.11.

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 a driver being installed, so install lpfcdriver or emlxsdriver first if it is not already installed.

1. Run the pkgrm routine to remove any previous version of HBAnyware: pkgrm HBAnyware
2. Run the unpack script : ./unpack_apps
to obtain correct package version
3. Unzip the file: gunzip HBAnyware-3.4a15-sparc.tar.gz
4. Untar the file: tar -xvf HBAnyware-3.4a15-sparc.tar
5. Run the pkgadd utility: pkgadd -d .
6. When prompted by pkgadd, choose to install HBAnyware
7. When prompted by pkgadd, answer the HBAnyware installation option questions
Running the HBAnyware GUI

1. su to root
2. Run the script /opt/emulex/hbanyware/hbanyware

Qualification: The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium 64-bit platforms. The 64-bit Itanium SCSIport Miniport driver is also Microsoft WHQL qualified and digitally signed for Windows Server 2003, Datacenter Edition. The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
Base driver, HBAnyware utility 2.1a17 and lputilnt 1.8a15 (15 MB exe file)

Qualification: The driver for Windows Server 2003 is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium platforms. The driver for Windows 2000 Server is qualified and digitally signed by WHQL labs for Server The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
OS Versions: Windows Server 2003 SP1 and Windows Server 2000 SP2
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note If you are upgrading from Windows 2000 Server to Windows Server 2003 and are currently running an Emulex SCSIport Miniport driver, you must uninstall the driver before upgrading the operating system. Reinstall the Emulex SCSIport Miniport driver after you upgrade the operating system.
Base driver, HBAnyware utility 2.1a16 and lputilnt 1.8a13
(14.4 MB exe file)

Qualification: The driver for Windows Server 2003 is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium platforms. The driver for Windows 2000 Server is qualified and digitally signed by WHQL labs for Server The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
OS Versions: Windows Server 2003 SP1 and Windows Server 2000 SP2
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note If you are upgrading from Windows 2000 Server to Windows Server 2003 and are currently running an Emulex SCSIport Miniport driver, you must uninstall the driver before upgrading the operating system. Reinstall the Emulex SCSIport Miniport driver after you upgrade the operating system.
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

Qualification: The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium 64-bit platforms. The 64-bit Itanium SCSIport Miniport driver is also Microsoft WHQL qualified and digitally signed for Windows Server 2003, Datacenter Edition. The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
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

Qualification: The driver for Windows Server 2003 is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium platforms. The driver for Windows 2000 Server is qualified and digitally signed by WHQL labs for Server The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
OS Versions: Windows Server 2003 SP1 and Windows Server 2000 SP2
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note If you are upgrading from Windows 2000 Server to Windows Server 2003 and are currently running an Emulex SCSIport Miniport driver, you must uninstall the driver before upgrading the operating system. Reinstall the Emulex SCSIport Miniport driver after you upgrade the operating system.
Installing the driver using AutoPilot Installer (3,085 KB)

Qualification: The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium 64-bit platforms. The 64-bit Itanium SCSIport Miniport driver is also Microsoft WHQL qualified and digitally signed for Windows Server 2003, Datacenter Edition. The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
Installing the driver using AutoPilot Installer (468 KB)

Qualification: The 32-bit SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003, and it is Microsoft WHQL qualified and digitally signed for Windows 2000 Server The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note The installation procedure for the driver and utilities has changed from earlier versions. For installation information, see the online Installation manual.

Qualification: The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003 on x86 and Itanium 64-bit platforms. The 64-bit Itanium SCSIport Miniport driver is also Microsoft WHQL qualified and digitally signed for Windows Server 2003, Datacenter Edition. The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
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
(6.97 MB exe file)

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or later, and the KB932755 update to the Microsoft Storport driver, are required.
SMI-S HBA Provider, compliant with the SMI-S 1.1.0 specification and certified against the SNIA-CTP v1.1.0.85 suite
Pre-packaged with OpenPegasus CIMOM v2.5.1, as a turnkey SMI-S agent for ease of installation and deployment
(7.18 MB exe file)

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note The KB916048 update to the Microsoft Storport driver is required.
SMI-S HBA Provider, compliant with the SMI-S 1.1.0 specification and certified against the SNIA-CTP v1.1.0.85 suite
Pre-packaged with OpenPegasus CIMOM v2.5.1, as a turnkey SMI-S agent for ease of installation and deployment
(7.18 MB exe file)

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or SP2 and the KB932755 update to the Microsoft Storport driver are required. The KB932755 update must be applied before the Emulex Storport Miniport driver version 2.00 can be installed.
HBAnyware Utility Version 3.3

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

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or SP2 and the KB932755 update to the Microsoft Storport driver are required. The KB932755 update must be applied before the Emulex Storport Miniport driver version 2.00 can be installed.
Storport Miniport Driver Version 2.00 for Windows Server 2003 and Windows Vista

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

Qualification: The 32-Bit SCSIport Miniport driver is qualified and digitally signed by WHQL labs for Windows Server 2003 and Windows 2000 Server and Workstation products (Service Pack 2 or above).
For Windows 2000 Server, Service Pack 4 is required for cluster configurations.
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note The installation procedure for the driver and utilities has changed from earlier versions. For installation information, see the online Installation manual.

Qualification: The 32-Bit SCSIport Miniport driver is qualified and digitally signed by WHQL labs for Windows Server 2003 and Windows 2000 Server and Workstation products (Service Pack 2 or above).
For Windows 2000 Server, Service Pack 4 is required for cluster configurations.
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note The installation procedure for the driver and utilities has changed from earlier versions. For installation information, see the online Installation manual.

Qualification: The 32-bit SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows Server 2003, and it is Microsoft WHQL qualified and digitally signed for Windows 2000 Server The SCSIport Miniport driver is Microsoft WHQL qualified and digitally signed for Windows 2000 Server.
For Windows 2000 Server, Service Pack 4 is required.
Note New versions are available for all Emulex drivers that include support for Windows Server 2003 SP1. We recommend that you upgrade to one of these new drivers. In most cases, older drivers can be configured to work with SP1 by running the HBA API-SP1 Migration program prior to installing SP1.
Note If you are currently running the Emulex SCSIport Miniport driver version 5.10a10 or earlier, please follow these
Upgrade Instructions before upgrading from Windows 2000 Server to Windows Server 2003.
Note The installation procedure for the driver and utilities has changed from earlier versions. For installation information, see the online Installation manual.

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or later, and the KB932755 update to the Microsoft Storport driver, are required.
Installing the driver using AutoPilot Installer (498 KB)

Introduction
AutoPilot Installer™ for Emulex® drivers provides installation options that range from a simple
installation with a few mouse clicks to custom unattended installations using predefined script files.
AutoPilot Installer is included with Emulex drivers and utilities in Windows executable files that can be
downloaded from the Emulex Web site. Run the distribution executable file to extract all of the software
needed for an installation, then complete the installation using AutoPilot Installer.
AutoPilot Installer allows you to install a driver using any of the following methods:
Hardware-first installation. The host bus adapter (HBA) is installed before the downloaded Emulex
drivers and utilities are installed. See page 3 for this procedure.
Software-first installation. This new installation method allows drivers and utilities to be downloaded
from the Emulex Web site and installed using AutoPilot Installer prior to the installation of any HBAs. The
drivers and utilities are automatically used when HBAs are installed at a later time. See page 4 for this
procedure.
Unattended installation. This new installation method allows you to set up AutoPilot Installer to run
unattended using customized scripts. Unattended installation can be used for both hardware-first and
software-first installations. See the complete Installation section of the driver user manual for more
information.

Updating the Driver Using AutoPilot Installer
If you are currently running an older driver version, use the hardware-first installation procedure to
update your driver. Begin at step 2 to update the driver.
You can also update the Emulex drivers following the manual installation method. See the complete
Installation section of the driver user manual for this procedure.

Distribution Executable File Overview
The distribution executable file is a self-extracting file that includes the following:
• AutoPilot Installer - installs driver and utilities.
• Driver - manages communication and data transfer between applications and I/O devices, using
HBAs as agents.
• HBAnyware utility - performs installation and configuration tasks on remote and local adapters.
• Driver-specific utility (elxcfg for FC Port, lputilnt for Storport Miniport and SCSIport Miniport) -
provides a user-friendly interface that allows you to examine, manage and configure local HBAs.
4. The default installation location is displayed. Browse to a different location, if desired. Click
Install to continue the installation.
5. The Progress window is displayed. As each task is completed, the corresponding checkbox is
automatically selected.
6. After all tasks are completed, a confirmation window is displayed. The Start AutoPilot Installer
checkbox is automatically selected. To start AutoPilot Installer later, clear this checkbox.
7. Click Finish to close the distribution executable file.
AutoPilot Installer Introduction
The Emulex AutoPilot Installer is a Fibre Channel HBA installation wizard for Windows. The AutoPilot
Installer installs (or updates) Emulex drivers and utilities and configures HBAs, drivers and utilities.

Prerequisites
• One of the following operating systems:
•Windows Server 2003 running on an x86, x64 or Itanium 64-bit platform.
•For the Emulex Storport Miniport driver, a Microsoft driver update may be required. See the Emulex Web site for the latest update to the Microsoft Storport driver.
•Windows 2000 Server - Service Pack 4 or later is recommended for all installations. Storport Miniport is not compatible with Windows 2000 Server.

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note The KB916048 update to the Microsoft Storport driver is required.
Installation, Configuration and Troubleshooting (3,264 KB)

Introduction.............................................................................................................. 1
Important Considerations......................................................................................... 2
Changing Driver Types...................................................................................... 2
Microsoft Storport Driver Update ....................................................................... 2
Updating the Storport Miniport Driver Using AutoPilot Installer.......................... 2
Definitions................................................................................................................ 2
Storport Miniport Driver Information ......................................................................... 3
Prerequisites ..................................................................................................... 3
Compatibility...................................................................................................... 3
New in This Release ......................................................................................... 3
Known Issues .................................................................................................... 3
Files Included in this AutoPilot Installer ............................................................. 4
Distribution Executable File Overview ..................................................................... 5
Running the Distribution Executable File ........................................................... 5
AutoPilot Installer..................................................................................................... 6
Introduction ....................................................................................................... 6
Prerequisites ............................................................................................... 6
AutoPilot Installer Features ......................................................................... 6
Configuration Questions.............................................................................. 6
Installation Planning .......................................................................................... 6
AutoPilot Installation Procedures ............................................................................. 7
Hardware-First Installation................................................................................. 7
If the Installation Fails ................................................................................. 8
Software-First Installation .................................................................................. 8
Installing the HBAnyware Security Configurator ...................................................... 9
Unattended Installation .......................................................................................... 10
AutoPilot Configuration File Format................................................................. 10
Mandatory Configuration File Changes ........................................................... 10
Deleting Questions in the APInstall.cfg File ..................................................... 11
Optional Configuration File Changes............................................................... 11
Setting Up Driver Parameters.......................................................................... 14
Setting Up System Parameters ....................................................................... 14
Unattended Error Codes Reference Table....................................................... 14
Invoking AutoPilot Installer .............................................................................. 15
Batch File Example ......................................................................................... 15
Manually Installing or Updating the Storport Miniport Driver .................................. 17
Overview ......................................................................................................... 17
Removing the Adjunct Driver Registry Key...................................................... 17
Manually Installing the Emulex PLUS (ElxPlus) Driver .................................... 17
Manually Updating the Emulex PLUS (ElxPlus) Driver .................................... 18
Manually Installing or Updating the Storport Miniport Driver ............................ 19
Manually Installing the Driver Utilities .............................................................. 20
Uninstalling the Utility Package ....................................................................... 20
Uninstalling the Emulex Drivers....................................................................... 22
Configuration ...........................................................................................................23
Introduction............................................................................................................ 23
Starting HBAnyware from the Desktop ............................................................ 24

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or later, and the KB932755 update to the Microsoft Storport driver, are required.
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

Qualification: The Storport Miniport driver is WHQL qualified for the Microsoft "Designed for Windows" logo program and digitally signed for x86, Itanium and x64 Editions versions of Windows Server 2003 and Windows Server 2003 Datacenter Edition.
Note Windows Server 2003 SP1 or later, and the KB932755 update to the Microsoft Storport driver, are required.
Installing the driver using AutoPilot Installer (498 KB)

Introduction
AutoPilot Installer™ for Emulex® drivers provides installation options that range from a simple
installation with a few mouse clicks to custom unattended installations using predefined script files.
AutoPilot Installer is included with Emulex drivers and utilities in Windows executable files that can be
downloaded from the Emulex Web site. Run the distribution executable file to extract all of the software
needed for an installation, then complete the installation using AutoPilot Installer.
AutoPilot Installer allows you to install a driver using any of the following methods:
Hardware-first installation. The host bus adapter (HBA) is installed before the downloaded Emulex
drivers and utilities are installed. See page 3 for this procedure.
Software-first installation. This new installation method allows drivers and utilities to be downloaded
from the Emulex Web site and installed using AutoPilot Installer prior to the installation of any HBAs. The
drivers and utilities are automatically used when HBAs are installed at a later time. See page 4 for this
procedure.
Unattended installation. This new installation method allows you to set up AutoPilot Installer to run
unattended using customized scripts. Unattended installation can be used for both hardware-first and
software-first installations. See the complete Installation section of the driver user manual for more
information.

Updating the Driver Using AutoPilot Installer
If you are currently running an older driver version, use the hardware-first installation procedure to
update your driver. Begin at step 2 to update the driver.
You can also update the Emulex drivers following the manual installation method. See the complete
Installation section of the driver user manual for this procedure.

Distribution Executable File Overview
The distribution executable file is a self-extracting file that includes the following:
• AutoPilot Installer - installs driver and utilities.
• Driver - manages communication and data transfer between applications and I/O devices, using
HBAs as agents.
• HBAnyware utility - performs installation and configuration tasks on remote and local adapters.
• Driver-specific utility (elxcfg for FC Port, lputilnt for Storport Miniport and SCSIport Miniport) -
provides a user-friendly interface that allows you to examine, manage and configure local HBAs.
4. The default installation location is displayed. Browse to a different location, if desired. Click
Install to continue the installation.
5. The Progress window is displayed. As each task is completed, the corresponding checkbox is
automatically selected.
6. After all tasks are completed, a confirmation window is displayed. The Start AutoPilot Installer
checkbox is automatically selected. To start AutoPilot Installer later, clear this checkbox.
7. Click Finish to close the distribution executable file.
AutoPilot Installer Introduction
The Emulex AutoPilot Installer is a Fibre Channel HBA installation wizard for Windows. The AutoPilot
Installer installs (or updates) Emulex drivers and utilities and configures HBAs, drivers and utilities.

Prerequisites
• One of the following operating systems:
•Windows Server 2003 running on an x86, x64 or Itanium 64-bit platform.
•For the Emulex Storport Miniport driver, a Microsoft driver update may be required. See the Emulex Web site for the latest update to the Microsoft Storport driver.
•Windows 2000 Server - Service Pack 4 or later is recommended for all installations. Storport Miniport is not compatible with Windows 2000 Server.