abdosi 6d767e549d [chassis] Support advertisement of Loopback0 of all LC's across all e-BGP peers in TSA mode (#16714) (#17837) ... What I did: In Chassis TSA mode Loopback0 Ip's of each LC's should be advertise through e-BGP peers of each remote LC's How I did: - Route-map policy to Advertise own/self Loopback IP to other internal iBGP peers with a community internal_community as define in constants.yml - Route-map policy to match on above internal_community when route is received from internal iBGP peers and set a internal tag as define in constants.yml and also delete the internal_community so we don't send to any of e-BGP peers - In TSA new route-map match on above internal tag and permit the route (Loopback0 IP's of remote LC's) and set the community to traffic_shift_community. - In TSB delete the above new route-map. How I verify: Manual Verification UT updated. sonic-mgmt PR: sonic-net/sonic-mgmt#10239 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>		2024-01-19 12:53:26 +08:00
..
instance.conf.j2	[chassis][bgp] create v4 and v6 peer group for VoQ internal neighbors (#9693)	2022-02-24 11:21:26 -08:00
peer-group.conf.j2	[chassis/multi-asic] Enable Sending BGP Community over internal neighbors over iBGP Session (#16705)	2023-11-18 12:34:04 +08:00
policies.conf.j2	[chassis] Support advertisement of Loopback0 of all LC's across all e-BGP peers in TSA mode (#16714) (#17837)	2024-01-19 12:53:26 +08:00