Hi Lukas,
thank you. Well, I've to wait for some firewall changes for 5405 UDP.
But I'm not sure if it's correct what I'm doing.
Node1:
interface {
member {
memberaddr: 10.128.61.60 # node 1
}
member {
memberaddr: 10.128.62.60 # node 2
}
# The following values need to be set based on your environment
ringnumber: 0
bindnetaddr: 10.128.61.0
mcastport: 5405
}
transport: udpu
Node2:
interface {
member {
memberaddr: 10.128.61.60
}
member {
memberaddr: 10.128.62.60
}
# The following values need to be set based on your environment
ringnumber: 0
bindnetaddr: 10.128.62.0
mcastport: 5405
}
transport: udpu
Something seems to be wrong defenitly. My firewall was on very high load...
Mit freundlichen Grüßen / Best regards
Björn
-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Lukas Grossar
Gesendet: Donnerstag, 23. Januar 2014 16:54
An: [email protected]
Betreff: Re: [Linux-HA] heartbeat failover
Hi Björn
Here ist an example how you can setup corosync to use Unicast UDP:
https://github.com/fghaas/corosync/blob/master/conf/corosync.conf.example.udpu
The important parts are "transport: udpu" and that you need to configure every
member manually using "memberaddr: 10.16.35.115".
Best regards
Lukas
On Thu, 23 Jan 2014 13:36:22 +0000
<[email protected]> wrote:
> Hello,
>
> thanks a lot! I didn't know about heartbeat is almost deprecated.
> I'll try corosync and pacemaker, but I read that corosync need to run
> over multicast. Unfortunately, I can't use multicast in my network.
> Do you know any other possibility, I can't find anything that corosync
> can run without multicast?
>
>
> Best regards
> Björn
>
> -----Ursprüngliche Nachricht-----
>
> Von: [email protected]
> [mailto:[email protected]] Im Auftrag von Digimer
> Gesendet: Mittwoch, 22. Januar 2014 20:36 An: General Linux-HA mailing
> list Betreff: Re: [Linux-HA] heartbeat failover
>
> On 22/01/14 10:44 AM, [email protected] wrote:
> > Hello,
> >
> > I got a drbd+nfs+heartbeat setup and in general it's working. But it
> > takes to long to failover and I try to tune this.
> >
> > When node 1 is active and I shutdown node 2, then node 1 try to
> > activate the cluster. The problem is, node 1 already got the primary
> > role and when re-activating it take time again and during this the
> > nfs share isn't available.
> >
> > Is it possible to disable this? Node 1 don't have to do anything if
> > it's already in primary role and the second node is not available.
> >
> > Mit freundlichen Grüßen / Best regards Björn
>
> If this is a new project, I strongly recommend switching out heartbeat
> for corosync/pacemaker. Heartbeat is deprecated, hasn't been developed
> in a long time and there are no plans to restart development in the
> future. Everything (even RH) is standardizing on the
> corosync+pacemaker stack, so it has the most vibrant community as
> well.
>
--
Adfinis SyGroup AG
Lukas Grossar, System Engineer
Keltenstrasse 98 | CH-3018 Bern
Tel. 031 550 31 11 | Direkt 031 550 31 06
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
