2. yast-cluster
3. Chinese (Taiwan) (zh_TW)

<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>
<p><b><big>Bind Network Address</big></b><br>This specifies the address which the corosync executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>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 selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>
<p><b><big>Multicast Address</big></b><br>This is the multicast address used by corosync executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a "config" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>
<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the corosync services configured for different UDP ports.<br></p>
<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>
<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>
<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>
<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>
<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>
<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>

<p><b><big>IP 版本</big></b><br>指定用於通訊的 IP 版本。值可以是 ipv4 或 ipv6 之一。預設值 (若未指定) 為 ipv4。<br></p>
<p><b><big>結合網路位址</big></b><br>指定 openaiscorosync 可執行檔應該結合的位址。此位址應一律以 0 結尾。如果應該透過 192.168.5.92 路由 totem 流量，請將結合網路位址設定為 192.168.5.0。<br>這也可以是 IPV6 位址，如此即會使用 IPV6 網路。在此情況下，必須指定完整位址，系統不會像使用 IPv4 時一樣自動選取特定子網路中的網路介面。如果使用 IPv6 網路，必須指定節點 ID 欄位。<br></p>
<p><b><big>多路廣播點傳送位址</big></b><br>這是 openaiscorosync 可執行檔使用的多路廣播點傳送位址。預設值適用於大部分網路，但您應該諮詢網路管理員要使用哪個多路廣播點傳送位址。請勿指定 224.x.x.x，因為這是一個「 "config」多路廣播" 多點傳送位址。<br>這也可以是 IPV6 多路廣播點傳送位址，如此即會使用 IPV6 網路。如果使用 IPv6 網路，必須指定節點 ID 欄位。</p>
<p><b><big>連接埠</big></b><br>指定 UDP 連接埠號碼。在將 openaiscorosync 服務設定為使用不同 UDP 連接埠的網路上可以使用相同的多路廣播點傳送位址。<br></p>
<p><b><big>成員位址</big></b><br>此清單依 IP 位址指定叢集中的所有節點。使用 udpu(Unicast) 時可以設定此值。<br></p>
<p><b><big>節點 ID</big></b><br>使用 IPv4 時，此組態選項是選擇性的，而使用 IPv6 時，則必須指定此選項。這是一個 32 位元值，指定傳送給叢集成員服務的節點識別碼。如果使用 IPv4 時未指定此選項，則節點 ID 將基於系統透過環識別碼 0 結合到的 32 位元 IP 位址來確定。節點識別碼值 0 是保留值，不應使用。<br></p>
<p><b><big>rrp_mode</big></b><br>指定備援環的模式，可以是「無」、「主動」或「被動」 "無"、"主動" 或 "被動"。主動複製可使故障網路環境中從傳輸到遞送的延遲時間略微降低，但效能會下降。被動複製可使該通訊協定的速度提高近一倍，前提是 totem 通訊協定不受限於 CPU。最後一個選項為「無」 "無"，在此情況下，將僅使用一個網路介面執行 totem 通訊協定。如果僅指定了一個介面指令，則會自動選取「無」 "無"。如果指定了多個介面指令，則只能選取「主動」或「被動」 "主動" 或 "被動"。<br></p>
<p><b><big>叢集名稱</big></b><br>指定叢集的名稱，用於自動產生多路廣播點傳送位址。預設為 hacluster。對於地理叢集，每個叢集的名稱必須是唯一的。<br></p>
<p><b><big>預期投票數</big></b><br>投票人數對應的預期投票數。當 corosync.conf 中存在 nodelist {} 區段時會自動計算該值 (使用單路廣點傳播傳輸時會產生該清單)，您也可以在 quorum {} 區段中指定該值 (「"預期投票數」" 應使用叢集的節點總數)。如果單路廣點傳播傳輸中存在預期投票數，該值將覆寫自動計算的值。為安全起見，一旦節點清單不是空白的，將會停用「 "預期投票數」"，最好忽略設定的不適當的「 "預期投票數」"。<br></p>
<p><b><big>自動產生節點 ID</big></b><br>使用 IPv6 時必須指定節點 ID。啟用自動節點 ID 會自動產生節點 ID。<br></p>

<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>
<p><b><big>Bind Network Address</big></b><br>This specifies the address which the openaiscorosync executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>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 selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>
<p><b><big>Multicast Address</big></b><br>This is the multicast address used by openaiscorosync executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a "config" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>
<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the openaiscorosync services configured for different UDP ports.<br></p>
<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>
<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>
<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>
<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>
<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>
<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>

Need to press "Generate Auth Key File"

需要按 "產生驗證金鑰檔案"