|
|
@@ -81,13 +81,18 @@ ring. The ringnumber must start at 0.
|
|
|
.TP
|
|
|
bindnetaddr
|
|
|
This specifies the network address the corosync executive should bind
|
|
|
-to. For example, if the local interface is 192.168.5.92 with netmask
|
|
|
-255.255.255.0, set bindnetaddr to 192.168.5.0. If the local interface
|
|
|
-is 192.168.5.92 with netmask 255.255.255.192, set bindnetaddr to
|
|
|
-192.168.5.64, and so forth.
|
|
|
+to.
|
|
|
+
|
|
|
+bindnetaddr should be an IP address configured on the system, or a network
|
|
|
+address.
|
|
|
+
|
|
|
+For example, if the local interface is 192.168.5.92 with netmask
|
|
|
+255.255.255.0, you should set bindnetaddr to 192.168.5.92 or 192.168.5.0.
|
|
|
+If the local interface is 192.168.5.92 with netmask 255.255.255.192,
|
|
|
+set bindnetaddr to 192.168.5.92 or 192.168.5.64, and so forth.
|
|
|
|
|
|
This may also be an IPV6 address, in which case IPV6 networking will be used.
|
|
|
-In this case, the full address must be specified and there is no automatic
|
|
|
+In this case, the exact address must be specified and there is no automatic
|
|
|
selection of the network interface within a specific subnet as with IPv4.
|
|
|
|
|
|
If IPv6 networking is used, the nodeid field in nodelist must be specified.
|