4a7aa2634f
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> |
||
|---|---|---|
| .. | ||
| base_image_files | ||
| frr | ||
| .dockerignore | ||
| bgp_regex.json | ||
| docker_init.sh | ||
| Dockerfile.j2 | ||
| events_info.json | ||
| snmp.conf | ||
| TS | ||
| TSA | ||
| TSB | ||
| TSC | ||
| vtysh.conf | ||
| zsocket.sh | ||