I will try to figure out what's happening here but I think you
misunderstand the relation between fenced and fence_node -- the
two have nothing to do with each other.
fenced deals with the fence domain and executes a fencing agent
against a node when a node is removed from the domain, based on
input from cman.
fence_node is not used by our software but is a simple and potentially
useful utility. fence_node looks up fencing parameters from ccs and
then calls the specified agent on the victim. In effect, fenced
calls fence_node when it needs to fence a node that's left the domain.