Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

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

This example shows how to interconnect EVPN-VXLAN data center networks through a WAN running EVPN-MPLS to leverage the benefits of EVPN as a Data Center Interconnect (DCI) solution.

Requirements

This example uses the following hardware and software components:

  • Four Juniper Networks MX Series routers to be configured as data center gateways and WAN edge routers.

  • Four Juniper Networks MX Series routers to be configured as top-of-rack (ToR) routers.

  • Six customer edge (CE) devices.

  • Six host devices connected to each CE device that has the capability to configure multiple VLANs.

  • One provider (P) router part of the EVPN-MPLS WAN network.

  • Junos OS Release 17.2 or later.

Overview

You can interconnect different data center networks running Ethernet VPN (EVPN) with Virtual extensible LAN (VXLAN) encapsulation through a WAN running MPLS-based EVPN using the logical tunnel (lt-) interface.

Figure 1 illustrates the interconnection of data center networks running EVPN with VXLAN encapsulation through a WAN running MPLS-based EVPN. For the purposes of this example, the MX Series routers acting as data center gateways and as WAN edge routers are named MX11, MX12, MX21, and MX22. The MX Series routers acting as top-of-rack (ToR) routers are named ToR11, ToR12, ToR21, and ToR22. The customer edge (CE) devices connected to the data center network 1 (DC1) are named CE1, CE2, and CE3. The customer edge (CE) devices connected to the data center network 2 (DC2) are named CE4, CE5, and CE6. The host devices connected to each CE device should be able to configure multiple host VLANs. The WAN provider router is named P.

Note:

CE devices are part of the logical system of ToR devices.

Figure 1: EVPN-VXLAN Data Center Interconnect Through WAN Running EVPN-MPLSEVPN-VXLAN Data Center Interconnect Through WAN Running EVPN-MPLS

For the MX Series routers acting as data center gateways and WAN edge routers, configure the following information:

  • IRB interfaces, virtual gateway addresses, and loopback logical interfaces.

  • Multiprotocol external BGP (MP-EBGP) underlay connectivity between gateway and ToR routers, EVPN as the signaling protocol.

  • Routing policies to allow specific routes into the virtual-switch tables.

  • Routing instances (Layer 3 VRFs) for each virtual network, including a unique route distinguisher, and a vrf-target value.

  • Virtual-switch instances (Layer 2 MAC-VRFs) for each virtual network, the VTEP source interface (always lo0.0), route distinguisher, and vrf-import policy.

  • EVPN protocol, encapsulation method, VNI list, and BUM traffic forwarding method for each virtual switch.

  • Bridge domain within each virtual switch that maps VNIDs to VLAN IDs, an IRB (Layer 3) interface, and the BUM forwarding method.

For the MX Series routers acting as top-of-rack (ToR) routers, configure the following information:

  • Host facing interfaces with VLANs, VLAN IDs, and loopback logical interfaces.

  • Link Aggregation Control Protocol (LACP)-enabled link aggregation group (LAG), Ethernet Segment ID (ESI), and all-active mode.

  • Multiprotocol external BGP (MP-EBGP) overlays between ToR and gateway routers using EVPN as the signaling protocol.

  • EVPN with VXLAN as the encapsulation method, extended-vni-list, multicast mode, and route targets for each VNI.

  • Vrf-imp policy, vtep-source-interface, route-distinguisher, and vrf import and target information.

  • VLANs, with VLAN IDs mapped to globally significant VNIs.

Note:

You can set the virtual gateway address as the default IPv4 or IPv6 gateway address for end hosts (virtual machines or servers).

Configuration

CLI Quick Configuration

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

ToR11

ToR12

Data Center Gateway and WAN Edge 1 Router (MX11)

Data Center Gateway and WAN Edge 2 Router (MX12)

Data Center Gateway and WAN Edge 3 Router (MX21)

Data Center Gateway and WAN Edge 4 Router (MX22)

ToR–21

ToR–22

