From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"s.hanreich@proxmox.com" <s.hanreich@proxmox.com>
Subject: Re: SPAM: Re: [RFC pve-network 1/1] sdn: apply changes on all nodes in parallel
Date: Tue, 22 Sep 2026 08:53:45 +0000 [thread overview]
Message-ID: <d62c5c581d3787b6ac10350337a0cf47a4d8eb1b.camel@groupe-cyllene.com> (raw)
In-Reply-To: <8425f301-48ac-4e24-b356-da38fcc4e686@proxmox.com>
quite possible that graceful restart was not implemented or buggy at
this time.
(I'm also using route reflectors on my arista core routers)
Le mardi 22 septembre 2026 à 10:47 +0200, Stefan Hanreich a écrit :
> On 9/22/26 10:45 AM, DERUMIER, Alexandre wrote:
> > Hi,
> >
> > could we have an option to enable/disable it ?
> >
> > I remember to have some flood with evpn && frr peering when
> > reloading
> > all nodes at same time in the past. (don't remember exactly on
> > which
> > change, but it was on frr side)
>
> Makes sense, was this with graceful restart enabled as well? But it
> doesn't hurt to make this opt-in! I remember there being a bug as
> well
> where graceful restart wasn't enabled all the time, so that might
> have
> been the problem as well?
next prev parent reply other threads:[~2026-09-22 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 14:06 [RFC pve-network 1/1] sdn: apply changes on all nodes in parallel Stefan Hanreich
2026-07-13 8:58 ` Daniel Herzig
2026-09-18 9:50 ` Gabriel Goller
2026-09-18 11:21 ` Stefan Hanreich
2026-09-18 11:28 ` Gabriel Goller
2026-09-21 10:56 ` DERUMIER, Alexandre
2026-09-22 8:47 ` SPAM: " Stefan Hanreich
2026-09-22 8:53 ` DERUMIER, Alexandre [this message]
2026-09-22 8:55 ` Stefan Hanreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d62c5c581d3787b6ac10350337a0cf47a4d8eb1b.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox