Re: Bogus Message on VMWare ESX

I've solved in two step:

1. use unicast instead of multicast or broadcast for heartbeat, on the new ha configuration
2. use iptables or a firewall to accept heartbeat packets only from the correct node

Diego

[email protected] ha scritto:
> hello
> 
> thanks for the fast reply.
> 
>> Usually I've only seen this with multiple disparate installs on the same
>> subnet. If this is the case, if you run a tcpdump you should see multicast
>> messages from another machine not in the current configuration.
>>
> 
> u mean a other ultramonkey install ? yes there is in the same network
> (class b (255.255.0.0)a prox-cluster.
> what can i do "against" ist ?
> 
> anyway when i am back tomorrow in the office i will look with tcpdump
> 
> regards
> 
> 
> _______________________________________________
> Ultramonkey-users mailing list
> [email protected]
> http://lists.vergenet.net/listinfo/ultramonkey-users
> 

_______________________________________________
Ultramonkey-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/ultramonkey-users