![]() In networking restart event, l3vni (vxlan) interface followed by associated vrf interfaces go down/deleted. L3vni (oper) down event (from zebra to bgp) triggers to clean up/un-import evpn routes (one-by-one) from the vrf table, zebra internally removes the route entry from nexthop and RMAC hash. When all the routes references in nexthop and RMAC db removed, both (nexthop/rmac) are suppose to be uninstalled from the bridge fdb and neigh table. While evpn routes removal in progress, a vrf disable event removes l3vni to its vrf association. Subsequent bgp to evpn routes removal does not clean up thus evpn routes reference to nexthop and RMAC remains in zebra hash. bridge fdb and neigh tables are flushed out since networking restart brings down all interfaces which results in flush of fdb and neigh tables. By product is the zebra does not install nexthop and rmac when routes are re-imported into vrf in VNI/VRF up event. The fix is in vrf disable event to flush all l3vni's nexthop and rmac db. Ticket:CM-30338 Reviewed By:CCR-10489 Testing Done: Performed multiple networking restart and checked neigh and bridge fdb tables for respective nexthop and router mac entry programmed. Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com> |
||
---|---|---|
.github | ||
alpine | ||
babeld | ||
bfdd | ||
bgpd | ||
debian | ||
doc | ||
docker | ||
eigrpd | ||
fpm | ||
gdb | ||
grpc | ||
include | ||
isisd | ||
ldpd | ||
lib | ||
m4 | ||
mlag | ||
nhrpd | ||
ospf6d | ||
ospfclient | ||
ospfd | ||
pbrd | ||
pimd | ||
pkgsrc | ||
python | ||
qpb | ||
redhat | ||
ripd | ||
ripngd | ||
sharpd | ||
snapcraft | ||
solaris | ||
staticd | ||
tests | ||
tools | ||
vrrpd | ||
vtysh | ||
watchfrr | ||
yang | ||
zebra | ||
.clang-format | ||
.dir-locals.el | ||
.dockerignore | ||
.gitignore | ||
bootstrap.sh | ||
buildtest.sh | ||
changelog-auto.in | ||
config.version.in | ||
configure.ac | ||
COPYING | ||
COPYING-LGPLv2.1 | ||
Makefile.am | ||
README.md | ||
stamp-h.in |
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 as well as Solaris 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