Emulex LP9802DC Manuale Utente

Emulex Driver for HP-UX Download ManualVersion 4.20.04Table of Contents Compatibility Prerequisites Things to Know Before You Download Changes and Co

Cautions and Warnings● CAUTION: Failure to update the firmware with an image containing boot code will make the dual channel adapter unavailable

Files Included in this ReleaseThis driver kit includes the following files.File Name Descriptioncatalog/INDEX SWPackage-generated filescatalog/dfiles/

LPFC/driver/opt/lpfc/conf/adapCfg.hDriver configuration fileLPFC/driver/sbin/init.d/lpfcStart up scriptLPFC/driver/usr/conf/lib/lpfc.aDevice driver li

Verifying the Dragonfly Chip VersionThere are three methods for determining the Dragonfly chip version: Looking at the Host Bus Adapter, running the D

5. Select 3, Adapter Revision Levels . If there are multiple host adapters,specify a list of numbers from 1 – 3 separated by spaces, or use a '–

Using the UNIX-based Utility1. Enter the appropriate command to start the lputil utility:The main menu is displayed. 2. Select 2, Adapter Informatio

3. Select 2, Adapter Revision Levels. If there are multiple host adapters, a list is displayed and you need to select an adapter. The following type

Emulex Driver for HP-UX Installation ManualVersion 4.20.04Table of Contents Compatibility Prerequisites Installation Install the Driver Remove Ex

Driver InformationCompatibility● Emulex Fibre Channel adapters LP10000DC and LP10000● Emulex Fibre Channel adapters LP9802DC and LP9802 ●

● Installed Fibre Channel host bus adapter● For dual channel host bus adapters only: a version of firmware with boot code must be present on t

Driver InformationCompatibility● Emulex Fibre Channel adapters LP10000DC and LP10000● Emulex Fibre Channel adapters LP9802DC and LP9802 ●

Using the UNIX-based Utility1. Enter the appropriate command to start the lputil utility:For AIX enter: /usr/lpp/diagnostics/lputilFor HP-UX enter: /

3. Select 2, Adapter Revision Levels. If there are multiple host adapters, a list is displayed and you need to select an adapter. The following type

Install the DriverTo install the driver and boot the system, follow these instructions. While it is possible to install lpfc onto one or more clients

5. To modify the default driver configuration parameter, rebuild Kernel and Reboot the machine using the following commands:/usr/sbin/mk_kernel -o /s

Remove the Emulex lpfc Device DriverDriver Removal (swremove)The driver can be removed by using swremove. Run the following command: swremove –x autor

Emulex Driver for HP-UX Configuration ManualVersion 4.20.04Table of Contents Introduction Change Configuration Parameters Set Up Persistent Binding a

IntroductionYou can use either of the following methods to configure the driver for HP-UX:● Use HP's System Administration Tool (SAM) to make

Change Configuration Parameters Per Adapter1. Using a text editor, access the adapCfg.h configuration file by entering:cd /opt/lpfc/conf 2. Locate t

7. Save the adapCfg.h file. We recommended that you make a copy of the modified adapCfg.h file and keep it as a backup. If a new driver is installed,

adapCfg.h FileClick on a parameter to view a detailed description.Cfg Parameter Default Min Max CommentsCFG_ACK0 0 0 1Use ACK0 for Class 2CFG_AUTOMAP

● Installed Fibre Channel host bus adapter● For dual channel host bus adapters only: a version of firmware with boot code must be present on t

CFG_NODEV_TMO 0 0 255Seconds to hold I/O if device disappears.CFG_NUM_BUFS 512 64 4,096ELS and misc data buffers.CFG_NUM_IOCBS 512 128 10,240Adapter c

Set Up Persistent Binding and LUN Blocking Persistent bindings are based on the target device's WWPN, WWNN or DID. This binding guarantees that t

digit representation of the target's WWPN or WWNN. Xis the driver instance number Yis the target assignment.Line 15 provides a sample

Interpreting the IOSCAN ReportFrom the output of ioscan you can determine the hardware address and LUN. This sample output has been color coded to hel

Hardware address: 10/1/8/0.1.22SCSI ID = SCSI Offset + SCSI Index = 255 + 22 = 277This hardware address results from binding 0000e4:lpfc0t277Hardware

Understand Device NumberingWhen the driver is configured, there are various configuration parameters that rely upon device numbers. This section expla

List AdaptersWhen you start the LightPulse Utility (lputil), all adapters are listed with information such as the host adapter number, instance number

View Adapter InformationThe LightPulse Utility (lputil) allows you to view information for a selected adapter. Once you start lputil, the Main menu op

Wakeup Parameters - Displays BIOS status and version, as well as SLI (service level interface). IEEEE Address - Displays the adapter board address. Lo

Update FirmwarePrerequisites● The driver for HP-UX is installed properly.● The firmware file has been downloaded to a local drive. Firmware ve

Using the UNIX-based Utility1. Enter the appropriate command to start the lputil utility:For AIX enter: /usr/lpp/diagnostics/lputilFor HP-UX enter: /

