Hi Dumitru,

yes sure, please see below.

DB dumps (just in case you want to import db contents instead of db file 
replacement) (I got them with ovsdb-client backup, so you need to run 
ovsdb-client restore):
NB: 
https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/nb-snap-1776328141.backup
SB: 
https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/sb-snap-1776328148.backup
NB DB file: https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/ovnnb_db.db
SB DB file: https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/ovnsb_db.db
GW node OVSDB file: 
https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/gw_ovs_conf.db
Workload node OVSDB file: 
https://s3.ru-msk.k2.cloud/odivlad/ovn-evpn-dump/wl_ovs_conf.db

FRR "external" config:

frr version 10.6.0
frr defaults traditional
hostname vtep01
log syslog informational
log file /var/log/frr/frr.log
!
vrf ovnvrf300
  vni 300
exit-vrf
!
router bgp 64513
  no bgp ebgp-requires-policy
  bgp bestpath as-path multipath-relax
  neighbor 10.128.0.4 remote-as external
  neighbor 10.128.0.6 remote-as external
  neighbor 10.128.0.14 remote-as external
  !
  address-family ipv4 unicast
   no neighbor 10.128.0.4 activate
   no neighbor 10.128.0.6 activate
   no neighbor 10.128.0.14 activate
  exit-address-family
  !
  address-family l2vpn evpn
   neighbor 10.128.0.4 activate
   neighbor 10.128.0.6 activate
   neighbor 10.128.0.14 activate
   advertise-all-vni
   advertise-svi-ip
  exit-address-family
exit
!
router bgp 64513 vrf ovnvrf300
  bgp router-id 10.128.0.5
  bgp bestpath as-path multipath-relax
  !
  address-family ipv4 unicast
   redistribute kernel
   redistribute connected
   maximum-paths 4
  exit-address-family
  !
  address-family l2vpn evpn
   advertise ipv4 unicast
  exit-address-family
exit

OVN GW node ip a output (let me know if you need some more infos):

