RE: Configuring the net-snmp proxy with the same community string

Hi Dave ,
Thanks  for the input but I tried proxy directive with same community string
and it doesn't seems to 
Be working. Below is what my snmpd.conf looks like 

com2sec  testgroup2     default         testgroup2

group testgroup2        v1        testgroup2 
group testgroup2        v2c       testgroup2 
group testgroup2        usm       testgroup2

view mib2   	 included  .1.3.6.1.2.1                  fc

access testgroup2    ""          v1         noauth     exact    mib2    none
none
access testgroup2    ""          v2c        noauth     exact    mib2    none
none
access testgroup2    ""          usm        authNoPriv exact    mib2    none
none

proxy directive I am using is :

proxy -v 2c -c testgroup2  192.168.205.33  .1.3.6.1.4.1.562.3.21.6  

But when I do a getnext / get  the query times out. 
snmpgetnext -v 2c -c testgroup2 192.168.205.33 .1.3.6.1.4.1.562.3.21.6.1.1.1
Timeout: No Response from 192.168.205.33.

On the the debug port I get the following message 


vacm:checkSubtree: , excluded
vacm:checkSubtree: , excluded
vacm:checkSubtree: , excluded
vacm:checkSubtree: , excluded

results: request results (status = 0):
results:        SNMPv2-SMI::enterprises.562.3.21.6.1.1.1.1 = No more
variables left in this MIB View (It is past the end of the MIB tree)

If I use a separate context and separate community string for the remote
host I am succesfully able to do the query. My requirement is that with
community string "testgroup2" I should be able to query the remote host also
along with local host OIDs. Can you suggest something which I am missing in
my snmpd.conf file ? 

Thank you very much for your valuable time.


Thanks & Regards,
Rajendra Singh
ESN: 343-3426

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave Shield
Sent: Friday, November 09, 2007 4:27 AM
To: Rajendra, Singh
Cc: net-snmp-users.sourceforge.net
Subject: Re: Configuring the net-snmp proxy with the same community string

On 08/11/2007, Rajendra, Singh <[email protected]> wrote:
> With net-snmp 5.4.1 running on it. I have configured A as to proxy 
> some OIDs to B. .... I want to use the same community string for both A
and B.

> Linux Box A (community string test) should respond to OIDS till 
> .1.3.6.1 and for OIDS in subtree .1.3.6.1.4.1.562.3.21.6 A should 
> proxy the request to linux box B.

That's no problem - just use the "proxy" directive in A's snmpd.conf file.
That's the natural way of using this mechanism.



> See the documentation below
> If you want to have the same OID tree proxied to multiple devices.... 
> you need to use contexts.... [or] have a SNMPv1 community string map 
> to a context for proxying. You will need a unique community string per 
> proxied device.

You only need a unique community string per proxy if you are proxying the
*same* set of OIDs..    For example, if you wanted to query values in
the subtree
.1.3.6.1.4.1.562.3.21.6  from B *and* from A itself (and possibly from
another proxy C as well).
    When the main agent received a request for
.1.3.6.1.4.1.562.3.21.6.1.2.3, it would need some way of knowing which
system (A, B or C) to report the values from.  This is where the
context/community comes in - different contexts (or communities) can be used
to distinguish the three cases.



That's not the situation here.
If it's only B that will be handling values from .1.3.6.1.4.1.562.3.21.6,
then the main agent (A) knows where to send such requests, so doesn't
need a hint from the community string.   You don't need to use the context
mechanism at all.   Just use a plain "proxy" directive, and things should
work as expected.


Dave


-------------------------------------------------------------------------
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