Replies: 1 comment
Considering that every platform also has different defaults, and that a different (sub)set of timers are configurable on different platforms, I would say this is not worth solving. Engineers who want to have consistent timers across multiple vendors can always use custom config templates, and there are beautiful mechanisms to implement them in multi-vendor environment. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There is currently a wide variety in timer settings:
FRR OSPF timers are set here:
netlab/netsim/ansible/templates/ospf/frr.ospfv2.j2
Line 22 in 1cb846e
EOS has:
netlab/netsim/ansible/templates/ospf/eos.ospfv2.j2
Line 21 in 1cb846e
and most platforms use their (more conservative) defaults. Similar for ISIS and BGP,
e.g. FRR has
netlab/netsim/ansible/templates/initial/frr.j2
Line 169 in 1cb846e
but SR Linux uses
netlab/netsim/ansible/templates/bgp/srlinux.macro.j2
Line 175 in 1cb846e
and I couldn't find any specific EOS settings.
Perhaps it would be good to harmonize these settings, i.e. define an object model with parameters and use those?
All reactions