PACEMAKER-FENCED(7)

🌸 PACEMAKER-FENCED 🌸

okay so bestie, before we even start β€” this page is pacemaker-fenced, and it lives in section 7 (that's the "miscellaneous" girlies) of the Pacemaker Configuration manual. Buckle up πŸ’…


✨ NAME ✨

pacemaker-fenced β€” the instance attributes that are available for all "stonith"-class resources. every single one of them, no cap 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

[pcmk_host_argument=string] [pcmk_host_map=string]
[pcmk_host_list=string] [pcmk_host_check=select] [pcmk_delay_max=time]
[pcmk_delay_base=string] [pcmk_action_limit=integer]
[pcmk_reboot_action=string] [pcmk_reboot_timeout=time]
[pcmk_reboot_retries=integer] [pcmk_off_action=string]
[pcmk_off_timeout=time] [pcmk_off_retries=integer]
[pcmk_on_action=string] [pcmk_on_timeout=time] [pcmk_on_retries=integer]
[pcmk_list_action=string] [pcmk_list_timeout=time]
[pcmk_list_retries=integer] [pcmk_monitor_action=string]
[pcmk_monitor_timeout=time] [pcmk_monitor_retries=integer]
[pcmk_status_action=string] [pcmk_status_timeout=time]
[pcmk_status_retries=integer]

πŸ’– DESCRIPTION πŸ’–

So these are the instance attributes that are available for all "stonith"-class resources, and they're the ones used by Pacemaker's fence daemon. If you're configuring a stonith resource and you're like "wait, what can I even set on this thing" β€” it's this. this whole list. literally all of it ✨


πŸ‘‘ SUPPORTED PARAMETERS πŸ‘‘

okay this is the main character section, hydrate before you read it πŸ“

  • pcmk_host_argument (string) β€” * Advanced Use Only * this is the name of the agent parameter that should be set to the fencing target.

Fr fr: if the fencing agent metadata advertises support for the "port" or "plug" parameter, that one gets used as the default. Otherwise "none" is used, which is the cluster's way of saying "don't supply any additional parameters, I got this." πŸ™ˆ

  • pcmk_host_map (string) β€” a mapping of node names to port numbers, for those devices that simply do not support node names. rude of them, but okay.

Example era: "node1:1;node2:2,3" tells the cluster to use port 1 for node1 and ports 2 and 3 for node2. slay πŸ’…

  • pcmk_host_list (string) β€” the nodes that this device targets.

It's a comma-separated list of the nodes that can be targeted by this device (for example, "node1,node2,node3"). And heads up: if pcmk_host_check is "static-list", then either this or pcmk_host_map must be set. no vibes-based fencing, bestie 🌸

  • pcmk_host_check (select) β€” how to figure out which nodes this device can actually target.

The options, lowkey a whole menu:

  • use "dynamic-list" to query the device via the 'list' command
  • use "static-list" to check the pcmk_host_list attribute
  • use "status" to query the device via the 'status' command
  • or use "none" to assume every device can fence every node (chaotic, but go off)

The default value is "static-list" if pcmk_host_map or pcmk_host_list is set; otherwise "dynamic-list" if the device supports the list operation; otherwise "status" if the device supports the status operation; otherwise "none". Allowed values: dynamic-list, static-list, status, none.

  • pcmk_delay_max (time) [0s] β€” enable a delay of no more than the time specified, before executing fencing actions.

Enable a delay of no more than the time specified before executing fencing actions. Pacemaker derives the overall delay by taking the value of pcmk_delay_base and adding a random delay value such that the sum is kept below this maximum. math girlie behavior honestly 🧚

  • pcmk_delay_base (string) [0s] β€” enable a base delay for fencing actions, and specify the base delay value.

This enables a static delay for fencing actions, which can help avoid "death matches" where two nodes try to fence each other at the same time. 😭 (yes that's the real term, iconic and terrifying.) If pcmk_delay_max is also used, a random delay will be added such that the total delay is kept below that value. You can set this to a single time value to apply to any node targeted by this device (useful if a separate device is configured for each target), or to a node map (for example, "node1:1s;node2:5") to set a different value for each target.

  • pcmk_action_limit (integer) [1] β€” the maximum number of actions that can be performed in parallel on this device.

If the concurrent-fencing cluster property is "true", this specifies the maximum number of actions that can be performed in parallel on this device. A value of -1 means unlimited. go wild, but like, responsibly πŸ”₯

  • pcmk_reboot_action (string) [reboot] β€” * Advanced Use Only * an alternate command to run instead of 'reboot'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'reboot' action.

  • pcmk_reboot_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'reboot' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'reboot' actions. patient queen energy ⏳

  • pcmk_reboot_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'reboot' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'reboot' action before giving up. it's giving "she's on another call" energy πŸ“ž

  • pcmk_off_action (string) [off] β€” * Advanced Use Only * an alternate command to run instead of 'off'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'off' action.

  • pcmk_off_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'off' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'off' actions.

  • pcmk_off_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'off' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'off' action before giving up. (yes, "a 'off'", the original said it like that, don't come for me πŸ’€)

  • pcmk_on_action (string) [on] β€” * Advanced Use Only * an alternate command to run instead of 'on'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'on' action.

  • pcmk_on_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'on' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'on' actions.

  • pcmk_on_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'on' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'on' action before giving up.

  • pcmk_list_action (string) [list] β€” * Advanced Use Only * an alternate command to run instead of 'list'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'list' action.

  • pcmk_list_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'list' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'list' actions.

  • pcmk_list_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'list' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'list' action before giving up.

  • pcmk_monitor_action (string) [monitor] β€” * Advanced Use Only * an alternate command to run instead of 'monitor'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'monitor' action.

  • pcmk_monitor_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'monitor' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'monitor' actions. she's watching πŸ‘€

  • pcmk_monitor_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'monitor' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'monitor' action before giving up.

  • pcmk_status_action (string) [status] β€” * Advanced Use Only * an alternate command to run instead of 'status'.

Some devices do not support the standard commands, or may provide additional ones. Use this to specify an alternate, device-specific command that implements the 'status' action.

  • pcmk_status_timeout (time) [60s] β€” * Advanced Use Only * specify an alternate timeout to use for 'status' actions, instead of fencing-timeout.

Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific timeout for 'status' actions.

  • pcmk_status_retries (integer) [2] β€” * Advanced Use Only * the maximum number of times to try the 'status' command within the timeout period.

Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'status' action before giving up.

bestie real talk: everything marked * Advanced Use Only * is advanced use only. don't just set it because it looked fun in the list. i'm not being mean, i'm being a good friend πŸ’œ

πŸŽ€ AUTHOR πŸŽ€

Andrew Beekhof <andrew@beekhof.net> β€” Author. (yes, the actual author line, we stan a credited king πŸ‘‘)


🌈 SEE ALSO 🌈

(iykyk β€” there's no SEE ALSO section on this page, so there's nothing else to point you at. go touch some grass, or go fence something. πŸ¦‹)


and that's the whole page bestie!! 🫢 this was Pacemaker Configuration, dated 09/17/2026 β€” now go forth and configure your stonith resources with main character energy. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from