search

FRRouting / frr

The FRRouting Protocol Suite
https://frrouting.org/
Other
3.19k stars 1.23k forks source link

EVPN-VXLAN not loading VNI definitions from config file on start #6082

Open RobertB93 opened 4 years ago

RobertB93 commented 4 years ago

Describe the bug When using EVPN with VXLAN, you could specify a custom route target for each vni in the evpn address family. This works when entering via cli and will also get saved to frr.conf. The issues arises once you stop and start frr again. The running config is complete, except the custom route target for vni defintions, they are missing.

running conf before frr service restart:

address-family l2vpn evpn
  neighbor EVPN activate
  vni 123
   route-target import 101:1
   route-target export 101:1
  exit-vni
  advertise-all-vni
 exit-address-family

running conf after frr service restart:

address-family l2vpn evpn
  neighbor EVPN activate
  vni 123
  exit-vni
  advertise-all-vni
 exit-address-family

However, once you got frr service running and have the route targets missing, you could still have them reinserted by issuing systemctl reload frr. This will result in the running config being corretly imported. So the workaround as of now is to start frr and then immediately reload it.

(put "x" in "[ ]" if you already tried following) [x] Did you check if this is a duplicate issue? [ ] Did you test it on the latest FRRouting/frr master branch?

To Reproduce Steps to reproduce the behavior:

  1. Stop frr via systemctl stop frr
  2. Start frr via systemctl start frr
  3. enter vtysh and show running config
  4. See the vni route target definition being gone

Expected behavior vni definitions should be loaded after restarting the service

Versions

aderumier commented 3 years ago

@RobertB93

I think it's because "advertise-all-vni" is defined after vni. It has been fixed in more recent release of frr.

BTW, I'm the maintenair of frr version in proxmox distro. Just curious, why do you use debian version and not proxmox version? (currently 7.2.1,but I'm planning to upgrade to last 7.4 stable branch)

RobertB93 commented 3 years ago

Hey, thanks for your reply, I will give it another try soon. I was experimenting using different versions after hitting this bug, just to make sure that it's not my local version that's causing it and thus confirmed it in the latest version at this time.

ton31337 commented 1 month ago

Is this still a bug in the latest releases?