Ingress 'Undefined' Initial Profile - Alcatel-Lucent 7450 Quality Of Service Manual

Ingress 'Undefined' Initial Profile

Access ingress packets have one of three initial profile states prior to processing by the
policer:
The SAP ingress QoS policy classification rules map each packet to either a forwarding class
or a sub-class within a forwarding class. The forwarding class or sub-class may be defined as
explicit profile in or profile out (the default is no profile). When a packet's forwarding class
or sub-class is explicitly defined as profile in or profile out, the packet's priority is ignored,
and it is not handled by the ingress policer as profile 'undefined'.
See
on that initial state.
At egress, an ingress policer output of 'in-profile' is treated as 'soft-in-profile' and an ingress
policer output of 'out-of-profile' is treated as 'soft-out-of-profile'. Each may be changed by
egress profile reclassification or by an egress policer with a CIR rate defined.
Ingress Explicitly 'In-Profile' State Packet Handling
without Profile-Capped Mode
Packets that are explicitly 'in-profile' remain 'in-profile' in the ingress forwarding plane and
are not affected by the ingress policer CIR bucket state when profile-capped mode is not
enabled. They do not bypass the policer's CIR leaky bucket but are extended with a greater
threshold than the CBS derived 'threshold-bc'. This allows the 'undefined' packets to backfill
the remaining conforming CIR bandwidth after accounting for the explicit 'in-profile'
packets. This does not prevent the sum of the explicit 'in-profile' from exceeding the
configured CIR rate, but it does cause the 'undefined' packets that are marked 'in-profile' to
diminish to zero once the combined explicit 'in-profile' rate and 'undefined' rate causes the
bucket to reach 'threshold-bc'.
The policer's CIR bucket will indicate that the explicit 'in-profile' packets should be marked
'out-of-profile' once the bucket reaches the greater threshold, but this indication is ignored
by the ingress forwarding plane. All explicit 'in-profile' packets remain in-profile within the
ingress forwarding plane. However, once the packet is received at egress, an ingress 'in-
profile' packet will be treated as 'soft-in-profile' and the profile may be changed either by
explicit profile reclassification or by an egress policer with a CIR rate defined.
Quality of Service Guide
• Undefined
• profile in
• profile out
Table 74 to track the ingress behavior of initial profile and the effect of the CIR bucket
Class Fair Hierarchical Policing (CFHP)
863