topic Re: Fibre Channel interface in Operating System - HP-UX

Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:10:54 GMT

I have a L-3000-8x, I have installed

5158A B.11.00.06 HP PCI/HSC Tachyon TL Fibre Channel
A5230A B.11.00.05 100BT/9000 PCI
B2491BA B.11.00 MirrorDisk/UX
BUNDLE B.11.00 Patch Bundle
HPUXEng64RT B.11.00.01 English HP-UX 64-bit Runtime Environment
UXCoreMedia B.11.00.02 HP-UX Media Kit (Reference Only. See Description)
XSWGR1100 B.11.00.53.2 HP-UX General Release Patches, June 2001
XSWHWCR1100 B.11.00.53.8 HP-UX Hardware Enablement and Critical Patches, June 2001

And I have installed the drivers in fcXXXX.

I have do: #insf -e

But when I do #ioscan , it doesn't reconice the target.

What is the problem? What I have doing bad?
Thanks very much.

Carmen.

Re: Fibre Channel interface

Cheryl Griffin — Mon, 02 Jun 2003 10:15:13 GMT

When the hardware fails to show up in ioscan it indicates a HW problem still. Check your connections, cable, termination, etc.

Re: Fibre Channel interface

Bruno Vidal — Mon, 02 Jun 2003 10:16:57 GMT

Hi,
What is the fibre channel interface ?
-A5158A (td driver)
-old fcms interface ?
-other ?

Do you have the added to the kernel the driver and/or fcms subsystem (go to SAM,kernel configuration/driver and subsystem).

Cheers.

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:25:29 GMT

Hi,

Its a target of Fibre Channel, to connect disks by fibre.

I only have the target, it is not some cable connected to the target, but the system would have to reconoce it, doesn't it?

Thanks!

Re: Fibre Channel interface

Bruno Vidal — Mon, 02 Jun 2003 10:28:53 GMT

The system will recognize it only if it has the good driver in the kernel, ie: fcms can add fcms fibre channel interface (olf HP fashion), A5158 11.06 will recongnise the 1Gb interface, and the A5158 11.10 product will be able to recognise 2Gb interface. If you have a third party interface you need their own driver.
Cheers.

Re: Fibre Channel interface

Cheryl Griffin — Mon, 02 Jun 2003 10:31:03 GMT

On a separate note, the A5158A installation instructions says patch PHKL_23939 is required
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=A5158A&oper=install
These instructions include how to enable the driver. This patch is not in any of the bundles you mention.

The A5230A requires a SAM patch and a Lanadmin patch which has dependencies. This is the complete list of required patches for this lan card:
PHCO_21187 cumulative SAM/ObAM patch
PHNE_21767 cumulative ARPA Transport patch
PHNE_22566 Cumulative STREAMS Patch
PHNE_22962 LAN product cumulative patch

Mirror/UX requires:
PHCO_21187 cumulative SAM/ObAM patch
PHCO_23651 fsck_vxfs(1M) cumulative patch
PHCO_23791 LVM commands cumulative patch
PHKL_18543 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016 2nd CPU not recognized in G70/H70/I70
PHKL_27813 POSIX AIO;getdirentries;MVFS;rcp;mmap/IDS
PHKL_27980 VxFS 3.1 cumulative patch: CR_EIEM
PHKL_27814 LVM Cumulative Patch w/Performance Upgrades
PHKL_28180 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,PDC,CLK

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:38:07 GMT

Hi,

I have revised the patxes and I have the PHKL_23939 and the rest....

> swlist -l product |grep -i 23939 PHKL_23939 1.0 Fibre Channel Mass Storage Driver Patch

Re: Fibre Channel interface

Bruno Vidal — Mon, 02 Jun 2003 10:41:57 GMT

I think we will try shortly, do this command:
#what /stand/vmunix | grep -E 'td|fcms'
You should have two lines:
PATCH_11.00: libtd.a : Jul 15 2002, 11:34:12, PHSS_26798
libfcms.a $Date: 2001/06/06 14:20:00 $Revision: PATCH_11.00 (PHKL_23939)

