Page 496 7750 SR OS Services Guide
• In earlier releases, in BGP-AD when the import RT policy changes a VPLS shutdown
followed by a no shutdown was required for the next pw-template-bin match to be
considered.
• Now the above command can be used also to apply the changes to the mapping between
pw-template-bind and import-rt. When used the command checks if all the bindings using
this pseudowire template in the command context (service id, if used) are still meant to use
this policy. If the mapping has changed and allow-service-impact is TRUE, then the old
binding is removed and then re-added with the new template.
Usage example: assuming the service vpls 100 bgp pw-template-bind 1 import-rt 100:50 was
removed, the following command can be used to remove the old pseudowire-bindings:
tools perform service id 100 eval-pw-template 1 allow-service-impact
Including the service id is not mandatory but it is recommended as it will reduce the scope of the
command to only the affected service id.
BGP Multi-Homing for VPLS
This section describes BGP based procedures for electing a designated forwarder among the set of
PEs that are multi-homed to a customer site. Only the local PEs are actively participating in the
selection algorithm. The PE(s) remote from the dual homed CE are not required to participate in
the designated forwarding election for a remote dual-homed CE.
The main components of the BGP based multi-homing solution for VPLS are:
• Provisioning model
• MP-BGP procedures
• Designated Forwarder Election
• Blackhole avoidance – indicating the designated forwarder change towards the core PEs
and access PEs or CEs
• The interaction with pseudowire signaling (BGP/LDP)
To Next Page
Loading...
