Editing Cluster and its component Understanding (section)

=== ⁠1.3.3. Fencing ===
Fencing is the disconnection of a node from the cluster's shared storage. Fencing cuts off I/O from shared storage, thus ensuring data integrity. The cluster infrastructure performs fencing through the fence daemon, <tt>fenced</tt>. 

When CMAN determines that a node has failed, it communicates to other cluster-infrastructure components that the node has failed. <tt>fenced</tt>, when notified of the failure, fences the failed node. Other cluster-infrastructure components determine what actions to take — that is, they perform any recovery that needs to done. For example, DLM and GFS, when notified of a node failure, suspend activity until they detect that <tt>fenced</tt> has completed fencing the failed node. Upon confirmation that the failed node is fenced, DLM and GFS perform recovery. DLM releases locks of the failed node; GFS recovers the journal of the failed node. 

The fencing program determines from the cluster configuration file which fencing method to use. Two key elements in the cluster configuration file define a fencing method: fencing agent and fencing device. The fencing program makes a call to a fencing agent specified in the cluster configuration file. The fencing agent, in turn, fences the node via a fencing device. When fencing is complete, the fencing program notifies the cluster manager. 

Red Hat Cluster Suite provides a variety of fencing methods: 

* Power fencing — A fencing method that uses a power controller to power off an inoperable node. Two types of power fencing are available: external and integrated. External power fencing powers off a node via a power controller (for example an API or a WTI power controller) that is external to the node. Integrated power fencing powers off a node via a power controller (for example,IBM Bladecenters, PAP, DRAC/MC, HP ILO, IPMI, or IBM RSAII) that is integrated with the node. 
* SCSI3 Persistent Reservation Fencing — A fencing method that uses SCSI3 persistent reservations to disallow access to shared storage. When fencing a node with this fencing method, the node's access to storage is revoked by removing its registrations from the shared storage. 
* Fibre Channel switch fencing — A fencing method that disables the Fibre Channel port that connects storage to an inoperable node. 
* GNBD fencing — A fencing method that disables an inoperable node's access to a GNBD server. 

For more information about brands and models of fencing hardware that are compatible with Red Hat Cluster Suite components, refer to the hardware configuration guidelines at [http://www.redhat.com/cluster_suite/hardware/ http://www.redhat.com/cluster_suite/hardware/]. 

[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Suite_Overview/index.html#fig-fence-example-pwr-CSO Figure 1.3, “Power Fencing Example”] shows an example of power fencing. In the example, the fencing program in node A causes the power controller to power off node D. [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Suite_Overview/index.html#fig-fence-example-fc-CSO Figure 1.4, “Fibre Channel Switch ][https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Suite_Overview/index.html#fig-fence-example-fc-CSO Fencing Example”] shows an example of Fibre Channel switch fencing. In the example, the fencing program in node A causes the Fibre Channel switch to disable the port for node D, disconnecting node D from storage. 

⁠

[[Image:fence-example-pwr.png]]

'''Figure&nbsp;1.3.&nbsp;Power Fencing Example'''

⁠

[[Image:fence-example-fc.png]]

'''Figure&nbsp;1.4.&nbsp;Fibre Channel Switch Fencing Example'''

Specifying a fencing method consists of editing a cluster configuration file to assign a fencing-method name, the fencing agent, and the fencing device for each node in the cluster. 

The way in which a fencing method is specified depends on if a node has either dual power supplies or multiple paths to storage. If a node has dual power supplies, then the fencing method for the node must specify at least two fencing devices — one fencing device for each power supply (refer to [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Suite_Overview/index.html#fig-fence-pwr-dual-CSO Figure 1.5, “Fencing a Node with Dual Power Supplies”]). Similarly, if a node has multiple paths to Fibre Channel storage, then the fencing method for the node must specify one fencing device for each path to Fibre Channel storage. For example, if a node has two paths to Fibre Channel storage, the fencing method should specify two fencing devices — one for each path to Fibre Channel storage (refer to [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Suite_Overview/index.html#fig-fence-fc-dual-CSO Figure 1.6, “Fencing a Node with Dual Fibre Channel Connections”]). 

⁠

[[Image:fence-example-pwr-dual.png]]

'''Figure&nbsp;1.5.&nbsp;Fencing a Node with Dual Power Supplies'''

⁠

[[Image:fence-example-fc-dual.png]]

'''Figure&nbsp;1.6.&nbsp;Fencing a Node with Dual Fibre Channel Connections'''

You can configure a node with one fencing method or multiple fencing methods. When you configure a node for one fencing method, that is the only fencing method available for fencing that node. When you configure a node for multiple fencing methods, the fencing methods are ''cascaded'' from one fencing method to another according to the order of the fencing methods specified in the cluster configuration file. If a node fails, it is fenced using the first fencing method specified in the cluster configuration file for that node. If the first fencing method is not successful, the next fencing method specified for that node is used. If none of the fencing methods is successful, then fencing starts again with the first fencing method specified, and continues looping through the fencing methods in the order specified in the cluster configuration file until the node has been fenced.