FRR 10.6 added a check in ospfd that allows area X virtual-link only when the router is currently an ABR
With the default abr-type cisco, a router attached to two non-backbone areas is not an ABR, because it has no area 0.
Giving it area 0 is exactly what the
virtual-link is for. The virtual-link setup therefore stops working in VyOS with FRR 10.6 10.7
Topology
r1 ---- area 0 ---- r2 (ABR 0/1) ---- area 1 ---- r3 (area 1 + area 2) ---- area 2: 10.22.22.1/32
10.0.2.1 10.0.2.2 10.0.3.2 10.0.3.3
virtual-link 10.0.3.3 <-------------------> virtual-link 10.0.2.2Area 2 is not connected to area 0, so a virtual-link across area 1 is needed. Only r3 is affected: r2 has a real area-0
interface.
Steps to reproduce
r1
set interfaces ethernet eth1 address '10.0.2.1/24' set interfaces dummy dum2 address '10.11.11.1/32' set protocols ospf parameters router-id '10.0.2.1' set protocols ospf interface eth1 area '0' set protocols ospf interface dum2 area '0' set protocols ospf interface dum2 passive commit
r2
set interfaces ethernet eth1 address '10.0.2.2/24' set interfaces ethernet eth2 address '10.0.3.2/24' set protocols ospf parameters router-id '10.0.2.2' set protocols ospf interface eth1 area '0' set protocols ospf interface eth2 area '1' set protocols ospf area 1 virtual-link '10.0.3.3' commit
r3
set interfaces ethernet eth1 address '10.0.3.3/24' set interfaces dummy dum2 address '10.22.22.1/32' set protocols ospf parameters router-id '10.0.3.3' set protocols ospf interface eth1 area '1' set protocols ospf interface dum2 area '2' set protocols ospf interface dum2 passive set protocols ospf area 1 virtual-link '10.0.2.2' commit
Configuring VLs on non-ABRs is not allowed line 46: Failure to communicate[13] to ospfd, line: area 1 virtual-link [ospfd] Configuration file[/etc/frr/frr.conf] processing failure: 13 [[protocols ospf]] failed Commit failed
Actual
- the r3 commit fails with the error above;
- r1: show ip route ospf has no 10.22.22.1/32, and ping 10.22.22.1 source-address 10.11.11.1 gives 100% loss;
- r2: no VLINK neighbor in show ip ospf neighbor;
- r3: show ip ospf has no "This router is an ABR" line.
Expected: the commit succeeds, the virtual-link comes up, and r1 learns 10.22.22.1/32.
Workaround
set protocols ospf parameters abr-type 'standard', if it fail again try two separate commits: first the areas and
abr-type, then the virtual-link.
set protocols ospf parameters router-id '10.0.3.3' set protocols ospf parameters abr-type 'standard' set protocols ospf interface eth1 area '1' set protocols ospf interface dum2 area '2' set protocols ospf interface dum2 passive commit
set protocols ospf area 1 virtual-link '10.0.2.2' commit
FRR upstream has already reverted this check: PR #22979 "ospfd:
allow virtual-link configuration before ABR state",
The revert is in master and stable/10.8 only. It is not in stable/10.6 or stable/10.7