Pseudowire SAPs can be shaped on egress by a Vport on a physical port. The pseudowire SAP egress cannot explicitly declare which Vport to use, but they inherit the Vport used by the PW port egress shaping.
The intermediate destination identifier, used for ESM on MPLS pseudowires, is not applicable to VLL, IES and VPRN pseudowire SAPs.
If a pseudowire port is configured on a LAG, then Vport shaping is only supported if the LAG is in link mode.
Per-access node shaping is configured as follows:
Configure a Vport per AN under the port (or LAG) to which the SDP corresponding to the pseudowire SAP is bound. The Vport would be configured with aggregate rate-limit. (config>port>ethernet>access>egress>vport vport-name create).
Explicitly assign (by static configuration) a pseudowire port to a Vport. For limiting the total traffic to an AN, all pseudowire ports for an AN-port would refer to the same Vport.
For bandwidth control per pseudowire, the following configuration steps are used:
Create multiple Vports under the port to which SDP is bound. Each Vport can be configured with agg-rate rate, a scheduler or port-scheduler.
Assign each pseudowire to an AN to a unique Vport shaper (regular IOM/MDA).
To make use of the agg-rate rate or port-scheduler under a Vport, PW SAP queues and schedulers must be configured with the port-parent command. To make use of a scheduler under a Vport, PW SAP schedulers must be configured with a parent command and the parent-location vport under the tier 1 of the scheduler policy. The egress hierarchical parenting relationship options are shown in Figure: PW SAP egress scheduling hierarchy options. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide Quality of Service guide for more information.
