Advanced Server cluster alias in single Alpha cluster

[Dave Gudewicz]

Wondered if it was really necessary to define an Advanced Server cluster alias in a VMS cluster that has only 1 Alpha.

We have a 4 node (3 Vax and 1 Alpha) cluster. Pathworks (of any flavor) is *not* running on any of the VAXen.

Since Advanced Server will not run on VAXen, why bother with the alias.

[Bojan Nemec]

Hi,

The cluster alias is not necessary. So you can work without it. But the cluster alias may be very useful in the future.
I give you an example:
You define connections to the Advanced Server using the alpha name. This can be done on a quite large number of PCs. Then you receive a new Alpha which will be in cluster with yours old Alpha and VAXes and will run Advanced Server. Now you will define the cluster alias and have to change all the PCs connections. If you define the cluster alias now, and all connections are made to that name, there will not be any work.

Bojan

[Dave Gudewicz]

Bojan,

Good point on the need of the alias if/when another Alpha joins the cluster.

Thanks,

Dave..

[Paul Nunez · Accepted solution]

Hi Dave,

The alias name is required (you can't remove it) in a cluster - even a single-node cluster - because the entire cluster is considered a single domain entity. The name of the machine/computer account created when in a cluster, will be the same as the alias name.

Having an alias name shouldn't present any issues...

HTH,

Paul

[Dave Gudewicz]

Thanks Paul.

Our issue with the alias was the underscore (_) used as the default; nodename_alias DNS server didn't like it.

The underscore (_) has be replaced with a dash (-) as the default; nodename-alias in later releases of Advanced Server, which is goodness.