Alcatel-Lucent 7950 Quality Of Service Manual page 185

field within the IPv4 header or the Traffic Class field from the IPv6 header. If the packet does not have an IP
header, dscp based matching is not performed.
The reclassification actions from a dscp reclassification rule may be overridden by an IP flow match event.
The fc keyword is optional. When specified, the egress classification rule will overwrite the forwarding
class derived from ingress. The new forwarding class is used for egress remarking and queue mapping
decisions. If an ip-criteria match occurs after the DSCP match, the new forwarding class may be overridden
by the higher priority match actions. If the higher priority match actions do not specify a new fc, the fc from
the dscp match will be used.
The profile keyword is optional. When specified, the egress classification rule will overwrite the profile of
the packet derived from ingress. The new profile value is used for egress remarking and queue congestion
behavior. If an ip-criteria match occurs after the DSCP match, the new profile may be overridden by the
higher priority match actions. If the higher priority match actions do not specify a new profile, the profile
from the DSCP match will be used.
The hsmda-counter-override keyword is optional. When specified, and the egress SAP is created on an
HSMDA, the egress classification rule will override the default queue accounting function for the packet.
By default, the HSMDA uses each queues default queue counters for packets mapped to the queue. The
hsmda-counter-override keyword is used to map the packet to an explicit exception counter. One of eight
counters may be used. When the packet is mapped to an exception counter, the packet will not increment the
queues discard or forwarding counters, instead the exception discard and forwarding counters will be used.
The DSCP-based counter override decision may be overwritten by an ip-criteria reclassification rule match
if the higher priority classification rule has an hsmda-counter-override action defined.
The no form of the command removes the specified the dscp-names from the reclassification rule in the SAP
egress QoS policy. As dscp-names are removed, the system repacks the lists of dscp-names with the same
parameters (up to 8 per list). As the no command does not have any additional parameters, it is possible to
remove multiple dscp-names from multiple DSCP statements having different parameters with one
command. If a dscp-name specified in a no command does not exist in any DSCP statement then the
command is aborted at that point with an error message displayed. Any dscp-names in the list before the
failed entry will be processed as normal but the processing will stop at the failed entry so that the remainder
of the list is not processed.
7950 XRS Quality of Service Guide Page 185