[rtg] RE: RTG Digest, Vol 27, Issue 4

[eji]

Steve,

Nice try. If it's generic to make adding new types of
devices and OIDs configurable, and also provide the
input interfaces for plain file, database etc, that
would be very useful. Looking forward to its coming.

For us, we ended up writing our own targetmaker script,
but it's very customized, so if there's a flexible
alternative that's nice.

Regards,
Eric


   1. Developing a carrier-class replacement for
rtgtargmaker.pl
      (Steve Scaffidi)

Message: 1
Date: Wed, 10 May 2006 15:04:54 -0400
From: "Steve Scaffidi" <sscaffidi at gmail.com>
Subject: [rtg] Developing a carrier-class replacement
for
	rtgtargmaker.pl
To: rtg at fireflynetworks.net
Message-ID:
	
<c6f957e10605101204t7722b828x909009b34e5c0be6 at mail.gmai
l.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi there.

I've been playing with RTG for the past two months with
the idea that I may
be able to use it to replace Trend SNMP. The poller
itself is quite
impressive and works exactly as I'd like it to.

However, I ended up having several serious issues with
rtgtargmaker.pl,
making that script unusable for configuring RTG for my
network. It functions
exactly as it's supposed to, but I have some very
ornery SNMP devices.

On the other hand, the beauty of open source is that
one can simply fix or
replace what doesn't work for what does.


I work for a company with a large network with several
dozen different types
of devices. I've begun writing a configuration engine
for RTG, in Perl, that
should address my (and my company's) needs, and perhaps
it could be useful
for others using RTG.

I have already applied for hosting of the project on
Sourceforge.net and I
hope to be approved within a week. Currently, I
consider my code in
pre-alpha state - 75% of the basic functionality is
written. I plan on
having a functional *alpha* demo within a week.

If anyone on the list is interested, I would be
delighted to have the input
of some other developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://gizmo.fireflynetworks.com/pipermail/rtg/attachme
nts/20060510/e6368edb/attachment-0001.htm