FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 231
5.11.2 BGP VPLS Configuration Procedure
BGP VPLS configuration requires the setup of the MPLS infrastructure and VPLS
instance:
• create LSPs
• create SDPs if manually provisioned ones are required
• create a VPLS service
• configure interfaces and SAPs
The provisioning of the BGP VPLS information is similar with the BGP AD for LDP
VPLS procedure:
• configure Route Distinguisher, Route Target
• configure pseudowire template to be used, eventually multiple mappings between
import RT and pseudowire template
• the above information is reused also by BGP-AD
• configure the local VE-ID
The BGP VPLS parameters are provisioned at VPLS instance level, once for all
SDPs, automatically generating the SDP associations using a procedure similar with
the auto-binding in BGP-VPNs/BGP-AD. That is:
• The MP-BGP Next Hop value is used to determine the Far End (FE) information.
• The FE value is used to see if any SDP already exist to the remote PE.
• If none exist, the equivalent SDP must be instantiated:
• FE value is used to find any existing LSP to remote PE
• SDP and pseudowire parameters from the related pseudowire template are used
5.11.3 Use of Pseudowire Template for BGP VPLS
The pseudowire template concept used for BGP AD is re-used also for BGP VPLS
to dynamically instantiate pseudowire (SDP-bindings) and the related SDP
(provisioned or automatically instantiated).
On transmission the settings for the L2-Info extended community in the BGP Update
are derived from the pseudowire-template attributes. The following rules apply:
• If multiple pseudowire-templates (with or without import-rt) are specified for the
same VPLS instance the first pseudowire-template entry will be used.
• Encaps Type is always 19 (13 in hex)
• BGP VPLS supports only the Ethernet pseudowire type so the setting of vc-type
parameter in pseudowire-template is ignored and ether value is always used.
To Next Page
Loading...
