Results Summary and Analysis
For the 3-stage JVD, comprehensive functional testing was performed on devices listed in Table 1 to validate the Junos OS Release 22.2R3-S3 and Apstra 4.2.1:
Baseline System Test:
- Enabling devices for Apstra, applying pristine configuration, and designing logical devices and interface maps.
- Apstra Provisioning of the entire 3-stage using the Data Center Reference Architecture feature of Apstra, involving racks, Templates, and blueprints, assigning interface maps and resources to switches, and cabling switches.
- Modifying Apstra blueprints to swap border leaf switches during testing.
- Apstra commits to deploy configurations to devices.
- Provisioning virtual networks and routing zones, assigning EVPN loopbacks for VRFs, and IRB interfaces through Apstra.
Operational and Trigger Tests:
- Operational testing of switches was carried out for the following:
- Device upgrade to 22.2R3-S3 release
- Reboot devices cause no issues when the devices boot up
- Process Restarts—l2ald, interface-control, rpd—aim to minimize packet loss and fully restore the control and data plane.
- Move 4 MAC hosts from one port to another without connectivity issues.
- BFD failover tests by deactivating BGP on the leaf switches with ESI configured to allow for traffic convergence.
- Reset DHCP Bindings to ensure fabric forwards the DHCP requests and address assignment should be released and reassigned.
- Extended negative tests (process restart, deactivate BGP, link failures) in an 8-hour cycle to ensure switches restore to baseline state and resume normal traffic forwarding.
- Connectivity tests for the following items were carried out:
- Service leaf link failure
- Multihomed link failure
- Leaf-to-spine link failure
- Resiliency tests for overlay connectivity testing for the below scenarios:
- Intra-VLAN
- Inter-VLAN to every host
- Traffic to external route
- DHCP client/server flows
Scale testing numbers are as shown in Table 1.
Features | Tested Scale Numbers | Tested Scale Numbers with EX4400* ESI Leaf pair |
---|---|---|
VLANs | 500 | 500 |
V4 host entries (MAC-IP) | 35500 | 17500 |
V6 host entries (NDP) | 1400 | 1400 |
VNI | 500 | 500 |
VTEP | 6 | 6 |
ESI | 4 | 4 |
IRB | 500 | 500 |
BGP Routing Table | 343000 | 148900 |
EVPN Table | 35500 | 17500 |
The scale numbers above are not device maximums; they only reference the scale at which these multidimensional test cases are performed.
The maximum VLANs per aggregated Ethernet (AE) interface is 2,000 on the QFX5120 and 1,000 on the EX. Attempting to define more VLANs than this on these platforms will cause a commit warning of too many VLAN IDs on an untagged interface.
Overall, the JVD validation testing didn’t detect any issues, and all performance parameters were within the threshold and performed as expected. Traffic profiles tested on all server leaf switches for intra-VRF, inter-VRF, and external routes were 1000 pps with a random packet size of 256-1024 bytes.