- if (add_ifaddr(objdb, mcast, node, portnum, transport)) {
+ if (add_ifaddr(objdb, mcast, node, portnum, altttl, transport)) {
write_cman_pipe(error_reason);
return -1;
}
diff --git a/config/tools/xml/cluster.rng.in b/config/tools/xml/cluster.rng.in
index 04906c9..c873cae 100644
--- a/config/tools/xml/cluster.rng.in
+++ b/config/tools/xml/cluster.rng.in
@@ -147,14 +147,22 @@ To validate your cluster.conf against this schema, run:
instead of using the multicast address generated by cman. If
a user does not specify a multicast address, cman creates one. It
forms the upper 16 bits of the multicast address with 239.192 and
- forms the lower 16 bits based on the cluster ID."> <attribute
- name="addr" rha:description="A multicast address specified
+ forms the lower 16 bits based on the cluster ID.">
+ <optional>
+ <attribute name="addr" rha:description="A multicast address specified
by a user. If you do specify a multicast address, you should
use the 239.192.x.x series that cman uses. Otherwise, using a
multicast address outside that range may cause unpredictable
results. For example, using 224.0.0.x (All hosts on the network)
may not be routed correctly, or even routed at all by some
hardware." rha:sample="239.192.0.1"/>
+ </optional>
+ <optional>
+ <attribute name="ttl" rha:description="Define the TTL (time to live) of
+ a multicast packets. Useful only if nodes are on different subnets and
+ a multicast router is available in between." rha:default="1"
+ rha:sample="24"/>
+ </optional>
</element>
</optional>
</element>
@@ -734,6 +742,11 @@ To validate your cluster.conf against this schema, run:
<attribute name="mcast" rha:description="The multicast address
to use on the second interface. cman(5)"/>
</optional>
+
+ <optional>
+ <attribute name="ttl" rha:description="The multicast TTL
+ to use on the second interface. cman(5)"/>
+ </optional>
</element>
</optional>