Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

APPENDIX: Junos Configuration from This Fabric

Campus Fabric Core-Distribution ERB Configurations

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

Mist provides 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

Throughout the Campus Fabric between core and distribution layers, Mist enables per-packet (Junos OS defines this as per-flow) load-balancing using ECMP and fast convergence of BGP in the event of a link or node failure using BFD.

Core1 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:

Core2 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:

Dist1 Configuration:

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

Dist2 Configuration:

  1. Interconnects between the two core switches:
  2. Loopback interface and router ID:
  3. Per-packet load-balancing:
  4. BGP underlay network to the two core 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 and distribution 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 the core and distribution layers.

Mist provisions L3 IRB interfaces on the distribution layer.

Mist enables VXLAN tunnelling, VLAN to VXLAN mapping, and MP BGP configuration snippets such as vrf-targets on the distribution and core switches.

VRFs for traffic isolation are provisioned on the distribution switches.

Core1 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. 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. VLAN to VXLAN mapping:

Dist1 Configuration:

  1. BGP overlay peering between the two core 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:

Dist2 Configuration:

  1. BGP overlay peering between the two core 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 Layer 2 ESI-LAG Between the Distribution Switches and the Access Switches

This section displays the configuration output from the Juniper Mist cloud for the enablement of the Layer 2 ESI-LAGs between the distribution switches and access switches. This Mist profile enables all VLANs on the Ethernet bundle with requisite ESI and LACP configuration options. From the perspective of the access switches, the Ethernet bundle that is configured on the access layer views the ESI-LAG as a single MAC address with the same LACP system-ID. This enables load hashing between distribution and access layers without requiring L2 loop-free detection protocols such as RSTP.

Figure 1: Access Switch Attach to Distribution Switches Access Switch Attach to Distribution Switches

Dist1 Configuration:

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

Dist2 Configuration:

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

Access Configuration:

  1. VLANs associated with the new LACP Ethernet bundle:

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

This section displays the configuration output from the Juniper Mist cloud for the enablement of the Layer 2 ESI-LAGs between the core switches and the MX router. 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 2: Layer 2 ESI-LAG Supporting Active-Active Load Balancing Layer 2 ESI-LAG Supporting Active-Active Load Balancing

Core 1 Configuration:

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

Core 2 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: