Emulex Troubleshooting
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Emulex Troubleshooting as PDF for free.
More details
- Words: 23,431
- Pages: 103
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.......................................................................................................................................... 6 Firmware Operation and Port Activity LEDs............................................................. 6 Common LED States ............................................................................................... 6 Power Indicator LEDs........................................................................................ 6 LED Reference.................................................................................................. 6 Emulex Web Site and Emulex Support ................................................................................... 8 Emulex Support Page.............................................................................................. 8 Storage and System Supplier-Qualified and Supported HBAs........................... 8 Emulex Driver Downloads and Documentation.................................................. 8 Emulex Knowledgebase .................................................................................... 8 Product Registration .......................................................................................... 9 Product Repair and Return ...................................................................................... 9 Obtain an RMA for 10 Products or Fewer .......................................................... 9 Check on the Status of an RMA for 10 Products or Fewer................................. 9 Return More than 10 Products, Check RMA Status or Contact Emulex After -Hours, Weekends or Holidays................................................... 10 Online Support System.................................................................................... 10 The HBAnyware Utility........................................................................................................... 11 Introduction............................................................................................................ 11 Starting HBAnyware from the Desktop ............................................................ 11 HBAnyware Window Element Definitions ........................................................ 12 Starting the HBAnyware Security Configurator ................................................ 14 Resetting the HBA ........................................................................................... 16 Determine the HBA Link State - The General Tab ........................................... 16 Enable or Disable Boot Code - Firmware Tab.................................................. 18 Performing Basic Diagnostic Tests .................................................................. 19 Running Advanced Diagnostic Tests ............................................................... 22 Driver-specific Tools .............................................................................................................. 26 Windows-specific Tools.......................................................................................... 26 UNIX-specific Tools ............................................................................................... 27 Unix (Solaris, Linux and HP-UX) ..................................................................... 27 Linux-specific Tools ......................................................................................... 27 The Offline Utility ................................................................................................................... 28 Introduction............................................................................................................ 28 Prerequisites: ........................................................................................................ 28 Hardware Compatibility.......................................................................................... 28 Using the Offline Utility .......................................................................................... 28 Running the Offline Utility from the Command Prompt .................................... 29 Resetting the HBA - reset................................................................................ 29 Viewing HBA Information ....................................................................................... 29 Troubleshooting and Maintenance Manual for Emulex HBAs
Page iii
Viewing the Offline Utility’s Version Information - version ................................ 29 Viewing Vital Product Data - vpd ..................................................................... 30 Viewing Help Syntax for Commands - help ..................................................... 30 Viewing Boot Device Information - 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 ................................................ 32 Firmware and Boot Code Download Commands ................................................... 33 Downloading a File - download ....................................................................... 33 Accessing the Flash Device Directly - directdownload..................................... 34 World Wide Name Commands............................................................................... 34 Writing WWN and Updating NVPARMS - writeWWN....................................... 34 Reading IEEE Information and Saving It to a File - saveWWN........................ 35 Restoring WWN and Updating NVPARMS - restoreWWN ............................... 35 Boot Code Commands .......................................................................................... 35 Enabling or Disabling BootBIOS - enable/disable............................................ 36 Selecting a Boot Device - setbootdevice ......................................................... 36 Selecting One or More Alternate Boot Devices - setAlBoot ............................. 36 Configuration Commands ...................................................................................... 37 Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper ......... 37 Updating Configuration Regions - config ......................................................... 37 Running Diagnostic Tests ...................................................................................... 38 Running External Loopback Test - extloopback ............................................... 38 Running Internal Loopback Test - intloopback ................................................. 38 Running PCI Loopback Test - pciloopback ...................................................... 38 Using Script Files................................................................................................... 39 Creating Script Files ........................................................................................ 39 Script File Commands ..................................................................................... 39 Creating a logfile - logfile................................................................................. 40 Error Codes ........................................................................................................... 42 The lp6dutil Utility .................................................................................................................. 44 Introduction............................................................................................................ 44 Start lp6dutil .................................................................................................... 44 Use the Menu Bar ........................................................................................... 45 Navigation Tips................................................................................................ 45 Use the Command Line................................................................................... 46 Commands and Syntax Reference Table ....................................................... 47 Reset the HBA....................................................................................................... 48 Perform a Warm Start ............................................................................................ 49 Exit the lp6dutil Utility ............................................................................................ 49 View HBA Information............................................................................................ 50 View Adapter Parameters................................................................................ 50 View DC Bridge Information ............................................................................ 50 View VPD Information ..................................................................................... 51 View PCI Information....................................................................................... 52 View Revision Information ............................................................................... 52 View Service Parameters ................................................................................ 53 View Counter Information ................................................................................ 54 View Link Status Information ........................................................................... 54 View Link Attention Data ................................................................................. 55 View Wakeup Parameters ............................................................................... 56 Troubleshooting and Maintenance Manual for Emulex HBAs
Page iv
View Service Level Interface Memory (SLIM) .................................................. 56 View Mailbox ......................................................................................................... 57 View the Registers .......................................................................................... 58 Update Boot Code ................................................................................................. 59 Change the Boot Code State ........................................................................... 59 Load and Update Firmware, Test and Boot Code Files ................................... 60 View and Maintain the Flash Load List ............................................................ 61 View and Maintain Configuration Regions ............................................................. 62 View Configuration Region Information ........................................................... 62 Initialize a Region or Cleaning a Configuration................................................ 63 Set an HBA to Use Soft Jumpers........................................................................... 63 Use Script Files ............................................................................................... 64 View the Log File ................................................................................................... 66 Run Diagnostic Tests ............................................................................................. 67 Select HBAs to Test......................................................................................... 67 Select Tests ..................................................................................................... 68 Configure Tests ............................................................................................... 68 Start Tests ....................................................................................................... 69 Set or Reset Status Word Mask....................................................................... 70 Debug Tasks.......................................................................................................... 71 Dump Memory ................................................................................................. 71 Run Program ................................................................................................... 72 Run Diagnostics .............................................................................................. 72 Try to Recover HBA ........................................................................................ 74 Solaris SFS Driver Console and Log Messages .................................................................. 76 Introduction............................................................................................................ 76 Severity Levels ................................................................................................ 78 Message Log Example .................................................................................... 78 Miscellaneous Events ............................................................................................ 79 Driver Events ......................................................................................................... 79 HBA Initialization Events........................................................................................ 81 Memory Management Events ................................................................................ 82 SLI Events ............................................................................................................. 83 Mailbox Events ...................................................................................................... 85 Node Events .......................................................................................................... 86 Link Events ............................................................................................................ 87 ELS Events............................................................................................................ 88 General I/O Packet Events .................................................................................... 90 FCP Traffic Events................................................................................................. 92 IP Traffic Events .................................................................................................... 92 Solaris SFS Events................................................................................................ 93 IOCTL Events ........................................................................................................ 95 Firmware Download Events ................................................................................... 96 Common Transport Events .................................................................................... 97
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 6)
•
How to contact Emulex Technical Support (see page 8)
•
The Offline Utility (see page 28)
•
The lp6dutil Utility (see page 44)
•
Event trace message and error log information for these Emulex drivers for Windows and UNIX: •
Storport Miniport driver (see page 96)
•
SCSIport Miniport driver (see page 111)
•
FC Port driver (see page 126)
•
lpfc driver for Linux (see page 135)
•
Driver for Solaris (see page 178)
•
Driver for HP-UX (see page 217)
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 the support link, then click the knowledgebase link. 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 (also check for known issues).
•
Verify that you have current switch firmware.
•
Use a good cable.
•
Check HBA and switch LEDs.
•
If system hangs, install the HBA in another server.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 1
•
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 firmware using the Offline Utility ? download (see page 33).
•
Reload firmware using lp6dutil/nr. (see page 60).
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 9 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 by the HBAnyware utility Statistics tab. •
CRC errors, frames out of order, bad frames (replacing the cable may provide a quick fix to these types of problems)
•
Bad HBA optics
See “Product Repair and Return” on page 9 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 2
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 operating 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 the HBAnyware utility 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 16).
•
The cable working 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 the HBAnyware utility (see page 23), the Offline Utility (see page 38), or lp6dutil (see page 72).
•
The HBA optics do not match the cabling. If the HBA is 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: •
All 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 documentation.
•
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 will not be mapped to the operating system. •
On the FC Port driver, automap is off by default. It can be enabled with the HBAnyware utility or elxcfg. See the driver user manual for more information.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 3
•
•
On the Storport Miniport and SCSIport Miniport drivers, automap is on by default. It can be changed with the HBAnyware utility or the driver-specific lputilnt utility. See the driver user manual for more information.
•
On the driver for Solaris, automap is on by default. It can be changed with the HBAnyware utility. See the driver user manual for more information.
•
On the driver for Linux, lpfc_automap is on by default. It can be changed with the HBAnyware utility. 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 the HBAnyware utility to determine discovered targets.
•
•
To determine the number of discovered targets, click on Discovered Elements in the discovery-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 software.
•
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 the Drivers, Downloads and Documentation link to navigate to the Support page. On the Support page, click the link for your operating system. •
The drivers for Windows 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, the HBAnyware utility and a driver-specific utility.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 4
•
•
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. Windows drivers and utilities can be installed manually without using AutoPilot Installer. This is accomplished by following 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 the HBAnyware utility, 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, the HBAnyware utility 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 the HBAnyware utility and driverspecific 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 has stopped flashing.
•
System hangs.
•
Lower than expected performance.
Firmware Updates You can download the latest Emulex firmware from the Emulex Web site. Click the Drivers, Downloads and Documentation link to navigate to the Support page. On the Support page, click the link for your HBA model. A page appears with downloads for firmware, boot code and drivers. Download the firmware, and then use the HBAnyware utility or a driver-specific utility to update the firmware on the HBA.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 5
LEDs Firmware Operation and Port Activity LEDs Emulex HBAs have a POST function. Green and yellow LEDs are visible through openings in the HBA's mounting bracket. These LEDs indicate the conditions and results of the POST function. Green indicates firmware operation, and yellow signifies port activity. Each port has a corresponding set of green and yellow LEDs. HBA LEDs identify possible problems. For more information on LED states, see Table 1 on page 6. LEDs will help you locate: •
Bad cables.
•
Bad transceivers.
•
Bad switches or hub ports.
LEDs will 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 link-up
•
Link-down or HBA waiting
•
Heart-beat indication
Power Indicator LEDs In addition to the firmware operation and port activity LEDs, some HBA models 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 the mounting bracket). If lit, the HBA has power.
•
HBA model LP9002C has an additional LED on the mounting bracket labeled, “Power”. If this LED is lit, 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 6
Table 1: LED Reference Table (Continued) Off
On
Failure while functioning
On
On
Failure while functioning
4-Gb HBAs: 1 blink 2 blinks 3 blinks
On On On
1-Gb link rate - normal, link up 2-Gb link rate - normal, link up 4-Gb link rate - normal, link up
2-Gb HBAs: Slow blink Fast blink
On On
1-Gb link rate - normal, link up 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)
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 7
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).
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 8
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.
Obtain 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: Troubleshooting and Maintenance Manual for Emulex HBAs
Page 9
•
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, Check RMA Status or Contact Emulex After -Hours, Weekends or Holidays Phone to check repair status or return more than 10 products. Also, phone if you have after-hours, holiday or weekend issues. Within the Americas and in Asia: •
E-mail address: [email protected]
•
Telephone: 800-752-9068, option 2.
Within Europe: •
E-mail address: [email protected]
•
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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 10
The HBAnyware Utility Introduction The HBAnyware utility runs on Windows, Solaris and Linux systems. The HBAnyware utility 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 the HBAnyware server has been installed, access the utility from the desktop Start menu. To start HBAnyware for Windows: •
On the Windows desktop, click Start, Programs /HBAnyware.
Initially discovery information for the host appears:
Figure 1: HBAnyware Utility, Discovery Information (Example)
The HBAnyware utility contains five basic elements: the menu bar, the toolbar, the discovery-tree, the property tabs and the status bar (see “HBAnyware Window Element Definitions” on page 12). 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 11
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 exiting HBAnyware, resetting HBAs and sorting items in the discovery-tree. 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 the menu item is checked, 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 Sort discovered HBAs by host name, fabric addresses or local HBAs. By default, HBAs are sorted by host name, with local HBAs appearing first. Show only local or remote HBAs. See page 51 for details on sorting buttons. Troubleshooting and Maintenance Manual for Emulex HBAs
Page 12
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 (local host name, system host names and 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. Other hosts connected to the system.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 13
A green HBA icon with black descriptive text represents an online HBA. A gray HBA icon with red descriptive text represents 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 visible by default. Use the Status Bar item in the View menu to hide the status bar. If checked, the status bar is visible.
Management Mode The management mode determines whether you can manage HBAs on the host. If you cannot manage HBAs from the host, the host has restricted access. 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 (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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 14
To start the HBAnyware Security Configurator for Windows Server 2003 or Windows 2000 Server: 1. On the desktop, click Start, then select Programs/ 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 15
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. Operational indicates that the HBA 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 16
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 selected 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 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:
•
•
The operational state 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 signal 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 17
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.
•
SLI-2 Firmware Name - the name of the SLI-2 firmware overlay.
•
Kernel Version - the version of the firmware responsible for starting the driver
Firmware Buttons •
Update Firmware - click to open the HBAnyware utility Firmware Download dialog box and update firmware. Using the HBAnyware Firmware Download dialog box, browse to the file you wish to download and download the file.
•
Enable/Disable - click to enable or disable the boot code.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 18
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 23)
•
Internal Loopback (see page 23)
•
External Loopback (see page 23)
•
POST (see page 20)
•
Echo Test (see page 24)
•
Quick Test (see page 19)
•
Perform a diagnostic dump (see page 21).
•
View PCI registers and wakeup parameter (see page 22).
•
Control HBA beaconing (see page 21).
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 wish to run the Quick Test.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 19
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 wish 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 20
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 wish 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, the 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 wish to remove existing dump files from your system.
Figure 13: HBAnyware Utility, Diagnostic Dump Dialog Box
4. Click Start Dump.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 21
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 Advanced Diagnostics Test on the Diagnostics tab 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 ECHO test concurrently. If you select External Loopback the ECHO test section is disabled and vice versa.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 22
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 via 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 23
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 wish 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 wish 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 wish to initiate the ECHO Test. 3. Select the Diagnostics tab. Click Advanced Diagnostics Test. Troubleshooting and Maintenance Manual for Emulex HBAs
Page 24
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 wish to test from the tree-view and click Select.
All relevant information for the selected port is automatically added to the Target Identifier section 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 25
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 wish and click Save.
Driver-specific Tools In addition to the HBAnyware utility, 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.
•
Error and event logs (see page 96).
•
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 a tool 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)
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 26
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 page 132).
•
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. .
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 27
The Offline Utility Introduction The Offline Utility is an Emulex program to configure Emulex HBAs before a server operating system is installed or booted.The Offline Utility can be used with Microsoft MS-DOS or FreeDOS. You can use the Offline Utility to do the following: •
View information on Emulex HBAs
•
Reset the HBA
•
Download firmware and boot code files
•
Select a boot device
•
Read and update worldwide names
•
Enable BootBIOS
•
Update configuration regions
•
Set up the HBA to use soft jumpers
•
Run diagnostic tests
•
Read and process script files
Prerequisites: •
The Offline Utility on a bootable media with MS-DOS or FreeDOS.
Hardware Compatibility The Offline Utility supports: •
All current Emulex HBAs
•
Up to 12 HBAs on one system
Using the Offline Utility •
Commands are not case-sensitive.
•
Commands require one space between the command name and the first argument and one space between additional arguments. There is no 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 together for the full WWN.
•
The 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 specifies 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 would need to add max=7 to the end of each command. In this example, if your system had eight HBAs and you entered max=7 at the end of a command, only the first seven HBAs would be seen by the Offline Utility. If your system has more than 530 KB of memory, the Offline Utility can support up to twelve HBAs and no Insufficient Memory message is displayed.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 28
Running the Offline Utility from the Command Prompt Note: You cannot start the Offline Utility at the DOS prompt in Windows.
1. Boot the system with MS-DOS or FreeDOS. 2. You can start the Offline Utility with a valid command or a valid script file name. •
To start the Offline Utility with a command, from the directory where the DOSLPCFG.exe file resides, type:
doslpcfg •
Example of starting the Offline Utility with a reset command:
doslpcfg reset n=2 s=1 •
To start the Offline Utility with a script file name, from the directory where the DOSLPCFG.exe file resides, type:
doslpcfg @<script file name> •
Example of starting the Offline Utility with script1.txt in the c:\test directory:
doslpcfg @C:\test\script1.txt Note: To redirect screen output to a file, add >filename at the end of each command. Example: DOSLPCFG listboot n=1 >result.out Note: For more information on script files, See “Creating Script Files” on page 39 and “Script File Commands” on page 39.
Resetting the HBA - reset This command resets one specific HBA or all HBAs in the system. The s argument determines whether POST is skipped when the HBA(s) restart. Enter s=1 to skip POST or s=0 to run POST. The s argument is not optional for this command. •
To reset the HBA, type:
doslpcfg reset n= 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
Viewing HBA Information Viewing the Offline Utility’s Version Information - version This command displays the Offline Utility’s version information. •
To view this information, type:
doslpcfg version •
Sample response: DOSlpcfg version 1.0a8 released on May 26, 2007.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 29
Viewing Vital Product Data - vpd This command displays the vital product data (VPD) contents of the HBA specified by its number. •
To display VPD, type:
doslpcfg vpd n= •
The following example displays VPD for HBA #2:
doslpcfg vpd n=2 •
Sample response: 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 Help Syntax for Commands - help •
To view all available commands, type:
doslpcfg help or
doslpcfg ? •
To view syntax for a specific command, type:
doslpcfg help or
doslpcfg ? For example,
doslpcfg help download or
doslpcfg ? download both return a response similar to the following: download or download
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 30
Viewing Boot Device Information - 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:
doslpcfg readbootdevice n= •
The following example reads WWN and LUN for HBA #1:
doslpcfg readbootdevice n=1 •
Sample response: 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 indexes (base 1) and their 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. •
To list BootBIOS versions, type:
doslpcfg listboot n= •
The following example lists BootBIOS versions that are loaded on HBA #3:
doslpcfg listboot n=3 •
Sample Response: boot 1 (enabled): RB1.60A7 boot 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), WWN, the functional firmware, the HBA type and possible mailbox errors. •
To list all HBAs in the system, type:
doslpcfg listhba •
Sample response: adapter 1:
10000000
C920A4B3
adapter 2:
WWN err.
adapter 3:
10000000
C920B4C2
Functional FW: CS3.81A3
LP850
adapter 4:
10000000
C920A6D1
Functional FW: CS3.90A4
LP9000
adapter 5:
10000000
C920C6B4
Functional FW: HS1.00A2
LP9802
adapter 6:
10000000
C920E4B6
Functional FW: RS3.90A6
LP950
!!!
Functional FW: ES1.91A0
ReadRev Error
!!!
LP250048-900
LP8000
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 31
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 Nonvolatile WWPN and the WWNN used to identify an HBA in the SAN. The factory-assigned WWN is listed in two parts and is an Institute of Electrical and Electronic Engineers (IEEE) address that cannot be changed in the field. Concatenate 10000000 and the number that follows in the response to obtain the WWN. The non-volatile WWPN and WWNN can be modified using the write WWN command or the scriptWWPN and scriptWWNN commands. For more information on the WWN, see “Writing WWN and Updating NVPARMS - writeWWN” on page 34. If the system does not have any Emulex HBAs installed, error code 45 is returned. •
To show information, type:
doslpcfg listWWN •
Sample response:
adapter 1:
LP250048-900
Config IEEE 10000000
C920B2F4
Non-Volatile WWPN: 2AB148C6 46A2D3F2, WWNN: 4B5C6D8E 12345678
adapter 2:
LPe11000
Config IEEE 10000000
C920DAB8
Non-Volatile WWPN: 5AB0E2F4 B620DAB8, WWNN: 46A0B4DA E2F4C8A0
where the Config IEEE is the original IEEE address from manufacturing, obtained from Configuration Region 16 or 32. The Non-Volatile WWPN and WWNN are the port name and node name (respectively) you have written using the scriptWWPN and scriptWWNN commands (respectively) or the WWNN command.
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 present. If the system does not have any Emulex HBAs installed, error code 45 is returned. •
To list PCI I/O base addresses, type:
doslpcfg listIoBase •
Sample response: 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 firmware versions that are loaded in the flash of the HBA, specified by its number. •
To show revisions, type:
doslpcfg listrev n=
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 32
•
The following example lists information for HBA #3:
doslpcfg listrev n=3 •
Sample response: Chipset Rev: BIU:
1001206D
SM:
00000000
SM FW:
07B21950
ENDEC:
00000000
FW Rev: Current FW:
SLI-2 Overlay
Kernel Rev:
FFB01314
Kernel
LP250048-9001.30a4
Init FW:
LP250048-900Init Load 1.91a0 (ES1.91A0)
SLI-1:
LP250048-900Overlay 1.91a0 (E1M1.91A0)
SLI-2:
LP250048-900Overlay 1.91a0 (E2M1.91A0
FC-PH Version Supported: Highest FC-PH Version Supported = 4.3 Lowest FC-PH Version Supported = 4.3
Firmware and Boot Code Download Commands Downloading a File - download This command downloads a firmware or boot code file to all HBAs of the same name or to a specific HBA. •
To download a firmware image file to all HBAs of the same specified name, type:
doslpcfg download a= i= 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 LP9802 HBAs:
doslpcfg download a=lp9802 i=c:\image\hd100a4.all •
To download a firmware image file to an HBA specified by its number, type:
doslpcfg download n= i= The following example downloads the 1.70a3 BootBIOS file to HBA # 6; in this example, the x86 BootBIOS file is for an LP982 HBA:
doslpcfg download n=6 i=lb170a3.prg
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 33
Accessing the Flash Device Directly - directdownload This command directly accesses the flash device on the HBA without interfacing with 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: •
LPe11002, LPe11000 and LPe1150
•
LP11002, LP11000 and LP1150
•
LP10000ExDC and LP1050Ex
•
LP10000DC and LP10000
•
LP1005DC-CM2
•
LP1050 and LP1050DC
Note: This command cannot be used in a script file.
•
To access the flash device on the HBA directly, type:
doslpcfg directdownload a= i= 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:
doslpcfg directdownload a=lp1050 i=C:\image\mfp191a5.rom The following example accesses the flash device if the Offline Utility cannot detect the HBA type and there is only one single-channel HBA or one dual-channel HBA in the system:
doslpcfg directdownload a=default i=C:\image\tdu191a5.rom Note: The a=default option can be used only if there is 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 1 and word 0 of the WWPN or WWNN via 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 will be used when the HBA is discovered. The HBA will also retain the original WWPN and WWNN in another region of the firmware that can be used to identify the HBA as manufactured. The writeWWN command is not valid in a script file; use the scriptWWPN and scriptWWNN commands instead. Caution: Use the writeWWN command with caution. Do not use the same WWPN or WWNN on more than one HBA in a fabric, or unpredictable results may occur.
•
To modify the WWPN and WWNN, type:
doslpcfg writeWWN n= •
The Offline Utility prompts you to enter a new WWPN or WWNN. The following example writes the WWPN and WWNN for HBA #1.
doslpcfg writeWWN n=1
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 34
Reading IEEE Information and Saving It to a File - saveWWN This command reads the original words 0 and 1 of the IEEE address from manufacturing, obtained 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:
doslpcfg saveWWN n= 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:
doslpcfg 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 this information to update the NVPARMS port name with this IEEE address. The HBA will use this WWPN to identify its port. •
To restore the WWN, type:
doslpcfg restoreWWN n= c=<wwn filename> •
The following example reads the WWN on HBA #4 and updates the NVPARMS with the ctwwn.sav file.
doslpcfg restoreWWN n=4 c=ctwwn.sav
Boot Code Commands To set the boot device with the Offline Utility, perform the following commands in this order: 1. Verify that the BootBIOS is present with the listboot command . (See “Viewing BootBIOS Versions - listboot” on page 31 for more information.) 2. If necessary, enable BootBIOS with the enableboot command . (See See “Enabling or Disabling BootBIOS - enable/disable” on page 36 for more information.) 3. Set the boot device with the setbootdevice command . (See "See “Selecting a Boot Device setbootdevice” on page 36 for more information.) Example:
doslpcfg listboot n=1 Returns the following: boot 1 (enabled): RB1.70A3 boot 2 (disabled): RB1.50A8 doslpcfg enableboot n=1 i=2 doslpcfg setbootdevice n= 1 w0=a1b2c3d4 w1=b946a4e8 l=2 Configure the system BIOS to have the HBA boot device highest in the boot order.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 35
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 indexes (base 1) shown when you run the listboot command. •
To enable BootBIOS, type: doslpcfg enableboot n= i= The following example enables BootBIOS on HBA #6:
doslpcfg enableboot n=6 i=1 •
To disable BootBIOS, type:
doslpcfg disableboot n= The following example disables BootBIOS on HBA #6:
doslpcfg disableboot n=6
Selecting a Boot Device - setbootdevice This command sets up the boot device specified by its WWN, LUN and desired topology. Set t to 1 for Point-to-Point and 0 for Arbitrated Loop. The selected device will boot 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):
doslpcfg setbootdevice n= w0=<WWPN word 0> w1=<WWPN word 1> l= t= Note: The command for specifying the LUN is a lower- or upper-case L.
•
The following example set the boot device on HBA #1, LUN #46 with a desired topology of Arbitrated Loop:
doslpcfg setbootdevice n=1 w0=a1b2c3d4 w1=b946a4e8 l=46 t=0 Note: If PLOGI fails after 50 msecs, the boot will be 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):
doslpcfg setAltBoot n= i= w0=<WWPN word 0> w1=<WWPN word 1> l= Note: The command for specifying the LUN is a lower- or upper-case L.
•
The following example set the alternate boot device on HBA #1, LUN #3:
doslpcfg setAltBoot n=1 i=1 w0=12345678 w1=a842b6 1=3
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 36
Configuration Commands Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper This command allows you to select the default PCI configuration or alternate configurations. Selections are 0 for none, 1 for hardware default or 2 for soft jumper. 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):
doslpcfg jumper n= s=<selection> r= •
The following example sets up HBA #5 to use soft jumpers in region 7:
doslpcfg jumper n=5 s=2 r=7 •
The following example selects the default PCI configuration for HBA #4:
doslpcfg jumper n=4 s=1
Updating Configuration Regions - config To update configuration regions, those configuration regions must be initialized 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):
doslpcfg config a= r= l= c= 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 command for specifying byte length is a lower- or upper-case Byte length is in decimal format.
The following example updates region 6 of all LP9000 HBAs with ctplus1.cfl.
doslpcfg config a=lp9000 r=6 l=68 c=ctplus1.cfl The following example updates region 17of all ABC24-FC56 HBAs with d:\dfplus1.cfl.\:
doslpcfg 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):
doslpcfg config n= r= l= c= The following example updates region 17 of HBA number 4 with heplus1.cf1:
doslpcfg config n=4 r=17 l=100 c=heplus1.cfl The following example updates region 6 of HBA number 2 with d:\dfplus1.cf1:
doslpcfg config n=2 r=6 l=68 c=d:\dfplus1.cfl
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 37
Running Diagnostic Tests Running External Loopback Test - extloopback This command runs the external loopback test. A loopback plug must be installed. 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; enter o=1 for stop, o=2 for repeat or o=3 for ignore. •
To run the external loopback test, type (all on one line):
doslpcfg extloopback n= r= o=
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.......................................................................................................................................... 6 Firmware Operation and Port Activity LEDs............................................................. 6 Common LED States ............................................................................................... 6 Power Indicator LEDs........................................................................................ 6 LED Reference.................................................................................................. 6 Emulex Web Site and Emulex Support ................................................................................... 8 Emulex Support Page.............................................................................................. 8 Storage and System Supplier-Qualified and Supported HBAs........................... 8 Emulex Driver Downloads and Documentation.................................................. 8 Emulex Knowledgebase .................................................................................... 8 Product Registration .......................................................................................... 9 Product Repair and Return ...................................................................................... 9 Obtain an RMA for 10 Products or Fewer .......................................................... 9 Check on the Status of an RMA for 10 Products or Fewer................................. 9 Return More than 10 Products, Check RMA Status or Contact Emulex After -Hours, Weekends or Holidays................................................... 10 Online Support System.................................................................................... 10 The HBAnyware Utility........................................................................................................... 11 Introduction............................................................................................................ 11 Starting HBAnyware from the Desktop ............................................................ 11 HBAnyware Window Element Definitions ........................................................ 12 Starting the HBAnyware Security Configurator ................................................ 14 Resetting the HBA ........................................................................................... 16 Determine the HBA Link State - The General Tab ........................................... 16 Enable or Disable Boot Code - Firmware Tab.................................................. 18 Performing Basic Diagnostic Tests .................................................................. 19 Running Advanced Diagnostic Tests ............................................................... 22 Driver-specific Tools .............................................................................................................. 26 Windows-specific Tools.......................................................................................... 26 UNIX-specific Tools ............................................................................................... 27 Unix (Solaris, Linux and HP-UX) ..................................................................... 27 Linux-specific Tools ......................................................................................... 27 The Offline Utility ................................................................................................................... 28 Introduction............................................................................................................ 28 Prerequisites: ........................................................................................................ 28 Hardware Compatibility.......................................................................................... 28 Using the Offline Utility .......................................................................................... 28 Running the Offline Utility from the Command Prompt .................................... 29 Resetting the HBA - reset................................................................................ 29 Viewing HBA Information ....................................................................................... 29 Troubleshooting and Maintenance Manual for Emulex HBAs
Page iii
Viewing the Offline Utility’s Version Information - version ................................ 29 Viewing Vital Product Data - vpd ..................................................................... 30 Viewing Help Syntax for Commands - help ..................................................... 30 Viewing Boot Device Information - 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 ................................................ 32 Firmware and Boot Code Download Commands ................................................... 33 Downloading a File - download ....................................................................... 33 Accessing the Flash Device Directly - directdownload..................................... 34 World Wide Name Commands............................................................................... 34 Writing WWN and Updating NVPARMS - writeWWN....................................... 34 Reading IEEE Information and Saving It to a File - saveWWN........................ 35 Restoring WWN and Updating NVPARMS - restoreWWN ............................... 35 Boot Code Commands .......................................................................................... 35 Enabling or Disabling BootBIOS - enable/disable............................................ 36 Selecting a Boot Device - setbootdevice ......................................................... 36 Selecting One or More Alternate Boot Devices - setAlBoot ............................. 36 Configuration Commands ...................................................................................... 37 Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper ......... 37 Updating Configuration Regions - config ......................................................... 37 Running Diagnostic Tests ...................................................................................... 38 Running External Loopback Test - extloopback ............................................... 38 Running Internal Loopback Test - intloopback ................................................. 38 Running PCI Loopback Test - pciloopback ...................................................... 38 Using Script Files................................................................................................... 39 Creating Script Files ........................................................................................ 39 Script File Commands ..................................................................................... 39 Creating a logfile - logfile................................................................................. 40 Error Codes ........................................................................................................... 42 The lp6dutil Utility .................................................................................................................. 44 Introduction............................................................................................................ 44 Start lp6dutil .................................................................................................... 44 Use the Menu Bar ........................................................................................... 45 Navigation Tips................................................................................................ 45 Use the Command Line................................................................................... 46 Commands and Syntax Reference Table ....................................................... 47 Reset the HBA....................................................................................................... 48 Perform a Warm Start ............................................................................................ 49 Exit the lp6dutil Utility ............................................................................................ 49 View HBA Information............................................................................................ 50 View Adapter Parameters................................................................................ 50 View DC Bridge Information ............................................................................ 50 View VPD Information ..................................................................................... 51 View PCI Information....................................................................................... 52 View Revision Information ............................................................................... 52 View Service Parameters ................................................................................ 53 View Counter Information ................................................................................ 54 View Link Status Information ........................................................................... 54 View Link Attention Data ................................................................................. 55 View Wakeup Parameters ............................................................................... 56 Troubleshooting and Maintenance Manual for Emulex HBAs
Page iv
View Service Level Interface Memory (SLIM) .................................................. 56 View Mailbox ......................................................................................................... 57 View the Registers .......................................................................................... 58 Update Boot Code ................................................................................................. 59 Change the Boot Code State ........................................................................... 59 Load and Update Firmware, Test and Boot Code Files ................................... 60 View and Maintain the Flash Load List ............................................................ 61 View and Maintain Configuration Regions ............................................................. 62 View Configuration Region Information ........................................................... 62 Initialize a Region or Cleaning a Configuration................................................ 63 Set an HBA to Use Soft Jumpers........................................................................... 63 Use Script Files ............................................................................................... 64 View the Log File ................................................................................................... 66 Run Diagnostic Tests ............................................................................................. 67 Select HBAs to Test......................................................................................... 67 Select Tests ..................................................................................................... 68 Configure Tests ............................................................................................... 68 Start Tests ....................................................................................................... 69 Set or Reset Status Word Mask....................................................................... 70 Debug Tasks.......................................................................................................... 71 Dump Memory ................................................................................................. 71 Run Program ................................................................................................... 72 Run Diagnostics .............................................................................................. 72 Try to Recover HBA ........................................................................................ 74 Solaris SFS Driver Console and Log Messages .................................................................. 76 Introduction............................................................................................................ 76 Severity Levels ................................................................................................ 78 Message Log Example .................................................................................... 78 Miscellaneous Events ............................................................................................ 79 Driver Events ......................................................................................................... 79 HBA Initialization Events........................................................................................ 81 Memory Management Events ................................................................................ 82 SLI Events ............................................................................................................. 83 Mailbox Events ...................................................................................................... 85 Node Events .......................................................................................................... 86 Link Events ............................................................................................................ 87 ELS Events............................................................................................................ 88 General I/O Packet Events .................................................................................... 90 FCP Traffic Events................................................................................................. 92 IP Traffic Events .................................................................................................... 92 Solaris SFS Events................................................................................................ 93 IOCTL Events ........................................................................................................ 95 Firmware Download Events ................................................................................... 96 Common Transport Events .................................................................................... 97
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 6)
•
How to contact Emulex Technical Support (see page 8)
•
The Offline Utility (see page 28)
•
The lp6dutil Utility (see page 44)
•
Event trace message and error log information for these Emulex drivers for Windows and UNIX: •
Storport Miniport driver (see page 96)
•
SCSIport Miniport driver (see page 111)
•
FC Port driver (see page 126)
•
lpfc driver for Linux (see page 135)
•
Driver for Solaris (see page 178)
•
Driver for HP-UX (see page 217)
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 the support link, then click the knowledgebase link. 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 (also check for known issues).
•
Verify that you have current switch firmware.
•
Use a good cable.
•
Check HBA and switch LEDs.
•
If system hangs, install the HBA in another server.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 1
•
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 firmware using the Offline Utility ? download (see page 33).
•
Reload firmware using lp6dutil/nr. (see page 60).
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 9 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 by the HBAnyware utility Statistics tab. •
CRC errors, frames out of order, bad frames (replacing the cable may provide a quick fix to these types of problems)
•
Bad HBA optics
See “Product Repair and Return” on page 9 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 2
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 operating 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 the HBAnyware utility 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 16).
•
The cable working 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 the HBAnyware utility (see page 23), the Offline Utility (see page 38), or lp6dutil (see page 72).
•
The HBA optics do not match the cabling. If the HBA is 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: •
All 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 documentation.
•
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 will not be mapped to the operating system. •
On the FC Port driver, automap is off by default. It can be enabled with the HBAnyware utility or elxcfg. See the driver user manual for more information.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 3
•
•
On the Storport Miniport and SCSIport Miniport drivers, automap is on by default. It can be changed with the HBAnyware utility or the driver-specific lputilnt utility. See the driver user manual for more information.
•
On the driver for Solaris, automap is on by default. It can be changed with the HBAnyware utility. See the driver user manual for more information.
•
On the driver for Linux, lpfc_automap is on by default. It can be changed with the HBAnyware utility. 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 the HBAnyware utility to determine discovered targets.
•
•
To determine the number of discovered targets, click on Discovered Elements in the discovery-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 software.
•
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 the Drivers, Downloads and Documentation link to navigate to the Support page. On the Support page, click the link for your operating system. •
The drivers for Windows 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, the HBAnyware utility and a driver-specific utility.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 4
•
•
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. Windows drivers and utilities can be installed manually without using AutoPilot Installer. This is accomplished by following 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 the HBAnyware utility, 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, the HBAnyware utility 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 the HBAnyware utility and driverspecific 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 has stopped flashing.
•
System hangs.
•
Lower than expected performance.
Firmware Updates You can download the latest Emulex firmware from the Emulex Web site. Click the Drivers, Downloads and Documentation link to navigate to the Support page. On the Support page, click the link for your HBA model. A page appears with downloads for firmware, boot code and drivers. Download the firmware, and then use the HBAnyware utility or a driver-specific utility to update the firmware on the HBA.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 5
LEDs Firmware Operation and Port Activity LEDs Emulex HBAs have a POST function. Green and yellow LEDs are visible through openings in the HBA's mounting bracket. These LEDs indicate the conditions and results of the POST function. Green indicates firmware operation, and yellow signifies port activity. Each port has a corresponding set of green and yellow LEDs. HBA LEDs identify possible problems. For more information on LED states, see Table 1 on page 6. LEDs will help you locate: •
Bad cables.
•
Bad transceivers.
•
Bad switches or hub ports.
LEDs will 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 link-up
•
Link-down or HBA waiting
•
Heart-beat indication
Power Indicator LEDs In addition to the firmware operation and port activity LEDs, some HBA models 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 the mounting bracket). If lit, the HBA has power.
•
HBA model LP9002C has an additional LED on the mounting bracket labeled, “Power”. If this LED is lit, 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 6
Table 1: LED Reference Table (Continued) Off
On
Failure while functioning
On
On
Failure while functioning
4-Gb HBAs: 1 blink 2 blinks 3 blinks
On On On
1-Gb link rate - normal, link up 2-Gb link rate - normal, link up 4-Gb link rate - normal, link up
2-Gb HBAs: Slow blink Fast blink
On On
1-Gb link rate - normal, link up 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)
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 7
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).
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 8
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.
Obtain 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: Troubleshooting and Maintenance Manual for Emulex HBAs
Page 9
•
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, Check RMA Status or Contact Emulex After -Hours, Weekends or Holidays Phone to check repair status or return more than 10 products. Also, phone if you have after-hours, holiday or weekend issues. Within the Americas and in Asia: •
E-mail address: [email protected]
•
Telephone: 800-752-9068, option 2.
Within Europe: •
E-mail address: [email protected]
•
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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 10
The HBAnyware Utility Introduction The HBAnyware utility runs on Windows, Solaris and Linux systems. The HBAnyware utility 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 the HBAnyware server has been installed, access the utility from the desktop Start menu. To start HBAnyware for Windows: •
On the Windows desktop, click Start, Programs /HBAnyware.
Initially discovery information for the host appears:
Figure 1: HBAnyware Utility, Discovery Information (Example)
The HBAnyware utility contains five basic elements: the menu bar, the toolbar, the discovery-tree, the property tabs and the status bar (see “HBAnyware Window Element Definitions” on page 12). 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 11
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 exiting HBAnyware, resetting HBAs and sorting items in the discovery-tree. 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 the menu item is checked, 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 Sort discovered HBAs by host name, fabric addresses or local HBAs. By default, HBAs are sorted by host name, with local HBAs appearing first. Show only local or remote HBAs. See page 51 for details on sorting buttons. Troubleshooting and Maintenance Manual for Emulex HBAs
Page 12
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 (local host name, system host names and 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. Other hosts connected to the system.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 13
A green HBA icon with black descriptive text represents an online HBA. A gray HBA icon with red descriptive text represents 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 visible by default. Use the Status Bar item in the View menu to hide the status bar. If checked, the status bar is visible.
Management Mode The management mode determines whether you can manage HBAs on the host. If you cannot manage HBAs from the host, the host has restricted access. 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 (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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 14
To start the HBAnyware Security Configurator for Windows Server 2003 or Windows 2000 Server: 1. On the desktop, click Start, then select Programs/ 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 15
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. Operational indicates that the HBA 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 16
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 selected 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 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:
•
•
The operational state 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 signal 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 17
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.
•
SLI-2 Firmware Name - the name of the SLI-2 firmware overlay.
•
Kernel Version - the version of the firmware responsible for starting the driver
Firmware Buttons •
Update Firmware - click to open the HBAnyware utility Firmware Download dialog box and update firmware. Using the HBAnyware Firmware Download dialog box, browse to the file you wish to download and download the file.
•
Enable/Disable - click to enable or disable the boot code.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 18
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 23)
•
Internal Loopback (see page 23)
•
External Loopback (see page 23)
•
POST (see page 20)
•
Echo Test (see page 24)
•
Quick Test (see page 19)
•
Perform a diagnostic dump (see page 21).
•
View PCI registers and wakeup parameter (see page 22).
•
Control HBA beaconing (see page 21).
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 wish to run the Quick Test.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 19
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 wish 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 20
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 wish 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, the 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 wish to remove existing dump files from your system.
Figure 13: HBAnyware Utility, Diagnostic Dump Dialog Box
4. Click Start Dump.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 21
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 Advanced Diagnostics Test on the Diagnostics tab 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 ECHO test concurrently. If you select External Loopback the ECHO test section is disabled and vice versa.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 22
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 via 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.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 23
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 wish 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 wish 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 wish to initiate the ECHO Test. 3. Select the Diagnostics tab. Click Advanced Diagnostics Test. Troubleshooting and Maintenance Manual for Emulex HBAs
Page 24
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 wish to test from the tree-view and click Select.
All relevant information for the selected port is automatically added to the Target Identifier section 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
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 25
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 wish and click Save.
Driver-specific Tools In addition to the HBAnyware utility, 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.
•
Error and event logs (see page 96).
•
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 a tool 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)
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 26
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 page 132).
•
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. .
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 27
The Offline Utility Introduction The Offline Utility is an Emulex program to configure Emulex HBAs before a server operating system is installed or booted.The Offline Utility can be used with Microsoft MS-DOS or FreeDOS. You can use the Offline Utility to do the following: •
View information on Emulex HBAs
•
Reset the HBA
•
Download firmware and boot code files
•
Select a boot device
•
Read and update worldwide names
•
Enable BootBIOS
•
Update configuration regions
•
Set up the HBA to use soft jumpers
•
Run diagnostic tests
•
Read and process script files
Prerequisites: •
The Offline Utility on a bootable media with MS-DOS or FreeDOS.
Hardware Compatibility The Offline Utility supports: •
All current Emulex HBAs
•
Up to 12 HBAs on one system
Using the Offline Utility •
Commands are not case-sensitive.
•
Commands require one space between the command name and the first argument and one space between additional arguments. There is no 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 together for the full WWN.
•
The 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 specifies 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 would need to add max=7 to the end of each command. In this example, if your system had eight HBAs and you entered max=7 at the end of a command, only the first seven HBAs would be seen by the Offline Utility. If your system has more than 530 KB of memory, the Offline Utility can support up to twelve HBAs and no Insufficient Memory message is displayed.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 28
Running the Offline Utility from the Command Prompt Note: You cannot start the Offline Utility at the DOS prompt in Windows.
1. Boot the system with MS-DOS or FreeDOS. 2. You can start the Offline Utility with a valid command or a valid script file name. •
To start the Offline Utility with a command, from the directory where the DOSLPCFG.exe file resides, type:
doslpcfg
Example of starting the Offline Utility with a reset command:
doslpcfg reset n=2 s=1 •
To start the Offline Utility with a script file name, from the directory where the DOSLPCFG.exe file resides, type:
doslpcfg @<script file name> •
Example of starting the Offline Utility with script1.txt in the c:\test directory:
doslpcfg @C:\test\script1.txt Note: To redirect screen output to a file, add >filename at the end of each command. Example: DOSLPCFG listboot n=1 >result.out Note: For more information on script files, See “Creating Script Files” on page 39 and “Script File Commands” on page 39.
Resetting the HBA - reset This command resets one specific HBA or all HBAs in the system. The s argument determines whether POST is skipped when the HBA(s) restart. Enter s=1 to skip POST or s=0 to run POST. The s argument is not optional for this command. •
To reset the HBA, type:
doslpcfg reset n=
The following example resets all HBAs in the system and runs POST when the HBAs restart.
doslpcfg reset n=all s=0
Viewing HBA Information Viewing the Offline Utility’s Version Information - version This command displays the Offline Utility’s version information. •
To view this information, type:
doslpcfg version •
Sample response: DOSlpcfg version 1.0a8 released on May 26, 2007.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 29
Viewing Vital Product Data - vpd This command displays the vital product data (VPD) contents of the HBA specified by its number. •
To display VPD, type:
doslpcfg vpd n=
The following example displays VPD for HBA #2:
doslpcfg vpd n=2 •
Sample response: 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 Help Syntax for Commands - help •
To view all available commands, type:
doslpcfg help or
doslpcfg ? •
To view syntax for a specific command, type:
doslpcfg help
doslpcfg ?
doslpcfg help download or
doslpcfg ? download both return a response similar to the following: download
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 30
Viewing Boot Device Information - 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:
doslpcfg readbootdevice n=
The following example reads WWN and LUN for HBA #1:
doslpcfg readbootdevice n=1 •
Sample response: 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 indexes (base 1) and their 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. •
To list BootBIOS versions, type:
doslpcfg listboot n=
The following example lists BootBIOS versions that are loaded on HBA #3:
doslpcfg listboot n=3 •
Sample Response: boot 1 (enabled): RB1.60A7 boot 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), WWN, the functional firmware, the HBA type and possible mailbox errors. •
To list all HBAs in the system, type:
doslpcfg listhba •
Sample response: adapter 1:
10000000
C920A4B3
adapter 2:
WWN err.
adapter 3:
10000000
C920B4C2
Functional FW: CS3.81A3
LP850
adapter 4:
10000000
C920A6D1
Functional FW: CS3.90A4
LP9000
adapter 5:
10000000
C920C6B4
Functional FW: HS1.00A2
LP9802
adapter 6:
10000000
C920E4B6
Functional FW: RS3.90A6
LP950
!!!
Functional FW: ES1.91A0
ReadRev Error
!!!
LP250048-900
LP8000
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 31
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 Nonvolatile WWPN and the WWNN used to identify an HBA in the SAN. The factory-assigned WWN is listed in two parts and is an Institute of Electrical and Electronic Engineers (IEEE) address that cannot be changed in the field. Concatenate 10000000 and the number that follows in the response to obtain the WWN. The non-volatile WWPN and WWNN can be modified using the write WWN command or the scriptWWPN and scriptWWNN commands. For more information on the WWN, see “Writing WWN and Updating NVPARMS - writeWWN” on page 34. If the system does not have any Emulex HBAs installed, error code 45 is returned. •
To show information, type:
doslpcfg listWWN •
Sample response:
adapter 1:
LP250048-900
Config IEEE 10000000
C920B2F4
Non-Volatile WWPN: 2AB148C6 46A2D3F2, WWNN: 4B5C6D8E 12345678
adapter 2:
LPe11000
Config IEEE 10000000
C920DAB8
Non-Volatile WWPN: 5AB0E2F4 B620DAB8, WWNN: 46A0B4DA E2F4C8A0
where the Config IEEE is the original IEEE address from manufacturing, obtained from Configuration Region 16 or 32. The Non-Volatile WWPN and WWNN are the port name and node name (respectively) you have written using the scriptWWPN and scriptWWNN commands (respectively) or the WWNN command.
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 present. If the system does not have any Emulex HBAs installed, error code 45 is returned. •
To list PCI I/O base addresses, type:
doslpcfg listIoBase •
Sample response: 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 firmware versions that are loaded in the flash of the HBA, specified by its number. •
To show revisions, type:
doslpcfg listrev n=
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 32
•
The following example lists information for HBA #3:
doslpcfg listrev n=3 •
Sample response: Chipset Rev: BIU:
1001206D
SM:
00000000
SM FW:
07B21950
ENDEC:
00000000
FW Rev: Current FW:
SLI-2 Overlay
Kernel Rev:
FFB01314
Kernel
LP250048-9001.30a4
Init FW:
LP250048-900Init Load 1.91a0 (ES1.91A0)
SLI-1:
LP250048-900Overlay 1.91a0 (E1M1.91A0)
SLI-2:
LP250048-900Overlay 1.91a0 (E2M1.91A0
FC-PH Version Supported: Highest FC-PH Version Supported = 4.3 Lowest FC-PH Version Supported = 4.3
Firmware and Boot Code Download Commands Downloading a File - download This command downloads a firmware or boot code file to all HBAs of the same name or to a specific HBA. •
To download a firmware image file to all HBAs of the same specified name, type:
doslpcfg download a=
The following example downloads the hd100a4.all firmware file to all LP9802 HBAs:
doslpcfg download a=lp9802 i=c:\image\hd100a4.all •
To download a firmware image file to an HBA specified by its number, type:
doslpcfg download n=
doslpcfg download n=6 i=lb170a3.prg
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 33
Accessing the Flash Device Directly - directdownload This command directly accesses the flash device on the HBA without interfacing with 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: •
LPe11002, LPe11000 and LPe1150
•
LP11002, LP11000 and LP1150
•
LP10000ExDC and LP1050Ex
•
LP10000DC and LP10000
•
LP1005DC-CM2
•
LP1050 and LP1050DC
Note: This command cannot be used in a script file.
•
To access the flash device on the HBA directly, type:
doslpcfg directdownload a=
The following example accesses the flash device on an LP1050 HBA:
doslpcfg directdownload a=lp1050 i=C:\image\mfp191a5.rom The following example accesses the flash device if the Offline Utility cannot detect the HBA type and there is only one single-channel HBA or one dual-channel HBA in the system:
doslpcfg directdownload a=default i=C:\image\tdu191a5.rom Note: The a=default option can be used only if there is 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 1 and word 0 of the WWPN or WWNN via 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 will be used when the HBA is discovered. The HBA will also retain the original WWPN and WWNN in another region of the firmware that can be used to identify the HBA as manufactured. The writeWWN command is not valid in a script file; use the scriptWWPN and scriptWWNN commands instead. Caution: Use the writeWWN command with caution. Do not use the same WWPN or WWNN on more than one HBA in a fabric, or unpredictable results may occur.
•
To modify the WWPN and WWNN, type:
doslpcfg writeWWN n=
The Offline Utility prompts you to enter a new WWPN or WWNN. The following example writes the WWPN and WWNN for HBA #1.
doslpcfg writeWWN n=1
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 34
Reading IEEE Information and Saving It to a File - saveWWN This command reads the original words 0 and 1 of the IEEE address from manufacturing, obtained 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:
doslpcfg saveWWN n=
The following example reads the configuration region information on HBA #4 and saves it to the contents of the ctwwn.sav file:
doslpcfg 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 this information to update the NVPARMS port name with this IEEE address. The HBA will use this WWPN to identify its port. •
To restore the WWN, type:
doslpcfg restoreWWN n=
The following example reads the WWN on HBA #4 and updates the NVPARMS with the ctwwn.sav file.
doslpcfg restoreWWN n=4 c=ctwwn.sav
Boot Code Commands To set the boot device with the Offline Utility, perform the following commands in this order: 1. Verify that the BootBIOS is present with the listboot command . (See “Viewing BootBIOS Versions - listboot” on page 31 for more information.) 2. If necessary, enable BootBIOS with the enableboot command . (See See “Enabling or Disabling BootBIOS - enable/disable” on page 36 for more information.) 3. Set the boot device with the setbootdevice command . (See "See “Selecting a Boot Device setbootdevice” on page 36 for more information.) Example:
doslpcfg listboot n=1 Returns the following: boot 1 (enabled): RB1.70A3 boot 2 (disabled): RB1.50A8 doslpcfg enableboot n=1 i=2 doslpcfg setbootdevice n= 1 w0=a1b2c3d4 w1=b946a4e8 l=2 Configure the system BIOS to have the HBA boot device highest in the boot order.
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 35
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 indexes (base 1) shown when you run the listboot command. •
To enable BootBIOS, type: doslpcfg enableboot n=
doslpcfg enableboot n=6 i=1 •
To disable BootBIOS, type:
doslpcfg disableboot n=
doslpcfg disableboot n=6
Selecting a Boot Device - setbootdevice This command sets up the boot device specified by its WWN, LUN and desired topology. Set t to 1 for Point-to-Point and 0 for Arbitrated Loop. The selected device will boot 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):
doslpcfg setbootdevice n=
•
The following example set the boot device on HBA #1, LUN #46 with a desired topology of Arbitrated Loop:
doslpcfg setbootdevice n=1 w0=a1b2c3d4 w1=b946a4e8 l=46 t=0 Note: If PLOGI fails after 50 msecs, the boot will be 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):
doslpcfg setAltBoot n=
•
The following example set the alternate boot device on HBA #1, LUN #3:
doslpcfg setAltBoot n=1 i=1 w0=12345678 w1=a842b6 1=3
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 36
Configuration Commands Setting the HBA to Use Soft Jumpers or the Hardware Default - jumper This command allows you to select the default PCI configuration or alternate configurations. Selections are 0 for none, 1 for hardware default or 2 for soft jumper. 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):
doslpcfg jumper n=
The following example sets up HBA #5 to use soft jumpers in region 7:
doslpcfg jumper n=5 s=2 r=7 •
The following example selects the default PCI configuration for HBA #4:
doslpcfg jumper n=4 s=1
Updating Configuration Regions - config To update configuration regions, those configuration regions must be initialized 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):
doslpcfg config a=
The following example updates region 6 of all LP9000 HBAs with ctplus1.cfl.
doslpcfg config a=lp9000 r=6 l=68 c=ctplus1.cfl The following example updates region 17of all ABC24-FC56 HBAs with d:\dfplus1.cfl.\:
doslpcfg 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):
doslpcfg config n=
doslpcfg config n=4 r=17 l=100 c=heplus1.cfl The following example updates region 6 of HBA number 2 with d:\dfplus1.cf1:
doslpcfg config n=2 r=6 l=68 c=d:\dfplus1.cfl
Troubleshooting and Maintenance Manual for Emulex HBAs
Page 37
Running Diagnostic Tests Running External Loopback Test - extloopback This command runs the external loopback test. A loopback plug must be installed. 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; enter o=1 for stop, o=2 for repeat or o=3 for ignore. •
To run the external loopback test, type (all on one line):
doslpcfg extloopback n=
Related Documents
Emulex Troubleshooting
October 2019 5
Troubleshooting
December 2019 34
Troubleshooting
June 2020 23
Troubleshooting
May 2020 25
Emulex Uc13 Configuration
May 2020 4