ON THIS PAGE
Test Objectives
JVDs are 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 port fan out solution validates that PE's IFL is a demarcation line between the fan-out domain and the rest of the provider's network and is completely agnostic of services provided on a PE. The PE device is configured with customer facing IFLs to accept customer's frames and the PE processes it in accordance with services configured on that IFL. Hence, the services on PE's IFLs are orthogonal to port fan-out and can be any point-to-point or multipoint L2 and/or L3 services.
Validation Goals
The focus of the testing is to validate that the port fan-out Solution includes, but not limited to, the following features:
- L2circuit for point-to-point services between CEs
- L2VPN (VPWS, VPLS and EVPN-MPLS) for multipoint L2 services
- L3VPN for L3 VPN services
- QoS/CoS—Policing, QoS classification, filters, scheduling, and queueing
- OAM's Connectivity Fault Management (CFM) (IEEE 802.1g, ITU-T G.8013 / Y.1731) with UP MEP on FO and DOWN MEP on PE's
- CFM's continuity check Message (CCM) to detect loss of continuity between a pair of MEPs
- Asynchronous notification (laser-off) on fan-out’s CE-facing IFD
- PE–PE fault propagation using underlying status TLV in an LDP-signaled L2 circuit
The validation confirms that solution provides:
- A consistent traffic steering between fan-out device and service logical interfaces of the adjacent PE device
- A consistent fault and state propagation between fan-out and adjacent PE for failure and restore events
- A consistent fault propagation between local and remote FO nodes
- A consistent fault propagation between local and remote PE nodes
- A consistent system behavior on restoration events
Additional validations were performed to measure impact of:
- Restart/Kill of critical Junos OS or Junos OS Evolved processes and assess its impact
- Device reboot to evaluate impact in the network
- Interface flap events to evaluate impact on network traffic
- Deletion or configuration of various configuration stanzas to evaluate impact of node and network stability
- Clearing of protocol sessions to simulate protocol session flap and assess its impact on service and traffic
Validation Non-Goals
The following items were not part of the solution validation goals:
- Fan-out and PE devices’ management plane integration
- Traffic steering based on three VLAN tags: C-VLAN, S-VLAN, FO-PE Multiplexing VLAN
- Protocols other than mentioned in the “Validation Goals” section