Applying CoS Queue Mapping based on Re-Marked DSCP in vFlow


Currently, Netvisor One allows a vFlow to mark or re-mark matched packets with a DSCP value on egress. As a result, Netvisor One does not prioritize any of the traffic in terms of the egress port CoS queue selected for transmit. Another feature, Enabling DSCP to Priority and CoS Mappings introduces the ability to create DSCP QoS maps and apply to ports, but the maps apply to ingress packets. This feature introduces the ability prioritize traffic based on the remarked DSCP value in a vFlow.


Netvisor One creates named DSCP maps as independent objects, and applies the maps to ingress ports for prioritizing packets based on the DSCP markings.


In this feature, you can apply the same maps in a vFlow. QoS maps can be applied to ports, but not to Flow Processor entries corresponding to vFlows. This implementation does the prioritizes explicitly, since flows can be configured with CoSQ values. The implementation has the following features:


  • Verify the DSCP map named in the vFlow exists.
  • Determine the priority and CoS for the DSCP value assigned to the vFlow.
  • Apply this CoS value to the Flow Processor entry in hardware.
  • Reconfigure CoS in the flow when the vFlow DSCP setting changes.
  • Prevent deleting a DSCP map in use by a vFlow.
  • Update the CoS setting of vFlows using the DSCP map when the DSCP map priority settings are updated.


You can specify the name of a DSCP map in the vflow-create command:


dscp-map dscp-map name | none

Specify the DSCP map to apply on the flow.

Please reapply if map priorities are updated.