Adrian Gibanel napsal(a):
Even as I've described that they are both in totally different networks?
Yes. Even it purely theoretically it can work (udp side), corosync is
sending message which includes list of known nodes, and two
192.168.58.10 will simply not work.
Also keep in mind that redirecting 5405 is not enough. Corosync is also
using port - 1.
I believe what are you trying to achieve is stretch cluster, what is not
very well covered/tested field, so I really can't guarantee that
changing internal IP will work (and I personally think it will not).
Honza
Thank you.
Although both nodes have the same 192.168.58.10 as you might see in the logs
they live in two different networks... I mean...
there's no problem about 192.168.58.10 begin repeated as far as I know.
----- Mensaje original -----
De: "Jan Friesse"<jfriesse@xxxxxxxxxx>
Para: "Adrian Gibanel"<adrian.gibanel@xxxxxxxxxxx>
CC: discuss@xxxxxxxxxxxx
Enviados: Lunes, 20 de Agosto 2012 11:26:36
Asunto: Re: Help on debugging corosync communication
So,
first problem is, that both of corosync nodes have same ip addrs.
Corosync nodes MUST have different addresses (so let's say
192.168.58.1
and 192.168.58.2). You must configure them in so, so:
interface {
member {
memberaddr: 192.168.58.1
}
member {
memberaddr: 192.168.58.2
}
ringnumber: 0
bindnetaddr: 192.168.58.0
mcastport: 5405
}
I believe that main problem is, that you think that corosync is
responsible for keeping service IP (so let's say 192.168.58.10). It's
not, this is job for pacemaker and resource scripts.
So first, ensure you have really 2 different IPs on your nodes, you
can
ping them, then configure corosync correctly and I believe everything
will start working as expected.
Honza
Adrian Gibanel napsal(a):
Short description
---------------------
...
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
