Service SAP QoS Policy Command Reference
264 Quality of Service Guide
config>qos>sap-ingress>policer
Description The percent-rate command within the SAP ingress and egress QOS policy enables supports for a
policer’s PIR and CIR rate to be configured as a percentage of the immediate parent root policer/arbiter
rate or the FP capacity.
This enables the same QOS policy to be used on SAPs on different FPs without needing to use SAP
based policer overrides to modify a policer’s rate to get the same relative performance from the policer.
If the parent arbiter rate changes after the policer is created, the policer’s PIR and CIR rates will be
recalculated based on the defined percentage value.
The rate and percent-rate commands override one another. If the current rate for a policer is defined
using the percent-rate command and the rate command is executed, the percent-rate values are deleted.
In a similar fashion, the percent-rate command causes any rate command values to be deleted. A
policer’s rate may dynamically be changed back and forth from a percentage to an explicit rate at
anytime.
The no form of this command returns the queue to its default shaping rate and cir rate.
Parameters pir-percent — Specifies the policer’s PIR as a percentage of the immediate parent root policer/
arbiter rate or the FP capacity.
Values Percentage ranging from 0.01 to 100.00
Default 100.00
cir cir-percent — The cir keyword is optional and when defined the required cir-percent CIR
parameter expresses the policer’s CIR as a percentage of the immediate parent root policer/
arbiter rate or the FP capacity.
Values Percentage ranging from 0.00 to 100.00
Default 100.00
profile-capped
Syntax [no] profile-capped
Context config>qos>sap-ingress>policer
config>qos>sap-egress>policer
config>qos>queue-group-templates>ingress>queue-group
config>qos>queue-group-templates>egress>queue-group
Description Profile capped mode enforces an overall in-profile burst limit to the CIR bucket for ingress undefined,
ingress explicit in-profile, egress soft-in-profile, and egress explicit in-profile packets. The default
behavior when profile-capped mode is not enabled is to ignore the CIR output state when an explicit
in-profile packet is handled by an ingress or egress policer.
The profile-capped mode makes two changes:
To Next Page
Loading...
