On Wed, 4 Feb 2015, Tait Clarridge wrote:
Got it!
http://www.rsyslog.com/doc/v5-stable/configuration/modules/imudp.html
So I just have to use something like below, since I am using older rsyslog
$ModLoad imudp
$UDPServerAddress 192.168.1.100
Thanks a lot!
Asif,
You may run into filtering issues with loading up on IPs that way,
I've found the easiest way to deal with that is via rulesets where
your config might look like:
$ModLoad imudp
$RuleSet CiscoDevices
$RulesetCreateMainQueue on
# This can also go into a template where the IP or hostname received is used
*.* /var/log/cisco/cisco.log
$InputUDPServerBindRuleset CiscoDevices
$UDPServerAddress 192.168.1.100
$UDPServerRun 514
$RuleSet JuniperDevices
$RulesetCreateMainQueue on
*.* /var/log/juniper/juniper.log
$InputUDPServerBindRuleset JuniperDevices
$UDPServerAddress 192.168.2.100
$UDPServerRun 514
I haven't tested whether the UDPServerAddress config option actually
binds that IP to the ruleset, I usually just do port (with
UDPServerRun) which I know binds correctly to the ruleset for anything
received on that port.
When you start doing this sort of thing, you _really_ want to upgrade to
something closer to current so that you can use the new configs.
Going from 5.x you will also see a huge performance improvement as well as not
getting confused as to what's happening.
David Lang
_______________________________________________
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.
