[SNMP4J] SNMPv3 Trap reception where autodiscovery of EID is not possible

Ganesh, Lakshmi Prabha lakshmi-prabha.ganesh at hp.com
Tue Apr 2 10:47:09 CEST 2013


Hi,

In our management environment, some of the agents operate in push only mechanism where they only send out the SNMPv3 traps to management station and will not respond for any of the SNMPGet's.
In this scenario, autodiscovery of EngineID fails hence the management station is doing the following -


1.)     Creating the user with the EID of the agent  (fixed value that is known to the administrator)

new USM(SecurityProtocols.getInstance(),new OctetString(eID), 0);

2.)     Adding this to the MPv3 model in addition to it's local EID that was added during initialization.
Snmp.getMessageDispatcher().addMessageProcessingModel(new MPv3(usm));

Can someone please help clarify if this is the right approach as though the specification recommends usage of a unique EID, to unblock the reception of traps this is being done.

Also, when trying to delete the old EID anytime the user information is modified or deleted, the below code is deleting the MPv3 model altogether. So not using this code leads to only additions of EID's for every single node IP where auto discovery of EID is not possible.
Snmp.getMessageDispatcher().removeMessageProcessingModel(new MPv3(eID.getBytes()));


Kindly clarify the right approach for this use case. Thank you.


Regards




More information about the SNMP4J mailing list