Closed onurgashi closed 3 years ago
no bgp default ipv4-unicast
is not hardcoded into the templates today, but is in the <type>_bgp_defaults
. If we remove the explicit enable/disable, the configuration may fail if <type>_bgp_defaults
was overridden without no bgp default ipv4-unicast
.
Issue Type
Is your feature request related to a problem? Please describe. Checking the EOS CLI standard behaviour and AVD there is redundant knobs for MPBGP where we explicitly disable peers/peer groups that are not meant to be part of the particular address-family.
By default with MPBGP we will not negotiate capability for any address-family that the peer is not defined, thus there is no need for us to explicitly do this so.
AVD
Describe the solution you'd like A clear and concise description of what you want to happen.
The following provides the exact same result
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
It's liveable but the more address-families we have the more no neighbours we will have which in the end the result is simpler with the above.
Additional context Add any other context or screenshots about the feature request here.