billg@bony1.bony.com (Bill Gripp) (05/23/91)
We have a "Hardware VAXcluster" where 3 nodes are running off the same Star Coupler and set of HSC's. VAXCLUSTER is set to 1 on only one of the nodes, but our boot procedures are such that we cannot cross mount (and hence trash) disks between the systems. The situation is: NODE VMS VAXCLUSTER ---- --- ---------- M 4.7 1 A 5.4 0 P 5.4 0 For a number of reasons, node M must remain at VMS V4.7 for the rest of this year. I want to set VAXCLUSTER to 0 on M and to 1 on P and A and form a true cluster between P and A. When M is upgraded to V5.4 it will be added to the cluster as well. Here is the problem. When I set VAXCLUSTER to 0 on M and reboot, M can no longer "see" any of the HSC50's or their disks! It can still see the HSC70's though. The two V5.4 systems see all the HSC's and all their disks. Anybody else ever seen this??? More important anybody have a fix??? Thanks for all replies. Bill