> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Manfred Wassmann
> Sent: Wednesday, January 16, 2008 2:42 PM
> On Mon, 14 Jan 2008, Mike Ayers wrote:
> > There is a simple workaround, though, which is to have a USM
> > username/password (secure the password!) as part of the MIB
> > information, which the MIB uses to query 127.0.0.1 for the needed
> > information. The v3 security keeps the agent locked down while your
> > MIB gets the data it needs. It's probably a good idea to have a port
> > number in that tuple, too, just in case the agent must be run on an
> > off-port.
>
> This sounds like I would have to follow the steps described in the
> "Writing aa Simple Application" tutorial to get to the data from
> within my module?
Exactly.
> I just wonder if this is also the application field of the AgentX
> stuff and if it would pay off to use it here.
No. AgentX subagents, by design, have no knowledge of their master
agent or any of its subagents. They can not even determine the addess at which
their data is being served, which is why you would need a MIB variable for port
number.
HTH,
Mike
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
