On Mon, 2021-09-06 at 14:36 +0800, 重力加速度 wrote: > Thank you for your reply. > Let me describe in detail that there are two network ports eth0 and > eth1. They configure the IP of the same network segment, similar to > 172.0.2.51/16 and 172.0.2.52/16. They are connected to the > same network switch. Then configure access to VIP resources on the > eth0 network card, such as CIDR_ netmask=16 ip=172.0.2.50 nic=eth0, > and add the routing information of the VIP in the eth0 routing > table. Of course, I configured the VIP recurring monitor, and when I > changed eth1 to other network segments, the same test cluster can > switch normally.
Does the systemd journal or /var/log/pacemaker/pacemaker.log show any interesting messages around the time of the test? > > ------------------ 原始邮件 ------------------ > 发件人: "Ken Gaillot" <kgail...@redhat.com>; > 发送时间: 2021年9月3日(星期五) 晚上10:55 > 收件人: "Cluster Labs - All topics related to open-source clustering > welcomed"<users@clusterlabs.org>; > 抄送: "Roger Zhou"<zz...@suse.com>;"重力加速度"<1414529...@qq.com>; > 主题: Re: [ClusterLabs] (no subject) > > On Fri, 2021-09-03 at 12:14 +0800, Roger Zhou via Users wrote: > > On 9/3/21 10:09 AM, 重力加速度 via Users wrote: > > > HELLO! > > > I built a two node corosync + pacemaker cluster, and the > main > > > end runs on > > > node0. There are two network ports with the same network segment > IP > > > on node0. I > > > > This need attention a bit. > > "Usually not a good idea to connect two interfaces using the same > > subnet" [1] > > That is an unusual setup, can you describe it more? Are the ports > connected to the same network switch? Are the IPs purely local to the > subnet or is routing involved at some point? > > > > created a VIP resource on one of the network ports and specified > > > the NIC > > > attribute. When I down the network port where the VIP resource is > > > located, > > > theoretically, the cluster will automatically switch to another > > > node, but the > > > cluster did not successfully switch to another node. I don't know > > > why, and > > > there is no log information about cluster errors. Is this a bug > or > > > do I need to > > > configure some additional parameters? > > Did you configure a recurring monitor on the IP resource? Without a > monitor, the cluster will only start the resource. > > > journalctl will tell you a lot of cluster messages and might tell > you > > the > > reason behind. > > > > [1] https://access.redhat.com/solutions/30564 > > > > Cheers, > > Roger > > -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/