[ovs-discuss] ovs del-port does not clean up ethX.Y vlan interfaces

Tue Sep 30 15:59:26 UTC 2014

Hi Ben,

There seems to be another problem here with the VLAN Splinters.

ovs-vsctl add port eth2 trunks 105

ovs-vsctl add port eth2 trunks 104

[root at XXX-BServer01 backend_ui_script]# ovs-vsctl get port eth2 trunks

[104, 105]

[root at XXX-BServer01 backend_ui_script]# ifconfig | grep eth2

eth2      Link encap:Ethernet  HWaddr 00:25:90:EA:28:E2

eth2.104  Link encap:Ethernet  HWaddr 00:25:90:EA:28:E2

eth2.105  Link encap:Ethernet  HWaddr 00:25:90:EA:28:E2

If I now add another port eth3 to the bridge, it automatically creates following interfaces:

[root at XXX-BServer01 backend_ui_script]# ifconfig | grep eth3

eth3      Link encap:Ethernet  HWaddr 00:25:90:EA:28:E3

eth3.104  Link encap:Ethernet  HWaddr 00:25:90:EA:28:E3

eth3.105  Link encap:Ethernet  HWaddr 00:25:90:EA:28:E3

Even though I want to use eth3 with other VLANs . Can you please look into this?

I am already on kernel 3.10.

Regards,

Madhur

-----Original Message-----
From: Ben Pfaff [mailto:blp at nicira.com]
Sent: 18 September 2014 00:07
To: Madhur Sethi
Cc: 'discuss at openvswitch.org'
Subject: Re: [ovs-discuss] ovs del-port does not clean up ethX.Y vlan interfaces

OK.

OVS is supposed to remove the vlan interfaces when they are no longer needed.  VLAN splinters are not widely used so there could be a bug.

I'll try to check but it's a low priority.

Until then, please consider using some other workaround.  The FAQ lists

several:

Q: VLANs don't work.

A: Many drivers in Linux kernels before version 3.3 had VLAN-related

   bugs.  If you are having problems with VLANs that you suspect to be

   driver related, then you have several options:

       - Upgrade to Linux 3.3 or later.

       - Build and install a fixed version of the particular driver

         that is causing trouble, if one is available.

       - Use a NIC whose driver does not have VLAN problems.

       - Use "VLAN splinters", a feature in Open vSwitch 1.4 and later

         that works around bugs in kernel drivers.  To enable VLAN

         splinters on interface eth0, use the command:

           ovs-vsctl set interface eth0 other-config:enable-vlan-splinters=true

         For VLAN splinters to be effective, Open vSwitch must know

         which VLANs are in use.  See the "VLAN splinters" section in

         the Interface table in ovs-vswitchd.conf.db(5) for details on

         how Open vSwitch infers in-use VLANs.

         VLAN splinters increase memory use and reduce performance, so

         use them only if needed.

       - Apply the "vlan workaround" patch from the XenServer kernel

         patch queue, build Open vSwitch against this patched kernel,

         and then use ovs-vlan-bug-workaround(8) to enable the VLAN

         workaround for each interface whose driver is buggy.

         (This is a nontrivial exercise, so this option is included

         only for completeness.)

   It is not always easy to tell whether a Linux kernel driver has

   buggy VLAN support.  The ovs-vlan-test(8) and ovs-test(8) utilities

   can help you test.  See their manpages for details.  Of the two

   utilities, ovs-test(8) is newer and more thorough, but

   ovs-vlan-test(8) may be easier to use.

On Wed, Sep 17, 2014 at 05:55:54PM +0000, Madhur Sethi wrote:

> No Ben. No ipaddress was configured on the eth3.5. None of the ethX on the host in my setup have ipaddresses.

>

> Regards,

> Madhur Sethi

> -----Original Message-----

> From: Ben Pfaff [mailto:blp at nicira.com]

> Sent: 17 September 2014 23:23

> To: Madhur Sethi

> Cc: 'discuss at openvswitch.org'

> Subject: Re: [ovs-discuss] ovs del-port does not clean up ethX.Y vlan

> interfaces

>

> Did you configure an IP address on eth3.5 (e.g. with "ifconfig")?

>

> On Wed, Sep 17, 2014 at 05:26:50PM +0000, Madhur Sethi wrote:

> > Thanks for the reply Ben.

> >

> > Yes , I did enable the vlan-splinters. The ports have intel igb drivers and the vlan doesn't work without enabling the vlan splinters. If its deprecated then could you please point me to the newer workaround?

> >

> >

> > Regards,

> > Madhur Sethi

> >

> > -----Original Message-----

> > From: Ben Pfaff [mailto:blp at nicira.com]

> > Sent: 17 September 2014 22:52

> > To: Madhur Sethi

> > Cc: 'discuss at openvswitch.org'

> > Subject: Re: [ovs-discuss] ovs del-port does not clean up ethX.Y

> > vlan interfaces

> >

> > On Wed, Sep 17, 2014 at 09:49:23AM +0000, Madhur Sethi wrote:

> > > I am facing an issue wrt the del-port command here. Refer to my config here:

> > > Commands used:

> > > ovs-vsctl add-port OVS-VlanBridge vnet96 ovs-vsctl set port vnet96

> > > tag=5 ovs-vsctl add-port OVS-VlanBridge eth3

> > >

> > >

> > > [root@ kvm ~]# ovs-vsctl show

> > > 412338cc-eca8-4ea0-a4d8-793ec0444d23

> > > Bridge OVS-VlanBridge

> > >        Port OVS-VlanBridge

> > >             Interface OVS-VlanBridge

> > >                 type: internal

> > >        Port "eth3"

> > >             Interface "eth3"

> > >        Port "vnet96"

> > >             tag: 5

> > >             Interface "vnet96"

> > >

> > > The port vnet96  is connected to a vm interface which provides outside access to the vm for VLAN 5.

> > > The eth3 port is the physical port on the host connected to the outside world.  It acts as a trunk with no trunk tags specified, hence being a VLAN all trunk port.

> > > Ifconfig output on the host :

> > >

> > > [root@ kvm ~]# ifconfig | grep eth3

> > > eth3      Link encap:Ethernet  HWaddr 0C:C4:7A:12:33:27

> > > eth3.5    Link encap:Ethernet  HWaddr 0C:C4:7A:12:33:27

> > >

> > > The eth3.5 is automatically created by the OVS. If however I delete the eth3 from OVS-VlanBridge using the del-port command the eth3.5 is not cleaned up. Do I need an additional command to clean this up? Or is this an bug?

> >

> > eth3.5 would only be created automatically by OVS if you enable the deprecated "vlan splinters" feature.  Did you enable vlan splinters?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140930/92b9a766/attachment-0002.html>