LUN scanning

[Clint Gibler]

I need to know how to find out if the scsi card I am trying to attach my new HP 1/8 autoloader 232 Ultrium to my HP 9000 rp5405 hpux 11.00 supports LUN scanning and if so how to make sure it is enabled. The EBS matrix did not help and the card shows up as SCSI C896 Ultra Wide LVD under the ioscan.

[Steven E. Protter]

Shalom Clint,

SAN disk, once assigned to the ownership of a fiber card it is just another scsi device.

You may have an address conflict between the SCSI C896 and the Fiber card.

Seeing all the ioscan output would be helpful in resolving your question.

SEP

[Clint Gibler]

The card I have it attached to is 0/0/1/0 but as you can see the autoloader is not showing up. I am not sure what you mean by the fibre channel interfering I don't think I have any fibre channel hardware. This card had a different tape drive hooked up to it before and it worked fine.


H/W Path Class Description
====================================================
root
0 ioa System Bus Adapter (803)
0/0 ba Local PCI Bus Adapter (782)
0/0/0/0 lan HP PCI 10/100Base-TX Core
0/0/1/0 ext_bus SCSI C896 Ultra Wide LVD
0/0/1/0.7 target
0/0/1/0.7.0 ctl Initiator
0/0/1/1 ext_bus SCSI C896 Ultra Wide Single-Ended
0/0/1/1.2 target
0/0/1/1.2.0 disk HP 36.4GMAM3367MC
0/0/1/1.7 target
0/0/1/1.7.0 ctl Initiator
0/0/2/0 ext_bus SCSI C875 Ultra Wide Single-Ended
0/0/2/0.2 target
0/0/2/0.2.0 disk HP 36.4GMAM3367MC
0/0/2/0.7 target
0/0/2/0.7.0 ctl Initiator
0/0/2/1 ext_bus SCSI C875 Fast Wide Single-Ended
0/0/2/1.2 target
0/0/2/1.2.0 disk HP DVD-ROM 305
0/0/2/1.7 target
0/0/2/1.7.0 ctl Initiator
0/0/4/0 tty PCI BaseSystem (103c128d)
0/0/4/1 tty PCI Serial (103c1048)
0/1 ba Local PCI Bus Adapter (782)
0/2 ba Local PCI Bus Adapter (782)
0/3 ba Local PCI Bus Adapter (782)
0/4 ba Local PCI Bus Adapter (782)
0/5 ba Local PCI Bus Adapter (782)
0/8 ba Local PCI Bus Adapter (782)
0/9 ba Local PCI Bus Adapter (782)
0/10 ba Local PCI Bus Adapter (782)
0/10/0/0 ext_bus SCSI C1010 Ultra160 Wide LVD
0/10/0/0.0 target
0/10/0/0.0.0 disk HP 36.4GMAN3367MC
0/10/0/0.1 target
0/10/0/0.1.0 disk HP 36.4GMAN3367MC
0/10/0/0.2 target
0/10/0/0.2.0 disk HP 36.4GMAN3367MC
0/10/0/0.3 target
0/10/0/0.3.0 disk HP 36.4GMAN3367MC
0/10/0/0.4 target
0/10/0/0.4.0 disk HP 73.4GST373405LC
0/10/0/0.5 target
0/10/0/0.5.0 disk HP 73.4GST373405LC
0/10/0/0.7 target
0/10/0/0.7.0 ctl Initiator
0/10/0/0.15 target
0/10/0/0.15.0 ctl HP A6491A
0/12 ba Local PCI Bus Adapter (782)
32 pbc Bus Converter
33 processor Processor
96 pbc Bus Converter
97 processor Processor
192 memory Memory

[Steven E. Protter]

Okay Clint,

I understand now.

There may be a san configuration problem preventing the autoloader from showing up.

AS I recall, the device can be shared on a scsi connection and a SAN/Fiber connection.

Since we're working with SCSI, I would surmise that the SCSI ID of the autoloader is not compatible with the SCSI ID of the card.

I'd check the SCSI Id of the autoloader. There may be a procedure with the autoloader doc that would be helpful.

SEP

[Clint Gibler]

I checked and the scsi id is set to 5 and the old tape drive I chained off of it is set to 6, now one of the guys I work with said I should take that other drive off and terminate the scsi on the drive, which I am planning on doing however when I use the hp troubleshooting it tells me to make sure that LUN scanning and/or multiple LUN support is turned on and that it is disabled by default and the tape drive won't work without it. I cannot find out how or where to check and see if the machine supports it or if it is turned on.

[A. Clay Stephenson]

I haven't used your particular AutoLoader but in general there is a SCSI Target ID associated with each tape drive and a separate SCSI Target ID associated with the robotics device. Since the system doesn't "see" either (and it should if properly configured), I would check cabling, termination, (there must be exactly 2 terminators on the bus -- at the physical ends of the bus), termination power -- at least one device on the bus must supply it, and finally that the tape drive and robotics are not misconfigured and share a common target ID. A comon target id is only possible if the drive and robotics differ by LUN number.

[Steven E. Protter]

Clint,

With no auto loader to play with, I'm out of ideas.

http://h40132.www4.hp.com/upload/se/sv/StorageOverview.pdf

Slim picking in google as well.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=893726

I would suggest you either wait for other answers or contact your HP Response Center. They have specialists on this hardware that should be able to help.

I'm assuming that the normal trouble checklist like checking cables and such has been done.

The HP-9000 server has been booted since the auto loader was connected?

Bowing out. Good Luck.

SEP

[David Bellamy]

Clint try changing the SCSI ID on the autoloader,I had the same problem once and changing the ID fixed it.

[A. Clay Stephenson]

By the way, you are not doing an "ioscan -k" are you? In that case, new devices would not be visible. Do an ioscan -fn and see if the new devices appears.