Hi Thanks. Effectively,I saw this in documentation but in fact, my question was more precisely : if we have two eth interfaces eth0 and eth1 , and we don't want the heart beat goes through eth1 in any case, even if the CS4 has to failover in case of eth0 failure, is there a way in CS4 configuration to avoid eth1 ? or do we have to disable Broadcast (or Multicast if choosen in CS4 configuration) at the eth interface configuration ? Thanks Alain Lon Hohberger wrote: > On Thu, 2005-09-22 at 08:15 +0200, Alain Moulle wrote: > >>Hi everybody >> >>Some questions about heart-beat under Cluster Suite 4 : >> >>1. how is choosen the eth interface under CS4 ? >> if we have eth0 and eth1, it seems that HearBeat >> goes through eth0 and we don't have the possibility >> to configure this in CS4 , right ? >> >>2. does that mean also that if eth0 fails, the CS4 >> automatically goes through eth1 ? >> >>3. do I miss the way to configure this via GUI ? > > > One easy way to do this is to use bonded interfaces, which will provide > failover transparent to the cluster. > > -- Lon > > -- mailto:Alain.Moulle@xxxxxxxx +------------------------------+--------------------------------+ | Alain Moullé | from France : 04 76 29 75 99 | | | FAX number : 04 76 29 72 49 | | Bull SA | | | 1, Rue de Provence | Adr : FREC B1-041 | | B.P. 208 | | | 38432 Echirolles - CEDEX | Email: Alain.Moulle@xxxxxxxx | | France | BCOM : 229 7599 | +-------------------------------+-------------------------------+ -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
