[189409] in North American Network Operators' Group
Re: SNMP "bridging"/proxy?
daemon@ATHENA.MIT.EDU (Wes Hardaker)
Tue May 24 15:55:31 2016
X-Original-To: nanog@nanog.org
From: Wes Hardaker <wjhns61@hardakers.net>
To: Eric Kuhnke <eric.kuhnke@gmail.com>
In-Reply-To: <CAB69EHg3LtCvggHRvYGdRkMEn0nTGbP6jWtW6_ihA2xiuSM3-g@mail.gmail.com>
(Eric Kuhnke's message of "Fri, 20 May 2016 17:09:22 -0700")
Date: Mon, 23 May 2016 14:50:02 -0700
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Eric Kuhnke <eric.kuhnke@gmail.com> writes:
> http://www.adventuresinoss.com/2009/09/30/the-many-uses-of-net-snmp/
Ha! I've never seen that article, thanks for pointing it out.
Note that the performance of Net-SNMP's extensibility mechanisms should
way into the decision. The fastest backend needs to be written in C,
and embedded perl is an easy second. Beyond that, pass_persist is
somewhere in the middle and pass/extend/other execs are the slowest
because of the need to exec a command for every incoming request which
is expensive. Great for bootstrapping and testing, but in the long run
look to the better coding solutions.
Tutorials for most of these exist:
http://www.net-snmp.org/wiki/index.php/Tutorials#Coding_Tutorials
[as a point of history: Net-SNMP has always been very extensible since
it was started based on my need to add extensibility to an agent way
back in 1995-ish in order to monitor some special cases on a map with HP
OV (as it was known back then)]
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://blog.capturedonearth.com/
