Hi,

As per Net-SNMP tutorial (refer section describing how to configure
snmptrapd to receive v3 notification  -
http://www.net-snmp.org/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications),


- With SNMPv3 TRAPs, the *authoritative* engine is the engine that sends the
trap
- user details with engineID details should be configured in snmptrapd.conf
to receive SNMP v3 trap.

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.

Thanks,
Tony
------------------------------------------------------------------------------

_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to