Support Center > Search Results > SecureKnowledge Details
SNMP OID vsxCountersConnTableLimit returns wrong value on VSX if IPv6 is enabled
Symptoms

  • SNMP OID vsxCountersConnTableLimit (.1.3.6.1.4.1.2620.1.16.23.1.1.4) returns wrong value on VSX if IPv6 is enabled - the returned value is two times larger than the real limit of Connections Table as shown in the output of "fw ctl pstat" command and "fw6 ctl pstat" command.

    Example:

    • [Expert@VSX_HostName:0]# snmpwalk -v 3 -l authPriv -u MyUserName -A MyPassword localhost .1.3.6.1.4.1.2620.1.16.23.1.1.4 
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.4.1.0 = INTEGER: 31800

    • [Expert@VSX_HostName:0]# fw ctl pstat | head -n 10

Context is set to Virtual Device MyVirtualSystem (ID 0).

Virtual System Capacity Summary:
  Physical memory used:  12% (2903 MB out of 24008 MB) - below watermark
  Kernel   memory used:   5% (1225 MB out of 23912 MB) - below watermark
  Virtual  memory used:  19% (787 MB out of 4014 MB) - below watermark
     Used: 243 MB by FW, 544 MB by zeco
  Concurrent Connections: 0% (117 out of 15900) - below watermark
  Aggressive Aging is not active
Cause

The value is incorrectly calculated twice for the same table (for IPv4 and for IPv6).


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