Chapter 11: Troubleshooting

Your system might operate in an unexpected manner in some circumstances. This chapter explains many of these circumstances and offers one or more workarounds for each situation.

11.1 General Situations

The following table lists general situations and their resolution.

Table 5: General Situations

Situation

Resolution

After the Emulex HBA Manager application is installed and started, the status bar displays the message Initializing discovery engine..., but after a delay, nothing is displayed in the discovery-tree.

It is possible that the discovery server was not installed properly and therefore is not running. Try uninstalling and reinstalling the Emulex HBA Manager application package.

The FC link fails to come up.

Verify that the adapter port is attached to a port that supports a compatible link speed. For example, verify that an 8Gb/s adapter is not attempting to connect to a 1Gb/s device or that a 16Gb/s adapter is not attempting to connect to a 1Gb/s or 2Gb/s device.

The other utilities can be installed, but the Emulex HBA Manager application cannot be installed.

You have attempted to install the utilities before installing the Emulex driver.

Perform the installation tasks in the following order:

1.    Install the Emulex driver (refer to the installation section of the driver manual).

2.    Install the utilities. See Chapter 2, Installing and Uninstalling the Emulex HBA Manager Application Components, for more information.

An operating error, such as when the system stops responding, occurs when attempting to run the Emulex HBA Manager application.

Reboot the system.

Unwanted remote servers appear in the Emulex HBA Manager application.

To prevent remote servers from appearing in the Emulex HBA Manager application, perform one of the following actions on the remote systems:

n    In Windows, disable the Emulex HBA Manager application service.

n    In Linux, stop the elxhbamgr daemon by running the following script:

/usr/sbin/ocmanager/stop_ocmanager

NOTE: Disabling this service or process prevents the local servers from being seen remotely.

If Help > Contents is selected in the Emulex HBA Manager application, the online help is not opened in a web browser. The index.htm file can be opened in a text editor (displaying HTML code) or in some other application.

This situation occurs when the operating system has associated .html files with an application other than a web browser.

On Windows systems, this issue can be fixed using the following steps:

1.    In Windows Explorer, navigate to the following directory:
C:\Program Files\Emulex\Util\OCManager\OCManager_help\

2.    Right-click on index.html.

3.    Select Open With > Choose default program.

4.    Select a web browser, such as Internet Explorer.

5.    Check Always use the selected program to open this kind of file.

6.    Click OK.

On Linux, the preceding steps are very similar, with the index.html file located in the /usr/sbin/ocmanager/ocmanager_help directory.

Selecting Help > Contents in the Emulex HBA Manager application in a Firefox browser results in an unresponsive page, and the help contents are not seen.

Turn off the strict cross-origin policy (enabled by default) in the Firefox configuration by performing the following steps:

1.    Open a new tab and enter about:config in the address bar.

2.    Search for the strict_origin_policy preference.

3.    Toggle the security.fileuri.strict_origin_policy value to false (off).

4.    Close the browser.


11.2 Firmware Update Error Messages

The following table lists error messages that pertain to firmware updates.

Table 6: Firmware Update Situations

Message

Resolution

Incompatible object

A component of the firmware image is incompatible with the HBA. Install a later version of the firmware from www.broadcom.com.

Firmware incompatible with flash part

A new flash device on the HBA is not supported by the version of firmware you are installing. Install a later version of firmware from www.broadcom.com.

Incorrect ASIC version

The firmware you are installing does not support the HBA. Install a firmware image that supports the HBA from www.broadcom.com.

Incompatible object - general error

The firmware image has an unknown error. Contact Broadcom Technical Support.


11.3 Emulex Driver for Linux and Emulex HBA Manager Application Situations

The following table lists possible situations and resolutions involving the Emulex HBA Manager application for Linux.

Table 7: Situations Involving the Emulex HBA Manager Application for Linux

Situation

Resolution

The Emulex HBA Manager application software package is installed, but an error message says: inserv Service Elxlpfc has to be enabled for service ElxDiscSrvinserv: exiting now/sbin/ inserv failed exit code 1.

Reinstall the driver for Linux with the elx_lpfc_install script.

rmmod fails to unload the driver because the device or resource is busy. This situation occurs when you attempt to remove the driver without first stopping the Emulex HBA Manager application, when the Emulex HBA Manager application is installed and running, or when FC disks connected to an Emulex adapter are mounted.

Stop the Emulex HBA Manager application before attempting to unload the driver. The script is located in the /usr/sbin/ocmanager directory.

1.    Type the following command:

./stop_ocmanager

2.    Unmount any disks connected to the adapter.

3.    Unload the driver.

4.    Type the following command:

rmmod lpfc

The driver uninstallation fails. The elx_lpfc_install --uninstall script fails with an error.

Try the following solutions:

n    Uninstall the Emulex HBA Manager application by running the /uninstall script from the Emulex HBA Manager application installation directory.

n    Unmount all FC disk drives.

n    Unload the FC driver.

The Emulex HBA Manager application cannot detect any adapters.

Try the following solutions:

n    Perform an lsmod to see if the Emulex drivers are loaded. On the command line, look for an error message stating that the LPFC driver is not loaded. If you find such a message, perform an lsmod of the FC driver and restart the Emulex HBA Manager application.

n    Exit the Emulex HBA Manager application and run the following scripts in this order:

1.    /usr/sbin/ocmanager/stop_ocmanager – Stops the Emulex HBA Manager application daemons.

2.    /usr/sbin/ocmanager/start_ocmanager – Starts the Emulex HBA Manager application daemons.

3.    /usr/sbin/ocmanager/ocmanager – Starts the Emulex HBA Manager application GUI.

The adapters should be visible. If they are not visible, reboot your system.

The Emulex HBA Manager application cannot see new LUNs.

Try the following procedure:

1.    Click Refresh LUNs in the toolbar.

2.    Exit the Emulex HBA Manager application and restart it. If new LUNs are visible, you are finished.

If that does not work, try the following procedure:

1.    Exit the Emulex HBA Manager application.

2.    Navigate to /usr/sbin/ocmanager.

3.    Run ./stop_ocmanager to stop both the elxhbamgr and elxdiscovery processes.

4.    Run ./start_ocmanager and ./start_elxdiscovery to restart both processes.

5.    Start the Emulex HBA Manager application.


11.4 vPorts and Emulex HBA Manager Application Situations

The following table lists possible vPort situations and their resolution.

Table 8: Situations Involving vPorts and the Emulex HBA Manager Application

Situation

Resolution

The Emulex HBA Manager application fails to create vPorts.

If an error occurs during vPort creation, an error message indicates the failure. Several conditions must be met before a virtual port can be created.

To view a detailed list of unsatisfied conditions, perform the following steps:

1.    Start the Emulex HBA Manager application.

2.    Select View > Group Adapters by Virtual Port from the Main menu.

3.    In the discovery-tree, select the FC function on which you want to create a virtual port.

The Virtual Ports tab should contain a list of unsatisfied conditions (if any) that are preventing a virtual port from being created.

4.    If there are no unsatisfied conditions, yet vPort creation still fails, contact Broadcom Technical Support.

The port is not ready.

The controls in the New Virtual Port area of the Virtual Port tab are replaced by a list of reasons why vPorts cannot be created. The reasons can be one or more of the following:

n    The driver NPIV parameter is disabled.

n    The adapter port is out of resources for additional virtual ports.

n    The port is not connected to a fabric.

n    The fabric switch does not support virtual ports.

n    The fabric switch is out of resources for additional virtual ports.

n    The port link state is down.