Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Test Objectives

Juniper Validated Design (JVD) is a cross-functional collaboration between Juniper solution architects and test teams to develop coherent multidimensional solutions for domain-specific use cases. The JVD team comprises technical leaders in the industry with a wealth of experience supporting complex customer use cases. The scenarios selected for validation are based on industry standards to solve critical business needs with practical network and solution designs.

The key goals of the JVD initiative include:

  • Test iterative multidimensional use cases.
  • Optimize best practices and address solution gaps.
  • Validate overall solution integrity and resilience.
  • Support configuration and design guidance.
  • Deliver practical, validated, and deployable solutions.

A reference architecture is selected after consultation with Juniper Networks global theaters and a deep analysis of customer use cases. The design concepts that are deployed use best practices and leverage relevant technologies to deliver the solution scope. Key performance indicators (KPIs) are identified as part of an extensive test plan that focuses on functionality, performance integrity, and service delivery.

Once the physical infrastructure that is required to support the validation is built, the design is sanity-checked and optimized. Our test teams conduct a series of rigorous validations to prove solution viability, capturing, and recording results. Throughout the validation process, our engineers engage with software developers to quickly address any issues found.

The Metro Ethernet Business Services solution validates a comprehensive multidimensional architecture that includes best practices for the design and implementation of a dense services L2/L3 portfolio across intra-domain and inter-AS regions.

The Metro Evolving Use Cases table describes the solution transformation through multiple stages that provide an operator entry points at any of the three stages.

  1. Stage 1 describes a complete solution architecture leveraging Seamless Segment Routing MPLS with diverse services that support intra/inter-region termination points enabled by BGP Labeled Unicast. The stage 1 portion of the solution includes all the VPN services described in the JVD documentation.
  2. Stage 2 enhances the solution to support network “Lite” slicing with flexible algorithms and transport classes. All services are mapped to color transport within the AS. Flex-Algo prefix leaking with FAPM extends color-mapped services across IGP boundaries. A default resolution scheme is used that enables color-aware service failover to inet.3 resolved next hops.
  3. Stage 3 further enhances the design by introducing BGP Classful Transport as the mechanism for Inter-AS color-aware traffic steering. All services are color-mapped. In addition, a more sophisticated resolution scheme is included to govern the failover of gold to bronze and bronze to best-effort paths.

Table 3: Metro Evolving Use Cases

A table with text on it Description automatically generated

Test Goals

The focus of the testing includes:

  • Validate Metro Fabric performance, convergence, resiliency, ability to optimize traffic flows within the fabric, and support MEC connectivity models allowing MEG1/MEG2 services edge compute access.
  • Validate Metro Multi-Ring performance, convergence, resiliency, and ability to optimize traffic flows within/between rings, leveraging MDR1/2 for leaking.
  • Validate the ACX7100-48L as an Access Leaf (AN3) DUT supporting EVPN-VPWS, EVPN-FXC, EVPN-ELAN, EVPN Type-5, EVPN Anycast IRB, L2VPN, L2Circuit, BGP-VPLS, and L3VPN services.
  • Validate the ACX7100-32C as a Metro Edge Gateway (MEG1) DUT and functioning as a Border Leaf and Route Reflector to facilitate MEC connectivity, access leaf service termination, and inter-AS functions. Services include EVPN-VPWS, EVPN-FXC, EVPN-ELAN, EVPN Type-5, EVPN Anycast IRB, L2Circuit, and BGP-VPLS.
  • Validate the ACX7509 as a Metro Edge Gateway (MEG2) DUT and function as a Border Leaf and Route Reflector to facilitate MEC connectivity, and access leaf service termination, and inter-AS functions. Services include EVPN-VPWS, EVPN-FXC, EVPN-ELAN, EVPN Type-5, EVPN Anycast IRB, L2Circuit, and BGP-VPLS.
  • Validate the MX304 as a Multi-Services Edge (MSE1 and MSE2) DUT supporting advanced services termination with PWHT, Floating PW Anycast-SID, EVPN-ETREE, Dedicated Internet Access (DIA) using Internet-VRF model, Route Reflector, and providing an interconnectivity point for Q-in-Q handoff into SP Core.
  • Validate the ACX7100-48L as a Metro Access node (MA3) DUT supporting local-switching E-NNI / E-Access services with EVPN-VPWS and L2Circuit LSW, dense L2Circuit aggregation and facilitating multi-instance ISIS with connections in both metro ring blue and green.
  • Validate the ACX7024 as a Metro Access node (MA1.1 and MA1.2) DUT supporting active-active VPN services with multi-homing or single-homing. Services include EVPN-VPWS, EVPN-FXC, EVPN-ELAN, L2Circuit Floating PW, and BGP-VPLS.
  • The ability for all services to support inter-AS with BGP Labeled Unicast (Seamless MPLS).
  • The ability for services to be mapped onto color transport (Flex-Algo) and color agnostic paths.
  • Support of intra-domain, inter-domain, and inter-AS network abstraction, creating distinct color paths through the network.
  • The ability for services to support BGP Classful Transport extending color mapping across autonomous systems (Seamless SR).
  • Validate performance and functionality for EVPN-ELAN, EVPN-VPWS, EVPN Flexible Cross Connect, EVPN-VPWS Local-Switching, EVPN with IRB Virtual Gateway, EVPN Pure Type-5, EVPN Anycast Floating PW, BGP-VPLS, L2VPN, L2Circuit, L2Circuit Local-Switching, and L3VPN with Internet-VRF DIA.
  • Additional helper nodes are critical to the solution architecture:
    • MX204 as Access Node (AN1) to support EVPN ESI LAG with 3xPEs, supporting device interoperability with ACX5448 (Junos OS) and ACX7100-48L (Junos OS Evolved) platforms.
    • ACX5448 as Access Node (AN2) supporting EVPN-VPWS multi-homing topology scale and EVPN ESI LAG with 3xPEs, supporting device interoperability with MX204 (Junos OS) and ACX7100-48L (Junos OS Evolved) platforms.
    • ACX710 as Access Node (AN4) for scaling of single-homed EVPN-VPWS services.
    • MX204 as Metro Access (MA2) supporting the metro blue ring. No services are enabled here, but the architecture supports adding services to this node.
    • MX204 as Metro Access (MA5) supporting local-switching transport, EVPN-ETREE services as a leaf node, Inter-Ring BGP-VPLS services, and topology scaling with L2Circuit, L2VPN, and VPLS.
    • MX204 as Metro Access (MA4) supporting EVPN-ETREE services as a leaf node and L3VPNs with Internet access.

