Re: [ovs-discuss] ovs-ofctl broken when getting table features reply

2021-01-07 Thread Ben Pfaff 
On Mon, Jan 04, 2021 at 11:13:53AM +0800, Dickens Yeh wrote:
> Hi,
> When I using the ovs-ofctl utility tool to dump flows from a
> non-openvswitch switch without --no-names parameter, and I got error
> message.
> 
> cmd:
> 
> ~/openvswitch-2.13.1/utilities/ovs-ofctl -O OpenFlow13 dump-flows tcp:
> 192.168.17.166:6644
> 
> msg:
> 2020-12-31T10:12:22Z|1|ofp_table|WARN|table features message missing
> required property
> ovs-ofctl: received bad reply: (***only uses 512 bytes out of 7056***)
>   04 50 02 00 00 00 00 00-6e 6f 76 69 5f 74 61 62 |.P..novi_tab|
> 0010  6c 65 5f 32 00 00 00 00-00 00 00 00 00 00 00 00 |le_2|
> ...
> 
> I also attached the pcap file, please tell me if the switch should be fixed
> with the reply messages.

I ran "ovs-ofctl ofp-parse-pcap dump-error.pcap 6644" and got only the
following output:

192.168.13.141.52476 > 192.168.17.166.6644:
OFPT_HELLO (OF1.3) (xid=0x1):
 version bitmap: 0x04

192.168.13.141.52476 > 192.168.17.166.6644:
OFPST_FLOW request (OF1.3) (xid=0x2):

192.168.13.141.52478 > 192.168.17.166.6644:
OFPT_HELLO (OF1.3) (xid=0x3):
 version bitmap: 0x04

192.168.13.141.52478 > 192.168.17.166.6644:
OFPST_TABLE_FEATURES request (OF1.3) (xid=0x4):

I don't think the table features reply is in the pcap.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN Dynamic Routing

2021-01-07 Thread Greg Smith 
+ Greg A Smith

From: Daniel Alvarez Sanchez 
Date: Thursday, January 7, 2021 at 4:17 AM
To: Ankur Sharma 
Cc: Frode Nordahl , Greg Smith , 
ovs-discuss 
Subject: Re: [ovs-discuss] OVN Dynamic Routing

Thanks Ankur, all for the presentation and slides.

If I may, I have a some questions regarding the proposed solution:

1) Who is responsible for creating the VTEP endpoints on each hypervisor? Are 
they assumed to be created in advance or somehow this solution will take care 
of it? If the latter, how will it work and how will 'ovn-routing' know the 
addresses of the endpoints? OVN VTEP gateways?

2) In the diagram at [0], what's the 'MAC ROUTER'? Is this OVN Logical Router 
connected to a Logical Switch with a localnet port and this MAC address 
corresponds to such port in the router? Or it would be the MAC address of 
'10.0.0.1'. What if two VMs in the same LS reside on different hypervisors, 
would you still advertise the same MAC but use a different VNI?
With OVN routers being distributed we'd have the same MAC address advertised on 
multiple HVs and we need to use different VNIs to distinguish them, right?

3) If two OVN VMs want to reach each other, it will still use the Geneve 
overlay right? This whole solution is mainly for incoming traffic or I'm 
missing something?

I'm sorry if the questions are a bit blurry but I guess that after reviewing 
the slides and recording I didn't quite grasp it :)

Thanks a lot in advance!
daniel

[0] https://youtu.be/9DL8M1d4xLY?t=330 
[youtu.be]


On Mon, Dec 14, 2020 at 8:25 PM Ankur Sharma 
mailto:ankur.sha...@nutanix.com>> wrote:
Hi Frode,

Glad to see your message.
Yes, while we started with EVPN as our main use case, we agree that it is more 
of a generic dynamic routing capability in OVN.

Sure, we will kickstart the discussions around this on mailing list as well.


Thanks

Regards,
Ankur

