Solution and Validation Key Parameters
This section outlines solution key parameters and validation objectives for this JVD.
Supported Platforms and Positioning
Solution | Supported Platforms | OS | Positioning |
---|---|---|---|
DUT Platforms | MX480 with MPC10E and SCBE3 | Junos OS 23.2R2 | DC-WAN edge |
MX10003 | Junos OS 23.2R2 | DC-WAN edge | |
Helper Platforms | MX204 | Junos OS 23.2R2 | WAN edge |
ACX5448-D | Junos OS 23.2R2 | WAN edge | |
MX240 with 16x10G MPC | Junos OS 23.2R2 | Enterprise Campus/Branch Access | |
ACX7100-48L | Junos OS Evolved 23.2R2 | Core Network | |
Core and Data Center | PTX10003-160C | Junos OS Evolved 23.2R2 | Core Network |
QFX5120-48Y | Junos OS 23.2R2 | Leaf | |
QFX5200-32C-32Q | Junos OS 23.2R2 | Spine | |
QFX5120-48Y | Junos OS 23.2R2 | ToR |
Feature List
The supported features include:
- Single-homed EVPN-MPLS Service with fast reroute (FRR) features enabled in the MPLS domain
- EBGP for the underlay and IBGP as the overlay protocol for EVPN-VXLAN within the enterprise data center
- EVPN Modes:
- VLAN based
- VLAN bundle
- VLAN aware bundle
- OSPF
- LDP
- MPLS based transport network
- LFA (link/node)
- Route Reflection
- IPv4
- IPv6
- LACP
- AE
- ECMP
- VLAN (802.1Q)
Contact your Juniper Networks representative for test results reports.
Test Bed Diagram
Figure 1 shows the test bed topology that is used to validate this design. The topology emulates the following network segments:
- Enterprise data center
- Enterprise data center WAN edge device
- Campus/branch WAN edge device
- Enterprise WAN
The validated design topology includes the routers and switches shown in Table 1.
![A diagram of a network Description automatically generated](media/image5.png)
Contact your Juniper Networks representative for test results reports.
Solution Validation Goals
The goal is to validate that the MX480 and MX10003 Universal Routing platforms can interconnect EVPN-MPLS and EVPN-VXLAN services.
Data center and WAN scaling information are available in Table 1 and Table 2.
Traffic Stream | Packet Size (Bytes) | Rate |
---|---|---|
EVPN VLAN based from WAN edge to devices connected to TOR | 512 Bytes | 600 Mbps |
EVPN VLAN bundle from WAN edge to devices connected to TOR | 512 Bytes | 600 Mbps |
EVPN VLAN aware from WAN edge to devices connected to TOR | 512 Bytes | 600 Mbps |
Here are the primary test goals for this JVD:
- Validate all three EVPN service models:
- VLAN-based
- VLAN bundle
- VLAN aware bundle
- Validate all active multihoming scenarios within the data center.
- Validate single-homed scenarios on the WAN edge devices.
- Validate LDP based transport
- Capture failure and convergence scenarios at scale.
- Capture CPU and memory utilization.
- Identify and document product limitations and anomalies.
- Validate network performance and convergence times under these
failure conditions:
- Link failures on the WAN edge device
- Link failures on the data center spine and leaf devices
- Node failures
- Process restarts–RPD, DCD, CHASSISD, and so on
- Deactivate/activate configuration options
Contact your Juniper Networks representative for the services and feature scaling information.
Solution Validation Non-Goals
Protocols and technologies that are not included in this design include:
- Non-Collapsed Assisted Replication (AR) support. AR is configured on QFX spines. No AR support exists on MX Series Universal Routing Platforms for collapsed AR mode.
- An active-active WAN edge configuration.
- Underlay protocols in transport/core networks other than those specified in the solution validation goals.
- Overlay service validation other than what is specified in the solution validation goals section.
- EVPN-VXLAN to EVPN-VXLAN stitching or EVPN-VXLAN to VPLS stitching is not validated.
- Management and automation using Juniper Apstra.