Repository navigation
zr_800_operational_mode_inventory_recovery_test
This test validates that coherent 400G ZR and ZR+ (SPEED_400GB,
PMD_400GBASE_ZR, PMD_400GBASE_ZR_PLUS) and 800G ZR and ZR+ (SPEED_800GB,
PMD_800GBASE_ZR, PMD_800GBASE_ZR_PLUS, e.g., OSFP-800G-ZR,
OSFP-800G-ZR-M, OSFP-800G-ZR-M-HP) optical transceivers across
multiple line cards properly initialize, transition from a default optical
application selection (Appsel) mode to a custom operational-mode with a
transceiver state bounce, and retain complete hardware inventory telemetry
across repeated gNMI.Set interface deletion and re-creation cycles.
Additionally, the test verifies event-driven gNMI.Subscribe state
convergence, negative fault and recovery handling (unsupported
operational-mode, optical frequency/mode mismatch, and administrative laser
shutoff), and zero-loss bidirectional dual-stack IPv4 and IPv6 traffic
forwarding across scaled static route prefixes.
+------------+ 400ZR / 800ZR Link 1 (FPC A) +------------+
| | (Port 1: 192.0.2.2/30, 2001:db8::2/126) | |
| | <========================================> | |
| | (Port 1: 192.0.2.1/30, 2001:db8::1/126) | |
| ATE | | DUT |
| | 400ZR / 800ZR Link 2 (FPC B) | |
| | (Port 2: 192.0.2.6/30, 2001:db8::6/126) | |
| | <========================================> | |
| | (Port 2: 192.0.2.5/30, 2001:db8::5/126) | |
+------------+ +------------+
-
Topology & Multi-Line-Card Placement: Connect two coherent 400ZR/400ZR+
(
SPEED_400GB) or 800ZR/800ZR+ (SPEED_800GB) interfaces between the DUT and ATE (or connect two coherent ZR/ZR+ interfaces on the DUT via a duplex LC fiber jumper with less than 2-3 dB insertion loss while anchoring ingress/egress L3 traffic on ATE ports). On modular chassis systems, DUT port 1 and DUT port 2 should reside on distinct line cards (FPCs) so multi-FPC transceiver initialization and inventory database synchronization are exercised simultaneously:-
Link 1 (DUT Port 1 <-> ATE Port 1):
- DUT Interface Name:
Ethernet4/1/1(Subinterface index0) - DUT Hardware Port Component:
Ethernet4/1-Port - DUT Transceiver Component:
Ethernet4/1 - DUT Optical-Channel Component:
Ethernet4/1-Optical0 - DUT Coherent OTN Logical Channel Index:
8000(PROT_OTN, or4000on 400ZR/400ZR+ platforms) - DUT Ethernet Logical Channel Index:
80000(PROT_ETHERNET, or40000on 400ZR/400ZR+ platforms) - Port Speed / Tributary Rate / Tributary Protocol:
- For 400ZR/400ZR+ (
PMD_400GBASE_ZR/PMD_400GBASE_ZR_PLUS):SPEED_400GB,TRIB_RATE_400G,PROT_400GE,num-physical-channels:4,allocation:"400" - For 800ZR/800ZR+ (
PMD_800GBASE_ZR/PMD_800GBASE_ZR_PLUS):SPEED_800GB,TRIB_RATE_800G,PROT_800GE,num-physical-channels:8,allocation:"800"
- For 400ZR/400ZR+ (
- Optical Center Frequency:
196100000MHz (196.1THz) - Optical Target Output Power:
-7dBm ("-7") - Default Operational Mode (
Appsel):1 - Custom Operational Mode (
Appsel):2(or the platform-specific custom 400ZR/800ZR operational mode supplied via test flag/deviation)
- DUT Interface Name:
-
Link 2 (DUT Port 2 <-> ATE Port 2):
- DUT Interface Name:
Ethernet5/1/1(Subinterface index0) - DUT Hardware Port Component:
Ethernet5/1-Port - DUT Transceiver Component:
Ethernet5/1 - DUT Optical-Channel Component:
Ethernet5/1-Optical0 - DUT Coherent OTN Logical Channel Index:
8001(PROT_OTN, or4001on 400ZR/400ZR+ platforms) - DUT Ethernet Logical Channel Index:
80001(PROT_ETHERNET, or40001on 400ZR/400ZR+ platforms) - Port Speed / Tributary Rate / Tributary Protocol: Matching Link 1
(
SPEED_400GB/TRIB_RATE_400G/PROT_400GEfor 400ZR/400ZR+, orSPEED_800GB/TRIB_RATE_800G/PROT_800GEfor 800ZR/800ZR+) - Optical Center Frequency:
196100000MHz (196.1THz) - Optical Target Output Power:
-7dBm ("-7") - Default Operational Mode (
Appsel):1 - Custom Operational Mode (
Appsel):2(matching Link 1)
- DUT Interface Name:
-
Link 1 (DUT Port 1 <-> ATE Port 1):
-
Explicit L3 Addressing and Scaled Static Routing Plan:
-
DUT port 1 connected to ATE port 1 (
Ethernet4/1/1.0):- IPv4 address:
192.0.2.1/30 - IPv6 address:
2001:db8::1/126
- IPv4 address:
-
ATE port 1:
- IPv4 address:
192.0.2.2/30(Default Gateway:192.0.2.1) - IPv6 address:
2001:db8::2/126(Default Gateway:2001:db8::1)
- IPv4 address:
-
DUT port 2 connected to ATE port 2 (
Ethernet5/1/1.0):- IPv4 address:
192.0.2.5/30 - IPv6 address:
2001:db8::5/126
- IPv4 address:
-
ATE port 2:
- IPv4 address:
192.0.2.6/30(Default Gateway:192.0.2.5) - IPv6 address:
2001:db8::6/126(Default Gateway:2001:db8::5)
- IPv4 address:
-
Scaled Static Routes on DUT (
DEFAULTnetwork-instance):-
Forward Direction (Egressing
Ethernet5/1/1toward ATE Port 2):- 16 IPv4
/24prefixes:198.51.100.0/24through198.51.115.0/24(where198.51.100.0/24is the primary canonical prefix), each configured with next-hop index"0"and next-hop IP192.0.2.6. - 16 IPv6
/64prefixes:2001:db8:2::/64(primary canonical prefix) and2001:db8:2:1::/64through2001:db8:2:f::/64, each configured with next-hop index"0"and next-hop IP2001:db8::6.
- 16 IPv4
-
Reverse Direction (Egressing
Ethernet4/1/1toward ATE Port 1):- 16 IPv4
/24prefixes:203.0.113.0/24through203.0.128.0/24, each configured with next-hop index"0"and next-hop IP192.0.2.2. - 16 IPv6
/64prefixes:2001:db8:1::/64and2001:db8:1:1::/64through2001:db8:1:f::/64, each configured with next-hop index"0"and next-hop IP2001:db8::2.
- 16 IPv4
-
Forward Direction (Egressing
-
DUT port 1 connected to ATE port 1 (
TRANSCEIVER-109.1: Validate 400ZR / 800ZR operational-mode transition with transceiver bounce and bidirectional dual-stack traffic
Some coherent 400G ZR/ZR+ (SPEED_400GB) and 800G ZR/ZR+ (SPEED_800GB)
optical pluggables can experience transient module faults during initial boot
when the default application selection (Appsel) mode is applied, and
subsequently fail to lock when reconfigured to a custom operational-mode
unless the transceiver state is bounced. This subtest verifies that
transitioning from the default operational-mode (1) to a custom
operational-mode (2) accompanied by a deterministic transceiver state bounce
cleanly initializes the optical channel on both line cards/ports, preserves all
hardware inventory telemetry, brings the 400ZR or 800ZR interfaces UP, and
forwards bidirectional IPv4 and IPv6 traffic with zero packet loss and zero
uncorrectable FEC errors.
-
Step 1 - Initial Default Operational Mode Provisioning (Both Ports):
- Using a batched
gNMI.Setrequest, enable the physical transceivers on bothEthernet4/1andEthernet5/1:-
/components/component[name=Ethernet4/1]/transceiver/config/enabled:true -
/components/component[name=Ethernet5/1]/transceiver/config/enabled:true
-
- Configure 400G or 800G breakout parameters matching the port PMD on
hardware ports
Ethernet4/1-PortandEthernet5/1-Port:-
/components/component/port/breakout-mode/groups/group/config/index:1 -
/components/component/port/breakout-mode/groups/group/config/breakout-speed:SPEED_800GB(for 800ZR/800ZR+) orSPEED_400GB(for 400ZR/400ZR+) -
/components/component/port/breakout-mode/groups/group/config/num-breakouts:1 -
/components/component/port/breakout-mode/groups/group/config/num-physical-channels:8(for 800ZR/800ZR+) or4(for 400ZR/400ZR+)
-
- Configure interfaces
Ethernet4/1/1andEthernet5/1/1viagNMI.Set:-
/interfaces/interface/config/enabled:true -
/interfaces/interface/config/type:ethernetCsmacd -
/interfaces/interface/ethernet/config/port-speed:SPEED_800GB(for 800ZR/800ZR+) orSPEED_400GB(for 400ZR/400ZR+) -
/interfaces/interface/ethernet/config/duplex-mode:FULL
-
- Configure optical channels
Ethernet4/1-Optical0andEthernet5/1-Optical0with initial default operational mode1, center frequency"196100000"MHz (196.1 THz), and target output power"-7"dBm:-
/components/component/optical-channel/config/operational-mode:1 -
/components/component/optical-channel/config/frequency:"196100000" -
/components/component/optical-channel/config/target-output-power:"-7"
-
- Configure the logical-channel hierarchy under
/terminal-device/logical-channels/channelfor both ports:-
Port 1 (
Ethernet4/1/1): Coherent OTN logical channel index8000(or4000on 400ZR/400ZR+ platforms;logical-channel-type:PROT_OTN,admin-state:ENABLED, assignment index1withassignment-type:OPTICAL_CHANNEL,optical-channel:"Ethernet4/1-Optical0",allocation:"800"for 800ZR/800ZR+ or"400"for 400ZR/400ZR+) and Ethernet logical channel index80000(or40000on 400ZR/400ZR+ platforms;logical-channel-type:PROT_ETHERNET,rate-class:TRIB_RATE_800Gfor 800ZR/800ZR+ orTRIB_RATE_400Gfor 400ZR/400ZR+,trib-protocol:PROT_800GEfor 800ZR/800ZR+ orPROT_400GEfor 400ZR/400ZR+,admin-state:ENABLED, ingressinterface:"Ethernet4/1/1", ingresstransceiver:"Ethernet4/1", assignment index1withassignment-type:LOGICAL_CHANNEL,logical-channel:8000or4000,allocation:"800"or"400"). -
Port 2 (
Ethernet5/1/1): Coherent OTN logical channel index8001(or4001on 400ZR/400ZR+ platforms;logical-channel-type:PROT_OTN,admin-state:ENABLED, assignment index1withassignment-type:OPTICAL_CHANNEL,optical-channel:"Ethernet5/1-Optical0",allocation:"800"for 800ZR/800ZR+ or"400"for 400ZR/400ZR+) and Ethernet logical channel index80001(or40001on 400ZR/400ZR+ platforms;logical-channel-type:PROT_ETHERNET,rate-class:TRIB_RATE_800Gfor 800ZR/800ZR+ orTRIB_RATE_400Gfor 400ZR/400ZR+,trib-protocol:PROT_800GEfor 800ZR/800ZR+ orPROT_400GEfor 400ZR/400ZR+,admin-state:ENABLED, ingressinterface:"Ethernet5/1/1", ingresstransceiver:"Ethernet5/1", assignment index1withassignment-type:LOGICAL_CHANNEL,logical-channel:8001or4001,allocation:"800"or"400").
-
Port 1 (
- Using a batched
-
Step 2 - Baseline Transceiver Inventory Verification (
gNMI.Subscribe&gNMI.Get):- Establish an
ON_CHANGEgNMI.Subscribesession and performgNMI.Getqueries on/components/component[name=Ethernet4/1]and/components/component[name=Ethernet5/1]to verify and record baseline non-empty values for all inventory leaves on both transceivers:-
/components/component/state/name("Ethernet4/1","Ethernet5/1") -
/components/component/state/type(TRANSCEIVER) -
/components/component/state/parent(non-empty parent port/FPC component string) -
/components/component/state/oper-status(ACTIVE) -
/components/component/transceiver/state/enabled(true) -
/components/component/transceiver/state/form-factor(e.g.,OSFPorQSFP_DD) -
/components/component/state/serial-no(non-empty string) -
/components/component/state/part-no(non-empty string) -
/components/component/state/mfg-name(non-empty string) -
/components/component/state/mfg-date(non-empty string) -
/components/component/state/hardware-version(non-empty string) -
/components/component/state/firmware-version(non-empty string) -
/interfaces/interface[name=Ethernet4/1/1]/state/transceiver("Ethernet4/1") -
/interfaces/interface[name=Ethernet5/1/1]/state/transceiver("Ethernet5/1") -
/terminal-device/logical-channels/channel[index=80000]/ingress/state/interface("Ethernet4/1/1") -
/terminal-device/logical-channels/channel[index=80000]/ingress/state/transceiver("Ethernet4/1") -
/terminal-device/logical-channels/channel[index=80001]/ingress/state/interface("Ethernet5/1/1") -
/terminal-device/logical-channels/channel[index=80001]/ingress/state/transceiver("Ethernet5/1")
-
- Establish an
-
Step 3 - Reconfigure to Custom Operational Mode (
Appsel) and Execute Event-Driven Transceiver Bounce:- Using a batched
gNMI.Set, update/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/operational-modeand/components/component[name=Ethernet5/1-Optical0]/optical-channel/config/operational-modefrom1to2(or the platform-specific custom 400ZR/800ZR operational mode) on both DUT ports and their peer ATE ports. - Bounce both transceivers using event-driven
gNMI.Subscribe(ON_CHANGE) state gates (do not use fixed sleep timers):- Set
/components/component[name=Ethernet4/1]/transceiver/config/enabledand/components/component[name=Ethernet5/1]/transceiver/config/enabledtofalseviagNMI.Set. - Wait via
gNMI.Subscribe(ON_CHANGE) until/components/component/transceiver/state/enabledisfalseon bothEthernet4/1andEthernet5/1and/interfaces/interface/state/oper-statuson bothEthernet4/1/1andEthernet5/1/1transitions toDOWN(orLOWER_LAYER_DOWN). - Set
/components/component[name=Ethernet4/1]/transceiver/config/enabledand/components/component[name=Ethernet5/1]/transceiver/config/enabledback totrueviagNMI.Set.
- Set
- Wait via
gNMI.Subscribe(ON_CHANGEandSAMPLE) and verify that:-
/components/component/optical-channel/state/operational-modereports2(the configured custom operational mode) on bothEthernet4/1-Optical0andEthernet5/1-Optical0. -
/components/component/optical-channel/state/frequencyreports196100000and/components/component/optical-channel/state/target-output-powerreports-7.0(within +/- 1.0 dBm). -
/components/component/state/oper-statusfor bothEthernet4/1andEthernet5/1transitions toACTIVE,/components/component/transceiver/state/enabledistrue, and all inventory leaves (serial-no,part-no,mfg-name,mfg-date,firmware-version,hardware-version) remain populated and match the exact strings recorded in Step 2. -
/interfaces/interface/state/oper-statuson bothEthernet4/1/1andEthernet5/1/1transitions toUP. -
/components/component/optical-channel/state/input-power/instant(between-15.0dBm and+2.0dBm) and/components/component/optical-channel/state/output-power/instant(within +/- 1.0 dBm of-7.0dBm) report validdecimal64optical power levels on both optical channels. -
/terminal-device/logical-channels/channel[index=8000]/otn/state/pre-fec-ber/instantand/terminal-device/logical-channels/channel[index=8001]/otn/state/pre-fec-ber/instantreport valid pre-FEC BER values below the FEC limit, and/terminal-device/logical-channels/channel/otn/state/fec-uncorrectable-blocksis0.
-
- Using a batched
-
Step 4 - Event-Driven Control-Plane/AFT Convergence and Bidirectional
Dual-Stack Traffic Validation:
- Configure the IPv4 and IPv6 subinterface addresses and the 32 IPv4 + 32
IPv6 static routes on the DUT via
gNMI.Setas specified in Test environment setup. -
Pre-Traffic gNMI Convergence Gate (No Sleep Timers): Before starting
traffic, wait via
gNMI.Subscribe(ON_CHANGE) until:-
/interfaces/interface[name=Ethernet4/1/1]/subinterfaces/subinterface[index=0]/ipv4/addresses/address[ip=192.0.2.1]/state/ip=="192.0.2.1"and/interfaces/interface[name=Ethernet5/1/1]/subinterfaces/subinterface[index=0]/ipv4/addresses/address[ip=192.0.2.5]/state/ip=="192.0.2.5". -
/interfaces/interface[name=Ethernet4/1/1]/subinterfaces/subinterface[index=0]/ipv6/addresses/address[ip=2001:db8::1]/state/ip=="2001:db8::1"and/interfaces/interface[name=Ethernet5/1/1]/subinterfaces/subinterface[index=0]/ipv6/addresses/address[ip=2001:db8::5]/state/ip=="2001:db8::5". - ARP and ND neighbor entries are resolved and present in
/interfaces/interface/subinterfaces/subinterface/ipv4/neighbors/neighbor/state/link-layer-address(for192.0.2.2and192.0.2.6) and/interfaces/interface/subinterfaces/subinterface/ipv6/neighbors/neighbor/state/link-layer-address(for2001:db8::2and2001:db8::6). - OTG neighbor resolution is verified using the standard
otgutils.WaitForARPhelper for both IPv4 and IPv6 before starting traffic. - All 32 IPv4 static prefixes (
198.51.100.0/24–198.51.115.0/24and203.0.113.0/24–203.0.128.0/24) are installed in AFT at/network-instances/network-instance[name=DEFAULT]/afts/ipv4-unicast/ipv4-entry/state/prefix, and all 32 IPv6 static prefixes (2001:db8:2::/64–2001:db8:2:f::/64and2001:db8:1::/64–2001:db8:1:f::/64) are installed in AFT at/network-instances/network-instance[name=DEFAULT]/afts/ipv6-unicast/ipv6-entry/state/prefix.
-
- Record baseline counter values on
Ethernet4/1/1andEthernet5/1/1viagNMI.Getforin-pkts,out-pkts,in-unicast-pkts,out-unicast-pkts,in-errors,in-fcs-errors,out-errors, and OTNfec-uncorrectable-blocks. -
Bidirectional IPv4 Traffic Flow:
-
Flow 1A (
ATE Port 1 -> ATE Port 2): Source IP192.0.2.2, Destination IPs cycling uniformly across the 16 prefixes198.51.100.1through198.51.115.1, frame size512bytes, rate10,000pps, duration10seconds (100,000packets total). -
Flow 1B (
ATE Port 2 -> ATE Port 1): Source IP192.0.2.6, Destination IPs cycling uniformly across the 16 prefixes203.0.113.1through203.0.128.1, frame size512bytes, rate10,000pps, duration10seconds (100,000packets total).
-
Flow 1A (
-
Bidirectional IPv6 Traffic Flow:
-
Flow 2A (
ATE Port 1 -> ATE Port 2): Source IP2001:db8::2, Destination IPs cycling uniformly across the 16 prefixes2001:db8:2::1through2001:db8:2:f::1, frame size512bytes, rate10,000pps, duration10seconds (100,000packets total). -
Flow 2B (
ATE Port 2 -> ATE Port 1): Source IP2001:db8::6, Destination IPs cycling uniformly across the 16 prefixes2001:db8:1::1through2001:db8:1:f::1, frame size512bytes, rate10,000pps, duration10seconds (100,000packets total).
-
Flow 2A (
-
Pass/Fail Criteria:
- All four flows (Flow 1A, Flow 1B, Flow 2A, Flow 2B) complete with
0% packet loss (
rx_pkts == tx_pkts == 100,000per flow). - On both
Ethernet4/1/1andEthernet5/1/1,/interfaces/interface/state/counters/in-unicast-pktsand/interfaces/interface/state/counters/out-unicast-pkts(as well asin-pktsandout-pkts) increment by at least200,000packets. -
/interfaces/interface/state/counters/in-errors,/interfaces/interface/state/counters/in-fcs-errors,/interfaces/interface/state/counters/out-errors, and/terminal-device/logical-channels/channel/otn/state/fec-uncorrectable-blocksdeltas are strictly0.
- All four flows (Flow 1A, Flow 1B, Flow 2A, Flow 2B) complete with
0% packet loss (
- Configure the IPv4 and IPv6 subinterface addresses and the 32 IPv4 + 32
IPv6 static routes on the DUT via
{
"openconfig-interfaces:interfaces": {
"interface": [
{
"config": {
"enabled": true,
"name": "Ethernet4/1/1",
"type": "iana-if-type:ethernetCsmacd"
},
"ethernet": {
"config": {
"duplex-mode": "FULL",
"port-speed": "SPEED_800GB"
}
},
"name": "Ethernet4/1/1",
"subinterfaces": {
"subinterface": [
{
"config": {
"index": 0
},
"index": 0,
"openconfig-if-ip:ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "192.0.2.1",
"prefix-length": 30
},
"ip": "192.0.2.1"
}
]
},
"config": {
"enabled": true
}
},
"openconfig-if-ip:ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8::1",
"prefix-length": 126
},
"ip": "2001:db8::1"
}
]
},
"config": {
"enabled": true
}
}
}
]
}
},
{
"config": {
"enabled": true,
"name": "Ethernet5/1/1",
"type": "iana-if-type:ethernetCsmacd"
},
"ethernet": {
"config": {
"duplex-mode": "FULL",
"port-speed": "SPEED_800GB"
}
},
"name": "Ethernet5/1/1",
"subinterfaces": {
"subinterface": [
{
"config": {
"index": 0
},
"index": 0,
"openconfig-if-ip:ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "192.0.2.5",
"prefix-length": 30
},
"ip": "192.0.2.5"
}
]
},
"config": {
"enabled": true
}
},
"openconfig-if-ip:ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8::5",
"prefix-length": 126
},
"ip": "2001:db8::5"
}
]
},
"config": {
"enabled": true
}
}
}
]
}
}
]
},
"openconfig-network-instance:network-instances": {
"network-instance": [
{
"config": {
"name": "DEFAULT"
},
"name": "DEFAULT",
"protocols": {
"protocol": [
{
"config": {
"identifier": "STATIC",
"name": "STATIC"
},
"identifier": "STATIC",
"name": "STATIC",
"static-routes": {
"static": [
{
"config": {
"prefix": "198.51.100.0/24"
},
"next-hops": {
"next-hop": [
{
"config": {
"index": "0",
"next-hop": "192.0.2.6"
},
"index": "0"
}
]
},
"prefix": "198.51.100.0/24"
},
{
"config": {
"prefix": "2001:db8:2::/64"
},
"next-hops": {
"next-hop": [
{
"config": {
"index": "0",
"next-hop": "2001:db8::6"
},
"index": "0"
}
]
},
"prefix": "2001:db8:2::/64"
}
]
}
}
]
}
}
]
},
"openconfig-platform:components": {
"component": [
{
"config": {
"name": "Ethernet4/1-Port"
},
"name": "Ethernet4/1-Port",
"openconfig-platform-port:port": {
"breakout-mode": {
"groups": {
"group": [
{
"config": {
"breakout-speed": "openconfig-if-ethernet:SPEED_800GB",
"index": 1,
"num-breakouts": 1,
"num-physical-channels": 8
},
"index": 1
}
]
}
}
}
},
{
"config": {
"name": "Ethernet4/1"
},
"name": "Ethernet4/1",
"openconfig-platform-transceiver:transceiver": {
"config": {
"enabled": true
}
}
},
{
"config": {
"name": "Ethernet4/1-Optical0"
},
"name": "Ethernet4/1-Optical0",
"openconfig-terminal-device:optical-channel": {
"config": {
"frequency": "196100000",
"operational-mode": 1,
"target-output-power": "-7"
}
}
}
]
},
"openconfig-terminal-device:terminal-device": {
"logical-channels": {
"channel": [
{
"config": {
"admin-state": "ENABLED",
"description": "OTN Logical Channel",
"index": 8000,
"logical-channel-type": "openconfig-transport-types:PROT_OTN"
},
"index": 8000,
"logical-channel-assignments": {
"assignment": [
{
"config": {
"allocation": "800",
"assignment-type": "OPTICAL_CHANNEL",
"description": "OTN to optical channel assignment",
"index": 1,
"optical-channel": "Ethernet4/1-Optical0"
},
"index": 1
}
]
}
},
{
"config": {
"admin-state": "ENABLED",
"description": "ETH Logical Channel",
"index": 80000,
"logical-channel-type": "openconfig-transport-types:PROT_ETHERNET",
"rate-class": "openconfig-transport-types:TRIB_RATE_800G",
"trib-protocol": "openconfig-transport-types:PROT_800GE"
},
"index": 80000,
"ingress": {
"config": {
"interface": "Ethernet4/1/1",
"transceiver": "Ethernet4/1"
}
},
"logical-channel-assignments": {
"assignment": [
{
"config": {
"allocation": "800",
"assignment-type": "LOGICAL_CHANNEL",
"description": "ETH to OTN assignment",
"index": 1,
"logical-channel": 8000
},
"index": 1
}
]
}
}
]
}
}
}TRANSCEIVER-109.2: Validate scaled multi-port 400ZR / 800ZR transceiver inventory persistence and link recovery across repeated interface delete and re-create cycles
When interfaces associated with coherent 400G ZR/ZR+ (SPEED_400GB) or 800G
ZR/ZR+ (SPEED_800GB) optics across multiple line cards are deleted and
re-created, the device software database must retain the physical transceiver
component inventory rather than purging the optic record (no-info / missing
from /components/component). Building directly on the established state of
TRANSCEIVER-109.1, this subtest executes 5 consecutive cycles of simultaneous
batched gNMI.Set interface deletion and re-creation across both 400ZR or
800ZR interfaces (Ethernet4/1/1 and Ethernet5/1/1), verifying continuous
hardware inventory presence via ON_CHANGE gNMI.Subscribe and full
bidirectional dual-stack L3 traffic recovery.
-
Step 1 - Maintain Continuous
ON_CHANGEInventory Subscription:- Starting from the active state of
TRANSCEIVER-109.1, keep an activeON_CHANGEgNMI.Subscribesubscription monitoring/components/component[name=Ethernet4/1]/state/and/components/component[name=Ethernet5/1]/state/and verify that the current values match the baseline strings recorded inTRANSCEIVER-109.1Step 2 (name,type,parent,oper-status,serial-no,part-no,mfg-name,mfg-date,hardware-version,firmware-version).
- Starting from the active state of
-
Step 2 - Execute 5 Consecutive Multi-Port Interface Delete and Re-Create
Cycles (
Iteration i = 1..5):- For each iteration
$i \in {1, 2, 3, 4, 5}$ :-
Batched Interface Delete via
gNMI.Set:- Issue a single batched
gNMI.Set(Delete) request removing/interfaces/interface[name=Ethernet4/1/1],/interfaces/interface[name=Ethernet5/1/1],/terminal-device/logical-channels/channel[index=80000]/ingress/config/interface(or40000on 400ZR/400ZR+ platforms), and/terminal-device/logical-channels/channel[index=80001]/ingress/config/interface(or40001on 400ZR/400ZR+ platforms), while keeping both physical transceivers enabled (/components/component[name=Ethernet4/1]/transceiver/config/enabled=trueand/components/component[name=Ethernet5/1]/transceiver/config/enabled=true).
- Issue a single batched
-
Verify Transceiver Inventory Persistence While Interfaces Are
Deleted:
- Inspect the active
ON_CHANGEgNMI.Subscribestream and query/components/component[name=Ethernet4/1]/state/and/components/component[name=Ethernet5/1]/state/viagNMI.Get. -
Pass/Fail Criteria (Per Delete Cycle):
- No gNMI delete notification is emitted for
/components/component[name=Ethernet4/1],/components/component[name=Ethernet5/1], or any of their inventory leaves. -
/components/component/state/name,/components/component/state/type(TRANSCEIVER),/components/component/state/parent,/components/component/state/serial-no,/components/component/state/part-no,/components/component/state/mfg-name,/components/component/state/mfg-date,/components/component/state/hardware-version, and/components/component/state/firmware-versionremain populated on bothEthernet4/1andEthernet5/1and match the exact baseline strings fromTRANSCEIVER-109.1Step 2.
- No gNMI delete notification is emitted for
- Inspect the active
-
Batched Interface Re-Creation and Custom Operational Mode
Verification:
- Using a batched
gNMI.Set, re-create/interfaces/interface[name=Ethernet4/1/1](SPEED_800GBfor 800ZR/800ZR+ orSPEED_400GBfor 400ZR/400ZR+,192.0.2.1/30,2001:db8::1/126) and/interfaces/interface[name=Ethernet5/1/1](SPEED_800GBfor 800ZR/800ZR+ orSPEED_400GBfor 400ZR/400ZR+,192.0.2.5/30,2001:db8::5/126), re-bind/terminal-device/logical-channels/channel[index=80000]/ingress/config/interface(or40000) to"Ethernet4/1/1"and/terminal-device/logical-channels/channel[index=80001]/ingress/config/interface(or40001) to"Ethernet5/1/1", and ensure/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/operational-modeand/components/component[name=Ethernet5/1-Optical0]/optical-channel/config/operational-modeare set to the custom operational mode (2). - Wait via
gNMI.Subscribe(ON_CHANGE) until:-
/interfaces/interface[name=Ethernet4/1/1]/state/oper-status==UPand/interfaces/interface[name=Ethernet5/1/1]/state/oper-status==UP. -
/interfaces/interface[name=Ethernet4/1/1]/state/transceiver=="Ethernet4/1"and/interfaces/interface[name=Ethernet5/1/1]/state/transceiver=="Ethernet5/1". -
/components/component[name=Ethernet4/1]/state/oper-status==ACTIVEand/components/component[name=Ethernet5/1]/state/oper-status==ACTIVE.
-
- Using a batched
-
Batched Interface Delete via
- For each iteration
-
Step 3 - Post-Stress Bidirectional Dual-Stack IPv4 and IPv6 Traffic
Validation:
- Wait via
gNMI.Subscribe(ON_CHANGE) for ARP (192.0.2.2,192.0.2.6), IPv6 ND (2001:db8::2,2001:db8::6), and all 32 IPv4 + 32 IPv6 AFT entries to converge inDEFAULT. - Re-run the bidirectional IPv4 flows (Flow 1A and Flow 1B,
100,000packets each) and bidirectional IPv6 flows (Flow 2A and Flow 2B,100,000packets each). -
Pass/Fail Criteria: All four flows complete with 0% packet loss,
interface unicast packet counters increment by at least
200,000packets per interface, and interface error counters (in-errors,in-fcs-errors,out-errors) and OTNfec-uncorrectable-blocksdeltas remain0.
- Wait via
TRANSCEIVER-109.3: Negative Validation — Unsupported Operational Mode, Optical Mismatch Fault Recovery, and Laser Shutoff
Building on the active state from TRANSCEIVER-109.2, this subtest validates
that negative optical configurations and fault conditions do not purge
transceiver hardware inventory from /components/component and that the 400ZR
or 800ZR coherent transceivers cleanly recover via custom operational-mode
provisioning and transceiver state bounce.
-
Step 1 - Negative Case 1: Unsupported / Out-of-Range
operational-mode(Appsel) Handling:- Using
gNMI.Set, attempt to configure an unsupportedoperational-modevalue (65535) on/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/operational-mode. -
Pass/Fail Criteria:
- The DUT must either reject the
gNMI.Setrequest with a gRPC/gNMI error (INVALID_ARGUMENT) or transition the optical channel out of service without crashing the optics daemon. - Query
/components/component[name=Ethernet4/1]/state/viagNMI.Getand inspect theON_CHANGEgNMI.Subscribestream: verify thatEthernet4/1is not deleted from/components/componentand thatserial-no,part-no,mfg-name,mfg-date,hardware-version, andfirmware-versionremain populated and identical to baseline values.
- The DUT must either reject the
- Using
-
Step 2 - Negative Case 2: Optical Frequency / Mode Mismatch Fault
Simulation and Subsequent Bounce Recovery:
- Using
gNMI.Set, configure a mismatched center frequency of"193100000"MHz (193.1THz) on/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/frequencywhile the peer ATE port remains at"196100000"MHz (196.1THz), forcing an optical loss-of-lock fault on Link 1. - Wait via
gNMI.Subscribe(ON_CHANGE) for/interfaces/interface[name=Ethernet4/1/1]/state/oper-statusto transition toDOWN(orLOWER_LAYER_DOWN). - Verify via
gNMI.Getthat/components/component[name=Ethernet4/1]/state/retains all static transceiver inventory leaves (serial-no,part-no,mfg-name,mfg-date,hardware-version,firmware-version) while in the optical fault state, and verify that traffic sent on Flow 1A and Flow 2A experiences 100% loss while Link 1 is down. -
Recovery from Optical Fault: Restore
/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/frequencyto"196100000"MHz and/components/component[name=Ethernet4/1-Optical0]/optical-channel/config/operational-modeto the custom operational mode (2), and bounce the transceiver viagNMI.Setby setting/components/component[name=Ethernet4/1]/transceiver/config/enabledtofalse, waiting viagNMI.Subscribefortransceiver/state/enabled==false, and settingtransceiver/config/enabledtotrue. - Wait via
gNMI.Subscribe(ON_CHANGE) for/interfaces/interface[name=Ethernet4/1/1]/state/oper-statusto transition back toUPand verify 0% packet loss across Flows 1A, 1B, 2A, and 2B.
- Using
-
Step 3 - Negative Case 3: Administrative Transceiver Disable Laser Shutoff
and Inventory Retention:
- Using
gNMI.Set, set/components/component[name=Ethernet4/1]/transceiver/config/enabledtofalsewhile keeping/interfaces/interface[name=Ethernet4/1/1]/config/enabledset totrue. - Wait via
gNMI.Subscribefor/components/component[name=Ethernet4/1]/transceiver/state/enabledto reportfalseand/interfaces/interface[name=Ethernet4/1/1]/state/oper-statusto reportDOWN. -
Pass/Fail Criteria:
- Verify via
gNMI.Getthat/components/component[name=Ethernet4/1-Optical0]/optical-channel/state/output-power/instantdrops below-30.0dBm (confirming laser shutoff). - Verify via
gNMI.Getthat all static transceiver inventory leaves (serial-no,part-no,mfg-name,mfg-date,hardware-version,firmware-version) remain present in/components/component[name=Ethernet4/1]/state/.
- Verify via
-
Final Recovery Verification: Re-enable
/components/component[name=Ethernet4/1]/transceiver/config/enabledtotrueviagNMI.Set, wait viagNMI.Subscribefor/interfaces/interface[name=Ethernet4/1/1]/state/oper-status==UP,/components/component[name=Ethernet4/1-Optical0]/optical-channel/state/output-power/instantwithin +/- 1.0 dBm of-7.0dBm, ARP/ND resolution, and verify 0% packet loss across all bidirectional IPv4 and IPv6 flows.
- Using
- Revert all modified optical-channel
operational-mode,frequency, logical-channel, subinterface IPv4/IPv6, and static route configurations to the baseline state usinggNMI.Set(registered viat.Cleanup()in test automation), and verify viagNMI.Getthat all tested transceivers and interfaces return to their pre-test operational state.
paths:
# Config Parameter coverage
/components/component/optical-channel/config/frequency:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/config/operational-mode:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/config/target-output-power:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/port/breakout-mode/groups/group/config/breakout-speed:
platform_type: ["PORT"]
/components/component/port/breakout-mode/groups/group/config/index:
platform_type: ["PORT"]
/components/component/port/breakout-mode/groups/group/config/num-breakouts:
platform_type: ["PORT"]
/components/component/port/breakout-mode/groups/group/config/num-physical-channels:
platform_type: ["PORT"]
/components/component/transceiver/config/enabled:
platform_type: ["TRANSCEIVER"]
/interfaces/interface/config/enabled:
/interfaces/interface/config/type:
/interfaces/interface/ethernet/config/duplex-mode:
/interfaces/interface/ethernet/config/port-speed:
/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:
/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/next-hop:
/terminal-device/logical-channels/channel/config/admin-state:
/terminal-device/logical-channels/channel/config/description:
/terminal-device/logical-channels/channel/config/index:
/terminal-device/logical-channels/channel/config/logical-channel-type:
/terminal-device/logical-channels/channel/config/rate-class:
/terminal-device/logical-channels/channel/config/trib-protocol:
/terminal-device/logical-channels/channel/ingress/config/interface:
/terminal-device/logical-channels/channel/ingress/config/transceiver:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/allocation:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/assignment-type:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/description:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/index:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/logical-channel:
/terminal-device/logical-channels/channel/logical-channel-assignments/assignment/config/optical-channel:
# Telemetry Parameter coverage
/components/component/optical-channel/state/frequency:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/state/input-power/instant:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/state/operational-mode:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/state/output-power/instant:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/optical-channel/state/target-output-power:
platform_type: ["OPTICAL_CHANNEL"]
/components/component/state/firmware-version:
platform_type: ["TRANSCEIVER"]
/components/component/state/hardware-version:
platform_type: ["TRANSCEIVER"]
/components/component/state/mfg-date:
platform_type: ["TRANSCEIVER"]
/components/component/state/mfg-name:
platform_type: ["TRANSCEIVER"]
/components/component/state/name:
platform_type: ["PORT", "TRANSCEIVER", "OPTICAL_CHANNEL"]
/components/component/state/oper-status:
platform_type: ["TRANSCEIVER"]
/components/component/state/parent:
platform_type: ["PORT", "TRANSCEIVER", "OPTICAL_CHANNEL"]
/components/component/state/part-no:
platform_type: ["TRANSCEIVER"]
/components/component/state/serial-no:
platform_type: ["TRANSCEIVER"]
/components/component/state/type:
platform_type: ["PORT", "TRANSCEIVER", "OPTICAL_CHANNEL"]
/components/component/transceiver/state/enabled:
platform_type: ["TRANSCEIVER"]
/components/component/transceiver/state/form-factor:
platform_type: ["TRANSCEIVER"]
/interfaces/interface/state/counters/in-errors:
/interfaces/interface/state/counters/in-fcs-errors:
/interfaces/interface/state/counters/in-pkts:
/interfaces/interface/state/counters/in-unicast-pkts:
/interfaces/interface/state/counters/out-errors:
/interfaces/interface/state/counters/out-pkts:
/interfaces/interface/state/counters/out-unicast-pkts:
/interfaces/interface/state/oper-status:
/interfaces/interface/state/transceiver:
/interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address/state/ip:
/interfaces/interface/subinterfaces/subinterface/ipv4/neighbors/neighbor/state/link-layer-address:
/interfaces/interface/subinterfaces/subinterface/ipv6/addresses/address/state/ip:
/interfaces/interface/subinterfaces/subinterface/ipv6/neighbors/neighbor/state/link-layer-address:
/network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/prefix:
/network-instances/network-instance/afts/ipv6-unicast/ipv6-entry/state/prefix:
/terminal-device/logical-channels/channel/ingress/state/interface:
/terminal-device/logical-channels/channel/ingress/state/transceiver:
/terminal-device/logical-channels/channel/otn/state/fec-uncorrectable-blocks:
/terminal-device/logical-channels/channel/otn/state/pre-fec-ber/instant:
rpcs:
gnmi:
gNMI.Get:
gNMI.Set:
gNMI.Subscribe:- FFF
-
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