[root@test-ovn1 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
     inet6 2001::1/64 scope global
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
     link/ether 0a:00:3b:9d:fb:80 brd ff:ff:ff:ff:ff:ff
     inet 10.128.0.14/24 brd 10.128.0.255 scope global dynamic eth0
        valid_lft 3540sec preferred_lft 3540sec
     inet6 fe80::800:3bff:fe9d:fb80/64 scope link
        valid_lft forever preferred_lft forever
5: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
group default qlen 1000
     link/ether f6:31:ff:e7:09:41 brd ff:ff:ff:ff:ff:ff
6: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group 
default qlen 1000
     link/ether 4a:b5:5a:e6:11:4b brd ff:ff:ff:ff:ff:ff
24: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group 
default qlen 1000
     link/ether ca:75:2c:30:60:43 brd ff:ff:ff:ff:ff:ff
42: vxlan300: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
master br-300 state UNKNOWN group default qlen 1000
     link/ether 3e:7d:ed:d7:f8:a5 brd ff:ff:ff:ff:ff:ff
     inet6 fe80::3c7d:edff:fed7:f8a5/64 scope link
        valid_lft forever preferred_lft forever
43: br-300: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
master ovnvrf300 state UP group default qlen 1000
     link/ether 0a:00:aa:21:e5:e0 brd ff:ff:ff:ff:ff:ff
     inet6 fe80::800:aaff:fe21:e5e0/64 scope link
        valid_lft forever preferred_lft forever
44: lo-300: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master 
br-300 state UNKNOWN group default qlen 1000
     link/ether 3a:7e:60:a3:08:82 brd ff:ff:ff:ff:ff:ff
     inet6 fe80::387e:60ff:fea3:882/64 scope link
        valid_lft forever preferred_lft forever
54: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc 
noqueue master ovs-system state UNKNOWN group default qlen 1000
     link/ether 06:63:2b:e8:d2:ba brd ff:ff:ff:ff:ff:ff
     inet6 fe80::463:2bff:fee8:d2ba/64 scope link
        valid_lft forever preferred_lft forever
57: ovnvrf300: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state 
UP group default qlen 1000
     link/ether 6e:9b:64:32:23:97 brd ff:ff:ff:ff:ff:ff
60: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc 
noqueue master ovs-system state UNKNOWN group default qlen 1000
     link/ether 8e:ec:85:4e:e1:18 brd ff:ff:ff:ff:ff:ff
     inet6 fe80::8cec:85ff:fe4e:e118/64 scope link
        valid_lft forever preferred_lft forever

[root@test-ovn1 ~]# ip vrf
Name              Table
-----------------------
ovnvrf300          300

[root@test-ovn1 ~]# ip vrf
Name              Table
-----------------------
ovnvrf300          300
[root@test-ovn1 ~]# bridge  fdb show
33:33:00:00:00:01 dev eth0 self permanent
01:00:5e:00:00:01 dev eth0 self permanent
33:33:ff:9d:fb:80 dev eth0 self permanent
33:33:00:00:00:02 dev eth0 self permanent
33:33:ff:00:00:00 dev eth0 self permanent
33:33:00:00:00:01 dev ovs-system self permanent
33:33:00:00:00:02 dev ovs-system self permanent
33:33:00:00:00:01 dev br-int self permanent
33:33:00:00:00:02 dev br-int self permanent
33:33:00:00:00:01 dev br-ls1 self permanent
00:04:00:00:00:01 dev vxlan300 vlan 1 extern_learn master br-300
00:04:00:00:00:01 dev vxlan300 extern_learn master br-300
00:05:00:00:00:01 dev vxlan300 vlan 1 extern_learn master br-300
00:05:00:00:00:01 dev vxlan300 extern_learn master br-300
3e:7d:ed:d7:f8:a5 dev vxlan300 vlan 1 master br-300 permanent
3e:7d:ed:d7:f8:a5 dev vxlan300 master br-300 permanent
00:04:00:00:00:01 dev vxlan300 dst 10.128.0.5 self extern_learn
00:05:00:00:00:01 dev vxlan300 dst 10.128.0.4 self extern_learn
01:00:5e:00:00:01 dev br-300 self permanent
33:33:00:00:00:02 dev br-300 self permanent
33:33:00:00:00:01 dev br-300 self permanent
33:33:ff:21:e5:e0 dev br-300 self permanent
33:33:ff:00:00:00 dev br-300 self permanent
0a:00:aa:21:e5:e0 dev lo-300 vlan 1 master br-300 static
0a:00:aa:21:e5:e0 dev lo-300 master br-300 static
3a:7e:60:a3:08:82 dev lo-300 vlan 1 master br-300 permanent
3a:7e:60:a3:08:82 dev lo-300 master br-300 permanent
33:33:00:00:00:01 dev lo-300 self permanent
01:00:5e:00:00:01 dev lo-300 self permanent
33:33:00:00:00:01 dev ovnvrf300 self permanent
01:00:5e:00:00:01 dev ovnvrf300 self permanent
33:33:00:00:00:01 dev genev_sys_6081 self permanent
33:33:00:00:00:02 dev genev_sys_6081 self permanent
01:00:5e:00:00:01 dev genev_sys_6081 self permanent
33:33:ff:4e:e1:18 dev genev_sys_6081 self permanent
33:33:ff:00:00:00 dev genev_sys_6081 self permanent


[root@test-ovn1 ~]# ovs-vsctl show
09af3e8a-5f2b-42b5-ae6d-c1d885fd1e77
     Bridge br-ex
         Port patch-test-ovn1-uplink-lsp-to-br-int
             Interface patch-test-ovn1-uplink-lsp-to-br-int
                 type: patch
                 options: {peer=patch-br-int-to-test-ovn1-uplink-lsp}
         Port br-ex
             Interface br-ex
                 type: internal
     Bridge br-int
         fail_mode: secure
         datapath_type: system
         Port lsp1
             Interface lsp1
                 type: internal
         Port patch-br-int-to-test-ovn1-uplink-lsp
             Interface patch-br-int-to-test-ovn1-uplink-lsp
                 type: patch
                 options: {peer=patch-test-ovn1-uplink-lsp-to-br-int}
         Port ovn-65d5ec-0
             Interface ovn-65d5ec-0
                 type: geneve
                 options: {csum="false", key=flow, 
local_ip="10.128.0.14", remote_ip="10.128.0.6"}
         Port br-int
             Interface br-int
                 type: internal
         Port ovn-evpn-4789
             Interface ovn-evpn-4789
                 type: vxlan
                 options: {dst_port="4789", key=flow, local_ip=flow, 
remote_ip=flow}
     ovs_version: "3.7.0-1.el8"

Dumitru Ceara wrote:
> Внимание: ВНЕШНИЙ отправитель!
> 
> 
> Будьте осторожны с вложениями и ссылками.
> 
> 
> Hi Vladislav,
> 
> On 4/16/26 10:03 AM, Dumitru Ceara wrote:
>> I'm not sure it's possible or that easy to sync the learned evpn/arps in
>> the SB database.  We should look into it though.
> 
> I actually realized we might have of a potential solution for this with
> a relatively small change in the code but I'd like to investigate some
> more locally.  Would it be possible to share the following?
> 
> - OVN NB DB file
> - OVN SB DB file
> - OVS DB (conf.db) files from the gateway and workload nodes
> - host interface config (br-<vni>, lo-<vni>, vxlan-<vni> from the GW node
> - FRR configs (preferably the external host config too)
> 
> Thanks,
> Dumitru
> 

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to