Show Table of Contents
4.2. General Properties of Fencing Devices
Note
To disable a fencing device/resource, you can set the
target-role as you would for a normal resource.
Note
To prevent a specific node from using a fencing device, you can configure location constraints for the fencing resource.
Table 4.1, “General Properties of Fencing Devices” describes the general properties you can set for fencing devices. Refer to Section 4.3, “Displaying Device-Specific Fencing Options” for information on fencing properties you can set for specific fencing devices.
Note
For information on more advanced fencing configuration properties, see Section 4.9, “Additional Fencing Configuration Options”
Table 4.1. General Properties of Fencing Devices
| Field | Type | Default | Description |
|---|---|---|---|
priority | integer | 0 | The priority of the stonith resource. Devices are tried in order of highest priority to lowest. |
pcmk_host_map | string | A mapping of host names to ports numbers for devices that do not support host names. For example: node1:1;node2:2,3 tells the cluster to use port 1 for node1 and ports 2 and 3 for node2 | |
pcmk_host_list | string | A list of machines controlled by this device (Optional unless pcmk_host_check=static-list). | |
pcmk_host_check | string | dynamic-list | How to determine which machines are controlled by the device. Allowed values: dynamic-list (query the device), static-list (check the pcmk_host_list attribute), none (assume every device can fence every machine) |

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.