Alcatel-Lucent 7450 Quality Of Service Manual page 288

Service SAP QoS Policy Command Reference
profile
Syntax profile {in | out}
no profile
Context config>qos>sap-ingress>fc
Description This command places a forwarding class or sub-class into a color aware profile mode. Normally,
packets associated with a class are considered in-profile or out-of-profile solely based on the dynamic
rate of the ingress queue relative to its CIR. Explicitly defining a class as in-profile or out-of-profile
overrides this function by handling each packet with the defined profile state.
The profile command may only be executed when the forwarding class or the parent forwarding class
(for a sub-class) is mapped to a queue that has been enabled to support color aware profile packets. The
queue may only be configured for profile-mode at the time the queue is created in the SAP ingress QoS
policy.
A queue operating in profile-mode may support in-profile, out-of-profile and non-profiled packets
simultaneously. However, the high and low priority classification actions are ignored when the queue
is in profile-mode.
The no form of the command removes an explicit in-profile or out-of-profile configuration on a
forwarding class or sub-class.
Default no profile — The default profile state of a forwarding class or sub-class is not to treat ingress packets
as color aware. An explicit definition for in-profile or out-of-profile must be specified on the
forwarding class or sub-class.
Parameters in — The in keyword is mutually exclusive to the out keyword. When the profile in command is
out — The out keyword is mutually exclusive to the in keyword. When the profile out command
288
The value specified by prec-value is used to overwrite the Precedence bits within a matching
routed packets IP header ToS field.
Values
0 to 7
Default None (an explicit Precedence value must be specified)
An explicit dscp name or prec value must be specified for out-of-profile remarking to be
applied.
executed, all packets associated with the class will be handled as in-profile. Packets explicitly
handled as in-profile or out-of-profile still flow through the ingress service queue associated
with the class to preserve order within flows. In-profile packets will count against the CIR of
the queue, diminishing the amount of CIR available to other classes using the queue that are
not configured with an explicit profile.
is executed, all packets associated with the class will be handled as out-of-profile. Packets
explicitly handled as in-profile or out-of-profile still flow through the ingress service queue
associated with the class to preserve order within flows. Out-of-profile packets will not count
against the CIR of the queue, allowing other classes using the queue that are not configured
with an explicit profile to be measured against the full CIR.
Quality of Service Guide