FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 241
 
A pw-template-bind command configured within the VPLS service under the bgp-ad 
subcommand is a pointer to the pw-template that should be used. If a VPLS service 
does not specify an import-rt list, then that binding applies to all route targets 
accepted by that VPLS. The pw-template-bind command can select a different 
template on a per import-rt basis. It is also possible to specify pw-templates for some 
route targets with a VPLS service and use the single pw-template-bind command to 
address all unspecified but accepted imported targets. See Table 120 for the 
pw-template-bind CLI syntax.
Table 120 pw-template-bind CLI Syntax
It is important to understand the significance of the split-horizon-group used by the 
pw-template. Traditionally, when a VPLS instance was manually created using 
mesh-sdp bindings, these were automatically placed in a common 
split-horizon-group to prevent forwarding between the pseudowire in the VPLS 
instances. This prevents loops that would have otherwise occurred in the Layer 2 
service. When automatically discovering VPLS service using BGP AD, the service 
provider has the option of associating the auto-discovered pseudowire with a 
split-horizon group to control the forwarding between pseudowires.
To match the incoming traffic’s TPID with pw-template, you can use vlan-vc-etype. 
The following scenarios can occur:
• For traffic ingress on pw-template, the data plane traffic whose TPID (Ethertype 
after the MPLS label) does not match with the vlan-vc-etype configured on the 
pw-template, then the traffic would be forwarded with extra VLAN tag, for 
example, a user tag preserved and outer tag added with the VLAN of the egress 
SAP and the TPID of the service.
• In case the ingress control plane traffic TPID does not match with the 
pw-template TPID, then it will be dropped.
Example:
configure>service# pw-template 79
configure>service>pw-template# vlan-vc-etype 0x88a8
PERs6>config>service>vpls>bgp# pw-template-bind
— pw-template-bind <policy-id> [split-horizon-group <group name>]
— no pw-template-bind <policy-id>
<policy id> : [1..2147483647]
<group name> [32 chars max]