[ClusterLabs] (no subject)
kgaillot at redhat.com
Fri Sep 3 10:55:39 EDT 2021
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" 
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
> reason behind.
>  https://access.redhat.com/solutions/30564
Ken Gaillot <kgaillot at redhat.com>
More information about the Users