A QoS traffic class-to-CoS mutation map can be configured to create a priority mapping table using a traffic-class-cos map. The traffic class-to-CoS map is then applied to an egress interface to effect the priority re-mapping.
If a QoS traffic class-to-CoS mutation map is not defined, the default traffic class-to-CoS map is used, which is a one-to-one map for each priority.
Global configuration mode
A traffic class can be mapped to the outgoing PCP value when a packet egresses the switch. You can create a priority mapping table using a traffic class-to-CoS map. This traffic class-to-CoS map can then be applied to an egress interface to effect the priority re-mapping. This feature only maps the internal traffic class to outgoing priority.
Enter no qos map traffic-class-cos name command to delete the named QoS traffic class-to-CoS mutation map.
A QoS map can only be deleted if it is not bound to an interface.
This command is not available on the SLX 9740 and Extreme 8820 devices.
SLX 9150, SLX 9250, Extreme 8520, and Extreme 8720
To create and apply a QoS traffic class-to-CoS mutation map use the following command:
device# configure terminal device(config)# qos map traffic-class-cos CoSMap device(traffic-class-cos-CoSMap)# map traffic-class 3 drop-precedence 1 to cos 2 device(traffic-class-cos-CoSMap)# map traffic-class 4 drop-precedence 1 to cos 3 device(traffic-class-cos-CoSMap)# map traffic-class 5 drop-precedence 2 to cos 4 device(conf-if-eth-1/4)# qos traffic-class-cos tcCos1
To delete a QoS traffic class-to-CoS mutation map that is bound to an interface follow this example.
device# configure terminal device(config)# interface ethernet 1/4 device(conf-if-eth-1/4)# no qos traffic-class-cos CoSMap device(conf-if-eth-1/4)# exit device(config)# no qos map traffic-class-cos CoSMap