• Static route ECMP must be supported
• Static route metric must be supported
• Static route Administrative Distance / Preference must be supported
• set-tag attribute must be supported for static routes
• Disabling recursive nexthop resolution must be supported

• https://github.com/openconfig/featureprofiles/blob/main/topologies/atedut_4.testbed

• Connect DUT port-1, port-2 and port-3 to ATE port-1, port-2 and port-3 respectively
• Configure IPv4/IPv6 addresses on DUT and ATE the interfaces
• Configure one IPv4 destination i.e. ipv4-network = 203.0.113.0/24 connected to ATE port 1 and 2
• Configure one IPv6 destination i.e. ipv6-network = 2001:db8:128:128::/64 connected to ATE port 1 and 2

• Configure IPv4 static routes:
  • Configure one IPv4 static route i.e. ipv4-route-a on the DUT for destination ipv4-network 203.0.113.0/24 with the next hop set to the IPv4 address of ATE port-1
  • Configure another IPv4 static route i.e. ipv4-route-b on the DUT for destination ipv4-network 203.0.113.0/24 with the next hop set to the IPv4 address of ATE port-2
• Validate both the routes i.e. ipv4-route-[a|b] are configured and reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
• Configure IPv6 static routes:
  • Configure one IPv6 static route i.e. ipv6-route-a on the DUT for destination ipv6-network 2001:db8:128:128::/64 with the next hop set to the IPv6 address of ATE port-1
  • Configure another IPv6 static route i.e. ipv6-route-b on the DUT for destination ipv6-network 2001:db8:128:128::/64 with the next hop set to the IPv6 address of ATE port-2
• Validate both the routes i.e. ipv6-route-[a|b] are configured and reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is received from DUT on both port-1 and port-2 and ECMP works

• Configure metric of ipv4-route-b and ipv6-route-b to 100
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/metric
• Validate that the metric is set correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/metric
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is received from DUT on port-1 and not on port-2

• Configure preference of ipv4-route-a and ipv6-route-a to 50
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/preference
• Validate that the preference is set correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/preference
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is now received from DUT on port-2 and not on port-1

• Configure a tag of value 10 on ipv4 and ipv6 static routes
  • /network-instances/network-instance/protocols/protocol/static-routes/static/config/set-tag
• Validate the tag is set
  • /network-instances/network-instance/protocols/protocol/static-routes/static/state/set-tag

• Remove metric of 100 from ipv4-route-b and ipv6-route-b
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/metric
• Remove preference of 50 from ipv4-route-a and ipv6-route-a
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/preference
• Change the IPv6 next-hop of the ipv6-route-a with the next hop set to the IPv4 address of ATE port-1
• Change the IPv6 next-hop of the ipv6-route-b with the next hop set to the IPv4 address of ATE port-2
• Validate both the routes i.e. ipv6-route-[a|b] are configured and the IPv4 next-hop is reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop
• Initiate traffic from ATE port-3 towards destination ipv6-network 2001:db8:128:128::/64
• Validate that traffic is received from DUT on both port-1 and port-2 and ECMP works

• Change the IPv4 next-hop of the ipv4-route-a with the next hop set to the IPv6 address of ATE port-1
• Change the IPv4 next-hop of the ipv4-route-b with the next hop set to the IPv6 address of ATE port-2
• Validate both the routes i.e. ipv4-route-[a|b] are configured and the IPv6 next-hop is reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24
• Validate that traffic is received from DUT on both port-1 and port-2 and ECMP works

• Configure IPv4 static routes:
  • Configure one IPv4 static route i.e. ipv4-route-a on the DUT for destination ipv4-network 203.0.113.0/24 with the next hop set to DROP local-defined next hop
• Validate the route is configured and reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
• Configure IPv6 static routes:
  • Configure one IPv6 static route i.e. ipv6-route-a on the DUT for destination ipv6-network 2001:db8:128:128::/64 with the next hop set to DROP local-defined next hop
• Validate the route is configured and reported correctly
  • /network-instances/network-instance/protocols/protocol/static-routes/static/prefix
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is dropped on DUT and not received on port-1 and port-2

• Configure ipv4 and ipv6 ISIS between ATE port-1 <-> DUT port-1 and ATE port-2 <-> DUT port2
  • /network-instances/network-instance/protocols/protocol/isis/global/afi-safi
• Configure one IPv4 /32 host route i.e. ipv4-loopback = 198.51.100.100/32 connected to ATE and advertised to DUT through both the IPv4 ISIS adjacencies
• Configure one IPv6 /128 host route i.e. ipv6-loopback = 2001:db8::64:64::1/128 connected to ATE and advertised to DUT through both the IPv6 ISIS adjacencies
• Configure one IPv4 static route i.e. ipv4-route on the DUT for destination ipv4-network 203.0.113.0/24 with the next hop of ipv4-loopback 198.51.100.100/32. Remove all other existing next hops for the route.
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop
• Configure one IPv6 static route i.e. ipv6-route on the DUT for destination ipv6-network 2001:db8:128:128::/64 with the next hop of ipv6-loopback = 2001:db8::64:64::1/128. Remove all other existing next hops for the route.
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is received from DUT (doesn't matter which port)
• Disable static route next-hop recursive lookup (set to false)
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/recurse
• Validate static route next-hop recursive lookup is disabled
  • /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/recurse
• Initiate traffic from ATE port-3 towards destination ipv4-network 203.0.113.0/24 and ipv6-network 2001:db8:128:128::/64
• Validate that traffic is NOT received from DUT

The below yaml defines the OC paths intended to be covered by this test. OC paths used for test setup are not listed here.

paths:
  ## Config Paths ##
  /interfaces/interface/config/enabled:
  /interfaces/interface/subinterfaces/subinterface/ipv4/config/enabled:
  /interfaces/interface/subinterfaces/subinterface/ipv6/config/enabled:
  /network-instances/network-instance/protocols/protocol/static-routes/static/config/prefix:
  /network-instances/network-instance/protocols/protocol/static-routes/static/config/set-tag:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/metric:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/preference:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/recurse:

  ## State Paths ##
  /network-instances/network-instance/protocols/protocol/static-routes/static/state/prefix:
  /network-instances/network-instance/protocols/protocol/static-routes/static/state/set-tag:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/next-hop:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/metric:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/preference:
  /network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/state/recurse:

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

• FFF