Hi again Jan ,
OK that's clear.
Just a last question :
what is the risk when you write "rrp will not work as expected" ?
I've tested several times a ifdown on one IF eth / ring, and never
got a crash ... so what is the real risk ?
Thanks again
Alain
Hi,
"you can choose" ... meaning that it is not mandatory ? and my
configuration is correct anyway ?
No, your configuration is not correct. "You can choose..." means binary
OR. So (table)
same_mcast_addr | same_port +- 1 | works
----------------------------------------
0 | 0 | 1
0 | 1 | 1
1 | 0 | 1
1 | 1 | 0
Because somebody told me that it we put same mcastaddr it is written in
corosync documentation (but I can't find where)
that corosync may crash if one network becomes unreachable ... could you
confirm this or reassure me telling that it is not true ;-) ?
Yes, rrp will not works as expected.
Honza
Thanks
Alain
Moullé Alain napsal(a):
Hi,
corosync-1.4.1-7
with two rings in corosync.conf , and rrp mode active, is it recommended
to have two distinct mcastaddr ?
You can choose to have ether two distinct mcastaddr(eses) or distinct
ports (don't use port +- 1).
(and if so, where can I find this information ?)
It looks like it's not documented (thanks for that information, I will
add to my TODO) and sadly, corosync will not complain (this already
exists in TODO)
Regards,
Honza
or it is not important and we can have same mcast addr on both rings ?
Saying it in another way , is this sample correct :
interface {
ringnumber: 0
# The following three values need to be set based on your
environment
bindnetaddr: 182.128.3.0
mcastaddr: 239.0.0.1
mcastport: 5405
}
interface {
ringnumber: 1
# The following values need to be set based on your
environment
bindnetaddr: 182.128.2.0
mcastaddr: 239.0.0.1
mcastport: 5405
}
Thanks
Alain
_______________________________________________
Openais mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/openais
_______________________________________________
Openais mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/openais
