Re: How to run my legacy snmp "agent" as sub-agent of net-snmp agent
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
2009/7/3 Krishna Mohan <[email protected]>: > I configured net-snmp listening on port 161 to proxy requests for all OIDs > (.1.3) as below expecting it to proxy all requests to legacy agent > listening on port 1661 > proxy -v 2c -c public localhost:1661 .1.3 No - that will proxy any request ==>that does not have a more specific registration<==. A more specific registration (i.e. longer root OID) will always take precedence over more general ones (with a shorter root OID). See the AgentX specs for details. > In other words, I observed, for MIBs having implemented > in both master-agent (snmpd) and sub-agent (legacy agent), master-agent > implementation supersedes It's not a matter of the master superceding the subagent. Rather it's a more specific registration taking precedence over a general one. If you want to direct requests to the proxied agent, the best approach would be to disable the unwanted module in the master agent (e.g. snmpd -I-module....) Failing that, it *might* be possible to explicitly registering the OID in question via "proxy". Though I suspect you might run into problems with duplicate registrations. The best approach is definitely to turn off the bits you don't want in the master agent. Dave ------------------------------------------------------------------------------ _______________________________________________ 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