Pseudowire Shaping For Layer 2 And Layer 3 Services - Alcatel-Lucent 7950 Quality Of Service Manual

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:
1. Create an ingress queue-group template and configure policers for each FC that needs to
2. Apply the queue-group template to the network ingress forwarding plane where there
3. Configure FC-to-policer mappings together with the policer redirect to a queue-group in
4. Apply this network QoS policy to the ingress context of a spoke-sdp inside a service, or
One or more spoke-sdps can have their FCs redirected to use policers in the same policer queue-
group instance.
The egress PW shaping provisioning model allows the mapping of one or more PWs to the same
instance of queues, or policers and queues, that are defined in the queue-group template.
Operationally, the provisioning model consists of the following steps:
1. Create an egress queue-group template and configure queues only, or policers and queues
2. Apply the queue-group template to the network egress context of all ports where there
7950 XRS Quality of Service Guide
Ingress and Egress Queue Group Creation and Redirection
be redirected and optionally for each traffic type (unicast, broadcast, unknown, or
multicast).
exists a network IP interface that the PW packets can be received on. This creates one
instance of the template on the ingress of the FP. One or more instances of the same
template can be created.
the ingress context of a network QoS policy. No queue-group name is specified in this
step, which means the same network QoS policy can redirect different PWs to different
queue-group templates.
to the ingress context of a PW template and specify the redirect queue-group name.
for each FC which needs to be redirected.
exists a network IP interface which the PW packets can be forwarded on. This creates one
instance of the template on the egress of the port. One or more instances of the same
template can be created.
Page 309