[PVE-User] OSPF when migrating from v8 to v9

[Julien OHAYON]

Thanks for your reply. Unfortunately, when we apply the SDN configuration, it modifies the daemons file and sets it to “no”, since we haven’t configured OSPF directly in Proxmox. That’s the file I would like to prevent from being modified.



Cheers

Julien

> Le 7 oct. 2025 à 15:52, Stefan Hanreich <s.hanreich at proxmox.com> a écrit :
> 
> 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
> 
>