1
2fence_xvmd(8) System Manager's Manual fence_xvmd(8)
3
4
5
7 fence_xvmd - I/O Fencing agent host for Xen virtual machines.
8
9
11 fence_xvmd [OPTION]...
12
13
15 fence_xvmd is an I/O Fencing host which resides on dom0 and is used in
16 conjunction with the fence_xvm fencing agent. Together, these two pro‐
17 grams can be used to fence can be used to fence Xen virtual machines
18 which are part of a cluster. There is a requirement that the parent
19 dom0s are also a part of their own CMAN/OpenAIS based cluster, and that
20 the dom0 cluster does not share any members with the domU cluster.
21 Furthermore, the dom0 cluster is required to have fencing if domU
22 recovery is expected to be automatic.
23
24 fence_xvmd accepts options on the command line.
25
26
28 -f Foreground mode (do not fork)
29
30 -d Enable debugging output. The more times you specify this param‐
31 eter, the more debugging output you will receive.
32
33 -i family
34 IP family to use (auto, ipv4, or ipv6; default = auto)
35
36 -a address
37 Multicast address to listen on (default=225.0.0.12 for ipv4,
38 ff02::3:1 for ipv6)
39
40 -p port
41 Port to use (default=1229)
42
43 -C auth
44 Authentication type (none, sha1, sha256, sha512;
45 default=sha256). This controls the authentication mechanism
46 used to authenticate clients. The three SHA hashes use a key
47 which must be shared between both the Xen virtual machines and
48 the host domain-0 cluster. The three SHA authentication mecha‐
49 nisms use a simple bidirectional challenge-response based on
50 pseudo- random number generation and a shared private key.
51
52 -c hash
53 Packet hash type (none, sha1, sha256, sha512; default=sha256).
54 This controls the hashing mechanism used to authenticate fencing
55 requests. The three SHA hashes use a key which must be shared
56 between both the Xen virtual machines and the host domain-0
57 cluster.
58
59 -k key_file
60 Use the specified key file for packet hashing / SHA authentica‐
61 tion. When both the hash type and the authentication type are
62 set to "none", this parameter is ignored.
63
64 -u Fence by UUID instead of Xen Domain name.
65
66 -? Print out a help message describing available options, then
67 exit.
68
69 -h Print out a help message describing available options, then
70 exit.
71
72 -X Do not connect to CCS for configuration; only use command line
73 parameters. CCS configuration parameters override command line
74 parameters (because they are cluster-wide), so if you need to
75 override a configuration option contained in CCS, you must spec‐
76 ify this parameter. -V Print out a version message, then exit.
77
78
80 CCS options are simply attributes of the <fence_xvmd> tag, a child of
81 the <cluster> tag in /etc/cluster/cluster.conf.
82
83 debug="1"
84 Same as the -d option. Specify numbers >1 for more debugging
85 information.
86
87 family="param"
88 Same as the -i option.
89
90 multicast_address="param"
91 Same as the -a option.
92
93 port="param"
94 Same as the -p option.
95
96 auth="param"
97 Same as the -C option.
98
99 hash="param"
100 Same as the -c option.
101
102 key_file="param"
103 Same as the -k option.
104
105 use_uuid="1"
106 Same as the -u option.
107
108
109
110
111 SEE ALSO
112 fence(8), fence_node(8), fence_xvm(8)
113
114
115
116 fence_xvmd(8)