Alcatel-Lucent 7450 Quality Of Service Manual page 299

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. This keyword is mutually exclusive with the redirection to a policer.
The policer keyword is optional. When specified, the egress packet will be redirected to the configured
policer. Optional parameters allow the user to control how the forwarded policed traffic exits the egress
port. By default, the policed forwarded traffic will use a queue in the egress port's policer-output-
queue queue group, alternatively a queue in an instance of a user configured queue group can be used
or a local SAP egress queue. This keyword is mutually exclusive with the hsmda-counter-override
keyword.
The no form of this command removes all reclassification actions from the IP flow reclassification
entry and also removes the entry from the evaluation list. An entry removed from the evaluation list
will not be matched to any packets egress a SAP associated with the SAP egress QoS policy.
Default Action specified by the default-fc.
Parameters fc fc-name — The fc reclassification action is optional. When specified, packets matching the IP
profile {in | out} — The profile reclassification action is optional. When specified, packets
in — The in parameter is mutually exclusive to the out parameter following the profile
out — The out parameter is mutually exclusive to the in parameter following the profile
Quality of Service Guide
flow reclassification entry will be explicitly reclassified to the forwarding class specified as
fc-name regardless of the ingress classification decision. 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 IP flow entry, the action command must be re-executed without
the fc reclassification action defined.
Values
fc: class[.sub-class]
Default none
matching the IP flow reclassification entry will be explicitly reclassified to either in-profile
or out-of-profile regardless of the ingress profiling decision. To remove the profile
reclassification action for the IP flow reclassification entry, the action command must be re-
executed without the profile reclassification action defined.
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.
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.
Service Egress and Ingress QoS Policies
class: be, l2, af, l1, h2, ef, h1, nc
sub-class: 29 characters max
299