[DualToR] enforce same loopback ip and drop bgp pkts on loopback1 for dualtor (sonic-net#18766)

What is the motivation for this PR?
This PR updates the DualToR config to enforce the same loopback1 IP address for both ToRs.
Based on a recent Incident 628608070 : [SONiC RCA][SLB_DNC] Gemini Tors dropping vip traffic, we need to block BGP from being established on loopback1.

How did you do it?
Assign the same loopback1 IP to both ToRs.
Added an iptables rules to drop the packets sonic-net/sonic-host-services#262

How did you verify/test it?
Confirmed both ToRs used the same loopback1 IP, and verify the drop rule.

Signed-off-by: Yael Tzur <ytzur@nvidia.com>

Author: yyynini

ansible/vars/topo_cable-test.yml

@@ -93,10 +93,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1::34/128
-        - FC00:1::35/128
+        - FC00:1::34/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-120.yml

@@ -210,10 +210,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-56.yml

@@ -114,10 +114,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-64-breakout.yml

@@ -115,10 +115,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-64.yml

@@ -118,10 +118,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-aa-120.yml

@@ -267,10 +267,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-aa-56.yml

@@ -139,10 +139,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-aa-64-breakout.yml

@@ -139,10 +139,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-aa-64.yml

@@ -155,10 +155,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32

ansible/vars/topo_dualtor-aa.yml

@@ -91,10 +91,10 @@ topology:
     loopback1:
       ipv4:
         - 10.1.0.34/32
-        - 10.1.0.35/32
+        - 10.1.0.34/32
       ipv6:
         - FC00:1:0:34::/128
-        - FC00:1:0:35::/128
+        - FC00:1:0:34::/128
     loopback2:
       ipv4:
         - 10.1.0.36/32