Re: [ClusterLabs] heartbeat IP chenged to 127.0.0.1

2020-05-13 Thread Strahil Nikolov
On May 12, 2020 3:10:28 PM GMT+03:00, kexue 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 >    

Re: [ClusterLabs] heartbeat IP chenged to 127.0.0.1

2020-05-13 Thread kexue
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 corosync.conf: totem {     version: 2     secauth: on     cluster_name: mycluster     transport: udpu     rrp_mode:

Re: [ClusterLabs] heartbeat IP chenged to 127.0.0.1

2020-05-13 Thread 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 wrote: Hi, I have a two-nodes cluster on

[ClusterLabs] heartbeat IP chenged to 127.0.0.1

2020-05-12 Thread kexue
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    =