requirements for wECMP support with link bandwidth community (opencon…

…fig#2556) * requirements for wecmp support with link bandwidth community * Update feature/bgp/multipath/otg_tests/bgp_multipath_wecmp_lbw_community_test/README.md Co-authored-by: Darren Loher <dloher@google.com> * Update feature/bgp/multipath/otg_tests/bgp_multipath_wecmp_lbw_community_test/README.md Co-authored-by: Darren Loher <dloher@google.com> --------- Co-authored-by: Darren Loher <dloher@google.com>
open-traffic-generator · Jan 30, 2024 · a97a28d · a97a28d
1 parent 11f724a
commit a97a28d
Show file tree

Hide file tree

Showing 3 changed files with 89 additions and 14 deletions.
diff --git a/feature/bgp/multipath/otg_tests/bgp_multipath_ecmp_test/README.md b/feature/bgp/multipath/otg_tests/bgp_multipath_ecmp_test/README.md
@@ -6,7 +6,7 @@ Validate BGP in multipath scenario
 
 ## Testbed type
 
-[TESTBED_DUT_ATE_4LINKS](https://github.com/openconfig/featureprofiles/blob/main/topologies/atedut_2.testbed)
+[TESTBED_DUT_ATE_4LINKS](https://github.com/openconfig/featureprofiles/blob/main/topologies/atedut_4.testbed)
 
 ## Procedure
 
@@ -18,7 +18,7 @@ Validate BGP in multipath scenario
     *   ATE port-1 and DUT port-1
     *   ATE port-2 and DUT port-2
     *   ATE port-3 and DUT port-3
-    *   ATE port-3 and DUT port-3
+    *   ATE port-4 and DUT port-4
 *   Enable an Accept-route all import-policy/export-policy for eBGP session
     under the neighbor AFI/SAFI
 *   Create an IPv4 internal target network attached to ATE port 2, 3 and 4
@@ -30,7 +30,7 @@ Validate BGP in multipath scenario
     *   Configure ATE devices(ports) on same AS
     *   Advertise equal cost paths from 3 interfaces of ATE of same AS
     *   Check entries in FIB for advertised prefix, it should only have 1 entry
-    *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
+        *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
     *   Initiate traffic from ATE port-1 to the DUT and destined to internal
         target network
     *   Check entire traffic should only be forwarded by one of DUT port2, port3
@@ -40,33 +40,33 @@ Validate BGP in multipath scenario
 
     *   Configure ATE devices(ports) on same AS
     *   Enable multipath and set maximum-paths limit to 2
-    *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
-    *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
     *   Advertise equal cost paths from 3 interfaces of ATE of same AS
     *   Check entries in FIB for advertised prefix, it should only have 2
         entries
-    *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
+        *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
     *   Initiate traffic from ATE port-1 to the DUT and destined to internal
         target network
-    *   Check entire traffic should only be forwarded by any two among DUT
+    *   Check entire traffic should only be equally forwarded by any two among DUT
         port2, port3 or port4
 
-*   RT-1.51.3: Verify use of allow-mulitple-as for ECMP routing across different
+*   RT-1.51.3: Verify use of allow-multiple-as for ECMP routing across different
     peer AS
 
     *   Configure ATE devices(ports) on different AS
     *   Enable multipath, set maximum-paths limit to 2 and enable allow multiple
         AS
-    *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
-    *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/allow-multiple-as
-    *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/allow-multiple-as
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
     *   Advertise equal cost paths from 3 interfaces of ATE of different AS
     *   Check entries in FIB for advertised prefix, it should only have 2
         entries
-    *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
+        *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
     *   Initiate traffic from ATE port-1 to the DUT and destined to internal
         target network
-    *   Check entire traffic should only be forwarded by any two among DUT
+    *   Check entire traffic should only be equally forwarded by any two among DUT
         port2, port3 or port4
 
 ## Config Parameter Coverage
@@ -90,5 +90,5 @@ Validate BGP in multipath scenario
 
 ## Required DUT platform
 
-*   vRX - virtual router device
+*   FFF - Fixed Form Factor
 
diff --git a/feature/bgp/multipath/otg_tests/bgp_multipath_wecmp_lbw_community_test/README.md b/feature/bgp/multipath/otg_tests/bgp_multipath_wecmp_lbw_community_test/README.md
@@ -0,0 +1,69 @@
+# RT-1.52: BGP multipath UCMP support with Link Bandwidth Community
+
+## Summary
+
+Validate BGP in multipath UCMP support with link bandwidth community
+
+## Testbed type
+
+[TESTBED_DUT_ATE_4LINKS](https://github.com/openconfig/featureprofiles/blob/main/topologies/atedut_4.testbed)
+
+## Procedure
+
+### Setup
+
+*   Connect DUT port 1, 2 and 3 to ATE port 1, 2 and 3 respectively
+*   Configure IPv4/IPv6 addresses on the interfaces
+*   Establish eBGP sessions between:
+    *   ATE port-1 and DUT port-1
+    *   ATE port-2 and DUT port-2
+    *   ATE port-3 and DUT port-3
+*   Enable an Accept-route all import-policy/export-policy for eBGP session
+    under the neighbor AFI/SAFI
+*   Create an IPv4 internal target network attached to ATE port 2 and 3
+
+### Tests
+
+*   RT-1.52.1: Verify use of community type
+
+    *   Configure ATE port 1, 2 and 3 on different AS
+    *   Enable multipath, set maximum-paths limit to 2, enable allow multiple
+        AS, and send community type to BOTH (STANDARD and EXTENDED)
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/allow-multiple-as
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/send-community-type
+        *   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/use-multiple-paths/ebgp/link-bandwidth-ext-community/config/enabled
+    *   Advertise equal cost paths from port2 and port3 of ATE
+    *   Check entries in FIB for advertised prefix, it should have 2 entries
+        *   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
+    *   Initiate traffic from ATE port-1 to the DUT and destined to internal
+        target network
+    *   Check entire traffic should only be unequally forwarded between DUT
+        port2 and port3
+
+## Config Parameter Coverage
+
+*   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/config/enabled
+*   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/allow-multiple-as
+*   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/use-multiple-paths/ebgp/config/maximum-paths
+*   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/send-community-type
+*   /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/use-multiple-paths/ebgp/link-bandwidth-ext-community/config/enabled
+
+## Telemetry Parameter Coverage
+
+*   /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state
+*   /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/next-hop-group
+*   /network-instances/network-instance/afts/next-hop-groups/next-hop-group[id=<id>]/state
+*   /network-instances/network-instance/afts/next-hop-groups/next-hop-group/next-hops
+
+## Protocol/RPC Parameter Coverage
+
+*   gNMI
+    *   Set
+    *   Subscribe
+
+## Required DUT platform
+
+*   FFF - Fixed Form Factor
+
diff --git a/testregistry.textproto b/testregistry.textproto
@@ -302,6 +302,12 @@ test: {
   readme: "https://github.com/openconfig/featureprofiles/blob/main/feature/bgp/multipath/otg_tests/bgp_multipath_ecmp_test/README.md"
   exec: " "
 }
+test: {
+  id: "RT-1.52"
+  description: "BGP multipath ECMP support with Link Bandwidth Community"
+  readme: "https://github.com/openconfig/featureprofiles/blob/main/feature/bgp/multipath/otg_tests/bgp_multipath_wecmp_lbw_community_test/README.md"
+  exec: " "
+}
 test: {
   id: "RT-1.7"
   description: "Local BGP Test"