[ClusterLabs] getting "Totem is unable to form a cluster" error

[Muhammad Sharfuddin]

On 04/08/16 19:51, Jan Friesse wrote:
 >>  >> /var/log/messages:
 >>  >> Apr  6 17:51:49 prd1 corosync[8672]:  [TOTEM ] Initializing 
transport
 >>  >> (UDP/IP Unicast).
 >>  >> Apr  6 17:51:49 prd1 corosync[8672]:  [TOTEM ] Initializing
 >>  >> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
 >>  >> Apr  6 17:51:49 prd1 corosync[8672]:  [TOTEM ] The network 
interface is
 >>  >> down.
 >>  >
 >>  > ^^^ This is important line. It means corosync was unable to find
 >> interface for bindnetaddr 192.168.150.0. Make sure interface with this
 >> network address exists.
 >>  >
 >>  >
 >> this machine has two IP address assigned on interface bond0
 >>
 >> bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
 >>      link/ether 74:e6:e2:73:e5:61 brd ff:ff:ff:ff:ff:ff
 >>      inet 10.150.20.91/24 brd 10.150.20.55 scope global bond0
 >>      inet 192.168.150.12/22 brd 192.168.151.255 scope global 
bond0:cluster
 >>      inet6 fe80::76e6:e2ff:fe73:e561/64 scope link
 >>         valid_lft forever preferred_lft forever
 >
 > This is ifconfig output?
 >
No this is the output of "ip a s bond0".

 > I'm just wondering how you were able to set two ipv4 addresses (in 
this format, I would expect another interface like bond0:1 or nothing
 > at all)?
 >
These IPes are physical i.e assigned via configuration file of bond0 
interface
cat /etc/sysconfig/network/ifcfg-bond0
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=active-backup miimon=100'
BONDING_SLAVE0='em1'
BONDING_SLAVE1='em2'
BOOTPROTO='static'
IPADDR='10.150.20.91/24'
IPADDR_0='192.168.150.12/22'
LABEL_0='cluster'

 > Anyway, I was trying to create bonding interface and set second ipv4 
(via ip addr) and corosync (flatiron what is 1.4.8 + 4 for your problem 
completely unrelated
 > patches) was able to detect it without any problem.
 >
 > I can recommend you to try:
 > - Set bindnetaddr to IP address of given node (so you have to change 
bindnetaddr on both nodes)
 >
Thanks a lot, I got the similar advice from SUSE Support, and changing 
the bindnetaddr from 192.168.150.0 to 192.168.148.0(as the netmask we 
are using on this bond is bond0:cluster IP address: 192.168.150.12/22 ) 
fixed the issue.

 > - Try upstream corosync 1.4.8/flatiron
 >
Not required.

 > Regards,
 >   Honza
 >

--
Regards,
Muhammad Sharfuddin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160408/e75062ce/attachment.htm>