Emulex LP9002 Download Drivers, Manual and Firmware

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\readme.txt This file you are reading
\CO131A5.PRG Lp9000 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).
This README applies to the following boot products:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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, AIX, PowerPC

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

5. There is an issue which user can't use "Alpa" command to set Boot ID,
because the command was missing, the new release correct this issue,
so the user can use "Alpa" to set the boot id on HBA in the loop mode.
(CR9257)

Platform: SPARC, AIX, PowerPC

(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)
----------------------- NEW CHANGES 1.50a3 ------------------------

1. Bug fixed on cannot configure boot device using DID on boot.
(CR14497)

2. Bug fixed on error message "Data Stack corrupted!!!" when booting
with Fcode on some machines, the new release fixed this issue by
change the different device path /fp when booting with "SD Boot"
format. (CR14633)

3. Supported E-VPD. If e-VPD fields are empty or blank on the HBA then
the HBA will identified as it is today, if VPD HBA Model number info
is present, then display the new VPD HBA Model number. (CR15513)

4. Rename function call for setting the boot format from "set-XXX-on"
to "set-XXX-boot" to boot with XXX Boot format, and "set-XXX-off"
to "set-sd-boot" to boot with SD Boot format. (CR15514)

5. Per the FC-GS4 spec, all CT commands shall have a timeout value of
3 x R_A_TOV instead of 2 times. (CR15521)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Platform: SPARC, AIX, PowerPC This version of Open Boot supports FC-AL: Private loop and Public
loop, and Fabric Point to Point. Also, it supports multi-initiators
and multi-LUNs (0 through 255).
\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, 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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Platform: SPARC, AIX, PowerPC 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

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)

Development, desk checks and source code review found possible problems
that had no reported instances of failure.
(CR 14066, 14359, 13393, 14586, 14115, 14602, 11934, 14604, 11933,
14605, 11932, 14606, 11931, 14607, 14751)

If you use LP6DUTIL to upgrade the firmware, you must use version
8.6a4 or higher. The latest version of LP6DUTIL is included in
this kit.

Several files, such as the .DWC files and /prg_kit/ files, have been
eliminated from this kit in order to simplify the update process and
ensure correct operation of the updated HBA.

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

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

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

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

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

Prerequisites
The host computer must provide 3.3 VDC bus power (a power LED on
the bracket shows bus power)
·
One open 32-bit or 64-bit (64-bit recommended) cPCI bus slot can be
either 3.3 VDC or 5.0 VDC signaling interface
·
· PCI bus clock rate of 66 MHz is preferred
· Media and connectors

Install the Host Bus Adapter Board
Record IEEE and serial numbers.
Each host bus adapter port is shipped with a unique address identifier
called the IEEE address. Since this adapter has two ports, there are two
IEEE addresses. The IEEE address is used when configuring your
system. The serial number is used when communicating with Emulex.
All numbers are clearly marked on the board. We recommend that you
record these numbers before installing the adapter.
Turn off the computer.
Remove the blank panel from an empty 32- or 64-bit cPCI bus slot, or
remove the existing HBA.
With the lever open, hold the LP9002C board by the two side edges or
the bracket, and slide the card into the slot between the two guides.
Press on the front panel to completely seat the card in the I/O
assembly.Push the lever in to lock the lever. You should feel it click.

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

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

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

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

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

1. System Requirements

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

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

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

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

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

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

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

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

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