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

Setting a non-zero rate for the egress policer's CIR will modify this behavior, but only for Dot1P
and DEI egress marking purposes. For egress IP header ToS field marking decisions, the policer's
CIR state will not change the profile used for the marking decision. Both soft-in-profile and hard-
in-profile retain their inherent in-profile behavior and the soft-out-of-profile and hard-out-of-
profile retain their inherent out-of-profile behavior.
For L2 marking decisions (Dot1P and DEI), the hard-in-profile and hard-out-of-profile packets
ignore the egress policer's CIR state. When the packet state is hard-in-profile, the in-profile Dot1P
marking will be used and when DEI marking is enabled for the packets forwarding class it will be
marked 0. When the packet state is hard-out-of-profile, the out-of-profile Dot1P marking will be
used and when DEI marking is enabled for the packets forwarding class it will be marked 1.
When the egress packet state is soft-in-profile and soft-out-of-profile and the policer's CIR is
configured as non-zero, the current CIR state of the policer's CIR bucket will override the packets
soft profile state. When the policer's CIR is currently conforming, the output will be in-profile.
When the CIR state is currently exceeding, the output will be out-of-profile. The Dot1P and DEI
(when DE marking is configured) will reflect the CIR derived packet state.

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 Table 37
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.
7950 XRS Quality of Service Guide
Undefined
profile in
profile out
to track the ingress behavior of initial profile and the effect of the CIR bucket on that
Ingress 'Undefined' Initial Profile
Page 585