[PATCH docs 3/4] ha-manager: add disarming HA section

[Maximiliano Sandoval <m.sandoval@proxmox.com>]

Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
 ha-manager.adoc | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 68fb7d1..3c97a2d 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -1086,6 +1086,37 @@ this is not the case the update process can take too long which, in the worst
 case, may result in a reset triggered by the watchdog.
 
 
+[[ha_manager_cluster_maintenance]]
+Cluster-wide Maintenance
+------------------------
+
+If a cluster has HA-resources then one has to be careful during a maintenance
+that involves multiple nodes or when performing configuration changes on
+multiple node, as connectivity issues on the Corosync network can result in one
+or more nodes fencing. One common example is when editing Corosync's
+configuration as the changes will be picked up by all cluster nodes and any
+configuration error can lead to nodes potentially fencing. In this scenario one
+can temporarily disarm HA in order to release the watchdogs in the cluster.
+
+You can disarm and arm HA using the ha-manager CLI tool.
+
+.Disarming HA
+----
+# ha-manager crm-command disarm-ha <RESOURCE_MODE>
+----
+
+.Arming HA
+----
+# ha-manager crm-command arm-ha
+----
+
+There are two possible resource modes for disarming HA:
+
+- `freeze`: new commands and state changes are not applied.
+- `ignore`: resources are removed from HA tracking and can be managed as if they
+  were not HA managed.
+
+
 [[ha_manager_node_maintenance]]
 Single Node Maintenance
 -----------------------
-- 
2.47.3