Moving a priority from one traffic group to another
Typically, when modifying a traffic template, priorities are reassigned to different queues. When moving a priority from one traffic group to another, you must first delete that priority from the traffic group it is currently mapped to (no map-traffic-group
<queue-num> priority
<priority>
and then add it the desired traffic group.
Before changing the traffic groups’ priority mappings from the defaults, it is important to examine the current policies that act on 802.1p priorities to ensure that the policies best serve the behavior desired on the network, including DSCP, VLAN, interface, or protocol rules.
Removing priorities from a traffic group
switch(cfg-tcgt-example)# no map-traffic-group 2 priority 0
After removing the priority from the currently mapped queue, the template becomes invalid because priority 0 is no longer mapped to any queue.
Mapping the priority to a new queue results in a valid traffic template again.
Invalid traffic template because a priority is unmapped
switch(cfg-tcgt-example)# show qos traffic-template example TRAFFIC-TEMPLATE: example Status : Invalid Queue-no Priorities Name -------- ------------- -------------------- 1 1,2 background-tcg 2 3 best-effort-tcg 3 4,5 controlled-load-tcg 4 6,7 control-tcg
Valid traffic template with remapped queue
switch(cfg-tcgt-example)# map-traffic-group 1 priority 0 switch(cfg-tcgt-example)# show qos traffic-template example Template Name: example Status : Valid Queue Priorities Name -------- ------------- -------------------- 1 1,2 background-tcg 2 3,0 best-effort-tcg 3 4,5 controlled-load-tcg 4 6,7 control-tcg
After modifying a traffic template, you must apply it to the switch to activate the new mapping. See Applying a traffic template.