You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the problem, these two instructions are exactly the same from the point of view of the vtysh:
pppoe-server(config-vrf)# ip route 10.0.0.0/8 blackhole tag 220 250
pppoe-server(config-vrf)# ip route 10.0.0.0/8 blackhole 250 tag 220
When you apply config frr-reload.py forms a temporary config to apply. It consists of two parts: one is to apply newly added instructions (first pass) and one to remove unnecessary instructions (second pass). In order to create temp config, frr-reload.py reads running config and applied config, and compares them.
The trick is that this instruction in running and applied config is written in different way. So, we apply the new one (from the config) and remove the old one (from the running config). But they are the same, so, at-the-end-of-a-day, we just remove it.
Also, this explains, why modifying applied config instruction helps. That's a nice workaround.
Description
Using
frr-reload.py
on every second reload of a VRF blackhole route with distance and tag applied it will vanish from vtysh.Version
stable/10.2
6cd056bHow to reproduce
Use
First reload the configuration which will add the route into the VRF block:
Now reload the same file again a second time - the route will be removed
Expected behavior
vtysh
configuration should be the same on every config reloadActual behavior
routing inconsitencies between individual
frr-reload
callsAdditional context
Changing the order of the reload configuration to
Will not remove the config
Checklist
The text was updated successfully, but these errors were encountered: