- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: a fabic problem?
HPE EVA Storage
1753458
Members
4564
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2007 02:22 PM
тАО04-13-2007 02:22 PM
a fabic problem?
my rx 4640 is connected to a eva4000 via a san switch,but on /var/adm/syslog/syslog.log I find a error about fribc?
How to solve it?
the output is :
CURRENT MONITOR DATA:
Event Time..........: Sat Apr 14 09:45:40 2007
Severity............: SERIOUS
Monitor.............: dm_TL_adapter
Event #.............: 23
System..............: nmnd
Summary:
Adapter at hardware path 0/3/2/0 : Fibre Channel driver has gone into
non-participating mode
Description of Error:
lbolt value: 5163
The Fibre Channel Driver has gone into non-participating mode
Frame Manager Status Register = 0x200002ff
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...: 172.16.1.12
Event Id............: 0x4620324400000004
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.01
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4620309c00000002
Additional System Data:
System Model Number.............: ia64 hp server rx4640
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.54.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/3/2/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B0000BDC562
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: 65 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000003 0000142B 00000001 00000001 200002FF 2F75782F 636F7265 2F697375
2F544C2F 6B65726E 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E
63
How to solve it?
the output is :
CURRENT MONITOR DATA:
Event Time..........: Sat Apr 14 09:45:40 2007
Severity............: SERIOUS
Monitor.............: dm_TL_adapter
Event #.............: 23
System..............: nmnd
Summary:
Adapter at hardware path 0/3/2/0 : Fibre Channel driver has gone into
non-participating mode
Description of Error:
lbolt value: 5163
The Fibre Channel Driver has gone into non-participating mode
Frame Manager Status Register = 0x200002ff
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
If the problem persists after verifying fiber optic cabling,
replace the adapter
Additional Event Data:
System IP Address...: 172.16.1.12
Event Id............: 0x4620324400000004
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.01
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4620309c00000002
Additional System Data:
System Model Number.............: ia64 hp server rx4640
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.54.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/3/2/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B0000BDC562
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: 65 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000003 0000142B 00000001 00000001 200002FF 2F75782F 636F7265 2F697375
2F544C2F 6B65726E 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E
63
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2007 08:25 PM
тАО04-13-2007 08:25 PM
Re: a fabic problem?
Hi,
The error message appears to contain fairly specific troubleshooting methods...
Can we assume that you've done this and the fault persists ?
Cheers,
Rob
The error message appears to contain fairly specific troubleshooting methods...
Can we assume that you've done this and the fault persists ?
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2007 01:34 PM
тАО04-14-2007 01:34 PM
Re: a fabic problem?
I have executed the command:
/opt/fcms/bin/fcmsutil /dev/td0 lb plm ├п┬╝
the output indicate the data came back intact├г
and I replace the fabic cable,
but the problem also exist├г
so I should replace the adapter├п┬╝
/opt/fcms/bin/fcmsutil /dev/td0 lb plm ├п┬╝
the output indicate the data came back intact├г
and I replace the fabic cable,
but the problem also exist├г
so I should replace the adapter├п┬╝
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2007 03:14 AM
тАО04-16-2007 03:14 AM
Re: a fabic problem?
Hi,
That's what the event details suggest you do... however you might want to get a fault called logged with HP to confirm.
Regards,
Rob
That's what the event details suggest you do... however you might want to get a fault called logged with HP to confirm.
Regards,
Rob
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP