Alcatel-Lucent 7950 Quality Of Service Manual page 233

entry will override all IP precedence or DSCP based reclassification rule actions when an explicit
reclassification action is defined for the entry.
It is also possible to redirect the egress packet to a configured policer. The forwarding class or profile can
also be optionally specified, but redirection to a policer is mutually exclusive with the hsmda-counter-
override keyword.
When an IP flow entry is first created, the entry will have no explicit behavior defined as the reclassification
actions to be performed. In show and info commands, the entry will display no action as the specified
reclassification action for the entry. When the entry is defined with no action, the entry will not be populated
in the IP flow reclassification list used to evaluate packets egressing a SAP with the SAP egress policy
defined. An IP flow reclassification entry is only added to the evaluation list when the action command for
the entry is executed either with explicit reclassification entries or without any actions defined. Specifying
action without any trailing reclassification actions allows packets matching the entry to exist the evaluation
list without matching entries lower in the list. Executing no action on an entry removes the entry from the
evaluation list and also removes any explicitly defined reclassification actions associated with the entry.
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.
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.
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 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.
7950 XRS Quality of Service Guide Page 233