Add multi asic

sonic-net · Feb 13, 2025 · 8d5bfc0 · 8d5bfc0
1 parent 3e7824d
commit 8d5bfc0
Showing 1 changed file with 53 additions and 4 deletions.
diff --git a/docs/testplan/BGP-Router-ID-test-plan.md b/docs/testplan/BGP-Router-ID-test-plan.md
@@ -20,7 +20,7 @@ The tests will include:
 
 ### Supported Topology
 
-Test cases should run on T0/T1/M0/Mx topology.
+Test cases should run on all topologies.
 
 ## Test Case
 
@@ -37,15 +37,17 @@ This module is to test BGP router ID in single asic.
 #### test_bgp_router_id_default
 
 * **Test objective**
-To test in default scenario (BGP router ID is not specified explicitly), BGP router ID would be set as IPv4 address of Loopback0.
+
+  To test in default scenario (BGP router ID is not specified explicitly), BGP router ID would be set as IPv4 address of Loopback0.
 
 * **Test detail**
   * `verify_bgp` to check BGP router ID and sessions status.
 
 #### test_bgp_router_id_set
 
 * **Test objective**
-To test when BGP router ID is set and Loopback0 IPv4 address is configured, BGP router ID would be set as router ID in CONFIG_DB rather than IPv4 address of Loopback0 and BGP would work well.
+
+  To test when BGP router ID is set and Loopback0 IPv4 address is configured, BGP router ID would be set as router ID in CONFIG_DB rather than IPv4 address of Loopback0 and BGP would work well.
 
 * **Setup**
   * Add BGP router ID to CONFIG_DB.
@@ -60,7 +62,8 @@ To test when BGP router ID is set and Loopback0 IPv4 address is configured, BGP
 #### test_bgp_router_id_set_without_loopback_ipv4
 
 * **Test objective**
-To test when BGP router ID is set and Loopback0 IPv4 address is not configured, BGP router ID would be set as router ID in CONFIG_DB and BGP would work well
+
+  To test when BGP router ID is set and Loopback0 IPv4 address is not configured, BGP router ID would be set as router ID in CONFIG_DB and BGP would work well
 
 * **Setup**
   * Add BGP router ID to CONFIG_DB.
@@ -73,3 +76,49 @@ To test when BGP router ID is set and Loopback0 IPv4 address is not configured,
 
 * **Test detail**
   * `verify_bgp` to check BGP router ID and sessions status.
+
+### Test module test_bgp_router_id_multi_asic.py
+This module is to test BGP router ID in multi asic.
+
+#### test_bgp_router_id_default
+
+* **Test objective**
+
+  To test in default scenario (BGP router ID is not specified explicitly), eBGP router ID would be set as IPv4 address of Loopback0 and iBGP router ID would be set as IPv4 address of Loopback4096.
+
+* **Test detail**
+  * `verify_bgp` to check iBGP and eBGP router ID and sessions status.
+
+#### test_bgp_router_id_set
+
+* **Test objective**
+
+  To test when BGP router ID is set and Loopback0 and Loopback4096 IPv4 address are configured, BGP router ID would be set as router ID in CONFIG_DB rather than IPv4 address of Loopback0 and BGP would work well.
+
+* **Setup**
+  * Add BGP router ID to CONFIG_DB of corresponding asic.
+  * Restart BGP container.
+* **Teardown**
+  * Remove BGP router ID in CONFIG_DB of corresponding asic.
+  * Restart BGP container.
+
+* **Test detail**
+  * `verify_bgp` to check BGP router ID and sessions status.
+
+#### test_bgp_router_id_set_without_loopback_ipv4
+
+* **Test objective**
+
+  To test when BGP router ID is set and Loopback0 and Loopback4096 IPv4 address are not configured, BGP router ID would be set as router ID in CONFIG_DB and BGP would work well
+
+* **Setup**
+  * Add BGP router ID to CONFIG_DB of corresponding asic.
+  * Remove IPv4 address of Loopback0 of corresponding asic.
+  * Restart BGP container.
+* **Teardown**
+  * Remove BGP router ID in CONFIG_DB of corresponding asic.
+  * Add IPv4 address of Loopback back of corresponding asic.
+  * Restart BGP container.
+
+* **Test detail**
+  * `verify_bgp` to check BGP router ID and sessions status.