Policing of Virtual Channel (vChannel) [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:dpi:dpi_options:opt_shaping:shaping_multi [2024/10/04 12:56] – [For VLANs:] elena.krasnobryzhen:dpi:dpi_options:opt_shaping:shaping_multi [2025/08/19 15:43] (current) – [Policing Configuration] elena.krasnobryzh
Line 84: Line 84:
     * ''ok'' — the number of successful executions       * ''ok'' — the number of successful executions  
     * ''ierr'' — the number of errors       * ''ierr'' — the number of errors  
 +    * ''isset'' — the number of commands that were issued but not executed due to missing settings or restrictions  
 +    * ''noset'' — the number of commands that were not executed for other reasons  
   - Checking the applied service plan on vchannel: <code bash>fdpi_ctrl list --policing  --vchannel 2 --outformat json     - Checking the applied service plan on vchannel: <code bash>fdpi_ctrl list --policing  --vchannel 2 --outformat json  
 {   {  
Line 131: Line 133:
  
 where vchannel1.cfg - file with policing definition (same as for the general channel,virtual channels and subscriber rate plans) where vchannel1.cfg - file with policing definition (same as for the general channel,virtual channels and subscriber rate plans)
 +
 +<note warning>Using virtual channel (vChannel) policing entails additional internal locks, which reduces system performance to 40G (when using tbf) and to 20G (when using htb) of total traffic on the vChannel, regardless of the number of cores.</note>
  
 **Example of the configuration file:** **Example of the configuration file:**