cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Weller <swel...@ena.com.INVALID>
Subject Re: Circumventing VXLAN MTU issues
Date Mon, 20 Nov 2017 17:36:31 GMT
Change your host interface MTU to something a lot higher.


________________________________
From: Nux! <nux@li.nux.ro>
Sent: Monday, November 20, 2017 10:51 AM
To: users
Cc: dev
Subject: Re: Circumventing VXLAN MTU issues

Hi,

I probably can use jumbo frames, but for now my lab is restricted to a single machine.
Anything I can do in this situation?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Simon Weller" <sweller@ena.com.INVALID>
> To: "dev" <dev@cloudstack.apache.org>, "users" <users@cloudstack.apache.org>
> Sent: Monday, 20 November, 2017 16:38:33
> Subject: Re: Circumventing VXLAN MTU issues

> Lucian,
>
> Can you run jumbos on your switches?
>
> - Si
>
>
> ________________________________
> From: Nux! <nux@li.nux.ro>
> Sent: Monday, November 20, 2017 10:08 AM
> To: dev
> Cc: users
> Subject: Circumventing VXLAN MTU issues
>
> Hello,
>
> I am playing around with the native VXLAN implementation and I have of course
> hit the situation where MTU on the host gets chomped by 50 bytes and traffic
> crawls to a stop in the VMs.
> How are you people circumventing this? The easiest, but kind of inconvenient for
> customers would be to set MTU 1450 inside the VM, though it could be baked into
> the templates or via cloud-init.
>
> Is the OpenVSwitch implementation (of VXLAN) suffer from the same problem, I
> understand ovs can dynamically adjust MTUs to compensate (?), but at the same
> time this VXLAN implementation suffers from some limitations (multicast etc).
>
> Lucian
>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message