I'm looking for the best way to put my rsyslog servers behind a VIP for TCP & 
UDP traffic.

It appears that the best solution thus far at least for TCP is fault tolerant 
setup with port probing.  I have tried a VIP load balance/round-robin 
configuration but it takes a while for the syslog/rsyslog client to start 
logging to the surviving rsyslog server when I bring one down.  As for UDP I'm 
not having good results at all and I'm starting to wonder if the best solution 
would be to have a static VIP IP where I use CLUSTERIP configuration on my 
systems where the failover occurs over the virtual network interface.

Any suggestions is appreciated.


Here is my configuration:


syslog/rsyslog client ->->->-> VIP ->->->-> rsyslog_server1, rsyslog_server2

VIP options:  1) fault tolerant w/port probing 2) load balance/round robin 3) 
static IP (multicast) utilizing CLUSTERIP option.

I prefer the load balance configuration for data center HA.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards

Reply via email to