Is A5149 compatible with DS21XX and DAT/DVD Devices?

[Alzhy]

'Been trying to resolve this problem we're having. My SCSI devices (DS21XX disks and DAt/DVD) always result in lbolt errors..

Even when igniting accross the LAN -- LAN boot Ignite, my ignite boot fails (and panics) as I think Ignite-UX tries to scan teh A5149's..

OS is 11.11 so these HBAs should still be supported.


Thanks.

[Torsten. · Accepted solution]

This ultry2 HBA should IMHO perfectly work.

Maybe you have a bad HBA/terminator/cable/switch?

[Alzhy]

Torsten,

Just found the Docu on the A5149.. it may possibly be a termination issue. It turns out this card has a jumper to enable/disable auto termination.

Our DS21XX and DAT/DVD strings are possibly not terminated -- relying instead on the SCSI HBAs auto termination features.

So hopefully tis is it.

[TTr]

I don't think there is a hardware compatibility issue here. Also check for flaky hardware, disks, tape drives, SCSI card, cables. Check if there is a SCSI ID conflict in the devices and also in the SCSI card itself in case it was changed form the original SCSI ID 7. Check if there is a server firmware upgrade as well.

[Torsten.]

Autotermination or not - this is just the HBA end of the bus.

Of course you MUST terminate the disk chassis end!

[Alzhy]

Torsten,

Are you saying even if the A5149 is set to atuotermination -- that the DS21XX must also need to be terminated?

The A5149 docu states:

Shorting these pins together causes automatic termination to be disabled. Termination for this bus must now be provided by some other SCSI device (e.g. disk, disk array, or other HBA, as required).

The DS21XX Docu also mentions termination depends on the HBA...

[Torsten.]

Are you saying even if the A5149 is set to atuotermination -- that the DS21XX must also need to be terminated?

Definitively yes.


The manual says

"When the adapter is used in High-Availability (HA) applications (such as MC/ServiceGuard) and it is required to be in the middle of the bus, the adapter's termination must be disabled."


Note: in the middle of the bus.

This was only used if there were internal or external connections are used or in unusual configurations like this (bus layout):

server_hba -> server_hba -> storage (Y-cable).

[Alzhy]

Torsten, the A5149s we were using were not set to auto termination (maybe they were used in a cluster before?). But our DS21XX and DVD/DAT modules are. So we set the A5149 to auto termination. But the same thing man.

On Ignition via DVD, Tape or Lan Boot -- the Ignite boot process always result in lbolt errors and panics. (See below).

I even tried to bring fown the nPar to just 1 Cell -- containing only my NIC and FC Card (an Ad193 that's hooked up to our SAN) but my LAN boot ignite is still resulting in lbolt errors. Note however that my one cell card still has an A5149 SCSI HBA that may probbaly still is set to not auto-terminate but it has no SCSI devices chained to it...

Any ideas man?


Main Menu: Enter command or menu > BO 6/0/4/0/0/6/0 install

BCH Directed LAN Path: 6/0/4/0/0/6/0.0.0.0.0


Do you wish to stop at the ISL prompt prior to booting? (y/n) >> n

Initializing boot Device.


Boot IO Dependent Code (IODC) Revision 3


Boot Path Initialized.


HARD Booted.

ISL Revision A.00.44 Mar 12, 2003

ISL booting hpux KernelPrompt "Choose an operating system to install that your hardware supports:" 120 1

Resetting boot device...



1. target OS is B.11.11
2. Exit

Choose an operating system to install that your hardware supports:1


Boot
: lan(6/0/4/0/0/6/0;0)/boot/Rel_B.11.11/WINSTALL
12283904 + 2244720 + 2718888 start 0x20c568





Stored message buffer up to panic:
-- lbolt: 3343, bus: 0
SCSI: Reset detected -- lbolt: 3346, bus: 0
SCSI: Reset detected -- lbolt: 3350, bus: 0
SCSI: Reset detected -- lbolt: 3353, bus: 0
SCSI: Reset detected -- lbolt: 3357, bus: 0
SCSI: Reset detected -- lbolt: 3360, bus: 0
SCSI: Reset detected -- lbolt: 3364, bus: 0
SCSI: Reset detected -- lbolt: 3367, bus: 0
SCSI: Reset detected -- lbolt: 3371, bus: 0
SCSI: Reset detected -- lbolt: 3374, bus: 0
SCSI: Reset detected -- lbolt: 3378, bus: 0
SCSI: Reset detected -- lbolt: 3381, bus: 0

[TTr]

> ...the A5149s we were using were not set to auto termination (maybe they were used in a cluster before?)
Did you check if the SCSI ID of the adapter was changed from 7 to 6? If as you say it might have been used in a cluster before, maybe its scsi id was changed and there is a conflict with the id of one of the disks?