Thanks Dave. Shall try the new version.
Appreciated!!
-Chalapathi
On Wed, 2012-04-04 at 13:37 +0100, Dave Shield wrote:
> [ First - *please* don't mail me privately, without copying
> any responses to the mailing list. I don't have the time
> or inclination to offer private, unpaid, SNMP consultancy.
> Keep discussions to the list, where others can both learn
> and offer advice. Thanks. ]
>
>
> On 4 April 2012 13:22, Chalapathi Rao <[email protected]> wrote:
> > Thanks for the prompt response Dave. Much appreciated.
> >
> >
> > On Wed, 2012-04-04 at 13:05 +0100, Dave Shield wrote:
> >
> > On 4 April 2012 11:55, Chalapathi Rao <[email protected]> wrote:
> >> We seem to be having the following issue with our snmpagent
> >> (using Net-SNMP Version: 5.3.2.2).
> >
> > First thing - that's a very old version
> > (and the 5.3.x line is no longer actively supported).
> > Would it be possible to try with something a little newer?
> >
> > We wanted do that but noticed the latest FAQ says filtering ain't supported.
> > Why is that?
>
> Because at the time that FAQ entry was written, this was
> indeed the case. It's quite normal for things to move on,
> and the documentation to lag behind.
> My suspicion is that this particular FAQ entry probably
> needs to be updated. But I'd need to check.
>
> Try it - see what happens.
>
>
>
> >> Issue: Traps can be filtered (snmpTargetMIB, snmpNotificationMIB)
> >> but INFORMs can't be.
> >
> > It's been a while since I looked at the notification filtering code,
> > but I don't believe the basic framework distinguishes between
> > Traps and Informs.
> > The basic snmpNotifyTable has a field snmpNotifyType to
> > control whether a particular target should be send a trap or
> > an inform notification. But all of the subsequent filtering is
> > common to both.
> >
> > Perhaps you could give a little more detail about how exactly
> > you are setting up the trap and inform destinations, and the
> > filtering for each of them. And what exact behaviour you are
> > seeing.
>
> PFA the config (Ignore the XXXX in TAddress. Its configured to a valid trap
> receiver).
> My tests showed that when snmpNotifyType is configuerd as trap,
> filtering seems to have worked (with include/exclude that is).,
> whereas, it didn't work when it was configured as INFORM (i.e., the
> respective trap didn't reach receiver with include).
>
>
> I strongly suspect that what you are seeing here is not a problem
> with filtering of Informs per se. Rather, it's much more likely to
> be an issue with the configuration of SNMPv3 inform targets.
> This is a known hairy topic!
>
> I suggest you try setting up an equivalent configuration using
> SNMPv2c targets (both trap and inform), and confirm whether
> or not filtering is working there.
>
> Then have a look at the documentation on the project website
> that discusses SNMPv3 informs, and have a play with that
> (*not* using filters).
> Only when you've got that working would it be sensible to try
> turning on filtering. But get the two elements working individually
> first.
>
> Dave
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
