Fibre Channel target installed but I can't see it

[Michael Tully]

Please provide the output of ioscan.

# ioscan -fn

[Carme Torca]

Hi,
Here you are:

# ioscan -fn
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 (582)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0 /dev/lan0
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
target 0 0/0/1/0.6 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t6d0
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
target 1 0/0/1/1.0 tgt CLAIMED DEVICE
disk 1 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
target 2 0/0/1/1.6 tgt CLAIMED DEVICE
ctl 1 0/0/1/1.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t6d0
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
target 3 0/0/2/0.0 tgt CLAIMED DEVICE
disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
target 4 0/0/2/0.6 tgt CLAIMED DEVICE
ctl 2 0/0/2/0.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t6d0
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
target 5 0/0/2/1.2 tgt CLAIMED DEVICE
disk 3 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
target 6 0/0/2/1.6 tgt CLAIMED DEVICE
ctl 3 0/0/2/1.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t6d0
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/mux0 /dev/tty0p1
/dev/diag/mux0 /dev/tty0p0 /dev/tty0p2
tty 1 0/0/5/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/diag/mux1 /dev/mux1 /dev/tty1p1
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/6 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 7 0/7 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 5 0/7/0/0 c720 UNCLAIMED UNKNOWN PCI SerialBus (10dff900)
memory 0 8 memory CLAIMED MEMORY Memory
processor 0 160 processor CLAIMED PROCESSOR Processor
processor 1 166 processor CLAIMED PROCESSOR Processor
#

[Tom Geudens]

Hi,
The "UNCLAIMED" would still point to the fact that you don't have the correct driver for the fibrecard. What type of fibrecard is it ?

Regards,
Tom Geudens

[Carme Torca]

Hi,

The fibre channel target doesn't have anything write in it... I don't know... maybe it ocurred an error and someone put a fibre changed.

I am going to ask it. Thanks very much for all!!!

[Carme Torca]

Hi,

I don't know what kind of fibre channel is.... I only can see that its 2GB interface....

What drivers I could install to probe it?

[Michael Tully]

Before you can install the FC driver, you have to first install the FC-Mass storage filesets (and dependencies) from the CORE-OS CD. Attempting to install any other driver will not be successful until this is done. This problem usually happens after nstalling a card into a system that previously did not have one.

[Carme Torca]

One question... Could I install this from Core OS hp-ux 11.0 july 2001. It would be correct?

Thanks!!

[Michael Tully]

yes you can, but you may still need to install some additional patches afterwards. At least you will have a starting point on which to work from.
Regards
Michael

[Carme Torca]

Hi,

I have seen that I have installed all this filesets:

# swlist -l fileset |grep -i fc


Asian-UTILITY.MFCONV-JPN-RUN A.03.00 Code Convertion Tools Runtime - Japan
# FC-TACHYON-TL B.11.11.09 PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A
FC-TACHYON-TL.FC-TL-KRN B.11.11.09 Fibre Channel Tachyon TL Kernel Library
FC-TACHYON-TL.FC-TL-RUN B.11.11.09 Fibre Channel Tachyon TL User Space files
# FCMassStorage B.11.11 Fibre Channel Mass Storage
FCMassStorage.FCMS-ENG-A-MAN B.11.11 FCMS-ENG-A-MAN
FCMassStorage.FCMS-INIT B.11.11 Fibre Channel Mass Storage Utilities
FCMassStorage.FCMS-JPN-E-MAN B.11.11 FCMS-JPN-E-MAN
FCMassStorage.FCMS-JPN-S-MAN B.11.11 FCMS-JPN-S-MAN
FCMassStorage.FCMS-KRN B.11.11 Fibre Channel Mass Storage Drivers
FCMassStorage.FCMS-RUN B.11.11 Fibre Channel Mass Storage Utilities
PHKL_23626.FCMS-ENG-A-MAN 1.0 FCMassStorage.FCMS-ENG-A-MAN
PHKL_23626.FCMS-KRN 1.0 FCMassStorage.FCMS-KRN
PHKL_23626.FCMS-RUN 1.0 FCMassStorage.FCMS-RUN
PHSS_26799.FC-TL-KRN 1.0 Fibre Channel Tachyon TL Kernel Library
PHSS_26799.FC-TL-RUN 1.0 Fibre Channel Tachyon TL User Space files
#

