# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "Configure STONITH"
msgstr ""

#. Tag: title
#, no-c-format
msgid "What is STONITH?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "STONITH (Shoot The Other Node In The Head aka. fencing) protects your data from being corrupted by rogue nodes or unintended concurrent access."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Just because a node is unresponsive doesn’t mean it has stopped accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH to ensure that the node is truly offline before allowing the data to be accessed from another node."
msgstr ""

#. Tag: para
#, no-c-format
msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Choose a STONITH Device"
msgstr ""

#. Tag: para
#, no-c-format
msgid "It is crucial that your STONITH device can allow the cluster to differentiate between a node failure and a network failure."
msgstr ""

#. Tag: para
#, no-c-format
msgid "A common mistake people make when choosing a STONITH device is to use a remote power switch (such as many on-board IPMI controllers) that shares power with the node it controls. If the power fails in such a case, the cluster cannot be sure whether the node is really offline, or active and suffering from a network fault, so the cluster will stop all resources to avoid a possible split-brain situation."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Likewise, any device that relies on the machine being active (such as SSH-based \"devices\" sometimes used during testing) is inappropriate."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure the Cluster for STONITH"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Install the STONITH agent(s). To see what packages are available, run <literal>yum search fence-</literal>. Be sure to install the package(s) on all cluster nodes."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Configure the STONITH device itself to be able to fence your nodes and accept fencing requests. This includes any necessary configuration on the device and on the nodes, and any firewall or SELinux changes needed. Test the communication between the device and your nodes."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Find the correct STONITH agent script: <literal>pcs stonith list</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Find the parameters associated with the device: <literal>pcs stonith describe <replaceable>agent_name</replaceable></literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Create a local copy of the CIB: <literal>pcs cluster cib stonith_cfg</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Create the fencing resource: <literal>pcs -f stonith_cfg stonith create <replaceable>stonith_id stonith_device_type [stonith_device_options]</replaceable></literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Any flags that do not take arguments, such as <literal>--ssl</literal>, should be passed as <literal>ssl=1</literal>."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Enable STONITH in the cluster: <literal>pcs -f stonith_cfg property set stonith-enabled=true</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special <emphasis role=\"strong\">pcmk_host_map</emphasis> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If the device does not support the <emphasis role=\"strong\">list</emphasis> command, you may also need to set the special <emphasis role=\"strong\">pcmk_host_list</emphasis> and/or <emphasis role=\"strong\">pcmk_host_check</emphasis> parameters. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If the device does not expect the victim to be specified with the <emphasis role=\"strong\">port</emphasis> parameter, you may also need to set the special <emphasis role=\"strong\">pcmk_host_argument</emphasis> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Commit the new configuration: <literal>pcs cluster cib-push stonith_cfg</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Once the STONITH resource is running, test it (you might want to stop the cluster on that machine first): <literal>stonith_admin --reboot <replaceable>nodename</replaceable></literal>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Example"
msgstr ""

#. Tag: para
#, no-c-format
msgid "For this example, assume we have a chassis containing four nodes and an IPMI device active on 10.0.0.1. Following the steps above would go something like this:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 1: Install the <emphasis role=\"strong\">fence-agents-ipmilan</emphasis> package on both nodes."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 2: Configure the IP address, authentication credentials, etc. in the IPMI device itself."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 3: Choose the <emphasis role=\"strong\">fence_ipmilan</emphasis> STONITH agent."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 4: Obtain the agent’s possible parameters:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs stonith describe fence_ipmilan\n"
"fence_ipmilan - Fence agent for IPMI\n"
"\n"
"fence_ipmilan is an I/O Fencing agentwhich can be used with machines controlled by IPMI.This agent calls support software ipmitool (http://ipmitool.sf.net/). WARNING! This fence agent might report success before the node is powered off. You should use -m/method onoff if your fence device works correctly with that option.\n"
"\n"
"Stonith options:\n"
"  ipport: TCP/UDP port to use for connection with device\n"
"  port: IP address or hostname of fencing device (together with --port-as-ip)\n"
"  inet6_only: Forces agent to use IPv6 addresses only\n"
"  ipaddr: IP Address or Hostname\n"
"  passwd_script: Script to retrieve password\n"
"  method: Method to fence (onoff|cycle)\n"
"  inet4_only: Forces agent to use IPv4 addresses only\n"
"  passwd: Login password or passphrase\n"
"  lanplus: Use Lanplus to improve security of connection\n"
"  auth: IPMI Lan Auth type.\n"
"  action: Fencing Action WARNING: specifying 'action' is deprecated and not necessary with current Pacemaker versions.\n"
"  cipher: Ciphersuite to use (same as ipmitool -C parameter)\n"
"  target: Bridge IPMI requests to the remote target address\n"
"  privlvl: Privilege level on IPMI device\n"
"  timeout: Timeout (sec) for IPMI operation\n"
"  login: Login Name\n"
"  power_wait: Wait X seconds after issuing ON/OFF\n"
"  login_timeout: Wait X seconds for cmd prompt after login\n"
"  delay: Wait X seconds before fencing is started\n"
"  power_timeout: Test X seconds for status change after ON/OFF\n"
"  ipmitool_path: Path to ipmitool binary\n"
"  shell_timeout: Wait X seconds for cmd prompt after issuing command\n"
"  port_as_ip: Make \"port/plug\" to be an alias to IP address\n"
"  retry_on: Count of attempts to retry power on\n"
"  sudo: Use sudo (without password) when calling 3rd party sotfware.\n"
"  priority: The priority of the stonith resource. Devices are tried in order of highest priority to lowest.\n"
"  pcmk_host_map: A mapping of host names to ports numbers for devices that do not support host names. Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for node1 and ports\n"
"                 2 and 3 for node2\n"
"  pcmk_host_list: A list of machines controlled by this device (Optional unless pcmk_host_check=static-list).\n"
"  pcmk_host_check: 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),\n"
"                   none (assume every device can fence every machine)\n"
"  pcmk_delay_max: Enable random delay for stonith actions and specify the maximum of random delay This prevents double fencing when using slow devices such as sbd. Use this to\n"
"                  enable random delay for stonith actions and specify the maximum of random delay.\n"
"  pcmk_action_limit: The maximum number of actions can be performed in parallel on this device Cluster property concurrent-fencing=true needs to be configured first. Then use this\n"
"                     to specify the maximum number of actions can be performed in parallel on this device. -1 is unlimited.\n"
"\n"
"Default operations:\n"
"  monitor: interval=60s"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 5: <literal>pcs cluster cib stonith_cfg</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 6: Here are example parameters for creating our STONITH resource:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f stonith_cfg stonith create ipmi-fencing fence_ipmilan \\\n"
"      pcmk_host_list=\"pcmk-1 pcmk-2\" ipaddr=10.0.0.1 login=testuser \\\n"
"      passwd=acd123 op monitor interval=60s\n"
"[root@pcmk-1 ~]# pcs -f stonith_cfg stonith\n"
" ipmi-fencing   (stonith:fence_ipmilan):        Stopped"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Steps 7-10: Enable STONITH in the cluster:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f stonith_cfg property set stonith-enabled=true\n"
"[root@pcmk-1 ~]# pcs -f stonith_cfg property\n"
"Cluster Properties:\n"
" cluster-infrastructure: corosync\n"
" cluster-name: mycluster\n"
" dc-version: 1.1.16-12.el7_4.5-94ff4df\n"
" have-watchdog: false\n"
" stonith-enabled: true"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 11: <literal>pcs cluster cib-push stonith_cfg</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Step 12: Test:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster stop pcmk-2\n"
"[root@pcmk-1 ~]# stonith_admin --reboot pcmk-2"
msgstr ""

#. Tag: para
#, no-c-format
msgid "After a successful test, login to any rebooted nodes, and start the cluster (with <literal>pcs cluster start</literal>)."
msgstr ""