15a39ac806
What I did: Fix the Loopback0 IPv6 address of LC's in chassis not reachable from peer devices. Why I did: For Ipv6 Loopback0 address we only advertise /64 subnet to the peer devices. However, in case of chassis each LC will have it own /128 address of that /64 subnet . Since this /128 address does not get advertised peer devices can-not ping/reach the LC's loopback0. How I fix: Advertise /128 Loopback0 Ipv6 address only between i-BGP peers. This way even though /64 is advertised to e-BGP peer devices when packet reaches any of LC's it can reach the appropriate LC's. How I verify: Manual verification UT added for same. 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 | ||