[Info-vax] Third node into 2-node cluster

[Richard B]

On Tuesday, March 26, 2019 at 9:20:37 AM UTC-4, Richard B wrote:
> Morning all,  (Or afternoon!)
> 
> I currently have 2x 2-node VMS clusters running v8.4 on rx2600 i2 boxes. It is configured as an NI cluster.
> 
> My company purchased 2x rx2660 boxes to add to the existing clusters to make each a 3-node cluster.
> 
> The main function of the 3rd node will be to provide quorum, enabling me to do away with the quorum disk.  That is basically the 3rd nodes only function aside from some assorted maintenance tasks.  The 3rd node will boot from its own SYSTEM disk, and not from the existing system disk which is shared by the existing 2 nodes.
> 
> When I want to add this third node to the mix, should I run CLUSTER_CONFIG or CLUSTER_CONFIG_LAN?  I ask because I've always build clusters using one system disk so this is sort of new to me.  Anything I should look out for?
> 
> (The new 3rd nodes have been built with v8.4 and all patches associated with it. They are currently up and running on the Network but have not been configured as a cluster member.  I now I need to set the SYSGEN param VAXCLUSTER to 2)
> 
> Thanks in advance.
> 
> R

Thanks all for the great advice.  However, I'm not sure I understand why I would want to point any logicals to the existing 2-node cluster.  This third node will be a voting/quorum member only.  That will be it's only function.  No one, aside from me, will log into it, no one will use any of its resources, nada, nothing, zilch.  (It will, however, suck power!). It has it's own system disk, will have VOTES=1 set and any disks on the existing 2-node cluster (MSCP-served) may well be mounted on this new node but not shadowed with this 3rd node.  Or am I missing something?

Again, thanks for all the advice/suggestions.