ON THIS PAGE
Test Objectives
This 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.
Using this JVD, you can significantly reduce the risk of costly mistakes while saving time and money in the deployment of network solutions. A JVD-based network provides benefits such as a more stable network with fewer bugs and a shorter time to resolution if any bugs are discovered. The validation process ensures that the network is optimized for maximum performance, leading to a better user experience for enterprise, service provider operation, and network service consumers. Furthermore, the design concepts deployed are formulated around best practices, leveraging relevant technologies to deliver the scope of the solution. KPIs are identified as part of an extensive test plan that focuses on functionality, performance integrity, and service delivery. With JVDs, you can shorten the time to market when implementing new network solutions, reducing the lead time to generate revenue from new services.
The key test 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
Test Goals
There are two test goals to achieve in this JVD.
The primary goal of the tests is to confirm that automation enhances the existing 5G Fronthaul JVD solution ( Low Latency QoS Design for 5G Solution ). These automation enhancements aim to streamline network operations and improve overall efficiency. Their success is defined by several critical goals. These goals ensure that the automated processes are seamlessly integrated and effectively improve the overall network solution.
Key success criteria include:
- DHCP/Bootstrap server integration. A DHCP server is assumed to be inserted at Service Edge.
- Aggregation nodes act as DHCP relays.
- Successful access nodes (AN) onboarding through ZTP.
- After onboarding, the devices are managed by Paragon Automation.
- Paragon Automation can communicate with DUT using different interfaces (SSH/CLI, gNMI, NETCONF/YANG).
- Paragon Automation has an updated inventory of all onboard devices.
- Paragon Automation manages the lifecycle of the devices (SW upgrades/downgrades, configuration backup/restore, configuration template provisioning).
- DUT stream telemetry to Paragon Automation.
- Paragon Automation collects and displays telemetry from DUT at device level (CPU, memory, power supplies, fans, and so on).
- Network management traffic is classified as QoS.
- Telemetry is in-band and classified as network control traffic.
The secondary goal is to confirm not only that this JVD solution in which this automation JVD is based, is not adversely affected by the Paragon Automation and still ensures that the advanced CoS features of the ACX7000 series routers meet the requirements for reliable and high-quality performance in 5G Fronthaul, but also that the CoS behaviors are consistent throughout the mobile backhaul topology and across different devices.
Test Non-Goals
As the Paragon Automation solution is being continuously developed, there are still a few things which might not be available and are out of scope of the current solution:
- Paragon Automation currently lacks DHCP/Bootstrap server. ZTP is not supported by Paragon Automation and the current DHCP solution is a workaround.
- Paragon Automation does not support all the devices (for example, CU/DU QFX5210 (Helper node)).
- Only access nodes are onboarded automatically. Any aggregation or core nodes are onboarded manually (CLI) and provisioned by a script.
- Network observability (focused on device level only).
- Network assurance (focused on device level only).
- Service orchestration and provisioning.
- Service assurance.
Paragon Automation negative test cases are out of scope (loss of a worker/master node, loss of connectivity to a network node, SW upgrade of the worker/master, full cluster reboot, cluster running out of disk space, and so on). This JVD first phase does not consider these tests as part of the solution validation, but part of the product validation.
| Devices Under Test | |||
|---|---|---|---|
| Role | Platform | Device Series | Release |
| AN1 (Access Node) | ACX Series | ACX-7100-48L | Junos OS Evolved Release 24.2R2 |
| AN4 (Access Node) | ACX Series | ACX-7024 | Junos OS Evolved Release 24.2R2 |
| AN3 (Access Node) | ACX Series | ACX-7100-48L | Junos OS Evolved Release 24.2R2 |
| AG1.1 (Aggregation Node) | ACX Series | ACX7509 | Junos OS Evolved Release 24.2R2 |
| AG1.2 (Aggregation Node) | ACX Series | ACX-7100-32C | Junos OS Evolved Release 24.2R2 |
| AG2.1 (Aggregation Node) | MX Series | MX204 | Junos OS Release 24.2R2 |
| AG2.2 (Aggregation Node) | MX Series | MX204 | Junos OS Release 24.2R2 |
| AG3.1 (Aggregation Node) | MX Series | MX480 | Junos OS Release 24.2R2 |
| AG3.2 (Aggregation Node) | MX Series | MX480 | Junos OS Release 24.2R2 |
| CU/DU | QFX Series | QFX5210 | Junos OS Release 24.2R2 |
| SAG (Services Aggregation Gateway) | MX Series | MX304 | Junos OS Release 24.2R2 |
| CR1 | PTX Series | PTX10001-36MR | Junos OS Evolved Release 24.2R2 |
| CR2 | PTX Series | PTX10001-36MR | Junos OS Evolved Release 24.2R2 |