Loading Boot CodeIf you are using the HP-UX 11.11 operating system with an Emulex LP9802DC, LP9402DC or LP8000DC host bus adapter, you must load the b

Reset the AdapterThe LightPulse Utility (lputil) is loaded automatically when the driver utilities kit is installed and allows you to reset the adapte

Download PCI ConfigurationNoteSelect this option only if you are familiar with PCI configuration registers. To download PCI Configuration follow these

Emulex Driver for HP-UX Troubleshooting ManualVersion 4.20.04Table of Contents Introduction HBA Not Available After A Firmware UpdateError Codes Tabl

IntroductionThere are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting manual explains many of thes

HBA Not Available After A Firmware UpdateSituation:On HP-UX 11.11 systems, if firmware is updated on a dual channel HBA without including boot bios th

Error Codes TableError/warning messages are logged only into /var/adm/syslog/syslog.log file. Some messages are recorded only if the log-verbose confi

Platform Independent errors - 001 to 099lpfcN: 1 : Stray ELS completionReceived an ELS command completion without issuing a corresponding ELS command

lpfcN: 3 : Device Discovery completion errorThis indicates that an uncorrectable error was encountered during device (re)discovery after a link up. Fi

lpfcN: 6 : FARP-[REQ RSP] receivedA FARP ELS command was received from a fabric. The command originator’s PortID is recorded.ACTION: None needed.WARNI

3. Select 2, Adapter Revision Levels. If there are multiple host adapters, a list is displayed and you need to select an adapter. The following type

lpfcN: 9 : FAN receivedA FAN ELS command was received from a fabric. The assigned PortID and internal driver state are recorded.ACTION: None needed.WA

lpfcN: 12 : ELS Retry failedIf an ELS command fails, it may be retried up to 3 times. This message will be recorded if the driver gives up retrying a

lpfcN: 15 : Memory Buffer Pool is out of buffersA driver memory buffer pool is exhausted. The buffer pool number is recorded.ACTION: Configure more re

lpfcN: 18 : Device Discovery StartedDevice discovery/rediscovery after FLOGI or FAN has started. The location within the driver is recorded.ACTION: No

lpfcN: 21 : Rcv Ring: out of posted buffersIf the ring number is 1 (IP ring) this usually means the system is out of TCP/IP buffers. The ring number a

lpfcN: 24 : Command ring timeoutAn IOCB command was posted to a ring and did not complete within a timeout based on R_A_TOV. The ring number and the I

lpfcN: 27 : NameServer Registration timeoutOur registration request to the fabric is not acknowledged within R_A_TOV.ACTION: Check the fabric configur

lpfcN: 30 : SCSI timeoutAn FCP IOCB command was posted to a ring and did not complete within ULP timeout seconds. The IOCB command, NPortID and SCSI I

lpfcN: 33 : SCSI Link resetThe SCSI layer has determined that the link needs to be reset. A LIP is sent to restart loop initialization. ACTION: None n

lpfcN: 36 : Abort Target I/O: clearqThis is displayed if the driver internally detects that it needs to abort all I/O to a specific device. This resul

Things to Know Before You Download● Before you download, create a temporary directory for the driver kit.● Before you update your driver, make

lpfcN: 39 : Cannot issue FCP commandA valid login with a target no longer exists. The target NPortID, SCSI ID and LUN are recorded.ACTION: Check the s

lpfcN: 42 : Xmit sequence completion errorA XMIT_SEQUENCE command completed with a status error in the IOCB. The IOCB status, the IOCB IOTAG, the IOCB

lpfcN: 45 : Adapter initialization failed, Mailbox commandThe host adapter failed to initialize properly because a mailbox command failed. The mailbox

lpfcN: 48 : Enable interrupt handler failedThis error occurs if the driver cannot assign an interrupt vector to the host adapter.ACTION: Check the con

lpfcN: 51 : [29,xx] Check condition receivedCould indicate a problem with an FCP target. The check condition response info fields are recorded. A 29,x

HP-UX specific errorsGeneral HP-UX error codes range from 100 to 109. HP-UX FCP specific error codes range from 120 to 139.lpfcN: 100 : Attach failure

lpfcN: 103 : fc_malloc: XXXXXThe driver memory allocation routine failed for reason XXXXX. Various memory allocation parameters are recorded.ACTION: T

lpfcN: 122 Override default SCSI tag age limitThe default SCSI tag age limit has been overridden. The new tag age and default tag age are recorded.ACT

lpfcN: 125 DMA allocation errorIndicates an error for allocating a DMA memory. The MALLOC status error is recorded.ACTION: This error could indicate a

lpfcN: 130 SCSI Auto Sense is not enabledThe target driver can either issue a SCSI Request Sense command when the error occurred or enable the AutoSen

Changes and Corrections● 'isoscan' was enhanced to better detect targets.● The driver software now supports analyzing trace data fro

Known IssuesThe adapCfg.h fileYou may need to modify the adapCfg.h file after installing the driver. You might also need to modify the file if the har

the SCSI target ID to the new D_ID on the fly. However, a second system may use a different SCSI target ID for that target. Thus, if you are seeking t