Thanks for the quick response. Well, I learned something
today... Of course, I always set 7 and 8 for scsi IDs and
my customer set 15, and I never thought to go lower
than 7. That is the summary/solution.
SCSI ID's for DU4.0 must be 0-7. Silly me.
I did get a couple of responses, which I feel I must
correct, cause I know this is not true and perhaps it
will help others.
The shared scsi controllers do NOT have to be in the
same config/slot on the different machines. The kernel
config takes care of software IDs and changing them to
match. I appreciate those answers, but they were
incorrect.
Thanks again to all for a great list... I still believe this
list makes many "support" groups look really bad...
cheers
rich
At 01:06 PM 9/23/99 -0400, you wrote:
>Hi,
>This cluster is being a pain -- one more question please....
>
>Two DS20s and 1 RA3000
>2 PKZBA controllers w/TERMs removed.
>2 Y cables, one W external TERM.
>
>SCSI host ID's have been changed -- 7 and 15
>
>The cluster can now configure, BUT only on the
>net. The SCSI ping keeps failing and if I run
>cluster_map_create, it tells me the scsi configs are not
>symmetric. I think they are, but it tells me otherwise.
>
>NOW, from either machine, the drives can be mounted
>and used separately with NO problems... But if you try,
>as mentioned above to get a cluster map, OR create a
>DISK-service, it will only start on one system or the other,
>but will not failover.
>
>The EXACT same controllers and drives work with AS 300/4-266's
>but not with the DS20's. Is there something about the 20's that
>would cause this? The same controllers are in the AS 300's.
>
>thanks
>r
>
>
Received on Thu Sep 23 1999 - 23:53:40 NZST