close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Features Common to EVPN-VXLAN, EVPN-MPLS, and EVPN-VPWS
- play_arrow Configuring Interfaces
  - VLAN ID Ranges and Lists in an EVPN Environment
- play_arrow MAC Address Features with EVPN Networks
- play_arrow Configuring Routing Instances for EVPN
- play_arrow Configuring Route Targets
- play_arrow Routing Policies for EVPN
  - Routing policies for EVPN
  - Example: Using Policy Filters to Filter EVPN Routes
- play_arrow Layer 3 Gateways with Integrated Routing and Bridging for EVPN Overlays
  - Understanding the MAC Addresses For a Default Virtual Gateway in an EVPN-VXLAN or EVPN-MPLS Overlay Network
- play_arrow EVPN Multihoming
- play_arrow Link States and Network Isolation Conditions in EVPN Networks
- play_arrow EVPN Proxy ARP and ARP Suppression, and NDP and NDP Suppression
  - EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression
  - ARP and NDP Request with a proxy MAC address
- play_arrow Configuring DHCP Relay Agents
  - DHCP Relay Agent in EVPN-MPLS Network
  - DHCP Relay Agent over EVPN-VXLAN
- play_arrow High Availability in EVPN
- play_arrow Monitoring EVPN Networks
  - Connectivity Fault Management Support for EVPN and Layer 2 VPN Overview
  - Configure a MEP to Generate and Respond to CFM Protocol Messages
- play_arrow Layer 2 Control Protocol Transparency
  - Layer 2 Control Protocol Transparency for EVPN
play_arrow EVPN-VXLAN
- play_arrow Overview
- play_arrow Configuring EVPN-VXLAN Interfaces
- play_arrow Configuring VLAN-Aware Bundle Services, VLAN-Based Services, and Virtual Switch Support
- play_arrow Load Balancing with EVPN-VXLAN Multihoming
  - Dynamic Load Balancing in an EVPN-VXLAN Network
  - Fast Reroute for Egress Link Protection with EVPN-VXLAN Multihoming
- play_arrow Setting Up a Layer 3 VXLAN Gateway
- play_arrow Configuring an EVPN-VXLAN Centrally-Routed Bridged Overlay
  - Example: Configure an EVPN-VXLAN Centrally-Routed Bridging Fabric
  - Example: Configure an EVPN-VXLAN Centrally-Routed Bridging Fabric Using MX Routers as Spines
- play_arrow Configuring an EVPN-VXLAN Edge-Routed Bridging Overlay
- play_arrow IPv6 Underlay for VXLAN Overlays
  - EVPN-VXLAN with an IPv6 Underlay
  - Example: Configure an IPv6 Underlay for Layer 2 VXLAN Gateway Leaf Devices
- play_arrow Multicast Features with EVPN-VXLAN
- play_arrow Configuring the Tunneling of Q-in-Q Traffic
  - Examples: Tunneling Q-in-Q Traffic in an EVPN-VXLAN Overlay Network
- play_arrow Tunnel Traffic Inspection on SRX Series Devices
  - Tunnel Inspection for EVPN-VXLAN by SRX Series Devices
- play_arrow Fault Detection and Isolation in EVPN-VXLAN Fabrics
play_arrow EVPN-MPLS
- play_arrow Overview
- play_arrow Convergence in an EVPN MPLS Network
  - Convergence in a Multihomed EVPN-MPLS Network
- play_arrow Pseudowire Termination at an EVPN
- play_arrow Configuring the Distribution of Routes
- play_arrow Configuring VLAN Services and Virtual Switch Support
- play_arrow Configuring Integrated Bridging and Routing
- play_arrow Configuring IGMP or MLD Snooping with EVPN-MPLS
play_arrow EVPN E-LAN Services
play_arrow EVPN-VPWS
- play_arrow Configuring VPWS Service with EVPN Mechanisms
play_arrow EVPN-ETREE
- play_arrow Overview
  - EVPN-ETREE Overview
- play_arrow Configuring EVPN-ETREE
  - Example: Configuring EVPN E-Tree Service
play_arrow Using EVPN for Interconnection
- play_arrow Interconnecting VXLAN Data Centers With EVPN
  - VXLAN Data Center Interconnect Using EVPN Overview
  - Example: Configuring VXLAN Data Center Interconnect Using EVPN
- play_arrow Interconnecting EVPN-VXLAN Data Centers Through an EVPN-MPLS WAN
- play_arrow Extending a Junos Fusion Enterprise Using EVPN-MPLS
play_arrow PBB-EVPN
- play_arrow Configuring PBB-EVPN Integration
- play_arrow Configuring MAC Pinning for PBB-EVPNs
  - PBB-EVPN MAC Pinning Overview
  - Configuring PBB-EVPN MAC Pinning
play_arrow EVPN Standards
- play_arrow Supported EVPN Standards
  - Supported EVPN Standards
play_arrow VXLAN-Only Features
- play_arrow Flexible VXLAN Tunnels
  - Understanding Programmable Flexible VXLAN Tunnels
