Jobin Jose Sebastin wrote:
> Actually my intension is to forward the requests comes for the part of
> my mib tree to a remote agent ( say IPADDRESS 192.168.157.41 with
> sysName : remote agent).
>
> My configuratin file /etc/snmp/snmpd.conf is as follows.
>
[snip]
> proxy -v 1 -c public 192.168.157.41 .1.3.6.1.2.1.1.5
>
> ----------------------------------------------------------------------
>
> ie whenever any SNMPv1 request is coming to my agent ( running in the
> machine with IPADDRESS 192.168.157.222
> with say sysName :my agent),it should forward (in this case i am
> requesting for the sysName of the device )
> the request to the remote system with IPADDRESS 192.168.157.41 and
> should give the sysName of that device.
>
Yes - given that snmpd.conf file, I would expect this to work as expected.
You don't say explicitly, but I presume that you're actually seeing the
sysName
of the local device ("my agent") - correct?
The one possible cause that springs to mind is that "more specific"
registrations
take precedence over more general ones. So a local registration of
.1.3.6.1.2.1.1.5.0
would override the proxy registration of .1.3.6.1.2.1.1.5
Try dumping the contents of the module registry (either by walking
NET-SNMP-AGENT::nsModuleTable
or by sending the signal USR1 to the agent), and look for mention of
.1.3.6.1.2.1.1.5
What can you see?
What happens if you run the local agent using '-I-system_mib' (to
suppress the
registration of the system group altogether).
What version of the code are you using?
Dave
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
