Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FRR][patch] Add encap type when building packet for FPM (sonic-net#1…
…7052) Back port a patch from upstream FRR - FRRouting/frr#14675 Why I did it The EVPN route is not treated correctly and thus leading to messages: Oct 30 11:40:00.494083 r-tigris-22 INFO swss#orchagent: :- addRoute: Failed to get next hop 30.0.0.2@Vlan200 for 20.0.0.2/32, resolving neighbor Oct 30 11:40:00.494083 r-tigris-22 INFO swss#orchagent: :- addRoute: Failed to get next hop 30.0.0.2@Vlan200 for 200.0.0.0/24, resolving neighbor Oct 30 11:40:00.494083 r-tigris-22 INFO swss#orchagent: :- addRoute: Failed to get next hop ::ffff:30.0.0.2@Vlan200 for 200::/64, resolving neighbor Oct 30 11:40:00.494083 r-tigris-22 INFO swss#orchagent: :- addRoute: Failed to get next hop ::ffff:30.0.0.2@Vlan200 for 20::/64, resolving neighbor Oct 30 11:40:00.494083 r-tigris-22 INFO swss#orchagent: :- addRoute: Failed to get next hop ::ffff:30.0.0.2@Vlan200 for 20::2/128, resolving neighbor This happens because fpmsyncd does not get encap type field in FPM message. Work item tracking Microsoft ADO (number only): How I did it Backport fix from FRR. How to verify it EVPN scenario.
- Loading branch information