[ovirt-users] Re: Ovirt OVN help needed
Hi Dominik,
sadly reinstall of all hosts is not helping.
@ Miguel,
I have 2 clusters1. Default (amd-based one) -> ovirt1 (192.168.1.90) & ovirt2
(192.168.1.64)2. Intel (intel-based one and a gluster arbiter) -> ovirt3
(192.168.1.41)
The output of the 2 commands (after I run reinstall on all hosts ):
[root@engine ~]# ovn-sbctl list encap_uuid :
d4d98c65-11da-4dc8-9da3-780e7738176fchassis_name :
"baa0199e-d1a4-484c-af13-a41bcad19dbc"ip :
"192.168.1.90"options : {csum="true"}type : geneve
_uuid : ed8744a5-a302-493b-8c3b-19a4d2e170dechassis_name :
"25cc77b3-046f-45c5-af0c-ffb2f77d73f1"ip :
"192.168.1.64"options : {csum="true"}type : geneve
_uuid : b72ff0ab-92fc-450c-a6eb-ab2869dee217chassis_name :
"5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3"ip :
"192.168.1.41"options : {csum="true"}type : geneve
[root@engine ~]# ovn-sbctl list chassis_uuid :
b1da5110-f477-4c60-9963-b464ab96c644encaps :
[ed8744a5-a302-493b-8c3b-19a4d2e170de]external_ids : {datapath-type="",
iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan",
ovn-bridge-mappings=""}hostname : "ovirt2.localdomain"name
: "25cc77b3-046f-45c5-af0c-ffb2f77d73f1"nb_cfg :
0transport_zones : []vtep_logical_switches: []
_uuid : dcc94e1c-bf44-46a3-b9d1-45360c307b26encaps :
[b72ff0ab-92fc-450c-a6eb-ab2869dee217]external_ids : {datapath-type="",
iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan",
ovn-bridge-mappings=""}hostname : "ovirt3.localdomain"name
: "5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3"nb_cfg :
0transport_zones : []vtep_logical_switches: []
_uuid : 897b34c5-d1d1-41a7-b2fd-5f1fa203c1daencaps :
[d4d98c65-11da-4dc8-9da3-780e7738176f]external_ids : {datapath-type="",
iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan",
ovn-bridge-mappings=""}hostname : "ovirt1.localdomain"name
: "baa0199e-d1a4-484c-af13-a41bcad19dbc"nb_cfg :
0transport_zones : []vtep_logical_switches: []
If you know an easy method to reach default settings will be best, as I'm
currently not using OVN in production (just for tests and to learn more about
how it works) and I can afford any kind of downtime.
Best Regards,Strahil Nikolov
В вторник, 17 декември 2019 г., 11:28:25 ч. Гринуич+2, Miguel Duarte de
Mora Barroso написа:
On Tue, Dec 17, 2019 at 10:19 AM Miguel Duarte de Mora Barroso
wrote:
>
> On Tue, Dec 17, 2019 at 9:17 AM Dominik Holler wrote:
> >
> >
> >
> > On Tue, Dec 17, 2019 at 6:28 AM Strahil wrote:
> >>
> >> Hi Dominik,
> >>
> >> Thanks for your reply.
> >>
> >> On ovirt1 I got the following:
> >> [root@ovirt1 openvswitch]# less ovn-controller.log-20191216.gz
> >> 2019-12-15T01:49:02.988Z|00032|vlog|INFO|opened log file
> >> /var/log/openvswitch/ovn-controller.log
> >> 2019-12-16T01:18:02.114Z|00033|vlog|INFO|closing log file
> >> ovn-controller.log-20191216.gz (END)
> >>
> >> Same is on the other node:
> >>
> >> [root@ovirt2 openvswitch]# less ovn-controller.log-20191216.gz
> >> 2019-12-15T01:26:03.477Z|00028|vlog|INFO|opened log file
> >> /var/log/openvswitch/ovn-controller.log
> >> 2019-12-16T01:30:01.718Z|00029|vlog|INFO|closing log file
> >> ovn-controller.log-20191216.gz (END)
> >>
> >> The strange thing is that the geneve tunnels are there:
> >
> >
> >
> > Miguel, do you know how to remove and re-add the chassis to the southbound
> > db?
> > (We have to check this to address bug https://bugzilla.redhat.com/1758289 )
>
> "ovn-sbctl chassis-del CHASSIS" will get rid of the chassis / encap.
>
> Afterwards, the ovn-controller will re-register itself on OVN southbound.
>
> There's something weird about your chassis, I see you have listed 3
> different chassis IDs on your port IDs:
> - ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"
> - ovn-chassis-id="25cc77b3-046f-45c5-af0c-ffb2f77d73f1@192.168.1.64"
> - ovn-chassis-id="baa0199e-d1a4-484c-af13-a41bcad19dbc@192.168.1.90"
>
> From your 'ovs-vsctl show' I can see the IP encaps 192.168.1.41 and
> 192.168.1.64 are 'expected'.
>
> I would expect to see a duplicate chassis entry in the same IP . Who
> has this 192.168.1.90 IP ?
>
> A couple of further questions:
> - did you upgrade recently your environment ? If so, from which
> version to which version ?
> - what is the switch type of the cluster where you are running OVN ?
- what is the output of "ovn-sbctl list chassis" and "ovn-sbctl list
encap" on your engine node ?
>
> >
> >>
> >> [root@ovirt1 ~]# ovs-vsctl show
> >> c0e938f1-b5b5-4d5a-9cda-29dae2986f29
> >> Bridge br-int
> >>
[ovirt-users] Re: Cannot start VM 2 hosts
Problem found. on these 2 hosts was the firewall disabled bye shb ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q64MJ7IXIEA2VE6BFDQNWZMCOCK3JRIN/
[ovirt-users] Cannot start VM 2 hosts
I ve got 4 Hosts
after changeing the harddrive on every Host and normal updates I am not able
anymore to start VM's on 2 of these 4 hosts.
I am also not able to migrate a running vm to these hosts.
This is the error log for start up
2019-12-17 16:01:28,326+01 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(default task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] Lock Acquired to object
'EngineLock:{exclusiveLocks='[40cf6c27-6464-4fa7-bc01-9158cb03328b=VM]',
sharedLocks=''}'
2019-12-17 16:01:28,609+01 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] START,
IsVmDuringInitiatingVDSCommand(
IsVmDuringInitiatingVDSCommandParameters:{vmId='40cf6c27-6464-4fa7-bc01-9158cb03328b'}),
log id: 5706d380
2019-12-17 16:01:28,611+01 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] FINISH,
IsVmDuringInitiatingVDSCommand, return: false, log id: 5706d380
2019-12-17 16:01:28,854+01 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(default task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] Running command:
RunVmOnceCommand internal: false. Entities affected : ID:
40cf6c27-6464-4fa7-bc01-9158cb03328b Type: VMAction group RUN_VM with role type
USER, ID: 40cf6c27-6464-4fa7-bc01-9158cb03328b Type: VMAction group
EDIT_ADMIN_VM_PROPERTIES with role type ADMIN
2019-12-17 16:01:28,999+01 INFO
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] START,
UpdateVmDynamicDataVDSCommand(
UpdateVmDynamicDataVDSCommandParameters:{hostId='null',
vmId='40cf6c27-6464-4fa7-bc01-9158cb03328b',
vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@147620b'}),
log id: 612dabdf
2019-12-17 16:01:29,097+01 INFO
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] FINISH,
UpdateVmDynamicDataVDSCommand, return: , log id: 612dabdf
2019-12-17 16:01:29,106+01 INFO
[org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-5)
[3beff980-0f1a-461b-a6da-89c6f4dea6b3] START, CreateVDSCommand(
CreateVDSCommandParameters:{hostId='d38bae4c-8494-4861-ae5a-38992db338e5',
vmId='40cf6c27-6464-4fa7-bc01-9158cb03328b', vm='VM [z-push]'}), log id:
56abde11
2019-12-17 16:01:29,110+01 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] START,
CreateBrokerVDSCommand(HostName = kvm360.durchhalten.intern,
CreateVDSCommandParameters:{hostId='d38bae4c-8494-4861-ae5a-38992db338e5',
vmId='40cf6c27-6464-4fa7-bc01-9158cb03328b', vm='VM [z-push]'}), log id:
36d088ab
2019-12-17 16:01:29,163+01 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] VM http://ovirt.org/vm/tune/1.0;
xmlns:ovirt-vm="http://ovirt.org/vm/1.0;>
z-push
40cf6c27-6464-4fa7-bc01-9158cb03328b
4194304
4194304
1
16777216
16
oVirt
OS-NAME:
OS-VERSION:
HOST-SERIAL:
40cf6c27-6464-4fa7-bc01-9158cb03328b
SandyBridge
/dev/urandom
38f2e3bb-687f-4f01-b769-3a5403136181
hvm
4096
4.3
0e279f02-0c73-11e9-bc47-00163e150480
1a9627d8-181b-4790-aa47-569dd1e6e9fb
38f2e3bb-687f-4f01-b769-3a5403136181
80364cc8-8afd-4482-884d-d63d5a7988df
false
auto_resume
2019-12-17 16:01:29,198+01 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (default
task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] FINISH, CreateBrokerVDSCommand,
return: , log id: 36d088ab
2019-12-17 16:01:29,252+01 INFO
[org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-5)
[3beff980-0f1a-461b-a6da-89c6f4dea6b3] FINISH, CreateVDSCommand, return:
WaitForLaunch, log id: 56abde11
2019-12-17 16:01:29,252+01 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(default task-5) [3beff980-0f1a-461b-a6da-89c6f4dea6b3] Lock freed to object
'EngineLock:{exclusiveLocks='[40cf6c27-6464-4fa7-bc01-9158cb03328b=VM]',
sharedLocks=''}'
2019-12-17 16:01:29,319+01 INFO
[ovirt-users] Re: Ovirt OVN help needed
On Tue, Dec 17, 2019 at 10:19 AM Miguel Duarte de Mora Barroso
wrote:
>
> On Tue, Dec 17, 2019 at 9:17 AM Dominik Holler wrote:
> >
> >
> >
> > On Tue, Dec 17, 2019 at 6:28 AM Strahil wrote:
> >>
> >> Hi Dominik,
> >>
> >> Thanks for your reply.
> >>
> >> On ovirt1 I got the following:
> >> [root@ovirt1 openvswitch]# less ovn-controller.log-20191216.gz
> >> 2019-12-15T01:49:02.988Z|00032|vlog|INFO|opened log file
> >> /var/log/openvswitch/ovn-controller.log
> >> 2019-12-16T01:18:02.114Z|00033|vlog|INFO|closing log file
> >> ovn-controller.log-20191216.gz (END)
> >>
> >> Same is on the other node:
> >>
> >> [root@ovirt2 openvswitch]# less ovn-controller.log-20191216.gz
> >> 2019-12-15T01:26:03.477Z|00028|vlog|INFO|opened log file
> >> /var/log/openvswitch/ovn-controller.log
> >> 2019-12-16T01:30:01.718Z|00029|vlog|INFO|closing log file
> >> ovn-controller.log-20191216.gz (END)
> >>
> >> The strange thing is that the geneve tunnels are there:
> >
> >
> >
> > Miguel, do you know how to remove and re-add the chassis to the southbound
> > db?
> > (We have to check this to address bug https://bugzilla.redhat.com/1758289 )
>
> "ovn-sbctl chassis-del CHASSIS" will get rid of the chassis / encap.
>
> Afterwards, the ovn-controller will re-register itself on OVN southbound.
>
> There's something weird about your chassis, I see you have listed 3
> different chassis IDs on your port IDs:
> - ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"
> - ovn-chassis-id="25cc77b3-046f-45c5-af0c-ffb2f77d73f1@192.168.1.64"
> - ovn-chassis-id="baa0199e-d1a4-484c-af13-a41bcad19dbc@192.168.1.90"
>
> From your 'ovs-vsctl show' I can see the IP encaps 192.168.1.41 and
> 192.168.1.64 are 'expected'.
>
> I would expect to see a duplicate chassis entry in the same IP . Who
> has this 192.168.1.90 IP ?
>
> A couple of further questions:
>- did you upgrade recently your environment ? If so, from which
> version to which version ?
> - what is the switch type of the cluster where you are running OVN ?
- what is the output of "ovn-sbctl list chassis" and "ovn-sbctl list
encap" on your engine node ?
>
> >
> >>
> >> [root@ovirt1 ~]# ovs-vsctl show
> >> c0e938f1-b5b5-4d5a-9cda-29dae2986f29
> >> Bridge br-int
> >> fail_mode: secure
> >> Port "ovn-25cc77-0"
> >> Interface "ovn-25cc77-0"
> >> type: geneve
> >> options: {csum="true", key=flow, remote_ip="192.168.1.64"}
> >> Port "ovn-566849-0"
> >> Interface "ovn-566849-0"
> >> type: geneve
> >> options: {csum="true", key=flow, remote_ip="192.168.1.41"}
> >> Port br-int
> >> Interface br-int
> >> type: internal
> >> Port "vnet2"
> >> Interface "vnet2"
> >> ovs_version: "2.11.0"
> >> [root@ovirt1 ~]# ovs-vsctl list ports
> >> ovs-vsctl: unknown table "ports"
> >> [root@ovirt1 ~]# ovs-vsctl list port
> >> _uuid : fbf40569-925e-4430-a7c5-c78d58979bbc
> >> bond_active_slave : []
> >> bond_downdelay : 0
> >> bond_fake_iface : false
> >> bond_mode : []
> >> bond_updelay: 0
> >> cvlans : []
> >> external_ids: {}
> >> fake_bridge : false
> >> interfaces : [3207c0cb-3000-40f2-a850-83548f76f090]lacp
> >> : []
> >> mac : []
> >> name: "vnet2"
> >> other_config: {}
> >> protected : false
> >> qos : []
> >> rstp_statistics : {}
> >> rstp_status : {}
> >> statistics : {}
> >> status : {}
> >> tag : []
> >> trunks : []
> >> vlan_mode : []
> >>
> >> _uuid : 8947f82d-a089-429b-8843-71371314cb52
> >> bond_active_slave : []
> >> bond_downdelay : 0
> >> bond_fake_iface : false
> >> bond_mode : []
> >> bond_updelay: 0
> >> cvlans : []
> >> external_ids: {}
> >> fake_bridge : false
> >> interfaces : [ec6a6688-e5d6-4346-ac47-ece1b8379440]lacp
> >> : []
> >> mac : []
> >> name: br-int
> >> other_config: {}
> >> protected : false
> >> qos : []
> >> rstp_statistics : {}
> >> rstp_status : {}
> >> statistics : {}
> >> status : {}
> >> tag : []
> >> trunks : []
> >> vlan_mode : []
> >>
> >> _uuid : 72d612be-853e-43e9-8f5c-ce66cef0bebe
> >> bond_active_slave : []
> >> bond_downdelay : 0
> >> bond_fake_iface : false
> >> bond_mode : []
> >> bond_updelay: 0
> >> cvlans : []
> >> external_ids:
> >> {ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"}
> >> fake_bridge : false
> >>
[ovirt-users] Re: Ovirt OVN help needed
On Tue, Dec 17, 2019 at 9:17 AM Dominik Holler wrote:
>
>
>
> On Tue, Dec 17, 2019 at 6:28 AM Strahil wrote:
>>
>> Hi Dominik,
>>
>> Thanks for your reply.
>>
>> On ovirt1 I got the following:
>> [root@ovirt1 openvswitch]# less ovn-controller.log-20191216.gz
>> 2019-12-15T01:49:02.988Z|00032|vlog|INFO|opened log file
>> /var/log/openvswitch/ovn-controller.log
>> 2019-12-16T01:18:02.114Z|00033|vlog|INFO|closing log file
>> ovn-controller.log-20191216.gz (END)
>>
>> Same is on the other node:
>>
>> [root@ovirt2 openvswitch]# less ovn-controller.log-20191216.gz
>> 2019-12-15T01:26:03.477Z|00028|vlog|INFO|opened log file
>> /var/log/openvswitch/ovn-controller.log
>> 2019-12-16T01:30:01.718Z|00029|vlog|INFO|closing log file
>> ovn-controller.log-20191216.gz (END)
>>
>> The strange thing is that the geneve tunnels are there:
>
>
>
> Miguel, do you know how to remove and re-add the chassis to the southbound db?
> (We have to check this to address bug https://bugzilla.redhat.com/1758289 )
"ovn-sbctl chassis-del CHASSIS" will get rid of the chassis / encap.
Afterwards, the ovn-controller will re-register itself on OVN southbound.
There's something weird about your chassis, I see you have listed 3
different chassis IDs on your port IDs:
- ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"
- ovn-chassis-id="25cc77b3-046f-45c5-af0c-ffb2f77d73f1@192.168.1.64"
- ovn-chassis-id="baa0199e-d1a4-484c-af13-a41bcad19dbc@192.168.1.90"
From your 'ovs-vsctl show' I can see the IP encaps 192.168.1.41 and
192.168.1.64 are 'expected'.
I would expect to see a duplicate chassis entry in the same IP . Who
has this 192.168.1.90 IP ?
A couple of further questions:
- did you upgrade recently your environment ? If so, from which
version to which version ?
- what is the switch type of the cluster where you are running OVN ?
>
>>
>> [root@ovirt1 ~]# ovs-vsctl show
>> c0e938f1-b5b5-4d5a-9cda-29dae2986f29
>> Bridge br-int
>> fail_mode: secure
>> Port "ovn-25cc77-0"
>> Interface "ovn-25cc77-0"
>> type: geneve
>> options: {csum="true", key=flow, remote_ip="192.168.1.64"}
>>Port "ovn-566849-0"
>> Interface "ovn-566849-0"
>> type: geneve
>> options: {csum="true", key=flow, remote_ip="192.168.1.41"}
>>Port br-int
>> Interface br-int
>> type: internal
>> Port "vnet2"
>> Interface "vnet2"
>> ovs_version: "2.11.0"
>> [root@ovirt1 ~]# ovs-vsctl list ports
>> ovs-vsctl: unknown table "ports"
>> [root@ovirt1 ~]# ovs-vsctl list port
>> _uuid : fbf40569-925e-4430-a7c5-c78d58979bbc
>> bond_active_slave : []
>> bond_downdelay : 0
>> bond_fake_iface : false
>> bond_mode : []
>> bond_updelay: 0
>> cvlans : []
>> external_ids: {}
>> fake_bridge : false
>> interfaces : [3207c0cb-3000-40f2-a850-83548f76f090]lacp
>>: []
>> mac : []
>> name: "vnet2"
>> other_config: {}
>> protected : false
>> qos : []
>> rstp_statistics : {}
>> rstp_status : {}
>> statistics : {}
>> status : {}
>> tag : []
>> trunks : []
>> vlan_mode : []
>>
>> _uuid : 8947f82d-a089-429b-8843-71371314cb52
>> bond_active_slave : []
>> bond_downdelay : 0
>> bond_fake_iface : false
>> bond_mode : []
>> bond_updelay: 0
>> cvlans : []
>> external_ids: {}
>> fake_bridge : false
>> interfaces : [ec6a6688-e5d6-4346-ac47-ece1b8379440]lacp
>>: []
>> mac : []
>> name: br-int
>> other_config: {}
>> protected : false
>> qos : []
>> rstp_statistics : {}
>> rstp_status : {}
>> statistics : {}
>> status : {}
>> tag : []
>> trunks : []
>> vlan_mode : []
>>
>> _uuid : 72d612be-853e-43e9-8f5c-ce66cef0bebe
>> bond_active_slave : []
>> bond_downdelay : 0
>> bond_fake_iface : false
>> bond_mode : []
>> bond_updelay: 0
>> cvlans : []
>> external_ids:
>> {ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"}
>> fake_bridge : false
>> interfaces : [a31574fe-515b-420b-859d-7f2ac729638f]lacp
>>: []
>> mac : []
>> name: "ovn-566849-0"
>> other_config: {}
>> protected : false
>> qos : []
>> rstp_statistics : {}
>> rstp_status : {}
>> statistics : {}
>> status : {}
>> tag : []
>> trunks : []
>> vlan_mode : []
[ovirt-users] Re: Ovirt OVN help needed
On Tue, Dec 17, 2019 at 6:28 AM Strahil wrote:
> Hi Dominik,
>
> Thanks for your reply.
>
> On ovirt1 I got the following:
> [root@ovirt1 openvswitch]# less ovn-controller.log-20191216.gz
> 2019-12-15T01:49:02.988Z|00032|vlog|INFO|opened log file
> /var/log/openvswitch/ovn-controller.log
> 2019-12-16T01:18:02.114Z|00033|vlog|INFO|closing log file
> ovn-controller.log-20191216.gz (END)
>
> Same is on the other node:
>
> [root@ovirt2 openvswitch]# less ovn-controller.log-20191216.gz
> 2019-12-15T01:26:03.477Z|00028|vlog|INFO|opened log file
> /var/log/openvswitch/ovn-controller.log
> 2019-12-16T01:30:01.718Z|00029|vlog|INFO|closing log file
> ovn-controller.log-20191216.gz (END)
>
> The strange thing is that the geneve tunnels are there:
>
Miguel, do you know how to remove and re-add the chassis to the southbound
db?
(We have to check this to address bug https://bugzilla.redhat.com/1758289 )
> [root@ovirt1 ~]# ovs-vsctl show
> c0e938f1-b5b5-4d5a-9cda-29dae2986f29
> Bridge br-int
> fail_mode: secure
> Port "ovn-25cc77-0"
> Interface "ovn-25cc77-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="192.168.1.64"}
> Port "ovn-566849-0"
> Interface "ovn-566849-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="192.168.1.41"}
> Port br-int
> Interface br-int
> type: internal
> Port "vnet2"
> Interface "vnet2"
> ovs_version: "2.11.0"
> [root@ovirt1 ~]# ovs-vsctl list ports
> ovs-vsctl: unknown table "ports"
> [root@ovirt1 ~]# ovs-vsctl list port
> _uuid : fbf40569-925e-4430-a7c5-c78d58979bbc
> bond_active_slave : []
> bond_downdelay : 0
> bond_fake_iface : false
> bond_mode : []
> bond_updelay: 0
> cvlans : []
> external_ids: {}
> fake_bridge : false
> interfaces :
> [3207c0cb-3000-40f2-a850-83548f76f090]lacp: []
> mac : []
> name: "vnet2"
> other_config: {}
> protected : false
> qos : []
> rstp_statistics : {}
> rstp_status : {}
> statistics : {}
> status : {}
> tag : []
> trunks : []
> vlan_mode : []
>
> _uuid : 8947f82d-a089-429b-8843-71371314cb52
> bond_active_slave : []
> bond_downdelay : 0
> bond_fake_iface : false
> bond_mode : []
> bond_updelay: 0
> cvlans : []
> external_ids: {}
> fake_bridge : false
> interfaces :
> [ec6a6688-e5d6-4346-ac47-ece1b8379440]lacp: []
> mac : []
> name: br-int
> other_config: {}
> protected : false
> qos : []
> rstp_statistics : {}
> rstp_status : {}
> statistics : {}
> status : {}
> tag : []
> trunks : []
> vlan_mode : []
>
> _uuid : 72d612be-853e-43e9-8f5c-ce66cef0bebe
> bond_active_slave : []
> bond_downdelay : 0
> bond_fake_iface : false
> bond_mode : []
> bond_updelay: 0
> cvlans : []
> external_ids: {ovn-chassis-id="
> 5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3@192.168.1.41"}
> fake_bridge : false
> interfaces :
> [a31574fe-515b-420b-859d-7f2ac729638f]lacp: []
> mac : []
> name: "ovn-566849-0"
> other_config: {}
> protected : false
> qos : []
> rstp_statistics : {}
> rstp_status : {}
> statistics : {}
> status : {}
> tag : []
> trunks : []
> vlan_mode : []
>
> _uuid : 2043a15f-ec39-4cc3-b875-7be00423dd7a
> bond_active_slave : []
> bond_downdelay : 0
> bond_fake_iface : false
> bond_mode : []
> bond_updelay: 0
> cvlans : []
> external_ids: {ovn-chassis-id="
> 25cc77b3-046f-45c5-af0c-ffb2f77d73f1@192.168.1.64"}
> fake_bridge : false
> interfaces :
> [f9a9e3ff-070e-4044-b601-7f7394dc295f]lacp: []
> mac : []
> name: "ovn-25cc77-0"
> other_config: {}
> protected : false
> qos : []
> rstp_statistics : {}
> rstp_status : {}
> statistics : {}
> status : {}
> tag : []
> trunks : []
> vlan_mode : []
> [root@ovirt1 ~]#
>
> [root@ovirt2 ~]# ovs-vsctl show
> 3dbab138-6b90-44c5-af05-b8a944c9bf20
> Bridge br-int
> fail_mode: secure
> Port "ovn-baa019-0"
> Interface "ovn-baa019-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="192.168.1.90"}
> Port br-int
> Interface br-int
>
