sonic-buildimage/dockers/docker-fpm-frr/frr/zebra/zebra.conf.j2

!
{% block banner %}
! =========== Managed by sonic-cfggen DO NOT edit manually! ====================
! generated by templates/zebra/zebra.conf.j2 using config DB data
! file: zebra.conf
!
{% endblock banner %}
!
{% block fpm %}
! Uses the old known FPM behavior of including next hop information in the route (e.g. RTM_NEWROUTE) messages
no fpm use-next-hop-groups
!
fpm address 127.0.0.1
{% endblock fpm %}
!
{% include "common/daemons.common.conf.j2" %}
!
{% include "zebra.interfaces.conf.j2" %}
!
[docker-frr]: bring quagga docker features to frr docker (#2870) - use superviord to manage process in frr docker - intro separated configuration mode for frr - bring quagga configuration template to frr. Signed-off-by: Guohan Lu <gulv@microsoft.com> 2019-05-09 01:00:49 -05:00			`!`
			`{% block banner %}`
			`! =========== Managed by sonic-cfggen DO NOT edit manually! ====================`
[bgpcfgd]: Split one bgp mega-template to chunks. (#4143) The one big bgp configuration template was splitted into chunks. Currently we have three types of bgp neighbor peers: general bgp peers. They are represented by CONFIG_DB::BGP_NEIGHBOR table entries dynamic bgp peers. They are represented by CONFIG_DB::BGP_PEER_RANGE table entries monitors bgp peers. They are represented by CONFIG_DB::BGP_MONITORS table entries This PR introduces three templates for each peer type: bgp policies: represent policieas that will be applied to the bgp peer-group (ip prefix-lists, route-maps, etc) bgp peer-group: represent bgp peer group which has common configuration for the bgp peer type and uses bgp routing policy from the previous item bgp peer-group instance: represent bgp configuration, which will be used to instatiate a bgp peer-group for the bgp peer-type. Usually this one is simple, consist of the referral to the bgp peer-group, bgp peer description and bgp peer ip address. This PR redefined constant.yml file. Now this file has a setting for to use or don't use bgp_neighbor metadata. This file has more parameters for now, which are not used. They will be used in the next iteration of bgpcfgd. Currently all tests have been disabled. I'm going to create next PR with the tests right after this PR is merged. I'm going to introduce better bgpcfgd in a short time. It will include support of dynamic changes for the templates. FIX:: #4231 2020-04-23 11:42:22 -05:00			`! generated by templates/zebra/zebra.conf.j2 using config DB data`
[docker-frr]: bring quagga docker features to frr docker (#2870) - use superviord to manage process in frr docker - intro separated configuration mode for frr - bring quagga configuration template to frr. Signed-off-by: Guohan Lu <gulv@microsoft.com> 2019-05-09 01:00:49 -05:00			`! file: zebra.conf`
			`!`
			`{% endblock banner %}`
			`!`
[FRR] Switch to dplane_fpm_nl plugin instead of fpm (#12852) Why I did it dplane_fpm_nl is a new FPM implementation in FRR. The old plugin fpm will not have any new features implemented. Usage of the new plugin gives us ability to use BGP suppression feature and next hop groups in the future. How I did it Switch to dplane_fpm_nl zebra plugin from old fpm plugin which is not supported anymore Remove stale patches for old fpm plugin and add similar patches for dplane_fpm_nl How to verify it Build and run on the switch. Signed-off-by: Stepan Blyschak <stepanb@nvidia.com> 2023-02-06 11:38:39 -06:00			`{% block fpm %}`
			`! Uses the old known FPM behavior of including next hop information in the route (e.g. RTM_NEWROUTE) messages`
			`no fpm use-next-hop-groups`
			`!`
			`fpm address 127.0.0.1`
			`{% endblock fpm %}`
			`!`
[bgpcfgd]: Split one bgp mega-template to chunks. (#4143) The one big bgp configuration template was splitted into chunks. Currently we have three types of bgp neighbor peers: general bgp peers. They are represented by CONFIG_DB::BGP_NEIGHBOR table entries dynamic bgp peers. They are represented by CONFIG_DB::BGP_PEER_RANGE table entries monitors bgp peers. They are represented by CONFIG_DB::BGP_MONITORS table entries This PR introduces three templates for each peer type: bgp policies: represent policieas that will be applied to the bgp peer-group (ip prefix-lists, route-maps, etc) bgp peer-group: represent bgp peer group which has common configuration for the bgp peer type and uses bgp routing policy from the previous item bgp peer-group instance: represent bgp configuration, which will be used to instatiate a bgp peer-group for the bgp peer-type. Usually this one is simple, consist of the referral to the bgp peer-group, bgp peer description and bgp peer ip address. This PR redefined constant.yml file. Now this file has a setting for to use or don't use bgp_neighbor metadata. This file has more parameters for now, which are not used. They will be used in the next iteration of bgpcfgd. Currently all tests have been disabled. I'm going to create next PR with the tests right after this PR is merged. I'm going to introduce better bgpcfgd in a short time. It will include support of dynamic changes for the templates. FIX:: #4231 2020-04-23 11:42:22 -05:00			`{% include "common/daemons.common.conf.j2" %}`
[docker-frr]: bring quagga docker features to frr docker (#2870) - use superviord to manage process in frr docker - intro separated configuration mode for frr - bring quagga configuration template to frr. Signed-off-by: Guohan Lu <gulv@microsoft.com> 2019-05-09 01:00:49 -05:00			`!`
[bgpcfgd]: Split default bgp config into main config and peer template (#3627) Now it's possible to add and remove peers based on ConfigDB - What I did Fixed functionality for dynamically adding/removing static bgp peers. - How I did it Split the bgp default template on bgp part and bgp peer part Changed bgpcfgd to use 1. - How to verify it Build an image and run on your DUT 2019-10-24 09:35:14 -05:00			`{% include "zebra.interfaces.conf.j2" %}`
[sonic-cfggen][FRR] Support T2 chassis frontend (#3100) 2019-07-08 19:32:20 -05:00			`!`