Page 494 7750 SR OS Services Guide
• Supports IGMP/PIM snooping
• Support for High Availability is provided
• Ethernet Service OAM toolset is supported: IEEE 802.1ag, Y.1731.
→ Not supported OAM features: CPE Ping, MAC trace/ping/populate/purge.
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 customer accounts
• Create template QoS, filter, scheduler, and accounting policies
• Create a VPLS service
• Configure interfaces and SAPs
• Create exclusive QoS and filter policies
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 re-used 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: i.e.
• 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
To Next Page
