<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div class="plainMail"><br>>> Hi,<br>>><br>>> I have two network cards and configured corosync-1.2.7 with<br>>> rrp_mode: active<br>>><br>>> at first corosync-cfg -s tells me<br>>> Printing ring status.<br>>> Local node ID 1210452490<br>>> RING ID 0<br>>> id = 10.10.38.72<br>>> status = ring 0 active with no faults<br>>> RING ID 1<br>>> id = 10.10.40.115<br>>> status = ring 1 active with no faults<br>>><br>>> after a very short time I see the following:<br>>><br>>> RING ID 1<br>>>
id = 10.10.40.115<br>>> status = Incrementing problem counter for seqid 1352 iface<br>>> 10.10.40.115 to [3 of 10]<br>>><br>>> and finally:<br>>> RING ID 1<br>>> id = 10.10.40.115<br>>> status = Marking seqid 1390 ringid 1 interface 10.10.40.115 FAULTY -<br>>> adminisrtative intervention required.<br>>><br>>> Anybody being successful at all using rrp_mode with corosync?<br>>> <br>>I use rrp_mode: active with two network bonds (4 network cards) and what <br>>I can tell you is that when I perform tests by shutting down the switch <br>>ports for one of the bonds, it starts to increment the counter then <br>>marks the ring as faulty, just as you mentioned, which is normal because <br>>I just shut the
ports.<br><br>>If you're encountering this without having network connectivity <br>>problems, then yes, it's an issue, otherwise, when the connection per <br>>ring is lost, that's the normal output.<br><br>>Also when the network connectivity is restored the ring doesn't restore <br>>it's previous condition automatically, it's a feature to be implemented <br>>in the corosync 2.y.z branch (a.k.a. Weaver's Needle). For now after <br>>restoring the network connectivity to get the ring back you either do a <br>>corosync-cfgtool -r or have some script monitor and do it for you.<br><br></div><div class="plainMail">I also consider use rrp_mode. If two network the bindnetaddr and mcastport is same only mcastaddr is different. is it ok?</div></blockquote></td></tr></table><br>