my client has an "old" L9 that has been identified as part of a b/up
solution in a new system/project.

On the rear of the L9, where the scsi cable connections is that
provides the connection to the host system is a sticker that says
"SCSI 3" - nobody actually knows what this means or why it is there.

If we connect the L9 to the host system (V440), the host system
doesn't even boot ... w/out the L9 connected we can see that scsi ids
already in use on the system are 0,1,2 ... and 3 (disk controllers).

So - our theory is that there is a scsi id clash that is preventing
the boot/causing headaches - and that in all likelihood the clash is
on scsi id 3 (hence the sticker). The answer therefore would
presumably be to change this scsi id to (say) 6. However, I can't
find out how to do it!!

The front panel menu thingy only provides for two scsi ids to be
changed, the autoloader controller and the drive - which are set to 0
and 1 respectively. So they are clearly not the "rogue" scsi id of
3...

So - are barking up th wrong tree completely? Or is it that we are
indeed right - but need to know how to change the clashing id?

any help greatfully appreciated!

ian

In comp.unix.solaris Ian Diddams <didds2@excite.com> wrote:
> my client has an "old" L9 that has been identified as part of a b/up
> solution in a new system/project.
>
> On the rear of the L9, where the scsi cable connections is that
> provides the connection to the host system is a sticker that says
> "SCSI 3" - nobody actually knows what this means or why it is there.

> If we connect the L9 to the host system (V440), the host system
> doesn't even boot ... w/out the L9 connected we can see that scsi ids
> already in use on the system are 0,1,2 ... and 3 (disk controllers).

> So - our theory is that there is a scsi id clash that is preventing
> the boot/causing headaches - and that in all likelihood the clash is
> on scsi id 3 (hence the sticker). The answer therefore would
> presumably be to change this scsi id to (say) 6. However, I can't
> find out how to do it!!

Or that the device is HVD scsi and incompatible with the V440 onboard.
When connected, can you do a 'probe-scsi-all' from the OBP? What output
do you get.

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

problem sorted - it was a duff cable!

cheers

Ian