Emulex Troubleshooting

Troubleshooting and
Maintenance Manual
for Emulex HBAs
Copyright© 2007 Emulex Corporation. All rights reserved worldwide. No part of this document may be reproduced
by any means nor translated to any electronic medium without the written consent of Emulex Corporation.
Information furnished by Emulex Corporation is believed to be accurate and reliable. However, no responsibility is
assumed by Emulex Corporation for its use; or for any infringements of patents or other rights of third parties which
may result from its use. No license is granted by implication or otherwise under any patent or patent rights of Emulex
Corporation.
Emulex, AutoPilot Installer, BlockGuard, cLAN, FabricStream, FibreSpy, Giganet, HBAnyware, InSpeed, IntraLink,
LightPulse, MultiPulse, SAN Insite, SBOD and Vixel are registered trademarks, and AutoPilot Manager, EZPilot,
SLI and VMPilot are trademarks, of Emulex Corporation. All other brand or product names referenced herein are
trademarks or registered trademarks of their respective companies or organizations.
Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not
limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex Corporation may
make improvements and changes to the product described in this manual at any time and without any notice. Emulex
Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties
that may result. Periodic changes are made to information contained herein; although these changes will be
incorporated into new editions of this manual, Emulex Corporation disclaims any undertaking to give notice of such
changes.
Troubleshooting and Maintenance Manual for Emulex HBAs Page ii

Overview ................................................................................................................................... 1
Be Informed, Stay Informed ..................................................................................... 1
Isolating the Problem ............................................................................................... 1
Gathering Information Before Contacting Emulex Technical Support....................... 2
Common Problems .................................................................................................................. 2
Hardware Issues...................................................................................................... 2
Link Down................................................................................................................ 2
Can’t See Devices or Drives .................................................................................... 3
Out-of-Date Driver Version ...................................................................................... 4
Emulex Driver Updates...................................................................................... 4
Out-of-Date Firmware Version ................................................................................. 5
Firmware Updates ............................................................................................. 5
LEDs.......................................................................................................................................... 5
Firmware Operation and Port Activity LEDs............................................................. 5
Common LED States ............................................................................................... 6
Power Indicator LEDs........................................................................................ 6
LED Reference.................................................................................................. 6
Emulex Web Site and Emulex Support ................................................................................... 7
Emulex Support Page.............................................................................................. 7
Storage and System Supplier-Qualified and Supported HBAs........................... 7
Emulex Driver Downloads and Documentation.................................................. 7
Emulex Knowledgebase .................................................................................... 7
Product Registration .......................................................................................... 7
Product Repair and Return ...................................................................................... 8
Get an RMA for 10 Products or Fewer .............................................................. 8
Check on the Status of an RMA for 10 Products or Fewer................................. 8
Return More than 10 Products or Check RMA Status........................................ 8
Contact Emulex After Hours, Weekends or Holidays......................................... 9
Online Support System...................................................................................... 9
HBAnyware ............................................................................................................................. 10
Introduction............................................................................................................ 10
Starting HBAnyware from the Desktop ............................................................ 10
HBAnyware Window Element Definitions ........................................................ 11
Starting the HBAnyware Security Configurator ................................................ 13
Resetting the HBA ........................................................................................... 15
Determine the HBA Link State - The General Tab ........................................... 15
Enable or Disable Boot Code - Firmware Tab.................................................. 17
Performing Basic Diagnostic Tests .................................................................. 18
Running Advanced Diagnostic Tests ............................................................... 21
Driver-specific Tools .............................................................................................................. 25
Windows-specific Tools.......................................................................................... 25
UNIX-specific Tools ............................................................................................... 26
Unix (Solaris, Linux and HP-UX) ..................................................................... 26
Linux-specific Tools ......................................................................................... 26
The Offline Utilities ................................................................................................................ 27
Introduction............................................................................................................ 27
Prerequisites: ........................................................................................................ 27
Hardware Compatibility.......................................................................................... 27
Installation ............................................................................................................. 27
Using the Offline Utilities ....................................................................................... 28
DosLpCfg (only) .............................................................................................. 28
Running the Offline Utilities from the Command Prompt ................................. 28
Troubleshooting and Maintenance Manual for Emulex HBAs Page iii
Resetting the HBA with DosLpCfg - reset........................................................ 29
Resetting the HBA with WinLpCfg - reset ........................................................ 29
Running the Power-On Self-Test - POSTtest................................................... 29
Viewing HBA Information ....................................................................................... 30
Viewing the Offline Utilities’ Version Information - version ............................... 30
Viewing Vital Product Data - vpd ..................................................................... 30
Viewing the Syntax for Commands - help ........................................................ 30
Viewing Boot Device Information, WWN, LUN and topology - readbootdevice 31
Viewing BootBIOS Versions - listboot .............................................................. 31
Viewing all HBAs in the System - listhba ......................................................... 31
Viewing WWN of all HBAs in the System - listWWN........................................ 32
Viewing PCI I/O Base Addresses of all HBAs in the System - listIOBase ........ 32
Viewing Firmware Program Revisions - listrev ................................................ 33
Viewing Selected Configuration Numbers - readConfig ................................... 33
Firmware and Boot Code Download Commands ................................................... 34
Downloading a File - download ....................................................................... 34
Accessing the Flash Device Directly - directdownload..................................... 34
World Wide Name Commands............................................................................... 35
Writing WWN and Updating NVPARMS - writeWWN....................................... 35
Restoring WWN and Updating NVPARMS - restoreWWN ............................... 36
Restoring NVPARMS - restoreNVWWN .......................................................... 36
Restoring the IEEE address - restoreDefWWN ............................................... 36
Boot Code Commands .......................................................................................... 36
Enabling or Disabling BootBIOS - enable/disable............................................ 37
Selecting a Boot Device - setbootdevice ......................................................... 37
Selecting One or More Alternate Boot Devices - setAlBoot ............................. 37
Configuration Commands ...................................................................................... 38
Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper ......... 38
Updating Configuration Regions - config ......................................................... 38
Running Diagnostic Tests ...................................................................................... 39
Running the External Loopback Test - extloopback ......................................... 39
Running the Internal Loopback Test - intloopback ........................................... 39
Running the PCI Loopback Test - pciloopback ................................................ 39
Using Script Files................................................................................................... 40
Creating Script Files ........................................................................................ 40
Script File Commands ..................................................................................... 40
Creating a logfile ............................................................................................. 42
Error Codes ........................................................................................................... 44
Solaris SFS Driver Console and Log Messages .................................................................. 46
Introduction............................................................................................................ 46
Severity Levels ................................................................................................ 48
Message Log Example .................................................................................... 48
Miscellaneous Events ............................................................................................ 49
Driver Events ......................................................................................................... 49
HBA Initialization Events........................................................................................ 51
Memory Management Events ................................................................................ 52
SLI Events ............................................................................................................. 53
Mailbox Events ...................................................................................................... 55
Node Events .......................................................................................................... 56
Link Events ............................................................................................................ 57
ELS Events............................................................................................................ 58
General I/O Packet Events .................................................................................... 60
FCP Traffic Events................................................................................................. 62
Troubleshooting and Maintenance Manual for Emulex HBAs Page iv

IP Traffic Events .................................................................................................... 62
Solaris SFS Events................................................................................................ 63
IOCTL Events ........................................................................................................ 65
Firmware Download Events ................................................................................... 66
Common Transport Events .................................................................................... 67
The lp6dutil Utility .................................................................................................................. 69
Introduction............................................................................................................ 69
Start lp6dutil .................................................................................................... 69
Use the Menu Bar ........................................................................................... 70
Navigation Tips................................................................................................ 70
Use the Command Line................................................................................... 71
Commands and Syntax Reference Table ....................................................... 72
Reset the HBA....................................................................................................... 73
Perform a Warm Start ............................................................................................ 74
Exit the lp6dutil Utility ............................................................................................ 74
View HBA Information............................................................................................ 75
View Adapter Parameters................................................................................ 75
View DC Bridge Information ............................................................................ 75
View VPD Information ..................................................................................... 76
View PCI Information....................................................................................... 77
View Revision Information ............................................................................... 77
View Service Parameters ................................................................................ 78
View Counter Information ................................................................................ 79
View Link Status Information ........................................................................... 79
View Link Attention Data ................................................................................. 80
View Wakeup Parameters ............................................................................... 81
View Service Level Interface Memory (SLIM) .................................................. 81
View Mailbox ......................................................................................................... 82
View the Registers .......................................................................................... 83
Update Boot Code ................................................................................................. 84
Change the Boot Code State ........................................................................... 84
Load and Update Firmware, Test and Boot Code Files ................................... 85
View and Maintain the Flash Load List ............................................................ 86
View and Maintain Configuration Regions ............................................................. 87
View Configuration Region Information ........................................................... 87
Initialize a Region or Cleaning a Configuration................................................ 88
Set an HBA to Use Soft Jumpers........................................................................... 88
Use Script Files ............................................................................................... 89
View the Log File ................................................................................................... 91
Run Diagnostic Tests ............................................................................................. 92
Select HBAs to Test......................................................................................... 92
Select Tests ..................................................................................................... 93
Configure Tests ............................................................................................... 93
Start Tests ....................................................................................................... 94
Set or Reset Status Word Mask....................................................................... 95
Debug Tasks.......................................................................................................... 96
Dump Memory ................................................................................................. 96
Run Program ................................................................................................... 97
Run Diagnostics .............................................................................................. 97
Try to Recover HBA ........................................................................................ 99
Troubleshooting and Maintenance Manual for Emulex HBAs Page v

Overview
This troubleshooting manual provides information on isolating, identifying and solving common
hardware problems. This manual provides information for the following types of problems:
• Hardware problems (see page 2)
• Link down (see page 2)
• Cannot see drives (see page 3)
• Out-of-date driver (see page 4)
• Out-of-date firmware (see page 5)
Other topics covered in this manual include:
• Light emitting diodes (LEDS) - includes a reference table for the many LED states (See “LEDs”
on page 5)
• How to contact Emulex Technical Support (see page 7)
• The Offline Utilities (see page 27)
• The lp6dutil Utility (see page 69)
Be Informed, Stay Informed

• Read the documentation on the Emulex Web Site. Each host bus adapter (HBA), driver,
firmware and boot code has documentation posted to the Web site. Documentation is also
contained on the CD-ROM disc provided with the HBA.
• Use the Emulex knowledgebase. From the main Emulex Web site, click support, then click
knowledgebase. This manual also provides some knowledgebase solutions that may be helpful
in finding answers to your problem or question.
Note: The Emulex knowledgebase solutions in this manual are current as of the
manual’s release date. Check the Emulex Web site for any solution updates
or new solutions applicable to your problem or question.
Isolating the Problem

• Isolate the problem to hardware, firmware, driver, or non-HBA (for example, zoning):
• Verify that the HBA firmware version is up-to-date per the original equipment manufacturer
(OEM) or storage vendor
• Check for known issues.
• Verify that you have current switch firmware.
• Use good cables.
• Check HBA and switch LEDs.
• If the system stops responding, install the HBA in another server.
• Verify that the current HBA driver is installed.
• Verify that cluster software and other storage and third-party applications are up-to-date.
• Check with disk and tape vendors for known issues.
• Reload the firmware using the Offline Utility ? download. (see page 33).
• Reload the firmware using lp6dutil/nr. (see page 85).
Troubleshooting and Maintenance Manual for Emulex HBAs Page 1

Gathering Information Before Contacting Emulex Technical Support
• Collect detailed event logging. Review error log information for your driver.
• Collect required information for returning an HBA before you call Emulex. See page 8 for a
check list. This will save you time.
Common Problems
Hardware Issues
Any of the following symptoms indicate that you may need to return your HBA to Emulex for repair:
• Host system (server) does not pass power-on self test (POST).
• The server does not boot.
• LEDs on the HBA stop flashing or flash an error code.
• The bus has incorrect power.
• Hardware errors are logged in the event log or message file.
• Onboard parity errors.
• Peripheral Component Interconnect (PCI) parity errors.
• Firmware “traps”.
• A physical Fibre Channel (FC) interface problem looks similar to a bad cable but follows the
HBA.
• A high error count is reported on the HBAnyware Statistics tab.
• CRC errors, frames out of order, bad frames (a bad cable can cause problems of this
type)
• Bad HBA optics
See “Product Repair and Return” on page 8 for information on returning your HBA for repair.
Link Down
Any of these symptoms may indicate the cause of a link down:
• Firmware operation and port activity indicate that the link is down.
LEDs are visible through openings in the HBA’s mounting bracket and indicate the conditions
and results of the POST function. A link-down is indicated when the green LED flashes and the
yellow LED is off (see Table 1 on page 6).
• If the HBA has a power LED, the power LED indicates that power is off.
Some HBA models have a separate green 3.3V power indicator LED (see page 6).
• Topology and link speed are improperly matched for the HBA and the devices connected to it.
When the driver loads, it attempts to bring the link up. If the topology and link speed are properly
matched, the link comes up. If there is a mismatch, the link does not come up. If you make
changes to the topology or link speed parameters, you may need to reboot the system.
• The boot code is improperly loaded, enabled or configured.
If the boot code is loaded, enabled and properly configured, the link comes up before the operat-
ing system and the driver are loaded. If boot code is enabled, the link is reset any time the driver
is loaded. If the boot code is not enabled, the link does not come up. If boot code brings the link
up, the link goes down when the HBA is reset.
• The status of the link is other than operational.
Use HBAnyware to determine the link state. Click on the General tab and look at the Link Status
field. If the status is operational, the link is up. If the status is other than operational, the link is
down (see page 15).
• The cable is not working.
You can use a cable from a known working connection to test. Isolate the problem to the HBA,
the cable or the connected device.
• If you have a loopback connector, the HBA fails the external loopback tests.
If you have isolated the problem to the HBA, run an external loopback tests using HBAnyware
(see page 22), the Offline Utility (see page 38), or lp6dutil (see page 97).
• The HBA optics do not match the cabling.
If the HBA is one type (single mode or multimode) and your cabling is the other type, the link will
not come up.
Can’t See Devices or Drives

Any of the following symptoms indicate why you cannot see drives or other devices:
• Some devices are not powered on.
Some HBA models have a separate green 3.3V power indicator LED (see page 6).
• The LEDs indicate that the link is down.
On an HBA, a link-down is indicated when the green LED flashes and the yellow LED is off (see
Table 1 on page 6).
On a switch, the LED states vary depending on the switch vendor. See the switch vendor’s doc-
umentation.
• The cable is not working.
Make sure you have a good cable. You can test with a cable from a known working connection.
Isolate the problem to the HBA, the cable, or the connected device.
• The driver is improperly installed or loaded.
Verify that a compatible driver is completely installed and loaded. Some devices may require a
specific device driver installed on the host.
• Automap is turned off.
The first time the machine boots with automap off, the devices are not mapped to the operating
system.
• On the FC Port driver, automap is off by default. You can enable it with HBAnyware or
elxcfg. See the driver user manual for more information.
• On the Storport Miniport and SCSIport Miniport drivers, automap is on by default. You can
change it with HBAnyware or the driver-specific lputilnt utility. See the driver user manual for
more information.
• On the driver for Solaris, automap is on by default. You can change it with HBAnyware. See
the driver user manual for more information.
• On the driver for Linux, lpfc_automap is on by default. You can change it with HBAnyware.
See the driver user manual for more information.

• On the driver for HP-UX, automap is on by default and automatically assigns SCSI IDs by
World Wide Port Name (WWPN). Three parameters (scan-down, fc-bind and automap)
control how the Emulex driver maps FC devices. You can change parameters at the
command line. See the driver user manual for more information.
• The targets are not discovered.
Use HBAnyware to determine discovered targets.
• To find the number of discovered targets, click on Discovered Elements in the discov-
ery-tree.
• To view information specific to a target, sort by host name and click on the Target
Attributes tab.
• The switch is configured incorrectly.
The HBA needs to be placed in the proper zone to see the target device.
• The array is configured incorrectly.
Check settings in the Redundant Array of Independent Disks (RAID) system security settings.
Verify that the array knows the HBA’s world wide node name (WWNN).
Out-of-Date Driver Version

Any of these symptoms indicate that you may need to update the driver:
• Target devices appear incorrectly in device manager.
• The Emulex driver operated correctly before cluster services were installed, but now that the
server has rebooted, the cluster will not start or there are connection time-outs.
Verify with the cluster or path management software vendor that you have the latest versions of
software and that you are running Emulex drivers and firmware that are qualified for that soft-
ware.
• Problem with third-party management software.
Verify with the software vendor that you have the latest versions of software and that you are
running Emulex drivers and firmware qualified for that software.
• An operating-system error (blue screen) occurs.
• Tape operation problems.
Emulex Driver Updates

