Priority Analyzer Shows Imprecise QoS Priority for Traffic 

The Problem 

The Priority Analyzer in the Cato Management Application (NetworkSites > {site name} > Site Monitoring > Priority Analyzer) shows traffic measurements that donmatch the configured network policyFor example, traffic that is assigned with QoS priority P30 in the Bandwidth Management window, appears in the Priority Analyzer as priority P10. 

The Reason 

Cato evaluates the network profile per network flow and assigns the priority after the application finalization. The first packets are before the flow is identified and are assigned with the default priority. This priority is the highest QoS priority that is used in your network rulebase and is used when showing traffic in the Priority Analyzer window. For example, if the highest priority used by a rule is P10, then the unfinalized flows are assigned with priority P10. Only after Cato inspects and determine the application, the flow is assigned with the configured priority based on your BW Management profiles in the rulebase.  


  • Unfinalized flows remain with QoS priority P10 
  • Blocked flows are assigned QoS priority P255 
  • The amount of the unfinalized traffic is minimal 
  • Lower profiles in the Bandwidth Management window (Network > Bandwidth Management) that aren't assigned to a network rule are ignored

Was this article helpful?

0 out of 0 found this helpful


Add your comment