Hi All,
We have been using SNMP4J (version 1.10.2) in our EMS application to
communicate with the network elements(Agent) we manage.
On one specific setup the behavior is bit weird and we could not conculde
where exactly the issue is.
As we know the first contact to Agent from SNMP4J(Manager) di
so my current approach of:
"discoverAuthoritativeEngineID(userTarget.getAddress(), 5000)" is not
working (returns null) so I must be hitting the scenario/implementation
dependentness, any pointers, code samples of how to approach? Sender is a
different product, so changing to INFORMs is unlikely.
Hi,
This sounds as if there are two agents using the same
engine ID.
Best regards,
Frank
Am 07.03.2012 12:53, schrieb Saravanan M:
> Hi All,
>
> We have been using SNMP4J (version 1.10.2) in our EMS application to
> communicate with the network elements(Agent) we manage.
>
> On one specific setu
David,
Then you have to follow these steps:
(1) Make sure that the trap sender are using unique engine IDs and
properly constantly
increment their engine boots counters
(2) Use USM users that are localized by the engine ID of each target.
Best regards,
Frank
Am 07.03.2012 14:37, schrieb david
Hi,
Simply use the "notify" method of the AgentXSubAgent
which implements the corresponding method of the
NotificationOriginator interface:
http://www.snmp4j.org/agentX/doc/org/snmp4j/agent/agentx/subagent/AgentXSubagent.html#notify(org.snmp4j.smi.OctetString,
org.snmp4j.smi.OID, org.snmp4j.smi
Hi
The extended index allocation preview can be found
at:
https://server.oosnmp.net/dist/snapshot/org/snmp4j/snmp4j-agentx/2.1-SNAPSHOT/
There are still some issue which need to be fixed.
The snapshot will thus be updated frequently within
the next days.
Best regards,
Frank
Am 05.03.2012 17:25,
