try broadcast mode On 11/30/2011 10:24 AM, David Golovan wrote: > All setting set to default(multicast address and port) now and same > still problem. > > The multicast looks like working, I can't check the switch, but we ran > multicast test on both servers(using mdump tool) and it works fine. > Also, using tcpdump I can see that both servers communicate with each > other using cluster multicast address and port. > > David Golovan > > On 11/30/2011 06:44 PM, Digimer wrote: >> On 11/30/2011 11:39 AM, David Golovan wrote: >>> Hi, >>> >>> Thanks for the help. >>> >>> I have removed the multicast address(now the cluster choose the address) >>> and tried to change the default port for multicast (from 5404 to 5400), >>> but no luck, still same problem... >>> >>> While changing this settings I have noticed something: >>> >>> I have removed to multicast address from the cluster(using luci) and >>> reboot only one node. When the node started it couldn't connect to the >>> cluster(as they had different multicast addresses), so it created >>> cluster of his own with same ring id as the second node's cluster. And >>> this time it didn't entered the loop of creating cluster generation number >>> >>> David Golovan >> If you can avoid changing the port or the IP and just let the cluster >> use the default multicast, it would be best. Also make sure that, if you >> have a managed switch, that it is handling multicast properly. >> > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
