Emre, this is bug in man page. ttl affects both udp and udpu mode. Honza Emre He napsal(a): > Hello Jan, > > i checked ttl by manual page: "ttl -- This specifies the Time To Live > (TTL). If you run your cluster on a routed network then the default of "1" > will be too small. This option provides a way to increase this up to 255. > The valid range is 0..255. Note that this is only valid on multicast > transport types" > looks like "ttl" only works for multicast types, it is not related to > point-to-point unicast type. > > thanks, > Emre > > > 2013/10/7 Jan Friesse <jfriesse@xxxxxxxxxx> > >> Emre, >> different subnets works without any problem as long as you set proper >> ttl (man corosync.conf / ttl). >> >> Heartbeat is integral part of totem protocol so there is nothing like >> separated heartbeat and transport protocol. Just use transport key >> (udp/udpu). >> >> Regards, >> Honza >> >> Emre He napsal(a): >>> Hi, >>> >>> i want to know if Corosync support unicast for cluster nodes heartbeat in >>> different sub-network? i google and found some pages said we can use >> below >>> configuration for unicast: >>> >> https://github.com/fghaas/corosync/blob/master/conf/corosync.conf.example.udpu >>> >>> but i cannot find any info about heartbeat styles: unicast or multicast >> or >>> broadcast on Corosync official wiki pages, where could i find this >> official >>> info? >>> >>> thanks, >>> Emre >>> >>> >>> >>> _______________________________________________ >>> discuss mailing list >>> discuss@xxxxxxxxxxxx >>> http://lists.corosync.org/mailman/listinfo/discuss >>> >> >> > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
