Cfhp Child Policer Definition And Creation - Alcatel-Lucent 7950 Quality Of Service Manual

CFHP Child Policer Definition and Creation

Policers are created within the context of SAP ingress (sap-ingress) and SAP egress (sap-egress)
QoS policies. Policer creation in a QoS policy is defined similar to SAP based queues. A policer is
identified using a policer ID. Queues and policers have different ID spaces (both a policer and
queue may be defined with ID 1).
The only create time parameter currently available is the unique policer ID within the policy.
Policers do not have a scheduling mode (expedite or best-effort), they also do not need to be
placed in profile-mode in order to accept traffic from profile in or profile out forwarding classes or
sub classes.
All policers within a SAP ingress or egress QoS policy must be explicitly created. No policers are
created by default. After a policer is created, forwarding classes or sub-classes may be mapped to
the policer within the policy. For ingress, each of the individual forwarding types (unicast,
multicast, broadcast and unknown) may be selectively mapped to a policer, policy created queue
or to an ingress port queue group queue. At egress, forwarding classes are not divided into
forwarding types, so all packets matched to the forwarding class may be mapped to either a
policer, policy created queue or egress port queue group queue.
Similar to queues, a policer is not created on the SAPs where the policy is applied until at least one
forwarding class is mapped to the policer. When the last forwarding class is unmapped from the
policer, all the instances of the policer on the SAPs to which the policy is applied are removed.
7950 XRS Quality of Service Guide
Explicit Arbiter Rate Limits
Page 579