[one-users] haveing problem with vswitch

[Jaime Melis]

Hi,

I think you should just configure your networking to use a single bridge
'br0' created with openvswitch. I don't really get why you need br10?

cheers,
Jaime


On Thu, Sep 5, 2013 at 1:09 PM, 12navidb2 at gmail.com <12navidb2 at gmail.com>wrote:

> thx man for reply :)
>
> hmm. u mean, I'm creating br0 from */etc/network/interfaces* ? that's my
> config
>
>
> iface p5p1 inet manual
>     pre-up ifconfig $IFACE up
>     pre-down ifconfig $IFACE down
> auto br0
> iface br0 inet static
>    address 172.20.0.14
>    network 172.20.0.0
>    netmask 255.255.255.0
>    gateway 172.20.0.1
>    bridge_ports p5p1
>    dns-nameservers 8.8.8.8
>
> with this config, i think so ubuntu use brctrl,
>
> *brctl show
> bridge name    bridge id        STP enabled    interfaces
> br0        8000.3085a9b07cae    no        p5p1*
> ovs-vsctl add-br br0
> and then use this command *ovs-vsctl add-br br0* ?
>
> or i changing my config  to below?
>
> auto p5p1
> iface p5p1 inet static
>    address 172.20.0.14
>    network 172.20.0.0
>    netmask 255.255.255.0
>    gateway 172.20.0.1
>    dns-nameservers 8.8.8.8
>
> and then use *ovs-vsctl add-br br0*?
> 2013/9/4 Dmitri Chebotarov <dchebota at gmu.edu>
>
>>  Can you create br0 with real interfaces before you add host to ONE and
>> use br0 in network config section? The same way you created fake br10, but
>> use ethXX . This should work...
>>
>>  You don't need brctl, OVS takes care of creating br0 with 'ovs-vsctl
>> addbr'.
>>
>>  ------------------------------
>> *From:* users-bounces at lists.opennebula.org <
>> users-bounces at lists.opennebula.org> on behalf of 12navidb2 at gmail.com <
>> 12navidb2 at gmail.com>
>> *Sent:* Wednesday, September 04, 2013 6:28 AM
>> *To:* users at lists.opennebula.org
>> *Subject:* [one-users] haveing problem with vswitch
>>
>>   I read openvswitch document completely about openvswitch
>> http://opennebula.org/documentation:rel4.2:openvswitch
>>
>>  there is 2 way for using openvswitch, i can implant  second way (*ovswitch_brcompat)
>> *but this way is deprecated
>> *Bridge compatibility is deprecated and may be removed no earlier than
>> February 2013*
>>
>>  now but when I'm using first way, (using from openvswith without  * brcompat
>> *and use from brctrl instead), opennebula when deploying new vm get
>> error.
>>
>>
>>
>> Wed Sep 4 06:05:28 2013 [VMM][I]: post: Executed "sudo /usr/bin/ovs-vsctl
>> set Port vnet0 tag=550".
>> Wed Sep 4 06:05:28 2013 [VMM][I]: ovs-ofctl: br0 is not a bridge or a
>> socket
>> Wed Sep 4 06:05:28 2013 [VMM][E]: post: Command "sudo /usr/bin/ovs-ofctl
>> add-flow br0
>> in_port=,dl_src=02:00:ac:14:04:04,priority=40000,actions=normal" failed.
>> Wed Sep 4 06:05:28 2013 [VMM][E]: post: ovs-ofctl:
>> dl_src=02:00:ac:14:04:04: bad syntax for in_port
>> Wed Sep 4 06:05:28 2013 [VMM][E]: ovs-ofctl: dl_src=02:00:ac:14:04:04:
>> bad syntax for in_port
>>
>>  the main problem is that br0 is not created with openvswitch and create
>> with brctl :)
>>
>>  but for solve this problem, I create fake bridge with openvswith
>>
>>  # ovs-vsctl add-br br0
>> # ovs-vsctl add-port br0 eth1
>> # ovs-vsctl add-br br10 br0 10
>> # ovs-vsctl list-br
>> br0
>> br10
>>
>>  so I inform to opennebula, br10 is my bridge
>>  now problem is ovs-ofctl using br10 instead br0 and i get error from ovs-ofctl
>> .
>>
>>  in this situation, ovs-vsctl must use fake bridge (br10) and ovs-ofctl
>> must use real bridge (br0) until anything  work well
>>
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>


-- 
Join us at OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin, 24-26
September, 2013
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | jmelis at opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130917/a4ba337b/attachment-0002.htm>