On 22/05/07, Sandrine MONOT wrote:
> /usr/local/bin/snmpwalk -v 1 -c public localhost:7075
> .1.3.6.1.4.1.2390.1.3.1


> SNMPv2-SMI::enterprises.2390.1.3.1.9999.0 = INTEGER: 2
> SNMPv2-SMI::enterprises.2390.1.3.1.9999.0 = ""
> Error: OID not increasing: SNMPv2-SMI::enterprises.2390.1.3.1.9999.0
> >= SNMPv2-SMI::enterprises.2390.1.3.1.9999.0



> After start sun master agent with /etc/init.d/init.sma commands
> I request agent whith following commands
> /usr/local/bin/snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2390.1.3.1
>
> I obtain same answer ...


Which agent is responsible for this MIB object? The Net-SNMP
agent or the Sun one? I'm assuming it's the Sun agent.

If you remove the "proxy" line from the Net-SNMP config, does
it behave correctly?



> So I deduce that sun master agent and my agent net-snmp are working good ?
> You confirm me that ?


Well *something* is not working properly.
It's not clear whether this is the Sun or the Net-SNMP agent.


I note that you've kept the '-d' flag when starting the Net-SNMP agent,
so presumably you can see the packet dumps in your logs.
Try running

/usr/local/bin/snmpgetnext -v 1 -c public localhost:7075
enterprises.2390.1.3.1.9999.0


What is logged as a result of this command?
You should see four packets dumps - one coming in from the
"snmpgetnext" command, a second for forwarding this request
on to the Sun agent, followed by the response from the Sun
agent, and finally returning the result to snmpgetnext.

Please post these four packet dumps.

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders