[147279] in North American Network Operators' Group
Re: Writable SNMP
daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Dec 6 15:39:16 2011
In-Reply-To: <20111206201338.GA47906@ussenterprise.ufp.org>
From: Jared Mauch <jared@puck.nether.net>
Date: Tue, 6 Dec 2011 14:38:13 -0600
To: Leo Bicknell <bicknell@ufp.org>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
What SNMP does have for it is it is lightweight (to some extent) vs XML that=
can get quite bulky, and certainly is the case when trying to do many inter=
faces at once.=20
I have seen better precision with snmp vs cli interaction/tcp based interact=
ion.=20
snmpbulkwalk has been my cruel mistress for several years... But does provid=
e the detail/accuracy most days.=20
Also keep in mind most hardware only pulls or pushes counters every 5s anywa=
ys...
Jared Mauch
On Dec 6, 2011, at 2:13 PM, Leo Bicknell <bicknell@ufp.org> wrote:
>=20
> I actually would submit SNMP was never the right tool for the job,
> just the tool we had. Even today where it's most popular use is
> to poll interfaces for statistics it would be easier on the device,
> programmer, and operator to make one tcp connection, send a list
> of things to poll, and get back a blob of text. I hesitate to say
> XML + Restful, becuse I think it need not be that specific solution,
> but that is a solution that meets the criteria. The only thing SNMP has
> going for it at this point in time is inertia.