- play_arrow Static VXLAN
  - Static VXLAN
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Example: Configuring Basic EVPN Active-Active Multihoming

date_range 20-Dec-24

arrow_backward

arrow_forward

This example shows how to configure an active-active multihomed customer edge (CE) devices and provider edge (PE) devices in an Ethernet VPN (EVPN).

Requirements

This example uses the following hardware and software components:

Four MX Series 5G Universal Routing Platforms with MPC interfaces only, where:
- Two devices are configured as provider edge (PE) routers connected to a common multihomed customer site.
- One device is configured as a remote PE router connected to a single-homed customer site.
- One device is configured as a provider router.
• Two customer edge (CE) devices, where:
- Two CE devices that are multihomed.
- One CE devices that is single-homed .

Before you begin:

Configure the router interfaces.
Configure OSPF or any other IGP protocol.
Configure a BGP internal group.
Configure MPLS.

Overview

Figure 1 illustrates a simple EVPN topology. Routers PE1 and PE2 are provider edge (PE) routers connected to multihomed customer edge (CE) router CE1. Router P is the provider router connected to Routers PE1, PE2, and PE3. Router PE3 is connected to customer edge router CE2.

Figure 1: Simple EVPN Multihomed Topology

Configuration

CLI Quick Configuration

The configurations parameters for the routers are as follows:

CE1

content_copy zoom_out_map
chassis {
    aggregated-devices {
        ethernet {
            device-count 1;
        }
    }
}
interfaces {
    ge-0/0/1 {
        description To-PE1;
        gigether-options {
            802.3ad ae0;
        }
    }
    ge-0/0/2 {
        description To-PE2;
        gigether-options {
            802.3ad ae0;
        }
    }
    ge-0/0/7 {
        unit 0 {
            family bridge {
                interface-mode access;
                vlan-id 10;
            }
        }
    }
    ge-0/0/8 {
        unit 0 {
            family bridge {
                interface-mode access;
                vlan-id 20;
            }
        }
    }
    ae0 {
        description To-PE1_and_PE2;
        unit 0 {
            family bridge {
                interface-mode trunk;
                vlan-id-list [ 10 20 ];
            }
        }
    }
}
bridge-domains { 
    BD {
        vlan-id-list [ 10 20 ];  
    }
}

PE1

