Starting EOS 4.22.1F (https://eos.arista.com/eos-4-22-1f/general-router-id/) we support to set global router-id which can inherited to all BGP VRFs. Currently, AVD add router-id knob per VRF, which is suboptimal comparing to single global router-id config.
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Less config within VRF, best practice from EOS perspective
Describe the solution you would like
Add eos-designs variable to enable using router general router-id ipv4 knob
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
[X] I agree to follow this project's Code of Conduct
Enhancement summary
Starting EOS 4.22.1F (https://eos.arista.com/eos-4-22-1f/general-router-id/) we support to set global router-id which can inherited to all BGP VRFs. Currently, AVD add router-id knob per VRF, which is suboptimal comparing to single global router-id config.
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Less config within VRF, best practice from EOS perspective
Describe the solution you would like
Add eos-designs variable to enable using router general router-id ipv4 knob
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide