Alcatel-Lucent 7950 Quality Of Service Manual page 179

default-priority
Syntax default-priority {high | low}
Context config>qos>sap-ingress
Description
This command configures the default enqueuing priority for all packets received on an ingress SAP using
this policy. To change the default priority for the policy, the fc-name must be defined whether it is being
changed or not.
Default
low
Parameters high — Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the
packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP
queuing, once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing
priority is lost.
low — Setting the enqueuing parameter to low for a packet decreases the likelihood of enqueuing the packet
when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing, once
the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
fc
Syntax [no] fc fc-name
Context config>qos>sap-ingress
Description
The fc command creates a class or sub-class instance of the forwarding class fc-name. Once the fc-name is
created, classification actions can be applied and the sub-class can be used in match classification criteria.
Attempting to use an undefined sub-class in a classification command will result in an execution error and
the command will fail.
The no form of the command removes all the explicit queue mappings for fc-name forwarding types. The
queue mappings revert to the default queues for fc-name. To successfully remove a sub-class, all
associations with the sub-class in the classification commands within the policy must first be removed or
diverted to another forwarding class or sub-class.
Parameters fc-name — The parameter sub-class-name is optional and must be defined using a dot separated notation
with a preceding valid system-wide forwarding class name. Creating a sub-class follows normal naming
conventions. Up to sixteen ASCII characters may be used. If the same sub-name is used with two or
more forwarding class names, each is considered a different instance of sub-class. A sub-class must
always be specified with its preceding forwarding class name. When a forwarding class is created or
specified without the optional sub-class, the parent forwarding class is assumed.
Within the SAP ingress QoS policy, up to 56 sub classes may be created. Each of the 56 sub-classes may
be created within any of the eight parental forwarding classes. Once the limit of 56 is reached, any
further sub-class creations will fail and the sub-class will not exist.
Successfully creating a sub-class places the CLI within the context of the sub-class for further sub-class
parameter definitions. Within the sub-class context, commands may be executed that define sub-class
7950 XRS Quality of Service Guide Page 179