diff --git a/images/src/png/yast_cluster_qdevice.png b/images/src/png/yast_cluster_qdevice.png
new file mode 100644
index 000000000..05202033e
Binary files /dev/null and b/images/src/png/yast_cluster_qdevice.png differ
diff --git a/xml/ha_qdevice-qnetd.xml b/xml/ha_qdevice-qnetd.xml
index 0a303937b..bb9924991 100644
--- a/xml/ha_qdevice-qnetd.xml
+++ b/xml/ha_qdevice-qnetd.xml
@@ -194,8 +194,8 @@
- A different physical network than the one that &corosync; uses.
- It is recommended for &qdevice; to reach the &qnet; server.
+ It is recommended for &qdevice; to reach the &qnet; server via a
+ different physical network than the one that &corosync; uses.
Ideally, the &qnet; server should be in a separate rack than the
main cluster, or at least on a separate PSU and not in the same
network segment as the Corosync ring or rings.
@@ -231,7 +231,7 @@
- Enable the &productname; using the command listed in
+ Enable &productname; using the command listed in
SUSEConnect --list-extensions.
diff --git a/xml/ha_yast_cluster.xml b/xml/ha_yast_cluster.xml
index 765be4f79..dc47c4f1e 100644
--- a/xml/ha_yast_cluster.xml
+++ b/xml/ha_yast_cluster.xml
@@ -229,6 +229,17 @@
+
+ &corosync; &qdevice; (optional but recommended for clusters with an even number of nodes)
+
+
+ Allows you to configure &qdevice; as a client of a &qnet; server to
+ participate in quorum decisions. This is recommended for clusters with
+ an even number of nodes, and especially for two-node clusters.
+ For details, see .
+
+
+ Security (optional but recommended)
@@ -596,6 +607,150 @@
+
+ Configuring an arbitrator for quorum decisions
+
+ &qdevice; and &qnet; participate in quorum decisions. With assistance from
+ the arbitrator corosync-qnetd,
+ corosync-qdevice provides a
+ configurable number of votes, allowing a cluster to sustain more node
+ failures than the standard quorum rules allow. We recommend deploying
+ corosync-qnetd and
+ corosync-qdevice for clusters
+ with an even number of nodes, and especially for two-node clusters.
+ For more information, see .
+
+
+ Requirements
+
+
+ Before you configure &qdevice;, you must set up a &qnet; server.
+ See .
+
+
+
+
+ Configuring &qdevice; and &qnet;
+
+
+ Start the &yast; cluster module and switch to the
+ &corosync; &qdevice; category.
+
+
+
+
+ Activate Enable &corosync; &qdevice;.
+
+
+
+
+ In the &qnet; server host field, enter the IP address
+ or host name of the &qnet; server.
+
+
+
+
+ Select the mode for TLS:
+
+
+
+
+ Use off if TLS is not required and should not be tried.
+
+
+
+
+ Use on to attempt to connect with TLS, but connect without TLS
+ if it is not available.
+
+
+
+
+ Use required to make TLS mandatory. &qdevice; will exit with
+ an error if TLS is not available.
+
+
+
+
+
+
+ Select the Heuristics Mode:
+
+
+
+
+ Use off to disable heuristics.
+
+
+
+
+ Use on to run heuristics on a regular basis, as set by the
+ Heuristics Interval.
+
+
+
+
+ Use sync to only run heuristics during startup, when cluster
+ membership changes, and on connection to &qnet;.
+
+
+
+
+
+
+ If you set the Heuristics Mode to on
+ or sync, add your heuristics commands to the
+ Heuristics Executables list:
+
+
+
+
+ Select Add. A new window opens.
+
+
+
+
+ Enter an Execute Name for the command.
+
+
+
+
+ Enter the command in the Execute Script field. This can be a
+ single command or the path to a script, and can be written in any language
+ such as Shell, Python, or Ruby.
+
+
+
+
+ Select OK to close the window.
+
+
+
+
+
+
+ Confirm your changes.
+
+
+
+
+ &yast; <guimenu>Cluster</guimenu>—&corosync; &qdevice;
+
+
+
+
+
+
+
+
+ The &corosync; &qdevice; screen shows the settings for configuring &qdevice;.
+ The Enable &corosync; &qdevice; check box is activated,
+ and the cursor is in the &qnet; server host field.
+
+
+
+
+
Defining authentication settings