On Wed, Sep 08, 2021 at 02:17:14PM -0400, Bill Fenner wrote: > On Fri, Sep 3, 2021 at 3:43 AM Feroz <feroz.afs...@gmail.com> wrote: > > > My question is, is there a way to block an agent from responding to > > queries ( by timeout), till time the sub-agent connects to the agent. > > > > No, the master agent always lives under the impression that it knows > everything. You may be able to fake it out by giving it an unreachable > proxy, something like "proxy udp:127.0.0.1:9 .1.3", and then having the > agentx registration use a better priority so that it overrides the proxy > config for each subtree that agentx registers. However, this does use up > snmp server resources trying to proxy each request to something that will > not respond. > > This is an interesting problem, especially if you have multiple > sub-agents. What if you had one sub-agent that serves IP-MIB, and a > separate one that serves the system MIB? Would you want to ignore requests > until both subagents are connected?
Given that the system MIB contains sysORTable I have to say I find the choise to put it in a subagent odd. /MF _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
