[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On Wed, 2005-07-20 at 10:42 +0530, [EMAIL PROTECTED] wrote:
> Hi Dave,
>
> Thanks for your response.
> The command that I have run is
>
> snmpget -c public -v 2c <hostname> system.sysUpTime.0
OK - that's the problem then.
Your agent is listening on a non-standard port (116),
but you haven't informed the snmpget command of this.
So it's still trying to talk to the usual port (161).
You need to run
snmpget -c public -v 2c <hostname>:116 system.sysUpTime.0
exactly as Patrick suggested yesterday.
> and I executed this command on the same linux box where the agent is running.
So firewalls probably won't be a problem.
Dave
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