You can download the latest Emulex driver and utilities from the Emulex Web site. Click Support, then
click the link for your operating system.
• The drivers for Windows includes support Windows Server 2003, Windows 2000 Server and
Windows NT (No future versions of drivers for Windows NT are planned.)
• The driver kit download includes the base driver, HBAnyware and a driver-specific utility.
• If you are running Windows Server 2003 or Windows 2000 Server, the driver kit download
includes AutoPilot Installer®, which is a quick way to install (or update) Emulex drivers and
utilities and configure HBAs, drivers and utilities. You can install Windows drivers and
utilities manually without using AutoPilot Installer. To do this, follow the same steps used
before AutoPilot Installer was available.
• The driver for Linux supports kernels for Open Source drivers.
• The driver download includes the base driver, and, if it is not included in the applications kit,
the application helper module install script.

• The applications kit includes HBAnyware, the driver-specific lputil utility and the application
helper module.
• The SMI-S Provider kit for RedHat includes the SMI-S HBA Provider, compliant with the
SMI-S 1.0.2 specification and certified against the SNIA-CTP v1.0.2.23 suite.
• The SMI-S Provider kit for SLES-8 is pre-packaged with OpenPegasus CIMOM v2.3.2, as a
turnkey SMI-S agent for ease of installation and deployment.
• The lpfc driver for Solaris supports several versions of 32-bit and 64-bit operating systems. The
driver kit includes the lpfc base driver, HBAnyware and lputil. Links to the Solaris’ SFS FCA
drivers are provided as well.
• The driver for HP-UX supports PA-RISC and the 64-bit Itanium processor family. The driver kit
download includes the base driver and the lputil utility.
• The driver for NetWare supports several versions of NetWare. The downloads include the base
driver only (no utilities).
• Installation and update procedures and instructions for using HBAnyware and driver-specific
utilities are in the driver user manual. If applicable, instructions for AutoPilot Installer are in the
quick installation manual and the complete user manual.
Out-of-Date Firmware Version

Any of the following symptoms indicate that you may need to update your firmware:
• The FC link fails to come up or stay up.
• Mailbox time-out errors in the operating system event log or the UNIX message file.
• One or more LEDs have stopped flashing.
• The system stops responding.
• The system has lower than expected performance.
Firmware Updates
You can download the latest Emulex firmware from the Emulex Web site. Click the Support to go to the
Support page, then click the link for your HBA model. A page appears with downloads for firmware, boot
code, drivers and utilities. Download the firmware, and then use HBAnyware or a driver-specific utility to
update the firmware to the HBA.
LEDs
Firmware Operation and Port Activity LEDs
Emulex HBAs have a POST test. Each port has a set of green and yellow LEDs (visible through
openings in the HBA's mounting bracket) that indicate the conditions and results of the POST.
• Green = firmware operation
• Yellow = port activity
HBA LEDs also identify possible problems. For more information on LED states, see Table 1 on page 6.
LEDs can help you locate:
• Bad cables.
• Bad transceivers.
• Bad switches or hub ports.

LEDs can help you determine whether:
• The switch or hub is on.
• The driver is loaded.
• The driver reset the HBA.
Common LED States

Although the HBA LED has many possible states, the three most common are:
• Normal, that is, the link is up
• Link-down or HBA waiting
• Heart-beat indication
Power Indicator LEDs

Some HBA models also have a separate green 3.3V power indicator LED.
• HBA models LP9402DC, LP1050, LP1050DC, LP10000 and LP10000 have an LED located on
the upper back corner of the HBA (not at the mounting bracket). If it is on, the HBA has power.
• HBA model LP9002C has an additional LED on the mounting bracket labeled, “Power”. If this
LED is lighted, the cPCI bus slot is supplying 3.3V power to the HBA.
LED Reference
Table 1: LED Reference Table
Yellow LED Green LED State
Off Off Wake-up failure (dead board)
On Off POST failure (dead board)
Slow blink Off Wake-up failure monitor
Fast blink Off POST failure
Flashing Off POST process in progress
Off On Failure while functioning
On On Failure while functioning
4-Gb HBAs:
1 blink On 1-Gb link rate - normal, link up
2 blinks On 2-Gb link rate - normal, link up
3 blinks On 4-Gb link rate - normal, link up
2-Gb HBAs:
Slow blink On 1-Gb link rate - normal, link up
Fast blink On 2-Gb link rate - normal, link up
Off Slow blink Normal - link down or not started
Slow blink Slow blink Off-line for download
Fast blink Slow blink Restricted offline mode (waiting for restart)
Flashing Slow blink Restricted offline mode (test active)

Emulex Web Site and Emulex Support
Emulex Support Page
The Emulex Support page contains links to the following:
• Storage and system supplier-qualified and supported HBAs
• Emulex driver, downloads and documentation
• Emulex knowledgebase
• Product registration
The Emulex Support page is part of the Emulex Web site at www.emulex.com.
Storage and System Supplier-Qualified and Supported HBAs

Most system and storage suppliers market and sell Emulex products under their own respective brands
and qualify Emulex drivers, software and documentation for these products. The Support page provides
qualified drivers, software and documentation as well as support information for suppliers of Emulex
products.
Emulex Driver Downloads and Documentation

The Emulex Support page contains downloads and documentation for several driver types, boot code
and firmware for each Emulex HBA model.
Emulex Knowledgebase
The searchable Emulex knowledgebase is an on-going effort to provide you with answers to questions
regarding all facets of Emulex products. Information is provided for older (legacy) products as well as for
current products. Knowledgebase topics are stored by knowledgebase solution ID (solution number). A
link to the Emulex knowledgebase is available from the Support page.
Search for information using the knowledgebase:
• By a word or phrase:
• Conduct a general search by entering one word (such as “Storport”) in the Keywords
field or by entering multiple words and choosing Any as the match method.
• Conduct a specific search by entering multiple words and choosing All as the match
method.
• By the solution ID:
• Enter a 1-5 digit solution ID in the Solution ID field (you must know the solution ID to
conduct this search).
Product Registration
Use this page to register your product online. You need the following information to register your
product:
• Customer name
• E-mail address
• Fax number
• Company name
• Contact name

• Address (street, city, state and zip code)
• Product model or part number
• Product serial number
• Purchase date
Product Repair and Return

Whether you contact Emulex through the Emulex Web site, by e-mail or by telephone, gather the
following information before you contact Emulex:
• Bill-to and ship-to company and address
• Model number
• Part number - required on all products to be returned
• Serial number - required on all products to be returned
• Purchase date - required for all cLAN products
• Description of failure
Note: Model and serial numbers are located on bar code labels on the product
itself. Record the information from the bar code label and not the packaging.
Get an RMA for 10 Products or Fewer

To return your product to Emulex for repair or replacement, you must obtain authorization using the
RMA request form for up to 10 units. Return products one of these ways:
• RMA form - Use this online Return Material Authorization form to return up to 10 units.
• E-mail service - Send an e-mail message to the Emulex service department.
Check on the Status of an RMA for 10 Products or Fewer

Call the Emulex Support Services Repair Hotline to check on the status of an existing RMA:
In the Americas:
• Telephone:
800-752-9068, select option 2 and then option 3
In Europe:
• Telephone:
(44) 1189-772929
In Asia:
• Telephone (call the Emulex 800 number, Monday through Friday, between 7:00 AM to 4:00 PM
(Pacific Time)
In China, Philippines: 00 + 1+ 800-752-9068, select option 2 and then option 3
In Japan, South Korea: 001 + 1 + 800-752-9068, select option 2 and then option 3
In Taiwan: 002 + 1 + 800-752-9068, select option 2 and then option 3
Return More than 10 Products or Check RMA Status

Phone to check repair status or return more than 10 products.

Contact Emulex After Hours, Weekends or Holidays
Phone if you have after-hours, holiday or weekend issues.
The Americas and in Asia:
• E-mail address:
tech.support@emulex.com
• Telephone:
800-752-9068, option 2.
Europe:
• E-mail address:
tech.support@emulex.com
• Telephone:
(44) 1189-772929
Online Support System

Open new cases and check the status of existing cases by clicking the online support link on the Emulex
Support page. The online support system is available on all non-holiday work days, Monday through
Friday, 7:00 AM to 4:00 PM (Pacific Time). If you have after-hours holiday or weekend issues, telephone
Emulex Technical Support.

HBAnyware
Introduction
The HBAnyware utility runs on Windows, Solaris and Linux systems. HBAnyware incorporates driver-
based technology to enable complete management of Emulex HBAs, including the ability to upgrade
firmware anywhere in a FC or Internet SCSI SAN from a single console.
Starting HBAnyware from the Desktop

After you have installed the HBAnyware server, access the utility from the desktop Start menu.
To start HBAnyware for Windows:
• On the Windows desktop, click Start, then click Programs /HBAnyware. Initial discovery
information for the host appears:
Figure 1: HBAnyware Utility, Discovery Information (Example)
HBAnyware contains five basic elements:

• The menu bar
• The toolbar
• The discovery-tree
• The property tabs
• The status bar
See “HBAnyware Window Element Definitions” on page 11
The element that you select in the discovery-tree determines whether a menu item or toolbar icon is
active. For example, if you select the local host or other system host, the Reset Adapter item on the
Adapter menu becomes unavailable. The Reset Adapter toolbar button becomes unavailable as well.

HBAnyware Window Element Definitions
Figure 2: HBAnyware Utility Window with Element Call Outs
The Menu Bar

The menu bar contains command menus that enable you to perform a variety of tasks such as resetting
HBAs, sorting items in the discovery-tree and exiting HBAnyware. Many of the menu bar commands are
also available from the toolbar.
The Toolbar
The toolbar contains buttons that enable you to refresh the discovery-tree, reset the selected HBA and
sort the discovery-tree. The toolbar is visible by default. Many of the toolbar functions are also available
from the menu bar.
Use the Toolbar item in the View menu to hide/view the toolbar. If you check the menu item, the toolbar
is visible.
The Toolbar Buttons
Click Rediscover to refresh the discovery-tree display.
Click Reset to reset the selected HBA.
Sort Toolbar Buttons

You can sort discovered HBAs by host name, fabric addresses or local HBAs. By default, HBAs are
sorted by host name, with local HBAs appearing first.
You can also show only local or remote HBAs. See page 51 for details on sorting buttons.

Sort by host name (default)
Sort by fabric address
Local HBAs only
Help
Discovery-Tree
The discovery-tree (left pane) shows icons that represent discovered network SAN elements including:
• Local host name
• System host names
• All HBAs active on each host
• Targets and LUNs, when present, are also displayed.
Figure 3: HBAnyware Utility, Discovery-Tree
Discovery-Tree Icons
Discovery-tree icons represent the following:
The Local host icon.

The Other hosts icon for additional hosts connected to the system.
A green HBA icon with black descriptive text is the Online HBA icon.
A gray HBA icon with red descriptive text is the Offline HBA icon. It means an HBA that is offline
or otherwise temporarily inaccessible. Several situations could cause an offline or inaccessible HBA:
• The HBA on a local host is not connected to the network, but is still available for local access.
• The HBA on a local host has malfunctioned and is inaccessible to the local host as well as the
network.
• The HBA on a local host is busy performing a local download and therefore temporarily
inaccessible to the local host as well as the network.
The Target icon represents connections to individual storage devices.
The LUN icon represents connections to individual LUNs.
Property Tabs
The property tabs display configuration, statistical and status information for network elements. The set
of available tabs is context-sensitive, depending on the type of network element or HBA currently
selected in the discovery-tree.
Status Bar
As you navigate through the menu bar or the toolbar, help messages appear on the status bar near the
bottom of the HBAnyware window.
The status bar is shown by default. Uncheck Status Bar in the View menu to hide the status bar.
Management Mode
The management mode determines whether you can manage HBAs on the host. If a host has restricted
access, you cannot manage HBAs from that host. See the driver user manual for more information on
setting and changing the management mode.
Starting the HBAnyware Security Configurator

You can use the HBAnyware security package to control which HBAnyware systems can remotely
access and manage HBAs on other systems in a FC network. HBAnyware security is systems-based,
not user-based. Anyone with access to a system that has been granted HBAnyware client access to
remote HBAs can manage those HBAs. Any unsecured system is still remotely accessible by the
HBAnyware client software (the HBAnyware utility). See the driver user manual for more information on
the HBAnyware Security Configurator.

Note: Before you start the Security Configurator, you must make sure that all of the systems
that are part of, or will be part of, the security configuration are online on the FC network
so that they receive updates or changes made to the security configuration.
Any system already part of the security installation might not run with the proper security
attributes if updates to the security configuration are made while it is offline. Any system
that is part of the security installation and that is offline when the Security Configurator
starts will not be available for security configuration changes even if it is brought online
while the Security Configurator is running.
To start the HBAnyware Security Configurator for Windows Server 2003 or Windows 2000 Server:
1. On the desktop, click Start, then select Programs, then HBAnyware Security Configurator.
The HBAnyware Security Configurator Discovery window appears:
Figure 4: HBAnyware Security Configurator Discovery Window
2. After discovery is completed, the HBAnyware Security Configurator appears.
Figure 5: HBAnyware Security Configurator, Access Control Group Tab

Resetting the HBA
To reset the HBA:
1. Start HBAnyware.
2. In the directory-tree, click the HBA you want to reset.
3. Do one of the following:
• From the menu bar, click Adapter, and then Reset Adapter.
• Click the button.

The following warning screen appears:
Figure 6: HBAnyware Utility, Reset Warning Screen

4. Click Yes on the warning screen to proceed with the reset.
The reset may require several seconds to complete. While the HBA resets, “Reset in progress” is
displayed in the status bar. “Ready” is displayed in the status bar when reset has finished.
Determine the HBA Link State - The General Tab

The General tab contains general HBA information. The Status field indicates the current HBA link
state. In the discovery-tree, a green HBA icon with black descriptive text represents an online HBA.
“Operational” appears in the Status field on the General tab to indicate an HBA that is connected to the
network and operating normally. Figure 7 is an example of the HBA in an operational state.
Figure 7: HBAnyware Utility, General Tab Example

Adapter Summary Field Definitions
Model - the Emulex HBA model number.
Port WWN - the WWPN of the HBA.
Node WWN - the WWNN of the selected HBA.
Fabric Name or Host Name - the Fabric Name field is displayed if you select Sort by Host Name. The
fabric name is a 64-bit worldwide unique identifier assigned to the fabric. The Host Name field is
displayed if you selected Sort by Fabric ID. The host name is the name of the host containing the HBA.
Driver Version - the version of the driver installed on the HBA.
Firmware Version - the version of Emulex firmware currently active on the HBA.
Driver Name - the executable file image name for the driver as it appears in the Emulex driver download
package.
Boot BIOS - indicates whether the HBA’s boot code is enabled or disabled.
Adapter Status Field Definitions

• State - The current operation state of the HBA: Up or Down.
• Link Status - the current link status between the HBA and the fabric. There are several possible
states:
• Operational indicates that the HBA is connected to the network and operating normally.
• All other states indicate the HBA is not connected to the network. Gray HBA icons with red
descriptive text indicate an offline HBA. These offline states are:
• User offline - the HBA is down or not connected to the network.
• Bypassed - the HBA is in FC discovery mode.
• Diagnostic Mode - the HBA is controlled by a diagnostic program.
• Link Down - there is no access to the network.
• Port Error - the HBA is in an unknown state; try resetting it.
• Loopback - an FC-1 mode in which information passed to the FC-1 transmitter is
shunted directly to the FC-1 receiver. In loopback mode, the FC interface loopback sig-
nal overrides any external signal detected by the receiver.
• Unknown - the HBA is offline for an unknown reason.
• Link Speed - the link speed of the HBA in gigabits per second.

Enable or Disable Boot Code - Firmware Tab
Use the Firmware tab to view current firmware versions and update firmware and boot code on remote
and local HBAs.
Figure 8: HBAnyware Utility, Firmware Tab
Firmware Area Field Definitions

• Firmware Version - the Emulex firmware version number installed on the HBA.
• Operational Firmware Name - if visible, the name of the operational firmware.
• Initial firmware - the firmware version stub responsible for installing the Service Level Interface
(SLI) code into its proper slot.
• SLI-1 Firmware Name - the name of the SLI-1 firmware overlay.
• Kernel Version - the version of the firmware responsible for starting the driver
Firmware Buttons
• Update Firmware - click to open HBAnyware Firmware Download dialog box and update
firmware. Using the HBAnyware Firmware Download dialog box, browse to the file you want to
download and download the file.
• Enable/Disable - click to enable or disable the boot code.

Performing Basic Diagnostic Tests
Use the Diagnostics tab to do the following:
• Run these tests on Emulex HBAs installed in the system:
• PCI Loopback (see page 22)
• Internal Loopback (see page 22)
• External Loopback (see page 22)
• POST (see page 19)
• Echo Test (see page 23)
• Quick Test (see page 18)
• Perform a diagnostic dump (see page 20).
• View PCI registers and wakeup parameter (see page 21).
• Control HBA beaconing (see page 20).
Figure 9: HBAnyware Utility, Diagnostics Tab
All functions are supported locally and remotely, except for the dump feature which is only supported
locally.
Running a Quick Test

The Quick Test consists of 50 PCI Loopback test cycles and 50 Internal Loopback test cycles.
To run a quick test:
1. Start HBAnyware.
2. From the discovery-tree, select the HBA on which you want to run the Quick Test.

3. Select the Diagnostics tab and click Quick Test. The following message appears:
Figure 10: HBAnyware Utility, Quick Test Message

4. Click OK to run the test. The Quick Diagnostics Test message shows the PCI Loopback and
Internal Loopback test results.
Figure 11: HBAnyware Utility, Quick Diagnostics Test Results
Running POST
A POST is a firmware test normally performed on an HBA after a reset or restart. A POST does not
require any configuration to run.
To run a POST:
1. Start HBAnyware.
2. From the discovery-tree, select the HBA on which you want to run a POST.
3. Select the Diagnostics tab and click Power-on Self Test (POST). A warning dialog box appears
(see Figure 11).
4. Click OK. A POST Test window shows POST test information.
Figure 12: HBAnyware Utility, POST Test Window

Using Beaconing
The beaconing feature enables you to force a specific HBA’s LEDs to blink in a particular sequence. The
blinking pattern acts as a beacon, making it easier to locate a specific HBA among racks of other HBAs.
When you enable beaconing, the two LEDs blink rapidly in unison for 24 seconds, after which the LEDs
report the HBA health status for 8 seconds. When the 8 seconds are up, the HBA returns to beaconing
mode. This cycle repeats indefinitely until you disable this feature or you reset the HBA.
Note: The beaconing buttons are disabled if the selected HBA does not support
beaconing.
To enable/disable beaconing:
1. Start HBAnyware.
2. From the discovery-tree, select the HBA whose LEDs you want to set.
3. Select the Diagnostics tab and click Beacon On or Beacon Off.
Starting a Diagnostic Dump
Note: The Diagnostic Dump feature is only supported for local HBAs. If a remote
HBA is selected from the tree-view, Initiate Diagnostic Dump is disabled.
To start a diagnostic dump:

1. Start HBAnyware.
2. From the discovery-tree, select a local HBA whose diagnostic information you want to dump.
3. Select the Diagnostics tab and click Diagnostic Dumps. The Diagnostic Dump dialog box
appears. You can specify how many files you want to save using the Files Retained counter.
Click Delete Existing Dump Files if you want to remove existing dump files from your system.
Figure 13: HBAnyware Utility, Diagnostic Dump Dialog Box

4. Click Start Dump.

Displaying PCI Registers and Wakeup Information
A PCI Register dump for the selected HBA appears in the lower left panel of the Diagnostics tab.
Wakeup information for the selected HBA appears in the lower right panel of the Diagnostics tab. The
information is read-only and is depicted below:
Figure 14: HBAnyware Utility, PCI Registers and Wakeup Parameters Area of the Diagnostics Tab
Running Advanced Diagnostic Tests

The Advanced Diagnostics feature gives you greater control than the Quick Test over the type of
diagnostics tests that run. Through Advanced Diagnostics, you can specify which tests to run, the
number of cycles to run, and what to do in the event of a test failure.
To run advanced diagnostics tests:
1. Start HBAnyware.
2. Click the Diagnostics tab, then click Advanced Diagnostics Test on to view the Advanced
Diagnostics dialog box.
You can run four types of tests:
• PCI Loopback
• Internal Loopback
• External Loopback
• ECHO
Note: You cannot run the External Loopback test and the ECHO test concurrently. If you
select External Loopback the ECHO test section is disabled and vice versa.

All test results, plus the status of running tests, are time stamped and appear in the log at bottom of the
dialog box.
Figure 15: HBAnyware Utility, Advanced Diagnostics
Running Loopback Tests

To run a loopback test, use the Loopback Test section of the Advanced Diagnostics dialog box.
You can run the following loopback test combinations using the appropriate boxes:
• PCI Loopback Test - A firmware-controlled diagnostic test in which a random data pattern is
routed through the PCI bus without being sent to an HBA link port. The returned data is
subsequently validated for integrity.
• Internal Loopback Test - A diagnostic test in which a random data pattern is sent down to an
HBA link port, then is immediately returned without actually going out on the port. The returned
data is subsequently validated for integrity.
• External Loopback Test - A diagnostic test in which a random data pattern is sent down to an
HBA link port. The data goes out the port and immediately returns by way of a loopback
connector. The returned data is subsequently validated for integrity.
Note: You cannot run the External Loopback test and ECHO test concurrently. If you select
External Loopback the ECHO test section is disabled and vice versa.
You can specify the number of test cycles by clicking one of the cycle counts values in the Test Cycles
section of the dialog box or enter a custom cycle count if you wish. The Test Status section displays
how many cycles of each test ran. The Error Action section of the dialog box enables you to define
what should be done in the event of a test failure.

There are two error action options:
• Stop Test - The error will be logged and the test aborted. No further tests will run.
• Ignore - Log the error and proceed with the next test cycle.
To run loopback tests:
1. Start HBAnyware.
2. From the discovery-tree, select the HBA on which you want to run the Loopback Test.
3. Select the Diagnostics tab and click Advanced Diagnostics Tests. From the Loopback Test
section of the dialog box, choose the type of Loopback test you want to run and define the
loopback test parameters.
Note: You must insert a loopback plug in the selected HBA before running an
External Loopback test.
4. Click Start. The following warning appears:
Figure 16: HBAnyware Utility, Advanced Diagnostic Tests Warning

5. Click OK. If you choose to run an External Loopback test the following window appears:
Figure 17: HBAnyware Utility, Advanced Diagnostic Tests Warning for External Loopback
6. Click OK. The progress bar indicates that the test is running.
Periodic test feedback, consisting of the current loopback test/cycle plus the completion status
of each type of test, is displayed in the Test Log section of the dialog box. Click Clear to erase
the contents of the log display or click Save to File to save the log file.
Running ECHO Test

Run echo tests using the ECHO Test section of the Diagnostics tab. The end-to-end test enables you
send an ECHO command/response sequence between an HBA port and a target port.
Note: Not all remote devices respond to an echo command.
You cannot run the ECHO test and the External Loopback test concurrently. If you
select the ECHO Test the External Loopback test is disabled.
To run end-to-end echo tests:

1. Start HBAnyware.
2. From the discovery-tree, select the HBA from which you want to initiate the ECHO Test.
3. Select the Diagnostics tab. Click Advanced Diagnostics Test.

4. Do one of the following:
• Check Echo Test. Enter the WWPN for the target.
• Click Select From List if you do not know the actual WWPN of the test target. The
Select Echo Test Target dialog box appears. Select the port you want to test from the
tree-view and click Select.
All relevant information for the selected port is automatically added to the Target Identifier sec-
tion of the Diagnostics dialog box.
Figure 18: HBAnyware Utility, Select Echo Test Target Window

5. Click Start. The following warning window appears:
Figure 19: HBAnyware Utility, Advanced Diagnostic Tests Warning

6. Click OK. A result screen appears and the test results appear in the Test Log. Click Clear to
erase the contents of the log display or click Save to File to save the log file.
Saving the Log File

You can save the test log to a log file for later viewing or printing. When new data is written to a saved
file, the data is appended to the end of the file. Each entry has a two-line header that contains the
identifier of the HBA being tested and the date and time of the test. Over time, the data accumulates to
forms a chronological history of the diagnostics performed on the HBA.
After writing an entry into the log, you are prompted to clear the display.
The default name of the saved file is DiagTestLog.log and by default is located in:
/usr/sbin/hbanyware/Dump

An example of a saved log file appears below:
Figure 20: Diag Testlog Window
To save the log file:

1. After running a test from the Diagnostic Test Setup dialog box, Click Save to File. The Select
Diagnostic Log file Name dialog box appears. The default name of a saved file is
DiagTestLog.log.
2. Browse to the desired directory, change the log file name if you want and click Save.
Driver-specific Tools
In addition to HBAnyware, Emulex provides Windows-specific and UNIX-specific utilities.
Windows-specific Tools
• The lputilnt utility is provided for the SCSIport Miniport and the Storport Miniport drivers. Use
lputilnt to identify problems on the local HBA only. See the driver user manual for more
information on lputilnt.
• The elxcfg utility is provided for the FC Port driver. Use elxcfg to identify problems on the local
HBA only. See the driver user manual for more information on elxcfg.
• Event logs (see “Creating a logfile” on page 42).
• Error codes (see “Error Codes” on page 44).
• Registry dump (see the driver user manual for parameter descriptions).
• The FC Information Tool (FCINFO, or FCIT) is available directly from Microsoft and runs only
on x86 platforms. FCINFO is used to discover SAN resources and configuration information on
the FC SAN. To download this tool, access the Microsoft Web site and search for “fcinfo” on the
Downloads page. This tool provides local information such as:
• List of HBA WWNs.
• Versions of installed firmware/driver.
• List of discovered targets.
• Statistics about installed HBAs.
The following Emulex drivers are compatible with FCINFO:
• Storport Miniport driver, version 1.03 (or later)
• SCSIport Miniport driver, version 5.10a10 (or later)

UNIX-specific Tools
Unix (Solaris, Linux and HP-UX)

• The lputil utility is a command-line interface. Use lputil to identify problems on the local HBA
only. See the driver user manual for more information on lputil.
• Message file logs (see).
• lpfc.conf, sd.conf (disk), st.conf (tape) files. See the driver user manual for more information.
Linux-specific Tools
Use Linux-specific tools to do the following:
• Boot from SAN with Linux and Emulex HBAs.
• Access the No-Reboot Dynamic Target/LUN Discovery Tool.
• Access the System Grab Diagnostic Tool.
• Re-insert an offline device (lun_change_state.sh).
• Adjust time-out for array behavior (set_target_timeout.sh).
See the driver user manual for more information on Linux-specific tools. Also, see the Linux tools, which
are available from the Linux page in the Support section of the Emulex Web site.

The Offline Utilities
Introduction
The offline utilities are Emulex programs to configure Emulex HBAs before you install or boot a server
operating system.
The offline utilities include:
• DosLpCfg - for use with MS-DOS, FreeDOS, IBM PC DOS and DR DOS operating systems.
• WinLpCfg - for use with 32-bit and 64-bit versions of the Microsoft WinPE operating system.
(Although not the intended use, you can use WinLpCfg with Windows Server 2003)
In all cases the commands are given with the prefix OS. When you enter any command, you must
replace the OS with either:
• Win for WinLpCfg commands for use on Windows machines
• Dos for DosLpCfg commands. for use on DOS machines
You can use the offline utilities to do the following:
• View information on an Emulex HBA
• Reset the HBA
• Download firmware and boot code files
• Select a boot device
• Read and update World Wide Names (WWNs)
• Enable BootBIOS
• Update configuration regions
• Set the HBA to use soft jumpers
• Run diagnostic tests
• Read and process script files
Prerequisites:
• The offline utilities on a bootable media with supported versions of DOS or WinPE.
• The Emulex Storport Miniport driver must be installed to use WinLpCfg.
Hardware Compatibility
The offline utilities support:
• All current Emulex HBAs.
• Up to 12 HBAs on one system with DosLpCfg.
• All HBAs discovered by the Storport Miniport driver with WinLpCfg.
Installation
• WinLpCfg is distributed in a single zip file. You must unzip that file and use the WinLpCfg
executable file that is appropriate for your system. (Instructions for creating bootable WinPE
media is beyond the scope of this document.)

• Under the WinLpCfg directory are two sub-directories:
• x86 - a 32-bit WinLpCfg for use with the 32-bit version of WinPE.
• x64 - a 64-bit WinLpCfg for use with the x64 version of WinPE.
• WinLpCfg depends on the Emulex Storport Miniport driver. You can use the Emulex Storport
Miniport driver that is distributed with WinPE or install a newer version.
• DosLpCfg is a 16-bit executable, distributed in a single zip file. You must unzip that file and copy
the executable file to an appropriate folder.
Using the Offline Utilities

• Offline utilities’ commands are not case-sensitive. You can enter them in upper or lower case.
• Offline utilities’ commands require both:
• one space between the command name and the first argument.
• one space between additional arguments.
Do not put a space before or after the equal sign within an argument.
• World Wide Name (WWN) values are reported and specified with two 8-byte hexadecimal words
— WWN word 0 (w0) and WWN word 1 (w1). The w0 and w1 values are concatenated to make
the full WWN.
DosLpCfg (only)
• The DosLpCfg offline utility detects the number of HBAs it can support if your system has limited
memory (530 KB or less). If your system has limited memory, a message appears, specifying an
additional argument you must add to each command, such as:
"Insufficient Memory to support 8 adapters. Use max=7 at the end of EACH command."
As directed in the message, you must add max=7 to the end of each command. In this example,
if your system has eight HBAs and you enter max=7 at the end of a command, only the first
seven HBAs are seen by the offline utilities. If your system has more than 530 KB of memory,
the offline utilities can support up to twelve HBAs and no message appears.
Running the Offline Utilities from the Command Prompt

Note: You cannot start the DosLpCfg offline utilities at the Command Prompt in Windows.
Note: You must start the WinLpCfg offline utilities at the Command Prompt.
1. Boot the system with a supported version of DOS or WinPE.

2. You can start an offline utility with a valid command or a valid script file name.
• To start an offline utility, move to the directory where the executable resides and type:
OSlpcfg <valid command> (be sure to replace the OS with win
or dos as appropriate)
• Example of starting DosLpCfg with a reset command:
DosLpCfg reset n=2 s=1
• Example of starting the WinLpCfg with a reset command:
WinLpCfg reset n=2

• To start an offline utility with a script file name, from the directory where the OSLpCfg.exe file
resides, type:
OSlpcfg @<script file name>
• Example of starting an offline utility with script1.txt in the c:\test directory:
OSlpcfg @C:\test\script1.txt
Note: To redirect screen output to a file, add >filename at the end of each command.
Example:
OSLpCfg listboot n=1 >result.out
Note: For more information on script files, See “Creating Script Files” on page 40 and
“Script File Commands” on page 40.
Resetting the HBA with DosLpCfg - reset

This command resets one specific HBA or all HBAs in the system. In DOSLpCfg (only) there is an s
argument that determines whether POST is run when the HBA(s) restart. The s argument is not optional
for this command.
Enter:
• s=1 to skip POST
or
• s=0 to run POST.
To reset one or more HBAs on a DOS system, type:
DosLpCfg reset n=<all/adapter number> s=<skip POST argument>
• The following example resets all HBAs in the system and runs POST when the HBAs restart.
DosLpCfg reset n=all s=0
Resetting the HBA with WinLpCfg - reset
This command resets one specific HBA or all HBAs in the system. In WinLpCfg (only) there is NO s
argument.
To reset one or more HBAs on a Windows system, type:
WinLpCfg reset n=<all/adapter number>
• The following example resets all HBAs in the system and runs POST when the HBAs restart.
WinLpCfg reset n=all
Running the Power-On Self-Test - POSTtest
This command runs the power-on self-test (POST) on the selected HBA.
• To run the HBA POST test, type:
OSLpCfg POSTtest n=<all/adapter number>
The following example runs the POST test on HBA #1.
OSLpCfg POSTtest n=1

Viewing HBA Information
Viewing the Offline Utilities’ Version Information - version

This command displays the offline utility’s version information.
• To view this information, type:
OSLpCfg version
• Sample response:
OSLpCfg version 1.0a8 released on May 26, 2007.
Viewing Vital Product Data - vpd
This command displays the vital product data (VPD) of the HBA specified by its number.
• To display VPD, type:
OSLpCfg vpd n=<adapter number>
• The following example displays VPD for HBA #2:
OSLpCfg vpd n=2
Model: LP250048-900
Serial Number: 0003
Port Number:
Model Description:
EMULEX LIGHTPULSE LP250048-900 2 GIGABIT PCI FC ADAPTER
Program Type:
T2: 0xB2, 0xB8, T3: 0xB1, 0xB2, 0xB3, 0xB5, 0xB6, 0xB7, T6: 0xB2, T7: 0xB2
Viewing the Syntax for Commands - help

• To view all available commands, type:
OSLpCfg help
or:
OSLpCfg ?
• To view syntax for a specific command, type:
OSLpCfg help <command>
or
OSLpCfg ? <command>
For example, either,
OSLpCfg help download
or
OSLpCfg ? download
returns a response similar to the following:
download <n=adapter> <i=imagepath>

or
download <a=adaptertype> <i=imagepath>

Viewing Boot Device Information, WWN, LUN and topology - readbootdevice
This command shows the WWN, the LUN (in decimal format) and the topology of the currently selected
boot device.
• To show this information, type:
OSLpCfg readbootdevice n=<adapter number>
• The following example reads WWN and LUN for HBA #1:
OSLpCfg readbootdevice n=1
Boot Device WWN: 104AC6D2 C920A4D6
Boot Device LUN: 43
Topology Point-to-Point
Viewing BootBIOS Versions - listboot

This command lists all the BootBIOS versions, with indices (base 1) and code names, that are loaded in
the flash of the HBA, specified by its number. If the selected HBA does not have any BootBIOS loaded,
error code 39 is returned.
Note: The DOS and Windows versions of this command return slightly different information.
• To list BootBIOS versions, type:

OSLpCfg listboot n=<adapter number>
• The following example lists BootBIOS versions that are loaded on HBA #3:
OSLpCfg listboot n=3
• Sample Response from DosLpCfg:
boot 1 (enabled): RB1.60A7

boot 2 (disabled): RB1.52A1
• Sample Response from WinLpCfg:
bootBIOS 1 (enabled): RB1.60A7

bootBIOS 2 (disabled): RB1.52A1
Viewing all HBAs in the System - listhba

This command lists all installed HBAs in the system. Information includes the HBA number (base 1), the
IEEE address assigned by the manufacturer, the functional firmware, the HBA type and possible mailbox
errors.
• To list all HBAs in the system, type:
OSLpCfg listhba

adapter 1: 10000000 C9420964 Functional FW: TS2.12X2 LP10000DC
adapter 2: 10000000 C9420964 Functional FW: TS2.12X2 LP10000DC
adapter 3: WWN err. !!! ReadRev Error !!! LP11000
adapter 4: 10000000 C96C146D Functional FW: WS2.70A5 LPe1150-F4
adapter 5: 10000000 C94B0718 Functional FW: ZS2.72A2 LPe11002-F4

adapter 6: 10000000 C94B0719 Functional FW: ZS2.72A2 LPe11002-F4
Viewing WWN of all HBAs in the System - listWWN

This command lists all HBAs installed in the system and shows the factory-assigned WWN, the Non-
volatile WWPN and the WWNN used to identify an HBA in the SAN.
The factory-assigned WWN is listed in two parts. It is an Institute of Electrical and Electronic Engineers
(IEEE) address that cannot be changed in the field. To get the WWN, concatenate 10000000 and the
number that follows in the response.
You can modify the non-volatile WWPN and WWNN using either the writeWWN command or the
scriptWWPN and scriptWWNN commands. For more information on the writeWWN command, see
“Writing WWN and Updating NVPARMS - writeWWN” on page 35.
If the system does not have any Emulex HBAs installed, it returns error code 45.
• To show the WWN information, type:
OSLpCfg listWWN
adapter 1: LPe11000 Factory IEEE 10000000 C920DAB8 Volatile WWPN: 5AB0E2F4 B620DAB8,
WWNN: 46A0B4DA E2F4C8A0
where the Factory IEEE is the original IEEE address from the manufacturer, read from Configu-
ration Region 16 (or 32). The Volatile or Non-volatile WWPN and WWNN are the port name and
node name. They are written with:
• the writeWWNN command
or with
• the scriptWWPN and scriptWWNN commands
or with
• the scriptVWWPN and scriptVWWNN commands
Viewing PCI I/O Base Addresses of all HBAs in the System - listIOBase
This command lists the PCI I/O base addresses of all HBAs in the system. If the system does not have
any Emulex HBAs installed, it returns error code 45.
• To list PCI I/O base addresses, type:
OSLpCfg listIoBase

adapter 1: 00001800
adapter 2: 00002000
adapter 3: 00001000
adapter 4: 00001400
adapter 5: 00001600
adapter 6: 00001300
Viewing Firmware Program Revisions - listrev

This command shows the firmware version(s) in the HBA’s flash memory, specified by their numbers.
• To show revisions, type:
OSLpCfg listrev n=<adapter number>
• The following example lists information for HBA #3:
OSLpCfg listrev n=3
Chipset Rev:
BIU: 1001206D
SM FW: 078321B2
FW Rev:
Current FW: SLI-2 Overlay
Kernel Rev: FFB01416
Kernel LP250048-9001.30a4
Init FW: LP250048-900Init Load 1.91a0 (ES1.91A0)
SLI-2: LP250048-900Overlay 1.91a0 (E1M1.91A0)
SLI-3: LP250048-900Overlay 1.91a0 (E2M1.91A0
FC-PH Version Supported:
Highest FC-PH Version Supported = 4.3
Lowest FC-PH Version Supported = 4.3
Feature Availability = 0000 0000
Viewing Selected Configuration Numbers - readConfig

This command displays the contents of the selected configuration number up to the initialized length or
the specified byte count (if the initialized length is less than the specified byte count). Valid region
numbers are 0 to 32. You must initialize the configuration region first by, for example, writing data to it.
• To read a configuration, type:
OSLpCfg readConfig n=<adapter number> r=<region number> l=<byte
count>
• The following example reads the configuration for HBA #1, region 0, byte count 20:
readConfig n=1 r=0 l=20

• Sample Response:
00000000: 10000000 c920a4b1e6
00000008: 20000000 c920a4b1e8
00000010: 00000000
Firmware and Boot Code Download Commands
Downloading a File - download

This command downloads a firmware or boot-code file to either:
• all HBAs of the same type
or,
• to a specific HBA.
To download a firmware image file to all HBAs of the same specified name, type:
OSLpCfg download a=<adapter name> i=<firmware image filename>
Note: The adapter name is the name that appears when you run the listHBA
command. For more information on the listHBA command, see “Viewing all HBAs in
the System - listhba” on page 31.
• The following example downloads the hd100a4.all firmware file to all LPe11000 HBAs:
OSLpCfg download a=lpe11000 i=c:\image\zd272a2.all
• To download a firmware image file to an HBA specified by its number, type:
OSLpCfg download n=<adapter number> i=<firmware image filename>
• The following example downloads the Zb200a1.prg (x86) BootBIOS file to HBA # 6; in this
example, the x86 BootBIOS file is for an LPe11000 HBA:
OSLpCfg download n=6 i=zb200a1.prg.
Accessing the Flash Device Directly - directdownload
Note: directdownload is only supported in DosLpCfg; not in WinLpCfg.
This command directly accesses the flash device on the HBA without using the HBA firmware. This
feature is useful in downloading a read-only memory (ROM) file image if the firmware has been
corrupted. You can use this feature on the following Emulex HBAs:
• LPe12000, LPe12002 and LPe1250
• LPe11000, LPe11002, LPe1150 and LPe1104
• LP11002, LP11000 and LP1150
• LP10000ExDC and LP1050Ex
• LP10000DC and LP10000
• LP1005DC-CM2
• LP1050 and LP1050DC
Note: You cannot use this command in a script file.

• To access the flash device on the HBA directly, type:
OSLpCfg directdownload a=<adapter name/default> i=<firmware image
filename>
Note: The adapter name is the name that appears when you run the listHBA
command. For more information on the listHBA command, see “Viewing all HBAs in
the System - listhba” on page 31.
• The following example accesses the flash device on an LP1050 HBA:

OSLpCfg directdownload a=lp1050 i=C:\image\mfp191a5.rom
• The following example accesses the flash device if the offline utilities cannot detect the HBA
type and there is only one single-channel HBA or one dual-channel HBA in the system:
OSLpCfg directdownload a=default i=C:\image\tdu191a5.rom
Note: You can use the a=default option only if there is only one single-channel
HBA or one dual-channel HBA in the system.
World Wide Name Commands
Writing WWN and Updating NVPARMS - writeWWN

This command allows you to enter word 0 and word 1 of the WWPN or WWNN from the keyboard or a
barcode scanner to update a specified HBA’s non-volatile parameters (NVPARMS) with a new WWPN or
WWNN. The new WWPN and WWNN are used when the HBA is discovered. The HBA stores the
original WWPN and WWNN in another region of the memory so it can be used to identify the HBA as it
was manufactured. The writeWWN command is not valid in a script file; use the scriptWWPN and
scriptWWNN commands instead.
Note: You cannot use this command in a script file.
Caution: Use the writeWWN command with caution. If you use the same WWPN or
WWNN on more than one HBA in a fabric, unpredictable results may occur.
• To modify the WWPN and WWNN, type:

OSLpCfg writeWWN n=<all/adapter number>
• The offline utilities prompts you to enter a new WWPN or WWNN. The following example writes
the WWPN and WWNN for HBA #1.
OSLpCfg writeWWN n=1
Reading IEEE Information and Saving It to a File - saveWWN
Note: "If the scriptVWWNN and scriptVWWPN commands were used previously, then
those WWNN and WWPN values are still in use. You can change them with the
restoreNVWWN command.
This command reads the original words 0 and 1 of the IEEE address, installed by manufacturing, from
configuration regions 16 (or 32) of the HBA (specified by its number) and saves the configuration region
information in the selected WWN file.
• To save the WWN, type:
OSLpCfg saveWWN n=<adapter number> c=<wwn filename>
• The following example reads the configuration region information on HBA #4 and saves it to the
contents of the ctwwn.sav file:
OSLpCfg saveWWN n=4 c=ctwwn.sav

Restoring WWN and Updating NVPARMS - restoreWWN
This command restores words 0 and 1 of the IEEE address from a specified file and uses them to update
the NVPARMS port name with this IEEE address.
• To restore the WWN, type:
OSLpCfg restoreWWN n=<adapter number> c=<wwn filename>
• The following example reads the WWN on HBA #4 and updates the NVPARMS with the
ctwwn.sav file.
OSLpCfg restoreWWN n=4 c=ctwwn.sav
Restoring NVPARMS - restoreNVWWN
This command allows you to restore the Non-Volatile WWPN and WWNN to the HBA, replacing any
previously-selected Volatile WWPN and WWNN data, without powering off the HBA.
If the HBA does not have firmware that supports the Volatile WWN, the error message, "Write Volatile
Parms Error. Reported Error of 48" appears. If this occurs, install firmware that supports the Volatile
WWN.
• To restore the NVWWN, type:
OSLpCfg restoreNVWWN n=<adapter number>
• The following example restors the NVWWN on HBA #2.
OSLpCfg restoreNVWWN n=2
Restoring the IEEE address - restoreDefWWN
This command reads the IEEE address (assigned by the manufacturer) from configuration region 16 (or
32) and writes it to the configuration region 0 to be used as the non-volatile WWPN.
• To restore the DefWWN, type:
OSLpCfg restoreDefWWN n=<adapter number>
• The following example restores the DefWWN on HBA #2.
OSLpCfg restoreDefWWN n=2
Boot Code Commands

You must enable the boot code before you can issue boot code commands.If necessary, use the
enableboot command to enable BootBIOS. (See “Configure the system BIOS so the HBA boot device is
the highest in the boot order.” on page 36 for more information.)
To set the boot device with the offline utilities, run the following commands in this order:
1. Use the listboot command to verify that the BootBIOS is present. (See “Viewing BootBIOS
Versions - listboot” on page 31 for more information.)
2. Use the setbootdevice command to set the boot device. (See “Selecting a Boot Device -
setbootdevice” on page 37 for more information.)
• Example:
OSLpCfg listboot n=1
• Sample return:
boot 1 (enabled): RB1.70A3
boot 2 (disabled): RB1.50A8
Configure the system BIOS so the HBA boot device is the highest in the boot order.

Enabling or Disabling BootBIOS - enable/disable
This command enables or disables the BootBIOS (selected by its index) for the specified HBA number.
Index i is one of the indices (base 1) shown when you run the listboot command.
• To enable BootBIOS, type:
OSLpCfg enableboot n=<adapter number> i=<index>
• The following example enables BootBIOS on HBA #6:
OSLpCfg enableboot n=6 i=1
• To disable BootBIOS, type:
OSLpCfg disableboot n=<adapter number>
• The following example disables BootBIOS on HBA #6:
OSLpCfg disableboot n=6
Selecting a Boot Device - setbootdevice
This command sets the boot device specified by its WWN, LUN and desired topology.
• Set t to 0 for Arbitrated Loop.
• Set t to 1 for Point-to-Point.
The selected device boots when the system reboots.
Note: The boot code must be enabled before you can issue the setbootdevice command.
• To set the boot device, type (all on one line):

OSLpCfg setbootdevice n=<adapter number> w0=<WWPN word 0>
w1=<WWPN word 1> l=<Decimal ID of LUN> t=<topology>
Note: Enter the LUN number in decimal.
• The following example set the boot device on HBA #1, LUN #46 with a desired topology of
Arbitrated Loop:
OSLpCfg setbootdevice n=1 w0=a1b2c3d4 w1=b946a4e8 l=46 t=0
Note: If port login fails after 50 msecs, the command is retried once.
Selecting One or More Alternate Boot Devices - setAlBoot

This command sets up alternate boot devices. You can set up to 7 alternate boot devices (index i can be
from 1 to 7).
Note: The boot code must be enabled before you can issue the setAltBoot command.
• To set up one or more alternate boot devices, type (all on one line):
OSLpCfg setAltBoot n=<adapter number> i=<index> w0=<WWPN word 0>
w1=<WWPN word 1> l=<Decimal ID of LUN>
• The following example set the alternate boot device on HBA #1, LUN #3:
OSLpCfg setAltBoot n=1 i=1 w0=12345678 w1=a842b6 I=3

Configuration Commands
Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper
With this command you can select the default PCI configuration or other configurations. Selections are:
• 0 for none
• 1 for hardware default
• 2 for soft jumpering
Alternate regions are 6 or 7 (used only for selection 2, soft jumper).
• To set soft jumpers or the hardware default, type (all on one line):
OSLpCfg jumper n=<adapter number> s=<selection> r=<alternate
region>
Note: Parameter r is only used in soft jumpering, that is, if s=2.
• The following example sets up HBA #5 to use soft jumpers in region 7:

OSLpCfg jumper n=5 s=2 r=7
• The following example selects the default PCI configuration for HBA #4:
OSLpCfg jumper n=4 s=1
Updating Configuration Regions - config
To update configuration regions, you must initialize those configuration regions prior to running the
config command. Valid region numbers range from 0 to 32.
HBA name is the one that appears in when you run the listHBA command.
• To update a specified configuration region with all HBAs of the same selected name with
contents from a selected configuration file, type (all on one line):
OSLpCfg config a=<adapter name> r=<region number> l=<byte length>
c=<configuration filename>
Note: The adapter name is the name that appears when you run the listHBA command. For
more information on the listHBA command, see “Viewing all HBAs in the System -
listhba” on page 31.
Byte length is in decimal format.

• The following example updates region 6 of all LP11000 HBAs with ctplus1.cfl.
OSLpCfg config a=lp11000 r=6 l=68 c=ctplus1.cfl
• The following example updates region 17 of all ABC24-FC56 HBAs with d:\dfplus1.cfl.\:
OSLpCfg config a=ABC24-FC56 r=17 l=100 c=d:\dfplus1.cfl
• To update a specified configuration region of only one HBA specified by its number with contents
from a selected configuration file, type (all on one line):
OSLpCfg config n=<adapter number> r=<region number> l=<byte
length> c=<configuration filename>
• The following example updates region 17 of HBA number 4 with heplus1.cf1:
OSLpCfg config n=4 r=17 l=100 c=heplus1.cfl
• The following example updates region 6 of HBA number 2 with d:\dfplus1.cf1:
OSLpCfg config n=2 r=6 l=68 c=d:\dfplus1.cfl

Running Diagnostic Tests
Running the External Loopback Test - extloopback

This command runs the external loopback test. You must install a loopback plug on each HBA to be
tested. You can test a specific HBA or on all HBAs in the system. Specify the number of times you want
the test to repeat, and direct the test response if an error is encountered. The test action option on error
is o:
• o=1 for stop
• o=2 for repeat
• o=3 for ignore
• To run the external loopback test, type (all on one line):
OSLpCfg extloopback n=<all/adapter number> r=<repeat count>
o=<option on error>
• The following example runs the external loopback test 50 times on HBA #1 and stops the test if
an error is encountered:
OSLpCfg extloopback n=1 r=50 o=1
• The following example runs the external loopback test 20 times on all HBAs in the system and
ignores any errors encountered:
OSLpCfg extloopback n=all r=20 o=3
Running the Internal Loopback Test - intloopback
This command runs the internal loopback test. You can run the test on a specific HBA or on all HBAs in
the system. Specify the number of times you want the test to repeat, and direct the test response if an
error is encountered.The test action option on error is o:
• o=1 for stop
• o=2 for repeat
• o=3 for ignore
• To run the internal loopback test, type (all on one line):
OSLpCfg intloopback n=<all/adapter number> r=<repeat count>
o=<option on error>
• The following example runs the internal loopback test 100 times on HBA #1 and stops the test if
an error is encountered:
OSLpCfg intloopback n=1 r=100 o=1
• The following example runs the internal loopback test 25 times on all HBAs in the system and
ignores any errors encountered:
OSLpCfg intloopback n=all r=25 o=3
Running the PCI Loopback Test - pciloopback
This command runs the PCI loopback test. You can run the test on a specific HBA or on all HBAs in the
system. Specify the number of times you want the test to repeat, and direct the test response if an error
is encountered. o is the test action option on error:
• o=1 for stop
• o=2 for repeat
• o=3 for ignore

• To run the PCI loopback test, type (all on one line):
OSLpCfg pciloopback n=<all/adapter number> r=<repeat count>
o=<option on error>
• The following example runs the PCI loopback test 100 times on all HBAs in the system and
stops the testing if any errors are encountered.
OSLpCfg pciloopback n=all r=100 o=1
Using Script Files
Creating Script Files

You can group commands together and execute them using a script file. You can also enter comment
lines (which begin with a semicolon). Each line follows the same command syntax as those documented
in this manual. The offline utilities allows you to:
• Execute commands entered in a script file. Use the @ command to execute the script file.
• Execute commands multiple times. Add the repeat command as the last line of the script file.
• Stop execution of a script file at any time by pressing <s>.
Script File Commands

Here is a sample script file. Each command follows the syntax covered above. The comment lines begin
with a semicolon (;):
version
screendisplay o=0
;download a=lpe11000 i=c:\temp\zd272a2.all
;reset n=1 s=0
;reset n=2 s=0
reset n=all s=0
listboot n=1
enableboot n=1 i=2
; pciloopback n=1 r=10 o=1
; pciloopback n=2 r=10 o=2
; pciloopback n=all r=50 o=3
intloopback n=all r=10 o=1
extloopback n=all r=40 o=3
;repeat r=10
Repeating a Series of Commands - repeat
This command is valid only in a script file. Enter this command at the end of a script file to repeat a
series of commands from the beginning of the script file a specific number of times.
Note: To interrupt and stop the repeat command, press <S> or <s>.
• To repeat the series of commands in the script file, add the following as the last line of the file:
repeat r=<repeat count>
• The following example repeats the series of commands in the script file 10 times.
repeat r=10
Enabling or Disabling Test Messages on the Screen - screendisplay
This command enables or disables test message display on the screen.

• o=0 prevents messages from appearing
• o=1 enables messages
Note: This command is supported only in script files.
• To enable or disable test message displays, add the following line to the script:
OSLpCfg screendisplay o=<display option>
• In the following script file example, messages from the version and listhba commands are output
to the log file and to the screen. After the screendisplay command is set to 0, all successive
commands (download, listboot and enableboot) result messages are output only to the log file,
not to the screen.
version
listhba
screendisplay o=0
download a=lpe11000 i=c:\temp\zd272a2.all
listboot n=2
enableboot n=2 i=1
Updating NVPARMS - scriptWWNN
This command reads the WWNN words 0 and 1 from the command line to update the NVPARMS. You
can also include this command in a script file. When the HBA is discovered, the new WWNN value is
used. The HBA retains the original WWNN in another region of the firmware.
Caution: Use the scriptWWNN command with caution. If you use the same WWNN on
more than one HBA in a fabric, unpredictable results may occur..
• To change WWNN words 0 and 1 from the command line, type (all in one line):
scriptWWNN n=<adapter number> w0=<WWNN word 0> w1=<WWNN word 1>
• The following example updates NVPARMS WWNN word 0 and word 1 for HBA #1:
scriptWWNN n=1 w0=40A2D6B8 w1=B620A1B2
Note: If the scriptVWWNN command has been used previously, the HBA continues to use
that WWNN until you change the WWNN with restoreNVWWN.
Note: If the HBA firmware does not support the Volatile WWN, an error message appears,
"Write Volatile Parms Error. Reported Error 48". Install the latest firmware to fix this.
Updating NVPARMS - scriptWWPN

This command reads WWPN words 0 and 1 from the command line to update the NVPARMS. You can
also include this command in a script file. When it is discovered, the HBA uses the new WWPN value. It
does not use the original IEEE address assigned by manufacturing. That address is located in
Configuration Region 16 (or 32).
Caution: Use the scriptWWPN command with caution. If you use the same WWNN on more
than one HBA in a fabric, unpredictable results may occur .
• To change WWPN words 0 and 1 from the command line, type (all in one line):
scriptWWPN n=<adapter number> w0=<WWPN word 0> w1=<WWPN word 1>
• The following example updates the NVPARMS WWPN word 0 word 1 for HBA #1:
scriptWWPN n=1 w0=40A2D6B8 w1=C920A1B2

Updating Volatile NVPARMS - scriptVWWPN
This command reads the WWPN words 0 and 1 from the command line to update the Volatile WWPN.
You can also include this command in a script file.
When discovered, the HBA uses this new WWPN. It does not use the original IEEE address assigned by
manufacturing (located in Configuration Region 16 [or 32]) nor does the HBA use the value entered by
WriteWWN or ScriptWWPN.
If the HBA does not have firmware that supports the Volatile WWN, the error message, "Write Volatile
Parms Error. Reported Error of 48" appears. If this occurs, install firmware that supports the Volatile
WWN.
Note: Once you enter this command, the WWPN selected is used by the HBA until the
restoreNVWWN is issued.
Caution: Use the scriptVWWPN command with caution. If you use the same VWWNN on
more than one HBA in a fabric, unpredictable results may occur.
• To change VWWPN words 0 and 1 from the command line, type (all in one line):
scriptVWWPN n=<adapter number> w0=<WWPN word 0> w1=<WWPN word 1>
• The following example updates the volatile NVPARMS WWPN word 0 word 1 for HBA #1:
scriptVWWPN n=1 w0=40A2D6B8 w1=C920A1B2
Creating a logfile
This command is valid only in a script file. It creates a log file with a specified directory and file name.
The default log file is LpCfglog.txt and is created in the system’s current directory.
• To create a log file use the following command as the first command in your script file, type:
logfile l=<filename>
• The following example creates a file called lplog.txt in the d:\ directory:
logfile l=d:\log\lplog.txt
• Results of all commands are recorded in a log file. Unless otherwise specified by the logfile
command, the default log file is LpCfglog.txt in the current directory.
• Sample log file:
>>>>>>>> Test Script starts on Tue Jul 31 14:52:36 2007>>>>>>>>

listhba
adapter 1: C96C146D Functional FW: WS2.70A5 LPe1150-F4
adapter 2: C94B0718 Functional FW: ZS2.72A2 LPe11002-F4
**Start tests on Adapter 1
Run EXT Loopback
Pass 500 test(s)
*Complete tests on Adapter 1, NO error
Run EXT Loopback
Pass 500 test(s)

intloopback n=all r=500 o=1
Run INT Loopback
Pass 500 test(s)
Run INT Loopback
Pass 500 test(s)
pciloopback n=all r=500 o=1
Run PCI Loopback
Pass 500 test(s)
Run PCI Loopback
Pass 500 test(s)
EXTLB: Error - Link is not UP
Encounter Error, stop all tests
>>>>>>> Test Script stops on Tue Jul 31 14:53:45 2007

Error Codes
Table 2: The Offline Utilities Error Codes
Error Code Description
0 No error
1 Invalid adapter number
2 Mailbox command error
3 No valid boot (BIOS) code found
4 Open file error
5 Invalid configuration region
6 Invalid adapter name
7 Download error
8 Invalid boot (BIOS) code index
9 Link NOT up for external loopback test
10 Link NOT up for internal loopback test
11 Invalid jumper selection (in jumper command)
12 Invalid alternate configuration region (in jumper command)
13 PCI loopback test fails
14 Adapter reset error
15 Read configuration region error
16 No VPD information available
17 No command in command line
18 Open log file error
19 Read wakeup parameters error
20 Update wakeup parameters error
21 Incorrect test parameters
22 Stopped by user
23 Internal loopback test fails
24 External loopback test fails
25 Error exists after four retries
26 Invalid command
27 Incorrect syntax
28 Command supported only in script files
29 Read_rev error
30 Dump configuration region error
31 Read file error
32 Short file error
33 Read NVPARMS error

Table 2: The Offline Utilities Error Codes (Continued)
Error Code Description
34 Write NVPAMRMS error

35 Command does not support all adapters
36 Invalid LUN number
37 No boot (BIOS) code enabled
38 Update configuration region error
39 No boot (BIOS) found
40 Dump memory error
41 Update erasable read-only memory (EROM) error
42 Delete load entry error
43 Write WWN error
44 Not supported in script files
45 No Emulex HBA found
46 Invalid Alternate Boot Device Index
47 Cannot Restart Adapter
48 Write Volatile Parameters error
49 POST Test Error
50 Incorrect Symbols
51 Invalid Length
62 Unable To Allocate Memory
63 DFC_InitDiagEnv Error
64 DFC_ReadPciCfg Error
65 No Driver Installed
66 No Valid Driver
200 General Error

Solaris SFS Driver Console and Log Messages
Introduction
Log messages are logged to the /var/adm/messages system file.
Table 1: Notice, Warnings and Error Types
Default/ Effect of Changing

Driver Parameter Related lpfc Driver Parameters
Min/Max Default
console-notices 0 Sets the verbose level for log-only (when set to 0, log
driver notices to the messages are logged to the
console. system log file and also printed on
the console.)
console-warnings 0 Sets the verbose level for
driver warnings to the Default = Disabled
console.
console-errors 0 Sets the verbose level for

driver errors to the console.
log-notices 0xffffffff; Sets the verbose level for log-verbose (when set to non-zero,
driver notices to the system verbose messages are generated.)
log file.
Default = Disabled
log-warnings 0xffffffff; Sets the verbose level for
driver warnings to the
system log file.
log-errors 0xffffffff; Sets the verbose level for

driver errors to the system
log file.

Table 2 lists the types of log messages that can be logged to the system file.
Table 2: Log Message Types
LOG Message Verbose Verbose Description

Verbose Bit
Mask
LOG_MISC 0x00000001 Miscellaneous events
LOG_DRIVER 0x00000002 Driver attach and detach events
LOG_INIT 0x00000004 HBA Initialization events
LOG_MEM 0x00000008 Memory management events
LOG_SLI 0x00000010 SLI events
LOG_MBOX 0x00000020 Mailbox events
LOG_NODE 0x00000040 Node events
LOG_LINK 0x00000080 Link events
LOG_ELS 0x00000100 ELS events
LOG_PKT 0x00000200 General I/O packet events
LOG_FCP 0x00000400 FCP traffic events
LOG_TGTM 0x00000800 FCP target mode events
LOG_IP 0x00001000 IP traffic events
LOG_SFS 0x00002000 Solaris SFS events
LOG_IOCTL 0x00004000 IOCTL events
LOG_FIRMWARE 0x00008000 Firmware download events
LOG_CT 0x00010000 FC Common Transport events
LOG_RESERVED 0x01FE0000 Reserved for future use
LOG_NODE_DETAIL 0x02000000 Detailed Node events
LOG_IOCTL_DETAIL 0x04000000 Detailed IOCTL events
LOG_IP_DETAIL 0x08000000 Detailed IP events
LOG_FIRMWARE_DETAIL 0x10000000 Detailed Firmware events
LOG_Solaris SFS_DETAIL 0x20000000 Detailed Solaris SFS events
LOG_MBOX_DETAIL 0x40000000 Detailed Mailbox events
LOG_SLI_DETAIL 0x80000000 Detailed HBA SLI events
LOG_ALL_MSG 0XFFFFFFFF Detailed Node events

Severity Levels
Table 3: Severity Levels
Level Message Description
DEBUG (Informational Message provides engineering debug information.
NOTICE (Informational) Message provides a general purpose information.
WARNING Message provides a general purpose warning.
ERROR Message indicates that a driver error has occurred.
PANIC (Severe) Message indicates that the driver has forced a system panic to occur.
Message Log Example

The following is an example of a message on the system console.
[5.0336]emlxs0: NOTICE: 720: Link up. (1Gb, fabric)
The following is an example of the same message in the system message log (/var/adm/messages) file.
Jan 19 14:45:36 sunv240 emlxs: [ID 349649 kern.info] [5.0336]emlxs0: NOTICE: 720:
Link up. (1Gb, fabric)
In the above system log message:
• Jan 19 14:45:36 unidentified the date and time when the error or event occurred.
• sunv240 identifies the name of the host machine.
• emlxs identifies the message came from the Emulex emlxs driver.
• [ID 349649 kern.info] identifies a Solaris-specific message ID and kernel message level. This
changes from one driver message to another.
• [5.0336] identifies the emlxs driver message context tag. This may change from one driver
version to another.
• emlxs0 identifies the message is coming from the emlxs driver instance zero. This changes from
one driver instance to another.
• NOTICE identifies the emlxs message severity level. This may change from one driver version
to another.
• 720 identifies the emlxs drive message id. This does not change from one driver version to
another.
• Link up identifies the actual error or event message. This does not change from one driver
version to another.
• (1Gb, fabric) identifies additional information specific to the error or event message. This
information is normally intended for Technical support / engineering use. This may change from
one driver version to another.

Miscellaneous Events
MSG_ID: 0001 Debug

VERBOSE_MASK: LOG_MISC (0x00000001)
DESCRIPTION: This is a general purpose informational message.
SEVERITY LEVEL: Debug
MESSAGE: None
ACTION: No action needed, informational.
MSG_ID: 0002 Notice

DESCRIPTION: This is a general purpose informational message.
SEVERITY LEVEL: Notice
MESSAGE: None
MSG_ID: 0003 Warning

DESCRIPTION: This is a general purpose warning message.
SEVERITY LEVEL: Warning
MESSAGE: None
MSG_ID: 0004 Error

DESCRIPTION: This is a general purpose error message.
SEVERITY LEVEL: Error
MESSAGE: None
MSG_ID: 0005 Panic

DESCRIPTION: This is a general purpose panic message.
SEVERITY LEVEL: Panic (Severe)
MESSAGE: None
ACTION: Contact Technical Support.
Driver Events
MSG_ID: 0100 Notice: Driver Attach

VERBOSE_MASK: LOG_DRIVER (0x00000002)
DESCRIPTION: This indicates that the driver is performing an attach operation.
MESSAGE: None

MSG_ID: 0101 Error: Driver Attach Failed
DESCRIPTION: This indicates that the driver was unable to attach due to some issue.
MESSAGE: Driver attach failed
ACTION: Check your hardware and software configuration. If problems persist, report these errors to
Technical Support.
MSG_ID: 0102 Debug: Driver Attach

DESCRIPTION: This indicates that the driver is performing an attach operation.
MESSAGE: Driver attach
MSG_ID: 0110 Notice: Driver Detach

DESCRIPTION: This indicates that the driver is performing an detach operation.
MESSAGE: Driver detach
MSG_ID: 0111 Error: Driver Detach Failed

DESCRIPTION: This indicates that the driver was unable to detach due to some issue.
MESSAGE: Driver detach failed
Technical Support.
MSG_ID: 0112 Debug: Driver Detach

DESCRIPTION: This indicates that the driver is performing an detach operation.
MESSAGE: Driver detach
MSG_ID: 0120 Debug: Driver Suspend

DESCRIPTION: This indicates that the driver is performing a suspend operation.
MESSAGE: Driver suspend

MSG_ID: 0121 Error: Driver Suspend Failed
DESCRIPTION: This indicates that the driver was unable to suspend due to some issue.
MESSAGE: Driver suspend failed
Technical Support.
MSG_ID: 0130 Debug: Driver Resume

DESCRIPTION: This indicates that the driver is performing a resume operation.
MESSAGE: Driver resume
MSG_ID: 0131 Error: Driver Resume Failed

DESCRIPTION: This indicates that the driver was unable to resume due to some issue.
MESSAGE: Driver resume failed
Technical Support.
HBA Initialization Events
MSG_ID: 0200 Notice: Adapter Initialization

VERBOSE_MASK: LOG_INIT (0x00000004)
DESCRIPTION: This indicates that the adapter is initializing.
MESSAGE: Adapter Initialization
MSG_ID: 0201 Error: Adapter Initialization Failed

DESCRIPTION: This indicates that an attempt to initialize the adapter has failed.
MESSAGE: Adapter initialization failed
ACTION: Check your hardware configuration. If problems persist, report these errors to Technical Support.
MSG_ID: 0202 Debug: Adapter Initialization

DESCRIPTION: This indicates that the adapter is initializing.
MESSAGE: Adapter Initialization

MSG_ID: 0210 Debug: Adapter Transition
DESCRIPTION: This indicates that the adapter is changing states.
MESSAGE: Adapter transition
MSG_ID: 0220 Debug: Adapter Online

DESCRIPTION: This indicates that the adapter is online and ready to communicate.
MESSAGE: Adapter online
MSG_ID: 0230 Debug: Adapter Offline

DESCRIPTION: This indicates that the adapter is offline and unable to communicate.
MESSAGE: Adapter offline
MSG_ID: 0230 Warning: Adapter Shutdown

DESCRIPTION: This indicates that the adapter has been shutdown and requires a reboot to reinitialize.
MESSAGE: Adapter shutdown
ACTION: Contact Technical Support.
MSG_ID: 0240 Error: Adapter Reset Failed

DESCRIPTION: This indicates that an attempt to reset the adapter has failed.
MESSAGE: Adapter reset failed
Memory Management Events
MSG_ID: 0300 Debug: Memory Allocated

VERBOSE_MASK: LOG_MEM (0x00000008)
DESCRIPTION: This indicates that the driver allocated system memory.
MESSAGE: Memory alloc

MSG_ID: 0301 Error: Memory Allocation Failed
DESCRIPTION: This indicates that the driver was unable to allocate system memory. The system is low
on memory resources.
MESSAGE: Memory alloc failed
ACTION: No action needed. If problems persist, report these errors to your system administrator.
MSG_ID: 0310 Error: Memory Pool Error

DESCRIPTION: This indicates that a problem has occurred with the memory buffer pool management.
MESSAGE: Memory pool error
ACTION: No action needed. If problems persist, report these errors to Technical Support.
MSG_ID: 0311 Debug: Memory Pool Allocation Failed

DESCRIPTION: This indicates that the driver was unable to allocate memory from one of its own memory
pools.
MESSAGE: Memory pool alloc failed
ACTION: If the problem occurs frequently you may be able to configure more resources for that pool. If this
does not solve the problem, report these errors to Technical Support.
MSG_ID: 0320 Notice: No Unsolicited Buffer Available

DESCRIPTION: This indicates that the driver’s unsolicited buffer pool is exhausted. The I/O is dropped
and most likely retried by the remote device.
MESSAGE: No unsolicited buffer available
ACTION: If the problem occurs frequently you may be able to configure more resources for that pool. If this
does not solve the problem, report these errors to Technical Support.
SLI Events
MSG_ID: 0400 Debug: Vital Product Data

VERBOSE_MASK: LOG_SLI (0x00000010)
DESCRIPTION: This provides vendor-specific information about the adapter.
MESSAGE: Vital Product Data
MSG_ID: 0410 Debug: Link Attention

DESCRIPTION: This indicates that the adapter has triggered a link attention interrupt.
MESSAGE: Link attn

MSG_ID: 0411 Debug: State Change
DESCRIPTION: This indicates that the adapter has changed state.
MESSAGE: State change
MSG_ID: 0420 Error: Adapter Hardware Error

DESCRIPTION: This indicates that an interrupt has occurred and the status register indicates a
nonrecoverable hardware error.
MESSAGE: Adapter hardware error
ACTION: This error usually indicates a hardware problem with the adapter. Try running adapter
diagnostics. Report these errors to Technical Support.
MSG_ID: 0430 Debug: Ring Event

DESCRIPTION: This indicates that an SLI ring event has occurred.
MESSAGE: Ring event
MSG_ID: 0431 Debug: Ring Error

DESCRIPTION: This indicates that an SLI ring error is being reported by the adapter.
MESSAGE: Ring error
MSG_ID: 0432 Debug: Ring Reset

DESCRIPTION: This indicates an SLI ring is being reset.
MESSAGE: Ring reset
MSG_ID: 0440 Debug: Adapter Msg

DESCRIPTION: This indicates that a message was sent to the driver from the adapter.
MESSAGE: Adapter msg

MSG_ID: 0450 Error: IOCB Invalid
DESCRIPTION: This indicates that an IOCB was received from the adapter with an illegal value. This error
could indicate a driver or firmware problem.
MESSAGE: IOCB invalid
MSG_ID: 0451 Debug: IOCB Queue Full

DESCRIPTION: This indicates that the IOCB queue is full. This occurs during normal operation.
MESSAGE: IOCB queue full
MSG_ID: 0452 Debug: IOCB Error

DESCRIPTION: This indicates an IOCB local error is being reported by the adapter.
MESSAGE: IOCB error
MSG_ID: 0453 Debug: IOCB Stale

DESCRIPTION: This indicates an IOCB completed after its associated packet completed.
MESSAGE: IOCB stale
MSG_ID: 0460 Debug: SLI Detail

VERBOSE_MASK: LOG_SLI _DETAIL (0x20000000)
DESCRIPTION: This provides detailed information about an SLI event.
MESSAGE: SLI detail
Mailbox Events
MSG_ID: 0500 Debug: Mailbox Event

VERBOSE_MASK: LOG_MBOX (0x00000020)
DESCRIPTION: This indicates that a mailbox event has occurred.
MESSAGE: Mailbox event

MSG_ID: 0501 Debug: Mailbox Detail
VERBOSE_MASK: LOG_MBOX _DETAIL (0x40000000)
DESCRIPTION: This provides detailed information about a mailbox event.
MESSAGE: Mailbox detail
MSG_ID: 0510 Debug: Stray Mailbox Interrupt

DESCRIPTION: This indicates that a mailbox command completion interrupt was received and the mailbox
is not valid. This error could indicate a driver or firmware problem.
MESSAGE: Stray mailbox interrupt
ACTION: No action needed, informational. If problems persist, report these errors to Technical Support.
MSG_ID: 0520 Error: Mailbox Completion Error

DESCRIPTION: This indicates that an unsupported or illegal mailbox command was completed. This error
could indicate a driver or firmware problem.
MESSAGE: Mailbox completion error
Node Events
MSG_ID: 0600 Debug: Node Create

VERBOSE_MASK: LOG_NODE (0x00000040)
DESCRIPTION: This indicates that a node has been created for a remote device.
MESSAGE: Node create
MSG_ID: 0601 Debug: Node Opened

DESCRIPTION: This indicates that a node has been opened for I/O transport.
MESSAGE: Node opened.
MSG_ID: 0602 Notice: Node Create Failed

DESCRIPTION: This indicates that a node create request for a remote device has failed.
MESSAGE: Node create failed

MSG_ID: 0603 Debug: Node Updated
DESCRIPTION: This indicates that a node has been updated for a remote device.
MESSAGE: Node updated
MSG_ID: 0610 Debug: Node Destroy

DESCRIPTION: This indicates that a node has been destroyed for a remote device.
MESSAGE: Node destroyed
MSG_ID: 0611 Debug: Node Closed

DESCRIPTION: This indicates that a node has been temporarily closed for I/O transport.
MESSAGE: Node closed
MSG_ID: 0612 Notice: Node Missing

DESCRIPTION: This indicates that an FCP2 device node has been found missing.
MESSAGE: Node missing
MSG_ID: 0620 Debug: Node Not Found

DESCRIPTION: This indicates that there was an attempt to send an I/O packet to an unknown device
node. The driver maintains a node table entry for every device it needs to communicate with on the FC
network.
MESSAGE: Node not found
Link Events
MSG_ID: 0700 Debug: Link Event

VERBOSE_MASK: LOG_SLI (0x00000010) or LOG_LINK (0x00000080)
DESCRIPTION: This indicates that a link event has occurred.
MESSAGE: Link event

MSG_ID: 0710 Notice: Link Down
VERBOSE_MASK: LOG_LINK (0x00000080)
DESCRIPTION: This indicates that the FC link is down to the adapter.
MESSAGE: Link down
ACTION: Check your network connections. If problems persist, report these errors to system administrator.
MSG_ID: 0720 Notice: Link Up

DESCRIPTION: This indicates that the FC link is up.
MESSAGE: Link up
MSG_ID: 0721 Notice: NPIV Link Up

DESCRIPTION: This indicates that the FC link is up for all virtual ports.
MESSAGE: NPIV Link up
MSG_ID: 0730 Notice: Link Reset

VERBOSE_MASK: LOG_LINK (0x00000080) or LOG_SFS (0x00002000)
DESCRIPTION: This indicates that an issue has forced the FC link to be reset.
MESSAGE: Link reset
MSG_ID: 0731 Error: Link Reset Failed

VERBOSE_MASK: LOG_LINK (0x00000080) or LOG_SFS (0x00002000)
DESCRIPTION: This indicates that an attempt to reset the FC link has failed.
MESSAGE: Link reset failed
ELS Events
MSG_ID: 0800 Debug: ELS Sent

VERBOSE_MASK: LOG_ELS (0x00000100)
DESCRIPTION: This indicates that an ELS command is being sent.
MESSAGE: ELS sent

MSG_ID: 0801 Debug: ELS Comp
DESCRIPTION: This indicates that an ELS command completed normally.
MESSAGE: ELS comp
MSG_ID: 0810 Error: Stray ELS Completion

DESCRIPTION: This indicates that an ELS command completion was received without issuing a
corresponding ELS command. This error could indicate a driver or firmware problem.
MESSAGE: Stray ELS completion
MSG_ID: 0811 Debug: Abnormal ELS Completion

DESCRIPTION: This indicates that an ELS command completion with a status error in the IOCB. It could
mean the FC device on the network is not responding or the FC device is not an FCP target. The driver
automatically retries this ELS command if needed.
MESSAGE: Abnormal ELS completion
ACTION: If the command is a PLOGI or PRLI, and the destination PortID is not an FCP target, no action is
needed. Otherwise, check the physical connections to the FC network and the state of the remote PortID.
MSG_ID: 0820 Debug: ELS Rcvd

DESCRIPTION: This indicates that an unsolicited ELS command was received.
MESSAGE: ELS recvd
MSG_ID: 0821 Debug: Unsolicited ELS Dropped

DESCRIPTION: This indicates that an unsolicited ELS command was received and then dropped for some
reason.
MESSAGE: Unsolicited ELS dropped
MSG_ID: 0822 Debug: ELS Reply

DESCRIPTION: This indicates that a reply is being sent for an unsolicited ELS command.
MESSAGE: ELS reply

MSG_ID: 0830 Error: Invalid ELS Command Found
DESCRIPTION: This indicates that an ELS command was found with an invalid command code.
MESSAGE: Invalid ELS command found
General I/O Packet Events
MSG_ID: 0900 Notice: Packet Abort

VERBOSE_MASK: LOG_PKT (0x00000200)
DESCRIPTION: This indicates that an I/O packet is being aborted.
MESSAGE: Packet abort
MSG_ID: 0901 Warning: Packet Abort Failed

DESCRIPTION: This indicates that an attempt to abort an I/O packet has failed.
MESSAGE: Packet abort failed
MSG_ID: 0910 Debug: Packet Timeout

DESCRIPTION: This indicates that an I/O packet has timed out and is being aborted.
MESSAGE: Packet timeout
MSG_ID: 0911 Debug: Ring Watchdog

DESCRIPTION: This indicates that I/O(s) are getting stale waiting on a ring TX queue
MESSAGE: Ring watchdog
MSG_ID: 0911 Debug: TXQ Watchdog

DESCRIPTION: This indicates that I/O(s) was found missing from the transmit queue.
MESSAGE: TXQ watchdog

MSG_ID: 0920 Debug: Packet Flush
DESCRIPTION: This indicates that an I/O packet is being flushed.
MESSAGE: Packet flush
MSG_ID: 0921 Debug: Packet Flushed

DESCRIPTION: This indicates that an I/O packet has been flushed.
MESSAGE: Packet flushed
MSG_ID: 0922 Notice: Packet Flush Timeout

DESCRIPTION: This indicates that an I/O packet flush request has timed out with some I/O packets still
not completed. The driver attempts to recover by itself.
MESSAGE: Packet flush timeout
MSG_ID: 0930 Notice: Packet Transport Failed

DESCRIPTION: This indicates that an attempt to send an I/O packet failed. The I/O packet is retried by the
upper layer.
MESSAGE: Packet transport failed
MSG_ID: 0931 Error: Packet Transport Error

DESCRIPTION: This indicates that an error occurred while attempting to send an I/O packet. The I/O
packet likely fails back to the user application.
MESSAGE: Packet transport error
MSG_ID: 0932 Debug: Packet Transport

DESCRIPTION: This provides additional information about a packet being sent.
MESSAGE: Packet transport

MSG_ID: 0940 Debug: Packet Completion Error
DESCRIPTION: This indicates that an I/O packet was completed with an error status. This can occur
during normal operation.
MESSAGE: Packet completion error.
FCP Traffic Events
MSG_ID: 1000 Debug: Stray FCP Completion

VERBOSE_MASK: LOG_FCP (0x00000400)
DESCRIPTION: This indicates that an FCP command completion was received without issuing a
corresponding FCP command. This error could indicate a driver or firmware problem.
MESSAGE: Stray FCP completion
MSG_ID: 1001 Debug: FCP Completion Error

VERBOSE_MASK: LOG_FCP (0x00000400)
DESCRIPTION: This indicates that an FCP command completed with an error status. These errors can
occur during normal operation.
MESSAGE: FCP completion error
IP Traffic Events
MSG_ID: 1200 Debug: IP Detail

VERBOSE_MASK: LOG_IP_DETAIL (0x08000000)
DESCRIPTION: This provides detailed information about the driver’s IP interface.
MESSAGE: IP detail
MSG_ID: 1210 Error: Stray IP Completion

VERBOSE_MASK: LOG_IP (0x00001000)
DESCRIPTION: This indicates that an IP sequence completion was received without issuing a
corresponding IP sequence. This error could indicate a driver or firmware problem.
MESSAGE: Stray IP completion

MSG_ID: 1211 Debug: Abnormal IP Completion
DESCRIPTION: This indicates that an IP sequence completed with a status error in the IOCB. It could
mean the FC device on the network is not responding.
MESSAGE: Abnormal IP completion
ACTION: No action needed, informational. If problems persist, report these errors to system administrator.
MSG_ID: 1220 Debug: Unsolicited IP Dropped

DESCRIPTION: This indicates that an unsolicited IP sequence was received, but was dropped for some
reason.
MESSAGE: Unsolicited IP dropped
MSG_ID: 1221 Debug: IP Recvd

DESCRIPTION: This indicates that an unsolicited IP sequence was received.
MESSAGE: IP received
MSG_ID: 1230 Error: Invalid IP Sequence Found

DESCRIPTION: This indicates that an IP sequence was found with an invalid code.
MESSAGE: Invalid IP sequence found
Solaris SFS Events
MSG_ID: 1300 Debug: SFS

VERBOSE_MASK: LOG_SFS (0x00002000)
DESCRIPTION: This provides general information about the driver’s Solaris SFS interface.
MESSAGE: SFS
MSG_ID: 1301 Debug: SFS Detail

VERBOSE_MASK: LOG_SFS_DETAIL (0x20000000)
DESCRIPTION: This provides detailed information about the driver’s Solaris SFS interface.
MESSAGE: SFS detail

MSG_ID: 1310 Warning: Diagnostic Error
DESCRIPTION: This indicates that a diagnostic request did not complete because of some issue.
MESSAGE: Diagnostic error
MSG_ID: 1311 Debug: ECHO Diagnostic Completed

DESCRIPTION: This indicates that an ECHO diagnostic has completed.
MESSAGE: ECHO diagnostic completed
MSG_ID: 1312 Warning: ECHO Diagnostic Failed

DESCRIPTION: This indicates that an ECHO diagnostic has failed to return a positive result. This could
indicate a connectivity problem with your FC network.
MESSAGE: ECHO diagnostic failed
ACTION: Check your network connections. If problems persist report these errors to system administrator.
MSG_ID: 1313 Debug: BIU Diagnostic Completed

DESCRIPTION: This indicates that a BIU diagnostic has completed.
MESSAGE: BIU diagnostic completed
MSG_ID: 1314 Error: BIU Diagnostic Failed

DESCRIPTION: This indicates that a BIU diagnostic has failed to return a positive result. This is usually
caused by an adapter hardware problem.
MESSAGE: BIU diagnostic failed
ACTION: Report this error to Technical Support.
MSG_ID: 1315 Debug: POST Diagnostic Completed

DESCRIPTION: This indicates that a POST diagnostic has completed.
MESSAGE: POST diagnostic completed

MSG_ID: 1316 Error: POST Diagnostic Failed
DESCRIPTION: This indicates that a POST diagnostic has failed to return a positive result. This is usually
caused by an adapter hardware problem.
MESSAGE: POST diagnostic failed
ACTION: Report this error to Technical Support.
IOCTL Events
MSG_ID: 1400 Debug: IOCTL

VERBOSE_MASK: LOG_IOCTL (0x00004000)
DESCRIPTION: This provides general information about the driver’s IOCTL interface.
MESSAGE: IOCTL
MSG_ID: 1401 Debug: IOCTL Detail

VERBOSE_MASK: LOG_IOCTL_DETAIL (0x04000000)
DESCRIPTION: This provides detailed information about the driver’s IOCTL interface.
MESSAGE: IOCTL detail
MSG_ID: 1410 Debug: DFC

DESCRIPTION: This provides general information about the driver’s DFC interface.
MESSAGE: DFC
MSG_ID: 1411 Debug: DFC Detail

VERBOSE_MASK: LOG_IOCTL_DETAIL (0x04000000)
DESCRIPTION: This provides detailed information about the driver’s DFC interface.
MESSAGE: DFC detail
MSG_ID: 1420 Debug: DFC Error

DESCRIPTION: This indicates that an error was found while processing a DFC request.
MESSAGE: DFC error

Firmware Download Events
MSG_ID: 1500 Debug: Firmware Image

VERBOSE_MASK: LOG_FIRMWARE (0x00008000)
DESCRIPTION: This provides information about the firmware interface.
MESSAGE: Firmware image
MSG_ID: 1501 Debug: Firmware Image Detail

VERBOSE_MASK: LOG_FIRMWARE_DETAIL (0x10000000)
DESCRIPTION: This provides detailed information about the firmware interface.
MESSAGE: Firmware detail
MSG_ID: 1510 Error: Bad Firmware Image

DESCRIPTION: This indicates that a bad firmware image was provided to the download function.
MESSAGE: Bad firmware image
ACTION: Obtain the proper image file. If problems persist report these errors to Technical Support.
MSG_ID: 1511 Error: Firmware Image Not Compatible

DESCRIPTION: This indicates that the firmware image provided was not compatible with the existing
hardware.
MESSAGE: Firmware image not compatible
ACTION: Obtain the proper image file. If problems persist report these errors to Technical Support.
MSG_ID: 1520 Notice: Firmware Download

DESCRIPTION: This indicates that an attempt to download a firmware image has occurred.
MESSAGE: Firmware download
ACTION: No action needed, informational. If problems persist report these errors to Technical Support.
MSG_ID: 1521 Notice: Firmware Download Complete

DESCRIPTION: This indicates that an attempt to download a firmware image was successful.
MESSAGE: Firmware download complete

MSG_ID: 1522 Error: Firmware Download Failed
DESCRIPTION: This indicates that an attempt to download a firmware image was failed.
MESSAGE: Firmware download failed
Common Transport Events
MSG_ID: 1600 Debug: CT sent

VERBOSE_MASK: LOG_CT (0x00010000)
DESCRIPTION: This indicates that a CT command is being sent.
MESSAGE: CT sent
MSG_ID: 1601 Debug: CT comp

VERBOSE_MASK: LOG_CT (0x00010000)
DESCRIPTION: This indicates that a CT command completed normally.
MESSAGE: CT comp
MSG_ID: 1610 Error: Stray CT completion

VERBOSE_MASK: LOG_CT(0x00010000)
DESCRIPTION: This indicates that a CT command completion was received without issuing a
corresponding CT command. This error could indicate a driver or firmware problem.
MESSAGE: Stray CT completion
MSG_ID: 1611 Debug: Abnormal CT completion

DESCRIPTION: This indicates that a CT command completed with a status error in the IOCB. It could
mean the FC device on the network is not responding. The driver automatically retries this CT command if
needed.
MESSAGE: Abnormal CT completion
ACTION: Check physical connections to FC network and the state of the remote PortID.
MSG_ID: 1620 Debug: CT rcvd

DESCRIPTION: This indicates that an unsolicited CT command was received.
MESSAGE: CT rcvd

MSG_ID: 1621 Debug: Unsolicited CT dropped
DESCRIPTION: This indicates that an unsolicited CT command was received and then dropped for some
reason.
MESSAGE: Unsolicited CT dropped.
MSG_ID: 1622 Debug: CT reply

DESCRIPTION: This indicates that a reply is being sent for an unsolicited CT command.
MESSAGE: CT reply
MSG_ID: 1630 Error: Invalid CT command found

DESCRIPTION: This indicates that a CT command was found with an invalid command code.
MESSAGE: Invalid CT command found

The lp6dutil Utility
Introduction
The lp6dutil utility for DOS includes options for doing routine diagnostic tasks and for viewing a variety of
information for the HBA.
All lp6dutil tasks can be performed using the graphical user interface (GUI) screen menus. All screens
require navigation and selection using the keyboard.
Some lp6dutil tasks can be performed using the command line. These include downloading images,
setting up and running diagnostics.
Information in view-only screens is typically presented in hexadecimal format.
Start lp6dutil
Note: You cannot start lp6dutil at the DOS prompt in Windows.
1. Boot up the system with DOS.

2. From the directory where the lp6dutil.exe file resides, enter the following command:
lp6dutil
Note: For debugging, activate the lp6dutil utility without restarting the adapter by entering
the following command: lp6dutil /nr
An Introduction screen appears. A menu bar is near the top. The lp> prompt is near the bottom.
Figure 1: Introduction Screen

Use the Menu Bar
• To select a function, press and hold <Alt> and press the letter that is highlighted in the function
title. A menu is displayed. For example, if you hold down <Alt> and press <L>, the Flash menu
is displayed.To move through items within a menu, press the up and down arrow keys. You can
also press the letter that is highlighted for that menu item. In the following example, press <D> to
open the Download Image screen.
Figure 2: Flash Menu, Download Selected
Figure 3: Download Image Screen
Navigation Tips
• To move from box to box (area to area) within a screen, tab to move to the right, or hold down
<Shift> and tab to move to the left. If the box title has a highlighted letter, hold down <Alt> and
press the letter to move into the box.
• To move through items within a box or area, press the up and down arrow keys.
• ( ) parentheses next to an item indicate that you must select one choice. Typically, a
default option is selected. Press the up and down arrow keys to move through choices if
you want to select a different choice.
• [ ] brackets near or next to an item indicate an option. Tab to the item list. Press the spa-
cebar to select or clear an item. Sometimes optional choices are not active unless a
specific required choice is selected.
• Boxes within various screens may contain a vertical scroll bar on the right side of the box. This
indicates that the box contains additional information that exceeds the display capabilities of the
box. Click on the scroll bar to view additional information or selections.

• To select a button, hold down <Alt> and press the letter in red, or tab to the button and press
<Enter>. If an option does not contain a red letter, tab to that button and press <Enter>.
Note: Press <Enter> after selecting an item in a screen. If you do not press
<Enter>, the selection is not made.
• Close a screen within lp6dutil by pressing <Esc>.
Use the Command Line

At the lp> prompt, enter the command you want with the correct syntax, then press <Enter>.
• To view all available help commands, type:
help
• To view the syntax for a command, enter help followed by the command name.For example,
type:
help download
The syntax for the download command is displayed:
Syntax: download <n=adapter> <i=imagepath>
or
Syntax: download <a=adaptertype> <i=imagepath>
• The syntax requires one space between the command name and the first argument, and a
space between additional arguments.
• There is no space before or after the equal sign within an argument.
• To exit lp6dutil, type:
exit
The DOS prompt is displayed.

Commands and Syntax Reference Table
Note: Internal loopback and static random-access memory (SRAM) tests are not supported
for the LP1005DC-CM2.
Table 4: Commands and Syntax
Command Syntax Description
@ @ <command-file> Executes commands in a script file. Follow

the @ sign with the pathname of the script
file. Example: @a:\script1.txt
enableboot enableboot <n=adapter> <i=index> Enables the selected boot code on the HBA
specified by its number.
logfile logfile <l=filename> Creates a log file using the specified file
name.
exit exit Terminates the lp6dutil session and passes

control to DOS.
jumper jumper <n=adapter> Changes the state of the HBA soft jumpers,
<s=selection> <r=region> which can be used in place of the physical
jumpers on the HBA. s=0 for none, 1 for
hardware default, 2 for soft jumper. Alternate
regions, r= 6 or r=7 (used only for selection 2,
soft jumper).
pciloopback pciloopback <n=adapter/all> <r=repeat- Runs the pciloopback test. You can run this
count> <o=option> test on one HBA or on all HBAs in the system.
Options: o=1 for stop, o=2 for repeat, and o=3
for ignore.
disableboot disableboot <n=adapter> Disables the current boot code on the HBA
specified by its number.
extloopback extloopback <n=adapter/all> <r=repeat- Runs the external loopback test. The
count> <o=option> loopback plug must be installed. You can run
this test on one HBA or on all HBAs in the
system. Options: o=1 for stop, o=2 for repeat,
and o=3 for ignore.
listhba listhba Lists the HBAs that are installed in the system
(HBA #, WWN, functional FW, HBA type and
mailbox error (if any).
reset reset <n=adapter/all> <s=custom/ Resets one or all adapters in the system. s=1
standard reset> skips POST during a restart, s=0 performs a
standard reset.
repeat repeat <script> This command is used at the end of a script

file to repeat a series of commands from the
beginning of the script file.
download download <a=adapter name> Downloads the specified firmware image to all
<i=firmware image filename> HBAs of the same name.
download download <n=adapter number> Downloads the specified firmware image file
<i=firmware image filename> to the one HBA, as specified by its number.

Table 4: Commands and Syntax
Command Syntax Description
help help <command> Lists the syntax for the specified command.
listboot listboot <n=adapter> Lists boot code versions with indices (base 1)
that are currently loaded in the flash of the
HBA specified by its number.
vpd vpd n=<adapter number> This command displays the VPD contents of
the adapter specified by its number.
Reset the HBA

1. Select the Adapter menu.
Figure 4: Adapter Menu, Reset Selected

2. Press <R>. The Reset Adapter screen is displayed.
Figure 5: Reset Adapter Screen

3. Select the adapter to reset. The default is adapter #1.
4. Specify the type of reset:
• Standard is a normal reset.
• Custom allows you to reset the HBA with one or both of the custom options selected.
• STUB resets only the functional firmware.
If you select a custom or STUB only reset, the Custom Options area becomes active and you
can specify whether to skip POST or whether to ignore errors. Select one or both options by
pressing the spacebar to select. Press the spacebar again to clear.
5. Select Reset. "Resetting" is displayed briefly.
6. Select Done. The screen closes.

Perform a Warm Start
Figure 6: Adapter Menu, Warmstart/NoRam Selected

2. Press <W>. The Warmstart Adapter screen is displayed.
Figure 7: Warmstart Adapter Screen

3. Specify a type of warm start:
• Warmstart Mode accesses the RAM.
• NORAM Mode does not access RAM.
• Restart causes the adapter to start in warm start mode and then restart normally.
4. Proceed to initiate the warm start.
5. Select Done to close the screen.
Exit the lp6dutil Utility

To exit lp6dutil:
1. Select the File menu.
Figure 8: File Menu, Exit Selected

2. Press <X>. The lp6dutil session is terminated and the DOS prompt appears.

View HBA Information
View Adapter Parameters

To display a list of HBAs installed in the system, including HBA model number and device ID, from the
Adapter menu:
Figure 9: Adapter Menu, Display Selected

2. Press <D>. The Installed Adapter Parameters screen is displayed.
Figure 10: Installed Adapter Parameters Screen

3. Select an HBA in the Adapters box. Information is displayed in the Adapter Info box. This
information is view-only.
4. Select OK to close the screen.
Note: A HS20 Blade can have one HBA and two ports (appears as a 1005DC HBA). A
HS40 Blade can have two HBAs or two ports (appears as two 1005DC HBAs).
View DC Bridge Information

Figure 11: Adapter Menu, DC Bridges Selected

2. Press <B>. The Dual Channel Bridges screen is displayed.
Figure 12: Dual Channel Bridges Screen

3. Select an HBA in the Adapters box. Adapter information is displayed in the Information box.
View VPD Information

Figure 13: Adapter Menu, VPD Selected

2. Press <V>. The Adapters VPD screen is displayed.
Figure 14: Adapter VPD Screen

3. Select an HBA in the Adapters box. The adapter's VPD information is displayed in the VPD box.

View PCI Information
1. Select the Info menu.
Figure 15: Info Menu, PCI Info Selected

2. Press <P>. The PCI Parameters screen is displayed.
Figure 16: PCI Parameters Screen

3. Select an HBA in the Adapters box. PCI information is displayed in the PCI Info box.
View Revision Information

Figure 17: Info Menu, Revisions Selected

2. Press <R>. The Revisions Info screen is displayed.
Figure 18: Revisions Info Screen

3. Select an HBA in the Adapters box. Revision information is displayed in the Rev Info box.
View Service Parameters

Figure 19: Info Menu, Service Parameters Selected

2. Press <S>. The Service Parameters screen is displayed.
Figure 20: Service Parameters Screen

3. Select an HBA in the Adapters box. Service parameters are displayed in the Service Parameters
box.

View Counter Information
Figure 21: Info Menu, Counters Selected

2. Press <C> The Counters Display screen appears.
Figure 22: Counters Display Screen

3. Select an HBA in the Adapters box. Counter information is displayed in the Counters Info box.
4. To set the counters to zero for all fields, select Clear.
View Link Status Information

Figure 23: Info Menu, Link Status Selected

2. Press <L>. The Link Status screen is displayed.
Figure 24: Link Status Screen

3. Select an HBA in the Adapters box. Link status information is displayed in the Link Status box.
View Link Attention Data

Figure 25: Info Menu

6. Press <A>. The Link Attention Data screen is displayed.
Figure 26: The Link Attention Data Screen

7. Select an HBA in the Adapters box. Link attention data is displayed in the Link Attention box.

View Wakeup Parameters
1. Select the Flash menu.
Figure 27: Flash Menu, Wakeup Parms Selected

2. Press <W>. The Wakeup Parameters screen is displayed.
Figure 28: Wakeup Parameters Screen

3. Select an HBA in the Adapters box. Wakeup parameters are displayed in the Parameters box.
View Service Level Interface Memory (SLIM)

1. Select the Debug menu.
Figure 29: Debug Menu, SLIM Selected

2. Press <S>. The SLIM Memory screen is displayed.
Figure 30: SLIM Memory Screen

3. Select an HBA in the Adapters box.
4. Enter values to specify how SLIM is to be displayed:
• The Offset field represents the starting byte at which information is displayed. An offset
of 0 means information is displayed at the beginning of SLIM. This value is displayed
based on your last session. You can change this value.
• The Length field represents the number of bits that are displayed.
The contents of the SLIM are displayed in the SLIM Contents box.
View Mailbox
Figure 31: Debug Menu, Mailbox Selected

2. Press <M>. The Read Mailbox screen is displayed.
Figure 32: Read Mailbox Screen

3. Select an HBA in the Adapter box. The contents of the mailbox are displayed in the Mailbox
Contents box.

View the Registers
Figure 33: Debug Menu, Registers Selected

2. Press <R>. The Registers screen is displayed.
Figure 34: Registers Screen
Select an HBA in the Adapters box. Register information is displayed in the Registers box.
• Host attention corresponds to 31 bits that describe information that the HBA provides to the
host. In Figure 34 the HBA informs the host when a current mailbox command is finished.
• Chip attention (also known as port attention) corresponds to how the utility gets the HBA's
attention. For the example, the utility informs the HBA when a pending Mailbox Attention
command has an error.
• Host status corresponds to errors and events.
• Host control corresponds to the driver utility.

Update Boot Code
Change the Boot Code State

This procedure allows you to enable or disable boot code (if x86 BootBIOS or OpenBoot is installed).
Figure 35: Flash Menu, Boot Bios Selected

2. Press <B>. The Change Boot BIOS State screen is displayed.
Figure 36: Boot Code Disabled

4. Select the boot code image in the BIOS Images list.
5. Select Change. The boot code is enabled or disabled for the selected HBA. In the following
example, the boot code is enabled.
Figure 37: Boot BIOS Enabled

Note: The Change Boot BIOS State screen is used to enable or disable the boot code. For
x86 BootBIOS, you must also enable the HBA to boot from the SAN using the BIOS
utility.

Load and Update Firmware, Test and Boot Code Files
You can load and update files and images to one or more HBAs using the menu bar. You can also load
and update files using the utility that was loaded with the driver.
Figure 38: Flash Menu, Download Selected

2. Press <D>. The Download Image screen is displayed.
Figure 39: Download Image Screen

3. Select the location of the image file and the HBA to be updated.
4. Select the Reset After Download setting.
• Defaults to Yes. If you are updating a single file to one HBA, keep the default setting.
• If you are updating several HBAs or several files to one HBA, select No.
5. Select OK. The screen closes and the load process begins. Various steps of the download
process are displayed. When the download is finished, the results of the download (success or
error) are displayed.

View and Maintain the Flash Load List
The flash load list enables you to view or delete the images that have been installed on the HBA.
To view the flash load list:
Figure 40: Flash Menu, Display Flash Selected

2. Press <F>. The Flash Load List screen is displayed.
Figure 41: Flash Load List Screen

3. Select the HBA. The flash load list Information is displayed for the selected HBA.
To delete an image from the HBA:
1. Display the flash load list and select an HBA.
2. Select the image you want to delete.
3. Select Delete.
A warning screen is displayed. On the warning screen, select Delete to delete the file, or Cancel
to close the warning screen and cancel the delete.The image selected in the Images box is
deleted.

View and Maintain Configuration Regions
View Configuration Region Information

Figure 42: Flash Menu, Configuration Regions Selected

2. Press <C>. The Configuration Regions screen is displayed.
Figure 43: Configuration Regions Screen

3. Select the HBA and corresponding region.
Region Specifics -
• Region 1 represents Node A configuration
• Region 2 represents Node B configuration
• Region 3 represents Node C configuration
• Region 4 represents the wakeup parameters
• Region 5 represents the default PCI configuration
• Region 6 represents the download 1 (on the Soft Jumpers screen, PCI Alt-1)
• Region 7 represents the download 2 (on the Soft Jumpers screen, PCI Alt-2)
Select Cleanup to clear the first 4 bytes of the specified configuration region in flash so that this
region can be programmed.
4. Enter values in the Hex Input area to specify the configuration region:
• The Offset field represents the starting byte at which information is displayed. An offset
of 0 means information is displayed at the beginning of the region. The value displayed
is based on your last session. You can change this value.
• The Length field represents the number of bits that are displayed.
For example, if you set the Offset value to 100 and the Length field to 100, information for the
selected region is displayed beginning at byte 100 and continuing through the next 100 bytes.

5. Select Read. Region information is displayed in the Region Data box.
Figure 44: Configuration Regions Screen with Information

6. Select Done to close the screen, or proceed to initializing or cleaning a region.
Initialize a Region or Cleaning a Configuration

1. After you have viewed configuration region information and determined that you want to initialize
a region or clean a configuration, make sure the adapter and region are selected in the
Configuration Regions screen.
On the Configuration Regions screen, select Init. The Init Region screen is displayed.
Figure 45: Init Region Screen

2. To initialize, select Init Region.
3. After the configuration is initialized, you can clean the configuration. Select Clean Config.
Set an HBA to Use Soft Jumpers

You can change the state of the adapter soft jumpers, which can be used in place of the physical
jumpers on the adapter.

Figure 46: Flash Menu, Soft Jumpers Selected

2. Press <J>. The Soft Jumpers screen is displayed.
Figure 47: Soft Jumpers Screen

3. Specify the adapter.
4. Specify Hardware Default or Soft Jumpers.
To select or clear an option, tab to it and press the spacebar.
If you select soft jumpers, you must select an alternate PCI region.
• PCI Alt-1 represents Download 1 and Region 6 on the Configuration Regions screen.
• PCI Alt-2 represents Download 2 and Region 7 on the Configuration Regions screen.
5. Select Update, then select Done. The information is updated on the HBA and the screen is
closed.
Use Script Files

Create or Edit Script Files
You can create script files to download images and run scripts from one file. You can download firmware
and boot code images from the Input Script screen.
Use a text editor to create or edit scripts. Script files follow these rules:
• You can run scripts on one adapter in the system or on all adapters in the system.
• n represents the number of adapters and may equal either a numeric value or all.
• r represents the repeat count. You can cause the series of all commands in the script file to
repeat indefinitely by adding the repeat command as the last line of the script file. If you include
this command, press <s> to stop a running script at any time.
• o represents the action option if an error is encountered. 1= stop the test, 2= repeat the test and
3= ignore the error.

For your convenience, this sample script (samplescript.txt) is included in the same directory as the
lp6dutil application:
download a=lp8000 i=c:\temp\dd381a3.awc;
reset n=1 s=0
;reset n=2 s=0
;reset n=all s=0
;pciloopback n=1 r=10 o=1
;pciloopback n=2 r=10 o=2
pciloopback n=all r=50 o=3
Copy this sample script and modify it to fit your needs. Commented lines begin with a semicolon and are
not executed.
Note: All script files end with .txt.
Run Script Files from the Menu Bar

Use the Select Input Script screen to select and run script files. The results are logged in an output file
named lp6dlog.txt and are displayed in the Test Logfile screen.
Figure 48: File Menu, Open Input Script Selected

2. Press <O>. The Select Input Script screen is displayed.
Figure 49: Select Input Script Screen

3. Select the location of the script file.
4. Select OK.

5. The Select Input Script screen closes. All scripts listed in the file are run. Results are logged in
the output file.
To close the screen without selecting an input script, select Cancel.
Run Script Files Using the Command Line

Use the @ command to run scripts files. In the following example, the script1.txt script residing on the
root directory of the A drive would run:
@a:\script1.txt
Note: You can view results (log files) with a text editor by opening the lp6dlog.txt file
(always saved in c:\lp6dutil\lp6dlog.txt), or by using the menu bar. You can change
the name and location of the log file using the command line.
View the Log File

After you have run input scripts, view the test results in the Test Logfile screen. These test results are
logged in an output file named lp6dlog.txt. This file is automatically placed in the c:\lp6dutil directory.
The system appends the lp6dlog.txt file as tests are run and results are logged.
To save the test results and ensure that future test results are logged, copy and rename the lp6dlog.txt
file. The lp6dlog.txt file has a limited scrolling buffer size of approximately 12 screens. Copying and
renaming the .txt file helps you to avoid accumulating a large lp6dlog.txt file.
Figure 50: File Menu, Read Logfile Selected

2. Press <L>. The Test Logfile screen is displayed. Figure 51 below contains tips for using the log
file, rather than an example of the log file itself.
Figure 51: Test Logfile Screen
The most recent test results are displayed at the bottom of the screen. Use the up and down
arrows on your keyboard to scroll through the test results.

3. Select OK. The screen closes.
Note: You can always view test results using a Text Editor. After you copy and rename the
log file however, you cannot view the file in the Test Logfile screen. Renamed log files
must be viewed using a text editor.
Run Diagnostic Tests
Select HBAs to Test

1. Select the Test menu.
Figure 52: Test Menu, Select Adapters Selected

2. Press <A>. The Select Adapters screen is displayed.
Figure 53: Select Adapters Screen

3. Select the HBAs you want to test.
• To select one HBA, press the up and down arrow keys.
• To select all HBAs, select All.
To close the screen without selecting any HBAs, select None.
4. Select OK. The adapters are selected and the screen is closed.

Select Tests
Note: Internal loopback and SRAM tests are not supported for the LP1005DC-CM2 HBA.
Figure 54: Test Menu, Select Tests Selected

2. Press <T>. The Select Tests screen is displayed.
Figure 55: Select Tests Screen

3. Select the tests you want to perform on the HBAs.
• To move through the test list, press <Tab>.
• To select a test, move to the [ ] field for the test and press the spacebar or <Enter>.
• To select all tests within a box, select All.
• To clear all tests (de-select all tests), select None.
To close the screen without selecting any tests, select Cancel.
4. To confirm your options, select OK. Tests are now selected and the screen is closed.
Configure Tests
Note: Internal loopback and SRAM tests are not supported for the LP1005DC-CM2 HBA.
Figure 56: Test Menu, Select Options Selected

2. Press <O>. The Configure Test Parameters screen is displayed.
Figure 57: Configure Test Parameters Screen

3. Select the test to configure. Press <Tab> to select the Test Specific Options box. Press the up
and down arrows keys to select the test you want to configure.
4. If you want the selected test to be repeated if an error is encountered, specify a value in the
Repeat Count field. The repeat count defaults to the last value entered in this field. To change
this value, tab to the Repeat Count field and press <Backspace> to clear the necessary fields.
Enter the new value. To repeat the tests indefinitely, set the count to 0.
5. To change the error action, tab to the Error Action list. Press the up and down arrow keys to
select an error action:
• Stop - stops the test if an error is encountered. This is the default error action.
• Repeat - runs the failed test again.
• Ignore - ignores the error.
6. To confirm your options, select Done.
To cancel out of this screen, press <Esc>.
Start Tests
1. After you have configured the tests, select Start Tests from the Test menu.
Figure 58: Test Menu, Start Tests Selected

2. The Test Results screen is displayed.
Figure 59: Test Results Screen

3. Select Start. All tests are run on all HBAs in the Under Tests box. As applicable, test result
messages are displayed in the Messages box.
To interrupt a test while it is running, select Stop
When all tests are finished, select Done. The screen is closed.
Set or Reset Status Word Mask

The Set/Reset Status Word Bits screen allows you to test the HBA's behavior in various modes.
Figure 60: Adapter Menu, Set Status Word Selected

2. Press S. The Set/Reset Status Word Bits screen is displayed.
Figure 61: Set/Reset Status Word Bits Screen

3. Select the HBA to test. The default is adapter #1.

4. Select the status and mask bits. Tab to the bit and press the spacebar to select or clear it. To
close the screen without changes, select Done.
5. Select Set, then select Done. The bits you have selected are set and the screen is closed.
Debug Tasks
Dump Memory
Figure 62: Debug Menu, Dump Selected

2. Press <D>. A warning screen is displayed.
Figure 63: Dump Memory Warning Screen

3. To continue with the memory dump, on the Warning screen select OK. To close the Warning
screen without dumping memory, select Cancel.
4. The Dump Memory screen is displayed.
Figure 64: Dump Memory Screen

6. Enter values in the Hex Input area to set up the memory dump:
• The Adr field represents the starting address.
• The Len field represents the number of bytes.

7. Select Dump. The memory contents are displayed.
Run Program
The Run Program screen allows you to run firmware test programs, if the firmware test images have
been downloaded. The test results are also displayed in this screen.
Figure 65: Debug Menu, Run Program Selected

2. Press <P>. The Run Program screen is displayed.
Figure 66: Run Program Screen

3. Select an HBA in the Adapter box.
4. Tab to the Program ID Word 1 field. Press <Backspace> to clear the necessary fields. Enter the
firmware test program name.
5. Select Start. Test results display in the Result box.
Run Diagnostics
• Four standard tests can be run using the Test menu (see “Run Diagnostics” on page 97). The
Run Diags screen allows you to run customized tests that must be downloaded to the HBA.
Instructions for creating customized tests are beyond the scope of this manual.
• To download customized tests, use the same procedure for downloading other files and images
(see “Load and Update Firmware, Test and Boot Code Files” on page 85).
The Run Diags screen allows you to run up to five tests at one time.

1. After starting lp6dutil, Select the Debug menu.
Figure 67: Debug Menu, Run Diag Selected

2. Press <I>. The Run Diags screen is displayed.
Figure 68: Run Diags Screen

3. Select an HBA in the Adapter box.
4. Specify values in the Select Common Parameters area. To change a value, tab to the field, and
press <Backspace> to clear the field.
• Repeat Count -
• 0 = Test loops indefinitely until the test is stopped manually.
• X = Enter any other number to indicate the number of times you want tests to be
repeated. If more than one test is specified, you cannot stop a test until all tests
are completed.
• Display Option - A binary code that determines the message information that is printed
in ASCII format to a serial port.
• 00 = No information is printed.
• 1F = All information is printed.
• 03 = Minimal information is printed.
• Request Type -
• 1 = Only one test can be run.
• 2 = Multiple tests (up to five) can be run.
• Entry Count - The number of tests to be run.

• Error Action -
• Stop = Test is stopped if an error is encountered.
• Ignore = Errors are ignored during testing.
• Repeat = If an error is encountered, the test is rerun.
• Loop = If an error is encountered, all tests are rerun.
• Select Parameters for - This field allows you to access a Parameters Selection screen
for the selected test. If multiple tests are downloaded, a down arrow is displayed on the
right side of this box. A separate Parameters Selection screen is displayed for each test.
Parameters Selection screen -
a. Enter values in this screen for the following custom test parameters:
• Version
• Program ID
• Revision Compatibility
• Subtest 3
• Subtest 2
• Subtest 1
• Subtest Selection
b. Select OK on the Parameters Selection screen to set up the test. The screen is closed.
5. On the Run Diags screen, select Start. Results are displayed in the Test Results box. If multiple
tests have run, a vertical scroll bar is displayed on the right side of the box. This indicates that
the box contains additional test results that exceed the display capabilities of the box. Click on
the scroll bar to view additional test results.
Try to Recover HBA

If the HBA cannot be reset, the Try to Recover screen allows you to attempt recovery.
Figure 69: Debug Menu, Recovery Selected

2. Press <E>. All adapters that are active in the system are displayed in the Try to Recover screen:
Figure 70: Try To Recover Screen

3. Select an HBA to recover.
4. Select Proceed to attempt recovery or Done to close the screen.

Emulex Troubleshooting

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Emulex Troubleshooting

Uploaded by

Copyright:

Available Formats

Troubleshooting and

Troubleshooting and Maintenance Manual for Emulex HBAs Page ii

Troubleshooting and Maintenance Manual for Emulex HBAs Page iv

Troubleshooting and Maintenance Manual for Emulex HBAs Page v

Be Informed, Stay Informed

Isolating the Problem

Troubleshooting and Maintenance Manual for Emulex HBAs Page 1

Can’t See Devices or Drives

Troubleshooting and Maintenance Manual for Emulex HBAs Page 3

Out-of-Date Driver Version

Emulex Driver Updates

Troubleshooting and Maintenance Manual for Emulex HBAs Page 4

Out-of-Date Firmware Version

Troubleshooting and Maintenance Manual for Emulex HBAs Page 5

Common LED States

Power Indicator LEDs

Yellow LED Green LED State

Off Off Wake-up failure (dead board)

On Off POST failure (dead board)

Slow blink Off Wake-up failure monitor

Fast blink Off POST failure

Flashing Off POST process in progress

Off On Failure while functioning

On On Failure while functioning

Off Slow blink Normal - link down or not started

Slow blink Slow blink Off-line for download

Flashing Slow blink Restricted offline mode (test active)

Troubleshooting and Maintenance Manual for Emulex HBAs Page 6

Storage and System Supplier-Qualified and Supported HBAs

Emulex Driver Downloads and Documentation

Troubleshooting and Maintenance Manual for Emulex HBAs Page 7

Product Repair and Return

Get an RMA for 10 Products or Fewer

Check on the Status of an RMA for 10 Products or Fewer

Return More than 10 Products or Check RMA Status

Troubleshooting and Maintenance Manual for Emulex HBAs Page 8

Online Support System

Troubleshooting and Maintenance Manual for Emulex HBAs Page 9

Starting HBAnyware from the Desktop

Figure 1: HBAnyware Utility, Discovery Information (Example)

HBAnyware contains five basic elements:

Troubleshooting and Maintenance Manual for Emulex HBAs Page 10

Figure 2: HBAnyware Utility Window with Element Call Outs

The Menu Bar

The Toolbar Buttons

Click Rediscover to refresh the discovery-tree display.

Click Reset to reset the selected HBA.

Sort Toolbar Buttons

Troubleshooting and Maintenance Manual for Emulex HBAs Page 11

Sort by fabric address

Local HBAs only

Figure 3: HBAnyware Utility, Discovery-Tree

The Local host icon.

Troubleshooting and Maintenance Manual for Emulex HBAs Page 12

The Target icon represents connections to individual storage devices.

The LUN icon represents connections to individual LUNs.

Starting the HBAnyware Security Configurator

Troubleshooting and Maintenance Manual for Emulex HBAs Page 13

Figure 4: HBAnyware Security Configurator Discovery Window

2. After discovery is completed, the HBAnyware Security Configurator appears.

Figure 5: HBAnyware Security Configurator, Access Control Group Tab

Troubleshooting and Maintenance Manual for Emulex HBAs Page 14