[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-users
Subject:    RE: v3 informs - snmpd.conf
From:       "Joan Landry" <Joan.Landry () overturenetworks ! com>
Date:       2010-05-26 17:21:53
Message-ID: A9FCB77F97940A418A61FD9BB71E4170031B5478 () dexbe012-6 ! exch012 ! intermedia ! net
[Download RAW message or body]

I am only using net-snmp to send traps and informs, the receiver of the traps is a \
non net-snmp entity - so all of my questions are transmit only related questions. \
With that I have the following issues I have not been able to resolve or figure out.

1. I am able to send and inform (and see it on the receiving station) but in order to \
get this to work I have to specify the engineID of the receiving entity in the \
trapsess cmd in snmpd.conf such as:

trapsess -Ci -e remoteengineId -l authPriv -u v3user2 -a MD5 -A abcdefgh -x DES -X \
abcdefgh 10.11.12.1

So I am not able to get net-snmp to automatically determine the engineId of the \
remote station as indicated should work per your reply below. So is it possible I am \
missing something else?

2. I have not found any documentation and I have not been able to figure out how to \
specify the notification filtering per the snmpNotifyFilterProfileTable and the \
snmpNotifyFilterTable. The configuration of these tables is not done not via an snmp \
set - so I need to be able to specify the filtering information in the snmpd.conf \
file. Any information on where I can find this type of information would be greatly \
appreciated. Thanks,
JL

-----Original Message-----
From: dave.shield@googlemail.com [mailto:dave.shield@googlemail.com] On Behalf Of \
                Dave Shield
Sent: Friday, May 21, 2010 3:50 AM
To: Joan Landry; Ron Rader
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: v3 informs - snmpd.conf

On 20 May 2010 16:46, Ron Rader <ron.rader@cipheroptics.com> wrote:
> If you wish to use
> INFORMs instead of TRAPs, your agent needs to include the remote
> target's engineID.

That's strictly accurate, but slightly misleading.
SNMPv3 requests will always include _some_ engine ID.
Which engine ID this is, depends on the style of request.

With traps, this will typically be the engineID of the sending application,
so the notification receiver needs to be configured with SNMPv3
users that specify this engine ID explicitly.

With INFORM notifications (as with the other GET* and SET requests),
this will typically be the engineID of the notification receiver.
and the sending application will probe to discover this automatically.
So it's *not* necessary to specify this explicitly in the "snmpinform"
or "trapsess" directive.
   (Or in the snmptrapd.conf createUser directive either, since this is
the natural engine ID of the trap receiver anyway)


Of course, it's always possible to explicitly specify a different engineID
for both the sending application and the notification receiver.  The vital
thing is that the same value should be used for both sides.


Dave

------------------------------------------------------------------------------

_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users


[prev in list] [next in list] [prev in thread] [next in thread]