Example: Interconnecting EVPN-VXLAN Data Center Networks Through a WAN Running EVPN-based MPLS

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 in the CLI User Guide.

Configure the MX router as ToR11:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set system host-name ToR11
   

2. Configure the interfaces and bridge domains on the CE2 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set logical-systems CE-2 interfaces ge-1/0/9 unit 0 description "CONNECTED TO Host 2"
   user@ToR11# set logical-systems CE-2 interfaces ge-1/0/9 unit 0 family bridge interface-mode trunk
   user@ToR11# set logical-systems CE-2 interfaces ge-1/0/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR11# set logical-systems CE-2 interfaces ge-1/1/6 unit 0 description "CONNECTED TO ToR11"
   user@ToR11# set logical-systems CE-2 interfaces ge-1/1/6 unit 0 family bridge interface-mode trunk
   user@ToR11# set logical-systems CE-2 interfaces ge-1/1/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR11# set logical-systems CE-2 bridge-domains BD-1 domain-type bridge
   user@ToR11# set logical-systems CE-2 bridge-domains BD-1 vlan-id 1
   user@ToR11# set logical-systems CE-2 bridge-domains BD-2 domain-type bridge
   user@ToR11# set logical-systems CE-2 bridge-domains BD-2 vlan-id 2
   user@ToR11# set logical-systems CE-2 bridge-domains BD-3 domain-type bridge
   user@ToR11# set logical-systems CE-2 bridge-domains BD-3 vlan-id 3
   user@ToR11# set logical-systems CE-2 bridge-domains BD-4 domain-type bridge
   user@ToR11# set logical-systems CE-2 bridge-domains BD-4 vlan-id 4
   user@ToR11# set logical-systems CE-2 bridge-domains BD-5 domain-type bridge
   user@ToR11# set logical-systems CE-2 bridge-domains BD-5 vlan-id 5
   

3. Configure trace options for the interfaces to enable trace logs.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set interfaces traceoptions file ToR11-DCD.log
   user@ToR11# set interfaces traceoptions file size 10m
   user@ToR11# set interfaces traceoptions flag all

4. Set the number of aggregated Ethernet interfaces.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set chassis aggregated-devices ethernet device-count 1
   

5. Configure the interfaces on the ToR11 device to connect to the MX12, CE-2, CE-1, ToR12, and MX11 devices to enable underlay connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set interfaces ge-1/0/0 description "CONNECTED TO CE-1"
   user@ToR11# set interfaces ge-1/0/0 gigether-options 802.3ad ae0
   user@ToR11# set interfaces ge-1/0/5 unit 0 description "CONNECTED TO MX12"
   user@ToR11# set interfaces ge-1/0/5 unit 0 family inet address 192.168.4.1/24
   user@ToR11# set interfaces ge-1/0/6 unit 0 description "CONNECTED TO CE-2"
   user@ToR11# set interfaces ge-1/0/6 unit 0 family bridge interface-mode trunk
   user@ToR11# set interfaces ge-1/0/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR11# set interfaces ge-1/1/1 unit 0 description "CONNECTED TO MX11"
   user@ToR11# set interfaces ge-1/1/1 unit 0 family inet address 192.168.3.1/24
   user@ToR11# set interfaces ge-1/1/3 unit 0 description "CONNECTED TO ToR12"
   user@ToR11# set interfaces ge-1/1/3 unit 0 family inet address 192.168.2.1/24

6. Configure a Link Aggregation Control Protocol (LACP)-enabled link aggregation group (LAG) interface towards the CE-1 end host device. The ESI value is globally unique across the entire EVPN domain. The all-active configuration enables ToR11 and ToR12 to forward traffic to, and from the CE devices, such that all CE links are actively used.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set interfaces ae0 esi 00:11:11:11:11:11:11:11:11:11
   user@ToR11# set interfaces ae0 esi all-active
   user@ToR11# set interfaces ae0 aggregated-ether-options lacp active
   user@ToR11# set interfaces ae0 aggregated-ether-options lacp periodic fast
   user@ToR11# set interfaces ae0 aggregated-ether-options lacp system-id 11:11:11:11:11:11
   user@ToR11# set interfaces ae0 unit 0 family bridge interface-mode trunk
   user@ToR11# set interfaces ae0 unit 0 family bridge vlan-id-list 1-5

7. Configure the loopback interface address and routing options.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set interfaces lo0 unit 81 family inet address 192.0.2.11/32
   user@ToR11# set routing-options router-id 192.0.2.11
   user@ToR11# set routing-options autonomous-system 65100
   

8. Apply the load balancing policy to the forwarding table.

   content_copy zoom_out_map

   [edit]
   user@ToR11# set routing-options forwarding-table export evpn-pplb

9. Configure external BGP (EBGP) underlay connectivity between the ToR (ToR11 and ToR12) and gateway routers (MX11 and MX12).

   content_copy zoom_out_map

   [edit]
   user@ToR11# set protocols bgp local-as 64100
   user@ToR11# set protocols bgp group MX11 type external
   user@ToR11# set protocols bgp group MX11 local-address 192.168.3.1
   user@ToR11# set protocols bgp group MX11 export LO
   user@ToR11# set protocols bgp group MX11 export TEST
   user@ToR11# set protocols bgp group MX11 peer-as 65400
   user@ToR11# set protocols bgp group MX11 neighbor 192.168.3.2 family inet unicast
   user@ToR11# set protocols bgp group MX12 type external
   user@ToR11# set protocols bgp group MX12 local-address 192.168.4.1
   user@ToR11# set protocols bgp group MX12 export LO
   user@ToR11# set protocols bgp group MX12 export TEST
   user@ToR11# set protocols bgp group MX12 peer-as 65500
   user@ToR11# set protocols bgp group MX12 neighbor 192.168.4.2 family inet unicast
   user@ToR11# set protocols bgp group ToR12 type external
   user@ToR11# set protocols bgp group ToR12 local-address 192.168.2.1
   user@ToR11# set protocols bgp group ToR12 export LO
   user@ToR11# set protocols bgp group ToR12 export TEST
   user@ToR11# set protocols bgp group ToR12 peer-as 65200
   user@ToR11# set protocols bgp group ToR12 local-as 65100
   user@ToR11# set protocols bgp group ToR12 neighbor 192.168.2.2 family inet unicast

10. Configure the external BGP (EBGP) overlay between the ToR (ToR11 and ToR12) and gateway routers (MX11 and MX12) and set EVPN as the signaling protocol.

    Step-by-Step Procedure

    1. Configure a MP-EBGP overlay to connect between ToR11 and MX11 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR11# set protocols bgp group MX11-EVPN type external
       user@ToR11# set protocols bgp group MX11-EVPN multihop ttl 2
       user@ToR11# set protocols bgp group MX11-EVPN multihop no-nexthop-change
       user@ToR11# set protocols bgp group MX11-EVPN local-address 192.0.2.11
       user@ToR11# set protocols bgp group MX11-EVPN export TEST
       user@ToR11# set protocols bgp group MX11-EVPN peer-as 65400
       user@ToR11# set protocols bgp group MX11-EVPN local-as 65100
       user@ToR11# set protocols bgp group MX11-EVPN neighbor 192.0.2.21 family evpn signaling

    2. Configure a MP-EBGP overlay to connect between ToR11 and MX12 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR11# set protocols bgp group MX12-EVPN type external
       user@ToR11# set protocols bgp group MX12-EVPN multihop ttl 2
       user@ToR11# set protocols bgp group MX12-EVPN multihop no-nexthop-change
       user@ToR11# set protocols bgp group MX12-EVPN local-address 192.0.2.11
       user@ToR11# set protocols bgp group MX12-EVPN export TEST
       user@ToR11# set protocols bgp group MX12-EVPN peer-as 65500
       user@ToR11# set protocols bgp group MX12-EVPN local-as 65100
       user@ToR11# set protocols bgp group MX12-EVPN neighbor 192.0.2.22 family evpn signaling

    3. Configure a MP-EBGP overlay to connect between ToR11 and ToR12 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR11# set protocols bgp group ToR12-EVPN type external
       user@ToR11# set protocols bgp group ToR12-EVPN multihop ttl 2
       user@ToR11# set protocols bgp group ToR12-EVPN multihop no-nexthop-change
       user@ToR11# set protocols bgp group ToR12-EVPN local-address 192.0.2.11
       user@ToR11# set protocols bgp group ToR12-EVPN export TEST
       user@ToR11# set protocols bgp group ToR12-EVPN peer-as 65200
       user@ToR11# set protocols bgp group ToR12-EVPN local-as 65100
       user@ToR11# set protocols bgp group ToR12-EVPN neighbor 192.0.2.12 family evpn signaling

11. Configure trace operations to track all Layer 2 address learning and forwarding properties.

    content_copy zoom_out_map

    [edit]
    user@ToR11# set protocols l2-learning traceoptions file TOR11-L2ALD.log
    user@ToR11# set protocols l2-learning traceoptions file size 10m
    user@ToR11# set protocols l2-learning traceoptions level all
    user@ToR11# set protocols l2-learning traceoptions flag all

12. Configure routing policy to accept the direct loopback address route.

    content_copy zoom_out_map

    [edit]
    user@ToR11# set policy-options policy-statement LO term 1 from protocol direct
    user@ToR11# set policy-options policy-statement LO term 1 from route-filter 192.0.2.11/32 exact
    user@ToR11# set policy-options policy-statement LO term 1 then accept
    

13. Configure the NO-EXPORT community.

    content_copy zoom_out_map

    [edit]
    user@ToR11# set policy-options community NO-EXPORT members no-advertise
    user@ToR11# set policy-options community NO-EXPORT members no-export
    user@ToR11# set policy-options community NO-EXPORT members no-export-subconfed
    

14. Configure the load balancing and TEST policies.

    content_copy zoom_out_map

    [edit]
    user@ToR11# set policy-options policy-statement TEST then community add NO-EXPORT
    user@ToR11# set policy-options policy-statement evpn-pplb from protocol evpn
    user@ToR11# set policy-options policy-statement evpn-pplb then load-balance per-packet

15. Configure EVPN routing instances for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@ToR11# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.81
    user@ToR11# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@ToR11# set routing-instances EVPN-VXLAN-1 interface ge-1/0/6.0
    user@ToR11# set routing-instances EVPN-VXLAN-1 interface ae0.0
    user@ToR11# set routing-instances EVPN-VXLAN-1 route-distinguisher 192.0.2.11:1
    user@ToR11# set routing-instances EVPN-VXLAN-1 vrf-target target:1:1
    user@ToR11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file TOR11-EVPN-VXLAN-1.log
    user@ToR11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@ToR11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@ToR11# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@ToR11# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@ToR11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5

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 in the CLI User Guide.

Configure the MX router ToR12:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set system host-name ToR12
   

2. Configure the interfaces and bridge domains on the CE-1 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set logical-systems CE-1 interfaces ge-1/0/9 unit 0 description "CONNECTED TO Host 1"
   user@ToR12# set logical-systems CE-1 interfaces ge-1/0/9 unit 0 family bridge interface-mode trunk
   user@ToR12# set logical-systems CE-1 interfaces ge-1/0/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set logical-systems CE-1 interfaces ae1 unit 0 description "CONNECTED TO ToR12"
   user@ToR12# set logical-systems CE-1 interfaces ae1 unit 0 family bridge interface-mode trunk
   user@ToR12# set logical-systems CE-1 interfaces ae1 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set logical-systems CE-1 bridge-domains BD-1 domain-type bridge
   user@ToR12# set logical-systems CE-1 bridge-domains BD-1 vlan-id 1
   user@ToR12# set logical-systems CE-1 bridge-domains BD-2 domain-type bridge
   user@ToR12# set logical-systems CE-1 bridge-domains BD-2 vlan-id 2
   user@ToR12# set logical-systems CE-1 bridge-domains BD-3 domain-type bridge
   user@ToR12# set logical-systems CE-1 bridge-domains BD-3 vlan-id 3
   user@ToR12# set logical-systems CE-1 bridge-domains BD-4 domain-type bridge
   user@ToR12# set logical-systems CE-1 bridge-domains BD-4 vlan-id 4
   user@ToR12# set logical-systems CE-1 bridge-domains BD-5 domain-type bridge
   user@ToR12# set logical-systems CE-1 bridge-domains BD-5 vlan-id 5
   

3. Configure the interfaces and bridge domains on the CE-3 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/7 unit 0 description "CONNECTED TO ToR12"
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/7 unit 0 family bridge interface-mode trunk
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/7 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/9 unit 0 description "CONNECTED TO Host 3"
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/9 unit 0 family bridge interface-mode trunk
   user@ToR12# set logical-systems CE-3 interfaces ge-1/1/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set logical-systems CE-3 bridge-domains BD-1 domain-type bridge
   user@ToR12# set logical-systems CE-3 bridge-domains BD-1 vlan-id 1
   user@ToR12# set logical-systems CE-3 bridge-domains BD-2 domain-type bridge
   user@ToR12# set logical-systems CE-3 bridge-domains BD-2 vlan-id 2
   user@ToR12# set logical-systems CE-3 bridge-domains BD-3 domain-type bridge
   user@ToR12# set logical-systems CE-3 bridge-domains BD-3 vlan-id 3
   user@ToR12# set logical-systems CE-3 bridge-domains BD-4 domain-type bridge
   user@ToR12# set logical-systems CE-3 bridge-domains BD-4 vlan-id 4
   user@ToR12# set logical-systems CE-3 bridge-domains BD-5 domain-type bridge
   user@ToR12# set logical-systems CE-3 bridge-domains BD-5 vlan-id 5

4. Configure trace options for the interfaces to enable trace logs.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set interfaces traceoptions file ToR12-DCD.log
   user@ToR12# set interfaces traceoptions file size 10m
   user@ToR12# set interfaces traceoptions flag all

5. Set the number of aggregated Ethernet interfaces.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set chassis aggregated-devices ethernet device-count 2
   

6. Configure the interfaces on the ToR12 device to connect to the MX12, CE-2, CE-3, ToR11, and MX11 devices to enable underlay connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set interfaces ge-1/0/0 unit 0 description "CONNECTED TO MX11"
   user@ToR12# set interfaces ge-1/0/0 unit 0 family inet address 192.168.6.1/24
   user@ToR12# set interfaces ge-1/0/4 unit 0 description "CONNECTED TO MX12"
   user@ToR12# set interfaces ge-1/0/4 unit 0 family inet address 192.168.5.1/24
   user@ToR12# set interfaces ge-1/0/6 description "CONNECTED TO CE-1"
   user@ToR12# set interfaces ge-1/0/6 gigether-options 802.3ad ae0
   user@ToR12# set interfaces ge-1/0/7 unit 0 description "CONNECTED TO CE-3"
   user@ToR12# set interfaces ge-1/0/7 unit 0 family bridge interface-mode trunk
   user@ToR12# set interfaces ge-1/0/7 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set interfaces ge-1/1/0 description "CONNECTED TO ToR11"
   user@ToR12# set interfaces ge-1/1/0 gigether-options 802.3ad ae1
   user@ToR12# set interfaces ge-1/1/3 unit 0 description "CONNECTED TO ToR11"
   user@ToR12# set interfaces ge-1/1/3 unit 0 family inet address 192.168.2.2/24
   user@ToR12# set interfaces ge-1/1/6 description "CONNECTED TO ToR12"
   user@ToR12# set interfaces ge-1/1/6 gigether-options 802.3ad ae1

7. Configure a Link Aggregation Control Protocol (LACP)-enabled link aggregation group (LAG) interface towards the CE-1 end host device. The ESI value is globally unique across the entire EVPN domain. The all-active configuration enables ToR11 and ToR12 to forward traffic to, and from the CE devices, such that all CE links are actively used.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set interfaces ae0 esi 00:11:11:11:11:11:11:11:11:11
   user@ToR12# set interfaces ae0 esi all-active
   user@ToR12# set interfaces ae0 aggregated-ether-options lacp system-id 11:11:11:11:11:11
   user@ToR12# set interfaces ae0 unit 0 family bridge interface-mode trunk
   user@ToR12# set interfaces ae0 unit 0 family bridge vlan-id-list 1-5
   user@ToR12# set interfaces ae1 aggregated-ether-options lacp active
   user@ToR12# set interfaces ae1 aggregated-ether-options lacp periodic fast

8. Configure the loopback interface address and routing options.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set interfaces lo0 unit 82 family inet address 192.0.2.12/32
   user@ToR12# set routing-options router-id 192.0.2.12
   user@ToR12# set routing-options autonomous-system 65200
   

9. Apply the load balancing policy to the forwarding table.

   content_copy zoom_out_map

   [edit]
   user@ToR12# set routing-options forwarding-table export evpn-pplb

10. Configure the external BGP (EBGP) underlay connectivity between the ToR (ToR12 and ToR11) and gateway routers (MX11 and MX12).

    content_copy zoom_out_map

    [edit]
    user@ToR12# set protocols bgp local-as 65200
    user@ToR12# set protocols bgp group MX11 type external
    user@ToR12# set protocols bgp group MX11 local-address 192.168.6.1
    user@ToR12# set protocols bgp group MX11 export LO
    user@ToR12# set protocols bgp group MX11 export TEST
    user@ToR12# set protocols bgp group MX11 peer-as 65400
    user@ToR12# set protocols bgp group MX11 local-as 65200
    user@ToR12# set protocols bgp group MX11 neighbor 192.168.6.2 family inet unicast
    user@ToR12# set protocols bgp group MX12 type external
    user@ToR12# set protocols bgp group MX12 local-address 192.168.5.1
    user@ToR12# set protocols bgp group MX12 export LO
    user@ToR12# set protocols bgp group MX12 export TEST
    user@ToR12# set protocols bgp group MX12 peer-as 65500
    user@ToR12# set protocols bgp group MX12 local-as 65200
    user@ToR12# set protocols bgp group MX12 neighbor 192.168.5.2 family inet unicast
    user@ToR12# set protocols bgp group ToR11 type external
    user@ToR12# set protocols bgp group ToR11 local-address 192.168.2.2
    user@ToR12# set protocols bgp group ToR11 export LO
    user@ToR12# set protocols bgp group ToR11 export TEST
    user@ToR12# set protocols bgp group ToR11 peer-as 65100
    user@ToR12# set protocols bgp group ToR11 local-as 65200
    user@ToR12# set protocols bgp group ToR11 neighbor 192.168.2.1 family inet unicast

