[ovs-dev] Loss of Network Connectivity
jpettit at nicira.com
Mon Dec 7 12:57:01 PST 2009
Just as you would with the bridge, you need to have all the devices you want to communicate on bridges. The way you have it currently configured, eth0 and eth1 will pass traffic between themselves, but your VM won't see any traffic. In the Xen setups I've seen, each PIF gets its own bridge and VIFs are attached to the appropriate bridge. I would have expected your config file to look more like this:
(This is assuming that vif0.1 is connected to eth0. Move it to br1, if it should communicate through eth1.)
If you have OVS installed on your computer with the bridge compatibility code, then Xen should be making bridge calls that OVS will intercept and make work properly.
If instead you want to do all this configuration by hand, then you may want to check how Xen set up the bridge initially (you can see this with "brctl show"). Then, just recreate the configuration in ovs-vswitchd.conf.
On Dec 7, 2009, at 12:43 PM, Timothy Ficarra wrote:
> I am running ovs-vswitchd and ovs-brcompatd.
> The RX counters increase on lo, peth1, and vif0.1
> eth1 is registering a flat zero on TX and RX.
> T Ficarra
> --- On Mon, 7/12/09, Justin Pettit <jpettit at nicira.com> wrote:
>> From: Justin Pettit <jpettit at nicira.com>
>> Subject: Re: [ovs-dev] Loss of Network Connectivity
>> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
>> Cc: dev at openvswitch.org
>> Date: Monday, 7 December, 2009, 3:36 PM
>> I assume you're running ovs-vswitchd
>> and ovs-brcompatd, correct? Do you see the RX counters
>> going up on your network devices when you run ifconfig?
>> On Dec 7, 2009, at 12:23 PM, Timothy Ficarra wrote:
>>> Here are the details of the problem:
>>> ovs version:
>>> open vswitch 0.90.7
>>> no git
>>> no patches
>>> os version:
>>> Linux version 2.6.18-164.6.1.el5xen
>>> gcc version 4.1.2 20080704
>>> Contents of ovs-vwitchd.conf:
>>> output of ovs-dpctl show:
>>> flows: cur:0, soft-max:512,
>>> ports: cur:3, max:1024
>>> groups: max:16
>>> lookups: frags:0, hit:0, missed:0,
>>> queues: max-miss:100,
>>> port 0: br0 (internal)
>>> port 1: eth0
>>> port 2: eth1
>>> What actually happened:
>>> loss of network connectivity after
>>> % rmmod bridge
>>> % insmod
>>> % insmod
>>> What was expected to happen:
>>> no loss of network connectivity
>>> T Ficarra
>>> --- On Mon, 7/12/09, Ben Pfaff <blp at nicira.com>
>>>> From: Ben Pfaff <blp at nicira.com>
>>>> Subject: Re: [ovs-dev] Loss of Network
>>>> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
>>>> Cc: dev at openvswitch.org
>>>> Date: Monday, 7 December, 2009, 12:05 PM
>>>> Timothy Ficarra <t.ficarra at yahoo.com>
>>>>> After following the steps in 'Using Open
>> vSwitch in
>>>> place of
>>>>> Linux bridging' the system is left in a state
>>>>> connectivity. Is there any further
>> configuration which
>>>> must be
>>>>> completed in order for the switch to function
>>>> There's too little information here to guess what
>>>> Could you include the information from the
>>>> This additional information might give us
>> something to work
>>> New Email names for you!
>>> Get the Email name you've always wanted on the new
>> @ymail and @rocketmail.
>>> Hurry before someone else does!
>>> dev mailing list
>>> dev at openvswitch.org
> Get your new Email address!
> Grab the Email name you've always wanted before someone else does!
> dev mailing list
> dev at openvswitch.org
More information about the dev