Alcatel-Lucent 7950 Quality Of Service Manual page 336

Network IP Interface Forwarding Class-Based Redirection
Egress Marking of PW Packet Header
When the queue-group name the PW is redirected to exists and the redirection succeeds, the
marking of the packet's DEI/dot1.p/DSCP and the tunnel's DEI/dot1.p/DSCP/EXP is performed
according to the relevant mappings of the {FC, profile} in the egress context of the network QoS
policy applied to the PW. This is true if an instance of the queue-group exists on the egress port the
PW packet is forwarded to. If the packet's profile value changed due to egress child policer CIR
profiling, the new profile value is used to mark the packet's DEI/dot1.p and the tunnel's DEI/
dot1.p/EXP but the DSCP is not modified by the policer's operation.
When the redirection command succeeds but there is no instance of the queue-group on the egress
port, or when the redirection command fails due to an inexistent queue-group name, the marking
of the packet's DEI/dot1.p/DSCP and the tunnel's DEI/dot1.p/DSCP/EXP fields is performed
according to the relevant commands in the egress context of the network QoS policy applied to the
network IP interface the PW packet is forwarded to.
Egress Packet Re-Classification Based on IPv4/IPv6 Criteria
The user enables IP precedence or DSCP based egress re-classification by applying the following
command in the context of the network QoS policy applied to the egress context of a spoke-SDP.
config>qos>network>egress>prec ip-prec-value [fc fc-name] [profile {in | out}]
config>qos>network>egress>dscp dscp-name [fc fc-name] [profile {in | out}]
The IP precedence bits used to match against DSCP reclassification rules come from the Type of
Service (ToS) field within the IPv4 header or the Traffic Class field from the IPv6 header.
The IP DSCP bits used to match against DSCP reclassification rules come from the Type of
Service (ToS) field within the IPv4 header or the Traffic Class field from the IPv6 header.
If the packet does not have an IP header, DSCP or IP-precedence based matching is not performed.
Note that the IP precedence and DSCP based re-classification are only supported on a PW used in
an IES or VPRN spoke-interface. The CLI blocks the application of a network QoS policy with the
egress re-classification commands to a network IP interface or to a spoke-SDP part of L2 service.
Conversely, the CLI does not allow the user to add the egress re-classification commands to a
network QoS policy if it is being used by a network IP interface or a L2 spoke-SDP.
Page 336 7950 XRS Quality of Service Guide