epipe
PwTemplateToVpwsBinding

This object specifies which PW template that the service will use to establish the PWs to the remote VE. The user then specify the import RT associated with this binding (PwTemplateBindingRouteTarget), maximum five RTs can be specified. If no import RT specified, or if multiple matches are found, the numerically lowest pw-template is used.

By specifying the PW template and RTs in this object, the node will bind the advertisements received with the RT that matches the configured ones to the PW template to setup the PWs.

For BGP VPWS the following additional rules govern the use of PW-template:

• On transmission, the settings for the L2-Info extended community in the BGP Update are derived from the PW-template attributes. If multiple pw-templates (with or without import-rt) are speci- fied for the same VPWS instance the first pw-template entry will be used.
• On reception, the values of the parameters in the L2-Info extended community of the BGP Update are compared with the settings from the corresponding pw-template. The following steps are used to determine the local pw-template:
  • The RT values are matched to determine the pw-template.
  • If multiple pw-templates matches are found from the previous steps,the first (numerically lowest) configured pw-template entry will be considered.
  • If the value used for Layer 2 MTU (unless the value zero is received) does not match the pseudowire is created but with the operational state down.
  • If the values used for the C (control word) or S (sequenced delivery) flags are not zero the pseudowire is not created.

• Relative Name=[[pwtempl-${templateId}]]
• Displayed Name=PW Template Binding