Este conteúdo não está disponível no idioma selecionado.
4.26. Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
Table 4.27, “Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)” lists the fence device parameters used by
fence_mpath, the fence agent for multipath persistent reservation fencing.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the fence_mpath device. |
| Devices (Comma delimited list) | devices | Comma-separated list of devices to use for the current operation. Each device must support SCSI-3 persistent reservations. |
| Use sudo when calling third-party software | sudo | Use sudo (without password) when calling 3rd party software. |
| Path to sudo binary (optional) | sudo_path | Path to sudo binary (default value is /usr/bin/sudo. |
| Path to mpathpersist binary (optional) | mpathpersist_path | Path to mpathpersist binary (default value is /sbin/mpathpersist. |
| Path to a directory where the fence agent can store information (optional) | store_path | Path to directory where fence agent can store information (default value is /var/run/cluster. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Unfencing | unfence section of the cluster configuration file | When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods. When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node(8) man page. |
| Key for current action | key | Key to use for the current operation. This key should be unique to a node and written in /etc/multipath.conf. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s). This parameter is always required. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
