Hi, I have two node active/passive setup. This is my configuration:
#service firewalld stop #vi /etc/hosts --> 192.168.2.121 (Node1) / 192.168.2.122 (Node2) ------------- Private Network (Direct connect) #systemctl start pcsd.service #systemctl enable pcsd.service #passwd hacluster --> define pw #pcs cluster auth Node1 Node2 #pcs setup --name Cluster Node1 Node2 #pcs cluster start -all #pcs property set stonith-enabled=false #pcs resource create ClusterIP ocf:heartbeat:IPaddr2 ip=192.168.10.123 cidr_netmask=32 op monitor interval=30s #pcs resource defaults resource-stickiness=100 #pcs resource create ens192-monitor ethmonitor interface=ens192 --clone #pcs constraint location ClusterIP rule score=-INFINITY ethmonitor-ens192 ne 1 My goal is to have two interfaces, service network(ens192) and heartbeat network(ens224). Based on my research, ethmonitor is used to monitor the interface via pacemaker, if there's a failed link, resources will failover to other Node. My problem is no error were prompted via pcs status, resource does not failover and service(ClusterIP) goes down. Testing scenario: 1. Disconnected physicall Link of Node1 ----> No error appears on pcs status and ClusterIP is not reachable as failover to other node does not happen. Any ideas? Is this a bug? Are there any missing configurations? Regards, imnotarobot
_______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
