Solution and Validation Key Parameters

Supported Platforms and Positioning

Table 1: Supported Platforms

Solution	Supported Platforms	OS	Positioning
DUT Platforms	MX304	Junos OS 22.3R1-S1	WAN edge
	ACX7100-48L ACX7509	Junos OS Evolved 22.3R1-S1	WAN edge
Helper Platforms	MX480 with MPC10E	Junos OS 22.3R1-S1	Campus/Branch Edge
	ACX7100-48L	Junos OS Evolved 22.3R1-S1	Campus/Branch Edge
Core and Data Center	PTX10003-160C	Junos OS Evolved 22.3R1-S1	Core Network
	PTX10008	Junos OS 22.3R1-S1	Core Network

Key Feature List

The supported key features include:

• Single-homed VPLS, L2CKT and L3VPN Service with fast reroute (FRR) features enabled in the MPLS domain
• VRRP
• OSPF as IGP in the core
• Route-Reflection session with all the PEs
• LDP
• MPLS-based transport network
• LFA (link/node), Route Reflection
• IPv4
• LACP
• Aggregated Ethernet (AE) Bundles
• Bi-directional Forwarding and Detection (BFD)
• ECMP
• VLAN (802.1Q)

Contact your Juniper Networks representative for the complete feature list.

Test Bed Diagram

Figure 1 shows the test bed topology that is used to validate this reference design. The topology emulates the following network segments:

• Campus and branch WAN edge
• Enterprise data center WAN edge
• Enterprise WAN backbone

The topology includes the router models shown in Table 1.

Note:

Contact your Juniper Networks representative for test results reports.

Solution Validation Goals

This report validates that the ACX7100-48L, ACX7509 and MX304 platforms can terminate L2 or L3 VPN connections from campus and branch locations. HQoS is enabled to validate the service levels. Multicast traffic is generated to validate the surveillance monitoring use case. The provider multicast service interface (PMSI) can set up the end-to-end provider tunnels. For details on all validated scenarios, see the full test report. All scenarios are validated using end-to-end traffic.

Validated scenarios include:

• VPLS, L2CKT and L3VPN services with unicast and BUM traffic.
• HQoS at IFD, IFL, and queue levels.
• Multicast delivery.
• NGMVPN with LDP.
• L3VPN native and hub/spoke models.
• L3VPN with VRRP.
• Single-homed VPLS services.

See Table 1 for WAN edge and core scaling information.

Table 2: Cumulative Traffic Flows Used During Validation

Traffic Stream	Packet Size (Bytes)	Rate
VPLS with BUM Traffic from WAN edge to remote WAN Edge and TGEN	512 Bytes	100 Mbps
L2CKT Traffic from WAN edge to remote WAN Edge and TGEN	1024 Bytes	400 Mbps
L3VPN Traffic for hub and spoke scenario	512 Bytes	50 Mbps
L3VPN Traffic for many-to-many with VRRP scenario	512 Bytes	100 Mbps
Native Multicast Traffic	512 Bytes	50 Mbps
Multicast Traffic from Source WAN Edge to remote PE and TGEN	512 Bytes	50 Mbps

The primary test goals for this JVD include:

• Validate end-to-end service delivery.
• Validate single-homed VPLS and L2CKT.
• Validate L3VPN single-active scenarios with VRRP.
• Validate LDP-based MPLS transport.
• Capture failure and convergence metrics.
• Capture CPU and memory utilization.
• Identify and document product limitations and anomalies.
• Validate network performance and convergence time under the following failure conditions:
  • Link failures on the WAN edge device
  • Link failures on core devices
  • Node failures
  • VRRP Active/Standby switchovers
  • Process restarts:
    • RPD
    • DCD
    • CHASSISD
    • MGD
    • Deactivate/activate configuration knobs

Note:

Contact your Juniper Networks representative for the complete details of services and feature scaling information.

Solution Validation Non-Goals

The protocols and technologies that are not tested include:

• VPLS multihoming
• VPLS IRB and unnumbered interface
• HQoS on interface sets
• HQoS on AE, VPLS, L3VPN, L2CKT
• NGMVPN with RSVP
• EVPN-MPLS Segment Routing
• Management and Automation
• Telemetry