Alcatel-Lucent 7950 Quality Of Service Manual page 199

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
Default
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>ingress>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:
•
•
Default
no profile-capped
profile-out-preserve
Syntax [no] profile-out-preserve
Context config>qos>sap-egress>policer
Description This command specifies whether to preserve the color of offered out-of-profile traffic at sap-egress policer
(profility of the packet can change based on egress CIR state).
When enabled, traffic determined as out-of-profile at ingress policer will be treated as out-of-profile at sap-
egress policer.
7950 XRS Quality of Service Guide
Percentage ranging from 0.00 to 100.00.
100.00
At egress, soft-in-profile packets (packets received from ingress as in-profile) are treated the same
as explicit in-profile (unless explicitly reclassified as out-of-profile) and have an initial policer state
of in-profile.
At both ingress and egress, any packet output from the policer with a non-conforming CIR state are
treated as out-of-profile (out-of-profile state is ignored for initial in-profile packets when profile
capped mode is not enabled)
Page 199