🚀 go-pugleaf

In article <1ao5keINNr45@gap.caltech.edu>, mccaslin@cco.caltech.edu (Stanley John McCaslin) writes:
>I am just installing MX on a vaxcluster, one of whose nodes
>violates the condition for a homogeneous MX-cluster in that
>it has its own UAF.  Has anyone done this, and if so could you
>advise me what files need to be specific to that node?  The
>manual seems pretty clear on homogeneous clusters, but this
>is not my situation.

The reason it's not clear in the heterogeneous case is because there are
many differing levels of heterogeneity.  If you have a different UAF, but
you keep the usernames and UIC's the same as in your main sub-cluster,
and you still share the same VMSMAIL_PROFILE.DATA file, and you share
the same disk space, you can probably treat the cluster as homogeneous --
just don't run any of the MX processing agents (or at least not the Router
and Local delivery agents) on the heterogeneous node.

The easiest thing to do in the completely heterogeneous case (separate
UAF, separate VMSMAIL_PROFILE.DATA, different user base entirely) is
to install MX separately on the heterogeneous node, give it an "MX Cluster
Name" that is different from the main sub-cluster, and make sure it also has
a different "MX Network Host Name" from the main sub-cluster.

What you do for an in-between case will depend on how heterogeneous your
cluster is.

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA