Re: [ClusterLabs] Antw: [EXT] Re: heartbeat IP chenged to 127.0.0.1

kexue Wed, 13 May 2020 02:45:23 -0700

Hi,guys,

I have solved this problem.

I installed NetworkManager-config-server in my centos7 OS. It changesthe behavior of NetworkManager.

Now, disconnect the heartbeat network cable, 127.0.0.1 will not bebinded to heartbeat IP.


Thanks.


在 2020/5/13 下午2:57, Ulrich Windl 写道:

kexue <kexue...@163.com> schrieb am 13.05.2020 um 08:46 in Nachricht

<940_1589352410_5ebb97da_940_560_1_826b6602-7157-4f1a-7c64-3f6583ff6...@163.com>

more configure details:

/etc/hosts:

172.60.60.34 centosA
192.168.44.34 centosA-0
192.168.55.34 centosA-1

172.60.60.35 centosB
192.168.44.35 centosB-0
192.168.55.35 centosB-1

Hi!

I don't know whether it matters, but the canonical form of host file entries
is
<IP> <FQHN> [<alias>]...

If you are also using a nameserver, make sure the FQHN in the host file
matches the name in DNS.

corosync.conf:

totem {
      version: 2
      secauth: on
      cluster_name: mycluster
      transport: udpu
      rrp_mode: passive
}

nodelist {
      node {
          ring0_addr: centosA-0
          ring1_addr: centosA-1
          nodeid: 1
      }

      node {
          ring0_addr: centosB-0
          ring1_addr: centosB-1
          nodeid: 2
      }
}

Also we run a different version, but we also set "name" of the node. ANd we
have the address explicitly, not the network (host) name...

Regards,
Ulrich

Disconnect the heartbeat network cable ,and corosync-cfgtool -s:

RING ID 0
      id    = 127.0.0.1
      status    = ring 0 active with no faults
RING ID 1
      id    = 127.0.0.1
      status    = ring 1 active with no faults

heartbeat ip binding to 127.0.0.1


在 2020/5/13 下午2:32, kexue 写道:

Thanks.

Each node has 2 similarly connected/configured NIC's. Both nodes are
connected each other by two network cables.

'unplug' means Disconnect the network cable


在 2020/5/13 下午2:12, Strahil Nikolov 写道:

On May 12, 2020 3:10:28 PM GMT+03:00, kexue<kexue...@163.com>  wrote:

Hi,

I have a two-nodes cluster on Centos7,and heartbeat interfaces connects

directly.

Execute  "corosync-cfgtool -s" command :

# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
      id    = 192.168.44.35
      status    = ring 0 active with no faults
RING ID 1
      id    = 192.168.55.35
      status    = ring 1 active with no faults

Unpluged the heartbeat network cable,Execute  "corosync-cfgtool -s"
command :

# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
      id    = 127.0.0.1
      status    = ring 0 active with no faults
RING ID 1
      id    = 127.0.0.1
      status    = ring 1 active with no faults

What is wrong with this? Could you give me some advice.

Thanks.

How do you 'unplug' the cable ?

Best Regards,
Strahil Nikolov

--
kexue
=====================================================
-岂曰无衣-
E-mail: kexue...@163.com

--
kexue
=====================================================
-岂曰无衣-
E-mail: kexue...@163.com



_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

--
kexue
=====================================================
-岂曰无衣-
E-mail: kexue...@163.com

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Antw: [EXT] Re: heartbeat IP chenged to 127.0.0.1

Reply via email to