Module: check_mk
Branch: master
Commit: 97a6e06fea257f668ebe089e74ba498ae3e977dc
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=97a6e06fea257f…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Sun Feb 27 14:09:38 2011 +0100
Updated bug entries
---
.bugs/161 | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/.bugs/161 b/.bugs/161
new file mode 100644
index 0000000..4a16a46
--- /dev/null
+++ b/.bugs/161
@@ -0,0 +1,18 @@
+Title: Add -Cc to snmpwalk options
+Component: core
+Benefit: 1
+State: open
+Cost: 1
+Date: 2011-02-27 14:08:10
+Class: feature
+
+This avoids problem on some devices. Might other introduce new ones.
+So I'm not sure what to do here. From the manpage of snmpwalk:
+
+-Cc 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.
+