Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
snmpwalk is a powerful tool, but it is a simple tool at the same time. You may be running up against this issue, taken from the man page for snmpwalk for the "-Cc" option
Do not check whether the returned OIDs are increasing. Some agents (LaserJets are an example) return OIDs out of order, but can complete the walk anyway. Other agents return OIDs that are out of order and can cause snmpwalk to loop indefinitely. By default, snmpwalk tries to detect this behavior and warns you when it hits an agent acting illegally. Use -Cc to turn off this check.
Other tools, especially graphical ones such as what you might be using on a PC, may be correcting that issue under the hood and continuing to display information past the point at which snmpwalk is stopping.
my problem was that I couldn't snmpwalk my custom application mib.
I could solve the problem. net-snmp uses 161 as default port. My application just accepts request from port 10020.
So I changed the command like this:
#snmpwalk -v 1 -c public -O e 10.10.10.74:10020 .1.3.6.1.4.1.33687.1.1.1.1.1.6
