Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Solution and Validation Key Parameters

This section outlines solution key parameters and validation objectives for this JVD.

Supported Platforms

To review the software versions and platforms on which this JVD was validated by Juniper Networks, see the Validated Platforms and Software section in this document.

Service Profiles

Table 1 and Table 2 show the list of Fronthaul and Midhaul service profiles respectively and associated network services which were used during validation. Note that Fronthaul profiles were in the focus of the validation, while Midhaul profiles and associated traffic flows were used for sake of completeness. The Fronthaul profiles were the focus of the validation, Midhaul profiles and their associated traffic patterns were used to ensure validation completeness.

Table 1: Fronthaul Service Profiles
Use Case Service Overlay Mapping End Points
4G L3VPN MBH End-to-End L3VPN between CSR (AN4) to SAG

AN4/SAG

IPv4; IPv6
5G Fronthaul Fronthaul EVPN-VPWS + FXC single-homing from AN4 to HSRs (AG1) with E-OAM Performance Monitoring

AN4/AG1

Untagged, Single/Dual Tag
5G Fronthaul Fronthaul EVPN-VPWS + FXC with Active/Active Multihoming from AN4 to HSRs (AG1)

AN4/AG1

Untagged, Single/Dual Tag
5G Fronthaul Fronthaul EVPN-ELAN with Active/Active Multihoming from AN4 to HSRs (AG1)

AN4/AG1

Untagged, Single/Dual Tag
L2VPN MBH End-to-End L2VPN between CSR (AN4) to SAG with FAT-PW

AN4/SAG

Untagged, Single/Dual Tag
L2Circuit MBH End-to-End L2Circuit between CSR (AN4) to SAG with FAT-PW

AN4/SAG

Untagged, Single/Dual Tag
BGP-VPLS MBH

End-to-End VPLS between CSR (AN4) to SAG

with E-OAM Performance Monitoring

AN4/SAG

Untagged, Single/Dual Tag
Table 2: Midhaul Service Profiles
Use Case Service Overlay Mapping End Points
5G Midhaul EVPN IRB anycast gateway with L3VPN multi-homing

AG1/SAG

IPv4; IPv6
5G Fronthaul Bridge Domain IRB anycast static MAC/IP with L3VPN

AN4/AG1

Untagged, Single/Dual Tag
L2VPN Midhaul Midhaul L2VPN HSR (AG) attachments (AG1) to SAG with FAT-PW AG1/SAG
L2Circuit Midhaul

Midhaul L2Circuit attachments between HSR (AG) to SAG

with FAT-PW

 AG/SAG

Scale and Performance

This section contains key performance indexes (KPIs) used in solution validation targets. Validated KPIs are multi-dimensional and reflect our observations in customer networks or reasonably represent solution capabilities. These numbers do not indicate the maximum scale and performance of individual tested devices. For uni-dimensional data on individual SKUs, contact your Juniper Networks representatives.

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.

The scale reference in Table 8 provides an overview of KPIs represented in the validated profile.

To validate CoS functionality, we tested the classification, scheduling, shaping, and rewriting behaviors of the ACX7024 across services utilizing the 5G xHaul infrastructure. As part of the testing, we measured the latency for critical Fronthaul traffic types.

Based on the network design, the architecture can deliver fast restoration within 50ms for most traffic flows transported over ISIS-SR with Topology Independent Loop-Free Alternate (TI-LFA) protection mechanisms. Load distribution and optimization features were shown to improve service restoration in the event of link or node failures. Link events consistently achieved convergence in less than 50ms. The ACX7024 with Junos OS Evolved Release 22.3R2 can deliver the solutions outlined here across intra- and inter-domain architectures and is ideally situated for the CSR access role.