11. Configure a multiprotocol external BGP (MP-EBGP) overlay between the ToR (ToR12 and ToR11) and gateway routers (MX11 and MX12) and set EVPN as the signaling protocol.

    Step-by-Step Procedure

    1. Configure a MP-EBGP overlay to connect between ToR12 and MX11 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR12# set protocols bgp group MX11-EVPN type external
       user@ToR12# set protocols bgp group MX11-EVPN multihop ttl 2
       user@ToR12# set protocols bgp group MX11-EVPN multihop no-nexthop-change
       user@ToR12# set protocols bgp group MX11-EVPN local-address 192.0.2.12
       user@ToR12# set protocols bgp group MX11-EVPN export TEST
       user@ToR12# set protocols bgp group MX11-EVPN peer-as 65400
       user@ToR12# set protocols bgp group MX11-EVPN local-as 65200
       user@ToR12# set protocols bgp group MX11-EVPN neighbor 192.0.2.21 family evpn signaling

    2. Configure a MP-EBGP overlay to connect between ToR12 and MX12 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR12# set protocols bgp group MX12-EVPN type external
       user@ToR12# set protocols bgp group MX12-EVPN multihop ttl 2
       user@ToR12# set protocols bgp group MX12-EVPN multihop no-nexthop-change
       user@ToR12# set protocols bgp group MX12-EVPN local-address 192.0.2.12
       user@ToR12# set protocols bgp group MX12-EVPN export TEST
       user@ToR12# set protocols bgp group MX12-EVPN peer-as 65500
       user@ToR12# set protocols bgp group MX12-EVPN local-as 65200
       user@ToR12# set protocols bgp group MX12-EVPN neighbor 192.0.2.22 family evpn signaling

    3. Configure a MP-EBGP overlay to connect between ToR12 and ToR11 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR12# set protocols bgp group ToR11-EVPN type external
       user@ToR12# set protocols bgp group ToR11-EVPN multihop ttl 2
       user@ToR12# set protocols bgp group ToR11-EVPN multihop no-nexthop-change
       user@ToR12# set protocols bgp group ToR11-EVPN local-address 192.0.2.12
       user@ToR12# set protocols bgp group ToR11-EVPN export TEST
       user@ToR12# set protocols bgp group ToR11-EVPN peer-as 65100
       user@ToR12# set protocols bgp group ToR11-EVPN local-as 65200
       user@ToR12# set protocols bgp group ToR11-EVPN neighbor 192.0.2.11 family evpn signaling
       user@ToR12# set protocols bgp group ToR12-EVPN export TEST

12. Configure trace operations to track all Layer 2 address learning and forwarding properties.

    content_copy zoom_out_map

    [edit]
    user@ToR12# set protocols l2-learning traceoptions file TOR12-L2ALD.log
    user@ToR12# set protocols l2-learning traceoptions file size 10m
    user@ToR12# set protocols l2-learning traceoptions level all
    user@ToR12# set protocols l2-learning traceoptions flag all

13. Configure routing policy to accept the direct loopback address route.

    content_copy zoom_out_map

    [edit]
    user@ToR12# set policy-options policy-statement LO term 1 from protocol direct
    user@ToR12# set policy-options policy-statement LO term 1 from route-filter 192.0.2.12/32 exact
    user@ToR12# set policy-options policy-statement LO term 1 then accept
    

14. Configure the NO-EXPORT community.

    content_copy zoom_out_map

    [edit]
    user@ToR12# set policy-options community NO-EXPORT members no-advertise
    user@ToR12# set policy-options community NO-EXPORT members no-export
    user@ToR12# set policy-options community NO-EXPORT members no-export-subconfed
    

15. Configure the load balancing and TEST policies.

    content_copy zoom_out_map

    [edit]
    user@ToR12# set policy-options policy-statement TEST then community add NO-EXPORT
    user@ToR12# set policy-options policy-statement evpn-pplb from protocol evpn
    user@ToR12# set policy-options policy-statement evpn-pplb then load-balance per-packet

16. Configure EVPN routing instances for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@ToR12# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.82
    user@ToR12# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@ToR12# set routing-instances EVPN-VXLAN-1 interface ge-1/0/7.0
    user@ToR12# set routing-instances EVPN-VXLAN-1 interface ae0.0
    user@ToR12# set routing-instances EVPN-VXLAN-1 route-distinguisher 192.0.2.12:1
    user@ToR12# set routing-instances EVPN-VXLAN-1 vrf-target target:1:1
    user@ToR12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file TOR12-EVPN-VXLAN-1.log
    user@ToR12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@ToR12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@ToR12# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@ToR12# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@ToR12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5

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 in the CLI User Guide.

Configure an MX Series router as the data center gateway and WAN edge router and name it as MX11:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@MX11# set system host-name MX11
   

2. Configure the interfaces on the MX11 router (DC GW/WAN Edge1) to enable the underlay connectivity to the MX12, ToR11, ToR12, and P devices, which is the EVPN-VXLAN part of DC1 network.

   content_copy zoom_out_map

   [edit]
   user@MX11# set interfaces ge-1/1/1 unit 0 description "CONNECTED TO ToR11"
   user@MX11# set interfaces ge-1/1/1 unit 0 family inet address 192.168.3.2/24
   user@MX11# set interfaces ge-5/1/0 unit 0 description "CONNECTED TO MX12"
   user@MX11# set interfaces ge-5/1/0 unit 0 family inet address 192.168.7.1/24
   user@MX11# set interfaces ge-5/1/8 unit 0 description "CONNECTED TO ToR12"
   user@MX11# set interfaces ge-5/1/8 unit 0 family inet address 192.168.6.2/24
   user@MX11# set interfaces ge-5/1/9 unit 0 description "CONNECTED TO P"
   user@MX11# set interfaces ge-5/1/9 unit 0 family inet address 203.0.1.1/24
   user@MX11# set interfaces ge-5/1/9 unit 0 family mpls

3. Configure external BGP (EBGP) underlay connectivity between the gateway routers (MX11 and MX12) and ToR (ToR11 and ToR12).

   content_copy zoom_out_map

   [edit]
   user@MX11# set protocols bgp group MX12 type external
   user@MX11# set protocols bgp group MX12 local-address 192.168.7.1
   user@MX11# set protocols bgp group MX12 export TEST
   user@MX11# set protocols bgp group MX12 export LO
   user@MX11# set protocols bgp group MX12 peer-as 65500
   user@MX11# set protocols bgp group MX12 local-as 65400
   user@MX11# set protocols bgp group MX12 neighbor 192.168.7.2 family inet unicast
   user@MX11# set protocols bgp group ToR11 type external
   user@MX11# set protocols bgp group ToR11 local-address 192.168.3.2
   user@MX11# set protocols bgp group ToR11 import TEST
   user@MX11# set protocols bgp group ToR11 export TEST
   user@MX11# set protocols bgp group ToR11 export LO
   user@MX11# set protocols bgp group ToR11 peer-as 65100
   user@MX11# set protocols bgp group ToR11 local-as 65400
   user@MX11# set protocols bgp group ToR11 neighbor 192.168.3.1 family inet unicast
   user@MX11# set protocols bgp group ToR12 type external
   user@MX11# set protocols bgp group ToR12 local-address 192.168.6.2
   user@MX11# set protocols bgp group ToR12 export TEST
   user@MX11# set protocols bgp group ToR12 export LO
   user@MX11# set protocols bgp group ToR12 peer-as 65200
   user@MX11# set protocols bgp group ToR12 local-as 65400
   user@MX11# set protocols bgp group ToR12 neighbor 192.168.6.1 family inet unicast
   

4. Configure a multiprotocol external BGP (MP-EBGP) overlay connectivity between the gateway routers (MX11 and MX12) and ToR (ToR11 and ToR12) and set EVPN as the signaling protocol.

   content_copy zoom_out_map

   [edit]
   user@MX11# set protocols bgp group MX12-EVPN type external
   user@MX11# set protocols bgp group MX12-EVPN multihop ttl 2
   user@MX11# set protocols bgp group MX12-EVPN multihop no-nexthop-change
   user@MX11# set protocols bgp group MX12-EVPN local-address 192.0.2.21
   user@MX11# set protocols bgp group MX12-EVPN export TEST
   user@MX11# set protocols bgp group MX12-EVPN peer-as 65500
   user@MX11# set protocols bgp group MX12-EVPN local-as 65400
   user@MX11# set protocols bgp group MX12-EVPN neighbor 192.0.2.22 family evpn signaling
   user@MX11# set protocols bgp group ToR11-EVPN type external
   user@MX11# set protocols bgp group ToR11-EVPN multihop ttl 2
   user@MX11# set protocols bgp group ToR11-EVPN multihop no-nexthop-change
   user@MX11# set protocols bgp group ToR11-EVPN local-address 192.0.2.21
   user@MX11# set protocols bgp group ToR11-EVPN export TEST
   user@MX11# set protocols bgp group ToR11-EVPN peer-as 65100
   user@MX11# set protocols bgp group ToR11-EVPN local-as 65400
   user@MX11# set protocols bgp group ToR11-EVPN neighbor 192.0.2.11 family evpn signaling
   user@MX11# set protocols bgp group ToR12-EVPN type external
   user@MX11# set protocols bgp group ToR12-EVPN multihop ttl 2
   user@MX11# set protocols bgp group ToR12-EVPN multihop no-nexthop-change
   user@MX11# set protocols bgp group ToR12-EVPN local-address 192.0.2.21
   user@MX11# set protocols bgp group ToR12-EVPN export TEST
   user@MX11# set protocols bgp group ToR12-EVPN peer-as 65200
   user@MX11# set protocols bgp group ToR12-EVPN local-as 65400
   user@MX11# set protocols bgp group ToR12-EVPN neighbor 192.0.2.12 family evpn signaling
   

5. Configure integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

   Step-by-Step Procedure

   1. The following is the IRB gateway configuration for the VLAN-1 on MX11 (which is the host part of VLAN-1):

      content_copy zoom_out_map

      [edit]
      user@MX11# set interfaces irb unit 1 proxy-macip-advertisement
      user@MX11# set interfaces irb unit 1 virtual-gateway-esi 00:11:aa:aa:aa:aa:aa:aa:aa:aa
      user@MX11# set interfaces irb unit 1 virtual-gateway-esi all-active
      user@MX11# set interfaces irb unit 1 family inet address 10.11.1.12/24 virtual-gateway-address 10.11.1.10
      

   2. The following is the IRB gateway configuration for the VLAN-2 on MX11 (which is the host part of VLAN-2):

      content_copy zoom_out_map

      [edit]
      user@MX11# set interfaces irb unit 2 proxy-macip-advertisement
      user@MX11# set interfaces irb unit 2 virtual-gateway-esi 00:11:bb:bb:bb:bb:bb:bb:bb:bb
      user@MX11# set interfaces irb unit 2 virtual-gateway-esi all-active
      user@MX11# set interfaces irb unit 2 family inet address 10.12.1.12/24 virtual-gateway-address 10.12.1.10
      

   3. The following is the IRB gateway configuration for the VLAN-3 on MX11 (which is the host part of VLAN-3):

      content_copy zoom_out_map

      [edit]
      user@MX11# set interfaces irb unit 3 proxy-macip-advertisement
      user@MX11# set interfaces irb unit 3 virtual-gateway-esi 00:11:cc:cc:cc:cc:cc:cc:cc:cc
      user@MX11# set interfaces irb unit 3 virtual-gateway-esi all-active
      user@MX11# set interfaces irb unit 3 family inet address 10.13.1.12/24 virtual-gateway-address 10.13.1.10
      

   4. The following is the IRB gateway configuration for the VLAN-4 on MX11 (which is the host part of VLAN-4):

      content_copy zoom_out_map

      [edit]
      user@MX11# set interfaces irb unit 4 proxy-macip-advertisement
      user@MX11# set interfaces irb unit 4 virtual-gateway-esi 00:11:dd:dd:dd:dd:dd:dd:dd:dd
      user@MX11# set interfaces irb unit 4 virtual-gateway-esi all-active
      user@MX11# set interfaces irb unit 4 family inet address 10.14.1.12/24 virtual-gateway-address 10.14.1.10

   5. The following is the IRB gateway configuration for the VLAN-5 on MX11 (which is the host part of VLAN-5):

      content_copy zoom_out_map

      [edit]
      user@MX11# set interfaces irb unit 5 proxy-macip-advertisement
      user@MX11# set interfaces irb unit 5 virtual-gateway-esi 00:11:ee:ee:ee:ee:ee:ee:ee:ee
      user@MX11# set interfaces irb unit 5 virtual-gateway-esi all-active
      user@MX11# set interfaces irb unit 5 family inet address 10.15.1.12/24 virtual-gateway-address 10.15.1.10

6. Configure trace operations to track all Layer 2 address learning and forwarding properties.

   content_copy zoom_out_map

   [edit]
   user@MX11# set protocols l2-learning traceoptions file MX11-L2ALD.log
   user@MX11# set protocols l2-learning traceoptions file size 10m
   user@MX11# set protocols l2-learning traceoptions level all
   user@MX11# set protocols l2-learning traceoptions flag all

7. Configure routing policy to accept the direct loopback address route.

   content_copy zoom_out_map

   [edit]
   user@MX11# set policy-options policy-statement LO from protocol direct
   user@MX11# set policy-options policy-statement LO from route-filter 192.0.2.21/32 exact
   user@MX11# set policy-options policy-statement LO then accept

8. Configure the NO-EXPORT community.

   content_copy zoom_out_map

   [edit]
   user@MX11# set policy-options community NO-EXPORT members no-advertise
   user@MX11# set policy-options community NO-EXPORT members no-export
   user@MX11# set policy-options community NO-EXPORT members no-export-subconfed

9. Configure the load balancing and TEST policies.

   content_copy zoom_out_map

   [edit]
   user@MX11# set policy-options policy-statement TEST then community add NO-EXPORT
   user@MX11# set policy-options policy-statement evpn-pplb from protocol evpn
   user@MX11# set policy-options policy-statement evpn-pplb then load-balance per-packet

10. Configure an ESI value on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

    content_copy zoom_out_map

    [edit]
    user@MX11# set interfaces lt-5/1/0 esi 00:22:22:22:22:22:22:22:22:22

11. Configure active-active multihoming on the logical tunnel interface by including the all-active statement.

    content_copy zoom_out_map

    [edit]
    user@MX11# set interfaces lt-5/1/0 esi all-active

12. Configure a pair of logical tunnel (lt-) interfaces on the MX11 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

    content_copy zoom_out_map

    [edit]
    user@MX11# set interfaces lt-5/1/0 unit 0 peer-unit 1
    user@MX11# set interfaces lt-5/1/0 unit 0 family bridge interface-mode trunk
    user@MX11# set interfaces lt-5/1/0 unit 0 family bridge vlan-id-list 1-5
    user@MX11# set interfaces lt-5/1/0 unit 1 peer-unit 0
    user@MX11# set interfaces lt-5/1/0 unit 1 family bridge interface-mode trunk
    user@MX11# set interfaces lt-5/1/0 unit 1 family bridge vlan-id-list 1-5

13. Configure the loopback interface address and routing options.

    content_copy zoom_out_map

    [edit]
    user@MX11# set interfaces lo0 unit 84 family inet address 192.0.2.21/32
    user@MX11# set interfaces lo0 unit 84 family mpls
    user@MX11# set routing-options router-id 192.0.2.21
    user@MX11# set routing-options autonomous-system 65300

14. Apply the load balancing policy to the forwarding table.

    content_copy zoom_out_map

    [edit]
    user@MX11# set routing-options forwarding-table export evpn-pplb

15. Enable RSVP, MPLS, BGP, and OSPF protocols on the core interfaces. Create MPLS LSPs and specify the address of the other gateway and WAN edge routers (MX12, P, MX21, MX22).

    content_copy zoom_out_map

    [edit]
    user@MX11# set protocols rsvp interface all
    user@MX11# set protocols rsvp interface fxp0.0 disable
    user@MX11# set protocols mpls label-switched-path MX11-TO-MX12 to 192.0.2.22
    user@MX11# set protocols mpls label-switched-path MX11-TO-P to 203.0.113.1
    user@MX11# set protocols mpls label-switched-path MX11-TO-MX21 to 198.51.100.21
    user@MX11# set protocols mpls label-switched-path MX11-TO-MX22 to 198.51.100.22
    user@MX11# set protocols mpls interface all
    user@MX11# set protocols mpls interface fxp0.0 disable
    user@MX11# set protocols bgp local-address 192.0.2.21
    user@MX11# set protocols bgp local-as 65300
    user@MX11# set protocols bgp group INT type internal
    user@MX11# set protocols bgp group INT local-address 192.0.2.21
    user@MX11# set protocols bgp group INT family evpn signaling
    user@MX11# set protocols bgp group INT export TEST
    user@MX11# set protocols bgp group INT neighbor 203.0.113.1
    user@MX11# set protocols ospf traffic-engineering
    user@MX11# set protocols ospf area 0.0.0.0 interface ge-5/1/9.0
    user@MX11# set protocols ospf area 0.0.0.0 interface lo0.84 passive

16. Configure EVPN-based MPLS routing instances on the MX11 router for each virtual network. Define the route distinguisher (used to identify and advertise EVPN-MPLS routes) and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure a bridge domain for each virtual router that maps VLAN IDs.

    content_copy zoom_out_map

    [edit]
    user@MX11# set routing-instances EVPN-MPLS-1 instance-type virtual-switch
    user@MX11# set routing-instances EVPN-MPLS-1 interface lt-5/1/0.0
    user@MX11# set routing-instances EVPN-MPLS-1 route-distinguisher 192.0.2.21:100
    user@MX11# set routing-instances EVPN-MPLS-1 vrf-target target:1:2
    user@MX11# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file MX11-EVPN-MPLS-1.log
    user@MX11# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file size 10m
    user@MX11# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions flag all
    user@MX11# set routing-instances EVPN-MPLS-1 protocols evpn extended-vlan-list 1-5
    user@MX11# set routing-instances EVPN-MPLS-1 protocols evpn default-gateway no-gateway-community
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 domain-type bridge
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 vlan-id 1
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 domain-type bridge
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 vlan-id 2
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 domain-type bridge
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 vlan-id 3
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 domain-type bridge
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 vlan-id 4
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 domain-type bridge
    user@MX11# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 vlan-id 5
    

17. Configure EVPN-VXLAN routing instances on the MX11 router for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@MX11# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.84
    user@MX11# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@MX11# set routing-instances EVPN-VXLAN-1 interface lt-5/1/0.1
    user@MX11# set routing-instances EVPN-VXLAN-1 route-distinguisher 192.0.2.21:1
    user@MX11# set routing-instances EVPN-VXLAN-1 vrf-target target:1:1
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file MX11-EVPN-VXLAN-1.log
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@MX11# set routing-instances EVPN-VXLAN-1 protocols evpn default-gateway no-gateway-community
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 routing-interface irb.1
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 routing-interface irb.2
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 routing-interface irb.3
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 routing-interface irb.4
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 routing-interface irb.5
    user@MX11# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5
    user@MX11# set routing-instances VRF instance-type vrf
    user@MX11# set routing-instances VRF interface irb.1
    user@MX11# set routing-instances VRF interface irb.2
    user@MX11# set routing-instances VRF interface irb.3
    user@MX11# set routing-instances VRF interface irb.4
    user@MX11# set routing-instances VRF interface irb.5
    user@MX11# set routing-instances VRF route-distinguisher 1:1
    user@MX11# set routing-instances VRF vrf-target target:10:10

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 in the CLI User Guide.

Configure an MX Series router as the data center gateway and WAN edge router and name it as MX12:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@MX12# set system host-name MX12
   

