From 8e00c94a675704e73ac33ac9727e115b280a1275 Mon Sep 17 00:00:00 2001 From: Sudhin Jacob Date: Wed, 30 Oct 2024 06:21:53 +0000 Subject: [PATCH] latest updates --- .../aft/aft_base/otg_tests/aft_base/README.md | 35 +++--- .../otg_tests/aft_prefixcounters/README.md | 105 +++++------------- 2 files changed, 48 insertions(+), 92 deletions(-) diff --git a/feature/aft/aft_base/otg_tests/aft_base/README.md b/feature/aft/aft_base/otg_tests/aft_base/README.md index 447e254ed28..92e38c522e1 100644 --- a/feature/aft/aft_base/otg_tests/aft_base/README.md +++ b/feature/aft/aft_base/otg_tests/aft_base/README.md @@ -4,6 +4,10 @@ IPv4/IPv6 unicast routes next hop group and next hop. +## Testbed + +* atedut_12.binding + ## Test Setup ### Generate DUT and ATE Configuration @@ -29,33 +33,36 @@ Establish RSVP Sessions between ATE:port3 and SUT:port3. * Configure explicit null and ipv6 tunneling. * BGP advertised routes from ATE:port3 must be pointing to the 2 tunnels in the DUT. -## Procedure +### Procedure -* Gnmi set with REPLACE option to push the configuration DUT. +* Use gNMI.Set with REPLACE option to push the Test Setup configuration to the DUT. * ATE configuration must be pushed. -## Verifications +### Verifications -* BGP 2000 routes advertised from ATE:port1,port2 must have 2 nexthops. -* IS-IS 2000 routes advertised from ATE:port3 must have one next hop. -* BGP 100 routes advertised from ATE:port3 must have 2 next hops pointing to tunnels. +* BGP route advertised from ATE:port1,port2 must have 2 nexthops. +* IS-IS route advertised from ATE:port3 must have one next hop. +* BGP route advertised from ATE:port3 must have 2 next hops pointing to tunnels. * Use gnmi Subscribe with ON_CHANGE option to /network-instances/network-instance/afts. +* For verifying prefix, nexthop groups, next hop use the leaves mentioed in the path section. * Verify afts prefix advertised by BGP,ISIS. * Verify its next hop group, number of next hop and its interfaces. * Verify the number of next hop is same as expected. * Verify all other leaves mentioned in the path section. + ## AFT-1.1.1: AFT Base Link Down scenario 1 ### Procedure -Bring down the link between ATE:port2 and DUT:port2 +Bring down the link between ATE:port2 and DUT:port2 using OTG api. ### Verifications * BGP routes advertised from ATE:port1,port2 must have 1 nexthop. * IS-IS routes advertised from ATE:port3 must have one next hop. * BGP routes advertised from ATE:port3 must have 2 next hops pointing to tunnels. +* For verifying prefix, nexthop groups, next hop use the leaves mentioed in the path section. * Verify afts prefix advertised by BGP,ISIS. * Verify its next hop group, number of next hop and its interfaces. * Verify the number of next hop is same as expected. @@ -64,13 +71,14 @@ Bring down the link between ATE:port2 and DUT:port2 ### Procedure -Bring down both links between ATE:port1,port2 and DUT:port1,port2 +Bring down both links between ATE:port1,port2 and DUT:port1,port2 using OTG api. ### Verifications * BGP routes advertised from ATE:port1,port2 must be removed from RIB,FIB of the DUT, query results nil. * IS-IS routes advertised from ATE:port3 must have one next hop. * BGP routes advertised from ATE:port3 must have 2 next hops pointing to tunnels. +* For verifying prefix, nexthop groups, next hop use the leaves mentioed in the path section. * Verify afts prefix advertised by BGP,ISIS. * Verify its next hop group, number of next hop and its interfaces. * Verify the number of next hop is same as expected. @@ -79,7 +87,7 @@ Bring down both links between ATE:port1,port2 and DUT:port1,port2 ### Procedure -Bring up link between ATE:port1 and DUT:port1 +Bring up link between ATE:port1 and DUT:port1 using OTG api. ### Verifications @@ -87,6 +95,7 @@ Bring up link between ATE:port1 and DUT:port1 * IS-IS routes advertised from ATE:port3 must have one next hop. * BGP routes advertised from ATE:port3 must have 2 next hops pointing to tunnels. * Verify afts prefix advertised by BGP,ISIS. +* For verifying prefix, nexthop groups, next hop use the leaves mentioed in the path section. * Verify its next hop group, number of next hop and its interfaces. * Verify the number of next hop is same as expected. @@ -94,13 +103,14 @@ Bring up link between ATE:port1 and DUT:port1 ### Procedure -Bring up both link between ATE:port1,port2 and DUT:port1,port2 +Bring up both link between ATE:port1,port2 and DUT:port1,port2 using OTG api. ### Verifications * BGP routes advertised from ATE:port1,port2 must have 2 next hops. * IS-IS routes advertised from ATE:port3 must have one next hop. * BGP routes advertised from ATE:port3 must have 2 next hops pointing to tunnels. +* For verifying prefix, nexthop groups, next hop use the leaves mentioed in the path section. * Verify afts prefix advertised by BGP,ISIS. * Verify its next hop group, number of next hop and its interfaces. * Verify the number of next hop is same as expected. @@ -113,10 +123,7 @@ The below yaml defines the OC paths intended to be covered by this test. OC pat paths: ## Config Paths ## - /network-instances/network-instance/protocols/protocol/bgp/global/config/as: - /network-instances/network-instance/protocols/protocol/isis/global/config/instance-id: - - + ## State Paths ## /network-instances/network-instance/afts/ethernet/mac-entry/state/next-hop-group: diff --git a/feature/aft/aft_base/otg_tests/aft_prefixcounters/README.md b/feature/aft/aft_base/otg_tests/aft_prefixcounters/README.md index 9ca656206af..924d611edda 100644 --- a/feature/aft/aft_base/otg_tests/aft_prefixcounters/README.md +++ b/feature/aft/aft_base/otg_tests/aft_prefixcounters/README.md @@ -4,6 +4,10 @@ IPv4/IPv6 prefix counters +## Testbed + +* atedut_12.binding + ## Test Setup ### Generate DUT and ATE Configuration @@ -17,50 +21,24 @@ Establish eBGP sessions between ATE:port1 and DUT:port1. * Configure eBGP over the interface ip. * Advertise 1000 ipv4,ipv6 prefixes from ATE port1 observe received prefixes at DUT. -## Procedure +### Procedure * Gnmi set with REPLACE option to push the configuration DUT. * ATE configuration must be pushed. -## verifications +### verifications * BGP routes advertised from ATE:port1 must have 1 nexthop. * IS-IS routes advertised from ATE:port1 must have one next hop. * Use gnmi Subscribe with ON_CHANGE option to /network-instances/network-instance/afts. -* Verify afts prefix entries using the following paths with in a period of 30s. +* Verify afts prefix entries using the following paths with in a timeout of 30s. /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/prefix, /network-instances/network-instance/afts/ipv6-unicast/ipv6-entry/state/prefix -## AFT-2.1.1: AFT Prefix Counters ipv4 packets forwarded, IS-IS route. - -### Procedure - -From ATE:port2 send 10000 packets to one of the ipv4 prefix advertise by IS-IS. - -### Verifications - -* Before the traffic measure the initial counter value. -* After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv4 forwarded packet counter entries using the path mentioned in the paths section of this test plan. - -## AFT-2.1.2: AFT Prefix Counters ipv4 packets forwarded, BGP route. - -### Procedure - -From ATE:port2 send 10000 packets to one of the ipv4 prefix advertise by BGP. - -### Verifications - -* Before the traffic measure the initial counter value. -* After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv4 forwarded packet counter entries using the path mentioned in the paths section of this test plan. - -## AFT-2.1.3: AFT Prefix Counters ipv4 octets forwarded, IS-IS route. +## AFT-2.1.1: AFT Prefix Counters ipv4 packets forwarded, ipv4 octets forwarded IS-IS route. ### Procedure @@ -70,11 +48,10 @@ From ATE:port2 send 10000 packets to one of the ipv4 prefix advertise by IS-IS. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv4 forwarded octets counter entries using the path mentioned in the paths section of this test plan. +* The difference between final and initial value must match with the counter value in ATE then the test is marked as passed. +* Verify afts ipv4 forwarded packets and ipv4 forwarded octets counter entries using the path mentioned in the paths section of this test plan. - -## AFT-2.1.4: AFT Prefix Counters ipv4 octets forwarded, BGP route. +## AFT-2.1.2: AFT Prefix Counters ipv4 packets forwarded, ipv4 octets forwarded BGP route. ### Procedure @@ -84,38 +61,11 @@ From ATE:port2 send 10000 packets to one of the ipv4 prefix advertise by BGP. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv4 forwarded octets counter entries using the path mentioned in the paths section of this test plan. - -## AFT-2.1.5: AFT Prefix Counters ipv6 packets forwarded, IS-IS route. - -### Procedure - -From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by IS-IS. +* The difference between final and initial value must match with the counter value in ATE, then the test is marked as passed. +* Verify afts ipv4 forwarded packets and ipv4 forwarded octets counter entries using the path mentioned in the paths section of this test plan. -### Verifications - -* Before the traffic measure the initial counter value. -* After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv6 forwarded packet counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.6: AFT Prefix Counters ipv6 packets forwarded, BGP route. - -### Procedure - -From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. - -### Verifications - -* Before the traffic measure the initial counter value. -* After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv6 forwarded packet counter entries using the path mentioned in the paths section of this test plan. - - - -## AFT-2.1.7: AFT Prefix Counters ipv6 octets forwarded, IS-IS route. +## AFT-2.1.3: AFT Prefix Counters ipv6 packets forwarded, ipv6 octets forwarded IS-IS route. ### Procedure @@ -125,11 +75,10 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by IS-IS. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv6 forwarded octets counter entries using the path mentioned in the paths section of this test plan. - +* The difference between final and initial value must match with the counter value in ATE, then the test is marked as passed. +* Verify afts ipv6 forwarded packets and ipv6 forwarded octets counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.8: AFT Prefix Counters ipv6 octets forwarded, BGP route. +## AFT-2.1.4: AFT Prefix Counters ipv6 packets forwarded, ipv6 octets forwarded BGP route. ### Procedure @@ -139,10 +88,10 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. -* Verify afts ipv6 forwarded octets counter entries using the path mentioned in the paths section of this test plan. +* The difference between final and initial value must match with the counter value in ATE, then the test is marked as passed. +* Verify afts ipv6 forwarded packets and ipv6 forwarded octets counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.9: AFT Prefix Counters withdraw the ipv4 prefix. +## AFT-2.1.5: AFT Prefix Counters withdraw the ipv4 prefix. ### Procedure @@ -152,10 +101,10 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. ### Verifications -* The counters must not send incremental value as the prefix is not present in RIB/FIB. +* The counters must not send incremental value as the prefix is not present in RIB/FIB. The test fails if the counter shows incremental values. * Verify afts ipv4 forwarded packet counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.10: AFT Prefix Counters add the ipv4 prefix back. +## AFT-2.1.6: AFT Prefix Counters add the ipv4 prefix back. ### Procedure @@ -167,10 +116,10 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. +* The difference between final and initial value must match with the counter value in ATE, then the test is marked as passed. * Verify afts counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.11: AFT Prefix Counters withdraw the ipv6 prefix. +## AFT-2.1.7: AFT Prefix Counters withdraw the ipv6 prefix. ### Procedure @@ -180,10 +129,10 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. ### Verifications -* The counters must not send incremental value as the prefix is not present in RIB/FIB. +* The counters must not send incremental value as the prefix is not present in RIB/FIB. The test fails if the counter shows incremental values. * Verify afts counter entries using the path mentioned in the paths section of this test plan. -## AFT-2.1.12: AFT Prefix Counters add the ipv6 prefix back. +## AFT-2.1.8: AFT Prefix Counters add the ipv6 prefix back. ### Procedure @@ -195,7 +144,7 @@ From ATE:port2 send 10000 packets to one of the ipv6 prefix advertise by BGP. * Before the traffic measure the initial counter value. * After the traffic measure the final counter value. -* The difference between final and initial value must match with the counter value in ATE. +* The difference between final and initial value must match with the counter value in ATE, then the test is marked as passed. * Verify afts counter entries using the path mentioned in the paths section of this test plan. ## OpenConfig Path and RPC Coverage