- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fibre channel driver received link dead
Operating System - HP-UX
1823975
Members
3679
Online
109667
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
Forums
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
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
тАО12-30-2008 06:31 AM
тАО12-30-2008 06:31 AM
fibre channel driver received link dead
Hi guys i have checked one of FC in the server has a status of Awaiting_link_up. I have checked this site http://docs.hp.com/en/diag/ems/dm_ql_adapter.htm and it give these actions
# Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
# Verify that the device which is connected to the adapter port is functioning correctly.
# Verify that the adapter port is functioning correctly by performing internal and external loopback tests. Please attach a loopback hood to the adapter port when executing a loopback test.
But i dont know how to do this, can anyone assist.
Also can this be done remotely? or do i have to verify it physically on the machine.
# Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
# Verify that the device which is connected to the adapter port is functioning correctly.
# Verify that the adapter port is functioning correctly by performing internal and external loopback tests. Please attach a loopback hood to the adapter port when executing a loopback test.
But i dont know how to do this, can anyone assist.
Also can this be done remotely? or do i have to verify it physically on the machine.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 08:07 AM
тАО12-30-2008 08:07 AM
Re: fibre channel driver received link dead
The first step must be verified physically on-site. Check that the connectors are securely plugged-in, and that the cable is not damaged. Observe the minimum bending radius of the fibre: a fibre-optic cable can be easily damaged by kinks or knots.
The second step depends on what the connected device actually is. If it's a large storage system which has independent network connection for configuration and diagnostics, you may be able to verify its state remotely (see the system's documentation on how to do that). If it's a simple device which is only accessible through the FibreChannel interface, you'll need to verify it physically (by looking at its front panel LEDs or something, see the manual of the device).
The third step:
The internal loopback test can be run remotely using the fcmsutil, BUT the looped-back test traffic will also be sent out on the fibre, so you'll need to disconnect or disable the device you have connected to the FC adapter before running the test. Read "man fcmsutil" and don't proceed until you understand the warnings.
The external loopback test requires that you unplug the fibre from the adapter and connect a loopback plug in its place. So this must be done physically on-site.
MK
The second step depends on what the connected device actually is. If it's a large storage system which has independent network connection for configuration and diagnostics, you may be able to verify its state remotely (see the system's documentation on how to do that). If it's a simple device which is only accessible through the FibreChannel interface, you'll need to verify it physically (by looking at its front panel LEDs or something, see the manual of the device).
The third step:
The internal loopback test can be run remotely using the fcmsutil, BUT the looped-back test traffic will also be sent out on the fibre, so you'll need to disconnect or disable the device you have connected to the FC adapter before running the test. Read "man fcmsutil" and don't proceed until you understand the warnings.
The external loopback test requires that you unplug the fibre from the adapter and connect a loopback plug in its place. So this must be done physically on-site.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 09:35 AM
тАО12-30-2008 09:35 AM
Re: fibre channel driver received link dead
fcmsutil is the one that i know, are there any other tools that i can use to check the status of the fibre channel i cant find any on the net.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 03:13 PM
тАО12-30-2008 03:13 PM
Re: fibre channel driver received link dead
As far as I know, there is nothing else.
MK
MK
MK
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