content_copy zoom_out_map
interfaces {
    ge-0/0/1 {
        description To-CE1;
        flexible-vlan-tagging;
        encapsulation flexible-ethernet-services;
        esi {
            00:11:11:11:11:11:11:11:11:11;
            all-active;
        }
        unit 10 {
            family bridge {
                interface-mode trunk;
                vlan-id-list [ 10 20 ];
            }
        }
    }
    ge-0/0/3 {
        unit 0 {
            family inet {
                address 10.3.3.1/30;
                }
            family mpls;
        }
    }
     lo0 {
        unit 0 {
            family inet {
                address 192.168.1.1/32;
            }
        }
    }
}
routing-options {
    router-id 192.168.1.1;
    autonomous-system 65432;
    forwarding-table {
        export evpn-pplb;
    }
}
protocols {
    rsvp {
        interface ge-0/0/3.0;
    }
    mpls {
        no-cspf;
        label-switched-path PE1-to-PE2 {
            to 192.168.2.2;
        }
        label-switched-path PE1-to-PE3 {
            to 192.168.3.3;
        }
        interface ge-0/0/3.0;
    }
    bgp {
        group EVPN-PE {
            type internal;
            local-address 192.168.1.1;
            family inet-vpn {
                unicast;
            }
            family evpn {
                signaling;
            }
            neighbor 192.168.3.3;
            neighbor 192.168.2.2;
        }
    }
    ospf {
        traffic-engineering;
        area 0.0.0.0 {
            interface all {
                interface-type p2p;
            }
            interface fxp0.0 {
                disable;
            }
        }
    }
}
routing-instances {
    evpn-ta {
        instance-type virtual-switch;         
        interface ge-0/0/1.10;   
        route-distinguisher 65432:10;    
        vrf-target target:65432:10;
        protocols {
            evpn {
                extended-vlan-list [ 10 20 ];
            }
        }
        bridge-domains {
            bd10 {
                domain-type bridge;
                vlan-id 10;
            }
            bd20 {
                domain-type bridge;
                vlan-id 20;
            }
        }
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}

PE2

content_copy zoom_out_map
interfaces {
    ge-0/0/2 {
        description To-CE1;
        flexible-vlan-tagging;
        encapsulation flexible-ethernet-services;
        esi {
            00:11:11:11:11:11:11:11:11:11;
            all-active;
        }
        unit 10 {
            family bridge {
                interface-mode trunk;
                vlan-id-list [ 10 20 ];
            }
        }
    }
    ge-0/0/4 {
        unit 0 {
            family inet {
                address 10.4.4.1/30;
                }
            family mpls;
        }
    }
     lo0 {
        unit 0 {
            family inet {
                address 192.168.2.2/32;
            }
        }
    }
}
routing-options {
    router-id 192.168.2.2;
    autonomous-system 65432;
    forwarding-table {
        export evpn-pplb;
    }
}
protocols {
    rsvp {
        interface ge-0/0/4.0;
    }
    mpls {
        no-cspf;
        label-switched-path PE2-to-PE1 {
            to 192.168.1.1;
        }
        label-switched-path PE2-to-PE3 {
            to 192.168.3.3;
        }
        interface ge-0/0/4.0;
    }
    bgp {
        group EVPN-PE {
            type internal;
            local-address 192.168.2.2;
            family inet-vpn {
                unicast;
            }
            family evpn {
                signaling;
            }
            neighbor 192.168.1.1;
            neighbor 192.168.3.3;
        }
    }
    ospf {
        traffic-engineering;
        area 0.0.0.0 {
            interface all {
                interface-type p2p;
            }
            interface fxp0.0 {
                disable;
            }
        }
    }
}
routing-instances {
    evpn-ta {
        instance-type virtual-switch;         
        interface ge-0/0/2.10;   
        route-distinguisher 65432:10;    
        vrf-target target:65432:10;
        protocols {
            evpn {
                extended-vlan-list [ 10 20 ];
            }
        }
        bridge-domains {
            bd10 {
                domain-type bridge;
                vlan-id 10;
            }
            bd20 {
                domain-type bridge;
                vlan-id 20;
            }
        }
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}

Router PE3

content_copy zoom_out_map
interfaces {
    ge-0/0/5 {
        unit 0 {
            family inet {
                address 10.5.5.1/30;
                }
            family mpls;
        }
    }
    ge-0/0/6 {
        flexible-vlan-tagging;   
        encapsulation flexible-ethernet-services;
        unit 10 {
            family bridge {
                interface-mode trunk;
                vlan-id-list 10;
            }
        }
        unit 20 {
            family bridge {
                interface-mode trunk;
                vlan-id-list 20;
            }
        }
    }
     lo0 {
        unit 0 {
            family inet {
                address 192.168.3.3/32;
            }
        }
    }
    routing-options {
        router-id 192.168.3.3;
        autonomous-system 65432;
        forwarding-table {
            export evpn-pplb;
        }
    }
    protocols {
        rsvp {
            interface ge-0/0/5.0;
        }
        mpls {
            no-cspf;
            label-switched-path PE3-to-PE1 {
                to 192.168.1.1;
            }
            label-switched-path PE3-to-PE2 {
                to 192.168.2.2;
            }
            interface ge-0/0/5.0;
        }
        bgp {
            group EVPN-PE {
                type internal;
                local-address 192.168.3.3;
                family inet-vpn {
                    unicast;
                }
                family evpn {
                    signaling;
                }
                neighbor 192.168.1.1;
                neighbor 192.168.2.2;
            }
        }
        ospf {
            traffic-engineering;
            area 0.0.0.0 {
                interface all {
                    interface-type p2p;
                }
                interface fxp0.0 {
                    disable;
                }
            }
        }
    }
    routing-instances {
        evpn-ta {
            instance-type virtual-switch;         
            interface ge-0/0/6.10;   
            interface ge-0/0/6.20;   
            route-distinguisher 65432:10;    
            vrf-target target:65432:10;
            protocols {
                evpn {
                    extended-vlan-list [ 10 20 ];
                }
            }
            bridge-domains {
                bd10 {
                    domain-type bridge;
                    vlan-id 10;
                    bridge-options {
                        interface ge-0/0/6.10;
                    }
                }
                bd20 {
                    domain-type bridge;
                    vlan-id 20;
                    bridge-options {
                        interface ge-0/0/6.20;
                    }
                }
            }
        }
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}

Router P

content_copy zoom_out_map
interfaces {
    ge-0/0/3 {
        unit 0 {
            family inet {
                address 10.3.3.2/30;
                }
            family mpls;
        }
    }
    ge-0/0/4 {
        unit 0 {
            family inet {
                address 10.4.4.2/30;
                }
            family mpls;
        }
    }
    ge-0/0/5 {
        unit 0 {
            family inet {
                address 10.5.5.2/30;
                }
            family mpls;
        }
    }
     lo0 {
        unit 0 {
            family inet {
                address 192.168.4.4/32;
            }
        }
    }
}
routing-options {
    router-id 192.168.4.4;
    autonomous-system 65432;
}
protocols {
    rsvp {
        interface all;
        interface fxp0.0 {
            disable;
        }
    }
    mpls {
        interface all;
        interface fxp0.0 {
            disable;
        }
    }
    ospf {
        traffic-engineering;
        area 0.0.0.0 {
            interface all {
                interface-type p2p;
            }
            interface fxp0.0 {
                disable;
            }
        }
    }
}

arrow_backward PREVIOUS Example: Configuring EVPN-MPLS Active-Standby Multihoming

NEXT arrow_forward Example: Configuring EVPN Active-Active Multihoming

EVPN User Guide

ON THIS PAGE

Example: Configuring Basic EVPN Active-Active Multihoming

Requirements

Overview

Configuration

CLI Quick Configuration

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry