mirror of
https://git.proxmox.com/git/mirror_frr
synced 2026-02-01 21:16:47 +00:00
bad029e92d
In scaled EVPN route sync from bgp to zebra, return code can be ZCLIENT_SEND_BUFFERED which was treated as error and leads to route install/uninstall failure. Following error logs were seen: 2023-07-07T17:05:59.640899+03:00 vtep12 bgpd[15305]: [WYBZ0-MM8F1][EC 33554471] 0: Failed to uninstall EVPN IMET route in VNI 478 2023-07-07T17:05:59.640913+03:00 vtep12 bgpd[15305]: [Y5VKN-9BV7H][EC 33554471] default (0): Failed to uninstall EVPN [3]:[0]:[32]:[27.0.0.5] route from VNI 465 IP table 2023-07-07T17:05:59.640927+03:00 vtep12 bgpd[15305]: [WYBZ0-MM8F1][EC 33554471] 0: Failed to uninstall EVPN IMET route in VNI 465 2023-07-07T17:05:59.640940+03:00 vtep12 bgpd[15305]: [Y5VKN-9BV7H][EC 33554471] default (0): Failed to uninstall EVPN [3]:[0]:[32]:[27.0.0.5] route from VNI 173 IP table Ticket:#3499957 Testing Done: Before fix: root@vtep12:mgmt:/home/cumulus# bridge -d -s fdb show | grep 27.0.0.5 | wc -l 16010 Once source VTEP withdraws, DUT VTEP still has stale entries root@vtep12:mgmt:~# bridge -d -s fdb show | grep 27.0.0.5 | wc -l 12990 After fix: Once source VTEP withdraws, DUT VTEP still is able to delete entries root@vtep12:mgmt:/home/cumulus# bridge -d -s fdb show | grep 27.0.0.5 | wc -l 0 Zapi stats: Client: bgp [32/133] ------------------------ FD: 76 Connect Time: 00:26:17 Nexthop Registry Time: 00:26:11 Nexthop Last Update Time: 00:23:31 Client will Not be notified about it's routes status Last Msg Rx Time: 00:21:33 Last Msg Tx Time: 00:23:31 Last Rcvd Cmd: ZEBRA_REMOTE_MACIP_ADD Last Sent Cmd: ZEBRA_NEXTHOP_UPDATE Type Add Update Del ================================================== IPv4 7 0 1 IPv6 0 0 0 Redist:v4 22 0 0 Redist:v6 0 0 0 VRF 2 0 0 Connected 4170 0 0 Interface 9 0 4 Intf Addr 2166 0 0 BFD peer 0 0 0 NHT v4 2 0 1 NHT v6 4 0 0 VxLAN SG 0 0 0 VNI 1010 0 0 L3-VNI 0 0 0 MAC-IP 46010 0 0 ES 2024 0 0 ES-EVI 0 0 0 Errors: 0 Signed-off-by: Chirag Shah <chirag@nvidai.com> |
||
|---|---|---|
| .github | ||
| alpine | ||
| babeld | ||
| bfdd | ||
| bgpd | ||
| debian | ||
| doc | ||
| docker | ||
| eigrpd | ||
| fpm | ||
| gdb | ||
| grpc | ||
| include | ||
| isisd | ||
| ldpd | ||
| lib | ||
| m4 | ||
| mgmtd | ||
| mlag | ||
| nhrpd | ||
| ospf6d | ||
| ospfclient | ||
| ospfd | ||
| pathd | ||
| pbrd | ||
| pceplib | ||
| pimd | ||
| pkgsrc | ||
| python | ||
| qpb | ||
| redhat | ||
| ripd | ||
| ripngd | ||
| sharpd | ||
| snapcraft | ||
| staticd | ||
| tests | ||
| tools | ||
| vrrpd | ||
| vtysh | ||
| watchfrr | ||
| yang | ||
| zebra | ||
| .clang-format | ||
| .dockerignore | ||
| .flake8 | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .isort.cfg | ||
| .pylintrc | ||
| .travis.yml | ||
| bootstrap.sh | ||
| buildtest.sh | ||
| config.version.in | ||
| configure.ac | ||
| COPYING | ||
| Makefile.am | ||
| README.md | ||
| stamp-h.in | ||
| version.h | ||
FRRouting
FRR is free software that implements and manages various IPv4 and IPv6 routing protocols. It runs on nearly all distributions of Linux and BSD and supports all modern CPU architectures.
FRR currently supports the following protocols:
- BGP
- OSPFv2
- OSPFv3
- RIPv1
- RIPv2
- RIPng
- IS-IS
- PIM-SM/MSDP
- LDP
- BFD
- Babel
- PBR
- OpenFabric
- VRRP
- EIGRP (alpha)
- NHRP (alpha)
Installation & Use
For source tarballs, see the releases page.
For Debian and its derivatives, use the APT repository at https://deb.frrouting.org/.
Instructions on building and installing from source for supported platforms may be found in the developer docs.
Once installed, please refer to the user guide for instructions on use.
Community
The FRRouting email list server is located here and offers the following public lists:
| Topic | List |
|---|---|
| Development | dev@lists.frrouting.org |
| Users & Operators | frog@lists.frrouting.org |
| Announcements | announce@lists.frrouting.org |
For chat, we currently use Slack. You can join by clicking the "Slack" link under the Participate section of our website.
Contributing
FRR maintains developer's documentation which contains the project workflow and expectations for contributors. Some technical documentation on project internals is also available.
We welcome and appreciate all contributions, no matter how small!
Security
To report security issues, please use our security mailing list:
security [at] lists.frrouting.org