Interesting! I tested Looper-NG a few years ago because I just *love* the
feature list (traps, syslog, text files as input, database, intelligent
routing, outputs to just about anything), but I had to axe that project
December 2009 after we detected that it was the cause of performance
problems on that server (RHEL4). From what we could tell, it didn't close
files properly so that server thought it was out of disk space in /var
(when it wasn't); only a reboot would fix the false alert. I wasn't able
to pin the bad behavior down more than that (in fact, I'm just taking a
wild guess that Looper-NG wasn't closing its files properly), so I didn't
file a bug report.
- Joni
--On February 22, 2011 2:17:27 PM -0500 "Pfleger, Jim"
<[email protected]> wrote:
We were using Looper-NG (http://muthanna.com/looperng/) long before we had
Spectrum or eHealth, and we continue to use it today. I like it a lot
because we can slice and dice traps (in Perl) on their way by so we can do
some data cleanup there instead of in the EventDisp files, which can be
tricky. We can also use it as the single receiver to configure on managed
devices, and then fan traps out to all our production and dev systems,
which is the problem you're trying to solve.
HTH,
Jim
On 2/18/11 2:32 PM, "Joni Keller" <[email protected]> wrote:
Back in the days when you could buy trapexploder without the cost of
buying the rest of the eHealth suite, I would have seconded that
recommendation. We bought trapexploder way back when we had devices that
couldn't send to as many trap receivers as we wanted. I keep telling my
CA team that they should never sell a copy of Spectrum without a copy of
trapexploder, at least not if the customer is going to install Spectrum
fault tolerant. I forward non-junk traps to all of my Spectrum servers
so it doesn't matter if it's not running on the primary. I also convert
some traps into email as requested. But enough of that ...
Take a look at http://www.net-snmp.org/docs/man/snmptrapd.conf.html and
jump down to "forward OID" -- I have never done this, but I think you can
forward traps with the (free) net-snmp package.
HTH,
- Joni
--On February 14, 2011 4:59:23 AM -0500 Marcel Schulte
<[email protected]> wrote:
Hi list,
we have several snmp devices sending traps to only a limited number of
receivers.
Because of this we'd like to force them to send the traps to a third
IP only which then duplicates the traps to our two FT nodes.
Did anyone of you do something like this? What would be the best way
to get this working?
Many thanks in advance!
Regards,
Marcel
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