2. Configure the P device as the logical system of MX12 data center gateway and WAN edge router.

   Step-by-Step Procedure

   1. Configure the interfaces of the P device.

      content_copy zoom_out_map

      [edit]
      user@MX12# set logical-systems P interfaces ge-1/0/0 unit 0 description "CONNECTED TO MX21"
      user@MX12# set logical-systems P interfaces ge-1/0/0 unit 0 family inet address 203.0.113.32/24
      user@MX12# set logical-systems P interfaces ge-1/0/0 unit 0 family mpls
      user@MX12# set logical-systems P interfaces ge-1/0/2 unit 0 description "CONNECTED TO MX22"
      user@MX12# set logical-systems P interfaces ge-1/0/2 unit 0 family inet address 203.0.113.52/24
      user@MX12# set logical-systems P interfaces ge-1/0/2 unit 0 family mpls
      user@MX12# set logical-systems P interfaces ge-1/1/1 unit 0 description "CONNECTED TO MX11"
      user@MX12# set logical-systems P interfaces ge-1/1/1 unit 0 family inet address 203.0.113.42/24
      user@MX12# set logical-systems P interfaces ge-1/1/1 unit 0 family mpls
      user@MX12# set logical-systems P interfaces ge-1/1/6 unit 0 description "CONNECTED TO MX12"
      user@MX12# set logical-systems P interfaces ge-1/1/6 unit 0 family inet address 203.0.113.12/24
      user@MX12# set logical-systems P interfaces ge-1/1/6 unit 0 family mpls
      

   2. Enable RSVP, MPLS, BGP, and OSPF protocols on the core interfaces of the P device. Create MPLS LSPs and specify the address of the other gateway and WAN edge routers (MX11, MX12, MX21, MX22).

      content_copy zoom_out_map

      [edit]
      user@MX12# set logical-systems P protocols rsvp interface all
      user@MX12# set logical-systems P protocols mpls label-switched-path P-TO-MX11 from 203.0.113.1
      user@MX12# set logical-systems P protocols mpls label-switched-path P-TO-MX11 to 192.0.2.21
      user@MX12# set logical-systems P protocols mpls label-switched-path P-TO-MX12 to 192.0.2.22
      user@MX12# set logical-systems P protocols mpls label-switched-path P-TO-MX21 to 198.51.100.21
      user@MX12# set logical-systems P protocols mpls label-switched-path P-TO-MX22 to 198.51.100.22
      user@MX12# set logical-systems P protocols mpls interface all
      user@MX12# set logical-systems P protocols bgp local-address 203.0.113.1
      user@MX12# set logical-systems P protocols bgp local-as 65300
      user@MX12# set logical-systems P protocols bgp group INT type internal
      user@MX12# set logical-systems P protocols bgp group INT import BLOCK-VXLAN-ROUTES-FROM-CORE
      user@MX12# set logical-systems P protocols bgp group INT family evpn signaling
      user@MX12# set logical-systems P protocols bgp group INT cluster 203.0.113.1
      user@MX12# set logical-systems P protocols bgp group INT neighbor 192.0.2.21
      user@MX12# set logical-systems P protocols bgp group INT neighbor 192.0.2.22
      user@MX12# set logical-systems P protocols bgp group INT neighbor 198.51.100.21
      user@MX12# set logical-systems P protocols bgp group INT neighbor 198.51.100.22
      user@MX12# set logical-systems P protocols ospf traffic-engineering
      user@MX12# set logical-systems P protocols ospf area 0.0.0.0 interface all
      user@MX12# set logical-systems P protocols ospf area 0.0.0.0 interface lo0.86
      

   3. Configure the loopback interface address and routing options.

      content_copy zoom_out_map

      [edit]
      user@MX12# set logical-systems P interfaces lo0 unit 86 family inet address 203.0.113.1/32
      user@MX12# set logical-systems P interfaces lo0 unit 86 family mpls
      user@MX12# set logical-systems P routing-options router-id 203.0.113.1
      user@MX12# set logical-systems P routing-options autonomous-system 65300
      

   4. Configure the routing policy BLOCK-VXLAN-ROUTES-FROM-CORE.

      content_copy zoom_out_map

      [edit]
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 1 from protocol bgp
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 1 from community RT-CORE
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 1 then accept
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 2 from protocol bgp
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 2 from community RT-DC1
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 2 then reject
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 3 from protocol bgp
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 3 from community RT-DC2
      user@MX12# set logical-systems P policy-options policy-statement BLOCK-VXLAN-ROUTES-FROM-CORE term 3 then reject

   5. Configure the RT-CORE, RT-DC1 and RT-DC2 communities.

      content_copy zoom_out_map

      [edit]
      user@MX12# set logical-systems P policy-options community RT-CORE members target:1:2
      user@MX12# set logical-systems P policy-options community RT-DC1 members target:1:1
      user@MX12# set logical-systems P policy-options community RT-DC2 members target:1:3
      

   6. Configure trace options for the interfaces to enable trace logs.

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces traceoptions file MX12-DCD.log
      user@MX12# set interfaces traceoptions file size 10m
      user@MX12# set interfaces traceoptions flag all

3. Configure the interfaces on the MX12 router (DC GW/WAN Edge 2) to enable the underlay connectivity to the MX11, ToR12, ToR11, and P devices, which is the EVPN-VXLAN part of DC1 network.

   content_copy zoom_out_map

   [edit]
   user@MX12# set interfaces ge-1/0/4 unit 0 description "CONNECTED TO ToR12"
   user@MX12# set interfaces ge-1/0/4 unit 0 family inet address 192.168.5.2/24
   user@MX12# set interfaces ge-1/0/5 unit 0 description "CONNECTED TO TOR11"
   user@MX12# set interfaces ge-1/0/5 unit 0 family inet address 192.168.4.2/24
   user@MX12# set interfaces ge-1/0/6 unit 0 description "CONNECTED TO P"
   user@MX12# set interfaces ge-1/0/6 unit 0 family inet address 203.0.113.11/24
   user@MX12# set interfaces ge-1/0/6 unit 0 family mpls
   user@MX12# set interfaces ge-1/1/0 unit 0 description "CONNECTED TO MX11"
   user@MX12# set interfaces ge-1/1/0 unit 0 family inet address 192.168.7.2/24

4. Configure external BGP (EBGP) underlay connectivity between the gateway routers (MX11 and MX12) and ToR (ToR11 and ToR12).

   content_copy zoom_out_map

   [edit]
   user@MX12# set protocols bgp group MX11 type external
   user@MX12# set protocols bgp group MX11 local-address 192.168.7.2
   user@MX12# set protocols bgp group MX11 export TEST
   user@MX12# set protocols bgp group MX11 export LO
   user@MX12# set protocols bgp group MX11 peer-as 65400
   user@MX12# set protocols bgp group MX11 local-as 65500
   user@MX12# set protocols bgp group MX11 neighbor 192.168.7.1 family inet unicast
   user@MX12# set protocols bgp group ToR11 type external
   user@MX12# set protocols bgp group ToR11 local-address 192.168.4.2
   user@MX12# set protocols bgp group ToR11 export TEST
   user@MX12# set protocols bgp group ToR11 export LO
   user@MX12# set protocols bgp group ToR11 peer-as 65100
   user@MX12# set protocols bgp group ToR11 local-as 65500
   user@MX12# set protocols bgp group ToR11 neighbor 192.168.4.1 family inet unicast
   user@MX12# set protocols bgp group ToR12 type external
   user@MX12# set protocols bgp group ToR12 local-address 192.168.5.2
   user@MX12# set protocols bgp group ToR12 export TEST
   user@MX12# set protocols bgp group ToR12 export LO
   user@MX12# set protocols bgp group ToR12 peer-as 65200
   user@MX12# set protocols bgp group ToR12 local-as 65500
   user@MX12# set protocols bgp group ToR12 neighbor 192.168.5.1 family inet unicast
   

5. Configure a multiprotocol external BGP (MP-EBGP) overlay connectivity between the gateway routers (MX11 and MX12) and ToR (ToR11 and ToR12) and set EVPN as the signaling protocol.

   content_copy zoom_out_map

   [edit]
   user@MX12# set protocols bgp group MX11-EVPN type external
   user@MX12# set protocols bgp group MX11-EVPN multihop ttl 2
   user@MX12# set protocols bgp group MX11-EVPN multihop no-nexthop-change
   user@MX12# set protocols bgp group MX11-EVPN local-address 192.0.2.22
   user@MX12# set protocols bgp group MX11-EVPN export TEST
   user@MX12# set protocols bgp group MX11-EVPN peer-as 65400
   user@MX12# set protocols bgp group MX11-EVPN local-as 65500
   user@MX12# set protocols bgp group MX11-EVPN neighbor 192.0.2.21 family evpn signaling
   user@MX12# set protocols bgp group ToR11-EVPN type external
   user@MX12# set protocols bgp group ToR11-EVPN multihop ttl 2
   user@MX12# set protocols bgp group ToR11-EVPN multihop no-nexthop-change
   user@MX12# set protocols bgp group ToR11-EVPN local-address 192.0.2.22
   user@MX12# set protocols bgp group ToR11-EVPN export TEST
   user@MX12# set protocols bgp group ToR11-EVPN peer-as 65100
   user@MX12# set protocols bgp group ToR11-EVPN local-as 65500
   user@MX12# set protocols bgp group ToR11-EVPN neighbor 192.0.2.11 family evpn signaling
   user@MX12# set protocols bgp group ToR12-EVPN type external
   user@MX12# set protocols bgp group ToR12-EVPN multihop ttl 2
   user@MX12# set protocols bgp group ToR12-EVPN multihop no-nexthop-change
   user@MX12# set protocols bgp group ToR12-EVPN local-address 192.0.2.22
   user@MX12# set protocols bgp group ToR12-EVPN export TEST
   user@MX12# set protocols bgp group ToR12-EVPN peer-as 65200
   user@MX12# set protocols bgp group ToR12-EVPN local-as 65500
   user@MX12# set protocols bgp group ToR12-EVPN neighbor 192.0.2.12 family evpn signaling
   

6. Configure integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

   Step-by-Step Procedure

   1. The following is the IRB gateway configuration for the VLAN-1 on MX12 (which is the host part of VLAN-1):

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces irb unit 1 proxy-macip-advertisement
      user@MX12# set interfaces irb unit 1 virtual-gateway-esi 00:11:aa:aa:aa:aa:aa:aa:aa:aa
      user@MX12# set interfaces irb unit 1 virtual-gateway-esi all-active
      user@MX12# set interfaces irb unit 1 family inet address 10.11.1.13/24 virtual-gateway-address 10.11.1.10
      

   2. The following is the IRB gateway configuration for the VLAN-2 on MX12 (which is the host part of VLAN-2):

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces irb unit 2 proxy-macip-advertisement
      user@MX12# set interfaces irb unit 2 virtual-gateway-esi 00:11:bb:bb:bb:bb:bb:bb:bb:bb
      user@MX12# set interfaces irb unit 2 virtual-gateway-esi all-active
      user@MX12# set interfaces irb unit 2 family inet address 10.12.1.13/24 virtual-gateway-address 10.12.1.10
      

   3. The following is the IRB gateway configuration for the VLAN-3 on MX12 (which is the host part of VLAN-3):

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces irb unit 3 proxy-macip-advertisement
      user@MX12# set interfaces irb unit 3 virtual-gateway-esi 00:11:cc:cc:cc:cc:cc:cc:cc:cc
      user@MX12# set interfaces irb unit 3 virtual-gateway-esi all-active
      user@MX12# set interfaces irb unit 3 family inet address 10.13.1.13/24 virtual-gateway-address 10.13.1.10
      

   4. The following is the IRB gateway configuration for the VLAN-4 on MX12 (which is the host part of VLAN-4):

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces irb unit 4 proxy-macip-advertisement
      user@MX12# set interfaces irb unit 4 virtual-gateway-esi 00:11:dd:dd:dd:dd:dd:dd:dd:dd
      user@MX12# set interfaces irb unit 4 virtual-gateway-esi all-active
      user@MX12# set interfaces irb unit 4 family inet address 10.14.1.13/24 virtual-gateway-address 10.14.1.10
      

   5. The following is the IRB gateway configuration for the VLAN-5 on MX12 (which is the host part of VLAN-5):

      content_copy zoom_out_map

      [edit]
      user@MX12# set interfaces irb unit 5 proxy-macip-advertisement
      user@MX12# set interfaces irb unit 5 virtual-gateway-esi 00:11:ee:ee:ee:ee:ee:ee:ee:ee
      user@MX12# set interfaces irb unit 5 virtual-gateway-esi all-active
      user@MX12# set interfaces irb unit 5 family inet address 10.15.1.13/24 virtual-gateway-address 10.15.1.10
      

7. Configure trace operations to track all Layer 2 address learning and forwarding properties.

   content_copy zoom_out_map

   [edit]
   user@MX12# set protocols l2-learning traceoptions file MX12-L2ALD.log
   user@MX12# set protocols l2-learning traceoptions file size 10m
   user@MX12# set protocols l2-learning traceoptions level all
   user@MX12# set protocols l2-learning traceoptions flag all
   

8. Configure routing policy to accept the direct loopback address route.

   content_copy zoom_out_map

   [edit]
   user@MX12# set policy-options policy-statement LO from protocol direct
   user@MX12# set policy-options policy-statement LO from route-filter 192.0.2.22/32 exact
   user@MX12# set policy-options policy-statement LO then accept
   

9. Configure the NO-EXPORT community.

   content_copy zoom_out_map

   [edit]
   user@MX12# set policy-options community NO-EXPORT members no-advertise
   user@MX12# set policy-options community NO-EXPORT members no-export
   user@MX12# set policy-options community NO-EXPORT members no-export-subconfed
   

10. Configure the load balancing and TEST policies.

    content_copy zoom_out_map

    [edit]
    user@MX12# set policy-options policy-statement TEST then community add NO-EXPORT
    user@MX12# set policy-options policy-statement evpn-pplb from protocol evpn
    user@MX12# set policy-options policy-statement evpn-pplb then load-balance per-packet
    

11. Configure an ESI value on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

    content_copy zoom_out_map

    [edit]
    user@MX12# set interfaces lt-1/0/0 esi 00:22:22:22:22:22:22:22:22:22
    

12. Configure active-active multihoming on the logical tunnel interface by including the all-active statement.

    content_copy zoom_out_map

    [edit]
    user@MX12# set interfaces lt-1/0/0 esi all-active
    

13. Configure a pair of logical tunnel (lt-) interfaces on the MX12 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

    content_copy zoom_out_map

    [edit]
    user@MX12# set interfaces lt-1/0/0 unit 0 peer-unit 1
    user@MX12# set interfaces lt-1/0/0 unit 0 family bridge interface-mode trunk
    user@MX12# set interfaces lt-1/0/0 unit 0 family bridge vlan-id-list 1-5
    user@MX12# set interfaces lt-1/0/0 unit 1 peer-unit 0
    user@MX12# set interfaces lt-1/0/0 unit 1 family bridge interface-mode trunk
    user@MX12# set interfaces lt-1/0/0 unit 1 family bridge vlan-id-list 1-5
    

14. Configure the loopback interface address and routing options.

    content_copy zoom_out_map

    [edit]
    user@MX12# set interfaces lo0 unit 85 family inet address 192.0.2.22/32
    user@MX12# set interfaces lo0 unit 85 family mpls
    user@MX12# set routing-options router-id 192.0.2.22
    user@MX12# set routing-options autonomous-system 65300
    

15. Apply the load balancing policy to the forwarding table.

    content_copy zoom_out_map

    [edit]
    user@MX12# set routing-options forwarding-table export evpn-pplb
    

16. Enable RSVP, MPLS, BGP, and OSPF protocols on the core interfaces. Create MPLS LSPs and specify the address of the other gateway and WAN edge routers (MX11, MX21, P, MX22).

    content_copy zoom_out_map

    [edit]
    user@MX12# set protocols rsvp interface all
    user@MX12# set protocols rsvp interface fxp0.0 disable
    user@MX12# set protocols mpls label-switched-path MX12-TO-MX11 to 192.0.2.21
    user@MX12# set protocols mpls label-switched-path MX12-TO-P to 203.0.113.1
    user@MX12# set protocols mpls label-switched-path MX12-TO-MX21 to 198.51.100.21
    user@MX12# set protocols mpls label-switched-path MX12-TO-MX22 to 198.51.100.22
    user@MX12# set protocols mpls interface all
    user@MX12# set protocols mpls interface fxp0.0 disable
    user@MX12# set protocols bgp local-address 192.0.2.22
    user@MX12# set protocols bgp local-as 65300
    user@MX12# set protocols bgp group INT type internal
    user@MX12# set protocols bgp group INT family evpn signaling
    user@MX12# set protocols bgp group INT export TEST
    user@MX12# set protocols bgp group INT neighbor 203.0.113.1
    user@MX12# set protocols ospf traffic-engineering
    user@MX12# set protocols ospf area 0.0.0.0 interface ge-1/0/6.0
    user@MX12# set protocols ospf area 0.0.0.0 interface lo0.85 passive
    

17. Configure EVPN-based MPLS routing instances on the MX12 router for each virtual network. Define the route distinguisher (used to identify and advertise EVPN-MPLS routes) and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure a bridge domain for each virtual router that maps VLAN IDs.

    content_copy zoom_out_map

    [edit]
    user@MX12# set routing-instances EVPN-MPLS-1 instance-type virtual-switch
    user@MX12# set routing-instances EVPN-MPLS-1 interface lt-1/0/0.0
    user@MX12# set routing-instances EVPN-MPLS-1 route-distinguisher 192.0.2.22:100
    user@MX12# set routing-instances EVPN-MPLS-1 vrf-target target:1:2
    user@MX12# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file MX12-EVPN-MPLS-1.log
    user@MX12# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file size 10m
    user@MX12# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions flag all
    user@MX12# set routing-instances EVPN-MPLS-1 protocols evpn extended-vlan-list 1-5
    user@MX12# set routing-instances EVPN-MPLS-1 protocols evpn default-gateway no-gateway-community
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 domain-type bridge
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 vlan-id 1
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 domain-type bridge
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 vlan-id 2
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 domain-type bridge
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 vlan-id 3
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 domain-type bridge
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 vlan-id 4
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 domain-type bridge
    user@MX12# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 vlan-id 5
    

18. Configure EVPN-VXLAN routing instances on the MX12 router for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@MX12# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.85
    user@MX12# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@MX12# set routing-instances EVPN-VXLAN-1 interface lt-1/0/0.1
    user@MX12# set routing-instances EVPN-VXLAN-1 route-distinguisher 192.0.2.22:1
    user@MX12# set routing-instances EVPN-VXLAN-1 vrf-target target:1:1
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file MX12-EVPN-VXLAN-1.log
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@MX12# set routing-instances EVPN-VXLAN-1 protocols evpn default-gateway no-gateway-community
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 routing-interface irb.1
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 routing-interface irb.2
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 routing-interface irb.3
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 routing-interface irb.4
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 routing-interface irb.5
    user@MX12# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5
    user@MX12# set routing-instances VRF instance-type vrf
    user@MX12# set routing-instances VRF interface irb.1
    user@MX12# set routing-instances VRF interface irb.2
    user@MX12# set routing-instances VRF interface irb.3
    user@MX12# set routing-instances VRF interface irb.4
    user@MX12# set routing-instances VRF interface irb.5
    user@MX12# set routing-instances VRF route-distinguisher 1:1
    user@MX12# set routing-instances VRF vrf-target target:10:10
    

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 in the CLI User Guide.

Configure an MX Series router as the data center gateway and WAN edge router and name it as MX21:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@MX21# set system host-name MX21
   

