RE: AgentX problems

Hi, 

> Aha!
> That explains why things aren't working the way you expected.

> Your AgentX subagent is registering stuff in the (non-default)
> context "public".    That means that the subagent will only be
> contacted when the master agent receives an SNMP request specifying
the context "public".

> But most SNMP requests (and certainly most community-based
> SNMP requests) use the default context "".   So the subagent
> registration isn't seen as relevant.

> That's why the master agent isn't passing on requests to your
subagent.

> Have a look at the documentation for your subagent, and see whether
you can register things in the default context instead.

OK, I will try this.

Two last questions: Must I send no context (no NON_DEFAULT_CONTEXT flag)
or
must I send a context of length 0 (or ist this the same).
(With my tests against JAgentX, I first tried with no context and this
did
not work, and it always answered with "public" context. So I changed it
tp
"public" and it worked.)

I can specify a read and write community in my MIB browser.
If I keep it empty, it will automatically send "public". Is context and
community the same or are these different things? If it is the same,
I cannot specify an empty string in the MIB browser I use.

Regards,
Andreas


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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