Replacement of DSCP on Egress
The switch can be configured to change the DSCP in a packet before forwarding the packet. This is done with no impact on switch performance and can be configured as described in the following sections:
Replacement in ACL-Based Traffic Groups
If you are using ACL-based traffic groups, you can use the replace-dscp action modifier to replace the ingress DSCP value with the DSCP value of the egress QoS profile as listed in Default QoS Profile and 802.1p Priority Value Mapping to DiffServ Code Points. This action modifier functions for both IPv4 and IPv6 traffic.
NoteIf you are using ACL-based traffic groups, you must use ACL action modifiers to replace the DSCP. Traffic that meets any ACL match conditions is not subject to non-ACL-based DSCP priority replacement. For all platforms, we recommend that you use ACL-based traffic groups when configuring DSCP replacement.
Replacement in Non-ACL-Based Traffic Groups
For non-ACL-based traffic groups, you can enable or disable DSCP replacement on specific ingress ports. When DSCP replacement is enabled, the DSCP value used on egress is determined by either the QoS profile or the 802.1p priority value. Default QoS Profile and 802.1p Priority Value Mapping to DiffServ Code Points shows the default mappings of QoS profiles and 802.1p priority values to DSCPs.
|QoS Profile||802.1p Priority Value||DSCP|