Table 3: KPI Scale Summary
Feature AN4 (ACX7024)—Access / CSR AG1.1 (ACX7509)—Pre-Agg / HSR AG1.2 (ACX7100-32C)—Pre-Agg / HSR SAG (MX10003)—Services Agg
RIB/FIB 200k/100k 400k/375k 400k/375k 640k/430k
IFLs 1498 11145 11010 16288
EVPN-VPWS SH 200 700 700 0
EVPN-VPWS MH A/A 100 200 200 0
EVPN-FXC SH 50 50 0 0
EVPN-FXC MH 50 50 50 0
EVPN-ELAN 50 50 50 0
L2Circuit 100 1000 1000 2500
L2VPN 50 1000 1000 2450
L3VPN 100 100 100 100
VPLS 100 1000 1000 2500
L3VPN BD (Midhaul) 0 500 500 500
MAC (VPLS) 10k 29k 111k 176k
CFM UP MEP (1s) 300 100 100 100
Total VPN Services 800 4650 4600 8050

Key Feature List

  • EVPN-VPWS
  • EVPN-ELAN
  • EVPN-FXC
  • L3VPN
  • BGP-VPLS
  • L2Circuit
  • L2VPN
  • Segment Routing ISIS
  • TI-LFA (link/node)
  • ISIS
  • BGP
  • BGP-LU
  • BFD
  • Community-based Routing Policy
  • Route Reflection
  • IPv4
  • IPv6
  • LACP
  • AE
  • CFM
  • LFM
  • VLAN (802.1q)

For the full test report and feature list, contact your Juniper Networks representative.

Test Bed

Figure 1 illustrates the test bed that we used. The network consists of four layers: access, pre-aggregation, aggregation, and transport core.

  • Fronthaul segment: Uses a spine-leaf access topology, connecting to redundant HSR (AG1.1/1.2) nodes, which also handle 4G pre-aggregation and 5G HSR functions. The pre-aggregation AG1 nodes provide connectivity for O-DUs and include additional emulated access insertion points (RT) for scalability.
  • Midhaul and Backhaul segments: These are represented by ring topologies and serve aggregation and core roles. This JVD does not focus on these segments.
Figure 1: 5G Fronthaul Lab Topology A diagram of a network Description automatically generated

Table 4 lists the topology definitions.

Table 4: Topology Definitions
Layer Devices Under Test
Access ACX7100-48L (AN3), ACX7100-48L (AN1), ACX710 (AN2) CSRs
Pre-Aggregation ACX7509 (AG1.1) and ACX7100-32C (AG1.2) HSRs
Aggregation MX204s (AG2.1/AG2/2), MX10003 (AG3.1), MX480 (AG3.2) aggregation routers
Core Network PTX1000 (CR1) and MX10003 (CR2) core routers. MX10003 (SAG) services router
Figure 2: End-to-End 4G/5G Traffic Flows and Network Architecture A computer screen shot of a diagram Description automatically generated

The flows are generated in the same way from AN4 (ACX7024) towards both AG1.1 and AG1.2, as well as AN4 to SAG. Load sharing is applied whenever possible. The network paths are chosen based on IGP metrics. The packet sizes for most VPN services range from 128 to 1000 bytes.

For additional details on validation scenarios and full archive of the test bed configuration used for this JVD, contact your Juniper Networks representative.

Solution Validation Goals

The main goal was to validate the reference design of a unified 5G xHaul network with a specific focus on the Fronthaul segment. To achieve this, we used Seamless MPLS over ISIS Segment Routing (ISIS-SR), enabling the support of multiple 4G/5G services including:

  • VLAN-aware services including L3VPN (IPv4 and IPv6 virtual private networks)
  • Active-Active Multihoming for EVPN-ELAN
  • EVPN-VPWS and EVPN Flexible Cross Connect (FXC) VLAN-aware services
  • Single-homed services such as EVPN-VPWS, EVPN-FXC, BGP-Virtual Private LAN Service (VPLS), Layer 2 Virtual Private Network (L2VPN), and L2Circuit

