My distro (Fedora 38) updated frr from 8.5.1 to 8.5.2 yesterday and upon restart of frr after that update, OSFP routing stopped working. It was working find prior to that. When I use vtysh to show the ospf route database: # show ip ospf database route % OSPF is not enabled in vrf default and indeed, the running config shows no OSPF configuration: # show running-config Building configuration... Current configuration: ! frr version 8.5.2 frr defaults traditional hostname pc.example.com no ipv6 forwarding no service integrated-vtysh-config ! end But my configuration files do configure ospf: ----- /etc/frr/daemons ----- bgpd=no ospfd=yes ospf6d=no ripd=no ripngd=no isisd=no pimd=no pim6d=no nhrpd=no eigrpd=no sharpd=no pbrd=no bfdd=no fabricd=no vrrpd=no pathd=no vtysh_enable=yes zebra_options=" -A 127.0.0.1 -s 90000000" bgpd_options=" -A 127.0.0.1" ospfd_options=" -A 127.0.0.1" ospf6d_options=" -A ::1" ripd_options=" -A 127.0.0.1" ripngd_options=" -A ::1" isisd_options=" -A 127.0.0.1" pimd_options=" -A 127.0.0.1" pim6d_options=" -A ::1" nhrpd_options=" -A 127.0.0.1" eigrpd_options=" -A 127.0.0.1" sharpd_options=" -A 127.0.0.1" pbrd_options=" -A 127.0.0.1" staticd_options="-A 127.0.0.1" bfdd_options=" -A 127.0.0.1" fabricd_options="-A 127.0.0.1" vrrpd_options=" -A 127.0.0.1" pathd_options=" -A 127.0.0.1" ----- /etc/frr/frr.conf ----- hostname pc.interlinx.bc.ca ----- /etc/frr/ospfd.conf ----- hostname pc password ospf4me enable password ospf4me ! router ospf ospf router-id 10.75.22.1 network 10.75.22.0/24 area 0 ! network 192.168.122.0/24 area 1 ! network 192.168.0.0/24 area 1 ! redistribute connected ----- /etc/frr/staticd.conf ----- ----- /etc/frr/vtysh.conf ----- no service integrated-vtysh-config ----- /etc/frr/zebra.conf ----- hostname pc password zebra enable password zebra log stdout interface pc_bridge link-detect interface virbr0 no link-detect This is the very same config that worked with 8.5.1 and is working on other machines in the network (albeit with earlier versions of frr as they are "EL8" systems which don't update as quickly as Fedora). Is there something about this configuration that is not compatible with 8.5.2? Cheers, b.
On 2023-07-11 10:41, Brian J. Murrell wrote:
My distro (Fedora 38) updated frr from 8.5.1 to 8.5.2 yesterday and upon restart of frr after that update, OSFP routing stopped working. It was working find prior to that.
When I use vtysh to show the ospf route database:
# show ip ospf database route % OSPF is not enabled in vrf default
and indeed, the running config shows no OSPF configuration:
# show running-config Building configuration...
Current configuration: ! frr version 8.5.2 frr defaults traditional hostname pc.example.com no ipv6 forwarding no service integrated-vtysh-config ! end
But my configuration files do configure ospf:
----- /etc/frr/daemons ----- bgpd=no ospfd=yes ospf6d=no ripd=no ripngd=no isisd=no pimd=no pim6d=no nhrpd=no eigrpd=no sharpd=no pbrd=no bfdd=no fabricd=no vrrpd=no pathd=no
vtysh_enable=yes zebra_options=" -A 127.0.0.1 -s 90000000" bgpd_options=" -A 127.0.0.1" ospfd_options=" -A 127.0.0.1" ospf6d_options=" -A ::1" ripd_options=" -A 127.0.0.1" ripngd_options=" -A ::1" isisd_options=" -A 127.0.0.1" pimd_options=" -A 127.0.0.1" pim6d_options=" -A ::1" nhrpd_options=" -A 127.0.0.1" eigrpd_options=" -A 127.0.0.1" sharpd_options=" -A 127.0.0.1" pbrd_options=" -A 127.0.0.1" staticd_options="-A 127.0.0.1" bfdd_options=" -A 127.0.0.1" fabricd_options="-A 127.0.0.1" vrrpd_options=" -A 127.0.0.1" pathd_options=" -A 127.0.0.1"
----- /etc/frr/frr.conf ----- hostname pc.interlinx.bc.ca ----- /etc/frr/ospfd.conf ----- hostname pc password ospf4me enable password ospf4me ! router ospf ospf router-id 10.75.22.1 network 10.75.22.0/24 area 0 ! network 192.168.122.0/24 area 1 ! network 192.168.0.0/24 area 1 ! redistribute connected ----- /etc/frr/staticd.conf ----- ----- /etc/frr/vtysh.conf ----- no service integrated-vtysh-config ----- /etc/frr/zebra.conf ----- hostname pc password zebra enable password zebra log stdout
interface pc_bridge link-detect
interface virbr0 no link-detect
This is the very same config that worked with 8.5.1 and is working on other machines in the network (albeit with earlier versions of frr as they are "EL8" systems which don't update as quickly as Fedora).
Is there something about this configuration that is not compatible with 8.5.2?
Have you tried putting the contents of /etc/frr/ospfd.conf in /etc/frr/frr.conf ?
Cheers, b.
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
On Tue, 2023-07-11 at 17:51 -0300, Patrick Boutilier wrote:
On 2023-07-11 10:41, Brian J. Murrell wrote:
no service integrated-vtysh-config
Have you tried putting the contents of /etc/frr/ospfd.conf in /etc/frr/frr.conf ?
I had not and indeed, that does resolve the issue. However: 1. Doesn't `no service integrated-vtysh-config` mean that each daemon read's it's own config file (I.e. as I have configured it) and as such I should not need to put the ospfd.conf into frr.conf? 2. If yes to the above and 8.5.2 is discontinuing `no service integrated-vtysh-config`, is that something that should happen in a bugfix release? 3. If `no service integrated-vtysh-config` is being discontinued, wouldn't it be good if frr emitted an error to the effect that it is discontinued yet still specified in the configuration -- alerting users that it will no longer work as they expect? Cheers, b.
On 2023-07-12 08:59, Brian J. Murrell wrote:
On Tue, 2023-07-11 at 17:51 -0300, Patrick Boutilier wrote:
On 2023-07-11 10:41, Brian J. Murrell wrote:
no service integrated-vtysh-config
Have you tried putting the contents of /etc/frr/ospfd.conf in /etc/frr/frr.conf ?
I had not and indeed, that does resolve the issue. However:
1. Doesn't `no service integrated-vtysh-config` mean that each daemon read's it's own config file (I.e. as I have configured it) and as such I should not need to put the ospfd.conf into frr.conf? 2. If yes to the above and 8.5.2 is discontinuing `no service integrated-vtysh-config`, is that something that should happen in a bugfix release? 3. If `no service integrated-vtysh-config` is being discontinued, wouldn't it be good if frr emitted an error to the effect that it is discontinued yet still specified in the configuration -- alerting users that it will no longer work as they expect?
1. I believe that only affects vtysh and how it writes out to config files . https://docs.frrouting.org/en/latest/vtysh.html#clicmd-service-integrated-vt... 3. If frr.conf is not present then the individual config files are read when frr starts up .
Cheers, b.
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
It sounds like your distro update created an empty file, which is overriding your previous choice of files.
So the thing that sticks out to me is that you have both a copy of frr.conf and ospfd.conf. If you are not using an integrated config, just have the individual daemon files.. If you are using the integrated config just use the frr.conf. Having both causes the daemons to get confused and do the wrong thing as you are experiencing here. donald On Wed, Jul 12, 2023 at 9:03 AM Brian J. Murrell <brian@interlinx.bc.ca> wrote:
On Tue, 2023-07-11 at 17:51 -0300, Patrick Boutilier wrote:
On 2023-07-11 10:41, Brian J. Murrell wrote:
no service integrated-vtysh-config
Have you tried putting the contents of /etc/frr/ospfd.conf in /etc/frr/frr.conf ?
I had not and indeed, that does resolve the issue. However:
1. Doesn't `no service integrated-vtysh-config` mean that each daemon read's it's own config file (I.e. as I have configured it) and as such I should not need to put the ospfd.conf into frr.conf? 2. If yes to the above and 8.5.2 is discontinuing `no service integrated-vtysh-config`, is that something that should happen in a bugfix release? 3. If `no service integrated-vtysh-config` is being discontinued, wouldn't it be good if frr emitted an error to the effect that it is discontinued yet still specified in the configuration -- alerting users that it will no longer work as they expect?
Cheers, b.
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
participants (4)
-
Brian J. Murrell -
Donald Sharp -
Michael Richardson -
Patrick Boutilier