Class Fair Hierarchical Policing (CFHP)
Quality of Service Guide 871
The net result is that explicit in-profile packets stay blue up to the high CBS threshold,
undefined profile packets would stay blue up to the low CBS threshold (1x CBS) and explicit
out-of-profile packets would always be orange due to a 0 CBS threshold. Orange packets
would be discarded by the parent policer within the child policer’s priority level before the
blue packets, preferring blue packets over orange once the discard-orange threshold is
crossed.
The following is the CLI for the new option. The same option applies to overrides applied to
the instances of a policer control policy under a SAP or subscriber or multi-service site
context.
config qos
policer-control-policy policy-name [create]
no policer-control-policy policy-name
description “description-string”
no description
root
max-rate {kilobits-per-second | max}
no max-rate
[no] profile-preferred
priority-mbs-thresholds
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
priority level
mbs-contribution size [bytes | kilobytes] [fixed]
no mbs-contribution
The profile-preferred option provides us a way to configure a specific FIR (since it uses the
CIR as FIR). In the direct-parented case (no intermediate arbiters present at all) the child
policers do not need to have their offered rate polled as each policer will always have PIR
equal to the min (child PIR, root PIR) and the FIR and CIR are fixed and equal. The child
parenting weights are thus not used. This impacts the show commands, for example offered
rate information will not be available. The output of some show commands (show qos
policer-hierarchy ... detail) should be adjusted for profile-preferred configurations.
If an intermediate arbiter is present, then polling is offered at different rates since the child
policer PIRs will be set based on this information so as to share the intermediate arbiter PIR
in proportional to their parenting weight to the intermediate arbiter.
To Next Page
Loading...
