2009/6/5 <a...@spatialsystems.org>:
> Debain Lenny Example:
> m...@serv:~$ snmpget -c public -v 1 192.168.1.201
> 1.3.6.1.4.1.2254.2.4.1.2.0
> Timeout: No Response from 192.168.1.201.
Please add the options '-d -r 0' and try again.
What do the raw packet dumps look like.
> What could possibly be the problem?
> Why does snmpget think that nothing is coming back?
Normally, if you get timeouts, this typically means that the
community string is wrong, or that the agent isn't listening
(as Michael suggests).
But if you are seeing packets coming back, that's unlikely
to be the cause here. My guess is that there's a bug in
the remote agent, and the response is not strictly valid.
If forced to guess further, I'd suggest setting the snmp.conf
directive "16bitIDs true"
(note snmp.conf, *not* snmpd.conf)
Dave
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
