Configuring Ingress QoS Policing based on Internal Priority

Internal priority is an intermediary priority value that maps DSCP values to CoS values. Netvisor ONE version 6.1.0 allows you to configure vFlows with internal priority as a filtering parameter. In effect, you can now perform traffic policing for any received traffic based on DSCP values. In earlier versions of Netvisor ONE, you needed to configure at least one vFlow per port per DSCP value or DSCP value range. However, with Netvisor ONE release 6.1.0, you need to configure only one vFlow per internal priority value.

The allowed range of internal priority values is between 0 and 7. For example, you can assign a maximum bandwidth limit of 100Mbps for packets with an internal priority of 1 by using the command:

CLI (network-admin@switch) > vflow-create name flow1 scope local internal-pri 1 bw-max 100M

Display the configuration by using the command:

CLI (network-admin@switch) > vflow-show

name:         flow1

scope:        local

type:         vflow

in-port:      

internal-pri: 1

bw-max:       100M

burst-size:   auto

precedence:   default

action:     

packet-res:

fwding-type:

enable:       enable

table-name:   System-L1-L4-Tun-1-0

To clear the internal priority field for a vFlow, use the command:

CLI (network-admin@switch) > vflow-create name flow1 internal-pri none

Note: 

• To achieve filtering of traffic based on the desired DSCP values, you must configure the internal priority value on the basis of the configured DSCP to CoS mapping. For more information, see the Configuring DSCP to CoS Mapping section of the Configuring and Using vFlows chapter.
• This feature does not support CoS values of 8 and 9 as these queues are used for internal control plane traffic.
• You can configure the internal-pri parameter in different hardware filter tables except System-VCAP-table-1-0 and VCAP-IPv6-table-1-0.