Dscp Marking Cpu Generated Traffic; Table 20: Dscp/Fc Marking - Alcatel-Lucent 7210 SAS E OS Quality Of Service Manual

Overview

DSCP Marking CPU Generated Traffic

Specific DSCP, forwarding class, and Dot1P parameters can be specified to be used by every
protocol packet generated by the node. This enables prioritization or de-prioritization of every
protocol (as required). The markings effect a change in behavior on ingress when queuing. For
example, if OSPF is not enabled, then traffic can be de-prioritized to best effort (be) DSCP. This
change de-prioritizes OSPF traffic to the CPU complex.
DSCP marking for internally generated control and management traffic by marking the DSCP
value should be used for the given application. This can be configured per routing instance. For
example, OSPF packets can carry a different DSCP marking for the base instance and then for a
VPRN service. IS-IS and ARP traffic is not an IP-generated traffic type and is not DSCP
configurable, but they are Dot1p configurable.
When an application is configured to use a specified DSCP value then the MPLS EXP, Dot1P bits
will be marked in accordance with the network or access egress policy as it applies to the logical
interface the packet will be egressing.
The DSCP value can be set per application. This setting will be forwarded to the egress IOM. The
egress IOM does not alter the coded DSCP value and marks the LSP-EXP and IEEE 802.1p
(Dot1P) bits according to the appropriate network or access QoS policy.
Sgt-qos is supported in the base router, VPRN and management contexts.

Table 20: DSCP/FC Marking

ARP
Telnet
TFTP
FTP
SSH (SCP)
SNMP (get, set, etc.)
SNMP trap/log
syslog
ICMP ping
Page 58
Protocol IPv4
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
DSCP
IPv6
Marking
Yes Yes
Yes
Yes Yes
Yes Yes
Yes Yes
Yes Yes
Yes Yes
7210 SAS-E OS Quality of Service Guide
Dot1P Default
Marking FC
Yes NC
Yes AF
Yes AF
AF
Yes AF
Yes AF
Yes AF
Yes AF
Yes AF