
Hello, I previously had OVN running on engine (as OVN provider with northd and northbound and southbound DBs) and hosts (with OVN controller). After changing mgmt ip of hosts (engine has retained instead the same ip), I executed again on them the command: vdsm-tool ovn-config <ip_of_engine> <nel_local_ip_of_host> Now I think I have to clean up some things, eg: 1) On engine where I get these lines below systemctl status ovn-northd.service -l . . . Sep 29 14:41:42 ovmgr1 ovsdb-server[940]: ovs|00005|reconnect|ERR|tcp: 10.4.167.40:37272: no response to inactivity probe after 5 seconds, disconnecting Oct 03 11:52:00 ovmgr1 ovsdb-server[940]: ovs|00006|reconnect|ERR|tcp: 10.4.167.41:52078: no response to inactivity probe after 5 seconds, disconnecting The two IPs are the old ones of two hosts It seems that a restart of the services has fixed... Can anyone confirm if I have to do anything else? 2) On hosts (there are 3 hosts with OVN on ip 10.4.192.32/33/34) where I currently have this output [root@ov301 ~]# ovs-vsctl show 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 Bridge br-int fail_mode: secure Port "ovn-1dce5b-0" Interface "ovn-1dce5b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.32"} Port "ovn-ddecf0-0" Interface "ovn-ddecf0-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.33"} Port "ovn-fd413b-0" Interface "ovn-fd413b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.168.74"} Port br-int Interface br-int type: internal ovs_version: "2.7.2" [root@ov301 ~]# The IPs of kind 10.4.192.x are ok. But there is a left-over of an old host I initially used for tests, corresponding to 10.4.168.74, that now doesn't exist anymore How can I clean records for 1) and 2)? Thanks, Gianluca

Hello Gianluca, Please check on the engine what hosts are registered on ovn-north: #ovn-sbctl show For each registered host you should see something like: Chassis "69b6b2a6-5afb-4908-8d66-c648cbe09ba8" hostname: "f43" Encap geneve ip: "192.168.120.43" .... I would assume you have some unwanted entries there (10.4.168.74) To get rid of this please use: # ovn-sbctl chassis-del <chassis id> // for example: ovn-sbctl chassis-del 69b6b2a6-5afb-4908-8d66-c648cbe09ba8 Please let me know if this helps. Note also that you would have to runplug/plug any vnics on any vm's you have on those two hosts. Marcin On Tue, Oct 3, 2017 at 3:41 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, I previously had OVN running on engine (as OVN provider with northd and northbound and southbound DBs) and hosts (with OVN controller).
After changing mgmt ip of hosts (engine has retained instead the same ip), I executed again on them the command:
vdsm-tool ovn-config <ip_of_engine> <nel_local_ip_of_host>
Now I think I have to clean up some things, eg:
1) On engine where I get these lines below
systemctl status ovn-northd.service -l . . . Sep 29 14:41:42 ovmgr1 ovsdb-server[940]: ovs|00005|reconnect|ERR|tcp:10 .4.167.40:37272: no response to inactivity probe after 5 seconds, disconnecting Oct 03 11:52:00 ovmgr1 ovsdb-server[940]: ovs|00006|reconnect|ERR|tcp:10 .4.167.41:52078: no response to inactivity probe after 5 seconds, disconnecting
The two IPs are the old ones of two hosts It seems that a restart of the services has fixed... Can anyone confirm if I have to do anything else?
2) On hosts (there are 3 hosts with OVN on ip 10.4.192.32/33/34) where I currently have this output
[root@ov301 ~]# ovs-vsctl show 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 Bridge br-int fail_mode: secure Port "ovn-1dce5b-0" Interface "ovn-1dce5b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.32"} Port "ovn-ddecf0-0" Interface "ovn-ddecf0-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.33"} Port "ovn-fd413b-0" Interface "ovn-fd413b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.168.74"} Port br-int Interface br-int type: internal ovs_version: "2.7.2" [root@ov301 ~]#
The IPs of kind 10.4.192.x are ok. But there is a left-over of an old host I initially used for tests, corresponding to 10.4.168.74, that now doesn't exist anymore
How can I clean records for 1) and 2)?
Thanks, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Tue, Oct 3, 2017 at 4:05 PM, Marcin Mirecki <mmirecki@redhat.com> wrote:
Hello Gianluca,
Please check on the engine what hosts are registered on ovn-north: #ovn-sbctl show
For each registered host you should see something like: Chassis "69b6b2a6-5afb-4908-8d66-c648cbe09ba8" hostname: "f43" Encap geneve ip: "192.168.120.43" ....
I would assume you have some unwanted entries there (10.4.168.74)
To get rid of this please use: # ovn-sbctl chassis-del <chassis id> // for example: ovn-sbctl chassis-del 69b6b2a6-5afb-4908-8d66-c648cbe09ba8
Please let me know if this helps.
Note also that you would have to runplug/plug any vnics on any vm's you have on those two hosts.
Marcin
Hello Marcin. it worked like a charm.. ;-) The "show" option of the command returned 4 chassis: - 3 are of running oVirt hosts that I notice have been automatically updated after the "vdsm-tool ovn-config ..." command run on them (their dns name has remained the same) - the leftover one After removing it with the suggested command it disappeared both from engine (ovn-sbctl show) and from hosts (ovs-vsctl show) I'm going to power on some VMs with their nics on OVN and see if all is ok. Thank you very much. Gianluca

Hi Gianluca did you ever resolve this ? I add a new host using the same IP as the old host but get errors that ovs already has an entry (the old one) Thanks Kevin

On Tue, Jan 26, 2021 at 7:54 PM Kevin Doyle <kevin.doyle@manchester.ac.uk> wrote:
Hi Gianluca did you ever resolve this ? I add a new host using the same IP as the old host but get errors that ovs already has an entry (the old one)
Thanks Kevin
yes, with the suggested command I was able to delete the previously defined chassis of the removed/readded host But probably it was oVirt 4.3 time. Are you using 4.4 or 4.3? In 4.4 the removal of host from web admin gui should imply an ansible playbook how removes ovn config for that host And probably you can cross check logs to understand why it was left over... Gianluca
participants (3)
-
Gianluca Cecchi
-
Kevin Doyle
-
Marcin Mirecki