- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Fiber channel problem
Operating System - HP-UX
1753435
Members
4529
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
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
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
08-07-2007 05:24 PM
08-07-2007 05:24 PM
Fiber channel problem
Could someone plz make me understand the output:
Aug 6 01:53:20 billing EMS [5029]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/adapters/
events/TL_adapter/0_0_12_0_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmo
n/bin/resdata -R 329580551 -r /adapters/events/TL_adapter/0_0_12_0_0 -n 329580545 -a
CURRENT MONITOR DATA:
Event Time..........: Mon Aug 6 01:53:19 2007
Severity............: MAJORWARNING
Monitor.............: dm_TL_adapter
Event #.............: 3
System..............: billing
Summary:
Adapter at hardware path 0/0/12/0/0 : Received an interrupt indicating and
Elastic Store Error Storm
Description of Error:
lbolt value: 86524156
The Fibre Channel Driver received an interrupt from the
adapter indicating an Elastic Store Error Storm
Frame Manager Status Register = 0x82000400
Probable Cause / Recommended Action:
The Tachyon TL chip controlling Fibre Channel operation has experienced
an overflow or underflow in its inbound data queue.
The following may cause this error :
1. Cable fault
2. Hardware fault
3. Optical Unit Fault
The Tachyon TL chip will recover without intervention
Preventive Information :
Verify the fiber optic cable integrity as follows:
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 on the
FCMS Adapter using fcmsutil. Command syntax is as follows:
/opt/fcms/bin/fcmsutil lb plm
If the problem persists, replace the adapter.
Additional Event Data:
System IP Address...: 10.10.20.20
Event Id............: 0x46b62ab000000000
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):
0x46b62aaf00000000
Additional System Data:
System Model Number.............: 9000/800/S16K-A
OS Version......................: B.11.11
EMS Version.....................: A.04.00
STM Version.....................: A.45.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#3
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/0/12/0/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B0000119050
I/O Log Event Data:
Driver Status Code..................: 0x00000003
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000004 052840FC 00000001 00000001 82000400 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63
Aug 6 01:53:20 billing EMS [5029]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/adapters/
events/TL_adapter/0_0_12_0_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmo
n/bin/resdata -R 329580551 -r /adapters/events/TL_adapter/0_0_12_0_0 -n 329580545 -a
CURRENT MONITOR DATA:
Event Time..........: Mon Aug 6 01:53:19 2007
Severity............: MAJORWARNING
Monitor.............: dm_TL_adapter
Event #.............: 3
System..............: billing
Summary:
Adapter at hardware path 0/0/12/0/0 : Received an interrupt indicating and
Elastic Store Error Storm
Description of Error:
lbolt value: 86524156
The Fibre Channel Driver received an interrupt from the
adapter indicating an Elastic Store Error Storm
Frame Manager Status Register = 0x82000400
Probable Cause / Recommended Action:
The Tachyon TL chip controlling Fibre Channel operation has experienced
an overflow or underflow in its inbound data queue.
The following may cause this error :
1. Cable fault
2. Hardware fault
3. Optical Unit Fault
The Tachyon TL chip will recover without intervention
Preventive Information :
Verify the fiber optic cable integrity as follows:
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 on the
FCMS Adapter using fcmsutil. Command syntax is as follows:
/opt/fcms/bin/fcmsutil
If the problem persists, replace the adapter.
Additional Event Data:
System IP Address...: 10.10.20.20
Event Id............: 0x46b62ab000000000
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):
0x46b62aaf00000000
Additional System Data:
System Model Number.............: 9000/800/S16K-A
OS Version......................: B.11.11
EMS Version.....................: A.04.00
STM Version.....................: A.45.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#3
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/0/12/0/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B0000119050
I/O Log Event Data:
Driver Status Code..................: 0x00000003
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000004 052840FC 00000001 00000001 82000400 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2007 05:36 PM
08-07-2007 05:36 PM
Re: Fiber channel problem
Shalom,
Sounds like one of the following issues.
1) A lip storm or other major problem on the Fiber network. Run the diagnostics recommended in the message to learn more. Post back here the good stuff.
2) LUN0 is not assigned to this fiber channel card and its detecting the disk array as a disk. Only its not a disk and causes errors. See if you can assign a LUN0 to the card and perhaps the message will magically go away.
SEP
Sounds like one of the following issues.
1) A lip storm or other major problem on the Fiber network. Run the diagnostics recommended in the message to learn more. Post back here the good stuff.
2) LUN0 is not assigned to this fiber channel card and its detecting the disk array as a disk. Only its not a disk and causes errors. See if you can assign a LUN0 to the card and perhaps the message will magically go away.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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