- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Diagnosing FC path down?
HPE EVA Storage
1819679
Members
3914
Online
109605
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
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
Go to solution
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-18-2009 04:50 AM
тАО08-18-2009 04:50 AM
Say you have a FC path go down between a server and a SAN switch. Is there anything to indicate if it's the cable, SFP, or HBA? I'm just wondering if there is a better way than physically replacing parts until you find what fixes it.
Specifics to my situation: Windows servers, QLogic or Emulex HBAs. HP (rebranded Brocade) SAN switches.
Specifics to my situation: Windows servers, QLogic or Emulex HBAs. HP (rebranded Brocade) SAN switches.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2009 05:10 AM
тАО08-18-2009 05:10 AM
Re: Diagnosing FC path down?
I'm not aware of any. The hardware only knows there is no link, but doesn't know if this is the cable or the emitter.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2009 05:17 AM
тАО08-18-2009 05:17 AM
Re: Diagnosing FC path down?
Well if you see the port properties you will see the sfp info.. it will display the current statistics..
if its faulty it wont show .. this is one of the way to identify the problem between cable & sfps.
if its faulty it wont show .. this is one of the way to identify the problem between cable & sfps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2009 08:22 AM
тАО08-18-2009 08:22 AM
Solution
A steady amber light on a brocade switch port indicates that it does receive light, but it cannot establish a link. It could be a problem with the port sender, the cable or the receiver.
There is also a customer advisory with some useful information:
c01392475 - HP StorageWorks B-Series Switches - Identifying if SFP or the Cable is the Cause for Loss of Link
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01392475
As usual, the formatting is bad. Here are the last lines:
enc_out -> Encoding error outside of frames
crc err -> Frames with CRC errors
Lr_in -> Link reset In (primitive sequence), does not apply to FL_Port
Lr_out -> Link reset Out (primitive sequence), does not apply to FL_Port
Ols_in -> Offline reset in (primitive sequence), does not apply to FL_Port
Ols_out -> offline reset out (primitive sequence), does not apply to FL_Port
There is also a customer advisory with some useful information:
c01392475 - HP StorageWorks B-Series Switches - Identifying if SFP or the Cable is the Cause for Loss of Link
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01392475
As usual, the formatting is bad. Here are the last lines:
enc_out -> Encoding error outside of frames
crc err -> Frames with CRC errors
Lr_in -> Link reset In (primitive sequence), does not apply to FL_Port
Lr_out -> Link reset Out (primitive sequence), does not apply to FL_Port
Ols_in -> Offline reset in (primitive sequence), does not apply to FL_Port
Ols_out -> offline reset out (primitive sequence), does not apply to FL_Port
.
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP