ON THIS PAGE
 

Validation Framework

Test Bed

The diagram below shows the suggested topology used for the JVD lab evaluating various EVPN multihoming fabric topologies. It applies to both the initial phase, which uses two collapsed core switches, and the current second phase, which expands the design to four collapsed core switches.

Figure 1: JVD Lab Proposal Phase1 and Phase2 JVD Lab Proposal Phase1 and Phase2

The suggested lab design allows for the evaluation of the following:

  • EVPN multihoming fabrics with:
    • Two collapsed core switches acting as spine and leaf.
      • One 4-member Virtual Chassis access switch acting as ToR.
      • One standalone access switch acting as ToR.
      • One 2-member Virtual Chassis access switch acting as ToR
    • Four collapsed-core switches acting as spine and leaf connected in a ring.
      • One 4-member Virtual Chassis access switch acting as ToR.
      • One standalone access switch acting as ToR.
      • One 2-member Virtual Chassis access switch acting as ToR.
    • Four collapsed-core switches acting as spine and leaf connected in a full mesh.
      • One 4-member Virtual Chassis access switch acting as ToR.
      • One standalone access switch acting as ToR.
      • One 2-member Virtual Chassis access switch acting as ToR.
  • Service block function through:
    • Integrated into existing collapsed core switches and acting as service leaf and collapsed core at the same time.
    • Attached WAN routers through Layer 2 or Layer 3 exit.
    • Attached servers through ESI-LAG redundant links.
  • WAN router integration:
    • Layer 2 fabric exit.
      • ESI-LAG-based trunks.
      • Bridged overlay where a WAN router is the default gateway for EZ-LAG and legacy migration scenarios.
    • Layer 3 fabric exit.
      • OSPF as routing protocol.
      • eBGP as routing protocol
    • Attached to:
      • Collapsed core switch.
    • Redundant WAN router design:
      • Two Juniper MX routers.
      • Two Juniper Networks® SRX Series Firewalls in cluster configuration.
  • Wi-Fi access points:
    • Local-attached to the access switches with Power over Ethernet (PoE).
    • Various Wi-Fi clients.
    • Basic Wi-Fi roaming.
  • Overlay server attached to a service block functionality:
    • DHCP server.
    • Other services.
  • RADIUS server:
    • Server location:
      • Local server attached to underlay network.
      • Remote Juniper Mist Access Assurance through public cloud.
    • Authentication for the following clients:
      • Wired clients attached to access switches.
      • Wi-Fi clients using the access points.
    • Authentication based on clients:
      • MAC address.
      • 802.1X EAP authentication.
    • Dynamic authorization profiles:
      • Single VLAN assigned.
      • Multiple VLANs assigned.
      • Filter-Id ACL assigned.
  • Testing fabric features such as:
    • DHCP relay
    • Protect RE-filter
    • DHCP snooping
    • Storm control
    • MAC address limit with aging
    • DNS
    • NTP

The following network topology was tested as part of the previous Phase 1 for this JVD.

Figure 2: EVPN Multihoming Fabric with Two Collapsed Cores EVPN Multihoming Fabric with Two Collapsed Cores

The following two network topologies were tested as part of Phase 2 of this JVD.

Figure 3: EVPN Multihoming Fabric with 4 collapsed cores in a Ring EVPN Multihoming Fabric with 4 collapsed cores in a Ring

The second topology adds more failover resiliency:

Figure 4: EVPN Multihoming Fabric with 4 collapsed cores in a full Mesh EVPN Multihoming Fabric with 4 collapsed cores in a full Mesh

Platforms / Devices Under Test (DUT)

The table below shows the devices that were tested and on which Junos OS version:

Table 1: Devices Under Test
Devices Under Test
Fabric function Device Junos OS Release
Collapsed Core Switches QFX5120 24.4R2
Access 4-member Virtual Chassis EX4400-48P 24.4R2
Access Switch standalone EX4100-48P 24.4R2
Access 2-member Virtual Chassis EX4000- 24.4R2
WAN router SRX380 23.4R2-S5

Test Bed Configuration

In the appendix section of this JVD, we are sharing information on exactly how some of the tests were performed. Contact Juniper or your Juniper account representative to obtain the full archive of the test bed configuration used for this JVD.