fence_xvmd - Libvirt-based, general purpose fencing host for virtual
fence_xvmd is an I/O Fencing host which resides on bare metal machines
and is used in conjunction with the fence_xvm fencing agent. Together,
these two programs can be used to fence can be used machines which are
part of a cluster.
If the virtual machines are backed by clustered storage or the virtual
machines may be migrated to other physical machines, all physical
machines in question must also be a part of their own CMAN/OpenAIS
based cluster. Furthermore, the bare metal cluster is required to have
fencing configured if virtual machine recovery is expected to be
fence_xvmd accepts options on the command line and from cluster.conf
-f Foreground mode (do not fork)
-d Enable debugging output. The more times you specify this
parameter, the more debugging output you will receive.
IP family to use (auto, ipv4, or ipv6; default = auto)
Multicast address to listen on (default=18.104.22.168 for ipv4,
ff02::3:1 for ipv6)
Port to use (default=1229)
Network interface to listen on, e.g. eth0.
Authentication type (none, sha1, sha256, sha512;
default=sha256). This controls the authentication mechanism
used to authenticate clients. The three SHA hashes use a key
which must be shared between both the virtual machines and the
host machine or cluster. The three SHA authentication
mechanisms use a simple bidirectional challenge-response based
on pseudo- random number generation and a shared private key.
Packet hash type (none, sha1, sha256, sha512; default=sha256).
This controls the hashing mechanism used to authenticate fencing
requests. The three SHA hashes use a key which must be shared
between both the virtual machines and the host machine or
Use the specified key file for packet hashing / SHA
authentication. When both the hash type and the authentication
type are set to "none", this parameter is ignored.
-u Fence by UUID instead of virtual machine name.
-? Print out a help message describing available options, then
-h Print out a help message describing available options, then
-X Do not connect to CCS for configuration; only use command line
parameters. CCS configuration parameters override command line
parameters (because they are cluster-wide), so if you need to
override a configuration option contained in CCS, you must
specify this parameter.
-L Local-only / non-cluster mode. When used with -X, this this
option prevents fence_xvmd from operating as a clustered
service, obviating the need to configure/run CMAN on the host
-U uri Force use of the specified URI for connecting to the hypervisor.
-V Print out a version message, then exit.
CCS options are simply attributes of the <fence_xvmd> tag, a child of
the <cluster> tag in /etc/cluster/cluster.conf.
Same as the -d option. Specify numbers >1 for more debugging
Same as the -i option.
Same as the -a option.
Same as the -p option.
Same as the -C option.
Same as the -c option.
Same as the -k option.
Same as the -u option.
fence(8), fence_node(8), fence_xvm(8)