Configuring ToR11

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.

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

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

  4. Set the number of aggregated Ethernet interfaces.

  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.

  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.

  7. Configure the loopback interface address and routing options.

  8. Configure load balancing on ToR11.

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

  10. Configure a multiprotocol external BGP (MP-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.

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

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

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

  12. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  13. Configure community policy options.

  14. Apply load balance.

  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.

Configuring ToR12

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.

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

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

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

  5. Set the number of aggregated Ethernet interfaces.

  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.

  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.

  8. Configure the loopback interface address and routing options.

  9. Configure load balancing on ToR12.

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

  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.

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

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

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

  13. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  14. Configure community policy options.

  15. Apply load balance.

  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.

Configuring Data Center Gateway and WAN Edge 1 Router (MX11)

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.

  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.

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

  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.

  5. Configure integrated routing and bridging (IRB) interfaces that advertises 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 Host (which is the host part of VLAN-1):

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

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

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

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

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

  7. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  8. Configure community policy options.

  9. Apply load balance.

  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.

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

  12. Configure a pair of logical tunnel (lt-) interface 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.

  13. Configure the loopback interface address and routing options.

  14. Configure load balancing on MX11.

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

  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.

  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.

Configuring Data Center Gateway and WAN Edge 2 Router (MX12)

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.

  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 P device to operate in the enhanced-ip mode because the EVPN active-active functionality is supported on routers with MPCs and MIC interfaces only. A system reboot is required on committing this configuration.

    2. Configure the interfaces of the P device.

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

    4. Configure the loopback interface address and routing options.

    5. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

    6. Configure community policy options.

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

  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.

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

  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.

  6. Configure integrated routing and bridging (IRB) interfaces that advertises 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 Host (which is the host part of VLAN-1):

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

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

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

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

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

  8. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  9. Configure community policy options.

  10. Apply load balance.

  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.

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

  13. Configure a pair of logical tunnel (lt-) interface 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.

  14. Configure the loopback interface address and routing options.

  15. Configure load balancing on MX12.

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

  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.

  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.

Configuring Data Center Gateway and WAN Edge 3 Router (MX21)

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.

  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.

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

  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.

  5. Configure integrated routing and bridging (IRB) interfaces that advertises 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 Host (which is the host part of VLAN-1):

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

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

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

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

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

  7. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  8. Configure community policy options.

  9. Apply load balance.

  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.

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

  12. Configure a pair of logical tunnel (lt-) interface 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.

  13. Configure the loopback interface address and routing options.

  14. Configure load balancing on MX21.

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

  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.

  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.

Configuring Data Center Gateway and WAN Edge 4 Router (MX22)

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.

  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.

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

  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.

  5. Configure integrated routing and bridging (IRB) interfaces that advertises 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 Host (which is the host part of VLAN-1):

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

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

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

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

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

  7. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  8. Configure community policy options.

  9. Apply load balance.

  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.

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

  12. Configure a pair of logical tunnel (lt-) interface 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.

  13. Configure the loopback interface address and routing options.

  14. Configure load balancing on MX22.

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

  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.

  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.

Configuring ToR21

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.

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

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

  4. Set the number of aggregated Ethernet interfaces.

  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.

  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.

  7. Configure the loopback interface address and routing options.

  8. Configure load balancing on ToR21.

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

  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.

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

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

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

  12. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  13. Configure community policy options.

  14. Apply load balance.

  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.

Configuring ToR22

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.

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

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

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

  5. Set the number of aggregated Ethernet interfaces.

  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.

  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.

  8. Configure the loopback interface address and routing options.

  9. Configure load balancing on ToR12.

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

  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.

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

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

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

  13. Configure routing policies to accept the direct loopback address route and redirect it into BGP.

  14. Configure community policy options.

  15. Apply load balance.

  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.

Verification

After you configure both the underlay and EVPN overlay we recommend that you verify that the configurations work as you intended.

Verifying ToR11 Configuration

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.

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.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying ToR12 Configuration

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.

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.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying Data Center Gateway and WAN Edge 1 Router (MX11) Configuration

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.

Integrated routing and bridging (IRB) interfaces that advertises 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.

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.

A pair of logical tunnel (lt-) interface 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.

Loopback interface address.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying Data Center Gateway and WAN Edge 2 Router (MX12) Configuration

Purpose

Verify that MX12 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.

Integrated routing and bridging (IRB) interfaces that advertises 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.

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.

A pair of logical tunnel (lt-) interface 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.

Loopback interface address.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying Data Center Gateway and WAN Edge 3 Router (MX21) Configuration

Purpose

Verify that MX21 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.

Integrated routing and bridging (IRB) interfaces that advertises 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.

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.

A pair of logical tunnel (lt-) interface 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.

Loopback interface address.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying Data Center Gateway and WAN Edge 4 Router (MX22) Configuration

Purpose

Verify that MX22 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.

Integrated routing and bridging (IRB) interfaces that advertises 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.

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.

A pair of logical tunnel (lt-) interface 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.

Loopback interface address.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying ToR21 Configuration

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.

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.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Verifying ToR22 Configuration

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.

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.

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

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

Verify that the routing policies and community policy options and load balancing are properly configured to accept the direct loopback address route and redirect it into BGP.

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

Related Documentation