Skip to content

[bgp quagga] increase BGP graceful restart timeout to 240 seconds#2754

Merged
lguohan merged 1 commit intosonic-net:masterfrom
yxieca:quagga
Apr 11, 2019
Merged

[bgp quagga] increase BGP graceful restart timeout to 240 seconds#2754
lguohan merged 1 commit intosonic-net:masterfrom
yxieca:quagga

Conversation

@yxieca
Copy link
Copy Markdown
Contributor

@yxieca yxieca commented Apr 8, 2019

- What I did

There are some platforms with less powerful CPU/hard-drive could take
longer to get ready for BGP. For these platforms, 240 seconds would be
a safer threshold.

Signed-off-by: Ying Xie ying.xie@microsoft.com

There are some platforms with less powerful CPU/hard-drive could take
longer to get ready for BGP. For these platforms, 240 seconds would be
a safer threshold.

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
bgp bestpath as-path multipath-relax
no bgp default ipv4-unicast
bgp graceful-restart restart-time 180
bgp graceful-restart restart-time 240
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per your description of the PR, it seems we are accommodating the value for some particular HW. I would think it is better to make it as a configurable item in minigraph/configDB. If not configured, the default is still 180, but on some particular platforms, we can increase the timer value.

@lguohan lguohan merged commit af64fd6 into sonic-net:master Apr 11, 2019
@yxieca yxieca deleted the quagga branch April 13, 2019 00:48
yxieca added a commit that referenced this pull request Apr 16, 2019
)

There are some platforms with less powerful CPU/hard-drive could take
longer to get ready for BGP. For these platforms, 240 seconds would be
a safer threshold.

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
mihirpat1 pushed a commit to mihirpat1/sonic-buildimage that referenced this pull request Jun 14, 2023
…age if lag menber will be added to LAG after binding (sonic-net#2754)

* Dual-ToR][ACL] bind LAG to ACL table in order to guarantee rule coverage if lag menber will be added to LAG after binding (sonic-net#2754)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants