- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: A6685A failure
Categories
Company
Local Language
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
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-30-2007 05:41 AM
01-30-2007 05:41 AM
A6685A failure
Driver state = AWAITING_LINK_UP
Most everything else on the "faulted" HBA matches the active card. I double checked that the zoning in the SAN is correct, which it is. I also found this note in OLDsyslog.log:
Dec 12 09:15:04 th9kkux vmunix: ct_query failed. hw_path = 8/8/1/0
So my question is; what other troubleshooting paths can be suggested before I break down and swap out the HBA.
Oh, yes; the system is no longer on a support contract, but I have a donor system waiting to have parts harvested.
Thanks in advance,
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 05:45 AM
01-30-2007 05:45 AM
Re: A6685A failure
~hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 05:52 AM
01-30-2007 05:52 AM
Re: A6685A failure
It might be the fabric network.
Trying the donor system will help you determine if the issue is the HBA. They have no moving parts, they don't often fail, but its not unheard of.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 05:58 AM
01-30-2007 05:58 AM
Re: A6685A failure
I have checked the cable. I see light on each end of each fiber.
I may try reseating the card before I do a transplant, but I need to make sure I've exhausted all uptime test first. (Our developers don't like to have the development system down when they are around)
Everything else in the SAN and particular zone are functioning properly. I've tried two other ports on the switch; one in the same Gbic and one in another Gbic.
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 06:20 AM
01-30-2007 06:20 AM
Re: A6685A failure
# ioscan -H 8/8/1/0
# fcmsutil /dev/td1 ns_query_ports
~thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 06:26 AM
01-30-2007 06:26 AM
Re: A6685A failure
Here they are:
$sudo ioscan -H 8/8/1/0
H/W Path Class Description
=======================================
8/8/1/0 fc HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
$ sudo fcmsutil /dev/td1 ns_query_ports
ERROR: Topology should be TD_FABRIC or TD_PUBLIC_LOOP.
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 08:32 AM
01-30-2007 08:32 AM
Re: A6685A failure
# ioscan -funC fc
# fcmsutil /dev/td0
# fcmsutil /dev/td1
assumes the device special file for your other HBA is /dev/td0??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 08:39 AM
01-30-2007 08:39 AM
Re: A6685A failure
Before replacing the HBA, connect a loopback cable and see if it syncs.
-denver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 10:44 AM
01-30-2007 10:44 AM
Re: A6685A failure
HBA is transmitting light and it is visible on the switch end of the fiber.
Sandman;
See outputs below:
$ sudo fcmsutil /dev/td1
Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 3.0
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Previous Topology = UNINITIALIZED
Local N_Port_id is = 0x000000
Local Loop_id is = 126
N_Port Node World Wide Name = 0x50060b0000135a4d
N_Port Port World Wide Name = 0x50060b0000135a4c
Driver state = AWAITING_LINK_UP
Hardware Path is = 8/8/1/0
Number of Assisted IOs = 0
Number of Active Login Sessions = 0
Dino Present on Card = YES
Maximum Frame Size = 992
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon
TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common
/wsio/td_glue.c: Sep 5 2005, 10:14:40
$ sudo fcmsutil /dev/td0
Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 3.0
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Topology = PTTOPT_FABRIC
Local N_Port_id is = 0x030000
N_Port Node World Wide Name = 0x50060b0000135875
N_Port Port World Wide Name = 0x50060b0000135874
Driver state = ONLINE
Hardware Path is = 8/4/1/0
Number of Assisted IOs = 92739952
Number of Active Login Sessions = 2
Dino Present on Card = YES
Maximum Frame Size = 992
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon
TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common
/wsio/td_glue.c: Sep 5 2005, 10:14:40
$ sudo ioscan -funC fc
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
fc 0 8/4/1/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre
Channel Mass Storage Adapter
/dev/td0
fc 1 8/8/1/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre
Channel Mass Storage Adapter
/dev/td1
Everything looks the same as far as I can tell on the HBA's.
Thanks,
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 10:57 AM
01-30-2007 10:57 AM
Re: A6685A failure
-denver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2007 11:36 PM
01-30-2007 11:36 PM
Re: A6685A failure
could you try the command as below,
fcmsutil /dev/td1 reset
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 12:18 AM
01-31-2007 12:18 AM
Re: A6685A failure
Valid point. I'll see if I have a cable that will work.
Cem,
I have tried that, but I didn't note it when I created the thread.
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 12:58 AM
01-31-2007 12:58 AM
Re: A6685A failure
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 12:59 AM
01-31-2007 12:59 AM
Re: A6685A failure
Stuart