One for the libtd and one for the fcms:
-td: driver for the interface itself
-fcms: the fibre channel protocol

(the patche version can differ from mine). But now, what is the interface that you have in your system ?

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:45:04 GMT

I have this, is it correct?

what /stand/vmunix | grep -E 'td|fcms'
libtd.a HP Fibre Channel Tachyon TL/TS Driver B.11.00.06 (AP0301(DART52) pre-release) /ux/core/kern/wsio/td_glue.c: Jan 3 2001, 14:33:20
libfcms.a $Date: 2001/06/06 14:20:00 $Revision: PATCH_11.00 (PHKL_23939)

Thanks!

Re: Fibre Channel interface

Bruno Vidal — Mon, 02 Jun 2003 10:48:20 GMT

So everything is correct from a kernel point of view, so you should have at ioscan:
fc 0 0/3/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
For the old kind of interface, or:

fc 1 0/2/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
For an A51R8A interface. So now, what kind of interface do you have inside the system ?

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:56:50 GMT

Hi,

I have this
#ioscan -f

hptmp01:/tmp/parches> ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide LVD
target 0 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
target 1 0/0/1/1.2 tgt CLAIMED DEVICE
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
target 2 0/0/1/1.7 tgt CLAIMED DEVICE
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 3 0/0/2/0.2 tgt CLAIMED DEVICE
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
target 4 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Single-Ended
target 5 0/0/2/1.2 tgt CLAIMED DEVICE
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
target 6 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
unknown -1 0/0/4/0 UNCLAIMED UNKNOWN PCI BaseSystem (103c128d)
tty 0 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 6 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 7 0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 8 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
unknown -1 0/10/0/0 UNCLAIMED UNKNOWN PCI Ethernet (14e41645)
ba 9 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
unknown -1 0/12/0/0 UNCLAIMED UNKNOWN PCI SerialBus (103c1029)
pbc 0 32 pbc CLAIMED BUS_NEXUS Bus Converter
processor 0 33 processor CLAIMED PROCESSOR Processor
pbc 1 36 pbc CLAIMED BUS_NEXUS Bus Converter
bc 1 36 pbc CLAIMED BUS_NEXUS Bus Converter
processor 1 37 processor CLAIMED PROCESSOR Processor
pbc 2 96 pbc CLAIMED BUS_NEXUS Bus Converter
processor 2 97 processor CLAIMED PROCESSOR Processor
pbc 3 100 pbc CLAIMED BUS_NEXUS Bus Converter
processor 3 101 processor CLAIMED PROCESSOR Processor
memory 0 192 memory CLAIMED MEMORY Memory

I have in the slot 11, this target: A6785A 2G/1G Fibre Channel.

What can I do?
Thansk a lot of!
Carmen.

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 10:58:17 GMT

Pardon,

The target is: A6795A,

Re: Fibre Channel interface

Bruno Vidal — Mon, 02 Jun 2003 11:03:13 GMT

Okay, now I've understand, it is what I said in my second or first reply, libtd 11.06 is not enought to support 2Gb Fibre channel interface, you need the libtd patche:
PHSS_26798 that will bring 11.00.10 version of the tachyon driver.

Cheers.

Re: Fibre Channel interface

Carme Torca — Mon, 02 Jun 2003 13:06:05 GMT

Perfect,

I Have installed the patch PHSS_26798, and now I can see the target.

Thanks very much!!!!

Re: Fibre Channel interface

Angus Crome — Tue, 03 Jun 2003 04:32:41 GMT

If you have not already done so, you should bring your Support Plus patch releases forward to at least June 2002. June 2001 was not extremely stable for Fibre Channel. This goes for the EMS (Diagnostics) as well.

Dec 2002 is very stable, but I have had some problems with the March 2003 HWEnable patches thus far.