TL_adapter question

[Filosofo]

Hello,
after a reboot of the server I see this error in Syslog:
------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource:
"/adapters/events/TL_adapter/2_0_5_0_0" (Threshold: >= " 3") Execute the following command to obtain ev
ent details: /opt/resmon/bin/resdata -R 239534082 -r /adapters/events/TL_adapter/2_0_5_0_0 -n 239534081 -a

I try to execute thi command, and i see:


Description of Error:


lbolt value: 1242

The Fibre Channel Driver has gone into non-participating mode
Frame Manager Status Register = 0xa0084480


Probable Cause / Recommended Action:

A cable or hardware problem exists. This can also be caused due
to the Tachyon TL adapter changing its AL_PA across a LIP.
Do the following:
1. Verify that the fiber optic cable is functional and securely
attached to the Fibre Channel Mass Storage Adapter.
2. After checking the cabling, execute a loopback test using
fcmsutil.
Command syntax is as follows:
/opt/fcms/bin/fcmsutil lb plm
If the problem persists after verifying fiber optic cabling,
replace the adapter

I verify the correct function of Fibre chanel, and now is all OK.

Is normal that during reboot I see this error?

Thanks


Filo

[Stefan Farrelly]

No, its not normal. Ive never seen messages like this on rebooting all our HP servers with fibre/SAN disks. Contact your storage expert/storage supplier to investigate.

Before you do that do ensure you have the latest Online Diagnostics installed as it may simply be a bug in the diags which is now fixed in a newer version.

[Bhuvaneswari Selvaraj]

No, You are not supposed to get this message.

1. Install the latest version and patches of OnlineDiagnostics.
2. Try using monconfig, and set some requests for the device and check whether the device is fine or not. If monconfig reports some erroe, fix the same.
3. If monconfig, shows no error, reboot the same and check again whether you are getting the message. If u still get the message, then contact fibre channel expert and check the device.

[Zeev Schultz]

Check with swlist -l product | grep -i fc that
you have all fc software/patches installed.
with fcmsutil /dev/tdX or /dev/fcmsX can get basic info on your card (patch,topology wwn etc),with fcmsutil "stat" option can get some more statistics.LIPs usualy happen when sone of the devices on arbitrated loop are reseting thus doing "logon" procedure to obtain port_id.
can be that on the other hand you have a device that doesn't have its AL-PA hard set?
Also check switchshow,porterrshow brocade switch commands to see a statistics for a specific port.

Zeev