We have a setup where our rsyslog servers are a RHEL cluster;  shared 
virtual-IP that is "owned" by the active member. That virtual IP name is what 
all clients will send traffic to.

Our clients are RHEL 6 systems (and use the standard rsyslog version that comes 
with RHEL6). They will be sending relatively high volumes of data (auditd is 
being setup to use rsyslog on all the clients). Currently all clients are being 
setup to use tcp transport - though we will probably look into RELP later. I'm 
using the r7 stable version of rsyslog on the servers if that matters.

Are there any specific directives I should use on the client side to ensure a 
smooth and quick failover should the servers failover? 

Thanks,
Chris Bartram


"The purpose of life is not to be happy. It is to be useful, to be honorable, 
to be compassionate, to have it make some difference that you have lived and 
lived well". (Ralph Waldo Emerson)
_______________________________________________
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
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to