Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000
Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE
Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472.
Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts.
This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186
Setup: 0ubuntu1. 1~cloud0 /docs.openstack .org/mitaka/ networking- guide/config- mtu.html
Pike neutron 11.0.2-
OVS 2.8.0
Jumbo frames setttings per: https:/
global_physnet_mtu = 9000
path_mtu = 9000
Symptoms:
gre_sys MTU is 1472
Instances with MTUs > 1500 fail to communicate across GRE
Temporary Workaround:
ifconfig gre_sys MTU 9000
Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472.
Previous behavior:
With Ocata or Pike and OVS 2.6.x
gre_sys MTU defaults to 65490
It remains at 65490 through restarts.
This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: /github. com/openvswitch /ovs/commit/ 8c319e8b73032e0 6c7dd1832b3b31f 8a1189dcd1 /github. com/openvswitch /ovs/commit/ 3a414a0a4f1901b a015ec80b917b9f b206f3c74f /github. com/openvswitch /ovs/blob/ 6355db7f447c8e8 3efbd4971cca926 5f5e0c8531/ datapath/ vport-internal_ dev.c#L186
https:/
https:/
https:/