topic Re: fc card error message in Operating System - HP-UX

fc card error message

Gurumanickam — Thu, 04 Jan 2007 23:36:02 GMT

hi all

I'm getting the following error in syslog

Jan 4 15:41:09 marc EMS [8967]: ------ EMS Event Notification ------ Value: "
SERIOUS (4)" for Resource: "/adapters/events/TL_adapter/0_9_0_0" (Threshold:
>= " 3") Execute the following command to obtain event details: /opt/resm
on/bin/resdata -R 587661314 -r /adapters/events/TL_adapter/0_9_0_0 -n 587661313
-a

CURRENT MONITOR DATA:

Event Time..........: Thu Jan 4 15:41:09 2007
Severity............: SERIOUS
Monitor.............: dm_TL_adapter
Event #.............: 23
System..............: marc

Summary:
Adapter at hardware path 0/9/0/0 : Fibre Channel driver has gone into
non-participating mode

Description of Error:

lbolt value: 4193

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

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

Additional Event Data:
System IP Address...: 10.1.1.26
Event Id............: 0x459cd2bd00000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x459cd0c800000000
Additional System Data:
System Model Number.............: 9000/800/L1500-7x
OS Version......................: B.11.00
EMS Version.....................: A.03.20
STM Version.....................: A.38.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#23

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v

Component Data:
Physical Device Path....: 0/9/0/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B00005FD220

I/O Log Event Data:

Driver Status Code..................: 0x00000017
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 47 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000003 00001061 00000001 00000001 A002D4B0 2F75782F 636F7265 2F6B6572
6E2F7773 696F2F74 645F6973 722E63

How to resolve this problem? help me?

Thanks in advance

Re: fc card error message

RAC_1 — Thu, 04 Jan 2007 23:48:57 GMT

You seem to have a problem with that card. Execute the command it says and post. Also try checking following.

fcmsutil /dev/tdx stat -s

/opt/resmon/bin/resdata -R 587661314 -r /adapters/events/TL_adapter/0_9_0_0 -n 587661313 -a

Re: fc card error message

Gurumanickam — Fri, 05 Jan 2007 00:00:34 GMT

hi RAC

I'm getting the following message:

# fcmsutil /dev/td0 stat -s
Fri Jan 5 10:24:05 2007
Channel Statistics

Statistics From Link Status Registers ...
Loss of signal 0 Bad Rx Char 255
Loss of Sync 3 Link Fail 1
Received EOFa 0 Discarded Frame 0
Bad CRC 0 Protocol Error 0

Thanks for the reply

Re: fc card error message

Andrew Young_2 — Fri, 05 Jan 2007 02:10:23 GMT

Hi.

This is often an indication that either the fibre cable itself has been disconnected or the device on the other end of the cable has been switched off or reset. I have never had this error with a fault on the local card.

Was this a single error or does it repeat?

HTH

Andrew Y

Re: fc card error message

Gurumanickam — Fri, 05 Jan 2007 03:56:36 GMT

hi,

I got this message yesterday, only one time at 15:24

Re: fc card error message

Andrew Young_2 — Fri, 05 Jan 2007 04:16:20 GMT

Hi.

Run fcmsutil /dev/td0

If the driver state is ONLINE then the link is up and you have no worries since it has reset itself.

If the driver state is not, then you need to check the actual connection to the FC HBA and see if the actual link light is on.

Is /dev/td0 the only FC HBA you have?

If you have more than 1 then run ioscan -funC fc to get the full listing of all the devices in the kernel. Check the hardware paths to make sure /dev/td0 is the correct one you are looking at.

If the link remains down any hardware attached to the other end of the cable should show up as NO_HW when you run an ioscan -fn. Check that that equipment is powerred on and the fibre connections are good.

I suspect though you have nothing to worry about unless this problem recurs frequently.

HTH

Andrew Y