Alcatel-Lucent 7750 Configuration Manual page 567

fixed — The optional fixed keyword is used to force the inclusion of the defined mbs-contribution value
(or an override value defined on the SAP or sla-profile) in the parent policer's discard threshold calculations.
If the mbs-contribution command is executed without the fixed keyword, the fixed calculation behavior for
the priority level is removed.
Default no mbs-contribution
The no mbs-contribution command returns the policy's priority level's MBS contribution to the default
value. When changed, the thresholds for the priority level and all higher priority levels for all instances of
the parent policer will be recalculated.
policer-override
Syntax [no] policer-override
Context config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description
This command, within the SAP ingress or egress contexts, is used to create a CLI node for specific overrides
to one or more policers created on the SAP through the sap-ingress or sap-egress QoS policies.
The no form of the command is used to remove any existing policer overrides.
Default no policer-overrides
policer
Syntax policer policer-id [create]
no policer policer-id
Context config>card>fp>ingress>access>qgrp>policer-over
config>card>fp>ingress>network>qgrp>policer-over
Description This command is used in the sap-ingress and sap-egress QoS policies to create, modify or delete a policer.
Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue
ID space, allowing both a queue and a policer to share the same ID. The sap-ingress policy may have up to
32 policers (numbered 1 through 32) may be defined while the sap-egress QoS policy supports a maximum
of 8 (numbered 1 through 8). While a policer may be defined within a QoS policy, it is not actually created
on SAPs or subscribers associated with the policy until a forwarding class is mapped to the policer's ID.
All policers must be created within the QoS policies. A default policer is not created when a sap-ingress or
sap-egress QoS policy is created.
Once a policer is created, the policer's metering rate and profiling rates may be defined as well as the
policer's maximum and committed burst sizes (MBS and CBS respectively). Unlike queues which have ded-
icated counters, policers allow various stat-mode settings that define the counters that will be associated
with the policer. Another supported feature—packet-byte-offset—provides a policer with the ability to mod-
ify the size of each packet based on a defined number of bytes.
Once a policer is created, it cannot be deleted from the QoS policy unless any forwarding classes that are
mapped to the policer are first moved to other policers or queues.
7750 SR Interface Configuration Guide
Interface Configuration
Page 567