I'd like to know best practice on this too. It's always seemed a bit unclear to me how to configure this if fail over is used "alt-name". Or how good or quick the failover is or worth it over bonding. Colin On Thu, 2011-02-03 at 10:49 +0000, Corey Kovacs wrote: > 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 > > This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
