Egress Explicit Profile Reclassification - Alcatel-Lucent 7950 Quality Of Service Manual

Extensible routing system
Table of Contents

Advertisement

Egress Explicit Profile Reclassification

An egress profile reclassification overrides the ingress derived profile of a packet and may set it to
either 'hard-in-profile' or 'hard-out-of-profile'. A packet that has not been reclassified at egress
retains its 'soft-in-profile' or 'soft-out-of-profile' status.
Egress in-profile (including 'soft-in-profile' and 'hard-in-profile') packets use the child policer's
high 'threshold-be' value within the child policer's PIR bucket while 'soft-out-of-profile' and
'hard-out-of-profile' packets use the child policer's low 'threshold-be' value.
Preserving Out of Profile State at Egress Policer
Traffic sent through an egress policer with a non zero CIR will be reprofiled by default based on
the CIR threshold of the egress policer. To accommodate designs where traffic is set to be out of
profile at ingress, and the out of profile state is required to be maintained by an egress policer, the
parameter profile-out-preserve can be configured under the egress policer. Explicit egress
reclassification to the profile takes precedence over the profile-out-preserve operation.
Egress Policer CIR Packet Handling without Profile Capped Mode
When an egress policer has been configured with a CIR (max or explicit rate other than '0') and
profile capped mode is not enabled, the policer's CIR bucket state will override the ingress 'soft-
in-profile' or 'soft-out-of-profile' state much like the ingress policer handles initial profile
'undefined' packets. If the CIR has not been defined or been set to '0' on the egress policer, the
egress policer output state will be 'in-profile' for 'soft-in-profile' packets and 'out-of-profile' for
'soft-out-of-profile' packets.
If a packet's profile has been reclassified at egress, the new profile classification is handled similar
to the ingress policer handling of initial 'in-profile' or 'out-of-profile' packets. When a packet has
been reclassified as 'hard-in-profile', it is applied to the egress policer's CIR bucket using a
'threshold-bc' higher than the 'threshold-bc' derived from the policer's CBS parameter, but the
policer output profile state will remain 'in-profile' even if the higher threshold is crossed. When a
packet has been reclassified as 'hard-out-of-profile', it does not consume the egress policer's CIR
bucket depth and the policer output profile state remains 'out-of-profile'.
Egress Policer CIR Packet Handling with Profile Capped Mode
When profile capped mode is enabled, the egress packet handling described in
Packet Handling without Profile Capped Mode on page 589
7950 XRS Quality of Service Guide
Egress Explicit Profile Reclassification
is modified in three aspects.
Egress Policer CIR
Page 589

Advertisement

Table of Contents
loading

Table of Contents