2. Configure the interfaces on the MX21 router (DC GW/WAN Edge 3) to enable the underlay connectivity to the MX22, ToR22, ToR21, and P devices, which is the EVPN-VXLAN part of DC2 network.

   content_copy zoom_out_map

   [edit]
   user@MX21# set interfaces ge-3/0/0 unit 0 description "CONNECTED TO MX22"
   user@MX21# set interfaces ge-3/0/0 unit 0 family inet address 192.168.13.1/24
   user@MX21# set interfaces ge-3/1/0 unit 0 description "CONNECTED TO ToR22"
   user@MX21# set interfaces ge-3/1/0 unit 0 family inet address 192.168.8.1/24
   user@MX21# set interfaces ge-5/0/0 unit 0 description "CONNECTED TO P"
   user@MX21# set interfaces ge-5/0/0 unit 0 family inet address 203.0.113.31/24
   user@MX21# set interfaces ge-5/0/0 unit 0 family mpls
   user@MX21# set interfaces ge-5/0/1 unit 0 description "CONNECTED TO ToR21"
   user@MX21# set interfaces ge-5/0/1 unit 0 family inet address 192.168.9.1/24
   

3. Configure external BGP (EBGP) underlay connectivity between the gateway routers (MX21 and MX22) and ToR (ToR21 and ToR22).

   content_copy zoom_out_map

   [edit]
   user@MX21# set protocols bgp group MX22 type external
   user@MX21# set protocols bgp group MX22 local-address 192.168.13.1
   user@MX21# set protocols bgp group MX22 export TEST
   user@MX21# set protocols bgp group MX22 export LO
   user@MX21# set protocols bgp group MX22 peer-as 64900
   user@MX21# set protocols bgp group MX22 local-as 64800
   user@MX21# set protocols bgp group MX22 neighbor 192.168.13.2 family inet unicast
   user@MX21# set protocols bgp group ToR21 type external
   user@MX21# set protocols bgp group ToR21 local-address 192.168.9.1
   user@MX21# set protocols bgp group ToR21 export TEST
   user@MX21# set protocols bgp group ToR21 export LO
   user@MX21# set protocols bgp group ToR21 peer-as 64600
   user@MX21# set protocols bgp group ToR21 local-as 64800
   user@MX21# set protocols bgp group ToR21 neighbor 192.168.9.2 family inet unicast
   user@MX21# set protocols bgp group ToR22 type external
   user@MX21# set protocols bgp group ToR22 local-address 192.168.8.1
   user@MX21# set protocols bgp group ToR22 export TEST
   user@MX21# set protocols bgp group ToR22 export LO
   user@MX21# set protocols bgp group ToR22 peer-as 64700
   user@MX21# set protocols bgp group ToR22 local-as 64800
   user@MX21# set protocols bgp group ToR22 neighbor 192.168.8.2 family inet unicast
   

4. Configure a multiprotocol external BGP (MP-EBGP) overlay connectivity between the gateway routers (MX21 and MX22) and ToR (ToR21 and ToR22) and set EVPN as the signaling protocol.

   content_copy zoom_out_map

   [edit]
   user@MX21# set protocols bgp group MX22-EVPN type external
   user@MX21# set protocols bgp group MX22-EVPN multihop ttl 2
   user@MX21# set protocols bgp group MX22-EVPN multihop no-nexthop-change
   user@MX21# set protocols bgp group MX22-EVPN local-address 198.51.100.21
   user@MX21# set protocols bgp group MX22-EVPN peer-as 64900
   user@MX21# set protocols bgp group MX22-EVPN local-as 64800
   user@MX21# set protocols bgp group MX22-EVPN neighbor 198.51.100.22 family evpn signaling
   user@MX21# set protocols bgp group ToR21-EVPN type external
   user@MX21# set protocols bgp group ToR21-EVPN multihop ttl 2
   user@MX21# set protocols bgp group ToR21-EVPN multihop no-nexthop-change
   user@MX21# set protocols bgp group ToR21-EVPN local-address 198.51.100.21
   user@MX21# set protocols bgp group ToR21-EVPN peer-as 64600
   user@MX21# set protocols bgp group ToR21-EVPN local-as 64800
   user@MX21# set protocols bgp group ToR21-EVPN neighbor 198.51.100.11 family evpn signaling
   user@MX21# set protocols bgp group ToR22-EVPN type external
   user@MX21# set protocols bgp group ToR22-EVPN multihop ttl 2
   user@MX21# set protocols bgp group ToR22-EVPN multihop no-nexthop-change
   user@MX21# set protocols bgp group ToR22-EVPN local-address 198.51.100.21
   user@MX21# set protocols bgp group ToR22-EVPN peer-as 64700
   user@MX21# set protocols bgp group ToR22-EVPN local-as 64800
   user@MX21# set protocols bgp group ToR22-EVPN neighbor 198.51.100.12 family evpn signaling
   

5. Configure integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

   Step-by-Step Procedure

   1. The following is the IRB gateway configuration for the VLAN-1 on MX21 (which is the host part of VLAN-1):

      content_copy zoom_out_map

      [edit]
      user@MX21# set interfaces irb unit 1 proxy-macip-advertisement
      user@MX21# set interfaces irb unit 1 virtual-gateway-esi 00:22:aa:aa:aa:aa:aa:aa:aa:aa
      user@MX21# set interfaces irb unit 1 virtual-gateway-esi all-active
      user@MX21# set interfaces irb unit 1 family inet address 10.11.1.14/24 virtual-gateway-address 10.11.1.11
      

   2. The following is the IRB gateway configuration for the VLAN-2 on MX21 (which is the host part of VLAN-2):

      content_copy zoom_out_map

      [edit]
      user@MX21# set interfaces irb unit 2 proxy-macip-advertisement
      user@MX21# set interfaces irb unit 2 virtual-gateway-esi 00:22:bb:bb:bb:bb:bb:bb:bb:bb
      user@MX21# set interfaces irb unit 2 virtual-gateway-esi all-active
      user@MX21# set interfaces irb unit 2 family inet address 10.12.1.14/24 virtual-gateway-address 10.12.1.11
      

   3. The following is the IRB gateway configuration for the VLAN-3 on MX21 (which is the host part of VLAN-3):

      content_copy zoom_out_map

      [edit]
      user@MX21# set interfaces irb unit 3 proxy-macip-advertisement
      user@MX21# set interfaces irb unit 3 virtual-gateway-esi 00:22:cc:cc:cc:cc:cc:cc:cc:cc
      user@MX21# set interfaces irb unit 3 virtual-gateway-esi all-active
      user@MX21# set interfaces irb unit 3 family inet address 10.13.1.14/24 virtual-gateway-address 10.13.1.11
      

   4. The following is the IRB gateway configuration for the VLAN-4 on MX21 (which is the host part of VLAN-4):

      content_copy zoom_out_map

      [edit]
      user@MX21# set interfaces irb unit 4 proxy-macip-advertisement
      user@MX21# set interfaces irb unit 4 virtual-gateway-esi 00:22:dd:dd:dd:dd:dd:dd:dd:dd
      user@MX21# set interfaces irb unit 4 virtual-gateway-esi all-active
      user@MX21# set interfaces irb unit 4 family inet address 10.14.1.14/24 virtual-gateway-address 10.14.1.11
      

   5. The following is the IRB gateway configuration for the VLAN-5 on MX21 (which is the host part of VLAN-5):

      content_copy zoom_out_map

      [edit]
      user@MX21# set interfaces irb unit 5 proxy-macip-advertisement
      user@MX21# set interfaces irb unit 5 virtual-gateway-esi 00:22:ee:ee:ee:ee:ee:ee:ee:ee
      user@MX21# set interfaces irb unit 5 virtual-gateway-esi all-active
      user@MX21# set interfaces irb unit 5 family inet address 10.15.1.14/24 virtual-gateway-address 10.15.1.11
      

6. Configure trace operations to track all Layer 2 address learning and forwarding properties.

   content_copy zoom_out_map

   [edit]
   user@MX21# set protocols l2-learning traceoptions file MX21-L2ALD.log
   user@MX21# set protocols l2-learning traceoptions file size 10m
   user@MX21# set protocols l2-learning traceoptions level all
   user@MX21# set protocols l2-learning traceoptions flag all
   

7. Configure routing policy to accept the direct loopback address route.

   content_copy zoom_out_map

   [edit]
   user@MX21# set policy-options policy-statement LO from protocol direct
   user@MX21# set policy-options policy-statement LO from route-filter 198.51.100.21/32 exact
   user@MX21# set policy-options policy-statement LO then accept
   

8. Configure the NO-EXPORT community.

   content_copy zoom_out_map

   [edit]
   user@MX21# set policy-options community NO-EXPORT members no-advertise
   user@MX21# set policy-options community NO-EXPORT members no-export
   user@MX21# set policy-options community NO-EXPORT members no-export-subconfed
   

9. Configure the load balancing and TEST policies.

   content_copy zoom_out_map

   [edit]
   user@MX21# set policy-options policy-statement TEST then community add NO-EXPORT
   user@MX21# set policy-options policy-statement evpn-pplb from protocol evpn
   user@MX21# set policy-options policy-statement evpn-pplb then load-balance per-packet
   

10. Configure an ESI value on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC2 network.

    content_copy zoom_out_map

    [edit]
    user@MX21# set interfaces lt-5/0/0 esi 00:33:33:33:33:33:33:33:33:33
    

11. Configure active-active multihoming on the logical tunnel interface by including the all-active statement.

    content_copy zoom_out_map

    [edit]
    user@MX21# set interfaces lt-5/0/0 esi all-active
    

12. Configure a pair of logical tunnel (lt-) interfaces on the MX21 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

    content_copy zoom_out_map

    [edit]
    user@MX21# set interfaces lt-5/0/0 unit 0 peer-unit 1
    user@MX21# set interfaces lt-5/0/0 unit 0 family bridge interface-mode trunk
    user@MX21# set interfaces lt-5/0/0 unit 0 family bridge vlan-id-list 1-5
    user@MX21# set interfaces lt-5/0/0 unit 1 peer-unit 0
    user@MX21# set interfaces lt-5/0/0 unit 1 family bridge interface-mode trunk
    user@MX21# set interfaces lt-5/0/0 unit 1 family bridge vlan-id-list 1-5
    

13. Configure the loopback interface address and routing options.

    content_copy zoom_out_map

    [edit]
    user@MX21# set interfaces lo0 unit 87 family inet address 198.51.100.21/32
    user@MX21# set interfaces lo0 unit 87 family mpls
    user@MX21# set routing-options router-id 198.51.100.21
    user@MX21# set routing-options autonomous-system 65300
    

14. Apply the load balancing policy to the forwarding table.

    content_copy zoom_out_map

    [edit]
    user@MX21# set routing-options forwarding-table export evpn-pplb

15. Enable RSVP, MPLS, BGP, and OSPF protocols on the core interfaces. Create MPLS LSPs and specify the address of the other gateway and WAN edge routers (MX11, MX12, P, MX22).

    content_copy zoom_out_map

    [edit]
    user@MX21# set protocols rsvp interface all
    user@MX21# set protocols rsvp interface fxp0.0 disable
    user@MX21# set protocols mpls label-switched-path MX21-TO-MX11 to 192.0.2.21
    user@MX21# set protocols mpls label-switched-path MX21-TO-MX12 to 192.0.2.22
    user@MX21# set protocols mpls label-switched-path MX21-TO-P to 203.0.113.1
    user@MX21# set protocols mpls label-switched-path MX21-TO-MX22 to 198.51.100.22
    user@MX21# set protocols mpls interface all
    user@MX21# set protocols mpls interface fxp0.0 disable
    user@MX21# set protocols bgp local-address 198.51.100.21
    user@MX21# set protocols bgp export TEST
    user@MX21# set protocols bgp local-as 65300
    user@MX21# set protocols bgp group INT type internal
    user@MX21# set protocols bgp group INT local-address 198.51.100.21
    user@MX21# set protocols bgp group INT family evpn signaling
    user@MX21# set protocols bgp group INT export TEST
    user@MX21# set protocols bgp group INT neighbor 203.0.113.1
    user@MX21# set protocols ospf traffic-engineering
    user@MX21# set protocols ospf area 0.0.0.0 interface ge-5/0/0.0
    user@MX21# set protocols ospf area 0.0.0.0 interface lo0.87 passive
    

16. Configure EVPN-based MPLS routing instances on the MX21 router for each virtual network. Define the route distinguisher (used to identify and advertise EVPN-MPLS routes) and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure a bridge domain for each virtual router that maps VLAN IDs.

    content_copy zoom_out_map

    [edit]
    user@MX21# set routing-instances EVPN-MPLS-1 instance-type virtual-switch
    user@MX21# set routing-instances EVPN-MPLS-1 interface lt-5/0/0.0
    user@MX21# set routing-instances EVPN-MPLS-1 route-distinguisher 198.51.100.21:100
    user@MX21# set routing-instances EVPN-MPLS-1 vrf-target target:1:2
    user@MX21# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file MX21-EVPN-MPLS-1.log
    user@MX21# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file size 10m
    user@MX21# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions flag all
    user@MX21# set routing-instances EVPN-MPLS-1 protocols evpn extended-vlan-list 1-5
    user@MX21# set routing-instances EVPN-MPLS-1 protocols evpn default-gateway no-gateway-community
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 domain-type bridge
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 vlan-id 1
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 domain-type bridge
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 vlan-id 2
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 domain-type bridge
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 vlan-id 3
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 domain-type bridge
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 vlan-id 4
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 domain-type bridge
    user@MX21# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 vlan-id 5
    

17. Configure EVPN-VXLAN routing instances on the MX21 router for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@MX21# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.87
    user@MX21# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@MX21# set routing-instances EVPN-VXLAN-1 interface lt-5/0/0.1
    user@MX21# set routing-instances EVPN-VXLAN-1 route-distinguisher 198.51.100.21:1
    user@MX21# set routing-instances EVPN-VXLAN-1 vrf-target target:1:3
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file MX21-EVPN-VXLAN-1.log
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@MX21# set routing-instances EVPN-VXLAN-1 protocols evpn default-gateway no-gateway-community
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 routing-interface irb.1
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 routing-interface irb.2
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 routing-interface irb.3
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 routing-interface irb.4
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 routing-interface irb.5
    user@MX21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5
    user@MX21# set routing-instances VRF instance-type vrf
    user@MX21# set routing-instances VRF interface irb.1
    user@MX21# set routing-instances VRF interface irb.2
    user@MX21# set routing-instances VRF interface irb.3
    user@MX21# set routing-instances VRF interface irb.4
    user@MX21# set routing-instances VRF interface irb.5
    user@MX21# set routing-instances VRF route-distinguisher 1:1
    user@MX21# set routing-instances VRF vrf-target target:10:10
    

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 in the CLI User Guide.

Configure an MX Series router as the data center gateway and WAN edge router and name it as MX22:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@MX22# set system host-name MX22
   

2. Configure the interfaces on the MX22 router (DC GW/WAN Edge 4) to enable the underlay connectivity to the MX22, ToR21, MX21, and P devices, which is the EVPN-VXLAN part of DC2 network.

   content_copy zoom_out_map

   [edit]
   user@MX22# set interfaces xe-0/0/0 unit 0 description "CONNECTED TO ToR22"
   user@MX22# set interfaces xe-0/0/0 unit 0 family inet address 192.168.11.1/24
   user@MX22# set interfaces xe-0/0/1 unit 0 description "CONNECTED TO ToR21"
   user@MX22# set interfaces xe-0/0/1 unit 0 family inet address 192.168.10.1/24
   user@MX22# set interfaces ge-1/0/0 unit 0 description "CONNECTED TO MX21"
   user@MX22# set interfaces ge-1/0/0 unit 0 family inet address 192.168.13.2/24
   user@MX22# set interfaces ge-1/0/2 unit 0 description "CONNECTED TO P"
   user@MX22# set interfaces ge-1/0/2 unit 0 family inet address 203.0.113.51/24
   user@MX22# set interfaces ge-1/0/2 unit 0 family mpls
   

3. Configure external BGP (EBGP) underlay connectivity between the gateway routers (MX21 and MX22) and ToR (ToR21 and ToR22).

   content_copy zoom_out_map

   [edit]
   user@MX22# set protocols bgp group MX21 type external
   user@MX22# set protocols bgp group MX21 local-address 192.168.13.2
   user@MX22# set protocols bgp group MX21 export TEST
   user@MX22# set protocols bgp group MX21 export LO
   user@MX22# set protocols bgp group MX21 peer-as 64800
   user@MX22# set protocols bgp group MX21 local-as 64900
   user@MX22# set protocols bgp group MX21 neighbor 192.168.13.1 family inet unicast
   user@MX22# set protocols bgp group ToR21 type external
   user@MX22# set protocols bgp group ToR21 local-address 192.168.10.1
   user@MX22# set protocols bgp group ToR21 export TEST
   user@MX22# set protocols bgp group ToR21 export LO
   user@MX22# set protocols bgp group ToR21 peer-as 64600
   user@MX22# set protocols bgp group ToR21 local-as 64900
   user@MX22# set protocols bgp group ToR21 neighbor 192.168.10.2 family inet unicast
   user@MX22# set protocols bgp group ToR22 type external
   user@MX22# set protocols bgp group ToR22 local-address 192.168.11.1
   user@MX22# set protocols bgp group ToR22 export TEST
   user@MX22# set protocols bgp group ToR22 export LO
   user@MX22# set protocols bgp group ToR22 peer-as 64700
   user@MX22# set protocols bgp group ToR22 local-as 64900
   user@MX22# set protocols bgp group ToR22 neighbor 192.168.11.2 family inet unicast
   

4. Configure a multiprotocol external BGP (MP-EBGP) overlay connectivity between the gateway routers (MX21 and MX22) and ToR (ToR21 and ToR22) and set EVPN as the signaling protocol.

   content_copy zoom_out_map

   [edit]
   user@MX22# set protocols bgp group MX21-EVPN type external
   user@MX22# set protocols bgp group MX21-EVPN multihop ttl 2
   user@MX22# set protocols bgp group MX21-EVPN multihop no-nexthop-change
   user@MX22# set protocols bgp group MX21-EVPN local-address 198.51.100.22
   user@MX22# set protocols bgp group MX21-EVPN peer-as 64800
   user@MX22# set protocols bgp group MX21-EVPN local-as 64900
   user@MX22# set protocols bgp group MX21-EVPN neighbor 198.51.100.21 family evpn signaling
   user@MX22# set protocols bgp group ToR21-EVPN type external
   user@MX22# set protocols bgp group ToR21-EVPN multihop ttl 2
   user@MX22# set protocols bgp group ToR21-EVPN multihop no-nexthop-change
   user@MX22# set protocols bgp group ToR21-EVPN local-address 198.51.100.22
   user@MX22# set protocols bgp group ToR21-EVPN peer-as 64600
   user@MX22# set protocols bgp group ToR21-EVPN local-as 64900
   user@MX22# set protocols bgp group ToR21-EVPN neighbor 198.51.100.11 family evpn signaling
   user@MX22# set protocols bgp group ToR22-EVPN type external
   user@MX22# set protocols bgp group ToR22-EVPN multihop ttl 2
   user@MX22# set protocols bgp group ToR22-EVPN multihop no-nexthop-change
   user@MX22# set protocols bgp group ToR22-EVPN local-address 198.51.100.22
   user@MX22# set protocols bgp group ToR22-EVPN peer-as 64700
   user@MX22# set protocols bgp group ToR22-EVPN local-as 64900
   user@MX22# set protocols bgp group ToR22-EVPN neighbor 198.51.100.12 family evpn signaling
   

