Problem with FC Attached SureStore 2/20

[Duncan Edmonstone]

I am having a problem with a 2/20 which is direct attached via fibre channel to a L class through an A5158A FC HBA.

After installing and cabling up as per the 2/20 manual (Drive 1 & Media changer on one SCSI bus on FC card, Drive 2 on the second SCSI bus on FC card), everything looks good, I see both tapes, and the media changer through an ioscan:

# ioscan -fnH 0/5/0/0
Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
fc 1 0/5/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage
Adapter
/dev/td1
fcp 1 0/5/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 20 0/5/0/0.8.0.255.7 fcpdev CLAIMED INTERFACE FCP Device Interface
target 7 0/5/0/0.8.0.255.7.12 tgt CLAIMED DEVICE
autoch 1 0/5/0/0.8.0.255.7.12.0 schgr CLAIMED DEVICE HP C7200-8000
/dev/rac/c20t12d0
tape 2 0/5/0/0.8.0.255.7.12.1 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/2m /dev/rmt/2mnb /dev/rmt/c20t12d1BESTn
/dev/rmt/2mb /dev/rmt/c20t12d1BEST /dev/rmt/c20t12d1BESTnb
/dev/rmt/2mn /dev/rmt/c20t12d1BESTb
tape 4 0/5/0/0.8.0.255.7.12.2 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/4m /dev/rmt/4mnb /dev/rmt/c20t12d2BESTn
/dev/rmt/4mb /dev/rmt/c20t12d2BEST /dev/rmt/c20t12d2BESTnb
/dev/rmt/4mn /dev/rmt/c20t12d2BESTb

However when I try and use the mc command, with any option the command fails, as in the following example:

# mc -p /dev/rac/c20t12d0 -q
ERROR: 0x2 Not Ready : 0x401 Logical unit in process of becoming ready

Both tape drives work fine, and happily respond to mt commands, and tar/cpio/fbackup if I load a tape manually from the front panel of the library, but the picker just doen't want to respond...

I am on the latest firmware release, downloaded and installed from HPs web site just yesterday.

Any ideas on anything else I can try before resorting back to SCSI?

Thanks

Duncan

[Vincent Farrugia]

Hello,

You have to install the driver for the picker in order for the command to communicate with the picker.

See man mc in the dependencies section.

HTH,
Vince

[Duncan Edmonstone]

The device drivers are configured in the kernel :

autoch 1 0/5/0/0.8.0.255.7.12.0 schgr CLAIMED DEVICE HP C7200-8000
/dev/rac/c20t12d0

This has worked fine, with the same drivers when SCSI attached.

[Vincent Farrugia]

Hello,

Did you configure the library for Fibre Channel on the front panel before attaching to the Fibre channel loop?

Also, check whether you have the patch for mc command. PHCO_16194 for HP/UX 10.20 or PHCO_16195 for HP/UX 11.00.

Check whether the firmware of the library is greater than or equal to 1.25 . It should be higher so that Fibre cards work properly.

HTH,
Vince

[Duncan Edmonstone]

>Did you configure the library for Fibre Channel on the front panel before attaching to the Fibre channel loop?

- Yes - I followed the manual pretty-much word for word.

>Also, check whether you have the patch for mc command. PHCO_16194 for HP/UX 10.20 or PHCO_16195 for HP/UX 11.00.

Yes:

#swlist -l product | grep 16195
PHCO_16195 1.0 mc(1m) bug fixes and enhancements

>Check whether the firmware of the library is greater than or equal to 1.25 . It should be higher so that Fibre cards work properly.

Here's an excerpt from the STM info log, showing firmware rev 1.33

Product ID: C7200-8000
Hardware Path: 0/5/0/0.8.0.255.7.12.0
Device Type: SCSI Media Changer
Device Qualifier: HPC7200-8000
Vendor: HP
Product Revision Level: 1330
Error Log Summary:
Hard errors: 0
Movement errors: 17
Good moves since hard error: 233
Soft errors since hard error: 18
Recovery errors: 0
Run-Time errors: 0

Thanks

Duncan

[Michael Tully]

Hi,

Duncan,

Seems that you don't actually have the device
that talks direct to the robot. The device
you are using is not the one. Have a look at
this link. It will help you create one. It
is usually created /dev/picker or /dev/robot,
the name choice is yours.

Have a look at the attachment, it will solve
your problem.

Cheers
-Michael

[Duncan Edmonstone]

Thanks for the help Michael, but no dice! It's still not working...

First problem was which driver to use, the document states:

A. When the driver for the ext_bus (the SCSI card) is c700 or c720, use sctl.
B. Otherwise, use spt.

Which suggests that I should use spt, as my ext_bus is fcp_dev

But then it states:

If the tape drive driver is stape, then the picker driver is sctl.
If the tape drive driver is tape2, then the picker driver is spt.

Which now presents me with a problem, cos my tape devices (on the same bus) are stape, which suggests I should use sctl!

OK, no problem, I'll try both...

FOllowing the instructions to the letter, I find that I already have the sctl and spt drive in my kernel, so I add the appropriate line to the bottom of my system file, and reboot.

First with sctl...

Makes no difference to the ioscan (still shows schgr as associated with the device) - so I go ahead and create the device file with the appropriate major and minor numbers. lssf can't seem to match this up with a real hardware path, but never mind, I'll try using the mc command again - but guess what? mc on the new devive gives the exact same error as before.

OK try the spt driver... This *does* appear against the correct device in ioscan, but the S/W state now becomes UNCLAIMED, and H/W UNKNOWN. Never mind... create the device file as before and try lssf.. lssf says it doesn't know how to handle driver 'spt', and now mc gives a 'No such device or address' error message.

I'm running out ideas on this now.... anything else anyone can contribute would help...

Thanks

Duncan

[Michael Tully]

Hi,

Using mknod, try to create the picker device
as these. First pick up from 'lsdev' the
type of device being used whether 'spt' or
whatever. So try these

for Example you H/W addressing suggests that
the answer is

20 12 0

so lets convert into hex to create the device

mknod /dev/robot c 203 0x14c000
or
mknod /dev/robot c 231 0x14c000

# lsdev 203 231
Character Block Driver Class
203 -1 sctl ctl
231 29 schgr autoch

HTH
-Michael

[Duncan Edmonstone]

Thanks Michael,

Yes I've tried both of these, without success. I think perhaps I should have made it clearer above that I have had this same unit working OK when it was SCSI attached, the problem only seems to occur when it is FC attached.

I'm going to re-visit the patch level on this server, see if I am missing anything vital...

[Vincent Farrugia]

Hello,

Do you have patch PHKL_22460 installed? It exhibits the problem you are stating.

http://europe-support.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=2cb44bad024957ca50

Download the latest patch PHKL_25675 or replacing patch PHKL_22759.

HTH,
Vince