Qos For Self-Generated (Cpu) Traffic On Network Interfaces - Alcatel-Lucent 7450 Quality Of Service Manual

Tunnel Termination QoS Override Operation
Tunnel termination QoS override only applies to IP routing decisions once the tunnel
encapsulation is removed. Non-IP routed packets within a terminating tunnel are ignored by
the override and are forwarded as described in the
When tunnel termination QoS override is enabled, the ToS field within the routed IP header
is evaluated against the IP ToS precedence and DSCP entries in the applied network QoS
policy on the ingress IP interface. If an explicit match entry is not found, the default QoS
mapping is used. Any dot1p and MPLS LSP EXP bits within the packet are ignored. If the
packet was IP GRE tunneled to the node, the tunnel IP header ToS field is ignored as well.
Any tunnel received on the ingress IP interface that traverses the node (the node is not the
ultimate hop for the tunnel) is not affected by the QoS override mechanism and is forwarded
as described in
Enabling and Disabling Tunnel Termination QoS Override
Tunnel termination QoS override is enabled and disabled within the network QoS policy
under the ingress node. The default condition within the policy is not to override tunnel QoS
for IP routed packets.

QoS for Self-Generated (CPU) Traffic on Network Interfaces

Differentiated services code point (DSCP), forwarding class (FC), and IEEE 802.1p values
can be specified to be used by every protocol packet generated by the node. This enables
prioritization or deprioritization 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 deprioritized to best effort (BE) DSCP. This change deprioritizes OSPF traffic to the CPU
complex.
DSCP marking for internally generated control and management traffic 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. ARP, IS-IS, and PPPoE are not IP protocols, so only 802.1p values can be
configured.
The DSCP value can be set per application. When an application is configured to use a
specified DSCP value, the 802.1p and MPLS EXP bits will be marked in accordance with the
network (default 802.1p value of 7) or access (default 802.1p value of 0) egress policy as it
applies to the logical interface the packet will be egressing.
Quality of Service Guide
Normal QoS Operation
Normal QoS Operation
section.
Network QoS Policies
section.
81