Alcatel-Lucent 7950 Quality Of Service Manual page 323

•
•
If the operation above is successful, then:
•
•
The system decrements the forwarding plane queue group template association counter for each
ingress queue group where redirection is applied to the ingress SAP.
For the SAP-based provisioning model, the rules for redirecting a forwarding class queue to an
egress port queue group are similar to those on ingress.
•
•
•
7950 XRS Quality of Service Guide
Ingress and Egress Queue Group Creation and Redirection
If the forwarding class is being moved to a local policer ID within the SAP ingress QoS
policy and the local policer ID does not exist, the redirection removal from the current
queue group policer ID will fail.
If the forwarding class is being moved to a local policer ID within the SAP ingress QoS
policy and it is the first forwarding class to be mapped to the policer ID the system will
attempt to instantiate the policer on each ingress SAP where the SAP ingress QoS policy
is applied. If the policer cannot be created on any of the SAPs, the redirection removal
from the current queue group policer ID will fail.
The system decrements the association counter for the ingress queue group template with
the same name as the queue group previously specified in the forwarding class redirection.
The system decrements the policer ID association counter within the queue group
template for the policer ID previously specified in the forwarding class redirection.
If an egress QoS policy containing one or more redirections is applied to a SAP, but either
no queue group instance is specified at association time, or a named queue group instance
is specified and either the queue group name or the instance identifier does not correspond
to a queue group that has been created on the egress port, then the association will be
rejected.
If all of the redirections in an egress QoS policy are to queue ids that do not exist in the
named queue group instance, then the association will be rejected.
Note that if a policer local to a SAP feeds into a SAP based queue group queue instance,
and the queue ID to use is not explicitly specified in the egress QoS policy (through the
command policer policer-id port-redirect-group-queue) and is instead inferred from the
forwarding class of the policer, but that forwarding class does not exist in the queue group
template, then no error is generated. Instead, the queue with the lowest queue ID is used in
the queue group instance. If at a later time, a user attempts to add a queue with a given
queue-id to a policer redirect for a given forwarding class in the egress QoS template, then
the system will check that the corresponding queue-id exists in any queue group instances
associated with any SAPs using the QoS policy.
Page 323