frr daemon can start with a full configuration file

[gbcbooks]

as you can see , my frr.conf has more than 50,000 static route save in it,

root@mia:/etc/frr# cat frr.conf | grep "ip route" | wc -l
53716

but when i start frr service and login to vtysh , command "show running-config", from the final end

ip route 199.245.224.0/24 192.168.1.1 217
ip route 199.245.225.0/24 192.168.1.1 217
ip route 199.245.226.0/24 192.168.1.1 217
ip route 199.245.227.0/24 192.168.1.1 217
ip route 199.245.230.0/24 192.168.1.1 217
ip route 199.245.231.0/24 192.168.1.1 217
ip route 199.245.232.0/24 192.168.1.1 217
ip route 10.174.131.110/32 192.168.1.1
ip route 45.32.49.128/32 192.168.1.1
ip route 139.196.29.57/32 192.168.1.1 10
ip route 192.168.0.1/32 192.168.1.1
ip route 192.168.4.4/32 192.168.1.1
ip route 192.168.100.254/32 192.168.1.1
!
end
mia.hostname.org 

as you can see , it juse load a very part of my configuration , i compared with my full configuration , frr only load 26255 lines from frr.conf

is this a frr limitation ? this whole full configuraion can run property in quagga.

[ton31337]

which version?

[ton31337]

I will check next week when having more time.

[gbcbooks]

thank you so much , i need it very much

[ton31337]

According to the logs, you have to use the latest version of FRR (it has a fix for watchfrr). To workaround in 8.1 and, etc. please increase watchfrr timeout like:

# grep watch /etc/frr/daemons 
# The watchfrr and zebra daemons are always started.
# The list of daemons to watch is automatically generated by the init script.
watchfrr_options="-T 120"

[ton31337]

Or you can check this branch #12351, it fixes your issue basically.

[gbcbooks]

thks vey much , i'll test it later and give you response