Support Center > Search Results > SecureKnowledge Details
CPView history shows large number of pps on the interfaces after "cpstop"
Symptoms
  • After running cpstop and cpstart commands, CPView utility's history shows a wrongly large number of pps on the interfaces.

    Example:
    Network > Interfaces > Traffic
    lo pps 6801
    eth0 pps 32,681
    eth1 pps 23,291
    instead of
    ls pps=0
    eth0 pps=1
    eth1 pps=1
Cause

After cpviewd daemon is restarted, the previous state of pps is not saved and CPView begins from the current TX/RX values from interface causing wrong peak pps indication.


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