Hi, On Mon, Jun 02, 2008 at 03:03:18PM +0200, Achim Stumpf wrote: > Hi, > > I want to configure only ucast for heartbeat between the two nodes. In > ha.cf I got: > > ucast eth0 10.11.20.221 > ucast eth0 10.11.20.222 > ucast eth1 10.11.20.223 > ucast eth1 10.11.20.224 > > In the logs I see: > > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: write socket > priority set to IPTOS_LOWDELAY on eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound send > socket to device: eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound > receive socket to device: eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: started on > port 694 interface eth0 to 10.11.20.221 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: write socket > priority set to IPTOS_LOWDELAY on eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound send > socket to device: eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound > receive socket to device: eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: started on > port 694 interface eth0 to 10.11.20.222 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: write socket > priority set to IPTOS_LOWDELAY on eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound send > socket to device: eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound > receive socket to device: eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: started on > port 694 interface eth1 to 10.11.20.223 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: write socket > priority set to IPTOS_LOWDELAY on eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound send > socket to device: eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: bound > receive socket to device: eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: ucast: started on > port 694 interface eth1 to 10.11.20.224 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: UDP Broadcast > heartbeat started on port 694 (694) interface eth0 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: UDP Broadcast > heartbeat closed on port 694 interface eth0 - Status: 1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: UDP Broadcast > heartbeat started on port 694 (694) interface eth1 > Jun 2 14:53:45 isintra5 heartbeat: [4767]: info: glib: UDP Broadcast > heartbeat closed on port 694 interface eth1 - Status: 1 > > So , ucast is working it looks like, but I am surprised, that bcast is > still working.
If you don't have bcast directives, then there really shouldn't be any broadcasts. Don't know what those messages are about. > In the future I will have multiple heartbeat clusters each > of a pair. I am wondering, if I would put now a second independent Cluster > pair on the network, if they see each other and complain about the bcast > messages as I had before. > > So far as I understood it now, ucast should prevent one of such errors, of > mutliple Clusters on the network. > > Does it do now, what I want or not? As long as you keep them on different UDP ports you should be OK. Of course, with only ucast directives you could use the same UDP port. Thanks, Dejan > > Thanks, > > Achim > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
