-
Notifications
You must be signed in to change notification settings - Fork 240
macsec_test
Github Action edited this page Jul 24, 2026
·
1 revision
Validate MACsec functionality (including encapsulation and decapsulation of MPLS over GRE and MPLS over UDP) and line-rate performance on 10G, 100G, and 400G interfaces. The test ensures that MACsec encryption/decryption, encapsulation, and decapsulation processes do not introduce packet loss, excessive latency, or throughput degradation.
All test cases are verified using both IPv4 and IPv6 traffic. Egress encapsulation and ingress decapsulation types are mapped to interface speeds:
- MPLS over GRE is used for traffic over 10G and 100G links.
- MPLS over UDP is used for traffic over 400G links.
-
topologies/atedutdutate.testbed(2-DUT, 1-ATE setup with 10G, 100G, and 400G links)
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ │ │ │ │ │ │ │
│ │ 10G │ │ 10G │ │ 10G │ │
│ 1├──────────│1 2├───────────┤2 1├───────────┤2 │
│ │ │ │ MACsec │ │ │ │
│ │ 100G │ │ 100G │ │ 100G │ │
│ 3├──────────│3 4├───────────┤4 3├───────────┤4 │
│ ATE │ │ DUT1 │ │ DUT2 │ │ ATE │
│ │ 400G │ │ 400G │ │ 400G │ │
│ 5├──────────│5 6├───────────┤6 5├───────────┤6 │
│ │ │ │ │ │ │ │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
- Connect the ATE to DUT1 and DUT2, respectively, using 1x10G, 1x100G, and 1x400G interfaces.
- Connect DUT1 and DUT2 using 1x10G, 1x100G, and 1x400G interfaces.
- Enable L3 routing (IPv4 and IPv6) on all interfaces in default VRF.
- MACsec will be enabled on the links between DUT1 and DUT2.
- Traffic flows are validated on:
-
10G path:
ATE:port1 <-> DUT1 <-> DUT2 <-> ATE:port2(using MPLSoGRE encapsulation/decapsulation) -
100G path:
ATE:port3 <-> DUT1 <-> DUT2 <-> ATE:port4(using MPLSoGRE encapsulation/decapsulation) -
400G path:
ATE:port5 <-> DUT1 <-> DUT2 <-> ATE:port6(using MPLSoUDP encapsulation/decapsulation)
-
10G path:
- Configure MACsec Static Connectivity Association Key (CAK) Mode on both ends
of the physical links connecting DUT1 and DUT2:
- Define the Policy to cover must-secure scenario.
- Use 256-bit cipher GCM-AES-256-XPN.
- Set Key server priority: 15.
- Set Replay Protection Window size: 64.
- Include ICV indicator: True.
- Include SCI: True.
- Configure keychain with pre-shared keys.
- Configure Policy Forwarding on DUT2 ingress interface from DUT1 (for
encapsulation test cases):
- Match incoming traffic (IPv4 and IPv6).
- Redirect matched traffic to Next Hop Group.
-
For 10G and 100G Paths (MPLSoGRE): Next Hop Group
MPLS_in_GRE_Encappushes MPLS label (e.g., 99998) and encapsulates in GRE (tunnel destination10.99.1.1, source10.235.143.208). -
For 400G Path (MPLSoUDP): Next Hop Group
MPLS_in_UDP_Encappushes MPLS label and encapsulates in UDP (destination port 6635, tunnel destination10.99.1.1, source10.235.143.208).
- Configure Policy Forwarding and MPLS on DUT2 ingress interface from ATE (for
decapsulation test cases):
-
For 10G and 100G Paths (MPLSoGRE): Match incoming GRE traffic
(protocol 47) destined to DUT2. Apply action
decapsulate-gre. -
For 400G Path (MPLSoUDP): Match incoming UDP traffic (dest
port 6635) destined to DUT2. Apply action
decapsulate-gue(or equivalent UDP decap). - Configure Static LSP on DUT2 to match the inner MPLS label (e.g., 99998) and perform a POP action.
- Route the decapsulated and popped IP traffic towards DUT1 via the MACsec-secured link.
-
For 10G and 100G Paths (MPLSoGRE): Match incoming GRE traffic
(protocol 47) destined to DUT2. Apply action
- Traffic Type: Tested with both IPv4 and IPv6 traffic.
-
Path: 10G path (
ATE:port1 -> DUT1 -> DUT2 -> ATE:port2) and 100G path (ATE:port3 -> DUT1 -> DUT2 -> ATE:port4). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting 10G and 100G links.
- Step 2 - Configure Policy Forwarding on DUT2 to encapsulate traffic in MPLSoGRE.
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate IPv4 and IPv6 IMIX traffic from ATE (port1/port3) destined to a remote IP (routed via DUT1 -> DUT2) at the Maximum Non-Drop Rate (NDR). To prevent packet drops due to MACsec overhead on the transit links, limit the offered rate to ~92.1% of physical line rate (~8.72 Gbps for 10G ATE Port 1, ~87.2 Gbps for 100G ATE Port 3, for a standard 354B average packet size IMIX).
- Step 5 - Verify that traffic is received at ATE (port2/port4) encapsulated in MPLSoGRE with no packet loss.
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: Triple-run on 10G path (
ATE:port1 -> DUT1 -> DUT2 -> ATE:port2), 100G path (ATE:port3 -> DUT1 -> DUT2 -> ATE:port4), and 400G path (ATE:port5 -> DUT1 -> DUT2 -> ATE:port6). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
security-policyset toMUST_SECURE. - Step 2 - Configure Policy Forwarding on DUT2 to encapsulate traffic (GRE for 10G/100G, UDP for 400G).
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate IPv4 and IPv6 IMIX traffic (using a standard 354B
average packet size IMIX) from ATE (port1/port3/port5) at the Maximum
Non-Drop Rate (NDR) to prevent queue drops:
- For the 10G run: Offer rate at ATE Port 1 limited to ~92.1% (~8.72 Gbps).
- For the 100G run: Offer rate at ATE Port 3 limited to ~92.1% (~87.2 Gbps).
- For the 400G run: Offer rate at ATE Port 5 limited to ~91.2% (~345.3 Gbps).
- Step 5 - Verify that traffic is received at ATE (port2/port4/port6) with no packet loss.
- Step 6 - Simulating MACsec failure: Modify the pre-shared key (CAK/CKN) configuration on DUT2 to introduce a mismatch, bringing the MKA session down.
- Step 7 - Verify that the MACsec session status on both DUTs transitions to DOWN.
- Step 8 - Resume traffic generation from ATE.
- Step 9 - Verify that all traffic is dropped on the DUT1-DUT2 link
(0% received rate at ATE) due to the
MUST_SECUREpolicy. - Step 10 - Restore the correct MACsec keys on DUT2. Verify that the MKA session recovers to UP and traffic forwarding resumes with zero packet loss.
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: Triple-run on 10G path (
ATE:port1 -> DUT1 -> DUT2 -> ATE:port2), 100G path (ATE:port3 -> DUT1 -> DUT2 -> ATE:port4), and 400G path (ATE:port5 -> DUT1 -> DUT2 -> ATE:port6). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
security-policyset toSHOULD_SECURE. - Step 2 - Configure Policy Forwarding on DUT2 to encapsulate traffic (GRE for 10G/100G, UDP for 400G).
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate IPv4 and IPv6 IMIX traffic (using a standard 354B
average packet size IMIX) from ATE (port1/port3/port5) at the Maximum
Non-Drop Rate (NDR) to prevent queue drops:
- For the 10G run: Offer rate at ATE Port 1 limited to ~92.1% (~8.72 Gbps).
- For the 100G run: Offer rate at ATE Port 3 limited to ~92.1% (~87.2 Gbps).
- For the 400G run: Offer rate at ATE Port 5 limited to ~91.2% (~345.3 Gbps).
- Step 5 - Verify that traffic is received at ATE (port2/port4/port6) with no packet loss.
- Step 6 - Verify via telemetry/CLI that all packets are transmitted and received as encrypted (MACsec-protected).
- Step 7 - Simulating MACsec failure: Modify the pre-shared key (CAK/CKN) configuration on DUT2 to introduce a mismatch, bringing the MKA session down.
- Step 8 - Verify that the MACsec session status on both DUTs transitions to DOWN.
- Step 9 - Resume traffic generation from ATE.
- Step 10 - Verify that traffic is still forwarded and received at ATE
with no packet loss, but is transmitted unencrypted (cleartext) over
the DUT1-DUT2 link. Verify that untagged packet counters
(
tx-untagged-pktsandrx-untagged-pkts) are incrementing. - Step 11 - Restore the correct MACsec keys on DUT2. Verify that the MKA session recovers to UP and traffic is again transmitted encrypted.
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: Triple-run on 10G path (
ATE:port1 -> DUT1 -> DUT2 -> ATE:port2), 100G path (ATE:port3 -> DUT1 -> DUT2 -> ATE:port4), and 400G path (ATE:port5 -> DUT1 -> DUT2 -> ATE:port6). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
security-policyset toMUST_SECUREandsak-rekey-intervalset to 28800 seconds. - Step 2 - Configure Policy Forwarding on DUT2 to encapsulate traffic (GRE for 10G/100G, UDP for 400G).
- Step 3 - Verify the SAK key value is accepted by the DUT (via CLI/telemetry).
- Step 4 - Verify that MACsec sessions are UP.
- Step 5 - Generate IPv4 and IPv6 IMIX traffic (using a standard 354B
average packet size IMIX) from ATE (port1/port3/port5) at the Maximum
Non-Drop Rate (NDR) to prevent queue drops:
- For the 10G run: Offer rate at ATE Port 1 limited to ~92.1% (~8.72 Gbps).
- For the 100G run: Offer rate at ATE Port 3 limited to ~92.1% (~87.2 Gbps).
- For the 400G run: Offer rate at ATE Port 5 limited to ~91.2% (~345.3 Gbps).
- Step 6 - Verify that traffic is received at ATE (port2/port4/port6) with no packet loss.
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links
(10G, 100G, and 400G) with
- Traffic Type: Tested with both IPv4 and IPv6 traffic.
-
Path: 400G path (
ATE:port5 -> DUT1 -> DUT2 -> ATE:port6). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting 400G link.
- Step 2 - Configure Policy Forwarding on DUT2 to encapsulate traffic in MPLSoUDP.
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate IPv4 and IPv6 IMIX traffic from ATE (port5) destined to a remote IP (routed via DUT1 -> DUT2) at the Maximum Non-Drop Rate (NDR). To prevent packet drops due to MPLSoUDP encapsulation overhead on the 400G egress link, limit the offered rate at ATE Port 5 to ~91.2% of physical line rate (~345.3 Gbps for a standard 354B average packet size IMIX).
- Step 5 - Verify that traffic is received at ATE (port6) encapsulated in MPLSoUDP with no packet loss.
- Traffic Type: Tested with both IPv4 and IPv6 traffic.
- Forwarding Mode: DUT2 uses encapsulation (MPLSoGRE for 10G and 100G, MPLSoUDP for 400G) to forward traffic towards ATE ports 2, 4, and 6.
-
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links (10G, 100G, and 400G).
- Step 2 - Configure encapsulation on DUT2 (MPLSoGRE for 10G and 100G egress, MPLSoUDP for 400G egress).
- Step 3 - Generate IPv4 and IPv6 traffic with fixed 64-byte frames from
the ATE at the Maximum Non-Drop Rate (NDR). Due to bandwidth expansion
from MACsec and encapsulation overhead, the offered rate at the ATE
ingress must be limited to prevent egress queue drops:
- Test run A: Over 10G path (using MPLSoGRE egress encap). Limit offered rate at ATE Port 1 to ~72.4% of physical line rate (~10.77 Mpps) to account for MACsec overhead on the transit link.
- Test run B: Over 100G path (using MPLSoGRE egress encap). Limit offered rate at ATE Port 3 to ~72.4% of physical line rate (~107.7 Mpps) to account for MACsec overhead on the transit link.
- Test run C: Over 400G path (using MPLSoUDP egress encap). Limit offered rate at ATE Port 5 to ~70.0% of physical line rate (~416.6 Mpps) to account for MPLSoUDP overhead on the egress link.
- Step 4 - Verify that no packet loss occurs over a 10-minute duration for each run.
- Step 5 - Validate that throughput matches the expected line rate for 64B frames (accounting for MACsec and respective encapsulation overhead).
- Traffic Type: Tested with both IPv4 and IPv6 traffic.
- Forwarding Mode: DUT2 uses encapsulation (MPLSoGRE for 10G and 100G, MPLSoUDP for 400G) to forward traffic towards ATE ports 2, 4, and 6.
-
Procedure:
- Step 1 - Maintain the MACsec and encapsulation configuration from PF-1.27.6.
- Step 2 - Generate IPv4 and IPv6 traffic using an IMIX profile (e.g., a
mix of 64B, 570B, and 1518B) at the Maximum Non-Drop Rate (NDR). Due to
overhead, the offered rate at the ATE ingress must be limited:
- Test run A: Over 10G path (using MPLSoGRE egress encap). Limit offered rate to ~92.1% of physical line rate (~8.72 Gbps for a standard 354B average packet size IMIX) to account for MACsec transit link overhead.
- Test run B: Over 100G path (using MPLSoGRE egress encap). Limit offered rate to ~92.1% of physical line rate (~87.2 Gbps for a standard 354B average packet size IMIX) to account for MACsec transit link overhead.
- Test run C: Over 400G path (using MPLSoUDP egress encap). Limit offered rate to ~91.2% of physical line rate (~345.3 Gbps for a standard 354B average packet size IMIX) to account for MPLSoUDP egress link overhead.
- Step 3 - Verify zero packet loss and consistent throughput for each run.
- Traffic Type: Tested with both IPv4 and IPv6 traffic.
- Forwarding Mode: DUT2 uses encapsulation (MPLSoGRE for 10G and 100G, MPLSoUDP for 400G) to forward traffic towards ATE ports 2, 4, and 6.
-
Procedure:
- Step 1 - Configure the DUT1<->DUT2 interfaces and DUT2 egress interfaces to support a MTU of 9216 bytes.
- Step 2 - Generate IPv4 and IPv6 traffic with 9000-byte Jumbo frames at
the Maximum Non-Drop Rate (NDR). Due to the very large packet size, the
relative impact of the overhead is very small (<0.4%):
- Test run A: Over 10G path (using MPLSoGRE egress encap). Limit offered rate to ~99.6% of physical line rate (~9.94 Gbps) to account for MACsec transit link overhead.
- Test run B: Over 100G path (using MPLSoGRE egress encap). Limit offered rate to ~99.6% of physical line rate (~99.4 Gbps) to account for MACsec transit link overhead.
- Test run C: Over 400G path (using MPLSoUDP egress encap). Limit offered rate to ~99.6% of physical line rate (~398.4 Gbps) to account for MPLSoUDP egress link overhead.
- Step 3 - Verify that the hardware correctly handles large encrypted and encapsulated payloads without fragmentation or loss for each run.
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: 10G path (
ATE:port2 -> DUT2 -> DUT1 -> ATE:port1) and 100G path (ATE:port4 -> DUT2 -> DUT1 -> ATE:port3). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting 10G and 100G links.
- Step 2 - Configure GRE decapsulation policy and static LSP with POP action on DUT2.
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate MPLSoGRE encapsulated traffic from ATE (port2/port4) destined to DUT2 decap IP (with inner payload destined to ATE (port1/port3) via DUT1) at the Maximum Non-Drop Rate (NDR). To prevent packet drops due to MACsec overhead on the transit link (which is larger than GRE overhead), limit the offered rate to ~99.0% of physical line rate (~9.41 Gbps for 10G ATE Port 2, ~94.1 Gbps for 100G ATE Port 4, for a standard 354B average inner packet size IMIX).
- Step 5 - Verify that decapsulated and decrypted traffic is received at ATE (port1/port3) with no packet loss.
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: 400G path (
ATE:port6 -> DUT2 -> DUT1 -> ATE:port5). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting 400G link.
- Step 2 - Configure UDP decapsulation policy and static LSP with POP action on DUT2.
- Step 3 - Verify MACsec session is established and secured.
- Step 4 - Generate MPLSoUDP encapsulated traffic from ATE (port6) destined to DUT2 decap IP (with inner payload destined to ATE (port5) via DUT1). Since the UDP encapsulation overhead at ingress is larger than the downstream MACsec overhead, the packets shrink as they traverse the path. Thus, traffic can be sent at 100% of the physical line rate of the encapsulated traffic (~380.5 Gbps L2 throughput for a standard 354B average inner packet size IMIX) without causing egress queue congestion or packet loss.
- Step 5 - Verify that decapsulated and decrypted traffic is received at ATE (port5) with no packet loss.
- Traffic Type: Tested with both IPv4 and IPv6 IMIX traffic.
-
Path: Triple-run on 10G path (
ATE:port1 -> DUT1 -> DUT2 -> ATE:port2), 100G path (ATE:port3 -> DUT1 -> DUT2 -> ATE:port4), and 400G path (ATE:port5 -> DUT1 -> DUT2 -> ATE:port6). -
Procedure:
- Step 1 - Configure MACsec on DUT1 and DUT2 on the interconnecting links (10G, 100G, and 400G).
- Step 2 - Configure a MACsec keychain on DUT1 and DUT2 with 5 unique keys (Key ID 01 through 05), each with a distinct, staggered activation time (e.g., staggered by 10 minutes).
- Step 3 - Apply the keychain to the MACsec profile on the 10G, 100G, and 400G links using cipher GCM-AES-256-XPN.
- Step 4 - Generate IPv4 and IPv6 IMIX traffic (using a standard 354B
average packet size IMIX) from ATE (port1/port3/port5) through DUT1 and
DUT2 towards ATE (port2/port4/port6) at the Maximum Non-Drop Rate (NDR)
to prevent queue drops:
- For the 10G run: Limit the offered rate at ATE Port 1 to ~92.1% of physical line rate (~8.72 Gbps) to account for MACsec transit link overhead.
- For the 100G run: Limit the offered rate at ATE Port 3 to ~92.1% of physical line rate (~87.2 Gbps) to account for MACsec transit link overhead.
- For the 400G run: Limit the offered rate at ATE Port 5 to ~91.2% of physical line rate (~345.3 Gbps) to account for MPLSoUDP egress link overhead.
- Step 5 - Monitor ATE receivers for sequence errors or packet loss during the key transition windows.
- Step 6 - Manually trigger a key rollover by updating the MKA primary-key or allow the activation timers to expire.
- Step 7 - Verify the active key transition using CLI (
show macsec mka session interface <interface> detail) and gNMI telemetry (/macsec/mka/interfaces/interface/state/active-key-id).
-
Expected Result:
- The platform must rotate through all 5 keys in the keychain hitlessly.
- Traffic must remain at line-rate with zero packet loss (0% drop) during every key transition.
- The MACsec session must remain stable across the transitions.
{
"openconfig-interfaces:interfaces": {
"interface": [
{
"name": "Ethernet1/1",
"config": {
"name": "Ethernet1/1"
}
}
]
},
"openconfig-keychain:keychains": {
"keychain": [
{
"name": "macsec_keychain",
"config": {
"name": "macsec_keychain"
},
"keys": {
"key": [
{
"key-id": "0xabcd111122223333444455556666777788889999000011112222333344445555",
"config": {
"key-id": "0xabcd111122223333444455556666777788889999000011112222333344445555",
"secret-key": "ad4rf10kn85fc0adk5dfcsnr1or4cm08q",
"crypto-algorithm": "AES_256_CMAC"
}
}
]
}
}
]
},
"openconfig-macsec:macsec": {
"interfaces": {
"interface": [
{
"name": "Ethernet1/1",
"config": {
"name": "Ethernet1/1",
"enable": true,
"replay-protection": 64
},
"mka": {
"config": {
"key-chain": "macsec_keychain",
"mka-policy": "must_secure_policy"
}
}
}
]
},
"mka": {
"policies": {
"policy": [
{
"name": "must_secure_policy",
"config": {
"name": "must_secure_policy",
"key-server-priority": 15,
"macsec-cipher-suite": [
"GCM_AES_XPN_256"
],
"confidentiality-offset": "0_BYTES",
"include-icv-indicator": true,
"include-sci": true,
"sak-rekey-interval": 30
}
},
{
"name": "should_secure_policy",
"config": {
"name": "should_secure_policy",
"key-server-priority": 15,
"macsec-cipher-suite": [
"GCM_AES_XPN_256"
],
"confidentiality-offset": "0_BYTES",
"include-icv-indicator": true,
"include-sci": true,
"sak-rekey-interval": 30
}
}
]
}
}
},
"openconfig-network-instance:network-instances": {
"network-instance": [
{
"name": "default",
"config": {
"name": "default",
"type": "openconfig-network-instance-types:DEFAULT_INSTANCE"
},
"mpls": {
"lsps": {
"static-lsps": {
"static-lsp": [
{
"name": "static-lsp-pop",
"config": {
"name": "static-lsp-pop"
},
"egress": {
"config": {
"incoming-label": 99998,
"next-hop": "192.0.2.1"
}
}
}
]
}
}
},
"static": {
"next-hop-groups": {
"next-hop-group": [
{
"name": "MPLS_in_GRE_Encap",
"config": {
"name": "MPLS_in_GRE_Encap"
},
"next-hops": {
"next-hop": [
{
"index": "1",
"config": {
"index": "1"
}
}
]
}
},
{
"name": "MPLS_in_UDP_Encap",
"config": {
"name": "MPLS_in_UDP_Encap"
},
"next-hops": {
"next-hop": [
{
"index": "2",
"config": {
"index": "2"
}
}
]
}
}
]
},
"next-hops": {
"next-hop": [
{
"index": "1",
"config": {
"index": "1",
"next-hop": "192.0.2.1"
}
},
{
"index": "2",
"config": {
"index": "2",
"next-hop": "192.0.2.1"
}
}
]
}
},
"policy-forwarding": {
"interfaces": {
"interface": [
{
"interface-id": "Ethernet1/1.20",
"config": {
"interface-id": "Ethernet1/1.20",
"apply-forwarding-policy": "customer1"
}
}
]
},
"policies": {
"policy": [
{
"policy-id": "customer1",
"config": {
"policy-id": "customer1",
"type": "PBR_POLICY"
},
"rules": {
"rule": [
{
"sequence-id": 1,
"config": {
"sequence-id": 1
},
"ipv4": {
"config": {
"protocol": 47
}
},
"action": {
"config": {
"next-hop-group": "MPLS_in_GRE_Encap"
}
}
}
]
}
},
{
"policy-id": "decap-policy",
"config": {
"policy-id": "decap-policy",
"type": "PBR_POLICY"
},
"rules": {
"rule": [
{
"sequence-id": 10,
"config": {
"sequence-id": 10
},
"ipv4": {
"config": {
"protocol": 47
}
},
"action": {
"config": {
"decapsulate-gre": true
}
}
},
{
"sequence-id": 20,
"config": {
"sequence-id": 20
},
"ipv4": {
"config": {
"protocol": 17
}
},
"action": {
"config": {
"decapsulate-gue": true
}
}
}
]
}
}
]
},
"path-selection-groups": {
"path-selection-group": [
{
"group-id": "MPLS_in_GRE_Encap",
"config": {
"group-id": "MPLS_in_GRE_Encap"
}
},
{
"group-id": "MPLS_in_UDP_Encap",
"config": {
"group-id": "MPLS_in_UDP_Encap"
}
}
]
}
}
}
]
}
}paths:
# Config paths:
/macsec/interfaces/interface/config/enable:
/macsec/interfaces/interface/config/replay-protection:
/macsec/mka/policies/policy/config/name:
/macsec/mka/policies/policy/config/macsec-cipher-suite:
/macsec/mka/policies/policy/config/confidentiality-offset:
/macsec/mka/policies/policy/config/key-server-priority:
/macsec/mka/policies/policy/config/sak-rekey-interval:
/keychains/keychain/keys/key/config/secret-key:
/keychains/keychain/keys/key/config/crypto-algorithm:
/interfaces/interface/config/description:
/interfaces/interface/config/enabled:
/interfaces/interface/config/name:
/interfaces/interface/hold-time/config/up:
/interfaces/interface/hold-time/config/down:
/interfaces/interface/subinterfaces/subinterface/config/index:
/interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address/config/ip:
/interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address/config/prefix-length:
/interfaces/interface/subinterfaces/subinterface/ipv6/addresses/address/config/ip:
/interfaces/interface/subinterfaces/subinterface/ipv6/addresses/address/config/prefix-length:
/interfaces/interface/subinterfaces/subinterface/vlan/config/vlan-id:
/lacp/interfaces/interface/config/name:
/lacp/interfaces/interface/config/lacp-mode:
/network-instances/network-instance/config/name:
/network-instances/network-instance/config/type:
/network-instances/network-instance/protocols/protocol/static-routes/static/config/prefix:
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/index:
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop:
/network-instances/network-instance/policy-forwarding/policies/policy/config/policy-id:
/network-instances/network-instance/policy-forwarding/interfaces/interface/config/interface-id:
/network-instances/network-instance/policy-forwarding/interfaces/interface/config/apply-forwarding-policy:
/network-instances/network-instance/static/next-hops/next-hop/encap-headers/encap-header/udp-v4/config/dst-udp-port:
/network-instances/network-instance/policy-forwarding/policies/policy/config/type:
/network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/action/config/decapsulate-gre:
/network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/action/config/decapsulate-gue:
/network-instances/network-instance/mpls/lsps/static-lsps/static-lsp/config/name:
/network-instances/network-instance/mpls/lsps/static-lsps/static-lsp/egress/config/incoming-label:
/network-instances/network-instance/mpls/lsps/static-lsps/static-lsp/egress/config/next-hop:
/network-instances/network-instance/static/next-hop-groups/next-hop-group/config/name:
/network-instances/network-instance/static/next-hops/next-hop/config/index:
/network-instances/network-instance/static/next-hops/next-hop/config/next-hop:
# State paths:
/macsec/interfaces/interface/state/counters/rx-badtag-pkts:
/macsec/interfaces/interface/state/counters/rx-late-pkts:
/macsec/interfaces/interface/state/counters/rx-nosci-pkts:
/macsec/interfaces/interface/state/counters/rx-unknownsci-pkts:
/macsec/interfaces/interface/state/counters/rx-untagged-pkts:
/macsec/interfaces/interface/state/counters/tx-untagged-pkts:
/macsec/interfaces/interface/mka/state/counters/in-cak-mkpdu:
/macsec/interfaces/interface/mka/state/counters/in-mkpdu:
/macsec/interfaces/interface/mka/state/counters/in-sak-mkpdu:
/macsec/interfaces/interface/mka/state/counters/out-cak-mkpdu:
/macsec/interfaces/interface/mka/state/counters/out-mkpdu:
/macsec/interfaces/interface/mka/state/counters/out-sak-mkpdu:
/macsec/mka/state/counters/in-mkpdu-bad-peer-errors:
/macsec/mka/state/counters/in-mkpdu-icv-verification-errors:
/macsec/mka/state/counters/in-mkpdu-peer-list-errors:
/macsec/mka/state/counters/in-mkpdu-validation-errors:
/macsec/mka/state/counters/out-mkpdu-errors:
/macsec/mka/state/counters/sak-cipher-mismatch-errors:
/macsec/mka/state/counters/sak-decryption-errors:
/macsec/mka/state/counters/sak-encryption-errors:
/macsec/mka/state/counters/sak-generation-errors:
/macsec/mka/state/counters/sak-hash-errors:
rpcs:
gnmi:
gNMI.Get:
gNMI.Set:
union_replace: true
gNMI.Subscribe:
on_change: true
sampled: true- FFF - Fixed Form Factor
- MFF - Modular Form Factor
-
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: General Authz (1-4) tests
- BMP-1.1: BMP Session Establishment and Telemetry Test
- BMP-2.7: BMP Pre Policy Test
- BMP-2.8: BMP Post Policy Test
- bootz: 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-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: Dataplane Hashing with Physical/Software 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.
- MGT-1: Management HA solution test
- 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.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: 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
- Replay-1.0: Record/replay presession test
- Replay-1.1: Record/replay diff command trees test
- Replay-1.2: P4RT Replay Test
- 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.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-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-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.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-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.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
- SEC-3.1: Authentication
- SFLOW-1: sFlow Configuration and Sampling
- 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-2.1: gRIBI IPv4 Entry
- TE-2.2: gRIBI IPv4 Entry With Aggregate Ports
- 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.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.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-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.
- 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