C H A P T E R  4

Known Issues

This chapter provides supplementary and workaround information about the HBA. The chapter contains the following topics:


Server Compatibility Issues

This section contains the following topics:

Cannot Set the HBA to a Configured State on a Sun Blade X6250 Server (6674189)

If you set the HBA to a disconnected state on a Sun Blade X6250 server, and you then set it back to a configured state, the HBA remains in a disconnected state.

Workaround - Perform one of the following to return the HBA to a configured state:

The HBA is Not Detected on a Sun Blade T6320 Server ( 6682447)

After rebooting a Sun Blade T6320 server, the server might not detect the HBA.

Workaround - Reboot the server again.


qlc Driver Issues

This section contains the following topics:

The fcinfo Command Displays Inconsistent Information About the HBA (6683551)

Upon running the fcinfo command, some, but not all, HBA information is displayed.

Workaround - Update the qlc driver to version 20080402-2.28 or later. The latest version of the qlc driver is included in the following Solaris patches:

You can download these patches from the SunSolve website at:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage

No Support For N-Port, Point-to-Point Topology (6547693)

The qlc driver does not provide support for the N-Port, point-to-point topology.

Workaround - Use the Sun StorageTek T10000A or T10000B tape drive in a switch configuration. This enables usage of the N-Port, point-to-point topology.


Red Hat Linux Enterprise Issues

This section contains the following topic:

Error Messages Are Displayed in System Log Files When Running the RHEL 5 OS

When running the RHEL 5 operating system with the ql2xextended_error_logging module parameter enabled, you might see softlock detected messages (soft lockup on CPU#0!) in the system log files.

Workaround - None. You can ignore these messages as they do not indicate operational failures.