Alcatel-Lucent 7450 Quality Of Service Manual page 874

Class Fair Hierarchical Policing (CFHP) Policy Command Reference
For each packet, the bucket is first decremented by the correct amount based on the decrement rate to
derive the current bucket depth. The current depth is then compared to one of two discard thresholds
associated with the packet. The first discard threshold (discard-unfair) is applied if the FIR (Fair
Information Rate) leaky bucket in the packet's child policer is in the confirming state. The second
discard threshold (discard-all) is applied if the child policer's FIR leaky bucket is in the exceed state.
Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR
bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular
packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state
for the packet.
If the result is "conform," the bucket depth is increased by the size of the packet (plus or minus the per-
packet-offset setting in the child policer) and the packet is not discarded by the parent policer. If the
result is "violate," the bucket depth is not increased and the packet is discarded by the parent policer.
When the parent policer discards a packet, any bucket depth increases (PIR, CIR and FIR) in the parent
policer caused by the packet are canceled. This prevents packets that are discarded by the parent policer
from consuming the child policers PIR, CIR and FIR bandwidth.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile
where the policy is applied.
Default max
Parameters
kilobits-per-second — Defining a kilobits-per-second value is mutually exclusive with the max
max — The max parameter is mutually exclusive with defining a kilobits-per-second value.
no max-rate — The no max-rate command returns the policer-control-policy's parent policer
profile-perferred
Syntax profile-preferred
no profile-preferred
Context config>qos>policer-control-policy>root
Description
The profile-preferred option ensures that the root policer provides a preference to consume its PIR
bucket tokens at a given priority level to packets that have their profile state set to in-profile by the
output of the child policer CIR bucket.
Default
no profile-preferred
876
parameter. The kilobits-per-second value must be defined as an integer that represents the
number of kilobytes that the parent policer will be decremented per second. The actual
decrement is performed per packet based on the time that has elapsed since the last packet
associated with the parent policer.
Values
max or 1 to 2000000000
When max is specified, the parent policer does not enforce a maximum rate on the aggregate
throughput of the child policers. This is the default setting when the policer-control-policy
is first created and is the value that the parent policer returns to when no max-rate is executed.
In order for the parent policer to be effective, a kilobits-per-second value should be specified.
maximum rate to max.
Quality of Service Guide