Re: [Linux-HA] heartbeat failover
Hello Arnold, yes, I recently found out that the sync-rate was to high for our old firewall. That are two datacenters, and all traffic is routed through this firewall. I don't know exactly why, this is the concept somehow. Do you know how to force another ip address on the other side? In heartbeat I was able to say, that the clusterip is another one as on the other node. In corosync/pacemaker I can't find such an example. Best regards Björn -Ursprüngliche Nachricht- Von: linux-ha-boun...@lists.linux-ha.org [mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Arnold Krille Gesendet: Samstag, 25. Januar 2014 01:46 An: linux-ha@lists.linux-ha.org Betreff: Re: [Linux-HA] heartbeat failover On Thu, 23 Jan 2014 16:45:04 + bjoern.bec...@easycash.de wrote: Uhhh..I got the same configuration as the example config you sent me now. But I cause high cpu load on our cisco asa firewall.. I guess this traffic is not normal? snip When you want your cluster to repair failures _fast_, the components have to sync their state _fast_. So they have to talk a lot, not in terms of megabytes but in terms of small packages with low latency in submission. So, yes that traffic is normal. Why is there a firewall between your nodes on the network where the cluster traffic happens? Have fun, Arnold ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] heartbeat failover
Hello,
I running corosync with success now.
But I got a problem, because I got two different subnet and I don't know which
ClusterIP I have to use.
I got 10.128.61.0 and 10.128.62.0, so a ClusterIP like 10.128.61.61 will not
routed in 10.128.62.0.
How I can use different ClusterIP's per side?
Best regards
Björn
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Becker, Björn
Gesendet: Donnerstag, 23. Januar 2014 17:45
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
Uhhh..I got the same configuration as the example config you sent me now.
But I cause high cpu load on our cisco asa firewall..
I guess this traffic is not normal?
root@node01:/etc/corosync# tcpdump dst port 5405
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:41:06.093140 IP node01.5405 node02.5405: UDP, length 70
17:41:06.097327 IP node02.5405 node01.5405: UDP, length 70
17:41:06.113418 IP node01.52580 node02.5405: UDP, length 82
17:41:06.286517 IP node01.5405 node02.5405: UDP, length 70
17:41:06.291095 IP node02.5405 node01.5405: UDP, length 70
17:41:06.480221 IP node01.5405 node02.5405: UDP, length 70 17:41:06.484520 IP
node02.5405 node01.5405: UDP, length 70
17:41:06.500608 IP node01.52580 node02.5405: UDP, length 82
17:41:06.673721 IP node01.5405 node02.5405: UDP, length 70
17:41:06.678654 IP node02.5405 node01.5405: UDP, length 70
17:41:06.867757 IP node01.5405 node02.5405: UDP, length 70
17:41:06.872492 IP node02.5405 node01.5405: UDP, length 70
17:41:06.888576 IP node01.52580 node02.5405: UDP, length 82
17:41:07.061664 IP node01.5405 node02.5405: UDP, length 70
17:41:07.066304 IP node02.5405 node01.5405: UDP, length 70
17:41:07.255409 IP node01.5405 node02.5405: UDP, length 70
17:41:07.260512 IP node02.5405 node01.5405: UDP, length 70
17:41:07.275601 IP node01.52580 node02.5405: UDP, length 82
Mit freundlichen Grüßen / Best regards
Björn
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Becker, Björn
Gesendet: Donnerstag, 23. Januar 2014 17:28
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Lukas Grossar
Gesendet: Donnerstag, 23. Januar 2014 16:54
An: linux-ha@lists.linux-ha.org
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 +
bjoern.bec...@easycash.de 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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] 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, bjoern.bec...@easycash.de 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
Re: [Linux-HA] heartbeat failover
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: linux-ha-boun...@lists.linux-ha.org [mailto:linux-ha-boun...@lists.linux-ha.org] 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, bjoern.bec...@easycash.de 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. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] heartbeat failover
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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Lukas Grossar
Gesendet: Donnerstag, 23. Januar 2014 16:54
An: linux-ha@lists.linux-ha.org
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 +
bjoern.bec...@easycash.de 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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] 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, bjoern.bec...@easycash.de 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
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] heartbeat failover
Uhhh..I got the same configuration as the example config you sent me now.
But I cause high cpu load on our cisco asa firewall..
I guess this traffic is not normal?
root@node01:/etc/corosync# tcpdump dst port 5405
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:41:06.093140 IP node01.5405 node02.5405: UDP, length 70
17:41:06.097327 IP node02.5405 node01.5405: UDP, length 70
17:41:06.113418 IP node01.52580 node02.5405: UDP, length 82
17:41:06.286517 IP node01.5405 node02.5405: UDP, length 70
17:41:06.291095 IP node02.5405 node01.5405: UDP, length 70
17:41:06.480221 IP node01.5405 node02.5405: UDP, length 70
17:41:06.484520 IP node02.5405 node01.5405: UDP, length 70
17:41:06.500608 IP node01.52580 node02.5405: UDP, length 82
17:41:06.673721 IP node01.5405 node02.5405: UDP, length 70
17:41:06.678654 IP node02.5405 node01.5405: UDP, length 70
17:41:06.867757 IP node01.5405 node02.5405: UDP, length 70
17:41:06.872492 IP node02.5405 node01.5405: UDP, length 70
17:41:06.888576 IP node01.52580 node02.5405: UDP, length 82
17:41:07.061664 IP node01.5405 node02.5405: UDP, length 70
17:41:07.066304 IP node02.5405 node01.5405: UDP, length 70
17:41:07.255409 IP node01.5405 node02.5405: UDP, length 70
17:41:07.260512 IP node02.5405 node01.5405: UDP, length 70
17:41:07.275601 IP node01.52580 node02.5405: UDP, length 82
Mit freundlichen Grüßen / Best regards
Björn
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Becker, Björn
Gesendet: Donnerstag, 23. Januar 2014 17:28
An: linux-ha@lists.linux-ha.org
Betreff: Re: [Linux-HA] heartbeat failover
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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Lukas Grossar
Gesendet: Donnerstag, 23. Januar 2014 16:54
An: linux-ha@lists.linux-ha.org
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 +
bjoern.bec...@easycash.de 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: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] 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, bjoern.bec...@easycash.de 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
[Linux-HA] heartbeat failover
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 ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
