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
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
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
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 {
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
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
