Strange system hang

[Don Spare]

Over the weekend my development server locked up. It would accept connections but never get to where it would let the user login. I tried using the console via Secure Web Console and got prompted for login, gave it the username and that was where it stayed. It never prompted for password. I had to cycle the power this morning when I came in and it seems to be okay now BUTTTTTTTT.....
In an attempt to try to find out what happened, I ran stm and found the Fibre Channel addapter in red. Drill down produced the following information:
-------------------------------------------------
.... dwdev001 : 10.1.10.98 ....

-- Current Device Status Log for Fibre Channel Interface on path 0/4/0/0 --

The following information was archived during the last hardware scan:

Product : Fibre Channel Interface
Qualifier : HP5158A_Tachyon_TL
Hardware Path : 0/4/0/0
Device Type : Interface
Device Qualifier : FibreTL

Most Recent Tool Run : Information
Tool Exit Status :
Tool completed with exit_status MOD_FAILED (4) indicating the tool completed
with a failure.
Current Status : FAILED

Recommended Action : Tool has failed. Check test_activity_log and
failure_log.

Installed tools:
Diagnostic : tl_adapter (Licensed)
Verifier : None
Exerciser : None
Information : tl_adapter
Expert Tool : None
Firmware Update : None
------------------------------------------------------

Can anyone tell me what this means and how serious it is? The fibre channel connects to the EMC Clariion and that's where all the databases are.

[Steven E. Protter]

Recommend the following:

Install this:
http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

Get the latest and greatest stm tool on your system.

I'd have that fiber channel adapter replaced.

Red means dead.

I don't believe in the raising of dead fiber channel cards.

This is as serious as having to lose your developer server to an unplanned outage during the day.

SEP

[Don Spare]

I believe that 'red means dead' but they seem to be working. I checked my production system and it shows red too. I don't know how long this has been this way. Is it possible that there is just some configuration problem that stm can't handle?