Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with FC Attached SureStore 2/20

Duncan Edmonstone
Honored Contributor

Problem with FC Attached SureStore 2/20

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

HTH

Duncan
15 REPLIES
Vincent Farrugia
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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
Tape Drives RULE!!!
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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.

HTH

Duncan
Vincent Farrugia
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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
Tape Drives RULE!!!
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

>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

HTH

Duncan
Michael Tully
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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
Anyone for a Mutiny ?
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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

HTH

Duncan
Michael Tully
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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
Anyone for a Mutiny ?
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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...

HTH

Duncan
Vincent Farrugia
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

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
Tape Drives RULE!!!
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

... Well I finaly got back to looking atthis problem - thanks Vincent the patch you suggested did look like a likely solution, but no it didn't work.... We';ve also tried the same unit attached to a Win2K machine and had very similar problems (the two tape devices were fine, but the robotics report as 'OFFLINE' and no way to bring it online).

Looks like its time to log a hardware support call!

Cheers

Duncan

HTH

Duncan
Curtis Ballard
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

Have you checked the RMC (network remote management card)? If you open the web pages on your RMC you should be able to see the true library status and narrow down your problem. The RMC status should show something like "checking inventory" if the library really does think it isn't fully powered up. It should show something like "Status: Good" if the library is actually ready.

If the RMC reports Good status then the possible problem locations are narrowed down to the the Fibre interface card, or something between it and your host. I don't believe mc uses any cached data so the problem probably isn't the host.

If the RMC doesn't report status Good or if you can't access it, the most common cause of a library not reporting good status is an unlocked or damaged drawer. Try opening all of them and if any opens then it needs closed and locked. If none of them open but the RMC or front panel reports "Door open" then a sensor on one of the drawers may be damaged and a hardware support call will be necessary.
Sanjay_6
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

Hi Duncan,

Try this.

To check the status of library,

mc -p /dev/rac/c20t12d0 -r DS

to move a DLT from slot 1 to Drive 1

mc -p /dev/rac/c20t12d0 -s S1 -d D1

To move the DLT from drive 1 to slot 1,

mc -p /dev/rac/c20t12d0 -s D1 -d S1

Hope this helps.

Regds
Vincent Farrugia
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

Hello,

Please keep us informed on how things develop. It's good to learn something new.

Thanks,
Vince
Tape Drives RULE!!!
Duncan Edmonstone
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

Well I do like to post my solutions, even when it takes me six months to arrive at them!

After working on an entirely seperate assignment for the last few months, I'd forgotten all about this problem, right up until the point I had to arrange a demo which used this fibre attached 2/20 - I'd assumed that one of my colleagues had gotten HP in and fixed the issue ages ago, but as it turns out the 2/20 has sat in a corner 'broken' for ages!

After several hours reminding myself everything I had done, we logged a hardware call, and got some HP CEs in to take a look...

After much to-ing and fro-ing and replacing almost every component in the 2/20 several times, we finaly hit on the problem...

The clue to the problem was actually in my original post:

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

Previous to the firmware upgrade I was on version 1.14 of the firmware, and I upgraded to version 1.33.

It turns out that there are some internal interfaces of the 2/20 known as 'bridging links' - these manage the interfaces between the cards (fibre controller/remote management card/library controller) - the firmware upgrade from 1.14 to 1.2? (something) made some changes to these bridging link interfaces, and guess what? the 1.33 version assumes these changes have already been made. The upshot of all this, is that upgrading straight from 1.14 to 1.33 appears to work 100% successfully, but completely breaks the library... this is made even more complex by the fact that:

a) Certain 2/20s only work with certain fibre controllers... you have to check the serial number of your unit before replacing...
b) you cannot go above a certain firmware rev (1.22 I think) if you have a particular transport mech which only has a 4K buffer (newer mechs have an 8k buffer)

Anyway the fix was to downgrade the firmware down to 1.14 (via the SCSI interface, patching firmware via the RMC or via fibre is apparently unreliable even without all these other problems!), and then upgrade in steps back up to 1.30 (we stopped there as I was out of time).

Lessons learned? well I already knew the golden rule of HP tape libraries, and I can't believe I broke it myself:

"NEVER NEVER NEVER upgrade tape library firmware yourself!!! ALWAYS get an HP CE in to do it"

and if you don't have HP support?

"NEVER NEVER NEVER upgrade tape library firmware AT ALL!!"

Anyway thanks for all the help guys, as usual I learned plenty of other neat stuff while fixing this.

Cheers

Duncan

HTH

Duncan
Michael Tully
Honored Contributor

Re: Problem with FC Attached SureStore 2/20

Hi Duncan,

Thanks for posting the solution. I should have hit on it myself. In the past I've only ever installed firmware on servers, and should have suggested a CE do it. We had a CE do our 20/700 tape library and they blew up the system board. So I guess it can happen to anyone, whether it's the right version or not. Firmware is even more finicky than normal software patches.

Anyway, I'm glad you found the solution.

Cheers
~Michael~
Anyone for a Mutiny ?