Reading this article is recommended if you want to use SNMP4J-Agent Manged Objects (MIB) objects like MOScalar and MOTable with multiple SNMPv3 contexts in your agent.
In SNMPv3 the concept of using contexts is generally used to separate MIB data into different virtual MIBs named by the context name. As a consequence, a basic requirement for the MIB instrumentation is, that the data content is separated by the contexts. With SNMP4J-Agent you have basically three options to realize this requirement:
For each context create a separate ManagedObject
instance and register it with the target context using MOServer.register
.
MOScalar myScalarObjAContext1 = new MyScalarObjA(..); MOScalar myScalarObjAContext2 = new MyScalarObjA(..); MOServer server = ..; server.register(myScalarObjAContext1, new OctetString("context1")); server.register(myScalarObjAContext2, new OctetString("context2")); |
Use the same ManagedObject
instance for all target contexts by calling MOServer.register
repeatedly for each context with the same instance. The single instance is then responsible to deliver and update its content (MIB data) based on the context information given in the ManagedObject.get
, .next
, .prepare
, .commit
, .undo
, and .cleanup
SubRequest
parameter in the MOScope
(in fact it is then a MOContextScope
) member.
OctetString context1 = new OctetString("context1"); OctetString context2 = new OctetString("context2"); MOScalar myScalarObjA = new MyScalarObjA(..) { public void get(SubRequest request) { if (request.gewtScope() instanceof MOContextScope) { MOContextScope scope = (MOContextScope)request.gewtScope(); if (context1.equals(scope.getContext()) { // return value from context1 .. } else if (context2.equals(scope.getContext()) { // return value from context2 .. } else { // cannot be reached } } } } MOServer server = ..; server.register(myScalarObjA, context1); server.register(myScalarObjA, context2)); |
Define the context values you want to support in the agent:
//|:AgenPro|=members OctetString context1 = new OctetString("ctx1"); OctetString context2 = new OctetString("ctx2"); //|AgenPro:| |
Add the contexts to the MOServer instance(s) you use in the agent:
public static void main(String[] args) { //|:AgenPro|=main server.addContext(context1); server.addContext(context2); defaultMain(args); //|AgenPro:| } |
Register your MIB object instances for each context separately (as explained above in the Background section):
protected void registerMIBs() { //|:AgenPro|=registerBefore // Create a new instance per generated MIB module (you can use different MOFactory instances per context if needed): Snmp4jAgentTutorialMib tutorialMibCtx1 = new Snmp4jAgentTutorialMib(getFactory()); tutorialMibCtx1.register(server, context1); Snmp4jAgentTutorialMib tutorialMibCtx2 = new Snmp4jAgentTutorialMib(getFactory()); tutorialMibCtx2.register(server, context2); //|AgenPro:| .. } |
Configure the SNMPv3 View-based Access Control Model (VACM) MIB to allow SNMPv3 (and/or SNMPv1/2vc) users to access the new non-default contexts:
protected void registerMIBs() { .. //|:AgenPro|=registerAfter VacmMIB vacm = agent.getAgentConfigManager().getVacmMIB(); vacm.addAccess(new OctetString("v3group"), context1, SecurityModel.SECURITY_MODEL_ANY, SecurityLevel.AUTH_PRIV, MutableVACM.VACM_MATCH_EXACT, new OctetString("fullReadView"), new OctetString("fullWriteView"), new OctetString("fullNotifyView"), StorageType.nonVolatile); vacm.addAccess(new OctetString("v3group"), context2, SecurityModel.SECURITY_MODEL_ANY, SecurityLevel.AUTH_PRIV, MutableVACM.VACM_MATCH_EXACT, new OctetString("fullReadView"), new OctetString("fullWriteView"), new OctetString("fullNotifyView"), StorageType.nonVolatile); .. //|AgenPro:| |
Related articles
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|