Is this correct?, then, what could it happened?

Thanks very much!,
Carmen.

[Mark Greene_1]

You could simply have a bad card. Do you have, or can you get, a second card to swap-out for this one?

mark

[Carme Torca]

Hi,

I haven't got another... it would be possible that the server cannot reconized any fibre channel targets??...

Thanks!
Carmen.

[Bernhard Mueller]

you have the filesets and the card is still unclaimed.

so for whatever reason I'd say the driver is not yet in the kernel (maybe you removed it after installing it? or something..)

Go into SAM and check what is IN and OUT.

Regards
Bernhard

[Bernhard Mueller]

Oops, forgot...

fcp should be IN

[Carme Torca]

Hi,

Someone say me that is an EMULEX target, and say me that is compatible with all servers....

Any idea?, Maybe L1000 doesn't work with determinated targets??

Thanks!

[Mark Greene_1]

What's the speed of the card? Some are 66mhz and some are 133mhz and you have to match the speed of the card with a slot on the bus that will communicate at that speed.

mark

[Carme Torca]

How can I do this?, I haven't got any idea....
How could I see this??

Thanks!,
Carmen.

[Paulo A G Fessel]

Seems that you're in need of the Emulex drivers for HP-UX. Emulex is really compatible with HP-UX when you get the drivers. ;-)

Notice that these aren't the drivers for EMC ou IBM frame, but they should work with EMC if you need it:

http://www.emulex.com/ts/docfc/hpuxframe.htm

HTH
Paulo Fessel

[Mark Greene_1]

To find out the speed of the fibre card, get the model number and then go to emulex's website and look-up the model of the card. The technical specs will include the bus speed.

Also, what are you connecting to? There may be other requirements for your system, depending on the fibre device you are trying to connect to.

mark

[Carme Torca]

Hi,

I have installed EMULEX driver and now I can see it ok:

7 0/7 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 5 0/7/0/0 lpfc CLAIMED INTERFACE PCI SerialBus (10dff900)

Now I do a insf -e, but it doesn't generated a file, it's necessary anything more?? it's necessay configure something??

Thanks!

[Paulo A G Fessel]

You must now configure your card. In order to do that, you have to know what mode your storage system uses. I'm almost certain that your topology is FC-SW (N_Port), but you must double-check this.

When you know the topology for sure, you must change the driver configuration - most precisely, the "CFG_TOPOLOGY" parameter. For more details, see this link:
http://www.emulex.com/ts/docfc/hpux/41108/indexconfig.htm

After configuring, you should be able to see your disks. Insf should detect them at boot time and assign devices automagically.

Don't forget to assign points if this solves your problem.

HTH,
Paulo Fessel

[Carme Torca]

Hi,

I have trying to understand all the configuration... but I can't understand all...
I have a target model LP9002L-EMC EMULEX 2GB 64 BIT 66MHZ PCI EMC, and I don't know what I have to put...
Could you help me??

Thanks!
Carmen.

[Paulo A G Fessel]

You must know what is the topology your FC card is using. There are basically two possible topologies: FC-SW and FC-AL. FC-SW - known as "N_Port" on Emulex driver - is used when you connect your FC card to a FC switch, such as EMC's Connectrix.

FC-AL is used on you have a set of disks which are dasychained, that is: the TX fiber from the FC card enters the RX connector in the first disk, then the TX fiber of the first disk connects to the RX connector of the second disk, and so on until you get to the last disk. Then finally, at the last disk, its TX fiber connects to RX connector back on the board, thus giving you a loop.

That's what you configure in the driver configuration file, and there's even a table inside it to guide you. Make sure you configure the correct value for your topology as shown in the config file; DON'T USE AUTODETECTS.

When you reconfigure and recompile the driver, you'll have to reboot your server. After the reboot - and assuming you have configured the driver correctly - the disks should be detected by your HP-UX installation.

Could you give more details on how this FC adapter is connected (direct to disks or to a switch)? What is your storage system?

[]'s
Paulo Fessel

P.S.: Don't forget to assign the points!