Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
See matching posts in thread - JNCIE-SP/VPNs/Layer 3 VPNs/6PE...h...
The most common MPLS connectivity services include: Virtual Private LAN Service (VPLS) Layer 3 virtual private networks (VPNs) Layer 2 circuits and Layer 2 VPNs Layer 3 VPN service is a point-to-point Layer 3 VPN network built over the service provider’s MPLS transport network. This type of service is based on RFC 2547bis, BGP/MPLS IP VPNs . To ramp up on Layer 3 VPNs in Junos OS, click Layer 3 VPNs Feature Guide . This article provides answers to the most common questions about Layer 3 VPNs on Juniper Networks MX Series routers
Question How is composite next hop used in Layer 3 VPNs? Answer Composite next hop infrastructure provides optimized data structures to handle a label-per-prefix case and to help with convergence
Answer Prior to Junos OS Release 10.3, indirect next hop is only supported for Layer 3 VPNs. However, in Junos OS Release 10.3 and later, a constraint of not allowing VPLS configuration when using indirect next hop for other services is removed
Support for four-label push/pop would only be needed for VPN PE routers that could be the ingress for an RSVP LSP, as well as for an LDP LSP that tunnels over the RSVP, and then egresses at a router beyond the endpoint of the RSVP LSP. For Juniper Networks devices, the VPN PE routers only need to push two labels (VPN and LDP) and the core routers only need to swap and then push up to two labels (swap LDP, push RSVP, and bypass)
See matching posts in thread - Layer 2 broadcast domain over layer 3...
For more information, click Layer 3 VPNs Feature Guide
This is because at least one PE router must know about all active sources in the VPN. This behavior is detailed in draft-ietf-l3vpn-2547bis-mcast-bgp-07: Multicast in MPLS/BGP IP VPNs . To configure the RPT-SPT mode, include the rpt-spt statement at the [edit routing-instances routing-instance-name protocols mvpn mvpn-mode] hierarchy level for all VRFs that make up the VPN. To configure a selective provider tunnel for the shared tree, include the wildcard-group-inet, wildcard-group-inet6, and wildcard-source statements at the [edit routing-instances routing-instance-name provider-tunnel selective] hierarchy level