[ClusterLabs] Stonith configuration
BASDEN, ALASTAIR G.
a.g.basden at durham.ac.uk
Fri Feb 14 05:41:58 EST 2020
Hi,
I wonder whether anyone could give me some advice about a stonith
configuration.
We have 2 nodes, which form a HA cluster.
These have 3 networks:
A generic network over which they are accessed (eg ssh)
(node1.primary.network, node2.primary.network)
A directly connected cable between them (10.0.6.20, 10.0.6.21).
A management network, on which ipmi is (172.16.150.20, 172.16.150.21)
We have done:
pcs cluster setup --name hacluster node1.primary.network,10.0.6.20 node2.primary.network,10.0.6.21 --token 20000
pcs cluster start --all
pcs property set no-quorum-policy=ignore
pcs property set stonith-enabled=true
pcs property set symmetric-cluster=true
pcs stonith create node1_ipmi fence_ipmilan ipaddr="172.16.150.20" lanplus=true login="root" passwd="password" pcmk_host_list="node1.primary.network" power_wait=10
pcs stonith create node2_ipmi fence_ipmilan ipaddr="172.16.150.21" lanplus=true login="root" passwd="password" pcmk_host_list="node2.primary.network" power_wait=10
/etc/corosync/corosync.conf has:
totem {
version: 2
cluster_name: hacluster
secauth: off
transport: udpu
rrp_mode: passive
token: 20000
}
nodelist {
node {
ring0_addr: node1.primary.network
ring1_addr: 10.0.6.20
nodeid: 1
}
node {
ring0_addr: node2.primary.network
ring1_addr: 10.0.6.21
nodeid: 2
}
}
quorum {
provider: corosync_votequorum
two_node: 1
}
logging {
to_logfile: yes
logfile: /var/log/cluster/corosync.log
to_syslog: no
}
What I find is that if there is a problem with the directly connected
cable, the nodes stonith each other, even though the generic network is
fine.
What I would expect is that they would only shoot each other when both
networks are down (generic and directly connected).
Any ideas?
Thanks,
Alastair.
More information about the Users
mailing list