[Bug 1674307] [NEW] Neutron v9 jumbo frames support

Piotr Malinowski cbspidi at gmail.com
Mon Mar 20 12:19:17 UTC 2017


Public bug reported:

Hi Guys

I just recant deployed openstack ocata using ubuntu-16.04, MAAS 2.1.3
and JUJU charm,

All my servers are set to use MTU=9000 on all connected
interfaces(setting propagated via MAAS/DHCP)

I have set configuration flags in neutron-api charm to reflect MTU size,
yet when i create networks its always uses MTU=1500

juju config neutron-api path-mtu=8600
juju config neutron-api global-physnet-mtu=9000
juju config neutron-api network-device-mtu=9000
juju config neutron-gateway instance-mtu=8500

When check interface MTU (phisical interface) all systems are reporting
jumbo size (9000).

One thing i have spotted when checked OVS bridges the br-tun bridge MTU
is only 1500

The behaviour is exactly same in both overlay setups vxlan/gre.


2: eno1: mtu 9000
3: eno2: mtu 9000
4: eno3: mtu 9000
5: eno4: mtu 9000
6: enp4s0: mtu 9000
7: enp5s0: mtu 9000
8: bond0: mtu 9000
9: bond1: mtu 9000
10: br-bond0: mtu 9000
11: ovs-system: mtu 1500
12: br-int: mtu 1450
13: br-ex: mtu 9000
14: br-tun: mtu 1500
15: lxdbr0: mtu 1500


JUJU app versions

neutron-api 9.0.0
neutron-gateway 9.0.0
neutron-openvswitch 9.0.0
nova-cloud-controller 14.0.2
nova-compute 14.0.2

Any assistance in fixing this will be greatly appreciated.

Thanks 
Piotr

** Affects: neutron (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1674307

Title:
  Neutron v9 jumbo frames support

Status in neutron package in Ubuntu:
  New

Bug description:
  Hi Guys

  I just recant deployed openstack ocata using ubuntu-16.04, MAAS 2.1.3
  and JUJU charm,

  All my servers are set to use MTU=9000 on all connected
  interfaces(setting propagated via MAAS/DHCP)

  I have set configuration flags in neutron-api charm to reflect MTU
  size, yet when i create networks its always uses MTU=1500

  juju config neutron-api path-mtu=8600
  juju config neutron-api global-physnet-mtu=9000
  juju config neutron-api network-device-mtu=9000
  juju config neutron-gateway instance-mtu=8500

  When check interface MTU (phisical interface) all systems are
  reporting jumbo size (9000).

  One thing i have spotted when checked OVS bridges the br-tun bridge
  MTU is only 1500

  The behaviour is exactly same in both overlay setups vxlan/gre.

  
  2: eno1: mtu 9000
  3: eno2: mtu 9000
  4: eno3: mtu 9000
  5: eno4: mtu 9000
  6: enp4s0: mtu 9000
  7: enp5s0: mtu 9000
  8: bond0: mtu 9000
  9: bond1: mtu 9000
  10: br-bond0: mtu 9000
  11: ovs-system: mtu 1500
  12: br-int: mtu 1450
  13: br-ex: mtu 9000
  14: br-tun: mtu 1500
  15: lxdbr0: mtu 1500

  
  JUJU app versions

  neutron-api 9.0.0
  neutron-gateway 9.0.0
  neutron-openvswitch 9.0.0
  nova-cloud-controller 14.0.2
  nova-compute 14.0.2

  Any assistance in fixing this will be greatly appreciated.

  Thanks 
  Piotr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1674307/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list