Multi-homing in rhel5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The cluster2 docs outline a procedure for multihoming which is
unsupported by redhat.

Is anyone actually using this method or are people more inclined to
use configs in which secondary interfaces are given names by which the
cluster then uses them as primary config nodes.

For example, on my cluster I have eth0 as the primary interface for
all normal system traffic, and eth1 as my cluster interconnect.

eth0 - nodename
eth1 - nodename-clu <-- cluster config points to this as nodes....

clients access the cluster services via eth0.

I've seen other configs where people configure the cluster to use eth0
for cluster coms so that ricci/luci work correctly, but I don't use
those.

Is there an advantage of one method over the other ?

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux