Getting error in syslog "FC driver received a loop port Bypass" ?

rveri — Thu, 23 Feb 2006 04:06:06 GMT

Hi Admins,

I am getting this error in syslog . Please help to understand as whats wrong, :

-------------------------------------
/opt/resmon/bin/resdata -R 190971945 -r /adapters/events/TL_adapter/7_1_0 -n 190971910 -a

CURRENT MONITOR DATA:

Event Time..........: Thu Feb 23 01:23:29 2006
Severity............: CRITICAL
Monitor.............: dm_TL_adapter
Event #.............: 33
System..............: server1.com

Summary:
Adapter at hardware path 7/1/0 : Unable to open previously opened target

Description of Error:

lbolt value: 97170169

Unable to access previously accessed target
nport ID = 0xcb

Probable Cause / Recommended Action:

An attempt to re-open a device which had been opened earlier
has failed.
There should be additional logging messages which will
allow diagnosis of the problem.

Additional Event Data:
System IP Address...: 10.80.10.69
Event Id............: 0x43fd62f100000000
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):
0x43fd62f100000000
Additional System Data:
System Model Number.............: 9000/800
OS Version......................: B.11.00
EMS Version.....................: A.03.20
STM Version.....................: A.44.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#33
--------------------------------------------------------------------------------

Also getting this message on syslog.log

Feb 23 01:39:28 server1 vmunix: 7/1/0: Fibre Channel Driver received a Loop Port Bypass. Frame Manager Status
Feb 23 01:39:29 server1 above message repeats 3 times
Feb 23 01:39:28 server1 vmunix: Register = 0x80200200.
Feb 23 01:39:28 server1 vmunix: Register = 0x101000E0.
Feb 23 01:39:37 server1 vmunix: 7/1/0: Fibre Channel Driver received a Loop Port Bypass. Frame Manager Status
Feb 23 01:39:37 server1 vmunix: Register = 0x101000E0.
Feb 23 01:39:41 server1 vmunix: Register = 0x102800E0.
Feb 23 01:39:54 server1 vmunix: 7/1/0: Fibre Channel Driver received a Loop Port Bypass. Frame Manager Status
Feb 23 01:39:54 server1 vmunix: Register = 0x802800A0.
Feb 23 01:39:54 server1 vmunix: Register = 0x101000E0.
Feb 23 01:40:08 server1 vmunix: 7/1/0: Fibre Channel Driver received a Loop Port Bypass. Frame Manager Status
Feb 23 01:39:54 server1 vmunix: Register = 0x102800E0.
Feb 23 01:40:08 server1 vmunix: Register = 0x101000E0.
Feb 23 01:40:08 server1 vmunix: Register = 0x102800E0.
Feb 23 01:40:08 server1 vmunix: Register = 0x80280090.
Feb 23 01:40:18 server1 vmunix: 7/1/0: Fibre Channel Driver received a Loop Port Bypass. Frame Manager Status
Feb 23 01:40:18 server1 vmunix: Register = 0x101000E0.
Feb 23 01:40:19 server1 vmunix: Register = 0x102800E0.
------------------------------------------

fcmsutil shows :
# fcmsutil /dev/td4

Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Previous Topology = PRIVATE_LOOP
Local N_Port_id is = 0x000001
Local Loop_id is = 125
N_Port Node World Wide Name = 0x50060b000006f6c5
N_Port Port World Wide Name = 0x50060b000006f6c4
Driver state = AWAITING_LINK_UP
Hardware Path is = 7/1/0
Number of Assisted IOs = 1737571
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 992
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL Driver B.11.00.10 PHSS_30597 /ux/core/kern/wsio/td_glue.c: Jul 25 2004, 13:14:38
----------------------------

Please suggest as what is wrong!

Thanks,

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

LoC_1 — Thu, 23 Feb 2006 04:51:48 GMT

Hi
This indicates that one of the device connected on 7/1/0: has become unavailable.
Fibre Channel Driver received a Loop Port Bypass mening that the port has dropped out of the loop.

It could be a bad device or a bad port on the switch/hub, or somebody disconnected a cable.
To me it looks like a flaky connection because its conneting and dropping.

Louis

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Deepak.R — Thu, 23 Feb 2006 10:54:58 GMT

Hi,

It looks like a connection issue or an issue related to your target . Find out what device was connected and had dev ID 0xcb. If it is an external tape device, it could also be a power issue at the device.

fcmsutil has options to list devices connected.

pls go thru fcmsutil man pages.

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Deepak.R — Thu, 23 Feb 2006 10:55:12 GMT

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Sandman! — Thu, 23 Feb 2006 12:38:28 GMT

Hello!

Most likely cause is that the Fibre Channel mass storage adapter on HW path 7/1/0 has failed. If you have redundant FC cards then I/O traffic should be transparently routed through the other one. Might help in isolating the problem if you could post the output of ioscan:

# ioscan -funC fc

thanks

topic Getting error in syslog "FC driver received a loop port Bypass" ? in Operating System - HP-UX

Getting error in syslog "FC driver received a loop port Bypass" ?

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Re: Getting error in syslog "FC driver received a loop port Bypass" ?

Re: Getting error in syslog "FC driver received a loop port Bypass" ?