Alcatel-Lucent 7450 Quality Of Service Manual page 265

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 (profile 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.
rate
Syntax rate {max | kilobits-per-second} [cir {max | kilobits-per-second}]
no rate
Context config>qos>sap-ingress>policer
Description This command is used to configure the policer's metering and optional profiling rates. The metering
rate is used by the system to configure the policer's PIR leaky bucket's decrement rate while the
profiling rate configures the policer's CIR leaky bucket's decrement rate. The decrement function
empties the bucket while packets applied to the bucket attempt to fill it based on the each packets size.
If the bucket fills faster than how much is decremented per packet, the bucket's depth eventually
reaches it's exceed (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are
used to configure the policer's PIR and CIR thresholds.
If a packet arrives at the policer while the bucket's depth is less than the threshold associated with the
packet, the packet is considered to be conforming to the bucket's rate. If the bucket depth is equal to
or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket,
the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR
bucket rate. If the packet is violating the PIR, the packet is marked red and will be discarded. If the
packet is not red, it may be green or yellow based on the conforming or exceeding state from the CIR
bucket.
When a packet is red neither the PIR or CIR bucket depths are incremented by the packets size. When
the packet is yellow the PIR bucket is incremented by the packet size, but the CIR bucket is not. When
the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that
conforming packets impact the bucket depth while exceeding or violating packets do not.
Quality of Service Guide
• 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)
Service Egress and Ingress QoS Policies
265