[ovs-discuss] VLAN splinters: How to make it effective after system reboot

Linux user linuxuser096 at gmail.com
Thu Nov 7 01:16:40 UTC 2013


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 <ashishyadav78 at gmail.com>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 <linuxuser096 at gmail.com> 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 at 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
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20131107/111f35a0/attachment.html>


More information about the discuss mailing list