This test verifies scaling of MPLSoGUE decapsulation of IP traffic using static MPLS LSP configuration. MPLSoGUE Traffic on ingress to the DUT is decapsulated and IPV4/IPV6 payload is forwarded towards the IPV4/IPV6 egress nexthop.

• featureprofiles/topologies/atedut_8.testbed

DUT has 2 ingress aggregate interfaces and 1 egress aggregate interface.

                         |         | --eBGP-- | ATE Ports 3,4 |
    [ ATE Ports 1,2 ]----|   DUT   |          |               |
                         |         | --eBGP-- | ATE Port 5,6  |

Test uses aggregate 802.3ad bundled interfaces (Aggregate Interfaces).

• Ingress Ports: Aggregate2 and Aggregate3

  • Aggregate2 (ATE Ports 3,4) and Aggregate3 (ATE Ports 5,6) are used as the source ports for encapsulated traffic.

• Egress Ports: Aggregate1

  • Traffic is forwarded (egress) on Aggregate1 (ATE Ports 1,2) .

Please generate config using PF-1.5.1

Generate traffic on ATE Ports 3,4,5,6 having:

• Outer source address: random combination of 1000+ IPV4 source addresses from 100.64.0.0/22
• Outer destination address: Traffic must fall within the configured IPV4 unicast decap prefix range for MPLSoGUE traffic on the device
• MPLS Labels: Configure streams that map to every egress interface by having associated IPV4/IPV6/Multicast static MPLS labels in the MPLSoGUE header
• Inner payload with all possible DSCP range 0-56 :
  • Both IPV4 and IPV6 unicast payloads, with random source address, destination address, TCP/UDP source port and destination ports
  • Multicast traffic with random source address, TCP/UDP header with random source and destination ports
• Use 64, 128, 256, 512, 1024.. MTU bytes frame size
• Increase the number of VLANs to 2000 under Aggregate1 with traffic running on the device

Verify:

• All traffic received on Aggregate2 and Aggregate3 gets decapsulated and forwarded as IPV4/IPV6 unicast on the respective egress interfaces under Aggregate1
• No packet loss when forwarding with counters incrementing corresponding to traffic
• Traffic equally load-balanced across member links of the aggregate interfaces
• Inner payload DSCP and TTL values are not altered by the device
• Device can achieve the maximum interface scale on the device
• Entire static label range is usable and functional by sending traffic across the entire label range

TODO: Finalize and update the below paths after the review and testing on any vendor device.

paths:
  # Telemetry for GRE decap rule    
  /network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/state/matched-pkts:
  /network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/state/matched-octets:
    
  # Config paths for GRE decap
  /network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/action/config/decapsulate-mpls-in-udp:

  /network-instances/network-instance/afts/policy-forwarding/policy-forwarding-entry/state/counters/packets-forwarded:
  /network-instances/network-instance/afts/policy-forwarding/policy-forwarding-entry/state/counters/octets-forwarded:
  /network-instances/network-instance/policy-forwarding/policies/policy/rules/rule/state/sequence-id:

rpcs:
  gnmi:
    gNMI.Set:
    gNMI.Subscribe:

FFF