yahoo-eng-team team mailing list archive

[Ian Kumlien <1744101@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When vxlans are created, f.ex. via ensure_vxlan in
neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py
- no mtu is assigned.

This explains why we get vxlan interfaces with 1500 byte mtu even-though
neutron has been instructed to use 9000 bytes mtu.

The function called:
    def add_vxlan(self, name, vni, group=None, dev=None, ttl=None, tos=None,
                  local=None, srcport=None, dstport=None, proxy=False):
        cmd = ['add', name, 'type', 'vxlan', 'id', vni]
...

Creates the interface, and from what I understand mtu should be between
'add' and 'type'.

I have been unable to find any other place where the mtu would be
propagated to the vxlan interface and our tests indicate that it never
happens.

The problem is that this causes the bridge to set it self to the lower
mtu and... noone is happy =)

This is on:
git describe
11.0.2-8-g7fd30cb
(stable/pike)

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1744101

Title:
  vxlan interfaces doesn't get MTU

Status in neutron:
  New

Bug description:
  When vxlans are created, f.ex. via ensure_vxlan in
  neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py
  - no mtu is assigned.

  This explains why we get vxlan interfaces with 1500 byte mtu even-
  though neutron has been instructed to use 9000 bytes mtu.

  The function called:
      def add_vxlan(self, name, vni, group=None, dev=None, ttl=None, tos=None,
                    local=None, srcport=None, dstport=None, proxy=False):
          cmd = ['add', name, 'type', 'vxlan', 'id', vni]
  ...

  Creates the interface, and from what I understand mtu should be
  between 'add' and 'type'.

  I have been unable to find any other place where the mtu would be
  propagated to the vxlan interface and our tests indicate that it never
  happens.

  The problem is that this causes the bridge to set it self to the lower
  mtu and... noone is happy =)

  This is on:
  git describe
  11.0.2-8-g7fd30cb
  (stable/pike)

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