A VPN in an L2VPN network is a collection of Forwarder, ForwarderEndpoint, and PseudoWire instances that are members of the same virtual private network. A BGP-signaled L2VPN also contains VRF and route target instances. All instances are configured on PE devices. All functions that are associated with establishing, maintaining, and operating an L2VPN take place in the PE devices.
The P devices are not aware of the L2VPNs; they forward packets over the established LSPs. Similarly, the CE devices are not aware of the L2VPNs; they operate without any knowledge of the existence of L2VPNs.
MPLS Manager discovers and creates the following L2VPNs:
-
VPWS VPNs or VPLS full-mesh VPNs for LDP-signaled L2VPNs that are implemented on Cisco devices
-
VPWS VPNs or VPLS full-mesh VPNs for LDP-signaled L2VPNs that are implemented on Juniper devices
-
VPWS VPNs or VPLS full-mesh VPNs for BGP-signaled L2VPNs that are implemented on Juniper devices
By default, MPLS Manager creates a VPN object for each discovered L2VPN. If you wish to change this behavior so that MPLS Manager does not create VPN objects for the discovered L2VPNs, set the L2VPN_CREATE_VPN parameter to FALSE in the MPLS Manager’s mpls.conf file, as explained in the VMware Smart Assurance MPLS Manager Configuration Guide.