From: Frode Nordahl 
mailto:frode.nord...@canonical.com>>
Sent: Thursday, December 10, 2020 1:10 AM
To: Ankur Sharma mailto:ankur.sha...@nutanix.com>>
Cc: Greg Smith mailto:g...@nutanix.com>>; ovs-discuss 
mailto:ovs-discuss@openvswitch.org>>
Subject: OVN Dynamic Routing

Hello, Ankur, Greg, All,

Thank you for sharing your view on dynamic routing support for OVN
during OVSCON 2020 [0].

I believe this is a topic that interests multiple parties in the
community, and it applies to multiple topologies/use cases, not just
EVPN.

Would you be interested in presenting and discussing the proposed
design on the mailing list?

0: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openvswitch.org_support_ovscon2020_=DwIBaQ=s883GpUCOChKOHiocYtGcg=mZwX9gFQgeJHzTg-68aCJgsODyUEVsHGFOfL90J6MJY=3HUT7aQXAsSImmITSraoqdZ6mWcRxUtwVRKAfH3ygQA=Xzze2S3f7Rstp66gRz7MSuTGvGltr3t8uxyx5M3R8og=

--
Frode Nordahl
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss 
[mail.openvswitch.org]
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN Dynamic Routing

2021-01-07 Thread Daniel Alvarez Sanchez 
Thanks Ankur, all for the presentation and slides.

If I may, I have a some questions regarding the proposed solution:

1) Who is responsible for creating the VTEP endpoints on each hypervisor?
Are they assumed to be created in advance or somehow this solution will
take care of it? If the latter, how will it work and how will 'ovn-routing'
know the addresses of the endpoints? OVN VTEP gateways?

2) In the diagram at [0], what's the 'MAC ROUTER'? Is this OVN Logical
Router connected to a Logical Switch with a localnet port and this MAC
address corresponds to such port in the router? Or it would be the MAC
address of '10.0.0.1'. What if two VMs in the same LS reside on different
hypervisors, would you still advertise the same MAC but use a different VNI?
With OVN routers being distributed we'd have the same MAC address
advertised on multiple HVs and we need to use different VNIs to distinguish
them, right?

3) If two OVN VMs want to reach each other, it will still use the Geneve
overlay right? This whole solution is mainly for incoming traffic or I'm
missing something?

I'm sorry if the questions are a bit blurry but I guess that after
reviewing the slides and recording I didn't quite grasp it :)

Thanks a lot in advance!
daniel

[0] https://youtu.be/9DL8M1d4xLY?t=330


On Mon, Dec 14, 2020 at 8:25 PM Ankur Sharma 
wrote:

> Hi Frode,
>
> Glad to see your message.
> Yes, while we started with EVPN as our main use case, we agree that it is
> more of a generic dynamic routing capability in OVN.
>
> Sure, we will kickstart the discussions around this on mailing list as
> well.
>
>
> Thanks
>
> Regards,
> Ankur
> --
> *From:* Frode Nordahl 
> *Sent:* Thursday, December 10, 2020 1:10 AM
> *To:* Ankur Sharma 
> *Cc:* Greg Smith ; ovs-discuss <
> ovs-discuss@openvswitch.org>
> *Subject:* OVN Dynamic Routing
>
> Hello, Ankur, Greg, All,
>
> Thank you for sharing your view on dynamic routing support for OVN
> during OVSCON 2020 [0].
>
> I believe this is a topic that interests multiple parties in the
> community, and it applies to multiple topologies/use cases, not just
> EVPN.
>
> Would you be interested in presenting and discussing the proposed
> design on the mailing list?
>
> 0:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openvswitch.org_support_ovscon2020_=DwIBaQ=s883GpUCOChKOHiocYtGcg=mZwX9gFQgeJHzTg-68aCJgsODyUEVsHGFOfL90J6MJY=3HUT7aQXAsSImmITSraoqdZ6mWcRxUtwVRKAfH3ygQA=Xzze2S3f7Rstp66gRz7MSuTGvGltr3t8uxyx5M3R8og=
>
> --
> Frode Nordahl
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss