--TRYliJ5NKNqkz5bu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 09, 2005 at 03:37:01PM -0400, der Mouse wrote:
>=20
> What I was looking for was a way to connect two devices, each of which
> thinks it's at ID 7, without producing a conflict.  It appears there
> more or less is no such way (since swapping the wires produces an
> arbitration conflict by breaking the assumption that any given device
> is at the same ID as seen by all devices); the best suggestion seems to
> be mycroft's, to have at least one of the hosts change its SCSI
> interface's ID.

You probably want both of them to change their ID. The problem is that=20
initial chip bringup may set a device's ID to 7 and driver config later=20
sets it to the correct ID. Like a motherboard SCSI firmware may set to ID=
=20
7 and it's the OS later that sets the right ID.

So if one device uses ID 7 normally, you can get conflicts while the other=
=20
box is (re)booting.

The joys of how you do this are one of the reasons folks came up with=20
SANs. :-)

Take care,

Bill

--TRYliJ5NKNqkz5bu
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFC+UbIWz+3JHUci9cRAso1AKCA4rolT9Sa1GUrGccTdITg0Pi/yQCeLav/
1MLzUY6RMr1jAY8YF1Afzds=
=BkCF
-----END PGP SIGNATURE-----

--TRYliJ5NKNqkz5bu--