5. Configure integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

   Step-by-Step Procedure

   1. The following is the IRB gateway configuration for the VLAN-1 on MX22 (which is the host part of VLAN-1):

      content_copy zoom_out_map

      [edit]
      user@MX22# set interfaces irb unit 1 proxy-macip-advertisement
      user@MX22# set interfaces irb unit 1 virtual-gateway-esi 00:22:aa:aa:aa:aa:aa:aa:aa:aa
      user@MX22# set interfaces irb unit 1 virtual-gateway-esi all-active
      user@MX22# set interfaces irb unit 1 family inet address 10.11.1.15/24 virtual-gateway-address 10.11.1.11
      

   2. The following is the IRB gateway configuration for the VLAN-2 on MX22 (which is the host part of VLAN-2):

      content_copy zoom_out_map

      [edit]
      user@MX22# set interfaces irb unit 2 proxy-macip-advertisement
      user@MX22# set interfaces irb unit 2 virtual-gateway-esi 00:22:bb:bb:bb:bb:bb:bb:bb:bb
      user@MX22# set interfaces irb unit 2 virtual-gateway-esi all-active
      user@MX22# set interfaces irb unit 2 family inet address 10.12.1.15/24 virtual-gateway-address 10.12.1.11
      

   3. The following is the IRB gateway configuration for the VLAN-3 on MX22 (which is the host part of VLAN-3):

      content_copy zoom_out_map

      [edit]
      user@MX22# set interfaces irb unit 3 proxy-macip-advertisement
      user@MX22# set interfaces irb unit 3 virtual-gateway-esi 00:22:cc:cc:cc:cc:cc:cc:cc:cc
      user@MX22# set interfaces irb unit 3 virtual-gateway-esi all-active
      user@MX22# set interfaces irb unit 3 family inet address 10.13.1.15/24 virtual-gateway-address 10.13.1.11
      

   4. The following is the IRB gateway configuration for the VLAN-4 on MX22 (which is the host part of VLAN-4):

      content_copy zoom_out_map

      [edit]
      user@MX22# set interfaces irb unit 4 proxy-macip-advertisement
      user@MX22# set interfaces irb unit 4 virtual-gateway-esi 00:22:dd:dd:dd:dd:dd:dd:dd:dd
      user@MX22# set interfaces irb unit 4 virtual-gateway-esi all-active
      user@MX22# set interfaces irb unit 4 family inet address 10.14.1.15/24 virtual-gateway-address 10.14.1.11
      

   5. The following is the IRB gateway configuration for the VLAN-5 on MX22 (which is the host part of VLAN-5):

      content_copy zoom_out_map

      [edit]
      user@MX22# set interfaces irb unit 5 proxy-macip-advertisement
      user@MX22# set interfaces irb unit 5 virtual-gateway-esi 00:22:ee:ee:ee:ee:ee:ee:ee:ee
      user@MX22# set interfaces irb unit 5 virtual-gateway-esi all-active
      user@MX22# set interfaces irb unit 5 family inet address 10.15.1.15/24 virtual-gateway-address 10.15.1.11
      

6. Configure trace operations to track all Layer 2 address learning and forwarding properties.

   content_copy zoom_out_map

   [edit]
   user@MX22# set protocols l2-learning traceoptions file MX22-L2ALD.log
   user@MX22# set protocols l2-learning traceoptions file size 10m
   user@MX22# set protocols l2-learning traceoptions level all
   user@MX22# set protocols l2-learning traceoptions flag all
   

7. Configure routing policy to accept the direct loopback address route.

   content_copy zoom_out_map

   [edit]
   user@MX22# set policy-options policy-statement LO from protocol direct
   user@MX22# set policy-options policy-statement LO from route-filter 198.51.100.22/32 exact
   user@MX22# set policy-options policy-statement LO then accept
   

8. Configure the NO-EXPORT community.

   content_copy zoom_out_map

   [edit]
   user@MX22# set policy-options community NO-EXPORT members no-advertise
   user@MX22# set policy-options community NO-EXPORT members no-export
   user@MX22# set policy-options community NO-EXPORT members no-export-subconfed
   

9. Configure the load balancing and TEST policies.

   content_copy zoom_out_map

   [edit]
   user@MX22# set policy-options policy-statement TEST then community add NO-EXPORT
   user@MX22# set policy-options policy-statement evpn-pplb from protocol evpn
   user@MX22# set policy-options policy-statement evpn-pplb then load-balance per-packet
   

10. Configure an ESI value on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC2 network.

    content_copy zoom_out_map

    [edit]
    user@MX22# set interfaces lt-1/0/0 esi 00:33:33:33:33:33:33:33:33:33
    

11. Configure active-active multihoming on the logical tunnel interface by including the all-active statement.

    content_copy zoom_out_map

    [edit]
    user@MX22# set interfaces lt-1/0/0 esi all-active
    

12. Configure a pair of logical tunnel (lt-) interfaces on the MX22 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

    content_copy zoom_out_map

    [edit]
    user@MX22# set interfaces lt-1/0/0 unit 0 peer-unit 1
    user@MX22# set interfaces lt-1/0/0 unit 0 family bridge interface-mode trunk
    user@MX22# set interfaces lt-1/0/0 unit 0 family bridge vlan-id-list 1-5
    user@MX22# set interfaces lt-1/0/0 unit 1 peer-unit 0
    user@MX22# set interfaces lt-1/0/0 unit 1 family bridge interface-mode trunk
    user@MX22# set interfaces lt-1/0/0 unit 1 family bridge vlan-id-list 1-5
    

13. Configure the loopback interface address and routing options.

    content_copy zoom_out_map

    [edit]
    user@MX22# set interfaces lo0 unit 88 family inet address 198.51.100.22/32
    user@MX22# set routing-options router-id 198.51.100.22
    user@MX22# set routing-options autonomous-system 65300
    

14. Apply the load balancing policy to the forwarding table.

    content_copy zoom_out_map

    [edit]
    user@MX22# set routing-options forwarding-table export evpn-pplb
    

15. Enable RSVP, MPLS, BGP, and OSPF protocols on the core interfaces. Create MPLS LSPs and specify the address of the other gateway and WAN edge routers (MX11, MX12, P, MX21).

    content_copy zoom_out_map

    [edit]
    user@MX22# set protocols rsvp interface all
    user@MX22# set protocols rsvp interface fxp0.0 disable
    user@MX22# set protocols mpls label-switched-path MX22-TO-MX11 to 192.0.2.21
    user@MX22# set protocols mpls label-switched-path MX22-TO-MX12 to 192.0.2.22
    user@MX22# set protocols mpls label-switched-path MX22-TO-P to 203.0.113.1
    user@MX22# set protocols mpls label-switched-path MX22-TO-MX21 to 198.51.100.21
    user@MX22# set protocols mpls interface all
    user@MX22# set protocols mpls interface fxp0.0 disable
    user@MX22# set protocols bgp local-address 198.51.100.22
    user@MX22# set protocols bgp export TEST
    user@MX22# set protocols bgp local-as 65300
    user@MX22# set protocols bgp group INT type internal
    user@MX22# set protocols bgp group INT family evpn signaling
    user@MX22# set protocols bgp group INT export TEST
    user@MX22# set protocols bgp group INT neighbor 203.0.113.1
    user@MX22# set protocols ospf traffic-engineering
    user@MX22# set protocols ospf area 0.0.0.0 interface ge-1/0/2.0
    user@MX22# set protocols ospf area 0.0.0.0 interface lo0.88 passive
    

16. Configure EVPN-based MPLS routing instances on the MX22 router for each virtual network. Define the route distinguisher (used to identify and advertise EVPN-MPLS routes) and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure a bridge domain for each virtual router that maps VLAN IDs.

    content_copy zoom_out_map

    [edit]
    user@MX22# set routing-instances EVPN-MPLS-1 instance-type virtual-switch
    user@MX22# set routing-instances EVPN-MPLS-1 interface lt-1/0/0.0
    user@MX22# set routing-instances EVPN-MPLS-1 route-distinguisher 198.51.100.22:100
    user@MX22# set routing-instances EVPN-MPLS-1 vrf-target target:1:2
    user@MX22# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file MX22-EVPN-MPLS-1.log
    user@MX22# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions file size 10m
    user@MX22# set routing-instances EVPN-MPLS-1 protocols evpn traceoptions flag all
    user@MX22# set routing-instances EVPN-MPLS-1 protocols evpn extended-vlan-list 1-5
    user@MX22# set routing-instances EVPN-MPLS-1 protocols evpn default-gateway no-gateway-community
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 domain-type bridge
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-1 vlan-id 1
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 domain-type bridge
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-2 vlan-id 2
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 domain-type bridge
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-3 vlan-id 3
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 domain-type bridge
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-4 vlan-id 4
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 domain-type bridge
    user@MX22# set routing-instances EVPN-MPLS-1 bridge-domains BD-5 vlan-id 5
    

17. Configure EVPN-VXLAN routing instances on the MX22 router for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@MX22# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.88
    user@MX22# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@MX22# set routing-instances EVPN-VXLAN-1 interface lt-1/0/0.1
    user@MX22# set routing-instances EVPN-VXLAN-1 route-distinguisher 198.51.100.22:1
    user@MX22# set routing-instances EVPN-VXLAN-1 vrf-target target:1:3
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file MX22-EVPN-VXLAN-1.log
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@MX22# set routing-instances EVPN-VXLAN-1 protocols evpn default-gateway no-gateway-community
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 routing-interface irb.1
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 routing-interface irb.2
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 routing-interface irb.3
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 routing-interface irb.4
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 routing-interface irb.5
    user@MX22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5
    user@MX22# set routing-instances VRF instance-type vrf
    user@MX22# set routing-instances VRF interface irb.1
    user@MX22# set routing-instances VRF interface irb.2
    user@MX22# set routing-instances VRF interface irb.3
    user@MX22# set routing-instances VRF interface irb.4
    user@MX22# set routing-instances VRF interface irb.5
    user@MX22# set routing-instances VRF route-distinguisher 1:1
    user@MX22# set routing-instances VRF vrf-target target:10:10
    

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 in the CLI User Guide.

Configure the MX router as ToR21:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set system host-name ToR21
   

2. Configure the interfaces and bridge domains on the CE4 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set logical-systems CE-4 interfaces ge-1/0/9 unit 0 description "CONNECTED TO Host 4"
   user@ToR21# set logical-systems CE-4 interfaces ge-1/0/9 unit 0 family bridge interface-mode trunk
   user@ToR21# set logical-systems CE-4 interfaces ge-1/0/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR21# set logical-systems CE-4 interfaces ge-1/1/6 unit 0 description "CONNECTED TO ToR21"
   user@ToR21# set logical-systems CE-4 interfaces ge-1/1/6 unit 0 family bridge interface-mode trunk
   user@ToR21# set logical-systems CE-4 interfaces ge-1/1/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR21# set logical-systems CE-4 bridge-domains BD-1 domain-type bridge
   user@ToR21# set logical-systems CE-4 bridge-domains BD-1 vlan-id 1
   user@ToR21# set logical-systems CE-4 bridge-domains BD-2 domain-type bridge
   user@ToR21# set logical-systems CE-4 bridge-domains BD-2 vlan-id 2
   user@ToR21# set logical-systems CE-4 bridge-domains BD-3 domain-type bridge
   user@ToR21# set logical-systems CE-4 bridge-domains BD-3 vlan-id 3
   user@ToR21# set logical-systems CE-4 bridge-domains BD-4 domain-type bridge
   user@ToR21# set logical-systems CE-4 bridge-domains BD-4 vlan-id 4
   user@ToR21# set logical-systems CE-4 bridge-domains BD-5 domain-type bridge
   user@ToR21# set logical-systems CE-4 bridge-domains BD-5 vlan-id 5

3. Configure trace options for the interfaces to enable trace logs.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set interfaces traceoptions file ToR21-DCD.log
   user@ToR21# set interfaces traceoptions file size 10m
   user@ToR21# set interfaces traceoptions flag all

4. Set the number of aggregated Ethernet interfaces.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set chassis aggregated-devices ethernet device-count 1
   

5. Configure the interfaces on the ToR21 device to connect to the MX22, CE-5, CE-4, ToR22, and MX21 devices to enable underlay connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set interfaces xe-0/0/0 unit 0 description "CONNECTED TO MX22"
   user@ToR21# set interfaces xe-0/0/0 unit 0 family inet address 192.168.10.2/24
   user@ToR21# set interfaces ge-1/0/0 description "CONNECTED TO CE-5"
   user@ToR21# set interfaces ge-1/0/0 gigether-options 802.3ad ae0
   user@ToR21# set interfaces ge-1/0/1 unit 0 description "CONNECTED TO MX21"
   user@ToR21# set interfaces ge-1/0/1 unit 0 family inet address 192.168.9.2/24
   user@ToR21# set interfaces ge-1/0/6 unit 0 description "CONNECTED TO CE-4"
   user@ToR21# set interfaces ge-1/0/6 unit 0 family bridge interface-mode trunk
   user@ToR21# set interfaces ge-1/0/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR21# set interfaces ge-1/1/3 unit 0 description "CONNECTED TO ToR22"
   user@ToR21# set interfaces ge-1/1/3 unit 0 family inet address 192.168.12.1/24

6. Configure a Link Aggregation Control Protocol (LACP)-enabled link aggregation group (LAG) interface towards the CE-5 end host device. The ESI value is globally unique across the entire EVPN domain. The all-active configuration enables ToR21 and ToR22 to forward traffic to, and from the CE devices, such that all CE links are actively used.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set interfaces ae0 esi 00:44:44:44:44:44:44:44:44:44
   user@ToR21# set interfaces ae0 esi all-active
   user@ToR21# set interfaces ae0 aggregated-ether-options lacp active
   user@ToR21# set interfaces ae0 aggregated-ether-options lacp periodic fast
   user@ToR21# set interfaces ae0 aggregated-ether-options lacp system-id 22:22:22:22:22:22
   user@ToR21# set interfaces ae0 unit 0 family bridge interface-mode trunk
   user@ToR21# set interfaces ae0 unit 0 family bridge vlan-id-list 1-5

7. Configure the loopback interface address and routing options.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set interfaces lo0 unit 90 family inet address 198.51.100.11/32
   user@ToR21# set routing-options router-id 198.51.100.11
   user@ToR21# set routing-options autonomous-system 64600
   

8. Apply the load balancing policy to the forwarding table.

   content_copy zoom_out_map

   [edit]
   user@ToR21# set routing-options forwarding-table export evpn-pplb

9. Configure external BGP (EBGP) underlay connectivity between the ToR (ToR21 and ToR22) and gateway routers (MX21 and MX22).

   content_copy zoom_out_map

   [edit]
   user@ToR21# set protocols bgp export TEST
   user@ToR21# set protocols bgp local-as 64600
   user@ToR21# set protocols bgp group MX21 type external
   user@ToR21# set protocols bgp group MX21 local-address 192.168.9.2
   user@ToR21# set protocols bgp group MX21 export LO
   user@ToR21# set protocols bgp group MX21 export TEST
   user@ToR21# set protocols bgp group MX21 peer-as 64800
   user@ToR21# set protocols bgp group MX21 local-as 64600
   user@ToR21# set protocols bgp group MX21 neighbor 192.168.9.1 family inet unicast
   user@ToR21# set protocols bgp group MX22 type external
   user@ToR21# set protocols bgp group MX22 local-address 192.168.10.2
   user@ToR21# set protocols bgp group MX22 export LO
   user@ToR21# set protocols bgp group MX22 export TEST
   user@ToR21# set protocols bgp group MX22 peer-as 64900
   user@ToR21# set protocols bgp group MX22 local-as 64600
   user@ToR21# set protocols bgp group MX22 neighbor 192.168.10.1 family inet unicast
   user@ToR21# set protocols bgp group ToR22 type external
   user@ToR21# set protocols bgp group ToR22 local-address 192.168.12.1
   user@ToR21# set protocols bgp group ToR22 export LO
   user@ToR21# set protocols bgp group ToR22 export TEST
   user@ToR21# set protocols bgp group ToR22 peer-as 64700
   user@ToR21# set protocols bgp group ToR22 local-as 64600
   user@ToR21# set protocols bgp group ToR22 neighbor 192.168.12.2 family inet unicast

10. Configure a multiprotocol external BGP (MP-EBGP) overlay between the ToR (ToR21 and ToR22) and gateway routers (MX21 and MX22) and set EVPN as the signaling protocol.

    Step-by-Step Procedure

    1. Configure a MP-EBGP overlay to connect between ToR21 and MX21 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR21# set protocols bgp group MX21-EVPN type external
       user@ToR21# set protocols bgp group MX21-EVPN multihop ttl 2
       user@ToR21# set protocols bgp group MX21-EVPN multihop no-nexthop-change
       user@ToR21# set protocols bgp group MX21-EVPN local-address 198.51.100.11
       user@ToR21# set protocols bgp group MX21-EVPN peer-as 64800
       user@ToR21# set protocols bgp group MX21-EVPN local-as 64600
       user@ToR21# set protocols bgp group MX21-EVPN neighbor 198.51.100.21 family evpn signaling

    2. Configure a MP-EBGP overlay to connect between ToR21 and MX22 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR21# set protocols bgp group MX22-EVPN type external
       user@ToR21# set protocols bgp group MX22-EVPN multihop ttl 2
       user@ToR21# set protocols bgp group MX22-EVPN multihop no-nexthop-change
       user@ToR21# set protocols bgp group MX22-EVPN local-address 198.51.100.11
       user@ToR21# set protocols bgp group MX22-EVPN peer-as 64900
       user@ToR21# set protocols bgp group MX22-EVPN local-as 64600
       user@ToR21# set protocols bgp group MX22-EVPN neighbor 198.51.100.22 family evpn signaling

    3. Configure a MP-EBGP overlay to connect between ToR21 and ToR22 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR21# set protocols bgp group ToR22-EVPN type external
       user@ToR21# set protocols bgp group ToR22-EVPN multihop ttl 2
       user@ToR21# set protocols bgp group ToR22-EVPN multihop no-nexthop-change
       user@ToR21# set protocols bgp group ToR22-EVPN local-address 198.51.100.11
       user@ToR21# set protocols bgp group ToR22-EVPN peer-as 64700
       user@ToR21# set protocols bgp group ToR22-EVPN local-as 64600
       user@ToR21# set protocols bgp group ToR22-EVPN neighbor 198.51.100.12 family evpn signaling

11. Configure trace operations to track all Layer 2 address learning and forwarding properties.

    content_copy zoom_out_map

    [edit]
    user@ToR21# set protocols l2-learning traceoptions file TOR21-L2ALD.log
    user@ToR21# set protocols l2-learning traceoptions file size 10m
    user@ToR21# set protocols l2-learning traceoptions level all
    user@ToR21# set protocols l2-learning traceoptions flag all

12. Configure routing policy to accept the direct loopback address route.

    content_copy zoom_out_map

    [edit]
    user@ToR21# set policy-options policy-statement LO term 1 from protocol direct
    user@ToR21# set policy-options policy-statement LO term 1 from route-filter 198.51.100.11/32 exact
    user@ToR21# set policy-options policy-statement LO term 1 then accept

