Hi Rushik,
That would be an error. The lexicographic ordering should be maintained
all the time.
What version of SNMP4J-Agent are you using? Have you modified it?
Do you change Managed Object OIDs while the managed object is registered
(that could cause such an error
and must not be done).
The unregisterMOs method is exactly what works. Why do you think it does
not?
Best regards,
Frank
Am 31.03.2016 um 17:37 schrieb [email protected]:
Is there a way to disable the snmp4j mibs ? These are the snmp4j specific mibs that have
"4976" in their OID.
My issue is when I do a getNext at the end of Mib Tree for a private enterprise
Mibs that I have I see the 4976 returned instead of my next custom private MIB
which are at 41192.
I get this back when I do a getnext:
"enterprises.4976.10.1.1.1.1.1.1.0 org.snmp4j.log.Log4jLogFactory@2b7639c8"
I tried to unregister the snmp4jLobMib in my extended BaseAgent class:
"snmp4jLogMIB.unregisterMOs(server, getContext(snmp4jLogMIB));" but that didn't
work.
thanks
Rushik
_______________________________________________
SNMP4J mailing list
[email protected]
https://oosnmp.net/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
[email protected]
https://oosnmp.net/mailman/listinfo/snmp4j
