Maximal number of tries to restart the service on a node after its start failed.
-`-state` `<disabled | enabled>` ('default =' `enabled`)::
+`-state` `<disabled | enabled | started | stopped>` ('default =' `started`)::
-Resource state.
+Requested resource state.
`-type` `<ct | vm>` ::
-*ha-manager disable* `<sid>`
-
-Disable a HA resource.
-
-`<sid>`: `<type>:<name>` ::
-
-HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
-
-
-
-*ha-manager enable* `<sid>`
-
-Enable a HA resource.
-
-`<sid>`: `<type>:<name>` ::
-
-HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
-
-
-
-
*ha-manager groupadd* `<group> -nodes <string>` `[OPTIONS]`
Create a new HA group.
`-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
-List of cluster node names with optional priority. We use priority '0' as default. The CRM tries to run services on the node with highest priority (also see option 'nofailback').
+List of cluster node names with optional priority.
`-nofailback` `<boolean>` ('default =' `0`)::
`-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
-List of cluster node names with optional priority. We use priority '0' as default. The CRM tries to run services on the node with highest priority (also see option 'nofailback').
+List of cluster node names with optional priority.
`-nofailback` `<boolean>` ('default =' `0`)::
Maximal number of tries to restart the service on a node after its start failed.
-`-state` `<disabled | enabled>` ('default =' `enabled`)::
+`-state` `<disabled | enabled | started | stopped>` ('default =' `started`)::
-Resource state.
+Requested resource state.