close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Common Configuration for All VPNs
- play_arrow VPNs Overview
- play_arrow Assigning Routing Instances to VPNs
- play_arrow Distributing Routes in VPNs
- play_arrow Distributing VPN Routes with Target Filtering
- play_arrow Configuring Forwarding Options for VPNs
  - Chained Composite Next Hops for VPNs and Layer 2 Circuits
  - Example: Configuring Chained Composite Next Hops for Direct PE-PE Connections in VPNs
- play_arrow Configuring Graceful Restart for VPNs
- play_arrow Configuring Class of Service for VPNs
  - VPNs and Class of Service
  - Rewriting Class of Service Markers and VPNs
- play_arrow Pinging VPNs
play_arrow Common Configuration for Layer 2 VPNs and VPLS
- play_arrow Overview
- play_arrow Layer 2 VPNs Configuration Overview
- play_arrow Configuring Layer 2 Interfaces
- play_arrow Configuring Path Selection for Layer 2 VPNs and VPLS
  - Understanding BGP Path Selection
  - Enabling BGP Path Selection for Layer 2 VPNs and VPLS
- play_arrow Creating Backup Connections with Redundant Pseudowires
  - Redundant Pseudowires for Layer 2 Circuits and VPLS
  - Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS
- play_arrow Configuring Class of Service for Layer 2 VPNs
  - Configuring Traffic Policing in Layer 2 VPNs
- play_arrow Monitoring Layer 2 VPNs
play_arrow Configuring Group VPNs
- play_arrow Configuring Group VPNv2
play_arrow Configuring Public Key Infrastructure
- play_arrow Configuring Digital Certificate Validation
  - Understanding Digital Certificate Validation
  - Example: Improving Digital Certificate Validation by Configuring Policy OIDs on an MX Series Device
- play_arrow Configuring a Device for Certificate Chains
  - IKE Authentication (Certificate-Based Authentication)
  - Example: Configuring a Device for Peer Certificate Chain Validation
- play_arrow Managing Certificate Revocation
  - Online Certificate Status Protocol and Certificate Revocation Lists
  - Example: Improving Security by Configuring OCSP for Certificate Revocation Status
play_arrow Configuring Layer 2 Circuits
- play_arrow Overview
  - Layer 2 Circuit Overview
- play_arrow Layer 2 Circuits Configuration Overview
- play_arrow Configuring Class of Service with Layer 2 Circuits
- play_arrow Configuring Pseudowire Redundancy for Layer 2 Circuits
- play_arrow Configuring Load Balancing for Layer 2 Circuits
  - Reducing APS Switchover Time in Layer 2 Circuits
- play_arrow Configuring Protection Features for Layer 2 Circuits
- play_arrow Monitoring Layer 2 Circuits with BFD
  - Configuring BFD for VCCV for Layer 2 Circuits
  - Example: Configuring BFD for VCCV for Layer 2 Circuits
- play_arrow Troubleshooting Layer 2 Circuits
  - Tracing Layer 2 Circuit Operations
play_arrow Configuring VPWS VPNs
- play_arrow Overview
- play_arrow Configuring VPWS VPNs
play_arrow Configuring VPLS
play_arrow Connecting Layer 2 VPNs and Circuits to Other VPNs
- play_arrow Connecting Layer 2 VPNs to Other VPNs
- play_arrow Connecting Layer 2 Circuits to Other VPNs
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

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

date_range 23-Dec-20

arrow_backward

arrow_forward

Requirements

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 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.

CE1

content_copy zoom_out_map
set interfaces ge-1/1/1 unit 0 family inet address 192.0.2.2/24
set interfaces ge-1/1/1 unit 0 family iso
set interfaces ge-1/1/1 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 198.51.100.1/24

PE1

content_copy zoom_out_map
set interfaces ge-0/0/4 unit 0 family inet address 10.38.0.5/30
set interfaces ge-0/0/4 unit 0 family mpls
set interfaces ge-0/1/1 encapsulation ethernet-ccc
set interfaces ge-0/1/1  unit 0 family ccc
set interfaces lo0 unit 0 family inet address 10.255.104.133/32
set routing-options forwarding-table chained-composite-next-hop ingress l2vpn
set routing-options autonomous-system 200
set routing-options forwarding-table export lbpp
set protocols mpls interface ge-0/0/4.0
set protocols ospf area 0.0.0.0 interface ge-0/0/4.0
set protocols bgp group PEs type internal
set protocols bgp group PEs local-address 10.255.104.133
set protocols bgp group PEs family l2vpn signaling
set protocols bgp group PEs family inet-vpn unicast
set protocols bgp group PEs neighbor 10.255.104.134
set routing-instances vpn-a instance-type l2vpn
set routing-instances vpn-a interface ge-0/1/1.0
set routing-instances vpn-a route-distinguisher 200:1
set routing-instances vpn-a vrf-target target:200:1
set routing-instances vpn-a protocols l2vpn  encapsulation-type ethernet
 set routing-instances vpn-a protocols l2vpn site 100 site-identifier 100
set routing-instances vpn-a protocols l2vpn site 100  interface ge-0/1/1.0 remote-site-id 200

PE2