Here are the major test goals for this JVD:

  • Validate VPN services, including L3VPN, EVPN-VPWS, EVPN-FXC, EVPN-ELAN, BGP-VPLS, L2Circuit, and L2VPN over SR-MPLS transport architecture.
  • Validate TI-LFA redundancy mechanisms over Segment Routing with Seamless MPLS/BGP-LU.
  • Validate network resiliency, traffic restoration, and measured convergence time for ACX7024 (AN4) with adjacent link failures for all traffic types.
  • Measure solution resilience of Layer 2 and Layer 3 flows from Access Node (AN) to Pre-Aggregation AG1 (O-RU to O-DU).
  • Validate input/output VLAN operations for the normalization of all VPN services.
  • Validate the basic mechanisms of CoS:
  • Classification of traffic based on DSCP, 802.1p and EXP with Packet Loss Priority (PLP) high and low.
  • Preservation of QoS codepoints end-to-end for inner and outer tags.
  • Support for ingress classification using fixed and behavior aggregate styles.
  • Creation of at least six forwarding classes and six queues (all featured platforms support eight queues).
  • Support for a two-priority queue scheduling system, consisting of a strict-high priority and a low priority. The system should allocate a certain percentage of time and buffers to each priority queue (Traffic Rate).
  • Strict-high priority queues pre-empt low priority queues.
  • Strict-high priority queue shaping prevents starving low priority queues.
  • The port shaper inherits the scheduler characteristics.
  • Rewrite operations, based on queue assignment, support 802.1p, DSCP and EXP.
  • Rewrite for single-tagged and dual-tagged (outer only) frames.
  • Validate latency budgets for non-congested scenarios where <100% line rate is offered while strict-high queue is in-profile:
  • O-RU-to-O-DU latency averages ≤10µ per device (≤6µs single DUT).
  • RU-to-SAG latency is ≤10ms (expected ≤150µ).
  • Validate congestion scenarios:
  • Preservation of highest priority (eCPRI) Fronthaul traffic.
  • Traffic priorities are maintained across shared links.
  • Traffic priorities are maintained within and between VPN services that share common links.
  • Validate consistency and resiliency of the ACX7024 against negative stress conditions (enabled/disable control and data plane daemons, add/delete configurations, and so on.)
  • Identify product limitations, anomalies, and open Problem Reports (PRs) exposed during validation stages.
  • Attempt to resolve and verify opened PRs during validation.

Class of Service Validation Points

We tested CoS operations and performance requirements to maintain the reliability of important 5G Fronthaul traffic between RU and DU. In Figure 3 , the DUTs are:

  • ACX7024 as the CSR to facilitate traffic flows
  • PTX10001-36MR for the core and peering role
  • MX304 as the services edge platform
Figure 3: Class of Service Validation Points A computer screen shot of a diagram Description automatically generated

In Figure 3 , the traffic flows from IXIA (RT) are directed through the ACX7024 (AN4) towards the O-DU or SAG (Services Aggregation Gateway). These flows are classified based on Layer 2 (802.1p) or Layer 3 (DSCP) codepoints at specific positions called classifiers. The codepoints are then mapped to EXP values across the SR-MPLS topology.

To ensure the expected behavior, queue statistics are monitored to confirm that the classification and scheduling process yields the desired outcomes. Additionally, rewrite operations are performed at designated positions to modify certain packet fields. Packet captures are taken to verify that DSCP, 802.1p, or EXP bits are correctly rewritten or preserved.

In the opposite direction, flows sent through the SAG are marked and validated once they exit the AN4, ensuring that the marking process operates as intended.

For the full test report including complete details on the hardware and software, contact your Juniper Networks representative.

Solution Validation Non-Goals

Non-goals represent protocols and technologies outside the scope of the current validation.

  • Underlay MPLS/SR transport other than specified in the Solution Validation Goals section
  • Latency validation under congestion scenarios
  • Temporal transmit rate or buffer (elastic buffer is used)
  • BGP PIC-Edge at border routers
  • Multifield classification to forwarding class mapping
  • Custom drop profiles (WRED) (defaults are used)
  • Hierarchical CoS and Traffic Control Profiles, IFD/IFL policers
  • End-to-End Timing and Synchronization Distribution: Synchronous Ethernet, IEEE1588v2
  • SLA Monitoring: RFC 2544, Y.1564, TWAMP, Active Assurance
  • Telemetry, management, and automation

Failure Scenarios

  • DUT Adjacent link failures
  • DUT Indirect link failures
  • DUT Node failures
  • Link congestion
  • Queue congestion
  • Process restart