judyjoseph 902ad1357a To decrease the Connect Retry Timer from default value which is 120sec to 10 sec. (#7087) ... Why I did it It was observed that on a multi-asic DUT bootup, the BGP internal sessions between ASIC's was taking more time to get ESTABLISHED than external BGP sessions. The internal sessions was coming up almost exactly 120 secs later. In multi-asic platform the bgp dockers ( which is per ASIC ) on switch start are bring brought up around the same time and they try to make the bgp sessions with neighbors (in peer ASIC's) which may be not be completely up. This results in BGP connect fail and the retry happens after 120sec which is the default Connect Retry Timer How I did it Add the command to set the bgp neighboring session retry timer to 10sec for internal bgp neighbors.		2021-03-26 17:39:50 +00:00
..
templates	To decrease the Connect Retry Timer from default value which is 120sec to 10 sec. (#7087)	2021-03-26 17:39:50 +00:00
tsa	[bgpcfgd]: Support default action for "Allow prefix" feature (#6370)	2021-01-09 08:29:19 -08:00
bgpd.conf.j2	[bgpcfgd]: Split one bgp mega-template to chunks. (#4143)	2020-04-23 09:42:22 -07:00
bgpd.main.conf.j2	FRR 7.5	2020-12-29 03:44:49 -08:00
bgpd.spine_chassis_frontend_router.conf.j2	[cfggen] Make Jinja2 Template Python 3 Compatible	2020-09-30 07:07:43 -07:00
gen_bgpd.conf.j2	[frrcfgd] introduce frrcfgd to manage frr config when frr_mgmt_framework_config is true (#5142)	2021-01-24 22:43:30 -08:00