Repository navigation
hashing_test
Verify Dataplane Hashing (ECMP, WCMP, and Intra-LAG) using physical loopback ports across multiple Network Instances (DEFAULT, SELF_SITE, EGRESS).
The test suite validates hashing uniformity, weight enforcement, and anti-polarization across two traffic profiles:
- Plain IPv4/IPv6 Traffic (5-tuple entropy).
- IPnIP Encapsulated Traffic (Outer IP static, inner 5-tuple entropy).
The testbed requires a DUT (dut_8_loop_2_ate.testbed) and an ATE.
The topology utilizes physical loopback pairs to route and verify traffic across multiple hashing stages on the DUT without relying on software drop loops.
graph LR
subgraph ATE ["ATE (Traffic Generator)"]
ate2["Port 1 (ixia2) - Ingress"]
ate1["Port 10 (ixia1) - Egress"]
end
subgraph DUT ["DUT (dut_8_loop_2_ate)"]
inPort["lc2_p10 (Ingress Port 1)"]
egPort["lc2_p9 (Egress Port 10)"]
subgraph PhysLoops ["Physical Loopbacks (8 Loops)"]
l1["lc1_p3 <--> lc2_p3 (Loop 1: Ingress -> SelfSite)"]
l2["lc1_p4 <--> lc2_p4 (Loop 2: Ingress -> SelfSite)"]
l3["lc1_p5 <--> lc2_p5 (Loop 3: Ingress -> Egress)"]
l4["lc1_p6 <--> lc2_p6 (Loop 4: Ingress -> Egress)"]
l5["lc1_p1 <--> lc2_p1 (Loop 5: SelfSite -> Egress)"]
l6["lc1_p8 <--> lc2_p8 (Loop 6: SelfSite -> Egress)"]
l7["lc1_p7 <--> lc2_p7 (Loop 7: SelfSite -> Egress)"]
l8["lc1_p2 <--> lc2_p2 (Loop 8: SelfSite -> Egress)"]
end
end
ate2 <-->|Ingress Link| inPort
egPort <-->|Egress Link| ate1
The test utilizes all 8 physical loopback cables and 2 ATE links on dut_8_loop_2_ate.testbed:
-
Physical Loopbacks:
-
Loop 1 (Port 2):
lc1_p3(Ingress) <->lc2_p3(SelfSite) -
Loop 2 (Port 3):
lc1_p4(Ingress) <->lc2_p4(SelfSite) -
Loop 3 (Port 4):
lc1_p5(Ingress) <->lc2_p5(Egress) -
Loop 4 (Port 5):
lc1_p6(Ingress) <->lc2_p6(Egress) -
Loop 5 (Port 6):
lc1_p1(SelfSite) <->lc2_p1(Egress) -
Loop 6 (Port 7):
lc1_p8(SelfSite) <->lc2_p8(Egress) -
Loop 7 (Port 8):
lc1_p7(SelfSite) <->lc2_p7(Egress) -
Loop 8 (Port 9):
lc1_p2(SelfSite) <->lc2_p2(Egress)
-
Loop 1 (Port 2):
-
ATE Connections:
-
ATE Ingress Port 1 (
ixia2) connects to DUT Port lc2_p10 (Ingress source). -
ATE Egress Port 10 (
ixia1) connects to DUT Port lc2_p9 (Egress sink).
-
ATE Ingress Port 1 (
All test scenarios are executed against the following two traffic profiles:
- Header Structure: Standard Ethernet + IPv4/IPv6 + UDP/TCP.
-
Entropy Generation:
- Destination IP: Random within target subnet
198.51.100.0/24. - Source IP: Incrementing / pseudo-random addresses across a /16 range.
- L4 Ports: Source and Destination UDP ports incremented across 1024–65535.
- Destination IP: Random within target subnet
- Verification: Evaluates native 5-tuple hash distribution across member next-hops.
- Header Structure: Outer IPv4 Header + Inner IPv4 Header + UDP Payload.
-
Outer Header:
- Source IP: Static
10.10.10.1. - Destination IP: Incrementing across
172.16.0.1to172.16.0.254(count 254).
- Source IP: Static
- Inner Header: 5-tuple varied IPv4 + UDP packets (1,009 src IPs, 1,013 dst IPs, 1,019 src UDP ports, 1,021 dst UDP ports).
- Verification: Verifies that the DUT hashing engine parses and computes hash keys from both outer and inner packet headers, ensuring uniform distribution without tunnel polarization.
The acceptable hashing distribution across any set of next-hops or LAG member links is defined with a
Examples:
- Expected 20.00% (1/5 share)
$\rightarrow$ Acceptable Range: 19.60% to 20.40% - Expected 33.33% (3-wide equal)
$\rightarrow$ Acceptable Range: 32.66% to 34.00% - Expected 60.00% (6/10 weight)
$\rightarrow$ Acceptable Range: 58.80% to 61.20% - Expected 14.28% (7-member LAG)
$\rightarrow$ Acceptable Range: 14.00% to 14.57% - Expected 42.86% (3:2:2 weight)
$\rightarrow$ Acceptable Range: 42.00% to 43.71%
Verifies end-to-end dataplane hashing across DEFAULT (Ingress), SELF_SITE, and EGRESS network instances using an 8-loop topology across two sub-cases:
-
Ingress VRF (
DEFAULT): Evaluates 4-way WCMP (4:3:2:1 weights) across:-
Port 2 (
lc1_p3-> SelfSite): Weight 4 (40.0%) -
Port 3 (
lc1_p4-> SelfSite): Weight 3 (30.0%) -
Port 4 (
lc1_p5-> Egress): Weight 2 (20.0%) -
Port 5 (
lc1_p6-> Egress): Weight 1 (10.0%) Total weight: 10. Split is 70% toSELF_SITE(Ports 2 & 3) and 30% direct toEGRESS(Ports 4 & 5).
-
Port 2 (
-
SelfSite VRF (
SELF_SITE): Receives 70% of traffic. Evaluates 4-way ECMP (1:1:1:1 equal weight) across:-
Port 6 (
lc1_p1-> Egress): 17.5% of total traffic (25% of SelfSite share) -
Port 7 (
lc1_p8-> Egress): 17.5% of total traffic (25% of SelfSite share) -
Port 8 (
lc1_p7-> Egress): 17.5% of total traffic (25% of SelfSite share) -
Port 9 (
lc1_p2-> Egress): 17.5% of total traffic (25% of SelfSite share)
-
Port 6 (
-
Egress VRF (
EGRESS): Recombines all 6 forwarded streams:- Direct from Ingress: Port 4 (20%), Port 5 (10%)
- Indirect via SelfSite: Ports 6, 7, 8, 9 (17.5% each)
Total arriving: 100%. All forwarded out Port 10 (
lc2_p9) to ATE Egress (ixia1).
graph TD
Ixia["ATE Ingress: Port 1 (ixia2)"] --> IngressPort1["Ingress: Port 1 (lc2_p10)"]
subgraph IngressVRF ["Ingress VRF (NHG_01: 4:3:2:1 WCMP)"]
IngressPort1 -->|"40% (Weight 4)"| IngressP2["Port 2 (lc1_p3)"]
IngressPort1 -->|"30% (Weight 3)"| IngressP3["Port 3 (lc1_p4)"]
IngressPort1 -->|"20% (Weight 2)"| IngressP4["Port 4 (lc1_p5)"]
IngressPort1 -->|"10% (Weight 1)"| IngressP5["Port 5 (lc1_p6)"]
end
IngressP2 -->|"Loop 1 (40%)"| SelfSiteP2["SelfSite: Port 2 (lc2_p3)"]
IngressP3 -->|"Loop 2 (30%)"| SelfSiteP3["SelfSite: Port 3 (lc2_p4)"]
IngressP4 -->|"Loop 3 (20%)"| EgressP4["Egress: Port 4 (lc2_p5)"]
IngressP5 -->|"Loop 4 (10%)"| EgressP5["Egress: Port 5 (lc2_p6)"]
subgraph SelfSiteVRF ["SelfSite VRF (NHG_02: 1:1:1:1 ECMP - 70% Share)"]
SelfSiteP2 -.->|ECMP| SelfSiteP6["Port 6 (lc1_p1): 17.5%"]
SelfSiteP2 -.->|ECMP| SelfSiteP7["Port 7 (lc1_p8): 17.5%"]
SelfSiteP2 -.->|ECMP| SelfSiteP8["Port 8 (lc1_p7): 17.5%"]
SelfSiteP2 -.->|ECMP| SelfSiteP9["Port 9 (lc1_p2): 17.5%"]
SelfSiteP3 -.->|ECMP| SelfSiteP6
SelfSiteP3 -.->|ECMP| SelfSiteP7
SelfSiteP3 -.->|ECMP| SelfSiteP8
SelfSiteP3 -.->|ECMP| SelfSiteP9
end
SelfSiteP6 -->|"Loop 5 (17.5%)"| EgressP6["Egress: Port 6 (lc2_p1)"]
SelfSiteP7 -->|"Loop 6 (17.5%)"| EgressP7["Egress: Port 7 (lc2_p8)"]
SelfSiteP8 -->|"Loop 7 (17.5%)"| EgressP8["Egress: Port 8 (lc2_p7)"]
SelfSiteP9 -->|"Loop 8 (17.5%)"| EgressP9["Egress: Port 9 (lc2_p2)"]
subgraph EgressVRF ["Egress VRF (6-Stream Arrival)"]
EgressP4 --> EgressOut["Port 10 (lc2_p9)"]
EgressP5 --> EgressOut
EgressP6 --> EgressOut
EgressP7 --> EgressOut
EgressP8 --> EgressOut
EgressP9 --> EgressOut
end
EgressOut --> ATE_Egress["ATE Egress: Port 10 (ixia1)"]
-
Ingress VRF (
DEFAULT): Evaluates 4-way ECMP (1:1:1:1 equal weight) across Ports 2, 3, 4, 5 (25.0% each). Total weight: 4. Split is 50% toSELF_SITE(Ports 2 & 3) and 50% toEGRESS(Ports 4 & 5). -
SelfSite VRF (
SELF_SITE): Receives 50% of traffic. Evaluates 4-way ECMP (1:1:1:1) across Ports 6, 7, 8, 9 (12.5% of total traffic each). -
Egress VRF (
EGRESS): Recombines all 6 streams:- Direct from Ingress: Port 4 (25%), Port 5 (25%)
- Indirect via SelfSite: Ports 6, 7, 8, 9 (12.5% each)
Total arriving: 100%. All forwarded out Port 10 (
lc2_p9) to ATE Egress (ixia1).
graph TD
Ixia["ATE Ingress: Port 1 (ixia2)"] --> IngressPort1["Ingress: Port 1 (lc2_p10)"]
subgraph IngressVRF_ECMP ["Ingress VRF (NHG_01: 1:1:1:1 ECMP)"]
IngressPort1 -->|"25% (Weight 1)"| IngressP2_e["Port 2 (lc1_p3)"]
IngressPort1 -->|"25% (Weight 1)"| IngressP3_e["Port 3 (lc1_p4)"]
IngressPort1 -->|"25% (Weight 1)"| IngressP4_e["Port 4 (lc1_p5)"]
IngressPort1 -->|"25% (Weight 1)"| IngressP5_e["Port 5 (lc1_p6)"]
end
IngressP2_e -->|"Loop 1 (25%)"| SelfSiteP2_e["SelfSite: Port 2 (lc2_p3)"]
IngressP3_e -->|"Loop 2 (25%)"| SelfSiteP3_e["SelfSite: Port 3 (lc2_p4)"]
IngressP4_e -->|"Loop 3 (25%)"| EgressP4_e["Egress: Port 4 (lc2_p5)"]
IngressP5_e -->|"Loop 4 (25%)"| EgressP5_e["Egress: Port 5 (lc2_p6)"]
subgraph SelfSiteVRF_ECMP ["SelfSite VRF (NHG_02: 1:1:1:1 ECMP - 50% Share)"]
SelfSiteP2_e -.->|ECMP| SelfSiteP6_e["Port 6 (lc1_p1): 12.5%"]
SelfSiteP2_e -.->|ECMP| SelfSiteP7_e["Port 7 (lc1_p8): 12.5%"]
SelfSiteP2_e -.->|ECMP| SelfSiteP8_e["Port 8 (lc1_p7): 12.5%"]
SelfSiteP2_e -.->|ECMP| SelfSiteP9_e["Port 9 (lc1_p2): 12.5%"]
SelfSiteP3_e -.->|ECMP| SelfSiteP6_e
SelfSiteP3_e -.->|ECMP| SelfSiteP7_e
SelfSiteP3_e -.->|ECMP| SelfSiteP8_e
SelfSiteP3_e -.->|ECMP| SelfSiteP9_e
end
SelfSiteP6_e -->|"Loop 5 (12.5%)"| EgressP6_e["Egress: Port 6 (lc2_p1)"]
SelfSiteP7_e -->|"Loop 6 (12.5%)"| EgressP7_e["Egress: Port 7 (lc2_p8)"]
SelfSiteP8_e -->|"Loop 7 (12.5%)"| EgressP8_e["Egress: Port 8 (lc2_p7)"]
SelfSiteP9_e -->|"Loop 8 (12.5%)"| EgressP9_e["Egress: Port 9 (lc2_p2)"]
subgraph EgressVRF_ECMP ["Egress VRF (6-Stream Arrival)"]
EgressP4_e --> EgressOut_e["Port 10 (lc2_p9)"]
EgressP5_e --> EgressOut_e
EgressP6_e --> EgressOut_e
EgressP7_e --> EgressOut_e
EgressP8_e --> EgressOut_e
EgressP9_e --> EgressOut_e
end
EgressOut_e --> ATE_Egress_e["ATE Egress: Port 10 (ixia1)"]
-
Sub-case 1.1 (WCMP 4:3:2:1 Expected):
-
Stage 1 (Ingress): Port 2: 40.0%, Port 3: 30.0%, Port 4: 20.0%, Port 5: 10.0% (acceptable:
$\pm2%$ relative). - Stage 2 (SelfSite): Ports 6, 7, 8, 9: 25.0% each of SelfSite volume.
- Stage 3 (Egress Multi-Stream): Port 4 (20.0%), Port 5 (10.0%), Ports 6, 7, 8, 9 (17.5% each).
- Stage 4 (ATE Arrival): 100% full arrival on ATE Port 10 (0 packet loss).
-
Stage 1 (Ingress): Port 2: 40.0%, Port 3: 30.0%, Port 4: 20.0%, Port 5: 10.0% (acceptable:
-
Sub-case 1.2 (ECMP 1:1:1:1 Expected):
-
Stage 1 (Ingress): Ports 2, 3, 4, 5: 25.0% each (acceptable:
$\pm2%$ relative). - Stage 2 (SelfSite): Ports 6, 7, 8, 9: 25.0% each of SelfSite volume.
- Stage 3 (Egress Multi-Stream): Port 4 (25.0%), Port 5 (25.0%), Ports 6, 7, 8, 9 (12.5% each).
- Stage 4 (ATE Arrival): 100% full arrival on ATE Port 10 (0 packet loss).
-
Stage 1 (Ingress): Ports 2, 3, 4, 5: 25.0% each (acceptable:
-
Traffic Profiles: Execute for Plain IP and IPnIP Encap.
Verifies traffic load balancing across member links within a single Link Aggregation Group (LAG). Traffic received on the Ingress interface is looked up in the TRANSIT VRF and routed to a single Next-Hop consisting of a 7-member LAG bundle.
graph TD
Ingress["ATE Ingress: Port 2 (ixia2)"] --> IngressPort["DUT Ingress: lc2_p10"]
IngressPort --> DefaultVRF["Default VRF (Loop 1 -> Transit)"]
DefaultVRF --> TransitVRF["Transit VRF"]
subgraph SingleNH ["Single Next-Hop: 7-Member LAG"]
TransitVRF --> M1["Member Port 1: ~14.28%"]
TransitVRF --> M2["Member Port 2: ~14.28%"]
TransitVRF --> M3["Member Port 3: ~14.28%"]
TransitVRF --> M4["Member Port 4: ~14.28%"]
TransitVRF --> M5["Member Port 5: ~14.28%"]
TransitVRF --> M6["Member Port 6: ~14.28%"]
TransitVRF --> M7["Member Port 7: ~14.28%"]
end
SingleNH --> EgressVRF["Egress VRF"] --> EgressPort["DUT Egress: lc2_p9"] --> Egress["ATE Egress (ixia1)"]
-
Expected Distribution: Uniform distribution across all 7 active member links:
- Per-Member Expected: ~14.28% (acceptable range: 14.00% – 14.57%).
- Traffic Profiles: Execute for Plain IP and IPnIP Encap.
Assesses the ability of the dataplane hashing engine to handle asymmetric next-hop capacities and verifies that software-programmed weights either align with or override physical member link counts.
The TRANSIT VRF is configured with 3 Next-Hops having unequal member link capacities:
- LAG A: 3 member links.
- LAG B: 2 member links.
- LAG C: 2 member links.
graph TD
TransitVRF["Transit VRF (3 Next-Hops with Asymmetric Capacity)"]
subgraph AsymmetricPaths ["3 Next-Hops (Unequal Members)"]
TransitVRF -->|LAG A| LagA["LAG A: 3 Member Links"]
TransitVRF -->|LAG B| LagB["LAG B: 2 Member Links"]
TransitVRF -->|LAG C| LagC["LAG C: 2 Member Links"]
end
LagA --> EgressVRF["Egress VRF"]
LagB --> EgressVRF
LagC --> EgressVRF
EgressVRF --> Egress["ATE Egress (ixia1)"]
- Goal: Validates proportional distribution when weights align with physical link capacity.
-
gRIBI Programming: Program NHG with weights
3 : 2 : 2matching the member counts of LAG A, LAG B, and LAG C. -
Expected Distribution:
- LAG A (weight 3): ~42.86% (acceptable range: 42.00% – 43.71%).
- LAG B (weight 2): ~28.57% (acceptable range: 28.00% – 29.14%).
- LAG C (weight 2): ~28.57% (acceptable range: 28.00% – 29.14%).
- Traffic Profiles: Execute for Plain IP and IPnIP Encap.
- Goal: Validates that software-configured weights strictly override physical underlying capacity.
-
gRIBI Programming: Program NHG with uniform weights
1 : 1 : 1across LAG A, LAG B, and LAG C. -
Expected Distribution:
- LAG A (weight 1): ~33.33% (acceptable range: 32.66% – 34.00%).
- LAG B (weight 1): ~33.33% (acceptable range: 32.66% – 34.00%).
- LAG C (weight 1): ~33.33% (acceptable range: 32.66% – 34.00%).
- Traffic Profiles: Execute for Plain IP and IPnIP Encap.
{
"interfaces": {
"interface": [
{
"config": {
"enabled": true,
"name": "ae1",
"type": "ieee8023adLag"
},
"name": "ae1"
},
{
"config": {
"enabled": true,
"name": "ae2",
"type": "ieee8023adLag"
},
"name": "ae2"
},
{
"config": {
"enabled": true,
"name": "eth1",
"type": "ethernetCsmacd"
},
"ethernet": {
"config": {
"aggregate-id": "ae1"
}
},
"name": "eth1"
},
{
"config": {
"enabled": true,
"loopback-mode": "TERMINAL",
"name": "eth2",
"type": "ethernetCsmacd"
},
"ethernet": {
"config": {
"aggregate-id": "ae2"
}
},
"name": "eth2"
}
]
},
"network-instances": {
"network-instance": [
{
"config": {
"name": "DEFAULT",
"type": "DEFAULT_INSTANCE"
},
"interfaces": {
"interface": [
{
"config": {
"id": "ae1",
"interface": "ae1"
},
"id": "ae1"
}
]
},
"name": "DEFAULT"
},
{
"config": {
"name": "TRANSIT",
"type": "L3VRF"
},
"interfaces": {
"interface": [
{
"config": {
"id": "ae2",
"interface": "ae2"
},
"id": "ae2"
}
]
},
"name": "TRANSIT"
},
{
"config": {
"name": "SELF_SITE",
"type": "L3VRF"
},
"name": "SELF_SITE"
},
{
"config": {
"name": "EGRESS",
"type": "L3VRF"
},
"name": "EGRESS"
}
]
}
}paths:
/interfaces/interface/config/name:
/interfaces/interface/config/enabled:
/interfaces/interface/config/loopback-mode:
/interfaces/interface/ethernet/config/aggregate-id:
/interfaces/interface/aggregation/config/lag-type:
/interfaces/interface/state/counters/in-pkts:
/interfaces/interface/state/counters/out-pkts:
/network-instances/network-instance/config/name:
/network-instances/network-instance/config/type:
/network-instances/network-instance/interfaces/interface/config/id:
/network-instances/network-instance/interfaces/interface/config/interface:
/acl/interfaces/interface/ingress-acl-sets/ingress-acl-set/config/set-name:
/acl/interfaces/interface/ingress-acl-sets/ingress-acl-set/config/type:
rpcs:
gribi:
gRIBI.Modify:
gRIBI.Flush:
gnmi:
gNMI.Set:
gNMI.Get:
gNMI.Subscribe:-
Home
- Test Plans
- ACCTZ-1.1: Record Subscribe Full
- ACCTZ-2.1: Record Subscribe Partial
- ACCTZ-3.1: Record Subscribe Non-gRPC
- ACCTZ-4.1: Record History Truncation
- ACCTZ-4.2: Record Payload Truncation
- ACCTZ-5.1: gNSI.acctz.v1 (Accounting) Test RecordSubscribe Idle Timeout - client becomes silent
- ACCTZ-6.1: gNSI.acctz.v1 (Accounting) Test RecordSubscribe Idle Timeout - DoA client
- ACCTZ-7.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Failure - Multi-transaction
- ACCTZ-8.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Failure - Uni-transaction
- ACCTZ-9.1: gNSI.acctz.v1 (Accounting) Test Accounting Privilege Escalation
- ACCTZ-10.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Error - Multi-transaction
- ACL-1.1: ACL match based on L3/L4 fields and DSCP value
- ACL-1.2: ACL Update (Make-before-break)
- ACL-1.3: Large Scale ACL with TCAM profile
- AFT-1.1: AFTs Base
- AFT-1.2: AFTs slow collector
- AFT-1.3: AFTs collector Flap
- AFT-2.1: AFTs Prefix Counters
- AFT-3.1: AFTs Atomic Flag Check
- AFT-5.1: AFTs DUT Reboot
- AFT-6.1: AFT Prefix Filtering
- AFT-6.2: AFT Prefix Filtering Dual-Stack
- AFT-6.3: AFT Prefix Filtering Resilience
- AFT-6.4: AFT Prefix Filtering Dynamic Updates
- attestz-1: General enrollz and attestz tests
- Authz-1.0: General Authz (1-4) tests
- Authz-5: gRPC Server Per-RPC Statistics YANG State Bounding
- BMP-1.1: BMP Session Establishment and Telemetry Test
- BMP-2.7: BMP Pre Policy Test
- BMP-2.8: BMP Post Policy Test
- bootz-1.0: General bootz bootstrap tests
- Certz-1: gNSI Client Certificate Tests
- Certz-2: Server Certificate
- Certz-3: Server Certificate Rotation
- Certz-4: Trust Bundle
- Certz-5: Trust Bundle Rotation
- CFM-1.1: CFM over ETHoCWoMPLSoGRE
- CNTR-1: Basic container lifecycle via
gnoi.Containerz. - CNTR-2: Container network connectivity tests
- CNTR-3: Container Supervisor Failover
- CPT-1.1: Interface based ARP policer
- Credentialz-1: Password console login
- Credentialz-2: SSH Password Login Disallowed
- Credentialz-3: Host Certificates
- Credentialz-4: SSH Public Key Authentication
- Credentialz-5: Hiba Authentication
- DP-1.2: QoS policy feature config
- DP-1.3: QoS ECN feature config
- DP-1.4: QoS Interface Output Queue Counters
- DP-1.5: Egress Strict Priority scheduler with bursty traffic
- DP-1.7: One strict priority queue traffic test
- DP-1.8: Two strict priority queue traffic test
- DP-1.9: WRR traffic test
- DP-1.10: Mixed strict priority and WRR traffic test
- DP-1.11: Bursty traffic test
- DP-1.12: ECN enabled traffic test
- DP-1.13: DSCP and ECN bits are copied over during IPinIP encap and decap
- DP-1.14: QoS basic test
- DP-1.15: Egress Strict Priority scheduler
- DP-1.16: Ingress traffic classification and rewrite
- DP-1.17: DSCP Transparency with ECN
- DP-1.19: Egress traffic DSCP rewrite
- DP-2.2: QoS scheduler with 1 rate 2 color policer, classifying on next-hop group
- DP-2.4: Police traffic on input matching all packets using 1 rate, 2 color marker
- DP-2.5: Police traffic on input matching all packets using 2 rate, 3 color marker
- DP-2.6: Police traffic on input matching all packets using 2 rate, 3 color marker with classifier
- enrollz-1: enrollz test for TPM 2.0 HMAC-based Enrollment flow
- enrollz-2: enrollz test for TPM 1.2 Enrollment flow
- example-0.1: Topology Test
- FP-1.1: Power admin DOWN/UP Test
- FPGA-1.1: FPGA Status Test
- gNMI-1.1: cli Origin
- gNMI-1.2: Benchmarking: Full Configuration Replace
- gNMI-1.3: Benchmarking: Drained Configuration Convergence Time
- gNMI-1.4: Telemetry: Inventory
- gNMI-1.5: Telemetry: Port Speed Test
- gNMI-1.6: System gRPC Servers running in more than one network-instance
- gNMI-1.7: gNMI Resiliency Test
- gNMI-1.8: Configuration Metadata-only Retrieve and Replace
- gNMI-1.9: Get requests
- gNMI-1.10: Telemetry: Basic Check
- gNMI-1.11: Telemetry: Interface Packet Counters
- gNMI-1.12: Mixed OpenConfig/CLI Origin
- gNMI-1.13: Optics Telemetry, Instant, threshold, and miscellaneous static info
- gNMI-1.14: OpenConfig metadata consistency during large config push
- gNMI-1.15: Set Requests
- gNMI-1.16: Fabric redundnacy test
- gNMI-1.17: Controller card redundancy test
- gNMI-1.18: gNMI subscribe with sample mode for backplane capacity counters
- gNMI-1.19: ConfigPush and ConfigPull after Control Card switchover
- gNMI-1.20: Telemetry: Optics Thresholds
- gNMI-1.21: Integrated Circuit Hardware Resource Utilization Test
- gNMI-1.22: Controller card port attributes
- gNMI-1.23: Telemetry: Aggregate Interface Counters
- gNMI-1.24: gNMI Leaf-List Update Test
- gNMI-1.25: Telemetry: Interface Last Change Timestamp
- gNMI-1.26: Carrier Transitions Test
- gNMI-1.27: gNMI Sample Mode Test
- gNMI-1.28: Telemetry: Interface openconfig validation.
- gNMI-1.29: Pipeline Counters Drops Test
- gNMI-1.30: gNMI Telemetry Performance under Dynamic Control Plane Churn
- gNMI-2: gnmi_subscriptionlist_test
- gNMI-3: union_replace
- gNOI-2.1: Packet-based Link Qualification on 100G and 400G links
- gNOI-3.1: Complete Chassis Reboot
- gNOI-3.2: Per-Component Reboot
- gNOI-3.3: Supervisor Switchover
- gNOI-3.4: Chassis Reboot Status and Reboot Cancellation
- gNOI-4.1: Software Upgrade
- gNOI-5.1: Ping Test
- gNOI-5.2: Traceroute Test
- gNOI-5.3: Copying Debug Files
- gNOI-6.1: Factory Reset
- gNOI-7.1: BootConfig
- gNPSI-1: Sampling and Subscription Check
- HA-1.0: Telemetry: Firewall High Availability.
- Hashing-1.0: Dataplane Hashing with Physical Loopbacks
- Health-1.1: Generic Health Check
- Health-1.2: Healthz component status paths
- INT-1.1: Interface Performance
- IPSEC-1.1: IPSec with MACSec over aggregated links.
- IPSEC-1.2: IPSec Scaling with MACSec over aggregated links.
- IPSEC-1.3: IPSec Packet-Order with MACSec over aggregated links.
- LB-1.1: wECMP Hashing Polarization Detection
- MGT-1: Management HA solution test
- MGT-2: QoS of Control and Management Traffic
- MPLS-1.1: MPLS label blocks using ISIS
- MPLS-1.2: MPLS Traffic Class Marking
- MPLS-2.2: MPLS forwarding via static LSP to BGP next-hop.
- MSEC-1.1: MACsec Configuration and Verification (DUT-to-DUT)
- MTU-1.3: Large IP Packet Transmission
- MTU-1.4: Large IP Packet through GRE/GUE tunnel Transmission
- MTU-1.5: Path MTU handing
- OC-1.2: Default Address Families
- OC-26.1: Network Time Protocol (NTP)
- P4RT-1.1: Base P4RT Functionality
- P4RT-1.2: P4RT Daemon Failure
- P4RT-1.3: P4RT behavior when a device/node is down
- P4RT-2.1: P4RT Election
- P4RT-2.2: P4RT Metadata Validation
- P4RT-3.1: Google Discovery Protocol: PacketIn
- P4RT-3.2: Google Discovery Protocol: PacketOut
- P4RT-3.3: P4RT Packet-Out Interaction with gRIBI
- P4RT-3.4: P4RT Packet-In Interaction with gRIBI
- P4RT-3.21: Google Discovery Protocol: PacketOut with LAG
- P4RT-5.1: Traceroute: PacketIn
- P4RT-5.2: Traceroute Packetout
- P4RT-5.3: Traceroute: PacketIn With VRF Selection
- P4RT-6.1: Required Packet I/O rate: Performance
- P4RT-7.1: LLDP: PacketIn
- P4RT-7.2: LLDP: PacketOut
- Pathz-1: Path-level Authorization (1-4) tests
- PF-1.1: IPv4/IPv6 policy-forwarding to indirect NH matching DSCP/TC.
- PF-1.2: Policy-based traffic GRE Encapsulation to IPv4 GRE tunnel
- PF-1.3: Policy-based IPv4 GRE Decapsulation
- PF-1.4: GUEv1 Decapsulation rule using destination-address-prefix-set and TTL and DSCP behavior test
- PF-1.6: Policy based VRF selection for IPV4/IPV6
- PF-1.7: Decapsulate MPLS in GRE and UDP
- PF-1.8: Ingress handling of TTL
- PF-1.9: Egress handling of TTL
- PF-1.11: Rewrite the ingress innner packet TTL
- PF-1.12: MPLSoGRE IPV4 decapsulation of IPV4/IPV6 payload
- PF-1.13: MPLSoGRE IPV4 decapsulation of IPV4/IPV6 payload scale test
- PF-1.14: MPLSoGRE IPV4 encapsulation of IPV4/IPV6 payload
- PF-1.15: MPLSoGRE IPV4 encapsulation of IPV4/IPV6 payload scale test
- PF-1.16: MPLSoGRE IPV4 encapsulation IPV4/IPV6 local proxy test
- PF-1.17: MPLSoGRE and MPLSoGUE MACsec
- PF-1.18: MPLSoGRE and MPLSoGUE QoS
- PF-1.19: MPLSoGUE IPV4 decapsulation of IPV4/IPV6 payload
- PF-1.20: MPLSoGUE IPV4 decapsulation of IPV4/IPV6 payload scale test
- PF-1.21: Configurable IPv6 flow labels corresponding to IPV6 tunnels
- PF-1.22: GUEv1 Decapsulation and ECMP test for IPv4 and IPv6 payload
- PF-1.23: EthoCWoMPLSoGRE IPV4 forwarding of IPV4/IPV6 payload
- PF-1.24: Add and remove interface bound to PBF
- PF-1.25: Egress Static MPLS LSP Verification
- PF-1.26: Double GUEv1 Decapsulation for Overlay Probing
- PF-1.27: MPLSoGRE/MPLSoGUE MACsec and Line Rate Performance
- PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
- PLT-1.1: Interface breakout Test
- PLT-1.2: Parent component validation test
- PLT-1.3: OnChange Subscription Test for Breakout Interfaces
- RELAY-1.1: DHCP Relay functionality
- RT-1.1: Base BGP Session Parameters
- RT-1.2: BGP Policy & Route Installation
- RT-1.3: BGP Route Propagation
- RT-1.4: BGP Graceful Restart
- RT-1.5: BGP Prefix Limit
- RT-1.7: Local BGP Test
- RT-1.8: BGP Route Reflector Test at scale
- RT-1.10: BGP Keepalive and HoldTimer Configuration Test
- RT-1.11: BGP remove private AS
- RT-1.12: BGP always compare MED
- RT-1.14: BGP Long-Lived Graceful Restart
- RT-1.15: BGP Addpath on scale with and without routing policy
- RT-1.19: BGP 2-Byte and 4-Byte ASN support
- RT-1.21: BGP TCP MSS and PMTUD
- RT-1.22: BGP TCP MSS
- RT-1.23: BGP AFI SAFI OC DEFAULTS
- RT-1.24: BGP 2-Byte and 4-Byte ASN support with policy
- RT-1.25: Management network-instance default static route
- RT-1.26: Basic Static Route Support
- RT-1.27: Static route to BGP redistribution
- RT-1.28: BGP to IS-IS redistribution
- RT-1.29: BGP chained import/export policy attachment
- RT-1.30: BGP nested import/export policy attachment
- RT-1.31: BGP 3 levels of nested import/export policy with match-set-options
- RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
- RT-1.33: BGP Policy with prefix-set matching
- RT-1.34: BGP route-distance configuration
- RT-1.35: BGP Graceful Restart Extended route retention (ExRR)
- RT-1.36: AIGP feature support test
- RT-1.51: BGP multipath ECMP
- RT-1.52: BGP multipath UCMP support with Link Bandwidth Community
- RT-1.53: prefix-list test
- RT-1.54: BGP Override AS-path split-horizon
- RT-1.55: BGP session mode (active/passive)
- RT-1.63: BGP Multihop
- RT-1.64: BGP Import/Export Policy (Control plane only) Functional Test Case
- RT-1.65: BGP scale test
- RT-1.67: IPv4 and IPv6 Static Route using Vlan Interface
- RT-1.71: BGP Disable Peer AS Filter (
disable-peer-as-filter) - RT-1.73: Static Route Resilience Test
- RT-1.102: DUT eBGP FNTs coverage for new L3VPN params
- RT-1.103: DUT iBGP passive listener FNT with common router id
- RT-1.106: BGP RT Membership Constraints (RFC 4684)
- RT-1.107: BGP FIB Isolation and Peer Soft Drain
- RT-1.108: Two-Tier BGP Route Propagation and Attribute Transparency
- RT-1.109: BGP Streaming Telemetry and Operational State Verification
- RT-1.110: Single-Hop BFD over eBGP Subinterfaces
- RT-1.111: BGP Autonomous System Confederations (RFC 5065)
- RT-2.1: Base IS-IS Process and Adjacencies
- RT-2.2: IS-IS LSP Updates
- RT-2.6: IS-IS Hello-Padding enabled at interface level
- RT-2.7: IS-IS Passive is enabled at interface level
- RT-2.8: IS-IS metric style wide not enabled
- RT-2.9: IS-IS metric style wide enabled
- RT-2.10: IS-IS change LSP lifetime
- RT-2.11: IS-IS Passive is enabled at the area level
- RT-2.12: Static route to IS-IS redistribution
- RT-2.13: Weighted-ECMP for IS-IS
- RT-2.14: IS-IS Drain Test
- RT-2.15: IS-IS Extensions for Segment Routing
- RT-2.16: IS-IS Graceful Restart Helper
- RT-2.17: IS-IS scale test
- RT-2.18: IS-IS Multi-adjacencies scale test
- RT-2.19: IS-IS Suppress Interface Reachability
- RT-3.1: Policy based VRF selection
- RT-3.2: Multiple <Protocol, DSCP> Rules for VRF Selection
- RT-3.4: VRF Selection Policy Hardware Programming with Linecard and Supervisor Resiliency
- RT-3.6: VRF Selection Policy Hardware Programming Across Multiple Linecards
- RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
- RT-3.53: Static route based GUE Encapsulation to IPv6 tunnel
- RT-4.10: AFTs Route Summary
- RT-4.11: AFTs Route Summary
- RT-5.1: Singleton Interface
- RT-5.2: Aggregate Interfaces
- RT-5.3: Aggregate Balancing
- RT-5.4: Aggregate Forwarding Viable
- RT-5.5: Interface hold-time
- RT-5.6: Interface Loopback mode
- RT-5.7: Aggregate Not Viable All
- RT-5.8: IPv6 Link Local
- RT-5.9: Disable IPv6 ND Router Arvetisment
- RT-5.10: IPv6 Link Local generated by SLAAC
- RT-5.11: LACP Intervals
- RT-5.12: Suppress IPv6 ND Router Advertisement [Depreciated]
- RT-5.13: Flow control test
- RT-5.14: Aggregate Subinterface in Default and Non-default Network Instance
- RT-5.15: LACP Fallback Support
- RT-5.16: LACP Member Linecard Reboot
- RT-5.17: Physical Interface Drain via Admin Down
- RT-5.18: Aggregate Interface (LAG) Drain via Admin Down
- RT-5.19: LAG Member-Link Drain
- RT-6.1: Core LLDP TLV Population
- RT-7.1: BGP default policies
- RT-7.2: BGP Policy Community Set
- RT-7.3: BGP Policy AS Path Set
- RT-7.4: BGP Policy AS Path Set and Community Set
- RT-7.5: BGP Policy - Match and Set Link Bandwidth Community
- RT-7.6: BGP Link Bandwidth Community - Cumulative
- RT-7.8: BGP Policy Match Standard Community and Add Community Import/Export Policy
- RT-7.9: BGP ECMP for iBGP with IS-IS protocol nexthop
- RT-7.10: Routing policy statement insertion and removal
- RT-7.11: BGP Policy - Import/Export Policy Action Using Multiple Criteria
- RT-7.12: BGP Drain using Route Policy
- RT-7.51: BGP Auto-Generated Link-Bandwidth Community
- RT-8: Singleton with breakouts
- RT-10.1: Default Route Generation based on 192.0.0.0/8 Presence
- RT-10.2: Non-default Route Generation based on 192.168.2.2/32 Presence in ISIS
- RT-14.2: GRIBI Route Test
- RT-14.3: Soft Drain vs. Hard Drain Convergence Verification
- SEC-3.1: Authentication
- SFLOW-1: sFlow Configuration and Sampling
- SFLOW-2: sFlow Egress Sampling Configuration and Verification
- SR-1.1: Transit forwarding to Node-SID via ISIS
- SR-1.2: Egress Node Forwarding for MPLS traffic with Explicit Null label
- Storage-1.1: Storage File System Check
- SYS-1.1: Test default COPP policy thresholds for Arista
- SYS-2.1: Ingress control-plane ACL.
- SYS-3.1: AAA and TACACS+ Configuration Verification Test Suite
- SYS-4.1: System Mount Points State Verification
- SYS-5.1: Configuration Commit Validation after Large gNMI-Set and reboot in parallel
- SYS-6.1: SSO Extended Forwarding and Stability Validation
- System-1.1: System banner test
- System-1.2: System g protocol test
- System-1.3: System hostname test
- System-1.4: System time test
- System-1.5: System software-version test
- TE-1.1: Static ARP
- TE-1.2: My Station MAC
- TE-1.3: P4RT ACL Interaction with gRIBI Forwarding
- TE-1.4: gRIBI Recursive Route Resolution under Routing Protocol Churn
- TE-1.7: gNMI Interface Config Change Impacting gRIBI NextHop
- TE-1.21: gRIBI Tunnel Fallback to Native Routing
- TE-1.22: Traffic Blackhole on gRIBI Invalid Next-Hop (Strict FIB Precedence)
- TE-2.1: gRIBI IPv4 Entry
- TE-2.2: gRIBI IPv4 Entry With Aggregate Ports
- TE-2.3: gRIBI IPv6 Entry with Prefix Length > 64
- TE-3.1: Base Hierarchical Route Installation
- TE-3.2: Traffic Balancing According to Weights
- TE-3.3: Hierarchical weight resolution
- TE-3.5: Ordering: ACK Received
- TE-3.6: ACK in the Presence of Other Routes
- TE-3.7: Base Hierarchical NHG Update
- TE-3.8: gRIBI Tunnel Recursion over Multi-Level LPM Underlays
- TE-3.9: gRIBI AFT Operations Ordering
- TE-3.10: gRIBI WCMP Group Resizing and Weight Changes
- TE-3.31: Hierarchical weight resolution with PBF
- TE-4.1: Base Leader Election
- TE-4.2: Persistence Mode
- TE-5.1: gRIBI Get RPC
- TE-6.1: Route Removal via Flush
- TE-6.2: Route Removal In Non Default VRF
- TE-6.3: Route Leakage between Non Default VRF
- TE-6.4: gRIBI to BGP Route Redistribution for IPv4
- TE-8.1: DUT Daemon Failure
- TE-8.2: Supervisor Failure
- TE-9.1: gRIBI MPLS Compliance
- TE-9.3: FIB FAILURE DUE TO HARDWARE RESOURCE EXHAUST
- TE-10: gRIBI MPLS Forwarding
- TE-11.1: Backup NHG: Single NH
- TE-11.2: Backup NHG: Multiple NH
- TE-11.3: Backup NHG: Actions
- TE-11.4: gRIBI BACKUP_ACTIVATE Hardware Convergence & FIB ACK Verification
- TE-11.21: Backup NHG: Multiple NH with PBF
- TE-11.31: Backup NHG: Actions with PBF
- TE-13.1: gRIBI route ADD during Failover
- TE-13.2: gRIBI route DELETE during Failover
- TE-14.1: gRIBI Scaling
- TE-14.2: encap and decap scale
- TE-14.3: gRIBI Scaling - full scale setup, target T1
- TE-14.4: gRIBI Scaling - full scale setup, target T2
- TE-14.5: gRIBI Scaling - full scale setup, target T0
- TE-14.6: gRIBI Scaling - all scenarios but with minimal scaling parameters
- TE-14.7: gRIBI Scaling - full scale setup, target T3
- TE-15.1: gRIBI Compliance
- TE-16.1: basic encapsulation tests
- TE-16.2: encapsulation FRR scenarios
- TE-16.3: encapsulation FRR scenarios
- TE-17.1: VRF selection policy driven TE
- TE-18.1: gRIBI MPLS-in-UDP Encapsulation
- TE-18.3: MPLS in UDP Encapsulation Scale Test
- TE-18.4: ECMP hashing on outer and inner packets with MPLSoUDP encapsulation
- TR-6.1: Remote Syslog feature config
- TR-6.2: Local logging destinations
- TRANSCEIVER-1.1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streaming
- TRANSCEIVER-1.2: Telemetry: 400ZR_PLUS Chromatic Dispersion(CD) telemetry values streaming
- TRANSCEIVER-3.1: Telemetry: 400ZR Optics firmware version streaming
- TRANSCEIVER-3.2: Telemetry: 400ZR_PLUS Optics firmware version streaming
- TRANSCEIVER-4.1: Telemetry: 400ZR RX input and TX output power telemetry values streaming.
- TRANSCEIVER-4.2: Telemetry: 400ZR_PLUS RX input and TX output power telemetry values streaming.
- TRANSCEIVER-5.1: Configuration: 400ZR channel frequency, output TX launch power and operational mode setting.
- TRANSCEIVER-5.2: Configuration: 400ZR_PLUS channel frequency, output TX launch power and operational mode setting.
- TRANSCEIVER-6.1: Telemetry: 400ZR Optics performance metrics (pm) streaming.
- TRANSCEIVER-6.2: Telemetry: 400ZR_PLUS Optics performance metrics (pm) streaming.
- TRANSCEIVER-7.1: Telemetry: 400ZR Optics inventory info streaming
- TRANSCEIVER-7.2: Telemetry: 400ZR_PLUS Optics inventory info streaming
- TRANSCEIVER-8.1: Telemetry: 400ZR Optics module temperature streaming.
- TRANSCEIVER-8.2: Telemetry: 400ZR_PLUS Optics module temperature streaming.
- TRANSCEIVER-9.1: Telemetry: 400ZR TX laser bias current telemetry values streaming.
- TRANSCEIVER-9.2: Telemetry: 400ZR_PLUS TX laser bias current telemetry values streaming.
- TRANSCEIVER-10.1: Telemetry: 400ZR Optics FEC(Forward Error Correction) Uncorrectable Frames Streaming.
- TRANSCEIVER-10.2: Telemetry: 400ZR_PLUS Optics FEC(Forward Error Correction) Uncorrectable Frames Streaming.
- TRANSCEIVER-11.1: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.
- TRANSCEIVER-11.2: Telemetry: 400ZR_PLUS Optics logical channels provisioning and related telemetry.
- TRANSCEIVER-12.1: Telemetry: 400ZR Transceiver Supply Voltage streaming.
- TRANSCEIVER-12.2: Telemetry: 400ZR_PLUS Transceiver Supply Voltage streaming.
- TRANSCEIVER-13.1: Configuration: 400ZR Transceiver Low Power Mode Setting.
- TRANSCEIVER-13.2: Configuration: 400ZR_PLUS Transceiver Low Power Mode Setting.
- TRANSCEIVER-20.1: Client Optics DOM Telemetry, Instant, Threshold, and Miscellaneous Static Info
- TRANSCEIVER-101: Telemetry: ZR platform OC paths streaming.
- TRANSCEIVER-102: Telemetry: ZR terminal-device OC paths streaming.
- TRANSCEIVER-103: Telemetry: ZR Plus platform OC paths streaming.
- TRANSCEIVER-104: Telemetry: ZR Plus terminal-device OC paths streaming.
- TRANSCEIVER-105: Telemetry: ZR platform OC paths streaming.
- TRANSCEIVER-106: Telemetry: ZR terminal-device OC paths streaming.
- TRANSCEIVER-107: Telemetry: ZR Plus platform OC paths streaming.
- TRANSCEIVER-108: Telemetry: ZR Plus terminal-device OC paths streaming.
- TRANSCEIVER-109: 400ZR / 800ZR Operational Mode Transition and Inventory Persistence
- TUN-1.3: Interface based IPv4 GRE Encapsulation
- TUN-1.4: Interface based IPv6 GRE Encapsulation
- TUN-1.6: Tunnel End Point Resize for Ecapsulation - Interface Based GRE Tunnel
- TUN-1.9: GRE inner packet DSCP
- URPF-1.1: uRPF validation from non-default network-instance
- Test Plans