The remark policy configuration guidelines for the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C are the following:
The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C mark the dot1p configured in the marking policy only if the node adds one or two tags or if it replaces existing tags. The platforms do not modify the VLAN tag which represents customer payload; for example, the platforms do not mark the packets when forwarding traffic out of dot1q range SAP or a null SAP.
A limited number of unique remark policies are available to be shared among all the different types of remark policies. In other words, dot1p, dscp, dot1p-dscp, lsp-exp, dot1p-lsp-exp, dot1p-dscp-lsp-exp remark policy types share the available resources and scaling one type of remark policy reduces the amount policies allowed for other type of remark policy.
The user also has an option to preserve the dot1p values in the received packet. See the CLI description for the config service sap egress dot1p-inner and config service sap egress dot1p-outer commands in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Services Guide.
When marking is enabled without explicitly associating the remark policy, the default remark policy is used for marking packets.
Any remark policy that specifies MPLS lsp-exp values cannot be associated with access-uplink port. The association is blocked by the system.
MPLS packets sent out of a network IP interface configured on a network port or hybrid port can be marked with MPLS lsp-exp values and dot1p, DEI values if both are configured.
IP packets sent out of a network IP interface configured on a network port or hybrid port can be marked with IP DSCP values and dot1p, DEI values if both are configured.
The dot1p bits of the packets sent out of a network IP interface configured on a network port or hybrid port are always marked by default, even when remarking is disabled.