Ok,

# netstat -aunp
Aktive Internetverbindungen (Server und stehende Verbindungen)
Proto Recv-Q Send-Q Local Address               Foreign Address             
State       PID/Program name
udp        0      0 0.0.0.0:32769               0.0.0.0:*                       
        2377/heartbeat: wri
udp        0      0 0.0.0.0:514                 0.0.0.0:*                       
        1542/syslogd
udp        0      0 0.0.0.0:32771               0.0.0.0:*                       
        2379/heartbeat: wri
udp        0      0 0.0.0.0:32772               0.0.0.0:*                       
        2381/heartbeat: wri
udp        0      0 0.0.0.0:32773               0.0.0.0:*                       
        2383/heartbeat: wri
udp        0      0 0.0.0.0:32774               0.0.0.0:*                       
        2385/heartbeat: wri
udp        0      0 0.0.0.0:32775               0.0.0.0:*                       
        2387/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2387/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2385/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2383/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2381/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2379/heartbeat: wri
udp        0      0 0.0.0.0:694                 0.0.0.0:*                       
        2377/heartbeat: wri
udp        0      0 0.0.0.0:8120                0.0.0.0:*                       
        2210/tweety
udp        0      0 10.11.20.222:123            0.0.0.0:*                       
        1701/ntpd
udp        0      0 10.11.20.224:123            0.0.0.0:*                       
        1701/ntpd
udp        0      0 127.0.0.1:123               0.0.0.0:*                       
        1701/ntpd
udp        0      0 0.0.0.0:123                 0.0.0.0:*                       
        1701/ntpd

I see six udp 694 ports here. This means udp bcast is still activated I think. 
I thought ucast should replace bcast?


Thanks,

Achim



Achim Stumpf schrieb:
Hi,

Dejan Muhamedagic schrieb:

If you don't have bcast directives, then there really shouldn't
be any broadcasts. Don't know what those messages are about.


I don't have any bcast enabled:

use_logd yes

ucast bond0 10.11.20.221
ucast bond0 10.11.20.222
ucast eth2 10.11.20.223
ucast eth2 10.11.20.224

keepalive 1
deadtime 10
warntime 5
initdead 30 # depend on your hardware

bcast bond0 eth2
watchdog /dev/watchdog

ping_group routers 10.14.0.10 10.14.0.11 10.14.0.12 10.14.0.13

crm yes
node    isintra5.fra
node    isintra6.fra

respawn root /usr/lib64/heartbeat/pingd -m 100 -d 30s -a pingd

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.


That's what I did before, but I thought ucast is a better solution for that. Does anyone know why I still get this bcast log entries, and if bcast is still acitvated. I thought bcast should be replaced by ucast to get rid of this error messages in case of another cluster on the network.


Thanks,

Achim


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to