Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation

5G CSR xHaul Seamless Segment Routing—Juniper Validated Design (JVD)

keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Results Summary and Analysis

date_range 02-Apr-24

The JVD team validated the reference design of the converged 5G xHaul network and MBH architectures over seamless segment routing with color-mapping pre-slicing capabilities supported by ACX710 and ACX5448 Universal Metro Routers. ACX710 and ACX5448 DUT routers with Junos OS Release 21.2R3 successfully passed the validation test cases with scale and performance parameters observed within anticipated limits.

The validation testing focused on delivering a Seamless MBH solution across BGP-LU stitched domains with ACX710 and ACX5448 in roles supporting 4G/5G Access Node and Pre-Aggregation packet-switched transport CSR-to-SAG, CSR-to-HSR, and HSR-to-SAG.

Contact your Juniper Networks representative for test result reports.

The JVD validation demonstrated a robust solution for 5G xHaul transport infrastructure utilizing Seamless SR and color-aware network pre-slicing concepts. The architecture provides for resilient and agile deployment, spanning multiple IGP domains and autonomous systems with end-to-end flexibility, path management, and traffic steering.

Key results are as follows:

  • JVD topology generates reasonable multi-vector scale of L2/L3 connectivity services as compared with mobile network operator (MNO) and metro area network (MAN) operator expectations for real network deployments, while satisfying SLA requirements.
  • The scale reference characterizes primary multidimensional KPI’s represented in the validated profile.
  • With given network design, the architecture can deliver fast restoration within 50ms for most traffic flows transported over ISIS-SR with TI-LFA.
  • Load distribution and optimization knobs were shown to improve service restoration against link/node failures.
  • Link events consistently achieve <50ms convergence while node failures were more disruptive than expected, exacerbated by scale and in some rare cases, production limitations.

ACX710 and ACX5448 Universal Metro Routers with Junos OS release 21.2R3 can deliver the solutions outlined herein across intra and interdomain architectures. Both platforms are ideally situated for access roles and ACX5448 Universal Metro Router can be further leveraged in an aggregation HSR role.

Load sharing operations are enabled on all devices for ECMP opportunities across Fronthaul, Midhaul, and Backhaul segments. Several ECMP mechanisms were configured including adjusting IGP metrics, BGP multipath and add-path, and ECMP fast-reroute. Colored underlay slices are available for all supported services. For example, bronze services are load shared across only blue paths and gold services are load shared across only red paths. Contact your Juniper Networks representative for the colored traffic distribution information. Color agnostic services are shown to always select and disperse over best paths. The distribution of traffic flows resulted in significantly reduced impact for most failure scenarios.

Contact your Juniper Networks representative for hash computation and ECMP validation information.

The goal of this JVD is to identify anomalous behaviors which might impact solution design.

The solution resiliency was validated against multiple stress conditions and failure scenarios which include but not limited to:

  • Adjacent link failures
  • Indirect link failures
  • Node failures

Table 1 summarizes some key results for Layer 2/Layer 3 services traffic flows restoration under failure conditions. The color-coded Events column represents the expected network slice that must be impacted by the described failure condition. For all test scenarios, we run nearly 200 traffic flows—with each bundling congruent VPN services and encompassing all VPN types—between each Access Node (CSR) to AG1s (HSR), ANs to SAG and AG1s to SAG. In greater majority of cases, the failure recovery measured <50ms but always the traffic item with the highest impact is recorded.

For example, in Table 1, the event AN2(R0) link disable (R0-R4), a red link is disabled between R0-R4, and the expected impact is to services which are mapped to red or color-agnostic.

Table 1: Convergence Times for Access Failure Events Per Flow Type
  L3VPN (ms) L2VPN (ms) L2CKT (ms) VPLS (ms)
Events FG-128 FG-129 IPv6 (no FG) FG-128 FG-129 FG-128 FG-129 No FG
AN2(R0) link disable (R0-R4) 263 0 0 2 0 0 0 0
AN2(R0) link enable (R0-R4) 186 0 0 2 0 0 0 1
AN3(R4) link disable (R4-R9) 0 14 0 0 3 0 290 0
AN3(R4) link enable (R4-R9) 0 0 0 0 5 0 5 2
AN3(R4) link disable (R4-R9) 8 0 0 8 0 0 0 2
AN3(R4) link enable (R4-R9) 143 0 0 10 2 0 5 4

Table 2 lists the results that were initially measured with higher failover. It was determined that the convergence delay was ECMP routing table update following the failure and hash algorithm calculating the new paths. By enabling equal-cost-multipath fast reroute protection (ecmp-fastreroute) on the SAG (R16), we were able to refresh ECMP information without waiting for route table update.

Table 2: Convergence times for Pre-Aggregation and Aggregation Failure Events Per Flow Type
  L3VPN (ms) L2VPN (ms) L2CKT (ms) VPLS (ms)
Events FG-128 FG-129 IPv6 (no FG) FG-128 FG-129 FG-128 FG-129 No FG
AG1.2 (R9) link disable (R9-R8)

10

(1093)

0 0

11

(1094)

0 1 0 1
AG1.2 (R9) link enable (R9-R8) 0 0 0 5 0 5 0 1
AG1.2 (R9) link disable (R9-R8)) 0 0 0 0 3 0 5 0
AG1.2 (R9) link disable (R9-R8) 0 0 0 4 5 0 2 1
AG1.2 (R9) link disable (R9-R11) 34 0 7 40 0 43 0

8

(6388)

AG1.2 (R9) link disable (R9-R11) 0 0 0 2 2 3 10 2
AG1.2 (R9) link disable (R9-R11) 0 13 1 0 18 0 20 2
AG1.2 (R9) link disable (R9-R11) 0 0 0 5 2 2 1 0
AG2.2(R11) link disable (R11-R13) 63 3 33 66 0 66 0 45
AG2.2(R11) link enable (R11-R13) 0 0 0 2 0 1 0 0
AG2.2(R11) link disable (R11-R13) 0 59 29 0 56 0 54 45
AG2.2(R11) link enable (R11-R13) 0 6 0 0 11 0 12 0
Table 3: Convergence Times for Core and SAG Failure Events Per Flow Type
  L3VPN (ms) L2VPN (ms) L2CKT (ms) VPLS (ms)
Events FG-128 FG-129 IPv6 (no FG) FG-128 FG-129 FG-128 FG-129 No FG
AG3.2 (R13) link disable (R13-R15))

0

(38)

0 14

0

(45)

0

0

(36)

0 22
AG3.2 (R13) link enable (R13-R15) 1 0 0 5 0 4 0 0
AG3.2 (R13) link disable (R13-R15) 0 43 19 0 50 0 44 28
AG3.2 (R13) link enable (R13-R15) 0 0 0 0 5 0 4 0
CR2 (R15) link disable (R15-R16) 57 69 67 60 67 63 64

61

(2006)

CR2 (R15) link enable (R15-R16) 0 0 0 0 0 0 0 0

There is further delay in scenarios where global repair is triggered rather than managed by Broadcom ASIC with HW FRR. Additionally, BFD FRR is not supported on ACX5448 or ACX710 Universal Metro Router. Adjusting revertive timers can help control service restoration but overall, these results were mostly within expectation.

footer-navigation