Alcatel-Lucent 7950 Quality Of Service Manual page 212

Extensible routing system
Table of Contents

Advertisement

Service Ingress QoS Policy Commands
reclassification actions. If an egress packet on the SAP matches the specified IP precedence value, the
forwarding class, profile or HSMDA egress queue accounting behavior may be overridden. By default, the
forwarding class and profile of the packet is derived from ingress classification and profiling functions.
The IP precedent bits used to match against prec reclassification rules come from the Type of Service (ToS)
field within the IPv4 header. If the packet does not have an IPv4 header, prec based matching is not
performed.
The reclassification actions from a prec reclassification rule may be overridden by a DHCP or IP flow
matching events.
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 a dhcp or ip-criteria match occurs after the prec 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 prec 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 a dhcp or ip-criteria match occurs after the prec 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 prec match will be used.
The no form of the command removes the reclassification rule from the SAP egress QoS policy.
Parameters
fc fc-name — This keyword is optional. When specified, packets matching the IP precedence value will be
explicitly reclassified to the forwarding class specified as fc-name regardless of the ingress
classification decision. The explicit forwarding class reclassification may be overwritten by a higher
priority dscp or ip-criteria reclassification match. The fc-name defined must be one of the eight
forwarding classes supported by the system. To remove the forwarding class reclassification action for
the specified prec-value, the prec command must be re-executed without the fc reclassification action
defined.
Values
Default
profile {in | out} — This keyword is optional. When specified, packets matching the IP precedence value
will be explicitly reclassified to either in-profile or out-of-profile regardless of the ingress profiling
decision. The explicit profile reclassification may be overwritten by a higher priority dscp or ip-criteria
reclassification match. To remove the profile reclassification action for the specified prec-value, the
prec command must be re-executed without the profile reclassification action defined.
in — The in parameter is mutually excusive to the out parameter following the profile reclassification
action keyword. Either in or out must be specified when the profile keyword is present. When in is
specified, any packets matching the reclassification rule will be treated as in-profile by the egress
forwarding plane. This value may be overwritten by an explicit profile action in a higher priority dscp
or ip-criteria reclassification match.
out — The out parameter is mutually excusive to the in parameter following the profile reclassification
action keyword. Either in or out must be specified when the profile keyword is present. When out is
specified, any packets matching the reclassification rule will be treated as out-of-profile by the egress
forwarding plane. This value may be overwritten by an explicit profile action in a higher priority dscp
or ip-criteria reclassification match.
Page 212
be, l1, af, l2, h1, ef, h2 or nc
None
7950 XRS Quality of Service Guide

Advertisement

Table of Contents
loading

Table of Contents