[AGENT++] notification-log-mib questions

[Claus Klein]

Hi Frank,

there is an additional issue I found today while testing the  
snmpNotifyFilterTable:

With a filter which excludes the trap OID, the trap is not added to  
the notificationLogTable, but it is send anyway?

That is wrong according the http://tools.ietf.org/html/rfc3413#page-15

(1) Any appropriate filtering mechanisms are applied to determine
        whether the notification should be sent to the management  
target.
        If such filtering mechanisms determine that the notification
        should not be sent, processing continues with the next  
management
        target.
...

and http://tools.ietf.org/html/rfc3413#page-64

Otherwise, if matching entries do exist, a notification may be sent
    if the NOTIFICATION-TYPE OBJECT IDENTIFIER of the notification (this
    is the value of the element of the variable bindings whose name is
    snmpTrapOID.0, i.e., the second variable binding) is specifically
    included, and none of the object instances to be included in the
    variable-bindings of the notification are specifically excluded by
    the matching entries.
...

With best regards,

Claus


On 10.09.2010, at 00:54, Frank Fock wrote:

> Hi Claus,
>
> If AGENT++ indeed logs the notifications like you wrote
> below, then it is a bug and will be fixed in the next
> release. I will check that.
>
> Best regards,
> Frank
>
> On 09.09.2010 23:10, Claus Klein wrote:
>> Hi everybody,
>>
>> while working with the agentx master demo I tested the notification-
>> log-mib.
>>
>> First, I found, that an target address (IPv6) is not right handled!
>> 	Only 4 bytes are used instead of 16?
>>
>> Second, for each notify target, an row is created at the  
>> nlmNotifyTable.
>> 	There is no new information if each address from the
>> targetAddressTable is stored at the nlmNotifyTable again.
>> 	The RFC says, the the source Address should be stored, not the
>> destination!
>>
>> What I expected was, that one notification which occurs at the snmp
>> agent will be stored, independent of the count of targets to deliver
>> it as traps or informs.
>> In worst case, it will only stored, but not delivered (and has to be
>> polled by NMS from the nlmNotifyTable)
>>
>> Only an snmptrapd (trap client) has to write the source address of  
>> the
>> trap to distinguish the same trap from different agents.
>> That is the way, net-snmp implements it.
>>
>>
>> What is your opinion about that?
>>
>> Whit kind regards,
>>
>> Claus
>> _______________________________________________
>> AGENTPP mailing list
>> AGENTPP at agentpp.org
>> http://lists.agentpp.org/mailman/listinfo/agentpp
>
> -- 
> AGENT++
> http://www.agentpp.com
> http://www.snmp4j.com
> http://www.mibexplorer.com
> http://www.mibdesigner.com
>
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp