Setting scsi-initiator-id
In a two node cluster setup using two V440 servers and shared SCSI SE 3320 storage with Solaris 9, regarding the PROM setting "scsi-initiator-id" , the first node is not changed (7) , and in the second node I changed using:
# eeprom scsi-initiator-id=6
Now, since the built-in on-board SCSI-connector is used (the HBA LVD ultra-320 scsi is used for another storage box since we have two SE 3320 storage boxes), is it possible that the chosen value for the scsi-initiator-id (6) will interfere with the internal cdrom(dvd) drive? How can I check the scsi target value of the internal cdrom(dvd) drive? and if the internal cdrom drive is using scsi target (6) what value can I use in the second server to reomve the conflict ob the storage scsi chain?
[768 byte] By [
goSolarisa] at [2007-11-27 3:35:30]
# 3
Thanks Tim
The issue here is that the shared storage SE 3320 is connected to the on-board HBA which I think is the same SCSI bus connected to the local internal disks (and cdrom).
As in the document you supplied, in step 5.e, the doument resets the scsi-initiator-id to (7) for the the HBA connected to the internal disks, in our case this is the HBA connected to the shared storage.
I think the question here is: the on-board SCSI interface, is it the same SCSI bus used by the internal disks and cdrom? if yes then can it be used to connect the servers to the shared SCSI storage SE 3320?
# 4
Don't be concerned about the optical drive in the V440 system.
It's an IDE device.
Consequently, there is no SCSI target ID associated with it.
The internal drives will remain on their own controller ( cXtYdZ ) for their target ID's.
Any external SCSI devices will have device paths for another controller.
They're pathed on a different `leaf` of the SCSI chipset.
It just works.
Use your Sunsolve login account and glance through Infodoc 21216.
"Solaris[TM] Operating System: Matrix of Recognized Device Paths"
