Re: Can't calculate bindnetaddr for unicast transport

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Rene,

Rene Hellmann napsal(a):
Hello,
the following setup is running in unicast-mode on my staging cluster.

2 x CentOS 6.2 with EPEL repo , corosync 1.4.1 and pacemaker 1.1.6 .

IP 1 :192.168.2.111 / 24
IP 2 . 192.168.2.112 / 24

->  bindnetaddr : 192.168.2.0


Now I'm trying to get this version run on my live system.
2 root server on different sub.nets

Server 1.
A.A.A.A / 32  with Bcast A.A.A.127


Do you really have mask /32? Because such setup is called point-to-point and it's little special.

ip addr | grep "inet " | tail -n 1  (see 'clusters from scratcg') give me the following line
inet  A.A.A.A  peer  A.A.A.97/32  brd  A.A.A.127  scope  global  eth0


Server 2.
B.B.B.B / 32 with Bcast B.B.B.127
inet  B.B.B.B  peer  B.B.B.97/32  brd  B.B.B.127  scope  global  eth0



If I follow the script for calculating the bindnetaddr. have to bo AAAA / B.B.B.B

if I follow ip addr | grep "inet " | tail -n 1 | awk '{print $4}' | sed s/255/0/ (see 'clusters from scratch')
It has to be A.A.A.97 and B.B.B.97

I nearly tried all combinations but nothing works:
In /var/log/messages I see:

May 13 02:59:32 pgpool02 corosync[10767]:   [TOTEM ] Totem is unable to form a cluster because of an operating system or network fault. The most common cause of this message is that the local firewall is configured improperly.



netstat -nlp :
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      1260/rpcbind
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      9729/sshd
tcp        0      0 127.0.0.1:25                0.0.0.0:*                   LISTEN      1494/master
tcp        0      0 0.0.0.0:50855               0.0.0.0:*                   LISTEN      1278/rpc.statd
tcp        0      0 :::53964                    :::*                        LISTEN      1278/rpc.statd
tcp        0      0 :::111                      :::*                        LISTEN      1260/rpcbind
tcp        0      0 :::22                       :::*                        LISTEN      9729/sshd
udp        0      0 0.0.0.0:43529               0.0.0.0:*                               10767/corosync
udp        0      0 127.0.0.1:5405              0.0.0.0:*                               10767/corosync
udp        0      0 0.0.0.0:42307               0.0.0.0:*                               1278/rpc.statd
udp        0      0 0.0.0.0:49743               0.0.0.0:*                               10767/corosync
udp        0      0 0.0.0.0:606                 0.0.0.0:*                               1278/rpc.statd
udp        0      0 0.0.0.0:111                 0.0.0.0:*                               1260/rpcbind
udp        0      0 0.0.0.0:1011                0.0.0.0:*                               1260/rpcbind
udp        0      0 :::57741                    :::*                                    1278/rpc.statd
udp        0      0 :::111                      :::*                                    1260/rpcbind
udp        0      0 :::1011                     :::*                                    1260/rpcbind

As you can see a port 5405 will be opened. But only listening on 127.0.0.1.



Anyway, for point to point just set bindnet to actual IP address (because you basically don't have network address or more correctly, ip is network address). So just set:

bindnetaddr: A.A.A.A

and on second server

bindnetaddr: B.B.B.B

but keep in mind, that your setup seems to be little incorrect (if you didn't setup router / routes correctly) and peer on A.A.A.A should be B.B.B.B and reverse for B.B.B.B


Btw, I disabled iptables, firewall and selinux extensions.
There is no specific route.


Can somebody give me a hint ?
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


Honza
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux