Network Port Queue Groups For Ip Interfaces; Pseudowire Shaping For Layer 2 And Layer 3 Services - Alcatel-Lucent 7450 Quality Of Service Manual

Queue Sharing and Redirection
When the first XCM in slot 11 or above is provisioned additional ingress hardware queues
will be allocated to XCMs in slots 11 to 20 for any configured ingress access port queue group
queue. If sufficient hardware queues are unavailable, the XCM provisioning will fail. Adding
queues to the queue group template or adding additional ingress access port queue groups will
continue to require more hardware queue to be allocated, with the configurations failing if
there are not sufficient available. When the last XCM in slot 11 and above is unprovisioned,
the related additional hardware queues to the all of the XCMs in slots 11 and above are freed.

Network Port Queue Groups for IP Interfaces

Queue groups may be created on egress network ports in order to provide network IP interface
queue redirection. A single set of egress port based forwarding class queues are available by
default and all IP interfaces on the port share the queues. Creating a network queue group
allows one or more IP interfaces to selectively redirect forwarding classes to the group in
order to override the default behavior. Using network egress queue groups it is possible to
provide dedicated queues for each IP interface.
Non-IPv4/non-IPv6/non-MPLS packets will remain on the regular network port queues.
Therefore, when using an egress port-scheduler it is important to parent the related regular
network port queues to appropriate port-scheduler priority levels to ensure the desired
operation under port congestion. This is particularly important for protocol traffic such as
LACP, EFM-OAM, ETH-CFM, ARP and IS-IS, which by default use the FC NC regular
network port queue.

Pseudowire Shaping for Layer 2 and Layer 3 Services

This feature allows the user to perform ingress and egress data path shaping of packets
forwarded within a spoke-sdp (PW). It applies to a VLL service, a VPLS/B-VPLS service,
and an IES/VPRN spoke-interface.
The ingress PW rate-limiting feature uses a policer in the queue-group provisioning model.
This model allows the mapping of one or more PWs to the same instance of policers that are
defined in a queue-group template.
Operationally, the provisioning model in the case of the ingress PW shaping feature consists
of the following steps:
392
1. Create an ingress queue-group template and configure policers for each FC that needs
to be redirected and optionally for each traffic type (unicast, broadcast, unknown, or
multicast).
Quality of Service Guide