[ClusterLabs] Antw: Re: EL6, cman, rrp, unicast and iptables

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Mon Sep 14 02:16:27 EDT 2015

>>> Noel Kuntze <noel at familie-kuntze.de> schrieb am 11.09.2015 um 20:40 in
Nachricht <55F32039.9010102 at familie-kuntze.de>:

> Hash: SHA256
> Hello,
> Personally, I would set filters in tc (packet priorization/shaper part of 
> the network stack)
> to prioritize Cluster packets. That way, delivery of the packets is basicly

> guaranteed. I'd do something similiar
> on the switch to make sure it prioritizes the packets, too.
> The migration traffic must always have a lower priority than the traffic if

> cman and the other components,
> so the totems get delivered in any case.


Actually I don't understand that claim: If packets are delivered in order
(mostly), any TOTEM packet has the same change to arrive than any other packet.
While all other communication protocols can actually deal with Ethernet and the
Internet, TOTEM is the only protocol that can fail even in a switched LAN. I
haven't benn convinced yet that it's not an implementation issue of TOTEM.
Instead of telling people to fiddle with their network configuration, I'd
prefer putting more efforts into fixing TOTEM.

> The default queuing behaviour is FIFO. This is obviously not desireable 
> here.
> If the preset queuing mechanism supports traffic priorization, you can 
> possible get away with
> a single set of iptables DSCP/TOS rules in *mangle OUTPUT to set the correct

> value
> so the queue prioritizes it.

The main problem with priorities is who decides what is most important,
especially if a medium is shered by many different software stacks and


> - -- 
> Mit freundlichen Grüßen/Kind Regards,
> Noel Kuntze
> GPG Key ID: 0x63EC6658
> Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658
> Version: GnuPG v2
> JCHjZKFYREM0E9MYESLxYmm0Ipvjy1qszJF4dN7DwzTNWM5/lmmvBfmu50+QNU04
> klfVxjCXza8u2nBWAMSMHjZ+VmhDSFcKNuPh5gNSgqOrLKsELoVbdtgbes/eWyDi
> 2lrTVgqZSDlmKimQGYX/PZOGnN+4fhkyc2zC2wX3lYmZuK2+r2ZEORe2zzt1oiK4
> xly2zN7AexkZpfKlaI/oC6DjnP04BKOnPDp3M169uxM7jT81MVL3qi7ZXqaFusnj
> XCobkBy/ts1s0svs9uGyHDweUWOCY0WGPoN4aPgDtP5AbLKcxrXTEnT20ZpRuXdW
> OeBAdb/Pz/UbAzuVoPKG4Vft8no/cNkWGLnB4wQSEL2xRG8YcfDXwyd3xyCwG/rX
> QLkcSl6t2lSU4uBXoPykNu8U9PDB0c8ZBUDR4Rz981Tr63y2EOLGbxImYubEkaSs
> dwaokoUXLiQLg869uUBtCaUNqXLsfj5fMCG08VrJcrxHwrMWlPsdSB/caBVVIUHN
> hcIoHOgop4a5cvrASA6p9dtYupFM5xlvwS6j13omJfea1OGxQG5bV8tSFMoD5cF7
> JCz+M5FbotD7sJO+5gbYPPg8+iblKSFlCO+ttMpluW5+KdDF27bF1uyy10vfxwZh
> I1A1CGPmpQ84+cGFqdm5
> =F1On
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> http://clusterlabs.org/mailman/listinfo/users 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org 

More information about the Users mailing list