[Linux-HA] two node firewall using heartbeat v2 problems [SOLVED]

[Andrew Beekhof]

On 10/1/07, Matt Zagrabelny <mzagrabe at d.umn.edu> wrote:
>
> On Mon, 2007-10-01 at 14:37 +0200, Andrew Beekhof wrote:
> > On 10/1/07, Dejan Muhamedagic <dejanmm at fast
>
> [...]
>
> > > > (there will be no <status/> element in the following file, I believe
> > > > that this is due to me manually 'kill -9'ing the processes after they
> > > > would not stop nicely)
> > >
> > > No, the status section is never saved to a file. It only exists
> > > in running nodes.
>
> I know that the actual status doesn't get written out, but doesn't the "<status/>" tag get written out when the processes exit?

nope


> > one of the nice things about v2 is that it keeps the resource config
> > in sync between nodes.  however this also includes the status section
> > and means that the data being transferred could quite conceivably
> > max-out a serial connection.
> >
> > a second NIC and a crossover cable is usually a good alternative
>
> I am already using a pair of NIC's (between the nodes) for heartbeat, in
> addition to the serial link. Are you suggesting using two NIC's per node
> to send heartbeat messages?

this is possible yes

> Are the status messages sent across both links? (ie. do they go across
> the serial link and the ethernet link between the nodes?) I would assume
> they would, but I thought I would ask for clarification.

to be honest, i dont know how heartbeat does its comms.
maybe someone else can answer this

> > > heartbeat[18326]: 2007/09/28_11:29:56 CRIT: Cluster node tim returning after partition.
> > >
> > > The node is leaving and coming back. Looks like the
> > > network/serial connection doesn't deliver what we expect. Perhaps
> > > you could try some other combinations:
> > >
> > > - without serial/higher baud
>
> Yes! Both of these solutions fix the problem. Should the default baud
> rate for a serial line be higher than 19200? What baud rate do others
> use for v2 heartbeat configurations? The reason I ask is that currently
> I have it set to 115200 and I am wondering if I am just above the
> threshold of saturating the serial link. Perhaps I will run some tests
> as well to see when the serial link gets saturated and report the
> findings.

not a bad idea, it will depend on the number of resources in your cluster.