6d767e549d
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> |
||
|---|---|---|
| .. | ||
| docker-base | ||
| docker-base-bullseye | ||
| docker-base-buster | ||
| docker-base-stretch | ||
| docker-basic_router | ||
| docker-config-engine | ||
| docker-config-engine-bullseye | ||
| docker-config-engine-buster | ||
| docker-config-engine-stretch | ||
| docker-database | ||
| docker-dhcp-relay | ||
| docker-eventd | ||
| docker-fpm-frr | ||
| docker-fpm-gobgp | ||
| docker-iccpd | ||
| docker-lldp | ||
| docker-macsec | ||
| docker-mux | ||
| docker-nat | ||
| docker-orchagent | ||
| docker-pde | ||
| docker-platform-monitor | ||
| docker-ptf | ||
| docker-ptf-sai | ||
| docker-router-advertiser | ||
| docker-sflow | ||
| docker-snmp | ||
| docker-sonic-mgmt | ||
| docker-sonic-mgmt-framework | ||
| docker-sonic-p4rt | ||
| docker-sonic-restapi | ||
| docker-sonic-sdk | ||
| docker-sonic-sdk-buildenv | ||
| docker-sonic-telemetry | ||
| docker-swss-layer-bullseye | ||
| docker-swss-layer-buster | ||
| docker-teamd | ||
| dockerfile-macros.j2 | ||