Enhancement NMS-7123: Expose SNMP4J 2.x noGetBulk and allowSnmpV2cInV…

…1 capabilities

core/snmp/impl-snmp4j/src/main/java/org/opennms/netmgt/snmp/snmp4j/Snmp4JStrategy.java

@@ -111,6 +111,9 @@ private static void initialize() {
         	SNMP4JSettings.setForwardRuntimeExceptions(true);
         }
 
+        SNMP4JSettings.setAllowSNMPv2InV1(Boolean.getBoolean("org.opennms.snmp.snmp4j.allowSNMPv2InV1"));
+        SNMP4JSettings.setAllowSNMPv2InV1(Boolean.getBoolean("org.opennms.snmp.snmp4j.noGetBulk"));
+
         s_initialized = true;
     }
 

opennms-base-assembly/src/main/filtered/etc/opennms.properties

@@ -83,6 +83,20 @@ snmp4j.LogFactory=org.snmp4j.log.Log4jLogFactory
 # to disable this workaround, comment out the following line.
 org.opennms.snmp.workarounds.allow64BitIpAddress=true
 
+# Some SNMP agents claim to support SNMPv2c, but either completely fail to
+# respond to GET-BULK requests or return bad responses to them under some
+# conditions. To disable the use of GET-BULK PDUs globally in the SNMP4J
+# strategy, set this property to true. This change will adversely affect the
+# efficiency of SNMP data collection from agents that properly support
+# GET-BULK.
+org.opennms.snmp.snmp4j.noGetBulk=false
+
+# Some buggy SNMP agents fail to exclude Counter64 objects from view when
+# responding to SNMPv1 requests (as mandated by RFC3584 § 4.2.2.1). To relax
+# handling of v1 responses to permit Counter64 varbinds rather than discarding
+# them as ill-formed (per the same RFC), set this property to true.
+org.opennms.snmp.snmp4j.allowSNMPv2InV1=false
+
 # ###### DATA COLLECTION ######
 # On very large systems the OpenNMS default mechanism of storing one data
 # source per RRD file can be very I/O Intensive.  Many I/O subsystems fail