On 26 May 2010 11:44, Tony Thomas <[email protected]> wrote:
> In my system, when a new element is added to the network, the subagent in it
> sends a notification (V3 trap) to the master agent in the network using its
> unique engineID. As per the tutorial, I understand that the snmptrapd.conf
> should have the engineID pre-configured in its snmptrapd.conf to receive the
> notification.
>
> As per system requirements, the new element must be added to system without
> user intervention (not possible to manually configure the engineID in master
> element). Also it is not acceptable to restart the snmptrapd service in
> master whenever a new element is added (snmptrapd.conf is updated with new
> engineID).
>
> Has anyone faced a situation like this? Any solution/suggestion would be
> highly appreciated.
Two options spring to mind:
a) configure the new element to send an INFORM notification
rather than a trap. In this situation, the authoritative engine is
the receiver (snmptrapd), so the engine ID remains constant
(and will be probed for anyway).
b) configure the new element to use an explicitly specified engineID
when sending traps, and configure snmptrapd with users that
also specify the same engineID.
Dave
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
