Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Additional Information

Configuration of the Underlay IP Fabric

This section displays the configuration output from the Juniper Mist cloud for the IP Fabric underlay on the core, distribution, and access switches using eBGP.

Mist provides the user with the following options (default in parenthesis):

  • BGP Local AS (65001)
  • Loopback Pool (172.16.254.0/23)
  • Subnet (10.255.240.0/20) – point to point interfaces between adjacent layers

Mist enables per-packet load-balancing using ECMP and fast convergence of BGP in the event of a link or node failure using BFD.

Core1 Switch Configuration

  1. Interconnects between the two distribution switches.
  2. Loopback interface, router ID, and AS number:
  3. Per-packet load balancing.
  4. BGP underlay network between the two distribution switches.

Core2 Switch Configuration

  1. Interconnects between the two distribution switches.
  2. Loopback interface address, router ID, and AS number.
  3. Per-packet load balancing.
  4. BGP underlay network between the two distribution switches.

Dist1 Switch Configuration

  1. Interconnects between the two core switches and the two access switches.
  2. Loopback interface address, router ID, and AS number.
  3. Per-packet load balancing.
  4. BGP underlay network between the two core switches and two access switches.

Dist2 Switch Configuration

  1. Interconnects between the two core switches and the two access switches.
  2. Loopback interface and router ID.
  3. Per-packet load balancing.
  4. BGP underlay network between the two core switches and two access switches.

Access1 Configuration

  1. Interconnects between the two distribution switches.
  2. Loopback interface and router ID and AS
  3. Per-packet load balancing.
  4. BGP underlay network between the two distribution switches.

Access2 Configuration

  1. Interconnects between the two distribution switches.
  2. Loopback interface and router ID and AS
  3. Per-packet load balancing.
  4. BGP underlay network between the two distribution switches.

Configuration of the EVPN VXLAN Overlay and Virtual Networks

This section displays the Juniper Mist cloud configuration output for the EVPN VXLAN overlay on the core, distribution, and access switches using eBGP.

Mist enables load balancing across the overlay network and fast convergence of BGP in the event of a link or node failure using BFD between adjacent layers.

Mist enables VXLAN tunneling, VLAN to VXLAN mapping, and MP-BGP configuration snippets such as vrf-targets on the access layer switches. The core switches have VXLAN tunneling and VLAN to VXLAN mapping enabled based on the selection of the Core as a Border option.

Core1 Switch Configuration

  1. BGP Overlay peering between the two distribution switches.
  2. Switch options that define vrf-targets and the source loopback interface used for VXLAN.
  3. VXLAN encapsulation.
  4. VRFs that are used for traffic isolation.
  5. VLAN to VXLAN mapping.

Core2 Configuration

  1. BGP overlay peering between the two distribution switches.
  2. Switch options that define vrf-targets and the source loopback interface used for VXLAN.
  3. VXLAN encapsulation.
  4. VRFs that are used for traffic isolation.
  5. VLAN to VXLAN mapping.

Dist1 Switch Configuration

  1. BGP overlay peering between the two core switches and the two access switches.

Dist2 Switch Configuration

  1. BGP overlay peering between the two core switches and the two access switches.

Access1 Configuration

  1. BGP overlay peering between the two distribution switches.
  2. Switch options that define vrf-targets and the source loopback interface used for VXLAN.
  3. VXLAN encapsulation.
  4. VRFs that are used for traffic isolation.
  5. VLAN to VXLAN mapping.
  6. L3 IRB interface enablement with anycast addressing.

Access2 Switch Configuration

  1. BGP overlay peering between the two distribution switches.
  2. Switch options that define vrf-targets and the source loopback interface used for VXLAN.
  3. VXLAN encapsulation.
  4. VRFs that are used for traffic isolation.
  5. VLAN to VXLAN mapping.
  6. L3 IRB interface enablement with anycast addressing.

Configuration of the L2 ESI-LAG Between the Core Switches and MX Router

This section displays the Juniper Mist Cloud configuration output for the enablement of the L2 ESI Link Aggregation Groups (LAG) between the core switches and MX routers. This Mist profile enables all VLANs on the Ethernet bundle with requisite ESI and LACP configuration options. From the perspective of the MX router, the Ethernet bundle that is configured on the MX router views the ESI-LAG as a single MAC address with the same LACP system id. This enables load hashing between the core and MX router without requiring L2 loop-free detection protocols such as RSTP.

Figure 1: L2 ESI-LAG Supporting Active-Active Load Balancing A diagram of a network Description automatically generated

Core 1 Switch Configuration

  1. Interface association with the newly created Ethernet bundle that includes ESI and LACP configuration.

Core 2 Switch Configuration

  1. Interface association with the newly created Ethernet bundle that includes ESI and LACP configuration.

MX Router Configuration

  1. Interface association with newly created Ethernet bundle and LACP configuration.