I've been doing something very similar by using a linux based load balancer. It wasn't the easiest thing to figure out how to configure, but it works very well. Here are couple of links that should get you started. I have heard on the IPVS mailing lists that Piranha will not supported by RedHat in the future, so you might be cautious about using that as a front end. https://www.centos.org/docs/5/html/Virtual_Server_Administration/index.html https://www.centos.org/docs/4/html/rh-cs-en-4/ch-lvs-piranha.html http://kezhong.wordpress.com/2010/03/28/setup-linux-loadbalancer-with-piranha-and-lvs-on-centos-5-4/
-Brandon -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martinez, Carlos R Sent: Thursday, April 19, 2012 8:48 AM To: [email protected] Subject: [rsyslog] rsyslog | VIP 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 -----Message Disclaimer----- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to [email protected] and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements. _______________________________________________ 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
