Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Example: Configuring Chained Composite Next Hops for Direct PE-PE Connections in VPNs


This example shows how to enable a Provider Edge (PE) router Layer 2 Virtual Private Network (VPN) connection with chained composite next hops for MIC and MPC interfaces on MX Series and T4000 routers. This example uses the following hardware and software components

  • Five routers that can be a combination of MX240, MX480, MX960, or T4000 routers.

  • Junos OS Release 17.3R1 or later running on all the devices.

Overview and Topology

Figure 1 shows the sample topology of a Layer 2 VPN connection with chained composite next hops for MIC and MPC interfaces on MX series routers.

Figure 1: Chained Composite Next Hop on a PE RouterChained Composite Next Hop on a PE Router


CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.







Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.

To configure basic Layer 2 VPN with chained composite next hop on the PE1 router:


Repeat this procedure for the PE2 router in the MPLS domain, after modifying the appropriate interface names, addresses, and any other parameters for the router.

  1. Configure the interfaces on the PE1 router.

  2. Enable chained composite next hop on the global Layer 2 VPN.

  3. Configure the autonomous system for PE1.

  4. Export the policy configured for load balancing.

  5. Configure MPLS on the PE1 interfaces that connects to the P router.

  6. Configure OSPF on the PE1 nterface.

  7. Configure the IBGP group for PE1 to PE2 router.

  8. Configure the routing instance parameters.


From configuration mode, confirm your configuration by entering the show chassis, show interfaces, show protocols, show routing-options, show routing-instances, and show policy-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.