Proxy forwarder question

[Ram Krishnaswamy]

Hi Frank,

Thanks for your response. I did go and buy the book that you recommended and
it has helped immensely in some ways. But I am still confused since there
are three tables to configure and hope you or somebody can help me out.

>From what I have read so far, seems that I should be able to send a snmpv3
request from a manager entity (10.10.13.78) to an agent entity (which has
the proxy forwarder and its ip address = 10.10.9.2) so that the request gets
forwarded as a SNMPv1 request to the target address 10.10.13.103.   If I
cannot do this, then what I have tried so far would not work. I understand
this although the documentation and book says that the message processing
subsystem should convert between versions. 

So I setup the table entries as given below. I initially set the
targetParamTableentry to support SNMPv1. But it did not work as I saw in
proxy_forwarder.cpp file. So I matched the versions and had it as SNMPv3.
The proxy forwarder sends it but times out. Obviously, since the
10.10.13.103 box talks only SNMPv1. 

What am I missing here or what have I done wrong? Thanks.

I have the following entries in the three tables:

snmpProxyTable
--------------

Instance: proxy 
snmpProxyName(IDX, IMP): not avaliable
snmpProxyType: read(1)
snmpProxyContextEngineID: dell4400
snmpProxyContextName: dellserv
snmpProxyTargetParamsIn: defaultV1Request
snmpProxySingleTargetOut: dellbox
snmpProxyMultipleTargetOut: 
snmpProxyStorageType: nonVolatile(3)
snmpProxyRowStatus: active(1)

snmpTargetParamsTable:
----------------------

Instance: defaultV1Request
snmpTargetParamsName(IDX, IMP): not available
snmpTargetParamsMPModel: 0
snmpTargetParamsSecurityModel: 1
snmpTargetParamsSecurityName: MD5DES
snmpTargetParamsSecurityLevel: noAuthNoPriv(1)
snmpTargetParamsStorageType: nonVolatile(3)
snmpTargetParamsRowStatus: active(1)

snmpTargetAddrTable:

Instance: dellbox
snmpTargetAddrName(IDX, IMP): not available
snmpTargetAddrTDomain: snmpV2.1.1 (UDP)
snmpTargetAddrTAddress: 0A.0A.0D.67.00.A1 translates to 10.10.13.103/161
snmpTargetAddrTimeout: 1500
snmpTargetAddrRetryCount: 3
snmpTargetAddrTagList: v1request
snmpTargetAddrParams: defaultV1Request
snmpTargetAddrStorageType: nonVolatile(3)
snmpTargetAddrRowStatus: active(1)


-----Original Message-----
From: Frank.Fock____t-online.de [mailto:Frank.Fock____t-online.de]
Sent: Thursday, February 22, 2001 2:59 PM
To: Ram Krishnaswamy
Cc: 'agentpp-dl____agentpp.com'
Subject: Re: Proxy forwarder question


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