Alcatel-Lucent 7950 Quality Of Service Manual page 223

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 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.
out — The out keyword is mutually exclusive to the in keyword. When the profile out command 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.
unknown-queue
Syntax unknown-queue queue-id [group queue-group-name]
no unknown-queue
Context config>qos>sap-ingress>fc fc-name
Description
This command overrides the default unknown unicast forwarding type queue mapping for fc fc-name. The
specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. Once
the forwarding class mapping is executed, all unknown traffic on a SAP using this policy is forwarded using
the queue-id.
The unknown forwarding type usually tracks the multicast forwarding type definition. This command
overrides that default behavior.
The no form of this command sets the unknown forwarding type queue-id back to the default of tracking the
multicast forwarding type queue mapping.
Parameters
queue-id — Specifiesan existing multipoint queue defined in the config>qos>sap-ingress context.
Values
Default
group queue-group-name — This optional parameter is used to redirect the forwarding type within the for-
warding class to the specified queue-id within the queue-group-name. When the policy is applied, all
packets matching the forwarding class and forwarding type will be redirected to the queue within the
specified queue group. The queue-group-name are configured in the config>qos>queue-group-tem-
plates egress and ingress contexts.
7950 XRS Quality of Service Guide
Any valid multipoint queue-id in the policy including 2 through 32.
11
Page 223