APPENDIX: Junos OS Configuration from This Fabric

Campus Fabric EVPN Multihoming 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.

Juniper Mist provides the following options (default in parentheses):

• BGP Local AS (65000)
• AS Base (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, Juniper 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 with core2:
2. Loopback interface and router ID:
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:
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 and distribution switches using eBGP.

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

Juniper Mist provisions Layer 3 IRB interfaces on the distribution layer.

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

The 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. VRFs used for traffic isolation:
5. VLAN to VXLAN mapping:
6. Layer 3 IRB interface enablement with virtual gateway addressing:

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 used for traffic isolation:
5. VLAN to VXLAN mapping:
6. Layer 3 IRB interface enablement with virtual gateway 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 Juniper 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 Layer 2 loop-free detection protocols such as RSTP.

Core1 Configuration:

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

   Core2 Configuration:

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

   Access1 Configuration:

3. VLANs associated with the new LACP Ethernet bundle:

   Access2 Configuration:

4. 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 LAG between the core switches and SRX Series Firewall. This Mist profile enables all VLANs on the Ethernet bundle with requisite ESI and LACP configuration options. From the perspective of the SRX Series Firewall, the Ethernet bundle that is configured on the SRX Series Firewall views the ESI-LAG as a single MAC address with the same LACP system- ID. This enables load hashing between the core and SRX Series Firewall without requiring Layer 2 loop-free detection protocols such as RSTP.

Core 1 Configuration:

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

   Core 2 Configuration:

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

   SRX Series Firewall Configuration:

3. Interface association with newly created Ethernet bundle and LACP configuration: