mix 2 Clusters

[labadie_1]

As I have not done this for a long time, I would like some advice.

I have a Cluster with a Alpha Server 800 (voting for 1) and a satellite (voting for 1).
I have a DS15 that I have declared as a member of (another) Cluster, voting for 1.

Now I want that the DS15 joins the Cluster of the AS 800.
The DS15 will not share disks with the AS 800, it is just the fact that they are in the same Cluster that I want (have cluster logical names, nodes in the same cluster...)

I was wondering if I had to go with cluster_config, or if I could just copy the file cluster_authorize.dat from the AS 800 to the DS15 and reboot the whole Cluster (or just the DS15).

Thanks for any hint.

Gerard

[Kris Clippeleyr · Accepted solution]

Gerard,

Basically, if the interconnects are established (for instance a LAN), I see no reason that simply copying the SYS$COMMON:[SYSEXE]CLUSTER_AUTHORIZE.DAT from the AS800 to the DS15 would not work if the DS15 has it's own system disk. No need to boot the cluster, just boot the DS15.
You have to be careful though, and examine the SYSTARTUP of the DS15. Things that come to mind are: disk naming, ALLOCLASS, queue database, SYSUAF, RIGHTSLIST, etc.

But wouldn't it be more simple to add the DS15 to the AS800 cluster as a satellite, and do a MOP-boot on the DS15?

Greetz,

Kris

[labadie_1]

Kris

The DS15 and the AS 800 are on the same Lan.

Th idea of this set-up is that the DS15 and the AS800 can switch (production and test nodes). I want to be able to shutdown the AS800 and still have the DS15 working.

The main appli is a Rdb database, and I have procedures for Rdb hot standby that are designed for nodes in a Cluster.

>>>Things that come to mind are: disk naming, ALLOCLASS, queue database, SYSUAF, RIGHTSLIST, etc.

Yes, and a common licence database, and...

Thanks

Gerard

[Kris Clippeleyr]

Gerard,

I overlooked something: the satellite.
If you shut down the AS800, the satellite is also gone, because the system disk is served by the AS800 to the satellite, and with 2 voting members gone from a 3-votes cluster, you definitely have "quorum lost".

Kris

[labadie_1]

Sorry I was wrong when saying satellite: the "satellite" is a station that is here for voting for 1, has its own system disk, and does nothing else.

So I think it will work.

[Uwe Zessin]

You don't need to reboot the existing cluster(s) - just the DS15.

Take a look at the file SYLOGICALS.TEMPLATE in SYS$MANAGER: - it gives some good hints about files that can/should be shared in a VMS cluster.

[Ian Miller.]

In addition to whats already mentioned
check for conflicts in SYSUAF and RIGHTSLIST (e.g different user, same UIC)

[John Gillings]

Gerard,

Copying cluster_authorize will work - it's the "standard" way to add a node when you don't know the cluster password (though if you don't know the cluster password, now is probably a good time to set it).

Your new node does not *need* to vote, and from the situation you've described, it probably shouldn't. The only reason you'd need to boot the other nodes is if NISCS isn't enabled. Otherwise, just add the new node to the existing cluster.