This is mostly an opinion question. The dedicated heartbeat cable, I envision as a legacy throw back to serial cables.
You could argue using quality of service QOS to partition one physical cable and guarantee bandwidth to both applications. You could three network cards (crossover HA) (crossover DRBD) (General data) People might get mad at me for saying this (and you might as well) but I would put the DRBD replication on the dedicated cable and the heartbeat on the same network. Here is why: 1) DRBD has the potential to transmit ALOT of data, passing all the data between a switch may actually burden the backplane affecting all the other hosts on the switch. 2) HA does not really produce a lot of data. The odds of UDP HA packets getting lost are very slow. I **think** the ideal deployment would be bonded ethernet and QOS control for one logical network. However this is also the most sophisticated deployment. I am a firm believer in Core - data - access and !never! having a host on two logical networks. Practically, DRBD on your general switch could saturate the backplane of the switch so avoid the LAN network for that. On Mon, Feb 25, 2008 at 3:09 PM, Doug Lochart <[EMAIL PROTECTED]> wrote: > I am testing my first cluster of 2 machines each with 2 gigabit ethernet > cards. > > eth1: crossover cable; primary heartbeat link bcast > eth0: connected to LAN; drbd replication path and secondary heartbeat > link bcast > > Is it better to have the drbd replication go over the crossover able > instead of LAN? > > is this a better configuration?: > > eth1: crossover cable; drbd replication pathand secondary heartbeat link > bcast > eth0: connected to LAN; primary heartbeat link bcast > > thanks! > > regards, > > Doug > > -- > What profits a man if he gains the whole world yet loses his soul? > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
