2. yast-cluster
3. Chinese (China) (zh_CN)

<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>绑定网c络地址</big></b><br>指定 openaiscorosync 可执行文件应该绑定的地址。此地址应始终以 0 结尾。如果应该通过 192.168.5.92 路由 totem 流量，请将绑定网络地址设置为 192.168.5.0。<br>这也可以是 IPV6 地址，在此情况下，将使用 IPV6 网络。此时，必须指定完整地址，系统不会像使用 IPv4 时一样自动选择特定子网中的网络接口。如果使用 IPv6 网络，必须指定 nodeid 字段。<br></p>
<p><b><big>多路广播地址</big></b><br>这是 openaiscorosync 可执行文件使用的多路广播地址。默认值适用于大多数网络，但您应该咨询网络管理员要使用哪个多路广播地址。请勿指定 224.x.x.x，因为这是一个“ "config”多路广" 多播地址。<br>这也可以是 IPV6 多路广播地址，在此情况下，将使用 IPV6 网络。如果使用 IPv6 网络，必须指定 nodeid 字段。</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 {} 段落中指定该值（“"预期投票数”" 应使用集群的总节点数）。如果单路广播传输中存在预期投票数，该值将覆盖自动计算的值。为安全起见，一旦 nodelist 非空，将禁用“ "预期投票数”"，最好忽略设置的不适当的预期投票数。<br></p>
<p><b><big>自动生成节点 ID</big></b><br>使用 IPv6 时必须指定 nodeid。启用自动节点 ID 将自动生成 nodeid。<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"

需要按 "生成身份验证密钥文件"