OVS-connected networks are missing in 'sh ip ospf database'

Volodymyr Litovka doka at funlab.cc
Tue Jul 25 13:13:08 UTC 2023


Hi,

brief: 'sh ip ospf database' do not show networks, configured on OVS 
bridges, while neighbors see these networks.

Details:

Here is 8.5.2-0~ubuntu22.04.1 from FRR repo and Openvswitch from Ubuntu 
repo (2.17.7-0ubuntu0.22.04.1 ). Host configured with OVS bridges 
(br-ex, bt-int), 802.1q subinterfaces (orange) and plain links (blue) 
and marked in bold below are subject of the question:

3: blue: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP 
group default qlen 1000
     inet 100.64.98.3/24 brd 100.64.98.255 scope global blue
        valid_lft forever preferred_lft forever
8: orange at ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1496 qdisc 
noqueue state UP group default qlen 1000
     inet 100.64.99.3/24 brd 100.64.99.255 scope global orange
        valid_lft forever preferred_lft forever
*10: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
state UNKNOWN group default qlen 1000**
**    inet 192.145.111.65/27 brd 192.145.111.95 scope global br-ex**
**       valid_lft forever preferred_lft forever**
****11: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1496 qdisc noqueue 
state UNKNOWN group default qlen 1000**
**    inet 100.64.4.1/23 brd 100.64.5.255 scope global br-int**
**       valid_lft forever preferred_lft forever*

OSPF configuration on FRR is the following:

interface blue
  ip ospf dead-interval 4
  ip ospf hello-interval 1
  no ip ospf passive
exit
!
interface orange
  ip ospf dead-interval 4
  ip ospf hello-interval 1
  no ip ospf passive
exit
!
router ospf
  ospf router-id 100.64.4.1
  passive-interface default
  network 100.64.4.0/23 area 0
  network 100.64.98.0/24 area 0
  network 100.64.99.0/24 area 0
  network 192.145.111.0/24 area 0
  default-information originate
exit

but while br-ex and br-int networks are missing in output of 'sh ip ospf 
database'

# sh ip ospf database

        OSPF Router with ID (100.64.4.1)

                 Router Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Link count
100.64.0.1     100.64.0.1       136 0x800000f8 0xfe2e 5
100.64.2.1     100.64.2.1       135 0x800000ba 0xcd74 3
100.64.4.1     100.64.4.1        96 0x80000374 0xceaf 4

                 Net Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
100.64.98.2    100.64.2.1       136 0x80000006 0xf9af
100.64.99.2    100.64.2.1       136 0x80000006 0xeeb9

                 AS External Link States

Link ID         ADV Router      Age  Seq#       CkSum  Route
0.0.0.0        100.64.0.1      1183 0x800000b9 0x4624 E2 0.0.0.0/0 [0x0]
0.0.0.0        100.64.4.1       130 0x800000bd 0x2240 E2 0.0.0.0/0 [0x0]

neighboring routers see them:

O>* 100.64.4.0/23 [110/20] via 100.64.98.3, blue, weight 1, 00:35:57
   *                        via 100.64.99.3, orange, weight 1, 00:35:57
O>* 192.145.111.64/27 [110/20] via 100.64.98.3, blue, weight 1, 00:16:17
   *                            via 100.64.99.3, orange, weight 1, 00:16:17

I guess the issue can be with UNKNOWN state of the interface (though 
LOWER_UP says that everything is ok with underlay). So the question is - 
whether this can lead to any issues (I do not see them at the moment 
except troubleshooting in case) or it worth attention and need to be 
fixed in some ways? If yes - in which ways it should be fixed?

Thank you.

-- 
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20230725/316d3f99/attachment.htm>


More information about the frog mailing list