Given that Path MTU Discovery is depreciated/no longer supported:
> - Tunnel Path MTU Discovery default value was set to 'disabled'.
> This feature is deprecated and will be removed soon.
http://openvswitch.org/releases/NEWS-1.9.0
What is the recommended best practice?
The situation at $WORK is: OpenStack Grizzly (Havanna RSN) on Ubuntu 13.04.
Originally running on OVS 1.9 but upgrade to 1.11 with compiled-from-source
Debian packages. We're currently using GRE between the compute nodes and the
network node for the current "beta", but will probably be going to VXLAN in the
next implementation.
After the OvS upgrade it was found that SSH still worked but SCP did not, and
this led to changing the VM/instance MTU:
http://unix.stackexchange.com/questions/14187
We found that an MTU of 1454 and below worked, but 1455 and above did not.
What is the recommended long-term best practice? Do we set the MTU lower on
the instances (via DHCP option 26), or do we set the MTU of the compute and
network nodes' NICs higher (e.g., 14546). Or is there a third option?
Thanks for any info.
Regards,
David
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
