Support Center > Search Results > SecureKnowledge Details
SNMP counters for "packets rate" / "throughput" show incorrect values - .1.3.6.1.4.1.2620.1.1.25.9 and .1.3.6.1.4.1.2620.1.1.25.16
Symptoms
  • The following SNMP counters on Security Gateway R77.10 and above always show "0" value for dropped packets:

    • .1.3.6.1.4.1.2620.1.1.25.9 (iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPolicyStat.fwDroppedBytesTotalRate)

    • .1.3.6.1.4.1.2620.1.1.25.16 (.iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPolicyStat.fwDroppedTotalRate)
  • SecureXL drops that appear in the output of 'fwaccel stats -d' command, are not counted in SNMP total dropped packets counters:

    • .1.3.6.1.4.1.2620.1.1.25.9 (iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPolicyStat.fwDroppedBytesTotalRate)

    • .1.3.6.1.4.1.2620.1.1.25.16 (.iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPolicyStat.fwDroppedTotalRate)
  • Examples from VSX:

    [Expert@HostName:0]# snmpwalk -n ctxname_vsid1 -v3 -l authNoPriv -u UserName -a MD5 -A Password localhost .1.3.6.1.4.1.2620.1.1.25.9
    SNMPv2-SMI::enterprises.2620.1.1.25.9.0 = STRING: "0"
    
    [Expert@HostName:0]# snmpwalk -n ctxname_vsid1 -v3 -l authNoPriv -u UserName -a MD5 -A Password localhost .1.3.6.1.4.1.2620.1.1.25.16
    SNMPv2-SMI::enterprises.2620.1.1.25.16.0 = STRING: "0"
    
Cause
  • Issue #1 (01583464): Incorrect definition of the involved SNMP counters - these counters hold total values not rate values.

  • Issue #2 (01583510): In R77.10 and above, the way these counters are working was changed.

  • Issue #3 (01584275): SecureXL drop statistics is not collected correctly for SNMP counters.

Solution
Note: To view this solution you need to Sign In .