Agent++ as subagent question

[Bettendorf, Cristian]

Hello,

1. the AGENT++v2.13NT include a proxy example, it this exactly what I need?

2. Has somebody a short HOW-TO-DOC how to configure the stuff on Solaris?

3. <<
Then you can use AgentX++ for implementing
your subagent (only very small changes are needed for that to your
existing AGENT++ agent).This is the only option for Linux (since the
linux SNMP agent is a NET-SNMP agent).
>>
ups, a new product with a new api. Ok, can somebody give me a hint which
changes I should made here?

Thanks in advance 
Cristian


-----Original Message-----
From: Frank.Fock____t-online.de [mailto:Frank.Fock____t-online.de]
Sent: Sonntag, 18. November 2001 15:15
To: Bettendorf, Cristian
Cc: 'agentpp-dl____agentpp.com'
Subject: Re: Agent++ as subagent question


Hello Cristian,

For Windows you will have to write a subagent interface for the
NT/2000 specific interface. AGENT++ will provide such an interface for
v3.x next year (althought the exact schedule have not been made yet).

At the moment you may use AGENT++v2.13NT which can be found
at http://www.agentpp.com/agent++v2_13d_nt.zip
It does implement such an interface for the obsoleted AGENT++ 2.13
version.

On Solaris, you may directly use AGENT++, since the SUN agent
uses SNMP to talk with subagents. Alternatively, you may use the
NET-SNMP master agent. Then you can use AgentX++ for implementing
your subagent (only very small changes are needed for that to your
existing AGENT++ agent). This is the only option for Linux (since the
linux SNMP agent is a NET-SNMP agent).

For Windows you have also the option to either buy a AgentX master
agent or subagent that implements the system MIBs you need. Then
you could use a AgentX++ agent as subagent or master respectively.

Hope this helps.

Best regards,
Frank


"Bettendorf, Cristian" wrote:

> Hello,
>
> most managers can't talk to agents configured to listen on a non-default
> SNMP port and also the managers can't manage more SNMP agents running on
the
> same host but each one configured to use it's own SNMP port.
>
> E.g. : under windows if I want to have both native windows snmp and my own
> Agent++ running at the same time then normally the native windows service
is
> use the port 161 and my own Agent++ something else, e.g 9161, but now the
> used managers can't access my Agent++ stuff...
>
> One solution could be to have a proxy running as windows subagent and
> forwarding all SNMP requests for a given OID tree to a preconfigured
IP:PORT
> address (the Agent++ stuff).
>
> The question is how to develop such subagent, are some code examples
> available? Or which other solution can be used here?
>
> I need to solve this for windows, solaris7, solaris8 and Linux :-(
>
> Manny thanks in advance
> Cristian Bettendorf
> Software AG