Proxy forwarder question

[Frank Fock]

Hello Ram,

Please see my comments inline:

Ram Krishnaswamy wrote:

> I have agent++ 3.4 on Windows NT and I am trying to configure the proxy
> forwarder to accept requests for the Microsoft native mib2 agent. First of
> all, is this possible?
>

Yes. I recommend using the ProxyForwarder available with
AGENT++v3.4.2 or later.

>
> I am running the agent++ proxy application on port 4700 and the Microsoft's
> mib2 agent is running on port 161. I created an entry in the
> SnmpTargetAddrTable with the following values:
>
> snmpTargetAddrTDomain: snmpV2.1.1
> snmpTargetAddrTAddress: 7F.00.00.01.00.A1  ie. (127.0.0.1/161)
> snmp..Tag: v1request
> snmp..addrParams: defaultV1Trap (this is the only string I can add to make
> it to work)
>

You should make a new entry in the snmpTargetParamTable
which fits your proxy needs. You can then reference it instead
of using "defaultV1Trap".

>
> The instance is 127.0.0.1/161.
>
> I was able to create the instance okay. But when I query for mib2, I get a
> no such object.

Mmmh, how do you query? Using SNMPv3 with a context engine
ID other than your proxy's engine ID? Or did you use SNMPv1/v2c
requests with a special community which you mapped to a context
engine ID (other than...) using the SNMP-COMMUNIY-MIB?

>
>
> I think I am trying to understand how this whole proxy forwarder works and
> how to configure it to send requests to the microsoft snmp agent and relay
> the traps back through the proxy to the management station.

Get a copy of "A practical guide to SNMPv3 and Network Management"
from D.Zeltersman. It is much easier to understand than the RFCs and
gives practical (!) examples.

Hope this helps.

Best regards,
Frank