Listed features are subject to individual device support. Contact your Juniper Networks representative for questions or concerns.

Test Non-Goals

Non-goals include elements that logically belong in the JVD but are excluded for various reasons, like being outside of the validation scope or because of feature or product limitations, etc.

  • Layer 2 VPN color service mapping onto transport classes with inter-AS BGP Classful Transport is validated for all DUTs in the JVD. However, this is included as a non-goal for ACX7000 platforms because this feature is planned for Junos OS Evolved Release 24.1R1. For this reason, all services include both color-aware and color-agnostic path selection. L3VPN with color service mapping and BGP-CT is supported and included for all devices.
  • A Class of Services (CoS) model is deployed as part of the overall solution architecture, but QoS is not a focus of this JVD.
  • Devices not listed as DUTs. Helper nodes are verified for correct functional behaviors in the design, but test cases are only executed against specified DUTs.
  • Any features not specifically listed and including specified solution gaps and known limitations.

Scale and Performance

This section contains the KPIs that are used as solution validation targets. Validated KPIs are multidimensional and reflect our observations in customer networks or reasonably represent the solution capabilities. These numbers do not indicate the maximum scale and performance of individual tested devices. For unidimensional data on individual SKUs, contact your Juniper Networks representative.

The Juniper JVD team continuously strives to enhance solution capabilities. Consequently, solution KPIs may change without prior notice. Always refer to the latest JVD test report for up-to-date solution KPIs. For the latest comprehensive test report, contact your Juniper Networks representative.

Table 4: KPI Scale Summary (DUT Only)

Device Under Test Scale















IFD 66 50 48 115 108 35 35
IFL 8581 4249 3945 16333 13776 789 1512
VLANs per-system 6064 3064 3061 7745 5686 600 830
ISIS Adjacency IPv4 4 7 9 4 3 2 2
IBGP v4 Sessions 2 7 7 8 3 4 4
EBGP sessions 200 2 2 2201 2203 - -
RIB routes ~279k ~155k ~154k ~349k ~1.2M ~31k ~33k
FIB routes ~65k ~12k ~12k ~113k ~966k ~4k ~4k
EVPN-VPWS SH 200 - - - - - -
EVPN-FXC SH vlan-unaware 500 - - 500 - - -
EVPN-FXC SH vlan-aware - - - - - - -
EVPN-FXC MH vlan-aware 0 50 50 - - 50 50
EVPN-VPWS A/A MH 1400 1000 1000 - - 400 400
EVPN-ELAN MH vlan-bundle 200 200 200 - - - -
EVPN-ELAN MH vlan-based 100 100 100 - - 100 100
EVPN-ETREE - - - 1000 1000 - -
EVPN TYPE-5 50 50 50 50 50 - -
EVPN Anycast IRB 25 25 25 25 25 - -
EVPN-VPWS EPL 1 - - - - 1 -
EVPN-ELAN EPL 1 - - - - - 1
EVPN Floating PW - - - 100 100 - 100
L2VPN EPL 1 - - - - - -
L2Circuit Hot Standby 1000 1000 1000 - - - -
L2 VPN Sessions 200 - - - - - -
L3VPN BGPv4 Instances 100 - - 1100 1100 - -
L3VPN BGPv6 Instances 100 - - 1100 1100 - -
L3VPN OSPF Instances 100 - - 1100 1100 - -
VPLS Instances 300 200 100 - - - 200
MAC Scale - VPLS 900 600 300 - - - 500
CFM UP MEP 1000 400 200 - - - 300
TOTAL VPN SERVICES 4278 2525 2525 4975 4475 551 851