Modifying Internal Priority at Ingress
After the packet priority is recognized as PCP, DSCP or EXP values, priority queue and drop precedence will be determined by one of the following methods:
• Global ingress mapping profiles are available for modification to configure non-default values on a Qumran device as explained in
Chapter 10, Configuring QoS. Following are the global ingress profiles affecting priority queues and drop precedence configuration:
qos profile cos-to-queue default – Configuration in this profile allows modifying default mapping of PCP to priority queue globally.
qos profile dscp-to-queue default – Configuration in this profile allows modifying default mapping of DSCP to priority queue and drop precedence globally.
qos profile exp-to-queue default – Configuration in this profile allows modifying default mapping of EXP to priority queue and drop precedence globally.
• User-defined ingress decode mapping profiles can be created and bound to port to override the global configuration:
qos profile cos-to-queue NAME – Configuration in this profile allows creating user-defined mapping of PCP to priority queue and can be bound to port to take effect.
qos profile dscp-to-queue NAME – Configuration in this profile allows creating user-defined mapping of DSCP to priority queue and drop precedence and can be bound to port to affect.
• User-defined PCP to TC profile map can be bound to VPLS instance or per-VLAN-based attachment circuit and this mapping will override the profiles mapping bound to port or the global mapping profile.
• User-defined PCP to TC profile map can be bound to VPWS VLAN based attachment circuits and this mapping will override the profile mapping bound to port or the global mapping profile.
• User-defined PCP to TC profile map can be bound to registration entries for provider edge ports and this mapping will override the profile mapping bound to port or the global mapping profile.
• QoS policy-maps can be configured as explained in
Chapter 2, Configuring a QoS Policy-map with set queue action and bound to an ingress port will override the priority queue configuration for the traffic that matches the policy-map configuration. Policy-map configured with
policer action resulting in color marking will override the drop precedence on the traffic as per configuration.
• Internal priority for untagged traffic received on switch ports will be set to zero by default.
• Untagged traffic can be assigned with a non-default priority queue with port level configuration:
qos untagged-priority <0-7> – This configuration assigns priority queue for untagged traffic received on the configured switch port.