Read the FAQ.
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 Thu, Nov 07, 2013 at 07:04:12AM +0530, ashish yadav wrote:
> Hi,
>
> I don't think , you can find any Configuration Cookbook for Vlan Splinters.
> Not so much material available on Vlan Splinters user cases ( like
> modification of network scripts for Vlan Splinters).
>
> You may need to see ovs-vswitchd.conf.db.5.pdf.
>
> May be Ben Pfaff or Jesse Gross help you in this issue.
>
>
> Thanks & Regards
> Ashish
>
>
> On Thu, Nov 7, 2013 at 6:46 AM, Linux user <[email protected]> wrote:
>
> > Hi Ashish,
> >
> > You are right, Its not work out.
> >
> > If we have any Configuration Cookbook for Vlan Splinters or some sort of
> > user case shown ?
> >
> > Thanks
> >
> >
> >
> >
> > On Wed, Nov 6, 2013 at 12:15 PM, ashish yadav
> > <[email protected]>wrote:
> >
> >> Hi,
> >>
> >> I am not sure if this works, But if Vlan Splinters is allowed on Bridge
> >> Port ovsbr0 ( as this is internal type) ?
> >>
> >> Thanks & Regards
> >> Ashish
> >>
> >>
> >>
> >> On Wed, Nov 6, 2013 at 9:51 AM, Linux user <[email protected]>wrote:
> >>
> >>> Hi ,
> >>>
> >>> As we already know that Vlan OVS (openvswitch.ko) not works with
> >>> Centos/Redhat 6.4 Kernel.
> >>>
> >>> I have used VLAN splinters as describe in
> >>> http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD
> >>>
> >>> I used "ovs-vsctl set interface ovsbr0
> >>> other-config:enable-vlan-splinters=true"
> >>>
> >>> Its works fine, but as soon as I reboot system Vlan OVS not works.
> >>>
> >>> So, How to make VLAN splinters effective after reboot ?
> >>>
> >>> I think we need to add a line in
> >>> /etc/sysconfig/network-scripts/ifcfg-ovsbr0:
> >>> other-config:enable-vlan-splinters=true
> >>>
> >>> Please let me know if my above understanding is correct or not ?
> >>>
> >>> My System network looks like:
> >>> [root@linux]# ovs-vsctl show
> >>> f95289de-40e2-4bf5-9f07-3c8300e296db
> >>> Bridge "ovsbr0"
> >>> Port "eth0"
> >>> Interface "eth0"
> >>> Port "ovsbr0"
> >>> Interface "ovsbr0"
> >>> type: internal
> >>> Port "ovsbr0.4093"
> >>> tag: 4093
> >>> Interface "ovsbr0.4093"
> >>> type: internal
> >>> ovs_version: "1.4.6"
> >>>
> >>> _______________________________________________
> >>> discuss mailing list
> >>> [email protected]
> >>> http://openvswitch.org/mailman/listinfo/discuss
> >>>
> >>>
> >>
> >
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
