Support Center > Search Results > SecureKnowledge Details
'Peak' number of connections - discrepancy between the output of 'fw tab -t connections -s' command and the output of 'fw ctl pstat' command when CoreXL is enabled Technical Level
Symptoms
  • 'Peak' number of connections differs in the output of 'fw tab -t connections -s' command and in the output of 'fw ctl pstat' command when CoreXL is enabled.

    Example:

    [Expert@FW]# fw tab -t connections -s 
    HOST                  NAME                               ID #VALS #PEAK #SLINKS
    localhost             connections                      8158   220  3299     631
    [Expert@FW]#
    
    [Expert@FW]# fw ctl pstat 
    ...................
    Connections:
            14602990 total, 5918317 TCP, 8322438 UDP, 260968 ICMP,
            101267 other, 27495 anticipated, 9066 recovered, 201 concurrent,
            2814 peak concurrent
    ...................
    [Expert@FW]#
    
    [Expert@FW]# fw ctl multik stat
    -------------------------------------------
    ID | Active  | CPU    | Connections | Peak    
    ----------------------------------------------
     0 | Yes     | 1      |         108 |     1807
     1 | Yes     | 0      |         117 |     1492
    [Expert@FW]#
    
Cause

The correct value is shown in the output of the 'fw ctl pstat' command.

The '#PEAK' counter in the output of 'fw tab -t connections -s' command is a sum of peak connections of all CoreXL FW instances (as seen in the output of 'fw ctl multik stat' command).


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