content_copy zoom_out_map
set interfaces ge-1/0/2 unit 0 family inet address 10.38.0.13/30
set interfaces ge-1/0/2 unit 0 family mpls
set interfaces ge-1/0/5 encapsulation ethernet-ccc
set interfaces ge-1/0/5 unit 0 family ccc
set interfaces lo0 unit 0 family inet address 10.255.104.134/32
set routing-options forwarding-table chained-composite-next-hop ingress l2vpn
set routing-options autonomous-system 200
set routing-options forwarding-table export lbpp
set protocols mpls interface ge-1/0/2.0
set protocols ospf area 0.0.0.0 interface ge-1/0/2.0
set protocols bgp group PEs type internal
set protocols bgp group PEs local-address 10.255.104.134
set protocols bgp group PEs family l2vpn signaling
set protocols bgp group PEs family inet-vpn unicast
set protocols bgp group PEs neighbor 10.255.104.133
set routing-instances vpn-a instance-type l2vpn
set routing-instances vpn-a interface ge-1/0/5.0
set routing-instances vpn-a route-distinguisher 200:1
set routing-instances vpn-a vrf-target target:200:1
set routing-instances vpn-a protocols l2vpn  encapsulation-type ethernet
set routing-instances vpn-a protocols l2vpn site 200 site-identifier 200
set routing-instances vpn-a protocols l2vpn site 200  interface ge-1/0/5.0 remote-site-id 100

content_copy zoom_out_map
set interfaces ge-2/0/1 unit 0 family inet address 10.38.0.6/30
set interfaces ge-2/0/1 unit 0 family mpls
set interfaces ge-2/0/2 unit 0 family inet address 10.38.0.14/30
set interfaces ge-2/0/2 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 10.255.104.136/32
set protocols mpls interface ge-2/0/1.0
set protocols ospf area 0.0.0.0 interface ge-2/0/1.0
set protocols mpls interface ge-2/0/2.0
set protocols ospf area 0.0.0.0 interface ge-2/0/2.0
set routing-options autonomous-system 200

CE2

content_copy zoom_out_map
set interfaces ge-2/2/2 unit 0 family inet address 192.0.2.4/24
set interfaces ge-2/2/2 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 198.51.100.2/24

Procedure

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:

Note:

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.

Configure the interfaces on the PE1 router.

content_copy zoom_out_map
PE1 to CE1
[edit interfaces]
user@PE1# set interfaces ge-0/1/1 encapsulation ethernet-ccc
user@PE1# set interfaces ge-0/1/1  unit 0 family ccc

content_copy zoom_out_map
PE1 to P
[edit interfaces]
user@PE1 # set ge-0/0/4 unit 0 family inet address 10.38.0.5/30
user@PE1 # set ge-0/0/4 unit 0 family mpls

content_copy zoom_out_map
Loopback interface
[edit interfaces]
user@PE1 # set lo0 unit 0 family inet address 10.255.104.133/32

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

content_copy zoom_out_map
[edit routing-options]
use@PE1# set forwarding-table chained-composite-next-hop ingress l2vpn

Configure the autonomous system for PE1.
```
[edit routing-options]
user@PE1# set autonomous-system 200
```
Export the policy configured for load balancing.
```
[edit routing-options]
user@PE1# set forwarding-table export lbpp
```
Configure MPLS on the PE1 interfaces that connects to the P router.
```
[edit protocols]
set mpls interface ge-0/0/4.0
```

Configure OSPF on the PE1 nterface.

content_copy zoom_out_map
[edit protocols]
user@PE1# set ospf area 0.0.0.0 interface ge-0/0/4.0

Configure the IBGP group for PE1 to PE2 router.

content_copy zoom_out_map
[edit protocols]
user@PE1# set bgp group PEs type internal
user@PE1# set bgp group PEs local-address 10.255.104.133
user@PE1# set bgp group PEs family l2vpn signaling
user@PE1# set bgp group PEs family inet-vpn unicast
user@PE1# set bgp group PEs neighbor 10.255.104.134

Configure the routing instance parameters.

content_copy zoom_out_map
[edit routing-instances]
user@PE1# set vpn-a instance-type l2vpn
user@PE1# set vpn-a interface ge-0/1/1.0
user@PE1# set vpn-a route-distinguisher 200:1
user@PE1# set vpn-a vrf-target target:200:1
user@PE1# set vpn-a protocols l2vpn  encapsulation-type ethernet
user@PE1# set vpn-a protocols l2vpn site 100 site-identifier 100
user@PE1# set vpn-a protocols l2vpn site 100  interface ge-0/1/1.0 remote-site-id 200

Results

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.

PE1

content_copy zoom_out_map
user@PE1# show interfaces
ge-0/0/4 {
    unit 0 {
        family inet {
            address 10.38.0.5/30;
        }
        family mpls;
    }
}
ge-0/1/1 {
    encapsulation ethernet-ccc;
    unit 0 {
        family iso;
        family mpls;
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.255.104.133/32;
        }
    }
}

content_copy zoom_out_map
user@PE1# show protocols
mpls {
    interface ge0/0/4.0;
}
bgp {
    group PEs {
        type internal;
        local-address 10.255.104.133;
        family inet-vpn {
            unicast;
        }
        family l2vpn {
            signaling;
        }
        neighbor 10.255.104.134;
    }
}
ospf {
    area 0.0.0.0 {
        interface ge-0/0/4.0;
    }
}

content_copy zoom_out_map
user@PE1# show routing-options
autonomous-system 200;
forwarding-table {
    export lbpp;
    chained-composite-next-hop {
        ingress {
            l2vpn;
        }
    }
}

content_copy zoom_out_map
user@PE1# show routing-instances
vpn-a {
    instance-type l2vpn;
    interface ge-0/1/1.0;
    route-distinguisher 200:1;
    vrf-target target:200:1;
    protocols {
        l2vpn {
            encapsulation-type ethernet;
            site 100 {
                site-identifier 100;
                interface ge-0/1/1.0 {
                    remote-site-id 200;
                }
            }
        }
    }
}

arrow_backward PREVIOUS Chained Composite Next Hops for VPNs and Layer 2 Circuits

NEXT arrow_forward VPN Graceful Restart

Layer 2 VPNs and VPLS User Guide for Routing Devices

ON THIS PAGE