Is it possible to run net-snmp in a docker container and extend net-snmp mibs
(e.g. add an enterprise mib) from an application process running either on the
host or in another container ?
Has anyone tried this ?
We are thinking of using the MasterAgent/SubAgent net-snmp architecture for this
i.e.
* where MasterAgent would own the root of the OID tree and own all the
general snmp configuration (e.g. protocol, user/community configuration, trap
destination configuration, etc. )
* Then one or more SubAgents can register with the MasterAgent, to take
ownership of a lower portion of the OID tree (e.g. a company’s enterprise tree).
* MasterAgent and SubAgent communicate over TCP/IP between containers or
between container and host
* SubAgent can use local techniques for binding requesthandlers for OID
groups or tables
Is this thinking correct ?
If this thinking is correct, are the following message flows correct ?
* For an SNMP GET
* External snmp manager --> MasterAgent --> SubAgent --> MasterAgent -->
External snmp manager
* For an SNMP Trap
* SubAgent --> MasterAgent --> External snmp manager
Let me know,
Greg.
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
