Well after looking at the documentation for this it appears this is a client/server use case... I cannot leverage this since my devices that are syslogging to my rsyslog servers are appliance type devices where I cannot configure RELP.
Back to the drawing board... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martinez, Carlos R Sent: Thursday, April 19, 2012 8:26 AM To: rsyslog-users Subject: Re: [rsyslog] rsyslog | VIP I assume the RELP configuration on the rsyslog server is easy to setup... would you happen to have a sample configuration using VIP load balancing? I will also search the rsyslog.com site for specific documentation. Thanks! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vlad Grigorescu Sent: Thursday, April 19, 2012 7:18 AM To: rsyslog-users Subject: Re: [rsyslog] rsyslog | VIP Well, the simplest solution would be for your clients to use RELP. That being said, I don't have RELP forwarding for most of my clients. I have two rsyslog forwarders behind a VIP. They both use RELP to forward to the central rsyslog server. I use load balance/round-robin, and have a health check for a high TCP port that I open with imtcp. There are no logs going to that port, it's just open to SYN/ACK. The health check probes the port every second, and if it goes down, it shunts all traffic to the other system. It's not as fast as it could be, but short of using multicast, I haven't found a better solution. --Vlad On 4/19/12 8:47 AM, Martinez, Carlos R wrote: > 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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
