2. yast-cluster
3. master
4. Slovak

<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>Verzia IP</big></b><br>Určuje verziu IP, ktorá sa použije na komunikáciu. Hodnota môže byť jedna z ipv4 alebo ipv6. Predvolená hodnota (ak nie je určená) je ipv4.<br></p>
<p><b><big>Viazaná sieťová adresa</big></b><br>Určuje adresu, ku ktorej by sa mal vykonávajúci program openaiscorosync viazať. Táto adresa by mala vždy končiť nulou. Ak sa má totem prevádzka smerovať cez 192.168.5.92, nastavte bindnetaddr na 192.168.5.0.<br>Môže to byť aj adresa IPV6, v takom prípade sa použije sieťovanie IPV6. V takom prípade sa musí zadať úplná adresa a neexistuje žiadny automatický výber sieťového rozhrania v rámci konkrétnej podsiete ako pri IPv4. Ak sa používa sieťovanie IPv6, musí byť zadané pole nodeid.<br></p>
<p><b><big>Viacsmerová adresa</big></b><br>Toto je viacsmerová adresa použitá vykonávajúcim programom openaiscorosync. Predvolená by mala fungovať pre väčšinu sietí, ale správca siete by sa mal dopytovaný na viacsmerovú adresu, ktorá sa má použiť. Treba sa vyhnúť 224.x.x.x pretože toto je "konfiguračná" viacsmerová adresa.<br>Môže to byť aj viacsmerová adresa IPV6, v takom prípade sa použije sieťovanie IPV6. Ak sa používa sieťovanie IPv6, musí byť zadané pole nodeid.</p>
<p><b><big>Port</big></b><br>Určuje číslo portu UDP. Rovnakú viacsmerovú adresu je možné použiť v sieti s openaiscorosync službami nakonfigurovanými pre rôzne porty UDP.<br></p>
<p><b><big>Členská adresa</big></b><br>Tento zoznam určuje všetky uzly v klastri podľa IP adresy. Toto by sa dalo nakonfigurovať pri použití udpu (Unicast). <br></p>
<p><b><big>ID uzla</big></b><br>Táto konfiguračná možnosť je voliteľná pri použití IPv4 a vyžaduje sa pri použití IPv6. Toto je 32-bitová hodnota určujúca identifikátor uzla doručený do členskej služby klastra. Ak to nie je určené s IPv4, id uzla sa určí z 32-bitovej IP adresy systému, na ktorý je systém viazaný s prstencovým identifikátorom 0. Hodnota nula identifikátora uzla je rezervovaná a nemala by sa používať.<br></p>
<p><b><big>rrp_mode</big></b><br>Určuje režim redundantného prstenca, ktorý môže byť žiadny, aktívny alebo pasívny. Aktívna replikácia ponúka mierne nižšie oneskorenie od vysielania po doručenie v chybných sieťových prostrediach, ale s menším výkonom. Pasívna replikácia môže takmer zdvojnásobiť rýchlosť protokolu totem, ak protokol nebude viazaný na CPU. Posledná voľba je žiadny, v takom prípade sa na prevádzku protokolu totem použije iba jedno sieťové rozhranie. Ak je určená iba jedna direktíva rozhrania, zvolí sa automaticky žiadny. Ak je určených viacero direktív rozhraní, môže sa zvoliť iba aktívny alebo pasívny.<br></p>
<p><b><big>Názov klastra</big></b><br>Špecifikuje názov klastra a používa sa na automatické generovanie viacsmerovej adresy. Predvolený je hacluster. Pre geo klaster musí mať každý klaster jedinečný názov.<br></p>
<p><b><big>Očakávané hlasy</big></b><br>Očakávané hlasovacie číslo pre hlasovacie kvórum. Automaticky sa vypočíta, keď bude sekcia nodelist {} prítomná v corosync.conf (zoznam sa vygeneruje pri použití jednosmerného prenosu) alebo môže byť určené v sekcii quorum {} (Očakávané hlasy by mali používať celkový počet uzlov klastra). Ak sa Očakávané hlasy vyskytujú v jednosmernom prenose, hodnota prepíše automaticky vypočítanú. Kvôli bezpečnosti Očakávané hlasy budú zakázané, keď nodelist nie je prázdny, je dobré ignorovať nevhodné nastavenie Očakávané hlasy.<br></p>
<p><b><big>Automaticky generovať ID uzla</big></b><br>Nodeid je vyžadovaný pri použití IPv6. Povolené Automatické ID uzla bude generovať nodeid automaticky.<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"

Je potrebné stlačiť "Generovať súbor overovacieho kľúča".

Need to press "Generate Auth Key File"

Je potrebné stlačiť "Generovať súbor overovacieho kľúča".