Hello [snip] >> >> No loop? Because S2 will receive DR method in >> the SYNC messages for its stack. You see traffic flow >> or just that there is no reset? > >Yes, after the failover, all connections that were open on the S2 (which >now becomes the active balancer) do not reset and continue to function >just fine (traffic flow in both directions). > >We do understand (we think) your explanation about the sync table >problem - the connections to the actual balancer are marked in a >special way, which causes problems when these connection table records >are used on a new balancer. > >It looks like updating the kernels is the only way, if (as you and Hans >Schillstrom outlines) even the latest CentOS/RedHat kernels do not >contain necessary patches. It's a pity, as the idea was to provide an >"out of the box" solution for our customers, and asking them to update >to some Linux kernel is not what they like to hear. > >But thank you very much in any case, we will update the kernels on our >test systems and will see if this (last?) problem disappears. > There is newer kernels floating around in the 3.x range Have a look at ELRepo Project there you can find a 3.5.x kernel that have all necessary changes. BR Hans -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
