<html><body><p><font size="2">Hi,<br><br>I have a question about resource level fencing. I read about it in the following document::<br></font><a href="https://clusterlabs.org/pacemaker/doc/crm_fencing.html"><font size="2">https://clusterlabs.org/pacemaker/doc/crm_fencing.html</font></a><font size="2"><br></font><br><font size="2">It has the following excerpt about resource level fencing:<br></font><i><font color="#000080">There are two kinds of fencing: resource level and node level.</font></i><p><i><font color="#000080">Using the resource level fencing the cluster can make sure that a node cannot access one or more resources. One typical example is a SAN, where a fencing operation changes rules on a SAN switch to deny access from a node.</font></i><p><i><font color="#000080">The resource level fencing may be achieved using normal resources on which the resource we want to protect would depend. Such a resource would simply refuse to start on this node and therefore resources which depend on it will be unrunnable on the same node as well.</font></i><br><br><font size="2">based on this description it is still unclear to me how I would go about implementing resource level fencing in my own cluster. I tried researching the topic for examples, but could not find much on the subject.<br></font><br><font size="2"><br>Could you please shed some light on how I could implement resource level fencing in my own cluster? and how it differentiates from traditional STONITH device fencing? If you had an example of resource level fencing, that would be very helpful.</font><br><font size="2"><br>Thanks,</font><br><br><b><font size="2">Phil Stedman</font></b><br><font size="2">Db2 High Availability Development and Support<br>Email: pmstedma@us.ibm.com</font><BR>
</body></html>