Fibre Channel Controller Status Change (worse)

[Steven Chie]

Fibre Channel Controller Status Change. The Fibre Channel Controller in Slot 3 has a new status of 6. (Host controller status values: 1=other, 2=ok, 3=failed, 4=shutdown, 5=connectionDegraded, 6=connectionFailed) [SNMP TRAP: 16028 in CPQFCA.MIB]

We are experiencing the error only after 3yrs of usage on the server. Previously it was running alright till recently, and not only does it have this error, it will auto shut down with nothing useful on the eventvwr except telling us there was an unexpected shutdown......

[Steven Clementi]

Is the server Booting from the SAN?

You could possibly have a bad fibre card or a bad cable (crimped somehow? or pinched?)

How are the drivers on the server? and the bios of the hba? Up to date?

There is also a possibility for the gbic to be bad on the SAN switch. Electronic components fail, it's no secret.

Simply narrow down the problem and get it fixed as soon as you can, is the best approach. I'd be kinda glad that in 3years, there were no problems.


Steven

[Steven Chie]

Thanks for the suggestions. Will take a look into it.

[Rob Leadbeater]

Hi,

What storage system do you have ?

Maybe there are some errors on that.

Cache batteries would be a likely suspect if the things been running for 3 years...

Cheers,

Rob

[Steven Chie]

That may be another possibility thanks

Regards

Steven

[skris]

I would second, Steven's suggestion here. you could also go through the switch(if any) reports and see the port status. Look for any non-zero link failures / CRC errors of Loss of Sync . (Most likely Link failures / LOS)

This should help you find the point of origin of all these errors.(start with the GBIC and then the cables for best results)

Cheers!
Shiva

[Steven Chie]

Hi all thanks for the replies!!!

Anyway i've tried the possibilities and it seems there is no issue with the Fibre channel card..... as it boots from local and not from the send as for the connection from past year events it was a common error. So i logged a call and apparently there were some issues with the mainboard (according to the HP engineer) well they came down and changed it hope it solves this unexpected shut down.......

Cheers!!!

Steven