[AGENT++] notification-log-mib questions

[Frank Fock]

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