13. Configure the NO-EXPORT community.

    content_copy zoom_out_map

    [edit]
    user@ToR21# set policy-options community NO-EXPORT members no-advertise
    user@ToR21# set policy-options community NO-EXPORT members no-export
    user@ToR21# set policy-options community NO-EXPORT members no-export-subconfed
    

14. Configure the load balancing and TEST policies.

    content_copy zoom_out_map

    [edit]
    user@ToR21# set policy-options policy-statement TEST then community add NO-EXPORT
    user@ToR21# set policy-options policy-statement evpn-pplb from protocol evpn
    user@ToR21# set policy-options policy-statement evpn-pplb then load-balance per-packet

15. Configure EVPN routing instances for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@ToR21# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.90
    user@ToR21# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@ToR21# set routing-instances EVPN-VXLAN-1 interface ge-1/0/6.0
    user@ToR21# set routing-instances EVPN-VXLAN-1 interface ae0.0
    user@ToR21# set routing-instances EVPN-VXLAN-1 route-distinguisher 198.51.100.11:1
    user@ToR21# set routing-instances EVPN-VXLAN-1 vrf-target target:1:3
    user@ToR21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file TOR21-EVPN-VXLAN-1.log
    user@ToR21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@ToR21# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@ToR21# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@ToR21# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@ToR21# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5

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 in the CLI User Guide.

Configure the MX router ToR22:

1. Set the system hostname.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set system host-name ToR22
   

2. Configure the interfaces and bridge domains on the CE-5 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set logical-systems CE-5 interfaces ge-1/0/9 unit 0 description "CONNECTED TO Host 5"
   user@ToR22# set logical-systems CE-5 interfaces ge-1/0/9 unit 0 family bridge interface-mode trunk
   user@ToR22# set logical-systems CE-5 interfaces ge-1/0/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set logical-systems CE-5 interfaces ae1 unit 0 description "CONNECTED TO ToR21"
   user@ToR22# set logical-systems CE-5 interfaces ae1 unit 0 family bridge interface-mode trunk
   user@ToR22# set logical-systems CE-5 interfaces ae1 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set logical-systems CE-5 bridge-domains BD-1 domain-type bridge
   user@ToR22# set logical-systems CE-5 bridge-domains BD-1 vlan-id 1
   user@ToR22# set logical-systems CE-5 bridge-domains BD-2 domain-type bridge
   user@ToR22# set logical-systems CE-5 bridge-domains BD-2 vlan-id 2
   user@ToR22# set logical-systems CE-5 bridge-domains BD-3 domain-type bridge
   user@ToR22# set logical-systems CE-5 bridge-domains BD-3 vlan-id 3
   user@ToR22# set logical-systems CE-5 bridge-domains BD-4 domain-type bridge
   user@ToR22# set logical-systems CE-5 bridge-domains BD-4 vlan-id 4
   user@ToR22# set logical-systems CE-5 bridge-domains BD-5 domain-type bridge
   user@ToR22# set logical-systems CE-5 bridge-domains BD-5 vlan-id 5
   

3. Configure the interfaces and bridge domains on the CE-6 device to enable Layer 2 connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/6 unit 0 description "CONNECTED TO ToR22"
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/6 unit 0 family bridge interface-mode trunk
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/9 unit 0 description "CONNECTED TO Host 6"
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/9 unit 0 family bridge interface-mode trunk
   user@ToR22# set logical-systems CE-6 interfaces ge-1/1/9 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set logical-systems CE-6 bridge-domains BD-1 domain-type bridge
   user@ToR22# set logical-systems CE-6 bridge-domains BD-1 vlan-id 1
   user@ToR22# set logical-systems CE-6 bridge-domains BD-2 domain-type bridge
   user@ToR22# set logical-systems CE-6 bridge-domains BD-2 vlan-id 2
   user@ToR22# set logical-systems CE-6 bridge-domains BD-3 domain-type bridge
   user@ToR22# set logical-systems CE-6 bridge-domains BD-3 vlan-id 3
   user@ToR22# set logical-systems CE-6 bridge-domains BD-4 domain-type bridge
   user@ToR22# set logical-systems CE-6 bridge-domains BD-4 vlan-id 4
   user@ToR22# set logical-systems CE-6 bridge-domains BD-5 domain-type bridge
   user@ToR22# set logical-systems CE-6 bridge-domains BD-5 vlan-id 5
   

4. Configure trace options for the interfaces to enable trace logs.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set interfaces traceoptions file R7-DCD.log
   user@ToR22# set interfaces traceoptions file size 10m
   user@ToR22# set interfaces traceoptions flag all
   

5. Set the number of aggregated Ethernet interfaces.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set chassis aggregated-devices ethernet device-count 2
   

6. Configure the interfaces on the ToR22 device to connect to the MX22, CE-5, CE-6, ToR21, and MX21 devices to enable underlay connectivity.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set interfaces xe-0/0/0 unit 0 description "CONNECTED TO MX22"
   user@ToR22# set interfaces xe-0/0/0 unit 0 family inet address 192.168.11.2/24
   user@ToR22# set interfaces ge-1/0/0 description "CONNECTED TO ToR21"
   user@ToR22# set interfaces ge-1/0/0 gigether-options 802.3ad ae1
   user@ToR22# set interfaces ge-1/0/6 unit 0 description "CONNECTED TO CE-6"
   user@ToR22# set interfaces ge-1/0/6 unit 0 family bridge interface-mode trunk
   user@ToR22# set interfaces ge-1/0/6 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set interfaces ge-1/0/7 description "CONNECTED TO ToR22"
   user@ToR22# set interfaces ge-1/0/7 gigether-options 802.3ad ae1
   user@ToR22# set interfaces ge-1/1/0 unit 0 description "CONNECTED TO MX21"
   user@ToR22# set interfaces ge-1/1/0 unit 0 family inet address 192.168.8.2/24
   user@ToR22# set interfaces ge-1/1/3 unit 0 description "CONNECTED TO ToR21"
   user@ToR22# set interfaces ge-1/1/3 unit 0 family inet address 192.168.12.2/24
   user@ToR22# set interfaces ge-1/1/7 description "CONNECTED TO CE-5"
   user@ToR22# set interfaces ge-1/1/7 gigether-options 802.3ad ae0
   

7. Configure a Link Aggregation Control Protocol (LACP)-enabled link aggregation group (LAG) interface towards the CE-5 end host device. The ESI value is globally unique across the entire EVPN domain. The all-active configuration enables ToR21 and ToR22 to forward traffic to, and from the CE devices, such that all CE links are actively used.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set interfaces ae0 esi 00:44:44:44:44:44:44:44:44:44
   user@ToR22# set interfaces ae0 esi all-active
   user@ToR22# set interfaces ae0 aggregated-ether-options lacp active
   user@ToR22# set interfaces ae0 aggregated-ether-options lacp periodic fast
   user@ToR22# set interfaces ae0 aggregated-ether-options lacp system-id 22:22:22:22:22:22
   user@ToR22# set interfaces ae0 unit 0 family bridge interface-mode trunk
   user@ToR22# set interfaces ae0 unit 0 family bridge vlan-id-list 1-5
   user@ToR22# set interfaces ae1 aggregated-ether-options lacp active
   user@ToR22# set interfaces ae1 aggregated-ether-options lacp periodic fast
   user@ToR22# set interfaces ae1 aggregated-ether-options lacp system-id 22:22:22:22:22:22
   

8. Configure the loopback interface address and routing options.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set interfaces lo0 unit 92 family inet address 198.51.100.12/32
   user@ToR22# set routing-options router-id 198.51.100.12
   user@ToR22# set routing-options autonomous-system 64700
   

9. Apply the load balancing policy to the forwarding table.

   content_copy zoom_out_map

   [edit]
   user@ToR22# set routing-options forwarding-table export evpn-pplb
   

10. Configure external BGP (EBGP) underlay connectivity between the ToR (ToR22 and ToR21) and gateway routers (MX21 and MX22).

    content_copy zoom_out_map

    [edit]
    user@ToR22# set protocols bgp local-as 64700
    user@ToR22# set protocols bgp group MX21 type external
    user@ToR22# set protocols bgp group MX21 local-address 192.168.8.2
    user@ToR22# set protocols bgp group MX21 export LO
    user@ToR22# set protocols bgp group MX21 export TEST
    user@ToR22# set protocols bgp group MX21 peer-as 64800
    user@ToR22# set protocols bgp group MX21 local-as 64700
    user@ToR22# set protocols bgp group MX21 neighbor 192.168.8.1 family inet unicast
    user@ToR22# set protocols bgp group MX22 type external
    user@ToR22# set protocols bgp group MX22 local-address 192.168.11.2
    user@ToR22# set protocols bgp group MX22 export LO
    user@ToR22# set protocols bgp group MX22 export TEST
    user@ToR22# set protocols bgp group MX22 peer-as 64900
    user@ToR22# set protocols bgp group MX22 local-as 64700
    user@ToR22# set protocols bgp group MX22 neighbor 192.168.11.1 family inet unicast
    user@ToR22# set protocols bgp group ToR21 type external
    user@ToR22# set protocols bgp group ToR21 local-address 192.168.12.2
    user@ToR22# set protocols bgp group ToR21 export LO
    user@ToR22# set protocols bgp group ToR21 export TEST
    user@ToR22# set protocols bgp group ToR21 peer-as 64600
    user@ToR22# set protocols bgp group ToR21 local-as 64700
    user@ToR22# set protocols bgp group ToR21 neighbor 192.168.12.1 family inet unicast
    

11. Configure a multiprotocol external BGP (MP-EBGP) overlay between the ToR (ToR22 and ToR21) and gateway routers (MX21 and MX22) and set EVPN as the signaling protocol.

    Step-by-Step Procedure

    1. Configure a MP-EBGP overlay to connect between ToR22 and MX21 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR22# set protocols bgp group MX21-EVPN type external
       user@ToR22# set protocols bgp group MX21-EVPN multihop ttl 2
       user@ToR22# set protocols bgp group MX21-EVPN multihop no-nexthop-change
       user@ToR22# set protocols bgp group MX21-EVPN local-address 198.51.100.12
       user@ToR22# set protocols bgp group MX21-EVPN peer-as 64800
       user@ToR22# set protocols bgp group MX21-EVPN local-as 64700
       user@ToR22# set protocols bgp group MX21-EVPN neighbor 198.51.100.21 family evpn signaling
       

    2. Configure a MP-EBGP overlay to connect between ToR22 and MX22 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR22# set protocols bgp group MX22-EVPN type external
       user@ToR22# set protocols bgp group MX22-EVPN multihop ttl 2
       user@ToR22# set protocols bgp group MX22-EVPN multihop no-nexthop-change
       user@ToR22# set protocols bgp group MX22-EVPN local-address 198.51.100.12
       user@ToR22# set protocols bgp group MX22-EVPN peer-as 64900
       user@ToR22# set protocols bgp group MX22-EVPN local-as 64700
       user@ToR22# set protocols bgp group MX22-EVPN neighbor 198.51.100.22 family evpn signaling
       

    3. Configure a MP-EBGP overlay to connect between ToR22 and ToR21 using EVPN signaling.

       content_copy zoom_out_map

       [edit]
       user@ToR22# set protocols bgp group ToR21-EVPN type external
       user@ToR22# set protocols bgp group ToR21-EVPN multihop ttl 2
       user@ToR22# set protocols bgp group ToR21-EVPN multihop no-nexthop-change
       user@ToR22# set protocols bgp group ToR21-EVPN local-address 198.51.100.12
       user@ToR22# set protocols bgp group ToR21-EVPN peer-as 64600
       user@ToR22# set protocols bgp group ToR21-EVPN local-as 64700
       user@ToR22# set protocols bgp group ToR21-EVPN neighbor 198.51.100.11 family evpn signaling
       

12. Configure trace operations to track all Layer 2 address learning and forwarding properties.

    content_copy zoom_out_map

    [edit]
    user@ToR22# set protocols l2-learning traceoptions file TOR22-L2ALD.log
    user@ToR22# set protocols l2-learning traceoptions file size 10m
    user@ToR22# set protocols l2-learning traceoptions level all
    user@ToR22# set protocols l2-learning traceoptions flag all
    

13. Configure routing policy to accept the direct loopback address route.

    content_copy zoom_out_map

    [edit]
    user@ToR22# set policy-options policy-statement LO term 1 from protocol direct
    user@ToR22# set policy-options policy-statement LO term 1 from route-filter 198.51.100.12/32 exact
    user@ToR22# set policy-options policy-statement LO term 1 then accept
    

14. Configure the NO-EXPORT community.

    content_copy zoom_out_map

    [edit]
    user@ToR22# set policy-options community NO-EXPORT members no-advertise
    user@ToR22# set policy-options community NO-EXPORT members no-export
    user@ToR22# set policy-options community NO-EXPORT members no-export-subconfed
    

15. Configure the load balancing and TEST policies.

    content_copy zoom_out_map

    [edit]
    user@ToR22# set policy-options policy-statement TEST then community add NO-EXPORT
    user@ToR22# set policy-options policy-statement evpn-pplb from protocol evpn
    user@ToR22# set policy-options policy-statement evpn-pplb then load-balance per-packet
    

16. Configure EVPN routing instances for each virtual network. Define the VTEP source interface, route distinguisher (used to identify and advertise EVPN routes), and vrf-target (exports and tags all routes for that local VRF using the defined route target). Configure the EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method. Finally, configure a bridge domain for each virtual router that maps VNIDs to VLAN IDs, and identify the BUM forwarding method.

    content_copy zoom_out_map

    [edit]
    user@ToR22# set routing-instances EVPN-VXLAN-1 vtep-source-interface lo0.92
    user@ToR22# set routing-instances EVPN-VXLAN-1 instance-type virtual-switch
    user@ToR22# set routing-instances EVPN-VXLAN-1 interface ge-1/0/6.0
    user@ToR22# set routing-instances EVPN-VXLAN-1 interface ae0.0
    user@ToR22# set routing-instances EVPN-VXLAN-1 route-distinguisher 198.51.100.12:1
    user@ToR22# set routing-instances EVPN-VXLAN-1 vrf-target target:1:3
    user@ToR22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file TOR22-EVPN-VXLAN-1.log
    user@ToR22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions file size 10m
    user@ToR22# set routing-instances EVPN-VXLAN-1 protocols evpn traceoptions flag all
    user@ToR22# set routing-instances EVPN-VXLAN-1 protocols evpn encapsulation vxlan
    user@ToR22# set routing-instances EVPN-VXLAN-1 protocols evpn extended-vni-list 1-5
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 domain-type bridge
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vlan-id 1
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-1 vxlan vni 1
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 domain-type bridge
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vlan-id 2
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-2 vxlan vni 2
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 domain-type bridge
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vlan-id 3
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-3 vxlan vni 3
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 domain-type bridge
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vlan-id 4
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-4 vxlan vni 4
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 domain-type bridge
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vlan-id 5
    user@ToR22# set routing-instances EVPN-VXLAN-1 bridge-domains BD-5 vxlan vni 5
    

Purpose

Verify that ToR11 is properly configured.

Action

Verify that the logical system interfaces and bridge domains on the CE2 device are properly configured to enable Layer 2 connectivity.

user@ToR11> show configuration logical-systems
CE-2 {
    interfaces {
        ge-1/0/9 {
            unit 0 {
                description "CONNECTED TO Host-2";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ge-1/1/6 {
            unit 0 {
                description "CONNECTED TO ToR11";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}

Verify that the interfaces and trace options on ToR11 are configured properly to enable underlay connectivity to other ToR and gateway and WAN edge devices.

user@ToR11> show configuration interfaces
traceoptions {
    file ToR11-DCD.log size 10m;
    flag all;
}
ge-1/0/0 {
    description "CONNECTED TO CE-1";
    gigether-options {
        802.3ad ae0;
    }
}
ge-1/0/5 {
    unit 0 {
        description "CONNECTED TO MX12";
        family inet {
            address 192.168.4.1/24;
        }
    }
}
ge-1/0/6 {
    unit 0 {
        description "CONNECTED TO CE-2";
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ge-1/1/1 {
    unit 0 {
        description "CONNECTED TO MX11";
        family inet {
            address 192.168.3.1/24;
        }
    }
}
ge-1/1/3 {
    unit 0 {
        description "CONNECTED TO ToR12";
        family inet {
            address 192.168.2.1/24;
        }
    }
}
ae0 {
    esi {
        00:11:11:11:11:11:11:11:11:11;
        all-active;
    }
    aggregated-ether-options {
        lacp {
            active;
            periodic fast;
            system-id 11:11:11:11:11:11;
        }
    }
    unit 0 {
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
lo0 {
    unit 81 {
        family inet {
            address 192.0.2.11/32;
        }
    }
}

Verify that the routing and load balancing options are properly configured.

user@ToR11> show configuration routing-options
router-id 192.0.2.11;
autonomous-system 65100;
forwarding-table {
    export evpn-pplb;
}

Verify that the external BGP (EBGP) underlay and overlay protocols and Layer 2 address learning and forwarding properties are properly configured.

user@ToR11> show configuration protocols
bgp {
    local-as 65100;
    group MX11 {
        type external;
        local-address 192.168.3.1;
        export [ LO TEST ];
        peer-as 65400;
        neighbor 192.168.3.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX12 {
        type external;
        local-address 192.168.4.1;
        export [ LO TEST ];
        peer-as 65500;
        neighbor 192.168.4.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR12 {
        type external;
        local-address 192.168.2.1;
        export [ LO TEST ];
        peer-as 65200;
        local-as 65100;
        neighbor 192.168.2.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.11;
        export TEST;
        peer-as 65400;
        local-as 65100;
        neighbor 192.0.2.21 {
            family evpn {
                signaling;
            }
        }
    }
    group MX12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.11;
        export TEST;
        peer-as 65500;
        local-as 65100;
        neighbor 192.0.2.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.11;
        export TEST;
        peer-as 65200;
        local-as 65100;
        neighbor 192.0.2.12 {
            family evpn {
                signaling;
            }
        }
    }
}
l2-learning {
    traceoptions {
        file TOR11-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@ToR11> show configuration policy-options
policy-statement LO {
    term 1 {
        from {
            protocol direct;
            route-filter 192.0.2.11/32 exact;
        }
        then accept;
    }
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-VXLAN routing instances for each virtual network are properly configured.

user@ToR11> show configuration routing-instances
EVPN-VXLAN-1 {
    vtep-source-interface lo0.81;
    instance-type virtual-switch;
    interface ge-1/0/6.0;
    interface ae0.0;
    route-distinguisher 192.0.2.11:1;
    vrf-target target:1:1;
    protocols {
        evpn {
            traceoptions {
                file TOR11-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            vxlan {
                vni 5;
            }
        }
    }
}

Purpose

Verify that ToR12 is properly configured.

Action

Verify that the logical system interfaces and bridge domains on the CE1 and CE3 devices are properly configured to enable Layer 2 connectivity.

user@ToR12> show configuration logical-systems
CE-1 {
    interfaces {
        ge-1/0/9 {
            unit 0 {
                description "CONNECTED TO Host 1";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ae1 {
            unit 0 {
                description "CONNECTED TO ToR12";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}

user@ToR12> show configuration logical-systems

CE-3 {
    interfaces {
        ge-1/1/7 {
            unit 0 {
                description "CONNECTED TO ToR12";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ge-1/1/9 {
            unit 0 {
                description "CONNECTED TO Host 3";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}

Verify that the interfaces and trace options on ToR12 are configured properly to enable underlay connectivity to other ToR and gateway and WAN edge devices.

user@ToR12>show configuration interfaces
traceoptions {
    file ToR12-DCD.log size 10m;
    flag all;
}
ge-1/0/0 {
    unit 0 {
        description "CONNECTED TO MX11";
        family inet {
            address 192.168.6.1/24;
        }
    }
}
ge-1/0/4 {
    unit 0 {
        description "CONNECTED TO MX12";
        family inet {
            address 192.168.5.1/24;
        }
    }
}
ge-1/0/6 {
    description "CONNECTED TO CE-1";
    gigether-options {
        802.3ad ae0;
    }
}
ge-1/0/7 {
    unit 0 {
        description "CONNECTED TO CE-3";
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ge-1/1/0 {
    description "CONNECTED TO ToR11";
    gigether-options {
        802.3ad ae1;
    }
}
ge-1/1/3 {
    unit 0 {
        description "CONNECTED TO ToR11";
        family inet {
            address 192.168.2.2/24;
        }
    }
}
ge-1/1/6 {
    description "CONNECTED TO ToR12";
    gigether-options {
        802.3ad ae1;
    }
}
ae0 {
    esi {
        00:11:11:11:11:11:11:11:11:11;
        all-active;
    }
    aggregated-ether-options {
        lacp {
            system-id 11:11:11:11:11:11;
        }
    }
    unit 0 {
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ae1 {
    aggregated-ether-options {
        lacp {
            active;
            periodic fast;
        }
    }
}
lo0 {
    unit 82 {
        family inet {
            address 192.0.2.12/32;
        }
    }
}

Verify that the routing and load balancing options are properly configured.

user@ToR12> show configuration routing-options
router-id 192.0.2.12;
autonomous-system 65200;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and Layer 2 address learning and forwarding properties are properly configured.

user@ToR12> show configuration protocols
bgp {
    local-as 65200;
    group MX11 {
        type external;
        local-address 192.168.6.1;
        export [ LO TEST ];
        peer-as 65400;
        local-as 65200;
        neighbor 192.168.6.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX12 {
        type external;
        local-address 192.168.5.1;
        export [ LO TEST ];
        peer-as 65500;
        local-as 65200;
        neighbor 192.168.5.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR11 {
        type external;
        local-address 192.168.2.2;
        export [ LO TEST ];
        peer-as 65100;
        local-as 65200;
        neighbor 192.168.2.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.12;
        export TEST;
        peer-as 65400;
        local-as 65200;
        neighbor 192.0.2.21 {
            family evpn {
                signaling;
            }
        }
    }
    group MX12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.12;
        export TEST;
        peer-as 65500;
        local-as 65200;
        neighbor 192.0.2.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.12;
        export TEST;
        peer-as 65100;
        local-as 65200;
        neighbor 192.0.2.11 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR12-EVPN {
        export TEST;
    }
}
l2-learning {
    traceoptions {
        file TOR12-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@ToR12> show configuration policy-options
policy-statement LO {
    term 1 {
        from {
            protocol direct;
            route-filter 192.0.2.12/32 exact;
        }
        then accept;
    }
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-VXLAN routing instances for each virtual network are properly configured.

user@ToR12> show configuration routing-instances
EVPN-VXLAN-1 {
    vtep-source-interface lo0.82;
    instance-type virtual-switch;
    interface ge-1/0/7.0;
    interface ae0.0;
    route-distinguisher 192.0.2.12:1;
    vrf-target target:1:1;
    protocols {
        evpn {
            traceoptions {
                file TOR12-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            vxlan {
                vni 5;
            }
        }
    }
}

Purpose

Verify that MX11 is properly configured.

Action

Verify that the interfaces on the MX11 router (DC GW/WAN Edge1) are configured for the following:

Underlay connectivity to the MX12, ToR11, ToR12, and P devices, which is the EVPN-VXLAN part of DC1 network.

user@MX11> show configuration interfaces
traceoptions {
    file MX11-DCD.log size 10m;
    flag all;
}
ge-1/1/1 {
    unit 0 {
        description "CONNECTED TO ToR11";
        family inet {
            address 192.168.3.2/24;
        }
    }
}
ge-5/1/0 {
    unit 0 {
        description "CONNECTED TO MX12";
        family inet {
            address 192.168.7.1/24;
        }
    }
}
ge-5/1/8 {
    unit 0 {
        description "CONNECTED TO ToR12";
        family inet {
            address 192.168.6.2/24;
        }
    }
}
ge-5/1/9 {
    unit 0 {
        description "CONNECTED TO P";
        family inet {
            address 203.0.1.1/24;
        }
        family mpls;
    }
}

Integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

user@MX11> show configuration interfaces
irb {
    unit 1 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:aa:aa:aa:aa:aa:aa:aa:aa;
            all-active;
        }
        family inet {
            address 10.11.1.12/24 {
                virtual-gateway-address 10.11.1.10;
            }
        }
    }
    unit 2 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:bb:bb:bb:bb:bb:bb:bb:bb;
            all-active;
        }
        family inet {
            address 10.12.1.12/24 {
                virtual-gateway-address 10.12.1.10;
            }
        }
    }
    unit 3 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:cc:cc:cc:cc:cc:cc:cc:cc;
            all-active;
        }
        family inet {
            address 10.13.1.12/24 {
                virtual-gateway-address 10.13.1.10;
            }
        }
    }
    unit 4 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:dd:dd:dd:dd:dd:dd:dd:dd;
            all-active;
        }
        family inet {
            address 10.14.1.12/24 {
                virtual-gateway-address 10.14.1.10;
            }
        }
    }
    unit 5 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:ee:ee:ee:ee:ee:ee:ee:ee;
            all-active;
        }
        family inet {
            address 10.15.1.12/24 {
                virtual-gateway-address 10.15.1.10;
            }
        }
    }
}

An ESI value and active-active multihoming on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

user@MX11> show configuration interfaces
lt-5/1/0 {
    esi {
        00:22:22:22:22:22:22:22:22:22;
        all-active;
    }
}

A pair of logical tunnel (lt-) interfaces on the MX11 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

user@MX11> show configuration interfaces
lt-5/1/0 {
    unit 0 {
        peer-unit 1;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
    unit 1 {
        peer-unit 0;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}

Loopback interface address.

user@MX11> show configuration interfaces
lo0 {
    unit 84 {
        family inet {
            address 192.0.2.21/32;
        }
        family mpls;
    }
}

Verify that the routing options and load balancing are properly configured.

user@MX11> show configuration routing-options
router-id 192.0.2.21;
autonomous-system 65300;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and RSVP, MPLS, BGP, and OSPF protocols are properly configured.

user@MX11> show configuration protocols
rsvp {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
mpls {
    label-switched-path MX11-TO-MX12 {
        to 192.0.2.22;
    }
    label-switched-path MX11-TO-P {
        to 203.0.113.1;
    }
    label-switched-path MX11-TO-MX21 {
        to 198.51.100.21;
    }
    label-switched-path MX11-TO-MX22 {
        to 198.51.100.22;
    }
    interface all;
    interface fxp0.0 {
        disable;
    }
}
bgp {
    local-address 192.0.2.21;
    local-as 65300;
    group INT {
        type internal;
        local-address 192.0.2.21;
        family evpn {
            signaling;
        }
        export TEST;
        neighbor 203.0.113.1;
    }
    group MX12 {
        type external;
        local-address 192.168.7.1;
        export [ TEST LO ];
        peer-as 65500;
        local-as 65400;
        neighbor 192.168.7.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR11 {
        type external;
        local-address 192.168.3.2;
        import TEST;
        export [ TEST LO ];
        peer-as 65100;
        local-as 65400;
        neighbor 192.168.3.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR12 {
        type external;
        local-address 192.168.6.2;
        export [ TEST LO ];
        peer-as 65200;
        local-as 65400;
        neighbor 192.168.6.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.21;
        export TEST;
        peer-as 65500;
        local-as 65400;
        neighbor 192.0.2.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.21;
        export TEST;
        peer-as 65100;
        local-as 65400;
        neighbor 192.0.2.11 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.21;
        export TEST;
        peer-as 65200;
        local-as 65400;
        neighbor 192.0.2.12 {
            family evpn {
                signaling;
            }
        }
    }
}
ospf {
    traffic-engineering;
    area 0.0.0.0 {
        interface ge-5/1/9.0;
        interface lo0.84 {
            passive;
        }
    }
}
l2-learning {
    traceoptions {
        file MX11-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@MX11> show configuration policy-options
policy-statement LO {
    from {
        protocol direct;
        route-filter 192.0.2.21/32 exact;
    }
    then accept;
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-based MPLS routing instances and EVPN-VXLAN routing instances are properly configured.

user@MX11> show configuration routing-instances
EVPN-MPLS-1 {
    instance-type virtual-switch;
    interface lt-5/1/0.0;
    route-distinguisher 192.0.2.21:100;
    vrf-target target:1:2;
    protocols {
        evpn {
            traceoptions {
                file MX11-EVPN-MPLS-1.log size 10m;
                flag all;
            }
            extended-vlan-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
        }
    }
}
EVPN-VXLAN-1 {
    vtep-source-interface lo0.84;
    instance-type virtual-switch;
    interface lt-5/1/0.1;
    route-distinguisher 192.0.2.21:1;
    vrf-target target:1:1;
    protocols {
        evpn {
            traceoptions {
                file MX11-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            routing-interface irb.1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            routing-interface irb.2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            routing-interface irb.3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            routing-interface irb.4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            routing-interface irb.5;
            vxlan {
                vni 5;
            }
        }
    }
}
VRF {
    instance-type vrf;
    interface irb.1;
    interface irb.2;
    interface irb.3;
    interface irb.4;
    interface irb.5;
    route-distinguisher 1:1;
    vrf-target target:10:10;
}

Purpose

Verify that MX12 is properly configured.

Action

Verify that the interfaces on the MX12 router (DC GW/WAN Edge2) are configured for the following:

Underlay connectivity to the MX11, ToR11, ToR12, and P devices, which is the EVPN-VXLAN part of DC1 network.

user@MX12> show configuration interfaces
traceoptions {
    file MX12-DCD.log size 10m;
    flag all;
}
ge-1/0/4 {
    unit 0 {
        description "CONNECTED TO ToR12";
        family inet {
            address 192.168.5.2/24;
        }
    }
}
ge-1/0/5 {
    unit 0 {
        description "CONNECTED TO ToR11";
        family inet {
            address 192.168.4.2/24;
        }
    }
}
ge-1/0/6 {
    unit 0 {
        description "CONNECTED TO P";
        family inet {
            address 203.0.113.11/24;
        }
        family mpls;
    }
}
ge-1/1/0 {
    unit 0 {
        description "CONNECTED TO MX11";
        family inet {
            address 192.168.7.2/24;
        }
    }
}

Integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

user@MX12> show configuration interfaces
irb {
    unit 1 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:aa:aa:aa:aa:aa:aa:aa:aa;
            all-active;
        }
        family inet {
            address 10.11.1.13/24 {
                virtual-gateway-address 10.11.1.10;
            }
        }
    }
    unit 2 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:bb:bb:bb:bb:bb:bb:bb:bb;
            all-active;
        }
        family inet {
            address 10.12.1.13/24 {
                virtual-gateway-address 10.12.1.10;
            }
        }
    }
    unit 3 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:cc:cc:cc:cc:cc:cc:cc:cc;
            all-active;
        }
        family inet {
            address 10.13.1.13/24 {
                virtual-gateway-address 10.13.1.10;
            }
        }
    }
    unit 4 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:dd:dd:dd:dd:dd:dd:dd:dd;
            all-active;
        }
        family inet {
            address 10.14.1.13/24 {
                virtual-gateway-address 10.14.1.10;
            }
        }
    }
    unit 5 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:11:ee:ee:ee:ee:ee:ee:ee:ee;
            all-active;
        }
        family inet {
            address 10.15.1.13/24 {
                virtual-gateway-address 10.15.1.10;
            }
        }
    }
}

An ESI value and active-active multihoming on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

user@MX12> show configuration interfaces
lt-1/0/0 {
    esi {
        00:22:22:22:22:22:22:22:22:22;
        all-active;
    }
}

A pair of logical tunnel (lt-) interfaces on the MX12 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

user@MX12> show configuration interfaces
lt-1/0/0 {
    unit 0 {
        peer-unit 1;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
    unit 1 {
        peer-unit 0;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}

Loopback interface address.

user@MX12> show configuration interfaces
lo0 {
    unit 85 {
        family inet {
            address 192.0.2.22/32;
        }
        family mpls;
    }
}
}

Verify that the routing options and load balancing are properly configured.

user@MX12> show configuration routing-options
router-id 192.0.2.22;
autonomous-system 65300;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and RSVP, MPLS, BGP, and OSPF protocols are properly configured.

user@MX12> show configuration protocols
rsvp {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
mpls {
    label-switched-path MX12-TO-MX11 {
        to 192.0.2.21;
    }
    label-switched-path MX12-TO-P {
        to 203.0.113.1;
    }
    label-switched-path MX12-TO-MX21 {
        to 198.51.100.21;
    }
    label-switched-path MX12-TO-MX22 {
        to 198.51.100.22;
    }
    interface all;
    interface fxp0.0 {
        disable;
    }
}
bgp {
    local-address 192.0.2.22;
    local-as 65300;
    group INT {
        type internal;
        family evpn {
            signaling;
        }
        export TEST;
        neighbor 203.0.113.1;
    }
    group MX11 {
        type external;
        local-address 192.168.7.2;
        export [ TEST LO ];
        peer-as 65400;
        local-as 65500;
        neighbor 192.168.7.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR11 {
        type external;
        local-address 192.168.4.2;
        export [ TEST LO ];
        peer-as 65100;
        local-as 65500;
        neighbor 192.168.4.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR12 {
        type external;
        local-address 192.168.5.2;
        export [ TEST LO ];
        peer-as 65200;
        local-as 65500;
        neighbor 192.168.5.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.22;
        export TEST;
        peer-as 65400;
        local-as 65500;
        neighbor 192.0.2.21 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR11-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.22;
        export TEST;
        peer-as 65100;
        local-as 65500;
        neighbor 192.0.2.11 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR12-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 192.0.2.22;
        export TEST;
        peer-as 65200;
        local-as 65500;
        neighbor 192.0.2.12 {
            family evpn {
                signaling;
            }
        }
    }
}
ospf {
    traffic-engineering;
    area 0.0.0.0 {
        interface ge-1/0/6.0;
        interface lo0.85 {
            passive;
        }
    }
}
l2-learning {
    traceoptions {
        file MX12-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@MX12> show configuration policy-options
policy-statement LO {
    from {
        protocol direct;
        route-filter 192.0.2.22/32 exact;
    }
    then accept;
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-based MPLS routing instances and EVPN-VXLAN routing instances are properly configured.

user@MX12> show configuration routing-instances
EVPN-MPLS-1 {
    instance-type virtual-switch;
    interface lt-1/0/0.0;
    route-distinguisher 192.0.2.22:100;
    vrf-target target:1:2;
    protocols {
        evpn {
            traceoptions {
                file MX12-EVPN-MPLS-1.log size 10m;
                flag all;
            }
            extended-vlan-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
        }
    }
}
EVPN-VXLAN-1 {
    vtep-source-interface lo0.85;
    instance-type virtual-switch;
    interface lt-1/0/0.1;
    route-distinguisher 192.0.2.22:1;
    vrf-target target:1:1;
    protocols {
        evpn {
            traceoptions {
                file MX12-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            routing-interface irb.1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            routing-interface irb.2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            routing-interface irb.3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            routing-interface irb.4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            routing-interface irb.5;
            vxlan {
                vni 5;
            }
        }
    }
}
VRF {
    instance-type vrf;
    interface irb.1;
    interface irb.2;
    interface irb.3;
    interface irb.4;
    interface irb.5;
    route-distinguisher 1:1;
    vrf-target target:10:10;
}

Purpose

Verify that MX21 is properly configured.

Action

Verify that the interfaces on the MX21 router (DC GW/WAN Edge3) are configured for the following:

Underlay connectivity to the MX22, ToR21, ToR22, and P devices, which is the EVPN-VXLAN part of DC1 network.

user@MX21> show configuration interfaces
ge-3/0/0 {
    unit 0 {
        description "CONNECTED TO MX22";
        family inet {
            address 192.168.13.1/24;
        }
    }
}
ge-3/1/0 {
    unit 0 {
        description "CONNECTED TO ToR22";
        family inet {
            address 192.168.8.1/24;
        }
    }
}
ge-5/0/0 {
    unit 0 {
        description "CONNECTED TO P";
        family inet {
            address 203.0.113.31/24;
        }
        family mpls;
    }
}
ge-5/0/1 {
    unit 0 {
        description "CONNECTED TO ToR21";
        family inet {
            address 192.168.9.1/24;
        }
    }
}

Integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

user@MX21> show configuration interfaces
irb {
    unit 1 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:aa:aa:aa:aa:aa:aa:aa:aa;
            all-active;
        }
        family inet {
            address 10.11.1.14/24 {
                virtual-gateway-address 10.11.1.11;
            }
        }
    }
    unit 2 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:bb:bb:bb:bb:bb:bb:bb:bb;
            all-active;
        }
        family inet {
            address 10.12.1.14/24 {
                virtual-gateway-address 10.12.1.11;
            }
        }
    }
    unit 3 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:cc:cc:cc:cc:cc:cc:cc:cc;
            all-active;
        }
        family inet {
            address 10.13.1.14/24 {
                virtual-gateway-address 10.13.1.11;
            }
        }
    }
    unit 4 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:dd:dd:dd:dd:dd:dd:dd:dd;
            all-active;
        }
        family inet {
            address 10.14.1.14/24 {
                virtual-gateway-address 10.14.1.11;
            }
        }
    }
    unit 5 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:ee:ee:ee:ee:ee:ee:ee:ee;
            all-active;
        }
        family inet {
            address 10.15.1.14/24 {
                virtual-gateway-address 10.15.1.11;
            }
        }
    }
}

An ESI value and active-active multihoming on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

user@MX21> show configuration interfaces
lt-5/0/0 {
    esi {
        00:33:33:33:33:33:33:33:33:33;
        all-active;
    }
}

A pair of logical tunnel (lt-) interfaces on the MX21 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

user@MX21> show configuration interfaces
lt-5/0/0 {
    unit 0 {
        peer-unit 1;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
    unit 1 {
        peer-unit 0;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}

Loopback interface address.

user@MX21> show configuration interfaces
lo0 {
    unit 87 {
        family inet {
            address 198.51.100.21/32;
        }
        family mpls;
    }
}

Verify that the routing options and load balancing are properly configured.

user@MX21> show configuration routing-options
router-id 198.51.100.21;
autonomous-system 65300;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and RSVP, MPLS, BGP, and OSPF protocols are properly configured.

user@MX21> show configuration protocols
rsvp {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
mpls {
    label-switched-path MX21-TO-MX11 {
        to 192.0.2.21;
    }
    label-switched-path MX21-TO-MX12 {
        to 192.0.2.22;
    }
    label-switched-path MX21-TO-MX22 {
        to 198.51.100.22;
    }
    label-switched-path MX21-TO-P {
        to 203.0.113.1;
    }
    interface all;
    interface fxp0.0 {
        disable;
    }
}
bgp {
    local-address 198.52.100.21;
    local-as 65300;
    group INT {
        type internal;
        local-address 198.51.100.21;
        family evpn {
            signaling;
        }
        export TEST;
        neighbor 203.0.113.1;
    }
    group MX22 {
        type external;
        local-address 192.168.13.1;
        export [ TEST LO ];
        peer-as 64900;
        local-as 64800;
        neighbor 192.168.13.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR21 {
        type external;
        local-address 192.168.9.1;
        export [ TEST LO ];
        peer-as 64600;
        local-as 64800;
        neighbor 192.168.9.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR22 {
        type external;
        local-address 192.168.8.1;
        export [ TEST LO ];
        peer-as 64700;
        local-as 64800;
        neighbor 192.168.8.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.21;
        peer-as 64900;
        local-as 64800;
        neighbor 198.51.100.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.21;
        peer-as 64600;
        local-as 64800;
        neighbor 198.51.100.11 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.21;
        peer-as 64700;
        local-as 64800;
        neighbor 198.51.100.12 {
            family evpn {
                signaling;
            }
        }
    }
}
ospf {
    traffic-engineering;
    area 0.0.0.0 {
        interface ge-5/0/0.0;
        interface lo0.87 {
            passive;
        }
    }
}
l2-learning {
    traceoptions {
        file MX21-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@MX21> show configuration policy-options
policy-statement LO {
    from {
        protocol direct;
        route-filter 198.51.100.21/32 exact;
    }
    then accept;
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-based MPLS routing instances and EVPN-VXLAN routing instances are properly configured.

user@MX21> show configuration routing-instances
EVPN-MPLS-1 {
    instance-type virtual-switch;
    interface lt-5/0/0.0;
    route-distinguisher 198.51.100.21:100;
    vrf-target target:1:2;
    protocols {
        evpn {
            traceoptions {
                file MX21-EVPN-MPLS-1.log size 10m;
                flag all;
            }
            extended-vlan-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
        }
    }
}
EVPN-VXLAN-1 {
    vtep-source-interface lo0.87;
    instance-type virtual-switch;
    interface lt-5/0/0.1;
    route-distinguisher 198.51.100.21:1;
    vrf-target target:1:3;
    protocols {
        evpn {
            traceoptions {
                file MX21-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            routing-interface irb.1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            routing-interface irb.2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            routing-interface irb.3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            routing-interface irb.4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            routing-interface irb.5;
            vxlan {
                vni 5;
            }
        }
    }
}
VRF {
    instance-type vrf;
    interface irb.1;
    interface irb.2;
    interface irb.3;
    interface irb.4;
    interface irb.5;
    route-distinguisher 1:1;
    vrf-target target:10:10;
}

Purpose

Verify that MX22 is properly configured.

Action

Verify that the interfaces on the MX22 router (DC GW/WAN Edge4) are configured for the following:

Underlay connectivity to the MX21, ToR21, ToR22, and P devices, which is the EVPN-VXLAN part of DC1 network.

user@MX22> show configuration interfaces
xe-0/0/0 {
    unit 0 {
        description "CONNECTED TO ToR22";
        family inet {
            address 192.168.11.1/24;
        }
    }
}
xe-0/0/1 {
    unit 0 {
        description "CONNECTED TO ToR21";
        family inet {
            address 192.168.10.1/24;
        }
    }
}
ge-1/0/0 {
    unit 0 {
        description "CONNECTED TO MX21";
        family inet {
            address 192.168.13.2/24;
        }
    }
}
ge-1/0/2 {
    unit 0 {
        description "CONNECTED TO P";
        family inet {
            address 203.0.113.51/24;
        }
        family mpls;
    }
}

Integrated routing and bridging (IRB) interfaces that advertise the MAC and IP routes (MAC+IP type 2 routes) for hosts in the topology. The IRB configuration is the gateway for the VLANs on the hosts.

user@MX22> show configuration interfaces
irb {
    unit 1 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:aa:aa:aa:aa:aa:aa:aa:aa;
            all-active;
        }
        family inet {
            address 10.11.1.15/24 {
                virtual-gateway-address 10.11.1.11;
            }
        }
    }
    unit 2 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:bb:bb:bb:bb:bb:bb:bb:bb;
            all-active;
        }
        family inet {
            address 10.12.1.15/24 {
                virtual-gateway-address 10.12.1.11;
            }
        }
    }
    unit 3 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:cc:cc:cc:cc:cc:cc:cc:cc;
            all-active;
        }
        family inet {
            address 10.13.1.15/24 {
                virtual-gateway-address 10.13.1.11;
            }
        }
    }
    unit 4 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:dd:dd:dd:dd:dd:dd:dd:dd;
            all-active;
        }
        family inet {
            address 10.14.1.15/24 {
                virtual-gateway-address 10.14.1.11;
            }
        }
    }
    unit 5 {
        proxy-macip-advertisement;
        virtual-gateway-esi {
            00:22:ee:ee:ee:ee:ee:ee:ee:ee;
            all-active;
        }
        family inet {
            address 10.15.1.15/24 {
                virtual-gateway-address 10.15.1.11;
            }
        }
    }
}

An ESI value and active-active multihoming on the logical tunnel interface. Use the same ESI value on all other gateway/WAN edge routers in the DC1 network.

user@MX22> show configuration interfaces
lt-1/0/0 {
    esi {
        00:33:33:33:33:33:33:33:33:33;
        all-active;
    }
}

A pair of logical tunnel (lt-) interfaces on the MX22 gateway router to interconnect the EVPN-VXLAN instance of the data center network with the MPLS-based EVPN instance of the WAN. One logical tunnel (lt-) interface is configured as the access interface for EVPN-VXLAN and the other logical tunnel (lt-) interface is configured as the access interface for MPLS-based EVPN.

user@MX22> show configuration interfaces
lt-1/0/0 {
    unit 0 {
        peer-unit 1;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
    unit 1 {
        peer-unit 0;
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}

Loopback interface address.

user@MX22> show configuration interfaces
lo0 {
    unit 88 {
        family inet {
            address 198.51.100.22/32;
        }
        family mpls;
    }
}

Verify that the routing options and load balancing are properly configured.

user@MX22> show configuration routing-options
router-id 198.51.100.22;
autonomous-system 65300;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and RSVP, MPLS, BGP, and OSPF protocols are properly configured.

user@MX22> show configuration protocols
rsvp {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
mpls {
    label-switched-path MX22-TO-MX11 {
        to 192.0.2.21;
    }
    label-switched-path MX22-TO-MX12 {
        to 192.0.2.22;
    }
    label-switched-path MX22-TO-MX21 {
        to 198.51.100.21;
    }
    label-switched-path MX22-TO-P {
        to 203.0.113.1;
    }
    interface all;
    interface fxp0.0 {
        disable;
    }
}
bgp {
    local-address 198.51.100.22;
    local-as 65300;
    group INT {
        type internal;
        family evpn {
            signaling;
        }
        export TEST;
        neighbor 203.0.113.1;
    }
    group MX21 {
        type external;
        local-address 192.168.13.2;
        export [ TEST LO ];
        peer-as 64800;
        local-as 64900;
        neighbor 192.168.13.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR21 {
        type external;
        local-address 192.168.10.1;
        export [ TEST LO ];
        peer-as 64600;
        local-as 64900;
        neighbor 192.168.10.2 {
            family inet {
                unicast;
            }
        }
    }
    group ToR22 {
        type external;
        local-address 192.168.11.1;
        export [ TEST LO ];
        peer-as 64700;
        local-as 64900;
        neighbor 192.168.11.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.22;
        peer-as 64800;
        local-as 64900;
        neighbor 198.51.100.21 {
            family evpn {
                signaling;
            }
        }
    }
}
    group ToR21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.22;
        peer-as 64600;
        local-as 64900;
        neighbor 198.51.100.11 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.22;
        peer-as 64700;
        local-as 64900;
        neighbor 198.51.100.12 {
            family evpn {
                signaling;
            }
        }
    }
ospf {
    traffic-engineering;
    area 0.0.0.0 {
        interface ge-1/0/2.0;
        interface lo0.88 {
            passive;
        }
    }
}
l2-learning {
    traceoptions {
        file MX22-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@MX22> show configuration policy-options
policy-statement LO {
    from {
        protocol direct;
        route-filter 198.51.100.22/32 exact;
    }
    then accept;
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-based MPLS routing instances and EVPN-VXLAN routing instances are properly configured.

user@MX22> show configuration routing-instances
EVPN-MPLS-1 {
    instance-type virtual-switch;
    interface lt-1/0/0.0;
    route-distinguisher 198.51.100.22:100;
    vrf-target target:1:2;
    protocols {
        evpn {
            traceoptions {
                file MX22-EVPN-MPLS-1.log size 10m;
                flag all;
            }
            extended-vlan-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
        }
    }
}
EVPN-VXLAN-1 {
    vtep-source-interface lo0.88;
    instance-type virtual-switch;
    interface lt-1/0/0.1;
    route-distinguisher 198.51.100.22:1;
    vrf-target target:1:3;
    protocols {
        evpn {
            traceoptions {
                file MX22-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
            default-gateway no-gateway-community;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            routing-interface irb.1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            routing-interface irb.2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            routing-interface irb.3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            routing-interface irb.4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            routing-interface irb.5;
            vxlan {
                vni 5;
            }
        }
    }
}
VRF {
    instance-type vrf;
    interface irb.1;
    interface irb.2;
    interface irb.3;
    interface irb.4;
    interface irb.5;
    route-distinguisher 1:1;
    vrf-target target:10:10;
}

Purpose

Verify that ToR21 is properly configured.

Action

Verify that the logical system interfaces and bridge domains on the CE4 device are properly configured to enable Layer 2 connectivity and to handle inter-VXLAN traffic.

user@ToR21> show configuration logical-systems
CE-4 {
    interfaces {
        ge-1/0/9 {
            unit 0 {
                description "CONNECTED TO Host 4";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ge-1/1/6 {
            unit 0 {
                description "CONNECTED TO ToR21";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}

Verify that the interfaces and trace options on ToR21 are configured properly to enable underlay connectivity to other ToR and gateway and WAN edge devices.

user@ToR21>show configuration interfaces
traceoptions {
    file ToR21-DCD.log size 10m;
    flag all;
}
xe-0/0/0 {
    unit 0 {
        description "CONNECTED TO MX22";
        family inet {
            address 192.168.10.2/24;
        }
    }
}
ge-1/0/0 {
    description "CONNECTED TO CE-5";
    gigether-options {
        802.3ad ae0;
    }
}
ge-1/0/1 {
    unit 0 {
        description "CONNECTED TO MX21";
        family inet {
            address 192.168.9.2/24;
        }
    }
}
ge-1/0/6 {
    unit 0 {
        description "CONNECTED TO CE-4";
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ge-1/1/3 {
    unit 0 {
        description "CONNECTED TO ToR22";
        family inet {
            address 192.168.12.1/24;
        }
    }
}
ae0 {
    esi {
        00:44:44:44:44:44:44:44:44:44;
        all-active;
    }
    aggregated-ether-options {
        lacp {
            active;
            periodic fast;
            system-id 22:22:22:22:22:22;
        }
    }
    unit 0 {
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
lo0 {
    unit 90 {
        family inet {
            address 198.51.100.11/32;
        }
    }
}

Verify that the routing and load balancing options are properly configured.

user@ToR21> show configuration routing-options
router-id 198.51.100.11;
autonomous-system 64600;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and Layer 2 address learning and forwarding properties are properly configured.

user@ToR21> show configuration protocols
bgp {
    export TEST;
    local-as 64600;
    group MX21 {
        type external;
        local-address 192.168.9.2;
        export [ LO TEST ];
        peer-as 64800;
        local-as 64600;
        neighbor 192.168.9.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX22 {
        type external;
        local-address 192.168.10.2;
        export [ LO TEST ];
        peer-as 64900;
        local-as 64600;
        neighbor 192.168.10.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR22 {
        type external;
        local-address 192.168.12.1;
        export [ LO TEST ];
        peer-as 64700;
        local-as 64600;
        neighbor 192.168.12.2 {
            family inet {
                unicast;
            }
        }
    }
    group MX21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.11;
        peer-as 64800;
        local-as 64600;
        neighbor 198.51.100.21 {
            family evpn {
                signaling;
            }
        }
    }
    group MX22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.11;
        peer-as 64900;
        local-as 64600;
        neighbor 198.51.100.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.11;
        peer-as 64700;
        local-as 64600;
        neighbor 198.51.100.12 {
            family evpn {
                signaling;
            }
        }
    }
}
l2-learning {
    traceoptions {
        file TOR21-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@ToR21> show configuration policy-options
policy-statement LO {
    term 1 {
        from {
            protocol direct;
            route-filter 198.51.100.11/32 exact;
        }
        then accept;
    }
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-VXLAN routing instances for each virtual network are properly configured.

user@ToR21> show configuration routing-instances
EVPN-VXLAN-1 {
    vtep-source-interface lo0.90;
    instance-type virtual-switch;
    interface ge-1/0/6.0;
    interface ae0.0;
    route-distinguisher 198.51.100.11:1;
    vrf-target target:1:3;
    protocols {
        evpn {
            traceoptions {
                file TOR21-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            vxlan {
                vni 5;
            }
        }
    }
}

Purpose

Verify that ToR22 is properly configured.

Action

Verify that the logical system interfaces and bridge domains on the CE5 and CE6 devices are properly configured to enable Layer 2 connectivity and to handle inter-VXLAN traffic.

user@ToR22> show configuration logical-systems
CE-5 {
    interfaces {
        ge-1/0/9 {
            unit 0 {
                description "CONNECTED TO Host 5";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ae1 {
            unit 0 {
                description "CONNECTED TO ToR21";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
       
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}
user@ToR22> show configuration logical-systems

CE-6 {
    interfaces {
        ge-1/1/6 {
            unit 0 {
                description "CONNECTED TO ToR22";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
        }
        ge-1/1/9 {
            unit 0 {
                description "CONNECTED TO Host 6";
                family bridge {
                    interface-mode trunk;
                    vlan-id-list 1-5;
                }
            }
      }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            
        }
    }
}

Verify that the interfaces and trace options on ToR22 are configured properly to enable underlay connectivity to other ToR and gateway and WAN edge devices.

user@ToR22>show configuration interfaces
traceoptions {
    file ToR22-DCD.log size 10m;
    flag all;
}
xe-0/0/0 {
    unit 0 {
        description "CONNECTED TO MX22";
        family inet {
            address 192.168.11.2/24;
        }
    }
}
ge-1/0/0 {
    description "CONNECTED TO ToR21";
    gigether-options {
        802.3ad ae1;
    }
}
ge-1/0/6 {
    unit 0 {
        description "CONNECTED TO CE-6";
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ge-1/0/7 {
    description "CONNECTED TO ToR22";
    gigether-options {
        802.3ad ae1;
    }
}
ge-1/1/0 {
    unit 0 {
        description "CONNECTED TO MX21";
        family inet {
            address 192.168.8.2/24;
        }
    }
}
ge-1/1/3 {
    unit 0 {
        description "CONNECTED TO ToR21";
        family inet {
            address 192.168.12.2/24;
        }
    }
}
ge-1/1/7 {
    description "CONNECTED TO CE-5";
    gigether-options {
        802.3ad ae0;
    }
}
ae0 {
    esi {
        00:44:44:44:44:44:44:44:44:44;
        all-active;
    }
    aggregated-ether-options {
        lacp {
            active;
            periodic fast;
            system-id 22:22:22:22:22:22;
        }
    }
    unit 0 {
        family bridge {
            interface-mode trunk;
            vlan-id-list 1-5;
        }
    }
}
ae1 {
    aggregated-ether-options {
        lacp {
            active;
            periodic fast;
            system-id 22:22:22:22:22:22;
        }
    }
}
lo0 {
    unit 92 {
        family inet {
            address 198.51.100.12/32;
        }
    }
}

Verify that the routing and load balancing options are properly configured.

user@ToR22> show configuration routing-options
router-id 198.51.100.12;
autonomous-system 64700;
forwarding-table {
    export evpn-pplb;
}

Verify that external BGP (EBGP) underlay and overlay protocols and Layer 2 address learning and forwarding properties are properly configured.

user@ToR22> show configuration protocols
bgp {
    export TEST;
    local-as 64700;
    group MX21 {
        type external;
        local-address 192.168.8.2;
        export [ LO TEST ];
        peer-as 64800;
        local-as 64700;
        neighbor 192.168.8.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX22 {
        type external;
        local-address 192.168.11.2;
        export [ LO TEST ];
        peer-as 64900;
        local-as 64700;
        neighbor 192.168.11.1 {
            family inet {
                unicast;
            }
        }
    }
    group ToR21 {
        type external;
        local-address 192.168.12.2;
        export [ LO TEST ];
        peer-as 64600;
        local-as 64700;
        neighbor 192.168.12.1 {
            family inet {
                unicast;
            }
        }
    }
    group MX21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.12;
        peer-as 64800;
        local-as 64700;
        neighbor 198.51.100.21 {
            family evpn {
                signaling;
            }
        }
    }
    group MX22-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.12;
        peer-as 64900;
        local-as 64700;
        neighbor 198.51.100.22 {
            family evpn {
                signaling;
            }
        }
    }
    group ToR21-EVPN {
        type external;
        multihop {
            ttl 2;
            no-nexthop-change;
        }
        local-address 198.51.100.12;
        peer-as 64600;
        local-as 64700;
        neighbor 198.51.100.11 {
            family evpn {
                signaling;
            }
        }
    }
}
l2-learning {
    traceoptions {
        file TOR22-L2ALD.log size 10m;
        level all;
        flag all;
    }
}

Verify that the routing policies for the loopback address, load balancing, and TEST policies, and the community policy options are properly configured.

user@ToR22> show configuration policy-options

policy-statement LO {
    term 1 {
        from {
            protocol direct;
            route-filter 198.51.100.12/32 exact;
        }
        then accept;
    }
}
policy-statement TEST {
    then {
        community add NO-EXPORT;
    }
}
policy-statement evpn-pplb {
    from protocol evpn;
    then {
        load-balance per-packet;
    }
}
community NO-EXPORT members [ no-advertise no-export no-export-subconfed ];

Verify that the EVPN-VXLAN routing instances for each virtual network are properly configured.

user@ToR22> show configuration routing-instances
EVPN-VXLAN-1 {
    vtep-source-interface lo0.92;
    instance-type virtual-switch;
    interface ge-1/0/6.0;
    interface ae0.0;
    route-distinguisher 198.51.100.12:1;
    vrf-target target:1:3;
    protocols {
        evpn {
            traceoptions {
                file TOR22-EVPN-VXLAN-1.log size 10m;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list 1-5;
        }
    }
    bridge-domains {
        BD-1 {
            domain-type bridge;
            vlan-id 1;
            vxlan {
                vni 1;
            }
        }
        BD-2 {
            domain-type bridge;
            vlan-id 2;
            vxlan {
                vni 2;
            }
        }
        BD-3 {
            domain-type bridge;
            vlan-id 3;
            vxlan {
                vni 3;
            }
        }
        BD-4 {
            domain-type bridge;
            vlan-id 4;
            vxlan {
                vni 4;
            }
        }
        BD-5 {
            domain-type bridge;
            vlan-id 5;
            vxlan {
                vni 5;
            }
        }
    }
}