On 2011. November 3. 13:29:25 Digimer wrote: > On 11/03/2011 01:12 PM, Székelyi Szabolcs wrote: > > On 2011. November 2. 21:00:18 Székelyi Szabolcs wrote: > >> how can I run a cluster on a network where nodes are on different > >> subnets? Currently the main problem is that heartbeats are sent with > >> their IP level TTL set to 1, which keeps them from reaching the other > >> nodes. How can I change this? I'm using multicasting. > > > > OK, I've found this: https://bugzilla.redhat.com/show_bug.cgi?id=640311 > > , > > saying that it's now possible to set the TTL for multicast. But I > > haven't > > found any info on *how* to set it. [...] > > But whatever I do, ccs_config_validate always says that my cluster.conf > > is invalid, and the TTL (as reported by tcpdump) is still zero. Is it > > possible that my cman is out of date? I'm using version 3.0.12. Can you > > tell me which is the eariest version that has this feature? > > > > Thanks, > > Looking in the cluster.rng file (the one used to validate cluster.conf), > '<cman ttl="x" ...>' should be valid. What version of cman are you using? If I add the ttl="8" attribute to <cman> in cluster.conf, it fails to validate according to ccs_config_validate. Without this attribute it validates. I've grepped cluster.rng for "ttl", but found nothing sensible. It looks like it's missing from my cluster.rng. My cman's version is 3.0.12: $ sudo cman_tool -V cman_tool 3.0.12 (built Jul 2 2010 09:55:13) The cluster starts with the attibute (it issues a warning), but the TTL is still 1. I've already upgraded corosync to support TTL adjustment, but it looks like I just have a problem to push it through cman. Thanks, -- cc -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
