Alcatel-Lucent 7450 Quality Of Service Manual page 410

Queue Sharing and Redirection
410
6. When a PW FC is redirected to use a policer in a named policer queue-group and the
queue-group name does not exist, the association is failed at the time the user
associates the ingress context of a spoke-SDP to the named queue-group. In such a
case, the PW packet feeds directly the ingress network shared queue for that FC
defined in the network-queue policy applied to the ingress of the MDA/FP.
7. When a PW FC is redirected to use a policer in a named policer queue-group and the
queue-group name exists but the policer-id is not defined in the queue-group
template, the association is failed at the time the user associates the ingress context
of a spoke-SDP to the named queue-group. In such a case, the PW packet feeds
directly the ingress network shared queue for that FC defined in the network-queue
policy applied to the ingress of the MDA/FP.
8. When a PW FC is redirected to use a policer in a named policer queue-group and the
queue-group name exists and the policer-id is defined in the queue-group template,
it is not required to check that an instance of that queue-group exists in all ingress FPs
which have network IP interfaces. The handling of this is dealt with in the data path
as follows:
a. When a PW packet for that FC is received and an instance of the referenced
queue-group name exists on that FP, the packet is processed by the policer and
is then feed the per-FP ingress shared queues referred to as policer-output-
queues.
b. When a PW packet for that FC is received and an instance of the referenced
queue-group name does not exist on that FP, the PW packets are fed directly into
the corresponding ingress network shared queue for that FC defined in the
network-queue policy applied to the ingress of the MDA/FP.
9. If a network QoS policy is applied to the ingress context of a PW, any PW FC, which
is not explicitly redirected in the network QoS policy, has the corresponding packets
feed directly the ingress network shared queue for that FC defined in the network-
queue policy applied to the ingress of the MDA/FP.
a. This behavior is the same regardless if the ingress network IP interface from
which the PW packet is received is redirected or not to a policer queue-group.
10. If no network QoS policy is applied to the ingress context of the PW, then all packets
of the PW feed:
a. the ingress network shared queue for the packet FC defined in the network-queue
policy applied to the ingress of the MDA/FP. This is the default behavior.
b. a queue-group policer followed by the per-FP ingress shared queues referred to
as policer-output-queues if the ingress context of the network IP interface from
which the packet is received is redirected to a queue-group. The only exceptions
to this behavior are for packets received from a IES/VPRN spoke interface and
from a R-VPLS spoke-SDP, which is forwarded to the R-VPLS IP interface. In
these two cases, the ingress network shared queue for the packet FC defined in
the network-queue policy applied to the ingress of the MDA/FP is used.
Quality of Service Guide