Access ingress packets have one of three initial profile states before processing by the policer:
undefined
profile in
profile out
The SAP ingress QoS policy classification rules map each packet to either a forwarding class or a subclass within a forwarding class. The forwarding class or subclass may be defined as explicit profile in or profile out (the default is no profile). When a packet’s forwarding class or subclass 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: Effect of profile-capped mode on CIR output to track the ingress behavior of initial profile and the effect of the CIR bucket 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.