From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Julien OHAYON <j.ohayon@xoxo.fr>
Subject: Re: [PVE-User] OSPF when migrating from v8 to v9
Date: Tue, 7 Oct 2025 15:52:17 +0200 [thread overview]
Message-ID: <fa7e21f2-1aaf-4d18-a3cf-46598a9543b4@proxmox.com> (raw)
In-Reply-To: <E8F46B6C-9048-4F41-A660-1524AC4F4C73@xoxo.fr>
On 10/7/25 8:17 AM, Julien OHAYON wrote:
> Hello,
>
> We are running version 8.4.1 and using SDN with EVPN. Since we already had OSPF in our infrastructure, we forced its activation through the configuration files and added some local configs. A few examples:
>
> in /etc/frr/daemons
>
> ospfd=yes
> and
> in /etc/frr/frr.conf.local
>
> router ospf
> redistribute connected
> redistribute static
> network X.X.X.X/24 area 0
> default-information originate
> exit
>
> However, with version 9, great news: it is now integrated. But for the migration, it’s not so simple. When we upgrade a node to v9, OSPF gets disabled in /etc/frr/daemons.
We ship the /etc/frr/daemons file via our FRR package, so if it gets
modified manually you should get a prompt on upgrade that asks whether
the modified file should be kept or not.
You can check if this is what happened by checking the term.log (or the
subsequent term.log.N.gz) file in /var/log/apt.
> Is it possible to keep it enabled? If yes, in which configuration file?
It should be kept enabled when choosing to keep the existing
configuration file as described above.
> Of course, afterwards it will be fine to modify the configuration via Proxmox, but what is the impact, especially if it doesn’t match the configuration we had manually applied?
As long as the additional manual configuration for OSPF is kept in
/etc/frr/frr.conf.local, then it will get merged on applying the SDN
configuration the same as before.
Kind Regards
Stefan
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-10-07 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:16 Julien OHAYON
2025-10-07 13:52 ` Stefan Hanreich [this message]
2025-10-07 15:58 ` Julien OHAYON
2025-10-08 9:34 ` Stefan Hanreich
2025-10-08 10:48 ` Julien OHAYON
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=fa7e21f2-1aaf-4d18-a3cf-46598a9543b4@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=j.ohayon@xoxo.fr \
--cc=pve-user@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.