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

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

[Julien OHAYON]

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.

Is it possible to keep it enabled? If yes, in which configuration file?

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?

Thanks in advance.

Julien OHAYON
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

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

[Stefan Hanreich]

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

Re: [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@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
> 
> 

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

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

[Stefan Hanreich]

On 10/7/25 5:58 PM, Julien OHAYON wrote:
> 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.

Ah sorry, I was only thinking of the upgrade process itself. In your
particular scenario (having an EVPN zone configured as well) I'm afraid
there's currently no easy way of preventing the daemons file from
getting overwritten by the SDN module.

The defaults are set in the frr config generation module [1] and
currently not overridable. I guess we'd have to expose a way of setting
the default value for those daemons to 1 instead of 0.

Another way would be trying to detect if the status of the daemons needs
to change compared to the previous SDN configuration and only re-write
the daemons file in the case it really *needs* to change instead of
every time. But that is probably a bit more tricky.

Could you open a feature request on our Bugzilla?

[1]
https://git.proxmox.com/?p=pve-network.git;a=blob;f=src/PVE/Network/SDN/Frr.pm;h=b607b32c248db1147b458fbfe3f32a94297d2c53;hb=HEAD#l117


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

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

[Julien OHAYON]

Maybe I’m overcomplicating things and there’s actually a much simpler solution.

My concern is during the migration: if I configure OSPF on a node running v9, will this have an impact on the nodes still running v8?



I’m referring to the entire FRR part about OSPF.



Thanks


> Le 8 oct. 2025 à 11:34, Stefan Hanreich <s.hanreich@proxmox.com> a écrit :
> 
> On 10/7/25 5:58 PM, Julien OHAYON wrote:
>> 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.
> 
> Ah sorry, I was only thinking of the upgrade process itself. In your
> particular scenario (having an EVPN zone configured as well) I'm afraid
> there's currently no easy way of preventing the daemons file from
> getting overwritten by the SDN module.
> 
> The defaults are set in the frr config generation module [1] and
> currently not overridable. I guess we'd have to expose a way of setting
> the default value for those daemons to 1 instead of 0.
> 
> Another way would be trying to detect if the status of the daemons needs
> to change compared to the previous SDN configuration and only re-write
> the daemons file in the case it really *needs* to change instead of
> every time. But that is probably a bit more tricky.
> 
> Could you open a feature request on our Bugzilla?
> 
> [1]
> https://git.proxmox.com/?p=pve-network.git;a=blob;f=src/PVE/Network/SDN/Frr.pm;h=b607b32c248db1147b458fbfe3f32a94297d2c53;hb=HEAD#l117
> 
> 

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user