DSCP, FC, and IEEE 802.1p values can be specified for use by protocol packets generated by the node. This enables prioritization or deprioritization of supported protocols.
DSCP marking for internally-generated control and management traffic should be used for a specified application. The DSCP marking can be configured per routing instance; for example, OSPF packets can carry a different DSCP marking for the base instance than for a VPRN service. ARP and IS-IS are not IP protocols, so only 802.1p values can be configured.
The DSCP value can also be set per application. When an application is configured to use a specified DSCP value and FC, the 802.1p and MPLS EXP bits are marked in accordance with the network (default 802.1p value of 7) or access (default 802.1p value of 0) egress policy, because it applies to the logical interface the packet is egressing.
Configuring self-generated QoS traffic is supported in the base router and VPRN service contexts.
Table: DSCP and dot1p Marking for 7210 SAS-K 2F1C2T and Table: DSCP and dot1p marking for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C list the default values for self-generated traffic on network interfaces.
ICMP echo requests (type 8) and ICMPv6 echo requests (type 128) initiated from the router use the DSCP value set using the ping command TOS value.
Configurable values for BFD are not supported.
On access SAP egress and access port egress, when remarking is not enabled, the dot1p value for all IP packets generated by the node is set to zero. To enable dot1p marking, remarking must be enabled.